There are also AA settings on the phone that impact how it will behave when it is connected.I can't say much about AA but assume that the requirements and procedures are the same. Helmets connect to bike. It takes a 1/2 minute for helmets to completely connect even after the helmets show on dash panel. Even though some cables are fine for charging, they are not suitable for transferring data reliably. I have purchased cheap cables and if they work, they seem to fail too soon. If you have the Android Auto installed on phone, make sure that your screen is lit up before attaching data/power cable to phone. Do not have bluetooth connection of phone. If this does not work, make sure you have shut off phone and turned it back on. Be sure your phone as capability for AA.
My two cents worth. I was also at my wits end and eventually came down to the cable. I had tried at least a half dozen, always buying the cheapest (a cable is a cable, right) Eventually bit the bullet and bought a top of the range cable. Can you believe it, works great now. Type C cables (especially made in China) are very fussy.Only good if they work and mine don't! have tried for two weeks and have yet to get Android auto working...
I have the some problem, but I believe the problem is in the headset, not in the bike system.Don't feel like the lone "stranger". ACP has it's problems too. Sometimes disconnects for no reason while riding (no loose cables), and says helmet headset needs to be connected first, when it already shows connected. Welcome to modern consumer electronics.
I am an Android user.Automakers are now starting to release 'wireless' versions of ACP/AA too. Gotta keep up with aftermarket....
Those I've looked at, it seems to depend on what trim level is on the vehicle. (of course, higher trims getting the wireless version)
I am using only braided magnetic cables. The brand is Remix.My two cents worth. I was also at my wits end and eventually came down to the cable. I had tried at least a half dozen, always buying the cheapest (a cable is a cable, right) Eventually bit the bullet and bought a top of the range cable. Can you believe it, works great now. Type C cables (especially made in China) are very fussy.
I have to agree with that. A good quality cable goes a long way and saves a lot of aggravation. Don't discount using some of theses "cheap" cables as pretty much ALL do come off the same assembly line in one of the Republic of China countries. Always look for the HSC insignia on the packaging as you will be assured of getting the best quality knock-offs and counterfeit products. The insignia guarantees your product was manufactured in the HungLow province and was certified by Harry S. Chung, the Minister of Commerce. That said, I really never had any issues with cables.My two cents worth. I was also at my wits end and eventually came down to the cable. I had tried at least a half dozen, always buying the cheapest (a cable is a cable, right) Eventually bit the bullet and bought a top of the range cable. Can you believe it, works great now. Type C cables (especially made in China) are very fussy.
I do. A buddy and I did a road trip from Wisconsin > New Orleans > Los Angeles > Seattle > Wisconsin back in the day. Only map was a two-page US highway map of the whole country. This was 1978, so pre cell phone days. We didn't even have credit cards. Stayed off the Interstates except in cases where they were the only roads we can find ... well and from Sturgis back to Madison. (We were kind of sick of each other by that point.) Anyway, b206driver is so right that the adventure is part of the deal. However, I do recognize that GPS and weather radar are useful for when you're DRIVING rather than EXPLORING.Do you remember the good 'ole days when you threw a leg over the bike, fired it up and only heard the engine and the wind? And you had to refer to a paper map in your tank bag?
I had similar problems with how it initiated AA on the bike. tried lots of options until the following worked for me:I will start out by saying that this really will not be considered a "loss" as I want my phone connected and used through my Zumo 595, not the bike.... I wanted to see what Android Auto brings to the table.
I finally got the update downloaded (failed many, many, many times to transfer). The install went fine, no errors or anything on the bike. I downloaded Android Auto and connected it all up. I keep getting either "stop the bike and follow directions on phone to use Android Auto" or "Android Auto failed to connect" (paraphrased as this is the less frequent message). The phone has no instructions, but I may get a complaint that I have not give permissions to "phone" and fails to connect, or worse, a red screen that it stopped working. A permission issue is not the case as "ALL" permissions were granted, there is nothing left to grant. I have even "reset Android Auto" on the bike settings many times, set "ipod" and "carplay" back and forth many times (which only adds or removes Apple Play from the "reset settings" list. There is nothing new on the screen for phone apps like I would suspect.
Now, I will not really be following this thread much, but I am sure I will not be the only Android person beating their heads against the wall with this. If anyone has some screen shots of what we are supposed to be seeing with Android Auto (NOT Apple, use another thread for that), please post.