ok so im running the STOCK GB but im rooted and have been running gingertiny 9/29 ran into rebooting issues.. phone constently reboots after 20 mins of use. usually when this happened before like on stock kernels the battery temp would rise up to 104 but i kept eyes on the temp and it never goes over 78.4 F
not overclocking cpu im actually running at about 625 mhz but issue still occurs
SO with that being said i need help finding either a better kernal or trying to find solutions with this one.
i went back to complete stock and rooted to see if i still have this issue
any help will do thanks!
These questions belong in the Q/A section. This has zero relevance to development.
Now:
1) pull the battery then place it back into your phone.
2) Charge it awhile to make sure you haven't dropped a considerable charge during the bootloops.
3) Turn your phone on and move your clock speed towards 998400 (stock clock speed) via setcpu or however you underclocked.
This bootloop is likely due to you being underclocked so low. If you want, flash Tiny's latest kernel from 9/29/2011 to bring yourself up to date.
Was your min clock speed underclocked below the stock 245000? I had random reboot issues when I underclocked my min to 128000.
Having your max_freq set at 628 or whatever it was shouldn't cause reboot issues. You're phone should be rock-solid stable at a speed like that. I'd suggest taking a look at your voltages.
I've never run that kernel so I'm not familiar with what the voltage table looks like, but it might very well be that your voltage is too low. If your max_freq were higher, the transition through that clock freq would probably be too brief to cause an issue. I don't know if that kernel has sysfs enabled, but if it does, upping the voltage at that step .25 volts should cure it.
Min speed was at 628 even switching back to stock kernel still having issues I'm not sure what can be the issue I only last few mins playing any games or watching anything all speeds are stock
Sent from my ADR6300 using XDA App
Sounds like it's time to start wiping stuff.
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.
I'm looking to optimize my battery life without sacrificing performance when I need it. I know it sounds easier said than done, but I figure that if anyone might know how, they'd be here. My goal here is to have the performance when I need it, and to keep the battery preserved when I don't.
I'm rooted and running ViperROM 4.0.4 Trinity v2.0. I have the "Genocide 1.2GhzOC EB13 Kernel v0.3a" kernel also flashed to my phone. SetCPU is installed and I've set up my profiles, but I think I may be doing something wrong with them.
I am using autodetect settings as is recommended for adjusting clockspeed. Everything is set to on boot. All profiles are set to conservative as I'm not sure which ones actually apply. Below are screens for everything I have currently set up.
|
|
Am I doing anything wrong here? And if not, is there anything I need to do to improve battery life without sacrificing performance?
I would bump your charging max to 1200Mhz and keep the min at 1000Mhz, although I keep max and min while charging through AC power at 1200Mhz.
Your screen off profile is fine. If you get hiccups or missed calls for any reason, bump the max up to 400Mhz.
If you can run it smoothly, set your minimums for your battery profiles to 100Mhz. It what I'm at now and it runs fine. You may want to keep your minimum for your "screen off" profile at 200Mhz if you get hiccups or missed calls like I mentioned before.
As for your battery <50% profile, I'd set the min at 200Mhz if you're wanting to save battery. Don't want the phone running at a higher clock when it doesn't need it. That's the point of running the min lower.
I personally uncheck the "set on boot" to allow SetCPU to always come back to the appropriate profile rather than going back to the default setting.
Also, set a Battery < 101% profile which will be your new default. I have mine at max 1000Mhz and min 100Mhz and it works well.
Also, conservative simply means the battery will remain at the lowest possible clock until it needs more juice. Assuming it starts at 200Mhz, it'll bump up to 400Mhz, 800Mhz, etc. depending on what the demand is. It will jump frequencies from 200Mhz to 1000Mhz if necessary.
On Demand means the CPU will either be at your minimum set clock frequency or your maximum.
On Demand is usually the most compatible/stable, but the conservative setting is best for battery/performance if your kernel allows it.
Hope this helps =). Let us know if you have more questions.
EDIT: The "set on boot" button simply sets the min and max that's shown on the main screen in SetCPU. If this button is unchecked but the "enable" button on the profiles menu is checked, your profiles will still adjust accordingly.
I can't really see the profiles but do you have the Max set at 400 when the battery is under 50%? If you do your phone will crawl. The 1000 is undervolted. That way you get speed and save battery. And on demand does not.mean that your CPU is either at min. Or Max. It means that it Scales faster then Conservative does. My profiles are when battery is less than 50% I go to 1000/100 and when screen is off I'm at 200/100 all set on demand. My regular setting.is 1200/100.
Sent From My Evo Killer!
I'd like to hijack this since I have a similar question.
I'm using ACS Frozen 1.0 and have the latest SetCPU and am still getting pretty crummy battery life.
The weird thing is that in SetCPU the maximum CPU frequency is always 1.2ghz even if I drag the slider down to 1.0. I don't currently have any profiles enabled that would cause this, so why won't SetCPU let me top off a 1ghz undervolted instead of 1.2ghz?
My battery life definitely hasn't improved at that's a big bummer for me :\
I also have a question. I kept getting a message about superusers rights not being given. I searched to see how to grant SU rights, but could not fond any. I turned the phone off and on, and that message did not pop up anymore.
Now the main screen I cannot adjust any of the numbers, is this normal? I can however enable and make profiles. I made the first one if temp is greater then 0 (I obviously do not want it like this, but its just a test) then it should be OC to 1200. When I saved this in the top right hand corner it says I am at 1200, however when I bring up a program, and go to setcpu and look at the main screen it says 1000.
So what am I doing wrong.
badbeats said:
I also have a question. I kept getting a message about superusers rights not being given. I searched to see how to grant SU rights, but could not fond any. I turned the phone off and on, and that message did not pop up anymore.
Now the main screen I cannot adjust any of the numbers, is this normal? I can however enable and make profiles. I made the first one if temp is greater then 0 (I obviously do not want it like this, but its just a test) then it should be OC to 1200. When I saved this in the top right hand corner it says I am at 1200, however when I bring up a program, and go to setcpu and look at the main screen it says 1000.
So what am I doing wrong.
Click to expand...
Click to collapse
This might be a dumb question, but is your phone fully rooted?
I think so I used Clockwork mod 3.0.6 and I am running Bonsai 3, with 2.2.1
ZeppelinJ0 said:
I'd like to hijack this since I have a similar question.
I'm using ACS Frozen 1.0 and have the latest SetCPU and am still getting pretty crummy battery life.
The weird thing is that in SetCPU the maximum CPU frequency is always 1.2ghz even if I drag the slider down to 1.0. I don't currently have any profiles enabled that would cause this, so why won't SetCPU let me top off a 1ghz undervolted instead of 1.2ghz?
My battery life definitely hasn't improved at that's a big bummer for me :\
Click to expand...
Click to collapse
Yeah I hear you, I get the same crummy battery life with SyndicateROM, I was dying for the 30 hours ! Starting to think it's the battery itself.
musclehead84 said:
I can't really see the profiles but do you have the Max set at 400 when the battery is under 50%? If you do your phone will crawl. The 1000 is undervolted. That way you get speed and save battery. And on demand does not.mean that your CPU is either at min. Or Max. It means that it Scales faster then Conservative does. My profiles are when battery is less than 50% I go to 1000/100 and when screen is off I'm at 200/100 all set on demand. My regular setting.is 1200/100.
Sent From My Evo Killer!
Click to expand...
Click to collapse
Do you keep your 1200/100 on conservative? And what's the battery life you're getting on average? Dummy question but you know...
I'm going to try out this setting today actually with BakedSnack.
Referring to those of you getting "crummy" battery life. The screen takes so much battery many other things don't come into play. Therefore, if you're getting 4-6 hours of screen-on time, you're getting about what everyone else is getting. Those who report 30 hours+ probably have there phone idle more often than not.
Blankrubber said:
Referring to those of you getting "crummy" battery life. The screen takes so much battery many other things don't come into play. Therefore, if you're getting 4-6 hours of screen-on time, you're getting about what everyone else is getting. Those who report 30 hours+ probably have there phone idle more often than not.
Click to expand...
Click to collapse
Ahh this is a good point then. I'm still confused though why when I set my SetCPU to 1ghz it still keeps it at 1.2 :\
ZeppelinJ0 said:
Ahh this is a good point then. I'm still confused though why when I set my SetCPU to 1ghz it still keeps it at 1.2 :\
Click to expand...
Click to collapse
Did you update to the latest Twilight kernel? It's 1.0.1 I believe. Try that as I believed it fixed some CPU scaling issues. Just install the zip in CW, but I'd still wipe cache at last, just in case.
Sent from my SPH-D700 using XDA App
Blankrubber said:
Did you update to the latest Twilight kernel? It's 1.0.1 I believe. Try that as I believed it fixed some CPU scaling issues. Just install the zip in CW, but I'd still wipe cache at last, just in case.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
+1 I think this was a bug with the original release of Twilight Zone that was fixed in 1.0.1.
Blankrubber said:
Did you update to the latest Twilight kernel? It's 1.0.1 I believe. Try that as I believed it fixed some CPU scaling issues. Just install the zip in CW, but I'd still wipe cache at last, just in case.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
I'm trying this out right away, thanks!
This whiny message brought to you by the letter E for Epic 4g
I have looked around and completed a few searches but cannot find any direct answers to this.
I have CPU Spy installed and have been checking it off and on since I got the phone. I have noticed that my phone does not run at any speed other than the absolute max. The phone does go into Deep Sleep without issue, but the only CPU speed it uses is 1728. I have tried a few ROMS without any change.
Currently running Juggernaut 5.0 with Darky's Kernal.
I have tried different Governers. I have tried Antutu's CPU Master, SetCPU and No-Frills. I just cannot get this phone to run anything other than MAX speed. Since I am constantly having things run in the background like music, this is effecting my battery life.
Anyone have any input, ideas or suggestions? Other than running stock.
Turn down your minimum CPU settings in set CPU and check set on boot?
Sent from my SGH-T989 using Tapatalk
You've done just about everything possible. Only option left it to Odin back to stock, root it and check cpu Spy to see if it is acting normal. If it is back to normal flash back to your favorite distro!
Perhaps something got messed up along the way of flashing all those roms? Shouldn't, but you never know.
da_dragon2k3 said:
You've done just about everything possible. Only option left it to Odin back to stock, root it and check cpu Spy to see if it is acting normal. If it is back to normal flash back to your favorite distro!
Perhaps something got messed up along the way of flashing all those roms? Shouldn't, but you never know.
Click to expand...
Click to collapse
I was really hoping it would not come to this :'(
*update....
I re-flashed Darky's Kernal and removed all OC apps and now I am showing full utilization of the different seed steps.
Quite glad it did not result in me having to start over again.
since i cant post this in the dev for cm10 i have to post this here. i installed it last night on my phone and everything has been running pretty good. i understand its still a wip so im not complaining. what has come to my attention is the fact that my phone now likes to run at 1026 no matter how low i set it at. if its sitting there itll change to 384. when i was on stock rom rooted and unlocked, it would never change speed on powersave. now if i go into antutu or just performance under settings minimum will always change to 1026. i havent had a chance to really test if its affecting my battery life but i can let someone know. im bringing it up so maybe the devs can have their way with it. if theres any way i can help, just let me know.
0328 update
with the latest update the speed issue is still there and the camera has been improved although i havent tried video yet. but on 0327 it has like a staircase set up on the upper lefthand side of the screen. did a wipe and fresh 0328 so ill see how that goes. keep up the great work and as always let me know if there is anything i can do to help.
update:recorded video still has issue but nexus7 camera apps work perfectly to get to camera here. flash or the camera worked once and hasnt worked since. still a great rom.
It looks like you're not using the latest cm10 builds, you need to hit the "next" thing on the top right of the download page.
I recommend taking a spin with the houcha kernel. It's pretty much fixed the cpu stuff, and intellidemand governor is amazing; Turns off 3 cores when nothing is taxing and idles at correct minimums.
They are always up to date with the cm10 kernel commits as well.
I get amazing battery life.
Sent from my LG-LS970 using xda app-developers app
0429 update
yeah. its running pretty good. the video recording is fixed so that helps me out at work. with all the phones and tablets i have, i havent installed another kernal so thats the only thing im a little sketchy on doing. but since you recommend it i think i have to give it a look. if theres anything i should know about it, just let me know.
I was on the latest update but I just fat fingered my posts and wasn't double checking it. Just had to install a keyboard that better suites me.
update-flash on the camera work only when i use touch to focus. does that kernal help with that?
clean install of 5/5
Did a clean install last night with standard 4.2.2 gapps. Camera icon has has appeared without the need to install a 3rd party app to access it. Battery life is about the same as before with installing a different kernel. As my daily driver I would recommend it all the way. Follow the forums specific to the ROM and you can't go wrong. I'll keep updating about the progress until I can post on there.
powersave for cm10.1
If you want to get powersave to work correctly; 1.set both speeds to the same number 2.must be below 1026.
If you set them both to 1026, they will stay at that speed. If you set them to two different numbers the minimum and maximum will default to 1026 and1350, respectively, when the system feels it needs the power above 384 and will stay there. Hopefully this will help someone out.
The reason the cpu speed gets raised to 1026 is due to mpdecision. It boosts the cpu speed on touch to increase the interactivity and decrease the lag. mpdecision is a qcom blob and since we are trying to stay as close to mako as possible these is nothing I can do about that blob.
Then I guess my question is why on stock I can run at 384 min with max at 1512 on powersave and it'll actually run at 384 but this cant?
fine for me
I have not really had this problem at all weird
harrybear25 said:
I have not really had this problem at all weird
Click to expand...
Click to collapse
So what min and max speeds is your phone set at? What speed does it end up at after using it for 5 mins on the net?
5/14
my powersave settings with the max at 1512 and min at 384 seemed to stick longer than normal with this rom. im going to backup everything, revert back to zvb and then do a clean install of the latest and see how that fairs.
Did a full restore of my phone back to zvb. Did all the GPS stuff I needed to, rooted and unlocked. Proceeded to do a full wipe and install of 5/27 ROM. Speed issue still there but as noted before I found a small workaround and randomly today I got a message that maps had stopped working.
I did play around with the ROM before install gapps and found some interesting things. None really stuck out except Bluetooth not working at all.
After installing gapps, everything seems to work perfectly. Downloading 5/28 right now and dont expect much to change. Some updates hold my speed settings and some dont. Not really an issue.
6/1 build
powersave function was working correctly with the max at 1512 and the min at 384 right after initial update. using antutu the temp and battery level would be displayed incorrectly. after the first reboot though, everything went back to "normal." but on the brightside if you set the max to 918 and the min at 384 on powersave, it appears to now stay that way. no more having to set them both at the same speed. i will continue to play with the speed settings and see if anything else comes up.