[Android Development on Bada] hunktb:
I am running out of ideas about bluetooth in S8530 vs S8500 so I give up searching by now. I share my last findings, maybe they inspire someone. Thanks to Volk204 and Ravariya for their help.

1. Android internals 10 - Debugging/Profiling, Bluetooth/WiFI/RIL (rev_1.1) Egor Elizarov

31 pages presentation with debugging tools: logcat, dmesg in page 8, ... but there are more things .... For example strace and dumpsys page 11 and they exist in badadroid. There are also tools for profiling/optimization. Pages 23 to 25 are bluetooth related.

2. Bluetooth changes in Android 4.2.2 (CM10.1). BlueZ disappears and is replaced by Bluedroid ... developed by Broadcom, so it should support better a broadcom chip like bcm4329

http://www.bluecreation.com/blog/android-dumps-bluez-and-integrates-broadcom-bluedroid-stack/

http://www.broadcom.com/press/release.php?id=s721534

http://xdaforums.com/showpost.php?p=35137737

ABS 2013: Android Jelly Bean Device Porting Walkthrough by Benjamin Zores Pages 111 and 112

Best Practices for Bluetooth Development, Google I/O 2013, May 15th

https://developers.google.com/events/io/sessions/326240948

3:25 The bluetooth core specification. Key versions from v1.0 to v4.0

3:41 android.bluetooth: Linux BlueZ stack (also Older Broadcom Stack and Motorola Bluetooth Stack)

6:57 "BlueDroid Stack introduced 4.2"

One of the speakers in this Google session (Mathew), says BlueZ s gooig to be abandoned:

https://groups.google.com/forum/?fromgroups#!topic/android-platform/CYtxCmtZ-WI

"We don't have resource to maintain both Bluedroid stack and bluez stack. Blue support is stopped after 4.2."

Information from android about Bluedroid (in some links the info is about bluez...)

https://source.android.com/devices/bluetooth.html

Curiosity: even ubuntu is thinking about switching from bluez to blued

https://blueprints.launchpad.net/ubuntu/+spec/client-1303-bluetooth

3. Tested bluetooth in CM10.1 it works in S8500 but no in S8530, but there are changes

-In /sys/class/rfkill, now there are just 3 directories, no 4

>busybox rfkill list

0: bcm4329: bluetooth

1: phy0: wlan

2: brcmfmac-wifi: wlan

>No hci0, and bluetooth persistent continues with 1 value in S8500, and now has 1 value in S8530

>bcm4329 continues starting with Software blocked=no in S8530 but yes in S8530

-No more hci* commands ! (hcidump)

-No more bluetoothd, no brcm_patchram_plus in init*rc

-No more /data/misc/bluetoothd: now /data/misc/bluedroid

-Now S8500 on first start is named "BCM4329B1 Generic FMRX 38.4 MHz" instead of "GT-S8500" (it is a string inside bcm4329.hcd file), but name can be changed ok.

-New logs in logcat

I/bt_hwcfg( 870): bt vendor lib: set UART baud 3000000

D/bt_hwcfg( 870): Chipset BCM4329B1

D/bt_hwcfg( 870): Target name = [BCM4329B1]

D/bt_hwcfg( 870): Target name = [BCM4329]

I/bt_hwcfg( 870): Found patchfile: /vendor/firmware//bcm4329.hcd

4. Bluetooth firmware

The file /vendor/firmware/bcm4329.hcd is the broadcom bluetooth firmware: there are others files for the same bcm4329 chip but they are wifi related

Details about the function of each file in http://redmine.replicant.us/projects/replicant/wiki/NexusSProprietary

One idea is to search for another bcm4329 firmware, maybe S8500 and S8530 have different ones ...

I have verified badadroid is using the firmware from aries https://github.com/teamgummy/vendor_samsung/blob/master/aries-common/proprietary/bcm4329.hcd, but there are others, for example I have tested this one in my S8500 and it works

https://github.com/faux123/android_.../firmware/BCM4329B1_002.002.023.0735.0745.hcd (internal string: BCM4329B1 38.4 MHz Class1.5 LGE_Star_SmartPhone)

I have also tested others firmwares that don't work, for example https://github.com/TheMuppets/propr.../firmware/BCM4329B1_002.002.023.0797.0863.hcd (internal string: BCM4329B1 37.4 MHz Class 1.5 AZW Module Ext LNA)

This firmware file is "loaded" into the chip (in CM10 with brcm_patchram_plus tool) through HCI (uart). This ubuntu bug is related and gives this info "If you don't have a hcd firmware, please try to get a hex firmware from windows driver, and convert it into hcd format. You can find the tool at https://github.com/jessesung/hex2hcd ."

5. Bada information about bluetooth

Testing with WinComm in S8500, I have been unable to see any log giving any useful information about bluetooth

I have been also unable to find any file similar to bluetooth firmware in bada filesystem, but I guess bada needs also a similar firmware file.