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
Related
After the 3.1 update, when I listen to music while the Music app is running in the background (using the widget or notification widget), the songs always crash in like 30 seconds.
Anyone getting this? Its pretty frustrating and annoying since it never did this before.
Should also write, that when I am listening to music with the player open, all songs work fine.
Anyone? No one is getting this problem?
Sent from my Nexus S using XDA App
Is it force closing or just stopping?
If it is just stopping, I would guess that honeycomb is removing it from ram due to being low on ram. It really shouldn't do that since it is an activite service, but that is my guess.
Sent from my Xoom using XDA App
Hmmm yea it doesn't force close it just stopped and the icon disappears like the xoom closed it out. However that really sucks because it is running....you know it may be a bigger issue. When I watch playon and switch to a browser for a sec then switch back I have to reload it and log in again. Its annoying but I never had to do that pre 3.1. Anyone else having these issues? Did Google mess with background apps and the multitasking resource allocation? Still the music player is active sso I don't know what is going on. Any help would be greatly appreciated
Sent from my Nexus S using XDA App
No issues here. Sorry to hear... try a reset?
I'm considering rooting, even though I'd prefer to keep this device stock, simply to have the ability to tweak the background process killer in Honeycomb. I don't know if it's something Asus cranked up, but I haven't heard of anyone else with a tablet having the same problems that I do. I literally cannot listen to music (through ANY app, default Android Music or whatever, they ALL die) because at some random point, beteeen 5 and 15 minutes after I switch away from the player to do something else with my tablet, ActivityManager will kill it and respawn it. This obviously stops playback, which is annoying.
I have no task killer apps or anything like that running on the tablet. Checking logcat shows nothing leading up to the event, simply a line for ActivityManager whacking the music player PID, then restarting it. If I leave the player in the foreground, it's fine, and plays without stoppage. When I switch away from it to browse, or write this post in the XDA app (expecting music to die shortly ...) or anything, it will get killed, even though it's still playing music.
Anyone else experiencing something like this?
Sent from my Transformer TF101 using xda premium
No, it's certainly not normal, and I suggest doing a factory reset before rooting if you want to keep it stock (even though custom ROMs do offer better overall performance). Does it happen randomly, even if you're sitting at the desktop for the 15 minutes, or does it only happen when you are switching between lots of apps, or using memory heavy apps?
Gary13579 said:
Does it happen randomly, even if you're sitting at the desktop for the 15 minutes, or does it only happen when you are switching between lots of apps, or using memory heavy apps?
Click to expand...
Click to collapse
The only situation which will keep the app from dying is if it's the active, foreground app. Strangely enough, the screen can sleep, as long as that music app is the one that's up when it shuts off, and it'll keep playing. I can sit at the home screen, and it will die. It will die if I switch apps, to run Talk, or the browser, or Mail, Market, anything other than Music (or any music app, I've tried them all, it's not a specific app problem.)
Checking the log via logcat shows an entry from the ActivityManager class killing the PID of the app, then immediately restarting it. If I'm watching it when it happens, the music stops, and if there's a status bar icon for the player (such as Music, WinAmp, or PowerAmp) it disappears for a moment, then reappears, on the same track, but reset to the beginning. I suspect this is because the current track is cached/saved somewhere but the position is not when the PID is killed. Oddly enough, the app must be considered to be in a "crashed" state because of the instant restart a second later.
As I said, the tablet is 100% stock. When I got it (early August, I think?) there was a single update that immediately applied. Then I got the latest 8.6.5.9 US update what, a few weeks ago? That's all that's been done as far as the code that's running on it. No root, ever, no custom ROMs, nothing.
I suppose I should do a factory reset and see if that helps. I just hate having to set everything up again without a backup (which I obviously don't have, not rooted.)
[Edit: I should add that the music player isn't the only app that ActivityManager logs kills/restarts on. logcat is full of them.]
Factory reset last night (VolDown while powering on, select "reset," so this was a full wipe) and it's STILL DOING IT.
Sent from my Transformer TF101 using xda premium
hm strange, maybe there is an issue with your music library that crashes the music player? file corruption during transfer, maybe?
or some app your recently installed is not 100% Honeycomb compatible and makes the Activity Manager go nuts.
d3l1 said:
hm strange, maybe there is an issue with your music library that crashes the music player? file corruption during transfer, maybe?
Click to expand...
Click to collapse
I've wiped and re-copied the music files several times. Also, as I said, if I keep the music app active (foreground) it plays forever, no problem.
or some app your recently installed is not 100% Honeycomb compatible and makes the Activity Manager go nuts.
Click to expand...
Click to collapse
I wiped back to stock with no apps and it still does it.
No, I actually did some more research yesterday, involving BTEP and staring at the output of "top" for an hour or two.
Warning: Linux babble ahead --
It seems that ALL the background apps will respawn at the same time. So, when Music drops and restarts, the com.google.android.music process is not the only one dying, pretty much anything running forked from zygote, except for the following exceptions: system_manager, com.android.systemui, com.nuance.xt9.input (part of the Asus keyboard,) com.android.phone (with wifi only, why is this running?) and com.google.process.apps.
You can tell when all the application PIDs are grouped tightly together, in the range of a few hundred, that some event is forcing a mass kill and refresh of the apps, except, curiously, if the app is running in the foreground. So there's at least some logic involved in whatever's doing it, and not simply a kill -HUP `pidof zygote` or something like that. (I don't even know what that would do, heh.)
While monitoring top I didn't notice any processes with extreme CPU or RAM usage. Everything looked fairly well behaved. The system had plenty of memory available at all times. I checked dmesg for any kernel errors, nothing at all to indicate a failed read/write or any other type of hardware error.
Since what I'm looking at is basically a Linux system (and I troubleshoot this sort of stuff for a living) I'm trying to dig into it from that angle first. If I can find out WHAT is causing the mass process kill, then I can hopefully have a better idea of WHY.
Sometimes I hate computers.
anyone else having issues with poweramp? works great for a couple weeks, then nothing seems to make it better. i end up flashing a different rom and the problem goes away for a couple weeks. currently running a ported rom. doesnt matter whether i'm on froyo unrooted/stock, rooted, gb port, or gb official release.. cant seem to figure this one out. i've always restored app only, never restore app data. and i have tried removing and installing a fresh version straight from the market..
when this happens it sounds like a cd skipping and the ENTIRE PHONE freezes. it can happen with the screen on while using the phone or with the screen off playing music through the headphone jack. i've tried different voltage settings and profiles, thinking that maybe im UV too much.(but the phone doesnt freeze any other time) when this happens the ONLY way to fix is to pull battery. none of the buttons work, capacitive or external, and the touch screen is completely unresponsive. this is driving me crazy. last night i tried clearing app data and it made no difference. this does not happen with ANY other apps.
ANY IDEAS?!
Did you try emailing the dev?
I've been running PowerAmp with Voodoo on Emancipation for awhile now without any problems. Have you tried any other music player to see if you get the same problem?
Sent from my Blue Emancipated Infuse using XDA
i have not used any other music apps, but i can tell you that this is the ONLY app that crashes the phone. the only thing i didnt like about gb custom roms was that my sms app(chomp sms) wouldn't sent messages sometimes at all, and the stock sms app was intermittent.. ported roms were better for me. and everything force closes on froyo.
Anyone else have issues where poweramp won't see the tags for several songs resulting in them not showing up whenever i go to the library? Some of the albums are missing songs and some entire albums don't show. I can see them without issue in other music players and I can see them in power amp if i browse by folder but they don't show up in library.
Never mind, found them under unknown artist and just manually changed them.
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?
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.