[KERNEL][EMUI 9][P20 lite] Phenix kernel

[TristanL]

Hi!
Did you try the test kernel in previous post?

Cheers

not yet sorry :/ , I'll do it this weekend

 

[TureX]

not yet sorry :/ , I'll do it this weekend

No problem! take your time, meanwhile i take a look at logs

Edit: i can't acces to dmesg log

 

[TristanL]

No problem! take your time, meanwhile i take a look at logs

Edit: i can't acces to dmesg log

Now it should work, I tested it in Private naviagation https://drive.google.com/file/d/1TBnMotBQLUG_dHFyJ8Fbe3KPeDyc3iMf/view?usp=sharing

 

[Frax3r]

Btw my situation is still the same. Even newpipe with adaptive brightness on didn't flicker. Let me know if I can help with anything else.

 

[TureX]

Btw my situation is still the same. Even newpipe with adaptive brightness on didn't flicker. Let me know if I can help with anything else.

Hi!

Could you please give me the output of dmesg | grep 'avc: denied' ?

Cheers

 

[Frax3r]

Hi!

Could you please give me the output of dmesg | grep 'avc: denied' ?

Cheers

anne:/ # dmesg | grep 'avc: denied'
[219306.854980] [pid:422,cpu3,logd.auditd]type=1400 audit(1633522522.600:183888): avc: denied { execute_no_trans } for pid=29758 comm="init" path="/vendor/bin/hw/vendor.huawei.hardware.graphics.displayeffect@1.0-service" dev="mmcblk0p57" ino=471 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
[219342.193817] [pid:422,cpu1,logd.auditd]type=1400 audit(1633522570.870:183960): avc: denied { execute_no_trans } for pid=29776 comm="init" path="/vendor/bin/hw/vendor.huawei.hardware.graphics.displayeffect@1.0-service" dev="mmcblk0p57" ino=471 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
[219357.239959] [pid:422,cpu3,logd.auditd]type=1400 audit(1633522570.870:183960): avc: denied { execute_no_trans } for pid=29776 comm="init" path="/vendor/bin/hw/vendor.huawei.hardware.graphics.displayeffect@1.0-service" dev="mmcblk0p57" ino=471 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
[219376.973449] [pid:422,cpu2,logd.auditd]type=1400 audit(1633522605.730:184003): avc: denied { execute_no_trans } for pid=29789 comm="init" path="/vendor/bin/hw/vendor.huawei.hardware.graphics.displayeffect@1.0-service" dev="mmcblk0p57" ino=471 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
[219381.513366] [pid:422,cpu3,logd.auditd]type=1400 audit(1633522605.730:184003): avc: denied { execute_no_trans } for pid=29789 comm="init" path="/vendor/bin/hw/vendor.huawei.hardware.graphics.displayeffect@1.0-service" dev="mmcblk0p57" ino=471 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
[219499.973754] [pid:422,cpu0,logd.auditd]type=1400 audit(1633522729.069:184061): avc: denied { execute_no_trans } for pid=29826 comm="init" path="/vendor/bin/hw/vendor.huawei.hardware.graphics.displayeffect@1.0-service" dev="mmcblk0p57" ino=471 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
[219508.796630] [pid:422,cpu1,logd.auditd]type=1400 audit(1633522729.069:184061): avc: denied { execute_no_trans } for pid=29826 comm="init" path="/vendor/bin/hw/vendor.huawei.hardware.graphics.displayeffect@1.0-service" dev="mmcblk0p57" ino=471 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
[219531.586578] [pid:422,cpu0,logd.auditd]type=1400 audit(1633522760.219:184134): avc: denied { sys_admin } for pid=29866 comm="adbd" capability=21 scontext=u:r:adbd:s0 tcontext=u:r:adbd:s0 tclass=capability permissive=0
[219532.918395] [pid:422,cpu1,logd.auditd]type=1400 audit(1633522760.219:184134): avc: denied { sys_admin } for pid=29866 comm="adbd" capability=21 scontext=u:r:adbd:s0 tcontext=u:r:adbd:s0 tclass=capability permissive=0
[219532.918426] [pid:422,cpu1,logd.auditd]type=1400 audit(1633522761.549:184135): avc: denied { read } for pid=945 comm="android.bg" name="zram0" dev="sysfs" ino=39575 scontext=u:r:system_server:s0 tcontext=u:object_r:sysfs_zram:s0 tclass=lnk_file permissive=0
[219534.433746] [pid:422,cpu3,logd.auditd]type=1400 audit(1633522761.549:184136): avc: denied { read } for pid=945 comm="android.bg" name="zram0" dev="sysfs" ino=39575 scontext=u:r:system_server:s0 tcontext=u:object_r:sysfs_zram:s0 tclass=lnk_file permissive=0
[219534.433807] [pid:422,cpu3,logd.auditd]type=1400 audit(1633522763.069:184137): avc: denied { execute_no_trans } for pid=29876 comm="init" path="/vendor/bin/hw/vendor.huawei.hardware.graphics.displayeffect@1.0-service" dev="mmcblk0p57" ino=471 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
[219539.458251] [pid:422,cpu3,logd.auditd]type=1400 audit(1633522763.069:184137): avc: denied { execute_no_trans } for pid=29876 comm="init" path="/vendor/bin/hw/vendor.huawei.hardware.graphics.displayeffect@1.0-service" dev="mmcblk0p57" ino=471 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
[219539.458343] [pid:422,cpu3,logd.auditd]type=1400 audit(1633522768.089:184138): avc: denied { execute_no_trans } for pid=29880 comm="init" path="/vendor/bin/hw/vendor.huawei.hardware.graphics.displayeffect@1.0-service" dev="mmcblk0p57" ino=471 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
[219544.476318] [pid:422,cpu1,logd.auditd]type=1400 audit(1633522768.089:184138): avc: denied { execute_no_trans } for pid=29880 comm="init" path="/vendor/bin/hw/vendor.huawei.hardware.graphics.displayeffect@1.0-service" dev="mmcblk0p57" ino=471 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
[219544.476470] [pid:422,cpu1,logd.auditd]type=1400 audit(1633522773.109:184139): avc: denied { execute_no_trans } for pid=29884 comm="init" path="/vendor/bin/hw/vendor.huawei.hardware.graphics.displayeffect@1.0-service" dev="mmcblk0p57" ino=471 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
[219545.281005] [pid:422,cpu1,logd.auditd]type=1400 audit(1633522773.109:184139): avc: denied { execute_no_trans } for pid=29884 comm="init" path="/vendor/bin/hw/vendor.huawei.hardware.graphics.displayeffect@1.0-service" dev="mmcblk0p57" ino=471 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
[219545.281127] [pid:422,cpu1,logd.auditd]type=1400 audit(1633522773.909:184140): avc: denied { dac_override } for pid=505 comm="usb@1.0-service" capability=1 scontext=u:r:hal_usb_default:s0 tcontext=u:r:hal_usb_default:s0 tclass=capability permissive=0
[219549.489593] [pid:422,cpu2,logd.auditd]type=1400 audit(1633522773.909:184141): avc: denied { dac_override } for pid=505 comm="usb@1.0-service" capability=1 scontext=u:r:hal_usb_default:s0 tcontext=u:r:hal_usb_default:s0 tclass=capability permissive=0
[219549.489654] [pid:422,cpu2,logd.auditd]type=1400 audit(1633522778.119:184142): avc: denied { execute_no_trans } for pid=29917 comm="init" path="/vendor/bin/hw/vendor.huawei.hardware.graphics.displayeffect@1.0-service" dev="mmcblk0p57" ino=471 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
[219554.510894] [pid:422,cpu0,logd.auditd]type=1400 audit(1633522778.119:184142): avc: denied { execute_no_trans } for pid=29917 comm="init" path="/vendor/bin/hw/vendor.huawei.hardware.graphics.displayeffect@1.0-service" dev="mmcblk0p57" ino=471 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
[219554.511016] [pid:422,cpu0,logd.auditd]type=1400 audit(1633522783.139:184143): avc: denied { execute_no_trans } for pid=29922 comm="init" path="/vendor/bin/hw/vendor.huawei.hardware.graphics.displayeffect@1.0-service" dev="mmcblk0p57" ino=471 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
[219556.041229] [pid:422,cpu0,logd.auditd]type=1400 audit(1633522783.139:184143): avc: denied { execute_no_trans } for pid=29922 comm="init" path="/vendor/bin/hw/vendor.huawei.hardware.graphics.displayeffect@1.0-service" dev="mmcblk0p57" ino=471 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
[219556.041351] [pid:422,cpu0,logd.auditd]type=1400 audit(1633522784.669:184144): avc: denied { sys_admin } for pid=29926 comm="adbd" capability=21 scontext=u:r:adbd:s0 tcontext=u:r:adbd:s0 tclass=capability permissive=0
[219559.518066] [pid:422,cpu1,logd.auditd]type=1400 audit(1633522784.669:184144): avc: denied { sys_admin } for pid=29926 comm="adbd" capability=21 scontext=u:r:adbd:s0 tcontext=u:r:adbd:s0 tclass=capability permissive=0
[219559.518127] [pid:422,cpu1,logd.auditd]type=1400 audit(1633522788.149:184145): avc: denied { execute_no_trans } for pid=29932 comm="init" path="/vendor/bin/hw/vendor.huawei.hardware.graphics.displayeffect@1.0-service" dev="mmcblk0p57" ino=471 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
[219564.534912] [pid:422,cpu1,logd.auditd]type=1400 audit(1633522788.149:184145): avc: denied { execute_no_trans } for pid=29932 comm="init" path="/vendor/bin/hw/vendor.huawei.hardware.graphics.displayeffect@1.0-service" dev="mmcblk0p57" ino=471 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
[219564.535095] [pid:422,cpu1,logd.auditd]type=1400 audit(1633522793.169:184146): avc: denied { execute_no_trans } for pid=29938 comm="init" path="/vendor/bin/hw/vendor.huawei.hardware.graphics.displayeffect@1.0-service" dev="mmcblk0p57" ino=471 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
[219569.542205] [pid:422,cpu3,logd.auditd]type=1400 audit(1633522793.169:184146): avc: denied { execute_no_trans } for pid=29938 comm="init" path="/vendor/bin/hw/vendor.huawei.hardware.graphics.displayeffect@1.0-service" dev="mmcblk0p57" ino=471 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
[219569.542266] [pid:422,cpu3,logd.auditd]type=1400 audit(1633522798.169:184147): avc: denied { execute_no_trans } for pid=29942 comm="init" path="/vendor/bin/hw/vendor.huawei.hardware.graphics.displayeffect@1.0-service" dev="mmcblk0p57" ino=471 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
[219574.563354] [pid:422,cpu3,logd.auditd]type=1400 audit(1633522798.169:184147): avc: denied { execute_no_trans } for pid=29942 comm="init" path="/vendor/bin/hw/vendor.huawei.hardware.graphics.displayeffect@1.0-service" dev="mmcblk0p57" ino=471 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
[219574.563385] [pid:422,cpu3,logd.auditd]type=1400 audit(1633522803.189:184148): avc: denied { execute_no_trans } for pid=29947 comm="init" path="/vendor/bin/hw/vendor.huawei.hardware.graphics.displayeffect@1.0-service" dev="mmcblk0p57" ino=471 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
[219579.576751] [pid:422,cpu0,logd.auditd]type=1400 audit(1633522803.189:184148): avc: denied { execute_no_trans } for pid=29947 comm="init" path="/vendor/bin/hw/vendor.huawei.hardware.graphics.displayeffect@1.0-service" dev="mmcblk0p57" ino=471 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
[219579.576873] [pid:422,cpu0,logd.auditd]type=1400 audit(1633522808.209:184149): avc: denied { execute_no_trans } for pid=29951 comm="init" path="/vendor/bin/hw/vendor.huawei.hardware.graphics.displayeffect@1.0-service" dev="mmcblk0p57" ino=471 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
[219584.593566] [pid:422,cpu3,logd.auditd]type=1400 audit(1633522808.209:184149): avc: denied { execute_no_trans } for pid=29951 comm="init" path="/vendor/bin/hw/vendor.huawei.hardware.graphics.displayeffect@1.0-service" dev="mmcblk0p57" ino=471 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
[219584.593688] [pid:422,cpu3,logd.auditd]type=1400 audit(1633522813.219:184150): avc: denied { execute_no_trans } for pid=29955 comm="init" path="/vendor/bin/hw/vendor.huawei.hardware.graphics.displayeffect@1.0-service" dev="mmcblk0p57" ino=471 scontext=u:r:init:s0 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=0
anne:/ #

