• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [Kernel]OptimusM OC stock 2.2.1

Updated the reserved post with something for the froyo users. lemme know how it works.
Well I'm going back to Froyo because this random reboot is pissing me off. It's not clock related, as I turned it down and it still does it; it's not even hot. It was fine this morning, but now I'm up to 3 random crashes today.

I'll let you know how my Froyo runs.
 
That happened to me too using adb. I used terminal emulator on my phone to flash and it worked fine.

I had one typo when typing the recovery name, It flashed the last time though, I didnt like that bad boot error message which it didnt mean anything, But i like the clean look one the new one.
 
Flashed it over the stock 2.2.1 ROM and I'm stuck at the boot animation. I'll let it sit for a few minutes.

finally booted, but locking up randomly instead of rebooting.
 
Flashed it over the stock 2.2.1 ROM and I'm stuck at the boot animation. I'll let it sit for a few minutes.

finally booted, but locking up randomly instead of rebooting.


Weird how same phones can act different when applying same kernels. I feel for you. But I'm glad mine isn't doing it
 
the lock-up may have been a fluke; it's running good right now with rOCK, but at stock clocks. I'll turn it back up in a bit once I'm sure it's stable.
 
I didn't have my temp/speed control profiles set in Froyo, I think my lock-up was due to an uncontrolled temp spike as I was performing a series of CPU-intensive operations when it locked.
 
Stock Froyo running great. No further crashes/lock-ups. Also noticed improved battery thus far. "Battery" temps are much cooler than GBCM7.
 
Yeah Reppard, what kind of wizardry is this?

My CPU runs faster AND my battery lasts longer.

How many virgins and baby kittens were sacrificed to make this possible? (not that I care it was totally worth it, lol)
 
now, all of the sudden, crash after crash after crash.

As much as I want it to be, this kernel just isn't stable.

Not on my phone anyway.

reppard, let me know if there's any data I can collect for you since I seem to ahve a troublesome handset.

PS: It appears that the battery calibration tool posted does the same thing as the Wipe Battery Stats function of Recovery, but without the need to reboot.

another edit: And it just crashed again even with the CPU set at 600/245. :( Definitely the kernel, methinks.
 
Yeah Reppard, what kind of wizardry is this?

My CPU runs faster AND my battery lasts longer.

How many virgins and baby kittens were sacrificed to make this possible? (not that I care it was totally worth it, lol)


Only 3 virgins but it took about 14 kittens to get the job done! Looks like we may have gotten that boot loop problem solved. I will probably lower the default Max in the next update for better compatibility across the board. Thank you all for testing and helping with the debug period of the early releases. I like to release stuff like that with lots if updates early on and get it all on to the table. I would love to have more froyo users to weigh in so I can thin this down to one release for everyone. Thank you to the 3 donators. I'll start a thanks list soon you are very much appreciated!
 
@Reppard I got a problem with r.O.C.K. V3. The boot loop problem is gone. But the default max speed of the kernel still screwed my phone when i try to make use of it. For example by playing Angry Birds RIO it will make my phone reboot. Anything that takes heavy processor action will reboot my phone with the default max speed which is 728 i believe. And the problem is that CPU apps go from 600 to 728 LOL so it doesn't give me an option like 690 so i can make at least a small use of over clocking.

If you could make a New version With 700 or 690 that would be great and maybe my phone can handle it.

It seems i got the short end of the stick with my phone. I can't believe that there is such variance in the capabilities of these chips. I call bad quality control! Lol

Thanks for all your work Reppard at the moment i'm using CPU master to stop it from going to 728 and killing me. I'm keeping it at the default 600 :(
 
you might want to try a different governor. sometimes that could make the difference. also for gosh sakes- do not set on boot
 
you might want to try a different governor. sometimes that could make the difference. also for gosh sakes- do not set on boot
I'll try running On Demand instead of Interactive.

man download speed is faster to
It's not the download that is faster, rather likely the CPU is just processing the received data faster. File operation times are greatly reduced by the overclock I've noticed. Titanium Backup's performance skyrocketed with the OC.
 
Back
Top Bottom