yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] mpower25:
Well it has HDR, so I'd say it equals stock and is better than CM13.
[Samsung Galaxy S 5 Unified Development] phalkon30:
The answer is literally quoted on the previous page.

Flash the boot image for your device that haggertk provided, or wait for the next "nightly" that will include the fix
[Samsung Galaxy S 5 Unified Development] zrockcool:
Thanks for the tip! Will wait then for the next nightly.
[Samsung Galaxy S 5 Unified Development] glostermeteor:
I have found this not to be the case unfortunately. I have found the picture quality to not be as good as Stock, even with HDR and an app like Snap Camera HDR.

The problem I have found is that the camera focussing time is far slower than stock, so often the pictures look a little blurred (unless I am taking a picture of a non-moving object like a tree). Not sure if this is down to different APIs or just different camera software but I have switched back to stock for now as I felt I was losing the main thing that makes me love the S5......the camera quality.
[Samsung Galaxy S 5 Unified Development] mpower25:
Well, my stock rom often took blurred pictures too...
[Samsung Galaxy S 5 Unified Development] s3nr1:
Not sure about the S5, but on my previous phones non stock roms like cm, aokp don't use the same camera drivers as stock as they're not open source, they're more generic and hacky that's why stock will always have better camera quality and the main reason I stay away from non stock. I of course want Nougat...
[Samsung Galaxy S 5 Unified Development] Kevinkuensken:
Hello,

i have flash the Nightly all work good but the Voice Mail on WhatsApp are very very quiet.Anyone else have this Problem
[Samsung Galaxy S 5 Unified Development] jiml8:
From the link:

"Given the EXPERIMENTAL nature of this process, we are going to remove this option in two months time."

Does this mean that we must update from CM13 to LOS14.1 within the next two months if we wish to do it without a clean install?
[Samsung Galaxy S 5 Unified Development] htb2050:
Yes.
[Samsung Galaxy S 5 Unified Development] RemusW:
Substratum working.

I am happy to say that Substratum is working perfectly in Legacy mode on this rom for me and am using the Swift Black for 7.1.1 theme without any issues at all. No boot looping and the only FC's i have seen were while the theme was being applied and nothing since.

After reading through a few dozen pages of the XDA substratum theme engine thread it seems not all themes are working on this rom but have not been able yet to find a reason why.

One of the theme developers reports that some themes are working and some are not, but do not use 'Accents or Cards'.

Navigate, and Statusbars Beta, are working... And I think Domination was working with it...

It maybe that not all themes have been made compatible with Nougat 7.1.1 yet and with a little bit more time more themes will become compatible.

Try looking for themes that say they have been updated for 7.1.1 as those are likely to have a better chance of working right.

It's still relatively early days yet for themes on Nougat but we are starting to see progress on that front and in time we should also get LOS theme engine to expand our options further.

i hope that this helps people looking for themes
[Samsung Galaxy S 5 Unified Development] gentano:
Of course not. You can download the Experimental now and flash it x months/years later, to avoid the clean install. 'Removing the option' only means the Experimental download will be removed from the servers.
[Samsung Galaxy S 5 Unified Development] lemurm1n:
https://xdaforums.com/galaxy-s5/general/galaxy-s5-low-audio-notes-fix-t3542279
[Samsung Galaxy S 5 Unified Development] singhpunjab:
Help me Pls

HI!!:o:o

Help me please

when I finished installing the rom and the gapps all apps starts to crash and my phone swicth off

after i tryed to install only the rom and it worked fine i need the gapps i dont what to do

Sorry for my english

Thanks:cowboy::cowboy:

And nice rom
[Samsung Galaxy S 5 Unified Development] Bubka3:
Get the fixed boot.IMG from 2-3 pgs before and flash it.
[Samsung Galaxy S 5 Unified Development] snapper87:
What is the recommended modem version for LOS official on klte?
[Samsung Galaxy S 5 Unified Development] Young Gunna:
Modem I version does not matter. Basically with modem version you choose the one that gives you the best reception in your area.

It can be flashed independently of anything else.
[Samsung Galaxy S 5 Unified Development] snapper87:
thanks! Good, since Samsung is still updating klte monthly, I was wondering if this has also effects on modem, not just system rom.
[Samsung Galaxy S 5 Unified Development] RockStaR_GER:
hey guys, i cannot use my slowmotion/ 240fps function on my s5. it says my resolution should be lower, but i also doesnt work at 720p which is the lowest resolution that i can pick. Am i doing something wrong or is there a fix?
[Samsung Galaxy S 5 Unified Development] haggertk:
Just an FYI, the klte-family is building now and klte looks to be up for download. This run should officially resolve the "gapps upgrade makes my phone curl up in a corner and die" problem - you should not need the updated boot image.
[Samsung Galaxy S 5 Unified Development] jiml8:
Yes, I did download it after posting my question.

