How odd. I'm on slightly newer versions of AA and Waze and it definitely does not work for me. Google Maps is fine.
-
Want to remove ads? Register an account and login to see fewer ads, and become a Supporting Member to remove almost all ads.
TESLAA - Android Auto for Tesla App
- Thread starter Jason71
- Start date
-
- Tags
- display driver display gui
goRt
Active Member
KArnold
Active Member
Yes, all of the time. You can also respond to alerts via the car's screen.
Hi there. I just purchased tried this app yesterday. It's a slick program and works very well. I really like the ability to use Android Auto as well as the other accessible android apps within my Tesla. The one question I had though....is with Google Assistant as the default voice command, is there a way to engage Navigate On Autopilot? Eg) double click microphone button to engage Tesla voice control over Google Assistant? Thanks in advance.
KArnold
Active Member
I've not noticed any exclusivity between the apps, assuming the voice inputs are not used simultaneously. Tesla voice commands nicely coexist with TeslAA/AA commands.
I tried teslaa today.. I'm not sure I'll keep using it.. couple of problems:
1. It keeps staling and flashing on and off, which is pretty annoying when trying to navigate using it.
2. The screen layout seems fixed unless there's something I've completely missed.. 1/4 of the screen dedicated to the weather.. given the screen is already small due to having to fit into the tesla browser space is seems pretty wasteful. Waze suffers a lot from that, being stuck in the top half of the screen.
3. When you add a new app you have to reboot the phone and manually reconnect everything.. teslaa doesn't seem to ever ask the phone if there are new apps unless you do that.
1. It keeps staling and flashing on and off, which is pretty annoying when trying to navigate using it.
2. The screen layout seems fixed unless there's something I've completely missed.. 1/4 of the screen dedicated to the weather.. given the screen is already small due to having to fit into the tesla browser space is seems pretty wasteful. Waze suffers a lot from that, being stuck in the top half of the screen.
3. When you add a new app you have to reboot the phone and manually reconnect everything.. teslaa doesn't seem to ever ask the phone if there are new apps unless you do that.
goRt
Active Member
Are you able to clarify how you engage Tesla Navigation via voice? When I press the microphone button on the steering wheel - Google Assistant is the default voice command. How are you able to engage the Tesla Voice command to use Navigate On Autopilot. (eg) I said "Navigate Home" - which was processed by Android Auto - not Tesla Navigation. Thanks
KArnold
Active Member
I don't recall seeing any setting like that. When I press the Tesla button, it beeps, I say "navigate to...", and the Tesla map does so.
The way I talk to Teslaa is to press the microphone button on the Teslaa app on the Tesla screen. I then just say an address and the app recognizes it. Same microphone, different app/process. I could do a 30 second video if this isn't clear.
You are able to get a Google response via the Tesla talk button on the steering wheel? If you turn your phone off, does it revert to the Tesla voice app?
goRt
Active Member
Waze support for coolwalk is in the final stages of testing before release
I can confirm it works
I just installed this yesterday and barely played around with it, but it appears to work pretty well. I love using Waze for road trips, to get traffic/speed trap alerts.
As the audio is going through bluetooth, does anyone notice the typical 2 sec. lag you get? I didn't play with it along enough, but it appears there was a lag. Is there to hardwire it so audio isn't going through bluetooth, or is that the only way to route audio to the Tesla from a phone? Or maybe it's an issue on my end with the bluetooth handshake that is causing the latency/lag.
As the audio is going through bluetooth, does anyone notice the typical 2 sec. lag you get? I didn't play with it along enough, but it appears there was a lag. Is there to hardwire it so audio isn't going through bluetooth, or is that the only way to route audio to the Tesla from a phone? Or maybe it's an issue on my end with the bluetooth handshake that is causing the latency/lag.
After some fiddling around/reboot, your description of how things should work is correct. I can confirm, pressing the microphone button on the steering wheel still initiates the Tesla Voice Command, and Navigate On Autopilot works as it should. If you say "OK Google" it hands over the command to Google Assistant, and you can specify your destination to to Android Auto. Works very well. Android Assistant is definitely more capable in terms of understanding the user requests/destination names.
Thank you
On long journeys I turn blue tooth off on my phone. The Waze navigation instructions come through the phone's speaker.
I have to remember to lock the car myself when I do this. So not perfect but suits my needs.
I wish TeslaAA would put audio through the browser.. it'd make setup much simpler & I could run less on the phone so preserve battery.
There is another project, Home - Tesla Android Project which does audio that way, so it's possible, but that one needs quite an investment in hardware..(can't get Pi4s without paying a scalper these days, and there's the cost of the separate LTE connection..).
There is another project, Home - Tesla Android Project which does audio that way, so it's possible, but that one needs quite an investment in hardware..(can't get Pi4s without paying a scalper these days, and there's the cost of the separate LTE connection..).
Similar threads
