Database Info

[nvm, found the issue] Graphics stuttering on my 100% stock unrooted Z3

So I just got a new Z3 D6603. It's running on stock Marshmallow, 23.5.A.0.570. Bootloader was never unlocked, it has never been rooted.
Everything is running fine, except there's a constant screen stutter in literally everything: regular apps, videos, gaming, everywhere.
I've made an app that shows this nicely. I'm attaching the apk. It simply draws a line that should smoothly move across the screen. It does move smoothly on all phones I've tried it on, except my Z3. Here's a video I made that shows this app running on a 1st gen Moto G (left) and the Z3: https://www.youtube.com/watch?v=Wqgr9u_4Sa0&feature=youtu.be. Unfortunately this video adds some stuttering on it's own, but in a few places you can still clearly see the problem, especially near the end of the video.
I've looked into the logs and every time there's a stutter, a bunch of these show up:
Code:
05-01 21:02:07.877 6699 6699 W osmcore : type=1400 audit(0.0:3470533): avc: denied { getattr } for path="/proc/1" dev="proc" ino=935969 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:init:s0 tclass=dir permissive=0 ppid=1 pcomm="init" tgid=1 tgcomm="init"
05-01 21:02:07.877 6699 6699 W osmcore : type=1400 audit(0.0:3470534): avc: denied { getattr } for path="/proc/2" dev="proc" ino=935970 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0 ppid=1 pcomm="init" tgid=1 tgcomm="init"
05-01 21:02:07.877 6699 6699 W osmcore : type=1400 audit(0.0:3470535): avc: denied { getattr } for path="/proc/3" dev="proc" ino=935971 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0 ppid=1 pcomm="init" tgid=1 tgcomm="init"
05-01 21:02:07.877 6699 6699 W osmcore : type=1400 audit(0.0:3470536): avc: denied { getattr } for path="/proc/6" dev="proc" ino=935972 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0 ppid=1 pcomm="init" tgid=1 tgcomm="init"
05-01 21:02:07.877 6699 6699 W osmcore : type=1400 audit(0.0:3470537): avc: denied { getattr } for path="/proc/7" dev="proc" ino=935973 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0 ppid=1 pcomm="init" tgid=1 tgcomm="init"
05-01 21:02:09.987 6699 6699 W osmcore : type=1400 audit(0.0:3470793): avc: denied { getattr } for path="/proc/1" dev="proc" ino=935969 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:init:s0 tclass=dir permissive=0 ppid=1 pcomm="init" tgid=1 tgcomm="init"
05-01 21:02:09.987 6699 6699 W osmcore : type=1400 audit(0.0:3470794): avc: denied { getattr } for path="/proc/2" dev="proc" ino=935970 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0 ppid=1 pcomm="init" tgid=1 tgcomm="init"
05-01 21:02:09.987 6699 6699 W osmcore : type=1400 audit(0.0:3470795): avc: denied { getattr } for path="/proc/3" dev="proc" ino=935971 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0 ppid=1 pcomm="init" tgid=1 tgcomm="init"
05-01 21:02:09.987 6699 6699 W osmcore : type=1400 audit(0.0:3470796): avc: denied { getattr } for path="/proc/6" dev="proc" ino=935972 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0 ppid=1 pcomm="init" tgid=1 tgcomm="init"
05-01 21:02:09.987 6699 6699 W osmcore : type=1400 audit(0.0:3470797): avc: denied { getattr } for path="/proc/7" dev="proc" ino=935973 scontext=u:r:untrusted_app:s0:c512,c768 tcontext=u:r:kernel:s0 tclass=dir permissive=0 ppid=1 pcomm="init" tgid=1 tgcomm="init"
Any help is welcome. Especially, if you have a stock ROM on your Z3, can you please
a) install the attached apk and see if you can spot the stuttering
b) look into the logs and see if you have those messages from osmcore popping up every few seconds?
Thanks in advance.
EDIT: found the problem myself: it was somehow caused by OS Monitor: https://play.google.com/store/apps/details?id=com.eolwral.osmonitor&hl=en. The problem went away after killing this app.

