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

Search This thread

SalsifiPourri

Senior Member
Jul 23, 2017
259
199
Haïroule
Thanks, and could you please compare that to Slim ROM and LineageOS 14.1? What are the main differences, I mean in functionality, stability and speed? Most options for customisation are not so important.

I have a lot of bugs with luminosity on lineage os. Also the camera crashes a lot when I switch between front and back. I do not have those bugs on RR

Also I don't know much about Slim so I can't talk about it
 

shimmyjimmy

New member
Aug 7, 2017
1
0
media download bug

Hi guys, I cannot solve an issue myself, maybe you can assist...
Messenger apps generally work and so does media download but whatsapp will not do the latter, regardless of privacy guard settings and permissions. Followed many troubleshooting guides to no avail. I receive messages and thumbnails but when it comes to loading the images/videos, "Download failed" alert pops up. sd card is writable. chat backup also not possible. seems like the app cannot write.
Any suggestions?
I'm on 14.1-20170602-unofficial-kminilte and sm-g800f
 

Lewdog45

Senior Member
Jan 26, 2016
116
16
New Plymouth
Hello everyone! If anyone has been using this ROM with Snapchat then you are probably aware of the video recording bug where you record video and its very choppy and laggy, I was reading through a forum for the S7 and came across this in the change log that apparently fixes this issue. I would like to thank henrymcc for this amazing ROM. I am asking all developers if it would be possible to also try to implement this into this ROM to maybe fix this issue. The forum mentioned something about this:

"hero-common: disable Exynos HW encoders
* This change fixed video recording(in camera app and other apps like Snapchat)."

Here is the original link: https://forum.xda-developers.com/ga...-unofficial-lineageos-14-1-galaxy-s7-t3529197

Thanks again dev's!
 

spookcity138

Senior Member
Nov 9, 2015
1,862
2,565
Eindhoven
Hey guys,
After much searching and trial and error I have figured out the cause of the missing F in the model name on recent builds. I have shared this in the research group on Telegram,but for those who are building ROMS and are not part of this group I will share here.... The cause: This commit. The quick,easy fix is to just revert this. The proper fix would be to edit our init file to reflect this change,which I will look into if I have some time.
 

starbright_

Senior Member
Apr 11, 2010
1,275
207
So we can look forward to a new build with recent security patches. :)

What I don't understand (but this is a Google/LOS issue imho) - why the keep the profiles, but don't have a fast access via a tile to switch the profile. I think profiles (Wifi, 3G, .... ) are very useful.
 
  • Like
Reactions: HaxxorHardy

ChriMo

Senior Member
Oct 13, 2014
285
57
I have a strange problem: when I open the caller/dialer app (I have only pure LinOS installed, no GApps) and enter a phone number as soon as I tap on the call icon the screen becomes black and only sometimes after pressing On/Off and the other hardware buttons multiple times the PIN login screen gets shown and I come back to the system (with the dialer app in the background, if I open it while the call is still active the same happens again).
I thought this should be a dialer app or theming issue but I never have changed settings regarding this; if I remember correctly I did a modem/baseband update when I first installed LinOS over the Stock Firmware this May.
Now I have clean flashed lineage-14.1-20170805-UNOFFICIAL-kminilte by Aykut and still the problem remains.
Not sure what to try next.

EDIT: found this https://www.reddit.com/r/LineageOS/comments/63rikp/galaxy_s5_black_screen_on_call/
So is this a proximity sensor / hardware problem not easily fixable?
 
Last edited:

spookcity138

Senior Member
Nov 9, 2015
1,862
2,565
Eindhoven
I have a strange problem: when I open the caller/dialer app (I have only pure LinOS installed, no GApps) and enter a phone number as soon as I tap on the call icon the screen becomes black and only sometimes after pressing On/Off and the other hardware buttons multiple times the PIN login screen gets shown and I come back to the system (with the dialer app in the background, if I open it while the call is still active the same happens again).
I thought this should be a dialer app or theming issue but I never have changed settings regarding this; if I remember correctly I did a modem/baseband update when I first installed LinOS over the Stock Firmware this May.
Now I have clean flashed lineage-14.1-20170805-UNOFFICIAL-kminilte by Aykut and still the problem remains.
Not sure what to try next.

