[G800F/M/Y][ROM][8.1.0][OPM2] LineageOS 15.1 for G800F/M/Y [Alpha]

Search This thread

a-dead-trousers

Senior Member
Jul 28, 2016
287
1
141
Can you release more updates and make it 100% stable? There's alot of SM-G800F roms with bugs in them and nobody updates them and before you make another rom pls finish this one
Hi.

This ROM is from fans, for fans. Sadly, there are not many developers here. So, if you want a "stable" and fairly recent ROM switch back to the 14.1 release, which I use for nearly two years now without any major problems.
https://forum.xda-developers.com/ga...t/g800f-m-y-lineageos-14-1-g800f-m-y-t3549055
There is a montly build with latest security updates but no further development.
Lets face it: The SM-G800F isn't built for Android O and even N was quite a struggle to get it running. Samsung itself supports only MM. Furthermore, hennymc, the main developer here and owner of the github repository was not very active lately. So I doubt that we will see a "100% stable" 15.1 release in the near future or ever at all.

wkr
ADT
 
Last edited:
  • Like
Reactions: Harp_River
Feb 1, 2016
5
0
Hi.

This ROM is from fans, for fans. Sadly, there are not many developers here. So, if you want a "stable" and fairly recent ROM switch back to the 14.1 release, which I use for nearly two years now without any major problems.
https://forum.xda-developers.com/ga...t/g800f-m-y-lineageos-14-1-g800f-m-y-t3549055
There is a montly build with latest security updates but no further development.
Lets face it: The SM-G800F isn't built for Android O and even N was quite a struggle to get it running. Samsung itself supports only MM. Furthermore, hennymc, the main developer here and owner of the github repository was not very active lately. So I doubt that we will see a "100% stable" 15.1 release in the near future or ever at all.

wkr
ADT
:( OK thanks
 

saintetienne

Senior Member
Jan 7, 2012
161
16
Hi.

This ROM is from fans, for fans. Sadly, there are not many developers here. So, if you want a "stable" and fairly recent ROM switch back to the 14.1 release, which I use for nearly two years now without any major problems.
https://forum.xda-developers.com/ga...t/g800f-m-y-lineageos-14-1-g800f-m-y-t3549055
There is a montly build with latest security updates but no further development.
Lets face it: The SM-G800F isn't built for Android O and even N was quite a struggle to get it running. Samsung itself supports only MM. Furthermore, hennymc, the main developer here and owner of the github repository was not very active lately. So I doubt that we will see a "100% stable" 15.1 release in the near future or ever at all.

wkr
ADT


Thanks for the information , I am just contemplating switching from stock 6.0.1 to the 14.1 you mention , if you have been using for 2 years it must be pretty solid , any issues or drawbacks ?

cheers
 

3442

New member
Aug 11, 2018
2
4
Are there any news regarding the storage bug? I appreciate so much all the great work you have all put on this, and understand that I shouldn't (and won't) ask about updates, but I would like to know the status on this particular bug since it can be quite annoying to get around it. I've noticed that it only occurs when image files are involved. For example, I can send photos in WhatsApp only if I compress them first or rename them to something like "image.png.pdf". Not sure if that's of any help.

Again, thanks!
 
Last edited:

a-dead-trousers

Senior Member
Jul 28, 2016
287
1
141
Thanks for the information , I am just contemplating switching from stock 6.0.1 to the 14.1 you mention , if you have been using for 2 years it must be pretty solid , any issues or drawbacks ?
The only "problem" I encountered is a sporadic slightly higher battery consumption, but nothing a reboot can't fix.
Sometimes this happens right after the montly security update, other times it happens at purely random. So nothing that can be pinned down exactly and therefor not fixed for good.
I would also recommand that you use spookcity's kernel.
https://forum.xda-developers.com/ga...el-spookcitykernel-n-7-x-custom-roms-t3626015
It has some quite interessting features built-in. For example some governors to lower the battery consumption. But a few circuit boards revisions might have problems with the overclocking, so they won't be stable. Just try it and see for yourself. You can always switch back to the kernel in this ROM.

wkr
ADT
 
Last edited:
  • Like
Reactions: saintetienne

Friedensfurz

