yashsingh1/xdaforums huggingface dataset:
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Carlos2100:
Thanks for the effort. I hope the proximity sensor is solved and you get the fixed ROM.

thank you very much in advance
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Zzuk:
Hey. thanks a lot for solving this mistery. I guess the kernel you uploaded here should also work for LineageOS 20?

About which touch firmware you are talking? I know how to flash a ROM but Im not sure what I need to do here.
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] -+BB+-:
Hopefully tomorrow I will upload a kernel without LTO so it can be flashed without other requirements

EDIT: please do not spam the thread, use the edit button

I've linked the firmware files in my repo and explained how to put them in /system/etc/firmware before flashing in previous page. And answering the other question most probably yes, I don't remember anything I merged that could break the boot on LOS, but you must do 2 things:

1 - Unpack my boot.img and LOS boot.img you are using with AIK, replace LOS kernel in decompressed LOS boot.img with my kernel (replace ONLY the kernel) and repack the boot.img

2 - Enable ZSTD compression in /vendor/bin/init.qcom.post_boot.sh or you'll end up with no compression for ZRAM, in LOS you probably should replace

if [ "$low_ram" == "true" ]; then
echo lz4 > /sys/block/zram0/comp_algorithm
fi

with

echo zstd > /sys/block/zram0/comp_algorithm
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Zzuk:
This worked perfectly fine. Thanks for taking the time to write this down. You got a paypal for donations?
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Pumukk:
Last version is on the first post?
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] -+BB+-:
Ok, at this point better release a new build with the proximity fixes and other changes that greatly improve power saving. This update include all changes released with the previous ROM and these additional changes:

ROM

- Synced PE sources with latest PE changes

Kernel

- msm: camera: Stub out the camera_debug_util API and compile it out

- sdm710-common.config: disable sde rotator debugging

- drm/msm/dsi-staging: Fix transposed panel_switch and panel_post_switch

- (1/2) Teckpack: fix compiling of techpack drivers

- (2/2) Teckpack: fix compiling of techpack drivers

- qcacld-3.0: nuke qcom_rx_wakelock

Device tree (sdm710-common)

- powerhints: reduce launch boost

- Change default GPU idle timeout to 60ms

- powerhint: fixup io_percent default value

- powerhint: Set camera cpuset to little cores when unused

- Add Flipendo powerhints

- bring back SoundTrigger

- sepolicy:fix GCam access restricted DSP device node

- sepolicy: allow system server to read battery stats

- wlan: enable QPower and Deep Sleep at the same time

- wlan:Smarter decisions on whether to use a 2- or 5Ghz AP.

Device tree (Grus)

- Revert "(2/3) Drop SoundTrigger"

Vendor (Grus)

- [DO NOT MERGE] grus: add goodix firmware to build --> allow to flash LTO kernel without touch not working issue

Vendor (sdm710-common)

- Revert "(3/3) Drop SoundTrigger"

Download links

Pixel Experience 13 Plus

Pixel Experience 13 --> will be available hopefully friday

NOTE: if Google Voice Match does not work clear the voice model and set it up again, this is caused by the migration to SoundTrigger from Hotword enrollment apks

LTO testing kernel can be downloaded from here and flashed without any issue, I've already included touch firmware files inside the ROM

@fabiomich : Termux kernel updated, synced with my LTO branch and removed the Android warn at boot, expose the real defconfig should not be needed now that all deps has been satisfied

Thanks, I do not accept donation because this is my hobby and I don't need money, but I really really appreciate your intention, again, thanks <3

And also thanks for make me smile, you are a LOS user and want to make a donation for my reply and the proximity fix, while 95% of people using my ROM in months did not have the time (yet) to push a thanks button... It's for the few people like you that people like me are still releasing their work for free :)

If you are interested you can try this:

1 - Flash the new LTO kernel I provided

2 - Replace /vendor/etc/wifi/WCNSS_qcom_cfg.ini with my WCNSS_qcom_cfg.ini

3 - Replace /vendor/etc/powerhint.json with my powerhint.json

4 - Replace /vendor/bin/init.qcom.post_boot.sh with my init.qcom.post_boot.sh

These changes allow LITTLE cores to use 300 Mhz freqs, reduce the battery usage from power hints, and enable Wlan QPower + Deep Sleep at the same time, improving a lot power saving

Last thing: I saw on LOS topic multiple people trying to get a working/compatible camera lib patched for GCAM, if you need it use this, it' s the LOS lib patched, it's 100% compatible and working even on LOS
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] fabiomich:
thanks for your work/update

I tried the new boot-LTO-Termux and herein the list of the enabled features

have I to do other modification to have all the features enabled?
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] -+BB+-:
That's expected because as you can see in latest kernel when you boot the device the "Internal Error" popup does not appear, because we are providing a fake defconfig for android, termux configuration scripts pick the same fake defconfig, all that option are enabled and according to Termux readme on their git you should be able to use all that features in docker, even if conf script says that are missing

Here's the real defconfig used for compiling, you can check that the features reported as missing are enabled in kernel

PS: if you find something not really enabled in real defconfig let me know, I will see if I can add to next build
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Zzuk:
Hey and thank you for the nice words. This one is definetly also nice for me and a way to learn something.

I did the following:

1. Download the boot-lto image from https://androidfilehost.com/?fid=10620683726822066611

2. Download latest LineageOS 20 for Grus: https://wiki.lineageos.org/devices/grus/

3. Unpack both boot images (LOS boot.img and the one provided from step 1 by you)

4. Replace just "\split_img\boot.img-kernel" of the splitted parts from the LineageOS 20 boot.img

5. Repack it aftwards and place the required bin files you provided on page 7 using the recovery before the fastboot flash:

adb push "C:\Users\XXX\Downloads\goodix_gt9886_fw_f2.bin" /system/etc/firmware

adb push "C:\Users\XXX\Downloads\goodix_gt9886_cfg_f2.bin" /system/etc/firmware

6. Flash the repacked boot.img (boot.img-kernel replaced with the counterpart from your LTO kernel)

7. Afterwards boot straight to recovery again and do the following with the files provided by you:

adb push "C:\Users\XXX\Downloads\WCNSS_qcom_cfg.ini" /vendor/etc/wifi/WCNSS_qcom_cfg.ini

adb push "C:\Users\XXX\Downloads\powerhint.json" /vendor/etc/powerhint.json

adb push "C:\Users\XXX\Downloads\init.qcom.post_boot.sh" /vendor/bin/init.qcom.post_boot.sh

After step 7 I do a final reboot but the touchscreen is not working. I guess LineageOS might have a different folder for the firmware which is not /system/etc/firmware?

I can definetly see after repacking that the new boot.img I created is different:

Do you have any idea what I could have done wrong?
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] -+BB+-:
You did everything right, that's strange, also the directory should be the same because it's the kernel goodix driver that search on that path. Could you please check if the files are really there?

adb shell ls /system/etc/firmware

PS: assuming you used a rooted adb shell and remounted system as rw there's the possibility that files aren't copied if the folder does not exist, you must first create it using adb:

adb shell mkdir /system/etc/firmware

EDIT: If doesn't work please upload the full dmesg picked a few seconds after the device booted, I'm curious to see what's wrong with it
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Zzuk:
Hey, yes I previously created the directory using an adb shell and mkdir.

After pushing the files I also checked the files where there using adb shell ls.

I will redo the process with twrp later and make sure that the files are really there using its filebrowser. The last time I used the lineageOS recovery.

Right now on phone. Will report later.
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Zzuk:
You are indeed right. After restarting the recovery the new files are also gone. I am right now working on some little script to automate creating the files and folders:

adb root
adb remount

adb push "C:\Users\Ano\Downloads\old\WCNSS_qcom_cfg.ini" /vendor/etc/wifi/WCNSS_qcom_cfg.ini
adb push "C:\Users\Ano\Downloads\old\powerhint.json" /vendor/etc/powerhint.json
adb shell mkdir /vendor/bin/
adb push "C:\Users\Ano\Downloads\old\init.qcom.post_boot.sh" /vendor/bin/init.qcom.post_boot.sh

adb shell mkdir /etc/firmware
adb shell mkdir /system/etc/firmware
adb shell mkdir /vendor/firmware
adb push "C:\Users\Ano\Downloads\old\goodix_gt9886_fw_f2.bin" /etc/firmware
adb push "C:\Users\Ano\Downloads\old\goodix_gt9886_cfg_f2.bin" /etc/firmware
adb push "C:\Users\Ano\Downloads\old\goodix_gt9886_fw_f2.bin" /system/etc/firmware
adb push "C:\Users\Ano\Downloads\old\goodix_gt9886_cfg_f2.bin" /system/etc/firmware
adb push "C:\Users\Ano\Downloads\old\goodix_gt9886_fw_f2.bin" /vendor/firmware
adb push "C:\Users\Ano\Downloads\old\goodix_gt9886_cfg_f2.bin" /vendor/firmware

