yashsingh1/xdaforums huggingface dataset:
[Spirit FM] mikereidis:
Reminder: In this 2.0.11 version, for normal BT access you MUST turn Bluetooth on manually.

Settings -> Wireless & networks -? Bluetooth and check the box. Personally I use the CM power widget; nice and quick for testing.
[Spirit FM] idkidk:
Hi to all,

i'm tryng all of above for my galaxy tab, but i'm not able to install/use hcitool for get the correct service hciattach, i'm a little bit confused, any help?

Tia

Idk
[Spirit FM] idkidk:
quote myself :eek:

I've installed the hcitool, but when i try hciconfig, no resut....

Tia

Idk
[Spirit FM] CR5N:
Installed latest files but radio app times out and fc required. Permissions set as suggested and reboot tried after each fail.

Bluetooth enabled and radio starts up. Still need ssd commands to enable audio.

Edit: HD2 on gb2.3.4
[Spirit FM] mikereidis:
Hi Idk,

I guess I need a "trouble-shoot" option that will send me the info I need from phones with problems.

Do you have adb installed on a PC and can you use it ? If hcitool was not already on your phone, it is unlikely to work by copying the hcitool from elsewhere.

The "adb shell" commands below work from a connected PC. Without adb on a PC you can use a terminal emulator and remove the "adb shell" part, but term em's are a pain to work with unless you have a physical keyboard,

With bluetooth on, when I run:

adb shell hciconfig dev

I get

hci0:	Type: BR/EDR Bus: UART

BD Address: 64:9C:8E:6B:72:E2 ACL MTU: 1021:4 SCO MTU: 180:4

UP RUNNING PSCAN

RX bytes:85525 acl:0 sco:0 events:5582 errors:0

TX bytes:40849 acl:0 sco:0 commands:5582 errors:0

When I run:

adb shell hcitool cmd 4 1

I get

< 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 get similar output and have a phone with a TI or Broadcom FM chip, the app should work. The signal indicator, RDS and seeking should wotk, although audio routing could still be a problem.

If you do not get similar output, then the original normal hcitool method of HCI access will not work for you. Your best hope is then this new HCI UART access method for Broadcom FM chips.

Unfortunately, so far, I'm the only one who has gotten the new mode working and it appears some trouble-shooting and fixing are required.
[Spirit FM] mikereidis:
Thanks for your patience and efforts CRSN. Do you have a SuperUser type app that asks for permission to let my app do things ? If not, the SU stuff will likely not work and you will see these failures.

To re-iterate some stuff, and add a few details:

- The new daemon modes will not work if BT is on and hcitool still works.

- For the direct HCI access mode, which I recommend as a test if hcitool method works, reboot, or make sure FM app is off, and turn on BT and rename or move hcitool so that "adb shell hcitool cmd 4 1" fails.

adb shell ps should show now the bcprp process running. adb logcat should eventually show a line starting with "srv_len:" and a /sdcard/bcfmok file should now exist.

- For the HCI UART mode, BT must be off and the stuff in the paragraph above should apply.

Your observations and "adb logcat" output would be very helpful in resolving this.

In the meantime I'll try looking through the code, trying the emulator and adding log stuff to help.
[Spirit FM] alphaori:
I jumped from latest market version to 2.0.11. It works fine the first time. After turning the radio power off, I can't turn it on again: radio times out and fc is required. I also cannot turn on bluetooth.

With Direct HCI access, it works fine.

I attach the logs running the app in HCI UART mode (bluetooth off). First time, it works and I switch it off. The second log, shows the app trying to run again.

Thanks for your wonderful job.
[Spirit FM] mikereidis:
Your welcome and thanks for your report, especially the logs. You are the first to report even partial success. Can I ask what phone and ROM you are running ?

In the ancient version 1 of my app, some people got the direct HCI access daemon mode working and other's did not. And this was all on the same phone and ROM: the HTC Legend with CyanogenMod.

I'll look over the logs and report.

Here's an idea for those having trouble with the daemon. Daemon communications requires network sockets. All 3 Android phones I've had supported network comms to the loopback address even when all networking was turned off: the wireless and 3g. But some phones/ROMs may not.

So try enabling wireless and 3g and any other network type enables. On some phones this might be required. If "adb shell ping 127.0.0.1" or from a terminal emulator "ping 127.0.0.1" is successful, the the daemon comms should work.
[Spirit FM] sirskull:
Hi, did some already test a HTC Blackstone?

