One of the more obvious settings missing from Android is the ability to use one keyboard, say Swype, in portrait orientation, and then automatically switch to another keyboard when the phone is in landscape.

This feature has been oft-requested, and is something that is strangely missing from many mobile OSes. Well, the clever clogs over at the XDA-Developers Nexus One forum have managed to figure it out with a little workaround.

However, the hack only works for those on rooted phones with access to the /system partition as Read-Write. Thankfully that is most phones, nowadays. In the words of the hack’s creator, ne0fhyk:

The application is rather simple so far. It shows you lists of the input method you have on your device, and allows you to specify different ones for portrait or landscape orientation.

It will then launch a service that's triggered by orientation's change events, and reset the input method based on your preference.

To do so, the service must run as system. Just copy the application under /system/app/.

Restarting after installation is recommended.

This is a work in progress. Occasionally, the keyboard switching shows lag. I am working on improving the app, so any feedback is appreciated.

I tried to install the hack myself, and it’s a little bit more complex than that.

1. Download the APK (there may be a newer version on XDA by the time you read this)

13. Now you want to reboot your system to load the application again, and also reset your /system partition to “ro” for security. Simply enter “reboot” and hit enter

14. Once your phone has restarted, open up Keyboard Manager from your application drawer

15. Choose which keyboards you’d like to use in which orientation, from the displayed drop-downs

Having used the app for a little bit, it does work, but it’s not instantaneous. It may take a few taps of the text entry field to work. The developer is definitely not done with this project, so at this stage it’s kind of a proof of concept, so don’t be surprised if the experience is a little buggy.

It’s great to see this issue finally, sort of, pretty much resolved. Check it out and leave your experiences in the comments below. Oh, and do a nandroid, k?