Database Develop

Bluetooth problem.

Hello everyone,
I'm currently trying to send items from my old phone (Sony Ericsson W910i) to my new XDA Stellar but for some reason everytime I try and send anything to my XDA it appears to fail. Is there some simple reason for this or is it something I am doing wrong?
Any help will be appreciated.
Thanks.
Just one other thing. Is there any way I can disable the XDA Stellar from turning off after two minutes. I notice that if I am signed into Windows Live Messenger it'll disconnect after two minutes of not using the phone causing the connection to fail. Thanks again.

auto recieve incomming beams have to be on for bluetooth transfers being recieved
if you bluetooth is set to be always on your battery life will be rather short

Success. Thanks for the help

[Q] Is Bluetooth AVRCP 1.3 Working?

I am just wondering if anyone has had success getting Bluetooth Track metadata to be listed when syncing to bluetooth devices such as ones found in our cars. I have a Ford Focus and when I send media to the Ford Sync system using things like Pandora or BeyondPod, the only information listed is "Unknown" under the bluetooth category.
I know that this in particular was an Android issue and was not support through Android until 4.3 Jelly Bean. My previous phone was a Galaxy S3 rooted with Tasks latest rom running Android 4.3 and that device works properly. It syncs immediately with the car stereo and track listings are displayed properly as well as incoming text messages display on the screen.
This is not the case with my brand new Galaxy Note 3. I assumed that since it was running Android 4.3 and supported the newer bluetooth standards that it would perform similarly. That might have been my first mistake...assuming....but is anyone else having similar issues? Can someone point me in a direction that I might be doing something wrong? Im really hoping its just a setting I am missing and not something that Samsung decided to leave out or forgot about.
Thanks in advance.

Vgamer4550 said:
I am just wondering if anyone has had success getting Bluetooth Track metadata to be listed when syncing to bluetooth devices such as ones found in our cars. I have a Ford Focus and when I send media to the Ford Sync system using things like Pandora or BeyondPod, the only information listed is "Unknown" under the bluetooth category.
I know that this in particular was an Android issue and was not support through Android until 4.3 Jelly Bean. My previous phone was a Galaxy S3 rooted with Tasks latest rom running Android 4.3 and that device works properly. It syncs immediately with the car stereo and track listings are displayed properly as well as incoming text messages display on the screen.
This is not the case with my brand new Galaxy Note 3. I assumed that since it was running Android 4.3 and supported the newer bluetooth standards that it would perform similarly. That might have been my first mistake...assuming....but is anyone else having similar issues? Can someone point me in a direction that I might be doing something wrong? Im really hoping its just a setting I am missing and not something that Samsung decided to leave out or forgot about.
Thanks in advance.
Click to expand...
Click to collapse
It works on Note 3, in fact it works on all 4.3's now, I've had this issue on Nexus 4 and the last few new updates it started working.
You can see the name of song and artist and so on...

odeccacccp said:
It works on Note 3, in fact it works on all 4.3's now, I've had this issue on Nexus 4 and the last few new updates it started working.
You can see the name of song and artist and so on...
Click to expand...
Click to collapse
Thanks for the reply. I have had it working on a couple of 4.3 devices now, including my own Galaxy S3 running 4.3 and on all of those devices I really did not have to do anything besides sync the Phone with the device and send a Pandora track to it. Did you confirm it is working on the Note 3 in particular, and if so, did you have to turn any settings on or do anything special to get it to send the data?
As of right now, the song is played by the bluetooth device but no track information is displayed. This is also supposed to work for text messages, however I dont see that information displayed either. I want to confirm it is working on these Note 3 so I can try and narrow down a software or hardware issue.

Doesn't work on my Note, syncd with a Kenwood DDX429.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app

