Develop Bugs

[Q] [REQ] Bluetooth MAP Protocol for Ford Sync

Is there any way that Bluetooth MAP profiles can be enabled for the Evo? I'm almost certain the changes would have to be at the kernel level... specifically, making additions to the Bluetooth stack.
Current Bluetooth Stack: Chipset: Broadcom BCM4329-B1
Current Bluetooth Version: Bluetooth 2.1 + EDR
Current Bluetooth Stack: Broadcom BTL-A
Currently supported profiles: A2DP, AVRCP, FTP, HFP, HSP, OPP, and PBAP.
This MAP profile would allow the EVO to send SMS and Email message information over Bluetooth to devices that also support MAP... namely Ford Sync.
I have found a few links that may provide leads:
google-summer-of-code-2010 BlueZ Bluetooth Stack for Nexus One: here
XDA forum for the G1 detailing a customer service rep attempting to explain AT commands: here
I know most Motorola phones also support MAP profiles, so the source for their kernels may be a good place to start.
I will continue looking for leads and picking through some source code... but I am pretty new to Android development, so any help or suggestions would be greatly appreciated.
Thanks!

Good luck, I have been posting all over the place trying to get an answer to this for my Incredible. So far, no one seems to be able to do it
addisonhammer said:
Is there any way that Bluetooth MAP profiles can be enabled for the Evo? I'm almost certain the changes would have to be at the kernel level... specifically, making additions to the Bluetooth stack.
Current Bluetooth Stack: Chipset: Broadcom BCM4329-B1
Current Bluetooth Version: Bluetooth 2.1 + EDR
Current Bluetooth Stack: Broadcom BTL-A
Currently supported profiles: A2DP, AVRCP, FTP, HFP, HSP, OPP, and PBAP.
This MAP profile would allow the EVO to send SMS and Email message information over Bluetooth to devices that also support MAP... namely Ford Sync.
I have found a few links that may provide leads:
google-summer-of-code-2010 BlueZ Bluetooth Stack for Nexus One: here
XDA forum for the G1 detailing a customer service rep attempting to explain AT commands: here
I know most Motorola phones also support MAP profiles, so the source for their kernels may be a good place to start.
I will continue looking for leads and picking through some source code... but I am pretty new to Android development, so any help or suggestions would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse

Have you made any discoveries in this?
addisonhammer said:
Is there any way that Bluetooth MAP profiles can be enabled for the Evo? I'm almost certain the changes would have to be at the kernel level... specifically, making additions to the Bluetooth stack.
Current Bluetooth Stack: Chipset: Broadcom BCM4329-B1
Current Bluetooth Version: Bluetooth 2.1 + EDR
Current Bluetooth Stack: Broadcom BTL-A
Currently supported profiles: A2DP, AVRCP, FTP, HFP, HSP, OPP, and PBAP.
This MAP profile would allow the EVO to send SMS and Email message information over Bluetooth to devices that also support MAP... namely Ford Sync.
I have found a few links that may provide leads:
google-summer-of-code-2010 BlueZ Bluetooth Stack for Nexus One: here
XDA forum for the G1 detailing a customer service rep attempting to explain AT commands: here
I know most Motorola phones also support MAP profiles, so the source for their kernels may be a good place to start.
I will continue looking for leads and picking through some source code... but I am pretty new to Android development, so any help or suggestions would be greatly appreciated.
Thanks!
Click to expand...
Click to collapse

Apparently some of the Motorola Droid models work with SYNC. I'd love to find a ROM that provides MAP. Alternatively, pointers to info on what Moto did to add this support would be appreciated.

any luck with this. I am in even more of a bind, being i am in canada, and the Droid Series of phones are not supported here.
Id really like to find an android phone that works in canada and is fully compatible with Sync

did anyone see this?
http://i-miss-erin.blogspot.com/2011/04/obex-message-access-profile.html
i don't know if it helps in anyway adding the profile to android?

Sgt.EddieWinslow said:
did anyone see this?
http://i-miss-erin.blogspot.com/2011/04/obex-message-access-profile.html
i don't know if it helps in anyway adding the profile to android?
Click to expand...
Click to collapse
This is cool... now, if I new how to compile this crap... it would be on!

[Q] New Bluetooth Stack in 4.2

New Bluetooth stack
Android 4.2 introduces a new Bluetooth stack optimized for use with Android devices. The new Bluetooth stack developed in collaboration between Google and Broadcom replaces the stack based on BlueZ and provides improved compatibility and reliability.
Does anyone know what the exact improvements are? I remember in ICS there was an issue with degraded audio quality when you had two bluetooth devices connected (ex: hands free car speaker, and audio streaming device).
My car only has phone support (no A2DP) over bluetooth, so I am looking into buying this in order to stream music. Ideally the phone can know when to send a call to the car and music to the aux plugin.

