Database Users

I'm done with all Android phones and tablets not released from Google.

FYI: This is a venting post, written spur of the moment. Probably rambling from point to point without proofreading or organizing thoughts. Don't even know if it will make sense to anyone.
In my haste to, you know, have the newest version of Android running on my Transformer, I totally destroyed it and cannot get it to be recognized in any USB form on my computer. There are tons of great ROMs built by the awesome development community, but I'm just sick of having to try out multiple ROMs just to find one that works without issues. IMO, the fault is split between Google and the hardware manufacturers. Google should force manufacturers to ship phones and tablets with stock Android. It is Google's system and they should have the control to do that. The manufacturers should be ashamed of themselves for not being able to release an update to the latest OS within a few weeks of the release, jellybean, and on a tablet that was only launched in the US in April 2011. Google should be ashamed for letting these manufacturers get away with running an outdated version on a device that is completely cabable of running the newest iteration. Had an official means of updating to Jellybean been available I would not have spent so much of my time rooting and testing ROMs to make sure I have a consistent user experience.
I look at Apple; the structure and consistency they have in regards to software updates. The first gen iPad received updates until iOS 5 for two years. Then you devices that are put out by Android manufacturers, new models are frequent and in the furry to try and saturate the market with tablets, they forget about the one that came out the day before. Too many screen sizes, different processors, causes developers to shy away. For example, there has yet to be a legitimate Spotify (which I use daily), twitter, Facebook tablet app. Even the official apps they do have for "tablets" are weak in the user interface compared to iPad apps.
I know the general public will probably never care that their phone/tablet doesn't receive the newest Android update, they call their phones "droids". That's because they don't know what they are missing since the manufacturers do not care about updating the firmware and they are running terrible skinned versions of the OS. I enjoy using my Galaxy Nexus on Verizon, but even that does not get updated from Google. Google needs to reassess how they distribute the OS and to who. Maybe it needs to be a little closed and vertical. It could help.

You have a very good point on it, I couldn't agree more with it.
But regarding the distribution of Android, I think that if the OS had to be the same on every phone/tablet, there wouldn't have a reason to exist so many different devices, it would be like Apple's iOS and its devices.
What makes the platform interesting is the fact that anyone can use it and alter some elements of it, a thing that you don't have in the strict control that Apple has on iOS.
Sent from my MB525 using xda app-developers app

I agree with you in certain points - as for update procedures in general.
I am still very annoyed by the update politics of the Transformer, since the officially offered upgrades caused so
many troubles for me, as random reboots and freezing ,......
On top of it, skilled people in this forum then manage to get nice kernels and ROMs done which are just
much better in performance and stability compared to stock, that you really do wonder who the heck ASUS is hiring
I found finally a stable combo for me based on ICS but failed so far for JB.
I am at the moment testing different JB EOS and kernel combos but experience still issues.
This can become indeed kind of boring....
Your view comparing the great support of Apple on the other hand I don't share completely. It is basically the same as for their Desktop/Laptops.
It is really so much easier to only support a handfulll of devices than thousands of different combinations. Sure, you have a point that
you benefit when you choose one of their devices. But bluntly I become afraid of the growing power of Apple, since I really embrace choice.
Their are always people who prefer a certain different device because it helps their needs ( look at all the different screen sizes for Android and
then check Apple), me I prefer e.g. HW keyboard for a mobile phone.
But then I prefer as well Linux and the choice to put together your preferred OS over a non-customizable MacOSX ...
BTW: I own as well Apple devices and this is not supposed to become a flame thread, please

At the end of the day its down to us as individuals what we buy.
The reviews are not always impartial but certainly a good starting point, but i find researching any product i buy before hand a must now a days.
Great example was when i had bought my gtab - if i had read about it properly i would have know Samsung are one of the worst for updates.....but then again none of the manufacturers promise any future upgrades - maybe again we are just expecting something that we were never told we were going to get??
Never had an issue with my TF but i agree you should not have to rely on a developers site to get "improved" versions of the software - but if i had an Ipad i would have no doubt jailbroken it to improve my ipad experience aswel, just like ive done in the past with ipod touches etc. Would i get another TF - yes - im looking to get the Infinity as i still feel that the Asus TF fits my needs and is still one of the best supported tablets out there.
So the moral of the story is nothings perfect, the infos out there......we just need to be a little more astute as individuals and put the time into looking at the pros and cons before we buy. We spend the money and make the choice - not Google, Asus or Apple.:good:

ultmontra08 said:
I totally destroyed it and cannot get it to be recognized in any USB form on my computer.
Click to expand...
Click to collapse
That's more or less impossible unless you managed to corrupt the first few EMMC blocks that contain the apx mode code. Which you have to know what you're doing to wipe.
Boot into apx mode, install the naked apx driver, then use Easyflasher to flash back to stock