Senior Member
Are there any news regarding the storage bug? I appreciate so much all the great work you have all put on this, and understand that I shouldn't (and won't) ask about updates, but I would like to know the status on this particular bug since it can be quite annoying to get around it. I've noticed that it only occurs when image files are involved. For example, I can send photos in WhatsApp only if I compress them first or rename them to something like "image.png.pdf". Not sure if that's of any help.

Again, thanks!
No problem here with sending WA images. I use Sdcard as internal formatted with F2FS. Strange thing is, that the patches to fix this issue were already applied. I had the issue with Firefox and wasn't able to download anything, but after a while it worked somehow. Very strange ?
 

3442

New member
Aug 11, 2018
2
4
No problem here with sending WA images. I use Sdcard as internal formatted with F2FS. Strange thing is, that the patches to fix this issue were already applied. I had the issue with Firefox and wasn't able to download anything, but after a while it worked somehow. Very strange ?

I have investigated on this a bit and found the following. I don't know how much of this was already known.

  • The issue occurs when any non-system app attempts to access /sdcard.
  • /sdcard is actually the following symlink chain: /sdcard -> /storage/self/primary -> /mnt/user/0/primary -> /storage/emulated/0.
  • /storage/emulated/0 is owned by user root and group sdcard_rw (GID 1015). It has access bits 0771 (full permissions for user and group, only transversable by others). Therefore, only processes on the sdcard_rw group can access it.
  • The OS is not adding apps to the sdcard_rw group, no matter if you try to give the storage permission from the UI or with pm. As a result, apps think they have the internal storage permission (and the OS does, too), but the kernel refuses any access to /sdcard since they are not in sdcard_rw. Logcat doesn't seem to say anything useful.

By the way, I'm not using a SD card as internal storage.
 
Last edited:

deSSy2724

Member
Sep 17, 2011
19
0
2Can I follow the same instruction to return to stock rom if I have "[7.1.2]RESURRECTION REMIX N 5.8.5][unofficial][kminilte" installed* and then to try this rom?
 

jimmy999x

Senior Member
Mar 13, 2016
252
335
buenos aires
2Can I follow the same instruction to return to stock rom if I have "[7.1.2]RESURRECTION REMIX N 5.8.5][unofficial][kminilte" installed* and then to try this rom?

go to your custom rom (twrp) and make all the wipes (make a backup of your relevant information) then go to restart and choose in download mode, download your samsung stock software (I recommend using the program samfirm, ignore that says abandoned , keeps running) and installs by odin
 

Yoggyp

New member
Aug 28, 2018
1
0
The battery problem also happens to me sometimes because of "Network Standby". When this problem happens, I just reboot my phone and the battery is not drained anymore ;)

Hello, the "Network Standby" battery problem also happens to me on two different devices. Up to 75% of the battery is sucked up by this "task". Reboot probably stop it some moment then it begins again. This is the only inconvenient thing for me on this ROM (great job guys) , but still it is a real problem.

have a nice day
 

Frostcrystal

Member
Sep 26, 2018
5
1
I've just installed the latest build of 15.1 on my G800F. Everything seems to be working great so far except for the mobile network standby battery drain issue, and one other thing that I haven't seen mentioned on this thread: Facebook Messenger is having trouble taking photos from the app. WhatsApp has no issues, so I'm wondering if anyone else here has encountered a similar problem?
 

sygey

New member
Jan 18, 2017
2
0
I've just installed the latest build of 15.1 on my G800F. Everything seems to be working great so far except for the mobile network standby battery drain issue, and one other thing that I haven't seen mentioned on this thread: Facebook Messenger is having trouble taking photos from the app. WhatsApp has no issues, so I'm wondering if anyone else here has encountered a similar problem?

Yes i confirm! i have similar isues! And the rom it,s a little bit lagy ..lazy
 

Frostcrystal

Member
Sep 26, 2018
5
1
Looks as though it's the same bug mentioned in the last page by 3442 - Kindle, Dropbox and other ebook readers are having issues downloading/exporting files to internal storage, temporarily or permanently. I was under the impression that this issue had already been fixed earlier in the year, guess I was wrong?

EDIT: Logcat seems to confirm that there are file read/write issues. I've attempted giving 777 permissions to the temp folders the apps use, no luck. Nothing seems to be wrong with runtime-permissions.xml. At this point I'm thinking that I'll probably revert back to 14.1.

