yashsingh1/xdaforums huggingface dataset:
[Spirit FM] mikereidis:
OK.

You rename the presets with longer words. I usually leave the frequencies and they are shorter and work even on my smallest test phone.

The font size could easily be changed with a UI config option. I'll see about adding a bold option. I thought I found it easier to see from a distance, but I'll test again. The font may affect it, my app just uses the default font style.
[Spirit FM] mikereidis:
EDIT: v1127b: http://www.mediafire.com/file/7kcmha54oa3ba98/Spirit_FM_Radio_v111127b.apk

(The earlier buggy one was http://www.mediafire.com/file/aa323qdr27odxrf/Spirit_FM_Radio_v111127.apk if anyone needs it.)

Fix attempts for just about all issues over last few days.

- Reduce RDS buffer sizes for faster data after frequency change, mostly for AF switching. My HTC Legend went from about 1.6 seconds to 1 second. My Broadcom phones went from 3.5-4 seconds to 2-2.5 seconds.

- Miscellaneous changes for TI and Broadcom chips that may help with many issues such as the Galaxy Mini problems on some ROMs.

- Re-revert changes that should re-enable BCM 4329 devices such as the HTC Desire.

- A fix for frequency set on IDEOS devices.

- Disable all bold text for a test at least.

Huawei audio control commands coming too...
[Spirit FM] dancer_69:
This version doesn't work on X5. I get the mesage:

Error: Power
Fm:SL Sh:1 Su:1 Bt:0 Hc1 H2:0 MO:SLS

and fm doesn't start.

If I change to another method and again to qdsp5v2, then I get a hiss noise only, and the above error if I tried to use power button(which is the only that is clickable)
[Spirit FM] alex1301:
i've got the problem too
[Spirit FM] mikereidis:
Thanks.

Can you try forcing the FM chip type ? Go to Settings->Debug->FM Chip and set it to V4L.
[Spirit FM] papatsonis:
with V4L works ok ;), but after a while it crashes :S
[Spirit FM] mikereidis:
OK...

Can you set frequency OK now ? I found a fix for that.

Nobody has reported if the RSSI signal strength at upper left goes up with a strong station. Even a bit at low levels of 1-3 is good as I wasn't sure what values to expect.

Seek still won't work. I can add that soon, but it's tricky to do without hardware.
[Spirit FM] dancer_69:
After crash/reboot, tried again and appears the same error and no sound. Tried to change again fm to automatic from settings/debug and I get signal again, but again get the crash and reboot. Before reboot the main spirit fm screen appear but doesn' t respond to anything, so cannot test frequencies etc.

With 26/11 version I could change frequencies and add stations on memory slots, but seeking don't work.
[Spirit FM] mikereidis:
Here are the adb comands that might reduce volume:

These may reduce the volume to 20% or so:

adb shell /data/data/com.mikersmicros.fm/files/ssd 4 3 33 5

For the rest I'll omit the "adb shell" part, as if running from a terminal:

/data/data/com.mikersmicros.fm/files/ssd 4 3 18 5

/data/data/com.mikersmicros.fm/files/ssd 4 3 20 5

/data/data/com.mikersmicros.fm/files/ssd 4 3 21 5

/data/data/com.mikersmicros.fm/files/ssd 4 3 34 5

These write to ALSA registers. I may have some luck with the more native sound driver too.

I'll post another version of my app in a few minutes that shouldn't require the chip type forcing.
[Spirit FM] mikereidis:
V111127b:

http://www.mediafire.com/file/7kcmha54oa3ba98/Spirit_FM_Radio_v111127b.apk

Try to send me debug logs for the crashing. Or run an app to collect the logcat if my app is crashing and can't send the log. This one is good: https://market.android.com/details?id=org.jtb.alogcat

I'm done for my "night" for the next 12 hours.

Happy Thanksgiving Weekend for those celebrating. We "Canucks" had ours a few weeks back.
[Spirit FM] dancer_69:
Just tried, immediately crash and reboot..

E/fm_hrdw ( 3134): enab_disab disable dev_id: 6 error errno: 1
E/fm_hrdw ( 3134): enab_disab enable dev_id: 7 error errno: 1

I'll try again after do clear data
[Spirit FM] mikereidis:
This app is good for getting the full logs during a crash: https://market.android.com/details?id=org.jtb.alogcat

I don't think those errors are causing or really associated with the crashing, but who knows.

