yashsingh1/xdaforums huggingface dataset:
[Spirit FM] mikereidis:
EDIT: I sent you a new test release that enables speaker in digital audio mode.

This likely will not clear up any "speaker interference" issues. I'll look into that.

As a temporary workaround you can try setting Debug-> Power Restart Media to "Enable" and restart Spirit.

This should reset the entire audio system when FM is turned off. It's "brute force" but usually works.

Oh, OK, you're having the GT-I9000 digital audio mode "no speaker output" problem I posted about above.

Setting Audio-> Method to "Automatic" provides a speaker mode, but it's not digital of course.

The "pull the headset cable" trick for speaker mode is an old trick that often still works. If the phone is on a table or whatever, the plug can be pushed in just enough for the antenna function without triggering the headset detection.

I'm not sure when, but at some point, at least some GT-I9000 AOSP ROMs changed something which has created audio issues when using Spirit digital audio.

I tried Spirit releases from early this year with the same no speaker result. So this is due to some change in the ROMs, not a change in Spirit.

I'll look into it.

Play says August 9 now for the August 10 release because Play uses California time, and as I often do, I uploaded the update between midnight and 3 AM locally.

I'm not sure why you saw August 8 but it's not too important a mystery to solve.
[Spirit FM] mervluk:
Great. Audio now broken on Xperia Z with latest update. Always worked perfectly before. Thank goodness for Titanium Backup to mitigate your tampering enthusiasm! I think you need a new project Mike.

Suggestion: could you not provide a beta update channel for registered users who want it rather than bunging everything straight on to Play? It's annoying*. But I know you have to chase the new customers to make money. And the existing ones will always get forgotten.

That being said I appreciate us Xperia users are small fry in your pond, and therefore will always get gobbled up. It must make no commercial sense though to compete with Sony's own excellent FM support so why not make their phones unsupported and we'll know where we stand. We can keep the app and escape the meddling. That's what happened with my Moto and the app is fine.

*Now I have to do manual updates for every Play app on my phone, apart from yours obviously; simply because you've messed up Spirit!
[Spirit FM] mikereidis:
Set Audio=> Method to "QC Intent" and it should be like "Automatic" was previously. Or "Digital Auto" if you have Unlocked and are rooted and you want that.

I tested OK on the Xperia Z running the absolute latest stock ROM that Sony wanted me to return yesterday, and it appeared to me it should still work on older ROMs. But the phone is overdue already and I'd like to spend more time with my family.

I've considered the new beta channel feature in Play, but it takes time and effort to set up, and I've still been working 60-70 hour weeks for approximately the legal minimum wage here.

I'm sorry if I can't meet your expectations. Please feel free to email me for a refund. Please email me anyway actually; I'll be happy to send a new version for your testing.

Sony and Samsung both have quite nice stock FM apps and they are free and pretty much flawless on the phones they support. I can't compete with that and don't try to.

Most of my customers are custom ROM users and used to things breaking from time to time, and also used to quick fixes and workarounds from me, at least for major bugs such as no sound. And any customer can email me at any time for any old version; I usually respond within 12 hours or so, often much faster.

All this reverse engineering of secret, undocumented APIs and chips is very time intensive, as evidenced by absolutely nobody else having any sort of similar 3rd party FM app, with support for over 10 APIs and about 100 distinct phones from multiple manufacturers, running MANY different custom and stock ROMs based on many different versions of Android and kernels and build dates....

Google isn't doing this, the OEMs don't do this, nobody else on this tiny planet of 7 billion+ people is doing this.

So, unfortunately, to a certain extent, I have to rely on users/customers to be part of my "QA Team".

If I stopped working on Spirit today, it would be broken on I think 50% of the phones running custom ROMs. That's just the way it is and has been. I'm one FM guy, "versus" hundreds of notable and perhaps thousands of less notable ROM guys.

Spirit2 was one solution to the "every new build that fixes some devices breaks others" problem I've long dealt with. But it's been delayed because I want to support my supporters/customers as well as I can, but it seems impossible to run 2 projects at once.

As I more or less posted for the August 10 release, I think Spirit is now "feature complete", with the addition of widgets and notification controls, thought there will always be some who want them to look or work differently.

And I think most of the major visible bugs on supported devices have been pretty much addressed, though a week will go by and likely some ROM on some device brings a new problem. I have a speaker fix pending for GT-I9000.

Other than some minor (?) bugs, I'm happy to leave Spirit alone for a while.

I still and always have a LOT of personal stuff to do that I've been neglecting.

