Develop Bugs

battery drain tips?

When I run the latest android build on my Tilt 2, it flies through battery like no other.
Are there any settings I can tweak to get at least a full day's worth of use out of it (mostly in standby anyways)?
Thanks
Regards
Smith

I'd love to hear anyone's tips as well. As mentioned here:
http://forum.xda-developers.com/showpost.php?p=7959929&postcount=7622
Setting the sleep mode = 1 doesn't seem to work for me. The processor seemingly goes to sleep and enters a coma (yes, I set the clock speed back to stock in the startup.txt).
One quick tip to the OP is set the clock speed to stock.
Edit: sleep mode = 0 seems to work (GSM phone here). However, deleting the "acpuclock.oc_freq_khz=XXX" line from the startup.txt and setting sleep=1 just might work as well.
Edit2: sleep mode = 0 seems to result in the phone functionality breaking. It stopped waking up to phone calls after a while, and calling out wouldn't work either. Damn.. Just a heads up.

1. Close every program that you don't use on startup of android. You can do this with advanced task killer.
2. Run stock speeds.
3. Turn down the screen brightness.
4. Make sure your phone goes to sleep when you are not using it (green led = sleep)

Is advanced task killer installed by default?
Also, how can I clock it to stock? I wasn't aware that it was overclocked past stock.
Screen brightness makes sense, I'll definitely do that.
So, if green is sleep, what is the orange?
Thanks
Smith

I reckon hepatic feedback would drain a little battery on its own probably best to turn that off

This is all true. I'll have to do that.
Still figuring it all out. Once I can get a solid 18-24 hour charge cycle out of it, Android will become my primary OS, easily. Simply works better, IMO

For me sometimes it's green, sometimes it's Orange - not sure how to change it back green -
I use Advance Task Killer, but then i also read that Froyo 2.2 doesn't need a task killer?
The two things that have helped battery life the most were:
-Switching to stock clock speed (the reference over the overclocked BLZN which i loved but killed the battery life)
-turning off background processes... i only turn it on when i have to (using the market, etc)
I would love to hear more tips

The colours are not that hard.
Red/orange = awake
Green = sleeping
If the LED stays red, then your device is doing something, you can either wait or try closing the programs with the task killer. That will help sometimes.
For returning to stock speeds read the faq And advanced task killer can be downloaded in the market.

Thank you guys all so much, big, big help to me!
Android is definitely going to be my full time OS shortly
Smith

Its kind of tough trying to go anywhere without a charger nearby. The battery drains quickly and on top of that the actual battery meter is off.
So sometimes that is a main issue
Sent from my MSM using Tapatalk

throwback1718 said:
Its kind of tough trying to go anywhere without a charger nearby. The battery drains quickly and on top of that the actual battery meter is off.
So sometimes that is a main issue
Sent from my MSM using Tapatalk
Click to expand...
Click to collapse
Indeed but that is something that they are working on it as we speak. Give them time

I ran a test last night before going to sleep to see how long the phone lasts.
Charged my phone fully. Ran advanced task killer and killed all the programs. Put the phone in deep sleep ( green light).
Woke up 7 hours later and phone was completely dead. I do have auto sync turned on, but only over wifi, so it should not have used any data as i have the data turned off and no widgets on my home screens that auto-update.
I'll try again tonight for a shorter time (5 hours).
Running the blazn aug 30th build.

karan1203 said:
I ran a test last night before going to sleep to see how long the phone lasts.
Charged my phone fully. Ran advanced task killer and killed all the programs. Put the phone in deep sleep ( green light).
Woke up 7 hours later and phone was completely dead. I do have auto sync turned on, but only over wifi, so it should not have used any data as i have the data turned off and no widgets on my home screens that auto-update.
I'll try again tonight for a shorter time (5 hours).
Running the blazn aug 30th build.
Click to expand...
Click to collapse
How did you 'put the phone in a deep sleep'

I turned off all auto updates.
The next day i did the test again, charged the phone to 100% and used the phone moderately for 8 hours before the battery died.
Without overclocking i can safely say i can get the phone to last 8 hours with moderate to heavy usage, which is excellent.

