Database Info

Lineage 14.1 Stable - Micromax Canvas 5 E481

Join this groups for roms and support...
Telegram:
https://t.me/teammaxmtk
Facebook:
https://m.facebook.com/groups/673560846179945?ref=bookmarks

Congrats to every canvas 5 user.
Don't forget to join the official whatsapp group of canvas 5.
https://chat.whatsapp.com/2YtWDoFzukZKthAUenMv74

Plz share the SS of the rom.
Big hit and Thanks to Arshjot singh and Harishwarrior bro... U two are the best dev... Give new soul to MMX CANVAS 5

..

sun75 said:
Hi,
after some debugging, I solved the compass problem (at least on the Wiko Fever 4G). If the Canvas has the same sensor, you have to put a /etc/init.d/30compass script as follow:
---CUT HERE
#!/system/bin/sh
# Adding Ecompass Daemon - By Sun75 @ XDA ####
su 0 setenforce 0
/system/bin/logwrapper /system/bin/akmd09911 &
##############################################
---CUT HERE
Make sure you have /xbin/su in your Rom, but in your's... there is!
Repack the Rom zip, and reflash it (you will lack Selinux permissions by adding with a Root explorer) with TWRP.
At next boot, your Msensord will fail starting the gsensor child daemon, but you will have the gsensor/compass daemon started as a separated daemon fixing the problem!
09-16 21:53:28.249 330 330 D MsensorDaemon: Msensor deamon statr!!!!!!!!!!!!
09-16 21:53:28.249 330 330 D MsensorDaemon: msensor demon start process detect demon name = akmd09911
09-16 21:53:28.249 330 330 D MsensorDaemon:
09-16 21:53:28.249 330 330 D MsensorDaemon: msensor demon start process detect demon prop = init.svc.akmd09911
09-16 21:53:28.249 330 330 D MsensorDaemon:
09-16 21:53:28.249 330 330 D MsensorDaemon: start_msensor_demon
09-16 21:53:28.500 330 330 D MsensorDaemon: do not USE_LIBC_SYSTEM_PROPERTIES
09-16 21:53:28.500 330 330 E MsensorDaemon: [99] ''
09-16 21:53:28.600 330 330 D MsensorDaemon: do not USE_LIBC_SYSTEM_PROPERTIES
09-16 21:53:28.601 330 330 E MsensorDaemon: [98] ''
09-16 21:53:28.701 330 330 D MsensorDaemon: do not USE_LIBC_SYSTEM_PROPERTIES
09-16 21:53:28.701 330 330 E MsensorDaemon: [97] ''
.....
09-16 21:53:38.324 330 330 E MsensorDaemon: [01] ''
09-16 21:53:38.424 330 330 D MsensorDaemon: do not USE_LIBC_SYSTEM_PROPERTIES
09-16 21:53:38.424 330 330 E MsensorDaemon: [00] ''
09-16 21:53:38.524 330 330 E MsensorDaemon: start daemon timeout!!
09-16 21:53:38.524 330 330 D MsensorDaemon: msensor demon start akmd09911 fail
09-16 21:53:38.524 330 330 D MsensorDaemon: Msensor deamon2 statr!!!!!!!!!!!!
09-16 21:53:38.525 330 330 D MsensorDaemon: open demon attr err = No such file or directory
-> and after:
09-16 21:53:29.396 448 448 I AKMD2 : AKMD 6D with Pseudo Gyro v20130531(Library for AK9911: v6.1.1.531) started.
09-16 21:53:29.396 448 448 I AKMD2 : Debug: ON
09-16 21:53:29.399 448 448 E AKMD2 : LoadPDC:106 fopen Error (No such file or directory).
Ignore the errors...
If your sensor is not the akm09911, you can find it yourself:
V:\Android\logs>adb shell cat /sys/bus/platform/drivers/msensor/chipinfo
akm09911 Chip
Ok, now open cpu-z or Mtk Engineering (Msensor data) and you will find your compass ready to use (and to calibrate!).
I have ported your all your RR Roms to Wiko Fever 4G fixing many problems, but not all:
- RR-N-v5.8.3-20170527-e481-Official -> VERY stable, compass and gps working, kernel 3.10.65 Stock, FM Radio and front flash NOT working
- RR-N-v5.8.4-20170903-E481-Release.zip -> instable, compass, FM Radio and gps working, kernel 3.10.65 Stock, front flash NOT working
- Resseruction Remix N 5.8.3 By Asfand.zip -> the MOST stable, compass and fm radio working, kernel 3.18.x (MM_V34 Stock), front flash AND gps NOT working. It's a pity that the kernel can not link /dev/stpgps and read /dev/ttyC2 (while it can on 3.10.x kernels!)... I reassembled the boot.img and edited the init.scripts many and many times trying everything... but, it's a no go, at least with the MM Kernel...
Ok, I think I have to open a new thread for the Wiko Fever releases, if you agree!
Click to expand...
Click to collapse
thank you so much , and please help us to fix front flash
Thanks in advance

Bro do you know how to make a volte patch?

--------- beginning of crash
09-17 11:46:21.913 302 302 F libc : CANNOT LINK EXECUTABLE "/system/bin/mtk_agpsd": cannot locate symbol "UCNV_TO_U_CALLBACK_STOP_53" referenced by "/system/bin/mtk_agpsd"...
09-17 11:46:21.913 302 302 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 302 (mtk_agpsd)
09-17 11:46:21.975 336 336 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
09-17 11:46:21.975 336 336 F DEBUG : LineageOS Version: '14.1-20170527-OFFICIAL-E481'
09-17 11:46:21.975 336 336 F DEBUG : Build fingerprint: 'Micromax/lineage_E481/E481:7.1.2/N2G47O/29cf694e04:userdebug/test-keys'
09-17 11:46:21.975 336 336 F DEBUG : Revision: '0'
09-17 11:46:21.975 336 336 F DEBUG : ABI: 'arm'
09-17 11:46:21.975 336 336 F DEBUG : pid: 302, tid: 302, name: mtk_agpsd >>> /system/bin/mtk_agpsd <<<
09-17 11:46:21.975 336 336 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
09-17 11:46:21.975 336 336 F DEBUG : r0 00000000 r1 0000012e r2 00000006 r3 00000008
09-17 11:46:21.975 336 336 F DEBUG : r4 f72e158c r5 00000006 r6 f72e1534 r7 0000010c
09-17 11:46:21.975 336 336 F DEBUG : r8 ff8502c8 r9 00000003 sl ff850300 fp f726f010
09-17 11:46:21.975 336 336 F DEBUG : ip 00000000 sp ff850260 lr f72c16a7 pc f72c209c cpsr 200f0010
09-17 11:46:22.197 336 336 F DEBUG :
09-17 11:46:22.197 336 336 F DEBUG : backtrace:
09-17 11:46:22.198 336 336 F DEBUG : #00 pc 0004609c /system/bin/linker (__dl_tgkill+12)
09-17 11:46:22.198 336 336 F DEBUG : #01 pc 000456a3 /system/bin/linker (__dl_pthread_kill+34)
09-17 11:46:22.198 336 336 F DEBUG : #02 pc 0003ded9 /system/bin/linker (__dl_raise+10)
09-17 11:46:22.198 336 336 F DEBUG : #03 pc 0003cb11 /system/bin/linker (__dl___libc_android_abort+34)
09-17 11:46:22.198 336 336 F DEBUG : #04 pc 0003bb14 /system/bin/linker (__dl_abort+4)
09-17 11:46:22.198 336 336 F DEBUG : #05 pc 0003da47 /system/bin/linker (__dl___libc_fatal+22)
09-17 11:46:22.198 336 336 F DEBUG : #06 pc 00009c43 /system/bin/linker (__dl__ZL29__linker_init_post_relocationR19KernelArgumentBlockj+3146)
09-17 11:46:22.198 336 336 F DEBUG : #07 pc 00008f63 /system/bin/linker (__dl___linker_init+358)
09-17 11:46:22.198 336 336 F DEBUG : #08 pc 000027c0 /system/bin/linker (_start+4)

Bro i got this
please help me

@sun75
Bravo! Have you opened the new thread for the Wiko Fever yet?
In other news, I have started work on a custom kernel based on the Wiko Fever MM source. I don't have much time to work on it though, so if anyone would like to help you can submit pull requests to the source here.

..

sun75 said:
I fixed LTE in build.prop, but I don't know how to to do a VoLTE patch: I'm not a developer, but a system engineer!
---------- Post added at 11:10 ---------- Previous post was at 10:56 ----------
I have already seen it:
just unpack the boot.img and edit the init.mt6735.rc. Diff format:
--- Line 21:
on init
+ export LD_SHIM_LIBS "/system/lib/libui.so|libshim_ui.so:/system/lib64/libui.so|libshim_ui.so:/system/lib/libgui.so|libshim_gui.so:/system/lib64/libgui.so|libshim_gui.so"
export USBOTG_STORAGE /storage/usbotg
mount tmpfs tmpfs /mnt/media_rw/ mode=0755,uid=1000,gid=1000
mkdir /mnt/media_rw/usbotg 0700 media_rw media_rw
mkdir /storage/usbotg 0700 root root
mount tmpfs tmpfs /storage/usbotg mode=0755,uid=1000,gid=1000
chmod 0666 /dev/kmsg
export USBOTG_STORAGE /storage/usbotg
-----
The export LD_ is ONE LINE!!
And:
---- Line 1286:
# GPS
service agpsd /system/bin/mtk_agpsd
class main
socket agpsd stream 660 gps system
socket agpsd2 stream 660 gps inet
socket agpsd3 stream 660 gps inet
user gps
group gps radio inet sdcard_r sdcard_rw misc
+ setenv LD_SHIM_LIBS "/system/bin/mtk_agpsd|libshim_agps.so"
service wifi2agps /system/bin/wifi2agps
--------
Repack the boot.img and reflash it with sp flash tool!
You have to make sure to have /system/[lib|lib64]/libshim_[agps|gui|ui].so
If you open with an hex editor libshim_agps.so you will find the symbol it'll search for!
---------- Post added at 11:37 ---------- Previous post was at 11:10 ----------
I'll open a Wiko Fever thread today, starting with this release: RR-N-v5.8.3-20170527-e481-Official -> RR-N-v5.8.3-20170527-l5460-Official.
Now I'm working on Stock Kernels only (they work on Stock images, they have to work on custom images... and, by the way, the 3.10.x custom based RR is working with the V39 Stock Kernel...): I miss the point on working with custom Kernels, the hardware is the same, what changes is only the OS layer. Please let me know your point of view, maybe in the Wiko thread, once opened. Thank you!
Click to expand...
Click to collapse
The main reasons for working on a custom kernel are:
To have a more up-to-date kernel (so with extra security and bug fixes)
To remove some unnecessary pre-installed bits making it smaller and therefore faster
Adding more tweaking options, such as custom governors, I/O schedulers, TCP congestion algorithms etc.
Add extra features, such as DT2W and Volte (looking at other android kernel sources helps with this)
Other tweaks and fixed if they come up and are needed
Besides, I'm a developer, and not a systems engineer

..

Thread Updated added TWRP 3.0.0 ported by Rick02
CrDROID and hexagon rom is on development
Hit the thank button

Gratitude
Really thankful to you man! Hats off:victory:
---------- Post added at 04:50 PM ---------- Previous post was at 04:47 PM ----------
Hope my heat issue resolves

Hello,
the Rom works fine and smoothly on my Wiko Fever 4g. The compass, front flash, UKW-Radio and Sim-Contacts are not working but I have restore the Contacts from Google.
When the display is on, it pulls up to 1.7 amps from the battery. I hope that there will be updates with bug fixes and security patches soon.
Otherwise good work.

NobodyDbg said:
Hello,
the Rom works fine and smoothly on my Wiko Fever 4g. The compass, front flash, UKW-Radio and Sim-Contacts are not working but I have restore the Contacts from Google.
When the display is on, it pulls up to 1.7 amps from the battery. I hope that there will be updates with bug fixes and security patches soon.
Otherwise good work.
Click to expand...
Click to collapse
i dont have wiko fever i only support mmx
sun75 will help you

Thanking
I would like to thanks XDA team . I have been waiting for months just for a single update for. MMX canvas 5 . Now this morning I found noighat for my phone . Thank you very much XDA team. Keep it on .

Rahul1436 said:
I would like to thanks XDA team . I have been waiting for months just for a single update for. MMX canvas 5 . Now this morning I found noighat for my phone . Thank you very much XDA team. Keep it on .
Click to expand...
Click to collapse
Thanks goes to Arshjot Singh
Hit the thanks button

Bug in Video playback
Harishwarrior said:
{
"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"
}
Lineage 14.1​
Arshjot singh made an another rom for Micromax Canvas 5.He puts his time ,Skills ,Effort and Brain on the line to make this awesome Rom.
Without wasting any further time. Lets get started.:fingers-crossed:
Requirements:
You must be in stock lollipop rom , whether it's Rooted or Non rooted
How to install :
1. Download and copy the Rom to your SD card.
2. Backup your Rom using TWRP recovery.
3. Format data and Wipe Factory reset your Phone.
4. Flash the Rom.
5. Change the language.
6. Go to developer option, and set the Animation to 0.5
7. Google apps are not included due to some reason. Go the Google apps link,and select ARM 64 as platform , 7.1 as android,pico as variant.download and flash the zip.
8. Dont install Google system webview otherwise your app will crash
Links:
Lineage 14.1 : https://drive.google.com/uc?id=0B9ToB3iQjd_-eWhuTU1tcnFod00&export=download
TWRP 2.8.7.0: https://forum.xda-developers.com/an...overy-twrp-2-8-7-0-micromax-canvas-5-t3641576
TWRP 3.0.0: https://forum.xda-developers.com/android/development/twrp-3-0-0-micromax-canvas-5-e481-t3677085
Google Apps : http://opengapps.org/
Bugs:
1. Front flash (Not necessary)the default camera app has Selfie flash option try that.
2.Compass (Useless) google maps works without Compass.
Heat Fix:
ONLY TRY THIS , IF YOU FACING HEATING ISSUE .Download and Open kernel Aduitor (Grant root permission)and Go to cpu , select apply on boot , Change the maximum frequency to 1040 Mhz .This will reduces the heat.
CREDITS::angel:
Thanks to
Arshjot singh for Lineage
Infinite4evr for TWRP 2.8.7.0
Rick02::fingers-crossed: for TWRP 3.0.0
Harishwarrior(Me) Moderator.
If you have any ideas or bug fix , Post it down.
This post will be updated Daily or Weekly.Stay tuned
Hit the thanks button......
Click to expand...
Click to collapse
Hello,
I assume that you have already observed bug in video playback issue with this rom.
Solution provided here is for high quality videos but the same can not work for low quality videos.
Is there any known fix for low quality video & formats like .3gpp ??

QUIZILLA said:
Hello,
I assume that you have already observed bug in video playback issue with this rom.
Solution provided here is for high quality videos but the same can not work for low quality videos.
Is there any known fix for low quality video & formats like .3gpp ??
Click to expand...
Click to collapse
Try SW Decoder or use stock video player(Gallery)

[Guide] Install LineageOS/AOSP keyboard on any phone

You may want to use the LineageOS keyboard with some other rom. Just installing the .apk file will result in the keyboard crashing. We can install the required files manually to get the keyboard working. This requires root, but does not require any changes to /system
Getting the files
It's best to get the files from a real LOS rom, but if you don't have one you can extract them out of a rom. Download the official rom, then extract payload.bin with https://github.com/cyxx/extract_android_ota_payload. Then mount the system.img into an empty folder
Code:
mkdir temp
sudo mount system.img temp
Grab the files system/app/LatinIME/LatinIME.apk and system/lib64/libjni_latinime.so and put them on your phone
Installing
Install the apk like normal. Then you will have to copy the lib into /data
Code:
cmd list packages -f | grep inputmethod.latin
go to that folder and copy the lib into lib/arm64. This most likely needs root. Make sure to change the permissions
Code:
# cd /data/app/com.android.input.method.latin-whatever==/
# cd lib
# mkdir arm64
# chown system:system arm64
# cd arm64
# cp /sdcard/libjni_latinime.so ./
# chown system:system libjni_latinime.so
# chmod 644 libjni_latinime.so
The keyboard should now start without crashing.

phailyoor said:
You may want to use the LineageOS keyboard with some other rom. Just installing the .apk file will result in the keyboard crashing. We can install the required files manually to get the keyboard working. This requires root, but does not require any changes to /system
Getting the files
It's best to get the files from a real LOS rom, but if you don't have one you can extract them out of a rom. Download the official rom, then extract payload.bin with https://github.com/cyxx/extract_android_ota_payload. Then mount the system.img into an empty folder
Grab the files system/app/LatinIME/LatinIME.apk and system/lib64/libjni_latinime.so and put them on your phone
Installing
Install the apk like normal. Then you will have to copy the lib into /data
go to that folder and copy the lib into lib/arm64. This most likely needs root. Make sure to change the permissions
The keyboard should now start without crashing.
Click to expand...
Click to collapse
@phailyoor would you mind making this a magisk module? I was unable to get it to work by doing it manually. Tried getting it to work on OOS and had no luck

I don't really have experience with magisk, so I probably won't be making one anytime soon.
Did you get an error when following the steps? If not post the permissions by running ls -l and include logcat of the crash

phailyoor said:
You may want to use the LineageOS keyboard with some other rom. Just installing the .apk file will result in the keyboard crashing.
Click to expand...
Click to collapse
I installed following AOSP-alike keyboard provided via F-Droid, without any manual step needed! But good to know what is needed to do it manually! :good:
Simple Keyboard (Simply keyboard and nothing more)
https://f-droid.org/app/rkr.simplekeyboard.inputmethod

phailyoor said:
You may want to use the LineageOS keyboard with some other rom. Just installing the .apk file will result in the keyboard crashing. We can install the required files manually to get the keyboard working. This requires root, but does not require any changes to /system
Getting the files
It's best to get the files from a real LOS rom, but if you don't have one you can extract them out of a rom. Download the official rom, then extract payload.bin with github.com/cyxx/extract_android_ota_payload[/URL]. Then mount the system.img into an empty folder
Code:
mkdir temp
sudo mount system.img temp
Grab the files system/app/LatinIME/LatinIME.apk and system/lib64/libjni_latinime.so and put them on your phone
Installing
Install the apk like normal. Then you will have to copy the lib into /data
Code:
cmd list packages -f | grep inputmethod.latin
go to that folder and copy the lib into lib/arm64. This most likely needs root. Make sure to change the permissions
Code:
# cd /data/app/com.android.input.method.latin-whatever==/
# cd lib
# mkdir arm64
# chown system:system arm64
# cd arm64
# cp /sdcard/libjni_latinime.so ./
# chown system:system libjni_latinime.so
# chmod 644 libjni_latinime.so
The keyboard should now start without crashing.
Click to expand...
Click to collapse
Thank you so much for the detailed guide! I did this all without a hitch and AOSP now works on my OxygenOS. However, I noticed that glide typing doesn't work. Do you have any idea how to enable this feature? I would really really appreciate any help!
Edit: nevermind I figured it out (credits to this post: android.stackexchange.com/a/187686 ); if you download the libjni_latinimegoogle.so library from the openGapps github repo, and do the exact same process you do above for libjni_latinime.so, it enables gesture typing.