My understanding is that this is necessary as a workaround to deal with the change from CM signing keys to LOS signing keys. But it occurs to me (and I don't know the truth of this) that possibly the production versions of LOS must explicitly support the possibility of this experimental version for the transition, and that support might be removed from LOS after some point (maybe after two months).

Should this be true, then that would suggest a rather specific set of choices to move from CM to LOS without a clean flash.

I have been thinking about picking up another S5 just to play with; I am a developer after all, and I would like to hack on this thing as I have the time (which I really don't have right now). But at this time, I am only thinking about it, and my S5 is my daily driver, and a critical component of my business operations. So I work on it only reluctantly and when I have a reasonable assurance of not encountering problems.

For that reason, I watch LOS with great interest while I remain on CM13. And when I make the move, I can't afford to have problems...and I really, really, really don't want to clean flash.

Now, I did clean flash, of course, from TW to CM, but I only did that when I just couldn't take TW any more. Making the move was the best thing I've ever done with my android, but I studied it for a solid year before I did it.
[Samsung Galaxy S 5 Unified Development] haggertk:
As a developer, it's always possible to roll your own migration build:

http://wiki.lineageos.org/signing_builds.html#changing-keys
[Samsung Galaxy S 5 Unified Development] jiml8:
That doesn't look difficult. Repopick looks like a tool that has been forked into many variants. I suppose the right one comes with the build environment?

...definitely would want a spare S5 just for hacking if I decided to do this... :P
[Samsung Galaxy S 5 Unified Development] Bubka3:
Just flashed newest build with boeffla kernel. Seems very stable. Good work!
[Samsung Galaxy S 5 Unified Development] Blackburn119:
No need to upgrade to newest flagship with SD 821 or SD 835 while we got this Nougat ROM running smoothly nightly after nightly
[Samsung Galaxy S 5 Unified Development] GioxSword:
https://review.lineageos.org/#/c/160194

This was canceling my incoming calls, thank you thank you thank you
[Samsung Galaxy S 5 Unified Development] ekulnitsua:
[MENTION=2693412]haggertk[/MENTION] - I'm getting an error - "unable to flash incompatible data" with the current nightly and your twrp.

Is this because of the boot image fix I flashed earlier in the week, or is it a partitioning problem, or both.... Or none at all ?

Ignorance is bliss....

Any tips for avoiding a full wipe?

Thanks,

L
[Samsung Galaxy S 5 Unified Development] Young Gunna:
I just tried as well on my kltvzw. Ends in error 7 and says can't install over incompatible data. Please try factory wipe. I also used the boot patch for Gapps freezing.
[Samsung Galaxy S 5 Unified Development] haggertk:
What build did you flash the replacement boot image on top of? That message indicates different signing keys which normally means that you were on an unofficial or something like an old CM nightly. Flashing a replacement boot image does not affect the signing keys.
[Samsung Galaxy S 5 Unified Development] Young Gunna:
[MENTION=2693412]haggertk[/MENTION] I'm running the 31 Jan official nightly

See screenshot. Only difference is the updated boot from your AFH and open gapps
[Samsung Galaxy S 5 Unified Development] ekulnitsua:
[/COLOR]

I'm on the 31st official, non experimental,and have been since the beginning. Worth trying the experimental?
[Samsung Galaxy S 5 Unified Development] haggertk:
This is, um, interesting. I'd suggest extracting the boot.img from the 31 Jan and flashing that to the boot partition, rebooting back into recovery, and re-try flashing the 7 Feb nightly.
[Samsung Galaxy S 5 Unified Development] Young Gunna:
Roger that! i will give it a shot later (cant have my phone at work)
[Samsung Galaxy S 5 Unified Development] Panzerknakker:
I'm on klteduos.

Was on 20170131 nightly + boot.img dated 04.02.17

Dirty flashed 20170207 nightly.

Everything fine.
[Samsung Galaxy S 5 Unified Development] :
Is it stable? What doesn't work?

Thx :)
[Samsung Galaxy S 5 Unified Development] ekulnitsua:
Tried - no dice, same error. It's not imperative to get on the new nightly yet (though losing the non seandroid enforcing message would be cool), your boot fix has been grand, so there's no desperate hurry on this one.
[Samsung Galaxy S 5 Unified Development] haggertk:
I looked at the flashable images and the only thing that emits the message in question is otasigcheck.sh. Somehow a key on some file for dorked. It's really weird for it to happen, and a migration build should fix it, but the boot images in the posted migration builds are broken. I'm going to ask that new migration builds get queued.
[Samsung Galaxy S 5 Unified Development] pacaldi:
Ciao,

yes it seem to be stable, i'm coming from:

lineage-14.1-20170125

lineage-14.1-20170131

lineage-14.1-20170207

dirty flash!

Google app 0119 and auto update disabled till lineage-14.1-20170131 when i enable auto update but this caused freeze and reboot, fortunately i can uninstall the Google Play Service update and the phone come back to work fine. Today another dirty flash with this new release and even enable the auto update, now my phone is set to:

lineage-14.1-20170207

Google Play Service 10.2.98

addonsu-arm

All seem to be still stable even after manual reboot.

Next and final step it's to wipe all and reinstall again with last version of GAPPS.

Stay tuned for more rock and roll :cool:
[Samsung Galaxy S 5 Unified Development] nictabor:
I can confirm that I have KLTEVZW, I had 1/31/2017 official build, supplemental boot image, and was able to dirty flash the 2/7/2017 nightly.

Everything works great!

On a side note. With the boot fix in place, should the updater work now?
[Samsung Galaxy S 5 Unified Development] haggertk:
I still need to do some work for the updater to work. It requires both the ROM and the recovery to be looking at the same thing for /misc. Official TWRP releases for our device don't mount a misc and I need to find a good partition to use that won't cause what just happened with the gapps fiasco.

It might be a couple weeks and anyone wanting to use it will have to update to a recovery image I recommend.
[Samsung Galaxy S 5 Unified Development] phalkon30:
Klteusc here, dirty flashed to 2-07 over 1-31 that had the updated boot, no issues.
[Samsung Galaxy S 5 Unified Development] Young Gunna:
[MENTION=2693412]haggertk[/MENTION] I saw your post about a key maybe being messed up on a file somewhere but wouldn't this make everyone have the same issue of "Can\'t install this package on top of incompatible data. Please try another package or run a factory reset" Looks like there's some successes and some failures. there's even another kltevzw that came from the same nightly and boot.img as me but was successful. Just curious and trying to learn
[Samsung Galaxy S 5 Unified Development] Rickmaster:
[MENTION=2693412]haggertk[/MENTION], thank you very much for your work!

On my klteduos I only the lineage-14.1-20170125-nightly-klteduos-signed get a LTE / data connection. With the 20170131-nightly and the 20170207-nightly the LTE / data connection does not work. I clean dalvik and cache an flash the rom with twpr.
[Samsung Galaxy S 5 Unified Development] Panzerknakker:
Here LTE works on all three nightlies above. (Using just first SIM presently).
[Samsung Galaxy S 5 Unified Development] Rickmaster:
[MENTION=8002612]Panzerknakker[/MENTION] only my first o2 SIM has data / LTE
[Samsung Galaxy S 5 Unified Development] Panzerknakker:
Yes, same o2 config than you, sorry can not test SIM2 at the moment.
[Samsung Galaxy S 5 Unified Development] raylogic:
Totally off topic!

SM-G900F

I'm in Warsaw for a week, get the O2 text when I landed telling me I have roaming unlimited data for £1.66 per day. So roaming switched on, phone selects Orange automatically but only phone calls working.

What gives?

Ta!

R.
[Samsung Galaxy S 5 Unified Development] Rickmaster:
[MENTION=8002612]Panzerknakker[/MENTION] how did you install the 0170131-nightly and the 20170207-nightly? I only clean dalvik and cache an flash the rom dirty with twpr.
[Samsung Galaxy S 5 Unified Development] KingKuno:
Where can I find the changelog of the new release?
[Samsung Galaxy S 5 Unified Development] htb2050:
Cmxlog.com
[Samsung Galaxy S 5 Unified Development] Malacant:
Currently running latest kltespr nightly and latest gapps stock version and everything is running wonderfully!

Two minor things I've noticed:

-SMS still not working over lte on the spr(no surprise I just use voice)

-tried to add Clock widget and it FC right away. But cLock widget worked. Not sure why it does that but it's not a big deal for me.

Will keep testing things out thanks so much!
[Samsung Galaxy S 5 Unified Development] 4ndr0x:
Can't install this package on top of incompatible data. Please try another package or run a factory reset

I'm on official CM 14.1.

First post says

Will you publish the information how to upgrade from to official releases in the first post?
[Samsung Galaxy S 5 Unified Development] Bubka3:
You must use the migration build first to go from cm official to lineage os official. The FAQ entry you quoted only applies to unofficial lineage os builds.
[Samsung Galaxy S 5 Unified Development] ekulnitsua:
[MENTION=2693412]haggertk[/MENTION] here's the log from twrp if it helps.
[Samsung Galaxy S 5 Unified Development] 4ndr0x:
Thank you. What is this migration build you mentioned and where can I download it? Also, what is this "Official SU Addon"? Do I need it for root access?
[Samsung Galaxy S 5 Unified Development] derAndroidler:
Do I still need to use older open gapps?
[Samsung Galaxy S 5 Unified Development] haggertk:
Not if you are running 7 Feb or later nightly.
[Samsung Galaxy S 5 Unified Development] haggertk:
Wow, scrolling through quickly, that doesn't look right at all. I need to take some real time after work to look at it.
[Samsung Galaxy S 5 Unified Development] omgbossis21:
The final list of errors are for out of storage space, do you have enough available?
[Samsung Galaxy S 5 Unified Development] cal002:
Out of interest I had a look at how the update via recovery process works:

1. app (e.g. Settings) uses android.os.RecoverySystem.installPackage() API

2. RecoverySystemService starts uncrypt via init (ctl.start property) and writes

the command via socket to uncrypt

3. uncrypt writes the command to /misc (/misc doesn't have a filesystem

and cannot be mounted, the command is written as a binary blob to the raw partition)

It used to work differently in the past, RecoverySystem wrote the

command to /cache/recovery/command. Maybe modifying

bootable/recovery/bootloader_message/bootloader_message.cpp

to use that as a fallback would be possible, but git log for RecoverySystemService

says "Since A/B devices may not have /cache partitions anymore..." (no idea

what A/B devices are).

It is interesting why gapps update wants to use this, does it try

to flash an update package to modify /system? (Your gerrit comments

indicated uncrypt was called).

BTW it should be easy to test writing some random

data to pad (atm I can't test myself) to see if that is a magic partition

that causes errors.
[Samsung Galaxy S 5 Unified Development] haggertk:
A/B devices are like Pixel and likely upcoming flagships that have two of each critical, non-userdata, partition so that updates can be installed and applications dexopted before rebooting. This allows allows for instantaneous (to the user) upgrades and fall-back on failed boot after upgrade. Interestingly, with this layout the ramdisk is part of /system, at least on Pixel.

There is a patch to allow the old method for writing the bootloader_message, but policy is that we are only going to use it if there is no partition that can be co-opted for /misc.

Even more curious is that it either only tries to do this on SOME devices or that only SOME devices go crazy after uncrypt is granted access to the partition marked as /misc. On my affected device, it was constant mmc resets until the system rebooted on its own (likely watchdog timer) or I forced it to reboot.
[Samsung Galaxy S 5 Unified Development] Bubka3:
See this post by the Lineage OS team for details.

Unlike cm, lineage does not ship with root/su. You will need to install that addon should you require root.
[Samsung Galaxy S 5 Unified Development] rodrigo.fac:
Hello.

How do I apply this new update?

How should I do to apply this new rom on the current one of the 01/31? Every time I try to pass the twrp the following error appears: error 7. I'm doing dirty flash.

Twrp 3.0.2-2. I am on 31/01. G900M.

Ty. :good:
[Samsung Galaxy S 5 Unified Development] systemcrash:
[MENTION=2693412]haggertk[/MENTION]

I'm okay with having (a) TWRP and Lineage share a path to send the update commands. Not having a partition is no deal breaker for me - it may seem hacky in comparison, but it works. This does not preclude any technical challenges I have not considered as a result of not having said /misc partition which seems more standard all round.

I contemplated the idea of changing the partition table on the G900F to have two partitions for /system so they would be compatible with the new A/B model that Pixel's use to aid in any upgrade problems (as are more likely with our open source ROMS). It's a space penalty (internal memory size minus 2x system partitions, where one system partition's space is stolen from userdata area), but would be a great help in the long-run for the S5s. Now with adoptable storage becoming more common, we could probably get away with this.

Has anyone actually done any work along these lines (I don't frequent other threads here on XDA so much for 'hacky crap' ;) )? I know some phones have modified partition tables available - would having an A/B for G900xx be worthwhile - let me reword that - would having A/B for the G900 series be drop in compatible with the update mechanism in Nougat? I don't mind hacking one together and testing, as long as I know specifics. I read the overview a while back for the A/B for Pixels, though the specifics are not yet clear.

I've likely not realised/remembered that the absence of /misc probably defeats such an effort. :/

We could commandeer the /modem partition. I mean, who the fack makes calls on their phones nowadays ;)

What about secure? That area that Samsung devices use(d) for secure storage which is erased anyway when the knox counter is incremented.

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

Edit: FOTA seems appealing to steal for alt system partition - those are supposed to be big enough to store a genuine samsung FOTA which is sometimes up to 1.5GB.

PS nicely done with the "this kernel is not seandroid enforcing" red text murdering. Only the yellow "set warranty bit: kernel" in yellow to go :D
[Samsung Galaxy S 5 Unified Development] Young Gunna:
Developers are working the issue. For now just be patient
[Samsung Galaxy S 5 Unified Development] haggertk:
What does the error actually say? The error 7 part is a generic assert error, the real thing will be above that.
[Samsung Galaxy S 5 Unified Development] philiptibbs:
I installed LOS 02-07 and opengapps 02-07 and so far so good. I even have Viper running and installed all my apps. Pray it works and doesn't freeze. Don't matter for me though. My LG V20 comes on the mail Tomorrow !!!!
[Samsung Galaxy S 5 Unified Development] Pabl088:
The apk of boeffla is really necesary? I don't wanna root just for that
[Samsung Galaxy S 5 Unified Development] haggertk:
There are hacky ways that someone could do it, whether that is by hijacking fota (that was my next target for misc) or by just slicing system in half using lvm or any other number of means, but it will never be merged into LineageOS.
[Samsung Galaxy S 5 Unified Development] donj001:
Good evening all. Long story short, I did a dirty flash of the 20170207 KLTE nightly over the 0131 nightly using TWRP and I got the ERROR 7 also. I only mention this because I don't typically dirty flash and just wanted to post. Thanks and really thanks for this ROM.
[Samsung Galaxy S 5 Unified Development] HulkSmashBurgers:
For a while now I've had a frequent annoyance of my power button activating the camera. I think it's due to my case causing frequent double clicks. I didn't see an option for it under the power button settings, so I didn't think there was a way to disable it. Turns out it's in the gestures settings. Wouldn't it make more sense to put the 'jump to camera' option in the power button settings menu, next to the 'long press for torch' option?
[Samsung Galaxy S 5 Unified Development] Bubka3:
OMG

I've been scratching my head over this for days. Thanks!
[Samsung Galaxy S 5 Unified Development] Young Gunna:
It's actually in multiple places to include the "buttons" menu under device settings
[Samsung Galaxy S 5 Unified Development] haggertk:
What is the actual error? It is above the error code.

Error code 7 just generically means assertion failure.
[Samsung Galaxy S 5 Unified Development] Young Gunna:
Oh yeah [MENTION=2693412]haggertk[/MENTION] I forgot that I could copy my logs from recovery of the error (see attached) looks like I have the same issue another guy did as well.
[Samsung Galaxy S 5 Unified Development] omgbossis21:
Your log is showing mismatched keys. You could dirty flash the experimental and then the latest.
[Samsung Galaxy S 5 Unified Development] donj001:
Updater process ended with ERROR: 7

Error installing zip file 'path'

Attached is the log
[Samsung Galaxy S 5 Unified Development] HulkSmashBurgers:
Not for me. I have 'long press for torch' in its place. How does that happen?
[Samsung Galaxy S 5 Unified Development] Panzerknakker:
Yes, same like you.

Unofficial -> Experimental -> Official nightlies. Always dirty with cache/dalvik wipe.
[Samsung Galaxy S 5 Unified Development] rodrigo.fac:
I downloaded the file 4 times I tried with the four.

It does not update through the internal updater or another third-party app (lineage downloader premium).

Every time I try to update manually it starts reading the file but it has this error: updater process ended whit error 7. Error installing zip file. Only show this.

Buuut, above show this: Can't install this package on top incompatible data. Try another package or run a factory reset.

Ty
[Samsung Galaxy S 5 Unified Development] GioxSword:
I can also confirm that substratum legacy themes "swift black" and "swift dark" work with the latest version on lineageOS :)
[Samsung Galaxy S 5 Unified Development] Blackburn119:
What about Google pixel theme does it work?
[Samsung Galaxy S 5 Unified Development] dotgeo:
How to hide brightness control in notification bar?

I cant find the option...