Bluetooth connection - Samsung Galaxy S10+ Questions & Answers

Hello everyone. I am enjoying my s10+. I don't have any issues with it except for one. I can't get Bluetooth audio to activate on my jvc double din in my car. The model is kw-340bt. On my pixel 3 xl it works with no problem. My s10+ can connect to the unit but it only lets me make phone calls. When I go to it in Bluetooth settings the audio option is off. When I try to turn it on it attempts to turn on then turns off. It will not come on. I have even reset my unit to factory settings and still the same thing happens. Does anyone have any other options I can try?

Yeah I'm having trouble myself with my ps4 controller, it connects but doesnt do anything! And even if I turn off the bluetooth it doesnt disconnect! What hell Samsung. It's so bad I have to force close / clear and data/ cache on bluetooth system app.

This happened to someone I knew when they used smart switch upgrading from their S5 to the S8+and moved over their settings. Unfortunately a factory reset was all they could find to fix it.

This may sound weird but I had problems getting my TV to connect. I had to go through the new Smartthings app, look for nearby devices. When I tapped on the TV it downloaded something and then I could connect.

Audio track data not updating on Bluetooth car audio head unit
Same. My previous phone (LG V20) was a breeze to connect via Bluetooth to car audio (Subaru Impreza MY15) & happily displayed the track information for my audio collection.
Fast forward to the new S10+ (exynos) & while it connects for audio, track information is only displayed for the first track & remains on-screen without change.
I've gone into developer options, and while I can change the Bluetooth AVRCP Versions from AVRCP 1.3, AVRCP 1.4 (default), AVRCP 1.5 & AVRCP 1.6, the Bluetooth Audio Codec Selection always defaults back to SBC.
Has anyone else had this problem?
Better yet, does anyone have a fix that I could apply???

Jimmy_Neutron said:
Same. My previous phone (LG V20) was a breeze to connect via Bluetooth to car audio (Subaru Impreza MY15) & happily displayed the track information for my audio collection.
Fast forward to the new S10+ (exynos) & while it connects for audio, track information is only displayed for the first track & remains on-screen without change.
I've gone into developer options, and while I can change the Bluetooth AVRCP Versions from AVRCP 1.3, AVRCP 1.4 (default), AVRCP 1.5 & AVRCP 1.6, the Bluetooth Audio Codec Selection always defaults back to SBC.
Has anyone else had this problem?
Better yet, does anyone have a fix that I could apply???
Click to expand...
Click to collapse
Every phone that I have ever had always goes back to default with the audio options. I never understood why. They give you options but you can't use the options. Makes no sense.

Related

Bluetooth on Android O Beta

