yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] phenix23:
Yes thats exactly my configuration. Managed to set up the whole phone incl downloading and installing several apps. Now after a reboot it starts freezing again...

How to stop play services from auto updating?
[Samsung Galaxy S 5 Unified Development] voak:
Experimental version says "Service is not available"
[Samsung Galaxy S 5 Unified Development] dollardollar:
Does this appear on experimental builds or nightly
[Samsung Galaxy S 5 Unified Development] firefds:
I've been using the latest gapps with the latest google service ever since it came out.

I havent experienced any of the issues you guys are reporting.

I can say that I have turned off a few google sync options.

Maybe you guys can try turning them off on a stable version and then flash the latest one and see if the device hangs again.

(Attached a screen shot of the options I turned off, the ones you don't see are on)
[Samsung Galaxy S 5 Unified Development] nictabor:
I'm getting that too... I was able to download the nightly though.
[Samsung Galaxy S 5 Unified Development] pacaldi:
it's a good idea honey :cool:

You have these files istalled?

ROM: lineage-14.1-20170125-nightly-klte-signed

GAPPS: open gapps arm 7.1 2017 01 25
[Samsung Galaxy S 5 Unified Development] Young Gunna:
The experimental build is only to be used to go from unofficial lineage which is unsigned to the official builds which are signed. This is only to be used so you don't have to wipe all your apps. So basically you flash the experimental first then the nightly if you don't want to lose all your apps. If you don't mind and honestly I prefer it as it's cleaner you don't use the experimental you do a complete wipe and just go straight to the nightly.

---------- Post added at 04:23 PM ---------- Previous post was at 04:21 PM ----------

@dollardollar

On the lineage blog they posted the exact update instructions I can't post the like (don't have the post count yet lol)
[Samsung Galaxy S 5 Unified Development] soren625:
So are folks still having the Google Play/Freezing issue with the new official nightly?
[Samsung Galaxy S 5 Unified Development] limeaide:
For those of us suffering with the play store crash you can update everything but the Google app. When you update it, Google services also updates. Also turn off auto updates so you don't accidently update it. Do not do mass updates click each one and update it.

This is beyond annoying especially when you need to use the phone and it just locks up. Happened to me during a important call and the other party was a total ****er.
[Samsung Galaxy S 5 Unified Development] dollardollar:
So u mean say, the "cm to lineage migration build" text all over the screen doesn't appear on nightly builds :fingers-crossed:
[Samsung Galaxy S 5 Unified Development] firefds:
Im still on latest unofficial lineage as I need root.

Gapps are latest gapps mini
[Samsung Galaxy S 5 Unified Development] Young Gunna:
lineageos dot org/Update-and-Build-Prep/

Change the dot to an actual. to go to the explanation blog from lineage. Also attached a screen shot
[Samsung Galaxy S 5 Unified Development] shjeanpy:
Help me with the link for the latest Bootloader and Modem files for SM-G900F thanks in advance
[Samsung Galaxy S 5 Unified Development] Blackburn119:
Official build is so complicated, if haggertk continue to release unofficial version I would rather stick with it forever.
[Samsung Galaxy S 5 Unified Development] willes74:
https://www.androidfilehost.com/?w=files&flid=18025

Here you are...
[Samsung Galaxy S 5 Unified Development] phenix23:
Solution Play Service Issue - Another Try

All right guys, another try to run the offical Nightly from today.

Device: S500F (ktle)

ROM: lineage-14.1-20170125-nightly-klte-signed

Gapps: open_gapps-arm-7.1-pico-20170119 (Will give you GPS Version 10.0.84)

Recovery: TWRP 3.0.0.0

I managed to install apps and reboot my mobile reliable. I also installed some Google apps like Gboard and calender (but NOT Google Search app!). Didnt experience any freezes so far. Would be nice if someone could verify the following procedure.

1. Remove SIM-card from phone

2. Start TWRP

3. Wipe dalvik, data, cache

4. Install ROM and gapps + boot to system

5. DO NOT set up WiFi skip all the following stuff at your will

6. Enter settings to "Apps" and chose Google Play Services

7. Chose Data Usage or whatever it is in English

8. Disable "Background data" (The point is to prevent GPS downloading the updates) so it looks like on the screenshot attached

9. Now set up WiFi

10. enter Play Store and disable auto app updates (so apps wont do some crazy update stuff)

11. Turn Phone off insert SIM reboot

12. Hope

