Tehouse,

I have read on a couple of message boards about a leak from a europe tech site that says it will come sometime in March. I do know the 4.04 version that was leaked on a picture with sprint nexus s 4g had a few bugs like WIMAX and WIFI connectivity which are pretty huge. Im just as fustrated as most people with why th hold up.

E

Just chatted with Sprint, at first the representative said that the update was rolling out and then she said that it wasn't that there is no date. I also saw a post in some forum, that said that Nesus s 4g was supposed to update in march. I hope it comes in march. I am running a ROM with 4.0.3 already and I love ICS. I hope they release the update soon.

I got tired of waiting and did a manual install to one of my Nexus S 4G's I guess I will wait for the OTA for the other to compare. From what I can say based on my own personal experience with ICS 4.0.4 on the Nexus S 4G is the user interface is very different, just answering the phone is different and when in a call to bring up features like swapping between callers or looking up contacts. This will be a little of a user learning experience.

Where is your proof?

Here are some of your other wild statements:

"The leaked Sprint Android 4.0.4 build has a significant amount of major bugs that has caused many Nexus S 4G phones to be bricked. This is true even when the Odin instructions are followed to the letter. It didn't happen to me but it has been happening to others. So far more than 60% of phones that were flashed with this unstable IMM26 build have been bricked and had to be sent in for out of warranty repair."

60 percent of phones? Really? Where is the proof of this, as I am on XDA (where 4.0.4 was leaked) all the time, and have not seen one reported case of bricking with either the odin method or just flashing with cwm.

"Samsung couldn't get Android to work on the Captivate at all which uses the same CPU as the Nexus S 4G. They ran in to a serious bug that would cause the phone to power off after putting it to sleep. The problem would get progressively worse over time eventually getting so bad that the power off would occur within 2-3 minutes of the phone going to sleep. To this very day Samsung has never figured out exactly what the problem was and has absolutely no idea how to fix it."

Where is your proof of this? How would you even know this?

When are carriers like going to learn that OTA updates are important to customers? If they spent a fraction of the time they spend on "value add" ROMs and programs that we don't want or need on OTA updates, I think we would be pretty happy customers. Release the official update already.

How would I know about the random power off issue on the Captivate? I'm a former AT&T customer that had a Samsung Captivate. The replacement that AT&T's device warranty center gave me also had the exact same problem. This was a very widespread issue. over 90% of Captivate phones had this problem. As for the issue with the leaked IMM26 build bricking NS4G phones, that's why the thread was locked. Also, the leaked IMM26 build from the OP was not a flashable CWM zip. The three files inside the original zip file absolutely had to be flashed with Odin or Fastboot.

Maybe I'm jaded, but I have so little faith in Google/Sprint at this point. I don't see us getting Ice Cream Sandwich before March. We'll be lucky if we get it before Sprint launches their Galaxy Nexus.

So your proof on how you have inside information on how "Samsung couldn't get Android to work on the Captivate" and that "over 90% of Captivate phones had this problem" is that you had 2 Captivates that did not work? That's all you got?

And as for the leaked IMM26 build, like W4tch3r07 states the thread was closed as per the OP request. Not because of bricking problems, which were few to none. And yes there were cwm flashable zips the next day after the release. I flashed one of them. Didn't brick my phone, just as the odin flash I did the day before didn't brick my phone either.

So as they say techguy379, the proof is in the pudding. And it looks like you have no pudding to share with us. How sad.