I've used Chevyno1 1.2 and Adamz's 1.1, and preferred Adamz's, as Chevy's in combination with BB was causing some lockups while the phone was asleep - would not wake up w/out battery pull...see the BB 1.1 thread and you'll see a number of posts on this in the last day or two.
I actually went back to BB 7.9...never had any issues w/that (though some did have root problems after installing...)
I've used Chevyno1 1.2 and Adamz's 1.1, and preferred Adamz's, as Chevy's in combination with BB was causing some lockups while the phone was asleep - would not wake up w/out battery pull...see the BB 1.1 thread and you'll see a number of posts on this in the last day or two.
I actually went back to BB 7.9...never had any issues w/that (though some did have root problems after installing...)
I had the same issue with BB 2.1 (.1) and Chevy's...BB 2.1 (.3) though, I have no problem with Chevy's...Going to flash to .4 and see how it works in combo with Chevys...
I've used Chevyno1 1.2 and Adamz's 1.1, and preferred Adamz's, as Chevy's in combination with BB was causing some lockups while the phone was asleep - would not wake up w/out battery pull...see the BB 1.1 thread and you'll see a number of posts on this in the last day or two.
I actually went back to BB 7.9...never had any issues w/that (though some did have root problems after installing...)
Had the exact same issue with BB1.0 and Chevy's 1.25 in addition to a couple of spontaneous reboots. I had a lot of FC's coming off the car dock too, but I couldn't say whether that was an issue with the ROM or the kernal. I also noticed that it ran pretty hot, pretty constantly.
I'm running BB1.1 now with Adamz 1100 kernal and I haven't had any issues in several hours now, but I haven't been docked, so we will see if that issue resolved itself. My temps have come down quite a bit as well.
Adamz 1.1 - works great. Runs a little warm at 1.1 ghz, but, uh, that makes sense. Only one issue since I installed this 2 days ago. Couldn't be happier
ugh 2 reboots already (hour) on droid mod. running at 1200. (BB1.1) first time market browsing, second time running benchmarkPI, guess ill have to drop the speed down a bit and test that
ugh 2 reboots already (hour) on droid mod. running at 1200. (BB1.1) first time market browsing, second time running benchmarkPI, guess ill have to drop the speed down a bit and test that
Stability can be due to the clock speed or the kernel. You might find that some kernels are stable at 1200 on your phone while others are not. Might want to try a few before you underclock it and test the stability of the system.
Chevy 1.25GHz. I set it to 1250MHz, fired up BenchmarkPi, and as soon as I started the benchmark, it froze and rebooted. 1100MHz works perfectly though. I might try flashing his 1.2GHz kernel later and seeing if I can run at 1200MHz, cause 1100MHz seems unusually stable given that I can't run BenchmarkPi at all at just 150MHz more.
I believe that it will. The only reason I could see unrooting though is if you need to send the phone in for service, and if you wanna do that, I would personally do the sbf method mentioned in the sticky at the top of this forum to get it back to out-of-the-box state.
Also, for some reason 1.2GHz seems to work fine for me. I can't believe 50MHz is the difference between a good run through BenchmarkPi and some use, and crashing.
I'm using Adamz, but what's weird is that I have access to two Droids, and one with Adamz ran fine, the other goes into reboot loop if I have Setcpu to load on boot. Turn off the setcpu, and the second unit is fine,turn it on, its fine...but have it with the "load on boot" setting...reboot...over and over.
I think because each processor is a little different, you really have to experiment for what's right for your phone.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.