I cannot get it to work using your method (Running Android Pie, Google Pixel 2)
Logcat below, what went wrong?
Code:
12-11 20:05:46.011 5765 5765 W SubtypeLocaleUtils: KeyboardLayoutSet not found, use QWERTY: locale=en_AU extraValue=TrySuppressingImeSwitcher,AsciiCapable,SupportTouchPositionCorrection,EmojiCapable
12-11 20:05:46.014 5765 5765 W RichInputMethodSubtype: Can't find emoji subtype
12-11 20:05:46.014 5765 5765 W RichInputMethodSubtype: No input method subtype found; returning dummy subtype: Multi-lingual subtype: [email protected], zz
12-11 20:05:46.076 5765 5765 E putmethod.lati: No implementation found for long com.android.inputmethod.keyboard.ProximityInfo.setProximityInfoNative(int, int, int, int, int, int, int[], int, int[], int[], int[], int[], int[], float[], float[], float[]) (tried Java_com_android_inputmethod_keyboard_ProximityInfo_setProximityInfoNative and Java_com_android_inputmethod_keyboard_ProximityInfo_setProximityInfoNative__IIIIII_3II_3I_3I_3I_3I_3I_3F_3F_3F)
12-11 20:05:46.078 5765 5765 D AndroidRuntime: Shutting down VM
12-11 20:05:46.081 5765 5765 E AndroidRuntime: FATAL EXCEPTION: main
12-11 20:05:46.081 5765 5765 E AndroidRuntime: Process: com.android.inputmethod.latin, PID: 5765
12-11 20:05:46.081 5765 5765 E AndroidRuntime: android.view.InflateException: Binary XML file line #29: Binary XML file line #21: Error inflating class com.android.inputmethod.keyboard.emoji.EmojiPalettesView
12-11 20:05:46.081 5765 5765 E AndroidRuntime: Caused by: android.view.InflateException: Binary XML file line #21: Error inflating class com.android.inputmethod.keyboard.emoji.EmojiPalettesView
12-11 20:05:46.081 5765 5765 E AndroidRuntime: Caused by: java.lang.reflect.InvocationTargetException
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at java.lang.reflect.Constructor.newInstance0(Native Method)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at java.lang.reflect.Constructor.newInstance(Constructor.java:343)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at android.view.LayoutInflater.createView(LayoutInflater.java:647)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:790)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at android.view.LayoutInflater.parseInclude(LayoutInflater.java:965)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at android.view.LayoutInflater.rInflate(LayoutInflater.java:859)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at android.view.LayoutInflater.rInflateChildren(LayoutInflater.java:824)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at android.view.LayoutInflater.inflate(LayoutInflater.java:515)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at android.view.LayoutInflater.inflate(LayoutInflater.java:423)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at android.view.LayoutInflater.inflate(LayoutInflater.java:374)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at com.android.inputmethod.keyboard.KeyboardSwitcher.onCreateInputView(KeyboardSwitcher.java:464)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at com.android.inputmethod.latin.LatinIME.onCreateInputView(LatinIME.java:789)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at android.inputmethodservice.InputMethodService.updateInputViewShown(InputMethodService.java:1427)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at android.inputmethodservice.InputMethodService.showWindowInner(InputMethodService.java:1833)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at android.inputmethodservice.InputMethodService.showWindow(InputMethodService.java:1801)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at android.inputmethodservice.InputMethodService$InputMethodImpl.showSoftInput(InputMethodService.java:570)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at android.inputmethodservice.IInputMethodWrapper.executeMessage(IInputMethodWrapper.java:207)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at com.android.internal.os.HandlerCaller$MyHandler.handleMessage(HandlerCaller.java:37)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at android.os.Handler.dispatchMessage(Handler.java:106)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at android.os.Looper.loop(Looper.java:193)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at android.app.ActivityThread.main(ActivityThread.java:6669)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at java.lang.reflect.Method.invoke(Native Method)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: Caused by: java.lang.UnsatisfiedLinkError: No implementation found for long com.android.inputmethod.keyboard.ProximityInfo.setProximityInfoNative(int, int, int, int, int, int, int[], int, int[], int[], int[], int[], int[], float[], float[], float[]) (tried Java_com_android_inputmethod_keyboard_ProximityInfo_setProximityInfoNative and Java_com_android_inputmethod_keyboard_ProximityInfo_setProximityInfoNative__IIIIII_3II_3I_3I_3I_3I_3I_3F_3F_3F)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at com.android.inputmethod.keyboard.ProximityInfo.setProximityInfoNative(Native Method)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at com.android.inputmethod.keyboard.ProximityInfo.createNativeProximityInfo(ProximityInfo.java:222)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at com.android.inputmethod.keyboard.ProximityInfo.<init>(ProximityInfo.java:81)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at com.android.inputmethod.keyboard.Keyboard.<init>(Keyboard.java:123)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at com.android.inputmethod.keyboard.internal.KeyboardBuilder.build(KeyboardBuilder.java:196)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at com.android.inputmethod.keyboard.KeyboardLayoutSet.getKeyboard(KeyboardLayoutSet.java:232)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at com.android.inputmethod.keyboard.KeyboardLayoutSet.getKeyboard(KeyboardLayoutSet.java:204)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at com.android.inputmethod.keyboard.emoji.EmojiCategory.getKeyboard(EmojiCategory.java:374)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at com.android.inputmethod.keyboard.emoji.EmojiCategory.addShownCategoryId(EmojiCategory.java:223)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at com.android.inputmethod.keyboard.emoji.EmojiCategory.<init>(EmojiCategory.java:176)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at com.android.inputmethod.keyboard.emoji.EmojiPalettesView.<init>(EmojiPalettesView.java:119)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: at com.android.inputmethod.keyboard.emoji.EmojiPalettesView.<init>(EmojiPalettesView.java:95)
12-11 20:05:46.081 5765 5765 E AndroidRuntime: ... 24 more
12-11 20:05:46.089 1183 1200 I ActivityManager: Showing crash dialog for package com.android.inputmethod.latin u0

My phone is not rooted, is there a way to install this keyboard without root? If not, can someone make that possible, thanks in advance.

Magisk module of LineageOS AOSP keyboard
Magisk module of LineageOS AOSP keyboard.
I put in attachment two magisk modules: laosime4arm32android81-1_0.zip - for arm32 architecture, laosime4arm64android81-1_0.zip - for arm64 architecture. Both modules are for android 8.1. I do not have devices with newer versions of android to test.
Also it's simple to manufacture versions for other versions of android: just replace LatinIME.apk and libjni_latinime.so inside zip to proper files from LineageOS appropriate distribution.

raven428 said:
Magisk module of LineageOS AOSP keyboard.
Click to expand...
Click to collapse
Thank you very much! I will test this on my Google Pixel 2 (Android 9).

SGH-i200 said:
Thank you very much! I will test this on my Google Pixel 2 (Android 9).
Click to expand...
Click to collapse
Works?

works on Miui 10?

I updated the keyboard apk, lib files and script to update with AOSP Keyboard 9.0 for Android Pie. Just flash in Magisk as a regular module and reboot. Credit goes to Raven428 for the original module, thank you! I flashed this on my Pixel 3a and OnePlus 6T and works fine. Make sure you have a good backup prior to just in case. If you want it to be Transparent then consider my Translucent Substratum theme (shameless plug lol)

some have modules for android 8.0 ?

Archangel said:
I updated the keyboard apk, lib files and script to update with AOSP Keyboard 9.0 for Android Pie. Just flash in Magisk as a regular module and reboot. Credit goes to Raven428 for the original module, thank you! I flashed this on my Pixel 3a and OnePlus 6T and works fine. Make sure you have a good backup prior to just in case. If you want it to be Transparent then consider my Translucent Substratum theme (shameless plug lol)
Click to expand...
Click to collapse
Man, thank you! Is there any way you can make it as a twrp flashable zip? It hangs sometimes via the module & I'd like to see if flashing it directly into the system speeds it up.

Sure, I am out of town right now so when I get back I can slide it into a zip
peestandingup said:
Man, thank you! Is there any way you can make it as a twrp flashable zip? It hangs sometimes via the module & I'd like to see if flashing it directly into the system speeds it up.
Click to expand...
Click to collapse

Archangel said:
I updated the keyboard apk, lib files and script to update with AOSP Keyboard 9.0 for Android Pie. Just flash in Magisk as a regular module and reboot. Credit goes to Raven428 for the original module, thank you! I flashed this on my Pixel 3a and OnePlus 6T and works fine. Make sure you have a good backup prior to just in case. If you want it to be Transparent then consider my Translucent Substratum theme (shameless plug lol)
Click to expand...
Click to collapse
In Lineage OS the swipe function only worked in connection with the Google Apps. I have Google Apps on my phone installet, but the swipe function still doesn't work. I guess this has something to do with customizations?
Is there anything you can do?

Yeah swipe function isnt working for me either, when I get a chance I will troubleshoot it to see if it can be fixed
tiga05 said:
In Lineage OS the swipe function only worked in connection with the Google Apps. I have Google Apps on my phone installet, but the swipe function still doesn't work. I guess this has something to do with customizations?
Is there anything you can do?
Click to expand...
Click to collapse

@Archangel
I did some research about this topic and found out, that you need a specific closed source file.
It's name is : libjni_latinimegoogle.so
It gets installed with the google keyboard. Some pages say you can manually copy it in a specific folder and than it should work.
Had no time to try it out. But will try this later.
Maybe it helps you!
Edit: OK I had the 5 minutes to try it .
It works!
Just take the .so file for example from here ( I took them from the current downloadable opengapps):
https://gitlab.opengapps.org/opengapps/arm64/blob/master/lib64/23/libjni_latinimegoogle.so
And put them into system/lib64.
Maybe you have to restart your smartphone. And then it works! Do you see any possibility to add this to your magisk module?

Here is the new Magisk Module with the .so included let me know if you have any problems flashing it in Magisk
https://www.dropbox.com/s/t83w56bpp616vqh/AOSPKeyBoardV9MagiskModule.zip?dl=0
tiga05 said:
@Archangel
I did some research about this topic and found out, that you need a specific closed source file.
It's name is : libjni_latinimegoogle.so
It gets installed with the google keyboard. Some pages say you can manually copy it in a specific folder and than it should work.
Had no time to try it out. But will try this later.
Maybe it helps you!
Edit: OK I had the 5 minutes to try it .
It works!
Just take the .so file for example from here ( I took them from the current downloadable opengapps):
https://gitlab.opengapps.org/opengapps/arm64/blob/master/lib64/23/libjni_latinimegoogle.so
And put them into system/lib64.
Maybe you have to restart your smartphone. And then it works! Do you see any possibility to add this to your magisk module?
Click to expand...
Click to collapse

