I plugged my Pixel into my car last week, waited for Android Auto to come up, and noticed the wireless projection option had vanished. It used to be in the main settings. After a software update, it was gone. I spent twenty minutes looking for it before a forum thread pointed me at the developer menu, which is exactly where Google quietly parked it. Here is the shortcut I wish I had known on day one.
The panel Google built for engineers but ships to everyone
Android Auto hides a separate developer menu inside the Android Auto app, completely apart from the Developer Options screen in your phone’s main Settings. Turning on the global Developer Options does not unlock this one. The Android Auto panel is older than most of the toggles it now contains, but Google has been quietly moving user-facing controls into it whenever the company wants to clean up the main settings screens.
The path to the panel is the same idea that has shown up in every Android version for the past decade: scroll to the bottom of a settings screen, find the version number, and tap it ten times in a row. A confirmation dialog appears, you accept it, and a new Developer settings entry shows up in the three-dot overflow menu at the top of the screen. Pick it to open the hidden panel. To revert, use the same overflow menu and pick Quit developer mode. The whole dance takes about ten seconds, and the unlock does not survive a factory reset, so you only have to do it once per device.
The exact path to the Android Auto settings screen varies by phone, and Google has not consolidated the menu across vendors. Pixel phones route the settings through one branch of the Apps list, Samsung and OnePlus phones route through another branch, and most modern Android phones also offer a generic Connected devices path as an alternative. The hidden menu you unlock is the same one regardless of which path you took.
- The Android Auto developer panel is separate from the global Android Developer Options menu
- Open the Android Auto settings screen, scroll to Version, tap it ten times in quick succession
- A confirmation pop-up appears; accepting it adds Developer settings to the overflow menu
- To revert, open the overflow and pick Quit developer mode
- Nothing in the menu persists across a phone reset
Why the wireless toggle matters
The wireless Android Auto toggle is the headline item inside the hidden menu. It is not a developer experiment or a debug switch. It is the regular wireless projection feature, just moved out of the main settings to keep the user-facing screens uncluttered. For anyone who has ever connected a phone to a car and watched the wireless option disappear after a software update, this hidden menu is where the switch now lives.
Flipping it on restores wireless projection to your dashboard screen, assuming the dashboard receiver and the phone both support it. Some aftermarket dashboard receivers advertise wireless projection but actually lock the feature behind a specific firmware version you have to chase down from the manufacturer. In that situation, the toggle alone will not bring back wireless projection, and the dashboard receiver firmware is the next thing to check.
The catch is real, but the upside is clear: if you drive with Android Auto every day, you almost certainly want the wireless toggle on, and the only reason it is not on by default is that Google decided the main settings screens were getting too crowded.
- The wireless toggle is the regular wireless projection feature, not an experiment
- Flipping it on restores wireless projection to a head unit that supports it
- Some aftermarket head units lock wireless projection behind firmware versions
- Check the head unit firmware if the toggle does not bring back wireless projection
The sideloaded apps switch is the riskier headline item
The other headline switch inside the hidden menu lets Android Auto run apps from outside the Play Store whitelist. Android Auto normally restricts the car dashboard to apps Google has approved, and that list is short on purpose. The sideloaded apps switch is the door that opens the door to third-party navigation apps, custom media players, and experimental builds you trust enough to run on a five-inch screen bolted to your dashboard.
The risk is that there is no sandbox between a sideloaded Android Auto app and the rest of your dashboard. A misbehaving navigation app can take the whole head unit down, which is a different category of problem than the same app freezing on your phone. Google keeps the whitelist tight for a reason, and turning on sideloaded apps is opting into that risk.
Most drivers should leave the switch off unless they trust a specific third-party client. The whitelist is tight for a reason, and the car dashboard is a bad place to debug a buggy app while you are driving.
- The sideloaded apps switch lets you run apps from outside the Play Store whitelist
- Android Auto normally restricts the dashboard to Google-approved apps
- No sandbox separates a sideloaded app from the rest of the dashboard
- Most drivers should leave the switch off unless they trust a specific third-party client
The diagnostic switches are noise, with two exceptions
Beyond the two headline items, the hidden menu contains a handful of diagnostic switches that exist for engineers and one or two that are genuinely useful for everyday drivers. Most should be left alone.
The forced wired connection toggle is the first exception. If you bought an aftermarket dashboard receiver that lies about supporting wireless projection, this switch forces the connection over USB regardless of what the receiver advertises. It is the right answer for a flaky wireless link on a dashboard you already know is borderline.
Verbose logging is the second exception. Turn it on when you are filing a bug report, and only when you are filing a bug report. The log file fills internal storage fast and does nothing for you until you attach it to a real support case.
Experimental flags are tempting but should be left alone. Flipping them on without reading the release notes is how people end up with broken car connections they cannot explain.
- Forced wired connection helps with aftermarket head units that lie about wireless
- Verbose logging is only useful when filing a bug report with a real log file attached
- Experimental flags should be left alone unless you have read the release notes
- Most diagnostic switches in the menu can be reverted the same way they were turned on
Trade-offs
Developer mode for Android Auto is mostly safe, but it does change a few things you should know about. The wireless toggle may surface features your head unit advertised but cannot actually deliver, which leaves you staring at a connection error instead of the user-facing screen that said everything was fine. The sideloaded apps switch is a foot-gun if you install builds from developers you do not trust, because a misbehaving app can take the whole dashboard down with no sandbox to catch it. The forced wired connection toggle can disable wireless projection on a head unit that was working fine before, which is useful for diagnostics and annoying for everyone else in the car.
In my case, the wins were the wireless toggle (a feature Google quietly moved out of regular settings) and the diagnostic switches for troubleshooting a flaky dashboard receiver. The loss was zero, because I left the sideloaded apps switch off and I did not touch the experimental flags. Your math will differ if you bought an aftermarket dashboard receiver that lies about wireless support, or if you want to run a third-party Android Auto client you already trust.
For daily drivers, the right move is to flip on developer mode, turn on the wireless toggle, and leave everything else alone. The sideloaded apps switch stays off unless you have a specific third-party client you want to run. The diagnostic flags stay off unless you are actively debugging a connection problem.
What I would tell past me
Three things, ordered by how much frustration they would have saved.
- Turn on developer mode before the first drive. The taps take about ten seconds, the menu can be put back the way you found it, and the wireless toggle alone is worth the effort.
- Default the sideloaded apps switch to off. A misbehaving third-party Android Auto app can take the whole head unit down, and there is no recovery button.
- Verbose logging is for bug reports, not for curiosity. The log file fills internal storage fast and does nothing for you until you attach it to a real support case.
Most of the hidden menu is built for engineers, and should be left to them. The wireless toggle and the forced wired connection switch are the only items most everyday drivers will ever touch. Flip those. Leave the rest alone.