yashsingh1/xdaforums huggingface dataset:
[BetterBatteryStats] foosion:
Do you suspect systemui because it's at the top of the alarms list and is leading wakeups by a large margin?

Touch sounds are off.

Is changing the time just for testing?

There does not seem to be a way to clear device cache on a Pixel 2 running Oreo. It's not on the recovery menu. I've turned off device and restarted numerous times while testing, and done a factory reset, to no avail. After the factory reset, I restored from Google's backup and restore.

I don't seem to have any brightness settings similar to "never"

I don't have a System UI tuner beyond the OS. I don't have a custom launcher.

I have a lot of apps, but they seem to have been quiet.

I'll try turning off location.

Bluetooth is off. I can't handle turning off sync.

I'll try Greenify, but isn't it for misbehaving apps and we haven't identified any misbehaving apps?

The apps and settings on this phone are essentially cloned from a Nexus 6P (setup wizard cable connection). The 6P does not have these issues. The only significant difference is that the 6P is rooted and running adaway (replace hosts file to eliminate ads).

Last night I updated the OS to 8.1 beta. No change in battery. Same sawtooth usage pattern.

FWIW, many Pixel 2 owners report minimal overnight drain, even with location, BT, sync, etc, etc.

Do you have any idea what RCS phone might be (see gsam screenshot)?

EDIT: is there any reason to believe there's a hardware problem? I might be able to RMA the phone for unrelated (and not really serious) reasons.
[BetterBatteryStats] Tundraswan:
Thanks you so much for taking your time out to analyse :o

I don't have Tencent/WeChat installed :eek: I'm scared now, are the Chinese hacking me!? :eek: I checked my phone and can't see that I have any other Tencent apps installed. Could this be OnePlus' analytics? I had a Magisk module activated to stop OPDeviceManager.apk and .odex systemlessly, could the module be doing more harm than good? I will try running with it disabled.

I found that I had the "Mobile data always active" developer option on! Which means that my mobile data was staying connected even when on Wi-Fi. I bet that had something to do with what you saw in the logs, so I've turned that off.

I don't have a clear toggle anywhere in settings for "Always on display", I tried turning it off using this code: *#99#

I've frozen the stock calendar using Titanium backup, that should be good enough right?

Will monitor and see if these changes help, thanks again! :)
[BetterBatteryStats] ipredatorv:
He got our replies mixed up in his quote haha.

Yeah thanks a huge lot fossils, WeChat is pretty filthy because you can't really limit the drain without crippling the functionality of its Push Voice & Video calls, and I unfortunately need it daily for work. Maybe Xposed with Amplify could help.
[BetterBatteryStats] Tundraswan:
Oh, so was the second part of fossil's post analysis for me? :confused: :-

Wakelocks:

Anywhere you see 'Firebase' in this section next to an app name, your device is being held awake for data collection.

Download a serivce disabler and check each installed app, and disable every instance of 'Package Measurement', 'Firebase', and 'Analytics' you find in each app. That should cut down on some of the chatter in the background.

qcom_rx_wakelock: Try a static IP, your Wi-Fi network may be crowded. Or try swtitching bands first (2.4g- 5g).

Alarms:

com.android.internal.telephony.data-stall. Poor data connection. Why this is happening while Wi-Fi is present is not clear to me.

Your installed apps are all using data during idle. I would suggest removing all uneeded apps, as this will lessen the drain on the battry immediately. Also, disabling Location and Sync wiill help also.
[BetterBatteryStats] suvishalreddy9:
Made New Dump with new francokernel before your suggestions(I will implement them)
[BetterBatteryStats] suvishalreddy9:
dump with changed kernel and few tweaks (10hrs ideal from 95%)

settings & tweaks used to generate this dump file

1)Turned off GCM push for greenified apps

2)flashed francokernel and using few francokernel app tweaks (screenshots posted) I did an overkill with no of screenshots sorry :rolleyes:

-underclocked the cpu by 25% (I generally don't play games)

-underclocked the Gpu I put the screenshot of the interface

3)Installed naptime and activated it with re-apply doze after wakeups (with default advance settings)

4)installed SERVICELY but still dont know how to use it will try in future

5)under battery optimization -I kept greenify,naptime,BBS,amplify,servicely to NOT OPTIMISED i felt it will hamper apps potential to save battery :confused: (SS attached) Should i optimise them also

6) Included wakelockdoctor screenshots and all extra info available it easy I renamed each screenshot to make it easier to read

I hope it's not annoying

