yashsingh1/xdaforums huggingface dataset:
[Spirit FM] mikereidis:
March 29 on Market and: http://www.mediafire.com/?hfu9h7hw5qegtv0

- Fixed mute for Samsung2 audio method on stock Galaxy 5 devices.

- Free version restores Settings and Frequency Up/Down buttons.

- UI enhancements:

Now using embedded multi-density ICS icons for all Android 2.1+ versions.

Default User Interface->Theme now "Auto Holo/Look" which emulates the ICS dark buttons on Android 2.3 GB and earlier.

If you were using Quinny's mods via Test->Preferences->Import, it's probably best now to disable User Interface->Custom Elements, restart the app and see how you like the new defaults.

Translucent works now, but it's GB look; there is no Holo translucent.

Holo Light added.

New User Interface->Text Color defaults to "Auto ICS Blue", and has many other settings, including "Default" which uses the default for your selected Theme.
[Spirit FM] kura808:
Just bought the lite version. I really like the new ui compared to the colored buttons ui. The notification bar icon access works great.

Btw i left a nice review on the market =) this dev deserves credit for this feat.
[Spirit FM] mikereidis:
Great. thanks ! :)

What do you mean by the "colored buttons ui" ?

Those psychedelic customizations shown for the free app on the Market/Play ?

They were only intended as a color and feature demonstration, and I've had almost no comments about them, so I left them there. But I should replace them with something more tasteful.

I'm surprised they didn't result in more people asking how to customize colors. I guess most people just use the defaults and expect me (or a helpful person such as Quinny) to figure out the best defaults.
[Spirit FM] Kess78:
Hi,

In the new version the Ratiotext is displayed on one line only again and is cut at the beginning and the end :(

I have to reduce text size to 10 to be able to read normally, but it's pretty small :(
[Spirit FM] mikereidis:
The tolerances are very tight here, especially for smaller screens.

I'm going to add a dedicated easier text size setting tonight, but I'll also try to give a little bit more room for Radiotext.

You can get more vertical room by disabling 1 or more lines under Settings->User Interface. For example:

Display Status: at top, contains RSSI.

Frequency Buttons 2: Settings and Frequency Up/Down one step (not seek).

Preset Buttons 1: If you have 6 presets or less, and only 1 preset list.

Preset Buttons 3: If you are OK with only 3 preset buttons on screen.
[Spirit FM] cba1986:
I noticed a bug. That wheni receive i message and the notification soubd is played the radio stops and i have to reboot the app to get it working again.
[Spirit FM] mikereidis:
Yes, this is a known issue and just one of many problems with the GalaxyS alsa/danger method.

I have some code that may be able to help. I'll try to enable it tonight with a new option.
[Spirit FM] TurboLed:
As a workaround, without restarting you can press pause then play and it will come back.
[Spirit FM] mikereidis:
Yes, thanks.

If sound ever stops or comes out of the wrong place, Pause/Play (Mute/Unmute) or Speaker/Headset usually restores it.

This is one thing the Unlocked media button support can help with, without having to re-open a screen off device.

But I'll try to get a fix in. EDIT: Not enough time tonight.
[Spirit FM] mikereidis:
March 30: http://www.mediafire.com/?6dxde5qtvoaa603

- SU detection bug fix for un-rooted. (Broken for a while; surprised no reports.)

- Smaller text for preset buttons, RadioText and Program Service. Should fit easier now.

- Translucent themes cause no end of problems, including auto rotation. Sounds cool, but nobody uses it. Replaced with "Full Screen" theme, that's like default "Auto Holo/Look" except removed the top status bar giving a bit more room.

- Email logs improvements to give me more data about device and ROM so I won't have to ask so often.
[Spirit FM] sp1980:
Unfortunately the latest version still crashes with both qdsp5v2 (normal and ics/plus) audio methods. After setting up it works but after starting the app the phone is going to reboot. To support you a little I bought the lite version but there's no difference between both versions concerned this behavior. Could kernel 2.6.35.14 cause problems? Really hope there will be a solution.
[Spirit FM] thermskin:
yes but after that no sound on dhd only reboot helps
[Spirit FM] mikereidis:
Thanks. :)

Yes, there should almost never be a difference between the versions for things such as this. If one version works on headphones, they should all work on headphones.

And I didn't do anything in this release that will fix any audio methods.

Yes, the kernel could be a source of trouble. Low level audio methods such as qdsp5v2 send "ioctl" commands directly to the kernel device drivers, thus bypassing the audio libraries. These libraries likely don't have FM support in AOSP ROMs.

Manufacturer ROMs that support a stock FM app will have audio library support, so methods such as "Samsung" or "HTC" will likely work.

