Related
Hello. I've only joined today as a result of the Samsung 9305 Jellybean Update 4.3.
I am on an EE T-Mobile UK i9305 LTE handset in factory condition, no rooting or any other modifications. I have just upgraded to the new update on 20 Jan 2014.
Apart from all the usual observations such as WI FI and battery life, I have another issue which I cannot find anywhere else.
Before the update and for the last year my i9305 worked fine with the bluetooth in my car. I have a 2004 X3 E83 BMW and the car paired absolutely fine. I would talk and connect with no problems. Since the update the phone connects to the bluetooth then drops after 3 seconds.
I have done the following:
Unpaired the phone and repaired;
Deleted the cache for bluetooth
Deleted the cache from the engineers mode
Samsung tells me that I now need to go to the dealer to ask them to upgrade my bluetooth software in the BMW, I explained that 1st I'm not sure if that could be done and second that would cost me money and time for something that was working perfectly fine 3 days ago for over a year. The only change is the update. Therefore I explained that there should be another update to correct this and all other problems immediately.
Has anyone encountered this issue with a car's bluetooth and anyone been able to figure out a fix. I don't really want to go down the avenue of trying a factory reset and testing if that works.
Many thanks
Havent had any issues like that with stock 4.3 and bluetooth so may or may not help but try clear the data for bluetooth share in application manager as well as un pair and re pair the device again after that has been done
I have flashed the official google images. MRA58K and MRA58R - both have the following issue:
I'll outline it logistically:
* I connect bluetooth to my 2013 Honda Accord
* When I dial a phone number from the nexus device OR using the car's bluetooth menu the bluetooth disconnects
* the phone continues to call the person
* after the person answers the phone and says hello a few times, the phone reconnects to bluetooth
* the phone call goes on as normal. At this point I have a 20% rate of failure where the phone call connects for a few minutes and then the phone just hangs up on the person randomly. The other 80% of the time the phone call goes correctly without hitch after this point.
I've found the following thread here that seems to outline my problem exactly: https://productforums.google.com/forum/#!topic/nexus/SaoZyWfkX94;context-place=forum/nexus
Add me to the list of people whose Bluetooth connectivity has suffered after upgrading from Lollipop to Marshmallow (on my Nexus 5). All was working perfectly in my 2015 Honda Accord, connecting to their HandsFreeLink software to make and receive calls. Now calls do go out, but you cannot hear the phone "ringing", and the radio comes back on again until the call is completed, when you suddenly hear the caller say "hello." Also many instances of poor call connection (unusable screeching sounds or very garbled speech). Did everything except reset to factory settings: wiped cache, reset the phone to the car's bluetooth, etc. Waiting hopefully for the 6.0.1 update to save the day….
Click to expand...
Click to collapse
Is anyone else experiencing this? How can I fix?
Me too
I have the same exact problem with my kia.
It is really annoying, can anyone help?
arsenik13 said:
I have flashed the official google images. MRA58K and MRA58R - both have the following issue:
I'll outline it logistically:
* I connect bluetooth to my 2013 Honda Accord
* When I dial a phone number from the nexus device OR using the car's bluetooth menu the bluetooth disconnects
* the phone continues to call the person
* after the person answers the phone and says hello a few times, the phone reconnects to bluetooth
* the phone call goes on as normal. At this point I have a 20% rate of failure where the phone call connects for a few minutes and then the phone just hangs up on the person randomly. The other 80% of the time the phone call goes correctly without hitch after this point.
I've found the following thread here that seems to outline my problem exactly: https://productforums.google.com/forum/#!topic/nexus/SaoZyWfkX94;context-place=forum/nexus
Is anyone else experiencing this? How can I fix?
Click to expand...
Click to collapse
I am also having almost the exact same issue.
I have yet to find a working solution. In the meantime, all I could do is go back to 5.1.1.
Also, M developer preview 1, 2 and 3 all work fine.
poncespr said:
I am also having almost the exact same issue.
I have yet to find a working solution. In the meantime, all I could do is go back to 5.1.1.
Also, M developer preview 1, 2 and 3 all work fine.
Click to expand...
Click to collapse
This must be a very widespread issue, I wonder why it's not getting any coverage here?
arsenik13 said:
This must be a very widespread issue, I wonder why it's not getting any coverage here?
Click to expand...
Click to collapse
OK. I finally got it working right.
I will tell you what I did in case you want to try it, if you are comfortable flashing a CM13 alpha.
While on 5.1.1 lmy48y, I flashed CM13 Alpha cm-13.0-20151124-UNOFFICIAL found here.
And gapps found here.
I kept the 5.1.1 bootloader and radio, and have not had any issues.
I am using Elemental kernel 3.06.
And I also formatted my device to remove encryption.
So far so good. No more weird behavior on my CRV blue-tooth.
I don't think that the kernel makes a difference, but that is what I am using and have not tried with any others after getting this working combination.
Hope this helps.
6.0.1 Stock fixes bluetooth issues.
Just in case anyone is still having these issues. I just downloaded and installed stock 6.0.1 and everything is now working great.
Cheers.
poncespr said:
Just in case anyone is still having these issues. I just downloaded and installed stock 6.0.1 and everything is now working great.
Cheers.
Click to expand...
Click to collapse
I am running stock 6.0.1 and my bluetooth doesn't work. At all. Annoying.
6.0.1 introduced a slew of other Bluetooth issues. Because it links phone and BT accessory volume levels (before this they were separate,) this causes some headsets to be stuck on max volume no matter what you do. Rendered my LG HBS-730 useless.
Am getting 100% bluesleep / msm_serial_ds wakelocks on various ROMs using a pebble watch. This makes using Bluetooth and my watch unusable due to radically reduced battery. Any ideas?
Sent from my Nexus 6 using Tapatalk
Chahk said:
6.0.1 introduced a slew of other Bluetooth issues. Because it links phone and BT accessory volume levels (before this they were separate,) this causes some headsets to be stuck on max volume no matter what you do. Rendered my LG HBS-730 useless.
Click to expand...
Click to collapse
True. I had not noticed the bluetooth volume bug, but it is there.
They finally fixed it in N Preview. Hopefully this rolls out as part of monthly security updates for 6.0.1 as well.
I am on N, and Since Marshmallow, i have not been able to pair in my Acura TL bluetooth. Same issue with N. Every other phone before or after has or is working well with my Acura TL. So I KNOW it's not the Vehicle, and I know it's not the phone. I can pair my Nexus 6 with a bluetooth speaker, a bluetooth headset, a NON factory bluetooth DIN radio, and a Bluetooth NON factory In vehicle hands free (GROM) without any issues. Somehow, there is a slight change that is affecting CERTAIN devices prior to marshmallow, that is present now.
I have read about activating the GPS, and trying to sync the phone to the Acura Bluetooth... this has made NO difference. Bluetooth will eventually timeout.
Hello everyone,
So I've been having some troubles with Bluetooth on two devices running nougat, and I haven't really found any good resolutions.
I've been practicing app development lately and was originally Bluetoothing the apk to my phones to test out (email or cord has been the obvious solution but I get obsessive and wanted to figure out why bt would not work). Weird thing is it was working fine for a couple attempts then it would not work. Laptop is an msi apache, it will connect and transfer to other devices running marshmallow and cyanogenmod no problem. But my s6 and note 5 on nougat will not work. It will attempt to send, time out and say device disconnected AND THEN I'll get the prompt on my phone asking to accept the file, but of course it's already disconnected.
Tried clearing cache, resetting network connections, disabling Wi-Fi, re pairing devices on the phones.
On my laptop I changed the device type from 128bit encryption to 40-58 or what ever it was.
Repaired, restarted, tried changing support services to a local service login type, reinstalled the bt driver... I'm assuming it's the phone but just wanted to list a couple things I tried.
Any ideas or just an android 7.0 issue?
Thanks.
Edit- first post and I put it in the wrong section, sorry about that! Should be in qa
What rom are you using? Try another perhaps, I've had lots of issues with Bluetooth over the years due to buggy roms.
Just installed latest firmware (ERC1) on my Note 5 SM-N920T and bt don't work plz help. Just came off a wipe ESF lost IMEI LOST ALL carrier signal no sim card detected. Finally got it back and no bluetooh.
Something similar happens to me
Ghost19841984 said:
Just installed latest firmware (ERC1) on my Note 5 SM-N920T and bt don't work plz help. Just came off a wipe ESF lost IMEI LOST ALL carrier signal no sim card detected. Finally got it back and no bluetooh.
Click to expand...
Click to collapse
Something similar happens to me I installed the ERC1 in my note5 N920T, the wifi does not work well, and the bluethooth either. sorry for my English
I've heard this a bug with Oreo, but I've had this issue since Nougat. Essentially, I've tried connecting several Bluetooth devices to my OnePlus 3T with OOS 5.0.3 rooted w/ Magisk, and while I can get music and notifications to play, I can neither hear nor speak through the phone options using Bluetooth. I've searched for hours on Google as to why this may be happened, and while there are hundreds of reports and instances of this happening, there isn't a single consistent solution.
I've tried messing with the settings, codecs, deleting cache, deleting data from Bluetooth, repairing devices, deactivating Google Now, resetting the phone, you name it.
Is this a problem that is still prevalent with Oreo? This is probably the stupidest unsolvable thing I've ever encountered, and I'm convinced its software related, given that music and all other audio works.
Never had such issue with Nougat or Oreo.
Where did you read about such standard bug at Oreo?
Unleashed by my rooted OP3T on 8.0
RASTAVIPER said:
Never had such issue with Nougat or Oreo.
Where did you read about such standard bug at Oreo?
Unleashed by my rooted OP3T on 8.0
Click to expand...
Click to collapse
https://www.zdnet.com/article/andro...-looking-into-buggy-bluetooth-audio-problems/
https://forums.oneplus.com/threads/bluetooth-mic-not-working-on-phone-calls.805719/
https://www.reddit.com/r/oneplus/comments/7zz7fc/oneplus_55t_callers_cant_hear_me_solution/
https://forums.oneplus.com/threads/...all-whether-i-m-calling-or-vice-versa.731333/
smo69 said:
https://www.zdnet.com/article/andro...-looking-into-buggy-bluetooth-audio-problems/
https://forums.oneplus.com/threads/bluetooth-mic-not-working-on-phone-calls.805719/
https://www.reddit.com/r/oneplus/comments/7zz7fc/oneplus_55t_callers_cant_hear_me_solution/
https://forums.oneplus.com/threads/...all-whether-i-m-calling-or-vice-versa.731333/
Click to expand...
Click to collapse
Of those links, only the last one is relevant to the 3T.
What specific Bluetooth devices do you have the problem with?
I've use the phone feature with 3 different headsets, my car head unit, and a BT speaker, all with no issues with calls.
I have a problem with every Bluetooth device that uses phone features. This includes a Gear S3, Car Dongle and ear phones.
I have tried 2 BT SPEAKERS, 2 BT headset,.1 smart band and 1 smartwatch (moto 360).
No issues at all
Unleashed by my rooted OP3T on 8.0
I must have some kind of app causing the problem. I'm just not even sure which app it could possibly be.
smo69 said:
I must have some kind of app causing the problem. I'm just not even sure which app it could possibly be.
Click to expand...
Click to collapse
Any Magisk modules being used? I haven't seen this Bluetooth issue specifically (from Magisk modules) but they can sometimes cause random bugs, and it is a good enough place to start as any.
I think the Samsung gear watches in general, do not play well with a lot of non-Sammy phones. At least from other threads I've seen around. But it is suspicious that you are having the issue on multiple Bluetooth devices (although you don't name the other brands). So I think you are on the right track, that it may be an app or something else peculiar to your device setup.
I've had the phone functions work just fine with Motorola, Plantronics, JBL headsets, JBL speaker, Subaru head unit (Kenwood made stereo, from what I understand).
smo69 said:
I've heard this a bug with Oreo, but I've had this issue since Nougat. Essentially, I've tried connecting several Bluetooth devices to my OnePlus 3T with OOS 5.0.3 rooted w/ Magisk, and while I can get music and notifications to play, I can neither hear nor speak through the phone options using Bluetooth. I've searched for hours on Google as to why this may be happened, and while there are hundreds of reports and instances of this happening, there isn't a single consistent solution.
I've tried messing with the settings, codecs, deleting cache, deleting data from Bluetooth, repairing devices, deactivating Google Now, resetting the phone, you name it.
Is this a problem that is still prevalent with Oreo? This is probably the stupidest unsolvable thing I've ever encountered, and I'm convinced its software related, given that music and all other audio works.
Click to expand...
Click to collapse
I have the exact same issue. I've tried nougat/oreo.....official OOS....different roms also. Clean flashed the 3T but no luck.
Media audio works perfectly fine. As soon as somebody calls and I answer, the line becomes mute to whatever it is connected to. I've tried both with my car and BT speaker.
I then have to route the call to the ear pierce on the phone to be able to continue with the call.
Everyone I have found with this issue have sent their phones back for repairs.
OnePlus 3Ts seem to face an issue where if you're in a voice call using your SIM card, and also connected to some Bluetooth device at the same time, the WiFi seems to just s**t itself. It can't give more than 0.10 Mbps ever. It left me confused for a long time until I figured it was due to me calling on my Bluetooth headset/speaker. Truly annoying imo.
I finally figured it out. As I stated earlier, I was sure it was software based because music worked just fine, so I was looking for a culprit app that might have been hogging the phone audio/mic. Oddly enough, it was the T-Mobile Visual Voicemail app. I went ahead an uninstalled it. That app was not worth being unable to use Bluetooth hands-free in my car.
I take that back. Suddenly, it's not working anymore, so I'm more inclined to believe there's something wrong with the phone speaker/mic suddenly hanging with apps other than the actual phone app. The Visual Voicemail app only exposed that there was an issue with this, but the app itself did not seem to be the problem.
Same problem here, I am on Oreo (final beta). Have you managed to find a solution?
DIOmenik said:
Same problem here, I am on Oreo (final beta). Have you managed to find a solution?
Click to expand...
Click to collapse
Just saying.
When was the last time that you had a factory reset?
Sent from my ONEPLUS A3003 using Tapatalk
RASTAVIPER said:
Just saying.
When was the last time that you had a factory reset?
Sent from my ONEPLUS A3003 using Tapatalk
Click to expand...
Click to collapse
A few months ago, when moving back from Oreo to Nougat for battery problems.
If you can confirm that on the last (stable?) Oreo release you are not facing this issue, I would really appreciate it and proceed with a factory reset.
DIOmenik said:
A few months ago, when moving back from Oreo to Nougat for battery problems.
If you can confirm that on the last (stable?) Oreo release you are not facing this issue, I would really appreciate it and proceed with a factory reset.
Click to expand...
Click to collapse
I am not at any stable version.
And have tried many different bt sets.
Also never had battery problems at Oreo
Sent from my ONEPLUS A3003 using Tapatalk
DIOmenik said:
A few months ago, when moving back from Oreo to Nougat for battery problems.
If you can confirm that on the last (stable?) Oreo release you are not facing this issue, I would really appreciate it and proceed with a factory reset.
Click to expand...
Click to collapse
I'm on stable OOS 5.0.6 (and multiple/sequential stable OOS builds before that) and never had issues with BT calls, using a headset and my car stereo.
2020, OnePlus 3T rooted magisk, android Pie, same bluetooth problem.
Hello all,
I hope everyone is fine...
Is anyone facing issues with auto-connect after pairing...
After pairing my galaxy watch and my car, connection is fine...
But if I restarted the phone or the watch or even get in the car start it...
The phone keeps asking for pairing code confirmation but never connects...
I tried removing the the paired devices but that didn't work...
Every time I want to connect to the car or the watch or anything, I have to pair. it again...
It's annoying but acceptable for the watch and other devices since after hitting pair they're connected...
But the car... I have to remove the device and add it again whenever I want to connect...
My phone wasn't tested as stock,
I immediately rooted (which was a mistake, with root, I can't tell if the root is the problem or not),
I noticed that after 2 days from rooting as it was when I decided to pair my device...
I used Dr.ketan aroma installer to root with custom magisk since it wasn't supported for note 9 (now Magisk 17 and above supports it)...
So, I kindly ask if any non rooted users have Bluetooth issues or not as well rooted users...
As I plan on re-flashing latest stock and test it then root it and test one more time...
Highly appreciated for any help...
Sincerely,
Dante
same issue happen with me, Also I rooted my SM-N960F with Dr.ketan rom.
NOW I am rooted but with stock firmware everything is fine.
Found the problem, it was Xposed, there is an issue and they released a workaround... You can find it on Dr ketan thread or github... I'll post the github link later...