Samsung admits Note incompatible with Android Auto

[CrashAlpha]

After many months of trying to find a solution for my problem with very low audio on my my Samsung Note Edge to my Kenwood DDX9902S via Android Auto, Samsung finally told me about the incompatibility. Here is what support said:

“I would like to inform you that, the Android Auto product you are referring is not compatible with the Note devices."

There has been no public announcement, there is nowhere to reference the issue, there is no reason given.

I have no idea if this is something Android can address.

 

[Cant Miss]

The more mods made to Android by OEMs, the more likely it doesn't work with the rest of the Android ecosystem. This is one of many reasons I avoid Samsung.

 

[TheLastPanda]

It mostly works with my Note 5.

 

[zelium]

I am very sad to hear from Samsung. I have a Note 4 (T-Mobile) and am suffering from low volume on Android Auto. I wished to have a firmware update to fix this issue, however, it sounded like Samsung is saying that they are not interested in the Android Auto issue by declaring 'Not Compatible.'

I am very tempted to replace my phone just because of Android Auto.

 

[zelium]

It mostly works with my Note 5.

TheLastPanda,

So, the Note 5 does not have a low volume issue? What do you mean by 'mostly works'? Does it mean that the Note 5 has an issue with Android Auto?

Thanks.

 

[TheLastPanda]

TheLastPanda,

So, the Note 5 does not have a low volume issue? What do you mean by 'mostly works'? Does it mean that the Note 5 has an issue with Android Auto?

Thanks.

Volume is fine. Most the issue is with the voice command functions. For example I'll say "take me to xxxxx" and it'll respond with "you have limited network access". Another issue is not being able to search for new stations for Google Play music.

 

[CrashAlpha]

It mostly works with my Note 5.

Since my Note Edge is basically a Note 4, it is quite possible that the Note 5 has solved the audio problem and the tech didn't know - which is actually my point. I was left to myself to solve this for six months. There was no informed help anywhere.

And - as is typical for this situation - Samsung cannot tell me why it is incompatible, which means I do not know if there will be any fixes for it. Is it a basic hardware issue? No idea, but I doubt it. Digital audio is not like analog audio, so it isn't as if there is a low quality VCA chip in the phone that doesn't have the power or fidelity to put out the signal.

I will be replacing my Samsung Note Edge, which is basically a Note 4. It's unlikely to be another Samsung product (this is my 2nd Note). After spending $1200 on a new nav/sound system for my car, I discovered this problem and no one, anywhere knew anything about the issue - not via Android, my provider, Kenwood or Samsung - until just now.

I find the entire Android Auto experience with its very limited ability to choose music (as a built in safety feature) far too limited. By contrast, I plugged in my girlfriend's iPhone, and Apple CarPlay came up instantly and offered me a much more pleasant experience - and with full audio. Granted, all those playing options may promote unsafe driving, but the AA experience gives you fewer options than you would have if you had a traditional CD player and AM/FM radio.

Panda, I am glad that you don't experience the audio issue, it is very, very frustrating. If I could modify the title of the post to reflect your experience, I would, but the quote I posted came directly from my Samsung Support chat window, and despite my prompts for more detail, Samsung tech support said no other info was available.

 

[Deputy1]

I have a Note 5 from T Mobile. It runs well on my 2016 Honda Civic. I had some initial issues, but it turned out to be an infotainment system issue. That was replaced, and it's been good since. I have USB bugging enabled, and plug my phone in AFTER I start the car. Location is enabled. Bluetooth was paired a while ago, and connects effortlessly. It's not perfect, as sometimes it doesn't recognize voice inputs, but that's most likely a reception issue.

 

[anon(7923)]

I have a Note 5 that works with my GMC Sierra. The annoying thing I'm encountering is after connecting I have to go into Settings and turn on USB Tethering for the system to see my phone. (Not exactly plug and play in my opinion)

 

[CrashAlpha]

Well, now we know that Samsung's unqualified support statement is inaccurate. The problems (probably the specific low audio problems) don't apply to the Note 5. As I said, support would not give me ANY additional info, they just say that AA is incompatible with the Note.

 

[Uncle Eliot]

AA on my Verizon Note 5 works on my 2016 Honda Accord. The Samsung rep is definitely wrong.

 

[Dr Claw]

After many months of trying to find a solution for my problem with very low audio on my my Samsung Note Edge to my Kenwood DDX9902S via Android Auto, Samsung finally told me about the incompatibility. Here is what support said:

