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

Search This thread
S

StanleyNL

Guest
Thx! Do you know why these apps require Safetynet?
Well, as you may know, root access allows you to do things on Android with superuser access. You can do basically anything, like system apps can. The problem with it is that it makes things less secure, since you (technically) could fake a successful request when logging into Snapchat without knowing the password, or completing a payment through Android Pay, without losing money. Therefore, both Snapchat and Android Pay won't run when the user has root access, just to make sure.

Safetynet is a way for apps to make sure that the user is not rooted and the device is secure. Magisk has some tools for hiding root access, so that apps won't be able to find out that a device has been rooted. So when you're using Magisk or a tool that does a similar thing, you're basically lying to the system that your device is secure enough to use it.
 
Last edited:

mirhciulica

Senior Member
Jun 5, 2012
54
73
48
Bucharest
Hi.
I have some problems with Firefox after activating SELinux using magisk. Logcat shows this error message:

04-01 14:58:46.809 I/debuggerd(5782): type=1400 audit(0.0:155): avc: denied { read } for name="libnss3.so" dev="mmcblk0p21" ino=263416 scontext=u:r:debuggerd:s0 tcontext=u:eek:bject_r:app_data_file:s0:c512,c768 tclass=file permissive=1

Without MagiskHide (and SELinux permissive) everything is fine. I just want to know if it is a problem caused by Magisk or the SELinux policies in this ROM.

wkr ADT

P.S.: the april fools joke was great. didn't expect so many to fall for it though.

Hey, the fact that the 'avc: denied' line shows at the end permissive=1 it means that SELinux is not working actively, thus not blocking any file requests. Can you check whether SELinux is really activated by Magisk? I suspect there may be some other issue that's causing unexpected Firefox behavior.

I'll add the missing SELinux policy to address this denial next week. I'm taking this opportunity to ask everyone who wants to help on SELinux, to share logs with 'avc: denied' so we can review them and add the missing policies. There might be some missing policies for our device that we don't have at the moment.

Regarding SafetyNet, it's a collection of many checks - some well known, others that only Google knows about - that can be updated at any time on device via play store services. Devices with custom ROMs and enforcing SELinux that don't have root access should be able to pass it (as in the case of S4 Mini and many others), but our device has some other issues at the moment.

Sent from my SM-G800F using Tapatalk
 

a-dead-trousers