So now I will likely spend 1 hour at least on email, and then hopefully find some time to spend with my family.

:)
[Spirit FM] DjMcM:
Bluetooth Headset Not Working

Dear Developer(s)!

(Sorry my bad english!) :eek:

My Jabees IS901 Bluetooth Headset not working with Spirit FM. Working with any app: Total Commander - Player, MX Player, etc. If running Spirit FM, I hear only system voice in the BT headset. :confused: With wired earphones and built in speaker is very good.

Please, help!

Phone: Samsung i9001 (Rooted)

ROM: LiquidSmooth JB v2.8 (Android 4.2.2)

Kernel: 3.4.51

Thanks!
[Spirit FM] mervluk:
Sorry. Guess I didn't appreciate you're in a nightmare break and mend cycle with every rom. Oh, the joys of android. I've found one that works, the penultimate, and will now just stick with it.
[Spirit FM] DjMcM:
Yes ! I'm testing the many more ROM while the bluetooth work properly. LiquidSmooth ROM is the best for my Samsung i9001!

Working many BT device: JVC CAR-radio, Ipega BT gamepad, Jabees headset, etc. Only Spirit FM not listening on the BT headset.
[Spirit FM] cajunflavoredbob:
Hey Mike. My heart nearly skipped a beat this morning when I noticed that the Nexus 7 (flo) was listed as compatible in the market for Unlocked. I installed it and opened it. I granted it SU permission, then it crashed. I opened it again, and while it was loading, it rebooted the tablet. I tried this once more to confirm. The tablet locks up when the app is opened, while it's got the "Please wait" dialogue box open. Can't send an error log due to this, but I can send a logcat when I get home, which will be shortly.

When I deny SU permissions, I get a popup error message saying

Error: No FM accessible
SU: 1 FM:SLS SU:0 Bt:3 Ht:0 Mo:SLS

Normally I wouldn't even bother sending you a report on this, but I have caught myself up on the thread and noticed that the Nexus 7 support wasn't explicitly ruled out. I'm not expecting it to work, but figured I could lend a hand in giving it a shot anyway.

Logcat coming your way in an hour or so.

EDIT: logcat is attached for the issue described above. The logcat should show me unlocking the screen, then opening Spirit, then the tablet locking up, then the tablet shuts itself down. It's worth noting that I'm not on a stock ROM, so I'll give that a shot next, since I have some free time.

EDIT2: On the stock ROM, refusing root gives the same error as before in the code box. Granting root results in a reboot instead of a shut down. I've uploaded the logcat from the stock ROM as well.
[Spirit FM] mikereidis:
Galaxy S Plus GT-I9001 is not capable of digital audio features such as Bluetooth headset support.
[Spirit FM] mikereidis:
:)

It's an iterative process. After a few quick updates I generally get one that lasts a month. If it's been available for 2 weeks, it likely works on most phones/ROMs without "show-stopper" bugs.

We Android devs would love it if Play allowed a user to revert to previous versions.

At least we now can do a slow rollout 5-10% at a time, or use this new Beta channel feature. I'll look into the Beta channel thing when I get some time.

I have a new release ready soon that basically does the old Qualcomm Intent thing as well as the new API calls thing.
[Spirit FM] mikereidis:
Unfortunately the Play developer console does not allow me to specify the 150 or so device names that I support. By default all devices are marked as supported.

The console requires me to regularly go in, identify all the new devices added to Play identification that I DON'T support, and manually switch them off. I haven't done this in 3-4 weeks now, since it takes a lot of "stupid work", so new devices are by default marked as supported.

I'm trying (ahhh !) to take time off now (more or less), but I should go in and disable some of the new, most popular devices. That reduces my email load for questions (a bit) and sales refunds.

That's fine. I want to verify the 2013 N7 doesn't work too.

To send me a log, start Spirit without FM starting:

- Clear the app data or reinstall.

- When prompted at startup, press Back or "Stop".

- Now Menu/Wrench-> Test-> Email-> Logs ...

"SLS" likely means there is a V4L /dev/radio0 device node visible.

EDIT: SLS is for Samsung's driver. Try setting Debug-> FM Chip to "QC V4L (HTC)".

EDIT2: Apparently Xperia Z GPE has exact same problem. I curse your FM hate Google !! ;)

I think the new N7 uses Qualcomm WCN3660 FM/combo chip for BT and WiFi, and /dev/radio0 is how FM is accessed.

