Samsung S22U (Snapdragon) Proximity Sensor not working

[sha3rawi33]

Please check before submitting an issue

• [x] I have searched the issues and haven't found anything relevant
• [x] I will upload bugreport file in KernelSU Manager - Settings - Report log
• [ ] I know how to reproduce the issue which may not be specific to my device

Describe the bug

Installing the GKI ready image from github releases are causing the proximity sensors not to work properly in calls.

To Reproduce

Just flashing boot.img from github releases

Expected behavior

should work properly

Screenshots

NA

Logs

No response

Device info

• Device: Samsung Galaxy S22 Ultra (Snapdragon)
• OS Version: Android 14, and 15 after updating today
• KernelSU Version: latest (1.0.5)
• Kernel Version: 5.10

Additional context

also when taking camera pics with phone rotated, it is saved as if phone was not rotated which makes the image itself rotated. like, when flipping your phone and taking pictures, it should save as if it was normally posed, but when GKI is installed; it is saved as if the world was flipped

btw, I used to install boot.img files from someone on XDA who built the original phone Kernel with KSU, there was no issue with it. I think issue is related only to GKI as it is not phone specific or am I missing something?

[rsuntk]

You must use GKI source from Samsung

[sha3rawi33]

@rsuntk

You must use GKI source from Samsung

I requested latest android 15 sources from Samsung and they uploaded it, I downloaded it, then followed the instructions to build the kernel in the Readme.md they added with the sources and then I executed the KSU command to modify drivers with KSU

however, when I build the kernel with KSU, and then flash the outcome's boot.img I'm stuck on the boot screen with the knox warning of the non-official software warning.

when I read further; I think it is related to some missing prebuilt defconfigs and abi_symbollist.raw that I needed to add, then I have to disable knox from the config. here is a reference of someone who built the kernel for my device with KSU : https://github.com/russel5/android_kernel_samsung_sm8450/commits/EXE4/

btw I saw your GH account and you are already building kernel for a Samsung device, can you help me with this? I noticed tiann mentioned that Samsung are using private symobls that needs to be customly added while building. can you help me with this?

like, how can I reproduce same commits that guy is doing on his repo? btw I asked him for help but still no answer. It would be much appreciated if you could help me.

[hhihhio]

I don't know how kernelsu works. but if root is provided directly by the kernel and a special app can manage root like a system app then root is basically undetectable, what needs to be done is to remove or prevent android, google malware spying system, which is intelligence for 3rd party apps. no vulnerabilities and the "cleanest" root possible, with other apps they are required to not able collect fingerprints or system status. with root the phone will be able to execute customizations like linux or windows on a computer. it's annoying if the user wants to use a feature but is blocked by his own phone: access denied, because you're just "guest", not root (owner of all system)

[hhihhio]

it is the mechanism of samsung root restriction or built in qualcomm kernel inside the bootloader, when it detects the device is rooted. this has happened on some devices. it is possible to remove direct interaction by the main kernel in boot.img or edit the code in the main kernel so that it affects the secondary kernel and prevents sensors and some functions from working. i don't know commit the kernel code to do this because the reference i know is deleted

[tiann]

https://github.com/tiann/KernelSU/issues/2291#issuecomment-2561867374 https://github.com/tiann/KernelSU/issues/263#issuecomment-1437963812