@Archangel Sorry to bother, but I seem to have an issue with the Magisk module (and with LatinIME in general). On my Lenovo Vibe K5 on MoKee 8.1.0, LatinIME crashes, even though the libs are installed and with their permissions set. Any help?
Here's a link to the bugreport: https://paste.ubuntu.com/p/JVWDXvBS4B/
EDIT: After I deleted manually the files libjni_latinime.so and the folder LatinIME inside /system/lib64/ and /system/app/ respectively, a reinstall of the module got the app finally working.

[CLOSED][J2 lte] Found a working Nougat kernel on GitHub

Deleted

TBM 13 said:
Hey guys, i just found a Nougat kernel for Exynos3475, and i built it for the J2. It's able to get to the boot animation of a Nougat ROM.
I'm a noob on this, so i didn't managed to fix the errors that prevent ROM from booting.
There is also a CM-14.1 device tree for our device.
Here is the link:
https://github.com/Exynos3475
All credits to the developers. Remember to ask they permissions to share something.
I hope that someone more experienced, with the approval of the devs, manages to get Nougat/CM 14.1 fully working and shares it to this community.
Click to expand...
Click to collapse
You can try on your own it seems?
On5 and On5 Pro (same chipset) has LineageOS for long already.
These should be used in build tree.
-kernel: https://github.com/Exynos3475/android_kernel_samsung_exynos3475
>> please add your own defconfig file in <your device kernel>/arch/arm/configs to that one
-exynos3475: https://github.com/Exynos3475/android_device_samsung_exynos3475-common
-j2lte: https://github.com/Exynos3475/android_device_samsung_j2lte
the vendor tree should be created on your own. Take On5 Pro as reference.
bug(s) should be the same as this one https://forum.xda-developers.com/samsung-galaxy-on5/development/rom-lineageos-rom-14-1-t3821807
I cannot try this since I dont have a J2 LTE, and Im already busy with Samsung Blowfish in AOSP for J2 Prime so..
Good Luck!

Prove N. said:
You can try on your own it seems?
On5 and On5 Pro (same chipset) has LineageOS for long already.
These should be used in build tree.
-kernel: https://github.com/Exynos3475/android_kernel_samsung_exynos3475
>> please add your own defconfig file in <your device kernel>/arch/arm/configs to that one
-exynos3475: https://github.com/Exynos3475/android_device_samsung_exynos3475-common
-j2lte: https://github.com/Exynos3475/android_device_samsung_j2lte
the vendor tree should be created on your own. Take On5 Pro as reference.
bug(s) should be the same as this one https://forum.xda-developers.com/samsung-galaxy-on5/development/rom-lineageos-rom-14-1-t3821807
I cannot try this since I dont have a J2 LTE, and Im already busy with Samsung Blowfish in AOSP for J2 Prime so..
Good Luck!
Click to expand...
Click to collapse
Thank you and don't worry, i already built the kernel and everything.
Tried to boot On5 Pro stock ROM. It doesn't matters if i put propietary blobs on it or not, the problem is the same:
It's stuck in the boot animation waiting forever for the service "edmnativehelper" but it has a problem:
Code:
01-01 13:11:53.552 2448 2448 E logwrapper: executing /system/bin/iptables-restore failed: No such file or directory
01-01 13:11:53.554 2041 2041 E Netd : /system/bin/iptables-restore failed with res=0, status=65280
01-01 13:11:53.555 2449 2449 E logwrapper: executing /system/bin/ip6tables-restore failed: No such file or directory
01-01 13:11:53.556 2041 2041 E Netd : /system/bin/ip6tables-restore failed with res=0, status=65280
01-01 13:11:53.593 2452 2452 E logwrapper: executing /system/bin/iptables-restore failed: No such file or directory
01-01 13:11:53.594 2041 2041 E Netd : /system/bin/iptables-restore failed with res=0, status=65280
01-01 13:11:53.595 2453 2453 E logwrapper: executing /system/bin/ip6tables-restore failed: No such file or directory
01-01 13:11:53.596 2041 2041 E Netd : /system/bin/ip6tables-restore failed with res=0, status=65280
01-01 13:11:53.632 2456 2456 E logwrapper: executing /system/bin/iptables-restore failed: No such file or directory
01-01 13:11:53.633 2041 2041 E Netd : /system/bin/iptables-restore failed with res=0, status=65280
01-01 13:11:53.634 2457 2457 E logwrapper: executing /system/bin/ip6tables-restore failed: No such file or directory
01-01 13:11:53.635 2041 2041 E Netd : /system/bin/ip6tables-restore failed with res=0, status=65280
Also, i don't build Android/LOS at the moment. Maybe in a future.
Btw you still working on AOSP for the J2 Prime? i also have that device haha. I hope it doesn't eats my cat.

TBM 13 said:
Don't worry, i already built the kernel and everything.
Tried to boot On5 Pro stock ROM. It doesn't matters if i put propietary blobs on it or not, the problem is the same:
It's stuck in the boot animation waiting forever for the service "edmnativehelper" but it has a problem:
Code:
01-01 13:11:53.552 2448 2448 E logwrapper: executing /system/bin/iptables-restore failed: No such file or directory
01-01 13:11:53.554 2041 2041 E Netd : /system/bin/iptables-restore failed with res=0, status=65280
01-01 13:11:53.555 2449 2449 E logwrapper: executing /system/bin/ip6tables-restore failed: No such file or directory
01-01 13:11:53.556 2041 2041 E Netd : /system/bin/ip6tables-restore failed with res=0, status=65280
01-01 13:11:53.593 2452 2452 E logwrapper: executing /system/bin/iptables-restore failed: No such file or directory
01-01 13:11:53.594 2041 2041 E Netd : /system/bin/iptables-restore failed with res=0, status=65280
01-01 13:11:53.595 2453 2453 E logwrapper: executing /system/bin/ip6tables-restore failed: No such file or directory
01-01 13:11:53.596 2041 2041 E Netd : /system/bin/ip6tables-restore failed with res=0, status=65280
01-01 13:11:53.632 2456 2456 E logwrapper: executing /system/bin/iptables-restore failed: No such file or directory
01-01 13:11:53.633 2041 2041 E Netd : /system/bin/iptables-restore failed with res=0, status=65280
01-01 13:11:53.634 2457 2457 E logwrapper: executing /system/bin/ip6tables-restore failed: No such file or directory
01-01 13:11:53.635 2041 2041 E Netd : /system/bin/ip6tables-restore failed with res=0, status=65280
Also, i don't build Android/LOS at the moment. Maybe in a future.
Btw you still working on AOSP for the J2 Prime? (i also have that device haha)
Click to expand...
Click to collapse
I am. Just got summer vacation yesterday which gives me heaven of time. Redo-ing cm13.
And the one problem persists is / cannot open Gatekeeper HAL / (or some sorts). Gatekeeper keeps trying to call TZDaemon (Samsung Trustzone) and fails. This is eng build, boot in permissive..
Old stuffy
(even weirder, old ROM with SubZero tree + cyanogen_mt6735-common booted up for me. There werent any reference to TZd lol )
^ correction to this. There WAS one. When it tried to turn on Wi-Fi, which called tzd for stored stuffs like password and certificate, it failed of course, and caused phone to bootloop which is what I experienced.
__
out of context, for your device, make an eng build with added blobs and permissive them?
> (in the future)