Vgamer4550 said:
Thanks for the reply. I have had it working on a couple of 4.3 devices now, including my own Galaxy S3 running 4.3 and on all of those devices I really did not have to do anything besides sync the Phone with the device and send a Pandora track to it. Did you confirm it is working on the Note 3 in particular, and if so, did you have to turn any settings on or do anything special to get it to send the data?
As of right now, the song is played by the bluetooth device but no track information is displayed. This is also supposed to work for text messages, however I dont see that information displayed either. I want to confirm it is working on these Note 3 so I can try and narrow down a software or hardware issue.
Click to expand...
Click to collapse
Maybe S3 did not the lates updates.
Nexus 4 is like the lates you can get them, and NOTE 3 just came out so should have latest.
I can confirm BT work amazing with all the proper displaying, SMS, pictures in phonebook and so on on my NOTE 3 N900W8 and my Ford SYNC, touch, latest firmware.
I did not have to do anything special, just paired and done.
Voice clarity and sound volume are amazing.
One problem BT creats a wakelocck "bluetooth_timer" trying to figure it out why.

Thanks for that.. So we have a Note 3 that works and one that doesn't. My Note 3 is an N900A on ATT..... I wonder if there is a carrier software issue at play here?
Can anyone else on different carriers confirm or deny the functionality of this feature?
Sent from my SAMSUNG-SM-N900A using Tapatalk 4

My n900a works great on my Kenwood ddx480
Sent from my SAMSUNG-SM-N900A using xda app-developers app

I get some bluetooth crashes when I try to use apps with bluetooth metadata, such as the Spotify app that I modified to have bluetooth metadata... It works on every device I have except the Note 3... I get an error that says Bluetooth share has crashed every so often when I try...

hotbyz168 said:
My n900a works great on my Kenwood ddx480
Sent from my SAMSUNG-SM-N900A using xda app-developers app
Click to expand...
Click to collapse
After a bit more testing, it looks like my text messages on my N900A actually do work with the car bluetooth unit. Which makes things a bit more odd since I know that before I got 4.3 on my S3, I was not able to receive any information on the display. Once I upgraded to 4.3 then everything just started working.
Since your N900A seems to work properly it makes me wonder if something is wrong with this particular phone. I'll have to test with a friends Note 3 and see what happens.
What apps were you using that worked properly? Did you do anything special (i.e. settings, app settings, etc) or like previously mentioned, did you just sync the phone and everything started working?

Vgamer4550 said:
Thanks for that.. So we have a Note 3 that works and one that doesn't. My Note 3 is an N900A on ATT..... I wonder if there is a carrier software issue at play here?
Can anyone else on different carriers confirm or deny the functionality of this feature?
Sent from my SAMSUNG-SM-N900A using Tapatalk 4
Click to expand...
Click to collapse
Try looking if there is a new soft for the car.
Also I've checked the "bluetooth_timer" wakelock problem, and if you press "cancel" when phone asks you to allow messages, and you don't check markalways allow for the phone book, the wakelock is not a problem. Also don;t set phonebook to auto download if you have the option, just do one time download.

odeccacccp said:
Try looking if there is a new soft for the car.
Also I've checked the "bluetooth_timer" wakelock problem, and if you press "cancel" when phone asks you to allow messages, and you don't check markalways allow for the phone book, the wakelock is not a problem. Also don;t set phonebook to auto download if you have the option, just do one time download.
Click to expand...
Click to collapse
Thanks for the suggestion, unfortunately I just upgraded the car software to the latest release as of last month. I also ruled that out because the S3 is working just fine. Where before it was on Android 4.3 I would not see any info on the screen.
At this point I might be leaning towards a defective phone, due to text messages appearing on the screen but no metadata, but I will try some more testing. I have access to a second Note 3 that I will try to sync up and see what happens.
I am hoping I get some more feed back before I resort to replacing the unit. We shall see.

