Hello,
I have been struggling with this issue forever. I am using my Google nav app and all of a sudden it freezes barely updating with CPU @100%. I have tried different options using 3g instead of 4g, not using bluetooth, not starting nav when CPU is busy nothing has worked. All of a sudden either at the start or during a navigation session the CPU will go up to 100% and the app will stop updating and if I am driving I left without directions until I reboot. Huge headache. I used different system monitors like 'WatchDog Lite' and 'System Tuner' and those apps say that the most CPU consuming process during that time period is 'Android System Process'. I have no clue as to what 'Android System Process' is doing during that period of time except it is taking a large amount of CPU.
Only option left is to overclock, upgrade to a faster CPU from Verizon or go to Apple IPhone
That's strange, I used the navigation all the time without a problem, besides slow locks. Have you tried clearing the app data, sounds like its the app itself misbehaving.
Sent from my DROID RAZR using XDA
I haven't had an issue like that and its definitely abnormal. Have you tried installing a ROM like Tweaked or a kernel like PBJ?
Sent from my SCH-I510 using xda premium
I had the same problem before I rooted and installed my first ROM. No problems since then. Recommend you root, install Tweeked or Eclipse and PBJ, also don't undervolt too much. You're headache should stop. I haven't had that happen to me in long long time. I'm a truckdriver and use the maps quite often.
Sent from my SCH-I510 using XDA
I had the same problem star up all of a sudden a month or two ago. Google maps would just close by itself, and nav would freeze while driving. While messing around one day, I ended up having to wipe my phone and ODIN stock, re root, and put Tweaked 2.1 ROM on it again, and restore all my backed up apps. To my pleasant surprise Google maps and nav are working flawlessly now.
Sent from my SCH-I510 using XDA
I have been partially able to fix the problem. One I downloaded Copilot Live as a navigation app which uses offline maps instead of downloading maps on the fly like google nav. However, still my phone used to lag close to 20-30 seconds when I would go to my home screen and similarly when I went to my application lists. I was using Seepu so I could see that my CPU was at 100% all the time. This led me to believe that there might be an issue with my SDCard and hence I downloaded sdbooster https://play.google.com/store/apps/details?id=de.mehrmann.sdbooster&hl=en .
I saw an amazing performance improvement after I set the cache size to 8192 mb and the lags all but disappeared. However, still when I am on my home screen it sometimes lags 5 seconds which is still infuriating. What the heck is it doing, is it reading apps from the disk?
Related
Alright guys, I have a simple question for ya.
I've recently flashed CyanogenMod 7 onto my Droid 1, and have been experiencing problems. They are as follows:
1) After a phone call, I either need to wait about 5 minutes to get my data(3G) signal back, or reboot because it never gets a data connection back
2) I can no longer multitask as efficiently, and example is if I'm listening to music (Pandora, Rhapsody, or the default music app) and I go home to do another activity (Facebook, Browser, Pulse, etc.) my music app stops playing and the ongoing notification disapears.
3) My Facebook contacts are no longer kept in sync. It still is the same version as the one I used on CM6.1.2. However, when I do select to sync, it adds the contacts, without pictures, and within an hour, they are removed.
4) My messaging app, although it is locked in my memory, still is being killed by my system.
I've tried restoring, fixing permissions, formatting data and system.
So: has anyone else that hs CM7 expierenced these problems and if you did, did you have a solution?
Thanks in advance
Sent from my Droid 1 running CM 7 OC'd to 1.2GHtz using XDA app
I have the problem with Pandora/slacker and mutlitasking... though I haven't had any of the other problems. I'm on nightly #25. No solutions yet.
Protocol 7 said:
Alright guys, I have a simple question for ya.
I've recently flashed CyanogenMod 7 onto my Droid 1, and have been experiencing problems. They are as follows:
1) After a phone call, I either need to wait about 5 minutes to get my data(3G) signal back, or reboot because it never gets a data connection back
2) I can no longer multitask as efficiently, and example is if I'm listening to music (Pandora, Rhapsody, or the default music app) and I go home to do another activity (Facebook, Browser, Pulse, etc.) my music app stops playing and the ongoing notification disapears.
3) My Facebook contacts are no longer kept in sync. It still is the same version as the one I used on CM6.1.2. However, when I do select to sync, it adds the contacts, without pictures, and within an hour, they are removed.
4) My messaging app, although it is locked in my memory, still is being killed by my system.
I've tried restoring, fixing permissions, formatting data and system.
So: has anyone else that hs CM7 expierenced these problems and if you did, did you have a solution?
Thanks in advance
Sent from my Droid 1 running CM 7 OC'd to 1.2GHtz using XDA app
Click to expand...
Click to collapse
1) Known issue with all GB based ROM's for the D1. Enable airplane mode a few times to force it to come back.
2) This is due to GB's aggressive memory management and the D1's lack of RAM. To help this you can do 1 of 3 things.
A. Use Swappa 2 to make a swap space on your SDcard.
B. Enable Compcache at about 18% or so.
C. Change ROM's and use Project Elite 5.0.2. They have a function that allows you to lock up to three apps into memory so they don't get auto-closed.
3) I don't use Facebook so I'm no help there.
4) Refer to number 2.
Good Luck!
Hello I'm having the same problem. My Droid seems to not be able to multitask very well anymore. My music player will often get killed by the system randomly, and it has made this phone pretty much useless for music.
I have tried enabling compcache and everything and it doesn't seem to help. I assume this is a problem of the Droid not having enough memory?
Sent from my Droid using XDA App
I'm running CM7 RC4 on my droid and the only "issue" I've noticed is that I get a low memory warning from time to time.
What kernel are you running?
Perhaps CM7 is too much for droid at stock speeds.
The 1.1Ghz low volt Chevy kernel does a very good job for me.
Do you have any issues with music playback? Maybe my kernel is the problem. The 1.2 ghz slayher kernel bootloops with my CM7 but it worked fine on CM6.
Sent from my Droid using XDA App
Sorry to post again, but I just wanted to update you guys. Flashed the Chevy 1.1 LV kernel and am still having the music player shut itself off when I try to open other apps. If I leave the music player up in the foreground, it will run all day with no issues. The minute it gets sent to the background, android seems to kill it within seconds.
The taskbar notification for the player will also disappear, but may reappear randomly as I continue to use my phone. It will appear briefly, then vanish. The music will never resume playback, however, until you physically hit the pause button and then the play button.
The sad part is that this behavior was exactly what my Motorola Q used to do. The thing had so little memory that the minute apps were released from the foreground view, they'd almost instantly close. I hate to say this but I think the only solution is a new phone... I guess android has finally outpaced the hardware on the OG Droid.
I've tried everything setting the music & media processes to 'always keep alive' using the little blue fish memory manager, but that doesn't seem to work. Like I said before, *something* is closing the music process very aggressively when it leaves the foreground and I'm not sure why it's doing this.
Sent from my Droid using XDA App
Yeah I'm using cm7 on my Droid incredible. Everything works fine except, sometimes applications such as messaging app and the default web browser restart randomly. I'm also using the kernel that came with it.
Sent from my ADR6300 using XDA App
I've found that particular memory-hungry apps tend to cause the music player to close itself. The browser for one, almost guarantees that the music playback will stop. Last night I was able to keep the music playback going while switching between my SMS inbox and Tweetdeck. However certain other app combinations don't seem to work so well.
I've heard some talk of "bulletproofing" ... is this something that could help in my case? What does it do and how do I go about locking the music player in memory?
Sent from my Droid using XDA App
Last night flashed generic 2.3.3 from forum to phone. All running fine till today. Sometimes when exiting apps its like the home app has restarted. I lose the icons either side of the app drawer button then they come back. Weirdly if i go into the drawer lots of the icons have been replaced by empty space or a grey box. Then they slowly re appear. Anyone ever had this? All the menu order settings default also. Returning to my setting when what i guess is the home app finishes re loading.
Sent from my X10i using Tapatalk
Sent from my X10i using Tapatalk
Seems to be a memory issue. Unstalled swiftkey which was munching memory and turned off the timescape auto update and removed widget now seems to have fixed memory issue and freed up about 60 mb of memory. Now got 60 free constant
Sent from my X10i using Tapatalk
And the problem is back within 20 mins. Definatley a memory issue I thought, time to clear some apps out! Its doing it when they all open to do updates even when set not to!
Now I've turned phone on and off for 1st time since turning on after flashing and not used my task killer all day - not a problem no crashes, no lag, swiftkey re-installed. No other programs removed. Phone very fast and responsive, battery drain considerably less.
Will try with timescape again but have it set to manual refresh and see how it goes.
Lately my Nexus S has been behaving oddly. It's slow to respond for simple things like opening up gosms takes 10-15 seconds at times, pulling down the notification bar takes longer than normal and when it gets slow it tends to freeze up while loading whatever I have asked it to do.
I figured it was just jelly bean causing it to work harder than before so I went back to gingerbread (CM 7.2) which I had on it before and it used to be pretty snappy, but alas the issue remains. Very sluggish and freezing up.
On top of this my battery now does not last more than 4 hours when it used to go a good 12-13 hours and the phone gets very hot at times, I can feel it in my pocket when it heats up.
All of this has been happening the last 4 days.
So far I've tried doing a factory reset, a full wipe and re-flash, fixed permissions. Nothing has worked so far.
I am on the CM 7.2 kernel, Right now the only apps I've installed are the google apps, thinking it may have been a rogue app, but the problem is still there.
Any ideas what the issue may be, or is my dearly beloved Nexus just taking it's final breaths? lol
Install OS Monitor and see which app or process is eating up the cpu. Most likely the media scanner is running with an almost full sdcard. Also try to reformat your sdcard, back up first though.
Sent from my Nexus S using xda premium
[email protected] said:
Install OS Monitor and see which app or process is eating up the cpu. Most likely the media scanner is running with an almost full sdcard. Also try to reformat your sdcard, back up first though.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
My SD Card has only 2GB used at the moment.
I installed watchdog and this morning I see 3 alerts that the Gmail app was pushing the cpu at 63%. That's the only app that shows heavy cpu use.
Fiasco said:
My SD Card has only 2GB used at the moment.
I installed watchdog and this morning I see 3 alerts that the Gmail app was pushing the cpu at 63%. That's the only app that shows heavy cpu use.
Click to expand...
Click to collapse
That's weird. Try uninstalling Gmail and see if that fixes your issue. Then you can reinstall it from the PlayStore.
Sent from my Nexus S using xda premium
So gmail was the battery killer in this case. I removed it then reinstalled from market and it's normal again.
My nexus is still vsery sluggish when opening and using apps. Even typing this now it freezes up and skips letters.
Also the phone is quite hot to the touch at the moment after doing a reboot about 5 minutes ago.
Any ideas?
Hi,
What JB ROM were u using? What kernel?
Because JB is smooth as heck for me and I've tried a few different ROMs.
It could be ur apps notifications or the animation on the app drawer.... or other transition animation. Just turn them all off.
Try clearing the cache and data on some the app under "manage app" section.
Crack up the CPU if u got a lot of data being used in the background such as email, gmail, goggle now, etc.
Heck find some time to reflash the ROM u like, but run it without adding anything to see if it starts out sluggish. If so then its the ROM and or kernel.
If it starts out smooth then add ur apps and background data one by one to see what is hogging the CPU.
I'm running codename android with air kernel(stable) and I have minimal or no lag at all.
Slim bean with air kernel also runs smooth.
Good luck
Vs Nexus S4G using tapatalk2
---------- Post added at 11:26 PM ---------- Previous post was at 11:21 PM ----------
I've also read that if u were a flash a holic u may have some unwanted data on ur SD card that being read by the android system.
So copy ur SD card to ur computer and format the SD card.... then only add the ROM zip files onto the SD card for a very fresh I stall.
Good luck
Vs Nexus S4G using tapatalk2
I tried androxide and the 99% google experience JB roms. I then tried CM 9.
All of these were sluggish, freezing up constantly and running very hot.
Since my last post I have gone back to CM 7.0.3 which is the rom I was running prior to trying JB.
This rom runs smooth, very responsive and the battery life is great.
Go figure I guess.
I am on CleanRom 3.0 right now, fresh install. Now, for the problem. Today while sitting in class I took my phone out to see it was booted into safe mode. So I rebooted it back, and noticed a lot of my downloaded apps were launching 10-25 seconds after I clicked to open them. So, I rebooted again. That didn't work. I cleared cache and dalvik cache. That didn't work. So, I dirty flashed CleanRom 3.0, which still didn't work. After driving and listening to spotify in my car, the apps launched completely fine, and still are. Does anyone know why this is happening? By the way, this happened on my rooted stock rom, that's why I switched roms. I don't know if this could cause any issues, but I do use Directory Bind.
Have you checked if power saver is on?
Another possibility could be a lot of applications running the background and just slowing your phone down.
Check your task manager by holding the home button for about 2-3 seconds.
Yea, power saving is off. And there isn't any apps running in the background when it's ran slow. Most stock apps will launch fast (settings, phone, clock), but downloaded ones won't (I funny, handcent sms). I seriously can't figure out what the issue is. I've even tried messing around with set cpu, but that didn't help.
Sent from my SCH-I535 using xda app-developers app
Try cache mate.
Sent from my SCH-I535 using xda app-developers app
Hi all,
I just bought a Moto G LTE 8GB (XT1045) and so far, I'm loving it! However, I have run into difficulties running two apps at the same time. For example, when I use the Rdio app to play music, and then press the home key, and then run Google Maps, my Rdio app will quit (i.e. not just stop playing music, but really quit). Then, if I start navigating somewhere in Google Maps, and then go back and re-run Rdio, Google Maps will quit as soon as Rdio boots up.
This doesn't only happen with these two apps-- it happens with my Audible too with my running app, and stuff like that.
Any ideas? Is it sound-related? ROM-related? (And if it's ROM-related ... is there any ROM out for XT1045 that fixes this?)
Thank you so much! I tried searching the forums but could not find an answer ... I learned that Back button ends app while Home leaves it running, but I have only been pressing Home.
best,
toohsieh
I've been having this same problem lately. Figured I would bump this thread. I've been using Titanium Backup to freeze some Motorola apps because i think Motorola's background services are to blame, but not positive it is helping.
In developer mode, go to "Background Processes" and verify that 1 process isn't clicked. You could even experiment with forcing more apps to run in the background.
I don't know if this is the problem but it's a simple place to start.
Sent from my XT1045 using XDA Free mobile app
jtcartrite said:
In developer mode, go to "Background Processes" and verify that 1 process isn't clicked. You could even experiment with forcing more apps to run in the background.
I don't know if this is the problem but it's a simple place to start.
Sent from my XT1045 using XDA Free mobile app
Click to expand...
Click to collapse
For me at least, they do run in the background, but only for like 10 minutes. After a certain time one of the apps will be cleared out to make room for ram. I have been monitoring the ram and running Google Maps Navigation and Google Music in the background and the ram is indeed listed as Critical (<96mb inactive). Cleared out a ton of the Motorola services and it did help a ton because they all ran with a Nice priority of 100.
After running the phone for a while there seems to be memory leaks. Restarting helps a lot. I'm using XPosed, so I wonder if Gravitybox is doing anything nefarious to my ram, but that is purely speculation. I'm thinking of switching to GPE to see if that helps.
EDIT: Switching to GPE has helped immensely so far. But, I'm noticing Google Maps seems to grow in memory over time a lot too. It has gone from 70mb to now 170mb over a few hours in navigation mode.
EDIT2: Maps seems to cap off at 170mb. So I guess it is fine. Ran Google Music and Google Maps for about 8 hours and they both continued without closing.