GL1800Riders Forums banner

Need help connecting Android phone to my 2018 wing.

290 Views 10 Replies 5 Participants Last post by  networkguy3
Hi all.

I have a new to me 2018 Honda Goldwing Tour.

I am having problems trying to connect my phone/android auto to this bike.

I have updated the software to the latest per Honda: HG.ACM.21.11.28.12.04.00

I have paired my Lexin B4FM headset to the bike. Pairing works. A headset and 1 are up in the top left corner of the bikes display.

My phone is a Samsung Galaxy S22. The Android auto appears to be on all the time on this phone. Connects to my 2019 Buick as soon as I plug in.

I followed the instructions on this video:

His Android starts right up as soon as he plugs in.

Mine does nothing. I know my wired connection is good because my phone begins charging when I plug in.

Any ideas?
1 - 11 of 11 Posts
Hard to say... many people have many different results. Best I can do it list what I do:
  • My Samsung Phone (S22+) is NOT Bluetooth connected to the bike - Cable Connection Only
    • I plug the phone into the bike when I first walk up to it (bike is off at this point)
      • I have a music player on my phone that plays my own playlists, that are stored on my phone (Samsung Music)
  • Immediately after I start the bike, even before the bike's screen is fully active, I then turn on my 'headset' (actually Bluetooth earbuds, but either will work) * Paired to the BIKE not the Phone *
  • Once they connect to the bike, Android Auto starts on the bike's Nav system
  • Total process from turning on the bike to connected and playing music = 10-15 seconds
  • ----- Below is just how I do things using earbuds to "trick" AA into starting -----
  • Immediately after the buds connect, I put them back in their charging case (turning them off)
    • AA notifies me the 'headset' is disconnected, but remains active with maps, music, and all AA functions
  • In Android Auto on the bike, I now have access to all the albums that are on my phone, played through the bike's speakers.
    • If I actually leave the buds connected, I can wear them, and all sound & notifications from the bike run through the ear buds, but I prefer to run the speakers.
AA Settings on you phone:
  1. Start AA Automatically - ALWAYS
  2. Start AA While Locked - ON
  3. "Hey Google" Detection - HANDS FREE VOICE COMMANDS
  4. Customize Launcher - If you want to use apps within AA, have them selected here
    1. You can reorder them here as well, add phone call contacts, etc...
  5. Other settings as you want/need
HTH! :cool:
See less See more
  • Like
  • Helpful
Reactions: 2
When you first plug it in, keep the phone unlocked and watch the screen. First time you connect you have to tell the phone it is ok to do so.

If that isn't the problem, it is the cable you are using. Our Wings are very picky about the cable.
  • Like
Reactions: 2
  • Like
Reactions: 2
Thank you all for your responses. I have gotten it to work. It appears to have been a couple of things (which always makes it harder).

I replaced the cable that had a usb to usb-a (I think) with -c adapter and put on a clean usb to usb-c. With that I when I plugged in the phone I got an error (paraphasing) "Android auto could not start because the headset is disconnected". At least I got something!

Keep in mind my headset was on, and had stated "connected" and the wing had a headset and 1 still in the top left corner. Crud, now what?

So I kept turning wing, headset on and off and phone (plugged in). Finally I found the right combo and it worked. Asked if I wanted to connect always, yup, 1 continue on the wing screen and I was in. Google maps and Sirius XM both working and on screen. Yeah.

Then came trying to recreate what order I did things. I "think" the order for this bike is on, turn on headset, get a connection and then plug in. It fails sometimes and works sometimes. No idea why.

I did find out once I was in, I could turn off the headset and the Android auto kept working on the bike.

Part of my problem may also be blutooth. I turn if off, and unpaired it from the wing. Plug the phone into the wing and it auto comes on and pairs itself to the wing. I hate programmers that think, "Hell, he doesn't know what he wants, we will over ride it and no way to stop it".

I do want to add that I used a number of your recommendations and they helped. Thanks again to all.
See less See more
  • Like
Reactions: 1
. I "think" the order for this bike is on, turn on headset, get a connection and then plug in. It fails sometimes and works sometimes. No idea why.
Welcome to the club. What you describe is apparently considered normal at Honda. Couple of expansion to your list above.

Bike on, wait for the Nav system to fully start up.

Then the headset. Again wait a bit.

Then the phone.

No headset detected is the most common error we face. I have noticed with my Sena that there are two voice notifications from the Sena when it connects. First time it says "media connected" them a few seconds later it says "phone connected". In my case making sure I get that second prompt helps.
Plug the phone into the wing and it auto comes on and pairs itself to the wing.
Depending on who makes the phone Bluetooth turning itself back on is a thing. I hate it, off means off. It also means Bluetooth is never really off, it is on enough to know it is in range of something you have used Android Auto with before.
So my post above got me to Google why Android Auto requires Bluetooth.

The answer is that the audio for phone calls goes through Bluetooth even when your are cable connected with Android Auto.

Now why they chose to do it that is still a mystery.
  • Like
Reactions: 1
So my post above got me to Google why Android Auto requires Bluetooth.

The answer is that the audio for phone calls goes through Bluetooth even when your are cable connected with Android Auto.

Now why they chose to do it that is still a mystery.
I suspect is it is an Android thing - not a Honda thing - that manages the HPF protocol from the A2DP protocol when using AA. Honda had to implement AA as Google designed it
  • Like
Reactions: 1
I suspect is it is an Android thing - not a Honda thing - that manages the HPF protocol from the A2DP protocol when using AA. Honda had to implement AA as Google designed it
Oh that part is totally an Android thing. Same behavior with my car.
Welcome to the club. What you describe is apparently considered normal at Honda. Couple of expansion to your list above.

Bike on, wait for the Nav system to fully start up.

Then the headset. Again wait a bit.

Then the phone.

No headset detected is the most common error we face. I have noticed with my Sena that there are two voice notifications from the Sena when it connects. First time it says "media connected" them a few seconds later it says "phone connected". In my case making sure I get that second prompt helps.
With the Sena 50S, AA will usually start up if my headset is on when I turn on the motorcycle, even with the phone already plugged in. It seems AA takes long enough to start up that the headset connects before AA looks for the headset. Like many things bluetooth, other Bluetooth devices in the area may cause issues with the timing of the connections. I have the same issue with the connection between my phone and my Neutrino Element PDU which is has a Bluetooth connection to the phone. Sometimes close to my house, the phone won't connect at all. If that happens I have to move away from my house and then restart the software for the Neutrino Element to get it to connect. The other connection that seems to be sensitive to other BT devices around is the HFP connection between my Garmin Zumo and my headset. With the Zumo connection, other devices around can make the audio from the Zumo be very choppy even to the point of being impossible to understand.
1 - 11 of 11 Posts
Top