[Q] Bluetooth not working after update to D85120e - T-Mobile LG G3

I'm hoping someone can help me here. I have an T-Mo LG G3 (D851) that had been running the D85120b software from April 7, 2015. We all know that WiFi Calling was not working on that version of software, which is why T-Mo pulled it and quit distributing it after only a couple of weeks. But Bluetooth worked perfectly for me. Then on June 9, the new D85120e came out to fix the wifi calling. So I updated to the new 20e yesterday without any problems. But now, bluetooth won't work through the phone no matter what I do. Even with LG wireless headphones or in my car. I have removed all devices, re-paired all devices, everything possible. Can't place or receive calls on my headset now, nor can I place or receive calls through my car now, even though both devices say paired and connected (1 at a time of course). This just started yesterday when I upgraded to D85120e. Any ideas out there? Please help and thank you very much.

I had to delete and pair my bluetooth devices again after I upgraded to 20e. That fixed it for me.

jobella said:
I had to delete and pair my bluetooth devices again after I upgraded to 20e. That fixed it for me.
Click to expand...
Click to collapse
Thanks for the reply, but as I said in the original post, I have already done that numerous times. I have also done complete "factory" resets of both bluetooth devices (headphones and car system) and I still get the same result. I wish it had been that easy. Thanks for answering though.

Issue resolved. Just an update to close this thread. Fortunately for me, after I had upgraded to D85120e, I had done a complete TWRP backup. After that I flashed 2 TWRP zips that i wanted to use. I flashed the zip to delete Carrier IQ and the zip file by @spiderio to raise the volume level of the speakers. It was one of these zips that killed the bluetooth. ( I am guessing it was the Volume increase since that one dealt with sound issues)
In any case, I restored the TWRP backup to the system before those 2 flashes and bluetooth came back fine. I hope this may help someone else sometime. Just FYI.

Related

After AT&T JB update, Bluetooth connection keeps dropping (paired with car)

