yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] Apathetik:
I'm not sure which version you're on. But it's confirmed that Open Gapps 1-19 builds and prior work properly on ktle, and kltevzw (I'm on ktlevzw and 1-18 build and can confirm it works fine). There's a discussion on the reddit regarding this issue >link<. You do need to disable automatic updates from the google play store. And make sure that the Google App does not get updated. The first post in that thread has a workaround to get the phones booting again if the play store does update it automatically. Hopefully this helps get you up and running. :)
[Samsung Galaxy S 5 Unified Development] airidosas252:
I managed somehow to update google stuff successfully. Previously, when I flashed Open Gapps, Google Play Services were crashing all the time, even hanging up for no apparent reason. But now everything's fine.

I'm pretty sure something's wrong with permissions, but that's only my guess.
[Samsung Galaxy S 5 Unified Development] brianinmaine:
just noticed root is available:

https://download.lineageos.org/extras

I've not tried it yet...
[Samsung Galaxy S 5 Unified Development] rhyzan:
Ok pardon my ignorance. You're right. I just backtracked a few (actually 10+ pages) and you're right. Again, apologies.
[Samsung Galaxy S 5 Unified Development] Apathetik:
It's ok. And tbh, perfectly understandable, 400+ pages makes it really easy for stuff to get confusing and info to get missed. But like I said, I was just trying to make sure that the right information got posted (why my initial reply took so long, had to check and verify everything lol). So once again, sorry if I came off as being rude at all. Wasn't my intention. :D
[Samsung Galaxy S 5 Unified Development] TemhAAhmeT:
I just flashed root from the page you have posted.

All working fine :D
[Samsung Galaxy S 5 Unified Development] 4rz0:
Since one of my recently installs (currently the unofficial build from 21th), Titanium Backup stopped working, it can't seem to properly access my storage anymore.

Is that a know issue? Or a general issue at all?
[Samsung Galaxy S 5 Unified Development] brianinmaine:
yep all working fine on mine also! all up to date and all working fine.

All praise the devs!
[Samsung Galaxy S 5 Unified Development] TemhAAhmeT:
Except GApps issue if you may noticed at previous posts.
[Samsung Galaxy S 5 Unified Development] Puddies:
I tried it and it seems to work so far. But wifi does not work when su is installed. :/

So I removed it.
[Samsung Galaxy S 5 Unified Development] Apathetik:
Doesn't work at all? Both 2.4ghz, and 5ghz? I know there was a bug where 5ghz wouldn't work if the channel was set to higher than 48, and airplane mode was on. But this is the first I'm hearing of the su package breaking wifi completely. I'm running it on kltevzw with no problems.

Probably best to go ahead and grab a logcat and let the devs know.
[Samsung Galaxy S 5 Unified Development] mini01:
Not here. I'm on 5GHz channel 52 - wifi is working with su.
[Samsung Galaxy S 5 Unified Development] ItsMeShouko:
WiFi works on 25th Jan Lineage Official build + open_gapps-arm-7.1-pico-20170109 + root package

My Device: klte/kltecan (SM-G900W8)
[Samsung Galaxy S 5 Unified Development] Puddies:
Well, thank you guys. After reading your posts, I gave it a second try and reinstalled su and now wifi works.

I dont know why it was not working the first time, when I installed it earlier today.

I am very sorry for any confusions.
[Samsung Galaxy S 5 Unified Development] Apathetik:
Yeah, that's why I said it was a bug. Was pretty sure it got fixed. But I'm not on the same build as he's using. So wasn't sure if something weird might have happened and it was still a potential bug in his build. lol Like I said, I'm on the official kltevzw build, with su installed and no problems as well.
[Samsung Galaxy S 5 Unified Development] grey1213:
So I was using 24/12/16, and switched to the LOS official build, and my battery seems to be worse. Is it just me?
[Samsung Galaxy S 5 Unified Development] nictabor:
I actually did some research after this issue presented itself on my phone (kltevzw) when updating from 1-16 unofficial to experimental to official.

I was able to boot to recovery (twrp), delete system, reflash the same build of lineage official, and boot again with no issues. Then I simply uninstalled play services and disabled play store automatic updates.

At this point I was able to reinstall OGapps (used 1-09-17 per a previous post) and I'm stable. If any of you figure out how to resume updates without boot looping, please key me know.
[Samsung Galaxy S 5 Unified Development] Apathetik:
You can still update stuff with automatic updates turned off. You just have to do it manually. All of your apps, and the google apps like Calculator, Calendar, Photos, etc. Can all be updated manually without issue afaik. There's just one thing, shows up in the available updates as just the "Google" application. This is the one you DO NOT update.

