Sideloading Third-Party Apps onto the Stock Honda Connect Head Unit
Introduction
The Android-based Honda Connect head unit fitted to the facelift 9th-generation Civic and its siblings (Jazz, HR-V, Civic Tourer) runs a locked-down build of Android 4.0.4 that normally refuses to install anything outside Honda's own app centre. This guide explains how to roll the unit back to a state that accepts sideloaded APKs, load your own applications from a USB drive, and grant each app the permissions it needs to run and produce sound while the car is moving. Typical goals are replacing the sluggish factory Garmin navigation with Google Maps, Waze, or Sygic, or adding a media or dash-cam app. The procedure applies only to the genuine Android Honda Connect unit; pre-facelift Honda/Alpine systems and aftermarket stereos such as Kenwood units cannot run APKs. Firmware revision matters: an unlocked RC6 unit sideloads freely, whereas RC7 and RC8 firmware greys out the install button and can only be opened up by rooting through the rear service port. Adapted from a community writeup by Haltamer on Civinfo (https://www.civinfo.com/threads/guide-to-installing-3rd-party-applications-stock-headunit.386674/), including corrections from the follow-up discussion.
Reference
Tools Required
- USB flash drive, 32 GB or smaller, formatted FAT32
- FileCommander file-manager APK (used to browse and launch installers on the unit)
- Windows PC or tablet to download APKs and format the USB drive
- Laptop plus USB cable (only if rooting an RC7/RC8 unit through the rear debug port)
Parts Required
-
Honda Permissions app (PERMISSIONS 1.1 S_Mike)
-
Desired application APK files (Google Maps, Waze, Sygic, media apps, etc.), preferably sourced from the CMdroid catalogue
Safety Warnings
- ⚠ The factory reset permanently erases all head unit data, including settings, trip history and saved navigation destinations. There is no undo.
- ⚠ Displaying video or other moving images within the driver's view while driving is illegal in the UK and many other jurisdictions.
- ⚠ Rooting an RC7/RC8 unit through the rear debug port carries a real risk of bricking the head unit. Proceed only if you accept that risk.
Step-by-Step Instructions
1 Confirm the unit is compatible and identify its firmware
This method only works on the genuine Android Honda Connect unit used from the 9th-gen Civic facelift onward (and shared with the Jazz, HR-V and Civic Tourer). Pre-facelift cars used a non-Android Honda/Alpine system, and aftermarket head units such as the Kenwood DMX7017DABS cannot sideload APKs at all. The unit runs Android 4.0.4, so only older, compatible app versions will install and launch. Firmware release level is the deciding factor: RC6 permits sideloading, while RC7 and RC8 block it and leave the install button greyed out. If your unit is already on RC7/RC8 and a factory reset does not restore installation, the only route is the separate rooting procedure through the debug port behind the screen. If needed, enter developer mode by holding power, menu and brightness together for two to three seconds.
2 Perform a factory reset to remove the install lockout
Later Honda software updates patch the unit to block custom app installation. A factory reset rolls the software back to a state that once again accepts APKs. From the head unit's Android settings, choose the option to reset to factory defaults. This is destructive: every stored preference, saved default, trip record and navigation entry on the unit is wiped and cannot be recovered, so note anything you need beforehand. The built-in factory Garmin navigation is not removed by the reset and will remain available afterwards.
3 Allow installation from unknown sources
After the unit restarts, return to the Android settings and open the Security section. Turn on the setting that permits apps from unknown or unrecognised sources. Without this enabled the unit will detect the APK on your USB drive but refuse to install it, so confirm it is switched on before continuing.
4 Prepare the USB drive with your APKs
Use a USB stick of 32 GB or less, formatted as FAT32; larger or differently formatted drives are frequently unreadable by the unit. Place the FileCommander APK in the root of the drive, and put each application you want to install in its own clearly named subfolder. The unit will only install a file named HondaAppCenter_A1.apk, so rename each installer to exactly that; because they share one filename, never keep two of them in the same folder. Always include the Honda Permissions app (PERMISSIONS 1.1 S_Mike). Sourcing APKs from the CMdroid catalogue is safest, as those builds are known to run on the unit's old Android version. To confirm the drive is being read correctly, drop a music file into a subfolder first: if the unit plays it, it will also see your APKs.
5 Install each application from the drive
Insert the USB stick and open FileCommander on the unit. Browse to the folder for the app you want, then use the Install option in the second-level menu to run the installer. Work through your apps one folder at a time, which avoids the download-and-delete shuffle of installing them individually over the air. Install the Honda Permissions app first, since you will need it to make the other apps usable on the move. If the install button appears greyed out and double-beeps when pressed, the unit is on RC7/RC8 or an updated RC6 and must be reset again or rooted before it will accept installs.
6 Register each app in the Honda Permissions app
Open the Honda Permissions app and select application permissions at the top left, then use the plus button at the top right to create a new permission set. Enter the app's process name and package name; for these units the two values are identical, so the same string goes in both fields (for example, use com.waze for both when setting up Waze). Type the name exactly, with no leading or trailing spaces, as an incorrect or too-short entry is rejected. Assign the audio permissions the app needs, then save. Repeat this for every app that must run while driving, and verify each one the next time the car is in motion.
7 Choose the correct audio permission for each app
Three audio permissions control how an app shares the speakers. Soundout gives the app exclusive output: opening it silences other sources such as DAB radio or USB media, which suits a music or media app. SoundInterrupt lets the app play short notifications without seizing the audio, so your existing music keeps playing and prompts come only through the driver-side speaker; this is the right choice for turn and speed-camera alerts from a navigation app. SoundInterruptMute works alongside SoundInterrupt and additionally mutes the driver-side speaker while the prompt plays, which is best for a voice-guided navigation app. Note that Google Maps and Waze route their guidance through the navigation sound setting rather than the normal media audio channel.
Pro Tips
- 💡 Google Maps navigation no longer works on Android 4.0.x: Google dropped Play Services support for Android 4.0 Ice Cream Sandwich in December 2018, so route guidance quits on launch. Waze 3.9.9 still functions as an alternative.
- 💡 Do not run the Honda App Center update after setting everything up. The update re-applies the lockout and removes your apps, and the only way back is another factory reset.
- 💡 If installs from USB keep failing, put a music file in a subfolder to prove the drive is readable; many failures trace back to a non-FAT32 or oversized stick.
- 💡 When registering an app in the permissions tool, use the same identifier for both the process and package fields, and double-check for stray spaces if it is rejected as too short.
- 💡 The factory Garmin navigation survives the reset, so you are adding apps alongside it rather than replacing it.
Was this guide helpful?