Wanting to avoid boilerplate code, and to experiment a little with Dependency Injection in Android, i based my work on RoboGuice. I think I followed all the example code, but my activities would simply crash with a RuntimeException on startup.

Since finding the root cause of this problem was not as trivial as I wished it to be, I decided to write this up as an article for myself and of course for all the other Android developers out there who don’t want to waste time hunting this issue when they could be gold-plating their apps

To cut to the core of the problem: If your activity is throwing this:


E/AndroidRuntime( 246): Uncaught handler: thread main exiting due to uncaught exception
E/AndroidRuntime( 246): java.lang.RuntimeException: Unable to start activity
ComponentInfo{com.gurkensalat.osm.osmsync/com.gurkensalat.osm.osmsync.HelloAndroidActivity}: java.lang.ClassCastException: android.app.Application
E/AndroidRuntime( 246): at
android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2496)
...


maybe you need to declare your actual application class type in AndroidManifest.xml:


<application android:icon="@drawable/icon"
android:label="@string/app_name"
android:name="roboguice.application.RoboApplication">
...
</application>


The only bad thing is that reading on an eInk display can become pretty addictive as well, but my previous readers had either no wireless capability or an useless operating system.

So, one day while reading through my blogs, suddenly I stumbled on this little wonder device… smallish form factor, useful operating system and an eInk display… I was hooked from the first day on

Actually ordering this thing and getting it to germany was a little adventure in itself, but in the end, I have a reader that is very close to my dream device… Now, if only Aldiko could synchronize its bookmarks between devices

O.k., having to empty my email inbox every few days because the internal memory was way too little sucked. And installing a custom rom just so I could have a slightly more usable app2sd sucket a little bit more. But what really broke the camel’s back was the poor visibility of the display in the sun. Which meant that I could not read any ebooks while relaxing after lunch or go to a quick geocaching hunt just as the fancy hit me.

So, without futher ado, since many many other people already wrote everything necessary about this cool device, here is my second android device: