[ROM][Unofficial][11.0][microG][signed]hardened LineageOS 18.1 Oneplus 3/3T

Search This thread

davidlyerly

Member
Nov 5, 2021
16
11
Hello MSe. I haven't rooted my 7T, yet, may never. The 3T is showing her age and I had to go back to using it because of the new laws here in the stupid US saying only 4G phones are allowed now. I threw my essentially brand new sonim 5700 in the trash.

Every single dumb phone similar to the sonim 5700 has gps ,except for a single device or 2 I found from AGM. The M6 (fully rugged like the sonim) has no wifi or gps and sells for $70 right here in the US. A new pixel 4a is ~$350 and ships out of HK. I saved both $ and time and will get hopefully exactly what I want. A device that isn't my gps navigator. Still rockin your rom until the 3T gives up and maybe I'll root the 7T. Who knows? I finally get to leave the 3T in my car but this new law about no more gsm phones is retarded. If they ever go 5G only I simply won't own one.

BTW, espeak has a newer version on fdroid but you missed it.
 
Hello MSe. I haven't rooted my 7T, yet, may never. The 3T is showing her age and I had to go back to using it because of the new laws here in the stupid US saying only 4G phones are allowed now. I threw my essentially brand new sonim 5700 in the trash.
Oh, is that? Didn't know that - what's the reason for such a legislation? Is that across US or specific to each state?

BTW, espeak has a newer version on fdroid but you missed it.
Thanks for the hint, however - I've built the apk from the new sources, but the phone didn't boot using this new apk. So far I have used the prebuilt apk from the /e/ OS fork - so for now continuing that path...
 

ozrocks

New member
Aug 12, 2022
3
1
OnePlus 3
Hello, and thanks in advance for any solutions here. I am new to custom OS so please bear with me if I get confused. My issue is that on my 3t, I installed the latest build, 18.1 20220805, and I still have no cameras. I didn't on the previus build either. Where the flashlight button is, it is greyed out, and says "camera in use" below it. I have at times, installed gcam from gcam hub, open cam etc, but get zilch as far as a functional camera is concerned . I can post logcat , I used camera as a filter.

<<< log_count = 129 >>>
[08-12 12:25:02.414 23991:23991 E/QCamera]
<MCI><ERROR> mm_camera_open: 291: Failed with Connection timed out error, retrying after 20 milli-seconds

[08-12 12:25:02.437 0:0 I/]
[<ffffffc00088f094>] camera_v4l2_open+0x2c4/0x4d8

[08-12 12:25:02.495 24117:24117 W/CAM_startstats]
type=1400 audit(0.0:3062): avc: denied { search } for name="/" dev="sda2" ino=2 scontext=u:r:mm-qcamerad:s0 tcontext=u:eek:bject_r:persist_file:s0 tclass=dir permissive=0

[08-12 12:25:02.498 24117:24117 W/CAM_startstats]
type=1400 audit(0.0:3063): avc: denied { search } for name="/" dev="sda2" ino=2 scontext=u:r:mm-qcamerad:s0 tcontext=u:eek:bject_r:persist_file:s0 tclass=dir permissive=0

[08-12 12:25:08.440 24117:24163 F/libc]
Fatal signal 6 (SIGABRT), code -6 (SI_TKILL) in tid 24163 (POSIX timer 0), pid 24117 (mm-qcamera-daem)

[08-12 12:25:08.522 24183:24183 F/DEBUG]
pid: 24117, tid: 24163, name: POSIX timer 0 >>> /system/vendor/bin/mm-qcamera-daemon <<<

[08-12 12:25:08.620 24117:24117 E/mm-camera]
<MCT ><ERROR> 645: main: main: camera daemon notify error

[08-12 12:25:08.773 0:0 I/init]
Service 'qcamerasvr' (pid 24117) received signal 6

[08-12 12:25:08.773 0:0 I/init]
Sending signal 9 to service 'qcamerasvr' (pid 24117) process group...

[08-12 12:25:08.777 0:0 I/init]
starting service 'qcamerasvr'...

[08-12 12:25:09.061 24196:24196 E/mm-camera]
<IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_ppeiscore.so error dlopen failed: library "libmmcamera_ppeiscore.so" not found

[08-12 12:25:09.061 24196:24196 E/mm-camera]
<IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_ppeiscore.so

[08-12 12:25:09.069 24196:24196 E/mm-camera]
<IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_llvd.so error dlopen failed: library "libmmcamera_llvd.so" not found

[08-12 12:25:09.069 24196:24196 E/mm-camera]
<IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_llvd.so

[08-12 12:25:09.083 24196:24196 E/mm-camera]
<IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_chromaflash_lib.so error dlopen failed: library "libmmcamera_chromaflash_lib.so" not found

[08-12 12:25:09.083 24196:24196 E/mm-camera]
<IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_chromaflash_lib.so

[08-12 12:25:09.084 24196:24196 E/mm-camera]
<IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_optizoom_lib.so error dlopen failed: library "libmmcamera_optizoom_lib.so" not found

[08-12 12:25:09.084 24196:24196 E/mm-camera]
<IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_optizoom_lib.so

[08-12 12:25:09.085 24196:24196 E/mm-camera]
<IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_ubifocus_lib.so error dlopen failed: library "libmmcamera_ubifocus_lib.so" not found

[08-12 12:25:09.085 24196:24196 E/mm-camera]
<IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_ubifocus_lib.so

[08-12 12:25:09.085 24196:24196 E/mm-camera]
<IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_ubifocus_lib.so error dlopen failed: library "libmmcamera_ubifocus_lib.so" not found

[08-12 12:25:09.085 24196:24196 E/mm-camera]
<IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_ubifocus_lib.so

[08-12 12:25:09.086 24196:24196 E/mm-camera]
<IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_trueportrait_lib.so error dlopen failed: library "libmmcamera_trueportrait_lib.so" not found

[08-12 12:25:09.086 24196:24196 E/mm-camera]
<IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_trueportrait_lib.so

[08-12 12:25:09.086 24196:24196 E/mm-camera]
<IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_stillmore_lib.so error dlopen failed: library "libmmcamera_stillmore_lib.so" not found

[08-12 12:25:09.086 24196:24196 E/mm-camera]
<IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_stillmore_lib.so

[08-12 12:25:09.086 24196:24196 I/mm-camera]
<MCT >< INFO> 135: server_process_module_init: CAMERA_DAEMON: init mods done

[08-12 12:25:12.438 23991:23991 E/QCamera]
<MCI><ERROR> mm_camera_open: 291: Failed with Connection timed out error, retrying after 20 milli-seconds

[08-12 12:25:12.461 0:0 I/]
[<ffffffc00088f094>] camera_v4l2_open+0x2c4/0x4d8

[08-12 12:25:12.495 24196:24196 W/CAM_startstats]
type=1400 audit(0.0:3064): avc: denied { search } for name="/" dev="sda2" ino=2 scontext=u:r:mm-qcamerad:s0 tcontext=u:eek:bject_r:persist_file:s0 tclass=dir permissive=0

[08-12 12:25:12.501 24196:24196 W/CAM_startstats]
type=1400 audit(0.0:3065): avc: denied { search } for name="/" dev="sda2" ino=2 scontext=u:r:mm-qcamerad:s0 tcontext=u:eek:bject_r:persist_file:s0 tclass=dir permissive=0

[08-12 12:25:18.465 24196:24242 F/libc]
Fatal signal 6 (SIGABRT), code -6 (SI_TKILL) in tid 24242 (POSIX timer 0), pid 24196 (mm-qcamera-daem)

[08-12 12:25:18.542 24271:24271 F/DEBUG]
pid: 24196, tid: 24242, name: POSIX timer 0 >>> /system/vendor/bin/mm-qcamera-daemon <<<

[08-12 12:25:18.638 24196:24196 E/mm-camera]
<MCT ><ERROR> 645: main: main: camera daemon notify error

[08-12 12:25:18.776 0:0 I/]
CPU: 2 PID: 24240 Comm: mm-qcamera-daem Tainted: G W 3.18.124-lineageos-gfce013ed1787 #1

[08-12 12:25:18.777 0:0 I/init]
Service 'qcamerasvr' (pid 24196) received signal 6

[08-12 12:25:18.777 0:0 I/init]
Sending signal 9 to service 'qcamerasvr' (pid 24196) process group...

[08-12 12:25:18.797 0:0 I/init]
starting service 'qcamerasvr'...

[08-12 12:25:19.081 24284:24284 E/mm-camera]
<IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_ppeiscore.so error dlopen failed: library "libmmcamera_ppeiscore.so" not found

[08-12 12:25:19.081 24284:24284 E/mm-camera]
<IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_ppeiscore.so

[08-12 12:25:19.089 24284:24284 E/mm-camera]
<IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_llvd.so error dlopen failed: library "libmmcamera_llvd.so" not found

[08-12 12:25:19.089 24284:24284 E/mm-camera]
<IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_llvd.so

[08-12 12:25:19.100 24284:24284 E/mm-camera]
<IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_chromaflash_lib.so error dlopen failed: library "libmmcamera_chromaflash_lib.so" not found

[08-12 12:25:19.100 24284:24284 E/mm-camera]
<IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_chromaflash_lib.so

[08-12 12:25:19.101 24284:24284 E/mm-camera]
<IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_optizoom_lib.so error dlopen failed: library "libmmcamera_optizoom_lib.so" not found

[08-12 12:25:19.101 24284:24284 E/mm-camera]
<IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_optizoom_lib.so

[08-12 12:25:19.102 24284:24284 E/mm-camera]
<IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_ubifocus_lib.so error dlopen failed: library "libmmcamera_ubifocus_lib.so" not found

[08-12 12:25:19.102 24284:24284 E/mm-camera]
<IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_ubifocus_lib.so

[08-12 12:25:19.102 24284:24284 E/mm-camera]
<IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_ubifocus_lib.so error dlopen failed: library "libmmcamera_ubifocus_lib.so" not found

[08-12 12:25:19.102 24284:24284 E/mm-camera]
<IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_ubifocus_lib.so

[08-12 12:25:19.102 24284:24284 E/mm-camera]
<IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_trueportrait_lib.so error dlopen failed: library "libmmcamera_trueportrait_lib.so" not found

[08-12 12:25:19.102 24284:24284 E/mm-camera]
<IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_trueportrait_lib.so

[08-12 12:25:19.103 24284:24284 E/mm-camera]
<IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_stillmore_lib.so error dlopen failed: library "libmmcamera_stillmore_lib.so" not found

[08-12 12:25:19.103 24284:24284 E/mm-camera]
<IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_stillmore_lib.so

[08-12 12:25:19.103 24284:24284 I/mm-camera]
<MCT >< INFO> 135: server_process_module_init: CAMERA_DAEMON: init mods done

[08-12 12:25:22.013 1473:6495 I/ActivityTaskManager]
START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.GoogleCamera/com.android.camera.CameraLauncher bnds=[52,797][178,923]} from uid 10259

[08-12 12:25:22.094 1473:1584 I/ActivityManager]
Start proc 24339:com.google.android.GoogleCamera/u0a251
for pre-top-activity {com.google.android.GoogleCamera/com.android.camera.CameraLauncher}

[08-12 12:25:22.461 23991:23991 E/QCamera]
<MCI><ERROR> mm_camera_open: 291: Failed with Connection timed out error, retrying after 20 milli-seconds

[08-12 12:25:22.481 0:0 I/]
[<ffffffc00088f094>] camera_v4l2_open+0x2c4/0x4d8

[08-12 12:25:22.515 24284:24284 W/CAM_startstats]
type=1400 audit(0.0:3067): avc: denied { search } for name="/" dev="sda2" ino=2 scontext=u:r:mm-qcamerad:s0 tcontext=u:eek:bject_r:persist_file:s0 tclass=dir permissive=0

[08-12 12:25:22.518 24284:24284 W/CAM_startstats]
type=1400 audit(0.0:3068): avc: denied { search } for name="/" dev="sda2" ino=2 scontext=u:r:mm-qcamerad:s0 tcontext=u:eek:bject_r:persist_file:s0 tclass=dir permissive=0

[08-12 12:25:22.629 6064:17558 D/GmsServicesProvider]
query caller=com.google.android.GoogleCamera name=camera:camera.use_perf_logger value=null

[08-12 12:25:22.688 6064:17558 D/GmsServicesProvider]
query caller=com.google.android.GoogleCamera name=camera:camera.debug.trace value=null

[08-12 12:25:22.690 24339:24384 I/CameraManagerGlobal]
Connecting to camera service

[08-12 12:25:22.696 1434:5805 W/ServiceManager]
Permission failure: android.permission.CAMERA_OPEN_CLOSE_LISTENER from uid=10251 pid=24339

[08-12 12:25:22.697 24339:24339 W/CAM_Log]
Tag CameraSearchIndexablesProvider is 11 chars longer than limit.

[08-12 12:25:22.704 24339:24386 W/CamDeviceVerify]
Attempting to reconnect to the camera service with a 7000ms timeout in 200ms increments.

[08-12 12:25:22.710 6064:15920 D/GmsServicesProvider]
query caller=com.google.android.GoogleCamera name=camera:camera.debug.trace value=null

[08-12 12:25:22.851 6064:15920 D/GmsServicesProvider]
query caller=com.google.android.GoogleCamera name=camera:camera.use_perf_logger value=null

[08-12 12:25:22.870 6064:15920 D/GmsServicesProvider]
query caller=com.google.android.GoogleCamera name=camera:smartburst_enabled value=null

