The code is there to detect headset. I disabled it to allow antenna-less operation. Do you think it would be better to re-enable the code as is so it enforces the insertion of a headset antenna, or just inform the user that an antenna is recommended ?
I'll look into your speaker/headset issues. I saw something weird myself.
Yes, I'll re-alphabetitize. The United States is likely effectively there twice as it's such an awesome country.
EDIT: There are some slight differences in the code for US versus North America. I also realise now that certain
areas (Europe and Japan) are favoured by being at the top of the list instead of alphabetical. I'd bet you were happy
to see North America conveniently at the top, even though (or perhaps because) it's the default. So, for now at least
I'll leave this the way CodeAurora set it up. If anyone else has an opinion, please speak up.
Record didn't FC for me. It created an empty file on SDcard each time. I'll disable it though until it works as most people won't read instructions/release notes and will just experiment.
I suspect that it was the FMRadio Service that FC'd. Android automatically restarts services that crash after 5 seconds or so and that's why the "FM" reappeared in the notification bar.
The version 1 app supported 100 volume steps. The standard Android media volume only supports 16 steps including 0 volume. I will try making volume an exponential function, more like decibels than linear. I hope that 16 steps will be sufficient, but if not, it would require code that goes beyond standard Android media volume control. I doubt many (any?) apps do that and I'd think Google must have thought 16 steps are sufficient.
I'm guessing the "quiet fuzz" is due to the analog path from FM radio still being open, despite the FM chip being off. I'll add some code to shut that path down completely when the app powers down FM.