yashsingh1/xdaforums huggingface dataset:
[Spirit FM] mikereidis:
Only a few people have showed up here with an interest in RSSI units in the last 3+ years. I removed RSSI polling from Spirit2 due to CPU usage and I don't think anyone has complained, LOL.

V4L "standard" doesn't apply here. I've seen other V4L drivers return values from 0 - 65535 ar "full strength".

A spec sheet from the leaked cache of QC docs indicates WCN3660 has FM sensitivity of -2.5 dBuV for audio. RDS w/ 5% error rate requires 15-20 dBuV. Maybe that's somewhere around 40-80 RSSI shown in Spirit.

The QC V4L signal value reported ranges from about 150 to 205. Two's complement of those are -106 to -51.

Spirit reports: (signal - 150) * 1.5

The kernel open source V4L drivers don't explain the number and I don't think the Qualcomm FM app does either.

So, I dunno...
[Spirit FM] mikereidis:
500 turns into the value 320. Try 320. Then try 640, 960, 1280, 2560 and 3840.

Tx won't be affected. Reception low when set to External is a good thing. That means the "Internal Antenna" pin is being used for FM, which is the only FM antenna pin (of 2) that works for Tx.

Xperia T (now $200 or less new on Ebay) was the first I saw this on and I guess it's continuing, at least on some Sony's and likely all since the "Bond phone". Had to give Bond FM Tx for 1960's style Fm Tx "bugs", LOL.

Fm Rx/Tx perspective is opposite on the audio chip. To receive FM digital audio, Spirit enables "MultiMedia2 Mixer INTERNAL_FM_TX". I use MultiMedia2 for the 2nd port to allow possible simultaneous microphone usage on the 1st port; don't think I've ever tested it though.

So most likely you'll want to enable "INTERNAL_FM_RX Audio Mixer MultiMedia1" while music is playing; I don't recall if you need to set Spirit Audio-> Method to "None" or similar and/or turn off Silent Loop or whatever. You can also adjust "Internal FM RX Volume" from 0 to 8192 or so; I see 2047 as default on my OneXL, but the much newer MotoG defaults to 0.

Play a 48K sample rate music file if possible. Uncompressed WAV or FLAC may be better than MP3.

Sounds so simple. Looking forward to hearing you say "It works !!" :) But I'm too used to the opposite...

Unlike the GS3 mini amd Xperia P/U/Sola/Go Novathor, Qualcomm chips have been very popular the last few years. So I don't mind spending some time researching it. I have the Xperia P and I know it does digital audio, but it's just not worth the time for Spirit2/digital audio for the few Sony Novathor customers I have or could gain. I only recently rooted it, and only to test the other app I'm working on.

If all or most Xperia devices since the Xperia T can transmit FM, that would be an incredibly interesting find, although in 2014 might not generate TOO much excitement. People used to ask about FM Tx ALL the time, now very little. Main usage would be in cars, where wires give better audio quality and many good car audio systems (as well as Android) support Bluetooth well now.

I had this FM Tx hypothesis when I added the Xperia T adjustment but never followed up and thought it might be just the T, or a few not so popular models. If most recent Sony's can FM Tx it could be worth it to officially support Tx as a Spirit feature, or maybe even a separate app. I think root would be required, but there's a small chance not.
[Spirit FM] orlanddon:
If I understood correctly, then spirit shouldn't show values less than 0 and above than 83.That's definitely not my case.

Anyway, thank you for useful info. -2.5 dBuV is really nice sensitivity comparable to Sony xdr f1hd radio.
[Spirit FM] raffe:
The free FM app NextRadio ( https://play.google.com/store/apps/details?id=com.nextradioapp.nextradio ) has support for Galaxy S5 according to http://nextradioapp.com/supported-devices/ (if you have Sprint.com, Virgin Mobile, or Boost Mobile).

In http://nextradioapp.com/whynotme/ they say
[Spirit FM] Kess78:
Well Mike, it works !!!!! I'm actually listening to the song of my phone on my radio!!!! INTERNAL_FM_RX Audio Mixer MultiMedia1 did the trick !

Changing INTERNAL RX VOLUME in the ALSA mixer app doesn't apply the changes but I see the values changing when I change the volume on the phone. At max volume the value is set to 2000, which is not very loud but still ok.

Thanks a lot !
[Spirit FM] mikereidis:
Cool ! :)

