[Android Development on Bada] hunktb:
Bluetooth S8530 ...

Thanks again, I don't really know; I edited my previous post to add this:

As this is something I can try to investigate without development (despite I don't have a S8530), I continue ...

I have found this link about bluetooth debugging in android: http://www.kandroid.org/online-pdk/guide/bluetooth.html.

In this link there are several debugging tools: hciconfig, hcidump, hcitool, l2ping. In badadroid I have found one in /system/xbin/hcidump

Maybe testing with them in S8530 we can get more info about the point where bluetooth is not working.

These are my tests in S8500.

With hcidump -Xt, this is the output of 2 scans, the first one without results (no nearby devices), the second one finding one device (galaxy ace with BC:85:1F:46:A1:D8 mac)

hcidump -Xt
HCI sniffer - Bluetooth packet analyzer ver 2.0
device: hci0 snap_len: 1028 filter: 0xffffffff
2013-05-10 00:45:30.817047 < HCI Command: Inquiry (0x01|0x0001) plen 5
lap 0x9e8b33 len 8 num 0
2013-05-10 00:45:30.823331 > HCI Event: Command Status (0x0f) plen 4
Inquiry (0x01|0x0001) status 0x00 ncmd 1
2013-05-10 00:45:41.065274 > HCI Event: Inquiry Complete (0x01) plen 1
status 0x00
2013-05-10 00:45:52.432931 < HCI Command: Inquiry (0x01|0x0001) plen 5
lap 0x9e8b33 len 8 num 0
2013-05-10 00:45:52.439335 > HCI Event: Command Status (0x0f) plen 4
Inquiry (0x01|0x0001) status 0x00 ncmd 1
2013-05-10 00:45:53.366612 > HCI Event: Extended Inquiry Result (0x2f) plen 255
bdaddr BC:85:1F:46:A1:D8 mode 1 clkoffset 0x50e6 class 0x5a020c rssi -32
Unknown type 0x47 with 8 bytes data
Unknown type 0x05 with 2 bytes data
Flags: 0x07 0x00 0x00 0x00
Unknown type 0x00 with 6 bytes data
2013-05-10 00:46:02.682272 > HCI Event: Inquiry Complete (0x01) plen 1
status 0x00

I have downloaded hciconfig from here https://code.google.com/p/androidobex/downloads/detail?name=hciconfig, and with "chmod +x hciconfig; adb push /system/bin/hciconfig", it works in my S8500 and it gives this info

hciconfig -a
hci0:	Type: UART
BD Address: D4:E8:B2:9E:39:DE ACL MTU: 1021:6 SCO MTU: 64:1
UP RUNNING PSCAN
RX bytes:1713 acl:0 sco:0 events:68 errors:0
TX bytes:1347 acl:0 sco:0 commands:68 errors:0
Features: 0xbf 0xfe 0x8f 0xfe 0x9b 0xff 0x79 0x83
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH SNIFF
Link mode: SLAVE ACCEPT
Name: 'GT-S8500'
Class: 0x5a020c
Service Classes: Networking, Capturing, Object Transfer, Telephony
Device Class: Phone, Smart phone
HCI Ver: 2.1 (0x4) HCI Rev: 0x2e8 LMP Ver: 2.1 (0x4) LMP Subver: 0x4217
Manufacturer: Broadcom Corporation (15)

Same for hcitool from here https://code.google.com/p/androidobex/downloads/detail?name=hcitool

hcitool scan I think gives less info than hcidump

hcitool dev
Devices:
hci0	D4:E8:B2:9E:39:DE
hcitool scan
Scanning ...
BC:85:1F:46:A1:D8	GT-S5830i

The diagram in the link suggest to me that "BT power on/off" is independent from the driver communication and maybe chipset is not really powered in S8530? I have been investigating with rfkill in badadroid, and I have discovered that in /sys/class/rfkill/rfkill1 , "echo 0 > state" stops wifi, and "echo 1 > state" starts wifi, but no luck finding something similar with bluetooth.

Also tested that somehow I can "bring down" bluetooth, but this I understand it is uart communication, not power.

hciconfig hci0 down
hciconfig
hci0:	Type: UART
BD Address: D4:E8:B2:9E:39:DE ACL MTU: 1021:6 SCO MTU: 64:1
DOWN
RX bytes:2318 acl:0 sco:0 events:83 errors:0
TX bytes:1424 acl:0 sco:0 commands:80 errors:0