It doesn't work on my ZTE Racer with custom ROM (2.3.3/CM7)
If it helps:
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 1D 00 C7 0D
adb shell hcitool cmd 3f 15 0 1 1
< HCI Command: ogf 0x3f, ocf 0x0015, plen 3
00 01 01
> HCI Event: 0x0e plen 4
01 FF FF 01
adb shell hcitool cmd 3f 137 1 1
< HCI Command: ogf 0x3f, ocf 0x0137, plen 2
01 01
> HCI Event: 0x0e plen 4
01 FF FF 01
It doesn't look like it should be, right? Is it because of the custom ROM or chip is incompatible?
Sorry, but thanks for your report.
The first hcitool command shows that Bluetooth is running and accessible, which is great as a first requirement.
The second two commands have a "01" at the end of their output which indicates the phone likely does not have a Broadcom or TI FM chip.
I did some quick googling and couldn't find anything definitive as to what FM chip the ZTE Racer has. The ZTE blade has, I think, an SI4709 (w/ RDS) or possibly a SI4708.
I'm hoping to be able to support the SI470x chips and will look into the issues. This chip is supported by the FM TwoO app and associated library I could link to. (But source code and specs are available though.)
AFAIK though, FM TwoO only works on Samsung Galaxy S. It doesn't work on similar Google/HTC Nexus S. Regardless, give FM TwoO in the market a try. An "adb logcat" and perhaps "dmesg" might give some useful info.
FM TwoO seems to rely on a "/dev/fmradio" device. Could you run this and report ?:
adb shell "ls -l /dev | grep -i fm"
I found some references to ChiperTest.apk which might be able to detect various chips. Apparently the dial code "*983*24474636#" might run "CHIPINFO Chiper Test (chip info) [Note: requires ChiperTest.apk in /system/app]".
I also found this for ZTE Blade I think: http://andorko.hu/android/ It appears to be an FM app with RDS, but relies on some modified kernel for RDS.
I'm hoping to eventually release a test app which might be able to identify chips and if the phone can be supported.
Last edited: