yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] Ibuprophen:
[MENTION=2693412]haggertk[/MENTION], I just wanted to add, to my previous post, the following (additional information) listing of what I had used/tried/tested, where their located and any additional information that I could think of that may (hopefully) be helpful to you.

Official LineageOS 16.0 build Used

lineage-16.0-20190314-nightly-klte-signed.zip

https://download.lineageos.org/klte

Official LineageOS 16.0 AddonSU Used

addonsu-16.0-arm-signed.zip

https://download.lineageos.org/extras

GApps Packages Used With Clean Flash

(of course I used one or the other and never together)

MindTheGapps

MindTheGapps-9.0.0-arm-20190216_211054.zip

http://downloads.codefi.re/jdcteam/javelinanddart/gapps

https://github.com/MindTheGapps/vendor_gapps

OpenGApps (Pico)

open_gapps-arm-9.0-pico-20190314.zip

https://github.com/opengapps/arm/releases/

https://opengapps.org/

Apps Used That Requires Root Access

(Tried anywhere from One to All of them)

ES File Explorer Pro

https://play.google.com/store/apps/details?id=com.estrongs.android.pop.pro

BusyBox Pro (Stericson)

https://play.google.com/store/apps/details?id=stericson.busybox.donate

Root Essentials

https://play.google.com/store/apps/details?id=com.superthomaslab.rootessentials

https://xdaforums.com/showthread.php?t=3359589

PowerGrasp File Manager

https://play.google.com/store/apps/details?id=com.malcolmsoft.powergrasp

Total Commander

https://play.google.com/store/apps/details?id=com.ghisler.android.TotalCommander

https://www.ghisler.com

Root ToolCase

https://play.google.com/store/apps/details?id=com.cpu82.roottoolcase

https://xdaforums.com/showthread.php?t=3601723

https://github.com/cp82/roottoolcase

The attached images (below) reflect, what I've been experiencing, in addition to the above report.

Please note that 2 of them may be for the BusyBox app but, the same popup messages are reflected for all the apps that require root.

View attachment 4723906

Thanks a bunch! :)

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

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] wdfitzpat007:
No Service SM-G900V

Upgraded to the 3-13-19 build, lost service the first time the battery died. Flashing baseband and modem does nothing this time, TWRP restore says that modem is locked.

After restoring everything else I have service again, but this build is signed with public keys, uber is broken, and google pay is broken. Any ideas? Could the problem be in the EFS?

Also the charging bug where booting is not possible while plugged in is still bugging away.
[Samsung Galaxy S 5 Unified Development] Borsti666:
I dont HAVE a working TWRP-Backup that I can restore. I just made a backup in the state of not working dsiplay...

Contacted google drive support before I posted here. They wind themselves out by saying "no official Software" and "thats a Samsung-Problem"...
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: Restore Google Backup 3x3 Pattern Problem

You can't access your Google Backup anyway so what do you have to loose trying what I suggested?

You did not answer my question: Maybe you could restore your TWRP backup which was made after you successfully restored your Google backup, right?

***
[Samsung Galaxy S 5 Unified Development] thetaphi:
Hi, thanks for the feedback. You are using bank cards from Poland, which is one of the few countries in the EU where banks don't support CDCVM (Customer Device Cardholder Verification Method) in their card infrastructure, so you have to enter your PIN code on the terminal (you can easily check this by reading your phone's virtual card with CardPeek and look into the ATR - you need a patch to show CDCVM). Interestingly, people from Germany can pay in Poland with HCE and fingerprint using CDCVM as all terminals support it, it's just your banks not allowing/supporting that in Google Pay. If you want to have this I'd suggest to try a Revolut card.

My request was about a confirmation if CDCVM works (it does accoring to card data) and this supports fingerprint or not. If you have to enter pin on terminal, it's not using CDCVM. If you have to enter unlock PIN on your phone and tap again, but fingerprint is not working for that, you have CDCVM but Google Pay does not recognize the fingerprint reader as "safe". At least in the original Android 6 firmware of the device this was the case, which made the phone unuseable for paying, as entering the complicated unlocking password and tapping again was a no-go.

