Spirit1, Spirit2 Real FM Radio General Thread

Search This thread

mikereidis

Inactive Recognized Developer
Jan 28, 2011
7,823
4,146
Ottawa/Gatineau, Canada

For future reference about this common radio-iris-transport problem, I copied my post from here: http://xdaforums.com/showpost.php?p=55472430&postcount=429

Re: FM drivers:

I see relevant commit messages here: https://github.com/CyanogenMod/android_kernel_htc_msm8974/tree/cm-11.0/drivers/media/radio


I'm guessing that this m8_defconfig file is not used: https://github.com/CyanogenMod/android_kernel_htc_msm8974/blob/cm-11.0/arch/arm/configs/m8_defconfig

Because it specifies a module for radio-iris-transport. But it shows the important requirements without the committed fixes:

Code:
CONFIG_MODULES=y
CONFIG_RADIO_IRIS=y
CONFIG_RADIO_IRIS_TRANSPORT=m
 

KoscheiTheDeathless

Senior Member
Sep 2, 2013
91
18
I'm not crazy about the new update to Spirit xmit. It has to be force closed to turn off, for one, which I can't imagine is expected behavior. My main gripe is the turning off headphone output bit, though. I prefer the old way, as i like to just turn on xmit with earbuds in, then take them out and be at the exact same spot in the song. The fact that it kills earbud output without pausing means it's skipping part of the song.

Both are just minor niggles, and I can (and have) just go back to xmit 1, but I feel like it at least bears mentioning.
 

mikereidis

Inactive Recognized Developer
Jan 28, 2011
7,823
4,146
Ottawa/Gatineau, Canada
I'm not crazy about the new update to Spirit xmit. It has to be force closed to turn off, for one, which I can't imagine is expected behavior.

No it's not. I'm not noticing this on my Z or Z1, both with stock rooted Kitkat.

What device and ROM/version ?


My main gripe is the turning off headphone output bit, though. I prefer the old way, as i like to just turn on xmit with earbuds in, then take them out and be at the exact same spot in the song. The fact that it kills earbud output without pausing means it's skipping part of the song.

Both are just minor niggles, and I can (and have) just go back to xmit 1, but I feel like it at least bears mentioning.

I'm always happy to get feedback. If it makes sense, I'll make things configurable.

I left wired headset audio on for version 1, for testing as much as anything. But some people have preferred it be off, and that worked better for me too, so the only audio would come from the receiver. Best transmit results come from maximised volume, and that can be annoying coming out of an earphone.


I'm not sure what you mean about taking the earbuds out; out of your ear or unplugging them ? And I don't understand why it would be skipping part of the song.
 

Kess78

Senior Member
Oct 3, 2010
168
22
A little trick to increase the volume for Spirit transmit when it's already at the maximum : Go to Settings > Sound > Sound effect, and enable dynamic normaliser. All your songs will then have the same volume which is usually higher than the default maximum volume.

Is it possible that the PS shows the title of the song and the album ? Many car sysstems doesn't have RT and I don't find having just the song duration to be very usefull... Maybe it's not possible because you have to make it scrollable...
 

mikereidis

Inactive Recognized Developer
Jan 28, 2011
7,823
4,146
Ottawa/Gatineau, Canada
A little trick to increase the volume for Spirit transmit when it's already at the maximum : Go to Settings > Sound > Sound effect, and enable dynamic normaliser. All your songs will then have the same volume which is usually higher than the default maximum volume.

That's exactly what TV & Radio stations, and CD producers do as part of the "Loudness Wars".

So EQ is applied then... I haven't even tested that....


Is it possible that the PS shows the title of the song and the album ? Many car sysstems doesn't have RT and I don't find having just the song duration to be very usefull... Maybe it's not possible because you have to make it scrollable...

Anything is possible. :)

Here in North America, the most common use for PS is scrolled RT, although it's SUPPOSED to be non-distracting for car drivers according to the RBDS spec. My Prius only shows info when car is stopped.

The Qualcomm chip and the API even support scrolling, so it shouldn't be very hard.

But for now I'm back to Spirit2; there's a lot of work to do for Android L, which seems imminent.
 

mikereidis

Inactive Recognized Developer
Jan 28, 2011
7,823
4,146
Ottawa/Gatineau, Canada
Android L / 5.0 / LMP:

I've started the work on Spirit2 to deal with the imminent Android L release.

Access to the FM device and audio drivers will have to be done from a daemon process running with SU/root privilege.

The Spirit2 code was setup to do these things from the app process, using chmod to change device permissions. But this doesn't work with the more secure SELinux setup.

FM device daemon looks good, and will help me remove a few dead layers devoted to the now "old" (especially on Z2 and maybe Z3+) Sony/STE proposed Android FM API.

Audio, OTOH could be tricky. A daemon doesn't have easy access to Android APIs for sound output.

I'm considering a new approach that reads from the "microphone" as far as Android knows. (But under the cover is secretly switched to an FM input). This might actually help to resolve Google Now problems and GT-I9000 chipmunk issues.
 
  • Like
Reactions: Trinition

mikereidis

Inactive Recognized Developer
Jan 28, 2011
7,823
4,146
Ottawa/Gatineau, Canada
Android One kernel source for the Mediatek devices is released and has a lot of code for various Mediatek chips. FM drivers for Mediatek are here: https://android.googlesource.com/kernel/msm/+/android-4.4.4_r3/drivers/misc/mediatek/fmradio/

I still have no plans at this time to support Mediatek, simply because I don't think it's an efficient use of my time; I might make literally a few extra sales and at the same time make millions of Chinese "non-customers" happy, and sending me 10+ times as many debug logs, LOL. And I'd need many devices and a few years to support properly anyway.

Then again, they might just run the Google FM app.

I haven't seen the Google FM app yet. It might work ONLY on the Android One Mediatek devices. It might be open sourced, or maybe it won't be, like GMail, Play, etc.

It's interesting because this would be the first Google Android FM app. But I think it will be limited to Android One in a few countries, just like SDCard, dual SIM and removable batteries.

Hmm, since an SDCard is needed to "download content" and since some people may not buy one, or may have limited space, it seems to me that the FM app would be even more important as a source of music.
 
Last edited:

Cookie Ninja

Senior Member
Jan 21, 2010
2,043
700
Seriously doubt Google making FM player on One devices open-source. These are mediatek based, has lot of hackability/better use potential by the industrious hacker community in India / Asia, which Google DOES NOT WANT!

Dead Cookies leave no trails...
 

mikereidis