I haven't tried out device encryption, but when reverting I'll try it out prior to wiping my phone.
 
Last edited:
Jul 10, 2018
13
5
Is device encryption working on this ROM?

See my old post:

But it seems encryption also not working. It ends on bootloop.

But i found a workaround. Only start encryption is not working on all Oreo builds for G800F, it end on endless boot loop. But when data partition is already encrypted, it works.

So when you need encryption, first install or downgrade to lineageos 14.1, start encryption process and after encryption process is finished and phone is encrypted, flash LineageOS 15.1
 
  • Like
Reactions: Panzerknakker

hackintosh5

Senior Member
Sep 15, 2017
1,246
949
See my old post:



But i found a workaround. Only start encryption is not working on all Oreo builds for G800F, it end on endless boot loop. But when data partition is already encrypted, it works.

So when you need encryption, first install or downgrade to lineageos 14.1, start encryption process and after encryption process is finished and phone is encrypted, flash LineageOS 15.1
That's a) a very bad idea because you are cross-flashing data and b) because Oreo tries to use a different encryption method by default.
 

Frostcrystal

Member
Sep 26, 2018
5
1
Here's another issue that I've been running into lately: Every once in a while (it's only happened twice so far), the battery stops charging. I'll plug the power cord into my phone and the battery indicator will show a lighting bolt and the charging light will come on, but it's not actually charging - on the contrary, it actually drains battery faster because the LED is on.

The solution is to do a reboot. You may also have to pull the battery to get it to shut down properly.
 
  • Like
Reactions: ugeins

ScRe13

New member
Nov 11, 2018
3
0
I wanted to backup Whatsapp messages to the Drive but it says it failed. Does anyone know how to overcome that?

I think it is related to storing data to the internal storage.
I'm using @Andrea224's build of 21.07.2018.
Whenever a backup should be performed, the are some errors related to the internal storage:

/data/data/com.whatsapp/files/Logs

Code:
2018-11-11 11:56:54.929 LL_I W [840:WhatsApp Worker #4] chat-settings-store/backup/to /storage/emulated/0/WhatsApp/Backups/chatsettingsbackup.db.crypt1
2018-11-11 11:56:54.942 LL_E W [840:WhatsApp Worker #4] chat-settings-store/backup failed; exception=java.io.FileNotFoundException: /storage/emulated/0/WhatsApp/Backups/chatsettingsbackup.db.crypt1 (Invalid argument)
### begin stack trace 2.18.349-play-beta
java.io.FileNotFoundException: /storage/emulated/0/WhatsApp/Backups/chatsettingsbackup.db.crypt1 (Invalid argument)
	at java.io.FileOutputStream.open0(Native Method)
	at java.io.FileOutputStream.open(FileOutputStream.java:287)
	at java.io.FileOutputStream.<init>(FileOutputStream.java:223)
	at java.io.FileOutputStream.<init>(FileOutputStream.java:171)
	at com.whatsapp.ed.b(:81582)
	at com.whatsapp.data.ct$a.doInBackground(:72274)
	at android.os.AsyncTask$2.call(AsyncTask.java:333)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
	at com.whatsapp.util.dn.run(Unknown Source:7)
	at java.lang.Thread.run(Thread.java:764)
### end stack trace

But it looks like this project is no longer maintained, so I think there will be no bug fixing anymore?
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 53
    This is a LineageOS 15.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
    Please do not ask for support or ROMs for the G800H. G800F and G800H have nothing in common.

    Working features
    • HW accelerated GUI
    • Initiate and receive calls
    • Camera (only photos)
    • Flash Light
    • Sound
    • Fingerprint scanner
    • 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)
    • Wifi
    • GPS
    • Bluetooth (A2DP, HFP, HID)
    • Mobile Data
    • SMS
    • MTP storage
    • USB-OTG (Keyboard, Mouse, USB-Audio)
    • IR
    • NFC
    • Video reproduction is still sometimes a bit buggy on browser (Youtube works fine)

    Untested features:
    • SD-Card as internal storage

    Known issues:
    • USB-OTG (Mass-Storage): detected but the file-system is not usable and will be corrupted afterwards (--> do not connect your USB-stick at the moment)
    • SELinux not enforcing
    • Video recording is still buggy/not working (crashes)
    • Fingerprint scanner can only records 3 fingers and sometimes it could be unresponsive

    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)
    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.
    • 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.

    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, 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.

    Flash ROM:
    • Reboot into recovery mode (Press Volume-Up + Home + Power button)
    • 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.
    • Copy GApps and LineageOS ROM zip to your device's internal or external SD card
      • Connect your device via USB to a PC. You should see the device in the Windows File Explorer now.
        • If you do not see the device in File Explorer, make sure that MTP is enabled (inside Mounts, click on Enable MTP).
        • If MTP does not work from recovery, try to copy via MTP by booting your old Android ROM or just remove the external SD card and copy to it directly.
      • Select one of the two drives (internal or external SD) and copy the files to it.
        • Do not put the files into the data directory of the internal sd card, otherwise they will be wiped in the next step.
    • 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 LineageOS 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:
    24/10/2017:
    * Wake on Home button press
    * Model string fixed ("G800F" instead of "G800")
    * GPS fixed
    * Bluetooth fixed
    * Update to newest LineageOS sources
    * Note: Android 8.0 requires a new TWRP recovery (build from 22/10/2017). otherwise you will not be able to flash the image ("E3004: This package is for device: kminiltexx,kminiltedv,kminilteub,kminilte; this device is .")
    
    10/10/2017:
    * telephone calls working
    * Camera works (recording videos might still not work)
    * LineageOS sources updated
    
    24/09/2017:
    * Initial test build

    Source:

    Help from other developers is always welcome. Just ask in this thread or PM if you want to help.

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

    XDA:DevDB Information
    [G800F/M/Y][ROM][8.1.0][OPM2] LineageOS 15.1 for G800F/M/Y [Alpha], ROM for the Samsung Galaxy S5 Mini

    Contributors
    hennymcc, ayke, Andrea224, spookcity138, mirhciulica, CTXz
    Source Code: https://github.com/cm-3470

    ROM OS Version: 8.x Oreo
    ROM Kernel: Linux 3.4.x
    ROM Firmware Required: TWRP Recovery [version >= 22/10/2015]
    Based On: LineageOS

    Version Information
    Status: Alpha

    Created 2017-09-24
    Last Updated 2018-07-05
    21
    A new build is available:
    https://www.androidfilehost.com/?fid=962021903579487392

    Changelog:
    * Wake on Home button press
    * Model string fixed ("G800F" instead of "G800")
    * GPS fixed
    * Bluetooth fixed
    * Update to newest LineageOS sources

    Note: Android 8.0 requires a new TWRP recovery (build from 22/10/2017). otherwise you will not be able to flash the image ("E3004: This package is for device: kminiltexx,kminiltedv,kminilteub,kminilte; this device is .")

    TWRP Link: https://www.androidfilehost.com/?fid=962021903579487486

    Thanks to Ayke for the new TWRP build. Unfortunately it is not yet available on the official TWRP download page.
    18
    I uploaded a new build with RIL and camera fixed. See opening post for more details.
    18
    Hi everyone, now that I'm a contributor I've updated the main post and I've finally added my Gdrive folder link where you can find the last and the previous LOS 15.1 updates. I'll release them at least monthly/weekly, when the security patches are updated or if there's a new fix for the phone. Also, I'll post a changelog (even if short) about the update.

    Regards
    17
    A short status update on Oreo:
    Lineage 15.1 finally left the staging area last week (which does not mean that it is already released).

    I just tried it and telephony, mobile data, wifi, audio and bluetooth are working.
    Camera is not working anymore (neither taking photos nor video recording) as the patches I applied to 15.0 do not apply anymore to 15.1.
    For some reason RIL (i.e. telephony) which was working in 15.0 is broken now but I did not take a deeper look at it so far.

    Camera video recording (with HAL1) is still not fixed in lineage. About 1/3 or 2/3 of the devices supported by lineage 14.1 only support camera HAL1 so the chances are quite good that this will be fixed in lineage in the next months.

    As long as camera (at least taking photos) and RIL is not working I will not provide builds for it. All source updates are pushed to github in case somebody wants to try it.
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