7)would be happy to add your valuable suggestions and any other tweaks

i want to improve ideal drain this week then active drain to to best settings possible with any major loss in performance [MENTION=4138220]fossils-n-dents[/MENTION] [MENTION=1330150]chamonix[/MENTION] @v7

All healthy suggestions are welcomed from everyone :)
[BetterBatteryStats] fossils-n-dents:
System UI is an offender, however, it's actually a process using system UI.

I have one last trick: (There aren't many instant workarounds for the non-rooted)

1. Clear data in Google Play Services, Google Maps, and Google Play Store.

2. Go to Settings> Power> Battery Optimization> Reset App Preferences...Reboot.

3. In Settings, turn off Body Sensors, Vibration, Location, disable 'Backup and Reset'. (You can enable later)

Have you tried running Safe Mode to see if the problem perssists? If not, your issue can be traced to an app. If it persists, you may have to go the warranty route.

Rich Communication Services is a communication protocol between mobile-telephone carriers and between phone and carrier, replacing SMS messages with a text-message system that is more rich, provide phonebook polling (for service discovery), and transmit in-call multimedia.

In a nutshell, RCS is a set of communication standards for SMS, MMS and calling that will make text messages look and feel more like Google Hangouts or Facebook Messenger. VoLTE it should remove RCS, but messaging will come through stock sms only, so apps like Textra may not work.

Greenify also steps up the elapsed time for devices to enter doze mode with the 'Automated Doze' feature enabled.

Sorry for the mix up(s). Usually, I can answer most members questions from work. Yesterday, they made me actually work. I got in late, and fatigue must have taken over. My apologies.

I messed up the replies. My aplogies. And Thank You for trusting my opinion.:good:

I mixed up my replies. My apologies.

I found that I had the "Mobile data always active" developer option on! Which means that my mobile data was staying connected even when on Wi-Fi. I bet that had something to do with what you saw in the logs, so I've turned that off.

I don't have a clear toggle anywhere in settings for "Always on display", I tried turning it off using this code: *#99#

Yes, that should be fine. Did you..Force stop> Clear App Data> Freeze?

Will monitor and see if these changes help, thanks again! :)[/QUOTE]

My Pleasure. good Luck.:good:

Yes, the second part is for you also. I had a rough night. My apologies.
[BetterBatteryStats] suvishalreddy9:
[MENTION=4138220]fossils-n-dents[/MENTION]

:good:
[BetterBatteryStats] foosion:
Alas, there's no TWRP yet available for the Pixel 2, so no root.

I don't have that setting in Oreo. I do have battery optimization and everything is optimized other than some system items for which battery optimization is not available.

I ran it once. Idle discharge was about 1.2%/hour and gsam change over time showed the same sawtooth pattern shown in the gsam screenshot I posted. I'm going to try it again.

I'm guessing there is some google app or process that wakes up periodically and that's what's causing the problem. I'm now charging to full and will run safe mode again.

I'm not sure if what gsam is showing as RCS phone is really RCS. I've disabled everything that seems to be a messaging app and let the phone sit without running anything. gsam nonetheless show "RCS phone" at the top of the list (see screenshots I posted). I can't figure out what app is causing RCS phone to show up on the list.

Do you mean Automated Hibernation? I've enabled that, aggressive doze and wake-up tracking and cut-off. Anything else I should be doing in Greenify?
[BetterBatteryStats] fossils-n-dents:
No, a backup of your system if something should go wrong. If you have MyAndroidtools, you won't need to use Servicely.

Sorry about the WhatsApp/ browser thing, I don't use the app.
[BetterBatteryStats] suvishalreddy9:
[MENTION=4138220]fossils-n-dents[/MENTION]

from your old post

*I also use App Ops* I tried appopsxposed I can use it from settings but when i tap app ops app icon it crashes for Google Play Services to select the 'Prevent Phone From Sleeping' option. =Deny (Optional) any alternative for app ops it keeps crashing on 7.1.2 i think it is not nougat supported . but i did not understand what exactly to do here?

Google Play Services' under 'Broadcast Reciever' tab:

*packagemeasurementservice(i dont have that anyway) & packagemeasurementreciever will reset upon any reboot. I simply reenable them. They help towards lessening 'com.google.android.gms' issues for those that have them. should they be disabled or enabled?

Locate and disable any entry in all installed/ downloaded apps on your device that have the following in it's description in the 'Service' and 'Broadcast Reciever' entry: installed/ downloaded is not avilable???

appmeasurement, firebase, campaigntracking, analytics, installrefer, adservice.

all your changes from thread have been implemented, so is amplify still worth it now or useless ? (can it squeeze out any extra %)?

I reduced no of apps from 110 to 60 so i thing things will improve now with greenify+nap Time+25%cpu underclocked+gpu underclocked+ MyAndroidTools Pro (gms disabled stuff) I think this is best config possiable i will generate next dump without amplify and one with amplify to see if there is any significant difference
[BetterBatteryStats] foosion:
[MENTION=4138220]fossils-n-dents[/MENTION] After using Greenify with Automated Hibernation, Aggressive Doze and Wake-up tracking and cut-off, plus running DNS66, my phone is down to using 0.2%/hour for the past four hours. I'm testing with location services and sync on.

I'm going to charge back to 100%, reboot and see what happens overnight.
[BetterBatteryStats] fossils-n-dents:
[MENTION=4693971]foosion[/MENTION];74362539]

I forgot you were running stock. No worries about backups. No way to reset App Preferences anymore, huh? Google is slowly closing every avenue for the user to make the most minimal of adjustments. That was one of the major selling points of Android, the ability to fine tune everything, even while stock.

Concerning that saw-tooth pattern, the way it looks as if something has an infinite wakelock or process, Possibly syncing from both system and apps. I would suggest a small expriment...running your device for about an hour with sync turned off, then checking GSAM for a usage pattern.

RCS is now your default messaging app in Oreo, maybe called Android Messages on your device. If it is what I have read so far, it probably is a data leaking/ wakeup nightmare for some as RCS does more than just text messages, it will be more like WeChat with the various ways one can communicate by using the built-in app. Experiment by disabling messaging to double-check. If relief is found, try a 3rd party text solution.

I'm sorry, 'Automated Hibernation' is the correct term.

You can download App Ops from Play Store. Runs fine on Nougat.

Once downloaded, you can head to the Google Play Services entry in App Ops...'PreventPhone From Sleeping' =Deny. While still in Google Play Services entry...'Run in Background Or Be Woken Up' =Deny.

In the Google Play Store entry, use the same settings.

...'Installed/ Downloaded' means most every app installed or downloaded will have some type of analytics/ data gathering built in to the app. Use MATPro to search for the services I layed in the list out in each app, and disable them. It cuts down on battery use/ wakeups for things not needed by the user.

Ahhh, the million dollar question about Amplify. I used to use Amplify, but when Nougat came out, there was no Xposed/ Amplify solution, I simply moved on. I came to this thread, Davey126 read my log and said' "Your problems are because of user actions". I instantly sought to learn all I could about the causes of device drain. By the time I figured how to keep my battery honest, Amplify was not needed.

In moderation, Amplify can be a great ally, or your worst enemy.

---------- Post added at 09:15 PM ---------- Previous post was at 09:10 PM ----------

Awesome news!!! See you in a bit!
[BetterBatteryStats] suvishalreddy9:
got ideal drain below 1%
[BetterBatteryStats] chamonix:
In this post [MENTION=5124760]yochananmarqos[/MENTION] suggests that there may be an impact of certain perms not being granted explicitely when using the unrooted app. We decided to take the conversation over to this thread.

The permissions in question are:

android.permission.DUMP

android.permission.READ_LOGS

android.permission.DEVICE_POWER
[BetterBatteryStats] foosion:
Running for 8 hours overnight, usage was 0.4% / hour!! I can post a dump or more screenshots if that would be useful for you.

I wonder if I'm losing any meaningful functions (such as any syncing or notifying) by using the Greenify settings Automated Hibernation, Aggressive Doze and Wake-up tracking and cut-off. It would also be nice to figure out what was causing the problem. I'm guessing Aggressive Doze was the key to fixing it.

Any suggestions for a strategy for answering these questions (other than turning off Greenify settings one at a time to see what happens)?