Senior Member
Jul 28, 2016
267
135
43
Hey, the fact that the 'avc: denied' line shows at the end permissive=1 it means that SELinux is not working actively, thus not blocking any file requests. Can you check whether SELinux is really activated by Magisk? I suspect there may be some other issue that's causing unexpected Firefox behavior.
Sorry I'm not sure. According to the release notes of Magisk it seems that they try to "simulate" SELinux enforced.
https://forum.xda-developers.com/showpost.php?p=70897029&postcount=12
I'll add the missing SELinux policy to address this denial next week. I'm taking this opportunity to ask everyone who wants to help on SELinux, to share logs with 'avc: denied' so we can review them and add the missing policies. There might be some missing policies for our device that we don't have at the moment.
Okay, thanks I'll look out for those and maybe test some without Magisk. Do you know how to enable SELinux without root?
Regarding SafetyNet, it's a collection of many checks - some well known, others that only Google knows about - that can be updated at any time on device via play store services. Devices with custom ROMs and enforcing SELinux that don't have root access should be able to pass it (as in the case of S4 Mini and many others), but our device has some other issues at the moment.
I thought something like this is the case here. :(
If it helps: Using the old CM13 of hennymcc with SuperSU and Rootswitch everything worked just fine. Even SafteyNet. The funny part was I needed SuperSU and Rootswitch otherwise SafteyNet didn't work.
 
  • Like
Reactions: mirhciulica

Andi46

Senior Member
Feb 7, 2016
238
131
0
Vechta
Sorry I'm not sure. According to the release notes of Magisk it seems that they try to "simulate" SELinux enforced.
https://forum.xda-developers.com/showpost.php?p=70897029&postcount=12

I thought something like this is the case here. :(
If it helps: Using the old CM13 of hennymcc with SuperSU and Rootswitch everything worked just fine. Even SafteyNet. The funny part was I needed SuperSU and Rootswitch otherwise SafteyNet didn't work.

i can verify with my S4 mini- unrooted/Magisk uninstalled the SELinux state was already Enforcing - now with fully functioning Magisk v12.0 it's Enforcing too.
with my S5 mini - unrooted/Magisk uninstalled the SELinux state is Permissive - with Magisk v12.0 after 1st boot into OS still permissive but after rebooting 2nd time it's Enforcing!
Firefox+GelloMod+GoogleLWP crash, Titanium Backup+Root_Explorer+L_Speed+Root_Checker+Busybox ask this time after second reboot for root access <---- don't know if i tried to reboot 2 times yesterday
translation: Strikt = Enforcing
 

Attachments

  • Screenshot_20170401-234612.png
    Screenshot_20170401-234612.png
    60.3 KB · Views: 178
  • Screenshot_20170402-000340.png
    Screenshot_20170402-000340.png
    86.7 KB · Views: 178
  • Screenshot_20170402-010832.png
    Screenshot_20170402-010832.png
    95.6 KB · Views: 178
Last edited:
  • Like
Reactions: mirhciulica

Andi46

Senior Member
Feb 7, 2016
238
131
0
Vechta
I'll add the missing SELinux policy to address this denial next week. I'm taking this opportunity to ask everyone who wants to help on SELinux, to share logs with 'avc: denied' so we can review them and add the missing policies. There might be some missing policies for our device that we don't have at the moment.

Regarding SafetyNet, it's a collection of many checks - some well known, others that only Google knows about - that can be updated at any time on device via play store services. Devices with custom ROMs and enforcing SELinux that don't have root access should be able to pass it (as in the case of S4 Mini and many others), but our device has some other issues at the moment.

Sent from my SM-G800F using Tapatalk

...would be NICE if we all can get it working properly. I've made 5 logcats with Magisk v12 installed and SELinux state Enforcing - copied from Minimal ADB, opened a new .txt and saved the logs a unicode .txt from boot to crash of the several app. Or should i better let Minimal ADB create the log with the command
adb logcat > logcat.txt ?
If you need anything else - let US know please ;)

I also found a SN training site: https://developer.android.com/training/safetynet/index.html
Magisk v12.0 summary of the more important changes: https://www.xda-developers.com/magisk-receives-an-update-to-v12-fixes-samsung-bugs-adds-core-only-mode-and-more/ and full change-log: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/post71658118#post71658118
 

Attachments

  • Screenshot_20170402-021302.png
    Screenshot_20170402-021302.png
    85.9 KB · Views: 172
  • logcats.PNG
    logcats.PNG
    9.8 KB · Views: 168
  • logcats_reboot_to_..._.rar
    444.1 KB · Views: 12
  • S5mini-magisk_error_20170402_094402.log
    5.9 KB · Views: 2
Last edited:

a-dead-trousers

Senior Member
Jul 28, 2016
267
135
43
Is there not another place to discuss Magisk? For those of us who come here because we are interested in the development of this rom we have to wade through pages of this Magisk stuff.
It's not only for Magisk. It's also regarding SELinux a feature of Android/Lineage currently not working properly on this ROM. See first page.
Lately SafetyNet and SELinux are becoming an increased concern because many app developers are chaning over to using it (snapchat, mario run, pokemon, android pay and many more)
The main reason for me to use Magisk/SuperSU and so on was not to get root but to get something cloaking my phone so i can get to use apps using SafetyNet. Out-of-the box the current ROM and also the previous CM versions of it were not able to pass SafetyNet. It would be great when I don't need theses anymore and this ROM works without them.
So I'm sorry that you're annoyed by the "hi-jack" of this thread for the problems others have with this ROM and wanting it to be fixed. Which of course doesn't help the "development" of it at all and is a total waste of your precious time to "wade through the pages".
 
  • Like
Reactions: mirhciulica

ayke

Senior Member
May 16, 2011
70
180
0
yeahh cool! THX 4 that... :good:;) the last 3.1.0 had an issue if you have wiped Dalvik,cache, data + system - there's no recovery anymore/or it just doesn't open (tried with reboot to recovery and with hw keys...)

