Development [ROM][12.1][UNOFFICIAL] LineageOS 19.1 for Xiaomi MIX 4

Search This thread

EnzoG54

New member
Mar 16, 2015
2
0
Hello, just flashed 19.1 LOS, awesome rom, very smooth. However, is there a fix for Netflix to detect L1 Widevine? Or I'm stuck at L3. Thanks..
 

Chris_of_Topher

New member
May 7, 2022
1
0
Hello, I would like to know what the current quality of the selfie/front facing camera is?

And does Gcam now work perfectly (especially in the selfie department) like the ANX camera app?
 

0201m

Member
Dec 14, 2012
19
7
Bavaria, Germany
I had problem with proximity with another ROM and it was due to wrong firmware.
I had xiaomi.eu beta flashed before.
But after flashing Chinese stable firmware (no wipe or anything needed, just sideloading through adb sideload) it worked flawlessly

Maybe that fixes your network issue as well. I don't have 5g contract so i don't know
Thanks for the input. I did reflash the firmware, no change. I downlaoded a sensor test app and noticed a pattern. As long as there is no audio playing the test in the app works perfectly. But as soon as there is audio coming thourgh the top speaker, the ultrasound proximity sensors works 1/25 times and is really unresponsive. So i guess it has something to do with an audio route issue. Also i have to restart the test app so it reinitializes the seonsor, so definitely sounds like a audio route thing

I went through the logcat when starting the test in the working and non working usecase. The only two things different are the sensor initializations:

