Not sure if this is a feature of AA or a bug/quirk to my implementation. My Xperia (XZ1 Compact) with Oreo 8.0.0 will not sound an SMS alert when Android Auto is running. I turned off DND which was turning on automatically when AA started, but it doesn't make a difference. I thought it might be the Ford Sync 3 system, but after running without the cable I think I have it isolated to just the AA app in the phone. I'm running the Google "Messages" app (comes with the phone) and Lightflow for notifications.
Can anyone confirm one way or the other how this thing is supposed to work?
This is a known bug, Google has been working on a fix for about a month now
Related
Hello everyone! I have been trying to track down a problem with my Galaxy S4 Active that has been driving me nuts for a while. I figured that making a new thread would probably be best because I did not find my particular issue listed.
Basically, what happens is that I will make a call over Bluetooth and everything will be fine. Once this call has ended, all audio related to phone calls dies. The phone still behaves as if it is making and receiving calls, but nobody can hear me and I cannot hear them. Not over Bluetooth, through the earpiece, nor over the loudspeaker. It’s all dead. I also cannot hear it ringing if I dial out, but the phone itself still rings.
I have tried turning the Bluetooth device on and off, disabling Bluetooth and turning it back on, going into Airplane mode and back out again, turning speakerphone on and off, muting and unmuting the call, and muting and unmuting the phone itself. The only thing that fixes this situation is restarting the phone.
I recall this situation first started presenting itself after updating to the ML2 firmware, but it didn’t happen all the time. It became much more apparent after updating to the NE3 firmware. At that point I spent some more time looking into it and became able to readily duplicate the issue.
I have gone so far as to reflash the NE3 firmware with Odin 3.07 to see if the issue remained. Interestingly enough, this appeared to correct the issue until I started updating and reinstalling a few apps. So now I’m trying to track down exactly what did it.
I suspect that it may be the “OK Google” hotword scanning from Google Search because I had it set to detect “From any screen” as well as “From lock screen”. Although I did not have the “Bluetooth headset” setting enabled because I wanted to take that out of the equation. Once I turned off “From any screen”, the Bluetooth appears to be working normally.
Another possibility is that I had frozen S-Voice because it got in the way of the normal voice dialer. This has been restored. I also have to mention that the voice dialer appears to be more stable after disabling “From any screen” as well.
I also can’t say for sure, but it also seems to happen more frequently when charging. Although that may just be a coincidence as I normally do charge my phone when I connect it to Bluetooth. Also I have duplicated the issue when not charging and gotten it to work fine while on the charger. So it is probably just a coincidence.
Here is what I’m working with:
AT&T Galaxy S4 Active (SGH-i537) reflashed back to I537UCUCNE3 Android 4.4.2 stock firmware.
Jabra SP700 - Main device I’m testing with. Old Bluetooth 1.1 speakerphone that clips on a visor. Supports A2DP for an FM transmitter to stream music, but I have Media disabled on it. I tested with and without this setting and it made no difference. It worked great back when I was on MF3, but started having problems since I upgraded to ML2 that are easily replicated now on NE3.
Jabra BT620s - Secondary device that I tested with that also demonstrated the same problems. Although I haven’t tested as much as the SP700. This is a pair of stereo headphones that uses Bluetooth 1.2 and A2DP for streaming music. Also worked better with older firmwares, but I haven’t used it much lately save for testing this problem.
Installed/Updated Programs:
Facebook
Facebook Messenger
Google Authenticator
Google Chrome
Google Maps
Google Play Newsstand
Google Play Services
Google Play Store
Google Search
Google Voice
Google Hangouts
Jift
SuperSU
Titanium Backup
Titanium Backup PRO
towelroot
YouTube
Other apps that I updated and then I rolled back to get things working:
AllShareCase Dongle S/W Update
Amazon Kindle
ANT Radio Service
ANT+ Plugins Service
Antivirus & Security | Lookout
Beaming Service for Samsung
Beats Music
Blurb Checkout
Gmail
Google Drive
Google Play Books
Google Play Games
Google Play Movies
Google Text-to-Speech
Google+
GROUP PLAY
HP Print Service Plugin
Lux
myAT&T
Samsung Link
Samsung Print Service Plugin
Samsung Push Service
Samsung WatchON (Video)
Samsung WatchON (On TV)
YP - Yellow Pages local search
I also tested it quite a bit right before and after rooting it and it was working fine at the time, so I don’t believe that it’s related to root.
I would like to know if anyone else has encountered similar issues or can duplicate what I’m seeing?
Thanks!
After spending some more time testing it, I can verify that it IS in fact the “OK Google” hotword scanning from Google Search 3.6.14.1337016.arm. When it is set to detect “From any screen” and well as “From lock screen”, the audio will die after the first call over Bluetooth. Once I turned off “From any screen”, the Bluetooth works normally.
Now that I've finally found it and can easily replicate it, I'm still curious if other people can replicate it or if this is something isolated to my phone and/or Bluetooth devices. Would anyone be interested in testing this with me?
I'm planning on writing up some feedback on it once I have a better idea of how big an issue it is. I think it would also help anyone else that runs into this problem. I've been fighting with this off and on for over a month because it seemed so random.
Thanks.
I am having the exact same issue with the 2 s4's that I own. I suspected it was either svoice or Ok google, I will try to turn off the from any screen setting and see if it fixes the issue on mine as well. That is a shame because I really like using the ok google feature from any screen.
I've been having the same issue, but did not realize it was ok google from any screen. I've turned it off now, let's see if it works. Thanks for the heads up.
It looks like a recent Google Search update re-enabled the "From any screen" OK Google hotword detection setting. This still is not fixed and it killed all call audio while I was trying to lead another vehicle. I didn't find out until I parked that it was turned back on.
I have sent feedback to Google on the Search app and recommend that everyone else who has had this problem do the same. If this continues to happen, I will resort to negative reviews if I must. Please help get the word out if you are having the same issue. Thanks!
EDIT:
There are apparently several other people having the same problem on other Samsung devices (particularly Galaxy S4's):
https://productforums.google.com/forum/#!msg/websearch/mEhHyCs6F5o/HVArojlzIrAJ
http://forums.androidcentral.com/sa...-sound-phone-calls-after-using-bluetooth.html
I wonder if anyone can help me with an issue I'm having with Android Auto which is driving me nuts !
I have a Sony Xperia Z3 Compact, with AA installed. This is connected to the screen on my Mercedes via the USB connection. So far, so good ! I can use Google Maps, Spotify & Audible, as well as make calls. The recent update to allow for "OK Google" commands enhances things even further.
However....
Whenever I receive an SMS message when AA is active (I am using SimplyText, v5.94), it sets off the ringtone I have for calls. Frustratingly, the ringtone continues once I listen to the message. Indeed, it continues until I reboot the phone, which is very frustrating !!
Is anyone aware of why this might be the case and whether any of the settings, either on the 'phone or the APP itself, could address this issue*
Any help would be greatly appreciated.
Hello,
Today I installed the SONY XAV-AX100. Super. Everything works quite smoothly. I just have a problem with calling through android car. If someone calls me or call me and I connected via android car, so the call does not appear on the radio display only phone which is useless.
When I tested the Nexus 4 with Android CyanogenMod v6, it works well.
Some idea?
matata86 said:
Hello,
Today I installed the SONY XAV-AX100. Super. Everything works quite smoothly. I just have a problem with calling through android car. If someone calls me or call me and I connected via android car, so the call does not appear on the radio display only phone which is useless.
When I tested the Nexus 4 with Android CyanogenMod v6, it works well.
Some idea?
Click to expand...
Click to collapse
Firstly double check your bluetooth settings for that device and make sure all the sliders related to phone calls and Bluetooth audio are enabled, if that doesn't work - try a variation of making your head unit connect to the device and vice versa.
I have a 2014 passat and the Bluetooth works perfectly when connected, first connection on car start is a bit pissy because my smartwatch initially demands all Bluetooth, manually connecting to the VW Phone in Bluetooth just reconnects both devices and it works fine for calling, music and voice control.
If these tips don't work, It might sadly be a lack of support within the head unit itself (some are very picky)
@stevob21
You don't have AA and don't understand the problem, so why did you respond? It's not BT related issue.
@matata86
I have the same problem. AA has all needed permissions, but calls still not show on the unit. Interesting is that with my previous phone, P9 - it was working as long phone has Android 6.0. After update to 7.0 - it has stopped working. So it has to be related with Huawei's 7.0 phone manager. Someone with root access should try to freeze phone manager and check it...
mr.mrcn said:
@stevob21
You don't have AA and don't understand the problem, so why did you respond? It's not BT related issue.
@matata86
I have the same problem. AA has all needed permissions, but calls still not show on the unit. Interesting is that with my previous phone, P9 - it was working as long phone has Android 6.0. After update to 7.0 - it has stopped working. So it has to be related with Huawei's 7.0 phone manager. Someone with root access should try to freeze phone manager and check it...
Click to expand...
Click to collapse
Yeah apologies, I must have got this mixed with another thread I was looking at when writing this related to BT issues when connecting where phone calls/address books aren't operable though they work fine after manually initiating the connection.
Same problem here. I can make calls with "ok google, call John Smith" but the notification doesn't show in order for me to end the call. I can end the call from the phone but usually rely on the other party to end the call from their phone.
Text messaging has similar behavior. I can send text messages from AA using voice commands but cannot receive them on screen nor are they read back to me. Again, they do show up on the phone.
All notifications are allowed for the phone and messaging apps. I've also set the battery manager to NOT turn off those apps to save power during screen off. I've tried other phone apps, though I didn't think this should matter but why not try
The deck is a JVC KW-V930BW and the phone is a P10 plus. All other Android Auto features seem to function correctly. I read in a forum for some other phone brand that exhibits the same behavior that it is due to some security feature in that phone and cannot be changed. I wonder if that is the case with the P10 plus?
Anyone else run into this or have a fix? Thanks all!
PS: not interested in rooting.
follow-up
From a thread in another forum, this appears to be an android auto/huawei compatibility issue that they're working on. A recent update seems to have fixed an sms issue so now text messages are read back to me. Regarding the phone notifications, I've mounted the phone using a magnetic vent mount close the steering wheel so I can end calls easily from the phone itself. I'm going to call that "good enough"
It seems to working now with B171, at least in my A6 from 2015 with the latest MMI-Update.
LwannaCM said:
It seems to working now with B171, at least in my A6 from 2015 with the latest MMI-Update.
Click to expand...
Click to collapse
All of a sudden mine is working too, though still on B170. The only thing that changed that I can recall is I updated Google Messages and was prompted whether I wanted to make it my default messaging app to which I agreed.
I've been posting regularly in Google Android Auto forums, but nothing has been happening. I thought maybe someone here would be of more help.
I use Android Auto (just updated again today, version 4.2.591444-release) on my OnePlus 5 (Android 9, OxygenOS Beta 30) with a Bluetooth FM Transmitter in my car. Same setup as I've had for a while (apart from updates to the OS or the app, of course.)
There are three issues here.
1. The hotword doesn't trigger anything to happen. Sometimes it does right after an uninstall/reinstall, but once and only once and only if it's not connected to my FM transmitter via Bluetooth. I have tried uninstall/reinstall, deleting and retraining my voice model, giving AA every permission it asks for. The hotwords trigger with no problem when it's not in AA mode.
2. AA auto triggers Do Not Disturb mode. This means it doesn't give any audible notification for phone calls/texts/hangouts/weather alerts/job notifications. Doesn't matter what the app is, it doesn't trigger. I only know I'm getting a call if I happen to look at my phone. I can go in and manually turn off DND mode, but I have to touch "turn off" twice every time for it to work.
3. It's set to autolaunch when it connects to my FM transmitter. It often doesn't. It pairs to my transmitter with no problem, but doesn't launch. The AA icon is in my notification shade, but when I pull it down, it's saying that it's launching with the little progress bar. I have to actually launch it myself.
All of these issues are new within the last few months. Before all of this, I'd jump in to take kids to school, my phone would autoconnect to my transmitter, and the kids would proceed to ask Google to play their favorite songs. Awesome. Sometimes I'd get a notification that a job was available (I'm a substitute teacher) and I could accept it. Now...none of this happens.
Any thoughts you all have? I've not seen threads here describing this issue, but in Google's forums, it seems to be happening both with head units and the app, no matter what kind of phone/auto combo it is.
I have the same issues (2 & 3) and I'm pissed
Hi,
I have VW Passat with AA (MIB3 based system). Android Auto works in general, but there is a problem with applications like ReplaIO, Spotify and sometimes even TuneIn.
Those start to stream audio "into nowhere". The sound volume control does not work then either from the panel or from the steering wheel. What I do to enable sound?
I need to run ANY Google based app, like Youtube or Youtube Music/Google Play Music, then stop it and switch to another app. Then it plays correctly, with sound.
Anyone got same behaviour in the car? What is the reason? Any workaround? This is not happening when same phone plays via Bluetooth, there is always the sound.
Only via AA connection, there is a problem. Later, after my manual workaround as above, switching the sources (FM/DAB/BT/AA) works correctly.
But if I disconnect the USB cable and connect it again... no sound from AA
Please help.
As far as I know, this is an ongoing bug. To reenable audio when the bug occurs you can simply dial to some phone number (best and easiest is if you call a number with an automatic answering machine), wait for the answer and then disconnect the call. Immediately you will get the sound back. In my car, when it happens, there is no sound at all, in any app, the only way is dialing.
Sent from my SM-N975F using Tapatalk
uhi711 said:
As far as I know, this is an ongoing bug. To reenable audio when the bug occurs you can simply dial to some phone number (best and easiest is if you call a number with an automatic answering machine), wait for the answer and then disconnect the call. Immediately you will get the sound back. In my car, when it happens, there is no sound at all, in any app, the only way is dialing.
Sent from my SM-N975F using Tapatalk
Click to expand...
Click to collapse
Similar problem: support.google.com/androidauto/thread/66269926?hl=en - add http
Well, for sure the problem exists, but it seems we need to live with that. No fix until now from Google. I wonder if this is related to Android 10, have anyone tried that with earlier versions?
In my case (just tested), the phone call does not fix that. The only way for me is to play some song from Youtube Music, pause that and switch to Spotify, for example. Then it plays normally.
I suspect this bug is related to sound focus/sound routing/mixer.
This bug is related to AA only and it is happening in Android 9 also, maybe not everyday, but from time to time. I have a Note 10+ with Android 9 and a Peugeot 3008. In my case, the trigger is, almost always, the lack of internet connection in my underground parking. If the phone is connected to my car's display through AA, and if I try to play internet music (spotify or other internet radio app) before I get out from the parking and before my phone gets connected to the internet, then the music app gets stucked and the sound from any app disappears. Only making a phone call and waiting for somebody to respond or restarting the phone does help.
Sent from my SM-N975F using Tapatalk