Featured image of post PixelExperience 13 / 13 Plus 20230130-1650 Official Venus Build

PixelExperience 13 / 13 Plus 20230130-1650 Official Venus Build

Initial release based on android 13.


  • 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, clean flash is recommended when upgrading to PE 13. Dirty flash from PE 12 to PE 13 may be fine, but please consider a clean flash if you run into any issues. Here is a concise version of clean flash guide for the experienced users.
    • Download the vendor_boot.img (
    • Download PE recovery from the official PE website
    • 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 in your cmd/powershell/terminal and wait until it finishes
    • Reboot to system

Device Specific Changes

  • Etude kernel: Op.13 Op.1
    • CL tag LA.UM.9.14.r1-21000-LAHAINA.QSSI13.0
    • built with an updated LLVM CLang 16
  • Updated and fixed several things in the init script
    • Optimized cpuset values for different task groups.
    • Removed read ahead tuning to avoid hogging up memory.
    • Set default USB product string.
  • Cleaned several things in audio configs to drop unsupported formats and align with stock configs.
  • Moved GSI AVB keys and recovery resources to vendor_boot
  • Updated to boot control HAL v1.2
  • Used surfaceflinger offsets from taro (SM8450) to slightly reduce latency
  • Switched to vendor defined color modes from Xiaomi. You can change the color modes in Settings/Display/Colors. The sRGB and P3 mode will also change the color space of display composition respectively.
  • Switched to the new AOSP Bluetooth stack with various fixes for a2dp.
  • Updated system-side DPM, IMS, RIL, and WFD blobs from LA.QSSI.13.0.r1-05300-qssi.0.
  • Switched to AOSP NFC stack.
  • Switched to AIDL Clearkey DRM HAL.
  • Properly configured the Aperture camera app.
    • You can switch between the main camera, the ultrawide camera, and the macro camera.
    • Enabled 60fps video recording for supported camera-resolution configurations.

ROM Side Changes

  • Initial android 13 release with January security patch.
  • For the Plus edition, perhaps not all customization options are here yet. They will be brought back in future releases.

Known Issues

  • 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, but we do not have such mechanism on AOSP. More work is needed to bring up our own solution in the future.
    • I have some ideas on a better implementation, but I need more time to to experiment with it and improve the algorithm.
  • The fingerprint sensor and the double-tap-to-wake feature may appear broken if you just flashed a new build and rebooted to system. It can be easily fixed if you just reboot a few times. If you are near a computer, connecting your phone to the computer to run adb reboot can reliably fix it in one try. I have no idea why that happens, but I suspect there is a bug in the slot switching in Xiaomi’s bootloader or firmware.

Download | XDA thread | Support group

Licensed under CC BY-NC-SA 4.0
comments powered by Disqus
Built with Hugo
Theme Stack designed by Jimmy