Develop Bugs

Bluetooth Connectivity Issues

Dear All,
since having (official Oxygen OS) Android N on my OP3 my bluetooth headset (Sony SBH80) and most other devices are unusable. It seems the strength of the bluetooth signal has dropped by a factor of 10 - as soon as there is more than 1 meter air or more than one material (e.g. trouser pockets) between the phone and the headset the music starts skipping or drops out completely. When I have the phone in my hands near my chest, even tilting my head back breaks the connection.
- I tried other phones, they work completely with the headset fine in any normal use (phone in front pocket)
- The issue was NOT present when I was still on Android 6 (also stock Oxygen OS)
- I recently installed the Oxygen OS Beta (Android 7.1.1) with no change to the issue
I saw here in the forum and on various news sites posts about bluetooth issues with Android 7, but they were from the end of last year, still tried every "trick" or solution that was standing there. Here in the forum I only found posts about connection problems to car bluetooth. The thing is, I can connect fine, it's just that the signal seems to be too weak.
Is anyone facing the same issues or even better, was anyone facing the same issues and found a solution?
Thanks,
Georg

Unresolved BT issues... (updated after 7.1.2)

[I'm running a stock 7.1.1 without root or any other mods]
BT doesn;t work with 2 BT devices which can do phone...
Example:
1) BT watch, Huawei Watch connected - this watch can receive and make phone calls... It has a microphone and speaker, so it works like a full-fledged phone device. It is basically **** Tracy device... look it up ...
2) When the watch is connected, another BT phone device, like a car kit, doesn't connect. You can go to BT settings and manually click on the BT device to connect. Sometimes, it connects w/o extra help. And sometimes, clicking doesn't connect at all. Sometimes it connects automatically. Bugs!
3) When both devices seem to be connected (even though only one is shown to be connected), both can make calls, but only the "active" one receives them...
The active being the one that was connected last.
4)
------ This was not a problem in 7.1.0. Whichever device (watch or car kit) initiated or answered a call, would be used to do the complimentary function - If you make a call on watch, you get audio for the call on watch. If you receive the call on BT car kit, you answer on it. Without fail this worked just fine. Both incoming and outgoing calls. It made sense and it worked beautifully.
-----
Until 7.1.1.
---- Now, if a watch is connected (Huawei Watch, which can act as a phone itself), the BT car kit will not connect. If you connect it manually by clicking on it in BT settings, it will connect, but all phone actions, even initiated from the watch will only work on the phone.
In other words, 7.1.1 killed BT functionality with several BT phone devices.
Why can't they fix it?
UPDATE after 7.1.2
So, 7.1.1 killed phone functionality when both a phone capable watch and another BT phone device were connected simultaneously - both wouldn't work correctly at the same time.
7.1.2 didn't fix this at all.
What 7.1.2 did was introduce new bugs: 1) Weather built-in app no longer works on my Huawei watch, it just spins the circle retrieving weather data and then just goes back to watch face, 2) The watch no longer displays some notifications, for example, SMS.
I played with all of the settings in the watch, phone, and android wear app. Nothing.
I have a theory... Google has two android development teams. Let's call them Team A and Team B. Team A works on a yearly cycle developing new android OSes, for example, they are probably working on Android O right now. Team B picks up development and maintenance duties after Team A makes the initial android release. Team B would be working on Nougat right now. Team B is comprised of rejects from Team A; they have very little talent, attention to detail, or even skill. They may fix 1-2 bugs in an incremental android version, but they introduce 5 more new ones.
This is why Android 7.1.0 was less buggy than 7.1.1, and conversely, 7.1.1 was less buggy than 7.1.2.

Me with my powerbeats it seems to work but eventually it will stop playing music so I turn off headset turn back on and music starts playing again and then the music will start skipping because it hears background noise. It drives me nutts.

..

--

Worked for me.. I could connect to my headphones but yet it acted like it was not connected. Connected to my truck yet it acted like it was not connected.. I for the hell of it wiped dalvik/cache and now it all works with no problems. Headphones instantly worked after doing it. Truck worked just fine this morning..
Sent from my Pixel XL using Tapatalk

--

..
Sent from my Pixel XL using Tapatalk

