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

[Q] [SOLVED] Random shutdowns / turning off.

Hey guys,
The topic of this thread has change slightly since I started it. Please disregard the first few posts after this one.
The problem is that when I install a new ROM, it works perfectly for an hour or perhaps even the day, and then I start getting random shutdowns. These seem to start out of the blue and I cant work it out.
When installing a new ROM, I always check the MD5 and perform a superwipe before starting to use the ROM. Ill put back a few apps using titanium backup pro.
I don't use any hacked apps or task killers.
I have searched but cant find anything useful.
Currently using Insertcoin Sense 4 RC5. Firmware 3.32.
I have tried three different kernals (Bricked, Sebastian and RCMix), all with the same problem.
Update: tjamaican has kindly sent me a fix he found of the forums, its for a battery fix that worked for me on insertcoin's ICS Sense 4 RC4.1 ROM. However I have just moved to RC5 and the problem is back even with the fix.
http://www.mediafire.com/?2a8837bcatym1ju
I am going to try and set a lower CPU level, already down to 1.2 Ghz with max screen off at ~500Mhz. Seems stable for now, been running 24hrs - no restarts.
This is interesting because I had a GB Rom running at 1.5Ghz with no problems, maybe its something to do with ICS.
Any ideas?
[SOLVED]
Sent the phone off to htc and they have replaced the motherboard. Its all fine and dandy now!
They dont know why it happened or how to avoid it in the future...useful, but if you're still in warranty then send it off, it took exactly a week to get back to me (Monday to Monday). Good luck!
Max

Well no need for factory reset. Superwipe? Yes.
What roms cause this?
What firmware is ur senny on? Ex: 1.17? 3.24?
Phone have physical damage?
Has it been wet?
Sent From Space Using My ICS Flavored Sensation

Thanks for your reply.
No, the phone is basically new, but as I said this has happened before.
Running this ROM on 3.24:
http://forum.xda-developers.com/showthread.php?t=1468683
But this does happen on other ROMS too, they work perfectly for a while and then slowly begin to develop problems. At this stage I usually install the latest version of the ROM but I'm actually happy with the ROM at the moment and dont want to have to keep changing it!

I've been running Darkforest ROM since early stages and have had no problems so far. Maybe try that one. It's on v 5.1.5 now and it's very fast and very stable, moreso than many other ROMs i've tried.

Could be a defective device possibly? Are u using the kernel that comes with the rom?
Sent From Space Using My ICS Flavored Sensation

I would download 1-click cleaner and clean the cache every week. Also you might want to boot into recovery and wipe cache and dalvik cache every two weeks.
Sent from my HTC Sensation 4G using XDA App

I dont think there is anything wrong with the device, I'll try wiping the cache's and see if that makes a difference. Thank you very much for all your answers so far.
Max

Could possibly be an app try removing all your apps and install 1 by 1 give it a couple of weeks see if it happens again, I got a problem from juice defender pro (payed for) worked alright for few days then my launcher started force closing all the time took me ages to figure it out but got there by removing all my apps and installing them 1 by 1 long and time staking but worth a try
Sent from my HTC Sensation Z710e using xda premium

Okay well ive tried clearing the cache and davlik cache with no luck, less restarts but they are still there. I am resistant to start removing apps as I use them on a daily basis. Before I try this, does anyone have any other ideas?
Thanks,
Max

I have the same problem :/ it happens in both GB and ICS but It never happened to me till about 2 or 3 months ago
Sent from my HTC Sensation Z710e using xda premium

This is still happening, but now its starts to happen more quickly, the new Sense 4 insert coin ROM works fine for the first DAY then I get trouble

darksupernova said:
This is still happening, but now its starts to happen more quickly, the new Sense 4 insert coin ROM works fine for the first DAY then I get trouble
Click to expand...
Click to collapse
Please elaborate more of the problem/concern, so we could atleast help you somehow.
Sent from my HTC Sensation XE with Beats Audio

ardom said:
Please elaborate more of the problem/concern, so we could atleast help you somehow.
Sent from my HTC Sensation XE with Beats Audio
Click to expand...
Click to collapse
What other information would you like?
I think it may be a kernel issue, I'm going to try a few...
Tried three different kernals now, all with the same problem which would indicate its not a kernal problem? Something else perhaps? (Tried bricked, sebastian and RCMix)

its not a problem, its with network connection
I've had this problem since ages and couldn't fix it yet. First thing, download LTE switch and change the value from wcdma preferred to gsm auto. see if it avoids the restarts. Another thing you can try is, change the sim card (I havent tried it yet). Or, if possible, change the back cover. But I'm pretty pretty sure its the problem with the network.
Please reply.

Danyal93 said:
I've had this problem since ages and couldn't fix it yet. First thing, download LTE switch and change the value from wcdma preferred to gsm auto. see if it avoids the restarts. Another thing you can try is, change the sim card (I havent tried it yet). Or, if possible, change the back cover. But I'm pretty pretty sure its the problem with the network.
Please reply.
Click to expand...
Click to collapse
Pretty sure its a power/bat problem for me.
Update: tjamaican has kindly sent me a fix he found of the forums, its for a battery fix that worked for me on insertcoin's ICS Sense 4 RC4.1 ROM. However I have just moved to RC5 and the problem is back even with the fix.
http://www.mediafire.com/?2a8837bcatym1ju
I am going to try and set a lower CPU level, already down to 1.2 Ghz
Any ideas?

Well I have been at the 1.2GHz level for almost 24 hours now without too much trouble. Im not sure if it was lowering the CPU clock for screen on, or raising the CPU clock for screen off. Either way I can notice the device is slightly slower. I dont see why ICS doesnt like overclocking on this phone, GB was fine with it?!
Max
Update:
Just had a random shutdown, could have been anywhere in the last 20 mins. I really don't know what else to try!

Having EXACT ones you are having. Buy another battery if that doesn't work its a hardware problem. I still need to buy my battery but will post and let you know if it worked.
---------- Post added at 04:37 PM ---------- Previous post was at 04:33 PM ----------
darksupernova said:
Well I have been at the 1.2GHz level for almost 24 hours now without too much trouble. Im not sure if it was lowering the CPU clock for screen on, or raising the CPU clock for screen off. Either way I can notice the device is slightly slower. I dont see why ICS doesnt like overclocking on this phone, GB was fine with it?!
Max
Update:
Just had a random shutdown, could have been anywhere in the last 20 mins. I really don't know what else to try!
Click to expand...
Click to collapse
I'm also starting to think its caused by not letting the battery fully die and recharging it a lot but that's just my guess?

I switched back to gingerbread yesterday and so far I've had no problems which would indicate its not a hardware issue...? Usually by now I've had a few shut downs..

So I went as far as unrooting and switching batteries with my bro and the problem continues idk what to do

sickorwuut said:
So I went as far as unrooting and switching batteries with my bro and the problem continues idk what to do
Click to expand...
Click to collapse
Yeah the problems started again for me on gingerbread. I've read its a motherboard problem I think I'm gonna have to send it off to HTC... Great... 3 weeks no phone...

Please help, CM7 SUPER LAGGY fresh install

I was on CM7 then went to AOKP, didnt like it and went back to CM7, now my phone is super laggy.
I have found out it is running at 200mhz almost constantly unless i set my minimum to 800 or 1200, but then my battery would die in minutes.
Nothing seems to fix this. it is SOOO bad that the skateboard cm7 droid dude, lags. the first samsung logo takes like 30 seconds or more, then when it jumps to the skateboard guy it lags and the circle arrow skips frames horribly. not like usual.
The only thing i can think of is when i was on AOKP (ICS) i "v6 super charged it" when i went back could there be remnance of issues?
please help i am pulling my hair out in stress and annoyance.
I have reflashed 5 times, reset with heimdall to stock, then back to CWM recovery RED, (entropy) and back to CM7... no fix. im wondering if a certain file is causing the cpu to underclock.
what file do i delete and reset.
please help

Go back to stock...and then once on stock go to settings>privacy>reset to factory defaults>format USB drive....let it do its thing and you should be good...make sure you back up important data first...this will wipe everything!!!!
Sent from my HTC PH39100 using XDA

is this honestly my only option? seems a bit harsh to wipe everything

Skwerl23 said:
is this honestly my only option? seems a bit harsh to wipe everything
Click to expand...
Click to collapse
Yes...remember you dealing with files...folders...that sometimes leave a trail of stuff....so a good wipe and kill all, reload clears...so being lazy will have it's effect....
My thing if ya gonna do it..do it right, work now, rest/enjoy it later......

all i should have to back up is my titanium, and my pictures i believe.

im not against doing it right, problem is i have reflashed probably 50 times, and this is the first time ive had an issue. its weird.

so when i reset to stock, it boots normal speed. im not so sure its the folders. this is so weird. but im trying this step anyhow

