Database Info

Google maps not working once I did upgrade from google Maps v1 to google Maps v2

1. When I am using Maps V2 as a standalone application, its working fine. But When I am using Maps V2 which is a sub activity of my project getting below mentioned error logs.
2. My application works fine with Map v1 but I want to upgrade my application from Map V1 to V2
Added below mentioned code to call Map Activity : try { Class.forName("com.google.android.gms.maps.SupportMapFragment");Intent n=new Intent(Information.this,Gmaps.class); n.setFlags(Intent.FLAG_ACTIVITY_REORDER_TO_FRONT);startActivity; }
Followed below steps to upgrade Google Maps v1 to v2
Added google-play-services.jar into my project.
Added library named_ google-play-services_lib found under the extras folder of my Android SDK setup folder to my Android project.
updated map.xml & Androidmanifiest.xml as per new version dependency
Error logs :
11-10 20:03:42.659: W/dalvikvm(9654): Unable to resolve superclass of Lcom/google/android/gms/maps/SupportMapFragment; (168)
11-10 20:03:42.659: W/dalvikvm(9654): Link of class 'Lcom/google/android/gms/maps/SupportMapFragment;' failed
11-10 20:03:42.659: W/System.err(9654): java.lang.ClassNotFoundException: com.google.android.gms.maps.SupportMapFragment
11-10 20:03:42.659: W/System.err(9654): at java.lang.Class.classForName(Native Method)
11-10 20:03:42.659: W/System.err(9654): at java.lang.Class.forName(Class.java:217)
11-10 20:03:42.659: W/System.err(9654): at java.lang.Class.forName(Class.java:172)

ntlabsanand said:
1. When I am using Maps V2 as a standalone application, its working fine. But When I am using Maps V2 which is a sub activity of my project getting below mentioned error logs.
2. My application works fine with Map v1 but I want to upgrade my application from Map V1 to V2
Added below mentioned code to call Map Activity : try { Class.forName("com.google.android.gms.maps.SupportMapFragment");Intent n=new Intent(Information.this,Gmaps.class); n.setFlags(Intent.FLAG_ACTIVITY_REORDER_TO_FRONT);startActivity; }
Followed below steps to upgrade Google Maps v1 to v2
Added google-play-services.jar into my project.
Added library named_ google-play-services_lib found under the extras folder of my Android SDK setup folder to my Android project.
updated map.xml & Androidmanifiest.xml as per new version dependency
Error logs :
11-10 20:03:42.659: W/dalvikvm(9654): Unable to resolve superclass of Lcom/google/android/gms/maps/SupportMapFragment; (168)
11-10 20:03:42.659: W/dalvikvm(9654): Link of class 'Lcom/google/android/gms/maps/SupportMapFragment;' failed
11-10 20:03:42.659: W/System.err(9654): java.lang.ClassNotFoundException: com.google.android.gms.maps.SupportMapFragment
11-10 20:03:42.659: W/System.err(9654): at java.lang.Class.classForName(Native Method)
11-10 20:03:42.659: W/System.err(9654): at java.lang.Class.forName(Class.java:217)
11-10 20:03:42.659: W/System.err(9654): at java.lang.Class.forName(Class.java:172)
Click to expand...
Click to collapse
downgrade "Maps" from V2 to V1 ._.

Thanks a lot for replying. But I want to upgrade my App with Google Map V2.
I added all the dependency w.r.t Maps V2 like added fragment tag in map.xml and AndroidManifest.xml added
Map API key etc.
to get project sample for map v2 check below link :
drive.google.com/folderview?id=0ByHh24AkXWSHbTlCTmppMkd3SGs&usp=sharing

