Related
Anyone have any idea what may have happened here?
I was unexpectedly away from home, but using the device quite heavily, and didn't have a method to charge the battery.
Once the battery had drained to about 3%, I switched the phone off but I ended up needing to make another call. The phone booted, but all core apps returned a force close message. Phone, Maps, Google Account, all the main stuff... Other apps would launch and function with no problem though.
Thinking it may have just been a glitch, I rebooted the phone again thinking there would still be just enough juice to allow a phone call, but while booting, the battery totally failed.
Once I had a chance to plug in the charger, all core apps continued to fail, even though the phone now had plenty of power.
Even after a battery pull, the same issues continued, rendering the phone pretty much useless. No link to Sprint, no WiFi network, nothing...
The phone is rooted with v1.5.2 RC and Fresh ROM v1.0, so lacking anything else to do, I performed a Nandroid restore from a backup made about 2 days ago and that seems to have fixed up the problem. (whew.. I did not want to resort to the RUU)
But, I just can't figure out what may have caused this odd behavior in the first place....
Are you using apps2sd?
No, I'm not using the apps2sd feature.
The lockscreen text showed "No service" and the notification bar icon showed the same. The "phone" application was the only one that would attempt to restart after being forced closed. After a second fc though, it would apparently give up.
Oh, and just remembered one other oddity.. Once booted and all force close messages removed, attempting to turn on the mobile network resulted in a hard reboot. I really didn't expect anything since there was no service link, but I was just clicking various shortcuts to see what did or didn't work.
Good part is that a Nandroid restore saved the day, so it's more of a curiosity at this point to what the root cause might have been.
I wouldn't have thought that a battery drain could have corrupted the apps or prevented the root filesystem from mounting.
You probably had too many apps installed. It's a known issue with the Hero, where having too many apps installed causes a bunch of core apps to fail to load for no apparent reason. The phone losing power just caused it to reboot, which triggers the issue.
mkhopper said:
Anyone have any idea what may have happened here?
I was unexpectedly away from home, but using the device quite heavily, and didn't have a method to charge the battery.
Once the battery had drained to about 3%, I switched the phone off but I ended up needing to make another call. The phone booted, but all core apps returned a force close message. Phone, Maps, Google Account, all the main stuff... Other apps would launch and function with no problem though.
Thinking it may have just been a glitch, I rebooted the phone again thinking there would still be just enough juice to allow a phone call, but while booting, the battery totally failed.
Once I had a chance to plug in the charger, all core apps continued to fail, even though the phone now had plenty of power.
Even after a battery pull, the same issues continued, rendering the phone pretty much useless. No link to Sprint, no WiFi network, nothing...
The phone is rooted with v1.5.2 RC and Fresh ROM v1.0, so lacking anything else to do, I performed a Nandroid restore from a backup made about 2 days ago and that seems to have fixed up the problem. (whew.. I did not want to resort to the RUU)
But, I just can't figure out what may have caused this odd behavior in the first place....
Click to expand...
Click to collapse
oddly enough I've had a similar experience. it was 2 days before christmas and i was doing all my last minute shopping. heavy use of the phone caused the battery to die, so i just threw it on my car charger. it booted, but REFUSED to get any data at all (i didn't run into any fc's, however). I rebooted it 3 times and each time the issue persisted.
I was running the AOSP 2.0 build at the time, so i flashed my backup of 2.1 and everything was fine from there...
patches11 said:
You probably had too many apps installed. It's a known issue with the Hero, where having too many apps installed causes a bunch of core apps to fail to load for no apparent reason. The phone losing power just caused it to reboot, which triggers the issue.
Click to expand...
Click to collapse
Hmm, good possibility there. Just did a count and I do have 85 apps installed.
(whoof, I had no idea the number had gotten that high. just too many useful apps for this phone.
Hi all,
I'm experiencing an issue on my stock 4.1.1 Nexus 7. The screen seems to be turning itself on randomly. It normally turns off again but may toggle on/off quite a few times. Then it seems to go for a while whitout turning on. Bit odd.
Anyone else experienced this or have any thoughts on a reason for it?
Thanks
Same problem here, except with a Samsung Galaxy Nexus.
I just updated to 4.1.1 today and this is the first time I've seen it happen. Was previously on 4.02 without issues.
I have had the same problem. It seems to happen in the evening and I wondered whether the case was causing it to overheat. Seems to be OK when I take it out of the case. I phoned Google and was told that it hadn't happened before. I will contact them again if it doesn't get any better.
Sorry. Misread the post. Mine goes to sleep, not turns on
Sent from my Nexus 7 using xda app-developers app
gifton1 said:
Hi all,
I'm experiencing an issue on my stock 4.1.1 Nexus 7. The screen seems to be turning itself on randomly. It normally turns off again but may toggle on/off quite a few times. Then it seems to go for a while whitout turning on. Bit odd.
Anyone else experienced this or have any thoughts on a reason for it?
Thanks
Click to expand...
Click to collapse
Same here but mine is not exactly stock.
I have installed Apex Launcher plus numerous apps. I thought maybe it was the launcher doing it. But at this point... I have no idea. Just noticed it tonight coming on and then going off within 1 sec. but its random. it may do it once within an hour, or it may do it up to 5 times within a min... then go several minutes completely black screen. Crazy stuff. I thought maybe it was getting a message at first but then realized I had the WiFi off on my phone so it was dead to any incoming messages/wifi. I am really curious as to what is causing it and will be following this post as well as others quite frequent. Also.... the latest app that I have downloaded was OSMOS HD. it wasn't waking then sleeping before that app... just my 2 cents.
Hi Qbensis,
By stock, I just mean not rooted and not running any custom firmware. I had various apps and the like installed.
I have actually since rooted my N7 and installed a few custom ROMs and since then have not seen the issue at all. If you want to stay stock, I assume the issue will be fixed in the next update
I have seen this a few times. Middle of the night I look over and the screen is on then off. I check the power usage overnight and I see little blips of screen on when looking at the graph. Not sure whats causing it (I figure a app).
Same Problem over here, any solutions???
I'm on stock 4.1.2 and having the same problem, not rooted. Creeped me out in the middle of the night when it goes on and off.
N7 Random Turn On
Same here on 4.2.1. I carry in front pocket all the time with screen facing leg and feel heat when it happens. Has even done it when in Power Off mode and still does it. I thought that would prevent it for sure. Very irritating and drains battery. We Winter in 55+ community and drive around in golf carts. I am starting to wonder if WiFi spots trigger it. Will continue to track behavior and search other forums. Curious that there have not been any solid suggestions or solutions.
Happens to my rooted but stock 4.2.1. It happens randomly when I recharge using a battery pack (4AA) as opposed to charging using regular AC. It's annoying as heck! I don't know how to get this fixed!
I've been getting this on both SmoothROM and raspbeanjelly, and it's very irritating.
It has to be an app that is causing this. I initially thought perhaps it was GPS Status, because I caught it in the notification bar a few times when the screen turned on.
My device definitely isn't hot when it happens.
I'm suspecting the Email app, Maps, or Facebook.
EDIT - not any of them either. I'll test Beautiful Widgets next.
Okay guys, try this.
http://forum.xda-developers.com/showpost.php?p=29420959&postcount=7059
I'd been suffering from this for weeks, factory reset, reinstalled and changed out ROMs, installed apps one by one over the course of several days to keep an eye on what might be triggering it etc. Nothing worked for more than 2-3 days at most, and the issue always came back in one way or another.
It was causing me to have to turn the Nexus off when not in use because it would be draining battery (15-20% overnight compared to 2-3% when the issue wasn't present).
Then I stumbled upon that guide and using Gemini I disabled Maps from auto-running, turned off Latitude, and so far so good.
If it works for you too, be sure to hit thanks on Karpfenhai's post!
I was having this same problem on my Nexus 7 running stock 4.2.2 rooted with SuperSU. Finally tracked it down to having installed BetterBatteryStats and for some reason, I had not granted it perpetual root. It was causing the device to wake and turn the display on for random times (up to 13 hours, which killed the battery), not always showing the SU request dialogue. I granted perpetual SU privilege to BetterBatteryStats and problem went away.
Try taking out the battery and clean out the USB port with a toothpick. This worked for me. All the dust that accumulates in the post can cause the phone to think it's charging.
Just flashed the new MG1 on my SGH-I337M. I am noticing a consistent high partial wakelocks with GCM_LIB. Almost completely stops deep sleep. I just removed each of my google accounts and readded to see if that fixes the problem.
Anyone else experiencing this anomaly?
Cheers
R0N1N said:
Just flashed the new MG1 on my SGH-I337M. I am noticing a consistent high partial wakelocks with GCM_LIB. Almost completely stops deep sleep. I just removed each of my google accounts and readded to see if that fixes the problem.
Anyone else experiencing this anomaly?
Cheers
Click to expand...
Click to collapse
+1
Carried by a Raven
mrnovanova said:
+1
Carried by a Raven
Click to expand...
Click to collapse
+1! Something I did/installed/modified in the last week since I got the phone made the battery life plummet. Thought it was the "listen for wake-up command" part of S Voice... better, but nope. GCM_LIB had it awake 7 1/2 hours out of 8 I slept last night. This morning removed Samsung acct to see how that goes. Next the google acct...
I have the exact same problem as the OP, same phone/model too. Any clue what this "GCM_Lib (Android System)" under BetterBatteryStats is? It is preventing the phone from going into Deep Sleep. I notice this GCM_Lib is only active when there is an active connection (either WiFi or Mobile Data) turned on. With Flight Mode, there is no excessive battery drain. I am losing 15% battery over night (6-8 hours sleep). With Flight mode, I am only losing 1%.
I have removed all accounts off my device, and GCM_Lib is still wrecking my battery usage. Phone is unrooted. Any ideas?
I had the same problem on my SGH-M919V, upgrading firmware from MDJ to MG1. Same symptoms about suddenly poor battery life during sleep, and constant GCM_LIB wake locks. In the end, I never did figure out what was causing it, or a good way of fixing it, however I did end up solving the problem indirectly.
I flashed my phone back to the old MDJ firmware (NO data wipe, just firmware only), to check if I was getting the same problem previously, without knowing it. Sure enough, the problem went away, and didn't happen on the old MDJ firmware. So next, I re-applied the new MG1 firmware (again, NO data wipe, just firmware only), figuring that I would systematically disable/uninstall everything, one thing at a time, to try and figure out what app, account or setting was causing this. However, as soon as I re-flashed the new MDJ firmware, the GCM_LIB wake lock problem never re-appeared afterwards.
I don't know if this was something uniquely corrupt or misconfigured with my accounts or phone settings, or something unique to the SGH-M919V phone or firmware, but oddly enough, the firmware rollback & upgrade process described above did somehow fix the problem for me. I'm not sure if this process of firmware rollback without data wipe is supported or recommended without causing other issues along the way. I haven't other any other issues as a result of doing this. But still, make sure to have a full backup of your phone before you start, just in case something goes wrong during the process or some time afterwards.
Having the same issue here, don't know what causes it and how to fix it. I tried killing all the process with the System Panel app, it fixes the wakelock for a moment then it starts again
I have researched this topic, and haven't found an actual match for it.
I have a Google Nexus 4. My phone is rooted, running stock ROM, and Android 4.2.2. Recently I've been having random battery drain issues. More than once I've taken my phone out to make a call and found it as warm as if I'd been streaming audio, running the GPS and navigating. On one occasion, I pulled my phone out to make a call and discovered it was already quite warm; upon rebooting it I suddenly had a several hours-old emails, a couple of texts and a voicemail from a call I never received. I use this phone at work, and if this issue is causing normal operations to fail, that is completely unacceptable.
I run my phone with minimal services; normally wifi, gps bluetooth and pretty much anything else I don't need at the moment are disabled. The only ongoing processes I have running are K-9 mail checking for email every 15 minutes; the only widget I have is for weather, which updates when I unlock my phone. Normally I get really good battery life, even during periods of heavy usage. A recent 4 hour phone conversation only dropped the charge by 25%. However, when this issue is active, the charge can drop that much in less than an hour doing nothing. If it happens when charging, the charger barely keeps up or loses ground.
I have determined that Download Manager or more likely something that's invoking it is the issue. If I manually terminate DM when I'm having this problem, my power curve returns to normal, and I'm able to recharge at a normal rate. I've never yet had this issue while DM is disabled. Disabling DM also results in the error message "Unfortunately the process com.google.process.gapps has stopped" showing at boot and at random other times, which tends to get a bit annoying.
Google Play uses Download Manager and also starts itself periodically, so some of the error messages are likely from GP, especially at boot. However, with DM enabled and GP disabled, I still have the drain issue, so GP isn't what's causing it.
What exactly is it that is invoking Download Manager, and more importantly keeping it running full-bore for extended periods? Does anybody have a list of what processes invoke Download Manager and under what circumstances, or any idea of what might be going on? I'm hoping to identify the actual root cause of this problem and resolve it without other adverse consequences.
I have sync enabled for "backup my data", app data, calendar and contacts, and these do not appear to be affected by disabling DM since the manual sync will still work with no errors with Download Manager disabled.
I have the following processes/apps disabled, so I also think they can be ruled out:
Chrome, Currents, Gmail, Google Korean keyboard, Google Pinyin, Google Play Books, Google Play Magazines, Google Play Movies & TV, Google Play Music, Google+, iWnn IME, iWnnIME Keyboard (White), News & Weather, Picassa Uploader, Sound Search for Google Play, Tags, Talk, and Wallet.
Any help or advice on this would be greatly appreciated.
having the same issue on CM10.1 stable DM runing for a while in random way
disabled DM and getting same gapps errors.
Nobody to Answer?!?! Admins!
i also am used to engage whit DOWNLOADMANAGER service running in background taking pretty cpu and battery on both my phones this happens on boot or right after managing files(rename cut paste etc...)
whats the relationship between filemanaging and DOWNLOADMANAGER while being offline ? dose the process trigger the media scanning ? it keeps running for even hours till phone gets warm!
my phones both rooted:Xperia mini GB and Xperia go JB
my cpu monitoring app is usage-timeline
excuse my bad English
Nobody to Answer?!?!
Nobody Answer?!?! Admins!
please...
android 4.2.2..
sounds like your phone is constantly downloading updates to your phone(but cant apply because of your root/modded situation). what you should do, because of your 4.2.2, is update your phone or itll keep happening. there have been a MASSIVE amount of bug fixes since 4.2.2 which you arent letting your phone get.
simms22 said:
android 4.2.2..
sounds like your phone is constantly downloading updates to your phone(but cant apply because of your root/modded situation). what you should do, because of your 4.2.2, is update your phone or itll keep happening. there have been a MASSIVE amount of bug fixes since 4.2.2 which you arent letting your phone get.
Click to expand...
Click to collapse
Are you with me?well,i dont think so bro!
phone itself and also pc companion say your device is up to date(4.1.2)
i have exprienced this on many Xperia devices i had by now ,and as you see i had explained that this usually happens just after i finish opening, modifying ,renaming and copying/moving files with any type of file manager or gallery apps and such.
i m going to get assured that the process DownloadManager has relations and interactions with MediaScanning process(at least in Xperia devices). it warms up the device and drains my battery, i have to charge my devices every 6-10 hour's.
im so obsessive about my device behavior,may somebodies else having this issue but nobody minds ever like me.
so plz be more patient reading noobies posts like me
somebody help for God sake!
i thank you in advance
Reporting similar problem (no answer here)
My nexus is already in 4.4.4. There's no more update that can loop DM currently. Yet, after I travelled to Italy and back, battery drains irregularly. Today, I save a .mp3 file from an email from hotmail.com. the download loops for over 50 times before I reboot the phone. After restart, the loop continues. I enforced stop from DM. can we delete Download Manager and replace it by other apps?
Thought I would share this here - though I believe this is effecting other Moto models as well.
The Moto app "CQATest" seems to be the culprit with major instability issues I've had since the Android Marshmallow update. Before the update, my phone was so smooth and fast. Then the update came, and I blamed it on Marshmallow. Screen response to anything was very slow. Sometimes completely unresponsive. If i tried to touch a notification in my notification bar, it might be 5-10 seconds later before anything would happen, and the app would open. Sometimes it wouldn't ever open at all. Or when Facebook did open, it might take another 10-15 seconds before it went to the item it had notified me about. The camera in particular was slow to respond - with visible lag whenever trying to take a video - or would just crash. The phone itself got into a fairly normal habit of rebooting itself several times a day. And on startup, sometimes it would take 3-5 minutes before it would finally get to the home screen. Simply unacceptable.
So yesterday I started Googling for answers, and ran across a thread on Android Forums talking about issues people were having with CQATest. I immediately went and found the app in the settings>applications menu, under "All Apps" - force stopped and disabled it, then rebooted.
Guess what? The phone boots normally again! And the general responsiveness and functionality are back to what it was prior to the Marshmallow update. I couldn't be more pleased right now - because I was getting very frustrated with what is a relatively new phone.
I'd be interested if others have experienced something similar? Or are having similar lag issues and try this solution to see if it works for you.
Mods - if this CAN be confirmed, it really should be shared with ALL Moto users who've been upgraded to Marshmallow and have similar issues. The Android Forums thread user was originated by someone on the Moto X for instance.
Thanks for your time and feedback.
Do you have any misbehavior since you've disabled CQA Test? Like something doesn't work... Are you getting better battery life? I think you should.
I have Moto X Force, didn't touch app and system is smooth, stable with great battery life. I suppose you have Turbo 2.
No apparent issues with anything else since disabling it that I can see. And yes, I'm on a DT2.
Zeljko1234 said:
Do you have any misbehavior since you've disabled CQA Test? Like something doesn't work... Are you getting better battery life? I think you should.
I have Moto X Force, didn't touch app and system is smooth, stable with great battery life. I suppose you have Turbo 2.
Click to expand...
Click to collapse
I have had CQA Test disabled before and after Marshmallow and notice no misbehavior. I also have been using advanced calling since i got the phone on launch day and have never had a problem with the call quality as others have.
CQATest not causing problems on my Droid Turbo(1)
I just got a refurb Droid Turbo on Marshmallow, and I've had others. I was experiencing some of those same issues that you described.... extremely slow boot and shutdown, and lag on launching apps or other screen clicks.
I just disabled the following and was amazed at the speedy boot time and responsiveness:
CQATest
Amazon (old app.... new one is Amazon Shopping)
Connect
Message+ (verizon sms)
Mobile Hotspot
After that first boot, I re-enabled CQATest and have rebooted several times since. It still seems fast and responsive. I've got a boot time of 35 seconds to the home screen, shutdown time of about 10 seconds.
Just to check, I disabled CQATest again, shutdown and started. The times are the same as above. I was hoping to explore the CQA menu, but haven't been able to so far. I've got USB debugging enabled, but not plugged into a computer. I'll look for answers in other threads.
GeckoDad said:
I just got a refurb Droid Turbo on Marshmallow, and I've had others. I was experiencing some of those same issues that you described.... extremely slow boot and shutdown, and lag on launching apps or other screen clicks.
I just disabled the following and was amazed at the speedy boot time and responsiveness:
CQATest
Amazon (old app.... new one is Amazon Shopping)
Connect
Message+ (verizon sms)
Mobile Hotspot
After that first boot, I re-enabled CQATest and have rebooted several times since. It still seems fast and responsive. I've got a boot time of 35 seconds to the home screen, shutdown time of about 10 seconds.
Just to check, I disabled CQATest again, shutdown and started. The times are the same as above. I was hoping to explore the CQA menu, but haven't been able to so far. I've got USB debugging enabled, but not plugged into a computer. I'll look for answers in other threads.
Click to expand...
Click to collapse
My DT2 was suffering from slow-downs for a couple weeks, then suddenly had the random shutdown and power-only-on-charge scenario yesterday. I was getting ready to do a factory reset.
On one of the reboots, I had a notification about CQA test. When I acknowledged it, I got notifications that "CQATest wants to access this," and "CQATest wants to access that." I denied them all and started hunting up this app I'd never heard of. That's when I came across this thread. I disabled CQATest, but still had the problem. I then remembered that the "old" Amazon app had just updated. I force-closed it, disabled it, and now the phone is back to normal. I see no need for CQATest, so I'm leaving that disabled, but I firmly believe that the Amazon app was culprit.
EDIT: I may have typed to soon. The phone shut off randomly twice today, requiring connection to a power cord to bring it back to life. It does, however, remain powered up upon disconnection (for now?).:-/ I did not clear the cache after deactivating those apps, though, so we'll see if that does the trick.
..
Hi there.
Backstory: My DT2 is almost 3 years old. I already had to send it back to Motorola once for a camera issue, but generally I didn't have any major performance issues for the first year and a half or so. Then it started to decline. Namely OS was taking longer to respond, battery life declining. Then when it was about 2 years old it began the random shutdowns. For the last several months I haven't really had the random shutdowns, however, my battery has been pitifully horrible at holding a charge, and it will usually shut down before the battery indicator hits 0%. First it was around 15%, gradually getting worse. Now it often shuts down between 30-40%, especially if I haven't been on battery saver since disconnecting from the charger.
Now today, I ran down my battery within a few hours to about 30% and it shut off, which was not abnormal. However, upon connecting to charger and attempting restart, the battery indicator jumped from 30 up to 40, then down to 4. Got a weird screen before startup that looked like a system error screen and was afraid it was going into factory reset without my prompting it. Pressed the power key once briefly and the phone went into normal startup, but when it turned on, CommServer was stuck in notifications bar and battery indicator was stuck at 3%, similar story to the others in this thread and others.
I disabled the apps suggested by GeckoDad, and so far the phone can operate, but I've had it plugged in for maybe 30 minutes and it's still hanging out at 3%. Was planning to get a new phone soon, but had hoped to wait another month or two... Probably going to head over to Verizon this afternoon to see if they have any suggestions to keep my DT2 alive until I'm able to replace it.