Related
Just thought I'd pass some information on I had from my O2 Premium support team. Google has advised that a fix was released to 1000 handsets yesterday from 17:00Hrs GMT. They will make sure that no issues arise from the fix and if all is well will start rolling out a full scale update 24Hrs Later, ie this evening from 17:00Hrs.
Anyway looks like it will be sooner rather than later
JustinL01 said:
Just thought I'd pass some information on I had from my O2 Premium support team. Google has advised that a fix was released to 1000 handsets yesterday from 17:00Hrs GMT. They will make sure that no issues arise from the fix and if all is well will start rolling out a full scale update 24Hrs Later, ie this evening from 17:00Hrs.
Anyway looks like it will be sooner rather than later
Click to expand...
Click to collapse
Very nice if it turns out to be true
That is actually smart move releasing to just 1k handsets to avoid any mass problems.
From what i understood the O2 phones firmware was the same as the sim frees/all the others, meaning o2 wont even be involved in ANY updates , that they'll all just come direct from Google.(that has to be good news)
Nice to know it's on the way though, although i've yet to experience the problem in "real life" and not having to put another phone 2mm away from it.
rbs_uk said:
That is actually smart move releasing to just 1k handsets to avoid any mass problems.
Click to expand...
Click to collapse
It does seem like a smart thing to do, although it does beg the question...how does O2 / Google know which handsets have received the update, and also how quickly do they expect people to be able to verify if they're still exhibiting symptoms?
oscillik said:
It does seem like a smart thing to do, although it does beg the question...how does O2 / Google know which handsets have received the update, and also how quickly do they expect people to be able to verify if they're still exhibiting symptoms?
Click to expand...
Click to collapse
Could handset send feedback back to o2 after it has updated itself so that o2 know what firmware your phone is running? Or if you phoned o2 they will ring you back and ask if you are still expriencing this fault.
rbs_uk said:
Could handset send feedback back to o2 after it has updated itself so that o2 know what firmware your phone is running? Or if you phoned o2 they will ring you back and ask if you are still expriencing this fault.
Click to expand...
Click to collapse
Hmmm I personally doubt it, since the firmware is supposed to be un-tied to carrier tinkering.
If the carriers are aware of what firmware any of it's customers handsets are running, that raises another worrying issue. But I really don't think that they are capable of finding this out.
As an aside, I used to work for the UK's largest pub gaming machine company, and we had the largest network of computer-based touchscreen gaming machines (at the time at least) and they all ran a custom java based software running on top of Windows. When we made updates to the games or anything else, we would always roll out the update to 1000 machines as a preliminary measure.
The difference there however is that we knew exactly which machines had the updates, and could keep track of any issues that popped up. I don't see how Google would be able to do this unless these 1000 handsets they're talking about are Google employees (could very well be possible).
Mine (o2 via p4u) updated itself last night to android version 4.0.1
not really had the problem with the volume control, so can't say if it helped. But nothing else seems to have changed
oscillik said:
I don't see how Google would be able to do this unless these 1000 handsets they're talking about are Google employees (could very well be possible).
Click to expand...
Click to collapse
could be.. as you'd think atleast 1 of the 1000 would have posted here on XDA
**edit**
post above proves me wrong - although my android version is 4.0.1 and i have had no update
drp297 said:
Mine (o2 via p4u) updated itself last night to android version 4.0.1
not really had the problem with the volume control, so can't say if it helped. But nothing else seems to have changed
Click to expand...
Click to collapse
The HSPA+ version of the Galaxy Nexus has always had 4.0.1, so you haven't received any update at all.
I don't think the Android version is changing it's the buildnumber that is changing, mine is currently ITL41D, he advised a new version of that.
rbs_uk said:
Could handset send feedback back to o2 after it has updated itself so that o2 know what firmware your phone is running? Or if you phoned o2 they will ring you back and ask if you are still expriencing this fault.
Click to expand...
Click to collapse
It would likely go to Google, not O2, and is IMEI based, so they will know how many and which handsets have received the update. They will log the IMEIs that the update was sent to and if you call your various support options with a complaint one of the questions will certainly be your IMEI number. Then this can be cross-referenced to see if you have received the update or not (and evaluate 1. it's success 2. other problems it generated).
When the phone's IMEI gets released for the OTA, there is a "whisper" service that checks the software/whatever version and if below the impending OTA it will prompt the notification for the update- if the same it will send no notification and the user will have no idea of/no need for the OTA. At least this is generally how the G1 and N1 both worked in the past.
JustinL01 said:
I don't think the Android version is changing it's the buildnumber that is changing, mine is currently ITL41D, he advised a new version of that.
Click to expand...
Click to collapse
He never mentioned what build number he had, as you can see he just mentions Android version:
drp297 said:
Mine (o2 via p4u) updated itself last night to android version 4.0.1
not really had the problem with the volume control, so can't say if it helped. But nothing else seems to have changed
Click to expand...
Click to collapse
I turned it back on and it said it was updating itself...
I hope my phone isn't lying to me...
They all say 'Android is updating' everytime you power the phone on ;-)
oscillik said:
He never mentioned what build number he had, as you can see he just mentions Android version:
Click to expand...
Click to collapse
No not the poster I am talking about what I was advised by O2, it is the buildnumber that differed with the update.
drp297 said:
I turned it back on and it said it was updating itself...
I hope my phone isn't lying to me...
Click to expand...
Click to collapse
Ice Cream Sandwich does that. Everyone's phone does that, it's already been raised on here in at least two separate threads.
It doesn't mean you have received an Android update, it is regarding Android getting the home screen and apps ready.
an OTA update would require user intervention to be applied - you would have to first of all agree to the phone downloading and applying the update.
Well, if it really is released today at 5pm then we will know in little bit more than an hour,so keep your fingers crossed ;-)
gambiting said:
Well, if it really is released today at 5pm then we will know in little bit more than an hour,so keep your fingers crossed ;-)
Click to expand...
Click to collapse
It was due 5pm yesterday too. Fingers firmly uncrossed, only a single digit is required aimed squarely at sam/goog.
I heard that they are updating the baseband, not the software version...
I have not received any update for Android 5.0 yet. I find this pretty odd considering it has been out for a long time. Everything seems to be functionally normally, but I never get any OTA update notification and it says I have the latest updates. Is this something to be concerned about, or am I just extremely unlucky to be one of the last ones to get it? Thanks.
Dillon610 said:
I have not received any update for Android 5.0 yet. I find this pretty odd considering it has been out for a long time. Everything seems to be functionally normally, but I never get any OTA update notification and it says I have the latest updates. Is this something to be concerned about, or am I just extremely unlucky to be one of the last ones to get it? Thanks.
Click to expand...
Click to collapse
The Nexus 7 is experiencing issues with L. My dad's device also didn't get it yet.
However, nothing stops you from flashing the image yourself from Googl's developer site.
This is the first time I've heard of this. Thanks for giving us all a heads up!
Oh wait, there's only about 10 other threads on the first page about this very issue.
Is this a sloooooow rollout or what?
Yeah...
TabGuy said:
Is this a sloooooow rollout or what?
Click to expand...
Click to collapse
I am in Moscow, Russia, still no update.... I tried like 20 times to reset but nothing... This is getting frustrating!
same for me France
Any french did get it ?
Same in Germany (Erfurt)
Still no update to lollipop.
houdini1er said:
Any french did get it ?
Click to expand...
Click to collapse
Troyes, France, nothing...
Nothing in The Netherlands either.
Is there any easy way to push OTA zip without rooting or pogo cabling?. I mean via adb bluetooth, or similar...
nothing here usa
I'm thinking it's nothing to do with country now and possibly serial numbers instead.
nothing also here in Colombia, we're supposed to get it tomorrow 15/12 as someone said it would reach 100% of moto 360 that day. who knows if that's even true
http://phandroid.com/2014/12/14/motorola-moto-360-android-wear-lollipop-lwx48p-december-15/
If it's like their stock we can expect to wait few more weeks.
Begining of september you could read every where moto 360 is out, but no one had it in stock.... Not very serious compagny motorala
still nothing in Moscow....Russia
houdini1er said:
http://phandroid.com/2014/12/14/motorola-moto-360-android-wear-lollipop-lwx48p-december-15/
If it's like their stock we can expect to wait few more weeks.
Begining of september you could read every where moto 360 is out, but no one had it in stock.... Not very serious compagny motorala
Click to expand...
Click to collapse
Hound,
I believe that the rollout of Android Wear is by Google, not Motorola.
It's not like for the smartphone ? Well not very Lucky then...
Still nothing
I STILL have not gotten the lollipop update. This is annoying as fu**. I have tried resetting my watch multiple times and even clean flashed lollipop 5.0.1 from 5.0 to see if that made a difference but still no go. I then reverted back to stock (LG G3 T-mo D851) and reset my watch and wear app and looked for an update but still no luck. I then saw something strange. In the about page on my watch, I clicked on 4.4W.2 under "software version" it opened a page that says:
Android Wear
1.0.1.1526154
Google Play Services
6.1.74 (1511752-534)
On my phone the wear app is on version 1.0.5.1630507 and Google Play Services is version 6.5.99.
This is likely why my watch will not update, it doesnt think that my phone has the latest versions of each which is required to update my watch. I wonder if this is the method that google uses to control the rollout of the newest versions of wear... It would be a quick and dirty way to handle it but is not beyond the realm of possibilities..
Is anyone else having this issue and/or know a work around?
Thanks
there's another thread on this but for those still waiting, there are two builds floating around. some of us have received both builds so that could be the reason for the delay.
Do you need to be on a specific rom or something?
im using moto 360 (i bought in USA) and im using in Mexico and no update i get 5.01 in my gear live tho
I got the upgrade today in SoCal about 1pm.
Got it today in Kabul Afhganistan
Hi, I purchased this phone about a week ago and have loved it so far. I saw that Android 7 came out a day ago but when I search for updates I get the message that my device is up to date even though it's on 6.0.1. I have not rooted my phone yet (or even unlocked my bootloader), in short I have not messed with my phone yet, it's as it was when it came from the box (except for the OTAs installed).
All I can think the reason for this may be my region since I live in Pakistan. With my previous phone, I used to get the OTAs on time but this is my first nexus phone and I'm a bit disappointed that I'm not getting the update as soon as it is rolled out if that really is the case. Also, does anyone have an idea when I'll get my update?
this is called a staged rollout. it is to ensure the stability of the update servers as well as to grant google a chance to put an update on hold and safe the majority of the trouble, should critical errors come to light during the early phase of a rollout
Broken303 said:
this is called a staged rollout. it is to ensure the stability of the update servers as well as to grant google a chance to put an update on hold and safe the majority of the trouble, should critical errors come to light during the early phase of a rollout
Click to expand...
Click to collapse
Oh, so how long should it take given the staged rollout goes well.
Hadisultan said:
Oh, so how long should it take given the staged rollout goes well.
Click to expand...
Click to collapse
i believe up to two wrrks, but don't quote me on that. you could always make use of the beta-program to skip the line as i did. just look through some recent threads here or over at androidpolice
Hadisultan said:
Hi, I purchased this phone about a week ago and have loved it so far. I saw that Android 7 came out a day ago but when I search for updates I get the message that my device is up to date even though it's on 6.0.1. I have not rooted my phone yet (or even unlocked my bootloader), in short I have not messed with my phone yet, it's as it was when it came from the box (except for the OTAs installed).
All I can think the reason for this may be my region since I live in Pakistan. With my previous phone, I used to get the OTAs on time but this is my first nexus phone and I'm a bit disappointed that I'm not getting the update as soon as it is rolled out if that really is the case. Also, does anyone have an idea when I'll get my update?
Click to expand...
Click to collapse
You will get OTA update in first 2 weeks of the month, I always get about 15th day in the month, so don't worry.
How mate said, you can use android beta program, just you will get final update and after upgrade just leave android beta program
Sent from my Nexus 5X using XDA-Developers mobile app
Samsung apparently has sent out a final notification to all those enrolled in the Nougat Beta that there will be no more updates and that the beta ends officially on December 30th and that they will attempt to push out the official update to everyone in January. Hope this means they were able to quash all major bugs.
http://www.androidcentral.com/galaxy-s7-and-s7-edge-receive-nougat-update-january
And it is officially Android 7.1.1, at least for those in the US.
Hopefully we get it soon, I would love some Nougat. At this point I prefer to not have to root my phone to get updates because it's a hassle without being able to unlock the bootloader. I was rooted for awhile and IMHO stock runs butter unless you spend hours customizing it. I love debloating but I would prefer a fully unlocked/rooted phone to a partial solution.
I don't have high hopes for when we get this updated because of verizon but we eventually will, about 2 years after everyone else
JerseyDubbin said:
Hopefully we get it soon, I would love some Nougat. At this point I prefer to not have to root my phone to get updates because it's a hassle without being able to unlock the bootloader. I was rooted for awhile and IMHO stock runs butter unless you spend hours customizing it. I love debloating but I would prefer a fully unlocked/rooted phone to a partial solution.
I don't have high hopes for when we get this updated because of verizon but we eventually will, about 2 years after everyone else
Click to expand...
Click to collapse
I haven't been rooted for over a year. I was on an LG G3 before my S7 and so far, I haven't found a real need to root. Before, I rooted because I used TiBu to backup my apps, but with the G3, they had their own backup utility that worked just like TiBu, but it's only for LG devices.
But with how Google Play uploads settings now, that appears to work just fine for me as well, so at this point, I have no reason to root. Plus, I really love Samsung Pay so I don't want to lose that.
This is the first device I have owned that I have never rooted. No need to. Faster than anything I have ever owned and mine never slows down for my usage. It's the first device that I feel works as intended. I also wasted a few years of my life with this stuff and just don't have the motivation anymore. Especially without an unlocked bootloader and custom recovery, I'd never.
JediDru said:
This is the first device I have owned that I have never rooted. No need to. Faster than anything I have ever owned and mine never slows down for my usage. It's the first device that I feel works as intended. I also wasted a few years of my life with this stuff and just don't have the motivation anymore. Especially without an unlocked bootloader and custom recovery, I'd never.
Click to expand...
Click to collapse
Agree completely. The root process works well etc but I had to go through xposed and do a lot of tweaks to get it running well for really no gain over what I had stock.
JediDru said:
This is the first device I have owned that I have never rooted. No need to. Faster than anything I have ever owned and mine never slows down for my usage. It's the first device that I feel works as intended. I also wasted a few years of my life with this stuff and just don't have the motivation anymore. Especially without an unlocked bootloader and custom recovery, I'd never.
Click to expand...
Click to collapse
I completely agree. The G3 was the first phone I ended up not rooting. I did at first because I was just in that mode of, get a new phone, root, flash a custom ROM. But as I started getting used to a lot of the features, and found that the battery life wasn't bad, coupled with running Greenify in non-root mode, I could make the battery last 1.5 days. So, over the last year of the two years I owned it, I didn't root.
With the S7, no need to root. This is smoothest phone I've had yet. The quality of the phone itself is excellent. So, this phone will not be rooted.
It appears the official Nougat OTA is being pushed out, with beta testers getting it first.
Anyone on here that has gotten the Nougat OTA notification yet? I'm holding off on accepting until I know better on how it performs, etc.
http://www.androidcentral.com/stabl...ing-galaxy-s7-and-s7-edge-starting-beta-users
iBolski said:
It appears the official Nougat OTA is being pushed out, with beta testers getting it first.
Anyone on here that has gotten the Nougat OTA notification yet? I'm holding off on accepting until I know better on how it performs, etc.
http://www.androidcentral.com/stabl...ing-galaxy-s7-and-s7-edge-starting-beta-users
Click to expand...
Click to collapse
Nothing on my end yet.
Sent from my SM-G930V using XDA-Developers Legacy app
was there ever a second beta OTA sent out to Verizon testers? I didn't get into the beta but side loaded the only 7.0 beta build OTA that was floating around and my build number is NRD90M.G930VVRU4ZPK4. Was there an update to after that? Trying to figure out if the Nougate beta -> final OTA (assuming someone pulls it) will work on my phone or if I'll need to find the intermediary beta OTAs or else wipe clean and start from scratch.
sklarskyj said:
was there ever a second beta OTA sent out to Verizon testers? I didn't get into the beta but side loaded the only 7.0 beta build OTA that was floating around and my build number is NRD90M.G930VVRU4ZPK4. Was there an update to after that? Trying to figure out if the Nougate beta -> final OTA (assuming someone pulls it) will work on my phone or if I'll need to find the intermediary beta OTAs or else wipe clean and start from scratch.
Click to expand...
Click to collapse
I believe there were only two betas for VZW phones and then they cancelled the beta testing for VZW-based phones. Not sure why. Kind of sucks. Probably Big Red had something to do with it.
j0hnh0lmes said:
Nothing on my end yet.
Sent from my SM-G930V using XDA-Developers Legacy app
Click to expand...
Click to collapse
Same here, tried rebooting and checking again a few times and still nothing.
Oh well
I spoke to Verizon about this and they dont know when the update will be out.
SoerenHelmer said:
I spoke to Verizon about this and they dont know when the update will be out.
Click to expand...
Click to collapse
Of course they don't. They have to add crapware, disable a bunch of stuff and add backdoors.
Sent from my SM-G930V using XDA-Developers Legacy app
SoerenHelmer said:
I spoke to Verizon about this and they dont know when the update will be out.
Click to expand...
Click to collapse
That's their usual response.
I've read US-Based carriers have no ETA yet. Grr.
iBolski said:
I've read US-Based carriers have no ETA yet. Grr.
Click to expand...
Click to collapse
I swear searching around the interwebs for information on release dates has at least as much mis-information as looking for information on the election candidates during the election. So much trash.
But I haven't found anyone stating they heard definite dates. I'm thinking it will be late January at this point maybe early Feb before it hits our phones.
i have given up speculating anything that involves verizon. nothing would surprise me.
Take it where its coming from but it looks like some US non-beta testers are starting to see the update. "Unlocked" phones only but still....
http://www.theverge.com/2017/1/19/14321980/samsung-galaxy-s7-edge-android-nougat-update
I have an official unlocked US model, but nothing yet. I expect to see the update by the weekend. Crossing fingers.
lickwid said:
I have an official unlocked US model, but nothing yet. I expect to see the update by the weekend. Crossing fingers.
Click to expand...
Click to collapse
I believe unlocked models should be getting it before us on Verizon. But, there was a story out that stated OTAs for some reason have stopped being pushed out and Samsung has acknowledged this and is looking into why it happened.
http://www.droidviews.com/samsung-galaxy-s7-android-nougat-problems-firmware-delivery-stops/
Whether the "bug" is in the firmware itself or with the update process that sends out the notifications is not mentioned.