yashsingh1/xdaforums huggingface dataset:
[Spirit FM] mikereidis:
ABSO friggin LUTELY.

IE, yes. :)

I'm not going to ignore the most anticipated device of 2012, and I think likely the single biggest seller. As long as we're talking about the Non US versions that have the Si4709 FM chip....

Nobody has told me yet, or sent a debug log, but I've heard it works fine on a stock GS3.

Apparently it doesn't work on CM9, but I haven't heard what the symptoms are yet. I have one debug log showing the Samsung FM driver was loaded OK, and the first RSSI reading was 0.

But I saw no more RSSIs, so I don't know if it's just an audio issue (the bane of my app.)

Please install June 15 Free (top of post 1 of this thread) or one of the Play versions.

Then let me know in detail what happens as you tune, etc. Feel free to try different Audio->Method settings. Try them all if you can but start with the ones with Samsung or Galaxy in the name.

You can stay in the Audio settings screen as you do this, as long as you are tuned to a known good channel, the volume is cranked up, the RSSI is 10 or preferably much higher, and a wired headset is plugged in and laid out for an antenna. Even if RSSI is 0, try it.

And send me a debug log with Menu->Test->Email Logs. Then reboot and send me another.

If someone(s) can send a debug log or 2 from a stock or stock derived ROM, that would also be very helpful.
[Spirit FM] mikereidis:
Were we emailing ?

Can you send me a debug log with Menu->Test->Email->Logs ?

I'd like to make the Audio->Method selection automatic.
[Spirit FM] mikereidis:
June 18 test release only for Qualcomm FM chip devices: http://d-h.st/imk

Audio->Method = "HTC" may work on HTC One S/XL.

Audio->Method = "HTC OneX" may work on HTC devices, and Huawei devices might work better with this than with the usual "Huawei Tavarua".

EDIT: I just placed an order for an AT&T OneX. Hopefully I'll get it this week.
[Spirit FM] aseanity:
Will, by any chance, the little brother of S2, I9100G get supported by sipirt FM :)?
[Spirit FM] mikereidis:
I've had several requests, I guess due to CM9.

I look here: http://teamhacksung.org/wiki/index.php/CyanogenMod9:GT-I9100G:Nightly:Known_issues

and see:

LOL. :)

Only problem is the lack of audio, but it can often be a BIG problem. I've had a nice detailed voodoo report sent to me, but I haven't spent TOO much time on it yet.

So hopefully "soon-ish". :)
[Spirit FM] aseanity:
Thanks, really looking forward it.
[Spirit FM] Matchstick:
I can confirm that the app works fine on an SGS3 running stock firmware once you set the audio method to Galaxy Note/S2 ICS.

As requested I've sent along a log file but if you need any more information or testing please let me know.
[Spirit FM] djbill2005:
LG Optimus Sol LG-E730

Hi to all.

I have one simple question: Anyone have Spirit Fm working on LG E730?

I just have read this, but i think someone maybe have Spirit FM working on LG-E730

My LG E730 have CyanogenMod 7.2 Stable ROM.

I attached screenshot with error at start.

Thanks in advance.
[Spirit FM] bobbybob:
yes, lot of the CM9 people on S2 G version are waiting and wish to get it so that turn the phone become perfect.
[Spirit FM] cccpro:
How can I increase the RSSI value with 26 units? i want Spirit to return the real dBuV signal value.

I tried to edit the .apk with APK Edit and APK Manager but couldnt figure out how...
[Spirit FM] Simoleon23:
I really hope you can release Spirit FM for GT-I9100G CM9 :D
[Spirit FM] mikereidis:
I'm not aware of any success reports. The good new was just above your quote:

When I wrote that I was under the mistaken impression that the International OneX (that I have now) had the same FM chip. But it uses a TI chip.

So I've now ordered an AT&T OneX and hope it arrives this week. I can't make any guarantees about "LG E730"; for all I know it's audio system is very different and there is no FM audio support on your ROM. Generally I can look at the stock FM app and make my app work on the stock ROM at least.

Your screenshot indicates the FM chip is misidentified as "Samsung Silicon Labs". This is a result of the CM folk using /dev/radio0 for a non V4L device (sigh).

You may have better luck if you set Debug->FM Chip to "QC V4L (HTC/u8800+)" and restart the app. If that doesn't help, try setting Debug->FM API to "Low Level" and restart again.
[Spirit FM] mikereidis:
Thanks for your "vote". Demand/votes certainly influence my decisions/priorities.

