T989 turns off at random times..

[NJ_RAMS_FAN]

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..

 

[tmak22]

Mines does the same thing except it only reboot when its on charge, and all my contacts dissapear

 

[2hvy4grvty]

@OP: Try flashing a different ROM.

Juggernaut has pretty aggressive UVing that not all phones might like.

 

[Joy2DaWurld]

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

 

[yoft1]

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..

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

 

[NJ_RAMS_FAN]

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

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.

 

[AaronPauley]

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.

 

[yoft1]

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.

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.

 

[AaronPauley]

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.

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.

 

[AaronPauley]

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.

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.