Related
I'm trying to troubleshoot a problem I'm having where my phone will randomly switch from vibrate to audio on. so that's my first problem, can someone help me analyze my log to determine what is causing it? it started after updating my kernel. the second thing is that i'm seeing a bunch of lines I don't recognize:
??? this gets repeated excessively.
08-16 19:54:02.741 D/RecurrenceProcessor( 2688): RRULE := FREQ=WEEKLY;WKST=MO;BYDAY=MO,TU,WE,TH,FR
why is TouchPal dialer crashing? I don't notice anything
08-16 19:54:45.348 W/ActivityManager( 1344): Scheduling restart of crashed service com.cootek.smartdialer/.SmartDialerService in 5000ms
08-16 19:54:50.365 I/ActivityManager( 1344): Start proc com.cootek.smartdialer for service com.cootek.smartdialer/.SmartDialerService: pid=19378 uid=10094 gids={1007, 1015, 3003}
what is this?
08-16 19:54:50.615 I/PROFILE ( 1344): Group: Gmail containing : com.android.systemui : false
08-16 19:54:50.615 I/PROFILE ( 1344): Group: Phone containing : com.android.systemui : false
08-16 19:54:50.615 I/PROFILE ( 1344): Group: Calendar containing : com.android.systemui : false
08-16 19:54:50.615 I/PROFILE ( 1344): Group: Email containing : com.android.systemui : false
08-16 19:54:50.615 I/PROFILE ( 1344): Group: SMS containing : com.android.systemui : false
08-16 19:54:50.615 V/ProfileManager( 1641): No active group, returning default: Other
08-16 19:54:50.615 V/AudioManager( 1641): shouldVibrate, group: Other mode: DEFAULT
1. What rom are you using?
2. What kernel were you trying to flash?
Sent from my Inspire 4G using XDA Premium App
dooyoo222 said:
1. What rom are you using?
2. What kernel were you trying to flash?
Sent from my Inspire 4G using XDA Premium App
Click to expand...
Click to collapse
1. cm7. unsure what nightly it corresponds to. the dev is alienmind over in the DHD forums.
2. lordmod 6.9
never had this issue with 6.8 and previous. I already reported to the kernel thread but i'm trying to dissect the issue myself.
Well I can't be much help since I don't use either of those two. Maybe try using the 6.8 kernel again and see what happens?
Sent from my Inspire 4G using XDA Premium App
This one is fun - I'm getting an FC every time an application requests keyboard input. If I hit the Google search icon on the top left of the home screen, it immediately FCs - that's what I'm using to test.
I downloaded aLogCat to the device via Google Play on my desktop, and ran it. Here is what I believe to be the relevant log section , from tapping the search icon, to re-entering aLogCat.
I believe the ClipboardEx service is causing the issue, possibly as an interference with another app I have installed - but I don't know what, or how to give you guys a list of apps installed without just typing each one.
This issue happened once to me, and a factory restore fixed it - two weeks later, and it's back. I'm not an experience Android guy, though I am a nerd and a developer. Surely this is something fixable. Does anyone have any thoughts on what could be causing this?
Code:
I/InputReader( 184): Touch event's action is 0x1 (deviceType=0) [pCnt=1, pending(waiting finished signal)=1, s=]
I/InputDispatcher( 184): Delivering touch to current input target: action: 0x1
I/InputDispatcher( 184): Delivering touch to current input target: action: 0x1
I/InputDispatcher( 184): Delivering touch to current input target: action: 0x1
I/ActivityManager( 184): START {intent.toShortString} from pid 383
D/PowerManagerService( 184): acquireDVFSLockLocked : type : DVFS_MIN_LIMIT frequency : 1008000 uid : 1000 pid : 184 tag : ActivityManager
W/ActivityManager( 184): mDVFSLock.acquire()
D/Launcher.HomeFragment( 383): onPause
D/Launcher( 383): onPause
V/TaskCloserActivity( 3234): TaskCloserActivity onReceive()
D/KeyguardViewMediator( 184): setHidden false
D/ActivityManager( 184): Trying to launch applicationName
D/ControlPanelRemoteService( 3246): onDestroy()
D/OpenGLRenderer( 383): Flushing caches (mode 1)
D/dalvikvm( 3157): GC_CONCURRENT freed 259K, 5% free 6784K/7111K, paused 2ms+3ms
D/KeyguardViewMediator( 184): setHidden false
D/STATUSBAR-StatusBarManagerService( 184): setSystemUiVisibility(0x0)
D/STATUSBAR-StatusBarManagerService( 184): manageDisableList what=0x0 pkg=WindowManager.LayoutParams
D/libEGL ( 3157): loaded /vendor/lib/egl/libEGL_POWERVR_SGX540_120.so
D/libEGL ( 3157): loaded /vendor/lib/egl/libGLESv1_CM_POWERVR_SGX540_120.so
D/libEGL ( 3157): loaded /vendor/lib/egl/libGLESv2_POWERVR_SGX540_120.so
D/OpenGLRenderer( 3157): Enabling debug mode 0
E/ClipboardServiceEx( 3157): Had failed to obtaining clipboardEx service.
D/AndroidRuntime( 3157): Shutting down VM
W/dalvikvm( 3157): threadid=1: thread exiting with uncaught exception (group=0x40bb01f8)
E/AndroidRuntime( 3157): FATAL EXCEPTION: main
E/AndroidRuntime( 3157): java.lang.NullPointerException
E/AndroidRuntime( 3157): at android.sec.clipboard.ClipboardExManager.updateData(ClipboardExManager.java:241)
E/AndroidRuntime( 3157): at android.widget.EditText.onFocusChanged(EditText.java:134)
E/AndroidRuntime( 3157): at android.view.View.handleFocusGainInternal(View.java:3727)
E/AndroidRuntime( 3157): at android.view.View.requestFocus(View.java:5420)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2110)
E/AndroidRuntime( 3157): at android.view.ViewGroup.onRequestFocusInDescendants(ViewGroup.java:2154)
E/AndroidRuntime( 3157): at android.view.ViewGroup.requestFocus(ViewGroup.java:2113)
E/AndroidRuntime( 3157): at android.view.View.requestFocus(View.java:5370)
E/AndroidRuntime( 3157): at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1598)
E/AndroidRuntime( 3157): at android.view.ViewRootImpl.handleMessage(ViewRootImpl.java:2459)
E/AndroidRuntime( 3157): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 3157): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 3157): at android.app.ActivityThread.main(ActivityThread.java:4514)
E/AndroidRuntime( 3157): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 3157): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 3157): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:790)
E/AndroidRuntime( 3157): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:557)
E/AndroidRuntime( 3157): at dalvik.system.NativeStart.main(Native Method)
W/ActivityManager( 184): Force finishing activity com.google.android.googlequicksearchbox/.SearchActivity
E/android.os.Debug( 184): [email protected] > dumpstate -k -t -n -z -d -o /data/log/dumpstate_app_error
I/dumpstate( 3272): begin
W/ActivityManager( 184): Activity pause timeout for ActivityRecord{423f3fe0 com.google.android.googlequicksearchbox/.SearchActivity}
W/PowerManagerService( 184): Timer 0x7->0x3|0x0
I/PowerManagerService( 184): Ulight 7->3|0
D/PowerManagerService( 184): setLightBrightness : mButtonLight : 0
E/lights ( 184): write_int failed to open /sys/class/sec/sec_touchkey/brightness
I/InputReader( 184): Touch event's action is 0x0 (deviceType=0) [pCnt=1, pending(waiting finished signal)=0, s=0.70 ]
E/lights ( 184): write_int failed to open /sys/class/sec/sec_touchkey/brightness
I/PowerManagerService( 184): Ulight 3->7|0
D/PowerManagerService( 184): setLightBrightness : mButtonLight : 140
I/InputReader( 184): Touch event's action is 0x1 (deviceType=0) [pCnt=1, pending(waiting finished signal)=0, s=]
D/VoldCmdListener( 89): asec list
D/VoldCmdListener( 89): CommandListener::AsecCmd::runCommand -> --
I/dumpstate( 3272): done
D/KeyguardViewMediator( 184): setHidden false
D/Launcher( 383): onResume
D/STATUSBAR-StatusBarManagerService( 184): setSystemUiVisibility(0x0)
D/STATUSBAR-StatusBarManagerService( 184): manageDisableList what=0x0 pkg=WindowManager.LayoutParams
D/myTest ( 383): [MonthTheme] onResume!!
D/KeyguardViewMediator( 184): setHidden false
D/myTest ( 383): firstDayOfWeek = -1
I/power ( 184): *** release_dvfs_lock : lockType : 1
D/myTest ( 383): [MonthView] updateView.mStartDay: 1
D/DEFERED_APP_VISIBILITY( 184): tweaking closing app
D/PowerManagerService( 184): releaseDVFSLockLocked : all DVFS_MIN_LIMIT are released
W/ActivityManager( 184): mDVFSLock.release()
D/Launcher.HomeFragment( 383): onResume
I've now removed all downloaded applications from my Tab. No dice.
I'm going to see if I can dig up any more logs, then reset it I guess.
I've discovered that copying something to the clipboard also causes the FC. This is definitely an issue with TouchWiz's clipboard as far as I can figure out.
Weird because I know I've copy pasted from the tab before
Sent from my SAMSUNG-SGH-I727 using xda premium
jamesd86 said:
Weird because I know I've copy pasted from the tab before
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
It works for me, too, until the whole thing starts crashing, lol.
I reset to factory and re-installed all my stuff; it seems to be working now. I guess it's Samsung's way of reminding me to keep regular backups...
My tab crashed and then this same exact thing started happening. The logs mentioned ClipboardServiceEx.
I am rooted, so I started an adb shell and found that /data/clipboard has all the persistent clipboard entries (I love that feature by the way).
I did this:
su
mv /data/clipboard /data/oldclipboard
mkdir /data/clipboard
chmod 775 /data/clipboard
chown system.system /data/clipboard
reboot
This fixed it, although it cleared all my "held" info in the clipboard. A small price to pay. If you really had to, you could probably fish in /data/oldclipboard for it. Of course, now I will go delete oldclipboard.
Hope that helps someone.
Thanks for that info, you never know!
Pp.
Transmitted from another galaxy with an Infected P-5113.
same thing happening to me. but i was prompted to update my device so i clicked yes thinking it would fix the problem now im stuck on the "use google location" page of the setup forms because when i click next i guess theres a keyboard involved so it crashes. only other button is a back arrow which does nothing.
i havent ever messed with this stuff but i guess ill have to find out how to factory reset through the usb cable.
unwanted pain in the butt
dorkmo said:
same thing happening to me. but i was prompted to update my device so i clicked yes thinking it would fix the problem now im stuck on the "use google location" page of the setup forms because when i click next i guess theres a keyboard involved so it crashes. only other button is a back arrow which does nothing.
i havent ever messed with this stuff but i guess ill have to find out how to factory reset through the usb cable.
unwanted pain in the butt
Click to expand...
Click to collapse
If you plan to root, just do that, boot into recovery, do an adb shell and clear the clipboard directory.
If you aren't going to install a custom recovery then yeah, wipe it out.
wd5gnr said:
If you plan to root, just do that, boot into recovery, do an adb shell and clear the clipboard directory.
If you aren't going to install a custom recovery then yeah, wipe it out.
Click to expand...
Click to collapse
ok newbie here with samsung tabs having same problem, how do you boot into recovery and do an adb shell ? can see above how to clear the clipboard directory and i dont want to factory reset too hard to reload all the crap on ....
thanks
I had the same problem, I do not want to root my device, but I like to use the standard key board from Sumsung. I send a a-mail to a lot of dutch companies (resellers) to tell them about the problem. I think that Sansung must make a firware update to solve this problem. I what to ask all people who have problems with the keyboard to e-mail Samsung and there reseller to put preasure on Samsung to make a firmware.
I use a work a round, I use a 3e party keyboard untill Samsung makes a firmware update.
wd5gnr said:
I did this:
su
mv /data/clipboard /data/oldclipboard
mkdir /data/clipboard
chmod 775 /data/clipboard
chown system.system /data/clipboard
reboot
Hope that helps someone.
Click to expand...
Click to collapse
YEZZZZZ THANK YOU VERY MUCH!!!:good::laugh:
This worked perfectly on my Samsung Galaxy Tab 2 10.1 (P5110)
Thanks wd5gnr for the solution, worked very well!
Regards.
Glad it helped. I noticed someone asked earlier for more details.
There are plenty of root tutorials here. As for installing ADB there are a few ways to go and it depends on your PC's OS and if you want to get someone's simplified package or not. Read: http://www.howtogeek.com/125769/how-to-install-and-use-abd-the-android-debug-bridge-utility/ and the comments on that page too. If you google something like "installing ADB" you should find lots of help.
Once you have adb installed and can get to a shell, you should be good with my earlier instructions.
It appears this is long-running problem plaguing N5's for some time. I saw sporadical "Can't connect to camera" on 5.0.1 but after update to 5.1 (I flashed the stock image) I literally cannot get the camera working for more than 1 unlock session.
I did have root but I thought it might be a problem so I unrooted and reflashed stock, but no help. The only other thing I can imagine to do is factory reset, but I have a few security apps that will need some time to be setup again (mostly banking and 2 factor stuff), plus I am not sure if I can restore data w/o Titanium using Google's new 'Restore', so I'm keeping the factory reset as last option.
Any ideas what I can do here? Is it happening to anyone else on 5.1? Can I somehow verify it's not a HW issue? (although, it was working on 5.0.1 so it's unlikely HW issue).
The only apps which *may* be accessing camera are Trusted face unlock, Whatsapp and Hangouts. Nothing special I'd say
Click to expand...
Click to collapse
Acknowledged bug by google https://code.google.com/p/android/issues/detail?id=160609
cthulu said:
It appears this is long-running problem plaguing N5's for some time. I saw sporadical "Can't connect to camera" on 5.0.1 but after update to 5.1 (I flashed the stock image) I literally cannot get the camera working for more than 1 unlock session.
I did have root but I thought it might be a problem so I unrooted and reflashed stock, but no help. The only other thing I can imagine to do is factory reset, but I have a few security apps that will need some time to be setup again (mostly banking and 2 factor stuff), plus I am not sure if I can restore data w/o Titanium using Google's new 'Restore', so I'm keeping the factory reset as last option.
Any ideas what I can do here? Is it happening to anyone else on 5.1? Can I somehow verify it's not a HW issue? (although, it was working on 5.0.1 so it's unlikely HW issue).
The only apps which *may* be accessing camera are Trusted face unlock, Whatsapp and Hangouts. Nothing special I'd say
Click to expand...
Click to collapse
If you reflashed factory image, you allready did a factory reset. Can you be more accurate with your description? Is this start immediately after first boot or later?
zagorteney said:
If you reflashed factory image, you allready did a factory reset. Can you be more accurate with your description? Is this start immediately after first boot or later?
Click to expand...
Click to collapse
I did reflash stock without wiping (to actually get the 5.1 upgrade - I didn't want to wait for OTA). If you wipe you start with clean phone, which I didn't want
So my problem manifests like this:
boot phone
camera seems to be working (opening camera app doesn't crash but actually allows taking pics)
after few screen locks/minutes, camera doesnt work anymore - opening camera either immediately crashes or shows "Can't connect to camera"
reboot fixes it for another few minutes
cthulu said:
I did reflash stock without wiping (to actually get the 5.1 upgrade - I didn't want to wait for OTA). If you wipe you start with clean phone, which I didn't want
So my problem manifests like this:
boot phone
camera seems to be working (opening camera app doesn't crash but actually allows taking pics)
after few screen locks/minutes, camera doesnt work anymore - opening camera either immediately crashes or shows "Can't connect to camera"
reboot fixes it for another few minutes
Click to expand...
Click to collapse
That's why i was asking this. Data partition can also cause problems. Flash completely and it will fix it.
zagorteney said:
That's why i was asking this. Data partition can also cause problems. Flash completely and it will fix it.
Click to expand...
Click to collapse
I also have this issue. I flashed 5.1 with the flash-all script, which did wipe my data. Any suggestions?
PHPanos said:
I also have this issue. I flashed 5.1 with the flash-all script, which did wipe my data. Any suggestions?
Click to expand...
Click to collapse
And this was happening immediately after booting your phone? Then must be hardware. ?
It works fine everytime I reboot, for xx minutes. It's difficult to say for how long but not too long. I see that "Trusted face" unlock stops working and that's a signal the whole camera subsystem is gone. Everything else works just no camera access from any app is possible.
zagorteney said:
And this was happening immediately after booting your phone? Then must be hardware. ��
Click to expand...
Click to collapse
No. It works at first. Then after a few times of locking/unlocking the phone and opening the camera app and switching to front camera it shuts down. The problem goes away after a reboot but it comes back again after a while.
cthulu: We have both the same problem.
Same here for me since upgrading to 5.0 every now and then i must reboot my phone in order to fix it.This is really annoying maybe we should wait for a new camera app by google ?
Same issue
Hi guys,
This has been the problem for me since 5.0 . I thought maybe its just me. But after a while, the camera stops working. I assume this is a s/w issue since the phone was fine in Kitkat. Even in 5.1 the issue persists.
I am also getting frequent "can't connect to camera" since 5.1. Nexus 5.
Do you know if there's an issue for this in Google's issue tracker? I'm sure they won't check xda forums for bug reports.
I've clicked a few times to send the error to Google when starting the camera but I honestly don't think they're checking those...
I hoped full wipe will fix this but as it happens to the folks who did full wipe I'm rather not going to do it yet...
Already reported here https://code.google.com/p/android/i... Owner Summary Stars&groupby=&sort=&id=160609
zagorteney said:
If you reflashed factory image, you allready did a factory reset. Can you be more accurate with your description? Is this start immediately after first boot or later?
Click to expand...
Click to collapse
Flashing system image does not mean factory reset. You can flash just the system and boot images without wiping data.
THRUSTer said:
Flashing system image does not mean factory reset. You can flash just the system and boot images without wiping data.
Click to expand...
Click to collapse
You are on a right direction. Just start to read a little more careful.
Happens the same for me.
Some days ago i see that the face Trusted face have Stop. So, now i desible the Trusted face, clear data of camera app e until now (about 2 hours) the camera works fine, without any shut up.
Try you too, i think that the problems are in the Smart lock.
Many people have this issue since they moved to 5.1
'Hardware defect' and 'no full wipe' were told to be the culprit straight away, but looking at the bug report that seems unjustified, especially given the number of reports with exactly this issue.
The issue arises when using face unlock. It somehow breaks the camera and the face unlock itself after a short while until you reboot it. I'm not sure if this happens with everyone or only with specific configurations, but for sure disabling face unlock has solved this for me.
zagorteney said:
Flash completely and it will fix it.
Click to expand...
Click to collapse
zagorteney said:
Then must be hardware. ?
Click to expand...
Click to collapse
So please be a bit more thorough in your advice....
Can't connect to camera error Nexus 5 Android 5.1
Hi gays, I am new here. I keep getting the ' can't connect to camera' error on my Nexus 5 Android 5.1, and I tried everything that is suggested here and it did not help. I turned off Face unlock, uninstall Viber and install again, cleared cache of the camera and force stop and everything else. Only help restart the device. I succeeded to catch the logcat with the error. Here is the logcat:
04-02 21:19:26.744 724-2687/? I/ActivityManager﹕ START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.GoogleCamera/com.android.camera.CameraLauncher bnds=[849,1532][1050,1784] (has extras)} from uid 10019 on display 0
04-02 21:19:26.747 724-2687/? V/WindowManager﹕ addAppToken: AppWindowToken{2498ae08 token=Token{83da7ab ActivityRecord{3a47c5fa u0 com.google.android.GoogleCamera/com.android.camera.CameraLauncher t32}}} to stack=1 task=32 at 0
04-02 21:19:26.751 724-819/? V/WindowManager﹕ Based on layer: Adding window Window{15bd6123 u0 Starting com.google.android.GoogleCamera} at 3 of 9
04-02 21:19:26.824 724-1360/? I/ActivityManager﹕ Start proc 22932:com.google.android.GoogleCamera/u0a42 for activity com.google.android.GoogleCamera/com.android.camera.CameraLauncher
04-02 21:19:26.837 1361-3270/? W/GsaThreadFactory﹕ Not creating another thread for Background Blocking because there are already 30
04-02 21:19:26.876 22932-22932/? W/ResourcesManager﹕ Asset path '/system/framework/com.google.android.camera2.jar' does not exist or contains no resources.
04-02 21:19:26.935 22932-22932/? W/CAM_Log﹕ Tag SessionStatsCollector is 2 chars longer than limit.
04-02 21:19:26.989 22932-22932/? I/CameraManagerGlobal﹕ getCameraService: Reconnecting to camera service
04-02 21:19:27.254 22932-22979/? I/CAM2PORT_AndCamAgntImp﹕ Opening camera 0 with camera1 API
04-02 21:19:27.266 193-1682/? W/AudioFlinger﹕ acquireAudioSessionId() unknown client 22932 for session 116
04-02 21:19:27.268 193-1682/? I/AwesomePlayer﹕ setDataSource_l(<no-scheme URI suppressed>)
04-02 21:19:27.289 193-1682/? W/AudioFlinger﹕ acquireAudioSessionId() unknown client 22932 for session 117
04-02 21:19:27.290 193-1682/? I/AwesomePlayer﹕ setDataSource_l(<no-scheme URI suppressed>)
04-02 21:19:27.301 193-1682/? I/Camera2ClientBase﹕ Camera 0: Opened. Client: com.google.android.GoogleCamera (PID 22932, UID 10042)
04-02 21:19:27.302 22932-22992/? W/CAM_PhotoData﹕ Zero dimension in ContentResolver for /storage/emulated/0/DCIM/Camera/IMG_20150402_180439.jpg:0x0
04-02 21:19:27.303 193-1682/? D/mm-camera-intf﹕ mm_camera_open: dev name = /dev/video1, cam_idx = 1
04-02 21:19:27.304 206-206/? I/mm-camera-sensor﹕ module_sensor_start_session:583 session 1
04-02 21:19:27.305 206-206/? E/mm-camera-sensor﹕ csiphy_open:126 VIDIOC_MSM_CSIPHY_IO_CFG failed
04-02 21:19:27.305 206-206/? E/mm-camera-sensor﹕ module_sensor_init_session:335 failed rc -1
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ sensor_close:2499 VIDIOC_MSM_SENSOR_CFG failed
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ module_sensor_init_session:500 failed
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ module_sensor_start_session:612 failed
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ module_sensor_start_session:617 failed
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ sensor_get_capabilities:1632 failed
04-02 21:19:27.306 206-206/? E/mm-camera-sensor﹕ module_sensor_query_mod:2421 failed rc -4
04-02 21:19:27.307 206-206/? E/mm-camera﹕ cpp_hardware_process_command:254: failed, subdev not opened
04-02 21:19:27.307 206-206/? E/mm-camera﹕ cpp_module_query_mod:268: failed
04-02 21:19:27.307 206-206/? E/mm-camera﹕ pproc_module_query_mod:1697] error in cpp query mod
04-02 21:19:27.307 206-206/? I/mm-camera-sensor﹕ module_module_set_session_data:2666 max delay 2 report dSelay 1
04-02 21:19:27.307 206-206/? E/mm-camera﹕ isp_set_session_data: Session could not be found!
04-02 21:19:27.307 206-206/? E/mm-camera﹕ cpp_module_get_params_for_session_id:178, failed, session_id=0x1
04-02 21:19:27.307 206-206/? E/mm-camera﹕ cpp_module_set_session_data:329, failed
04-02 21:19:27.307 206-206/? E/mm-camera﹕ pproc_module_set_session_data:1928] error in cpp set_session_data
04-02 21:19:27.307 206-206/? D/mm-camera﹕ module_faceproc_set_session_data:1836] Per frame control 2 1
04-02 21:19:27.307 206-206/? I/mm-camera-sensor﹕ module_sensor_stop_session:636 session 1
04-02 21:19:27.307 206-206/? E/mm-camera-sensor﹕ module_sensor_deinit_session:526 ref count 0
04-02 21:19:27.307 206-206/? E/mm-camera-sensor﹕ module_sensor_stop_session:664 failed
04-02 21:19:27.307 206-206/? E/mm-camera-sensor﹕ module_sensor_stop_session:669 failed
04-02 21:19:27.307 206-206/? I/mm-camera﹕ cpp_module_stop_session:462, info: stopping session 1 ...
04-02 21:19:27.307 206-206/? I/mm-camera﹕ cpp_module_stop_session:504, info: session 1 stopped.
04-02 21:19:27.307 206-206/? I/mm-camera﹕ c2d_module_stop_session:322, info: stopping session 1 ...
04-02 21:19:27.307 206-206/? I/mm-camera﹕ c2d_module_stop_session:361, info: session 1 stopped.
04-02 21:19:27.308 206-206/? E/mm-camera﹕ main: New session [1] creation failed with error
04-02 21:19:27.308 193-1682/? D/mm-camera-intf﹕ mm_camera_open: opened, break out while loop
04-02 21:19:27.308 193-1682/? E/mm-camera-intf﹕ mm_camera_open: cannot open control fd of '/dev/video1' (Bad address)
04-02 21:19:27.308 193-1682/? E/mm-camera-intf﹕ camera_open: mm_camera_open err = -1
04-02 21:19:27.308 193-1682/? E/QCamera3HWI﹕ camera_open failed.
04-02 21:19:27.308 193-1682/? E/Camera3-Device﹕ Camera 0: initialize: Could not open camera: No such device (-19)
04-02 21:19:27.308 193-1682/? E/Camera2ClientBase﹕ initialize: Camera 0: unable to initialize device: No such device (-19)
04-02 21:19:27.308 193-1682/? E/CameraService﹕ connectFinishUnsafe: Could not initialize client from HAL module.
04-02 21:19:27.308 193-1682/? I/Camera2Client﹕ Camera 0: Closed
04-02 21:19:27.309 193-1682/? I/Camera2ClientBase﹕ Closed Camera 0. Client was: com.google.android.GoogleCamera (PID 22932, UID 10042)
04-02 21:19:27.313 193-1682/? W/AudioFlinger﹕ session id 116 not found for pid 22932
04-02 21:19:27.317 193-1682/? W/AudioFlinger﹕ session id 117 not found for pid 22932
04-02 21:19:27.318 22932-22979/? W/CameraBase﹕ An error occurred while connecting to camera: 0
04-02 21:19:27.318 22932-22979/? E/CAM2PORT_AndCamAgntImp﹕ RuntimeException during CameraAction[OPEN_CAMERA] at CameraState[1]
java.lang.RuntimeException: Fail to connect to camera service
at android.hardware.Camera.<init>(Camera.java:497)
at android.hardware.Camera.open(Camera.java:342)
at com.android.ex.camera2.portability.AndroidCameraAgentImpl$CameraHandler.handleMessage(AndroidCameraAgentImpl.java:370)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.os.HandlerThread.run(HandlerThread.java:61)
04-02 21:19:27.371 22932-23015/? D/OpenGLRenderer﹕ Use EGL_SWAP_BEHAVIOR_PRESERVED: true
04-02 21:19:27.377 22932-22932/? D/Atlas﹕ Validating map...
04-02 21:19:27.381 724-1360/? V/WindowManager﹕ Adding window Window{312f9c81 u0 com.google.android.GoogleCamera/com.android.camera.CameraLauncher} at 3 of 10 (before Window{15bd6123 u0 Starting com.google.android.GoogleCamera})
04-02 21:19:27.387 22932-22932/? W/CAM_CameraActivity﹕ Camera open failure: HIST_ID0_-1_1_HEND
04-02 21:19:27.387 22932-22932/? E/CAM_Util﹕ Show fatal error dialog
04-02 21:19:27.402 724-2689/? V/WindowManager﹕ Adding window Window{302ae167 u0 com.google.android.GoogleCamera/com.android.camera.CameraLauncher} at 4 of 11 (before Window{15bd6123 u0 Starting com.google.android.GoogleCamera})
04-02 21:19:27.406 22932-22932/? D/WearableClient﹕ WearableClientImpl.onPostInitHandler: done
04-02 21:19:27.431 22932-23015/? I/Adreno-EGL﹕ <qeglDrvAPI_eglInitialize:379>: QUALCOMM Build: 01/14/15, ab0075f, Id3510ff6dc
04-02 21:19:27.432 22932-23015/? I/OpenGLRenderer﹕ Initialized EGL, version 1.4
04-02 21:19:27.444 22932-23015/? D/OpenGLRenderer﹕ Enabling debug mode 0
04-02 21:19:27.487 22932-22932/? I/CAM_UsageStats﹕ PlayLogger.onLoggerConnected
04-02 21:19:27.512 724-2689/? D/WifiService﹕ acquireWifiLockLocked: WifiLock{NlpWifiLock type=2 [email protected]}
04-02 21:19:27.516 22932-22932/? I/CAM_PhotoModule﹕ onPreviewUIReady
04-02 21:19:27.516 22932-22932/? I/CAM_PhotoModule﹕ attempted to start preview before camera device
04-02 21:19:27.518 724-851/? E/WifiStateMachine﹕ WifiStateMachine CMD_START_SCAN source 10007 txSuccessRate=0.00 rxSuccessRate=0.00 targetRoamBSSID=10:fe:ed:4e:a3:ae RSSI=-47
04-02 21:19:27.574 724-819/? I/ActivityManager﹕ Displayed com.google.android.GoogleCamera/com.android.camera.CameraLauncher: +790ms
Please HELP, it's really annoying
Best regards.
meranto said:
The issue arises when using face unlock. It somehow breaks the camera and the face unlock itself after a short while until you reboot it. I'm not sure if this happens with everyone or only with specific configurations, but for sure disabling face unlock has solved this for me.
So please be a bit more thorough in your advice....
Click to expand...
Click to collapse
Nope..
https://code.google.com/p/android/i... Owner Summary Stars&groupby=&sort=&id=160609
has a lot of people who didn't use face unlock and still experienced the issue.
Replay
Hi meranto,
thanks for the replay. I did not use face unlock and the issue still show up
The All-In-One thread for Ground Zero ROMs - GZOSP 10.0 and Validus 10.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
@sparx: Bullhead Maintainer
@Char_G: Public Relations and Thread Maintainer
@scoobyjenkins: Graphics and Thread Maintainer
About the ROMs :
Validus is GZOSP based with a Clown theme and has a lot of features.
GZR Tapatalk Group
here
TBO apps
here
GZR Custom Mods & Extras
here
Installation Instructions
ALWAYS MAKE A NANDROID BACKUP FIRST!
Coming from another rom/clean install:
Reboot to recovery, flash required firmware
Wipe system, cache,, data
Flash rom zip and gapps
Reboot
Updating from a previous build/dirty flash:
Wipe system, cache in recovery
Flash rom zip, gapps and any other zips you may use
Reboot
Never dirty flash from one rom to another
Builds are rootless, so to be rooted, flash your SU of choice
If you have any issues, grab a log after a clean flash, upload and link here please. Add steps to reproduce the issue in your post.
Do not report issues dirty flashing this over some unofficial build or with some kernel flashed.
Logcat Extreme app is great as you can choose to start recording a log just before reproducing an error and stop recording just after so you log just the part you need.
Xposed is not supported here, if you want to run it and have issues, try an Xposed thread for support and bug reports here only welcome with a clean install with no Xposed present.
Make sure to state which rom you are running when asking for support
Open Gapps
here
GZOSP AIO Thread
here
Downloads
GZOSP :
Build 03/15 (10.0) (Stable)
--> Get GZOSP here
Validus :
Build 08/23 (10.0) (Stable)
--> Get Validus here
GZR Telegram Updates Channel
here
Source Code:
https://github.com/ValidusOs
https://github.com/ValidusOs-devices
https://github.com/GZR-Kernels
https://github.com/BigTopKrazies
XDA:DevDB Information
Ground Zero Roms, ROM for the LG Nexus 5X
Contributors
scoobyjenkins, sparx, Char_G
Source Code: https://github.com/GZOSP
ROM OS Version: Android 10
ROM Kernel: Linux 3.10.x
Based On: GZOSP
Version Information
Status: Stable
Created 2020-01-02
Last Updated 2020-08-24
Reserved
Reserved #2
We're back!! Nice job @scoobyjenkins!!
Hi, thx for your hard working, the ROM is good.
I found some minor issues:
- System time does not synchronized with the internet.
- First time opening the wifi preferences page leads an ANR of system, please see the attachment.
imknown said:
Hi, thx for your hard working, the ROM is good.
I found some minor issues:
- System time does not synchronized with the internet.
- First time opening the wifi preferences page leads an ANR of system, please see the attachment.
Click to expand...
Click to collapse
Thanks for the info, I'm not suffering from either of those issues and can't recreate...I'll keep trying :good:
sparx said:
Thanks for the info, I'm not suffering from either of those issues and can't recreate...I'll keep trying :good:
Click to expand...
Click to collapse
Yes, strange. I met the second issue only once when first time booting up.
The first issue about datetime I can reproduct it here. Here is the logcat.
Code:
--------- beginning of main
01-03 15:49:43.433 892 1260 D SntpClient: request time failed: java.net.SocketTimeoutException: Poll timed out
--------- beginning of system
01-03 15:49:45.624 892 910 W LocalDisplayAdapter: Unable to find color mode 0, ignoring request.
01-03 15:49:45.661 12195 12195 D DashboardFragment: Cannot find preference with key system_update_settings in Controller SystemUpdatePreferenceController
01-03 15:49:45.669 12195 21224 W TileUtils: Found com.android.settings.Settings$DataUsageSummaryActivity for intent Intent { act=com.android.settings.action.SETTINGS pkg=com.android.settings } missing metadata com.android.settings.category
01-03 15:49:45.696 12195 22101 D SettingsActivity: No enabled state changed, skipping updateCategory call
01-03 15:49:45.729 12195 22102 D SummaryLoader: No fragment specified for ComponentInfo{com.android.settings/com.android.settings.backup.UserBackupSettingsActivity}
01-03 15:49:45.778 1157 1170 I ndroid.systemu: NativeAlloc concurrent copying GC freed 8212(493KB) AllocSpace objects, 0(0B) LOS objects, 49% free, 14MB/28MB, paused 163us total 146.403ms
01-03 15:49:45.953 892 892 V SettingsProvider: Notifying for 0: content://settings/system/screen_brightness
01-03 15:49:45.975 335 335 I hwservicemanager: getTransport: Cannot find entry [email protected]::ILight/default in either framework or device manifest.
01-03 15:49:46.174 335 335 I chatty : uid=1000(system) hwservicemanage identical 12 lines
01-03 15:49:46.190 335 335 I hwservicemanager: getTransport: Cannot find entry [email protected]::ILight/default in either framework or device manifest.
01-03 15:49:46.202 1354 21936 D DhcpClient: Received packet: 1c:1b:0d:6d:db:1a ACK: your new IP /0.0.0.0, netmask /255.255.248.0, gateways [/10.20.0.1] DNS servers: /10.20.0.152 /10.20.0.144 , lease time null
01-03 15:49:46.206 335 335 I hwservicemanager: getTransport: Cannot find entry [email protected]::ILight/default in either framework or device manifest.
01-03 15:49:49.202 892 3895 E TaskPersister: File error accessing recents directory (directory doesn't exist?).
01-03 15:49:49.237 892 909 I ActivityTaskManager: START u0 {act=android.intent.action.MAIN cmp=com.android.settings/.SubSettings (has extras)} from uid 1000
01-03 15:49:46.521 335 335 I chatty : uid=1000(system) hwservicemanage identical 19 lines
01-03 15:49:46.538 335 335 I hwservicemanager: getTransport: Cannot find entry [email protected]::ILight/default in either framework or device manifest.
01-03 15:49:49.266 12195 12195 W ActivityThread: handleWindowVisibility: no activity for token [email protected]
01-03 15:49:49.283 12195 12195 D SettingsActivity: Starting onCreate
01-03 15:49:49.319 12195 12195 D SettingsActivity: Starting to set activity title
01-03 15:49:49.320 12195 12195 D SettingsActivity: Done setting title
01-03 15:49:49.320 12195 12195 D SettingsActivity: Switching to fragment com.android.settings.DateTimeSettings
01-03 15:49:49.320 12195 12195 D SubSettings: Launching fragment com.android.settings.DateTimeSettings
01-03 15:49:49.330 12195 12195 D DateTimeSettings: NO dashboard tiles for DateTimeSettings
01-03 15:49:49.330 12195 12195 D DateTimeSettings: All preferences added, reporting fully drawn
01-03 15:49:49.332 12195 12195 D SettingsActivity: Executed frag manager pendingTransactions
01-03 15:49:49.349 12195 21224 W TileUtils: Found com.android.settings.Settings$DataUsageSummaryActivity for intent Intent { act=com.android.settings.action.SETTINGS pkg=com.android.settings } missing metadata com.android.settings.category
01-03 15:49:49.362 12195 22113 D SettingsActivity: No enabled state changed, skipping updateCategory call
01-03 15:49:50.311 892 892 V SettingsProvider: Notifying for 0: content://settings/global/auto_time
01-03 15:49:50.315 538 22121 E ResolverController: No valid NAT64 prefix (109, <unspecified>/0)
01-03 15:49:52.041 559 559 W wificond: Failed to get NL80211_ATTR_EXT_FEATURES
01-03 15:49:52.046 559 559 I chatty : uid=1010(wifi) /system/bin/wificond identical 1 line
01-03 15:49:52.049 559 559 W wificond: Failed to get NL80211_ATTR_EXT_FEATURES
01-03 15:49:52.853 892 3895 E TaskPersister: File error accessing recents directory (directory doesn't exist?).
01-03 15:49:55.329 892 1260 D SntpClient: request time failed: java.net.SocketTimeoutException: Poll timed out
imknown said:
Yes, strange. I met the second issue only once when first time booting up.
The first issue about datetime I can reproduct it here. Here is the logcat.
Code:
--------- beginning of main
01-03 15:49:43.433 892 1260 D SntpClient: request time failed: java.net.SocketTimeoutException: Poll timed out
--------- beginning of system
01-03 15:49:45.624 892 910 W LocalDisplayAdapter: Unable to find color mode 0, ignoring request.
01-03 15:49:45.661 12195 12195 D DashboardFragment: Cannot find preference with key system_update_settings in Controller SystemUpdatePreferenceController
01-03 15:49:45.669 12195 21224 W TileUtils: Found com.android.settings.Settings$DataUsageSummaryActivity for intent Intent { act=com.android.settings.action.SETTINGS pkg=com.android.settings } missing metadata com.android.settings.category
01-03 15:49:45.696 12195 22101 D SettingsActivity: No enabled state changed, skipping updateCategory call
01-03 15:49:45.729 12195 22102 D SummaryLoader: No fragment specified for ComponentInfo{com.android.settings/com.android.settings.backup.UserBackupSettingsActivity}
01-03 15:49:45.778 1157 1170 I ndroid.systemu: NativeAlloc concurrent copying GC freed 8212(493KB) AllocSpace objects, 0(0B) LOS objects, 49% free, 14MB/28MB, paused 163us total 146.403ms
01-03 15:49:45.953 892 892 V SettingsProvider: Notifying for 0: content://settings/system/screen_brightness
01-03 15:49:45.975 335 335 I hwservicemanager: getTransport: Cannot find entry [email protected]::ILight/default in either framework or device manifest.
01-03 15:49:46.174 335 335 I chatty : uid=1000(system) hwservicemanage identical 12 lines
01-03 15:49:46.190 335 335 I hwservicemanager: getTransport: Cannot find entry [email protected]::ILight/default in either framework or device manifest.
01-03 15:49:46.202 1354 21936 D DhcpClient: Received packet: 1c:1b:0d:6d:db:1a ACK: your new IP /0.0.0.0, netmask /255.255.248.0, gateways [/10.20.0.1] DNS servers: /10.20.0.152 /10.20.0.144 , lease time null
01-03 15:49:46.206 335 335 I hwservicemanager: getTransport: Cannot find entry [email protected]::ILight/default in either framework or device manifest.
01-03 15:49:49.202 892 3895 E TaskPersister: File error accessing recents directory (directory doesn't exist?).
01-03 15:49:49.237 892 909 I ActivityTaskManager: START u0 {act=android.intent.action.MAIN cmp=com.android.settings/.SubSettings (has extras)} from uid 1000
01-03 15:49:46.521 335 335 I chatty : uid=1000(system) hwservicemanage identical 19 lines
01-03 15:49:46.538 335 335 I hwservicemanager: getTransport: Cannot find entry [email protected]::ILight/default in either framework or device manifest.
01-03 15:49:49.266 12195 12195 W ActivityThread: handleWindowVisibility: no activity for token [email protected]
01-03 15:49:49.283 12195 12195 D SettingsActivity: Starting onCreate
01-03 15:49:49.319 12195 12195 D SettingsActivity: Starting to set activity title
01-03 15:49:49.320 12195 12195 D SettingsActivity: Done setting title
01-03 15:49:49.320 12195 12195 D SettingsActivity: Switching to fragment com.android.settings.DateTimeSettings
01-03 15:49:49.320 12195 12195 D SubSettings: Launching fragment com.android.settings.DateTimeSettings
01-03 15:49:49.330 12195 12195 D DateTimeSettings: NO dashboard tiles for DateTimeSettings
01-03 15:49:49.330 12195 12195 D DateTimeSettings: All preferences added, reporting fully drawn
01-03 15:49:49.332 12195 12195 D SettingsActivity: Executed frag manager pendingTransactions
01-03 15:49:49.349 12195 21224 W TileUtils: Found com.android.settings.Settings$DataUsageSummaryActivity for intent Intent { act=com.android.settings.action.SETTINGS pkg=com.android.settings } missing metadata com.android.settings.category
01-03 15:49:49.362 12195 22113 D SettingsActivity: No enabled state changed, skipping updateCategory call
01-03 15:49:50.311 892 892 V SettingsProvider: Notifying for 0: content://settings/global/auto_time
01-03 15:49:50.315 538 22121 E ResolverController: No valid NAT64 prefix (109, <unspecified>/0)
01-03 15:49:52.041 559 559 W wificond: Failed to get NL80211_ATTR_EXT_FEATURES
01-03 15:49:52.046 559 559 I chatty : uid=1010(wifi) /system/bin/wificond identical 1 line
01-03 15:49:52.049 559 559 W wificond: Failed to get NL80211_ATTR_EXT_FEATURES
01-03 15:49:52.853 892 3895 E TaskPersister: File error accessing recents directory (directory doesn't exist?).
01-03 15:49:55.329 892 1260 D SntpClient: request time failed: java.net.SocketTimeoutException: Poll timed out
Click to expand...
Click to collapse
Thanks dude - been a while since I've seen a properly reported issue
I don’t have sound in wired headphones when talking on the phone (aosp dialer, google dialer)
pincher65 said:
I don’t have sound in wired headphones when talking on the phone (aosp dialer, google dialer)
Click to expand...
Click to collapse
I'll check it out
---------- Post added at 02:39 PM ---------- Previous post was at 01:47 PM ----------
pincher65 said:
I don’t have sound in wired headphones when talking on the phone (aosp dialer, google dialer)
Click to expand...
Click to collapse
Plugged in my wired headphones - works perfectly!
sparx said:
I'll check it out
---------- Post added at 02:39 PM ---------- Previous post was at 01:47 PM ----------
Plugged in my wired headphones - works perfectly!
Click to expand...
Click to collapse
the music works, the sound of pressing the buttons is there, but the voices are not heard.
only possible with me. flash clean
pincher65 said:
the music works, the sound of pressing the buttons is there, but the voices are not heard.
only possible with me. flash clean
Click to expand...
Click to collapse
Do you mean headphones or a proper hands free head set with built-in microphone?
Headphones worked perfectly for me during a call, I don't own a head set...
GZOSP & Validus 10.0 builds in the OP,
GZOSP: Fixed hotspot, raised volumes, other fixes/stuffses
Validus: Initial release, all gzosp fixes plus extra stuffses
scoobyjenkins said:
GZOSP & Validus 10.0 builds in the OP,
GZOSP: Fixed hotspot, raised volumes, other fixes/stuffses
Validus: Initial release, all gzosp fixes plus extra stuffses
Click to expand...
Click to collapse
Thanks Scoobs
Encryption and SELinux
Thanks for creating this ROM. Does this ROM support device encryption? Is SElinux enforcing?
Rahulmsinghvi said:
Thanks for creating this ROM. Does this ROM support device encryption? Is SElinux enforcing?
Click to expand...
Click to collapse
No encryption and not enforcing...
scoobyjenkins said:
GZOSP & Validus 10.0 builds in the OP,
GZOSP: Fixed hotspot, raised volumes, other fixes/stuffses
Validus: Initial release, all gzosp fixes plus extra stuffses
Click to expand...
Click to collapse
the sound of a voice in a wired headset appeared in both ROMs.
Validus (clean installation):
If you flash openengapps immediately (with a reboot in recovery), then it is impossible to connect to Wifi. First installed ROM, booted into the system, turned on Wifi, then flashed the gapps. When installing apps from the market, only 9 was downloaded and then froze. When you press the power button and try to boot from its menu in recovery, the phone also freezes.
A clean flash of GCOSP did not cause problems, while everything is working. I'll try all day tomorrow.
for some reason I can’t install the Pixel Launcher 10, only 7.1 works.
Thank you your work.
the test failed. Chrome does not work, applications constantly freeze, even a gps test.
as a daily rum I do not advise
pincher65 said:
the sound of a voice in a wired headset appeared in both ROMs.
Validus (clean installation):
If you flash openengapps immediately (with a reboot in recovery), then it is impossible to connect to Wifi. First installed ROM, booted into the system, turned on Wifi, then flashed the gapps. When installing apps from the market, only 9 was downloaded and then froze. When you press the power button and try to boot from its menu in recovery, the phone also freezes.
A clean flash of GCOSP did not cause problems, while everything is working. I'll try all day tomorrow.
for some reason I can’t install the Pixel Launcher 10, only 7.1 works.
Thank you your work.
the test failed. Chrome does not work, applications constantly freeze, even a gps test.
as a daily rum I do not advise
Click to expand...
Click to collapse
Would be good if you logged all that and posted...
It does sound like a gaps issue though
sparx said:
Would be good if you logged all that and posted...
It does sound like a gaps issue though
Click to expand...
Click to collapse
no, it's not gapps, on another ROM everything works after they are installed
opengapps nano 20191209 beta
pincher65 said:
no, it's not gapps, on another ROM everything works after they are installed
opengapps nano 20191209 beta
Click to expand...
Click to collapse
Please link me the gapps and supply some logs, I need to examine this...also, did you restore any backups before?
The Blackview BV9800 Pro is a relatively rare device, and has no support from LineageOS or any other popular ROM project I can find. This is kind of a shame, because it's a pretty cool device - in particular, it has an integrated thermal camera, and is also just a nice ruggedized phone at a surprisingly low price. The bootloader is unlockable out of the box without any need for an unlock code or other nonsense from the vendor, which is also a big bonus.
Being a Project Treble-compatible device, it's possible to run unofficial GSI builds of LineageOS on it, such as these, which are replacement images to flash over /system. These work well with the majority of the BV9800 Pro's functions (wireless, visible-light cameras, sensors, etc.), but getting the thermal camera to work requires a little bit more work. I have done this successfully, so I wanted to share what I did in case anyone else finds themselves in the same situation.
I have only tested these procedures on a BV9800 Pro (EEA version), running LineageOS 16 (Android 9) from the link above. Other versions of Android may work, but I do not know whether they do or not, and decided to stay with Android 9, since this is what the vendor ships on the device. Your results may vary if you decide to try a newer version.
The factory MyFLIR app for the device can be found at this location in the stock ROM:
Code:
/system/app/myflir-bv2.3.6-release-signed/myflir-bv2.3.6-release-signed.apk
However, if you try to just install it like a normal app package under LineageOS, it crashes on startup without providing any useful information. The system logs reveal that it crashes because it's trying to communicate with a system service that manages the thermal camera, but this service isn't installed. Fortunately, you can install it by just copying a few files from the factory ROM over to the LineageOS system. The files in question are located at these paths in the factory ROM:
Code:
/system/bin/leptonServer
/system/etc/init/LeptonCameraServer.rc
/system/lib64/libleptoncamera.so
If you copy these files to the same paths in the LineageOS /system tree, then the Lepton camera server backend, which is required for the MyFLIR app to function, will be installed and configured to start at boot.
SELinux seems to prevent the app from connecting to the Lepton server on my device, so I had to disable it by running
Code:
setenforce 0
in a root shell on the device. I didn't install it as a system app, though, which could be part of the problem. I don't know much about how SELinux actually works, but I feel comfortable enough disabling it. If you don't want to disable it, you can probably find information about how to make it allow the FLIR app to work, but I'm afraid I can't be of much help there.
You can find a copy of the stock BV9800 Pro ROM here on the Blackview forum.
If you want to root the stock ROM to allow you to inspect /system, this thread explains how. If you prefer, you can instead extract the ROM zip archive on a computer, decompress the included system.img with simg2img, and mount it to inspect the contents directly, which is what I did. Modifying /system on a running device can be difficult these days, so it will probably work best to mount up the GSI image the same way and copy the files into it, rather than try to edit it in-place on a running device.
I hope this information helps. The thermal camera is one of the most important (and expensive) features of the BV9800 Pro, and getting it working was pretty much the deciding factor for me as to whether I would keep the (kind of bad) factory ROM, or get to enjoy all the perks of LineageOS. I'm not really knowledgeable enough to write a complete and trustworthy guide to installing LineageOS, though, so if you're just getting started, you'll want to find a more detailed tutorial about how installing custom ROMs (especially GSI/Treble builds) works.
That's a cool rugged phone. Stock it's running on Pie... personally I leave it be and optimize it as best I could to get maximum battery life.
I was looking at these... FLIR, hell yes.
I was following your guide, I'm using my Blackview 9800pro without GApps (but with MicroG 0.2.18.204714) on LineageOS 17.1-20210321. When opening the MyFlir camera or gallery app, it asks me for all the relevant permissions on the first start and then promptly crashes every time I open it. I tried both as a system and a regular app, with and without selinux. In the error below, it complains about not finding the right function in libvndksupport.so. This library is much smaller in LineageOS than it is shipped in the Stock ROM from Blackview. Replacing the LineageOS shared object file with the one from Blackview causes my phone not to boot. Is there something I am missing that causes my instance of the app (I tried both 2.3.6 and 2.3.8) to crash?
Code:
04-28 00:27:34.047 1383 5788 I ActivityTaskManager: START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.flir.tiger/com.flir.monarch.ui.MainActivity bnds=[27,996][232,1321]} from uid 10121
04-28 00:27:34.057 783 804 I [email protected]: powerHintAsync hint:8, data:1
04-28 00:27:34.061 783 803 I libPowerHal: 8: legacy set freq: 1989000 -1 2106000 -1
04-28 00:27:34.076 1383 1420 E system_server: Invalid ID 0x00000000.
04-28 00:27:34.077 1383 1419 W ActivityManager: Stopping service due to app idle: u0a216 -10s135ms com.flir.tiger/com.flir.monarch.media.MediaScanner
04-28 00:27:34.084 1008 1008 D Zygote : Forked child process 7648
04-28 00:27:34.087 1383 1426 I ActivityManager: Start proc 7648:com.flir.tiger/u0a216 for pre-top-activity {com.flir.tiger/com.flir.monarch.ui.MainActivity}
04-28 00:27:34.147 1579 1579 D ImageWallpaper: wallpaper visibility changes to: false
04-28 00:27:34.161 762 864 I hwcomposer: [DEV] 1024 0 0 0
04-28 00:27:34.162 762 864 I hwcomposer: [DEV] 0 741 0 0
04-28 00:27:34.162 762 864 I hwcomposer: [DEV] 0 0 470 0
04-28 00:27:34.162 762 864 I hwcomposer: [DEV] 0 0 0 1024
04-28 00:27:34.173 7648 7648 D FirebaseApp: com.google.firebase.auth.FirebaseAuth is not linked. Skipping initialization.
04-28 00:27:34.174 7648 7648 D FirebaseApp: com.google.firebase.crash.FirebaseCrash is not linked. Skipping initialization.
04-28 00:27:34.174 7648 7648 I FirebaseInitProvider: FirebaseApp initialization successful
04-28 00:27:34.177 762 864 I hwcomposer: [DEV] [DEV] (Send identity matrix)
04-28 00:27:34.187 7648 7673 I FA : App measurement is starting up, version: 15300
04-28 00:27:34.187 7648 7673 I FA : To enable debug logging run: adb shell setprop log.tag.FA VERBOSE
04-28 00:27:34.187 7648 7673 I FA : To enable faster debug mode event logging run:
04-28 00:27:34.187 7648 7673 I FA : adb shell setprop debug.firebase.analytics.app com.flir.tiger
04-28 00:27:34.196 762 864 I hwcomposer: [DEV] 1024 0 0 0
04-28 00:27:34.196 762 864 I hwcomposer: [DEV] 0 741 0 0
04-28 00:27:34.196 762 864 I hwcomposer: [DEV] 0 0 470 0
04-28 00:27:34.196 762 864 I hwcomposer: [DEV] 0 0 0 1024
04-28 00:27:34.200 7648 7648 I CrashlyticsCore: Initializing Crashlytics 2.6.8.32
04-28 00:27:34.207 7648 7686 W ContextImpl: Failed to ensure /data/user/0/com.google.android.gms/shared_prefs: mkdir failed: EACCES (Permission denied)
04-28 00:27:34.208 7648 7648 I CrashlyticsInitProvider: CrashlyticsInitProvider initialization successful
04-28 00:27:34.212 762 864 I hwcomposer: [DEV] [DEV] (Send identity matrix)
04-28 00:27:34.220 2428 2428 D GmsMeasureBrokerSvc: onBind: Intent { act=com.google.android.gms.measurement.START pkg=com.google.android.gms }
04-28 00:27:34.222 3179 3179 D GmsGcmRegister: onBind: Intent { act=com.google.android.c2dm.intent.REGISTER pkg=com.google.android.gms }
04-28 00:27:34.223 1024 1024 I netd : firewallSetUidRule(2, 10161, 1) <2.63ms>
04-28 00:27:34.227 1024 1024 I netd : firewallSetUidRule(2, 10160, 1) <1.74ms>
04-28 00:27:34.230 1024 1024 I netd : firewallSetUidRule(2, 10157, 1) <2.14ms>
04-28 00:27:34.233 1024 1024 I netd : firewallSetUidRule(2, 10151, 1) <1.85ms>
04-28 00:27:34.236 7648 7648 I ashmem : memfd: device VNDK version (28) is < Q so using ashmem.
04-28 00:27:34.277 7648 7648 D AndroidRuntime: Shutting down VM
04-28 00:27:34.277 7648 7648 E AndroidRuntime: FATAL EXCEPTION: main
04-28 00:27:34.277 7648 7648 E AndroidRuntime: Process: com.flir.tiger, PID: 7648
04-28 00:27:34.277 7648 7648 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "android_get_exported_namespace" referenced by "/data/app/com.flir.tiger-EcVVz9vk2XWvVymOtKJxOQ==/lib/arm64/libvndksupport.so"...
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at java.lang.Runtime.loadLibrary0(Runtime.java:1071)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at java.lang.Runtime.loadLibrary0(Runtime.java:1007)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at java.lang.System.loadLibrary(System.java:1667)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at com.flir.flirone.sdk.FlirOne.<clinit>(FlirOne.java:59)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at com.flir.flirone.sdk.FlirOne.registerDeviceCallback(FlirOne.java:341)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at com.flir.monarch.app.ForegroundApplication.onActivityStarted(ForegroundApplication.java:88)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.app.Application.dispatchActivityStarted(Application.java:406)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.app.Activity.dispatchActivityStarted(Activity.java:1238)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.app.Activity.onStart(Activity.java:1723)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.support.v4.app.FragmentActivity.onStart(FragmentActivity.java:614)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.support.v7.app.AppCompatActivity.onStart(AppCompatActivity.java:178)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at com.flir.monarch.ui.MainActivity.onStart(MainActivity.java:79)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.app.Instrumentation.callActivityOnStart(Instrumentation.java:1432)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.app.Activity.performStart(Activity.java:7847)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.app.ActivityThread.handleStartActivity(ActivityThread.java:3294)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.performLifecycleSequence(TransactionExecutor.java:221)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.cycleToPath(TransactionExecutor.java:201)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:173)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:97)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2016)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:107)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.os.Looper.loop(Looper.java:214)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:7356)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:491)
04-28 00:27:34.277 7648 7648 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:940)
04-28 00:27:35.334 1383 5501 D AlarmManagerService: Kernel timezone updated to -120 minutes west of GMT
04-28 00:27:35.348 1383 6143 D AlarmManagerService: Kernel timezone updated to -120 minutes west of GMT
04-28 00:27:35.709 1090 1371 I 1090 1371 [sunwave-hal] : (711) 'healthMonitoringThread' enter.
04-28 00:27:35.710 1090 1371 I 1090 1371 [sunwave-client] : (90) ---8<---- TA LOG BEGINS ---------
04-28 00:27:35.710 1090 1371 I 1090 1371 [sunwave-ta-core] : (2869) 'sf_get_device_state' state:0008
04-28 00:27:35.710 1090 1371 I 1090 1371 [sunwave-client] : (107) --------- TA LOG FINISH ---->8---
Thanks for the info for the flir Camera,
It works fine with lineage OS 16 !
I want to add the info I got while doing it:
It does not work with all version of Andy Custom Lineage OS: I could not make it works with this one: lineage-16.0-20191017-UNOFFICIAL-treble_arm64_bvN.img.xz the lepton server had a seg fault.
I try with a lineage OS 18 , the lepton server worked but the application failed, I will look into it one day... maybe
I root my phone with magisk
I used a script to bypass SElinux and start the server when i want ( because i don't know if it wise to always have SElinux in permissive mode)
tylab said:
Thanks for the info for the flir Camera,
It works fine with lineage OS 16 !
I want to add the info I got while doing it:
It does not work with all version of Andy Custom Lineage OS: I could not make it works with this one: lineage-16.0-20191017-UNOFFICIAL-treble_arm64_bvN.img.xz the lepton server had a seg fault.
I try with a lineage OS 18 , the lepton server worked but the application failed, I will look into it one day... maybe
I root my phone with magisk
I used a script to bypass SElinux and start the server when i want ( because i don't know if it wise to always have SElinux in permissive mode)
Click to expand...
Click to collapse
thank u for the additional info!,so which version of lineage os 16 worked for u? iam on lineage-16.0-20191017-UNOFFICIAL-treble_arm64_bvN.img.xz and tried the author's steps but didn't work for me, also it'd be nice if u share with us the script u use to bybass selinux,thanks.
I want to report back some of my own success in regards to this thread. I have the camera working, but it's not a perfect solution and was wondering if you guys could assist me in checking what I could have possibly missed. I'm running it on the most current Lineage OS 18.1; I've compiled a version using the Treble ROM lineage-18.1-20210512-UNOFFICIAL-treble_arm64_bvS with Magisk as root (I also added MindTheGapps into it after some workarounds with the mounts, and had to register my device as an "unsupported device").
I followed the OP's guide to the T, and still couldn't get the app to even open. The logs revealed it was trying to call leptonServer, nulling out after five tries, and then crashing. Narrowed this down to being an issue with the /bin/leptonServer file itself being set as -rwx-r--r--, and changing it to -rwxr-x-r-x got the app to boot up. The only problem is, for the camera to actually start, I have to open a terminal session and start leptonServer from there, and I assume this has something to do with the SELinux policies in place. I've fought half the battle and got a version of sepolicy-inject set up to run (using the following policy: allow untrusted_app_27 default_android_service:service_manager { find }; (sepolicy-inject -s untrusted_app_27 -t default_android_service -c service_manager -p find (if this doesn't work for you, try doing logcat ServiceManager:V SELinux:V *:S to find the relevant SELinux policies that you need to apply, and follow the formulas))), but I figure this is still erroring out somewhere, since, after a restart, the only way I can get it working again is to go and disable SELinux using setenforce to 0 and then starting the server again using some sort of terminal. I also installed the MyFlir app as a system app.
I believe that part of the issue might be that I haven't properly added the SELinux policy, but I'm not entirely positive how I would go about testing this (I've more or less just gotten into the ROM building scene last week, but feel I have somewhat of an edge being a software developer for a living). I think if I boot into recovery I can grab the sepolicy file, but I'm not sure what else to do with it at this point.
The error I get when it's not running, aside from the PID is pretty consistent too:
05-31 19:19:06.814 372 372 E SELinux : avc: denied { find } for pid=20308 uid=10195 name=LeptonCameraService scontext=u:r:untrusted_app_27:s0:c195,c256,c512,c768 tcontext=ubject_r:default_android_service:s0 tclass=service_manager permissive=0
Hopefully, this helps someone to find the right answers before I can; I know I'll keep tinkering with it until I find the solution (I'm also attempting to overcome the CTSProfile/Basic failure in Magisk, which I plan to make a guide if I can find an answer).
I get the same error as @&00&V5yt$r2$E!n1IDUiJ9bF on Lineage18.1 - treble_arm64_bvS-userdebug
04-28 00:27:34.277 7648 7648 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "android_get_exported_namespace" referenced by "/data/app/com.flir.tiger-EcVVz9vk2XWvVymOtKJxOQ==/lib/arm64/libvndksupport.so"...
My leptonServer is working correctly and service runs from the start so it I feel this is related to the /system/app/myflir-bv2.3.6-release-signed.
Are you guys using a different version of the app?
Flir said:
I get the same error as @&00&V5yt$r2$E!n1IDUiJ9bF on Lineage18.1 - treble_arm64_bvS-userdebug
04-28 00:27:34.277 7648 7648 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "android_get_exported_namespace" referenced by "/data/app/com.flir.tiger-EcVVz9vk2XWvVymOtKJxOQ==/lib/arm64/libvndksupport.so"...
My leptonServer is working correctly and service runs from the start so it I feel this is related to the /system/app/myflir-bv2.3.6-release-signed.
Are you guys using a different version of the app?
Click to expand...
Click to collapse
I also used myflir-bv2.3.6-release-signed, pulled straight from the currently available 9.0 ROM.
For that specifically, if you are looking at the most recent ROM build available from Blackview, in the directory /system/system/app/myflir-bv2.3.6-release-signed, there is both the APK and a lib folder. I'd copy the lib folder over to your phone in that same directory; I think you're missing the dependencies from there.
If you already have those libaries in there, try the read/write settings on the folder too.
Hi bv9800 pro customers! Anyone tryed the magisk module in the thread https://forum.xda-developers.com/t/blackview-bv9900pro-magisk-modules.4331187/
to get flir worked on linage?
ilich79 said:
Hi bv9800 pro customers! Anyone tryed the magisk module in the thread https://forum.xda-developers.com/t/blackview-bv9900pro-magisk-modules.4331187/
to get flir worked on linage?
Click to expand...
Click to collapse
Hi ilich79
I tryed the magisk module for BV9900pro.
I have installed it manualy to improve my understanding.
First, selinux block as always :
E/SELinux ( 338): avc: denied { find } for pid=18411 uid=10175 name=LeptonCameraService scontext=u:r:priv_app:s0:c512,c768 tcontext=u:object_r:default_android_service:s0 tclass=service_manager permissive=0
After enforce selinux and relanch the leptonServer.
Application launch completly but the camera send only the first image and block after that
So, i replace the leptonServer by the old one and retry.
Finally it works fully.
I someone know how to correctly set the selinux policy for this app ? I will be graceful
May be this can help?
[MODULE] SELinux Mode Inverter (Advanced SELinux Mode Changer)
It Is Now A Part Of The Main Module Of MultiFunctions & Its Thread https://forum.xda-developers.com/apps/magisk/module-multifunctions-bootloop-t3933386. Introduction: Simple Module To Invert The Default Android SELinux Mode During Startup ([From...
forum.xda-developers.com
Flir said:
I get the same error as @&00&V5yt$r2$E!n1IDUiJ9bF on Lineage18.1 - treble_arm64_bvS-userdebug
04-28 00:27:34.277 7648 7648 E AndroidRuntime: java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol "android_get_exported_namespace" referenced by "/data/app/com.flir.tiger-EcVVz9vk2XWvVymOtKJxOQ==/lib/arm64/libvndksupport.so"...
My leptonServer is working correctly and service runs from the start so it I feel this is related to the /system/app/myflir-bv2.3.6-release-signed.
Are you guys using a different version of the app?
Click to expand...
Click to collapse
I get the same error, @QuentinX5 : Did you use a different version? Would be nice to have a Lineage upgrade.
Regarding the problem with the MyFlir camera app: I had the same problem (unable to read camera files). I looked everywhere. I mean, everywhere trying to find an answer. There's also a video on youtube with comments suggesting flashing the APD.BIN file (I did not try). I even translated different language websites. Finally, I contacted the BV customer support and their reply was the classic (clear the app cache), which doesn't work at all and not just for me. I tried to get the APK file from the image and installing it which didn't work either.
Here's the simple magic solution that kept me trying for a week, and no one wrote it anywhere:
There's a folder named (com.flir.tiger) inside the Android folder in the phone storage with the contents:
com.flir.tiger\files\iron
com.flir.tiger\files\CameraFiles\system\calib.rsc
com.flir.tiger\files\CameraFiles\system\maps\ds_we_ap_fi_le_LCFMap.fff
Just copy the folder from another phone and paste it on your phone, and that's it!
thelaseman said:
Regarding the problem with the MyFlir camera app: I had the same problem (unable to read camera files). I looked everywhere. I mean, everywhere trying to find an answer. There's also a video on youtube with comments suggesting flashing the APD.BIN file (I did not try). I even translated different language websites. Finally, I contacted the BV customer support and their reply was the classic (clear the app cache), which doesn't work at all and not just for me. I tried to get the APK file from the image and installing it which didn't work either.
Here's the simple magic solution that kept me trying for a week, and no one wrote it anywhere:
There's a folder named (com.flir.tiger) inside the Android folder in the phone storage with the contents:
com.flir.tiger\files\iron
com.flir.tiger\files\CameraFiles\system\calib.rsc
com.flir.tiger\files\CameraFiles\system\maps\ds_we_ap_fi_le_LCFMap.fff
Just copy the folder from another phone and paste it on your phone, and that's it!
Click to expand...
Click to collapse
Hi do you think your solution works for all lineageos releases? If I change the stock rom I was thinking on putting release 19.1
thelaseman said:
Regarding the problem with the MyFlir camera app: I had the same problem (unable to read camera files). I looked everywhere. I mean, everywhere trying to find an answer. There's also a video on youtube with comments suggesting flashing the APD.BIN file (I did not try). I even translated different language websites. Finally, I contacted the BV customer support and their reply was the classic (clear the app cache), which doesn't work at all and not just for me. I tried to get the APK file from the image and installing it which didn't work either.
Here's the simple magic solution that kept me trying for a week, and no one wrote it anywhere:
There's a folder named (com.flir.tiger) inside the Android folder in the phone storage with the contents:
com.flir.tiger\files\iron
com.flir.tiger\files\CameraFiles\system\calib.rsc
com.flir.tiger\files\CameraFiles\system\maps\ds_we_ap_fi_le_LCFMap.fff
Just copy the folder from another phone and paste it on your phone, and that's it!
Click to expand...
Click to collapse
Hi, I'm trying to get the flir camera working on lineage 19.1 can @thelaseman gime me the file you write about? beacause I don't have another phone to copy from.
Thanks
Max
max74926 said:
Hi, I'm trying to get the flir camera working on lineage 19.1 can @thelaseman gime me the file you write about? beacause I don't have another phone to copy from.
Thanks
Max
Click to expand...
Click to collapse
If you are still looking for it I might be able to extract these files for you.
@thelaseman @QuentinX5
Is anyone still using a BV9800 Pro with a Lineage ROM? What version are you on, what specific build did you install, did you encounter any specific issues, were they fixable and how?
Not asking for a full guide (wouldn't mind of course ) but before I start messing with what is currently my daily driver I'd like to know if anyone else was successful with a certain version. Particularly interested if any newer versions have also ended up working with the FLIR-camera.
Hi @dj__jg,
I use the attached files for lineage 19.1 GSI (https://forum.xda-developers.com/t/gsi-12-lineageos-19-x-gsi-a64b-64b.4358041/).
My camera calib is wrong (the thermal camera is upside down.) so I don't push the calib file here, if you have a good one, i'm interested.
I don't have fixed the selinux error for the moment, so just disable it went you launch the '/system/bin/leptonServer'
I missnamed the attached file, it's for BV9800 pro
I suddenly feel very stupid, I just realised I've gotten confused about my phones model number
I actually have a Blackview ninethousandninehundred pro, not 9800. I either had a brainfart or made a typo as I was searching if anyone had managed to use a recent Lineage ROM on it and accidentally ended up on this thread and didn't notice.
Luckily I didn't upload my calib file etc here, or someone could have gotten very confused. I think I will try to run a GSI build at some point, but when I have some more spare time/don't need this phone every day. The information about the com.flir.tiger folder is still very handy because it is the same on my model, I hope the same tactics will work to get the FLIR working in a GSI build.
(Wrote out the model number in text so other people googling the model number won't end up confused on this thread without even making a typo)
It's my bad i missnamed my file, it's 9800 pro not 9800 (who don't have thermal camera)