dont know if you can see the pic, you can also that a look into my gallery:

https://xdaforums.com/picture.php?albumid=13931&pictureid=55023
[Samsung Galaxy S 5 Unified Development] pacaldi:
Ok thanks, i'll try your guideline, stay tuned!
[Samsung Galaxy S 5 Unified Development] shjeanpy:
Thanks for your help, I have for BL 29 December 2016 and CP is 25 October 2016 is it the latest one? Is it right?
[Samsung Galaxy S 5 Unified Development] ItsMeShouko:
I flashed latest lineageos and latest gapps too and it caused freeze and reboots but then I flashed open_gapps-arm-7.1-pico-20170109 and everthing works good!

Bug/Missing feature:

I am also missing gestures tab in settings, when I searched for gestures in settings, it only gave me option to use camera by tapping power button two times...
[Samsung Galaxy S 5 Unified Development] nictabor:
KLTEVZW Experimental seems to be available now... I just downloaded it.
[Samsung Galaxy S 5 Unified Development] alyousmy:
Is IR working for anyone? I am trying to use some remote apps but they are not working on my G900F with the latest lineage os nightly. I don't see my led flashing when I press the buttons in remote apps.
[Samsung Galaxy S 5 Unified Development] RemusW:
Flashed the experimental build, cleaned caches, rebooted then flashed the 25th dated nightly, cleaned caches and rebooted.

Everything works exactly as it should as far as i can tell so far. the play store working and used it to update some of my installed apps.

the bug i reported with settings crashing when selecting other sounds has been fixed.

Does anyone know if the built in call/sms message blocker that was in CM13 will at any stage be ported to lineage ?

more than happy to wait for that feature and hope that it will get ported at some point.

thank you everyone concerned with bringing this rom to us.
[Samsung Galaxy S 5 Unified Development] harise100:
Anymote works for me.

using official nightly.
[Samsung Galaxy S 5 Unified Development] papei:
I can't get that far even with the pico gapps. It hangs after the the first of second section of the set up, either where you set the time zone or where you log on to wifi. It reboots constantly. I did a clean flash, even tried reformatting the system. Nothing seems to work. Guess I'll have to wait another day or two.
[Samsung Galaxy S 5 Unified Development] square_eyes:
The Mrs and I have similar phones G900i AU/NZ and G900F UK. We are both in New Zealand. I loaded the same unofficial ROM on both our phones - G900F klte 29/12 (the G900i one would fail on hers).

I received bootloops here in NZ yesterday morning, followed by a factory reset and install then repeat within an hour. But somehow she has avoided them. So I don't think it's locale, but perhaps some sort of level lower than OS - model or serial perhaps.
[Samsung Galaxy S 5 Unified Development] raylogic:
Same question here
[Samsung Galaxy S 5 Unified Development] willes74:
It should be the last Bootloader and Modem for G900f klte
[Samsung Galaxy S 5 Unified Development] Genmaizen:
Dirty flashed over last unofficial klte lineageos via twrp: experimental - reboot - official - reboot. Worked. Without additional GAPPS installation. Nice :)
[Samsung Galaxy S 5 Unified Development] GioxSword:
What "display size" setting do you guys use

I feel that normal is just too large
[Samsung Galaxy S 5 Unified Development] derAndroidler:
Where is the root add on?

And will it be possible to uninstall the root add on?
[Samsung Galaxy S 5 Unified Development] raylogic:
Same question
[Samsung Galaxy S 5 Unified Development] Apathetik:
I have mine set in developer options to 432 DPI (screen is 432ppi so figured it would look nice). But I have really good eyesight. This might be too small for a lot of people. lol

