This is not an idle dump, strictly speaking. The screen on time should be as less as possible, preferably under a minute. Please generate another idle dump and post. As soon as you unlock the screen, open BBS and save the dump before doing any exploration.
Bump.The attached dump is from my primary device where I never quite had much luck with idle drain except for a while when I was using a custom kernel. Majority of the time in the 0.5-0.8%/h range. Very rarely reduced to 0.1%/h which almost always coincided with charging to 100%. Also right after unplugging the device 2-3% drop occurs in the first 2-3 minutes. Could anyone please check if anything stands out? Thanks.
Drain is only 0.6% per hour. Except the following two items, nothing to speak about. Battery should be nearing 3 years. May be a factor.
I will say considering the age of the battery and running A11, this drain is ok.
I think that this is a normal behaviour. If you take a dump for 15 odd minutes like you did, the phone will be awake most of the time (awake screen off). That is why an idle dump is required for a longer period of not less than 6 hours so that the effect of the initial wakelocks/alarms are mitigated over the longer period.Ive been noticing that my phone randomly stops going into deepsleep. This doesn't happen very often but like twice a week..and the moment i reboot my phone the problem is solved most of the times
Im attaching a few screenshots below
Whenever this happens I observe that there aren't any major partial wakelocks that are keeping the device up but a few kernel wakelocks..
Any feedback is highly appreciated!!
(I wouldve taken an overnight battery dump and posted but this happens very randomly so it isn't under my control Any help is appreciated)
I have searched for a solution for the "transaction failed on small parcel" error on android 11.
I found something here:
Starting with Android Pie, access to certain hidden classes, methods and fields was restricted. Before Pie, it was pretty easy to use these hidden non-SDK components by simply using reflection. N...stackoverflow.com
bbs seems to work correctly if I use this command:
adb shell settings put global hidden_api_policy 1
Just scroll up to post #37,758 slightly above yours. On top of post #2 you can also read about Play Store.Hey, sorry if this is off-topic but it appears that BBS was removed from play store. Can't find it anymore and also gone from my purchase history in my account. Strange that there's isn't a link to download if you already purchased the app. Any info about this? Thanks
I'm sorry I didn't realize that it was info there. I just panic search everywhere because google decided to remove 4 apps that I paid for from Play Store and I can't reinstall them now. Sorry again.
I guess you have to blame Google but not the developers of those apps - I know you don't blame the developes. Google tends to remove everything that doesn't fit into their business scheme.
No no no, there's no way I'm blaming the devs for this, this mess is on google's part. And it's not the first time they do this. I lost quite some apps because they decided to remove them from store ( google I mean ). A few I had the apk files but others I did not
Cant get it to work on my pixel 4 xl a12 stock beta 2 rooted. Already did the command mention in termux.BBS is not dead!
Google has pulled BBS from GPlay. The given reason is that I use a library (HockeyApp) that allows installations by other means than the GPlay; that is correct except that library is a) deprecated and does not have backend anymore and b) the GPlay edition does not use that library, only the xda-edition does.
Removing HockeyApp is unfortunately not so simple because Google has also updated the minSDK to 29 (was 28) previously and some o you have noticed the latst build (with SDK29) had some other issues.
Anyhow, I think I have made some progress, and I have a version that now runs on my Pixel 3 XL and the current beta 2. After some testing - and your feedback - I hope to be able to get BSS re-instated in GPlay.
If you want to test this early fix please make sure to run (in a terminal, or "settings put global hidden_api_policy 1" directly on the device):
(Failing to do that will lead to errors telling you that the battery info service can not be contacted. This is another step by Google to further restrict access to private APIs with SDK29: I stay of the opinion that the only reason is that they don't want to expose how bad their own code is in regards to battery usage).
Tests I could do so far:
- Pixel 3 XL with current beta: OK
- Galaxy S10 running Android 11: NOK (known issue, Samsung unfortunately runs unpublished / undocumented code)
(more to come, I have a few phones laying around)
The build is going up in a few minutes
Surprising. There were background downloads by many apps via mobile data & wifi. Plus some alarms are shown with a minus (-) sign in front of them. I have not come across such minus signs before. So obviously it requires a clean flash. I think that you merely uninstalled Magisk and did not do a clean flash while removing Magisk. That may be the cause.WiFi, Mobile Data & Bluetooth were Off. Mobile Signal usually has no issues as I live in a metropolitan area.
Battery is slightly lesser than 3 years old, but I doubt that is the issue and this suddenly started after I uninstalled Magisk. I was hoping someone could pinpoint the issue using above stats, so that I don't have to reflash and resetup the entire ROM which would take many days for me.
You haven't followed the instructions in the first page of this thread or those given by @pjadec above. You should save the dump as soon as you unlock the phone, not use it for hours on end and then save it. We need an idle dump, not an in-use one.