Database Info

OTA update in stages?

Just wondering if it is rolling out in stages as it does for major updates?
My girlfriend and I both have a Captivate, both bought on release date at same place.
I checked for updates on both phones, and hers found one, mine did not. I'm no to worried about it honestly, just wondering.

Yes, that is correct. About 15k per day for the next few weeks.
Or if you don't want to wait, you could always move the date on your phone ahead and try again. That's how I got mine, had to go two days ahead.
Good luck.

Yes, the update will be done in batches based on your IMEI number's.. It will be a push message to the phone.. so you don't necessarily have to go to the settings->>software update menu - I keep getting the "communication failed" error - regardless how many days I set ahead

cappysw10 said:
Yes, that is correct. About 15k per day for the next few weeks.
Or if you don't want to wait, you could always move the date on your phone ahead and try again. That's how I got mine, had to go two days ahead.
Good luck.
Click to expand...
Click to collapse
Were you rooted when you updated?

bassahaulic said:
Were you rooted when you updated?
Click to expand...
Click to collapse
Sure was, and was after the update. Sideloading still works as well. Dunno if this will be the case if/when we get a Froyo update.
Reading through all the troubles that people were having I did remove the clockwork update zip before trying. Don't know if that had any bearing, I'm just paranoid. Worked like a charm.

Random OTA update

I'm downloading a new software update . I had already installed the last update.
edit
When I say last update I meant the one with the GPS fix.
What else could this be besides froyo ?
edit
Something funny happen, the update didnt install and now I cant check for another one.
edit
I changed the date on my phone so now I'm trying the update again.
edit
It keeps failing, so I dont know what this is .

wrong.........

i tried 4 times, wasted many of my limited data, never get updated. Att sucks.

pobinghun said:
i tried 4 times, wasted many of my limited data, never get updated. Att sucks.
Click to expand...
Click to collapse
AT&T doesn't charge you for anything that comes from the update server. You sir, suck. ;-)

i just got my brand new phone in the mail yesterday, im just gonna wait till it tells me there's an update before I download any updates..

link12245 said:
AT&T doesn't charge you for anything that comes from the update server. You sir, suck. ;-)
Click to expand...
Click to collapse
It sure does show up under data used, so I assume that it will be counted against you data plan.

Is your phone rooted? Showing symptoms associated with.

AGAIN
Yeah I have no idea what this update is ? This is like the 5th time it failed on me, so forget it.
I am rooted.

When I got the update, I had just gotten the phone. The update went through just fine, the day after I rooted my phone. So maybe rooting had something to do with it. I don't see how that could effect it but maybe.

I think it's time you detach the umbilical cord to the OTA update Update using Clockwork. (Just a suggestion).

[Q] voice search bug but no OTA update yet

I just bought a Nexus S, bought via Fido account but I SIM it to Rogers Canada. I have the voice search popup bug and I thought there was an OTA update for this. I'm still on 2.3.4. Does it just take time or does the carrier make any difference at all? I'm stock except for root.

3rdcoast said:
I just bought a Nexus S, bought via Fido account but I SIM it to Rogers Canada. I have the voice search popup bug and I thought there was an OTA update for this. I'm still on 2.3.4. Does it just take time or does the carrier make any difference at all? I'm stock except for root.
Click to expand...
Click to collapse
It takes time. The OTA will likely roll out over a few weeks. Once your imei is flagged you'll get the ota when the device checks in again.
Sent from my Nexus S using xda premium

you could try a manual check in or installing the update manually.
dial *#*#2432546#*#* to do a manual check in (didn't work for me, but give it a try anyways)
edit: follow this thread to update manually --> http://forum.xda-developers.com/showthread.php?t=1056062

hoponpop said:
you could try a manual check in or installing the update manually.
dial *#*#2432546#*#* to do a manual check in (didn't work for me, but give it a try anyways)
Click to expand...
Click to collapse
That has never worked for me. Does it actually work for anyone?

