Maintenance builds with November security patch and some fixes.
Note
This is a maintenance build with November security patch. This build includes a fix for a recently revealed security vulnerability in AOSP’s keyguard. PE 12 is deprecated, and there will be no more PE 12 builds in the future. PE 13 builds are coming soon.
Sorry for skipping October’s release and the absence on forums. I was insanely busy with work and other IRL stuff.
Please follow the wiki for detailed install instructions. I will not provide support if you fail to follow the required steps.
If you are on my previous PE 12 / 12 Plus builds, you can directly OTA or dirty flash in recovery. A concise version of clean flash guide for the experienced users:
Boot your phone into bootloader mode. You can either
hold power + volume down button
or adb reboot bootloader
Connect your phone to a computer
Run fastboot flash vendor_boot vendor_boot.img in your cmd/powershell/terminal
Run fastboot flash boot pe_recovery_file_name.img in your cmd/powershell/terminal
Hold power + volume up to boot into recovery, or fastboot reboot recovery
In PE recovery, select Factory reset" --> "Format data/factory reset
Go back to main menu and select “Apply update” –> “Apply from ADB”
Run adb sideload pe_rom_file_name.zip in your cmd/powershell/terminal and wait until it finishes
Reboot to system
Device Specific Changes
Etude kernel: Op.12 Op.3
Linux 5.4.210
wireguard 1.0.20220627
CL tag LA.UM.9.14.r1-20800-LAHAINA.QSSI13.0
fixed high touchscreen polling rate after suspend and resume. Previously the polling rate would return to normal after you lock and unlock the screen.
built with the latest LLVM Clang 15.0.2
ROM Side Changes
November security patch.
Translation updates
Known Issues
One of the gapps update may mess with the haptic feedback strength. I am not sure if it still happens after we reverted back to the AOSP haptic strength menu. If your haptic feedback feels weak after a clean flash, go to Settings/Accessibility/Vibration & haptics and try setting all 3 categories again. You only need to do it once, and the haptic strength will remain normal afterwards.
Light sensor reading is affected by the screen brightness. This may cause jumpy auto brightness under low light.
We have two light sensors, one in the front under the display panel, and the other on the back. Currently only the front one is reported as an android.sensor.light sensor, of which the auto brightness is based off. The problem is that the light emitted by the display panel also affects the front light sensor, so the sensor reports a high value when the screen is displaying bright white content, even if the phone is actually in a dark environment with little ambient light. (What could go wrong when you put an ambient light sensor directly under a light source?) MIUI uses some algorithm to combine the reading of both light sensors on the system side in libsensor_cal.so, but we do not have such mechanism on AOSP. More work is needed to bring up our own solution in the future.
The AOSP Camera2 app may take a severely cropped and blurry photo using the main sensor on the back. This is caused by an incorrect selection of default image ratio and resolution. In the main UI of Camera2, swipe to the right to reveal the photo/video switch buttons. On the bottom right corner, press the small “gear” icon to enter settings. In “Resolution and quality”, change “Back camera photo” to the second option: (4:3) 13.1 megapixels.