I'll see about setting that control in Spirit.
[Spirit FM] mikereidis:
The "signal" value is one byte, treated by my code as unsigned and range from 0 - 255.

So " (signal - 150) * 1.5" could hypothetically range from:

(0 - 150) * 1.5 = -225

to:

(255-150) * 1.5 = 157

I tend to see values displayed by Spirit1 between 0 and 83 or so at most. Spirit2 takes this number and multiplies by 16 to try and range RSSI from 0 - 1000. Then the Spirit2 UI divides by 10 for a range of 0 - 100. Spirit2 RSSI polling is now disabled, but can still be seen sometimes when the UI is brought up.

I've been thinking that "signal" may be in units of dBv, ranging from -105 to -50 or so. I guess that would be -45 to +10 dBmV or 15 to 70 dBuV. I'm not too familiar with these units; 70 dBuV seems possible on the high end but 15 is a big difference from sensitivity of -2.5 dBuV.
[Spirit FM] mikereidis:
The only reason Sprint is asking OEMs to enable FM access is because Sprint is being paid millions of dollars every year by US broadcasters to do so. Before Emmis/NextRadio and US FM broiadcsters struck a deal with Sprint, Sprint was among all the other "bad guy" US carriers.

Prior to that, International models of high end Galaxys had FM, while US/North American variants did not.

It's a bit surreal to now see the only high end Galaxys with FM are US Sprint models. International variants don't have it anymore and Samsung claims this is due to lack of demand.
[Spirit FM] Kess78:
Thanks, could you also set SLIMBUS_0_RX Audio Mixer Multimédia1 to off? This will stop the sound in the headphones which is still playing while it transmits even though I notice it goes to on again everytime I press pause and play in the media player. Because as the volume has to be max the headphones are also full blast which is not good for them I think...

And do you think there is a way to increase the power?

Thanks
[Spirit FM] mustasusi:
Yes, better off with Note3 for now.

In fact, the NOTE series has always rung my bell. I considered it as an elite class. I believe the fo(u)rth coming Note4 might have no analog radio as well, excluding the Sprint variant which gives me a new hope to keep up with Samsung legacy.

I can't keep away from Samsung for too long, *unless HTC starts selling REMOVABLE battery cells. My curiosity about the Sprint Note 3 is so extreme that I felt like I have to try and figure out, disregard the $400~ (hopefully including taxes and) and the possibility it might be carrier locked (maybe I'll have some good news about it as well). I would go for it the next month or two, in case I have to much expenses, not that I'm too suffering with HTC in the meantime. If I knew about this variant exclusiveness November last year, I'd definitely grab one over the HTC. I guess it's never too late...
[Spirit FM] paulle:
spirit with sony xperia z1c and CM11

Will Spirit wor with a sony xperia z1c and CM11 installed ? Any experiences or hints ?

edit:

tried it (very little time (less than 15min)) because when you have to pay for the app. Result: Spirit1 working (buyed it), Spirit2 not working.
[Spirit FM] mikereidis:
I guess.

Code here indicates there may be 7 Tx power levels: https://android.googlesource.com/kernel/msm/+/android-msm-flo-3.4-jb-mr2/include/media/radio-iris.h

But that's at the lower level HCI API, which I've never been able to access. The V4L driver does not have such control, AFAICT.

My guess is that a 3 volt chip could max out at 1 volt RMS, and a 50 ohm impedance means about 20 milliwatts max. That's well below the common unlicensed limit of 100 mw, so my guess is that the 20 mw or so max is the default.

