Database Info

Cryptfs : unmounting /data failed: Device or resource busy

I am trying to encrypt my rooted Nexus 5 (running CyanogenMod 13/Marshmallow).
Here is how I am doing:
1. With the phone running and connected to USB, make sure that /mnt/asec/ is empty
2. Long-press the power physical button, this makes the Power off dialog pop up
3. Long-press the "Power off" option of the pop up, confirm that you want to reboot in Safe Mode
4. Without starting any app, run adb shell on the computer then su to get root then pkill -KILL daemonsu to kill the SuperSU daemon
5. Settings > Security > Encrypt phone, confirm
6. The phone reboots, from the computer type adb logcat
Here is what I see:
Code:
I ServiceManager: service 'drm.drmManager' died
D libEGL : loaded /vendor/lib/egl/libEGL_adreno.so
D libEGL : loaded /vendor/lib/egl/libGLESv1_CM_adreno.so
D libEGL : loaded /vendor/lib/egl/libGLESv2_adreno.so
I Adreno-EGL: <qeglDrvAPI_eglInitialize:379>: QUALCOMM Build: 09/02/15, 76f806e, Ibddc658e36
E BootAnimation: couldn't find audio_conf.txt
W BootAnimation: Audio service is not initiated.
D BootAnimation: Use save memory method, maybe small fps in actual.
D BootAnimation: Use save memory method, maybe small fps in actual.
E Cryptfs : unmounting /data failed: Device or resource busy
E Cryptfs : Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/metadata
W vold : type=1400 audit(0.0:19): avc: granted { read } for name="mmcblk0p28" dev="tmpfs" ino=6735 scontext=u:r:vold:s0 tcontext=u:object_r:userdata_block_device:s0 tclass=blk_file
W vold : type=1400 audit(0.0:20): avc: granted { read open } for name="mmcblk0p28" dev="tmpfs" ino=6735 scontext=u:r:vold:s0 tcontext=u:object_r:userdata_block_device:s0 tclass=blk_file
W vold : type=1400 audit(0.0:21): avc: granted { ioctl } for path="/dev/block/mmcblk0p28" dev="tmpfs" ino=6735 ioctlcmd=1260 scontext=u:r:vold:s0 tcontext=u:object_r:userdata_block_device:s0 tclass=blk_file
D Cryptfs : Just asked init to shut down class main
W vold : emulated unmount requires state mounted
E Cryptfs : unmounting /data failed: Device or resource busy
W SocketClient: write error (Broken pipe)
W SocketClient: Unable to send msg '200 8 -
At that point the CyanogenMod loading screen keeps animating for 10+ hours and probably forever if I don't stop it. Pressing the Power physical button for 5 seconds makes it reboot and start normally this time. Obviously encryption has not been performed.
I tried the whole procedure twice.
What could be causing this Cryptfs : unmounting /data failed: Device or resource busy problem?

[SOLVED] can't get gapps to work after porting a rom

I just ported a rom for my device. When I try to run opengapps I get the following error:
"there was a problem communicating with google servers"
I think it might be related to this that I found in dmesg
Code:
[ 1398.055688] type=1400 audit(1503798238.823:50): avc: denied { search } for pid=7470 comm="IntentService[P" name="com.google.android.gsf" dev="mmcblk0p46" ino=803248 scontext=u:r:untrusted_app:s0:c522,c768 tcontext=u:object_r:app_data_file:s0:c512,c768 tclass=dir permissive=1
Is there any way to fix this or a way around this?
Thanks in advance.

I have an idea it has something to do with my build.

Widevine L3 with locked bootloader

