Database Info

Overcloking

Is anyone else having an issue with custom kernels? My Tbolt only seems to run on the stock kernel/voltage. When I flash an oc kernel sometimes it will load and then freeze the system.
Sent from my ADR6400L using XDA App

All phones are NOT created equally. Your phone may just not be able to handle it while others could.

I realize every cpu used is not the same and can't handle being overclocked to the max, but come on, I can't overclock it at all without it freezing shortly after the Rom starting. Don't you think that's a little out of the ordinary?
Sent from my rooted Tbolt.

I seem to be able to run speeds up to 1.8 or so without issues. Something I'm noticing is even with higher speeds, being on the smart-ass setting still isn't baby butt smooth consistently. I know they are still fine tuning it. I can run at a much lower clock speed while set to on-demand and get great results. How it is on battery life? Still testing. I'm using Ziggy's latest from this evening, BFS.

Yeah that does sound kinda sketchy. Which kernels have you tried? Have you tried running one that wasn't undervolted? I've heard people having issues with the UV kernels.

Wkd1 said:
I seem to be able to run speeds up to 1.8 or so without issues. Something I'm noticing is even with higher speeds, being on the smart-ass setting still isn't baby butt smooth consistently. I know they are still fine tuning it. I can run at a much lower clock speed while set to on-demand and get great results. How it is on battery life? Still testing. I'm using Ziggy's latest from this evening, BFS.
Click to expand...
Click to collapse
I know what you mean. I had the 1.2 GHz uv kernel from adrenalyne and the phone ran like crap. What's the point of over clocking if real world results are worse. Smart-Ass would stutter while it was ramping up and gun bros ran like crap until I reverted back to the stock kernel.
I'm hoping somebody makes an OC kernel that isn't under volted.
Sent from my HTC Thunderbolt using Tapatalk.

I'm running Imoseyon's version 3 of the lean kernal, 1.4 ghz, undervolted. it seems much faster and more responsive, and has yet to cause me any problems. Right now I'm running on 20 hours off the charger with 45% battery life left (extended battery, so assuming stock would last around 9 hours).

The only kernel that works for me is adrenaline's 2.6.32.21 battery is life kernel. I've tried his other kernels, imoseyon's lean kernels, and a few others all with the same result of freezing up the Tbolt.
Sent from my rooted Tbolt.

Have you tried adrenalynes newest kernel? I'm using version 4 right now with no problems.

Yeah, another vote for Adrenalyne's kernels here.
I'm running the version 4c, and it's flawless on my phone. (4b locked up at higher speeds.) But the other tweaks he threw in there kick ass. Louder audio, faster charging and, I think, most significant, a potential fix for the GPS issues a lot of people are experiencing. Granted, mine was not too bad -- I could usually get a lock within a minute or two, but now it's locking in under ten seconds.
Can't quite comment on the battery life yet, but it's probably pretty damn good, especially with a minimal overclock or even staying at 1Ghz.

Running one of Ziggy's...so far so good...

I ran Drod's 1.5 kernel with no problems overclocking. When I switched over to Ziggy's or Adrynalyne's overclock kernels, I am unable to overclock with out my phone freezing and going into constant boot loops. Kinda weird but I have no real need to OC so I just went with Adrynalyne's stock kernel and been fine ever since.

Overclock lag

Hey everyone, I'm having a issue with the overclocking on my inspire. I searched but couldn't find anything relevant to our phones. When I wake my phone up it lags pretty bad for a few minutes and never really seems snappy. Even when it says I'm running at 1.2, 1.4.... its painfully slow. I'm currently running Ingersoll 2.4 with his JV kernel. This happened on Ar 3.5 as well. I did a full wipe before switching rom's and even un-rooted and re-rooted for good measure. I think it has to do with the speed the phone runs at while sleeping but I even tried to set it at 600 mhz while sleeping and still got the same lag. If I return to stock speeds and delete the overclocking app then it runs smooth. Help?
Edit: I've tried Setcpu and overclock widget with the same result from both.

kev012in said:
Hey everyone, I'm having a issue with the overclocking on my inspire. I searched but couldn't find anything relevant to our phones. When I wake my phone up it lags pretty bad for a few minutes and never really seems snappy. Even when it says I'm running at 1.2, 1.4.... its painfully slow. I'm currently running Ingersoll 2.4 with his JV kernel. This happened on Ar 3.5 as well. I did a full wipe before switching rom's and even un-rooted and re-rooted for good measure. I think it has to do with the speed the phone runs at while sleeping but I even tried to set it at 600 mhz while sleeping and still got the same lag. If I return to stock speeds and delete the overclocking app then it runs smooth. Help?
Edit: I've tried Setcpu and overclock widget with the same result from both.
Click to expand...
Click to collapse
You didn't say if you've tried different CPU governors, but have you tried different ones? (ondemand, interactive, etc.)

Yeah forgot to mention I did that as well. All with the same result, I'm starting to think maybe I got a bad CPU which just doesn't like to overclock at all. But it even lags if I only push it to 1050 mhz.

I can tell you when my phone is at screen off it's maxed at 368Mhz and I have it OC to 1.2Ghz when phone is in use and when I wake it up it is very responsive and runs great.

I wish mine was the same. the worst is when I'm trying to press the screen it won't react. then 3-4 seconds later it will decide to open the app and take forever doing it. Lame.

Before thinking the worst why not try to RUU to stock then reroot and see if that clears the issue? Worth a shot and if still bad go to AT&T and say the battery is shot or something and they will probably replace the phone for you.

lol I already returned to stock and rooted again for good measure. same result, but I believe your right, I need to think up a good excuse to get a replacement as I'm sure "it won't overclock" isn't good enough lol.

Is 1.5Ghz too high?

I have my Sensation set to 1.5Ghz and it works perfectly. The only thing is that it's getting a little hot (which is expected btw). It's currently fixed at 42C. 1.5Ghz is great but is it really that necessary? Should I just OC it to 1.3Ghz? I'm trying to find a nice temp base.

monkey hung said:
I have my Sensation set to 1.5Ghz and it works perfectly. The only thing is that it's getting a little hot (which is expected btw). It's currently fixed at 42C. 1.5Ghz is great but is it really that necessary? Should I just OC it to 1.3Ghz? I'm trying to find a nice temp base.
Click to expand...
Click to collapse
To answer your question, each device will have a differing operational ceiling depending on the quality of the SoC, soldering, silk-screening etc. They aren't all created equal. If 1.5GHz works fine for you, stick with it I see OC kernels pushing to 1.8GHz now.
Naturally the higher you go the hotter your SoC will run, so I'd play around and find the point where you gain some performance, but negligible heat over stock. Heat will kill not only your SoC, but your battery as well.
I'm only going from personal experience, but I've never found an OC to be worth it in terms of an actual, real-life performance increase, on any device. It looks good in benchmarks, but I'd rather have a phone that was smooth as butter in day-to-day operation than a jerky piece of sh*t that gets 10,000 in Quadrant YMMV of course!
The heat stress and battery drainage costs, plus stability issues, outweigh the positives for me.

How can I reset my CPU back to stock then?

monkey hung said:
How can I reset my CPU back to stock then?
Click to expand...
Click to collapse
Most of the Sensation ROMs feature what's called an OC Daemon.
This is pretty much an automatic overclocker of sorts. It can change your clock ceiling/floor automatically depending on load. Read a bit more about it here.
If you have something like SetCPU installed, the Daemon is redundant, giving you manual control over your clocks. The easiest way to return to 'stock' frequencies would be to simply delete SetCPU and allow the Daemon to do it's thing

Well I uninstalled it and I have LeeDroid. How do I find this "daemon"? Where would it be located? What do I do I'm a noob