ultmontra08 said:
In my haste to, you know, have the newest version of Android running on my Transformer, I totally destroyed it and cannot get it to be recognized in any USB form on my computer. There are tons of great ROMs built by the awesome development community, but I'm just sick of having to try out multiple ROMs just to find one that works without issues
Click to expand...
Click to collapse
ultmontra08 said:
I would not have spent so much of my time rooting and testing ROMs to make sure I have a consistent user experience.
Click to expand...
Click to collapse
ultmontra08 said:
I know the general public will probably never care that their phone/tablet doesn't receive the newest Android update, they call their phones "droids". That's because they don't know what they are missing
Click to expand...
Click to collapse
You don't need to update Android unless it's a big jump like going from Honeycomb to Ice Cream Sandwich going to all that trouble to Root, Install a custom Recovery, Install a custom ROM for a minor update like Jelly Bean is silly what could you possibly need from Jelly Bean that Ice Cream Sandwich can't already do I bet the only reason is "It's the latest" and Asus are officially going to release Jelly Bean for the Transformer.
ultmontra08 said:
There are tons of great ROMs built by the awesome development community, but I'm just sick of having to try out multiple ROMs just to find one that works without issues.
Click to expand...
Click to collapse
Unfortunately if you want to use something other then the stock ROM it's a process of trial and error I tried Android Revolution HD ROM for example (popular ROM) and had problems with my Transformer not responding in sleep mode and random reboots I found that Cyanogenmod was stable for my device every device is different so the trial and error process is unavoidable.
ultmontra08 said:
IMO, the fault is split between Google and the hardware manufacturers. Google should force manufacturers to ship phones and tablets with stock Android. It is Google's system and they should have the control to do that.
Click to expand...
Click to collapse
ultmontra08 said:
I enjoy using my Galaxy Nexus on Verizon, but even that does not get updated from Google. Google needs to reassess how they distribute the OS and to who. Maybe it needs to be a little closed and vertical. It could help.
Click to expand...
Click to collapse
Google Android is licensed as an open source operating system so Google doesn't have any power to tell manufactures they can't make their own version of Android to sell with their hardware or when you receive updates that's all the manufacturer.
ultmontra08 said:
since the manufacturers do not care about updating the firmware.
Click to expand...
Click to collapse
Asus have actually been great with Android updates for the Transformer just a bit slow.
ultmontra08 said:
The manufacturers should be ashamed of themselves for not being able to release an update to the latest OS within a few weeks of the release, jellybean, and on a tablet that was only launched in the US in April 2011.
Click to expand...
Click to collapse
You don't understand that it takes time to develop and test a new operating system on a device the process isn't as simple as you think it is you wouldn't want to suddenly get an update from Asus and then be complaining that it's unstable would you?.
ultmontra08 said:
there has yet to be a legitimate twitter, Facebook tablet app
Click to expand...
Click to collapse
If you are using a Tablet the screen is wide enough to be able to acceptably use a web browser for these tasks so you don't really need a specific App developed, it's really only necessary for Mobile due to small screens.
ultmontra08 said:
I look at Apple; the structure and consistency they have in regards to software updates. The first gen iPad received updates until iOS 5 for two years. Then you devices that are put out by Android manufacturers, new models are frequent and in the furry to try and saturate the market with tablets, they forget about the one that came out the day before. Too many screen sizes, different processors, causes developers to shy away.
Click to expand...
Click to collapse
If you prefer Apple feel free to switch but while having a range of hardware options does have it's down falls it gives you and developers more freedom and choice where as Apple will always have a small limited choice range.

Just get a Windows Phone or Windows 8 tablet. I am too, one of those who are totally sick about Android.
You know, I bought Asus Transformer TF101 right on launch and YOU HAVE NO idea how excited I am. But things started to change after using it for a day, lags, crashes, limited apps.
I've been waiting and waiting for months before ICS came, but a lot of issues are still left unresolved. Asus firmware is very prone to crashes.
I've been flashing ROM after ROM and wasted so many days on this... No way I will ever get an Android again.

LastBattle said:
Just get a Windows Phone ....
Click to expand...
Click to collapse
Talk about limited apps...

Eh, the way I look at it, ill have this tablet forever and by the time its so scratched and old I can give it to my kids and I can get the latest and greatest NEXUS having learned my lesson buying non NEXUS.
Sent from my SCH-I510 using xda app-developers app

im on jb rom from team EOS, this is the only jb rom i use until now. using nova launcher makes it almost perfect buttery smooth (perfect without Widgets on the screen) .
it's easy to find good rom without having to try all of them. just read people's comment. go to last page and see how many complaints user's has.

Using the EOS build 74 with KAT 1.4 and nothing else yields a Transformer that works perfectly for me minus the GPS. I know that people with the dock have a different set of issues but honest, my TF with EOS and KAT runs better than any stock ROM. The difference is amazing. Web browsing is very very fast, I can play all my 720P videos via SMB streaming with BSplayer.
So after more than a year my TF works as I expected it to out of the box.

ultmontra08 said:
I totally destroyed it and cannot get it to be recognized in any USB form on my computer.
Click to expand...
Click to collapse
Have you tried Wheelie?
http://forum.xda-developers.com/showthread.php?t=1676845

