yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] -+BB+-:
I took a quick look at laurel PE 12 sources and there's nothing related to that function, unless your friend used a different launcher with an icon pack or a Magisk module native icon support should be beta like now. Hopefully will be available with March or April update as Google added it in QPR2

Logs of the crash? Are you using this blob? The GCam version shipped with the ROM is the only one released by BSG with an "acceptable" apk size for system (around 85 Mb), new versions are around 350 Mb, ROM size will be increased of 250+ Mb for an user upgradable app, that's why i let users the possibility to upgrade GCAM app. Also the patch simply fixes the mutex restrictions, it does nothing else, and has nothing to do with HDR

Regarding the large app icon on drawer I've wiped my devices during the bringup at least 25-30 times and never happened to me, and no one else reported this bug... Unless you changed the font/icon size during the first boot (Setup Wizard asks if you want to change font and icon size during the setup) no idea why it happened.
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] sotux:
I uploaded a log.

03-17 21:33:14.840 993 1763 E CHIUSECASE: chxusecaseutils.cpp:2320 ReleaseReference() [AdvancedCameraBufferManager_1] ReleaseReference failed, cannot find Image buffer for buffer handle 0xdba2e310
03-17 21:33:14.840 993 12737 E CHIUSECASE: chxusecaseutils.cpp:2265 AddReference() [AdvancedCameraBufferManager_1] AddReference failed, cannot find Image buffer for buffer handle 0xdba2e310

May be this is the reason the stock googleCameraMod crashed.

I'll try the blob then. Which folder should I put this blob file?

Thanks.
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] -+BB+-:
Thanks for the log, I will inspect deeper in these days, at a first look sounds more like a GCAM bug, but the patched blob is loaded a few msecs before GCAM crash, and may be related (the crash is caused by a null point exception in GCAM, but it's not the root cause of the issue). You can copy the blob with adb, just download it from here, enable adb in developer settings and run:

adb root
adb shell mount -o rw,remount /vendor
adb push /path/to/downloaded/com.qti.chi.override.so /vendor/lib/hw/
adb reboot

NOTE: these commands are for Linux OSes, if you are on Windows or Mac syntax may be slighty different.
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] davidetri:
Hi guys, I just installed this rom, how is it consuming? it's good? and do you have any problems? Thank you
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] RS966:
Hi,

installed this rom a few hours ago. Looks good, install was smoth.

Til now really great, have to test a few Days for Accu and ......

Thx to dev !!
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] -+BB+-:
Hi to everyone, march update is available for download, here's the changelog:

ROM

- Updated sources to latest PE updates

- Merged AOSP android-13.0.0_r35 updates

Device tree

- audio: added missing hph highquality and lowpower paths

- audio: fixed and cleaned wrong devices name

- Updated and fixed power profile

- Audio: fixed gapless support

- Audio: fixed record concurrencies

- audio: enabled ULL mode

- audio: misc cleaning and improvements

- ZRAM: use LZ4 instead of LZO

Proprietary blobs

- Patched original com.qti.chi.override.so for mutex restrictions

Kernel

- Disabled various debugging stuffs and full tracing

- Disabled some unuseful things (modules, profiling, bounce buffers)

- Disabled auditing

- Enabled power efficient workqueues as default

- Enabled LZ4 and disabled LZO

Here's the direct download link

Enjoy :)

@RS966 thanks, i'm glad you like it, but unfortunately you have to upgrade again after a few hours :)
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] soltek57:
Hi.

The rom looks very good, but is it possible to enable call recording?

Thank you very much for the work
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] -+BB+-:
Added here, will be in next public release, unfortunately Google Dialer recorder is broken on all my devices at the moment, but all third party apps I've tested works fine
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] RS966:
When the new Version run as smoth as before ... ;-)

Update was fine, looks like good as before, maybe better Battery, but i will keep an eye on it.

