Shutting Down - Thunderbolt General

Anyone having issues with their Thunderbolt shutting off and the only way to turn it back on is to do a battery pull? I'm rooted running Ginger3DTh3ory 6.2, but it did this also when I was running Bamf 3.0. Any thoughts on how to fix this?

No idea, are you oc'd?
Sent from my TBolt using my f***king thumbs...

Let me describe what mine has done a few times and you tell me if that's what you're talking about. Twice, in the last 2 days, it's just locked up with the screen off. It doesn't respond to power or volume buttons. Only way to get it to work again it to pull that battery.
BUT... the weirdest thing happened the last time. It did it while I was in a call. I could answer with my bluetooth, talk, and hang up with my bluetooth, but the phone wouldn't respond to anything I did to it.
Is this what you're talking about?

Sound like SOD = Sleep of Death. It doesn't happen to much but a pain in the rear...switch Ur govenor from interativex to ondamandx see if that fixes it
Sent from my ADR6400L using XDA App

I've had this problem quite a bit lately with the same roms. I switched to Gingeritis3D beta 6 and the problem seems to have gone away. Gingeritis and some other roms are starting to claim they are using an official build of GB and not the alpha leak version. That could be the issue.

adoublearonn said:
I've had this problem quite a bit lately with the same roms. I switched to Gingeritis3D beta 6 and the problem seems to have gone away. Gingeritis and some other roms are starting to claim they are using an official build of GB and not the alpha leak version. That could be the issue.
Click to expand...
Click to collapse
the official build's kernel is a piece of crap that is leading to a whole new batch of reboots.
OP, that is usually an issue where your phone is not getting enough voltage. I would do what the other poster suggested and switch your governor. It will give the phone a little more juice so it doesn't do that.
All phones are different when it comes to that stuff.

Thanks forvthe responses. I'm not OC'd and I'm not sure where in this rom I can change my governor. Its only happened once with those rom so far, hoping its just a fluke.

Mines running fine. Maybe try reflashing?

jeck77 said:
Thanks forvthe responses. I'm not OC'd and I'm not sure where in this rom I can change my governor. Its only happened once with those rom so far, hoping its just a fluke.
Click to expand...
Click to collapse
you have to open terminal emulator (I think its preinstalled on gingertheory, if not there is a free one in the market).
type su (hit enter), it might drop your keyboard, pressing menu will let you reopen it.
type speedtweak.sh
This will open script fusion, there you can change the governor to ondemandx.

Related

[Q] Frequent launcher freezes

I've been having a really annoying problem for a little over a week now and I'm out of guesses...
After running for a while my launcher (either ADW or LP) will lock up and make the phone unresponsive until I pull the battery let it come back up...It'll typically happen once or twice a day, and has happened with the stock .5 RUU rooted (using SenseUI, no LP or ADW), CM6 stable, NFXHero, Fresh, etc, so I'm leaning away from it being a ROM problem, but when it happens I can't unlock the phone from sleep. I booted the phone around 12:30am CST this morning and it just happened at 8:30am CST. When I slide to unlock it freezes, and I can hit end, try to wake it back up, and repeat the process and it continues to be unresponsive until the launcher FC's...the only thing I could figure to start with was ask in the IRC and Decad3nce recommended turning JIT off because over time it would bog down the phone, so I decided I would just flash CM6 and GAPPS and no tweaks, etc since no one else had a similar issue and still having the issue. I also limited what apps I installed to rule out something eating up CPU in the background (didn't install anything that stays running) I've ruled out CM6 being the problem seeing as it happens with any ROM I use and the only thing I can think of being the issue would be memory leak, and the only way I've come to that conclusion is since this is flash memory, I know it has a lifespan of reads/writes, and I'm wondering if I've just wiped and flashed too many different ROMs, etc...Also, I'm not using ANY homescreen widgets or themes, only a custom background. I don't have Autokiller installed or the battery tweak or ATK...just bare ROM.
Has anyone else had this issue? Is there any way I can troubleshoot it or do I just need to RUU the phone and take it to Sprint and try to get a replacement? I'm not due for an upgrade until Feb. so I can't just go swap out, plus I really like this phone and would like to keep it as long as possible...
Matt262 said:
I've been having a really annoying problem for a little over a week now and I'm out of guesses...
After running for a while my launcher (either ADW or LP) will lock up and make the phone unresponsive until I pull the battery let it come back up...It'll typically happen once or twice a day, and has happened with the stock .5 RUU rooted (using SenseUI, no LP or ADW), CM6 stable, NFXHero, Fresh, etc, so I'm leaning away from it being a ROM problem, but when it happens I can't unlock the phone from sleep. I booted the phone around 12:30am CST this morning and it just happened at 8:30am CST. When I slide to unlock it freezes, and I can hit end, try to wake it back up, and repeat the process and it continues to be unresponsive until the launcher FC's...the only thing I could figure to start with was ask in the IRC and Decad3nce recommended turning JIT off because over time it would bog down the phone, so I decided I would just flash CM6 and GAPPS and no tweaks, etc since no one else had a similar issue and still having the issue. I also limited what apps I installed to rule out something eating up CPU in the background (didn't install anything that stays running) I've ruled out CM6 being the problem seeing as it happens with any ROM I use and the only thing I can think of being the issue would be memory leak, and the only way I've come to that conclusion is since this is flash memory, I know it has a lifespan of reads/writes, and I'm wondering if I've just wiped and flashed too many different ROMs, etc...Also, I'm not using ANY homescreen widgets or themes, only a custom background. I don't have Autokiller installed or the battery tweak or ATK...just bare ROM.
Has anyone else had this issue? Is there any way I can troubleshoot it or do I just need to RUU the phone and take it to Sprint and try to get a replacement? I'm not due for an upgrade until Feb. so I can't just go swap out, plus I really like this phone and would like to keep it as long as possible...
Click to expand...
Click to collapse
+1-I am having the exact same issues with same setup although I do have AutoKiller and it is set to Optimum.
If you havent already try the Brainfunct kernal from this forum. I used to have random lockups and such before I used that..
Jason kiDD said:
If you havent already try the Brainfunct kernal from this forum. I used to have random lockups and such before I used that..
Click to expand...
Click to collapse
Sorry, I should've mentioned that I DID try the BFS kernel (9/28 build) and it was after flashing kernels that I noticed it (mostly coincidence I'm sure) which is why I flashed straight CM6 to rule out the kernel
Funny as you mentioned it my phone rebooted once and then was non-responsive a second time after being untouched.. You must remember that these are RC1 roms and not final so there will be issues with each iteration.. Its the drawback of pushing our phones to the limit..
Jason kiDD said:
Funny as you mentioned it my phone rebooted once and then was non-responsive a second time after being untouched.. You must remember that these are RC1 roms and not final so there will be issues with each iteration.. Its the drawback of pushing our phones to the limit..
Click to expand...
Click to collapse
It happened with the stock .5 RUU ROM with the only modification being AndROOT...I RUU'd it back to .5 this morning and am going to ride it out untarnished to see if the problem replicates again. If so, I believe I will have successfully found it's a problem with the phone itself, and at that point take it to Sprint and see about paying the $35 for an exchange. I would do the OTA updates but if this shows its fixed I don't want to lose the ability to root, and I don't want to have to RUU back to .5 in order TO root. I was really hoping a dev who understands these ROM's better than I could chime in with some thoughts, but I guess I'll just have to keep test and tuning...I definitely appreciate these responses, though, and I'm happy I'm not the only one having this issue (though I'm still not happy it's happening lol)
not trying to be mean but your better off actually posting this in the right section and you might get some better answers. Q&A section is there for a reason.
t12icky0 said:
not trying to be mean but your better off actually posting this in the right section and you might get some better answers. Q&A section is there for a reason.
Click to expand...
Click to collapse
Thanks...I figured sticking it in the Dev section would be more fitting since my first inclination was strictly a software problem, and not too sure how often dev's surf the other threads.
Matt262 said:
Thanks...I figured sticking it in the Dev section would be more fitting since my first inclination was strictly a software problem, and not too sure how often dev's surf the other threads.
Click to expand...
Click to collapse
oh...devs go in there quite a bit. If not them then plenty of people who know the answers are in there.
I have the same issue I've used stock roms cm6 roms and tons of different kernels. I've noticed it moreso when its been asleep for a while it will wake up fine and then a couple minute later it will freeze up and force me to do a battery pull.
t12icky0 said:
oh...devs go in there quite a bit. If not them then plenty of people who know the answers are in there.
Click to expand...
Click to collapse
Gotcha...if you check out my post count I'm a n00b to these boards, but I appreciate you not blasting me like I've seen others have that happen to them (for not searching ,etc)...maybe a mod could move this for me so I don't clutter the boards?
Dono74 said:
I have the same issue I've used stock roms cm6 roms and tons of different kernels. I've noticed it moreso when its been asleep for a while it will wake up fine and then a couple minute later it will freeze up and force me to do a battery pull.
Click to expand...
Click to collapse
Exactly! Now if a resolution can be found...since I posted this in the wrong section, maybe there is a resolution and I just wasn't in the right spot to see it...
Matt262 said:
I've been having a really annoying problem for a little over a week now and I'm out of guesses...
After running for a while my launcher (either ADW or LP) will lock up and make the phone unresponsive until I pull the battery let it come back up...It'll typically happen once or twice a day, and has happened with the stock .5 RUU rooted (using SenseUI, no LP or ADW), CM6 stable, NFXHero, Fresh, etc, so I'm leaning away from it being a ROM problem, but when it happens I can't unlock the phone from sleep. I booted the phone around 12:30am CST this morning and it just happened at 8:30am CST. When I slide to unlock it freezes, and I can hit end, try to wake it back up, and repeat the process and it continues to be unresponsive until the launcher FC's...the only thing I could figure to start with was ask in the IRC and Decad3nce recommended turning JIT off because over time it would bog down the phone, so I decided I would just flash CM6 and GAPPS and no tweaks, etc since no one else had a similar issue and still having the issue. I also limited what apps I installed to rule out something eating up CPU in the background (didn't install anything that stays running) I've ruled out CM6 being the problem seeing as it happens with any ROM I use and the only thing I can think of being the issue would be memory leak, and the only way I've come to that conclusion is since this is flash memory, I know it has a lifespan of reads/writes, and I'm wondering if I've just wiped and flashed too many different ROMs, etc...Also, I'm not using ANY homescreen widgets or themes, only a custom background. I don't have Autokiller installed or the battery tweak or ATK...just bare ROM.
Has anyone else had this issue? Is there any way I can troubleshoot it or do I just need to RUU the phone and take it to Sprint and try to get a replacement? I'm not due for an upgrade until Feb. so I can't just go swap out, plus I really like this phone and would like to keep it as long as possible...
Click to expand...
Click to collapse
Sounds like a garbage collection fail when coming from sleep, try using ondemand cpu governor for the time being.
Otherwise.. don't set your max freq too high, that's usually where lockups stem from.
Decad3nce said:
Sounds like a garbage collection fail when coming from sleep, try using ondemand cpu governor for the time being.
Otherwise.. don't set your max freq too high, that's usually where lockups stem from.
Click to expand...
Click to collapse
Actually when I flashed CM6 last night with no tweaks I didn't even install SetCPU or any kernels...just the one that came with it capped at 691.2...no battery tweak or anything
I think there is a problem in the latest iteration of CM6 but again its not a promised fully stable build.. All I did since then was to flash the battery tweak over stock CM6 and poof problems were gone.. With the 9/22/10 it was the opposite and i had to flash the Brainfunct kernal instead of the battery tweak one..
Jason kiDD said:
I think there is a problem in the latest iteration of CM6 but again its not a promised fully stable build.. All I did since then was to flash the battery tweak over stock CM6 and poof problems were gone.. With the 9/22/10 it was the opposite and i had to flash the Brainfunct kernal instead of the battery tweak one..
Click to expand...
Click to collapse
Still a mystery to me as to why it's happening with more ROM's than just CM6 though...oh well, I'll see how stock .5 unrooted treats me this weekend, and if I have the same problem happen again, I know it's phone related and not to be blamed on a ROM (which I'd like to make clear -- I do NOT blame CM6, Fresh, or NFXHero for my issues. I know the dev's spent a TON of time building everything for us to have something we would otherwise NOT have, and my sole reason for this post is really to find out exactly what is wrong with my phone, not necessarily with a ROM, and most importantly to find out if I'm the only one experiencing these issues)...I do appreciate all the help and responses, and I'm thoroughly impressed with XDA and the responsiveness of everyone
Just in case anyone was interested at all, my phone completely bricked today (stock .5 running all weekend no issues) and the culprit is the touchscreen and all buttons but power stopped working...sprint's overnighting me a replacement so evidently something got too hot at some point or the like...thanks to all for the responses, and to those who had similar issues (not related to the ROM you're running) then keep an eye out for imminent failure lol

ATTENTION: Potential fix for sleep death

Ive had sleep death since day 2 of ownership....three days ago i flashed existz jvp voodoo gb kernel and have NOT had sleep death. I need people to see if this is a fix or just luck. If your on gingerbread, (NOT miui or cm7) try this kernel and see if it fixes it. I *think* its compatible with all jvo and jvp. Im on jvo and it works
Sent from my 2.3.3 Ext4 Fresh Ginger Blue equipped Samsung Captivate.
Appreciate the heads up fyi for us all. I'm running DG's latest right now but will keep this in mind.
I dont think it would work on newest cog due to different kernel source. This is I9000 based and cog is captivate based.
Sent from my 2.3.3 Ext4 Fresh Ginger Blue equipped Samsung Captivate.
Yeah, I just meant I'll keep it in mind for when I flash to a Rom that could use that Kernel. Again, thanks for the fyi.
topiratiko said:
Ive had sleep death since day 2 of ownership....three days ago i flashed existz jvp voodoo gb kernel and have NOT had sleep death. I need people to see if this is a fix or just luck. If your on gingerbread, (NOT miui or cm7) try this kernel and see if it fixes it. I *think* its compatible with all jvo and jvp. Im on jvo and it works
Sent from my 2.3.3 Ext4 Fresh Ginger Blue equipped Samsung Captivate.
Click to expand...
Click to collapse
I personally tried every kernel/rom combo out there and finally just had to replace my phone. I really hope you found a solution for your phone, but when I'd find a good combination for my phone it would usually start shutting down again eventually. Not trying to shoot you down, just letting you know my experience with the issue.
The only thing that actually put a band-aid on my issue was the app "Captivate Keep Alive". I say "band-aid" because although the phone was no longer shutting off on it's own, the battery would drain real fast, so it wasn't really the ideal solution. If you're still under warranty, I recommend just getting it replaced.
Thread with same issue: http://forum.xda-developers.com/showthread.php?t=731560
id10terror said:
I personally tried every kernel/rom combo out there and finally just had to replace my phone. I really hope you found a solution for your phone, but when I'd find a good combination for my phone it would usually start shutting down again eventually. Not trying to shoot you down, just letting you know my experience with the issue.
The only thing that actually put a band-aid on my issue was the app "Captivate Keep Alive". I say "band-aid" because although the phone was no longer shutting off on it's own, the battery would drain real fast, so it wasn't really the ideal solution. If you're still under warranty, I recommend just getting it replaced.
Thread with same issue: http://forum.xda-developers.com/showthread.php?t=731560
Click to expand...
Click to collapse
I know the feelin...i was using softlocker...same as keep alive but without the atrocious status bar icon....if it shuts down on this kernel ill do the warranty....its been 4 dayz with no shutdowns and 8 + hours of phone idle nightly....lookin good so far
Sent from my 2.3.3 Ext4 Fresh Ginger Blue equipped Samsung Captivate. Yea I get 2000+ on quadrant. Yea ive pulled 5.17 mbps down from a tower. I appreciate XDA helping me turn this phone into a beast.
One day without random shutdown, may be it really works.
I've tried many Roms and kernels with no luck, thanks
pexo74 said:
One day without random shutdown, may be it really works.
I've tried many Roms and kernels with no luck, thanks
Click to expand...
Click to collapse
Glad its working. Keep me posted...day 5 no shutdown
Sent from my 2.3.3 Ext4 Fresh Ginger Blue equipped Samsung Captivate.
The reason you may not be having any sleep death is if the governor is set not to go into Deep Sleep. The Talon kernel supports OC/UV and that may be the culprit. However, my experience with voltage regulation kernels has not been nearly as stable as with ones that don't. I had to just replace my phone when I had the sleep death issues...good luck though.
Is sleep death a reboot. Ive been on oc/uv talon kernal and it gets reboots pretty often it drives me nuts. Always happens when i listen to music too
Sent from my GT-I9000 using XDA App
trekie86 said:
The reason you may not be having any sleep death is if the governor is set not to go into Deep Sleep. The Talon kernel supports OC/UV and that may be the culprit. However, my experience with voltage regulation kernels has not been nearly as stable as with ones that don't. I had to just replace my phone when I had the sleep death issues...good luck though.
Click to expand...
Click to collapse
I'm sure that is going to Deep Sleep, I've Cpu Spy installed in my phone.
pexo74 said:
I'm sure that is going to Deep Sleep, I've Cpu Spy installed in my phone.
Click to expand...
Click to collapse
Same here
Sent from my 2.3.3 Ext4 Fresh Ginger Blue equipped Samsung Captivate.
Anyone have anymore feedback?
Sent from my 2.3.3 Ext4 Fresh Ginger Blue equipped Samsung Captivate.
Day 7 NO sleep death
Sent from my 2.3.3 Ext4 Fresh Ginger Blue equipped Samsung Captivate.
1 week without shutdown. O'be tried the new release of talon, and works too.

[Q] Fix for G2X sleep of death?

The main problem with my G2X is the sleep of death, which happens a lot. I get occasional reboots too, but not too often. I tried flashing EaglesBlood 1.05 and then CM7 nightly (7/6), which I'm on now, and I still get sleeps of death and reboots, with perhaps reduced frequency but still bad. Maybe it's the battery, though I don't have overheating/charging/battery drain issues, so I'm not sure what the problem is and if it's hardware or software. Any advice on what I should do would be appreciated - thanks!
I enabled "stay awake" and flashed faux's oc kernel and haven't had an sod in weeks on the stock rom.
regP said:
I enabled "stay awake" and flashed faux's oc kernel and haven't had an sod in weeks on the stock rom.
Click to expand...
Click to collapse
Wouldn't that drain your battery much faster?
Also, I only seem to get the SOD when the phone is charging overnight, and I have a damn screen off profile set to underclock too, not even the lowest frequencies either so it cant be the freeze that that causes sometimes. Tho when it does and I figure out it is frozen asleep, it is usually hot. Might have to either get new battery or replacement. Tho what seems to heat up the most is the area around the camera, so I don't know if the battery or CPU are to blame.
No. Stay Awake only takes effect when your phone is plugged into a power source. Give it a try. I used to get 1 SOD per day. Since i made those changes I've had none in over a month. I posted the same thing in other SOD related threads but no one seems to care.
Thanks regP - I enabled Stay Awake and it seems to help. I've only had one SoD since. My new theory is that it relates to heat (leaving phone in the sun, running too many apps etc.). I've also noticed I don't get an SoD at work, where I get no reception and it's air-conditioned...might be related.
You also need to flash Faux's OC kernel. Even if you dont OC it gets rid of the faulty 300hz frequency that is believed to be part of the problem. Do that along with stay awake and you should not see any more SOD or reboots.
I've noticed I only ever got SOD when using any different kernel than what's in the original ROM. I have been on CM7 since RC1 and have been updating each nightly since and not touched the kernel and have not had a single SOD since, even when charging overnight. Only when I would try Faux kernel or Trinity kernel I would get SOD's.
I dunno then. completely stock for mean means sod and reboots. gingerbreak leak means sod and reboots. stocks + days kernel and stay awake means no sod or reboots. buddy of mine also cured his problems the same way.
For me stock froyo and gingerbread solves the problem.Initially when there was a call waiting sods used to occur, not in any other situation.I tired latest cm7 nightly with fauxs kernel,MIUI with fauxs kernel (and yes wiped cache , wiped dalvik cache and fix permissions and stay awake) but still sods.Then the stock froyo / gingerbread solves the problem for me.Hope this helps somebody.But my point is can I install the stock kernel with cm7 or MIUI ?.
viraj071 said:
For me stock froyo and gingerbread solves the problem.Initially when there was a call waiting sods used to occur, not in any other situation.I tired latest cm7 nightly with fauxs kernel,MIUI with fauxs kernel (and yes wiped cache , wiped dalvik cache and fix permissions and stay awake) but still sods.Then the stock froyo / gingerbread solves the problem for me.Hope this helps somebody.But my point is can I install the stock kernel with cm7 or MIUI ?.
Click to expand...
Click to collapse
no, miui and cm7 are both built from AOSP code and thus won't work with the stock kernel.
I guess I got lucky... never encounter the SOD or Reboot. Running cm nightly 163... I only update nightly when I notice major change only from change log.
Sent from my LG-P999 using XDA App
regP said:
no, miui and cm7 are both built from AOSP code and thus won't work with the stock kernel.
Click to expand...
Click to collapse
So can you suggest any other kernel I should try to stop the sleep of death ?
I have two G2x - Stock Froyo and kernel, manually restart once per day - no SOD or async reboots. Both G2x did suffer from SOD (with or without heat) and reboots. Manual restarts are not as sexy as 3rd party kernels and roms, but it works.
My wife uses her G2x as an alarm clock - she gets in beds, manually shutsdown the G2x, restarts it, plugs into the charger, and it wakes her up in the morning. EVERY DAY.
viraj071 said:
So can you suggest any other kernel I should try to stop the sleep of death ?
Click to expand...
Click to collapse
my sod issues stopped when I enables "stay awake". never used anything but the included kernel of whatever Tom I decide to use.
What is the best solution for this? Makes me think i wasted good money on getting 2, for me and my girl. I tried that "stay awake" and same, shuts off out of nowhere. Ive flashed both faux kernel, same results. I dont experience it with CM but for me, stock its just more responsive BESIDES the shutoff. And Weapons rom just has too much addons.. Now people are saying that the SGS2 isnt all that because of benchscores.. And i wanted that phone.. But they make it seem like it isbt a big step forward.
Sent from my LG-P999 using Tapatalk
noodles2224 said:
What is the best solution for this? Makes me think i wasted good money on getting 2, for me and my girl. I tried that "stay awake" and same, shuts off out of nowhere. Ive flashed both faux kernel, same results. I dont experience it with CM but for me, stock its just more responsive BESIDES the shutoff. And Weapons rom just has too much addons.. Now people are saying that the SGS2 isnt all that because of benchscores.. And i wanted that phone.. But they make it seem like it isbt a big step forward.
Sent from my LG-P999 using Tapatalk
Click to expand...
Click to collapse
Our phone at 1 ghz has surpassed the gs2 and 1.2 ghz
Sent from my LG-P999 using XDA App
If missing with software and settings dont work you may just have a bad phone.
regP said:
I enabled "stay awake" and flashed faux's oc kernel and haven't had an sod in weeks on the stock rom.
Click to expand...
Click to collapse
Thanks for this. I'll be sure to use the "Thanks" button when i have enough posts. I'd been leaving the phone screen on in my pocket (using an alarm clock app) because it would SOD anytime i used the lock button. Working better already.
I keep on getting SODs ONLY when there is a call waiting in the background and this happens only with CM7,MIUI.When I flash the stock gingerbread or even weapons G2x,EaglesBlood ROM the sods that occur during call waiting vanish. Can anyone help me here ? I tried fauxs kernel along with Stay awake and increasing the minimum CPU frequency but failed. Any help will be appreciated.
For the people that SOD occurs on the charger, try another charger (instead of stock LG charger). I tried the Motorola micro USB charger which put out only 550mA (which came with the H730 bluetooth) and the SOD vanished.
Probably over heating with the LG charger which puts out 1000mA

Two questions...

1). I'm running TC CM10 a3 w/ InstigatorX 6.3.4. What program do I need to under volt my CPU? I love having it oc'd but it destroys my battery using anything above 1628Mhz.
2). Using the xda app on my phone, every time I hit the 'back' button to return to a forum, the app closes and I have to reopen it. It doesn't fc, it just closes like normal. Just an annoyance.
Thanks for any help!
Dispatched from ye ol' Skyrocket running TeamChopsticks CM10 a2 4.1.1 JB w/ InstigatorX 6.1 kernel
clip1003 said:
1). I'm running TC CM10 a3 w/ InstigatorX 6.3.4. What program do I need to under volt my CPU? I love having it oc'd but it destroys my battery using anything above 1628Mhz.
2). Using the xda app on my phone, every time I hit the 'back' button to return to a forum, the app closes and I have to reopen it. It doesn't fc, it just closes like normal. Just an annoyance.
Click to expand...
Click to collapse
Question 1 I can help with. First off, before you UV (if you've never done so before), Google "undervolting android" and read at least one or two of the guides that come up. They'll tell you exactly what to do and how to safely do it, and many will even suggest an app for doing so. Personally, I prefer System Tuner to any of the others that come up.
A word of warning with undervolting: if you go too low, you can create all kinds of problems with your ROM, severely drain your battery and potentially even cause permanent damage to your phone. If you've never done it before and don't have a complete understanding of what you're doing, read up first and save yourself trouble later.
Question 2, unfortunately, I can't do much with. Almost seems like your back button might be registering multiple taps. Try it with another app and see what happens. If it's not an issue there but it persists with XDA, well, the great thing about apps is that you can always reinstall them.
Thanks for the assist bro. I've read up on uv'ing. Seen some graphs but each phone is a little different and don't wanna FUBAR it. I've reinstalled the app 3 times and its the only one to do it. Oh well. Thanks again!
Dispatched from ye ol' Skyrocket running TC CM10 a3 4.1.1 JB w/ InstigatorX 6.3.4
System Tuner. FYI it tends to cause some instability on current Jellybean ROMs. I'd recommend UV to -25mv or -37.5mv or maybe -50mv (at each frequency), save the voltage table, and only use the UV setting when you really want the additional battery life.

Whats Your Trigger

Alright Guys i needs some help ive been trying for days to trigger where the heat issue is coming from. Now im not a Vet but im not no noob. ive searched countless threads from android Donut to Jelly bean. so far i havent found the full triggers yet but i have found that if your ram is running around 50mb left over and extensive downloading example long period download like a ROM the heat starts to spike any where from 78 to 111.2!!!
so my question is does anyone else experience this as well im currently runnign slim bean/hotcakez NO oc runnning 384-918 ive tried every rom/kernel and i still experience the same issue and depending on the heat my phone SMELLS LIKE BURNT Bacon lol help please
crashpsycho said:
Alright Guys i needs some help ive been trying for days to trigger where the heat issue is coming from. Now im not a Vet but im not no noob. ive searched countless threads from android Donut to Jelly bean. so far i havent found the full triggers yet but i have found that if your ram is running around 50mb left over and extensive downloading example long period download like a ROM the heat starts to spike any where from 78 to 111.2!!!
so my question is does anyone else experience this as well im currently runnign slim bean/hotcakez NO oc runnning 384-918 ive tried every rom/kernel and i still experience the same issue and depending on the heat my phone SMELLS LIKE BURNT Bacon lol help please
Click to expand...
Click to collapse
Have you tried going back to stock with Odin?
Not sure if your issue is the same as mine, but after I went back to stock it seems to have corrected the issue. It still seems to warm up a little when I'm using it a lot (playing a game, looking at the LOL Droid app, but not, oddly, playing a video) but the battery issue seems to have been solved.
I know that using the phone is going to make the processor run faster, and that faster processor speeds can definitely contribute to heat build up. Do you have a case? If so, take it off. If not, maybe give the phone a break every now and then? I don't know.
liquidzoo said:
Have you tried going back to stock with Odin?
Not sure if your issue is the same as mine, but after I went back to stock it seems to have corrected the issue. It still seems to warm up a little when I'm using it a lot (playing a game, looking at the LOL Droid app, but not, oddly, playing a video) but the battery issue seems to have been solved.
I know that using the phone is going to make the processor run faster, and that faster processor speeds can definitely contribute to heat build up. Do you have a case? If so, take it off. If not, maybe give the phone a break every now and then? I don't know.
Click to expand...
Click to collapse
Yes sir reverted several times to stock and back to another even happens on ICS personally I think its my phone but wanted to know if anyone had similar issues. Thanks for the feedback
Sent from my SAMSUNG-SGH-I727 using xda premium
I had a over heating issue a while back... Turned out to be a run away wake lock. Media scanner. I had to Odin back to stock and rebuild back to the custom rom to totally get rid of it.
Sent from my SAMSUNG-SGH-I727 using xda premium
crashpsycho said:
Yes sir reverted several times to stock and back to another even happens on ICS personally I think its my phone but wanted to know if anyone had similar issues. Thanks for the feedback
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
You never know...it could be the weather around here
I would install Better Battery Stats (if you don't already have it installed) and monitor it for wakelocks to see if something is preventing the phone from deep sleeping.
liquidzoo said:
You never know...it could be the weather around here
I would install Better Battery Stats (if you don't already have it installed) and monitor it for wakelocks to see if something is preventing the phone from deep sleeping.
Click to expand...
Click to collapse
Agreed az is known for pure heat not humidity thank god lol but I will check my wake locks again again and try to find what's cause media scanner only runns once at boot otherwise doesn't need to run. But I think I might switch back to stock and see if it does it on rot stock
thanks guys
Sent from my SAMSUNG-SGH-I727 using xda premium

Categories

Resources