Thanks folks. I'll wait a few days before looking at a manual update. Or until the bug happens too often. It rather freaked me out at first and then I found that this is a common bug on certain versions of the phone.

The "search button firing on its own" bug is NOT fixed in the latest OTA
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en
I still have it and so do half a dozen or more people in the thread that got this whole thing started.
I know "Voice Search" bug has already penetrated the blogosphere ecochamber, and it is therefore useless for me to continue to correct people on semantics, but the Voice Search app just happens to be tied to a long-press of the search button so occasionally it pops up when this bug occurs. If "compose new text message" is tied to that event, you will see it and not Voice Search.. its the hardware search button that fires in low 3G areas that is the bug. Voice Search the app is completely unrelated other than most people have it tied to long-press of the hardware search button... ok, off my soap box

ericshmerick said:
That has never worked for me. Does it actually work for anyone?
Click to expand...
Click to collapse
I have no idea lol. I just figured the op could see if it works for him.

like I said, I'm not going to force an update, if I wanted it that bad I'll flash it from recovery. Now that I know what this is about I see that the update doesn't fix the problem anyway so why update? It will likely just cause more trouble. Turning off data is a crappy work around. I'll give it just enough time to get fixed by google where I can still take this back and then never look at a Samsung ever again. That's what I said about the SGS but I got the N on a direct swap so I tried it and am already disappointed.

hoponpop said:
you could try a manual check in or installing the update manually.
dial *#*#2432546#*#* to do a manual check in (didn't work for me, but give it a try anyways)
edit: follow this thread to update manually --> http://forum.xda-developers.com/showthread.php?t=1056062
Click to expand...
Click to collapse
I've used this successfully. It's how I got 2.3.6 on Friday morning and got the link to post in the forums
Sent from my Nexus S

3rdcoast said:
like I said, I'm not going to force an update, if I wanted it that bad I'll flash it from recovery. Now that I know what this is about I see that the update doesn't fix the problem anyway so why update? It will likely just cause more trouble. Turning off data is a crappy work around. I'll give it just enough time to get fixed by google where I can still take this back and then never look at a Samsung ever again. That's what I said about the SGS but I got the N on a direct swap so I tried it and am already disappointed.
Click to expand...
Click to collapse
Ok, there is an update and yes it takes time for every IMEI to be loaded into Google's system for dispatch.
Your options are:
1. Force update by using checkin and hope it works
2. Flash the update that's floating around this forum
Why update? Well, I have read the huge thread on google about the voice search bug and ... wait for it ... this OTA doesn't address it.
So, I wouldn't lose any sleep over it. It breaks tethering anyway.
By the way, although Samsung manufactured the hardware, as you know, it's purely managed by google. So if you have a beef, take it up with google, not Samsung. I've owned the SGSII and hated it. Returned to the Nexus S in a flash. It's so much better, IMO.
Phones are a very personal thing. If you have a hate for Samsung and the Nexus S is roped into that hate, 2.3.6 will do nothing for you. I'd recommend leaving Sammy for good and seek happiness elsewhere (where there are also issues and bugs...no phone is perfect).