[08-12 12:25:22.873 6064:15920 D/GmsServicesProvider]
query caller=com.google.android.GoogleCamera name=camera:hybrid_burst_enabled value=null

[08-12 12:25:22.882 6064:15920 D/GmsServicesProvider]
query caller=com.google.android.GoogleCamera name=camera:lightcycle_enabled value=null

[08-12 12:25:22.894 6064:15920 D/GmsServicesProvider]
query caller=com.google.android.GoogleCamera name=camera:logging_override_level value=null

[08-12 12:25:22.932 24339:24339 I/GCamMod_Instrumentation]
CameraActivity: App OnCreate duration: 3ms

[08-12 12:25:22.932 24339:24339 I/GCamMod_Instrumentation]
CameraActivity: App OnCreate End to Activity OnCreate Start: 37ms

[08-12 12:25:22.967 24339:24339 D/GCamMod_ActivityStartup]
Futures.transform: WaitForCameraDevices

[08-12 12:25:23.019 24339:24339 I/GCamMod_CameraUiInflater]
Initializing Camera Ui

[08-12 12:25:23.209 24339:24339 D/GCamMod_ActivityUiStartup]
Futures.transform: CameraActivityController

[08-12 12:25:23.211 24339:24339 I/GCamMod_Instrumentation]
CameraActivity: OnCreate duration: 279ms

[08-12 12:25:23.217 24339:24339 D/GCamMod_Instrumentation]
CameraActivity: OnStart: @2905919ms

[08-12 12:25:23.219 24339:24339 I/GCamMod_Instrumentation]
CameraActivity: OnCreate End to OnResume Start: 8ms

[08-12 12:25:23.220 24339:24339 I/GCamMod_Instrumentation]
CameraActivity: OnResume duration: 0ms

[08-12 12:25:23.246 6064:15920 D/GmsClearcutSvc]
bound by: GetServiceRequest{serviceId=CLEARCUT_LOGGER, gmsVersion=10298000, packageName='com.google.android.GoogleCamera', extras=Bundle[{}]}

[08-12 12:25:23.270 24339:24339 I/GCamMod_CamBoxHelper]
Computed layout: CameraLayoutBoxes{window=1080x1857, preview=Rect(0, 0 - 0, 0), uncoveredPreview=Rect(0, 189 - 1080, 1440), topBar=Rect(0, 0 - 1080, 116), optionsBar=Rect(0, 0 - 1080, 189), bottomBar=Rect(0, 1440 - 1080, 1857), fullScreen=Rect(0, 0 - 1080, 1857), modeSwitchUi=Rect(0, 1324 - 1080, 1440)}

[08-12 12:25:23.270 24339:24339 D/GCamMod_MainActivityLayout]
Updated layout: CameraLayoutBoxes{window=1080x1857, preview=Rect(0, 0 - 0, 0), uncoveredPreview=Rect(0, 189 - 1080, 1440), topBar=Rect(0, 0 - 1080, 116), optionsBar=Rect(0, 0 - 1080, 189), bottomBar=Rect(0, 1440 - 1080, 1857), fullScreen=Rect(0, 0 - 1080, 1857), modeSwitchUi=Rect(0, 1324 - 1080, 1440)}

[08-12 12:25:23.286 24339:24339 I/GCamMod_CamBoxHelper]
Computed layout: CameraLayoutBoxes{window=1080x1920, preview=Rect(0, 0 - 0, 0), uncoveredPreview=Rect(0, 189 - 1080, 1556), topBar=Rect(0, 0 - 1080, 116), optionsBar=Rect(0, 0 - 1080, 189), bottomBar=Rect(0, 1556 - 1080, 1920), fullScreen=Rect(0, 0 - 1080, 1920), modeSwitchUi=Rect(0, 1440 - 1080, 1556)}

[08-12 12:25:23.287 24339:24339 D/GCamMod_MainActivityLayout]
Updated layout: CameraLayoutBoxes{window=1080x1920, preview=Rect(0, 0 - 0, 0), uncoveredPreview=Rect(0, 189 - 1080, 1556), topBar=Rect(0, 0 - 1080, 116), optionsBar=Rect(0, 0 - 1080, 189), bottomBar=Rect(0, 1556 - 1080, 1920), fullScreen=Rect(0, 0 - 1080, 1920), modeSwitchUi=Rect(0, 1440 - 1080, 1556)}

[08-12 12:25:23.366 1473:1582 I/ActivityTaskManager]
Displayed com.google.android.GoogleCamera/com.android.camera.CameraLauncher: +1s332ms

[08-12 12:25:28.483 24284:24331 F/libc]
Fatal signal 6 (SIGABRT), code -6 (SI_TKILL) in tid 24331 (POSIX timer 0), pid 24284 (mm-qcamera-daem)

[08-12 12:25:28.551 24405:24405 F/DEBUG]
pid: 24284, tid: 24331, name: POSIX timer 0 >>> /system/vendor/bin/mm-qcamera-daemon <<<

[08-12 12:25:28.647 24284:24284 E/mm-camera]
<MCT ><ERROR> 645: main: main: camera daemon notify error

[08-12 12:25:28.757 0:0 I/init]
Service 'qcamerasvr' (pid 24284) received signal 6

[08-12 12:25:28.757 0:0 I/init]
Sending signal 9 to service 'qcamerasvr' (pid 24284) process group...

[08-12 12:25:28.772 0:0 I/init]
starting service 'qcamerasvr'...

[08-12 12:25:29.038 24419:24419 E/mm-camera]
<IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_ppeiscore.so error dlopen failed: library "libmmcamera_ppeiscore.so" not found

[08-12 12:25:29.038 24419:24419 E/mm-camera]
<IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_ppeiscore.so

[08-12 12:25:29.047 24419:24419 E/mm-camera]
<IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_llvd.so error dlopen failed: library "libmmcamera_llvd.so" not found

[08-12 12:25:29.047 24419:24419 E/mm-camera]
<IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_llvd.so

[08-12 12:25:29.061 24419:24419 E/mm-camera]
<IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_chromaflash_lib.so error dlopen failed: library "libmmcamera_chromaflash_lib.so" not found

[08-12 12:25:29.061 24419:24419 E/mm-camera]
<IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_chromaflash_lib.so

[08-12 12:25:29.062 24419:24419 E/mm-camera]
<IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_optizoom_lib.so error dlopen failed: library "libmmcamera_optizoom_lib.so" not found

[08-12 12:25:29.062 24419:24419 E/mm-camera]
<IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_optizoom_lib.so

[08-12 12:25:29.062 24419:24419 E/mm-camera]
<IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_ubifocus_lib.so error dlopen failed: library "libmmcamera_ubifocus_lib.so" not found

[08-12 12:25:29.062 24419:24419 E/mm-camera]
<IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_ubifocus_lib.so

[08-12 12:25:29.063 24419:24419 E/mm-camera]
<IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_ubifocus_lib.so error dlopen failed: library "libmmcamera_ubifocus_lib.so" not found

[08-12 12:25:29.063 24419:24419 E/mm-camera]
<IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_ubifocus_lib.so

[08-12 12:25:29.063 24419:24419 E/mm-camera]
<IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_trueportrait_lib.so error dlopen failed: library "libmmcamera_trueportrait_lib.so" not found

[08-12 12:25:29.063 24419:24419 E/mm-camera]
<IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_trueportrait_lib.so

[08-12 12:25:29.064 24419:24419 E/mm-camera]
<IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_stillmore_lib.so error dlopen failed: library "libmmcamera_stillmore_lib.so" not found

[08-12 12:25:29.064 24419:24419 E/mm-camera]
<IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_stillmore_lib.so

[08-12 12:25:29.064 24419:24419 I/mm-camera]
<MCT >< INFO> 135: server_process_module_init: CAMERA_DAEMON: init mods done

[08-12 12:25:29.750 24339:24386 E/CamDeviceVerify]
Camera Manager reconnect failed, or there are no cameras on this device.

[08-12 12:25:29.766 24339:24386 I/GCamMod_ActivityStartup]
WaitForCameraDevices complete.

[08-12 12:25:29.771 24339:24339 E/AndroidRuntime]
FATAL EXCEPTION: main
Process: com.google.android.GoogleCamera, PID: 24339
java.lang.IllegalStateException: No Cameras are currently available.
at dor.a(Unknown Source:25)
at dot.a(Unknown Source:32)
at kwc.a(Unknown Source:16)
at byl.a(Unknown Source:8)
at kwc.a(Unknown Source:16)
at gqe.run(Unknown Source:2)
at iki.run(Unknown Source:2)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:462)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.jav
a:301)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
at java.lang.Thread.run(Thread.java:923)
at ijj.run(Unknown Source:5)

[08-12 12:25:29.775 24339:24386 I/GCamMod_ActivityUiStartup]
CameraActivityController complete.

[08-12 12:25:29.798 1473:1498 W/ActivityTaskManager]
Force finishing activity com.google.android.GoogleCamera/com.android.camera.CameraLauncher

[08-12 12:25:29.826 6064:15920 D/GmsClearcutLogSvcImpl]
log: LogEventParcelable[1, PlayLoggerContext[1, package=com.google.android.GoogleCamera, packageVersionCode=42349277, logSource=-1, uploadAccount=null, loggingId=-1, logAndroidId=true, logSourceName=ANDROID_CAMERA, isAnonymous=false, qosTier=0], LogEventBytes: CK2js4KpMDIaCBayAQIIAf0BO06pcZACA8ICBzUuMy4wMTV4gMIDiAHb4bEB, AddPhenotypeExperimentTokens: true]

[08-12 12:25:29.835 6064:15920 D/GmsClearcutLogSvcImpl]
log: LogEventParcelable[1, PlayLoggerContext[1, package=com.google.android.GoogleCamera, packageVersionCode=42349277, logSource=-1, uploadAccount=null, loggingId=-1, logAndroidId=true, logSourceName=ANDROID_CAMERA, isAnonymous=false, qosTier=0], LogEventBytes: CLSjs4KpMDJvCAdKVQgJGlFsaW5lYWdlX29uZXBsdXMzLXVzZXJkZWJ1ZyAxMSBSUTNBLjIxMTAwMS4wMDEgZW5nLmFuZHJvaS4yMDIyMDgwNS4xOTE0NDMgZGV2LWtleXP9ATtOqXGAAgGQAgPCAgc1LjMuMDE1eIDCA4gB4+GxAQ==, AddPhenotypeExperimentTokens: true]

[08-12 12:25:29.847 1473:1584 I/ActivityManager]
Start proc 24469:com.google.android.GoogleCamera:crash_report/u0a251 for service {com.google.android.GoogleCamera/com.google.android.apps.camera.app.silentfeedback.SilentFeedbackService}

[08-12 12:25:29.886 1473:9264 I/ActivityManager]
Process com.google.android.GoogleCamera (pid 24339) has died: fg TOP

[08-12 12:25:29.889 1473:6584 I/WindowManager]
WIN DEATH: Window{95e704b u0 com.google.android.GoogleCamera/com.android.camera.CameraLauncher}

[08-12 12:25:29.889 1473:6584 W/InputDispatcher]
Attempted to unregister already unregistered input channel '95e704b com.google.android.GoogleCamera/com.android.camera.CameraLauncher (server)'

[08-12 12:25:30.273 6064:15920 D/GmsServicesProvider]
query caller=com.google.android.GoogleCamera name=camera:logging_override_level value=null

[08-12 12:25:30.300 1473:1513 W/ActivityTaskManager]
Activity top resumed state loss timeout for ActivityRecord{60c5e26 u0 com.google.android.GoogleCamera/com.android.camera.CameraLauncher t-1 f}}

[08-12 12:25:30.406 6064:17558 D/GmsFeedbackSvc]
bound by: GetServiceRequest{serviceId=FEEDBACK, gmsVersion=10298000, packageName='com.google.android.GoogleCamera', extras=Bundle[{}]}

[08-12 12:25:32.482 23991:23991 E/QCamera]
<MCI><ERROR> mm_camera_open: 291: Failed with Connection timed out error, retrying after 20 milli-seconds

[08-12 12:25:32.506 0:0 I/]
[<ffffffc00088f094>] camera_v4l2_open+0x2c4/0x4d8

[08-12 12:25:32.561 24419:24419 W/CAM_startstats]
type=1400 audit(0.0:3069): avc: denied { search } for name="/" dev="sda2" ino=2 scontext=u:r:mm-qcamerad:s0 tcontext=u:eek:bject_r:persist_file:s0 tclass=dir permissive=0

[08-12 12:25:32.565 24419:24419 W/CAM_startstats]
type=1400 audit(0.0:3070): avc: denied { search } for name="/" dev="sda2" ino=2 scontext=u:r:mm-qcamerad:s0 tcontext=u:eek:bject_r:persist_file:s0 tclass=dir permissive=0




Thanks for any assistance
 
Hello, and thanks in advance for any solutions here. I am new to custom OS so please bear with me if I get confused. My issue is that on my 3t, I installed the latest build, 18.1 20220805, and I still have no cameras. I didn't on the previus build either. Where the flashlight button is, it is greyed out, and says "camera in use" below it. I have at times, installed gcam from gcam hub, open cam etc, but get zilch as far as a functional camera is concerned . I can post logcat , I used camera as a filter.
Thanks for the log. Maybe an "unfiltered log" might provide even more useful information (please do not post hundreds of lines, but rather attach a file or provide a download link). Nevertheless, the errors show next to SELinux denials also missing libraries and the logs seem to show Google Camera failing to load (I would be more interested to see the shipped Camera from LineageOS). The logs create to me the impression, that you have somehow changed or modified something on the ROM

