[Q] Frequent launcher freezes - Hero CDMA Android Development

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

Related

Juice defender problems?

anyone else having problems with the most recent update of Juice defender?
Running Kings kernel #6 and #8 (that i've tried, and its causing extreme lag)
seems like this started after last update to it if I recall.
anyone have a rolled back version of Ultimate juice?
Can you give any more info on what exactly is going wrong? Is the touchscreen just not responding quickly, or is the whole phone that's chugging along? Juice defender on my phone always takes a second or so to re-enable everything after I unlock the screen, and I had an issue for a while where that would take 10+ seconds for it to do this.
Wiping the cache and Dalvik seemed to fix the issue, but I haven't the slightest idea why. That's what worked for me, but if you've tried different kernels and wiped in between flashes and you're still having the issue, your guess is as good as mine.
i had to uninstall juice defender... it was causing everything to go so slow.. even the KB would lag that it would input the secondary fuctions like if i would long press... it kinda ruined the BFS kernel if you ask me
Both hardware unresponsive and chugging during scrolling and selection.
Terribly bad.
Its either SetCPU or Juice defender doing it.
I installed SETCPU and did my thing for 2 hours and it was fine.
installed Juice defender, problems arose.
uninstalled Juice defender, Problem persisted.
Uninstalled SETCPU problems went away.
so tried to opposite the cycle and install Juice defender first.
Phone is now problematic again.
So my guess is not only is Juice defender the problem but its causing an issue with SETCPU as well
(I am not using the CPU option in Juice defender before anyone asks)
yeah, like I said multiple roms, using Amon Ra recovery (since I don't feel clockwork wipes well) and have wiped dalvik/cache , problem still persists.
I've noticed that SetCPU has been updated recently, and maybe they just arent playing well together, But even with SetCPU uninstalled JuiceDefender is wreaking havoc, phone is completely unusable, I can barely uninstall the application after its been installed, have to reboot phone and get to it within 30 seconds before it bogs down and lags phone.
Edit: so its not just me? also running kings and last few days with JD installed its killing me, Which sucks because it really did double my battery life.
Literally didn't lose 1% battery when screen was off all night unplugged haha.
I had just installed Juice Defender 4 days ago and I gotta admit, I was kinda hesitant to do so. I have read quite a few posts regarding the slow downs and sluggishness related to juice defender. As of today, I couldn't be happier with it. My battery life has definitely improved (I'm getting at least 5+ hours more a day with JD running). And i haven't experienced and slow downs or delays with any of my evos functions. I'm running cm 6 nightly (forget which one) with snap 7.11 kernel, and setcpu.
dschoenike
I was stupid enough to actually buy this crapplication. it slows down my system every time I think "let's give it one more try". It slows it down to the point that it is completely unresponsive and doesn't do anything at all but sits there until I kill the application.
If you're experiencing this as well. just uninstall it, best thing you'll do for yourself.
something ruined the App in the most recent update thats for sure, I'll have to report and watch for further development because it truly is great when it works.
The recent update messed everything up, I actually stopped using it after the update because its not helping anything at all. Hopefully the developer gets the kinks worked out.
Jfree3000 said:
The recent update messed everything up, I actually stopped using it after the update because its not helping anything at all. Hopefully the developer gets the kinks worked out.
Click to expand...
Click to collapse
did you hav the "Stable" or BETA version" the BETA is much much better than the "stable".
Ultimate Juice always caused lag for me when I used it. It is a completely useless app, in my opinion, since SetCPU + the natural battery life is fantastic.
JD
Im running Juicedefender ultimate, 1.8.8 Fresh 3, netarchy 4.1.9 and everything is awesome. batt x 2.46 and no lag
i don't know what version is in the market, but when i'm on sense roms i use 2.1.7 i will attach it for you guys. this one works well on the evo. like really well.
uninstall whatever version is in the market and try this one out
on CM6 i normally just turn data off from the power control widget, this nets awesome battery life.
brock1909 said:
did you hav the "Stable" or BETA version" the BETA is much much better than the "stable".
Click to expand...
Click to collapse
I used the stable version, once I updated it ran like crap.
thedudejdog said:
i don't know what version is in the market, but when i'm on sense roms i use 2.1.7 i will attach it for you guys. this one works well on the evo. like really well.
uninstall whatever version is in the market and try this one out
on CM6 i normally just turn data off from the power control widget, this nets awesome battery life.
Click to expand...
Click to collapse
Thx man, that seemed to have done the job.
does juice defender cut off 4G ?
sanjsrik said:
I was stupid enough to actually buy this crapplication. it slows down my system every time I think "let's give it one more try". It slows it down to the point that it is completely unresponsive and doesn't do anything at all but sits there until I kill the application.
If you're experiencing this as well. just uninstall it, best thing you'll do for yourself.
Click to expand...
Click to collapse
Most people don't have any issues with this app. Maybe you should check to make sure it isn't something else entirely, or maybe just another app like setCPU conflicting.
thedudejdog said:
i don't know what version is in the market, but when i'm on sense roms i use 2.1.7 i will attach it for you guys. this one works well on the evo. like really well.
uninstall whatever version is in the market and try this one out
on CM6 i normally just turn data off from the power control widget, this nets awesome battery life.
Click to expand...
Click to collapse
whats the difference from the apk you posted to the one in the market?
The one in the market is the latest stable (v1.8.8) - while thedudejdog attached the latest beta available that time. You could also check http:/latedroid.com/beta/latest/ (sorry, as a new user I cannot post this as working link) for the always latest beta (currently v2.2.0).
But as I'm just here: I currently have installed the latest stable (1.8.8), and have some severe problems with it. What is the best way to switch to the beta (to give JD another chance) without losing the settings - if that's possible at all?
My probs with 1.8.8:
As soon as JD is running and the screen switches off, my IRC client (AndChat) loses the connection
I cannot "configure apps" - JD won't save the changes. With a little trick I can do changes here - but settings are always saved for 1 app only, i.e. if I enable/disable app b with this trick, settings of app b are saved - but those of app a (configured previously) are lost. That means there can only be 1 app configured at a given time.
If JD disabled data completely, they sometimes can be enabled only by a phone reboot (yes, I heard this may also be Android-2.1 specific).
With those problems persisting, the app would be quite useless to me: what does it help if I gain 2..5 hours (or even a day) of battery when I'm not able to use the phone as I require? Without JD, it currently lasts for about 3 full days. Gaining more would be nice - but compared to any trouble I'd prefer staying with my 3 days

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.

