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?
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.
Invites went out today. Finally, we're getting an official Jelly Bean update 10 months after WiFi. If anyone is participating in the soak test, could you pull the OTA URL? I wonder if this will be JZO54K like WiFi or if it'll be a newer build of 4.1.2. I guess we'll see!
Thanks!
Sent from my Xoom using Tapatalk HD
This is excellent news of course, despite being ridiculously late arriving.
I have been running the leaked Motorola 4.1.1 JRO03H build since it dropped last June so I certainly hope its a newer build than that one.
It's actually quite stable despite some annoyances like limiting write access to the sdcard and keyboard misbehavior persisting.
The radios perform very well in this build so it will be interesting to see what changes, if any, appear assuming a new baseband is included.
How do you capture the URL?
I think it's a shame google stopped supporting the xoom. A google experience device and for a long time, the baby of android, always getting the OS updates first. Now it's just the red headed stepchild to the nexus 7 and 10. I would love to see google give us official 4.3 but that probably won't happen. If they did though, it would be really good PR and xoomers would rejoice.
scoobaspeaz said:
How do you capture the URL?
Click to expand...
Click to collapse
When you get the OTA notification, but before applying the update, run adb logcat and output it to a text file. It'll be in there. The URL will be something like this: http://android.clients.google.com/p...signed-trygon-JZO54K-from-IMM76L.abcdef12.zip
Thanks!
Sent from my Galaxy Nexus using Tapatalk 4 Beta
cellzealot said:
This is excellent news of course, despite being ridiculously late arriving.
I have been running the leaked Motorola 4.1.1 JRO03H build since it dropped last June so I certainly hope its a newer build than that one.
It's actually quite stable despite some annoyances like limiting write access to the sdcard and keyboard misbehavior persisting.
The radios perform very well in this build so it will be interesting to see what changes, if any, appear assuming a new baseband is included.
Click to expand...
Click to collapse
There's no discussion. It'll be newer. It'll either be JZO54K like Wi-Fi or a newer build of 4.1.2 that we haven't seen yet (unlikely). I'm sure there will at least be a new CDMA baseband if not a new LTE baseband as well. I say this because the original leaker of that 4.1.1/JRO03H build had a newer CDMA baseband in his screenshot that no one had ever seen before (03.1A.66SP), but his LTE baseband was the same as the IMM76L ICS build.
Speaking of that leaked 4.1.1/JRO03H build, it looks like it was just the Wi-Fi build with the LTE drivers dropped in for testing.
The leaker claimed that Verizon had signed off on it but I don't buy it for two reasons. First, it was never released. Second, that build has a major DRM bug. Google Play Movies won't stream content when using that build because either the DRM keys are hosed or the build itself has something turned on that makes the app think the ROM is rooted.
As for how he got it, he said his own Xoom had the build installed by Motorola development. That much I do believe due to the fact that he had a CDMA baseband that no one else had ever seen.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Anyone get the soak test yet?
Sent from my Nexus 7 using Tapatalk HD
oldblue910 said:
Anyone get the soak test yet?
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Not yet. I have made a couple posts about this up and coming and seems no one heard me. Glad to see someone is happy as me
I am 100% certain I will get the soak as I have received the last 3 released on my phones. I will go to xda w/out passing "go " or collecting $200 lol. No pit stops. You will be the first to know.
Sent from my MZ617 using Tapatalk 2
Thanks, man!
Sent from my Galaxy Nexus using Tapatalk 4 Beta
I am on pins and needles for this. Hopefully the soak test starts today!
Sent from my Nexus 4 using Tapatalk 4 Beta
Small snag...my xoom is not my daily driver b/c I gave to my wife. I will not have my hands on it until next week. Hopefully I can pull the link from email when it hits...if not just be patient with me. Her finals is this week and don't want me messing with it lol.
Sent from my MZ617 using Tapatalk 2
csmoore88 said:
Small snag...my xoom is not my daily driver b/c I gave to my wife. I will not have my hands on it until next week. Hopefully I can pull the link from email when it hits...if not just be patient with me. Her finals is this week and don't want me messing with it lol.
Sent from my MZ617 using Tapatalk 2
Click to expand...
Click to collapse
No worries. By next week hopefully there will be a public OTA! haha
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Project: platform/build
eab7126 : JZO54L
Project: device/moto/stingray
80ce2db : RIL and network configuration update for new modem
looks like maybe you'll be getting JZO54L....
xdatastic said:
Project: platform/build
eab7126 : JZO54L
Project: device/moto/stingray
80ce2db : RIL and network configuration update for new modem
looks like maybe you'll be getting JZO54L....
Click to expand...
Click to collapse
Thanks! Note if only they'd hurry and release it! haha Where did you find that?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
oldblue910 said:
Thanks! Note if only they'd hurry and release it! haha Where did you find that?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
sorry i forgot to give my source. was a google plus post by this mob which linked to their site:
http://www.funkyandroid.com/aosp-JZO54K-JZO54L.html
...which can be verified here:
https://android.googlesource.com/device/moto/stingray/+/android-4.1.2_r2
it doesnt confirm you'll get that build, but seems likely i guess.
And our seemingly endless wait continues. Ugh.
Sent from my Galaxy Nexus using Tapatalk 4 Beta
I also got an invite for the soak test and signed up. I'd be happy to help out. My Xoom is on the Verizon network but my bootloader is unlocked. Will I need to lock the bootloader to get the update?
ggparker said:
I also got an invite for the soak test and signed up. I'd be happy to help out. My Xoom is on the Verizon network but my bootloader is unlocked. Will I need to lock the bootloader to get the update?
Click to expand...
Click to collapse
Nope, your bootloader can remain unlocked. As long as you're running the stock ICS 4.0.4/IMM76L firmware, you'll get the update when they finally do roll the soak test out. Do you know how to pull an update URL, or do you need me to provide you some quick steps?
oldblue910 said:
Nope, your bootloader can remain unlocked. As long as you're running the stock ICS 4.0.4/IMM76L firmware, you'll get the update when they finally do roll the soak test out. Do you know how to pull an update URL, or do you need me to provide you some quick steps?
Click to expand...
Click to collapse
I am running ICS 4.0.4/IMM76L so I should be good. I just ran adb logcat and dumped the logs. Worked fine. So after I receive the notification but before downloading and installing I need to run logcat, correct?
ggparker said:
I am running ICS 4.0.4/IMM76L so I should be good. I just ran adb logcat and dumped the logs. Worked fine. So after I receive the notification but before downloading and installing I need to run logcat, correct?
Click to expand...
Click to collapse
You got it. Just output the logcat to a text file and then search the text file for "android.clients.google.com". Post the URL here. Simple as that. Thanks for your help!
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.....
Hey guys. My dad upgraded his 6p to 7.0 via the beta program. He still has not gotten the September security update. I keep thinking he should've gotten it by now. Anyone else have this issue?
acts4:12 said:
Hey guys. My dad upgraded his 6p to 7.0 via the beta program. He still has not gotten the September security update. I keep thinking he should've gotten it by now. Anyone else have this issue?
Click to expand...
Click to collapse
This is purposeful. Google does slow rollouts for OTAs, presumably to monitor potential OTA issues on release. Every device receives OTAs at a different time spanning weeks.
Sent from my Nexus 5X using Tapatalk
I re-enrolled in the Beta program yesterday and it sent me the September update a minute later. Try un-enrolling and re-enroll and see what happens. My concern is the camera's new on screen zoom +and - buttons and burst mode button. I find them very annoying and unnecessary. Can't seem to turn em off though.
joelsgotmail said:
I re-enrolled in the Beta program yesterday and it sent me the September update a minute later. Try un-enrolling and re-enroll and see what happens. My concern is this new on screen zoom +and - buttons and burst mode button. I find them very annoying and unnecessary. Can't seem to turn em off though.
Click to expand...
Click to collapse
Ya that's what I had him do. It sent him the NRD90T update. Hopefully from here on out hell just be able to get the update OTA without a problem
Anyone have any idea when we may get a Leaked of Android 10 Beta, since T-Mobile is working on it I read???
It may not leak, who knows. The official betas only work with the Google pixel which is out already. To me, Android 10 sucks as it's all swipe gestures to do stuff, so I am not in a hurry to get it.
tailgunner9 said:
Anyone have any idea when we may get a Leaked of Android 10 Beta, since T-Mobile is working on it I read???
Click to expand...
Click to collapse
Sorry bro, but T-Mobile is no longer working on the Android 10. They had marked the Android 10 update under the 'testing' phase earlier, but it turns out it was a mistake as yesterday, they fixed by marking the update to be under 'Development' phase, meaning Samsung is still building the update and that they are yet to receive it. (Source)
Sad.
There's been a beta program with every other major release for Samsung, why not 10
StoneyJSG said:
It may not leak, who knows. The official betas only work with the Google pixel which is out already. To me, Android 10 sucks as it's all swipe gestures to do stuff, so I am not in a hurry to get it.
Click to expand...
Click to collapse
Sounds like iOS from Apple phones to me with Swipe.
tailgunner9 said:
Sounds like iOS from Apple phones to me with Swipe.
Click to expand...
Click to collapse
You still have the option for buttons. If your upgrading from 9 with buttons enabled it will stay after update. Otherwise you have the option during setup and in settings.
Sent from my SM-G975U using XDA Labs
jwarrior319 said:
You still have the option for buttons. If your upgrading from 9 with buttons enabled it will stay after update. Otherwise you have the option during setup and in settings.
Sent from my SM-G975U using XDA Labs
Click to expand...
Click to collapse
This is good news! I thought on screen buttons were completely removed from Android 10 due to a YouTube demo I watched. I gotta have my buttons!
StoneyJSG said:
This is good news! I thought on screen buttons were completely removed from Android 10 due to a YouTube demo I watched. I gotta have my buttons!
Click to expand...
Click to collapse
Yep me also StoneyJSG.
So looking at the ota server log its looking like they are currently working on android 10 update.
The "o=10" part is usually what marks the android version the firmware is for. (i cant confirm that but based on previous updates listed that number has reflected the android version)
http://fota-cloud-dn.ospserver.net/firmware/SPR/SM-G975U/version.test.xml
Sent from my SM-G975U using XDA Labs