monkey hung said:
Well I uninstalled it and I have LeeDroid. How do I find this "daemon"? Where would it be located? What do I do I'm a noob
Click to expand...
Click to collapse
I couldn't see whether the daemon in included on LeeDroid, or whether LeeDroid has actually just modified the frequency tables (list of supported frequencies) to allow for the ~1730MHz ceiling. If the daemon is there, it'll already be working for you - you don't see it
I don't believe it's something you can just download and tack on. I think you'd have to be running a supported ROM. You may need to dig a little deeper into the LeeDroid thread and do some reading, or perhaps retitle this thread to ask 'Does LeeDroid include the OC Daemon' or something similar.
Sorry I can't be more help, I'm a devout Android Revolution HD supporter myself, although I am running the UNITY kernel.
Good luck mate!

personally I can't see the need to over clock, given that all software is probably written for devices currently in use, I do not know of any dual core 1.5 or higher phones, so why oc ?
I agree , I would rather have a fast stable phone, than some jerky fc piece of ****e that gets 10000 jiggawatts in a benchmark, and that can cook my crumpets..................... on second thoughts, I do like my crumpets.

Unresponsive Screen (Screen Freeze)

Of all the issues that plague the tbolt the one that bothers me most is screen freeze (screen becomes totally unresponsive to touch while using the tbolt).
I'm currently using bamf cubed 1.0.9 but I've had the problem in every rom I tried including stock. I do find it is happening more frequently now though. Used to get maybe one freeze a week. Now about 2 per day.
I tried bamf's latest kernel but that didn't help.
Currently I'm back in stock kernel and I'm trying the performance.governor.
I find hit or miss approach I'm using stupid and unacceptable. Can someone suggest a more logical approach to my problem? I'm especially interested if you had the SAME problem and found a way to fix it.
Thanks!

recDNA said:
Of all the issues that plague the tbolt the one that bothers me most is screen freeze (screen becomes totally unresponsive to touch while using the tbolt).
I'm currently using bamf cubed 1.0.9 but I've had the problem in every rom I tried including stock. I do find it is happening more frequently now though. Used to get maybe one freeze a week. Now about 2 per day.
I tried bamf's latest kernel but that didn't help.
Currently I'm back in stock kernel and I'm trying the performance.governor.
I find hit or miss approach I'm using stupid and unacceptable. Can someone suggest a more logical approach to my problem? I'm especially interested if you had the SAME problem and found a way to fix it.
Thanks!
Click to expand...
Click to collapse
It looks like that most people that end up with this problem (sleep of death, blank screen of death, or whatever you want it to be called) were either underclocking to low or undervolting to low, some governors have also been the culprit on some devices. Not all of our thunderbolts are the same, guess solder joints are weaker or something that makes this such a random problem. Your best solution is to try different kernels, cpu settings, and governors to find out what your phone likes. I personally haven't had this issue with eternity. However, some others have! Good Luck

Yes, what the above poster said. Like for my phone it does not like smartass gov. It will work but the screen will freeze as you have experienced also. Also overclocking, i can overclock to 1.7ghz but will also freeze randomly as you experienced.
Sent from my HTC ThunderBolt using xda premium

I think (but could be mistaken) this is more like the opposite of black screen of death. I believe that is when the phone wont wake from sleep.
My problem occurs only when phone is awake and being used heavily. The screen isn't black nor blank - I see whatever screen I am on when it happens: lock screen, an app, home screen, keyboard, etc. I see all the icons but screen becomes totally unresponsive to touch. Wide awake.screen but no matter how you tap, slide, or use capacitive buttons nothing works.
Only way out is to pull battery or hold down up volume, down volume, and power key simultaneously to force a restart.
There is someone out there who understands this phenomenon better than I and can suggest approaches but I must be clear - this is.not a black or blank screen and doesn't occur when clock speed is low.
I would.guess cpu is operating at full 1 ghz when screen freezes occur in my tbolt. I am not overclocking at the moment but I do believe overclocking makes it worse but not sure.

