[Samsung Galaxy S 5 Unified Development] Apathetik:
[MENTION=2693412]haggertk[/MENTION] I managed to pull some logcats during bootup of a google play services broken install (will attach below).

Started with a 1-31 install on kltevzw (all PF4 aside from what LineageOS installs). And Open GApps 1-18 mini. Enabled ADB Debugging, restarted phone to recovery, and flashed 2-03 super gapps (was supposed to be a mini install, but it ignored my config file lol). Then went to full power off, ran "adb wait-for-device logcat > file" from computer, powered the phone up, and plugged in USB. And to my surprise... it did nothing. Logcat recorded 0 bytes of information.

I ended up having to go back to recovery, clear cache / dalvik. THEN boot with the same method, and it actually pulled a logcat. Just for testing, I tried rebooting and doing it again, and as it turns out. The first boot after clearing dalvik / cache is the only boot where ADB debugging still works. Any boot after that and it appears to be broken, and won't take a log. So if you go through the process I am to try and figure this out as well, hopefully knowing that will save you some time. lol

In regards to the logcats I'm attaching. There are 2, from 2 separate boots. But both taken of the same broken install, with the same method. The only difference being one was taken with '-v long' switch, the other is just a default 'logcat > file' (I find the -v long is much easier on my eyes, figured it couldn't hurt. In case you're the same). They are both rather large, around 2 MB each. I intended to let them run until the phone crashed and rebooted (which it was doing initially before I got logcats working), but it didn't seem that it was going to, so I just cut them off. (if you actually want me to try letting a logcat run until the phone reboots, let me know and I'll start it up again.)

Potential temp fix for ninja Google Services update (needs testing, more below).​

Ok, for starters. I do NOT know for sure, if this will prevent Google Services from updating in the background. And unfortunately (or maybe fortunately), my phone hasn't been pushed the update yet. So the only way I can reproduce a crash from updated Google Services, is to manually flash a newer version. So I can't personally test if this prevents a background update. Need a guinea pig to test this for me. :)

Need someone who is having their Google Services updated in the background (consistently), and having that boot loop their phone. What I need you to do is this:

Make Nandroid Backup of whatever ROM you're running (always step 1)

Wipe Data, and System

Flash latest Official LineageOS (should be 1-31 build)

DO NOT flash ANY gapps package (skipping this should ensure you can set up the phone without any crashes)

Wipe Dalvik, and Cache

Restart phone and complete set up process

Disable Mobile Data

Manually disconnect from, and delete any saved wireless networks. Can be done by going to Settings > Wifi > Gear Icon (top right) > Saved networks > Click any listed AP's and select 'Forget'

Enable Airplane mode

Power off phone, and restart into recovery

Flash preferred gapps package dated 1-19 or BEFORE, and restart

Go to Settings > Apps > 3 dot icon (top right), select 'Show System' > Scroll down and select 'com.google.android.gms.setup' > Data Usage > Enable options to "Disable all cellular data access", and "Disable all Wi-Fi data access". Repeat for "Google Play Services" (quick video Here showing how to disable the data for those two apps/services.)

Turn off Airplane mode, re-enable your cellular data (global setting only, NOT for those two apps), reconnect to wifi (optional, if you were using wifi).

The steps for globally disabling all data communication to the device are intentionally overkill, to ensure nothing potentially slips through until data for the Google Play Services is disabled. If you want, pulling your SIM card is also an additional option. After doing those steps though, monitor the phone for a while and see if it starts crashing / boot looping.

I did test running a phone with data to those two services disabled. And it seems to not really cause any issues. However, your mileage may vary (I can't test every app, feature, and gadget that you may or may not be running differently than me). But the google play store still functions properly (search for, install, update, uninstall apps). And all of my apps seemed to function properly as well.

But yeah, it's going to be a pain in the ass for someone to go through that to test this. So whoever does so, it's greatly appreciated. And even if this doesn't work. Hopefully we can keep at it and at least get peoples phones up and running. Until the root cause can be identified, and patched. :)