[Samsung Galaxy S5 Neo ROMs, Kernels, Recoveries, &] FalsAlarm:
Problems running Lineage OS 16

Hi everyone, I read about up to page 10 on this thread but I don't have anymore time tonight to read the rest up to current. I'm having problems with Lineage OS 16 which I just finished installing on my SM-G903W. I used the patched Odin(Odin3_v3.13.1_3B_PatcheD) to flash TWRP using the AP button to select the file called, twrp-3.3.1-0-s5neolte.img.tar and I unticked 'Reboot' option. The flash was successful and I had to power my phone off manually and boot immediately into recovery mode after I performed the flash of TWRP. I know everybody already knows this but just to be clear on what I did.

Initially I tried following a tutorial on the net somewhere that says to use Heimdall to flash the Lineage OS 16 archive. I wasn't ever able to get Heimdall to work no matter what USB driver I installed. I ended up using the latest official Samsung USB driver(https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows) and just copied the Lineage OS 16 and the gapps zip to internal storage using Windows explorer copy/paste. Then, I used the TWRP to flash them. No errors during the flashing process and when I rebooted, Lineage OS 16 was finally installed!. Feeling pretty good, as soon as I setup the google account and other welcome screen settings, Lineage OS asked me which launcher I should use. There were 2 selections, Pixel launcher and Trebuchet. Personally I like to use Microsoft launcher but I thought I'd try Pixel launcher this time. After selecting Pixel launcher, it tries to load up but crashes. A window pops up saying Pixel Launcher has crashed. App info and Close app are the only options. If I choose close, it tries to load again and the window pops back up with same options. If I click on App info-->Advanced-->Open by default, then click on Clear defaults button, it will then allow me to select the other option which is Trebuchet. After selecting Trebuchet, I tried to visit the Play Store to see if I could update pixel launcher to the latest version but I think it already is the latest version as there was no update button.

The second problem I had was that I was holding my phone in my left hand and using my right index finger to tap the screen. The volume slider bar moved down to 0 position all by itself. I noticed it moving by itself and so I turned it back to 100, and within 3 seconds it went back down to 0. So I thought maybe the phone was detecting some kind of gesture shortcut for turning down the volume perhaps with my left hand index finger by the rear facing camera. I turned it up to 100, again it went back down to 0 by itself. I got a little worried and so I took out the battery for my phone and changed my Google account, Facebook account and online banking passwords using my laptop. Anyways I'm not sure why this volume incident happened but I was worried about my online accounts. So I am gonna flash back to stock for now and wait to hear back from you android rockstars/ninja's about what could cause this type of behaviour before trying Lineage OS 16 again. :D

Below are the details.

LineageOS version: lineage-16.0-20191019-nightly-s5neolte-signed

LineageOS Download url: https://mirrorbits.lineageos.org/fu...age-16.0-20191019-nightly-s5neolte-signed.zip

Gapps version: open_gapps-arm-9.0-mini-20191017.zip

Gapps selection: ARM, 9.0, Mini

== Did you ==

wipe: Yes(TWRP , WIPE-->Advanced WIPE(checkmarked, Dalvik/ART cache, Cache, Data))

restore with titanium backup: No

reboot after having the issue: Yes, tried rebooting and it did not resolve the pixel launcher crashing

Are you using--

a task killer: No

a non-stock kernel: No

other modifications: None

For the record, I really liked using Lineage OS 16 because it's nice and fast. The S5 Neo's octa core processor and the light weight Lineage OS go really well together. Is it possible to run android 10 or is that not really cool right now. I don't want to turn into a android ninja and get it to work by compiling the source but am just curious if it could work or not. No making fun of when I decide to use bold tags in my text on here, :eek:.