Mayhem
Android Expert
I thought y'all might enjoy.
Balky carriers and slow OEMs step aside: Google is defragging Android | Ars Technica
Balky carriers and slow OEMs step aside: Google is defragging Android | Ars Technica
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
An interesting read about Google Play Services
- Thread starter Mayhem
- Start date
This is good and all, but ever since they started pushing the Google Play Services my T-bolt has been a DOG. It seriously takes 2 minutes from the time I press a contact's number till the time I actually start hearing the ring and that doesn't account for actually locating and opening the contact. The phone was wiped after it got ICS.
I hardly use the "smart" features of the phone because they're so useless, it's turned into a phone and music player with occasional email tossed in.
I hardly use the "smart" features of the phone because they're so useless, it's turned into a phone and music player with occasional email tossed in.
A good decision by Google for the future of Android. And if I end up hearing fewer people whining about not having the latest version that makes it even better.
Thanks for the link.
SiempreTuna
Android Expert
Fascinating reading - two problems, though: first, Key Lime Pie's going to pretty dull but second - and way more important - what's the point me having a Nexus if there's no reason to boast about getting updates first 
zuben el genub
Extreme Android User
I do have a Nexus, but not to get updates first. Google, Windows, Apple, any form of Linux can't be everything to all people. If they could, we wouldn't tweak. If the majority want all the goodies, that's fine.
Once I get something working my way, I hate getting the apple cart upset.
I use the phone for other purposes, and would rather have the storage for all the apps I have with large databases.
I think that Google needs to separate out the services and let users choose whether or not they want to update. Some have limited data plans, others have wifi constraints. Some go prepaid to save money. Not everyone has, affords or wants unlimited everything. There is no hard and fast general rule for what an Android user is, and that is how it should be.
PS - looks like the new upgrade is Kit kat. Did Google get approval from Nestle? Or will we have another spate of copyright lawsuits?
Once I get something working my way, I hate getting the apple cart upset.
I use the phone for other purposes, and would rather have the storage for all the apps I have with large databases.
I think that Google needs to separate out the services and let users choose whether or not they want to update. Some have limited data plans, others have wifi constraints. Some go prepaid to save money. Not everyone has, affords or wants unlimited everything. There is no hard and fast general rule for what an Android user is, and that is how it should be.
PS - looks like the new upgrade is Kit kat. Did Google get approval from Nestle? Or will we have another spate of copyright lawsuits?
rabidhunter
Android Expert
Fascinating reading - two problems, though: first, Key Lime Pie's going to pretty dull but second - and way more important - what's the point me having a Nexus if there's no reason to boast about getting updates first
Of course, because KLP was a shell game. Just the new official name of the update alone is pretty exciting... Give me a break.
rabidhunter
Android Expert
Yup, a secret deal in which no money changed hands, but the reason it works and makes sense is... I want a friggen KitKat now!
Revenant Ghost
Android Expert
"Gimme a Break, Gimme a Break.
Break me off a piece of that new OS!"
Break me off a piece of that new OS!"
i don't think that OEMs should be allowed to block OS updates anyway.
you're just another programmer. you don't see titanium track blocking an android rollout because it breaks his app. no, he fixes the broken shit after the rollout and moves on. why are OEMs any different? you want your bloatware to run on my operating system? great! update it to work when i update my OS.
it'd be like adobe blocking windows updates because they don't work with Reader 11.2.3.33. no, that's not how that system works, i don't understand why google is allowing it to happen here.
you're just another programmer. you don't see titanium track blocking an android rollout because it breaks his app. no, he fixes the broken shit after the rollout and moves on. why are OEMs any different? you want your bloatware to run on my operating system? great! update it to work when i update my OS.
it'd be like adobe blocking windows updates because they don't work with Reader 11.2.3.33. no, that's not how that system works, i don't understand why google is allowing it to happen here.
The problem with this is that the skins are considered a "core" part of the OS on the phones that have them. Until or unless the skins are considered an optional part of the OS by the phone manufacturer this just won't be possible. Plus, the OS update would need to pass muster with the carriers, I think THAT is where much of the delays come from and I believe that the carriers wouldn't allow the update to pass without the skin since the phone would potentially lose some of its original functionality until the skin is updated.