Hi I have an xperia play with doomkernel @ 1.7ghz stable.. Well that is until I leave it charging overnight then maybe twice a week wake up to find it stuck in a boot loop. Thing is I have a profile in CPU that underclocks when screen is off. I'm thinking its to do with temp coz after this happens the phone is hot and has that unmistakable electrical smell I remember from when I tried to OC to 2.0ghz (which froze phone until I removed batt). Thing is phone works 100% stable at 1.7ghz for hours on end when I'm actually using it, its only going into loop occassionally after being left on charge overnight (underclocked). Have searched forums but couldn't find an answer to my particular problem, any suggestions?
You answered your own question. At 1.7ghz your CPU will be creating maybe double the heat it would normally, the CPU is designed to reboot device when it is being stressed to prevent damage to the SOC. I suggest maybe your device is not as stable as you think at such a high clock speed. The fact your device is rebooting at all is a warning that you are pushing it too far and at risk of damaging it.
Sent from my R800i using Tapatalk
k
AndroHero said:
You answered your own question. At 1.7ghz your CPU will be creating maybe double the heat it would normally, the CPU is designed to reboot device when it is being stressed to prevent damage to the SOC. I suggest maybe your device is not as stable as you think at such a high clock speed. The fact your device is rebooting at all is a warning that you are pushing it too far and at risk of damaging it.
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
doesn't the processor only overclock when it is needed.?
like it will run the. lowest speed needed to complete current tasks
Sent from my R800i using Tapatalk
fma965 said:
k
doesn't the processor only overclock when it is needed.?
like it will run the. lowest speed needed to complete current tasks
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
That depends on the governor, for example the performance governor, is either at min or max, there is no inbetween, add a hot charging battery and well .....
Sent from my R800i using Tapatalk
AndroHero said:
You answered your own question. At 1.7ghz your CPU will be creating maybe double the heat it would normally, the CPU is designed to reboot device when it is being stressed to prevent damage to the SOC. I suggest maybe your device is not as stable as you think at such a high clock speed. The fact your device is rebooting at all is a warning that you are pushing it too far and at risk of damaging it.
Sent from my R800i using Tapatalk
Click to expand...
Click to collapse
The thing its not overclocked when it restarts. I have it set @ 245/768 min/max on smartass v2 governor when in the "screen off" profile, wouldnt that still apply even while charging?
Try ondemand governor...That works for me. Also it is set at 122/652.
Edit: I think "screen off" profile is different than "charging" profile..
Sent from my R800i using XDA App
ryballs said:
The thing its not overclocked when it restarts. I have it set @ 245/768 min/max on smartass v2 governor when in the "screen off" profile, wouldnt that still apply even while charging?
Click to expand...
Click to collapse
It could be something simple like underclocking too much, a lack of voltage would also cause a reboot.
Sent from my R800i using Tapatalk
Thanks everyone for your help it seems the screen off profile doesn't apply whilst charging ;p
ryballs said:
Thanks everyone for your help it seems the screen off profile doesn't apply whilst charging ;p
Click to expand...
Click to collapse
I have identical problems, how did you solve it
Related
hey all, couldnt search forums since its disabled. so like my title says, my phone turns off whenever. the samsung logo comes up and turns off. it happens every so often but nothing annoying. to get it back on is either take battery out or plug to charger and turn it on. when i did this, it gave me the searching for battery thing. this leads me to believe it could be battery? it happens whether the battery is 90% or 20%. anybody have this problem? my phone is rooted using juggs 5.0. phone is just over a month old so wonder if i can get a replacement battery to ruled that one? thanks for the help..
Mines does the same thing except it only reboot when its on charge, and all my contacts dissapear
@OP: Try flashing a different ROM.
Juggernaut has pretty aggressive UVing that not all phones might like.
It happened to me just today. I tried opening Facebook and for whatever reason it FCed. So I reopened it and my phone just turned off. I had to hold the power button for 15 seconds before I felt a vibration and it was alive again. Not sure what the issue is but it's safe to say you're not the only one experiencing this
NJ_RAMS_FAN said:
hey all, couldnt search forums since its disabled. so like my title says, my phone turns off whenever. the samsung logo comes up and turns off. it happens every so often but nothing annoying. to get it back on is either take battery out or plug to charger and turn it on. when i did this, it gave me the searching for battery thing. this leads me to believe it could be battery? it happens whether the battery is 90% or 20%. anybody have this problem? my phone is rooted using juggs 5.0. phone is just over a month old so wonder if i can get a replacement battery to ruled that one? thanks for the help..
Click to expand...
Click to collapse
Random reboots are usually a sign of too aggressive of undervolting. If it's not happening under heavy CPU load and is just happening during standby/sleep phases, then you're just barely on the edge of too much undervolting. Download system tuner from the market and go to voltages in the main menu then knock up the voltage one step (+12.5mV). You should be fine then.
For reference, you can compare your voltages to this list of stock voltages to see what Jugs' global undervolt is. I'm not too familiar with Jugs v5.0:
http://forum.xda-developers.com/showthread.php?t=1523064
yoft1 said:
Random reboots are usually a sign of too aggressive of undervolting. If it's not happening under heavy CPU load and is just happening during standby/sleep phases, then you're just barely on the edge of too much undervolting. Download system tuner from the market and go to voltages in the main menu then knock up the voltage one step (+12.5mV). You should be fine then.
For reference, you can compare your voltages to this list of stock voltages to see what Jugs' global undervolt is. I'm not too familiar with Jugs v5.0:
http://forum.xda-developers.com/showthread.php?t=1523064
Click to expand...
Click to collapse
cool. I give this a try. The last time it turned off was right after I used gps. yesterday I was just browsing. thanks again.
Are you overclocking? If so what freqs/governor? Mine would do this when I would clock it too high for too long. May be an undervolting problem as well.
AaronPauley said:
Are you overclocking? If so what freqs/governor? Mine would do this when I would clock it too high for too long. May be an undervolting problem as well.
Click to expand...
Click to collapse
Your overclocking issue is actually still an undervolting issue. Your phone would reboot after overclocking for long periods of time because the processor wasn't getting supplied enough voltages for those higher clock speeds.
Undervolting isn't a linear process: if you run a global -50mV undervolt and cap your processor at 1.5Ghz, that doesn't mean that you can run a -50mV undervolt at a 1.8Ghz cap. For example, I'm currently undervolted -112.5mV at 1.35Ghz but if I bump my processor to 1.8Ghz, my phone reboots immediately because -112.5mV for 1.8Ghz is way too big of an undervolt.
yoft1 said:
Your overclocking issue is actually still an undervolting issue. Your phone would reboot after overclocking for long periods of time because the processor wasn't getting supplied enough voltages for those higher clock speeds.
Undervolting isn't a linear process: if you run a global -50mV undervolt and cap your processor at 1.5Ghz, that doesn't mean that you can run a -50mV undervolt at a 1.8Ghz cap. For example, I'm currently undervolted -112.5mV at 1.35Ghz but if I bump my processor to 1.8Ghz, my phone reboots immediately because -112.5mV for 1.8Ghz is way too big of an undervolt.
Click to expand...
Click to collapse
Thanks for the clarification. I've not really dabbled in undervolting much, and haven't been too concerned with overclocking since the ol' mt3g days. I'm definitely going to read more about it. I've found that for my s2, stock kernel w/ stock frequency set and governor have worked best. Every device is different they say. Thanks your way for the knowledge. Always appreciated.
yoft1 said:
Your overclocking issue is actually still an undervolting issue. Your phone would reboot after overclocking for long periods of time because the processor wasn't getting supplied enough voltages for those higher clock speeds.
Undervolting isn't a linear process: if you run a global -50mV undervolt and cap your processor at 1.5Ghz, that doesn't mean that you can run a -50mV undervolt at a 1.8Ghz cap. For example, I'm currently undervolted -112.5mV at 1.35Ghz but if I bump my processor to 1.8Ghz, my phone reboots immediately because -112.5mV for 1.8Ghz is way too big of an undervolt.
Click to expand...
Click to collapse
Thanks for the clarification. I've not really dabbled in undervolting much, and haven't been too concerned with overclocking since the ol' mt3g days. I'm definitely going to read more about it. I've found that for my s2, stock kernel w/ stock frequency set and governor have worked best. Every device is different they say. Thanks your way for the knowledge. Always appreciated.
Hi! I noticed that according to Franco's app my CPU temp is almost always above 40 degrees just after some usage (Facebook,browsing,texting) and only drops to around 28 degrees after being idle. As this is causing throttling I wanted to ask if it was just me or are these normal temperatures?
I am running Franco Kernel r98 with no CPU overclocking or undervolting
Sent from my Galaxy Nexus using XDA
Thanks Can you please tell me how ro set the throttling settings?
Sent from my Galaxy Nexus using XDA
bencozzy said:
On cellular data yes fairly normal.
All the way up to 60c on our CPU can be sustained with out to much harm.
Click to expand...
Click to collapse
Agreed. 60c is probably a conservative termal design limit (I'd expect something at a minimum of 80-100c before there was any actual damage to the CPU. Though, that kind of temp would probably damage your HAND or the plastic housing before the silicon. Anyone know why anyone would force throttling at only 40c? Power conservation comes to mind.
bencozzy said:
True power conservation, but now we are making it complete a task at 700mhz for twice as long when it could be done in a flash at 1350 MHz kind of defeats the purpose? That's like hot plugging good in theory but real world says other governors give same battery life and without the instability lagginess.
Click to expand...
Click to collapse
I though someone did some real world testing a while back and found that 2x700MHz drew less power than 1x1350MHz?
after root... i have installed SetCpu, i have overclock my processor to 1.4ghz.. the question is, can i use this setting for daily use? is it will cause my processor hot or damage??
I think there are still profiles you can make so if the internal temp reaches a certain point, it will underclock the processor, that is what I did for my Droid Incredible. Just keep an eye on it (there is a widget in SetCPU) for a day or two and if it seems stable then there you go!
FYI if you choose to create a profile to underclock it, I highly recommend also making one to set it back to normal (<= 1.2 Ghz) when charging because my Nexus tends to heat up a bit when plugged in to the AC outlet.
The CPU gets throttled automatically once it hits a certain temperature.
On Franco kernel its 75c.
The CPU will shut down automatically at 110c to prevent damage.
By its very nature, overclocking is going to shorten the life of your hardware. How much so is anyone's guess. While it could be significant, the odds are that it will last well past you moving on to your next phone. That being said, only you can answer whether or not 1.4 will be a good, stable daily driver on your phone.
Sent from my Galaxy Nexus using Tapatalk 2
Yeah, but the question is "why?". You don't need it, so why kill battery/raise temp for the hell of it?
theking_13 said:
Yeah, but the question is "why?". You don't need it, so why kill battery/raise temp for the hell of it?
Click to expand...
Click to collapse
Because its fun and because we can.
Same reason we drink too much.
I have been using francos app along with kernel version 3.61. I set the minimum freq to 1.8 and then moved to set the max 1.8 and then that sent it into a boot loop and the back got real hot. I don't know what happened maybe between charging which makes it also hot contributed to it. Has this happened to anyone else. I tried it again but not plugged in and it was fine.
Why would you set Min and Max frequency the same? Over clocking increases the core(s) temperature, to much and you'll fry your device.
Sent from my Galaxy Nexus using xda premium
pr0xyw0rm said:
Why would you set Min and Max frequency the same? Over clocking increases the core(s) temperature, to much and you'll fry your device.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I think it's indeed the problem of overheating that causes the bootloop.
@TS: My Galaxy Nexus is blazingly fast at max 1,4 and min 400. It's no use to set min and max at the same frequency.
Good to know. I won't try that again.
Was that a safety thing related to temp?
F-Fect said:
I think it's indeed the problem of overheating that causes the bootloop.
@TS: My Galaxy Nexus is blazingly fast at max 1,4 and min 400. It's no use to set min and max at the same frequency.
Click to expand...
Click to collapse
Overheating won't cause a bootloop. The phone has built in safeties that force it to downclock regardless of your settings if it gets too hot. What will cause a bootloop is setting your phone to a frequency that is unstable, especially if you set it as min and max.
How much can the phone be underclocked while maintaining the stability of the system?
What would happen if i set Max freq to 600 Mhz?
What is the best thing to do to save up the very last bit of juice in the battery for emergency situations where i would only need the phone and message facility? Besides switching off Bt,wifi,sync.
Im asking because i was wondering if underclocking "too much" saves a substantial amount of battery when my battery is quite low and I am "hours away" from a charging port!
And is there a way to change the carrier name on the notification drop down to whatever we want.
Sorry if i sound noobish or if a similar query has been asked before
Thnx.
Underclocking the CPU dramatically isn't going to gain you a great deal in the way of extra battery life because:
1. Unless you are heavily taxing the CPU (complex 3d games etc), the biggest drains on the battery are the screen and the radio.
2. If the screen is off, the phone will drop the CPU frequency right down anyway.
The best way to get extended battery life is simply to carry spare batteries!
Regards,
Dave
Sent from my GT-N7100 using Tapatalk 2
I think 600mhz is way too low and counter productive or for that matter anything less than 1ghz. The phone will lag alot and you'll have freezes. You'll probably end up using up alot of the battery life trying to get tasks completed. You could try leaving the stock clockspeed 1.6ghz, set minimum cores to 2 and slightly undervolt to -25mv, leave the gpu setup to its default 533mhz and also undervolt to -25mv using a kernel that supports stweak app. Then run an app called Stability Test for 10minutes to check for errors.
Also I tried Go Power Master, which can be assigned to disable certain features once your battery hits critical low levels.
Sent from my GT-N7100 using xda premium
bushako said:
I think 600mhz is way too low and counter productive or for that matter anything less than 1ghz. The phone will lag alot and you'll have freezes. You'll probably end up using up alot of the battery life trying to get tasks completed. You could try leaving the stock clockspeed 1.6ghz, set minimum cores to 2 and slightly undervolt to -25mv, leave the gpu setup to its default 533mhz and also undervolt to -25mv using a kernel that supports stweak app. Then run an app called Stability Test for 10minutes to check for errors.
Also I tried Go Power Master, which can be assigned to disable certain features once your battery hits critical low levels.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Thats quite informative. Thanx!