ICS Update for the Nexus S 4G Discussion Thread

[Ryuuie]

Where did you get this info?

Read back a few pages if you want more information, but it comes from Sprint.

To add to what plee82 posted (he JUST asked JBQ actually...I just noticed that, hah cool)

https://twitter.com/#!/jbqueru/status/189441940633300992

Also, it's probably due to the CDMA files needed as they're not open-source. The other factory images don't need those.

 

[vincentallen2]

Does anyone else feel like they just released the update to a small amount of people just so it can shutup the complainers?

I'm not sure why, but I feel like the update isn't 100% ready yet, and this approval thing makes my theory seem like it's right.

How are the people who actually received the OTA reporting? Any lag or stability issues?

 

[smcolbert]

It's a roll out. Be patient. It"s coming.

Sent from my Nexus S 4G using Tapatalk

 

[siczek.p]

OK, so jerked around again, huh?
Its astounding how poor a job is being done with this update.

 

[smcolbert]

Nobody's being jerked around. It's being rolled out over 3 weeks.

Sent from my Nexus S 4G using Tapatalk

 

[Ryuuie]

Does anyone else feel like they just released the update to a small amount of people just so it can shutup the complainers?

I'm not sure why, but I feel like the update isn't 100% ready yet, and this approval thing makes my theory seem like it's right.

How are the people who actually received the OTA reporting? Any lag or stability issues?

If the update wasn't 100% ready, it wouldn't be on the other Nexus phones.

Not many ARE reporting because not many will usually see a need to. Not everyone is letting this ruin their day or anything.

The only time you see reports or reviews are if something breaks, rarely do you see a "OMG THIS IS THE BEST THING EVER!" now a days.

JBQ stated on Twitter (asked by our very own plee82, in fact) that Google's updates ALWAYS start slow to check for feedback but then become more widespread once they are satisfied that nothing major is breaking like it did with 4.0.3.

https://twitter.com/#!/jbqueru/status/189447590012649472

Sure, it got to other Nexus devices faster, but this is the first time it's officially on Sprint. Sprint doesn't want it to screw up and Google doesn't want it to screw up either. It's better to take your time and do it right than to rush and break...ask ASUS and the early Transformer Prime adopters about that sometime.

In other news, I wish my sig wasn't so long. But it's to help people sooo......

 

[mattg67]

Woot official images are up!

 

[MacGuyInNC]

Woot official images are up!

And you're going to provide us the link... Right?

 

[mattg67]

https://code.google.com/android/nexus/images.html

 

[kuoirad]

https://code.google.com/android/nexus/images.html#sojus

This is not the one most of us have been waiting for - this is the factory restore image that wipes your phone.

 

[tukarjabi]

Factory Images for Nexus Devices - Google Support for Nexus Phones and Flagship Devices - Google Code

 

[Ryuuie]

Yep, the factory images are up!

However:

Going with its matching OTA, the factory image of 4.0.4 for Nexus S 4G is available at the usual location https://code.google.com/android/nexus/images.html

This is meant to be used by people who built and flashed their own custom version of AOSP and wish to return to the factory state. If you're currently running an official retail build, I simply recommend that you wait for the OTA.

Because this isn't actually my job, I don't know the exact schedule for this or any other OTA. Thanks for not asking about those.

Specifically about Nexus S 4G, there's a known bug in the bootloader, where it reports the wrong radio version number after flashing the radio, which then doesn't get recognized by fastboot. The workaround is to boot into whatever version of Android is on your device, and then return to fastboot and restart the flashing sequence.

Soure: https://plus.google.com/112218872649456413744/posts/TmDuWd3kcAR

https://code.google.com/android/nexus/images.html

 

[Paul627g]

https://code.google.com/android/nexus/images.html#sojus

This is not the one most of us have been waiting for - this is the factory restore image that wipes your phone.

Cool. Yes it's true it would wipe your device but using fast boot you can give your self the ICS update.

 

[Ryuuie]

Cool. Yes it's true it would wipe your device but using fast boot you can give your self the ICS update.

(You can ignore the PM I shot you about this)

Would there be a fix for the bug that JBQ mentioned?

 

[kuoirad]

Would there be a fix for the bug that JBQ mentioned?

I just put a comment on his g+ post asking how those of us opting for the OTA would handle this - if it's a simple re-application of the OTA, or...

 

[Paul627g]

I'm looking into the workaround... This should be easily done within a fastboot custom script. Also talking to someone about a possible "update.zip" for use from stock recovery

 

[Ryuuie]

I asked JBQ about the 10 - 21 time that Google gave Sprint:

Sascha Pr?ter - +Ryuuie Ryuu 10-14 days is usually a realistic timeframe assuming that no issues bubble up that require pausing/halting the roll out.
(Jean-Baptise Queru and myself +1'd this)

Jean-Baptiste Queru - Each OTA follows slightly different schedules. I don't follow the plans with great details, that'd take too much of my time. That's why I don't know for sure, sorry.

Sascha seems to work at Google as well, so we can take that as official too if you want.

Also he had this to say about sideloading the OTA:

Jean-Baptiste Queru - BTW, joke aside, the code that side-loads OTA packages might not be such a great area for contributions at the moment, as I know it's been modified in Google's internal source tree (mostly, the classic approach of loading via the SD card doesn't work so well on devices without an SD card...)

Ryuuie Ryuu - +Jean-Baptiste Queru So we shouldn't try the "update.zip" method for the OTA and just wait for our phones to update on its own?

Jean-Baptiste Queru - +Ryuuie Ryuu - Sideloading OTA packages isn't meant to be used by end-users, for several reasons. I recommend just waiting for the OTA. It's the most tested path by a very long shot, and it's the one on which it's possible to hit the proverbial "big red button" the fastest in case anything appears to go wrong.

Going from this, it's safe to say the OTA is tested more than the factory image that was just released and probably has bugs fixed that the factory image may not. Not to mention Sprint themselves tested it as well as Google to make 99.9% (never 100%, things can happen) SURE it works on not only our phones but also Sprint's network.

So there you have it, April 15th - 21st is a likely timeframe to see the OTA on all Nexus S 4G phones (but April 15th - 18th is even more realistic, according to one of Google's employees).

We don't have long to wait. It's pretty much either this coming Sunday or next Wednesday that all phones should have the update. Or you can use the factory image, but I think I'll personally wait this time around.

 

[tommy_2]

Is the that korey from xda released the Assamese as ota?

 

[tommy_2]

Same as ota? . My mistake.

 

[kraven867]

I just got the OTA a few minutes ago, in Minnesota. Installing it right now