Database Info

Enable OpenGL ES in Hero

Ok so I was glancing through the logs and noticed the following. I'm assuming I'm not the only person with this issue so has anyone else noticed that opengl was not being initialized? Perhaps this would explain our strong reliance on optimizing Hero to run smoothly as opposed to letting the onboard graphics chip help do the rendering
I/SurfaceFlinger( 77): SurfaceFlinger is starting
I/SurfaceFlinger( 77): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
D/SurfaceFlinger( 77): pid 77 requesting gpu core (owner = -1)
W/SurfaceFlinger( 77): couldn't grant gpu core to pid 77
D/EGL ( 77): requestGPU returned -1
E/GLLogger( 77): h/w accelerated eglGetDisplay() failed (EGL_SUCCESS)
I/SurfaceFlinger( 77): EGL informations:
I/SurfaceFlinger( 77): # of configs : 6
I/SurfaceFlinger( 77): vendor : Android
I/SurfaceFlinger( 77): version : 1.31 Android META-EGL
I/SurfaceFlinger( 77): extensions:
I/SurfaceFlinger( 77): Client API: OpenGL ES
I/EGLDisplaySurface( 77): using (fd=23)
I/EGLDisplaySurface( 77): id = msmfb
I/EGLDisplaySurface( 77): xres = 320 px
I/EGLDisplaySurface( 77): yres = 480 px
I/EGLDisplaySurface( 77): xres_virtual = 320 px
I/EGLDisplaySurface( 77): yres_virtual = 960 px
I/EGLDisplaySurface( 77): bpp = 16
I/EGLDisplaySurface( 77): r = 11:5
I/EGLDisplaySurface( 77): g = 5:6
I/EGLDisplaySurface( 77): b = 0:5
I/EGLDisplaySurface( 77): width = 45 mm (180.622223 dpi)
I/EGLDisplaySurface( 77): height = 67 mm (181.970154 dpi)
I/EGLDisplaySurface( 77): refresh rate = 60.00 Hz

shafty023 said:
Ok so I was glancing through the logs and noticed the following. I'm assuming I'm not the only person with this issue so has anyone else noticed that opengl was not being initialized? Perhaps this would explain our strong reliance on optimizing Hero to run smoothly as opposed to letting the onboard graphics chip help do the rendering
I/SurfaceFlinger( 77): SurfaceFlinger is starting
I/SurfaceFlinger( 77): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
D/SurfaceFlinger( 77): pid 77 requesting gpu core (owner = -1)
W/SurfaceFlinger( 77): couldn't grant gpu core to pid 77
D/EGL ( 77): requestGPU returned -1
E/GLLogger( 77): h/w accelerated eglGetDisplay() failed (EGL_SUCCESS)
I/SurfaceFlinger( 77): EGL informations:
I/SurfaceFlinger( 77): # of configs : 6
I/SurfaceFlinger( 77): vendor : Android
I/SurfaceFlinger( 77): version : 1.31 Android META-EGL
I/SurfaceFlinger( 77): extensions:
I/SurfaceFlinger( 77): Client API: OpenGL ES
I/EGLDisplaySurface( 77): using (fd=23)
I/EGLDisplaySurface( 77): id = msmfb
I/EGLDisplaySurface( 77): xres = 320 px
I/EGLDisplaySurface( 77): yres = 480 px
I/EGLDisplaySurface( 77): xres_virtual = 320 px
I/EGLDisplaySurface( 77): yres_virtual = 960 px
I/EGLDisplaySurface( 77): bpp = 16
I/EGLDisplaySurface( 77): r = 11:5
I/EGLDisplaySurface( 77): g = 5:6
I/EGLDisplaySurface( 77): b = 0:5
I/EGLDisplaySurface( 77): width = 45 mm (180.622223 dpi)
I/EGLDisplaySurface( 77): height = 67 mm (181.970154 dpi)
I/EGLDisplaySurface( 77): refresh rate = 60.00 Hz
Click to expand...
Click to collapse
Very interesting point, I'd really like to see one of the more informed devs look at this. +1

this would definitelly help rosie if its not working already with all the effects in the widgets

RaiderX303 said:
this would definitelly help rosie if its not working already with all the effects in the widgets
Click to expand...
Click to collapse
I think its using software based rendering which means more cpu power to do the effects