To understand you better:
  • You originally clean-flashed my July build on your 3T. When you did that, before flashing anything on top, was the originally shipped Camera working?
  • Did you apply, as explained in the OP, the correct 9.0.6 firmware (next to the ROM)?
  • Did you flash anything on top, have executed scripts, manually replaced or added files via root access etc.?
 
  • Like
Reactions: thomasnsr

ozrocks

New member
Aug 12, 2022
3
1
OnePlus 3
Hi, I origionally flashed lineage 17.1 factory version which worked camera included. After a few days, I discovered your build and installed that, and tried to insttall kali on top which bricked it, and somehow I lost cameras before I reinstalled your version prior to the current one. The current one I flashed yesterday in a final attempt to get cams running, so its probably not to do with the latest build at all, but some error I have made.
I hve attached full files, I hope this gives you a better understanding, many thanks. Sorry I couldnt seem to attach a a file

08-13 10:50:25.894 6971 6971 E mm-camera: <MCT ><ERROR> 4800: mct_pipeline_start_session: Timeout in starting session on all modules
08-13 10:50:25.894 6971 6971 E mm-camera: <MCT ><ERROR> 73: mct_controller_new: Start session failed with status -1
08-13 10:50:25.894 6971 6971 I mm-camera: <MCT >< INFO> 4721: mct_pipeline_stop_session: Initiating stop_session on session 2
08-13 10:50:25.894 6971 6971 E mm-camera: <MCT ><ERROR> 769: mct_pipeline_unmap_parm: Cannot find session stream
08-13 10:50:25.894 6971 6971 E mm-camera: <MCT ><ERROR> 4523: mct_pipeline_stop_stream_internal: stream unmap_parm failed
08-13 10:50:25.895 6971 7053 I mm-camera: <MCT >< INFO> 4455: mct_pipeline_stop_session_thread: Stop module name: sensor - E
08-13 10:50:25.899 6971 7054 I mm-camera: <MCT >< INFO> 4455: mct_pipeline_stop_session_thread: Stop module name: iface - E
08-13 10:50:25.901 6971 7054 I mm-camera: <MCT >< INFO> 4463: mct_pipeline_stop_session_thread: Stop module name: iface - X
08-13 10:50:25.902 6971 7056 I mm-camera: <MCT >< INFO> 4455: mct_pipeline_stop_session_thread: Stop module name: isp - E
08-13 10:50:25.902 6971 7056 I mm-camera: <ISP >< INFO> 487: isp_module_stop_session: session id 2
08-13 10:50:25.904 6971 7056 I mm-camera: <MCT >< INFO> 4463: mct_pipeline_stop_session_thread: Stop module name: isp - X
08-13 10:50:25.905 6971 7057 I mm-camera: <MCT >< INFO> 4455: mct_pipeline_stop_session_thread: Stop module name: stats - E
08-13 10:50:25.909 7055 7055 W crash_dump32: failed to attach to thread 7033: No such process
08-13 10:50:25.909 7055 7055 E crash_dump32: failed to interrupt 7033 to detach: No such process
08-13 10:50:25.909 7055 7055 W crash_dump32: failed to ptrace interrupt thread 7033: No such process
08-13 10:50:25.909 7055 7055 W crash_dump32: failed to attach to thread 7034: No such process
08-13 10:50:25.909 7055 7055 E crash_dump32: failed to interrupt 7034 to detach: No such process
08-13 10:50:25.909 7055 7055 W crash_dump32: failed to ptrace interrupt thread 7034: No such process
08-13 10:50:25.909 7055 7055 W crash_dump32: failed to attach to thread 7035: No such process
08-13 10:50:25.909 7055 7055 E crash_dump32: failed to interrupt 7035 to detach: No such process
08-13 10:50:25.909 7055 7055 W crash_dump32: failed to ptrace interrupt thread 7035: No such process
08-13 10:50:25.983 963 28701 I WifiService: startScan uid=1000
08-13 10:50:25.986 7055 7055 W crash_dump32: failed to attach to thread 7056: No such process
08-13 10:50:25.987 7055 7055 E crash_dump32: failed to interrupt 7056 to detach: No such process
08-13 10:50:25.987 7055 7055 W crash_dump32: failed to ptrace interrupt thread 7056: No such process
08-13 10:50:26.027 7055 7055 I crash_dump32: obtaining output fd from tombstoned, type: kDebuggerdTombstone
08-13 10:50:26.027 6971 7060 I mm-camera: <MCT >< INFO> 4455: mct_pipeline_stop_session_thread: Stop module name: pproc - E
08-13 10:50:26.028 503 503 I tombstoned: received crash request for pid 7018
08-13 10:50:26.029 7055 7055 I crash_dump32: performing dump of process 6971 (target tid = 7018)
08-13 10:50:26.033 6971 7061 I mm-camera: <MCT >< INFO> 4455: mct_pipeline_stop_session_thread: Stop module name: imglib - E
08-13 10:50:26.033 6971 6971 I mm-camera: <MCT >< INFO> 4743: mct_pipeline_stop_session: Modules left: 4
08-13 10:50:26.033 6971 6971 I mm-camera: <MCT >< INFO> 4743: mct_pipeline_stop_session: Modules left: 3
08-13 10:50:26.033 6971 7061 I mm-camera: <MCT >< INFO> 4463: mct_pipeline_stop_session_thread: Stop module name: imglib - X
08-13 10:50:26.033 6971 6971 I mm-camera: <MCT >< INFO> 4743: mct_pipeline_stop_session: Modules left: 2
08-13 10:50:26.034 6971 7060 I mm-camera: <MCT >< INFO> 4463: mct_pipeline_stop_session_thread: Stop module name: pproc - X
08-13 10:50:26.034 6971 6971 I mm-camera: <MCT >< INFO> 4743: mct_pipeline_stop_session: Modules left: 1
08-13 10:50:26.045 7055 7055 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
08-13 10:50:26.046 7055 7055 F DEBUG : LineageOS Version: '18.1-20220805-UNOFFICIAL-microG-signed-oneplus3'
08-13 10:50:26.046 7055 7055 F DEBUG : Build fingerprint: 'OnePlus/OnePlus3/OnePlus3T:8.0.0/OPR1.170623.032/02281230:user/release-keys'
08-13 10:50:26.046 7055 7055 F DEBUG : Revision: '0'
08-13 10:50:26.047 7055 7055 F DEBUG : ABI: 'arm'
08-13 10:50:26.048 7055 7055 F DEBUG : Timestamp: 2022-08-13 10:50:26+0800
08-13 10:50:26.048 7055 7055 F DEBUG : pid: 6971, tid: 7018, name: POSIX timer 0 >>> /system/vendor/bin/mm-qcamera-daemon <<<
08-13 10:50:26.048 7055 7055 F DEBUG : uid: 1006
08-13 10:50:26.048 7055 7055 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
08-13 10:50:26.048 7055 7055 F DEBUG : r0 00000000 r1 00001b6a r2 00000006 r3 eb653d38
08-13 10:50:26.048 7055 7055 F DEBUG : r4 eb653d38 r5 eb653d28 r6 eb653cd8 r7 0000010c
08-13 10:50:26.048 6971 7053 I mm-camera: <MCT >< INFO> 4463: mct_pipeline_stop_session_thread: Stop module name: sensor - X
08-13 10:50:26.049 7055 7055 F DEBUG : r8 eb653d08 r9 eb653cf8 r10 eb653ce8 r11 00000070
08-13 10:50:26.049 7055 7055 F DEBUG : ip eb653d18 sp eb653cc0 lr f0987f5d pc f09b8030
08-13 10:50:26.049 6971 6971 I mm-camera: <MCT >< INFO> 4743: mct_pipeline_stop_session: Modules left: 0
08-13 10:50:26.049 6971 6971 I mm-camera: <MCT >< INFO> 4752: mct_pipeline_stop_session: Stopped session 2 successfully
08-13 10:50:26.049 6971 6971 E mm-camera: <MCT ><ERROR> 525: main: New session [2] creation failed with error
08-13 10:50:26.049 6971 6971 E mm-camera: <MCT ><ERROR> 645: main: main: camera daemon notify error
08-13 10:50:26.056 7055 7055 F DEBUG : backtrace:
08-13 10:50:26.056 7055 7055 F DEBUG : #00 pc 00071030 /apex/com.android.runtime/lib/bionic/libc.so (tgkill+12) (BuildId: d029b4ff0a1a2985f36525649613dac7)
08-13 10:50:26.056 7055 7055 F DEBUG : #01 pc 00040f5b /apex/com.android.runtime/lib/bionic/libc.so (__timer_thread_start(void*)+158) (BuildId: d029b4ff0a1a2985f36525649613dac7)
08-13 10:50:26.056 7055 7055 F DEBUG : #02 pc 00081ca7 /apex/com.android.runtime/lib/bionic/libc.so (__pthread_start(void*)+40) (BuildId: d029b4ff0a1a2985f36525649613dac7)
08-13 10:50:26.056 7055 7055 F DEBUG : #03 pc 00039cf7 /apex/com.android.runtime/lib/bionic/libc.so (__start_thread+30) (BuildId: d029b4ff0a1a2985f36525649613dac7)
08-13 10:50:26.199 0 0 D logd : logdr: UID=1006 GID=1006 PID=7055 n tail=50 logMask=8 pid=6971 start=0ns timeout=0ns
08-13 10:50:26.207 0 0 D logd : logdr: UID=1006 GID=1006 PID=7055 n tail=50 logMask=1 pid=6971 start=0ns timeout=0ns
08-13 10:50:26.221 963 28701 I WifiService: startScan uid=1000
08-13 10:50:26.245 0 0 D logd : logdr: UID=1006 GID=1006 PID=7055 n tail=0 logMask=8 pid=6971 start=0ns timeout=0ns
08-13 10:50:26.252 0 0 D logd : logdr: UID=1006 GID=1006 PID=7055 n tail=0 logMask=1 pid=6971 start=0ns timeout=0ns
08-13 10:50:26.271 963 3690 W NativeCrashListener: Couldn't find ProcessRecord for pid 6971
08-13 10:50:26.277 503 503 E tombstoned: Tombstone written to: /data/tombstones/tombstone_44
08-13 10:50:26.284 0 0 E : msm_csiphy_release csiphy dev NULL / ref_count ZERO
08-13 10:50:26.285 0 0 I chatty : uid=0(root) logd identical 1 line
08-13 10:50:26.285 0 0 E : msm_csiphy_release csiphy dev NULL / ref_count ZERO
08-13 10:50:26.285 0 0 E msm_csid_release: csid invalid state 1
08-13 10:50:26.285 0 0 I chatty : uid=0(root) logd identical 2 lines
08-13 10:50:26.285 0 0 E msm_csid_release: csid invalid state 1
08-13 10:50:26.285 0 0 E : msm_cci_release invalid ref count 0 / cci state 1
08-13 10:50:26.285 0 0 E MSM-SENSOR-INIT msm_sensor_init_subdev_ioctl: 121 default
08-13 10:50:26.285 0 0 W MSM-CPP msm_cpp_subdev_ioctl: 3315 shutdown cpp node. open cnt:0
08-13 10:50:26.285 0 0 I msm_pm_qos_remove_request: remove request
08-13 10:50:26.285 0 0 W : ------------[ cut here ]------------
08-13 10:50:26.285 0 0 W : WARNING: CPU: 3 PID: 7057 at ../../../../../../../../data/android/lin-18.1/kernel/oneplus/msm8996/kernel/power/qos.c:636 pm_qos_remove_request+0x15c/0x174()
08-13 10:50:26.285 0 0 I : pm_qos_remove_request() called for unknown object
08-13 10:50:26.285 0 0 I : CPU: 3 PID: 7057 Comm: CAM_stopstats Tainted: G W 3.18.124-lineageos-gfce013ed1787 #1
08-13 10:50:26.285 0 0 I Hardware name: Qualcomm Technologies, Inc. MSM 8996pro + PMI8996 MTP (DT)
08-13 10:50:26.285 0 0 F Call trace:
08-13 10:50:26.285 0 0 I : [<ffffffc00008aff8>] dump_backtrace+0x0/0x284
08-13 10:50:26.285 0 0 I : [<ffffffc00008aff0>] show_stack+0x14/0x1c
08-13 10:50:26.285 0 0 I : [<ffffffc0003b422c>] dump_stack+0xac/0xe0
08-13 10:50:26.285 0 0 I : [<ffffffc0000a9bf4>] warn_slowpath_common+0x94/0x110
08-13 10:50:26.285 0 0 I : [<ffffffc0000a9b3c>] warn_slowpath_fmt+0x50/0x74
08-13 10:50:26.285 0 0 I : [<ffffffc0000fdd50>] pm_qos_remove_request+0x15c/0x174
08-13 10:50:26.285 0 0 I : [<ffffffc00088e06c>] msm_close+0xf8/0x2f4
08-13 10:50:26.285 0 0 I : [<ffffffc00082cc14>] v4l2_release+0x38/0x84
08-13 10:50:26.285 0 0 I : [<ffffffc0001d8adc>] __fput+0xb4/0x190
08-13 10:50:26.285 0 0 I : [<ffffffc0001d89d0>] ____fput+0xc/0x14
08-13 10:50:26.285 0 0 I : [<ffffffc0000c6c00>] task_work_run+0xbc/0xdc
08-13 10:50:26.285 0 0 I : [<ffffffc0000ab4bc>] do_exit+0x38c/0x874
08-13 10:50:26.285 0 0 I : [<ffffffc0000aba68>] do_group_exit+0x90/0xa4
08-13 10:50:26.285 0 0 I : [<ffffffc0000b8178>] get_signal+0x334/0x5b8
08-13 10:50:26.285 0 0 I : [<ffffffc00008a7e8>] do_notify_resume+0xb4/0x588
08-13 10:50:26.285 0 0 W : ---[ end trace f0775e96575f9477 ]---
08-13 10:50:26.286 0 0 I init : Service 'qcamerasvr' (pid 6971) received signal 6
08-13 10:50:26.286 0 0 I init : Sending signal 9 to service 'qcamerasvr' (pid 6971) process group...
08-13 10:50:26.297 0 0 I libprocessgroup: Successfully killed process cgroup uid 1006 pid 6971 in 10ms
08-13 10:50:26.299 0 0 I init : Untracked pid 7055 exited with status 0
08-13 10:50:26.299 0 0 I init : Untracked pid 7059 exited with status 0
08-13 10:50:26.299 0 0 I init : starting service 'qcamerasvr'...
08-13 10:50:26.305 963 1288 I BootReceiver: Copying /data/tombstones/tombstone_44 to DropBox (SYSTEM_TOMBSTONE)
08-13 10:50:26.310 963 1288 I DropBoxManagerService: add tag=SYSTEM_TOMBSTONE isTagEnabled=true flags=0x2
08-13 10:50:26.434 7066 7066 I mm-camera: < INFO> 420: init: memleak lib init.
08-13 10:50:26.434 7066 7066 I mm-camera: < INFO> 439: init: memleak tracer not attached
08-13 10:50:26.470 7066 7066 E mm-camera: <SENSOR><ERROR> 385: eebin_read: failed!
08-13 10:50:26.470 7066 7066 E mm-camera: <SENSOR><ERROR> 385: eebin_read: failed!
08-13 10:50:26.470 7066 7066 E mm-camera: <SENSOR><ERROR> 467: sensor_init_probe: failed: to probe eeprom bin sensors (non-fatal)
08-13 10:50:26.466 0 0 I msm_pm_qos_add_request: add request
08-13 10:50:26.472 0 0 E slot0 : sensor name: imx298 sensor id664 already probed
08-13 10:50:26.475 0 0 E slot1 : sensor name: s5k3p8sp sensor id12552 already probed
08-13 10:50:26.481 0 0 I msm_csid_init: CSID_VERSION = 0x30050000
08-13 10:50:26.483 0 0 E : msm_csid_irq CSID0_IRQ_STATUS_ADDR = 0x800
08-13 10:50:26.485 0 0 I msm_csid_init: CSID_VERSION = 0x30050000
08-13 10:50:26.487 0 0 E : msm_csid_irq CSID0_IRQ_STATUS_ADDR = 0x800
08-13 10:50:26.492 7066 7066 I mm-camera: sony_imx298_eeprom_format_wbdata: IMX298 vendor id:4 (1-Sunny/4-Lite_On)
08-13 10:50:26.492 7066 7066 I mm-camera: sony_imx298_eeprom_format_wbdata: 5100K awb_r_over_gr: 0.446237, awb_b_over_gr: 0.521505, awb_gr_over_gb: 1.000000
08-13 10:50:26.492 7066 7066 I mm-camera: sony_imx298_eeprom_format_wbdata: 3000K awb_r_over_gr: 0.713450, awb_b_over_gr: 0.374269, awb_gr_over_gb: 0.994186
08-13 10:50:26.492 7066 7066 I mm-camera: sony_imx298_eeprom_format_afdata orig macro:602 infinity:315
08-13 10:50:26.494 7066 7066 E mm-camera: <SENSOR><ERROR> s5k3p8sp_m24c64s_eeprom_format_calibration_data: 321: Buff pointer 0xf1780010 buffer size 5890
08-13 10:50:26.494 7066 7066 I mm-camera: s5k3p8sp_m24c64s_eeprom_format_wbdata: S5K3P8 sensor id:0x3b (3A-3P8/3B-3P8SP)
08-13 10:50:26.494 7066 7066 I mm-camera: s5k3p8sp_m24c64s_eeprom_format_wbdata: S5K3P8 vendor info:1
08-13 10:50:26.494 7066 7066 I mm-camera: s5k3p8sp_m24c64s_eeprom_format_wbdata: 5100K awb_r_over_gr: 0.406417, awb_b_over_gr: 0.588235, awb_gr_over_gb: 1.000000
08-13 10:50:26.494 7066 7066 I mm-camera: s5k3p8sp_m24c64s_eeprom_format_wbdata: 3000K awb_r_over_gr: 0.673913, awb_b_over_gr: 0.375000, awb_gr_over_gb: 1.000000
08-13 10:50:26.494 7066 7066 I mm-camera: AWB valid = 1, checksum[5100K] = [8,8] checksum[3000K] = [102,102]
08-13 10:50:26.494 7066 7066 I mm-camera: LSC valid = 1, checksum[LSC] = [81,81]
08-13 10:50:26.494 7066 7066 I mm-camera: Valid; cross-talk valid = 1, checksum[cross-talk] = [29,29]
08-13 10:50:26.494 7066 7066 I mm-camera: s5k3p8sp_m24c64s_eeprom_get_calibration_items: Sensor ID:0x3b is_wbc:1 is_lsc:1
08-13 10:50:26.494 7066 7066 E mm-camera: <SENSOR><ERROR> 71: cm_create: Sensor_name: imx298 Vendor_info: 4 Lens_info: 0
08-13 10:50:26.501 7066 7066 E mm-camera: <SENSOR><ERROR> 119: cm_create: 3A chromatix name (preview, video) = (imx298_zsl_preview, imx298_zsl_video)
08-13 10:50:26.505 7066 7066 E mm-camera: <SENSOR><ERROR> 119: cm_create: 3A chromatix name (preview, video) = (imx298_default_preview, imx298_default_video)
08-13 10:50:26.507 7066 7066 E mm-camera: <SENSOR><ERROR> 119: cm_create: 3A chromatix name (preview, video) = (imx298_hfr_60_3a, imx298_hfr_60_3a)
08-13 10:50:26.510 7066 7066 E mm-camera: <SENSOR><ERROR> 119: cm_create: 3A chromatix name (preview, video) = (imx298_hfr_90_3a, imx298_hfr_90_3a)
08-13 10:50:26.513 7066 7066 E mm-camera: <SENSOR><ERROR> 119: cm_create: 3A chromatix name (preview, video) = (imx298_hfr_120_3a, imx298_hfr_120_3a)
08-13 10:50:26.514 7066 7066 E mm-camera: <SENSOR><ERROR> 119: cm_create: 3A chromatix name (preview, video) = (imx298_4K_preview, imx298_4K_video)
08-13 10:50:26.516 7066 7066 E mm-camera: <SENSOR><ERROR> 119: cm_create: 3A chromatix name (preview, video) = (, )
08-13 10:50:26.517 7066 7066 E mm-camera: <SENSOR><ERROR> 119: cm_create: 3A chromatix name (preview, video) = (, )
08-13 10:50:26.519 7066 7066 E mm-camera: <SENSOR><ERROR> 119: cm_create: 3A chromatix name (preview, video) = (imx298_zsl_preview, )
08-13 10:50:26.520 7066 7066 E mm-camera: <SENSOR><ERROR> 119: cm_create: 3A chromatix name (preview, video) = (imx298_3a_HDR, )
08-13 10:50:26.520 7066 7066 E mm-camera: <SENSOR><ERROR> 119: cm_create: 3A chromatix name (preview, video) = (, )
08-13 10:50:26.524 7066 7066 E mm-camera: <SENSOR><ERROR> 119: cm_create: 3A chromatix name (preview, video) = (imx298_3a_clearshot, )
08-13 10:50:26.527 7066 7066 E mm-camera: <SENSOR><ERROR> 119: cm_create: 3A chromatix name (preview, video) = (imx298_3a_panorama, )
08-13 10:50:26.528 7066 7066 E mm-camera: <SENSOR><ERROR> 119: cm_create: 3A chromatix name (preview, video) = (, )
08-13 10:50:26.528 7066 7066 E mm-camera: <SENSOR><ERROR> 119: cm_create: 3A chromatix name (preview, video) = (, imx298_4K_video)
08-13 10:50:26.529 7066 7066 E mm-camera: <SENSOR><ERROR> 119: cm_create: 3A chromatix name (preview, video) = (, )
08-13 10:50:26.529 7066 7066 E mm-camera: <SENSOR><ERROR> 71: cm_create: Sensor_name: s5k3p8sp Vendor_info: 1 Lens_info: 0
08-13 10:50:26.534 7066 7066 E mm-camera: <SENSOR><ERROR> 119: cm_create: 3A chromatix name (preview, video) = (s5k3p8sp_3a_2304x1728_30fps_preview, s5k3p8sp_3a_2304x1728_30fps_video)
08-13 10:50:26.540 7066 7066 E mm-camera: <SENSOR><ERROR> 119: cm_create: 3A chromatix name (preview, video) = (s5k3p8sp_3a_4608x3456_30fps_preview, s5k3p8sp_3a_4608x3456_30fps_video)
08-13 10:50:26.541 7066 7066 E mm-camera: <SENSOR><ERROR> 119: cm_create: 3A chromatix name (preview, video) = (, )
08-13 10:50:26.542 7066 7066 E mm-camera: <SENSOR><ERROR> 119: cm_create: 3A chromatix name (preview, video) = (s5k3p8sp_3a_2304x1728_30fps_face_unlock, )
08-13 10:50:26.542 7066 7066 I mm-camera: <MCT >< INFO> 98: server_process_module_init: Begin init mods
08-13 10:50:26.542 7066 7066 E mm-camera: <IFACE ><ERROR> 12480: iface_util_setloglevel: iface_util_setloglevel:12480 IFACE_Loglevel 1
08-13 10:50:26.608 26408 26408 W HidlServiceManagement: Waited one second for [email protected]::IRadio/slot2
08-13 10:50:26.611 446 446 I hwservicemanager: Since [email protected]::IRadio/slot2 is not registered, trying to start it as a lazy HAL.
08-13 10:50:26.616 26408 26408 I HidlServiceManagement: getService: Trying again for [email protected]::IRadio/slot2...
08-13 10:50:26.617 7066 7066 I mm-camera: <ISP >< INFO> 893: module_isp_init: module 0xf19c0c50
08-13 10:50:26.618 446 7067 W libc : Unable to set property "ctl.interface_start" to "[email protected]::IRadio/slot2": error code: 0x20
08-13 10:50:26.615 0 0 E init : Control message: Could not find '[email protected]::IRadio/slot2' for ctl.interface_start from pid: 446 (/system/bin/hwservicemanager)
08-13 10:50:26.620 0 0 I MSM-CPP cpp_init_hardware: 1011 CPP HW Version: 0x60000000
08-13 10:50:26.620 0 0 E MSM-CPP cpp_init_hardware: 1029 stream_cnt:0
08-13 10:50:26.630 7066 7066 I mm-camera: <CPP >< INFO> 145: cpp_module_init: info: CPP module_init successful
08-13 10:50:26.637 7066 7066 E mm-camera: <IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_ppeiscore.so error dlopen failed: library "libmmcamera_ppeiscore.so" not found
08-13 10:50:26.637 7066 7066 E mm-camera: <IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_ppeiscore.so
08-13 10:50:26.637 7066 7066 E mm-camera: <IMGLIB><ERROR> 3115: module_imgbase_init: module_imgbase_init_ppeiscore:3115] Error rc -7
08-13 10:50:26.648 7066 7066 E mm-camera: <IMGLIB><ERROR> 957: frameproc_comp_load_fn_ptrs: img_algo_post_process can be NULL for few AOST features
08-13 10:50:26.649 7066 7066 E mm-camera: <IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_llvd.so error dlopen failed: library "libmmcamera_llvd.so" not found
08-13 10:50:26.649 7066 7066 E mm-camera: <IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_llvd.so
08-13 10:50:26.649 7066 7066 E mm-camera: <IMGLIB><ERROR> 3115: module_imgbase_init: module_imgbase_init_llvd:3115] Error rc -7
08-13 10:50:26.652 7066 7066 E mm-camera: <IMGLIB><ERROR> 957: frameproc_comp_load_fn_ptrs: img_algo_post_process can be NULL for few AOST features
08-13 10:50:26.667 7066 7066 E mm-camera: <IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_chromaflash_lib.so error dlopen failed: library "libmmcamera_chromaflash_lib.so" not found
08-13 10:50:26.667 7066 7066 E mm-camera: <IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_chromaflash_lib.so
08-13 10:50:26.667 7066 7066 E mm-camera: <IMGLIB><ERROR> 3115: module_imgbase_init: module_imgbase_init_imglib_chroma_flash:3115] Error rc -7
08-13 10:50:26.667 7066 7066 E mm-camera: <IMGLIB><ERROR> 744: module_imglib_create_topology: module_imglib_create_topology:744] Can not init the module imglib_chroma_flash
08-13 10:50:26.668 7066 7066 E mm-camera: <IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_optizoom_lib.so error dlopen failed: library "libmmcamera_optizoom_lib.so" not found
08-13 10:50:26.668 7066 7066 E mm-camera: <IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_optizoom_lib.so
08-13 10:50:26.668 7066 7066 E mm-camera: <IMGLIB><ERROR> 3115: module_imgbase_init: module_imgbase_init_imglib_optizoom:3115] Error rc -7
08-13 10:50:26.668 7066 7066 E mm-camera: <IMGLIB><ERROR> 744: module_imglib_create_topology: module_imglib_create_topology:744] Can not init the module imglib_optizoom
08-13 10:50:26.669 7066 7066 E mm-camera: <IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_ubifocus_lib.so error dlopen failed: library "libmmcamera_ubifocus_lib.so" not found
08-13 10:50:26.669 7066 7066 E mm-camera: <IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_ubifocus_lib.so
08-13 10:50:26.669 7066 7066 E mm-camera: <IMGLIB><ERROR> 3115: module_imgbase_init: module_imgbase_init_imglib_ubifocus:3115] Error rc -7
08-13 10:50:26.669 7066 7066 E mm-camera: <IMGLIB><ERROR> 744: module_imglib_create_topology: module_imglib_create_topology:744] Can not init the module imglib_ubifocus
08-13 10:50:26.670 7066 7066 E mm-camera: <IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_ubifocus_lib.so error dlopen failed: library "libmmcamera_ubifocus_lib.so" not found
08-13 10:50:26.670 7066 7066 E mm-camera: <IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_ubifocus_lib.so
08-13 10:50:26.670 7066 7066 E mm-camera: <IMGLIB><ERROR> 3115: module_imgbase_init: module_imgbase_init_imglib_refocus:3115] Error rc -7
08-13 10:50:26.670 7066 7066 E mm-camera: <IMGLIB><ERROR> 744: module_imglib_create_topology: module_imglib_create_topology:744] Can not init the module imglib_refocus
08-13 10:50:26.671 7066 7066 E mm-camera: <IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_trueportrait_lib.so error dlopen failed: library "libmmcamera_trueportrait_lib.so" not found
08-13 10:50:26.671 7066 7066 E mm-camera: <IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_trueportrait_lib.so
08-13 10:50:26.671 7066 7066 E mm-camera: <IMGLIB><ERROR> 3115: module_imgbase_init: module_imgbase_init_imglib_trueportrait:3115] Error rc -7
08-13 10:50:26.671 7066 7066 E mm-camera: <IMGLIB><ERROR> 744: module_imglib_create_topology: module_imglib_create_topology:744] Can not init the module imglib_trueportrait
08-13 10:50:26.672 7066 7066 E mm-camera: <IMGLIB><ERROR> 1168: frameproc_comp_reload_lib: frameproc_comp_reload_lib:1168] Error opening frameproc library libmmcamera_stillmore_lib.so error dlopen failed: library "libmmcamera_stillmore_lib.so" not found
08-13 10:50:26.672 7066 7066 E mm-camera: <IMGLIB><ERROR> 1037: frameproc_comp_load: frameproc_comp_load:1037] cannot load libmmcamera_stillmore_lib.so
08-13 10:50:26.672 7066 7066 E mm-camera: <IMGLIB><ERROR> 3115: module_imgbase_init: module_imgbase_init_imglib_stillmore:3115] Error rc -7
08-13 10:50:26.672 7066 7066 E mm-camera: <IMGLIB><ERROR> 744: module_imglib_create_topology: module_imglib_create_topology:744] Can not init the module imglib_stillmore
08-13 10:50:26.672 7066 7066 E mm-camera: <IMGLIB><ERROR> 744: module_imglib_create_topology: module_imglib_create_topology:744] Can not init the module imglib_oem1
08-13 10:50:26.672 7066 7066 I mm-camera: <MCT >< INFO> 135: server_process_module_init: CAMERA_DAEMON: init mods done
08-13 10:50:27.617 26408 26408 W HidlServiceManagement: Waited one second for [email protected]::IRadio/slot2
08-13 10:50:27.618 446 446 I hwservicemanager: Since [email protected]::IRadio/slot2 is not registered, trying to start it as a lazy HAL.
08-13 10:50:27.620 26408 26408 I HidlServiceManagement: getService: Trying again for [email protected]::IRadio/slot2...
08-13 10:50:27.627 446 7131 W libc : Unable to set property "ctl.interface_start" to "[email protected]::IRadio/slot2": error code: 0x20
08-13 10:50:27.624 0 0 E init : Control message: Could not find '[email protected]::IRadio/slot2' for ctl.interface_start from pid: 446 (/system/bin/hwservicemanager)
08-13 10:50:28.205 0 0 W healthd : battery l=100 v=4316 t=27.2 h=2 st=5 c=0 fc=2966000 chg=u
08-13 10:50:28.621 26408 26408 W HidlServiceManagement: Waited one second for [email protected]::IRadio/slot2
08-13 10:50:28.623 446 446 I hwservicemanager: Since [email protected]::IRadio/slot2 is not registered, trying to start it as a lazy HAL.
08-13 10:50:28.625 26408 26408 I HidlServiceManagement: getService: Trying again for [email protected]::IRadio/slot2...
08-13 10:50:28.626 0 0 E init : Control message: Could not find '[email protected]::IRadio/slot2' for ctl.interface_start from pid: 446 (/system/bin/hwservicemanager)
08-13 10:50:28.629 446 7132 W libc : Unable to set property "ctl.interface_start" to "[email protected]::IRadio/slot2": error code: 0x20
08-13 10:50:29.626 26408 26408 W HidlServiceManagement: Waited one second for [email protected]::IRadio/slot2
08-13 10:50:29.628 446 446 I hwservicemanager: Since [email protected]::IRadio/slot2 is not registered, trying to start it as a lazy HAL.
08-13 10:50:29.630 26408 26408 I HidlServiceManagement: getService: Trying again for [email protected]::IRadio/slot2...
08-13 10:50:29.632 446 7133 W libc : Unable to set property "ctl.interface_start" to "[email protected]::IRadio/slot2": error code: 0x20
08-13 10:50:29.856 6062 6062 E QCamera : <MCI><ERROR> mm_camera_open: 291: Failed with Connection timed out error, retrying after 20 milli-seconds
08-13 10:50:29.629 0 0 E init : Control message: Could not find '[email protected]::IRadio/slot2' for ctl.interface_start from pid: 446 (/system/bin/hwservicemanager)
08-13 10:50:29.853 0 0 E msm_post_event: Timed out
08-13 10:50:29.854 0 0 E : Evt_type=8002000 Evt_id=1 Evt_cmd=0
08-13 10:50:29.854 0 0 E : Evt_session_id=2 Evt_stream_id=0 Evt_arg=-1
08-13 10:50:29.854 0 0 E camera_v4l2_open: NEW_SESSION event failed,rc -110
08-13 10:50:29.881 7066 7066 I mm-camera: < INFO> 395: enable_memleak_trace: start memleak tracking.
08-13 10:50:29.876 0 0 I msm_pm_qos_update_request: update request 100
08-13 10:50:29.877 0 0 I msm_pm_qos_add_request: add request
08-13 10:50:29.877 0 0 W : ------------[ cut here ]------------
08-13 10:50:29.877 0 0 W : WARNING: CPU: 0 PID: 6062 at ../../../../../../../../data/android/lin-18.1/kernel/oneplus/msm8996/kernel/power/qos.c:583 pm_qos_update_request+0x50/0x5c()
08-13 10:50:29.877 0 0 E : pm_qos_update_request() called for unknown object
08-13 10:50:29.877 0 0 I : CPU: 0 PID: 6062 Comm: android.hardwar Tainted: G W 3.18.124-lineageos-gfce013ed1787 #1
08-13 10:50:29.877 0 0 I Hardware name: Qualcomm Technologies, Inc. MSM 8996pro + PMI8996 MTP (DT)
08-13 10:50:29.877 0 0 F Call trace:
08-13 10:50:29.877 0 0 I : [<ffffffc00008aff8>] dump_backtrace+0x0/0x284
08-13 10:50:29.877 0 0 I : [<ffffffc00008aff0>] show_stack+0x14/0x1c
08-13 10:50:29.877 0 0 I : [<ffffffc0003b422c>] dump_stack+0xac/0xe0
08-13 10:50:29.877 0 0 I : [<ffffffc0000a9bf4>] warn_slowpath_common+0x94/0x110
08-13 10:50:29.877 0 0 I : [<ffffffc0000a9b3c>] warn_slowpath_fmt+0x50/0x74
08-13 10:50:29.877 0 0 I : [<ffffffc0000fd9ac>] pm_qos_update_request+0x50/0x5c
08-13 10:50:29.877 0 0 I : [<ffffffc00088c22c>] msm_pm_qos_update_request+0x8c/0x98
08-13 10:50:29.877 0 0 I : [<ffffffc00088f094>] camera_v4l2_open+0x2c4/0x4d8
08-13 10:50:29.877 0 0 I : [<ffffffc00082cb94>] v4l2_open+0xac/0xf4
08-13 10:50:29.877 0 0 I : [<ffffffc0001db7bc>] chrdev_open+0x7c/0x17c
08-13 10:50:29.877 0 0 I : [<ffffffc0001d4f64>] do_dentry_open+0xdc/0x288
08-13 10:50:29.877 0 0 I : [<ffffffc0001d5174>] vfs_open+0x54/0x8c
08-13 10:50:29.877 0 0 I : [<ffffffc0001e8f9c>] do_last+0xb94/0x1064
08-13 10:50:29.877 0 0 I : [<ffffffc0001e1bcc>] path_openat+0xb8/0x6a8
08-13 10:50:29.877 0 0 I : [<ffffffc0001e1a9c>] do_filp_open+0x40/0xb8
08-13 10:50:29.877 0 0 I : [<ffffffc0001d56b4>] do_sys_open+0x144/0x250
08-13 10:50:29.877 0 0 I : [<ffffffc00022c500>] compat_SyS_openat+0xc/0x14
08-13 10:50:29.877 0 0 W : ---[ end trace f0775e96575f9478 ]---
08-13 10:50:29.905 7066 7066 I mm-camera: <MCT >< INFO> 63: mct_controller_new: Creating new mct_controller with session-id 2
08-13 10:50:29.905 7066 7134 I mm-camera: <MCT >< INFO> 4643: mct_pipeline_start_session_thread: E sensor
08-13 10:50:29.904 0 0 I msm_csid_init: CSID_VERSION = 0x30050000
08-13 10:50:29.906 0 0 E : msm_csid_irq CSID0_IRQ_STATUS_ADDR = 0x800
08-13 10:50:29.905 7066 7134 I mm-camera: <MCT >< INFO> 4650: mct_pipeline_start_session_thread: Calling start_session on Module sensor
08-13 10:50:29.906 7066 7135 I mm-camera: <MCT >< INFO> 4643: mct_pipeline_start_session_thread: E iface
08-13 10:50:29.906 7066 7135 I mm-camera: <MCT >< INFO> 4650: mct_pipeline_start_session_thread: Calling start_session on Module iface
08-13 10:50:29.908 7066 7135 I mm-camera: <MCT >< INFO> 4653: mct_pipeline_start_session_thread: Module iface start_session rc = 1
08-13 10:50:29.908 7066 7137 I mm-camera: <MCT >< INFO> 4643: mct_pipeline_start_session_thread: E isp
08-13 10:50:29.909 7066 7135 I mm-camera: <MCT >< INFO> 4661: mct_pipeline_start_session_thread: started_num = 1, success = 1
08-13 10:50:29.909 7066 7135 I mm-camera: <MCT >< INFO> 4668: mct_pipeline_start_session_thread: X iface
08-13 10:50:29.909 7066 7137 I mm-camera: <MCT >< INFO> 4650: mct_pipeline_start_session_thread: Calling start_session on Module isp
08-13 10:50:29.909 7066 7137 I mm-camera: <ISP >< INFO> 201: isp_module_start_session: session id 2
08-13 10:50:29.910 7066 7139 I mm-camera: <MCT >< INFO> 4643: mct_pipeline_start_session_thread: E stats
08-13 10:50:29.911 7066 7139 I mm-camera: <MCT >< INFO> 4650: mct_pipeline_start_session_thread: Calling start_session on Module stats
08-13 10:50:29.912 7066 7139 W mm-3a-core: init_light_sensor: skip light sensor init, cnt=1
08-13 10:50:29.916 7066 7134 I mm-camera: <MCT >< INFO> 4653: mct_pipeline_start_session_thread: Module sensor start_session rc = 1
08-13 10:50:29.916 7066 7134 I mm-camera: <MCT >< INFO> 4661: mct_pipeline_start_session_thread: started_num = 2, success = 2
08-13 10:50:29.916 7066 7134 I mm-camera: <MCT >< INFO> 4668: mct_pipeline_start_session_thread: X sensor
08-13 10:50:29.917 7066 7140 I mm-camera: <MCT >< INFO> 4643: mct_pipeline_start_session_thread: E pproc
08-13 10:50:29.917 7066 7140 I mm-camera: <MCT >< INFO> 4650: mct_pipeline_start_session_thread: Calling start_session on Module pproc
08-13 10:50:29.926 7066 7141 I mm-camera: <MCT >< INFO> 4643: mct_pipeline_start_session_thread: E imglib
08-13 10:50:29.926 7066 7141 I mm-camera: <MCT >< INFO> 4650: mct_pipeline_start_session_thread: Calling start_session on Module imglib
08-13 10:50:29.928 0 0 I MSM-CPP cpp_init_hardware: 1011 CPP HW Version: 0x60000000
08-13 10:50:29.928 0 0 E MSM-CPP cpp_init_hardware: 1029 stream_cnt:0
08-13 10:50:29.936 7066 7141 I mm-camera: <MCT >< INFO> 4653: mct_pipeline_start_session_thread: Module imglib start_session rc = 1
08-13 10:50:29.937 7066 7141 I mm-camera: <MCT >< INFO> 4661: mct_pipeline_start_session_thread: started_num = 3, success = 3
08-13 10:50:29.937 7066 7141 I mm-camera: <MCT >< INFO> 4668: mct_pipeline_start_session_thread: X imglib
08-13 10:50:29.940 7066 7139 E mm-camera: <STATS_AIS ><ERROR> 448: dsps_open: try to sensor1_open()
08-13 10:50:29.938 7066 7066 W CAM_startstats: type=1400 audit(0.0:10427): avc: denied { search } for name="/" dev="sda2" ino=2 scontext=u:r:mm-qcamerad:s0 tcontext=u:eek:bject_r:persist_file:s0 tclass=dir permissive=0
08-13 10:50:29.940 7066 7140 I mm-camera: <MCT >< INFO> 4653: mct_pipeline_start_session_thread: Module pproc start_session rc = 1
08-13 10:50:29.940 0 0 I msm_cci_init: 1434: hw_version = 0x10040000
08-13 10:50:29.940 7066 7140 I mm-camera: <MCT >< INFO> 4661: mct_pipeline_start_session_thread: started_num = 4, success = 4
08-13 10:50:29.940 7066 7140 I mm-camera: <MCT >< INFO> 4668: mct_pipeline_start_session_thread: X pproc
08-13 10:50:29.940 7066 7139 E libsensor1: realpath failed for directory name13
08-13 10:50:29.941 7066 7139 E Diag_Lib: Diag_LSM_Init: Failed to open handle to diag driver, error = 13
08-13 10:50:29.941 7066 7139 E libsensor1: realpath failed for directory name13
08-13 10:50:29.941 7066 7139 E libsensor1: check_sensors_enable: sensors settings file not available
08-13 10:50:29.946 7066 7137 I mm-camera: <MCT >< INFO> 4653: mct_pipeline_start_session_thread: Module isp start_session rc = 1
08-13 10:50:29.947 7066 7137 I mm-camera: <MCT >< INFO> 4661: mct_pipeline_start_session_thread: started_num = 5, success = 5
08-13 10:50:29.947 7066 7137 I mm-camera: <MCT >< INFO> 4668: mct_pipeline_start_session_thread: X isp
08-13 10:50:30.122 0 0 I msm_ois_control: 417 ois init [0x8200]=0x735/0xa75 retry=5
08-13 10:50:30.493 963 14489 D WifiNl80211Manager: Scan result ready event
08-13 10:50:30.493 963 14489 D WifiNative: Scan result ready event
08-13 10:50:30.496 945 3766 I LOWI-8.6.0.33: [LOWI-Scan] lowi_close_record:Scan done in 25391039ms, 18 APs in scan results
08-13 10:50:30.591 963 3491 D WificondScannerImpl: Filtering out 4 scan results.
08-13 10:50:30.632 26408 26408 W HidlServiceManagement: Waited one second for [email protected]::IRadio/slot2
08-13 10:50:30.633 446 446 I hwservicemanager: Since [email protected]::IRadio/slot2 is not registered, trying to start it as a lazy HAL.
08-13 10:50:30.634 26408 26408 I HidlServiceManagement: getService: Trying again for [email protected]::IRadio/slot2...
08-13 10:50:30.637 446 7150 W libc : Unable to set property "ctl.interface_start" to "[email protected]::IRadio/slot2": error code: 0x20
08-13 10:50:30.633 0 0 E init : Control message: Could not find '[email protected]::IRadio/slot2' for ctl.interface_start from pid: 446 (/system/bin/hwservicemanager)
08-13 10:50:31.634 26408 26408 W HidlServiceManagement: Waited one second for [email protected]::IRadio/slot2
08-13 10:50:31.636 446 446 I hwservicemanager: Since [email protected]::IRadio/slot2 is not registered, trying to start it as a lazy HAL.
08-13 10:50:31.637 26408 26408 I HidlServiceManagement: getService: Trying again for [email protected]::IRadio/slot2...
08-13 10:50:31.640 446 7151 W libc : Unable to set property "ctl.interface_start" to "[email protected]::IRadio/slot2": error code: 0x20
08-13 10:50:32.638 26408 26408 W HidlServiceManagement: Waited one second for [email protected]::IRadio/slot2
08-13 10:50:32.641 446 446 I hwservicemanager: Since [email protected]::IRadio/slot2 is not registered, trying to start it as a lazy HAL.
08-13 10:50:32.644 26408 26408 I HidlServiceManagement: getService: Trying again for [email protected]::IRadio/slot2...
08-13 10:50:32.645 446 7152 W libc : Unable to set property "ctl.interface_start" to "[email protected]::IRadio/slot2": error code: 0x20
08-13 10:50:33.560 6013 7195 D WireGuard/GoBackend/ProtonTunnel: peer(Jmke…Y+SU) - Sending handshake initiation
08-13 10:50:33.610 6013 7433 D WireGuard/GoBackend/ProtonTunnel: peer(Jmke…Y+SU) - Received handshake response
08-13 10:50:33.611 6013 7433 D WireGuard/GoBackend/ProtonTunnel: peer(Jmke…Y+SU) - Sending keepalive packet
08-13 10:50:33.644 26408 26408 W HidlServiceManagement: Waited one second for [email protected]::IRadio/slot2
08-13 10:50:33.648 446 446 I hwservicemanager: Since [email protected]::IRadio/slot2 is not registered, trying to start it as a lazy HAL.
08-13 10:50:33.650 26408 26408 I HidlServiceManagement: getService: Trying again for [email protected]::IRadio/slot2...
08-13 10:50:33.654 446 7153 W libc : Unable to set property "ctl.interface_start" to "[email protected]::IRadio/slot2": error code: 0x20
08-13 10:50:32.643 0 0 I chatty : uid=0(root) logd identical 2 lines
08-13 10:50:33.651 0 0 E init : Control message: Could not find '[email protected]::IRadio/slot2' f

