Overclocking help? - Thunderbolt Q&A, Help & Troubleshooting

Im running Cm7 withh Imoseyon's kernal. Every time i oc to 1.9 phone will freeze almost instantly any suggestions to fix this
Sent from my ADR6400L using Tapatalk

Yep, slow the overclock to 1.5 your phone can't handle it, neither can mine. Some can and some can't but other than running a nice CPU test to show off to your buddies you don't want to push your TB like that on a daily basis. I have mine set to 368/1.02 and happy as can be with the extra battery life I get from my phone.
If I helped you in any way please use the thank you button

Alrighty i have mine set to 1.4 extremely undervolted and i get 9-10 hours battery life with heavy use thank you
Sent from my ADR6400L using Tapatalk

Hello,
I have a few issues with IMO's lean kernel that someone might can help with. 1) Extreme settings 2 and 4 cause instant phone freeze and reboot. 2) Option 3 works for the first minute or two after boot but then freezes (CPU spy shows 1.92 GHz runs smooth through boot). I believe it to be caused by the ramp up/down of the governor or possibly a script/setting messing with my system.
I am able to run very stably and smooth with a top CPU speed of 1.6 GHZ( 1.593 GHz on A05P). Any ideas on what I can do to increase the CPU speed so that the system stays stable? Your input is much appreciated. Thank you again for helping this poor noob.

Veltar said:
Hello,
I have a few issues with IMO's lean kernel that someone might can help with. 1) Extreme settings 2 and 4 cause instant phone freeze and reboot. 2) Option 3 works for the first minute or two after boot but then freezes (CPU spy shows 1.92 GHz runs smooth through boot). I believe it to be caused by the ramp up/down of the governor or possibly a script/setting messing with my system.
I am able to run very stably and smooth with a top CPU speed of 1.6 GHZ( 1.593 GHz on A05P). Any ideas on what I can do to increase the CPU speed so that the system stays stable? Your input is much appreciated. Thank you again for helping this poor noob.
Click to expand...
Click to collapse
Don't OC that high, simple as that. There is no need to run the phone constantly at 1.9ghz.

Related

[Q] Overclocking a daily driver?