Mine was doing that at being underclocked too low keep it at say, 368 mine never did it again, also don't undervolt too much it can cause phone to power down. I use ondemand and keep you lowest speed to 368 and you should be fine. Using battery saver mode for kernel in speedtweak may be undervolting your phone to much if you are using that.
Try this kernel working great for me. http://db.tt/QqkRvtjm jdk newest kernel.
Sent from my ADR6400L using XDA App

I was in smartass governor with low at 368 and high of 1.4when all this occured. I then dropped the highto 1.2 then finally back to 1. Now im back in Stock kernel. I don't see what difference the minimum makes in my case.
I guaranty you my phone is at 1 ghz when it freezes it only happens when I'm using the tbolt - never when sleeping. Anyway I did have it set to min. Of 368 all along. It was the first advice I got when I first tried 1.0.7 and I've stuck with it.
I had screen freezes in stock kernel ondemand governor 368/1ghz which is why I tried overclocking in bamf 3++ kernel smartass governor. It was even worse (more frequent) in smartass so went back to stock kernel ondemand 368/1ghz.
Tonight I'm in stock kernel performance governor (1ghz all the time). There's gotta be a better way than random trial and error.
Imagine if dell told you to try windows xp or windows me if your computer doesn't "like" windows 7?

recDNA said:
I was in smartass governor with low at 368 and high of 1.4when all this occured. I then dropped the highto 1.2 then finally back to 1. Now im back in Stock kernel. I don't see what difference the minimum makes in my case.
I guaranty you my phone is at 1 ghz when it freezes it only happens when I'm using the tbolt - never when sleeping. Anyway I did have it set to min. Of 368 all along. It was the first advice I got when I first tried 1.0.7 and I've stuck with it.
I had screen freezes in stock kernel ondemand governor 368/1ghz which is why I tried overclocking in bamf 3++ kernel smartass governor. It was even worse (more frequent) in smartass so went back to stock kernel ondemand 368/1ghz.
Tonight I'm in stock kernel performance governor (1ghz all the time). There's gotta be a better way than random trial and error.
Imagine if dell told you to try windows xp or windows me if your computer doesn't "like" windows 7?
Click to expand...
Click to collapse
That might be the case if we all used the exact same set up. We don't some change fonts, some use different apps, and there are so many variables.

Nothing unusual going on in my tbolt. 1.0.9 cubed with no unusual apps or settings. I seldom add.an app to my bolt unless it has 1000's of downloads in the market with high ratings. I learned that back before I rooted. I bet someone who writes.kernels understands this phenomenon and could point me in the right direction. Imagine if your computer was bonked up and advice was to randomly try changing settings?

recDNA said:
I was in smartass governor with low at 368 and high of 1.4when all this occured. I then dropped the highto 1.2 then finally back to 1. Now im back in Stock kernel. I don't see what difference the minimum makes in my case.
I guaranty you my phone is at 1 ghz when it freezes it only happens when I'm using the tbolt - never when sleeping. Anyway I did have it set to min. Of 368 all along. It was the first advice I got when I first tried 1.0.7 and I've stuck with it.
I had screen freezes in stock kernel ondemand governor 368/1ghz which is why I tried overclocking in bamf 3++ kernel smartass governor. It was even worse (more frequent) in smartass so went back to stock kernel ondemand 368/1ghz.
Tonight I'm in stock kernel performance governor (1ghz all the time). There's gotta be a better way than random trial and error.
Imagine if dell told you to try windows xp or windows me if your computer doesn't "like" windows 7?
Click to expand...
Click to collapse
That sounds more like your phone doesn't like whatever voltage is set for your top end frequencies. Might want to try IncrediControl from the market and increase the vdd levels a little. I think a lot of the kernels floating around are under volted a little. Could be the cause.
Sent from my ADR6400L using Tapatalk

Its worth a try. I never tried that. Thanks.

You say it only happens when using your bolt, maybe the processor is just maxed out. How long do you wait to see if it comes back around?

