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.
Related
Hi all,
I've been having random reboots/freeze-ups ever since I rooted.
This happens regardless of whether I am OC'ed or at 1ghz. These reboots tend to happen when watching Youtube or when browsing.
Would just like to have a feel of the ground if any of you who are rooted experiencing this?
Maybe we can start off by stating the following:
Kernel:
Clock Speed:
OC app: Setcpu or Droid OC
Governor setting: Interactive, on-demand etc..
Last app you were in that caused reboot:
For me, I am on the following:
Kernel: Tiamat 1.41
Clock Speed: 1ghz or 1.2 ghz
OC app: Setcpu
Governor setting: Interactive
Last app you were in that caused reboot: Youtube, browser
Im not sure if this thread shld belong here but since this is Dev where most of us root and OC, I thought I'd ask it here and hopefully we spot some trends with regard to the reboots.
Pls dun flame me Thanks!
wrong section
Moved to Q&A.
I have the same issue - Canada WIFI version
same problem, Canadian WiFi Version.
Not sure if it's because I flashed 1.4.0 then flash 1.4.1 to get the external sd card to show up. But I noticed after I got the external sd card to work, my usbOTG started working too, but from what I've read that should have been removed in 1.4.1 for stability issues.
Same issue. Using the tiamat kernel. It happens with different apps so its not any one for me.
Sent from my Xoom using XDA App
Switch to Droid oc and delete setcpu. Worked for me. Interactive. On demand is junk on Xoom. I use on demand on DroidX.
The kernel will Max to 1504 causing reboot (on some Xooms). Some device can't handle 1504, mine included. Superuser will throw up an occasional user permission for Droid oc as it brings the MHz back down to user setting.
I was experiencing random reboots with the same kernel, mostly just browsing in Dolphin HD. I first stopped OC in setcpu but the reboots still occurred. Then I uninstalled/reinstalled Flash 10.2 and cleared Dolphin's data.
So far, it seems to be much more stable and even battery usage has toned down.
This shouldn't have been moved to Q&A. There is enough discussion at this point on this exact topic that it needs to be addressed. There is a serious problem with the over clock in the tiamat kernel and/or the software that is supposed to govern the overclock. The developers here work very hard for all of us to get the most out of our devices and I fully support them in their work, but we are putting ourselves at risk. It is my understanding that SETCPU and Droid Overclock are only able to govern One of the Dual Core processors while the other is overclocked all the time. There is a widget in the Marketplace (Temp+CPU V2) that will enable you to monitor your clock speeds.... See for yourself.
Sent from my Xoom using Tapatalk
I installed temp+CPU and don't see two cores. Only one display for MHz and it cycles from 216 to 1200. Is there a screen I'm missing?
crauzz said:
This shouldn't have been moved to Q&A. There is enough discussion at this point on this exact topic that it needs to be addressed. There is a serious problem with the over clock in the tiamat kernel and/or the software that is supposed to govern the overclock. The developers here work very hard for all of us to get the most out of our devices and I fully support them in their work, but we are putting ourselves at risk. It is my understanding that SETCPU and Droid Overclock are only able to govern One of the Dual Core processors while the other is overclocked all the time. There is a widget in the Marketplace (Temp+CPU V2) that will enable you to monitor your clock speeds.... See for yourself.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
This is right where it should be... Development forum is for developing...Discussing does not go there unless its in a thread where something was developed...The tiamat crew knows all about it...they did not make the overclocking, they used someone elses, and are about to remove out. And yes you are correct on the 2nd core.
Sent from my PC36100
bwcorvus said:
This is right where it should be... Development forum is for developing...Discussing does not go there unless its in a thread where something was developed...The tiamat crew knows all about it...they did not make the overclocking, they used someone elses, and are about to remove out. And yes you are correct on the 2nd core.
Sent from my PC36100
Click to expand...
Click to collapse
Remove it? So no more overclocking? Can't a ROM allow OC and voltage control? But I guess it always comes back to the lack of source code.
Mandelbrot.Benoit said:
But I guess it always comes back to the lack of source code.
Click to expand...
Click to collapse
Kernel source is available. It's the rest of Honeycomb that isn't.
So what is the best resolution to the problem? I get at least 5-6 reboots a day...I dl'ed Droid OC and deleted setcpu.
I had a harder time getting it to reboot with Droid OC so I think that's your best solution for now.
Sent from my Xoom using Tapatalk
ruvanist said:
So what is the best resolution to the problem? I get at least 5-6 reboots a day...I dl'ed Droid OC and deleted setcpu.
Click to expand...
Click to collapse
Flash back the stock kernel.
solarnz said:
Flash back the stock kernel.
Click to expand...
Click to collapse
This is probably the best thing to do. If you think about it; Can't be good if your device is rebooting all the time, plus it's just too annoying.
Sent from my Xoom using Tapatalk
crauzz said:
This is probably the best thing to do. If you think about it; Can't be good if your device is rebooting all the time, plus it's just too annoying.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
Where can I find the stock kernel? Is it available in xda? Cos i did not back it up.
ruvanist said:
Where can I find the stock kernel? Is it available in xda? Cos i did not back it up.
Click to expand...
Click to collapse
Yes. Go here > http://forum.xda-developers.com/showthread.php?p=13178555
Sent from my Xoom using Tapatalk
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
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...
well I just got my xoom and its overclockable to like 1.6ghz but I wannna make sure my device life won't go down, also what are good temps what should I try to keep the temperature under. Simply what temps are you guys getting
Thanks guys
Most people stay under 1.7 ghz because the processor becomes unstable (rebooting, freezing up, etc.). There has been zooms that don't overclock very well above 1.5 ghz so you will have to play with it and see what works well for you. If you get freezing, and rebooting then just dial it back until you get the sweet spot. As far as temp, unless you are a extreme power use you should not see temp's 100 degrees, I am a power user and rarely get above 98 degrees. Hope this helps?
Sent from my Xoom
johnny0911 said:
Most people stay under 1.7 ghz because the processor becomes unstable (rebooting, freezing up, etc.). There has been zooms that don't overclock very well above 1.5 ghz so you will have to play with it and see what works well for you. If you get freezing, and rebooting then just dial it back until you get the sweet spot. As far as temp, unless you are a extreme power use you should not see temp's 100 degrees, I am a power user and rarely get above 98 degrees. Hope this helps?
Sent from my Xoom
Click to expand...
Click to collapse
Alright thanks buddy I'm currently at 1.2 and I'm in the 90s browsing and using YouTube
Oh what do you use for temp oh and also are you over clocked? Oh but I'm stable at 1.6 so idk how high to set it, what your opinion?
1.2 and your temp is at 90? I think your reading it wrong or something. I have mine at 1.6 and use it all day (even playing games) and it does not get to 90. What kind of case do you have it in? What rom/kernel are you using?
jucery said:
Alright thanks buddy I'm currently at 1.2 and I'm in the 90s browsing and using YouTube
Oh what do you use for temp oh and also are you over clocked? Oh but I'm stable at 1.6 so idk how high to set it, what your opinion?
Click to expand...
Click to collapse
no case using the new tiamat for xoom 2.2.2 it completely stable at 1.6 GHz but temps stay around 90-100 when using heavily. ambient temp is like 75, when i let it rest and its just locked its like 75-80
i run around 1.5 daily... with 1.6 for benchies...
temps are VERY cool for my tab... honestly it is astounding... my phone gets way hotter
jucery said:
no case using the new tiamat for xoom 2.2.2 it completely stable at 1.6 GHz but temps stay around 90-100 when using heavily. ambient temp is like 75, when i let it rest and its just locked its like 75-80
Click to expand...
Click to collapse
90 to 100? I have a otterbox defender case that completely encases my xoom, oc to 1.6, also on moray 2.2.2 and I have work really hard to get a temp of 98. Download battery monitor widget from the market (free or paid one) and see what your temp is. I think you are running a little hot.
Also, are you using a app to overclock or the built in setting under tiamat settings?
Sent from my Xoom
joshndroid said:
i run around 1.5 daily... with 1.6 for benchies...
temps are VERY cool for my tab... honestly it is astounding... my phone gets way hotter
Click to expand...
Click to collapse
Same here.
Sent from my Xoom
Another thing to check is your governor and wht is is set to (interactive, userspace, proformance, etc) if you have it set to proformance, you're gov will keep you at 1.6 all the time and could cause heat issues. Download a app called android system info (free in the market) and check your CPU info. I have provided a screenshot of what it looks like.
As you can see I'm at 1.2ghz only 21% of the time and 216, 58%.
https://dl-web.dropbox.com/get/Public/P20111026155145.png?w=640402e6
Sent from my Xoom
johnny0911 said:
90 to 100? I have a otterbox defender case that completely encases my xoom, oc to 1.6, also on moray 2.2.2 and I have work really hard to get a temp of 98. Download battery monitor widget from the market (free or paid one) and see what your temp is. I think you are running a little hot.
Also, are you using a app to overclock or the built in setting under tiamat settings?
Sent from my Xoom
Click to expand...
Click to collapse
Build in Tiamat setting, will download the app wait up
johnny0911 said:
Another thing to check is your governor and wht is is set to (interactive, userspace, proformance, etc) if you have it set to proformance, you're gov will keep you at 1.6 all the time and could cause heat issues. Download a app called android system info (free in the market) and check your CPU info. I have provided a screenshot of what it looks like.
As you can see I'm at 1.2ghz only 21% of the time and 216, 58%.
https://dl-web.dropbox.com/get/Public/P20111026155145.png?w=640402e6
Sent from my Xoom
Click to expand...
Click to collapse
Yeah i just came back from work my xoom was sitting at around 72 F without using it, do you Recommend using tiamat setting or setcpu or anything else. thanks +1
jucery said:
Yeah i just came back from work my xoom was sitting at around 72 F without using it, do you Recommend using tiamat setting or setcpu or anything else. thanks +1
Click to expand...
Click to collapse
I use the tiamat settings, I have not seen any reason to use anything else. 72 degrees is good when not in use for some time.
Sent from my Xoom
use the tiamat settings. I dont have my xoom in front of me but i keep it set on "on demand" i think. You xoom is running hot. I would lower it OC until you find the sweet spot for your heat issue. I think your xoom will run fine but you will start to kill the "life" of the xoom IMO.
NissanNick said:
use the tiamat settings. I dont have my xoom in front of me but i keep it set on "on demand" i think. You xoom is running hot. I would lower it OC until you find the sweet spot for your heat issue. I think your xoom will run fine but you will start to kill the "life" of the xoom IMO.
Click to expand...
Click to collapse
I think the reason he is running hot is do to his governor settings, when I first started playing with overclocking I noticed my xoom would run hotter when I would increase the preformance. But I agree if he is running 90 to 100 degrees regularly, there is a problem somewhere.
Sent from my Xoom
I have my Xoom overclocked to 1.2 and when I give it on 1.4 it becomes pretty unstable. Temp is always ok. So angry I can't have higher OC. :/
DomButcher said:
I have my Xoom overclocked to 1.2 and when I give it on 1.4 it becomes pretty unstable. Temp is always ok. So angry I can't have higher OC. :/
Click to expand...
Click to collapse
What rom and kernel are you using?
Sent from my Xoom
[email protected]
Temps is near 80, sometime it goes to 90-95 but that when I play some game/watch movie. Its pretty stable, never crashed and I ran a stress test from 100% to 0%.
Sent from my Xoom using xda premium
DomButcher said:
I have my Xoom overclocked to 1.2 and when I give it on 1.4 it becomes pretty unstable. Temp is always ok. So angry I can't have higher OC. :/
Click to expand...
Click to collapse
It's not really a race...the cpu is only rated to 1GH so anything you can squeeze out above that and still remain stable is gravy, don't you think? In Xoom as in life--YMMV.