Inactive Recognized Developer
Jan 28, 2011
7,823
4,146
Ottawa/Gatineau, Canada
Seriously doubt Google making FM player on One devices open-source. These are mediatek based, has lot of hackability/better use potential by the industrious hacker community in India / Asia, which Google DOES NOT WANT!

Android isn't like many other open source projects. Google works on it secretly, then one day, unannounced until the last minute, they "throw it over the wall".

Except for "AOSP", it seems rare for Google to pre-announce whether or not they will release source code for things. I don't know if they have said if they will release "Android One", and same for Android Wear and Google Glass.

Kernel source is of course covered by GPL, so we know Google will release that. But we never know if Google might start using binary blobs, as NVidia has for PC Linux, without any court challenges.

So we don't know if "Google FM" will be closed source like other Google apps, or open like AOSP apps. It may even be a closed source Mediatek FM app, or at least derived from the Mediatek app.

I see various FM kernel drivers here: https://android.googlesource.com/kernel/mediatek/+/android-4.4.4_r3/drivers/misc/mediatek/fmradio/

I'll note that the now released Android One kernel with Mediatek drivers has code for many more chipsets than just the one used in Android One right now. Hopefully this is the start of new GPL co-operation from Mediatek. (Though I still have little incentive to support Mediatek.)

The current Google/Mediatek FM app may only have code for Mediatek chips at this time, and might even be tightly bound to their chips, just like the Qualcomm FM app we see on some CM ROMs now.


I couldn't find an Anbdroid One ROM dump anywhere yesterday. If anyone sees one, please let me know. I'm also interested in a video with a good look at the FM app. I don't want to waste a lot of time watching videos that may only have a brief glance.
 

mikereidis

Inactive Recognized Developer
Jan 28, 2011
7,823
4,146
Ottawa/Gatineau, Canada
Spirit2 0920 HIGHLY EXPERIMENTAL Audio mods, in preparation for Android L: http://d-h.st/0z9

Also available via Play: https://play.google.com/store/apps/details?id=fm.a2d.s2 for those signed up as beta group members: https://play.google.com/apps/testing/fm.a2d.s2

May be glitchy on HTC OneXL, Xperia Z1 and ROMs I haven't tested with (mostly CM11). Xperia Z2 probably stock only.

The method to read digital audio data from the FM chip has a major change. 0912 and earlier use low level ALSA PCM functions to get the digitized audio.

This has problems when the Android audio system is not aware a digital input is being used, and eg Google Now hotword detection can cause problems. It also seems to be broken by the security likely in at least some Android L ROMs, if not all.

This new 0920 Hi-Xperimental release uses the standard Android APIs to read from the microphone input. Then Spirit sneaks underneath and switches the input from microphone to FM. This seems to be working pretty good, though some phones can have strange audio effects sometimes. Sometimes pressing Pause/Play or rebooting will fix.

Other positive effects, besides mic interference avoidance and Android L support may include:

- Reduction of audio glitching.
- Reduction of CPU/power usage.
- Faster audio switching.
- Less dependence on SU commands.


These mods alone won't guarantee Android L compatibility.

At a minimum the low level tuner code needs to become a root daemon and shed the shackles of the now clearly dead STEricsson ancient proposed and dead Android FM API on which Spirit2 was built. This will be much cleaner. faster and more efficient when done. I've prototyped it and might need a week to fix it up.
 
Last edited:
G

GuestK00114

Guest
Spirit2 0920 HIGHLY EXPERIMENTAL Audio mods, in preparation for Android L: http://d-h.st/0z9

...deleted...to keep quote neat ....

- Reduction of audio glitching.
- Reduction of CPU/power usage.
- Faster audio switching.
- Less dependence on SU commands.


These mods alone won't guarantee Android L compatibility.

At a minimum the low level tuner code needs to become a root daemon and shed the shackles of the now clearly dead STEricsson ancient proposed and dead Android FM API on which Spirit2 was built. This will be much cleaner. faster and more efficient when done. I've prototyped it and might need a week to fix it up.

Mike,
just downloaded, will test when Canada ist asleep but as for now, that Europe is awake, have to chop wood at first.
 

MrSteve555

Senior Member
Nov 30, 2013
1,028
2,010
Hi Mike,
I'm trying to get native FM radio support on huashan CM11(Xperia SP), but after building, I can use the radio app, but there is absolutely no reception.
I can only get some crackling sounds, that get louder on certain frequencies.
I'm getting the same problem on Spirit 2 - I diagnosed this a bit and found out that the antenna "layout" is weird on Xperia SP. Internal uses headphone cord to recieve the FM waves, and I think the External uses the internal antenna. It's inverted and I have absolutely no idea how to fix it.
But here comes my real question:
Is there any way to switch the antennas with a command/BoardConfig flag/hack/anything? I'd love to get your app and native CM app to work ;)
 

j1miroquai

Senior Member
Apr 15, 2011
60
13
Hi Mike.

I bought both your apps but unfortunately they don't work since I'm on Mahdi rom 4.4.4.
Of course its not your fault. I just have to ask. Is there any chance at all the app will work in the future on aosp roms? I own a lg g2 d802
 
  • Like
Reactions: mikereidis
G

GuestK00114

Guest
My chainsaw is dull now...

Mike,
just downloaded, will test when Canada ist asleep but as for now, that Europe is awake, have to chop wood at first.

... but FM radio still works sharp as a razor's edge.

:D

Tested the experimental release 2014/09/20 on my I9000 running CM11 nightly release as of 2014/09/19.

Volume control now works on lockscreen, yay!
Speaker mode works, volume is more than sufficient.

FM over bluetooth did not test.

I receive more FM channels than ever. The amount of station storage places is not enough as for todays reception possibilities!
I wonder if you did some magic on the tuner.

When receiving a call audio is properly muted and continues after call has ended.
This is not dependent on who ends the call.

When making a call its all the same.

When overriding FM with another app that needs audio, FM is properly muted but does not continue after app is closed.
You have to restart FM.

Please aks for any other checks i can do with my hardware. I would be glad if it helps.
Spirit is what it says :good:: Inspired.
 

mikereidis

Inactive Recognized Developer
Jan 28, 2011
7,823
4,146
Ottawa/Gatineau, Canada
Hi Mike.

I bought both your apps but unfortunately they don't work since I'm on Mahdi rom 4.4.4.
Of course its not your fault. I just have to ask. Is there any chance at all the app will work in the future on aosp roms? I own a lg g2 d802

Hi, Thanks for your support. :)

Absolutely, I'm happily running the Vanir ROM with no problems on my Sprint LS980 variant of the LG G2.

At this point it's up to the Mahdi ROM dev(s) to decide if they want working FM support.