I'm on stock like the OP. My bluetooth issues are similar and I have one more.
Devices I'm paired to disappear from the BT list. I got in my car yesterday and was surprised the screen needed me to enter my PIN as I had my car in Smart Lock. Go look and sure enough not connected to the car and the BT list doesn't have my car listed as a device. I had to re-pair to the car. Then I had to readd to Smart Lock. This has happened with other BT devices (primarily headsets as that is really the only other things I use with my phone). This happens frequently and almost daily that I lose one or more BT paired devices from the list.
Other times, primarily with my Bose QC35 as I frequently turn it on/off, it will be in the BT list but the phone says I need to pair the device again. This only happens about every 10th time I turn the headphones back on.
Unfortunately, I've only had 7.1.1 on this phone as it is only a few weeks old. So I don't know if stuff would have worked in 7.1.0.

djr4x4 said:
Worked for me.. I could connect to my headphones but yet it acted like it was not connected. Connected to my truck yet it acted like it was not connected.. I for the hell of it wiped dalvik/cache and now it all works with no problems. Headphones instantly worked after doing it. Truck worked just fine this morning..
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
I'd like to know what you did to make things work.

Updated op with 7.1.2 info.

Bluetooth issues

Hi. Wondering if anybody could help. When I connect my oneplus 5T to my car I have problems. When it starts to call it disconnects the bluetooth from the car completely. However the call continues on the phone which is a complete pain as you cant use it through the hands free. Car is a BMW 630CI with pro nav if that helps.
Many Thanks

i first had problems to connect to my audi A3 bluetooth ... it simply didn´t find it
after trying again and changing the bluetooth audio codec it suddenly worked ...
Idk if it will work for you, but you can try changing the codec and se if it helps

Hi. Ive tried all 3. It connects fine and I can see my contacts but as soon as I hit dial it disconnects from the car.
Very strange.
Thanks for the suggestion tho

with mine in my car it every now and then gives me this a crackling sound.. Kind of irritating, I'm hoping a software update down the road fixes this.. I've tried all 3 codecs

Having issues with Bluetooth connection on my Prius Prime as well. It always disconnects, I had to disable Bluetooth on the phone and re-able it for it to work.
I experience the same with my Boss QC35. First connection, audio breaks with lots of noise and had to disable it and re-enable it.

Still found no solution. Hope the next update sorts it out as the bluetooth seems a mess.

So after looking around, there are issues with certain codecs and devices connecting being posted in the OP community forums. My Sony WH1000xm2 headphones stutter when using AptX HD. My JBL Everest 750NC's - if you turn the volume up too high, they disconnect from the phone. In my Cadillac ATS, whenever you place a call it'll stay connected, but you won't hear anything, and the other user can't hear you either.
I think they've acknowledged the issues and are working on them, but after putting Oreo on my Moto G5 Plus and Oreo's ability to change between all codec's on the fly (including native LDAC support!) I'm anxiously awaiting Oreo to be 'officially' released.
I'd say just be patient.. I'm sticking with this phone because I think it'll be worth it in the end. Wish I had better news!

so I resolved my Bluetooth issues by flashing FreedomOS. Now there is no intermittent crackling sound now and there is no issues at all ymmv, this was just my experience.

Thanks. Will wait for Oreo and then try different roms if it continues.

on FreedomOS before, it was giving me headache re-connecting to my Subaru car bluetooth, like after you shutoff engine, go somewhere and come back, unless you manually force connecting to the car, it barely auto reconnect back.
And also takes so long to get data sync from my Fitbit chargeHR to the app.
I don't think this kind of bluetooth issue related to what rom we have but the kernel and more specifically BT firmware.
-----edit-------
My friend also got BT issue when he tried to connect to BT headset. Hope Oneplus get something fixed on new oreo or updates

Just an update. Since upgrading to the official Oreo rom my problems have disappeared and my phone now works fine with the car Bluetooth.
Chris

I still have problems. Pause and unpause, and the track restarts. After ending a phone call the track restarts. 2018 RAM, Uconnect

With stock ROM 4.7.2 bluetooth connected only for a few seconds with my Audi A6. With every following stock ROM version it didn't even connect.
I tried every single Audio-Codec and the different settings in developer options - nothing helped. Once I cleared data & cache from the bluetooth system apps followed with a soft brick

