All this is nice, but what does it really matter if Google can't figure out how to push out updates to Android devices in a reasonable manner and speed? The fragmentation level of Android is borderline absurd.
I don't think this is Google's problem. They make the whole platform open source to everyone including Smartphones companies which are to be blamed here. Targeting a Vanilla Android on a smartphone is much easier and faster than spending huge resources to build layers upon layers of custom UI and uninstallable bloat.
My next phone is probably going to be an iPhone. I've been with Android since the beginning, but the bugs, stability and lack of updates is going to force me with Apple. I litterally spent hundreds of hours getting my Nexus 4 and now LG G2 to the state where they are stable and working (with decent battery) while offering the services and options that they should have in the beginning.
I'm tired of rooting, installing several ROM's to find a stable one/one with good features, deleting system files, tweaking the build prop, installing Xposed (and all the nonsense with it), etc., just to get a stable system and long lasting system.
Not saying Apple is a million times better, but it's godamn easier to live with and gets timely updates. Even after searching through all the Kernels and ROM's, the latest stable one's for my LG G2 (a year and 8 months old flagship) is Lollipop 5.02, with 5.1 (forget about Android M) nowhere on the horizon. The Lollipop update (from 4.4.2, not 4.4.4 even) took over 6 months to arrive from Lollipop's release.
What's the advantage of a Nexus over an iPhone, they're both expensive and they both come in one flavor.
The whole idea of Android was to bring diversity to the market: lots of unique phones like the Yotaphone, lots of different form factors like sliders and even flip-phones. But without Google taking updating seriously, it pushes people away who actually care about security, updates, bug fixes, and enhanced features/improvements over time.
This is why iPhone continues to sell so well. The iPhone 4S is still supported, and contrary to popular belief, DOES RUN iOS 8.3 WELL.
So, this IS Google's problem, because they are in effect, acquiring less users through less devices sold, and at no time have more people been switching from Android to IOS than now. The iPhone 6 was proof of that. 61 million units sold in a month aren't coming from 61 million previous iPhone users. There were a hefty number of Android converts in there. And sure, many of them used Android because that was the only way to get a smartphone with a large screen (except for a few WinMo devices) but many people like myself left Android because the support was just crap.
Google relying on OEM's to keep devices updated and secure, in effect depending on them to hold the perception of quality to a high bar, is like Honda depending on Takata to keep their vehicles safe with quality airbags. In the end, who do you think the end-user is going to remember, Honda or Takata? This affects Honda's bottom line, just like Samsung having a bad rep for not supporting phones affects Google's bottom line.
Google needs to man up and deploy a universal update system that works around OEM customization. I don't see why an Android update or even an entire ROM can't be deployed on top of a Touchwiz ROM keeping the OEM tweaks in place.
From Google's POV, Android is nothing more than a delivery vehicle for Gapps, which is their true moneymaker. Google doesn't make or sell devices like Apple so as long as users can still grab the latest Gapps on whatever outdated Android version they can care less about fragmentation.
So agree! When Goog finally brought out ICS I got an HTC. No updates, unstable, worse GPU than the iPh3GS, but it was two years newer than the iPh4 I left. Despite this, it was supposedly as good as the iPh5.
And then I need to study rooting in a different language to install Goog's latest keyboard or whatever. This poor user experience is not worth the tweaks I can make in the user interface.
OEM's seem to be stepping up there update game. I was shocked to recieve a security update for a $39 LG. It's not possible for Google to update OEM'S os forks. Even though Samsung is 100% compadible with Googles original source code. The GUI and key API's are so heavily modified that its almost a total fork of the original OS. I agree that Google could implement a system that at least provided universal security updates but pushing out entire new roms is not possible with freedom it's given out to modify the operating system. It's a fundamental difference between open and closed source.
I have a nexus 4 but with android 5.1 update my 3g modem stops working. Also on nexus 5 my camera app causes the camera driver to crash and no other application can use it. Only restart fixes the problem for a while, and it is on 5.1.1. So nexus won't solve all your problems either. But I know people have some problems with their iPhones.
It does solve the timely updates issue tho, for the most part... I used to mod the heck out of the first three HTC phones I owned, just haven't felt the need with the N5. Still rooted it to unlock some power user functionality, but I like being able to get OTAs as they show up without tracking down kernels or worrying about what ROM is hot/current/stable.
I never had to jump through all those hoops, and I bought a dirt cheap ZTE phone. It runs fine for weeks before needing a restart, and has incredible battery life.
I think you've been trying too hard chap. I started off with all the custom room rooted crap with my Nexus 4. It all worked but it was a pain to just keep it all current. I decided to dump all that stuff and go back to stock/unrooted about 18 months ago.
Been so much easier and more reliable since. Not all of those guys creating ROMs in their bedrooms are necessarily doing the right thing or helping.
To counter your one-person anecdotal argument with my five-person anecdotal argument: I've had the Samsung Galaxy S2, Galaxy Nexus and LG G2 and all have worked well on stock images, only crashing when I used custom ROMs with experimental stuff. I've spent well under 100 hours on each phone and went through at most 3 ROMs per Android interation until I was satisfied. My wife owned a Chinese Galaxy S3 knock off that worked very well for the price and I only did one custom ROM (4.1 to 4.2) that worked well as well. Now she has another Chinese phone and is happy with the 4.4 Android with no need for anything else and a stable experience except for some weird video behaviour from MXPlayer that sometimes crashes. I've had 3 friends who owned iPhones 4 through 5 and had updates that destroyed performance, made the camera app crash very frequently and tanked battery life. They have looked at my ability to tweak my phone in awe, because they could not do anything to fix those issues except wait for Apple to release a new update or send their stuff in.
If you're restricted in your options, then it is easier to "live with" whatever you have (because you know you can't change it anyway). That's part of the appeal of Apple devices. Android is more of a "tinkerer's phone", for better and worse. Google needs to make the baseline/default system experience pleasant and then let the power users mess it up if they want (with ROMs and such). I feel the default has actually gotten pretty good on modern Android phones, but manufacturers keep aiming for differentiation through system level software differences. Would be nice if they did it more like Motorola. Another barrier for timely updates is, of course, the carriers. They request further changes and Google seems to lack the clout to fight those. Carriers continue to damage Android in that way.
"My next phone is probably going to be an iPhone."
The fragmentation issue is a little bit tricky. If someone is OK with sticking to the hardware from just one company (Apple) then she/he should not complain about Android fragmentation because sticking with one Android vendor (say, Samsung) resolves fragmentation issue completely. You will be getting Samsung version of Android and you will be getting timely updates (well, there is still wireless provider delay but still)
My Galaxy S4, my girlfriend's S3 and my friends S5 all run different major versions of Android, none of them current. Sticking with one Android vendor doesn't "fix" the fragmentation issues either.
Maybe the problem is the ROMs. Most third-party ROMs are not very stable. I personally like LG's OEM ROMs compared to Samsungs. I just root it and remove all the bloatware.
Your Nexus 4 got timely updates. My iPhone has far more stability issues than any Nexus devices I ever had.
None of the rooting and other BS you talk about was required with a Nexus device, so you chose to do that.
Apple's timely updates consistently make phones that are over a year and a half old so slow that you're forced to upgrade due to the pain - and there's no way that's just by chance.
All I hear is "I wanted options, but I didn't like having options, so I'm going to go with a vendor who locks the phone down so hard that I literally can't do anything to fix issues found in the base OS." The fact I can't control a notification volume separate from my ring volume on my iPhone is enough to make my head spin. And that's what you want? Just so you can get updates that more often than not slow the phone down and don't add any new functionality? *OK*
I have the LG G2 as well, it didn't take me that long to get it working nicely because I have stopped bothering with aftermarket roms. Stick with stock, use a bit of xposed (G2 Tweaksbox, don't use gravitybox), and then debloat. Mine's doing pretty well.
Same here. Previously I was running Cyanogenmod on a Samsung Skyrocket. On the LG G2 I'm running totally stock with most of the LG stuff disabled. I haven't seen a reason to go to a custom ROM.
Its your own fault for being a fusspot and you'll find the same issue in reverse in IOS land - if you're so fussy you want Xposed features, good luck customising IOS.
I had a G2 and it was fine out of the box. Waaah I got lollipop late - what key feature were you missing that actually detracted from your life?
Except that security has been blown up to such a huge deal when its not really a big deal... When was the last time you actually had been affected by by mobile security issues? I'll be honest in my experience.. NEVER. "Security" seems like such a buzzword these days when it was never something that impacted the majority of users. Sure if you are a high level target who may be targeted by malicious software or viruses then its a concern, but thats not the case with the majority of users.
@Chillin1248 My kid's got the Nexus 4. It's running the latest version of Lollipop, and the updates have been totally timely. We haven't encountered any instability. This of course is vanilla Android.
youre obviously doing something wrong then... the nexus4 (as with with all nexus phones) has vanilla android from the factory you shouldnt have to mess with Roms... if you jailbreak iOS and start adding features it will have the same issues. The G2 already has one of the highest rated battery life of all phones (higher than most of the iphone models) so once again i think you messing with the roms and installing rogue apps is the issue (which once again can happen with iphone if you jailbreak and install rogue apps)
i use an android phone (LG G3) and an ipad mini3 and i have no issues with both... i dont mess with roms, xposed, and i dont jailbreak so thats probably where you issues are
you cant cherry pick instances where you caused your phone to be more unstable and then blame android for it... its like add nitrous an aftermaket parts to you car and saying that the car is unstable and has bad gas mileage and blaming the car manufacturer.
It is Google's problem though because they allow it to happen, really Google needs to take stricter control over Android like Apple does. Now I don't mean insanely locking down Android like iOS is, simply that they need to require all manufacturers to use the vanilla Android ROM and the need to add a robust built in skinning support, so then the manufacturer customizations are separated from the OS itself and Android updates can be pushed out to all phones in a timely manner and manufacturers can update their skins as required. Also Google or the Manufactures need to outright ban carrier customization like Apple does as the carriers being in the process of updates makes it way worse.
Precisely -- this level of abstraction was already common in systems development 20+ years ago.
Apropos of nothing, it's nice to see that after Apple cribbed from Android for iOS 7 and 8 that Google is cribbing from Apple again (Google Pay and permissions). Turnabout is fair play!
This. I don't know why people say it's not Google's fault when it was Google's choice to make Android open source and therefore let Android turn into the mess that it is in. If Google had simply kept Android closed source and properly controlled the platform, it would be so much better.
It has nothing to do with the evils of open source (it's probably the preferred way for "younger" devs to work and even microsoft is jumping onto the open source train) and everything to do with the specifics of licensing. As others have said, they could have easily attached more requirements to use of the code as they have done with use of gapps.
Then it would be no different than Apple. There would be no high level customization short of "jailbreaking". Many manufactures would not agree to produce hardware to have the software match the competition. You can't simply say if Google kept Android closed things would be better... you wouldnt have the rich world of android we have today.
Sony and Motorola started doing things along these lines. They use an almost stock Android install, and push all their customisations into apps that can be installed (and upgraded) separately via the Play Store. They also push a lot of their changes back into the Android repos, and are very developer-friendly when it comes to the custom ROM scene.
It's just too bad their marketing departments are so lean. They have some great hardware that no one has heard of or is able to use outside of certain countries.
I don't see why it should be on Google's shoulders to force this approach, clearly there ARE OEMs adopting it regardless... And the masses aren't beating down their doors for a closer to stock experience, they just don't care.
For the rest of us, there are plenty of options without Google trying to meddle further with OEMs or killing the open source side of the equation, which has countless other side benefits.
Sony are still pushing their own services on the happy owners of devices like Xperia Z3 Compact, who are unable to uninstall them. Another example of bad function design is the button for the camera app. It is locked to Sony's camera app only -making it useless for a person who does not like that app. On top of that the camera app is integrated with Sony's own album app if I remember correctly, and not your own default album app.
What a load a bullshit. I have the Nexus 7 2013, and it took me 3 months after Lollipop came out before I got it. Nexus devices have been gotten updates slower than some non-Stock phones actually, which is totalt bullshit.
Seriously, as a Nexus 1 user who's flashed their phones to hell and back... WHO CARES IF YOU GET UPDATES A LITTLE BIT LATE. How exactly has your phone stopped working as soon as there's a newer update? Oh wait, its still working just fine....
Part of the "problem" is that Google does open betas of Android. If there's a new version of Android coming soon, you know about it and get a steady stream of reports from people using it. Thus you get a sense that it's "taking a long time" for the latest Android version to make it to your phone.
With iOS, until recently Apple kept all development releases private. So from the user's perspective they were using one version. Then suddenly one day there's a new version available. You don't feel like you're waiting for the new version if you don't know the new version is coming.
Anyway, the biggest problem is the phone carriers. Most of the phone manufacturers get the latest version of Android working on their newer phones within a month or two. It's the carriers (Verizon, AT&T, etc) who sometimes take a year or more before they've customized it to their taste and release it to customers. Apple strong-armed the carriers and refused to let them customize iOS. Google's open approach means the carriers can do what they want.
The real fix is to break the carriers' stranglehold on what phone you can use. If you could buy any phone which is technologically capable of running on a carrier's network, and the carrier was legally required to let you use it on their network, then we wouldn't have this problem. People would buy their phones off Amazon or eBay or whatever, and activate it on their carrier's network. Updates would then come straight from the phone's manufacturer, who usually get the latest version out immediately (they work with Google to test new versions) or within a month or two.
A phone needs to implement their drivers and things, so there's a bit of work to it. I actually have no idea how Android's driver model works, or what changes from release to release. It could be that things have calmed down a lot and it'll now be easier to update to newer versions on older devices.
I don't think Android has many class drivers, which would allow specific types of devices to run without needing their drivers explicitly installed. I could see that kind of thing being handy for cameras and touchscreens, but I have no idea what's supported globally today.
Thats why "Android One" project started. Android One phones has no modification, so that updates can directly be pushed to phone.
So if you want to get the latest updates, you have to get an Android One or a Nexus phone. Otherwise you have to wait for companies to update their "own sources", that they included modifcations and apps like Sense, Touchwiz etc.
Stop buying from the manufacturers who do that to you then. That's not Google's issue.
Why would you buy a phone you know won't get long term support if that is what is important to you? Buy Nexus or buy Motorolla. Don't tell me they're too expensive for you they both have options under $500 - half the price of iphone.
why do people like you say this. you really have no idea what your talking about. Google could do that, but doing so would take away what android is all about. but google gives you the option. buy a nexus device and you will get updates a reasonable speed. man your just ignorant as hell
Hopefully they can get the Dark theme working for more settings and apps. 1. I think it looks better. 2. I want all the power savings I can get on my OLED devices.
Should just be a matter of setting a global system flag, the app reading the flag, and employing an alternative color scheme. That's on the developer then. Alternatively, Google could redefine the palette space and shift it for the two themes, but that would risk unexpected or undesirable behavior in the apps.
It's already an option and has been for some time. I don't recall exactly when, but I know it's pre-Lollipop.
Developer Options > Device Hostname
If you don't have Developer Options enabled you need to tap a bunch on something in About, I think it was the build ID. Google it if you can't figure it out from random tapping.
Not sure why anyone wants the name "Muffin." It's supposed to be sweet-themed, and muffins are not always sweet (English muffins, cornbread muffins, etc). Marshmallow is more likely.
My hopes are that it will move back toward expandable storage to be more useful with Spiral 2/Project Ara.
Or Mars, or MilkyWay, or MilkDuds, or if they really want to earn neckbeard cred, MountainDew. Any are possible if they want to milk ad revenue like with KitKat.
That new permissions system sounds good, until you think about it a bit. It increases the effort on the part of the developer, they need to add more error handling for the cases where they don't have X permission and they need to target Android M, which means they'll need to support both permissions systems for a long while.
Something that requires more effort and isn't backwards compatible is going to take a long time to roll out.
I've been using AppOps in one form or another for a long time now. I haven't run into ANY issues with an app wanting to use a permission I've blocked. Literally none.
You know what you're doing tho, when Joe six pack starts clicking deny willy nilly and then starts dropping one star reviews because Skype can't make calls it'll be a different story...
I've used AppOps too in the past. This is a problem. There were some apps that crash or don't load if you block some permissions. One of them I remember was McDonalds app.
I hope they bring this permission blocking ASAP though. There are so many bogus permissions that the apps ask for these days. If they crash all the time because the lack of permission, it should be the developers problem. They shouldn't have included it in the first place.
Another change is in the Widgets screen, from a long-press on the home screen. They've re-organized it, similar to the app drawer. Scrolls vertically, and the widgets are separated based on the app they're associated with. Makes it much easier to find the widget you're looking for.
The clock's font looks like it is still Roboto, but they decreased the font size and increased the weight. They probably wanted to make it more legible against the new default background.
Been an Android user since I first bought a smartphone in 2010 (GS1). But all I'm hearing and seeing lately, and just have confirmed after I/O, is that Windows 10 Mobile is shaping up to becoming the next big thing in mobile. If things go right in the next year or two (and hopefully so), it's going to be one's best option for both a flagship and a budget device since both will be guaranteed to get updates. I also hope flagships will be launching with DX12 support.
iOS has never been an option for me since its crazy closed down. Android has been both a blessing and a curse. But W10 Mobile seems to have the least amount of compromises and best balance of openness and sandboxing. W10 Mobile supports everything that was announced in I/O and then some. The only couple of things it doesn't have over Android is side-loading, rooting, and crazy customization that you quickly get bored of. It also seems that both consumers and power Android users are moving away from the times of rooting, flashing, etc. Google's Nexus program is a JOKE in both device capability and availability.
I'm not an App freak, and I've been checking the Windows Store for apps and it mostly has what I need. The only thing left for Microsoft to do is make/buy a Youtube competitor for the sole purpose of forcing Google to submit into moving its entire ecosystem to Windows Universal.
I'm fed up with Google's "data-mining > user experience" approach, and what they're offering right now is too little, too late. I'm looking forward to a Wacom enabled Samsung Galaxy Note running Windows 10 Mobile that supports continuum.
"iOS has had a Do Not Disturb feature for years now, and it coexists perfectly with the ability to have a silent mode that blocks all alerts or vibrations."
Most alerts and vibrations, yes, but not the alarm (from the Clock app) – that plays at normal volume on the iPhone, even when it is in silent mode, and system volume is on "Mute". And isn't that the same as this Android "Alarms only" mode?
Btw -- in iOS, the alarm still sounds when DND is activated, and I suspect the same is true in Android (after all, it is common to activate DND overnight, and you still want to hear the alarm in the morning). The key advantages of DND over silencing the ringer and turning off vibrations are (a) it's faster to activate; (b) calls from your Favorite contacts will still come through (if desired); and (c) DND prevents the screen from lighting up with lockscreen notifications, which would disturb your sleep in a dark room.
That is an add choice. When a user sets an alarm, you would assume they want it to go off (no matter what); even if they choose not to be distracted by other notifications.
It could be a DND for other situations.. I know I'd love it for when I to the movies... so many times I hear and iPhone ring in the movies... or the sound of Siri activating haha.
"It may be best to think of Android M being to Lollipop what Jellybean was to Ice Cream Sandwich."
As long as we can get back to that Jelly Bean stability. Ice Cream Sandwich wasn't bad, but Jelly Bean, specifically the 4.2 and 4.3 era, was one of the best, most stable versions of Android, and it was kind of annoying to see KitKat with a slew of bugs, especially the camera wakelock one. Lollipop seemed to fix the camera bug, but introduced another crippling one, the memory leak bug, and still is a big mess in my opinion.
I mean, Jelly Bean was Android's peak in my opinion, and I'd like to get back to that. I'm not gong to lie, if I could get a phone with current gen hardware, but ran Jelly Bean 4.3, I would probably be just as happy as (or maybe even happier than) getting a new phone with Lollipop 5.1. If Android M could really do to Lollipop what Jelly Bean did to ICS, that would be awesome.
@metayoshi I have owned multiple android flagships over the years and yes JB 4.2 on my nexus 7 OG was the most fluidic i have ever felt on android , not even my G3 and OPO with 3 gb of ram come close .
It's somewhat amusing to me how Google keeps tinkering with things like the clock font and look/layout of the app drawer. While there's obviously nothing wrong with implementing good changes, I feel like even fundamentals of Android design are constantly under revision.
I fail to see why they had to go with such a halfassed solution which requires developer support for the permissions and it does not support disabling the really critical permissions like network access. Even App Ops and CyanogenMod provide much better solutions right now...
I'll say it outright - I'm not a fan of Lollipop. UI slowness is back and redraws happen all the time. It's not like I have an old phone. I'm running an S6 just a couple months after it's release.
ICS/Jellybean had a good interface for phones that didn't have 5+ inch screens. I don't see people using phones super-differently now than they were three years ago. It's twitter/snapchat, facebook, instawhatever, gmail, maps, a gps app, whatsapp, txt, and games.
What we need are phones that are FAST. Not fast phones that are slowed down by pretty animations. When I'm biking down the road, navigating traffic by foot or wheel and want to quick reply to something, change my destination or switch music tracks - I don't have time for slowness.. nor do I want it.
The focus on constantly updating the UI is just flat out wrong.
I have both the Nexus 4 and Nexus 7 (2012 model). The Nexus 4 gets new updates faster than the Nexus 7 by a good few weeks. Once it took a month for the 7 to get the update that the 4 already had. However once, the 7 got an update a week before the 4.
At the end of the day I get the updates on both devices and that's fine. My mates who have other brands mostly get stuck on some version or another. I'm slowly converting them all to Nexus, as it seems Google will keep sending me updates until my device no loger functions.
I can't see why many people get their knickers in a twist that they didn;t get an update the same day that it was released. I suppose it is just s symptom of the "wah wah, give me now wah wah" society that we now exist in.
And my unrooted, unmodified Nexus devices both work flawlessly so far.
.If anyone is looking for a steam email configuration on your device, So, you can read on Steam Customer Service and also can call us for more information. for more info:- https://emailsaccountrecovery.com/steam-account-re...
Yes, It can be. You just have to complete some Stap. Recover my Google account without my phone number. If you were experiencing issues with using your account, please contact our support department for assistance… https://emailsaccountrecovery.com/google-password-...
We’ve updated our terms. By continuing to use the site and/or by logging into your account, you agree to the Site’s updated Terms of Use and Privacy Policy.
88 Comments
Back to Article
Chillin1248 - Friday, May 29, 2015 - link
All this is nice, but what does it really matter if Google can't figure out how to push out updates to Android devices in a reasonable manner and speed? The fragmentation level of Android is borderline absurd.texasti89 - Friday, May 29, 2015 - link
I don't think this is Google's problem. They make the whole platform open source to everyone including Smartphones companies which are to be blamed here. Targeting a Vanilla Android on a smartphone is much easier and faster than spending huge resources to build layers upon layers of custom UI and uninstallable bloat.Chillin1248 - Friday, May 29, 2015 - link
My next phone is probably going to be an iPhone. I've been with Android since the beginning, but the bugs, stability and lack of updates is going to force me with Apple. I litterally spent hundreds of hours getting my Nexus 4 and now LG G2 to the state where they are stable and working (with decent battery) while offering the services and options that they should have in the beginning.I'm tired of rooting, installing several ROM's to find a stable one/one with good features, deleting system files, tweaking the build prop, installing Xposed (and all the nonsense with it), etc., just to get a stable system and long lasting system.
Not saying Apple is a million times better, but it's godamn easier to live with and gets timely updates. Even after searching through all the Kernels and ROM's, the latest stable one's for my LG G2 (a year and 8 months old flagship) is Lollipop 5.02, with 5.1 (forget about Android M) nowhere on the horizon. The Lollipop update (from 4.4.2, not 4.4.4 even) took over 6 months to arrive from Lollipop's release.
mr_tawan - Friday, May 29, 2015 - link
You can just go with the Nexus Devices.tarqsharq - Friday, May 29, 2015 - link
I second that.I love my Nexus 5.
Samus - Friday, May 29, 2015 - link
What's the advantage of a Nexus over an iPhone, they're both expensive and they both come in one flavor.The whole idea of Android was to bring diversity to the market: lots of unique phones like the Yotaphone, lots of different form factors like sliders and even flip-phones. But without Google taking updating seriously, it pushes people away who actually care about security, updates, bug fixes, and enhanced features/improvements over time.
This is why iPhone continues to sell so well. The iPhone 4S is still supported, and contrary to popular belief, DOES RUN iOS 8.3 WELL.
So, this IS Google's problem, because they are in effect, acquiring less users through less devices sold, and at no time have more people been switching from Android to IOS than now. The iPhone 6 was proof of that. 61 million units sold in a month aren't coming from 61 million previous iPhone users. There were a hefty number of Android converts in there. And sure, many of them used Android because that was the only way to get a smartphone with a large screen (except for a few WinMo devices) but many people like myself left Android because the support was just crap.
Google relying on OEM's to keep devices updated and secure, in effect depending on them to hold the perception of quality to a high bar, is like Honda depending on Takata to keep their vehicles safe with quality airbags. In the end, who do you think the end-user is going to remember, Honda or Takata? This affects Honda's bottom line, just like Samsung having a bad rep for not supporting phones affects Google's bottom line.
Google needs to man up and deploy a universal update system that works around OEM customization. I don't see why an Android update or even an entire ROM can't be deployed on top of a Touchwiz ROM keeping the OEM tweaks in place.
mkozakewich - Saturday, May 30, 2015 - link
The Nexus 5 isn't expensive.whiteiphoneproblems - Tuesday, June 2, 2015 - link
It's actually no longer even sold!StrangerGuy - Saturday, May 30, 2015 - link
From Google's POV, Android is nothing more than a delivery vehicle for Gapps, which is their true moneymaker. Google doesn't make or sell devices like Apple so as long as users can still grab the latest Gapps on whatever outdated Android version they can care less about fragmentation.Brakken - Saturday, May 30, 2015 - link
So agree! When Goog finally brought out ICS I got an HTC. No updates, unstable, worse GPU than the iPh3GS, but it was two years newer than the iPh4 I left. Despite this, it was supposedly as good as the iPh5.And then I need to study rooting in a different language to install Goog's latest keyboard or whatever. This poor user experience is not worth the tweaks I can make in the user interface.
patrioteagle07 - Friday, June 5, 2015 - link
*Contrary to user comments on their iphones...Jwraith15 - Monday, September 28, 2015 - link
OEM's seem to be stepping up there update game. I was shocked to recieve a security update for a $39 LG. It's not possible for Google to update OEM'S os forks. Even though Samsung is 100% compadible with Googles original source code. The GUI and key API's are so heavily modified that its almost a total fork of the original OS. I agree that Google could implement a system that at least provided universal security updates but pushing out entire new roms is not possible with freedom it's given out to modify the operating system. It's a fundamental difference between open and closed source.mmrezaie - Friday, May 29, 2015 - link
I have a nexus 4 but with android 5.1 update my 3g modem stops working. Also on nexus 5 my camera app causes the camera driver to crash and no other application can use it. Only restart fixes the problem for a while, and it is on 5.1.1. So nexus won't solve all your problems either. But I know people have some problems with their iPhones.Impulses - Friday, May 29, 2015 - link
It does solve the timely updates issue tho, for the most part... I used to mod the heck out of the first three HTC phones I owned, just haven't felt the need with the N5. Still rooted it to unlock some power user functionality, but I like being able to get OTAs as they show up without tracking down kernels or worrying about what ROM is hot/current/stable.Shadowmaster625 - Friday, May 29, 2015 - link
I never had to jump through all those hoops, and I bought a dirt cheap ZTE phone. It runs fine for weeks before needing a restart, and has incredible battery life.jabber - Friday, May 29, 2015 - link
I think you've been trying too hard chap. I started off with all the custom room rooted crap with my Nexus 4. It all worked but it was a pain to just keep it all current. I decided to dump all that stuff and go back to stock/unrooted about 18 months ago.Been so much easier and more reliable since. Not all of those guys creating ROMs in their bedrooms are necessarily doing the right thing or helping.
Death666Angel - Friday, May 29, 2015 - link
To counter your one-person anecdotal argument with my five-person anecdotal argument:I've had the Samsung Galaxy S2, Galaxy Nexus and LG G2 and all have worked well on stock images, only crashing when I used custom ROMs with experimental stuff. I've spent well under 100 hours on each phone and went through at most 3 ROMs per Android interation until I was satisfied. My wife owned a Chinese Galaxy S3 knock off that worked very well for the price and I only did one custom ROM (4.1 to 4.2) that worked well as well. Now she has another Chinese phone and is happy with the 4.4 Android with no need for anything else and a stable experience except for some weird video behaviour from MXPlayer that sometimes crashes. I've had 3 friends who owned iPhones 4 through 5 and had updates that destroyed performance, made the camera app crash very frequently and tanked battery life. They have looked at my ability to tweak my phone in awe, because they could not do anything to fix those issues except wait for Apple to release a new update or send their stuff in.
cgalyon - Friday, May 29, 2015 - link
If you're restricted in your options, then it is easier to "live with" whatever you have (because you know you can't change it anyway). That's part of the appeal of Apple devices. Android is more of a "tinkerer's phone", for better and worse. Google needs to make the baseline/default system experience pleasant and then let the power users mess it up if they want (with ROMs and such). I feel the default has actually gotten pretty good on modern Android phones, but manufacturers keep aiming for differentiation through system level software differences. Would be nice if they did it more like Motorola. Another barrier for timely updates is, of course, the carriers. They request further changes and Google seems to lack the clout to fight those. Carriers continue to damage Android in that way.haukionkannel - Friday, May 29, 2015 - link
Try windows phone. It will be cheaper and also support updates...lilo777 - Friday, May 29, 2015 - link
"My next phone is probably going to be an iPhone."The fragmentation issue is a little bit tricky. If someone is OK with sticking to the hardware from just one company (Apple) then she/he should not complain about Android fragmentation because sticking with one Android vendor (say, Samsung) resolves fragmentation issue completely. You will be getting Samsung version of Android and you will be getting timely updates (well, there is still wireless provider delay but still)
Gigaplex - Friday, May 29, 2015 - link
My Galaxy S4, my girlfriend's S3 and my friends S5 all run different major versions of Android, none of them current. Sticking with one Android vendor doesn't "fix" the fragmentation issues either.snajk138 - Sunday, May 31, 2015 - link
But what are the issues? Do they not run all the apps that you care about?hughlle - Friday, May 29, 2015 - link
I have an htc M7. I turned it on, it's worked just great ever since. Not sure why you have experienced so much grief.takhyon - Friday, May 29, 2015 - link
Maybe the problem is the ROMs. Most third-party ROMs are not very stable. I personally like LG's OEM ROMs compared to Samsungs. I just root it and remove all the bloatware.sfc - Friday, May 29, 2015 - link
Your Nexus 4 got timely updates. My iPhone has far more stability issues than any Nexus devices I ever had.None of the rooting and other BS you talk about was required with a Nexus device, so you chose to do that.
Apple's timely updates consistently make phones that are over a year and a half old so slow that you're forced to upgrade due to the pain - and there's no way that's just by chance.
All I hear is "I wanted options, but I didn't like having options, so I'm going to go with a vendor who locks the phone down so hard that I literally can't do anything to fix issues found in the base OS." The fact I can't control a notification volume separate from my ring volume on my iPhone is enough to make my head spin. And that's what you want? Just so you can get updates that more often than not slow the phone down and don't add any new functionality? *OK*
noone2 - Sunday, May 31, 2015 - link
Sounds like you're using your phone wrong.soccerballtux - Sunday, May 31, 2015 - link
I have the LG G2 as well, it didn't take me that long to get it working nicely because I have stopped bothering with aftermarket roms. Stick with stock, use a bit of xposed (G2 Tweaksbox, don't use gravitybox), and then debloat. Mine's doing pretty well.barleyguy - Tuesday, June 2, 2015 - link
Same here. Previously I was running Cyanogenmod on a Samsung Skyrocket. On the LG G2 I'm running totally stock with most of the LG stuff disabled. I haven't seen a reason to go to a custom ROM.wintermute000 - Sunday, May 31, 2015 - link
Its your own fault for being a fusspot and you'll find the same issue in reverse in IOS land - if you're so fussy you want Xposed features, good luck customising IOS.I had a G2 and it was fine out of the box. Waaah I got lollipop late - what key feature were you missing that actually detracted from your life?
Chillin1248 - Sunday, May 31, 2015 - link
It does matter very much when you take into account the security fixes and enhancements that came with Lollipop:https://source.android.com/devices/tech/security/e...
Murphs_Law - Tuesday, June 16, 2015 - link
Except that security has been blown up to such a huge deal when its not really a big deal... When was the last time you actually had been affected by by mobile security issues? I'll be honest in my experience.. NEVER."Security" seems like such a buzzword these days when it was never something that impacted the majority of users. Sure if you are a high level target who may be targeted by malicious software or viruses then its a concern, but thats not the case with the majority of users.
Gadgety - Sunday, May 31, 2015 - link
@Chillin1248 My kid's got the Nexus 4. It's running the latest version of Lollipop, and the updates have been totally timely. We haven't encountered any instability. This of course is vanilla Android.kpxgq - Sunday, May 31, 2015 - link
youre obviously doing something wrong then... the nexus4 (as with with all nexus phones) has vanilla android from the factory you shouldnt have to mess with Roms... if you jailbreak iOS and start adding features it will have the same issues. The G2 already has one of the highest rated battery life of all phones (higher than most of the iphone models) so once again i think you messing with the roms and installing rogue apps is the issue (which once again can happen with iphone if you jailbreak and install rogue apps)i use an android phone (LG G3) and an ipad mini3 and i have no issues with both... i dont mess with roms, xposed, and i dont jailbreak so thats probably where you issues are
you cant cherry pick instances where you caused your phone to be more unstable and then blame android for it... its like add nitrous an aftermaket parts to you car and saying that the car is unstable and has bad gas mileage and blaming the car manufacturer.
patrioteagle07 - Friday, June 5, 2015 - link
You should probably read this... http://www.nextpowerup.com/news/17955/my-first-tim...Aka, iphones are even more buggy and crash prone, they just cost more and are more liable to break.
Shizuma - Friday, May 29, 2015 - link
It is Google's problem though because they allow it to happen, really Google needs to take stricter control over Android like Apple does. Now I don't mean insanely locking down Android like iOS is, simply that they need to require all manufacturers to use the vanilla Android ROM and the need to add a robust built in skinning support, so then the manufacturer customizations are separated from the OS itself and Android updates can be pushed out to all phones in a timely manner and manufacturers can update their skins as required. Also Google or the Manufactures need to outright ban carrier customization like Apple does as the carriers being in the process of updates makes it way worse.johnnycanadian - Friday, May 29, 2015 - link
Precisely -- this level of abstraction was already common in systems development 20+ years ago.Apropos of nothing, it's nice to see that after Apple cribbed from Android for iOS 7 and 8 that Google is cribbing from Apple again (Google Pay and permissions). Turnabout is fair play!
mrochester - Friday, May 29, 2015 - link
This. I don't know why people say it's not Google's fault when it was Google's choice to make Android open source and therefore let Android turn into the mess that it is in. If Google had simply kept Android closed source and properly controlled the platform, it would be so much better.tuxRoller - Sunday, May 31, 2015 - link
It has nothing to do with the evils of open source (it's probably the preferred way for "younger" devs to work and even microsoft is jumping onto the open source train) and everything to do with the specifics of licensing. As others have said, they could have easily attached more requirements to use of the code as they have done with use of gapps.Murphs_Law - Tuesday, June 16, 2015 - link
Then it would be no different than Apple. There would be no high level customization short of "jailbreaking". Many manufactures would not agree to produce hardware to have the software match the competition. You can't simply say if Google kept Android closed things would be better... you wouldnt have the rich world of android we have today.phoenix_rizzen - Friday, May 29, 2015 - link
Sony and Motorola started doing things along these lines. They use an almost stock Android install, and push all their customisations into apps that can be installed (and upgraded) separately via the Play Store. They also push a lot of their changes back into the Android repos, and are very developer-friendly when it comes to the custom ROM scene.It's just too bad their marketing departments are so lean. They have some great hardware that no one has heard of or is able to use outside of certain countries.
Impulses - Friday, May 29, 2015 - link
I don't see why it should be on Google's shoulders to force this approach, clearly there ARE OEMs adopting it regardless... And the masses aren't beating down their doors for a closer to stock experience, they just don't care.For the rest of us, there are plenty of options without Google trying to meddle further with OEMs or killing the open source side of the equation, which has countless other side benefits.
superclementz - Sunday, May 31, 2015 - link
Sony are still pushing their own services on the happy owners of devices like Xperia Z3 Compact, who are unable to uninstall them. Another example of bad function design is the button for the camera app. It is locked to Sony's camera app only -making it useless for a person who does not like that app. On top of that the camera app is integrated with Sony's own album app if I remember correctly, and not your own default album app.generalako - Friday, May 29, 2015 - link
What a load a bullshit. I have the Nexus 7 2013, and it took me 3 months after Lollipop came out before I got it. Nexus devices have been gotten updates slower than some non-Stock phones actually, which is totalt bullshit.tuxRoller - Sunday, May 31, 2015 - link
But we got the 5.1 update very quickly.Your blanket statement needs support.
wintermute000 - Sunday, May 31, 2015 - link
Seriously, as a Nexus 1 user who's flashed their phones to hell and back... WHO CARES IF YOU GET UPDATES A LITTLE BIT LATE. How exactly has your phone stopped working as soon as there's a newer update? Oh wait, its still working just fine....Solandri - Sunday, May 31, 2015 - link
Part of the "problem" is that Google does open betas of Android. If there's a new version of Android coming soon, you know about it and get a steady stream of reports from people using it. Thus you get a sense that it's "taking a long time" for the latest Android version to make it to your phone.With iOS, until recently Apple kept all development releases private. So from the user's perspective they were using one version. Then suddenly one day there's a new version available. You don't feel like you're waiting for the new version if you don't know the new version is coming.
Anyway, the biggest problem is the phone carriers. Most of the phone manufacturers get the latest version of Android working on their newer phones within a month or two. It's the carriers (Verizon, AT&T, etc) who sometimes take a year or more before they've customized it to their taste and release it to customers. Apple strong-armed the carriers and refused to let them customize iOS. Google's open approach means the carriers can do what they want.
The real fix is to break the carriers' stranglehold on what phone you can use. If you could buy any phone which is technologically capable of running on a carrier's network, and the carrier was legally required to let you use it on their network, then we wouldn't have this problem. People would buy their phones off Amazon or eBay or whatever, and activate it on their carrier's network. Updates would then come straight from the phone's manufacturer, who usually get the latest version out immediately (they work with Google to test new versions) or within a month or two.
mkozakewich - Saturday, May 30, 2015 - link
A phone needs to implement their drivers and things, so there's a bit of work to it. I actually have no idea how Android's driver model works, or what changes from release to release. It could be that things have calmed down a lot and it'll now be easier to update to newer versions on older devices.I don't think Android has many class drivers, which would allow specific types of devices to run without needing their drivers explicitly installed. I could see that kind of thing being handy for cameras and touchscreens, but I have no idea what's supported globally today.
xmRipper - Friday, May 29, 2015 - link
Thats why "Android One" project started. Android One phones has no modification, so that updates can directly be pushed to phone.So if you want to get the latest updates, you have to get an Android One or a Nexus phone. Otherwise you have to wait for companies to update their "own sources", that they included modifcations and apps like Sense, Touchwiz etc.
blzd - Friday, May 29, 2015 - link
Stop buying from the manufacturers who do that to you then. That's not Google's issue.Why would you buy a phone you know won't get long term support if that is what is important to you? Buy Nexus or buy Motorolla. Don't tell me they're too expensive for you they both have options under $500 - half the price of iphone.
PitneFor - Saturday, May 30, 2015 - link
why do people like you say this. you really have no idea what your talking about. Google could do that, but doing so would take away what android is all about. but google gives you the option. buy a nexus device and you will get updates a reasonable speed. man your just ignorant as hellnathanddrews - Friday, May 29, 2015 - link
Hopefully they can get the Dark theme working for more settings and apps. 1. I think it looks better. 2. I want all the power savings I can get on my OLED devices.When are the new Windows 10 phones arriving?
hans_ober - Friday, May 29, 2015 - link
Would be nice if all apps automatically enabled a dark theme when the dark theme option is enabled in settings. Would really help OLED devices.cgalyon - Friday, May 29, 2015 - link
Should just be a matter of setting a global system flag, the app reading the flag, and employing an alternative color scheme. That's on the developer then. Alternatively, Google could redefine the palette space and shift it for the two themes, but that would risk unexpected or undesirable behavior in the apps.ntam - Friday, May 29, 2015 - link
Will be possible change the hostname? is very annoying the name android_1234567890abedfc,wolrah - Friday, May 29, 2015 - link
It's already an option and has been for some time. I don't recall exactly when, but I know it's pre-Lollipop.Developer Options > Device Hostname
If you don't have Developer Options enabled you need to tap a bunch on something in About, I think it was the build ID. Google it if you can't figure it out from random tapping.
CZroe - Friday, May 29, 2015 - link
Not sure why anyone wants the name "Muffin." It's supposed to be sweet-themed, and muffins are not always sweet (English muffins, cornbread muffins, etc). Marshmallow is more likely.My hopes are that it will move back toward expandable storage to be more useful with Spiral 2/Project Ara.
Curun - Friday, May 29, 2015 - link
Or Mars, or MilkyWay, or MilkDuds, or if they really want to earn neckbeard cred, MountainDew.Any are possible if they want to milk ad revenue like with KitKat.
biofrog - Tuesday, June 2, 2015 - link
I have no idea why anyone would think 'Muffin' either :)My best guess is Marzipan! Plus, "Android Marizpan" rolls off the tongue a lot easier.
Flunk - Friday, May 29, 2015 - link
That new permissions system sounds good, until you think about it a bit. It increases the effort on the part of the developer, they need to add more error handling for the cases where they don't have X permission and they need to target Android M, which means they'll need to support both permissions systems for a long while.Something that requires more effort and isn't backwards compatible is going to take a long time to roll out.
Gray05 - Friday, May 29, 2015 - link
I've been using AppOps in one form or another for a long time now. I haven't run into ANY issues with an app wanting to use a permission I've blocked. Literally none.Impulses - Friday, May 29, 2015 - link
You know what you're doing tho, when Joe six pack starts clicking deny willy nilly and then starts dropping one star reviews because Skype can't make calls it'll be a different story...hp79 - Monday, June 1, 2015 - link
I've used AppOps too in the past. This is a problem. There were some apps that crash or don't load if you block some permissions. One of them I remember was McDonalds app.I hope they bring this permission blocking ASAP though. There are so many bogus permissions that the apps ask for these days. If they crash all the time because the lack of permission, it should be the developers problem. They shouldn't have included it in the first place.
jabber - Friday, May 29, 2015 - link
Out of all of that, the only thing that appeals is the new App Permissions.Da W - Friday, May 29, 2015 - link
Can't wait for the new Microsoft's Windows 10 phone! Gonna throw my Android phone to trash!bloinkXP - Friday, May 29, 2015 - link
I wonder when someone is going to report of Android for Work...dshirtliff - Friday, May 29, 2015 - link
Another change is in the Widgets screen, from a long-press on the home screen. They've re-organized it, similar to the app drawer. Scrolls vertically, and the widgets are separated based on the app they're associated with. Makes it much easier to find the widget you're looking for.Significant - Friday, May 29, 2015 - link
Still no undo/redo editing?Also systemwide copy/paste of more than just text..
Timbrelaine - Friday, May 29, 2015 - link
The clock's font looks like it is still Roboto, but they decreased the font size and increased the weight. They probably wanted to make it more legible against the new default background.der - Friday, May 29, 2015 - link
YAAAAAAAAAAAAAASlilmoe - Friday, May 29, 2015 - link
Been an Android user since I first bought a smartphone in 2010 (GS1). But all I'm hearing and seeing lately, and just have confirmed after I/O, is that Windows 10 Mobile is shaping up to becoming the next big thing in mobile. If things go right in the next year or two (and hopefully so), it's going to be one's best option for both a flagship and a budget device since both will be guaranteed to get updates. I also hope flagships will be launching with DX12 support.iOS has never been an option for me since its crazy closed down. Android has been both a blessing and a curse. But W10 Mobile seems to have the least amount of compromises and best balance of openness and sandboxing. W10 Mobile supports everything that was announced in I/O and then some. The only couple of things it doesn't have over Android is side-loading, rooting, and crazy customization that you quickly get bored of. It also seems that both consumers and power Android users are moving away from the times of rooting, flashing, etc. Google's Nexus program is a JOKE in both device capability and availability.
I'm not an App freak, and I've been checking the Windows Store for apps and it mostly has what I need. The only thing left for Microsoft to do is make/buy a Youtube competitor for the sole purpose of forcing Google to submit into moving its entire ecosystem to Windows Universal.
I'm fed up with Google's "data-mining > user experience" approach, and what they're offering right now is too little, too late. I'm looking forward to a Wacom enabled Samsung Galaxy Note running Windows 10 Mobile that supports continuum.
whiteiphoneproblems - Friday, May 29, 2015 - link
"iOS has had a Do Not Disturb feature for years now, and it coexists perfectly with the ability to have a silent mode that blocks all alerts or vibrations."Most alerts and vibrations, yes, but not the alarm (from the Clock app) – that plays at normal volume on the iPhone, even when it is in silent mode, and system volume is on "Mute". And isn't that the same as this Android "Alarms only" mode?
whiteiphoneproblems - Friday, May 29, 2015 - link
Btw -- in iOS, the alarm still sounds when DND is activated, and I suspect the same is true in Android (after all, it is common to activate DND overnight, and you still want to hear the alarm in the morning). The key advantages of DND over silencing the ringer and turning off vibrations are (a) it's faster to activate; (b) calls from your Favorite contacts will still come through (if desired); and (c) DND prevents the screen from lighting up with lockscreen notifications, which would disturb your sleep in a dark room.blzd - Friday, May 29, 2015 - link
DND silences even Alarms on Android. Before 5.1 it even disabled the notification LED.whiteiphoneproblems - Monday, June 1, 2015 - link
That is an add choice. When a user sets an alarm, you would assume they want it to go off (no matter what); even if they choose not to be distracted by other notifications.Murphs_Law - Tuesday, June 16, 2015 - link
It could be a DND for other situations.. I know I'd love it for when I to the movies... so many times I hear and iPhone ring in the movies... or the sound of Siri activating haha.metayoshi - Friday, May 29, 2015 - link
"It may be best to think of Android M being to Lollipop what Jellybean was to Ice Cream Sandwich."As long as we can get back to that Jelly Bean stability. Ice Cream Sandwich wasn't bad, but Jelly Bean, specifically the 4.2 and 4.3 era, was one of the best, most stable versions of Android, and it was kind of annoying to see KitKat with a slew of bugs, especially the camera wakelock one. Lollipop seemed to fix the camera bug, but introduced another crippling one, the memory leak bug, and still is a big mess in my opinion.
I mean, Jelly Bean was Android's peak in my opinion, and I'd like to get back to that. I'm not gong to lie, if I could get a phone with current gen hardware, but ran Jelly Bean 4.3, I would probably be just as happy as (or maybe even happier than) getting a new phone with Lollipop 5.1. If Android M could really do to Lollipop what Jelly Bean did to ICS, that would be awesome.
sandy105 - Tuesday, June 2, 2015 - link
@metayoshiI have owned multiple android flagships over the years and yes JB 4.2 on my nexus 7 OG was the most fluidic i have ever felt on android , not even my G3 and OPO with 3 gb of ram come close .
whiteiphoneproblems - Friday, May 29, 2015 - link
It's somewhat amusing to me how Google keeps tinkering with things like the clock font and look/layout of the app drawer. While there's obviously nothing wrong with implementing good changes, I feel like even fundamentals of Android design are constantly under revision.Daniel Egger - Friday, May 29, 2015 - link
I fail to see why they had to go with such a halfassed solution which requires developer support for the permissions and it does not support disabling the really critical permissions like network access. Even App Ops and CyanogenMod provide much better solutions right now...enderscottcard - Friday, May 29, 2015 - link
I think the comments saying Android should be closed source are odd. If you want closed source there are other choices for you.As far as the name goes I think "Marshmallow" is a better choice than the other possibilities I've seen
der - Friday, May 29, 2015 - link
50th comment. y'all like that?coburn_c - Saturday, May 30, 2015 - link
My LG phone already has hover copy paste, proper volume control, customization, and a proper usb menu. Vanilla Android really is shit.sandy105 - Tuesday, June 2, 2015 - link
Second that , the g3 has a really good clipboard for copy pasting .Really nice and handy !relativityboy - Wednesday, June 3, 2015 - link
I'll say it outright - I'm not a fan of Lollipop. UI slowness is back and redraws happen all the time. It's not like I have an old phone. I'm running an S6 just a couple months after it's release.ICS/Jellybean had a good interface for phones that didn't have 5+ inch screens. I don't see people using phones super-differently now than they were three years ago. It's twitter/snapchat, facebook, instawhatever, gmail, maps, a gps app, whatsapp, txt, and games.
What we need are phones that are FAST. Not fast phones that are slowed down by pretty animations. When I'm biking down the road, navigating traffic by foot or wheel and want to quick reply to something, change my destination or switch music tracks - I don't have time for slowness.. nor do I want it.
The focus on constantly updating the UI is just flat out wrong.
robo bee - Saturday, June 6, 2015 - link
I have both the Nexus 4 and Nexus 7 (2012 model). The Nexus 4 gets new updates faster than the Nexus 7 by a good few weeks. Once it took a month for the 7 to get the update that the 4 already had. However once, the 7 got an update a week before the 4.At the end of the day I get the updates on both devices and that's fine. My mates who have other brands mostly get stuck on some version or another. I'm slowly converting them all to Nexus, as it seems Google will keep sending me updates until my device no loger functions.
I can't see why many people get their knickers in a twist that they didn;t get an update the same day that it was released. I suppose it is just s symptom of the "wah wah, give me now wah wah" society that we now exist in.
And my unrooted, unmodified Nexus devices both work flawlessly so far.
ameliaryan - Saturday, August 18, 2018 - link
It's just too bad their marketing departments are so lean,a look at the android, have any problem take help with https://www.gmailtechnicalsupportnumbers.com/forgo...mary224488 - Thursday, July 11, 2019 - link
.If anyone is looking for a steam email configuration on your device, So, you can read on Steam Customer Service and also can call us for more information. for more info:- https://emailsaccountrecovery.com/steam-account-re...tiara03255 - Thursday, August 1, 2019 - link
Yes, It can be. You just have to complete some Stap. Recover my Google account without my phone number. If you were experiencing issues with using your account, please contact our support department for assistance… https://emailsaccountrecovery.com/google-password-...