I overclocked my phone to 1.4GHz but it freezes soon after. 1GHz works fine. I followed the youtube vid from blackprince. Any help would be nice thanks
Sent from my T-Mobile G2 using XDA App
Bdix said:
I overclocked my phone to 1.4GHz but it freezes soon after. 1GHz works fine. I followed the youtube vid from blackprince. Any help would be nice thanks
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
More info, are you rooted? Im assuming yes from the blackprince video reference. What rom are you on, what kernel, setcpu, any profiles etc...????
Bdix said:
I overclocked my phone to 1.4GHz but it freezes soon after. 1GHz works fine. I followed the youtube vid from blackprince. Any help would be nice thanks
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
That's just your phones' way of saying "Stop making me work harder than I need to!!!!"
Bdix said:
I overclocked my phone to 1.4GHz but it freezes soon after. 1GHz works fine. I followed the youtube vid from blackprince. Any help would be nice thanks
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
R u using gscript overclock??
Sent from my HTC Vision using XDA App
Kernal is
2.6.32.17-g9ab3677
Yes I im useing gscript. I have the
OC. File and Oshitttt
Oc. Works fine, but have to overclock it every time I reboot. Every thing is stock on my phone beside the peraroot (S-off) and the kernal.
Sent from my T-Mobile G2 using XDA App
I do have setcpu, astro, and all apps needed to root and over clock. I am still on stock rom.
Sent from my T-Mobile G2 using XDA App
Then I guess you're just unlucky :/
You'll have to just settle for 1GHz I guess.
Sent from my T-Mobile G2 running Cyanogenmod.
Wow! That sux...........
Sent from my T-Mobile G2 using XDA App
Bdix said:
Kernal is
2.6.32.17-g9ab3677
Yes I im useing gscript. I have the
OC. File and Oshitttt
Oc. Works fine, but have to overclock it every time I reboot. Every thing is stock on my phone beside the peraroot (S-off) and the kernal.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
I dont think I quite understand your situation, are you rooted or not, according to this post you say you are stock besides "peraroot (I think you meant permroot)and the kernel" , so meaning you are rooted (s-off)??. Anyways if you are rooted why are you using gscript to OC with? And if your on a custom kernel why not use setcpu or something similar.
If your not rooted (s-on) then I think I remember when using the gsript files that 1.4 and over was unstable, if you want something a little higher than 1ghz use something like word pad to change the value in the script you are pushing for the oc to go to 1.1ghz or 1.2ghz etc..
Bdix said:
I overclocked my phone to 1.4GHz but it freezes soon after. 1GHz works fine. I followed the youtube vid from blackprince. Any help would be nice thanks
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
From my experience, not all processors are created equal... Some just handle the higher frequencies better than others do.
I have loaded everything why not working download kernel should put first in phone should I do in computer
Sent from my T-Mobile G2 using XDA App
Yes I'm permarooted. S-off. I'm useing gscript because that's what was done in the video. I have setcpu and use it but with out a overclock program I can only raise it to 806MGz and with oc. I can raise it to 1017MGz. If that's as high as I can go then I guess I just have to deal with that.
Sent from my T-Mobile G2 using XDA App
Bdix said:
Yes I'm permarooted. S-off. I'm useing gscript because that's what was done in the video. I have setcpu and use it but with out a overclock program I can only raise it to 806MGz and with oc. I can raise it to 1017MGz. If that's as high as I can go then I guess I just have to deal with that.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
As someone said earlier, I think you are using the old, unstable method. I highly recommend u updating to a ROM with OC embedded into the kernel.
It is also true that "not all processors are created equally" but this is the only case I have read with it freezing at 1.4.
Bdix said:
Kernal is
2.6.32.17-g9ab3677
Yes I im useing gscript. I have the
OC. File and Oshitttt
Oc. Works fine, but have to overclock it every time I reboot. Every thing is stock on my phone beside the peraroot (S-off) and the kernal.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
U need to find a rom that suits u and use pershoots kernel download any cpu tuner for overclock do not use gscript it really freezes ur phone
Sent from my HTC Vision using XDA App
I have the same problem ,i am running virtouos ROM with evil 12/10 and if i over-clock anything over 1094mhz my phone freezes the the only way that i can manage more than that is if i set it to performance scaling with no profile and there is no point on doing that because it eats the battery .its only good for benchmarking ,i think your problem is same is me, you have been unlucky with your CPU .i am just hoping its going to be different when gingerbread come out.
bahmanxda said:
I have the same problem ,i am running virtouos ROM with evil 12/10 and if i over-clock anything over 1094mhz my phone freezes the the only way that i can manage more than that is if i set it to performance scaling with no profile and there is no point on doing that because it eats the battery .its only good for benchmarking ,i think your problem is same is me, you have been unlucky with your CPU .i am just hoping its going to be different when gingerbread come out.
Click to expand...
Click to collapse
Have you given CM6.1 a go just to compare if you can clock higher using a different ROM?
If you are indeed using the gscript method then this has been explained many times! there's a whole giant humungo thread about that hack when it initially came out.
the reason your phone's freezing is because you're asking it to clock faster, but you arent giving it more juice to offset the additional work it's conducting..hence the freeze. that old hack (while it was awesome at the time) is very outdated and has been surpassed by actual performance kernels.
It's all in the thread. you wouldnt put low octane in a sports car would you? same principle lol
wileykat said:
Have you given CM6.1 a go just to compare if you can clock higher using a different ROM?
Click to expand...
Click to collapse
No i havnt ,i got desire z i thought CM6.1 is for G2 only ,i will look into it and see if its compatible with Desire z though i really like sense ,thanks
bahmanxda said:
No i havnt ,i got desire z i thought CM6.1 is for G2 only ,i will look into it and see if its compatible with Desire z though i really like sense ,thanks
Click to expand...
Click to collapse
I think they have already solved the key mapping for the CM rom, look here:
http://forum.xda-developers.com/showthread.php?t=847824
wileykat said:
Have you given CM6.1 a go just to compare if you can clock higher using a different ROM?
Click to expand...
Click to collapse
I gave CM6.1 a go and i am stable at 1.5ghz cheers for that , i really like sense though, i will play with CM6.1 and see what happens maybe i will continue using it.
Related
so i know the kernel desgnates the amount you can overclock and set cpu does it and all that, but is there only so much a particular rom can take? for example i ran netarchy 4.1.8 on my evio 1.1, and i can overclock up to 1.276, but even if i accidentally put it all the way up there, the phone freezes or resets, is it because the rom cant handle it, or just too much for the phone itself?
Too much for your phone. Some can get up thereband some can't. Mine handles 1228800 just fine. Anything higher it freezes..
Sent from my PC36100 using XDA App
martyzidek said:
Too much for your phone. Some can get up thereband some can't. Mine handles 1228800 just fine. Anything higher it freezes..
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
well thats strangely depressing, thanks for easy to understand reply =)
I also can run at 1.23 ghz stable
hey guys
Yesterday I switched from the HTC Stock rom to the nightly cyanogenmod 7, latest version as of today.
Now my question:
i have the feeling that the phone is a bit slow compared to the htc stock rom (of course I have activated USB Debugging). Now my question is if it is recommended to flash another kernel.
I experience the performance loss for example on the homescreen and in the app drawer, it just doesnt feel that smooth any more... which is strange because the cyanogen mod uses the adwlauncher and I had the same launcher on the stock rom, running very smoothly.
Now is it just my immagination or am I not the only one experiencing that "problem".
I appreciate any comments
greetings from switzerland
I'm on build 12 now and find it very fast and stable. I am using adw launcher without any lag. Did you do a complete wipe before the upgrade?
As for the kernel, these are currently no kernels that work for cm7, how ever the stock kernel is very good and will overclock to 1.5ghz if you want it to.
Sent from my Desire HD using Tapatalk
Blinkydamo said:
I'm on build 12 now and find it very fast and stable. I am using adw launcher without any lag. Did you do a complete wipe before the upgrade?
As for the kernel, these are currently no kernels that work for cm7, how ever the stock kernel is very good and will overclock to 1.5ghz if you want it to.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
yes I did a full wipe of the data and the cache..
It's just strange because everything was running so smooth with the stock rom and adwlauncher or launcher Pro. I even flashed the stable versoin of cm... same thing there...
You are using live wallpapers,right?
Sent from my Desire HD using XDA App
tolis626 said:
You are using live wallpapers,right?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
I already thought of that and I did disable them without any success... still feels chunky...
Are you using setcpu? If so what gov you running?
Sent from my Desire HD using Tapatalk
Blinkydamo said:
Are you using setcpu? If so what gov you running?
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
No I'm not using any of this stuff... I tried to sort out everything that may cause the performance drop but with no results..
What linpack and quadrant scores are you getting after a reboot? You should really run each one 3 times and take an average, this will let you know how slow it is (not a 100% test but it'll help)
Also might be worth having a look at "Power Tutor", it'll be able to tell you which programs are using the cpu the most, might find one that is hogging it for some reason.
Blinkydamo said:
What linpack and quadrant scores are you getting after a reboot? You should really run each one 3 times and take an average, this will let you know how slow it is (not a 100% test but it'll help)
Click to expand...
Click to collapse
How exactely do I get those scores?
//EDIT: Ok results: about 40 - 41 Mflops, Time ~2s, Norm Res 5.68, Precision 2.22etc
Have you tried downloading spare parts off the market and setting screen animations to fast, might be them that make it look like its running slower. Be Dr this I an running out off ideas, your score on Linpack is about right for a stock kernel, yet could try running setCPU and have the CPU running a little faster, I have mine running at 1.2ghz for day to day stuff.
Sent from my Desire HD using Tapatalk
If you are using apache14's kernel and use smartass that is your problem.If it's stock CM kernel I don't know...Try setting the governor to performance in setcpu and re-run the benchmarks.Telling us your kernel and CPU clock would help!
Sent from my Desire HD using XDA App
I have the stock kernel (as far as I know.. at least I didnt flash a new one... I just flashed the cyanogen mod) as far as the CPU goes: I dont use setcpu... how's the battery performance when u run it on 1.2 ghz?
expremo said:
I have the stock kernel (as far as I know.. at least I didnt flash a new one... I just flashed the cyanogen mod) as far as the CPU goes: I dont use setcpu... how's the battery performance when u run it on 1.2 ghz?
Click to expand...
Click to collapse
I can usually get to the end of the day and still have about 30% left, but I an a heavy user and running the WiFi all evening, do a good 3-4 hours of browsing each day as well as other stuff.
This is not a problem for me as I charge every night. You should give it a go, if its no good return it to normal.
Sent from my Desire HD using Tapatalk
Blinkydamo said:
I can usually get to the end of the day and still have about 30% left, but I an a heavy user and running the WiFi all evening, do a good 3-4 hours of browsing each day as well as other stuff.
This is not a problem for me as I charge every night. You should give it a go, if its no good return it to normal.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
And you do experience a performance boost when overclocking it to 1,2 ghz?
Yes mate, I have a few profiles setup, when charging I have it set to 1.5ghz on performance, normal running is 1.2ghz on interactive and screen off set to 245mhz powersave. The phone is very fast, wakes up well and isn't doing to bad with the battery. The battery life will get better as the development of the Rom continues.
Sent from my Desire HD using Tapatalk
I just flashed the latest nightly build of 15 and it is just as fast as stock rom. Did not notice any slowness.
So on the miui.us.us latest after installing tiamat kernel everything works great...but do I need to install something like setCPU(which I would like to avoid) to set clock speeds etc etc. I'm pretty sure you do seeing how I can't find it anywhere in settings. I know in roms such as mexdroid and the like new kernels replace "performance settings". So I'm thinking I need to use setCPU.
Thanks for any help given
Sent from my HTC Desire Z using XDA Premium App
I'm not completely sure about that specific kernel, but its a pretty good idea to run SetCPU if your ROM doesn't include CPU settings.
For example, if the kernel you installed OC's up to 1.5ghz or something, you may prefer to run at a lower frequency. SetCPU is probably a good idea. Also, if you want to run at 1.5ghz you're going to need SetCPU profiles for heat and screen off, etc.
martonikaj said:
I'm not completely sure about that specific kernel, but its a pretty good idea to run SetCPU if your ROM doesn't include CPU settings.
For example, if the kernel you installed OC's up to 1.5ghz or something, you may prefer to run at a lower frequency. SetCPU is probably a good idea. Also, if you want to run at 1.5ghz you're going to need SetCPU profiles for heat and screen off, etc.
Click to expand...
Click to collapse
Thanks for response. I know all about setCPU, I just don't like it. But yeah looks like that's the only option. Although miui.us seems to be clocked at 1GHz so I think I'll just stick with that.
Thanks again...and tiamat kernel works great on it
Sent from my HTC Desire Z using XDA Premium App
Spastic909 said:
Thanks for response. I know all about setCPU, I just don't like it. But yeah looks like that's the only option. Although miui.us seems to be clocked at 1GHz so I think I'll just stick with that.
Thanks again...and tiamat kernel works great on it
Click to expand...
Click to collapse
Good. Yea I don't like setCPU either. I use the built in controls in CM7. If you're happy with the stock clock speed and don't have issues you won't need to use it.
Sent from my CM7-powered T-Mobile G2
I wonder wat causes all the random reboot,is it got to do with undervolt,overvolt,CPU speed and minfree value?
Sent from my Desire Z using xda app-developers app
Steven How said:
I wonder wat causes all the random reboot,is it got to do with undervolt,overvolt,CPU speed and minfree value?
Sent from my Desire Z using xda app-developers app
Click to expand...
Click to collapse
..overvolt?
Anyway undervolting and CPU speed can definitely cause reboots. Some phones can't go beyond 1.2GHz and I know undervolting can cause instability when brought down too low.
Personally I haven't had a random reboot in as long as I can remember, but I also don't undervolt and I don't OC past 1.2GHz.
Well,I'm using sense rom in the moment,enabled swap and supercharge.. and oc it at 468-1458mhz.. =\ still reboot,does vm heapsize affect rebooting?
Sent from my Desire Z using xda app-developers app
Steven How said:
Well,I'm using sense rom in the moment,enabled swap and supercharge.. and oc it at 468-1458mhz.. =\ still reboot,does vm heapsize affect rebooting?
Sent from my Desire Z using xda app-developers app
Click to expand...
Click to collapse
My phone's upper limit is also at 1.4GHz, runs stable on it, but haven't really felt the need for that. One thing that comes to mind is that your lower limit is pretty high. What governor do you use? Do you have a profile for screen off and what's the frequency fork there?
I would assume that with that setup the phone gets pretty heated, which could very easily cause random reboots. Any idea what temperature it usually runs on?
Myth010 said:
My phone's upper limit is also at 1.4GHz, runs stable on it, but haven't really felt the need for that. One thing that comes to mind is that your lower limit is pretty high. What governor do you use? Do you have a profile for screen off and what's the frequency fork there?
I would assume that with that setup the phone gets pretty heated, which could very easily cause random reboots. Any idea what temperature it usually runs on?
Click to expand...
Click to collapse
468-1457mhz smartass screen in,122-468mhz screen off conservative.. =\
Sent from my Desire Z using xda app-developers app
Maybe you should try lowering the upper limit to 1.2GHz for a while see if it makes any change... in the meantime it might be helpful to know:
a) Which specific rom are you using?
b) Any custom kernel?
Myth010 said:
Maybe you should try lowering the upper limit to 1.2GHz for a while see if it makes any change... in the meantime it might be helpful to know:
a) Which specific rom are you using?
b) Any custom kernel?
Click to expand...
Click to collapse
Android revolution 6.3.3 (sense 3)
And unity v9 kernel..
Sent from my Desire Z using xda app-developers app
mine used to reboot when i first had it, searched the net & it suggested the sim card.... made sure it was pushed in properly & its been fine ever since....
I found out when I use this android revolution 6.3.3 rom,and flash a music player mod by lyapota,it mix up the word,like holding home it appear recent app,but after flashing I get your personal information and if I use home long press to multitask,the whole phone will just reboot :/
Sent from my Desire Z using xda app-developers app
Ive done a lot of seaching but cant seem to find the answer....
I have a P936 running a slightly modified version of AT & T's ICS P930 ROM and Kernal.
Ive just finished setting up everything but want to overclock and dont know which kernal to choose.....
Any help? My software version is V20c.....
Use wind kernel, you won't be disappointed. Just make sure you run through the whole thread for the p930/6 version. I'm now using it on a clean v20f, couldn't be happier.
Sent from my LG-P930 using xda app-developers app
Awsome, thx man! Im rockin at 1800MHz now
But now I also want to OC the GPU, know any good app for that? I cant seem to find one...
Faux123 kernel tool is designed to work with windkernel and allows gpu over clock and many other useful tools for kernel tuning
Sent from my LG-P930 using xda app-developers app
Faux clock lets me set the GPU's 3D clock speed to 320MHz and thats where Ive got it. But the Wind kernal is also supposed to allow overclocking the 2D speed. How do you do that? Cant find any setting for that in the faux app. They say something about echoing something somewhere in the Wind kernal thread.... Any help?
StashCompInc said:
Faux clock lets me set the GPU's 3D clock speed to 320MHz and thats where Ive got it. But the Wind kernal is also supposed to allow overclocking the 2D speed. How do you do that? Cant find any setting for that in the faux app. They say something about echoing something somewhere in the Wind kernal thread.... Any help?
Click to expand...
Click to collapse
Use a terminal emulator app and run the commands listed in that thread exactly as written in the thread to overclock 2d
Sent from my LG-P930 using xda app-developers app
Hutch89 said:
Use a terminal emulator app and run the commands listed in that thread exactly as written in the thread to overclock 2d
Sent from my LG-P930 using xda app-developers app
Click to expand...
Click to collapse
Ok but then will the setting stick or do I have to set it again via terminal every time I reboot?