PE 11 is no longer maintained. The issue is caused by a recent GMS update from Google. It's been fixed on PE 12, so you probably should consider upgrading.View attachment 5674199Whats happening here? I'm abroad and got left without data? I'm on
RQ3A.211001.001
PixelExperience_Plus_polaris-11.0-20211223-0443-OFFICIAL
Here are some domains you can block, although I don't know how effective it is today.I am considering upgrading, but not on Holiday... Anything else I can disable to stop this traffic?
Thanks for the help, will try!Here are some domains you can block, although I don't know how effective it is today.
![]()
hosts: Block OTA downloading from GMS · PixelExperience/[email protected]
https: //github.com/PixelExperience/android-issues/issues/1008 Change-Id: I4d611ee8b8490832b310fca48f2576fc9790d483github.com
Try this modI just noticed that the Instagram app is not compatible with this latest version (I didn't check it with the previous ones, it's a fresh installation), I can't install it from the Play Store. has anyone else experienced this?
I believe I finally found the solution after a long investigation.I'm having a bit of an annoyance with notifications (ambient display ones), when the phone is on my wireless charging cradle, the notification pops up, the screen turns on for a second or two (normal behavior), but the screen is very dim I can't see it even on a dark room.
I can't seem to see where I can adjust a setting for this, as when I touch the screen the brightness comes back to normal and if I adjust the brightness slider it's from now on, not for the notification(s) that turned on the screen.
Also turned off adaptive brightness, automatic brightness, set it to the highest brightness level and it doesn't seem to do anything.
Charging via the USB port doesn't seem to affect the ambient display notifications' brightness, also on battery it works as I expect, notifications arrive and can be read on normal brightness.
I'm using latest Plus version installed from scratch.
Any ideas?
Uh what is the correct behavior? I thought "Hold for assistant" means press-and-hold power button action is replaced with assistant?It looks like the "Press and hold power button" > "Hold for assistant" function is broken in the July version. It does bring up the assistant but completely disables the power off function. If you keep pressing long enough, the phone will eventually hard-reset but no power options are available. Cheers
Short hold for assistant, longer hold for power menu (Emergency, Lockdown, Power Off, Restart buttons). If you hold even longer, then hard-reset. The power menu is what's missing. CheersUh what is the correct behavior? I thought "Hold for assistant" means press-and-hold power button action is replaced with assistant?
Was it working in builds before July?Short hold for assistant, longer hold for power menu (Emergency, Lockdown, Power Off, Restart buttons). If you hold even longer, then hard-reset. The power menu is what's missing. Cheers
I'm not 100% sure, but I seem to recall it was working in the April version.
E:[libfs_mgr]Failed to mount /cache: File exists
E: failed to set up expected mounts for install; Installation aborted
No idea. It didn't happen to me. You can try formatting cache in PE recovery. It won't affect your data.I tried to install the new update first with the built in updater but it faild, and then via recovery adb sideload, but my PE recovery fails with the message:
E:[libfs_mgr]Failed to mount /cache: File exists
and then
E: failed to set up expected mounts for install; Installation aborted
Only if I enable ADB on recovery and mount /cache manually on the terminal I could install the upgrade without errors.
What is wrong with my /cache partition?
Oh I see the option of formatting cache now that I entered on "Factory Reset"No idea. It didn't happen to me. You can try formatting cache in PE recovery. It won't affect your data.
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.
Cheers
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
Thanks @jjpprrrrThat means you are still running PE 12's recovery somehow. Try going back to fastboot, flash the recovery, and reboot to recovery again.
abd shell
su
setenforce 0
getenforce