Will do if it happens again.
Wiping cache with PE Recovery seems to have fixed it.
Will do if it happens again.
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?Just updated to PixelExperience_Plus_polaris-12.1-20220828-0031-OFFICIAL.zip, still have this issue
PS: formatting cache partition doesn't helps for me
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).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?
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.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).
All problems are gone![]()
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.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.
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 brighnessI still don't understand. Adaptive brightness is auto brightness. If you disable adaptive brightness, the brightness does not change automatically.
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.
It was working fine on PE 12 as well, but you probably needed to uninstall a language model update that was auto installed.Just realised that the recorder app is fully functional in PE 13, now with the local transcription feature enabled. In PE 12 this wasn't working because it relied on some hardware component that only Tensor and some Exynos socs had. Personally I don't record audio often, but it's pretty cool nevertheless!
Please wait for the next update.Hi,
today I found Google Pay having stopped working. it's complaining about the system not fulfilling the security requirements/ no original Android version.
I found the Google Wallet having been updated yesterday (the version shows a release date of Feb 14), so I assume that they introduced some more strict checking.
anyone found some workaround already?
Regards
sthones
Thanks! Will try to do it with on WSL, don't have experience building Android ROMs but yes in other stuff. So is there any extra step to get Google Pay working again or is it enough building it as provided?Build and install
- Get a 64bit x86 linux machine that has a minimum of 16GB RAM. I used one with32 GB. VMs are fine.
- install rsync: `sudo apt install rsync`
- Follow the build guide https://wiki.pixelexperience.org/devices/polaris/build You can skip the "Turn on caching to speed up build" section if this is just a one-off build. For example, if you're planning to use a VM that you will blow away at the end.
- If the build is successful, install your ROM from recovery: https://wiki.pixelexperience.org/devices/polaris/install/#installing-pixelexperience-from-recovery
Not sure about OTA, but you could always install the official version on top of this from recovery if/when it comes out. Theoretically it's the same code, so OTA might work too, but there may be other factors in play, such as that your ROM won't be signed and it will be marked UNOFFICIAL. Not sure if the server allows UNOFFICIAL roms to pull OTA updates for example. Best to ask @jjpprrrr about that.
And, most importantly, if you don't know what you're doing, don't build your own rom!![]()
abd shell
su
setenforce 0
getenforce