Question: Is FastSMS marked as a dependency of FastSMSEvo? I just glanced at the dependencies list for FastSMSEvo and didn't notice it, but I may very well be wrong about that, and just didn't see it.

@Minhaz: He'd have to recode both FastSMS and FastSMSEvo probably, to make that work. What I would have done is made FastSMSEvo stand-alone and then made FastSMS depend on and use FastSMSEvo. But I can understand why he went his route, since FastSMS was here first, so that was the natural progression coding-wise.

Some quick test results:
There is a slightly noticeable memory use difference. I use both the normal CPUMEM applet and my own python clone of it with five bars - cpumem applet shows bars at 30, 50, 70, and 90 % RAM used. Mine shows bars at 20, 40, 60, 80, and 100. Normally a new reboot puts both versions at two bars, implying memory use between 50-60 %. After launching FastSMS and letting it sit in the background [EDIT: Meaning, after I launched the VKB normally, and it loaded FastSMS in the background as is explained in the first post), my applet shows 3 bars, cpumem still shows 2 - implying 60-70 % memory used. Not an issue, and it could be the difference of 1-2 %, but just letting you know it's somewhat noticeable.

I also JUST realized that the red/white icon button was an eraser, and that was backspace. For a while I thought there was no backspace at all. That icon is prob'ly a gamble in terms of intuitiveness, but it works, and so long as you know what it is it's not a problem to use.

One thing I noticed (so far testing in Conversations only) is that if I auto-rotate conversations itself, it has a hard time rotating to portrait sometimes. The first time I auto-rotated Conversations and clicked on the text-box in portrait mode, the entire Conversations app flipped back to landscape, the FastSMS keyboard came up in landscape, then the entire thing auto-rotated to portrait then back to landscape... Or something like that. I then wiggled it a bit (landscape then portrait so that the system knew to flip again) and it went to portrait just fine. Testing it again for repeatability, however, I noticed that it launches in portrait mode from portrait mode Conversations just fine. It does, when you click out of the portrait VKB to enter text, go momentarily to landscape, exits the keyboard, and then Conversations rotates back to portrait. The text is entered just fine however.

I had one instance of text NOT being entered when clicking out of the VKB when in landscape, I haven't really been able to reproduce it since though.

I'll report back when I can with reports on how well it works in a bunch of other apps, but in the meantime I just want to say: this is wonderful. Suddenly the N900s versatility just skyrocketed tremendously on top of all the other great things about it.