I may not have applied firmware as specified, and have not intentionally altered any OS files.
 
Last edited:
Hi, I origionally flashed lineage 17.1 factory version which worked camera included. After a few days, I discovered your build and installed that, and tried to insttall kali on top which bricked it, and somehow I lost cameras before I reinstalled your version prior to the current one. The current one I flashed yesterday in a final attempt to get cams running, so its probably not to do with the latest build at all, but some error I have made.
I hve attached full files, I hope this gives you a better understanding, many thanks. Sorry I couldnt seem to attach a a file

I may not have applied firmware as specified, and have not intentionally altered any OS files.
Let's do a test:
Please reboot to TWRP and make a full backup. To be on the safe side, copy afterwards the complete content of your "Internal Memory" (which includes the TWRP backup) to your PC (be patient, this may take a while). So you have now a backup allowing you to go back to your current state.

When done, please do a 'factory reset' (this should normally leave out your Internal Memory, but we want to be on the safe side) and then also wipe the /system partition.
Now, install my latest ROM again, confirm to wipe cache & dalvik, and reboot. Does the Camera work now on the 'naked' freshly installed ROM ?

I assume, the answer would be 'yes', but I would like to have a confirmation. Based on this, we can discuss the next steps. In fact, if it is OK for you to simply continue from here and re-install your apps one by one, that would be the cleanest way forward. If you however absolutely depend on getting certain apps restored, let me know - then it may become cumbersome, but we'll see...
 
  • Like