Hey all,
Ever since opting into the Android O beta, my Nexus 6p has been working fine, except for connected to my car via BT. It connects, but just shows 'Unknown Artist' for any kind of track info, and if I switch playback apps (for instance, from Pocketcasts to Google Play Music), my phone disconnects from the car for a second or two, connects again, and still doesn't work. The car in question is a 2016 Mini Cooper S. Anyone else seeing issues like this? Works fine on 7.1.2.
ive got the same issue vw polo. audio plays via bluetooth but no artist info it just shows im connected to 6P and skip track controls dont work just mute and volume
Yeah, I don't even get audio. Nothing actually plays, car displays "unknown artist".
I have this as well on a 2017 toyota, calls etc work fine, just music dips out
sickfallout said:
Hey all,
Ever since opting into the Android O beta, my Nexus 6p has been working fine, except for connected to my car via BT. It connects, but just shows 'Unknown Artist' for any kind of track info, and if I switch playback apps (for instance, from Pocketcasts to Google Play Music), my phone disconnects from the car for a second or two, connects again, and still doesn't work. The car in question is a 2016 Mini Cooper S. Anyone else seeing issues like this? Works fine on 7.1.2.
Click to expand...
Click to collapse
what are the bluetooth settings in the developer setting section?
mine are as follows if you want to try them to see if it gives you some audio
Bluetooth AVCRP Version
AVCRP 1.6
Bluetooth Audio Codec
Streaming: SBC
Bluetooth Audio Sample Rate
Streaming: 44.1kHz
Bluetooth Audio Bits Per Sample
Streaming: 16 Bits/Sample
Bluetooth Audio Channel Mode
Streaming: Stereo
Bluetooth Audio LDAC Codec: Playback Quality
Streaming: Optimised for Audio Quality
MkBy said:
what are the bluetooth settings in the developer setting section?
mine are as follows if you want to try them to see if it gives you some audio
Bluetooth AVCRP Version
AVCRP 1.6
Bluetooth Audio Codec
Streaming: SBC
Bluetooth Audio Sample Rate
Streaming: 44.1kHz
Bluetooth Audio Bits Per Sample
Streaming: 16 Bits/Sample
Bluetooth Audio Channel Mode
Streaming: Stereo
Bluetooth Audio LDAC Codec: Playback Quality
Streaming: Optimised for Audio Quality
Click to expand...
Click to collapse
Thanks for the setting tips, I'll try them out tomorrow and report back.
No luck, same issue persists. I even tried usb-c to usb-a, but my Mini doesn't recognize it as an audio device that way Time to get a new head unit possibly.
No luck, still 'unknown artist' and no audio, even though my phone thinks it's connected and playing.
sickfallout said:
No luck, still 'unknown artist' and no audio, even though my phone thinks it's connected and playing.
Click to expand...
Click to collapse
Do you have this issue on 7.1.2 as well? Don't forget Android O is still in "beta" and I wouldn't be surprised if the BT is a little screwy still.
Triscuit said:
Do you have this issue on 7.1.2 as well? Don't forget Android O is still in "beta" and I wouldn't be surprised if the BT is a little screwy still.
Click to expand...
Click to collapse
Everything works fine on 7.1.2, I had to decide what was more important: working car audio or a much faster OS experience. Hopefully this is something that's either fixed in the release of O, or something my car manufacturer can patch into their system.
Not sure if this will help but my car seems to have pretty good luck with this technique and BMW/Mini ICE systems are similar. I use the aac codec keeping everything else default. I've had the issue a well where it's playing on my phone but not the car; the info also doesn't show. Restarting the phone right before starting the car or soon after seems to be relatively effective as it would then connect after the restarts and actually play the music correctly and show the info.
Not the best solution but hopefully this ends after the final is released.
Hi! I hope this helps. It seem like changing the setting (unchecking) for AAC audio helps with the issue. This seems to be a new feature in Oreo, so go to Bluetooth settings and in the little gear next to device it will popup with a couple of options, uncheck AAC.

OP5 Hogging Bluetooth

Hi all,
I'm running the latest OOS4.5.8 (rooted, Magisk (no modules installed)), and noticed for a whilst (including when on previous versions) that the phone will 'hog' bluetooth audio devices connected.
I've got a pair of bluetooth headphones that will pair and connect to 2 audio devices - but only play audio from one at a time (the first to start transmitting). Before I got my OP5 I could connect 2 phones easily and start playing from Spotify on either without any issues.
With the OP5 connected, I've noticed often no audio comes out when I play spotify on the other phone - until I turn off Bluetooth on the OP5 at which point the headphones announces the phone is disconnected and audio that was playing from the other phone comes out.
I think this has been happening for a while, but I've only just identified the actual cause (before this I thought it was a headphone / spotify problem).
Has anyone experienced this / have any suggestions?
There's a Bluetooth audio codec in the advanced menu in settings, would that make any change ?
If not then potentially unpair all the devices and then resync up, there are very few options in regards to Bluetooth, it's pretty much on or off.
Also (could be unrelated) I've read that you can only have one Bluetooth controller at a time connected for gaming, so maybe this is related ? Could a Kernel change possibly help?
Check the threads to see if it's listed.

Bluetooth with Android Oreo Final

With the final Oreo final, is anyone still having the BT issues from DP4? I think the issues still exist for me (playing music over BT in the car) but so far, simply turning the bluetooth off and then back on seems to fix it; this was not the case during DP4.
Yes, lots of issues with BT audio in the car for me. Doesn't work at all.
BMW 2-series, 2017
I'm trying wiping the phone entirely to see if that'll fix it.
Yeah, it auto connects to my head unit but doesn't play audio. Opening up Bluetooth, it shows the name of the head unit and says "connected (no audio)".
I have to unpair from my head unit and re-pair. Then it works normally.
Still annoying.
@ dan_delaney - yep having problems on the same car!
arts711 said:
@ dan_delaney - yep having problems on the same car!
Click to expand...
Click to collapse
May be an isolated issue related to the new audio codec. Everything is working the same for me in all my cars. I would dig around in Dev Settings and try toggling some of the BT audio settings. There are at least 6 BT settings and a BT logging tool there. For example, under BT Audio Codec there are MANY different codecs to choose from. Mine is using the default SBC now. I would start there. May be an easy fix. You may also RTFM (haha) and see which BT audio codec is preferred by this BMW head unit. @dan_delaney

