yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] Skazzy3:
SM-900P (kltedv) with lineage-16.0-20190302-nightly-kltedv-signed.zip is sending me into Download mode instead of booting.

Glad to hear I'm not the only one with this problem, just that I have to give this phone back today and it's kinda unfortunate.
[Samsung Galaxy S 5 Unified Development] godofsalt:
Depends.... If you have to give it back, can always do stock. From there, can put TWRP back on and do what ever. Except LOS 16.0, maybe, tomorrow!
[Samsung Galaxy S 5 Unified Development] haggertk:
kltedv users, please try this experimental build and report back: https://ftp.acc.umu.se/mirror/linea...-16.0-20190302-experimental-kltedv-signed.zip
[Samsung Galaxy S 5 Unified Development] hintegra:
Works fine now.
[Samsung Galaxy S 5 Unified Development] Couchy:
Boots for me now, thanks!
[Samsung Galaxy S 5 Unified Development] haggertk:
Thx guys, all klte* builds should be booting fine tomorrow. They are signed the same, so you can even flash the normal nightly over the experimental.
[Samsung Galaxy S 5 Unified Development] Skazzy3:
It works! 900P
[Samsung Galaxy S 5 Unified Development] dezraj:
I am also having the problem of going straight to download mode after installing the official klteduos build. Ended up formatting all data and losing all my apps for nothing. :(

I hope you can fix that soon.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: klteduos, kltedv & S5 klte Variants Official LineageOS 16.0 Fix

Is tomorrow soon enough for you? ;)

Thanks :good: LineageOS Quick Response Team!

"all klte* builds" - includes klteduos & all other S5 klte variants. Use build 2019-03-03 or newer:

klte - SM-G900AZ, SM-G900F, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8, SM-S902L - This one already works fine since the Official 16.0 build 2019-03-01 initial launch as I reported here and here for a 2019-03-02 OTA successful update while running Magisk.

klteactivexx - SM-G870F

kltechn - SM-G9006V, SM-G9008V

kltechnduo - SM-G9006W, SM-G9008W

klteduos - SM-G900FD, SM-G900MD

kltedv - SM-G900I, SM-G900P

kltekdi - SCL-23

kltekor - SM-G900K, SM-G900L, SM-G900S

You can see what the LineageOS firmware builder is doing @ the present here: https://builds.lineageos.org/

***

" Ended up formatting all data and losing all my apps for nothing." - Just restore the full TWRP backup that surely you made before installing a major firmware change, right? :confused:

All users tinkering with their phones and/or installing custom firmwares without having a recent TWRP full backup and/or a Google cloud backup should be Hanged, drawn and quartered IMO.

***
[Samsung Galaxy S 5 Unified Development] godofsalt:
Seen few (3) hours late....

Holy MOLY, no Download mode!

AWESOME!!!

That said, I Thank You!

So awesome you were able to worked OUT.

Am sure you have had a wonderful time. It will get better, see, it already has.

Thank you! As well as your Team, that worked a ton too!
[Samsung Galaxy S 5 Unified Development] dezraj:
Yes, it is. I can wait with no problem. I still have a laptop to use the internet.

And yes, you can hang me, lol. I didn't backup my data. But I had nothing so important in my phone. The only thing I backup was my Whatsapp chat. My pictures and my downloads I had already copied to my laptop prior to updating. The only nuisance will be downloading all my apps again. :rolleyes:
[Samsung Galaxy S 5 Unified Development] Pat_D:
Hi I'm on the 03-02 klte build. Seems fast and stable, thanks to the developers. Anyway the camera won't open. Is it a bug or did I mess up something?

Edit: thanks for the reply, my phone is a sm-g900f, I have the latest firmware, twrp 3.2.1, gapps nano. Anyway I've just updated to the 13-02 build and now the camera works!

What doesn't work instead is google assistant. If I long press the home button (which in the settings is associated to the assistant) nothing shows up. Any ideas?

Edit 2: no magisk, no root, nothing, upgraded from official 15.1 via dirty flash.
[Samsung Galaxy S 5 Unified Development] anondev:
With the official do I have to clean flash or can I dirty flash?

EDIT: currently running unofficial
[Samsung Galaxy S 5 Unified Development] curiousrom:
LineageOS Camera Not Working Official 16.0 - Dirty Flash?

The stock LineageOS 16.0 camera (Snap - Camera, Video, Panorama & QReader for QR & bar codes) works fine on my S5 SM-G900M (klteub) running Official 16.0 build 2019-03-02 klte + Open GApps ARM 9.0 Pico + Magisk v18.1.

