[kirtan05]

Problem

On a fresh install with Shizuku running, the app never gets Shizuku access. The main screen shows "Shizuku Access Denied", and tapping Retry only makes the card flash; the Shizuku permission dialog never opens.

Nothing in the app calls Shizuku.requestPermission(). SHIZUKU_PERMISSION_REQUEST_ID is declared in ShizukuNetworkControlDataSource but never used. Retry only re-runs checkCompatibility(), so the state goes Pending → PermissionDenied again, which is the "blink" reported in #36. It is not specific to One UI: I reproduced it on a Pixel 8 with stock Android 17.

Fixes #36

Change

• NetworkControlDataSource.requestPermission(): the Shizuku version shows Shizuku's dialog and suspends until OnRequestPermissionResultListener answers. The listener is removed on every path (result, cancellation, exception). Binder errors count as "not granted" instead of crashing. If the user denied before (shouldShowRequestPermissionRationale()), it returns false, because Shizuku won't show the dialog again. The root version keeps the existing Utils.isRootGranted() check.
• NetworkControlRepository.requestPermission(method) and a RequestPermissionUseCase, following the existing layering.
• MainViewModel.retryCompatibilityCheck(): when the state is PermissionDenied(SHIZUKU), it asks for permission first and then re-checks. Extra taps while a request is open are ignored.
• SettingsViewModel.retryCompatibilityCheck(): same, but only when Shizuku is the selected method, so a root user isn't shown a Shizuku dialog.
• 3 tests in SettingsViewModelTest: requests when Shizuku is denied, doesn't request when root is selected, doesn't request when Shizuku is already compatible. ./gradlew test passes.

Testing

Pixel 8, Android 17 (CP3A.261005.005), Shizuku 13.7.0 (thedjchi fork, started over wireless debugging).

Before (v1.1.0)	After (this branch)

Before: three taps on Retry, and no activity starts:

10-25 21:51:00.474 ActivityTaskManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.supernova.networkswitch/.presentation.ui.activity.MainActivity}
10-25 21:51:00.633 ActivityTaskManager: Displayed com.supernova.networkswitch/.presentation.ui.activity.MainActivity for user 0: +167ms
10-25 21:51:04.068 adbd: adb shell: input tap 540 773
10-25 21:51:06.832 adbd: adb shell: input tap 540 773
10-25 21:51:09.592 adbd: adb shell: input tap 540 773

After: one tap on Retry opens Shizuku's dialog. After "Allow all the time", the app shows "Device Compatible":

10-25 21:51:52.727 ActivityTaskManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.supernova.networkswitch.debug/com.supernova.networkswitch.presentation.ui.activity.MainActivity}
10-25 21:51:53.519 ActivityTaskManager: Displayed com.supernova.networkswitch.debug/com.supernova.networkswitch.presentation.ui.activity.MainActivity for user 0: +811ms
10-25 21:51:56.394 adbd: adb shell: input tap 540 773
10-25 21:51:56.598 ActivityTaskManager: START u0 {act=moe.shizuku.privileged.api.intent.action.REQUEST_PERMISSION flg=0x10080000 pkg=moe.shizuku.privileged.api cmp=moe.shizuku.privileged.api/moe.shizuku.manager.authorization.RequestPermissionActivity (has extras)}
10-25 21:51:56.682 ActivityTaskManager: Displayed moe.shizuku.privileged.api/moe.shizuku.manager.authorization.RequestPermissionActivity for user 0: +84ms
10-25 21:52:01.371 adbd: adb shell: input tap 540 1318

Notes

• If the app was denied in Shizuku earlier, Retry still can't show the dialog; the user has to allow the app in Shizuku's app list. The message could say so; I left that for a separate change.
• MainActivity.onResume also starts a compatibility check, and that can race with the one after Retry. This race existed before and I didn't change it here.
• feat: Upgrade to Material 3 Expressive, Permission Request Flow, Bottom Sheets & Edge-to-Edge, MaterialExpressiveTheme, enableOnBackInvokedCallback #15 also adds a permission request flow, but together with a large UI rework. This PR is only the fix.