Wireless Moot

[BIONICPREDATOR]

So guys my source is finally going to tell me whats going on tomorrow yeahhh ^_^

Sent from my 2.106 ghz quadrant score 5680 .247 Droid Bionic using Droid Forums

Can't wait!

Sent from my DROID BIONIC using Droid Forums

 

[BIONICPREDATOR]

Thanks for the advice, I will try it and see how it goes, by the way any more news on our ICS OTA for our Bionic, I keep seeing 30-40 more pages to read through and haven't had the time lately

Sent from my DROID BIONIC using Droid Forums

What's the name of the calibration app you use?

Sent from my DROID BIONIC using Droid Forums

 

[unbesorgt]

Thats done in recovery?

I believe i did that when i used HoB to install 247

Yeah, you can clear your cache partition from stock recovery. Dalvik cache however, I believe you have to be rooted and running a custom recovery like CWM. If you're not already rooted I wouldn't do it just for this.

BTW have you tried just rebooting your phone? Sometimes it's as simple as that.

 

[raidermc]

Yeah, you can clear your cache partition from stock recovery. Dalvik cache however, I believe you have to be rooted and running a custom recovery like CWM. If you're not already rooted I wouldn't do it just for this.

BTW have you tried just rebooting your phone? Sometimes it's as simple as that.

I am rooted.

CWM in google play?

 

[unbesorgt]

I am rooted.

CWM in google play?

Bionic Bootstrap. Better yet, courtesy of Samuri upthread, here's touch recovery for the Bionic. My new favorite.

 

[LaurelRaven]

Three scenarios.

1) Moto releases ICS. Most likely build 247. From there, we upgrade to JB. The most likely scenario.
2) Moto ditches 11 builds of ICS and goes to JB directly on top of 905. There is almost a 0 chance of this happening.
3) Moto pushes a patch to 905 that will allow JB to be installed on top of GB. This is the one you should be worried about.

Scenario 1...no problem. We're all covered. Scenario 2....not as big of an issue even with new security. Higher security means I can push it with the HoB so not a problem. Scenario 3 is the one that'd screw us. Unless they pushed higher security with, let's say 906. If it's the same security as 905 and they pushed another GB build, then those on 235+ are screwed for quite some time. Not a likely scenario, but, if they want to abandon ICS for JB that's the likely way it'd go down. And it'd be ugly if it did.

I know I'm replying to an "ancient" (few hours old) post, but...

My two cents, after everything they've already gone through, they aren't going to scrap it to do that. Unless I've missed my mark, that would actually be harder than just pushing ICS 247 and proceeding, both from a technical standpoint (they would basically be starting over to a point) and a PR standpoint (how badly would it hurt their image to delay again when it's known there is a fix ready to go?).

My two cents...I think you're right in that option one is what they will do. Smart money, on both sides of the bet.

Sent from my Nexus 7

 

[jayrod]

Omg whats with u guys an bacon in the last 6300 posts -_-

Sent from my 2.106 ghz quadrant score 5680 .247 Droid Bionic using Droid Forums

I know...it's crazy!

View attachment 57007

 

[GiovanniTheToker]

Hey Sam, or anyone that knows how (or the answer), does the HoB root .247? And if so, why won't it root mine? It jus stays on the "daemon not running. starting it now. daemon started successfully". How long should it stay on that screen? Lol.

 

[hAHAha Halo]

I would download 247.. But I remember when 242 was expected to be the final build, and here we are on 247 believing its going to be the final build. I'd *like* to believe 247 is final, but if it isn't, it'd be too much work for me to get back on the upgrade path.

Bionic 905

 

[raidermc]

Bionic Bootstrap. Better yet, courtesy of Samuri upthread, here's touch recovery for the Bionic. My new favorite.

I did a cache wipe in recovery and ran the quad test and came up with 1200 I/O.
Out of all the scores thats the lowest.

I did not see the clear dalvic option so i didnt perform that operation.

If i get that number up to where every one else is up to this phone will have some impressive scores

 

[Bfp]

Is It Wednesday yet?

 

[SamuriHL]

I would download 247.. But I remember when 242 was expected to be the final build, and here we are on 247 believing its going to be the final build. I'd *like* to believe 247 is final, but if it isn't, it'd be too much work for me to get back on the upgrade path.

Bionic 905

Suit yourself. I'm not sure what you consider "too much work". I've made it about as drop dead simple as it can possibly be. If a new build comes out, you download the HoB update installer that installs support for it or make a ### directory that corresponds to the update, drop the update zip into it, and run the HoB. 30 minutes later you're on the new version with no data loss. I'm not sure where the work is?

 

[Soocold]

Hey Sam, or anyone that knows how (or the answer), does the HoB root .247? And if so, why won't it root mine? It jus stays on the "daemon not running. starting it now. daemon started successfully". How long should it stay on that screen? Lol.

You need to select the options O'you're phone that hob tells you too. It does root that how we've all done it.

I did a cache wipe in recovery and ran the quad test and came up with 1200 I/O.
Out of all the scores thats the lowest.

I did not see the clear dalvic option so i didnt perform that operation.

If i get that number up to where every one else is up to this phone will have some impressive scores

To clear dalvik, go into the advanced option.


ICS Droid Bionic
.247 courtesy of HoB
OC @ 1.333Ghz

 

[SamuriHL]

Hey Sam, or anyone that knows how (or the answer), does the HoB root .247? And if so, why won't it root mine? It jus stays on the "daemon not running. starting it now. daemon started successfully". How long should it stay on that screen? Lol.

Covered in the faq.

 

[raidermc]

Bionic Bootstrap. Better yet, courtesy of Samuri upthread, here's touch recovery for the Bionic. My new favorite.

It seems to take longer on database writes in the I/O test.

Is that any indication of whats slowing it down?