Related
Hello,
I have an ongoing annoyance with my G1, and was wondering if anyone knew a workaround. I have a Motorola S705 bluetooth device. It's basically a little rechargeable dongle that lets me use regular headphones and walk around. It also has a built-in mic so it can work for accepting phone calls, which is retarded because it stays clipped to my belt.
I really only want it to ever take over media-playing functions and nothing else. I have a rooted G1 running Cyanogen's latest. Is there a config file or something I can edit and force the phone to never ever ever (ever) use the phone-headset bluetooth profile and only connect via the stereo media profile?
When I set it to only use the media profile via the GUI, it obeys these settings for a little while, but for no apparent reason it will occasionally revert back to defaulting to the phone profile when connected, and I have to go back in and uncheck the phone box, check the media box, reconnect, etc.
Thanks!
Alternatively, since I have no desire to use a bluetooth headset, is there a way to just disable that profile entirely?
I searched this forum and didn’t see any posts related to this issue directly, please direct me to any existing threads if I may have missed them. Sorry for the length of post, but I wanted to be as detailed as possible to fully explain the issue.
I am having some issues with the Bluetooth connections that I use in my car. I had this setup working previously on my Droid Razr Maxx with no issues, and was really hoping it would carry over to my Moto X.
I use Tasker in my car and have several profiles setup based on my Bluetooth connection state. When I enter my car, I connect to my General Motors Bluetooth for hands free calling. This connection works without issue. I also have a small USB powered Bluetooth audio receiver that converts the Bluetooth stream to a 3.5mm cable and goes into the radio deck for audio. It was a pretty cheap dongle that I got on eBay. It doesn’t have a brand name on it, but it comes up in my phone as “dmzmusic”. I’ve never had any major issues with it before, other than on occasion it fails to turn on when the car starts, but shutting the car off and turning it back on again works fine.
Last week I had my phone in a basically stock 4.4 state. Not rooted, nothing changed, etc. When I would get in the car, General Motors Bluetooth connected just fine. I did not happen to take any phone calls last week, so I’m not sure about how well that was working. I’ll get to this in a minute. My other connection for dmzmusic seemed to connect and then very quickly disconnect. This was evidenced by my Tasker profile launching Pandora, which it is supposed to do when it connects to dmzmusic. However, Pandora immediately exited again, and when I went to the Bluetooth settings, only General Motors was connected. If I tapped on dmzmusic in the list of paired devices, it connected and worked fine.
Over the weekend I rooted my Moto X with SlapMyMoto, which was quite a long process, but in the end, I was rooted and all was well. This morning, I got in my car and re-paired both devices mentioned above. When the Tasker profile fired for dmzmusic, I watched it launch Pandora, and then close it within a few seconds (there is an exit task to kill Pandora). It did this cycle three times, and then apparently stopped trying. As with before, I tapped on the connection and it worked fine. It launched Pandora, music played my whole way to work, and Pandora was killed when I arrived at work.
Now, back to the General Motors issue. Today when I was driving to work in the lovely Minnesota weather, my boss called to see where I was. My music paused, but my radio deck did not show an incoming call on the screen. I pressed the hands-free answer button, but it didn’t work. I picked up the phone and swiped right to answer, but it didn’t come through on Bluetooth. So I started talking on the handset, and after about 30 seconds, it connected to the radio and hands-free worked. When I was done with the call Pandora and music resumed, as it should.
So my question is, has anyone else had any issues with hands free Bluetooth, and/or any issues when using a hands-free device AND a media only device? In the Bluetooth settings, my General Motors connection only has the option for phone. The dmzmusic device has phone and media, but I have unchecked phone so it’s set to media only, if that makes any difference.
I know it’s a somewhat unique situation, but it’s really annoying that it doesn’t work. Tonight I am going to test having a few seconds delay on the Pandora task to see if that helps the repeat cycle that it did this morning.
Thanks!
fury683 said:
I searched this forum and didn’t see any posts related to this issue directly, please direct me to any existing threads if I may have missed them. Sorry for the length of post, but I wanted to be as detailed as possible to fully explain the issue.
I am having some issues with the Bluetooth connections that I use in my car. I had this setup working previously on my Droid Razr Maxx with no issues, and was really hoping it would carry over to my Moto X.
I use Tasker in my car and have several profiles setup based on my Bluetooth connection state. When I enter my car, I connect to my General Motors Bluetooth for hands free calling. This connection works without issue. I also have a small USB powered Bluetooth audio receiver that converts the Bluetooth stream to a 3.5mm cable and goes into the radio deck for audio. It was a pretty cheap dongle that I got on eBay. It doesn’t have a brand name on it, but it comes up in my phone as “dmzmusic”. I’ve never had any major issues with it before, other than on occasion it fails to turn on when the car starts, but shutting the car off and turning it back on again works fine.
Last week I had my phone in a basically stock 4.4 state. Not rooted, nothing changed, etc. When I would get in the car, General Motors Bluetooth connected just fine. I did not happen to take any phone calls last week, so I’m not sure about how well that was working. I’ll get to this in a minute. My other connection for dmzmusic seemed to connect and then very quickly disconnect. This was evidenced by my Tasker profile launching Pandora, which it is supposed to do when it connects to dmzmusic. However, Pandora immediately exited again, and when I went to the Bluetooth settings, only General Motors was connected. If I tapped on dmzmusic in the list of paired devices, it connected and worked fine.
Over the weekend I rooted my Moto X with SlapMyMoto, which was quite a long process, but in the end, I was rooted and all was well. This morning, I got in my car and re-paired both devices mentioned above. When the Tasker profile fired for dmzmusic, I watched it launch Pandora, and then close it within a few seconds (there is an exit task to kill Pandora). It did this cycle three times, and then apparently stopped trying. As with before, I tapped on the connection and it worked fine. It launched Pandora, music played my whole way to work, and Pandora was killed when I arrived at work.
Now, back to the General Motors issue. Today when I was driving to work in the lovely Minnesota weather, my boss called to see where I was. My music paused, but my radio deck did not show an incoming call on the screen. I pressed the hands-free answer button, but it didn’t work. I picked up the phone and swiped right to answer, but it didn’t come through on Bluetooth. So I started talking on the handset, and after about 30 seconds, it connected to the radio and hands-free worked. When I was done with the call Pandora and music resumed, as it should.
So my question is, has anyone else had any issues with hands free Bluetooth, and/or any issues when using a hands-free device AND a media only device? In the Bluetooth settings, my General Motors connection only has the option for phone. The dmzmusic device has phone and media, but I have unchecked phone so it’s set to media only, if that makes any difference.
I know it’s a somewhat unique situation, but it’s really annoying that it doesn’t work. Tonight I am going to test having a few seconds delay on the Pandora task to see if that helps the repeat cycle that it did this morning.
Thanks!
Click to expand...
Click to collapse
Yup... My Dev GSM Moto X on 4.2.2 connected just fine to my Mazda for both Phone and A2DP everytime I entered or exited the car. With 4.4, I'd have to manually go into Bluetooth and have the phone connect to the car. Very annoying... Haven't had that happen since ICS days.. Might have to downgrade to 4.2.2 again just to make this go away.
Bluetooth working fine on 4.4 with my Hyundai Elantra. Phone and A2DP. Maybe try repairing?
totempole said:
Yup... My Dev GSM Moto X on 4.2.2 connected just fine to my Mazda for both Phone and A2DP everytime I entered or exited the car. With 4.4, I'd have to manually go into Bluetooth and have the phone connect to the car. Very annoying... Haven't had that happen since ICS days.. Might have to downgrade to 4.2.2 again just to make this go away.
Click to expand...
Click to collapse
Thanks. I wasn't able to test it on 4.2.2 (it took right away OTA out of the box) with my Moto X, but it was working fine on my Droid Razr Maxx on 4.1.2 Jelly Bean before I got the Moto X.
I will have to try and see how it works with just the A2DP device without the handsfree. I rarely ever talk on the phone, and with the Touchless Controls I could call people and just pick up the phone. Or turn the phone portion back on for the A2DP device so the sound would come through my speakers but I'd still have to use the mic on my phone...
Still annoying. Thanks again for the reply.
gtg465x said:
Bluetooth working fine on 4.4 with my Hyundai Elantra. Phone and A2DP. Maybe try repairing?
Click to expand...
Click to collapse
Both pair automatically together when you enter the car?
I can get them to coexist, but I have to manually add the A2DP device. The car radio (General Motors) connects fine, but the A2DP cycles and then gives up, it seems.
I will try pairing them in a different order, and temporarily disabling or adding a wait clause to my Tasker profile to see if it works without that.
Thanks,
I have a Dension BT gateway for my car that provides BT audio and hands free. My phone connects automatically as long is bluetooth is turned on. I also connect to a BT OBD2 adapter sometimes, and I tried it today, and I kept playing Pandora via BT and also connected to the OBD2 adapter and had data going from both of them.
fury683 said:
Both pair automatically together when you enter the car?
I can get them to coexist, but I have to manually add the A2DP device. The car radio (General Motors) connects fine, but the A2DP cycles and then gives up, it seems.
I will try pairing them in a different order, and temporarily disabling or adding a wait clause to my Tasker profile to see if it works without that.
Thanks,
Click to expand...
Click to collapse
Yeah, but they aren't a separate connection I don't think. Pretty sure the one connection handles both.
Seems to be an issue with the A2DP device specifically. I unpaired my car and the dmzmusic device and repaired them both, same result. I added just the dmzmusic, and got the same thing.
I changed my Tasker profile to just flash a toast message to show it connecting and disconnecting instead of firing Pandora to see if that mattered and it didn't. I did not try disabling the Tasker actions entirely to see if that worked.
I have a pair of Bluetooth headphones at home that I may try as well to see if it will connect to those. They fire the same task as the dmzmusic does to launch Pandora when they connect, and kill it when they disconnect.
Hoping this gets fixed, because it's VERY annoying.
Is it possible to submit this to Google/Moto as a bug if it is a larger problem with all A2DP devices?
But it's not a problem with all A2DP devices. Works fine with both my 2013 Hyundai Elantra and my Jaybird Freedom buds.
gtg465x said:
But it's not a problem with all A2DP devices. Works fine with both my 2013 Hyundai Elantra and my Jaybird Freedom buds.
Click to expand...
Click to collapse
Thanks. I will try it with the Philips bluetooth headphones as well. The device in my car is pretty cheap. I don't know what version of Bluetooth it has, but it was only about $5. Anyone know of a similar device that can receive a Bluetooth audio signal and convert it to 3.5mm, and is powered by USB?
totempole said:
Yup... My Dev GSM Moto X on 4.2.2 connected just fine to my Mazda for both Phone and A2DP everytime I entered or exited the car. With 4.4, I'd have to manually go into Bluetooth and have the phone connect to the car. Very annoying... Haven't had that happen since ICS days.. Might have to downgrade to 4.2.2 again just to make this go away.
Click to expand...
Click to collapse
Well I sort of solved this. There's an app in the Play Store called Bluetooth Auto Connect. This can connect to bluetooth devices with a set of conditions and states, and works as a plug-in to Tasker. I told it to connect to dmzmusic upon connection to any other bluetooth device (in this case, my General Motors hands free). Worked perfectly. Thought you'd like to try it out for your dual device setup.
However, I also have a new issue. It seems the reason my phone call wasn't on bluetooth at first was due to some sort of connection issue with the General Motors unit. While driving home tonight, every few minutes my car radio said Connected. And every time I turned the car screen on to thumb up a song on Pandora, it flashed Connected to a trusted device. Which implied to me that it was disconnecting periodically. No idea why it would do this. Didn't see any setting for it in bluetooth, and battery saver isn't on.
Anyone seen something like this? Will try tomorrow without the trusted device settings to see if that matters....
I noticed a similar auto-connect issue with mine, when I was attempting to troubleshoot the stuttering A2DP issues I'm having. If I have the HFP and A2DP profiles both enabled, they both connect right up when the ignition is on. If I have the HFP profile disabled, and only A2DP enabled, it doesn't connect right away and I usually have to manually force it. Very strange. This whole BT situation on this phone has been a pretty big disappointment for me, since I had everything working great with my GNex (running 4.3) and now it's like I've lost the heart of my car audio system.
I bought the Kinovo BT dongle for my wife for Christmas, so it will be interesting to see how that works with her Moto X. I'm pretty excited about trying out the AptX encoding for lossless audio, but I doubt she will even notice the difference.
Just to give you an update.. I downgraded to 4.2.2 and it connects to my Mazda automatically just fine.. Upgraded to 4.4 and the problem returns.. No apps.. Stock + root. Keep in mind that the problem lies only with the auto connect aspect of it.. Streaming/calls work fine but only after manually connecting.
Sent from my XT1053 using Tapatalk
totempole said:
Just to give you an update.. I downgraded to 4.2.2 and it connects to my Mazda automatically just fine.. Upgraded to 4.4 and the problem returns.. No apps.. Stock + root. Keep in mind that the problem lies only with the auto connect aspect of it.. Streaming/calls work fine but only after manually connecting.
Sent from my XT1053 using Tapatalk
Click to expand...
Click to collapse
Did you look at the auto connect app? It worked fine for me. My Bluetooth stopped working for a day or two because I froze a process without realizing what it was so BT wouldn't turn on at all. I think I have to remove and repair both of my devices to get the same setup I had on my Razr Maxx on 4.1.2,
The connecting/disconnection and/or 1-2 minute lag from my General Motors hands-free connection was annoying too. Have to see if that persists. I tried making the A2DP device the trusted one to see if that changes anything.
Really hoping this is something that Moto can/does fix, especially through a Play Store push like they've done with Active Display and the camera app.
not that this is much help for the OP, but my subaru auto connects voice (calls) automagically each time. it also auto-pairs/connects with my TuneLink audio (BT receiver for audio output over headphone/FM).
in the bluetooth settings, the settings button next to your device brings up the paired bt device profile. check to see if all of your devices are registered correctly. for example, my subaru says, "phone audio" and my tunelink says, "media audio".
to help complicate/annoy/support above, i also have a soundbar and BT house phone (cordless). both devices behave the same way my car/tunelink do.
640k said:
not that this is much help for the OP, but my subaru auto connects voice (calls) automagically each time. it also auto-pairs/connects with my TuneLink audio (BT receiver for audio output over headphone/FM).
in the bluetooth settings, the settings button next to your device brings up the paired bt device profile. check to see if all of your devices are registered correctly. for example, my subaru says, "phone audio" and my tunelink says, "media audio".
to help complicate/annoy/support above, i also have a soundbar and BT house phone (cordless). both devices behave the same way my car/tunelink do.
Click to expand...
Click to collapse
Thanks. I do have the boxes ticked in the device settings for which stream to use. The General Motors connection only has Phone Audio (and it's checked) and the dmzmusic A2DP device lists Phone Audio and Media Audio, only Media is checked.
Did you have these devices setup on 4.2.2 before taking the upgrade to 4.3? Did you wipe in the process? Wondering if that's why @totempole had the issue if he is rooted, he probably wiped the device in the process SBFing back to 4.2.2. If you aren't rooted and didn't wipe between 4.2.2 and 4.4, that could explain why it works OK for you and not us..
fury683 said:
Thanks. I do have the boxes ticked in the device settings for which stream to use. The General Motors connection only has Phone Audio (and it's checked) and the dmzmusic A2DP device lists Phone Audio and Media Audio, only Media is checked.
Did you have these devices setup on 4.2.2 before taking the upgrade to 4.3? Did you wipe in the process? Wondering if that's why @totempole had the issue if he is rooted, he probably wiped the device in the process SBFing back to 4.2.2. If you aren't rooted and didn't wipe between 4.2.2 and 4.4, that could explain why it works OK for you and not us..
Click to expand...
Click to collapse
not rooted/haven't wiped.
640k said:
not rooted/haven't wiped.
Click to expand...
Click to collapse
Must be something with setting it up AFTER taking the update to 4.4 Kit Kat. Wonder if @totempole tried setting thiers up after going back to 4.2 and before taking the upgrade for the root process with SlapMyMoto?
fury683 said:
Must be something with setting it up AFTER taking the update to 4.4 Kit Kat. Wonder if @totempole tried setting thiers up after going back to 4.2 and before taking the upgrade for the root process with SlapMyMoto?
Click to expand...
Click to collapse
could be completely device specific too. if your vehicle is BT v2.x or whatever. my tunelink specifically has problems with data/audio stream with the X that my X doesn't have problems with on other devices. could be software/hardware incompatibility issues.
FWIW, my vtech BT phone @ home would NEVER pair with other devices. i would always have to manually pair.
I just emailed Moto about this, because I'm having bugs too. I think that you're on to something, 640k. My Pioneer headunit (FH-P800BT) has BT 2.0, and while HSP connects fine, A2DP only works on the first pair, and after disconnecting once and reconnecting, it won't ever connect A2DP. I have to completely unpair the phone and re-pair it to get both A2DP and HSP working. My phone also gets stuck on "Connecting..." under BT whenever it's having issues connecting with A2DP. Here's the email I sent off to Moto"
I've noticed an issue with my new Moto X that I never had with my Samsung Galaxy Nexus. The phone itself performs way better than my older phone, but I've had a specific bluetooth problem. I have a Pioneer headunit that supports A2DP as well as HSP (music playback and headset functionality) and with my Galaxy Nexus, it worked great, I paired my phone up with the headunit, and both A2DP and HSP would pair at the same time, and work perfectly. With my Moto X, when I first pair the phone to the headunit, it pairs both profiles, but after I've disconnected (turned car off or turned bluetooth off) and come back, it only pairs HSP, and when I try to pair A2DP, my phone gets stuck on "Connecting..." under bluetooth to the headunit, and never will connect to A2DP unless I unpair and re-pair the entire phone. I've tried resetting my headunit and phone and still the same problem exists. Looks like other people are having issues with bluetooth too, as per this article on a popular Android forum > http://forum.xda-developers.com/showthread.php?t=2562186 < I'd like you all to check this out. Seems it's just on 4.4, and wasn't present on 4.2.2 (I never checked myself on 4.2.2, as I immediately upgraded to 4.4 when I got my phone. This doesn't seem to be a hardware problem, but more of a software problem. Please check into this, and don't just read this and act like it's only a problem a handful of people are having. I'd like to have this fixed, and while it's not a deal-breaker for me to use the phone, it does make me a bit frustrated. Thanks in advance!
Click to expand...
Click to collapse
Hey All,
I've done a quick and dirty search for this problem, but I haven't found anything that's exactly the same.
I have an XT1060, Dev Ed, on KK 4.4.4, and I'm just wondering, am I the only one who cannot get my bluetooth radio to hook up to paired devices easily?
The problem is, I always have to ask to connect manually; this is a bit of a pain, especially after turning off my car, say, for a few seconds. Oh, it'll connect, but sometimes it takes 10-15 tries before that connection is made, and even then, it's often after I have to disconnect then attempt to reconnect a few times because it doesn't connect both the phone and media modes.
I have done the unpair/re-pair thing a couple of times, but nothing changes.
I had an HTC phone before this, and it'd reconnect automagically to my cars BT server, so I suspect it's nothing to do with the car's BT radio. I really miss that...
Thanks for any suggestions anyone might have in how to remedy this. Fwiw, I'm willing to go through a diagnostic procedure if someone would clue me in to just how to do that.
cheers,
john
I've had issues with the bluetooth and pairing. When I was on 4.2.2 (I think..) it wouldn't connect automatically at all, and I used an app to connect for me. I have a Chevrolet Cobalt and it wouldn't connect to my built in bluetooth for calls or a small bluetooth dongle that I use for playing music through the AUX input on the stock radio.
https://play.google.com/store/apps/details?id=org.myklos.btautoconnect&hl=en
Once I was on 4.4.2 it seemed to work much better. I have no real issues now on 4.4.4. The only time I notice it not really working right is when I try to connect to the bluetooth speaker in our bathroom at home. If I turn the speaker on, it almost always connects to my girlfriends phone nearly instantly, even though I open the bluetooth menu and tap the paired device to manually initiate right when I turn on the speaker. It usually takes me a few tries to get mine to connect before hers, or I ask her to shut her bluetooth off for a moment while I connect. She uses the speaker every day because she leaves for work after me, so it only happens to me 1-2 times per month on the off chance that I want to listen to music or a baseball game in the shower, so it never really bothered me much.
I think the bluetooth radio in this phone could be better.. I never had any similar issues with my Droid X or Moto Razr Maxx so I'm not sure what the deal is...
Edit: forgot to mention I also have an XT1060, but not dev edition. My bootloader is unlocked and I am rooted, but using the official 4.4.4 VZW rom with Xposed.
I have never had any issues pairing Bluetooth - on either my car or moto 360 watch (even simultaneously).
However, I have noticed that the Bluetooth connects much quicker on custom ROMs when compared to stock.
I think tour connection issue may be a setting or rogue app related.
Sent from my Moto X using XDA Free mobile app
Thanks to both of you for your replies!
Fwiw, things have not gotten any better since I posted my question. I'm getting more accustomed to it, though.
As for the possibility of a rogue app, yes I suppose so, but short of uninstalling everything, and adding them one by one and trying to connect to something via BT, how can someone go about debugging such a thing?
cheers,
john
jrredho said:
Thanks to both of you for your replies!
Fwiw, things have not gotten any better since I posted my question. I'm getting more accustomed to it, though.
As for the possibility of a rogue app, yes I suppose so, but short of uninstalling everything, and adding them one by one and trying to connect to something via BT, how can someone go about debugging such a thing?
cheers,
john
Click to expand...
Click to collapse
You may need to delete the profile for the Bluetooth pairing in your car. Could be a conflict there.
Otherwise, try looking at your Bluetooth settings on the phone.
Sent from my Moto X using XDA Free mobile app
jrredho said:
...
I have an XT1060, Dev Ed, on KK 4.4.4, and I'm just wondering, am I the only one who cannot get my bluetooth radio to hook up to paired devices easily?
The problem is, I always have to ask to connect manually; this is a bit of a pain, especially after turning off my car, say, for a few seconds. Oh, it'll connect, but sometimes it takes 10-15 tries before that connection is made, and even then, it's often after I have to disconnect then attempt to reconnect a few times because it doesn't connect both the phone and media modes.
Click to expand...
Click to collapse
Is it *ALL* bluetooth devices, or just the car? What model and year car? Are you connecting to the Hands Free profile, Headset Profile, or doing something like A2DP for music streaming?
How long have you had the phone, how long has this been a problem? Has the symptom ever changed?
Keep in mind, just because your HTC phone connected to the car just fine, doesn't mean the car could not be the issue. While the Bluetooth profiles and protocols should be "standard" I've seen many issues of interoperability issues between bluetooth devices over the years. Especially with car kits.
KidJoe said:
Is it *ALL* bluetooth devices, or just the car? What model and year car? Are you connecting to the Hands Free profile, Headset Profile, or doing something like A2DP for music streaming?
How long have you had the phone, how long has this been a problem? Has the symptom ever changed?
Keep in mind, just because your HTC phone connected to the car just fine, doesn't mean the car could not be the issue. While the Bluetooth profiles and protocols should be "standard" I've seen many issues of interoperability issues between bluetooth devices over the years. Especially with car kits.
Click to expand...
Click to collapse
Guys, thanks for staying with me on this. One thing I've definitely learned is that the bluetooth thing is something I'm pretty ignorant on. I can see that I'm going to have to study it a bit before too long. Gad, that HTC spoiled me rotten---at least in that way.
I haven't tried the phone with any other BT devices. This is mostly because I don't own but two, the car and a travel speaker, and I haven't had the speaker out of its case since I scored the phone six or eight weeks ago. Also, I did some housecleaning, so I have only a small fraction, maybe 20%, of the same apps on the MotoX that I had on the HTC. I have no apps on the MotoX that I didn't have on the latter.
As for some of the car-related suggestions, it's a 2015 Subaru Forester Premium 2.5i, which is really only level up from the base model of that line. I can't find that there is a bluetooth profile setting in the car that I can change; I think that it's too basic. The relevant user manual simply states the following:
Media format
Bluetooth audio devices cannot be
connected if they are not compatible with
the following Bluetooth® profiles.
. A2DP (Advanced Audio Distribution
Profile)
. AVRCP (Audio/Video Remote Control
Profile)
I don't even know what either of those mean!
Anyway, what I did do is go to the phone settings, and uncheck the Media box that shows up once the car's BT server is detected. Then I try to connect with the Phone box checked. It'll still fail to connect several times, but (a) it doesn't take as long to fail to connect, (b) it doesn't take as many tries (it seems) to make the connection, and (c) when it fails, it fails totally, so I don't have to disconnect from 'Media-only Connected (No Phone)' connection. That makes it easier I suppose. Then once the connection is established, it's a simple matter to go back to settings, and check the Media box. That add-on connection happens pretty quickly, but the process is still a little overwrought, imo.
Of course, KidJoe, up until you mentioned a Headset Profile, I didn't know one existed. But when I try to play music on my phone using PowerAmp, well, the app doesn't hook up to the BT anyway. That's a key difference between the HTC and the MotoX. In PowerAmp, I have "Play over Bluetooth on Detection" selected. The headset isn't being detected at all. So maybe that goes some distance to explaining what I'm encountering.
Again thanks to both of guys for hanging in there with me! I'll keep trudging "onward through the fog," as it were...
cheers,
john
A2DP and AVRC are used for Bluetooth Stereo audio streaming (like playing Pandora on your phone via your car stereo). Not phone calls.
For phone calls, usually a Headset or Handsfree profiles are used, and sometimes BT Phone Book Access (so you can see your phone's contact names/numbers on the car's screen).
I've run into compatibility issues between some phones and some Headset/Handfree devices (mostly cars, but a few bluetooth headsets too). Often times when this happens, you're stuck. Each side will blame the other (i.e. Moto will blame the Subaru car stereo, and Subaru will blame the phone).
I have had issues re-connecting to my car (a 2011 Saab 9-4x with Bose/Nav), IF I had my Moto S11 Flex HD headset connected to my Moto X before I got in the car (even if the S11 was powered off/disconnected from the X before I started the car). Usually toggling the X's bluetooth off/on, and sometimes worst case rebooting the phone, has always fixed it.. Another time I had troubles connecting to my Saab's car kit was when my wife was using her phone to stream audio. The next time I got in the car, I had to manually connect my phone. The car always tries to connect to the the last phone used, so it was looking for my wifes and it took a while before it timed out. When it did time out, it didn't look for mine.
Since you have a 2015 Subaru, I would consider visiting your car dealer, ask them to help with pairing the phone properly, and making sure its working right. See what they have to say.
My bluetooth in my car stopped pairing the other day, and it turns out it was an app that updated and requested permissions related to bluetooth. I didn't notice them because it's an app I trust so I accepted the new permissions without really looking at it.
I used App Settings (Xposed module) to disable the permissions and my bluetooth works fine again.
I could still pair with things if I went to the bluetooth paired device list and manually tapped on the device I wanted to connect with, but it would not pair automatically (like when I got in my car). Once I disabled that permission, it started working again without issue.
May be worth a look through your installed apps to see if anything has access to bluetooth and may be interfering.
Hey All,
Thanks again for the continued help!
It's true, I didn't do any research on app interference before I posted this thread topic, but since a couple of you have brought it up, I decided to do a little research. I installed a permissions app, and took a look at the permissions that allows an app to automatically seek out, and pair with, Bluetooth servers. I have to admit, I got some surprises there. (Who would've thought that Beautiful Widgets needed that permission; it is now gone.)
Anyway, most of the remaining apps are either system/Moto-related, or ones I would really like to keep. I'll report back on what I learn. If there are other permissions that I need to reference besides the two pairing-connecting to Bluetooth ones please let me know...
cheers,
john
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
I recently purchased a new VW car and have been using Android Auto on the built in display. The first time I used it it all worked perfectly, since then it hasn't. My Android Auto no longer gives me notifications when I receive texts. And if they do show up on the home screen and I click the play button to read them, it shows the four dots as if its thinking but nothing happens and I have to cancel out of it.
Additionally, I've noticed that my bluetooth smart lock doesn't seem to be working at all. Every time I connect it asks if I want to add my car to my trusted devices. Each time I say yes but it NEVER seems to save it. It will then later sometimes prompt for permission to read my messages. To this I again say yes but it doesn't seem to make the message issue go away even after I do this. I am not sure if these two issues are related (I'm hoping they are).
Can anyone tell me why the hell my smart lock can't seem to register and remember my car? And why wont android auto read my messages properly? (Pixel XL. Phone calls and navigation all are working properly)
Same issue here
You have to give Android Auto all permissions it asks for at the first start. And be sure to use a very good cable. There are many USB C cables on market which are not fully supporting USB C features and the system do expect them.
I'm in the same situation with my VW Atlas. Problem is with both my Pixel (running Android O) and my wife's Nexus 6p (running Nougat). I have given it all permissions, including some that it didn't ask for. I also have been using the little 4 inch cord that came with the 6p, so the cable or its length should not be an issue. In addition to the above, my car also forgets its bluetooth pairings if I try to connect the AA cable before the bluetooth has connected. I've been learning to do that but sometimes I forget. It's got to be an issue with the VW software.
I have come across these issues myself in a Golf Mk7 both with a Motorola Droid Turbo and now with a Google Pixel 3 XL.
In the case of getting Android Auto to read/send messages where you just get the four dots bouncing up and down and doing nothing else, that's a setting with the Google Assistant app. Go into that app on your phone (the round G icon) and drill into settings and under Voice >> Voice Match, make sure "OK Google" detection is turned on. Even though you might not be actually using it, it has to be turned on for this to work. Totally lame and non-intuitive, but that's what fixed that for me.
As for the car falling out of your Smart Lock and for repeatedly prompting you for permission to access your text messages, I have only had this issue with AA in my VW and not in other cars, so it's a VW-specific issue and something to do with the bluetooth hardware. I do not have a fix for it but the workaround is you must have BT turned on on your phone first and let it connect fully to your car OUTSIDE of AA. Make sure at that point you permit text message access (if prompted) and check your Smart Lock and add your car to it if needed. Then going forward whenever you connect to your car you MUST let BT connect fully first before you plug in and fire up AA. It's unfortunate that you can't just plug in and go w/o waiting for BT first but that's the only way I've gotten this to work without re-prompting me for SMS access permissions and Smart Lock.
Good luck!