H870 Bluetooth Issues with VW RNS 315

Hi,
I recently got my LG G6. I'm really satisfied with it. Especially the camera and the performance , but I have a problem with my hands-free equipment in my car .
Everytime I want to use the phone as audio source e.g. Spotify I would have to un-pair and pair the devices again .
I have a Volkswagen Passat 2014 with a RNS 315 and original hands-free equipment.
I can pair the devices without any problem. Also the "connected with audio equipment" option will be displayed on the phone. After a few seconds this option disappears in the overview of the connection details, only "use hands-free" and "sync phone book" will be displayed on the phone. Only in the overview of paired devices I can see that it is connected to the car as audio source. I can use the steering wheel buttons to switch between the tracks and the current title displays on the car radio.
The problem:
After the phone disconnects form the car (remove the key) and it reconnects gain (starting the car again) the phone do not recognize the A2DP protocol anymore and it just connects as hands-free without the ability to play music over the car speakers. I can use the steering wheel controls to switch the music title and the car also displays the current title, but the audio comes from the phone and not from the car speakers. But the car displays the phone as hands-free and audio source.
I had no problem with my Nexus 5X. I have already tried to clear the bluetooth cache and data. I have already tried with an other LG G6 and there was the same problem.
Is there any way to enforce A2DP even if the phone do not recognize it anymore?
The phone software is V11g-EUR-XX with security patch level 6th November 2017.
I hope anyone can help me, because I don't want to send it back.
Same issue here. I have to unpair and pair again if I want media playback to the car. I have tried pretty much every solution I came across and nothing worked apart from pairing again. Having said that, I think the problem is both with the RNS315 and the G6. I had a similar issue with the Note 3 but disconnecting and reconnecting was enough so I was using trigger to get around it. I have a small hope the oreo update may fix it.

Here's how to remove audio lag in carplay (sound, music and most importantly call lag) - requires Carlinkit dongle

Just posted the same on reddit:
Gonna be a long read, with many tips
So, I have an Android headunit and was using the built-in Carplay app Zlink. Now I'm using Carlinkit dongle for Carplay, and here's why.
I'm referring to Carlinkit wireless carplay dongle, not Carlinkit wired to wireless adapter - very important!
As you already know, using Carplay in Android headunits generally introduces some audio lag, especially on wireless carplay. For example it takes some time after you press "next song" until the current song stops and the next one starts. Same with pause. Especially with wireless Carplay.The biggest issue for me is during phone calls, when you ask a question, takes a while to get an answer, and you also end up talking over eachother.
This is what I did: In the recent versions of Autokit with a recent version of the box firmware there is an advanced option to route audio through car bluetooth instead of through box. (not sure exactly what version you need, but latest versions have this option)If you select this, you need to connect your phone to the headunit bluetooth also, not only to autokit's box bluetooth (you connect to box BT for wireless)
Doing this allows for all audio to go through headunit's bluetooth which is basically lag-free.
So my setup is like this:
Wired: phone is connected by USB to dongle, and by BT to unitWireless: phone connects to box BT then to box WiFi for Carplay, and meanwhile also connects to head unit's BT for audio.
Advantages:
- No more lag when switching music or making calls, even in wireless carplay mode
- When the unit detects a call, it might do something smart that you want. Mine has a different volume for in-call, so I can now have louder phone calls without manually changing volume
- Since the phone is playing music over the BT connection, the unit is now aware that music is playing and knows artist and track name and it might display it somewhere, maybe have an overlay when changing tracks. Might be nice if you switch outside Carplay to some other screen/app on the unit.
- No more lag
- If unit has proper echo cancellation, it should work better, as BT is better controlled by the unit, unlike Carplay solutions which can have various delays that the unit cannot counter easily.
- If you were using built-in Carplay before (like I was), you wouldn't be able to use wireless Carplay and have internet from a hotspot, since unit's wifi was busy. If you switch to using Carlinkit dongle with Autokit, you free up unit's wifi and can now use a hotspot.
- Did I mention no more lag?
Disadvantages:
- Seems to use more battery when in wireless carplay mode, I think BT is less power efficient. My unit has BT 4.0, if yours has BT 5.0 maybe this would be better.
- This is a minor annoyance, but if your headunit BT is slow to connect to the phone (mine is) and you start playing music as soon as you have Carplay working (or have autoplay enabled), you might have music coming out of the phone speaker(s) for a few seconds, until unit BT connects and music goes to BT.
Beware the following:
- When using BT to listen to music, the volume on the phone matters, so make sure to turn it up to max. This volume level will be saved separately from usual phone volume though, so it's not a problem.
- Latest version of Autokit didn't find box updates for me, so if this option is not in the advanced settings, you might need to revert to an older version and use that to update box, then update app.
- After making this setup and trying to make a call, you might not hear anything, as the phone might use the carplay connection instead of the bluetooth connection. Just switch output from the phone "audio" button, and it seems to remember it for next times.
- Depending on the headunit and the software, when you get a call with this setup, headunit might decide to switch to it's own bluetooth phone app or just show an overlay. If it switches and it bothers you, try to find a solution specific to your unit. If it's an overlay and you want to remove it, what worked for me was going into android settings for app permissions and removing permission to draw over other apps for the unit's bluetooth app.
thanks for your post; i have a carplay dongle connected to an android headunit; when i call someone they have a very annoying echo voice. i wish it improves when my phone it connect to headunit bluetooth for calls
Are you able to get navigation audio using this option? I have the same dongle and was hoping I would get navigation too but I only get music audio. If I say "Hey Siri" just before Waze/Google Maps is about to prompt then I can hear the audio but doesn't really help me when driving. Looks like in my car the Navigation audio is going over the Siri channel? Not sure if anyone has a work around for that. Could be the way my car has bluetooth setup -- it's a 2012.
Can you provide a link or exact model for the "Carlinkit wireless carplay dongle"?
RPG0 said:
Just posted the same on reddit:
Gonna be a long read, with many tips
So, I have an Android headunit and was using the built-in Carplay app Zlink. Now I'm using Carlinkit dongle for Carplay, and here's why.
I'm referring to Carlinkit wireless carplay dongle, not Carlinkit wired to wireless adapter - very important!
As you already know, using Carplay in Android headunits generally introduces some audio lag, especially on wireless carplay. For example it takes some time after you press "next song" until the current song stops and the next one starts. Same with pause. Especially with wireless Carplay.The biggest issue for me is during phone calls, when you ask a question, takes a while to get an answer, and you also end up talking over eachother.
This is what I did: In the recent versions of Autokit with a recent version of the box firmware there is an advanced option to route audio through car bluetooth instead of through box. (not sure exactly what version you need, but latest versions have this option)If you select this, you need to connect your phone to the headunit bluetooth also, not only to autokit's box bluetooth (you connect to box BT for wireless)
Doing this allows for all audio to go through headunit's bluetooth which is basically lag-free.
So my setup is like this:
Wired: phone is connected by USB to dongle, and by BT to unitWireless: phone connects to box BT then to box WiFi for Carplay, and meanwhile also connects to head unit's BT for audio.
Advantages:
- No more lag when switching music or making calls, even in wireless carplay mode
- When the unit detects a call, it might do something smart that you want. Mine has a different volume for in-call, so I can now have louder phone calls without manually changing volume
- Since the phone is playing music over the BT connection, the unit is now aware that music is playing and knows artist and track name and it might display it somewhere, maybe have an overlay when changing tracks. Might be nice if you switch outside Carplay to some other screen/app on the unit.
- No more lag
- If unit has proper echo cancellation, it should work better, as BT is better controlled by the unit, unlike Carplay solutions which can have various delays that the unit cannot counter easily.
- If you were using built-in Carplay before (like I was), you wouldn't be able to use wireless Carplay and have internet from a hotspot, since unit's wifi was busy. If you switch to using Carlinkit dongle with Autokit, you free up unit's wifi and can now use a hotspot.
- Did I mention no more lag?
Disadvantages:
- Seems to use more battery when in wireless carplay mode, I think BT is less power efficient. My unit has BT 4.0, if yours has BT 5.0 maybe this would be better.
- This is a minor annoyance, but if your headunit BT is slow to connect to the phone (mine is) and you start playing music as soon as you have Carplay working (or have autoplay enabled), you might have music coming out of the phone speaker(s) for a few seconds, until unit BT connects and music goes to BT.
Beware the following:
- When using BT to listen to music, the volume on the phone matters, so make sure to turn it up to max. This volume level will be saved separately from usual phone volume though, so it's not a problem.
- Latest version of Autokit didn't find box updates for me, so if this option is not in the advanced settings, you might need to revert to an older version and use that to update box, then update app.
- After making this setup and trying to make a call, you might not hear anything, as the phone might use the carplay connection instead of the bluetooth connection. Just switch output from the phone "audio" button, and it seems to remember it for next times.
- Depending on the headunit and the software, when you get a call with this setup, headunit might decide to switch to it's own bluetooth phone app or just show an overlay. If it switches and it bothers you, try to find a solution specific to your unit. If it's an overlay and you want to remove it, what worked for me was going into android settings for app permissions and removing permission to draw over other apps for the unit's bluetooth app.
Click to expand...
Click to collapse
What is your box version?
When I try audio routing, on my iPhone still it shows Carplay as sound output option.
I tried this same option, but when my iPhone connects to wireless CarPlay, the head unit (not the dongle) turn off the bluetooth automatically, anyone knows how to stop this?
RPG0 said:
Just posted the same on reddit:
Gonna be a long read, with many tips
So, I have an Android headunit and was using the built-in Carplay app Zlink. Now I'm using Carlinkit dongle for Carplay, and here's why.
I'm referring to Carlinkit wireless carplay dongle, not Carlinkit wired to wireless adapter - very important!
As you already know, using Carplay in Android headunits generally introduces some audio lag, especially on wireless carplay. For example it takes some time after you press "next song" until the current song stops and the next one starts. Same with pause. Especially with wireless Carplay.The biggest issue for me is during phone calls, when you ask a question, takes a while to get an answer, and you also end up talking over eachother.
This is what I did: In the recent versions of Autokit with a recent version of the box firmware there is an advanced option to route audio through car bluetooth instead of through box. (not sure exactly what version you need, but latest versions have this option)If you select this, you need to connect your phone to the headunit bluetooth also, not only to autokit's box bluetooth (you connect to box BT for wireless)
Doing this allows for all audio to go through headunit's bluetooth which is basically lag-free.
So my setup is like this:
Wired: phone is connected by USB to dongle, and by BT to unitWireless: phone connects to box BT then to box WiFi for Carplay, and meanwhile also connects to head unit's BT for audio.
Advantages:
- No more lag when switching music or making calls, even in wireless carplay mode
- When the unit detects a call, it might do something smart that you want. Mine has a different volume for in-call, so I can now have louder phone calls without manually changing volume
- Since the phone is playing music over the BT connection, the unit is now aware that music is playing and knows artist and track name and it might display it somewhere, maybe have an overlay when changing tracks. Might be nice if you switch outside Carplay to some other screen/app on the unit.
- No more lag
- If unit has proper echo cancellation, it should work better, as BT is better controlled by the unit, unlike Carplay solutions which can have various delays that the unit cannot counter easily.
- If you were using built-in Carplay before (like I was), you wouldn't be able to use wireless Carplay and have internet from a hotspot, since unit's wifi was busy. If you switch to using Carlinkit dongle with Autokit, you free up unit's wifi and can now use a hotspot.
- Did I mention no more lag?
Disadvantages:
- Seems to use more battery when in wireless carplay mode, I think BT is less power efficient. My unit has BT 4.0, if yours has BT 5.0 maybe this would be better.
- This is a minor annoyance, but if your headunit BT is slow to connect to the phone (mine is) and you start playing music as soon as you have Carplay working (or have autoplay enabled), you might have music coming out of the phone speaker(s) for a few seconds, until unit BT connects and music goes to BT.
Beware the following:
- When using BT to listen to music, the volume on the phone matters, so make sure to turn it up to max. This volume level will be saved separately from usual phone volume though, so it's not a problem.
- Latest version of Autokit didn't find box updates for me, so if this option is not in the advanced settings, you might need to revert to an older version and use that to update box, then update app.
- After making this setup and trying to make a call, you might not hear anything, as the phone might use the carplay connection instead of the bluetooth connection. Just switch output from the phone "audio" button, and it seems to remember it for next times.
- Depending on the headunit and the software, when you get a call with this setup, headunit might decide to switch to it's own bluetooth phone app or just show an overlay. If it switches and it bothers you, try to find a solution specific to your unit. If it's an overlay and you want to remove it, what worked for me was going into android settings for app permissions and removing permission to draw over other apps for the unit's bluetooth app.
Click to expand...
Click to collapse
Wait, What??? the only way to remove the 3 second lag from headunit with zlink is by buying a dongle ??? I paid extra for Carplay/Android Auto Headunit.
And the 3 seconds delay is driving me nuts. This happens even without the zlink app open.
The dongle is carlinkit Autokit (CPC200-CCPA)? It is specially made for Android head units.

Categories

Resources