ericshmerick said:
Ok, there is an update and yes it takes time for every IMEI to be loaded into Google's system for dispatch.
Your options are:
1. Force update by using checkin and hope it works
2. Flash the update that's floating around this forum
Why update? Well, I have read the huge thread on google about the voice search bug and ... wait for it ... this OTA doesn't address it.
So, I wouldn't lose any sleep over it. It breaks tethering anyway.
Click to expand...
Click to collapse
Then there is no reason to force an update. Not one. In fact it breaks more than it fixes. 12 more days of this and it goes back. I'm not going to go with the manufacturer route and I know that Google won't talk to me about it.
100 pages of the same issue in one post with many of them being told they are the first to report it tells me all I need to know.
By the way, although Samsung manufactured the hardware, as you know, it's purely managed by google. So if you have a beef, take it up with google, not Samsung. I've owned the SGSII and hated it. Returned to the Nexus S in a flash. It's so much better, IMO.
Click to expand...
Click to collapse
I'm pissed at Google for sure but Sammy isn't off the hook yet. Why the same code doesn't do this on other phones and also seems to infect Canadian phones more than others says to me there is more to this than just Google code. The original SGS was a disaster until they finally replaced the pb and I flashed it properly. Now it is fine but thought I would have a better time with the N. Three times back for warranty is a bad track record. And this one might be making a trip back too.
Phones are a very personal thing. If you have a hate for Samsung and the Nexus S is roped into that hate, 2.3.6 will do nothing for you. I'd recommend leaving Sammy for good and seek happiness elsewhere (where there are also issues and bugs...no phone is perfect).
Click to expand...
Click to collapse
yep, my personal opinion is that Samsung has too many issues to make up for what it does do well. And google has zero customer service, this isn't the only issue I have that the robot alone will never fix.
Anyway, I'm done with this topic. I'll wait to see if a definitive fix comes or not.

Fair enough, but I still don't understand your beef with not receiving the 2.3.6 OTA instantaneously. It takes days to roll out to every Nexus S in the world.
I'm just not sure why you are all upset that it didn't arrive the moment it hit the news. Can't you just wait a few days (less than 12 for sure) and install when it's pushed to you?

ericshmerick said:
Fair enough, but I still don't understand your beef with not receiving the 2.3.6 OTA instantaneously. It takes days to roll out to every Nexus S in the world.
I'm just not sure why you are all upset that it didn't arrive the moment it hit the news. Can't you just wait a few days (less than 12 for sure) and install when it's pushed to you?
Click to expand...
Click to collapse
whoa there sparky. I haven't complained one bit about an OTA being slow. Not one word. I asked about OTA and if it takes time to roll out. Actually I wasn't even terribly upset about the bug until I read that the updates won't fix it and I might be waiting a very long time. That thread that I've now found started in May.
Yes I can wait a few days but I expect to wait months like I did for the SGS to be fixed. THEN I'll be pissed off or rather I won't because I won't have the thing if it takes THAt long. A few days I can deal with.

3rdcoast said:
whoa there sparky. I haven't complained one bit about an OTA being slow. Not one word. I asked about OTA and if it takes time to roll out. Actually I wasn't even terribly upset about the bug until I read that the updates won't fix it and I might be waiting a very long time. That thread that I've now found started in May.
Yes I can wait a few days but I expect to wait months like I did for the SGS to be fixed. THEN I'll be pissed off or rather I won't because I won't have the thing if it takes THAt long. A few days I can deal with.
Click to expand...
Click to collapse
Sparky? No need to go there kiddo.
Anyway, I have bad news for you. 2.3.6 doesn't fix the voice search bug.
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=49e8ca84071d51a4&hl=en
By the way, it's a google managed phone, so you will get 2.3.6 soon. It's not like Samsung grabs the release, adds bloatware and jacks up the rom like they do with their managed phones (i.e. Galaxy S).
Any other Android phone you leave for the Nexus S will mean loooong wait times for official releases.
Good luck in your journey.

I thought you read the thread, it isn't very long. Others have said and I repeated the big news about 2.3.6 not fixing the problem and causing tethering issues and who knows what else. That's why the OTA is a moot point. I won't be flashing it anyway as it turns out. So I'll go wherever I want including buying phones like I've always done which means root and rom, I know all about carrier's and manufacturer's history. The N is looking like the same deal.
Now I'm really done. No need for a reply. goodnight.

I'll reply anyway and you will read it anyway.
I'm not sure what your purpose of this thread was. Yes I read it.
You asked if it takes time to receive the update. Many answered yes.
You then said you would wait a few days (posted today) and if it wasn't OTA'd, you'd go download it.
You then said you won't force an update and if you wanted it that bad you'd flash recovery.
You then expressed your disappointment with the Nexus S.
You mentioned your frustrations with a completely different Samsung phone, the Galaxy S (not the Nexus S).
You then said Samsung has too many issues to make up for anything it does well.
You then called out Google for having zero customer service and stated you will wait to see if there is a definitive fix for your issue.
Lastly, you said the OTA and flashing the ROM is a moot point and went to bed.
When I put all of this into a calculator, the result that's spat out is:
Get an iPhone. Android isn't for you.
(outside of this and re-reading your posts, I have no idea what you want out of this thread)

ericshmerick said:
(outside of this and re-reading your posts, I have no idea what you want out of this thread)
Click to expand...
Click to collapse
i'll read that much. now stfu, you aren't helping.
iphone, that's funny

Has Verizon Started Pushing Lollipop

Hey guys, has Verizon started pushing the official Lollipop for our M8's? Thanks!

pettigrew95 said:
Hey guys, has Verizon started pushing the official Lollipop for our M8's? Thanks!
Click to expand...
Click to collapse
Not yet..

If you follow this thread. You will know when it is pushed cause I post firmware rt away.
http://forum.xda-developers.com/showthread.php?t=2723159
[10-22][firmware][all stock img]all files have updated t0 4.4.4

I don't think there has even been so much as speculation about when it will be pushed out. Either it's still really far away or they are staying extremely quiet about it.

xsteven77x said:
I don't think there has even been so much as speculation about when it will be pushed out. Either it's still really far away or they are staying extremely quiet about it.
Click to expand...
Click to collapse
I know right? Even a Google search brings back nothing.. Would say it's weird but then again that's Verizon.
Save the Manuals!

I"am sure verizon is still trying to shove as much bloatware in it as possible, their goal is to make you never forget they are the largest carrier they do this by trying to lock you out of everything and make you pay them every dime they can squeeze. I heard last week that the at&t one is close but verizon does not care about its customers in the least.

5.1.1 OTA?

So today(5-15) I saw online that T-Mobile USA released the 5.1.1 OTA for there branded Galaxy S6/S6 Edge, so any info on when the Verizon branded version is coming out? I'm having multiply major bugs(wifi, memory, and lagging) across 3 different S6 devices(original device and 2 replacements) since launch day. Also, the Verizon Branded OTA that just came out brought me new bugs like with Google voice to text giving me 2 new bugs and making it unusable. Also, apps are freezing like crazy and ends up freezing the whole phone and when I try to lock the phone with the power button when an app is freezing it opens up the camera instead of locking the phone and most of the time I have to restart the phone when this happens and it happens quite often, but only started after the Verizon OTA. Also, from launch day(across all 3 devices) I been having memory issues with the phone, it tells me it has between 1GB-1.2GB of total memory on the phone and I only have 748MB total available with only very few apps on the phone at the moment, everything closed and all the bloatware gone off the phone. I herd that the Verizon OTA we just got was suppose to fix the memory issue, but apparently for me it did nothing at all with the memory on my phone. and lastly I'm having the major wifi bug a lot of us are having witch for me started on the 6th day after launch and never worked again even after I had 3 different devices and still the same thing is still ongoing, and in fact the Verizon OTA we just got made the wifi bug even worst then before.
So the 5.1.1 OTA is really needed for me to fix these ongoing and new bugs I'm having and after 2 months I'm getting sick and tired of waiting for patches to come out!

You probably should go into your system recovery and clear cache. That will probably help a majority of your bugs.

charlesvw9 said:
You probably should go into your system recovery and clear cache. That will probably help a majority of your bugs.
Click to expand...
Click to collapse
I already did that and nothing changed at all, and like I said I had 3 different devices and nothing changed at all. In fact the 3rd device I got which I still have was giving me problems from very first time I turned it on and during the initial setup as soon as I turned it on from the FedEx box and the keyboard was slow and not putting the letters I clicked in the box and to click next/skip, restart or power off I had to use my pointer finger and press multiple times and fast like a woodpecker would on a tree in order for those functions to respond, and before I can even finish the initial setup I had to already do a factory reset on the phone. Even typing right now in this box responding to you the phone is lagging just typing now.

Don't think Verizon has announced anything yet. The current G920VVRU1A0E2 works fine for me.

To help with keyboard lag - go into settings and make sure the proper language is intalled and updated. Have you tried different keyboards? Swiftkey?

krelvinaz said:
Don't think Verizon has announced anything yet. The current G920VVRU1A0E2 works fine for me.
Click to expand...
Click to collapse
Same here and I'm in no hurry to lose root.

krelvinaz said:
Don't think Verizon has announced anything yet. The current G920VVRU1A0E2 works fine for me.
Click to expand...
Click to collapse
Well 3 different phones since launch day have been giving me all different kinds of problems and never had a device with out a major problem in it and the new Verizon OTA that just came out in June made the phone even worst then before. The Build for the update is G920VVRU1A0E2, and in fact I even had problems getting the update on my phone because from launch day of the OTA-4days after it came out the OTA would not fully download and give me error code 503 and it wasn't until the 5th day that it worked and then when I finally got it installed on my phone it just brought more bugs to the phone like I talked about in the OP

bigj0110 said:
Well 3 different phones since launch day have been giving me all different kinds of problems and never had a device with out a major problem in it and the new Verizon OTA that just came out in June made the phone even worst then before. The Build for the update is G920VVRU1A0E2, and in fact I even had problems getting the update on my phone because from launch day of the OTA-4days after it came out the OTA would not fully download and give me error code 503 and it wasn't until the 5th day that it worked and then when I finally got it installed on my phone it just brought more bugs to the phone like I talked about in the OP
Click to expand...
Click to collapse
Have you tried using Odin to flash back to stock with the full tar file instead of the update? If not go here and give it a shot. If you use the OE2 one you will have to factory data reset to wipe your phone clean either after or before you flash.

charlesvw9 said:
To help with keyboard lag - go into settings and make sure the proper language is intalled and updated. Have you tried different keyboards? Swiftkey?
Click to expand...
Click to collapse
yea I tired that, but this started as soon as I turned on my phone for the very 1st time trying to do the initial set up, plus like I said even pressing next/skip, power off or reset in the initial setup was a hassle. I had to take my pointer finger and point it down and press fast and many times like a woodpecker in order for the buttons functions to work and I could not even finish the initial setup and had to already do a factory reset before the initial setup was even finished on the 3rd device I have now. The phone is so bad that even clicking the home button some of the apps, Google search and weather is not on screen right away and takes second or 2 to show up, its lagging to show up.

Misterxtc said:
Have you tried using Odin to flash back to stock with the full tar file instead of the update? If not go here and give it a shot. If you use the OE2 one you will have to factory data reset to wipe your phone clean either after or before you flash.
Click to expand...
Click to collapse
Thanks, but I already did that last night and still the same thing nothing different at all changed for me, it was a complete waste of time!

bigj0110 said:
Thanks, but I already did that last night and still the same thing nothing different at all changed for me, it was a complete waste of time!
Click to expand...
Click to collapse
That stinks, hopefully the next update will fix things for you. Mine has been running fine for the most part.

Misterxtc said:
That stinks, hopefully the next update will fix things for you. Mine has been running fine for the most part.
Click to expand...
Click to collapse
3 different devices and still the same exact major things plus new things on each device are going on with the phone. Switching out the device should fix it all, but I guess this is not the case here. Plus about the wifi issues I'm in a XDA forum 13 pages long about the phones wifi not working(I know it says edge, but it's the same problems with the S6 and S6 edge so no difference)
http://forum.xda-developers.com/galaxy-s6-edge/help/wifi-dropping-t3079504

