Spirit1, Spirit2 Real FM Radio General Thread

Search This thread

Victorino86

Senior Member
Mar 25, 2011
60
1
Great work

Yes, install the update. It should fix the issue (I hope). Now when radio power goes of the volume buttons should revert to the default (likely ringer volume).

I WAS talking about those 3 (or 4) Androd system volume controls. The ringer volume there SHOULD have worked around this problem.

I'm on the 2.0.8 (from the market), the volume issue is solved, sweet!

RDS is working, just wondering what are the letters i get below the 4 bars.
Also i see there is already TPY on the right.


Not sure how the scan should work :p


BTW, keep going best FM app! Gonna buy the donate version for sure.
 

cos68

Senior Member
Dec 21, 2010
76
16
Aalborg
PTY and RT are there already. Some stations don't transmit PTY (or RT or whatever they please). RT is the longest data type at 64 bytes, and the code needs to see the same string twice to consider it valid and display it. If you have a high RDS error rate, or the station changes RT too often, or their encoder is funky, you may never see RT.


RDS locations in app:

PI : At left below RSSI (signal strenth bars) and above frequency down button.
PT: At same height as PI but on right side below where the "Stereo" indicator was in prior releases.
PS: Top middle between RSSI and "Stereo" indicator,
RT: 3 lines below frequency and above preset section.

Sounds great. I haven't seen anything but the PS information in your application, even though I know that more stations in my area send both RT and PT but I guess I will have to test it outside to see if I can get a better signal then.
Thanks for your answer!
 

MonacoHias

Senior Member
Dec 1, 2007
243
29
...

But due to IMO the virtually insurmountable technical challenges of making FM recording work, I am unlikely to add it anytime soon. Even if I got it working on one or some phones with much work, many other phones would likely not have this feature.


But I've read MANY threads where this subject was brought up and considered a useful feature. Many people, especially the less technical, still listen to airwave radio, instead of MP3/audio players or streaming stations.

If they get a phone call, they may want to pause the music or talk show etc. If they want to play a favourite song or show for a friend, they could do so. They many never download a song and may not know how, nor want to learn. A simple record button would be wonderful for them, especially if it could break up the songs and automatically title them from RDS data.
...
My greatest desire right now is to support as many popular devices as possible, especially those running stock ROMs (the majority). But features like RDS could put my app ahead of stock apps like the one from HTC.

You are probably right. Especially with the last one: best and (for now) unique FM RDS Radio. I wished I could push your app on the (German) market ...

If you want to offer a paid version as well - differences between free -> paid could be:
- store more than xx stations
- the desired recording functionality
- skins / skinning
- streaming radio :rolleyes: -> one app for all radio-listening
- something more in my mind ...

Anyway, I hope you keep a well featured free version as well. ;)
 
Last edited:

mikereidis

Inactive Recognized Developer
Jan 28, 2011
7,823
4,146
Ottawa/Gatineau, Canada
I'm on the 2.0.8 (from the market), the volume issue is solved, sweet!

RDS is working, just wondering what are the letters i get below the 4 bars.
Also i see there is already TPY on the right.


Not sure how the scan should work :p


BTW, keep going best FM app! Gonna buy the donate version for sure.


Great ! :)

3 or 4 letters under signal bars should be a US callsign, starting with W or K I should disable that for regions outside North America and just show the number. There's also a few databases on the Internet I might hook into.


Long press (hold for 1/2 second or more) the frequency up/down buttons to seek to the next strong station. As I say, broken on Broadcom in v2.0.8 and should be fixed in next.
 

mikereidis

Inactive Recognized Developer
Jan 28, 2011
7,823
4,146
Ottawa/Gatineau, Canada
differences between free -> paid could be:
- store more than xx stations
- the desired recording functionality
- skins / skinning
- streaming radio :rolleyes: -> one app for all radio-listening

Thanks for your thoughts. Warning: no particularly useful app info in this post:


Recording won't be done unless I can find an easy way. If anyone can point me to an app or phone that does it, or can help me get it working on some phone, then I will re-consider.

Skinning should be more or less possible now, without access to my source code, by modifying the XML files in my APK. I might document this so others can try. I'm all for anything that can allow users to modify and improve so that I can concentrate on the harder or core parts.


