Related
So I have a shiny new Kenwood KDC-BT838U and for a $220 dollar toy it is pissing me off very much. It does not automatically connect or disconnect from my phone when powering on or off. Simple fix for that is an app to manually establish connection. a2dp will be running fine, then a call comes in. After the call sound will not work and I get all kinds of connection issues until I just power down the head unit then turn it back on (sometimes a few times).
I tested my kaiser with other bluetooth HU's and it worked fine. Then kenwood was not in the store but I love all its other features and it looks great. I contacted Kenwood support and they said that it is a problem with my phone's bluetooth protocol. I decided to give Kenwood the benefit of the doubt. I want to try the widcomm stack.
Found it here.
http://forum.xda-developers.com/showpost.php?p=1072773&postcount=72
I have read that it works with the kaiser. True? After installing the cab, do I need to delete the MS bluetooth reg key or do anything special?
Any Kaiser widcomm users out there? Can you comment on any issues you have? Thanks!
I went ahead and installed the cab linked above. At first I was getting the out of memory error on boot. I changed the baud rate ([HKLM\Software\Widcomm\BTConfig\SerialTransport]) to 115200 and it appears to be working now. Will report more findings later. If anyone else is using it please share your experiences here. Pretty much all the threads I found by searching were people with the same question and they pretty much all went unanswered.
Wellit only thinks it is working. Kasier would not find any bluetooth devices near by and my computer cannot find my kaiser. I guess I will give up now but if anyone else got it working please let me know.
Oh BTW, don't install the CAB unless you don't mind a hard reset. I was prepared for that of course, but just a heads up.
My car's headunit has A2DP, and once paired, my OG would always reconnect when in range. The bionic doesn't seem to do this - so I have to open the wireless/network->bluetooth settings screen and manually force it to connect.
Not the end of the world, but it'd be nice to not have to do that everytime you get in the car.
Anyone else have any feedback on the Bionic's BT functionality?
This is not a problem I have experienced as mine reconnects no problem. What type of headset are you using. If problem persists I suggest turning headset off and back on, then it should reconnect. That beats navigating around the phone menu.
Sent from my DROID BIONIC using xda premium
I am having this same issue with my 2010 Ford Ford Fusion Hybrid with MS Sync and the Bionic. The phone connects fine but the A2DP does not. I wonder if there is a thread on the Moto support forums about this?
yutzyscott said:
This is not a problem I have experienced as mine reconnects no problem. What type of headset are you using. If problem persists I suggest turning headset off and back on, then it should reconnect. That beats navigating around the phone menu.
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
I'm not using a headset, I'm using a JVC xr810 headunit (in-dash stereo ). Both the phone and A2DP connect quickly when I force it to under BT settings; but neither reconnects automatically, regardless of which device I turn power-on first.
WPWoodJr said:
I am having this same issue with my 2010 Ford Ford Fusion Hybrid with MS Sync and the Bionic. The phone connects fine but the A2DP does not. I wonder if there is a thread on the Moto support forums about this?
Click to expand...
Click to collapse
Interesting - so the phone auto-connects?
I am having a similar issue with my Sony Head unit. It will always automatically connect via the handsfree profile but the A2PD does not. I have to turn the Bluetooth on the headunit off and then back on and it then connects with both profiles. Its annoying to say the least.
WhiskeySlx said:
Interesting - so the phone auto-connects?
Click to expand...
Click to collapse
Yes it auto-connects to the phone, but for A2DP MS Sync says "Connection failed". I used to see this on my Droid X but it would always connect a second later anyway.
I am seeing the same issue with my bionic and pioneer audio head unit. When i force the connection manually it works. But the phone does not connect automatically. I have a friend with a bionic who is pairing with his mini without issues. We will test my phone on his car and his phone on my HU. This will at least tells us if the issue is with the phone itself or the other unit.
Same problem here. I have an Alpine IDA-001 deck. My OG Droid handled it fine.
WhiskeySlx said:
My car's headunit has A2DP, and once paired, my OG would always reconnect when in range. The bionic doesn't seem to do this - so I have to open the wireless/network->bluetooth settings screen and manually force it to connect.
Not the end of the world, but it'd be nice to not have to do that everytime you get in the car.
Anyone else have any feedback on the Bionic's BT functionality?
Click to expand...
Click to collapse
My 2011 Frontier has basic connection, and it always reconnects. But, when I paired my BIONIC, I deleted my DROID profile so there is only the one profile for it to connect to.
Could that be the key?
I posted about this here in the Motorola Support forum:
supportforums.motorola.com/thread/57688
---------- Post added at 10:29 PM ---------- Previous post was at 10:24 PM ----------
Ziggyrama said:
I am seeing the same issue with my bionic and pioneer audio head unit. When i force the connection manually it works. But the phone does not connect automatically. I have a friend with a bionic who is pairing with his mini without issues. We will test my phone on his car and his phone on my HU. This will at least tells us if the issue is with the phone itself or the other unit.
Click to expand...
Click to collapse
Looking forward to the results of this test!
johnlgalt said:
My 2011 Frontier has basic connection, and it always reconnects. But, when I paired my BIONIC, I deleted my DROID profile so there is only the one profile for it to connect to.
Could that be the key?
Click to expand...
Click to collapse
See my post below on how I resolved this. Thanks!
Sorry I am not allowed by the forum to post links yet so just paste this into your browser:
supportforums.motorola.com/thread/57688?tstart=0
WPWoodJr said:
See my post below on how I resolved this. Thanks!
Sorry I am not allowed by the forum to post links yet so just paste this into your browser:
supportforums.motorola.com/thread/57688?tstart=0
Click to expand...
Click to collapse
Thanks for the link! I'll see what I can do, but I don't have ford-media-sync.
I've already tried deleting all pairings, and restablishing, but... maybe I'll connect to my handsfree earpiece first, and then connect to the car's HU?
(I'm not sure if you closed that thread or what, but you might want to leave it open since others without the ford system can continue debugging/discussing?)
looking to get bt working in my nissan, the bionic connects but no sound, my eris connected no problem. deleted all profiles in car system with the bionic #1 priority.
WhiskeySlx said:
Thanks for the link! I'll see what I can do, but I don't have ford-media-sync.
I've already tried deleting all pairings, and restablishing, but... maybe I'll connect to my handsfree earpiece first, and then connect to the car's HU?
(I'm not sure if you closed that thread or what, but you might want to leave it open since others without the ford system can continue debugging/discussing?)
Click to expand...
Click to collapse
Maybe you should start a new thread at Moto support with your particular issue, so as not to confuse things.
My car has two ways to connect - via the media setup (A2DP) and via the phone setup (headset profile). I connected through the A2DP setup, but again I'm not sure that was what fixed the problem, or whether it was the deleting of some other phones from my Bluetooth list.
I've marked it Not Answered again over at Moto support.
hmmm... My TomTom Go! 730 reconnects just fine every time. Curious!
Mine also reconnects fine, but I don't have A2DP on the headunit so I can't help with that part.
cruiser86 said:
looking to get bt working in my nissan, the bionic connects but no sound, my eris connected no problem. deleted all profiles in car system with the bionic #1 priority.
Click to expand...
Click to collapse
Nissan's BT implementation is horrible. Moto had the best sound quality on my Altima, but that's not saying much.
I also had slow to nonexistent reconnects in my car as well, with having to force the connection manually to get it to connect.
OK, so today I got some help from my friend with another bionic and we tried my phone that is having issues with reconnecting on his mini that he has no issues with. So, the results are:
My phone was able to pair successfully with his Mini and it reconnected automatically when we turned the car off and on.
I did not try his phone in my car as I see no point. It is clear to me that the issue is with the combination of my Pioneer HU and the Bionic. I am going to conduct another test tomorrow. I will factory reset the BT unit thus wiping anything that could potentially be left over from my old D1 which could be interfering with the new pairing.
I do sincerely hope that clearing out the profiles will work, but I'm less than optimistic about the fact that it is a head unit as opposed to a general BT unit that was included by Nissan in my truck, which I'm almost positive is not controlled by the head unit itself.
At any rate, I had some issue with freezing the wrong app and factory reset my phone, and today it was not connecting (obviously, b/c for some odd reason it did not fetch my saved APNs, WP, BT profiles, etc. from my Google account, while when I first bought the phone it readily pulled everything so that all the info from my DROID transferred flawlessly.
Long story short, I had to re-pair with my truck, but it recognized (presumably by MAC address) my phone and the truck's female copilot announced that the phone was already stored in a profile and that I could just go ahead and connect to it. So I did.
Tomorrow, I'll let you know if it connects automatically or not.
---------- Post added at 10:18 PM ---------- Previous post was at 10:16 PM ----------
WPWoodJr said:
See my post below on how I resolved this. Thanks!
Sorry I am not allowed by the forum to post links yet so just paste this into your browser:
supportforums.motorola.com/thread/57688?tstart=0
Click to expand...
Click to collapse
Yeah, I'm a member over there as well, same username and everything. I was on the private panel that was studying the Call Quality issues that the original DROID was having with some people.
Glad that it worked out for you, and hopefully it works out for others. See my post just above for my little test to see if it works after a factory reset - I'm suspecting that in fact I'll need to delete that profile and start fresh....
I use the Motorola Assist driving feature, and I noticed in the settings that it should learn my bluetooth devices associated with driving over time. I connect frequently to my JVC head unit through bluetooth, but it has never learned the device and will not auto play media from the application that I select.
Anyone else have this issue or know how to fix it?
bravesfan171 said:
I use the Motorola Assist driving feature, and I noticed in the settings that it should learn my bluetooth devices associated with driving over time. I connect frequently to my JVC head unit through bluetooth, but it has never learned the device and will not auto play media from the application that I select.
Anyone else have this issue or know how to fix it?
Click to expand...
Click to collapse
Yup... and nope. My in-truck bluetooth device (originally a Logitech adaptor, and recently a Kinivo BTC450) have never been recorded as a device in Asisst's Drive settings. As for play resume... this worked two updates ago, but the last two updates broke it, and this has been confirmed by Mark Rose @ Moto.
I have no solutions for fixing either short of waiting for another update... and hoping as many as possible reporting it through official channels so it becomes a priority for them to fix.
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
Has anyone been able to successfully update the SWM 8802 headunit to android 8.1. I received this unit and installed it. I was under the impression that it was android 7.1, but turns out its actually 5.1. I have a couple issues I need to figure out/resolve.
Bluetooth - I cannot connect to my OBDII device or control any bluetooth settings
Touch Beep - The head unit beeps everytime I touch it and there is no setting to disable it
Any help would be greatly appreciated.
jedigesus said:
Has anyone been able to successfully update the SWM 8802 headunit to android 8.1. I received this unit and installed it. I was under the impression that it was android 7.1, but turns out its actually 5.1. I have a couple issues I need to figure out/resolve.
Bluetooth - I cannot connect to my OBDII device or control any bluetooth settings
Touch Beep - The head unit beeps everytime I touch it and there is no setting to disable it
Any help would be greatly appreciated.
Click to expand...
Click to collapse
What do the reseller suggest when contacted for support answer to your impression?
marchnz said:
What do the reseller suggest when contacted for support answer to your impression?
Click to expand...
Click to collapse
I didn't contact. They are a chinese ebay seller. Didn't want to waste my time. I will send an email though, see what they say.
I am looking for this answer on the disabling the beep too! Did you figure it out? If I find any info, I will post it here as well as this thread