yashsingh1/xdaforums huggingface dataset:
[Spirit FM] patrcost:
no reception on sgs1

The new version doesn't work on my sgs1, with slim bean 1.0 and semaphore.

What also happens is that bluetooth gets activated when starting spirit fm?

I can hear a murmur but the device doesn't find any channels.

I am using the belgian frequencies.

Tried the other settings excluding the galaxy S3 alsa(I read somewhere not to use this one or am I wrong about this?)

It worked before so there must something I'm overlooking...

edit: didn't read post a few places lower, am now trying the devil kernel

edit² : devil does the job, reception seems weaker then before on other roms or is this impossible?

edit³: most important thing I forgot! Thank you for the app!
[Spirit FM] akromatic:
I've paid for the unlocked version on google play and the latest update ruined it for the note. its stuck in speaker mode and i cant get it to play through the headset. how do i roll back to a known working issue while keeping my unlock features?
[Spirit FM] mikereidis:
Great ! :)

Oh, I HAVE to check in. I'm not going away from email or this thread. Will check both at least every 24-48 hours. Just won't be doing much development.

My sales numbers are "pretty good" now and many new customers need help of some sort.
[Spirit FM] mikereidis:
Yeah, semaphore likely doesn't support the FM driver either, or it doesn't enable it by default at least. I didn't try it as I thought it might not work on JB, or at least the Slim Bean ROM.

I've been getting a wide variety of reports that some version or another improved or degraded RF sensitivity. But this happens on different FM chips, and I don't think anybody has been able to say June XX is better while July YY is worse.

In general I don't think I can take credit or blame for any improvement or degradation. I and nobody has been able to confirm this, other than with a long known Motorola issue. If you see this problem, please note RSSI values for a few stations, and if you can check other versions, note the RSSI values there too.

Perhaps it's sunspot or weather related. Lightning and spikes can damage FM chips too.

Recently I had my first case of a broken antenna connection, likely on the circuit board. Happened on my cheapest $80 Galaxy 5 series device, GT-I5500. And this phone was my sensitivity star, doing RDS no problem with no antenna.

Also, in some locations stations go lower power at night and may switch RDS off. I see that locally with most stations between about 1 AM and 6 AM on weekdays.

And the other night, ALL of my phones were showing weak signal and noise. I have no idea where the RF noise was coming from but it's gone now. I hope it wasn't one of the phones doing that.
[Spirit FM] mikereidis:
Sorry about that. Best option in such a case is to email me for help and older versions, preceded with a post here where I may see it more quickly.

With a license file you can also take any Free version, as listed in post 1, and give it Unlocked capabilities.

I and many other devs are hoping that Google comes out with a rollback feature. It's absolutely needed, especially given the ease with which Android apps can be updated. Google maintains ALL of our old releases, so they have what they need to do it.

A dev can't even disable a new release; He has to build a new one with a higher version number.

-----------

Re: the GS2/3/Note speaker issues:

- The previous July 14 Play release had the sticking speaker issue, and it is resolved by re-plugging the wired headset. July 27 resolves this issue on my GS2 and Note, so I'm not sure why you'd see the opposite.

Most people with problems are reporting the latest releases doesn't allow speaker mode, despite it working for me.

I haven't tested a stock Note ROM in the last few days, since I re-loaded it with custom ICS and JB.

I will get to my email after dinner... (Gotta eat SOME time :) )
[Spirit FM] mikereidis:
EDIT: I don't know why but I'm seeing the no speaker mode problem now. (Possibly because running older versions after a reboot fixes the problem.)

EDIT: Turns out this was due to using a Galaxy S wired earphone, with only one media button. After a reboot with the proper white Galaxy S2/Note earphone with 3 media buttons, speaker works fine on CM9 nightly July 26 with Spirit July 27.

For speaker issues on Galaxy S2/Note.

Also applies to S3 with custom ROMs, except CM9 versions later than July 9, CM10 or any ROM derived from these.

Free app versions are available in post 1 from June 15 to present.

The other night I ran tests on my SGS2 running CM9 July 26 nightly. These are my results from June 7 (607) to July 26:

Success 726 723 722 721

No Audio 720

Sticky Speaker 714

Success 712b 712 710 705 630 628 622

No Speaker 618 617 615 613 607

Some people are clearly having different results than I though.

Success = Both speaker and headset seem to work.

No Audio = Neither worked.

Sticky Speaker = Once speaker selected, can't switch to headset until headset is re-plugged.