Skwerl23 said:
all i should have to back up is my titanium, and my pictures i believe.
Click to expand...
Click to collapse
Pics should be on your ext sd card...and yes you can back up via tibu your apps only...

usb wiped from stock. no change. am i missing a certain kernel?
fixing permissions helps some what for one boot then back to where it was.
tried going back a month to may 1st of CM7 release. no go.
my wifes infuse is just like mine and works fine. difference is i was on ICS im gonna flash that and see how ICS works.
ive been working on this for around 14 hours, this is insane.
everything i do is no good.
i honestly think supercharger messed it up, but i dont know how. either that or my CPU is some how fried, but it works fine from time to time, and when i set it to 1200 mhz minimum speed
its as if my governor's are jacked up, but it is slow in boot up and recovery as well. which is what really confuses me

just installed ics AOKP Brocolli, and its as smooth as ics has been, i dont like the random crashes and problems i get from ICS so i want to go to CM7
plus this AOKP Broccoli theme is god awful to me.
i think im just to old to look at circuit board designs all day.

[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

VZW S3 constant random rebooting across multiple ROMs/kernels below 50% battery.

I first had the problem with Carbon and Leantastic, then switched to KT, then flashed to Paranoid Android and its kernel, then to AOKP and its kernel. All of these configurations work fine until I dip below 50% battery, when I start to experience constant random reboots no matter what I do. I tried flashing back to stock then flashing back to custom, different kernels, different firmware, wiping caches/factory resets, etc. and nothing has fixed the problem. The only commonality I can think of in each configuration is that the ROM or kernel is CM-based, because the problem is not present in stock. I've turned Google upside-down trying to find a solution, but haven't had luck. Anyone know what the problem could be?

virsago said:
I first had the problem with Carbon and Leantastic, then switched to KT, then flashed to Paranoid Android and its kernel, then to AOKP and its kernel. All of these configurations work fine until I dip below 50% battery, when I start to experience constant random reboots no matter what I do. I tried flashing back to stock then flashing back to custom, different kernels, different firmware, wiping caches/factory resets, etc. and nothing has fixed the problem. The only commonality I can think of in each configuration is that the ROM or kernel is CM-based, because the problem is not present in stock. I've turned Google upside-down trying to find a solution, but haven't had luck. Anyone know what the problem could be?
Click to expand...
Click to collapse
EVERY phone is different. Yours may not like the custom kernels you are trying to put on it.

z06mike said:
EVERY phone is different. Yours may not like the custom kernels you are trying to put on it.
Click to expand...
Click to collapse
I've never had this persistent of a problem until about two weeks ago, but prior to that I've been flashing ROMs/kernels since I got the phone in September. I'm not sure why it's having trouble now all of a sudden.

virsago said:
I've never had this persistent of a problem until about two weeks ago, but prior to that I've been flashing ROMs/kernels since I got the phone in September. I'm not sure why it's having trouble now all of a sudden.
Click to expand...
Click to collapse
Hmm strange. How far did you push the phone with the OC'ing?

z06mike said:
Hmm strange. How far did you push the phone with the OC'ing?
Click to expand...
Click to collapse
Nowhere. I've never OC'ed, but I have tried upping the minimum voltage. That didn't help either.

virsago said:
Nowhere. I've never OC'ed, but I have tried upping the minimum voltage. That didn't help either.
Click to expand...
Click to collapse
Upping the minimum voltage will cause you're battery life to suffer so I hope you meant undervolting.

reboot issues
virsago said:
I first had the problem with Carbon and Leantastic, then switched to KT, then flashed to Paranoid Android and its kernel, then to AOKP and its kernel. All of these configurations work fine until I dip below 50% battery, when I start to experience constant random reboots no matter what I do. I tried flashing back to stock then flashing back to custom, different kernels, different firmware, wiping caches/factory resets, etc. and nothing has fixed the problem. The only commonality I can think of in each configuration is that the ROM or kernel is CM-based, because the problem is not present in stock. I've turned Google upside-down trying to find a solution, but haven't had luck. Anyone know what the problem could be?
Click to expand...
Click to collapse
I had this happen with my Thunderbolt previously, rooted with Infected ROM. But it wasn't anything to do with the ROM. Happened when I got a "new" battery off EBAY. with the new battery, even though I charged it at one time for about 36 hours it continued to reboot randomly. Changed back to the old battery and it never did it again. Never really persued resolving it cause I just picked up the S3.