I cannot reproduce that issue. I have backed up system, then wiped it, reinstalled the ROM via sideload (to test), reboot (don't try this: it messes up Google apps), wipe+restore system, then backed up and wiped data, wiped cache/dalvik cache, reboot, wiped and restored data, reboot. That whole time TWRP continues to work.

It is possible this only happens when multiple partitions are wiped at once, but it seems unlikely to me.

Is it still an issue with the latest TWRP (2017-03-24)? What are the exact steps to reproduce?
 
  • Like
Reactions: Friedensfurz

Andi46

Senior Member
Feb 7, 2016
238
131
0
Vechta
I cannot reproduce that issue. I have backed up system, then wiped it, reinstalled the ROM via sideload (to test), reboot (don't try this: it messes up Google apps), wipe+restore system, then backed up and wiped data, wiped cache/dalvik cache, reboot, wiped and restored data, reboot. That whole time TWRP continues to work.

It is possible this only happens when multiple partitions are wiped at once, but it seems unlikely to me.

Is it still an issue with the latest TWRP (2017-03-24)? What are the exact steps to reproduce?

Hi, i verified the issue just to be sure... I'll explain how it's reproduceble: boot to recovery, inside to wipe - then tick Dalvik, cache, sytem + data - wipe, then back to Restart menu, there reboot to recovery - but then you end at Samsung boot logo. it was always possible before and should be STILL there if these 4 partitions are wiped, right? I had read of the issue in Tab 2 7''+10'' Unified Lineage OS 13 thread and experienced it now twice... The dev Android-Andi is already at TWRP 3.0.1-2... just wanted to let you know ;) latest twrp-20170324-UNOFFICIAL-kminilte - flashed the image in twrp before

@all- i'm SORRY some people were pissed of all the Magisk + SELinux stuff. i didn't notice something ESSENTIAL in the troubleshooting section of this really nice tool - if it's functioning!!! It has to do something with Stock Roms ability to have SN working, its boot image and of course with the SELinux state and their policies.
,,If your ROM itself is not able to pass SafetyNet, then there is nothing Magisk can help.
Your best bet is 100% stock ROMs, because your phone manufacturer is forced to release a
device passing CTS.''
- so the S5 mini is DEAD for SafetyNet compatibility !!! - didn't try the Stock KK, LP Rom, only MM... :crying: REALLY,REALLY POOR from Samsung because MM arrived just recently!!! they wanna sell something...
SORRY AGAIN ;)
 

Attachments

  • IMG_20170403_142035.jpg
    IMG_20170403_142035.jpg
    249.8 KB · Views: 176
Last edited:
  • Like
Reactions: Pat750

Andi46

Senior Member
Feb 7, 2016
238
131
0
Vechta
Guys, I can't connect my phone to any computer via USB. Is it only me? I cannot​ use Google auto as well... Plz help
Do you use Win 10 ? is USB-Debugging enabled in dev options? - if so you can use MyPhoneExplorer (by far the BEST Android/Win PC solution i had since symbian 60 times! ), free client app (installs aut. at first try to add a phone, but has to be updated via playstore to mirror, + plugged in usb to control your device) and free Windows Software http://www.fjsoft.at/en/. In options don't forget a tick to load filelists and multi-sync at start and connection type to auto, then usb is no more needed - the client on phone auto connects to PC via USB, WLAN or Bluetooth at MPE start.
At my side my phone appears in Explorer but when i enter, nothing 's to see... If you're already rooted a really nice tool is also UMS Enabler, if activated your external SD will be mounted as USB Mass Storage in Explorer, cause with MPE i'm only sometimes able to write something to eSD. - the external card disaster.
Even with disabled USB-Debugging there's no chance at my side (Win 10 X64 Pro v1607) to enter the phone in Explorer. Stock MM it's fully working... tried with the drivers win 10 installed when plugged in first time and actual SamsungDrivers.
Android Auto: do you know if this feature is/was already available with Stock Rom? https://support.google.com/androidauto#topic=6348027
or buy a really, really good usb cable and try it again - that sometimes helped at work... you also have to enable it first in radio! (there are videos on Youtube + set preferred usb connection --> Android Auto) - MirrrorLink the same! Haven't tried to combine Stock Radio + Custom Rom (no handys at work)
for some radios there are also custom roms - there it will be working and even some more functions
 

