I'm a little disappointed that this doesn't also add the "magnifying glass" feature that motorola has been implementing into it's latest phone UIs. Anyone know where I can get this for a Droid 1?
i think the problem with the stock keyboard fc'ing on you is related to the fact that libjni_latinime.so had to be replaced, so the stock keyboard is expecting to use the stock library and when it calls this one it pukesgot it working.. using the "old/manual" method on a rooted D1 using Pete's vanilla FRG01B ROM (no theme).
1. backup my ROM (nandroid)
2. backup (zipped) system/lib/libjni_latinime.so with root explorer
3. sent the apk to gmail and then installed apk
4. copy/paste new libjni_latinime.so in place over old (remounted as r/w with root explorer)
5. installed green highlight theme .zip via recovery (found earlier in this thread)
6. settings > lang & keyboard > selected the multi-touch keyboard
so, it seems to work! I do have the choice, using the "manual" method in that thread, to select stock keyboard or multi-touch. but I love this multi-touch as it looks way better, seems snappier, faster, more accurate, nice colors, I do have multi touch ability now (I can touch two or more spaces on the screen and the screen registers two or more individual fingers).
also, my shift key and some of the other key oddities others list - alt and caps keys sticking on - seem to work as expected for me.
Now, I did try to select the stock keyboard and did have some FC issues others reported.. but not sure I will even go back though. Also, the manual method does allow to keep the stock, so I should be able to roll back. But odd that I followed the method to keep stock and still get forceclosing on the stock KB. I like having the option to go back if I want, so it is kind of a bummer. But I like this KB so much, I will not likely go back to stock. Curious if anyway has an idea for a fix for this 1 issue.
thanks.. I kind of suspected that. Am I correct in assuming I cannot push back the libjni_latinime.so file for my ROM without busting this great KB, correct? It seems like, even though I have the "choice" and can select the stock KB or this D2 KB, if I want this D2 KB I should just accept this forceclose issue on the stock KB as I cannot put back my stock libjni_latinime.so file to fix the forceclose without then busting this D2 KB?i think the problem with the stock keyboard fc'ing on you is related to the fact that libjni_latinime.so had to be replaced, so the stock keyboard is expecting to use the stock library and when it calls this one it pukes
Wanted to add that this bug only occurs in landscape not portrait. In portrait it's sound but in landscape it cuts half the text that you have typed out in the main texting field and you can only see the bottom half.With every multi-touch keyboard I've applied/tried out there's a slight bug.
When I'm texting, I can only see the bottom half of what I'm texting. I have to scroll in the main text area to see what I'm typing fully, but as soon as I go back to typing it only shows the bottom half of the letter again.
Wondering if you could check it out or fix it?
Running BB 0.4 on Droid1.
I've posted this on other themers/devs threads as well hoping to find a fix for this, thanks.
look at the op toward the top, theres a link to kaos's port (it is much more advanced than my "port") it works on all phones (afaik)Anyone got it working with hero cdma and cyanogenMod 6? It does not work for me. I tried flashing and the old method. I have selected it as input. I don't have FC's, it just doesn't show up.