Ok, I'm running infusion A2, not OC'd, UV'd 100 across the board just fine.
My problem starts fast when I OC to 1600, it rans ok there, for the few minutes I tested it at stock voltages. The problem is when I change ANY CPU step to UV it just crashes and reboots my phone instantly. Tried it 3 times. It comes back on fine, even if I left set as boot checked (accidentally), but the settings were not saved. Haven't tried B2 yet to see it is repeatable on 1400, and don't really want to repeat it at all.
Any ideas why this is happening? On Doctorz ROM using SetCPU to OC/UV.
Thanks y'all
Try voltage control instead (free in the market) but honestly, not all Infuses can handle 1.6 ghz. In your case, you are most likely right on the line of crashing at 1.6, when you change the voltages, you cross that line.
Its well know messing with the native clock speed can AT some phones and some times cause low stability and reboots also force closes etc. I suggest you to try lower OC speeds like 1.4 Ghz ive been running my Infuse on 1.4 forever without one single problem.
Yeah, was gonna go to B2 and try 1.4, but figured I would get some suggestions first.
Had VC at first, but didn't try OC, just UV, gonna try that tomorrow.
jonrobertd - did you flash a certain kernal to OC your Infuse? Everything I've read says either the Infuse can't be OCed. I even tried using SetCPU but it kept giving me errors when I'd run it, telling me something like "no profiles loaded" or something like that.
---------- Post added at 07:31 AM ---------- Previous post was at 07:25 AM ----------
koriotto said:
...ive been running my Infuse on 1.4 forever without one single problem.
Click to expand...
Click to collapse
koriotto - how are you overclocking your Infuse? What OS are you using (Froyo, GB, etc.)?
You have to have a kernel that supports overclocking....and yes the infuse can be overclocked...I'm running it at 1.6 myself on my rom....the infusion gb kernel can be overclocked....entropy's daily driver can't...the community kernel is Froyo....if your running gingerbread rom and flash the community kernel your phone will bootloop.....read...
Sent from my SAMSUNG-SGH-I997 using xda premium
Overclock to high frequencies and lower the voltage too much and the CPU becomes unstable. Some can handle it, some can't, all cpus are different.
Sent from my SAMSUNG-SGH-I997 using XDA App
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
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.
I am using Tsugi 2.3.4 with the Oyasumi 0.1 UV kernal I want to overclock to 1500 but what settings should I undervolt it to that is stable thanks in advance for the info.
DirtyPISTOLA said:
I am using Tsugi 2.3.4 with the Oyasumi 0.1 UV kernal I want to overclock to 1500 but what settings should I undervolt it to that is stable thanks in advance for the info.
Click to expand...
Click to collapse
We can't tell you not all phones are the same, uv a little (10 or 25) run it for a day or two see how it acts, if its steady, uv a little more, when it starts acting up thats your limit go back to previous settings.
NVIDIA NEVER AGAIN!
fcisco13 said:
We can't tell you not all phones are the same, uv a little (10 or 25) run it for a day or two see how it acts, if its steady, uv a little more, when it starts acting up thats your limit go back to previous settings.
NVIDIA NEVER AGAIN!
Click to expand...
Click to collapse
Alright thanks will try
Sent from my LG-P999 using Tapatalk
I've seen some general advice not to UV for anything over 1ghz speeds as well, but it may not hurt to try if you want and adjust as needed for stability.
I'm running on a -75mv at 1.5Ghz faux kernel 0.4.7..
Perfectly stable, benchmarked AnTuTu, Quadrant, and all those other good stuff.
I have not tried -100mv yet, I doubt it will be stable.
Every phone is different, but I run mine at -20 up to 1 G, and -10 for the rest.
Mine I cant undervolt shoot I have to keep my minimum frequency at 500 to be stable, course I can also run at 1.5 all day (I keep it at 1.2).
Well I guess I can't say I cant UV since I use pimp my cpu and it only gives you options in 25 increments, maybe I would be stable at like -10. But coming from my galaxy s 4g where I could UV over -150 and still be stable, that just doesnt even sound worth doing.
Edit: I just thought about it and maybe the reason I cant UV (more) is because I'm using fauxs pre UV/OC kernel, so I dont even know what stock voltage is. But comparing to my sgs4g at stock voltage I am running considerably lower voltages on the g2x.
The faux thread says it's pre uv at -50 across the board.
Beekersguy said:
The faux thread says it's pre uv at -50 across the board.
Click to expand...
Click to collapse
I been running it so long and flashed so many friends phones I can't even remember details anymore!
Sent from my LG-P999 using xda premium
Hello, I have a launch Evo Shift (almost a year old now), and am running Cyanogenmod Nightly 255 with a2ext and a ton of apps installed (above 200 apps running from a class 10 32gb card, dalvik cache on the card), and ScaryKernel with the smartass governor (max 1497 MHz). However, I sporadically get random reboots, gps not working (requiring a reset), camera reboots, and the rare "turn off" bug where it turns off while sleeping. In addition most recently I have a bug where every time that I reboot into clockworkmod recovery to back up , it resets almost all of my phone preferences.
I absolutely love cyanogenmod and appreciate the hell out of it and the work that has been done, but I'm wondering if these bugs are either due to running cyanogenmod nightlies or if I have a defective phone. I also have tried Sense-based roms such as Mikshifted, but the Sense memory overhead is just too large for me. I have no worries if the phone is defective, since I have sprint insurance and can wipe back to stock to exchange it. However, going through all the exchange, re-root and restore procedure would be a pain if its not necessary. Does anyone have any thoughts or advice?
Thanks in advance.
I don't think this is s shift problem. I experienced this myself and even had my phone replaced by sprint because i thought it was. Try not overclocking and see if that helps. Another way to test if its the phone is to see if you have these same problems on a sense rom
Sent from my PC36100 using xda premium
draven760 said:
Hello, I have a launch Evo Shift (almost a year old now), and am running Cyanogenmod Nightly 255 with a2ext and a ton of apps installed (above 200 apps running from a class 10 32gb card, dalvik cache on the card), and ScaryKernel with the smartass governor (max 1497 MHz). However, I sporadically get random reboots, gps not working (requiring a reset), camera reboots, and the rare "turn off" bug where it turns off while sleeping. In addition most recently I have a bug where every time that I reboot into clockworkmod recovery to back up , it resets almost all of my phone preferences.
I absolutely love cyanogenmod and appreciate the hell out of it and the work that has been done, but I'm wondering if these bugs are either due to running cyanogenmod nightlies or if I have a defective phone. I also have tried Sense-based roms such as Mikshifted, but the Sense memory overhead is just too large for me. I have no worries if the phone is defective, since I have sprint insurance and can wipe back to stock to exchange it. However, going through all the exchange, re-root and restore procedure would be a pain if its not necessary. Does anyone have any thoughts or advice?
Thanks in advance.
Click to expand...
Click to collapse
I would say try using shift deck, U.K.E, or any cm based aosp roms and see if the problem persist. If it does then its your phone, if not then its a bug in the nightly which is the reason its a nightly because bugs could be there
From what you've stated above I don't think it's a phone, or Rom issue. Seems like you have way too many apps. You have to keep in mind a lot of those apps run in the background. Which uses up Memory, which slows the phone. It will also in xtreme cases cause Random Reboots, Lag, even Random app shut down. I'd remove at the very least half of those and see how it performs. Even 100 apps is still a bit much.
Great, thank you for the advice. Even though I have been monitoring my free memory and running programs, I'm kind of a pack rat so I think it's just time to streamline my programs.
Yes definately loose a lot of thoose apps. Might even want to try a fresh reflash, no apps. Then just add what you know you'll definately need. Willing to bet it's not even half.
TEAM MiK
Mik Roms Since 3/13/11
Which governor are you using with Scary kernel? You should be using Scary gov not any of the others.
Min mhz 300+
Check this first.
If that wasn't your problem run fix permissions from ROM manager and reboot.
If that wasn't your problem boot into clockwork recovery, format /system, wipe dalvik cache, wipe cache, reflash cm255, flash crashv2010's gapps, reflash scary kernel, reboot, wait 10 minutes, problems solved.
---------- Post added at 02:10 PM ---------- Previous post was at 02:08 PM ----------
draven760 said:
and ScaryKernel with the smartass governor
Click to expand...
Click to collapse
This is your problem! ONLY USE Scary, Toasty or Batterysave!
Scary = smartass
Toasty = performance
Batterysave! = conservative
ALL OTHER GOVS WILL NOT BE STABLE!!!
Smartass has always been stable for me
Sent from my PG06100 using Xparent Pink Tapatalk
YoungCorruptionV2.0 said:
Smartass has always been stable for me
Sent from my PG06100 using Xparent Pink Tapatalk
Click to expand...
Click to collapse
Depends how large the gap between your min/max cpu is.
What's your min max?
Try widening it with smartass and see how stable it is.
Well I guess I'm the exception . Dodge Kernel v1.6 Ext.4 , smartass setting , 1.92gHz Max , 245gHz Min. Can run that all day, but usually don't. I use the default settings 1.2gHz Max , 245gHz min. The battery life is better at the default settings.
VICODAN said:
Depends how large the gap between your min/max cpu is.
What's your min max?
Try widening it with smartass and see how stable it is.
Click to expand...
Click to collapse
I usually have the min at the lowest and the max at around 1.2 - 1.6 ghz
prboy1969 said:
Well I guess I'm the exception . Dodge Kernel v1.6 Ext.4 , smartass setting , 1.92gHz Max , 245gHz Min. Can run that all day, but usually don't. I use the default settings 1.2gHz Max , 245gHz min. The battery life is better at the default settings.
Click to expand...
Click to collapse
Some shifts can run 1.9ghz some cant. I have 2 shifts here, both hardware rev 004, one can't go past 1.6ghz.
---------- Post added at 01:38 AM ---------- Previous post was at 01:36 AM ----------
YoungCorruptionV2.0 said:
I usually have the min at the lowest and the max at around 1.2 - 1.6 ghz
Click to expand...
Click to collapse
smartass on pershoot is ok
smartass on scarykernel is not ok.
Yes definately know what you mean. Out of six mine is the only one that will do 1.9gHz . All hardware 004. Out of the others two will do 18gHz, but only one is stable. The rest max out at 1.5gHz, after that they're not stable.
TEAM MiK
Mik Roms Since 3/13/11
VICODAN said:
Some shifts can run 1.9ghz some cant. I have 2 shifts here, both hardware rev 004, one can't go past 1.6ghz.
---------- Post added at 01:38 AM ---------- Previous post was at 01:36 AM ----------
smartass on pershoot is ok
smartass on scarykernel is not ok.
Click to expand...
Click to collapse
Probably true, i'm on tiamat v1.1.4 with smartassV2 so that could make a difference but i always use smartass cause i love the battery life i get with it
prboy1969 said:
Yes definately know what you mean. Out of six mine is the only one that will do 1.9gHz . All hardware 004. Out of the others two will do 18gHz, but only one is stable. The rest max out at 1.5gHz, after that they're not stable.
TEAM MiK
Mik Roms Since 3/13/11
Click to expand...
Click to collapse
YoungCorruptionV2.0 said:
Probably true, i'm on tiamat v1.1.4 with smartassV2 so that could make a difference but i always use smartass cause i love the battery life i get with it
Click to expand...
Click to collapse
Thank you for confirming my opinion as fact. I will reference this thread again later if I need to.
i would get new rom manager that fixed some of my problems also try reloading cm7 and put back on you phone with titanium backup
VICODAN said:
Some shifts can run 1.9ghz some cant. I have 2 shifts here, both hardware rev 004, one can't go past 1.6ghz.
---------- Post added at 01:38 AM ---------- Previous post was at 01:36 AM ----------
smartass on pershoot is ok
smartass on scarykernel is not ok.
Click to expand...
Click to collapse
I have rev 0004 and mine clocks to 2ghz just fine...Some kernels just can't handle 2ghz, and most only clock to 1.8 or 1.9