This exact same crash happens on pretty much every WCN3660 based device that does not have radio-iris-transport.ko loaded. It's a stupid, stupid kernel bug that nobody has fixed because it never affects stock ROMs that support FM officially. Spirit tries to access the driver in the normal way, and boom-crash.

I've written the same story for the Nexus 4, the Optimus G, HTC OneXL/S and similar WCN3660 devices.

The radio-iris-transport.ko may not be loading due to needing some lower level code or some other error. Or it may not even be present on your stock Google ROM, since Google doesn't support FM.

An alternate kernel can be built with this driver enabled with a simple 1 line change to the kernel config file. Probably every kernel being built by custom kernel/ROM devs has the same config as AOSP/Google: no FM.
[Spirit FM] mikereidis:
Same with all FM apps for your phone, including stock.

FM almost always has a special audio path, very different from non-FM apps that supply digital audio data. This sentence describes the basis for 50% of my development time and headaches.

Spirit gets partly away from this problem in digital audio mode, on supported Phones. (And does it in a "super fancy" way that no other FM app does, stock or not.)
[Spirit FM] cajunflavoredbob:
Log has been sent.
[Spirit FM] DjMcM:
Than you for all! Unfortunately, you have to look for another solution.

Maybe, sending the line out to BT with any app? A phone call is not necessary, only the FM!
[Spirit FM] mikereidis:
Log confirms exactly what I said.

First, a driver module named radio-iris-transport.ko needs to exist somewhere like under /system/lib/modules .

Then it needs to load without error.

Then, my guess is we'll see RSSI at 0 or negative when Spirit starts, even though the wired headset is plugged in for the antenna.

BUT, then we should try setting Debug-> QCom Antenna to "Internal" and restart Spirit and check RSSI again.

Then set it to "External/Headset", restart Spirit and try again.

This chip has 2 FM antenna pins, and antenna circuitry could be attached to either or both. And on any device on which "Internal" works, the bonus is the possibility of FM transmit.
[Spirit FM] mikereidis:
There IS another solution, and compatible devices are as posted in post #1 of this thread:

Unsupported devices fall in 2 categories:

- Phones that are physically incapable of FM record or digitization.

- Phones that have too few paid customers for me to have that phone among my 20 test phones, or for which it's too much work for too few users.

It's an "impossible" job just supporting regular FM audio on all the phones and ROMs I do, with over 10 undocumented and secret FM APIs.

There's no way I can afford to spend 100 hours on a phone that has even 100 customers. And that assumes that your particular phone is even possible of digital FM audio. It takes a lot of work often just to find that out. I've probably spent over 200 hours on Galaxy S digital audio mode; until I had it working, I wasn't even sure it was possible. And Galaxy S has problems, partly due to CPU load on a now old phone, partly due to stereo/mono problems. I did it because it offered a probable solution to the horrible speaker damage problem, AND because Galaxy S continues to be a sizable fraction of my total sales.
[Spirit FM] cajunflavoredbob:
Is this something for the kernel or ROM so I can forward it to the right person?
[Spirit FM] mikereidis:
Kernel.
[Spirit FM] mikereidis:
Spirit Free August 12: http://d-h.st/vCj

Unlocked and Light updated on Play.

- Fix no audio on Xperia Z*.

- Fix no speaker on Galaxy S GT-I9000 digital audio mode on recent ROMs. Speaker might get "sticky" in some cases, please report.

Hopefully this will be the last update of August.
[Spirit FM] Quinny899:
Hi Mike,

Don't know if you know this, but I just spotted a little part of this month's Android Magazine that might interest you:
[Spirit FM] mikereidis:
:)

Cool, thanks for the tip. Can I find that "mag" online ? Can't imagine a print only mag for smartphones in 2013.

My quick read indicates at least 2 errors:

- Price in Great Britain Pounds is localized actually & I think 6.99.

- Supported devices indicated by the blurb is actually criteria for full digital audio support.

The actual Spirit support list, for non-digital FM audio is much larger than that.
[Spirit FM] Quinny899:
Conveniently on the Play Store: https://play.google.com/store/magazines/details/Android_Magazine?id=CAowq9HnAw
[Spirit FM] mikereidis:
Hmm, $3 an issue and rated 2.6...

It was hard to find any contact info, but I found enquiries@imagine-publishing.co.uk

and sent this:

I have some doubts I'll get any reply, but we'll see.
[Spirit FM] zviki:
WTF are you talking? You can disable automatic updates only for SpiritFM.Or any other installed app... :banghead:
[Spirit FM] GordonFreetux:
I recently formated with the Stock rom on my HTC Wildfire S A510e. Now Google Play tells me Spirit FM is incompatible with my device. What can I do?
[Spirit FM] James Bottomtooth III:
Hi Mike

