Hello,
BBS is better than Battery Guru, but on my A54 nothing works except the alarms! (you get "no stats have been collected yet" message).
It's probably an issue with Android 13, because I tested BBS on a Samsung A42 running Android 12 and it's working fine. So on A54 I have to use BatteryGuru as a replacement.
I never use that diagram for wakelocks. Instead I use Partial Wakelocks, which are relative to applications. The kernel wakelocks are generated by the kernel, and you cannot do much about that (except rooting the phone and installing a different kernel).
On your screenshot I see 199 wakeups for com.android.phone. This seems too much for an idle phone. On my phone I get zero wakeups about the phone app.
In any case this is what I usually do:
I open Partial Wakelocks (not working on A54) or alarms.
Before taking measurements I usually set a custom ref. using the menu at top right (this will be my starting point for measurements).
Then I let the phone rest for the entire night, or at least some hours (like 4 or 5). don't touch the phone during this time, since all of this is for detecting battery drain during idle time.
After some rest time I open BBS and select "custom" instead of boot, and "screen on" instead of current. this way I have the list of alarms/wakelocks fired during the period of measurement
Note: sometime I open BBS and get an emtpy list. To workaround this issue I close BBS in the recent apps list, and the I reopen it. The measurements are not deleted.
To identify the drain you search for a high number of alarms/wakelocks. Ideally you want to have the minimum number of alarms and wakelocks, because those are preventing the phone form going into deep sleep.
Then by looking at the number you identify the application and you can decide what to do: sometimes you can change options in the app to reduce the alarms, like for example disabling notifications if they're not important for you. or you can uninstall the app if you really don't need it, or finally you can disable the app (not uninstall) using ADB or ADB AppControl. I usually google the name of the wakelock to find some common solutions from other users.
Another option is to save a log and upload that to the XDA forum of BBS: there are some kind users that will take a look at the log and tell you what is going on in your phone during idle time.
I use Battery Guru for wakelocks: there is a section that lists them, but you cannot set the range of the measurement (or at least I didn't find any way to do it).
Currently I have moderately debloated my A54 using ADB (ie I disabled some applications I don't use, like Bixby or beacon manager). I can provide my list of disabled apps, but usually is not very useful: each person uses the phone in a different manner, so maybe you'll need some apps that instead I keep disabled.
I then tried some solutions to wakelocks I was getting, like a wakelock related to multimedia, IIRC. I'm getting some moderate wakelock numbers, like rilj_ack_wl but I didn't found a solution for that yet.
I keep my A54 with no data or wifi enabled during the night, and I'm currently getting a drain of 0.2 per hour, which is very good IMHO).
![Screenshot_20230824-202615[1].png](https://eu.community.samsung.com/t5/image/serverpage/image-id/1825580i019F03B52134C76B/image-size/large?v=v2&px=999 "Screenshot_20230824-202615[1].png")
![Screenshot_20230824-203458[1].png](https://eu.community.samsung.com/t5/image/serverpage/image-id/1825582i4EE10DE44C429C9B/image-size/large?v=v2&px=999 "Screenshot_20230824-203458[1].png")
