Not that, but I've had another weird issue that I've solved by formatting the cache partition from recovery. Some guys couldn't install the OTA update and a cache format solved it for them too. Kind of a blind stab in the dark, but maybe give it s go.
Is any testing needed? I don't see high percentage of GMS (Google Play Services) in battery statistics, but CPU locked on max frequency (so battery discharges pretty quickly) and many apps freezes on startupIt appears that some users are suffering from the same GMS heat/battery drain issue again. Google probably changed something on their side (again), so our previous workaround no longer works.
If you see a big percentage of GMS (Google Play Services) in your battery statistics, contact me on telegram and I will give you a few test builds to try. Thanks.
Might be something with your phone or your battery is dying. If you install a ROM that worked for you before, does the issue go away?
I think no, that was software issue. I'm did "factory reset" (wiped all data/cache/system from recovery and re-installed current build from adb).
Yeah it was probably because the gms service was still using results from cache. Clean flash will do the trick, but you could wait for the cache to expire/be invalidated or wipe the storage/cache of gms in Settings.
What do you mean by "Disabling adaptive brightness doesn't help"? If you don't use auto brightness, the screen brightness stays at the value you set before. It should not change at all.When using phone in darkness/low light environments, and with automatic and adaptive brightness enabled the screen wakes up with very low brightness (only a little portion of the brightness setting bar) and is almost unusable until you raise the level.
It's not too annoying in complete darkness but it wakes up with low brightness too when the room light is not too bright (in the morning/sunset).
Disabling adaptive brightness doesn't help.
On sunlight / normally lit room it wakes up on an usable brightness level (close to the middle of the brightness bar).
I mean this setting (pic not from this ROM but it's the same) adaptive brightness works only with automatic brightness also enabled.
I still don't understand. Adaptive brightness is auto brightness. If you disable adaptive brightness, the brightness does not change automatically.I mean this setting (pic not from this ROM but it's the same) adaptive brightness works only with automatic brightness also enabled.
If I had put too low brightness with adaptive enabled the phone could have interpreted I want low brightness with very low room light, but I mean that's not the case because if I disable adaptive brigthness the problem with low brightness remains.
Then forget about adaptive brighness
Lol if the light sensor reads 0 lux, then it thinks the room is completely dark. That's the reading from a hardware sensor. I cannot do anything about it.Then forget about adaptive brighness
This is on AUTO brightness, room with low ambient light BUT NOT complete darkness:
View attachment 5708899
View attachment 5708901
This is the same room, letting more of the sunlight in:
View attachment 5708903
View attachment 5708905
What I'm seeing here is that, even if the room has sufficient light as I told you (I can see my hands, I can see everything on the room easily), on the first two images the lux meter reads 0.
Can argue that my sensor is broken, but my girlfriend's Mix2S has this same ROM and it does exactly the same.
Found it somewhere on a forum and it worked for me:Installed latest update, now when entering phone app it shows this warning:
View attachment 5816175
(this device is not conpatible and it's possible that phone calls don't work correctly)
Functionality wise the phone works well, i checked making and receiving phone calls.
Every gapp is updated through the play store.
That worked, thank you!Found it somewhere on a forum and it worked for me:
- Open Play Store
- Search for the Phone app
- Click Uninstall (this only uninstalls updates because it's a system app)
- Open Phone app
- Close Phone app
- Go back to the Play Store and click Update (this will bring it up to date again)
- Open Phone app
Should work fine after this.
Partially, yes, tried to clear cache from Android System Intelligence, that solved it for a short while (like a reboot would). Tried to uninstall updates from Android System Intelligence as recommended in the changelog, unfortunately that didn't help. I didn't actually try the clean flash option as this is my everyday phone and didn't want to set up everything from scratch for a "maybe". Cheers
abd shell su setenforce 0 getenforce