No Speaker = Headset works and speaker doesn't, unless you remove headset plug.

In other words:

- Up to June 18, the speaker button didn't work.

- Speaker button fixed in June 22.

- July 14 was first Play release in several weeks. Changes were made to resolve audio problems due to the speaker changes, but this resulted in sticky speaker.

- July 21 introduced an apparent fix for sticky speaker. For some people, this may have caused some issues.
[Spirit FM] mikereidis:
Blog & Phones with no FM:

Was asked recently if I do a blog. This thread is my blog, and changelog and general repository of info and tips. XDA or Google search can be useful, even/especially for me.

If a post is long I try to identify the subject in the first line. If you have no interest, skip to next post.

I again had some contact with an interesting organisation that wants to see more FM in mobile devices. I was asked a bunch of questions and here are my main thoughts, which apply more to North America/US than elsewhere:

- Radio broadcast industry has little money compared with the "new economy" industries that seem aligned against it, including Google. IE. Internet portals & services, "big media", electronics/phone manufacturers. So I don't see how radio can win.

- Most phones have an FM or FM/combination chip or SOC in them capable of FM reception. At least half of those are dormant because the manufacturers don't spend the extra 1 cent to 1 dollar or so to enable it and include an app. In some cases cost would be negative due to the need to have an "FM castrated" SKU/variant of a phone.

- The elimination of FM happens most in the US (& Canada now), and on higher end phones. Elimination is by not including an app (eg Motorola or AT&T OneX), or by not enabling, or by disabling hardware needed for FM.
[Spirit FM] mikereidis:
Sony devices & "ST-Ericsson proposed standard Android FM API":

Sony devices & "ST-Ericsson proposed standard Android FM API":

Copied from another thread: http://xdaforums.com/showthread.php?p=29431256#post29431256

Regarding the "seemingly almost dead" "ST-Ericsson proposed standard Android FM API":

Google DID eventually get the servers back up, after taking an IMO ridiculous amount of time for a major world class corporation.

Here are the only comments on the main patch for 2012:

So maybe, just maybe, someday there MIGHT be a standard Android FM API. But given the 1.5-2 years (or 3+ ?) it's gone almost nowhere, the odds don't seem that good to me.

I don't know enough about AOSP to say if there are any FM related changes in Jellybean.

Some of the Sony 2012 phones use ST-Ericsson FM chips now, and they appear to support a variant of the proposed API. The Spirit FM app now supports 10 different APIs, including 5 higher level Java based APIs such as this.

But Sony market-share seems small enough that I am not planning to support it anytime soon, despite it being half documented and related to this potential standard API.

URLs to the proposed API code, as posted by blunden, if anyone is interested:
[Spirit FM] jwhood:
Got a question i bought light ver on market and running dark unicorn 2.5 aokp on htc glacier(mytouch 4g) all works well when i go to turn off it freezes and phone reboots any help for this issue,thanks and great work!!!:)
[Spirit FM] groksteady:
Mike, if an organization is contacting you, ostensibly to contract you or somehow fund development, they may find wider support and funding from NGOs or national overseas development agencies such as USAID. I generally work in developing countries, and radio is a primary and very important source of info. I know one major development agency did a thorough study centered on communication and social media in all of Cambodia's provinces, and the major conclusion was to push Android devices. Moreover, Hillary Clinton was just here for the ASEAN summit and promised $50 million in aid. NGOs are scrambling for a slice.

It could be worth suggesting to those orgs to look into.

sent from a telephonic device
[Spirit FM] mikereidis:
So it freezes and reboots every time when turning off ?

Does Mute/Pause also do this ?

Have you every had Spirit running OK on other ROMs or kernels, even the Free version ?

Do you normally have Bluetooth on, or does Spirit turn Bluetooth on automatically ? If it's running in Bluetooth mode, it would be nice to try UART mode, or vice-versa. Unfortunately many ICS/JB custom ROMs have Bluetooth on all the time (under the covers) so UART mode might not be possible.

If you have ADB installed on a PC, it would be possible to run adb logcat from the PC and try to see what causes the reboot.

Can you send a debug log with Menu-> Email Logs, and after it finishes, press Send ? At least this will give me more info to go on. Do this right after a freeze and reboot.
[Spirit FM] mikereidis:
Thanks for the ideas. There are 2 different "organisations or businesses" who've been in touch with me, and I've been asked not to disclose their names, but it's probably not TOO hard for many people to guess what one of them was.

Anyway, neither of them are really able to secure funding from "overseas". And IMO the amount of funding you need to go up against Google, Apple, Samsung, Motorola, AT&T, etc. etc. is almost unthinkable.

And funding isn't even the issue, it's just that there is more concern about reaping the benefits of jobs etc for "new economy" businesses, rather than favoring (almost subsidizing) the old "buggywhip" radio business.

Gee, I say that and it almost convinces me, LOL.

There was some talk of possible contract work for me, but as I've said before, I'd prefer to have thousands of small bosses / employers than 1 or 2 large ones. But if someone were to throw money at me, and it didn't require too much work or commitment from me (unlikely), I'd be happy to catch it.
[Spirit FM] jwhood:
I will try to get logcat for you,havent tryed pause or anything yet,ill give uart a try and see if that helps,first time i tryed your app out every thing else is fine ill get back too you on this,and yes automaticlly turns bluetooth on
[Spirit FM] Rizaria:
So..how do I actually get this to work anyways?

On an SGS2 in Australia, currently on Ressurection Remix ICS.

I get static no matter what. :o Curious to know if this'll work for me.
[Spirit FM] Scofield81:
Samsung Galaxy W I8150

Hi Mike,

I found this fantastic apk and is working on Samsung Galaxy W I8150.

However I saw some bugs during the tests. If I'm using Spirit FM and receive a call, the apk stops and I start listen the incommig call. This is the expected result.

The problem happen when I stop the call. The Galaxy W I8150 crashed and did a reboot.

If you want I can post some debug info in order to help you.

It is possible add a small icon on status bar when the SPIRIT FM is working?

Thanks
[Spirit FM] LLStarks:
I got a self-built radio-iris-transport.ko to load on the Verizon Galaxy S3.

<4>[ 565.786570] radio_iris_transport: Unknown symbol radio_hci_unregister_dev (err 0)

<4>[ 565.786632] radio_iris_transport: Unknown symbol radio_hci_register_dev (err 0)

<4>[ 565.786693] radio_iris_transport: Unknown symbol radio_hci_recv_frame (err 0)
[Spirit FM] ruffneckZeVo:
I can't find this app on the market can u post a link
[Spirit FM] Pseudonym:
The free version isn't in the market. Only the unlocked and lite version.
[Spirit FM] Spectator_0o:
Unable to get working on Desire HD

I've tried getting this to work on my Desire HD. But I'm only getting the following error:

Error: No FM accessible

SU:1 Fm:BC2 Su:0 Bt:1 Ht:0 Mo:BCU

I have the Method set to qdsp5v2 Plus/ICS, region Australia, BT enabled and earplugs plugged in. Just keep getting the above error.

I have:

ROM: IceColdSandwich - 8.3,AOKP

RADIO12.54.60.25U_26.09.04.11_M2

Kernel: 2.6.35.14-LorDmodUE-9.8.8-ICS-CFS

I've search XDA and Google but haven't been able to find anything to help. Anyway know what I'm doing wrong?

I've tried Spirit FM July 26 & 27 versions but no luck.
[Spirit FM] mikereidis:
Sorry for my delays, but I Really needed the last 48 hours away from the computer and cellphones. As posted at top of post 1:
[Spirit FM] mikereidis:
I don't recall right now which kernels are good on SGS2, but most of the more popular ones support the FM driver.

It's time to build an official Spirit FAQ.

I'm OK with people asking the same questions over and over. But to streamline my work I will quote the FAQ section(s).

----------------------------------------------------------------------------------------------------------------------------------------------------------------

Q: Why doesn't Spirit receive anything ? It starts with no error.

A1: For Samsung Silicon Labs FM chip devices, including the International versions of Galaxy S/S2/S3/Note/Player/etc:

You may need a Samsung Silicon Labs FM chip driver (si470x), and your kernel and/or the ROM kernel may not include it or support it.

To fix this, install a new kernel. If the kernel supports the FM driver, but doesn't load it by default, let me know and I'll try to support automatic loading.

Explanation: These devices contain Broadcom combination chips capable of supporting WiFi, Bluetooth and FM. The FM antenna and audio pins are not connected anywhere useful.

If the Samsung FM driver is not available as /dev/fmradio or /dev/radio0, Spirit attempts to load (insmod) the FM driver from common locations.

If this doesn't work, Spirit will assume the device may support Broadcom FM and attempts to use it.

This will usually appear to succeed, but RSSI signal strength numbers (at top left of app) will likely be 0 or less, or jump around crazily, even when tuned to a known strong station.
[Spirit FM] mikereidis:
Does audio work OK when you set Audio-> Method to "qdsp5v2 Altern" ? Or what method are you using ?

Try setting Debug->Mute kill mediaserver to "Disable". This might cause audio problems, but at least we can try to determine the source of the reboot.

The status bar icon is enabled on the Light and Unlocked versions, but not on Free. I don't expect that to change.
[Spirit FM] mikereidis:
Good.

That's part of our problem now. We need to get at least parts of the Bluetooth / HCI software running for the Qualcomm SOC internal Bluetooth/FM core. That's where the radio_hci_* functions are.

Unlike the AT&T OneX (L), the North American GS3 uses an external Broadcom chip for Bluetooth and WiFi.

So the drivers we need aren't loaded by default. I'm not sure if we can even load the needed Qualcomm drivers if the Broadcom drivers are loaded.

AFAIK, the Linux/Android kernel only supports one HCI provider.
[Spirit FM] mikereidis:
SPH-D710 is not physically capable of FM.

Q: Where can I get Spirit ?

A: The latest Free version is usually linked at the top of post 1: http://xdaforums.com/showpost.php?p=13379669&postcount=1

The Unlocked version is on Google Play: https://play.google.com/store/apps/details?id=com.mikersmicros.fm_unlock

The Light version is on Google Play: https://play.google.com/store/apps/details?id=com.mikersmicros.fm_li

If you can't purchase from Google Play, email me at mikereidis @ gmail.com for an Unlocked Paypal option.
[Spirit FM] gelim:
Hi,

I can see bluetooth is disabled from the GUI (using switchpro widget here and notification bar as a confirmation) when powering down application BUT I notice battery drain curve has a slight constant slope it didn't have previously.

EDIT: the FM part is more likely to still be up, I noticed there's a slight white noise that can be heard from the speaker after stopping the application

regular slope : 1% per hour

after fm closed : 1% each 20min

I'm using Battery snap to monitor battery drain.

EDIT: if I pkill mediaserver white noise stops and battery drain too apparently.

Cheers,
[Spirit FM] XYZ-Moscow:
handsfree - it's wired headphones. sorry for my English.
[Spirit FM] mikereidis:
I've been seriously considering that.

Android app APK files allow anyone to view and modify the XML files that usually define the UI. To a certain extent, a third party without source code can modify the UI. They won't be able to do things like add a draggable frequency control, but they should be able to move buttons and change their appearance. This is "skinning" pretty much.

Two people have asked if they could do this, I've said "Go ahead and please show me the results". So far I haven't seen any results. Having ideas is easy but actually doing the work is harder...

I've considered open sourcing the app itself, and keeping the source for the underlying hardware "driver" in the driver library to myself. But my experiences with those who want to modify the XML files is not promising thus far. If I did open source the app and not the drivers, I think rather than seeing apps using my drivers, I will me more likely to see someone(s) taking my app code, "slapping" the simple API from the CM/MIUI apps on it, and trying to sell it. Or even using my library in their paid app.

But creating and documenting an API for public use is work too. As it is now I'm the only user of the API so I can easily make changes on both sides. Public APIs need to be more stable and documented.

AND, I'm not fond of the idea of creating my own proprietary FM API. Sony/Ericson is working on an Android FM API, and that might be the best model for such an API. But implementing that API is a bunch of work too.

So, this and similar are ideas I'm constantly re-evaluating.
[Spirit FM] mikereidis:
1) Well then I'll build a debug version with a lot more debug messages for you to try. The values you are seeing for RSSI seem wrong; Two of the few you see are, in hexadecimal: 0x90 and 0x9F. That is a clue that the wrong register may be getting read, but I can't imagine how.

I'll try to build this new version later tonight, and include some minor audio tweaks, I AM taking my week off now, but a few minor changes isn't too much work, especially if I don't test it much. Today I got our living room window air-conditioner installed... :)

2) Yes to pay version, perhaps a week after I restart work. One article I read recently indicated that app devs may be making more on ad versions than on pay versions. The "awful thing" though is that I anticipate putting ads over where the RDS RadioText goes, at least some of the time. BUT, I NEED to do whatever I can to create at least a little income to keep this project alive.

3) I haven't seen or heard of the Local feature for seeks/scans on car radios. Interesting... I always favour having config options so that I don't have to make a fixed choice.