IMO a free version should use all the things that are different between phones, so I get plenty of feedback on what works and what doesn't.

For example, both versions would use the back/pause/forward buttons on HTC or other earphone cables. A free version might map those buttons to volume and mute. A pay version may allow configuring the mapping to the same or to next/previous station or whatever.

My biggest challenges are at least some of the reasons why Google hasn't produced an FM app (and may never?). Ideally these could be solved for all phone and ROM combinations without root/SuperUser:

(1) Audio routing

(2) FM chip access, provided by HCI access for TI and Broadcom chips.


I'm hoping I can get assistance from others to help solve these problems on various phone/ROM combos. Thus a free app that uses these features is essential.

BUT, once the hard part of getting, for example, BT HCI access, is done, it's relatively easy to have universal TI and Broadcom code using that API. And a paid app could offer more features, like transmitting perhaps that use the same HCI interface for basic functions like power on/off or tuning.
 
Last edited:

4silvertooth

Senior Member
Mar 23, 2011
1,422
137
Android Hell
Ok I get you now I know why the dsp manager (cyanogenmod) doesn't effect audio from radio. If you get the audio to rout there would be cool possibility to get audio effects to work on FM like bass treble etc etc... Or can the equilizer be implimented internally.

Tip:There r call recorders which can record audio maybe we can get hint from it. As soon as I get time I m gonna decompile one such app and will post something usefully.
Is the lib file mikersmicros.... compiled from scratch with source code? Edit: ofcourse you have sorry.

Sent from my LG-P500 using XDA Premium App
 
Last edited:

Talbes

Member
Jul 28, 2010
46
13
Melbourne, Oz
www.mainplan.com
Any chance of getting this to work with MIUI GB

Hi,

Talbess here from miui-au.

just wondering if you are able to get Spirit Radio working with MIUI GB release. The FM radio has been absent from all MIUI GB releases as is hcitool.

I have tried putting hcitool back but it won't run and when I install Spirit Radio it doesn't connect to anything.

Just wondering if its some other missing modules or is it something MIUI have removed from CM7 that is stopping it.

Thanks
 

mikereidis

Inactive Recognized Developer
Jan 28, 2011
7,823
4,146
Ottawa/Gatineau, Canada
Ok I get you now I know why the dsp manager (cyanogenmod) doesn't effect audio from radio. If you get the audio to rout there would be cool possibility to get audio effects to work on FM like bass treble etc etc... Or can the equilizer be implimented internally.

Tip:There r call recorders which can record audio maybe we can get hint from it. As soon as I get time I m gonna decompile one such app and will post something usefully.
Is the lib file mikersmicros.... compiled from scratch with source code? Edit: ofcourse you have sorry.

Sent from my LG-P500 using XDA Premium App

Yes, the audio path in use is the same the HTC FM app uses. It's analog from the BT/FM chip through where-ever eventually on to the speaker or headphones. It seems to be a "special" path and can result in two audio streams mixing without regard for each other.

Yes, DSP stuff and VU meters etc would be wonderful if possible.

Yes, I stumbled across a thread where some hack is used for 2 way voice call recording. Maybe...

Yes libmikersmicros_fm.so is compiled C code via the NDK. Most of my audio routing code is in the Java app, and modelled after the routing code in the CM FM app. But there is still some code in the lib that writes to /sys/devices/virtual/htc_accessory/fm/flag, which does nothing on CM, but works on stock ROMs. Also an ioctl to /dev/msm_snd but that is disabled by default now since CM supports the routing now.
 

mikereidis

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

Talbess here from miui-au.

just wondering if you are able to get Spirit Radio working with MIUI GB release. The FM radio has been absent from all MIUI GB releases as is hcitool.

I have tried putting hcitool back but it won't run and when I install Spirit Radio it doesn't connect to anything.

Just wondering if its some other missing modules or is it something MIUI have removed from CM7 that is stopping it.

Thanks

Hi Talbess. I haven't tried, but I hope it's possible some how.

Some time back I tried to get hciattach, hcitool etc running on a sense ROM (Blayo) based on the stock HTC ROM for the Legend, but I was not successful after a few days of trying. I'm not too experienced with the innards of Bluetooth however.

