Oreo developer options Bluetooth settings not sticking - Samsung Galaxy Note 8 Questions and Answers

I'm wondering if anyone else is having issues with this... Factory Unlocked version on OTA Oreo that got pushed out over the weekend. I was able to change the Bluetooth AVRCP to 1.6 but any other developer Bluetooth settings I change will go back to default if I go back into developer settings.

same here.

---------- Post added at 11:07 PM ---------- Previous post was at 11:06 PM ----------
travistyofjustice said:
I'm wondering if anyone else is having issues with this... Factory Unlocked version on OTA Oreo that got pushed out over the weekend. I was able to change the Bluetooth AVRCP to 1.6 but any other developer Bluetooth settings I change will go back to default if I go back into developer settings.
Click to expand...
Click to collapse
anmara said:
same here.
Click to expand...
Click to collapse
For me it auto selects the compatible codec depending on source. I guess it switches back between two connections.
Check to see if changes the used codec when connected to your headphones.
Cheers~

Are these settings what's keeping my connected devices from launching My Music app like Pandora when I get in my truck my stereo supposed to launch Pandora and I'm also supposed to be able to control it from the head unit which I'm not able to do since the update

tossero said:
---------- Post added at 11:07 PM ---------- Previous post was at 11:06 PM ----------
For me it auto selects the compatible codec depending on source. I guess it switches back between two connections.
Check to see if changes the used codec when connected to your headphones.
Cheers~
Click to expand...
Click to collapse
Yeah, that is it. Thanks!

travistyofjustice said:
I'm wondering if anyone else is having issues with this... Factory Unlocked version on OTA Oreo that got pushed out over the weekend. I was able to change the Bluetooth AVRCP to 1.6 but any other developer Bluetooth settings I change will go back to default if I go back into developer settings.
Click to expand...
Click to collapse
Having the same issue. My car's Sony headunit has been having connectivity issues since the Oreo update. (3 months or ago or something like that). I finally figured out the cause is the codec, the phone changes to AAC when the stereo is used to seeing SBC. I can switch it to SBC but as soon as the stereo tries to connect it goes to AAC. After connected I switch it to SBC and for the first time in 3 months I can listen to music in the car again without it disconnecting every 5 mins. The problem is it is a bit ridiculous to have to switch a setting back every single time I get into my car.
Then I just discovered that no matter what change I make to the bluetooth developer options they immediately revert back to what they were upon leaving the menu. No one has found a fix for this issue yet?

Related

Bionic: Bluetooth doesn't automatically reconnect?

My car's headunit has A2DP, and once paired, my OG would always reconnect when in range. The bionic doesn't seem to do this - so I have to open the wireless/network->bluetooth settings screen and manually force it to connect.
Not the end of the world, but it'd be nice to not have to do that everytime you get in the car.
Anyone else have any feedback on the Bionic's BT functionality?
This is not a problem I have experienced as mine reconnects no problem. What type of headset are you using. If problem persists I suggest turning headset off and back on, then it should reconnect. That beats navigating around the phone menu.
Sent from my DROID BIONIC using xda premium
I am having this same issue with my 2010 Ford Ford Fusion Hybrid with MS Sync and the Bionic. The phone connects fine but the A2DP does not. I wonder if there is a thread on the Moto support forums about this?
yutzyscott said:
This is not a problem I have experienced as mine reconnects no problem. What type of headset are you using. If problem persists I suggest turning headset off and back on, then it should reconnect. That beats navigating around the phone menu.
Sent from my DROID BIONIC using xda premium
Click to expand...
Click to collapse
I'm not using a headset, I'm using a JVC xr810 headunit (in-dash stereo ). Both the phone and A2DP connect quickly when I force it to under BT settings; but neither reconnects automatically, regardless of which device I turn power-on first.
WPWoodJr said:
I am having this same issue with my 2010 Ford Ford Fusion Hybrid with MS Sync and the Bionic. The phone connects fine but the A2DP does not. I wonder if there is a thread on the Moto support forums about this?
Click to expand...
Click to collapse
Interesting - so the phone auto-connects?
I am having a similar issue with my Sony Head unit. It will always automatically connect via the handsfree profile but the A2PD does not. I have to turn the Bluetooth on the headunit off and then back on and it then connects with both profiles. Its annoying to say the least.
WhiskeySlx said:
Interesting - so the phone auto-connects?
Click to expand...
Click to collapse
Yes it auto-connects to the phone, but for A2DP MS Sync says "Connection failed". I used to see this on my Droid X but it would always connect a second later anyway.
I am seeing the same issue with my bionic and pioneer audio head unit. When i force the connection manually it works. But the phone does not connect automatically. I have a friend with a bionic who is pairing with his mini without issues. We will test my phone on his car and his phone on my HU. This will at least tells us if the issue is with the phone itself or the other unit.
Same problem here. I have an Alpine IDA-001 deck. My OG Droid handled it fine.
WhiskeySlx said:
My car's headunit has A2DP, and once paired, my OG would always reconnect when in range. The bionic doesn't seem to do this - so I have to open the wireless/network->bluetooth settings screen and manually force it to connect.
Not the end of the world, but it'd be nice to not have to do that everytime you get in the car.
Anyone else have any feedback on the Bionic's BT functionality?
Click to expand...
Click to collapse
My 2011 Frontier has basic connection, and it always reconnects. But, when I paired my BIONIC, I deleted my DROID profile so there is only the one profile for it to connect to.
Could that be the key?
I posted about this here in the Motorola Support forum:
supportforums.motorola.com/thread/57688
---------- Post added at 10:29 PM ---------- Previous post was at 10:24 PM ----------
Ziggyrama said:
I am seeing the same issue with my bionic and pioneer audio head unit. When i force the connection manually it works. But the phone does not connect automatically. I have a friend with a bionic who is pairing with his mini without issues. We will test my phone on his car and his phone on my HU. This will at least tells us if the issue is with the phone itself or the other unit.
Click to expand...
Click to collapse
Looking forward to the results of this test!
johnlgalt said:
My 2011 Frontier has basic connection, and it always reconnects. But, when I paired my BIONIC, I deleted my DROID profile so there is only the one profile for it to connect to.
Could that be the key?
Click to expand...
Click to collapse
See my post below on how I resolved this. Thanks!
Sorry I am not allowed by the forum to post links yet so just paste this into your browser:
supportforums.motorola.com/thread/57688?tstart=0
WPWoodJr said:
See my post below on how I resolved this. Thanks!
Sorry I am not allowed by the forum to post links yet so just paste this into your browser:
supportforums.motorola.com/thread/57688?tstart=0
Click to expand...
Click to collapse
Thanks for the link! I'll see what I can do, but I don't have ford-media-sync.
I've already tried deleting all pairings, and restablishing, but... maybe I'll connect to my handsfree earpiece first, and then connect to the car's HU?
(I'm not sure if you closed that thread or what, but you might want to leave it open since others without the ford system can continue debugging/discussing?)
looking to get bt working in my nissan, the bionic connects but no sound, my eris connected no problem. deleted all profiles in car system with the bionic #1 priority.
WhiskeySlx said:
Thanks for the link! I'll see what I can do, but I don't have ford-media-sync.
I've already tried deleting all pairings, and restablishing, but... maybe I'll connect to my handsfree earpiece first, and then connect to the car's HU?
(I'm not sure if you closed that thread or what, but you might want to leave it open since others without the ford system can continue debugging/discussing?)
Click to expand...
Click to collapse
Maybe you should start a new thread at Moto support with your particular issue, so as not to confuse things.
My car has two ways to connect - via the media setup (A2DP) and via the phone setup (headset profile). I connected through the A2DP setup, but again I'm not sure that was what fixed the problem, or whether it was the deleting of some other phones from my Bluetooth list.
I've marked it Not Answered again over at Moto support.
hmmm... My TomTom Go! 730 reconnects just fine every time. Curious!
Mine also reconnects fine, but I don't have A2DP on the headunit so I can't help with that part.
cruiser86 said:
looking to get bt working in my nissan, the bionic connects but no sound, my eris connected no problem. deleted all profiles in car system with the bionic #1 priority.
Click to expand...
Click to collapse
Nissan's BT implementation is horrible. Moto had the best sound quality on my Altima, but that's not saying much.
I also had slow to nonexistent reconnects in my car as well, with having to force the connection manually to get it to connect.
OK, so today I got some help from my friend with another bionic and we tried my phone that is having issues with reconnecting on his mini that he has no issues with. So, the results are:
My phone was able to pair successfully with his Mini and it reconnected automatically when we turned the car off and on.
I did not try his phone in my car as I see no point. It is clear to me that the issue is with the combination of my Pioneer HU and the Bionic. I am going to conduct another test tomorrow. I will factory reset the BT unit thus wiping anything that could potentially be left over from my old D1 which could be interfering with the new pairing.
I do sincerely hope that clearing out the profiles will work, but I'm less than optimistic about the fact that it is a head unit as opposed to a general BT unit that was included by Nissan in my truck, which I'm almost positive is not controlled by the head unit itself.
At any rate, I had some issue with freezing the wrong app and factory reset my phone, and today it was not connecting (obviously, b/c for some odd reason it did not fetch my saved APNs, WP, BT profiles, etc. from my Google account, while when I first bought the phone it readily pulled everything so that all the info from my DROID transferred flawlessly.
Long story short, I had to re-pair with my truck, but it recognized (presumably by MAC address) my phone and the truck's female copilot announced that the phone was already stored in a profile and that I could just go ahead and connect to it. So I did.
Tomorrow, I'll let you know if it connects automatically or not.
---------- Post added at 10:18 PM ---------- Previous post was at 10:16 PM ----------
WPWoodJr said:
See my post below on how I resolved this. Thanks!
Sorry I am not allowed by the forum to post links yet so just paste this into your browser:
supportforums.motorola.com/thread/57688?tstart=0
Click to expand...
Click to collapse
Yeah, I'm a member over there as well, same username and everything. I was on the private panel that was studying the Call Quality issues that the original DROID was having with some people.
Glad that it worked out for you, and hopefully it works out for others. See my post just above for my little test to see if it works after a factory reset - I'm suspecting that in fact I'll need to delete that profile and start fresh....

Apt-X Support?

So, I tried choosing "Apt-X" from within the developer settings - but it doesn't stick. I know my headphones support it, and I looked up the SD660 - it has support for it as well. So, is there a way to enable Apt-X on the A2?
When you say "stick" u mean u can't select it? I can select either of the AptX options and they stay selected. But I'm not closing settings and shutting off the phone to check if it's still "sticking".
If you can't select them, it may be some other BT setting you've changed that's preventing those from being selected? All of my other BT selections are of the 'Auto' type.
AsItLies said:
[...] But I'm not closing settings and shutting off the phone to check if it's still "sticking". [...]
Click to expand...
Click to collapse
Thats exactly right - I can select them, but back out of settings and then check again and its back to the default (auto). I also tried changing the setting while my headphones were connected - in that case, it doesn't even change temporarily and will stay on AAC.
Same here it always goes back to default setting.. can't even use srgb mode
I think the device build is missing the aptx libraries. Currently aptx is not supported. Maybe they will integrate this in any coming release, but I wouldn't count on that.
Weird enough the device is able to use AAC apple Bluetooth driver.
Sent from my Mi A2 using Tapatalk
soulicro said:
Thats exactly right - I can select them, but back out of settings and then check again and its back to the default (auto). I also tried changing the setting while my headphones were connected - in that case, it doesn't even change temporarily and will stay on AAC.
Click to expand...
Click to collapse
After further reflection;
Remembered there are other USB settings that don't persist also. Change the USB connection type (say from Midi to Charge Only), back out, return...
It's not persistent either.
I found a way to work around it, for my purposes anyway, just leave the settings app up, don't close it. And sometimes just connecting with USB set it back, so would have to reset it again. But eventually it worked.
Kind of a pain. Because Android One and Lineage are so similar, I'd check in Lineage forums to see if there's a fix for that.
Small update: I installed Magisk and tried applying two separate modules that should add the Apt-X library files to the phone, but no luck. I've resigned to going back to stock and being hopeful that as community support starts ramping up for our device, we'll see a solution.
Oh well! AAC will need to hold us over 'til then.
need aptX support also
Just came across this in a MiA1 thread, it seems (like camera2API) that it has to be enabled (root access needed) for it to work;
https://forum.xda-developers.com/mi-a1/how-to/guide-enable-custom-bluetooth-audio-t3744371
I can't check, but I saw on another forum that someone enabled aptx this way (and noticed sound improvement): connect headphones, start palying music and only then enable aptx in developer settings. I think you should try it.
AlexX333BY said:
I can't check, but I saw on another forum that someone enabled aptx this way (and noticed sound improvement): connect headphones, start palying music and only then enable aptx in developer settings. I think you should try it.
Click to expand...
Click to collapse
Where did you read this?
pianistaPL said:
Where did you read this?
Click to expand...
Click to collapse
4pda.ru
AlexX333BY said:
I can't check, but I saw on another forum that someone enabled aptx this way (and noticed sound improvement): connect headphones, start palying music and only then enable aptx in developer settings. I think you should try it.
Click to expand...
Click to collapse
Could anybody verify this method?
AsItLies said:
Just came across this in a MiA1 thread, it seems (like camera2API) that it has to be enabled (root access needed) for it to work;
https://forum.xda-developers.com/mi-a1/how-to/guide-enable-custom-bluetooth-audio-t3744371
Click to expand...
Click to collapse
Does not work for me
soulicro said:
So, I tried choosing "Apt-X" from within the developer settings - but it doesn't stick. I know my headphones support it, and I looked up the SD660 - it has support for it as well. So, is there a way to enable Apt-X on the A2?
Click to expand...
Click to collapse
I have the same with my Sony MDR-1000X. They support aptx to. But the A2 won't stick to it
a5c said:
Could anybody verify this method?
Click to expand...
Click to collapse
doesn't work for me. it immediately switches back to sbc.
soulicro said:
Small update: I installed Magisk and tried applying two separate modules that should add the Apt-X library files to the phone, but no luck. I've resigned to going back to stock and being hopeful that as community support starts ramping up for our device, we'll see a solution.
Oh well! AAC will need to hold us over 'til then.
Click to expand...
Click to collapse
I used to have a MI Max and I was able to enable apt-x hd after installing some libraries with magisk. Which process did you follow? I still can't try it on my phone.
apt-x on Mi A2? Yesss! i did it! https://forum.xda-developers.com/mi-a2/help/apt-x-mi-a2-yesss-t3854813
rulezman said:
apt-x on Mi A2? Yesss! i did it! https://forum.xda-developers.com/mi-a2/help/apt-x-mi-a2-yesss-t3854813
Click to expand...
Click to collapse
Just got the official October update. Aptx is supported nativly now. No need to install any magisk module.

LDAC support missing after Pie Update

Has LDAC support been lost with the Pie Update? I just got the Android Pie update but now when I connect my Sony WH-1000XM2 (which had LDAC working fine in Oreo) to my Note 9, I see it’s only using AptX. When I got to Developer options, selecting LDAC no longer sticks.
When I search on XDA, I see that some users on other handsets that have gotten their Pie update have had similar issues with LDAC support. Does anyone have any insight into this?
EDIT: It turns out that, for whatever reason, when the Pie update happened, it turned off the LDAC setting in my headset's bluetooth profile. It just needed to be re-enabled.
jpbl1976 said:
Has LDAC support been lost with the Pie Update? I just got the Android Pie update but now when I connect my Sony WH-1000XM2 (which had LDAC working fine in Oreo) to my Note 9, I see it’s only using AptX. When I got to Developer options, selecting LDAC no longer sticks.
When I search on XDA, I see that some users on other handsets that have gotten their Pie update have had similar issues with LDAC support. Does anyone have any insight into this?
EDIT: It turns out that, for whatever reason, when the Pie update happened, it turned off the LDAC setting in my headset's bluetooth profile. It just needed to be re-enabled.
Click to expand...
Click to collapse
Sorry misread your post turn off dual audio from Bluetooth cog that’s why it don’t stick
N1NJATH3ORY said:
Step 1 Enable Developer Options
The first step is to enable Developer Options on your Galaxy S9. There is a quick and easy-to-follow guide on doing that for the Galaxy S9. Head to Settings –> About Phone –> Software Information and tap "Build Number" 7 times.
Next, navigate back to Settings and select Developer Options.
Step 2 Select a Bluetooth Audio Codec
Select "Bluetooth Audio Codec" from the list of Developer Options. Next, you can select any of the aforementioned codecs from a popup that will appear. Of course, to decide which to enable, it helps to know what the advantages are to each codec.
Click to expand...
Click to collapse
I edited my post a couple of hours ago saying the update just switched off the LDAC option.
jpbl1976 said:
I edited my post a couple of hours ago saying the update just switched off the LDAC option.
Click to expand...
Click to collapse
Sorry haven’t slept for over 30 hours I’m misreading see my update dual audio that’s why it don’t stick i was having same issue dude Bluetooth cog go there!!
jpbl1976 said:
Has LDAC support been lost with the Pie Update? I just got the Android Pie update but now when I connect my Sony WH-1000XM2 (which had LDAC working fine in Oreo) to my Note 9, I see it’s only using AptX. When I got to Developer options, selecting LDAC no longer sticks.
When I search on XDA, I see that some users on other handsets that have gotten their Pie update have had similar issues with LDAC support. Does anyone have any insight into this?
EDIT: It turns out that, for whatever reason, when the Pie update happened, it turned off the LDAC setting in my headset's bluetooth profile. It just needed to be re-enabled.
Click to expand...
Click to collapse
I'm facing similar issues and everytime I change the LDAC preference on developer options it always switched back to aptx. Have you found the solution of this issue?
maharrific said:
I'm facing similar issues and everytime I change the LDAC preference on developer options it always switched back to aptx. Have you found the solution of this issue?
Click to expand...
Click to collapse
Yes. Make sure your device is connected. Go to BT > Device > Click the settings gear > There should be an LDAC switch at the bottom.
Sent from my iPhone using Tapatalk
jpbl1976 said:
Yes. Make sure your device is connected. Go to BT > Device > Click the settings gear > There should be an LDAC switch at the bottom.
Click to expand...
Click to collapse
THANK YOU!!
This has been bugging me with my Fiio BTR3 always using AAC on my S8+. Result
jpbl1976 said:
Yes. Make sure your device is connected. Go to BT > Device > Click the settings gear > There should be an LDAC switch at the bottom.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
This helped me too! Enjoying LDAC on Android 9, Thanks
jpbl1976 said:
Yes. Make sure your device is connected. Go to BT > Device > Click the settings gear > There should be an LDAC switch at the bottom.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Jesus. 3 1/2 later and I hit this comment, which solves the problem!!!! It's unreal how ****ed up that issue is.
Thanks!
jpbl1976 said:
Yes. Make sure your device is connected. Go to BT > Device > Click the settings gear > There should be an LDAC switch at the bottom.
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Hello! I'm at a loss. There "should" be an LDAC switch at the bottom after clicking the gear icon. However, I don't have any such option. (LG Q7+ running Pie.) I used the headphone app to select Quality over Connection. The connection swaps from SBC to ACC. LDAC is available under Dev Options but I'm not able to utilize. Please help!

PIE Update - Car Bluetooth Issue

Received PIE OTA today. Everything seemed great until I got in the car to drove home from work. Phone connects to Bluetooth fine and stayed connected until I tried making a call. When I dialed a contact it started ringing properly over the car speakers then dropped and the status stopped showing on the car display. Phone still said it was connected to BT and phone audio routing through the Handsfreelink. I couldn't hear anything. Switching the call audio to Phone I was able to hear the person through the phone handset.
I've tried repairing to the car and restarting phone. I did not try calling through Android Auto I interface on the car, but will try that tomorrow.
Looking for similar issues I saw some hit for the Pixel devices, but it was on older beta builds of PIE.
Anyone else have this issue?
I don't have your exact issue, but my Bluetooth keeps disconnecting on my car. It worked fine on 8.1.
I also have the problem through the Android Auto app. I cleared cache from recovery and still have a problem. This makes Android 9 unusable for me...
ilatimer1 said:
I don't have your exact issue, but my Bluetooth keeps disconnecting on my car. It worked fine on 8.1.
Click to expand...
Click to collapse
Are you using a Galaxy watch? I used to have the same problem until I reset my watch then everything worked fine.
I would recommend you find out what's disconnecting the bluetooth through bluetooth > Advanced > Bluetooth control history and see if there are any apps turning off the bluetooth. Galaxy Wearable was constantly disconnecting my bluetooth when it was disconnected to my car's bluetooh and that's why I reset it.
I hope that helps.
---------- Post added at 01:40 PM ---------- Previous post was at 01:15 PM ----------
EzEddie said:
I also have the problem through the Android Auto app. I cleared cache from recovery and still have a problem. This makes Android 9 unusable for me...
Click to expand...
Click to collapse
I recommend you delete your phone 's profile from your car and reestablish it all over again after your reset your phone's bluetooth as well through settings > general management > reset > reset network settings. Bear in mind that this will erase all your bluetooth connections as well as wifi data.
Good luck.
Moe100021 said:
Are you using a Galaxy watch? I used to have the same problem until I reset my watch then everything worked fine.
I would recommend you find out what's disconnecting the bluetooth through bluetooth > Advanced > Bluetooth control history and see if there are any apps turning off the bluetooth. Galaxy Wearable was constantly disconnecting my bluetooth when it was disconnected to my car's bluetooh and that's why I reset it.
I hope that helps.
---------- Post added at 01:40 PM ---------- Previous post was at 01:15 PM ----------
I recommend you delete your phone 's profile from your car and reestablish it all over again after your reset your phone's bluetooth as well through settings > general management > reset > reset network settings. Bear in mind that this will erase all your bluetooth connections as well as wifi data.
Good luck.
Click to expand...
Click to collapse
I have already tried deleting my profile in car and clearing Bluetooth and network connections. I dont have a smart watch. The only thing left is a factory reset. But I've been reading the same problem has been reported on Pixel devices on Android Pie. I didnt see a fix though.
I have issues while playing music on Spotify and black player ex via Bluetooth on my pioneer deck in my car. The music will stop playing for like a second or two then resume. Reverting to 8.1 fixed it. I've tried a clean wipe as well.
enzyne said:
I have issues while playing music on Spotify and black player ex via Bluetooth on my pioneer deck in my car. The music will stop playing for like a second or two then resume. Reverting to 8.1 fixed it. I've tried a clean wipe as well.
Click to expand...
Click to collapse
Reverting will only fix it until the OTA installs it again though.
Wow. Thats definitely a deal breaker for me..Kind of glad Sprint hasnt received it yet! hope they fix it as I know how annoying that is.
Car BT disconnects after 5 min
EzEddie said:
Received PIE OTA today. Everything seemed great until I got in the car to drove home from work. Phone connects to Bluetooth fine and stayed connected until I tried making a call. When I dialed a contact it started ringing properly over the car speakers then dropped and the status stopped showing on the car display. Phone still said it was connected to BT and phone audio routing through the Handsfreelink. I couldn't hear anything. Switching the call audio to Phone I was able to hear the person through the phone handset.
I've tried repairing to the car and restarting the phone. I did not try calling through Android Auto I interface on the car, but will try that tomorrow.
Looking for similar issues I saw some hit for the Pixel devices, but it was on older beta builds of PIE.
Anyone else have this issue?
Click to expand...
Click to collapse
I have the same issue, Phone will connect fine initially but after like 5 minutes of playing music or calling Car will lose connection all together to BT in Phone (phone says it still connected for a couple of secs then drops as well) If I leave alone BT will connect again after a minute or so then disconnect again in a couple of minutes
I'm using Android Auto on my phone (My car does not have AAuto so use the phone as a display) so everytime BT connects disconnects AA launches
Tried resetting BT cache and data and repairing but everytime same thing.
EzEddie said:
Received PIE OTA today. Everything seemed great until I got in the car to drove home from work.
.....
Anyone else have this issue?
Click to expand...
Click to collapse
Are you using Android Auto on the phone by any chance?
What brand Car do you have?
I tested today after some BT resets and in the morning everything stayed connected so I thought it was fixed but in the drive home it disconnected 3 times while in a call !
I can confirm that this is happening specifically for me as well. Long time lurker/reader.
I'm confident I've isolated the issue to the Pie update. My Google search bringing me back 180° to here supports that.
I have that sinking feeling that this is gonna be an ongoing bugaboo. Let's hope I'm wrong!
I'm not an Android Auto user. The accompanied "drop signal" notification from my Galaxy Watch losing BT signal to phone to every few minutes is slowly eroding my sanity. Most recently on official AT&T CSAA clean wipe.
Cheers!
What's the current version of Pie on our Note 9 at the moment? From the looks of all these posts describing issues, I may have to permanently remain on Oreo for the entire life of this phone.
Hi, Annon here. Here's a real quirk... After receiving the update on my phone, I was happily driving home with music streaming through spotify via bluetooth and my husband decides to call me. The phone rings, I try to answer from the steering wheel and instead of answering the phone, it looks like it's connected the the car is still ringing the phone at me while not connecting to any voice. On my husband's end, he gets this really loud and annoying screeching sound so obviously he hangs up. But it doesn't stop there. Even though the call is disconnected (not that it ever stopped ringing on my end or connected), the phone continues to ring through my car UNTIL I GET HOME AND TURN OFF MY VEHICLE. Even after I turn off blue tooth and the radio console. It was the cherry on top of my crap day.
PIE in the face
I have exactly the same problem with a note9 connecting to a Discovery Sport. The phone connects for a short while then drops completely, then reconnects automatically and cycles like this for 3 or so times then seems to stabilise.
If I am on a call its a total nightmare, thinking of trying to revert to Oreo.
Anybody have a fix yet besides revert to oreo firmware?
Note 9 At&T on latest pie. Can confirm Bluetooth disappears from memory. Happens to car, headset, watch and have to re-pair over and over. Pretty frustrating. Was working perfectly prior to pie.
sledwich said:
I have exactly the same problem with a note9 connecting to a Discovery Sport. The phone connects for a short while then drops completely, then reconnects automatically and cycles like this for 3 or so times then seems to stabilise.
If I am on a call its a total nightmare, thinking of trying to revert to Oreo.
Click to expand...
Click to collapse
Same same my Note 9 constantly drops from my Discovery sport, I'm thinking about Odin flashing back to 8.1.
---------- Post added at 09:18 AM ---------- Previous post was at 09:06 AM ----------
sledwich said:
I have exactly the same problem with a note9 connecting to a Discovery Sport. The phone connects for a short while then drops completely, then reconnects automatically and cycles like this for 3 or so times then seems to stabilise.
If I am on a call its a total nightmare, thinking of trying to revert to Oreo.
Click to expand...
Click to collapse
dave5777 said:
Same same my Note 9 constantly drops from my Discovery sport, I'm thinking about Odin flashing back to 8.1.
Click to expand...
Click to collapse
I chatted with Samsung+ after I told them I already FDR'd my phone and everything else they asked about they recommended I get in contact with the warranty Dept so I can get another phone that will have the same issue once it updates to Pie
same issue here . Before describing issue please e-mail me if anyone has a fix ([email protected]) .
I have Galaxy Watch and a Honda Accord 2017. Everything went fine until upgrading to Pie. Now when phone is connected to the car system it rings but cant answer the call. Not on my steering wheel nor on my touch display. Furthermore if I try calling back It rings until person answers call and then it totally drops the call from my car system. Very annoying . If anyone comes with an answer to that please e-mail me the solution
Flashed back to 8.1 and no issues, I removed system permissions for the software update app and so far it hasn't automatically updated, I just get the persistent notification.
Same here - I just migrated from my oneplus 3t to the Note 9. And as a constant User of Android Auto, this is really a big big issue for me. Any hints besides Re-Odin?

Unstable Bluetooth bitrate

I have a serious problem with Bluetooth audio.
I have really good headphones, but they are quite old and there's no support for ldac or aptx (just sbc). However I'm coming from Huawei P20 Pro and I never had any problem with audio quality on that phone.
And what exactly I mean? When I'm listening the music I can hear occasional drops of audio bitrate. It's extremely annoying. And no, I'm not using different Bluetooth devices (but I was able to do this with Huawei which had older Bluetooth version [!]), everything about multiple output is disabled, that option in developer's menu is set to 1.6. I'm out of ideas and pretty disappointed that premium device like Note 9 have problems with basic functions like this.
Ps. It's not a problem with my device. Same thing is happening on my friend's Note 9.
connect headphone via Bluetooth then go to
developer mode enable it/Bluetooth audio codec/(select the code you needed)
At what volume do you listen via bluetooth?
I have the same issue with my car receiver and noticed that if i play it at max volume i experience that and if i play it at a slighty lower volume, one or two steps from max, the issue is gone (or so i hope) for now it seems it is resolved by lowering the volume from max, or it is fixed in CSC1
---------- Post added at 10:42 AM ---------- Previous post was at 10:06 AM ----------
Amit.A said:
connect headphone via Bluetooth then go to
developer mode enable it/Bluetooth audio codec/(select the code you needed)
Click to expand...
Click to collapse
How do you make it stay on the selected option? Regardless which option i select the moment i go back or out of developer options it goes back to SBC
u sure ure not streaming through some streaming app and not reading actuall media from internal storage?
I'd try local media and see how that behaves.
bober10113 said:
u sure ure not streaming through some streaming app and not reading actuall media from internal storage?
I'd try local media and see how that behaves.
Click to expand...
Click to collapse
I do not know about the OP but in my case regardles if it is a streaming service (deezer) local files (mp3) and sometimes with call audio, it does that.
_robojock_ said:
I do not know about the OP but in my case regardles if it is a streaming service (deezer) local files (mp3) and sometimes with call audio, it does that.
Click to expand...
Click to collapse
what build if android are you running?
bober10113 said:
what build if android are you running?
Click to expand...
Click to collapse
Devbase PIE CSC1 (It does it with all previous builds too.) I have also tried Dr. Ketan and other n9 roms same issue.
_robojock_ said:
Devbase PIE CSC1 (It does it with all previous builds too.) I have also tried Dr. Ketan and other n9 roms same issue.
Click to expand...
Click to collapse
im using viper audio and other audio mods.
not sure if its me that dosen't realise it but i dont think I've experienced any of this. i use only local media. i play it through power amp and set the audio output manually to high res output.
bober10113 said:
u sure ure not streaming through some streaming app and not reading actuall media from internal storage?
I'd try local media and see how that behaves.
Click to expand...
Click to collapse
No. I'm not using any streaming services. Just FLAC or 320kbps AAC files ripped directly from CD.
_robojock_ said:
At what volume do you listen via bluetooth?
I have the same issue with my car receiver and noticed that if i play it at max volume i experience that and if i play it at a slighty lower volume, one or two steps from max, the issue is gone
Click to expand...
Click to collapse
I'm not listening on max volume, but sometimes it's close (older or more niche music recorded and mastered properly).
Btw just tried listening on my dad's S8+ and it's the same, so Samsung generally has something broken with sbc codec which is rather disappointing.
Btw, I'm using European Exynos model.
That's probably why Samsung still includes the headphone jack with their phones. I don't use bluetooth that often, except in the car and I don't recall experiencing any issues with it. Maybe I don't pay attention to it, but I will this time and see.

Categories

Resources