Since I upgraded my AT&T Galaxy S3 with the official Jelly Bean update last week, my bluetooth pairing with my car has not worked.
At first, I was continuing to use the existing pairing which was set up and perfectly working in ICS. Whenever I made a call from my car ('09 BMW 3-series, bluetooth phone via built in nav system), there would be a loud pitch sound when the call was answered and then connection lost.
So I unpaired, and re-paired.
But now it does not work at all. Connection keeps dropping every few seconds. I have not even managed to get the data sync (transferring of contact data from phone to car) to complete.
This is beyond me. Jelly Bean is great, but it is not worth the price of not having properly functioning bluetooth.
Any suggestions? Anyone with similar issue? Is it possible to somehow roll back to ICS?
I know this is a typical response for any issues after an upgrade, but have you tried a factory reset?
Also can you delete your phone from your cars memory(I know mine remembers all phones that have connected to it) might help.
nsmith4 said:
I know this is a typical response for any issues after an upgrade, but have you tried a factory reset?
Also can you delete your phone from your cars memory(I know mine remembers all phones that have connected to it) might help.
Click to expand...
Click to collapse
Thanks for your response.
I have not (yet) tried a factory reset, was sort of hoping to avoid the hassle of having to restore my data and apps. But I will eventually resort to it, if nothing else can fix it.
Good suggestion with regards to erasing from car memory. I am not sure if or how that can be done, but I will try and look through the settings to see if I can. (what I have done so far is just "remove" the device from the list of paired devices...
nsmith4 said:
Also can you delete your phone from your cars memory(I know mine remembers all phones that have connected to it) might help.
Click to expand...
Click to collapse
Pretty sure this is the actual cause of your problem.
HiKsFiles said:
Pretty sure this is the actual cause of your problem.
Click to expand...
Click to collapse
I went through all possible options in my car's nav system (xDrive) and I do not see any options to delete the car's memory.
So the only option as far as I know is to remove the device from the list of paired devices before pairing it again. And I tried that already...
Look through All Applications in Application Manager for BT share. Wipe data for that. Be warned this should wipe all your bt pairings.
Ok. So I resorted to restoring to factory settings.
With it clean, before restoring backup (made with Titanium), I went to my car and paired.
It worked - it synced the (very few, AT&T default) contacts, and no dropping (as far as I waited, a few minutes).
This was good news.
So I went back up and restored all app data, signed into Google account to sync all contacts etc.
Then back down in car and connected.
Problem is back It won't sync the contacts and continously drops and reconnects.
Well at least I have a reference point to go back to now and perhaps take one step at the time.
I was thinking next step is to restore to factory settings again, then ~only~ add google account to sync up contacts, then try. If that works, restore one app at a time to see if I can isolate the issue.
I will do this tomorrow.
mrhaley30705 said:
Look through All Applications in Application Manager for BT share. Wipe data for that. Be warned this should wipe all your bt pairings.
Click to expand...
Click to collapse
I just did this. I am however too tired for the day and will check first thing in the morning, if this resolved it (as I am back in the problem state) - before resetting and starting all over (ref. my above mentioned thoughts of how to do a gradual restore)...
Thanks all for your input so far - I cannot tell you how much I appreciate it. This forum rocks so far.
/Lars
Progress this morning:
First of all, I tried as suggested clearing data for Bluetooth Share. Didn't fix the problem.
I know now that if I pair the phone and connect after factory reset, with the contacts list on the phone at default/almost empty (11 pre-defined AT&T numbers), it works.
So what I did this morning:
I factory reset the phone again. Then I added my Google account to sync up contacts list from my GMail account.
I ~only~ did this. No apps installed or restored.
Paired and connected. And I have the problem.
So this seem to somehow be caused by my contacts list after it has synced up with Google.
Any suggestions?
I am thinking that if I cannot get this resolved, I want to roll back to ICS. Having no functional bluetooth pairing with my car is not an acceptable tradeoff, no matter how great JB is. Is there a way to roll back? Can I get the official ICS ROM from AT&T, if needed?
But of course - this will be my final solution; I much prefer to get this resolved. I am open to any suggestions re. my contacts/google account.
You have an old problem. There are stock roms and instructions to do it stickied on the original development forum. I suggest you download the jb version of your carrier and flash that through Odin first.
If that doesn't work, then go back to ics
Sent from my SGH-I747M using xda app-developers app
Deoxlar said:
You have an old problem. There are stock roms and instructions to do it stickied on the original development forum. I suggest you download the jb version of your carrier and flash that through Odin first.
If that doesn't work, then go back to ics
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Thanks for your feedback.
Can I ask, if you know where this problem is perhaps discussed?
I looked in the developer forum, but must admit I am confused which thread/which ROM you are referring to. Are you talking about a modified stock ROM? I would greatly appreciate a link if it is...
Today's update:
At work we have a Galaxy S3 AT&T device (identical to my own) for testing purposes.
I just upgraded it to Jelly Bean today and then added my gmail account to it, paired to my car - and the same problem.
So at least that rules out an issue with my specific hardware/phone.
I also tried using a Galaxy Nexus (Verizon version) from work. Issue did NOT happen.
I then flashed my own phone with the stock Jelly Bean ROM downloaded from here:
http://forum.xda-developers.com/showthread.php?t=1739426
Same issue happens
So my final solution (at least for now):
I flashed to the stock Ice Cream Sandwich ROM (downloaded from same place as listed above).
It works now.
Funny how one can be so happy with a downgrade, but I am
Thanks all for all your input.
I am still open to any suggestions (as I would love to be on Jelly Bean in the future), and I have an easy way to test possible solutions on my work test device...
Thanks again!
Lars
Hey, I am having Bluetooth problems as well. I have the sprint s3 stock jb. My blue tooth will not connect to my moga controller. Everything I have been reading points at it being a software issue on Samsung JB devices. Can anybody else confirm this?
Sent from my SPH-L710 using xda premium
Aren't the bluetooth "drivers" in the kernal? Perhaps using a different, or going back to a stock kernal.
I was having a similar issue with my phone not automatically connecting with my car. It would connect if I cycled BT off then on. All this on Tasks 4.1 rom & KT's kernal.
Flashed with the new 4.2 rom & kernal and it seems to be fixed.
Just curious, did the OP ever try a factory reset? I'm on Blackjelly, which is a ROM heavily based on AT&T stock JB and I have no issues with my Bluetooth whatsoever. However, I do have the KT747 kernel installed, which has its own set of bluetooth drivers.
crazililazn said:
Just curious, did the OP ever try a factory reset? I'm on Blackjelly, which is a ROM heavily based on AT&T stock JB and I have no issues with my Bluetooth whatsoever. However, I do have the KT747 kernel installed, which has its own set of bluetooth drivers.
Click to expand...
Click to collapse
I have a Verizon S3 (running stock) and the same problem is happening. I've even tried a factory reset but that doesn't seem to have helped although I'm still testing it (need to go drive for a while). My car is a 2010 Audi A4. I've spoken to both Samsung and Audi and both tell me it's not their problem. I'm hoping Samsung updates the phone with a backwards compatible BT driver or Audi upgrades their driver. I am not happy.
EDIT: I drove some more today and bluetooth only dropped once. The strange thing is that while I am driving I only see 2 bars on my dashboard screen when the phone shows 5 bars. I would "assume" that the phone is the most accurate signal meter. In any case, everything "seems" to be working better although not as well as before.
Bluetooth in car only has voice audio, no ability to control the phone
Ansextra said:
I have a Verizon S3 (running stock) and the same problem is happening. I've even tried a factory reset but that doesn't seem to have helped although I'm still testing it (need to go drive for a while). My car is a 2010 Audi A4. I've spoken to both Samsung and Audi and both tell me it's not their problem. I'm hoping Samsung updates the phone with a backwards compatible BT driver or Audi upgrades their driver. I am not happy.
EDIT: I drove some more today and bluetooth only dropped once. The strange thing is that while I am driving I only see 2 bars on my dashboard screen when the phone shows 5 bars. I would "assume" that the phone is the most accurate signal meter. In any case, everything "seems" to be working better although not as well as before.
Click to expand...
Click to collapse
Hi guys,
I have the same problem.
Details:
Phone: GALAXY S3 I747M
Carrier: Rogers
What happened?
Let me start by saying Bluetooth was flawless before moving to Jellybean (flawless means it would work consistently EVERY time on all featureS). Data and Voice between my Car (2010 Audi A4). I consider data the phonebook information back and fourth to the car, the ability for the car to control my device (make calls, end calls, switch calls) and the number of bars for reception.
I upgraded to Jellybean, then stuff wouldn't work (Bluetooth, GPS, 3G, wifi, etc.), so I tried a few roms (I would factory reset, wipe cache, wipe delvik cache, format /system EACH time I swapped ROM's). Unable to get anything to work consistently with everything. I downgraded to 4.0.4 (Using the WanamLite ICS SGH-I747 V1.3 Android 4.0.4 ROM).
Everything started working again! EXCEPT Bluetooth. It connects with no problems, but it seems like it's only the voice part, the data part (as decribed above) doesn't...I can tell by not seeing any information go back and fourth between call logs and the wrong number of bars for reception, it's like the connection is jumbled.
Unfortunately, it's inconsistent to around 50% of the time, sometimes it DOES work.
Voice/audio through phone calls work ALL the time. IF someone calls, the car recognizes it and the audio mic and through speakers work...but the car doesn't realize it's happening enough to give me options (like ending the call from the car).
This only happened once I went from Jellybean and then went back....not sure what's happened...
Appreciate your help and thanks in advance!
rohanverma said:
Hi guys,
I have the same problem.
Details:
Phone: GALAXY S3 I747M
Carrier: Rogers
What happened?
Let me start by saying Bluetooth was flawless before moving to Jellybean (flawless means it would work consistently EVERY time on all featureS). Data and Voice between my Car (2010 Audi A4). I consider data the phonebook information back and fourth to the car, the ability for the car to control my device (make calls, end calls, switch calls) and the number of bars for reception.
I upgraded to Jellybean, then stuff wouldn't work (Bluetooth, GPS, 3G, wifi, etc.), so I tried a few roms (I would factory reset, wipe cache, wipe delvik cache, format /system EACH time I swapped ROM's). Unable to get anything to work consistently with everything. I downgraded to 4.0.4 (Using the WanamLite ICS SGH-I747 V1.3 Android 4.0.4 ROM).
Everything started working again! EXCEPT Bluetooth. It connects with no problems, but it seems like it's only the voice part, the data part (as decribed above) doesn't...I can tell by not seeing any information go back and fourth between call logs and the wrong number of bars for reception, it's like the connection is jumbled.
Unfortunately, it's inconsistent to around 50% of the time, sometimes it DOES work.
Voice/audio through phone calls work ALL the time. IF someone calls, the car recognizes it and the audio mic and through speakers work...but the car doesn't realize it's happening enough to give me options (like ending the call from the car).
This only happened once I went from Jellybean and then went back....not sure what's happened...
Appreciate your help and thanks in advance!
Click to expand...
Click to collapse
It's a know JB problem. No solution right now
Ironically, I had the same exact bluetooth problem the OP describes, but it happened with my stock ICS ROM. Made trying to call someone extremely frustrating since I have a stickshift!
The problem disappeared with my upgrade to the 4.1.1 stock ROM. I have also had no issues at all with any 4.1.2 JB custom ROM.
I believe it is a generalized issue with Android, because the problem I had with ICS was not reproducible when using a different bluetooth headset. Only my own would cause the problem. As soon as I realized that the problem no longer existed in 4.1, I began using my own headset again, and have done so without a single dropped call.
BWolf56 said:
It's a know JB problem. No solution right now
Click to expand...
Click to collapse
Thanks, but just for clarification. It was working on JB perfectly. I upgraded to ICS, thats when bluetooth with my car stopped working (with a number of other things). So i downgraded BACK to JB (stock rom) and I still have the same problem.
It's almost like the data side of the connection is all jumbled up....did ICS leave something on my phone (I did a factory reset, wipe cache, wipe delvik cache, format /system when switching back).
So I feel like it wasn't a JB problem it was an ICS problem, but reverting back to JB didn't fix the problem, so I feel like ICS left something on there that the old rom didn't overwrite. Any files I should be checking to ensure that isn't the case?
Thanks a lot!
rohanverma said:
Thanks, but just for clarification. It was working on JB perfectly. I upgraded to ICS, thats when bluetooth with my car stopped working (with a number of other things). So i downgraded BACK to JB (stock rom) and I still have the same problem.
It's almost like the data side of the connection is all jumbled up....did ICS leave something on my phone (I did a factory reset, wipe cache, wipe delvik cache, format /system when switching back).
So I feel like it wasn't a JB problem it was an ICS problem, but reverting back to JB didn't fix the problem, so I feel like ICS left something on there that the old rom didn't overwrite. Any files I should be checking to ensure that isn't the case?
Thanks a lot!
Click to expand...
Click to collapse
Umm just to clarify, firmware goes like this (in order): Eclair, Froyo, GB, ICS, JB. So JB is the latest.
Here's a JB fix for BT: https://dl.dropbox.com/u/28275651/REVERT-MY-ALSA.zip
Flash it in recovery, clear cache and dalvik and hopefully it will work.