shafty023 said:
I think its using software based rendering which means more cpu power to do the effects
Click to expand...
Click to collapse
but if opengl aint working then the cpu is doing all gpu work making the cpu do twice as much

Hmm, couldn't you test this by running an OpenGL or GPU intensive app (Doom?) on the Hero build. See if it differs significantly from the other builds.

KyleK29 said:
Hmm, couldn't you test this by running an OpenGL or GPU intensive app (Doom?) on the Hero build. See if it differs significantly from the other builds.
Click to expand...
Click to collapse
Maybe but you can't benchmark performance by saying "this seems faster" but that makes me wonder what the OGL logs are showing when you launch Doom, for instance.

Where are the logs saved?

Sirus20x6 said:
Where are the logs saved?
Click to expand...
Click to collapse
He's either using log collector or ddms (SDK tool)

uberingram said:
Maybe but you can't benchmark performance by saying "this seems faster" but that makes me wonder what the OGL logs are showing when you launch Doom, for instance.
Click to expand...
Click to collapse
Well, if OpenGL isn't running correctly, I'm sure the difference may just very well be noticeable.
Ever tried to play a game in software mode? Not pretty.

Wow. This could be why it's always been pretty slow. Hmmm, someone should PM JustAnotherCrowd and inform him about this, just in case he doesn't know.

So is I guess the question is, is there an easy way of enabling this.

maydaysos said:
So is I guess the question is, is there an easy way of enabling this.
Click to expand...
Click to collapse
good way of putting it

ccyrowski said:
He's either using log collector or ddms (SDK tool)
Click to expand...
Click to collapse
Ya I was using "adb logcat". So to find the error do this:
1) adb shell reboot
2) adb logcat
It will say waiting for device. Soon as the phone starts booting you'll see logs coming at you like there's no tomorrow. One of which will be that section that shows opengl not loading.

