Mate Proximity sensor missing in CIT settings so always when you try to unlock show info that is covering something that sensor.

miui-n can't use f2fs, request to add support.

couldnt create a pull request on your repo,
you can cherry pick
chhapil@b4df689

i'm testing this, but so far its good

Hello.
I've installed PIE on mi5s using this guide
With your latest kernel for P camera isn't working, but it works with BG kernel.
Could you please take a look?

Unable to remember screen brightness for certain lighting condition like default MIUI does.q

In the second half of the typing, the screen will flicker and flicker more frequently in the game

miui 10.2 Wifi dosen't connect some AP.

Yesterday,I flash this kernel,and when I reboot my phone,it interrupt and my phone's screen show "MI"logo so long time so that i have to flash MIUI offical package again to save my phone ,my MIUI version is MIUI 10 Oreo-8.6.14，I wanna a Kernel to control Sdm 821(msm8996 pro)myself，Are you going to update it?

I noticed that the thermal control of this kernel is unable to override the Xiaomi's.
I didn't change the value, just simply enabled the intellithermal & core control.

Xiaomi's tried to cap the temp to 40C, while the kernel throttle at 90C & temp limit 80C (default).

The reality was the phone throttle everything down and I can only get 43C max.

Then I deleted the Xiaomi's thermal-engine-8996.conf file, thus freeing the phone from Xiaomi's thermal control.
Reboot.
Intellithermal & core control enabled, CPU throttle value 70C, temp limit 60C.

Gaming time now, the temp soar as high as 90C and stays there, no throttling.
It doesn't even honor the kernel thermal settings.

FYI, xiaomi curiously got 3 encrypted thermal-engine-8996 file:
thermal-engine-8996.conf
thermal-engine-8996-map.conf
thermal-engine-8996-high.conf

but the only file that really affect the phone was thermal-engine-8996.conf

i reckon you already solved the segmentation fault error getting thrown from cypto backage when using gcc 7 or ubertc 8.
how did u fixed it?

kcal settings disabling after screen lock on miui oreo mi5s. the values have to change with every lock & unlock.
i dont know its related with kernel or miui rom.

Hello Jonas.
Best kernel ever made to gemini. Period.
I've been testing most of them including Miui , HMP and EAS . And man.. even Pie support!
I wonder why no one had ever mentioned that , but Quick Charge 3.0 won't be recognized , giving a +17~20 minutes in any charging cycle.
Moreover, with voltage detector it didn't of course trigger the 9V charging resulting in 5V 2A fast charge but not 9V.

You are the best , keep up the flawlessly excellent work.
Danik.

https://github.com/JonasCardoso/android_kernel_xiaomi_msm8996/releases/tag/FloppyKernel-01%2F11%2F2020-Eleven-HMP

This (first 4) Kernel Not Boot with lineage-18.1-20210718-nightly

I see a screen that says MI (30 sec) and the phone turns off .

Natrium_defconfig modifies CONFIG_THERMAL_MONITOR=y to CONFIG_THERMAL_MONITOR=n, which causes frequent auto reboot, especially when the frequency is increased. this is not auto reboot caused by overheat,Is there a workaround?
Because I don't want to start this function.

I'm running kernel 1501 and it's ok. Tried to use later builds, but it is extremely laggy.
On mi5s, lineage 8.1, latest

MIUI Nougat latest build for Natrium got Wifi MAC changed to 00:03:7F:C2:00:43 but working properly.

Tried the Google & Linaro.

console-ramoops.txt
Attached is my console-ramoops file which from my understanding is the replacement to the last_kmsg file in newer android versions.
This seems to be happening on global developer version 8.2.8. Some of the data looks a bit screwy and I am not sure why... like "size 3% MiB" or U3ing instead of using.
Although, looking at the log, I am not positive if this is the TWRP booting log or the log that is being unhappy booting the Floppy Kernel.

3D touch and Reading mode cannot be used

My phone is MI5's latest AEX
And when I use this kernel for a while, the screen will flicker at about 1/3, but I can guarantee that ROM and the kernel are clean.

Natrium_defconfig modifies CONFIG_THERMAL_MONITOR=y to CONFIG_THERMAL_MONITOR=n, which causes frequent auto reboot, especially when the frequency is increased. this is not auto reboot caused by overheat,Is there a workaround?
Because I don't want to start this function.