Prove N. said:
I am. Just got summer vacation yesterday which gives me heaven of time. Redo-ing cm13.
And the one problem persists is / cannot open Gatekeeper HAL / (or some sorts). Gatekeeper keeps trying to call TZDaemon (Samsung Trustzone) and fails. This is eng build, boot in permissive..
Old stuffy
(even weirder, old ROM with SubZero tree + cyanogen_mt6735-common booted up for me. There werent any reference to TZd lol )
^ correction to this. There WAS one. When it tried to turn on Wi-Fi, which called tzd for stored stuffs like password and certificate, it failed of course, and caused phone to bootloop which is what I experienced.
__
out of context, for your device, make an eng build with added blobs and permissive them?
> (in the future)
Click to expand...
Click to collapse
Well, i wish you good luck!
With make an eng build i think that you mean when i'm able to build LOS right?
Around 30 GB is too much for my internet. Also i don't use Linux at all, just WSL so i'm not sure if it will be compatible.
Btw, i disabled this:
https://github.com/Exynos3475/andro...m-14.1-20180513/ramdisk/init.samsung.rc#L1547
The waiting for the service edmnativehelper isn't anymore but the problem stills there, so maybe it's a Netd problem and the edmnativehelper service was waiting for it.

Are you still working on it??
Would really like to see this device running nouget, but also would like to stay stock.
I really like On5 port for J2LTE, was't bugfree but debugged most of them.

Bad.Wolf said:
Are you still working on it??
Would really like to see this device running nouget, but also would like to stay stock.
I really like On5 port for J2LTE, was't bugfree but debugged most of them.
Click to expand...
Click to collapse
Well, i did a few tries to build LOS 14.1. It builds successfully and i get to the boot animation, but then i get some weird problem and i can't find nothing about it on Google.
Also, Izzy (the one that made that kernel and the device tree for our phone) told me that he wasn't able to boot LOS 14.1 in our phone and it seems that he isn't working anymore on this.
We just need someone experienced to continue his work.

Thread closed as per request of op

Lineage 17.1 *UNOFFICIAL* for FIH (SAT/SS2/HH1/HH6/HD1/DRG)

Android 11 here: Lineage 18.1 *UNOFFICIAL* for Sharp Aquos S2, S3 (SAT/SS2/HH1/HH6)
LEGAL
https://lineageos.org/legal/
You flash this ROM on own risk!
XDA:DevDB Information
Lineage 17 *UNOFFICIAL* for Sharp Aquos S2, S3 (SAT/SS2/HH1/HH6)
Multi ROM from sources supporting devices:
Sharp Aquos S2 4/64 -SS2/C10,
Sharp Aquos S2 6/128 -SAT,
Sharp Aquos S3 -sdm630 (HH1/HH6).
Sharp Aquos P6
Nokia x6 (DRG)
Contributors/Maintainers
heineken78
ROM OS Version: Android 10
ROM Kernel: CAF 4.4.205
ROM Firmware Required: Minimum update installed 2130WW/CN -for S2. For S3 - D350KR, Nokia DRG - Android 9-10.
Based On: Android 10- Lineage 17.1
Recovery: TWRP included.
Device sources: here
Gapps: Not included. Recommend to use only NANO version, because it includes necessary apps like Welbeing
Data Encryption: encrypted;
Do not: use boot(twrp) or vendor with other older/stock roms.
Version Information
Status: Beta
Created 2019-11-03
Last Updated LOS 17.1 2020-09-02
Sources: https://github.com/Eddie07
DOWNLOAD:
Gdrive folder
Changelog 02.09.2020:
Lineage OS 17.1 02/09/20 for SAT/SS2/HH6/HD1
-kernel: optimize power driver;
-kernel: fix mdsi panel on from suspend crushes;
-vendor/system:implement from sources Bluetooth QTI;
-vendor/System:implement from sources perf QTI;
-vendor/system:implement com.qualcomm.gps and drivers from sources;
-kernel/system/vendor: new touchscreen gestures;
-system: more options for Android 10 gestures;
-system: disable magnet sensor;
-system: implement new telecom framework from sources;
-system: sim toogle swithes;
-vendor/system: audio enhancements.
-selinux fixes;
-GSI:flash and go.
-other.
Changelog 07.08.2020:
-remove restrictions for audio records
-fixed auto recording option in Dialer
-icon packs support option for LA Trebuchet: nova, etc.
-long screenshot (Q from ASUS);
-enabled show mv of QC in lockscreen.
-fixes screen on bug after suspend
Changelog 02.08.2020:
Kernel:
-Livedisplay for S2 & S3 & NOkia DRG; -Fast charging S2;
System:
-ARcore support without Magisk;
-Dialer: autorecording;
-Quick internet change via QCTiles (multisim); -Imitation of wifi for android when using a mobile network: persist.force.unmetered = true: -Display Profiles (4) for S2 & S3
Vendor:
- updating halls; - selinux fixes; - fix for gsi boot; - other garbage to make everything work.
Changelog 13.05.2020:
-updated recovery 3.4.0: supports OTA updates, key decryption works;
-added custom face unlock: may need to assign camera perms manually;
-fixed sensors init issue;
-updated vendor.
Note: due to fixes in encryption this version needs fresh boot after format! Backup your data.
Use old backup, and apply gapps zip only after the first boot of system, dont boot to recovery after formatting.
LOS 17.1 beta 13b-04-2020
-fixed selinux denials: sensors issue, ril;
LOS 17.1 beta 13-04-2020
-LOS Android update android-10.0.0_r33 (05.04)
-added Nokia DRG (x6) support
-fixed configs media -front camera video fail fix in gcam.
-updated audio configs to Q.
-selinux still in testing.
LOS 17.1 beta 23-02-2020
-Able to disable sim card (if 2)- experimental;
-Lineage vendor implementations: Off screen gestures; Adjustable vibrations ( 3 levels);- More overlays.
- yuv support;
Also:
Kernel:
Power, sound, display changes, updated latest wifi driver. Also defined min brightness and tfa chip switching via nodes.
System:
Extra Minimum brightness option, reorganized, added settings, implementation of google personalisation (work but Screen Attention fails) no need gapps. 6x5 grid for launcher, option to add quick tile rows.
Vendor:
Made real blue accent color pickable, sound chip tweaking.
Still to do:virtual displays and wfd. (I think problem is hwc sources, need fix later)
LOS 17.1 daily 04-02-2020
-VENDOR: fixes wifi sharing (want working in last two builds), fixed diag_lsm error,
added support of external usb cameras.
LOS 17.1 daily 02-02-2020
-KERNEL: power drain fix to all previous kernels from 28.12 due hotplug conflict with PERF2.0 hal;
merged with LA.UM.8.2.r2-00700-sdm660.0;
updated qcacld (wifi);
not tested with s3.
-SYSTEM: Latest LOS updates, more telephony implementations from nokia stock Q;
-VENDOR: LOS updates, qcom caf updates, more display implementations.
LOS 17.1 test 08-01-2020
-New LOS Android;
-Kernel battery control changes (s2)
-gps enchantment, phone enchantments.
05-01-2020
-kernel: thermal related fixes.
-system: Snap camera replace by stock FIH cam, qcom ril framework blobs remade.
-vendor: manual network selection fix, new thermal impl.Fixed compatibility with GSI roms: camera and softkey navigation bar enabled.
25-12-2019
Kernel:
-merged 4.4.205;
-camera fix for gcam, dualcam; use this cam with dualcam enabled.
If gcam keeps crashing disable dualcam: persist.vendor.camera.expose.aux=0
-showing battery type (C10/S2);
System and Vendor:
-LOS up-to-date;
-implementation on new qcom encryption, booting faster;
-LOS beta circle battery icon ;
Note if you find that media folder is not getting encrypted with key/password - make full format from twrp and boot with current version.
14-12-2019
service pak N141219
28-11-2019
kernel: changes in kernel config
system: LOS 17.1 upd up 27.11
vendor: upd ril, qti, camera blobs, fixed PERF drain, fix bt lags, add APTX Bt codec.
-Rounded corners can be now disabled via vendor/build.prop.
-GUI of S3 of S2 can be chosen from developers settings (remain for GSI too)
17-11-2019
Update Android 10.0.0_r11
15-11-2019
-supports Sharp Aquos S3 models -HH1 and HH6!
-Los up-to-date
05-11-2019
-kernel updated to 4.4.194 (caf LA.UM.8.2.r1-04800-sdm660.0)
-CAMERA: latest camera vendor blobs Q from 2060 Nokia PL2 (test option prop persist.cam.dv=(PL2/B2N/C1N) for camera hal)
-PERFORMANCE: PERF 2.0 fixed
-LINEAGE: current Lineage updates from mainstream(not much)
-SOUND: revert to stock soundtrigger
-VNDK rebuild with Q rules
-added many enhancements in build.props
03-11-2019
First release
Installation
1. First time
Enter twrp or from fastboot and flash images: boot, system, vendor. Reboot back recovery and format data. Install Gapps same time (as option).Reboot to new system.
2. Next updates/upgrades
Enter twrp and flash new images. If you had installed Gapps, flash same zip file o gapps. Reboot to system.
Pls note: Due to changes in encryption, if your data is before July 2020, you will have to format data to be able to use newer roms.
Bugs:
-Minor LOS bugs.
-You will find may be
Please donate if you want to support my work.

I'm testing rom from yesterday. Updated from treble 3.4
Does't show % battery in status bar and the battery icon can't be changed.
There is a problem when I kill applications, it shows a problem with the launcher - operation stops and cant kill applikactions.
Some app from playstore like revolut isn't compatybile with 17.
Gcam working.
Thx for great work.

iiandrusii said:
I'm testing rom from yesterday. Updated from treble 3.4
Does't show % battery in status bar and the battery icon can't be changed.
There is a problem when I kill applications, it shows a problem with the launcher - operation stops and cant kill applikactions.
Some app from playstore like revolut isn't compatybile with 17.
Gcam working.
Thx for great work.
Click to expand...
Click to collapse
% of battery is still to do (Linage bug), there are others too..
About error, may be its because of current launcher problem. I don't have such.

I used vendor rom gsi I installed the camera and the flash didn't work

amiali said:
I used vendor rom gsi I installed the camera and the flash didn't work
Click to expand...
Click to collapse
I'm not able to test GSI's, pls bugs with LOS17 system/vendor. Try another GSI.

I tested three gsi models. The camera and the flash don't work

Hello heineken78. First of all thank you very much for all your work and help with this device.
I wanted to report 3 problems I saw with the ROM:
1) I cannot use NFC: when placing the NFC card near the phone NFC trigger reacts (it blocks, disables and enables) but it doesn't seem to work. The same works, for example, on 4.1. Is there something I could try?
2) I couldn't find a way to disable fingerprint actions on screen on when using gestures, which makes it trigger sometimes accidentally.
3) Data doesn't seem to be encrypted. When accessing TWRP it doesn't ask for a password and I can read sdcard without issues. Not sure if this is common with Android 10 as of yet.
Other than that, the ROM seems to be working perfectly, which is a lot since Android Q is really new.
Thanks!

jokolom said:
1) I cannot use NFC: when placing the NFC card near the phone NFC trigger reacts (it blocks, disables and enables) but it doesn't seem to
work. The same works, for example, on 4.1. Is there something I could try?
Click to expand...
Click to collapse
NFC works, people use safetynetfix and pay with gpay app
jokolom said:
2) I couldn't find a way to disable fingerprint actions on screen on when using gestures, which makes it trigger sometimes accidentally.
Click to expand...
Click to collapse
to do
jokolom said:
3) Data doesn't seem to be encrypted. When accessing TWRP it doesn't ask for a password and I can read sdcard without issues. Not sure if this is common with Android 10 as of yet.
Click to expand...
Click to collapse
encrypted, even password will not match in TWRP, cos TWRP uses old keymaster sources.

heineken78 said:
NFC works, people use safetynetfix and pay with gpay app
to do
encrypted, even password will not match in TWRP, cos TWRP uses old keymaster sources.
Click to expand...
Click to collapse
I have reinstalled LOS17 to retry these things on my phone, and this is the summary:
- Encryption: OK. I have now verified that after installing the ROM, wiping data and rebooting, data in TWRP shows as encrypted even though password will not match like you say (file names appear as garbled characters) so this seems to be working OK.
- NFC: I still cannot make NFC work. I have installed safetypatch on Magisk, CTS profile and basic integrity show as OK on Magisk. Not sure what makes NFC not work, maybe I'm missing something.
- Notification LED: I cannot see notification LED working after receiving a notification, such as Whatsapp.
- Warning message on boot: a warning message triggers on system reboot. This is a minor detail since it's just an informative message.
Other than that, everything seems to be working correctly. I will keep using this ROM as a daily driver and report any other problem I can see.
Thank you!

heineken78 said:
NFC works, people use safetynetfix and pay with gpay app
to do
encrypted, even password will not match in TWRP, cos TWRP uses old keymaster sources.
Click to expand...
Click to collapse
After installing latest version (0611) now NFC card makes sound when it's near the phone and opens NFC app. However, it seems to crash. I have taken a logcat regarding NFC problem. These are the following lines worthy of notice, please tell me if this helps:
Code:
11-06 12:35:07.189 11571 11618 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'short android.os.Bundle.getShort(java.lang.String)' on a null object reference
11-06 12:35:07.189 11571 11618 E AndroidRuntime: at android.nfc.tech.NfcA.<init>(NfcA.java:76)
11-06 12:35:07.189 11571 11618 E AndroidRuntime: at android.nfc.tech.NfcA.get(NfcA.java:62)
Code:
11-06 12:35:07.853 3646 11670 E libnfc_nci: [ERROR:phNxpExtns.cpp(220)] Error Sending msg to Extension Thread
11-06 12:35:07.854 879 879 D NxpExtns: find found MIFARE_READER_ENABLE=(0x1)
11-06 12:35:07.854 879 879 D NfccPowerTracker: NfccPowerTracker::ProcessCmd: Enter,Recieved len :4
Code:
11-06 12:35:59.782 10874 10874 I RenderThread: type=1400 audit(0.0:846): avc: denied { execute } for path="/vendor/lib/hw/gralloc.sdm660.so" dev="mmcblk0p80" ino=776 scontext=u:r:untrusted_app_27:s0:c168,c256,c512,c768 tcontext=u:object_r:vendor_file:s0 tclass=file permissive=1
According to logcat, even though it doesn't work, it seems to know the card type (mifare):
Code:
11-06 12:35:10.155 758 3327 D NxpHal : NxpNci: RF Interface = MIFARE
11-06 12:35:10.155 758 3327 D NxpHal : NxpNci: Protocol = MIFARE
Thank you!