No Call Audio

Hello, im on cm 12.1 and recently i have no call audio, calling works fine on facebook and the like, but not when im calling someone from my contacts , ive tried factory reset, flashing different rom , back to stock and nothing works ,can someone help me???
dpwguenther said:
Hello, im on cm 12.1 and recently i have no call audio, calling works fine on facebook and the like, but not when im calling someone from my contacts , ive tried factory reset, flashing different rom , back to stock and nothing works ,can someone help me???
Click to expand...
Click to collapse
Need more info....download samsung phone info and post a screenshot of the firmware tab. If your bootlader and baseband dont match, theres your problem. If they do, try reflashing stock (twice) then doing a tactory reset from the stock recovery right after. If after that the issue is still present....probably something else.....mabey hardware related. Good luckl
Do you use bluetooth? I had a very similar problem and figured out that the only time I had call audio was when I was using a bluetooth headset or the bluetooth in my car. I don't know what sets it off but I've done some searching on this problem and it appears to be common among GSM GS4 owners, and even doing stuff like a complete reset doesn't fix it.
The one fix that I did find, that helped some people, was to go into Google Now and disable "Okay Google" detection from any screen. Several people found that that worked. But I didn't have that feature enabled anyway so it didn't apply.
I don't know if the same problem occurs with CDMA GS4s; my wife has a Sprint GS4 and doesn't have the problem but that doesn't mean it doesn't exist. I think it was just AT&T and T-Mobile GS4 owners who reported this.
lordodin912 said:
Need more info....download samsung phone info and post a screenshot of the firmware tab. If your bootlader and baseband dont match, theres your problem. If they do, try reflashing stock (twice) then doing a tactory reset from the stock recovery right after. If after that the issue is still present....probably something else.....mabey hardware related. Good luckl
Click to expand...
Click to collapse
My bootloader is nb4 and baseband is foh3, but it's been that way for a while now, and this problem is only recently, also I've tried that and it didn't work
Sent from my SGH-M919 using XDA Free mobile app
Mama Luigi said:
Do you use bluetooth? I had a very similar problem and figured out that the only time I had call audio was when I was using a bluetooth headset or the bluetooth in my car. I don't know what sets it off but I've done some searching on this problem and it appears to be common among GSM GS4 owners, and even doing stuff like a complete reset doesn't fix it.
The one fix that I did find, that helped some people, was to go into Google Now and disable "Okay Google" detection from any screen. Several people found that that worked. But I didn't have that feature enabled anyway so it didn't apply.
I don't know if the same problem occurs with CDMA GS4s; my wife has a Sprint GS4 and doesn't have the problem but that doesn't mean it doesn't exist. I think it was just AT&T and T-Mobile GS4 owners who reported this.
Click to expand...
Click to collapse
I don't have Bluetooth, I've tried it with a wired headset and even that didn't work, but what's so puzzling about this is that my calling works fine with Facebook messenger calling feature, hangouts and things like that
Sent from my SGH-M919 using XDA Free mobile app
Edit:
Nevermind. It worked twice then I tried calling a different phone and it broke again. I will keep searching and update.
Original:
I have had this issue intermittently for the past year. It was fixed for about 6 months then two weeks ago started occurring again. Today I flashed a new Rom (PacMan) and the M919UVUFOK3_M919TMBFOK3_TMB firmware. That did not fix it. I was connecting to a 5Ghz WiFi so on a whim I forgot that network and made a call without WiFi enabled. Call worked!
So I connected to my 2.4Ghz WiFi and it is working again. I would try turning off WiFi and see if your calls go through if so it could be 5Ghz or the router...maybe a forget network / reconnect to network will fix it consistently.
Hope this helps you and if anything new comes up I will let you know.
So an update. I finally just gave up on it. My wife had an old phone I remembered (from 2 - 3 years ago) that was ran over and the digitizer broke. I just took her guts and put it in my phone and now it magically works. Hopefully it stays that way.
Should have done this years ago as my phone would no longer charge with the USB Cable nor was my SD Card accessible. Now it is all functioning right again.
dpwguenther said:
My bootloader is nb4 and baseband is foh3, but it's been that way for a while now, and this problem is only recently, also I've tried that and it didn't work
Sent from my SGH-M919 using XDA Free mobile app
Click to expand...
Click to collapse
So after flashing stock NB4 twice.....and factory resetting after from stock recovery, your still not getting call audio?.....doesnt make sense....try again and make sure the bootloader and baseband match.....and dont reboot into download from the OS.
For anyone having issues with no call audio through cell service but for some reason it works through data calls through whats app or facebook messenger, etc ,i have been having the same problem for awhile now. I believe i have traced it to be a hardware issue with the middle frame, when looking at the phone with the battery cover open on the top right over by where there are two markings R1 and L1. There is a module there labeled J-AT TMGA 7-3. When i was having issues i noticed that if i put slight pressure on that module my audio would fade back in on the call but if i put too much pressure it goes away again. If it is a hardware connectivity issue it would explain why slunked was able to get his phone working again by changing the guts in the unit. Im currently waiting for a middle frame and a blue cable for the antenna to confirm if this is indeed the issue.

