I did notice that GV works when started after power-up of phone. I was curious if the failure at power-off/on was happening on any other device or is it a unique combination of apps on my phone. I think the bug is in version 0.3.0.
This error is
not due to modified kernels for two reasons: 1. I run stock kernel and 2. check the following log which shows the trace. Although it is only a section of the trace, people who are playing with Android SDK or understand Object-oriented programming will appreciate it
01-09 22:21:59.271 I/ActivityManager( 1857): Start proc com.google.android.apps.googlevoice for broadcast com.google.android.apps.googlevoice/.BootUpReceiver: pid=2172 uid=10073 gids={3003}
01-09 22:21:59.431 I/dalvikvm( 2172): Debugger thread not active, ignoring DDM send (t=0x41504e4d l=38)
01-09 22:21:59.786 E/dalvikvm( 2172): Could not find method android.content.Context.getApplicationInfo, referenced from method com.google.android.apps.googlevoice.BootUpReceiver.onReceive
01-09 22:21:59.786 W/dalvikvm( 2172): VFY: unable to resolve virtual method 101: Landroid/content/Context;.getApplicationInfo ()Landroid/content/pm/ApplicationInfo;
01-09 22:21:59.786 W/dalvikvm( 2172): VFY: rejecting opcode 0x6e at 0x0037
01-09 22:21:59.786 W/dalvikvm( 2172): VFY: rejected Lcom/google/android/apps/googlevoice/BootUpReceiver;.onReceive (Landroid/content/Context;Landroid/content/Intent
V
01-09 22:21:59.786 W/dalvikvm( 2172): Verifier rejected class Lcom/google/android/apps/googlevoice/BootUpReceiver;
01-09 22:21:59.821 W/dalvikvm( 2172): Class init failed in newInstance call (Lcom/google/android/apps/googlevoice/BootUpReceiver
01-09 22:21:59.821 D/AndroidRuntime( 2172): Shutting down VM
PID: 2172 SIG: 3
01-09 22:22:00.001 I/dalvikvm( 2172): threadid=7: reacting to signal 3
01-09 22:22:04.816 I/Process ( 2172): Sending signal. PID: 2172 SIG: 9 01-09 22:22:04.826 I/ActivityManager( 1857): Process com.google.android.apps.googlevoice (pid 2172) has died.
---------
Not responsible for the winks they are due to the set of characters in the log file.