Applications

Nook Sideload Launching

One of the most annoying aspects of working with a stock Nook for development is trying to load up your application after you install it. The arcane series of buttons you need to press, and tapping on the speaker icon. Just stupid. And the fact that you need to reboot the device in order to get it to recognize a newly installed app – it’s like they don’t want you to create apps for the platform.

There are a few different workarounds, like launching using an adb command (ie. adb shell am start -a android.intent.action.MAIN -n com.example.myapp/com.example.myactivity). But my favorite so far is simply installing a new launcher application. I grabbed the Home sample from the Android resources, compiled that, sideloaded and launched it with the adb command.

Now when I hit the ‘n’ button on my device I have the option of launching into the Nook default home or the Home Sample application. From the Home Sample I can just pick the app I want directly, and I don’t need to reboot the device to see anything new I put on there. Great for when I’m poking around with a bunch of new stuff.

Bonus tip: On OS X you can use /etc/fstab to keep your development machine from mounting up the device every time you plug it in, resulting in an annoying error if you unplug without ejecting. Just add a line like this to keep it from mounting by default:


LABEL=MyNOOKcolor none msdos rw,noauto

When you do want to mount it, you can either do it from the command line or fire up Disk Utility.