Hello, first post in xda.
I have an app on the Play Store, it has an IntentService that does some work when the app starts, and it seems to be causing crashes on Android 5.0. This service just scans the assets folder for app updating purposes.
Specifically, this crash seems to happen on Samsung S5 after the ugrade to Lollipop, but I don't know if it's strictly related to that device, as it's an Italian app and here that's still the only widely diffuse device that's getting Lollipop. However, I tried it on the emulator, with stock Android 5, and it's working fine, so I don't know. I'm not linking to the app, but let me know if that's ok, in case anyone wants to see what's happening.
I'm attaching the stack trace, any help on how to proceed would be appreciated... with native problems, I don't know where to put my hands.
Code:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'samsung/kltexx/klte:5.0/LRX21T/G900FXXU1BNL9:user/release-keys'
Revision: '14'
ABI: 'arm'
pid: 24219, tid: 24259, name: IntentService[I >>> it.mydomain.myapp <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
r0 afcb8c00 r1 001000e6 r2 af201428 r3 00000000
r4 76eb1338 r5 700981c0 r6 af50e4c2 r7 afcb8c00
r8 af201070 r9 b4f7e300 sl b4efac64 fp fffffb18
ip 00100002 sp af200f60 lr b4cd52ab pc b4cd52ca cpsr 600f0030
backtrace:
#00 pc 000d32ca /system/lib/libart.so (art::ClassLinker::FindClassInPathClassLoader(art::ScopedObjectAccessAlreadyRunnable&, art::Thread*, char const*, art::Handle<art::mirror::ClassLoader>)+77)
#01 pc 000d3739 /system/lib/libart.so (_ZN3art11ClassLinker9FindClassEPNS_6ThreadEPKcNS_6HandleINS_6mirror11ClassLoaderEEE.part.404+356)
#02 pc 000d5ded /system/lib/libart.so (art::ClassLinker::CreateArrayClass(art::Thread*, char const*, art::Handle<art::mirror::ClassLoader>)+88)
#03 pc 000d37d1 /system/lib/libart.so (_ZN3art11ClassLinker9FindClassEPNS_6ThreadEPKcNS_6HandleINS_6mirror11ClassLoaderEEE.part.404+508)
#04 pc 000d5ded /system/lib/libart.so (art::ClassLinker::CreateArrayClass(art::Thread*, char const*, art::Handle<art::mirror::ClassLoader>)+88)
#05 pc 000d37d1 /system/lib/libart.so (_ZN3art11ClassLinker9FindClassEPNS_6ThreadEPKcNS_6HandleINS_6mirror11ClassLoaderEEE.part.404+508)
#06 pc 001fe583 /system/lib/libart.so (art::Array_createObjectArray(_JNIEnv*, _jclass*, _jclass*, int)+422)
#07 pc 00093489 /system/framework/arm/boot.oat
I am also facing the same issue on Samsung S5 device
Hi,
I too struggling for the same issue If you know the workaround please share with me .
I am pasting the adb log please have a look.
02-13 16:06:38.943 D/CrashAnrDetector( 903): pid: 6235, tid: 7331, name: Timer-0 >>> com.verizon.pushtotalkplus <<<
02-13 16:06:38.943 D/CrashAnrDetector( 903): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x23007e4
02-13 16:06:38.943 D/CrashAnrDetector( 903): r0 00400000 r1 023007d8 r2 00080401 r3 00000000
02-13 16:06:38.943 D/CrashAnrDetector( 903): r4 0000025a r5 700cf940 r6 7712c388 r7 1324dfc0
02-13 16:06:38.943 D/CrashAnrDetector( 903): r8 1325a820 r9 a2894800 sl 131c8a00 fp 1325a820
02-13 16:06:38.943 D/CrashAnrDetector( 903): ip 00000000 sp 95dff9f8 lr 7511a065 pc b4d81ff0 cpsr 20000030
02-13 16:06:38.943 D/CrashAnrDetector( 903): d0 0000000000ffffff d1 0000000000000000
02-13 16:06:38.943 D/CrashAnrDetector( 903): d2 c0c0c0c0c0c0c0c0 d3 0000000000000000
02-13 16:06:38.943 D/CrashAnrDetector( 903): d4 c0808080c0000000 d5 0001000100010001
02-13 16:06:38.943 D/CrashAnrDetector( 903): d6 ffffffffff000000 d7 0000000000000000
02-13 16:06:38.943 D/CrashAnrDetector( 903): d8 0000000000000000 d9 0000000000000000
02-13 16:06:38.943 D/CrashAnrDetector( 903): d10 0000000000000000 d11 0000000000000000
02-13 16:06:38.943 D/CrashAnrDetector( 903): d12 0000000000000000 d13 0000000000000000
02-13 16:06:38.943 D/CrashAnrDetector( 903): d14 0000000000000000 d15 0000000000000000
02-13 16:06:38.943 D/CrashAnrDetector( 903): d16 0000000000000000 d17 0000000000000000
02-13 16:06:38.943 D/CrashAnrDetector( 903): d18 0706050403020100 d19 0000000200000002
02-13 16:06:38.943 D/CrashAnrDetector( 903): d20 0101010101010101 d21 0101010101010101
02-13 16:06:38.943 D/CrashAnrDetector( 903): d22 8080808080808080 d23 8080808080808080
02-13 16:06:38.943 D/CrashAnrDetector( 903): d24 0000000000808080 d25 0000000000000000
02-13 16:06:38.943 D/CrashAnrDetector( 903): d26 0303030303030303 d27 0303030303030303
02-13 16:06:38.943 D/CrashAnrDetector( 903): d28 0100000001010101 d29 0100000001000000
02-13 16:06:38.943 D/CrashAnrDetector( 903): d30 00ffffff00000000 d31 00ffffff00ffffff
02-13 16:06:38.943 D/CrashAnrDetector( 903): scr 20000013
02-13 16:06:38.943 D/CrashAnrDetector( 903):
02-13 16:06:38.943 D/CrashAnrDetector( 903): backtrace:
02-13 16:06:38.943 D/CrashAnrDetector( 903): #00 pc 0027eff0 /system/lib/libart.so (artIsAssignableFromCode+23)
02-13 16:06:38.943 D/CrashAnrDetector( 903): #01 pc 002d5063 /system/framework/arm/boot.oat
02-13 16:06:38.943 D/CrashAnrDetector( 903):
Its showing as libart.so having some issue please let me know the workaround for this issue .
Advance Thanks to all.
-Bikash
Related
I am trying to debug a crash with trying to load a library that I cross-compiled using System.loadLibrary(). I have been able to successfully load this library on any device running 4.0.4 (ICS), but it crashes on all of my devices running 4.1.1 (JB). It seems to crash when running in to pthread_create() in libc:
Code:
10-01 14:25:34.173: D/dalvikvm(8215): Trying to load lib /data/data/com.gnychis.awmon/lib/libtshark.so 0x410fb430
10-01 14:25:34.181: A/libc(8215): Fatal signal 11 (SIGSEGV) at 0x5dfaa01c (code=2), thread 8232 (AsyncTask #1)
// And here is the end of the stack....
I/DEBUG ( 246): #10 pc 0001263c /system/lib/libc.so (pthread_create+180)
Here is the much longer crash log that is involved showing the entire stack trace, and you will see it ends at libc and pthread_create:
Code:
D/dalvikvm(26364): Trying to load lib /data/data/com.gnychis.awmon/lib/libtshark.so 0x410a5ee0
F/libc (26364): Fatal signal 11 (SIGSEGV) at 0x5dff301c (code=2), thread 27345 (AsyncTask #1)
D/AndroidRuntime(27404): Calling main entry com.android.commands.am.Am
I/DEBUG ( 246): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 246): Build fingerprint: 'd2uc-user 4.0.4 IMM76D I747UCALEM release-keys'
I/DEBUG ( 246): pid: 26364, tid: 27345, name: AsyncTask #1 >>> com.gnychis.awmon <<<
I/DEBUG ( 246): signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 5dff301c
D/AndroidRuntime(27404): Shutting down VM
D/dalvikvm(27404): GC_CONCURRENT freed 99K, 88% free 498K/4096K, paused 1ms+1ms, total 7ms
I/AndroidRuntime(27404): NOTE: attach of thread 'Binder_3' failed
I/DEBUG ( 246): r0 80000000 r1 02b1a000 r2 00000005 r3 5dff3000
I/DEBUG ( 246): r4 40102894 r5 4010aaec r6 00000000 r7 00000029
I/DEBUG ( 246): r8 00000029 r9 5dff3000 sl 60871000 fp 02b1a000
I/DEBUG ( 246): ip 00000005 sp 5d95ace0 lr 6004d1bb pc 400ec6e0 cpsr 600d0030
I/DEBUG ( 246): d0 61642f617461642f d1 672e6d6f632f6174
I/DEBUG ( 246): d2 612e73696863796e d3 62696c2f6e6f6d77
I/DEBUG ( 246): d4 00000000000e16f0 d5 000000000000695f
I/DEBUG ( 246): d6 000000000002a715 d7 0000012f00000000
I/DEBUG ( 246): d8 0000000000000000 d9 0000000000000000
I/DEBUG ( 246): d10 0000000000000000 d11 0000000000000000
I/DEBUG ( 246): d12 0000000000000000 d13 0000000000000000
I/DEBUG ( 246): d14 0000000000000000 d15 0000000000000000
I/DEBUG ( 246): d16 7420676e69797254 d17 6c2064616f6c206f
I/DEBUG ( 246): d18 0063002f00610074 d19 0067002e006d006f
I/DEBUG ( 246): d20 006800630079006e d21 0061002e00730069
I/DEBUG ( 246): d22 006e006f006d0077 d23 00620069006c002f
I/DEBUG ( 246): d24 000000000000e16f d25 0000000000000000
I/DEBUG ( 246): d26 000000000000695f d27 0000000000000000
I/DEBUG ( 246): d28 000000000000695f d29 0000000000000000
I/DEBUG ( 246): d30 0000000500000005 d31 0000000500000005
I/DEBUG ( 246): scr 60000012
I/DEBUG ( 246):
I/DEBUG ( 246): backtrace:
I/DEBUG ( 246): #00 pc 000046e0 /system/bin/linker
I/DEBUG ( 246): #01 pc 00005b6f /system/bin/linker
I/DEBUG ( 246): #02 pc 0004f73b /system/lib/libdvm.so (dvmLoadNativeCode(char const*, Object*, char**)+186)
I/DEBUG ( 246): #03 pc 000662bd /system/lib/libdvm.so
I/DEBUG ( 246): #04 pc 000274e0 /system/lib/libdvm.so
I/DEBUG ( 246): #05 pc 0002be08 /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+180)
I/DEBUG ( 246): #06 pc 0005f9f5 /system/lib/libdvm.so (dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)+272)
I/DEBUG ( 246): #07 pc 0005fa1f /system/lib/libdvm.so (dvmCallMethod(Thread*, Method const*, Object*, JValue*, ...)+20)
I/DEBUG ( 246): #08 pc 000545ab /system/lib/libdvm.so
I/DEBUG ( 246): #09 pc 00012ee4 /system/lib/libc.so (__thread_entry+48)
I/DEBUG ( 246): #10 pc 0001263c /system/lib/libc.so (pthread_create+180)
The interesting thing is that if I use arm-eabi-objdump on the library, the address 1263c seems to be when it tries to do a pthread_clone:
Code:
$ arm-eabi-objdump -S /tmp/libc.so | grep 1263c
1263c: ebffed71 bl dc08 <__pthread_clone>
Does anyone have any insight as to why this would not be working on 4.1.1? Also, why does my "Build fingerprint" at the top of my crash log show:
Code:
Build fingerprint: 'd2uc-user 4.0.4'
Could this be the root issue of why it's not running on 4.1.1? I am using the newest NDK (r8b), with android-14 as the platform with the arm-eabi-4.4.3 toolchain.
Thanks so much for any help/guidance.
Sent from my KFTHWI using xda premium
EDIT: BTW I'm new here
Cydia substrate is only for jailbroken Apple ios devices. The Kindle fire is not made by apple. It runs on android.
Sent from my SCH-I545 using Tapatalk
joshuabg said:
Cydia substrate is only for jailbroken Apple ios devices. The Kindle fire is not made by apple. It runs on android.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Cydia Substrate is in the play store. I believe Saurik ported it to run on android a few years ago.
https://play.google.com/store/apps/details?id=com.saurik.substrate&hl=en
O and yes it should work fine since we're rooted and have play store working.
-UPDATE-
It does not work. "Note: your device is not fully compatible with this version of Substrate. Please contact saurik via e-mail and include the following symbols:
__metrics_log_print"
Yea I tried it too, and after doing a little research I've found that the app itself can't even figure out what's wrong. It's supposed to be printing the app's full startup log. Apparently it's giving up before it can even start running the first setup scripts. I'll try debugging it when I get done with my school work. But for now we don't have anything we can report to Saurik.
Sent from my KFTHWI using xda premium
Yeah, even tried to manually link it up, logcat is throwing an error around the native jni loader library that substrate uses. He should really open up the source to this...
D/dalvikvm( 5047): Added shared lib libnativehelper.so 0x0
F/libc ( 5047): Fatal signal 11 (SIGSEGV) at 0x00000000 (code=1), thread 5047 (app_process)
I/DEBUG ( 416): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 416): Build fingerprint: 'Amazon/thor/thor:4.2.2/JDQ39/13.3.1.0_user_310079820:user/release-keys'
I/DEBUG ( 416): Revision: '0'
I/DEBUG ( 416): pid: 5047, tid: 5047, name: app_process >>> app_process <<<
I/DEBUG ( 416): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
I/DEBUG ( 416): r0 5943ded0 r1 00000000 r2 5a864000 r3 00000000
I/DEBUG ( 416): r4 41940ce0 r5 5943ded0 r6 41940ce0 r7 4000e771
I/DEBUG ( 416): r8 4000e741 r9 00000000 sl 00000000 fp 00000000
I/DEBUG ( 416): ip 00000000 sp bec2d260 lr 40b64424 pc 00000000 cpsr 60000010
I/DEBUG ( 416): d0 7465670300646564 d1 6c436b6f6f680d00
I/DEBUG ( 416): d2 0064616f4c737361 d3 74654d6b6f6f680a
I/DEBUG ( 416): d4 766e690600646f68 d5 766e690700656b6f
I/DEBUG ( 416): d6 6f6c060064656b6f d7 6f6c070072656461
I/DEBUG ( 416): d8 0000000000000000 d9 0000000000000000
I/DEBUG ( 416): d10 0000000000000000 d11 0000000000000000
I/DEBUG ( 416): d12 0000000000000000 d13 0000000000000000
I/DEBUG ( 416): d14 0000000000000000 d15 0000000000000000
I/DEBUG ( 416): d16 00000b7a00000005 d17 0000000100001000
I/DEBUG ( 416): d18 000005e00000000a d19 0000004600002002
I/DEBUG ( 416): d20 0000200300000636 d21 00000a7200000006
I/DEBUG ( 416): d22 0000000b00002004 d23 0000200000000af7
I/DEBUG ( 416): d24 0000000000000000 d25 0000000000000000
I/DEBUG ( 416): d26 0000000000000000 d27 0000000000000000
I/DEBUG ( 416): d28 0000000000000000 d29 0000000000000000
I/DEBUG ( 416): d30 0000000000000000 d31 0000000000000000
I/DEBUG ( 416): scr 80000010
I/DEBUG ( 416):
I/DEBUG ( 416): backtrace:
I/DEBUG ( 416): #00 pc 00000000 <unknown>
I/DEBUG ( 416): #01 pc 00002420 /data/app-lib/com.saurik.substrate-2/libDalvikLoader.cy.so
I/DEBUG ( 416): #02 pc 00002fbc /data/app-lib/com.saurik.substrate-2/libDalvikLoader.cy.so
I/DEBUG ( 416): #03 pc 000014c1 /system/lib/libandroid_runtime.so
Hello all,
We have ported Android 4.4 (kitkat) version on a custom board with iMX6 processor and are successful in getting Android running on the custom board. Now, when tried to add support for 3G modem provided by ZTE, the rild daemon is crashing continuously there disabling the complete telephony.
Android service for rild in init.rc file is as below
service ril-daemon /system/bin/rild -l /system/lib/libreference-ril.so -- -d /dev/ttyUSB2
class main
socket rild stream 660 root radio
socket rild-debug stream 660 radio system
user root
group radio cache inet misc audio
The sockets are getting created with the specified permissions as specified in the init.rc but unfortunately rild daemon is crashing throwing segmentation fault (SIGSEGV). The core dump of the crash
F/libc ( 2810): Fatal signal 11 (SIGSEGV) at 0x0000000c (code=1), thread 2821 (rild)
I/DEBUG ( 2387): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG ( 2387): Build fingerprint: 'HKI/indus_1012/i1012:4.4.2/1.0.0-rc3/20140630:user/dev-keys'
I/DEBUG ( 2387): Revision: '405525'
I/DEBUG ( 2387): pid: 2810, tid: 2821, name: rild >>> /system/bin/rild <<<
I/DEBUG ( 2387): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0000000c
I/DEBUG ( 2387): r0 0000000c r1 00000000 r2 00000011 r3 00000000
I/DEBUG ( 2387): r4 0000000c r5 00000000 r6 00000000 r7 4021909c
I/DEBUG ( 2387): r8 40219157 r9 4021d02c sl 402190fc fp 4021d028
I/DEBUG ( 2387): ip 4021cf00 sp 405f7cd8 lr 4015315d pc 4014f708 cpsr 200d0010
I/DEBUG ( 2387): d0 0000000000000000 d1 0000000000000000
I/DEBUG ( 2387): d2 0000000000000000 d3 0000000000000000
I/DEBUG ( 2387): d4 0000000000000000 d5 0000000000000000
I/DEBUG ( 2387): d6 0000000000000000 d7 0243d58000000000
I/DEBUG ( 2387): d8 0000000000000000 d9 0000000000000000
I/DEBUG ( 2387): d10 0000000000000000 d11 0000000000000000
I/DEBUG ( 2387): d12 0000000000000000 d13 0000000000000000
I/DEBUG ( 2387): d14 0000000000000000 d15 0000000000000000
I/DEBUG ( 2387): d16 41826b235ab851ec d17 3f50624dd2f1a9fc
I/DEBUG ( 2387): d18 41c2ab23a6000000 d19 0000000000000000
I/DEBUG ( 2387): d20 0000000000000000 d21 0000000000000000
I/DEBUG ( 2387): d22 0000000000000000 d23 0000000000000000
I/DEBUG ( 2387): d24 0000000000000000 d25 0000000000000000
I/DEBUG ( 2387): d26 0000000000000000 d27 0000000000000000
I/DEBUG ( 2387): d28 0000000000000000 d29 0000000000000000
I/DEBUG ( 2387): d30 0000000000000000 d31 0000000000000000
I/DEBUG ( 2387): scr 00000010
I/DEBUG ( 2387):
I/DEBUG ( 2387): backtrace:
I/DEBUG ( 2387): #00 pc 0000e708 /system/lib/libc.so
I/DEBUG ( 2387): #01 pc 00012159 /system/lib/libc.so (readdir+10)
I/DEBUG ( 2387): #02 pc 000026fd /system/lib/libreference-ril-mw3820.so
I/DEBUG ( 2387): #03 pc 00004069 /system/lib/libreference-ril-mw3820.so
I/DEBUG ( 2387): #04 pc 0000d248 /system/lib/libc.so (__thread_entry+72)
I/DEBUG ( 2387): #05 pc 0000d3e0 /system/lib/libc.so (pthread_create+240)
I/DEBUG ( 2387):
I/DEBUG ( 2387): stack:
I/DEBUG ( 2387): 405f7c98 00000000
I/DEBUG ( 2387): 405f7c9c 00000000
I/DEBUG ( 2387): 405f7ca0 00000000
I/DEBUG ( 2387): 405f7ca4 00000000
I/DEBUG ( 2387): 405f7ca8 00000000
libc.so is not getting loaded but libc.so and libreference-ril-mw3820.so are all available in the system/lib folder. and the contents of system.prop is
rild.libpath=/system/lib/libreference-ril-mw3820.so
rild.libargs=-d /dev/ttyUSB2
but still the above crash persists. Any help on this would be of great help.
I Don't knơ lolll
---------- Post added at 09:35 AM ---------- Previous post was at 09:34 AM ----------
xdavn.com said:
I Don't knơ lolll
Click to expand...
Click to collapse
xdavn.com have
Hello guys! After a lot of problems I succeded in porting this wonderful rom to Moto E 2014 but there are some problems...I solved the most invalidating problems that didn't allow you to use the rom...but the theme app still don't work because I don't understand the log file...so I ask you some help...I would that someone that can help me doesn't hesitate to write his answer here. Thanks in advance
Here there are the details of the error:
Code:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build fingerprint: 'motorola/condor_retaildsds/condor_umtsds:4.4.4/KXC21.5-40/46:user/release-keys'
Revision: '33456'
pid: 10479, tid: 10479, name: zygote >>> zygote <<<
signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
r0 00000000 r1 000028ef r2 00000006 r3 00000000
r4 400a0f2c r5 00000006 r6 00000000 r7 0000010c
r8 00000000 r9 415ecc7c sl 00000000 fp 00000000
ip 000028ef sp bedc82b8 lr 400cb0ff pc 400da024 cpsr 00070010
d0 0000000000000000 d1 0000000000000000
d2 0000000000000000 d3 0000000000000000
d4 0000000000000000 d5 0000000000000000
d6 4a802a3000601518 d7 4040000000000003
d8 0000000000000000 d9 0000000000000000
d10 0000000000000000 d11 0000000000000000
d12 0000000000000000 d13 0000000000000000
d14 0000000000000000 d15 0000000000000000
d16 7320746f6e6e6163 d17 6e694c4553207465
d18 726f6674616c703d d19 6e69616d6f64206d
d20 726f6674616c703d d21 7974207070615f6d
d22 645f7070613d6570 d23 656c69665f617461
d24 0000000000000000 d25 4008000000000000
d26 3fc2f112df3e5244 d27 0000000000000001
d28 00000000000000e6 d29 00000000000000e5
d30 0000000000000001 d31 0000000000004000
scr 80000010
backtrace:
#00 pc 00022024 /system/lib/libc.so (tgkill+12)
#01 pc 000130fb /system/lib/libc.so (pthread_kill+50)
#02 pc 000132f3 /system/lib/libc.so (raise+10)
#03 pc 00011fe3 /system/lib/libc.so
#04 pc 000218d8 /system/lib/libc.so (abort+4)
#05 pc 00047217 /system/lib/libdvm.so (dvmAbort+78)
#06 pc 00068245 /system/lib/libdvm.so
#07 pc 000685fd /system/lib/libdvm.so
#08 pc 00027ea0 /system/lib/libdvm.so
#09 pc 0002f3e4 /system/lib/libdvm.so (dvmMterpStd(Thread*)+76)
#10 pc 0002ca48 /system/lib/libdvm.so (dvmInterpret(Thread*, Method const*, JValue*)+184)
#11 pc 00061afd /system/lib/libdvm.so (dvmCallMethodV(Thread*, Method const*, Object*, bool, JValue*, std::__va_list)+336)
#12 pc 0004b2af /system/lib/libdvm.so
#13 pc 0005187b /system/lib/libandroid_runtime.so
#14 pc 0005259f /system/lib/libandroid_runtime.so (android::AndroidRuntime::start(char const*, char const*)+354)
#15 pc 0000105b /system/bin/app_process
#16 pc 0000e41b /system/lib/libc.so (__libc_init+50)
#17 pc 00000d7c /system/bin/app_process
code around pc:
400da004 e8bd00f0 e3700a01 912fff1e e2600000
400da014 ea006deb e92d50f0 e3a07f43 ef000000
400da024 e8bd50f0 e3700a01 912fff1e e2600000
400da034 ea006de3 e92d50f0 e3a070ee ef000000
400da044 e8bd50f0 e3700a01 912fff1e e2600000
400da054 ea006ddb f200429a bf0080b9 f040f891
400da064 4001e92d f2c02a04 2a1080a5 8093f2c0
400da074 f2c02a20 2a408088 ea4fdb7f f1bc1c92
400da084 dd6c0f0a 0600e92d 0f40f1bc f500dd4a
400da094 f5016e80 ebae7920 ea4f0e09 ea4f5e4e
400da0a4 f50e5e5e ebbc7e20 dd3b1f9e f04fbfc4
400da0b4 ebd9090a dd35199e 0a0eeb01 0a3ff02a
400da0c4 1c9eebac bfd245e1 0c09ebac f04f46e1
400da0d4 f8910c00 f891f240 f921f280 f921028d
400da0e4 f8da428d f1b93000 f9000901 f900028d
400da0f4 f10a428d d1ee0a40 0f00f1bc f5bcd02b
code around lr:
400cb0dc 4b11ebe8 e010447b d10e42bb 6a1f480f
400cb0ec f7fb4478 f00dec60 4639e9cc f00e462a
400cb0fc 3001ef8e 2500d00a 681be009 d1eb2b00
400cb10c 25034807 f7fb4478 e000ec4e 60266825
400cb11c bdf84628 0003b2c4 0003b2b8 0003b2b0
400cb12c 0003b28c bf82f7ff 4a3a4b39 47f0e92d
400cb13c 4607b08a 447b460d 6833589e 930946b1
400cb14c f9f4f001 f8d04604 2d008000 4628d04a
400cb15c f910f010 4606280f f7ffd846 4287ffe3
400cb16c 200fd106 f00d4629 2800e89a e032d03d
400cb17c 44784829 eb94f7fb 44784828 42b8e015
400cb18c 6a07d113 44784826 ec0cf7fb 463b4a25
400cb19c a8012120 f013447a 2101f991 f01aa801
400cb1ac 1c43fc8b d1044607 6800e015 d1e62800
400cb1bc 4638e023 46324629 e8d4f00d 3ffff1b0
400cb1cc d1024682 29046821 4638d0f3 e924f00d
Hi,
I'm new to the board and hopefully this is the right spot to ask a question.
I was able to port Lineage cm-14.1 to an unsupported tablet (Samsung Galaxy Tab E SM-T560 with Spreadtrum CPU). Boot and Apps are working so far. Except graphics, everything is build from source. Of course, some things like Sound, Bluetooth, do not work, but thats OK for the moment.
However, after a WIFI connection is initialised successfully, system_server crashes with the following message:
Code:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
LineageOS Version: '14.1-20180312-UNOFFICIAL-gtelwifi'
Build fingerprint: 'samsung/gtelwifixx/gtelwifi:4.4.4/KTU84P/T560XXU0APL1:user/release-keys'
Revision: '0'
ABI: 'arm'
pid: 13389, tid: 14235, name: Thread-11 >>> system_server <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x78
r0 7084da80 r1 00000000 r2 00000002 r3 95daee50
r4 95daee4c r5 00000000 r6 00000001 r7 95daed90
r8 00100015 r9 95daedf4 sl 95daee50 fp 95daee0c
ip 95daed74 sp 95daeca8 lr b4128fd1 pc b4128fd2 cpsr 000f0030
d0 0061007000690063 d1 006e006900720070
d2 002e0031002e0063 d3 0032003100310000
d4 70cfa28738012a85 d5 c5cae7c4c97aa4ad
d6 c218fef23223bcda d7 10d0d42f3bdfe07b
d8 0000000000000000 d9 0000000000000000
d10 0000000000000000 d11 0000000000000000
d12 0000000000000000 d13 0000000000000000
d14 0000000000000000 d15 0000000000000000
d16 0000000000000000 d17 0000000000000000
d18 ba477909c171394d d19 d3ae31fe0363f924
d20 8c6b848e8d263350 d21 da82799950a1ac75
d22 643eae4cf301b269 d23 68899da5e3aa691f
d24 b1401b90d960c774 d25 e0b124ed89024d71
d26 8f6330182fe5dfa9 d27 4d27558dee6bf79c
d28 5a8279995a827999 d29 5a8279995a827999
d30 0000000000000000 d31 0000000000000000
scr 80000093
backtrace:
#00 pc 00316fd2 /system/lib/libart.so (_ZN3art12InvokeMethodERKNS_33ScopedObjectAccessAlreadyRunnableEP8_jobjectS4_S4_j+69)
#01 pc 002b51f9 /system/lib/libart.so (_ZN3artL24Constructor_newInstance0EP7_JNIEnvP8_jobjectP13_jobjectArray+868)
#02 pc 005aaee5 /system/framework/arm/boot-core-oj.oat (offset 0x51b000)
Because the backtrace is really small, it's hard for me to understand what went wrong.
Does somebody know what I can do to solve the system_server crash?
Complete tombstone can be found here:
github.com/olliiiver/local_manifest/blob/cm-14.1/tombstone.txt
Sources for device can be found here:
github.com/olliiiver/android_device_samsung_gtelwifi