But my time is in short supply lately, and sometimes I just have to turn the computer off for 24 hours, as I did the last 24.

Wikipedia says:

Can anyone tell me which countries in Asia and Europe ?
[Spirit FM] mikereidis:
As I said in my last reply:

"The data sheets say this number is in dbuV (decibels microvolts.)"

For the Si4709 FM chip, my code returns the exact raw value from the chip, so it should already be in dBuV.

The license validation code pretty much prevents you from changing any of the code in the app. Otherwise, it would be as trivial to bypass as it was 9 months ago, when it first appeared cracked.
[Spirit FM] Jiangyi:
Here's a list (Apparently it's not just Asia and Europe, but Africa too. Didn't know that.):

Iraq, Morocco, Kenya, Algeria, Tunisia,

Malaysia, Vietnam, China, Pakistan, India,

Bangladesh, France, Germany, Austria, Libya,

Afghanistan, Iran, Egypt, and Saudi Arabia.

P.S. I kind of helped write that part of the Wikipedia article. :p
[Spirit FM] mikereidis:
Thanks ! :)

I have a good number of customers in France, Germany, Austria, and India. Some in Hong Kong also, and they might get some Chinese models. Even 1 customer each in Pakistan and Saudi Arabia...
[Spirit FM] spaventoso11:
Do include Philippines.. it seems there are just i9100g sold here and Spirit FM will complete this baby. Will buy your app if this work on CM9 nightly build..

Thanks in advance mike.. \m/
[Spirit FM] Simoleon23:
I'm glad that you're considering developing a radio for I9100G :) Here's some additional countries in Asia:

- UAE

- Bahrain

- Qatar
[Spirit FM] mikereidis:
:)

Philippines: 6

UAE: 0

Bahrain: 1

Qatar: 1

Qatar seems the richest country on earth, with a per capita income around $100k.
[Spirit FM] mikereidis:
Pirates ! LOL. :)

If anyone can clue me in to the best pirate offerings of Spirit lately, I'd be much obliged. I went looking but I can't and don't want to run the EXEs I saw.

Feel free to PM or email mikereidis@gmail.com anonymously or whatever, but I won't be tracking you down or anything. I get like 20-30 emails a day from pirates, LOL.

AND I think someone somewhere has been passing around an Unlocked license file...
[Spirit FM] Mohanned85:
Works perfectly now. Btw does this work for galaxy s 2
[Spirit FM] Jiangyi:
I found almost every one of your recent releases of the unlocked version on a popular Chinese forum site through a simple search. I don't blame them though, most people don't even know the existence of Google Play since phones don't come with it due to Government censorship against Google.

I will send you a PM with all the info.

EDIT: Played around with the unlocked Jun 15 release. I actually now get static coming out of my phone's speaker. Here's a Spirit FM log:

http://www.mediafire.com/?o96wpc2gik6ykkt
[Spirit FM] mikereidis:
Thanks ! Waiting for your PM.

Actually I think now that June 15 has been hacked to not need a license file. I figured it wasn't TOO hard for someone with some skills to do. But I haven't activated the 2nd level of protection yet. :) (And nothing is unbreakable, really.)

And I understand too, with no easy, legal way to buy in China, and among those who just can't afford apps, or will never pay anyway.

But the worst is when someone is "stealing my time".

I have a Galaxy S speaker damage report today from someone running May7b, a popular pirate date, since May25 actually enforced it's protection after 3 minutes. I pointed him to June 15 on Play and he quickly sent back a log with June 15 indicating a license file.

So I sent him a "special" version to find out whose license file he is using, and it indicates no license, but no license file either.

I don't take any particular joy in Galaxy S speaker damage reports, but sometimes karma works out properly it seems, especially for the people trying to steal my most precious possession: time.

And it's not really outright theft I guess, given that I try to support free users. But it's fraud or false pretenses at a minimum.
[Spirit FM] mikereidis:
Great ! :)

Yes it does work on the SGS2, rooted or un-rooted stock. No

"proper" speaker mode on SGS2/Note on custom non-stock-derived ICS ROMs though.

I try to support every "worthy" phone. That tends to include just about everything capable of FM from Samsung and HTC. Motorola and LG are also desirable but come 3rd and 4th. This matches their market share and my own perceptions of desirability as a normal user or a power user.
[Spirit FM] cccpro:
Then I suppose the raw value is attenuated by 26dB - www[dot]silabs.com/Support%20Documents/TechnicalDocs/Si4708-09_short.pdf