Soft keyboard, touchscreen issue

After a search, I know other people have had this issue with the MT4GS. I'm currently running Virtuous Inquisition 4.02. I'm pretty sure i've flashed any updates. Also, I don't remember having this issue on any other ROM that I have ran in the past (virtuous unity, CM 7). The issue is the soft keyboard not responding randomly to certain keys. The weirder thing is if i use a different finger, it usually responds, but if i keep using the same finger, it won't. Is this my digitizer going bad, or just a soft keyboard thing? I haven't experienced the issue in any other part of android, just when using the soft keyboard. is there a touchscreen driver to flash or anything i can do to fix this? thank you!
At least someone else has my same problem
anitgandhi said:
After a search, I know other people have had this issue with the MT4GS. I'm currently running Virtuous Inquisition 4.02. I'm pretty sure i've flashed any updates. Also, I don't remember having this issue on any other ROM that I have ran in the past (virtuous unity, CM 7). The issue is the soft keyboard not responding randomly to certain keys. The weirder thing is if i use a different finger, it usually responds, but if i keep using the same finger, it won't. Is this my digitizer going bad, or just a soft keyboard thing? I haven't experienced the issue in any other part of android, just when using the soft keyboard. is there a touchscreen driver to flash or anything i can do to fix this? thank you!
Click to expand...
Click to collapse
It isn't anything related to the digitizer aparently. I say this because it never gave me a problem using stock rom. This usually happens when the phone gets too hot (you can feel this on the touchscreen). It starts lagging from what i could see, i mean my touches are not recognized properly.
If anyone has a screen calibration .zip laying around i would highly appreciate you to share it
ahh ok thanks for the info. after flashing cm 9.1.0 i can definitely tell the phone isn't getting as hot (according to spare parts, on inquisition the battery would go upwards of 35 celsius regularly, with cm it hasn't gone above 25), and the issue isn't happening anymore. thanks for the help!
rafaelrfq said:
It isn't anything related to the digitizer aparently. I say this because it never gave me a problem using stock rom. This usually happens when the phone gets too hot (you can feel this on the touchscreen). It starts lagging from what i could see, i mean my touches are not recognized properly.
If anyone has a screen calibration .zip laying around i would highly appreciate you to share it
Click to expand...
Click to collapse
You won't believe it but I do have something. This will help to increase sensitivity but for the life of me I can't remember where I got it.
anitgandhi said:
ahh ok thanks for the info. after flashing cm 9.1.0 i can definitely tell the phone isn't getting as hot (according to spare parts, on inquisition the battery would go upwards of 35 celsius regularly, with cm it hasn't gone above 25), and the issue isn't happening anymore. thanks for the help!
Click to expand...
Click to collapse
That's something I just can't understand...when people have troubles with Virtual Inquisition, that is. My wife runs it ALWAYS and I will jump back to it at least once a month for a while myself. It's always been one of the most stable, coolest running and longest battery life ROMs in my nandroids of my favorites. ANYway....give that flashable a try & see if it helps. The best I remember, you can reflash it until you achieve the sensitivity you're looking for. Good Luck!
WeekendsR2Short said:
That's something I just can't understand...when people have troubles with Virtual Inquisition, that is. My wife runs it ALWAYS and I will jump back to it at least once a month for a while myself. It's always been one of the most stable, coolest running and longest battery life ROMs in my nandroids of my favorites. ANYway....give that flashable a try & see if it helps. The best I remember, you can reflash it until you achieve the sensitivity you're looking for. Good Luck!
Click to expand...
Click to collapse
inquisition definitely was very stable and had great battery life, there is little doubt about that. i'm guessing i just didn't flash it correctly, and that caused some really high temps. other than that, i had no issues with it...for example, though, when i was running inquisition, if i left the phone in my pocket and forgot about it until say someone texted me/called me/i got a notification, and i checked the temps, it was at 30-35 celsius, and felt burning. again, i'm guessing i didn't flash it right.
also, thanks for the touchscreen fixer zip, if i have the issue again, i will flash it. fingers crossed i don't need it.
side questions about kernel flashing: 1) do i wipe cache and dalvik cache then flash the kernel zip? 2) is there a way to go back to the original kernel without having to flash the rom all over again?
thanks!
anitgandhi said:
inquisition definitely was very stable and had great battery life, there is little doubt about that. i'm guessing i just didn't flash it correctly, and that caused some really high temps. other than that, i had no issues with it...for example, though, when i was running inquisition, if i left the phone in my pocket and forgot about it until say someone texted me/called me/i got a notification, and i checked the temps, it was at 30-35 celsius, and felt burning. again, i'm guessing i didn't flash it right.
also, thanks for the touchscreen fixer zip, if i have the issue again, i will flash it. fingers crossed i don't need it.
side questions about kernel flashing: 1) do i wipe cache and dalvik cache then flash the kernel zip? 2) is there a way to go back to the original kernel without having to flash the rom all over again?
thanks!
Click to expand...
Click to collapse
Wipe user data/cache .....cache....dalvik....battery stats. All of them 3 times. (CWM has some small issues getting everything on the first shot) Then you flash your Rom. Let it set a minute or two. Lastly....Flash your Boot.img. Be sure not to just let windows just show what's in the .zip file and copy it out but highlightit and open it with Winzip (or whatever you use). EXTRACT it to where you flash your files from. If you don't do it like that it will remain partially compressed and you'll forfet the parts of your kernel that are. Once flashed, let it rest for 5 minutes and you should be good to go.
If flashing another ROM ALWAYS follow those rules but if reflashing with another kernel you can forgo clearing user data so you will keep your apps & their placement in your ROM. Just clear everything else reflash your ROM again & then your kernel. It will look just like it did but with the new kernel. If by chance you then have an issue with force closes just go back to recovery & fix permissions & it should straighten that right out.
BTW....If you are unlocked & S-On you will not be able to flash it from recovery in any form or fashion. You will always need to extract the boot.img file and "ADB fastboot flast boot boot.img" from your command window.
WeekendsR2Short said:
Wipe user data/cache .....cache....dalvik....battery stats. All of them 3 times. (CWM has some small issues getting everything on the first shot) Then you flash your Rom. Let it set a minute or two. Lastly....Flash your Boot.img. Be sure not to just let windows just show what's in the .zip file and copy it out but highlightit and open it with Winzip (or whatever you use). EXTRACT it to where you flash your files from. If you don't do it like that it will remain partially compressed and you'll forfet the parts of your kernel that are. Once flashed, let it rest for 5 minutes and you should be good to go.
If flashing another ROM ALWAYS follow those rules but if reflashing with another kernel you can forgo clearing user data so you will keep your apps & their placement in your ROM. Just clear everything else reflash your ROM again & then your kernel. It will look just like it did but with the new kernel. If by chance you then have an issue with force closes just go back to recovery & fix permissions & it should straighten that right out.
BTW....If you are unlocked & S-On you will not be able to flash it from recovery in any form or fashion. You will always need to extract the boot.img file and "ADB fastboot flast boot boot.img" from your command window.
Click to expand...
Click to collapse
i'm s-off so i don't need to worry about the boot.img extraction and all that, but the rest was very helpful, thank you very much!
:good:
anitgandhi said:
it was at 30-35 celsius, and felt burning.
Click to expand...
Click to collapse
Whenever anyone mentions overheating issues with the device - the first questions should always be:
Are you on a stock battery?
If so, then that is your problem.
I've forgotten to manage setcpu and left it running at 1.7 more often then anything, yet very rarely run into overheating issues...unless I go back to a stock battery (even without overclocking)
Blue6IX said:
Whenever anyone mentions overheating issues with the device - the first questions should always be:
Are you on a stock battery?
If so, then that is your problem.
I've forgotten to manage setcpu and left it running at 1.7 more often then anything, yet very rarely run into overheating issues...unless I go back to a stock battery (even without overclocking)
Click to expand...
Click to collapse
i am on stock battery. good to know that it usually causes overheating...glad it's not happening with cm 9.1.0 though
WeekendsR2Short said:
You won't believe it but I do have something. This will help to increase sensitivity but for the life of me I can't remember where I got it.
Click to expand...
Click to collapse
the issue came back (although not as frequently) so i went to flash the zip that you attached... it says it's something relating to beats audio and then it errors out and the installation aborts. i looked at the files inside all have "beats" and "audio" in the filenames...