Hi all,
Had same issues with my Hyundai ix35 and oneplus 5t (Nougat), tracks skipping, distorted audio in calls, etc... Tried emptying bluetooth cache, switching audio codecs without success. Now I just received the OTA update to Oreo (8.0), Oxygen rom 5.0.3 and it solved the issues!!! Yeay, no more auxilary cable hanging around !

fx_viper said:
Hi all,
Had same issues with my Hyundai ix35 and oneplus 5t (Nougat), tracks skipping, distorted audio in calls, etc... Tried emptying bluetooth cache, switching audio codecs without success. Now I just received the OTA update to Oreo (8.0), Oxygen rom 5.0.3 and it solved the issues!!! Yeay, no more auxilary cable hanging around !
Click to expand...
Click to collapse
I started from scratch but the issue persists.

I am having the same issue in my car. It no longer displays track information and the connection is not very stable. I will try switching the codec and report back.

i don.t have any volume control from the phone basically when i connect it to my car stereo
i can control the volume for the first 4-5 clicks ... and then the slider moves but there is no difference in the volume
i have to turn the volume from the stereo almost to the max
whit my old samsung tablet works great ... i have maybe 50% more volume then with my phone
tried all codecs ...

Weird problem re. Bluetooth phone connection and dialing out

Hi guys,
I own a Ford Mondeo (Fusion) built in 2007 and have a problem using my 5t with it's bluetooth hands free.
It works fine, gets recognized, phonebook is in sync.
Problem is it seems to loose connection when dialling very often, but not always. I dial the number, my radio mutes and brings up one ringtone and then all of a sudden it unmutes, plays music again and the phone continues dialling anyway, as if no bluetooth would be active. Normally this happens once or twice and then works the third time around.
Havent found a couse for this issue, it worked flawlessly with all predecessors.
Any ideas on that?
I am running Open Beta 9 on Oreo 8.1.0 but it also was the case on stock 8.0.0. Cant remember how it was under Nougat, tho.

i Have a 2010 mondeo and i have the same issues.. it does work if i dial the number from my actual phone, but scrolling though on the car stereo and dialing a number doesnt always work.
I'm sure its an issue with the car and not the phone.

Well, I think it's solved....and it seems OP did the trick. A few days ago I installed the OTA update onto Open Beta 10 and havent had the error once since then. So maybe this might be worth a try for you as well....
Anyway, I dont think its the car coz all the other devices before the 5 t worked from the off.
Lets hope it now stays that way.

Bluetooth phone call issues in car

Hey there,
I'm currently running a OP3 with the OmniDragon 8.1 ROM and previously the ResurrectionRemix ROM. However, I do not believe this issue to be a ROM issue so that's why I'm posting here instead.
I've recently been having some issues with bluetooth and was hoping someone could help. I can connect my phone to my cars handsfree system perfectly fine and it works correctly. I can play music via Spotify and any other music player fine.
However, as soon as I make or receive a phone call I'm left where the person can't hear me, and I can't hear them. I can't even hear the ringing tone when phoning someone. However, as soon as I turn it from bluetooth back to the phone or just regular speaker, it works fine.
This previously was not the case when I was running Nougat.
But as soon as I upgraded to 8.1 this issue started happening.
I don't think it has anything to do with the ROM and is actually something to do with perhaps OP3 Firmware/Modem or something similar.
Car hands free works fine with other phones like an iPhone, so that's out of the question.
I've attached a catlog to this post from when this issue was happening in the car, so hopefully someone can narrow it down for me.
Any help is appreciated!

Actually many roms have been having issues with BT calls. It's due to some of the changes in the telephony package.

Hello, did you manage to find any Oreo rom that fixed this issue for you? Would appreciate any tips.
I too have had similar issues with Oreo and OnePlus 3. Using an handsfree Jabra Freeway and the microphone often does not work when I answer or phone someone during a drive. Which is extremely annoying and dangerous.
I had hopes that with the release of some alpha Android Pie roms, these BT issues would be fixed. But the issue seem to persist, at least for my device.
My only fix was to go back to nougat. The most stable rom i've found is the unofficial lineage 14.1 by sultan. This have been my daily driver for awhile now and seems to work fine.