Not working on Samsung Android 16, OneUi 8.5

[ar5to]

[ 2026-06-17T17:56:28.751 10348: 31798: 31798 I/LSPosedFramework ] (com.google.android.inputmethod.latin)[com.keyflux,XposedBridge,7c36-19ed6156c4e-2-3,0,1] xposed-KeyFlux-hook-Failed to hook Application#attachBaseContext: android.app.Application#attachBaseContext[class android.content.Context]#exact

[NawafCode]

I have pushed a fix to target android.content.ContextWrapper instead, which safely resolves this compatibility issue on Samsung Android 16 devices without breaking other versions.

I will be releasing a hotfix update ( v1.0.1 ) shortly that includes this fix. Please test it once it's out and let me know if it resolves the issue for you!

[ar5to]

Thank you for trying to fix it, but it still doesn’t work.
I’m getting these errors:

[2026-06-18T01:48:57.731 I/LSPosedFramework] (com.google.android.inputmethod.latin)[com.keyflux,XposedBridge] xposed-KeyFlux-hook-getPreferenceScreen unobfuscated failed: NoSuchMethodError, trying obfuscated

[2026-06-18T01:48:57.732 I/LSPosedFramework] (com.google.android.inputmethod.latin)[com.keyflux,XposedBridge] xposed-KeyFlux-hook-getContext unobfuscated failed: NoSuchMethodError, trying obfuscated

[2026-06-18T01:48:54.611 I/LSPosedFramework] (com.google.android.inputmethod.latin)[com.keyflux,XposedBridge] Failed to hook android.support.v7.preference.PreferenceFragmentCompat: ClassNotFoundException

[ar5to]

Device: Samsung Galaxy A54
Android Version: 16
One UI Version: 8.5
Kernel: KernelSU Next
LSPosed: Internal Test 2.1.0-it (7774), API 102
Target App: Gboard 17.5.7.917159154-release-arm64-v8a

[NawafCode]

Thanks for the detailed logs!
I have just released v1.0.2 which includes a completely rewritten preference hooking engine that should bypass
Gboard's obfuscation and work perfectly on Samsung OneUI 8 (Android 16).
Please download the new v1.0.2 update from the releases, Force Stop Gboard, and let me know if it resolves the issue for you!

[ar5to]

LSPosed_20260618_080422.zip
Still same.

[NawafCode]

Thanks for testing and for the additional logs.

It looks like v1.0.2 did not fully resolve the issue on your setup. The original Application#attachBaseContext problem appears to be only one part of the failure; your newer logs also show preference-hook compatibility issues with Gboard 17.5 on Samsung One UI 8.5 / Android 16.

I have prepared a new build, v1.0.3, with a safer initialization path, fallback hook handling, and once-per-process initialization protection.

Could you please try v1.0.3 with these steps?

1. Uninstall the old KeyFlux version.
2. Install KeyFlux v1.0.3.
3. Enable the module for Gboard only.
4. Force stop Gboard.
5. Reboot the device.
6. Open Gboard settings again.
7. Send a fresh LSPosed/Vector log if it still fails.

Please also confirm that LSPosed shows KeyFlux as v1.0.3 after installing it.

I will keep this issue open until we confirm whether the new build fixes the Samsung One UI 8.5 / Gboard 17.5 compatibility problem.

[ar5to]

I followed all the suggested steps, but unfortunately it's still not working.
I'm not sure whether this issue is specific to my device or affects all devices running One UI 8.5.
I also tested the module on another phone running One UI 8, and it worked correctly there. However, I noticed that the Gboard UI on that device looks different from the Gboard UI on my main phone running One UI 8.5.
This makes me wonder if the module might not be compatible with the newer Gboard UI introduced on One UI 8.5, but I'm not sure.

[NawafCode]

Thanks. I prepared a new diagnostic build: v1.0.4-diagnostic.

This is not marked as fixed yet. The purpose of this build is to compare your Samsung One UI 8.5 setup against a working device and identify exactly where the hook path differs.

https://github.com/NawafCode/KeyFlux/releases/download/v1.0.4-diagnostic/KeyFlux-v1.0.4-diagnostic.apk

Please install the diagnostic APK, enable KeyFlux only for Gboard, force stop Gboard, reboot, then open Gboard settings.

After that, please send:

1. LSPosed logs filtered by:

xposed-KeyFlux-hook-

2. Your exact Gboard package information:

adb shell dumpsys package com.google.android.inputmethod.latin | grep -E "versionName|versionCode|versionCodeMajor|firstInstallTime|lastUpdateTime"
adb shell pm path com.google.android.inputmethod.latin

3. Device information:

adb shell getprop ro.product.manufacturer
adb shell getprop ro.product.model
adb shell getprop ro.build.version.sdk
adb shell getprop ro.build.version.release
adb shell getprop ro.build.version.incremental

If you do not have a PC, you can optionally use aShell You with Shizuku, root, or Wireless Debugging to run the same commands directly on your phone.

In aShell You, run the commands without the adb shell prefix:

dumpsys package com.google.android.inputmethod.latin | grep -E "versionName|versionCode|versionCodeMajor|firstInstallTime|lastUpdateTime"
pm path com.google.android.inputmethod.latin
getprop ro.product.manufacturer
getprop ro.product.model
getprop ro.build.version.sdk
getprop ro.build.version.release
getprop ro.build.version.incremental

If using ADB or aShell You is difficult, screenshots are also okay:

• LSPosed logs filtered by xposed-KeyFlux-hook-
• Gboard app info showing the exact version
• About phone / Software information showing Android version and One UI version
• LSPosed scope showing KeyFlux enabled only for Gboard

I’m specifically checking whether the diagnostic log shows:

PreferenceFragment class resolved and cached
PreferenceHooker.hook called
Found PreferenceFragment class
Hooked method

[ar5to]

I forget something to tell, I am currently using a ported S23 FE ROM, which may be influencing the behavior.

[ar5to]

[NawafCode]

@ar5to Thanks for your patience and for all the logs/screenshots you shared.

I have not marked this as fixed yet because I am working on a larger compatibility update for KeyFlux. The next build will focus heavily on improving compatibility across different Android versions, Gboard versions, Samsung/One UI builds, and other OEM devices.

This may take some time, because Gboard beta/stable builds and different ROMs can expose different obfuscated method mappings. I want the next version to be more reliable instead of just adding another temporary patch.

The new build will also include some additional improvements/features, but compatibility is the main priority right now.

I will reply here in this issue as soon as the next build is ready for testing.

As a side note, I currently have Samsung S24 and S25 Ultra devices, but I have not updated them to One UI 8.5 because I rely on bootloader/root development and do not want to risk losing root or bootloader unlock compatibility. My main testing device right now is Xiaomi 17, which has been more flexible for this kind of Android development and testing.

[ar5to]

Thanks for the detailed update and for working on the compatibility improvements.
Take your time with the next build, no rush from my side. For now I’ll switch to another patch until the new version is ready for testing.
I appreciate the effort you’re putting into making it more stable across different devices and ROMs.