Bluetooth issues after upgrading to OTA 6.0.1 on 6/22

My Bluetooth used to work when it was on 5.x and when I updated to 6.0.1 yesterday, my car's Bluetooth is disconnecting every couple of minutes and connecting itself back, same thing happening with my Gear S2. It stays connected for a minute then disconnects and connects back.
Anyone else facing this issue?
I'm on MM (the sideloaded version) and have never had bluetooth issues with any connection. In past updates, as much as this may suck, so many issues like this one can be fixed with a factory reset.
jack man said:
I'm on MM (the sideloaded version) and have never had bluetooth issues with any connection. In past updates, as much as this may suck, so many issues like this one can be fixed with a factory reset.
Click to expand...
Click to collapse
will try that.. thank you!

T-Moble HTC 10 updated to 1.81.531.4 and now Bluetooth not working well

Hi all.
Anyone else get upgraded to 1.81.531.4 and have inconsistent Bluetooth behavior? Specifically, I cannot connect to some speakers that previously worked flawlessly. Oddly, I can still connect to my car.
My wife's HTC 10 which is still on 1.81.531.1 is still working fine with the speakers in question.
ERamseth said:
Hi all.
Anyone else get upgraded to 1.81.531.4 and have inconsistent Bluetooth behavior? Specifically, I cannot connect to some speakers that previously worked flawlessly. Oddly, I can still connect to my car.
My wife's HTC 10 which is still on 1.81.531.1 is still working fine with the speakers in question.
Click to expand...
Click to collapse
Yes! Me too! I can no longer connect to my bluetooth headphones. Not one problem before the update. None. And yes, I can still connect to my car. It is odd and frustrating. Glad at least I'm not alone. I've sought help on-line but found no solution as of yet...:crying:
I got 2 10s and both on T-Mobile I updated 1 then flashed back to leedroid rom I can't make any noticeable differences in the update. And didn't bother to update other one as its running great anyway. Wait for a bigger update or revert back to. .1 thru ruu. If you're having problems. It works with the custom roms perfectly fine and custom kernels can't forget that.
RUU will reset all settings and stuff right? Not worth the hassle for me honestly.

