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.
Related
In the Mango previews I read that there was to be added bluetooth compatibility to help with the numerous issues that people have had with connecting with hands free devices.
See this thread if you are unaware of the problem.
http://answers.microsoft.com/en-us/...-problem/b53c64ce-30ee-4734-9dab-28ce0d561132
My question is:
Does anyone know for certain if this beta version includes the updated bluetooth? I have Mango beta on my Focus and so far I still have not been able to completely connect to my vehicles hands free device. I'm hoping that maybe it just has not been implemented yet.
Microsoft has updated the Bluetooth stack in Windows Phone 7.5, with the new stack receiving Bluetooth SIG approval on the 5th June 2011.
New is Hand-Free Profile 1.5, which should mean better support for Bluetooth car kits. Also updated is the AVRCP (Audio Video Remote Control Protocol) from version 1.0 to 1.3, which brings track and other meta-data information transmission and playback status information (paused, stopped, etc).
Unfortunately it still does not bring Sim Access Profile.
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.
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
In a news artical I read that the January 2023 pixel build broke blue tooth connection in cars. Can anyone confirm or deny the validity of this report?
Works fine in my car. P6P January update.
I cannot connect to car BT as well. Maybe because I'm on custom kernel. I'm gonna flash stock ROM again and check tomorrow.
I'm on a custom kernel too (Kirisakura) with no car bluetooth issues.
AlDollaz said:
I'm on a custom kernel too (Kirisakura) with no car bluetooth issues.
Click to expand...
Click to collapse
That's strange, definitely there a problem since many people reporting BT issues after January update
Literally just went out to the car to make sure I wasn't crazy. Works fine. I've got a 2012 Scion.
I can't connect to my car since the January update, I'm not on a custom Kernel. Guess I can try kirisakura in the meantime to see if that fixes my issue
DarkShadowMX said:
I can't connect to my car since the January update, I'm not on a custom Kernel. Guess I can try kirisakura in the meantime to see if that fixes my issue
Click to expand...
Click to collapse
It will not, I think that it depends on car, Jaguar XF here, no BT connection at all
felek73 said:
It will not, I think that it depends on car, Jaguar XF here, no BT connection at all
Click to expand...
Click to collapse
That sucks, I already flashed Kirisakura and gonna try in a bit but guess I'm SOL until Google fixes this
DarkShadowMX said:
That sucks, I already flashed Kirisakura and gonna try in a bit but guess I'm SOL until Google fixes this
Click to expand...
Click to collapse
Actually I fixed it. I unpaired my Garmin watch and paired again using Garmin App. Now watch is not visible in BT connection but is connected. BT in car is also ok so it seems that January build can't handle two BT connection at the same time
The reddit complaints are highly-specific to vehicle bluetooth only, not other BT devices. I run the kirisakura kernel but don't see how that would make any difference. I'll skip the January update until that gets fixed. I haven't seen any update publicly or otherwise from Google though.
I just updated to Jan23 and my BMW 5 series, my Galaxy watch, and my Resound hearing aids all work fine fortunately.