WorkingNon working
05-09 23:39:43.658 790 2511 D ultrasound_extn: dump_usecase_list: start ======================================
05-09 23:39:43.659 790 2511 D ultrasound_extn: dump_usecase_list: enter state: 1[start] suspended: 0 cnt: 1 pre_cnt 0
05-09 23:39:43.661 790 2511 D ultrasound_extn: dump_usecase_list: RX_CDC_DMA_RX_0 SampleRate KHZ_48
05-09 23:39:43.662 790 2511 D ultrasound_extn: dump_usecase_list: RX_CDC_DMA_RX_0 Format S16_LE
05-09 23:39:43.662 790 2511 D ultrasound_extn: dump_usecase_list: RX_CDC_DMA_RX_0 Channels One
05-09 23:39:43.663 790 2511 D ultrasound_extn: dump_usecase_list: RX_CDC_DMA_RX_1 SampleRate KHZ_48
05-09 23:39:43.663 790 2511 D ultrasound_extn: dump_usecase_list: RX_CDC_DMA_RX_1 Format S16_LE
05-09 23:39:43.664 790 2511 D ultrasound_extn: dump_usecase_list: RX_CDC_DMA_RX_1 Channels Two
05-09 23:39:43.664 790 2511 D ultrasound_extn: dump_usecase_list: end ======================================
05-09 23:41:42.211 790 2511 D ultrasound_extn: dump_usecase_list: start ======================================
05-09 23:41:42.211 790 2511 D ultrasound_extn: dump_usecase_list: enter state: 1[start] suspended: 0 cnt: 1 pre_cnt 0
05-09 23:41:42.211 790 2511 D ultrasound_extn: dump_usecase_list: ultrasound_start usecase[#0]:(0, deep-buffer-playback) in_dev:(0, ) out_dv:(2, speaker)
05-09 23:41:42.213 790 2511 D ultrasound_extn: dump_usecase_list: RX_CDC_DMA_RX_0 SampleRate KHZ_48
05-09 23:41:42.214 790 2511 D ultrasound_extn: dump_usecase_list: RX_CDC_DMA_RX_0 Format S16_LE
05-09 23:41:42.215 790 2511 D ultrasound_extn: dump_usecase_list: RX_CDC_DMA_RX_0 Channels One
05-09 23:41:42.215 790 2511 D ultrasound_extn: dump_usecase_list: RX_CDC_DMA_RX_1 SampleRate KHZ_48
05-09 23:41:42.216 790 2511 D ultrasound_extn: dump_usecase_list: RX_CDC_DMA_RX_1 Format S16_LE
05-09 23:41:42.216 790 2511 D ultrasound_extn: dump_usecase_list: RX_CDC_DMA_RX_1 Channels Two
05-09 23:41:42.216 790 2511 D ultrasound_extn: dump_usecase_list: end =====================================
05-09 23:39:43.751 790 2511 D ultrasound_extn: dump_usecase_list: start ======================================
05-09 23:39:43.751 790 2511 D ultrasound_extn: dump_usecase_list: enter state: 1[start] suspended: 0 cnt: 1 pre_cnt 0
05-09 23:39:43.751 790 2511 D ultrasound_extn: dump_usecase_list: ultrasound_start usecase[#0]:(72, ultrasound-proximity-input) in_dev:(300, ultrasound-input) out_dv:(0, )
05-09 23:39:43.751 790 2511 D ultrasound_extn: dump_usecase_list: ultrasound_start usecase[#1]:(71, ultrasound-proximity-output) in_dev:(0, ) out_dv:(132, ultrasound-output)
05-09 23:39:43.752 790 2511 D ultrasound_extn: dump_usecase_list: RX_CDC_DMA_RX_0 SampleRate KHZ_48
05-09 23:39:43.753 790 2511 D ultrasound_extn: dump_usecase_list: RX_CDC_DMA_RX_0 Format S16_LE
05-09 23:39:43.754 790 2511 D ultrasound_extn: dump_usecase_list: RX_CDC_DMA_RX_0 Channels One
05-09 23:39:43.755 790 2511 D ultrasound_extn: dump_usecase_list: RX_CDC_DMA_RX_1 SampleRate KHZ_48
05-09 23:39:43.756 790 2511 D ultrasound_extn: dump_usecase_list: RX_CDC_DMA_RX_1 Format S16_LE
05-09 23:39:43.756 790 2511 D ultrasound_extn: dump_usecase_list: RX_CDC_DMA_RX_1 Channels Two
05-09 23:39:43.756 790 2511 D ultrasound_extn: dump_usecase_list: end ======================================
05-09 23:41:42.279 790 2511 D ultrasound_extn: dump_usecase_list: start ======================================
05-09 23:41:42.279 790 2511 D ultrasound_extn: dump_usecase_list: enter state: 1[start] suspended: 0 cnt: 1 pre_cnt 0
05-09 23:41:42.279 790 2511 D ultrasound_extn: dump_usecase_list: ultrasound_start usecase[#0]:(0, deep-buffer-playback) in_dev:(0, ) out_dv:(2, speaker)
05-09 23:41:42.279 790 2511 D ultrasound_extn: dump_usecase_list: ultrasound_start usecase[#1]:(72, ultrasound-proximity-input) in_dev:(300, ultrasound-input) out_dv:(0, )
05-09 23:41:42.279 790 2511 D ultrasound_extn: dump_usecase_list: ultrasound_start usecase[#2]:(71, ultrasound-proximity-output) in_dev:(0, ) out_dv:(2, speaker)
05-09 23:41:42.281 790 2511 D ultrasound_extn: dump_usecase_list: RX_CDC_DMA_RX_0 SampleRate KHZ_48
05-09 23:41:42.283 790 2511 D ultrasound_extn: dump_usecase_list: RX_CDC_DMA_RX_0 Format S16_LE
05-09 23:41:42.283 790 2511 D ultrasound_extn: dump_usecase_list: RX_CDC_DMA_RX_0 Channels One
05-09 23:41:42.284 790 2511 D ultrasound_extn: dump_usecase_list: RX_CDC_DMA_RX_1 SampleRate KHZ_48
05-09 23:41:42.285 790 2511 D ultrasound_extn: dump_usecase_list: RX_CDC_DMA_RX_1 Format S16_LE
05-09 23:41:42.285 790 2511 D ultrasound_extn: dump_usecase_list: RX_CDC_DMA_RX_1 Channels Two
05-09 23:41:42.285 790 2511 D ultrasound_extn: dump_usecase_list: end ======================================
 

Attachments

  • bad.txt
    26.2 KB · Views: 4
  • good.txt
    26.4 KB · Views: 4
Last edited:

Inkypen

Senior Member
Aug 19, 2018
459
1,386
London
Samsung Galaxy Note 4
Xiaomi Mi 5s
New builds with May security patch are up. ANX camera is now default camera solution. The SE policy rules for ANX have been rewritten and now almost everything is working correctly, including the downloadable features like Panaroma and Document scanner. The only things not working are slow motion video recording and HDR video recording.

Download links:
@0201m Thank you for the logs concerning proximity sensor, I'll look into it. The sensor was working correctly on 11 and 12 and I haven't done any major changes to my device tree so something must have changed in 12.1 to cause this. Also I fixed the screen animations to line up with physical buttons so thanks for letting me know about that too ;)
 

0201m

Member
Dec 14, 2012
19
7
Bavaria, Germany
New builds with May security patch are up. ANX camera is now default camera solution. The SE policy rules for ANX have been rewritten and now almost everything is working correctly, including the downloadable features like Panaroma and Document scanner. The only things not working are slow motion video recording and HDR video recording.

Download links:
@0201m Thank you for the logs concerning proximity sensor, I'll look into it. The sensor was working correctly on 11 and 12 and I haven't done any major changes to my device tree so something must have changed in 12.1 to cause this. Also I fixed the screen animations to line up with physical buttons so thanks for letting me know about that too ;)
Thank you for the update! If you need additional logs just let me know.
I experienced another side effect of the non working proximity. I have AOD enabled and somehow even without anything playing and the proximity theoretically working the phone wakes up in my pocket and starts random inputs.
So the "check prxoimity in doze" somehow doesnt work. i believe there once was an option to enable it under display settings, but its not there.
 

0201m

Member
Dec 14, 2012
19
7
Bavaria, Germany
Oh anothter question. How do i update on lineage? Can i boot into twrp and dirty flash even with an encrypted data partition? I guess it should work as data is not concerened in the update process.
 

lightskreen

Member
Oct 3, 2014
7
0
Milwaukee
Thank you so much for making this room, it's very good. My only nitpick is I wish the status bar height was a little more uniform. Is there a way to make it so it looks more like the notification shade clock and icons?
 

Attachments

  • Screenshot_20220516-194401_Google Play Store.png
    Screenshot_20220516-194401_Google Play Store.png
    78.2 KB · Views: 26
  • Screenshot_20220516-194452_Chrome.png
    Screenshot_20220516-194452_Chrome.png
    80.6 KB · Views: 26

er453r

Member
Jan 1, 2012
48
8
@Inkypen just dirty-flashed the lineage-19.1-20220511-UNOFFICIAL-gapps-odin build and everything that was working still works great :) Two issues already noted in this thread:
  1. ANX downloadable features still do not work for me (I get the "network error" massage)
  2. I have the same proximity issues @0201m reported, and probably had them before all along, just did not notice them (phone can go crazy in the pocket or during a phone call from face touches - I just blamed it on xiaomi hardware :p)
 

Inkypen

Senior Member
Aug 19, 2018
459
1,386
London
Samsung Galaxy Note 4
Xiaomi Mi 5s
Oh anothter question. How do i update on lineage? Can i boot into twrp and dirty flash even with an encrypted data partition? I guess it should work as data is not concerened in the update process.
Someone else asked me this so I'm just going to copy/paste the reply:
Sideload is one way to update but it seems that TWRP won't sideload some A12 ROMs. I built OrangeFox for myself and I haven't had any issues with sideload.
https://sourceforge.net/projects/xiaomi-odin/files/OrangeFox-R11.1-Unofficial-odin.zip/download

The other method you can try is to use adb to copy a ROM to the phone and install it directly from the device. Internal storage isn't actually mounted because of encryption, so /sdcard becomes attached to a temporary filesystem in memory. You can take advantage of this, for example:
adb push lineage.zip /sdcard
 

Inkypen

Senior Member
Aug 19, 2018
459
1,386
London
Samsung Galaxy Note 4
Xiaomi Mi 5s
@Inkypen just dirty-flashed the lineage-19.1-20220511-UNOFFICIAL-gapps-odin build and everything that was working still works great :) Two issues already noted in this thread:
  1. ANX downloadable features still do not work for me (I get the "network error" massage)
  2. I have the same proximity issues @0201m reported, and probably had them before all along, just did not notice them (phone can go crazy in the pocket or during a phone call from face touches - I just blamed it on xiaomi hardware :p)
Very strange, ANX downloadables are working here. Try this sequence to see if it works:
Enable USB debugging and ADB Root/rooted debugging in developer options
Connect device to a PC and use a terminal window to enter these commands
adb root
adb shell setenforce 0

This temporarily disables selinux. Try to download ANX features. You can just reboot device to re-enable selinux.

Also good news, I've managed to fix the erratic operation of the proximity sensor. Fix will be in next update.
 

santimaster2000

Senior Member
Dec 25, 2009
399
98
Buenos Aires
@Inkypen just dirty-flashed the lineage-19.1-20220511-UNOFFICIAL-gapps-odin build and everything that was working still works great :) Two issues already noted in this thread:
  1. ANX downloadable features still do not work for me (I get the "network error" massage)
  2. I have the same proximity issues @0201m reported, and probably had them before all along, just did not notice them (phone can go crazy in the pocket or during a phone call from face touches - I just blamed it on xiaomi hardware :p)
Would you mind sharing the steps you followed in order to dirty flash ?
 

santimaster2000

Senior Member
Dec 25, 2009
399
98
Buenos Aires
New builds with May security patch are up. ANX camera is now default camera solution. The SE policy rules for ANX have been rewritten and now almost everything is working correctly, including the downloadable features like Panaroma and Document scanner. The only things not working are slow motion video recording and HDR video recording.

Download links:
@0201m Thank you for the logs concerning proximity sensor, I'll look into it. The sensor was working correctly on 11 and 12 and I haven't done any major changes to my device tree so something must have changed in 12.1 to cause this. Also I fixed the screen animations to line up with physical buttons so thanks for letting me know about that too ;)
lnkypen, I just flashed thim, ehm, quick question, is it normal that before this update I truly couldn't see the "camera hole" and now I can ?

