Skip to main content

​
Hardware

Use Rokid Glasses with the development cable when you need direct ADB installs, log access, or debugging. Non-cable APK upload workflows can be useful for simple installs, but the cable is the preferred development path. For device and cable sourcing details, see How to get Rokid Glasses.

​
Device Wi-Fi

If the device is connected by cable but Wi-Fi is disabled, enable Wi-Fi and join a network through ADB:
After the device is reachable on the same network as the development machine, you can switch to wireless ADB:

​
Common commands

  • ./gradlew :app:build: build the app module and produce APKs.
  • adb install -r app/build/outputs/apk/debug/app-debug.apk: install the debug APK.
  • adb shell am start -n com.example.example/.MainActivity: launch an installed app.
  • adb logcat -c && adb logcat -v time: clear and stream the full device log.
  • adb logcat -v time --pid "$(adb shell pidof -s com.example.example)": stream only the app logs once the app is running.
  • emulator ...: launch an Android emulator when one is available.

​
Runtime permissions

Physical Rokid Glasses do not show an interactive Android permission dialog in the HUD; runtime permission requests on-device behave as accepted, but keep normal permission request code for phone and emulator testing.

​
Phone and emulator

You can test most app flows on an Android phone or emulator for convenience, but confirm final behavior on physical Rokid Glasses. This is especially important for the camera and microphone, which are often unstable in the emulator. If you decide to use an Android phone or emulator, refer to the Rokid Hello World starter for a viewport wrapper and touchpad navigation mapping with touchscreen controls.

​
Emulator setup