- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-31-2021 10:59 PM in
Galaxy M- « Previous
- Next »
- Mark as New
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-09-2021 08:21 AM in
Galaxy M- Mark as New
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-25-2021 01:14 PM in
Galaxy M- Mark as New
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-03-2021 12:41 PM in
Galaxy M- Mark as New
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-01-2021 04:24 AM in
Galaxy MI have two S5e tablets that dramatically increased battery drain after the Android 11 update. The subsequent update did not correct the issue.
The only way I see to diagnose this problem is to be able to see the tasks running within android and the CPU each is consuming. This ability was removed in Android 10. Does anyone know of a way to accomplish this on Android 11 preferably without rooting?
Using the GPUWatch feature (developer options), I see a 20% CPU load at idle (no foreground app running and in airplane mode. This remains the same in Safe Mode. With WiFi active I also see periodic CPU spikes, some as much as 100%. The implication here is that the problem is within Android (or a part Samsung modified) and not an app issue.
I found this interesting but haven't tried it yet:
https://dontkillmyapp.com/samsung
I am really getting tired of version updates causing me major issues to the point that Samsung should pay me to use their products.
- Mark as New
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2021 08:35 PM in
Galaxy MHello is there anyone who is using A30 since its launch when it was on Android 9 pie
Please tell me that whether there was any battery drain issue?
Because there is severe battery drain issue like 20-25% battery fall at average during night after android 11 update. I also tried downgrading it to android 10 but the issue was not solved.

- « Previous
- Next »