Vgamer4550 said:
Thanks for the suggestion, unfortunately I just upgraded the car software to the latest release as of last month. I also ruled that out because the S3 is working just fine. Where before it was on Android 4.3 I would not see any info on the screen.
At this point I might be leaning towards a defective phone, due to text messages appearing on the screen but no metadata, but I will try some more testing. I have access to a second Note 3 that I will try to sync up and see what happens.
I am hoping I get some more feed back before I resort to replacing the unit. We shall see.
Click to expand...
Click to collapse
that sucks, but I highly doubte it's the phone defect, it's just software of the car or phone. Best bet is to wait for CM ROM for this phone CM worked always best for me re: car bluetooth.
Also some cars are just bad that way I tried my Nexus 4 on brand new Infinity FX fully loaded everything, the phone would not even connect to their system
My friend has Infinity EX35 2008, his Andorid phone would not allow him to play music through BT or cable, but I gave him my old crappy Iphone 3G and it works perfectly.
Try googling your car's smartphone supported list. Like this but for your car: here
My best suggestion keep the phone try not to get bothered by this and eventually it will work, I had to wait for about 5-6 month till it started working again. It all has to do with software updates and BT files.

odeccacccp said:
that sucks, but I highly doubte it's the phone defect, it's just software of the car or phone. Best bet is to wait for CM ROM for this phone CM worked always best for me re: car bluetooth.
Also some cars are just bad that way I tried my Nexus 4 on brand new Infinity FX fully loaded everything, the phone would not even connect to their system
My friend has Infinity EX35 2008, his Andorid phone would not allow him to play music through BT or cable, but I gave him my old crappy Iphone 3G and it works perfectly.
Try googling your car's smartphone supported list. Like this but for your car: here
My best suggestion keep the phone try not to get bothered by this and eventually it will work, I had to wait for about 5-6 month till it started working again. It all has to do with software updates and BT files.
Click to expand...
Click to collapse
I thought of that too, just wait for software patch or CM. Its my OCD that is getting in the way. The phone seems to work fine otherwise. I know its a little thing and it could also just be that the phone is newer then my car and car software so it may just take some time to get the kinks worked out.
I'll give it a few more days and see who else replies before I do anything rash I did live with the S3 just fine with no metadata before it got upgraded. Thanks for taking the time to reply. I'll keep your wakelock suggestions in mind as well.

Vgamer4550 said:
I thought of that too, just wait for software patch or CM. Its my OCD that is getting in the way. The phone seems to work fine otherwise. I know its a little thing and it could also just be that the phone is newer then my car and car software so it may just take some time to get the kinks worked out.
I'll give it a few more days and see who else replies before I do anything rash I did live with the S3 just fine with no metadata before it got upgraded. Thanks for taking the time to reply. I'll keep your wakelock suggestions in mind as well.
Click to expand...
Click to collapse
No problem, I've had lot's BT issues and been trying to solve then over the years. It's surprising not that many people use phones here with car BT's like that, so not many replies
Re: Wakelock, install this and see if you even have the problem, it would be in Kernel Wakelocks.
Also what car do you have? I'll keep an eye out if I hear anything, I'll let you know.

odeccacccp said:
No problem, I've had lot's BT issues and been trying to solve then over the years. It's surprising not that many people use phones here with car BT's like that, so not many replies
Re: Wakelock, install this and see if you even have the problem, it would be in Kernel Wakelocks.
Also what car do you have? I'll keep an eye out if I hear anything, I'll let you know.
Click to expand...
Click to collapse
Ford Focus Titanium 2013, I really appreciate it.
It always makes me laugh when I see so many people who have bluetooth in their vehicle or a fancy smartphone and have no idea what they can do together Its a curse being the tech guy and knowing what things can do and agonizing over some specific issue that the normal person/user doesn't even realize is there. I.E. metadata on the display.
Me: "The phone isn't working right"
Normal Person: "Does the car play the song?"
Me: "Ya"
Normal Person: "Then what's the problem"
Me: "Its supposed to do more tho...gahhhh"