Android Revolution HD and be done with it. Why the need for the latest and greatest when you can use what works? I used to be an HTC fanboy, until I got the mytouch 4g slide. I hated that phone so much. I love Sense, but just the phone was.... eh. I'm very happy with my Galaxy S3. I feel like I should have opted for the Nexus, but I'm happy with my purchase.
I still have a G1 sitting on my dresser with a charged battery just in case I feel like rockin it oldschool. I'm an OG Android user. Been using android ever since the release of the G1. I do love vanilla android, but what Samsung did with TouchWiz is just short of amazing. I used to run MIUI on my HTC Vision, I ran it for a few hours on my S3, and had to go back to TouchWiz!!
And what was posted earlier, why are you using apps on a tablet when the browser works perfectly for all those websites? Apps are more of a phone thing, screen sizes sub-5"

The update from Honeycomb to ICS was a huge one and we got it, it was not bug free but good enough to get developers working. JB is not that big update unless you need Google Now.

wow i dont know where to start. i really dont want to turn this into an ios vs android flame war. but youre completly out of your mind. first of all you have to look at it from the carriers, hardware manf, and googles point of veiw.
now hardware manuf. , and carriers have it in their best interest to not release updates for all the previous gen devices from a year or two ago, even if they are capable of running the new versions. this way the new devices look more attractive to current and potential customers.
another thing is that you cant really compare the updates from iphone-iphone3g-iphone3gs-iphone4-iphone4s-iphone5-and probably in a couple months the iphone5s that wont do anything more exciting than the last model did. same thing with the ipads. before you know it you have a drawer full of iphones that look the same and dont really do anything different.
then you have android. approx 800,000 new android devices are activated every day. EVERY EFFIN DAY. now thats insane.
how many devices that didnt originally come with ios can now run ios better than they ran their org stock os? for example there are tons of devices that came stock with windows mobile/symbian/webos etc etc and they can now run many different versions of android.
my htc HD, my htc HD2, my hp touchpad, and those are just the ones ive owned. theres tons of others that were given new life because of android and the dev community.
another thing that doesnt make sense is how you can blame google, and the hardware manufacturers and the carriers for 3rd party apps that they have no involvement in. there are millions of developers making millions of apps for millions of devices. its not googles job to make sure they run perfectly on every device. thats the deveolpers fault if facebook app works better on one device than it does on another.
you see iphone and ipad apps dont really have that problem because all the devices are exactly the same. screen size/resolution doesnt change very much at all, and new features are a bore. "oh yay the new iphone can make face time calls over a cell connection and isnt limited to wifi anymore" so what they should have been able to do that years ago.
its also not googles or the hardware manuf. fault if you knowingly go against their waranty terms and screw up your device. thats the risk you knew was there. and its part of the learning process. things like unlocking bootloaders, building custom roms, modifying hardware, cross compiling drivers and kernels, overclocking, and overall getting he most out of your device, is not for kids.
yes the typical ios fanboy just wants to get his facebook updates and be able to locate the nearest starbucks, or genius bar, just by asking siri.
but the android dev comunity and the devices they work on are doing it right. why should you be told what you can and cant do with your device? why should you pay more for a device that only does less. why should you sleep on the sidewalk for 7 days to be first in line to get the new lame updated iphone that costs double and doesnt do double.
the hp touchpad is a great example of an awesome device that was on sale for 99-150 dollars from hp. it currently runs ICS like a champ, and will be getting JB roms that rock. i also have a tf101 asus that runs JB eos like WHOA! overclocked on both cores, awesome tegra2 chip. expandable memory, AND A NORMAL HEADPHONE PORT AND USB PORT. even a nice little hdmi port. its an old device already and it still blows he doors off any current gen ipad.
then theres the newer mk802 devices and hackberry A10 boards that will do anything a high end smartphone will do for 50 bucks and hooks right up to your tv. LETS see apple tv or roku do that.
bottom line is that you dont understand how this really works, and youre getting frustrated and giving up instead of learning and becoming better and the tech.
YOU EITHER MASTER TECHNOLOGY OR TECHNOLOGY WILL MASTER YOU!! thats all for now.
---------- Post added at 10:38 PM ---------- Previous post was at 10:30 PM ----------
redrol said:
Using the EOS build 74 with KAT 1.4 and nothing else yields a Transformer that works perfectly for me minus the GPS. I know that people with the dock have a different set of issues but honest, my TF with EOS and KAT runs better than any stock ROM. The difference is amazing. Web browsing is very very fast, I can play all my 720P videos via SMB streaming with BSplayer.
So after more than a year my TF works as I expected it to out of the box.
Click to expand...
Click to collapse
yeah i just updated with eos jb rom today and its so much faster than the stock asus ics rom. i was really surprise, because its still got a ways to go.
---------- Post added at 11:08 PM ---------- Previous post was at 10:38 PM ----------
Then you devices that are put out by Android manufacturers, new models are frequent and in the furry to try and saturate the market with tablets, they forget about the one that came out the day before. Too many screen sizes, different processors, causes developers to shy away.
Click to expand...
Click to collapse
just to clarify a couple of things. There's no such thing as Android Manufacturers. well i guess with the exception of googles devices that they release is as close as you could come to calling them and android manufacturer, but the rest are not Android manufacturers. and when you think about it the screen sizes are usually pretty consistent even across different hardware manuf. you had 2.8"/3.5"/3.8"/ 4.2's were common for a while. now youre seeing mini tablet/phones in the 4.7-5+ range. but there arent that many sizes to worry about development wise. same with tablets. 7"-8"-9.7"-10.1" etc etc. same with the cpu and gpu arcitecture. you got your arms, your tegras, your mali 400's, etc etc theres an android device for everyone for anything.
i also love how my buddies iphone 5 wont display netflix properly or pandora correctly on the new screen size/dimension. maybe the iphone5s ver. 2.1 will have fixed that. in a couple years.
I know the general public will probably never care that their phone/tablet doesn't receive the newest Android update, they call their phones "droids". That's because they don't know what they are missing since the manufacturers do not care about updating the firmware and they are running terrible skinned versions of the OS. I enjoy using my Galaxy Nexus on Verizon, but even that does not get updated from Google. Google needs to reassess how they distribute the OS and to who. Maybe it needs to be a little closed and vertical. It could help.
Click to expand...
Click to collapse
the general public doesnt care that their phones arent getting the newest rom/kernel versions although alot of them do. android seems to realease new versions as the hardware advances. they grow with the advancing power and abilities of devices. you wouldnt really expect a first generation tmobile g1 to run the latest jellybean version would you? its almost as if the hardware cannot really come out faster than the os to support it. everytime you hear of a new android version theres a whole new generation of way better spec'd devices that shortly follow. sorta opposite of apple, they release devices that are barely on par with devices that were released over 6 months ago or longer. if carriers dont want o update devices in order to entice customers to upgrade then i understand that. theyre in business to make a profit. i really dont see how restricting and limiting android would help in any way at all. thats the great thing about android. its just linux with a few things on top. and that is the nail in the coffin right there. unlimited customization and hackability.

