search

joelmap / imsdroid

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

Crash on toshiba Folio100 #186

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Download last release (366)
2. Install OK 
3. Start application 

What is the expected output? What do you see instead?

Application crash at the start when the libtinyWRAP.so are loaded .

Traces :
I/wpa_supplicant( 1271): CTRL-EVENT-STATE-CHANGE id=-1 state=2 
BSSID=00:00:00:00:00:00
V/WifiMonitor( 1053): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=2 
BSSID=00:00:00:00:00:00]
V/WifiStateTracker( 1053): Changing supplicant state: INACTIVE ==> SCANNING
D/NetworkStateTracker( 1053): setDetailed state, old =IDLE and new 
state=SCANNING
I/wpa_supplicant( 1271): CTRL-EVENT-SCAN-RESULTS 
I/ActivityManager( 1053): Starting activity: Intent { 
act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] 
flg=0x10200000 cmp=org.doubango.imsdroid/.Main }
I/ActivityManager( 1053): Start proc org.doubango.imsdroid for activity 
org.doubango.imsdroid/.Main: pid=1946 uid=10001 gids={3003, 1015, 1006}
D/dalvikvm( 1946): Trying to load lib 
/data/data/org.doubango.imsdroid/lib/libtinyWRAP.so 0x4a3cd378
D/dalvikvm( 1946): Added shared lib 
/data/data/org.doubango.imsdroid/lib/libtinyWRAP.so 0x4a3cd378
D/dalvikvm( 1946): No JNI_OnLoad found in 
/data/data/org.doubango.imsdroid/lib/libtinyWRAP.so 0x4a3cd378, skipping init
I/DEBUG   ( 1409): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** 
***
I/DEBUG   ( 1409): Build fingerprint: 
'TOSHIBA/TOSHIBA_FOLIO_AND_A/:2.2/TOSHIBA_FOLIO_AND_A/5.0053:user/test-keys'
I/DEBUG   ( 1409): pid: 1946, tid: 1946  >>> org.doubango.imsdroid <<<
I/DEBUG   ( 1409): signal 4 (SIGILL), fault addr 81a63094
I/DEBUG   ( 1409):  r0 0000aa58  r1 4a3df8b0  r2 4410bc48  r3 459bd354
I/DEBUG   ( 1409):  r4 be8c3e68  r5 00000003  r6 4a3df8b0  r7 4410bc14
I/DEBUG   ( 1409):  r8 be8c3e48  r9 4410bc0c  10 4410bbf8  fp 00000000
I/DEBUG   ( 1409):  ip 81a63090  sp be8c3e30  lr 80f16df8  pc 81a63094  cpsr 
a0000010
I/DEBUG   ( 1409):  d0  000000003f400000  d1  3ff000003f400000
I/DEBUG   ( 1409):  d2  0000000050baf6de  d3  0000000000000000
I/DEBUG   ( 1409):  d4  00000009000000b4  d5  3fe999999999999a
I/DEBUG   ( 1409):  d6  3fe8000000000000  d7  3eaaaaab3f800000
I/DEBUG   ( 1409):  d8  0000000000000000  d9  0000000000000000
I/DEBUG   ( 1409):  d10 0000000000000000  d11 0000000000000000
I/DEBUG   ( 1409):  d12 0000000000000000  d13 0000000000000000
I/DEBUG   ( 1409):  d14 0000000000000000  d15 0000000000000000
I/DEBUG   ( 1409):  scr 20000012
I/DEBUG   ( 1409): 
I/DEBUG   ( 1409):          #00  pc 00263094  
/data/data/org.doubango.imsdroid/lib/libtinyWRAP.so
I/DEBUG   ( 1409):          #01  pc 00016df4  /system/lib/libdvm.so
I/DEBUG   ( 1409):          #02  pc 00044974  /system/lib/libdvm.so
I/DEBUG   ( 1409):          #03  pc 0004a0d6  /system/lib/libdvm.so
I/DEBUG   ( 1409):          #04  pc 0001bd58  /system/lib/libdvm.so
I/DEBUG   ( 1409):          #05  pc 00022744  /system/lib/libdvm.so
I/DEBUG   ( 1409):          #06  pc 000215e0  /system/lib/libdvm.so
I/DEBUG   ( 1409):          #07  pc 0005bcb6  /system/lib/libdvm.so
I/DEBUG   ( 1409):          #08  pc 0005bee8  /system/lib/libdvm.so
I/DEBUG   ( 1409):          #09  pc 00067b68  /system/lib/libdvm.so
I/DEBUG   ( 1409):          #10  pc 000694f2  /system/lib/libdvm.so
I/DEBUG   ( 1409):          #11  pc 00018c28  /system/lib/libdvm.so
I/DEBUG   ( 1409):          #12  pc 00022744  /system/lib/libdvm.so
I/DEBUG   ( 1409):          #13  pc 000215e0  /system/lib/libdvm.so
I/DEBUG   ( 1409):          #14  pc 0005bcb6  /system/lib/libdvm.so
I/DEBUG   ( 1409):          #15  pc 0005bee8  /system/lib/libdvm.so
I/DEBUG   ( 1409):          #16  pc 0006313e  /system/lib/libdvm.so
I/DEBUG   ( 1409):          #17  pc 0001bd58  /system/lib/libdvm.so
I/DEBUG   ( 1409):          #18  pc 00022744  /system/lib/libdvm.so
I/DEBUG   ( 1409):          #19  pc 000215e0  /system/lib/libdvm.so
I/DEBUG   ( 1409):          #20  pc 0005be78  /system/lib/libdvm.so
I/DEBUG   ( 1409):          #21  pc 0006441e  /system/lib/libdvm.so
I/DEBUG   ( 1409):          #22  pc 0001bd58  /system/lib/libdvm.so
I/DEBUG   ( 1409):          #23  pc 00022744  /system/lib/libdvm.so
I/DEBUG   ( 1409):          #24  pc 000215e0  /system/lib/libdvm.so
I/DEBUG   ( 1409):          #25  pc 0005bcb6  /system/lib/libdvm.so
I/DEBUG   ( 1409):          #26  pc 00047362  /system/lib/libdvm.so
I/DEBUG   ( 1409):          #27  pc 0002da18  /system/lib/libandroid_runtime.so
I/DEBUG   ( 1409):          #28  pc 0002eb0c  /system/lib/libandroid_runtime.so
I/DEBUG   ( 1409):          #29  pc 00008caa  /system/bin/app_process
I/DEBUG   ( 1409):          #30  pc 0000d3d8  /system/lib/libc.so
I/DEBUG   ( 1409): 
I/DEBUG   ( 1409): code around pc:
I/DEBUG   ( 1409): 81a63074 e2833008 e5842004 e5843000 e8bd8070 
I/DEBUG   ( 1409): 81a63084 00169a8c 00001630 00000000 e92d4037 
I/DEBUG   ( 1409): 81a63094 eddf0b0b e1a05000 edcd0b00 e3a00018 
I/DEBUG   ( 1409): 81a630a4 ebf7be2b e1a01005 e1a04000 ebffffe2 
I/DEBUG   ( 1409): 81a630b4 e1a00004 e59d1004 e28dd00c e8bd8030 
I/DEBUG   ( 1409): 
I/DEBUG   ( 1409): code around lr:
I/DEBUG   ( 1409): 80f16dd8 3497c004 3488c004 3afffff9 e2888004 
I/DEBUG   ( 1409): 80f16de8 eafffff9 e899000c e594c008 e12fff3c 
I/DEBUG   ( 1409): 80f16df8 e3550000 1594c00c 188c0003 e914a3f0 
I/DEBUG   ( 1409): 80f16e08 e1a05e22 e5946004 e3a02000 e4d6c001 
I/DEBUG   ( 1409): 80f16e18 e35c0000 0a000007 e2822001 e35c0044 
I/DEBUG   ( 1409): 
I/DEBUG   ( 1409): stack:
I/DEBUG   ( 1409):     be8c3df0  00257b90  [heap]
I/DEBUG   ( 1409):     be8c3df4  0000a000  [heap]
I/DEBUG   ( 1409):     be8c3df8  80f16fc0  /system/lib/libdvm.so
I/DEBUG   ( 1409):     be8c3dfc  0000cd00  [heap]
I/DEBUG   ( 1409):     be8c3e00  4410bbf8  
I/DEBUG   ( 1409):     be8c3e04  afd0be23  /system/lib/libc.so
I/DEBUG   ( 1409):     be8c3e08  0011e4b8  [heap]
I/DEBUG   ( 1409):     be8c3e0c  0011e478  [heap]
I/DEBUG   ( 1409):     be8c3e10  00001400  
I/DEBUG   ( 1409):     be8c3e14  0000cd00  [heap]
I/DEBUG   ( 1409):     be8c3e18  4410bbf8  
I/DEBUG   ( 1409):     be8c3e1c  0011e4b8  [heap]
I/DEBUG   ( 1409):     be8c3e20  00000000  
I/DEBUG   ( 1409):     be8c3e24  00000000  
I/DEBUG   ( 1409):     be8c3e28  df002777  
I/DEBUG   ( 1409):     be8c3e2c  e3a070ad  
I/DEBUG   ( 1409): #00 be8c3e30  0000aa58  [heap]
I/DEBUG   ( 1409):     be8c3e34  4a3df8b0  /dev/ashmem/mspace/dalvik-heap/2 
(deleted)
I/DEBUG   ( 1409):     be8c3e38  4410bc48  
I/DEBUG   ( 1409):     be8c3e3c  be8c3e68  [stack]
I/DEBUG   ( 1409):     be8c3e40  00000003  
I/DEBUG   ( 1409):     be8c3e44  80f16df8  /system/lib/libdvm.so
I/DEBUG   ( 1409): #01 be8c3e48  0000cd00  [heap]
I/DEBUG   ( 1409):     be8c3e4c  443209b8  /dev/ashmem/dalvik-LinearAlloc 
(deleted)
I/DEBUG   ( 1409):     be8c3e50  4a3df8b0  /dev/ashmem/mspace/dalvik-heap/2 
(deleted)
I/DEBUG   ( 1409):     be8c3e54  4410bc0c  
I/DEBUG   ( 1409):     be8c3e58  80f16fc0  /system/lib/libdvm.so
I/DEBUG   ( 1409):     be8c3e5c  0000cd00  [heap]
I/DEBUG   ( 1409):     be8c3e60  be8c3e68  [stack]
I/DEBUG   ( 1409):     be8c3e64  80f44977  /system/lib/libdvm.so
I/BootReceiver( 1053): Copying /data/tombstones/tombstone_01 to DropBox 
(SYSTEM_TOMBSTONE)
D/Zygote  (  938): Process 1946 terminated by signal (4)
D/dalvikvm( 1053): GC_FOR_MALLOC freed 3105 objects / 758360 bytes in 47ms
I/ActivityManager( 1053): Process org.doubango.imsdroid (pid 1946) has died.
I/UsageStats( 1053): Unexpected resume of com.toshiba.homemenu while already 
resumed in org.doubango.imsdroid
E/Launcher( 1203): onResume~~~~~~~~~~~~~
D/dalvikvm( 1203): GC_EXPLICIT freed 4028 objects / 249824 bytes in 26ms
D/dalvikvm( 1203): GC_EXPLICIT freed 419 objects / 19400 bytes in 24ms
W/InputManagerService( 1053): Window already focused, ignoring focus gain of: 
com.android.internal.view.IInputMethodClient$Stub$Proxy@4a542c28
I/wpa_supplicant( 1271): CTRL-EVENT-STATE-CHANGE id=-1 state=1 
BSSID=00:00:00:00:00:00
V/WifiMonitor( 1053): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=1 
BSSID=00:00:00:00:00:00]
V/WifiStateTracker( 1053): Changing supplicant state: SCANNING ==> INACTIVE

