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

Search This thread

CHEF-KOCH

Senior Member
Jan 2, 2012
451
234
0
To be honest I say let LOS 14.x die and focus on the 15 build. As said we not have enough manpower to handle two or even three ROM branches - instead I say go with quality and focus on the latest ones. We have bunch of ROM's but there all bugged (of course no software is bug-free) but there fundamental bugs I'm talking about.
 
  • Like
Reactions: nico_vo

dorkeinath

New member
Nov 11, 2017
1
0
0
Missing files: TWRP and PIT

Hello!
Downloading `recovery.tar.md5` doesn't work ("Standby... Error.").
I'm trying with TWRP-img from aykevl.nl/android but JODIN3 asks me for a PIT-file, that I don't have.
What can I do?
 

hennymcc

Senior Member
Dec 7, 2014
374
1,662
0
Do we have a chance to see a backported cam driver in LOS 14.1 or (imho would make more sense) in LOS 15 ?
The one in LOS/CM 13 was a least 10 times better ... ;)

That is interesting. LOS 14.1 (at least 20170819 in the OP) is the most stable build in terms of camera stability i used so far. Crashes are rather seldom in comparison to CM 13. So at least i do not really want to go back.

From the driver point of view there should be no difference between the LOS-14.1 builds as they all use the same device tree. Differences probably come from LOS itself, e.g. changes or bugs/bugfixes in the camera, media system.
I noticed the most significant changes when the LOS devs improved the default camera app (snap2).

As there was some discussion about it:
in terms of stability not only the camera drivers matter. It is the whole path from camera driver to the media infrastructure (video4linux) to the en-/decoders (omx) and graphics system (e.g. gralloc: graphics allocator) and finally the app (snap2, opencamera, ...).

All the lower parts (cam driver, v4linux, omx, gralloc) are hardware specific and need internal knowledge of the Samsung Exynos SoC which is not disclosed to the public. This is also why there are no open source drivers for these components. And this is why we use the stock camera drivers and infrastructure.

The problem with stability is that these drivers were designed for Android 6 with TouchWiz. Parts even are for Android 4 or 5. The APIs changed a lot since then and also Samsung made some changes that are not in official Android. So the chances that the camera will work 100% is rather low with the manpower we have (it was basically only me who looked into the camera internals so far).

I am still thinking about getting the open source gralloc to work which might improve the stability - but this will probably take at least one week full of work. At least working on the camera is always very time consuming and mostly with little benefit in the end. In addition the S5 mini is still my daily driver, so I cannot work on the graphics system for a longer time as this means that I cannot use my phone during this time :)
This will probably be easier when I buy a new phone. But volunteers who want to work on camera are always welcome ...

For me the camera in LOS 14.1 is ok as a daily driver (in comparison to the workload to improve it). But I have to admit that I do not take that much pictures every day.

About builds:
I have not build any ROMs in the last months as other users build up-to-date ROMs quite frequently. I don't have the time to build LOS-15 and 14.1 ROMs every week and test them. In addition my builds would be the same as the builds of the others (as long as nobody changed the sources).
Maybe I will have time for a new build when Oreo is less time consuming.
 
Last edited:

2faraway2

Senior Member
Apr 24, 2016
160
23
18
@hennymcc : Thanks a lot for your explanation

To be honest: The picture part of the cam works very well (in LOS 14.1, 20171025-build by panzerknacker), only the video recording part does not .. the result is more or less a 5 to 10 fps recording instead of the desired 30 fps recording ..
Exactly this part works better in LOS 13 (your 20170128-build).

btw: Thank you very much for your continious work on LOS for the S5 Mini :)
 

starbright_

Senior Member
Apr 11, 2010
1,270
206
83
As the ROMs will probably again not become official status, can the patch be included to use MicroG ?
Especially for an rather old device it can be helpful to not use the heavy google framework and still have the benfit of notification and maps.
That would be nice and a step to even more open source.
Many thanks for your work!!!
 
Last edited:
  • Like
Reactions: agjeavue

a-dead-trousers

Senior Member
Jul 28, 2016
269
135
43
Is there a possibility to make an music player inside of the flip cover?
I think you're asking at the wrong place.
This thread is only for porting LOS to the S5mini and not for expanding the (app) feature list.
You should either ask the guys over at LineageOS.org to implement a flip-cover option for their music player or search for an existing one offering this option in the google play store.
 
Last edited:

starbright_

Senior Member
Apr 11, 2010
1,270
206
83
A big "thank you" to the devs. The latest version is rather stable and LOS even brought back the tile for "profile" changes. Yeah!!

For me just two problems left, but this is probably hardware (compass and GPS).

The calibration of compass disappears rather fast, the update of current orientation is rather slow compared to other devices (when moving around, the needle follows very slowly).

Regarding GPS: I observed that for no obvious reason (not moving the device, not a drop down in SNR of satellites) the notification goes from 5/18 (5 sats out of 18 are in use) to 0/18 and position lock is gone. This is strange. Also it shows the Glonass sats, but I have never seen that they are used.
Is there a special part of firmware inside the GPS modules that can be updated? Are different GPS chips used?
 
Last edited:

zpk787

Member
Oct 16, 2017
25
3
0
Yeah ayke's build from 2017-10-22 with OpenCamera works very well for me too. Even though before it used to crash when switching to the frontal camera. One think that's kind of wonky is that it seems to be worse at finding cellular network compared to stock and have weaker signal. The network also consumes relatively high amount of battery (not to a level where it's a problem, but noticeably higher that stock). One symptom is that after rebooting the signal gets weak and it eats battery like crazy. That's solved by tuning the plane mode on and off.
 

co-moi

Member
Mar 1, 2016
31
2
0
All i do brings me to error 6 or 7 even with youtube and xda fix. Can anyone prepare the file for me?

I tried out TWRP 3.0.0, 3.1.1-0 and 3.2.0
 
Last edited:

starbright_

Senior Member
Apr 11, 2010
1,270
206
83
Yeah ayke's build from 2017-10-22 with OpenCamera works very well for me too. Even though before it used to crash when switching to the frontal camera. One think that's kind of wonky is that it seems to be worse at finding cellular network compared to stock and have weaker signal. The network also consumes relatively high amount of battery (not to a level where it's a problem, but noticeably higher that stock). One symptom is that after rebooting the signal gets weak and it eats battery like crazy. That's solved by tuning the plane mode on and off.

Battery live is poor for me too. But until now I would blame it to bad reception in my area. Can't compare to a stock rom, whether signal is stronger or weaker.
I can't imagine that this is a problem of LOS, istn't that a question of the baseband? Imho it is controlled by an own µP.
I am on latest 2017-11-20 version
 
Last edited:

Andi46

Senior Member
Feb 7, 2016
238
131
0
Vechta
Battery live is poor for me too. But until now I would blame it to bad reception in my area. Can't compare to a stock rom, whether signal is stronger or weaker.
I can't imagine that this is a problem of LOS, istn't that a question of the baseband? Imho it is controlled by an own µP.
I am on latest 2017-11-20 version

from my experience it didn't matter a lot which baseband was installed, no big change if i flashed a newer one. But bad reception, the always searching for a better radio mast is really sucking your battery a lot. It really went better when i changed the provider to a better network coverage. 24h are no problem with middle usage and a 2250mAh battery, changing the preferred network type to 3G if you have no LTE contract and if you switch off the wifi and bluetooth scanning under location.
 

Attachments

  • Screenshot_20171208-012155.png
    Screenshot_20171208-012155.png
    63.4 KB · Views: 244
  • Screenshot_20171208-012132.png
    Screenshot_20171208-012132.png
    60.1 KB · Views: 244

zpk787

Member
Oct 16, 2017
25
3
0
Battery live is poor for me too.
It's not necessarily poor for me, I just noticed network handles bad reception worse than stock (thankfully, it's fine at my house). Actual battery life of the system is fantastic, I disabled preinstalled email and calendar.provider apps and got a system without wakelocks (besides basic system ones), drained 0% in 6 hours of sleep (it's something like 0,x obviously). Cell network was on in 2g, everything else turned off. I also have stock gallery and music disabled (because I prefer different apps), don't know if they affect battery. I use Spookcity's kernel with interactive governor. Doubt it affects much in deep sleep.
 

a-dead-trousers

Senior Member
Jul 28, 2016
269
135
43
It's not necessarily poor for me, I just noticed network handles bad reception worse than stock (thankfully, it's fine at my house). Actual battery life of the system is fantastic, I disabled preinstalled email and calendar.provider apps and got a system without wakelocks (besides basic system ones), drained 0% in 6 hours of sleep (it's something like 0,x obviously). Cell network was on in 2g, everything else turned off. I also have stock gallery and music disabled (because I prefer different apps), don't know if they affect battery. I use Spookcity's kernel with interactive governor. Doubt it affects much in deep sleep.
Hi!
If you're interessted in a more detailed overview which app affects the battery life you could use BetterBatteryStats.
That way I found out that the radio/wifi sometimes runs riot ("No data connection" for 100% of the time) which drains the battery just a little bit more than usual. A reboot helps to fix this problem.
wkr ADT
 
  • Like
Reactions: Andi46

U03A6

New member
Dec 6, 2017
3
0
0
The overall experience is great, thanks for the great work!
I have two issues:
The phone doesn't boot when switched of and the charging symbol is visible. The power button just dosen't have any effect.
The second thing is that the battery drain is much higher than in stock, up to a point where the phone loses charge while being charged in use. Cellular network seems to be the culprit. Reception is better than with stock, though.
Any additional information I could provide to fix these bugs?
 

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