Reactions: thomasnsr

ozrocks

New member
Aug 12, 2022
3
1
OnePlus 3
Let's do a test:
Please reboot to TWRP and make a full backup. To be on the safe side, copy afterwards the complete content of your "Internal Memory" (which includes the TWRP backup) to your PC (be patient, this may take a while). So you have now a backup allowing you to go back to your current state.

When done, please do a 'factory reset' (this should normally leave out your Internal Memory, but we want to be on the safe side) and then also wipe the /system partition.
Now, install my latest ROM again, confirm to wipe cache & dalvik, and reboot. Does the Camera work now on the 'naked' freshly installed ROM ?

I assume, the answer would be 'yes', but I would like to have a confirmation. Based on this, we can discuss the next steps. In fact, if it is OK for you to simply continue from here and re-install your apps one by one, that would be the cleanest way forward. If you however absolutely depend on getting certain apps restored, let me know - then it may become cumbersome, but we'll see...
OK, I shall do this. I actually tried reflashing a clean os, but I did not do a backup and full reinstall. The result was that it still didnt work. I have been doing a bit of reading, and believe that the main issue is in the HAL3, as i downloaded the camera 2 api probe, and the results are here. This is my only phone/daily rider, so I shall when I can afford the possible downtime if I stuff it up !
 