BTW, gsam was showing RCS Phone even with Android Messages disabled and no SMS app running , other than Google Voice (Google Hangouts keeps telling me it doesn't do SMS), which uses data, not normal phone.

Thank you!!!
[BetterBatteryStats] fossils-n-dents:
That sentence should have read as "...Or your worst enemy by implementing incorrect settings".

Not really, if you get a fitness app/ smart watch, ect, or notice performance issues, simply disable them. This operation is designed for apps like WeChat, whose high sensor usage is unexplainalble for a social media app. Especially during doze. I feel that while the device is idle, sensors should not be spinning at all.[/QUOTE]

Now you are learning the gentle balance between convenience and battery saving. You can add lots of apps, and Android System will manage them, but at a higher performance/ battery draining rate. Android is a system of compromise in that regard. It ihas limits. The less apps installed (Careful app selection/ device settings), the less work your system does =better battery life.

Screen-on time is highly dependent on how you use your device. Screen brightness is a major factor, after that, things become device/ user specific IMO. I have the HTC 10, no matter what I do, I cannot get more than 4.5 h/ SOT. And that's okay, as long as I know when I put my device down the madness stops.

Use your device normally (Without charging) until the battery gets to 2%, then check your SOT. Your particular device should get at least 3-4 h/ SOC.

You could also check the SOT threads on XDA for further explainations/ tips... https://xdaforums.com/oneplus-3/review/screen-time-t3400058 or other device forums to see what they do for better SOT.

Automated Hibernation only puts the device into Doze quicker, Aggressive Doze may delay some notifications, in that regard, use the Greenify Whitelist feature for any app you need instant notification from. In my experience Wake Up/ Tracking/ Cut-Off is not needed at all. If using Pro version, enable 'Greenify system Apps'.

Within Greenify, you can also try Whitelisting the apps you think may be the culprit(s) of your saw tooth pattern one-by-one, (Or in groups of three) until it/ they reveal themselves.

Then it's possible Messaging wasn't the culprit...the investigation continues. Re-enable your messaging. In your 2nd GSAM shot, 'Photos' had some usage (Assuming this is a device in Idle), the saw tooth pattern could be a sync pattern, which would not be high-priority enough to break aggressive doze in Greenify. (Just a wild guess)

And You're Welcome, my pleasure.:good:
[BetterBatteryStats] foosion:
I'm no doubt missing something very obvious, but how exactly does one whitelist an app in Greenify? I'd probably only whitelist gmail, google voice and led manager (unless some of these are already whitelisted).

Another likely obvious thing I'm missing, but how do I get a report from the tracking? Or does Greenify just use it internally?
[BetterBatteryStats] fossils-n-dents:
In the aggressive doze settings, you will see 'About', Doze on the go', then 'White List'.

As for the Wake up Tracker, I never used it, and playing around with right now it has yielded no results. However, when I get home, I shall see what I can come up with unless another member has the solution to your question before that time. My apologies.
[BetterBatteryStats] foosion:
How did I miss that? smh

If it actually gives detailed information on which apps are waking up the phone, it could be very helpful.

Someone as helpful as you has no need to apologize for not knowing everything.
[BetterBatteryStats] DB126:
+1 x 100 :)
[BetterBatteryStats] fossils-n-dents:
All of my research has led me to believe Wake Up Tracking is only available through the Xposed/Greenify module, or ADB commands (Non-Root). It dosen't appear to be operational with plain root for everyone. I would suggest running the Wake Up Tracking settings, and seeing if your device may get a 'Scissors' icon in the notification bar while idling for a while.

I shall do the same from my end.

[MENTION=4693971]foosion[/MENTION] and [MENTION=5488402]Davey126[/MENTION]...Thank You for the kind words, and your patience.:cool::good:
[BetterBatteryStats] westingham:
I'm having an issue where BetterBatteryStats won't display any results, it constantly says "No stats have been collected yet". I've got a Pixel running stock Android 8.0.

I'm using the 2.2.2.0 version from the Play Store and I enabled the BATTERY_STATS permission via ADB. Nothing.

Then I saw this post:

and tried enabling those permissions as well. The first two were no problem, the third gave me an error: "Operation not allowed: java.lang.SecurityException: Permission android.permission.DEVICE_POWER is not a changeable permission type".

When I switch to the Raw Stats tab of the app, I get the message "BatteryInfo Service could not be contacted".

Tried plugging/unplugging and rebooting but still nothing.
[BetterBatteryStats] suvishalreddy9:
I had same setup as my previous dump but idea drain increased

Ideal drain increased quit a bit I even disabled sync for this dump expecting under 1% but it was significantly higher can you check the reason for that ?? [MENTION=4138220]fossils-n-dents[/MENTION]
[BetterBatteryStats] zetret:
45% wlan_rx_wake for Nexus 6P?

I am using the default Kernel of the RR custom ROM in Nexus 6P, and I am seeing a 45% wlan_rx_wake Kernel Wakelock.

Is this normal?

How do I proceed to reduce this? Is there a specific Kernel I can move to?

I have attached a screenshot - please check.