An AOSP kernel may not have FM support in the device drivers, or it could be different or deficient in some way.
[Spirit FM] mikereidis:
I decided to un-publish the Free app due to comments/reviews such as these (and I added some responses):

====

Michael on Friday, March 30, 2012 at 15:06 Samsung SAMSUNG-SGH-I727 (SGH-I727)

Garbage..	Its listed as FREE but, they want 99c to use it in their "lite" mode. Deceptive advertising... deleted..

Response: They ? I'm one dev, not some big, rich corporation. It takes very little reading to figure that out. Deceptive ? Please feel free to point out any alleged deception.

====

r3loaded on Friday, March 30, 2012 at 11:21 Samsung Galaxy S (GT-I9000) Version Mar30

Works great, but...	This app feels a lot like bait-and-switch to me - it started off fine, and I was OK with premium features being in the full app. But over time, more core features are slowly being removed from the free app (even something as simple as stereo FM) rather than advanced features being added to the premium app. Upgrades shouldn't remove functionality by definition. I was planning to buy the premium app eventually, but I think I won't bother now due to the crippled functionality and incessant nag screens...

Response: Nag screens ???? Where ? What ? Updates can and do remove functions. It happens in software all the time. Bait & Switch ? I can understand that it might feel that way. But would you rather I had never released a free version with those many features ?

====

Ciaran on Friday, March 30, 2012 at 18:49 HTC Nexus One (passion) Version Mar9

Meh	OK, so devs want to make money for their efforts. So add functionality to the premium version. This dev has started to belittle free version. Bah humbeg. Titanium revert + market freeze.

Response: Functions, device supports and improvements are being added on a regular basis.

====

Free apps always have worse reviews than paid. That just makes sense. Anybody can review/criticize a free app, including angry people who expect perfection for free, and refuse to pay for any app.

And once people get used to free apps with good features, they get angry when new releases remove features. So the reviews are worse than they would have been for an equivalent new app.

I expect to still post mediafire links for updates to the free app. I guess I can re-publish the free app on the Market and I may do so at some point. But I will likely use a different package name and start fresh.

One reviewer seemed to think my GalaxyS ALSA warnings were "condescending" and another seems to feel I have an "attitude" that needs toning down. I'm trying my best not to do such things, but as a human it's hard not to feel anything when your work is being slammed, sometimes with outright lies and ridiculous accusations.

I owe nothing to anybody, except my paid customers. When I offer a free app, or free technical support, it is at least partly for "business reasons", but it's also a "gift" and if you can't appreciate that, then... well that's just... I don't know.

As always, comments are welcome. :)
[Spirit FM] tiwag:
It's your decision and i respect that.but personally i think you should not be angered about and stand above such comments.

All my best to you, brgds tiwag

__

sent using recycled bits and bytes, tiwag
[Spirit FM] mikereidis:
:D

It's always difficult to convey "tone" in email or text posts. I don't think I'm angry and I hope what I write isn't misinterpreted.

In my original unedited post above, there are no capital letter words, or exclamation marks. The closest is the only case of more than one question mark in a row for: "Nag screens ????", and that's just because that's false. See *.

My un-publishing is not driven by anger. I'm not trying to "get back" at anyone. It's just a calculated decision that is mine to make. I've never made any promises to indefinitely support, update, add features and never remove any features from a free version that is easily available on the Market, or otherwise.

People who want to keep running old free versions are welcome to. People who are willing to spend a few minutes figuring out how to install an app outside of Market can also install from mediafire or where-ever.

And I'm pretty sure I'll continue to build a free version indefinitely. I won't guarantee it will always be easily available on the Market. But it will likely return to the Market as a new package name at some point.

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

* IMO, Nag screens are unexpected and unwanted popups saying "Buy this app". They usually pop up every few minutes or whatever when running an app. My app has never had that; closest is recent popups warning about speaker problems and explaining the Light version, with a bit of a sales pitch, but a one time message isn't a nag screen. Or even pressing Menu->Support and being offered a purchase choice. First 2 definitions I Googled seem to agree with me pretty much. My "Intro Message" goes away as soon as you press Disable. The only time I create a new one that needs a new "Disable" is where there is very important updated info and that's only happened a few times in the last year.

Now that I think of it, someone who just hits OK each startup and doesn't read or understand the message, may never hit Disable. But nobody has complained about that before, and I'm pretty sure an Intro message does more good than harm, and sometimes forcing someone to read something is in their best interest, as with the possible speaker damage warnings.
[Spirit FM] sp1980:
The dec23 version works ok with this kernel, so it's not something about FM support in general. I think it's quite complicated :/
[Spirit FM] aderta:
GSmart G1315 Skate

