hi,
when i run system_server in adb shell on new b70 unrooted tf it crashes
crashlog here>
Code:
09-26 18:32:29.100: INFO/DEBUG(2988): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
09-26 18:32:29.100: INFO/DEBUG(2988): Build fingerprint: 'asus/WW_epad/TF101:3.2/HTJ85B/WW_epad-8.6.5.9-20110816:user/release-keys'
09-26 18:32:29.100: INFO/DEBUG(2988): pid: 6845, tid: 6845 >>> system_server <<<
09-26 18:32:29.100: INFO/DEBUG(2988): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 00000000
09-26 18:32:29.100: INFO/DEBUG(2988): r0 00000000 r1 a7b01863 r2 00010004 r3 59d64681
09-26 18:32:29.100: INFO/DEBUG(2988): r4 a7b02250 r5 a7b01744 r6 a7b01863 r7 a81177a9
09-26 18:32:29.100: INFO/DEBUG(2988): r8 a7b01883 r9 00000000 10 00000000 fp 00000000
09-26 18:32:29.100: INFO/DEBUG(2988): ip a7b022bc sp bef2db50 lr ad335a1d pc ad335674 cpsr 60000030
09-26 18:32:29.100: INFO/DEBUG(2988): d0 447a00003f800000 d1 3f80000000000000
09-26 18:32:29.100: INFO/DEBUG(2988): d2 000000003f19999a d3 0000000000000000
09-26 18:32:29.100: INFO/DEBUG(2988): d4 0000000000000000 d5 41b42fdb75000000
09-26 18:32:29.100: INFO/DEBUG(2988): d6 3f19999ad2f1a9fc d7 3f80000000000000
09-26 18:32:29.100: INFO/DEBUG(2988): d8 0000000000000000 d9 0000000000000000
09-26 18:32:29.100: INFO/DEBUG(2988): d10 0000000000000000 d11 0000000000000000
09-26 18:32:29.100: INFO/DEBUG(2988): d12 0000000000000000 d13 0000000000000000
09-26 18:32:29.100: INFO/DEBUG(2988): d14 0000000000000000 d15 0000000000000000
09-26 18:32:29.100: INFO/DEBUG(2988): scr 00000010
09-26 18:32:29.210: INFO/DEBUG(2988): #00 pc 00035674 /system/lib/libandroid_runtime.so (_ZN7android14AndroidRuntime9getJNIEnvEv)
09-26 18:32:29.210: INFO/DEBUG(2988): #01 pc 00035a18 /system/lib/libandroid_runtime.so (_ZN7android14AndroidRuntime10callStaticEPKcS2_)
09-26 18:32:29.210: INFO/DEBUG(2988): #02 pc 00001658 /system/lib/libsystem_server.so (system_init)
09-26 18:32:29.210: INFO/DEBUG(2988): #03 pc 0000861a /system/bin/system_server
09-26 18:32:29.210: INFO/DEBUG(2988): #04 pc 00014aa0 /system/lib/libc.so (__libc_init)
09-26 18:32:29.210: INFO/DEBUG(2988): libc base address: aff00000
09-26 18:32:29.210: INFO/DEBUG(2988): code around pc:
09-26 18:32:29.210: INFO/DEBUG(2988): ad335654 68cb6801 bd104798 0005a860 47702001
09-26 18:32:29.210: INFO/DEBUG(2988): ad335664 bf004770 4a08b507 6812447a 4a056810
09-26 18:32:29.210: INFO/DEBUG(2988): ad335674 698b6801 4798a901 2000b108 9801e000
09-26 18:32:29.210: INFO/DEBUG(2988): ad335684 bf00bd0e 00010004 000530cc 44784801
09-26 18:32:29.210: INFO/DEBUG(2988): ad335694 47706800 0005a81e 460cb570 e0062500
09-26 18:32:29.210: INFO/DEBUG(2988): code around lr:
09-26 18:32:29.210: INFO/DEBUG(2988): ad3359fc 0003a03b 0003a03f 0003a042 0003a04d
09-26 18:32:29.210: INFO/DEBUG(2988): ad335a0c 0003a073 41f3e92d 4690460e fe26f7ff
09-26 18:32:29.210: INFO/DEBUG(2988): ad335a1c b1604604 f7ff4631 4605ff09 4914b950
09-26 18:32:29.210: INFO/DEBUG(2988): ad335a2c 4a142006 44794633 f7ef447a f04fed9e
09-26 18:32:29.210: INFO/DEBUG(2988): ad335a3c e01a4000 46206822 46294b0f 71c4f8d2
09-26 18:32:29.210: INFO/DEBUG(2988): stack:
09-26 18:32:29.210: INFO/DEBUG(2988): bef2db10 00000000
09-26 18:32:29.210: INFO/DEBUG(2988): bef2db14 00000000
09-26 18:32:29.210: INFO/DEBUG(2988): bef2db18 00000000
09-26 18:32:29.210: INFO/DEBUG(2988): bef2db1c 00000000
09-26 18:32:29.210: INFO/DEBUG(2988): bef2db20 00000000
09-26 18:32:29.210: INFO/DEBUG(2988): bef2db24 00000000
09-26 18:32:29.210: INFO/DEBUG(2988): bef2db28 00000004
09-26 18:32:29.210: INFO/DEBUG(2988): bef2db2c 00000001
09-26 18:32:29.210: INFO/DEBUG(2988): bef2db30 0000f8c8
09-26 18:32:29.210: INFO/DEBUG(2988): bef2db34 0000a000
09-26 18:32:29.210: INFO/DEBUG(2988): bef2db38 0000f7f8
09-26 18:32:29.210: INFO/DEBUG(2988): bef2db3c 00000000
09-26 18:32:29.210: INFO/DEBUG(2988): bef2db40 00000000
09-26 18:32:29.210: INFO/DEBUG(2988): bef2db44 aff13f17 /system/lib/libc.so
09-26 18:32:29.210: INFO/DEBUG(2988): bef2db48 df002777
09-26 18:32:29.210: INFO/DEBUG(2988): bef2db4c e3a070ad
09-26 18:32:29.210: INFO/DEBUG(2988): #00 bef2db50 00000000
09-26 18:32:29.210: INFO/DEBUG(2988): bef2db54 a7b01863 /system/lib/libsystem_server.so
09-26 18:32:29.210: INFO/DEBUG(2988): bef2db58 a7b01883 /system/lib/libsystem_server.so
09-26 18:32:29.210: INFO/DEBUG(2988): bef2db5c ad335a1d /system/lib/libandroid_runtime.so
09-26 18:32:29.210: INFO/DEBUG(2988): #01 bef2db60 00000000
09-26 18:32:29.210: INFO/DEBUG(2988): bef2db64 a7b01863 /system/lib/libsystem_server.so
09-26 18:32:29.210: INFO/DEBUG(2988): bef2db68 a7b02250
09-26 18:32:29.210: INFO/DEBUG(2988): bef2db6c a7b01744 /system/lib/libsystem_server.so
09-26 18:32:29.210: INFO/DEBUG(2988): bef2db70 00000000
09-26 18:32:29.210: INFO/DEBUG(2988): bef2db74 a81177a9 /system/lib/libbinder.so
09-26 18:32:29.210: INFO/DEBUG(2988): bef2db78 0000f7f8
09-26 18:32:29.210: INFO/DEBUG(2988): bef2db7c a7b0165b /system/lib/libsystem_server.so
09-26 18:32:29.390: INFO/BootReceiver(710): Copying /data/tombstones/tombstone_05 to DropBox (SYSTEM_TOMBSTONE)
dissassembly
Code:
text:AD335668 _ZN7android14AndroidRuntime9getJNIEnvEv ; CODE XREF: android::AndroidRuntime::callMain(char const*,int,char const* const*)+1Cp
.text:AD335668 ; android::AndroidRuntime::callStatic(char const*,char const*)+8p ...
.text:AD335668
.text:AD335668 var_C = -0xC
.text:AD335668
.text:AD335668 PUSH {R0-R2,LR}
.text:AD33566A LDR R2, =(off_AD38873C - 0xAD335670) ; _ZN7android14AndroidRuntime7mJavaVME
.text:AD33566C ADD R2, PC
.text:AD33566E LDR R2, [R2]
.text:AD335670 LDR R0, [R2]
.text:AD335672 LDR R2, =0x10004
.text:AD335674 LDR R1, [R0] <- crashed here R0=0
.text:AD335676 LDR R3, [R1,#0x18]
.text:AD335678 ADD R1, SP, #0x10+var_C
.text:AD33567A BLX R3
.text:AD33567C CBZ R0, loc_AD335682
.text:AD33567E MOVS R0, #0
.text:AD335680 B locret_AD335684
.text:AD335682 ; ---------------------------------------------------------------------------
.text:AD335682
.text:AD335682 loc_AD335682 ; CODE XREF: android::AndroidRuntime::getJNIEnv(void)+14j
.text:AD335682 LDR R0, [SP,#0x10+var_C]
.text:AD335684
.text:AD335684 locret_AD335684 ; CODE XREF: android::AndroidRuntime::getJNIEnv(void)+18j
.text:AD335684 POP {R1-R3,PC}
.text:AD335684 ; End of function android::AndroidRuntime::getJNIEnv(void)
.text:AD335684
.text:AD335684 ; ---------------------------------------------------------------------------
.text:AD335686 ALIGN 4
.text:AD335688 dword_AD335688 DCD 0x10004 ; DATA XREF: android::AndroidRuntime::getJNIEnv(void)+Ar
.text:AD33568C off_AD33568C DCD off_AD38873C - 0xAD335670
when _ZN7android14AndroidRuntime7mJavaVME is uninitialized = 0 it crashes
Iam not exploit writer only little bit rewerse engineer if this could be exploited let me now iam owner of nonrootable new tf 101 with new SBK B70KAS25 :/
Enjoy
in 3.2.1 update the bug is still here
No
10char
Maybe I found a way to sign the root with asus certificates, so the system will think it's an asus update and will flash it
gnufabio said:
Maybe I found a way to sign the root with asus certificates, so the system will think it's an asus update and will flash it
Click to expand...
Click to collapse
i think you dont have asus private rsa keys
why NO?
Z!L0G80 said:
i think you dont have asus private rsa keys
why NO?
Click to expand...
Click to collapse
You just answered your own question
There is nothing funnier than watching some-one smack them-self in the face with the Shovel Of Logic.
nevermind. delete please.
Z!L0G80 said:
why NO?
Click to expand...
Click to collapse
thebadfrog said:
No
10char
Click to expand...
Click to collapse
thebadfrog:
it was reaction on you post #3 dont uderstand your post
CaNsA:
my post's is funny for you?
ok i dont no more share my findings :/
delete this thread
Z!L0G80 said:
thebadfrog:
it was reaction on you post #3 dont uderstand your post
CaNsA:
my post's is funny for you?
ok i dont no more share my findings :/
delete this thread
Click to expand...
Click to collapse
WTF guys? I know being polite and courteous are not your strong points, but really?
Sent from my Transformer TF101 using XDA Premium App
jhanford said:
WTF guys? I know being polite and courteous are not your strong points, but really?
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
This thread is pointless, to summarize it for you. He provided the means to an "exploit" then gave the reasoning for why it can't be exploited. So, this can't be used.
Sent from my creaky Thunderbolt
mb02 said:
This thread is pointless, to summarize it for you. He provided the means to an "exploit" then gave the reasoning for why it can't be exploited. So, this can't be used.
Sent from my creaky Thunderbolt
Click to expand...
Click to collapse
other posts(2<) in this thread have nothing to do with post 1 and 2 (it is spam)
Btw. i have other ideas to root transformer maybe in few days it could be done
Seriously guys, really?
He finds a bug, disassembles the crashing code, asks for insight in the situation of wether it's a usable for an exploit and all you do is hand out metaphorical facepunches? Whatever happened to "operation iron fist"? Mods?
Give the guy some credit for trying, this isn't youtube.
ok this bug is not exploitable :/
another idea
there is:
Code:
on boot
# logtool service start
service logdog-conf /system/bin/sh /data/data/com.asus.LogTool/files/logdog-conf.sh
user root
group root
oneshot
in init.ventana.rc
it is started with root permissions on boot ?? ,but there no package com.asus.LogTool on device
i have fake app com.asus.LogTool with fake file logdog-conf.sh
but this script dont start ,why ? can i start this service manualy ?
in this script is simple "touch /sdcard/ok"
Z!L0G80 said:
ok this bug is not exploitable :/
another idea
there is:
Code:
on boot
# logtool service start
service logdog-conf /system/bin/sh /data/data/com.asus.LogTool/files/logdog-conf.sh
user root
group root
oneshot
in init.ventana.rc
it is started with root permissions on boot ?? ,but there no package com.asus.LogTool on device
i have fake app com.asus.LogTool with fake file logdog-conf.sh
but this script dont start ,why ? can i start this service manualy ?
in this script is simple "touch /sdcard/ok"
Click to expand...
Click to collapse
Maybe it's disabled somewhere, or the fact it runs in oneshot mode - I think that stuff is only ran on first run of the device (or, every time the device boots but only once).
i just want to tell the OP not to get discouraged by some of the answers ... keep trying and keep learning. Good luck
Related
Developers here :
deepss1
Aceximix
Requested developers to join the topic :
1) Karandeepdps
2) aj1234josh
3) prateek1992
4) Christianvari
Beta testers :
Yet to set beta testers.
PM me if you want to be a beta tester.
Only two beta testers.
Number of GB roms : 9
Number of ICS roms : 3 (camera not working)
Number of JB roms : 1 (with many bugs)
Aim - To solve ICS camera bug
Bugs solved -
Yet to solve any bugs.
Note :
1) Developers please do reserve posts for your contribution.
2) Also write your contribution for LG P690
3) For non P690 devs - If you want to develop for P690 make pm to me and get involved in development of P690.
There are many testers for ONet.
If you want you can buy us a beer
Contact me by mail or pm.
Email id - [email protected]
Reserved!!
Reserved!!
Direct to topic..:silly:
AS OF MY THIS LOG..I GUESS>>WE HAVE CAMERA HAL WORKING.. ANY FURTHUR IDEAS FROM YOU??
V/CameraHolder( 2101): open camera 0
I/CameraHAL( 2330): CameraHAL_GetCam_Info:
D/CameraHAL( 2330): CameraHAL_GetNum_Cameras: loading libcamera at 0xb000e5a8
I/CameraService( 2330): Opening camera 0
D/CameraHAL( 2330): qcamera_device_open: name:0 device:0x13e0c cameraId:0
D/CameraHAL( 2330): loading libcamera at 0xb000e5a8
D/QualcommCameraHardware( 2330): createInstance: E
I/QualcommCameraHardware( 2330): startCamera: camsensor name s5k5caga, flash 0
I/DEBUG ( 1482): #00 pc 0000b2f2 /system/lib/liboemcamera.so (isp3a_exit)
I/DEBUG ( 1482): #01 pc 000086f6 /system/lib/liboemcamera.so
I/DEBUG ( 1482): #02 pc 00008824 /system/lib/liboemcamera.so (cam_conf)
I/DEBUG ( 1482): 41628a28 a77460ec /system/lib/liboemcamera.so
I/DEBUG ( 1482): 41628a30 a771dc71 /system/lib/liboemcamera.so
I/DEBUG ( 1482): 41628a3c a77460ec /system/lib/liboemcamera.so
I/DEBUG ( 1482): 41628a7c a77460ec /system/lib/liboemcamera.so
I/DEBUG ( 1482): 41628a8c a77086fb /system/lib/liboemcamera.so
I/DEBUG ( 1482): 41628a94 a77460ec /system/lib/liboemcamera.so
I/DEBUG ( 1482): 41628a9c a7708829 /system/lib/liboemcamera.so
E/CameraHolder( 2101): fail to connect Camera
E/CameraHolder( 2101): java.lang.RuntimeException: Fail to connect to camera service
E/CameraHolder( 2101): at android.hardware.Camera.native_setup(Native Method)
E/CameraHolder( 2101): at android.hardware.Camera.<init>(Camera.java:320)
E/CameraHolder( 2101): at android.hardware.Camera.open(Camera.java:280)
E/CameraHolder( 2101): at com.android.camera.CameraHolder.open(CameraHolder. java:131)
E/CameraHolder( 2101): at com.android.camera.Util.openCamera(Util.java:313)
E/CameraHolder( 2101): at com.android.camera.Camera$4.run(Camera.java:1246)
E/CameraHolder( 2101): at java.lang.Thread.run(Thread.java:856)
I/ServiceManager( 1477): service 'media.camera' died
W/Camera ( 2101): Camera server died!
V/camera ( 2101): surfaceChanged. w=320. h=427
I/ActivityManager( 1598): Displayed com.android.camera/.Camera: +2s851ms
I/CameraService( 2514): CameraService started (pid=2514)
E/CameraHAL( 2514): CameraHAL_GetNum_Cameras:
D/CameraHAL( 2514): CameraHAL_GetNum_Cameras: loading libcamera at 0xb000e5a8
D/CameraHAL( 2514): CameraHAL_GetNum_Cameras: numCameras:1
Click to expand...
Click to collapse
Samsung galaxy pop have camera working and also p500 which is almost same configured to our p690
Hope we developers will solve this camera bug early.
Just little guidance from p500 and galaxy pop developers may solve our camera bug. So looking forward to camera bug and that too without any donations
Something good....
Now you can find lg optimus net forum in this website ----->>
http://www.fesilo.com/forum/lg-optimus-net-p690
So from now ask developers to post ROMs here so its easy to find ROMs for Optimus Net....
Any news? Hope they help Onet p690, please samsung pop and p500 developers
Sent from my LG-P690 using xda app-developers app
Does somebody know where to find CUSTOM ROM for this tablet ?? http://t3.gstatic.com/images?q=tbn:ANd9GcTJMYTIWWdsgvZCPrAmGWqo4iLR2D6aYp3o1zBlKn8NL1gXgDJ2cg
Send you a PM.
For further help just ask me cause I have experience with those generic crap tablets
Sent from my shooteru using Xparent Green Tapatalk 2
gesange said:
ask me cause I have experience
Click to expand...
Click to collapse
EGLconfig cannot find config to draw on surface. I have got error:
D/AndroidRuntime( 83): CheckJNI is OFF
I/SurfaceFlinger( 82): SurfaceFlinger is starting
I/SurfaceFlinger( 82): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
I/gralloc ( 82): using (fd=10)
I/gralloc ( 82): id =
I/gralloc ( 82): xres = 800 px
I/gralloc ( 82): yres = 480 px
I/gralloc ( 82): xres_virtual = 800 px
I/gralloc ( 82): yres_virtual = 960 px
I/gralloc ( 82): bpp = 32
I/gralloc ( 82): r = 16:8
I/gralloc ( 82): g = 8:8
I/gralloc ( 82): b = 0:8
I/gralloc ( 82): width = 127 mm (160.000000 dpi)
I/gralloc ( 82): height = 76 mm (160.421051 dpi)
I/gralloc ( 82): refresh rate = 59.75 Hz
D/libEGL ( 82): loaded /system/lib/egl/libGLES_android.so
I/dalvikvm( 83): DexOpt: source file mod time mismatch (40fbbd60 vs 41115696)
D/dalvikvm( 83): ODEX file is stale or bad; removing and retrying (/data/dalvik-cache/[email protected]@[email protected])
D/libEGL ( 82): loaded /system/lib/egl/libEGL_mali.so
D/libEGL ( 82): loaded /system/lib/egl/libGLESv1_CM_mali.so
D/libEGL ( 82): loaded /system/lib/egl/libGLESv2_mali.so
D/Kernel ( 0): <7>[ 6.270000] UMP<2>: New session opened
E/SurfaceFlinger( 82): couldn't find an EGLConfig matching the screen format
D/dalvikvm( 83): DexOpt: --- BEGIN 'core.jar' (bootstrap=1) ---
E/ ( 82): mali_surface* __egl_platform_create_surface_from_native_buffer(android_native_buffer_t*, egl_surface*, mali_base_ctx_type*):488 [EGL-ERROR] invalid buffer handle given (0x10110)
E/ ( 82): void __egl_platform_dequeue_buffer(egl_surface*):1234 [EGL-ERROR] Failed to create a surface from native buffer (0x10078)
F/libc ( 82): Fatal signal 11 (SIGSEGV) at 0x00000023 (code=1)
What to do with it?
Problem with EGL bpp=32bits does not match eglSurface: 5-6-5-0 = 16bits.
How to insert 8-8-8-8 to EGLconfig?
can you help me ?
gesange said:
Send you a PM.
For further help just ask me cause I have experience with those generic crap tablets
Sent from my shooteru using Xparent Green Tapatalk 2
Click to expand...
Click to collapse
allwinner a13 softwinerEvb 4.0.4 7" MID
model number : softwinerEvb
android version : 4.0.4
baseband version : 1.5
kernel version : 3.0.8+ [email protected] #1 TueFeb 26 14:49:51 CST 2013
Build number : 713B7.V2.00.TZX.R01.eng.dan0308.0304
anyone help to upgrade?
peetyj said:
allwinner a13 softwinerEvb 4.0.4 7" MID
model number : softwinerEvb
android version : 4.0.4
baseband version : 1.5
kernel version : 3.0.8+ [email protected] #1 TueFeb 26 14:49:51 CST 2013
Build number : 713B7.V2.00.TZX.R01.eng.dan0308.0304
Click to expand...
Click to collapse
just curious to know any upgrade for this tablet?
because it can't connect when browsing sometimes
my tablet detail here:
MODE Q8 (A-1)
P:Q8-4.04-CZY-TZX0309-YY-8.0
ROHS
MODEL NUMBER Q8
ANDROID 4.04
BASEBAND VER 1.5
KERNEL VER 3.0.8 + [email protected] #1 Tue Feb 26 14:49:51 CST 2013
BUILD NUMBER 713B7.V2.00. TZX.R01.eng.gc0309.20130308
BOARD ID FIRMWARE TZX_713_83-16B
CHIPSET ALLWINNER A13 D2195CA-23C1
256 memory 1 camera
thanks
email ksuwanto8ksd gmail com
Ok, I dont know android programming ...
But I'm trying to find what the problem with the USSD.
Only with running a "logcat-b radio," and using USSD code on GSM,
The logcat show me if supports but does not display the results.
Code:
04-20 14:03:54.256 1409 1409 D RILJ : [0717]> SEND_USSD *10#
04-20 14:03:54.256 1197 1284 I RIL-MAIN: onReq: reqCode = 29, dataLen = 4
04-20 14:03:54.256 1197 1286 I RIL-MX : Ch0 > 0533AT+CUSD=1,*10#,0
04-20 14:03:54.256 1197 1286 I RIL-MX :
04-20 14:03:54.287 1197 1285 I RIL-MX : Read Ch0 << 0533+CUSD:eek:K
04-20 14:03:54.287 1409 1545 D RILJ : [0717]< SEND_USSD
04-20 14:03:54.342 1409 1409 D RILJ : [0718]> SET_MUTE false
04-20 14:03:54.342 1197 1284 I RIL-MAIN: onReq: reqCode = 53, dataLen = 4
04-20 14:03:54.342 1197 1286 I RIL-MX : Ch1 > 0534AT+CMUT=0
04-20 14:03:54.365 1197 1285 I RIL-MX : Read Ch1 << 0534+CMUT:eek:K
04-20 14:03:54.365 1409 1545 D RILJ : [0718]< SET_MUTE
04-20 14:03:54.592 1197 1285 I RIL-MX : Read Ch0 << 0294~+RSSI=0,15,99,99,0,0,0
04-20 14:03:54.599 1409 1409 D GSM : handleMessage what 12
04-20 14:03:55.334 1197 1285 I RIL-MX : Read Ch0 << 0295~+CREG=1,7,297D,00008D73,0,0,0,0,0,0
04-20 14:03:55.334 1409 1545 D RILJ : [UNSL]< UNSOL_RESPONSE_NETWORK_STATE_CHANGED
04-20 14:03:55.334 1409 1409 D GSM : handleMessage what 2
04-20 14:03:55.342 1409 1409 D RILJ : [0719]> OPERATOR
04-20 14:03:55.349 1197 1284 I RIL-MAIN: onReq: reqCode = 22, dataLen = 0
04-20 14:03:55.349 1197 1286 I RIL-MX : Ch0 > 0535AT+COPS?
04-20 14:03:55.365 1409 1409 D RILJ : [0720]> GPRS_REGISTRATION_STATE
04-20 14:03:55.373 1197 1285 I RIL-MX : Read Ch0 << 0535+COPS=0,COL MOV / TIGO,TIGO COL,732103
04-20 14:03:55.373 1409 1545 D RILJ : [0719]< OPERATOR {COL MOV / TIGO, TIGO COL, 732103}
04-20 14:03:55.381 1197 1284 I RIL-MAIN: onReq: reqCode = 21, dataLen = 0
04-20 14:03:55.381 1197 1286 I RIL-MX : Ch0 > 0536AT+CGREG?
04-20 14:03:55.381 1197 1286 I RIL-MX :
04-20 14:03:55.381 1409 1409 D RILJ : [0721]> REGISTRATION_STATE
04-20 14:03:55.388 1197 1284 I RIL-MAIN: onReq: reqCode = 20, dataLen = 0
04-20 14:03:55.388 1409 1409 D RILJ : [0722]> QUERY_NETWORK_SELECTION_MODE
04-20 14:03:55.388 1197 1284 I RIL-MAIN: onReq: reqCode = 45, dataLen = 0
04-20 14:03:55.388 1409 1409 D GSM : handleMessage what 6
04-20 14:03:55.412 1197 1285 I RIL-MX : Read Ch0 << 0536+CGREG=1,7,297D,00008D73,0
04-20 14:03:55.412 1197 1286 I RIL-MOD : onReqComp: Ch0 process reqCode = 20
04-20 14:03:55.412 1197 1286 I RIL-MX : Ch0 > 0537AT+CREG?
04-20 14:03:55.412 1409 1545 D RILJ : [0720]< GPRS_REGISTRATION_STATE {1, 297d, 8d73, 2, 0}
04-20 14:03:55.412 1409 1409 D GSM : handleMessage what 5
04-20 14:03:55.451 1197 1285 I RIL-MX : Read Ch0 << 0537+CREG=1,7,297D,00008D73,0,0,0,0,0,0
04-20 14:03:55.451 1197 1286 I RIL-MOD : onReqComp: Ch0 process reqCode = 45
04-20 14:03:55.451 1197 1286 I RIL-MX : Ch0 > 0538AT+COPSM?
04-20 14:03:55.451 1409 1545 D RILJ : [0721]< REGISTRATION_STATE {1, 297d, 8d73, 2, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0}
04-20 14:03:55.451 1409 1409 D GSM : handleMessage what 4
04-20 14:03:55.490 1197 1285 I RIL-MX : Read Ch0 << 0538+COPSM=0
04-20 14:03:55.490 1409 1545 D RILJ : [0722]< QUERY_NETWORK_SELECTION_MODE {0}
04-20 14:03:55.490 1409 1409 D GSM : handleMessage what 14
04-20 14:03:55.490 1409 1409 D GSM : Network selection mode = false
04-20 14:03:55.490 1409 1409 D GSM : Poll ServiceState done: oldSS=[0 home domestic COL MOV / TIGO TIGO COL 732103 EDGE CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false] newSS=[0 home domestic COL MOV / TIGO TIGO COL 732103 EDGE CSS not supported -1 -1RoamInd: -1DefRoamInd: -1EmergOnly: false] oldGprs=0 newGprs=0 oldType=EDGE newType=EDGE
04-20 14:03:58.646 1197 1285 I RIL-MX : Read Ch0 << 0296~+CUSD=0,15,SALDO:$180.50;BONO:$0.00,0+0minTigo,0+0+0minOtroOpdr,35smsTigo,0smsToDes,0minTigoNoche,0minOtroNoche,0minFavorito,0minDia,0minCUG
04-20 14:03:58.654 1409 1545 D RILJ : [UNSL]< UNSOL_ON_USSD 0
04-20 14:03:58.693 1197 1285 I RIL-MX : Read Ch0 << 0297~+CUSD=2,15,SALDO:$180.50;BONO:$0.00,0+0minTigo,0+0+0minOtroOpdr,35smsTigo,0smsToDes,0minTigoNoche,0minOtroNoche,0minFavorito,0minDia,0minCUG
04-20 14:03:58.693 1409 1545 D RILJ : [UNSL]< UNSOL_ON_USSD 2
The last two lines show the result that I should appear after executing the USSD.
But I always get the response of MMI complete
USSD does not work, you're limited to MMI only. Period. This device was not made with GSM in mind.
You're not the first (and not even in the first 10) person who tried to “fix” this.
Good luck if you have time to spare on this, I guess. Note that USSD processing is core Android functionality and you cannot just write an app which replaces these functions.
Try custom ROMs if you really need USSD.
I try a custom rom but still same problem...
the droid 3 has the same chip as the droid 2 global can run USSD codes.
I heard that it was a problem with not being supported in the baseband kernel. I doubt it is easily fixable.
When I try to activate NFC it turns off again after 4 seconds.
Can someone tell me if this is software or hardware related?
Here is my logcat:
12-17 07:38:34.325 I/NfcService(1078): Enabling NFC
12-17 07:38:34.325 E/NfcAdaptation(1078): NfcAdaptation::Initialize: ver=NFCDROID_MI_422.10.0.15 nfa=NFA_MI_1.03.62+
12-17 07:38:34.325 I/BrcmNfcNfa(1078): NFC_TASK started.
12-17 07:38:34.325 E/NfcNciHal(1078): HaiInitializeLibrary: ver=NFCDROID_MI_422.10.0.15 nfa=NFA_MI_1.03.62+
12-17 07:38:34.325 I/USERIAL_LINUX(1078): USERIAL_Init
12-17 07:38:34.325 I/NfcNciHal(1078): HAL_NfcInitialize (): NFC_HAL_TASK id=0
12-17 07:38:34.325 I/BrcmNfcNfa(1078): nfa_dm_init ()
12-17 07:38:34.325 I/BrcmNfcNfa(1078): nfa_sys_register () id=1, enable_cplt_mask=0x0
12-17 07:38:34.325 I/BrcmNfcNfa(1078): nfa_sys_register () id=3, enable_cplt_mask=0x8
12-17 07:38:34.325 I/BrcmNfcNfa(1078): nfa_rw_init ()
12-17 07:38:34.325 I/BrcmNfcNfa(1078): nfa_sys_register () id=6, enable_cplt_mask=0x48
12-17 07:38:34.325 I/BrcmNfcNfa(1078): nfa_ce_init ()
12-17 07:38:34.325 I/BrcmNfcNfa(1078): nfa_sys_register () id=7, enable_cplt_mask=0xc8
12-17 07:38:34.325 I/BrcmNfcNfa(1078): nfa_ee_init ()
12-17 07:38:34.325 I/BrcmNfcNfa(1078): nfa_sys_register () id=2, enable_cplt_mask=0xcc
12-17 07:38:34.325 I/BrcmNfcNfa(1078): LLCP - llcp_init ()
12-17 07:38:34.325 I/BrcmNfcNfa(1078): num_rx_buff = 9, rx_congest_start = 6, rx_congest_end = 4, max_num_ll_rx_buff = 2
12-17 07:38:34.325 I/BrcmNfcNfa(1078): max_num_tx_buff = 21, max_num_ll_tx_buff = 6
12-17 07:38:34.325 I/BrcmNfcNfa(1078): LLCP_RegisterServer (): SAP:0x1, link_type:0x2, ServiceName:<urn:nfc:sn:sdp>
12-17 07:38:34.325 I/BrcmNfcNfa(1078): LLCP_RegisterServer (): Registered SAP = 0x01
12-17 07:38:34.325 I/BrcmNfcNfa(1078): NFA_Enable ()
12-17 07:38:34.325 I/BrcmNfcNfa(1078): NFC_SetTraceLevel () new_level = 1
12-17 07:38:34.325 I/USERIAL_LINUX(1078): USERIAL_Open(): enter
12-17 07:38:34.325 I/USERIAL_LINUX(1078): USERIAL_Open() device: /dev/bcm2079x port=5, uart_port=0 WAKE_DELAY(20) WRITE_DELAY(20) POWER_ON_DELAY(0) PRE_POWER_OFF_DELAY(10) POST_POWER_OFF_DELAY(0)
12-17 07:38:34.345 I/USERIAL_LINUX(1078): USERIAL_Open(): exit
12-17 07:38:35.195 V/PanelView(900): animationTick called with dtms=0; nothing to do (h=858.0 v=-6750.0)
12-17 07:38:35.355 E/USERIAL_LINUX(1078): USERIAL_Write len = 4, ret = -1, errno = 5
12-17 07:38:35.425 W/InputMethodManagerService(772): Window already focused, ignoring focus gain of: [email protected] attribute=null, token = [email protected]
12-17 07:38:35.435 V/PhoneStatusBar(900): setLightsOn(true)
12-17 07:38:37.365 E/BrcmNfcJni(1078): nfcManager_doInitialize: fail nfa enable; error=0x0
12-17 07:38:38.275 I/BrcmNfcNfa(1078): GKI TASK_DEAD received. exit thread 3...
12-17 07:38:38.475 W/NfcService(1078): Error enabling NFC
I have a same problem on S4 mini with the same error since 19-DEC:
BrcmNfcJni
nfcManager_doInitialize: fail nfa enable; error=0x0
kernel:
https://github.com/yangyangnau/android_kernel_xiaomi_msm8937
device:
https://github.com/yangyangnau/android_device_xiaomi_land
local_manifests and patchs:
https://github.com/yangyangnau/redmi3s-misc
Reserved
STATUS REPORT:
boot: almost OK
random freezing
random reboot
Reserved
Does it mean xiaomi hasn't release the kernel yet?
Sent from my Redmi 3 using Tapatalk
h4fiz said:
Does it mean xiaomi hasn't release the kernel yet?
Sent from my Redmi 3 using Tapatalk
Click to expand...
Click to collapse
Yeah! I'm porting linux kernel for redmi3s.
http://forum.xda-developers.com/redmi-3/development/port-linux-kernel-source-xiaomi-redmi3s-t3469965
yangyangnau said:
Yeah! I'm porting linux kernel for redmi3s.
http://forum.xda-developers.com/redmi-3/development/port-linux-kernel-source-xiaomi-redmi3s-t3469965
Click to expand...
Click to collapse
Wow, keep working on dev ?? so you do have a redmi 3s?? Cause i have a plan to buy redmi 3x in near future, so maybe i can help you testing the kernel
Sent from my Redmi 3 using Tapatalk
h4fiz said:
Wow, keep working on dev so you do have a redmi 3s?? Cause i have a plan to buy redmi 3x in near future, so maybe i can help you testing the kernel
Sent from my Redmi 3 using Tapatalk
Click to expand...
Click to collapse
Oh, NO, It's HELL.
If you think it's important to get sourcecode, don't jump to redmi3s/3x yet.
If you insist it, you are wellcome.
yangyangnau said:
Oh, NO, It's HELL.
If you think it's important to get sourcecode, don't jump to redmi3s/3x yet.
If you insist it, you are wellcome.
Click to expand...
Click to collapse
I'm not that hurry to get the source code, i can live with miui though, but if there is a faster rom builded from source then i'll move there ??? cause i really need fingerprint on it, and the the design that different from any other redmi 3 varian ???
Sent from my Redmi 3 using Tapatalk
@yangyangnau pm sent.
Very interesting! I've been away from Xiaomi for about 2 years... but decided to get the Redmi 3S as backup phone. Now running some Chinese CM 13 rom, but this looks promising.
Totally forgot about Xiaomi and the trouble surround kernel sources. I remember with the Mi2S we used a kernel build from scratch too for development. But it seems they do release stuff nowadays? Only not directly?
Robin>Hood said:
Very interesting! I've been away from Xiaomi for about 2 years... but decided to get the Redmi 3S as backup phone. Now running some Chinese CM 13 rom, but this looks promising.
Totally forgot about Xiaomi and the trouble surround kernel sources. I remember with the Mi2S we used a kernel build from scratch too for development. But it seems they do release stuff nowadays? Only not directly?
Click to expand...
Click to collapse
Xiaomi released some source, but redmi 3s doesn't get luck.
https://github.com/MiCode/Xiaomi_Kernel_OpenSource
You're the best,
I also wrote a complaint letter today to them
Hi, I've used your device source code as base for my own port, but I updated most of the HAL drivers from stock QC files.
But I can't boot. I get stuck with an error "Too many open files". Did you ever had this bug ?
I also did my own kernel based of the LA.UM.5.3_RB1.1 It seam to be the most up to date for MSM8937.
You can have a look at my port here :
Kernel : https://github.com/supercairos/android_kernel_xiaomi_msm8937
Device : https://github.com/supercairos/android_device_xiaomi_land
Supercairos said:
Hi, I've used your device source code as base for my own port, but I updated most of the HAL drivers from stock QC files.
But I can't boot. I get stuck with an error "Too many open files". Did you ever had this bug ?
I also did my own kernel based of the LA.UM.5.3_RB1.1 It seam to be the most up to date for MSM8937.
You can have a look at my port here :
Kernel : https://github.com/supercairos/android_kernel_xiaomi_msm8937
Device : https://github.com/supercairos/android_device_xiaomi_land
Click to expand...
Click to collapse
copy from porting kernel thread:
About LA.UM.5.3-01110-8x37.0:
I just try to find a QAEP release which match the release date of Redmi 3S as much as possible. Nothing more.
About "too many open files":
My repo #deccaf5 (9.21.2016) can boot cm, but it need force reboot several times.
After that commit, the error same as yours. Sorry for my bad.
https://github.com/yangyangnau/andro...ce_xiaomi_land
A few of days ago, I'm try using my kernel and proprietary-files.txt with the repo below.
https://github.com/Silentlys/android_device_xiaomi_land
Clean the fake kernel header tree. Clean the malware (2345 stuff). Clean TWRP stuffs.
No luck. Just get black screen. Can't remember the error messages. Could be "too many open files".
I guess the proprietary-files.txt is a problem.
Thanks!
Might be
I will investigate more soon. I've tried to raise the Open file limit but doesn't seams to fix the issue.
About the Kernel Xiaomi based his SW on, it's probably LA.UM.5.1_rb1.4 (not sure what manifest exactly quite hard to test ) as it's the branch that Ardreno was build on (you can check the logs and see that at each app boot). I based mine on the lastest branch that support msm8937_64.
Supercairos said:
Might be
I will investigate more soon. I've tried to raise the Open file limit but doesn't seams to fix the issue.
About the Kernel Xiaomi based his SW on, it's probably LA.UM.5.1_rb1.4 (not sure what manifest exactly quite hard to test ) as it's the branch that Ardreno was build on (you can check the logs and see that at each app boot). I based mine on the lastest branch that support msm8937_64.
Click to expand...
Click to collapse
I don't think the kernel version is a big issue, but i will check it.
yangyangnau said:
I don't think the kernel version is a big issue, but i will check it.
Click to expand...
Click to collapse
Agreed
update:
https://github.com/Silentlys/android_device_xiaomi_land/issues/3
https://github.com/Silentlys/proprietary_vendor_xiaomi
we can update the proprietary-files.txt, and try to build CM soon.
Still can't boot CM-13.
[ 12.092118] surfaceflinger[425]: unhandled input address range fault (11) at 0x6e5f6570697012, esr 0x92000044
[ 12.092131] pgd = ffffffc07679f000
[ 12.092138] [6e5f6570697012] *pgd=0000000000000000, *pud=0000000000000000
[ 12.092148]
[ 12.092159] CPU: 7 PID: 425 Comm: surfaceflinger Tainted: G W 3.18.20-g5d5fa78-dirty #1
[ 12.092165] Hardware name: Qualcomm Technologies, Inc. MSM8937-PMI8950 QRD SKU1 (DT)
[ 12.092172] task: ffffffc078c6be80 ti: ffffffc075820000 task.ti: ffffffc075820000
[ 12.092180] PC is at 0x7fb5294fc8
[ 12.092186] LR is at 0x7fb5294fac
[ 12.092193] pc : [<0000007fb5294fc8>] lr : [<0000007fb5294fac>] pstate: 80000000
[ 12.092198] sp : 0000007ff6cb01b0
[ 12.092204] x29: 0000007ff6cb01d0 x28: 0000000000000000
[ 12.092213] x27: 0000000000000000 x26: 0000007fb5354048
[ 12.092223] x25: 0000007fb52f8060 x24: 00000055cbc274c9
[ 12.092232] x23: 00000055cbc26fb0 x22: 00000055cbc273e0
[ 12.092241] x21: 0000000000000004 x20: 00000055cbc273e0
[ 12.092250] x19: 00000055cbc27ea0 x18: 0000000000000000
[ 12.092260] x17: 0000000000000000 x16: 0000007fb7340a58
[ 12.092269] x15: 0000000000000007 x14: 0000000000000043
[ 12.092280] x13: 0000000000000004 x12: 0000000000000072
[ 12.092289] x11: 0000000000000007 x10: 7069702030313a6d
[ 12.092298] x9 : 00000055cbc27e40 x8 : 00000055cbc27fec
[ 12.092307] x7 : 0000000000000040 x6 : 0000000000000000
[ 12.092316] x5 : 0000000000000001 x4 : 0000000000000000
[ 12.092325] x3 : 0000000000000004 x2 : 0000000000000001
[ 12.092334] x1 : 0000007fb7347eb4 x0 : 756e5f6570697012
[ 12.092342]
[ 12.096796] init: Service 'surfaceflinger' (pid 425) killed by signal 11
[ 12.096828] init: Service 'surfaceflinger' (pid 425) killing any children in process group
Click to expand...
Click to collapse
If I do crazy thing as below, the backlight flashes.
Code:
chmod -R 777 /dev
and get logcat:
01-12 04:26:01.870 1738 1738 I gralloc : using (fd=19)
01-12 04:26:01.870 1738 1738 I gralloc : id = mdssfb_80000
01-12 04:26:01.870 1738 1738 I gralloc : xres = 720 px
01-12 04:26:01.870 1738 1738 I gralloc : yres = 1280 px
01-12 04:26:01.870 1738 1738 I gralloc : xres_virtual = 720 px
01-12 04:26:01.870 1738 1738 I gralloc : yres_virtual = 2560 px
01-12 04:26:01.870 1738 1738 I gralloc : bpp = 32
01-12 04:26:01.870 1738 1738 I gralloc : r = 0:8
01-12 04:26:01.870 1738 1738 I gralloc : g = 8:8
01-12 04:26:01.870 1738 1738 I gralloc : b = 16:8
01-12 04:26:01.871 1738 1738 I gralloc : width = 62 mm (294.967743 dpi)
01-12 04:26:01.871 1738 1738 I gralloc : height = 110 mm (295.563629 dpi)
01-12 04:26:01.871 1738 1738 I gralloc : refresh rate = 369.50 Hz
01-12 04:26:01.876 1738 1738 E SurfaceFlinger: hwcomposer module not found
01-12 04:26:01.878 1738 1738 I SurfaceFlinger: EGL information:
01-12 04:26:01.878 1738 1738 I SurfaceFlinger: vendor : Android
01-12 04:26:01.878 1738 1738 I SurfaceFlinger: version : 1.4 Android META-EGL
01-12 04:26:01.878 1738 1738 I SurfaceFlinger: extensions: EGL_KHR_get_all_proc_addresses EGL_ANDROID_presentation_time EGL_KHR_swap_buffers_with_damage EGL_KHR_image EGL_KHR_image_base EGL_KHR_lock_surface EGL_KHR_gl_texture_2D_image EGL_KHR_gl_texture_3D_image EGL_KHR_gl_texture_cubemap_image EGL_KHR_gl_renderbuffer_image EGL_KHR_reusable_sync EGL_KHR_fence_sync EGL_KHR_create_context EGL_KHR_surfaceless_context EGL_EXT_create_context_robustness EGL_ANDROID_image_native_buffer EGL_KHR_wait_sync EGL_ANDROID_recordable EGL_KHR_partial_update EGL_KHR_create_context_no_error
01-12 04:26:01.878 1738 1738 I SurfaceFlinger: Client API: OpenGL_ES
01-12 04:26:01.878 1738 1738 I SurfaceFlinger: EGLSurface: 8-8-8-8, config=0x55b063d2a0
01-12 04:26:01.886 1738 1738 I SurfaceFlinger: OpenGL ES informations:
01-12 04:26:01.886 1738 1738 I SurfaceFlinger: vendor : Qualcomm
01-12 04:26:01.886 1738 1738 I SurfaceFlinger: renderer : Adreno (TM) 505
01-12 04:26:01.886 1738 1738 I SurfaceFlinger: version : OpenGL ES 3.1 [email protected] ([email protected])
01-12 04:26:01.886 1738 1738 I SurfaceFlinger: extensions: GL_OES_EGL_image GL_OES_EGL_image_external GL_OES_EGL_sync GL_OES_vertex_half_float GL_OES_framebuffer_object GL_OES_rgb8_rgba8 GL_OES_compressed_ETC1_RGB8_texture GL_AMD_compressed_ATC_texture GL_KHR_texture_compression_astc_ldr GL_KHR_texture_compression_astc_hdr GL_OES_texture_compression_astc GL_OES_texture_npot GL_EXT_texture_filter_anisotropic GL_EXT_texture_format_BGRA8888 GL_OES_texture_3D GL_EXT_color_buffer_float GL_EXT_color_buffer_half_float GL_QCOM_alpha_test GL_OES_depth24 GL_OES_packed_depth_stencil GL_OES_depth_texture GL_OES_depth_texture_cube_map GL_EXT_sRGB GL_OES_texture_float GL_OES_texture_float_linear GL_OES_texture_half_float GL_OES_texture_half_float_linear GL_EXT_texture_type_2_10_10_10_REV GL_EXT_texture_sRGB_decode GL_OES_element_index_uint GL_EXT_copy_image GL_EXT_geometry_shader GL_EXT_tessellation_shader GL_OES_texture_stencil8 GL_EXT_shader_io_blocks GL_OES_shader_image_atomic GL_OES_sample_variables GL_EXT_texture_border_clamp GL_EXT_multisampled_render_to_texture
01-12 04:26:01.886 1738 1738 I SurfaceFlinger: GL_MAX_TEXTURE_SIZE = 16384
01-12 04:26:01.886 1738 1738 I SurfaceFlinger: GL_MAX_VIEWPORT_DIMS = 16384
01-12 04:26:01.887 1738 1738 W GraphicBufferAllocator: alloc(720, 1280, 1, 20001a00, ...) failed -12 (Out of memory)
01-12 04:26:01.887 1738 1738 D GraphicBufferAllocator: Allocated buffers:
01-12 04:26:01.887 1738 1738 D GraphicBufferAllocator: 0x55b071f040: 3600.00 KiB | 720 ( 720) x 1280 | 1 | 0x20001a00
01-12 04:26:01.887 1738 1738 D GraphicBufferAllocator: 0x55b071f290: 3600.00 KiB | 720 ( 720) x 1280 | 1 | 0x20001a00
01-12 04:26:01.887 1738 1738 D GraphicBufferAllocator: Total allocated (estimate): 7200.00 KB
01-12 04:26:01.887 1738 1738 E : GraphicBufferAlloc::createGraphicBuffer(w=720, h=1280) failed (Out of memory), handle=0x0
01-12 04:26:01.887 1738 1738 E BufferQueueProducer: [FramebufferSurface] allocateBuffers: failed to allocate buffer (0 x 0, format 1, usage 536877568)
01-12 04:26:01.889 1738 1738 D SurfaceFlinger: Set power mode=2, type=0 flinger=0x55b05b2550
01-12 04:26:01.931 501 501 I ServiceManager: Waiting for service AtCmdFwd...
01-12 04:26:01.962 1743 1743 I Dpps : static DppsServer *DppsServer::GetInstance(): DppsServer ref count increased to 1
01-12 04:26:01.962 1742 1742 F appproc : app_process: Unable to determine ABI list from property ro.product.cpu.abilist64.
01-12 04:26:01.962 1742 1742 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 1742 (app_process64)
01-12 04:26:01.962 1743 1743 I Dpps : InitPrimaryContextFeatures():265 Dpps feature enable properties are false, skipping primary feature context init
01-12 04:26:01.963 452 452 I DEBUG : property debug.db.uid not set; NOT waiting for gdb.
01-12 04:26:01.963 452 452 I DEBUG : HINT: adb shell setprop debug.db.uid 100000
01-12 04:26:01.963 452 452 I DEBUG : HINT: adb forward tcp:5039 tcp:5039
01-12 04:26:02.014 452 452 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
01-12 04:26:02.014 452 452 F DEBUG : CM Version: '13.0-20161007-UNOFFICIAL-land'
01-12 04:26:02.014 452 452 F DEBUG : Build fingerprint: 'Xiaomi/land/land:6.0.1/MMB29M/V7.5.9.0.MALCNDE:user/release-keys'
01-12 04:26:02.014 452 452 F DEBUG : Revision: '0'
01-12 04:26:02.014 452 452 F DEBUG : ABI: 'arm64'
01-12 04:26:02.014 452 452 F DEBUG : pid: 1742, tid: 1742, name: app_process64 >>> /system/bin/app_process64 <<<
01-12 04:26:02.014 452 452 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
01-12 04:26:02.023 452 452 F DEBUG : Abort message: 'app_process: Unable to determine ABI list from property ro.product.cpu.abilist64.'
Click to expand...
Click to collapse