Related
I've been having bluetooth problems with this phone since day 1 & I'm wondering if it's just my phone or if anyone else is having the same experience. No matter what rom or headset I use, I get a craptastic connection. I don't have any problems pairing devices, but I can't get 10 feet away from the phone without it disconnecting and I can't even turn my head without the audio cutting out. It also randomly disconnects for no reason & sometimes won't reconnect until I reboot. This has happened with every rom I've tried & every headset too. I've bought & returned multiple headsets thinking it was just my Blueant, but it happens with every one.
Could I have a faulty unit or does the bluetooth on this phone really suck this bad? I listen to podcasts & music all day long at work so I need to have a decent connection. Opinions needed please.
I think it may be a bad phone.
I have and used the following bluetooth devices:
Plantronics 590A
Jawbone Icon and Era
BlueAnt S4 which I use in the car. And auto connects before I sit down to drive when I have it on.
Sony Ericsson MW600
And Jabra Pro 9470 (office phone setup that connects to my phone via bt)
All connects without a problem. Have you done a titanium backup and perform a factory reset? And after the reset use titanium backup to restore app and data only and leave the system settings alone. You can restore the wifi stuff if you like. From there that's like a fresh install. Hope that works for you.
Yeah I've done many, many wipes & fresh installs & nothing helps. I don't have any problems connecting, I just have problems STAYING connected & listening to audio. It cuts out constantly without me even touching the phone. I've never had such shoddy bluetooth on any other device.
*sigh* Looks like I may be doing an exchange...
kabuk1 said:
Yeah I've done many, many wipes & fresh installs & nothing helps. I don't have any problems connecting, I just have problems STAYING connected & listening to audio. It cuts out constantly without me even touching the phone. I've never had such shoddy bluetooth on any other device.
*sigh* Looks like I may be doing an exchange...
Click to expand...
Click to collapse
Well before leaving the store...if you are going to a brick and mortar to do the exchange, bring the bt headset with you and try it out there and try to replicate the problem with a new phone.
I do not have range problems but I don't usually have my phone more than 5 ft way from me when talking on it via bt.
I have a replacement on the way for bluetooth problems,people complained of a horrid background noise and the range was maybe 8 feet before major static would kick in
Macklessdaddy said:
I have a replacement on the way for bluetooth problems,people complained of a horrid background noise and the range was maybe 8 feet before major static would kick in
Click to expand...
Click to collapse
My BT sounds like crap! People say it sounds like I'm in a wind tunnel or they can't hear me that well, when they speak to me it cuts in and out.
This is when I connect to my Parrot BT in my truck. I know its not the Parrot system because my HD2 works fine with it.
rosedog said:
My BT sounds like crap! People say it sounds like I'm in a wind tunnel or they can't hear me that well, when they speak to me it cuts in and out.
This is when I connect to my Parrot BT in my truck. I know its not the Parrot system because my HD2 works fine with it.
Click to expand...
Click to collapse
I have a Dual car stereo & now that I think about it, everyone says they can't hear me even though I installed the mic on the side column & it's no more than a foot from my face at any time. Aargh this is so annoying. Freaking $600 phone & my damn $25 RAZR from Big Lots has better bluetooth.
If I bring it to the store, would they exchange it for me? I ordered it directly from T-Mobile, I didn't get it in a store.
kabuk1 said:
I have a Dual car stereo & now that I think about it, everyone says they can't hear me even though I installed the mic on the side column & it's no more than a foot from my face at any time. Aargh this is so annoying. Freaking $600 phone & my damn $25 RAZR from Big Lots has better bluetooth.
If I bring it to the store, would they exchange it for me? I ordered it directly from T-Mobile, I didn't get it in a store.
Click to expand...
Click to collapse
No you will have to call T-Mobile and do a warranty exchange. I have no problems with BT on my phone at all.
http://androidforums.com/htc-sensation-4g/375199-white-noise-bluetooth-htc-sensation-4g.html
http://community.htc.com/na/htc-forums/android/f/133/p/12494/52795.aspx
http://forum.xda-developers.com/showthread.php?t=1184936
a few threads about bluetooth problems
So whats the deal? Has anyone been able to fix the BT problems with this phone yet?
Can we flash a different BT.apk file or something?
Somebody by now should have some answers I would think.
My parrot system in my truck suck ass with this phone. Always cutting in and out.
Streaming audio is fine its the talking to people I'm have problems with.
rosedog said:
So whats the deal? Has anyone been able to fix the BT problems with this phone yet?
Can we flash a different BT.apk file or something?
Somebody by now should have some answers I would think.
My parrot system in my truck suck ass with this phone. Always cutting in and out.
Streaming audio is fine its the talking to people I'm have problems with.
Click to expand...
Click to collapse
I use this with my blueant s4 without an issue and experience no cutting in and out. However, I have been running MIUI and now running sense-o-maniac 3.5 and I have no issues.
kpjimmy said:
I use this with my blueant s4 without an issue and experience no cutting in and out. However, I have been running MIUI and now running sense-o-maniac 3.5 and I have no issues.
Click to expand...
Click to collapse
You've been running what and what?
MIUI / Sense-o-maniac 3.5?
I'm running the latest ARHD w/sense 3.5
horrid bluetooth sound quality
it seems a lot of people have been having issues with the bluetooth sound quality. i have mine paired with a motorola HF850 car kit, which has bluetooth v1.1, or something like that. i wonder if the problem is with backward compatibility, as people seem not to have as many issues with newer devices. would flashing a different radio potentiall help this problem? is it possible to downgrade the bluetooth version with a custom ROM? any other thoughts on ways to address this issue?
Hello,
Pardon if this has been answered already, I simply did not find my exact question answered.
I am using my unmodified Nexus 5 (not even rooted), with the latest KitKat (v.4.4.2 build KOT49H) with quite a few wired and wireless headsets and people always complain they cannot hear me. Eventually I got my hands on an old Samsung Galaxy S2 and tried my best bluetooth headset with it: Imagine my surprise, I could hear myself quite clearly even when I was talking really really softly, barely above a whisper. My headset is excellent. My phone is not.
My questions revolve around what to do about it.
Nothing in KitKat allows me to adjust the bluetooth microphone gain, nor does it let me use an equalizer on my microphone. I can adjust the volume of the headset, but this does not do anything to the microphone gain.
So...
Question 1: am I the only person with this problem?
Question 2: what do you people do about it?
Question 3: are there any mods / custom ROMs out there that attempt to fix this problem? Google does not appear to be interested in doing so.
Thanks in advance!
*bump*
Any ideas? I have tried re-pairing my bluetooth headset - no go. I have tried flashing custom ROMs and kernels - no go again. It seems to be a problem with the phone, but I have no idea how to fix it. And Google searches always return other people having this problem. Noone with solutions, though.
Using a wired headset results in even worse results, if that were at all possible.
Has anyone tried to replace the bluetooth stack or driver with something that works?
Thanks!
*bump*
Yesterday I spent quite a few hours tinkering with my phone. I tried every last radio out there for the Nexus 5 and none had any effect on bluetooth microphone levels. Then I tried a few AOSP ROMs: CM11 and Omni. They turned out to be so closely related I might as well have just tried one. None had any effect on bluetooth microphone. Heck if CM11 doesn't do it, there really are no alternatives out there! I tried the FauxAudio tweak, even paid $2 to Faux, which successfully managed to do nothing: app didn't was written badly. Finally, I tried a bunch of volume boost tweaks. That worked, actually. That is, it boosted the wrong volume. Finally, in a moment of true and utter desperation, I opened an ADB shell and edited that mixer file by hand. I then discovered that microphone gain on bluetooth is not controlled there.
I tried all my wired headsets again: Etymotic HF3's microphone produces such an atrocious sound, if I am to rely on it I need to seriously consider becoming a mime. Then there were my Bose QC15 headphones with a remote cable for Android by some off-brand company: that was terrible, the cable is useless. Heck, not even mime lessons can help me there.
Eventually I chanced upon an old microphone cable for my QC15 headphones. Just microphone, no remote. Surprisingly, this one is loud and clear! That after being anything but loud or clear on my old cell phone. Interesting. Unfortunately, it's been out of production for a few years. My working theory is that Bose realized putting a decent microphone on expensive headphones gives people real value, makes them spend money, and that way lies madness. We can't have that, can we. So when that cable starts cutting, so does my use of this cell phone.
I am screwed.
In any case, I will stop bumping my own thread, you guys obviously don't know a solution or there would have been a lively conversation right now. And I am pretty sure there is a moderator or two frowning right now, possibly getting ready to throw an encyclopedia at me. My only hope is that Google is going to do something about that pesky Broadcom driver that doesn't work sometime before the mass exodus to the iPhone. And before my precious microphone cable stops working, or I will be leading the way for that exodus. It's a phone, damnit, if it doesn't work like one it's no good.
Hmmm.... it should be possible to wire a good lavalier mike on a cell phone cable... maybe I can get an op-amp from an old tape recorder to get decent amplification... When attaching a 9V battery on my headphone cable begins to look appealing, we really have a problem.
Yes, if nobody reply you is because no one can help u.
But for what it's worth, i had an Xperia Play for 2 years. Using an Motorola Bluetooth Headset H350 while driving and a MW600 Sony Ericsson Stereo Bluetooth Headset, both never had a problem.
Now from 2013 Christmas both headsets with my new N5: still never a problem and not noticing any low volume or mic. Sorry
same issue
Dany XP said:
Yes, if nobody reply you is because no one can help u.
But for what it's worth, i had an Xperia Play for 2 years. Using an Motorola Bluetooth Headset H350 while driving and a MW600 Sony Ericsson Stereo Bluetooth Headset, both never had a problem.
Now from 2013 Christmas both headsets with my new N5: still never a problem and not noticing any low volume or mic. Sorry
Click to expand...
Click to collapse
hi,
i am having the same issue with my Nexus 5 in combination with my Logitech H800 Wireless headset (people can`t hear me).
Anybody who did find a solution for this?
Thx
pitchdown said:
hi,
i am having the same issue with my Nexus 5 in combination with my Logitech H800 Wireless headset (people can`t hear me).
Anybody who did find a solution for this?
Thx
Click to expand...
Click to collapse
No solution. I tried everything, everything I could think of. I got FauxAudio to work eventually and that did nothing for Bluetooth performance (and it said it wouldn't, but I was desperate).
I returned a lot of high end bluetooth headsets over this issue. Eventually I came upon the Plantronics Voyager Legend. I would like to tell you this really expensive headset works fine, but no - microphone gain is still low, though this time around people can hear me okay. Not great, just okay. I am using that now. It's not perfect, it's far from perfect, but finally usable. Sort of. If I speak loudly.
For what it is worth, the ElementalX kernel improves Bluetooth stability on the N5 quite a bit. Microphone gain is still low, though. Another thing that sometimes helps a little is turning off the multimedia profile on the headset, though why THAT would make a difference is beyond me.
All we can do is wait, watch the Samsung Galaxy S5 get released and wonder if we should switch.
kangelov said:
No solution. I tried everything, everything I could think of. I got FauxAudio to work eventually and that did nothing for Bluetooth performance (and it said it wouldn't, but I was desperate).
I returned a lot of high end bluetooth headsets over this issue. Eventually I came upon the Plantronics Voyager Legend. I would like to tell you this really expensive headset works fine, but no - microphone gain is still low, though this time around people can hear me okay. Not great, just okay. I am using that now. It's not perfect, it's far from perfect, but finally usable. Sort of. If I speak loudly.
For what it is worth, the ElementalX kernel improves Bluetooth stability on the N5 quite a bit. Microphone gain is still low, though. Another thing that sometimes helps a little is turning off the multimedia profile on the headset, though why THAT would make a difference is beyond me.
All we can do is wait, watch the Samsung Galaxy S5 get released and wonder if we should switch.
Click to expand...
Click to collapse
Somebody advised me to download the app "persist"
This is free from the playstore.
Can you try this and let me know this is working for you?
Thx
pitchdown said:
Somebody advised me to download the app "persist"
This is free from the playstore.
Can you try this and let me know this is working for you?
Thx
Click to expand...
Click to collapse
This app controls the bluetooth volume, not the bluetooth gain. The bluetooth volume was never a problem.
kangelov said:
This app controls the bluetooth volume, not the bluetooth gain. The bluetooth volume was never a problem.
Click to expand...
Click to collapse
Ok,
i am having the problem with my Logitech H800 headset with the nexus 5.
So this is a android kitkiat 4.4 issue?
Or is this problem only on several Nexus 5-devices?
pitchdown said:
Ok,
i am having the problem with my Logitech H800 headset with the nexus 5.
So this is a android kitkiat 4.4 issue?
Or is this problem only on several Nexus 5-devices?
Click to expand...
Click to collapse
My guess is either the bluetooth baseband or the bluetooth kernel driver used in the N5 is flaky. This is why I think so:
Problem does not exist on my old Samsung Galaxy S2, including when it runs the same nightly of CM11, nor does it exist on my computer or my desk phone. All the headsets I've owned performed admirably there, so the headsets are not directly the cause. From what I've seen no ROM and no kernel out there seem to be making a difference as far as Bluetooth gain is concerned, the problem is persistently there and the same. Best I could tell it's just the N5 with a problem and it's just for the phone profile. I've tried the Bose headset (the worst performer headset with the N5 of the lot) on a colleague's N5 and his phone was just as bad with it as mine. I am not sure if it's a small batch of N5s having a problem, I don't own lots and lots of N5 phones to try on, but I doubt it: with anything digital things are usually all-or-nothing and the N5 has an off-the-shelf Bluetooth chip, which is not unique to the N5. My guess is it's the entire model, but having only tried on 2 N5 phones, this is no more than a guess.
From what I saw online, the entire Nexus line has poor Bluetooth performance, not just the 5, and Google changed the Bluetooth stack with KitKat besides possibly introducing more problems. If you have a non-Nexus phone, the manufacturer most certainly replaced the Bluetooth driver and radio with one of their own, so problem goes away, but the Nexus line does not enjoy such attention.
An interesting thing to try would be for someone to put the LG G2 Bluetooth driver on a N5 kernel and try it out. I don't have the time or the expertise to do that, but there are plenty of people who do. Assuming the G2 does not have problems with bluetooth gain, if the problem still persists it will tell us if it's the N5 baseband or hardware doing it, and noone can help us there if that's the case.
I have this problem too, using my Nexus5 with iphone headsets. Peoples told me in skype and hangouts, that they hear me bad...
Shiver2005 said:
I have this problem too, using my Nexus5 with iphone headsets. Peoples told me in skype and hangouts, that they hear me bad...
Click to expand...
Click to collapse
That's a different problem. The wired headset problem is easily solvable with FauxAudio and a supported kernel.
This maybe realted to the changes Google made to the core Bluetooth stack as of Android 4.3+ I know they made adjustments for the BLE [low poer Bluetooth devices like pedometers and other senor type crap]. It is BEYOND me as to why Google keeps adding functionality ot the core Bluetooth stack when it is GLARINGLY OBVIOUS they have real problems with Bluetooth as a whole. WHY NOT fix the core issues so Bluetooth is much better at the basics before trying to add functionality or more complex?
I know they complained it would cost a bit for a different newer Bluetooth license but I mean in my personal experience with many different phones Bluetooth is SUPER flaky even at it's best in Android, and does not even work the same way across devices [I have used 3 different Jabra speakerphones on my bosses Galaxy 3 recently and they all worked to varying degrees even though they all use the same version of Bluetooth protocol], but my T989 [Galaxy 2 T-mobile], my parents G2s My bosses older Bionic, My fathers new Droid X, etc. all have random problems. You can usually find one device that works well with a certain phone/ROM, but that can change between ROM versions and devices so it is like you need to go and buy 1 of everything every time there is an update and go crazy finding the ONE that works [and as noted on page 1 with the gentleman using the same Platronics Voyager Platinum as I have it is a super expensive very nice device that worked BEAUTIFULLY in ICS, but now in 4.1 + you can not get more than 1 or 2 words across the mic unless you are YELLING at it like a crazy person on the SAME device].
So all that to say I think it is prolly related to changes Android made in 4.3+ flipped the Bluetooth operability on it's head.
Mic Volume OK with KitKat 4.4.4 and cheap "HB-800" headset
there've been no posts for a while so maybe the problem has gone away with the KitKat updates.
But anyway:-
I have a Nexus 5 and recently bought a cheap generic stereo earbud headset with mic from eBay .... $14.82 Ozzie including delivery to Western Australia.
I've actually asked the other party whether they can hear me (specifically "am I loud enough?") because I read this thread and have been assured that it's all good.
In fact it's a pity the sound quality at MY end isn't better, but that's probably the low quality ear buds rather than electronics / firmware reasons.
Of course, ymmv.
Here's the ebay item title in case anyone wants to look it up or I can pm the item number if it helps.
"Headphones Earphones with MIC 1st Stereo Bluetooth Hands-Free Wireless HV/HB-800"
No, the problem is still there. Reason there are no posts is that no one has a solution. Nothing has changed since March. I am somewhat controlling it with CM11 running on the ElementalX kernel. Without this kernel Bluetooth performance is unbearable. With it it is barely adequate.
It's funny that a cheap headset would work okay while multiple top-of-the-line everything-but-the-kitchen-sink models like the Plantronics Voyager Pro would still be having problems.
I was seriously considering getting the OnePlus One, the Nexus 6 and even the iPhone 6 hoping the issue would finally be fixed. It's ridiculous that a phone commonly accepted as the measuring stick of the Android world would be having problems with simple tasks like driving a bluetooth headset. *very disappointed*
Me too. Two days with my new N5 and when I use my Sony SBH20 people hear me bad... With my N4 no problem. Its annoying! Ive to speak with headset because Ive problems with my left arm and legs, I only have the right to hold the phone, I cant do anyhing more and when I walk I need that arm to hold my cane.
I dont see a real solution, I will have to return the N5
i've seen this being discussed a few times but with no resolve.I bought 4 oneplus one phones altogether.The first two were for me and my daughter bought a week apart.
These have worked flawlesly and both have been rooted both connect to the bluetooth in the car with no problems.
I then ordered one for the wife and the brother (family thing going here) they both arrived at the same time and both failed to pick up any signal...
I updated them through wifi then the phone aquired a signal with no problems.But here is the problem, both of that phones will not connect to the cars bluetooth..
everything on all the phones match up from the android version to the baseband so i can't get my head around why there is a problem.?
i hear that its a problem with cm ! but why are some working and others not?
are there any roms that are not cm11 based that i can flash and see if it is the software that's causing the fault or should i wait to see if there are any updates to fix this common problem?
It's the brother's phone thats the problem,he was a long time apple user and i convinced him to change to the opo now thats jumped up and kicked me in the butt...
if this is the wrong place to post this question i do appologise,not used to posting on forums.!
thank you
bluetooth problems
well here is an update if anybody is interested.I installed multirom and mahdi rom,bluetooth connects no problem now
I'm having the exact same issue. I had a Chinese OnePlus that connected easy-breezy to both my BMW and Acura cars. I got a new OnePlus just last week which has not been able to connect/pair at all with either car. The phone can not find any BT devices.
This is back breaking here in the anti-cell phone+driving Northeast.
When they do connect, as mine does, can it send/receive text msg's and emails via the car. Mine works for phone calls and music but no msg's. 2014 Toyota Corolla
same here, just got my OPO not quite a wek ago.
64gig-version, rooted, stock FW, latest OTA.
my BT headset connects just fine, just tried it in the car today, but the phone just does not find the alpine CD-headunit (connected fine with my GNEX or N4 before).
im actually thinking about trying ParanoidAndroid-ROM wich i liked very much on my N4.
any leads?
OK then, I just flashed paranoidAndroid .. Ta-Daa: connects to in-car BT Unit.
ParanoidAndroid by the way doesnt come with the OPO-Lockscreen, but the double-tap to wake up. just enough for me.
cheers!
Bizarre issue. It seems that lately my first phone call from my 2015 CRV results in louder than normal ringing and static-y voice noise from the person on the other end. I have to hang up, redial, and then it is fine. It happens with every first call I make or receive when connecting to bluetooth in the car. At first I thought it was an issue with the phone being rooted(sounds ridiculous I know) but that wasn't it. It seems to be on Marshmallow. I went back to Lollipop 5.1.1 and low and behold there is no issue. I took my girlfriends Galaxy S4 and paired it with my car and there was no issue at all. I don't want to waste my time bringing my car into the dealer because I have a feeling they won't know what to do so I figured I would ask here. I have deleted the pairings multiple times too when dealing with the issue. TIA
Well obviously it's a problem with marshmallow so I would wait for an update or stay on lollipop
Sent from my Nexus 5 using Tapatalk
Yeah agreed although pretty annoying.
I pretty much love this phone. It would be my ideal device if it had double-tap-to-wake. As it is, I could almost learn to live with using the fingerprint scanner (which I avoid using on all of my other phones) to unlock, but I finally encountered a deal breaker.
I have had all kinds of bluetooth issues. I have a lot of connected devices and I've been encountering the following:
Gear S3 constantly disconnects (even when it's really close to the phone)
Fitbit will not sync
Car Stereo Bluetooth profile deleted itself
AirPods break up, have static, or completely cut out
Here's the thing. I went back to my V20 and I don't have any of these issues. The Fitbit always syncs, the AirPods work flawlessly, the Gear S3 NEVER disconnects, and my car stereo has never disconnected. I have to believe it's a bluetooth stack issue. Perhaps the proprietary processor is to blame. But with all of the bluetooth devices I use on a daily basis, I can't live with this.
I really want to keep the phone, but I think I'm going to have to return it. That sucks because there's nothing else really like it on the market for me. But after all of the testing I've done, I can't draw any other conclusion. Maybe a software update might fix it in the future, but I can't take that chance.
I'm sure some of you will chime in and say "I'm not having any of these issues". That's great. I'm fairly certain you don't have the exact same devices/combination I've listed here. The fact is, my currently daily setup does not mesh with this phone. I still have my Mate 8, but I haven't tested this combination of devices with it yet.
I also have a big issue with this phone's Bluetooth. I can't pair it with a 2014 Pajero. Any other phone works perfect when paired with the car but this one cannot even pair. I always get "pairing failed".
I tried every oprtion and pairing application and still no success.
I know mate 9 has bluetooth 4.2 but it should be backward compatible.
Anyone has a solution or similar issue?
I wonder what firmware version your mate is on.
I'm running MHA-L29C432B138 and I have no problems with my Gear S3, nor with my Mazda bluetooth hookup.
Yeap, latest B138 version.
Gear S3 is fine. Only issue is the car connection
B138 here.
Won't connect to my 451 Bosch Highline car radio (they can't even see each other).
Connects fine to my laptops (Win & MacOS), BT speakers and Xiaomi Roidmi.
Sent from my MHA-L29 using XDA Labs
duraaraa said:
I wonder what firmware version your mate is on.
I'm running MHA-L29C432B138 and I have no problems with my Gear S3, nor with my Mazda bluetooth hookup.
Click to expand...
Click to collapse
I am on MHA-L29C567B138
I have the U.S. unlocked model. So, unless there's something specific about the firmware on that model, I don't know what to tell you. I have tested this repeatedly with all of my Bluetooth devices. Nothing works as it should, especially compared to my other phones. It would be interesting to see if I have the same issues on the Europe firmware, but I'm not flashing it to find out.
This bluetooth seems to be issue with this phone, does anyone know if this is something huewei is working on to fix or its an android issue ?
I hate to be the guy that says "mine works blah blah blah" but I've got multiple devices connected through Bluetooth and have yet to have an issue on any of them. 2 Ford vehicles running Android auto, 3 Bluetooth speakers and a set of Bluetooth headphones.
With that said, I wonder if your actual device is faulty. Has anyone with the issues done a factory reset? If so I'd be contacting Huawei support.
Sent from my MHA-L29 using Tapatalk
I have same issue as describe. My tought is mate 9 do not accept Bluetooth multipoint connection... 2 devices with same profil cannot be connected in same time
Envoyé de mon MHA-L29 en utilisant Tapatalk
I am wondering if the manufacturer is aware of the issue or not but to me it seems more of a Android nogut issue than anything else
I have the same issue. The Mate 9 takes about 3 minutes to pair with my car where my LGV10 automatically did it within seconds. It also does not seem capable of handling being paired with multiple Bluetooth devices at the same time. It has to be disconnected from one and wait to pair with the next one. For cars, I have tried it with both a Tesla and a Jeep GC and the I have the same problem.
greyhulk said:
I pretty much love this phone. It would be my ideal device if it had double-tap-to-wake. As it is, I could almost learn to live with using the fingerprint scanner (which I avoid using on all of my other phones) to unlock, but I finally encountered a deal breaker.
I have had all kinds of bluetooth issues. I have a lot of connected devices and I've been encountering the following:
Gear S3 constantly disconnects (even when it's really close to the phone)
Fitbit will not sync
Car Stereo Bluetooth profile deleted itself
AirPods break up, have static, or completely cut out
Here's the thing. I went back to my V20 and I don't have any of these issues. The Fitbit always syncs, the AirPods work flawlessly, the Gear S3 NEVER disconnects, and my car stereo has never disconnected. I have to believe it's a bluetooth stack issue. Perhaps the proprietary processor is to blame. But with all of the bluetooth devices I use on a daily basis, I can't live with this.
I really want to keep the phone, but I think I'm going to have to return it. That sucks because there's nothing else really like it on the market for me. But after all of the testing I've done, I can't draw any other conclusion. Maybe a software update might fix it in the future, but I can't take that chance.
I'm sure some of you will chime in and say "I'm not having any of these issues". That's great. I'm fairly certain you don't have the exact same devices/combination I've listed here. The fact is, my currently daily setup does not mesh with this phone. I still have my Mate 8, but I haven't tested this combination of devices with it yet.
Click to expand...
Click to collapse
It's interesting and frustrating how different people have different experiences.
As you'll see from my sig area, I am on US version, with 183 firmware. Interesting too, I had first tried a V20, and left it because of BT issues. As you are probably expecting to hear given my intro statement, I am not having BT issues. But, I am on different phone and firmware from most posts here.
I've only had my phone a couple weeks. When I received it it was on 138, and the GPS didn't work at all. Was about to box it back up and send back, but then checked, and had the update. After update, it's been great for me so far.
I'm not sure how different the 138 is from my US phone and yours...but a common thread for problems seems to be (based on this thread) is 138.