Sirus20x6 said:
Where are the logs saved?
Click to expand...
Click to collapse
The logs are not saved anywhere, they are sent to the console (linux term meaning if you connect to the syslog server you'll see debug messages scrolling like an IRC chatroom). You can view them with "adb logcat" but you'll have to have downloaded the free android 1.5 sdk in order to use that command. Once you download it, it's in the tools/ directory along with a bunch of other useful executables that anybody who wants to hack their phone will need.

ok well is there more to the log? when i look this up in google the explination for the error is just after the 60.00 Hz part
http://osdir.com/ml/android-porting/2009-04/msg00245.html

Sirus20x6 said:
ok well is there more to the log? when i look this up in google the explination for the error is just after the 60.00 Hz part
http://osdir.com/ml/android-porting/2009-04/msg00245.html
Click to expand...
Click to collapse
I have copybit.trout.so loaded so that is not the cause of the problem. Those modules are located at /system/lib/hw/
Here is what I have in my logs starting at the 60Hz part and down a couple lines
Code:
I/EGLDisplaySurface( 77): width = 45 mm (180.622223 dpi)
I/EGLDisplaySurface( 77): height = 67 mm (181.970154 dpi)
I/EGLDisplaySurface( 77): refresh rate = 60.00 Hz
I/SurfaceFlinger( 77): OpenGL informations:
I/SurfaceFlinger( 77): vendor : Android
I/SurfaceFlinger( 77): renderer : Android PixelFlinger 1.0
I/SurfaceFlinger( 77): version : OpenGL ES-CM 1.0
I/SurfaceFlinger( 77): extensions: GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision GL_OES_read_format GL_OES_compressed_paletted_texture GL_OES_draw_texture GL_OES_matrix_get GL_OES_query_matrix GL_ARB_texture_compression GL_ARB_texture_non_power_of_two GL_ANDROID_direct_texture GL_ANDROID_user_clip_plane GL_ANDROID_vertex_buffer_object GL_ANDROID_generate_mipmap
W/HAL ( 77): load: module=/system/lib/hw/overlay.trout.so error=Cannot find library
W/HAL ( 77): load: module=/system/lib/hw/overlay.trout.so error=Cannot find library
W/HAL ( 77): load: module=/system/lib/hw/overlay.msm7k.so error=Cannot find library
W/HAL ( 77): load: module=/system/lib/hw/overlay.default.so error=Cannot find library
I don't believe overlay.*.so was ever compiled for the HTC Hero as it is not in the build. But since HAL is complaining about it AFTER opengl failed I don't think the two are related. Just my guess though

shafty023 said:
I have copybit.trout.so loaded so that is not the cause of the problem. Those modules are located at /system/lib/hw/
Here is what I have in my logs starting at the 60Hz part and down a couple lines
Code:
I/EGLDisplaySurface( 77): width = 45 mm (180.622223 dpi)
I/EGLDisplaySurface( 77): height = 67 mm (181.970154 dpi)
I/EGLDisplaySurface( 77): refresh rate = 60.00 Hz
I/SurfaceFlinger( 77): OpenGL informations:
I/SurfaceFlinger( 77): vendor : Android
I/SurfaceFlinger( 77): renderer : Android PixelFlinger 1.0
I/SurfaceFlinger( 77): version : OpenGL ES-CM 1.0
I/SurfaceFlinger( 77): extensions: GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision GL_OES_read_format GL_OES_compressed_paletted_texture GL_OES_draw_texture GL_OES_matrix_get GL_OES_query_matrix GL_ARB_texture_compression GL_ARB_texture_non_power_of_two GL_ANDROID_direct_texture GL_ANDROID_user_clip_plane GL_ANDROID_vertex_buffer_object GL_ANDROID_generate_mipmap
W/HAL ( 77): load: module=/system/lib/hw/overlay.trout.so error=Cannot find library
W/HAL ( 77): load: module=/system/lib/hw/overlay.trout.so error=Cannot find library
W/HAL ( 77): load: module=/system/lib/hw/overlay.msm7k.so error=Cannot find library
W/HAL ( 77): load: module=/system/lib/hw/overlay.default.so error=Cannot find library
I don't believe overlay.*.so was ever compiled for the HTC Hero as it is not in the build. But since HAL is complaining about it AFTER opengl failed I don't think the two are related. Just my guess though
Click to expand...
Click to collapse
looking through my phone i don't see the overlays at all so i guess they weren't compiled. couldn't a developer take the missing overlays from a build that works and rebuild them to work on hero?

sorry to potentially burst your bubble, but here's my logcat from cyanogenized rogers (which runs ridiculously smooth, said to be comparable to ion):
Code:
I/SurfaceFlinger( 68): SurfaceFlinger is starting
I/SurfaceFlinger( 68): SurfaceFlinger's main thread ready to run. Initializing graphics H/W...
D/SurfaceFlinger( 68): pid 68 requesting gpu core (owner = -1)
W/SurfaceFlinger( 68): couldn't grant gpu core to pid 68
D/EGL ( 68): requestGPU returned -1
E/GLLogger( 68): h/w accelerated eglGetDisplay() failed (EGL_SUCCESS)
I/SurfaceFlinger( 68): EGL informations:
I/SurfaceFlinger( 68): # of configs : 6
I/SurfaceFlinger( 68): vendor : Android
I/SurfaceFlinger( 68): version : 1.31 Android META-EGL
I/SurfaceFlinger( 68): extensions:
I/SurfaceFlinger( 68): Client API: OpenGL ES
I/EGLDisplaySurface( 68): using (fd=24)
I/EGLDisplaySurface( 68): id = msmfb
I/EGLDisplaySurface( 68): xres = 320 px
I/EGLDisplaySurface( 68): yres = 480 px
I/EGLDisplaySurface( 68): xres_virtual = 320 px
I/EGLDisplaySurface( 68): yres_virtual = 960 px
I/EGLDisplaySurface( 68): bpp = 16
I/EGLDisplaySurface( 68): r = 11:5
I/EGLDisplaySurface( 68): g = 5:6
I/EGLDisplaySurface( 68): b = 0:5
I/EGLDisplaySurface( 68): width = 45 mm (180.622223 dpi)
I/EGLDisplaySurface( 68): height = 67 mm (181.970154 dpi)
I/EGLDisplaySurface( 68): refresh rate = 60.00 Hz
W/HAL ( 68): load: module=/system/lib/hw/copybit.trout.so error=Cannot find library
W/HAL ( 68): load: module=/system/lib/hw/copybit.trout.so error=Cannot find library
I/SurfaceFlinger( 68): OpenGL informations:
I/SurfaceFlinger( 68): vendor : Android
I/SurfaceFlinger( 68): renderer : Android PixelFlinger 1.0
I/SurfaceFlinger( 68): version : OpenGL ES-CM 1.0
I/SurfaceFlinger( 68): extensions: GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision GL_OES_read_format GL_OES_compressed_paletted_texture GL_OES_draw_texture GL_OES_matrix_get GL_OES_query_matrix GL_ARB_texture_compression GL_ARB_texture_non_power_of_two GL_ANDROID_direct_texture GL_ANDROID_user_clip_plane GL_ANDROID_vertex_buffer_object GL_ANDROID_generate_mipmap
W/HAL ( 68): load: module=/system/lib/hw/copybit.trout.so error=Cannot find library
W/HAL ( 68): load: module=/system/lib/hw/copybit.trout.so error=Cannot find library
W/HAL ( 68): load: module=/system/lib/hw/overlay.trout.so error=Cannot find library
W/HAL ( 68): load: module=/system/lib/hw/overlay.trout.so error=Cannot find library
W/HAL ( 68): load: module=/system/lib/hw/overlay.msm7k.so error=Cannot find library
W/HAL ( 68): load: module=/system/lib/hw/overlay.default.so error=Cannot find library
I/sysproc ( 68): System server: starting Android runtime.
I/sysproc ( 68): System server: starting Android services.
I/SystemServer( 68): Entered the Android system server!
I/sysproc ( 68): System server: entering thread pool.
I/HtcBootAnimation( 68): mGifPath = /system/media/boot.gif
I/SystemServer( 68): Starting Power Manager.
I/SystemServer( 68): Starting Activity Manager.
I/SystemServer( 68): Starting telephony registry
I/SystemServer( 68): Starting Package Manager.
looks similar to me. even the parts with the copybit and overlay not found.
the interesting part is after the 60hz it does identify OpenGL ES-EM 1.0 along with the extensions available. does it show the same on Hero?

i dont think i can remember the article where i read it, but due to the limitations of portable devices, android does not initialize opengl at the gpu until an app specifically requests it, this is both for gpu and cpu gl rendering. the display elements are all software rendered through a simple frame buffer to conserve battery life, so having opengl on all the time would still yield no advantage, quite the opposite actually, as you'd be draining your battery for nothing.

ROM Allwinner a13

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

Ussd codes

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.

[PORT] CM-13.0 for Xiaomi Redmi 3S (land) with my porting kernel

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

Android 9+ for S7 with camera and fingerprint working properly

I've tested already many S7 (herolte) ROMs and couldn't find any that would have both working properly: camera and fingerprint.
For camera: all of the AOSP based ROMs stop working after about 20 minutes of video chat (sometimes even earlier). Then you have to reboot telephone to make camera working again. I have tried PixelExperience, LineageOS 17-19 and others I don't really remember names now. You can try it yourself by starting WhatsApp or Messenger video chat and waiting bout 20 minutes.
Quite irritating is the fact, that they never mention this issue in ROM summary page, you can only test it yourself or sometimes find reports from ROM users comments, that there's this issue, and it seems quite old and known issue.
For fingerprint: all the stock kernel based ROMs support for fingerprint functionality is partial. Some applications will work with it, but some will crash or just refuse to work like Keepass2Android. Sad thing to say is, that great ROMs like for example FloydQ and Lightheart have no issue with camera but they do with fingerprint.
For this one at least I've found some explanation by @ananjaser1211 why it's not compatible with the stock kernel:
"The 3rd party fingerprint bug is not related to safetynet. It's an incompatibility between the oreo auth tz server we use and the pie+ fingerprint hidl. We can't use the lineage fingerprint hidl. I've tried but it's not compatible with oneui. And we need such custom hidls in order to have working fp"
It seems that it's impossible at the moment to have both fixed. I believe it's a kernel-related thing.
Or maybe someone has found a ROM or a way to make both working correctly?

I think fingerprint was resolved in recent lineage builds, as they found a way to make a compatible hidl that resolves the mismatch we faced, however i had no luck implementing it in my ROM, AOSP components dont really love oneui much.
regarding the camera not working, this is due to a patch made in the camera HAL to bypass FDSAN issues, it does bypass the issue, but after a while of usage it will have issues with FD's and stop working (either not loading entirely or showing a green screen)
we faced this issue in FloydQ v4 or V5 i do not recall when i implemented that patch, however due to it being unstable i resorted to a different method of disabling FDSAN in the ROM itself, rather than fixing it in the camera driver, which is a hack, not really something lineage peeps are interested in.
in lineage this is done in source by setting FDSAN error level to "ANDROID_FDSAN_ERROR_LEVEL_DISABLED"
in OneUI Q it is done by setting "debug.fdsan=0" in prop, which samsung left exposed, however it is not the case for lineage and it needs to be done in the source

I've tested most of the available Android 9+ custom ROMs for S7 (herolte) just to be sure no one made one that would have fixed both camera and fingerprint. Here is my result:
ROMs with camera issue (camera stops working after 20 minutes of uninterrupted usage like in video chat):
PixelExperience 11 and 12 by @expressluke
Lineage 16,18,19 by @Ivan_Meler
DotOS by @expressluke
crDroid by @expressluke
Evolution X by @expressluke
aicp by @expressluke
ROMs with fingerprint issue (fingerprint in some apps like Keepass2Android and some banking apps won't work):
FloydQ by @ananjaser1211
Havoc-OS by @expressluke
ResurrectionRemix by @expressluke
LightRom by @yash92duster
Lightheart by @Skulldron
MKUltraBlack by @MKUltraBlack
NfeSuperleggera by @arcatarc
So to have both working correctly there is only one option: Stock / Android 8- ROMs.
Thank you @ananjaser1211 for the explanation. So the temporary fix for Lineage (and I guess other AOSP ones too) seems quite easy. I'll give it a try as it seems easier than fixing the fingerprint issue.
For me personally faulty video/camera makes ROM unusable in these days when video chats are so common. I can live without fingerprint in some apps, it is definitely less irritating than very unreliable camera. But it is of course a personal preference in the end.

ananjaser1211 said:
in lineage this is done in source by setting FDSAN error level to "ANDROID_FDSAN_ERROR_LEVEL_DISABLED"
Click to expand...
Click to collapse
I've tried disabling FDSAN on PixelExperience. It made camera work longer (like 30 minutes instead of 20 minutes) but still camera crashes after that. Here are logs that appear when camera crashes:
Code:
01-16 10:24:06.278 13467 14324 E SnapCam_CaptureModule: onError 1 4
01-16 10:24:06.280 13467 14324 D CompatibilityChangeReporter: Compat change id reported: 147798919; UID 10187; state: DISABLED
01-16 10:24:06.291 3682 13614 I chatty : uid=1047(cameraserver) HwBinder:3682_3 expire 5 lines
01-16 10:24:06.295 3621 14862 I chatty : uid=1047(cameraserver) [email protected] expire 22 lines
01-16 10:24:06.365 3608 3785 I nanohub : mergeDirectReportRequest - enable = 0 activate = 1 direct.rate = 0 normal.rate = 66667000
01-16 10:24:06.366 3608 3785 I nanohub : mergeDirectReportRequest - activate = 1 normal.rate = 66667000
01-16 10:24:06.366 3608 3785 I Sensors : batch(0) - accelerometer_sensor try to batching with 66667000
01-16 10:24:06.375 3682 3740 I chatty : uid=1047(cameraserver) HwBinder:3682_2 expire 7 lines
01-16 10:24:06.387 13467 13467 W System.err: android.hardware.camera2.CameraAccessException: CAMERA_ERROR (3): The camera device has encountered a serious error
01-16 10:24:06.388 13467 13467 W System.err: at android.hardware.camera2.impl.CameraDeviceImpl.checkIfCameraClosedOrInError(CameraDeviceImpl.java:2267)
01-16 10:24:06.388 13467 13467 W System.err: at android.hardware.camera2.impl.CameraDeviceImpl.submitCaptureRequest(CameraDeviceImpl.java:1161)
01-16 10:24:06.388 13467 13467 W System.err: at android.hardware.camera2.impl.CameraDeviceImpl.setRepeatingRequest(CameraDeviceImpl.java:1234)
01-16 10:24:06.388 13467 13467 W System.err: at android.hardware.camera2.impl.CameraCaptureSessionImpl.setRepeatingRequest(CameraCaptureSessionImpl.java:327)
01-16 10:24:06.388 13467 13467 W System.err: at com.android.camera.CaptureModule.setAFModeToPreview(CaptureModule.java:2287)
01-16 10:24:06.388 13467 13467 W System.err: at com.android.camera.CaptureModule.cancelTouchFocus(CaptureModule.java:8107)
01-16 10:24:06.388 13467 13467 W System.err: at com.android.camera.CaptureModule.cancelTouchFocus(CaptureModule.java:4366)
01-16 10:24:06.388 13467 13467 W System.err: at com.android.camera.CaptureModule.onPauseBeforeSuper(CaptureModule.java:4249)
01-16 10:24:06.388 13467 13467 W System.err: at com.android.camera.CameraActivity.onPause(CameraActivity.java:1784)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.Activity.performPause(Activity.java:8168)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.Instrumentation.callActivityOnPause(Instrumentation.java:1516)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.ActivityThread.performPauseActivityIfNeeded(ActivityThread.java:4733)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.ActivityThread.performPauseActivity(ActivityThread.java:4694)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.ActivityThread.handlePauseActivity(ActivityThread.java:4645)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.servertransaction.PauseActivityItem.execute(PauseActivityItem.java:46)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2066)
01-16 10:24:06.388 13467 13467 W System.err: at android.os.Handler.dispatchMessage(Handler.java:106)
01-16 10:24:06.388 13467 13467 W System.err: at android.os.Looper.loop(Looper.java:223)
01-16 10:24:06.389 13467 13467 W System.err: at android.app.ActivityThread.main(ActivityThread.java:7664)
01-16 10:24:06.389 13467 13467 W System.err: at java.lang.reflect.Method.invoke(Native Method)
01-16 10:24:06.389 13467 13467 W System.err: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
01-16 10:24:06.389 13467 13467 W System.err: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
01-16 10:24:06.390 3797 3839 W LocalDisplayAdapter: Unable to find color mode 0, ignoring request.
01-16 10:24:06.391 13467 13467 D SnapCam_CaptureModule: onPause exit camera
01-16 10:24:06.392 3797 4390 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.395 3797 8295 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.398 3797 8295 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.399 3797 3907 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.400 3797 8295 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.401 3797 4390 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.402 3797 8733 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.406 3797 4390 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.409 3797 4390 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.410 13467 13467 D SnapCam_CaptureModule: closeCamera
Maybe it's also matter of camera software. @ananjaser1211 Do you know if it's possible to use stock camera on AOSP based ROMS and if it is, how much effort might that take?

Makowal said:
I've tried disabling FDSAN on PixelExperience. It made camera work longer (like 30 minutes instead of 20 minutes) but still camera crashes after that. Here are logs that appear when camera crashes:
Code:
01-16 10:24:06.278 13467 14324 E SnapCam_CaptureModule: onError 1 4
01-16 10:24:06.280 13467 14324 D CompatibilityChangeReporter: Compat change id reported: 147798919; UID 10187; state: DISABLED
01-16 10:24:06.291 3682 13614 I chatty : uid=1047(cameraserver) HwBinder:3682_3 expire 5 lines
01-16 10:24:06.295 3621 14862 I chatty : uid=1047(cameraserver) [email protected] expire 22 lines
01-16 10:24:06.365 3608 3785 I nanohub : mergeDirectReportRequest - enable = 0 activate = 1 direct.rate = 0 normal.rate = 66667000
01-16 10:24:06.366 3608 3785 I nanohub : mergeDirectReportRequest - activate = 1 normal.rate = 66667000
01-16 10:24:06.366 3608 3785 I Sensors : batch(0) - accelerometer_sensor try to batching with 66667000
01-16 10:24:06.375 3682 3740 I chatty : uid=1047(cameraserver) HwBinder:3682_2 expire 7 lines
01-16 10:24:06.387 13467 13467 W System.err: android.hardware.camera2.CameraAccessException: CAMERA_ERROR (3): The camera device has encountered a serious error
01-16 10:24:06.388 13467 13467 W System.err: at android.hardware.camera2.impl.CameraDeviceImpl.checkIfCameraClosedOrInError(CameraDeviceImpl.java:2267)
01-16 10:24:06.388 13467 13467 W System.err: at android.hardware.camera2.impl.CameraDeviceImpl.submitCaptureRequest(CameraDeviceImpl.java:1161)
01-16 10:24:06.388 13467 13467 W System.err: at android.hardware.camera2.impl.CameraDeviceImpl.setRepeatingRequest(CameraDeviceImpl.java:1234)
01-16 10:24:06.388 13467 13467 W System.err: at android.hardware.camera2.impl.CameraCaptureSessionImpl.setRepeatingRequest(CameraCaptureSessionImpl.java:327)
01-16 10:24:06.388 13467 13467 W System.err: at com.android.camera.CaptureModule.setAFModeToPreview(CaptureModule.java:2287)
01-16 10:24:06.388 13467 13467 W System.err: at com.android.camera.CaptureModule.cancelTouchFocus(CaptureModule.java:8107)
01-16 10:24:06.388 13467 13467 W System.err: at com.android.camera.CaptureModule.cancelTouchFocus(CaptureModule.java:4366)
01-16 10:24:06.388 13467 13467 W System.err: at com.android.camera.CaptureModule.onPauseBeforeSuper(CaptureModule.java:4249)
01-16 10:24:06.388 13467 13467 W System.err: at com.android.camera.CameraActivity.onPause(CameraActivity.java:1784)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.Activity.performPause(Activity.java:8168)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.Instrumentation.callActivityOnPause(Instrumentation.java:1516)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.ActivityThread.performPauseActivityIfNeeded(ActivityThread.java:4733)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.ActivityThread.performPauseActivity(ActivityThread.java:4694)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.ActivityThread.handlePauseActivity(ActivityThread.java:4645)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.servertransaction.PauseActivityItem.execute(PauseActivityItem.java:46)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:176)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
01-16 10:24:06.388 13467 13467 W System.err: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2066)
01-16 10:24:06.388 13467 13467 W System.err: at android.os.Handler.dispatchMessage(Handler.java:106)
01-16 10:24:06.388 13467 13467 W System.err: at android.os.Looper.loop(Looper.java:223)
01-16 10:24:06.389 13467 13467 W System.err: at android.app.ActivityThread.main(ActivityThread.java:7664)
01-16 10:24:06.389 13467 13467 W System.err: at java.lang.reflect.Method.invoke(Native Method)
01-16 10:24:06.389 13467 13467 W System.err: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:592)
01-16 10:24:06.389 13467 13467 W System.err: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:947)
01-16 10:24:06.390 3797 3839 W LocalDisplayAdapter: Unable to find color mode 0, ignoring request.
01-16 10:24:06.391 13467 13467 D SnapCam_CaptureModule: onPause exit camera
01-16 10:24:06.392 3797 4390 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.395 3797 8295 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.398 3797 8295 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.399 3797 3907 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.400 3797 8295 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.401 3797 4390 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.402 3797 8733 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.406 3797 4390 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.409 3797 4390 W BackupManagerService: [UserID:0] dataChanged but no participant pkg='org.lineageos.snap' uid=10187
01-16 10:24:06.410 13467 13467 D SnapCam_CaptureModule: closeCamera
Maybe it's also matter of camera software. @ananjaser1211 Do you know if it's possible to use stock camera on AOSP based ROMS and if it is, how much effort might that take?
Click to expand...
Click to collapse
Regarding the error, this is a bit generic, the actual hal crash would be in data/tombstones probably, you have disabled fdsan, but did you revert the libexynoscamera "fdsan" patches, i.e the hacks that causes the green issue in the first place. since you disabled fdsan in the rom, you dont need these patches, you should check them in the vendor tree of the rom you are compiling, (generally speaking, using unmodified Note 7 fe libexynoscamera should be fine), after that, test the camera further and keep an eye on HAL crashes (not app crashes) , in theory there should be none. since as far as i know fdsan is the only fatal error on our hal
on the topic of using stock camera on AOSP, no it is not doable, samsung camera (and apps in general) have deep SEM/SEP hooks everywhere , in frameworks / helpers / libs, without having oneui source i dont see how someone can do it without losing half their hair.

Thank you so much @ananjaser1211 for the information. In this situation I'm seriously considering trying my best with your FloydQ compliation for herolte to help fixing fingerprint issue. Personally the cameras used in AOSP are not only faulty but also slow, and herolte is already old so I'm afraid there will be only less effort in future to do anything special for this device.
About the fingerprint I know you have already done some research in the matter. In FloydQ do you think that fixing existing fingerprint software would be easier or rather porting the one from AOSP? Do you have any hints for me where to start?

Makowal said:
Thank you so much @ananjaser1211 for the information. In this situation I'm seriously considering trying my best with your FloydQ compliation for herolte to help fixing fingerprint issue. Personally the cameras used in AOSP are not only faulty but also slow, and herolte is already old so I'm afraid there will be only less effort in future to do anything special for this device.
About the fingerprint I know you have already done some research in the matter. In FloydQ do you think that fixing existing fingerprint software would be easier or rather porting the one from AOSP? Do you have any hints for me where to start?
Click to expand...
Click to collapse
I did not dive into the fingerprint issue on floyd significantly (from testing fixes perspective) so there might be ways to fix it outside the hidl, but to summarize,
we use hero mcDriverDaemon / libmcregistry / libmcclient and vendor/app/mcRegistry,
these are only designed to work properly with OREO libbauth/libauth server (the blobs responsible for fingerprint), however, we dont use oreo bauth, we use the ones from pie (gracerlte) because the oreo ones does not load properly with pie and higher fingerprint HAL, in our case it is `[email protected]`
To test some fixes, i would first start by replacing the hidl used in floyd with latest compiled one from AOSP (making sure it is being compiled with android Q dependencies) and debug why it does not exec, because it "should" work, as this is more or less a generic hidl
once the hal executes, i put back oreo libbauth/libauth servers and try my luck.
i am working on V7 of that rom, so i might give the FP another shot, maybe i missed something when i tackled it last time.

@ananjaser1211 I've tried again with an official PixelExperience ROM and this time I did exactly as you said. I'm happy to say that it worked! I've tested it for over an hour. I finally have a ROM with both working Camera and Fingerprint
I suspect that the reason lays in this commit from git log:
Git:
commit 77e12d12a0c9659aed776332c0f1511c54d2b906
Date: Thu Aug 6 09:32:35 2020 +0200
universal8890: pin hexedited libexynoscamera3
* some fd close in loop causes android Q fdsan go mad
* binary patching them as nop fixes the issue
Change-Id: I56f409fde5902b5340291bb5d454a619cdd7d0a0
What I think happens here is after the binary was hexedited it doesn't close fds, so after some time there are too many open and the app crashes (even if fdsan is disabled).
Of course it is some workaround because fdsan is disabled now but well, good enough for me

Makowal said:
@ananjaser1211 I've tried again with an official PixelExperience ROM and this time I did exactly as you said. I'm happy to say that it worked! I've tested it for over an hour. I finally have a ROM with both working Camera and Fingerprint
I suspect that the reason lays in this commit from git log:
Git:
commit 77e12d12a0c9659aed776332c0f1511c54d2b906
Date: Thu Aug 6 09:32:35 2020 +0200
universal8890: pin hexedited libexynoscamera3
* some fd close in loop causes android Q fdsan go mad
* binary patching them as nop fixes the issue
Change-Id: I56f409fde5902b5340291bb5d454a619cdd7d0a0
What I think happens here is after the binary was hexedited it doesn't close fds, so after some time there are too many open and the app crashes (even if fdsan is disabled).
Of course it is some workaround because fdsan is disabled now but well, good enough for me
Click to expand...
Click to collapse
Fantastic to hear! and yes indeed the patch used to prevent fdsan from breaking camera also allows for FDs to say open i believe and after a while the camera breaks, Glad the workaround is working for you

Recently I started using this newly updated ROM of @Exodusnick . It is a Lineage 16.0 (Android 9) and has both camera and fingerprint working without issues so it meets my criteria (as in this topic title). Unfortunately higher Android versions of the same microG compilation do have camera crash issue after 20m usage, but Pie is ok and works for me.
Personally I'd definitely prefer some Android 9 with OneUI. I don't care about newest Android versions, just the ROM to be daily-usable (stable). Android 9 is required by one of my must-have applications this is the only reason why I put it as a minimum version. Unfortunately I don't think any Android 9 OneUI ROM for S7 exists with working fingerprint. @ananjaser1211 did your compilations of Android 9 had this fingerprint issue?