Thread: [Android] Another Android port: NITdroid
View Single Post
solca's Avatar
solca is offline solca
2008-12-25 , 20:44
Posts: 109 | Thanked: 196 times | Joined on Sep 2008 @ Guatemala
#384
Originally Posted by Bundyo View Post
And while we are at it - Solca, can you get these two files in the next userspace? omap-keypad.kl and omap-keypad.kcm.bin are just a copy of the n8x0 ones. You can probably symlink them too.
kcm files are not needed for the N700/N800 keypad, they are used for letter variations and these keypad lacks letters... if it loads the default qwerty.kcm.bin that's correct, as for the omap-keypad.kl file it is included now in my working copy and will appear in the next NITdroid release but a complete evtest output on N700 will be useful to determine if exactly the same keycodes apply. Thx!.

Originally Posted by Chinpokomon View Post
As per installation instructions, I reformated one of the partitions as ext3. I think this should be reconsidered. Ext3 partitions are not ideally suited for flash drives at all, since the journal is busy doing its thing.
That's true for MTD devices but not for MMC/SD cards that do hardware wear leveling, in fact EXT3 with noatime option (as NITdroid do) is fine and is much better than the default FAT partitions (which have fixed locations for the file allocation tables) and even FAT is not remotely a problem on MMC/SD cards.

But the opposite as per your suggestion, using flash filesystems (YAFFSx, JFFSx, UBI, etc.) on wear leveling devices can be slow, useless and maybe harmful if it happens that the hardware wear leveling is invalidated by the software filesystem wear leveling.

Originally Posted by rasmithuk View Post
I'm not sure if this is the right place to report this but I think the touch screen pressure code is backwards (or google picked an odd way to represent it).
If you go to 'Dev Tools' > 'Pointer Location' the current pressure is displayed at the top of the screen. Now I'm assuming that this is scaled from 0 to 1 with 1 being as higher force as possible. However on my n800 the harder I push the closer to 0 the value goes.
This does explain why the on-screen keyboard is a bit odd to use with multiple key presses being detected for no reason. I'm guessing the pressure calibration code still needs tweaking.
That's an interesting discovery, I'm looking into integrating tslib for the next release and use the calibration data used in Maemo for this, can this be helpful?

(BTW next release is near... )
__________________
NITdroid
Last edited by solca; 2008-12-25 at 20:55.