EDIT: found this https://www.reddit.com/r/LineageOS/comments/63rikp/galaxy_s5_black_screen_on_call/
So is this a proximity sensor / hardware problem not easily fixable?
You can try a Proximity sensor check or test app from the play store. There are a few. Perhaps one will help. I don't know though. Just a thought.

Sent from my SM-G800F using Tapatalk
 
  • Like
Reactions: ChriMo

guntzog

Senior Member
May 5, 2016
200
63
I have a strange problem: when I open the caller/dialer app (I have only pure LinOS installed, no GApps) and enter a phone number as soon as I tap on the call icon the screen becomes black and only sometimes after pressing On/Off and the other hardware buttons multiple times the PIN login screen gets shown and I come back to the system (with the dialer app in the background, if I open it while the call is still active the same happens again).
I thought this should be a dialer app or theming issue but I never have changed settings regarding this; if I remember correctly I did a modem/baseband update when I first installed LinOS over the Stock Firmware this May.
Now I have clean flashed lineage-14.1-20170805-UNOFFICIAL-kminilte by Aykut and still the problem remains.
Not sure what to try next.

EDIT: found this https://www.reddit.com/r/LineageOS/comments/63rikp/galaxy_s5_black_screen_on_call/
So is this a proximity sensor / hardware problem not easily fixable?

I had the same problem
I used a proximity sensor tester on playstore, the proximity configuration was messed up, i reseted it, it forced closed sudently and went back to normal
 
  • Like
Reactions: ChriMo

ChriMo

Senior Member
Oct 13, 2014
285
57
Thank you @guntzog and @spookcity138
So I have some hope it can be resolved and will try directly the "Proximity Fix" App which needs LinOS root (addonsu-14.1-arm-signed.zip).

EDIT: Proximity Fix gave a "not compatible" error when installing. So I tried "Proximity Sensor Fixer" which gave ERROR caused either by lack of ROOT (was available) or incompatibility with the fix by the manufacturer/system.
Then I tried "Proximity Sensor Reset Repair" which seemed to try a fix including boot write of values. It showed the sensor always on "NEAR".
So I tried another solution by blowing air from a Power Duster into the ear-speaker at the top. It worked! For now proximity sensor seems to do the job as expected.
 
Last edited:
  • Like
Reactions: guntzog

Pat750

Senior Member
Sep 12, 2016
588
256
So I tried another solution by blowing air from a Power Duster into the ear-speaker at the top. It worked! For now proximity sensor seems to do the job as expected.
What an creative approach How did you fix your smartphone...with a power duster...I love it...
 

0verdraww

New member
Aug 17, 2017
2
0
Hi.

First of all: This ROM is really amazing Work for an unofficial Lineage OS. Thank you for all the work put in!


That being said, I have a serious problem with the 7.1.2 release. It won't recognize my SIM card. Just for troubleshooting I packed an image of my system, flashed TWRP again from Odin - tried both Versions, the avkev 3.0 and 3.1 from this thread - wiped everything and flashed only the ROM from hennymcc, but the Problem still persisted. I've been using this ROM since CM13 and never encountered a similar Error. When I downgrade again, firmware or clean flash, everything works as intended again.

The flash zip ain't corrupted either, I checked the hashes.


Anyone else got a clue?
 

Friedensfurz

Senior Member
I have a serious problem with the 7.1.2 release. It won't recognize my SIM card.

You need to flash the official MM rom (from Sammobile or similar) via Odin and let it boot completely before switching to Android 7. Then it will find your SIM ;)
@hennymcc Many had this question before - could you please add that info to the OP? Many thanks ;))
 
Last edited:
  • Like
Reactions: Pat750

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Security Patch Level April, plz try
  • 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