I will try on my own the next time I take the old phone with me.
[Samsung Galaxy S 5 Unified Development] Privateblood:
Sorry if this question has already been answered, but (especially after seeing that a new build is being released daily since the 5th of March) I wanted to ask if it is possible to get these updates over the air (OTA) or must one reformat their device each time they want to switch to the newest build? Or is there a specific, optional instruction that must be followed before installing LineageOS that will enable receiving OTA updates? And lastly, are there cases in which even though it is possible to update over the air, it might be much better to do a fresh install due to maybe some leftover files or new files causing conflicts? Thank you for all your efforts to keep our precious S5s up-to-date.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Updating S5 Official LineageOS 16.0

"...or must one reformat their device each time they want to switch to the newest build?" - If you are asking about installing 16.0 over an other firmware like 14.1 or 15.1, or an other custom firmware that's an other story. If asking about updating an official 16.0 installation then continue below.

The S5 klte + variants Official LineageOS 16.0 built-in OTA Updater works fine (System > Advanced > Updater), I used it several times including this morning to build 2019-03-15.

It's important to have the most recent TWRP (3.2.3-0 @ the present) so it can run without errors the OpenRecoveryScript that the Updater is using in TWRP to apply the update. See Updating TWRP.

I described how I did it here with screenshots: S5 Official 16.0 OTA Update Success - 2019-03-02. Check the Changelog as illustrated as some updates have very little changes and are not worth the trouble. It's not necessary to update daily.

One of the advantage of the Updater is that it checks the integrity of the downloaded update before offering the option to install it as seen in the screenshot.

You can manually download & flash an update but then I would recommend to check the sha256 hash (linked just under every downloads in https://download.lineageos.org ) to make sure the download is not corrupted. I don't see any advantage to doing it manually.

A good practice is to have a recent full TWRP backup just in case including an EFS partition backup as described here: No Network, No IMEI, No SIM & EFS Partition Restore Fix if a cold boot: power off, wait 5 seconds & power on did not fix a network access problem.

"...it might be much better to do a fresh install due to maybe some leftover files or new files causing conflicts?" - No, the Updater updates all that is needed. If you installed Open GApps originally just after flashing the LineageOS firmware without rebooting in between then it includes a survival script. Same for Magisk or the LineageOS Addonsu if you installed it previously either at the same time you installed the LineageOS firmware + Open GApps or later.

Edit: [MENTION=9621336]Privateblood[/MENTION] I just added some screenshots made this morning. The third one is of > System > About phone > after pressing on Android version 9.

***
[Samsung Galaxy S 5 Unified Development] Privateblood:
Thanks a lot for quickly replying! One other question, how do you feel the battery life compares to that of the stock rom? I had tried a build from months ago, and my biggest gripe was that there was so much battery drain. Is this something maybe related to Android Pie itself? Is changing the theme to dark provide a visible boost to battery life? And lastly, since the Pie build becoming stable version and the bump from 15 to 16 happened very recently, can you estimate when would this release become more stable and be updated every two weeks or so? Having an update so often may prove annoying to me if it lasts too long. Thanks.
[Samsung Galaxy S 5 Unified Development] kurtn:
Ota works in default installation as long as you stay with official 16.0
[Samsung Galaxy S 5 Unified Development] curiousrom:
Battery Life LineageOS 16.0 vs Stock Samsung & 15.1

Thanks :good: for the Thanks.

"...battery life compares to that of the stock rom?" - I don't know because I bought my S5 900M in Oct. 2018, ran Samsung stock for only 2 days then LineageOS 15.1 until I installed unofficial 16.0 on Nov. 21, 2018 and now running official 16.0 since 2019-03-01.

All I can say is that LineageOS 16.0 for the S5 klte is better then 15.1, Doze is incredible with very low battery usage @ idle. I applied the tips described in Remove Animations UI Speedup Test - Taming Google & Apps.

"...I had tried a build from months ago" - Well official 16.0 was launched on 2019-03-01 and a ton of patches were merged since a couple of months so try again. ;)

"...Is changing the theme to dark provide a visible boost to battery life?" - YMMV depending on your usage. To extend battery life, thanks to the S5's Super AMOLED display properties which uses less power when the color is black, I use in LineageOS 16.0 > Settings > Display > Style > Dark and Dark Mode > Black. Also Display > Wallpaper > No wallpaper without the need of using any third-party theme engine like Substratum or whatnot.

