At least for me, one of the main factors when deciding to buy new phone is 3rd party development community. And what place is better to find custom ROMs than XDA-Developers? However, it is hard to determine which devices are more XDActive than other. Only statistics I have found was total number of posts, which does not help much as 3 year old device will probably have more total posts than 3 months old one even though 3 year old device will be more abandoned than new one.
That is why I decided to make little scrapper that went through all recent threads on all development forums and counted all posts made in October 2015. Results are there:
RAW Data
CLICK
Breakdown by manufacturer flagships
Here is little graph that displays all posts made in October 2015 broken down by manufacturer and phone release date (all flagships from specific year and manufacturer are counted together):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(I had to collect these manually so graph only includes flagship phones).
As you can see, if you get anything else than Nexus, Samsung or Oneplus, activity on the XDA will be relatively low regardless of the device's age. While 2015 devices are included on the graph, numbers for most of them are irrelevant because they were just released. However we can still make some comparisons, for example between HTC, Samsung, LG. Even though they have been released at about the same time, activity on this year Samsung's devices is already comparable to last year's and it is vastly higher than all other devices..
Original Development breakdown
Second graph is similar to first one, but only counts posts made in Original Development forums of the devices. That shows clear picture of actual development, instead of just buttload of ROMs with changed themes or different baked-in apps.
I don't think there is anything surprising here. Anything except for Nexuses and Oneplus scored really bad here.
I will attempt to re-do those periodically and post the result, I think it will be interesting to see how device activity evolves over time, especially for 2015 Samsung devices that only have supposedly developer-unfriendly Exynos chips.
After an analysis I found that number of all posts is not very indicative of device's activity. For example G4 development forums are barren wasteland, except for one thread that generated a lot of traffic, moving it near the top of the list even though there was no activity really.
That is why I updated RAW data link in first post with two additional metrics:
Number of all threads that were posted to in October 2015. I feel this is much better metric, because it indicates that device is actually active, not just one lone ROM.
Number of posts made by recognized contributors/developers. This metric is suspectible to the "one active thread" metric as original one, but it can be used to distinguish between actual developers posting something instead of people just rambling about.
Related
I am a big fan of ASUS.. and here is the pic of one leaked model they are supposed to launch in 1st three months of 2011..!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is what they have to say:
“We want to be more focused, so we do a lot of integration in terms of the software and maps. This kind of integration takes time, so we won’t launch a lot of models like other competitors. We want to be focused and provide the best location-based services for our customers” Fei Yen, Garmin-Asus
Damn, it's fugly ;>
Purple11 said:
I am a big fan of ASUS.. and here is the pic of one leaked model they are supposed to launch in 1st three months of 2011..!
This is what they have to say:
“We want to be more focused, so we do a lot of integration in terms of the software and maps. This kind of integration takes time, so we won’t launch a lot of models like other competitors. We want to be focused and provide the best location-based services for our customers” Fei Yen, Garmin-Asus
Click to expand...
Click to collapse
I thought garmin broke up with asus???
No matter really for me, asus rarely makes it to the states.
http://www.gpsworld.com/consumer-oe...asus-smartphone-partnership-end-january-10678
Purple11 said:
“We want to be more focused, so we do a lot of integration in terms of the software and maps. This kind of integration takes time, so we won’t launch a lot of models like other competitors. We want to be focused and provide the best location-based services for our customers”
Click to expand...
Click to collapse
Let me translate that for you: "We are going to mess with the software until WP7 will be completely unstable and lagging as hell. Furthermore we are trying to determine what the competition has been doing wrong to be sure that we are able to make the same mistakes. Then, months late, we will provide an ugly handset with outdated hardware and crappy software, just like we always did."
I don't think it looks that bad at all. Just a bad picture of it
Thanks, but that picture already got posted months ago...
skycamefalling said:
Let me translate that for you: "We are going to mess with the software until WP7 will be completely unstable and lagging as hell. Furthermore we are trying to determine what the competition has been doing wrong to be sure that we are able to make the same mistakes. Then, months late, we will provide an ugly handset with outdated hardware and crappy software, just like we always did."
Click to expand...
Click to collapse
ROTFL......
Another Clip called GameKlip appeared on the Market for Android users (lucky ones). This one is one of it’s kind, seems that have a better *grip* and better security to avoid your expensive cellphone end on the ground with a broken screen or worst
To quote:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Mobile games is a growing market, people love their mobiles and a lot love gaming so it’s a winning combination. However there is only so much fun you can have with a touch screen interface. It works great for some games but not so great with others. For a start putting your hands on the screen obscures your view of the game world. In addition it’s just more natural to use a physical controller, the shapes and designs of which have evolved for decades to make the most of gaming. GameKlip decided to pair a tried and trusted industry standard controller with you Android phone. The company chose the PlayStation 3 dual shock controller.
GameKlip is currently compatible with;
HTC One X
HTC Evo
Galaxy Note
Galaxy Nexus
Galaxy SII
Galaxy S
END OF THE ARTICLE - END OF THE ARTICLE - END OF THE ARTICLE - END OF THE ARTICLE - END OF THE ARTICLE - END OF THE ARTICLE - END OF THE ARTICLE - END OF THE ARTICLE - END OF THE ARTICLE
This is what I've send to the guy who made this little piece of magic:
Hi, my name is Santiago Console, I’m a Captivate Glide user and an active participant of the XDA Forum dedicated to the development for this phone. A few month’s back, we gathered a bunch of request, from people who were trying to make this guys:
http://www.game-gripper.com/
Adapt their product to our phone, for some reason, they didn’t bother, even after we gather more people than the D3 Community, and that guys ended up getting it. That aside, will you be interested in adapting the GameKlip to our phone ? I can assure you, that, at least, you will sell 30 units, right after you set up the pre-order J
To know the dimensions and the shape of our phone, you can look into this page:
http://www.gsmarena.com/samsung_i927_captivate_glide-4071.php
Thanks, and I hope you can make this happen
END OF THE E-MAIL- END OF THE ARTICLE - END OF THE ARTICLE - END OF THE ARTICLE - END OF THE ARTICLE - END OF THE ARTICLE - END OF THE ARTICLE - END OF THE ARTICLE - END OF THE ARTICLE
PD: Sorry bashing the GG guys, but, they have it coming, really.
PD2: Please, If you have some time, and want to have this "Clip" available for the Glide, take a few minutes, and write an E-Mail to the creator, and tell hin that, If he makes it, you will buy it. His E-Mail is [email protected]
Someone delete this spam
Sent from my SAMSUNG-SGH-I927 using xda premium
It's been like that since the first A10 update on February, (I'm global version)I'm on V11.0.14.0 now and it's has yet to be fixed, it's really starting to annoy me as I used to use that feature almost everyday, but it seems that Xiaomi is doing that on purpose, even the EU update has this bug now, people have been reporting ever since the first A10 update on February but they still released the EU update without fixing it (because they really don't want to), so I starting to think that we should make a petition on change.org or something because I've never seen such a bad customer service/development team from any other company in my life, I think it's just because this is stock Android not MIUI. I've been using the Feedback app since the first day they released it but i didn't get any response regarding this issue, doubt they check those reports, I had hopes that this was a bug it looks like it's a feature for people with Stock Android, so they can sell more MIUI phones.
Any thoughts?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I've lost any faith in Xiaomi support and customer service. I can confirm that, as European consumer, I've never seen a company ignoring their userbase as Xiaomi. I'm more disappointed as I was using Xiaomi phones and devices for years and now I feel like they're totally betraying their customers. No petition will change this attitude and they confirmed it, since they say that they make money through software and ads and not with the hardware.
Best way to use the A series is using a custom rom: until now I feel that Pixel Experience builds on A2 lite and A3 are way better than stock roms.
In customs roms and in the global version they are also lost and in all apps, not only the stock camera, they leave us 1/4 or at most 1 / 3s of exposure time, this problem I have seen in all roms whose base or vendor is 10, even in many gcam, except some, that if they manage to jump the exposure time limit, which makes me think that it is something that is in the vendor of the new update, in the global rom It has been reported since the first failed updates, the 48Mpx have also disappeared in the Open Camera, Android 10 has been a disaster for the cameras and apparently it is the intention of Xiaomi the limitation because if they had not corrected it a while ago.
I think the custom roms should all be done again with vendor 9 as the base, instead of vendor 10, since these limitations are absurd, or in any case find the solution.
Should be fixed with the upcoming May security patch updates as some users have been reporting.
"We’re delighted to announce that we are working with Google to sell genuine parts for Pixel phones, starting later this year. You can learn more about it in Google’s blog post.
We will be continuing to write our step-by-step Google Pixel phone repair guides, which are comprehensive going all the way back to the original Pixel. Repair guides are live for every Pixel through the Pixel 5, and we are writing guides for the 5a, 6, and 6 Pro right now.
Our parts selection will include everything you need for the most common Google Pixel repairs—batteries, displays, cameras, and more. We will sell them both individually and as part of Fix Kits, which include all the tools you need to fix your Google Pixel, from screwdriver bits to spudgers. "
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Google's Blog entry
Coming soon: More ways to repair your Pixel phone
We’re working with iFixit to make it easier to access the high-quality, genuine Google parts needed to repair Pixel phones.
blog.google
IFixit announcement
iFixit and Google are Launching a Genuine Pixel Parts Program | iFixit News
We’re delighted to announce that we are working with Google to sell genuine parts for Pixel phones, starting later this year. You can learn more about it in…
www.ifixit.com
---
This means that Google joined the growing list of companies that - at least officially - care for the Right to Repair. Since the EU is about to pass legislation (will still take a certain amount of time until it comes into effect) that will force companies to simplify battery removal, and other sustainability changes, this change of heart doesn't come as a surprise. But it's still ofc nice to see companies acting without immediate pressure.
This is a very good thing and about time, my only concern is the parts will all be sold with a hefty profit and therefore will not be very attractive to most people given you could bugger the phone up completely trying to repair it.
There are a few issues I see with XDA that need quick attention:
1. Posting a new threadIdeally, the 'Post Thread' button should be available universally, and user must choose the appropriate forum (and sub-forum) before the button gets activated for posting.
Currently, one has to 'search' to find forums and sub-forums, which itself isn't intuitive. This is more like Apple's way of implementing some of their things. This being the world of Android, we should stick with the simpler and intuitive approach.
Alternatively, there should be easy and quick access to the following two pages:
General Discussion
forum.xda-developers.com
Android Development and Hacking
forum.xda-developers.com
2. Sub-Forums by Android version and brandThere is a sub-forum for each device model. I guess this is done so users can find the right files to flash (this being the XDA) for their device. I'm not sure what % of posts on XDA are about flashing stuff.
I would like to think that the number of posts about general topics concerning Android would be far higher than those specific to flashing and modding.
In this regard, it would be nice to have a forum for each version of Android, and then a sub-forum per brand. An issue with a particular version of Android will affect all devices, especially those that are from the same brand. This will make it easy for users to find posts per Android versions and learn about problems that may not have been discussed in the device specific sub-forum.
An example:
When Samsung releases OneUI 6 based on Android 14 later this year, any issues with it would be seen on S23 Ultra, S23 Plus, S23, S22 Ultra, S22 Plus, S22, S21 FE, and a whole lot of devices that get OneUI 6. Same logic applies to all the smartphone brands.
It is far easier to discuss issues related to the OS version in one sub-forum than spread it out over multiple sub-forums, which will also result in many duplicate posts for the same issue. Plus, users watching device specific sub-forums may not be aware of issues on their device if they haven't been discussed in those sub-forums.
3. Filters in Watched section
Just as we have filters in New Posts section, it would be nice to have one in Watched section too.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I had already made a suggestion for this here and here.
Hopefully XDA would consider these suggestions after taking inputs from its members.
@TheMystic
It would be nice to post it here, your request might be seen by xda admins
https://forum.xda-developers.com/t/xenforo-2-2-upgrade-post-bugs-issues-and-comments-here.4245677/
khusika said:
@TheMystic
It would be nice to post it here, your request might be seen by xda admins
https://forum.xda-developers.com/t/xenforo-2-2-upgrade-post-bugs-issues-and-comments-here.4245677/
Click to expand...
Click to collapse
Already made a request in a different sub-forum (New Device Forum Request) some time back, and it got lost in the comments section.
I have posted a link to this post in the sub-forum you suggested. Thank you. Hopefully it won't get lost like last time.