Related
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
So my first Inspire apparently had a GPS radio issue, it would never lock on, Navigation wouldn't work, etc. I was running Revolution 3.1 Sense ROM and Set CPU OC to 1.2ghz. Phone worked great apart from the GPS issue.
I exchanged the first phone yesterday for one with GPS that works great and proceeded to set it up exactly like the first phone, Revolution 3.1 Sense, Set CPU OC to 1.2. But the moment I started Set CPU and it acquired SU permission the phone locked up. And I mean completely locked up, even the live wallpaper stopped moving. I had to do a battery pull and a factory reset just to get the phone to boot again.
I tried everything to get it to work, reflashed the Buzz kernel, reflashed the ROM, flashed a different ROM and then flashed back, restored the ROM from my previous phone. No luck, Set CPU locks up the new phone.
The phone still works great, but it concerns me that Set CPU worked before just fine and doesn't work now. Anyone else have this issue and find a fix? Is it possible HTC made a hardware revision after the first production run that is now causing compatibility issues with OC kernels?
Actually just ran into this today. I have two inspires and the first one I got does fine with oc and setcpu but the one I just picked up causes instafreeze when trying to oc. I was going return it and grab another to see if it was just my particular phone but am curious now that I have seen your post.
Sorry to hear that, but so glad I'm not the only one! If you exchange the one that freezes please let me know the result!
Damn that sucks to hear, I had an inspire on launch day, returned it just cause I wasn't too happy with it and got the atrix. The bootloader issue makes that phone useless to me so I returned it and picked up another inspire off contract, and this one performs WAAAAY better than the first one did stock. Even Linpack confirms. My first ones top score when stock never topped 38 or so, deff. never hit 40 stock. This one consistently hits 41+, and I was just thinking there may have been a software update since then that slightly improve CPU performance but didn't look into it at all. Hopefully this isn't a new batch that HTC did something stupid to, but ill find out tonight.
di11igaf said:
Damn that sucks to hear, I had an inspire on launch day, returned it just cause I wasn't too happy with it and got the atrix. The bootloader issue makes that phone useless to me so I returned it and picked up another inspire off contract, and this one performs WAAAAY better than the first one did stock. Even unpack confirms. My first ones top score when stock never topped 38 or so, deff. never hit 40 stock. This one consistently hits 41+, and I was just thinking there may have been a software update since then that slightly improve CPU performance but didn't look into it at all. Hopefully this isn't a new batch that HTC did something stupid to, but ill find out tonight.
Click to expand...
Click to collapse
I kinda think this too. My first one was a launch unit, I bought it a day or two after they hit shelves. This new one is getting Quadrant scores as high as my first one with no OC.
Has there been any software updates since launch or no
di11igaf said:
Has there been any software updates since launch or no
Click to expand...
Click to collapse
No idea, I was so focused on custom ROMs since I've owned it I haven't noticed if anything official came out.
Well, looks like I might have my answer: http://forum.xda-developers.com/showpost.php?p=12074403&postcount=2056
Still don't know why one phone would work and the other wouldn't though.
Just an update:
Went and got a different inspire today and it does not have the problem with locking up.
newter55 said:
Just an update:
Went and got a different inspire today and it does not have the problem with locking up.
Click to expand...
Click to collapse
Weird. So I updated to the new Revolution ROM with the updated Buzz kernel that's supposed to fix the issue and my new phone still locks up. So there has to be two different version of this phone out in the field, unless someone who knows more than me can tell me what's up.
If I was you i would swap it out if you still can so you don't have to worry about the issue.
What excuse did you use the second time
First time I swapped I had a legit reason with the GPS not working, I'll have to think about what to tell them this time since I can't say "Set CPU can't overclock this phone once it's rooted."
I'm still hoping someone knows what this is though, pretty sure it's not a defect since the phone actually works better than my first one, everything else considered.
I see these post where people are running there cpu at 1.5 even a few at 1.8.
If i set mine to anything over 1267 my phone locks up instantly and i have to pull the battery.
Am i doing something wrong or something ??
I have used both setcpu and no frills.
Every CPU is different. Yours, unfortunately, is terrible at OCing.
Sucks, but there's nothing you can do about it.
LOL just my luck !!
Have you tried it on any other roms? I could be mistaken, but the kernle could have a bit to do w/ it too.
I can take mine to the highest the CM7 allows w/out issue, not that I'd do it w/ an regularity. That's be a 50% OC.
Ive tried about every rom ... lol They are all the same anything over 1267 locks up... so i just run at 1190 smartass.
That blows.
My wife says she is surprised it even still works .. Ive flashed it 50 or 60 times ...LOL
david032766 said:
My wife says she is surprised it even still works .. Ive flashed it 50 or 60 times ...LOL
Click to expand...
Click to collapse
like a boss
lol, what kernel are you working with?
LeeDroid 3.0.1
Try MDeeJays new kernel it rocks. Always been a flawless flash for me. Just makes sure your rom will run it.
I had this issue with several ROMS. I recently flashed phoenix gb cm rom and oc work awesome Max settings. I'm also surprised my phone still works considering I flash multiple times daily.
Sent from my HTC Inspire 4G
It's hit and miss for me on CM7, I can run 1.5oc pretty easily though.
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.
Is anyone else experiencing this? I get it on Viper 2.2.0 using beastmode, elemental and stock kernels. BM and Elemental were both max 1.7, min 192. I have completely wiped everything, including sd and did a fresh install of viper 1.2.0 up to 1.2.4 with elemental kernel with no issues. Bumped up to 2.2.0 and installed elemental. I made a few test calls and it seemed to be ok then a few hours ago my gf called and it was back. Every single call my phone reboots..Anyone have any ideas? I had been using 2.2.0 for over a week then it just started doing the reboot thing yesterday. I'm currently wiping everything and rolling back to either 1.2.4 or king cobra 1.5. It's so frustrating because I was getting the best battery life I've ever seen on my phone with the viper 2.2.0 beastmode 4.3 combo. All helpful thoughts or suggestions are welcome.
I've not run Viper, but I have the same experience with any of the JB roms. Its even worse with custom kernals, so you might try it without. Just an idea.
After trial and error (flashing, setting up my rom a few changes at a time, test calling to see what breaks calling, wiping..rinsing and repeating) til 5 in the morning I think I've finally figured out my problem.
Turns out for me it wasn't a kernel issue at all, or even a rom issue for that matter. I love the aosp lock screen way more than sense so I would un install the HTC lock screen with tibu; that was fine, no reboots. Then in venom tweaks>lock screen I enabled aosp lock screen...still fine. Then lastly I enabled aosp call work around and bam! Reboots every time! I disabled the work around and have not had a single reset and I've probably made around 15 test calls just to be thorough lol.
I've tested while locked, unlocked, on the lock screen, while browsing, watching YouTube, rebooted then tested...I hope I'm not jinxing myself here but by jove I think I've got it. My settings from a clean wipe are viper 2.3.1, stock radio, beast mode 4.4, max 1.7, min 192, no gpu over clock, mp decision on, s2w off, intilidemand governor. So far everything has been humming right along and working like a charm.
I can't believe I overlooked something so simple and immediately pointed the finger at the rom and kernel when it was my own damn fault lol. Sorry to make so much clutter in the thread but hopefully it can help someone having the same issue.