Root Noobly rooted-a word of advice

[mentaloaf]

Aloha all,
Rooting your droid may seem a little daunting if you don't know what a lot of the forums and tech talkers are talking about, but I urge you......ROOT your phone! I just did it yesterday and am running bugless beast which I got from ROM manager premium. I'm loving it!! Most importantly though....MAKE A NANDROID BACKUP or 3...I would have been #$!!@ed if I hadn't made a few backups (pre-root, post-root, pre-ROM switch). The kernel I first chose which was 1.1 gHz made my phone almost go out the window, but I was able to revert to one of my backups and try the 1 gHz kernel, which is working awesomely...you MUST do a backup though.

Anyway, should I even get an overclocker or is BB1.1 overclock it already? Seems like my battery is doing great but my phone is lightning fast...Any suggestions on some really good useful apps?

 

[droidftw]

Bugless beast is ocverclocking your droid for you but it has no profiles such as 250/250 when i sleep mode or 550/250 when charing or whatever it is just clocking it ondemand which when it is need to overclock it does and when it needs underclock it does.

 

[nstallion]

Download SetCPU in the market.

 

[mentaloaf]

Bugless beast is ocverclocking your droid for you but it has no profiles such as 250/250 when i sleep mode or 550/250 when charing or whatever it is just clocking it ondemand which when it is need to overclock it does and when it needs underclock it does.

What does this mean? Profiles 250/250? Please forgive my noobiness...

 

[mentaloaf]

Download SetCPU in the market.

If my BB is over and underclocking for me, is there some reason I should still get setcpu?

Also, are the different kernels different processing speeds? Maybe my droid didn't like the first kernel I tried because it was too overclocked or something, does that happen?

 

[droidftw]

250/250 means maximum of 250 mhz and minimum of 250 mhz 550/250 menas maximum of 550 mhz and minimum of 250 mhz

 

[shrink57]

Word of advice: try and keep the minimum a little higher than 250 as many have had problems receiving calls when it is clocked too low. I keep the minimum between 400-500 (depending on what is available in the kernel I am using).

 

[droidftw]

Word of advice: try and keep the minimum a little higher than 250 as many have had problems receiving calls when it is clocked too low. I keep the minimum between 400-500 (depending on what is available in the kernel I am using).

hmm i guess im the lucky one when i running certain kernels i can even go to 125/125 and still get calls...

 

[shrink57]

hmm i guess im the lucky one when i running certain kernels i can even go to 125/125 and still get calls...

I have run into situations where the phone rings but will not unlock when in sleep mode. Upping the minimum speed cured that. I depends on your paticular phone, ROM you are using, and the kernel (and I guess a little luck ).

 

[markc2]

I was rooted, used CM and BB, loved both of them, and overclocking. Now on my second Droid, the first is about to go back for data corruption problems on the first and replacement SD cards. (yes I put it back to stock before shipping).

I am so close to rooting this second phone, but it's so snappy and fast with Launcher Pro and ADW. I hardly notice the difference between this and the
1 ghz root from before. Maybe web pages load a microsecond slower, but I don't miss the "acore" fc's and the other odds and ends errors that would pop up. OK try a different kernal, get stuck at the M, nandroid back, etc. etc. All lots of fun for a techie.... Bugless was great but never really bugless for me, and I may miss the miscellaneous tweaks available in both BB and CM, but I like having a VERY STABLE phone. When I start reading about the changes Froyo brings I'll probably re-root then, or maybe just wait for the OTA.....

​

 

[droidftw]

I have run into situations where the phone rings but will not unlock when in sleep mode. Upping the minimum speed cured that. I depends on your paticular phone, ROM you are using, and the kernel (and I guess a little luck ).

Ive noticed it takes maybe half a second longer to wake up but that doesnt make a difference to me.

 

[Rodeojones]

I underclock to 250/250 while in sleep mode as well (mostly because the kernel I use has no other options between 250-500). I've never had issues with lag when I get a phone call or text. I guess I'm lucky in that area.

 

[ZXMustang]

I underclock to 250/250 while in sleep mode as well (mostly because the kernel I use has no other options between 250-500). I've never had issues with lag when I get a phone call or text. I guess I'm lucky in that area.

I have. I had mine set to 250/1000 and it would almost not answer everyother call that came in. It was annoying, and when I read this thread this made sence. Now it seems to be much better at 500/1000.

 

[YankeeDudeL]

For the OP, the reason to underclock to 250MHz is that your processor will use less power when the phone is asleep (in other words, when you're not using it). This helps to save your battery life. At very least, it should compensate for the extra power being zapped when you overclock. For me, it's actually helped extend my daily battery life (w/ normal usage).

As for the call delay issue, I have noticed it and never attributed it to being UCed. Learn something new everyday. But I've found this issue at other times, too (especially if running an app or two...streaming music, for sure).

I've found that after I flash a new ROM, the first call I answer takes forever for me to be able to answer. I make it a point to call myself afterwards and it usually takes care of the issue.