If it does somehow update for you though. Or breaks again, there's a post in the reddit thread I linked originally that has a solution for getting the phone to stop bootlooping (requires deleting a folder from custom recovery).
[Samsung Galaxy S 5 Unified Development] I0tacle:
Can you give us a how-to?

Flash via TWRP?

Dirty or not?

Which sequence? LOS->root-> Gapps?
[Samsung Galaxy S 5 Unified Development] _linux_:
Hi all I installed lineage-14.1-20170125-nightly-klte-signed.zip to you does the fingerprint sensor?
[Samsung Galaxy S 5 Unified Development] TemhAAhmeT:
With Twrp. And clean install.

Flash LOS + Gapps 20170119 build. (But do not login wifi and disable google play auto updates after boot.)

Reboot

Root install

reboot.

Point is not loging in to wifi. So with mobile data connection, google play doesnt update. default setting is update only on wifi. So after first boot disable google play auto updates to avoid self update of google play services.
[Samsung Galaxy S 5 Unified Development] nictabor:
Just install via recovery. It's that simple. On reboot, root is enabled.
[Samsung Galaxy S 5 Unified Development] Apathetik:
Follow what [MENTION=5228319]TemhAAhmeT[/MENTION] posted about Gapps.

As far as installing the root package. It can be installed, or removed at any point once you've got Official build up and running. No need to wipe caches before or after.

Fingerprint sensor works just fine for me on kltevzw. I imagine it should also work properly on the klte build.
[Samsung Galaxy S 5 Unified Development] nictabor:
Thanks for that. I've actually updated everything already, including the Google app. Play is showing no updates. I'm tempted to re-enable updates, but don't want to do it all over again.
[Samsung Galaxy S 5 Unified Development] Apathetik:
lol, you're brave to update the Google app. :P Hope all stays stable. But yeah, for now I'd recommend leaving auto updates off anyway. Tbh, the time it takes to manually select apps to update is insignificant. Compared to the time it takes to wipe and reflash, or restore a NAndroid backup.
[Samsung Galaxy S 5 Unified Development] darksx:
Just made a clean flash,as usual in same order- official nightly+gapps(pico 19.01.)+su addon.Everything went perfect,i just updated manually latest google play services.Not single crash or something and forgot-device klte.
[Samsung Galaxy S 5 Unified Development] I0tacle:
Thx guys, that worked perfectly for me. :good:

Very strange - i didn't have any trouble with Gapps nor playstore issues. I did come over unofficial an migration build to nightly - perhaps thats the reason ?
[Samsung Galaxy S 5 Unified Development] ItsMeShouko:
Most of the times I noticed that many apps only works on WiFi and not on Mobile Data (I am using LTE). This happens on every 7.X rom... Any fixes? [MENTION=2693412]haggertk[/MENTION]
[Samsung Galaxy S 5 Unified Development] McMatias_2:
Sorry for the dumb question but with root package i should flash for my klte? It's su(arm) or su(x86)?

Sorry :eek:
[Samsung Galaxy S 5 Unified Development] voak:
Thanks. Do you use the SuperSU app? I dont mind not using it but i dont want # on the status bar showing. Do you know how to remove it?
[Samsung Galaxy S 5 Unified Development] shirioko:
ARM of course!
[Samsung Galaxy S 5 Unified Development] Arjun KalyanRam:
No support of VoLTE even in official build ! .
[Samsung Galaxy S 5 Unified Development] shirioko:
Of course not, unofficial builds work off the same code repository as the official ones. Only difference between the two are the build servers and the signature.
[Samsung Galaxy S 5 Unified Development] Arjun KalyanRam:
Flashing the superuser V2.79 zip file.. gives root and WiFi works flawlessly !!
[Samsung Galaxy S 5 Unified Development] dzincha:
Just flashed official 25.01 built on g900f. On previous flashes during flash it showed status bar and animation that is slowly filling and that process is ongoing. But now i got just empty bar for few minutes and done. Hopefully script finished succesfully. Is it also same for others or its just me? Recovery - TWRP.

Seems all good so far (apps/contacts/ settings migrated from unofficial 21.01 without any change - COOL).
[Samsung Galaxy S 5 Unified Development] Arjun KalyanRam:
So official also goes according to the bug fix list in the op !
[Samsung Galaxy S 5 Unified Development] ItsMeShouko:
arm
[Samsung Galaxy S 5 Unified Development] nictabor:
I installed the SU zip this morning via TWRP. It basically just restored the existing functionality to Lineage, where Root is controlled via the Developer menu. The # only shows when an app granted root privileges is running.
[Samsung Galaxy S 5 Unified Development] danduerden:
Hi all,

I'm currently running Philz Touch recovery. I've installed the official Lineage no probs on klte. My question is, would there be any benefit to changing to TWRP, also, if I did change, can you flash a new recovery without losing data etc...?
[Samsung Galaxy S 5 Unified Development] voak:
It works. Thanks.

---------- Post added at 03:03 PM ---------- Previous post was at 03:00 PM ----------

I use root for nova launcher so the # is persistent. superuser V2.79 zip file suggested by Arjun works and i did not lose wifi.
[Samsung Galaxy S 5 Unified Development] jdrch:
The smallest setting.
[Samsung Galaxy S 5 Unified Development] szokun:
Just disable signature verification.
[Samsung Galaxy S 5 Unified Development] rodrigo.fac:
Hello guys. I installed the 25th version with gapps aroma (for testing).

After the first boot I realized that everything was fine. However, I activated root in the developer options and realized that there was no app option.

I read on some topics that it was necessary to install the updated version of super su by recovery.

My question: Does it work to install super su after you have installed rom and gapps and made the app updates in the play store?
[Samsung Galaxy S 5 Unified Development] KazuDante:
is anyone facing and issue , when flashing gapps the phone steps in constant reboots but installing the rom without gapps it works normally. Can anyone help me out with this issue?
[Samsung Galaxy S 5 Unified Development] Malacant:
You have to flash an older version of gapps. For me the 20170109 pico worked perfectly on my kltespr
[Samsung Galaxy S 5 Unified Development] nictabor:
So, I'm experiencing a weird issue now that I've gone to the newest build of LOS. My Pixel Launcher no longer swipes to show Google Now. I did check the setting, but still not working. Are any of you experiencing this?
[Samsung Galaxy S 5 Unified Development] KazuDante:
Where can i get the one that worked for you?
[Samsung Galaxy S 5 Unified Development] Malacant:
https://github.com/opengapps/arm/releases/download/20170109/open_gapps-arm-7.1-pico-20170109.zip
[Samsung Galaxy S 5 Unified Development] KazuDante:
Thank you so much.
[Samsung Galaxy S 5 Unified Development] zeifers:
just a heads up, i installed the weekly and the 1-26 nano gapps, clean install. no problems so far, no restarts, i installed all the google apps i use from the store and reset my phone to see if it would loop, its still working fine.
[Samsung Galaxy S 5 Unified Development] jdrch:
I did exactly this on my G900V updating from the unofficial Jan 21 build to the official Jan 25 build, and it worked perfectly. Thanks, man :)

---------- Post added at 10:13 ---------- Previous post was at 10:11 ----------

Yes, you can flash the supersu app at any time after the official build, AFAIK.
[Samsung Galaxy S 5 Unified Development] GGTheGooch:
Probably a dumb question but is there a new forum for the official builds? I looked around but found nothing.
[Samsung Galaxy S 5 Unified Development] ad0dh67:
older playstore works without any problems [emoji106]

addon supersu [emoji106]
[Samsung Galaxy S 5 Unified Development] phenix23:
Which version of Google Play services is running in this package?
[Samsung Galaxy S 5 Unified Development] Kadajo:
Gaps still hangs or crashing the phone, i just try pico from today and instant freez and phone getting hot, im going back to Marshmallow., and wait for fix.
[Samsung Galaxy S 5 Unified Development] GGTheGooch:
Is there a fix for the official 25 build root access issue? I remember seeing something on here but I don't remember where it was discussed.
[Samsung Galaxy S 5 Unified Development] zeifers:
10.2.91 came with the gapps
[Samsung Galaxy S 5 Unified Development] systemcrash:
no fix for you - what did you forget to provide????
[Samsung Galaxy S 5 Unified Development] Kadajo:
Sorry..

klte
[Samsung Galaxy S 5 Unified Development] derAndroidler:
No problem with Gapps
[Samsung Galaxy S 5 Unified Development] ad0dh67:
[emoji6] your lazy or word blind

https://download.lineageos.org/extras
[Samsung Galaxy S 5 Unified Development] GGTheGooch:
^ You're
[Samsung Galaxy S 5 Unified Development] ad0dh67:
Join Date: Feb 2011

