Problem is I am stuck here.
Nothing happen when I plug in
It would help a lot of you could find another another Android phone and check whether it has the same issue. And if it doesn’t work either, do yourself a favor and ask your Suzuki dealer if there’s a software update you’re missing.
3 Likes
I think the wired Android Auto and even CarPlay require Bluetooth connection for sound. The USB bandwidth is not big enough to fit everything (video, audio, metadata). I assume it’s an old USB 1.0 standard (my car has a white USB socket for Android Auto).
My FP5 works without issues in my car (different brand), and I even tried it with various Android Auto wireless adapters. All good. The same was true with FP4. Since FP5 uses an almost stock Android, it should be fine out of the box unless you change settings.
The first thing I would check is the cable. It has to support data transfer. I would try to confirm that by:
- setting the phone in MTP/USB Storage mode
- connect it to a computer or even to the car in storage mode to check if it detects audio files on it (assuming your car supports it, and you have some music on the phone).
A lot of cables are “charge-only” cables. They don’t have the wires for the data lines. My father had the same issue. Because of this, he took his car to warranty, and he was a bit embarrassed when the outcome was a note: buy a “data” cable.
Then I would double-check this:
Then, play with different USB settings by searching for USB in the configuration app.
5 Likes
I have recently acquired a Suzuki Swace, which features Android Auto and is not featured on any of the compatibility lists posted earlier in this thread. When I got it, I was very eager to try out Android Auto and was immediately disappointed when it just didn’t work with my Fairphone 4 on Android 13.
Luckily I had multiple cables at my disposal which I could try out. Only one would work: The one with a blue USB A to C connection, meaning a USB 3 cable. All the others, which had white USB A plugs did not work as I guess speed is not high enough or they are just charging cables.
When I asked the dealer as to why Android Auto needs a cable at all he responded that there is simply too much data being transferred and only very recently (I guess via Bluetooth 5 or Wi-Fi) is it possible to use Android Auto wirelessly.
So all this leads me to believe that Android Auto needs a good USB 3 compatible cable to ensure it has the proper bandwidth available.
1 Like
Which software version is running in your cars navigation system? Did any other Android ever run on this car? My Opel needed an update first, when i got the car because no other Android device at all connected (some years ago).
In case of Android Auto problems please always try to cross check with other Android phones (e.g. colleagues) and cables. Please check car manufacturer related topics in other support forums as well.
Please note, i googled your car type and there were reports of other users with other phones that had troubles with some firmware of the car …
My FP5 connects out of the box via wired Android Auto without any problems with a Toyota C-HR and an Kia EV6.
Even with an AAWireless-adapter I can use wireless Android Auto with my FP5. This works with all three firmware versions I used on my FP5 since I bought it.
Thanks to all of you
I will buy a generation 2.1 blue usb C short cable to try (already try with 3 diff cables)
I can’t access to update option in my screen car, was working with iPhones but not with android, I will see if I can do update in a Suzuki garage.
A post was split to a new topic: FP4 Android Auto not working
I got the more expensive USB 3.2 cable, and so far Android Auto now works. There has been an occasion where it didn’t, but this was probably the fault of the car’s system as it worked before in this same car and it works without issues in another car.
My android auto stopped working with my Fairphone 5 on my Jaguar I-Pace.
It was still working with the same cable (OnePlus red) on my spare Nokia 5.3 and it worked with my Fiat500e wirelessly.
I deleted the app from play store, updated the app and then switched on usb debugging.
It now works.
1 Like