Morning all,
I am running the Hammerhead ROM with the OC GPU kernel. I have been able to run at 1.6 GHZ with no issues. When I push it to 1.7 GHZ I get alot of browser closes, hangs, and reboots.
Has anyone been able to run reliably at 1.7 GHZ with the OC GPU kernel, and if so are you doing anything special with voltages to get this to run reliably?
Thanks,
Steve
stevefxp said:
Morning all,
I am running the Hammerhead ROM with the OC GPU kernel. I have been able to run at 1.6 GHZ with no issues. When I push it to 1.7 GHZ I get alot of browser closes, hangs, and reboots.
Has anyone been able to run reliably at 1.7 GHZ with the OC GPU kernel, and if so are you doing anything special with voltages to get this to run reliably?
Thanks,
Steve
Click to expand...
Click to collapse
Each device and each Tegra chip are slightly different..some will run that fast without any problem, some can do it in bursts, while others will crash before you close SetCPU. It often has very little to do with settings.
I had the same issue as you. At 1.6, it has never rebooted, but at 1.7 it very consistently reboots or forces a close.
qsg001 said:
I had the same issue as you. At 1.6, it has never rebooted, but at 1.7 it very consistently reboots or forces a close.
Click to expand...
Click to collapse
I am going to fool around with voltages and see if I can get 1.7 Ghz to stabilize.
same here.. i had no reboots but some force closes when i really push the device with 1.7 ghz ( tiamat kernel&3.2) ... if depends on the load of the cpu i guess.. when i run quadrant test continuously it works without a problem even a non-stop half hour.. but when i open 15+ pages in theb browser it freezes and sometimes forse closes.. i assume the voltage management is not stable or enough for 1.7 ghz .. when its 1.6 its perfect.. ( to be honets none of this gpu and cpu overclocks are really necessary and effecting my everyday usage, its already a very fast and good device)
Hi guys!
Which app are you using to control the clock?
Schellin said:
Hi guys!
Which app are you using to control the clock?
Click to expand...
Click to collapse
SetCPU is the best for the Xoom, imho.
Sent from my GT-I9000 using XDA Premium App
Sorry man. It's been said before about the tegra and other procs, it's all luck of the draw. I am one of the lucky ones who can get stable at 1.7ghz but it won't work for everyone. I wish there was an easy fix that would make this work for you.
Related
I have been looking for a couple of days, and I can't seem to find my answer anywhere. Sorry if this question has already been asked. Does the Tiamat Kernel come overclock already, or do you need to use an app like SetCPU?
SetCPU is needed
Thank Brenardo.
I really want to root so i can get the USB host, and SD card. I just didn't want the overclock. I was told that Tiamat was overclock from the get go.
anovinger said:
Thank Brenardo.
I really want to root so i can get the USB host, and SD card. I just didn't want the overclock. I was told that Tiamat was overclock from the get go.
Click to expand...
Click to collapse
If you do not run an overclock program, the stock max is still on the CPU.
Sent from my Xoom
Do you know what the set Max is on the tiamat kernel?
anovinger said:
Do you know what the set Max is on the tiamat kernel?
Click to expand...
Click to collapse
1ghz
Sent from my Xoom
bwcorvus said:
1ghz
Sent from my Xoom
Click to expand...
Click to collapse
even without an OC app running my CPU sometimes runs up to 1504mhz. I've tried every kernel since the first tiamat one. I have a Canadian xoom rooted with one click. I'm using tiamat 1.4.1 and the issue isn't fixed. I've read many others experiencing the same issue. I've tried using setcpu and Droid OC to limit it to 1ghz but it still hits 1504. There both uninstalled now but I'm still having spikes. Just my 2 cents not trying to hyjack your thread. But if anyone has any input as to whats happening I'd appreciate it.
Also my battery life is significantly shorter since rooting. From about 9 hours to 4 now.
Any suggestions ?
Bandit504 said:
even without an OC app running my CPU sometimes runs up to 1504mhz. I've tried every kernel since the first tiamat one. I have a Canadian xoom rooted with one click. I'm using tiamat 1.4.1 and the issue isn't fixed. I've read many others experiencing the same issue. I've tried using setcpu and Droid OC to limit it to 1ghz but it still hits 1504. There both uninstalled now but I'm still having spikes. Just my 2 cents not trying to hyjack your thread. But if anyone has any input as to whats happening I'd appreciate it.
Also my battery life is significantly shorter since rooting. From about 9 hours to 4 now.
Any suggestions ?
Click to expand...
Click to collapse
How are you seeing its over with no app? I'm not calling you a liar, just trying to get all the facts. In all test we have done, even with the setcpu oc to 1.5/1.5, we actually see the cpu running at 1 ghz after a wakeup.
Sent from my PC36100
bwcorvus said:
How are you seeing its over with no app? I'm not calling you a liar, just trying to get all the facts. In all test we have done, even with the setcpu oc to 1.5/1.5, we actually see the cpu running at 1 ghz after a wakeup.
Sent from my PC36100
Click to expand...
Click to collapse
I'm watching the temp+CPU widget to monitor what's happening. Are you suggesting its giving inaccurate readings? Setcpu at 1ghz would still show random spikes to 1504mhz. I don't have any OC tools installed right now but my widget still shows it hitting 1504 especially under load. I was thinking of returning to stock and rooting manually but it not a huge problem just strange. I was hoping the new kernel would fix it but its still happening. Is there anything I can do besides start from scratch?
Bandit504 said:
I'm watching the temp+CPU widget to monitor what's happening. Are you suggesting its giving inaccurate readings? Setcpu at 1ghz would still show random spikes to 1504mhz. I don't have any OC tools installed right now but my widget still shows it hitting 1504 especially under load. I was thinking of returning to stock and rooting manually but it not a huge problem just strange. I was hoping the new kernel would fix it but its still happening. Is there anything I can do besides start from scratch?
Click to expand...
Click to collapse
Yea setcpu is not 100% yet. Does your widget show both cpus? What we were testing was the second CPU. After you xoom goes to sleep, the second CPU is never set again by setcpu (known bug). So lets say you are running 1.0/1.5. After you xoom goes to sleep you will wake up with cpu 0 at a max of 1.5, but cpu 1 will have a max of 1.0. The info i gave earlier was said wrong. I was actually looking at the wrong line, so you may in fact be correct on the 1.5ghz random jump . Gonna stop talking now, as we are hyjacking someone else's thread .
In theory, you should not need overclocking software, as the max is set at 1ghz on both cpus. But as said above by Bandit504, this may NOT be the case .
Thanks bwcorvus and Bandit504 . So I guess to call it is safe, it would be good idea to use SetCPU, or Droid Overclock and have the maximum set to 1 ghz, to keep the proc from hitting the 1.5 ghz speed. I just hate to ruin the hardware with the overclock, and have to drop another $600 for another xoom.
Ok, sorry if this seems like a stupid question but... I have flashed/tested all of the Tiamat Kernels onto my xoom and it seems that I can only run the 1.4 Ghz Kernel with no random reboots. So I thought that if i download the higher 1.5Ghz or the 1.6Ghz and just under-clock it to 1.4Ghz that should stop it from doing random reboots, but sadly it doesnt and I still get random reboots even with Setcpu Under-clocking it to 1.4Ghz. Now is this typical or am I missing or misunderstanding something? Is there a reason why I cant use the higher Kernels and Under-clock them to 1.4Ghz and get no random reboots? I am only asking because I flashed the Riptide and under-clocked it to 1.4Ghz and it really made my xoom feel much faster and nicer in my hands and would love to keep using the Riptide Kernel.
Thanks in advance,
-Dez
I have the same issues and have been wondering the same thing.
I have similar , with 1.6 with ums
only flashed to get ums , and had a few crash/reboots for the first time since i bought my xoom about a month ago.
what i could do with is a stock speed kernal with all the bells on !
nexan21 said:
I have similar , with 1.6 with ums
only flashed to get ums , and had a few crash/reboots for the first time since i bought my xoom about a month ago.
what i could do with is a stock speed kernal with all the bells on !
Click to expand...
Click to collapse
I too have noticed this, after reading your post I tried keeping the Kernels but with no OC and left it at 1.0Ghz and it still has random reboots. So is there something in the Higher Kernels that are causing it to be unstable regardless of what Ghz you clock it to?
watch setcpu at times. It doesn't matter what you set the clock at in setcpu it will still go to the max clock the kernel allows. I am not sure if it is a bug with setcpu or if it is just the way the kernel works. If you reboot your Xoom when setcpu is at 1ghz, then go and play with the xoom after reboot for awhile. Go back into setcpu and look under the info tab. You will see that the cpu has indeed been running the higher clocks then 1ghz at times. It doesn't run those higher clocks much but it does. Which is most likely why you are getting lockups or reboots. My Xoom seems to love the 1.5ghz kernel but hates the 1.6ghz one.
Funny I was on the same boat. Started out with 1.6...reboots. went to 1.4 no problems. Tried riptide. Got app force closes. Now on 1.5...stable once again. The thing is im not even using OC on any of them
Sent from my SGH-T959 using Tapatalk
tribalb said:
Funny I was on the same boat. Started out with 1.6...reboots. went to 1.4 no problems. Tried riptide. Got app force closes. Now on 1.5...stable once again. The thing is im not even using OC on any of them
Sent from my SGH-T959 using Tapatalk
Click to expand...
Click to collapse
The oc is in the kernal i think , i dont have setcpu installed but cpu still at times peaks at the max 1.504 ghz ac ording to
"Temp+cpu"
https://market.android.com/details?id=com.sanels.tempcpuv2&feature=more_from_developer
So after being S-OFF and perm rooted, I have found that setCPU is being a turd. While it works when it works, it requires quite a bit of effort to work.
Each time my phone reboots for whatever reason (pitiful attempts at getting adfree to work, ect) setCPU must be uninstalled, then reinstalled, then set back up via command prompt. If this isnt done, it will cause the phone to restart over and over again.
Any ideas as to why this is?
Matt
Because SetCPU doesn't have a profile for the Sensation's processor yet.
Any good alternatives to setCPU then?
Matt
i have the same issue but no fix for OC Daemon, except restoring, flashing and setting the oc to 1.5. if i set to 1.8 it reboots and reboots and reboots and so on.
MT4gUY said:
i have the same issue but no fix for OC Daemon, except restoring, flashing and setting the oc to 1.5. if i set to 1.8 it reboots and reboots and reboots and so on.
Click to expand...
Click to collapse
This is never going to be fixed. Your phone can't handle 1.8 ghz, it's the hardware.
mrg02d said:
Any good alternatives to setCPU then?
Matt
Click to expand...
Click to collapse
If you flash a custom ROM and want overclock, flash Android Revolution HD. It has OC Daemon and is really good!
You can overclock to 1.5ghz and be quite stable. You can also underclock to about 245mhz when asleep so it saves the battery when it's in your pocket However, as MT4gUY said, right now you can't overclock to 1.8ghz.
@Sdobron As I understand it, the EVO 3D has overclock to 1.8ghz and that has the same processor as the Sensation...? Is that overclock stable...?
Sdobron said:
This is never going to be fixed. Your phone can't handle 1.8 ghz, it's the hardware.
Click to expand...
Click to collapse
This is incorrect. I was overclocked to 1.8 Ghz for the longest time before I decided to go down to 1.6Ghz (what I am at now) for battery reasons. 1.8Ghz was good for getting 3100 Quadrant scores, but that was it.
There must be a way to reliably overclock without a ROM? I dont see the need for a ROM right now. My phone is already fast! I use ADW EX with overclock, and I have bloatware frozen along with Sense frozen. I am perm rooted, but would love to be able to reboot my phone and not have setCPU act a fool.
Matt
I try and set my sensation to 1.9 (1.89)ghz on setcpu. Right after i set it up, the phone reboots and the setting is lost. I tried different apps but nothing changes. i have a custom setcpu setting and still nothing happens. It only works when i overclock to something under 1.9. Anyone else having the same problem? Disable perflock isn't working for me. If thats the solution, how to fix it?
Running SENSEaY - XE35 v2.1.0 with Bricked 1.5 kernel.
pranker98 said:
I try and set my sensation to 1.9 (1.89)ghz on setcpu. Right after i set it up, the phone reboots and the setting is lost. I tried different apps but nothing changes. i have a custom setcpu setting and still nothing happens. It only works when i overclock to something under 1.9. Anyone else having the same problem? Disable perflock isn't working for me. If thats the solution, how to fix it?
Running SENSEaY - XE35 v2.1.0 with Bricked 1.5 kernel.
Click to expand...
Click to collapse
Sounds like you weren't aware that 1.7GHz and higher aren't considered stable freqs, 1.9GHz has a high Voltage which may cause the kernel to panic and issue a reboot. Just stick with a lower freq around the 1.2 stock speed.
pranker98 said:
I try and set my sensation to 1.9 (1.89)ghz on setcpu. Right after i set it up, the phone reboots and the setting is lost. I tried different apps but nothing changes. i have a custom setcpu setting and still nothing happens. It only works when i overclock to something under 1.9. Anyone else having the same problem? Disable perflock isn't working for me. If thats the solution, how to fix it?
Running SENSEaY - XE35 v2.1.0 with Bricked 1.5 kernel.
Click to expand...
Click to collapse
Any CPU aren't the same. It seem that your CPU can't handle that much clock speed. Speed on 1.9 and 1.782 Ghz are quite the same. (Quadrant might shows couple hundreds higher but not effect any everyday uses.)
Ace42 said:
Sounds like you weren't aware that 1.7GHz and higher aren't considered stable freqs, 1.9GHz has a high Voltage which may cause the kernel to panic and issue a reboot. Just stick with a lower freq around the 1.2 stock speed.
Click to expand...
Click to collapse
Thanks for the heads up. Where'd you hear that? i dont remember reading about it. Is there a way to make 1.9ghz work?
What benefits will 1.9GHz provide other than wearing down your battery faster?
pranker98 said:
Thanks for the heads up. Where'd you hear that? i dont remember reading about it. Is there a way to make 1.9ghz work?
Click to expand...
Click to collapse
Just looking at that voltage table and my experiences with that freq from past phones tells me so . Jumping from the low level to such a high one should cause a freeze on any device.
@LooieEng 1.9GHz may help this phone run future Android revisions smoothly, and perhaps Win8 will function on the phone too.
ok so it was running ok with minimal lag now it lags like crazy where you cant even move at times with unexpected closes or pauses in the game. Very frustrating. Running Fp1 Stock
Any help appreciated
Works fine for me in Eclipse 2.0, even with conservative governor. My brother was on stock fp1 and he was lagging out so he made me root his phone and put eclipse on it
JihadSquad said:
Works fine for me in Eclipse 2.0, even with conservative governor. My brother was on stock fp1 and he was lagging out so he made me root his phone and put eclipse on it
Click to expand...
Click to collapse
Yeah thought about placing eclipse 2.0 on the phone although i couldnt get some of the stock apps to migrate with it Backup manager, Feeds & updates, Buddies Now, and the weather widget but, ill try
Whats conservative governor ?
babyjake said:
Whats conservative governor ?
Click to expand...
Click to collapse
It makes the CPU frequency go up slower to save battery. Basically in games it reduces performance if it doesn't demand max speed all the time.
I'm running Eclipse 2.0 as well but when I play Temple run o just overclock to 1.2 with smartassv2 governor and there's no lag at all.
Sent from my SCH-I510 using XDA
Interesting i guess i should try Eclipse 2.0 Just going to be hard to get used to not having my stock widgets
If I'm on Eclipse 2.0 with the stock FP1 kernel . What is the safest and most stable way to bump my Charge CPU up to 1.2 ghz ?
- I experienced quite a bit of lag as well while trying to play Temple Run .
The only way to do it on a stock kernel is with Tegrak Overclock from the Market. The free version will overclock. To make it stick on boot, you have to buy the pay version.
I was on FP1 stock and temple run was working fine without any lags. And yesterday I put the Tweaked v2.0 on my phone and now temple run lags a lot. Kinda weird
Sent from my SCH-I510 using XDA
the sandman89 said:
I was on FP1 stock and temple run was working fine without any lags. And yesterday I put the Tweaked v2.0 on my phone and now temple run lags a lot. Kinda weird
Sent from my SCH-I510 using XDA
Click to expand...
Click to collapse
Im Running Tweaks 1.4 with PBnJ at 1.2GHz with Smartass V2 and mine lags as well.
I suspect that this may be a memory contention problem. When I play Temple Run with my phone on Tweaked 2.1 with imnuts PBJ 0524, it's horribly laggy - if my Yahoo! Mail and Facebook (official) apps are either sitting in the background constantly hitting the network or trying to reload whenever OOM-killed. If I go to Titanium Backup and freeze those two, Temple Run becomes playable again.
There are a number of fat, pushy apps out there that just won't back off even when your phone is otherwise busy, including the two mentioned above. Try trimming your widgets and temporarily freezing things you don't want to uninstall, and you'll get a better user experience on heavyweight games like Temple Run.
ya I run my charge on tweaked 2.1 UV'd at 800mhz but I use tasker to OC my phone to 1.2 whenever I open a CPU intensive game it takes a second for it to run without lag but then it works with no problems
p2kmafia said:
ya I run my charge on tweaked 2.1 UV'd at 800mhz but I use tasker to OC my phone to 1.2 whenever I open a CPU intensive game it takes a second for it to run without lag but then it works with no problems
Click to expand...
Click to collapse
What does your setup look like to stay UVd (which you can't do in tasker afaik) while not in the game? I've played with some things, but they turned out to be kind of cumbersome.
BleedsOrangeandBlue said:
What does your setup look like to stay UVd (which you can't do in tasker afaik) while not in the game? I've played with some things, but they turned out to be kind of cumbersome.
Click to expand...
Click to collapse
I run:
100mhz -200
200mhz -150
400mhz -125
800mhz -100
1000mhz -75
1200mhz -50
I'm always UV'd at the 800 mark but I think when tasker overclocks me to 1.2ghz it keeps my UV settings but idk.
edit: I use smartass v2 governor
Whenever I would have tasker take over, I would later reopen Voltage Control and all the voltage settings would be reset to their standard values.
I actually just noticed that my tasker isn't actually doing anything lol. I'll set up the task and press the play (test) button and it'll work but then I'll go into an app I've set up and my max is set to 1200 but my phone is maxing at 800 still. I don't think that voltage control and tasker integrate very well and that might be your problem but my UV setting are intact.