andyli Posted November 3, 2014 Report Share Posted November 3, 2014 Hi, The Android client works great for me until recently it simply crash when it starts...What could be the issue? Here is the logcat output when it start and crash:11-04 01:38:06.662: I/ActivityManager(628): Start proc com.bittorrent.sync for activity com.bittorrent.sync/.ui.activity.StartActivity: pid=16269 uid=10158 gids={50158, 1006, 3003, 1028, 1015}11-04 01:38:06.992: I/ActivityManager(16269): Timeline: Activity_launch_request id:com.bittorrent.sync time:1502830211-04 01:38:06.992: I/ActivityManager(628): START u0 {cmp=com.bittorrent.sync/.ui.activity.MainActivity} from pid 1626911-04 01:38:07.372: E/dalvikvm(16269): Could not find class 'com.amazon.device.messaging.ADM', referenced from method com.bittorrent.sync.service.CoreService.checkADM11-04 01:38:07.372: W/dalvikvm(16269): VFY: unable to resolve new-instance 974 (Lcom/amazon/device/messaging/ADM;) in Lcom/bittorrent/sync/service/CoreService;11-04 01:38:07.372: D/dalvikvm(16269): VFY: replacing opcode 0x22 at 0x000d11-04 01:38:07.382: D/dalvikvm(16269): DexOpt: unable to opt direct call 0x2126 at 0x0f in Lcom/bittorrent/sync/service/CoreService;.checkADM11-04 01:38:07.382: D/dalvikvm(16269): Trying to load lib /data/app-lib/com.bittorrent.sync-1/libbtsync.so 0x41d6529811-04 01:38:07.462: D/dalvikvm(16269): Added shared lib /data/app-lib/com.bittorrent.sync-1/libbtsync.so 0x41d6529811-04 01:38:07.492: D/AudioHardwareMSM8660(201): Bufsize 480011-04 01:38:07.492: D/AudioHardwareMSM8660(201): SampleRate 44.1k11-04 01:38:07.502: D/AudioHardwareMSM8660(201): Bufsize 480011-04 01:38:07.502: D/AudioHardwareMSM8660(201): SampleRate 44.1k11-04 01:38:07.522: D/AudioHardwareMSM8660(201): Bufsize 480011-04 01:38:07.522: D/AudioHardwareMSM8660(201): SampleRate 44.1k11-04 01:38:07.532: D/AudioHardwareMSM8660(201): Bufsize 480011-04 01:38:07.532: D/AudioHardwareMSM8660(201): SampleRate 44.1k11-04 01:38:07.542: D/AudioHardwareMSM8660(201): Bufsize 480011-04 01:38:07.542: D/AudioHardwareMSM8660(201): SampleRate 44.1k11-04 01:38:07.742: I/Adreno200-EGL(16269): <qeglDrvAPI_eglInitialize:269>: EGL 1.4 QUALCOMM build: AU_LINUX_ANDROID_JB_VANILLA.04.02.02.60.051_msm8960_JB_VANILLA_CL2997615_release_AU (CL2997615)11-04 01:38:07.742: I/Adreno200-EGL(16269): Build Date: 04/11/13 Thu11-04 01:38:07.742: I/Adreno200-EGL(16269): Local Branch: 11-04 01:38:07.742: I/Adreno200-EGL(16269): Remote Branch: quic/mako_jb_mr111-04 01:38:07.742: I/Adreno200-EGL(16269): Local Patches: NONE11-04 01:38:07.742: I/Adreno200-EGL(16269): Reconstruct Branch: AU_LINUX_ANDROID_JB_VANILLA.04.02.02.60.051 + NOTHING11-04 01:38:07.792: D/OpenGLRenderer(16269): Enabling debug mode 011-04 01:38:07.882: E/UTERRORONOES(16269): setting up callback11-04 01:38:07.882: E/UTERRORONOES(16269): setting up descriptor with dump path: (null)11-04 01:38:08.072: I/ActivityManager(628): Displayed com.bittorrent.sync/.ui.activity.MainActivity: +1s81ms (total +1s434ms)11-04 01:38:08.402: I/ActivityManager(628): Timeline: Activity_windows_visible id: ActivityRecord{42a3cee0 u0 com.bittorrent.sync/.ui.activity.MainActivity t9} time:1502971711-04 01:38:09.492: E/UTERRORONOES(16269): Dump path: /data/data/com.bittorrent.sync/files/.sync//5e3595f7-a14c-0370-516842c8-67ac4872.dmp11-04 01:38:09.572: I/Choreographer(16269): Skipped 54 frames! The application may be doing too much work on its main thread.11-04 01:38:09.592: I/UTERRORONOES(16269): BTSync Core error: coreCrashCallback() called successfully.11-04 01:38:09.612: I/ActivityManager(628): Process com.bittorrent.sync (pid 16269) has died.11-04 01:38:09.612: I/WindowState(628): WIN DEATH: Window{429ed518 u0 com.bittorrent.sync/com.bittorrent.sync.ui.activity.MainActivity}11-04 01:38:09.612: W/ActivityManager(628): Force removing ActivityRecord{42a3cee0 u0 com.bittorrent.sync/.ui.activity.MainActivity t9}: app died, no saved state11-04 01:38:09.682: D/Zygote(199): Process 16269 terminated by signal (11)Any help is appreciated. Quote Link to comment Share on other sites More sharing options...
andyli Posted November 7, 2014 Author Report Share Posted November 7, 2014 Ahh, it works again after I reinstalled the app. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.