Check the Pure Colors vs Power Consumption image attachment from [Info] AMOLED Power Consumption Tested and Explored. There are plenty of web pages on the subject as you can see in this web search: power usage black amoled screens.

View attachment 4724420

See this XDA portal article [Hands-on] LineageOS 16 gives you the Android Pie experience, but with extra goodies about the LineageOS 16.0 features.

"...can you estimate when would this release become more stable and be updated every two weeks or so?" - Sorry but my crystal ball is broken :crying: so can't predict which update will contain important updates or not. I can say that 16.0 is very stable & I had zero system crashes or unwanted reboots so far. You could follow this thread as users report when there are valuable changes or check in Settings > System > Advanced > Updater > 3-dots > Changelog or in https://download.lineageos.org/klte/changes/ . BTW you did not mention yet your exact S5 model.

Edit: Added a screenshot of LineageOS Updater > Preferences where you can set the Auto updates check to Never, Once a day, Once a week or Once a month.

View attachment 4724445

I never tested this but maybe it's possible to make a full restorable backup of your stock Samsung setup before trying 16.0. XDA site search: site:xdaforums.com/ s5 how to backup samsung stock or maybe a S5 user could chime in?

If you do a Google Backup in Samsung stock make sure not to use encryption & disable Screen lock & SIM lock before doing it to avoid restoration problems.

Make sure you have the most recent modem & bootloader before installing 16.0. I described how I updated my S5 G900M here & included Odin screenshots: S5 Odin Flashable Modem & Bootloader.

While in stock Samsung & after installing TWRP make an EFS partition backup before flashing LineageOS. See this post No Network, No IMEI, No SIM & EFS Partition Restore Fix

