Hi all,
I'm trying to understand if this is REALLY happening...
It would appear that BMW is blocking audio from my maps apps (google maps, waze, etc). I can connect my Samsung Note 4 to my BMW, play music over bluetooth, receive calls over bluetooth, but if I turn on google maps, audio turn by turn will NOT play back.
Has anyone else experienced this behavior? Is there a trick to get this working?
Thanks,
RR
Related
I use SVOX to drive using Google Navigation, because the Android default engine does not support portuguese. It's been working fine since yesterday, appearently after I installed Waze. For some reason, I can no longer hear the streets names using Google Navigation. Only "turn left", "turn right" and stuffs like that.
I uninstalled Waze, but the issue keeps on. The SVOX TTS app is working fine, because I can test it by clicking the "Listen to Sample" in Android Settings.
My device is a Galaxy Nexus running 4.2.1 stock ROM. Any ideas to solve the problem?
I adore the new keyboard functionality of 2.0, but in general my watch has been behaving poorly since the update. I have it paired to a Huawei mediapad m3 8.4 (cellular version)
At all times, notifications seem to come through in a timely fashion. But anything that requires an Internet connection (specifically Google Assistant, voice replies to notifications, and weather) are hit or miss. Half the time they work just fine. Other times they don't.
I've factory reset the watch since the update, with no improvement. Again, at all times notifications come through. But sometimes, anything that requires voice dictation or data fails. At these times, I go into the Android wear app, and it says connected. I can see and even reply to notifications with the keyboard, but if I try to use voice, or the assistant, or query for a weather update, it will tell me disconnected, or couldn't reach Google. Play store updates on watch apps are the same problem.
When I go into the watch settings while observing this bad behavior, under Bluetooth settings, it shows my phones Bluetooth ID, and says disconnected. When it's working properly, it says connected. But in BOTH cases it properly receives notifications, so just the Internet sharing to the watch from the phone seems at issue.
I've done everything short of factory resetting my phone, which I'd rather not do, including clearing data from Google app and clearing data /Uninstalling /reinstalling Android wear on the phone. Does anyone have further suggestions?
Screenshots for reference
https://flic.kr/p/UCzYGL
Weather app
https://flic.kr/p/TpK7s1
https://flic.kr/p/TsD85r
https://flic.kr/p/TpKcvY
Edit: just on a whim, I decided to try Shazam on the watch while assistant, weather, and voice were not working. Even in the "disconnected" state, it could properly identify music. Baffling. Though if Shazam on wear just records the audio, sends it to the phone, and that does the identification, I suppose this follows logic. Still sort of feel like it's specific to Google though.
Before my phone updated from 8.0 to 8.1 Google Assistant would open Deezer, which is the music streaming service I use. Now it refuses to and I can't re-set it to do so, as I only get the choice of Google Play Music or Spotify. Is this down to Google or Deezer?
I've had this odd bug every now and then in which my phone automatically dials itself when it connects to the car. You didn't always know it until you tried to play music or something "Hey Google" related and you had no audio feedback.
This would only happen once every few weeks so it wasn't something I was always watching for. It happened again today and found it is related to Google Voice.
If Google Voice is open and in focus/being used when connecting to vehicle Bluetooth the phone will dial itself. It Google Voice is running in the background or opened after the connection three problem doesn't occur
Can anyone that uses Google Voice have the app open and in focus when it connects to your vehicle and see if you get the same self-dialing error?
cahiatt said:
I've had this odd bug every now and then in which my phone automatically dials itself when it connects to the car. You didn't always know it until you tried to play music or something "Hey Google" related and you had no audio feedback.
This would only happen once every few weeks so it wasn't something I was always watching for. It happened again today and found it is related to Google Voice.
If Google Voice is open and in focus/being used when connecting to vehicle Bluetooth the phone will dial itself. It Google Voice is running in the background or opened after the connection three problem doesn't occur
Can anyone that uses Google Voice have the app open and in focus when it connects to your vehicle and see if you get the same self-dialing error?
Click to expand...
Click to collapse
I get this at least once a week. At first it freaked me out until I realized that it wasn't really making a call. Now I ignore it. I didn't realize it was related to the app being open.
I almost going crazy here, but if anyone here is using Google assistant and YouTube music on a note 10 can someone confirm if you experience this behaviour.
I use the band muse as an example.
Firstly make sure YouTube music is the default music provider for Google assistant.
While the phone is unlocked ask "hey Google, play muse" and Google assistant try to play in Google music, not YouTube music.
Then try to lock the phone and say the exactly same thing, and it works and play in YouTube music.
Anyone have any idea how this can happen that Google assistant works when the phone is locked or on lock screen, but when unlocked it does not respect the provider.
Tried with Spotify too and same issue
Update: it's a bug, but to solve it, go into Google music and deauthorize all phones, then uninstall Google music. You need to deauthorize the phones before uninstall or Google assistant want to reinstall Google music
i also have same issue. it doesn't hear me sometime .
i can't using it when screen is locked.