Related
Hey there,
quick question, as i'm new to this, since this is my first android phone. so i've heard that 4.2.2 was released about a week ago. now apparently this update comes in waves, meaning that not everyone will get it at the same time. now i've got two questions about it, since i still haven't received this update:
- is this normal that you have to wait so long to get an update that's already available to a lot of people? (don't wanna do the framework trick)
- what is the purpose of that? please don't tell me, google couldn't handle the traffic when some people want to download this tiny update at the same time? oO
i'm just asking because im starting to worry if there's something wrong with my phone that makes it unable to receive system updates. i don't need the update that bad.
Yes. Don't worry.
I have a n4 ,n7 and n10. Framework worked for me 1st time with all the devices. Its very easy. Why not just do it???
rican408 said:
I have a n4 ,n7 and n10. Framework worked for me 1st time with all the devices. Its very easy. Why not just do it???
Click to expand...
Click to collapse
Because i've read that it messes up / resets settings of certain apps.
Worked fine for me.
Clearing Google services framework from the apps section definitely works.
I haven't gotten it either. Framework worked on N10 and gnex. I'm mainly not forcing it on N4 out of curiosity of how long it will take. Yes, I'm strange but not really needing update on N4. No reboots, no butter in the update, etc.
Sent from my Nexus 4 using Tapatalk 2
I haven't got it either. Is that related to the country or the batch of the phone you purchased?
Still havent got it either. I dont wanna force it with the framework data delete trick, the update is nothing interesting so id like to wait and see how long it would take to recieve the OTA.
Sent from my Nexus 4 using xda app-developers app
i know in canada, the updates go through service providers(if purchased from them) instead of google servers. maybe this is what is happening if you don't see the update yet?
melo_mx said:
i know in canada, the updates go through service providers(if purchased from them) instead of google servers. maybe this is what is happening if you don't see the update yet?
Click to expand...
Click to collapse
Is there a way to check this?
jb91 said:
Hey there,
quick question, as i'm new to this, since this is my first android phone. so i've heard that 4.2.2 was released about a week ago. now apparently this update comes in waves, meaning that not everyone will get it at the same time. now i've got two questions about it, since i still haven't received this update:
- is this normal that you have to wait so long to get an update that's already available to a lot of people? (don't wanna do the framework trick)
- what is the purpose of that? please don't tell me, google couldn't handle the traffic when some people want to download this tiny update at the same time? oO
i'm just asking because im starting to worry if there's something wrong with my phone that makes it unable to receive system updates. i don't need the update that bad.
Click to expand...
Click to collapse
So you have to torce update Kipling google framework,then update,reboot band you're ok
I ended up getting bored and sideloading it
No update for me yet either
Sent from my Nexus 4 using xda premium
ragnarok12 said:
No update for me yet either
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
No update for me either, but I don't mind it. Nothing major that I've read so far will force me to manually update my phone. If it doesn't come by Google I/O, then I'd worry, but by then KLP will probably be out.
facetubespam said:
No update for me either, but I don't mind it. Nothing major that I've read so far will force me to manually update my phone. If it doesn't come by Google I/O, then I'd worry, but by then KLP will probably be out.
Click to expand...
Click to collapse
The whole update cycle can take weeks before everyone has it.
gee2012 said:
The whole update cycle can take weeks before everyone has it.
Click to expand...
Click to collapse
This. People don't realize that updates are rolled out in batches.
Sent from my Nexus 4 using Tapatalk 2
joshnichols189 said:
This. People don't realize that updates are rolled out in batches.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Is there any reason for that? I still don't understand why they would do it this way.
jb91 said:
Is there any reason for that? I still don't understand why they would do it this way.
Click to expand...
Click to collapse
I'm curious about this too. Oddly, clearing the cache from my Google Framework didn't work. I'm curious to see if battery life gets ANY better with this update.
jb91 said:
Is there any reason for that? I still don't understand why they would do it this way.
Click to expand...
Click to collapse
They stagger the updates so their servers don't get overloaded with everyone trying to download the update at once. Microsoft does the same thing with Windows updates but they finish within a few days.
Canada here. My N7 took five days to get the OTA. It's been five days since the rollout began and still no OTA on my N4 yet.
This post is not really a cry for help. Just throwing this out here. I've been having problems with this error message ([RPC:S-5:AEC-0]) that I'm getting from the playstore for about almost a week now. I first experienced this after I saw quite a few update notifications on my phone. When I tapped on the update button, none of the apps updated and I got this error message instead, So I googled information on how I can fix it and found out the following
1. Clear data and/or cache on the following
- Downloads
- Google Play Store
- Google Service Framework
2. Remove and re-add google account from device
3. Factory reset
None of the methods above worked for me. I even tried accessing my paid apps from my pc by going to https://play.google.com/. Unfortunately, I also got an error message when I clicked on the "My Android Apps" link. Take note that I tried doing all these with different ISPs so issue is definitely not with my internet connection as well.
I've already contacted the google play support group and I was told that this issue has been going on and unresolved since October of 2012. The google techs are stummped and don't have the slightest idea of what's causing the problem. They can't even give me a time frame of when this will be resolved. They asked me to send bug reports from my devices which I did although I know for a fact that this problem is not being caused by any of my devices.
I'm pretty much stuck with a useless smart phone and tablet since I did a factory reset on both and I'm unable to redownload all of my apps including the ones that I have purchased...
I attached a few screenshots from my N7000 and Nexus 7 and my PC as well showing the errors.
This is how google wants to solve my issue... BY RIPPING ME OFF!!!
On Mon, Jun 10, 2013 at 11:20 PM, <[email protected]> wrote:
Hi Manolo,
Thank you for contacting Google and keeping us updated on your situation while experiencing the error RPC:S-5:AEC-0. As we discussed over the phone the only option left to do regarding your current account is to wait. [B]however I was informed that you can try by passing this by creating a new account and I apologize for information that I had provided you over the phone as that was incorrect knowledge. This does appear to also be an account base problem. Please keep in mind that paid apps are non transferable.[/B]Here is the link to check out that will be keeping update on the progress of the RPC:S-5:AEC-0 error.
http://support.google.com/googleplay/bin/static.py?&page=known_issues.cs&ki_topic=1319135
If you could let me know if creating a new gmail account works that knowledge will be greatly appreciated. Please let me know if you continue to have questions at any time.
Thanks and have a great day,
Devan
The Google Play Team
Have you changed any account settings lately on Google.
Go to play.google.com and login. From top right corner click on my order & settings and check the details.
#Galaxtus - Over and Out
Galaxtus said:
Have you changed any account settings lately on Google.
Go to play.google.com and login. From top right corner click on my order & settings and check the details.
#Galaxtus - Over and Out
Click to expand...
Click to collapse
I haven't. I just checked. Nothing irregular with the details.
Did you tried to uninstall/install some free app? Can you install new app?
...from SG NOTE N7000 with Tapatalk 2
zviki said:
Did you tried to uninstall/install some free app? Can you install new app?
...from SG NOTE N7000 with Tapatalk 2
Click to expand...
Click to collapse
Reread the op
Sent from my GT-N7000 using Tapatalk 2
Perhaps flashing a new firmware might help as this changes the android id?
Sent from my GT-N7000 using xda premium
kishd said:
Perhaps flashing a new firmware might help as this changes the android id?
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Nope. It's a known issue that has blown up over the last few weeks.
This is the most active thread on xda I can locate, up to 10 pages and growing fast.
A thread started on Google Plus today about it as well. Happening across all devices and ROMs to a significant number of users.
hgoldner said:
Nope. It's a known issue that has blown up over the last few weeks.
This is the most active thread on xda I can locate, up to 10 pages and growing fast.
A thread started on Google Plus today about it as well. Happening across all devices and ROMs to a significant number of users.
Click to expand...
Click to collapse
Just talked to one of the google techs again today. This is really getting out of hand crazy! They have sent me numerous emails asking me to do the same thing over and over. It's like they don't even check on previous documentation that I have responded to telling them that none of the trouble shooting they told me to do worked. To top it all off, we started discussing about refunds. I was told that thier policy is they can only do the last 6 months. I have so many paid applications that I have accumulated for the last year and a half! A lot of the ones I use the most have been purchased more than 6 months ago, Then she tells me that I'd have to talk to the individual 3rd party developers and ask them for a refund. I mean, why would a developer refund me if it's not even thier fault that this issue is happening. This is all google!
Did you tried it on another android phone with your login id
#Galaxtus - Over and Out
Galaxtus said:
Did you tried it on another android phone with your login id
#Galaxtus - Over and Out
Click to expand...
Click to collapse
Note, S3, Nexus 7 and my desktop PC. I've done it all sir. Nothing else you can say would be any different from the ones that I've already read from all the forums. This is an issue from google's side affecting several accounts.
l0rd_almighty said:
Note, S3, Nexus 7 and my desktop PC. I've done it all sir. Nothing else you can say would be any different from the ones that I've already read from all the forums. This is an issue from google's side affecting several accounts.
Click to expand...
Click to collapse
In the same boat across multiple devices and very frustrated. Hopefully this is becoming a very widespread issue and will get more attention with Google's higher level techs and developers.
I was having this issue, and all the normal steps didn't help. I called Google, they were no help, other than to say it was a known issue. I tried removing my Google account, and clearing the cache/data for Google Service Framework and Play Store apps - nothing worked
Then I tried clearing the cache/data on Google Play Services, on the off chance that this might be the culprit and after a reboot everything is working great again.
Hope this will help some of the other folks who are struggling with this.
Exact Steps:
1) Open Settings->Apps
2) Select Google Play Store
3) Clear Cache and Force Stop
4) Select Google Framework Services
5) Clear Data and Force Stop
6) Select Google Play Services
7) Clear Data and Force Stop
8) Reboot
Why are you ****ting On Us Google?
On another forum, a poster had this to say about this RPC:S-5:AEC-0 problem:
I don't believe this has anything to do with what is running on the device...whether its 4.2.2 or 4.1.2. It's simply an issue with corruption in the Google Play account on Google's servers. The lack of any fix for this or a workaround is abysmal on Google's part. I have paid apps that will no longer run because Google Play no longer recognizes them as paid apps. I have wasted numerous hours trying to get this resolved with escalated calls to Google support. Basically, anyone who is affected by this account "corruption" issue is currently screwed with no fix in sight. This needs to get major media attention or possible class action status before Google gets serious and fixes this acknowledged issue they've known about for several months now.
​
That is a good summary of the issue.
Google knows all about this.
It's endemic and the worst part about it is that Google is ignoring it.
There has been one simple post by Google -- in March -- saying they were working on the problem, and then a one-line addendum in April to say that they were still working on the problem.
THIS IS NOT ONLY ABSURD, BUT UNACCEPTABLE.
I've tried every effing solution that's been posted -- and none works.
I'm sick to the back teeth about the crap that GOOGLE thinks I can take. I'm just steaming mad.
The sheer inconvenience and time-wasting is mind numbing.
Am I pissed off at Google. You betcha.
Do I scream at Google, What do you think!
How can Google sit back and do nothing about this for months. (And don't point me to the lame suggestions of a work around like: Clear the cache in the Play Store app; clear the data in the Google Services framework; delete and reinstall the offending account .... etc etc etc. I've tried every one and more. Even tried deleting the whole OS and reinstalling,; tried factory reset.
THIS IS CRAP AND GOOGLE KNOWS IT.
Setting up a new gmail account is not practicable as the Google user base has a huge investment in their Play Store account by way of the money they've paid to Google for apps which Google is fraudulently now stopping them from using.
The problem appears to be tied to the link between the kernel and the play store account. If a user starts a whole new account, then there is no problem for that new account. However, for Android's database of users, this is not a practicable solution as that base of users has an investment in their Play Store account -- not the least of which is in the value of the apps that they have paid for to date.
MY QUESTION IS: WHY ARE YOU ****TING ON US - YOUR LOYAL USERS - GOOGLE?
Another question: How do we escalate this into main stream media so that Google has to get off their fat arse and fix the proble? Any ideas would be helpful.
Looks like google finally fixed the issue. My apps finally started updating today with no errors.
l0rd_almighty said:
Looks like google finally fixed the issue. My apps finally started updating today with no errors.
Click to expand...
Click to collapse
Congrats buddy. Hope finally you found all your answers. Anyways try to backup your apps with TB once updated, just in case
l0rd_almighty said:
Looks like google finally fixed the issue. My apps finally started updating today with no errors.
Click to expand...
Click to collapse
+1
This is NOT a time to pat Google on the back
Last night, shortly after posting my rant on this forum, I went to the app store to see if I could get some sense out of the bloody thing. Lo and Behold! It was all go!!!!
Now while I like to think -- in my hedonostoc idle moments -- that it was my posting on this forum that did the trick, reality tells me that Google had been working on this for some time and that the fix was in place coincidentally at approximately 10pm NZ time yesterday (12th June 2013).
Why am I being so pedantic about the time.
Simple.
Google, quite clearly, must have been working on this for some time in order for the fix to be put in place at that precise moment. The problem with this conduct though, is that they did NOT at any time inform its constituency that it had even acknowledged that there was this effing problem in the first place. A lot of good people have been mystified, frustrated, angry, confused and suspicious by this smorgasbord of crap that Google has dished up and even felt that they had no option but to eat the **** sandwich presented to them.
SO, if Google thinks that this lowly serf is going to thank them for getting rid of the RPC:S-5:AEC-0 bug, then they need to take their heads out of the arses and smell the real world, 'cos it aint going to happen.
At the very least I would expect Google to make some gesture to its user base to placate them after the harrowing ordeal that their incompetence has put them through.
Enough said.
Unless or until this rears its ugly head again.
martin1952 said:
Last night, shortly after posting my rant on this forum, I went to the app store to see if I could get some sense out of the bloody thing. Lo and Behold! It was all go!!!!
Now while I like to think -- in my hedonostoc idle moments -- that it was my posting on this forum that did the trick, reality tells me that Google had been working on this for some time and that the fix was in place coincidentally at approximately 10pm NZ time yesterday (12th June 2013).
Why am I being so pedantic about the time.
Simple.
Google, quite clearly, must have been working on this for some time in order for the fix to be put in place at that precise moment. The problem with this conduct though, is that they did NOT at any time inform its constituency that it had even acknowledged that there was this effing problem in the first place. A lot of good people have been mystified, frustrated, angry, confused and suspicious by this smorgasbord of crap that Google has dished up and even felt that they had no option but to eat the **** sandwich presented to them.
SO, if Google thinks that this lowly serf is going to thank them for getting rid of the RPC:S-5:AEC-0 bug, then they need to take their heads out of the arses and smell the real world, 'cos it aint going to happen.
At the very least I would expect Google to make some gesture to its user base to placate them after the harrowing ordeal that their incompetence has put them through.
Enough said.
Unless or until this rears its ugly head again.
Click to expand...
Click to collapse
Very well said!
Sent from my GT-N7000 using Tapatalk 4 Beta
abhinav quietly brilliant said:
Reread the op
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Why? I'm talking about new app not existed one,but I should write install/uninstall(not uninstall/install). It's not important anymore if the others have the same problem...
P.S. ...and it's solved...
...from SG NOTE N7000 with Tapatalk 2
Hi Everyone,
As I do with many Nexus devices, I intend to maintain a thread here with links to all the stock OTA updates for the HTC One Google Play Edition. Each time there is an OTA update, its direct link on Google's servers will be posted here for reference and posterity. I also mirror these files at http://www.randomphantasmagoria.com/htc-one/m7_google.
Any questions about flashing these OTA updates can be discussed and answered here as well.
You must have S-OFF on your bootloader in order to flash OTAs manually on a GPE One.
----------------------------------------------------
Current firmware (m7_google): Android 5.1, Build LMY47O.H9
LMY47O.H10 from LMY47O.H9 - https://android.googleapis.com/pack....10-6.04.1700.9_LMY47O.H10_release_453155.zip
-----------------------------------------------------
LMY47O.H9 from LMY47O.H6 - https://android.googleapis.com/pack..._10.33R.1718.01L_LMY47O.H9_release_449435.zip
-----------------------------------------------------
LMY47O.H6 from LRX22C - http://android.clients.google.com/p...00.6-5.11.1700.3_LMY47O.H6_release_430567.zip
-----------------------------------------------------
LRX22C from KTU84P - http://android.clients.google.com/p...00.3-4.09.1700.1_LRX22C.H3_release_403340.zip
-----------------------------------------------------
KTU84P from KTU84L - http://android.clients.google.com/p...00.1-4.07.1700.4_KTU84P.H1_release_381467.zip
-----------------------------------------------------
KTU84L from KOT49H - http://android.clients.google.com/p...00.4-3.62.1700.1_KTU84L.H4_release_377648.zip
-----------------------------------------------------
KOT49H from KRT16S - http://android.clients.google.com/p...WE_3.62.1700.1-3.58.1700.5_release_343526.zip
-----------------------------------------------------
KRT16S from JWR66Y - http://android.clients.google.com/p...WE_3.58.1700.5-3.07.1700.1_release_341696.zip
-----------------------------------------------------
JWR66Y from JDQ39 - http://android.clients.google.com/p...3.07.1700.1-2.14.1700.15_R_release_332395.zip
JWR66Y from JWR66V - http://android.clients.google.com/p...E_3.07.1700.1-3.06.1700.10_release_332016.zip
-----------------------------------------------------
JWR66V from JDQ39 - http://android.clients.google.com/p....06.1700.10-2.14.1700.15_R_release_330258.zip
SPECIAL THANKS
EthanFirst
saturn_de
madasahat
jasalta387
This space for sale, rent, or lease.
Considering that HTC has delivered the GPE KitKat update to Google for release, it's logical to expect it to begin rolling out this week or next. If anyone gets the OTA update, please get the filename of the OTA ZIP before applying it. You can find it in your /cache folder if you're rooted. If you're not rooted, the process is a bit more involved. PM me for details.
Thanks!
Both links send you to a 404 error page.
NJGSII said:
Both links send you to a 404 error page.
Click to expand...
Click to collapse
DOH! Stupid typos. My bad. I fixed it. Thanks for pointing it out.
Thanks to XDA forum member @EthanFirst, we now have the link to the direct OTA update for JDQ39 to JWR66Y. Thank you!
Thank for create forum. :good:
How to get the OTA URLs
The easiest way to get the OTA URLs is to search in the output of:
Code:
adb shell dumpsys dropbox --print event_log
On Linux this can be done with "grep":
Code:
adb shell dumpsys dropbox --print event_log | grep android.clients.google.com
This can be done even after the update.
Wonder if tomorrow will vebthe day now that n4 and other nexus devices have gotten full access to otas. And moto x devices are starting to get it.
sent from my gpe HTC one
monkeypaws said:
Wonder if tomorrow will vebthe day now that n4 and other nexus devices have gotten full access to otas. And moto x devices are starting to get it.
sent from my gpe HTC one
Click to expand...
Click to collapse
I guess we'll find out! If anyone gets the OTA, please make sure to post the filename so I can list it in the OP and mirror it on the website!
Sent from my Xoom using Tapatalk 4
I did the GPe conversion to my phone and got an OTA message only to realize it was another 4.3 update. I hope today is the day. I really hope Google isn't sitting on it until Samsung gets the S4 GPe update to them.
Sent from my HTC One using XDA Premium 4 mobile app
RobBull69 said:
I did the GPe conversion to my phone and got an OTA message only to realize it was another 4.3 update. I hope today is the day. I really hope Google isn't sitting on it until Samsung gets the S4 GPe update to them.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I really am sad to this GPe stuff, the idea is great, but something always fails: if isn't a delay by HTC, it's a delay from Google and we stay watching damn Motorola getting updates...
I thought that it would come after N4 OTA (wich sucks but I can understand), now it seems like we are waiting for Samsung update, probably the delays are just Google marketing at work...
15 days is pretty good for deliverance but first time we prayed for 15 days, now we pray for 15 work days...
My opinion? We are not getting 4.4 update before December. Now I know why my previous phones were nexus and my next probably will be too...
RobBull69 said:
I did the GPe conversion to my phone and got an OTA message only to realize it was another 4.3 update. I hope today is the day. I really hope Google isn't sitting on it until Samsung gets the S4 GPe update to them.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Well seeing as Motorola is Google I can see why they would get it faster...
Sent from my HTC One using xda app-developers app
eng.stk said:
I really am sad to this GPe stuff, the idea is great, but something always fails: if isn't a delay by HTC, it's a delay from Google and we stay watching damn Motorola getting updates...
I thought that it would come after N4 OTA (wich sucks but I can understand), now it seems like we are waiting for Samsung update, probably the delays are just Google marketing at work...
15 days is pretty good for deliverance but first time we prayed for 15 days, now we pray for 15 work days...
My opinion? We are not getting 4.4 update before December. Now I know why my previous phones were nexus and my next probably will be too...
Click to expand...
Click to collapse
The GPE updates aren't scheduled together. The HTC One GPE got JWR66Y almost a week before the GS4 did. Also, it appears there were some problems with those initial KitKat builds. I'm sure that has something to do with the delays. For me, 3 weeks after a full Nexus rollout is acceptable. A full Nexus rollout did not start until about 3 days ago. KRT16O only launched for N7 and N10 wifi models, and was quickly pulled. KRT16S started about 3 days ago and THAT is the one that is seeing rollout to the complete Nexus line. So, as far as I'm concerned, my 3 week counter began 3 days ago.
Sent from my Nexus 7 using Tapatalk 4
oldblue910 said:
The GPE updates aren't scheduled together. The HTC One GPE got JWR66Y almost a week before the GS4 did. Also, it appears there were some problems with those initial KitKat builds. I'm sure that has something to do with the delays. For me, 3 weeks after a full Nexus rollout is acceptable. A full Nexus rollout did not start until about 3 days ago. KRT16O only launched for N7 and N10 wifi models, and was quickly pulled. KRT16S started about 3 days ago and THAT is the one that is seeing rollout to the complete Nexus line. So, as far as I'm concerned, my 3 week counter began 3 days ago.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
HTC is still claiming that the timing is up to Google, at least on their Twitter. https://twitter.com/HTCUSA/status/403666789080375296
They have made no indications that they need to use a new build or re-deliver code to Google.
dipdewdog said:
HTC is still claiming that the timing is up to Google, at least on their Twitter. https://twitter.com/HTCUSA/status/403666789080375296
They have made no indications that they need to use a new build or re-deliver code to Google.
Click to expand...
Click to collapse
Just because they didn't communicate it doesn't mean it isn't going to happen. We'll see.
dipdewdog said:
HTC is still claiming that the timing is up to Google, at least on their Twitter. https://twitter.com/HTCUSA/status/403666789080375296
They have made no indications that they need to use a new build or re-deliver code to Google.
Click to expand...
Click to collapse
I wish they never would have made a deadline promise. they never should have updated us that they sent the code to Google. samsung isnt doing this. how do we know they havent sent their code to Google as well. there has never been a need in the past to tell consumers this info.
CraigP17 said:
I wish they never would have made a deadline promise. they never should have updated us that they sent the code to Google. samsung isnt doing this. how do we know they havent sent their code to Google as well. there has never been a need in the past to tell consumers this info.
Click to expand...
Click to collapse
Agreed 100%. We really don't need to know.
oldblue910 said:
Agreed 100%. We really don't need to know.
Click to expand...
Click to collapse
Communication is always good as long the info provided holds its truth.
Sent from my HTC One using Tapatalk
I have a Nexus 4 and a Nexus 7 beside my HTC One GPE. None of those got an OTA update yet to KitKat. So please stop whining and blaming HTC for a "delay". There is no delay. The roll-out is just slow like always with Android.....
Many phones are recieving the update v5 of google play material design.
Wonder why didn't we got it!!
Anybody here who recieved it already?
Sent from my XT1068 using XDA Free mobile app
No bro same here ?, I don't know why.....
rahilsayed said:
Many phones are recieving the update v5 of google play material design.
Wonder why didn't we got it!!
Anybody here who recieved it already?
Sent from my XT1068 using XDA Free mobile app
Click to expand...
Click to collapse
You can update manually.
http://www.apkmirror.com/apk/google-inc/google-play-store/google-play-store-5-0-31-apk/
Try this
Just download the apk lol.
I have a friend with oneplus one and n5 and he didn't receive it either, so it doesn't mean anything
Google for most of their apps (esp Play Services and Play Store) roll out updates in stages usually over a week or two, you just get it when you do, I don't have it on any of my devices yet but it will come.
Like others have said you can manually update with the apk if you want it faster.
Thanks friends for replies......and i must say that our community has reach way far than any phone in a month.
I have seen S3,Sony SL communities but they never grew this big as our yet in short time .:thumbup::thumbup::thumbup:
Sent from my XT1068 using XDA Free mobile app
Just received update 2 days before
Not a big deal though
Just wanted to tell you
I've just had mine update not 10 minutes ago, looks very good the material design makes me want Android L even more now
My brother's SAMSUNG GALAXY GRAND DUOS (GT-I9082) rooted running on LiquidSmooth v 3.2 just got it few hours ago. May be he got it due to PA GAPPS!
And I'm still waiting for it! Haha
2 days ago I already got that update.
vikasb32 said:
2 days ago I already got that update.
Click to expand...
Click to collapse
I got it last night. Must say not quite impressed. Minor UI changes & nothing else. So all those who have not received it yet, you ain't missing much guys. :good:
Miner UI changes. But its awesome.
And i feel now its double fast too.
I got an update today on 5.0.31 ....
Update manually
I found a way to update manually without having to download any apk file. You can do it right from Google Play Store. Here is how:
-Open Play Store
-Press the menu button (top left of the screen, 3 horizontal lines)
-Select "Settings"
-Scroll down and under "About" you should see "Build version". Press it and it should say that "Google is going to download a new version of Play Store and update it" or something similar
-Wait a few minutes
That's it. You should have the latest version of Play Store now.
I was just about to check, but then realised, it's already v5.0.31 :good:
I just got the update, not much but good ui
me too checked today and it was updated
I am on v5.0.32 due to force update through normal apk installation.
Sent from my XT1068 using XDA Free mobile app
rahilsayed said:
I am on v5.0.32 due to force update through normal apk installation.
Sent from my XT1068 using XDA Free mobile app
Click to expand...
Click to collapse
I am on v5.0.31[emoji46] and 32 got out?
Is anyone having trouble getting this OTA? I had 1-4 available right away, but I've been checking for an update since yesterday and nothing.
Sent from my Nexus 6P using XDA-Developers mobile app
Same for my Nexus 6p. All of the prior DP OTAs were very quick, but I'm waiting for the DP5 OTA .
Sent from my Nexus 6P using XDA-Developers mobile app
Just wait and it will arrive, if you can't wait then sideload... simple.
Same boat, really wack.
Yea. It's annoying
Sent from my Nexus 6P using XDA-Developers mobile app
Don't side load from what I read it hasn't come for the 6p yet because of some issues that are being worked out. I haven't checked to see if they pulled the images but I would just wait for the OTA. I also read that dp5 is really laggy on the Nexus 6
mojorisin7178 said:
Don't side load from what I read it hasn't come for the 6p yet because of some issues that are being worked out. I haven't checked to see if they pulled the images but I would just wait for the OTA. I also read that dp5 is really laggy on the Nexus 6
Click to expand...
Click to collapse
Can you send your sources?
Same here, btw.
Sent from my Nexus 6P using Tapatalk
eidl113 said:
Can you send your sources?
Same here, btw.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I don't remember what site it was it was 4am and I was just having coffee and It came up in my Google now news feed. The post wasn't about that I read it in the comment section after the post. Also I see some people on here who did sidload it and are having problems with recovery and some apps. So personally I am going to wait till Google fixes it.
maybe they are actually trying to fix the slow-motion bug that has existed since release on 6.0. after a day or two, slow motion records very choppy. the small group of people who actually notice the bug think it will never get fixed. oh well....
mojorisin7178 said:
I don't remember what site it was it was 4am and I was just having coffee and It came up in my Google now news feed. The post wasn't about that I read it in the comment section after the post. Also I see some people on here who did sidload it and are having problems with recovery and some apps. So personally I am going to wait till Google fixes it.
Click to expand...
Click to collapse
mojorisin7178 said:
Don't side load from what I read it hasn't come for the 6p yet because of some issues that are being worked out. I haven't checked to see if they pulled the images but I would just wait for the OTA. I also read that dp5 is really laggy on the Nexus 6
Click to expand...
Click to collapse
I sideloaded DP5 to my 6P on Monday, and I can confirm that it's borderline disastrous. It's way slower and jankier than the last couple of preview milestones, and there's general bugginess that I didn't see in the last two builds. Additionally, I've had way more crashes than I experienced on DP3 and DP4, both of which were mostly stable. I hope the OTA delay means they are working out a few kinks, because I would hate for this to be what Google considers "near final" software.
Thanks for the heads up.
Sent from my Nexus 6P using Tapatalk
curtis_bond said:
I sideloaded DP5 to my 6P on Monday, and I can confirm that it's borderline disastrous. It's way slower and jankier than the last couple of preview milestones, and there's general bugginess that I didn't see in the last two builds. Additionally, I've had way more crashes than I experienced on DP3 and DP4, both of which were mostly stable. I hope the OTA delay means they are working out a few kinks, because I would hate for this to be what Google considers "near final" software.
Click to expand...
Click to collapse
I'm sure that is what the delay is. I was thinking it was a OTA issue but then I saw your post a a few others. This is the first android phone I have ever owned that I didn't root right out of the box. I'm too tired to do all the flashing and deal with the bugs and all that. I didn't even opt in to the dev preview till dp3. With that said all my previous experience has taught me to research before I update or install new software and wait till it is mostly bug free. This phone just works. I won't have to root it till Google stops supporting it and I have to go with cyanogenmod
mojorisin7178 said:
I'm sure that is what the delay is. I was thinking it was a OTA issue but then I saw your post a a few others. This is the first android phone I have ever owned that I didn't root right out of the box. I'm too tired to do all the flashing and deal with the bugs and all that. I didn't even opt in to the dev preview till dp3. With that said all my previous experience has taught me to research before I update or install new software and wait till it is mostly bug free. This phone just works. I won't have to root it till Google stops supporting it and I have to go with cyanogenmod
Click to expand...
Click to collapse
Could you do us a favor and let us know if/when the OTA pops up on your device? It would be nice to compare build numbers to see if Google is preparing an updated build for release.
Curtis Bond, Thanks for the very helpful post! I feel a lot more patient waiting for DP5 now.
Sent from my Nexus 6P using XDA-Developers mobile app
Hey guys, I got mine around noon in Philadelphia, PA. Prior to that, I was experiencing the same issues you guys were in that my OTA was not showing up. Happy updating!
Me too I got mine at 12:30 pm in new York. It now says android 7.0 instead of Android n npd90g is the build number. I just finished with work so I have to test it out but so far it seems to be really good and snappy. And yes they fixed the toggle switches back to what they should be.
I just checked and OTA was ready to download. Installing dp5 now.
Downloaded and running....
Seems faster?
Sent from my Nexus 6P using XDA-Developers mobile app
Google disabled the option to reply directly from lockscreen. Now everytime you want to reply you need to unlock the phone. What's the point?
Sent from my Nexus 6P using Tapatalk
If I already sideloaded will I get the fixed OTA? Did they uploaded the fixed version to https://developer.android.com/preview/download.html yet?