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

Search This thread

Andrea224

Senior Member
Jan 18, 2016
795
475
Rome
what changes in the Roma 15 20171119
As I said, it's only a repo sync, so, unless there were some changes by hennymcc and others, everything should be as before (but LOS now is more updated, i.e. november 5 patch)

---------- Post added at 10:35 AM ---------- Previous post was at 10:31 AM ----------

Thanks for the new unofficial build, works better than the Oct. build, sadly it still has the same issue with settings, as soon as you remove something from LOS like Trebuchet or other integrated apps it FCs.
That's probably because it isn't already done. I think it would take another 1 or 2 months to be at least almost done. Time will see.
 
  • Like
Reactions: CHEF-KOCH

Tek_No

Senior Member
Jul 21, 2008
219
67
Flashed latest yesterday : working fine but having some strange things going on with alarm sounds. When setting an alarm it is notifying you immediately with a notification using the default notification sound. Then when the alarm is being triggered it is playing the alarm sound in the background with the notification sound on top of it.

Anyone else having the same problem going on?

---------- Post added at 08:24 AM ---------- Previous post was at 07:57 AM ----------

Flashed latest yesterday : working fine but having some strange things going on with alarm sounds. When setting an alarm it is notifying you immediately with a notification using the default notification sound. Then when the alarm is being triggered it is playing the alarm sound in the background with the notification sound on top of it.

Anyone else having the same problem going on?

No worries, found it in the mean time : needed to disable notifications for clock alarm. All good now.
 

Andrea224

Senior Member
Jan 18, 2016
795
475
Rome
Flashed latest yesterday : working fine but having some strange things going on with alarm sounds. When setting an alarm it is notifying you immediately with a notification using the default notification sound. Then when the alarm is being triggered it is playing the alarm sound in the background with the notification sound on top of it.

Anyone else having the same problem going on?

---------- Post added at 08:24 AM ---------- Previous post was at 07:57 AM ----------



No worries, found it in the mean time : needed to disable notifications for clock alarm. All good now.
That was quick.
 

hackintosh5

Senior Member
Sep 15, 2017
1,246
947
I have important info about the random reboots. After flashing the unofficial November update, my device did not reboot till I connected it to USB. Not a wall charger, it must be a REAL computer. If I create an ADB shell and wait for the reboot, I see the reboot on the device but adb shell stays connected; I can retain root (via magisk su command) across reboots. Will upload last_kmsg soon. Now testing if reboots occur when no USB or power.
EDIT 1: It does reboot when no power at all.
EDIT 2: If it reboots, and you connect it to usb while it is booting, adb says no devices.
 
Last edited:

hackintosh5

Senior Member
Sep 15, 2017
1,246
947
Output from adb bugreport attatched (all created during boot, after random reboot) will soon collect logcat during reboot.
 

Attachments

  • bugreport-lineage_kminilte-OPR3.170623.013-2017-11-21-14-54-26.zip
    1.8 MB · Views: 10
  • bugreport-lineage_kminilte-OPR3.170623.013-2017-11-21-15-20-53.zip
    2 MB · Views: 8
  • bugreport-lineage_kminilte-OPR3.170623.013-2017-11-21-15-27-06.zip
    2.2 MB · Views: 4
  • bugreport-lineage_kminilte-OPR3.170623.013-2017-11-21-15-42-31.zip
    2 MB · Views: 6

hackintosh5

Senior Member
Sep 15, 2017
1,246
947
More space, more running time...

Output from adb bugreport attatched (all created during boot, after random reboot) will soon collect logcat during reboot.

Code:
 KILLING SYSTEM PROCESS: Blocked in handler on i/o thread (android.io)
11-21 19:11:21.165 20813 20991 W Watchdog: i/o thread stack trace:
11-21 19:11:21.227 20813 20991 W Watchdog:     at android.os.BinderProxy.transactNative(Native Method)
11-21 19:11:21.227 20813 20991 W Watchdog:     at android.os.BinderProxy.transact(Binder.java:748)
11-21 19:11:21.227 20813 20991 W Watchdog:     at android.os.IInstalld$Stub$Proxy.freeCache(IInstalld.java:962)
11-21 19:11:21.227 20813 20991 W Watchdog:     at com.android.server.pm.Installer.freeCache(Installer.java:402)
11-21 19:11:21.227 20813 20991 W Watchdog:     at com.android.server.pm.PackageManagerService.freeStorage(PackageManagerService.java:4362)
11-21 19:11:21.227 20813 20991 W Watchdog:     at com.android.server.storage.DeviceStorageMonitorService.check(DeviceStorageMonitorService.java:204)
11-21 19:11:21.227 20813 20991 W Watchdog:     at com.android.server.storage.DeviceStorageMonitorService.-wrap0(Unknown Source:0)
11-21 19:11:21.227 20813 20991 W Watchdog:     at com.android.server.storage.DeviceStorageMonitorService$1.handleMessage(DeviceStorageMonitorService.java:166)
11-21 19:11:21.228 20813 20991 W Watchdog:     at android.os.Handler.dispatchMessage(Handler.java:105)
11-21 19:11:21.228 20813 20991 W Watchdog:     at android.os.Looper.loop(Looper.java:164)
11-21 19:11:21.228 20813 20991 W Watchdog:     at android.os.HandlerThread.run(HandlerThread.java:65)
11-21 19:11:21.228 20813 20991 W Watchdog:     at com.android.server.ServiceThread.run(ServiceThread.java:46)
11-21 19:11:21.228 20813 20991 W Watchdog: *** GOODBYE!
11-21 19:11:21.228 20813 20991 I Process : Sending signal. PID: 20813 SIG: 9
11-21 19:11:21.253 21819 21819 E JavaBinder: !!! FAILED BINDER TRANSACTION !!!  (parcel size = 1296)