I'd like to report some findings. With the latest Spirit update digital mode works properly within the app. Volume control, play/pause, and switching speaker/headset work fine, like they used to before an update in March.

(Back in March I was on slimbean 4.1.2 and digital mode worked. It broke after I upgraded to slimbean 4.2.2 AND a March update of Spirit. I wasn't sure if it was the Android update or the app update that broke it. I sent you a debug log but unfortunately you couldn't figure it out. Since then I switched back to 4.1.2 but speaker still wasn't working under digital mode.)

Digital FM works now, but if I quit Spirit with the headset plugged in, unplug the headset then try to make a call or play music, the earpiece and the speaker don't work. If I unplug the headset before quitting Spirit then the earpiece and speaker work as they should. Meanwhile if I receive a call while using Spirit I can only hear them through the headset or the speaker.

Currently, the only workaround that works for me is to enable Power Restart Media in Spirit > Debug.

Hope this makes sense.
[Spirit FM] mikereidis:
Google Play has had some recent troubles, which are now apparently fixed, so try again.

If not, send me an email and I can send you the latest.

Better yet, so I can see your device name, send me a debug log with Menu-> Test-> Email-> Logs and press Send after 20 seconds.

The official device names for Wildfire S are "marvel" and "marvelc" and both have always been enabled on Play.

BUT, "marvelc" seems to have disappeared from the Play dev console. The display name used to USCCADR6230US" (for US Cellular), then changed to "HTC-PG762" and now I don't see it anywhere.

Devices which don't use official names usually allow downloading ANY app, disregarding the Play compatibility list. So, if you're on a true stock ROM, I find this strange.
[Spirit FM] mikereidis:
Thanks for reporting, that's exactly why I said:

:)

Audio should work exactly like in previous releases, as long as Spirit is always in headset mode. If you select Speaker, you may need to reboot the phone or use that Power Restart Media trick.

Pushing audio to the speaker when the headset is plugged in, is not natural for Android. It's an FM specific situation, and only because the wired headset is used for an antenna.

What happened is that somewhere between Android 4.1 and 4.2, custom ROMs/AOSP changed something that prevented the old speaker enable code in Spirit from working. As I said, a Spirit version from February showed the same no speaker problem on current ROMs, despite that it worked OK on the ROMs of that time.

Another example, sadly, of how broken the current version of Spirit will likely be on many custom ROMs in a mere 3 months or so. Even if Spirit was "perfect". LOL.

I'll fix what I can when I can...
[Spirit FM] mikereidis:
Strange volume control issues seen on my HTC One with GPE ROM (and maybe some other devices/ROMs)...

If I use the Spirit app on screen volume slider and set it to higher than 10 volume ticks, out of a maximum of 15 ticks (plus zero), volume goes low or doesn't change.

Use the hardware controls at least once at higher volume, and respond to the high volume warning, and the on screen slider should work OK, until next reboot I think.

The problem seems related to the new high volume warning. Spirit sets the volume without the "User Interface" flag, so the Android audio system decides it shouldn't pop up the prompt. On some stock ROMs and previous AOSP ROMs, this worked OK.

Unlike on other ROMs, on GPE I don't see a way to disable the High Volume Warning permanently.

This might also affect media button volume controls. Maybe even hardware volume controls if the screen is off; never tested that yet...
[Spirit FM] spunker88:
Just wanted to let you know Spirit is still working on CM10.2 on my Droid 3 and also Bionic.
[Spirit FM] mikereidis:
:)

I've also tested Spirit successfully on the new CM 10.2 Android 4.3 Nightlies for:

HTC One

HTC OneX LTE

Galaxy S3 GT-I9300

Galaxy S2 GT-I9100

Galaxy Note GT-N7000

And with no notable bugs/issues being reported, the August 12 release is "golden".

Time for me to work on other things than code for a while.
[Spirit FM] Zero_Shadow:
Galaxy Player 5.0 YP-G70 No Sound

Hello Mike,

I first want to say thank you for all your help support and your work on this app I hate to add on to you pile of work but I do have a small problem with my Galaxy Player 5.0 YP-G70.

Im using this ROM

http://xdaforums.com/showthread.php?t=2386740 (CyanogenMod 10.2)

and this Kernel

http://xdaforums.com/showthread.php?t=2252851 (Sultan-kernel-Venturi-r6-USA-CWM-Fixed).

