Oh! That's actually a great way to find out about that! I've been fiddling around to get more info but this works (and without root).
How did you combine the messages into number of occurences? Manually, or is there a built-in way to do this?
OOS 4.5.5 nearly never in Deep Sleep
- Thread starter TheColin21
- Start date
How did you combine the messages into number of occurences? Manually, or is there a built-in way to do this?
It's present in the generated file InternalStorage/oem_log/<date with dashes>_dumpsys batterystats.log
Under the "All wakeup reasons" section. Around it there are other interesting sections.
Do any of you use Google Assistant? I had that feature on with it constantly providing cards, weather updates, etc but once I disabled that it was able to go into deep sleep. Maybe something to try?
I believe that's more related to Google Now / Google, than the assistant if I'm not mistaken.
I'm fiddling around with doze and aggressive doze right now. It helps a bit but not enough yet.
I just use Greenify and check everything except what I absolutely want to get updated on. Mine enters sleep no problem.
Big thanks for pointing to the right tools under developer options.
I have the same wakelock I think:
Wakeup reason Abort
ending Wakeup Sources: ipc00000128_ColorBalanceThr : 1h 27m 42s 815ms (17917 times) realtime
Wakeup reason 53:qcom,glink-smem-native-xprt-rpm:52:qcom,glink-smem-native-xprt-dsps: 1h 18m 19s 768ms (13450 times) realtime
Wakeup reason unknown: 50m 26s 380ms (9622 times) realtime
Wakeup reason Abort:Last active Wakeup Source: ipc00000128_ColorBalanceThr: 29m 38s 648ms (5420 times) realtime
Wakeup reason Abort:noirq suspend of alarmtimer device failed: 8m 27s 104ms (1863 times) realtime
Wakeup reason Abort:alarmtimer device failed to power down: 8m 21s 60ms (1760 times) realtime
Wakeup reason Abort:Some devices failed to suspend, or early wake event detected: 50m 24s 13ms (1711 times) realtime
By it's name, it looks like a Qualcomm (modem) thing?ending Wakeup Sources: ipc00000128_ColorBalanceThr : 1h 27m 42s 815ms (17917 times) realtimeWakeup reason 53:qcom,glink-smem-native-xprt-rpm:52:qcom,glink-smem-native-xprt-dsps: 1h 18m 19s 768ms (13450 times) realtime
Wakeup reason unknown: 50m 26s 380ms (9622 times) realtime
Wakeup reason Abort:Last active Wakeup Source: ipc00000128_ColorBalanceThr: 29m 38s 648ms (5420 times) realtime
Wakeup reason Abort:noirq suspend of alarmtimer device failed: 8m 27s 104ms (1863 times) realtime
Wakeup reason Abort:alarmtimer device failed to power down: 8m 21s 60ms (1760 times) realtime
Wakeup reason Abort:Some devices failed to suspend, or early wake event detected: 50m 24s 13ms (1711 times) realtime
I have done a full clean flash with the OxygenOS 4.5.7 Full ROM (1.5GB). I was hoping this would eliminate any previous problems caused by the numerous OTA's which have been issued. But the problem appears almost every day.
Did you do any further research, actions to solve it, or pointed OnePlus support towards this?
Last edited:
Wakeup reason Abort
So what's up with this one then?
Just wanted to join the wakelock club, in around 6 hours on 4.5.8:Big thanks for pointing to the right tools under developer options.
I have the same wakelock I think:
Wakeup reason AbortBy it's name, it looks like a Qualcomm (modem) thing?
Wakeup reason 53:qcom,glink-smem-native-xprt-rpm:52:qcom,glink-smem-native-xprt-dsps: 1h 18m 19s 768ms (13450 times) realtime
Wakeup reason unknown: 50m 26s 380ms (9622 times) realtime
Wakeup reason Abort:Last active Wakeup Source: ipc00000128_ColorBalanceThr: 29m 38s 648ms (5420 times) realtime
Wakeup reason Abort:noirq suspend of alarmtimer device failed: 8m 27s 104ms (1863 times) realtime
Wakeup reason Abort:alarmtimer device failed to power down: 8m 21s 60ms (1760 times) realtime
Wakeup reason Abort:Some devices failed to suspend, or early wake event detected: 50m 24s 13ms (1711 times) realtime
I have done a full clean flash with the OxygenOS 4.5.7 Full ROM (1.5GB). I was hoping this would eliminate any previous problems caused by the numerous OTA's which have been issued. But the problem appears almost every day.
Did you do any further research, actions to solve it, or pointed OnePlus support towards this?
Code:
All wakeup reasons:
Wakeup reason 53:qcom,glink-smem-native-xprt-rpm:52:qcom,glink-smem-native-xprt-dsps: 1h 19m 27s 492ms (11848 times) realtime
Wakeup reason Abort:Pending Wakeup Sources: qcom_rx_wakelock : 4m 29s 139ms (923 times) realtime
Wakeup reason Abort:Last active Wakeup Source: qcom_rx_wakelock: 2m 49s 937ms (632 times) realtime
Wakeup reason Abort:Some devices failed to suspend, or early wake event detected: 16m 45s 573ms (565 times) realtime
Wakeup reason Abort:Last active Wakeup Source: ipc00000128_PowerManagerSer: 3m 34s 185ms (502 times) realtimeIt seems mine are different, any idea what ipc00000169_PowerManagerSer might be related to?
Code:
All wakeup reasons:
Wakeup reason Abort:Pending Wakeup Sources: ipc00000169_PowerManagerSer : 1h 18m 49s 653ms (17208 times) realtime
Wakeup reason Abort:Last active Wakeup Source: ipc00000169_PowerManagerSer: 49m 14s 219ms (10654 times) realtime
Wakeup reason unknown: 28m 40s 13ms (5153 times) realtime
Wakeup reason 53:qcom,glink-smem-native-xprt-rpm:50:qcom,glink-smem-native-xprt-modem: 15m 15s 79ms (894 times) realtime
Wakeup reason 53:qcom,glink-smem-native-xprt-rpm:52:qcom,glink-smem-native-xprt-dsps: 4m 7s 324ms (788 times) realtimeIt is a blind guess, but I think it might be the Inter Process Communication protocol that handles the wakelocks from the user applications. I have seen the PowerManagerService wakelocks other times as well.
You could try digging further with Battery Historian to see if something comes up there.
I've opened a support ticket at OnePlus, they have asked me to do a hard reset and at first boot setup, to install no apps at all. Running now for a day without any non-ROM apps, and battery life is very well, no wakelock so far.
But the question rises: which app has gone rogue? My first guess would be Google Fit.
Attachments
Here my list of apps I installed on the OnePlus 5, maybe we can find an app which we have in common and find the app which causes a 'Android OS' wakelock.
Code:
AndSMB (samba client)
ClockSync
CPU Spy
Gmail
Google
Google Drive
Google+
GPS Status & Toolbox
ING Bankieren
Maps: Navigatie en OV (Beta)
NOS
Nova Launcher
NPO
Photo Editor
Speedtest.net
Twitter
WhatsApp Messenger (Beta)
Wifi Analyzer
XiiaLive™ - Internet Radio
YouTube
CatLog - Logcat Reader!
Chrome-browser - Google
Fing - Netwerktools
Flightradar24 Flight Tracker
Gboard: het Google-toetsenbord
Google Agenda
[B]Google Fit - Fitnesstracking[/B]
Google Foto's
Google Home
Google Keep
Google Now Launcher
Google Play Services
Google Tekst-naar-spraak
Hangouts
Klok
Marktplaats
Microsoft Word
NS Reisplanner Xtra
Onkyo Remote
Spotify Music
Calculator
Exchange Services
Google Authenticator
Meteogram Weer Widget
Microsoft OneDrive
My Citroën – Onderhoud, reizen
OpenVPN Connect
WiFiAnalyzer (open-source)
WinZip – Zip UnZip ToolNice idea!
This is the list of the apps that we have in common.
Code:
Gmail
Google
ING Bankieren (I actually have the IT version)
Twitter
WhatsApp Messenger (Beta)
YouTube
Google Maps
Chrome-browser - Google
Gboard: het Google-toetsenbord
Google Agenda
Google Foto's
Google Keep
Google Play Services
Calculator
Exchange Services
OpenVPN ConnectCould it be ING/OpenVPN?
Thanks for your apps list we have in common.
I was asked to run 2 days without any apps. So I've now a device with only pre-installed apps (in the ROM). In this collection, there are quite a lot Google Apps, which don't cause the wakelock so far (almost two days running with this list):
Code:
Chrome-browser - Google
Gboard: het Google-toetsenbord
Gmail
Google
Google Calendar
Google Drive
Google Duo
Google Photos
Google Play Films
Google Play Music
Google Play Services
Google TalkBack
Google Text to Voice
Maps: Navigatie en OV (Beta)
OnePlus Icon Pack (Unreleased)
OnePlus Icon Pack - Round (Unreleased)
OnePlus Icon Pack - Square (Unreleased)
OnePlus Launcher (Beta)
YouTubeIf I filter this list with your list, the following suspects remain:
Code:
ING Bankieren (I actually have the IT version)
Twitter
WhatsApp Messenger (Beta)
Google Keep
Calculator
[B]Exchange Services[/B]
OpenVPN Connect
Last edited:
Nope, no exchange services for me. As a matter of fact, it seems that I don't even have the APK installed.
I also tried removing OpenVPN Connect, but I still have wakelocks.
Battery Historian looked nice but doesn't work for me on OP5. Do you have it running?
I've reported it at https://github.com/google/battery-historian/issues/127#issuecomment-320889977
---------- Post added at 04:25 PM ---------- Previous post was at 04:21 PM ----------
I'm running ING Bankieren too, as well as OpenVPN. I do have Exchange services enabled as my work uses Office365 for their emailsolution (which worked fine on OP3 for me btw, so I tend to lean towards something else). Also using Whatsapp Beta and using Nova launcher.
I'm really curious about your experiment running after factory reset as I was planning on doing that as well. Perhaps we can chat offlist about this. I'm @wschoot on telegram
No I can't get it to work either.
It seems that there is an issue with quotes.
As soon as I have time I will try to script the quoting around that part, to see if this solves the issue.
Your list is with Exchange Services on it. So that assumes you have the actual APK installed.
So we have at least three suspect apps on the short list:
ING Bankieren (ING Banking)
OpenVPN
Exchange Services
and number four, although weak: Whatsapp Beta. But this one is so popular, I don't think it's that bad...
For OpenVPN and Exchange Services, that two were uninitialised at my device, I haven't start them for the first time.
For ING Bankieren, I have also the companion 'Mobile Payments' app for handling NFC payments.
I'm running almost two days without charging, so definitely no wakelock issues so far... I will post my results tomorrow.
Yesterday evening I had reached 2 days on one charge (93% to 8% = 85%). SOT of 2h30m, light usage throughout the days, 4-5 hours from home, ~1 hour of Bluetooth paired to the car. Very well.
Conclusion
So no long-running wakelocks. I already installed Whatsapp and no problems so far. Conclusion for now is to not restore your apps on first boot setup. I think some garbage or data is also coming through during restore of previously installed apps causing strange, seemingly unrelated, hard to diagnose wakelocks.
I will now gradually install most-needed apps, and measuring if any problems will occur.
At night, with doze enabled, the drain was around 0.7% per hour:
Full details:
All wakeup reasons:
Conclusion
So no long-running wakelocks. I already installed Whatsapp and no problems so far. Conclusion for now is to not restore your apps on first boot setup. I think some garbage or data is also coming through during restore of previously installed apps causing strange, seemingly unrelated, hard to diagnose wakelocks.
I will now gradually install most-needed apps, and measuring if any problems will occur.
At night, with doze enabled, the drain was around 0.7% per hour:
Code:
#75: +1h30m24s943ms to 83 (screen-off, power-save-off, device-idle-on)
#76: +1h41m7s261ms to 84 (screen-off, power-save-off, device-idle-on)
#77: +1h44m21s184ms to 85 (screen-off, power-save-off, device-idle-on)
#78: +1h34m24s250ms to 86 (screen-off, power-save-off, device-idle-on)
#79: +1h34m14s644ms to 87 (screen-off, power-save-off, device-idle-on)
#80: +1h9m5s927ms to 88 (power-save-off)
Code:
Statistics since last charge:
System starts: 0, currently on battery: true
Estimated battery capacity: 3300 mAh
Time on battery: 2d 0h 21m 44s 286ms (100.0%) realtime, 5h 55m 57s 196ms (12.3%) uptime
Time on battery screen off: 1d 21h 49m 57s 926ms (94.8%) realtime, 3h 24m 10s 827ms (7.0%) uptime
Total run time: 2d 0h 21m 44s 284ms realtime, 5h 55m 57s 194ms uptime
Battery time remaining: 4h 35m 0s 40ms
Discharge: 0 mAh
Screen off discharge: 0 mAh
Screen on discharge: 0 mAh
Start clock time: 2017-08-06-21-48-26
Screen on: 2h 31m 46s 360ms (5.2%) 95x, Interactive: 2h 31m 21s 848ms (5.2%)
Screen brightnesses:
dark 2h 21m 15s 441ms (93.1%)
dim 1m 23s 355ms (0.9%)
medium 3m 48s 599ms (2.5%)
bright 5m 18s 965ms (3.5%)
Device light idling: 19h 33m 22s 809ms (40.4%) 62x
Idle mode light time: 19h 24m 14s 455ms (40.1%) 159x -- longest 18m 24s 86ms
Device full idling: 19h 1m 28s 497ms (39.3%) 6x
Idle mode full time: 18h 57m 26s 196ms (39.2%) 14x -- longest 3h 57m 18s 279ms
Connectivity changes: 186
Total full wakelock time: 7m 17s 954ms
Total partial wakelock time: 1h 41m 9s 658ms
Mobile total received: 6.99MB, sent: 1.56MB (packets received 8525, sent 8794)
Phone signal levels:
none 2m 45s 816ms (0.1%) 21x
poor 4h 39m 46s 990ms (9.6%) 279x
moderate 21h 17m 15s 681ms (44.0%) 665x
good 17h 53m 0s 983ms (37.0%) 747x
great 4h 28m 54s 816ms (9.3%) 353x
Signal scanning time: 0ms
Radio types: (no activity)
Mobile radio active time: 1h 22m 23s 770ms (2.8%) 367x
Mobile radio active unknown time: 6m 55s 39ms (0.2%) 60x
Mobile radio active adjusted time: 3s 109ms (0.0%)
Radio Idle time: 6h 31m 23s 794ms (57.3%)
Radio Rx time: 4h 18m 34s 517ms (37.8%)
Radio Tx time: 33m 28s 734ms (4.9%)
[0] 18m 15s 99ms (54.5%)
[1] 29s 594ms (1.5%)
[2] 12m 4s 667ms (36.1%)
[3] 2m 0s 183ms (6.0%)
[4] 39s 191ms (2.0%)
Radio Power drain: 0mAh
Wi-Fi total received: 1.07GB, sent: 1016.26MB (packets received 1002767, sent 1112825)
Wifi on: 2d 0h 21m 44s 286ms (100.0%), Wifi running: 2d 0h 21m 44s 286ms (100.0%)
Wifi states: (no activity)
Wifi supplicant states:
disconn 4h 46m 27s 604ms (9.9%) 307x
scanning 3m 19s 20ms (0.1%) 299x
associating 326ms (0.0%) 8x
associated 391ms (0.0%) 8x
4-way-handshake 200ms (0.0%) 8x
group-handshake 330ms (0.0%) 8x
completed 1d 19h 31m 56s 415ms (90.0%) 8x
Wifi signal levels:
level(1) 12s 85ms (0.0%) 1x
level(2) 40m 28s 814ms (1.4%) 31x
level(3) 22h 3m 51s 157ms (45.6%) 63x
level(4) 1d 1h 37m 12s 230ms (53.0%) 38x
WiFi Idle time: 3h 16m 21s 96ms (98.7%)
WiFi Rx time: 1m 3s 287ms (0.5%)
WiFi Tx time: 1m 25s 975ms (0.7%)
WiFi Power drain: 0mAh
Bluetooth total received: 966B, sent: 30.62KB
Bluetooth scan time: 42s 49ms
Bluetooth Idle time: 4m 40s 856ms (38.1%)
Bluetooth Rx time: 7m 25s 474ms (60.4%)
Bluetooth Tx time: 11s 787ms (1.6%)
Bluetooth Power drain: 3.83mAh
Device battery use since last full charge
Amount discharged (lower bound): 84
Amount discharged (upper bound): 85
Amount discharged while screen on: 26
Amount discharged while screen off: 59
Code:
All wakeup reasons:
Wakeup reason 53:qcom,glink-smem-native-xprt-rpm:76:WLAN_CE_2: 36m 7s 772ms (5052 times) realtime
Wakeup reason Abort:Pending Wakeup Sources: qcom_rx_wakelock : 12m 30s 355ms (2078 times) realtime
Wakeup reason 53:qcom,glink-smem-native-xprt-rpm:91:7781b8.qcom,mpm: 4m 52s 207ms (1169 times) realtime
Wakeup reason 53:qcom,glink-smem-native-xprt-rpm:50:qcom,glink-smem-native-xprt-modem: 5m 9s 190ms (735 times) realtime
Wakeup reason 53:qcom,glink-smem-native-xprt-rpm:52:qcom,glink-smem-native-xprt-dsps: 4m 4s 992ms (562 times) realtime
Wakeup reason Abort:Some devices failed to suspend, or early wake event detected: 14m 0s 638ms (506 times) realtime
Wakeup reason unknown: 2m 33s 368ms (428 times) realtime
Wakeup reason Abort:Last active Wakeup Source: qcom_rx_wakelock: 1m 48s 809ms (289 times) realtime
Wakeup reason Abort:noirq suspend of c171000.uart device failed: 1m 35s 744ms (237 times) realtime
Wakeup reason Abort:Last active Wakeup Source: PowerManagerService.WakeLocks: 43s 76ms (111 times) realtime
Wakeup reason Abort:Last active Wakeup Source: eventpoll: 34s 232ms (96 times) realtime
Wakeup reason Abort:Pending Wakeup Sources: PowerManagerService.WakeLocks : 16s 334ms (85 times) realtime
Wakeup reason Abort:Pending Wakeup Sources: bluetooth_timer wcnss_filter_lock : 1m 31s 397ms (77 times) realtime
Wakeup reason 53:qcom,glink-smem-native-xprt-rpm: 34s 551ms (76 times) realtime
Wakeup reason Abort:Pending Wakeup Sources: ipc00000176_PowerManagerSer : 21s 587ms (63 times) realtime
Wakeup reason Abort:noirq suspend of 18800000.qcom,icnss device failed: 21s 541ms (60 times) realtime
Wakeup reason 53:qcom,glink-smem-native-xprt-rpm:47:ipa: 13s 748ms (52 times) realtime
Wakeup reason 53:qcom,glink-smem-native-xprt-rpm:91:7781b8.qcom,mpm:163::285:soc:fpc_fpc1020: 23s 322ms (40 times) realtimeAttachments
Last edited:
Thanks for your very thorough and detailed analysis!
Conclusion for now is to not restore your apps on first boot setup
If this really is the case, it might be my reason as well, I usually restore my phone this way as it's a major timesaver.
Looking at your batterygraph, you have wifi enabled during nighttime?
~2h30m SOT isn't a whole lot but running two days without a charge explains the lower SOT.
SOT is overrated as a compareable metric anyway.
Code:
Discharge step durations:
#0: +17m41s502ms to 64 (power-save-off)
#1: +15m38s704ms to 65 (power-save-off)
#2: +6m42s569ms to 66 (power-save-off, device-idle-off)
#3: +10m51s482ms to 67 (power-save-off, device-idle-off)
#4: +12m33s771ms to 68 (power-save-off, device-idle-off)
#5: +11m48s357ms to 69 (power-save-off, device-idle-off)
#6: +13m4s259ms to 70 (power-save-off, device-idle-off)
#7: +18m28s978ms to 71 (screen-off, power-save-off)
#8: +10m6s122ms to 72 (power-save-off, device-idle-off)
#9: +4m30s932ms to 73 (power-save-off, device-idle-off)
#10: +4m12s838ms to 74 (screen-on, power-save-off, device-idle-off)
#11: +4m6s857ms to 75 (screen-on, power-save-off, device-idle-off)
#12: +7m58s656ms to 76 (power-save-off, device-idle-off)
#13: +5m49s178ms to 77 (screen-on, power-save-off, device-idle-off)
#14: +7m8s934ms to 78 (power-save-off, device-idle-off)
#15: +5m28s827ms to 79 (power-save-off, device-idle-off)
#16: +2m18s464ms to 80 (screen-on, power-save-off, device-idle-off)
#17: +3m24s674ms to 81 (screen-on, power-save-off, device-idle-off)
#18: +3m18s660ms to 82 (screen-on, power-save-off, device-idle-off)
#19: +3m6s623ms to 83 (screen-on, power-save-off, device-idle-off)
#20: +3m12s639ms to 84 (screen-on, power-save-off, device-idle-off)
#21: +3m0s602ms to 85 (screen-on, power-save-off, device-idle-off)
#22: +4m0s796ms to 86 (screen-on, power-save-off, device-idle-off)
#23: +44m30s120ms to 87 (power-save-off, device-idle-off)
#24: +1h12m1s770ms to 88 (screen-off, power-save-off)
#25: +1h16m2s306ms to 89 (screen-off, power-save-off)
#26: +1h10m35s614ms to 90 (screen-off, power-save-off)
#27: +1h10m57s423ms to 91 (screen-off, power-save-off)
#28: +1h0m59s975ms to 92 (screen-off, power-save-off)
#29: +1h3m19s280ms to 93 (power-save-off)
#30: +5m31s113ms to 94 (power-save-off, device-idle-off)
#31: +5m13s73ms to 95 (screen-on, power-save-off, device-idle-off)
#32: +4m54s980ms to 96 (screen-on, power-save-off, device-idle-off)
#33: +3m0s591ms to 97 (screen-on, power-save-off, device-idle-off)
Estimated screen off time: 4d 6h 31m 41s 100ms
Estimated screen on time: 6h 22m 2s 800ms
Last edited:
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone