Shizuku 13.7.0 r1367 RazGame Beta - Android 17 startup fix

Fixes a Shizuku startup crash on recent Android 17 beta builds:

SecurityException: Permission denial, must have one of: [android.permission.MANAGE_DEBUGGING]

Android can now reject changes to ADB settings even when WRITE_SECURE_SETTINGS is granted. These optional settings writes no longer abort startup: Shizuku can discover and connect to an already enabled wireless debugging service.

The fix covers manual startup, wireless ADB discovery, background startup (including after unlocking), and connection cleanup. Successful settings writes on older Android builds retain their previous behavior.

Validation:

• Debug and release APKs built successfully.
• Installed and tested on a Google Pixel 9 Pro XL running Android 17, API 37, build DP11.261016.003.
• Startup from the app succeeded; shizuku_server remained running as shell, with no new Shizuku crash observed.
• The unit-test task reported NO-SOURCE; older Android versions and background startup were not tested on devices for this release.

Limitations:

• MANAGE_DEBUGGING is a system (signature|privileged) permission. This build does not grant it to Shizuku.
• Automatic enabling or disabling of debugging settings may be unavailable on affected Android builds. Enable USB/wireless debugging manually in Developer options when needed.
• Unofficial beta, signed with a development key.

Prepared with the help of OpenAI Codex.

shizuku-v13.7.0.r1366-razgame-beta-release

• Merge upstream thedjchi/Shizuku 13.7.0
• Fix false "USB debugging is not enabled" when starting on Android 17 (the system now always reports ADB_ENABLED as 0 to apps)
• Build against the Android 17 SDK (targetSdk 37)

shizuku-v13.6.1.r1320-razgame-beta-release

Fix Android 17 compatibility