Dev [MENTION=2693412]haggertk[/MENTION] worked hard on Snap for 16.0 as you can see here in the LineageOS Gerrit: https://review.lineageos.org/q/owner:haggertk%40lineageos.org+snap

Maybe you could reboot, reproduce the problem & use the fast & easy SysLog to capture a logcat & attach it to a reply which could be useful to haggertk for troubleshooting.

Or maybe he prefers that we create bug reports as described in the LineageOS Wiki How to submit a bug report?

The current LineageOS firmware for the S5 klte + variants are unified and support several devices with hardware & firmware variations.

For example: klte - SM-G900AZ, SM-G900F, SM-G900M, SM-G900R4, SM-G900R7, SM-G900T, SM-G900V, SM-G900W8, SM-S902L

It's ESSENTIAL troubleshooting info that you guys specify the firmware build date, exact phone model number & if you modified the System or not like Magisk, custom kernel, etc.

Pro tip: I copy/paste my phone description from a .txt doc so I don't have to type it every time.

So could you please edit your post & include the phone model number? And read the logcat part above.

***

You did not say your device model nor which firmware you are running exactly. :rolleyes:

If you are running haggertk's unofficial 16.0 read this: Official 16.0 for S5 2019-03-01 - Dirty Flash Report

***
[Samsung Galaxy S 5 Unified Development] Vini69:
S5 klteduos with TWRP 3.2.3

Full wipe/format + lineage-16.0-20190303-nightly-klteduos-signed.zip

=> WORKS fine !

Not enough thanks for the time and efforts, it's greatly appreciated !

ps: su from addonsu-15.1-arm-signed.zip installs but doesn't seem to work
[Samsung Galaxy S 5 Unified Development] Anidatte:
I could, but do I need root access to capture a logcat? If it's necessary, can I use SU addon from version 15.1? On LineageOS Extras download page I don't see addon for 16.

Currently I'm using latest official build without root. Stock kernel, no Magisk, no other mods.

My bootloader is G900FXXU1CRH1, modem G900FXXU1CQK3.

Another issues I found in 20190302:

1. Something is broken with notifications in default messages app, I can hear the sound of notification, but the popup not showing up and the notification LED not blinking. Only default messages app are affected, as far as I tested.

2. The MMS cannot be downloaded with active data connection (LTE in my case). When I receive MMS it locks all data transfer (and my phone shows "X" near the cellular signal icon). When I restart data connection, the MMS will download normally and unlocks the connection.
[Samsung Galaxy S 5 Unified Development] curiousrom:
LineageOS Addonsu for 16.0? - Using Addonsu 15.1 on 16.0?

No & for some strange reasons a motorcycle tire does not fit on my bicycle either. ;)

Run addonsu-remove-15.1-arm-signed.zip from https://download.lineageos.org/extras maybe & good luck! :eek:

"...can I use SU addon from version 15.1?" - No!

The SysLog Play Store page explains how to give permission via adb if you don't have root.

Also in Syslog > 3-dots > FAQ > manually enable access which links to https://github.com/Tortel/SysLog > Readme.md.

The LineageOS Wiki - How to submit a bug report links to LineageOS Wiki - How to capture logs (logcat) without root using adb.

Pasting from my post in an other thread:

The Lineage Team Member jrizzoli posted here on 2019-03-01 about LineageOS Addonsu for 16.0: "It should be out next week".

Meanwhile on my Galaxy S5 klte 16.0 I use Magisk v18.1 for root & download also the MagiskManager.apk from that page.

First install LineageOS & Open Gapps if you wish, reboot to System then reboot to TWRP to install Magisk.

If you install Magisk for the first time via TWRP & don't see the Manager after rebooting: manually install the MagiskManager.apk and it should show that Magisk is installed properly.

I posted this S5 Official 16.0 OTA Update Success - 2019-03-02 and Magisk survived the OTA update.

***

[MENTION=8031265]kurtn[/MENTION] reported here that he is using successfully a addonsu-16.0-arm-unofficial.zip by [MENTION=7344859]RenanQueiroz[/MENTION] that he first posted here "Unofficial 16.0 addon while Lineage doesn't release an official one": https://xdaforums.com/moto-g-2014/orig-development/rom-lineageos-16-0-t3833953

I did not try it because he does not include a flashable removal tool.

If you just install LineageOS & Open GApps for now you can install LineageOS Addonsu for 16.0 later.

If you install Magisk, there is a completely uninstall function built-in.

If you use an unofficial Addonsu & the dev does not include a removal tool then I don't know how to remove it because I don't know what it installs nor if it includes an update survival script.

***
[Samsung Galaxy S 5 Unified Development] Anidatte:
[MENTION=4122877]curiousrom[/MENTION] Thank you for your answers, I really appreciate that.

So, I captured logcat after granting access to READ_LOGS for SysLog, but I have to write at least 10 post to add attachments or links, sooo... :D
[Samsung Galaxy S 5 Unified Development] curiousrom:
You can post anything here: https://xdaforums.com/general/off-topic
[Samsung Galaxy S 5 Unified Development] Anidatte:
LineageOS Camera Not Working Official 16.0 - Dirty Flash

https://drive.google.com/open?id=1zZQ_LD070sPR9tsNV77j7jGVT6VgsK9o

So, I still can't add files to post, but this link above should work just fine.

I capture this logcat after trying to open a Snap camera app from the launcher and from the Settings menu. Snap crashed every time I tried to do something with it.

In the meantime I upgraded to build 20190303, but this issue still exist.
[Samsung Galaxy S 5 Unified Development] portsample:
Last night's build (lineage-16.0-20190303-nightly-klteactivexx-signed) installed on S5 Active (G870F) no problem. Many thanks.
[Samsung Galaxy S 5 Unified Development] Fly_7113:
Hello everyone, I did a clean install of Lineage OS 16 build 03/03/2019 with OpenGapps Mini on my SM-G900T. Everything is so smooth, installation went on with no problems.

Then I wanted to gain root access for some customizations, and given that there is no addonsu for LOS 16 yet, I chose the Magisk way.

Booted into recovery and flashed zip. According to the output everything went smooth. Booted to system and installed Magisk Manager. Then I opened the app.

And here the problem comes: Magisk manager doesn't see Magisk installed. I tried to download again the zip, booted to recovery, flashed Magisk uninstaller and then again the installer. No positive results though.

Is anyone having the same issue?
[Samsung Galaxy S 5 Unified Development] Ibuprophen:
[MENTION=4122877]curiousrom[/MENTION] had posted the following that has both Unofficial AddonSU and Magisk pointers included...

https://xdaforums.com/showthread.php?p=79027812

Good Luck!

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.
[Samsung Galaxy S 5 Unified Development] fbs:
random 2-sec whole-system freeze is driving me crazy
[Samsung Galaxy S 5 Unified Development] Ibuprophen:
I've gotta state that today's build (03-Mar-2019) is a very good improvement [MENTION=2693412]haggertk[/MENTION] on my SM-G900T device after performing another clean installation using only the Firmware and OpenGApps first and then the Firmware and MindTheGApps second. :thumbup:

No issues experienced with the MAC address as previously reported and its surprisingly running much more smoothly and even shuts down and restarts much more quickly as well.

I had tested this without any additional items like Kernels, Unofficial AddonSU, etc... So I can get a better idea of how it runs with those barebone essentials.

I'll be doing some more "trial and error" style testing with a few other variations but, I just wanted to provide you with my initial feedback.

To add, though very few of them on the forum, I just wish that there were more Lineage Team Maintainers that popped in on the forum more than once every 6 months (if that) for feedback and support as you do. Thank you so much for keeping the XDA Forum in your loop My Friend! :)

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.
[Samsung Galaxy S 5 Unified Development] kurtn:
Please don't call GApps "barebone essentials"
[Samsung Galaxy S 5 Unified Development] anondev:
For some reason I have been getting random reboots on both official and unofficial (and 15.1) on my G900I. Does anyone know how to diagnose it or any possible fixes for it?
[Samsung Galaxy S 5 Unified Development] Anidatte:
HCE / Google Pay not working on LOS16?

Today I tried to pay using Google Pay, but it doesn't seems to work. NFC itself is working correctly, but HCE / Google Pay doesn't.

SM-G900F / klte with latest 20190303 build, OpenGApps nano, latest bootloader and modem. No root, no magisk.
[Samsung Galaxy S 5 Unified Development] shkedov:
Yes, you should post a logcat so devs can debug it and see what's causing it.

I don't experience random boots in my kltechn (g9006v) so it could be maybe something with a specific app you use, maybe?? :confused:

And sometimes it can be corrosion on the logic board, so it you are familiar with contact cleaners and doing it safely on your phone - it could be a reason too.