At one point, Spirit worked on Mahdi. Then he switched to a Nexus derived kernel to fix audio problems. Sadly the Nexus kernel audio driver did not have FM support.

I spent many hours developing a patch for the Mahdi kernel. It worked fine and I posted the patches and kernels here and on the Mahdi thread, with the hope the Mahdi dev would incorporate. It should take less than 5 minutes to do IMO.

But I guess he declined. There's nothing I can do about that; I can't force other people to do what I ask. And I can't get bogged down in creating and maintaining kernels on an ongoing basis. I have more than enough to do with my apps alone, with all the phones and ROMs I support, ongoing fixes, and major updates needed for Android L (and most Android releases really.)

I then found that the Vanir ROM already had the stuff needed in the audio driver for FM. So I've been happily running Vanir and all it's OTA updates. I don't use my G2 as a real phone so I have no idea how good it is as a "daily driver" ROM.


I'd recommend that you use kernels that have FM friendly audio drivers. I'm not sure which might at this time; I can only say Vanir works fine. CM11 used to work fine also, and may still do so, but I guess a lot of people didn't like that it required old bootloaders; I'm not sure if that is still true.

Beyond that, please feel free to "bug" kernel or ROM devs nicely for FM compatible audio drivers, more so perhaps if you've made any donations to their cause.
 
Last edited:
  • Like
Reactions: j1miroquai

mikereidis

Inactive Recognized Developer
Jan 28, 2011
7,823
4,146
Ottawa/Gatineau, Canada
Hi Mike,
I'm trying to get native FM radio support on huashan CM11(Xperia SP), but after building, I can use the radio app, but there is absolutely no reception.
I can only get some crackling sounds, that get louder on certain frequencies.
I'm getting the same problem on Spirit 2 - I diagnosed this a bit and found out that the antenna "layout" is weird on Xperia SP. Internal uses headphone cord to recieve the FM waves, and I think the External uses the internal antenna. It's inverted and I have absolutely no idea how to fix it.
But here comes my real question:
Is there any way to switch the antennas with a command/BoardConfig flag/hack/anything? I'd love to get your app and native CM app to work ;)

Spirit1 and Spirit2 both handle this automatically, as long as "ro.product.device" starts with (case independent) "C53", "M35" or "HAUSHAN" (for SP; there are others, see my C code at the end.)

Spirit1 can even be explicitly set, using Debug-> QCom Antenna.

Xperia SP requires "External". Most other Sony's require "Internal" and these are the ones that Spirit Transmit works on.

Pretty much all other Qualcomm chip based devices need "External", so the SP is more non-Sony "normal".

I have not found a single device that can use both; External or Internal refer to one of the two FM antenna pins on the chip, and in all cases I've seen, only one is connected to the wired headset, the other always seems to be grounded/disabled.


C code I use:

Code:
     if (! strncasecmp (prop_get ("ro.product.manufacturer"), "SONY", 4)) {
      if (! strncasecmp (prop_get ("ro.product.device"), "C2",    2) || ! strncasecmp (prop_get ("ro.product.device"), "S39",     3) || ! strncasecmp (prop_get ("ro.product.device"), "C19", 3) ||
          ! strncasecmp (prop_get ("ro.product.device"), "C53",   3) || ! strncasecmp (prop_get ("ro.product.device"), "M35",     3) || //! strncasecmp (prop_get ("ro.product.device"), "C19", 3) ||
          ! strncasecmp (prop_get ("ro.product.device"), "NICKI", 5) || ! strncasecmp (prop_get ("ro.product.device"), "TAOSHAN", 7) || ! strncasecmp (prop_get ("ro.product.device"), "HUASHAN", 7)
        )
        v4l_antenna = 2;
      else
        v4l_antenna = 3;
    }

    if (v4l_antenna >= 2) {
      ret = chip_ctrl_set (V4L2_CID_PRIVATE_IRIS_ANTENNA, v4l_antenna - 2);                     // 0 = External/headset antenna for OneS/XL/Evo 4G/All others, 1 = internal for Xperia T - Z1
     logd ("chip_pwr_on PRIVATE_IRIS_ANTENNA ret: %d  v4l_antenna: %d", ret, v4l_antenna);
    }
 
Last edited:

MrSteve555

Senior Member
Nov 30, 2013
1,028
2,010
Spirit1 and Spirit2 both handle this automatically, as long as "ro.product.device" starts with (case independent) "C53", "M35" or "HAUSHAN" (for SP; there are others, see my C code at the end.)

Spirit1 can even be explicitly set, using Debug-> QCom Antenna.

Xperia SP requires "External". Most other Sony's require "Internal" and these are the ones that Spirit Transmit works on.

Pretty much all other Qualcomm chip based devices need "External", so the SP is more non-Sony "normal".

I have not found a single device that can use both; External or Internal refer to one of the two FM antenna pins on the chip, and in all cases I've seen, only one is connected to the wired headset, the other always seems to be grounded/disabled.


C code I use:

Code:
     if (! strncasecmp (prop_get ("ro.product.manufacturer"), "SONY", 4)) {
      if (! strncasecmp (prop_get ("ro.product.device"), "C2",    2) || ! strncasecmp (prop_get ("ro.product.device"), "S39",     3) || ! strncasecmp (prop_get ("ro.product.device"), "C19", 3) ||
          ! strncasecmp (prop_get ("ro.product.device"), "C53",   3) || ! strncasecmp (prop_get ("ro.product.device"), "M35",     3) || //! strncasecmp (prop_get ("ro.product.device"), "C19", 3) ||
          ! strncasecmp (prop_get ("ro.product.device"), "NICKI", 5) || ! strncasecmp (prop_get ("ro.product.device"), "TAOSHAN", 7) || ! strncasecmp (prop_get ("ro.product.device"), "HUASHAN", 7)
        )
        v4l_antenna = 2;
      else
        v4l_antenna = 3;
    }

    if (v4l_antenna >= 2) {
      ret = chip_ctrl_set (V4L2_CID_PRIVATE_IRIS_ANTENNA, v4l_antenna - 2);                     // 0 = External/headset antenna for OneS/XL/Evo 4G/All others, 1 = internal for Xperia T - Z1
     logd ("chip_pwr_on PRIVATE_IRIS_ANTENNA ret: %d  v4l_antenna: %d", ret, v4l_antenna);
    }
Hmm,
Maybe it wasn't working from day 0 or something has changed recently, because right now External is the one that doesn't work, and Internal works perfectly fine.
And nice to know that actually the name External/Internal don't refer to headphones/no headphones. I'm a complete newbie into this, so forigve my lack of knowledge.
 

mikereidis

Inactive Recognized Developer
Jan 28, 2011
7,823
4,146
Ottawa/Gatineau, Canada
Mike,
just downloaded, will test when Canada ist asleep but as for now, that Europe is awake, have to chop wood at first.

I'm roughly on "Hawaii time", or up from about 19:00 - 11:00 GMT. :)


... but FM radio still works sharp as a razor's edge.

:D

Tested the experimental release 2014/09/20 on my I9000 running CM11 nightly release as of 2014/09/19.

Volume control now works on lockscreen, yay!
Speaker mode works, volume is more than sufficient.

FM over bluetooth did not test.

I receive more FM channels than ever. The amount of station storage places is not enough as for todays reception possibilities!
I wonder if you did some magic on the tuner.

When receiving a call audio is properly muted and continues after call has ended.
This is not dependent on who ends the call.

When making a call its all the same.

When overriding FM with another app that needs audio, FM is properly muted but does not continue after app is closed.
You have to restart FM.

Please aks for any other checks i can do with my hardware. I would be glad if it helps.
Spirit is what it says :good:: Inspired.

Great ! I definitely appreciate testing around phone calls; this is one of the more common issues and I don't have the resources to buy 20 SIMs and do a lot of phone call testing myself.

An issue to watch for on GT-I9000 is the "chipmunk" problem, where audio frequencies are doubled. This happens after an app (including Google Now) uses the microphone in mono mode. The audio driver gets stuck in mono and can't be switched back to stereo. A few people report that they ALWAYS get audio frequency doubling, even after a fresh boot. I think they must have some app that starts the microphone, even if only briefly at startup. Google Now hotword detection needs to be disabled lately to avoid this.

