Fullscreen switch mode does not start automatically when shield also active

[Jorge Silva]

When both the option to connect to shield and fullscreen switch mode are selected, the latter does not start automatically. Furthermore, when fullscreen switch mode is unchecked after this happens, the application force-closes. This must be due to the fact that unchecking fullscreen switch mode refers to an overlay that does not exist, likely causing a null pointer exception.

[Jorge Silva (jorge-silva)]

Some refactoring allowed for both preferences to start automatically. However, the app is timing out at boot-up showing an annoying force-close / wait message. This may be due to a locking method that simply takes too long to complete, will try to track it down and deal with it accordingly

[Jorge Silva (jorge-silva)]

A timed call to show the keyboard was added on boot. This now works on Motorola Droid/Milestone but may need testing in other devices