After all, our S5 weren't manufactured yesterday :p
[Samsung Galaxy S 5 Unified Development] DoonPhone:
I'm exposing myself as a novice when I ask this question but it's been something that I've wanted to know for some time:

In much the same way PC operating systems require more horsepower with newer versions (XP's system requirements are less than Win 7's, which are less than Win 10) does each Lineage OS subsequent release demand more resources from my aged SM-G900T? In short, is 14.x less demanding on my phone than 15.x or 16.x? And is 15.x Official more reliable than 16.x Unofficial?

I hope I made myself clear and I'm ready for the noobie bashing but this falls into the Gotta Know category.

Thanks.
[Samsung Galaxy S 5 Unified Development] kurtn:
OK I'm first with bashing! I don't think newer android requires more horsepower. But your apps do. Especially GApps has been growing bigger. But hey S5 is still a powerful device compared to modern low enders.

For stability I recommend to stay on Oreo and give pie some more weeks to settle.
[Samsung Galaxy S 5 Unified Development] godofsalt:
well maybe.... As stated prior, the Experimental ktledv build works. but still seems to not be able to use the Updater!

It shows "Android 9, march 02 2019 ... last check 04march19, no new updates found " shows that there are no build yet.

do like the Updater, awesome feature, never lost Magisk, did not have to play with Opengapps... just let it do all the work, then reboot to newer build....

[MENTION=2693412]haggertk[/MENTION] -am planing to do a clean install, which is more work, however, want it in, clean and good to go. Sorry, it seems that, in "Experiment build" the updater seems to not detect newer builds.. Which is OK, with me, but felt you needed to know.

Just one more - Had some Bluetooth issues right from the start. (Yes, when it went Official, I ended like other on( kltedv- going into download mode)... So then, did a clean install of this build, I had Bluetooth problems right from start.) Am talking about a pop up, like very 1.1 second . took a bit to be able to Freeze that crap, just so I can complete the new start up.

So, is there a problem with Bluetooth on the Official 16.0 builds ? Seem to work fine prior (Unofficial 16.0, your last build)
[Samsung Galaxy S 5 Unified Development] haggertk:
Every "experimental"->"nightly" is a manual flash since forever. Updater purposely won't find it, simply download and sideload/flash in TWRP.
[Samsung Galaxy S 5 Unified Development] kurtn:
Deleted
[Samsung Galaxy S 5 Unified Development] curiousrom:
I don't like mystery links without description linking to a device that is not the topic of this thread. :eek:
[Samsung Galaxy S 5 Unified Development] Triviox:
After update my S5 to LOS 16 i saw that i have the "provider security parch" outdated.. How can i update it? Thanks!

https://www.directupload.net/file/d/5381/sufrm4ox_jpg.htm
[Samsung Galaxy S 5 Unified Development] Ibuprophen:
Okay... :confused:

To clarify what I had meant by "barebone essentials" was the use of Firmware and minimal GApps only since, Officially, LineageOS support is provided for the two GApps offered.

If the developer sees that something is not right with the GApps specifically, then they may decide to reach out to those developers and/or provide further guidance to its users.

Though I can only suggest/recommend this but, try not to be so picky with stating something that an individual "did" do (aka assuming) without first asking for some clarification.

I appreciate your time and understanding with this... :thumbup:

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.
[Samsung Galaxy S 5 Unified Development] dcarvil:
I've never been able to access the external SD card on my G900T in any version of LOS unless I use the ExSDCard Access Enabler Magisk module. Without the module, I can see the files in Solid Explorer, but they show 0 bytes and I get a "File not found" message whenever I do anything with them. With the module, I can access them via the /mnt/media_rw shortcut the module provides. Unfortunately, many apps are not able to use that shortcut.

I did a super clean install of todays build of LOS 16 following the instructions provided by [MENTION=4122877]curiousrom[/MENTION] (thanks for the instructions). I did not format the card using the phone however. The card is formatted ext4. Would reformatting the card resolve the problem? What format should I use?

Is there another workaround or fix that will allow all apps access to the external SD?

LOS lineage-16.0-20190304-nightly-klte-signed

Baseband/Boot Loader G900TUVU1GQC2 (latest available)

