I Gave My Broken Pixel 4a a Second Life on My Motorcycle

An old Android phone becomes a clever motorcycle navigation device, while Android Auto exposes frustrating limits on small screens.

By early 2026, my old Pixel 4a had been living in a drawer for more than two years. It was cracked, slightly bent, and officially out of Google's software support cycle, but it still booted, still held a charge, and still had working cameras. Honestly, it refused to die. I had already upgraded to a newer phone, but I couldn't bring myself to toss the old one. The drawer became its retirement home, and I told myself I would find a use for it someday.

That someday arrived when I started shopping for a navigation device for my current motorcycle. I did not want to mount my main phone to the handlebars. Phone mounts can damage a camera's OIS, or optical image stabilization, and I was not about to risk my daily driver. The Pixel 4a, with its cracked screen and bent frame, was the perfect test device. If it fell, I would be annoyed—not heartbroken.

i-gave-my-broken-pixel-4a-a-second-life-on-my-motorcycle-image-0

The phone's backstory made the project feel personal. In December 2023, it was in my pocket during a motorcycle crash and took most of the impact from the handlebars. The screen cracked and the frame bent, but the phone kept working. I retired it anyway, mostly because I did not want to risk a battery leak or fire. Nearly two years later, in 2025, it still worked fine. By 2026, it was old, unsupported, and a little grumpy, but it could still log into my Google account and run the apps I needed.

Setting everything up was easy. I picked up a Quadlock-inspired mount from a local bike shop, dusted off the Pixel 4a, charged the battery, and mounted it to the handlebars. I run Google Maps and YouTube Music on the old phone, powered by a personal hotspot from my main phone. My helmet intercom connects to two devices at once, so the Pixel 4a handles navigation and music while my Pixel 9a handles calls and notifications. No kidding—it felt like I had hired a tiny, cracked-screen co-pilot.

For a while, the setup was great. Then I got greedy. I wanted to change music and destinations without stopping, taking the phone out of the holder, making changes, and getting going again. That routine is not a huge hassle, but it is a bit of a pain when you change tracks as often as I do. So I tried turning the Pixel 4a into an Android Auto head unit using the Headunit Reloaded Emulator HUR app. It is a cheap $5 app that lets you use an old phone or tablet as an Android Auto display over USB or Wi-Fi.

The app works, and setup is simple, but the experience on a small phone was rough. I ran into display scaling issues. The map was unresponsive. The buttons were hard to press. Android Auto is made for larger screens, and on a phone as small as the Pixel 4a, it felt like trying to read a billboard through a keyhole. The app also drained the battery faster than my motorcycle's built-in charging port could power the phone, so I often ran out of battery mid-ride. And because Android Auto is built for cars, it only showed car routes. Google Maps has different routes for motorcycles and cars, so that limitation made the whole experiment useless for my bike.

That failure taught me something useful: the old phone is not a magic infotainment system. It is a focused tool. For my motorcycle, plain Google Maps and YouTube Music in the regular Android interface work better than Android Auto. If you want an Android Auto head unit for a car, the HUR approach can work wonders. For a bike, let us be real—simple is better.

There are a few catches you should know before you reuse an old phone. Battery life is the big one. With maps and music running, brightness cranked up, and the phone constantly working, I can run the Pixel 4a's battery down in as little as two hours. Thankfully, my bike has a built-in USB-C charging port, which keeps it alive. Without that, the phone would be unusable unless I found a replacement battery. The screen is another issue. Mine is cracked, the frame is bent, and the brightness is low, so visibility takes a hit in daylight. Depending on how old your phone is, this may or may not be a problem.

✅ What worked well ⚠️ What did not work well
Google Maps and YouTube Music via hotspot Android Auto on a small screen
Helmet intercom pairing with two devices Display scaling and unresponsive controls
Cheap mount and easy setup Battery drain during long rides
Keeping my main phone safe Car-only routes in Android Auto

Even with the drawbacks, the Pixel 4a turned out to be exactly what I needed. It handles navigation duty, removes my anxiety about dropping expensive hardware mid-ride, and even comes in handy as a backup camera. Is it fancy? No. Is it practical, affordable, and surprisingly effective? Absolutely. If you have a broken or aging Android phone lying around, and you want to add navigation or music to your vehicle, give this a shot. You might just find that the old tech in your drawer has been waiting for a second chance...

And honestly? That quiet moment when the old phone lit up on the handlebars, cracked screen and all, felt like a small victory. It was not the fastest setup, and it was not the prettiest. But it was mine, it worked, and it kept my main phone out of harm's way. In 2026, with e-waste piling up and new gadgets getting more expensive, that feels like a win worth sharing.

Comments