search

angeloh / chrometophone

Automatically exported from code.google.com/p/chrometophone
0 stars 0 forks source link

Auto launch crashes app #5

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Download App
2. Register app and set it to "Launch browser/map directly"
3. Send link to phone

What is the expected output?
Link opens

What do you see instead?
App force closes.

This was tested in the Android 2.2 emulator.

Original issue reported on code.google.com by patrick....@gmail.com on 21 May 2010 at 12:19

GoogleCodeExporter commented 9 years ago 
FYI

I flashed FRE51-user onto my phone and went through the steps above, without 
crash. Sometimes the message 
takes 30+ seconds to arrive but that's the only "issue".

Original comment by that...@google.com on 22 May 2010 at 11:41

GoogleCodeExporter commented 9 years ago 
Thanks, I'll check it out in the morning.

Original comment by patrick....@gmail.com on 23 May 2010 at 12:00

GoogleCodeExporter commented 9 years ago 
hi, patrick.oreilly, how can u Register account in emulator? i found nothing in
'Desktop Account'.
 One more thing, when i click 'Resister Device', i got this message from logcat:

"05-23 23:42:02.907: WARN/ActivityManager(59): Unable to start service Intent {
act=com.google.android.c2dm.intent.REGISTER (has extras) }: not found"

Any help?

Original comment by caojunvincent@gmail.com on 23 May 2010 at 3:42

Attachments:

GoogleCodeExporter commented 9 years ago 
Vincent,
Yup I was able to login, the account show's in the dropdown and all.
Got to Settings -> Accounts & Sync -> Add Account. That worked for me.

Chrometophone is still crashing in the emulator with auto launch turned on.

Original comment by patrick....@gmail.com on 23 May 2010 at 4:16

GoogleCodeExporter commented 9 years ago 
I also experience the same problem with auto-launch enabled.  I'm running a 
Nexus One 
(standard, non-rooted) with Android 2.2.

Original comment by betabo...@gmail.com on 23 May 2010 at 8:56

GoogleCodeExporter commented 9 years ago 
Patick, thanks for your reply. but still i'm failed to setup my account in 
emulator.
I have no idea how to set the domain, server, etc, and i got the log from 
logcat:

05-24 11:17:18.354: INFO/ActivityManager(67): Starting activity: Intent {
cmp=com.android.email/.activity.setup.AccountSetupCheckSettings (has extras) }
05-24 11:17:18.504: DEBUG/Email(177): Begin check of incoming email settings
05-24 11:17:18.614: DEBUG/EAS SyncManager(177): !!! EAS SyncManager, onCreate
05-24 11:17:18.954: INFO/ActivityManager(67): Displayed activity
com.android.email/.activity.setup.AccountSetupCheckSettings: 555 ms (total 555 
ms)
05-24 11:17:20.214: VERBOSE/EmailServiceProxy(177): validate returns 1
05-24 11:17:20.274: DEBUG/EAS SyncManager(177): !!! EAS SyncManager, onDestroy

Original comment by caojunvincent@gmail.com on 24 May 2010 at 3:22

Attachments:

GoogleCodeExporter commented 9 years ago 
Hi,

I am facing the same problem.

Original comment by gbha...@gmail.com on 24 May 2010 at 4:23

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Vincent,
It looks like you are trying to login to email rather than google. The prompt 
shouldn't be asking for a server (as it assumes it's Google.)
are you sure you are using a version of the emulator with the Google API's? Not 
just 
the vanilla version?

Original comment by patrick....@gmail.com on 24 May 2010 at 1:53

GoogleCodeExporter commented 9 years ago 
I also experience the same issue with auto-launch enabled.  After pushing a 
link to 
the phone, an error message appears on the phone that says:

"Sorry! The application Chrome to Phone (process 
com.google.android.apps.chrometophone) has stopped unexpectedly.  Please try 
again."

Links work properly without auto-launch enabled. 

I'm running a Nexus One with Android 2.2
Build number: passion-userdebug 2.2 FRF51 38176 test-keys

Original comment by thol...@google.com on 24 May 2010 at 5:25

GoogleCodeExporter commented 9 years ago 
Can you send the exception reported from running adb logcat? Thnx.

Original comment by burke.da...@gmail.com on 24 May 2010 at 6:04

GoogleCodeExporter commented 9 years ago 
It happens to me too. Here's the exception from logcat:

05-24 14:23:37.061: INFO/ActivityManager(85): Start proc 
com.google.android.apps.chrometophone for broadcast 
com.google.android.apps.chrometophone/.DataMessageReceiver: pid=704 uid=10077 
gids={3003}
05-24 14:23:37.121: DEBUG/MediaPlayer(704): Couldn't open file on client side, 
trying 
server side
05-24 14:23:37.121: ERROR/MediaPlayerService(59): Couldn't open fd for 
content://settings/system/notification_sound
05-24 14:23:37.121: ERROR/MediaPlayer(704): Unable to to create media player
05-24 14:23:37.121: ERROR/RingtoneManager(704): Failed to open ringtone 
content://settings/system/notification_sound
05-24 14:23:37.121: DEBUG/AndroidRuntime(704): Shutting down VM
05-24 14:23:37.121: WARN/GTalkService(155): [DataMsgMgr] broadcast intent 
callback: 
result=CANCELLED forIntent { act=com.google.android.c2dm.intent.RECEIVE 
cat=[com.google.android.apps.chrometophone] (has extras) }
05-24 14:23:37.121: WARN/dalvikvm(704): threadid=1: thread exiting with 
uncaught 
exception (group=0x4001d7f0)
05-24 14:23:37.131: ERROR/AndroidRuntime(704): FATAL EXCEPTION: main
05-24 14:23:37.131: ERROR/AndroidRuntime(704): java.lang.RuntimeException: 
Unable to 
start receiver com.google.android.apps.chrometophone.DataMessageReceiver: 
java.lang.NullPointerException
05-24 14:23:37.131: ERROR/AndroidRuntime(704):     at 
android.app.ActivityThread.handleReceiver(ActivityThread.java:2821)
05-24 14:23:37.131: ERROR/AndroidRuntime(704):     at 
android.app.ActivityThread.access$3200(ActivityThread.java:125)
05-24 14:23:37.131: ERROR/AndroidRuntime(704):     at 
android.app.ActivityThread$H.handleMessage(ActivityThread.java:2083)
05-24 14:23:37.131: ERROR/AndroidRuntime(704):     at 
android.os.Handler.dispatchMessage(Handler.java:99)
05-24 14:23:37.131: ERROR/AndroidRuntime(704):     at 
android.os.Looper.loop(Looper.java:123)
05-24 14:23:37.131: ERROR/AndroidRuntime(704):     at 
android.app.ActivityThread.main(ActivityThread.java:4627)
05-24 14:23:37.131: ERROR/AndroidRuntime(704):     at 
java.lang.reflect.Method.invokeNative(Native Method)
05-24 14:23:37.131: ERROR/AndroidRuntime(704):     at 
java.lang.reflect.Method.invoke(Method.java:521)
05-24 14:23:37.131: ERROR/AndroidRuntime(704):     at 
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
05-24 14:23:37.131: ERROR/AndroidRuntime(704):     at 
com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
05-24 14:23:37.131: ERROR/AndroidRuntime(704):     at 
dalvik.system.NativeStart.main(Native Method)
05-24 14:23:37.131: ERROR/AndroidRuntime(704): Caused by: 
java.lang.NullPointerException
05-24 14:23:37.131: ERROR/AndroidRuntime(704):     at 
com.google.android.apps.chrometophone.DataMessageReceiver.launchBrowserOrMaps(Da
taMes
sageReceiver.java:85)
05-24 14:23:37.131: ERROR/AndroidRuntime(704):     at 
com.google.android.apps.chrometophone.DataMessageReceiver.handleMessage(DataMess
ageRe
ceiver.java:68)
05-24 14:23:37.131: ERROR/AndroidRuntime(704):     at 
com.google.android.c2dm.C2DMBroadcastReceiver.onReceive(C2DMBroadcastReceiver.ja
va:97
)
05-24 14:23:37.131: ERROR/AndroidRuntime(704):     at 
android.app.ActivityThread.handleReceiver(ActivityThread.java:2810)
05-24 14:23:37.131: ERROR/AndroidRuntime(704):     ... 10 more
05-24 14:23:45.211: DEBUG/SystemPanel(413): Created master record in: 5ms.  
Checkpoint=true, Processes Recorded=false
05-24 14:23:45.241: ERROR/Tethering(85): active iface (usb0) reported as added, 
ignoring
05-24 14:23:45.241: DEBUG/WifiService(85): ACTION_BATTERY_CHANGED pluggedType: 2
05-24 14:23:47.761: DEBUG/dalvikvm(413): GC_FOR_MALLOC freed 4229 objects / 
525200 
bytes in 67ms

Original comment by ed.burnette on 24 May 2010 at 6:25

GoogleCodeExporter commented 9 years ago 
This looks like an old version. Can you try installing the latest version at 
http://code.google.com/p/chrometophone/downloads/list

Original comment by burke.da...@gmail.com on 24 May 2010 at 6:49

GoogleCodeExporter commented 9 years ago 
Davey,
I downloaded the new APK and I'm still getting the F/C when auto open is 
enabled.

Attached is the logcat (I'm running this in the SDK emulator). This is from 
boot to 
F/C, followed by sending a second link and another F/C

Original comment by patrick....@gmail.com on 25 May 2010 at 1:04

Attachments:

GoogleCodeExporter commented 9 years ago 
Where did you find Andriod 2.2

Original comment by MRAi...@gmail.com on 25 May 2010 at 9:28

GoogleCodeExporter commented 9 years ago 
Thanks. Fixed and upload new APK.

Original comment by burke.da...@gmail.com on 25 May 2010 at 11:40

GoogleCodeExporter commented 9 years ago 
Still crashing for me, even after update.

Original comment by carlosc...@gmail.com on 25 May 2010 at 7:45

GoogleCodeExporter commented 9 years ago 
Fixed for me.

Carloschee, could you connect your Android to your PC, then from the Android 2.2
SDK/Tools folder run "adb logcat > logcat.txt" from the command line, then try 
again
and attach logcat.txt to this page so Davey can look for a fix?

Original comment by patrick....@gmail.com on 25 May 2010 at 10:30

GoogleCodeExporter commented 9 years ago 
Here you go. Just duplicated the error.

Original comment by carlosc...@gmail.com on 25 May 2010 at 10:36

Attachments:

GoogleCodeExporter commented 9 years ago 
Carloschee - this is the error that was just fixed. Please uninstall (Settings 
-> Applications -> Manage 
Applications -> Chrome to Phone -> Uninstall) and reinstall the latest from 
code.google.com/p/chrometophone/downloads/list.

Original comment by burke.da...@gmail.com on 25 May 2010 at 10:48

GoogleCodeExporter commented 9 years ago 
Thanks Burke, looks like uninstalling and reinstalling the new version again 
fixed it.

Original comment by carlosc...@gmail.com on 25 May 2010 at 10:59

GoogleCodeExporter commented 9 years ago 
I'm facing two problems working with Android 2.2 Emulator - API Level 8:
1) When I launch ChromeToPhone it doesnt't detect any account on the device and 
I can't continue.
2) When I configure an account the only way I can do this is setting the server 
as m.google.com. If not I get the same error mentioned in another comment.

Original comment by SGHM...@gmail.com on 13 Nov 2010 at 7:06

Attachments: