I know there have been multiple threads on sleep issues but I haven't found one like this one.
My phone is able to sleep but only for a certain amount of time. It seems that after I reboot my phone, it can sleep appropriately for the first 8-12 hours and the battery life is amazing during this time and only drops about 20-30%. Up time verses awake time also reflects this. However, after about 8-12 hours, the phone stops going to sleep and the awake timer never stops running. This will drain the remainder of the battery in about 10 hours. After a reboot, the phone is able to sleep again until it develops insomnia once more. Does anyone know what could be causing the phone to stay awake only after being on for several hours? I'm rooted on the stock firmware with the latest OTA. Only extra programs are Google Voice, ePocrates, and Slacker Radio.
*#*#4636#*#* was no help in tracking down the culprit. Spare Parts contributed pretty much nothing either.
Mine did this for the first time yesterday. It's hasn't done it since, but it was very weird. I checked the sleep settings and it was still set to 1 minute, but the phone would not turn itself off.
Probably an app
Same Problem...
I have tried every thing to solve this issue. Change phones; problem return. No apps other than Stock; problem returns. Syncing Exchange, Facebook, and HTC Facebook. Custom Ringtones seem to increase the speed of the error occurrence. Tried leaving them off, but the problem returned. I have changed SD cards. reformated the card, and started it fresh. I have done a factory reset between each test (at least 8 at this point). I have a suspicious that it is the contacts that are getting corrupted, but I have not been able to verify that theory.
Mine has only done it on one evening and not since.
So since I have switched to this phone from my previous Galaxy Nexus, randomly during the night Slacker radio will start itself even though I had not used it that day. Ill take my phone when leaving for work and slacker keeps it awake 100% of the time. I will usually notice around lunch when I have unusual battery drain, and its the culprit with 100% awake time. I do not use / have enabled the caching functionality so I am not sure what is causing it to start itself. This has happened on both Jedi and Clean ROM, clean installs on both. This has never happened on my previous android phones. Anyone else encountered this / suggestions for a fix?
Thanks!
Nothing to do with the phone, it's Slacker radio bug. This crap has been going on since...well, at least 1.5 years now:
http://forums.slacker.com/viewtopic.php?f=186&t=9546
I've seen a number of other posts with similar issues, and most suggest that there may be some corrupted data that the media scanner is attempting to pick up on. I have done a complete system wipe, and am still experiencing the same issue. I will attach a couple of screenshots showing the issue, but as of right now, the phone being on for 1 hr 7 minutes, Mediaserver has kept the phone awake for 53 minutes. I have not opened any media playing applications (Play Music, etc) - it basically kicked off within a few seconds after bootup.
I am currently running PA 3.96, but with the bizarre issues I've been running into lately, I am considering reverting back to stock and giving up on the custom ROM thing entirely. If anybody has any suggestions on the Mediaserver thing, I'd be very interested.
Thanks!
[deleted]
Rodya234 said:
Is NFC on? That happens to me when I forget to turn it off.
Click to expand...
Click to collapse
Hi Rodya,
Yes, NFC is on, but there is absolutely no reason why having NFC on should cause that issue, otherwise it would be completely useless. I have always kept NFC on, and it's only in this most recent iteration of PA that I have started seeing this issue. If that's a legitimate issue within PA 3.96, then fine, I can revert to a different ROM and that's fine.
At some point after I originally posted this, Mediaserver stopped acting up, and my battery stabilized around the 77% mark without any intervention from me. I am extremely confused here, but more and more convinced it's time to go back to stock so that I can at least get back to a usable device again. Makes me a little sad because there are lots of very cool features in PA, particularly the per-app DPI, per-app color, and PIE / fullscreen mode.
So weird Issue.
Using Google Maps on MaximusHD 6 with the latest t-mo firmware (2.11) I get constant "GPS SIGNAL LOST" when obviously driving and using it as my nav since I got it. I'm in southern California with a pretty good LTE signal almost everywhere. The highways are pretty open so trees, mountains, buildings etc are ruled out as a probable cost.
Now today I noticed that I normally keep the phone locked/screen off when driving since it's connected over BT so there's no real need to look at it. During a normal 15-20min drive I would get the signal lost alert a lot. Upwards of 10 or so times on that single drive. While with my M8 it never happened especially when literally not 5min after getting out of the parking lot doing maybe 20mph down the street. I first I thought i messed something up since I took the phone apart to apply thermal paste to keep it from overheating.
However today on a drive back I kept the phone with the screen on. Never did it lose signal while the screen was on, but a minute after I locked the phone (screen off) did it lose GPS signal. I turned it back on and after driving 20min or so the signal wasn't lost.
So overall has anyone experience a similar issue? Full cellular coverage with frequent google maps alerts that the GPS signal was lost. Maybe a background gps process being killed or another coming up and hindering it.
Gonna wait for the Thanksgiving break to mess around with stock/custom roms and see if it's just something that can be fixed with a reflash.
I'm having the same issue, have you figured anything out? Have you tried using a different app besides google maps to see if it's the actual app doing it's power save feature, or the background powersaving process being started by the phone being screen off? Really interested because my phone starts burning up to extreme temps...
On the backup I had with the issue I narrowed It down to possibly a background process cutting it off once the screen turns back. Power saving was off and all that would stick while screen was off was maps, Google service, and social apps.
As for the cause I couldn't figure it out. I went with a stock from without issues. Then went back to custom roms and haven't had the issue again. Also I drastically lowered my app count. Barely use any apps not needed for basic functionality.
As for the temp issue you're having. I noticed gets warm just like any other device when using GPS. I have opened up the phone and applied a new thermal coat following off a thread around here.
I have another issue came up where the phone would seek out a GPS signal while battery saving was selected to even location turned off. Killed my battery in a heart beat. Hasn't happened again.
I would suggest you make a full backup and either flash a stock rom or redownload whatever custom rom your using. Do a trial run for a day or two with minimal apps and see if it improves.
Here's where it gets interesting..
I used to own a galaxy s3 i9300 and custom kernels caused exactly the same issue. Flashing a stock rom solved it and a few other issues, one in particular was gps inaccurate coordinates.
Now I have moved to an m9. This has in the past run great. It is completely stock and untouched by curious fingers.. However, recently my gps has been running at random intervals even though it is completely off in all accessable settings. I can't find the culprit and it sapped 40% in a few minutes. It was literally a short face to face conversation, jumped back in the car and went for my phone for waze.. Dead as a dodo..
Confuzzled completely as to whether this is the actual rom doing it or an app..
I wish I stole my HTC M9.
shivadow said:
Here's where it gets interesting..
I used to own a galaxy s3 i9300 and custom kernels caused exactly the same issue. Flashing a stock rom solved it and a few other issues, one in particular was gps inaccurate coordinates.
Now I have moved to an m9. This has in the past run great. It is completely stock and untouched by curious fingers.. However, recently my gps has been running at random intervals even though it is completely off in all accessable settings. I can't find the culprit and it sapped 40% in a few minutes. It was literally a short face to face conversation, jumped back in the car and went for my phone for waze.. Dead as a dodo..
Confuzzled completely as to whether this is the actual rom doing it or an app..
I wish I stole my HTC M9.
Click to expand...
Click to collapse
Android 6 should be released around here soon so maybe that'll improve/fix these issues. I wouldn't be surprised if Google services is causing this since it has in the past drained batteries and causes similar issues. If the kernel is involved then the issue has been seen on both stock and custom.
well it may be a setting from the maximums HD, try using other Rom and tell us if problem is solved, try HD Revolution or ViperOne.
Hi all, I got a Moto G3 and having issues with the gps no signal message, it is on and off, but more the time that have no signal. So have heard that Android 6 could be the guilty one.. Do any of you know if there is a fix yet? ?
Enviado desde mi Nexus 7 mediante Tapatalk
I have searched as much as I can, but can't find any info on this. It has happened on both mine and my wife's M8, but only after updating to Marshmallow. If the phone dies suddenly without being able to shut down fully most of the time it will lose certain settings, like sounds, data and Wi-Fi turned off, saved Wi-Fi networks gone, etc. If it happens while starting up it has lost whole apps, all contacts; mostly acting like a first boot but some installed apps, settings, call history, text messages, etc did remain. Any ideas?
zenisnotchosen said:
I have searched as much as I can, but can't find any info on this. It has happened on both mine and my wife's M8, but only after updating to Marshmallow. If the phone dies suddenly without being able to shut down fully most of the time it will lose certain settings, like sounds, data and Wi-Fi turned off, saved Wi-Fi networks gone, etc. If it happens while starting up it has lost whole apps, all contacts; mostly acting like a first boot but some installed apps, settings, call history, text messages, etc did remain. Any ideas?
Click to expand...
Click to collapse
I spend the same, and also turns off me having 20 % battery....google traslate, sorry.
I get the exact same issue, but no idea why it happens :/
Sent from my HTC One_M8 using Tapatalk
It's a glitch with HTC's Marshmallow version. It happens on stock as well as custom ROMs. Nothing to do but wait for an update from them, or always make sure your battery stays charged. It happens to me at 6%
Same Problem but phone dies at 20%-30%
zenisnotchosen said:
I have searched as much as I can, but can't find any info on this. It has happened on both mine and my wife's M8, but only after updating to Marshmallow. If the phone dies suddenly without being able to shut down fully most of the time it will lose certain settings, like sounds, data and Wi-Fi turned off, saved Wi-Fi networks gone, etc. If it happens while starting up it has lost whole apps, all contacts; mostly acting like a first boot but some installed apps, settings, call history, text messages, etc did remain. Any ideas?
Click to expand...
Click to collapse
I am having the same problem, heaps of settings change, including default keyboard, messaging app quick settings wifi etc
if my phone was dying at 5%i could deal with it but it is dying anywhere between 20 and 30% and often catches my unawares.
An update to fix this would be great.
Yup, I have the same problem only I don't lose saved wifi networks but I get signed out of every single app. I also get a google play services error which requires me to clear the apps data.
Snap!
I have been having these problems for the past 4 months (running Lollipop)
I thought that the Wifi passwords issue and app logouts was due to low system memory. (battery would die around 15%)
Since doing a factory reset and 2 weekends ago, the battery dies around 25% and I still experience app log outs etc.
My device is close to the 24month warranty limit and I need a fix urgently.
I also have Bluetooth call random clipping happening both on lollipop and Marshmallow.
This is killing me. Any fixes yet?
Lately it's been losing home screen icons and a couple settings even when I manually shut the phone down. Ironically yesterday when it died suddenly some previously missing icons I had yet to restore reappeared.
please!! any Fix ???
Any fix??? My phone does this too, and its becoming more often than a weekly thing now
A few times now manually shutting the phone down before the battery dies has led to all Google related icons (Chrome, YouTube, Play Music, etc.) being removed from my home screens and having to manually re-add them. When the battery dies it's a roll of the dice what, if anything, will be changed/lost.
In addition to almost everything already said RE: most customization is lost, apps and widgets disappear on restart, etc. I've noticed that all of the (mostly AT&T) apps that I disabled are enabled and updated when the phone comes back on! This is so annoying and is my first major problem with this phone! It's taking time to have to redo all my settings each time the phone dies!
Same problem here very annoying especially as I have to phone bank to reset my mobile banking app as it screws the settings in this. #leaveitoncharge
Yesterday mine died at 30%, and upon restarting it went through the "Optimizing Applications 1 of 261" then proceeded to come up with a warning that the phone had an internal error and might be unstable until doing a factory reset. After clearing the warning it was stuck in a "Sense Home has stopped working" loop until I could get into Settings and clear the data for Sense Home. This allowed me to at least make sure things were backed up before doing a factory reset, but more than half of my contacts were missing as well as many text, call history, etc. A similar thing happened with the wife's M8 last week and had to factory reset hers then too.
I had this problem and had my battery and main board replaced in the final month before 24 m warranty ran out.
Do a battery test *#*#3424#*#*
Then hit more, and select battery test.
Battery has to be 100% to complete teat which takes an hour. Do this when you don't need it.
My test would often show 91-94% but I had one that said 71% which I saved a screen shot.
Since the battery and main board replacement it's still my favourite phone.
solve the problem of battery and loss of settings , change the battery of my htc, now everything is fine , 3 days that the battery is discharged properly , I hope this information will help someone.
Not positive I've lost settings, though I'm fairly certain I have. I have lost app permissions many times. And my phone seems to die around 30% and won't let me boot unless I am plugged into charger. I was recently forced into a factory reset due to a message that popped up just like a somebody else a few posts back. This is a recently replaced phone (VZW replaced it as the prior had battery problems). The prior one did not do this. I hope HTC get's their act together and fixes the issue. Highly annoying.
Ive been having this issue since the beginning of the year and now it seems to happen every few days. I pretty much don't have a choice but to buy a new phone at this point, which sucks because I love my m8.
This is exactly the same issue I've been having. I'm at my wits end with having to re-do all of my settings and apps daily, and sometimes (randomly!) it won't hang onto a charge for more than a few hours even if I'm barely using it. I basically have to leave it on a charger all the time to keep it from shutting down and losing all my settings! I used to love my M8, but for the first time ever I'm considering swapping to a Samsung just to get away from these issues. I've had this phone for a little over two years and these problems only just started around March 2016 - but they've been an absolute constant since then, and only getting worse.