Hey all, I am rooted have been running GB .588 for a while. I have been very happy with it (after I found the apps I had to freeze to correct the perpetual sync issue), but in the last few days my phone has gotten almost as laggy as my old Eris was before I rooted and rom'ed it. Has anyone else experienced this, or do I need to look at my recently added apps? Will upgrading to .595 correct these issues? Please forgive me if this is an asked and answered situation, I have recently gone back to school and I don't have the time to peruse the forum the way that I used to. Thanks so much.
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root Debilitating Lag
- Thread starter Trumpup
- Start date
-
- Tags
- motorola droid x
spartan141
Android Enthusiast
of all the GB rom leaks .595 seems to be the most stable and most snappy. touch response is good. ive been running it on my wifes DX for a few days now. before, it was soo laggy to the point that i could not do anything to the phone. try to turn it on and it hangs in the lockscreen. try to type and nothing shows up. constant reboots every 45 mins. and i could not make a call or send a text without it taking a crap. so i did a factory reset and upgraded to the .595 leak. but we shall see if its any better in the long run. but so far soo good.
VoidedSaint
Resident Ninja
the X was always plagued with random reboots, but it hasnt happened very often for us as of late, the new roms have seem to put a stop to that. its possible your phone is overheating. is it overclocked? if its left out in the heat it will become very sluggish and unresponsive, i have found this out the hard way, but my X is a brick, it can take the punishment and still continue to be the best phone i have ever owned.
cougar214
Android Expert
I've only ever had 2 random reboots on my phone but after tweaking some settings it would stop. The first time it ever happened was right after I flashed the .571 release. The second time was after I flashed the .595.
There was a post about someones phone always rebooting into CWR and the fix for it was hitting the "bootstrap recovery" button in bootstrap but NOT hitting "reboot recovery". I had this issue as well and coincidentally it also stopped the random rebooting.
We all know these DX's are not consistent so what works for one user won't work for another. But it can't hurt to try anyway. As for the OP, I would flash the .595. It's more stable than any release before it. Also go with Stevens suggestion and use the autokiller memory optimizer. It's the only one that seams to have a positive impact.
Don't waste your time with all the other memory/ram optimizers and app killers. They seam to actually do more harm then good because your phone needs these apps running to work properly( by harm I just mean lag/poor performance issues).
EDIT: VoidedSaint you're right. I also made the mistake of leaving my X out in the sunlight one day. Boy was that a mistake. This thing wouldn't do anything till I turned it off and let it cool first. I couldn't even make/receive calls it was so bad. The DX is a great phone but it doesn't like heat.
There was a post about someones phone always rebooting into CWR and the fix for it was hitting the "bootstrap recovery" button in bootstrap but NOT hitting "reboot recovery". I had this issue as well and coincidentally it also stopped the random rebooting.
We all know these DX's are not consistent so what works for one user won't work for another. But it can't hurt to try anyway. As for the OP, I would flash the .595. It's more stable than any release before it. Also go with Stevens suggestion and use the autokiller memory optimizer. It's the only one that seams to have a positive impact.
Don't waste your time with all the other memory/ram optimizers and app killers. They seam to actually do more harm then good because your phone needs these apps running to work properly( by harm I just mean lag/poor performance issues).
EDIT: VoidedSaint you're right. I also made the mistake of leaving my X out in the sunlight one day. Boy was that a mistake. This thing wouldn't do anything till I turned it off and let it cool first. I couldn't even make/receive calls it was so bad. The DX is a great phone but it doesn't like heat.
deathratlehead
Android Enthusiast
what settings do you use for autokiller? There are a ton of presets.
Wally World
Android Expert
I am not overclocked, and I don't think it has been overheated. It had been working great, but over the course of a few days, it got unbearably laggy. I read another post where they discussed turning the phone off and removing the battery for an hour to clean up processes that were looping in the background. I tried that, and it seems to have helped.
Thanks for your help.
Thanks for your help.
VoidedSaint
Resident Ninja
or you could have booted into cwm and cleared cache, would have been the same process and faster
personal thoughts: I know taskkillers are shunned by some but I find it usefully to keep around. I don't have my set to autokill anything but when I notice the phone lagging I fire it up and knock out the big memory users, like browsers, markets, voice, etc.
I was just about to flash last night due to lags but then I realized my underclock was the problem. I had my CPU set down to 350 when the battery got too low. Caused all sorts of problems. Lagging really didn't stop until I got back over 600.
Anyway, just my 2 cents.
I was just about to flash last night due to lags but then I realized my underclock was the problem. I had my CPU set down to 350 when the battery got too low. Caused all sorts of problems. Lagging really didn't stop until I got back over 600.
Anyway, just my 2 cents.