Can we use encryption in this ROM? I've tried a couple of a12 pixel based roms and all of them, after encrypting, Google apps just started crashing and I couldn't fix. Only option was to format data.
12/June/2022 update
Changelog ->
- June Security Patch
- Increase BootCompletedReceiver priority (Helps to restore Xiaomi Parts as soon as device boots up)
- Optimise dex flags
- Ok Google should work now
- Removed Google Camera due to multiple issues
- Added GrapheneOS Camera
- Added Smooth Scrolling props
- Disable slow blur effect to avoid laggish blur effect
- Upstream kernel to 4.9.317~hyper
Download
You can dirty flash, but i always recommend clean flashDo I have to wipe System, Dalvik, Cache before flashing?
Thanks for your work.
Prior release was a bit laggy to me, going to give this one a try...
You May try encryption is fixed but not 100% sure. Do at your own riskCan we use encryption in this ROM? I've tried a couple of a12 pixel based roms and all of them, after encrypting, Google apps just started crashing and I couldn't fix. Only option was to format data.
Sorry, I forgot to mention I'm already on this ROM.
Nope doesn't work. It did asked for decryption in recovery but failed to boot to system (20 mins on Google logo no signs of booting up). It would be amazing to fix this actually. Everything is stable too, haven't found any bugs, smooth enough for 3gb variant with spare 1.1gb to 800mb in memory. Also bsg gcam 8.1 can be used in future build too cuz it's the most well known gcam for mido with very few bugs (even slow-mo and AR core works even with omnivision sensor for bsg 8.1 gcam).You May try encryption is fixed but not 100% sure. Do at your own risk
only wipe cache and dalvik then flash rom zip then wipe cache and dalvik before rebootSorry, I forgot to mention I'm already on this ROM.
I only want to know about dirty flash for upgrading, if it should be better to wipe cache,dalvik and system or if wiping only cache and dalvik is ok
Ok thanksonly wipe cache and dalvik then flash rom zip then wipe cache and dalvik before reboot
Don't wipe system partition in dirty flashing
Its working
Orangefox
Sorry I forgot to tag the person for whom this question was
Which recovery you usedNope doesn't work. It did asked for decryption in recovery but failed to boot to system (20 mins on Google logo no signs of booting up). It would be amazing to fix this actually. Everything is stable too, haven't found any bugs, smooth enough for 3gb variant with spare 1.1gb to 800mb in memory. Also bsg gcam 8.1 can be used in future build too cuz it's the most well known gcam for mido with very few bugs (even slow-mo and AR core works even with omnivision sensor for bsg 8.1 gcam).
This. It is a custom twrp zeelog (current LOS 19.1 unofficial maintainer) made with support for A12 decryption. It did work on his rom, both encrypting and decrypting and it only took 15 mins to encrypt so it's not the problem with recovery I'm guessing. But PE+ latest build just doesn't boot when started the encryption. But when booted to recovery it did ask for decryption meaning the encryption did work but can't boot to the system. Orange Fox is old and doesn't support a12 decryption so I don't use it anymore. Also, one bug I found is that sometimes in landscape mode, back gestures fail to work even going back to portrait mode. To fix this I have to re-enable gestures.
OKThis. It is a custom twrp zeelog (current LOS 19.1 unofficial maintainer) made with support for A12 decryption. It did work on his rom, both encrypting and decrypting and it only took 15 mins to encrypt so it's not the problem with recovery I'm guessing. But PE+ latest build just doesn't boot when started the encryption. But when booted to recovery it did ask for decryption meaning the encryption did work but can't boot to the system. Orange Fox is old and doesn't support a12 decryption so I don't use it anymore. Also, one bug I found is that sometimes in landscape mode, back gestures fail to work even going back to portrait mode. To fix this I have to re-enable gestures.
Had the same issue a while back in arcana os. You can temporarily fix it by going to recovery and in the settings, find the fix contexts or selinux contexts or something like that. It doesn't wipe data, it just fixes storage. I think that happens when you change rom but still have your sdcard set as internal storage.having some problems on every android 12 rom about the internal storage missing. any workarounds about that? tried clean flash especially formatting the data
install fastboot driver on your pcFastboot starts but can't be find from the computer... command "fastboot devices" shows "waiting for any devices" . and after one minute or so it reboots and boots up to TWRP, where it hangs.