haxin said:
YOU EITHER MASTER TECHNOLOGY OR TECHNOLOGY WILL MASTER YOU!! thats all for now.
Click to expand...
Click to collapse
AMEN!

[Q] Firefox 2.0 and Geeksphone Revolution

Hello,
I've searched around the forum and haven't seen anything related to this, so I thought I'd create a thread and ask in case anyone knew.
I was interested in purchasing the Geeksphone Revolution and was wondering if a Firefox 2.0 build existed for it? I see there is a a 2.0 build for the Peak and Keon, but those are not available for purchase. So would I be stuck on 1.3 if I got the Geeksphone or would someone have a build that could be loaded onto the Geeksphone Revolution?
Thanks in advance for any info

TheEternalAbyss said:
Hello,
I've searched around the forum and haven't seen anything related to this, so I thought I'd create a thread and ask in case anyone knew.
I was interested in purchasing the Geeksphone Revolution and was wondering if a Firefox 2.0 build existed for it? I see there is a a 2.0 build for the Peak and Keon, but those are not available for purchase. So would I be stuck on 1.3 if I got the Geeksphone or would someone have a build that could be loaded onto the Geeksphone Revolution?
Thanks in advance for any info
Click to expand...
Click to collapse
Hi,
to be honestly - I hate the developers of the Geeksphone. For several reasons:
1. The Android Project is just ****ed up - no USB drivers for PC / MAC (really, you have to put out the SD to copy data!)
2. in the beginning the battery had huge drainage - it just held not even a day (after some updates it's okay and useable!)
3. There are no updates since more than a month. In the beginning there were plenty updates for both systems - every week for android! Now I think they stopped the support.. don't know why
4. Firefox OS has plenty bugs, too - that's why no one uses it. No apps is not a bug - but the hardware keys always shine (that's a battery drainer without purpose - I mean under Android they go off after not touching them. Under FFOS they always stress me). Also other smaller bugs..
5. The most interesting feature - Dual boot - there is no actual dual boot (and never will be) - you can only use and flash 1 OS. Android or FireFox os.. or other os. =>
6. Other OS ? There are no other os! I am really sad that I bought a phone with the ability to flash other OS and there are no! You simply can use 2 buggy OS, none of them are really special or work perfectly.
7. The screen resolution of the phone isn't really nice and bright. I can't understand how they did this. Not even 720p. You can count the pixels in nearly every app..
8. No new updates any more ?! Mhh, don't know but no support from Hackers, no support from Geeksphone themselves - no Android, no FFOS updates (okay they said they would release FFOS 2.0 - but I believe there are still like no APPS in the store, probably other bugs, too but didn't test it).. and no OTHER OS! Okay, you have the ability but if no one releases one - that's a pity!
9. No accessories - you can get a pouch for this phone, but no better batteries, no other things.. I didn't even found replacement screen or something (don't need one, just in case)..
To be honestly - simply get another phone. Maybe Jollaphone, or Fairphone (which may get open webos support or firefox or others as well), or wait for Neo900 (Nokia N900 case with better hardware) or something else.
If you are fine with all those problems and bugs - then go ahead and buy one.
I'm just an honest user.. currently I use my HP Pre 3, Huawei Mate, Galaxy Camera as everyday devices, the Geeksphone more or less for spair and for music outside or something..
Greetz from Germany!

