anyone pairing this with a kaiser... any tips would be welcome
mex-2500 - guess it's allmost the same
No problems here
Can't remember the excact way to do it but it's something with turning the radio off and holding down a button for a long long time until the BT icon flashes on the radio and KEEP pressing it for a while longer
been playing with it today... just need to hold 6 once their paired. what a great bit of kit. Love the mp3 streaming via bt
The streaming is not working for me after I switch the radio off and on again, only works the first time it's paired
I guess it's the MEX-BT2500's firmware or something
Yours have USB also right? I'd love to have that
Wireless Stereo
In "Comm Manager" go to "Settings" then to "Bluetooth" then press "XPLOD" and you will see two items: "Wireless Stereo" and "Hands Free". Switch off "Wireless Stereo" and save. Then open this page again and switch "Wireless Stereo" on.
Save it. On your car radio is the sign of "Wireless Stereo" again. I know, it´s crazy but it works.
wireless stereo
I checked setup yesterday: select "Wireless Stereo" on the radio then push
knob "6" (station channel) and your "Wireless Stereo" is "on" again.
Damn... Your right
Switching to "BT AUDIO" on the radio and pressing 6 ('pause' as it also says above it) switches it on again - Thanks a million mate
...any chance I can start playback using the buttons on the radio too?
just need to hold 6 once their paired once and will always be reconised again.
I have installed steering wheel controlls and this lets me controll playback on the phone (skiping tracks ect). Nice kit
holding button calls last number. Pressing quickly lets you use voice activation.
Has anyone got the voice activation to actually work on the Kaiser? I can't get it tow work.
I'm using Hyper Dragon III (Opal) which didn't have any voice software installed so I got MS Voice command on there.
The voice dialing doesn't work
I installed cyperion or whatever it's called aswell as the MS Voice command and that doesn't work either
Any help would be great!
Help with Sony MEX-BT3600U Bluetooth Calling
Please help me solve this issue with my Sony MEX-BT3600u. I recently installed the head unit, everything is connected and works fine, but every time I try to call someone i cannot hear the person but the they can hear me. Now I've connected 2 apms and a cross over unit. I've connected the head unit by RCA Cable to the Cross-Over and then the 2 Amps are connected by RCA Cables to the Cross-Over, but instead of connecting the speakers to the unit I connected them directly to the amps instead.
Do I have to connect the a pair of speakers to the head so that I can hear the person I called?
Please help..
Thanks
Hi,
I just purchased the scala rider intercom
its an intercom system for motors. I am having one issue with my N1 on voice dialing. I can give a command to voice dial and while the phone is "on" (that is, the screen is on) it works, kinda, it gives me the suggestions of the name I just said. when I press it on my phone it dials. ( so to be clear the input command is done by my scala head set.)
obviously this isnt how it should works. I need to give the command and not touch my phone at all. When my phone is "off" (that is, the screen is off) it does give a vibrate signal after I give the voice command, but it doesnt dial. I suppose this is because the phone wants me to choose and confirm the name i just shouted.
I tried adding 'mobile' to a name in my list. when voice dialing normally it only prompted the correct name (no other suggestions), but the nexus still wants you to confirm it. I cannot confirm a name while riding a bike so I actually want it to just call the first suggestion. its always right anyway.
the scala rider manual doesnt say anything, it just refers you to the phone's manual. but I cant get it to work.
I cant really test it on my 'normal' bluetooth headset, because it doesnt support any voice dial options.
does anyone know if I can force the nexus to dial the first suggestion? maybe someone has experience with voice dialing via a Bluetooth system and has another solution..??
any help is much appreciated.
Tom
I have a Scala Q2, however i have never used it for voice calls.
However have you tried to 'confirm' the call by pressing one of the buttons on you Scala. I think one is accept and the other is decline.
Hello,
I just purchased and installed a Pioneer AVH-4100NEX. So far it's pretty slick. I'll be using it with my Galaxy S6.
I noticed that when I try to disable the Call Audio Bluetooth profile from the phone side, it re-enables itself... like I HAVE to use the NEX for call audio.
I would like to be able to turn on my BT headset and use that instead, without much hassle. There are definitely times where I'll be in the car with other people and don't want the whole car to hear the conversation. It also presents a call quality issue with the far end being able to hear the system speakers.
Do I have to unplug USB from the NEX to make this work?
muzicman82 said:
Hello,
I just purchased and installed a Pioneer AVH-4100NEX. So far it's pretty slick. I'll be using it with my Galaxy S6.
I noticed that when I try to disable the Call Audio Bluetooth profile from the phone side, it re-enables itself... like I HAVE to use the NEX for call audio.
I would like to be able to turn on my BT headset and use that instead, without much hassle. There are definitely times where I'll be in the car with other people and don't want the whole car to hear the conversation. It also presents a call quality issue with the far end being able to hear the system speakers.
Do I have to unplug USB from the NEX to make this work?
Click to expand...
Click to collapse
I would like to know this also
I have same unit, try having headset connected before plugging in your phone. That may work
Sent from my SM-N910V using Tapatalk
I'm bumping this up. With my previous phone (LG V10) I could select which device use to make phone calls, Android Auto device or a bluetooth headset (Plantronics). Now with a Oneplus 3T that is not possible anymore.
AA automatically rerouting "BT phone" to main AA device. That is really annoying.
If someone knows a workaround to this please give advice, thanks...
You have to have it enabled, in a nutshell the unit (Pioneer) declares that it has bluetooth capabilities and declares the bluetooth mac address when it initialize the connection, than Android Auto (trough Google Play Services which is a system app) will enable the bluetooth, set up a pairing if it doesn't exist and connect to it, so no matter what you do it will always connect to it, the only way to "avoid" this is:
a) Get another phone which connects to the Pioneer bluetooth, then connect the phone (haven't tried this, but probably will do the trick)
b) Alter the pioneer unit so it doesn't send the bluetooth mac and it doesn't declare the bluetooth service (almost impossible, you will need to replace the app on the unit)
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!