Is there anything can be done for such phone: GSmart G1315 Skate from Gigabyte?

I tried to use all possible variants, but couldn't make this phone start your app working.

If it is anything can be done, I'll appreciate it.

Thanks.
[Spirit FM] mikereidis:
Thanks for saying "Complicated" instead of "I broke it". ;)

Hmmm, icke has been saying Dec23 is the only one working on his HD2 on ICS.

I just looked at your earlier messages, and your problem is reboots the 2nd time on Desire Z, so it's something not right with the SU facility or commands that set the file permissions.

I changed the SU method around that time due to problems on some devices. On versions up to March 29 you can enable Debug->Use fm_hcitool and I think it should use the old method. On March 30 I disabled that. Enabling fm_hcitool might cause other problems, but at least we can see about stopping the reboot.

I'll create some SU related options tonight.
[Spirit FM] mikereidis:
It's disabled on the Market, simply because I've heard no reports of success. The latest free version is here: http://www.mediafire.com/?6dxde5qtvoaa603

You can send me a debug log: Hit the Frequency button, enter 7 and OK, and after a few seconds. enter "Phone Model" in the email text and press send.

Someone emailed me Jan 3 and got this: "Error: Power" and:

Fm:V4 Sh:1 Su:1 Bt:0 Ht:0 H2:0 Mo: V4D

So it uses a V4L FM driver. It may be Qualcomm Tavarua, and I've given up trying to make that chip work, or any other V4L driver supported chips.

If it's Tavarua, then there's a free open source app posted (for ICS) on this thread that might work: http://xdaforums.com/showthread.php?t=1151928&page=39
[Spirit FM] xmguy:
Mike. I'm looking into buying a Pantech Breakout 4G Verizon phone. I know your first thread said Pantech doesn't work. Wondered if you heard any different?
[Spirit FM] rollon76:
2.0.14 Works well on Wildfire,but when turn it off and then turn it on no sound at all.
[Spirit FM] mikereidis:
Woohoo ! :) Hopefully it works as well or better with v2.0.15.
[Spirit FM] mikereidis:
Here's the new v2.0.15 on Microsoft Windows Live: https://cid-55f5bd3bd01e3387.office.live.com/self.aspx/.QuickDocuments/FMRadio^_v2015.zip

And on Google Docs: https://docs.google.com/leaf?id=0B7...jgtMmI5NGZlYzJmNzYx&hl=en_US&authkey=CLvEkL8D

Fixes many issues related to blocking (hang, FC etc.) and timeouts. Now if there are problems, the app is more likely to give errors or start in emulator mode, instead of hanging. Also, startup may be quicker in certain circumstances.

Also some modifications to seeking, and low power mode when the app is not visible now turns RDS off completely for better power savings. If RDS doesn't resume for some reason, power cycling the app will hopefully fix it.

The SU/root mechanism is modified so that only one SU request will be made and after that different commands are handled by, in a way, "fooling" the SU utility.

I did note a last minute problem where the app might not start properly in direct HCI access mode (with BT on and using bcprp without hcitool.) This seems to be fixable by power cycling the app.
[Spirit FM] mikereidis:
Hmm, OK. That seems kind of strange. If anyone else sees this please let me know.

Can you try the v2.0.15 I just posted ? I don't think it will help, but who knows ?

I'm in the midst of adding an audio customisation mechanism that should be able to deal with issues like this. It's mostly to fix the "No Audio" problem on some device and ROM combinations, but should also be able to fix issues like this.
[Spirit FM] dancer_69:
Htc Tatto with CM7(android 2.3.4) no signal or sound

I didn't follow this thread for the last weeks and I had the latest version from market which works well.

I just today see that there are new versions from the one I had and I downloaded and test the latest 2.15.

On this version I haven't any signal or sound any more.

Here is the logcat output file:

EDIT:

Just tried 2.14 version. No sound or signal here too
[Spirit FM] rollon76:
The same problem on v 2.0.15

For the first time, when the radio turn on everything is ok.Turn the radio off and then turn it on, the application is working, but no sound at all.After that BT seems not working.
[Spirit FM] idkidk:
Hi mikereidis,

first of all, some info:

i use sdk 1.6 from windows pc, no problem with adb. The test is done with BT OFF.

I have "magic" srv_len line with this setting:

1) adb shell bcprp --initbaud 115200 --baudrate 115200 --patchram /system/bin/BCM4329B1_002.002.023.0534.0590.hcd /dev/s3c2410_serial0

