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.
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.
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
So,
We've all got our Xooms, what are you experiences with each kernel, which one do you find the best? (and with what governors?)
Secondly, What are your UV values? Whats the best you've got when trying to undervolt?
Ive just got my Xoom (32gb, wifi, uk) and im just on the brink of experimenting with the undervolting, i searched but couldn't find a relevent topic.
So please, do post values, kernels and your experiences
ah okay, I thought this would be quite an important issue,
I've managed to get the xoom to handle 1.6 undervolting each state by 100mv
I am however having trouble getting both cores to stabilse at 1.6. Using os monitor I can see that only one core sticks, the other goes down to 300 mhz,.
tremblingwater said:
So,
We've all got our Xooms, what are you experiences with each kernel, which one do you find the best? (and with what governors?)
Secondly, What are your UV values? Whats the best you've got when trying to undervolt?
Ive just got my Xoom (32gb, wifi, uk) and im just on the brink of experimenting with the undervolting, i searched but couldn't find a relevent topic.
So please, do post values, kernels and your experiences
Click to expand...
Click to collapse
I haven't fooled around with over/undervolting, but I like the oc gpu version of the Tachi kernel.
Zero problems and very smooth. I am very stable at 1504MGh
okantomi said:
I haven't fooled around with over/undervolting, but I like the oc gpu version of the Tachi kernel.
Zero problems and very smooth. I am very stable at 1504MGh
Click to expand...
Click to collapse
what you using for OC?
Setcpu or pimp my cpu or anything else.
Which governor you use?
I had lots of rebooting with setcpu especially after applying voltages.
rohit3192 said:
what you using for OC?
Setcpu or pimp my cpu or anything else.
Which governor you use?
I had lots of rebooting with setcpu especially after applying voltages.
Click to expand...
Click to collapse
I use CPU Master for oc and setting profiles. I do have the oc set on boot, because 1504 is my sweetspot and is stable.
Just installed Moray+tachi
Mobo player freezed few times,rest ok.
Edit: Trying "No frills" discarded Set Cpu for now.
rohit3192 said:
Just installed Moray+tachi
Mobo player freezed few times,rest ok.
Edit: Trying "No frills" discarded Set Cpu for now.
Click to expand...
Click to collapse
No Frills is good, but I don't know if you can set profiles, which are good to save battery, control overheating, etc...
I loaded the Blades 2 kernel on my TF along side the Revolver ROM.
How can I tell if the OC is safe and working? I am not sure if you stress test it or anything like you do on a Windows PC type device..
acdcking12345 said:
I loaded the Blades 2 kernel on my TF along side the Revolver ROM.
How can I tell if the OC is safe and working? I am not sure if you stress test it or anything like you do on a Windows PC type device..
Click to expand...
Click to collapse
I've found that, in overclocking several Android devices, more often than not if you have an unstable OC, the device will either fail to boot, or will crash constantly. If it's not doing that, you're likely fine.
Um, you're not OCed yet. You need to install setcpu or cpu master and crank up the clock. Clemsyn or Blades gives you the option to OC. It doesn't just OC for you.
lol, and learn from my mistake: when overclocking, don't check the option of "set on boot" untill you have tried overclocking at the Ghz level that you want to use. Believe me, you don't want a bootloop that can only be solved by flashing or restoring from a backup.
acdcking12345 said:
I loaded the Blades 2 kernel on my TF along side the Revolver ROM.
How can I tell if the OC is safe and working? I am not sure if you stress test it or anything like you do on a Windows PC type device..
Click to expand...
Click to collapse
I have done extensive overclocking and undervolting.
Set your OC and voltage settings. Then use setcpu or pimpmycpu min and max to your highest OC MHz.
Then play 1 round of Dungon Defenders. If you make it through that then open the camera.
Repeat this on every MHz from top to bottom. If you are unstable at a frequency then increase your voltage slightly (like 10 - 20 mV) and try again.
If you are stable and want to get a little bit better battery do the same thing but lower the mV until dungeon defenders crashes.
Then start to increase it until you are stable.
If your tablet reboots your way low on mV
If it freezes your low on mV
If the widgets act funny, and/ or disapear every once in awhile your in the right ball park
If everything works except your camera freezes you are very close
Some kernels have more aggressive GPU timings which you can't really change so you might want to try another's kernel if you can't get stable.
Well, it seems that I can't go higher than the 1.2 GHZ. If I go any higher, I get some weird freezes and reboots.
Now I saw the post above but I dont see where I can adjust the different voltages, etc..Maybe I am not using the right program?
acdcking12345 said:
Well, it seems that I can't go higher than the 1.2 GHZ. If I go any higher, I get some weird freezes and reboots.
Now I saw the post above but I dont see where I can adjust the different voltages, etc..Maybe I am not using the right program?
Click to expand...
Click to collapse
What program are you using? Try SetCpu or Pimpmycpu
baseballfanz said:
What program are you using? Try SetCpu or Pimpmycpu
Click to expand...
Click to collapse
SetCPU is what I loaded
acdcking12345 said:
I loaded the Blades 2 kernel on my TF along side the Revolver ROM.
How can I tell if the OC is safe and working? I am not sure if you stress test it or anything like you do on a Windows PC type device..
Click to expand...
Click to collapse
Are you referring to this kernel?
I'm wondering because I have never heard about a "Blades 2" kernel.
EDIT: Nevermind, I figured it out. This is what Revolver Parts calls Blades' 10-01-2011 kernel.
Blades uses some aggressive GPU timings in some of his kernels. You may want to try Clemsyn 22 if you want to try and go above 1.2 GHz.
I'm on ViperXL 3.22 and use ElementalX JB kernel. I have over-clocked the processor to min-192MHZ, max- 1890 MHz and have done nothing with voltages. I'm achieving a fairly high Quadrant score, in the 7K region, but noticed today that incoming phone calls are starting to break before I or my calling party hangs up.
Does anyone know, or think, this may be caused by my over/under clocking the processor, or something else? I'd appreciate any and all comments.
JohnnyMac999 said:
I'm on ViperXL 3.22 and use ElementalX JB kernel. I have over-clocked the processor to min-192MHZ, max- 1890 MHz and have done nothing with voltages. I'm achieving a fairly high Quadrant score, in the 7K region, but noticed today that incoming phone calls are starting to break before I or my calling party hangs up.
Does anyone know, or think, this may be caused by my over/under clocking the processor, or something else? I'd appreciate any and all comments.
Click to expand...
Click to collapse
have you tried reflashing to see if that fixes it?
JohnnyMac999 said:
I'm on ViperXL 3.22 and use ElementalX JB kernel. I have over-clocked the processor to min-192MHZ, max- 1890 MHz and have done nothing with voltages. I'm achieving a fairly high Quadrant score, in the 7K region, but noticed today that incoming phone calls are starting to break before I or my calling party hangs up.
Does anyone know, or think, this may be caused by my over/under clocking the processor, or something else? I'd appreciate any and all comments.
Click to expand...
Click to collapse
What do you mean by "breaking"?
JohnnyMac999 said:
I'm on ViperXL 3.22 and use ElementalX JB kernel. I have over-clocked the processor to min-192MHZ, max- 1890 MHz and have done nothing with voltages. I'm achieving a fairly high Quadrant score, in the 7K region, but noticed today that incoming phone calls are starting to break before I or my calling party hangs up.
Does anyone know, or think, this may be caused by my over/under clocking the processor, or something else? I'd appreciate any and all comments.
Click to expand...
Click to collapse
are you using the defaut or aosp lockscreen?
I notice that over in the ViperXL thread there is some suggestion that using the aosp lockscreen might be the reason behind some people having calls drop out.
Calls Breaking
All I've done so far is to reset both processors back to Hi Freq Max=1517MHz. Seems to have done the trick.Back down to the low 6K's in Quadrant now though...
fordraimo said:
have you tried reflashing to see if that fixes it?
Click to expand...
Click to collapse
Calls Breaking
I mean that they end without hanging up. Suddenly I would hear a beep and I'd be back to the dialer screen.
..Cory.. said:
What do you mean by "breaking"?
Click to expand...
Click to collapse
Calls Breaking
Default. Lowering Max Freq in my kernel seems to have helped. Thanks
cr1960 said:
are you using the defaut or aosp lockscreen?
I notice that over in the ViperXL thread there is some suggestion that using the aosp lockscreen might be the reason behind some people having calls drop out.
Click to expand...
Click to collapse