I compared the reception with an Tecsun PL-310 portable, there is clearly a difference between the signal level returned by Spirit and the tuner. For example, a weak signal station, which is still intelligible, had around 22-23dBu on Tecsun and 0 on Spirit, and the sound was almost the same for both devices.

I can do the math by myself, but it would make more sense if the value would be increased by 26dB in the code for the SI4709 chip. 0dBuV should be nothing, not intelligible signal.
[Spirit FM] Jiangyi:
PM sent. Also, I understand what you mean completely, time is extremely important in a job like yours. I mean to purchase Spirit FM once it supports the I9100G, and again, if you need anything else from me, please ask! :)
[Spirit FM] mikereidis:
A longer document says this:

The EVB document shows a scale on a "scope like" screen from 0-80.

I've never seen values over around 65-70 or so, and never values below 0. Yes, it bottoms at 0 and signal is still somewhat listen-able at 0.

The range roughly matches what the most common Broadcom FM chips report, so I'm not particularly inclined to mess with it.

All I could do would be to add or subtract a number, and then scale.

And I hope to add settings at some point for things like seek threshold and "squelch" or "RF mute", and I think it would be best to consistently use values the chip provides.
[Spirit FM] Ozgurce:
Every thing works on Incredible S.

Only one feature I want to is notification area edit.

If you look at the screenshot above you can see the notification area bug.

Is there anyway to you can make it more like other notifications?
[Spirit FM] TheRecRuiT89:
i had installed Paranoid v0.2 custom rom (CM9) and the FM radio was not there on this rom. So i found this great application and i have to say here, it works perfectly and without any problems on Galaxy Note Paranoid v0.2 :)
[Spirit FM] Jinsuke32:
Would love to see some support for my i9100g on cm9.....only thing missing from the rom. :(
[Spirit FM] Madarox:
Please add support for the I9100G variant of the S2 :) Would be great to have spirit FM on cm9/aokp:D
[Spirit FM] Quinny899:
I think we get the point that everyone with a I9100G with CM9 or AOKP want Spirit FM
[Spirit FM] mikereidis:
You mean you want the PS pulled to the right ? Better than left I guess.

OK, done for next release.

I think the Radiotext was pulled left (by default) too. I think by it's nature it might look better centred horizontally and vertical, so I've done that too. That will make it different though, so I'm happy to hear feedback.
[Spirit FM] Quinny899:
UI/Pro feature bug:

Selecting automatic in the orientation pop up wields a toast message saying that 'Pro/Unlocked version is required for this feature' and then the orientation does not become automatic, yet the app states that it does

Also, I don't know if this is supposed to be happening, but the lockscreen control settings don't work
[Spirit FM] Ozgurce:
For statusbar thing. I mean like this.
[Spirit FM] mikereidis:
I don't see that. The toast says "Restart app to apply orientation" or "Requires Unlocked version".

If Menu->About says "Spirit FM Light" and you are running the Unlocked package, that indicates the protection has kicked in.

This should never happen if you have a license file. It will happen 3 minutes after starting the app if you don't have ALL of these:

- Play app installed, working and configured with account of purchase.

- Internet working to access Google license servers.

- Enough "luck" for at least 1 of the 3 packets sent to be responded to with a valid "Licensed" response.

Otherwise, please send a debug log after you see this issue. I've had at least one other report like this, so IMO it's very important to fix.

Especially since there are hacked versions semi-readily available out there, the last thing I want is to cause hassles for legitimate customers.

Only works on a small subset of CM7 ROMs. I haven't figured out the "magic" that some ROMs support yet.

It does something though, so because I've had several questions about this, I've moved it from:

User Interface->Lockscreen Display

to:

Debug->Test CM7 Lckscrn Dspl
[Spirit FM] therion1985:
Sometimes when i open spirit fm the sound is not exists but the working settings are ok,and the signal is ok(around 40)Then i restart the application and the sound is back again.

Also sometimes,when i shut down the spirit fm,are not working the phone speakers,if i make a phone call.The problem solved when i reboot my phone.

i have samsung galaxy s i9000.

settings: audio method Galaxy s ICS

Region greece

sorry for the english
[Spirit FM] Quinny899:
I installed it at school and that happened on the way home. I think the school blocks access to Google's servers, and I'm not on contract. It works now though, thanks for your help
[Spirit FM] mikereidis:
I thought you had a license file from me, which avoids this issue. But I guess you don't. Would you like me to send you one ?