[Q] TW vs. AOSP Bluetooth

I have been running SkyNote 8.2 for a while now and have really liked Sean's ROM. I flashed Liquid last week (also a great ROM) and noticed something that I found confusing. With the TW Bluetooth (including the stock ROM), my 2009 car didn't really react well to the Bluetooth in my Note II. The connection between the car and phone would constantly connect and then drop off, connect again then drop off. Once I was on the phone (call), after initialing disconnecting me, the connection would stay but once I hung up it would go back to the on off cycle. My contacts would not sync either and yes I did grant access to the contacts. I just assumed it was because the phone has a newer Bluetooth profile (4) than my car (3). But after flashing Liquid my Bluetooth connection was fine, never dropped off and my contacts were all visible. I don't know much about the inner workings of Bluetooth, is the difference a TW thing?
Just looking for some insight from folks smarter than me.

Bump.... I would also like to know

AOSP only has Bluetooth 3.0 right now, so that's probably why you get more information. I have a FitBit and it only works with TouchWiz since it uses Bluetooth 4.0.

This is a fairly well known issue, but I haven't see a good summary anywhere, so I'll try here.
The problem isn't so much TW vs AOSP, it is Jellybean versions 4.1.x vs 4.2.x. Touchwiz is 4.1.2 and most maintained AOSP ROMs are 4.2.x.
Google, though their ultimate wisdom, decided to effectively castrate 4.2 by switching the Bluetooth stack.
From Android.com
New Bluetooth stack
Android 4.2 introduces a new Bluetooth stack optimized for use with Android devices. The new Bluetooth stack developed in collaboration between Google and Broadcom replaces the stack based on BlueZ and provides improved compatibility and reliability.
Click to expand...
Click to collapse
So...
Jellybean versions 4.1.x use the opensource BlueZ stack
Jellybean versions 4.2.x use the quasi-opensource Broadcom/Google stack called Bluedroid,
4.2.x has documented issues with audio streaming which are attributed to A2DP, or the Advanced Audio Distribution Profile. Google has proposed a fix, but the community consensus is that the issue remains.
Another problem with 4.2.x is that it doesn't support AVRCP 1.3 like 4.1.x did. This means that track metadata is not available to devices on 4.2. This is bad for me since I like to see track information when I connect the phone to my BMW M3.
I'm sure there are some workarounds on this problem, but I am not aware of a single, silver-bullet solution to make BT work flawlessly on 4.2.x Roms.
In summary, if you want to use Bluetooth in any meaningful way, stick with 4.1.x builds until Google gets their **** together. This is a fairly large miss on their part and they have been slow to address it.

Anyone know of any updates to this? There are so many 4.2.x ROMs out there that i love, but without a good BT A2DP connection, i just cant use that as the regular ROM.
ZoinksS2k said:
In summary, if you want to use Bluetooth in any meaningful way, stick with 4.1.x builds until Google gets their **** together. This is a fairly large miss on their part and they have been slow to address it.
Click to expand...
Click to collapse

[Q] Bluetooth 4.0 to 3.x DOWNGRADE, possible?

I have a Galaxy Note 2 running Jedi Master 13. Every single thing is awesome about this phone...
EXCEPT:
I have a Lincoln with the new MyLincoln Touch radio. It supports text messaging ONLY with ICS or more specifically, Bluetooth 3.x. The Bluetooth MAP (messaging access profile) is different in 4.0 and thus not supported. Is there any way to downgrade said Bluetooth version?
I only use BT stereo and phone headsets normally, never use file transfers so the 4.0 advantages wouldn't affect me (I hope).
Thanks in advance for the input! :good:

Did u try and call the dealership, maybe ur car has update they can do

BACARDILIMON said:
Did u try and call the dealership, maybe ur car has update they can do
Click to expand...
Click to collapse
Yes, yes I did. I was in touch with the people that make the MyLincoln Touch device that works with Microsoft Sync. I have the newest version, which supports up to Android 4.1.1 and the Bluetooth 3.0 software, which has advanced compatibility with MAP. The Bluetooth 4.0 doesn't work the same and makes it lose the ability to do SMS from the car itself. Ugh.
I was hoping I could somehow put the old Bluetooth stack onto my phone to make it work properly. As of right now, Ford/Lincoln say that only Android ICS' Bluetooth stack is compatible. I feel better than the Apple community, they don't even get pictures to transfer. At least It's cool having the address book picture on my phone.

So can it be downgraded or not?

I am also interested in this (for another device though). Is it possible in principle?

No this stuff is way too complex due to the new advancement of spamsung Knox controling everything, we have very little control of our devices any more

Android Pie (and Oreo) Bluetooth Pbap

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.