We tried to change power on the NovaThor chip and I think we found the default was maximum power.
[Spirit FM] mikereidis:
Thanks for your support. :)

I cancel any order on request within a reasonable time period (less than a year), so no worries about 15 minutes.

In fact, Google now allows any order to be cancelled if you click in the right places, and the dev still gets paid, but I imagine Google will be unhappy if that happens too often.

Z1c is Z1 Compact ? Yes, so far all 2013+ Sony's work with Spiriit1, but some don't on Spirit2, and I hope to fix that. I can cancel any Spirit1 order to change to Spirit2 in future once that's done.
[Spirit FM] paulle:
yes z1c is Z1 Compact. Excuse me was lazy for typing. "Google now allows any order to be cancelled if you click in the right places, and the dev still gets paid" that's interesting (I'm not a dev only a noob), but there are these places? Because with an app like yours I would like to have an hour or more to try it.
[Spirit FM] mikereidis:
Here's an article about beyond 15 minute refunds: http://www.cnet.com/how-to/get-a-refund-on-apps-in-google-play-after-15-minutes/

Best to contact the dev first though. I cancel on request. But while my eye was injured someone's requests went into my Spam folder and I didn't see for 3+ weeks. In such a case, with no response, you can ask Google. Also in cases where an app is a clear scam or any other legit reason.

Hopefully good news about Sony devices tonight I think. :)

I realized tonight that I only set the FM chip to use the Sony Internal antenna for a few Sony models: LT29*, LT30*, MINT & HAYA.

I've changed it so that all Sony's use Internal Antenna pin now. I'm guessing no reception was the main problem w/ Spirit2 not working on other Sony's. People often just report "no audio" even when it's a tuner related issue.
[Spirit FM] Kess78:
Ok the power is enough for my use anyway :) I had a little mp3 that could transmit to more than 1 km so I thought it could have more power.

Too bad I don't have the skills to build an app and play with the api a bit. It was easier on the Sola with the stock api I managed to transmit RDS :) I'll just stick with what's works now it does perfectly fine.

And BTW the trick to disable soft mute worked on spirit 2 thanks. Are you planning to add multiple preset list and the option to shut down the radio when the headset is pulled off?
[Spirit FM] mikereidis:
Wow, 1 km is a lot if it was 100 mw or less.

Well I'm thinking (haven't looked at or though about the Tx code lately), and Spirit1 does transmit with the proposed Sony/STE API. So I'm finding it unexpected that there must be a Tx library for the Qualcomm chip on that phone. There was only Rx library in the days of Xperia T. Have you tried your RDS Tx app on this phone ?

Yeah, headset pull to Off is something I can do. Preset lists, I guess, but I'm not sure many people need that.

Right now I'm trying to get the speaker mode issues resolved.
[Spirit FM] ffxx68:
Hi,

kindy asking for a review of logcat (grep by "fm_"), here: http://pastebin.com/3xxSn7QA

I can't tune in any station, but wondering it's a H/W or S/W limitation here...

It's the first time I use the app on my device (an "almost custom" one, using the bcm 4329 chip: AOSP porting details at: https://groups.google.com/forum/#!forum/renesas-emev-osp ).

I can see recurring error messages (even when no action is performed), like below:

...
E/fm_hrdw ( 1783): hci_cmd error res_len: -203 hci_err: 254 Unknown HCI Error
D/fm_hrdw ( 1783): d0 55 1d 2a 98 4c 7a fe 96 00 20 1d a8 91 7a 40
D/fm_hrdw ( 1783): hci_cmd failed command ogf: 0x3f ocf: 0x15 cmd_len: 11 res_max: 252
D/fm_hrdw ( 1783): 00 00 00 00 00 00 00 00 12 01 02
E/fm_hrdw ( 1783): reg_get hci_cmd error: 0 hci error: 254 Unknown HCI Error reg: 0x12 val: 0x1d20
V/AudioPolicyManagerBase( 74): getDeviceForStrategy() from cache strategy 0, device 4
D/fm_hrdw ( 1783): hcitool_get waitpid exited status: 1
...