PS: Thats my second phone, i bought a new one before as the Mi9SE was fully mad with MIUI. I could blame you now that you did that so late ( just kidding hahahaha ) , but now its a gaming device for me. And runs really cool. If i had that ROM before, i think i did not have a new main mobile now.....

Thanks -+BB+- for your work !!
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] -+BB+-:
Hi to everyone, April update is out and starting from this month i will provide PE Plus version too.

Here's the changelog from last public release:

ROM

- Sync sources with latest PE changes

- Merged android-13.0.0_r41 AOSP updates

Device Tree

- Audio: misc fixes/updates and enabled call recording. NOTE: Google Dialer Call Recording is actually broken, 3rd party apps works fine

- Disable configstore

- switch to Vulkan for UI rendering

- Added back LiveDisplay feature (Plus version only)

- bind several services to system background cpuset

Kernel

- Huge debloating

- disable frame pointer, ipc logging, tracing and debugging

- enable jump label

- remove POPP

- adreno: disable tracing, snapshot and coresight

- adreno: compile only 5xx and 6xx part

- Fix some clang warns after debug removal

Pixel Experience 13 Direct download link

Pixel Experience 13 PLUS Direct download link

NOTE: Plus version can be dirty flashed over default version

Enjoy :)
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Berkbe07:
Thanks for the pe plus version 🐧🐧😍😍
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] prog19:
Sorry to ask, but i'm not familiar with PE ROM. I would like to know If this ROM have the "adaptative charging" feature from pixel phones.

Thank you in advance
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] os388a:
how setting Double Tap To Wake?
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Giac99:
Thank you I will dirty flash pe plus, do you have any telegram channel?
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Kaisar999:
Flash plus version or use lawnchair launcher
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] kolouch.petr:
I successfully upgraded from march to the april plus edition. My phone does not "see" my WPA3 wifi. If I switch back to WPA2 - then it is OK. Does the ROM supports WPA3 ? anyway thank you for your work :)
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Dron_GTR:
Latest build have problem with bluetooth headphones. Wireless headphones not working. Tried two different headphones: QCY and Xiaomy.

Connect work properly but no sounds and volume level can't be changed.

Everything works perfect, thanks alot for the PixelExpirience!
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] danger2u:
Google pay working?
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] -+BB+-:
As far as i know our device don't support SAE, it's disabled in WCNSS config like in stock MIUI, but I cannot test it because I don't have a WPA3 router

Only difference with march update is aptX libs removal but i've tested calls and aptX with 4 different BT adapter and it's working fine for me

It's wrote in the OP
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Dron_GTR:
Yes, im sorry, it is was my mistake :) I'am disabled all media sounds in dont disturb mode
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] wally-soft:
I really love this ROM but i have a problem. Sometimes it says "no sim card detected" and i have to reboot. Any ideas how to solve this?
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] -+BB+-:
Hi to everyone, may update is out, here's the changelog:

ROM

- Sync sources with latest PE changes

- Merged android-13.0.0_r43 AOSP updates

Device Tree

- audio: set valid and supported channel mask for earpiece

- audio: fix audio policy for v7 Audio HAL

- rootdir: fix qvr_external_sensor entry and remove a typo

- fix various props not applied and remove duplicates

- rootdir: update vendor.audio service override

- reintroduce ULL output

- SEPolicy: fix various denials

Download links:

Pixel Experience 13 Direct download link

Pixel Experience 13 PLUS Direct download link

@wally-soft logs? could be an HW issue because we are using the same identical blobs/config of official los, I havent't made any changes on that part of code
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] -+BB+-:
I've tried to enable SAE/WPA3 and it's working pretty fine, tested with Courbet Hotspot, the change will be included in next release, meanwhile if you want to enable WPA3 you can do it using adb and a text editor:

adb root && adb shell mount -o rw,remount /vendor
adb pull vendor/etc/wifi/WCNSS_qcom_cfg.ini /YOUR/PATH/WCNSS_qcom_cfg.ini

