• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[G800F/M/Y][ROM][7.1][NJH47F] LineageOS 14.1 for G800F/M/Y [Beta 19/08/2017]

Search This thread

Tempak

Member
Nov 21, 2009
37
10
Hi. Few weeks ago I replaced my stock ROM (Android 6.0.1) with lineage-14.1-20210608-UNOFFICIAL-kminilte.zip (clean install) + GAPPS (mini) + root (addonsu-14.1-arm-signed.zip).

What I found, that magnetic field sensor sampling rate seems to be really low on SM-G800F (kminilte).

It is slow looking at readings from app like Sensors Multitool (https://play.google.com/store/apps/details?id=com.wered.sensorsmultitool), GPS Test (compass screen) (https://play.google.com/store/apps/details?id=com.chartcross.gpstest) or Sensor Kinetics (https://play.google.com/store/apps/details?id=com.innoventions.sensorkinetics).

I feel it affects navigation apps. GPS precision is the same on both ROMs, but magnetic orientation refresh rate looks bad on LineageOS.

I measured sampling ratio with Sensor Kinetics, setting read rate to FASTEST, and refresh rate on stock ROM is abut 100Hz, while on LineageOS it's about 4Hz.
Look at attached screenshots from S5 mini running on stock and custom ROM.

Can abybody confirm this?
Can it be changed / fixed somehow?

magnetic_field_sensor_compare.png
 
  • Like
Reactions: 7wells

schnarchzapfen

New member
Aug 23, 2021
3
0
Hi,

i had done the mod on my Samsung Galaxy S5 Mini G800F and it works fine. I used Odin and installed the TWRP 3.0.0 recovery image. I also wipped the data like written in the thread on the first page. I flashed the image:
lineage-14.1-20210810-UNOFFICIAL-kminilte

I works great. At the second step i want to install the google playstore over the recovery manger also this worked but i got errors after systemboot ... cant open apmanger etc.... "Einrichtungsassistent wird wiederholt beendet"

I used this this open_gapps-arm-7.1-pico-20210821 file i also tried the next it wont work.

Can somebody give me a hint whats going wrong i only want to use the playstore?

Regards
 
Last edited:

Tempak

Member
Nov 21, 2009
37
10
Hi,

i had done the mod on my Samsung Galaxy S5 Mini G800F and it works fine. I used Odin and installed the TWRP 3.0.0 recovery image. I also wipped the data like written in the thread on the first page. I flashed the image:
lineage-14.1-20210810-UNOFFICIAL-kminilte

I works great. At the second step i want to install the google playstore over the recovery manger also this worked but i got errors after systemboot ... cant open apmanger etc.... "Einrichtungsassistent wird wiederholt beendet"

I used this this open_gapps-arm-7.1-pico-20210821 file i also tried the next it wont work.

Can somebody give me a hint whats going wrong i only want to use the playstore?

Regards
Did you be able to configure Google account with wizard just after system boot or this error occurs at very first boot stage and you can't configure it at all ?

I personally flashed lineage-14.1-20210608-UNOFFICIAL-kminilte.zip with open_gapps-arm-7.1-mini-20210724.zip, but I can try to flash lineage-14.1-20210810-UNOFFICIAL-kminilte.zip with latest "pico" Gapps on my spare S5 mini G800F, to check it.
 

schnarchzapfen

New member
Aug 23, 2021
3
0
Hi,

the error occours at the very first boot at all.

Also i tried your lineage-14.1-20210608-UNOFFICIAL-kminilte.zip with open_gapps-arm-7.1-mini-20210724.zip.

I downloaded the correct files + md5 and uploaded it to the micro SD Card of my phone.

What i did before:
1. I flashed with ODIN the Bootloader TWRP 3.0.0-0
2. I format the DATA.
3. I did the EXTENEND Deleting "Dalvik/ART Cache + Cache + System + Daten + Internal Storage
I did not reboot.

I installed in one session from the SD CARD of my phone:

lineage-14.1-20210608-UNOFFICIAL-kminilte.zip
open_gapps-arm-7.1-mini-20210724.zip

After this action i rebooted the system.

The system was starting initial.

After the first initial start of the system (after 15 Minutens) i get the message "Setup Wizard has stopped" "Open app again".
Then "Setup Wizard keeps stopping" "Close App". And also by clicking i see "Google has stopped".

If you need more details i can support.

Thanks.
 

eddie-77

Member
Aug 25, 2021
7
2
Hi,

the error occours at the very first boot at all.

Also i tried your lineage-14.1-20210608-UNOFFICIAL-kminilte.zip with open_gapps-arm-7.1-mini-20210724.zip.

I downloaded the correct files + md5 and uploaded it to the micro SD Card of my phone.

What i did before:
1. I flashed with ODIN the Bootloader TWRP 3.0.0-0
2. I format the DATA.
3. I did the EXTENEND Deleting "Dalvik/ART Cache + Cache + System + Daten + Internal Storage
I did not reboot.

Я установил за один сеанс с SD-карты своего телефона:

lineage-14.1-20210608-UNOFFICIAL-kminilte.zip
open_gapps-arm-7.1-mini-20210724.zip

After this action i rebooted the system.

The system was starting initial.

After the first initial start of the system (after 15 Minutens) i get the message "Setup Wizard has stopped" "Open app again".
Then "Setup Wizard keeps stopping" "Close App". And also by clicking i see "Google has stopped".

If you need more details i can support.

Thanks.
I also had such a problem. You need to flash using a newer version of twrp. After that, my smartphone flashed completely without errors.
 

Attachments

  • twrp-3.3.1-0-kminilte.img.tar
    11.5 MB · Views: 21
  • Like
Reactions: Tempak

schnarchzapfen

New member
Aug 23, 2021
3
0
Hi,

thanks after the update to twro recovery 3.3.10 it worked perfect.
Only a short question who can update and upload it to the first page of the "howto".

Here is written "TWRP 3.0.0 recovery image [25/03/2016" --> should be updatet.

Thanks!!

Great WORK
 

Tempak

Member
Nov 21, 2009
37
10
Can somebody confirm low refresh rate from magnetic sensor in LOS 14.1 vs stock ROM ?
I wrote about this here.
Below video camparing two same G800F devices running GPS test app (https://play.google.com/store/apps/details?id=com.chartcross.gpstest). On the left LOS 14.1 (lineage-14.1-20210608-UNOFFICIAL-kminilte.zip) on the right latest available stock ROM with Android 6.0.1.

Maybe some older or newer build does not have this issue?

I really think about back to stock because of this. Magnetometer cannot be even calibrated in such poor refresh rate. It is used by navigation apps, like Google Maps.
Do anybody else have the same poor megnetometer sampling ratio like me?

 

jimbob00

Member
Feb 19, 2016
48
11
has anyone found a workaround with the = receive and make any call the display goes off and impossible to turn it on until the caller drops the call. ?
 

jimbob00

Member
Feb 19, 2016
48
11
Hi, this is my first post.I have in this Rom the problem that with incoming calls the display does not turn on. So I do not see who calls me, and thus can not wipe to accept or reject. Also with outgoing calls switches off the display directly. Is this a setting thing in the permissions of the notifications? Since apart from me seems to have no such problem, I guess that somewhere is missing a check mark.I would be very happy about suggestions. Thank you in advance.
did you manage to fix this problem. same thing happening to me. pizzing me right of ?
 

kodx

New member
Apr 25, 2020
4
2
has anyone found a workaround with the = receive and make any call the display goes off and impossible to turn it on until the caller drops the call. ?
Looks like you have a broken proximity sensor. This is how i fixed it:
- install magisk and Xposed Framework
- install Xposed Framework Installer application
- in application install XPrivacyLua
- install XprivacyLua from apk or your app store
- in XprivacyLua Pro install 2 scripts
(you can search it in repo with name "Wakelock")
- in XprivacyLua Pro enable "Fif" collection
- in XprivacyLua find dialer (or another application where you want to disable proximity sensor) and check "Use proximity wakelock"

You can(have to) change Xposed Framework to Riru and Riru EdXposed(i am using android 7, so xposed my only choice).

Have found this solution somewhere in this forum, if you don't know how to do one of the steps - search for proximity sensor fix.

I wrote a step by step instruction for myself with images, but it is in russian, can translate, format in pdf and send for you, write me direct message if you want it.
 
  • Like
Reactions: jimbob00

jimbob00

Member
Feb 19, 2016
48
11
Looks like you have a broken proximity sensor. This is how i fixed it:
- install magisk and Xposed Framework
- install Xposed Framework Installer application
- in application install XPrivacyLua
- install XprivacyLua from apk or your app store
- in XprivacyLua Pro install 2 scripts
(you can search it in repo with name "Wakelock")
- in XprivacyLua Pro enable "Fif" collection
- in XprivacyLua find dialer (or another application where you want to disable proximity sensor) and check "Use proximity wakelock"

You can(have to) change Xposed Framework to Riru and Riru EdXposed(i am using android 7, so xposed my only choice).

Have found this solution somewhere in this forum, if you don't know how to do one of the steps - search for proximity sensor fix.

I wrote a step by step instruction for myself with images, but it is in russian, can translate, format in pdf and send for you, write me direct message if you want it.
Xposed Framework will not install /installation failed/ unsupported device ?
 

jimbob00

Member
Feb 19, 2016
48
11
Looks like you have a broken proximity sensor. This is how i fixed it:
- install magisk and Xposed Framework
- install Xposed Framework Installer application
- in application install XPrivacyLua
- install XprivacyLua from apk or your app store
- in XprivacyLua Pro install 2 scripts
(you can search it in repo with name "Wakelock")
- in XprivacyLua Pro enable "Fif" collection
- in XprivacyLua find dialer (or another application where you want to disable proximity sensor) and check "Use proximity wakelock"

You can(have to) change Xposed Framework to Riru and Riru EdXposed(i am using android 7, so xposed my only choice).

Have found this solution somewhere in this forum, if you don't know how to do one of the steps - search for proximity sensor fix.

I wrote a step by step instruction for myself with images, but it is in russian, can translate, format in pdf and send for you, write me direct message if you want it.
Riru EdXposed will not install
 

kodx

New member
Apr 25, 2020
4
2
are sorry i dirty flashed to 9

Works on Lineage 16 from this topic https://forum.xda-developers.com/t/...f-m-y-lineageos-16-0-beta-28-09-2021.3868612/

  1. Install Riru and Riru - LPosed modules in Magisk
    01-Magisk.png
  2. After reboot LSPosed suggest you to add widget on desktop, it is manager application, you can read about it in this topic https://forum.xda-developers.com/t/...e-magisk-module-edxposed-alternative.4228973/ . Install XprivacyLua module in LSPosed manager
    02-LSPosed.png03-LSPosed.png04-LSPosed.png
  3. In LSPosed manager activate XprivacyLua mod
    05-LSPosed.png06-LSPosed.png
  4. Install XprivacyLua Pro application from app of your choose (i'm using Aurora Store).
  5. Run XprivacyLua Pro and install WakeLock scripts.
    07-XPrivacyLua_Pro.png08-XPrivacyLua_Pro.png09-XPrivacyLua_Pro.png10-XPrivacyLua_Pro.png
  6. In XprivacyLua Pro enable "Fif" collection.
    11-XPrivacyLua_Pro.png
  7. Run XprivacyLua app and set "Use proximity wakelock" for Dialer application
    12-XPrivacyLua.png13-XPrivacyLua.png
I hope this will help you out, Good luck.
 
  • Like
Reactions: jimbob00

jimbob00

Member
Feb 19, 2016
48
11
Works on Lineage 16 from this topic https://forum.xda-developers.com/t/...f-m-y-lineageos-16-0-beta-28-09-2021.3868612/

  1. Install Riru and Riru - LPosed modules in Magisk
    View attachment 5431779
  2. After reboot LSPosed suggest you to add widget on desktop, it is manager application, you can read about it in this topic https://forum.xda-developers.com/t/...e-magisk-module-edxposed-alternative.4228973/ . Install XprivacyLua module in LSPosed manager
    View attachment 5431781View attachment 5431783View attachment 5431785
  3. In LSPosed manager activate XprivacyLua mod
    View attachment 5431787View attachment 5431789
  4. Install XprivacyLua Pro application from app of your choose (i'm using Aurora Store).
  5. Run XprivacyLua Pro and install WakeLock scripts.
    View attachment 5431791View attachment 5431793View attachment 5431795View attachment 5431797
  6. In XprivacyLua Pro enable "Fif" collection.
    View attachment 5431799
  7. Run XprivacyLua app and set "Use proximity wakelock" for Dialer application
    View attachment 5431801View attachment 5431803
I hope this will help you out, Good luck.
thank you. i will give it a go.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 59
    This is a LineageOS 14.1 ROM for the Exynos3470 based Samsung Galaxy S5 mini (G800F/G800M/G800Y).

    DO NOT USE IT FOR G800H OR YOU WILL BRICK YOUR DEVICE

    Although G800F and G800H share the same name they are not related in terms of hardware due to the different SoCs used (Exynos vs. Snapdragon).
    Hence please do not ask for support or ROMs for the G800H.

    Important note: It is possible that flashing this ROM can cause efs partition issues. Therefore it is strongly recommended to make a backup of your efs partition before flashing this ROM. This can be done via TWRP.

    Working features
    • HW accelerated GUI
    • Camera (pictures+video: Back+Front) (switching between camera and video-recording might crash the camera-app)
    • MTP storage
    • Flash Light
    • Bluetooth (A2DP, HFP, HID)
    • IR
    • Sound
    • SMS
    • Initiate and receive calls
    • Wifi
    • Mobile Data
    • USB-OTG (Keyboard, Mouse, USB-Audio, Mass-Storage)
    • NFC
    • Hardware sensors (Orientation, Compass, Proximity, Acceleration, Hall sensor, Step counter)
    • Light sensor (needed for auto-brightness)
    • Pulse sensor (preliminary and very inaccurate. Works with Apps like Kardiograph)
    • SD-Card as internal storage (new Android M feature)
    • GPS
    • Fingerprint scanner
    • SELinux

    Non-working features:

    Known issues:
    • Camera crashes when switching from camera to video. Use Google camera or Open camera to solve camera issues.
    • See the Bug Report section of this thread.

    Disclaimer:
    • You flash this image at your own responsibility. I am not responsible for any damage that might be caused by flashing this image (bricked device, lost data, ...)
    • Flashing this kernel image will trigger the KNOX counter, so your warranty will be void.
    • Applications that use KNOX (e.g. "Private Mode") might not work anymore when returning to the stock ROM, as the device is regarded as compromised. Do not flash this ROM if you need those applications.
    • The image is only for Exynos3470 based S5 Mini variants SM-G800F/M/Y.
    • It might be instable, crash your device, drain your battery, or even might damage your smartphone (e.g. if an USB-OTG device drains too much power)
    • Some users reported that their touch-screen stopped working permanently after some weeks of usage. For some user's (two at the moment including me) NFC stopped working permanently. Probably this issues are not related to this ROM as also many stock user's complain about hardware issues (random reboots, black screens, unresponsive touchscreen) but you have been warned.
    • Backup your data before flashing and check if the original firmware is present (e.g. at SamMobile)
    Before you start:
    • Backup your data, like call history, contacts, sms, WhatsApp messages, favourite app settings that are on internal and external sd (by using Titanium Backup or other apps available on PlayStore). At least all internal data will be lost in any case. If you have bad luck you might also loose data from your external sd card.

    Download:

    Install recovery:
    • Reboot your device into Download mode: turn off your device, then press Volume-Down + Home + Power button at the same time and release them.
    • Confirm the following warning message with the Volume-Up button.
    • Connect your device to your PC via USB
    • Make sure the device driver's are installed on your PC
    • Start Odin
    • In Odin select "PDA" (in newer versions: "AP") and select the recovery image (recovery.tar.md5)
    • Check that only "F. Reset Time" is set. "Auto Reboot" should be disabled to avoid a reboot into stock ROM.
    • Click on "Start": the recovery image should be flashed now. By flashing the recovery, your warranty will be void.
    • After the recovery flashing process was successful, power of your device, wait a few seconds and reboot into recovery mode (see instructions below).
    • Important: make sure not to boot into stock ROM, otherwise the stock ROM might remove the custom recovery again. If this happens, flash the recovery image again.

    Before you flash:
    • You need the latest TWRP recovery (see above). Otherwise TWRP might not be able to flash the ROM. This is because TWRP checks now if the device is "supported".
    • Wipe the device to avoid problems with remaining files from the old installation (see instructions below). This also applies if you already installed an older version of CM 14.1.

    Flash ROM:
    • Reboot into recovery mode (Press Volume-Up + Home + Power button)
    • If you come from a stock ROM, this is your opportunity to make a Backup of your phone(Backup, then select Boot, System, Data, then swipe to backup). Note that the recovery might fail to restore the backup when you want to go back to the stock ROM (for me it got stuck after a restore during boot. But the backup was made with a different version of TWRP, so it might work in general) - simply do not expect too much of it at the moment.
    • If you haven't copied the installation files yet, you can now copy the GApps and the ROM zip to your internal sd or external sd (be careful not to put the files into the data directory of the internal sd card as this will be deleted in the next step). Be sure that MTP is enabled (inside Mounts, click on Enable MTP), then, from your pc, copy the files. If MTP does not work from recovery, try it directly from Android or remove the external sd card from the phone and put it into your PC.
    • Wipe Dalvik Cache, Cache, System and Data (inside Wipe -> Advanced Wipe). Do not report problems if you did not wipe those partitions as the problems are most probably related to this!
    • Install the CM ROM zip-package
    • Install the GApps zip-package

    How to root:
    LineageOS does not have root support integrated by default. You have to download addonsu-arm-signed.zip for 14.1 from the Lineageos Extras download page and install it with TWRP.
    After that root access is still disabled by default. If you want to activate root access for apps, do the following:
    • Open the Settings menu, select "About Phone"
    • Tap on the "Build number" entry seven times. You should be notified, that the developer settings are now active.
    • Open the Settings menu, select "Developer options". Enable root access by selecting "Apps" in the "Root-Access" setting.

    In case you want to go back to the stock ROM:
    • lf you do not have the latest ROM for the G800F you can download it from SamMobile
    • Reboot your phone into Odin mode
    • Open Odin on your PC and connect your smartphone with your PC via USB
    • If you have a zip-file unzip it so that you have a .tar.md5 file
    • In Odin click on the PDA button and select the .tar.md5 file. Then press "Start".
    • Normally the stock rom fails to boot as the data from CM is still on the data partition. So after flashing the stock rom, reboot into recovery mode (it looks a bit different now). First wipe the data partition, then wipe the cache.
    • Reboot

    Changelog
    Code:
    Changelog:
    19/08/2017:
    * SELinux policy update
    * Update to newest LineageOS sources
    02/06/2017:
    * Firefox crash&reboot fixed (thanks to Spookcity)
    * Enabling the fingerprint reader does not cause bootloops anymore (thanks to Spookcity)
    * Ambient display option added (disabled by default)
    28/05/2017:
    * [COLOR="red"]Note: ROM is stuck in bootloop when fingerprint reader is enabled. ROM removed.[/COLOR]
    * Enabled selinux (thanks to mirhciulica for fixing all those selinux denials). If you encounter problems check for "avc: denied" messages in logcat (see: https://source.android.com/security/selinux/validate)
    * Fixed Snapchat and SafetyNet problems (Snapchat reported server errors, Safetynet Helper reported a 1970 timestamp): Kernel patch was necessary.
    * Updated kernel to 3.4.107
    * Applied most of the patches from [URL="https://android.googlesource.com/kernel/common/+/deprecated/android-3.4"]kernel/common/deprecated/android-3.4[/URL]
    * Updated LineageOS sources
    * FlipFlap added to support smart flip covers: shows a screen with the current time in the window of the smart cover. Note that this relies on the magnetic sensor at the bottom of the phone. So magnets near the sensor can trigger this behavior too.
    * Replaced the buggy Gello webbrowser with Jelly - the new LineageOS default browser
    * Replaced the buggy Snap camera with the LineageOS default camera app
    * Replaced the Samsung battery charger app (lpm) with healthd (looks uglier but at least works with selinux)
    
    20/02/2017:
    * Fixed Youtube scaling issue on window resizing
    * Compass fixed (thanks to mirhciulica for figuring out what's wrong)
    * cpufreq config added
    * Charge mode fixed (starts when plugging USB into a powered-off phone)
    * USB-Tethering and Wifi SoftAP (Hotspot) fixed
    * Camera doesn't crash when switching between camera and video (but might still crash sometimes)
    * Fingerprint libs reverted from MM to LP (maybe that fixes the fingerprint issues - please test)
    
    01/02/2017:
    * conversion to LineageOS
    * updated some libs with stock MM versions
    * fixed robotic voice problem
    * fixed silence on first call
    
    07/11/2016:
    * Initial test build

    This section is for developers:
    A README file with build instructions can be found here:
    Code:
    https://github.com/cm-3470/android_device_samsung_kminilte

    Sources:
    Code:
    https://github.com/cm-3470/android_device_samsung_kminilte
    https://github.com/cm-3470/android_vendor_samsung_kminilte
    https://github.com/cm-3470/android_kernel_samsung_kminilte
    https://github.com/cm-3470/android_device_samsung_smdk3470-common

    Developers welcome
    • At the moment the G800F/M/Y specific port of this ROM is only done by two persons (CTXz and hennymcc). Although Unjustified Dev also works on this ROM he does not own an Galaxy S5 Mini but a Galaxy Light which has a similar base but is different when it comes to camera, nfc and other components (maybe even slightly when it comes to audio and radio).
    • Help from other developers is always welcome. See the bug/feature section and this thread to see what is missing. Just give some short info (here in this thread or PM) that you want to work on some issue or feature so that work can be synchronized. Maybe there are also other devs that want to work with you on the same issue.
    • Knowledge in how the kernel works and good programming skills in C, C++ and Java would be nice but not necessary for all problems. At least you should be able to build the ROM and test your changes yourself but you do not need experience in porting ROMs.

    Thanks to CTXz, Psyafter, spookcity138, ayke and mirhciulica for working on this ROM.

    XDA:DevDB Information
    [G800F/M/Y][ROM][7.1][NJH47F] LineageOS 14.1 for G800F/M/Y [Beta 19/08/2017], ROM for the Samsung Galaxy S5 Mini

    Contributors
    hennymcc, Panzerknakker, spookcity138, psyafter, ayke
    Source Code: https://github.com/cm-3470

    ROM OS Version: 7.x Nougat
    ROM Kernel: Linux 3.4.x
    ROM Firmware Required: TWRP Recovery [version >= 15/08/2015]
    Based On: LineageOS

    Version Information
    Status: Beta

    Created 2017-02-01
    Last Updated 2018-08-18
    21
    Hi there is a new build:
    https://www.androidfilehost.com/?fid=529152257862704787

    Changelog:
    • Fixed Youtube scaling issue on window resizing
    • Compass fixed (thanks to mirhciulica for figuring out what's wrong)
    • cpufreq config added
    • Charge mode fixed (starts when plugging USB into a powered-off phone)
    • USB-Tethering and Wifi SoftAP (Hotspot) fixed
    • Camera doesn't crash when switching between camera and video (but might still crash sometimes)
    • Fingerprint libs reverted from MM to LP (maybe that fixes the fingerprint issues - please test)
    21
    Official TWRP 3.1.1

    I've worked together with the TWRP maintainers to make TWRP official, and it's finally here :D
    https://forum.xda-developers.com/galaxy-s5-mini/orig-development/recovery-twrp-3-1-1-exynos-t3626646

    You can download it from here:
    https://twrp.me/devices/samsunggalaxys5miniexynos.html
    21
    A new build is available:
    https://www.androidfilehost.com/?fid=961840155545570720

    It turned out that the patch found by Spookcity not only fixes Firefox but also the fingerprint bootloop. So the new build should be usable again.
    As the initial bootloops probably were also caused by the fingerprints it should not be necessary anymore to wipe everything (although still recommended).

    Changes:
    • Firefox crash&reboot fixed
    • Enabling the fingerprint reader does not cause bootloops anymore
    • Ambient display option added (disabled by default)
    17
    A new build is available.
    https://www.androidfilehost.com/?fid=889764386195902448

    Changelog:
    Code:
    * Enabled selinux (thanks to mirhciulica for fixing all those selinux denials). If you encounter problems check for "avc: denied" messages in logcat (see: https://source.android.com/security/selinux/validate)
    * Fixed Snapchat and SafetyNet problems (Snapchat reported server errors, Safetynet Helper reported a 1970 timestamp): Kernel patch was necessary.
    * Updated kernel to 3.4.107
    * Applied most of the patches from [URL="https://android.googlesource.com/kernel/common/+/deprecated/android-3.4"]kernel/common/deprecated/android-3.4[/URL]
    * Updated LineageOS sources
    * FlipFlap added to support smart flip covers: shows a screen with the current time in the window of the smart cover. Note that this relies on the magnetic sensor at the bottom of the phone. So magnets near the sensor can trigger this behavior too.
    * Replaced the buggy Gello webbrowser with Jelly - the new LineageOS default browser
    * Replaced the buggy Snap camera with the LineageOS default camera app
    * Replaced the Samsung battery charger app (lpm) with healthd (looks uglier but at least works with selinux)