Develop Bugs

OTA update Fix new for O2 Phones/Customers

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...

Did Verizon stop the 12A role out?

Quick question for the forum. I was wondering if anyone reading has not yet received the VS98612A update (that is not rooted) that was pushed to some users at the beginning of October?
The reason I ask is that I am planning to sell this phone. First the touch screen issues, now I intermittently receive push notifications over WiFi which has kind of turned into a deal breaker for me. Since the upgrade, the touch screen and overall software performance have been great, BESIDES the notifications. Since I would like to possibly sell this phone I was wondering what the chances of me getting a referb with the 12A update if I were to send my current phone in for a replacement. Apparently my conscious won't let me sell a phone that has a known software big to someone who may completely unaware.... If only Verizon/LG felt the same way....
Thanks,
Nate
Vs98612a
Sent from my VS986 mobile app

They pulled the update as far as I can tell. My VS98611a unrooted cannot see it. Was stoked about the Marshmallow update news until they apparently pulled the European update as well! LG, W T F!
I put my SIM back in my G2 and wow, its a way better phone experience. The antennas and camera aren't as good, but everything else feels like an upgrade IMHO.

natec003 said:
Quick question for the forum. I was wondering if anyone reading has not yet received the VS98612A update (that is not rooted) that was pushed to some users at the beginning of October?
The reason I ask is that I am planning to sell this phone. First the touch screen issues, now I intermittently receive push notifications over WiFi which has kind of turned into a deal breaker for me. Since the upgrade, the touch screen and overall software performance have been great, BESIDES the notifications. Since I would like to possibly sell this phone I was wondering what the chances of me getting a referb with the 12A update if I were to send my current phone in for a replacement. Apparently my conscious won't let me sell a phone that has a known software big to someone who may completely unaware.... If only Verizon/LG felt the same way....
Thanks,
Nate
Vs98612a
Sent from my VS986 mobile app
Click to expand...
Click to collapse
I sent in my bricked 12A and got back 11A with no update in sight. So I'd say, send it back.

I'm trusting you lol. Just called and am having another one sent. Have a nexus 6P being delivered tomorrow, but will have to wait a day or 2 to activate it until I get my referb g4. Thanks for the update!
Sent from my VS986 using XDA Free mobile app

P8000 unusual problem.

Hello.
11.11.2015 i recived a notification on phone that Elephone had released a new update to improve system functioning ect.
Keep in mind this is a stock p8000. nothing done with it.
I downloaded update, installed and it said phone will reboot.
After that phone is stuck in bootloader and simply wont boot.
Ive tried wiping cache and factory reset but PHONE WONT turn on.
So question is. What the hell do i do now?

There's like five threads about the same problem, so nothing really unusual about this excerpt for the lack of quality control from Elephone which apparently releases broken OTA:s and phones with old or modified base roms. ?
This thread should be merged with other ones.

Have anyone found a solution?
pitrus- said:
There's like five threads about the same problem, so nothing really unusual about this excerpt for the lack of quality control from Elephone which apparently releases broken OTA:s and phones with old or modified base roms.
This thread should be merged with other ones.
Click to expand...
Click to collapse
Have anyone found a solution to the problem then?
Or is my only choice to open a dispute with PayPal?

The Boards are full of Threads and solutions about this problem !
Why aren't you looking around a bit ?
How about the first post in Q&A section ???
http://forum.xda-developers.com/elephone-p8000/help/boot-loop-ota-upgrade-t3246203

StormiZMo said:
Have anyone found a solution to the problem then?
Or is my only choice to open a dispute with PayPal?
Click to expand...
Click to collapse
manually flash the stock rom .. i faced the same ****.. i followed the below steps and my elephone working fine
http://bbs.elephone.hk/thread-9229-1-1.html
hope this will work...

Fixed
As it turns out i managed to fix the problem.
Manually flashed a new rom and now the phone works fine. Tho im not installing the new update again.
Have to be said that the people behind the update and responsible for keeping the phone updated and fresh should have been fired.
People without the necessary skills on this subject would have to return or get the money refunded because THE only way to fix this is flashing a new rom..
Thanks for the help people!!