What version of the product are you using? On what operating system?
Version 366 
Toshiba AC100 
Androide 2.2 
Kernel 2.6.32.9

$ cat /proc/cpuinfo
Processor   : ARMv7 Processor rev 0 (v7l)
processor   : 0
BogoMIPS    : 1998.84

Features    : swp half thumb fastmult vfp edsp vfpv3 vfpv3d16 
CPU implementer : 0x41
CPU architecture: 7
CPU variant : 0x1
CPU part    : 0xc09
CPU revision    : 0

Hardware    : Tegra 2 Development System
Revision    : 0000
Serial      : 0000000000000000

Please provide any additional information below.

Have test to rebuild all libtinyWRAP ( with NEON ) in debug mode ( add debug on 
file bindings/java/android/buildAll.sh (make PROJECT=$project debug BT=static 
$@ all).

But i don't have more informations .

If you want more informations or another tests , just contact me .
Thank you ,

Bye .

Original issue reported on code.google.com by verney.p...@gmail.com on 24 Feb 2011 at 9:13

GoogleCodeExporter commented 9 years ago

Original comment by boss...@yahoo.fr on 28 Feb 2011 at 9:12

GoogleCodeExporter commented 9 years ago 
Hi , 
I temporarily resolved the problem by forcing to use of libtinyWRAP.so armv5.

Bye ,

Original comment by verney.p...@gmail.com on 8 Mar 2011 at 6:16

GoogleCodeExporter commented 9 years ago 
I saw on several forums your are the best in what you do.
I have a major problem. 

My little brother played on my folio( never had to give him this) i had your 
latest update 3x and it freezed. and for one or another reasen he pushed 
several types on power butten. now my folio is crashed. if i turn it on, i just 
have the powerlight, nothing more.
Please help me dexter or i can throw my folio away.
I really don't have any more options then contacting you

thanx in advance

Original comment by beaudobb...@gmail.com on 6 Jul 2011 at 4:16

GoogleCodeExporter commented 9 years ago 
Hi ,
Have you test at the boot :
press "power" + " Volume UP " , 
after you have a menu , press
"volume Up" to reset your system .

If you have windows O.S. , connect your folio 100 with USB .
There are a new version of android for this .

Bye ,
Philippe

Original comment by verney.p...@gmail.com on 12 Jul 2011 at 6:16

GoogleCodeExporter commented 9 years ago 
all data is destroyed, it is like my device in some kind of sleepmodus.
also i have blackscreen, don`t see anything! accept the powerlight on green

Original comment by beaudobb...@gmail.com on 13 Jul 2011 at 5:49