Also, I no longer have root, sorry, first time dirty flashing, not really sure what to do.
 
Last edited:

er453r

Member
Jan 1, 2012
48
8
Very strange, ANX downloadables are working here. Try this sequence to see if it works:
Enable USB debugging and ADB Root/rooted debugging in developer options
Connect device to a PC and use a terminal window to enter these commands
adb root
adb shell setenforce 0

This temporarily disables selinux. Try to download ANX features. You can just reboot device to re-enable selinux.

Also good news, I've managed to fix the erratic operation of the proximity sensor. Fix will be in next update.
@Inkypen tried it exactly as you said, but the same - network error
 

santimaster2000

Senior Member
Dec 25, 2009
399
98
Buenos Aires
@santimaster2000 I do it in 4 steps:
  1. Temporarily flash twrp from Inkypen in fastboot with
    1. fastboot boot twrp-odin.img
  2. Push the zip to data with
    1. adb push lineage-19.1-20220511-UNOFFICIAL-gapps-odin.zip /data/
  3. Install with TWRP without wiping anything
  4. Restart to system :)
Did it, but wiped dalvik/cache, everything seems to be working, aside from root, also, for some reason "Phone Services" keeps making the location green notification thingy pop up.
 

santimaster2000

Senior Member
Dec 25, 2009
399
98
Buenos Aires
OK, got root, problem seemd to be that I was flashed the first patched boot.img that I got from the stock MIUI ROM, I extracted the new boot.img from the latest LOS build, patched and flashed that, now I got root.

I still have the problem with "Phone Services" constantly accessing location, and also the front camera "hole" seems to remain open all the time.
 

Inkypen

Senior Member
Aug 19, 2018
459
1,386
London
Samsung Galaxy Note 4
Xiaomi Mi 5s
@Inkypen tried it exactly as you said, but the same - network error
Not an selinux issue then. It's working fine here on LOS and on PE. Go to app info (long press anx icon on launcher and select the "i") clear all storage and try again. If it still doesn't work then I'll need a logcat to try and troubleshoot it.
OK, got root, problem seemd to be that I was flashed the first patched boot.img that I got from the stock MIUI ROM, I extracted the new boot.img from the latest LOS build, patched and flashed that, now I got root.

I still have the problem with "Phone Services" constantly accessing location, and also the front camera "hole" seems to remain open all the time.
Kinda sounds like the issue I had early in development when various things work on one boot slot but not the other. Reboot to recovery and flash MIUI 13 firmware again.

Also, why does everyone seem to extract and patch the boot image when trying to install Magisk? Why not just sideload it in recovery?

For future builds the relevant latest firmware will be included in the ROM zip, to avoid all these headaches about firmware version.
 

santimaster2000

Senior Member
Dec 25, 2009
399
98
Buenos Aires
Kinda sounds like the issue I had early in development when various things work on one boot slot but not the other. Reboot to recovery and flash MIUI 13 firmware again.
Are you talking about the camera thing or the location thing ?