StormiZMo said:
Have to be said that the people behind the update and responsible for keeping the phone updated and fresh should have been fired.
Click to expand...
Click to collapse
LOL, fired for what? it worked on most devices.
you get what you pay for! how are elephone selling a phone with decent specification for that price? they cut corners everywhere.
quality being 1 and skilled staff is the other.
with the given resources, their staff did they best they could with the test hardware they had.

StormiZMo said:
As it turns out i managed to fix the problem.
Manually flashed a new rom and now the phone works fine. Tho im not installing the new update again.
Have to be said that the people behind the update and responsible for keeping the phone updated and fresh should have been fired.
People without the necessary skills on this subject would have to return or get the money refunded because THE only way to fix this is flashing a new rom..
Thanks for the help people!!
Click to expand...
Click to collapse
Also, most China phones don't even get updates, or even more exclusive, source code releases like this one. My guess is that there's likely only a one man show in charge of software development for this model, so give them some slack will you. [emoji1]

mine went off to after the OTA so i had to flash manually and like my friend said there trying, unlike most china phone company's so even though mine failed my father's and my friend's p8000 got there OTA np

It seems like the first 5000 batch delivered had no notification led,they seem to put in different hardware thats available.So end up with a hotch podge of slightly different devices.
So fingers crossed that a update works.Thankfully Elephone allows ,enables development.

It also looks like OTA update fails on rooted phones, which is not so different than what happens to most Android phones. When I used a Samsung phone long ago, OTA update notifications wouldn't even show up if you had rooted your phone, and on other phones I remember having a similar issue after I applied an OTA update with the phone rooted

Verzion started bricking the N7?

There is a thread on another forum that a user's phone is suddenly non responsive over night. I am not sure if link can be posted or not. Anyone else has this problem?

Is it possible his (or her) phone is simply about to fail like so many others have because it's a known defective device?

I have the updates blocked, and mine is still good to go.

Cool, there hadn't used to be a warning before it happened . It appears more like IMEI block I think? It is only showing Verzion logo and some "lights are blinking"? Disabling updates wouldn't prevent it?

My original unit shut off on its own and then started bootlooping. And then with a few magic presses, the entire thing got wiped out. So bad, the Samsung Service Centre couldn't recover it. And actually told me to wait for the exchange. The first one.
So...I doubt it's Verizon bricking the N7.

So mine actually got blocked , i was using it on tmobile and then all the sudden it stopped working. It was working fine on ATT but on tmo it was dead , i did a IMEI check and it showed it was blacklisted. This happen a week ago now! wala! it magically works 0_0

Why would Verizon do this?
I mean, what's in it for them to block or disable your phone? I don't get it. They are not stolen.

To avoid any potential law suits against them? Actually I don't think they would do it themselves but by the request of Samsung. There is now a law suit filed over exploding s6. Half of the population can't distinguish between Note 7 and their other phones. Samsung might be forced to do it just to save reputation. If they can claim there are no more Note 7s in use, they can protect it better than by saying "Oh we let 1 million of them stay in use because we believe they won't explode"...
Edit: Probably hasn't happened in this case though, I am sure there would have been a warning first, notification of public by Samsung...

I think they'd open themselves up to lawsuits if they go around disabling peoples' phones without formal written notification, not just rumours on websites and chat rooms. And maybe lawsuits even after the warning. I've not read all the detailed t's and c's and maybe they would be within their rights to do it, but maybe in fact they would not.

Probably they are, because there has been a recall and are offering refunds. I don't know...

notefreak said:
Probably they are, because there has been a recall and are offering refunds. I don't know...
Click to expand...
Click to collapse
That doesn't explain it.

taz1458 said:
I have the updates blocked, and mine is still good to go.
Click to expand...
Click to collapse
What did you use to block future OTAs? Thanks!

CraigSam said:
What did you use to block future OTAs? Thanks!
Click to expand...
Click to collapse
Package disabled pro

taz1458 said:
Package disabled pro
Click to expand...
Click to collapse
Trying that now. Thanks!

Nougat Beta Completed - Official update due in January to S7 and S7 Edge

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.