If a new install after removing my app (or clearing all it's data) doesn't crash at startup, that may indicate the Huawei audio method is associated with the crashing. (Since the default is CyanogenMod.)
[Spirit FM] dancer_69:
Same results, after I choose the audio method, fm works but stuck and crash.

I'm using logcat from adb shell, I saw the description of alogcat and doesn't seem to use something else, except that is android app.

For Ideos X5 version 26/11 is the best for now. The adb commands for volume handling you mentioned before will work on that version?
[Spirit FM] mikereidis:
Yes the adb commands will work, going back weeks at least. They are just to test ways to reduce the volume from full.

So, the crash happens AFTER setting the audio method... The driver calls may need to be different than standard qdsp5v2. I'll see what I can find.
[Spirit FM] sanpsa:
Installed the 111127b version, X5 with miui. With qdsp5v2 method it indeed works :eek: Balance is way off and cant control volume. Nice work :)
[Spirit FM] denzel09:
Hi mik i have send you some email with some debug and logcat from 3nov version, last in this moment on market. So now you can say to all that 3nov version works for me well on cyano rom by squadzone. ;-)

:screwy:

:)

Inviato dal mio GT-S5570 usando Tapatalk
[Spirit FM] cos68:
Hi Mike

Thanks for the update.

Volume is working perfect again!

I hate to say it, but I am afraid I have another problem with this release. This time it is the RDS function, which is causing problems. The problem is, that if I start your application while it is tuned to a station transmitting RDS signal, then I see the station name and program type as expected. But if I search for a station with the arrows and it finds a station with RDS signal, then no station name and program type is displayed. If I then leave your application by pressing home (still running in the background) and then go back into you application, then the station name is displayed just fine. It seems like the RDS station ID is not updated when searching for new stations?!

This is the same for both my Desire HD and my Incredible S.

Sorry for only reporting errors. Otherwise your application is working GREAT! :)

Thanks

Claus
[Spirit FM] mikereidis:
Great !

So it doesn't crash for you ? Even after restarting the app ?

If not then I guess the crashing is specific to the CM ROM. perhaps in the kernel.
[Spirit FM] mikereidis:
Hi. Good, no surprise.

No need to be sorry. I'd prefer there weren't any but I WANT to hear about any bugs or other issues.

That's why I release test versions here, for the more technical people, until the code seems stable. Then a new Market version, for everyone else, about once a month. There should be a new Market version soon.

Yes, I was seeing the same thing. It shouldn't be too hard to track down.
[Spirit FM] dancer_69:
I tried all adb commands, but there wasn't any change on volume.
[Spirit FM] mikereidis:
Copied from another thread, re IDEOS devices: Thanks for all the reports.

If anyone is NOT having freezing or crashing, please report which ROM you are using.

But I REALLY need to see logs captured while a freeze or crash occurs and nobody has sent me any yet.

Remember that I don't have one of these phones, so for low level hardware specific stuff like this, I consider it a "minor miracle" to have gotten this far.

Of course hard work and skills help too... :)

If you have a crash or a freeze, and can get back into my app without rebooting the phone, you can send me logs with Menu->Help->EM Logs. That MIGHT be able to catch the problem, going back into the log history buffer.

It may be better to run a logcat app like this: https://market.android.com/details?id=org.jtb.alogcat . Start it before my app and hopefully after the problem, there will be log files you can send me.

Best would be someone with technical skills who can run ADB from a connected PC to a phone with a rooted shell and start these commands:

# These are just comments: In first window:

adb logcat > logcat.txt

# In another window:

adb shell cat /proc/kmsg > kmsg.txt

# Now start the app and wait for the problem, kill both commands with Ctrl-C (or they have already died) and run:

adb shell dmesg > dmesg.txt

# Then send me the logcat.txt, kmesg.txt and dmesg.txt files

Thanks !
[Spirit FM] edowar:
Hi Mike....your adb command works for my device huawei x6. And also able change to speaker mode..and sound much better hear in speaker mode :D. Btw I will send log to you asap.
[Spirit FM] mikereidis:
GT-s5570:

You were first to report here and I didn't catch your post, sorry.

Can you try going to Settings and enabling Debug->BCM BT Headset ? Then power-cycle the app.

If that doesn't help, shut the app/FM off and start Bluetooth and try again. A reboot might help too.

I don't know if anyone has tried the CM FM app from the subpsyke and sfortier CM ROM for GT-i5500 . It would be useful to know if it had the same problem. You can download it here: http://www.mediafire.com/file/6zrz43jqwd9gnzd/FM.apk

From the reports on this thread, everyone is running the tj_style CM ROM, presumably the latest. I presume you all have enabled Debug->BCM 20780 and my logs show that. If nothing else works, you could try disabling BCM 20780 and rebooting the phone, then start with Bluetooth off.

One last idea, once you have enabled Debug->BCM BT Headset, is to try with a Bluetooth headset, starting the app after the headset has been paired AND connected (I go into Android Settings for connecting.)

denzel09 is not seeing the problem, but you (giri_189), newxda85 and roofrider are.

The problem is that only buzzing is heard. I don't think anyone has said if RSSI signal strength or seek are working.

The september 26 version works OK. Somewhere around October 4, all releases since then are not working for most.

The last market version, November 3 is the one working for denzel09.

The only problem visible in the logs are an HCI error 12 (Command disallowed) for writes to Broadcom FM register 9. This register is used to initiate a frequency set or a seek start or stop tuning operation.

I have no idea why that error happens but it appears related as denzel09's log doesn't show it.

If an old version of my app works, then I'm sure I'll be able to fix this, with enough patience and effort all around.
[Spirit FM] mikereidis:
Woohoo ! Great !

Now the X5 owners will be jealous. :)

So there may be some hardware difference or a software bug on the X5 perhaps....

I can use all the info you can give on your ROM and device. Is the app running stable ?
[Spirit FM] mikereidis:
Thanks ! Looking at your log, you aren't having the same HCI error that others are having. So it appears related.

For your bug where the audio is muted, you say you "click on setting" to fix it. Do you mean you select Menu->Settings ? Or press some other buttons ?

I also see you are using the CyanogenModNew audio method in the last Market version Nov 3. I don't know if that might be helping you, or even causing your mute bug.
[Spirit FM] denzel09:
1) yes, menu > setting. But problem solve also click other buttons

2) mute bug w all cyanogenmod audio method

3) when i open application, for example, i have mute bug. If i click on setting or other, mute bug disappear. ;)

It s not big problem for me. App works very well buddy :)

Inviato dal mio GT-S5570 usando Tapatalk
[Spirit FM] denzel09:
Mike how is it possible that hci error not on all mini w same rom? Do you have control logcat from who say that dont work ?
[Spirit FM] mikereidis:
Yes. Both newxda85 and roofrider sent me logs, and they both showed the same error in the same place, and yours doesn't.

There are often subtle differences between hardware revisions, often to fix bugs on the older version.

The BCM 20780 seems a pretty new or rare FM chip. Only the Galaxy 5 series seem to have it, that I know.

One of the silliest, most infuriating things with this chip was finding out how to enable audio. It took a long time and a lot of work, as you might recall, and much of that was to find the one "bit", the needle in the haystack.

It required setting the "RF mute" bit, which lowers volume when signal is low. Without this, it doesn't work, but just on this one Broadcom 20780 chip.
[Spirit FM] denzel09:
Understand. so i am lucky with that "revision"? but about mute bug it will be a fix or this will can other problems?
[Spirit FM] cowsgo:
Edowar, I am using your cm7 rom and all I can get is static out of the app which is more than what I was able to get before. I downloaded the latest spirit app that Mike put out. What are you settings so I can match them and see if I can get some stations

Thanks
[Spirit FM] edowar:
In order to works, first input plugin headset, then go to setting audio then choose qdsp5v2 method.

And get speaker works, go to debug then choose HW Mute Off.
[Spirit FM] mikereidis:
Menu -> Settings -> Debug -> HW Mute Off ??

That's very interesting. I added that option for testing, but haven't found a general use for it yet.

It just disables the hardware specific (V4L in this case) Mute/Unmute function.

In theory it should never be needed, as unmute should undo any mute, but if it makes the speaker work that's a great clue.
[Spirit FM] mikereidis:
Could be. You have the exact same ROM as the others ?

Is it possible you have a different radio/baseband ? Do you have the same carrier in the same country ? There are many possible differences.

If you can send me a log after startup, then press menu -? settings, or whatever you do to start audio, I can try to figure out your problem, and I'd really like to figure out that little bug you have.
[Spirit FM] mikereidis:
From email:

Device: Motorola XT701

ROM: CM7

Problem: Able to get signal, but no sound. XT701 stock rom has a built-in FM radio app, but they are not able to port it to CM7.

---

Did you try setting Menu->Settings->Audio->Audio Method to Motorola or Motorola2 ? You could try other audio methods, but those are the 2 most likely to work.

---

I tried all of them but still no sound.

I got a "Aud?" near the signal bar in your app

---

I've never had a Motorola device working unless it uses the Motorola audio libraries, the the CM libraries if they support FM audio routes.

There IS a /dev/snd/mixer device that might be usable to enable FM audio.

I will try to look into that and hopefully at some point have a solution.
[Spirit FM] mikereidis:
Re: Samsung Galaxy Mini GT-s5570:

I need more information before I can put further work into trying to fix this.

Chances are much better if I know exactly which release stopped working.

This zip file:

http://www.mediafire.com/file/ed3bnepc59x839j/Spirit_FM_Radio_Sept26_to_Oct6.zip

Contains these versions:

Spirit_FM_Radio_v110926.apk

Spirit_FM_Radio_v110930.apk

Spirit_FM_Radio_v111001.apk

Spirit_FM_Radio_v111004.apk

Spirit_FM_Radio_v111005.apk

Spirit_FM_Radio_v111006.apk

Start with Sept 26 and verify it works. Then update to:

Sep 30

Oct 1

Oct 4

Oct 5

Oct 6

I presume one of these will stop working. It may be good to continue at that point, just to see if any subsequent release works.

Then go back to the last working release and re-test it to ensure it still works. Perhaps a reboot would help.

Alternatively, if someone sent me a device for at least a week, I could likely solve this. Doesn't matter if it's banged up with a half broken screen, as long as it still works otherwise.
[Spirit FM] denzel09:
1) i use squadzone rom CYANOGEN

Last) ok, i will send you a log

My baseband: S5570XWKS2

Inviato dal mio GT-S5570 usando Tapatalk
[Spirit FM] roofrider:
Thanks, it'll take sometime for me test and report...lil busy. U can concentrate on other devices...in the meantime :)
[Spirit FM] fishskin:
Thanks Mike

I'll try to find out what library the ROM use.
[Spirit FM] mikereidis:
I think there are CM ROMs for similar Motorola devices that support the CM FM app.

Perhaps the CM dev for your phone could use those other libraries.

I see you posted here with a new registration. Good; They previously prevented posting here by new users in a "Dev forum" and it was annoying.
[Spirit FM] mikereidis:
:)

That I'm doing.

Currently trying to figure out the Broadcom proprietary FM API. Therein lie the keys to FM on MANY stock phones and hopefully better income for this "poor dev"...
[Spirit FM] cowsgo:
Edowar, Thank you I have the app getting stations, but now I cant control the volume. I have tried all the things that Mike has suggested in this thread but with no luck. Also once I set it to qdsp5v2 and I close out of the app I cannot reopen it, it locks everytime and I have reset the data before I can use it again. Was wondering in you are having this issues as well?
[Spirit FM] alex1301:
hi mikereidis

the answer of your request in the PM: i've got an Ideos X5 with CM7 111128
[Spirit FM] roofrider:
Mike,

Every version u included in that zip works just fine...except for a weird pause unpause issue...I think that comes later.

But everything in that zip works.
[Spirit FM] edowar:
Hi Mike,

for make sure I did test again, and speaker out really works :D

Yes indeed, I have that issues too.
[Spirit FM] mikereidis:
From the other thread: It looks like it crashes in the audio switching. Since it works, more or less, the first time the app is run, my guess would be some bug in the audio driver.

But I'll see what I can find out, thanks...
[Spirit FM] mikereidis:
Thanks, so somehow the version number where it stopped working was misunderstood.

I heard the problem started at Oct 3, but there was only Oct 1 and 4. Maybe it was the Nov 3 Market release.

If anyone wants to test here's a repost of Oct 17: http://www.mediafire.com/file/e42ow33yq2kif1g/Spirit_FM_Radio_v111017.apk

And Oct 27: http://www.mediafire.com/file/jhb7pi3s5k5sw3s/Spirit_FM_Radio_v111027.apk

The next was the Nov 3 market release that it seems most are saying is broken.
[Spirit FM] mikereidis:
Status/Plans:

I think I should do a feature freeze now for December. I have documentation, design, planning and personal time to attend to.

I'm also thinking of making my source code open via GPLv2.

I'm wondering if I should support the ST-Ericcson Android FM API. It's an obvious API candidate, despite the lack of news and the project allegedly moving to India...

Infuriatingly the code and comments are no longer available since https://review.source.android.com/ has been down since the kernel.org attack. Really Google ? You can't get servers back up and running in over 2 months ?

I'm hoping that an open source move will increase the amount of community support. One person can't do it all, and there's so much that could be done.

I'd love to see integration with streaming radio, similar to the AF Alternative Frequency feature. Easy access to websites of stations, or phone numbers, or song lyrics or whatever you can imagine.

I would expect to continue to offer exclusive features, and support, in my paid/unlocker app, although it might eventually stop being an unlocker for the base app.

I'd like to think that nobody who has purchased the unlocker would see this as a bad thing, but as a good thing for the continued advancement of the project. A similar FM project was done for Win Mobile but the developer has disappeared and so has his source code. Open source lives on.

If I'm unable to reach my "meagre income target" with the sales of apps, I will seek sponsorships or contract opportunities, preferably related. A few such opportunities may be forthcoming and at least one has the potential to be very interesting and "symbiotic" I think.

It's pretty tough trying to generate income from an Android app such as this. I've tried several pricing experiments over the last few months, and the results seem somewhat inconclusive but do indicate $400 per month is my peak at this point.

Based on 80 hour weeks, that's around 12% of the minimum wage legislated here. Time, features and stock phone support can/will improve this but who knows how fast. If I could support stock phones, and multiply sales by 4, AND drop to 40 hour weeks, I could make minimum wage. Salary or contract, developers here can make 5 - 10 times as much as minimum wage, so even a pretty good scenario for the next year is not that good.

Corporations may be "psychotic" and profit focused by design, but they can pay well, LOL.

I had at least 2 recent "sponsorships" (ie "donations") of well beyond the app price, and that's wonderful, thanks all. Perhaps open sourcing would increase the "sponsorship" rate. I'm not really a charity, so dislike the term "donation".

Any and all thoughts are welcome. Thanks for reading...
[Spirit FM] mikereidis:
v November 30 now on the Market: https://market.android.com/details?id=com.mikersmicros.fm

- Very minimal changes from v111127b.

No major new bugs in 3 days = New market release. :)
[Spirit FM] denzel09:
Previous bug still is here for me. If i click on setting option sound come back.

In this version i hear a big big big background noise, at least for me.

And initially the volume was so big that i was going deaf.

btw too many changes buddy ..

---------- Post added at 03:19 PM ---------- Previous post was at 02:35 PM ----------

Playing on setting seems that noise is attenuated ..
[Spirit FM] VerizonKoolaid:
woops

I read FM RDS as RDS-TCM

Traffic data by FM
[Spirit FM] sanpsa:
Got some logs from X5 with official 2.3.5

Newest from market just freezes after few seconds...

Cant get kmsg because its permissions denied and dmesg after it has frozen...
[Spirit FM] ruben00:
Mike, how hard would it be to make it work on the stock firmware? If we take the miui apk and your app will that make it work on a stock sg2 (and hopefully stock sg2 skyrocket)?
[Spirit FM] mikereidis:
I've looked briefly at some of the traffic data I can get locally, but have no immediate plans for support. Perhaps open sourcing can help, if someone creates a decoder.

AFAIR, it requires some decoding and not just ASCII display (?). There are more modern solutions I think, such as Google maps traffic, although they require a data connection.

Looking at a mobile phone display while driving may not be the best idea, although not so bad when stopped I guess.
[Spirit FM] mikereidis:
Last I recall, the only problem on a stock and rooted ROM is lack of audio.

If the Samsung and Samsung2 audio methods don't work, then a 3rd option is needed. If I examine the stock FM app for Galaxy S2, I should be able to determine what is needed.

So if someone pointed me to or "loaned" me copies of the APK and ODEX, and perhaps the contents of /system/framework I could see. And yes, that might technically be a copyright violation and technically frowned upon here (but often tolerated in cases such as this), I don't think Samsung would be overly concerned.

The MIUI FM app, and mine, both rely on FM specific audio routing code in the audio libraries. Without those libraries, or some other possible workaround, no sound is possible.

The stock ROM has it's own FM specific audio routing code in the audio libraries. We just need to figure out how to use it. It's a shame that most manufacturers have their own proprietary methods. If there were Google blessed or specified methods, this wouldn't be so much of a problem.
[Spirit FM] ruben00:
Which sgs2 comes with the FM app? I will soon be borrowing my friends international sgs2 so I can take a the files from there
[Spirit FM] oskaratk:
Samsung GT-P7510

Hi everbody,

I was searching this thread for info about the Samsung Galaxy Tab GT-P7510 .. no luck

Device is rooted, original rom

Trying to run Spirit ( Hats off to Mike )

The startup debug info is FM:BC Sh:1 Su:1 Bt:0 Ht:0 H2:0 Mo:BCH SD Hv:5 Ma:15 BC

RDS sometimes is 0, sometimes -128, however the values are not changing.

Compared to my HTC Sensation, startup takes way longer, the tab seems to be less responsive when Spirit is running

Any hints ?

Thanks

Oskar