thanks

Fabio
[Spirit FM] amtomio2004:
G2 D802

Can you solve the trouble of listening Spirit FM in G2 AOSP?
[Spirit FM] mervluk:
Is that anything to do with the static only occasionally, cured if I run the stock fm (with no audio on my former rom) then return to Spirit 2.? That's my only issue on a Z running either 4.3 or 4.4 modified stock ROMs. I always thought Spirit should work on latest Sony's whose stock ROMs are basically AOSP with their bloatware added! So good news indeed.
[Spirit FM] mikereidis:
This is Android 2.3 ?

Email me mikereidis@gmail.com and I can send a newer version. The free version is about 9 months old now.

Spirit needs HCI Access to the BCM chip. On Android 2.3 the ways that work are:

- With Bluetooth off, via the HCI Uart directly. Usually at /dev/ttyHS0 but I think others can be detected. Should work in any Android version.

- With BT on, via the kernel BT socket. I think this stopped working in Android 4.0.

- With BT on, via the command line utility hcitool. If you get a good response from "hcitool cmd 4 1" then it should work. I think this stopped working in Android 4.1.

It might help to force a method. Set Menu-> Settings-> Debug-> HCI Access to one of these:

- UART

- BT Socket

- Ext hcitool

Sometimes "Int hcitool" works, with the internal copy, when there is no native hcitool.

Bluedroid shim only works on later Android 4.1 or 4.2+ I think.
[Spirit FM] mikereidis:
Occasionally ? Maybe.

Spirit's default is not to touch the antenna control at all. That way it should be set to whatever the kernel driver or framework libraries set it to, or normal power on default.

By not touching it at all, it may remain in whatever the last state was.
[Spirit FM] mikereidis:
Saved your post for a new page. :)

I hope so.

The latest G2 info is in "lucky" post 777 of the Spirit2 thread: http://xdaforums.com/showpost.php?p=53636291&postcount=777

Quick answer is that once I get my G2 restored from "Security Error", I will try poking the GPIO 69 at /sys/class/gpio/ and see if that's a usable solution.

I think maybe I should close the Spirit2 thread and redirect discussion for both 1 and 2 to the original 1 thread. Feedback is welcome.
[Spirit FM] Kess78:
The app didn't work (force close) as well as Spirit in STE AFM TX (No FM accessible).

Indeed speaker mode doesn't work on Spirit 2. When I activate it and then change the volume it's the incall volume which is controlled. It works fine in Spirit 1 though.
[Spirit FM] mikereidis:
I don't understand then. How do you get your phone transmitting ?

Until you get my recent updates, one trick is to use the speaker icon in Spirit2 and adjust media volume from there. Or when volume control popup is on screen, select the gear at right to open the other volumes and adjust media.
[Spirit FM] mikereidis:
If anyone can help with my aggravating G2 issues, please see this thread I opened: http://xdaforums.com/showthread.php?t=2794130

At this point I have Sprint LS980 Stock KK ZVC loaded and working, rooted and w/ TWRP 2.7.0.

But for some crazy reason, flashing Slimkat or CM11 and wiping results in a bootloop.

I hate LG. I hate LG. I hate LG....
[Spirit FM] Kess78:
For the Sola I was using STE AFM Tx or my app which used the same API. For the Z1C I use QC V4L and check qvom Tx (warning). Using STE AFM TX doesn't work but using the Rx API works.

Yes the trick works :) the volume was at 0 and as I couldn't adjust it I thought speaker more wasn't working...
[Spirit FM] mikereidis:
Oh yeah, I forgot about the Debug-> QCom Tx setting, LOL. Spirit1 is in maintenance mode w/ no new features expected.