Another unfortunate example of legitimate customers being inconvenienced, while the hackers have worked around it. :(

I've read a good idea I think I'll implement. Instead of limiting the license cache time to 2 weeks, as Google does, I'll make it several months at least, or even permanent, assuming no factory reset, and that the first 2 week period has elapsed.
[Spirit FM] Quinny899:
If you could PM me one, that would be good, or email @ quinny898@gmail.com

Thanks :D
[Spirit FM] mikereidis:
June 15 version ?

Due to further speaker damage reports (after 7 weeks of success) I had to go back to the "safer" audio method, and it has some known problems with audio.

You may avoid these issues by setting the new Debug->Galaxy S to "Better", or even "Danger".

If you were running the previous May25 for a week or more, I think it's unlikely you have to worry about speaker damage. Virtually all reports are from people who just started using the app, or using a more dangerous version or setting. I think only certain hardware revisions are susceptible.

Also, if you enable Debug->Mute kill mediaserver, the whole audio system should be reset on mute or power down. This is a brute force tactic, but can be a usable alternative to rebooting the phone.
[Spirit FM] therion1985:
I have the unlocked june 15 version.I had the new debug to safer.You suggest me to set the new debug to better?
[Spirit FM] mikereidis:
Yes, you can try it, but only if you accept a possibly higher risk of speaker damage.

That said, even "safer" and/or the defaults carries some risk, but if you were running May 25 for a week at least I think the risk is low.

And I'll presume you have a legitimate copy from Play or from me. Copies from "other sources" carry risks of viruses and who knows what else, especially with a root/SU app.
[Spirit FM] therion1985:
I paid 7 euro for this app.I don't want to install old version.You are scaring me with the speakers damage :crying:
[Spirit FM] mikereidis:
It's most important for me to give you the truth, without what we call "sugar coating".

I offer a full refund at anytime to anyone for any or no reason.

If you're concerned, your best option is just to not run the app and you can wait to see if any new reports come in over the next few weeks.

The safer code has been widely available since June 15, over 6.5 days ago. "Normally" I was getting about one report every 6 days, so if 14-21 days go by since the 15th, with no new reports, I think we're good.

That puts the ETA at June 29 - Jul 6. But this also assumes you keep the Galaxy S setting at "Automatic" or "Safer". And assumes you can live with whatever audio glitches you might get.

Glitches are better than damage IMO.

So I do my best to try and be truthful and lay out your choices, from which you can choose:

A - Don't run the app. Get a refund, whatever.

B - Run GB ROMs including stock or stock derived.

C - Accept the risk, assessing whatever I've said.

There's a bunch of information in post 3 of this thread: http://xdaforums.com/showpost.php?p=13380066&postcount=3

As I've said, this problem usually hits people who just started running the app. I suspect it is hardware revision related, but it remains a mysterious issue for almost 10 months now. I think it hits 1-10% of users/devices.

It is confined to Galaxy S, does not happen on stock or stock derived ROMs, CM7, or most GB ROMs.

The problem was solved for 7 weeks, but when I made changes to improve the audio, it returned. Now I've made further changes, which can have bad audio effects sometimes, but seems to be safe or safer.

I think I've put at least 200 hours into trying to solve it, so far. There are no public documents available for these audio drivers, so I pretty much have to figure it out on my own and it's not easy. The source code for, and the registers and capabilities of these chips is quite complex; even though it's a few years old now, but state of the art at the time.

I wish I could damage my own speakers, but my particular phone is immune.

I more or less disabled Galaxy S ICS support at one point (for the free version only), and suffered from a huge amount of email and criticism. So I was "forced" to re-enable it.

I had some warnings in the app, but many don't read them (and some don't understand or don't understand English) and the problem appeared solved, so I removed the specific warning. Perhaps I should re-enable it.
[Spirit FM] Jotvingis:
Hello mike, I can't find ANYWHERE on the Internet Spirit FM Free's install file. Where from could I download that simplest Broadcom version?

(I ask because yours app is the only working FM app in CM9's port for my Galaxy 5.
[Spirit FM] DevilTH:
Look at the first post. There is the free version linked.

Greetings DevilTH.

Gesendet von meinem GT-I5500 mit Tapatalk 2
[Spirit FM] mikereidis:
:)

June 22 Free: http://d-h.st/vd7

(Not connected with my dev-host account as I can't log in for some reason. Via mediafire: http://www.mediafire.com/?dde6xb4pet4b5ls ).

Not too well tested, "hot off the press".

Speaker mode enabled for:

Galaxy SL GT-i9003

Galaxy S2 (and S3 ?)

Galaxy Note

For Galaxy S3, recent releases were reported working on stock ROM. Now reported working on CM9, but you must reboot before you can run a 2nd time. I think if you mute instead of power off, that's a reboot alternative, at the cost of some battery usage.

I tested successfully on Galaxy Note with stock GB ROM, and Galaxy S2 with CM9 Nightly June 4 w/ Suyah 3.3.2 kernel June 13.

There are other mods and fixes I'll document later.
[Spirit FM] Jotvingis:
Oh, thank you.
[Spirit FM] Quinny899:
Hey Mike, how can I move the elements around in the XMLs?

Thanks in advance :)
[Spirit FM] mikereidis:
In theory, in the "normal" way.

In practice, this can create issues with the code, especially for settings/customizations under User Interface and UI Elements.

UI Elements isn't that important though, since likely only 0-2 people are using it.

For example, from main.xml:

<LinearLayout android:id="@+id/mode_btn_1"

android:visibility="gone"

android:layout_weight="1"

android:layout_width="fill_parent"

android:layout_height="0dip"

>

<ImageButton android:id="@+id/btn_mute"

android:layout_weight="1"

android:layout_width="0dip"

android:layout_height="fill_parent"

android:layout_margin="2dip"

android:src="@drawable/ic_media_pause"

/>

<ImageButton android:id="@+id/btn_spkr"

android:layout_weight="1"

android:layout_width="0dip"

android:layout_height="fill_parent"

android:layout_margin="2dip"

android:src="@drawable/ic_lock_silent_mode_off"

/>

...

You could swap the btn_spkr and btn_mute buttons. You could even move things between the "lines", such as "mode_btn_1" and "prst_btn_3". But that misnames them which can result in confusion when enabling/disabling those lines in the User Interface sections.

I created the settings for User Interface and UI Elements so people could customize easily without editing XML files, rebuilding the APK etc. And some things are "package dependent". For example the Light package disables "Preset Buttons 1" because Light only supports 6 presets and 1 preset list. All this can conflict with anyone trying to edit XML files.
[Spirit FM] Quinny899:
I was actually aiming to move the buttons to the right places on that background, would I have to move the LinearLayouts around for that?
[Spirit FM] Quinny899:
I need to go to bed now, so I'll try any more ideas tomorrow
[Spirit FM] mikereidis:
Yes, pretty much.

"Way back when", Spirit screen layout was fixed in XML files, and this provided a relatively nice separation of code from user interface layout. The code and UI layout/XML could be changed relatively independently.

Many apps are like this. Other apps create a UI entirely in Java code, or more commonly with a mixture of code and UI layout/XML, as Spirit does now.

A mixture (or pure code) allows settings (preferences) to modify the UI layout. I provided customizability, as I have little "UI taste" and am happy to let others try things. I even allow relative element sizes to be changed, but not their positions.

In a "perfect world", Google or some commercial company would provide a set of tools that allows full GUI configurability, easily, and without me having to create a library of code that should be in the hands of all developers. I don't want to re-create the wheel, so I'm not sure I'll be doing much more with the UI in the short term at least.

I think you should be able to move things around, as long as the "UI elements" settings aren't used.

The impossible part, without code support, is things like sliders, rotate-able knobs, pinch and zoom etc. I could in future possibly add such things. One could even have, say, 4 different types of frequency controls, and the user could select which are visible on the screen (enabled). Invisible elements are very little bother if you can't see them.

I was really hoping that Google App Inventor (AI) would be usable by "anybody" to create app UIs. My first 1.x versions of Spirit used AI, but it required ridiculous Rube Goldberg contortions to make work.

Google has passed AI to MIT now, they didn't want to "waste" more money on it. AFAICT, it's still pretty lame, except for very basic apps, and/or those with special components already built. Perhaps in future...
[Spirit FM] Quinny899:
I've been doing some work with the layouts today, swapping elements and setting visibilities to "gone" to get everything in the right place. So far I have this:

And I'm aiming to get the elements to about this position:

With the exception of the station name, which will go in place of the "headset, stereo, streaming etc." bit

Which IDs should I be swapping? If I try to swap the station name for the preset list button, I get a force close on open

Thanks :)
[Spirit FM] mikereidis:
By station name do you mean the PI Program ID ? This ? :

<TextView android:id="@+id/call_sign_tv"

And I guess you want to swap with this ? :

<Button android:id="@+id/btn_presets_list"

Textview and Button are not interchange-able. Interestingly, Textview can be clicked like a button, there's an option to search when RT Radiotext is clicked.

But the button looks like a button, based on the theme configured and that the ROM supports. That's the biggest difference for me, on this button at this time.