Originally Posted by kdoggy
So um does this work on the new Nexus 6 with L 5.0? The Google Apps Store says its compatible but I can't find any mention of this working on the N6.
Oh nevermind, I just saw the thread where you said Moto doesn't enable FM. Damn......
Nice looking app too!
I don't think there is any official confirmation yet. But it is EXTREMELY unlikely that Google did anything different this time.
There has never been a Nexus that officially supported FM, and I doubt there ever will be. (And Android One does not equal Nexus).
The original Nexus One was a slightly reworked HTC Desire and the FM antenna connection was left active. But it requires a custom kernel and root to get the audio part working.
I tested my Nexus Player and Nexus 9 and neither are capable of FM. (Nor either of my Nexus 7's of course.)
Basically, somebody needs to run Spirit1 on a rooted device with a kernel supporting the FM driver and send me a debug log. Spirit1 should APPEAR to work, but RSSI will be negative or around 0.
Google Play is pretty clueless about app compatibility. AFAIK, there is no Google blessed "FM Radio" attribute that I could specify as a requirement in Spirit, and there likely never will be one. (I should check Android One FM app to be sure, but there is no such documentation AFAICT last I looked.)
So for the most part, I can only go into Google Play developer console, decode the MANY thousands of code names for devices, and manually one by one disable the ones I know do not work. I'm sure I spent at least 50-100 hours trying to do this for Spirit1/Unlocked as well as Spirit1/Light. Some popular phones, like GS4/GS5 etc have dozens of different code names, and there is no secret decoder to figure out which might have FM and which don't.
There appears to be no way to only specify that Spirit1 or Spirit2 ONLY work on these 20 or 100 different phones. Disabling an app on a given device variant is a negative option. Google does this on purpose IMO because they make more money this way, and don't have to worry about it making them look bad, only the dev looks bad and has to deal with support, refunds and bad reviews.
I'd be happy just to have a "Needs SU" attribute for Android apps on Play, but Google will never support that either it appears.
I abandoned this as "silly work" and decided my customers would be better off if I spent that time developing. This is one reason there are many Spirit2 Play reviews that are rather bad*, because I did not do this for Spirit2, and because there are so many people who prefer to post reviews calling me a thief instead of emailing me for an order cancel, even after a popup message saying "Not compatible please email for refund". And too many people do not read app descriptions, though I do understand not everybody knows English.
*Spirit2 Play reviews that are rather bad: I wasn't reading reviews for a few years, for various reasons. I just went through all 80 or so for Spirit2 asking people with incapable devices to email me for a refund.
*Maybe I should at least disable popular devices, like GS4/GS5. I am surprised at the number of Spirit2 sales on these. And I hate to say it, but disabling them means my income gets even smaller than it is already.
And some people are OK with supporting me with an app sale despite that their current phone can never support FM.