-
Notifications
You must be signed in to change notification settings - Fork 0
Troubleshooting
Please read through this section before reporting a bug.
Please consult the setup guide for how to disable Android Auto.
Check the logs under [3 dot menu > Debug] for specific connection errors. There is no UI for it yet.
- Try importing official Android Auto keys and certificates.
- If you have expired Android Auto keys and certificates, try setting the date back on your headunit to before they expired.
- Try using the self-signed keys by disabling "Use imported keys".
- If you're using root mode, ensure you haven't denied Flywheel superuser access. Alternatively, try Shizuku mode.
If the above doesn't work, please report a bug.
Unfortunately, touch input doesn't work on Android 9 and below yet. This is a known limitation due to the way touch inputs are being injected by Flywheel.
- Try turning your screen on and/or unlocking your phone. Some versions of Android stop accepting touch inputs when the screen is off.
If the above doesn't work, please report a bug.
When on-screen notifications are tapped, they are supposed to be read aloud with the default text-to-speech engine configured on your device.
If you hear nothing, you may not have the default TTS engine configured correctly:
- The most common cause is not having any TTS engine installed at all, since Google's TTS engine is typically removed when de-Googling, leaving nothing.
- Another common cause is not having properly selected and set up the TTS engine in your device settings.
Personally, I still use eSpeak due to its simplicity, consistency, and reliability, but with a reasonably fast phone you can get significantly higher quality dictation from some of the other TTS engines on F-Droid.
After installing and possibly opening and configuring your app of choice:
- Go to [Settings > Accessibility > Text-to-speech output]
- Change the "Preferred engine" to the engine you want to use
- Use the "Play" button to make sure it works (you may have to exit and re-open the Text-to-speech output settings first).
If your issue wasn't mentioned here or the advice didn't work, please submit a bug report.