I'm running a mix of FRX06 CWM and FroyoXGinger.

Blackstone is using the Broadcom chipset BRF6350.

I'm able to see the reception meter changing on known frequencies but no audio. Also no RDS.

Maybe the logcat file will help?
[Spirit FM] alphaori:
Sorry: I forgot to mention it. It is a HTC Desire running Oxygen v2.1.2.
[Spirit FM] mikereidis:
OK, great ! Oxygen seems to be popular.

It appears to me that the bcprp daemon is not being killed. If you could somehow run "killall bcprp" or "killall -9 bcprp" that should fix things when the radio is powered on again, without having to reboot.

The code in the app that does this needs improvement. It was a last hour addition to make things more automatic.

Also the bcprp daemon should be improved so that it does not need to be restarted. I'll try to get these issues fixed ASAP and post a new version.

I see from the logs that you are getting RDS traffic data. The raw data is shown in the logs but it doesn't appear in the app yet. Can you tell me what country you are in and what country the station is in ? Thanks !
[Spirit FM] mikereidis:
Yes, all logs help, thanks !

You are the first to report on the HTC Blackstone / Touch HD / T828X. I see it's a Windows Mobile phone with several Android ROMs available.

The log file looks good with no unexpected errors. For RDS on the 6350 there is a strange byte re-ordering in the code that I copied from a TI driver, but perhaps if I disable this, it will start working for you. I would think there would be some errors in the logs though.

The following commands are done in the app and will enable audio on stock HTC ROMs, but not on CyanogenMod ROMs, nor most aftermarket ROMs. These MIGHT work for you so please try:

adb shell "echo fm_headset > /sys/class/htc_accessory/fm/flag"

adb shell "echo fm_speaker > /sys/class/htc_accessory/fm/flag"

After either of these, try this to confirm the setting:

adb shell cat /sys/class/htc_accessory/fm/flag

If I can confirm your audio chipset, I can create, or repost one of my existing audio control utilities. For this it would be useful to get the output from:

adb shell dmesg

adb shell ls -l -R /dev

The "adb shell dmesg" command is best done after a boot, then run the app, and run the command again.
[Spirit FM] mikereidis:
I think at least 50% of Android devices have the theoretical potential for FM, via Broadcom or Texas Instruments BT/WiFi/FM combination chips.

But sadly most of those don't seem to have the needed antenna, power or audio connections. At least one person soldered an antenna successfully to a well marked spot on the PCB of a cheap Chinese tablet, but no audio.

In theory sometimes audio might be send-able direct to a Bluetooth headset even without analog audio connections....

I don't recall your ROM, but it might be possible to get my app working, more or less, and at least see the result. But likely you would see an RSSI of around 0 at best, due to no antenna or grounded antenna pin.
[Spirit FM] ARieS_:
For Nexus One ICS;

First open the bluetooth to found chip, then Settings>Audio>Method>qsd8250 for sound.

Issues:

-When notification came, shotdown or change to headset from speaker.

- I forgot. :)

Sorry for my English.

Sent from my Nexus One
[Spirit FM] mikereidis:
Is this a stock ICS and is it rooted ? I can look a bit if you point me to which ICS it is.

This is expected with many ICS ROMs at this time.
[Spirit FM] Barracuda72:
How can I help with bringing Spirit FM to Ideos X5 U8800 Pro? I tried to run it on stock FW (B512, Gingerbread 2.3.5), it starts, but after 5-6 seconds of "Please wait"-ing, phone hangs and then reboots.

U8800 Pro differs from U8800 - it has Qualcomm 8225 instead of 7230.
[Spirit FM] mikereidis:
I've been working on the rare Tavarua chip support this past week, for Ideos X5, X6 and Acer Liquid Metal. There's an active thread here: http://xdaforums.com/showthread.php?p=22218317

I've been led to believe though that the Pro version doesn't have the same chip, or perhaps doesn't even have FM at all. Is there a stock FM app known to work on any u8800 Pro ?

I can say more if you send me a log with Menu->Help->EM Logs, and enter "u8800 pro" in the email text after a few seconds, then press send.

But a crash at startup will prevent this. You can prevent the crash by disabling Superuser access for my app. That may be easier if you remove and re-install my app and then select "Deny" when Superuser pops up.

There is something different with the SU feature on Ideos devices and that's why the crash. I'm working on a new release now that should fix that, and provide more reliable log sending.
[Spirit FM] mikereidis:
Feb 6: http://www.mediafire.com/file/1003o9171yolu16/Spirit_FM_Radio_v120206.apk

Mostly with enhancements for Tavarua chips in Huawei u8800/u9000 and Acer Liquid Metal. See this thread for more specific details: http://xdaforums.com/showthread.php?p=22238481

Modified SU mechanism that I hope will work better on several devices.

Added a permission so logcat can be run on non-rooted devices.

Broadcom and TI proprietary support are enabled by default. Samsung Silicon Labs proprietary support is enabled if the /dev/fmradio device driver exists.

Motorola proprietary support is still disabled by default, and doesn't seem to work, except on MIUI for Galaxy S.
[Spirit FM] CR5N:
Mike,

Installed full version on HD2 running Tytung Nexus3.2a

Everything runs out of the box, great job. Audio is much improved even with screen on (used to get noise on reception with early versions and othet fm apps) :cool:
[Spirit FM] ARieS_:
MeDroid CM9 http://xdaforums.com/showthread.php?t=1411429 CyanogenMod and it's rooted.

Sent from my Nexus One
[Spirit FM] mikereidis:
Good... And thanks for your purchase/support. :)

If there was noise before and it's gone now, I wish I knew what fixed it. I don't think I've done anything really for Broadcom support lately.

I'll presume that when it starts it says "FM: BC" in the radiotext area, and not "BC Proprietary". Proprietary could affect this.

If other FM apps (Stock ?) were affected then perhaps it was just a loose connection around the headset/antenna...

Let me know if it returns, but unless we can see that one release is OK and another is bad, I'd think this is likely a hardware issue.
[Spirit FM] spunker88:
Works on the Droid 3 with stock rooted using either Audio Method Motorola or Motorola2. Its the same hardware as the Bionic so I figured it would. Volume control with the hardware buttons is unpredictable, sometimes it works. Outside of the app it doesn't work at all, but neither does the Motorola app.
[Spirit FM] CR5N:
Mike, you are correct in that noise is very likely due to hardware as this is a refurbished phone :rolleyes:
[Spirit FM] mikereidis:
Sometimes they just test a returned phone quickly and then throw it in the refurbished pile. Other times they don't even bother to test, LOL. And factory return replacements often come from that pile too, which explains why some get 3 replacements all with problems.

If it's a noisy connection, a quick squirt from a aerosol can of electrical contact cleaner may help, or using a different headset.
[Spirit FM] mikereidis:
Good... I love success stories in between all the problem reports. :)

Volume control may improve if you enable Settings->Debug->Silent Loop and restart the app. This uses some CPU and might drain the battery a bit faster though.

So reception is OK and RSSI is at least 20 or so on decent stations ? I get the feeling the Droid 3 and Bionic don't have the hidden "antenna switch" that Droid 2/X and some others have.
[Spirit FM] spunker88:
Reception is the same as the Motorola FM app that has to be sideloaded, about what you would expect for using headphones as an antenna. The Droid 3, Bionic and RAZR all have the WL1285 chip from TI so in theory all 3 should work unless the FM part of the chip isn't wired.

The only reason I can see why they would include perfectly working FM hardware without an app is because big red would prefer people use up bandwidth streaming. The international version of the Droid 3 includes an FM app.
[Spirit FM] tsynik:
Silicon Labs and other USB radios

mikereidis, thx for the great app. I tried it on my WITS A81 with TI chip, but there was problem with audio routing. One design flaw in Spirit FM: try to use it on tablet or a phone in only landscape mode (as i do in my car and tablet instead car stereo)... it will be not comfortable at all. Adding few layouts just a sec ;-)

You told about Silicon Labs / V4L support. I have new tablet with full kernel and android sources (so i can add support to any chipset in kernel), and i only miss working FM radio in Android 2.3 system. My tab have USB host, so I use it for connection to HQ USB audio, GPS etc. I also want to add FM USB stick (SiLabs based, for example, or other V4L device with FM cap). Is it enough having appropriate /dev/radio /dev/snd/xxx for Spirit FM to work with it? Or, can you suggest proper USB hardware?
[Spirit FM] mikereidis:
The paid Unlocked app supports a Landscape mode. You can see it in the 3rd screenshot on the Android Market listing. What do you think of that layout ?

If you search this thread for A81, someone tried already. He got a decent signal once he soldered an antenna wire, but we never determined audio routing. Send me a log and I'll take another look. Use Menu->Help->EM Logs, wait a few seconds, then put A81 in the email text.