Open the file with a text editor and on line 613 change sae_enabled=0 to sae_enabled=1 then

adb push /YOUR/PATH/WCNSS_qcom_cfg.ini vendor/etc/wifi/WCNSS_qcom_cfg.ini
adb reboot

That's all, after the reboot you will be able to scan and connect to WPA3 networks :)

NOTE: change is persistent, no need to do it every reboot
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] givemerobot:
Is it normal for Pixel Launcher to drain so much battery?
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Carlos2100:
Hola, buena rom pero no funciona el asistente de Google. Hola google con voz, no funciona.
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Toyohama:
There seems to be a problem with the deep sleep of the kernel, whether it is the plus version or the normal version, I also build your kernel for other roms, but the deep sleep is always 0%
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] -+BB+-:
Are you experiencing battery drain? You should try a full charge so stats will be reset, use your phone without charging and see if the battery consumption is still high. A logcat would be useful too. BTW there are multiple reports of this bug, seems related to Pixel launcher and has been reported on Pixel devices too, does not seem ROM/Device tree related, this bug should be reported to Google. Someone fixed it restoring deleted/disabled system apps, someone else changed the wallpaper and solved, other fixed it disabling google search function in search your phone section of pixel launcher settings and other are still living with it. Luckily, affects only a small amount of users (there are few reports, but compared the number of devices running pixel launcher are nothing), i'm running Pixel Experience on 4 different devices and I never had this issue

Tested Google assistant and Voice match on my Grus right now and both are working as expected, also checked soda logs and there are no errors, logs or never happened

Deep sleep works fine here, checked right now, what process is keeping the phone awake? Also if you compile the kernel for other ROMs be sure that the ROM has been built with EAS support or nothing will work

EDIT: Booted, waited 5 minutes and turned off the screen (also reported by kernel logs):

EDIT 2: I made the test with 3 commits not released yet, this, this and this, but none of them affect deep sleep, worst thing CPUFreq times usage driver can do is to cause a memory leak under some circumstances, but I never noticed that on Grus kernel
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Carlos2100:
Ya trabajo mi error
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Carlos2100:
What is It the difference between plus and normal? Thank so much
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] skoora05:
Everything works great except the vibration. I think they are very weak. I have everything maxed out in settings. And I can't change anything in karnel because I don't want root. Any ideas? Other roms have no problem. Maybe install another karnel, but which one? I don't know...
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] -+BB+-:
Haptic driver and vibrator intensities are 100% the same used on official Los 20
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] givemerobot:
I dont know, I switched to another launcher and the problem disappeared.

But I have another problem. I tried to install Magisk, but I cant do that because phone is still encrypted. Recovery is SHRP 3.7.0_12. It worked fine with another A13 rom.
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] skoora05:
I have install CherishOS , its's based in los 20 too, and have this problem too. i have install Alphadroid , it's based los 20 too and there vibration strangth is very good. so I don't know if in Alpha someone used a different driver or the problem is elsewhere.
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] -+BB+-:
I'm sorry but I don't support other recoveries and Magisk, and even if I highly discourage encryption removal (unless you are using it as a test phone without any sensible data on it) I suppose that some script remove encryption keys from the device and edit the fstab, you may need to check the recovery log and see why it fails, if that is the case this commit may be related. Also before trying to remove encryption i suggest to edit build.prop and change ro.adb.secure=1 to ro.adb.secure=0 and ro.secure=1 to ro.secure=0 or you won't be able to use logcat after you wipe data and the device bootloops

I need a working phone in these days and i cannot flash other ROMs so i cannot see differences by myself, does it happen with all kind of vibrations or only with some specific vibration (incoming calls, notifications, etc)?

EDIT: i took a look at Alphadroid sourced and

1 The kernel is different than los

2 I'm unable to find the device tree repo in their sources . I found vendor and kernel repo, but no device tree for grus or sdm710 devices, do you have a link?
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] skoora05:
All vibrations are muffled. It's like they're running at half power. You can ask the creator directly on telegram, I don't know about that. Telegram @elpaablo
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Lumyat:
Can anyone provide me the average SOT on this?
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Carlos2100:
Hola, la huella digital funciona muy mal con la pantalla de atenuación extrema. Espero que en la próxima actualización sea mejor por favor. The rest is wondeful
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] givemerobot:
I am not trying to remove encryption, I am trying to unlock my phone in recovery so I can install Magisk (so I can see logs and figure out why my pay app doesnt start sometimes) but the recovery which worked on another rom doesn't ask for unlock in this one. But I guess it's not that important now, because I installed Magisk in fastboot mode.
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] -+BB+-:
1 - Please write in English, if everyone starts to write in their language i will lose my life on Google translate page

2 - From Google official support page:

Extreme battery profile should be used only on "emergency" situation, the device is barely usable but you can still receive messages and calls, and that's the purpose of extreme battery profile. For a complete list of all the limitations take a look at the link i posted

I'm sorry, I misunderstood your message. Regarding recovery the issue may be related to different fstab, you should decompile the recovery and see if there are differences between the version shipped with the recovery and the version i provide with my ROM. There's the possibility that simply replacing the recovery fstab with the one provided with my ROM make it working, you can give it a try, in the worst case you'll end up with a broken recovery, not a big problem if fastboot is working.

Regarding rooting may I ask why you need it? Logcat works even without that, and if you need root permissions you can start a root shell with

adb root

Are you trying to do something that require root perms and cannot be done with adb using the command line?

Also, if you need to take a look at SELinux policy please let me know, in the kernel shipped with the ROM auditing has been disabled, I will share a kernel with audit enabled if you need it

EDIT:

I took a look at Alphadroid kernel defconfig and they are using a different driver for vibration
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Toyohama:
I usually use some apps for a few minutes before close the screen, and then deep sleep will fail. Deep sleep is normal for a period of time after reboot, until I wake up again and use some apps.

Besides, I don't seem to have enabled EAS

Is EAS enabled by default?

I revert commit and commit of your kernel because I want to use the old version of encryption to support rec decryption

This is my kernel link(aosp branch): https://github.com/Tkiliay/android_kernel_xiaomi_sdm710/commits/aosp
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] -+BB+-:
EAS is the Energy Aware Scheduling used by the kernel scheduler to predict power consumption, and unless you changed something in device tree you are using it, if something is not set properly from your device tree then deep sleep may be broken, you should take a look if values in your rootdir are really set on you phone when boot is completed

Regarding the first commit you reverted there's no need to remove it, simply disable INITRAMFS_IGNORE_SKIP_FLAG and will work in the old way.

The other commit you reverted requires (probably) more changes. If I remember well second stage support requires changes on device tree too, if you revert that on kernel side then you must revert it even on device tree

Also I'm not sure I understood what you are trying to do, do you want to drop FBE and bring back

FDE? If that is the case AOSP removed FDE support in Android 13, more work may be required on ROM sources in order to properly support FDE in Android 13

SELinux may also break things too, did you try to run in permissive mode?

Have you tried to boot in safe mode? Same behaviour?

There are a lot of things that may break deep sleep, only way to really understand what's wrong is to debug and check logcat and dmesg from the device, it's definitely something you merged in your kernel/dt or the ROM you are using, because I have no problem at all here:

I'm using my Grus as primary phone, these are the stats from last time i rebooted (when I posted the other screenshot), as you can see everything is working as expected here
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Toyohama:
Lineage official used second stage init mount and FBEV1. But grus does not have rec that can decrypt FBE normally. So I reverted them. This is my dt(derp branch), I tried turning off selinux but it still doesn't work. Log here logcat and dmesg
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] -+BB+-:
Yes, we are running FBE in legacy mode, what's the problem? We are following Android guidelines, I don't see any benefit in bring back FDE which probably requires more changes in AOSP sources, as FBEV1 is the only crypto allowed for devices launched with android <11.