Last edited:
  • Like
Reactions: thomasnsr
Volunteers wanted - Test build for 'sandboxed play services'

Hi all,

I have created (and also briefly tested myself) a test build of this ROM with an Android 11/LineageOS 18.1 port of GrapheneOS's Sandboxed Play services .

The test build - clean-flash strongly recommended - does not contain any microG app (but besides all other existing hardening measures and features of this ROM) and you would have to install the respective Google apps (GSF proxy, Play services and Play store) manually as ordinary apps - this means: NO FLASHING ANY ZIP, but manually installing the three apps as APK files or bundles. [You could either try to extract the APK files from a flashable Gapps ZIP (make sure to choose Android 11 and arm64) or to e.g. look at apkmirror.com - once again: DON'T flash any Gapps.zip!].

Whilst the current microG ROM offered in this thread mainly aims at users not really keen on using Google, but still providing a basic compatibility to many apps with G* dependencies without truly integrating with G* - this could become an option for those willing to use G* (and tolerating the known negative impacts), whilst not having to live with Google's infamous "kill switch" (factually allowing them to take over your device at any time and/or secretly replacing your installed apps with "crafted" ones) and ability to track you 24/7 (you however still choose to share information with them, don't ignore that fact!)

I would be interested to see, to what extent this approach is usable and whether this would be interesting for you as an offered 2nd build variant or not.

Your feedback is appreciated.
Thanks & regards - M.
 
Last edited:

davidlyerly

Member
Nov 5, 2021
16
11
Oh, is that? Didn't know that - what's the reason for such a legislation? Is that across US or specific to each state?


Thanks for the hint, however - I've built the apk from the new sources, but the phone didn't boot using this new apk. So far I have used the prebuilt apk from the /e/ OS fork - so for now continuing that path...
You don't know?? The US corrupt to the core bidens harryass regime has now made 3G phones (basically any gsm device) blocked by all networks in every state. If the phone is not a "4G VOLTE" built device, it will no longer work, PERIOD. What this means is that they are trying to force everyone to use a "modern" smartphone cucked by google (POS co). As google has slowly "fused" the radios to the OS's themselves. All that really means is that google (F google) is slowly but surely removing the ability to control the radios, and thus the actual hardware of the phones. Forcing everyone to use a "smartphone", which 99% of the population does not root, is yet one more example of the surveillance state creep. ALL new cars now have cellular radios and gps "fused" of course, and you can't shut it off.
Essentially forcing everyone to have a gps enabled tracking device they carry at all times and which then is used to further their slavery model. I don't use 5G anymore AT ALL. 2.4G ONLY. From what I understand 5G phones is a sham and doesn't exist. It's an excuse for people to trade up to the new device when really the threat itself are the 5G towers which are nothing less and nothing more than a military weapon. You can't see it, and they don't talk about the effects of the microwaving/beamforming lethality of the MASSIVE amount of energy the towers are capable of transmitting.
"US" and "FREEDOM" are 2 words that don't know each other at all. Especially when it comes to any electronic devices whatsoever.

I tossed the 7T in the trash as it was tmobile branded and I couldn't root it. The AGM phone I bought does not work with prepaid sims and I tossed that too. If I had kept it I would have had to pay 4x what I do now just to use it yearly. My mistake I should have checked the imei first. I will be running a pixel 4a (non 5g) next week with calyx os. After that? VOIP. Data plan sim card with a voip plan and the networks can all go screw themselves with their 4g/5g BS.

My 3t still works but it has problems. Can't update osmand maps ( I use my other sonim 7700), no front camera, no speaker phone, no call logs now, and it's generally hard to hear the other party. It will simply be a backup device should something happen to the pixel.
I refuse to be tracked and surveilled like a farm animal and I don't gas what that takes. I don't gaf if I have to use a payphone or only a landline. Don't GAF!
I'm pissed because of the time and money I have wasted on the **** networks here in the bidens harryas regime land. I'd kill that **** for free.
Thank you very much for your work. One plus has gone 5G only and is no longer a company I will do business with. Speaking of which, their unlock code webpage doesn't exist here in the US either. F oneplus. One minus. I will no longer be spending money or time to find out I wasted it. never again

I'd like to add that ANY dumphone you can buy here in the US has GPS. It's a fused feature c/o google and scumbags. Your life is simpler but now you really are using a tracking device that's attached to your your phone #.
 
Last edited:

davidlyerly

Member
Nov 5, 2021
16
11
If I understand you correctly the gms compat build is the graphene type build with sandboxing for google? I'd run graphene myself but his idea of security is to use multiple profiles for every application (banking, browsing, etc-though not required of course). Calyx, oth, has the option to install microg and has a built-in firewall (datura). In the interest of making my life simpler and not more complicated I chose calyx. I don't have to install afwall (? maybe) and microg is an option only.

As far as I can tell microg is good for push notifications, (totally unnecessary for basic txting which is what I do-no mms at all, and ties you to google) and the 'backends' it uses are also totally unnecessary for gps/osmand/magic earth. In essence microg is simply a more private version of gapps, that's it. USELESS. I 'uninstalled' microg on my oneplus 3t and my banking ap works fine. Microg is rather just bloat as is gapps, imho.
My twrp backup is now ~ a gig smaller when framework, core and fakestore is uninstalled. AND, now I don't have to enter my password at boot twice like I've been doing, which was weird to begin with. I only password the phone so I can fingerprint into pwsafe and my bank app. If it weren't for those two I wouldn't even bother. It's a rooted one+ 3t so even with a password anyone can flash over it and still use it jus fine.
I use fdroid classic only as aurora stopped working long ago and for some reason the official fdroid ap won't work either. The repos are sketchy as F too.
 
