Expert Mode not enabled when SystemBridge is started externally (adb / root)

[binhmod]

Have you checked if an issue already exists for this bug?

• Nobody else has reported this bug before

Have you tried restarting your device?

• I have tried restarting my device and that did not help

What happened that you did not expect?

When SystemBridge is started externally (outside the app UI), Expert Mode is not enabled in the app even though the service is running successfully.
For example, running the following command starts SystemBridge without errors:
`sh /data/user_de/0/io.github.sds100.keymapper/start.sh

`
However, returning to the app, Expert Mode still appears as disabled / stopped, and the UI does not transition to the “Started” state.
Expected behavior
If SystemBridge is already running, the app should detect it and enable Expert Mode automatically.
The Expert Mode UI should reflect the actual running state regardless of how SystemBridge was started.
Actual behavior
SystemBridge starts successfully via shell.
No error is reported.
Expert Mode remains disabled in the app UI.
Root cause (likely) Expert Mode state seems to depend on in-app start flows and connection callbacks.
When SystemBridge is launched externally, there is no explicit signal back to the app that the service is already running.

What did you expect to happen?

ExpertMode will enable.

What would the developer need to do to reproduce the bug?

1. Detect running SystemBridge on app resume / screen entry (e.g. binder availability, process check, or explicit broadcast).
2. Treat external starts the same as in-app starts.
3. Ensure loading / starting state is reset when SystemBridge is already active.

App version

4.0.0-beta.06-foss 227

Android version

Android 10

Device model and manufacturer

Samsung Galaxy

Extra info

• My device is rooted

[sds100]

It looks like the system bridge is crashing/dying after the shell command returns which is why it isn't connecting. Can you send the key mapper log at the bottom of Key Mapper settings?