Open GoogleCodeExporter opened 8 years ago
Can you do adb logcat ?
Original comment by cos...@google.com
on 20 Sep 2010 at 3:48
To be honest, not familiar with running command prompt tools, but Googled
around and it seems the first step was to download and install the SDK, which
I'm doing. However, can't find clear steps on how/where to run this command.
If you can provide the simple steps, or just point me to the right place, would
greatly appreciate. Thx again.
Original comment by jonathan...@gmail.com
on 20 Sep 2010 at 3:58
I believe this can happen if the notification volume is set to silent in the
phone settings. Fixed in the code and will be in the next release. For now,
make sure notification volume isn't silent.
Original comment by burke.da...@gmail.com
on 28 Sep 2010 at 8:57
I was hopeful that you were correct, but unfortunately the issue remains even
when not in silent mode. Any specific settings I should check/uncheck other
than sound? Much thx.
Original comment by jonathan...@gmail.com
on 28 Sep 2010 at 6:19
Go into Settings, Sound, Volume. Assuming "Use incoming call volume for
notifications" is unchecked, make sure the notification volume slide isn't set
to zero.
This may not be the issue but it's the only crash I'm aware of...
Original comment by burke.da...@gmail.com
on 28 Sep 2010 at 8:40
Greatly appreciate your help, but unfortunately didn't work. Tried
reinstalling as well after I changed settings, but no luck. Any way for me to
do a diagnostic test and then send to you? Thanks again.
Original comment by jonathan...@gmail.com
on 28 Sep 2010 at 10:05
Installing the SDK, running adb logcat from a command prompt with the phone
plugged into USB and copying and pasting the logs is the best way to pinpoint
the issue.
I still suspect something to do with the ringtone setting on the phone...
Original comment by burke.da...@gmail.com
on 28 Sep 2010 at 10:51
I was also having the crash problem, but changing the notification ringtone did
fix the problem. When I changed back to notification being silent, the problem
returned.
So thanks for the workaround! (though i'd still like the option of having both
silent notifications AND working chrome-to-phone :)).
Keep up the good work.
Original comment by HMaye...@gmail.com
on 28 Sep 2010 at 11:43
Mine crashes too, every single time, consistantly. I'm on a Nexus-One, Chrome
to phone 2.1.0, Android 2.2.1, Build # FRG83D
------------------
D/KeyguardViewMediator( 85): pokeWakelock(5000)
D/KeyguardViewMediator( 85): pokeWakelock(5000)
W/WindowManager( 85): No window to dispatch pointer action 1
D/WifiService( 85): acquireWifiLockLocked: WifiLock{NetworkLocationProvider
type=2 binder=android.os.Binder@44a23ac0}
D/LocationMasfClient( 85): getNetworkLocation(): Returning cache location
with accuracy 60.0
D/dalvikvm( 518): GC_FOR_MALLOC freed 4106 objects / 470184 bytes in 72ms
D/WifiService( 85): releaseWifiLockLocked: WifiLock{NetworkLocationProvider
type=2 binder=android.os.Binder@44a23ac0}
I/Process ( 8172): Sending signal. PID: 8172 SIG: 9
W/InputManagerService( 85): Window already focused, ignoring focus gain of:
com.android.internal.view.IInputMethodClient$Stub$Proxy@44f4e990
I/ActivityManager( 85): Process com.google.android.apps.chrometophone (pid
8172) has died.
W/ActivityManager( 85): Scheduling restart of crashed service
com.google.android.apps.chrometophone/.C2DMReceiver in 5000ms
D/dalvikvm( 194): GC_EXPLICIT freed 1120 objects / 57760 bytes in 81ms
I/ActivityManager( 85): Start proc com.google.android.apps.chrometophone for
broadcast
com.google.android.apps.chrometophone/com.google.android.c2dm.C2DMBroadcastRecei
ver: pid=8183 uid=10062 gids={3003}
D/MediaPlayer( 8183): Couldn't open file on client side, trying server side
E/MediaPlayerService( 59): Couldn't open fd for
content://settings/system/notification_sound
E/MediaPlayer( 8183): Unable to to create media player
E/RingtoneManager( 8183): Failed to open ringtone
content://settings/system/notification_sound
W/dalvikvm( 8183): threadid=7: thread exiting with uncaught exception
(group=0x4001d7f0)
E/AndroidRuntime( 8183): FATAL EXCEPTION: IntentService[stp.chrome@gmail.com]
E/AndroidRuntime( 8183): java.lang.NullPointerException
E/AndroidRuntime( 8183): at
com.google.android.apps.chrometophone.C2DMReceiver.playNotificationSound(C2DMRec
eiver.java:171)
E/AndroidRuntime( 8183): at
com.google.android.apps.chrometophone.C2DMReceiver.onMessage(C2DMReceiver.java:9
6)
E/AndroidRuntime( 8183): at
com.google.android.c2dm.C2DMBaseReceiver.onHandleIntent(C2DMBaseReceiver.java:10
7)
E/AndroidRuntime( 8183): at
android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:59)
E/AndroidRuntime( 8183): at
android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 8183): at android.os.Looper.loop(Looper.java:123)
E/AndroidRuntime( 8183): at
android.os.HandlerThread.run(HandlerThread.java:60)
I/Process ( 85): Sending signal. PID: 8183 SIG: 9
W/ActivityManager( 85): Process com.google.android.apps.chrometophone has
crashed too many times: killing!
I/DropBoxManagerService( 85): Usage (156) > Quota (155)
D/dalvikvm( 518): GC_EXPLICIT freed 1345 objects / 139848 bytes in 61ms
D/dalvikvm( 7770): GC_EXPLICIT freed 57 objects / 2976 bytes in 64ms
I/power ( 85): *** set_screen_state 0
D/WifiService( 85): ACTION_SCREEN_OFF
D/SurfaceFlinger( 85): About to give-up screen, flinger = 0x1fe220
Original comment by g...@greggman.com
on 20 Dec 2010 at 10:01
I'm experiencing more or less the same issue but in my case it constantly
crashes during the first execution when I select the account to use the service
with. Then the app reloads and crashes again if I retry.
The system volume workaround did not work for me.
Original comment by marco.pr...@gmail.com
on 18 Sep 2014 at 10:38
Original issue reported on code.google.com by
jonathan...@gmail.com
on 20 Sep 2010 at 3:44