hackint0sh said:
Hi,
to be honestly - I hate the developers of the Geeksphone. For several reasons:
1. The Android Project is just ****ed up - no USB drivers for PC / MAC (really, you have to put out the SD to copy data!)
2. in the beginning the battery had huge drainage - it just held not even a day (after some updates it's okay and useable!)
3. There are no updates since more than a month. In the beginning there were plenty updates for both systems - every week for android! Now I think they stopped the support.. don't know why
4. Firefox OS has plenty bugs, too - that's why no one uses it. No apps is not a bug - but the hardware keys always shine (that's a battery drainer without purpose - I mean under Android they go off after not touching them. Under FFOS they always stress me). Also other smaller bugs..
5. The most interesting feature - Dual boot - there is no actual dual boot (and never will be) - you can only use and flash 1 OS. Android or FireFox os.. or other os. =>
6. Other OS ? There are no other os! I am really sad that I bought a phone with the ability to flash other OS and there are no! You simply can use 2 buggy OS, none of them are really special or work perfectly.
7. The screen resolution of the phone isn't really nice and bright. I can't understand how they did this. Not even 720p. You can count the pixels in nearly every app..
8. No new updates any more ?! Mhh, don't know but no support from Hackers, no support from Geeksphone themselves - no Android, no FFOS updates (okay they said they would release FFOS 2.0 - but I believe there are still like no APPS in the store, probably other bugs, too but didn't test it).. and no OTHER OS! Okay, you have the ability but if no one releases one - that's a pity!
9. No accessories - you can get a pouch for this phone, but no better batteries, no other things.. I didn't even found replacement screen or something (don't need one, just in case)..
To be honestly - simply get another phone. Maybe Jollaphone, or Fairphone (which may get open webos support or firefox or others as well), or wait for Neo900 (Nokia N900 case with better hardware) or something else.
If you are fine with all those problems and bugs - then go ahead and buy one.
I'm just an honest user.. currently I use my HP Pre 3, Huawei Mate, Galaxy Camera as everyday devices, the Geeksphone more or less for spair and for music outside or something..
Greetz from Germany!
Click to expand...
Click to collapse
Greetz from USA
Wow, everything that you said is quite interesting. I honestly don't care too much if there are bugs since Android has always had issues (and I'm talking official releases. That's why there are so many updates and each device can't guarantee it works because between Android changes, and hardware manufacturers customizations...it's a giant mess). I currently have a Open ZTE with a prerelease of FFOS 1.3 so like I said, a few bugs isn't a big deal.
No usb drivers is just plain silly though. Seriously that's pretty dumb :\
Thanks for the suggestions though, I'll check them out
I hadn't heard of Sailfish OS either. looks very interesting. I really am interested in FireFox OS though and I'd love to keep using it and watch it mature It really has great potential. That's why I thought it woul dbe nice to have something that allows me to switch between OS. I'm happy to consider other alternatives, so please anyone, keep the suggestions coming

hackint0sh said:
Hi,
1. The Android Project is just ****ed up - no USB drivers for PC / MAC (really, you have to put out the SD to copy data!)
Click to expand...
Click to collapse
That's why i use Linux

Geeksphone forum is start 18 August.

Marshmallow Defect Corrections Release?