Thanks for any help.
[Samsung Galaxy S 5 Unified Development] kurtn:
Sorry, there is no update. With provider the closed source part of the device software is meant. Would be Samsung's job to provide an update.
[Samsung Galaxy S 5 Unified Development] xenokc:
How is Bluetooth stability, especially on KLTEDV?
[Samsung Galaxy S 5 Unified Development] Ibuprophen:
ext4 is the file system used for internal storage and is normally hidden and can't be accessed as a typical external/portable storage unless something (like that module) allows for it to be seen and accessed. The ext4 also doesn't have an Identifier or similar like a drive letter on a PC or a drive label name either.

It's a little challenging to explain...

When needed, I personally use the PC software called Partition Magic to clean and repartition a MicroSD. It will be able to see and work with any hidden partitions that aren't typically seen like the ext4 partition.

There's other software out there that are just fine for this as well. I can only mention what I use.

When formatting a MicroSD, I just simply use FAT32 and, so far, hasn't been an issue for myself and if you do change the format of the file system, be sure to backup anything you currently have on it that you want to save because this would wipe it clean.

I hope that I had explained this okay via text... :thumbup:

Good Luck! :)

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.
[Samsung Galaxy S 5 Unified Development] dcarvil:
Thanks, that helped. I reformatted the SD using TWRP, which created an exfat partition. That seems to have fixed it.
[Samsung Galaxy S 5 Unified Development] Ibuprophen:
I almost forgot about the exFAT... LOL! :thumbup:

It's been a while since I had gotten into this area. I guess it's something that you get used to and do it by practice rather than by reference.

I'm happy to see that your good to go! :)

Just remember, if the LineageOS asks about the handling of the MicroSD/External Storage, be sure to select the Removable Storage (I believe it's the second/bottom option) because if you select the Internal Storage (aka Adoptable Storage) option, it will want to reformat the MicroSD again and you'll end up in the previous situation.

Some like the Adoptable Storage option but, I've never been a big fan of it personally.

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.
[Samsung Galaxy S 5 Unified Development] xiaoyeng:
Waiting for the official build!~ ♥
[Samsung Galaxy S 5 Unified Development] Reverse-anastomosis:
It is here https://download.lineageos.org/klte
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: LineageOS Camera Not Working Official 16.0 Fix

Thanks :good::cool: for the logcat.

Sorry for the response delay, I've been hiking in a cloud forest reserve with no cell coverage there & it was awesome.

I checked in your logcat & searching for org.lineageos.snap which is the name of the LineageOS stock Camera app in S5 16.0 the first lines are:

W/PackageManager( 531): Destroying /data/user/0/org.lineageos.snap due to: com.android.server.pm.PackageManagerException: Package org.cyanogenmod.snap is <private info omitted>

I/BackupManagerService( 531): Package org.lineageos.snap not installed; dropping from full backup

And later:

--------- beginning of crash

E/AndroidRuntime( 3002): FATAL EXCEPTION: main

E/AndroidRuntime( 3002): Process: org.lineageos.snap, PID: 3002

E/AndroidRuntime( 3002): java.lang.RuntimeException: Unable to instantiate application com.android.camera.app.CameraApp: java.lang.IllegalStateException: Unable to get package info for org.lineageos.snap; is package not installed?

So my guess is that you don't even have Camera in > Settings > Apps & notifications or if you do what does it say under > Camera > Storage > App size?

There is already a merged fix for that and will be included in the 16.0 next build 2019-03-05 as seen in https://download.lineageos.org/klte/changes/ >>> 242966: Snap: Add back original-package in manifest: "When you upgrade from 14.1 to 15.1 and then 16.0, Snap is no longer working because the system is confused about the package name." and expanding > AndroidManifest.xml: "<original-package android:name="org.cyanogenmod.snap" />"

On my S5 G900M I went from Official 15.1 klte > unofficial 16.0 > Official 16.0 & in my logcat there is no mention of org.cyanogenmod.snap and the stock Camera is working fine:

I/ActivityManager( 597): START u0 {act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 pkg=org.lineageos.snap cmp=org.lineageos.snap/com.android.camera.CameraLauncher bnds=[827,1674][1018,1914]} from uid 10223

I/ActivityManager( 597): Start proc 6380 : org.lineageos.snap/u0a23 for activity org.lineageos.snap/com.android.camera.CameraLauncher

Please report back after updating to build 2019-03-05 or newer.

If you did not "upgrade from 14.1 to 15.1 and then 16.0" & updating does not fix the problem maybe you will need to do a clean install: wipe both System & Data in TWRP or do a S5 LineageOS Super Clean Install which recreates the entire Data partition's file system instead of just wipe that only erases files.

***
[Samsung Galaxy S 5 Unified Development] kurtn:
SU 16.0 is in downloads