I would not be surprised to see that the new upgrade to lollipop was to foil or prevent root. Kind of like the s4. screwed up everything now I have no root.
THANKS SAMSUNG !!!!!!

traco1 said:
I would not be surprised to see that the new upgrade to lollipop was to foil or prevent root. Kind of like the s4. screwed up everything now I have no root.
THANKS SAMSUNG !!!!!!
Click to expand...
Click to collapse
They already said that the new update(5.1.1) is taking away root

My 1st phone which arrived on Sat came with G920VVRU1A0E2 out of the box.
Other than normal setups, and uninstalling Google Play Services and Google Play it has not had any problems.
Perhaps you should go into a store and show them how it is not working?

traco1 said:
I would not be surprised to see that the new upgrade to lollipop was to foil or prevent root. Kind of like the s4. screwed up everything now I have no root.
THANKS SAMSUNG !!!!!!
Click to expand...
Click to collapse
Ya you're thanking the wrong company here. You need to thank Verizon...

krelvinaz said:
My 1st phone which arrived on Sat came with G920VVRU1A0E2 out of the box.
Other than normal setups, and uninstalling Google Play Services and Google Play it has not had any problems.
Perhaps you should go into a store and show them how it is not working?
Click to expand...
Click to collapse
I did on launch day, I went back to the same corporate store a few hours later and got into a fight with the sales rep who sold me the phone a few hours earlier and the store GM because they were Ignorant because my phone was hot as fuc k at 90F and hotter and they said nothing was wrong. On top of that they even lied to me about having the edge devices in stock on launch day and even pulled out the normal S6 trying to trick me and it was not until I said something did he say oh this is not an edge and then said there was no edge's in stock, but while I was waiting in line I asked him and 2 other reps and they all said they had the white 64GB edge in stock. They rather lie to there customers to make a sale then tell the truth(at least this corporate store location), and then when you have problems with the phone they don't care to help you at all. Even 611 said this was very wrong and made a complaint on mine and 611's behalf on the corporate store and the sales rep.

Misterxtc said:
Have you tried using Odin to flash back to stock with the full tar file instead of the update? If not go here and give it a shot. If you use the OE2 one you will have to factory data reset to wipe your phone clean either after or before you flash.
Click to expand...
Click to collapse
Here is an update, as of recently my phone is getting really really hot and temperatures of 120F+ and even Verizon technical support saw that through their diagnostic system as it was actually on those temperatures at that very moment when they were looking. Also, from me just being tech savvy and Verizon technical support confirming it as well this phone is also supposed to have a safeguard in the phone and if it gets too hot the device is upposed to power off on its own, but apparently the safeguard is not working because when the phone gets very hot the battery starts flashing and in the middle of the screen it tells me the phone is very hot and it only lets me click OK. If I'm charging the phone the battery flashes and say the same thing but just adds unable to charge, & I can unplug the charger and immediately plug it back in to the phone and it will start charging again and then a few minutes later it will give me the same message. When it's doing that its not supposed to tell me anything it's supposed to just shut off and its not doing so.
So there overheating policy states that I have to bring my phone too a corporate store and they're going to replace the device right on spot. So Sunday I went to the corporate store to do that, but for some reason their system wouldn't allow them to process this because it didn't have an option to do it and the general manager and the store representative we're booth trying together for at least 45 minutes. They ultimately ended up just sending me a replacement device via Fedex to my house and when the phone arrives today(7-2) I have to bring the overheating device that I currently have to the store so they can do what they need to do to send it back because by law I'm not allowed to send an overheating device back. Verizon corporate store processed my order on Sunday and I was supposed to get the device on Tuesday but I'm getting it today due to inclement weather at the FedEx Memphis Tennessee hub and so Fedex at the Memphis Tennessee hub was at a complete standstill and my package was part of it.
Once I get my 4th replacement device and start using it for a while I will let you know how it's working