PAUSE

Ignore pushing the files also to the wrong location please. this was only for my testing.

Edit: Cant get the firmware files to remain a reboot and the fastboot flash of the modified boot.img will never find them. Any idea here?

Edit 2: Got it to work, After executing the above script I had to do a straight reboot to bootloader and flash modified boot.img followed by another reboot straight to system. Then it worked.

Since changes from recovery are reverted I guess I have to make the changes to the following files with magisk right?

adb push "C:\Users\XXX\Downloads\old\WCNSS_qcom_cfg.ini" /vendor/etc/wifi/WCNSS_qcom_cfg.ini adb push "C:\Users\XXX\Downloads\old\powerhint.json" /vendor/etc/powerhint.json adb shell mkdir /vendor/bin/ adb push "C:\Users\XXX\Downloads\old\init.qcom.post_boot.sh" /vendor/bin/init.qcom.post_boot.sh

Edit 3: Got it to work by executing the upper part of my above script while booted into Android and having root via Magisk aswell ADB root enabled in development settings. This way I could replace WCNSS_qcom_cfg.ini, powerhint.json and init.qcom.post_boot.sh

Now testing the kernel under LineageOS 20. Will report back with battery stats soonish.

Thanks once again! <3
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Pumukk:
Will there be an easier way to flash it in the future? For newbies this is a bit complicated. Thanks for your time
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] fabiomich:
GREAT GREAT JOB

It works very well, fake defconfig is been a great idea, No warnings on the boot with all the kernel features enabled

I've just done some containers with docker, you can see the result in the attachment

now I have to find how it's feasable to do in termux and also the performance/speed

thanks again
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Zzuk:
Little feedback:

My setup is Lineageos 20 latest official nightly build for Grus with the boot.img I created with the steps explained in the quoted message.

First thing first: The proximity sensor is finally working again.

With EX Kernel Manager I activated powersave for CPU-Governor and CPU-Governor (Block 2).

All special features like AOD that could keep the phone active are deacivated. Vanced Micro G is battery optimized like all kind of other Apps that dont need to run. Each 30 Minute PhoneProfilePlus is checking the location to activate a possible profile but thats about it.

With Screen On I have from 9% to 14% battery drain per hour depending on brightness and what I am doing (Maps Navigation and Youtube in Background is about 14%).

Screen off is ranging from 1,5% (sleeping and nothing is happening - 10% awake) to 4% (40% awake) with bluetooth headphone connected and a podcast playing.

I just flashed Universal GSM Doze and activated energy saving. Lets see how it effects the screen off drain and awake percentage. Will edit later.

This is definetly way better than what I get with the current LOS 20 Kernel but at the same time I have the feeling that something got worse battery wise in late June / early July.

I have an old Kernel from 10.06 for GRUS which is working fine for all LOS/PE/PixelOS and having screen off drain of only 0,5% and screen on from around 7% to 12%.

Edit: Energy Saver on and Universal GSM Doze with Screen off = 0,6% drain per hour
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Carlos2100:
Hi, excellent work, a little thing, the vibration is very, very low. It's possible set up stronger
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Zzuk:
Wow yeah maybe the governor settings were the culprit here. Im right now switching to an unofficial PixelOS build in another attempt to find the most battery friendly rom for my grus but I will definetly revisit LOS 20 without altering the governor to see if it does make a difference. Luckily my routine for switching rom is taking only 20 minutes each time with SwiftBackup etc etc.

Thank you. Those internals are actually kinda interesting.
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] nathankaunang:
work too on other LO ?like LO @kyasu build?
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] masterdex:
really thanks dev I've been waiting for PE for a long time new life for our little one.
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] -+BB+-:
Not sure, but should work pretty fine on all ROMs forked from official LOS 20 repo (the same can be done with other kernels and my ROM), only thing that must be changed is the zstd compression for ZRAM, init.qcom.post_boot.sh, WCNSS_qcom_cfg.ini and powerhint.json are optional, and should be compared with the file in ROM you are using (100% safe on official LOS, not sure on other ROMs)