Vgamer4550 said:
Ford Focus Titanium 2013, I really appreciate it.
It always makes me laugh when I see so many people who have bluetooth in their vehicle or a fancy smartphone and have no idea what they can do together Its a curse being the tech guy and knowing what things can do and agonizing over some specific issue that the normal person/user doesn't even realize is there. I.E. metadata on the display.
Me: "The phone isn't working right"
Normal Person: "Does the car play the song?"
Me: "Ya"
Normal Person: "Then what's the problem"
Me: "Its supposed to do more tho...gahhhh"
Click to expand...
Click to collapse
Hahah
I used to contact SYNC support and the answers where just crazy, that's when I started to do it myself, my problem is I don;t know Linux well

Can anyone else confirm or deny how well the AVRCP 1.3 is working on their Note 3 to show track information on their bluetooth devices.?
Please list model and carrier if possible.
Sent from my SAMSUNG-SM-N900A using Tapatalk 4

DanMc85 said:
I get some bluetooth crashes when I try to use apps with bluetooth metadata, such as the Spotify app that I modified to have bluetooth metadata... It works on every device I have except the Note 3... I get an error that says Bluetooth share has crashed every so often when I try...
Click to expand...
Click to collapse
I get this same error with Pandora modified. It works perfect on all other devices but my note3 on tmobile. Saddens me that I had to downgrade.

Bluetooth AVRCP issues
I have used multiple devices in my car and the song information always displays correctly. Ever since I purchased my Note 3, I have noticed that my car's
display gets stuck on the first song's information and never switches. The songs will correctly play and quality does not seem to be impaired.
I have not found a way to update my car's software but I will look into it. Just wanted to add my issues to the thread.
I have the AT&T SM-N900A version of the Note and my car is a 2012 Honda Civic Si.

smkcody said:
I have used multiple devices in my car and the song information always displays correctly. Ever since I purchased my Note 3, I have noticed that my car's display gets stuck on the first song's information and never switches. The songs will correctly play and quality does not seem to be impaired.
I have not found a way to update my car's software but I will look into it. Just wanted to add my issues to the thread. I have the AT&T SM-N900A version of the Note and my car is a 2012 Honda Civic Si.
Click to expand...
Click to collapse
Thanks for the reply, I would bet Samsung is doing things a little differently with these new phones and it might take a bit for the Manufacturers to catch up. I have also read on a couple other sites that AVRCP 1.3 may not be implemented properly and might need to be updated by Samsung, it is unknown at this point but hopefully I will be able to test this out with a Tmobile Note 3 this afternoon and report back on how things look.
With my ATT Note 3, I get text messages on the screen (which I didnt on the S3 prior to updating) but I dont get any track info.
Lets keep the confirmations coming, maybe we can narrow down a make and model and let the Carriers/Samsung know they need to fix something if its broke.

gear live connection issues

So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?

mstrpeter said:
So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?
Click to expand...
Click to collapse
All righty then, I guess its me

mstrpeter said:
So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?
Click to expand...
Click to collapse
That happened to me a couple of times too, but the watch usually had the cloud connection symbol thing while my phone said "connected, running sync loop." Turning bluetooth on and off and/or hitting the connect/disconnect button in the android wear app fixed the problem, but it seems to happen again whenever I leave the phone away from the watch and the BT connection is lost. It's doesn't seem to regain the connection on its own.
Is this is a CM11 problem, though? I also have CM11 (nightlies and milestones) and I had the same issue with my pebble watch. I'm thinking of going stock to see if it fixes the problem.

Komodo Rogue said:
That happened to me a couple of times too, but the watch usually had the cloud connection symbol thing while my phone said "connected, running sync loop." Turning bluetooth on and off and/or hitting the connect/disconnect button in the android wear app fixed the problem, but it seems to happen again whenever I leave the phone away from the watch and the BT connection is lost. It's doesn't seem to regain the connection on its own.
Is this is a CM11 problem, though? I also have CM11 (nightlies and milestones) and I had the same issue with my pebble watch. I'm thinking of going stock to see if it fixes the problem.
Click to expand...
Click to collapse
The thing that gets me is how inconsistent it appears to be. My phone is always in my pocket, and the cloud "disconnected" icon never appears.
however the link is clearly broken. I may do a wipe and install AOSP. I hope that is not the issue, ive really been enjoying the theme engine in cm11 along with all of the other customizability features