amiali said:
I tested three gsi models. The camera and the flash don't work
Click to expand...
Click to collapse
release 06/11/19 fixes this issue.

jokolom said:
According to logcat, even though it doesn't work, it seems to know the card type (mifare):
Click to expand...
Click to collapse
config nfc-nxp.conf needs to be fixed to new drivers.
unfortunately im not able to use nfc at all on my SAT - antenna is broken.
so someone has to do it...

heineken78 said:
config nfc-nxp.conf needs to be fixed to new drivers.
unfortunately im not able to use nfc at all on my SAT - antenna is broken.
so someone has to do it...
Click to expand...
Click to collapse
I have found this file: /vendor/etc/libnfc-nxp.conf. Is that the file you reference to?
What can I do to help? I have no problem trying thing but I would need some pointers on what should be changed.
Thank you

Here's : /vendor/etc/libnfc-nxp.conf from 2080WW SAT (stock Oreo).
View attachment libnfc-nxp.zip

paulzie said:
Here's : /vendor/etc/libnfc-nxp.conf from 2080WW SAT (stock Oreo).
View attachment 4869289
Click to expand...
Click to collapse
I have just tried it. Instead of crashing, it will get stuck while trying to read the NFC card. Moreover, the NFC settings get stuck as well.
Thanks

Many GCam mod versions stop to get HDR+ shots at some point. Usually it start with exception in UI handler thread:
11-07 20:51:03.620 6899 7544 I CAM_PhotoCaptureSession: [409d074|IMG_20191107_205058] saveAndFinish
11-07 20:51:03.621 6899 7544 W System.err: java.util.concurrent.ExecutionException: java.lang.Exception
11-07 20:51:03.621 6899 7544 W System.err: at oxp.a(Unknown Source:20)
11-07 20:51:03.621 6899 7544 W System.err: at oxp.get(Unknown Source:475)
11-07 20:51:03.621 6899 7544 W System.err: at oxz.get(Unknown Source:0)
11-07 20:51:03.621 6899 7544 W System.err: at lqi.b(Unknown Source:6)
11-07 20:51:03.622 6899 7544 W System.err: at iqu.a(Unknown Source:46)
11-07 20:51:03.622 6899 7544 W System.err: at hfd.run(Unknown Source:44)
11-07 20:51:03.622 6899 7544 W System.err: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:462)
11-07 20:51:03.622 6899 7544 W System.err: at java.util.concurrent.FutureTask.run(FutureTask.java:266)
11-07 20:51:03.622 6899 7544 W System.err: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
11-07 20:51:03.622 6899 7544 W System.err: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
11-07 20:51:03.622 6899 7544 W System.err: at java.lang.Thread.run(Thread.java:919)
11-07 20:51:03.622 6899 7544 W System.err: at loy.run(Unknown Source:5)
11-07 20:51:03.622 6899 7544 W System.err: Caused by: java.lang.Exception
11-07 20:51:03.622 6899 7544 W System.err: at lqi.a(Unknown Source:4)
11-07 20:51:03.622 6899 7544 W System.err: at frh.d(Unknown Source:35)
11-07 20:51:03.622 6899 7544 W System.err: at egc.a(Unknown Source:152)
11-07 20:51:03.622 6899 7544 W System.err: at eeg.y(Unknown Source:158)
11-07 20:51:03.622 6899 7544 W System.err: at eeg.o(Unknown Source:32)
11-07 20:51:03.622 6899 7544 W System.err: at efb.onShutterButtonClick(Unknown Source:44)
11-07 20:51:03.622 6899 7544 W System.err: at jyl.onShutterButtonClick(Unknown Source:25)
11-07 20:51:03.622 6899 7544 W System.err: at com.google.android.apps.camera.ui.shutterbutton.ShutterButton.performClick(Unknown Source:98)
11-07 20:51:03.622 6899 7544 W System.err: at android.view.View.performClickInternal(View.java:7117)
11-07 20:51:03.623 6899 7544 W System.err: at android.view.View.access$3500(View.java:801)
11-07 20:51:03.623 6899 7544 W System.err: at android.view.View$PerformClick.run(View.java:27351)
11-07 20:51:03.623 6899 7544 W System.err: at android.os.Handler.handleCallback(Handler.java:883)
11-07 20:51:03.623 6899 7544 W System.err: at android.os.Handler.dispatchMessage(Handler.java:100)
11-07 20:51:03.623 6899 7544 W System.err: at android.os.Looper.loop(Looper.java:214)
11-07 20:51:03.623 6899 7544 W System.err: at android.app.ActivityThread.main(ActivityThread.java:7356)
11-07 20:51:03.623 6899 7544 W System.err: at java.lang.reflect.Method.invoke(Native Method)
11-07 20:51:03.623 6899 7544 W System.err: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
11-07 20:51:03.623 6899 7544 W System.err: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:930)
And then no more shots could be taken until rebooted (probably camera left in illegal state after exception):
11-07 20:51:27.555 6899 7388 E CAM_HdrPBurstTkr: Failed to receive any frames. Aborting capture for shot 6
11-07 20:51:27.558 6899 7388 I CAM_HdrPShotParams: HDR+ pipeline reported shotId 6 was aborted.
11-07 20:51:27.559 6899 6899 I CAM_VirtualCameraManage: Disconnecting camera 0 asynchronously.
11-07 20:51:27.559 6899 6936 I CAM_CamDevLsnrShim: Camera device 1548342258(0) has been disconnected.
11-07 20:51:27.559 6899 7388 W libgcam : [pipeline_manager.cc:853]: AbortShot: Shot aborted by AbortShot() during capture.
11-07 20:51:27.559 6899 6936 I CAM_VirtualCameraManage: Camera device 0 was closed.
11-07 20:51:27.560 6899 6899 I CAM_CptrBtnReadiness: addCameraReadinessCallback: cameraReadiness=Obs.of{false}
11-07 20:51:27.563 6899 7388 I CAM_PictureTakerImpl: availability: get=true ret=filtered{DerefObs{filtered{TransformedObs{[email protected], [email protected]}}}} [email protected]
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: PictureTaker command failed: [email protected][status=SUCCESS, result=[[email protected]]]
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: mbl: HDR+ shot didn't succeed
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at den.a(Unknown Source:574)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at fan.a(Unknown Source:20)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at eyz.a(Unknown Source:39)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at fal.a(Unknown Source:7)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at hfu.a(Unknown Source:146)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at gnw.run(Unknown Source:42)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:462)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at pal.b(Unknown Source:2)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at ozq.run(Unknown Source:22)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at paj.run(Unknown Source:4)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at java.lang.Thread.run(Thread.java:919)
11-07 20:51:27.564 6899 7388 E CAM_PictureTakerImpl: at loy.run(Unknown Source:5)
11-07 20:51:27.564 6899 7388 I CAM_PictureTakerImpl: PictureTakerCommand.run: success=false

jokolom said:
I have just tried it. Instead of crashing, it will get stuck while trying to read the NFC card. Moreover, the NFC settings get stuck as well.
Thanks
Click to expand...
Click to collapse
that what Im trying to tell you. Paul shared old config, I have put modified to work with new hals.
May be you can compare both and fix it.
My nfc is not working due antenna problems.
Thats it!

@heineken78 Sorry but I can't find link to download rom files in first post (update 2019-11-06 too) .

iiandrusii said:
@heineken78 Sorry but I can't find link to download rom files in first post (update 2019-11-06 too) .
Click to expand...
Click to collapse
This is question to XDA designer. Change XDA style page and find tabs, we are on "di-scussion" now, next is " downloads"...

I found ? thx

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)