PS: I've updated my kernel main branch with everything I was testing except LTO, can be compiled and flashed with Anykernel without the need to copy touchscreen firmware files in system partition
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] kolouch.petr:
thank you for July update, I confirm WPA3 is working fine without any problem (y)(y)
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Pumukk:
Deleted
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] talhabw:
Hi, I wonder what do you think is the best rom for daily usage? I currently use a 2022 build of LOS20 Unoffical.
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Zzuk:
Im also on the unofficial LOS 20 now. After installing all kind of ROMs (cherish, pixelOS, Pixel Experience, Official LOS 20, CrDroid, Unofficial LOS20) I can vouch for this one.

Battery backup was best on crDroid and the unofficial LOS20 but since crDroid is having FPS spikes for a game I play on my phone I chose this one. Also this ROM doesnt has the proximity sensor bug the official is stil having as we speak.

In terms of bugs in daily use all ROM were the same. None had any dealbreaker bug.
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] talhabw:
Is there a way to hide At a Glance widget? And remove the bottom google bar? Rom looks good. I was going to observe the battery for a few days, and decide between LOS20 and this, but Glance widget just takes too much space without much useful info, and it messes up with my standard main page arrangement.

Also, @Zzuk thanks for sharing your experience.
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Dummy0016:
Face retouching is not working. Tried different version of gcam mods.
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] fabiomich:
thanks again for the termux boot.img the docker containers work very well

I'm trying to use the battery only as backup of ac charger, is there any way to stop the battery charging?

I tested acc vr25 as magisk module but it doesn't work

the same result setting 0/1 on

/sys/class/power_supply/battery/charging_enebled

/sys/class/power_supply/battery/input_suspend

are there a specific folder in this version of PE where I can manage the battery charger?
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] -+BB+-:
Nice catch, i can reproduce that, will take a look at it but I don't know what can be done as the whole camera stack is closed source. It would be useful to know if it was working in previous releases (I'm not a big camera user, honestly I never tried that feature before your report)

I' ve tried with adb and it's working fine for me:

adb root
echo 1 > /sys/class/power_supply/battery/input_suspend

This stops battery charging, phone is still connected and your PC recognise it so you can work with adb, but be aware that when the screen is off it doesn't enter in deep sleep state, if you use root you can probably set some kind of task with tasker or similar app (ie check battery percentage every 10/15 min and start charging if battery < 20% or stop charging if battery is > 80%)

EDIT: remember that /sys/class/power_supply/battery/input_suspend value will be reset when you connect/disconnect the usb cable, you must set it manually everytime you connect the phone
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] fabiomich:
Thanks, battery control works with /sys/class/power_supply/battery/input_suspend and input_suspended, probably when I tested it I done something wrong

now I'm trying to use Zigbee USB like conbee II, zbdongle-e and -p and also Silicon Labs EFR32MG2

I find them i.e. in /dev/bus/usb/001/002 and I can ask the permission with termux-usb -r /dev/bus/usb/001/002 but they doesn't work

If I searched well they use a serial driver, these are chips cp2102(N) ch9102f ch340 but problably this driver is not loaded

I built the driver ch340.ko but although the kernel has been set for loading modules it doesn't work

Is it feasible to enable this loading method in android?

If not, is it possible to insert these drivers in the kernel?

Thanks a lot again

drivers found

cp2102

CP210x USB to UART Bridge VCP Drivers - Silicon Labs

The CP210x USB to UART Bridge Virtual COM Port (VCP) drivers are required for device operation as a Virtual COM Port to facilitate host communication with CP210x products. These devices can also interface to a host using the direct access driver.

www.silabs.com

ch340

驱动程序 - 南京沁恒微电子股份有限公司

www.wch.cn

ch34x

GitHub - gorgiaxx/CH34x-Driver-Linux: CH340/CH341 Driver for Linux

CH340/CH341 Driver for Linux. Contribute to gorgiaxx/CH34x-Driver-Linux development by creating an account on GitHub.

github.com
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Dummy0016:
Thank you sir.

I used this rom since May build and face retouching is not working at that time and up to current build.
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Dummy0016:
My battery is draining so fast even when not use. Can you guys confirm ?
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Yos_g:
Thanks for this wonderful rom!

It has everything I wanted. And the battery life is great!

