X10 mini pro Radio Chip - Sony Ericsson XPERIA X10 Mini

Can please someone say me what's the chip of FM radio that our devices use?
thanks.

---

Gee I just spent at least 15 minutes looking for that answer too.
Show me the ps output with BT on and I can probably tell you the family. btld or brcm_patchram_plus are components of the proprietary Broadcom BT stack which is the most common.
btipsd would be a TI device.
Just hciattach without any of the above might require checking the /init.*.rc files for the options to hciattach. Firmware files are also a clue, as is dmesg output.
Of course you might have a rarer Silicon Labs chip and lsmod might show it, or some fm device driver pseudo file in /dev/ and perhaps Si4709_driver.ko or similar somewhere.
If you have a working hcitool and bt is enabled this HCI Get Version command would show something similar to this:
adb shell hcitool cmd 4 1
< HCI Command: ogf 0x04, ocf 0x0001, plen 0
> HCI Event: 0x0e plen 12
01 01 10 00 04 00 00 04 0D 00 1F 1D
If you have a working hcitool on a Broadcom family device the following would be shown when the radio and RDS are on:
adb shell hcitool cmd 3f 15 0 1 1
< HCI Command: ogf 0x3f, ocf 0x0015, plen 3
00 01 01
> HCI Event: 0x0e plen 7
01 15 FC 00 00 01 03
And here's the equivalent on a TI device:
adb shell hcitool cmd 3f 133 20 2 0
< HCI Command: ogf 0x3f, ocf 0x0133, plen 3
20 02 00
> HCI Event: 0x0e plen 6
01 33 FD 00 00 03

---

Here's my output
Code:
# hcitool cm 4 1
hcitool cm 4 1
# hcitool cmd 3f 15 0 1 1
hcitool cmd 3f 15 0 1 1
< HCI Command: ogf 0x3f, ocf 0x0015, plen 3
00 01 01
Send failed: File descriptor in bad state
# hcitool cmd 3f 133 20 2 0
hcitool cmd 3f 133 20 2 0
< HCI Command: ogf 0x3f, ocf 0x0133, plen 3
20 02 00
Send failed: File descriptor in bad state
#
What does Descriptor means?

---

D4rKn3sSyS said:
Here's my output
Code:
# hcitool cm 4 1
hcitool cm 4 1
# hcitool cmd 3f 15 0 1 1
hcitool cmd 3f 15 0 1 1
< HCI Command: ogf 0x3f, ocf 0x0015, plen 3
00 01 01
Send failed: File descriptor in bad state
# hcitool cmd 3f 133 20 2 0
hcitool cmd 3f 133 20 2 0
< HCI Command: ogf 0x3f, ocf 0x0133, plen 3
20 02 00
Send failed: File descriptor in bad state
#
What does Descriptor means?
Click to expand...
Click to collapse
If you ran these commands with Bluetooth (BT) enabled, then in this case it means you have a proprietary BT stack.
In general: http://en.wikipedia.org/wiki/File_descriptor

---

mikereidis said:
If you ran these commands with Bluetooth (BT) enabled, then in this case it means you have a proprietary BT stack.
In general: http://en.wikipedia.org/wiki/File_descriptor
Click to expand...
Click to collapse
its broadcom bt. with brcm_patchram_plus you can check in se sources und platform/system/bluetooth/
here is kernel config:
CONFIG_BT_HCIUART=y
CONFIG_BT_HCIUART_H4=y
CONFIG_BT_HCIUART_BCSP=y
CONFIG_BT_HCIUART_LL=y

---

slade87 said:
its broadcom bt. with brcm_patchram_plus you can check in se sources und platform/system/bluetooth/
here is kernel config:
CONFIG_BT_HCIUART=y
CONFIG_BT_HCIUART_H4=y
CONFIG_BT_HCIUART_BCSP=y
CONFIG_BT_HCIUART_LL=y
Click to expand...
Click to collapse
OK, thanks much.
In that case my app should be usable on this phone in the currently experimental "HCI UART" mode, where a daemon speaks directly with the UART. It only works with BT off though, but I'm hoping to find a better HCI access method. Also need root.
I should post a new experimental version on the thread in my sig in an hour or so. One warning though; on many phones where my app tunes and gets RDS data etc, there is no audio. I'm working on "tricks" for that issue also.

---

mikereidis said:
OK, thanks much.
In that case my app should be usable on this phone in the currently experimental "HCI UART" mode, where a daemon speaks directly with the UART. It only works with BT off though, but I'm hoping to find a better HCI access method. Also need root.
I should post a new experimental version on the thread in my sig in an hour or so. One warning though; on many phones where my app tunes and gets RDS data etc, there is no audio. I'm working on "tricks" for that issue also.
Click to expand...
Click to collapse
thank you for your development!