As I mentioned in previous post, customisation CAN be done today with the app, but nobody has done so, that I know about. But I could document it and provide an example; Antique radio theme ties into the idea that a REAL FM app is outdated, LOL.
[Spirit FM] mikereidis:
Hi gelim, and thanks for investigating this. Most people here have devices with Broadcom chips so I don't get much feedback about the TI chips.

There is one older post in this thread from someone else who was concerned about battery drain, but since most were more interested in just getting the app working, I didn't look into it much.

When you say "I notice battery drain curve has a slight constant slope it didn't have previously"

do you mean my FM app didn't do this previously ?

Killing mediaserver stops the drain ? Interesting...

One thing weird about the TI chips is that there is an HCI command to power on or off the "FM core" that is not like the normal commands. (There is also a normal command in addition.) But the command to power off the FM core doesn't do anything in my experience, yet my code still uses it. Perhaps there is some way to do this I'm not aware of.

As for the "white noise" with the app off, that is likely related to audio routing code I disabled. I will try re-enabling it for the next version.

One of the interesting things about the TI chip, on my Legend at least, is that if WiFi is on, and BT is turned off, the FM will keep on playing, but the app can't control the FM anymore. This is in effect, a lower power mode. But as soon as WiFi is turned off, so does the FM audio.

So instead of killing the mediaserver, you might try turning WiFi off and see if that also kills the white noise and power consumption.

I'll try to figure out what is going on...
[Spirit FM] Ivanovic:
mikereidis big thanks for your efforts! Its nice to have RDS support!

Is the application going to work in the htc desire without any mods? Or does it require any tricks after installing the apk and copying the ssd to /system/bin ?
[Spirit FM] welard:
can anyone confirm if there is a fix, or possible fix for bluetooth audio headset for (winmo) blackstone with TI chipset brf6350

theres no audio output from bluetooth headset when making a call

thanks a bunch!!
[Spirit FM] Victorino86:
AFAIK for a working FM Radio you need a wired headset that works like an antenna for the radio...

I think just a few phones over the last ten years came out with the capability to scan FM without a wire jacked-in.
[Spirit FM] magnus48:
I'm trying to edit the apk whith apktool to make some graphic's work but I can't recompile it?:confused:
[Spirit FM] gelim:
No, I meant for "previously" when the app is not started.

I tend to never use WiFi. So I just tested after closing the app to turn on & off WiFi but it doesn't have any effects on the white noise.

I might try when I'll have more time to play with hcitool...
[Spirit FM] mikereidis:
Sorry, I've been away for several days and my email is backed up by 6 days.

This is the minor v2.0.19 release:

http://www.mediafire.com/file/72noebovkvo0hh1/FMRadio_v2019.zip

This is only recommended for those who have trouble with earlier releases, or who feel adventurous. V2.0.17 is the most "stable" recent release.

This release will hopefully fix speaker/headset switching on some devices that have some ROM support for FM audio switching. (More ROMs that I originally imagined I think, including several derived from stock or CM etc.)

If you created any customisations under /sdcard/sprt/opt, you can go back to defaults by either deleting or renaming the /sdcard/sprt or /sdcard/sprt/opt directories.

Also in this release is the enabling of several debug messages for "adb logcat". There are 4 categories and with all enabled while tuned to a station with regularly updating RDS data, the logs produced are around 1.2 Megabytes per minute.

To disable all these new logs and reduce the load on the phone, this can be done:

adb shell mkdir /sdcard/sprt

adb shell mkdir /sdcard/sprt/opt

adb shell mkdir /sdcard/sprt/opt/dbg

adb shell touch /sdcard/sprt/opt/dbg/custom

adb shell "echo 0 > /sdcard/sprt/opt/dbg/hci"

adb shell "echo 0 > /sdcard/sprt/opt/dbg/reg"

adb shell "echo 0 > /sdcard/sprt/opt/dbg/evt"

adb shell "echo 0 > /sdcard/sprt/opt/dbg/seek"
[Spirit FM] mikereidis:
Sorry for my delay...

If you mean an HTC desire with a stock ROM, the answer is likely no. Most stock ROMs use the proprietary Broadcom BT stack that doesn't support HCI access. If a device supports the full Bluez BT stack it will likely work.

BUT, a stock ROM modified to have SU/Root capability should work with the UART modes, when BT is off.

The ssd utility is just an experimental way to enable audio on some devices. As always, quickest/simplest way to find out if the app works on your device is just to try it.