I don't know if imo's new lean kernel based on the recently released htc kernel allows use of terminal to set overclocking?
Any Noticeable Difference Overclocking to 1.4 gHz
- Thread starter recDNA
- Start date
I'm diggin' it so far. It definitely has better performance, things open faster and are smoother. I'm calibrating the battery now so I'm hoping for noticeable results in battery life. I'm running it on extreme (extremely undervolted, overclocked to 1.41Ghz) and using smartassV2 governor. So far I'm at 80% after 5hrs 22mins (1st battery cycle still) normal usage at home using WiFi (bad cell signal at home).
I'd liie to try it but I thought I'd wait for the next version. Version 2 of anything is usually better.
From what I've been reading the pre-packaged kernel in cubed works the best so i'll have to hold off on trying this kernel for a while.
I have had a problem in bamf 1.0.7 and bamf 1.0.9 cubed and a little less often in stock gb that my screen becomes totally unresponsive to touch.
If i install Imo's latest gb kernel Is there a particular setting that would be likely to PREVENT these screen freezes? I have tried upping the minimum cpu speed in bamf settings but that made no difference.
If i install Imo's latest gb kernel Is there a particular setting that would be likely to PREVENT these screen freezes? I have tried upping the minimum cpu speed in bamf settings but that made no difference.
Usually upping the min will do it, I've had to up my min to 368 on pretty much every GB ROM I've ever run.
It may be working now, but I had trouble with some kernels getting to accept the settings when using the BAMF settings.
FYI, if you have an XDA account, then you can download SetCPU from there, and it has lot more options for setting CPU speeds, including profiles.
SetCPU for Root Users [2.2.4] Undervolting and more 07/07/2011 - xda-developers
SetCPU is also available from the Android Market.
I am an xda member. My problem isn't finding how to set speeds or voltages. My question is specifically what settings are best to prevent unresponsive screen?
Like would setting min even higher than 368 help? Would overclocking help? Would undervolting help? Since I don't have the slightest idea what causes my screen to freeze I don't know how to even try to fix it.
Like would setting min even higher than 368 help? Would overclocking help? Would undervolting help? Since I don't have the slightest idea what causes my screen to freeze I don't know how to even try to fix it.
Bond32
Well-known member
- Jun 27, 2010
- 1,358
- 35
- 0
Literally, the ONLY difference I have noticed is with watching videos... performance is slightly better when decoding higher res movies as well as seeking. Other than that to me, screen transitions are exactly the same. No reason to me to overclock.
I generally OC to 1.28, and leave the min at 368. With IMO's kernels, I usually use the Interactive Gov. Right now, I'm using ADR's latest kernel, with the same frequency settings and the "smoothass" gov.
I also keep a profile to scale the CPU back when my battery gets low or the device temp gets too hot.
For me, those settings usually stop the freezeups and the slight OC does make things like transitions and opening and closing of apps much quicker and smoother...but that's just my opinion/experience...yours may vary.
I just wondered if there is a direct correlation between any of these settings and screen freeze? I'm guessing most users have never even had a screen freeze?
I certainly have.
From what I've been able to figure out based solely on my experience, the screen freezes I've had were caused by/fixed by 2 main things...
1. CPU set too low. Not sure why, but pretty much every GB ROM I've run has had issues with the min CPU set to 245. My phone would lock up with the screen off, and only a battery pull would fix. Setting min up to 368 seems to definitely fix that on my device. If I set the min to 245, my phone locks up about once a day; at 368, pretty much never.
2. Wifi. On some GB ROMs, I would notice that when I had wifi on, my phone would occasionally lock up when my phone would fall out of range of the wireless access point (i.e. when I'd leave my apartment in the morning). I'm currently running BAMF Forever 1.0.9 and haven't noticed it happen with this ROM yet...but I did notice with earlier versions of Forever, so I'm not sure if it was fixed, or if I've just been lucky... (I also try to remember to actually turn off my wifi before I leave the house now too, but there are definitely times I forget).
Hard to say, but most reports say that 368 is just fine.
When the freezes occur, are they at random times, or is there any common denominator amongst them?
In other words, do they always happen when the phone is idle, or when you're actively using it? Do they happen when you're in a particular app, or at any time? etc....
Stuff like that can help to diagnose the issue.
Also, I wasn't suggesting that you don't know how to set CPU speeds, I was suggesting that perhaps using BAMF settings to change them doesn't always actually work. My settings seem to "hold" better when I use SetCPU, that's why I suggested it.
Oh, I see. Thanks. Didn't mean to be gruff. Its just frustrating trying to address this issue. I also like to understand what I'm doing and why. I don't even know if overclocking to 1.2 would help. It doesn't really happen that often but its always at the worst possible moment
Just installed setcpu. It did detect the same settings as in bamf settings so no need to tweek. If I try this kernel i'll try overclocking to 1.2 with setcpu. Will I have to manually set voltages of will setcpu take care of that?
Just installed setcpu. It did detect the same settings as in bamf settings so no need to tweek. If I try this kernel i'll try overclocking to 1.2 with setcpu. Will I have to manually set voltages of will setcpu take care of that?
Last edited:
Both the IMO and ADR kernels (the two most popular custom ones) have voltages already set. You *can* change them, but shouldn't have to.
I'm currently running Adrynalyne's latest on BAMF Forever cubed 1.0.9 and really like it.
[KERNEL][2.6.35.10][BETA]Test 3
From my experience with the freezeups, overclocking isn't necessary to fix it, just upping the min; however I like to OC up a step as well, for reasons I discussed earlier.
Had to leave the bamf kernel. For some reason it failed to install the bamf vdd file in the init.d folder.
Similar threads
Facebook
Twitter
Instagram