Development [ROM][12.1][VENUS] Pixel Experience [AOSP][2022/07/26]

Search This thread

Sage

Senior Member
Dec 12, 2005
1,614
376
AU
Xiaomi Mi 11
Which version and config of gcam you using? I'm finding in good conditions gcam is better though in not good conditions stock miui is much better.. low light, or mixed light or taking photos into the sun etc
 

jjpprrrr

Senior Member
Nov 27, 2018
929
833
jjpprrrr.com
Anyone else having issues with bluetooth audio after the last update? It breaks all sound on mine after connecting to a bluetooth device and I have to reboot to make speakers work again.

These are the errors I'm getting in logcat, that might be connected to this:
Code:
2022-07-03 10:16:21.859 2145-2145/? E/audioadsprpcd: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:2846: Error 0x72: apps_dev_init failed for domain 0, errno Transport endpoint is not connected
2022-07-03 10:16:21.859 2145-2145/? E/audioadsprpcd: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:2944: Error 0x72: open_dev (-1) failed for domain 0 (errno Transport endpoint is not connected)
2022-07-03 10:16:21.859 2145-2145/? E/audioadsprpcd: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:1334: Error 0x72: remote_handle_open failed for adsp_default_listener (errno Success)
2022-07-03 10:16:21.860 2145-2145/? E/audioadsprpcd: fastRPC device driver is disabled, retrying...
2022-07-03 10:16:21.860 2145-2145/? E/audioadsprpcd: audio adsp daemon will restart after 25ms...
2022-07-03 10:16:21.893 2145-2145/? E/ion: ioctl c0044901 failed with code -1: Inappropriate ioctl for device
2022-07-03 10:16:21.894 2145-24630/? E/audioadsprpcd: vendor/qcom/proprietary/adsprpc/src/log_config.c:268:Error 0x200: fopen failed for /vendor/lib/rfsa/adsp/audioadsprpcd.farf. (No such file or directory)
2022-07-03 10:16:21.894 2145-24630/? E/audioadsprpcd: vendor/qcom/proprietary/adsprpc/src/log_config.c:268:Error 0x200: fopen failed for /vendor/dsp/adsp/audioadsprpcd.farf. (No such file or directory)
2022-07-03 10:16:21.894 2145-24630/? E/audioadsprpcd: vendor/qcom/proprietary/adsprpc/src/log_config.c:268:Error 0x200: fopen failed for /vendor/dsp/audioadsprpcd.farf. (No such file or directory)
That should not happen at all. I just checked it on my venus. I took multiple logs, pre reboot, post reboot, using Bluetooth, etc., and none of them had such errors. Therefore, it's likely something on your side.
 

Pho3nX

Senior Member
Jun 13, 2013
2,689
1,925
Nothing Phone 1
Anyone else having issues with bluetooth audio after the last update? It breaks all sound on mine after connecting to a bluetooth device and I have to reboot to make speakers work again.

These are the errors I'm getting in logcat, that might be connected to this:
Code:
2022-07-03 10:16:21.859 2145-2145/? E/audioadsprpcd: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:2846: Error 0x72: apps_dev_init failed for domain 0, errno Transport endpoint is not connected
2022-07-03 10:16:21.859 2145-2145/? E/audioadsprpcd: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:2944: Error 0x72: open_dev (-1) failed for domain 0 (errno Transport endpoint is not connected)
2022-07-03 10:16:21.859 2145-2145/? E/audioadsprpcd: vendor/qcom/proprietary/adsprpc/src/fastrpc_apps_user.c:1334: Error 0x72: remote_handle_open failed for adsp_default_listener (errno Success)
2022-07-03 10:16:21.860 2145-2145/? E/audioadsprpcd: fastRPC device driver is disabled, retrying...
2022-07-03 10:16:21.860 2145-2145/? E/audioadsprpcd: audio adsp daemon will restart after 25ms...
2022-07-03 10:16:21.893 2145-2145/? E/ion: ioctl c0044901 failed with code -1: Inappropriate ioctl for device
2022-07-03 10:16:21.894 2145-24630/? E/audioadsprpcd: vendor/qcom/proprietary/adsprpc/src/log_config.c:268:Error 0x200: fopen failed for /vendor/lib/rfsa/adsp/audioadsprpcd.farf. (No such file or directory)
2022-07-03 10:16:21.894 2145-24630/? E/audioadsprpcd: vendor/qcom/proprietary/adsprpc/src/log_config.c:268:Error 0x200: fopen failed for /vendor/dsp/adsp/audioadsprpcd.farf. (No such file or directory)
2022-07-03 10:16:21.894 2145-24630/? E/audioadsprpcd: vendor/qcom/proprietary/adsprpc/src/log_config.c:268:Error 0x200: fopen failed for /vendor/dsp/audioadsprpcd.farf. (No such file or directory)

Surely because of a Magisk Addon/tweak or a dirty flash from other rom.

With a clean install this roms is perfect, i'm using BT everyday in call/deezer/GPS
 

Pho3nX

Senior Member
Jun 13, 2013
2,689
1,925
Nothing Phone 1
Not true, only thing I've flashed after clean installing the ROM is the update (through the OTA). Managed to fix it by dirty flashing the latest update through recovery.

"Not true" is not the good answer, you can said "Not in my case".

A lot of people dirty flash from other roms or using ****ty Magisk Modules causing this similar problem. So ok it's not in your case, but it's definitively true.

For your problem, try to clear cache SystemUI or rollback to the previous version just for fix the problem.
After that, better solution is to make a clean flash, even if it's boring.
 
Last edited:
"Not true" is not the good answer, you can said "Not in my case".

A lot of people dirty flash from other roms or using ****ty Magisk Modules causing this similar problem. So ok it's not in your case, but it's definitively true.

For your problem, try to clear cache SystemUI or rollback to the previous version just for fix the problem.
After that, better solution is to make a clean flash, even if it's boring.
Like I said, fixed it by flashing the latest update again.
 

Berard_Gutler

Senior Member
May 24, 2022
51
11
Because this ROM has only one purpose and that to deliver the experience of google pixel phones, there is no additional customization etc, it only delivers monthly security patch + any additional feature google phones might get, other than this bug fixes and optimizations, other roms are focusing on adding extra customizations thats why they have more frequent patches, PE doesn't need that.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    2022/07/26
    2
    Maybe I will switch from Mi10 to Mi11 because of this official support but it would he a downgrade :(

    How good.bad is the battery life compare to stock MIUI?

    battery life is better than MIUI. maybe 10% to 15% better imo.
    2
    This support this game Turbo ?
    What is that? The MIUI feature that limits the performance and puts more restriction on thermal when you launch a game? It's weird to call that "Turbo".
    2
    What is the Android security patch version? February 2020?
    It's written right there.

    1659749948292.png
    1
    the solution does not come from me there is a YouTube video but you need to be rooted to be able to enjoy this camera but I think many here are modding
    Link please?
  • 19

    GtwTyCR.png


    PixelExperience for Mi 11 [venus]

    What is this?
    Pixel Experience is an AOSP based ROM, with Google apps included and all Pixel goodies (launcher, wallpapers, icons, fonts, bootanimation)

    Our mission is to offer the maximum possible stability and security, along with essential and useful features for the proper functioning of the device

    Based on Android 12.1


    Whats working?
    Wifi
    RIL
    Mobile data
    GPS
    Camera
    Flashlight
    Bluetooth
    Fingerprint reader
    NFC
    Lights
    Sound / vibration


    Known issues
    Refer to the changelog for known issues.

    DO NOT FLASH GAPPS, ALREADY INCLUDED
    Download from Pixel Experience website

    Translation
    Help with project translation

    Stay tuned
    Our Telegram channel
    Our blog
    Donate me
    Device support group




    Android OS version: 12.1.0_r10
    Security patch level: July, 2022
    Build author/Device Maintainer: jjpprrrr
    Device and Kernel Source code: https://github.com/PixelExperience-Devices
    Source code: https://github.com/PixelExperience
    ROM Developer: jhenrique09
    8
    2022/06/26
    6
    Dear jjpprrr, thank you for the best Mi11 experience !
    After reading that there are many fixes already available und the security fixes for june are also released I want to ask kindly when you plan to release the next version of your wonderful ROM. (no pressure, it´s already my all time favorite for the Mi11!)
    I understand that you didn't mean to offend, but I genuinely have no idea how to answer questions like this. I feel like asking for an ETA is quite pointless: you would only get an estimate; whether the release will come as I promised or not is still undetermined.
    • If I find some regressions and need to take time to fix them, all you get is more disappointment.
    • Say everything is ready, and I deliberately hold on the update to mess with you guys. Why would I do it? What do I gain from it? Of course I release as soon as it's ready, so no need to ask about it. I don't freaking know when it will be ready. I only know after I finish testing everything.
    On the other hand, official PE's release window is not always open. We work on the ROM source at our own pace. Sometimes the CI is locked so we can start merging new patches or bringing in fixes. For example, right now due to some build server issue, all releases are halted. We cannot release anything even if the device is ready.

    Therefore, please relax and enjoy the current build. This would be the last time I answer questions regarding ETA.
    5
    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:
    - Download the vendor_boot.img (https://gitlab.pixelexperience.org/...venus/-/raw/twelve/android-12/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 pe_rom_file_name.zip` in your cmd/powershell/terminal and wait until it finishes
    5
    Hi jjpprrrr, we all know the rules about eta, but can you give some news about your next update ? 🥹