[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

[Q&A][PATCHROM] Stuck in Bootloop [Miui 8]

hi there
i am trying to port miui 8 marchmellow using patchrom project to our device
But after flashing the rom it stuck in mi logo (bootloop)
Code:
W init : type=1400 audit(0.0:22): avc: denied { execute } for name="shelld" dev="mmcblk0p19" ino=90304 scontext=u:r:init:s0 tcontext=u:object_r:unlabeled:s0 tclass=file permissive=0
W init : type=1400 audit(0.0:23): avc: denied { execute } for name="fdpp" dev="mmcblk0p19" ino=40996 scontext=u:r:init:s0 tcontext=u:object_r:unlabeled:s0 tclass=file permissive=0
W init : type=1400 audit(0.0:24): avc: denied { execute } for name="shelld" dev="mmcblk0p19" ino=90304 scontext=u:r:init:s0 tcontext=u:object_r:unlabeled:s0 tclass=file permissive=0
W init : type=1400 audit(0.0:25): avc: denied { execute } for name="fdpp" dev="mmcblk0p19" ino=40996 scontext=u:r:init:s0 tcontext=u:object_r:unlabeled:s0 tclass=file permissive=0
W init : type=1400 audit(0.0:26): avc: denied { execute } for name="shelld" dev="mmcblk0p19" ino=90304 scontext=u:r:init:s0 tcontext=u:object_r:unlabeled:s0 tclass=file permissive=0
W init : type=1400 audit(0.0:27): avc: denied { execute } for name="fdpp" dev="mmcblk0p19" ino=40996 scontext=u:r:init:s0 tcontext=u:object_r:unlabeled:s0 tclass=file permissive=0
W init : type=1400 audit(0.0:28): avc: denied { execute } for name="shelld" dev="mmcblk0p19" ino=90304 scontext=u:r:init:s0 tcontext=u:object_r:unlabeled:s0 tclass=file permissive=0
W init : type=1400 audit(0.0:29): avc: denied { execute } for name="fdpp" dev="mmcblk0p19" ino=40996 scontext=u:r:init:s0 tcontext=u:object_r:unlabeled:s0 tclass=file permissive=0
W init : type=1400 audit(0.0:30): avc: denied { execute } for name="shelld" dev="mmcblk0p19" ino=90304 scontext=u:r:init:s0 tcontext=u:object_r:unlabeled:s0 tclass=file permissive=0
W init : type=1400 audit(0.0:31): avc: denied { execute } for name="fdpp" dev="mmcblk0p19" ino=40996 scontext=u:r:init:s0 tcontext=u:object_r:unlabeled:s0 tclass=file permissive=0
W init : type=1400 audit(0.0:7): avc: denied { execute_no_trans } for path="/system/xbin/su" dev="mmcblk0p19" ino=90310 scontext=u:r:init:s0 tcontext=u:object_r:su_exec:s0 tclass=file permissive=0
W init : type=1400 audit(0.0:8): avc: denied { execute } for name="mcd" dev="mmcblk0p19" ino=41033 scontext=u:r:init:s0 tcontext=u:object_r:unlabeled:s0 tclass=file permissive=0
W init : type=1400 audit(0.0:9): avc: denied { execute } for name="miuioneshots" dev="mmcblk0p19" ino=90292 scontext=u:r:init:s0 tcontext=u:object_r:unlabeled:s0 tclass=file permissive=0

Sadly I can't help you, because I'm not an expert,but can I ask you how is development going? Did you find a solution?

Maybe you need a permissive kernel cos I'm seeing a lot of selinux denials

osas514 said:
Maybe you need a permissive kernel cos I'm seeing a lot of selinux denials
Click to expand...
Click to collapse
it already permissive
i will build another one
thanks for reply

AymenDe7 said:
it already permissive
i will build another one
thanks for reply
Click to expand...
Click to collapse
A proper full log will be necessary here..
Goodluck

Any luck with miui8 for Samsung galaxy s2 plus ?
 @AymenDe7

Any luck?

Ribin Manuel said:
Any luck with miui8 for Samsung galaxy s2 plus ?
@AymenDe7
Click to expand...
Click to collapse
aborted

AymenDe7 said:
aborted
Click to expand...
Click to collapse
Oops

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?

Trying to get the stock camera app to work under AOSP

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.