Related
I need help too...
I have Tom Tom on mmc card but my Gps receiver wont connect. I always get 'no gps device' message although my device is connected. the red light begins by flashing but then stays on constant. (is this relevant?).
My incoming beams box is already unchecked.
I have XDA 2i and would like exact step by step instructions how to get my GPS to work... (I'm a new user - it took me one hour to set a song as my ring tone - so imagine how long this is taking!) I feel like I have tried absolutely everything and its really starting to drive me crazy. All I want is sat nav.
Thanks.....
XDAIIi GPS problem
Chicken,
what version of TT are u using?
what gps receiver?
If it's TT3.x, 4.x, or 5.x (don't know v6 yet), first you'll need to pair your receiver with your XDA. Go to Bluetooth Manager->Tools->Paired Devices. Here (if it's not there already) tap on Add and then tap on search icon (next to Device: field). It will search for any bluetoothdevices in range. Once it finds your GPS receiver, enter the passkey (provided with the receiver, usually 0000) and tap ok. The GPS receiver should be installed.
Start TT, go to Change Preferences and browse to Show GPS Status. Here, tap on Configure, choose your GPS device (I guess it will be Other Bluetooth GPS), click on Select (if prompted for pairing the GPS with PDA just tap on Continue) and choose the port. It'll be one of the bluetooth serial ports (it's COM6 in my case). Make sure that the receiver is still on and bluetooth active and watch the GPS status. If there is No GPS device! message on the top go back to configuration and change to another port.
If still no luck go to your XDA Start->Settings->Connections->Beam, make sure the Receive all incoming beams is not selected. If still no joy, you'll need to test all the connections, check if you can 'see' the receiver with another bluetooth device ez mobile phone, than do the same with your PDA. You can also reset the GPS receiver (check the manual), you can also do it by removing the battery from it and leave it like this overnight...
Good luck!
can you recommend a good GPS receiver?
Hi Robsonix.
Thanks for your reply. I got stuck at the first stage though - but was relieved to find out I'm not a complete dummy as this is what I had already tried - but failed. I cannot get my GPS to pair up with my bluetooth. My phone cannot find it.
I bought my receiver on Ebay. its just a wire thing that connects through my cig lighter to my phone. It didnt come with any instructions!! I think its a little dodgy. Can you recommend a proper one?
I'm not sure what tom tom it is, I think 5?? But actually I havent a clue.
I cant check if the receiver works with another phone as it only has connections for the xda 2i.
Thanks for your help - I hope u can help me some more.....
any recommendations??
Chiken
ha ha. Never mind - I think I've found the problem. I'm such a thicko!! It takes two to tango right? I'm such a thicko...
Port Numbers
chiken said:
I need help too...
I have Tom Tom on mmc card but my Gps receiver wont connect. I always get 'no gps device' message although my device is connected. the red light begins by flashing but then stays on constant. (is this relevant?).
My incoming beams box is already unchecked.
I have XDA 2i and would like exact step by step instructions how to get my GPS to work... (I'm a new user - it took me one hour to set a song as my ring tone - so imagine how long this is taking!) I feel like I have tried absolutely everything and its really starting to drive me crazy. All I want is sat nav.
Thanks.....
Click to expand...
Click to collapse
Do you select the correct port number to match your gps port number in the gps setup in TomTom?
DAz
SPV 1500 "Alpine" TT5 with GPS receiver
I've just joined this Forus following the aquisition of an Orange SPV which is now unlocked to run on T-Mobile. I have also used an MDA Compact II (Charmer?) successfully for the past year.
Like this current thread originator "chicken" (and no doubt many others) have had difficulty running my Holox BT-321 BT sat receiver with TT5. It pairs OK, but I TT5 cannot "see" the device, even though I have selected just about every Com device available.
I recently bought a wired sat receiver (just like chicken did), and thought this would work better. However, TT5 will not see this device either!
Can someone tell me how I can check which Com port is active on the PDA, or check if there is an input stream coming in from the sat receiver?
This is getting bloody frustrating now. My old Nokia 6600's worked first time out of the box!
Thanks
Peter (with the Aprilia Falco 1000)
I wonder if anybody knows if it is possible to have two (or more) divices connected at onceon a Blue Angel?
eg. Tom Tom 6 plus a hands free connection.
I have tried every configuration I can think of, different ports ect, but to now avail.
With the gps connection up and running, as soon as you turn on the hands free , the gps connection link is lost, turn off hands free and it will resume connection.
I am using BA WM5 AKU3.5 R4 - xplode's excellent rom
In GPS settings
Program is using COM 5
Hardware is using COM 0
Manage GPS settings set to Auto
In Device settings,
BTGPS unit is on COM 0 (Serial box ticked)
Hands free is unassigned
Any help will be much appreciated.
any idea's anyone?
On Last Baniaczek's ROM I made an experiment just a moment ago: BlueAngel, Navigation system (Polish one, Automapa), plus GPS on Bluetooth and A2DP headset - first connected headphones, then added GPS (using automatic GPS connection - it's M$ Stack) - Everything seems to be working fine. I thought it was a bit unstable at first, but AD2P stops sending data, when there is no sound from the device.
GPS Settings are default: COM6 for applications and GPS has COM7 assigned on Hardware tab and in Bluetooth outgoing port. Quite seamless.
then I made the 2nd one: same headset connected in Handsfree mode: indeed turning on navigation made it connect and disconnect every few seconds.
For me it seems to be fault of M$ BT stack: it cannot hold 2 similar streams on BT (COM and Handsfree/Headset are both typical serial connections of highest priority in BT stream). At the same time it can cope easily with two different streams (A2DP is lower priority, high-bandwidth BT connection).
I'm not sure, but I think when I used old Helmi 1.3.2 with Widcomm stack it could cope with GPS and Handsfree at the same time, but it needs more testing.
jakubd is right it is limitation in MS BT Stack
Don't give up and it should start to work. I have similar problem with BT GPS and BT headset. GPS goes on and off while headset is on. And than I try to switch headset off and on, BT off and on, GPS off and on and after some time it start to work together with no problem. It takes first 10-15 minutes of my voyage but then it works for the remaining few hours.
Sorry, but I still didn't find out what combination make it work. If I do, I will post it here as workaround.
And I'm almost sure that I had no such problem with Helmi 1.4 ROM.
Thanks guys,
have tried every configuration I can think of, but its always the GPS connection that is dropped, not the hands free, this would not be a problem if it was just when you are answering a call.The GPS reconnects only when you disconnect the hands free connection. ?
Has anyone Successfully used the Widcomm stack with this type of setup?
I am sure alot of members would find this usefull if it can be made to work!
This is my experience:
ROM : Helmi_BA_WM2k5_AKU3.5_v1.4.CF2.R2 (baniaczek)
Tom Tom 6
GPS : Bluetooth
Headset : Nokia BH-300
When the headset is on and connected, the GPS doesn't work (TT say no GPS found). When I turn off the headset, the GPS is working.
With ActiveSync I have the same problem: when the headset is turned on, I can't establish a connection with the PC via bluetooth.
BUT!
If I use a different headset, a Logitech HS03, all is working fine. I can leave the headset on and the GPS is working. I can receive incoming calls with no problem (using the headset) while I'm driving without loosing GPS signal.
With ActiveSync is the same: I can connect my PC with the headset on.
I have no idea why there is this difference with these two headsets, but one is working and the other no. I don't know if the problem is the MS BT stack, but my test demonstrates that under some circumstances this stack could manage more than one connection at time.
bigmike said:
I don't know if the problem is the MS BT stack, but my test demonstrates that under some circumstances this stack could manage more than one connection at time.
Click to expand...
Click to collapse
Bigmike, my point exactly. As I wrote in my post I keep turning on and off until finally it works. So there are some circumstances under coexistence is possible.
It seems that devices try to use same port which means that first device does not reserve port for itself. I am not an expert but it seems if we could somehow force devices to use different ports problem would be gone.
bigmike said:
If I use a different headset, a Logitech HS03, all is working fine. I can leave the headset on and the GPS is working. I can receive incoming calls with no problem (using the headset) while I'm driving without loosing GPS signal.
Click to expand...
Click to collapse
If this works with one set and doesn't work with another, it might be connected to list of profiles supported by the headset:
1. Headset - HSP - more common, typical profile for use with cell phones (supports AT commands)
2. Handsfree - HFP - audio-centric, used mostly in cars, less common
http://en.wikipedia.org/wiki/Bluetooth_profile
My SonyEricsson HBH-600 has both profiles (checked with services list on SonyEricsson phone), but I don't know how to select which profile is used by headset.
Just a thought...
sassa said:
Bigmike, my point exactly. As I wrote in my post I keep turning on and off until finally it works. So there are some circumstances under coexistence is possible.
Click to expand...
Click to collapse
I hope you haven't misunderstand my previous post. I haven't in mind to minimize the value of your post (very useful is someone will try to investigate about this problem).
I was thinking that somebody, reading your contribute, could wrongly think: “you're are a lucky guy and turning on-off the headset repeatedly you crash some library and the two devices are working together”.
My intention was to remark the fact that under some circumstances the headset and the gps can connect together every time and always at first try: it's not lucky, crash or random events.
jakubd said:
If this works with one set and doesn't work with another, it might be connected to list of profiles supported by the headset
Click to expand...
Click to collapse
I have a similar thought.
It seems to me that some times ago I have read that it should be possible to change some profile's parameters “playing” with the registry.... but I could be wrong...
bigmike said:
I hope you haven't misunderstand my previous post. I haven't in mind to minimize the value of your post (very useful is someone will try to investigate about this problem).
Click to expand...
Click to collapse
No I have not, bigmike, just the opposite. I was delighted that somebody confirmed my point.
bigmike said:
My intention was to remark the fact that under some circumstances the headset and the gps can connect together every time and always at first try: it's not lucky, crash or random events.
Click to expand...
Click to collapse
Couldn't agree more. And I think it's worth trying to resolve it.
Multiple BT connections - solution?
I think I find a solution for this, or maybe we can call it workaround. At least it works for me.
As I wrote in my previous posts, I could make it work every time just didn't know how. Now I established repetable procedure which worked every time for reasonable number of experiments.
Secret was to turn on BT headset (in my case Plantronics) and BT GPS device (Haicom 406-BT) and GPS program (iGo) first, and then go to Comm Manager and turn bluetooth on.
So my procedure is:
1. make sure that BT is off in Comm Manager
2. turn on BT headset
3. turn on GPS device
4. open iGo program
5. minimize iGo
6. turn on BT in Comm manager
7. open iGo and make sure it's connected
8. go to phone and call myself just to make sure it works
9. back to iGO and make sure it works
If 8 or 9 fails for the first time, just turn BT off and on again in Comm manager and check it again. I never need to do this more than twice.
Try this, guys, and good luck.
P.S. I don't know if it matters, but make sure that in Settings/Connections/GPS "GPS program port" and "GPS hardware port" is set to (None) and "Manage GPS automatically" unticked.
Very good! Many thanks Sassa!
I have tried for two times your procedure and both tries worked very well (with TomTom6 and Nokia BH-300)
I use a slightly different procedure:
1. BT off in Comm Manager
2. turn on BT headset
3. turn on GPS device
4. turn on BT in Comm manager
5. open TomTom 6 (wait some seconds and make sure it's connected)
6. go to phone and call myself (on the first call the headset is disconnected)
7. back to TomTom and make sure it works
I have noticed a different behavior of the BT headset having the BT always on (in Comm Manager) and using this procedure... but I need to make some tests before writing more.
i HAVE A KAISER TILT ALSO KNOW AS ATT TILT AND AM HAVING TROUBLE DOWNLOADING MY CONTACTS TO MY NOKIA BLUETOOTH CAR KIT HAS ANY ONE HAVE ANY TROUBLE DOWNLOADING THERE CONTACT LIST IS THERE ANY SOFTWARE I NEED TO ADD TO THE PHONE. I TRIED USING AN APPLICATION CALLED JETWARE WHICH WILL ALLOW ME TO DOWNLOAD BUT WHEN I MAKE A CALL IT WONT ALLOW ME TO HANG-UP THE CALL. ANY HELP WOULD BE GREATLY APPRECIATED.
First, STOP YELLING !!
Second, try using the enter key sometimes.
Third, i didn't read your post, can't help ya, sorry.
anaethelion said:
First, STOP YELLING !!
Second, try using the enter key sometimes.
Third, i didn't read your post, can't help ya, sorry.
Click to expand...
Click to collapse
dude? why?
hey man sorry that guy was such a jerk dont want that to be your first expericne here as long as you search before asking most people will be more then willing to help you. sorry i cant help ya though. my only guess is maybe did you install a wm 6.1 rom? they have some probems with bluetooth but i dont think thats it
Did you try it without Jetware? Made sure your bluetooth was set as discoverable? Paired the device? The more info YOU provide as to what you've done, tried, & what setup you've done it with...the beter the help & answers you'll get.
I'd suggest filtering through the following threads. There have been similar problems fixed:
http://forum.xda-developers.com/showthread.php?t=364559&highlight=Kaiser+Nokia+car+kit
In the above thread the original poster solved his nokia carkit issue following this:
1. Pair the TyTN II to the car (Nokia HT-2) phone.
2. Switch car ignition OFF and switch off TyTN II.
3. Remove SIM from TyTN II.
4. Place SIM into a compatible phone (in my case Nokia N95).
5. Switch on N95, switch on Bluetooth, switch on Remote SIM access.
6. Change the Bluetooth ID name on the N95 to the same as the TyTN II.
7. Make phone discoverable via Bluetooth.
8. Switch on car ignition - car phone will not be able to connect.
9. Using car controls search for new device.
10. When N95 is found, select connect, it will use the same user profile as the TyTN II (if you selected the same name for the Bluetooth ID).
11. On the car browse to Settings - Phonebook - Update, this will then import all your contacts from your N95 (or compatible phone).
12. Switch off ignition and switch off N95.
13. Replace SIM back to TyTN II.
14. Ensure TyTN II Bluetooth is ON, Remote SIM is ON and the phone is Discoverable.
15. Switch on car ignition - car phone will not be able to connect.
16. Using car controls search for new device.
17. When TyTN II is found, select connect, it will use the same user profile as before.
18. Now browse the car Phonebook as normal - All your contacts are now available for you to use.
19. Don't forget to turn off discoverability on the TyTN II and to rename your compatible phone (N95) to prevent any future conflicts.
This worked for me! I hope it will work for you! Good Luck!
I did try it with removing the jetware the bluetooth works fine but cant download contacts is there anyother patch or software more compatable with nokia bluetooth devices. Jet ware is good but wont let me disconect call when done any one else have an issue like this
BOBBYDS1 is your connection between the Kaiser and the Car Kit using Bluetooth as a headset (in other words the phone still functions and you can look up and dial with the phone) or is it using rSAP (Remote Sim) which switches your Kaiser into flight mode.
I ask this as it will determine which way you look for a solution. If its using rSAP then most Nokia systems that are fitted into cars as factory fit have not yet developed the correct software to communicate with Windows Mobile devices, in which case you will need to remove Jetware from you Kaiser and use my solution on a previous post as quoted above.
http://forum.xda-developers.com/show...+Nokia+car+kit
Mark
The phone still functions as i can disconnect by the phone it self here is the thing sometimes I can disconnect call by the nokia bluetooth device but a lot of times I cannot disconnect, i have to pull phone out of my pocket and end call
@BOBBYDS1 and fb.knight
No offence guys, but you need to go back to Junior High and learn how to use commas, question marks and letter cases.
Posts like that will rarely get you any kind of a reasonable response.
what nokia bluetooth car kit are you trying to use?
Still not clear if your carkit is using headset or rSAP profiles. Can you either tell us the model of the carkit, or tell us if you can browse the internet from the phone whilst its connected to the carkit?
Punctuation good enough there Dark?! (JOKE!!)
IT is a Nokia CK15-w Bluetooth Car kit Here is a link to it. http://www.nokiausa.com/A4431279
Also I can surf the internet while it is connected to the bluetooth.
Looks like that model supports:
Hands-free Profile 1.5, Phonebook Access Profile 1.0
(Source: Nokia Europe
The Kaiser supports:
File Transfer Profile, SIM Access Profile (rSAP), Dial-Up Networking Profile, Personal Area Networking Profile, Hands-Free Profile 1.5, Advanced Audio Distribution Profile (I'm guessing A2DP)
(Source: www.theunwired.net
So I'm guessing that whilst it will work as a glorified headset, you have no chance of getting your contacts downloaded! Should be able to get them from your SIM, just not the main memory. Wonder why Nokia removed the rSAP profile? It was on their 610 (rSAP only) 616 (rSAP and Handsfree) then from the 810 and CK-15 it seems to be handsfree only. This could be why so many are having problems with Nokia carkits, Nokia went and changed the supported bluetooth profiles. Funny, I would have thought the newer the model, the more it would have done, but I guess not! Glad I looked into this as I was thinking about 'upgrading' to the 810 for the full handset, guess I won't be now!
I am getting confused, I downloaded the jetstream program to the phone and was able to download the contact list no problem. The problem i am having is when i make a call from the nokia bluetooth when I am done and hit the endcall button on the nokia it does not end the call, I have to pull out the phone and hit the end button on the phone itself. any suggestions on how to correct this.
BOBBYDS1 said:
I am getting confused,
Click to expand...
Click to collapse
Not as much as everyone else reading your post and trying to help!
BOBBYDS1 said:
AM HAVING TROUBLE DOWNLOADING MY CONTACTS
Click to expand...
Click to collapse
BOBBYDS1 said:
ANY ONE HAVE ANY TROUBLE DOWNLOADING THERE CONTACT LIST
Click to expand...
Click to collapse
BOBBYDS1 said:
I TRIED USING AN APPLICATION CALLED JETWARE WHICH WILL ALLOW ME TO DOWNLOAD BUT WHEN I MAKE A CALL IT WONT ALLOW ME TO HANG-UP THE CALL.
Click to expand...
Click to collapse
BOBBYDS1 said:
removing the jetware the bluetooth works fine but cant download contacts
Click to expand...
Click to collapse
So downloading contacts isn't your problem, hanging up whilst having jetware installed is? Better post would have been something along the lines of:
"I'm having trouble ending calls on my Kaiser using the end button on my Nokia CK-15 carkit. I installed the Jetware program to enable downloading contacts, but this stops the end key working on the Kaiser, before this it was working fine just the carkit couldn't download contacts. Does anyone know of any settings in Jetware I can try, that would restore the end key function, or other software that would still enable me to download contacts and have and end key?" - That might have got you an answer sooner...
Right, the phone as it comes doesn't support phonebook access, thus you won't be able to download your contacts. Actually, none of the Nokia bluetooth carkits support downloading contacts from the internal memory of a Windows Mobile device, probably because no Nokia uses Windows Mobile (yet).
You add something like Jetware which gives you the ability to access the phonebook, but then you are unable to end a call via the carkit. My best guess is Jetware does something which interupts the commands from the carkit. I'm also guessing your stuck with either having contacts download or and end call option. Add Jetware back and play with it's settings. You may get lucky. However bluetooth is very buggy and the only way to get 2 devices to work perfectly with eachother without running the risk of having to fiddle or loose something is to buy them from the same manufacturer and check they are fully compatible with eachother. Two devices from 2 manufacturers don't always work.
Here are some examples:
Old Ericsson headset, will work perfectly with my old HTC phone and can't even be seen by my Kaiser. Slightly newer one (that has an LCD for caller ID) will work once connected until I switch it off, then requires the old HTC phone to be soft reset before it will connect again. Works perfectly with the Kaiser. Brand new, cheapy Motorola headset does what it feels like with no consistency on my older HTC, again works perfectly on the Kaiser. My Nokia 610 carkit will connect to both phones, but whilst the older phone needs to be soft reset before turning off the ignition (otherwise the phone part of things crashes), the Kaiser will connect and disconnect just as Nokia intend. The carkit will only download SIM contacts. The fix posted above isn't really a fix, it's fooling the carkit into thinking that another phone (the Nokia N95) is the kaiser, downloading the contacts from it and then reconnecting the real Kaiser. Not a fix, but a brilliant workaround.
Also noticed that the CK-15 uses bluetooth version 1.2, the Kaiser bluetooth version 2. This might be something to do with it.
In short, I think you will have to live with either a phonebook, or an end function. Welcome to the wonderful world of bluetooth. It also doesn't help that Nokia hasa a history of making devices which don't work with anything other than another Nokia device...
Is there any way to change the kaiser to use bluetooth 1.2. Also is there a way to contact jetware besides email as they dont reply.
In your reply you state thAT Nokia devices csnt download from internal memory of kaiser phone, how can i set it up to download from the sim is there a way.
BOBBYDS1 said:
Is there any way to change the kaiser to use bluetooth 1.2
Click to expand...
Click to collapse
I seriously doubt anyone will be writing a bluetooth stack v1.2 for the Kaiser anytime soon. I also have a feeling that the versions are hardware, not software related, so its impossible. I think you may have to accept that the Kaiser and Nokia will never play nicely. Why don't you install Jetware, sync your contacts, then either disable it (I'm sure I remember an option in the settings when I tried it previously) or just delete the program? You could keep the installer cab on your device somewhere as its only 500kb for when you need to reinstall it?
If there isn't a phone number on the jetware homepage, I'm betting you can't call them. But I did notice there is an advanced set-up options menu. Did you try unchecking all the boxes apart from phonebooks? If the "hang-up/swap to incomming call" option is unchecked, Jetware should pass that command to the phones standard bluetooth software and give you back your end key. From the Jetware site:
"When this option is unchecked the Extension will allow hang up commands to be processed by the built-in code, which will disconnect all active voice calls."
If it's currently checked, try unchecking it.
BOBBYDS1 said:
In your reply you state thAT Nokia devices csnt download from internal memory of kaiser phone, how can i set it up to download from the sim is there a way.
Click to expand...
Click to collapse
Have you read the manual? In my 610 manual, it tells me I can choose to dowload phone, SIM, or phone and SIM memory. Does yours?
Now it seems that call waiting is not working in the bluetooth unit, itried the settings both ways in jetware but still no go. any ideas
Steve-C said:
Still not clear if your carkit is using headset or rSAP profiles. Can you either tell us the model of the carkit, or tell us if you can browse the internet from the phone whilst its connected to the carkit?
Punctuation good enough there Dark?! (JOKE!!)
Click to expand...
Click to collapse
Well, since you asked, it should be 'it's', not 'its'.
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!