I have waited as long as 10 minutes but usually ibjust restart within 30 seconds based on experience. Once "frozen" it has never recovered on its own.
What's interesting is the processor is still working whilebthe screen becomes unresponsive. I know this because I was streaming a r radio into a jawbone earpiece and when I switched apps the screen froze yet the radio continued to play. I HAD to restart to stop the music since the screen wouldn't respond to touch.

I flashed Imo's lean Sense Kernel and haven't had a freeze yet. I hope this has solved the problem. There is a little lag now when I hit a widget or app shortcut but no more freeze.

Your lag is prob due to being in safe made, put in normal mode in speed tweak to rid yourself of lag.
Sent from my ADR6400L using XDA App

No, I'm in standard mode. I chose #1 in speedtweak. I varified at 1.4 ghz max/ 254 min
I couldn't figure out how to raise min value in speedtweak so I reinstalled set cpu and set min to 368. Seems to reduce the lag.
Still a slight lag but most importantly no screen freeze since installation.

This might be unrelated, but I've run into a situation where the touch screen is entirely unresponsive. I was running CM7.1.1 and the phone randomly restarted while sitting on the desk, after that it now claims to have no service and won't unlock because it won't respond to touch. Any ideas?

mkitchen said:
This might be unrelated, but I've run into a situation where the touch screen is entirely unresponsive. I was running CM7.1.1 and the phone randomly restarted while sitting on the desk, after that it now claims to have no service and won't unlock because it won't respond to touch. Any ideas?
Click to expand...
Click to collapse
Have you tried flashing a stock ruu in fastboot? You may try to go back to completely stock and then go from there. You could try a different rom too and wipe the system partition as well as the usual stuff first.
Sent from my ADR6400L using Tapatalk

I went back to the stock ROM using clockwork mod recovery, and the problem persists. I am wiping system partition now, but I did some of the stuff that has worked for me in the past such as dalvik, user data, and cache.

Wiping system may help but if that doesn't I'm not sure what else for you to try except fastboot flashing an ruu.
Sent from my ADR6400L using Tapatalk

Actually wiping system worked, I may have not done it in the correct order the first time I tried to flash back to stock. I really appreciate the help.

[Q] Overclocking cm7 to 1600 Mhz

So overclocking cm7 to 1600 doesnt work and causes boot loops, i have been trying to get a kernel that would do it and i cant find one.
anyone know any kernels that work?

Only kernal for cm7 is the one that is with it no other kernals are compatible as for 1600 some phones run fine at 1600 others don't just depends on your CPU in your phone
Sent from my SGH-I997 using xda premium

^^^ what he said ^^^
my cappy was maginally stable @ 1300 within a very narrow voltage range. my infuse runs 100% @ 1664 with a ton of uv untill i turn on gps and everything starts to get warm. every cpu is different.
most infuses seem to be a higher test cpu than galaxy s phones though. you may be able to run at 1500 or better if you take a lot of time and figure out what the cpu likes and doesnt like. remember heat, uv and rapid voltage change can all cause instability so too much uv can cause problems as well as too little! to get maximum speed you may want keep the top few freq's at the same voltage (not the same uv but the same actual voltage) and have zero uv on the low freq's. it can be a pain to figure it all out but when you see the benchmarks you may think it was worth it.

ok well i kinda messed around with the overclocking built in and was messing with the type of governors and userspace seems to support over clocking on 1600.
really weird but my phone hasnt done the boot loop yet.
but thanks for your guy's help.

I set mine at 1600 last night via SetCPU. After 5 min it got hot and started boot looping. Its running good at 1200 now. I'm gonna bump it up little by little.
Good info, nice to know its "normal".

Honestly, the performance of CM7 outperforms all the other ROMS even running at 1.2GHz (IMO). I really don't see much of a performance increase by stepping up the clock speed, just a decrease in battery life, so it's not worth it to me.

ive talked to many people about this and most can only run at 1.4ghz even though 1.6ghz was stable in froyo. alot of people repeat "it depends on your specific chipset" but i dont buy that cop out. i think theres something wrong with the 1.6ghz setting in cm7.