Just something I have noticed - it seems like the phone is a bit sluggish on some apps... Like it's throttling even though the temps are OK... Are there any kernel settings I can change? Any other kernel that will support changing the settings? Any help will be appreciated
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] drik05:
It appears that some apps are not functioning correctly. Could this issue be related to the ROM? The screenshot below shows error. It was working fine on previous May build.

I only recently noticed this error because I rarely use the app.
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] Lumyat:
AOD uses a ton of battery at night because it cannot connect with proximity sensor to tell if the room is dark or it's facing downward.
[Xiaomi Mi 9 SE ROMs, Kernels, Recoveries, & Other ] thony11:
Hii,,, where is new update ?.
[Google Pixel 7 Pro] comicbookguy72:
Hi all! Just coming over from my trusty OP7Pro this week after 3 1/2 years. The phone seems great even though I don't like the punch hole from camera but I've noticed on Pixel and Nova launchers in landscape mode the widgets and icons won't use all the screen. There's a huge gap before the dock on the right and the punch hole on the left sides that's not useable. Seems such a waste and I was wondering if there was a fix or workaround? Apologies for the work in progress kwgt widgets in the screenshot.
[Google Pixel 7 Pro] HipKat:
Portrait mode isn't great. For one, it makes the text on my widgets get very tine and doesn't scale the wallpaper
[Google Pixel 7 Pro] xunholyx:
Use the None Display Cutout Magisk module to fix it

GitHub - Magisk-Modules-Repo/noneDisplayCutout

Contribute to Magisk-Modules-Repo/noneDisplayCutout development by creating an account on GitHub.

github.com

https://xdaforums.com/t/module-none-display-cutout-v2.4227537/
[Google Pixel 7 Pro] comicbookguy72:
I'm using LSposed and the phone's developer options to hide the camera but they don't seem to help. I'll try this later tho
[Google Pixel 7 Pro] comicbookguy72:
Ive been using kwgt for ages to sort that type of problem out. I tend to build my own widgets...
[Google Pixel 7 Pro] comicbookguy72:
Thanks for this. The "ignore cutout" setting is perfect!
[Google Pixel 7 Pro] HipKat:
I do the same. I just never have my phone in Landscape mode without an app being open, so I ignore it
[Google Pixel 7 Pro] comicbookguy72:
I have a specific launcher page and widget for landscape mode in the car
[Samsung Galaxy S23 Ultra] thecrater:
Hello,

I don't know if this is a bug, a "feature" or just my device but would anyone be able to check their "Call & Text on other devices" Quick Panel icon to see if it toggles the feature on or off and let me know? Mine takes me to the settings. I used to have it enabled all the time on my phone and I would toggle it on the tablet as required. That way I get to enable it only when I need to use it on the tablet.

Since migrating to my S23 U from my S22 U and updating my tablet to One UI 5.1, the option now takes me to the settings page instead of simply toggling the feature. This is the case on both the phone and the tablet (S8 +) so I think it's either a bug or a "feature"

Thanks in advance
[Samsung Galaxy S23 Ultra] termdj:
I don't have a S23u, but a S22u and tab s8 ultra...my s22u was setup with call & text with the tabs s8ultra. worked like a charm. My s22u screen broke and sent in for repairs. I used an old s9+ lying around. For some reason it asked me to change to s9+ for call & text. I ignored the pop up...when I got my s22u back call & text was disabled. When opening call & text I had to re-register/configure my s22u for call & text as it automatically changed it to my s9+, although it never worked on s9+. After changing settings it worked on s22u and tab s8u. re-register/configure call & text
[Samsung Galaxy S23 Ultra] Barmenchik:
Yes, the same. The icon is not activated (disabled) although the function itself is enabled. When pressed, it jumps to the Settings of this function, where Calls on other devices and Messages on other devices are now separated. In Calls, my GW5Pro watch and in Messages - empty!
[Samsung Galaxy S23 Ultra] Ornisense:
Google messages has this bug that keeps any notice below sms screen flickering forever.
[Samsung Galaxy S23 Ultra] thecrater:
Looks like they modified the Quick Panel icon to take you to the settings so that you can toggle individual options i.e. call and/or text on other devices. I can see how that could be useful but I really miss the ability to simply keep the feature "on" on the phone and toggle it on/off on the tablet as required.

I would have preferred two icons one to toggle calls and one to toggle texts if they wanted to give users the option instead of the extra steps especially since it's called the Quick Panel for a reason lol

Thanks for looking guys. I really appreciate it