Official root should be out within the next few days. Zifnab (LOS team member) confirmed this on the reddit the other day (can't find the link atm, sorry.) That is however, assuming everything goes according to schedule. Life is rarely so polite. :P

As far as uninstalling root. If I'm not mistaken, that's pretty much as simple as deleting the su binary from the system (someone feel free to correct me if this is inaccurate.)
[Samsung Galaxy S 5 Unified Development] raylogic:
Well blow me.

Lost Root means lost A.R.I.S.E (well at least Dolby Atmos) for me..

Roll on Root, long live the King! God save the Queen!

R.
[Samsung Galaxy S 5 Unified Development] willes74:
Deleted
[Samsung Galaxy S 5 Unified Development] glostermeteor:
Hi Guys, I have a rather stupid question to ask, how do I know which version of S5 nightlys to download? I have a UK S5 with Model Number SM-G900F. I bought it originally on a UK Vodafone contract but it is unlocked and can be used on any network, and so I am getting a little confused between klte and kltedv (Which says Vodafone). Can I use either or will only 1 work with my device?
[Samsung Galaxy S 5 Unified Development] Apathetik:
What carrier you're on doesn't matter afaik. Only the model of the phone itself. If you go into Settings > About Phone. You should see an entry "Device model". That model correlates to a "code name" (for lack of a better term, not sure what their actual name is). Such as 'klte', 'kltevzw', etc.

If I'm not mistaken, the G900F is the international variant and uses the 'klte' version of the ROM. But please confirm this with another source. I'm not 100% sure on that, as I don't have that version of the phone.

Edit: Just double checked, from the OP it lists the SM-G900F as specifically using the klte version.
[Samsung Galaxy S 5 Unified Development] square_eyes:
Correct I have G900F also from UK (not relevant though I think) and I use klte builds.
[Samsung Galaxy S 5 Unified Development] Brigham999:
I did the same except I reflashed GAPPS (Nano) at the same time as the signed nightly. Everything working well.:good:

---------- Post added at 03:31 AM ---------- Previous post was at 03:24 AM ----------

As others have stated, you have an SM-G900F which is the International variant of the S5 - also known as klte. I have the exact same phone and running the latest LineageOS 14.1 signed nightly perfectly.

It sounds like you may be new to all this (sorry, if I'm wrong! :o) so I would advise that you read carefully the steps to getting your phone running LineageOS
[Samsung Galaxy S 5 Unified Development] square_eyes:
So... now I'm back on CM13, with hours of wasted time recovering... what's the next step. Do we wait for Lineage OS to address the Gapps bootloop? Or is it not an OS thing? I don't want to risk it again. I do Nandroid backups, but the nature of this bug is that it's a ticking time bomb. Inevitably you are going to loose photos and messages etc.
[Samsung Galaxy S 5 Unified Development] Sdc5364:
Weird thing happened if anyone can give advice. I am running the latest from haggertk on Ktlevzw. Got it from the link he provided however there is no 20170125 build uploaded but my phone says that there is a an upgrade through lineages updater. Do I update or wait for haggertk to upload
[Samsung Galaxy S 5 Unified Development] rhyzan:
Yep. Anything in the LineageOS Updater is official. Grab that one.

You can also check the lineage builds for your device here: https://download.lineageos.org/kltevzw
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
I'm running official Lineage OS on my kltekor with mini dynamic Gapps without any issue
[Samsung Galaxy S 5 Unified Development] Apathetik:
The OP has not been updated to reflect the changes yet.

The new builds you should be using for LineageOS for the kltevzw variant can be found here: https://download.lineageos.org/kltevzw

However, before you just go grab those and start flashing. Make sure you read This and make sure you understand it. The process for updating from unofficial to official is different. But after that, we'll be back to just straight dirty flashing new official builds. Or using OTA.

Lastly, although it is not explicitly stated anywhere. OTA updates from unofficial are NOT supported. I'm not sure what kind of madness it may cause. But it's best to just flash manually until you're on official.

---------- Post added at 10:16 PM ---------- Previous post was at 10:14 PM ----------

Wish this was the case. But OTA updater is NOT supported for going from cm / unofficial LineageOS to Official LineageOS. Once you're on an Official Build, the OTA updater will work again. But not before that.
[Samsung Galaxy S 5 Unified Development] rhyzan:
What GApps did you use? So far OpenGApps Nano and Mini worked fine... I'm on micro and I'm yet to upgrade the newest micro. If you haven't tried those flavors, I suggest you do so.

You can also try other GApps like this one: https://download.dirtyunicorns.com/gapps/Dynamic/

---------- Post added at 12:24 ---------- Previous post was at 12:18 ----------

Huh? If you're on haggertk's lineage you can dirty flash to the official build, on the site or using the updater. Haggertk mentioned that a few times here. I'm downloading the 25th build via the OTA right now.
[Samsung Galaxy S 5 Unified Development] Apathetik:
I think at this point people have narrowed down the culprit to an update to the Google Play services. I think you said you're on the klte version right? (pretty sure I saw you state this a few post back. Too lazy atm to go check :P). If that's the case, it seems OpenGApps prior to 01-19 work fine as long as you don't let the Play Store update the Google App. I only do manual updates anyway so it's not a big deal for me. There's a post over on the LOS reddit about this on the klte variant >Link< first reply has a solution in case it updates somehow and sticks you into a bootloop.

---------- Post added at 10:34 PM ---------- Previous post was at 10:29 PM ----------

Pretty sure this isn't the case because of how they're going about changing the official builds. Apparently due to the changes they're making to now signing with private keys (and potentially other things). Flashing straight to nightly builds from CM or Unofficial LineageOS is not supported. Which is why they'll be supporting experimental migration builds for two months. With the new build type (experimental). That afaik was not previously used. I can understand how this would cause problems trying to update via OTA from older versions. They're most likely setup to check for new 'Nightly' builds. And if you try to flash straight to one of those. It will probably wreck stuff. lol
[Samsung Galaxy S 5 Unified Development] rhyzan:
Dude. Again. Dirty flashing from unofficial Lineage (ie. Haggertk) to Official lineage *should* pose no problems. If it doesn't, dirty flashing from experimental build to official build wouldn't work since it also runs on experimental/userdebug keys and haggertk would notify us ahead of time not to update the via OTA updater. Only users using CM or CM-based rom will break their apps and app data if they dirty flashed the official one without flashing the experimental build first.
[Samsung Galaxy S 5 Unified Development] Apathetik:
I thought that they were building ALL LineageOS official builds with their own private keys, including the experimental builds. But I wanted to checked, just to be sure before correcting you. And they are. Both experimental, and nightly builds are signed with the same private keys. I can post a screenshot of verified fingerprints if you'd like, but they aren't hard to check yourself (good habit to get into anyway, if you're paranoid like me. :P)

Also, a post from LOS team member on the reddit >Here< verifying that unofficial lineage builds DO NOT have OTA support.

Lastly, I'm not trying to be rude. And hope I didn't come off as being such. I'm just trying to prevent incorrect information from spreading.
[Samsung Galaxy S 5 Unified Development] Arjun KalyanRam:
I did a clean install of the official lineage on KLTEDV ..And flashed the stock gapps.Zip it freezes at startup and reboots then tried with nano the same then tried with Pico ! The same ..But boots good while not flashing gapps !!

I downloaded 25012017 zip of all gapps mentioned above ..So as u guys said will 19012017 will work ?? Even the stock gapps ???
[Samsung Galaxy S 5 Unified Development] fitittome:
A redit post says: Until a solution is found flash 0119 version of OpenGApps and delete the data/app/com.google.android.gms-1.apk folder from TWRP if it updates.
[Samsung Galaxy S 5 Unified Development] izzyfanto:
So I use to root and mess around with the OG Moto Droid, the one with the physical keyboard. Still have it in a box somewhere with SteelDroid ROM on it. Fun memories. Left for iPhone in 2009 (Android was pretty buggy and sluggish back then).....but finally got sick of Apple's BS a couple months ago and now I'm back on team Android. I plan on buying a nice Android this year, but in the meantime, a friend gave me their old G900V kltevzw. Cannot be happier. Woke up at 9AM, 1130PM now, sitting at 63% battery! Fantastic for an old phone with an old battery. This thing does everything I need it to do! Really like the gestures to wake the screen. And the AMOLED screen. And SDcard storage. Very thankful for communities like this that extend the life of these devices.

Running TWRP 3.0.0.0 - Unofficial 20170119 - picoOGapps 20170118. Zero problems, completely stable.

I've tried not posting, and just doing research, but I still have these questions after combing through everything:

1. If everything is working for me on unofficial 19, why update to official while the root package isn't out? Are the benefits to going official?

2. Same thing for TWRP? I've noticed people saying there are issues with higher versions.

3. What is Dirty Unicorn's Dynamic GApps opposed to OGapps?

4. I flashed PB1 during the rooting process instructions. Everything works, but I couldn't figure out what PB1 was. What is it?

5. I hear the terms Baseband and Modem being tossed around. What are these? Seems a person cannot corrupt these and have to flash to stock to get correct ones?

Not sure if this is kosher to post this here, but thought I say I enabled Android's NavBar by editing the build.prop and inserting this:

qemu.hw.mainkeys = 0

Restart, and boom. Pretty sweet when used in conjunction with Lineage's button remappings . . . despise Samsung's back/recent positions!

On a side note, anyone every have issues with the screen going pixelated, or screen staying lit but unresponsive? It's not the software, because it's persisted through stock, stock rooted, CM14, crDroid, and now Lineage.....and I found a couple threads about the display connector not being solid on these phones, and to press really hard on the back to try and re-seat it to the motherboard. That works most of the time. Sometimes I have to pull the battery and let it sit for a couple minutes. Any tips would be appreciated. Would rather not heat up the adhesive and peel the screen off the midframe like iFixit teardown shows.

Sorry for the long post and questions. I've been slowly reading through all the threads for this phone and familiarizing myself with rooting and flashing again. Cheers!
[Samsung Galaxy S 5 Unified Development] Apathetik:
1. If you're happy with how the unofficial build works. That's great. As far as upgrading to a newer version. There are several considerations. First and foremost is that the unofficial builds are technically no longer supported by the devs. So they won't be getting any further bug fixes, feature upgrades, or patches of any kind. That includes more recent android security patches. Upgrading to official means you get all of these. They're just getting up and running right now. So the build schedule is weekly for now. But that's still a lot in terms of rolling out bug fixes. Not to mention getting security patches much quicker compared to stock OS's. On top of the fact that once you get on official OTA (Over the Air) updates will once again be supported. No more manual flashing for updates (unless you want to, like me... but I'm weird).

As far as them moving away from baking root into the OS. This, along with a few other things. Have been done to try and make LineageOS a much more secure AOSP (Android Open Source Project) option. As well as the fact that not having root baked in, means SafetyNet isn't broken starting from the first boot of your freshly flashed phone. This means people who don't need root are already set up to use apps that require SafetyNet checks (Pokemon Go for example).

2. TWRP 3.0.0-0 is actually the version I use. It's an incredibly stable version of TWRP (I've not had a single issue, not even a hiccup out of it lol.) As well as still properly supporting Aroma installers which is a nice feature.

3. Haven't had any issues with OpenGApps, so I've not looked into alternatives. So not really in a position to answer this one. :(

4. PB1 is the last 3 characters of a Kernal / Rom version. It's basically just shorthand instead of typing out the whole thing.

5. If I'm not mistaken (I may very well be lol). Baseband refers to a group of things in the phone. Whereas Modem refers to a single thing. For more information about this, and your #4 question. I'd highly recommend Painiac's Essential Guide To Galaxy S5 this has a LOT of information that will help get you up to speed all in one place. For more in-depth stuff, a quick search on the forum (or even some of the links provided in his guide) are a good place to start.
[Samsung Galaxy S 5 Unified Development] Puddies:
Can I simply clear the cache and install 14.1 lineageos over cm 14.1? Or will I have to delete all data before upgrading from cm 14.1 to lineageos 14.1?
[Samsung Galaxy S 5 Unified Development] Apathetik:
They are pushing out experimental migration builds alongside the nightly builds. Those are specifically for migrating from CM or unofficial LineageOS builds to Official. You can read more about the change here.

Basically the steps are this for preserving data and migrating to official:

**Note, I Wipe Cache, and Dalvik between EVERY action (before and after every install). This is NOT necessary (probably a really good idea to do it before the initial CM to Experimental flash though). And quite frankly, probably overkill. But it really doesn't hurt anything afaik. As well as preventing any potential issues that can sometimes arise from not having cleared the caches properly before / after a flash.

Boot to custom recovery and make NAndroid Backup (always step 1)

Wipe Cache, and Dalvik. (not explicitly stated, but recommended)

Install Experimental LineageOS build for your device.

Wipe Cache, and Dalvik. (not explicitly stated, but recommended)

Reboot phone and let it boot all the way into the OS.

Power Off, then back into custom recovery.

Wipe Cache, and Dalvik. (not explicitly stated, but recommended)

Install Official Nightly LineageOS build for your device.

Wipe Cache, and Dalvik. (not explicitly stated, but recommended)

Power Off device, then boot into OS (first boot is gonna take a while)
[Samsung Galaxy S 5 Unified Development] haggertk:
Addon SU: https://download.lineageos.org/extras
[Samsung Galaxy S 5 Unified Development] Apathetik:
Yay! Thanks for the heads up [MENTION=2693412]haggertk[/MENTION]

Was kinda expecting that soon™. But not this soon. Very pleasant surprise. :D
[Samsung Galaxy S 5 Unified Development] airidosas252:
Still a no-go for Open Gapps. Bootloops for me after updating and that's all. Using 0121 build.

Dynamic Gapps were more promising.

Gonna test some more, though.
[Samsung Galaxy S 5 Unified Development] raylogic:
This worked for me perfectly.