I wish there was an easily available USB FM stick that could work. I would support it, if it could be at least a reasonably popular option.

I imagine analog audio output to a dedicated jack would be good, but digital audio via USB would be a nice option, albeit requiring audio driver support on the Android device.

The current V4L support is oriented towards Qualcomm Tavarua, but should be generic enough to work with other V4L devices. This would require a /dev/radio0 device for radio control. Audio control would likely have to be customized somehow, but that can still be done with shell scripts or other binaries as I was doing 6 months ago.

If needed and useful, I could even support such shell scripts or binaries for radio control, and any chip/device that can be controlled with Linux commands could be supported. But there hasn't been any call for that. Almost nobody wants an FM toolkit, they want an app that "just works".

I think most Android device kernels probably don't include V4L drivers for any FM tuners, except a few that use V4L natively. So you'd likely need a new kernel or loadable modules (and root).

So there are some USB FM sticks out there. I've decided for now to forgo any substantial research on the subject unless sufficient demand is apparent.

But if you can get V4L working, I'll do what I can to help you.
[Spirit FM] mikereidis:
( ? Is Big Red = Verizon ? )

Yes. And I wish I could say one way or another with 100% confidence.

AT&T still have at least one new phone with OTA FM and I've wondered why. I forget, but perhaps it was a cheaper one, and their users might not pay for a data plan anyway, or it's for pre-paid or a non-data plan or something.

Who knows, one manufacturer might sell their device a little cheaper with no FM app, and another might actually raise the price for the "customization" of removing the FM app.
[Spirit FM] mikereidis:
Feb 8: http://www.mediafire.com/file/eb1s5tg8d4ecyl1/Spirit_FM_Radio_v120208.apk

Best improvement should be for logging, especially on non-rooted devices.

This is close to Market release and it would be very helpful if I could get "Email Logs" on as wide a variety of devices as possible. If you can, try disabling SU access for the app so I can see if that works.

So: Select Menu->Help->EM Logs, wait a few seconds, then enter your device, ROM or other useful info in the email text and press send. Thanks !

If you enable Debug->Extra Logs and have SU, the Android bugreport utility output will be included. It might include phone numbers or IMEIs or similar info. It also takes around 20 seconds on one of my phones before the app will respond again.
[Spirit FM] mikereidis:
email:

First, please try the Feb 8 free version here: http://www.mediafire.com/file/eb1s5tg8d4ecyl1/Spirit_FM_Radio_v120208.apk

Thanks for your purchase. :) Send me enough info to verify and I can send you the latest Unlocked if you want.

The free version can be useful to test new features without messing up a working Unlocked app install.

Then please send me a log with Menu->EMail Logs, wait a few seconds, then enter your phone type /ROM in the email text and press Send. If possible, do this after a fresh boot and first start of my app, or when the problem appears.

Your problem seems very unusual and unique. HTC Tattoo/Click CM7.0.0 dates back to April of 2011; very old ! Can you update to the last CM7 nightly here: http://download.cyanogenmod.com/get/cm_click_full-256.zip , at least to test ? I'll presume you make a backup if you need to go back.

So the problem happens sometimes and not others ? Does the audio stop ? Is RDS affected ?

Is there anything, like some system setting, or hardware related, that changed when the problem started ?

Since the TI chip is a combination chip, try changing the WiFi power state and see if it helps. Bluetooth On is required on TI chips.

There is no specific reset I'm aware of that would help across phone reboots. Sometimes pulling the battery for 10 minutes can reset such things though, so please try that.
[Spirit FM] zamiurratul:
Great work, just Needs ui improvement

Works fine with my i9000 ICSSGS 3.1 with the plugin "GALAXY S ASLA"

but i cant help saying UI NEEDS A MASSIVE IMPROVEMENT, otherwise its LEGENDARY

I have two questions :

**1. My phone showing me wrong (???) RDS data, it shows -

Fm:SL Sh:1 Su:1Bt:1 Ht:0 H2:0 Mo:SLS

Why its showing this instead of RDS? ( I am using the free version)

2.Is it safe to use "GALAXY S ASLA" with/without headphones ??
[Spirit FM] J_Palito:
Hi!

Sorry, I meant 7.1.0, but I could install the last nightly.

The audio does not stop, it just makes noise like if the antenna was not connected, although it is.

It's the same with the WIFI on. Bluetooth is also On, as it doesn't allow to be off.

I think the problem is in the chip, not in your software, of course.

I don't recall changing any system setting, but nothing like re-installing everything to test it.

