[ROM][13][POLARIS] Pixel Experience [AOSP][2023/05/01]

[the_marox]

how's the battery compared to 12 ?

a lot better, especially in thermal management

 

[Milou25]

Thanks @jjpprrrr
I flashed the latest PE13 recovery again but it didn't solve the problem.
Then I tried the prior version of the PE13 recovery (20221122) which successfully flashed the current stable PE13 zip.

I am not sure if this is a bug that was introduced in the latest recovery build or my device, but it may warrant investigation if others have the same issue with the latest recovery.

Anyhow Thanks for the help!

I have the same issue and it started when I tried to flash PE13 beta in recovery mode. So I just downgraded back to the latest PE12 build. Then the stable PE13 was released and again got the same error. Are you saying that if I flash the beta version again (successfully?) then I will be able to flash the stable version of PE13?

 

[stinkytoes]

I have the same issue and it started when I tried to flash PE13 beta in recovery mode. So I just downgraded back to the latest PE12 build. Then the stable PE13 was released and again got the same error. Are you saying that if I flash the beta version again (successfully?) then I will be able to flash the stable version of PE13?

What worked for me was using the beta PE13 recovery to flash the stable PE13 ROM. It was the stable PE13 recovery that was giving me the problem.
So follow the PE13 installation instructions (https://jjpprrrr.com/pe/20230119-1051/) except use beta version of the recovery instead of the stable recovery.

 

[sthones]

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

 

[marioosh666]

anyone found some workaround already?

February Update: Slow and steady! - PixelExperience Blog

With the latest security patches, fixes for essential features, improved translations, and stability improvements, this update offers a more secure, stable, and accessible experience for all users.

blog.pixelexperience.org

"The update includes the February security patch, providing the latest fixes for potential vulnerabilities in Android. The update also includes fixes for SafetyNet and Google Pay, two essential features for many users. With these fixes, users can use these services without any issues or restrictions, providing a more seamless experience."

 

[lamasfoker]

anyone found some workaround already?

The same here with the latest version (build January 19, 2023, 10:51 UTC)

 

[zmylna]

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

Hi.
I have exactly the same problem. Last update installed.
Did you find solution ?

 

[sthones]

Hi.
I have exactly the same problem. Last update installed.
Did you find solution ?

No, not working.
From what @marioosh666 sent up there, we need to wait for a February security patch update of the Pixel Experience OS.

 

[ElRocha]

Hi.
I have exactly the same problem. Last update installed.
Did you find solution ?

Install magisk if you haven't and then this module, which is a fork of the original Universal SafetyNet Fix.
After you reboot, safetynet should pass.

 

[zmylna]

Install magisk if you haven't and then this module, which is a fork of the original Universal SafetyNet Fix.
After you reboot, safetynet should pass.

Do I need root to install magisk?

 

[ElRocha]

Do I need root to install magisk?

Magisk is the thing that gives you root. You need to have the bootloader unlocked and flash it through the recovery.

 

[zmylna]

Last question.
Will the Pixel experience recovery allow me to install magisk? Or do I need to install another recovery? TWRP?

 

[ElRocha]

Last question.
Will the Pixel experience recovery allow me to install magisk? Or do I need to install another recovery? TWRP?

It does allow you. Just sideload magisk like you would the rom. Also when you get a new update to the rom, you'll need to sideload magisk again after the update.

 

[ch0d.curry]

Last question.
Will the Pixel experience recovery allow me to install magisk? Or do I need to install another recovery? TWRP?

zmylna, I'm just a random person online, so you don't have to take my advice, but I would recommend holding off on rooting and installing safetynet-fix unless passing SafetyNet is absolutely essential for you at the moment.

If you root, you will have to update the Magisk module far more often, and you will need to mess with the Magisk Deny List regularly to make sure all of your apps work correctly. There are other ways of detecting root besides failing SafetyNet, so you will be stuck playing cat and mouse. Be patient and trust in the developers of PixelExperience and jjpprrrr for their excellent work. I believe the last time the ROM was failing SafetyNet was in 2021, so it's just a temporary anomaly.

 

[jjpprrrr]

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!

It was working fine on PE 12 as well, but you probably needed to uninstall a language model update that was auto installed.

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

Please wait for the next update.

 

[Parciez]

Is there any expected date of updated version?
Also I've some problems with fingerprint reader, I can't unlock the phone with fp, while it's working completely fine in apps. Any idea how to solve this?

 

[dRm42]

@jjpprrrr I've built a version for myself to get Google Pay working again and found that two crucial bits of info were missing from the build guide at https://wiki.pixelexperience.org/devices/polaris/build

Do you happen to know who maintains it?

#1, What you'll need - This list doesn't say but the build machine must be 64bit x86. It doesn't work on Arm. I've built it on AWS and wasted hours by the time I've managed to figure it out from the error messages. Nobody's fault, but it would be nice to add a note as it's a must have, not optional.

#2, rsync is not installed by the pre-build prep scripts and it's required at the very end of the build process The build died on me at 96% because it couldn't find rsync haha. Anyway, probably the best thing to do would be to add rsync to android_build_env.sh, while the second best thing to just add a line to the build docs and say install rsync `sudo apt install rsync`

Cheers

ps: Safetynet passes now

 

[vocalico]

Any hint on how to build it for getting safetyket pass again?
I guess it wouldn't be able to OTA update to the next release, right?

@jjpprrrr I've built a version for myself to get Google Pay working again and found that two crucial bits of info were missing from the build guide at https://wiki.pixelexperience.org/devices/polaris/build

Do you happen to know who maintains it?

#1, What you'll need - This list doesn't say but the build machine must be 64bit x86. It doesn't work on Arm. I've built it on AWS and wasted hours by the time I've managed to figure it out from the error messages. Nobody's fault, but it would be nice to add a note as it's a must have, not optional.

#2, rsync is not installed by the pre-build prep scripts and it's required at the very end of the build process The build died on me at 96% because it couldn't find rsync haha. Anyway, probably the best thing to do would be to add rsync to android_build_env.sh, while the second best thing to just add a line to the build docs and say install rsync `sudo apt install rsync`

Cheers

ps: Safetynet passes now

 

[dRm42]

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!

 

[vocalico]

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!

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?

EDIT: So after setting the environment and getting all files, which took around 1 hour and some effort from my computer, I saw that WSL only get 7.71GB of RAM from the 16 available in my machine. I guess that I would pass and wait until an official relase because I'm too lazy for setting up all again in another environment that I'd need to figure out.

Thanks anyway