Related
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.
Hello everyone,
Xiaomi hasn't released Redmi 3s land kernel to us. It's SHAME.(2016.09.28)
I want to run normal GNU/Linux OS on Xiaomi Redmi 3S.
So I am porting Linux kernel base on QAEP kernel and Redmi3 drivers.
My porting kernel version is 3.18.20.
https://github.com/yangyangnau/android_kernel_xiaomi_msm8937
BASE ON:
* QAEP for msm8937:
Code:
lynx -dump -width 120 https://wiki.codeaurora.org/xwiki/bin/QAEP/release | grep msm8937
06.23.2016 LA.UM.5.3.1-01010-89xx.0 msm8937_64 LA.UM.5.3.1-01010-89xx.0.xml 06.00.01
06.10.2016 LA.UM.5.3-04410-89xx.0 msm8937_64 LA.UM.5.3-04410-89xx.0.xml 06.00.01
06.09.2016 LA.UM.5.3.1-00610-89xx.0 msm8937_64 LA.UM.5.3.1-00610-89xx.0.xml 06.00.01
06.07.2016 LA.UM.5.1-04210-8x37.0 msm8937_64 LA.UM.5.1-04210-8x37.0.xml 06.00.01
06.06.2016 LA.UM.5.3.1-00610-89xx.0 msm8937_64 LA.UM.5.3.1-00610-89xx.0.xml 06.00.01
05.31.2016 LA.UM.5.3-03710-89xx.0 msm8937_64 LA.UM.5.3-03710-89xx.0.xml 06.00.01
05.24.2016 LA.UM.5.3.1-00310-89xx.0 msm8937_64 LA.UM.5.3.1-00310-89xx.0.xml 06.00.01
05.15.2016 LA.UM.5.1-04010-8x37.0 msm8937_64 LA.UM.5.1-04010-8x37.0.xml 06.00.01
04.29.2016 LA.UM.5.1-03810-8x37.0 msm8937_64 LA.UM.5.1-03810-8x37.0.xml 06.00.01
04.14.2016 LA.UM.5.1-03610-8x37.0 msm8937_64 LA.UM.5.1-03610-8x37.0.xml 06.00.01
03.30.2016 LA.UM.5.1-03210-8x37.0 msm8937_32 LA.UM.5.1-03210-8x37.0.xml 06.00.01
03.22.2016 LA.UM.5.3-01410-8x37.0 msm8937_64 LA.UM.5.3-01410-8x37.0.xml 06.00.01
03.15.2016 LA.UM.5.1-02910-8x37.0 msm8937_64 LA.UM.5.1-02910-8x37.0.xml 06.00.01
02.28.2016 LA.UM.5.1-02410-8x37.0 msm8937_64 LA.UM.5.1-02410-8x37.0.xml 06.00.01
02.25.2016 LA.UM.5.3-01110-8x37.0 msm8937_64 LA.UM.5.3-01110-8x37.0.xml 06.00.01
02.12.2016 LA.UM.5.1-02110-8x37.0 msm8937_64 LA.UM.5.1-02110-8x37.0.xml 06.00.01
02.12.2016 LA.UM.5.3-00610-8x37.0 msm8937_64 LA.UM.5.3-00610-8x37.0.xml 06.00.01
01.29.2016 LA.UM.5.1-01910-8x37.0 msm8937_64 LA.UM.5.1-01910-8x37.0.xml 06.00.01
01.21.2016 LA.UM.5.1-01610-8x37.0 msm8937_64 LA.UM.5.1-01610-8x37.0.xml 06.00.01
01.11.2016 LA.UM.5.1-01310-8x37.0 msm8937_64 LA.UM.5.1-01310-8x37.0.xml 06.00.01
12.21.2015 LA.UM.5.1-03700-8x37.0 msm8937_64 LA.UM.5.1-03700-8x37.0.xml 06.00.00
12.04.2015 LA.UM.5.1-01400-8x37.0 msm8937_64 LA.UM.5.1-01400-8x37.0.xml 06.00.00
11.21.2015 LA.UM.5.1-01010-8x37.0 msm8937_64 LA.UM.5.1-01010-8x37.0.xml 06.00.00
Click to expand...
Click to collapse
* QAEP kernel for msm8937:
Code:
mkdir -p android-source/qaep
cd android-source/qaep
repo init -u git://codeaurora.org/platform/manifest.git -b release -m LA.UM.5.3-01110-8x37.0.xml --repo-url=git://codeaurora.org/tools/repo.git
grep kernel/msm-3.18 .repo/manifest.xml
<project name="kernel/msm-3.18" path="kernel" revision="985da67f18431ac30e2c2d46b68067b71ebf8688" upstream="LA.UM.5.3_rb1.1"/>
<project name="kernel/msm-3.18" path="kernel" revision="a199af79618518255f6eb6656e1ba6fcb6b1e7ff" upstream="LA.UM.5.1_rb1.4"/>
Click to expand...
Click to collapse
git://codeaurora.org/kernel/msm-3.18 branchs:
LA.UM.5.1_rb1.3
LA.UM.5.1_rb1.4
LA.UM.5.3.1_rb1
LA.UM.5.3_rb1.1
06.23.2016 LA.UM.5.3.1-01010-89xx.0 msm-3.18 df25fdbbe93e8f1c16268faed04a065bf1cd7d89 LA.UM.5.3.1_rb1
06.10.2016 LA.UM.5.3-04410-89xx.0 msm-3.18 8235259992248adedca456006c027a938cc0f9d3 LA.UM.5.3_rb1.1
06.09.2016 LA.UM.5.3.1-00610-89xx.0 msm-3.18 235372e1f95010f66f4d353ac15402a4c314607f LA.UM.5.3.1_rb1
06.07.2016 LA.UM.5.1-04210-8x37.0 msm-3.18 a199af79618518255f6eb6656e1ba6fcb6b1e7ff LA.UM.5.1_rb1.4
06.06.2016 LA.UM.5.3.1-00610-89xx.0 msm-3.18 235372e1f95010f66f4d353ac15402a4c314607f LA.UM.5.3.1_rb1
05.31.2016 LA.UM.5.3-03710-89xx.0 msm-3.18 e4bd98b39aee92bd6f838c4c14189de51a16a258 LA.UM.5.3_rb1.1
05.24.2016 LA.UM.5.3.1-00310-89xx.0 msm-3.18 289277d0980d8075c20244d8aa8cfde3b4b57737 LA.UM.5.3.1_rb1
05.15.2016 LA.UM.5.1-04010-8x37.0 msm-3.18 67ea3027ee587c3cddc0c51024257816c0972312 LA.UM.5.1_rb1.4
04.29.2016 LA.UM.5.1-03810-8x37.0 msm-3.18 a9e54d65f9005af4075c24063ad2558260254dc5 LA.UM.5.1_rb1.4
04.14.2016 LA.UM.5.1-03610-8x37.0 msm-3.18 5b0c3e43afaa6639f6d41a6379e713382b220c5e LA.UM.5.1_rb1.4
03.30.2016 LA.UM.5.1-03210-8x37.0 msm-3.18 5f11194935c418e32e5308ae397227afc5797fed LA.UM.5.1_rb1.4
03.22.2016 LA.UM.5.3-01410-8x37.0 msm-3.18 261ac07c6a00d352d42fe412595beaa70d55c7ab LA.UM.5.3_rb1.1
03.15.2016 LA.UM.5.1-02910-8x37.0 msm-3.18 38a946316417e48534169a0e8174286f52d78685 LA.UM.5.1_rb1.4
02.28.2016 LA.UM.5.1-02410-8x37.0 msm-3.18 7d15cd5c720f21b63f269539edbec896d7e233f6 LA.UM.5.1_rb1.4
02.25.2016 LA.UM.5.3-01110-8x37.0 msm-3.18 985da67f18431ac30e2c2d46b68067b71ebf8688 LA.UM.5.3_rb1.1
02.12.2016 LA.UM.5.1-02110-8x37.0 msm-3.18 488a89d43651383c957f75a628534a7ad5d7eea0 LA.UM.5.1_rb1.4
02.12.2016 LA.UM.5.3-00610-8x37.0 msm-3.18 eef5da9a9bbc138fc7ee42f804b957a7758f8a78 LA.UM.5.3_rb1.1
01.29.2016 LA.UM.5.1-01910-8x37.0 msm-3.18 fb35f3c795229950ddf63280800b2390eafcb135 LA.UM.5.1_rb1.4
01.21.2016 LA.UM.5.1-01610-8x37.0 msm-3.18 1aa11b594d7ac1dfab73a86119998b4c4e80b506 LA.UM.5.1_rb1.4
01.11.2016 LA.UM.5.1-01310-8x37.0 msm-3.18 39d6e2eee46004ada9e72eb273b028986651d6dc LA.UM.5.1_rb1.4
12.21.2015 LA.UM.5.1-03700-8x37.0 msm-3.18 4e90549c8f8d5feb88e92c24dde4f15e1f94a616 rel/msm-3.18
12.04.2015 LA.UM.5.1-01400-8x37.0 msm-3.18 e70ad0cd5efdd9dc91a77dcdac31d6132e1315c1 rel/msm-3.18
11.21.2015 LA.UM.5.1-01010-8x37.0 msm-3.18 122fe9b172bd14c1c5dffa45fc4389da0c187461 LA.UM.5.1_rb1.3
Click to expand...
Click to collapse
* redmi 3 kernel:
https://github.com/MiCode/Xiaomi_Kernel_OpenSource branch ido-l-oss
STATUS REPORT:
Tested with my kernel #5d5fa78 + stock ROM MIUI V7.5.9.0. Stable enough.
boot: OK
panel: OK
vol+ vol- power key: OK
touchscreen: OK
eMMC: OK
mic: OK
phone: OK
external speaker: OK
sensors: OK
vibrator: OK
cameras: could be OK (QR code scan work, but can't get a photo)
fingerprint: need more work
wifi: OK
dial: OK
PREBUILT KERNEL:
https://github.com/yangyangnau/android_kernel_xiaomi_msm8937/releases/download/v0.9-beta/kernel
https://github.com/yangyangnau/android_kernel_xiaomi_msm8937/releases/download/v0.9-beta/wlan.ko
touchscreen firmware issue:
Perhaps we can just ignore this issue. The touchscreen works fine.
dmesg from my kernel #39aa441. striped non opensorce bin form lib*.a files from the redmi 3 ft5x06 driver.
Code:
[ 0.969584] input: ft5x06_720p as /devices/soc/78b7000.i2c/i2c-3/3-003e/input/input1
[ 1.210325] i2c-msm-v2 78b7000.i2c: msm_bus_scale_register_client(mstr-id:86):0xd (ok)
[ 1.210825] ft5x06_720p 3-003e: Device ID = 0x14
[ 1.211455] ft5x06_720p 3-003e: report rate = 90Hz
[ 1.213175] ft5x06_720p 3-003e: Firmware version = 8.0.0
[ 1.213624] FT5X06-TP-TAG INFO:boardid_info_tp:S88537AA1:bo
[ 1.213624]
[ 1.670057] ft5x06_720p 3-003e: Lockdown info: 34 35 32 31 00 A9 00 00
[ 1.731395] FT5X06-TP-TAG ERROR:Error Board ID.
[ 1.732698] FT5X06-TP-TAG ERROR:Error Board ID.
[ 1.733998] FT5X06-TP-TAG ERROR:Error Board ID.
[ 1.734068] [ TSP ] ist30xx_init()
dmesg from stock kernel MIUI V7.9.5.0.
Code:
[ 0.970901] input: ft5x06_720p as /devices/soc/78b7000.i2c/i2c-3/3-003e/input/input1
[ 1.210327] i2c-msm-v2 78b7000.i2c: msm_bus_scale_register_client(mstr-id:86):0xd (ok)
[ 1.210827] ft5x06_720p 3-003e: Device ID = 0x14
[ 1.211459] ft5x06_720p 3-003e: report rate = 90Hz
[ 1.213186] ft5x06_720p 3-003e: Firmware version = 8.0.0
[ 1.670059] ft5x06_720p 3-003e: Lockdown info: 34 35 32 31 00 A9 00 00
[ 1.670127] ft5x06_720p 3-003e: has no androidboot.mode
[ 1.670136] ft5x06_720p 3-003e: upgrade
[ 1.670144] FT5X06-TP-TAG DEBUG:[3148]********************Enter CTP Auto Upgrade********************
[ 1.670144]
[ 1.731401] FT5X06-TP-TAG DEBUG:[1342]Vendor ID:0xF3, TP FW:0x08, IC TYPE:20
[ 1.731409] FT5X06-TP-TAG DEBUG:[1370]OUFEI+BOE
[ 1.731417] FT5X06-TP-TAG DEBUG:[1396]update firmware size:28883
[ 1.731425] FT5X06-TP-TAG DEBUG:[1416][FTS] uc_tp_fm_ver = 8.
[ 1.731425]
[ 1.731433] FT5X06-TP-TAG DEBUG:[1417][FTS] uc_host_fm_ver = 8.
[ 1.731433]
[ 1.731516] [ TSP ] ist30xx_init()
[ 1.731912] [ TSP ] ### IMAGIS probe(ver:2.3.0.0, protocol:B, addr:0x50) ###
[ 1.732238] IST30XX 3-0050: irq gpio request failed
[ 1.732262] [ TSP ] Error, ist30xx init driver
FT5X06-TP-TAG DEBUG:[1342]Vendor ID:0xF3, TP FW:0x08, IC TYPE:20
FT5X06-TP-TAG DEBUG:[1370]OUFEI+BOE
FT5X06-TP-TAG DEBUG:[1396]update firmware size:28883
Click to expand...
Click to collapse
external speaker PA BUG: fixed. #5d5fa78
dmesg from my kernel #39aa441.
Code:
[ 3.179313] input: gpio-keys as /devices/soc/soc:gpio_keys/input/input2
[ 3.179650] qcom,qpnp-rtc qpnp-rtc-ffffffc079767000: setting system clock to 1970-01-03 02:20:00 UTC (181200)
[ 3.190542] qcom,qpnp-flash-led qpnp-flash-led-ffffffc079793400: Unable to acquire pinctrl
[ 3.195190] qcom,cc-debug-8952 1874000.qcom,cc-debug: Registered Debug Mux successfully
[ 3.201419] msm8952-asoc-wcd c051000.sound: default codec configured
[ 3.201790] msm8952_populate_dai_link_component_of_node: codec dai msm-stub-codec.1 failed
[ 3.201867] msm8952_populate_dai_link_component_of_node: codec dai msm-stub-codec.1 failed
dmesg from stock kernel (MIUI V7.5.9.0)
Code:
[ 3.277300] input: gpio-keys as /devices/soc/soc:gpio_keys/input/input4
[ 3.277650] qcom,qpnp-rtc qpnp-rtc-ffffffc079776c00: setting system clock to 1970-01-03 02:09:35 UTC (180575)
[ 3.288617] qcom,qpnp-flash-led qpnp-flash-led-ffffffc0797aac00: Unable to acquire pinctrl
[ 3.293341] qcom,cc-debug-8952 1874000.qcom,cc-debug: Registered Debug Mux successfully
[ 3.297473] msm8952_asoc_machine_probe: [hjf] request spk_pa_gpio is 124!
[ 3.297490] msm8952_asoc_machine_probe: [hjf] request headset_gpio is 129!
[ 3.299584] msm8952-asoc-wcd c051000.sound: default codec configured
[ 3.299947] msm8952_populate_dai_link_component_of_node: codec dai msm-stub-codec.1 failed
[ 3.300053] msm8952_populate_dai_link_component_of_node: codec dai msm-stub-codec.1 failed
spk_pa_gpio is 124 = 0x7c
headset_gpio is 129 = 0x7f
Click to expand...
Click to collapse
Just debug info? Or Xiaomi did some nasty work in function msm8952_asoc_machine_probe.
Code:
grep msm8952_asoc_machine_probe sound/ -ir
sound/soc/msm/msm8952-slimbus.c:static int msm8952_asoc_machine_probe(struct platform_device *pdev)
sound/soc/msm/msm8952-slimbus.c: .probe = msm8952_asoc_machine_probe,
sound/soc/msm/msm8952.c:static int msm8952_asoc_machine_probe(struct platform_device *pdev)
sound/soc/msm/msm8952.c: .probe = msm8952_asoc_machine_probe,
Redmi3s main dts file is arch/arm64/boot/dts/qcom/redmi3s-msm8937-38.dts.
Code:
9604 sound {
9605 status = "okay";
9607 qcom,model = "msm8952-sku1-snd-card";
9610 qcom,msm-ext-pa = "primary";
9615 ext-spk-amp-gpio = <0x97 0x7c 0x0>;
9616 headset-gpio = <0x97 0x81 0x0>;
ext-spk-amp-gpio = <0x97 0x7c 0x0>
headset-gpio = <0x97 0x81 0x0>
Click to expand...
Click to collapse
dial BUG: FALSE alarm
Amazing work bro, I'm following the thread to see your progress
I always want to try make custom ROMs (I'm developer but no experience about ROM development) but I don't know where to start xD.
Regards!
Keep up the good work man!!!!
The external speaker PA BUG has fixed. See #5d5fa78.
The fix isn't elegant, but it works.
Hi, why did you choose "LA.UM.5.3-01110-8x37.0" ?
i did the same as you, but i'm getting a Too many open files when I boot CM
If you have any ideas : https://github.com/supercairos/android_kernel_xiaomi_msm8937
Supercairos said:
Hi, why did you choose "LA.UM.5.3-01110-8x37.0" ?
i did the same as you, but i'm getting a Too many open files when I boot CM
If you have any ideas : https://github.com/supercairos/android_kernel_xiaomi_msm8937
Click to expand...
Click to collapse
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/android_device_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.
Please post CM issue at my thread below.
http://forum.xda-developers.com/redmi-3/development/port-cm-13-0-xiaomi-redmi3s-land-t3469996
QAEP for msm8937
Code:
lynx -dump -width 120 https://wiki.codeaurora.org/xwiki/bin/QAEP/release | grep msm8937
June 23, 2016 LA.UM.5.3.1-01010-89xx.0 msm8937_64 LA.UM.5.3.1-01010-89xx.0.xml 06.00.01
June 10, 2016 LA.UM.5.3-04410-89xx.0 msm8937_64 LA.UM.5.3-04410-89xx.0.xml 06.00.01
June 09, 2016 LA.UM.5.3.1-00610-89xx.0 msm8937_64 LA.UM.5.3.1-00610-89xx.0.xml 06.00.01
June 07, 2016 LA.UM.5.1-04210-8x37.0 msm8937_64 LA.UM.5.1-04210-8x37.0.xml 06.00.01
June 06, 2016 LA.UM.5.3.1-00610-89xx.0 msm8937_64 LA.UM.5.3.1-00610-89xx.0.xml 06.00.01
May 31, 2016 LA.UM.5.3-03710-89xx.0 msm8937_64 LA.UM.5.3-03710-89xx.0.xml 06.00.01
May 24, 2016 LA.UM.5.3.1-00310-89xx.0 msm8937_64 LA.UM.5.3.1-00310-89xx.0.xml 06.00.01
May 15, 2016 LA.UM.5.1-04010-8x37.0 msm8937_64 LA.UM.5.1-04010-8x37.0.xml 06.00.01
April 29, 2016 LA.UM.5.1-03810-8x37.0 msm8937_64 LA.UM.5.1-03810-8x37.0.xml 06.00.01
April 14, 2016 LA.UM.5.1-03610-8x37.0 msm8937_64 LA.UM.5.1-03610-8x37.0.xml 06.00.01
March 30, 2016 LA.UM.5.1-03210-8x37.0 msm8937_32 LA.UM.5.1-03210-8x37.0.xml 06.00.01
March 22, 2016 LA.UM.5.3-01410-8x37.0 msm8937_64 LA.UM.5.3-01410-8x37.0.xml 06.00.01
March 15, 2016 LA.UM.5.1-02910-8x37.0 msm8937_64 LA.UM.5.1-02910-8x37.0.xml 06.00.01
February 28, 2016 LA.UM.5.1-02410-8x37.0 msm8937_64 LA.UM.5.1-02410-8x37.0.xml 06.00.01
February 25, 2016 LA.UM.5.3-01110-8x37.0 msm8937_64 LA.UM.5.3-01110-8x37.0.xml 06.00.01
February 12, 2016 LA.UM.5.1-02110-8x37.0 msm8937_64 LA.UM.5.1-02110-8x37.0.xml 06.00.01
February 12, 2016 LA.UM.5.3-00610-8x37.0 msm8937_64 LA.UM.5.3-00610-8x37.0.xml 06.00.01
January 29, 2016 LA.UM.5.1-01910-8x37.0 msm8937_64 LA.UM.5.1-01910-8x37.0.xml 06.00.01
January 21, 2016 LA.UM.5.1-01610-8x37.0 msm8937_64 LA.UM.5.1-01610-8x37.0.xml 06.00.01
January 11, 2016 LA.UM.5.1-01310-8x37.0 msm8937_64 LA.UM.5.1-01310-8x37.0.xml 06.00.01
December 21, 2015 LA.UM.5.1-03700-8x37.0 msm8937_64 LA.UM.5.1-03700-8x37.0.xml 06.00.00
December 04, 2015 LA.UM.5.1-01400-8x37.0 msm8937_64 LA.UM.5.1-01400-8x37.0.xml 06.00.00
November 21, 2015 LA.UM.5.1-01010-8x37.0 msm8937_64 LA.UM.5.1-01010-8x37.0.xml 06.00.00
Click to expand...
Click to collapse
fingerprint:
stock kernel
Code:
ls -l /dev/goodix_fp /dev/input/event5
crw-r--r-- system system 225, 0 /dev/goodix_fp
crw-rw---- root input 13, 69 /dev/input/event5
The above dev nodes are missing with my kernel #5d5fa78.
Code:
cat /sys/devices/soc/soc:fpc1020/uevent
OF_NAME=fpc1020
OF_FULLNAME=/soc/fpc1020
OF_COMPATIBLE_0=soc:fpc1020
OF_COMPATIBLE_N=1
MODALIAS=of:Nfpc1020T<NULL>Csoc:fpc1020
Code:
cat /sys/devices/soc/soc:goodix_fp/uevent
OF_NAME=goodix_fp
OF_FULLNAME=/soc/goodix_fp
OF_COMPATIBLE_0=goodix,fingerprint
OF_COMPATIBLE_N=1
MODALIAS=of:Ngoodix_fpT<NULL>Cgoodix,fingerprint
fingerprint:
logcat from CM-13 with my kernel #5d5fa78.
01-12 02:44:46.021 456 456 E QSEECOMAPI: Error::Cannot open the file /system/etc/firmware/goodixfp.mdt errno = 2
01-12 02:44:46.021 456 456 E QSEECOMAPI: Error::Loading image failed with ret = -1
Click to expand...
Click to collapse
Code:
ls -l /firmware/image/goodixfp*
-r--r--r-- 1 root root 276 2016-08-16 21:18 /firmware/image/goodixfp.b00
-r--r--r-- 1 root root 6664 2016-08-16 21:18 /firmware/image/goodixfp.b01
-r--r--r-- 1 root root 397050 2016-08-16 21:18 /firmware/image/goodixfp.b02
-r--r--r-- 1 root root 397604 2016-08-16 21:18 /firmware/image/goodixfp.b03
-r--r--r-- 1 root root 392 2016-08-16 21:18 /firmware/image/goodixfp.b04
-r--r--r-- 1 root root 88 2016-08-16 21:18 /firmware/image/goodixfp.b05
-r--r--r-- 1 root root 832 2016-08-16 21:18 /firmware/image/goodixfp.b06
-r--r--r-- 1 root root 6940 2016-08-16 21:18 /firmware/image/goodixfp.mdt
Wow you're so far, and fast. I'm ultra impressed, thank you so much
Keep up the good work dev
You seem to be the only hope as Xiaomi is too lazy to release kernel sources.
Hopefully someone can build CyanogenMod 14 unofficial based on this kernel...
Edit: So I heard the dev is working on a cm13 bootable... If this is true, please work on cm14 as well! Thank you for your work.
Good work Dev !!!
Ptmaroct said:
Keep up the good work dev
You seem to be the only hope as Xiaomi is too lazy to release kernel sources.
Click to expand...
Click to collapse
Not lazy, rather caught up on releasing phones... Redmi 3S Plus, Mi 5s, Mi 5c... I just wish they'd stop and focus on the main thing here.
Speaking of which, almost everyone in India is buying a Lenovo lol... If I had the chance I'd kill all these weirdo Chinese companies because of their stupid skins...
I just wanted to say, that your work is very very impressive and we can be very thankful for guys like you, who make things possible on their own!!!
THANKS
My GF and I staying tuned...
So any updates?
ZelectroKarZ said:
So any updates?
Click to expand...
Click to collapse
Chill brother, here at XDA this is not very welcome.
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
Hi there,
a few days ago I posted my flavor of Pixel Experience 12 Plus and immediately got feedback that I should do something about the camera not working.
So, that's what I'm now trying to do. After bricking my phone several times and setting up my whole development system on a new PC, I now have a stable phone again and am able to continue.
I have added more proprietary files that were missing according to logcat.
Code:
lib/[email protected]
lib64/[email protected]
system_ext/lib/[email protected]
system_ext/lib64/[email protected]
Now I'm stuck here:
Code:
09-25 07:15:24.951 10496 10774 E AndroidRuntime: FATAL EXCEPTION: CameraAccess
09-25 07:15:24.951 10496 10774 E AndroidRuntime: Process: com.sonyericsson.android.camera, PID: 10496
09-25 07:15:24.951 10496 10774 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "_ZNK7android6Parcel10readIntPtrEv" referenced by "/system/lib64/libcacao_client.so"...
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at java.lang.Runtime.loadLibrary0(Runtime.java:1077)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at java.lang.Runtime.loadLibrary0(Runtime.java:998)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at java.lang.System.loadLibrary(System.java:1656)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at com.sonymobile.imageprocessor.bypasscamera2.BypassCamera.loadNativeLibrary(BypassCamera.java:214)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at com.sonyericsson.android.camera.device.CameraDeviceHandler$LoadNativeLibraryTask.doCameraDeviceAccess(CameraDeviceHandler.java:744)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at com.sonyericsson.android.camera.device.CameraDeviceHandler$CameraDeviceAccessTask.run(CameraDeviceHandler.java:4017)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:938)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:201)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.Looper.loop(Looper.java:288)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:67)
As far as I know, _ZNK7android6Parcel10readIntPtrEv is part of libbinder.so that belongs to the NDK and really should be part of the ROM.
Maybe someone has a clue how to continue?
I read on here not too long ago that the stock camera app broke since Android 12 because of a storage permission, I think? The only ROM I know of that has the stock camera app is Lineage 18.1 by @Sjll, but I don't think that ROM is AOSP based.
I think a few of the experts here like, @Miustone, @Sjll, @bobbyamarthaa, @elmaleek03, (sorry for the tags guys) might be able to help.
The moment you (or anyone else) get that stock camera app working I am gonna install your ROM straight away, it's the only thing keeping me on the Stock ROM.
Please continue the great work!
grisu59964 said:
Hi there,
a few days ago I posted my flavor of Pixel Experience 12 Plus and immediately got feedback that I should do something about the camera not working.
So, that's what I'm now trying to do. After bricking my phone several times and setting up my whole development system on a new PC, I now have a stable phone again and am able to continue.
I have added more proprietary files that were missing according to logcat.
Code:
lib/[email protected]
lib64/[email protected]
system_ext/lib/[email protected]
system_ext/lib64/[email protected]
Now I'm stuck here:
Code:
09-25 07:15:24.951 10496 10774 E AndroidRuntime: FATAL EXCEPTION: CameraAccess
09-25 07:15:24.951 10496 10774 E AndroidRuntime: Process: com.sonyericsson.android.camera, PID: 10496
09-25 07:15:24.951 10496 10774 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "_ZNK7android6Parcel10readIntPtrEv" referenced by "/system/lib64/libcacao_client.so"...
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at java.lang.Runtime.loadLibrary0(Runtime.java:1077)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at java.lang.Runtime.loadLibrary0(Runtime.java:998)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at java.lang.System.loadLibrary(System.java:1656)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at com.sonymobile.imageprocessor.bypasscamera2.BypassCamera.loadNativeLibrary(BypassCamera.java:214)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at com.sonyericsson.android.camera.device.CameraDeviceHandler$LoadNativeLibraryTask.doCameraDeviceAccess(CameraDeviceHandler.java:744)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at com.sonyericsson.android.camera.device.CameraDeviceHandler$CameraDeviceAccessTask.run(CameraDeviceHandler.java:4017)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:938)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:201)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.Looper.loop(Looper.java:288)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:67)
As far as I know, _ZNK7android6Parcel10readIntPtrEv is part of libbinder.so that belongs to the NDK and really should be part of the ROM.
Maybe someone has a clue how to continue?
Click to expand...
Click to collapse
do using sony-msmnile tree?
i think u need to rebuild the tree's, cz msm-nile tree have many errors.
try to get contact with other dev here.
taken
You can view and join @Xperia007 right away.
t.me
grisu59964 said:
Hi there,
a few days ago I posted my flavor of Pixel Experience 12 Plus and immediately got feedback that I should do something about the camera not working.
So, that's what I'm now trying to do. After bricking my phone several times and setting up my whole development system on a new PC, I now have a stable phone again and am able to continue.
I have added more proprietary files that were missing according to logcat.
Code:
lib/[email protected]
lib64/[email protected]
system_ext/lib/[email protected]
system_ext/lib64/[email protected]
Now I'm stuck here:
Code:
09-25 07:15:24.951 10496 10774 E AndroidRuntime: FATAL EXCEPTION: CameraAccess
09-25 07:15:24.951 10496 10774 E AndroidRuntime: Process: com.sonyericsson.android.camera, PID: 10496
09-25 07:15:24.951 10496 10774 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "_ZNK7android6Parcel10readIntPtrEv" referenced by "/system/lib64/libcacao_client.so"...
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at java.lang.Runtime.loadLibrary0(Runtime.java:1077)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at java.lang.Runtime.loadLibrary0(Runtime.java:998)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at java.lang.System.loadLibrary(System.java:1656)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at com.sonymobile.imageprocessor.bypasscamera2.BypassCamera.loadNativeLibrary(BypassCamera.java:214)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at com.sonyericsson.android.camera.device.CameraDeviceHandler$LoadNativeLibraryTask.doCameraDeviceAccess(CameraDeviceHandler.java:744)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at com.sonyericsson.android.camera.device.CameraDeviceHandler$CameraDeviceAccessTask.run(CameraDeviceHandler.java:4017)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:938)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:201)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.Looper.loop(Looper.java:288)
09-25 07:15:24.951 10496 10774 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:67)
As far as I know, _ZNK7android6Parcel10readIntPtrEv is part of libbinder.so that belongs to the NDK and really should be part of the ROM.
Maybe someone has a clue how to continue?
Click to expand...
Click to collapse
Arent You the Guy from Android-Hilfe.de? I'm glad someone works on My old Xperia 5... Arent You willed to join Me with DIOS so we can work together on such Things? I have some other People around who can surely help with the Camera...
BrandonMCMFG said:
I read on here not too long ago that the stock camera app broke since Android 12 because of a storage permission, I think? The only ROM I know of that has the stock camera app is Lineage 18.1 by @Sjll, but I don't think that ROM is AOSP based.
I think a few of the experts here like, @Miustone, @Sjll, @bobbyamarthaa, @elmaleek03, (sorry for the tags guys) might be able to help.
The moment you (or anyone else) get that stock camera app working I am gonna install your ROM straight away, it's the only thing keeping me on the Stock ROM.
Please continue the great work!
Click to expand...
Click to collapse
Thanks for tagging Me, glad to see some Life over here!
bobbyamarthaa said:
do using sony-msmnile tree?
i think u need to rebuild the tree's, cz msm-nile tree have many errors.
try to get contact with other dev here.
taken
You can view and join @Xperia007 right away.
t.me
Click to expand...
Click to collapse
Trees are availble on many Places. I would suggest using the SODP Trees since everything works over there except for Mobile Data...
Miustone said:
Arent You the Guy from Android-Hilfe.de? I'm glad someone works on My old Xperia 5... Arent You willed to join Me with DIOS so we can work together on such Things? I have some other People around who can surely help with the Camera...
Thanks for tagging Me, glad to see some Life over here!
Trees are availble on many Places. I would suggest using the SODP Trees since everything works over there except for Mobile Data...
Click to expand...
Click to collapse
SODP need to much modified to work perfectly.
and it removes all xperia exclusive features.
Thank you everyone for your replies! I've been active in background, working on the problem.
So far, I have created a shim for _ZNK7android6Parcel10readIntPtrEv and modified the references of libcacao_client to use libbinder.so and libhidlbase.so. Now the stock camera app starts, but it still won't work. It takes a few seconds before the message "Unknown error" appears on the screen.
No more exceptions in log, but I saw this:
Code:
10-03 12:25:42.968 14151 14194 I CameraApp: [PlatformCapability] shared-preferences is not valid: name = com.sonyericsson.android.camera.supported_values.platform
10-03 12:25:42.971 1691 4803 W ServiceManager: Permission failure: android.permission.HIGH_SAMPLING_RATE_SENSORS from uid=10064 pid=14151
10-03 12:25:42.977 14151 14194 I CameraManagerGlobal: Connecting to camera service
10-03 12:25:42.979 1336 1936 W ServiceManager: Permission failure: android.permission.CAMERA_OPEN_CLOSE_LISTENER from uid=10064 pid=14151
10-03 12:25:42.999 14151 14220 W SharedPreferencesImpl: Cannot read /data/user/0/com.sonyericsson.android.camera/shared_prefs/com.sonyericsson.android.camera.supported_values.4.xml
10-03 12:25:42.999 14151 14220 W SharedPreferencesImpl: org.xmlpull.v1.XmlPullParserException: Unexpected end of document
10-03 12:25:42.999 14151 14220 W SharedPreferencesImpl: at com.android.internal.util.XmlUtils.readValueXml(XmlUtils.java:1548)
10-03 12:25:42.999 14151 14220 W SharedPreferencesImpl: at com.android.internal.util.XmlUtils.readMapXml(XmlUtils.java:969)
10-03 12:25:42.999 14151 14220 W SharedPreferencesImpl: at android.app.SharedPreferencesImpl.loadFromDisk(SharedPreferencesImpl.java:171)
10-03 12:25:42.999 14151 14220 W SharedPreferencesImpl: at android.app.SharedPreferencesImpl.access$000(SharedPreferencesImpl.java:59)
10-03 12:25:42.999 14151 14220 W SharedPreferencesImpl: at android.app.SharedPreferencesImpl$1.run(SharedPreferencesImpl.java:140)
10-03 12:25:43.000 14151 14194 I CameraApp: [PlatformCapability] shared-preferences is not valid: name = com.sonyericsson.android.camera.supported_values.4
10-03 12:25:43.003 636 636 E SELinux : avc: denied { find } for pid=14151 uid=10064 name=cacao scontext=u:r:platform_app:s0:c512,c768 tcontext=u:object_r:default_android_service:s0 tclass=service_manager permissive=0
10-03 12:25:43.003 14151 14194 I ServiceManager: Waiting for service 'cacao' on '/dev/binder'...
Is it possible that the cacao service is not running or cannot be found because of missing SELinux permissions?
I already set SELinux to permissive, but the only change was permissive=1 in the log.
bobbyamarthaa said:
do using sony-msmnile tree?
i think u need to rebuild the tree's, cz msm-nile tree have many errors.
try to get contact with other dev here.
taken
You can view and join @Xperia007 right away.
t.me
Click to expand...
Click to collapse
I'm now using a mixture of elmaleek03s device tree and some additional changes for the stock camera app. The advise to head over to Telegram was already helpful as I got the hint with the shim there.
Miustone said:
Arent You the Guy from Android-Hilfe.de? I'm glad someone works on My old Xperia 5... Arent You willed to join Me with DIOS so we can work together on such Things? I have some other People around who can surely help with the Camera...
Click to expand...
Click to collapse
I was active on android-hilfe.de, yes, but maybe I'm better known for my work back in the days on SE-world. I also dropped you a PM.
Currently, I'm using my Xperia 5 as my daily driver (keeping my old buddy alive) so I try not to ruin everything all the time. But I'm really curious what you are doing with DIOS.
grisu59964 said:
Thank you everyone for your replies! I've been active in background, working on the problem.
So far, I have created a shim for _ZNK7android6Parcel10readIntPtrEv and modified the references of libcacao_client to use libbinder.so and libhidlbase.so. Now the stock camera app starts, but it still won't work. It takes a few seconds before the message "Unknown error" appears on the screen.
No more exceptions in log, but I saw this:
Code:
10-03 12:25:42.968 14151 14194 I CameraApp: [PlatformCapability] shared-preferences is not valid: name = com.sonyericsson.android.camera.supported_values.platform
10-03 12:25:42.971 1691 4803 W ServiceManager: Permission failure: android.permission.HIGH_SAMPLING_RATE_SENSORS from uid=10064 pid=14151
10-03 12:25:42.977 14151 14194 I CameraManagerGlobal: Connecting to camera service
10-03 12:25:42.979 1336 1936 W ServiceManager: Permission failure: android.permission.CAMERA_OPEN_CLOSE_LISTENER from uid=10064 pid=14151
10-03 12:25:42.999 14151 14220 W SharedPreferencesImpl: Cannot read /data/user/0/com.sonyericsson.android.camera/shared_prefs/com.sonyericsson.android.camera.supported_values.4.xml
10-03 12:25:42.999 14151 14220 W SharedPreferencesImpl: org.xmlpull.v1.XmlPullParserException: Unexpected end of document
10-03 12:25:42.999 14151 14220 W SharedPreferencesImpl: at com.android.internal.util.XmlUtils.readValueXml(XmlUtils.java:1548)
10-03 12:25:42.999 14151 14220 W SharedPreferencesImpl: at com.android.internal.util.XmlUtils.readMapXml(XmlUtils.java:969)
10-03 12:25:42.999 14151 14220 W SharedPreferencesImpl: at android.app.SharedPreferencesImpl.loadFromDisk(SharedPreferencesImpl.java:171)
10-03 12:25:42.999 14151 14220 W SharedPreferencesImpl: at android.app.SharedPreferencesImpl.access$000(SharedPreferencesImpl.java:59)
10-03 12:25:42.999 14151 14220 W SharedPreferencesImpl: at android.app.SharedPreferencesImpl$1.run(SharedPreferencesImpl.java:140)
10-03 12:25:43.000 14151 14194 I CameraApp: [PlatformCapability] shared-preferences is not valid: name = com.sonyericsson.android.camera.supported_values.4
10-03 12:25:43.003 636 636 E SELinux : avc: denied { find } for pid=14151 uid=10064 name=cacao scontext=u:r:platform_app:s0:c512,c768 tcontext=u:object_r:default_android_service:s0 tclass=service_manager permissive=0
10-03 12:25:43.003 14151 14194 I ServiceManager: Waiting for service 'cacao' on '/dev/binder'...
Is it possible that the cacao service is not running or cannot be found because of missing SELinux permissions?
I already set SELinux to permissive, but the only change was permissive=1 in the log.
I'm now using a mixture of elmaleek03s device tree and some additional changes for the stock camera app. The advise to head over to Telegram was already helpful as I got the hint with the shim there.
I was active on android-hilfe.de, yes, but maybe I'm better known for my work back in the days on SE-world. I also dropped you a PM.
Currently, I'm using my Xperia 5 as my daily driver (keeping my old buddy alive) so I try not to ruin everything all the time. But I'm really curious what you are doing with DIOS.
Click to expand...
Click to collapse
glad to see someone popping out here. sadly im no longer using bahamut since months ago, i hope this issue can be fixed in a near. ive already tried ask Sjll, but he gave no clue except including all the related camera files in the build process. thats why his builds has a dedicated stock cam ROM ZIPS.
elmaleek03 said:
glad to see someone popping out here. sadly im no longer using bahamut since months ago, i hope this issue can be fixed in a near. ive already tried ask Sjll, but he gave no clue except including all the related camera files in the build process. thats why his builds has a dedicated stock cam ROM ZIPS.
Click to expand...
Click to collapse
om, coba intip ini.
GitHub - moghn1/android_device_sony_j9110: This is the error tree
This is the error tree. Contribute to moghn1/android_device_sony_j9110 development by creating an account on GitHub.
github.com
maybe u can use this as refference grisu59964
he is the same person who has built a custom rom for xperia 1 on coolapk forum
There were changes done by @elmaleek03 on setup-makefiles.sh that look like the camera APK gets elevated rights. Do I need to call setup-makefiles.sh manually during build? Can anybody help me fully understand what is going on in this commit?
added missing proprietary files and fix camera crash · sony-msmnile/[email protected]
:)
github.com
As far as my research goes now, the camera app needs to be executed in the system_app domain rather than platform_app and I would like to change that.
Alright, I found the answer to my last question myself. setup-makefiles.sh is called by extract-files.sh. And the code from the commit is written to vendor/sony/bahamut/Android.mk for anyone curious.
I'm currently starting /system/bin/cacaoserver via adb shell to get a message why the service crashes.
I have no idea why there is nothing to see in the log during boot. But at least now there is the first progress since days. Stay tuned!
Current state: cacaoserver is now able to start. I went through a lot of missing files and then segfaults. Unfortunately, the cacaoserver does somehow not survive the boot phase and is not running any more when the camera app starts. When I start the binary manually, it stays alive.
If SELinux is not enforcing, the camera app will start, connect to the cacaoserver and then crash:
Code:
10-09 10:24:50.660 860 860 D Zygote : Forked child process 12098
10-09 10:24:50.660 1639 1743 I ActivityManager: Start proc 12098:com.sonyericsson.android.camera/u0a64 for pre-top-activity {com.sonyericsson.android.camera/com.sonyericsson.android.camera.CameraActivity}
10-09 10:24:50.691 12098 12098 E .android.camer: Not starting debugger since process cannot load the jdwp agent.
10-09 10:24:50.694 12098 12098 D ProcessState: Binder ioctl to enable oneway spam detection failed: Invalid argument
10-09 10:24:50.702 12098 12098 D CompatibilityChangeReporter: Compat change id reported: 171979766; UID 10064; state: DISABLED
10-09 10:24:50.712 12098 12098 W .android.camer: ClassLoaderContext shared library size mismatch. Expected=0, found=1 (PCL[] | PCL[]{PCL[/product/framework/com.sonymobile.camera.addon_impl.jar*1938205956]})
10-09 10:24:50.719 12098 12098 V GraphicsEnvironment: ANGLE Developer option for 'com.sonyericsson.android.camera' set to: 'default'
10-09 10:24:50.720 12098 12098 V GraphicsEnvironment: ANGLE GameManagerService for com.sonyericsson.android.camera: false
10-09 10:24:50.720 12098 12098 D NetworkSecurityConfig: No Network Security Config specified, using platform default
10-09 10:24:50.721 12098 12098 D NetworkSecurityConfig: No Network Security Config specified, using platform default
10-09 10:24:50.801 12098 12119 I CameraManagerGlobal: Connecting to camera service
10-09 10:24:50.816 630 630 E SELinux : avc: denied { find } for pid=12098 uid=10064 name=cacao scontext=u:r:platform_app:s0:c512,c768 tcontext=u:object_r:default_android_service:s0 tclass=service_manager permissive=1
10-09 10:24:50.866 1318 27514 W ServiceManager: Permission failure: android.permission.SYSTEM_CAMERA from uid=10064 pid=12098
10-09 10:24:50.885 12067 12070 D CacaoService: client create - pid:12098
10-09 10:24:50.885 12067 12070 I cacao : 2079724329205 pal.cpp (2611) 12070 I [INF] PAL_Create
10-09 10:24:50.888 12098 12122 E .android.camer: BypassCameraBurst_changeToPhotoMode: stop cacao ret=-111
10-09 10:24:50.888 12098 12122 D .android.camer: [Debug] BypassCameraBurst_changeToPhotoMode: burstNum=4
10-09 10:24:50.890 12098 12122 E AndroidRuntime: FATAL EXCEPTION: CameraAccess
10-09 10:24:50.890 12098 12122 E AndroidRuntime: Process: com.sonyericsson.android.camera, PID: 12098
10-09 10:24:50.890 12098 12122 E AndroidRuntime: android.app.BackgroundServiceStartNotAllowedException: Not allowed to start service Intent { act=com.sonymobile.cameracommon.action.CAMERA_STATUS_UPDATE pkg=com.sonymobile.cameracommon (has extras) }: app is in background uid null
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1870)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.app.ContextImpl.startService(ContextImpl.java:1826)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.content.ContextWrapper.startService(ContextWrapper.java:776)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at com.sonyericsson.cameracommon.status.CameraStatusPublisher.publish(CameraStatusPublisher.java:96)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at com.sonyericsson.cameracommon.status.CameraStatusPublisher.publish(CameraStatusPublisher.java:86)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at com.sonyericsson.android.camera.device.BypassCameraController$OpenBypassCameraTask.doCameraDeviceAccess(BypassCameraController.java:1166)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at com.sonyericsson.android.camera.device.CameraDeviceHandler$CameraDeviceAccessTask.run(CameraDeviceHandler.java:4017)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:938)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:201)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.os.Looper.loop(Looper.java:288)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:67)
10-09 10:24:50.892 12098 12149 E CameraApp: [PlatformCapability] CameraInfo cannot be retrieved. Because PlatformCapability is not prepared.
10-09 10:24:50.894 12098 12149 E CameraApp: [PlatformCapability] CameraInfo cannot be retrieved. Because PlatformCapability is not prepared.
10-09 10:24:50.896 12098 12149 E CameraApp: [PlatformCapability] CameraInfo cannot be retrieved. Because PlatformCapability is not prepared.
10-09 10:24:50.900 1639 12166 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
10-09 10:24:50.900 12098 12098 I DynamicAreaFilter: .init sSmoothFactor=0.9 screenSize.x=1080 screenSize.y=2520 mScreenHeight=2520 mLimitScale=71 mDynamicFilterType=2 mValidScreenHeightMin=252 mValidScreenHeightMax=1789
10-09 10:24:50.900 12098 12149 E CameraApp: [PlatformCapability] CameraInfo cannot be retrieved. Because PlatformCapability is not prepared.
10-09 10:24:50.902 1639 4547 W ActivityTaskManager: Force finishing activity com.sonyericsson.android.camera/.CameraActivity
10-09 10:24:50.911 12098 12098 D SYMPHONY: Detected Symphony running as an Android application, using logcat for all debugging output
10-09 10:24:50.911 12098 12098 I SYMPHONY: [36mA t794df074f8 /local/mnt/workspace/pcgbait/docker.ci.tmp/build/aarch64-android-clang6.0/SecondParty/symphony/src/symphony/src/lib/internal/soc/topology.c:674 Could not resolve a cluster for cpu 7. The cluster may be offline. Power request will be ignored.[0m
10-09 10:24:50.920 12098 12122 I Process : Sending signal. PID: 12098 SIG: 9
10-09 10:24:50.920 1639 1742 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
10-09 10:24:50.920 1639 1742 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
10-09 10:24:50.921 1639 1742 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
10-09 10:24:50.921 1639 1742 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
10-09 10:24:50.944 957 2454 D [email protected]_lock: Release wakelock is released
10-09 10:24:50.973 12067 12067 D CacaoService: client delete - pid:12098
10-09 10:24:50.974 1639 1944 I ActivityManager: Process com.sonyericsson.android.camera (pid 12098) has died: fg TOP
10-09 10:24:50.974 1639 1746 I libprocessgroup: Successfully killed process cgroup uid 10064 pid 12098 in 0ms
The short life of the camera app process. 255 ms. Any hint solving those problems will massively improve my development speed, so please get in touch if you have a clue.
That is a very short life for a Camera App...
Rest in Piece Camera App - Lived for 255ms with SELinux set to permissive.
In all seriousness though, I really appreciate these updates please keep them coming.
grisu59964 said:
Current state: cacaoserver is now able to start. I went through a lot of missing files and then segfaults. Unfortunately, the cacaoserver does somehow not survive the boot phase and is not running any more when the camera app starts. When I start the binary manually, it stays alive.
If SELinux is not enforcing, the camera app will start, connect to the cacaoserver and then crash:
Code:
10-09 10:24:50.660 860 860 D Zygote : Forked child process 12098
10-09 10:24:50.660 1639 1743 I ActivityManager: Start proc 12098:com.sonyericsson.android.camera/u0a64 for pre-top-activity {com.sonyericsson.android.camera/com.sonyericsson.android.camera.CameraActivity}
10-09 10:24:50.691 12098 12098 E .android.camer: Not starting debugger since process cannot load the jdwp agent.
10-09 10:24:50.694 12098 12098 D ProcessState: Binder ioctl to enable oneway spam detection failed: Invalid argument
10-09 10:24:50.702 12098 12098 D CompatibilityChangeReporter: Compat change id reported: 171979766; UID 10064; state: DISABLED
10-09 10:24:50.712 12098 12098 W .android.camer: ClassLoaderContext shared library size mismatch. Expected=0, found=1 (PCL[] | PCL[]{PCL[/product/framework/com.sonymobile.camera.addon_impl.jar*1938205956]})
10-09 10:24:50.719 12098 12098 V GraphicsEnvironment: ANGLE Developer option for 'com.sonyericsson.android.camera' set to: 'default'
10-09 10:24:50.720 12098 12098 V GraphicsEnvironment: ANGLE GameManagerService for com.sonyericsson.android.camera: false
10-09 10:24:50.720 12098 12098 D NetworkSecurityConfig: No Network Security Config specified, using platform default
10-09 10:24:50.721 12098 12098 D NetworkSecurityConfig: No Network Security Config specified, using platform default
10-09 10:24:50.801 12098 12119 I CameraManagerGlobal: Connecting to camera service
10-09 10:24:50.816 630 630 E SELinux : avc: denied { find } for pid=12098 uid=10064 name=cacao scontext=u:r:platform_app:s0:c512,c768 tcontext=u:object_r:default_android_service:s0 tclass=service_manager permissive=1
10-09 10:24:50.866 1318 27514 W ServiceManager: Permission failure: android.permission.SYSTEM_CAMERA from uid=10064 pid=12098
10-09 10:24:50.885 12067 12070 D CacaoService: client create - pid:12098
10-09 10:24:50.885 12067 12070 I cacao : 2079724329205 pal.cpp (2611) 12070 I [INF] PAL_Create
10-09 10:24:50.888 12098 12122 E .android.camer: BypassCameraBurst_changeToPhotoMode: stop cacao ret=-111
10-09 10:24:50.888 12098 12122 D .android.camer: [Debug] BypassCameraBurst_changeToPhotoMode: burstNum=4
10-09 10:24:50.890 12098 12122 E AndroidRuntime: FATAL EXCEPTION: CameraAccess
10-09 10:24:50.890 12098 12122 E AndroidRuntime: Process: com.sonyericsson.android.camera, PID: 12098
10-09 10:24:50.890 12098 12122 E AndroidRuntime: android.app.BackgroundServiceStartNotAllowedException: Not allowed to start service Intent { act=com.sonymobile.cameracommon.action.CAMERA_STATUS_UPDATE pkg=com.sonymobile.cameracommon (has extras) }: app is in background uid null
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1870)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.app.ContextImpl.startService(ContextImpl.java:1826)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.content.ContextWrapper.startService(ContextWrapper.java:776)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at com.sonyericsson.cameracommon.status.CameraStatusPublisher.publish(CameraStatusPublisher.java:96)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at com.sonyericsson.cameracommon.status.CameraStatusPublisher.publish(CameraStatusPublisher.java:86)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at com.sonyericsson.android.camera.device.BypassCameraController$OpenBypassCameraTask.doCameraDeviceAccess(BypassCameraController.java:1166)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at com.sonyericsson.android.camera.device.CameraDeviceHandler$CameraDeviceAccessTask.run(CameraDeviceHandler.java:4017)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.os.Handler.handleCallback(Handler.java:938)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:99)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.os.Looper.loopOnce(Looper.java:201)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.os.Looper.loop(Looper.java:288)
10-09 10:24:50.890 12098 12122 E AndroidRuntime: at android.os.HandlerThread.run(HandlerThread.java:67)
10-09 10:24:50.892 12098 12149 E CameraApp: [PlatformCapability] CameraInfo cannot be retrieved. Because PlatformCapability is not prepared.
10-09 10:24:50.894 12098 12149 E CameraApp: [PlatformCapability] CameraInfo cannot be retrieved. Because PlatformCapability is not prepared.
10-09 10:24:50.896 12098 12149 E CameraApp: [PlatformCapability] CameraInfo cannot be retrieved. Because PlatformCapability is not prepared.
10-09 10:24:50.900 1639 12166 I DropBoxManagerService: add tag=system_app_crash isTagEnabled=true flags=0x2
10-09 10:24:50.900 12098 12098 I DynamicAreaFilter: .init sSmoothFactor=0.9 screenSize.x=1080 screenSize.y=2520 mScreenHeight=2520 mLimitScale=71 mDynamicFilterType=2 mValidScreenHeightMin=252 mValidScreenHeightMax=1789
10-09 10:24:50.900 12098 12149 E CameraApp: [PlatformCapability] CameraInfo cannot be retrieved. Because PlatformCapability is not prepared.
10-09 10:24:50.902 1639 4547 W ActivityTaskManager: Force finishing activity com.sonyericsson.android.camera/.CameraActivity
10-09 10:24:50.911 12098 12098 D SYMPHONY: Detected Symphony running as an Android application, using logcat for all debugging output
10-09 10:24:50.911 12098 12098 I SYMPHONY: [36mA t794df074f8 /local/mnt/workspace/pcgbait/docker.ci.tmp/build/aarch64-android-clang6.0/SecondParty/symphony/src/symphony/src/lib/internal/soc/topology.c:674 Could not resolve a cluster for cpu 7. The cluster may be offline. Power request will be ignored.[0m
10-09 10:24:50.920 12098 12122 I Process : Sending signal. PID: 12098 SIG: 9
10-09 10:24:50.920 1639 1742 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
10-09 10:24:50.920 1639 1742 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
10-09 10:24:50.921 1639 1742 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.stats.service.DropBoxEntryAddedReceiver
10-09 10:24:50.921 1639 1742 W BroadcastQueue: Background execution not allowed: receiving Intent { act=android.intent.action.DROPBOX_ENTRY_ADDED flg=0x10 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
10-09 10:24:50.944 957 2454 D [email protected]_lock: Release wakelock is released
10-09 10:24:50.973 12067 12067 D CacaoService: client delete - pid:12098
10-09 10:24:50.974 1639 1944 I ActivityManager: Process com.sonyericsson.android.camera (pid 12098) has died: fg TOP
10-09 10:24:50.974 1639 1746 I libprocessgroup: Successfully killed process cgroup uid 10064 pid 12098 in 0ms
The short life of the camera app process. 255 ms. Any hint solving those problems will massively improve my development speed, so please get in touch if you have a clue.
Click to expand...
Click to collapse
Really good work bro please keep it up with your work
Nice to see some one will work on stock camera for android 12 xperia 5
Best of luck for next progress
Short status update: It has been a rough few weeks for me in real life so I did not have so much time playing around and ruining my phone. I tried to make the Xperia 5 II stock camera app work, but that one freezes as soon as you capture something - without leaving a trace in the logs.
I also tried decompiling and modifying the Xperia 5 camera app and adding probably missing things to the manifest, but that did not improve anything.
My device bricked twice and I'm currently running out of ideas.
Maybe something worth thinking about is the fact that the error message from my last logcat
Code:
AndroidRuntime: android.app.BackgroundServiceStartNotAllowedException: Not allowed to start service Intent { act=com.sonymobile.cameracommon.action.CAMERA_STATUS_UPDATE pkg=com.sonymobile.cameracommon (has extras) }: app is in background uid null
belongs to com.sonymobile.cameracommon which maybe also does not start properly.
I'm not giving up yet, but I'm not too optimistic either.
grisu59964 said:
Short status update: It has been a rough few weeks for me in real life so I did not have so much time playing around and ruining my phone. I tried to make the Xperia 5 II stock camera app work, but that one freezes as soon as you capture something - without leaving a trace in the logs.
I also tried decompiling and modifying the Xperia 5 camera app and adding probably missing things to the manifest, but that did not improve anything.
My device bricked twice and I'm currently running out of ideas.
Maybe something worth thinking about is the fact that the error message from my last logcat
Code:
AndroidRuntime: android.app.BackgroundServiceStartNotAllowedException: Not allowed to start service Intent { act=com.sonymobile.cameracommon.action.CAMERA_STATUS_UPDATE pkg=com.sonymobile.cameracommon (has extras) }: app is in background uid null
belongs to com.sonymobile.cameracommon which maybe also does not start properly.
I'm not giving up yet, but I'm not too optimistic either.
Click to expand...
Click to collapse
I think xperia 5ii n xperia 5 have different camera drivers so face freezing during capture any images only slow motion video working in this app
I personally tried it so
Hello @grisu59964
Currently trying the same exercise now.
Could you please provide the shim you created ? I tried to find a github from you but no luck
About the permissions exceptions you are facing, did you try to go in permissive mode ?
Won't solve everything but should help.
nailyk said:
Hello @grisu59964
Currently trying the same exercise now.
Could you please provide the shim you created ? I tried to find a github from you but no luck
About the permissions exceptions you are facing, did you try to go in permissive mode ?
Won't solve everything but should help.
Click to expand...
Click to collapse
You can find my device tree on GitHub. https://github.com/grisumedia/android_device_sony_bahamut
Unfortunately, setting SELinux to permissive did not help either.