Note that Google Play had previously been prompting me to free up storage to install updates.

Will grab more logcats.

EDIT: All my logcats have the same GOODBYE! I think we need to fix the free storage checker. I think a temporary fix would be to disable auto update in Google Play and/or free up storage. Freeing up storage might not work though. I just don't know.

EDIT 2:
11-21 13:48:53.758 883 883 F DEBUG : Build fingerprint: 'samsung/kminiltexx/kminilte:6.0.1/MMB29K/G800FXXU1CPK5:user/release-keys'

Slightly worrying... :confused:
EDIT 3: I had ~2% free Internal Storage, and no SD Card, when random reboots were occurring. Still this doesn't explain why new (clean) flashers are getting GOODBYEs. Perhaps there are two different errors...
 
Last edited:

mongo0

Senior Member
Nov 7, 2013
174
110
Setting search I can confirm is broken. For issue 1, check the logcat. Package installer crashes rather than the main app when manifest is wrong. Idk about root, i use magisk

Sent from my kminiltexx using XDA Labs

Thanks. First, I installed Magisk. All went fine and SU privileges are present. Then I tried to install an apk, and suddenly it worked. The 'package installer' started successfully for the first time and did its job flawlessly.

Looking forward to follow the changes in this project
 
  • Like
Reactions: hackintosh5

bnt734

Member
Dec 16, 2012
23
3
Hi,
Can't install it, after each reboot i have the message "restore to factory image" and device is back to TWRP :(
I install TWRP with the link on 1st page with Odin,
Any idea?
 

hackintosh5

Senior Member
Sep 15, 2017
1,246
947
Hi,
Can't install it, after each reboot i have the message "restore to factory image" and device is back to TWRP :(
I install TWRP with the link on 1st page with Odin,
Any idea?
What theme does the message appear in? Did you enable OEM Unlock in stock? Does the command 'adb wait-for-any' finish, with the device booting from power off to error while plugged into usb?
How long does it take to show error?
Do you see screen with phone name?

Sent from my kminiltexx using XDA Labs
 

Bthamburg

Member
May 31, 2015
22
6
The update works much better, the search in the settings is fixed, but the video does not show in the browser and in the player ... solved the problem by installing the Lucky kernel.

I'am really new in install custom kernel. Could you upload your boot.img?
Is it right that it is nessary to use twrp version from 2017-07-09 for kernel update?
Thanks
 

bnt734

Member
Dec 16, 2012
23
3
What theme does the message appear in? Did you enable OEM Unlock in stock? Does the command 'adb wait-for-any' finish, with the device booting from power off to error while plugged into usb?
How long does it take to show error?
Do you see screen with phone name?

Sent from my kminiltexx using XDA Labs
Hi,
I'm able to unlock my screen, i can see the new icons / desktop and then 5 seconds after my phone is rebooting in recovery.
I was on LOS 14 before, did the upgrate to 15 as usuall, no USB connection / adb.
 

Andi46

Senior Member
Feb 7, 2016
238
131
Vechta
Hi,
I'm able to unlock my screen, i can see the new icons / desktop and then 5 seconds after my phone is rebooting in recovery.
I was on LOS 14 before, did the upgrate to 15 as usuall, no USB connection / adb.

why did you upgrade your OS using the standard update way? THAT can't be functioning.... :cool: from cm13 to 14.1 the were script ways, but.... i hope you have a backup stored on your external, or the other way start from the beginning with LOS 15
 
  • Like
Reactions: hackintosh5

wasya78

Senior Member
Mar 13, 2017
98
8
I noticed a function delete phone and contacts and standard posts in the system and put new versions of contacts and phone and other posts and after reboot выскавивает message that the application systems неотвечает lineage15
 

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