2) adb shell bcprp --initbaud 4800 --baudrate 57600 --patchram /system/bin/BCM4329B1_002.002.023.0534.0590.hcd /dev/s3c2410_serial0

3) adb shell bcprp --initbaud 4800 --baudrate 38400 --patchram /system/bin/BCM4329B1_002.002.023.0534.0590.hcd /dev/s3c2410_serial0

with higher setting like:

-adb shell bcprp --initbaud 3000000 --baudrate 3000000 --patchram /system/bin/BCM4329B1_002.002.023.0534.0590.hcd /dev/s3c2410_serial0

there isn't any srv_line.

This error:

-default_bdaddr_set open: /data/misc/bluetoothd/bt_addr errno: No such file or directory

the directory exist, this is the content:

D:\temp\DD\droid\asdk\tools>adb shell

/ # ls -l /data/misc/bluetoothd/

ls -l /data/misc/bluetoothd/

drwxr-xr-x bluetooth bluetooth 2011-04-13 19:50 A:D:7:p:9:p:5:D:2:):A:cool:

/ # exit

Finally, i've changed the bcfm to match 115000 - 115000 and try, but no signal and no audio.

In attach logcat.

Thanks!

Idk
[Spirit FM] icke:
Thank U for v2015. I've just installed the .apk w/o using the two other files in your package and after a reboot it's working great. I can turn off and on via standby button and it works like it should. GREAT!

Waiting for scann function!:D
[Spirit FM] VibrantOwnr:
It won't let me download off of google our windows live. Any chance of another server?

Thanks
[Spirit FM] Mach1Chris:
Not working on 2.0.9 version from the market on my stock Sony Xperia Arc, Rogers branded. Loads up but no signal and no sound both with and without the headset plugged in..
[Spirit FM] mikereidis:
If anybody is unable to access via Google Docs AND MS Windows Live, PM me your email, or just send me an email to the obvious username at gmail.com and I'll email the Zip or Apk to you.

I don't understand though how you could be in the US but neither of those servers are available to you.

Can your or anyone recommend a file server that just about anyone anywhere could access ? Preferrably without those "Wait for free download" issues. I REALLY don't want to have a list of 10 different file servers to upload to every revision.

CC via PM.
[Spirit FM] icke:
Dropbox?!;-)
[Spirit FM] mikereidis:
Sorry to hear that Mach1Chris, but thanks for your report.

At this time the app is most likely to work on CyanogenMod (CM), and least likely to work on stock ROMs.

Apparently xda user Blagus is working on a CM port for this phone, but it might be some time before that works well.

I found this item, which appears to indicate the FM is provided by a TI combo chip: http://www.thisisant.com/pages/spec...atrade-arc-connects-to-14-million-ant-devices.

It would be useful to get pointers to any technical threads about the Arc FM, as well as any info that can be dug up. If the phone is running the bipsd service/daemon, my app can support access via the btipsd_cli utility.
[Spirit FM] mikereidis:
Well despite the founders goals, my quick look at Dropbox "just made me think too much".

VibrantOwnr recommended mediafire, so here it is:

http://www.mediafire.com/file/vqbamhu0dh0k3dw/FMRadio_v2015.zip
[Spirit FM] mikereidis:
Yes ! We've solved the first major hurdle by getting bcprp to work. :) Stick with "--initbaud 115200 --baudrate 115200". The 4800 was only appearing to work because it ended up using the default of 115200.

The /data/misc/bluetoothd/bt_addr issue should not affect us for this.

Looking at the logs, it appears that bcfm is not getting started. I would guess the permissions are wrong, or it doesn't start with "#!/system/bin/sh" or your shell is not /system/bin/sh .

Use "adb shell which sh" to see your shell. Modify bcfm for this shell path.

Use "adb shell chmod 777 /system/bin/bcfm" to set Execute permission etc.

In the adb logcat after this:

D/fm_hrdw ( 1827): sys_run: 'su -c "sh < /mnt/sdcard/sprt_su_cmd"'

D/su ( 5731): 10034 /system/bin/sh executing 0 sh < /mnt/sdcard/sprt_su_cmd using shell /system/bin/sh : sh

D/fm_hrdw ( 1827): sys_run ret: 0

You should get this:

E/bcprp ( 5718): do_daemon_hci got ready inquiry

D/fm_hrdw ( 1827): bcfm_start ok

D/fm_hrdw ( 1827): HCI Version: 4 Revision: 288 LMP Version: 4 Subversion: 33031 Manuf: 15

Instead of this (bad):

E/fm_hrdw ( 7279): do_client: recvfrom errno: 11

...

E/fm_hrdw ( 7279): bcfm_start timeout error
[Spirit FM] idkidk:
Hi mikereidis,

this is my shell and how is bcfm directly from phone:

D:\Personal Device\Android\asdk1.6\tools>adb shell

/ # sh

sh

# exit

exit

/ # cd system

cd system

/system # cd bin

cd bin

/system/bin # ls -l sh

ls -l sh

-rwxr-xr-x root shell 91064 2008-08-01 14:00 sh

/system/bin # sh

sh

#

# exit

exit

/system/bin # ls -l bcfm

ls -l bcfm

-rwxrwxrwx root shell 150 2011-05-24 10:12 bcfm

/system/bin # more bcfm

more bcfm

#!/system/bin/sh

adb shell bcprp --initbaud 115200 --baudrate 115200 --patchram /system/bin/BCM43

29B1_002.002.023.0534.0590.hcd /dev/s3c2410_serial0

/system/bin #

I think that shell and permission are ok.... :confused:

P.S.

if needed busybox is installed...

Tia

Idk
[Spirit FM] mikereidis:
Yes, that is very strange. If you run "adb shell bcfm" does bcfm and bcprp start and do you see new lines in adb logcat ?

Here is an alternative approach for testing:

We need to start bcprp manually, but we must rename it first because the app will kill any processes named bcprp before starting a new one. But we must also ensure there IS a /system/bin/bcprp file, AND that bcfm won't start a second daemon. This is how I would do it, and more or less did do it to test:

adb remount

adb shell mv system/bin/bcprp system/bin/bcpr

adb shell touch system/bin/bcprp

adb shell /system/bin/bcpr --initbaud 115200 --baudrate 115200 --patchram /system/bin/BCM4329B1_002.002.023.0534.0590.hcd /dev/s3c2410_serial0

At this point, bcpr should remain running and the magic "srv_len" can be seen in the adb logcat.

Start the app, and hopefully there will be a logcat line: "bcfm_start ok" in there somewhere, and the app will hopefully work.
[Spirit FM] mikereidis:
OK, thanks for the logs.

The app is trying to start bcfm and bcprp, and this is failing due to lack of SU capability.

The quickest fix for you is to delete the /system/bin/bcfm and /system/bin/bcprp files. You only need them for the daemon modes. If you can get it working though, it reduces the system load.
[Spirit FM] mikereidis:
OK, can you tell me or remind me what phone and ROM you are using ?

Did you ever have the app working, any version from the Market or from links posted here ? Thanks...
[Spirit FM] mikereidis:
April 1: http://www.mediafire.com/?8m7lgrrddqi62e2

Free version only; No Market/Play update. Needs Debug->SU Type = "Command" on some devices when using SU.

- Minor fixes.

- Hopeful fix for post Dec23 reboot or other SU related problems. New Settings->Debug->SU Type settings:

Automatic (default): Identical to "Echo" SU method for now.

Disable: Disables requests for SU.

Echo: The SU method used Dec23 and prior.

- Doesn't work on Galaxy S w/ CM9 ICS and likely some other devices. Use "Command" instead. Echoes command to "su -c sh"

Command: The SU method used post Dec23 and pre Apr1.

- Writes command to file then runs "su -c sh FILE".

Simple: The simplest "su -c COMMAND" SU method.

- Using this SU method can result in 20 or more different SuperUser requests, and even then doesn't seem to work on GalaxyS w/ CM9. This issue is why the "tricky" methods above were created, to fool SuperUser.apk that they were all the same command.

From what I understand, there are some bugs and quirks in the different versions of "su" and SuperUser.apk or Superuser.apk etc. This isn't an AOSP feature so it seems to have some issues on some ROMs.

If I could find one SU method that worked on all ROMs, without 20+ popups, I'd use it. All I can say is "Fragmentation"... :)
[Spirit FM] mikereidis:
Pantech Breakout, huh ? :)

AFAICT it has no FM, despite what a minority of phone spec sites may say.

Pantech is on my "virtually unheard of" list, and thus Market excluded.

Any such device could be re-included on my "supported" list, but only if it worked reasonably well without too much work to be done. And I would likely never buy one for the test bench unless it became quite popular or was representative of a class of phones that were popular.
[Spirit FM] xmguy:
So I guess the Bionic is the only known working 4G Verizon phone with Spirit?
[Spirit FM] mikereidis:
Or the HTC Rezound or Thunderbolt. I'm not seeing the Thunderbolt on their website for some reason though, perhaps because it's over a year old ?
[Spirit FM] xmguy:
The ReZound is listed as NOT compatible on your first page. If I can't get the Bionic I'll grab a Rezound ONLY if Spirit will work however. I need Spirit back!