[Spirit FM] mikereidis:
There is no specific command for the "headphone jack requirement". The CM app and most other apps have standard Android code to detect the insertion/removal of the jack. Their code then deliberately does whatever it does, such as turning off the radio. On the CM app I hear a brief rush of static on the speaker when pulling the jack out, before the CM app mutes or turns off the chip.

I have this code too, but have disabled it for now. When I re-enable it, it will have options about what to do if anything.

Regarding transmit: No, I don't think any progress is possible until someone creates a phone (like the Sharps) with hardware designed to allow Tx. The TI WL127x and WL128x chips are CAPABLE of Tx, as are the Broadcom BCM4329 (but not the 4325 I have).

But if nobody is connecting the Tx power pins properly, we can't do anything without hardware mods. Same for the Tx antenna pins. I was once under the impression that one (TI or Broadcom?) had shared Rx/Tx antenna pins, but now I think they both have dedicated pins. And the Tx pins connect nowhere useful.

On that Legend FM thread (and/or my TI dev thread?) I posted a script I used to attempt Tx. All the registers looked good. But I couldn't detect any sign of a carrier even with the phone open and an Rx antenna almost touching. I didn't test Broadcom, but my hands are more than full with Rx and most people want Tx to stream audio and that brings up a whole other can of audio routing worms, so I've decided to focus on what seems possible: Rx.

If a manufacturer enabled the possibility of Tx (even without releasing the software), I suspect their costs for FCC etc. compliance testing would be much higher. And I think it's difficult enough with all the RF in a smart phone. Have you counted ? : Cell voice/data, WiFi, BT, FM Rx, GPS, some NFC and I'm likely forgetting something. Miracle of RF engineering these things.

Is that like "Your app is great, but what has it done for me lately ?". :D (An attempt at humor...)

I will read that then as "What other cool things are possible".

- RDS has features that remain untapped by my app. I've seen some stations transmit traffic info, and who knows what else. Many Europeans would like to see AF supported, as would I. I believe in Europe you can drive from one area to another and get the same channel on a different frequency, when the old freq is too weak.

- Stereo can be automatically and gradually blended into less stereo and more mono to increase S/N as signals get weak. Actually I think I already enable that but haven't really tested it. Also soft mute can reduce noise/static when tuning.

- Automatic scanning for all local frequencies would be really nice. Even better if they are identified by RDS and perhaps even Internet DB lookups. Also scanning by PT.

- It would also be interesting to look into Radio DNS and provide methods to link to station websites, playlists, or even to get artist and song info/lyrics. Also a "Name that tune" game.

- Digital audio to any device including BT, as well as Tivo like pause button and recording. Equalisation and VU meters could be enabled with a digital audio path.

- Might be able to get some RF stats,

- It would be WONDERFUL if my app could run on stock phones. It would greatly expand my target market. But I'm pessimistic about how feasible this is. Even if I reverse engineer the proprietary BT stacks, I will likely run into permissions problems that require root to work around. And if I DID, the carriers might just nix that like I think Bell may have done on the Samsung S with a new release requiring root for the FM driver access.

I think my list went past the TI specific, but it's a dream list for the next year I guess. That and a more likeable UI and support for more devices and ROMs.