• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

4.0.3 release date?

Patriot123 said:
Like I've said, if people REALLY want it, as in the sense that they're planning on using it, they can get it relatively easy. Verizon just didn't incorporate with the phone like people wanted them to. They're going to make it as bare-minimum of a Google phone as they can and as much of a Verizon phone as they can, but the fact that it is the GNex makes it super easy and super simple to work around.
Click to expand...

Yep, its called isis, they been working on it for a while but no word on when its going marketed.
 
adrynalyne said:
Its been officially released to AOSP. Galaxy Nexus yakju and mysid are officially supported by AOSP. So thats official enough for me :D
Click to expand...

That's why I specified "source". :D

repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.3
remote: Counting objects: 93, done
remote: Finding sources: 100% (80/80)
remote: Getting sizes: 100% (33/33)
remote: Compressing objects: 100% (20/20)
remote: Total 80 (delta 24), reused 80 (delta 24)
Unpacking objects: 100% (80/80), done.
From https://android.googlesource.com/platform/manifest
* [new branch] android-2.2.3_r1 -> origin/android-2.2.3_r1
* [new branch] android-2.2.3_r2 -> origin/android-2.2.3_r2
* [new branch] android-4.0.1_r1.1 -> origin/android-4.0.1_r1.1
* [new branch] android-4.0.1_r1.2 -> origin/android-4.0.1_r1.2
* [new branch] android-4.0.2_r1 -> origin/android-4.0.2_r1
* [new branch] android-4.0.3_r1 -> origin/android-4.0.3_r1
* [new branch] android-cts-2.2_r8 -> origin/android-cts-2.2_r8
* [new branch] android-cts-2.3_r10 -> origin/android-cts-2.3_r10
* [new branch] android-cts-2.3_r11 -> origin/android-cts-2.3_r11
* [new branch] android-cts-4.0_r1 -> origin/android-cts-4.0_r1
* [new branch] android-cts-verifier-4.0_r1 -> origin/android-cts-verifier-4.0_r1
* [new branch] android-sdk-4.0.3-tools_r1 -> origin/android-sdk-4.0.3-tools_r1
* [new branch] android-sdk-4.0.3_r1 -> origin/android-sdk-4.0.3_r1
* [new branch] android-sdk-adt_r16.0.1 -> origin/android-sdk-adt_r16.0.1
8e6ad14..87540a2 ics-mr0 -> origin/ics-mr0
* [new branch] ics-mr1 -> origin/ics-mr1
5f8c416..3b6bfd8 master -> origin/master
* [new branch] tradefed -> origin/tradefed
* [new tag] android-2.2.3_r1 -> android-2.2.3_r1
* [new tag] android-2.2.3_r2 -> android-2.2.3_r2
* [new tag] android-4.0.1_r1.1 -> android-4.0.1_r1.1
* [new tag] android-4.0.1_r1.2 -> android-4.0.1_r1.2
* [new tag] android-4.0.2_r1 -> android-4.0.2_r1
* [new tag] android-4.0.3_r1 -> android-4.0.3_r1
* [new tag] android-cts-2.2_r8 -> android-cts-2.2_r8
* [new tag] android-cts-2.3_r10 -> android-cts-2.3_r10
* [new tag] android-cts-2.3_r11 -> android-cts-2.3_r11
* [new tag] android-cts-4.0_r1 -> android-cts-4.0_r1
* [new tag] android-cts-verifier-4.0_r1 -> android-cts-verifier-4.0_r1
* [new tag] android-sdk-4.0.3-tools_r1 -> android-sdk-4.0.3-tools_r1
* [new tag] android-sdk-4.0.3_r1 -> android-sdk-4.0.3_r1
* [new tag] android-sdk-adt_r16.0.1 -> android-sdk-adt_r16.0.1


I think he was talking about the OTA, aka the pre-compiled official easy release for the masses.
 
Patriot123 said:
Anyone have an idea when Google's gonna start rolling out 4.0.3 to the Verizon GNex?
Click to expand...

I don't have an answer, and you won't get one out of Verizon (and if you do it will be about as accurate as all the "confirmed" release dates we got for the Nexus), but just so you know it's not up to Google, it's up to Verizon.