You should know that I switched back to backed up kernel from your los build (there isn't any difference between the two right?) and my uptime is around 48 hours. have fun with the log

 

[TureX]

Thank you for fast response! Brightness is working, right? I was looking for that displayeffect denied, but now i have confirm is not the root issue.

Edit: No difference between the two, only revert some pwm commits

 

[TureX]

Hi!

New test emui brightess fix kernel is up! let me know if works or not on stock/lineageos 16 the brightness.

Edit: tested on emui 9.1.0.132 and seems working well. I need some other test (other emui version, lineageos 16 and gsi). Let me know if someone test, thanks

Cheers

 

[hopeless_bricker]

Hi!

New test emui brightess fix kernel is up! let me know if works or not on stock/lineageos 16 the brightness.

Edit: tested on emui 9.1.0.132 and seems working well. I need some other test (other emui version, lineageos 16 and gsi). Let me know if someone test, thanks

Cheers

Hey TureX, I've just flashed it. I'm on ANE-LX1 running eremitein's CAOSR11 GSI. Auto Brightness has always worked for me and continues to do so.


I do have an issue with soft reboots and storage, I'm not sure it's to do with the kernel. Every now and then the phone does a soft reboot (CAOS logo, then 'Phone is starting'...) and afterwards primary storage is unavailable for a time. Then it either does another soft reboot and storage comes back or I have to reboot it fully to get storage access again. It happens during normal usage/idle sometimes but it is guaranteed to happen if the phone is charging.

I've attached some logs and dmesg from sessions where the bug has happened, if you have some ideas. I do have magisk and LSPosed but I've replicated this with both disabled. I'll try and flash the stock kernel when I have the chance to find my backup, to see if it's kernel related.

I really like your kernel, TureX. Thank you.

 

[Frax3r]

Hi, I encountered flickering today. Around 14:00-16:00. I was taking an online class (on Chrome 94.0.460671) and I got bored. So I used split screen and put twitter on lower half of screen. It continued flickering for like 3-4 seconds right after I selected twitter as second application. I was able to pull logs just recently so I removed recent entries from logcat in order to shorten it a little. I also tried to reproduce the effect without success. Let me know if you need anything else
I pulled dmesg and lshal accordingly as you said here. However I used adb -d logcat *:E -v long > logcat.txt for logcat.txt and adb logcat -b all > log.txt for log.txt .
Edit: I can't upload dmesg here so here's the link.
Edit2: I realised dmesg don't go back enough so it's useless.

 

[TureX]

Hi, I encountered flickering today. Around 14:00-16:00. I was taking an online class (on Chrome 94.0.460671) and I got bored. So I used split screen and put twitter on lower half of screen. It continued flickering for like 3-4 seconds right after I selected twitter as second application. I was able to pull logs just recently so I removed recent entries from logcat in order to shorten it a little. I also tried to reproduce the effect without success. Let me know if you need anything else
I pulled dmesg and lshal accordingly as you said here. However I used adb -d logcat *:E -v long > logcat.txt for logcat.txt and adb logcat -b all > log.txt for log.txt .
Edit: I can't upload dmesg here so here's the link.
Edit2: I realised dmesg don't go back enough so it's useless.

HI!

Did you tried last test kernel? I will take a look to the log as soon as possible, thanks for the feedback!

Cheers

 

[Frax3r]

HI!

Did you tried last test kernel? I will take a look to the log as soon as possible, thanks for the feedback!

Cheers

Nah, I didn't. I still have the one you bundled with your los build. However I have good news. Phh released an alpha build for android 12 (its in his telegram) and I booted it with your kernel. Not that I actually wanted to but I kinda forgot I had your kernel xd. I have logcat, lshal and dmesg from a12, I can upload them too if you want. Right after I get logs I returned back to los 16 so I can't experiment. Most stuff is broken and it's not daily drivable as of right now. Camera hal1 support is gone and bluetooth is dead for example. As for the flickering, a12's systemui is a little janky which makes it harder to distinguish if kernel was the cause or the systemui itself. I'd wait for a stable release before troubleshooting. In my los 16 installation I don't see regular flickering but I'll try to get dmesg right after I see it. Cheers.

 

[TureX]

Hey TureX, I've just flashed it. I'm on ANE-LX1 running eremitein's CAOSR11 GSI. Auto Brightness has always worked for me and continues to do so.


I do have an issue with soft reboots and storage, I'm not sure it's to do with the kernel. Every now and then the phone does a soft reboot (CAOS logo, then 'Phone is starting'...) and afterwards primary storage is unavailable for a time. Then it either does another soft reboot and storage comes back or I have to reboot it fully to get storage access again. It happens during normal usage/idle sometimes but it is guaranteed to happen if the phone is charging.

I've attached some logs and dmesg from sessions where the bug has happened, if you have some ideas. I do have magisk and LSPosed but I've replicated this with both disabled. I'll try and flash the stock kernel when I have the chance to find my backup, to see if it's kernel related.

I really like your kernel, TureX. Thank you.

Hi!

i was on Caos for a while and i never had soft reboot nor storage problems. Try a clean flash without magisk/LSPosed or first try with stock kernel. Let me know!

Cheers

Hi, I encountered flickering today. Around 14:00-16:00. I was taking an online class (on Chrome 94.0.460671) and I got bored. So I used split screen and put twitter on lower half of screen. It continued flickering for like 3-4 seconds right after I selected twitter as second application. I was able to pull logs just recently so I removed recent entries from logcat in order to shorten it a little. I also tried to reproduce the effect without success. Let me know if you need anything else
I pulled dmesg and lshal accordingly as you said here. However I used adb -d logcat *:E -v long > logcat.txt for logcat.txt and adb logcat -b all > log.txt for log.txt .
Edit: I can't upload dmesg here so here's the link.
Edit2: I realised dmesg don't go back enough so it's useless.

Hi!

try to flash latest test kernel and let me know.

Cheers

 

[TristanL]

Hi!

New test emui brightess fix kernel is up! let me know if works or not on stock/lineageos 16 the brightness.

Edit: tested on emui 9.1.0.132 and seems working well. I need some other test (other emui version, lineageos 16 and gsi). Let me know if someone test, thanks

Cheers

Hi, thanks for your work, still the same problem but I notice some changes:
In NewPipe it occurs when I see comments, and a tinny part of the screen does not flicker (half of status bar something like 30pixels). When I go back to the top of the page of new pipe (with the video), I stops flickering, thus It seems to be viewport and app related, not complete system (otherwise the status bar flick again).

Occurs on LOS16 official with your latest kernel. Magisk and LSPosed installed.
I attached logcat, dmesg and lshal logs

Edit1: The screen flicker like 2-4 times per second when it appends
Edit2: It occurs when the video is "Paused" and when I see comments in NewPipe, If I press "return" in NavBar, the player stops (no video is loading in background), and screen stop to flicker. Also when I touch the screen, it does not flicker
Edit3: I forgot to ention the I flash it with twrp from erecovery

 

[TureX]

Hi, thanks for your work, still the same problem but I notice some changes:
In NewPipe it occurs when I see comments, and a tinny part of the screen does not flicker (half of status bar something like 30pixels). When I go back to the top of the page of new pipe (with the video), I stops flickering, thus It seems to be viewport and app related, not complete system (otherwise the status bar flick again).

Occurs on LOS16 official with your latest kernel. Magisk and LSPosed installed.
I attached logcat, dmesg and lshal logs

Edit1: The screen flicker like 2-4 times per second when it appends
Edit2: It occurs when the video is "Paused" and when I see comments in NewPipe, If I press "return" in NavBar, the player stops (no video is loading in background), and screen stop to flicker. Also when I touch the screen, it does not flicker
Edit3: I forgot to ention the I flash it with twrp from erecovery

Hi!

What have you install with Magisk and LSPosed? I tried newpipe and i haven't prolems.

However the problem now seems "changed" according to dmesg spam

Cheers

 

[TristanL]

Hi!

What have you install with Magisk and LSPosed? I tried newpipe and i haven't prolems.

However the problem now seems "changed" according to dmesg spam

Cheers

Hi, yes Magisk and LSPosed are installed, noGapps (MicroG instead)

 

[TureX]

Hi, yes Magisk and LSPosed are installed, noGapps (MicroG instead)

no modules ecc? on magisk and lspoded

 

[TristanL]

no modules ecc? on magisk and lspoded

ecc?
Here are my majisk modules:
- AuroraServices
- Busybox
- F-Droid privileged Ext
- MicroG Installer Revived
- Riru
- Riru-LSPosed
- SQLIte
- Systemless Hosts
- Webview Manager
All up-to-date

And in LSPosed only FakeGapps is used

 

[TureX]

Hi!

I find a way to reproduce the issue, can some one install "Terminal Emulator for Android" by Jack Palevich and send me a logcat and a dmesg? At this point i guess if issue is in gsi too.
Thanks in advance

Cheers

 

[TristanL]

Hi!

I find a way to reproduce the issue, can some one install "Terminal Emulator for Android" by Jack Palevich and send me a logcat and a dmesg? At this point i guess if issue is in gsi too.
Thanks in advance

Cheers

Hi!
I can do that tomorrow if you send me the steps to reproduce. i actually use the Terminal provided by LOS. Does the Terminal Emulator by Jack Palevich flicker the screen?
Cheers