mstrpeter said:
The thing that gets me is how inconsistent it appears to be. My phone is always in my pocket, and the cloud "disconnected" icon never appears.
however the link is clearly broken. I may do a wipe and install AOSP. I hope that is not the issue, ive really been enjoying the theme engine in cm11 along with all of the other customizability features
Click to expand...
Click to collapse
I had the same issue with my nexus 5 running CM11. Two or three times throughout the day my watch would just stop receiving notifications, but it would still say it was connected. Often I noticed it because when I went to give it a voice command it would not register and then say it was disconnected until I swiped away the notification. I've just flashed over to Omni ROM to see if that fares better, since I'm pretty sure the issue was mainly with CM11 on this phone.

freekyfrogy said:
I had the same issue with my nexus 5 running CM11. Two or three times throughout the day my watch would just stop receiving notifications, but it would still say it was connected. Often I noticed it because when I went to give it a voice command it would not register and then say it was disconnected until I swiped away the notification. I've just flashed over to Omni ROM to see if that fares better, since I'm pretty sure the issue was mainly with CM11 on this phone.
Click to expand...
Click to collapse
Well I swapped to omnirom as well and sure enough, operation has been perfect. I also noticed while looking at obd2 apps that one had mentioned bluetooth connectivity issues on CM...
so i'd say, SOLVED.

My io2014 Samsung gear live won't connect to a new nexus 7 WiFi running 4.4.4 stock ROM.
Worked forma while, then flaky, nowmseems like zero connectivity.
Reset everything (on the watch and AR app), now it just won't pair.

jeffcrilly said:
My io2014 Samsung gear live won't connect to a new nexus 7 WiFi running 4.4.4 stock ROM.
Worked forma while, then flaky, nowmseems like zero connectivity.
Reset everything (on the watch and AR app), now it just won't pair.
Click to expand...
Click to collapse
The same exact thing is happening to me, just one day started to get in a "Pairing Loop" continually asking me to pair the watch to my phone. Upon pairing successfully and syncing some notifications the connection gets broken and immediately a new parigin code appears.

UPDATE:
I'm back on cm11 and everything is working properly. The problem is not the ROM, its the Kernel that comes baked in. Currently using elementalX Kernel and no issues.

Anyone able to run the app called utter!?

OK, I've been wrecking my brain trying to figure out why I can't get the app to run on my note 4. I've been to the devs. Xda page for the app. But he has been mia since February and my post keep getting ignored. I thought I'd make a last ditch effort and try here. Basically the app crashes when I try to launch it. I've downgraded Google search in hopes that it would fix the issue but no luck. I'm running a stock rooted 4.4.4. Any help would be appreciated.

Runs on my stock Rugby Pro running stock 4.1.2 Jelly Bean well enough to allow voice dial and texting from the bluetooth headset on my motorcycle helmet. Without the headset, it is hit-and miss because the app always tries online via wifi first. If in good wifi it still works, but when not good wifi it hangs for a variable (sometimes long) time looking for network. I loaded tasker to toggle wifi off/on when bluetooth is connected, and this seems to fix it well for use daily on my commute by motorcycle. If I drive, I'll probably need to use a bluetooth earpiece. I get the feeling that planets must align for this to work, and it does for me. Developer seems to have abandoned it. I think offline voice recognition - at a minimum for voice dial - should be a mandatory capability for all phones. (And S Voice does NOT work!) If I had not found a fix, I was planning to put my SIM back in the old Rugby II flip and just use the Pro for wifi. They are company phones, and I only went the smartphone route to get company email.
Loading the original Play store version worked for me initially, with no crash issues but still experimenting and learning commands. Then I loaded the latest beta (see page ~ 720 of his main thread) and it seems even better, and Tasker fixed the wifi issue somewhat.
Sent from my LePanII using Tapatalk 2

Thanks for the reply. I have the latest beta install but I still have no luck. I'm wondering if another app such as a antivirus app could be causing it to give me an error.

Doubt it is anti-virus (but possible). Most likely Google Search version or Android version. Check the official thread and find tge ones known to work. I'm just lucky to have a six-month old phone with three-year old software, I guess.

Android auto won't read my text messages to me

Hey, so I'm fairly new to android auto, having been in my 2016 civic for only a couple weeks. Everything is working great apart from the text message issue. Basically when I receive a text, it shows up on the home screen but when I click it, aa won't read it to me. The screen goes dark and the microphone icon goes blue as if it's trying to read it, but nothing happens and it returns to the home screen. Interestingly, if I press the microphone and use a voice command like 'read my last text message' aa says: "actually, I can't read your messages yet". Any help would be massively appreciated, it's really the only issue I've had so far with the vehicle or Android auto. Thanks.

Sorry, forgot to mention the phone is a nexus 5 with 6.0.1. The usb cord is the original that came with the phone, plugged into the usb port in the car designated for smartphone connection. Also I'm in Canada, if that matters.

Have you checked the permissions on the android app on your phone? Sounds like it doesn't have permissions to view your SMS?
Sent from my Nexus 6P using XDA-Developers mobile app

Yah I went to settings/apps/app permissions/sms and enabled all the apps in there. I also went to android auto, messenger, hangouts, Google play services, Google app, and contacts individually to make sure sms permissions were granted. I'm able to send a text from android auto, but it won't read out texts that I receive.

I'm having the same issue with my Galaxy S7 Edge running Android Auto on my Pioneer AVH-4100NEX. I went on vacation and my car sat for a while and now when I'm in Android Auto mode I can't receive and send text messages. I ask Google for the weather or to do a calculation and I get nothing. However, if I ask Google to dial someone whether in my contacts for not, it dials the number. Does this make any sense? There doesn't appear to be any official Android Auto support. I contact Pioneer and they told me my contacts weren't syncing with Android Auto which was strange enough when they said it, but given the fact that I don't get a reply when I ask GoogleNow for the weather means my contacts shouldn't have anything to do with it. Any help would be appreciated.
Thanks,
Matt

Same here: SEAT Ibiza with Full Link, Nexus 6 with 6.0.1 with SMS and WhatsApp. Could that be caused by some setting for language, text-to-speech? Everything else works fine, also sending messages.
PS: The system language ist German...

Similar.. it'll occassionaly read one message. But only one. Not always the first one per time I connect the phone to the car. Hyundai elantra 2017, vzw gs5.
Sent from my SM-T520 using Tapatalk

Made an account just so I could maybe help a few people. I'm using a Galaxy S6 with an AVH-4100NEX unit, and I was getting the same issue. Could send messages fine. Tap to read message - agonizing silence. Managed to solve it by factory resetting my device with Samsung's Smart Switch software. Backup. Reset to factory setting. Restore. Success. All the best!

**SOLVED** this problem has been driving me crazy, but I found the problem. Go to your Google Now settings, click "Voice" and turn OFF Bluetooth Headset.
Its to bad we can't have that on and use Android Auto. You have to choose either the built-in system in the car with Bluetooth or use Android Auto.
Anyways, I hope this solves your problems.

I was hoping Build A Wall's post was the fix but it didn't change anything at least for me. My GoogleNow works fine if I'm just using the phone in my hand. But ever since the end of June, when connected to my car, I can't text or ask for the weather but GoogleNow understand if I ask it to call someone or ask for directions. And even when it does work like making a call, it doesn't reply by saying "Calling Steve" like it used to. It's really weird. I'm wondering if Android Auto came out with an update and it screwed up things.

