So turned on stamina and have no apps in the exception list, it does not appear to be turning off my data nor my wifi when the screen is off? Also I often get an error Photo Analyzer has stopped working when i turn on the phone. How do i fix these issues? I am on newest stock firmware and am rooted.
Wifi and data is Just completly sleeped. Wifi dont drain battery when screen is locked +1 minute. Sorry for bad English.
Yes after a minute of screen off they are prevented from downloading/uploading data, which is the thing that drains battery, maintaining the connection means you typically get to use the internet immediate when you activate the phone again (no logging on etc.)
Why individual apps cause an error message isn’t really answerable – it happens from time to time, sometimes the app’s developers have made a mistake with an update, sometimes if you restore an app from a back up it doesn’t install properly, there are many other reasons too. Try clearing the data in the app, try re-installing it, try clearing the cache and the dalvik cache, try fixing permissions.
I’ve found clearing the data works the most often, not always – I usually get app errors like this after installing a mod/rom.
slyr114 said:
So turned on stamina and have no apps in the exception list, it does not appear to be turning off my data nor my wifi when the screen is off? Also I often get an error Photo Analyzer has stopped working when i turn on the phone. How do i fix these issues? I am on newest stock firmware and am rooted.
Click to expand...
Click to collapse
Setttings -> wifi -> menu/options from bottom right -> advanced -> Change Keep wi-fi on during sleep -> only on charge/never.
Turbo automatically changes from Priority mode to All when fully charged?
I seem to be having an issue with my phone automatically changing from the Priority mode to the All mode for notifications. This happens every morning (presumably after the phone has finished charging completely) and is REALLY annoying. I always change it to Priority mode indefinitely when I realize that it has switched, but doing this every day has been a pain, especially since I don't want my phone to go off at work. I've tried wiping the system cache, but that hasn't helped.
Has anyone had this issue? If so, is there any way to fix it without doing a factory reset?
IVIax94 said:
I seem to be having an issue with my phone automatically changing from the Priority mode to the All mode for notifications. This happens every morning (presumably after the phone has finished charging completely) and is REALLY annoying. I always change it to Priority mode indefinitely when I realize that it has switched, but doing this every day has been a pain, especially since I don't want my phone to go off at work. I've tried wiping the system cache, but that hasn't helped.
Has anyone had this issue? If so, is there any way to fix it without doing a factory reset?
Click to expand...
Click to collapse
Take a look at the configuration on Interruptions and on the Moto app; after Lollipop update, these two are not getting along really good and they produce some weird behaviour.
Hey all,
I just woke up late today without my alarm going off to realize my phone had went from 100% at 10PM to 0% by 8AM. I've read through a few different threads on overnight battery loss, and determined that the big recommendation is to clear the cache partition. I wanted to ask if you guys have any other major recommendations based on my screenshots and info below, because I'm really tired of having this happen. Thanks!
My settings:
-Wifi, Data, Location are always kept on (Wifi connected to a network)
-HD Calling is on
-Most/all bloatware is disabled
-I use the Edge Clock at night
First pic is from last night, the others are from other nights.
Try turning off location and bluetooth and wifi. It should solve your battery problem. I lose about 3% overnight by disabling things during sleep.
I don't think that would explain the other 97% of my problem. Here's another screen shot
Whats your app usage look like?
Also, if you haven't already make sure to wipe cache. It's always the first step to try to fix issues.
Try this too:
1) Turn off all of the advanced calling features
2) Turn off phone
3) Hold volume up, home button, power button until it boots into recovery
4) Wipe cache partition
5) Reboot
6) Re-enable the advanced calling features.
Ditto. Show us your detailed app usage screenshot
I misspoke in the first post, I don't keep Bluetooth on during the day or at night.
zimgir124 said:
Whats your app usage look like?
Also, if you haven't already make sure to wipe cache. It's always the first step to try to fix issues.
Try this too:
1) Turn off all of the advanced calling features
2) Turn off phone
3) Hold volume up, home button, power button until it boots into recovery
4) Wipe cache partition
5) Reboot
6) Re-enable the advanced calling features.
Click to expand...
Click to collapse
wolferno said:
Ditto. Show us your detailed app usage screenshot
Click to expand...
Click to collapse
Here's where I'm at today (turned off Wi-Fi mid-morning, which has helped a bit it seems) with detail of the app usage. zimgir, I did a cache wipe last week without any noticeable results, but I did not turn off advanced calling before doing that, so I'll give that a shot now and see how it goes.
Make sure to go to advanced wifi settings and disable search for signal during sleep. Even though you turn off wifi, this setting usually persists.
This is my wifi setup, I disallow any automatic scanning.
(It's the fifth item down.)
Also can you show us the details of your Android processes? It's very odd that it's using so much of your battery. I've only had that sort of usage when I encrypted my phone. I don't do that anymore since Samsung Pay won't work with encryption.
I've gotta ask, did any of the steps help you out?
zimgir124 said:
I've gotta ask, did any of the steps help you out?
Click to expand...
Click to collapse
It doesn't seem so, my app usage is still very high. I'll post pics of the Android System process details later today.
wolferno said:
Make sure to go to advanced wifi settings and disable search for signal during sleep. Even though you turn off wifi, this setting usually persists.
This is my wifi setup, I disallow any automatic scanning.
(It's the fifth item down.)
Also can you show us the details of your Android processes? It's very odd that it's using so much of your battery. I've only had that sort of usage when I encrypted my phone. I don't do that anymore since Samsung Pay won't work with encryption.
Click to expand...
Click to collapse
Details below from today:
After searching extensively on the whole Nexus 6 signal debacle. I've gotten some observations and studies to share and a couple questions.
I recently obtained a Nexus 6, which I already knew had the ! no data connection problem. (I tried to help the previous owner with the issue before, calls/texts would work, but data wouldn't) They were naturally on T-Mobile, so I assume it was related to the project Fi launch. Googling the issue recently states mostly T-Mobile and Sprint users having the issue, so I decided eh can't pass up a good deal! A like-new Nexus 6 for only $70, who can resist? I figured even if I get the no data issue, I can just turn on airplane mode, use as a mini-tab.
Here's where it gets interesting: I use Cricket (which is AT&T of course), popping the sim in results in good signal, LTE, etc as expected. Randomly (sometimes within 2 minutes) instead of the "!" on service problem, it drops to No Service completely. A reboot and it comes back fine, this wouldn't be too much of an issue except it happens EVERY 2-10 minutes. The only way to get it back is a reboot, airplane mode toggle doesn't help.
Which leads into the second part of the conundrum: Airplane mode doesn't help.
I figured I might just keep it in airplane mode and use as a tablet... The phone said no, Was fully charged before going to bed, by morning 17%. In airplane mode no less, which is of course is abnormal. Looking into it, it seems the phone never went into Deep Sleep, which I immediately delved into the cause. At this time I was running CM13 latest nightly, naturally I went for a fresh stock flash... Same issue. I even stock flashed to 5.0.0 and the same issue... Looks like hardware, but the randomness is the confusing part and you'd think if it was hardware a simple reboot wouldn't fix.
The phone never slept because when it would "No service" on me, I'd get wakelocks for "msm_hsic_host" which would keep the phone awake EVEN IN AIRPLANE MODE, which also in the battery settings showed the red bar for "bad" signal. This happens with AND without a sim, airplane mode or not. I'm currently on Pure Nexus and Franco's kernel to disable hsic wakelocks, and I'm seeing another one for "qcril_pre_client_init" when the issue happens. Which would be the Qualcomm radio interface layer, by the name, I'm assuming android is trying to turn on the radio and keeping the phone awake. This shouldn't happen in airplane mode, I've also tried "Toggle Cell Radio 5.0" to directly turn off the cell radio; Issue remains.
The randomness of when it happens, how it's "resolved" by a simple reboot, and the fact that airplane mode has zero effect on when it happens basically cripples it as a tablet as well, it never sleeps so the battery life is pretty crap (about 18%/hour screen off). After a reboot the thing is great as long as the thing has signal, runs cold, great life, charges fast, sleeps deep. Befuddled that it still does it without a sim card and airplane mode...
My question to the users here: If anyone else has any insight on this, and if anyone knows how to completely disable the cellular interface and literally turn it into a tablet. Is there any rom or such that doesn't try to wake/use the cellular radio and keep the thing awake.
EDIT: Yes, I've run the factory images from google, 5.0.0, 6.0, and 6.0.1 during testing.
The sim card is new, I've already changed it.
Yes the device is actually an XT1103, not a knockoff.
Sorry if any of this information wasn't clear enough.
Further Observations:
During the night I had zero reboots (It's setup to reboot on signal loss, so from here reboot == signal loss), then after taking it off of charge and turning the screen off, then back on after about 5 seconds the signal was lost and it rebooted.
This got me thinking, so on the way to work, I streamed music and had zero problems, not on the charger. After reaching work, I moved some offline music onto my phone and it acted fine as well. The phone never reboots if the screen is kept on as well.
This tells me it's something about how android switches to low-power on the cellular radio. Perhaps the radio cannot wake up properly from the low-voltage sleep state.
tl;dr
When phone is 'active' and not sleeping, problem doesn't arise.
Acts normal with screen off: Streaming music, Regular music, Plugged in.
Acts normal with screen on always.
If doing nothing and phone sleeps: reboots, usually on wake up (i.e. turning screen on to check time)
Likely issue with sleeping/low-power to the cellular radio.
Current bad "solution" play music with phone muted.
However, this doesn't seem to be too bad an impact on battery life, music player has used a total of 1% in the last two hours, screen is top again, where it was android os.
EDIT: Went all day without dropping signal by keeping music playing muted. At 52% after about 12 hours, 3 hours screen on, an hour VOIP call, wifi on the entire time. Not the best solution, but it's livable.
Further testing: I've tried a couple "keep awake" apps that set wakelocks and they do not seem to help, but this might be that they are not designed for marshmallow.
I've also "unoptimized" anything related to phone/cellular in the battery settings to prevent doze from sleeping them, no effect, double the apps directly hit the radio.
first off, first thing that I would do is fastboot flash the latest 6.0.1 factory image(then root it). as the issue sounds like a software problem. if it is, this would fix it. if it still is broken, then I'd root it for sure, then disable the cellular connectivity issue with my root access. without root, you are stuck with airplane mode, only.
simms22 said:
first off, first thing that I would do is fastboot flash the latest 6.0.1 factory image(then root it). as the issue sounds like a software problem. if it is, this would fix it. if it still is broken, then I'd root it for sure, then disable the cellular connectivity issue with my root access. without root, you are stuck with airplane mode, only.
Click to expand...
Click to collapse
I mentioned that I stock flashed... I tried 6.0.1 and even 5.0.0... Also I'm on a custom rom + kernel, so I kiiiinda have root access as well. I don't mean to sound uppity or anything, but did you even read my entire post? If you have a way to completely disable the cellular radio, by all means share. Only other thing I can think of to try tomorrow when I get time is to flash an incompatible baseband, but I can see it causing the same issue with I/O problems.
Skreelink said:
I mentioned that I stock flashed... I tried 6.0.1 and even 5.0.0... Also I'm on a custom rom + kernel, so I kiiiinda have root access as well. I don't mean to sound uppity or anything, but did you even read my entire post? If you have a way to completely disable the cellular radio, by all means share. Only other thing I can think of to try tomorrow when I get time is to flash an incompatible baseband, but I can see it causing the same issue with I/O problems.
Click to expand...
Click to collapse
By saying what you did that doesnt say if you went completely stock with the google images or some of the roms floating around. There is something in the background trying to force the device to connect to cell netowork. I would completely erase the device and make sure to format everything with the flash all bat file. You will ose everything on the device.
Also could be a lose connection in the hardware.
zelendel said:
By saying what you did that doesnt say if you went completely stock with the google images or some of the roms floating around. There is something in the background trying to force the device to connect to cell netowork. I would completely erase the device and make sure to format everything with the flash all bat file. You will ose everything on the device.
Also could be a lose connection in the hardware.
Click to expand...
Click to collapse
When I said stock, I meant the factory images from google... I've completely wiped the device several times. I'm not new to the entire process... That's why in my original post I stated possible hardware, but curious as to why it does it even in airplane mode when it shouldn't poll the cell radio at all. Further testing seems to say that disabling location access (I generally use battery saver, gps only for navigation), it holds signal longer. Potentially something wrong with how the system requests location.
Skreelink said:
I mentioned that I stock flashed... I tried 6.0.1 and even 5.0.0... Also I'm on a custom rom + kernel, so I kiiiinda have root access as well. I don't mean to sound uppity or anything, but did you even read my entire post? If you have a way to completely disable the cellular radio, by all means share. Only other thing I can think of to try tomorrow when I get time is to flash an incompatible baseband, but I can see it causing the same issue with I/O problems.
Click to expand...
Click to collapse
like was said, kinda sounded like you flashed a stockish kinda ROM. if not factory image, I recommend it.
Skreelink said:
When I said stock, I meant the factory images from google... I've completely wiped the device several times. I'm not new to the entire process... That's why in my original post I stated possible hardware, but curious as to why it does it even in airplane mode when it shouldn't poll the cell radio at all. Further testing seems to say that disabling location access (I generally use battery saver, gps only for navigation), it holds signal longer. Potentially something wrong with how the system requests location.
Click to expand...
Click to collapse
Are you sure it is a legit device? I have seen some knock offs have this issue.
You know we are all kinda dumb here. Myself included.
Run a logcat and see what is trying to connect.
zelendel said:
Are you sure it is a legit device? I have seen some knock offs have this issue.
You know we are all kinda dumb here. Myself included.
Run a logcat and see what is trying to connect.
Click to expand...
Click to collapse
Yes it is a legit device directly from tmobile. I'll do more testing tomorrow.
Maybe try a new sim card,only thing I can't think of
holeindalip said:
Maybe try a new sim card,only thing I can't think of
Click to expand...
Click to collapse
Already got a new sim, updated info in original post.
Attached a screen with battery info, from testing it's pretty accurate.
After implementing my "solution" for a couple days, it seems to sleep fine now without losing signal. Remember, I have tasker setup to reboot on signal loss so this is informative that it actually sleeps now...
Was the phone ever wet? The signal loss is common on my Nexus, as with my previous, always have missed calls etc, got a voicemail but no missed call notification. However it doesn't really describe the radio issue your describing. I'm almost certain the mother board is malfunctioning. The radio turns to low power mode in doze, but never returns to full power state. Seems to me that it's a communication issue from the motherboard. Neat idea for your "solution".
Sent from my Nexus 6 using Tapatalk
Jnewell05 said:
Was the phone ever wet? The signal loss is common on my Nexus, as with my previous, always have missed calls etc, got a voicemail but no missed call notification. However it doesn't really describe the radio issue your describing. I'm almost certain the mother board is malfunctioning. The radio turns to low power mode in doze, but never returns to full power state. Seems to me that it's a communication issue from the motherboard. Neat idea for your "solution".
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Phone has never been wet or suffered any trauma such as a drop or high temps. It's an odd little thing.
Try flashing a different modem?
dcrews said:
Try flashing a different modem?
Click to expand...
Click to collapse
I have, I think it's a hardware problem where the modem can't wake up from low power state similar to some cpus unable to wake if set too low.
Seemingly a breakthrough
Did a few more things and testing and I seem to have gotten onto something. I've attached screenshots showing just over 3 hours deep sleep and included battery info page. As a recap I couldn't get 10 seconds of deep sleep before tasker would wakeup the phone because it lost signal, then wait 30 seconds before rebooting it to get signal again, unless I was playing music (which kept the phone awake and thus never lost signal). You may notice on the upper left the carrier symbol, I'm on Project Fi and using Signal Spy to show which carrier I'm currently on. After doing my tests today it swaps carriers fine without ever completely dropping the radio and requiring a reboot to regain signal.
I'll do more tests and see how long, if it does to act up. If I seem to have actually found a real solution, I'll post what I did to resolve the issue just incase any other Nexus 6 users are experiencing problems.
Edit: Small note worth mentioning, wifi seems more stable as well. I'm able to keep AndroIRC connected with the screen off whereas I was having issues with it disconnecting randomly. This MAY just be due to something else, but still noting it here.
I'm having issues with several apps not triggering at specific times/notifications. Tried to whitelist Duolingo and that worked for two days and then it stopped. Podcast addict is doing the same thing. It should update every 4 hours but nothing happens. Tried to whitelist it but didn't work. The developer thinks it is the phone that kills the wake-up trigger/alarm. Anything else that I can try as it is rather annoying that various apps only work if I actually open the.
Running nougat and 4.0.2
Disable Doze Mode from Settings->Developer options. Reboot to wipe caches and check if problem is solved.
TweaknFreak said:
Disable Doze Mode from Settings->Developer options. Reboot to wipe caches and check if problem is solved.
Click to expand...
Click to collapse
I'll test that. Didn't know the reboot did that.
Eggstones said:
I'll test that. Didn't know the reboot did that.
Click to expand...
Click to collapse
What I meant by reboot was to boot into recovery mode and wipe caches.
Sorry not sure how to do that. Just going into memory clearing it from there doesn't do the trick?
Press the POWER+VOLUME DOWN keys simultaneously until the device restarts and oneplus splash screen appears. Then recovery mode will start and language selection menu will appear. Wipe caches from there. Be careful not to wipe anything else. Then restart your device. Most issues albeit small ones get resolved by doing this.
Seems like doze kills the check. If I switch doze off, podcast addict runs the check for new episodes. With it on it doesn't, even if I whitelist the app. It also seems like when it runs the new episode check , the phone kills the app as it showed up under power hungry apps. I'll see if the cache clean dies anything.