Google already has 4.0.3 done, has been for a while. It's up to Verizon to "OK" it and start the push--which they will do when they're darn good and ready and forget trying to get any info from them.

What's taking Verizon so long? Your guess is as good as mine:
- Holding it up for a possible inclusion of new radio software?
- It's big and they don't think their data network can handle it yet due to all the new users from the Holidays?
- Politics with software like Google Wallet or Google's Majel (Siri-competitor)?
- This is just how long it takes to work an upgrade through their red tape?
- There's another upgrade coming and they've decided to just hold off and roll them together?
 
If aosp 4.0.3 is already out, and you can dl it and compile it for your phone... but it hasnt been officially available to users... does that mean the aosp on Google's site isnt thefinal version/ build? So Google is still tweaking it? Does that mean that aosp 4.0.3 is still being updated? So if i dl and compile it today and then again next week or some other later time, it will be different?

is this the typical way it goes for android releases?
 
There are many branches of Android. AOSP is the only public one. For a retail build, it comes from a different branch that also builds closed source modules not available in AOSP. Ever wondered why Google Apps includes Calendar, even though Calendar is on AOSP? Its because there are closed source modules throughout Android (like google calendar sync). Retail also has additional testing and features, such as radios, and bootloaders. None of this comes into play with AOSP.

So will the oem OTA be the same version as on AOSP? Not entirely, because its a different branch. If they stay with 4.0.3, however, it will be the same in the main meat of the OS.

If there are bugs found in 4.0.3, they are also pushed to AOSP. To aspiring devs out there: Don't think a version is updated only once, and keep your repos updated often.
 
dhworph said:
If aosp 4.0.3 is already out, and you can dl it and compile it for your phone... but it hasnt been officially available to users... does that mean the aosp on Google's site isnt thefinal version/ build? So Google is still tweaking it? Does that mean that aosp 4.0.3 is still being updated? So if i dl and compile it today and then again next week or some other later time, it will be different?

is this the typical way it goes for android releases?
Click to expand...

No exactly, Google is not tweaking it, Verizon is tweaking it. Adding their customizations and bloatware, or radio firmware, or ignoring it or whatever it is they do in their ivory tower.

Google has a stable complete build, 4.0.3. It's "gone gold" so to speak, if google makes any other changes it would be a new version number.
 
ok,, I think I see.. if you look on the android dev page they have different revisions of 4.0.3 (currently revision 2). So I guess it's possible that other maintenance releases can happen before it is officially sent out to mobile devices.
 
Well, yes and no. Verizon may ask Google to make tweaks but does not make them, themselves. Google can and will make changes to it, but it will not be new features. It will be bugfixes and they will in turn be pushed to aosp when they are approved. New features will mean new build number. New bugfixes will not.

When I say features, I mean non-bug related changes.
 
That's kinda weird... why would the Xoom get it before the 'flagship' of ICS?

*edit: ok, I read a few other forums and it seems like the xoom is wifi only and so updating a phone sounds like its a bit more complicated... and plus ICS for xoom is starting with 4.0.3, 4.0.x<3 was never meant for anything other than GNex maybe...
 
dhworph said:
That's kinda weird... why would the Xoom get it before the 'flagship' of ICS?

*edit: ok, I read a few other forums and it seems like the xoom is wifi only and so updating a phone sounds like its a bit more complicated... and plus ICS for xoom is starting with 4.0.3, 4.0.x&lt;3 was never meant for anything other than GNex maybe...
Click to expand...


Correct the base version of ICS is really 4.0.3. My Prime was updated to it as well
 
dhworph said:
That's kinda weird... why would the Xoom get it before the 'flagship' of ICS?

*edit: ok, I read a few other forums and it seems like the xoom is wifi only and so updating a phone sounds like its a bit more complicated... and plus ICS for xoom is starting with 4.0.3, 4.0.x<3 was never meant for anything other than GNex maybe...
Click to expand...


Simple answer. Carriers are testing it right now.

One of the first 4G handsets for LTE testing apparently looked nothing like what the retail version looked like. I'm SURE that we have to wait for VZW to test, review their testing results, and then finally give approval or denial to SamGoog.

AOSP is one thing, proprietary drivers (like binaries for radios) is another thing. Cows are one more thing. :D:D
 
You must log in or register to reply here.
Back
Top Bottom