I unlocked my bootloader and rooted my OnePlus 6 a couple of months ago. For work reasons I was required to relock my bootloader and unroot my phone. This didn't work well at first, so eventually I had to do a full restore via MsmDownloadTool as described in this thread.
However, even with a locked bootloader, I still see Widevine L3 in DRM Info. Some error messages from logcat include:
Code:
02-21 15:17:08.274 746 12466 D WVCdm : Instantiating CDM.
02-21 15:17:08.275 746 12466 I WVCdm : CdmEngine::QueryStatus
02-21 15:17:08.275 746 22869 I WVCdm : Level3 Library 4445 Oct 4 2017 17:06:25
02-21 15:17:08.276 746 12466 I WVCdm : L3 Initialized. Trying L1.
02-21 15:17:08.331 746 12466 W WVCdm : File::eek:pen: fopen failed: 2
02-21 15:17:08.331 746 12466 W WVCdm : Could not open /factory/wv.keys. Falling Back to L3.
02-21 15:17:08.334 746 12466 I WVCdm : L3 Terminate.
I also see some SELinux errors:
Code:
02-21 14:32:38.395 746 746 W HwBinder:746_2: type=1400 audit(0.0:7787): avc: denied { read } for name="u:object_r:oem_prop:s0" dev="tmpfs" ino=22392 scontext=u:r:hal_drm_widevine:s0 tcontext=u:object_r:oem_prop:s0 tclass=file permissive=0
02-21 14:32:38.395 746 746 W HwBinder:746_2: type=1400 audit(0.0:7789): avc: denied { read } for name="u:object_r:oem_prop:s0" dev="tmpfs" ino=22392 scontext=u:r:hal_drm_widevine:s0 tcontext=u:object_r:oem_prop:s0 tclass=file permissive=0
Any thoughts? It looks like others have run into this issue but there was no resolution.

Was something like Secure Element chip burnt out by unlocking bootloader?

I had the same problem. Talk with oneplus support and they will fix it in warranty.

[ROM][EOL][KLTE][PIE]Unofficial Resurrection Remix [V7.x][LuisROM][G900F]

My Unoffical Resurrection Remix (PIE)
(LuisROM) for Samsung Galaxy S5 (klte)​
{
"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"
}
Code:
*** Disclamer
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
EOL - End of life / End of development since 2020-02-13! The RR Team has stopped the development. Please switch to my LuisROM based on crDroid.
Link crDroid builds: http://luis-builds.de/downloads/lineageos/cr/
This is my unofficial Resurrection Remix V7.x (pie) cutsom rom.
This is a ROM that works on Samsung Galaxy S5 (klte/snapdragon/G900F) only! This ROM comes with a highly-customized kernel, as well as some other very custom modifications.
I will NOT provide support if you install a custom kernel!
Changelogs: http://luis-builds.de/downloads/lineageos/rr/Samsung_Galaxy_S5_(klte)/RR-P-Changelog.mkdn
Introduction
Hello Friends!
I had troubles to find current builds for my devices so I decided to make regular builds for my devices. When my friends told me about similar problems, I extended the builds to include their devices as well. So these builds were and are mainly for my friends and me, but I finally decided to provide them also for public download.
My ROMs
My unofficial Resurrection Remix (LuisROM) an awesome combination of performance, customization, power and the most new features, brought directly to your device. The LuisROM build server generates automaticly every 2nd days new builds directly from the sources.
Notice
Sometimes I get a lot of help or feature requests from users of my LuisROMs. My dog Luis and I try to fulfill most of the wishes, but that is not always possible. I do that as a little hobby and Luis does not always want to build ROMs . Please understand if I can not always answer directly.
ROM features:
Based off latest Resurrection Remix V7.x (pie), lineageos and aosp sources
Latest security patches
OTA Updater (LineageOS Updater) since builds from 2019-01-26
Compatible with EX Kernel Manager
Many other misc. performance and stability improvements under the hood
Kernel: Linux 3.4.x Kernel with many mods other devs and me (thanks for your incredible work!)
Removed lots of excessive bloat (improves security and performance)
Improved stability (several bugs not listed here have been fixed)
More I/O-Schedulers
Optimized for performance and battery life
Compatible with systemless root
Many other misc. improvements not listed here
Installation instructions:
First time installation:
Unlock your bootloader
Flash recovery zip (TWRP)
Reboot into TWRP Recovery
Wipe all data
Flash my lastest RR LuisROM (download here)
Optional: Flash Open GApps and Magisk
Reboot and enjoy
OTA App update installation (auto):
Go to Settings > Advanced > Updater
Press reload button (right corner)
Select download on the new build list
After download select update/flash new build (the update process can take longer than expected on treble devices!)
Reboot and enjoy
Download
Samsung Galaxy S5 builds: (http://luis-builds.de/downloads/lineageos/rr/Samsung_Galaxy_S5_(klte)/)
My other devices/ROMs: (http://luis-builds.de/downloads/lineageos/)
Download OpenGapps: (http://opengapps.org)
Flash latest TWRP: (download here)
Changelog
Developer: http://luis-builds.de/downloads/lineageos/rr/Samsung_Galaxy_S5_(klte)/RR-P-Changelog.mkdn
Telegram group:
https://t.me/rr_luisrom
Thanks To/Credits
Special thanks to Teams:
LineageOS team: https://www.lineageos.org
RR Team: https://www.resurrectionremix.com
OMNI team https://omnirom.org/about/
SLIMROMS https://slimroms.org/#/about
topjohnwu (Magisk) https://forum.xda-developers.com/apps/magisk
Thanks to the best devs on earth:
francokernel (https://forum.xda-developers.com/member.php?u=3292224)
sultanxda (https://forum.xda-developers.com/member.php?u=4800121)
flar2 (https://forum.xda-developers.com/member.php?u=4684315)
nathanchance (https://forum.xda-developers.com/member.php?u=6842057)
eng.stk (https://forum.xda-developers.com/member.php?u=3873953)
zx2c4 for the wireguard vpn ROM Integration (https://forum.xda-developers.com/android/development/wireguard-rom-integration-t3711635)
and of course to all the supporters.
Thanks for the Sources/Blobs/Tweaks
Resurrection Remix (https://github.com/LineageOS)
ArrowOS (https://github.com/ArrowOS-Devices)
TheMuppets (https://github.com/TheMuppets)
My Sources/Blobs/Tweaks
FraEgg (me) (https://github.com/FraEgg)
XDA:DevDB Information
[ROM][EOL][KLTE][PIE]Unofficial Resurrection Remix [V7.x][LuisROM][G900F], ROM for the Samsung Galaxy S5
Contributors
8224Freak
Source Code: https://github.com/FraEgg
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.4.x
Based On: RR, LineageOS, Resurrection Remix, AOSP
Version Information
Status: Stable
Stable Release Date: 2019-03-18
Created 2019-03-18
Last Updated 2020-02-15

Reserved

Hello,
Is substratum working in that ROM?
I want to apply overlays but nothing happens after applying..
Regards
Sent from my SM-G960F with Tapatalk

How many resurrection-remix are their, and what the different between both

support Samsung S5 SM-G900W8 ?

Latest build is not working for me.
It stucks at Samsung Galaxy S5 logo and then reboots to download mode..
Regards
Sent from my SM-G960F with Tapatalk

Just installed on never rooted 900F
Root - reboot - TWRP - reboot - Wipe system, Data, Davlik, Cache. flash ROM + Gapps - Reboot and everything is working very nice No single lock up or reboot etc.. in this few hours of adjusting..
ps. Nice ring tone

I use it for 3~ days and the rom worked almost perfectly , with the exception after 3 days it just restarted and stuck in boot , i dont know what to do , i tryed multiple bootloader/modem and now i am with BL_G900FXXU1BNL9 and CP_G900FXXU1BNL9 , is a way i can see the original bootloader/modem also a log file ?

@sunny_sall
As written right in the beginning of #1:
ONLY for G900F

bmwdroid said:
@sunny_sall
As written right in the beginning of #1:
ONLY for G900F
Click to expand...
Click to collapse
Exactly , my model is g900F . i will try to give you guys more info in a bit , i am trying to get it rooted and take a logcat
Edit : https://ufile.io/0fmwx if u want me to upload somewhere else just specify because the atachement has 50 kb more over the limit and xda does't allow it , i made a clean instal with the latest update , how should i repost the log when the phone goes to boot and stuck there if the android does't work ?
Model of the phone with droid hardware info :
Code:
DEVICE
Model: SM-G900F (rr_klte)
Manufacturer: samsung
Baseband Version: G900FXXU1BNL9
RIL Version: Samsung RIL v3.0
Build Number: rr_klte-userdebug 9 PQ2A.190305.002 eng.franke.20190401.105640 test-keys
Build Fingerprint: samsung/kltexx/klte:6.0.1/MMB29M/G900FXXU1CRH1:user/release-keys
Bootloader: G900FXXU1BNL9
Java VM: ART 2.1.0
OS Version: P (9)
SDK: 28
DISPLAY
Resolution: Full HD, 1080x1920 pixels
Software Density: 480 dpi (xxhdpi)
Refresh Rate: 60 Hz
PROCESSOR
CPU Architecture: ARMv7 Processor rev 1 (v7l)
Board: MSM8974
Chipset: Qualcomm MSM8974PRO-AC
Cores: 4
Clock Speed: 268 MHz - 2457 MHz
Instruction Sets: armeabi-v7a, armeabi
CPU Features: swp half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32
CPU Governor: interactive
Kernel Version: 3.4.113-LuisROM-sp-g45c2f4a178e
Kernel Architecture: armv7l
GRAPHICS
Renderer: Adreno (TM) 330
Vendor: Qualcomm
OpenGL Version: OpenGL ES 3.0
RAM
Total: 1701 MB
Java Heap: 192 MB
STORAGE
Internal: 11.5 GB
EXTERNAL: Not Detected
PRIMARY CAMERA
Resolution: 15,9 MP
Flash: Yes
Video Resolution: 4K UHD, 3840x2160
Supported Resolutions:
Image:
5312x2988
3984x2988
3264x2448
3264x1836
2560x1920
2048x1152
1920x1080
1280x960
1280x720
800x480
640x480
320x240
Video:
3840x2160 (4K UHD)
1920x1080 (Full HD)
1440x1080
1280x720 (HD)
800x450
800x480 (WVGA)
720x480
640x480 (VGA)
352x288
320x240
176x144
SECONDARY CAMERA
Resolution: 2,1 MP
Video Resolution: 4K UHD, 3840x2160
Supported Resolutions:
Image:
1920x1080
1440x1080
1280x960
1280x720
960x720
720x480
640x480
320x240
Video:
3840x2160 (4K UHD)
1920x1080 (Full HD)
1440x1080
1280x720 (HD)
960x720
800x450
720x480
640x480 (VGA)
352x288
320x240
176x144
FEATURES
Bluetooth: Yes
Bluetooth LE: Yes
GPS: Yes
NFC: Yes
USB Accessory: Yes
WiFi: Yes
WiFi Direct: Yes
BATTERY
Technology: Li-ion
Health: Good
SENSORS
MPU6500 Acceleration Sensor
MPU6500 Gyroscope Sensor
MPU6500 Uncalibrated Gyroscope Sensor
AK09911C Magnetic field Sensor
AK09911C Magnetic Sensor UnCalibrated
Barometer Sensor
TMG399X Proximity Sensor
TMG399X RGB Sensor
MPL Rotation Vector
MPL Game Rotation Vector
SAMSUNG Step Detector Sensor
SAMSUNG Step Counter Sensor
SAMSUNG Significant Motion Sensor
HRM Sensor
HeartRate Sensor
MAX86900
Corrected Gyroscope Sensor
Game Rotation Vector Sensor
Gyroscope Bias (debug)
GeoMag Rotation Vector Sensor
Gravity Sensor
Linear Acceleration Sensor
Rotation Vector Sensor
Orientation Sensor
Created by Droid Info

Made a clean install of the 20190401 version on my G900F with TWRP 3.2.3-0 yesterday with pico gapps and Magisk.
Installation went well, booted quite fast.
Installed 22 Apps.
Only problem is that the screen shots off as soon as I take my finger away.
Shutdown time is set to 2'.
I love RR ROMs and am quite sad that it doesn't work on my S5.
Sent from my v1awifi using XDA Labs

Sometimes when I want to unlock the smartphone, I'm only half a blue screen with clock displayed. The device can then no longer be spun. what can you do to fix this problem?

Is there a way so i can make use the heart rate sensor in this rom?

Hey 8224Freak, there is a bootloop when dirty flashing 7.0.2 (RR-P-v7.0.2-20190422-klte-Unofficial-LuisROM.zip) over an existing 7.0.1 install. I did not have time to try a clean flash, but I did grab some logs using this boot debug patcher
Code:
************ Failure starting system services
04-23 18:24:35.311 2041 2041 E System : java.lang.SecurityException: Permission android.permission.WRITE_MEDIA_STORAGE is not a changeable permission type
04-23 18:24:35.311 2041 2041 E System : at com.android.server.pm.permission.BasePermission.enforceDeclaredUsedAndRuntimeOrDevelopment(BasePermission.java:383)
04-23 18:24:35.311 2041 2041 E System : at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(PermissionManagerService.java:1404)
04-23 18:24:35.311 2041 2041 E System : at com.android.server.pm.permission.PermissionManagerService.access$900(PermissionManagerService.java:89)
04-23 18:24:35.311 2041 2041 E System : at com.android.server.pm.permission.PermissionManagerService$PermissionManagerInternalImpl.grantRuntimePermission(PermissionManagerService.java:2093)
04-23 18:24:35.311 2041 2041 E System : at com.android.server.pm.PackageManagerService$PackageManagerInternalImpl.grantRuntimePermission(PackageManagerService.java:24286)
04-23 18:24:35.311 2041 2041 E System : at com.android.server.pm.permission.DefaultPermissionGrantPolicy.grantRuntimePermissions(DefaultPermissionGrantPolicy.java:1374)
04-23 18:24:35.311 2041 2041 E System : at com.android.server.pm.permission.DefaultPermissionGrantPolicy.grantRuntimePermissions(DefaultPermissionGrantPolicy.java:1269)
04-23 18:24:35.311 2041 2041 E System : at com.android.server.pm.permission.DefaultPermissionGrantPolicy.grantDefaultPermissionExceptions(DefaultPermissionGrantPolicy.java:1458)
04-23 18:24:35.311 2041 2041 E System : at com.android.server.pm.permission.DefaultPermissionGrantPolicy.grantDefaultPermissions(DefaultPermissionGrantPolicy.java:269)
04-23 18:24:35.311 2041 2041 E System : at com.android.server.pm.PackageManagerService.systemReady(PackageManagerService.java:21354)
04-23 18:24:35.311 2041 2041 E System : at com.android.server.SystemServer.startOtherServices(SystemServer.java:1792)
04-23 18:24:35.311 2041 2041 E System : at com.android.server.SystemServer.run(SystemServer.java:464)
04-23 18:24:35.311 2041 2041 E System : at com.android.server.SystemServer.main(SystemServer.java:309)
04-23 18:24:35.311 2041 2041 E System : at java.lang.reflect.Method.invoke(Native Method)
04-23 18:24:35.311 2041 2041 E System : at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:495)
04-23 18:24:35.311 2041 2041 E System : at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:838)
04-23 18:24:35.311 2041 2041 E Zygote : System zygote died with exception
04-23 18:24:35.311 2041 2041 E Zygote : java.lang.SecurityException: Permission android.permission.WRITE_MEDIA_STORAGE is not a changeable permission type
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.server.pm.permission.BasePermission.enforceDeclaredUsedAndRuntimeOrDevelopment(BasePermission.java:383)
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.server.pm.permission.PermissionManagerService.grantRuntimePermission(PermissionManagerService.java:1404)
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.server.pm.permission.PermissionManagerService.access$900(PermissionManagerService.java:89)
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.server.pm.permission.PermissionManagerService$PermissionManagerInternalImpl.grantRuntimePermission(PermissionManagerService.java:2093)
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.server.pm.PackageManagerService$PackageManagerInternalImpl.grantRuntimePermission(PackageManagerService.java:24286)
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.server.pm.permission.DefaultPermissionGrantPolicy.grantRuntimePermissions(DefaultPermissionGrantPolicy.java:1374)
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.server.pm.permission.DefaultPermissionGrantPolicy.grantRuntimePermissions(DefaultPermissionGrantPolicy.java:1269)
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.server.pm.permission.DefaultPermissionGrantPolicy.grantDefaultPermissionExceptions(DefaultPermissionGrantPolicy.java:1458)
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.server.pm.permission.DefaultPermissionGrantPolicy.grantDefaultPermissions(DefaultPermissionGrantPolicy.java:269)
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.server.pm.PackageManagerService.systemReady(PackageManagerService.java:21354)
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.server.SystemServer.startOtherServices(SystemServer.java:1792)
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.server.SystemServer.run(SystemServer.java:464)
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.server.SystemServer.main(SystemServer.java:309)
04-23 18:24:35.311 2041 2041 E Zygote : at java.lang.reflect.Method.invoke(Native Method)
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:495)
04-23 18:24:35.311 2041 2041 E Zygote : at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:838)
04-23 18:24:35.311 2041 2041 D AndroidRuntime: Shutting down VM
Edit: If no-one else has this problem, I probably stuffed up with opengapps somehow :/ Will clean flash when I have time.

Also, does Google Assistant work for anyone here? (Not just the 'OK Google' hotword which launches google searches - that works, but the actual 'assistant' feature?) The Google app appears to crash when tapping the 'Updates' button.

I don't like it, it's a boring rom

Anyone else having issues with quick tiles , when set the theme of the tiles to oreo style some of the tiles are not present ?

Poswa said:
I don't like it, it's a boring rom
Click to expand...
Click to collapse
Then I suggest that you build a less boring rom and I will be happy to test it.
You should be grateful that we have someone who volunteers their time and also willing to share their hard work for us to enjoy!

KazuDante said:
Anyone else having issues with quick tiles , when set the theme of the tiles to oreo style some of the tiles are not present ?
Click to expand...
Click to collapse
No problems here mate

pmduper said:
No problems here mate
Click to expand...
Click to collapse
are you sure , i mean did you actually put the quick tiles to the oreo style ? screenshot

Getting the Thermal Camera Working on the Blackview BV9800 Pro under a Custom ROM

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)