https://imgur.com/a/IOfQU

From the first page of this thread, I don't know how much is good.

Thanks

Regards
[BetterBatteryStats] OSheden:
do you know why I have the same values for several apps? it's not the first time that I notice this problem. thank you!!

OnePlus 3T, Android 7.1.2, Resurrection Remix
[BetterBatteryStats] DB126:
Have the same problem on AEX (AospExtended), Android 7.1.2. Does not appear to be a hardware dependency as BBS worked fine on the same device with other ROMs based on Android 6.x and below. Have cleared stats and verified permissions. Series of errors are recorded in SuperSU log; not sure if it's related. Should note other tools (eg: GSAM) report same corrupted figures. Guessing it's Nougat or ROM related - possibly a permissions issue.
[BetterBatteryStats] fossils-n-dents:
The thread you read was a Magisk thread (Rooted Devices). Are you using Magisk?

Send me a fresh dump file, and we shall try and see what your issue may be.

'wlan_rx_wake' issues could arise from a crowded Wi-Fi network (Many devices on the same band among other things). Try using a static IP with your device, or switch bands 2.4GHz-5GHz. Before attempting either, (If possible), try a different Wi-Fi network (Friend, relative, ect) to see if the problem exists.

Or, if you wish, submit your proper dump file for a complete overview.

Charge device to 95% (or start the idle run at any percentage lower than 95%).

Set BBS parameters to: 'Unplugged to Current'.

Unplug the device.

Let device idle for a minimum of 6 hours. During this time do Not use the device (Phone calls, messaging, ect)

Submit your dump file to this thread for analysis.

Are you using any Wakelock/ Alarm limitng software (Amplify, Naptime, WakeBlock, ect)? That would usually account for alarms firing at the same rate. If not, turn your device off...wait 30 seconds...reboot, and prepare a proper dump filefor this forum, and let's go deeper into your configuration. Most troubles are usually user inflicted.
[BetterBatteryStats] westingham:
No, not using Magisk. I used the adb method.
[BetterBatteryStats] githyanki:
Do you have root access?
[BetterBatteryStats] atarek:
Hello,

I know I'm disturbing you so forgive me.

I'm just trying to find a fix for my issue.

Attached Idle zip contain dump , dmesg and logcat for your review.

Also attached daily usage dump. i know it can't be reviewed but i want you to look for summary section to see how bad is my case.

Appreciate any advice.

PS: did you recommend changing baseband might decrease mobile data wakelocks.

Regards,

Ahmed
[BetterBatteryStats] westingham:
I do not have root access and do not wish to root my phone, that's why I went the adb route.
[BetterBatteryStats] zetret:
Google Camera App and Kernel?

I flashed a Google Camera APK (for 7.1.2) on RR, and it crashes every time.

Do you have any recommendations on how to get the Google Stock Camera on this ROM?

Also, any recommendations on battery saving Kernels? The default Kernel seems pretty good already (deep sleep very good), but still curious what others think.

Thanks
[BetterBatteryStats] Oswald Boelcke:
A kernel is not only ROM dependent but even more highly dependent on (and specially patched for) the designed device. Unless you tell us what's your device and precisely your RR version are, I doubt that anybody is able to provide any feedback.

And just for me to learn: How did you FLASH an apk?
[BetterBatteryStats] Sam Nakamura:
[OT]

If Google Cam force closes it's most likely a HAL1/HAL3 issue, Google Camera usually uses HAL3 but not all devices support this by default, there likely are ways to make it compatible but those are device specific and this is definitely the wrong place to discuss this anyways, check your device specific for further information or if you use a modified Google Cam check it's thread for information... [/OT]
[BetterBatteryStats] zetret:
Sorry I posted in the wrong forum. But, the RR version is Angler final (7.1.2) (RR-N-5.8.5-20170925-angler-final) for Huawei Nexus 6P.

Flash - I just meant installed. Typed it while half-asleep as you can see.

Regards
[BetterBatteryStats] Oswald Boelcke:
How about to post an idle dump to see how your ROM-inherent kernel performs?

Not familar with the Nexus 6P but quite a few custom kernels seem to be available: https://xdaforums.com/nexus-6p/orig-development#kernels. Maybe to check its threads for reputation and/or to search the BBS thread for experiences of other users?
[BetterBatteryStats] Tundraswan:
Hi all,

Logs attached, tried using ForceDoze and adjusted other settings, but still getting awful idle drain. What is keeping my phone awake? Is it Play Services?

Thanks in advance!