OnePlus 3 Problems with Car Bluetooth connection

Hi all,
Since the last few firmware versions (OS 4.02 and above) I´ve been experiencing some issues exclusively with the Bluetooth connection of my car (Jaguar XE). I couldn’t fixed the problem even with the last firmware version rolled out via OTA (4.1.0).
In the last two months the connection of my Jaguar has not been stable at all. Most of the times I am able to pair my phone with the car, upload my contacts and so. However, once I start to transfer music of Spotify via Bluetooth, it keeps failing the "multimedia audio" and the connection is interrupted the whole time. I also lose the connection with the “phone audio”. I seems that my phone disables both connections intermittently. My guess is that Android Nougat is a "control freak" of permissions and this leads to issues with some car stero units.
In the previous versions of the firmware (4.01 and below) I didn´t experienced such problem. In the past I did have perfect connection to play spotify in my car with my same Oneplus Unit. I am very confident that there is nothing wrong with my car stereo unit since the Bluetooth still working fine with my wife´s phone. I haven´t upgraded my Jaguar´s firmware lately…so that shouldn´t be the source of my problem.
Despite of all this, the Bluetooth of my Oneplus unit works perfectly fine with any other Bluetooth devices . In fact I am able to enjoy full connection playing music with my External Speaker (UE BOOM 2) and my Xiaomi roidmi 2s –used in my other car that lacks of Bluetooth technology -.
I´ve tried everything. A couple of days ago I even performed a factory reset using the last version of firmware (4.1.0). Of Course I reset system settings, wiped cache and all data (music, pics…etc)…but still experiencing the same issue. I am desperate.
Any instruction will be very much appreciated.
Thank you in advance.
Kind regards,
So there was another thread on these boards, cant find it for right now... but in my experience the problems were only present on OOS rom's.
Perhaps not the best solution, but have you tried a CAF or Lineage OS based rom? All my problems went away after I made the switch
Good luck
Gomezie said:
So there was another thread on these boards, cant find it for right now... but in my experience the problems were only present on OOS rom's.
Perhaps not the best solution, but have you tried a CAF or Lineage OS based rom? All my problems went away after I made the switch
Good luck
Click to expand...
Click to collapse
Thank you Gomezie, I´ve read all the threads but I dont seem to find the solution.
I stick to stock os. Never changed my stock rom.
The funny thing is that OP stated in its last changelog that they have fixed bluetooth problems....
Kind regards,
Hi, my one plus 3 has the same problem. Done all the required resets and clearing of cache and it still would randomly connect and disconnect. Problem only surface after the recent 4.1.0 update.
My kids phone and wife's phone all have no issues.
My op3 connects with all other Bluetooth devices without any problems.
Mine is a f-pace .
Same problem in Mazda 6
Hi, I've been experiencing similar problem in Mazda 6 after software update. Everything was working perfect in previous versions. I my case problem is with using Spotify. Phone connects to the headunit, just after engine starts with no isuess, but the music won't start to play. Only way to start playback is to disconnect the phone manually and reconnect every single time. Re-pairing the phone with car doesn't help.
I sent an email to customer service a couple days ago. i haven't got any reply yet. I will let you know.
Regards.
Brugalete said:
I sent an email to customer service a couple days ago. i haven't got any reply yet. I will let you know.
Regards.
Click to expand...
Click to collapse
I finally did receive a reply from OP customer service: The only solution they offer me is trying a downgrade to OS Oxygen version 3.2.8. This is the link suggested by the technical agent to do so:
http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_3.2.8/
I haven´t done it yet since I am not eager to this idea.
On the other hand, in the meantime, OP rolled out new OTA 4.1.1. I made the upgrade to the latest firmware version. It seemed to work at first. However right now I am having the same problems with bluetooth disconnecting the whole time.
Any other experiences?? Have anyone solved this issue with new OTA???
Kind regards,
Bluetooth and 4.1.1
It's worse now on 4.1.1. definitely not the car, Samsung works ok
Hi,
I've experienced the same problems starting on OpenBeta 12 and continuing through to OOS 4.1.1. I've posted in the Open Beta 12 thread on the Oneplus forums, and have been contaced by Oneplus regarding the issue. For the Open Beta I have provided log files for them, but due to work and private life getting in the way have not been able to do the same for OOS 4.1.0 or OOS 4.1.1. Also, I did not clean flash, but dirty flash - because I'm really lazy and stuff. It needs too much time, to be honest
Maybe if everyone who has the problem here contacts the guys at OP or the OP forums, respectively, providing logs etc. the problem can be solved faster.
I did some googling around and found a few articles that hinted in the direction of Android 7.1.1 being the culprit, which would mean that Google needs to fix it. In these articles, it said Nexus devices, and a fix coming up...don't know...
Best regards,
Chris
My phone audio always works fine but the media audio on both my nissan and ford sync system works randomly or not at all on both stock and Lineage based roms. My wife's iPhone 6s works perfectly every time on both cars. Fortunately for me it's not a big deal since both cars have usb inputs and I keep all my music on thumb drives...My old Galaxy S6 Edge works fine on both cars too so I am not sure why the OP3 is so spotty.
---------- Post added at 09:24 AM ---------- Previous post was at 09:23 AM ----------
kennonk said:
My phone audio always works fine but the media audio on both my nissan and ford sync system works randomly or not at all on both stock and Lineage based roms. My wife's iPhone 6s works perfectly every time on both cars. Fortunately for me it's not a big deal since both cars have usb inputs and I keep all my music on thumb drives...My old Galaxy S6 Edge works fine on both cars too so I am not sure why the OP3 is so spotty.
Click to expand...
Click to collapse
I should also mention I ordered my OP3 on release day and this has been true since the beginning.
OP3 not working error unable to mount storage data
I have tried rooting my OP3 but I landed up getting my phone into a mess. I think my OS is not working properly and my phone is getting stuck at one place while rebooting and when trying to use recovery mode it is getting stuck at twrp page. I am unable to connect my phone to my pc. Can u please help me getting it resolved
FahadMemon said:
I have tried rooting my OP3 but I landed up getting my phone into a mess. I think my OS is not working properly and my phone is getting stuck at one place while rebooting and when trying to use recovery mode it is getting stuck at twrp page. I am unable to connect my phone to my pc. Can u please help me getting it resolved
Click to expand...
Click to collapse
Ask your question in the proper place. This is a thread regarding bluetooth connectivity.

Categories

Resources