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?
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.
I have an N910F with Android 4.4.4, a few weeks old.
There are two issues that annoy me, perhaps they are related.
1. Sometimes when I get the phone out I find that it hasn't gone to sleep after the last use. There doesn't seem to be any one app that is keeping it awake. As a test I've been making a point of closing all apps, but even then it sometime stays awake.
2. Sometimes when I check Active Apps and Data Usage I find that Google Play Music, Google Play Movies and/or Evernote have started and used data. I don't use any of these and have stopped them all several times in Application Manager, but they just start up again at random.
Can anyone suggest how I can stamp on these problems please?
Thanks!
So I installed cm-11-20141115-SNAPSHOT-M12-mako.zip about two weeks ago on my Nexus 4.
Ever since, my phone randomly powers off, maybe every second or third day. It does not seem to be connected to the use of any special app or something.
And it only seems to happen when the screen is off. Never experienced the crash "live".
Any ideas what I could do? Is there an error log I could read out?
I rather like the OS, so I want to avoid going back to stock android, but this is something that's not tolerable.
The only thing I "modified" in the OS is to deny the google play service to send keep awake requests, due to the known battery drain bug.
I tried several other solutions before, but this was the only one that helped. Otherwise my phone was basically unusable and did not even last half a day with very basic usage.
Help is much appreciated.
I'm having the same battery drain issue with the latest snapshot from cm11. How do u fix this drain that is caused by checkin service?
I don't know about any battery drain that's caused by the checking service.
My battery drain was caused by the google play service. I solved it by denying keep awake request in the privacy settings menu. I can't tell you if that works for your problem as well...
Hi all,
Having a problem here.
Had my N9005 for about 18 months, never really had any problems with it - or rather, never really required anything of it which might manifest any problems.
I've always used Stock ROM's, soft-rooted.
Never triggered KNOX.
I'm currently running Stock Lollipop (latest Switzerland Open). Everything I'm about to elaborate is also the same using Stock Lollipop (latest UK Open).
I'm rooted on Lollipop using the method compiled by The TAMAS on XDADEV.
I root because my phone is work-critical, and so I use Titanium Backup to keep my data/calls/APN/SMS backed up and to make restoring easy, as well as to disable stock bloatware etc.
The problem may have pre-existed in pre-Lollipop ROM's, but the sequence of changes which caused it to be manifested included my need to update to Lollipop, about 5/6 months back.
THE PROBLEM - First and foremost, the damn phone reboots randomly. I become aware of it because it will vibrate for startup and play the Samsung startup tone and splash screen before booting to normal functionality. It can do this day or night, maybe 3-4 times a day. I have no error messages or warnings, it's done it while in my hand, while plugged in charging, while out and about, in the car, on wifi, on data. MOST times it reboots. SOME times it just shuts off and I don't realise it's off until I go to use it, or get a call on a second phone to ask why I'm not responding to calls or messages.
When it reboots itself, if I go to the Samsung Battery control panel pane and take a look at the battery chart it will show a gap which is longer than the time it took to reboot, and a shift in the battery meter level.
But, that's not the only possible symptom or problem with the phone.
I've noticed also that my WIFI does a lot of crapping out, or slowing to a crawl, even on my home AP. I've reset AP's, reset networks, reset the phone, forgotten and then reattached the AP in WiFi Settings. So I downloaded the Ookla Speedtest App, to see this issue in black and white, and sure enough, even though any other Android or iOS or Windows or OSX device in my place can connect via Wireless AP to my fibre connection and get great consistent throughput, the Note 3 can often appear crippled...
At it's best, it responds to ping quickly on the Speedtest app, and leaps up to the 30-40Mbps range with consistency for download, and up to 17-20Mbps for upload. This is the least I would expect it to do, my target standard.
At it's worst (which can be 'most of the time') it responds slowly to ping, and either struggles to get over 250Kbps download and maybe a crazy Meg or two for upload, consistently, a slow grind; or it may oscillate extremely wildly between slow and high speeds before eventually settling to unacceptably low transfer rates.
Up to press, I've been trying to chase these problems in isolation, believing them to be unconnected.
No success.
I've reflashed several times. I've Factory Reset. I've wiped data and cache. I've reinstalled and restored from Titanium. I've reinstalled and restored nothing but my SMS's and Call Logs. I've reduced my installed apps to bare minimums. I've tried it with a MicroSD installed, and without. I've bought another battery and replaced it. I've tried it in its case and without its case.
Then I started thinking that the problems were all the same thing, and stemming from the same root.
It suddenly occurred to me that my use of the phone changed significantly at the same time as I moved to Lollipop.
I need to be on Lollipop because apps and hardware that are critical to me are Lollipop dependent.
All at the same time, I began using a Moto360, a Bluetooth Receipt Printer and a Bluetooth Credit Card Reader, all of which are deficient in functionality or in some way hamstrung by not using Lollipop.
So I had gone from occasional BT user (maybe PlayerPro plus a BT link to headphones or my stereo occasionally; when needed, BT speakerphone in car) who usually turned BT off manually to preserve battery life, to a constantly connected BT user...
So I went back to Speedtest app, and tried to test the WIFI connection again. Sure enough, it was pitiful. Then I simply disabled BT on the N9005 and ran the test again, and had full 'through the roof' speed ratings.
I've tried this back and forth hundreds of times now, and it is predictable and established. BT is somehow crippling WIFI on my N9005.
I've tried running the phone on either wifi or data only, with BT off, and had a couple of days use at a time without any restarts. Put BT back on permanently, and the restarts resume within hours.
I'll be honest, I've even been cursing and swearing at my BT devices, because BT sometimes struggles to even maintain a continuous connection. I get vibrations all the time on my Moto360 indicating that the phone, which is on my person, has disconnected from the watch again, perhaps just for moments, sometimes for minutes, resulting in the watch eating battery life, trying to get reconnected.
I'm convinced now that all these things are related, and the problem lies somewhere in the interaction between BT and WIFI in my N9005.
It seems likely that I never noticed the problem before because I never required continuous BT connection before the point where I installed Lollipop.
Downgrading the ROM isn't an option. Leaving BT off isn't an option (nor should they have to be, on an 18 month old £600 smartphone).
Does anyone else have experience of this? Has anyone else had problems that they now suspect might be this same problem? Does anyone understand what's going on hardware/software wise, or have experience of a solution to these issues?
I'd appreciate your input urgently, even if only to affirm that I need to go to the inconvenience of temporarily buying another phone to replace this, while I send this away for a warranty repair.
Is this even a recognised hardware fault, or would I just get back an identical unit which is crippled from being able to perform as I expect it?
Please help.
My stock S7 exhibits random reboot behavior. 1-2x per week. Once in a while it happens 2x in one day. Once it a while it happens at the most inopportune time, like when I'm trying to take a picture of an event. When the reboot occurs usually it boot loops several times (and the phone gets warm while this is happening) and then finally stops. For the first year or so of owning the phone, no reboot problems. I did see the unmounted SD card notification issue that others reported (with a Samsung SD card). A while after the nougat update and after the 1 yr warranty period of course....random reboots. Also after the boot loops stop and I'm able to use my phone again, my Spotify login is lost and I have to re-download my playlists that I had saved locally. This is a real PITA if I'm traveling and not near any wifi connection.
Any ideas?
I've done the following:
- factory reset twice
- removed the SD card, not using it anymore -> I could consistently get the phone to reboot when scrolling through my pics in google photos. I do not get this behavior anymore with the sd card removed
- install a minimal amount of apps
I've read countless search results from Google search results and nothing has solved my problem. I'm past the 1 yr warranty period. I called a local shop and was told the cost of replacing the mainboard pretty high, I'm better off just getting a new phone...which I would like to avoid. Today I disabled the built in weather app to never refresh. I have little hope that this will fix my problem, we'll see.
I don't have any launcher apps. No games. Basic apps like Bank of America, Evernote, Flixster, Spotify, Swiftkey, Todoist, Logitech Harmony, etc. I disabled the built in Amazon app and installed the Amazon app from the google play store.
I have the same problem. Also after almost 1 year I am now getting random reboots. Especially but not exclusively uwhen using google maps. Mine is still under warranry.
Update: did a factory reset via recovery, working fine again.
Overnight while charging, my phone decided to bootloop until the battery died. Woke up to a warm phone that would not power on for about 20 min. I put the phone on a gel ice pack and now it's finally on. Uninstalled and disabled a bunch of apps, always on display, bluetooth etc. Just need this thing to stay alive until I can trade it in for the new Pixel.