“I would like to inform you that, the Android Auto product you are referring is not compatible with the Note devices."

There has been no public announcement, there is nowhere to reference the issue, there is no reason given.

I have no idea if this is something Android can address.

First, with your Note Edge:

Which carrier?
Which version of Android?
Which security update?

All of these will determine compatibility.

 

[CrashAlpha]

First, with your Note Edge:

Which carrier?
Which version of Android?
Which security update?

All of these will determine compatibility.

Carrier: Rogers Wireless
Version: 5.1.1
Security patch level: 2015-11-01


Again, my apologies for those with Note 5's - I am glad that you are not experiencing these problems. The rep simply said that the Samsung Note was not compatible, and would not give any more information. If I could change the title of the thread, I would.

If anyone knows of someone with a Note Edge or Note 4 that has no audio problems, I would love to know about it. Perhaps there is a version/patch carrier issue, but so far the complaints seem to be coming from pre-Note 5 users.

 

[DLCPhototography]

Just adding a data point:

I have the Note 3, Verizon, Android 5.0, and it works fine with Android Auto on my 2016 Hyundai Sonata.

 

[Got Milk]

Just wanted to let you know that I have the same head unit as you, the DDX 9902, and I am having the same low audio issue. So I know exactly what you are talking about.
Phone: Note 4
Carrier: T-Mobile
Version: 5.1.1
Security patch level: 2015-11-01

It was fine up when I was on Jelly Bean, and the version before 5.1.1.

I've looked at the bluetooth settings when the phone is connected to the device, and media audio will NOT turn on. Not sure if that means anything or not.

 

[CrashAlpha]

Two interesting comments:

1)

Just adding a data point:

I have the Note 3, Verizon, Android 5.0, and it works fine with Android Auto on my 2016 Hyundai Sonata.

2)

Just wanted to let you know that I have the same head unit as you, the DDX 9902, and I am having the same low audio issue. So I know exactly what you are talking about.
Phone: Note 4
Carrier: T-Mobile
Version: 5.1.1
Security patch level: 2015-11-01

It was fine up when I was on Jelly Bean, and the version before 5.1.1.

I've looked at the bluetooth settings when the phone is connected to the device, and media audio will NOT turn on. Not sure if that means anything or not.

My understanding is that once connected, the phone switches to USB Audio for higher fidelity. Some people have contested this, but none of them had a good understanding of Android Auto.

So, we have two users with a Note that reported that Android Auto works or worked with 5.0. We know the Note 5 works. Anyone know how to get DEEPER tech support than the agent that just said, “I would like to inform you that, the Android Auto product you are referring is not compatible with the Note devices."?

 

[laroucja]

I have a Note 4, with 5.1.1, the carrier is also Rogers and the head unit is a Kenwood 9702.
Had a "no audio" issue since the beginning. Samsung customer support was unable to help.
So I finally decided to reset the phone to factory default and the problem is now resolved,
even if I'd like to have it louder (compared to the radio's volume).

I believe there's an upgrade to MM coming soon but I fear about what will happen then,
seeing how much Samsung's support is so bad. And I don't expect Kenwood to be better, as they
protect themself by providing a list of compatible phones... That is a joke, since many unlisted phones
will work anyway.

 

[Tom Westrick]

I know it's not the same as AA, but most Samsung phones are compatible with MirrorLink, another in car method. Most car units that support AA should also support MirrorLink

 

[CrashAlpha]

Samsung's support is so bad. And I don't expect Kenwood to be better, as they
protect themself by providing a list of compatible phones

Both Samsung and Kenwood have basically been completely ignorant of the inner workings of Android. In fact, the Kenwood tech insists that AA works with Bluetooth Audio, whereas the AA community and tech reviewers insist it works with USB Audio. It seems to be a mystery to everyone. Samsung just has no idea, and just gave me the message quoted in the title, with no qualification or explanation.

 

[laroucja]

Yes it's USB Audio. I was able to listen to music using BT Audio but as soon as I plugged the cable, sound was gone as Google Play Music rely on USB Audio. My guess is the AA app on the phone should check for this issue (clearing some type of cache / driver after installing the app). Since I knew that the support people would tell me eventually to reset the phone to factory default, I did it before exchanging 100 emails! So to close the subject, let's blame Google for their App who needs some rework in order to be compatible with any phone. We're not in a closed (IOS) environment here...