I'm running the awesome das BAMF ROM 2.0-5 with the MR2 radio. The camera on this ROM runs much smoother when max CPU frequency is set at 1.4 ghz. Is it generally safe to leave my phone overclocked at 1.4 GHz indefinitely? Particularly for a daily driver/ primary and only phone? It seems to run this so far, but I don't know enough about long term effects of overclocking. Thanks everyone.
I overclocked my Eris for over a year. 1.4 ghz is safe as a general rule because it can run stable up to 1.8. If you use SetCPU you can set profiles to underclock when the screen is off, below a certain battery level, etc. Just remember that if you flashed imoseyon's kernel, you need to run the speedtweak.sh script in a terminal emulator and run option 13 if you are using SetCPU after selecting voltage options.
Sent from my ADR6400L using XDA App
I'm thinking I'll stick to whatever kernel is in the das bamf 2.0-5 ROM. Easy drop down menus
Also, if a kernel runs stable at a certain frequency (say 1.8 ghz), does it follow that the processor hardware itself will also be OK? In other words, if I can run at 1.8 ghz stable and deal with the battery life associated with it, will my phone last through my two-year contract or will I wake up one morning a year from now and find the phone has turned into a marshmallow?
Well obviously there is risk involved, but a processor either runs fine, or it wont run at all. Personally I run at 1.6 Max right now, only because its not worth the risk, with the minimal gains to run it at 1.8. In terms of the longevity, well sometimes you gotta just take the plunge bud, that's the fun in android.
Sent from my ADR6400L using XDA App
You won't really notice any performance difference with anything over 1.4 ghz.
I have been running imoseyon's kernels at 1.4 max & 245 min ever since he implemented speedtweak. No overheating, reboots or other weirdness. Ymmv, each phone has different tolerances. But as long as you don't o/c the min frequency (i.e., you're not constantly at 1.9 or 1.4 ghz) you will probably be fine.
Sent from my ADR6400L using XDA App
sublimaze said:
I have been running imoseyon's kernels at 1.4 max & 245 min ever since he implemented speedtweak. No overheating, reboots or other weirdness. Ymmv, each phone has different tolerances. But as long as you don't o/c the min frequency (i.e., you're not constantly at 1.9 or 1.4 ghz) you will probably be fine.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
same here, imo's kernels have made this phone what it should be. it has incredible battery life compared to stock.
but to answer the OP's question, i can't see why leaving it o/c'ed to 1.4 indefinitely will harm anything. like sublimaze mentioned, as long as you don't bump up the min freq, your phone won't be running at 1.4 the whole time. it only gets up that high when an app or system function needs the processing power.
on a side note, even if you did put your min freq at 1.4, i still don't think it would hurt anything, it would just murder your battery quickly

[Q] How hot is too hot?

I installed the webtop over hdmi mod on my Atrix and while testing it out, it got very warm in my hand. I opened the setcpu app and noticed that while overclocked to 1.3GHz, the CPU was running at 75C! I lowered it back down to the stock 1GHz and the temp slowly went down and settled at 63C.
It seems that while in webtop mode, the CPU is taxed at 100% all the time so I'm wondering if it's safe to stay overclocked when using webtop.
Everyone has different opinions of what is too hot around here.
IMO the cooler the better. IMI No Atrix should have a temp above 60c and I'm not even comfortable with above 50c either...
Sent from my MB860 using xda premium
I have experienced the same problem and worried that something may fry.... I have had mine overclocked at 1.45 using debian linux and all of a suddent he phone freezes and restarts.... Since it did it to me the second time I have kept my phone at 1Ghz... I am new at this so please don't beat me up too bad for being a noob... Just want to see if maybe undervolting it a little might help or hurt it?
Thanks in advance
Here are some tips I can offer
1.Try re-flashing your custom kernel and see if that fixes the web-top thing and over heating
Whenever the phone is plugged to the web-top it will naturally overheat so it's kinda expected remember now it's gotta work harder since its displaying on lap-dock or TV,but if you can cook an egg on it it might be too hot...lol
2.Set profile for temperature on setcpu so this way once you reach for example 100F your phone will clock down a little and so it might help the heat issue.You can set even more than one temp profile so this way when it reaches 96 it goes down a little then when it reaches 100 it will clock down a little more and such.
3.If that doesn't help,which in my situation it did.Flash a different kernel mayb it's just the one you're using that is causing funny stuff to happen.
Edit: not sure but i think undervolting helps battery but causes more heat,I myself don't undervolt I just created litterally a bunch of setcpu profiles for battery level,screen off,incall,charging,temp,and time and I'm getting 13 hour days at 1.3Ghz and temp profiles have been helping by clocking down when it's too hot therefore saving battery and drastic overheating.I dontlike my phone going anything over 104F it gets me paranoid,but that's just me.
I tried reflashing the kernel but it didn't change anything. I'm using Faux's 1.3GHz overclock kernel for Gingerbread (2.6.32.9). Is there something else I should be using?
sk8trix said:
Edit: not sure but i think undervolting helps battery but causes more heat,I myself don't undervolt I just created litterally a bunch of setcpu profiles for battery level,screen off,incall,charging,temp,and time and I'm getting 13 hour days at 1.3Ghz and temp profiles have been helping by clocking down when it's too hot therefore saving battery and drastic overheating.I dontlike my phone going anything over 104F it gets me paranoid,but that's just me.
Click to expand...
Click to collapse
Do what sktrix said in rest of his post.
I use the stopgap 1.0GHz kernel, and UV does lower temperatures. I would definitely try UV'ing a wee bit. You don't need to go crazy. I am using the following with great results for both temp and battery life:
-50
-50
-75
-75
-75
-100
-100
My setcpu profile clocks it back if I reach 60C, (I idle in the low to mid 30's). Under heavy load I reach around 52C max which is quite acceptable.
Now, granted I am not using Webtop, but the end result for UV should be the same. Lower temps and better battery life. You may also want to try just using 1.0GHz when on Webtop. The phone has more than enough power at this clock speed.
There is a bug with faux's kernel that causes the webtop to clock the phone at max speeds until restart.
Sent from my MB860 using xda premium
I know I'm straying from my correct forums here, however I have an LG Optimus 2X which like the Atrix, is a Tegra 2 CPU.
Our phones get VERY hot, I have had my CPU up to 86C before I decided to back off the stress test. CPUs are very good at handling high temperatures, and IMO you will see no ill effects from doing so, I am unsure of whether or not the Tegra 2 has thermal throttling/shut down, but in my experience they should be fine to around 80C.
The only issue I can forsee is the battery, batteries HATE high temperatures and it is awful for their life span, this is why your laptop batteries turn to crap after 1-2 years, even if low charge cycles, because they are always hot.
I would not be concerned about anything in the 70C realm, at all.
Alcapone263 said:
There is a bug with faux's kernel that causes the webtop to clock the phone at max speeds until restart.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Experienced this countless times. More with the latest 1.45Ghz, but it did happen on the previous release. When I dopped the mhz with setcpu, it wont scale but stay at max cpu. It even did it a few times without using the webtop.
g2tegg said:
Experienced this countless times. More with the latest 1.45Ghz, but it did happen on the previous release. When I dopped the mhz with setcpu, it wont scale but stay at max cpu. It even did it a few times without using the webtop.
Click to expand...
Click to collapse
So which overclocked kernel is best for webtop? I too have noticed where the CPU hangs at 100% at 1.45Ghz for a while when disconnected but it is always there when im in webtop mode.... How is Faux 1.3Ghz kernel with webtop?
ericemir said:
So which overclocked kernel is best for webtop? I too have noticed where the CPU hangs at 100% at 1.45Ghz for a while when disconnected but it is always there when im in webtop mode.... How is Faux 1.3Ghz kernel with webtop?
Click to expand...
Click to collapse
It will still hang at 1.3ghz, though it's a known bug. I just stick with the 1.0 enhanced, there's no noticeable real-world difference from going over 1.0ghz anyway, it's just a benchmark gimmick. Right now, the software that's out there is optimized to run on existing hardware w/o overclocks. I've run Shadowgun at 1.45ghz and didn't see any difference over the 1.0 enhanced.
Now, if we were trying to run games that were coded specifically or faster-paced chipsets then we'd need overclocking to catch up much like you would in the PC arena. That, however, is not happening in the cell phone market just yet.
treehumper said:
I just stick with the 1.0 enhanced, there's no noticeable real-world difference from going over 1.0ghz anyway, it's just a benchmark gimmick.
Click to expand...
Click to collapse
What's the advantage to running a custom kernel if you're not overclocking? Forgive me if this is a stupid question lol. Still a noob.
cjrhoades said:
What's the advantage to running a custom kernel if you're not overclocking? Forgive me if this is a stupid question lol. Still a noob.
Click to expand...
Click to collapse
Bump.
Anyone?
cjrhoades said:
Bump.
Anyone?
Click to expand...
Click to collapse
Read the history at the following:
http://forum.xda-developers.com/showpost.php?p=15387385&postcount=1
You will see a lot more optimization than just upping the clock speed. One of the reasons the 1.0GHz kernel works much better than the stock kernel. Also, the ability to undervolt saving battery life.
IMO there is no need for 1.3GHz or 1.45GHz in everyday use of a phone. The only benefit is for OC'ing bragging rights. Until we can control phone temperatures better, it's pointless to risk the substantial heat increase on ALL internal components for extended periods of time which results from much increased CPU temperatures.
CaelanT said:
Read the history at the following:
http://forum.xda-developers.com/showpost.php?p=15387385&postcount=1
You will see a lot more optimization than just upping the clock speed. One of the reasons the 1.0GHz kernel works much better than the stock kernel. Also, the ability to undervolt saving battery life.
IMO there is no need for 1.3GHz or 1.45GHz in everyday use of a phone. The only benefit is for OC'ing bragging rights. Until we can control phone temperatures better, it's pointless to risk the substantial heat increase on ALL internal components for extended periods of time which results from much increased CPU temperatures.
Click to expand...
Click to collapse
I see... guess that explains why the phone doesn't really feel any faster when it's overclocked. I'll flash the 1GHz kernel then.
Thanks for the info.
Not sure if this is the same with phones but normally a CPU should stay at 40C idle and 50C load. Maximum would be 60C while benching or something.
If it goes above that I would definitely underclock/undervolt.
cjrhoades said:
what's the advantage to running a custom kernel if you're not overclocking? Forgive me if this is a stupid question lol. Still a noob.
Click to expand...
Click to collapse
also has other fixes besides overclocking you can go read them in the kernel threads

Icecream Sunday Final + Lag

I installed Icecream Sunday Final (very nice rom btw), but the phone lags often. For example, when I unlock it, it can be frustratingly long to be able to launch any applications right away. There is always at least 100mb of ram free, so I am not sure what causes this.
Does anyone have any advice? Has this happened to any other ICS users?
Are you using an OC Kernel?
If so, I read around here on the forums that you should increase your minimum CPU speed a bit and that should clear up the lag when unlocking the phone. Haven't tried it myself since I am running theMyth - ICS Lite, but am going to go back to Cyanogenmod (once of the things that peeved me on Cyanogen was exactly this; lag after unlock).
Hope this helps
Gooner88 said:
I installed Icecream Sunday Final (very nice rom btw), but the phone lags often. For example, when I unlock it, it can be frustratingly long to be able to launch any applications right away. There is always at least 100mb of ram free, so I am not sure what causes this.
Does anyone have any advice? Has this happened to any other ICS users?
Click to expand...
Click to collapse
hi you have to flash a kernel (you ll find all the information needed in the ic sunday topic)
i did do that and its far better
Either you set your min. frequenzy to 245Mhz or just use smartass gov. @ 122Mhz. I prefer smartass @ 122Mhz and there no lag.
PS: I´m using the same rom but with SlaidFastMod V2
I'm having wake-up lag too! But I already gave up thinking that the SGA's CPU just sucks. Thanks for this info GerasVille, I did not think to tinker with the System settings of CyanoGen because of the "Dragons Ahead" prompt. I will try this smartass setting to see if the wake-up lag will be removed. It sucks when I have to send an emergency SMS and my phone is lagging like hell.
Anyway so let me get this straight. Does having the minimum CPU clocked at 122mhz mean that if the device is inactive, it dynamically clocks down the CPU to 122mhz to save battery? Hence the wake-up lag is caused by the CPU being clocked back up?
I'm also gonna try out slaidfastmod to see if it makes it even better.
You can put up with the lag and save a tiny bit of battery life, or speed up the CPU and lose some battery life. Whichever you feel is more useful. Personally I don't mind the small unlock delay. Happens on most phones low powered anyway.
Sent from a phone with an app.
Eniac77 said:
Are you using an OC Kernel?
If so, I read around here on the forums that you should increase your minimum CPU speed a bit and that should clear up the lag when unlocking the phone. Haven't tried it myself since I am running theMyth - ICS Lite, but am going to go back to Cyanogenmod (once of the things that peeved me on Cyanogen was exactly this; lag after unlock).
Hope this helps
Click to expand...
Click to collapse
The kernel that is currently installed is "2.6.35.7-perf-CL562111" Ketut-lenovo #4. I am not sure if it is an OC kernel.
GerasVille said:
Either you set your min. frequenzy to 245Mhz or just use smartass gov. @ 122Mhz. I prefer smartass @ 122Mhz and there no lag.
PS: I´m using the same rom but with SlaidFastMod V2
Click to expand...
Click to collapse
I installed SlaidFastMod v2, set governor to Smartass and min CPU frequency to 245 MHz and this fixed the issue! It's much smoother when unlocking.
Is it safe to tick the "Set on boot" setting for CPU settings?

[Q] my note blacked out

so...my note is rooted with OC and on CWM beta 3. i even have flashed a battery percentage status bar mod (after many tries and lots of FC's issues) i finally got everything stable on a stock rom oc'd at 1.8 and this thing was sick dude...i mean so fast and big and bright and perfect...no problems except for 1...was getting random reboots...3 a couple days ago while using boat browser every mtime so uninstalled and started using dolphin. worked great until 1 rando reboot today while on dolphin browser...i figure no big deal it happens when you tweak your phone...but then all of a sudden it did something different just now it did...it just randomly rebooted while toggling wifi on except after it booted back up i couldn't unlock the screen or get into the launcher and the screen went black and unresposive. power button did nothing even holding it down...i pulled the battery out and then back in and restart and phoone booted up normally. clear as a bell and lightning fast...
so i just dialed down the oc to 1700...hope it's all good though...can't think why it would do this...
thanks?
Your phone can't handle the 1.8 ghz overclock.
When overclocking, no 2 chipsets will perform the same. Some will be able to overclock to 1.8 and some will not.
zer0nine said:
Your phone can't handle the 1.8 ghz overclock.
When overclocking, no 2 chipsets will perform the same. Some will be able to overclock to 1.8 and some will not.
Click to expand...
Click to collapse
So then is this OK?
Well anyway I guess I'll post back with the results. Cuz I'm running that way now. Hope I don't brick this beauty.
All opinions welcome.
Sent from my SAMSUNG-SGH-I717 using xda premium
You won't brick by overclocking. If you run it at an unstable clockspeed for your phone, you'll just be getting constant reboots.
1782 mhz should be fine. Try benchmarking your phone using Quadrant and Antutu from the market to stress test your phone at that new CPU speed.
zer0nine said:
You won't brick by overclocking. If you run it at an unstable clockspeed for your phone, you'll just be getting constant reboots.
1782 mhz should be fine. Try benchmarking your phone using Quadrant and Antutu from the market to stress test your phone at that new CPU speed.
Click to expand...
Click to collapse
Thanks. I'm at 3723.....phone feels good.
Sent from my SAMSUNG-SGH-I717 using xda premium
yup, sounds like classic too-overclocked symptoms to me. Back it down a notch like you have already done and try again...

[Solution] Solving Doom Kernel Reboots!

I found a solution to fix the Doom kernel reboots for those who are unable to download stock roms from HTC (Rogers Customers). Requires CWM Recovery.
1. Download stock kernel here - http://www.box.com/s/7dc3bf2adc9e2f05b717
2. Unzip archive
3. Move Zip file to SD card
4. Reboot into bootloader fastboot reboot-bootloader
5. Flash the img file fastboot flash boot name.img
6. Go into CWM and install the zip.
This solved my problem, hopefully it works for you guys too.
This should work on ALL devices not just Rogers
it doesn't actually solve the kernel issues...
your just replacing him.
i still think his kernel has a lot more potential than the stock.
It fixed my issue.
I care more about having a functional tablet than a kernel that may have more potential but is buggy as hell.
i agree. and i'm running the stock as well.. just wished the doomlord one would work as well.
Hi there,
Noob user here.
I got HTC JetStream from previous owner with doomlord Kernel on it.
Tablet is constantly crashing for no logical reason which leads me to believe that the kernel is causing this issue.
I would like to flash back to the stock kernel only as my device (Rogers) is running a stock image.
I am having difficulties to follow your instructions.
Wold somebody be so kind to post more detailed process steps to complete this kernel flashing back to stock.
Thank you very much.
I had the same random reboots using Doom's kernel until i overclocked it to the maximum. It's been almost 2 weeks since i experienced any reboots....
Sent from my Inspire 4G using xda premium
could you be more specific?
did you set both the minimum and the maximum to the maximum?
did u change the voltage?
Yes I changed the min & max all the way to max.. not sure if it will have some long term effects on my tablet, but it's been working great for a while now.
Sent from my HTC PG09410 using xda premium
lol... so the "solution" to the DooM kernel reboots is to not use the DooM kernel. Brilliant.
If I find some time this weekend, I'll try maxing out the O/C though and see how it goes, as I do find the DooM kernel snappier, even at stock speeds.
craig0r said:
lol... so the "solution" to the DooM kernel reboots is to not use the DooM kernel. Brilliant.
If I find some time this weekend, I'll try maxing out the O/C though and see how it goes, as I do find the DooM kernel snappier, even at stock speeds.
Click to expand...
Click to collapse
You do realize that by doing that you are running your kernel at max speed constantly which means additional heat, stress and wear on all systems?
ATT Intruder said:
You do realize that by doing that you are running your kernel at max speed constantly which means additional heat, stress and wear on all systems?
Click to expand...
Click to collapse
No, it won't run at max speed constantly unless I set the governor to "performance" mode. In "interactive" mode, which I believe is the default, it will still clock the CPU at its minimum value until the tablet needs more CPU resources, such as when scrolling, loading a webpage, playing a game, etc.
But yes, I'm aware of the risks of overclocking. I've overclocked every HTC device I've had very few problems (my One XL has exhibited some bootloops, so I've stopped O/C'ing it.)
craig0r said:
No, it won't run at max speed constantly unless I set the governor to "performance" mode. In "interactive" mode, which I believe is the default, it will still clock the CPU at its minimum value until the tablet needs more CPU resources, such as when scrolling, loading a webpage, playing a game, etc.
But yes, I'm aware of the risks of overclocking. I've overclocked every HTC device I've had very few problems (my One XL has exhibited some bootloops, so I've stopped O/C'ing it.)
Click to expand...
Click to collapse
I'm running 1.83 ghz ondemand with also the lowest setting for the min freq setting. I will increase it to 1.944ghz ondemand as the max setting and increase my min setting to 756Mhz on deadline, and see if the reboots stop, otherwise I will have to install the stock kernal.
I am just wondering if I install the stock kernel on top of my OziMood rom, if this will cause Rom problems?
Any thoughts on this?
globalgpj said:
I'm running 1.83 ghz ondemand with also the lowest setting for the min freq setting. I will increase it to 1.944ghz ondemand as the max setting and increase my min setting to 756Mhz on deadline, and see if the reboots stop, otherwise I will have to install the stock kernal.
I am just wondering if I install the stock kernel on top of my OziMood rom, if this will cause Rom problems?
Any thoughts on this?
Click to expand...
Click to collapse
I have mine on max: 1.62 ghz , min: 594 onDemand and it hasn't crashed in two or three days. So we'll see. Now to answer your question, if you want to flash back to stock on that Rom you'll have to install the stock WiFi modules from recovery. After that everything should work normally.
AlexFG said:
I have mine on max: 1.62 ghz , min: 594 onDemand and it hasn't crashed in two or three days. So we'll see. Now to answer your question, if you want to flash back to stock on that Rom you'll have to install the stock WiFi modules from recovery. After that everything should work normally.
Click to expand...
Click to collapse
Thanks for that.
So far, I haven't had anymore reboots.
Increasing the minimum seems helpful.
I get plenty of battery life, so I am really happy about this for now.
Just a quick update.
I've been running 1.944 GHz as my high setting and 756 GHz as my low setting for some time now and I have to say, no reboots, no lag, super fast and stable.
Sent from my HTC Jetsream using xda premium
Nice, I'll try those frequencies on mine. Thanks for sharing.
Sent from my Galaxy Nexus using xda app-developers app

Categories

Resources