Just pulled out the battery for more than 10 minutes, it didn't worked...

Later I'll try the nightly build and report it to you.

In the mean while, I'm sending you the report, as you requested.

My best regards,
[Spirit FM] mikereidis:
UI improvement is still on hold until I can support most phones on which FM is possible. Currently I'm working on support for un-rooted phones with stock ROMs, which are in the majority. Rooted devices are just a small niche in comparison.

I work on this project 80+ hours per week, for the last year. The only way I can keep that going is to earn sufficient income. I won't be able to do that until I support un-rooted stock phones.

(1) You are seeing debug info. RDS is only available on the paid Unlocked app.

(2) I can't really feel confident about speaker safety until I go a few months without damage reports. I think the phone call fix also fixes this, but I only added it a few weeks ago. I had 2 new reports in the last month, but they were using the older release still on the Market that I hope to replace today or very soon.

So, proceed at your own risk until we get to at least May with no more reports on newer releases.

The good news is that 2 different people reported replacing the speaker was all they had to do. No permanent IC damage.
[Spirit FM] mikereidis:
I think this is most likely a hardware issue, in your headset cable or in the jack.

You could try a different headset, or just try jiggling the plug in the phone to see if reception improves. An aerosol can of electrical contact cleaner may also help.

In theory it could be some software issue related to the headset jack, but loose cables or connectors are almost always the cause of just about any intermittent electronics problem. Headset cables take a lot of "abuse" during normal use.
[Spirit FM] mikereidis:
Feb 9: http://www.mediafire.com/file/bq5z6rahsclh50z/Spirit_FM_Radio_v120209b.apk

Mostly logging and Tavarua fixes.
[Spirit FM] DarkSorcerer:
I'm sorry to ask, but this already has the fix for Galaxy S Alsa? :o

Thank you,
[Spirit FM] mikereidis:
Yes, all test releases since Jan 29.
[Spirit FM] mikereidis:
I've finally released the first new market version in 1.5 months: Feb 10:

https://market.android.com/details?id=com.mikersmicros.fm

It's almost identical to Feb9b, except I disabled some potentially trouble-causing background logcat collecting. It can be re-enabled with Settings->Debug->Extra Logs.

I expect to wait at least a few days before updating the Unlocked app so the 54,000 active free users can help test before the 449 active Unlocked users are "inflicted". :)

The biggest change since last Market release December 23 is the support for proprietary APIs on stock un-rooted devices. I'll post more info later.
[Spirit FM] DEMONTER:
working on huawei x5 but there rebut...
[Spirit FM] goodoane:
@mikereidis

I use the 120129 version on ICSSGS 4.2 on galaxy s and I found a bug: no icons on taskbar (status bar) and no menu also in dropping down taskbar. Hope you can get back this nice feture.

Thank you for your good work.

L.E.

I did installed the new market version and the same no FM icon on status bar.
[Spirit FM] hmarques:
Just installed on Huawei x5 stock 2.3.5.

App asks for root acess, ok;

Then the presentation pops up, I hit "keep ", it says please wait or so... And crashes, with phone reboot :(
[Spirit FM] mikereidis:
If I understand correctly, this is not a bug. It's the lack of a feature on the free app.

The Unlocked app has this feature, although it could bear some improvement.
[Spirit FM] mikereidis:
Thanks for your report. Are you aware of the ongoing Ideos X5/X6 thread here: http://xdaforums.com/showthread.php?p=22378440 ? There's at least one pretty good report about the Oxygen ROM, which makes me think that others may have unreliable FM kernel drivers.

I've been putting a lot of effort into these devices for the past few weeks (besides the initial week or 2 of work). And yet unfortunately some people on some ROMs have problems and others seem OK. And making changes to the code just seems to change who has problems, and which problems. LOL. ;)

I don't have one of these devices, and I'm not sure I ever will, so I'm not sure how much effort I can put in and when. For now at least I have to get back to the much more popular devices, such as Motorola Droid's and HTC Desire's.

Maybe, hopefully, some ROM dev or interested person will be able to explore these issues and help us all out.
[Spirit FM] xmguy:
MIKE, Do you know if the Droid Razr or Razr Maxx on verizon supports Spirit/FM Radio? I know the system architecture is similar to the Bionic. I may be switching to the Razr or Razr Maxx. I've read some threads on XDA saying it doesn't support it. But do you know if the FMradioservice.apk is present or can be added for support as was done with the Droid 2?