Skip to content

JSOS v2.0.38 R08 Accessibility Recovery preview

Latest
Latest

Choose a tag to compare

View all tags
@IWhatsskill IWhatsskill released this 03 Aug 16:28
v2.0.38-r08-accessibility-recovery
45501e5

JSOS v2.0.38 R08 Accessibility Recovery

This preview fixes R08 ring control becoming unavailable when some Rokid firmware disables the JSOS Accessibility Service after a power cycle or app update.

Fixed

  • JSOS HUD can restore only its own R08 Accessibility component after an optional one-time ADB grant.
  • Recovery runs at HUD startup and also listens for boot, unlock, package replacement, and Bluetooth startup.
  • Existing Accessibility services are preserved; JSOS adds only its own component and verifies the write.
  • Without WRITE_SECURE_SETTINGS, recovery is a strict no-op and manual Accessibility setup remains unchanged.
  • The existing isolated :ring process, bounded GATT timeout, active-client callback filtering, and 3/5/8/12-second reconnect behavior remain intact.

Included apps

  • JSOS Core 2.0.12-security-hardening (versionCode 212)
  • JSOS HUD 2.0.36-r08-accessibility-recovery (versionCode 237)
  • JSOS Watch remains available as source and is not included as an APK asset.

Optional one-time setup

Grant the HUD permission once from a trusted computer:

adb shell pm grant com.jsos.glasses android.permission.WRITE_SECURE_SETTINGS

The grant normally survives reboots and in-place APK updates. If it is not granted, JSOS does not change Android Accessibility settings.

Verification

  • Core Debug unit tests: 27 passed, 0 failed.
  • Core Release unit tests: 27 passed, 0 failed.
  • Core and HUD release builds completed successfully.
  • Core and HUD lintVitalRelease completed with no issues.
  • APK package names, labels, versions, non-debuggable status, signatures, and the JSOS Preview certificate were verified.
  • Source and expanded-APK secret/private-marker scans passed; tracked public text files are BOM-free.
Assets 6
Loading