I've seen that happen. I did an autodetect on a ROM cooked to run 710 and, for some reason, the autodetect decided that the CPU could run as high as the high 800s. So, the slider was about 2/3rds of the way to the end, and once I accidentally hit the slider and it froze my phone up right quick.
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root setcpu force close
- Thread starter chaos32
- Start date
-
- Tags
- htc droid eris
I've seen that happen. I did an autodetect on a ROM cooked to run 710 and, for some reason, the autodetect decided that the CPU could run as high as the high 800s. So, the slider was about 2/3rds of the way to the end, and once I accidentally hit the slider and it froze my phone up right quick.
Maybe the right approach to setting it up correctly without immediately freezing/crashing the phone is to avoid touching those sliders on the Main tab until AFTER profiles have been set up and enabled. I'm guessing (a W.A.G., actually) that the first touch of that slider causes the phone to immediately change it's OC settings - and that's what is causing chaos' crashes.
Some time ago, SetCPU didn't work that way - you had to do some other actions (I can't remember) for your settings to "take". If the OC values change immediately when you touch the slider, that's extremely dangerous (if you happen to accidentally set a value which is too high or too low).
Anyways, that's a prescription - but one I haven't tried.
eu1
WormDoes
Android Expert
Anyone have a problem with the setCPU widget never updating? I have my screen off profile set to 245/245 & whenever I wake my phone up my widget always reads 245/245. I have my normal ondemand profile set at 710/528. Even if my screen has been on for 5-10 minutes the widget never updates. I have updates set at 60 seconds so I don't understand what's going on here. Has this ever happened to anyone else?
lukesdiesel
Android Enthusiast
Ive noticed with my Eris that anything over 710 just kills the battery life. And anything over 787 freezes my phone.
I was just looking at this again. Based on the priority of these, I believe that the Charging/Full profile will only kick on when the battery is fully charged. (Of course, when the battery is better than 65% and less than 100%, the settings for "Battery <100%" are exactly the same.)
For anybody who wants to duplicate these but wants the phone to OC to 729 while it is charging, IMHO the priority of that profile should be higher. Also IMHO, it should definitely be lower that the temperature high profile - you want that to overrule over all. I'd suggest that the temp high priority be set to 100 so you never accidentally set another profile higher.
You are correct in your analysis, doogald - I put that profile in there so that the phone would know what to do when the phone was charged to exactly 100%
(Anything less than 100% and a different profile would take over - a profile with the same min/max values)But that's a "lifestyle choice" - if your phone is being clocked fast, it won't charge quite as quickly; so - when you plug it in to the charger, do you want it to "run fast" or "charge quickly" ?
The one other thing my profile needs is a "screen off" profile - and as you point out, it should be set below (in priority) the over-temperature profile, but above all the "battery %" profiles - that use higher clocking speeds.
Probably also for the convenience of further editing, you should set the profile priorities with big gaps between them, so that if you want, it is easy to slip something in between any two existing profiles
Maybe something like
Code:
[B]Pri Min Max Cond[/B]
100 160 480 Temp > 50.0C
70 160 480 Battery < 20%
60 245 480 Screen Off
50 245 528 Battery < 40%
40 480 710 Battery < 65%
30 480 729 Battery < 100%
20 480 729 Charging/Fullcheers
eu1
PS: My "max temp" limit of 50C might be considered high, but that's only because I am not currently using the phone for extended periods of time at high temperatures. If you were going to use the phone for wireless tethering purposes (all radios & cpu going full tilt), I would set that value lower - possibly down to 40C.
.
Honestly, I also have a profile set to clock at 528 max while charging, but I do that because I consider both charging and overclocking a heat risk for the CPU, and I want to be safe - and I am almost always charging the phone when I am not actively using it anyway.
I do have a screen off profile myself, set at the second highest priority.
I have my temp set at 40C because I don't want to think about when I may be running it hot and adjust manually - I want it to be fairly automatic. I brought my phone to the beach while on vacation (in a ziplock bag to keep out sand and water, of course) in case I needed it, and, after making one call, the temp was at 43C. And the one time I did a Nav (just to test it out, and before I knew about the temp failsafe profile - this was back about 7 weeks) I was driving in an air conditioned car for 30 minutes and the phone was so hot when I arrived that it was almost hard to hold. Thankfully, there have been no consequences from that, but now I'm glad I know about all of this to help protect the phone.
Good post, thanks.
I do have a screen off profile myself, set at the second highest priority.
I have my temp set at 40C because I don't want to think about when I may be running it hot and adjust manually - I want it to be fairly automatic. I brought my phone to the beach while on vacation (in a ziplock bag to keep out sand and water, of course) in case I needed it, and, after making one call, the temp was at 43C. And the one time I did a Nav (just to test it out, and before I knew about the temp failsafe profile - this was back about 7 weeks) I was driving in an air conditioned car for 30 minutes and the phone was so hot when I arrived that it was almost hard to hold. Thankfully, there have been no consequences from that, but now I'm glad I know about all of this to help protect the phone.
Good post, thanks.