Basically, I just need some way to get direct HCI access, even if root is required (but preferably not).

I trawled through MANY threads over many days trying to find someone who managed to do this on Android but found nothing. Supposedly the PyBluez guys did it, but I tried their scripts and they didn't work, except I think on CM with root. I tried some fancy tricks with the handles from the Java BT APIs but no go.

Even on CM, from NDK code I could not access the parts of HCI I needed. Android seemed to let me run the equivalent of "hcitool cmd 4 1" (Get BT version), but wouldn't allow me to talk to the FM.

I WAS able to write a daemon that could be started by my app, and the daemon could talk directly to the Bluez stack and FM just fine. But this only worked on CM, and with root to install the daemon (Although I think I know the trick to avoid this now).

AFAICT, hcitool is pretty simple and just talks directly to the libbluetooth stack like my daemon did. So if it won't run, then my daemon wouldn't either. I considered D-Bus APIs but never looked too far into it and couldn't see any HCI api there.


But assuming we have root and can modify the kernel or whatever, there has to be a way to do this.

Over the next few days I'm going to put a stock, or other Sense ROM back on my Desire HD and will be looking for some way to get my app running there. If anyone can recommend a Sense/Stock like ROM suitable for this, please let me know.

Perhaps I'll find some way for stock and hopefully your MIUI GB as well.
 

Victorino86

Senior Member
Mar 25, 2011
60
1
3 or 4 letters under signal bars should be a US callsign, starting with W or K I should disable that for regions outside North America and just show the number. There's also a few databases on the Internet I might hook into.
Yeah, sorry, didn't see the post where you were explaining all the PT, PI, PS stuff
Btw, I'm getting a code starting with K.


Long press (hold for 1/2 second or more) the frequency up/down buttons to seek to the next strong station. As I say, broken on Broadcom in v2.0.8 and should be fixed in next.
Ah, ok, 'cuz it finds the next station but sometimes when i tap "stop" it goes back to the starting station, but I think you already know.
 
Last edited:

CR5N

Senior Member
Jul 15, 2010
584
114
Hi, tried this on HD2 running Tytung2.7 GB2.3.4. If I put in a frequency for a known strong transmission, I see signal bars but no audio from headset or speaker.
 

gmpurohit

Member
Apr 15, 2011
35
1
Not working on lgop1 cm7

Not working on my lg optimus one flashed with cm7..neither is shows signal strength...hats off to the innovative idea.will wait till it gets more stable & polished &
 

nibras_reeza

Senior Member
Feb 8, 2011
852
415
Colombo
nibras.co.cc
EDIT:

If you are new to my app, you can now install the latest version from the Android Market: https://market.android.com/details?id=com.mikersmicros.fm

Since the initial release of v2.0.2 many bugs have been fixed and now RDS data is supported on both TI and Broadcom chips as of v2.0.9.

I hope to get this app working on phones with Silicon Labs FM chips as well, and stock or stock based ROMs, but there are challenges..

Skip to the end of this thread for latest info.


-----------------------
Version 2.0.2 of the "Spirit FM Radio" :

https://docs.google.com/uc?id=0B7UP...Tk2YTMtNGM3ZmFjNjgyZjZl&export=download&hl=en

This is NOT a streaming app. It's for "REAL" tuned radio, usually from 88-108 MHz or so. Like the MIUI and CM FM apps, it is derived from the Code Aurora FM app. I believe I've made more extensive mods than the MIUI or CM apps though.

Spirit FM Radio is in beta testing now. Don't expect a flawless, polished app. If I waited for all bugs to be squashed, this app would never be released.

The app has support for starting and stopping audio when a phone call is initiated or answered. I've done almost no testing on this feature at this time however, and it does not appear fully functional. So please don't expect proper co-operation between phone and FM audio until this is fixed.

Spirit requires Android version 2.1 or greater. On unsupported phones it should go into an emulator mode to allow the UI to be explored. For trouble-shooting, "adb logcat" can be useful. Root/superuser privileges are not required, but there is still one place in the audio routing code that attempts to run a "su" command to chmod /dev/msm_snd. This is only needed on older CM ROMs that do not have an FM radio app. Otherwise, you can configure SuperUser to deny the privilege.

The app has RDS data support on TI FM chip based phones, and hopefully I will be able to add RDS support for Broadcom based devices soon.

At this time it's most likely to work on CyanogenMod 7 on devices/phones on which the CM FM app works. It may also work on MIUI ROMs that support a MIUI FM app. I intend to get this app working on as many devices and ROMs as is feasible. Please feel free to "vote" on what I should prioritise, as far as device or ROM support, bug fixes or new features.

I also have it working on the HTC Legend using the Blayo ROM, and it may work on the stock ROM for HTC TI FM chip based phones such as Legend or Click/Tattoo. This requires the use of a "btipsd_cli_ binary. Under some circumstances, the btipsd daemon may crash. Slower devices, or those which are using a lot of CPU due to other apps/daemons etc. may have timing issues.


Other than the btipsd_cli method explained above, Spirit requires a working "hcitool" executable to control and retrieve data from the radio. The CM7 and MIUI apps use the same method for FM radio access. Spirit is also able to read data from the radio. I think the CM7 app does not have this capability (certainly not for TI chips).

To verify hcitool compatability, turn on Bluetooth and from a terminal emulator type "hcitool cmd 4 1", or from a USB connected PC with adb, enter the following and see if the results roughly match mine. This command gets the Bluetooth etc. versions. The last line should have 12 bytes, perhaps some will be different for you:

adb shell hcitool cmd 4 1
< HCI Command: ogf 0x04, ocf 0x0001, plen 0
> HCI Event: 0x0e plen 12
01 01 10 00 04 00 00 04 0D 00 1F 1D


The following should be able to confirm support for a Broadcom based FM chip. Eg. HTC Desire etc. The seventh and last byte should be 0, or 1 if running an FM app, or 2 if RDS is also being used.

a hcitool cmd 3f 15 0 1 1
< HCI Command: ogf 0x3f, ocf 0x0015, plen 3
00 01 01
> HCI Event: 0x0e plen 7
01 15 FC 00 00 01 00


The following should be able to confirm support for a TI based FM chip. Eg. HTC Legend or Click/Tattoo. The fourth and last byte should be 0. If running an FM app at this time, the radio will stop:

adb shell hcitool cmd 3f 137 1 1
< HCI Command: ogf 0x3f, ocf 0x0137, plen 2
01 01
> HCI Event: 0x0e plen 4
01 37 FD 00


The app supports somewhat different layouts for portrait and landscape. This has been tested at the resolutions:
- 240x320 For HTC Click/Tattoo on emulator).
- 320x480 HTC Legend.
- 480x800 HTC Desire HD

At this time, when switching orientation, the audio will always switch to the analog headset, which can be annoying if you are using the speaker.

Unlike many other FM apps, the app does not enforce the insertion of a headset wire as an antenna. On my Legend I can pick up strong stations without an antenna. On my Desire HD, even moderately strong stations come in without antenna. For best audio and RDS the antenna is recommended.


TI FM chip support has been tested extensively on my HTC Legend and is relatively mature, providing features such as RSSI, seeking, RDS program ID, program type, program service and radio text.

Broadcom FM chip support has been added just recently and is tested on my HTC Desire HD. It supports RSSI and seeking, although the seeking is somewhat broken at this time.

On recent CM7 ROMs, the app and the CM audio framework will "fight" a bit over volume levels. You will likely hear louder volume briefly when adjusting volume using the hardware volume buttons.

Only analog speaker and headphones are supported for audio outputs. The app has some experimental support for recording but it's unlikely to work on any phone at present.


The user interface has 3 "Blocks":
- Station Info. At top in portrait or top right in landscape.
- Presets. Middle in portrait or bottom in landscape.
- Mute/Power. Bottom in portrait or top left in landscape.


"Mute / Power" are simple on / off toggles. Power should automatically be enabled at app
startup. Bluetooth should be enabled automatically if not already enabled, but it's best to pre-enable it manually.

"Station Info" controls frequency via direct entry or left/right buttons. Tap frequency to enter manually. Frequency 102.1 MHz can be entered as "102.1" (with decimal) or "1021" or even "10210". Outside the US, NTSC channel 6 audio can be received (with lower volume) at "8775".

Tap the left or right arrows to move up or down one channel. Channels are 0.2 MHz apart in North America, and may be different elsewhere. The settings menu allows entering country/region to set things such as this increment. North America is default.

Long press the left or right arrows to seek to the next strong channel. This is working well for TI chips, but the Broadcom support for this is mostly broken at present.

"Station Info" also shows such info as RSSI, stereo/mono signal, and the 4 types of RDS data supported at present.

Presets: The app supports unlimited presets and multiple preset lists. The top or left button should display "LIST-1". Tap to select a list, or add a new list. Long press to rename or delete the list.

Pressing a preset button showing a frequency tunes to that frequency. To create a preset, tune to the desired frequency and long press any unused preset button. If there is a preset for that button already, you can select "Tune", "Replace", "Rename" or "Delete".

Once 5 presets are set, the right arrow will be enabled which allows moving to the next "page" of 5 presets.

On my Desire HD the app seems to automatically switch between speaker and headphones when plugging/unplugging the headphone jack. This does not work on my Legend.


The standard android phone "Menu" button provides access to "Settings", an "Enable/Disable Speaker" button which switches between speaker and headphones, and a "Sleep" function. The "Scan" button is not currently functional. The recording buttons may produce a file on the SD card (or may cause a crash!) but the file is unlikely to contain any FM audio.

The "Settings" menu allows changing region, which should change frequency limits, channel spacing, odd/even frequencies, pre-emphasis and RDS/RBDS switching as appropriate. Audio output mode can switch between stereo and audio. Alternate frequency is not yet functional. Factory Defaults should return the config to original.


At this time, the app sends hcitool output to a "fm1" file, on the /sdcard if available, otherwise in the app private cache directory. I will likely remove this requirement to write regularly to the file-system at some point.


This more or less completes my intro to the Spirit FM Radio app. This post will be regularly edited to contain the latest info.
Hmm, I was really looking forward to an FM app that doesn't require headset but alas, this doesn't work on GT540 with stock 2.1.
 

mikereidis

Inactive Recognized Developer
Jan 28, 2011
7,823
4,146
Ottawa/Gatineau, Canada
https://github.com/mik9/android_packages_apps_FM
well if it helps here's repository of FM app which is running successfully on cm7 lgp500.
Note: Its not my work all credit to Mik for the work.

Thanks ! I'll investigate further but first thing I see is "We're using hack in libaudiopolicy to fix crappy FM behavior.."

Can you refresh me on your issue ? I looked back but can't figure out if you are looking to record FM, or if my app isn't running on your phone. I've had at least one report of success on Optimus One/p500 with the unofficial CM port I guess.


------------------------------------------------------------------------------------------------------------
I had mutlii-quote working before but can't figure it out now, LOL.


CR5N and avalst :
>Hi, tried this on HD2 running Tytung2.7 GB2.3.4. If I put in a frequency for a known strong transmission, I see signal bars but no audio from headset or speaker.
>I'm having the same issue on my EVO no sound on any station I've tried.

Yes, I think you are close, but you've run into the dreaded "audio routing" issue. Do you have "adb shell" on a PC ? Here are some things you can try if so. If not, perhaps a terminal emulator for the phone, just remove "adb shell" from these commands:

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

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

If that fails, you can try this:

adb shell "touch /sdcard/fm_su"

But then you have to have a SuperUser.apk or similar installed, and when it requests su access you have to respond in the affirmative. All it does is a chmod on /dev/msm_snd so it can use an "ioctl" to route audio,


------------------------------
lupoalberto12:
>I tried it on my Wildfire but it doesn't work.


Do you get any indication of signal strength when set to a strong frequency ?


-------------------------
gmpurohit:
>Not working on my lg optimus one flashed with cm7..neither is shows signal strength..

OK. I don't know why I had one report of success on Optimus One with CM and many reports of failure. I will likely buy this phone soon and I'm sure I'll figure it out...


----------------------
nibras_reeza:
>Hmm, I was really looking forward to an FM app that doesn't require headset but alas, this doesn't work on GT540 with stock 2.1.


Stock ROMs seem to have these nasty proprietary BT stacks that make life difficult.

I've started a dev thread about this and hope to find solutions: http://xdaforums.com/showthread.php?p=13627988
 
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" ! :)