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'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.
Hi I just update my P20 Pro to EMUI 9.0.0.178 and my GPS stops working, everytime I use Google Map it says "searching for GPS" and leaves me a grey dot. It's becoming a headache since I heavily rely on it for driving. Does anyone have the same problem with their phone? I tried restarting it, toggling location, reloading the app, still the same problem.
please help.
i have same problem
Mines was jumping all over the place today. Is there a way to calibrate the compass?
I try to restart the phone everytime this problem shows up, and it seems to solve the problem. But it's annoying knowing I have to restart it everytime to make it work...
My wife and I have the same problem since the update. It looks like the GPS lag to update the position. Rebooting seems to solve the problem temporarily... But I don't want to have to reboot every other day.
Same problem here. Has anyone gotten a solution or has it started working again by itself?
Has anyone tried refreshing the a-gps data? Might help, I use gps test plus.
https://play.google.com/store/apps/details?id=com.chartcross.gpstest
Same issue here. Rebooting brings things back but that's not a solution. I'm on 9.0.0.178 with the CLT-L04 in Toronto.
going to check this soon.
No problem with GPS on my Pro.
9.0.0.163
OTG Update with full wipe
I have the same issue but only with google maps. Waze and other GPS functions work fine. I usually reboot and it works for a few hours.
Huawei acknowledged a problem
It's my first time posting here, as it's the first major problem I've had with my P20 Pro over the past year. I started experiencing GPS problems after the last software update. Like others reported, they'd go away after reboot but not for long. I tried a factory reset, which doesn't seem to have helped either.
I contacted Huawei support in Canada via their website. I got a response today which first suggested I try wiping the cache partition (restart my phone, hold down the volume-up button, then you get to an EMUI maintenance screen with this option - this also didn't help any more than restarting). But it also acknowledged that there is a known issue that they are working on fixing in the next update. I quote:
" In case the issue persists, we would like to inform you that this is related to the new software update, however, Huawei is currently working to solve it. This issue will be optimized in the new version, this one is expected to be released in March. You will automatically receive this update that will solve this issue your phone is facing."
I thought you all might like to know this. I'm keeping my fingers crossed!
I just updated to the 9.0.0.236 version available through FirmwareFinder and rooted as well. GPS is working normally again!
Greatings Bastian
There's an issue with the latest pie ( android 9.0) and the P20 Pro that bugs the gps out, you have to restart your phone every times you want to use your gps. There should be a patch around March 21st 2019. In the meantime if you want, you can always factory reset, which would solve the issue, and wait before reinstalling the latest firware
Any news about that issue ? I have the model CLT-L29 C636E2R1P12 with Android 9.0.0.234 and it's not working the gps....
I have the 213 update for my L04 and it now works great! If you have the Canadian model, check for the update! It didn't work with the 178, now it does!
Im also experiencing gps problem CLT-L29(C636) 9.0.0.234
i thought that i had the same issue but finally i found out that the problem was the new phone-case i put which has metal parts and blocks the gps signal. After remove the case gps works as it should.
Mine doing same. Always searching for gps. How did u fix it?
Same here. At first I thought it's EMUI, but the GPS was still broken after flashing lineage... Any chance that the gps will work again if I roll back to EMUI 8.1?
Hello All,
I am having a strange issue with bluetooth, all of my connected devices are not reconnecting if I came back to range or on/off bluetooth,
Its happening for my CAR Bluetooth and Gear Sport watch. every then and now and I have to do pairing. I am super frustrated with watch need to reset and reinstall everytime.
I also have swift install does it have anything to do with it.
prashant.saraf said:
Hello All,
I am having a strange issue with bluetooth, all of my connected devices are not reconnecting if I came back to range or on/off bluetooth,
Its happening for my CAR Bluetooth and Gear Sport watch. every then and now and I have to do pairing. I am super frustrated with watch need to reset and reinstall everytime.
I also have swift install does it have anything to do with it.
Click to expand...
Click to collapse
Did you force update? also which version are you on? CSB3 or CSAA?
I have CSAA and I don't think it's force update as it's through ATT.
prashant.saraf said:
I have CSAA and I don't think it's force update as it's through ATT.
Click to expand...
Click to collapse
I'm on VZ and I did the firmware.science forced update to CSAA and it would loose my bluetooth devices all the time for no reason. So I went back to 8.1 until VZ does there update. Some told me, that he had the same problem and had to factory reset his phone just to get that issue resolved.
Not sure if this helps. I had a somewhat similar issue and read somewhere that doing a "reset network settings" fixes the issue. I tried it and it seemed to clear up the reconnecting problems I was having.
Let me try network reset. I will post update
prashant.saraf said:
Let me try network reset. I will post update
Click to expand...
Click to collapse
I've already seen multiple folks state that the CSB3 update has solved lots of Bluetooth issues as well as the compass problem, for what it's worth! There's a CSAA to CSB3 update file out there...