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
Hi All,
I've been extremely excited about the integration of my smartphone with my car for a while. Almost anyone who would be in the market for a motor vehicle with an advanced head unit would also already own a smartphone with data access.
However, like any new use of technology, there are growing pains and Android Auto is no different. I have struggled through a few issues already and continue to grapple with others. A huge difficulty I had was simply finding discussion threads. Do I look on sites that focus on cars? On Android Auto? On Android OS?
So here it is. I'm starting a thread to pull together the most common problems and their solutions. Also, please note - I am not an expert in any of these things, just a user. I will give credit where I have a source but I am just gathering the info into one place and adding it to my own observations.
I haven't decided how this thread is going to look or if it will be small or big, so I will save the first few message placeholders in case and I will add known problems, work-arounds, and identified solutions as they come.
Hopefully this helps out some other users!
Troubleshooting:
I strongly suggest you make sure you have a good quality USB cable and confirm that you are able to connect your phone to your computer and transfer a file (some cables will allow charging but not data transfer).
1. Problem: Bluetooth won't pair, won't connect, etc.
Possible Solution:
It appears that Android Auto will attempt to create a BT profile. So
a) Delete the pairing on your cell phone
b) Delete the pairing on your car head unit
c) Turn OFF bluetooth on your phone
d) Plug your phone into your car's head unit. Depending on your settings, you may need to tell your car to launch Android Auto and you may need to select the device. If so, make sure you are selecting it in Android Auto (NOT Bluetooth pairing). Respond appropriately to any requests for authorization on your phone and car.
This should leave you with a properly paired device and car.
2. Problem: Every time I launch Android Auto, I have to pair my phone again!
Work-around: Once you have a working AA connection between the car and your device, go into the settings in the Android Auto app on your device and turn off the option to "Add new cars to Android Auto."
3. Problem: Android Auto notifies me of a new message but won't read it out loud/but starts to read it and cuts off.
It looks like there is a conflict between Google Now, Android Auto, and the Bluetooth handoff with the car head unit. Kudos to XDA member BuildaWall for discovering that turning off the BT headset option in Google Now fixed it for some people. I did a little more testing and found that forcing Android Auto to make your phone the primary source of audio seems to be the other piece.
UPDATE:I applied the August CM-13 Snapshot and this workaround no longer fixes the problem. I have reheaded it as a possible work-around as it might fix the issue for people on slightly older ROMs
UPDATE Sept 27/2016: I have upgraded to stock Nougat (Android 7). This issue still exists. However, after reading this XDA article, I tested an accessibility option. AA began reading the messages once again.
Possible Work-arounds:
A) Several people reported that their Media volume on their phone was being changed to zero when they plugged into AA. Some also reported that turning USB Debugging OFF fixed this issue. If you don't know what USB debugging is, don't worry about it; you would have to have intentionally turned it on. For volume, tap your volume rocker but then tap the drop down on the pop up volume notification.. It will expand to multiple volume sliders. For simplicity, make sure none are zero.
B) On your phone, go into Google Now, Options, Settings, Voice and then turn off Bluetooth Headset. This was reported to help by some but not didn't help for me.
C) On your car's head unit, in Android Auto, select a music option (I have Spotify and Google Play Music, but I think any audio source app within AA will work). If you don't want to listen to anything, just play and then pause/stop it but you CANNOT go back to the car as a primary source (eg radio or sirusXM).
D) On Nougat (Android 7) go to settings, accessibility, and enable one of the options (I have tested Voice Access, but in theory, activating any accessibility option should reactivate the message reading in AA.
4. Reported with work-around by @ReppinTheSouth - Android auto either being laggy or flat-out disconnecting
ReppinTheSouth observed this on a Pioneer avh 4100 and a galaxy s4 and reported August 7, 2016
Suggested Work-Around: Clearing the phone's cache periodically seems to help a lot. I also added a swap file which has seemed to help even more.
5. Reported by @ReppinTheSouth - When driving in maps with voice commands enabled, it will freeze sometimes right when a voice command is about to come on. My GPS will no longer track and my head unit at least an Android auto is completely unresponsive.
I'm not listing this as a work-around, as it doesn't resolve the problem, but is still good to know: @ReppinTheSouth advises: This only happens when voice commands are enabled & Unplugging and replugging the phone gets the head unit out of its frozen state.
More to come!
Tips and Tricks:
I will use this page to list tips to improve performance or usability that don't fit under troubleshooting.
1. Keeping the phone screen alive and accessible.
Please exercise safe driving habits.
TL; DR:
Turn on Developer options
Turn on Stay Awake
Optional: if you have a security lock you may want to add your car Bluetooth as a trusted device for smart lock so it doesn't lock you out.
Details:
Android Auto changes your screen timeout to 15 seconds every time it is activated. When combined with its flaws with hangouts chat notification (no groups, can't initiate a new chat without certain contact book entries, can't access chats that began before connecting to AA) it is VERY frustrating.
Access the Developer Options menu
Settings >>> About Phone
Scroll to the bottom and tap the Build Number option seven times in a row. You will get some sort of message saying you have access to developer options. You only need to do this once.
Settings >>> Developer Options
Make sure they are turned on. Next turn on the Stay Awake option.
Your phone will now allow dimming but won't turn off the display.
Optional:
If you use a security lock on your device, you may want to authorize your car Bluetooth connection as a trusted device under smart lock so it won't lock while connected.
==============================
Links to Other Resources:
https://forums.oneplus.net/threads/...to-connected-to-the-cara-infotainment.488786/
Thanks for this thread Mad Medik.
However, I also have the same problem as number 3, but the workaround doesn't work.... I changed my phone Bluetooth Headset setting to off and I was playing my spotify music through Android Auto. Am I forgetting something here? what versions of AA and Whatsapp do you use?
Good thread and it is much needed as far as I am concerned. I have a Pioneer avh 4100 and a galaxy s4. One of the issues I have had is with Android auto either being laggy or flat-out disconnecting for no reason. One of the things I have noticed is Android auto seems to be a resource hog. Clearing the phone's cache periodically seems to help a lot. I also added a swap file which has seemed to help even more.
The other issue I'm having which I can't solve is when driving in maps with voice commands enabled, it will freeze sometimes right when a voice command is about to come on. My GPS will no longer track and my head unit at least an Android auto is completely unresponsive. I have to unplug my phone and then plug it back up to get it to work. This only happens when voice commands are enabled. I have not been able to resolve this issue.
Sent from my SPH-L720T using XDA-Developers mobile app
NLatuny said:
Thanks for this thread Mad Medik.
However, I also have the same problem as number 3, but the workaround doesn't work
Click to expand...
Click to collapse
Hi NLatuny & ReppinTheSouth!
@NLatuny - Thanks for the info. I just updated my Nexus 6p to the latest (august 2016) CM13 Snapshot, and the work-around no longer fixes the problem for me either. I've updated the original post. I think your request for version numbers is probably a good idea moving forward. I will update the original post to suggest that people include that in their posts.
@ReppinTheSouth - Thanks! I will look at adding those problems and your possible solutions for the lag to the top of the thread
Might be good to add a list of things you can and cannot do. For example, I found the other day through just trying you could ask various questions.
How old is (enter famous person here). = Correct answer.
I need to remember some of the other ones I've done. Good thread.
---------- Post added at 10:42 AM ---------- Previous post was at 10:40 AM ----------
Perhaps also add how to get into Developer Mode, and what the settings in there do? The Force Day or Night mode thing is super useful.
I am not sure if this is the righjt place to ask, but I have been everywhere with no answer.
I Have a Galaxy s7 edge in a Mercedes a class. It connects just fine, but I cannot make calls saying "call >name>". Maps, Music, weather works just fine, but when I try to make a call, the woman just replies "not sure how to help you with "call..."". I can dial numbers as well BTW.
Making calls through Google Now works fine as well.
Any help would be much apiciated.
duze76 said:
I am not sure if this is the righjt place to ask, but I have been everywhere with no answer.
I Have a Galaxy s7 edge in a Mercedes a class. It connects just fine, but I cannot make calls saying "call >name>". Maps, Music, weather works just fine, but when I try to make a call, the woman just replies "not sure how to help you with "call..."". I can dial numbers as well BTW.
Making calls through Google Now works fine as well.
Any help would be much apiciated.
Click to expand...
Click to collapse
Check your permissions for Android Auto, you may have missed a few.
You can also uninstall and reinstall it.
I have tried all that, with no luck unfortunately
Having had a courtesy car for a few days that had an android auto system in I'm looking to purchase an android auto headunit for my car, probably after Christmas.
Until then I've been using my handsets connected to the aux input on my factory system. However since I got my Pixel handset last week I've encountered a couple of issues that weren't an issue on my m9 handset previously. I've reported then to the relevant support sites but as yet have received no response, so thought I would try you knowledgeable lot.
Firstly, when making or recurving phone calls with the aux cable connected the Pixel defaults to using the loudspeaker on the handset rather than putting through the aux to my car speakers.
Secondly, when receiving a message on WhatsApp i touch the screen too get it to read the message, it does so fine, then tells me I can press the mic soon symbol and say reply. When I do so I'm told "this chat app is not installed or needs an update". The app is installed and is up to date. I can send WhatsApp messages by saying "send a WhatsApp message to...." but can't reply.
Lastly, when I ask it to play specific tracks on Spotify it often comes back with no search results. Songs that I used to ask it to play regularly on my previous device come back as no search results found. Searching manually the tracks are there and can be played. And it isn't all tracks, some tracks are found without issue.
Thanks in advance.
Also hope this is in the right thread, I notice you seem to be taking mainly about the in car systems but as it can now be used on most android phones without a dedicated in car system I figured many would be doing so.
Hi folks, sorry for the absence. My N6P died on me in November and was sent away for warranty repair. Long story short, I'm very disappointed with Huawei and futuretel. Two months later, the process ended with me owning an unfixed Nexus 6P which is still under warranty until February 2017. It has a defective motherboard according the repair center but they will not repair it. So, after 2 months of making do with an iPhone 6 with a broken screen (wife's old phone), I have moved on to a One Plus 3T.
Irritatingly, Apple Carplay worked flawlessly for that time. Typical of Apple it was very locked down and had limited options. But in fairness, it executed those few features very well. Come on Google!
[/end rant]
I'm back and will try to get the thread up to date.
MM
Sent from my ONEPLUS A3000 using Tapatalk
Hello, thank you very much for this information, is very useful.
In my case, I have a Le Pro 3 X720 and is nightmare with AA, when I plug the phone on my Hyundai car the phone only charge so I had to change their ROM to lineage is 14.1 (Android 7.1.2) and with this AA starts quickly but after 5 minutes the screen is freeze then change the cable but it doesn't work, I change the cable again with the same result, so I back to use the original leeco cable and change their ROM again, with the same result, after 5 minutes the screen is freeze, the last one is AICP 12.1 (Android 7.1.2).
Do you know how to fix this?
Thank you in advance for your response.
Hello everyone,
i found this thread and i hope that is the correct one for my problem.
In the first page i read that AA set the screen timeout to 15sec when activate, but in my case, the timeout remain also after when i unplug the phone from my car.
If i manually set the timeout to 5 minutes, after the first screen lock, it return to 15sec and this is so frustrating.
So i tried to set the stay awke mode in the developer options, but i see that the description of this setting is "when is on charge" (i'm italian, i don't know the english description, sorry), there is some walkaround to fix the 15sec also after the unplug ?
Thanks in advance
mikefavro said:
Hello everyone,
i found this thread and i hope that is the correct one for my problem.
In the first page i read that AA set the screen timeout to 15sec when activate, but in my case, the timeout remain also after when i unplug the phone from my car.
If i manually set the timeout to 5 minutes, after the first screen lock, it return to 15sec and this is so frustrating.
So i tried to set the stay awke mode in the developer options, but i see that the description of this setting is "when is on charge" (i'm italian, i don't know the english description, sorry), there is some walkaround to fix the 15sec also after the unplug ?
Thanks in advance
Click to expand...
Click to collapse
Hi Mike,
You should say what phone and android version you are using. I have used both a One Plus 3T on Oreo beta and an LG V30 on 7.1.2.
The screen timeout sets to 15 sec when I plug in, but returns to normal when I unplug.
Sent from my LG-H933 using Tapatalk
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'm having issues with the audio when using Android Auto. I'm connected through a OEM usb cable to the car
it also appears to connect via bluetooth.
When I connect my phone to the car Ford Explorer 2017, or other 2017 models everything appears to work fine, I can use google now and ask questions, I can request to play a song. But when I ask to call someone it calls but then I can't hear an audio from the call, and the other person can't really hear me.
Sometimes it seems like it works but most of the time it doesn't. If it I reboot the phone and the car audio it works fine for a call if I don't do anything else. But If I play a song, and then trying making a call that's when I seem to have issues. Any ideas as to why this is?
I've searched the forums seems like people have similar issues but no one seemed to have any answers. I've checked the bluetooth profile and enabled all profiles, I've enabled all Android Auto App permissions.
I have a Google Pixel with Pure Nexus installed with Android 7.1.2 with the latest Android Auto app installed.
Any help would be greatly appreciated!
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