I have Virtuous 2.0 and it works fine with 1GHz in SetCPU, but if I set it to 1.5GHz and try to do anything it just crashes, then reboots
I just tried it now, have 800MHz set, but the phone was in off mode doing nothing, so turned it on, set it to 1.5GHz max, then opened up a game (Crazy Snowboard) and it loaded, then as I started the game, it counted down from 3 to 2, then froze and rebooted after a few seconds
Then, when it rebooted, I opened SetCPU and it was still set to 1.5GHz, but SetCPU said 1GHz max
Oh, and I never flashed another kernel by the way (don't know how on this phone), so was the kernel installed along with Virtuous (didn't know that was possible)?
LooieENG said:
I have Virtuous 2.0 and it works fine with 1GHz in SetCPU, but if I set it to 1.5GHz and try to do anything it just crashes, then reboots
I just tried it now, have 800MHz set, but the phone was in off mode doing nothing, so turned it on, set it to 1.5GHz max, then opened up a game (Crazy Snowboard) and it loaded, then as I started the game, it counted down from 3 to 2, then froze and rebooted after a few seconds
Then, when it rebooted, I opened SetCPU and it was still set to 1.5GHz, but SetCPU said 1GHz max
Oh, and I never flashed another kernel by the way (don't know how on this phone), so was the kernel installed along with Virtuous (didn't know that was possible)?
Click to expand...
Click to collapse
If you want to overclock to 1.5 ghz, you need a better kernel that allows overclocking to thats speeds. Try unity v4 kernel. It allows oc up to 1.7ghz. The link is in my signature. You can just flash the kernel right over without any problems. Hope this helps
Sent from my HTC Vision using XDA App
cool, thanks
LooieENG said:
I have Virtuous 2.0 and it works fine with 1GHz in SetCPU, but if I set it to 1.5GHz and try to do anything it just crashes, then reboots
I just tried it now, have 800MHz set, but the phone was in off mode doing nothing, so turned it on, set it to 1.5GHz max, then opened up a game (Crazy Snowboard) and it loaded, then as I started the game, it counted down from 3 to 2, then froze and rebooted after a few seconds
Then, when it rebooted, I opened SetCPU and it was still set to 1.5GHz, but SetCPU said 1GHz max
Oh, and I never flashed another kernel by the way (don't know how on this phone), so was the kernel installed along with Virtuous (didn't know that was possible)?
Click to expand...
Click to collapse
different kernels offer different things. You'll find one that you like and works with your ROM. Just as an FYI, not every kernel/ROM combo will be stable at 1.5ghz. That's a big overclock for a processor that is normally at 806mhz. Keep in mind you should use screen off and temperature SetCPU profiles to keep it in check.
Related
Hi
I have permroot and s/off my phone using gfree method and i flashed a kernal
that i downloaded (Cyanogen Kernel v1.3) the kernal allows overclocking upto over 1400 mhz ,at 1094 mhz everything is fine and my phone is stable but as soon as i set the frequency over that using setCPU my phone freezes ,i dont know what i am doing wrong this is the first time i tried overclocking a phone ,i hope i am wrong but i am thinking since every cpu is unique maybe thats the max mine can handle ??? i apprentice any tips, advise , help ,suggestions
Thanks.
i have also tried EZDZ_Godspeed_update03 but using this kernal my phone doesnt even boot up it crashes immediately when i turn my phone on.
bahmanxda said:
Hi
I have permroot and s/off my phone using gfree method and i flashed a kernal
that i downloaded (Cyanogen Kernel v1.3) the kernal allows overclocking upto over 1400 mhz ,at 1094 mhz everything is fine and my phone is stable but as soon as i set the frequency over that using setCPU my phone freezes ,i dont know what i am doing wrong this is the first time i tried overclocking a phone ,i hope i am wrong but i am thinking since every cpu is unique maybe thats the max mine can handle ??? i apprentice any tips, advise , help ,suggestions
Thanks.
i have also tried EZDZ_Godspeed_update03 but using this kernal my phone doesnt even boot up it crashes immediately when i turn my phone on.
Click to expand...
Click to collapse
You might be right. Not every CPU is created equal and since the phone is only supposed to run 800Mhz you can't exactly complain that it "only" does ~1.1ghz
On the other hand a little more juice can make a reluctant CPU run a little faster. I'm not sure how the voltage tables work out for different Kernels but you might want to look in to that. The higher the voltage, the better the chance your OC will work, typically.
That's true, every cpu is unique. But for now, since the kernels are still going through development, I would assume it's perfectly fine that overclocked speeds are still quite unstable
Thanks for the replys i am not really complaining i just wanna make sure that i havnt messed up somewhere i thought the crashing might be happening because i messed something up or maybe it happend to others and its a common problem or there is a fix for it .
Also i would appreciate it if someone could put me in the right direction in regard to changing the voltage.
Sent from my HTC Vision using XDA App
just wipe my original stock sense rom and flashed it with virtuous-vision_froyo_rom-v0.8.0 and applied all the patches but still the same problem
my phone freezes instantly as soon as i change it to just over 1100 mhz
its so strange its very very stable at 1094 mhz hasnt crashed even once.
any ideas?
The current overclock kernel that Flippy has over in Development (1.4) causes my phone to freeze when I'm trying to play Angry Birds. CyanogenMod's kernel runs it at 1.4Ghz, and I'm using an older, more stable version of Flippy's kernel.
bahmanxda said:
just wipe my original stock sense rom and flashed it with virtuous-vision_froyo_rom-v0.8.0 and applied all the patches but still the same problem
my phone freezes instantly as soon as i change it to just over 1100 mhz
its so strange its very very stable at 1094 mhz hasnt crashed even once.
any ideas?
Click to expand...
Click to collapse
It could be simply that your CPU isn't capable of over-clocking that high. Its hard to say as the kernels are still being developed but the ability to overclock a processor can vary greatly from unit to unit...
I have CM 6.1 and the last few days I have been running my phone at 1017 to compare the performance difference against the 1497 and thus far, I haven't really seen a drastic difference... That may change as the Gingerbread based ROMS start to trickle out but for now 1ghz seems like plenty of power.
You could always try a different kernel and see if it yields different results.
bahmanxda said:
Hi
I have permroot and s/off my phone using gfree method and i flashed a kernal
that i downloaded (Cyanogen Kernel v1.3) the kernal allows overclocking upto over 1400 mhz ,at 1094 mhz everything is fine and my phone is stable but as soon as i set the frequency over that using setCPU my phone freezes ,i dont know what i am doing wrong this is the first time i tried overclocking a phone ,i hope i am wrong but i am thinking since every cpu is unique maybe thats the max mine can handle ??? i apprentice any tips, advise , help ,suggestions
Thanks.
i have also tried EZDZ_Godspeed_update03 but using this kernal my phone doesnt even boot up it crashes immediately when i turn my phone on.
Click to expand...
Click to collapse
you should check/edit the overclock scripts..
I found wrong configuration script (650 Mhz using Androidiani OR)
I have a rooted myTouch 3g slide and am using the CyanogenMod 6.1.1 ROM. I have been trying to overclock the CPU using setCPU but for some reason every time I change the max speed past 600 mhz the phone just reboots. Am I doing something wrong or do I just have a phone that can't be overclocked beyond that speed?
Thanks for any insight into this problem!
I don't know how far past 600 MHz you're trying to go, but I have been successful at overclocking to 806 MHz. Anything over that, and I start getting lockups, reboots, etc.
Hope that helps a bit!
Lol i'm jealous now.. At this point I'd like to even just be able to overclock it to 768 or 787 mhz. Anything over 600 mhz really would be a step in the right direction.
It seems as though as soon as i change the max cpu speed in setCPU the phone hangs up for a second and then immediately reboots. I have to quickly change it when i get back into setCPU after the reboot otherwise it reboots again.
Do I not have the necessary tools or applications on the phone to do this? I thought CM 6.1.1 had the overclock kernel and everything...
arjuna_ said:
Lol i'm jealous now.. At this point I'd like to even just be able to overclock it to 768 or 787 mhz. Anything over 600 mhz really would be a step in the right direction.
It seems as though as soon as i change the max cpu speed in setCPU the phone hangs up for a second and then immediately reboots. I have to quickly change it when i get back into setCPU after the reboot otherwise it reboots again.
Do I not have the necessary tools or applications on the phone to do this? I thought CM 6.1.1 had the overclock kernel and everything...
Click to expand...
Click to collapse
it does, but the problem is that your phone's cpu is not able to handle it. Some people can do 900+(unfortunately im not that lucky) some cant touch 800 even. Even though we all have the same phone they all arent exactly the same. Like on a computer some can OC higher than others even if setup is the same...
So what your saying is that my phone just can't be overclocked beyond 600 mhz? Is there a way to manually adjust it to like 650 mhz or something else that I set? Or is that dangerous and stupid to do?
Sorry i'm a total noob at this...
arjuna_ said:
So what your saying is that my phone just can't be overclocked beyond 600 mhz? Is there a way to manually adjust it to like 650 mhz or something else that I set? Or is that dangerous and stupid to do?
Sorry i'm a total noob at this...
Click to expand...
Click to collapse
That can't be done because the cpu won't actually clock to anything in between certain multiples, I forget what the multiple is but it can't do in between unfortunately. I have stably clocked to 844 mhz. Every once and awhile, normally less than once a month it will freeze but not enough for me to go down to 825 or 806.
But to me, this doesn't sound like the processor not being able to handle it. It sounds like something software related, since at least in my experience, if the CPU can't handle it, the phone simply freezes and you have to pull the battery. It doesn't reboot, it just freezes, stops processing entirely.
If you don't have the android sdk, download it and install it (just google it), and then open a command prompt when your phone is plugged in and type adb logcat and press enter.
You also need the HTC sync drivers which can be obtained from HTC's site.
Then, while running the logcat, change your frequency up one step, and after your phone is back at the boot splash screen, press CTRL + C in the command prompt window and paste the entire logcat into a reply here in this thread
Code:
with code brackets like this
. You might even do a paste2: http://paste2.org/new-paste to make it easier to read
It sure sounds like it's a system crash, not a processor locking up from too high of speeds.
Maybe its the version of SetCPU that your using. Try re-installing it first, and if that doesn't help, Google up SetCPU 2.02 or something and see if that works.
I think the latest version of setcpu is 2.10
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
What rom are you using?
Maybe the kernel is not Over Clocked.
I've made it to overclock up to 844 pretty well on 3rdSense Rom...
Tzatlacael said:
What rom are you using?
Maybe the kernel is not Over Clocked.
I've made it to overclock up to 844 pretty well on 3rdSense Rom...
Click to expand...
Click to collapse
arjuna_ said:
I have a rooted myTouch 3g slide and am using the CyanogenMod 6.1.1 ROM. I have been trying to overclock the CPU using setCPU but for some reason every time I change the max speed past 600 mhz the phone just reboots. Am I doing something wrong or do I just have a phone that can't be overclocked beyond that speed?
Thanks for any insight into this problem!
Click to expand...
Click to collapse
CM 6.1.1 Should have the kernel included.
When i first started over clocking I recall being told not to use the perflock disabler on SetCpu or it would mess things up. Perhaps you are using it and should not be or vice versa? That was using DumFuq's (sp) kernels of course, I do not know if Cyanogen still uses the same overclock kernel.
Balem said:
When i first started over clocking I recall being told not to use the perflock disabler on SetCpu or it would mess things up. Perhaps you are using it and should not be or vice versa? That was using DumFuq's (sp) kernels of course, I do not know if Cyanogen still uses the same overclock kernel.
Click to expand...
Click to collapse
You only needed to use perflock on stock kernel that was used on stock rom. Dumfuq's kernel lets you yse setcpu w/o that setting being needed. but once i got soff it would save settings even after rebooting.
Just wondering if anyone else is having the same problem with CM7 and LauncherPro.
After rebooting, LauncherPro will hang for about 5-10 minutes before Android will force close it, or if I long-press the back key to manually force close it. It's only slightly annoying, since it functions properly afterwards, it would just be nice if there is a workaround or fix available so that I wouldn't have to do that after my daily reboot.
Sometimes it just happens, you may want to check you minimum frequency of your governor.
Min: 245
Max: 998
Governor: Conservative
You can try smartass...and what kernel are you using?
Yeah I am having the same problem. LP always forcecloses when I restart on RC4. Its not to annoying though.
Sent from my PC36100 using XDA App
Been happening to me since at least RC2, using stock kernel, minimum frequency of 384.
I'm pinging the devs to see if they know anything about it...
teh roxxorz said:
You can try smartass...and what kernel are you using?
Click to expand...
Click to collapse
Latest SavagedZen.
Conservative gives me the best battery life without sacrificing performance. From what I've read about smartass, I wouldn't like it.
Try setting memory usage to "high" in LP settings.
Menu>Preferences>Advanced Settings>Memory Usage Settings>Memory Usage preset>Select High.
Word from on high: We need some logcats. When I get home from work, I'm going to be flashing N35, no GApps, install LP, reboot, and then grab the log.
Hopefully that'll light some fires under people's arses. ;D
I have this issue as well.
Just chiming in that I too have this issue, also from about RC2.
Have used stock and Tiamat kernels, both exhibit the same behavior descibed in the OP.
I flashed Tiamat but the problem still exists, so I'm going to say it's either LP or CM7. Testing out the memory boost for LP now.
I have had this same problem with both my old Hero and now the Evo. LP Pro always hangs 1-2 min at bootup. Alternating between conservative, ondemand, smartass does nothing. I used CM6 on Hero, CM7 & Destroyer on the Evo.
Does not hang when I use SprintLovers.
jedijackie said:
I have had this same problem with both my old Hero and now the Evo. LP Pro always hangs 1-2 min at bootup. Alternating between conservative, ondemand, smartass does nothing. I used CM6 on Hero, CM7 & Destroyer on the Evo.
Does not hang when I use SprintLovers.
Click to expand...
Click to collapse
Yeah didn't hang when I had Sprint Lovers or Myn's Warm. Def points toward CM7 for me.
Sunsparc said:
Yeah didn't hang when I had Sprint Lovers or Myn's Warm. Def points toward CM7 for me.
Click to expand...
Click to collapse
Done think its cm7 either. I've had the issue on a few nightlies but set min CPU to 384 and fix permissions in rom manager and its gone away. Wifeys never complained about it on hers and she complains about everything
nate.spangler said:
Done think its cm7 either. I've had the issue on a few nightlies but set min CPU to 384 and fix permissions in rom manager and its gone away. Wifeys never complained about it on hers and she complains about everything
Click to expand...
Click to collapse
I'll try that out. The thing is, shouldn't the phone be running at full blast on boot? What would the min freq have to do with that?
Sunsparc said:
I'll try that out. The thing is, shouldn't the phone be running at full blast on boot? What would the min freq have to do with that?
Click to expand...
Click to collapse
If you have the "set on boot" option checked, then its running at whatever is set.
I unchecked "set on boot" and moved the min freq up to 384, no dice still hangs.
Well you'd have to re-check it after its reset. Are you using a custom kernel?
teh roxxorz said:
Well you'd have to re-check it after its reset. Are you using a custom kernel?
Click to expand...
Click to collapse
Ive used both SavagedZen and Tiamat. Using Tiamat at the moment.
i just flashed invisibleks .37 kernal with OMFGB (ran into some problems with CM7) and i was wondering the proper way to set up setcpu profiles with smartass (if needed at all)
Sorry. This should be in Q&A.....
Sent from my OMFGB powered hTc Incredible.
watt9493 said:
i just flashed invisibleks .37 kernal with OMFGB (ran into some problems with CM7) and i was wondering the proper way to set up setcpu profiles with smartass (if needed at all)
Click to expand...
Click to collapse
I ran OMFGB 1.1.1 for a long time before they screwed up 1.2(soooooo many errors), and really felt the need to have a lockscreen music controler(1.1.1 doesn't). I always ran 128/768, on 1.1.1 it should run perfect(I run chad's kernel though), just unlock slowly. If you want a faster unlock set it 245/768. Either one of those will get you really good battery life(128 being better obviously). If you are running 1.2, I highly recommend you set it atleast at 921(i think) or above as that just doesn't run as smooth. Also note the way smartass works, unless you want to kill battery life everytime you turn the screen on, try to set the max the lowest possible as it will sit as a frequency the phone feels it should run at without losing any speed(most of the time it's 1036 if you've overclocked). So unless you are just texting or calling, it's not bad, but any multitasking or big app using when the screen on, it'll jump way up.
I believe Chad is working on an ingenious kernel that tries to scale intelligently to what it is doing at all times so it'll save battery life not only when the screen is off, but also while the screen is on.
Can i set profiles or no? Like screen off, battery ones, and one temp one?
Sent from my OMFGB powered hTc Incredible.
watt9493 said:
Can i set profiles or no? Like screen off, battery ones, and one temp one?
Sent from my OMFGB powered hTc Incredible.
Click to expand...
Click to collapse
Oh, well, there is no point for a screen off one if you are using smartass on all your profiles. When it's not doing anything, it automatically scales down to the lowest setting possible(128 for best battery but slow unlock speeds or double clicks sometimes, 245 fixes those problems but using a fraction more battery).
I have a Normal profile(128/768), a Temp profile(245/614), just make sure if you are using GPS you manually scale it up some, my phone always ran like crap when Navigating anything less then 883, but everything, and I mean everything usually was fine at 768 on 1.1.1. If you are running 1.2 probably want to do 883 then 998 for GPS.
My CPU Speed automatically goes down to 810Mhz on all overclocked kernels.
Even in CM10 kernels,
It happens in between while I play a game or so.
Even if I install Kernel with only GPU overclock, it still happens.
But never happens on stock kernels. I have to manually increase the CPU speed by setCPU.
Any Solutions for it Guys?
Moved to Q&A
Try to use Kernel tuner, and normally the device uses 810 mhz too cool down...
patato800 said:
Try to use Kernel tuner, and normally the device uses 810 mhz too cool down...
Click to expand...
Click to collapse
Used kernel tuner but still the same result, it goes to 810mhz even if the phone is not hot (just homescreen) and when i increase it, it remains at max even if i play games and make it hot. but after some time (say 15 or 20 minutes) even if I am in standby mode the cpu goes down to 810Mhz. previously at some point it was 1134Mhz.
Guys, anyone with some help. It has even started to occur in Complete stock ROM. (flashed the ftf on locked bootloader, still the max cpu spped drops from 1.5 Ghz to 810 Mhz, some times both cores)
halleyrokz said:
Guys, anyone with some help. It has even started to occur in Complete stock ROM. (flashed the ftf on locked bootloader, still the max cpu spped drops from 1.5 Ghz to 810 Mhz, some times both cores)
Click to expand...
Click to collapse
I had the same problem but i discoverd that the Battery saver pro causes that problem for me. If you use the seme app untick control CPU frequency.
It is actually a built in security feature of our phones which gets activated when temperature of phone goes high . At least that's what I know .
Sent from my Xperia S using xda premium
Here's solution!!!
http://forum.xda-developers.com/showthread.php?p=32245228
Send from my stupid lt26i