• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Google Voice force closes on power-off/on..

momentoid

Android Enthusiast
Nov 11, 2009
363
60
US of A
Think Google Voice was updated a few days ago. Version 0.3.0 on device. Every time on power-off/on it force closes. Uninstalled and reinstalled it, did not help. Reviewed the log file and there are some unhandled exceptions in Google Voice code. Any one else with this problem? Is there a way to reinstall an older version of Google Voice app?
 
Think Google Voice was updated a few days ago. Version 0.3.0 on device. Every time on power-off/on it force closes. Uninstalled and reinstalled it, did not help. Reviewed the log file and there are some unhandled exceptions in Google Voice code. Any one else with this problem? Is there a way to reinstall an older version of Google Voice app?

Are you running stock kernel or one of Zefie's replacement ones?
 
Upvote 0
@AndroidSPCS: I have configured GV to ask when GV# should be used to make a call which works well when making a voice call. However to send SMS using GV#, we are forced to use GV app. I had requested integration of SMS with GV# to third party app such as Handcent SMS. So I updated hoping this would be fixed in the newer version. :(

@agent0014: running stock kernel.
 
Upvote 0
Think Google Voice was updated a few days ago. Version 0.3.0 on device. Every time on power-off/on it force closes. Uninstalled and reinstalled it, did not help. Reviewed the log file and there are some unhandled exceptions in Google Voice code. Any one else with this problem? Is there a way to reinstall an older version of Google Voice app?

Yes I am having this problem as well & also await a solution.

*edit* Running a stock Moment as well.
 
Upvote 0
To follow up on Agent's post, many people that are using Zefie's kernel are finding that Google Voice FC's upon starting. It doesn't seem to effect it and after the phone finds a signal, GV loads fine. It happens with mine.

But I'm not convinced that it's Zefie's kernel that's the cause. Prior to installing Odin my first step was using ADB to access the phone and I'm pretty sure that it was right after I did that (but prior to updating the kernel), that I noticed GV had a problem.
 
Upvote 0
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.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones