Should I try .246?

[SamuriHL]

Dave is starting to lose the bet. The FAQ is becoming exactly what I said it was going to....completely ignored.

 

[altspeed]

In the house you earn your place at the table or you don't get to eat, nuff said

 

[droidxd00d]

Cant beat this ^_^

<img src="http://www.droidforums.net/forum/attachment.php?attachmentid=56302"/>

<img src="http://www.droidforums.net/forum/attachment.php?attachmentid=56303"/>

<img src="http://www.droidforums.net/forum/attachment.php?attachmentid=56304"/>

<img src="http://www.droidforums.net/forum/attachment.php?attachmentid=56305"/>

daaaaaaaaang....that antutu score is ridiculous lol. how do you over clock the bionic? kernel modification?

 

[podspi]

For the D4 those who updated to the leaks were able to get back on the upgrade path but were not able to downgrade (just like these Bionic leaks). I would be very surprised if the same did not apply to the Bionic. That being said, with kexec does being on the upgrade path matter?

I would argue no, since I don't care about the VZW firmware and know I can still restore the phone if something goes wrong (though not as easy as a simple fastboot).

 

[sargentmajord]

daaaaaaaaang....that antutu score is ridiculous lol. how do you over clock the bionic? kernel modification?

Google tweakerz oc

 

[jayrod]

Dave is starting to lose the bet. The FAQ is becoming exactly what I said it was going to....completely ignored.

You wrote an FAQ?

Sent from my. 246 ICS leaked BIONIC

 

[devils3023]

Dave is starting to lose the bet. The FAQ is becoming exactly what I said it was going to....completely ignored.

No it's not. I must've read it like 10 times along with the main thread as well!! Perhaps that's why both my installs (244 and 246) went flawlessly though .

 

[GlueFactoryBJJ]

Dave is starting to lose the bet. The FAQ is becoming exactly what I said it was going to....completely ignored.

OK, I stand corrected, even though the info appears to be THREE WHOLE DAYS OLD! Sorry. I read the HOB OP and some of the early posts (before realizing there were 2500+ posts) and the last couple pages. I didn't see the answer there and saw this thread, so I posted here figuring that you may not be able to keep up with all of them.

I've now read BOTH of the OP (HOB and HOB FAQ) and the second question regarding reasons for going to .246 vs .232 (aside from battery and potentially not being able to get back on the OTA path) still stands.

Thanks for your help...

Scott

 

[jayrod]

I've now read BOTH of the OP (HOB and HOB FAQ) and the second question regarding reasons for going to .246 vs .232 (aside from battery and potentially not being able to get back on the OTA path) still stands.

Thanks for your help...

Scott

To be honest,it's up to you. I ran .232 for a bit and noticed a big difference in how the phone responded. I finally took the plunge to .244 then .246 a few days later. From what I understood about .232, there was a bunch of code that wasn't streamlined (Please don't shoot me if I worded that wrong)
.246 so far has been very stable, but because it's only been running less than 24 hours I haven't seen the battery results that some others have. Hoping to see that after a few days once it's all settled down.
All said,.232 will give you a taste of what ICS has to offer and since you can .fzx back to .905 it is much safer, just in case disaster strikes.

 

[altspeed]

took about 4 charge cycles for mine to start hitting 20-22 hours on moderate use after I went to 244, still not on 246 because I can see no reason, I don't have the charger/keyboard bug like a few people

 

[jayrod]

took about 4 charge cycles for mine to start hitting 20-22 hours on moderate use after I went to 244, still not on 246 because I can see no reason, I don't have the charger/keyboard bug like a few people

4 cycles!?!? Dang. I didn't notice the keyboard issue, but I only ran it for a couple of days before going to .246.
I am still trying to get a handle on how to maximize battery and still use my phone. I tried the smartactions to kill data,GPS,Wifi, etc. when screen off when I was on .232 and started to do it again on .244 but honestly, even though there is only a delay of a few seconds to get data back up, it seemed like it caused issues when a rule overlapped another rule and it ended up taking longer..it seems like it would eat more battery that way.

 

[GlueFactoryBJJ]

Thanks for the info. Sounds like .232 will be enough. I'm dying here with the data drops (and reboots necessary to get it back most of the time) and with the delay of the OTA I've decided to see if ICS will really solve this problem (as advertised... at least elsewhere). .905 was a bit better than .902, but by no means a solution to the problem.

Has anyone noticed any differences between .905 and .232 and/or .246 regarding the data drops?

Of course, I really like ICS (at least the times I've used it at the VZW stores) and I'm looking forward to exploring that also.

Scott

 

[altspeed]

it WILL fix your data problems, forget them, new radios, new kernel, etc

Biggest 232-/235+ differences are a bunch of dev debug code in the 232 and earlier and of course the new security model on the 235 and later

 

[GlueFactoryBJJ]

it WILL fix your data problems, forget them, new radios, new kernel, etc

Biggest 232-/235+ differences are a bunch of dev debug code in the 232 and earlier and of course the new security model on the 235 and later

Don't tease me now... LOL! Alright time to HOB (.232)!

Scott

 

[SamuriHL]

Make sure you're using 7.0.