My main problem with the new updates are that it constantly restarts or crashes after using it for less than 30 minutes while before I could use it for several hours. Not sure whether it's to do with battery life or not as when it boots back in WM the battery is near full.
The biggest things that have helped conserve battery life for me are disabling GPS and background syncing but some apps require this to be enabled. :S

Phone seems to recover from "sleep"
FWIW, I set sleep mode = 1 and removed the overclock line from the startup.txt and the phone SEEMS to sleep and "wake up" just fine. Previously, I had problems with the phone going to sleep and when waking up, everything seemed fine, but the phone didn't work. With the overclock line removed, it seems to "wake up" with the phone working now.
Just a heads up to anyone who wants to save battery life.. might want to remove the overclocking line in the startup.txt..

[Q] HTC Kaiser CPU Doesn't Sleep?

Did a search, and didn't find anything regarding this, so I'll point this out. I've noticed whenever my Kaiser (KAIS100) goes to sleep, it doesn't actually sleep, I can still press every button and the phone will "wake", screen comes on.
When I check Spare Parts > Battery History, it shows my phone's been running for 5days even though it's been on for 10 minutes actual. If I continue to put the phone to sleep that time grows exponentially.
Is my KAIS really sleeping, or is there a bug somewhere?
I'm running l1q1d's latest .32 kernel, with Fat Free Froyo build with system/data on NAND.
Battery also only lasts about 8hrs in "standby", and not even 2hrs with full use. With WinMo, I get about 36hrs standby, and about 5hrs full use.

Krazy-Killa said:
I've noticed whenever my Kaiser (KAIS100) goes to sleep, it doesn't actually sleep, I can still press every button and the phone will "wake", screen comes on.
Click to expand...
Click to collapse
Screen comes on, obiusly, but its locked right? that the way its ment to be... if you wanna check the hour or see if u got messages or missed calls... or it unlocks?
Krazy-Killa said:
When I check Spare Parts > Battery History, it shows my phone's been running for 5days even though it's been on for 10 minutes actual. If I continue to put the phone to sleep that time grows exponentially.
Click to expand...
Click to collapse
I guess its not completley implemented yet, search this forum I remember I looked something about it, or post a comment to our good friend n2rjt in that thread:
http://forum.xda-developers.com/showthread.php?t=782269
Have you modified .nbh file with atools and entered the correct value on the advanced batt capacity? (units = battery real mAh * 1.6) if you havent or if you own an old battery you'll experience a lot of batt consumption or inaccurate readings....

albertorodast2007 said:
Screen comes on, obiusly, but its locked right? that the way its ment to be... if you wanna check the hour or see if u got messages or missed calls... or it unlocks?
I guess its not completley implemented yet, search this forum I remember I looked something about it, or post a comment to our good friend n2rjt in that thread:
http://forum.xda-developers.com/showthread.php?t=782269
Have you modified .nbh file with atools and entered the correct value on the advanced batt capacity? (units = battery real mAh * 1.6) if you havent or if you own an old battery you'll experience a lot of batt consumption or inaccurate readings....
Click to expand...
Click to collapse
The phone locks like it's suppose too, but the problem I'm having is the CPU of the Kaiser isn't actually falling asleep. I'm getting the same battery consumption as when the screen is off compared to on, and sitting there (no activity on my part, just leaving the screen on for no reason )
Every so often the phone will be asleep, and the only way to bring it back on is by hitting the power button, but about 95% of the time I can press the call button, end button, OK button, IE button, hell even push down on the wheel on the other side of the Kaiser and the screen will come on showing the lock screen.
As far as the battery capacity, I have not done that, but the phone's been auto-learning my capacity, and it will get to the 2160 units, compared to the 2000 it's always set too, and sometimes reach 2377 units.
I have tried several Radio versions, down to 1.65.xx.xx version (which was the original version on my phone), and no changes, and tried different builds and no change either. DZOs kernel doesn't make a difference either, except screw up my battery meter completely. lol

uhm thats wierd.. i can only unlock through the power button, what i have experienced is that if its conected to an external power source it does reacts to any button I press.... but not on battery... maybe its a build issue... right now im using scoots CM rls 5a, dont remember if warbyte's donut behave like that...

albertorodast2007 said:
uhm thats wierd.. i can only unlock through the power button, what i have experienced is that if its conected to an external power source it does reacts to any button I press.... but not on battery... maybe its a build issue... right now im using scoots CM rls 5a, dont remember if warbyte's donut behave like that...
Click to expand...
Click to collapse
Did some more testing, and found that without it plugged into power it does only respond to the power button, but again it's only about 15-20% of the time, and even those times seem iffy as it just seems like the phone's just slow to respond.
Phone is also somewhat warm as well even when "off", and I do have the phone overclocked to 450MHz, kernel is set to 425 (running a test on speed/stability atm)
At 425MHz it's still reasonably warm, and at 450 the temperature jumps alot.
Anyone else have an issue of the tap sounds when tapping on the screen sometimes not playing? Granted phone quality is great, and GPS is working well, though Camera is broken on my end, even though it was working before.

It sounds like there is a real issue. Some application is running continuously for you, preventing the CPU from going to sleep. I have had that before. Try removing widgets from the main screen. For me, the problem was an app that showed a flip-clock and the weather, and looked just like HTC Sense. I don't remember its name but it used to be popular.
The newest 2.6.32 kernel seems to sleep relatively well for me. Sometimes it wakes on any key, and sometimes it wakes up to a totally white screen. Other times it just plain refuses to wake up. Usually I can coax it back to sanity (from white screen or from sleep) by Fn-Left keyboard softkey, then Fn-Right keyboard softkey.
Your phone should get approx 10 or so hours of life from a charged battery. Less than you get with WinMo, but lots more than you seem to be seeing.

n2rjt said:
It sounds like there is a real issue. Some application is running continuously for you, preventing the CPU from going to sleep. I have had that before. Try removing widgets from the main screen. For me, the problem was an app that showed a flip-clock and the weather, and looked just like HTC Sense. I don't remember its name but it used to be popular.
The newest 2.6.32 kernel seems to sleep relatively well for me. Sometimes it wakes on any key, and sometimes it wakes up to a totally white screen. Other times it just plain refuses to wake up. Usually I can coax it back to sanity (from white screen or from sleep) by Fn-Left keyboard softkey, then Fn-Right keyboard softkey.
Your phone should get approx 10 or so hours of life from a charged battery. Less than you get with WinMo, but lots more than you seem to be seeing.
Click to expand...
Click to collapse
by chanse wasnt weather widget? had a really bad slowdown over scoots CM because of that widget, was constantly trying to update the weather....

albertorodast2007 said:
by chanse wasnt weather widget? had a really bad slowdown over scoots CM because of that widget, was constantly trying to update the weather....
Click to expand...
Click to collapse
Yes that's the one. it needs to be removed, and can be replaced by Fancy Widget.
Sent from my Android on HTC Kaiser/Kaiser/Polaris using XDA App

n2rjt said:
It sounds like there is a real issue. Some application is running continuously for you, preventing the CPU from going to sleep. I have had that before. Try removing widgets from the main screen. For me, the problem was an app that showed a flip-clock and the weather, and looked just like HTC Sense. I don't remember its name but it used to be popular.
The newest 2.6.32 kernel seems to sleep relatively well for me. Sometimes it wakes on any key, and sometimes it wakes up to a totally white screen. Other times it just plain refuses to wake up. Usually I can coax it back to sanity (from white screen or from sleep) by Fn-Left keyboard softkey, then Fn-Right keyboard softkey.
Your phone should get approx 10 or so hours of life from a charged battery. Less than you get with WinMo, but lots more than you seem to be seeing.
Click to expand...
Click to collapse
Ok, I'll give it a whirl, and remove some of the widgets I have running, and see if it does help out. Right now though I'm re-installing /system as I tried messing around with the density as 110 seems to work real well with where things are placed on the home screen (no widgets are overlapping each other), but Market won't work, and the Android Keyboard keeps crashing (on-screen).
But anyways, phone's booting back up, so I'll test out the battery life here again, as I got about 95% charge right now, so should serve as a good test for battery life, and CPU Sleepage.