In the kernel the dev added support for the FM radio driver (SI4709) which allowed SpiritFM UL to work (see below)

as you can see the RDS works meaning that the driver and spirit are working together however the problem I am having deals with the No Sound issue (Headset or Speaker) that seem to have crept up the last few days as mention in the posts earlier. I tried a few of the suggestions mentioned changing the Audio Method, Debug-> Power Restart Media to "Enable" and restart Spirit, Audio=> Method to "QC Intent.

A user stated at one time it worked flawlessly Im guessing it was possibly it was a older version of Spirit that worked

http://xdaforums.com/showpost.php?p=44307081&postcount=47

http://xdaforums.com/showpost.php?p=44330267&postcount=57

Below is a link to the log from Spirit (for some reason could not attach here sorry)

https://www.box.com/shared/static/v3amcnr2h1502yo3rev7.txt

Is there anything that you can suggest to try to make this work or communicate to the dev to see if it will help or if you need additional information please let me know.

Once again thanks for all your help.
[Spirit FM] 089man:
Spirit runs fine with pacman Rom android 4.3

I9100 Tapatalk 2, Rom1 Rootbox / Rom2 Test only, Kernel Dorimanx
[Spirit FM] mikereidis:
There are likely only 3 Audio-> Method settings that might work:

Galaxy S ALSA/ICS (with speaker damage risk)

Galaxy SL/i9003 (same risk)

Digital GS1

If it was stock or used stock audio libs then "Galaxy S2/S/Gio GB stock" or even "Galaxy S3/Note/S2_ICS" might work.

If only an older version of Spirit has working audio, please try and find out the build date with Menu-> About.

There were a LOT of changes to "Galaxy S ALSA/ICS" over the years to attempt to eliminate the speaker damage risk.
[Spirit FM] mikereidis:
Short answer: No.

Long answer starts with: I already have.

No

Solving world hunger and war are also very needed.

See this post: http://xdaforums.com/showpost.php?p=31983221&postcount=4469

It starts with:

My hands are more than full with receive only.

Only a few phones are capable of transmission.

It would requires LOTS of work to support maybe 3 rare/old phones.

Spirit has a test mode for transmit that works on some of the ST-Ericsson based 2012 Sony phones. No audio though; that would require lots of reverse engineering and testing, and it may not even be possible.

Feel free to take up the cause yourself, or sponsor someone to do so. I don't have the time or sufficient incentive.
[Spirit FM] mikereidis:
The Emmis NextRadio app has finally been released, at least for Sprint versions of the HTC One & Evo 4G LTE: https://play.google.com/store/apps/details?id=com.nextradioapp.nextradio

I've got it now and will be examining it.
[Spirit FM] shunsai:
Off topic, but I just had to say cool screen cap! I actually used to DJ at WRAS! Album 88. Small world...
[Spirit FM] mikereidis:
Meh... Emmis NextRadio app is underwhelming.

It's interest to me is that besides Spirit, it's about the only other 3rd party FM app supporting multiple phones that could potentially be "notable".

Comments to news of the apps release (and the red HTC One) indicate very little interest in the FM. Basically it's boring; maybe if we just ignore it, it'll slink away, LOL.

It's intended for US only. It uses geolocation or manual US zip code entry to load a list of local stations.

App is pretty basic. Speaker/headset, Tune/Seek up/down, pause, play and add favorite.

RDS data seems not displayed. If you don't have a data connection, you don't get info. LOL, we often use OTA FM where we can't get a good data connection.

If you have a data connection, there are a small group of stations which can provide currently playing album art and song info. Otherwise you just get a static graphic of the station, or a standard graphic for stations that didn't bother registering one. At least some Emmis stations allow buying the current song. This info might be done via radiodns.

It uses an API created by Emmis in 2012 for NAB Labs as a demo. They added HTC specific support that calls functions/sends Intents to the HTC FM Service. Doing this they can support multiple stock recent HTC devices without much regard for the FM chip.

There's a basic widget, lockscreen and notification window controls.

What seems silly to me is that the whole Sprint/Emmis/US FM broadcasters deal was supposed to "put" FM chips in 30 million phones over 3 years (and for $15 million).

But the current Sprint devices being supported (One and Evo 4G LTE) are not new (except the red One, LOL) and those phones sold by Sprint already have stock HTC FM apps installed.

So basically they added an alternate FM app to the stock ROM that has some interactivity on some stations.

We'll see about future Sprint phones which have an FM chip "added" to them.