sargentmajord
Silver Member
Imprezive said:
.232 is the last ics leak that is fxzable
DroidForums.net | Android Forum & News
This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
new ics leak again 6.7.239
- Thread starter sargentmajord
- Start date
.232 is the last ics leak that is fxzable
LOL well nothing about the D4 OTA was conventional, so maybe they'll skip testing completely for the Bionic build LOL
Just judging by history of other Moto ICS releases, that's all. For example, the D4 release. Leaked on the 28th of July, not pushed out to soak/ota (whatever the hell that was) until 8/13. 238 was leaked on the 2nd of August. If it really takes 3 weeks between the time when a build shows up on cheesecake to the time it's pushed for soak/ota, well, do the math. It doesn't bode well for us getting it before the end of August/September if there really is going to be another build.
And what in the Bionic's history has been conventional?
So, maybe they'll do the same for us. Who knows. I just want us to hit OTA so we can start griping that the S3 has JB and we don't. sargentmajord
Silver Member
Tonik said:
The average time to create an update is 2 to 3 weeks but minor improvements on current leak is 1 week with a full recompiled update the system version goes up by increments of 10 minor bug fixes an coding to an existing leak system version goes up in increments of single digits ie. 230 231 232
That being said, given that 6.7.239 does exist (although only as an engineering build) does that mean that .238 won't be the OTA, but something after that?
It doesn't mean anything other than a build not meant for us.
sargentmajord
Silver Member
SamuriHL said:
Correct ^^^^^^^
nitephlight
New Member
If they really didn't want us to have these (or test thoroughly for them albeit at our own risk) they'd just release engie builds go home nothing to see but bricks lol. AFAIK , Verizon has no say over builds "stolen" from moto servers, but they can and W I L L delay OTAs till they have (or generous enough to spare...)the resources to support the build. Sometimes they need it out strategically before Motorola is ready...ahem razr...
Ok i have a question I'm a noob at this i flashed 232 wiped cache did all the things I've read to do. Now i get random notification tones also i reinstalledall my apps they worked for awhile now some have stopped working correctly I've uninstalled then and reinstalled them to no avail. Amy thought on how too stop the random tones and fix the apps.oh ive already did a factory reset didn't work. Thanks for any help you can give me.
Well, the thunderbolt is an HTC phone and has absolutely no relation to the bionic in any way other than they both run android. It's like comparing an apple to mars.
Next, how do you propose you install an update that wasn't designed for your phone? You could just as easily ask why can't we install a razr update on our bionic. Or why can't we upgrade from 232 to 238.
The answer is quite simple. Updates are designed to *PATCH* the system they were DESIGNED to update. All the ICS builds are designed to update 5.9.905. An engineering update is designed to update an engineering version of 5.9.905. Completely different bootloader. Completely different everything. When the update does a system check, it quickly fails the assertion that checks to make sure it's updating the system it was designed to. And no, you can't just go change it. The updates are signed. Even if you could, running an update on a system that it's not designed for will randomly patch files it wasn't meant to patch. Leaving you with a phone that is completely and totally bricked. This is why the assertions are done in the first place. To prevent the update from screwing up your phone...