What is killing my phone's performance?

Hi all,
I've been struggling for the past few months with terrible performance issues on my Droid Charge. Things like redrawing the home screen and lag between switching programs I can live with, but when it takes several minutes to pull up the dialer to make a phone call or to answer a text message, my phone kind of stops being useful as a phone.
I started off on stock when I got the phone last year, then I rooted it a few months later. Everything was great until June. Gradually, my phone had become less responsive (taking forever to make calls, view and send texts). That plus something weird was eating >2GB data/month, and I could only identify it as "Android OS/others" via Onavo. I decided to go clean and try Tweaked 2.2w/PBJ. Things were pretty good for a couple of weeks until the major lag started coming back. I stepped back and uninstalled many apps, hoping to find one that was the main culprit, but my phone continues to act like it's trying to calculate a billion values of pi or something.
I tried following the steps from the rootzwiki "5 Steps to Keep Your Phone Snappy/Lagfree" (not allowed to link yet ), which helped somewhat, but it has not eliminated the problem. I often find myself resetting my phone to make phone calls. SwiftKey often doesn't load correctly and requires me to enter and exit applications frequently to get it to allow me to type. I had to wait nearly 2 minutes to get my home screen to display until I removed Holo Launcher and went back to TouchWiz.
Sorry for the essay--I'd be happy to provide additional details if needed. What can I do to a) figure out what's wrong with my phone and b) fix it?
Thanks in advance!
petrivka said:
Hi all,
I've been struggling for the past few months with terrible performance issues on my Droid Charge. Things like redrawing the home screen and lag between switching programs I can live with, but when it takes several minutes to pull up the dialer to make a phone call or to answer a text message, my phone kind of stops being useful as a phone.
I started off on stock when I got the phone last year, then I rooted it a few months later. Everything was great until June. Gradually, my phone had become less responsive (taking forever to make calls, view and send texts). That plus something weird was eating >2GB data/month, and I could only identify it as "Android OS/others" via Onavo. I decided to go clean and try Tweaked 2.2w/PBJ. Things were pretty good for a couple of weeks until the major lag started coming back. I stepped back and uninstalled many apps, hoping to find one that was the main culprit, but my phone continues to act like it's trying to calculate a billion values of pi or something.
I tried following the steps from the rootzwiki "5 Steps to Keep Your Phone Snappy/Lagfree" (not allowed to link yet ), which helped somewhat, but it has not eliminated the problem. I often find myself resetting my phone to make phone calls. SwiftKey often doesn't load correctly and requires me to enter and exit applications frequently to get it to allow me to type. I had to wait nearly 2 minutes to get my home screen to display until I removed Holo Launcher and went back to TouchWiz.
Sorry for the essay--I'd be happy to provide additional details if needed. What can I do to a) figure out what's wrong with my phone and b) fix it?
Thanks in advance!
Click to expand...
Click to collapse
could any number of issues - ranging from a rogue app to the ROM not sticking correctly. when you installed Tweaked, did you do it via CWM or ODIN?
also, did you enable the build.prop tweaks to help with redraws and making calls?
otherwise, I would suggest to try wiping cache and dalvik (sometimes that cleans it up a bit as well rebooting the phone once every few days) to help clear out some of the clutter.
do you have any "force close" messages (such as SyncMLSvc)?
Thanks for the quick reply.
I installed Tweaked through ODIN. I haven't heard about the build.prop tweaks though. Is there a resource you can point me to or a quick process to enabling them? I thought that a lot of these tweaks were "cooked" into the Tweaked ROM.
I've got App Cache Cleaner dejunking me every 4 hours, and I try and hit the davlik every day...I still have issues.
I do have the SyncMLSvc force close on boot. I figured it was a known bug in Tweaked and that it'd be addressed in a later revision. Is it a symptom of something more ominous?
petrivka said:
Thanks for the quick reply.
I installed Tweaked through ODIN. I haven't heard about the build.prop tweaks though. Is there a resource you can point me to or a quick process to enabling them? I thought that a lot of these tweaks were "cooked" into the Tweaked ROM.
I've got App Cache Cleaner dejunking me every 4 hours, and I try and hit the davlik every day...I still have issues.
I do have the SyncMLSvc force close on boot. I figured it was a known bug in Tweaked and that it'd be addressed in a later revision. Is it a symptom of something more ominous?
Click to expand...
Click to collapse
i don't use App cache cleaner, and thus do not have any issues. also, if you have TiBu, you can uninstall that syncmlsvc. see if that does the trick.
regarding the build.prop tweak, remove the # from ro.home_app_adj=1
here is a link to some others: http://www.s3forums.com/forum/galaxy-s3-hacking-mods/474-list-some-build-prop-tweaks.html
Do you have facebook installed? That P.O.S. kills my phone everytime. I install it from time to time just to see if they are coming close to fixing it. Needless to say it gets uninstalled in under 10 minutes.
I know everybody will jump all over me on this but why not try stock rooted FP5 for a couple of days. It will give you a baseline to compare other roms and app impact with. If your phone still acts up it would seem to be pointing to a hardware error IMHO.
What can it hurt?
Still Charged Up
Reilly1812 said:
Do you have facebook installed? That P.O.S. kills my phone everytime. I install it from time to time just to see if they are coming close to fixing it. Needless to say it gets uninstalled in under 10 minutes.
I know everybody will jump all over me on this but why not try stock rooted FP5 for a couple of days. It will give you a baseline to compare other roms and app impact with. If your phone still acts up it would seem to be pointing to a hardware error IMHO.
What can it hurt?
Still Charged Up
Click to expand...
Click to collapse
Apparently Facebook is making their employees switch from ios to android so they finally so something about the app.
Sent from my SCH-I510 using Tapatalk 2
JihadSquad said:
Apparently Facebook is making their employees switch from ios to android so they finally so something about the app.
Sent from my SCH-I510 using Tapatalk 2
Click to expand...
Click to collapse
LOL! They're all too busy dumping their worthless stock to care.
Still Charged Up
Reilly1812 said:
LOL! They're all too busy dumping their worthless stock to care.
Still Charged Up
Click to expand...
Click to collapse
Abandon ship!
Sent from my SCH-I510 using xda premium
I started usin Fast for Facebook. U cant do as much, but its not a battery hog which i think is super important
Sent from my SCH-I510 using xda app-developers app
cnoevl21 said:
I started usin Fast for Facebook. U cant do as much, but its not a battery hog which i think is super important
Sent from my SCH-I510 using xda app-developers app
Click to expand...
Click to collapse
It probably doesn't make you believe your running Froyo again either : crawling and littered with FC's
Still Charged Up
Most importantly out of everything is to always check out your md5's and make sure they match. Also try going back to stock with the pit file too for a full fresh install. But I think the problem is the md5 sums unless you download apps off the internet
Edit: also remember to mount system when flashing roms
Reilly1812 said:
Do you have facebook installed? That P.O.S. kills my phone everytime. I install it from time to time just to see if they are coming close to fixing it. Needless to say it gets uninstalled in under 10 minutes.
I know everybody will jump all over me on this but why not try stock rooted FP5 for a couple of days. It will give you a baseline to compare other roms and app impact with. If your phone still acts up it would seem to be pointing to a hardware error IMHO.
What can it hurt?
Still Charged Up
Click to expand...
Click to collapse
So, an update: I thought it was SwiftKey that was killing my phone, because I was doing better after I removed it. It was crappified even then, even after removing Facebook. I bit the bullet yesterday and went back to stock, updated all the way to FP5. I kept Facebook off (I've mostly moved over to G+ anyways). Everything is great. I put SwiftKey back on, and everything is still great.
I hate to say it, but even though the loss of customization in Tweaked is disappointing, I'm more satisfied with the phone in general with the stock ROM. My battery even lasts more than 3 hours too.
If it ain't broke...
petrivka said:
So, an update: I thought it was SwiftKey that was killing my phone, because I was doing better after I removed it. It was crappified even then, even after removing Facebook. I bit the bullet yesterday and went back to stock, updated all the way to FP5. I kept Facebook off (I've mostly moved over to G+ anyways). Everything is great. I put SwiftKey back on, and everything is still great.
I hate to say it, but even though the loss of customization in Tweaked is disappointing, I'm more satisfied with the phone in general with the stock ROM. My battery even lasts more than 3 hours too.
If it ain't broke...
Click to expand...
Click to collapse
my phone usually has that affect after flashing a new ROM. basically it's the wiping of data and cache/dalvik that helps cleans out the problems.
jco23 said:
my phone usually has that affect after flashing a new ROM. basically it's the wiping of data and cache/dalvik that helps cleans out the problems.
Click to expand...
Click to collapse
Maybe...but I've been wiping the cache/davlik fairly often. I had uninstalled most my apps...maybe some weird bug was still manifesting itself. I don't think my phone has been this responsive even after first going to Tweaked. :-/
petrivka said:
Maybe...but I've been wiping the cache/davlik fairly often. I had uninstalled most my apps...maybe some weird bug was still manifesting itself. I don't think my phone has been this responsive even after first going to Tweaked. :-/
Click to expand...
Click to collapse
Well as long as your happy that's all that really matters. To be fair - there is nothing in Tweaked that should degrade performance at all compared to what is normally seen in stock. The one difference I could see is that Tweaked is deodexed - and many swear the odexed approach is faster/snappier/whatever-adjective-you-want-to-say-that-means-better than the deodexed one. Hopefully things stay functioning well.
dwitherell said:
Well as long as your happy that's all that really matters. To be fair - there is nothing in Tweaked that should degrade performance at all compared to what is normally seen in stock. The one difference I could see is that Tweaked is deodexed - and many swear the odexed approach is faster/snappier/whatever-adjective-you-want-to-say-that-means-better than the deodexed one. Hopefully things stay functioning well.
Click to expand...
Click to collapse
I hear ya. I figure I'll give stock a go for a while, at least until Tweaked comes out of beta. I'm still counting down the days until I can upgrade to something with ICS. Or maybe even a Lumia 920...
petrivka said:
...at least until Tweaked comes out of beta...
Click to expand...
Click to collapse
It's out of beta - check it out here if interested
I tried forever to get PBJ to play nice. RFS & ext4. Gemini App Manager autostart tweaks. MinFree tweaks. All the TweakTool init.d tweaks. The SQL index tweaks. overclocking. Autokiller, other memory apps, JuiceDefender, other build.prop tweaks, etc. I tried it all...
I'm not sure if it was my hardware version or what, but I just could not get it to work well. It always seemed like it ran out of memory and couldn't automatically manage the apps in an overloaded situation. If i manually ran some of the SQL scripts, and killed running apps, it would be ok, but not for long. I had problems losing text messages because I think the text message handler got killed or didn't run in time. I've tried GoSMS and the stock SMS. I ended up relying on Ghostly SMS to help catch the texts I lost.
Once I went back to stock FP1, most of my problems went away. It's been much more stable. So, since then, it's been stock kernel (obviously on RFS). I've been on FP5 with various versions of Tweaked 3 beta/RC and now I'm no the final. All good.
So, as much promise PBJ has or had (who knows what the FP1/FP5 hybrid will turn out like), stock kernel with Tweak 3 is the way to go for me!
CalPolyRock said:
I tried forever to get PBJ to play nice. RFS & ext4. Gemini App Manager autostart tweaks. MinFree tweaks. All the TweakTool init.d tweaks. The SQL index tweaks. overclocking. Autokiller, other memory apps, JuiceDefender, other build.prop tweaks, etc. I tried it all...
I'm not sure if it was my hardware version or what, but I just could not get it to work well. It always seemed like it ran out of memory and couldn't automatically manage the apps in an overloaded situation. If i manually ran some of the SQL scripts, and killed running apps, it would be ok, but not for long. I had problems losing text messages because I think the text message handler got killed or didn't run in time. I've tried GoSMS and the stock SMS. I ended up relying on Ghostly SMS to help catch the texts I lost.
Once I went back to stock FP1, most of my problems went away. It's been much more stable. So, since then, it's been stock kernel (obviously on RFS). I've been on FP5 with various versions of Tweaked 3 beta/RC and now I'm no the final. All good.
So, as much promise PBJ has or had (who knows what the FP1/FP5 hybrid will turn out like), stock kernel with Tweak 3 is the way to go for me!
Click to expand...
Click to collapse
You're 100% correct!!
Please correct me if I'm wrong because I really want to know. The way I see it is, the real improvements over FP1 came from what Samsung did with FP5. Then what Dwitherell did was remove the useless bloat and ugliness then add the useful features and beautify it without changing anything that would hurt the performance.
The first time I upgraded to FP5 stock I noticed the speed increase right off. I checked it out a little and was amazed. But of course it had all of Verizon's bloat garbage in it and none of the awesome tweaks from Dwith. And it had no user installed apps in it at all. It has always seemed like the more apps I install the slower the phone gets.
So am I right?

Categories

Resources