I don't think there has been another update, I just think it is primitive software that still doesn't quite work as it should. I have had similar problems that I have posted on here in that I could no longer send text messages but could still navigate etc. My situation now is that I have changed nothing on my Nexus or my car unit yet now it is working perfectly again! Hopefully, that is encouraging for you. I hope they will stabilise the software with some updates.
Sent from my Nexus 6P using XDA-Developers mobile app

@mpisani sorry that didn't work. It sounds like your problem is a little different than mine. I was having the same issues as the fiest post in this thread. It just wouldn't read my text to me, but everything else worked great.
I hope you get it figured out.

I turned off Bluetooth entirley before starting the car, it didn't help.

Having the same issue. Next text will come in, screen will show that there is a new text and from whom, but when you touch the card the microphone in the right corner turns blue while rest of screen changes tone a bit to show its in background but there is no audio of text message being read. ask google to read new texts and google says it cannot do that at this time. I'm wondering if it can tell thru gps if you are in a state that has banned all texting while driving and they are trying to cover their ass.

BuildAWall said:
**SOLVED** this problem has been driving me crazy, but I found the problem. Go to your Google Now settings, click "Voice" and turn OFF Bluetooth Headset.
Its to bad we can't have that on and use Android Auto. You have to choose either the built-in system in the car with Bluetooth or use Android Auto.
Anyways, I hope this solves your problems.
Click to expand...
Click to collapse
Thank you so much - it worked!!! My Voice commands did not work at all, no matter what I tried (which was a lot) - it just turned on, listened, turned off, repeated. This fixed it. Now I can again give voice commands, and it will read messages to me as well!
Sent from my Nexus 6P using Tapatalk

I've been having the same issues with my new 2017 Elantra. It's sporadic in reading it, sometimes it does and sometimes it doesn't. Interestingly, when reading messages it uses the other TTS service and not the one from Google Now.
Going to try the BT setting and see how it works. Also was wondering if the issue was from the SMS app.
Sent from my Nexus 6P using Tapatalk

tjk639 said:
I've been having the same issues with my new 2017 Elantra. It's sporadic in reading it, sometimes it does and sometimes it doesn't. Interestingly, when reading messages it uses the other TTS service and not the one from Google Now.
Going to try the BT setting and see how it works. Also was wondering if the issue was from the SMS app.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I don't believe it is the sms app purely because the fault is the same for me also with google hangouts which is of course a different app.
I'm really bored with it now sometimes working sometimes not no matter what solutions we come up with on here and try out.
Does Apple car play have all these issues with working just when it feels like it? Maybe we should all get iPhones so we can have software that just works as it should.
What about mirror link? Does anyone have experience with that? Or is it just music apps rather than communication like texting etc?

bradboyd said:
Hey, so I'm fairly new to android auto, having been in my 2016 civic for only a couple weeks. Everything is working great apart from the text message issue. Basically when I receive a text, it shows up on the home screen but when I click it, aa won't read it to me. The screen goes dark and the microphone icon goes blue as if it's trying to read it, but nothing happens and it returns to the home screen. Interestingly, if I press the microphone and use a voice command like 'read my last text message' aa says: "actually, I can't read your messages yet". Any help would be massively appreciated, it's really the only issue I've had so far with the vehicle or Android auto. Thanks.
Click to expand...
Click to collapse
Since this new update, my LG v10 Android Auto experience is horrible - essentially voice commands hardly every work - I'm not getting full prompts all the time (sometimes I get audio beeps before/after, sometimes just before, sometimes just after, sometimes never!). I've found I can guess at what I should be saying when it's listening for voice input to send a text, but I get zero feedback from the system. And my received texts will not read back. Very Very frustrating. As I work for a Honda dealer, our engineers have informed me it's all on Android. I think I'll fire up my iPhone today and go back to CarPlay for a while and hope the next release fixes my issues - it's just not usable in its current form.

The Bluetooth setting worked for me. Really odd fix that I would have never guessed to try. Thanks for the tip
Sent from my Nexus 6P using Tapatalk

So far, like others, that odd setting fixed it. Google Now update must have introduced it.