Re:Malware infects Android-based automotive head unit firmware
by m-s-y on Sunday August 23, 2026 @11:24AM
(#49409569)
Wireless CarPlay uses Bluetooth to exchange SSID and key info before switching over to WiFi for the duration of the session.
[ Parent
| on HN ]
Re:Malware infects Android-based automotive head unit firmware
by NewJazz on Sunday August 23, 2026 @03:17PM
(#49411580)
Wow that's cursed, never realized that's how it worked.
Re:Malware infects Android-based automotive head unit firmware
by xp84 on Sunday August 23, 2026 @05:40PM
(#49412904)
Cursed is exactly how I would describe it - because it works great until it doesn’t and it of course gives you zero clue why it won’t connect.
Re:Malware infects Android-based automotive head unit firmware
by NLMichel on Monday August 24, 2026 @10:04AM
(#49419961)
Anecdotally, I just got back from a holiday trip across Europe and crossed four international borders. At every single border crossing, my CarPlay session disconnected, and I had to toggle CarPlay off and back on in my phone settings to reconnect. Very strange, and I still have no idea what caused it.
Re:Malware infects Android-based automotive head unit firmware
by bluGill on Sunday August 23, 2026 @07:43PM
(#49413689)
It's a good idea actually, but it's also really complex to get right.
Early version of Android Auto could transfer over USB 2.0 instead of Bluetooth, which works, but it's not near as high bandwidth.
Re:Malware infects Android-based automotive head unit firmware
by izacus on Monday August 24, 2026 @04:15AM
(#49416668)
> Early version of Android Auto could transfer over USB 2.0 instead of Bluetooth, which works, but it's not near as high bandwidth.
This sentence doesn't make much sense - Auto (and CarPlay) still work in wired mode over USB 2.0 if the head unit supports it. They never worked over Bluetooth.
(And they use less than 15Mbps so USB 2.0s 480MBps are more than enough)