The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Most Android Auto emulator failures come from using the wrong tool or troubleshooting the wrong connection. Google’s Desktop Head Unit (DHU) runs on a Windows, macOS, or Linux computer and emulates the car display while a real Android phone supplies Android Auto. An Android Virtual Device (AVD) is a separate phone emulator, and a real vehicle has its own cable and infotainment requirements. Identify which setup you have before changing drivers, ports, or app settings.
Identify the Android Auto emulator you are actually using
Android Developers describes the Desktop Head Unit as a tool that lets a development machine emulate an Android Auto head unit for testing Android Auto apps. The DHU is not an emulated Android phone: it communicates with a physical phone over USB. The official instructions are in Android Developers’ Desktop Head Unit documentation.
| What you have | What it emulates | Typical connection | Use this troubleshooting path |
|---|---|---|---|
| Desktop Head Unit (DHU) | A car head-unit display on your computer | Development computer to a physical Android phone over USB | Install the DHU package, prepare the phone, then use Accessory Mode or ADB tunneling |
| Android Virtual Device (AVD) | An Android phone or tablet inside Android Studio | Virtual device running on the computer | Follow Android Emulator troubleshooting for boot, graphics, performance, and network problems |
| Real car display | Your vehicle’s infotainment system | Physical phone-to-car USB connection, or a supported wireless setup | Check cable quality, vehicle compatibility, infotainment settings, and receiver firmware |
If your error says that an AVD will not boot, renders a black screen, runs slowly, or cannot reach the network, DHU USB commands will not help. Use the relevant sections of Android Emulator troubleshooting, which covers issues such as ChromeOS libnss3, GPU and Vulkan failures, slow operation, and network or DNS problems.
Use the failure symptom to choose the right fix
- The DHU executable is missing: the Android Auto Desktop Head Unit Emulator package is not installed in the SDK.
- Linux reports a missing library or GLIBC error: the host operating system does not meet DHU 2.x runtime requirements.
- The DHU starts but cannot find a phone: investigate USB mode, Windows drivers, ADB state, and phone permissions.
- ADB tunneling connects but shows no Android Auto session: check the head unit server, the Add new cars setting, USB forwarding, screen unlock, and first-run approvals.
- Android Auto fails only in a physical vehicle: follow the separate vehicle and cable procedure rather than changing DHU files.
Install the official Desktop Head Unit package
Download it from Android Studio
- Open Android Studio on the development computer.
- Open the SDK Manager. In Android Studio, this is available from the SDK management entry in the application’s settings or tools menu; the exact menu location varies by operating system and Android Studio release.
- Select the SDK Tools tab.
- Select Android Auto Desktop Head Unit Emulator and apply the installation.
- After installation, look under
SDK_LOCATION/extras/google/auto/. The DHU executable and its supporting files should be in this directory.
If the package does not appear, verify that Android Studio is using the SDK location you expect. A common mistake is checking a different SDK directory than the one shown in Android Studio’s SDK settings.
#1 Best Overall
- Never Let a Dead Battery Ruin Your Drive. The LISEN 4 in 1 Retractable Car Charger delivers reliable power for your entire journey. Compatible with standard 12V cigarette lighter sockets, it keeps phones, tablets, and devices charged during daily commutes, road trips, and long drives — the perfect practical gift for dads, truck drivers, and anyone who lives on the road.
- Daily Driver Essential: Always Ready When You Need It. Featuring two retractable cables ( USB C & Old iPhone Charging Cable ) that extend up to 31.5 inches and dual USB ports, this charger solves cable clutter while charging up to 4 devices simultaneously. Ideal for busy fathers, commuters, and families who want a tidy car and never worry about low battery again.
- Deliver full-speed PD fast charging for iPhone 18 Pro Max & iPhone 18 Pro Max & iPhone 18 Pro right inside your car. The built-in 45W PD USB-C port hits the peak charging speed for these latest iPhone models, juicing up your phone to 50% power in just 15 minutes while you drive.(Note: Maximum 45W PD output is available under 24V vehicle power supply. When used with standard 12V car sockets, the peak output is limited to 36W.)
- Standard 12V Power Solution: Designed as a dedicated USB power supply for charging devices. Note: Does NOT support CarPlay, Bluetooth, or data transfer. Compatible with most phones, tablets, and small electronics. This retractable charger is a core car organization tool, keeping your vehicle tidy. Not compatible with Micro-USB devices.
- Clutter-Free Tech Organization: Featuring dual USB ports and retractable cables, the LISEN 4 in 1 charger provides a clean car storage solution. Perfect for truck enthusiasts or as a thoughtful gift for drivers, it supports fast USB-C charging for devices like the iPhone 18Pro & iPhone 18 ProMax. Keep your vehicle organized while ensuring efficient power delivery for all your tech on the road.
Make the executable usable on macOS or Linux
On macOS and Linux, change to the installation directory and grant execute permission if the shell reports permission denied:
cd SDK_LOCATION/extras/google/auto/chmod +x ./desktop-head-unitDo not move the bundled libusb library away from the DHU executable. The DHU expects that library to remain beside it. Moving or deleting it can create a startup or device-detection failure even when the package itself is installed correctly.
Meet Linux DHU 2.x runtime requirements
DHU 2.x on Linux requires GLIBC 2.32 or later, plus the libc++1 and libc++abi1 runtime libraries. Check the GLIBC version with:
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →ldd --versionThe first line reports the system’s GLIBC version. If it is older than 2.32, upgrading or changing the host distribution is a compatibility task; reinstalling Android Auto on the phone will not correct it. Install libc++1 and libc++abi1 with your Linux distribution’s package manager. Package names and commands differ between distributions, so use the distribution’s documented repositories and do not copy a command intended for another distribution.
Rank #2
- High Quality Material: The coaster is made of environmentally friendly silicone, safe, non-toxic and odorless. Soft with toughness, easily embedded in the cup holder. Very durable, wear-resistant, long service life. High temperature resistance, can withstand 100 ℃ high temperature water cups.
- Wide Compatibility: The coaster has a diameter of 3.15 inches and a height of 1.18 inches, which is widely used in most vehicles, such as SUV, sedan, MPV, etc., as long as the size fits your car cup holder.
- Protection Function: Our car cup holder coaster has a carry handle design and a stand-up ring edge on its edge to effectively prevent food crumbs, drinks and water from leaking out and preventing the car cup holder from getting dirty.Meanwhile,Thickened design effectively prevents the cup holder from being scratched by the cup when driving on bumpy roads and eliminates the annoying thumping sound, making your journey more enjoyable.
- Easy to Use and Clean: With embedded installation, you just need to put it flat on the car cupholder. It is also very quick to remove, there is a small bump on the coaster, pinch it and you can easily remove the coaster. It is very easy to clean, rinse with water or wipe with a wet towel (be careful not to clean with sharp tools).
- 100% Satisfaction: Our products have quality assurance, if you have questions or are not satisfied after receiving the product, don't worry, please contact us as soon as possible, we provide after-sales service.
- Permission denied: run
chmod +x ./desktop-head-unitin the DHU directory. - GLIBC not found or too old: confirm the host version with
ldd --version; DHU 2.x needs 2.32 or later. - C++ runtime error: install both
libc++1andlibc++abi1for the host distribution. - USB library error: restore the bundled
libusbbeside the executable.
Prepare the Android phone before the first DHU run
- Use an Android 9 phone or newer (API level 28 or higher).
- Enable Android developer mode on the phone.
- Install the Android Auto app and update it to the current version offered for that phone.
- If the phone runs Android 10 or later (API level 29 or higher), sign in to Google Play and update Android Auto before the first DHU connection.
- Keep the phone unlocked during setup. Watch its screen when the DHU first connects and accept any Android Auto terms, permission requests, or trust prompts.
The Android 10-or-later Google Play sign-in and update requirement is easy to miss because the DHU itself may already be installed correctly. A host that launches successfully can still fail to create a session when the phone’s Android Auto installation has not completed its first-run setup.
Connect with Accessory Mode (the normal DHU 2.x method)
Accessory Mode uses Android Open Accessory over USB. It is the recommended DHU 2.x connection method when it is available.
- Connect the prepared Android phone directly to the development computer with a USB data connection.
- Unlock the phone and respond to any Android Auto terms or permission dialogs.
- On macOS or Linux, open a terminal in
SDK_LOCATION/extras/google/auto/and run:
./desktop-head-unit --usbOn Windows, launch desktop-head-unit.exe with the corresponding USB option from a command prompt in the DHU directory. The DHU scans for a compatible connected device. If several devices are present or automatic discovery selects the wrong one, target a specific device with the documented form:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
./desktop-head-unit --usb=DEVICE_IDUse the equivalent executable name and option syntax for Windows. A DHU window appearing without a phone session usually means discovery or phone preparation has failed, not that the Android app being tested is necessarily defective.
Rank #3
- ✅【Designed for Magsafe】 - The most fashionable iphone car mount in 2026 Magsafe is designed for iPhone 18 Pro Max/17/16/15/14/13/12 Pro Max Mini and official Magsafe cases and other magnetic phone cases and can be fixed directly to these phones without the need to affix metal plates. All Android Phones Will Work: Metal rings are provided; they fit cases and other phones without magsafe. Based on Unique Grandmaster Design (Protected by US Design Patent No. US D1,112,194 S)
- ✅【STRONG MAGNETIC MagSafe Car Mount】 - This powerful magnetic phone holder can create a powerful attraction that firmly supports your device while allowing you to drive without distraction. it easily and securely holds your phone through bumps, sharp turns or even sudden stops, no worrying of dropping your phone.
- ✅【SUPER STICK FORCE】 - VHB Dash Mounted Holders adhesive provides strong stick force between the dashboard and the car phone holder, which can firmly stick to any plane in the car, fix your device, adapt to a variety of road conditions such as sudden braking, speed bump, and rugged mountain road.
- ✅【SAFE DRIVING VIEW】 - Mini-size, not taking up space, it is placed in the dashboard without blocking the view at all, and does not need to look down at the device to ensure your safe driving. Cell Phone Car Mount is suitable for most cars, pickups, SUV, taxi; It is the best assistant for Uber and Lyft drivers
- ✅【360° FREE ROTATION】 - With an adjustable swivel ball joint, you can rotate your smartphone or device at your own will, providing the best viewing angle. Quickly pick and place with one hand, free your hands and make calls and GPS navigation more convenient
What to check when Accessory Mode finds nothing
- Confirm the phone is Android 9/API 28 or newer and Android Auto is installed and current.
- Unlock the phone and inspect it for a pending terms, permissions, or USB approval dialog.
- Reconnect the USB cable directly to the computer rather than through a hub.
- On Windows, check whether the phone is using the WinUSB driver required for Accessory Mode; this driver can interfere with ADB.
- If Windows discovery remains unsuccessful, stop the ADB server with
adb kill-serverand start the DHU again, or switch to ADB tunneling.
Use ADB tunneling when Accessory Mode is unavailable
ADB tunneling is an alternate DHU workflow. It is especially useful when Accessory Mode discovery fails or when a Windows WinUSB installation conflicts with ADB. It has more prerequisites, so check them in order.
Enable the phone-side head unit server
- Open Android Auto’s settings on the phone.
- Enable Android Auto developer mode using the developer-menu controls provided by the app.
- From that developer menu, select Start head unit server.
- Confirm that Android Auto shows the head unit server’s foreground-service notification. If the notification is absent, the server is not running and port forwarding cannot establish a session.
- In Android Auto settings, open Previously connected cars.
- Ensure Add new cars to Android Auto is enabled.
Forward the DHU port from the computer
- Connect the phone to the computer over USB.
- Unlock the phone and approve any USB debugging or Android Auto permission prompt that appears.
- From the development computer, create the documented port forward:
adb forward tcp:5277 tcp:5277- Change to
SDK_LOCATION/extras/google/auto/. - Launch the DHU from that directory using its ADB connection option. If you changed the default port, pass the documented DHU host and port options for that port instead of assuming 5277.
ADB tunneling requires every item in the chain: the head unit server must be running, Add new cars must be enabled, the USB connection must be established, the screen must be unlocked, port 5277 must be forwarded (unless you deliberately changed it), and first-time terms and permissions must be accepted. Fix the first missing prerequisite rather than repeatedly restarting the DHU.
Resolve Windows WinUSB and ADB conflicts
Windows Accessory Mode may require WinUSB for the phone. Google notes that installing WinUSB can interfere with the ADB connection used by other workflows. This creates a common pattern: Accessory Mode needs the driver to discover the phone, while ADB tunneling stops working after the driver changes.
- If Accessory Mode cannot discover the phone, run
adb kill-serverbefore starting the DHU again. - Reconnect and retry Accessory Mode.
- If discovery still fails, use ADB tunneling instead. Start the phone’s head unit server, enable Add new cars, unlock the phone, run
adb forward tcp:5277 tcp:5277, and launch the DHU with the ADB option. - If ADB tunneling was working before a driver change and now is not, review the phone’s Windows device driver assignment and return to the connection method that matches the installed driver.
Do not treat WinUSB as a universal Android Auto repair. It is relevant to Windows Accessory Mode discovery and can be the reason to choose the documented ADB fallback.
Rank #4
- Buyer's Guide: The seat guard for car seat between seat & console measures 15.75*2.7*1.53", suitable for gaps of 1.43-1.53" in width, please double-check carefully the distance between your seat and the center console before placing an order
- Storage and Filling in One: Differ from traditional single-function gap fillers, gap filler for car incorporates storage function, offers you the convenience of storing phones and various other items, so that you can access them at any time while driving
- Avoid Items Slipping: With the bumps and vibrations of the car, phones, keys may fall into the seat crevices, which is difficult to pick up, and distracts the driver's attention. Car gap seat filler fills gaps seamlessly to create an effective barrier
- Easy to Install: Car side seat gap filler is easy to install, simply insert it into the gap between the seat and the center console, gap seat filler for car can fit tightly without affecting the normal adjustment of the seat and the use of the seat belt
- Premium Material: Crafted from premium EVA material, our car seat side gap filler boasts a combination of wear-resistant, softness&durability. Maintenance is effortless, simply rinse and wipe to quickly clean the dust and debris in corners and crevices
Troubleshoot DHU failures by stage
The package installed, but the command is not found
Run the executable from the directory where Android Studio installed it: SDK_LOCATION/extras/google/auto/. If you invoke desktop-head-unit from another directory without an absolute or relative path, the shell may report that it cannot find the command even though the package is present.
The DHU exits immediately on Linux
Check execute permission, GLIBC, and the C++ runtime before changing phone settings. Run chmod +x ./desktop-head-unit, verify GLIBC 2.32 or newer with ldd --version, install libc++1 and libc++abi1, and keep the bundled libusb beside the binary. These are host-runtime failures.
The DHU window opens but no phone appears
First decide whether you are using Accessory Mode or ADB tunneling. For Accessory Mode, check the direct USB connection, the Windows driver situation, and any phone-side prompts. For ADB tunneling, verify the head unit server notification, Add new cars, unlocked screen, and the exact port-forward command. Do not combine the two procedures halfway through; each mode has different discovery requirements.
Recommended Free Tools
The first connection stops at a phone prompt
Look at the physical phone, not only the DHU window. Accept Android Auto terms, permissions, and trust prompts. On Android 10 or newer, make sure Google Play sign-in and the Android Auto update were completed before trying again.
Best Value
- 🔰 UPGRADED SIDE STORAGE DESIGN - Our console cover is thinner than the old one, universal for all seasons. There is an 8.66*5.12 inch storage pocket design on each left and right side, expanding the storage space, convenient and practical. Meet the storage needs of the main passenger seat, you can store your cell phone, keys, tissues, ID and some other small daily items.
- 🔰 PREMIUM MICROFIBER LEATHER MATERIAL - This car center console cover is made of quality microfiber leather material, soft and skin-friendly touch. Exquisite and fashionable diamond shaped stitching, every detail is in place. Inside the car center console cover is made of thickened memory foam, even after squeezing, it can slowly recover to its original shape.
- 🔰 RELIEVE DRIVING FATIGUE - The arm rest cover for car adopts ergonomic design, giving just the right amount of arm support, effectively dispersing elbow pressure and relieving driving fatigue. Protect your car's center console from getting dirty or scratched. Especially suitable for long time driving or long distance traveling, bringing you a new experience of relaxation and comfort!
- 🔰 NON-DESTRUCTIVE INSTALLATION - This car console cover is designed with an elastic band for a firm fit and not easy to shake. And the back side is full of protruding dots, which can effectively avoid the armrest cover from slipping and shifting. All you need to do is to open the center console cover, put the elastic band directly into the cover and then close it.
- 🔰 BUYER'S GUIDE - You will receive a car armrest storage box with the size of 12.13*7.80 inch, please measure the size of your car's armrest storage box before you buy. We have prepared five simple and beautiful colors for you, you can choose according to your own preferences. Suitable for most of the vehicles on the market, such as car, truck, SUV, RV, van, etc.
The phone connects but the tested app does not appear
Separate transport from app configuration. A successful DHU connection proves that the head-unit session was established; it does not prove that the app meets Android Auto’s category, manifest, or testing requirements. Resolve any DHU or phone connection errors first, then inspect the app’s own development configuration.
When the problem is an Android Virtual Device instead
An AVD does not replace the DHU’s physical-phone connection. If your Android Studio virtual phone fails to start or display Android Auto-related content, use the Android Emulator troubleshooting guide at developer.android.google.cn/studio/run/emulator-troubleshooting.
- ChromeOS installations can require the
libnss3library. - GPU or Vulkan incompatibilities can cause rendering failures or a black display.
- Slow operation may require addressing emulator performance and host acceleration issues.
- Network and DNS failures need emulator network troubleshooting, not DHU USB forwarding.
Do not install WinUSB, run adb forward tcp:5277 tcp:5277, or change DHU permissions as a first response to an AVD boot or graphics problem. Those changes target a different tool.
Fix Android Auto in a real car separately
A physical vehicle display follows a different troubleshooting path from DHU development. Google’s Android Auto guidance recommends a high-quality USB cable shorter than one metre for wired connections and says not to use a USB hub or extension. Replace the cable if Android Auto worked previously and then stopped. Confirm that the connector matches the phone and that the cable supports data, not only charging.
- Connect the phone directly to the vehicle with the short, high-quality cable; remove hubs and extensions.
- Verify that the vehicle is compatible with Android Auto and that Android Auto is enabled in the infotainment system.
- Restart the vehicle’s infotainment system.
- If the receiver is aftermarket, check the manufacturer’s support site for firmware updates.
- When setting up a second car, forget previously connected cars as Google’s setup instructions describe, then reconnect the phone.
A cable can correct a physical car connection that drops or never starts. It cannot fix a missing DHU SDK package, an old Linux GLIBC, a missing C++ runtime, a WinUSB/ADB conflict, an unforwarded ADB port, or a phone permission prompt.
A repeatable recovery order
Use this order to avoid changing several variables at once:
Quick Recap
- Label the setup as DHU, AVD, or real car.
- For DHU, confirm the package location under
SDK_LOCATION/extras/google/auto/and correct host permissions or Linux runtime dependencies. - Prepare the physical phone: Android 9/API 28 or newer, developer mode, current Android Auto, and the Android 10/API 29 Google Play requirement where applicable.
- Choose one transport: Accessory Mode first for DHU 2.x, or ADB tunneling when discovery or driver conflicts make it necessary.
- For Accessory Mode, address USB discovery and Windows WinUSB/ADB interaction.
- For ADB tunneling, verify the head unit server, Add new cars, unlocked screen, USB link, port 5277 forwarding, and first-run approvals one by one.
- Only after the DHU path is working should you investigate the tested application itself.
- For a real car, stop using DHU fixes and check the short cable, vehicle settings, infotainment restart, and receiver firmware.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
