Toyota GR86, 86, FR-S and Subaru BRZ Forum & Owners Community - FT86CLUB

Toyota GR86, 86, FR-S and Subaru BRZ Forum & Owners Community - FT86CLUB (https://www.ft86club.com/forums/index.php)
-   GR86 General Topics (2nd Gen 2022+ Toyota 86) (https://www.ft86club.com/forums/forumdisplay.php?f=97)
-   -   Android Auto Keeps Crashing -> Need Wireless adapter? (https://www.ft86club.com/forums/showthread.php?t=149509)

Stigmaru 04-17-2022 10:29 PM

Android Auto Keeps Crashing -> Need Wireless adapter?
 
"Launching Error: To use Android Auto, please check the vehicle settings and the Android Device. The application is unavailable due to no GPS signal or the system clock not being set."

I've used two different USB-C cables already and both do the same thing.

https://i.postimg.cc/nV5jzZsd/launcherror.png

I'd like to try a wireless Android Auto box, but i haven't found any that works for Android phones. I bought a Carlink 3.0 but it only supports iPhones. :bonk:

edj 04-18-2022 12:03 AM

i had to un-pair my phone from the car and then pair it again. make sure the password
gets generated and stored/accepted correctly. ymmv.

treedodger 04-25-2022 12:09 AM

I have the exact same problem/error message. I bought a couple high end USB cables, this didn't fix it. Same problem w/ my Moto G7 and a Pixel4a.

I gave up on Android Auto, and just use Bluetooth. I imagine there will be a firmware fix at some point.

Let me know if you figure it out!



Quote:

Originally Posted by Stigmaru (Post 3517688)
"Launching Error: To use Android Auto, please check the vehicle settings and the Android Device. The application is unavailable due to no GPS signal or the system clock not being set."

I've used two different USB-C cables already and both do the same thing.

https://i.postimg.cc/nV5jzZsd/launcherror.png

I'd like to try a wireless Android Auto box, but i haven't found any that works for Android phones. I bought a Carlink 3.0 but it only supports iPhones. :bonk:


finch1750 04-26-2022 01:22 PM

We use a Motorola MA1 wireless adapter and get the same error some times. It usually fixes itself after a minute or two but sometimes I have to unplug the adapter and plug it back in. I thought it was the wireless having issues but I guess not

dragoontwo 04-26-2022 01:37 PM

I have yet to see this error on the Subaru. Will keep a look out.

Spektyr 04-26-2022 04:25 PM

I got this once. Set the clock.

Never saw it again.

spcmafia 05-03-2022 10:46 AM

Some phones are a bit picky on what cables they allow for use. For example, my Apple, being Apple, carplay won't fully work unless I'm using an original Apple cable. I had an otterbox $30 cable and it barely works for carplay, but works 100% for charging at home.

Try using some contact cleaner on the USB/charging terminals on phone, cable, and car.

Dubscientist 05-03-2022 01:52 PM

I had this same issue, I haven't had it since I started plugging my phone before I start the car.

timurrrr 05-04-2022 02:49 AM

So the essence of this thread is "Android Auto doesn't work reliably for me, should I replace a supposed-to-be-reliable connection method with a typically-less-reliable connection method"?

Mhaley777 05-10-2022 02:24 PM

Call Customer Care
 
I had similar issues when I bought my car. It may be a toyota issue. I had to call customer care and they had to update settings on their end in order for my apps to work. Took longer for the toyota app but I was having android issues too and they helped resolve that. If you've exhausted all other options they may not be a bad idea to try. Hope it helps!

Stigmaru 05-13-2022 02:24 PM

Quote:

Originally Posted by timurrrr (Post 3520775)
So the essence of this thread is "Android Auto doesn't work reliably for me, should I replace a supposed-to-be-reliable connection method with a typically-less-reliable connection method"?


1) Your hypothesis is highly inaccurate. Don't be a douche. There was a high chance that this is a software bug rather than a connection problem. Bluetooth connection itself is reliable, it's just software that is tricky.

2) I've read on a couple places that people blame the car's clock vs the phone's clock. There could possibly be a bug where if the car's clock and the phone's clock don't match up the Android Auto software crashes and this happens whenever the minute gets offset. Hard to tell as when it does crash the minutes are off between the two but it's difficult to say that it's not just coincidence

3) I fixed the problem. I ended up buying a wireless bluetooth adapter off Amazon (https://www.amazon.com/gp/product/B0...?ie=UTF8&psc=1) This one specifically, and I never got the crashing again. What I noticed is that this Ottocast device is a microcontroller that runs its own software that seems to emulate Apple Carplay. Which is funny because I'm using an Android device. So the Android phone bluetooth pairs with the Ottocast and the phone thinks it's connected by Android Auto, but on the GR86 side it sees Apple Carplay instead. No more crashing. Right now the culprit seems to be with Android Auto just being buggy with the GR86.

Andrew025 05-18-2022 01:56 AM

Quote:

Originally Posted by Stigmaru (Post 3522872)
1) Your hypothesis is highly inaccurate. Don't be a douche. There was a high chance that this is a software bug rather than a connection problem. Bluetooth connection itself is reliable, it's just software that is tricky.

2) I've read on a couple places that people blame the car's clock vs the phone's clock. There could possibly be a bug where if the car's clock and the phone's clock don't match up the Android Auto software crashes and this happens whenever the minute gets offset. Hard to tell as when it does crash the minutes are off between the two but it's difficult to say that it's not just coincidence

3) I fixed the problem. I ended up buying a wireless bluetooth adapter off Amazon (https://www.amazon.com/gp/product/B0...?ie=UTF8&psc=1) This one specifically, and I never got the crashing again. What I noticed is that this Ottocast device is a microcontroller that runs its own software that seems to emulate Apple Carplay. Which is funny because I'm using an Android device. So the Android phone bluetooth pairs with the Ottocast and the phone thinks it's connected by Android Auto, but on the GR86 side it sees Apple Carplay instead. No more crashing. Right now the culprit seems to be with Android Auto just being buggy with the GR86.

I've seen a good amount of people complain about Carplay and Android Auto issues on the Facebook groups, but they all use wired.
I've been using one of the wireless adapters and I've had 0 issues with mine.

timurrrr 05-18-2022 02:29 AM

Quote:

Originally Posted by Stigmaru (Post 3522872)
1) Your hypothesis is highly inaccurate.

Please re-read the supposed-to-be- and typically-less- qualifiers I've used in my previous post. :)

Glad the wireless solution helped you and @Andrew025!

Yoshoobaroo 05-18-2022 09:28 AM

Android Auto Keeps Crashing -> Need Wireless adapter?
 
Quote:

Originally Posted by Stigmaru (Post 3522872)
3) I fixed the problem. I ended up buying a wireless bluetooth adapter off Amazon (https://www.amazon.com/gp/product/B0...?ie=UTF8&psc=1) This one specifically, and I never got the crashing again.


Ugh. That’s like the only one of the major adapters I didn’t try lol. They all had connection drop issues after ~20-30mins of driving on CarPlay. I told myself I’m not buying another one lol [emoji23]


All times are GMT -4. The time now is 03:23 PM.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
User Alert System provided by Advanced User Tagging v3.3.0 (Lite) - vBulletin Mods & Addons Copyright © 2026 DragonByte Technologies Ltd.


Garage vBulletin Plugins by Drive Thru Online, Inc.