Set up MotoEye Remote with your E6 HUD
Five minutes from install to riding. You need an Android phone running Android 8.0 or later and a MotoEye E6 HUD.
1. Install the app
Download the latest motoeye-x.y.z-release.apk from GitHub Releases and open it on your phone. Android will ask you to allow installs from your browser or file manager the first time. A Google Play listing is coming; once it is live, Play updates the app for you.
Moving from an early APK? Versions before 1.1 used a
different app ID (com.motoeye.remote). The current app
installs alongside it — uninstall the old one and set up again.
2. Connect to the HUD
- Power on the HUD and make sure it is not connected to another phone running MotoEye Remote.
- Open MotoEye Remote and tap Scan for devices. Allow Nearby devices when asked.
- Pick your HUD from the list and accept the Bluetooth pairing prompt. The status turns green: Connected.
- Wait a few seconds for CAM and REC. The camera buttons light up once the keyboard channel attaches (default delay 5 s, adjustable under Settings → Advanced).
From then on the app reconnects to that HUD automatically when you open it, and after the HUD drops out or is switched off and on again.
3. Permissions, and what each one is for
Only Nearby devices is required. Everything else switches on an optional feature, and the app works without it.
| Permission | Why | Needed? |
|---|---|---|
| Nearby devices (Bluetooth) | Find and connect to the HUD and read the TPMS tyre sensors. | Yes |
| Location (Android 11 and older only) | Older Android versions require it for any Bluetooth scan. The app never reads your location. | Android 8–11 |
| Notifications | The “connected” notification with Camera and BACK actions, which also keeps the link alive in the background. | Recommended |
| Ignore battery optimisation | Stops Android putting the app to sleep mid-ride, so reconnects still work with the screen off. | Recommended |
| Notification access | Finds which app is playing media so Play, Previous and Next control it. | For media keys |
| Accessibility: “Android Auto / Exit AA” | Performs the Home action for the Exit AA button. It cannot read screen content. | For Exit AA |
| Accessibility: “Lock screen pad” | Draws the D-pad, camera and BACK buttons above the lock screen. It cannot read screen content. | For lock-screen pad |
About the accessibility services. Android only lets an app draw over the lock screen or press Home through an accessibility service. Both MotoEye Remote services are configured with window-content retrieval switched off, ignore every accessibility event, and collect nothing. You turn each on separately from Settings → Permissions & Services, and you can turn them off at any time in Android's accessibility settings.
4. Set up the extras
- Tyre pressure (TPMS). MotoEye TPMS sensors sleep when idle and transmit on motion or a pressure change. Roll the wheel and the readout (pressure, temperature, sensor battery) appears on the remote. Readings older than 30 minutes are dropped.
- Recording. Turn on Show record button to add REC. A long press toggles background DVR recording on the HUD; the HUD doesn't report its state, so the button label follows your presses.
- Macros. Settings → Macros → New macro. Add keys in order, with a hold time and a delay after each one, then run it from the macro button on the remote.
- Lock-screen pad. Turn on Lock screen controls and enable the Lock screen pad accessibility service.
- Voice. Turn on Long-press OK for voice to start Google Assistant from the D-pad, or add Assistant shortcuts under Voice commands.
5. Ride
Mount the phone where you can reach it without stretching. Turn on Keep awake if you want the screen on the whole ride, or lock the phone and use the lock-screen pad. Use the remote only when it is safe and legal where you ride.
Troubleshooting
The HUD doesn't show up when I scan
Check that Bluetooth and Nearby devices are allowed, then power-cycle the HUD and scan again straight away. If another phone is connected to the HUD as a remote, close MotoEye Remote there first.
CAM and REC stay grey after connecting
They need the second (keyboard) channel. Wait for the startup delay, or raise it under Settings → Advanced → Camera channel startup delay if the link drops when the channel attaches.
The app disconnects with the screen off
Allow Ignore battery optimisation and keep the notification enabled. Some phones (Samsung, Xiaomi) also need the app set to “Unrestricted” battery use.
No tyre pressure is shown
The sensors only broadcast while the wheel moves or shortly after. Ride a few metres and the reading appears.
Still stuck? Open an issue on GitHub.