Sorry for delay, I was writing up a detailed review for the current extras-devel release of the universal portrait mode virtual keyboard.

Anyway, on the one hand, the complexity and lack of a .exe in a friendly Windows formal scares me. On the other hand, fear is for the weak, and the N900 does not accept the weak as it's users (but seriously I got this device planning to use it as leverage to make myself learn stuff like this, so I'll dive right in).

Actually, I just read it again and though about and and it seems relatively simple. Override the proprietary FM Transmitter applet with yours, get a random program/script thing, which somehow is tied to the speaker being on, and then call/get-called -> speaker -> fancy script.

Couple of questions: firmware updates - would they override the FM transmitter applet, requiring overriding it again?

Does it matter what I change sig_call_state_ind to? It seems like I'm just changing state to sttte in that example just to force FMTXD not to recognize that particular line (or rather not have anything to reference when it gets that particular 'command'/whatever), and that the sttte is just a change meant to make it easy to remember, find, and and fix that line of the fmtxd later. Correct?

Anyway, I will try this soon, most likely. By the way, what do alsactl and -f mean in the alsactl -f (filepath to that attached unarchived file) command/script? Because I would remember it better on-the-fly if I could attach a meaning to that command.

At any rate, thanks. I hope it helps the poster before me, though.