Also did you take a look at your logs before posting? dmesg is full of

init: DM_DEV_STATUS failed for system: No such device or address
init: DM_DEV_STATUS failed for vroot: No such device or address
init: [libfs_mgr]dt_fstab: Skip disabled entry for partition system

These are caused by you changes in encryption on dt
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Toyohama:
I will restore these changes, but then there will be no rec that supports decryption:cry:After I build it, I will upload the log again
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] givemerobot:
I am trying to figure out why my pay app called Mir sometimes doesn't work, it might not start, crashes immediately, or hangs up on the its loading screen. So I installed MatLog with root privileges to gather logs when aforementioned app misbehaves. As far as I understand there is something to do with the app being hanged in the background.

Killing the app in apps overview doesnt solve the issue, but forse stop does.
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Toyohama:
This is the new log DMESG
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Phyo231:
Hello dear developer, I found the new bud while calling Via Viber. Have a great day bro✌️.
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] -+BB+-:
There are not so much info in locgat but tracking the PID of the app I saw this:

W/FirebaseInstanceId(20719): Token retrieval failed: SERVICE_NOT_AVAILABLE. Will retry token retrieval

There's a lot of reports for this error searching on Google, apparently is something related to the app and how firabase has been implemented

1 - As i told to another user please write in english

2 - This is a development thread for my ROM, not yours. You first post here was a report with deep sleep issues with my kernel and PE/PE Plus, but you are compiling your own version with your own changes, otherwise i should have several reports for this bug, but no one reported it since the initial release. Additionally you merged various commits that I don't have on both kernel and dt, and I'm not sure that are 100% safe/working on our device:

sdm710-common: overlay: Offload WM shell to another thread did you check that the separate thread is properly ending and doesn't stuck in the background? I'm asking because I'm not using it and I have no idea about how AOSP handle this but if the thread stuck in background may be a problem for deep sleep

sdm710-common: Disable per-cgroup PSI accounting it's a noop, needs the companion change in kernel

sdm710-common: Set virtual displays to 0 do we have that prop in QCOM sdm845 display HAL? I'm afraid that the prop does nothing

sdm710-common: rootdir: Get back to default from long-standing VM tweaks that values are already set by default on Android 13

arm64: Inline the spin lock function family should be used with LTO, but we are not compiling the kernel with LTO (at least not me)

sdm710-common: Remove LED entries nodes in init.qcom.rc are used by the torch, you can see by yourself the value on /sys/class/leds/led:switch_0/brightness changing when you enable/disable torch, pretty sure they are needed (if the nodes owner is the root user then probably not everything will work as expected)

sdm710-common: Reduce number of CPUs for system-background apps i'm not sure that this really help on Grus, at least not in my ROM where i have several services binded to system-background cpuset, should be tested if really has benefits and how impacts with deep sleep (it should not break it, but may reduce the deep sleep time)

You may also want to merge this: sched/tune: raise group count to 7 because we have 7 groups and without this sched tune is partially broken.

Last thing: did you try to see what process is keeping the phone awake? Why you are sure is kernel related? I'm asking because I did not see anything strange in dmesg

NOTE: I haven't reviewed all the changes merged in your branches, I just did a partial review but unless i missed them also CVE fixes has not been merged

Hi, I've tried to reproduce it with Whatsapp/Telegram/Viber but It's working fine with all the apps for me (I made 3 video calls for every app, worked all the times). It's happening even taking photo/videos with Viber or only when you made a video call?
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] makrei:
Is there pocket mode for this ROM? I have tap to wake on so I can use long press on fingerprint, but every time I put it in my pocket it always ends up opening the emergency menu.
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] givemerobot:
I wanna say thank you for your great rom, which is one of the best I've ever used, and for your support and patience.