Last edited:
You don't know?? The US corrupt to the core bidens harryass regime has now made 3G phones (basically any gsm device) blocked by all networks in every state. If the phone is not a "4G VOLTE" built device, it will no longer work, PERIOD.
WTF...? Tbh, I wasn't too interested before, but this is really ****** - combined with the extremely disturbing and annoying fact, that it seems very difficult in the US to even obtain a phone with an unlockable BL (the way, they "brand" their devices to limit even the plans you can use is beyond any rationale) and also some kind of crap checks, that the big mobile operators seem to even perform kind of "compatibility checks" to even let your phone register in their network.

"US" and "FREEDOM" are 2 words that don't know each other at all. Especially when it comes to any electronic devices whatsoever.
Well, that sadly is true since a very long time across all the different administrations (I don't want to get too political, as this is a tech. forum here...)

I tossed the 7T in the trash as it was tmobile branded and I couldn't root it. The AGM phone I bought does not work with prepaid sims and I tossed that too.
See above :(

Thank you very much for your work. One plus has gone 5G only and is no longer a company I will do business with. Speaking of which, their unlock code webpage doesn't exist here in the US either. F oneplus. One minus. I will no longer be spending money or time to find out I wasted it. never again
Unlock code webpage??? I am not a OP product expert, but as far as I know, OP does not work with unlock codes at all (at least for my 3T and 7T Pro, there was no unlock code). fastboot oem unlock and my BL was unlocked. That's it.

I'd like to add that ANY dumphone you can buy here in the US has GPS. It's a fused feature c/o google and scumbags. Your life is simpler but now you really are using a tracking device that's attached to your your phone #.
:sick:
 
If I understand you correctly the gms compat build is the graphene type build with sandboxing for google? I'd run graphene myself but his idea of security is to use multiple profiles for every application (banking, browsing, etc-though not required of course).
correct

Calyx, oth, has the option to install microg and has a built-in firewall (datura). In the interest of making my life simpler and not more complicated I chose calyx. I don't have to install afwall (? maybe) and microg is an option only.
What I try to do with my ROMs heads to a similar direction like Calyx. Btw, same as with my ROM, Calyx comes with pre-installed microG and you would have to freeze the apps, if you don't want to use microG. No idea about FW in particular, but "vanilla" LineageOS comes already with a Firewall allowing to block internet for every single app. It's somehow hidden in each individual app setting, and in my ROM, there is a FW option as a front end to that functionality for all apps at one place.

As far as I can tell microg is good for push notifications, (totally unnecessary for basic txting which is what I do-no mms at all, and ties you to google) and the 'backends' it uses are also totally unnecessary for gps/osmand/magic earth. In essence microg is simply a more private version of gapps, that's it. USELESS. I 'uninstalled' microg on my oneplus 3t and my banking ap works fine. Microg is rather just bloat as is gapps, imho.
Yes and no: https://calyxos.org/docs/guide/microg/ explains quite well the concept. I would like to add, that there are many apps out there, which simply check for the presence of the Gapps crap without actually using it, so microG provides first hand a basic compatibility layer.

My twrp backup is now ~ a gig smaller when framework, core and fakestore is uninstalled. AND, now I don't have to enter my password at boot twice like I've been doing, which was weird to begin with. I only password the phone so I can fingerprint into pwsafe and my bank app. If it weren't for those two I wouldn't even bother. It's a rooted one+ 3t so even with a password anyone can flash over it and still use it jus fine.
That really sounds more than weird! Did you somehow "manage" to "upgrade" the microG stuff by installing the 'real' Gapps on top?

I use fdroid classic only as aurora stopped working long ago and for some reason the official fdroid ap won't work either. The repos are sketchy as F too.
Which version of Aurora are you using? Sounds also weird to me...
 
  • Like
Reactions: thomasnsr
Custom ROMs ready to be signed?
how do you sign it
To be precise, every ROM is 'signed' - however, the majority of Custom ROMs simply makes use of the default, which is the publicly known and available 'test keys' provided by Google. I have created my own signing keys and during the build process, the ROM is signed with these keys.

This has got in fact two consequences:
1. You can't "dirty-flash" my ROM over somebody else's ROM and you can't "dirty-flash" somebody else's ROM over my ROM (see OP)
2. All shipped apps are signed with that key, so you cannot "update" these apps by some random stuff coming from other builds using the "test keys"

May sound inconvenient at first, but believe me, that is more secure!
 
Last edited:
  • Like
Reactions: thomasnsr and khbd

davidlyerly

Member
Nov 5, 2021
16
11
I run afwall atm. It can block system aps which is a requirement for me in any firewall, as is root. Regardless, I will be using calyx os on a pixel 4a very soon-no microg. Any app that needs to 'check' for google crap in order to function will be removed. PERIOD.

As for aurora, it has worked and then not worked. I 'uninstalled' it long ago and every next rom revision does not work either. I don't gas. F aorora if it fails to login anonymously. Basically I think once you remove the service part it will never work again. Again, I do not care. Don't gaf. I use phones for calls, txts, and offline gps directions. If I happen to take a pic or not I could care less. And hell no gapps is not installed. I fell out of love for google before gmail was out of beta.

My entire home network's wifi is now 2,4G only, and that includes my personal devices. My roommate has a 5G phone but I did disable 5G on it. POS samsuck probably updated and reenabled it. Who knows. Not my problem.

It is insulting to think I might have installed gapps on a rooted 1+3t using your roms. Regardless, my main phone will be a rooted pixel 4a with calyx os from now on. No 'g' anything whatsoever, no backends that simply tell the networks where YOU are, no mozilla crap either. Like I need them for sqaut. F mozilla and their mitm checks. F em.
Thanks for your hard work. It has made a meh phone into something very useable for a very long time past it's prime.

Forget what I said about twrp backups being smaller w/o microg and fakestore. My first backup was but they are now back to 7+gb's. I'm so sick of playing googles "fused your **** how you like it now game" I could puke. google eats **** in hell for free
 
Last edited:

davidlyerly

Member
Nov 5, 2021
16
11
Just a little update, calyx is not a root friendly os and is full of crap I do not need. I run lineage 19.1 (12) now on my pixel 4a.

I just noticed the other day that google's "fuse" feature set is essentially combining your carrier services to your network manager using location services, both coarse AND fine, allowing them as default, and you can't switch it off even with root. I did not know this til recently as I just started using App Manager, a must have fdroid ap for a rooted device. Basically every single system process defaults to allowing both coarse and fine. "Network manager" controls everything, wifi, bt, gps, and your sim card settings themselves. The gps is the "fused" in the fuse updates. The reason why they forced everyone in the US to use a modern '4G' smartphone is so that they could essentially force updates (remote control it). I seriously doubt if a recent version of android even HAS the ability to disable the GPS at all. IMO, it is probably on at all times even when you think it's not.

If you put a sim in your device and then turn on gps you will be tracked. Personally I do not trust the settings menus at all when it comes to the gps chip. The chip is receive only, whereas your cellular radio is both transmit and receive and works entirely differently in both function and form. Both can operate independently of each other, just not in any recent versions of android including mse's.

For this reason I will now no longer EVER turn gps on in a device with a sim card. And conversely when using gps, I will never insert an active sim card. When I said I would be leaving my oneplus in my vehicle for navigation purposes I wasn't kidding. The days of cell tower triangulation are long fng gone. They will now know exactly where you are at all times AND where you've been and even the routes you took.

BTW, I also just realized once you update Magic Earth it no longer needs internet access whatsoever. Magic earth is a DB of coordinates overlayed on a 2D street map. Search works with no data whatsoever. Loving my pixel 4a and droid 12 does work very well, user wise, but the fuse bs has kind of made the modern smartphone a dead end here in the US.

What's hilarious is if you buy a pinephone thinking it's somehow different, oh how you would be wrong. POS gets fused updates just like regular android but the difference is you are running garbage hardware. The physical switch option to disable the radios? Total fng nonsense. You disable one you disable ALL. Useless BS. Never buy a pinephone ever. You will be tossing it where it belongs.
I post this as it deserves to be known by all.
 
  • Like
Reactions: MSe1969
New build with September 2022 ASB patches available

Hi all,
a new build with the September 2022 ASB patches is available for download and also offered by the Updater app:

  • Security string 2022-09-05
  • Bromite Browser and Webview updated to 104.0.5112.91
  • Kernel: Some patches and also hardening (GrpaheneOS patches)
  • microG 0.2.24.214816-30
  • Contacts app slightly 'de-Googled'
Happy flashing!
Regards, M.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    New build with September 2022 ASB patches available

    Hi all,
    a new build with the September 2022 ASB patches is available for download and also offered by the Updater app:

    • Security string 2022-09-05
    • Bromite Browser and Webview updated to 104.0.5112.91
    • Kernel: Some patches and also hardening (GrpaheneOS patches)
    • microG 0.2.24.214816-30
    • Contacts app slightly 'de-Googled'
    Happy flashing!
    Regards, M.
    3
    I run afwall atm. It can block system aps which is a requirement for me in any firewall, as is root. Regardless, I will be using calyx os on a pixel 4a very soon-no microg. Any app that needs to 'check' for google crap in order to function will be removed. PERIOD.

    As for aurora, it has worked and then not worked. I 'uninstalled' it long ago and every next rom revision does not work either. I don't gas. F aorora if it fails to login anonymously. Basically I think once you remove the service part it will never work again. Again, I do not care. Don't gaf. I use phones for calls, txts, and offline gps directions. If I happen to take a pic or not I could care less. And hell no gapps is not installed. I fell out of love for google before gmail was out of beta.

    My entire home network's wifi is now 2,4G only, and that includes my personal devices. My roommate has a 5G phone but I did disable 5G on it. POS samsuck probably updated and reenabled it. Who knows. Not my problem.

    It is insulting to think I might have installed gapps on a rooted 1+3t using your roms. Regardless, my main phone will be a rooted pixel 4a with calyx os from now on. No 'g' anything whatsoever, no backends that simply tell the networks where YOU are, no mozilla crap either. Like I need them for sqaut. F mozilla and their mitm checks. F em.
    Thanks for your hard work. It has made a meh phone into something very useable for a very long time past it's prime.

    Forget what I said about twrp backups being smaller w/o microg and fakestore. My first backup was but they are now back to 7+gb's. I'm so sick of playing googles "fused your **** how you like it now game" I could puke. google eats **** in hell for free
    2
    Custom ROMs ready to be signed?
    how do you sign it
    To be precise, every ROM is 'signed' - however, the majority of Custom ROMs simply makes use of the default, which is the publicly known and available 'test keys' provided by Google. I have created my own signing keys and during the build process, the ROM is signed with these keys.

    This has got in fact two consequences:
    1. You can't "dirty-flash" my ROM over somebody else's ROM and you can't "dirty-flash" somebody else's ROM over my ROM (see OP)
    2. All shipped apps are signed with that key, so you cannot "update" these apps by some random stuff coming from other builds using the "test keys"

    May sound inconvenient at first, but believe me, that is more secure!
    1
    If I understand you correctly the gms compat build is the graphene type build with sandboxing for google? I'd run graphene myself but his idea of security is to use multiple profiles for every application (banking, browsing, etc-though not required of course).
    correct

    Calyx, oth, has the option to install microg and has a built-in firewall (datura). In the interest of making my life simpler and not more complicated I chose calyx. I don't have to install afwall (? maybe) and microg is an option only.
    What I try to do with my ROMs heads to a similar direction like Calyx. Btw, same as with my ROM, Calyx comes with pre-installed microG and you would have to freeze the apps, if you don't want to use microG. No idea about FW in particular, but "vanilla" LineageOS comes already with a Firewall allowing to block internet for every single app. It's somehow hidden in each individual app setting, and in my ROM, there is a FW option as a front end to that functionality for all apps at one place.

    As far as I can tell microg is good for push notifications, (totally unnecessary for basic txting which is what I do-no mms at all, and ties you to google) and the 'backends' it uses are also totally unnecessary for gps/osmand/magic earth. In essence microg is simply a more private version of gapps, that's it. USELESS. I 'uninstalled' microg on my oneplus 3t and my banking ap works fine. Microg is rather just bloat as is gapps, imho.
    Yes and no: https://calyxos.org/docs/guide/microg/ explains quite well the concept. I would like to add, that there are many apps out there, which simply check for the presence of the Gapps crap without actually using it, so microG provides first hand a basic compatibility layer.

    My twrp backup is now ~ a gig smaller when framework, core and fakestore is uninstalled. AND, now I don't have to enter my password at boot twice like I've been doing, which was weird to begin with. I only password the phone so I can fingerprint into pwsafe and my bank app. If it weren't for those two I wouldn't even bother. It's a rooted one+ 3t so even with a password anyone can flash over it and still use it jus fine.
    That really sounds more than weird! Did you somehow "manage" to "upgrade" the microG stuff by installing the 'real' Gapps on top?

    I use fdroid classic only as aurora stopped working long ago and for some reason the official fdroid ap won't work either. The repos are sketchy as F too.
    Which version of Aurora are you using? Sounds also weird to me...
    1
    Just a little update, calyx is not a root friendly os and is full of crap I do not need. I run lineage 19.1 (12) now on my pixel 4a.

    I just noticed the other day that google's "fuse" feature set is essentially combining your carrier services to your network manager using location services, both coarse AND fine, allowing them as default, and you can't switch it off even with root. I did not know this til recently as I just started using App Manager, a must have fdroid ap for a rooted device. Basically every single system process defaults to allowing both coarse and fine. "Network manager" controls everything, wifi, bt, gps, and your sim card settings themselves. The gps is the "fused" in the fuse updates. The reason why they forced everyone in the US to use a modern '4G' smartphone is so that they could essentially force updates (remote control it). I seriously doubt if a recent version of android even HAS the ability to disable the GPS at all. IMO, it is probably on at all times even when you think it's not.

    If you put a sim in your device and then turn on gps you will be tracked. Personally I do not trust the settings menus at all when it comes to the gps chip. The chip is receive only, whereas your cellular radio is both transmit and receive and works entirely differently in both function and form. Both can operate independently of each other, just not in any recent versions of android including mse's.

    For this reason I will now no longer EVER turn gps on in a device with a sim card. And conversely when using gps, I will never insert an active sim card. When I said I would be leaving my oneplus in my vehicle for navigation purposes I wasn't kidding. The days of cell tower triangulation are long fng gone. They will now know exactly where you are at all times AND where you've been and even the routes you took.

    BTW, I also just realized once you update Magic Earth it no longer needs internet access whatsoever. Magic earth is a DB of coordinates overlayed on a 2D street map. Search works with no data whatsoever. Loving my pixel 4a and droid 12 does work very well, user wise, but the fuse bs has kind of made the modern smartphone a dead end here in the US.

    What's hilarious is if you buy a pinephone thinking it's somehow different, oh how you would be wrong. POS gets fused updates just like regular android but the difference is you are running garbage hardware. The physical switch option to disable the radios? Total fng nonsense. You disable one you disable ALL. Useless BS. Never buy a pinephone ever. You will be tossing it where it belongs.
    I post this as it deserves to be known by all.
  • 17
    This thread is dedicated to provide hardened Lineage-OS 18.1 builds with microG included for the OnePlus 3/3T with current security patches.

    It is the successor of my Lineage 17.1 thread.
    It may be worth to also look there, if you are looking for information.

    Download here

    Features of this ROM

    • Pre-installed microG like LineageOS for microG project (own fork)
    • Pre-installed AuroraStore, AuroraDroid and AuroraServices
    • OTA Support
    • eSpeakTTS engine
    • Bromite as default browser
    • Additional security hardening features listed below:
    • Cloudflare as default DNS (instead of Google)
    • Privacy-preferred default settings
    • Optional blocking of Facebook- and Google-Tracking (Settings - Network & Internet)
    • Optional disable captive portal detection or choose from various providers (default is GrapheneOS and not Google; Settings - Network & Internet)
    • Firewall UI (under Trust)
    • Increased max. password length of 64
    • No submission of IMSI/phone number to Google when GPS is in use
    • Default hosts file with many blocked ad/tracking sites
    • Privacy-enhanced Bromite SystemWebView
    • Extra control of sensor access for additionally installed user apps (Special access under app permissions)
    • Kernel kept up to date with ASB patches of Google kernel/common 'android-4.14-q-release' branch
    • Debloated from Oneplus blobs for Soter and IFAA
    • Hardened bionic lib and constified JNI method tables
    • Option to only use fingerprint unlock for apps and not for the device
    • Optional timeout for Bluetooth and WLAN connections
    • Per connection WiFi randomization option


    Current release levels

    Security string: 2022-09-05
    AOSP tag: 11.0.0_r46
    Bromite Browser and System Webview: M104

    Source-code and build instructions

    Kernel: https://github.com/lin18-microg/android_kernel_oneplus_msm8996/tree/lin-18.1-mse3
    Build manifest: https://github.com/lin18-microg/local_manifests/tree/lin-18.1-hmalloc


    Installation Instructions​


    YOU ARE RESPONSIBLE SOLELY YOURSELF FOR ANY ACTIONS YOU DO WITH YOUR DEVICE !!!

    Please note - I won't explain any single aspect (e.g. how to install 'fastboot' on your PC or troubleshoot USB connectivity issues under Windows). Search the net and consult the search engine of your choice or look here in XDA, there is plenty of information available.

    Pre-Requisites

    • If you come from OxygenOS Stock ROM, make sure to update to the latest offered software version (if not, no issue).
    • Have fastboot and adb installed on your PC and make sure, you can connect via USB to your device in fastboot mode and via adb
    • An unlocked bootloader (see e.g. LineageOS install instructions)
    • OxygenOS 9.0.6 firmware, which is needed for LineageOS 18.1 - see next section
    • Download the most current .ZIP file of the ROM and place it to your phone's internal memory

    OxygenOS 9.0.6 Firmware

    If you come from my LineageOS 17.1 build - or any Android 10 based ROM, you most probably have already the proper firmware.
    And yes, LineageOS 18.1 is Android 11, but the latest firmware for this device has been published by Oneplus for Android 9.
    How to find out about your current firmware, if you use a Custom ROM:
    Connect as root via adb to your phone and enter the command adb shell cat /system/vendor/firmware_mnt/verinfo | grep Time_Stamp
    If the result is "Time_Stamp": "2019-11-04 21:25:29", you are on the latest firmware, if the date/time is earlier, you need to update the firmware. THIS THREAD has got more information for you.
    If you come from an Oreo (Android 8.x) Custom ROM, READ THE OP OF THIS THREAD CAREFULLY !
    I can't explain it better and I am not going to repeat or summarize this. It really is in your interest to carefully read it - you have been notified and warned. Please also pay attention to the last section named "Alipay, WeChatpay, Soter and IFAA" - I strongly recommend to use the debloated firmware.


    Install TWRP recovery

    If you come from stock ROM and have just unlocked your boot loader, this is the next thing to do. I recommend to use the TWRP recovery for the OnePlus 3/3T. The following instructions are based on TWRP.
    To install TWRP, download the twrp-x.x.x-x-oneplus3.img file (Note: replace "x.x.x-x" in the following instructions with the respective values from the real file name) to your PC, connect the phone via USB to your PC, get it into 'fastboot mode' and enter the following command on your PC:
    Code:
    fastboot flash recovery twrp-x.x.x-x-oneplus3.img
    Afterwards, directly boot into 'recovery mode' (enter fastboot reboot on your PC and hold Power and vol.down) - DO NOT boot into the phone's Android system after having flashed TWRP! Once TWRP has been launched, you may decide to reboot your phone and install the ROM at any time later. But the first boot after flashing TWRP must be TWRP in recovery mode.

    Advanced Wipe

    ONLY perform the steps described here, if you come from Stock ROM or a different Custom ROM![/B]
    Boot into recovery mode. In TWRP, choose "Wipe", "Advanced" and specify "Dalvik", "System", "Cache" and "Data" to be wiped. Make sure NOT to wipe "Internal memory". Swipe to confirm the deletion and get back into the main menu.

    DO NOT flash Gapps!
    This ROM comes with pre-installed microG. So don't attempt to flash Gapps.

    Install ROM

    In the TWRP main menu, choose "Install". A file manager appears to let you navigate to your internal memory (path /sdcard). Choose the .ZIP file of our ROM and swipe to flash.
    If you update from a previous version of my ROM, including my LineageOS 17.1 build, you don't need to perform a wipe. If you come from a different ROM (or stock firmware), make sure that you have performed the Wipe steps above.
    When finished flashing, return to the main menu, choose "Reboot" and then "System", which will cause your phone to boot into Lineage OS 18.1 - be patient, the first boot after flashing a new ROM takes quite long!


    Dealing with signed builds​

    Please note, that this builds is signed with an own key. When you come from a different build, you cannot directly "dirty-flash" this build. You have to perform a "clean flash" (recommended), or - you do this on your own risk - you may try the below steps.

    This happens at your own risk - make a backup with TWRP before!
    • Download and extract the file migration.sh from this archive
    • This file helps you to migrate from a build signed with the publicly available test keys (i.e. all builds around, which do not state that they are signed). If you come from another signed build (e.g. official LineageOS), you have to adapt the file accordingly (see below links).
    • boot into TWRP
    • push the migration.sh file to the directory /data/local on your device and mount the /system partition in TWRP (you can do so using the dedicated TWRP's menu entry)
    • launch the built-in terminal in TWRP, cd into /data/local, make migration.sh executable (chmod +x) and execute the command ./migration.sh official
    • (In case you receive an error, try sh ./migration.sh official instead)
    • flash the ROM .zip
    • wipe Cache and Dalvik/ART Cache
    • reboot system
    More background information and the "theory behind" can be found in the LineageOS wiki and AOSP reference.



    Why no Android 12 / LineageOS 19 build ?​

    The answer can be found here: https://lineageos.org/Changelog-26/ (section "Let’s talk about legacy devices…").

    Bug reports:

    If you have a problem, please create a post with these informations:
    Original Kernel shipped with this rom:
    Build Date:
    And try to get log as described here
    Please note that I can't and won't support issues with builds using a different kernel or Xposed.
    In regards to microG, I will try my best to help when it is related to this ROM (I use it myself), but any questions of the type "the YXZ-app can't do <some sort of fancy xyz Google functionality> properly" are better asked in the respective microG forums.


    Credits​

    AOSP project
    LineageOS project
    microG project
    Graphene OS project
    csagan5 (Bromite)
    WhyOrean (Aurora)
    nvertigo67 (for the modded 9.x firmware and for collaboration)
    SkewedZeppelin (Kernel patches)
    9
    Bugfix build
    Hi all, Bromite has released a version increment to incorporate an upstream fix, which could cause some misbehavior (actually in my OP7T thread, some people had issues). I have therefore decided to push a bugfix build, which will also be offered by the Updater app, having Bromite Webview and Browser on release 99.0.4844.58:

    8
    Change Log

    September 9th, 2022
    • Security string 2022-09-05
    • Bromite Browser and Webview updated to 104.0.5112.91
    • Kernel: Some patches and also hardening (GrpaheneOS patches)
    • microG 0.2.24.214816-30
    • Contacts app slightly 'de-Googled'
    August 6th, 2022
    • Security string 2022-08-05
    • Bromite Browser and Webview updated to 103.0.5060.140
    • Some kernel patches
    July 14th, 2022
    • Security string 2022-07-05
    • Some kernel patches

    June 15th, 2022
    • Security string 2022-06-05
    • Some kernel patches
    • Bromite Browser and Webview on 102.0.5005.96
    • microG updated to 0.2.24.214816-11

    May 9th, 2022
    • Security string 2022-05-05
    • Some kernel patches
    • Bromite Browser and Webview on 101.0.4951.53
    • microG updated to 0.2.24.214816-10
    • Mozilla Location provider on 1.5.0

    April 15th, 2022
    • Security string 2022-04-05
    • Some kernel patches
    • Bromite Browser and Webview on 100.0.4896.57

    March 15th, 2022
    • Bromite Browser and Webview on 99.0.4844.58 (bugfix build)

    March 12th, 2022
    • Security string 2022-03-05
    • Some kernel patches
    • Bromite Browser and Webview on 99.0.4844.55
    • microG 0.2.24.214816-2
    • AuroraStore 4.1.1

    Janaury 20th, 2020
    • Security string 2022-01-05
    • Some kernel patches
    • A couple of patches and fixes from LineageOS

    December 19th, 2021
    • Security string 2021-12-05
    • Bromite Webview and Browser on 96.0.4664.54
    • microG 0.22.214516-21

    November 13th, 2021
    • Security string 2021-11-05
    • Bromite Webview and Browser on 94.0.4606.109

    October 15th, 2021
    Initial build:
    • Security string 2021-10-01
    • AOSP tag 11.0.0_r46
    • Pre-installed microG (0.2.22.212658-2) like LineageOS for microG project (own fork)
    • Pre-installed AuroraStore (4.0.7), AuroraDroid (1.0.8) and AuroraServices (1.1.1)
    • OTA Support
    • eSpeakTTS engine
    • Bromite (93.0.4577.83) as default browser
    • Additional security hardening features listed below:
    • Cloudflare as default DNS (instead of Google)
    • Privacy-preferred default settings
    • Optional blocking of Facebook- and Google-Tracking (Settings - Network & Internet)
    • Optional disable captive portal detection or choose from various providers (default is GrapheneOS and not Google; Settings - Network & Internet)
    • Firewall UI (under Trust)
    • Increased max. password length of 64
    • No submission of IMSI/phone number to Google when GPS is in use
    • Default hosts file with many blocked ad/tracking sites
    • Privacy-enhanced Bromite SystemWebView (93.0.4577.83)
    • Extra control of sensor access for additionally installed user apps (Special access under app permissions)
    • Debloated from Oneplus blobs for Soter and IFAA
    • Hardened bionic lib and constified JNI method tables
    • Option to only use fingerprint unlock for apps and not for the device
    • Optional timeout for Bluetooth and WLAN connections
    • Per connection WiFi randomization option
    7
    New build with November 2021 ASB patches

    Hi all, a new build for the OP3(T) containing the November 2021 ASB patches has been released:

    The Updater app should soon indicate it to offer an OTA update.
    • Security string 2021-11-05
    • Bromite Webview and Browser on 94.0.4606.109
    • Some kernel patches
    Happy flashing,
    Regards, M.
    6
    New build with January 2022 ASB patches

    Hi all,
    a new build for the OP3(T) containing the January 2022 ASB patches has been released:

    The Updater app should already indicate to offer an OTA update.
    • Security string 2022-01-05
    • Some kernel patches
    • A couple of patches and fixes from LineageOS
    Happy flashing,
    Regards, M.

    EDIT: URL adapted, see next post