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
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.
Hi I am posting here because I can t post in the Development area yet.
So here is whats happening, I went and got the Latest CWM installed and rebooted. Then I flashed the newest Tiamat Xoom Rom 1.1 and signed in with my google account, let it download all my apps, then I restored all other missing apps + system data from Titanium and everything went a sweet as Pie. My missing apps was now there, my home screens were back to my previous layout and I was all happy as a kid can be... That is until i noticed my Xoom doing a random Reboot out of the corner of my eye. So I went into Setcpu and checked what I had OC'ed my xoom to and it was set to 1.4...Which i know is fine for my xoom. (Max I can go with mine is 1.5) So I went and clocked it to 1.2 and to my surprise about an hr later it did it again.... Mind you this is with my xoom sitting there not doing anything with no one touching it. So I decided to Flash back the 1.4.4 Tiamat Kernnel and OC'ed to 1.4 and all seems to be fine with no random reboots.
So, I would like to know if anyone else is/was having random reboots with the Tiamat Xoom Rom 1.1 w/the 1.4.5 Tiamat Kernnel?? If so what was their solution?
I did notice that with the 1.4.5 Kernnel the xoom did feel smoother. Also just some thing i noticed, in Setcpu with the 1.4.5 Kernnel there are optons to undervolt, however when I flashed back down to the 1.4.4 Kernnel that option is no longer an option in Setcpu.
Any thoughts??
No problems Here
I followed the same path you did. I installed Tiamat 1.1 yesterday, have SetCPU at 1200 interactive. Been running all day . . . very smooth, no reboots. In the past the only time I had random reboot was if I set the CPU at or above 1500. An update to setCPU came out a day or so ago. Maybe that might help.
I too am on v1.1 on 1.4.5 kernal typing this running at 1504 mghz smoothly. I been using my Xoom quite extensively since v1.1 at this clockspeed with no random reboots. My browser will occationally crash but I'm unsure if that's even related. When I first flashed the 1.1 rom on, I was running all out at 1.7 ghz but it started to generate screen artifacts and did reboot twice. Been running just fine at 1.5 tho.
Sent from my Tiamat Powered Xoom
Still No luck..
Ok, so I wiped/factory reset then re-flashed the Tiamat Xoom Rom 1.1 and I thought everything was all good as it went the day without a random reboot. Then Last night as i was laying in bed falling asleep and the xoom hooked up to the charger I notice a bright blue light.... it was the Xoom doing a random reboot.....grrrrrrr. Could it be a Setcpu issue?? Should I not set anything on boot?? As of right now, I Force Closed Setcpu and did a Cache Clear and then reopened Setcpu and had it "Auto Detect the speeds" and just Oc'ed to 1.4 and left "Set on boot" unchecked. I hope this will work, cause it seems alot smoother with the 1.4.5 Kernnel rather then the 1.4.4 Kernnel.
Just a Thought...(as I dont understand UV Kernnels), but could it have something to do with the Voltage of the 1.4.5 kernnel? Is setcpu with the 1.4.5 Kernnel you can change the Voltage of the frequencies...Should I even bother with this?
Thoughts??
I am seeing the exact same behavior.. Continual reboots all night, even if the screen is off and I am not doing anything.
It has happened 2x in the last hour while I'm sitting here at work.. Very strange. I'm uninstalling every app I installed, 1 at a time, in order to try to figure out if it is one of them. So far, WeatherBug and SetCPU are removed, I'll let you know if it helps.
vincentdeeney said:
I am seeing the exact same behavior.. Continual reboots all night, even if the screen is off and I am not doing anything.
It has happened 2x in the last hour while I'm sitting here at work.. Very strange. I'm uninstalling every app I installed, 1 at a time, in order to try to figure out if it is one of them. So far, WeatherBug and SetCPU are removed, I'll let you know if it helps.
Click to expand...
Click to collapse
Run a logcat and see what is causing the reboots...its common that some devices can't handle the overclocking....you can try flashing the stock GPU kernel and see if they go away. My device can't handle being overclocked...this is very common with any motorola device I have ever owned besides the droid 1.
dhemke17 said:
Run a logcat and see what is causing the reboots...its common that some devices can't handle the overclocking....you can try flashing the stock GPU kernel and see if they go away. My device can't handle being overclocked...this is very common with any motorola device I have ever owned besides the droid 1.
Click to expand...
Click to collapse
That is the killer.. I'm not even overclocking. Stock was absolutely fine.. even OC'ing in the past was fine, its just this 1.1 Rom that has caused this behavior.
Upside is, since removing those 2 apps, no reboots. If your not choosing to change the CPU/Volts, does SetCPU still change things in the background?
I've had the same problem. I have uninstalled Setcpu so I'll let you know if this stops the reboots.
Glad to see I'm not alone here. although I even had the problem on 1.0 rom. I'm still trying to fix it :-\
I have also been having issues with reboots. I flashed the 1.1 rom as directed and did everything exactly as I should. I think its an issue with the rom or the new kernel. I'm overclocked to 1.504ghz and always have been and have never had reboot issues until flashing the new rom. My xoom is stable up to 1.6ghz but I keep it on the 1.504ghz. But even at stock speeds and profiles to keep it running a max:216 min:216 my battery life has decreased alot it seems.
"My browser will occationally crash but I'm unsure if that's even related." I don't think it is related. I have two identical zooms ones been rooted since root was available, the other stayed stock and updated with the ota. Both are experiencing browser crashes when in the stock browser, so I'm not exactly sure what's goin on there.
Sent from my Xoom using XDA Premium App
Hwy guys I had the same problem to, here is a log I started,
One of the guys on the org thread stated that it may be a overclocked gpu problem causing reboots, which the 1.1 tiamat is oc gpu, he suggested that I try lunch pad kernel, which so far has worked without a reboot yet. You can install it on to of tiamat 1.1. Which is good cause I keep most all the benefits, but with no gpu overclocking, which is lead to be the cause of reboots.
Reboot times and events
My tablet: WIFI xoom, abd root (not one click), tiamat rom 1.1 with mod pack one.
Time and date: 7/8/11 6:45 pm cst
Currect status: standby, screen off
Cpu setting: stock 1.0 ghz max , 816 mhz min. Scaling set to interactive
Cpu app: setcpu
Time and date: 7/8/11 8:41 pm cst
Current status: just competed download of mp4, file size 205.9 meg
Cpu setting: overclocked at 1.2ghz max, 1.0 min. Scaling set to on demand
Cpu app: antutu cpu master
*updated
Time and date: 7/8/11 10:51pm cst
Current status: standby, screen off
Cpu setting: stock
Cpu app: all cpu overclocking apps uninstalled
** updated
Time and date: 7/9/11 12:11am cst
Current status: standby, screen off
Cpu setting: stock
Cpu app: all cpu overclocking apps uninstalled
IM SEEING A DEF PATTERN
People please see if reboots are spaced out evenly in time
runandhide05 said:
Hwy guys I had the same problem to, here is a log I started,
One of the guys on the org thread stated that it may be a overclocked gpu problem causing reboots, which the 1.1 tiamat is oc gpu, he suggested that I try lunch pad kernel, which so far has worked without a reboot yet. You can install it on to of tiamat 1.1. Which is good cause I keep most all the benefits, but with no gpu overclocking, which is lead to be the cause of reboots.
Reboot times and events
My tablet: WIFI xoom, abd root (not one click), tiamat rom 1.1 with mod pack one.
Time and date: 7/8/11 6:45 pm cst
Currect status: standby, screen off
Cpu setting: stock 1.0 ghz max , 816 mhz min. Scaling set to interactive
Cpu app: setcpu
Time and date: 7/8/11 8:41 pm cst
Current status: just competed download of mp4, file size 205.9 meg
Cpu setting: overclocked at 1.2ghz max, 1.0 min. Scaling set to on demand
Cpu app: antutu cpu master
*updated
Time and date: 7/8/11 10:51pm cst
Current status: standby, screen off
Cpu setting: stock
Cpu app: all cpu overclocking apps uninstalled
** updated
Time and date: 7/9/11 12:11am cst
Current status: standby, screen off
Cpu setting: stock
Cpu app: all cpu overclocking apps uninstalled
IM SEEING A DEF PATTERN
People please see if reboots are spaced out evenly in time
Click to expand...
Click to collapse
Is the gpu overclocked more in this kernel than tiamat 1.4.4? Cause i never had reboots with that kernel and it had an overclocked cpu.
Sent from my Xoom using XDA Premium App
phouse1025 said:
Is the gpu overclocked more in this kernel than tiamat 1.4.4? Cause i never had reboots with that kernel and it had an overclocked cpu.
Sent from my Xoom using XDA Premium
The gpu is overclock in this kernel, unlike the 1.4 which the gpu is not overclocked, just the cpu.
I installed lunchpad on to of the 1.1 last night and I didn't loose any of the features from 1.1 other than the overclocked gpu. Still have sd card and usb hosting and overclocked CPU. I would definitely do it if I were any of you guys having the reboot issues. One guy on the orig thread had to send his xoom back and moto repaired it and said that the gpu was fried. So again until there is a way to set the gpu back to stock on 1.1 user beware
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
runandhide05 said:
phouse1025 said:
Is the gpu overclocked more in this kernel than tiamat 1.4.4? Cause i never had reboots with that kernel and it had an overclocked cpu.
Sent from my Xoom using XDA Premium
The gpu is overclock in this kernel, unlike the 1.4 which the gpu is not overclocked, just the cpu.
I installed lunchpad on to of the 1.1 last night and I didn't loose any of the features from 1.1 other than the overclocked gpu. Still have sd card and usb hosting and overclocked CPU. I would definitely do it if I were any of you guys having the reboot issues. One guy on the orig thread had to send his xoom back and moto repaired it and said that the gpu was fried. So again until there is a way to set the gpu back to stock on 1.1 user beware
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
I could be wrong but if you check the post for 1.4.4 it says they have 2 versions, one with oc gpu and one without.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
phouse1025 said:
runandhide05 said:
I could be wrong but if you check the post for 1.4.4 it says they have 2 versions, one with oc gpu and one without.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
I just noticed that, but when I was running it I did not have the gpu oc'ed one, sorry fur the mis info
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
runandhide05 said:
phouse1025 said:
I just noticed that, but when I was running it I did not have the gpu oc'ed one, sorry fur the mis info
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
It's not a problem. I had the gpu overclocked version and never had reboots, that's what Leeds me to believe that the reboots are caused by something else in the new kernel or something in the new rom. Same with the decreased battery life issue that I hear has also affected alot of devices here recently.
Edit: I flashed the new launchpad kernel. No reboots since. Hopefully team tiamat can figure out the problem cause switching from the tiamat kernel was the last thing I wanted to do, but I had to have stability untilled things get worked out.
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
I had a lot of random reboots with 1.1. I resolved them by doing the following
Updating the CMW recovery img to the most recent one posted in the dev forum.
Wipe
Install ROM
Boot
The issue for me was that my recovery img was quite old so updating it and then applying the ROM resolved all of my issues. I had a few issues with the 1.4.5 kernel so I am running LaunchPad 1.2.3 now and that seems to be a bit more stable. 1.4.4 I was running at 1.4Ghz 1.4.5 I could only run at 1.2Ghz. LaunchPad 1.2.3 I am back to 1.4Ghz stable
Just an update, Since my last post on the 5th of july, I have flashed 1.4.4 OC'ed GPU Kernel and have been running Tiamat Rom 1.1 with no random reboots or any other issues. So I do believe there is something with the Stock 1.4.5 Kernel that could be making some of the xoom reboot randomly. Oh and I can OC up to 1.5 again (my xoom's max), but I leave it at 1.4 with Setcpu. Over all i'm happy once again.
Psyclic_1 said:
I had a lot of random reboots with 1.1. I resolved them by doing the following
Updating the CMW recovery img to the most recent one posted in the dev forum.
Wipe
Install ROM
Boot
The issue for me was that my recovery img was quite old so updating it and then applying the ROM resolved all of my issues. I had a few issues with the 1.4.5 kernel so I am running LaunchPad 1.2.3 now and that seems to be a bit more stable. 1.4.4 I was running at 1.4Ghz 1.4.5 I could only run at 1.2Ghz. LaunchPad 1.2.3 I am back to 1.4Ghz stable
Click to expand...
Click to collapse
Can post a link to the most recent CMW recovery ima, just so i can confirm that I have the latest??
Thanks
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
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.
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