It looks like Marshmallow is following the usual pattern of Android "x.0" alpha release to the public, followed by "x.0.1" beta release with initial defect ('bug") corrections starting with Nexus beta testers (I.e. Nexus users in general).
Reading about the MM 6.0 problems on MXPE, I'm sitting out the 6.0 alpha testing on the sideline with LP 5.1.1. Most trouble-free phone I've had yet, and I don't yet need the only compelling feature I see with MM on the MXPE (T-Mobile Band 12 support).
Any noises yet about MM beyond 6.0.1? (I know I can look for this elsewhere too, but thinking maybe some of the XDA community may have inside info from the Android community.)
TIA...

The marshmallow update give me some new features and better battery life (though I do own the X Style, not pure). Unless you are dead set on being intentionally obtuse, then this isn't considered an alpha update.
Also the 6.0.1 update is quite minor, the largest change being some ART performance improvements, the rest is adding bands to the Nexus line and some emoji's: http://www.androidheadlines.com/2015/12/google-posts-android-6-0-1-changelog.html

I know the label "alpha" is not not the official label for something like 6.0. But with so many substantial defects, and multiple forthcoming revisions to correct those defects a certainty, that's really what it is IMO. Maybe "public release alpha" would be a better description, since pre-release revisions go through even more defect-ridden levels including pre-release alpha, prior to public release.
Similar situation with previous Android versions, and in fact most software foisted on the public these days (I'm looking at you, Microsoft and Apple). Look at Lollipop and the multiple public release revisions it took to iron out most of the substantial defects, finally, with 5.1.1.
6.0.1 is not just "...some ART performance improvements, the rest is adding bands to the Nexus line and some emoji's...", it also includes defect corrections. (Bluetooth, anyone?) And if the changelog doesn't list a significant number of defect corrections, that doesn't necessarily mean it is already polished at 6.0.1. The fragmented Android ecosystem and separation between Google, phone manufacturers, carriers, and users guarantees a plethora of various non-trivial defects in the ecosystem, many of which Google will address only slowly or even never for most phones.
For example, the memory leak defect in LP was not fixed until 5.1.1. How may revisions and months did that take? How many phones still run pre-5.5.1 with this defect?
One reason I bought the MXPE was the idea that it would be one of the first to get the updates. That turned out to be overly optimistic. It looks like Nexus is the only one still close enough to the source to get timely updates, and it also looks like Google is not pursuing Android defect corrections with any kind of urgency at all nowadays, maybe because the hardware ecosystem is becoming way too diverse to adequately support any more (or maybe because the profits roll in no matter what). Motorola phones, with the Moto alterations to Android, outsider status with carriers, and now hollowed-out Motorola support, appear to be no closer to adequate Android support from Google than any other non-Nexus phone.
"Obtuse"? A "bug" is a euphemism for a defect. Let's stop being obtuse, and call it what it is.
Any other info also appreciated.

You're being obtuse by insisting that we're all public alpha testers.
You obviously have no idea about software development, nor about Android Open Source development. Not your fault, but running your mouth is.
You bemoan the memory leak fix took several revisions to fix. So, you think that Google dedicated the whole team to fixing that one bug? What then? No other bugfixes or features are introduced in the meantime? The likely case is (and this is from experience) that bug took some revisions to fix, in the meantime, Google were also pushing ahead with other fixes. Regardless to what the uneducated (about SW development), throwing 15 developers onto one problem doesn't solve it any quicker. 5.0.1 came, adn 5.0.2 came, then 5.1 came in the meantime. While that memory leak was being worked on, more releases come fixing other things. Be grateful they didn't listen to you and leave it at 5.0 for several months while they fixed one issue.
Whatever bluetooth fixes that you think are in 6.0.1 are pure fantasy, because none exist in AOSP 6.0.1: http://aosp.changelog.to/android-6.0.0_r5-to-android-6.0.1_r1.html <-- That's the FULL changelog of commits between 6.0.0_r5 and 6.0.1_r1.
It is not Google's job to fix a problem in anything other than their own devices. At all. Google's job is to make AOSP run smoothly on Nexus devices and release the source. Samsung, HTC, LG, Motorola et al all take the source code, just like CM, AICP, Slim and the rest do, and make modifications for their devices, using the sources given to them by their hardware partners and themselves. So if BT works in Nexus devices, but not others, then it's not Google's problem (usually). An AOSP issue will persist several devices, including Nexii devices.
Google also have taken on the quite large undertaking of monthly security updates for their devices, which I can tell you will be taking up some of the development teams time (it's what, 3-4 months into that project?).
No software ever released on this planet comes without bugs and issues. This is software development. You can check the status of AOSP development here: https://android-review.googlesource.com/#/q/status:open and feel free to download, code and submit your own features.

MattBooth said:
You're being obtuse by insisting that we're all public alpha testers.
You obviously have no idea about software development, nor about Android Open Source development. Not your fault, but running your mouth is.
You bemoan the memory leak fix took several revisions to fix. So, you think that Google dedicated the whole team to fixing that one bug? What then? No other bugfixes or features are introduced in the meantime? The likely case is (and this is from experience) that bug took some revisions to fix, in the meantime, Google were also pushing ahead with other fixes. Regardless to what the uneducated (about SW development), throwing 15 developers onto one problem doesn't solve it any quicker. 5.0.1 came, adn 5.0.2 came, then 5.1 came in the meantime. While that memory leak was being worked on, more releases come fixing other things. Be grateful they didn't listen to you and leave it at 5.0 for several months while they fixed one issue.
Whatever bluetooth fixes that you think are in 6.0.1 are pure fantasy, because none exist in AOSP 6.0.1: http://aosp.changelog.to/android-6.0.0_r5-to-android-6.0.1_r1.html <-- That's the FULL changelog of commits between 6.0.0_r5 and 6.0.1_r1.
It is not Google's job to fix a problem in anything other than their own devices. At all. Google's job is to make AOSP run smoothly on Nexus devices and release the source. Samsung, HTC, LG, Motorola et al all take the source code, just like CM, AICP, Slim and the rest do, and make modifications for their devices, using the sources given to them by their hardware partners and themselves. So if BT works in Nexus devices, but not others, then it's not Google's problem (usually). An AOSP issue will persist several devices, including Nexii devices.
Google also have taken on the quite large undertaking of monthly security updates for their devices, which I can tell you will be taking up some of the development teams time (it's what, 3-4 months into that project?).
No software ever released on this planet comes without bugs and issues. This is software development. You can check the status of AOSP development here: https://android-review.googlesource.com/#/q/status:open and feel free to download, code and submit your own features.
Click to expand...
Click to collapse
t
No new or useful information there. Thanks anyway, despite the ad hominem. I guess that comes with the territory (forums).
Yep, the Google-Android-(independent hardware makers) ecosystem is seriously flawed. Too much disconnect between the OS owner (Google), the hardware makers, the carriers, and the customer. And the first three in the chain (not including the customer) have different incentives/disincentives, and there are a bazillion hardware variations, of course it is broken. We know all this.
Reminds me of the original PC/Windows mess. Except worse because the carriers interpose an additional dysfunctional layer hindering OS updates/support. (Before anyone says "just DIY with one of the many available ROMs, I started this "Q" thread about stock MM, not third party ROMs.)
Still hoping for any useful information on anything happening to fix the MM defects, to get an idea when it might be past public beta and worth installing to MXPE.
TIA...

Tinkerer_ said:
t
No new or useful information there. Thanks anyway, despite the ad hominem. I guess that comes with the territory (forums).
Yep, the Google-Android-(independent hardware makers) ecosystem is seriously flawed. Too much disconnect between the OS owner (Google), the hardware makers, the carriers, and the customer. And the first three in the chain (not including the customer) have different incentives/disincentives, and there are a bazillion hardware variations, of course it is broken. We know all this.
Reminds me of the original PC/Windows mess. Except worse because the carriers interpose an additional dysfunctional layer hindering OS updates/support. (Before anyone says "just DIY with one of the many available ROMs, I started this "Q" thread about stock MM, not third party ROMs.)
Still hoping for any useful information on anything happening to fix the MM defects, to get an idea when it might be past public beta and worth installing to MXPE.
TIA...
Click to expand...
Click to collapse
What ad hominem? Your uneducated state affects your ability to understand the nature of Android and software development. It's a perfectly legitimate response to your position. You lack the ability to understand and therefore your argument is flawed. I'm not attacking you, I actually tried to give you some insight into how it works, but you're not really interested and would rather insist on this "public beta" bull.
As far as fixing any "defects" you suppose, you haven't actually listed any so no-one is going to be able to help you with temporary work around without a list of what you feel is broken. I also showed you the changelog, so you can do your own homework to see if your supposed defects are fixed in 6.0.1.
The various hardware configurations doesn't even matter because Android is built to deal with it. So long as the hardware vendors of chips and modules support them properly and give out functioning binaries to OEM's, or proper source code, it's irrelevant. The exact opposite of what you said is true, Google has a very close relationship with it's partners (anyone signed up to their Google programs, to preinstall Google apps). The problem is carriers, who really shouldn't have a say in software on the phones, but that seems to be a chiefly North American problem.
Google doesn't need to have any connection to Android users as customers. Google does not sell Android, therefore you are not Google's customer unless you use a Nexus phone. Google sell the Google Experience, with the Nexus. You are Motorola's customer, and you are using Motorola's branched version of Android. Google doesn't owe Motorola any fixes or patches for their device. Motorola must maintain their own device tree and maintain their own relationships with their partners.
EDIT:
Also, Motorola's problem is resources. They have four version of the Moto X 2015 to deal with, three versions of the Moto X 2014, the new X Force, then the various versions of the G and E to deal with, along with two smart watches, and so forth. Their line up is increasing whist I imagine their development team is not. There was outrage (rightly so) when news broke that the Moto G 2015 wasn't getting the MM update, despite being a couple of months old, and Motorola listened and OTA's are rolling out.

I am asking if anyone can offer any info on anything being done to move toward MM revision with the many significant defects of 6.0 corrected. Read the forums, there are way too many defects with 6.0, it is patently a de facto public alpha, and we are tracking the usual pattern where it takes 3 to 5 revisions before an OS major rev is ironed out enough that upgrading will not cause more problems than it fixes.
There are always excuses made for why there are so many defects in software. There is a euphemism for "defect" everybody uses, "bug". Everyone has been making excuses for so long about shoddy workmanship and inadequate testing and correction of software, with the "bug" euphemism to minimize the reality that these are defects, that we are all just to suppose to accept systems ridden with faults without complaint. It's unacceptable. It can be done better. Part of why it doesn't get better is because everybody says "that's just the way it is, deal with it". With mountains of byzantine excuses and even ad hominem attacks (as here).
This thread was not started to start a tit for tat ad hominem back and forth, nor to post long essays detailing excuses for the pathetic status quo of the fragmented Android ecosystem with respect to defect causes and distributions. It was started looking for any info about work being done to fix the stock MM defects. Still seeking info.
TIA.

You should probably check the definition of ad hominem. There was no attack on you as a person, just pointing out that your uneducated state with regards to knowledge about software development affects your ability to call judgement on this.
But you haven't listened to a single word I've said and still maintain a shoddy position, so I would suggest to anyone else who reads this to simply ignore you as a troll.

Tinkerer_ said:
It looks like Marshmallow is following the usual pattern of Android "x.0" alpha release to the public, followed by "x.0.1" beta release with initial defect ('bug") corrections starting with Nexus beta testers (I.e. Nexus users in general).
Reading about the MM 6.0 problems on MXPE, I'm sitting out the 6.0 alpha testing on the sideline with LP 5.1.1. Most trouble-free phone I've had yet, and I don't yet need the only compelling feature I see with MM on the MXPE (T-Mobile Band 12 support).
Any noises yet about MM beyond 6.0.1? (I know I can look for this elsewhere too, but thinking maybe some of the XDA community may have inside info from the Android community.)
TIA...
Click to expand...
Click to collapse
I think we'll close this debate. There are no real "Android" insiders on XDA, so asking for update info which is privy to Google is perhaps somewhat futile.
On a related note, XDA have a few dedicated "Android Fora", such as this complete Category where non-device specific discussion and indeed conjecture takes place. Perhaps you could take a look there and see what transpires?
Thanks

NVIDIA SHIELD Portable Software Upgrade 110

Just updated my NVIDIA SHIELD Portable to Software Upgrade 110.
Limited to Beta Testers.

akashkyh said:
Just updated my NVIDIA SHIELD Portable to Software Upgrade 110.
Limited to Beta Testers.
Click to expand...
Click to collapse
hi
i cant download it for some reason am currently on 106, is there any major changes or performance from 106
thanks

I got a download notification for this (and installed) after turning on the shield (it's been off for a month without any accounts logged in after upgrading to initial 5.1) and it isn't listed as beta anywhere.

eman2001 said:
hi
i cant download it for some reason am currently on 106, is there any major changes or performance from 106
thanks
Click to expand...
Click to collapse
So far I've only noticed Google Play services likes to crash unexpectedly for no reason whatsoever and couldn't open "search" without it quitting (even during updates). It's fine after its had time to do its thing with updates (after many crashes), not sure what the issue is/was. There's more lag on gamestream now than with older builds, probably going to move off NVidias specific implementation to something like Moonlight or Kainy. Haven't used any emulators yet, hopefully those aren't worse off.
It seems as we're getting pulled the "worse device with updates" crap like every other manufacturer out there.

Nvidia updates of the portable have made it worse each time. I will not buy another product like this from them. They need to stick to graphics cards since seen incompetent with Android devices.
Sent from my XT1575 using Tapatalk

will project treble successed

As seen here
https://www.reddit.com/r/LineageOS/...ect_trebel_devices/?utm_source=reddit-android
LineageOS team state that project treble is in its baby shoes and completely dependant on google to optimize it even more since as of now gsi rom requires certain adjustments for each device, so will project treble successed?
any1 has an insight please share.

I think it needs more adjustment. The kernel should be universal and updateable along with the OS, it's pretty universal as it is at the moment. Drivers should also be standard and updateable, at least for standard items. There should be a driver model where possible to support other devices, and any phone specific changes could be done through manufacturer supplied drivers. There's really no reason why it can't be done, it would be along the lines of how Windows works. Of course, it can be tailored to suit phones.
System updates should realistically come from Google, it would mean all phones and devices would be up to date with the latest security updates. The phone can also check with the manufacturer for specific updates. If Google keeps them apprised of any changes they can update their specific updates in time. This model would mean individual service testing for a new OS update etc wouldn't be a problem since it should at least be compliant with the base model.
Don't forget Google tracks down security leaks in other OS like Windows, which isn't even a direct competitor, and releases the security leak information if it isn't patched within 30? days. How many Android devices are updated with security patches within 30 days by the manufacturer? It's very much a double standard. Google really needs to think of an even more universal model like I just depicted for Android 10 Quinoa Slice (or whatever they call it).
Will Treble succeed? It's a step in the right direction, but needs more work. Not only should something like I just described be done, it should be made mandatory for all new devices. It doesn't mean custom versions are out, but custom versions would have to have OTA updates and be updated quickly along with the standard OS.

To say whether it succeeded or not, I think you'd first need to define what's its goal.
I still don't even know the answer as of today.
Some people say that the goal is to have a system image controlled and updated by Google.
But I don't see this happening any time soon. Google would need to test their GSIs on many devices, and they didn't even test P GSI over O-MR1 Pixels!
It seems to me that their goal was simply to make updates easier to OEMs. Considering Essential PH-1 getting Pie day-one, this might seem a success.
But we'll need to compare Oreo adoption rate to Pie's to confirm.

Oooh someone made a thread so i can moan cheers
The main problem with treble for me is that it's splintered between a plethora of devices, so one dev will release a treble rom and a multitude of device owners will flash it, each with their own subjective problems and issues, requests and wants.
And there lies the problem, it's difficult even when it's a dedicated rom thread for a particular device to get help at times.
So when you have a bunch of users talking about completely different devices you haven't got a hope in hell.
I think there should be branches to each thread for each specific device, that way help threads can be more linear rather than the chaos that it is at the moment.
Least that's my thoughts
My only rom i've flashed is RR and besides a few missing features, Fingerprint, Stereo and NFC i think it's brilliant.