So, I just flash this firmware, right ?


Thanks again for all your work man !
 

Inkypen

Senior Member
Aug 19, 2018
459
1,386
London
Samsung Galaxy Note 4
Xiaomi Mi 5s
New builds are up. Firmware is now included so no need to flash it separately.

  • Erratic proximity sensor fixed
  • Kernel upstreamed to 5.4.195
  • Firmware/vendor blobs updated to MIUI 13.0.6.0

Some people are having issues updating/sideloading via TWRP, so I made an unofficial build of OrangeFox.

To install it simply sideload it in TWRP. Occasionally the device won't get recognised when plugged into a PC and it's simple to fix. Go to the mount page in menu options (3 horizontal lines) and toggle MTP off/on.

Regarding updating the ROM, there seems to be some confusion on how to do it because no recovery is currently able to decrypt A12 data partitions. I mentioned it earlier but there are two ways in which to update.

  • Sideload
This is the simplest way to update but it seems that TWRP won't sideload some A12 ROMs. If sideload doesn't work then use the OrangeFox linked above.​
Usage:
Connect device to a PC and activate ADB sideload mode in recovery​
In a terminal type : adb sideload rom.zip

  • ADB
The other method you can try is to use ADB to copy a ROM to the phone and install it directly from the device. Internal storage isn't actually mounted because of encryption, so /sdcard becomes attached to a temporary filesystem in memory.​
Usage:
Connect device to a PC​
In a terminal type: adb push rom.zip /sdcard
Install zip in directly in recovery from internal storage

You should replace rom.zip with the filename of the zip you want to flash. Because of the virtual A/B setup on this device it appears that addon.d is no longer functional and this means anything that modifies the system will need to be flashed again once an update is completed, a prime example being Magisk (which you can sideload, no patching boot image is necessary). OrangeFox even prints a helpful message reminding you of this little fact.
 

santimaster2000

Senior Member
Dec 25, 2009
399
98
Buenos Aires
New builds are up. Firmware is now included so no need to flash it separately.

  • Erratic proximity sensor fixed
  • Kernel upstreamed to 5.4.195
  • Firmware/vendor blobs updated to MIUI 13.0.6.0

Some people are having issues updating/sideloading via TWRP, so I made an unofficial build of OrangeFox.

To install it simply sideload it in TWRP. Occasionally the device won't get recognised when plugged into a PC and it's simple to fix. Go to the mount page in menu options (3 horizontal lines) and toggle MTP off/on.

Regarding updating the ROM, there seems to be some confusion on how to do it because no recovery is currently able to decrypt A12 data partitions. I mentioned it earlier but there are two ways in which to update.

  • Sideload
This is the simplest way to update but it seems that TWRP won't sideload some A12 ROMs. If sideload doesn't work then use the OrangeFox linked above.​
Usage:
Connect device to a PC and activate ADB sideload mode in recovery​
In a terminal type : adb sideload rom.zip

  • ADB
The other method you can try is to use ADB to copy a ROM to the phone and install it directly from the device. Internal storage isn't actually mounted because of encryption, so /sdcard becomes attached to a temporary filesystem in memory.​
Usage:
Connect device to a PC​
In a terminal type: adb push rom.zip /sdcard
Install zip in directly in recovery from internal storage

You should replace rom.zip with the filename of the zip you want to flash. Because of the virtual A/B setup on this device it appears that addon.d is no longer functional and this means anything that modifies the system will need to be flashed again once an update is completed, a prime example being Magisk (which you can sideload, no patching boot image is necessary). OrangeFox even prints a helpful message reminding you of this little fact.
Will flash as soon as I can make a proper backup of EVERYTHING !!!

Quick question, if I'm dirty flashing, should I wipe dalvik/cache or not ?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    New builds are up:
    • June security patch
    • Kernel upstreamed to 5.4.197 and latest lahaina CAF tag
    • LHDC Bluetooth codec added (untested as I don't have a BT device that supports this)
    • Some ANX tweaks (should start a little bit faster)
    Regarding the conversation about the visible camera hole at maximum brightness, that's a hardware limitation. You must have seen Xiaomi's promotional image of the pixel array above the front facing camera showing the smaller pixels allowing light to pass through to the image sensor. A smaller pixel will not be able to shine as brightly as a larger one hence the slightly darker view on max brightness. MIUI gets around this flaw by displaying a sun symbol over the camera hole at max brightness. On a couple of builds I tried limiting the max brightness by about 15% so this wasn't noticeable but I had a few people in sunny areas complain about the change, so I reverted back. If it bothers you just turn the brightness down a little bit.

    Are there any plans to fix the widevine level from l3 to l1? I know that the China/eu Rom habe l1,so it should not be impossible to fix
    I've had L1 support since before I even released any builds. Download any media codec info app from play store and check for yourself.
    2
    I've built TWRP 3.6.2 A12 branch and decryption is working. Untested other than making sure it boots and decrypts internal storage correctly. Use fastboot boot to run it and Advanced/Flash current TWRP to actually install it. If you find any bugs feel free to report them but bear in mind the whole TWRP A12 branch is currently WIP.
    1
    @lightskreen have you enabled variable refresh rate in Display settings? I do not know how it knows when to use 60/120 Hz but I have noticed no stutter at all.

    @santimaster2000 @Inkypen I can confirm that front facing camera is more visible since 20220519 - as if it was a few levels darker than the rest of the screen.
    1
    One issue, that forced me to temporarily switch back to MIUI is Android Auto.
    For my new car it is not working. It starts connecting, the Android Auto app opens on the phone, but then closes (crashes) again.
    I suspect there is something wrong/missing with gapps, but i couldnt get a log.

    On MIUI everything works

    Update: Switched to PixelExperience, Android Auto is working perfectly there
  • 8
    2okPze5.png

    LineageOS is a free, community built, aftermarket firmware distribution of Android 12 (S), which is designed to increase performance and reliability over stock Android for your device.

    Code:
    #include <std_disclaimer.h>
    
    /*
    * Your warranty is now void.
    *
    * We are not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at us for messing up your device, we will laugh at you.
    *
    */

    LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.

    Base source code is available in the LineageOS Github repo. And if you would like to contribute to the project, please visit our Gerrit Code Review.

    GPL compliance:
    yG18r6g.png


    Working:
    Almost everything

    Broken:
    Screen off FOD (Fingerprint On Display)

    Downloads:
    https://sourceforge.net/projects/xiaomi-odin/files/12/LineageOS
    https://sourceforge.net/projects/xiaomi-odin/files/11/LineageOS

    Installation:
    Reboot to recovery
    Copy LineageOS zip to internal storage
    Install LineageOS zip package
    Install [optional] a Google Apps package of your choice
    Format data (wiping is not sufficient, formatting requires you to type "yes")
    Reboot

    Important notes:
    GApps can only be flashed on clean installs.
    Formatting data (all user data is wiped, including internal storage) is a must if MIUI was previously installed and device was encrypted.

    Contributors
    Inkypen
    ROM OS Version: Android 12
    ROM Kernel: Linux 5.4
    Based On: AOSP
    5
    New builds are up:
    • June security patch
    • Kernel upstreamed to 5.4.197 and latest lahaina CAF tag
    • LHDC Bluetooth codec added (untested as I don't have a BT device that supports this)
    • Some ANX tweaks (should start a little bit faster)
    Regarding the conversation about the visible camera hole at maximum brightness, that's a hardware limitation. You must have seen Xiaomi's promotional image of the pixel array above the front facing camera showing the smaller pixels allowing light to pass through to the image sensor. A smaller pixel will not be able to shine as brightly as a larger one hence the slightly darker view on max brightness. MIUI gets around this flaw by displaying a sun symbol over the camera hole at max brightness. On a couple of builds I tried limiting the max brightness by about 15% so this wasn't noticeable but I had a few people in sunny areas complain about the change, so I reverted back. If it bothers you just turn the brightness down a little bit.

    Are there any plans to fix the widevine level from l3 to l1? I know that the China/eu Rom habe l1,so it should not be impossible to fix
    I've had L1 support since before I even released any builds. Download any media codec info app from play store and check for yourself.
    5
    New test build is up. It has a new version of minimal gapps installed and it also passes safetynet from clean flash without the need of root or any additional patches or modules. OK Google detection is now working with the screen switched off. Biggest change is a much improved ANX camera experience. There are no more crashes when using certain camera modes, the only thing not working is slow motion. I'm considering making ANX the default camera for all future builds (gapps and non gapps) and I would appreciate any feedback about this change.

    Build is here: https://sourceforge.net/projects/xi...220426-UNOFFICIAL-gapps-anx-odin.zip/download
    4
    @Inkypen
    So I have been daily-driving lineage-19.1-20220321-UNOFFICIAL-odin.zip for over a week now and here are some things I have noticed:

    • Google Assistant Voice Match is not available (so no "OK Google") - this worked with Lineage 18.1
    • "OK Google" also does not work with locked/off screen (actually that also did not work 18.1... - that is something I miss from my Pixel 2)
    • I have used NikGApps and the security code loop during setup is still present
    • the same - using NikGApps with PixelLauncher loops the PixelLauncher (not a rom isssue, just giving a heads-up) - I have ended up using core apps flavor
    • camera Apps I have found working are some GCam builds, but they all have issues (not all cameras supported, no slow-mo videos, images are not properly scaled for diffirent lenses...) - we really need ANX - even if it means sacrificing some APIs and other cam apps...
    • I can confirm that safety net passes, the banking apps and NFC payments work OK
    • quick wireless charge works OK
    • 120Hz display works OK though I am not sure it is forced all the time
    • bluetooth works with all devices I could throw at it :)

    Other than that everything is nice and smooth :) Using it daily is pure pleasure. Kudos to @Inkypen
    Your first four points are not the fault of the ROM and are all related to the same thing: gapps

    OK Google detection needs Velvet which is only in Nikgapps stock edition and above, which you can't install because as you mentioned Pixel Launcher will crash. I've determined that the security code loop is due to using A12 version of setup wizard.

    Which leads me to the good news, I've found a 12.1 version of gapps that has fixed the setup wizard bug. It's meant to be part of a ROM build and is not suitable for flashing separately, so I'll start releasing gapps builds soon.

    As for ANX, you're in luck. I figured out what to change in the Lineage source code to get the Xiaomi camera stack working and I've successfully made a test build with it integrated. I just need to write selinux policy for it :)

    Screenshot_20220404-001531_Settings.png
    3
    I've been testing out LineageOS 19.0 based on Android 12. If anyone wants to try it out, it's available here:

    READ BEFORE INSTALLING
    **** EDIT ****
    I've uploaded a new build based on 12L and with fixed NFC. Still has same filename so download link is the same.