Attachments

  • IMG_20170403_172451.jpg
    IMG_20170403_172451.jpg
    251.1 KB · Views: 188
Last edited:

ayke

Senior Member
May 16, 2011
70
180
0
Hi, i verified the issue just to be sure... I'll explain how it's reproduceble: boot to recovery, inside to wipe - then tick Dalvik, cache, sytem + data - wipe, then back to Restart menu, there reboot to recovery - but then you end at Samsung boot logo. it was always possible before and should be STILL there if these 4 partitions are wiped, right? I had read of the issue in Tab 2 7''+10'' Unified Lineage OS 13 thread and experienced it now twice... The dev Android-Andi is already at TWRP 3.0.1-2... just wanted to let you know ;) latest twrp-20170324-UNOFFICIAL-kminilte - flashed the image in twrp before

(This should ideally move to a separate TWRP thread)

I could reproduce the issue using "reboot to recovery" from the TWRP menu but I am still able to boot into recovery using the volumeup+home+power buttons. I suspect wiping data or cache somehow disables the "reboot to recovery" feature. Are you sure you used the buttons correctly? It's hard to press them in just the right way to trigger the right boot mode.
 

Andi46

Senior Member
Feb 7, 2016
238
131
0
Vechta
(This should ideally move to a separate TWRP thread)

I could reproduce the issue using "reboot to recovery" from the TWRP menu but I am still able to boot into recovery using the volumeup+home+power buttons. I suspect wiping data or cache somehow disables the "reboot to recovery" feature. Are you sure you used the buttons correctly? It's hard to press them in just the right way to trigger the right boot mode.

hmm, maybe...:confused:
sometimes it's really hard to use the hw button method on mine . Ok that, the dev of tab 2 wrote that step a long time ago in the FAQ on his website and mentioned he could see the changes from version to version so and was able to debug.
As i already said, it was always functioning before v3.1.0-0
THX for your attention ;)
 
Last edited:

skysurfer1111

Senior Member
Jul 4, 2016
142
106
43
Berlin
Do you use Win 10 ? is USB-Debugging enabled in dev options? - if so you can use MyPhoneExplorer (by far the BEST Android/Win PC solution i had since symbian 60 times! ), free client app (installs aut. at first try to add a phone, but has to be updated via playstore to mirror, + plugged in usb to control your device) and free Windows Software http://www.fjsoft.at/en/. In options don't forget a tick to load filelists and multi-sync at start and connection type to auto, then usb is no more needed - the client on phone auto connects to PC via USB, WLAN or Bluetooth at MPE start.
At my side my phone appears in Explorer but when i enter, nothing 's to see... If you're already rooted a really nice tool is also UMS Enabler, if activated your external SD will be mounted as USB Mass Storage in Explorer, cause with MPE i'm only sometimes able to write something to eSD. - the external card disaster.
Even with disabled USB-Debugging there's no chance at my side (Win 10 X64 Pro v1607) to enter the phone in Explorer. Stock MM it's fully working... tried with the drivers win 10 installed when plugged in first time and actual SamsungDrivers.
Android Auto: do you know if this feature is/was already available with Stock Rom? https://support.google.com/androidauto#topic=6348027
or buy a really, really good usb cable and try it again - that sometimes helped at work... Haven't tried to combine Stock Radio + Custom Rom (no handys at work)
for some radios there are also custom roms - there it will be working and even some more functions
MyPhoneExplorer is great. Perfect to sync the phone to PC. Thx for the advice.
 
  • Like
Reactions: Andi46

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)
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone