This: http://www.androidpolice.com/2018/0...ittent-failure-start-february-security-patch/
I'm hoping it will make my OP3T finally connect reliably with my JVC KW-M730BT.
Related
Just got a Robin to replace a N5X that was killed while on vacation in MX. The bluetooth pairs just fine the first time to all four of the bluetooth devices I routinely use. Despite them now being listed in 'Paired Devices' none of them will automatically connect to the Robin. Each acts as if its the initial pairing again, asking to be included as a trusted source, and the device being connected to requiring a confirmation on the pairing. And even then getting them connected again has about a 50% success ration (if that). The N5X never had issues automatically connecting to the same four devices. Is this a known bug and is there any work around?
***UPDATE***
Well, nothing I've tried could make bluetooth work properly on stock 7.1.1. Deleting all paired devices, factory reset, you name it. Fed up, I decided to flash Omni Rom and now bluetooth works as well or better than any device I've owned. As such, it's definitely a software issue with stock 7.1.1.
Had a clean install of Android 8.0.0 with August Security updates. No issues. Since I've installed the September security update at least one of my devices will no longer pair (car bluetooth lighter). Other devices pair okay but this one it either doesn't see it, or if it does and I try to pair get the error "Can't communicate with...." I believe there was a patch for a Bluetooth vulnerability in the Sept updates, wonder if their "fix" may have broken the ability to pair with some devices. Not good Google, not good.
Since updating for February, my Pixel will no longer auto connect to my devices. It is stock unlocked and rooted with Magisk. I have a Ford escape and every time I start it, I have to manually connect my Bluetooth now, as before it would do it automatically. Same thing with my Soundpeats Bluetooth speaker. Ive tried forgetting and repairing, any other ideas?
I have a 2017 Honda Accord Sport SE, with only the single display system that handles bluetooth and streaming etc.
Ever since somewhere around the May or June Oreo update and including the new Pie first production release, the car has been unable to transfer contacts from the Pixel XL to the car system.
I've played around with the AVCP setting, but that does not help. Briefly on the last version of Oreo, I was able to use the app "Bluetooth PhoneBook" to alter the phones PBAP so that my contacts were appearing in the car, but the first Pie version is now incompatible with "Bluetooth PhoneBook", so I cannot get contacts into the car system, and therefore cannot use voice dial with the phone. So I disable the bluetooth in the car and have to use my Plantronics bluetooth earpiece to make calls via bluetooth. The author of the app at http://www.android-rsap.com/bluetooth-phonebook/38-aktuelle-nachrichten/143-phonebook-app-and-android-8-oreo.html, mentions:
Google once again changed the internals of the Android Bluetooth stack, and guess what: it breaks my phonebook app. It is no longer able to properly stop the built-in phonebook service.
Today I found out that the latest Android source contains a change which once again enables my app. I don't have an idea when that change will be published in an official release or if there may be new Android 8 firmwares in the future which don't contain that fix. Simply check if your car connects to my app, if not you'll probably have to wait for the next firmware update.
And these problems all happen only because Google refuses to add a proper Bluetooth SDP API to the Android SDK. So they work their way from hack to hack. Sad...
Click to expand...
Click to collapse
Can anyone explain to me how the Bluetooth PBAP works an if this is an issue with the car manufacturer's implementation or Google's fault.
Unfortunately, Honda being a car manufacturer is not very interested in keeping firmware in its cars up to date, at least as far as phone functionality.
The 2018 Honda's allow firmware updates easily, so I imagine this is going to be less of a problem for 2018 and newer models.
Ever since installing the September update I have had troubles with Bluetooth connecting and staying connected to my Galaxy Watch 3 and my hearing aids. Everything worked flawlessly until that installation. Is this a known issue or has anyone else observed this?
Quite the opposite for me, this update has made my phone more reliable to Bluetooth connections.
My BT headphones disconnect all the time. I think my Fitbit does too
With A13, the Bluetooth stack used by Android was changed. I saw some issues early on (problems pairing, needing to forget and repair, pairings simply disappearing), but after redoing some pairings, things seem to be getting better. Still some odd stuff, like impossible options enabled (like "Input Device" and "Contact Sharing" on speakers without that capability).
It's obviously a work in progress.
As mentioned above by Mike, I did also do a fresh start no restore for Android 13 since I thought I was having issues with other things that was really annoying me with android 13 after upgrading to that, all the problems that caused me to fresh start were still present but almost all of these have gone after Sept update