;) glad to help you lazy person
[Samsung Galaxy S 5 Unified Development] raylogic:
Woohoo
[Samsung Galaxy S 5 Unified Development] dotgeo:
Still crashes/freeze Gapps 26.01.17 (tried all versions mini/stock etc.) clean flash official lineage sm-g900f... :(
[Samsung Galaxy S 5 Unified Development] jdrch:
Modified version of the above that worked for me on the G900V going from the 20170121 unofficial build to the 20170125 official build:

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

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.

Install Official Nightly LineageOS build for your device.

Install su (arm) zip.

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

Power Off device, then boot into OS (first boot is gonna take a while)

---------- Post added at 13:59 ---------- Previous post was at 13:57 ----------

Does anyone know if the backup restoration process bug has been fixed? So we still need to use the OP workaround? Haven't seen an update on that issue in a while?

Also, any JIRA details?

Edit: Jira is here: https://jira.lineageos.org
[Samsung Galaxy S 5 Unified Development] ad0dh67:
just read couple pages back, there you will find your answer and the older gapps which won' t give you troubles

https://xdaforums.com/showthread.php?p=70739820
[Samsung Galaxy S 5 Unified Development] GGTheGooch:
And your point is??????
[Samsung Galaxy S 5 Unified Development] voak:
Try Dynamic gapps. That is what am using now and phone has been stable for 4hrs straight
[Samsung Galaxy S 5 Unified Development] RealMadri4Ever:
Klte

Clean flash

Wipe advanced

Factory wipe

Install lineageos

Install gapps 26.1.2017 mini

Reboot

All works
[Samsung Galaxy S 5 Unified Development] passie99:
I totally agree, I never had a ROM which was as great as lineage os is. Great work, seems to be almost bugless, but I'll try it out some more tomorrow. Seems to be usable as a daily driver.
[Samsung Galaxy S 5 Unified Development] omgbossis21:
Still on both ROM and gapps from 1-19, gapps updated last night with no issues. I did dirty flash from cm13, even tried that theme from playstore that was mentioned and had to restore backup last week which worked fine.
[Samsung Galaxy S 5 Unified Development] Young Gunna:
Running a KLTEVZW with clean install straight to Lineage lineage-14.1-20170125-nightly-kltevzw-signed i got boot loops and could not get past set up when i tried to install the latest opengapps open_gapps-arm-7.1-aroma-20170126.

Cleared everything but system and SD card using TWRP 3.0.2.0 and reinstalled opengapps version open_gapps-arm-7.1-aroma-20170119 and was able to complete setup and phone works fine. Checked my google play version and it is 7.4.12.L-all [0] [PR] 144479971 which is the latest and still no problems...
[Samsung Galaxy S 5 Unified Development] mrmarioman:
I supppose it won't be a problem dirty flashing from the Unofficial Lineage builds to the Official nightly?
[Samsung Galaxy S 5 Unified Development] Young Gunna:
This isnt recommended based on the blog on the lineage forum... if you want to dirty flash then you have to install the experimental first and then the latest nightly for your device.

Regarding installation, we recommend that users wipe when switching to LineageOS, and reinstall their gapps. However, we recognize that this can be time consuming, so we are offering an EXPERIMENTAL (read as, if it fails, you’ll have to wipe anyways) solution.

Alongside the ‘weekly’ release for your supported device, we’ll provide an EXPERIMENTAL data migration build.

This build will allow you to ‘upgrade’ from CM to the signed LineageOS weekly

This build may wipe permissions (you’ll have to re-allow app permissions), but should retain all user data

This build will be watermarked with an ugly banner to ensure that you don’t permanently run this EXPERIMENTAL release, and upgrade to a normal weekly after.

The process for this installation will be as follows:

Install EXPERIMENTAL migration build on top of cm-13.0 or cm-14.1 build (don’t try to install LineageOS 13.0 on top of CM 14.1, that will not work).

Reboot

Install LineageOS weekly build

Reboot

Re-setup your application permissions

Given the EXPERIMENTAL nature of this process, we are going to remove this option in two months time.
[Samsung Galaxy S 5 Unified Development] limeaide:
This is not a 100% fact. I am using GApps from october and I was having issues. Its from a auto update that I think has been fixed. Today I had to reinstall clean to get on the official build. And as soon as I finished setup the play store was doing a update even tho I have auto updates turned off. The minute I connected to wifi it did a update and then prompted me with 45 updates (lol) most of which are google apps from the outdated GApps I used.

If I want just to get play store and basic google apps which one should I use? Ive tried them all and it seems unless I use stock I cant get a keyboard app installed. And text to speech fails to recognize 90% of the stuff I say on a fresh install.
[Samsung Galaxy S 5 Unified Development] haggertk:
Assuming that you are coming from my unofficial it won't be a problem. I cannot guarantee coming from other unofficial since I cannot attest to what is in the build.

- Flash experimental build to strip the old test-keys

- Flash nightly

- Profit
[Samsung Galaxy S 5 Unified Development] mrmarioman:
Thanks for your detailed answer. I'll go for the clean install. Cheers.
[Samsung Galaxy S 5 Unified Development] Apathetik:
If you're happy with Philz and it does everything you need it to do. Perfectly fine to stick with it. I've not looked into Philz Touch Recovery (started with TWRP and it did everything I needed it to). So I'm not sure if there are feature difference between the two. As far as flashing a new recovery. I always do that from Odin, so it should not affect your data at all as it's a different partition. Just to be on the safe side though, before performing any flashing operation. Always a good idea to ensure you have a NAndroid backup.

Super SU is not officially supported. From what I've heard, it will work and provide root access on your phone. But due to not being officially supported. It does not have the same level of system integration. If you want LineageOS Official builds to behave like the unofficial builds with root baked in. You'll need to remove Super SU, then flash the official SU patch. Which you can find >Here<.

As far as installing the official SU package. That can be done ANY time you want as long as you're running an Official LineageOS build.

Had the same thing happen. Go into your apps, select a different launcher as the default (necessary to uninstall Pixel Launcher). Then uninstall the Pixel Launcher. Boot to recovery, then reflash Pixel Launcher onto the device. That's what I had to do to get it working. Also, fair warning. This IS going to reset your home screens, if you're like me and need everything in it's proper place. Take a screenshot of each of your home screens before removing the Pixel Launcher and reinstalling it. :)
[Samsung Galaxy S 5 Unified Development] nictabor:
Thanks. I actually did this several hours ago. Turns out that it won't work unless it's a system app.
[Samsung Galaxy S 5 Unified Development] Brasscat82:
Anyone running boeffla venom kernel with this? Any issues?

Also, has the Google Play services bug been fixed for the official nightly?

Been using RR rom since Cm went under and it seems to have a Lot more problems with the play services, any insights?
[Samsung Galaxy S 5 Unified Development] PorchSong:
Actually all you need to do is change your build prop to say pixel, then copy data/app/nexus.launcher to system/app. Then uninstall pixel from app store, then go into system/app/Nexus and install from there. Then choose pixel as default launcher. Reboot and you have assistant etc.
[Samsung Galaxy S 5 Unified Development] dataphry:
looking forward to call recording being enabled in the upcoming official release
[Samsung Galaxy S 5 Unified Development] :
Here on vzw, wiped and installed 1/25 nightly build of lineage (vzw) and open gapps and the phone is rebooting 20s after setup begins.

Any solutions for this?
[Samsung Galaxy S 5 Unified Development] Young Gunna:
Roll back to Gapps that was released in the Jan 19...
[Samsung Galaxy S 5 Unified Development] firefds:
I thought it was gone as well, it's still there
[Samsung Galaxy S 5 Unified Development] igorescu04:
Hy guys . It is available any official web there to see the daily changelog like the old cmxlog?
[Samsung Galaxy S 5 Unified Development] alyousmy:
I need help with my IR. I was on lineage-14.1-20170125-nightly-klte-signed but IR seemed to not work with any remote apps.

I odin to stock 6.0.1 and it started working again. I odin twrp-3.0.2-2-klte.img, factory wipe three times, flash lineage-14.1-20170125-nightly-klte-signed, flash open_gapps-arm-7.1-mini-20161230 and restart. IR still doesn't work. Everything seems to work for me except IR. Did anyone have this issue or know how to fix?

I tried the following remote apps:

Sure Universal Remote

Anymote Universal Remote

Peel Smart Remote
[Samsung Galaxy S 5 Unified Development] Big_T71:
Look here

https://www.cmxlog.com/14.1/klte/
[Samsung Galaxy S 5 Unified Development] mmtrt:
cmxlog now uses lineage inplace of cm.
[Samsung Galaxy S 5 Unified Development] mini01:
Same here, but still disabled auto updates. No problems at all - fingers cross:)
[Samsung Galaxy S 5 Unified Development] Cartoon69:
For the Google Play Services debacle, there seems to be a problem moving from version 10.0.x of this to 10.2.x. The version 10.2 has some new changes like removing API support for pre-ICS (android 4.x) devices and who knows what else.

On my stock Sony phone, it is fully updated according to Play Store, but I am now still on 10.0.84. I am pretty sure that it was on 10.2.x before, the Sony with stock ROM was unstable and I "disabled" the app forcing it to go back to some version 9.x and after I updated it again it only updated to 10.0.x... Has the 10.2.x version of it been withdrawn?

Can anyone who installed and updated all the Google apps and still have a stable phone check which version of the Google Play services they actually have installed?