Would love to use it but I just tried installing it 3 times and each time it appears small on my screen. I'm not going to do the LCD density fix because I know on Rubix ROMs it can cause random reboots.
Just checked locked and unlocked screen no reboots.
Ah I wasn't talking about the app, I manually put the density in within the build.prop... I was saying what number density did you use? I'm thinking 220?
240 works for me...Weird thing is the app said 240 when I launched it then I set it and it rebooted and has been fine.
Yea 240 is stock... that is weird.. I just tried 220 and 200... I guess I will try 240 again. Maybe reapplying the stock amount resets something somehow.
Yea the app worked but it makes absolutely no sense. I'm not complaining but I really want to know why the app worked but me manually changing the number didn't. I use to change my density all the time, it's not like I don't know which number/line to change.
Well that didn't last long. I just rebooted and now the keyboard went back to the smaller size. It seems like the change only lasts until you reboot the device.
Yea the keyboard is awesome. I was tying extremely fast on it. Sucks that it doesn't stay larger and you'd have to change the density every time you restart. Hopefully a better version comes out.
Reboot Recovery
Mount System
Install zip from sd card (navigate to the forementioned zip file)
Reboot
Done
I actually used this method from punk.kaos in XDA. I'm pretty sure yours works fine but the LatinIME file probably needs to be deleted from the
system/app folder. Otherwise the one in your zip will conflict with it, causing
force closes on the keyboard.
I actually used this method from punk.kaos in XDA. I'm pretty sure yours works fine but the LatinIME file probably needs to be deleted from the
system/lib folder. Otherwise the one in your zip will conflict with it, causing
force closes on the keyboard.
It's just that when I lost the MT keyboard on Rubix and I used the flash method,
I was still getting the FC on it. So I got rid of everything and just went the
route with a few more steps and didn't have a problem with the keyboard after that.