I'm actually pleasantly surprised that I got GT-I9000 working as well as I did. I was almost sure I'd have to leave it behind for Android L, due to the mono only microphone issue. (But I'm not sure CM12 or any L ROM will ever be built or work well on such a "classic" phone.)

I rarely touch tuner code any more and haven't done so for the Silicon Labs tuner lately. Sometime people say reception got better, or worse, and I just say that nothing was changed. Sometimes people mistake audio quality issues for tuner reception issues.

BUT, I did recently amplify the sound volume for GT-I9000, so maybe that's what you are noticing.


When a "temporary loss of audio focus" happens, such as for an audio notification, Android audio apps are supposed to pause and restart audio, or lower and re-raise volume.

When a "permanent loss of audio focus" happens, such as when a music app starts, Android audio apps are supposed to stop "semi-permanently", which means permanently, unless the user restarts it of course.

Spirit follows these rules for Android audio apps. Of course FM radio has the added issue of the running tuner. I COULD make Spirit continue to run the tuner with audio paused until explicitly turned off.

But all other stock and non-stock FM radio apps turn the tuner off completely in this scenario, so Spirit does the same. Most people want FM turned off completely when starting another music app. It's easy enough to restart for those who want that.
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 497
    Spirit1 and Spirit2 are real, tuned, over-the-air FM radio apps for Android. They do not require Internet access.

    Android 6+ Marshmallow Speaker mode and HTC One M8/Qualcomm startup problems: http://xdaforums.com/showpost.php?p=64465957&postcount=9434

    Dec 2, 2015: I'm going to close this thread for now at least, because sadly, too many "non customers" are coming here asking for support for paid versions and I've become very tired of it. Customers please email me mikereidis@gmail.com for support. Thanks !

    Dec 2, 2015: Spirit apps now available via Paypal through the new Alpha level Official XDA App: http://xdaforums.com/showpost.php?p=64109123&postcount=9431

    Spirit2 2015_03_25_lollipop & KitKat slow rollout: http://xdaforums.com/showthread.php?p=59681989#post59681989

    Mar 18/19, 2015: New Spirit2 release for Lollipop+: http://xdaforums.com/showthread.php?t=1059296&page=904#post59544280

    Feb 21, 2015: Spirit's 4th birthday, Spirit2 analog mode & other New features: http://xdaforums.com/showthread.php?p=58992351#post58992351

    GOOGLE BAN on the Spirit apps (SELinux, lifted). :( http://xdaforums.com/showpost.php?p=59810554&postcount=9046

    DAMMIT Google ! :( DAMMIT new EU VAT policies ! :( : http://xdaforums.com/showpost.php?p=58184929&postcount=8824

    LG G3 official support ?: http://xdaforums.com/showpost.php?p=57367265&postcount=8710

    Spirit2 Lollipop HTC One M7 & M8 GPE with root: http://xdaforums.com/showthread.php?t=1059296&page=872#post57367616

    Spirit2 Open/Free now on Play for "buy me a cheap beer" price, and free XDA download: http://xdaforums.com/showpost.php?p=57261604&postcount=8694

    Spirit1 Light resurrected on Play for "buy me a coffee" price, and free XDA download: http://xdaforums.com/showpost.php?p=57261804&postcount=8695

    Spirit2 Beta releases on Play for customers, updated sign up info: http://xdaforums.com/showpost.php?p=57079402&postcount=795

    Spirit2 11_24/11_25 pre-mature Lollipop re-design release bugs on some ROMs prompt re-org of Spirit2 variants: http://xdaforums.com/showpost.php?p=57057763&postcount=8664

    Spirit2 Free: Open Source Real FM Radio for AOSP & Root: http://xdaforums.com/apps/spirit-fm/app-spirit2-free-source-real-fm-radio-t2951455

    Spirit2 RC2 beta for Lollipop: November 24 / 141124: http://xdaforums.com/showthread.php?p=57006262

    Spirit2 November 21 (141121): Beta Re-architecture for Android Lollipop 5.0: http://xdaforums.com/showpost.php?p=56930903&postcount=8631

    Spirit2 November 12 (141112): Experimental Re-architecture for Android 5: http://xdaforums.com/showthread.php?t=1059296&page=861

    Spirit2 October 29 (141029): Experimental Re-architecture for Android 5: http://xdaforums.com/showpost.php?p=56376931&postcount=8571

    Nexus 6, 9, Player & Android 5.0: http://xdaforums.com/showthread.php?t=1059296&page=854#post56094758

    Spirit2 October 1 (141001): Extremely Experimental Re-architecture for Android L: http://xdaforums.com/showpost.php?p=55771652&postcount=8499

    Android L: Spirit1 and Spirit2: http://xdaforums.com/showthread.php?p=55733853#post55733853

    Spirit2 0920 HIGHLY EXPERIMENTAL Audio mods, in preparation for Android L: http://xdaforums.com/showpost.php?p=55560963&postcount=8455 APK: http://d-h.st/0z9

    Spirit Transmit v2 0915: ONLY works on ROOTED Sony Xperia T and Z class; NOT Z2: http://xdaforums.com/showthread.php?t=1059296&page=845#post55456171

    Download Experimental
    Spirit2 September 10-12
    : http://xdaforums.com/showpost.php?p=55397310&postcount=8427

    Official Sony Z series support coming: http://xdaforums.com/showthread.php?p=54229607

    LG G2 Mahdi & FM friendly kernels: http://xdaforums.com/showpost.php?p=54067863&postcount=8037

    LG G2 FM friendly kernel patches: http://xdaforums.com/showpost.php?p=54068182&postcount=8038

    Android ONE = Google FM Radio ?? !! http://xdaforums.com/showpost.php?p=53677209&postcount=781

    Spirit2: Hi Mike, I am still enjoying Spirit 1, is there any reason to pay again for Spirit 2? : http://xdaforums.com/showpost.php?p=52304938&postcount=7787

    HTC One M8 Verizon ! :) http://xdaforums.com/showthread.php?p=51904224

    Spirit2 is officially released ! :) New thread for Spirit2: http://xdaforums.com/showthread.php?t=2537861

    The Death of access to stock, unrooted OEM proprietary FM APIs:http://xdaforums.com/showthread.php?p=50954346

    New 30 day refund policy: http://xdaforums.com/showthread.php?p=50889714

    Digital Radio, the "Euro Chip Initiative" and "The Universal Smartphone Radio Project":http://xdaforums.com/showpost.php?p=50416866&postcount=7511

    Permissions problems on recent ROMs: http://xdaforums.com/showthread.php?p=48749760#post48749760

    --------------------
    Spirit name: http://xdaforums.com/showpost.php?p=45326547&postcount=6771

    New phones: Note 3 LTE, HTC One Mini, Xperia Z Ultra & Z1/Honami: http://xdaforums.com/showthread.php?t=1059296&page=673

    Broadcom OEM API for unrooted changes on Android 4.3 HTC One: http://xdaforums.com/showthread.php?p=44953912#post44953912

    Nexus 7 2013: http://xdaforums.com/showthread.php?p=44800402#post44800402

    Meh... Emmis NextRadio app is underwhelming: http://xdaforums.com/showthread.php?p=44669987#post44669987

    BT headsets: RDS PS & station info, pause/play, previous + next with AVRCP 1.3+: http://xdaforums.com/showpost.php?p=44463541&postcount=6619

    HTC One GPE Android 4.3 solution: Use Spirit August 5 or later version: http://xdaforums.com/showpost.php?p=44298000&postcount=6585 apk: http://d-h.st/gWe

    Android 4.3 may break FM on devices using Broadcom FM/combo chips: http://xdaforums.com/showpost.php?p=44233922&postcount=6571

    "Spying" on FM radio usage stats: http://xdaforums.com/showpost.php?p=44018032&postcount=6522

    Effem FM app in some CM ROMs ? : http://xdaforums.com/showthread.php?p=43795132#post43795132

    HTC One GPE + digital audio (Unlocked): http://xdaforums.com/showpost.php?p=43071149&postcount=6332

    HTC One first AOSP/Google support: http://xdaforums.com/showthread.php?p=42922397#post42922397

    HTC One Nexus Experience phone: http://xdaforums.com/showpost.php?p=42060507&postcount=6156

    Galaxy S4 MINI GT-I9190 FM: http://xdaforums.com/showpost.php?p=42061724&postcount=6157

    Galaxy S4 = No OTA FM: "In with a bang, and out with a whimper." http://xdaforums.com/showpost.php?p=40952026&postcount=6001

    Where has all the FM gone ? Gone to streaming, every one ? http://xdaforums.com/showpost.php?p=40952008&postcount=6000

    See Supported Device List in post #2 below.

    Variants:
    • Spirit Free: Basic & Mono. Digital audio on Galaxy S. See post #3.
    • Spirit Two Free Alpha: Digital Audio & other Unlocked features.
    • Spirit Light: (supported but no longer sold.)
    • Spirit Unlocked: RDS, Media Buttons, Lockscreen & much more.

    Spirit is the ONLY fully digital FM app:
    • Bluetooth A2DP headsets in CD quality stereo.
    • Recording in CD quality stereo.
    • External visualizers, equalizers and effects.
    • Internal Wave and FFT visual: 5x8 dB & log2 43 - 22,050 Hz.

    Digital audio support:
    • Rooted HTC One, One XL, One S, Evo 4G LTE, Sony Xperia T.
    • Rooted International non-US Galaxy S, S2, S3, Note, Note2.
    • Most stock Sony 2012-2013 devices.

    Record only support:
    • Stock International Galaxy S2 Jelly-Bean, S3, Note, Note2.


    Download:
    Info:


    News:


    Please purchase Spirit Unlocked for full features, excellent support, and help Android FM.

    Thanks ! :)
    Mike.
    92
    Compatibility

    Edit August 18, 2015: I haven't updated this list since June 29, 2013 largely because FM has been dying on Android devices. Samsung hasn't supported FM on flagships since the International GS3 GT-I9300 and Note2 GT-N7100 and never supported FM on US flagships except for some rare Sprint devices.

    If there is no stock working FM app on your device, chances are close to zero these days, especially on Samsungs.

    The only additions I have made in over 2 years are: Sony Xperia Z2/Z3 or compatible, rooted LG G2 International or Sprint, and rooted devices with Qualcomm FM/combo and audio chips, such as the HTC One M8, Xperia Z1 and similar, and some lesser known devices.


    November 12, 2012 compatibility list with more info on older devices: http://xdaforums.com/showthread.php?t=1059296&page=480


    No FM:

    These devices, and many more, are not physically capable of FM, except as noted:
    • Samsung Galaxy S4/S5/S6/Note3/Note4/Note5 & most US/LTE models of Galaxy S, S2, S3, Note, Note2.
    • All Google Nexus's except Nexus One w/ custom kernel.
    • Motorola Verizon Razr HD & M / Maxx. (Australia variant has FM.)
    • Motorola Verizon Razr I XT890 (JB update disables FM. May 8 worked w/ root, but no audio.)
    • HTC Verizon Droid Incredible 4G LTE.
    Manufacturers:
    • Samsung: 70 %
    • HTC: 23 %
    • Motorola: 4 %
    • Sony: 1.3 %
    • Huawei: 1.0 %
    • LG: 0.8 %

    Devices:

    As of April 7, 2013: 69 devices supported, except as noted.

    Other devices may work, but I can't support them.

    By 2013 popularity: most to least. I own the most popular and can support them much better.

    Samsung (14):
    • Galaxy S2 GT-I9100 / M / T
    • Galaxy S3 GT-I9300
    • Galaxy S GT-I9000 / M / B / 9010
    • Galaxy Note GT-N7000
    • Galaxy S Plus
    • Galaxy Note2 3G GT-N7100
    • Galaxy W / Wonder / GT-I8150 / B
    • Galaxy Cooper GT-S5830 / L / D / B
    • Galaxy S2 GT-I9100G
    • Galaxy Gio GT-S5660 / M
    • Galaxy 5 / Europa / 550 / i5500 / i5503
    • Galaxy SL GT-I9003
    • Galaxy Mini / Dart SGH-T499 / Tass GT-S5570
    • Galaxy Player / S WI-FI

    HTC (30):
    • One Stock, Google Play Edition & AOSP
    • One X LTE (AT&T) / XL / Evo 4G LTE / One S
    • One X International S720e
    • Sensation 4G / XE Z715e
    • Desire HD / Inspire 4G
    • Desire
    • Nexus One (need root & non-stock kernel)
    • One V (Virgin Mobile variant needs root)
    • Desire Z / G2 / Evo Shift 4G (G2 needs root)
    • Desire S
    • Wildfire S A510e / PG762
    • One X+ LTE (AT&T) (Not on custom ROMs)
    • Droid Incredible 2 / S S710E
    • HD2 / Leo / T8585 / T9193
    • Explorer a310e / a310b (No RDS unless rooted)
    • Velocity 4G
    • Evo 4G / Supersonic (2010)
    • Evo Design 4G / Kingdom / Acquire / HeroS
    • Aria / Liberty / Intruder A6366
    • Glacier / T-Mobile myTouch 4G
    • myTouch 4G Slide
    • One X+ 3G (Not on custom ROMs ; disabled pending confirmation)
    • ThunderBolt / Scorpion ADR6400L
    • Wildfire
    • Droid Incredible ADR6300
    • Amaze 4G / Ruby
    • Legend
    • Sensation XL X315e
    • Chacha / Status
    • Desire X (1 confirmation stock un-rooted)
    Motorola (12):
    • Defy A8210 / MB525
    • Droid 4 (need root)
    • Droid Bionic (JB update need root: http://xdaforums.com/showthread.php?t=2256439)
    • Photon 4G MB855
    • Droid X2
    • Droid 3
    • Droid X
    • Milestone 3 XT860 / ME863
    • Pro Plus ME632 / MB632
    • Droid2 A955 CDMA (need root & mono)
    • Atrix 2 MB865
    • Bravo MB520

    Sony (11) (Most only work stock for now):
    • Xperia S / SL LT22i / ii
    • Xperia Acro S LT26w
    • Xperia Ion LT28h / at / i
    • Xperia P LT22i
    • Xperia Sola MT27i
    • Xperia Go ST27a / i
    • Xperia U ST25i
    • Xperia T LT30a / at / p
    • Xperia V LT25i
    • Xperia TX LT29i
    • Xperia Z C6603 / C6602 (no speaker ?). ZL & Tablet Z may work with Audio-> Method = "Qualcomm Intent".

    Huawei (1):
    • Ascend G300 u8815

    LG (2):
    • Optimus One P500
    • Optimus 2X P990 re-enabled on Play & semi-official for AOSP ROMs as of June 29
    35
    This is an early document, for further details see: "Dec 19 Spirit2 design details": http://xdaforums.com/showthread.php?p=35571087

    Next Gen: Spirit2

    After almost 2 years, Spirit FM (Spirit1 or version 1) is "mature". Among over 10,000 paid customers, many have been happy to run Spirit on 2-4 generations of phones.
    From HTC Legends, Desires and Nexus1's running Android 2.1 Eclair, to OneX, Galaxy S, S2, and now S3 & Note2 running Android 4.2 Jellybean.

    Spirit1 was not designed much, it was rapidly built using an open source app as it's base. This enabled a quick implementation on many phones, ROMs, etc.
    A lot of quick hacks has accumulated, and now it's difficult to change or cleanup many sections of code without creating bugs on some phone and ROM combinations.

    It's time to start fresh and design and build Spirit2 "properly".
    I'll create a system to enable new settings/options in a few minutes, instead of an hour or more, editing 5 or 6 different files.
    The code will be much cleaner, efficient and bug free when it doesn't have to support 7 different versions of Android, 200 different phones and 10 different FM APIs.


    Spirit1 Future

    Spirit1 will not disappear. Support will continue, but I can't guarantee I'll be able to make it work on old (3-4 year) phones running Android 4.2 JellyBean, for example.
    No major new functions will likely be added to Spirit1. For example, FM record may remain an experimental test option, but will not be supported.

    I will continue to make and release some minor bug and compatibility fixes; timing & extent to be determined. My focus will be on Spirit2, the future.
    I hope those disappointed will eventually appreciate my decision to focus on the future when they get a new device.

    I expect to cease sales of Spirit1 at some time; maybe in months or maybe years. At present, Google doesn't provide a good way to do this, and still allow
    existing customers to re-download. AFAICT we can only set the price to high values, such as $99.99 or $249. If you ever see such a price on Spirit1 Light,
    or Light & Unlocked, don't be appalled. It just means I wish to stop new sales while keeping existing customers happy.

    In the short term, Spirit1 might even become a testing ground for Spirit2. Before a device is officially supported by Spirit2, it may be enabled on Spirit1.
    Sometimes I get several reports that a new phone works OK. Then after some time, major problems become evident that make me regret calling the device supported,
    especially for rarer devices.


    Spirit2 Plans

    Plans are always subject to change. Gotta be nimble. :)

    Spirit2 will be available on Google Play around January, 2013. Beta versions will be available earlier, linked on a new XDA thread.
    No Light version is planned, but a free version may be. Price should be the same as Spirit1 Unlocked.

    Existing Spirit1 Unlocked customers can upgrade at no cost to Spirit2. Spirit2 isn't about making you pay twice.
    But if you feel generous and appreciative of my support over the last few years, I'd be happy if you made a 2nd purchase.
    Or as some appreciative users have, a 3rd, via Light or an additional tip/donation. :)

    The upgrade path from Light to Spirit1 Unlocked, or to Spirit2, or from Unlocked to Spirit2 is the same. I cancel your original order, even 2 years later, and you get
    a full refund. Then you simply buy the new version. You can email me for special needs, such as needing 2 versions for different phones.
    I cancel any order at any time on request anyway, so this is nothing new.

    Spirit2 will focus on a smaller number of popular phones among custom ROM developers and users. I will only support phones that I own for testing, and those with
    very similar architectures. The 80/20 rule applies here, and focusing on 20% of the phones, for 80% coverage just makes sense.

    If you want to run Spirit2, I recommend popular high end devices, mostly from Samsung and HTC. I'll be happy to make exceptions for other OEMs with popular higher end
    phones, or phones with a similar architecture. For example, LG Optimus G and some Motorola devices have the same S3/S4/+ Qualcomm FM/audio architecture as HTC OneX LTE.


    Spirit2 Design

    Spirit2 design started November, 2012, after a 12 month delay from original plans. :)

    Spirit2 will support digital audio features, such as FM recording, Bluetooth, VU meters and who knows what, possibly including visualizations and audio analysis.
    Phones that are not capable of digital audio features likely won't be supported. Thankfully, the wildly popular GS2 GT-i9100 is now proven to support digital FM audio.

    Unchanged from my original 2011 plan, Spirit will use and support the ST-Ericsson proposed Android FM API, hereafter referred to as "Android FM API", despite it's
    mere "proposed" status. The Android FM API was first proposed over 2 years ago now, and seems to slowly be making it's way into AOSP. It's slow progress,
    and uncertain future, has disappointed me. I hope that Spirit2 will help this FM API gain support from
    phone and FM chip OEMs, as well as other 3rd party app developers.

    Many Sony 2012 phones support this API already, on devices based on ST-Ericsson, Broadcom and Qualcomm FM chips at least. So stock, unrooted Sony devices should be
    well supported, in theory at least. I'm not committing to official Sony support at this time however.
    This API is similar to other "OEM Proprietary FM APIa" that don't need SU/root. But it's not proprietary, it's openly documented & uses open source code.

    Other "OEM Proprietary" APIs will likely not be supported. Spirit2 will retain a focus on custom AOSP type ROMs that are incapable of running stock FM apps.
    Support for different FM chips will be via plugins, exactly as specified for use with the Android FM API.

    Unless and until phone or chip OEMs supply suitable FM chip plugins, Spirit2 will provide them. Sony has at least 3 plugins, but it's not clear if Sony can or would
    allow their free re-distribution for other devices.

    Third party developers will be able to write apps using the open, rich & documented Android FM API.
    They will be able to run as standalone apps, widgets, etc. without Spirit2, on devices such as the Sony's that support this API (or a slight derivative).

    On devices that do not support this API natively, 3rd party apps will be able to call compatible functions in the bottom-half, service portion of Spirit2.
    They won't have to bother with tedious, boring stuff such as configuration, as the top-half, app/GUI portion of Spirit2 can handle that.
    Or they could provide their own configuration mechanisms and do anything that Spirit2 does.

    I hope that custom ROMs will be built using the Android FM API AOSP code, and support FM natively within their audio libraries and frameworks.
    But I can't count on this anytime soon, so Spirit2 will do it's best to emulate functionality that is ideally done in the internals of a ROM.
    This is the current situation with Spirit1 on many custom ROMs and it requires LOTS of effort and can never be perfect.

    "FM Chip control" is just one part of the Android FM API. The other major component is audio routing and control. Audio has been the major challenge of Spirit1.
    The FM chip/API code has changed very little during 2012.

    A device that fully supports the Android FM API makes audio issues quite simple. The app can simply start or stop the audio with easy functions. Complexities like
    volume control, headset cable media buttons, lockscreen controls, and possibly A2DP Bluetooth support can be taken care of by the framework of the ROM.
    Even FM recording should be simple, on devices that support it. Spirit1 supports a simple FM record function, but it only works on devices like GS3 at present.

    But Spirit2 will remain a more or less normal SU/root app, as Spirit1 is. I'm one person & don't have the resources to get involved in building kernels, libraries,
    frameworks and ROMs. So Spirit2 will have components that replicate, as best it can, a proper system service for handling FM and FM related audio.

    It seems to make sense to design & build a plugin mechanism for handling FM audio, similar in concept to the FM chip plugin for the Android FM API.
    The Android FM API chip plugin, a library file such as libfmradio.cg2900.so, is oriented to code at the C/C++/JNI layer of Android/Java.
    The Spirit2 audio system plugin is more likely to be done at the Java level, as there are many Android Java APIs that are required or useful.

    Hypothetically, Spirit2 could run even on officially unsupported phones, if someone has or writes an FM plugin and an audio plugin.
    Many FM chips could be supported, with at least basic features, by a single generic V4L FM plugin. A simple generic audio plugin could be created
    that would rely on configurable "reflected" Java APIs or shell scripts etc. The "real world" however, is messier than this might imply.

    Some portions of Spirit2 will be open sourced. Details to be determined.


    EDIT: Which phones/architectures will Spirit2 support ?

    Tentative, but:

    Galaxy S3/Note2
    Galaxy S2/Note
    OneX International
    OneS/X LTE, Evo 4G LTE & similar S3/S4/+ + WCN3660 + WCD9310. Might include Optimus G, Motorola.
    Any Nexus capable of FM. Nexus 4 ? 10 ?
    Sony 2012's maybe, since they support this API when stock.
    I'm keeping an eye on popularity & compatibility of Motorola Razr I.
    34
    Galaxy S GT-I9000 speaker damage risk:

    EDIT Feb 12, 2014: I still get occasional reports of speaker damage, about 1 every 3-4 months. Nothing can be done I'm afraid... :(

    EDIT May 20, 2013: One person has reported damage with digital audio mode. Virtually everything is different in this mode, so I can't imagine why it would happen. The only audio commonality is the analog outputs feeding into the inputs of the audio chip.

    March 23, 2013: See end of post for a potential digital audio solution. Digital audio is normally an Unlocked exclusive feature, but on Galaxy S it is available for Free users.
    There is a risk of speaker damage on Galaxy S GT-i9000 when running custom ICS or JB ROMs.

    If you've been running Spirit for at least 10-40 hours with no problem, your risk is minimal. I think this is hardware related and about 1-5 % are susceptible. I get about 1 report every 3 weeks now.

    Avoiding use of the speaker or keeping volume low does not help. Risk may increase when using USB cables to PCs or chargers or external amplifiers.

    If you are worried about Galaxy S speaker damage, then DO NOT use Spirit, unless on CM7 or a stock derived ROM. Use GB ROMs with proven safe FM, get a new phone, or just live without FM.

    Unless you are familar with ALSA programming, Ioctls and low level Linux/Android kernel stuff, as well as DC servos in amplifiers, please do not think you have useful technical advice to give about what I should study. I've spent at least 400 hours on this problem, with no analog solution.


    Have Damage ?:
    If you've had GalaxyS speaker damage, and are a BRAVE do it yourselfer, here are some Ebay links for speakers and instructions on replacing them: http://xdaforums.com/showpost.php?p=23014977&postcount=2355 All responsibility for any problems doing this is yours.

    Ringer/Buzzer Speakers are available on Ebay new for $6 shipped, or $8 refurbished shipped from the US to the US.

    I'm very sorry for any problems. I had no idea this problem would happen or go on this long. It's rare that software causes hardware damage.

    If you're angry, or think my dev skills are sub-par, please refer me to the secret documents for FM audio via Galaxy S ALSA controls. There is none. I've read the code for various audio libraries, and the ALSA drivers, many times, and though the March 4th, 2012 attempt seemed a virtual duplicate of the CM7 audio lib, the problem continued.

    If you've been affected, please email me at mikereidis@gmail.com to report.

    Thanks, and sorry for any troubles.


    Hopeful Digital Audio Solution:

    Using digital audio mode likely reduces or eliminates the risk. As of March 23, 2013, it's too early to tell.

    EDIT May 20: One person has reported damage with digital audio mode. Virtually everything is different in this mode, so I can't imagine why it would happen. The only audio commonality is the analog outputs feeding into the inputs of the audio chip.

    On first Spirit startup, or after clearing app data, you are presented with a choice of "Digital" or "Danger". Choose "Digital". If running Unlocked, restart Spirit to enable Visualizations and a record button.

    You can also set Menu-> Settings-> Audio-> Method to "Digital Auto" or "Digital GS1", both near the end of the list.

    If you hear interrupted high frequency "chipmunk" sounds, rebooting may help, at least until the microphone is used (but phone calls OK ?).

    If a reboot doesn't help, you can disable Digital-> Stereo and do Pause / Play. Audio is now mono of course, so you might as well set Audio-> Output Mode (or Channels next release) to "Mono Force".

    More chipmunk info: http://xdaforums.com/showpost.php?p=39383252&postcount=5696

    Battery consumption may be a bit higher using digital. Unlocked uses substantially more CPU & battery when visualization is on screen, and when equalizers, effects and Bluetooth are in use.
    31
    I'm taking a MUCH needed break from Spirit and will restart work on Spirit2 in late October.


    After 2.7 years and over 9,000 hours spent developing, supporting and otherwise dealing with Spirit FM:

    - I need to draw a line in the sand here and take a week off to "detox" from the Internet.

    - Then I need a month for doing taxes and pressing family, household and personal tasks.

    - Then I need at least a few months to explore where Spirit is going with Spirit2 and/or some other FM app related stuff I'm considering.


    So,... given that I endeavour to be as honest and open as I can: I regret that going forward, I'm not going to be able to provide the high level of support
    I've been providing and been struggling to maintain.

    As always, if anyone has purchased Spirit and feel they haven't had sufficient enjoyment: I cancel any order at any time on request.

    For answers to most questions about Spirit, use the search feature on this XDA thread. If you can't find an answer, post, and hopefully some helpful person will answer,
    maybe even me occasionally. :) I previously answered every question on this thread, but I have to let that go now.

    I appreciate if anyone helps anyone else here, but ask that you be nice. I think it's probably better to ignore a poster than respond with an angry "Read the FAQ !".

    If Spirit doesn't work with default settings, maybe alternative settings will work. But this is the exception now. If it doesn't work by default, it probably won't.

    As time goes on, stock and custom ROMs will update/change and something may break in the FM access. I've hypothesized that for custom ROMs, within 3 months as many as 50%
    of ROMs will have a role in some problem with Spirit. If Spirit has 0 or just a few small updates in the next 3 months, I'll be interested to see the result.

    This breakage rate is largely the nature of the fast pace of change in ROMs, but change happens in stock ROMs too. The bluetooth stack has undergone major revisions in
    Android 4.2-4.3. I've dealt with that, and Android 4.3 related issues, so hopefully Spirit will run well on new or recent phones for a while.


    Since I'm looking at other "projects" in the Android FM app area, there's a reasonable chance that Spirit will continue to have related updates. But since I may
    (or may not) be concentrating on stock FM support, improvements may be restricted to stock support. The beta access for Spirit Unlocked and Light may be a way to deal with that.



    ----------------------------------------------------------------
    Sidebar:

    It's been a constant struggle to reverse engineer FM chip/API details as they change from chip to chip, phone to phone, OEM-OEM, Android version, API version, custom ROM, and more.

    Google isn't helping the cause any, nor are many of the phone OEMs, chip OEMs and carriers. Nobody else has been "crazy enough" to try what I'm doing with FM.

    Gee, even the top FM apps from Sony and Samsung don't do most of the digital audio features that Spirit can, even on an ancient GT-I9000 Galaxy S.

    But despite the work and crazy hours I put in, there are still some nasty & effectively unsolvable problems, like audio on Desire HD, a UI that needs serious improvement,
    and annoying things like 87.5 on startup with stock Broadcom API.

    The code for Spirit is a horrible mess, and deserves to be replaced with a (properly) designed Spirit2 or whatever.

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

    I'm not going to be monitoring my usual email address mikereidis@gmail.com as much, and not at all during any Internet "detox" week.

    This email will auto-respond that:

    - Purchase cancel requests (Only !) be sent to spirit.fm.unlocked.cancel@gmail.com, or perhaps to the normal email with "CANCEL"
    spelled out in capitals in the subject. And be patient please, even Google can be glacially slow handling these.

    I may or may not respond to any emails or posts. Sorry, I kinda hate to become "that kind of dev", but this is essential for me, and for Spirit, at this time.

    I appreciate all the appreciation for Spirit, and feel satisfied with the 4.7 out of 5 rating that Spirit Unlocked has on Play, from thousands of people.

    I hate to see that rating drop because I can't provide the same level of support, but I guess that would be fair and should be expected. I'd be more likely to drop a rating if I was the
    customer and there was little or no support for some problem.


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

    So, in the next few months, there is the potential for Spirit to re-continue, as it has for 2.7 years now. Or it may take a new form; remains to be seen.

    It's important for me to be honest and say that, instead of pretending I absolutely will return to Spirit if you can just wait. I refuse to be that kind of sales / business man.

    Business-wise, for Spirit as it exists now, some might see this as "burning a bridge". I see it more as a bridge in urgent need of repair/replacement to prevent loss of life. Need to replace the old wooden bridge with a modern steel structure...


    Thank you everyone for all your support, and see you on "the other side" ! :)