***
[Samsung Galaxy S 5 Unified Development] Privateblood:
Well, thank you for providing all this useful and detailed information and also guiding me to where I would best reach an answer to my questions. I am rocking an SM-G900FQ (Turkish Snapdragon variant; which, I assume, falls under klte(?)) that I bought in May 2014, 2-3 weeks after its release. And honestly, I am perfectly fine with this phone: it is the last Galaxy that Samsung made with a plastic, openable back which allowed me to just swap a new battery after the first 3 years and continue using it for another 3 years or so, it has waterproofing, headphone jack, the camera shoots really good (which I rarely use), and as I virtually never need the front camera I am more than happy to have taken the risk and made the decision back then to get this phone (and people hadn't received this phone well at all, saying it didn't improve much over the S4 and didn't deserve the higher price tag).

So I must say, during this near 5 year period of time I was perfectly happy with the stock ROM as I find it quite stable and snappy, to be honest. And I count myself rather fortunate since S5 is one of the rarest Samsung phones that was lucky enough to get its version bumped from 4.4 Kitkat to 5.0 Lollipop and then 6 Marshmallow within the official 2 years of support. Now we have 9 Pie and 10 is on the horizon, so when I found out that there was still an active development to my beloved phone I made the jump last December and broke my Knox counter (which resulted in Samsung browser refusing to go Private Mode even after I reverted back to the stock ROM, saying it detected rooting and won't allow Private Mode out of security reasons, which was a total bummer). Besides battery life, my biggest issue with the build then was that the phone would turn itself on as soon as I plug it in, which is big no-no in my book as I only ever charge my phone when it's switched on in emergency situations, and 99% of the time I charge it while it's switched off. Also, I had problems with Google services even after installing Gapps and Whatsapp failed to access my cloud backup on my Google Drive. Stock Google Gallery app also failed to load the content of my SD card (which I asked about here to no avail), so I had to try AOSP and HAVOC ROMs, within which these problems did not occur; however, my battery life took a major hit that I had to convert back to the stock ROM and have been using it since then.

Seeing Lineage ditched the experimental version 15 and bumped it to 16 very recently, I am now once again weighing up going back to it, and that is why I've been asking these questions about the stability of the ROM and the battery life. While I'm at it, maybe I should ask if not being able to charge the phone while it's off and not being able to view photos on the SD card in the stock Gallery app are fixed now.

Thank you for taking your time on my issues and providing invaluable insight that is very well-structured.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Camera, Gallery & Charging w/ S5 Off

"SM-G900FQ" - [MENTION=4828250]Ibuprophen[/MENTION] posted about SM-G900FQ vs. SM-G900F here & he included a spec comparison link. So LineageOS 16.0 klte should work.

Stock LineageOS 16.0 Camera > hamburger > Storage > if you select SD Card the photos & videos will be saved to /external sdcard I.D./Android/data/org.lineageos.snap/files/ & not in DCIM/Camera/ as usual. If Phone is selected it goes in the standard /storage/emulated/0/DCIM/Camera/.

Gallery works fine but in the Files album, official 16.0 could not see 800+ photos & videos taken while in unofficial 16.0 while the free open source Simple Gallery Pro on F-Droid and stock Files explorer can (screenshots). Otherwise Gallery works fine.

Workaround: drag all the old photos that Gallery does not see to /external sdcard I.D./DCIM/Camera or to computer. All new photos are seen in the Gallery > Album > Files.

Apps info > Gallery > Storage > Clear Storage & rebooting does not fix the problem.

That's on Official 16.0 for S5 2019-03-01 - Dirty Flash Report. I want to do a super clean install now so I can make proper official LineageOS Wiki > How to submit a bug report but keep on being delayed by all your questions. ;)

Battery charging: with the S5 turned off the battery status notification LED is not working but the phone is charging. With the phone off & connected it will not boot to system when pressing the Power button. The cable needs to be disconnected & wait a few seconds before pressing the Power button.

A long press (8-10 seconds) of the Power button with the S5 off & connected will reboot the charging process & the screen will turn on & show the charging animation.

With the charging animation stopped & the battery icon showing full, disconnecting the cable & powering on the S5 it will show battery charged at 90-92% on the status bar.

In TWRP with the S5 connected & charging to 100% + keeping it connected 20 minutes more, when booting to System it will show 100% on the status bar.

With the S5 turned on the LED works & the phone is charging. With the battery showing 100% on the Status bar & the S5 disconnected if rebooted it will now show 90~92%. More explanations in this post.

If you reboot again with the S5 disconnected and with the battery @ 92% or less it will show only a 1~2% battery loss.

I wonder if [MENTION=2693412]haggertk[/MENTION] is aware of all this. :confused:

***
[Samsung Galaxy S 5 Unified Development] Borsti666:
Either I dont understand you or you dont understand me...

At first I have the problem, that I have a black screen. In this state I entereded TWRP to make a backup of everything so I can try to solve the original problem with the black screen...

I recognised that I can only solve it by wiping \data. (For taht Im lokking for an alternative way...)

Not that big problem at all... IF I could restore my (only) google-backup, what doesnt work because of the pattern...

So I have all my data and settings in the google backup I cant access and in the TWRP backup with the black screen...

Yes, I know "why dont you have any other backups".... I have some, but they are not "actual/current", so Id like to avoid using them...
[Samsung Galaxy S 5 Unified Development] pascua28:
Nice [MENTION=4122877]curiousrom[/MENTION], I didn't know I can find you here. How much sot do you get with this rom on a typical usage?
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 LineageOS 16.0 SOT - Screen On Time?

Hello sir, long time no see a post of yours. I guess we hang in different forum neighborhoods. Do you have an S5 too?

Everything is relative & especially SOT (Screen On Time). ;)

Im pretty sure your typical is not the same as mine.

Screen on is usually the biggest consumer of battery life & just a few % brighter or darker can make a big difference.

Naturally if for a given period you used the phone mostly outdoor in daytime the brightness power usage will be much higher than indoor and/or @ night for example.

Also if you use apps consuming a lot of power then that's less left for the screen. Same for wifi vs. data, signal quality, location or not, etc, etc.

Obviously the wear & tear of the battery is a big variable too.

You can see in the attachments with 10% battery left 5h28, 7% left 5h40 & 6% left 6h13 of SOT on S5 SM-G900M running haggertk's klte Unofficial LineageOS 16.0 build 2019-02-09 + Open GApps Pico + Magisk without a custom kernel or any other system modifications.

And it's with the old 2015 OEM battery that came with the phone as so far I can only find cosmetically perfect fake batteries in Costa Rica with a weight of 40~40.2 grams while the original Samsung for S5 weight is 45~45.2 grams.

That's with, as posted above, the tips described in Remove Animations UI Speedup Test - Taming Google & Apps including using the Dark mode Style.

***

I am doing a super clean install (w/ Format Data) @ the present & restoring the huge Google Backup takes for ever. Will redo many tests after it's up & running & checking if restoring other partial data backups made with other apps & adb are required.

I expect better battery life w/ the most recent official LineageOS 16.0 for S5 as I saw several merged patches related to memory, power management & other stuff in the last couple of weeks.

***
[Samsung Galaxy S 5 Unified Development] pascua28:
Yeah. I recently got a used Samsung S5 and wanted to get my hands dirty on it. I was just browsing some threads for roms and I see that support for this device is very much alive. I just didn't like that they merged CAF into the kernel.

I'm gonna try LOS later and see.
[Samsung Galaxy S 5 Unified Development] wdfitzpat007:
SM-G900V No-service update

On my unlocked bootloader CID15 SM-G900V I have had nothing but problems, likely because I had been doing dirty installs every install after my rooted-marshmellow install.

On doing a clean install of the offical 3/16/19 I have no service from the get-go unlike when I was doing the dirty installs.

Clean install procedure: factory reset, cleare devlick+cache, install ROM + Pico opengapps

After successfully flashing the latest baseband and modem, I still have no service. [MENTION=4122877]curiousrom[/MENTION] [MENTION=522292]Haggar[/MENTION]tk what is there left for me to try?

While I have a restorepoint of an older buggy linage os 16, I really do not want to be left behind while the updates keep fixing more and more bugs.

LOS 3/16/19

TWRP 3.2.3

Odin3 3.13

haggartk basband+modem for sm-g900V 2018 pack

bootloader: unlocked 4.4.3

CID: 15

opengapps: pico 3/16/19
[Samsung Galaxy S 5 Unified Development] curiousrom:
SM-G900V No Service - TWRP Factory Reset, Clean Install & Format Data

"...Clean install procedure: factory reset..." - A TWRP > Wipe > Factory Reset > only wipes Data (Apps + their data & the System's data. Does not include the internal sdcard.) + Cache + Dalvik / Art cache.

View attachment 4725001

A clean install is a TWRP > Wipe > Advanced wipe > Data + System + Cache + Dalvik / Art cache.

View attachment 4725007

A super clean install in my book is a Format Data + Advanced wipe > System + Cache + Dalvik / Art cache as described in S5 LineageOS Super Clean Install which includes Format Data instead of just wipe.

Note that Format Data destroys all the content of the internal sdcard as it rebuilds the entire Data partition's file system as explained in that post. So backup your data before doing that.

View attachment 4725008 View attachment 4725010

That's what I did on my S5 G900M a couple of hours ago. Will post later about it & backup strategy before doing it.

"...haggartk basband+modem for sm-g900V 2018 pack" - Baseband, Modem & Radio are just different names for the exact same thing. Haggertk's SM-G900V package includes only a DQL1 modem.bin (2g & 3G) & NON_HLOS.bin (LTE modem) & does not include the bootloader (named aboot in the S5) so people don't end up with a SM-G900V locked bootloader as described here: S5 Odin Flashable Modem & Bootloader.

***

About your No Service problem:

1- Try a cold boot: power off, wait 5 seconds & power on.

2- Check your network provider's recommended APN settings then double check > Settings > Network & internet > Mobile network > expand Advanced > scroll all the way down to > Access Point Names (APN).

3- "...I have a restore point of an older buggy linage os 16..." - If you had service & network access when you did that backup you could restore only the EFS partition & it may solve your No Service problem. See this post for detailed explanation & screenshots: No Network, No IMEI, No SIM & EFS Partition Restore Fix.

4- If you don't have any TWRP backup that includes an EFS Partition backup made when you had network access & service then you may have to install an especially modified Samsung firmware which will not lock your S5 SM-G900V bootloader & make a EFS Partition backup while running it. See [ROM][VZW_Stock _QL1_Deodexed][DEV aboot Magisk Rooted][Locked Bootloader Safestrap].

Please report back if you fix your problem or not & good luck! :good:

***

Edit: [MENTION=9763966]wdfitzpat007[/MENTION] - I just added some TWRP screenshots to illustrate the differences.
[Samsung Galaxy S 5 Unified Development] j1gga84:
A super clean wipe is flashing a stock ROM and starting from the scratch.

This eliminated all errors in the past for me ;)

Regards

Sent from my SM-G960F with Tapatalk