Related
Ok, so I got this after reinstalling Cyanogen's 4.1.10.1 after installing a theme on top of it. So far I've tried wiping, restoring a backup, and installing multiple builds, no success.
Heres the logcat:
Code:
W/dalvikvm( 136): JNI_CreateJavaVM failed
E/AndroidRuntime( 136): JNI_CreateJavaVM failed
D/AndroidRuntime( 140):
D/AndroidRuntime( 140): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 140): CheckJNI is OFF
D/dalvikvm( 140): DexOpt: incorrect opt magic number (0xff ff ff ff)
D/dalvikvm( 140): Stale deps in cache file; removing and retrying
D/dalvikvm( 140): DexOpt: --- BEGIN 'services.jar' (bootstrap=1) ---
I/DEBUG ( 116): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *
**
I/DEBUG ( 116): Build fingerprint: 'tmobile/kila/dream/trout:1.5/CRC1/150275:
user/ota-rel-keys,release-keys'
I/DEBUG ( 116): pid: 142, tid: 142 >>> /system/bin/dexopt <<<
I/DEBUG ( 116): signal 11 (SIGSEGV), fault addr 44b60a42
I/DEBUG ( 116): r0 0000ea74 r1 415d0028 r2 41613df0 r3 44b60a42
I/DEBUG ( 116): r4 41051528 r5 00016510 r6 4000c358 r7 bedef9dc
I/DEBUG ( 116): r8 00000000 r9 00000000 10 00000000 fp 00000000
I/DEBUG ( 116): ip ad07a0d0 sp bedef980 lr ad053349 pc ad052c5c cpsr 000
00030
I/DEBUG ( 116): #00 pc 00052c5c /system/lib/libdvm.so
I/DEBUG ( 116): #01 pc 00053344 /system/lib/libdvm.so
I/DEBUG ( 116): #02 pc 00053506 /system/lib/libdvm.so
I/DEBUG ( 116): #03 pc 00053c2e /system/lib/libdvm.so
I/DEBUG ( 116): #04 pc 00053e3e /system/lib/libdvm.so
I/DEBUG ( 116): #05 pc 00054352 /system/lib/libdvm.so
I/DEBUG ( 116): #06 pc 000471da /system/lib/libdvm.so
I/DEBUG ( 116): #07 pc 000476d4 /system/lib/libdvm.so
I/DEBUG ( 116): #08 pc 000478b4 /system/lib/libdvm.so
I/DEBUG ( 116): #09 pc 00008e20 /system/bin/dexopt
I/DEBUG ( 116): #10 pc 00008ed6 /system/bin/dexopt
I/DEBUG ( 116): #11 pc 0000bf12 /system/lib/libc.so
I/DEBUG ( 116): #12 pc b00016cc /system/bin/linker
I/DEBUG ( 116): stack:
I/DEBUG ( 116): bedef940 00000000
I/DEBUG ( 116): bedef944 afe0ec28 /system/lib/libc.so
I/DEBUG ( 116): bedef948 000119c4 [heap]
I/DEBUG ( 116): bedef94c afe0ed18 /system/lib/libc.so
I/DEBUG ( 116): bedef950 00000000
I/DEBUG ( 116): bedef954 afe0ec28 /system/lib/libc.so
I/DEBUG ( 116): bedef958 000119c0 [heap]
I/DEBUG ( 116): bedef95c ad079e1c /system/lib/libdvm.so
I/DEBUG ( 116): bedef960 000014b4
I/DEBUG ( 116): bedef964 0000216c
I/DEBUG ( 116): bedef968 410514f0 /dev/ashmem/dalvik-LinearAlloc (delet
ed)
I/DEBUG ( 116): bedef96c ad051ba5 /system/lib/libdvm.so
I/DEBUG ( 116): bedef970 410514f0 /dev/ashmem/dalvik-LinearAlloc (delet
ed)
I/DEBUG ( 116): bedef974 00016510 [heap]
I/DEBUG ( 116): bedef978 df002777
I/DEBUG ( 116): bedef97c e3a070ad
I/DEBUG ( 116): #00 bedef980 ad079e1c /system/lib/libdvm.so
I/DEBUG ( 116): bedef984 41051504 /dev/ashmem/dalvik-LinearAlloc (delet
ed)
I/DEBUG ( 116): bedef988 41641118 /data/dalvik-cache/[email protected]@c
[email protected]
I/DEBUG ( 116): bedef98c 4000c358 /dev/ashmem/mspace/dalvik-heap/0 (del
eted)
I/DEBUG ( 116): bedef990 4191a361 /data/dalvik-cache/[email protected]@c
[email protected]
I/DEBUG ( 116): bedef994 00016510 [heap]
I/DEBUG ( 116): bedef998 41641118 /data/dalvik-cache/[email protected]@c
[email protected]
I/DEBUG ( 116): bedef99c ad053349 /system/lib/libdvm.so
I/DEBUG ( 116): #01 bedef9a0 00002bd0
I/DEBUG ( 116): bedef9a4 000000dc
I/DEBUG ( 116): bedef9a8 00000000
I/DEBUG ( 116): bedef9ac afe0afbb /system/lib/libc.so
I/DEBUG ( 116): bedef9b0 42409e54 /data/dalvik-cache/[email protected]@s
[email protected]
I/DEBUG ( 116): bedef9b4 0000003a
I/DEBUG ( 116): bedef9b8 bedef9dc [stack]
I/DEBUG ( 116): bedef9bc 00000abe
I/DEBUG ( 116): bedef9c0 00000460
I/DEBUG ( 116): bedef9c4 00000b05
I/DEBUG ( 116): bedef9c8 00000002
I/DEBUG ( 116): bedef9cc 00000070
I/DEBUG ( 116): bedef9d0 415fdbf0 /data/dalvik-cache/[email protected]@c
[email protected]
I/DEBUG ( 116): bedef9d4 4000c3f4 /dev/ashmem/mspace/dalvik-heap/0 (del
eted)
I/DEBUG ( 116): bedef9d8 afe3bb8c
I/DEBUG ( 116): bedef9dc 00000abe
I/DEBUG ( 116): bedef9e0 00000000
I/DEBUG ( 116): bedef9e4 000be364
I/DEBUG ( 116): bedef9e8 00000722
I/DEBUG ( 116): bedef9ec ad079e1c /system/lib/libdvm.so
I/DEBUG ( 116): bedef9f0 00016578 [heap]
I/DEBUG ( 116): bedef9f4 41641118 /data/dalvik-cache/[email protected]@c
[email protected]
I/DEBUG ( 116): bedef9f8 00000000
I/DEBUG ( 116): bedef9fc ad05350b /system/lib/libdvm.so
W/dalvikvm( 140): DexOpt: --- END 'services.jar' --- status=0x000b, process fai
led
E/dalvikvm( 140): Unable to extract+optimize DEX from '/system/framework/servic
es.jar'
D/dalvikvm( 140): Failed on '/system/framework/services.jar' (boot=1)
D/dalvikvm( 140): VM cleaning up
D/dalvikvm( 140): LinearAlloc 0x0 used 4100 of 4194304 (0%)
and repeats over and over... forever!
I've searched through the forums and on google and nothing relevant came up. Please help!
Ok, tried deleting the Dalvik-Cache from recovery console with no success. Formatted my linux parts and bam! fixed.
If your sdcard is partitioned try wiping your ext3, then trying flashing cm 4.0.4, if it still boot loops then you may need to go back to rc-29 and root again
david1171 said:
If your sdcard is partitioned try wiping your ext3, then trying flashing cm 4.0.4, if it still boot loops then you may need to go back to rc-29 and root again
Click to expand...
Click to collapse
Whats up david, glad you could finally join us. Must be nice to sleep in til noon.
nick_karstedt said:
Ok, tried deleting the Dalvik-Cache from recovery console with no success. Formatted my linux parts and bam! fixed.
Click to expand...
Click to collapse
Ive got the same problem along with several other people on this forum but none of us have been able to sort this out.
So pray tell how do you format linux parts?
Hello,
since the weekend m G1 (with Cyanogen 4.2.13) is suffering some bad errors.
It happens, that it just freezes.
activating adb logcat it gives me this output (which gets repeated in a two seconds cycle).
D/AndroidRuntime( 1476):
D/AndroidRuntime( 1476): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1476): CheckJNI is OFF
E/dalvikvm( 1476): opt header write failed: I/O error
I/dalvikvm( 1476): Unable to open or create cache for /system/framework/core.jar
(/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1476): Unable to process classpath element '/system/framework/core.j
ar'
E/dalvikvm( 1476): opt header write failed: I/O error
I/dalvikvm( 1476): Unable to open or create cache for /system/framework/ext.jar
(/data/dalvik-cache/[email protected][email protected]@classes.dex)
D/dalvikvm( 1476): Unable to process classpath element '/system/framework/ext.ja
r'
E/dalvikvm( 1476): opt header write failed: I/O error
I/dalvikvm( 1476): Unable to open or create cache for /system/framework/framewor
k.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1476): Unable to process classpath element '/system/framework/framew
ork.jar'
E/dalvikvm( 1476): opt header write failed: I/O error
I/dalvikvm( 1476): Unable to open or create cache for /system/framework/android.
policy.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1476): Unable to process classpath element '/system/framework/androi
d.policy.jar'
E/dalvikvm( 1476): opt header write failed: I/O error
I/dalvikvm( 1476): Unable to open or create cache for /system/framework/services
.jar (/data/dalvik-cache/[email protected]@[email protected])
D/dalvikvm( 1476): Unable to process classpath element '/system/framework/servic
es.jar'
E/dalvikvm( 1476): ERROR: no valid entries found in bootclasspath '/system/frame
work/core.jar:/system/framework/ext.jar:/system/framework/framework.jar:/system/
framework/android.policy.jar:/system/framework/services.jar'
D/dalvikvm( 1476): VM cleaning up
D/dalvikvm( 1476): LinearAlloc 0x0 used 4100 of 5242880 (0%)
W/dalvikvm( 1476): JNI_CreateJavaVM failed
E/AndroidRuntime( 1476): JNI_CreateJavaVM failed
Click to expand...
Click to collapse
Does anyone have a hint whats failing here?
-Radioactive Man
Just a guess, but probably an I/O error.
opt header write failed: I/O error
Click to expand...
Click to collapse
and what does it mean? broken sdcard? broken internal memory? something else broken?
Now I get another output:
D/AndroidRuntime( 1392):
D/AndroidRuntime( 1392): >>>>>>>>>>>>>> AndroidRuntime START <<<<<<<<<<<<<<
D/AndroidRuntime( 1392): CheckJNI is OFF
I/DEBUG ( 1342): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 1342): Build fingerprint: 'tmobile/kila/dream/trout:1.6/DRC83/14721:user/ota-rel-keys,re
lease-keys'
I/DEBUG ( 1342): pid: 1392, tid: 1392 >>> zygote <<<
I/DEBUG ( 1342): signal 7 (SIGBUS), fault addr 41a2633b
I/DEBUG ( 1342): r0 00015d80 r1 41a2633b r2 00015d18 r3 00352313
I/DEBUG ( 1342): r4 ad07ff50 r5 00015d80 r6 41746010 r7 00000000
I/DEBUG ( 1342): r8 00000000 r9 00000000 10 00000000 fp 00000000
I/DEBUG ( 1342): ip ad080214 sp be94b828 lr ad058471 pc ad057bd6 cpsr 20000030
I/DEBUG ( 1342): #00 pc 00057bd6 /system/lib/libdvm.so
I/DEBUG ( 1342): #01 pc 0005846c /system/lib/libdvm.so
I/DEBUG ( 1342): #02 pc 0005867e /system/lib/libdvm.so
I/DEBUG ( 1342): #03 pc 00040690 /system/lib/libdvm.so
I/DEBUG ( 1342): #04 pc 0003681c /system/lib/libdvm.so
I/DEBUG ( 1342): #05 pc 000384b2 /system/lib/libdvm.so
I/DEBUG ( 1342): #06 pc 00028d7e /system/lib/libandroid_runtime.so
I/DEBUG ( 1342): #07 pc 00008c9e /system/bin/app_process
I/DEBUG ( 1342): #08 pc 0000c4c2 /system/lib/libc.so
I/DEBUG ( 1342): #09 pc b00018c6 /system/bin/linker
I/DEBUG ( 1342): stack:
I/DEBUG ( 1342): be94b7e8 000081a4 /system/bin/app_process
I/DEBUG ( 1342): be94b7ec 00000001
I/DEBUG ( 1342): be94b7f0 00000000
I/DEBUG ( 1342): be94b7f4 00000000
I/DEBUG ( 1342): be94b7f8 afe3bc10
I/DEBUG ( 1342): be94b7fc afe0f370 /system/lib/libc.so
I/DEBUG ( 1342): be94b800 00000000
I/DEBUG ( 1342): be94b804 afe0f280 /system/lib/libc.so
I/DEBUG ( 1342): be94b808 41a5f3b0 /data/dalvik-cache/[email protected]@[email protected]
I/DEBUG ( 1342): be94b80c ad05f32f /system/lib/libdvm.so
I/DEBUG ( 1342): be94b810 00001df2
I/DEBUG ( 1342): be94b814 00001fff
I/DEBUG ( 1342): be94b818 416d4028 /data/dalvik-cache/[email protected]@[email protected]
I/DEBUG ( 1342): be94b81c ad0735bc /system/lib/libdvm.so
I/DEBUG ( 1342): be94b820 df002777
I/DEBUG ( 1342): be94b824 e3a070ad
I/DEBUG ( 1342): #00 be94b828 ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 1342): be94b82c 00015d80 [heap]
I/DEBUG ( 1342): be94b830 ad0735bc /system/lib/libdvm.so
I/DEBUG ( 1342): be94b834 ad056843 /system/lib/libdvm.so
I/DEBUG ( 1342): be94b838 00000002
I/DEBUG ( 1342): be94b83c ad06587c /system/lib/libdvm.so
I/DEBUG ( 1342): be94b840 be94b874 [stack]
I/DEBUG ( 1342): be94b844 ad074a04 /system/lib/libdvm.so
I/DEBUG ( 1342): be94b848 00015a60 [heap]
I/DEBUG ( 1342): be94b84c 00000000
I/DEBUG ( 1342): be94b850 0000bc20 [heap]
I/DEBUG ( 1342): be94b854 ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 1342): be94b858 00015d80 [heap]
I/DEBUG ( 1342): be94b85c ad058471 /system/lib/libdvm.so
I/DEBUG ( 1342): #01 be94b860 00015a58 [heap]
I/DEBUG ( 1342): be94b864 00015a60 [heap]
I/DEBUG ( 1342): be94b868 ad0735bc /system/lib/libdvm.so
I/DEBUG ( 1342): be94b86c 00000000
I/DEBUG ( 1342): be94b870 ad06587c /system/lib/libdvm.so
I/DEBUG ( 1342): be94b874 41746010 /data/dalvik-cache/[email protected]@[email protected]
I/DEBUG ( 1342): be94b878 000111b8 [heap]
I/DEBUG ( 1342): be94b87c ad07ff50 /system/lib/libdvm.so
I/DEBUG ( 1342): be94b880 00000354
I/DEBUG ( 1342): be94b884 0000a9c0 [heap]
I/DEBUG ( 1342): be94b888 fffec080
I/DEBUG ( 1342): be94b88c ad058683 /system/lib/libdvm.so
Click to expand...
Click to collapse
what is happening with my phone?
Have you messed with anything lately, new boot image, removed system apps, went to an eclair ROM and back, metamorphed, themed, etc?
cloverdale said:
Have you messed with anything lately, new boot image, removed system apps, went to an eclair ROM and back, metamorphed, themed, etc?
Click to expand...
Click to collapse
Nothing like that. I only have installed Cyanogen and a few apps from market. Nothing special as I think.
I have had this happen in only three cases:
1.) I tried adding framework that was not compatible with my ROM.
2.) I tried adding a launcher that was not compatible.
3.) I tried coming to a new ROM without a fresh format of my ext partition on my sdcard.
In all cases a fresh wipe of the phone and re-format of the sd ext partition fixed it.
cloverdale said:
I have had this happen in only three cases:
1.) I tried adding framework that was not compatible with my ROM.
2.) I tried adding a launcher that was not compatible.
3.) I tried coming to a new ROM without a fresh format of my ext partition on my sdcard.
In all cases a fresh wipe of the phone and re-format of the sd ext partition fixed it.
Click to expand...
Click to collapse
Might be a theme he's using that's not for the version or a metamorph that's for a older cyan.I remember I had something similar to this.
Ace42 said:
Might be a theme he's using that's not for the version or a metamorph that's for a older cyan.I remember I had something similar to this.
Click to expand...
Click to collapse
Good call. I second this.
Ace42 said:
Might be a theme he's using that's not for the version or a metamorph that's for a older cyan.I remember I had something similar to this.
Click to expand...
Click to collapse
well, I doubt it as I have never installed any theme so far. I will see if it happens again and if so I will try to make a fresh reinstall.
Does anyone have any ideas why Slingplayer wont work on any of the ROMs for the GTablet?
As soon as you click on the icon to launch the app, the screen goes black and then goes right back to the launcher.
Any ideas?
Thanks in advance!
boostenmkiv said:
Does anyone have any ideas why Slingplayer wont work on any of the ROMs for the GTablet?
As soon as you click on the icon to launch the app, the screen goes black and then goes right back to the launcher.
Any ideas?
Thanks in advance!
Click to expand...
Click to collapse
I tried sideloding it with the same results. I could not find it when searching the market. I did read today that it is working on the Archos 101. So, I would think there should be a way to get it working.
birchs said:
I tried sideloding it with the same results. I could not find it when searching the market. I did read today that it is working on the Archos 101. So, I would think there should be a way to get it working.
Click to expand...
Click to collapse
Did you try running logcat then starting the app to see if it is logging what's failing??
I am running tapntap lite 2 and I can run my slingbox client. I have to try it several times but it does load. May sound crazy but when I run quick reboot right before I start trying i have better luck getting it to run. After it runs the first time its fine till a full reboot.
wlawyer said:
I am running tapntap lite 2 and I can run my slingbox client. I have to try it several times but it does load. May sound crazy but when I run quick reboot right before I start trying i have better luck getting it to run. After it runs the first time its fine till a full reboot.
Click to expand...
Click to collapse
thanks for the info. I'll be more persistent to see if i can get it to work.
jtbnet said:
Did you try running logcat then starting the app to see if it is logging what's failing??
Click to expand...
Click to collapse
sorry, that's beyond my skill level at the moment
wlawyer said:
I am running tapntap lite 2 and I can run my slingbox client. I have to try it several times but it does load. May sound crazy but when I run quick reboot right before I start trying i have better luck getting it to run. After it runs the first time its fine till a full reboot.
Click to expand...
Click to collapse
Holy Crap that worked. I just had to try it a few times and finally the log in screen came up. Once it is running works nicely! Thanks for the tip!
sling player
It works, but you have to try to launch it atleast 10x, then it catches. Not sure what's going on with that, but it does work great after that.
Hopefully someone has the SDK loaded and can run 'adb logcat' and maybe catch the errors the times it fails... it might be a fairly obvious error if we were to see it
The Dish Network Remote app (probably nearly the same thing) has the same problem when using the Zpad firmware, but it works fine using the TnT firmware.
jtbnet et al.
Wow, adb was MUCH harder to get working on this tablet than any previous android phone i've worked on. (mt3g,n1,DI,Droid,DX)
anyhow, here is the log:
D/WifiService( 884): acquireWifiLockLocked: WifiLock{SlingWifiTag type=1 [email protected]}
D/dalvikvm( 4940): Trying to load lib /data/data/com.slingmedia.slingPlayer/lib/libspsdk.so 0x4619e5d0
D/dalvikvm( 4940): Added shared lib /data/data/com.slingmedia.slingPlayer/lib/libspsdk.so 0x4619e5d0
W/dalvikvm( 4940): JNI WARNING: illegal class name 'com.slingmedia.slingPlayer.SPEKHandler.PlayerEngine.AudioPlayer' (Check_FindClass)
W/dalvikvm( 4940): (should be formed like 'java/lang/String')
I/dalvikvm( 4940): "main" prio=5 tid=1 NATIVE
I/dalvikvm( 4940): | group="main" sCount=0 dsCount=0 s=N obj=0x4001d900 self=0xccd8
I/dalvikvm( 4940): | sysTid=4940 nice=1 sched=0/0 cgrp=default handle=-1345017812
I/dalvikvm( 4940): | schedstat=( 57004000 11633000 68 )
I/dalvikvm( 4940): at java.lang.Runtime.nativeLoad(Native Method)
I/dalvikvm( 4940): at java.lang.Runtime.loadLibrary(Runtime.java:448)
I/dalvikvm( 4940): at java.lang.System.loadLibrary(System.java:557)
I/dalvikvm( 4940): at com.slingmedia.slingPlayer.SPEKHandler.PlayerEngine.PlayerEngine.<clinit>(PlayerEngine.java:1330)
I/dalvikvm( 4940): at com.slingmedia.slingPlayer.SlingPlayerApplication.onCreate(SlingPlayerApplication.java:-1)
I/dalvikvm( 4940): at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:969)
I/dalvikvm( 4940): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4244)
I/dalvikvm( 4940): at android.app.ActivityThread.access$3000(ActivityThread.java:125)
I/dalvikvm( 4940): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2071)
I/dalvikvm( 4940): at android.os.Handler.dispatchMessage(Handler.java:99)
I/dalvikvm( 4940): at android.os.Looper.loop(Looper.java:123)
I/dalvikvm( 4940): at android.app.ActivityThread.main(ActivityThread.java:4627)
I/dalvikvm( 4940): at java.lang.reflect.Method.invokeNative(Native Method)
I/dalvikvm( 4940): at java.lang.reflect.Method.invoke(Method.java:521)
I/dalvikvm( 4940): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:868)
I/dalvikvm( 4940): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:626)
I/dalvikvm( 4940): at dalvik.system.NativeStart.main(Native Method)
I/dalvikvm( 4940):
E/dalvikvm( 4940): VM aborting
I/DEBUG ( 837): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 837): Build fingerprint: 'nvidia/harmony/harmony/:2.2/FRF91/eng.build.20101107.131556:eng/'
I/DEBUG ( 837): pid: 4940, tid: 4940 >>> com.slingmedia.slingPlayer <<<
I/DEBUG ( 837): signal 11 (SIGSEGV), fault addr deadd00d
I/DEBUG ( 837): r0 00000026 r1 afd148c9 r2 afd148c9 r3 00000000
I/DEBUG ( 837): r4 808a13f4 r5 80883ad0 r6 80e5462c r7 80cf2dc9
I/DEBUG ( 837): r8 80816fc0 r9 0000ccd8 10 4208bc7c fp 00000000
I/DEBUG ( 837): ip deadd00d sp bef11150 lr afd1591f pc 808417a4 cpsr 20000030
I/DEBUG ( 837): d0 0000006a42d40000 d1 3ff0000042d40000
I/DEBUG ( 837): d2 0000000050baf6de d3 0000000000000000
I/DEBUG ( 837): d4 0000001a000000b4 d5 3fe999999999999a
I/DEBUG ( 837): d6 3fe8000000000000 d7 3eaaaaab3f800000
I/DEBUG ( 837): d8 0000000000000000 d9 0000000000000000
I/DEBUG ( 837): d10 0000000000000000 d11 0000000000000000
I/DEBUG ( 837): d12 0000000000000000 d13 0000000000000000
I/DEBUG ( 837): d14 0000000000000000 d15 0000000000000000
I/DEBUG ( 837): scr 80000012
I/DEBUG ( 837):
I/DEBUG ( 837): #00 pc 000417a4 /system/lib/libdvm.so
I/DEBUG ( 837): #01 pc 00032bea /system/lib/libdvm.so
I/DEBUG ( 837): #02 pc 00033a4c /system/lib/libdvm.so
I/DEBUG ( 837): #03 pc 00033ad4 /system/lib/libdvm.so
I/DEBUG ( 837): #04 pc 000f2dec /data/data/com.slingmedia.slingPlayer/lib/libspsdk.so
I/DEBUG ( 837): #05 pc 00049c28 /system/lib/libdvm.so
I/DEBUG ( 837): #06 pc 000635d8 /system/lib/libdvm.so
I/DEBUG ( 837): #07 pc 0001bd58 /system/lib/libdvm.so
I/DEBUG ( 837): #08 pc 00022744 /system/lib/libdvm.so
I/DEBUG ( 837): #09 pc 000215e0 /system/lib/libdvm.so
I/DEBUG ( 837): #10 pc 0005bcb6 /system/lib/libdvm.so
I/DEBUG ( 837): #11 pc 0005bee8 /system/lib/libdvm.so
I/DEBUG ( 837): #12 pc 00067b48 /system/lib/libdvm.so
I/DEBUG ( 837): #13 pc 000694d2 /system/lib/libdvm.so
I/DEBUG ( 837): #14 pc 00018c28 /system/lib/libdvm.so
I/DEBUG ( 837): #15 pc 00022744 /system/lib/libdvm.so
I/DEBUG ( 837): #16 pc 000215e0 /system/lib/libdvm.so
I/DEBUG ( 837): #17 pc 0005be78 /system/lib/libdvm.so
I/DEBUG ( 837): #18 pc 000643fe /system/lib/libdvm.so
I/DEBUG ( 837): #19 pc 0001bd58 /system/lib/libdvm.so
I/DEBUG ( 837): #20 pc 00022744 /system/lib/libdvm.so
I/DEBUG ( 837): #21 pc 000215e0 /system/lib/libdvm.so
I/DEBUG ( 837): #22 pc 0005bcb6 /system/lib/libdvm.so
I/DEBUG ( 837): #23 pc 00047362 /system/lib/libdvm.so
I/DEBUG ( 837): #24 pc 0003a51c /system/lib/libdvm.so
I/DEBUG ( 837): #25 pc 0002db88 /system/lib/libandroid_runtime.so
I/DEBUG ( 837): #26 pc 0002ec7c /system/lib/libandroid_runtime.so
I/DEBUG ( 837): #27 pc 00008caa /system/bin/app_process
I/DEBUG ( 837): #28 pc 0000d3d8 /system/lib/libc.so
I/DEBUG ( 837):
I/DEBUG ( 837): code around pc:
I/DEBUG ( 837): 80841784 18612006 f7d418a2 2000eff8 e950f7d5
I/DEBUG ( 837): 80841794 58234808 b1036bdb 20264798 c018f8df
I/DEBUG ( 837): 808417a4 0000f88c e9b6f7d5 fffe26dc 0005fc78
I/DEBUG ( 837): 808417b4 fffe5950 0000039c deadd00d f8dfb40e
I/DEBUG ( 837): 808417c4 b503c02c 490aa200 aa03188b 1b04f852
I/DEBUG ( 837):
I/DEBUG ( 837): code around lr:
I/DEBUG ( 837): afd158fc 4b0db5f7 490da200 2600189b 585c4602
I/DEBUG ( 837): afd1590c 686768a5 f9b5e008 b120000c 46289201
I/DEBUG ( 837): afd1591c 9a014790 35544306 37fff117 6824d5f3
I/DEBUG ( 837): afd1592c d1ed2c00 bdfe4630 0002ca24 000000d4
I/DEBUG ( 837): afd1593c fb01b570 b086f602 9004460c a804a901
I/DEBUG ( 837):
I/DEBUG ( 837): stack:
I/DEBUG ( 837): bef11110 00000015
I/DEBUG ( 837): bef11114 afd148f9 /system/lib/libc.so
I/DEBUG ( 837): bef11118 afd42498 /system/lib/libc.so
I/DEBUG ( 837): bef1111c afd43b70 /system/lib/libc.so
I/DEBUG ( 837): bef11120 00000000
I/DEBUG ( 837): bef11124 afd1591f /system/lib/libc.so
I/DEBUG ( 837): bef11128 afd148c9 /system/lib/libc.so
I/DEBUG ( 837): bef1112c afd148c9 /system/lib/libc.so
I/DEBUG ( 837): bef11130 afd14920 /system/lib/libc.so
I/DEBUG ( 837): bef11134 808a13f4 /system/lib/libdvm.so
I/DEBUG ( 837): bef11138 80883ad0 /system/lib/libdvm.so
I/DEBUG ( 837): bef1113c 80e5462c /data/data/com.slingmedia.slingPlayer/lib/libspsdk.so
I/DEBUG ( 837): bef11140 80cf2dc9 /data/data/com.slingmedia.slingPlayer/lib/libspsdk.so
I/DEBUG ( 837): bef11144 afd1492b /system/lib/libc.so
I/DEBUG ( 837): bef11148 df002777
I/DEBUG ( 837): bef1114c e3a070ad
I/DEBUG ( 837): #00 bef11150 808a13f4 /system/lib/libdvm.so
I/DEBUG ( 837): bef11154 80832bef /system/lib/libdvm.so
I/DEBUG ( 837): #01 bef11158 808a13f4 /system/lib/libdvm.so
I/DEBUG ( 837): bef1115c 80833a51 /system/lib/libdvm.so
I/BootReceiver( 884): Copying /data/tombstones/tombstone_01 to DropBox (SYSTEM_TOMBSTONE)
D/Zygote ( 839): Process 4940 terminated by signal (11)
D/dalvikvm( 884): GC_FOR_MALLOC freed 4784 objects / 1053840 bytes in 45ms
D/WifiService( 884): releaseWifiLockLocked: WifiLock{SlingWifiTag type=1 [email protected]}
I/ActivityManager( 884): Process com.slingmedia.slingPlayer (pid 4940) has died.
I/UsageStats( 884): Unexpected resume of com.android.launcher while already resumed in com.slingmedia.slingPlayer
W/InputManagerService( 884): Window already focused, ignoring focus gain of: [email protected]
D/WifiService( 884): ACTION_BATTERY_CHANGED pluggedType: 0
Well the short of this...
D/WifiService( 884): acquireWifiLockLocked: WifiLock{SlingWifiTag type=1 [email protected]}
D/dalvikvm( 4940): Trying to load lib /data/data/com.slingmedia.slingPlayer/lib/libspsdk.so 0x4619e5d0
D/dalvikvm( 4940): Added shared lib /data/data/com.slingmedia.slingPlayer/lib/libspsdk.so 0x4619e5d0
W/dalvikvm( 4940): JNI WARNING: illegal class name 'com.slingmedia.slingPlayer.SPEKHandler.PlayerEngi ne.AudioPlayer' (Check_FindClass)
W/dalvikvm( 4940): (should be formed like 'java/lang/String')
I/dalvikvm( 4940): "main" prio=5 tid=1 NATIVE
I/dalvikvm( 4940): | group="main" sCount=0 dsCount=0 s=N obj=0x4001d900 self=0xccd8
I/dalvikvm( 4940): | sysTid=4940 nice=1 sched=0/0 cgrp=default handle=-1345017812
I/dalvikvm( 4940): | schedstat=( 57004000 11633000 68 )
I/dalvikvm( 4940): at java.lang.Runtime.nativeLoad(Native Method)
...
The call to a function ('com.slingmedia.slingPlayer.SPEKHandler.PlayerEngi ne.AudioPlayer') in libspsdk.so is failing based on the way the call was made...
W/dalvikvm( 4940): JNI WARNING: illegal class name 'com.slingmedia.slingPlayer.SPEKHandler.PlayerEngi ne.AudioPlayer' (Check_FindClass)
W/dalvikvm( 4940): (should be formed like 'java/lang/String')
I'm not sure why if you run this 10 or more times it finally works... But JAVA/JNI is not my forte... hopefully this info will provide more info to someone more versed in this...
disabled stagefright in build.prop and slingplayer streams flawlessly and opens on the first try.... with stagefright enabled it takes about 10 tries before davlik vm stops calling abort, and even then it plays choppy... anyone elsewant to disable stagefright and see if you get results like mine?
im running latest tnt lite with experimental upgrade
Sent from my GTablet-TnT-Lite using Tapatalk
TheTruth said:
disabled stagefright in build.prop and slingplayer streams flawlessly and opens on the first try.... with stagefright enabled it takes about 10 tries before davlik vm stops calling abort, and even then it plays choppy... anyone elsewant to disable stagefright and see if you get results like mine?
im running latest tnt lite with experimental upgrade
Sent from my GTablet-TnT-Lite using Tapatalk
Click to expand...
Click to collapse
Can someone tell me how to disable stagefright ? Thanks!
make sure you have root.
use rootexplorer or similar and browse to the /system/ folder on your internal storage.
click the mount r/w button, click on the build.prop file and open it as a text file.
scroll down in the build.prop file and change the values from true to false... save then reboot.
this will make slingplayer playback smooth but will not impact the other issue of davlik aborting the process (which is why we have to keep opening the app till it sticks)
Sent from my GTablet-TnT-Lite using Tapatalk
TheTruth said:
make sure you have root.
use rootexplorer or similar and browse to the /system/ folder on your internal storage.
click the mount r/w button, click on the build.prop file and open it as a text file.
scroll down in the build.prop file and change the values from true to false... save then reboot.
this will make slingplayer playback smooth but will not impact the other issue of davlik aborting the process (which is why we have to keep opening the app till it sticks)
Sent from my GTablet-TnT-Lite using Tapatalk
Click to expand...
Click to collapse
I disabled all stagefright option in the build.prop but no change after a reboot.
wlawyer said:
I disabled all stagefright option in the build.prop but no change after a reboot.
Click to expand...
Click to collapse
odd, with stagefright sling is a slideshow... stagefright off and it plays like a dream... but still no impact on the abort () called by dalvik vm... perhaps a setting added to build.prop that disables jni checking would work... but that would make the system unstable if bad or unsupported code happened to be around..
Sent from my GTablet-TnT-Lite using Tapatalk
jtbnet said:
The call to a function ('com.slingmedia.slingPlayer.SPEKHandler.PlayerEngi ne.AudioPlayer') in libspsdk.so is failing based on the way the call was made...
W/dalvikvm( 4940): JNI WARNING: illegal class name 'com.slingmedia.slingPlayer.SPEKHandler.PlayerEngi ne.AudioPlayer' (Check_FindClass)
W/dalvikvm( 4940): (should be formed like 'java/lang/String')
I'm not sure why if you run this 10 or more times it finally works... But JAVA/JNI is not my forte... hopefully this info will provide more info to someone more versed in this...
Click to expand...
Click to collapse
I was doing some research on this error and found this.
it looks like you are using "." as a
separator instead of "/". ("." is Java surface syntax for separating
package names, but "/" is what is used at the API boundary.) So, I
would check to make sure that your JNI registration code is
well-formed.
Click to expand...
Click to collapse
I still don't have my tablet, but sling player is an important feature to me on it.
TheTruth said:
odd, with stagefright sling is a slideshow... stagefright off and it plays like a dream... but still no impact on the abort () called by dalvik vm... perhaps a setting added to build.prop that disables jni checking would work... but that would make the system unstable if bad or unsupported code happened to be around..
Sent from my GTablet-TnT-Lite using Tapatalk
Click to expand...
Click to collapse
Try to add "dalvik.vm.checkjni=false" to build.prop and reboot. That might do it.
Edit, if that doesn't work try "ro.kernel.android.checkjni=false"
If this works when set, it may explain problems with other apps people are having. According to here, jni checking should only be enabled on dev units.
I just checked boot.img and "-Xcheck:jni" is passed when it starts.
Adam B. said:
I was doing some research on this error and found this.
I still don't have my tablet, but sling player is an important feature to me on it.
I extracted and hex edited the library to use slashes for that class. Can someone with adb test this out (you'll probably have to uninstall the old version first)? I tested it on my droid and it worked, but it never had a problem on there.
Click to expand...
Click to collapse
Tested the edited sling apk for you. Still took about 6 or 7 attempts before it opened.
Also it forced closed after I selected my slingbox...never made it to video
harpua1980 said:
Tested the edited sling apk for you. Still took about 6 or 7 attempts before it opened.
Also it forced closed after I selected my slingbox...never made it to video
Click to expand...
Click to collapse
Thanks.
I think we're better off with the build.prop fix anyway. Can you test that?
Hi there, actually no problems on my moto x with stock rom and xposed but watching log there is a fatal signal logged. Can't find nothing on google inside xda, my 2 modules are running good, no battery drain, no warm device only these two lines.
Can somebody explain, in few words, what this means?
Good night
michyall said:
Hi there, actually no problems on my moto x with stock rom and xposed but watching log there is a fatal signal logged. Can't find nothing on google inside xda, my 2 modules are running good, no battery drain, no warm device only these two lines.
Can somebody explain, in few words, what this means?
Good night
Click to expand...
Click to collapse
Well, "fatal signal" in Linux/Android terms means the process died or crashed. The "F/libc" means the fatal crash occurred in the libc library.
I also get these errors on my Moto X. I suspect it has something to do with us using Android 5.0 since most other Lollipop phones are on 5.0.1 or 5.0.2. My log contains a bit more information, notably the backtrace, which indicates this is occurring in dex2oat (one of the files replaced by Xposed).
Code:
11-20 00:00:01.980 I/Xposed ( 385): -----------------
11-20 00:00:01.980 I/Xposed ( 385): Starting Xposed binary version 60, compiled for SDK 21
11-20 00:00:01.980 I/Xposed ( 385): Phone: XT1095 (motorola), Android version 5.0 (SDK 21)
11-20 00:00:01.980 I/Xposed ( 385): ROM: LXE22.46-11
11-20 00:00:01.980 I/Xposed ( 385): Build fingerprint: motorola/victara_tmo/victara:5.0/LXE22.46-11/10:user/release-keys
11-20 00:00:01.980 I/Xposed ( 385): Platform: armeabi-v7a, 32-bit binary, system server: yes
11-20 00:00:01.980 I/Xposed ( 385): SELinux enabled: yes, enforcing: yes
02-14 12:04:48.293 I/Xposed ( 385): -----------------
02-14 12:04:48.298 I/Xposed ( 385): Added Xposed (/system/framework/XposedBridge.jar) to CLASSPATH
02-14 12:04:48.709 I/Xposed ( 385): Detected ART runtime
02-14 12:04:48.735 I/Xposed ( 385): Found Xposed class de/robv/android/xposed/XposedBridge, now initializing
02-14 12:04:48.919 I/Xposed ( 385): Initializing XposedBridge version 61
02-14 12:04:49.038 I/Xposed ( 385): Loading modules from /data/app/com.oasisfeng.greenify-2/base.apk
02-14 12:04:49.237 I/Xposed ( 385): Loading class com.oasisfeng.greenify.pro.FrameworkPatch
02-14 12:04:49.261 I/Xposed ( 385): Loading class com.oasisfeng.greenify.pro.SettingsPatch
02-14 23:02:35.698 F/libc (12653): Fatal signal 11 (SIGSEGV), code 2, fault addr 0xb32050c0 in tid 12653 (main)
02-14 23:02:35.698 F/libc (12653): Fatal signal 11 (SIGSEGV), code 2, fault addr 0xb3221eae in tid 12657 (Compiler driver)
02-14 23:02:35.698 F/libc (12653): Fatal signal 11 (SIGSEGV), code 2, fault addr 0xb3221f1a in tid 12656 (Compiler driver)
02-14 23:02:35.698 F/libc (12653): Fatal signal 11 (SIGSEGV), code 2, fault addr 0xb322212a in tid 12655 (Compiler driver)
02-14 23:02:35.841 I/DEBUG ( 368): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
02-14 23:02:35.841 I/DEBUG ( 368): Build fingerprint: 'motorola/victara_tmo/victara:5.0/LXE22.46-11/10:user/release-keys'
02-14 23:02:35.842 I/DEBUG ( 368): Revision: 'p2bf'
02-14 23:02:35.842 I/DEBUG ( 368): ABI: 'arm'
02-14 23:02:35.846 I/DEBUG ( 368): pid: 12653, tid: 12657, name: Compiler driver >>> /system/bin/dex2oat <<<
02-14 23:02:35.846 I/DEBUG ( 368): signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0xb3221eae
02-14 23:02:35.893 I/DEBUG ( 368): r0 00000001 r1 0000206e r2 0000000b r3 00000002
02-14 23:02:35.893 E/DEBUG ( 368): AM write failure (32 / Broken pipe)
02-14 23:02:35.893 I/DEBUG ( 368): r4 b3221eac r5 00000002 r6 b2ec0b30 r7 00000007
02-14 23:02:35.893 I/DEBUG ( 368): r8 00000435 r9 b6ea8618 sl b6a4a970 fp b3221ea8
02-14 23:02:35.893 I/DEBUG ( 368): ip b6a1c538 sp b2ec0a58 lr b6985e2f pc b696753a cpsr 600b0030
02-14 23:02:35.893 I/DEBUG ( 368):
02-14 23:02:35.893 I/DEBUG ( 368): backtrace:
02-14 23:02:35.893 I/DEBUG ( 368): #00 pc 0012253a /system/lib/libart-compiler.so (art::optimizer::DexCompiler::Compile()+517)
02-14 23:02:35.893 I/DEBUG ( 368): #01 pc 001230cf /system/lib/libart-compiler.so (ArtCompileDEX+114)
02-14 23:02:35.893 I/DEBUG ( 368): #02 pc 001434cd /system/lib/libart-compiler.so (art::CompilerDriver::CompileMethod(art::DexFile::CodeItem const*, unsigned int, art::InvokeType, unsigned short, unsigned int, _jobject*, art::DexFile const&, art::DexToDexCompilationLevel)+704)
02-14 23:02:35.893 I/DEBUG ( 368): #03 pc 00143d5b /system/lib/libart-compiler.so (art::CompilerDriver::CompileClass(art::ParallelCompilationManager const*, unsigned int)+1458)
02-14 23:02:35.894 I/DEBUG ( 368): #04 pc 0013aac1 /system/lib/libart-compiler.so
02-14 23:02:35.894 I/DEBUG ( 368): #05 pc 0022d6cb /system/lib/libart.so (art::ThreadPoolWorker::Run()+34)
02-14 23:02:35.894 I/DEBUG ( 368): #06 pc 0022df19 /system/lib/libart.so (art::ThreadPoolWorker::Callback(void*)+52)
02-14 23:02:35.894 I/DEBUG ( 368): #07 pc 00015e6b /system/lib/libc.so (__pthread_start(void*)+30)
02-14 23:02:35.894 I/DEBUG ( 368): #08 pc 00013e3f /system/lib/libc.so (__start_thread+6)
02-14 23:02:36.000 I/DEBUG ( 368):
02-14 23:02:36.000 I/DEBUG ( 368): Tombstone written to: /data/tombstones/tombstone_09
02-14 23:02:36.051 E/DEBUG ( 368): unexpected waitpid response: n=12656, status=0000000b
02-14 23:03:07.209 F/libc (12713): Fatal signal 11 (SIGSEGV), code 2, fault addr 0xb327d0c0 in tid 12713 (main)
02-14 23:03:07.209 F/libc (12713): Fatal signal 11 (SIGSEGV), code 2, fault addr 0xb3299eae in tid 12715 (Compiler driver)
02-14 23:03:07.209 F/libc (12713): Fatal signal 11 (SIGSEGV), code 2, fault addr 0xb3299f1a in tid 12716 (Compiler driver)
02-14 23:03:07.209 F/libc (12713): Fatal signal 11 (SIGSEGV), code 2, fault addr 0xb329a12a in tid 12717 (Compiler driver)
02-14 23:03:07.340 I/DEBUG (12665): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
02-14 23:03:07.340 E/DEBUG (12665): AM write failure (32 / Broken pipe)
02-14 23:03:07.340 I/DEBUG (12665): Build fingerprint: 'motorola/victara_tmo/victara:5.0/LXE22.46-11/10:user/release-keys'
02-14 23:03:07.340 I/DEBUG (12665): Revision: 'p2bf'
02-14 23:03:07.340 I/DEBUG (12665): ABI: 'arm'
02-14 23:03:07.340 I/DEBUG (12665): pid: 12713, tid: 12713, name: main >>> /system/bin/dex2oat <<<
02-14 23:03:07.340 I/DEBUG (12665): signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0xb327d0c0
02-14 23:03:07.356 I/DEBUG (12665): r0 00000001 r1 0000106e r2 00000028 r3 00000002
02-14 23:03:07.356 I/DEBUG (12665): r4 b327d0be r5 00000003 r6 beb60e08 r7 0000013c
02-14 23:03:07.356 I/DEBUG (12665): r8 00008367 r9 b6f20618 sl b6ac2970 fp b327d0b8
02-14 23:03:07.356 I/DEBUG (12665): ip b6a94538 sp beb60d30 lr b69fde2f pc b69df53a cpsr 600e0030
02-14 23:03:07.356 I/DEBUG (12665):
02-14 23:03:07.356 I/DEBUG (12665): backtrace:
02-14 23:03:07.356 I/DEBUG (12665): #00 pc 0012253a /system/lib/libart-compiler.so (art::optimizer::DexCompiler::Compile()+517)
02-14 23:03:07.356 I/DEBUG (12665): #01 pc 001230cf /system/lib/libart-compiler.so (ArtCompileDEX+114)
02-14 23:03:07.357 I/DEBUG (12665): #02 pc 001434cd /system/lib/libart-compiler.so (art::CompilerDriver::CompileMethod(art::DexFile::CodeItem const*, unsigned int, art::InvokeType, unsigned short, unsigned int, _jobject*, art::DexFile const&, art::DexToDexCompilationLevel)+704)
02-14 23:03:07.357 I/DEBUG (12665): #03 pc 00143d5b /system/lib/libart-compiler.so (art::CompilerDriver::CompileClass(art::ParallelCompilationManager const*, unsigned int)+1458)
02-14 23:03:07.357 I/DEBUG (12665): #04 pc 0013aac1 /system/lib/libart-compiler.so
02-14 23:03:07.357 I/DEBUG (12665): #05 pc 0022d9b1 /system/lib/libart.so (art::ThreadPool::Wait(art::Thread*, bool, bool)+172)
02-14 23:03:07.357 I/DEBUG (12665): #06 pc 0013da47 /system/lib/libart-compiler.so
02-14 23:03:07.357 I/DEBUG (12665): #07 pc 0013e2bb /system/lib/libart-compiler.so (art::CompilerDriver::Compile(_jobject*, std::__1::vector<art::DexFile const*, std::__1::allocator<art::DexFile const*> > const&, art::ThreadPool*, art::TimingLogger*)+146)
02-14 23:03:07.357 I/DEBUG (12665): #08 pc 00146a75 /system/lib/libart-compiler.so (art::CompilerDriver::CompileAll(_jobject*, std::__1::vector<art::DexFile const*, std::__1::allocator<art::DexFile const*> > const&, art::TimingLogger*)+64)
02-14 23:03:07.357 I/DEBUG (12665): #09 pc 0000c7c9 /system/bin/dex2oat
02-14 23:03:07.357 I/DEBUG (12665): #10 pc 0000ea3f /system/bin/dex2oat
02-14 23:03:07.357 I/DEBUG (12665): #11 pc 00012115 /system/lib/libc.so (__libc_init+44)
02-14 23:03:07.357 I/DEBUG (12665): #12 pc 00006844 /system/bin/dex2oat
02-14 23:03:07.497 I/DEBUG (12665):
02-14 23:03:07.497 I/DEBUG (12665): Tombstone written to: /data/tombstones/tombstone_00
02-14 23:03:07.548 E/DEBUG (12665): unexpected waitpid response: n=12716, status=0000000b
Thanks Sir.
Maybe next days i flash a custom rom with 5.0.2 and see what's in the log.
.
I'm seeing the same errors in my logs as well, but I'm also facing problems from the gravitybox module not really working... Can it be related? The module devs can't really offer any help as long as my framework is raising exceptions
bump
Tried Nitrogen and Beltz, and experienced on both.
In one of the cars, when talking via Bluetooth connection, every couple of minutes bluetooth on the phone dies, restarts and reconnects, and this keeps repeating (the call itself stays connected). Phone works fine with other cars and various bluetooth devices I've tried.
20:03:10.192 F/android.hardware.bluetooth-hci-h4(7210): OnDataReady: Unimplemented packet type 16
20:03:10.194 F/libc (7210): Fatal signal 6 (SIGABRT), code -6 in tid 7251 (hci_thread), pid 7210 (droid.bluetooth)
20:03:10.581 I/crash_dump32(15485): obtaining output fd from tombstoned, type: kDebuggerdTombstone
20:03:10.582 I//system/bin/tombstoned(396): received crash request for pid 7210
20:03:10.589 I/crash_dump32(15485): performing dump of process 7210 (target tid = 7251)
20:03:10.590 F/DEBUG (15485): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
20:03:10.590 F/DEBUG (15485): Build fingerprint: 'google/shamu/shamu:7.1.1/N6F27M/4299435:user/release-keys'
20:03:10.590 F/DEBUG (15485): Revision: '0'
20:03:10.590 F/DEBUG (15485): ABI: 'arm'
20:03:10.590 F/DEBUG (15485): pid: 7210, tid: 7251, name: hci_thread >>> com.android.bluetooth <<<
20:03:10.590 F/DEBUG (15485): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
20:03:10.617 F/DEBUG (15485): Abort message: 'OnDataReady: Unimplemented packet type 16'
20:03:10.617 F/DEBUG (15485): r0 00000000 r1 00001c53 r2 00000006 r3 00000008
20:03:10.617 F/DEBUG (15485): r4 00001c2a r5 00001c53 r6 97fa93fc r7 0000010c
20:03:10.617 F/DEBUG (15485): r8 00000000 r9 00000045 sl aa93429c fp aa9342d0
020:03:10.617 F/DEBUG (15485): ip aa9342a4 sp 97fa93e8 lr b38fab2b pc b38f4538 cpsr 20010030
20:03:10.634 F/DEBUG (15485):
20:03:10.634 F/DEBUG (15485): backtrace:
20:03:10.634 F/DEBUG (15485): #00 pc 0001a538 /system/lib/libc.so (abort+63)
20:03:10.634 F/DEBUG (15485): #01 pc 00006605 /system/lib/liblog.so (__android_log_assert+156)
20:03:10.635 F/DEBUG (15485): #02 pc 000079e5 /system/vendor/lib/hw/[email protected] (android::hardware::bluetooth::hci::H4Protocol::ee k:nDataReady(int)+196)
20:03:10.635 F/DEBUG (15485): #03 pc 00007475 /system/vendor/lib/hw/[email protected] (android::hardware::bluetooth::async::AsyncFdWatch er::ThreadRoutine()+404)
20:03:10.635 F/DEBUG (15485): #04 pc 0000778b /system/vendor/lib/hw/[email protected] (_ZNSt3__114__thread_proxyINS_5tupleIJNS_10unique_ ptrINS_15__thread_structENS_14default_deleteIS3_EE EEZN7android8hardware9bluetooth5async14AsyncFdWatc her14tryStartThreadEvE3$_0EEEEEPvSE_+22)
20:03:10.635 F/DEBUG (15485): #05 pc 00047e3f /system/lib/libc.so (__pthread_start(void*)+22)
20:03:10.635 F/DEBUG (15485): #06 pc 0001b125 /system/lib/libc.so (__start_thread+32)
Sometimes different packet type (i.e. 104).
Any help appreciated...
xduser1 said:
Tried Nitrogen and Beltz, and experienced on both.
In one of the cars, when talking via Bluetooth connection, every couple of minutes bluetooth on the phone dies, restarts and reconnects, and this keeps repeating (the call itself stays connected). Phone works fine with other cars and various bluetooth devices I've tried.
20:03:10.192 F/android.hardware.bluetooth-hci-h4(7210): OnDataReady: Unimplemented packet type 16
20:03:10.194 F/libc (7210): Fatal signal 6 (SIGABRT), code -6 in tid 7251 (hci_thread), pid 7210 (droid.bluetooth)
20:03:10.581 I/crash_dump32(15485): obtaining output fd from tombstoned, type: kDebuggerdTombstone
20:03:10.582 I//system/bin/tombstoned(396): received crash request for pid 7210
20:03:10.589 I/crash_dump32(15485): performing dump of process 7210 (target tid = 7251)
20:03:10.590 F/DEBUG (15485): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
20:03:10.590 F/DEBUG (15485): Build fingerprint: 'google/shamu/shamu:7.1.1/N6F27M/4299435:user/release-keys'
20:03:10.590 F/DEBUG (15485): Revision: '0'
20:03:10.590 F/DEBUG (15485): ABI: 'arm'
20:03:10.590 F/DEBUG (15485): pid: 7210, tid: 7251, name: hci_thread >>> com.android.bluetooth <<<
20:03:10.590 F/DEBUG (15485): signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
20:03:10.617 F/DEBUG (15485): Abort message: 'OnDataReady: Unimplemented packet type 16'
20:03:10.617 F/DEBUG (15485): r0 00000000 r1 00001c53 r2 00000006 r3 00000008
20:03:10.617 F/DEBUG (15485): r4 00001c2a r5 00001c53 r6 97fa93fc r7 0000010c
20:03:10.617 F/DEBUG (15485): r8 00000000 r9 00000045 sl aa93429c fp aa9342d0
020:03:10.617 F/DEBUG (15485): ip aa9342a4 sp 97fa93e8 lr b38fab2b pc b38f4538 cpsr 20010030
20:03:10.634 F/DEBUG (15485):
20:03:10.634 F/DEBUG (15485): backtrace:
20:03:10.634 F/DEBUG (15485): #00 pc 0001a538 /system/lib/libc.so (abort+63)
20:03:10.634 F/DEBUG (15485): #01 pc 00006605 /system/lib/liblog.so (__android_log_assert+156)
20:03:10.635 F/DEBUG (15485): #02 pc 000079e5 /system/vendor/lib/hw/[email protected] (android::hardware::bluetooth::hci::H4Protocol::ee k:nDataReady(int)+196)
20:03:10.635 F/DEBUG (15485): #03 pc 00007475 /system/vendor/lib/hw/[email protected] (android::hardware::bluetooth::async::AsyncFdWatch er::ThreadRoutine()+404)
20:03:10.635 F/DEBUG (15485): #04 pc 0000778b /system/vendor/lib/hw/[email protected] (_ZNSt3__114__thread_proxyINS_5tupleIJNS_10unique_ ptrINS_15__thread_structENS_14default_deleteIS3_EE EEZN7android8hardware9bluetooth5async14AsyncFdWatc her14tryStartThreadEvE3$_0EEEEEPvSE_+22)
20:03:10.635 F/DEBUG (15485): #05 pc 00047e3f /system/lib/libc.so (__pthread_start(void*)+22)
20:03:10.635 F/DEBUG (15485): #06 pc 0001b125 /system/lib/libc.so (__start_thread+32)
Sometimes different packet type (i.e. 104).
Any help appreciated...
Click to expand...
Click to collapse
Have you tried deleting the pairing and recreating it? The only times I've ever had that problem, setting Bluetooth up from scratch has resolved it.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
ktmom said:
Have you tried deleting the pairing and recreating it? The only times I've ever had that problem, setting Bluetooth up from scratch has resolved it.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Click to expand...
Click to collapse
Yes, re-paired completely from scratch, several times, and on both ROMs. Still get this.
xduser1 said:
Yes, re-paired completely from scratch, several times, and on both ROMs. Still get this.
Click to expand...
Click to collapse
I have the same issue with every 8.1 build I have tried. I think LOS is less problematic and I have fewer disconnects reconnects. Glad I'm not the only one with the issue. I was going to flash back to stock to see if the issue persists, but I'm pretty sure Bluetooth is incomplete for the N6 and 8.1. Every ROM i have tried also misreports Bluetooth battery drain.
I can say, I use a Bluetooth headset and external gps and connect to my ODBII port all simultaneously without any disconnects. I'm using ABC for shamu and it's been rock solid. I also do not get misreported numbers.
If that's one of the rooms you've tried, and you've clean flashed, then think about trying inn safe mode. Maybe some app is interfering. Safe mode will reset your settings and desktop. You probably want to take a nandroid first.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
Several data points:
On 8.1, I only experience this issue with this one car, all other bluetooth devices and cars that I've tried worked perfect.
I do not experience this issue with this car on 7.1.2..
All ROMs were clean flashed.
Also tried friend's Pixel 2 with stock 8.1, and it worked with this car without any issues.