Having a similar issue, seems to behave ok (screen lock comes on when I press power button) but power usage on standby is similar to original poster's. About 8 hours standby. Went to bed last night and it said 66% charged (1300mAH battery) and it didn't last the night. Takes a looooong time to charge to full though so I doubt it's lying about fully charging the battery, suggesting it's using it up at a fast rate.
How do I check background tasks?
Edit: This is with WiFi, GPS and Sync OFF by the way. On the other hand I live in a low signal area (typically 1-2 bars) could it be straining to get a better signal? Used to have an old nokia that used to run itself flat in no time when there was a low/missing signal!
Edit 2 : Figured it out, turns out the ebay app has a service and a process running - even with notifications turned off! Have killed these and see if anything improves

That could very well be part of the problem, although it shouldn't kill it from 66% with just the radio. How much capacity does it calibrate itself to?

cycloid said:
Having a similar issue, seems to behave ok (screen lock comes on when I press power button) but power usage on standby is similar to original poster's. About 8 hours standby. Went to bed last night and it said 66% charged (1300mAH battery) and it didn't last the night. Takes a looooong time to charge to full though so I doubt it's lying about fully charging the battery, suggesting it's using it up at a fast rate.
How do I check background tasks?
Edit: This is with WiFi, GPS and Sync OFF by the way. On the other hand I live in a low signal area (typically 1-2 bars) could it be straining to get a better signal? Used to have an old nokia that used to run itself flat in no time when there was a low/missing signal!
Click to expand...
Click to collapse
Phone Radio really shouldn't use more power with low signal, in fact it really shouldn't affect power output at all (well except the fact that it's on). I have a 1350mAH battery, but it's reading at 2470 adjusted, so I re-flashed a new kernel with the new battery changes, now it's reading 2437units adjusted, which is over 1500mAH for the battery which is not what I own. But on the bright side, my battery capabilities are improving, and the battery meter is starting to read alittle more accurately.

Krazy-Killa said:
Phone Radio really shouldn't use more power with low signal, in fact it really shouldn't affect power output at all (well except the fact that it's on). I have a 1350mAH battery, but it's reading at 2470 adjusted, so I re-flashed a new kernel with the new battery changes, now it's reading 2437units adjusted, which is over 1500mAH for the battery which is not what I own. But on the bright side, my battery capabilities are improving, and the battery meter is starting to read alittle more accurately.
Click to expand...
Click to collapse
yes, i boutght seidio 1600 mAh, and the kernel ended up adjusting it to 3260 units... (about 2000 mAh) maybe the 1.6 factor isnt right just as n2rjt said, maybe its closer to the 2.0

Seems like ebay may have been the culprit. Killed the ebay process and application in the background and only used about 10% over night (as opposed to over 60% the night before). I'll have to leave it overnight with ebay running again for a proper scientific test next

cycloid said:
Seems like ebay may have been the culprit. Killed the ebay process and application in the background and only used about 10% over night (as opposed to over 60% the night before). I'll have to leave it overnight with ebay running again for a proper scientific test next
Click to expand...
Click to collapse
Yah, I'm starting to run into issues with certain apps keeping the phone awake and not letting it sleep. I kill some of the apps and it actually helps out the battery some.
I installed the original launcher from one of the other froyo builds, but came across with an FC with acore, so now back with ADW.Launcher or LauncherPro.

Krazy-Killa said:
Yah, I'm starting to run into issues with certain apps keeping the phone awake and not letting it sleep. I kill some of the apps and it actually helps out the battery some.
I installed the original launcher from one of the other froyo builds, but came across with an FC with acore, so now back with ADW.Launcher or LauncherPro.
Click to expand...
Click to collapse
When you install a app, take a look at its requirements, like "PREVENT FROM SLEEP". You might have a app doing just that..

daedric said:
When you install a app, take a look at its requirements, like "PREVENT FROM SLEEP". You might have a app doing just that..
Click to expand...
Click to collapse
Yep, most of the apps I download have that. But in sad news, I'm actually going back to WMO 6.5 as I can't seem to keep Android stable on my kaiser.. I've reinstall the same build twice (which I know is not corrupted, as it was working fine 2 days ago), and Market is always corrupted...... So, for now, until I have a secondary phone I can revert too, I'll be going back to WMO for the time being.

Krazy-Killa said:
Yep, most of the apps I download have that. But in sad news, I'm actually going back to WMO 6.5 as I can't seem to keep Android stable on my kaiser.. I've reinstall the same build twice (which I know is not corrupted, as it was working fine 2 days ago), and Market is always corrupted...... So, for now, until I have a secondary phone I can revert too, I'll be going back to WMO for the time being.
Click to expand...
Click to collapse
Umh... sad...
We'll wait for you! Bye bye

daedric said:
Umh... sad...
We'll wait for you! Bye bye
Click to expand...
Click to collapse
LOL! Not like I'm leaving, I'll be popping on here every so often, and still doesn't mean I'll use Haret to load up Android to test out new builds that come out, and new kernels that are released in the future.

Krazy-Killa said:
LOL! Not like I'm leaving, I'll be popping on here every so often, and still doesn't mean I'll use Haret to load up Android to test out new builds that come out, and new kernels that are released in the future.
Click to expand...
Click to collapse
Man... that's a sin! You can't do that! You'll be off from the Brotherhood!
Kiddin' ;D

[Q] Battery issue on Wildfire S

Hi,
after running for 15 hours, one phone call for 2 min, and about 8 sms
and nothing more still remain 45% from 100%.
is that normal or it is something wrong?
wifi, gps, and bluetooth are off, and not many apps are working in background.
no livebackground or something else.
it seems to me, it is very less for such a phone, or I am wrong?
or are there some settings, which need to set to have a longer battery live?
thanks

Hi,
I saw that the dialer use 97% from the Battery! I had the whole day one call for 2 minutes.
is there someone else with such dialer usage?
thanks

andi_79 said:
Hi,
I saw that the dialer use 97% from the Battery! I had the whole day one call for 2 minutes.
is there someone else with such dialer usage?
thanks
Click to expand...
Click to collapse
I too am seeing that the dialler is using 97% of battery with only one short call made. However, I have so far and still counting got 3d 18h out of my first battery charge. (This is a new phone) This is with everything turned off mind you as I wanted to see the best time achievable with only phone functions active. Once the battery is run down I will re-charge and turn internet on etc.
It's funny that you too have "97%"??

very strange.
could someone post a normal state, how it supposed to be?
thanks

Hey i think you people don't know how the battery use calculate the battery usage in Android.
This is how it calculate
Suppose you had power on the phone then and you are using 3 apps like
1.dialer
2.wifi
3.display
then from above 3 which is the most used app the battery usage will give it more percentage.(But you will not see any 97 % if you are using 5-6 activities)The more the number of apps the less the percentage of each Activity.
The region why you are seeing 97% on battery usage about dialer is that you are using only dialer nothing else.If You use use gallary,wifi,bluetooth,calls,maps etc all together then battery usage will show you 15 to 20 % in each.
To increase battery life calibrate you battery.(let the battery discharge once and recharge it without power on and without any break)
In this forum i had seen that some are geting 4 days of battery with moderate usage and some getting only 1 day.You Had not calibrated your battery.Every Android mobile needs battery calibration atleast once in 1 month.

hi shreyasharusia
yesterday I made a reset, and I calibrate the phone.
Now I have following situation:
Dialer 41%
Cell Standby 29%
Phone Idle 28%
display 2%
android system 2%
Today I made just on call for 2 min, and I have 98%
do you think somthing is wrong with it?
thanks

could be a bug with the sense causing the battery life to be short. I usually let my phone discharge every day before I charge it for the next day. As I am usually using my phone every day the battery usually lats a day at the maximum this is usually because i am always listening to music or texting people.

now I have again this situation.
I did nothing with the phone. just one call for 2 min and 2 text, thats it.
dialer 95%
cell standby 3%
phone idle 3%
so then it is wrong to have the dialer on 95% right?

andi_79 said:
now I have again this situation.
I did nothing with the phone. just one call for 2 min and 2 text, thats it.
dialer 95%
cell standby 3%
phone idle 3%
so then it is wrong to have the dialer on 95% right?
Click to expand...
Click to collapse
that's not possible.Battery use limits to 100 % not 101%. 95+3+3 = 101.And in your first post 41+29+28+2+2 = 102.How it can be possible .
Also check is your connection is 3g or 2g.You get your battery life according to it.

.... I know, but it is fact
I was surprised too....)
I will search for a screenshot tool, and I will post it soon....
by the way, I check it with Advanced Task Manager, maybe this tool is wrong?
I use 2G only. I wouldn't be suprised if bluetooth and wlan would be on, and after a work day the battery is empty, but for one call and 2 text?
as for now, the Task Manager and a File Manager is installed, the rest is all on default.
thanks

andi_79 said:
.... I know, but it is fact
I was surprised too....)
I will search for a screenshot tool, and I will post it soon....
by the way, I check it with Advanced Task Manager, maybe this tool is wrong?
I use 2G only. I wouldn't be suprised if bluetooth and wlan would be on, and after a work day the battery is empty, but for one call and 2 text?
as for now, the Task Manager and a File Manager is installed, the rest is all on default.
thanks
Click to expand...
Click to collapse
Use Shootme for screenshot. And Take it to service center for getting low battery issue.

Hey try juice defender.It really works

Hi shreyasharusia
I need to be root to run this tool. is there another that I can use without being root?
Anyway now I have following situation.
Dialer 96%
Cell Standby 3%
Phone Idle 3%
I will try now the other tool, which do you recommend to me...
thanks by the way
but just to clear it, to have the dialer on 96% is wrong, right?
Andy

Hi, im new htc wildfire s user, barely a week. Before my battery usage showed lots of things but now theres Dialer 97%, Cell Standby 2 %, and Phone idle 2 %. Whats going on :S? Im releaved that im not the only one. Can somebody please help me im begging

My girlfriend's wildfire s' battery life is really bad. At first it was like 16 hours, but that was when it was in a really heavy use. Now it lasts only for about 12 hours with very minimal use: a couple sms' and little calling. In fact the usage doesn't even affect the battery life, as it drains at a constant rate. The values are _always_ the same: Dialer takes 49%, Android system 49%, Idle 2% It doesn't even show how much the display is using!

[SOLVED] this battery issue
Hello everyone who is experiencing really massive battery drain on wildfire S.
Symptoms:
1. you own wildfire S
2. in battery stats the "dialer" is on top (eg. 97%)
3. you have made a call recently
4. experiencing battery drain about 30-50% per hour.
Cause:
Maybe it really surprises you (or your girlfriend), but you are most probably making a phone call. The new wildfire's dialer is just a bit crappy. When you dial a number and then want to hang up, you have to do it by correct button (the red "hang-up" button). There is also a possibility to "terminate the call" by pressing the "back" button on the bottom, but in this case your call is not terminated at all, but dialer is running now in the background. The nice example is when you are calling a buddy and then you hang-up(using back button) after you realized that you are being redirected to voicemail. By doing this you are still talking to a voicemail for a period of time until the call is terminated automatically by that particular carrier.
Solution:
Use the red button to terminate the phone call. Check the logs and you will see if this is your case.
If you find this post helping to you, just say "Thanks" ---->

does anyone know the pin diagram for the battery?
I just want to know how the android takes the data from the battery.

For users experiencing massive battery drain after making a call and the infamous "Dialer" process is showing up in the battery, you need to follow the greatest battery saving top found in this thread. impreza_rs posted this solution taken from the HTC website:
"connect the phone to the charger with the phone powered on, and allow the phone to charge until the notification LED is green, indicating the device is fully charged. Disconnect the phone from the charger, and power it off. Reconnect the phone to the charger with the phone powered off, and allow the phone to charge until the notification LED is green. Disconnect the phone from the charger and power it on. Once the phone is powered completely on, power it off again and reconnect it to the charger until the notification LED is green. Disconnect the phone, power it on, and use it. You need to use this sequence only once"
I do this process every time I flash a new rom on my device and it works flawlessly. A little tedious, but you only have to do this once and you are good to go.

[APP] lightflow now works

Title says it all .. lightflow has been updated and appears to work. I tried it out. Uninstalled it because it wasn't for me but the colors appeared accurate.
Sent from my SPH-L710...if some one helps you press the thanks button

xtrezpasor said:
Title says it all .. lightflow has been updated and appears to work. I tried it out. Uninstalled it because it wasn't for me but the colors appeared accurate.
Sent from my SPH-L710...if some one helps you press the thanks button
Click to expand...
Click to collapse
Gonna give it a try.

