Database Info

[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

Shutting Down

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.

Phone continues to randomly reboot even with new radios

I have tried 4 different radios and this phone still randomly reboots with frequency. I am the the 802 radio and it seems even worse then earlier radios. I am currently on gingerritis rom which i installed yesterday and have probably had 12 reboots since then.
Is it a combination of the rom and radio, or does just the radio make the phone reboot? I am really just tempted to flash it back to stock, sell it with the warning of this phone enjoys random reboots and get another phone.
while i typed this up it just rebooted twice on its own

I dont think the radio is what is going to fix the reboot issue. I know for some of the roms the fix was flashing the ziggy kernel.
Maybe give that a shot.

brownsfan said:
I dont think the radio is what is going to fix the reboot issue. I know for some of the roms the fix was flashing the ziggy kernel.
Maybe give that a shot.
Click to expand...
Click to collapse
If hes using gingeritis, hes already using ziggy's kernel. Sounds weird i know, but try a new battery
Sent from my TBolt using my f***king thumbs...

i think overclocking to high and all the kernel cpu mods are whats causing this, not the radios.

fixxxer2008 said:
i think overclocking to high and all the kernel cpu mods are whats causing this, not the radios.
Click to expand...
Click to collapse
I agree. Ziggy's stock voltage settings are very conservative north of about 1.5GHz. If you're tweaking it, definitely pay attention to the voltage.

nope not touching voltage or overclocking, i just put rom on thats about as far as i go tweaking phone.
Installed M0N0LITHTH3ORY rom and so far no reboots today, the gingeritis one must hate my phone cause in the less than 24 hours it was on the phone damn thing rebooted easy 10 times. But now this one is giving me some unexpected errors with weather app. I will give this one a week and see how it does and if no good on to next rom i guess.

-magnum- said:
nope not touching voltage or overclocking, i just put rom on thats about as far as i go tweaking phone.
Installed M0N0LITHTH3ORY rom and so far no reboots today, the gingeritis one must hate my phone cause in the less than 24 hours it was on the phone damn thing rebooted easy 10 times. But now this one is giving me some unexpected errors with weather app. I will give this one a week and see how it does and if no good on to next rom i guess.
Click to expand...
Click to collapse
Have you ever formatted /system?

yeah every time i put new rom i go into clockwork recovery
i wipe / factory reset
then format /system /cache /data
and wipe davlik cache
then install rom

double post...

i know my phone didnt like a few different roms. try a diffeerent one. also try doing each step 3 times. i did that after my phone rebooted on an a0sp rom by droidtheroy, after that it worked just fine on the rom that was rebooting

You know what? I was having the same problem and tired as hell of my TB. I was so tired of the little problems and the large rebooting problem that I had learned to really hate this phone.
A few days ago I decided to just use the new leaked, stock, unrooted, GB 210 RUU and give that one more try before I either took a hammer to this phone or unrooted and tried to get VZW to replace it.
I've had the latest leaked RUU on this phone for a few days now and I'm loving it again. Yeah, stock, unrooted, but also super fast GPS locking, fast 3g/LTE switching, no more reboots, not one. Battery is actually not bad at all after turning off a few of the stock bloat like Blockbuster. The gui is fast and smooth, I can't say whether or not it is as fast as it was when I was running custom ROMs but as far as I'm concerned its a big who cares. I now have a nicely working phone again. This is just my experience and my opinion, YMMV!
R

-magnum- said:
I am currently on gingerritis rom which i installed yesterday and have probably had 12 reboots since then.
Click to expand...
Click to collapse
I got reboots with gingeritis and liquid ROMs, I've had no reboots in a week now running Virus' Synergy ROM. Try a different ROM, it should fix your problems.
Here's a link to Virus' work:
http://forum.xda-developers.com/showthread.php?t=1003891

Second the ROM recommendation. Try a different one. I had the same issue with wanting to grenade this thing until I found a combo of ROM and radio that was stable for my use and applications.
Now I wouldn't think of tossing this phone.
Sent from my ADR6400L using Tapatalk

Stability and battery life good for me with stock 1.70.605.0. Currently at 868 hours uptime.

yeah i am on monolith rom and so far no reboots, i am going to give this one a shot for now, hopefully this cures it.

[Q] Help

I'm having some issues with my S 4g. After leaving my phone alone, such as charging it over night. I'll wake up with it booted in to recovery, or as soon as I go to use it I'll get a lot of force closures. I've tried different ROMS I've tried wipping every thing that can be wiped and doing clean installs and it still happens.
At first I thought it was from my alarm app, so I stopped using it. That didn't help. Thought it might be deep idle, so I stopped using that, still happens. Does anyone have an idea what could be causing this? It's making my phone quite un-usable. I'm current on CM9 nightlies, this first started when I went to the CM9 RC1.

You need to provide more info.
Kernel, clock speeds, voltages etc.

If all else fails, you can always use ODIN to flash factory images of ICS and root from there.

063_XOBX said:
You need to provide more info.
Kernel, clock speeds, voltages etc.
Click to expand...
Click to collapse
I'm still using the kernel that came with CM9. I hadn't flashed a new one on to it. So those would be the stock clock speeds and voltages.
It's really weird, as long as I'm using my phone it's fine, but if I leave it alone for a while it misbehaves.... kinda like my kid.

Delete..........

I tried going back to completely stock, re-rooted my phone and doing a fresh install of cm9. Didn't help anything. Switched to a different Rom and no issues so far
Sent from my Nexus S 4G using Tapatalk 2

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