Develop Bugs

New Moto 360 battery died after 3 hours!

I've just changed from a Gear Live to a Moto 360 and after charging and syncing the battery died after three hours! Horrendous. Someone please advise! My gear Live with the same settings never did this.

Hi,
I just received a Moto 360, and I know what you're going through!
I've gone from 3 charges a day previously, and today the watch is reporting I have almost 2 days remaining of charge.
First, FULLY cycle the battery. Leave it on the stand over night, run it until it turns off (if you're in a rush, ambient display, full brightness!). Then, full charge to 100% and leave it for an hour on the charger once it is full.
After that, do a factory reset on the watch (in settings). In Android Wear on phone, use the settings menu to resync your apps.
Do one more full discharge and full charge, and you should be sorted.
If not, use the Watch Battery section of the wear app to identify problem apps. Before today, I had never seen a "watch idle" entry, because an app was holding the watch awake. Identifying and removing that app has solved the rest of my problems.
Hope all this works. Some of the steps seem/may be unnecessary, such as the factory reset, multiple full charge cycles. However, I speak from experience that they do work!
Edit: Do be aware that the charge cycles where you do a factory reset and sync will drastically drain the battery, giving the illusion that the problem is still there.

chrispy_212 said:
Hi,
I had never seen a "watch idle" entry, because an app was holding the watch awake. Identifying and removing that app has solved the rest of my problems.
Click to expand...
Click to collapse
So which app was that. Could you be specific please? I've had my 360 since October and had no issues with battery life until about 2 weeks ago and now it can't make it through a work shift all of a sudden. I've seen the 'watch idle' and the android guy with no title in the battery stats (as well as 'Bluetooth', which is mind blowing) as the main drains but I can't figure out which apps need the boot. Thanks in advance for the help, this problem is driving me crazy!

For me it was WeChat. I didn't even know it had a wear component. However, using Wear Battery Stats (available on Google Play) I noticed that there was a missing icon under "app activity" because it had updated that day. Tapping on this blank icon told me it was an activity belonging to WeChat. Using this, I deduced that was the problem app. Removing it seems to have solved my issue. I'd recommend a similar process, although I only found this app on that day due to it updating, so you may struggle. I get the impression the standard of coding of wear apps so far is pretty shoddy, I don't think not providing a package name and icon is unusual or specific to this one app.

chrispy_212 said:
Hi,
I just received a Moto 360, and I know what you're going through!
I've gone from 3 charges a day previously, and today the watch is reporting I have almost 2 days remaining of charge.
First, FULLY cycle the battery. Leave it on the stand over night, run it until it turns off (if you're in a rush, ambient display, full brightness!). Then, full charge to 100% and leave it for an hour on the charger once it is full.
After that, do a factory reset on the watch (in settings). In Android Wear on phone, use the settings menu to resync your apps.
Do one more full discharge and full charge, and you should be sorted.
If not, use the Watch Battery section of the wear app to identify problem apps. Before today, I had never seen a "watch idle" entry, because an app was holding the watch awake. Identifying and removing that app has solved the rest of my problems.
Hope all this works. Some of the steps seem/may be unnecessary, such as the factory reset, multiple full charge cycles. However, I speak from experience that they do work!
Edit: Do be aware that the charge cycles where you do a factory reset and sync will drastically drain the battery, giving the illusion that the problem is still there.
Click to expand...
Click to collapse
chrispy_212 said:
For me it was WeChat. I didn't even know it had a wear component. However, using Wear Battery Stats (available on Google Play) I noticed that there was a missing icon under "app activity" because it had updated that day. Tapping on this blank icon told me it was an activity belonging to WeChat. Using this, I deduced that was the problem app. Removing it seems to have solved my issue. I'd recommend a similar process, although I only found this app on that day due to it updating, so you may struggle. I get the impression the standard of coding of wear apps so far is pretty shoddy, I don't think not providing a package name and icon is unusual or specific to this one app.
Click to expand...
Click to collapse
Thanks for the reply. I don't use that specific app so no luck there. Good call on Wear Battery Stats though. I actually already use it but I'll use its stats this time instead of the standard wear stats. Thanks again, hopefully I can find the culprit, been having issues with my phone battery as well recently too.

B1gC72 said:
Thanks for the reply. I don't use that specific app so no luck there. Good call on Wear Battery Stats though. I actually already use it but I'll use its stats this time instead of the standard wear stats. Thanks again, hopefully I can find the culprit, been having issues with my phone battery as well recently too.
Click to expand...
Click to collapse
fyi - i haven't tested this since it happened, but i disabled BT on my phone (just disabled in settings, without disconnecting the wtch first) and the watch drained itself in probably about 20-30 minutes. When I finally got it charged, it said BT took everything.

When I was having app issues, I also noticed very high bluetooth consumption. This could likely be a poorly coded app constantly trying to ping your phone for data and receiving no reply as it is not designed for a scenario where your phone is not connected.
The alternative of course is defective hardware.
A step I did not include in my original post was that I also clean-flashed a new rom on my phone. I felt this was due to a unique problem that I had (bluetooth problems in car also) but nonetheless thought I should mention that too. It's hard to be sure which step exactly cured my watch.

Same was happening to me, after several master resets and trial and error, i found that on my Samsung s7 edge i had my watch set as a trusted device so when it was connected to my phone my device would unlock without passcode. After turning that off, battery life is normal again, 24hrs plus. I think the constant bluetooth checking to see if it was attached drained battery extremely fast, hopefully this helps someone

[Q] Moto 360, Android Wear, Blocking Apps (or NOT), and Battery Drain (Maps Draining)

Okay, this weekend, on a Friday, I drove to DC. As soon as navigation started on my Nexus 6, my watch started to display the navigation notifications. I quickly blocked the app, as I didn't want the 3+ hours of navigation to drain my watch.
2.5 hours into the trip, I look at my watch's battery, and it's down to 30%!!! I started the trip at about 90%. Not happy, very scared about running out of power. Figure out it's a bug, or whatever, and I factory reset that night.
During the weekend, while I'm in DC, I notice that it is not the normal battery life, despite a factory reset Friday night.
On the way home, Sunday, I noticed a huge drain as well. Not wanting to lose any more power, I turn it on AIRPLANE MODE when at 47%.
HERE'S WHERE IT GETS INTERESTING.
I get a notification that says something like "Maps Navigation App stopped." I don't remember the exact phrasing.
However, this leads me to believe that I was experiencing the battery drain because while I was blocking the Maps app, it was still running on my watch! What's up with that? I thought it totally stopped the app.
Am I correct? Does a blocked app still run while the watch despite being blocked?
IF so... how do I "fix" this? Is that possible?
Or, was something else draining my battery?

funkpod said:
Okay, this weekend, on a Friday, I drove to DC. As soon as navigation started on my Nexus 6, my watch started to display the navigation notifications. I quickly blocked the app, as I didn't want the 3+ hours of navigation to drain my watch.
2.5 hours into the trip, I look at my watch's battery, and it's down to 30%!!! I started the trip at about 90%. Not happy, very scared about running out of power. Figure out it's a bug, or whatever, and I factory reset that night.
During the weekend, while I'm in DC, I notice that it is not the normal battery life, despite a factory reset Friday night.
On the way home, Sunday, I noticed a huge drain as well. Not wanting to lose any more power, I turn it on AIRPLANE MODE when at 47%.
HERE'S WHERE IT GETS INTERESTING.
I get a notification that says something like "Maps Navigation App stopped." I don't remember the exact phrasing.
However, this leads me to believe that I was experiencing the battery drain because while I was blocking the Maps app, it was still running on my watch! What's up with that? I thought it totally stopped the app.
Am I correct? Does a blocked app still run while the watch despite being blocked?
IF so... how do I "fix" this? Is that possible?
Or, was something else draining my battery?
Click to expand...
Click to collapse
Okay, from another thread I was discussing on Android Central, another user found that Maps and probably other apps weren't totally OFF when the Notification was set to be BLOCKED. Meaning, even though you are Blocking a certain app, it appears that it is still running in the background of the watch, and that is leading to huge drains.
Anybody take any road trips or commuting with their moto360 and using Google Maps notice this?
http://forums.androidcentral.com/mo...ot-battery-drain-google-maps.html#post4317990

I have this exact same issue. I use navigation a few days a week. I'm a new Moto 360 owner, so I thought it was just other battery issues. But it isn't. Its Navigation. Once I start navigation, by battery plummets. I can't stop it. Then the battery usage says that Bluetooth uses the most battery. So I am gonna keep trying different things. Don't factory reset your phone. It doesn't help. Resetting the watch doesn't help either. I think its an issue with Android 5.0.2. But that's a guess. What else can it be?

The Horak said:
I have this exact same issue. I use navigation a few days a week. I'm a new Moto 360 owner, so I thought it was just other battery issues. But it isn't. Its Navigation. Once I start navigation, by battery plummets. I can't stop it. Then the battery usage says that Bluetooth uses the most battery. So I am gonna keep trying different things. Don't factory reset your phone. It doesn't help. Resetting the watch doesn't help either. I think its an issue with Android 5.0.2. But that's a guess. What else can it be?
Click to expand...
Click to collapse
THanks for your input, sorry I never replied. I didn't see the notifications.
ANYWAYS, I started a thread here as well...
http://forums.androidcentral.com/mo...cking-apps-not-battery-drain-google-maps.html
It seems it is NOT just a Moto 360 problem, but an ANDROID WEAR problem!?
WHOA. Can anyone else confirm this? If so, if this is an Android Wear problem... does Google know? And how do we let them know?

I have this issue. I drove 3 hours with Google maps navigation today and my watch was dead upon arrival. It was at 95% when I left.
Sent from my SAMSUNG-SM-N910A using Tapatalk

frellingfrakker said:
I have this issue. I drove 3 hours with Google maps navigation today and my watch was dead upon arrival. It was at 95% when I left.
Sent from my SAMSUNG-SM-N910A using Tapatalk
Click to expand...
Click to collapse
Mine also died again after three hours of driving yesterday, and this is with the latest Android Wear update (on the phone). When I tried to charge it, I got constant Google app and Android Wear crashes. I was finally able to reset the watch to get it back to working.

JimSmith94 said:
Mine also died again after three hours of driving yesterday, and this is with the latest Android Wear update (on the phone). When I tried to charge it, I got constant Google app and Android Wear crashes. I was finally able to reset the watch to get it back to working.
Click to expand...
Click to collapse
Mine charged back up without an issue but Maps definitely kills the watch even with notifications blocked.
Sent from my iPad using Tapatalk

Thanks everybody. Send in a bug report through the Android wear app.
Does anybody have they latest update on their watch? 5.1.1?

frellingfrakker said:
Mine charged back up without an issue but Maps definitely kills the watch even with notifications blocked.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Mine has charged up normally before too, in fact it did last night. The one time it didn't was pretty scary though.
funkpod said:
Thanks everybody. Send in a bug report through the Android wear app.
Does anybody have they latest update on their watch? 5.1.1?
Click to expand...
Click to collapse
I'd like to know if this is fixed in 5.1.1 too. I'll ask in the Urbane section.

JimSmith94 said:
Mine has charged up normally before too, in fact it did last night. The one time it didn't was pretty scary though.
I'd like to know if this is fixed in 5.1.1 too. I'll ask in the Urbane section.
Click to expand...
Click to collapse
YES, definitely do that, thank you!!!

5.1.1 update - your experience with the new software ?

I found it very hard to find information from people who actually have the update in other threads because it is mixed with information on how to actually obtain and install the update.
So what are your impressions of tge 5.1.1 update ? Please only post if you have the update installed and running for at least few hours.
My impressions:
- Battery life is worse, like 30% worse with Wi-Fi detection on, even if mostly using Bluetooth.
- Still can't edit the canned response list Emoji drawing is a bad joke.
- I can't dismiss notifications with flick gestures (only hide them)
- Very smooth and responsive UI overall
- No annoying "Ok Google" text on watch face until you say "ok Google" 5 times

Battery life for me for 5 times better.... One thing, this enables 'always on' apps... I would check some of your apps and see what battery consumption is. I've been in my watch since about 10am and I have 53% left right now. Way better than anything I have ever gotten. This is with wifi on.

It's pretty fantastic for me. I have no complaints. The processor is old, but I'm very impressed with how optimized they've made it. The lag just doesn't interrupt my work flow, unlike with the Apple Watch at least. There's no major delay. Will likely be buying V2 or V3 depending on how I feel the life cycle for these devices will be.

Updated yesterday. I feel like the battery lasts less, but you have to give it 2-3 days to settle down. Liking the new features, but I don't think I'm gonna use Wi-Fi too much since it drains battery.

For now, I'm keeping WiFi, gestures, and ambient mode off. This way within a week I'll have a true comparison of battery life. Then I'm going to test each function and how it effects battery. I'll let everyone know how it goes.

Have the update one day now,
Good points:
-Smootness
-less buggy
-wifi when out of range
-wrist flick(great idea)
-Google maps maps
Bad points:
-Wrist flick is hard to perform correct (think it is a learning curve)
-When wifi is active on whatch and is connected but phone isn't connected to internet it still says it is connected.
-Laggier in first minutes after boot
-Lock screen sometimes activates when on wrist.
Overall i'am happy. Batterylife is to early to judge

I got the update yesterday after resetting my device. The first thing that I have noticed is that I can no longer dismiss notifications that only take up the bottom part of the screen. I have to pull the notification up and can then dismiss it. If this is what the developers intended, then that it is a major step backwards.
Also where do I setup which apps should stay "always on"?
Battery life after the update is disasterous, about 6% per hour but I need to give it a few days to sort itself out.
The dismissing of notifications is very much hit and miss and is impracticable.
At the moment I am not impressed with the update. Hopefully things will sort themselves out over the next few days.

For me, the update has been surprisingly good.
Good:
- Battery life (which I must admit, was my primary concern) is as good as it was prior to the update, even with the watch connected to WiFi.
- I love the flicking gestures, they work exactly as I imagined they would, although they're not as smart as they should (you can swipe available cards up and down, but when a card has multiple sub-cards, you can't scroll between them).
- Performance is great, specially considering it's a device with 512MB RAM, UI is still responsive enough and with very little lag.
- I love the new contact screen, it saves me a lot of time for quick calls when I can't remember the contact name (I normally use Google Now to call someone).
Bad:
- For the life of me, I haven't figured out how to enable always-on apps. It's one of the features I've been waiting for so eagerly, specially for Google Keep's checked notes (which I use A LOT).
- The WiFi connection is USELESS if you leave your phone home and find a protected WiFi network, because you NEED the phone to input the password. It kinda defeats the whole purpose.

One thing I noticed after the update is all of my hangouts threads became unmerged. Now each person has SMS/Hangouts as seperate threads. My one buddy experienced the same issue when his watch updated. Not sure why the software update would cause that, but it's upsetting.

Overall, I'm really liking the update. The only thing that's really bugging me is that you can't seem to dismiss notifications unless they're open. I'm used to being able to dismiss them immediately if I can get all the information I need from their title. Now, I actually have to swipe up first to open them, and only then can I dismiss them. It's not so bad that I can't live with it, but it is annoying.

The update has exceeded my expectations so far. I have only had it installed for about 12 hours. Battery life seems better. Worst case I don't think it has gotten any worse which was a huge concern because it hasn't been so wonderful. It seems to give more feedback and explanations so I'm not guessing as much. For example when I added a playlist it informed me that the battery needed more charge to download to the watch. Prior to the update I would have been scratching my head all day and then it would magically download when I charged up at night.
I really hope the WiFi works as advertised. I can think of many ways it could be useful to me. It seems like there are lots of times when I want notifications in case of an emergency because I'm a single dad but I also don't want to carry the phone with me.

My biggest annoyance with update is that now I have to open cards before they can be swiped away. Most times I can tell what a card is telling me and used to swipe them away without opening them.

Seems more responsive.
As others have said, removal of swiping / dismissing the previews was not a good call.
Not entirely sure, but looks like I won't be able to connect to my work WiFi which uses certificate based EAP-TLS authentication ? Will see when I'm back in the office next week.
Sent from my Lollipop TF700T

Do the other watches have the same issue (yeah, I'm calling it an issue instead of a feature) with the notification swiping? Or maybe this is something Motorola did thinking they were compensating somehow for the flat tire? Regardless, I hope there's an update to fix it, it just annoys the piss out of me every time.

My first day battery report.
Off charger at 9am, end of the day (11pm) 67%. This is with WiFi and ambient mode off so I can have a direct comparison to prior then update. But to me that is a huge improvement.

Has anybody figured out how to enable the App Always On feature?

I've updated my watch yesterday and wanted to let my watch get to 0% to calibrate the battery because of the new update. so I didn't put my watch off at night, and the next morging (today) my watch was 10% and the screen was totally black and it wasn't responding to the side button so I tried to hold it for 30 seconds to let it restart I saw the normal bootupscren but as soon it was staring the app it became black again. I now have let it charge to 100% and it it's responding perfectly again. Does anyone know what was wrong?
Thanks for your time!

user of android said:
I've updated my watch yesterday and wanted to let my watch get to 0% to calibrate the battery because of the new update. so I didn't put my watch off at night, and the next morging (today) my watch was 10% and the screen was totally black and it wasn't responding to the side button so I tried to hold it for 30 seconds to let it restart I saw the normal bootupscren but as soon it was staring the app it became black again. I now have let it charge to 100% and it it's responding perfectly again. Does anyone know what was wrong?
Thanks for your time!
Click to expand...
Click to collapse
I noticed the same behavior when mine was at 2%. It did not respond to screen touches and only switched on for about half a second after clicking the side button several (5 or more) times. It still took about 30 minutes for the watch to finally shut down. Maybe this is because of a very aggressive battery saving mode?
I must add that I did reset the watch after the 5.1.1 update was fully installed and wanted the battery to drain completely for the same reason you did: to recalibrate it.
Sent from my One S using XDA Free mobile app

Mister-B said:
Has anybody figured out how to enable the App Always On feature?
Click to expand...
Click to collapse
I'm thinking it may only be an AMOLED feature.

Mine had the same issue at 10%. I wonder if this is related to the performance issue Motorola was talking about.
I don't know if I am happy or sad that this is widespread. Hopefully they patch this up.

Lost 50% Battery Overnight

I've had the phone for near a week now and this is the first time doze has failed me. Left it alone at 10pm with about 50% left and looks like it went to zero in about four hours. (screenshot) I've tested other nights and it worked as expected -- wifi and cell coming on and off periodically. When checking usage, I was disturbed to find Facebook took up 25% of my battery. Is there some way Facebook is overriding doze?

dipson626 said:
I've had the phone for near a week now and this is the first time doze has failed me. Left it alone at 10pm with about 50% left and looks like it went to zero in about four hours. (screenshot) I've tested other nights and it worked as expected -- wifi and cell coming on and off periodically. When checking usage, I was disturbed to find Facebook took up 25% of my battery. Is there some way Facebook is overriding doze?
Click to expand...
Click to collapse
Wow. Looks like it was constantly awake during that time. You didn't happen to turn on photo syncing with Facebook?
Sent from my Nexus 5X using Tapatalk

Facebook is one of the worst when it comes to battery drains, I stopped using it and i just use a browser to stay logged in. Snapchat is also pretty bad, I think it was top 3 in my list while I slept earlier. First time happening, i turned off location on snapchat, ill see if that helps

btort1 said:
Facebook is one of the worst when it comes to battery drains, I stopped using it and i just use a browser to stay logged in. Snapchat is also pretty bad, I think it was top 3 in my list while I slept earlier. First time happening, i turned off location on snapchat, ill see if that helps
Click to expand...
Click to collapse
Same here. Facebook did this to me back when I had an HTC Hero, killed my battery in 8 hours no problem. The moment they changed the application to a "service" and had those wake-lock bugs I ditched it, never looked back.
No application should install itself as an always-on service unless its there for push messages. I decided that having my phone last all day was more important than getting facebook messages immediately.

EeZeEpEe said:
Wow. Looks like it was constantly awake during that time. You didn't happen to turn on photo syncing with Facebook?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Yea, it looks like it was constantly connected. Don't have photo syncing, but good thought.
btort1 said:
Facebook is one of the worst when it comes to battery drains, I stopped using it and i just use a browser to stay logged in. Snapchat is also pretty bad, I think it was top 3 in my list while I slept earlier. First time happening, i turned off location on snapchat, ill see if that helps
Click to expand...
Click to collapse
I stopped using Snapchat a while ago for that reason. Facebook, however, never really gave me a problem on my N6. It usually hovered around 6-7% use. No app is worth that much drain, let alone Facebook. If this is a normal occurrence, I'll probably just uninstall it.
ryan stewart said:
Same here. Facebook did this to me back when I had an HTC Hero, killed my battery in 8 hours no problem. The moment they changed the application to a "service" and had those wake-lock bugs I ditched it, never looked back.
No application should install itself as an always-on service unless its there for push messages. I decided that having my phone last all day was more important than getting facebook messages immediately.
Click to expand...
Click to collapse
Hopefully this was a one time occurrence since it worked fine on my N6. I've got no problem getting rid of it though, because like you said, I'd rather have my phone last all day (or night in this case).

Second Night Update
While I agree the Facebook app is bad, it looks like it was not the culprit. Uninstalled, doze again failed to kick in overnight and drained 18% over about seven hours. Not as bad as the 50% the first time, but still no bueno. It looks like Android OS kept it awake for seven hours. I know doze is pretty new, but there are some smart people here; anyone got any ideas/theories as to what's going on and remedy? Screenshots

I'm experiencing the same EXACT issues except I don't have Facebook installed

tjrocks91 said:
I'm experiencing the same EXACT issues except I don't have Facebook installed
Click to expand...
Click to collapse
Good to know I'm not alone! Even after uninstalling Facebook I've got the same problem with Android OS keeping it on. I'm considering clearing the cache and see if that changes anything.

Wow you have a perfectly diagonal line. Try a battery monitoring app. Might have more useful information as to what is draining overnight.
Sent from my Nexus 5X using Tapatalk

I did a factory reset and installed ~10 of my most used apps instead of restoring all apps and it's been sleeping fine now, no wakelocks
I also turned off WiFi and Bluetooth scanning, location services are on battery saving, and Google location reporting is off

I am willing to bet there are going to be some hiccups with marshmallow or even some newer hardware features of the phone and some apps until everything gets up to speed.

Just wondering, what build are you guys on? MDA89E or MDB08I?? I'm on MDA89E

I got 08I immediately after turning it on, Ive always lost like 1-2% overnight.
Maybe that is what the last-minute update was for, fixing that bug that you (unfortunately) found.

Battery drain

Hello.
I've bought a G4 in March and only 20 days ago I've started to notice a odd and big battery drain. Android tells me it's "Android SO" consumption. What once drained like up to 5%, now drains more than screen. 20 days ago, battery lasted like 34h. With same usage now, turned 12h.
I've uninstalled the apps I've installed meanwhile, used it in battery eco mode and even on airplane mode, without any luck.
4-5 days ago I've installed Wake Lock Detector (no root, but with the right permissions) and Better Battery Stats. From what I understand from the reports, they don't blame any specific app but show thousands of wakelocks on Android SO. I believe sometimes it can be normal (for instance, when I run with GPS and music). Anyway, maybe the issue lies here.
What I find really odd is that those 2 apps say that the phone is awake more than 90% of the time. Like 1h of deep sleep only per full battery.
I could understand if someone says that it's the battery that had a great use already, but not only has 7 months of use, but also the phone behaviour changed (Android SO was never so high before, at least constantly).
Thanks in advance for any advice!

JoaoAfonso said:
Hello.
I've bought a G4 in March and only 20 days ago I've started to notice a odd and big battery drain. Android tells me it's "Android SO" consumption. What once drained like up to 5%, now drains more than screen. 20 days ago, battery lasted like 34h. With same usage now, turned 12h.
I've uninstalled the apps I've installed meanwhile, used it in battery eco mode and even on airplane mode, without any luck.
4-5 days ago I've installed Wake Lock Detector (no root, but with the right permissions) and Better Battery Stats. From what I understand from the reports, they don't blame any specific app but show thousands of wakelocks on Android SO. I believe sometimes it can be normal (for instance, when I run with GPS and music). Anyway, maybe the issue lies here.
What I find really odd is that those 2 apps say that the phone is awake more than 90% of the time. Like 1h of deep sleep only per full battery.
I could understand if someone says that it's the battery that had a great use already, but not only has 7 months of use, but also the phone behaviour changed (Android SO was never so high before, at least constantly).
Thanks in advance for any advice!
Click to expand...
Click to collapse
Suggest you check out and install the apps recommended apps on ✭[GUIDE][26-07-2016]Extreme Battery Life Thread(Greenify+Amplify+Power Nap)✭ at https://forum.xda-developers.com/android/general/guide-extreme-battery-life-t3095884
Read the OP thoroughly for each app discussed. The wakelock situation can be helped a good deal with Amplify and Greenify in particular - the paid versions - but I would also install AppOppsXposed - all require Xposed which requires root in order to be installed and I would also check out Power Nap to see if any incremental improvement.
You may a also want to run a malware scan ...

Thanks for the info. I checked it earlier, but most of those apps only run in root phones. I'm waiting for official Nougat in G4, mostly because haven't saw yet a Nougat image for this device without any problems, like camera not working, or such. I wouldn't mind to pay for apps that could work on this, but I want to avoid rooting. I guess I rather put Android 7, that has a bigger chance to even solve this problem, than root at this time.
Haven't said earlier but did a factory reset yesterday and device kept the behavior... I believe a hard reset would reduce almost to 0 the eventual malware problem.
No obvious alternatives for not rooted phones? Haven't this happened to someone else and been solved?
Thanks!

I had the same problem a few weeks ago...i was loosing ~30% of the battery at night with no wifi/data/gps etc. I tried everything...factory resets, different roms, greenfy & those kind of apps but the phone would not sleep. The last thing i tried was a factory reset and after i logged into my gmail account i set the phone as a new device...so no restoring apps and backups from my gmail account. Now everything is ok, my phone sleeps like a baby. I've read somewhere that it might be related with the syncing & backups....i don't really know, but you can give it a try.

uzadragos said:
I had the same problem a few weeks ago...i was loosing ~30% of the battery at night with no wifi/data/gps etc. I tried everything...factory resets, different roms, greenfy & those kind of apps but the phone would not sleep. The last thing i tried was a factory reset and after i logged into my gmail account i set the phone as a new device...so no restoring apps and backups from my gmail account. Now everything is ok, my phone sleeps like a baby. I've read somewhere that it might be related with the syncing & backups....i don't really know, but you can give it a try.
Click to expand...
Click to collapse
Haven't tried that yet. I'll try to remove and add the device again, to avoid the pain of a new hard reset.
To have a reference, it was good to know an average percentage of other G4 deep sleep. If everyone has around 90%... maybe it's not a problem at all. The "sleep like a baby" is which percentage? Also, there are plenty babies that wake up hourly crying for a period of time...
Thanks for the tip!

JoaoAfonso said:
Haven't tried that yet. I'll try to remove and add the device again, to avoid the pain of a new hard reset.
To have a reference, it was good to know an average percentage of other G4 deep sleep. If everyone has around 90%... maybe it's not a problem at all. The "sleep like a baby" is which percentage? Also, there are plenty babies that wake up hourly crying for a period of time...
Thanks for the tip!
Click to expand...
Click to collapse
My phone was awake >90% of the time(when screen was off), even in flight mode, when it had "the problem". Now things are back to normal...~2% awake when the screen is off.

Hello again.
Tried to reset a couple more times, tried to remove old phone register in my gmail account, but I wasnt successful.
How you did the
"The last thing i tried was a factory reset and after i logged into my gmail account i set the phone as a new device..."
?
Once it asks for my account, I'm not able to set it's a new device. I also did no restores... Is there a way to disconnect devices from Google account? I was only able to do so in devices I connected like one month, or more, ago, but not able to do so in the device I'm using at the moment.
One thing I did not try but that would confirm your thesis is to register device with a new account.
Anyone with an alternative?
I'm hoping LG really releases Nougat for G4 in 2017...

Today, the device returned to normality without any intervention. I can only imagine the following: since last factory reset I've disabled some apps I didn't used, like Google books, or Google music, but only yesterday I did a normal reboot (due to huge battery drain...). Eventually, some updates just took place after this reset. Anyway, even having imagined this theory, I don't believe in it. Wizardry, I bet.