There seems to be a bug with the "US Non-Root Light Control" it works fine with the root option, but with the US variant, in two hours, Light Flow was my number two app in Battery usage, and brought my power from 100% to 73%. For now I'm going to keep testing and see why it's doing this.
Has anybody else notice Android OS and Light Flow (number 1 and 2 on the list) use large amounts of cycles?
Cheers

I could defiantly tell it was putting strain on the battery. Android OS was my #1 on battery usage and LF was about 4th. Phone was on for about 4 hours standby time screen on for like 20 seconds and it dropped the battery about 15-20 percent cant remember exact number.

Battery Issue After Update, and how to solve

Some people might have experienced a battery issue after the latest update. It can be solved quite easily. Even If you don't believe you have an issue with your battery, you should try this as it seems baked into the update process.
Just to describe my experience first. After update my battery was going from 100 percent to 20 percent in about 8 hours while idle. It wouldn't charge while it was on. I would have to turn off the phone to charge it. I could not figure this out, until I found similar issues on different phones in the forums. It seems that when an update gets pushed to your phone, and your battery is low, your current battery charge is cached as 'max'.
First I thought the connector on my charger was broken. Then I thought maybe the charge port on the phone was somehow damaged. Then I thought there was possibly a foreign object in the charge port. It is actually none of these things. It's a software issue. Here is the resolution.
You want to boot into recovery mode. This is taken directly from Lenovo's website on the Turbo 2, but please read my caveats at the end.
Power off the device and unplug it.
Press and hold the Power and Volume Down buttons until the device turns on.
From the Boot Mode selection menu, press the Volume Down button to scroll to Recovery and the Power button to select it. The device will restart.
An image of an Android robot with a red exclamation mark will appear.
Press and hold the Power button, while still holding Power, press and release the Volume Up button, then release the Power button.
Use the Volume buttons to scroll to Wipe Cache Partition and press the Power button to select it.
If an additional confirmation screen appears, use the Volume buttons to scroll to Yes and the Power button to select it.
Press the Power button to select Reboot System Now.
This is basically the process, but you have to change up a couple things. After you wipe the cache, select 'turn off' rather than 'reboot'. Give the phone a minute to be sure it is entirely off. Plug the phone into a charger in the off state and let it charge fully. Once you are certain that the phone has been charged to 100 percent, you can reboot phone. Voila, back to almost 2 days worth of battery life.

It doesn't work for me, anyway thanks for sharing this info.
Wysłane z mojego XT1580 przy użyciu Tapatalka

I wrote this for X Style but it can be aplied to Moto x Force in the same way:
https://forum.xda-developers.com/mo...ide-improve-battery-life-performance-t3647155

I am having this issue, and sometimes Ampere shows the current draw at 2A even though the only thing I've done since power-on is run the Ampere app. I also have the green lines but that's been for much longer, so maybe there's a short but the issue started after an update not with the green lines. I'm suspecting something like a radio bug but unfortunately BetterBatteryStats requires root to do any real useful analysis (not possibly yet that I've seen with the VZWDT2). The only thing showing under usage is screen-on.
Wouldn't be ironic if it were an as-yet undiscovered crypto-miner? That hacker would be able to earn a huge bounty if they found permanent root.

Same problem here, any other solution? What's the best app to diagnose what's draining the battery?

I have done every thing with my turbo 2 , all given your tips i implemented on my mobile,
but still my phone battery not working well like working before update nougat. after updated nougat my mobile battery draining fast and after full 100 charge my mobile battery just work 3 and max 4 hours.
please launch any new update to resole this battery issue or give me some best tip to improve the battery work same work as before update nougat.
We are motorola users and we love this but company not support our users to actual solve this bad issue, really bad.
hope i hear from you with good news for users.
thanks & Regards,

I have tried multiple ways that I've found on the web, but still, my Turbo 2 has at best 3 to 4 hours of running time. Several months ago, I had the battery changed out. New battery behaved the same way. I'm convinced that Nougat is the culprit here.

Fully charged
Within an hour it went down to 68% and then shut down down. Any other fixes?

Just got a new battery fro the Droid Turbo 2
And it's working as it should. Apparently, the battery installed this past September was faulty.