-
-
Notifications
You must be signed in to change notification settings - Fork 160
Troubleshooting
If you encounter issues while using HeadUnit Revived, try the solutions below.
The connection is established (audio works), but the screen remains black.
- Cause: Your device's hardware video decoder might be incompatible or failing to initialize correctly.
- Solution 1: Enable Force Software Decoding in Settings -> Video.
- Solution 2: Try changing the Video Codec setting from "Auto" to "H.264".
A solid green screen appears, or the video stream displays green artifacts, glitches, and heavy pixelation.
- Cause: Many Android head units or older hardware video decoders cannot properly process H.265 / HEVC streams.
- Solution 1 (Recommended): Change the Video Codec in Settings -> Video from "Auto" or "H.265 (HEVC)" to H.264.
- Solution 2: Change the View Mode in Settings -> Graphic to GLES20 or TextureView.
- Solution 3: Enable Force Software Decoding in Settings -> Video.
- Solution 4: Lower the Resolution in Settings -> Graphic (e.g., to 720p or 480p).
- Design Choice: This is a built-in battery-saving feature of Android Auto. When you are not actively interacting with the display (e.g., while just viewing the map or driving without touching the screen), Android Auto drops the frame rate to 30 FPS to reduce power usage and heat. It automatically ramps up to 60 FPS as soon as you tap the screen, pan the map, or interact with any UI elements.
- Improvement in 1.12.0: We implemented a new handshake logic with Socket Reuse. This should eliminate most "Broken Pipe" errors during startup.
- Solution: Ensure Battery Optimizations are disabled for both HeadUnit Revived (Tablet) and Wireless Helper (Phone).
- Note: If you are using a Phone Hotspot (10.x.x.x networks), manual connection (Port 5277) often fails due to phone-side routing bugs.
- Solution: Switch to Wireless Mode: Helper Mode in the tablet settings and use the Wireless Helper app on your phone.
If your wireless connection is established but drops after a few seconds or minutes, it is likely caused by a battery-saving or "smart" network feature on your phone.
- Cause: Modern phones have features like "WiFi Assistant," "Switch to mobile data," or "Network acceleration." Since the WiFi network created by your headunit (or the hotspot) often doesn't provide internet access, the phone OS might decide to kill the WiFi connection to "help" you stay online.
-
Solution: Go to your phone's WiFi Settings -> Advanced/Additional Settings and disable features like:
- "Switch between networks"
- "WiFi Assistant"
- "Network acceleration"
- "Avoid poor connections"
The video is projected, but the music plays through the phone speakers.
-
Improvement in 1.14.1: We implemented
MediaSessionsupport and proactive audio focus requests. This ensures that HURev has higher priority and prevents other apps on the tablet from blocking the audio stream. - Solution 1: In Headunit Revived Settings, try toggling Use AAC Audio (OFF is usually more stable).
- Solution 2: Clear any other music or radio apps from the background on your tablet/headunit device.
- Solution 3: Check your music app (e.g., Spotify) on the phone. Ensure the output device is set to "This Phone" or "Android Auto" and not redirected to another Bluetooth device.
- Solution 4: Ensure Enable Audio Sink is turned ON in Settings.
- Solution: Enable Use Native SSL in Settings -> Debug. This is significantly faster on older devices. Version 1.12.0 now uses 16KB page-aligned libraries for maximum compatibility.
- Cause: This is a known issue in Android Auto when connected via USB (or wireless) while simultaneously paired to the car/headunit via Bluetooth. Bluetooth Media audio conflicts with Android Auto's audio stream, causing playback to repeatedly pause.
- Solution: On your phone, go to Settings -> Bluetooth, tap the settings (gear icon) next to your car/headunit connection, and disable "Media audio" / "Media Playback" (you can leave "Phone calls" enabled).
- Reference: This is an Android Auto bug acknowledged in the Google Support Community.
- Solution: Try changing the DPI in Settings -> Graphic. Setting it to 0 (Auto) usually works best.
Google has disabled the automatic wireless projection startup for Android 10 and below in Android Auto versions 16.4 and higher. While Self-mode still works on newer Android versions, it is normally impossible to trigger projection on Android 10 and below directly.
You can bypass this restriction by starting the built-in Android Auto Headunit Server on your phone and connecting via Wi-Fi mode in Headunit Revived.
Step 1: Enable Android Auto Developer Options The standard Android Auto menu hides the advanced tools we need. To unlock them:
- Open your phone's Settings → Connected devices → Android Auto (or search for "Android Auto" in your Settings app).
- Scroll all the way to the bottom to find the Version stub.
- Tap the "Version and permission info" section rapidly 10 times. A pop-up will appear saying that Developer Settings are now enabled.
Step 2: Start the Headunit Server Now that the hidden menu is unlocked:
- While still in the Android Auto settings, tap the three dots in the top-right corner.
- Select Start head unit server from the dropdown menu.
- You will see a persistent notification in your status bar confirming that the Android Auto server is running in the background.
Step 3: Connecting via Wi-Fi Mode in Headunit Revived Instead of tapping Self-mode on the main screen, we will force the app to connect to the active server using a virtual Wi-Fi loopback connection:
- Configure Settings: Open Headunit Revived, go to Settings, and make sure your Wireless Mode is set to Headunit Server.
- Select Wi-Fi: Go back to the Headunit Revived main screen and tap the Wi-Fi button.
- Search for the Server: The app will start scanning the network (in this case, your phone's internal loopback address).
- Select Your Device: Your local Android Auto server will pop up in the available connections list. Tap on it, and the Android Auto dashboard will launch successfully!