Now my head is wrapped around the Spirit2 code, when it's not in the new AudioTricks/VolumeTricks code (which is another way to control un-controllable volumes).
[Spirit FM] Kess78:
Ok, it would have been cool to have a fm transmit app thought...
[Spirit FM] ffxx68:
Following your suggestion, I sent you an email to get the newer version. Thanks!

My AOSP version is JB 4.1.2, but it's sitting on top of a relatively older kernel (2.6.35.7).

I have tried the "UART" and "BT shim" modes and seems like I'm getting no more those errors, but a message:

Error: No FM accessible

SU: 1 Fm:BC2 Su:0 Bt:0 Ht:1 Mo:BCU

Pushing the new "logcat | grep fm_" onto http://pastebin.com/WYWA2Lev
[Spirit FM] rubend447:
Where i download the newest version of it ?

My phone Gt-I8160 With Cm11 Developed by team canjica

My works :i YouTube Chanel called rubend447. ;D

If u want somethink : ask me, no problem.
[Spirit FM] Lagkage:
On Google Play, but I am not sure if it will work on your phone and ROM.
[Spirit FM] rubend447:
The phone has the harware and the rom is cm 11(4.4.4) i think that it will works . thanks

My phone Gt-I8160 With Cm11 Developed by team canjica

My works :i YouTube Chanel called rubend447 ;D

If u want somethink : ask me, no problem.
[Spirit FM] mikereidis:
I'm thinking about an FM transmit app. From what you say, it works already, though it could use a few tweaks.

And if it works on most Sony's made in the last few years, then there could be a reasonable size market that isn't too cost sensitive.
[Spirit FM] mikereidis:
Android ONE = Google FM Radio ?? !!

Android ONE = Google FM Radio ?? !!

Today may be the first time in 4 years that a Google executive put the words FM and Radio next to each other.

Android ONE may be under $100 and intended for "emerging markets".

And "emerging markets" pretty much demand FM radio since they don't have widespread connectivity and/or wealth for streaming via data. So it makes absolute sense to include FM or the phones will flop.

So,... Interesting... Maybe we'll see a real live Google built FM radio app soon. Maybe on Google Auto too.

I see no reason to believe that Google will start supporting FM in general, but if the source code is open and can be adapted to different FM/combo chips, then it could become more common on AOSP ROMs.

This may or may not impact Spirit and myself greatly. Regardless, it seems even more essential now to "have my toe in the water" regarding non-FM apps, such as the AudioTricks app in my sig in early development now.

EDIT: 5000 new APIs for preview tomorrow. Wouldn't be surprised to see FM? in there, though unusable on Nexus (unless there's a magic hidden switch, which would be great to discover.) http://www.androidpolice.com/2014/0...-apis-including-usb-audio-bt-4-1-burst-photo/
[Spirit FM] mikereidis:
Yes, newest is usually on Play as a paid app. There's a free version linked in the 1st few posts of this thread that was built 9 months ago, but it may work.

Email me mikereidis@gmail.com and I can send the full version to try.

Someone had it working on GT-8160 and asked me to re-enable that phone on Play, so I did.

I can't officially support Huawei's and have never had one, so glitches here and there are more likely.
[Spirit FM] rubend447:
If you want i can help you whit the test of them. Only Send me a pm if you think on it.
[Spirit FM] zaclimon:
I'm pretty sure you shed a tear when you listen that from the i/o. Though let's hope that there will be more devices that will use FM radio in the future!

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Spirit FM] mikereidis:
I disabled PMs. Too many silly PMs and requests for free private support instead of just posting on the thread publicly.
[Spirit FM] mikereidis:
Tear ? No.

I'm not emotionally attached to FM, or my apps. I'll go wherever there is a need, and where I figure I can make a decent living from app sales. That's why my new AudioTricks app, and as a bonus, learning the intricate details of Android audio is good for Spirit.

That said, Spirit1 and 2 are paying my bills these days, so I maintain an allegiance to them and my users/supporters.

It really REMAINS to be seen what will happen and what the ramifications are. I'm about to dive into the L preview and SDK to see if there's any FM stuff.

If Google has built/blessed FM APIs, I'll be happy to consider re-building Spirit on top of those APIs. That could eventually massively increase my userbase, and make things easier, while at the same time, providing free alternatives.
[Spirit FM] zaclimon:
I was joking, no need to be that serious regarding this loool :p. Though I would be surprised that something announced at Google I/O won't make an appearance on the OS itself. Left to be seen...

Running the L preview right now to my tablet, the new interface is a welcomed change even though some people will either agree/disagree with me. Hope it will give some new breeze to that ICS design language.
[Spirit FM] spunker88:
Having an API for FM would make sense for Android Auto. Android Auto is centered around streaming, but I imagine car companies that ship factory installed head units with Android Auto will still want to interface an FM tuner. Android Auto is essentially Android underneath so Google could make an FM API for Android Auto and also use it on the Android One to support its tuner. This would make sense and would probably encourage other OEMs to ship FM radios on their phones since the hardware is there on a lot of them already.
[Spirit FM] mikereidis:
Yes.

http://developer.android.com/auto/index.html

"Live radio" could be interpreted as normal AM/FM, but it could also be restricted to streaming too.

Details are fuzzy, but stuff like this:

Indicates that apps will be running on connected phones or tablets, but that the equipment in the car will be mostly "dumb" screens and controls.

But the visions of auto OEMs and Google's aren't necessarily aligned. They'd like you to upgrade cars as often as phones.

So I can see smart Android running behind the dash, as well as in your phone/tab, if that's what the car OEM wants.

What "makes sense" to us does not always "make dollars" for the carriers. AT, VZN, T-Mobile and carriers in Canada and Mexico VERY PURPOSELY ask for FM to be disabled in many/most of the flagship devices, most notably Samsung, but LG and HTC both bow to those requests at least some of the time.

I don't see any of this as a sign that Google or the North American carriers "see the errors of their ways" and are now repenting by giving us the FM that many want.

Google Auto MIGHT be a reason for Google to become a little more friendly with the idea of analog OTA FM.

But IMO the main driving force here is Google One. Google wants/needs Android growth, and now in 2014 almost everyone in the developed world with a few dollars to their name has a smartphone. So the remaining growth will be in the developing world.

And the developing world DEMANDS analog OTA FM. Google One will fail without it. Google also hates SDCards, in favor of their cloud. But Google will support SDCards on One also.

Then there is dual SIM. I've NEVER seen dual SIM here in North America, and it's pretty rare in Europe too.

It may be difficult, and cost too much in shipping, etc (?) to get a Google One phone outside of India/China/Asia/Africa. Carriers here won't want to touch them IMO. They hate the reason for dual SIM of course.
[Spirit FM] mikereidis:
Also running L on my N7 2013.

Google very much knows what they are doing, but they ARE catering to the masses, not we techies. And more and more their security enhancements will make rooting etc. harder and harder.

I'm waiting for a good root solution so I can see how many different ways my apps will break, LOL. N7 can still be used for basic testing, especially if the kernel still has a usable Qualcomm FM driver, despite "0" signal.

I looked through the preview image files for signs of FM. Only sign was in the Qualcomm firmware, as I'd expect anyway.

Haven't looked through the "5000 new APIs" yet, but I think a simple grep will tell me there is no FM API in there. If there is, that's a whole new post I'll post ASAP.
[Spirit FM] axilleas_syr:
thanks

thanks men:o
[Spirit FM] Kess78:
I just found this maybe this can help you but you may already have it...

https://github.com/sonyxperiadev/ke...6f513a8669fb/drivers/media/radio/radio-iris.c

https://github.com/sonyxperiadev/ke...fb/drivers/media/radio/radio-iris-transport.c

It has some descriptions for the commands that can be entered in Spirit above 200 Mhz.
[Spirit FM] selemine:
sometimes the Chip could receive fm but the antenna isn't wired to save a little bit of money. Stupidity