[5.1.x] [SM-T325] CyanogenMod 12.1 UNOFFICIAL Nightlies for the Tab Pro 8.4 LTE

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.x (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* 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.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 12.1 on your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Known Issues
* None
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
Download Links
CyanogenMod: download.crpalmer.org
Google apps addon:
Download: http://d-h.st/users/dhacker29/?fld_id=27426 (use latest lpmr1 gapps)
XDA:DevDB Information
CyanogenMod 12.1 for MondrianLTE (Unofficial), ROM for the Samsung Galaxy Tab Pro 12.2, 10.1, 8.4
Contributors
crpalmer
ROM OS Version: 5.1.x Lollipop
Version Information
Status: No Longer Updated
Created 2015-04-18
Last Updated 2016-02-13

Reserved

Works fine
ROM works fine, made a dirty flash from CM12.
No problems at all.

http://review.cyanogenmod.org/#/c/95004/2
hopefully merged soon (already in cm12 since late march..just noticed recently in cm12 builds in mms.apk...should have known by looking at the history for the cm12 version)
EDIt
One thing though
Email exchange (hotmail etc) app has a repeated error popup during sync..this is from 4/17 build and also today's 4/18...was not the case till 4/16..noticed the apk file size has changed (not sure what..but it starts giving error popups during sync...pretty irritating as have to somehow get it to stop the sync to stop the popup...using the cm12.1 email apk 5.82mb from 4/16 or earlier fixes the issue)
cm12 not having such issues,.at least from 4.16 to 4/18 no email.apk file size changes..no sync issues
Edit attached mixer file to address earpiece echo for other caller not speakerphone echo for other caller.. change zip in extension to xml.. not a zip file..put in system etc folder permissions 644

Does miracast work with this build? I know CM started enabling the feature, but it didn't work when I last tried it with my SM-T315. Thank you for your answer.

Can I just ask a general question to all who have flashed this on the T325, what version specifically of TWRP did you use to flash this? Been having some issues and just want to compare.

RavenY2K3 said:
Can I just ask a general question to all who have flashed this on the T325, what version specifically of TWRP did you use to flash this? Been having some issues and just want to compare.
Click to expand...
Click to collapse
TWRP 2.8.5.0 here. Any later version will work as well.

Hello,
Thank you @crpalmer - great job with this rom!
Any chance I could buy you a beer to express my gratitude? I don't see a donations link in the OP

vrl13 said:
Hello,
Thank you @crpalmer - great job with this rom!
Any chance I could buy you a beer to express my gratitude? I don't see a donations link in the OP
Click to expand...
Click to collapse
Thanks!
There's a donate link in my profile but I prefer not to clutter up useful information with extra donate links...
My PayPal is [email protected].

Beer uploaded: 7UG08116JF1461945
Thanks again!
Sent from my SM-T325 using Tapatalk

Anyone having issues with there WiFi. Sometimes it picks up my wifi other times it doesn't. Sees all the others around the building but not mine.
Sent from my Nexus 6 using XDA Free mobile app

mackenzie121 said:
Anyone having issues with there WiFi. Sometimes it picks up my wifi other times it doesn't. Sees all the others around the building but not mine.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Hello,
I'm having no issue with both 2.4 and 5ghz wifi in my home.
Sounds like a router problem though.. can your other devices pick your wifi without a hitch?
Maybe it would help using a fixed IP, in case you are using DHCP now.
Regards.
Sent from my SM-T325 using Tapatalk

RavenY2K3 said:
Can I just ask a general question to all who have flashed this on the T325, what version specifically of TWRP did you use to flash this? Been having some issues and just want to compare.
Click to expand...
Click to collapse
I used TWRP 2.8.6.0. I already flashed several nightlies on this tablet, no issues.
---------- Post added at 10:41 PM ---------- Previous post was at 10:26 PM ----------
Is the changelog the same of the nightlies for "MONDRIANWIFI"? Thanks

Is it support cifs ?

Device encryption doesn't work. Build 20150507
Log:
Code:
D/Cryptfs ( 247): unmounting /data succeeded
D/QSEECOMAPI: ( 247): QSEECom_get_handle sb_length = 0x2000
D/QSEECOMAPI: ( 247): App is not loaded in QSEE
E/QSEECOMAPI: ( 247): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt
E/QSEECOMAPI: ( 247): Error::Loading image failed with ret = -1
D/QSEECOMAPI: ( 247): QSEECom_get_handle sb_length = 0x2000
D/QSEECOMAPI: ( 247): App is not loaded in QSEE
E/QSEECOMAPI: ( 247): Error::Cannot open the file /firmware/image/keymaste.mdt
E/QSEECOMAPI: ( 247): Error::Loading image failed with ret = -1
E/QCOMKeyMaster( 247): Loading keymaster app failed
E/Cryptfs ( 247): could not open keymaster device in keystore (Operation not permitted)
E/Cryptfs ( 247): Failed to init keymaster
F/libc ( 247): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x3c in tid 316 (vold)
F/libc ( 247): Unable to open connection to debuggerd: Connection refused
W/vold ( 316): type=1400 audit(0.0:190): avc: denied { search } for name="/" dev="mmcblk0p1" ino=1 scontext=u:r:vold:s0 tcontext=u:object_r:firmware_file:s0 tclass=dir
W/vold ( 316): type=1300 audit(0.0:190): arch=40000028 syscall=322 per=800000 success=no exit=-13 a0=ffffff9c a1=b62f84fc a2=20000 a3=0 items=1 ppid=1 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 exe="/system/bin/vold" subj=u:r:vold:s0 key=(null)
W/auditd ( 314): type=1307 audit(0.0:190): cwd="/"
W/auditd ( 314): type=1302 audit(0.0:190): item=0 name="/vendor/firmware/keymaster/keymaster.mdt"
W/auditd ( 314): type=1320 audit(0.0:190):
W/vold ( 316): type=1400 audit(0.0:191): avc: denied { search } for name="/" dev="mmcblk0p1" ino=1 scontext=u:r:vold:s0 tcontext=u:object_r:firmware_file:s0 tclass=dir
W/vold ( 316): type=1300 audit(0.0:191): arch=40000028 syscall=322 per=800000 success=no exit=-13 a0=ffffff9c a1=b62f84fc a2=20000 a3=0 items=1 ppid=1 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 exe="/system/bin/vold" subj=u:r:vold:s0 key=(null)
W/auditd ( 314): type=1307 audit(0.0:191): cwd="/"
W/auditd ( 314): type=1302 audit(0.0:191): item=0 name="/firmware/image/keymaste.mdt"
W/auditd ( 314): type=1320 audit(0.0:191):
W/vold ( 316): type=1701 audit(0.0:192): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=u:r:vold:s0 reason="memory violation" sig=11
I/Vold ( 8391): Vold 2.1 (the revenge) firing up
D/Vold ( 8391): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold ( 8391): Volume usbdisk state changing -1 (Initializing) -> 0 (No-Media)
I/Cryptfs ( 8391): Check if PFE is activated on Boot
E/Cryptfs ( 8391): Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
E/Cryptfs ( 8391): Error getting crypt footer and key
I see, that file /vendor/firmware/keymaster/keymaster.mdt exists:
# ls -la /system/vendor/firmware/keymaster/keymaster.mdt
lrw-r--r-- root root 2015-05-07 07:04 keymaster.mdt -> /firmware/image/keymaste.mdt
# ls -la /firmware/image/keymaste.mdt <
-r--r----- system drmrpc 12892 2014-11-13 05:32 keymaste.mdt
Any ideas how to fix it? Thanks.

crpalmer said:
CyanogenMod
Click to expand...
Click to collapse
f2fs support?
I am waiting for 10 minutes, hanging on the logo

Alexey71 said:
f2fs support?
I am waiting for 10 minutes, hanging on the logo
Click to expand...
Click to collapse
Try again with today's build and let me know.

crpalmer said:
Try again with today's build and let me know.
Click to expand...
Click to collapse
For me :
cm-12.1-20150523-UNOFFICIAL-mondrianlte.zip work fine but
cm-12.1-20150527-UNOFFICIAL-mondrianlte.zip and cm-12.1-20150528-UNOFFICIAL-mondrianlte.zip don't work : hanging on the logo

27-28 build not work (ext4-f2fs)
26 build work ext4

Builds 0527 and 0528 does not boot; instead, causes shutdown of the tab.

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)

[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)