yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] fitittome:
There is another of these boot hangs on Reddit and the user was smart enough to get a log.

The circumstances are the same, they were using Official TWRP 3.1.0-1. I didn't experience this but had upgraded to Official TWRP 3.1.1.-1. There are a large group out there using the Official 3.1.0-1 version and I am a bit worried that others may encounter this over the next week.

I assume that the Upgrade app is writing 'something' (maybe a script) to that /misc partition that the 3.1.0-1 version of TWRP is unable to handle. Didn't I see a gerrit on 'toybox' or some other misc tools a little while ago?

PS.

Everybody, inc. Lord Boeffla, loves [MENTION=5110154]fipsy[/MENTION] the unparsable.

---------- Post added at 09:40 AM ---------- Previous post was at 08:51 AM ----------

This on-going issue with 'Files' app not refreshing free space. I think it's important to get this fixed.

It's a bug in Nougat.

Please can you click on the above link and STAR it.

I am hoping that if it gets more stars it will get a higher priority.
[Samsung Galaxy S 5 Unified Development] 10goto10:
I know discussion of Magisk is off-topic (and unsupported), but I just want to give a heads up: don't install the Android Mic Fix module, it will mute the in-call earpiece speaker. The bug is with the module changing the Qualcomm build.prop settings and incompatibility, not with the ROM.

If you want to boost the low Mic volume, first try cleaning the microphone holes first, and if that still doesn't fix it, try modifying the media_profiles.xml (there's a thread about it in this device forum.)
[Samsung Galaxy S 5 Unified Development] fipsy:
I always used the play store app and never had any problems with it. It also shows the list of changes in the current and next build with direct links to the corresponding review.lineageos.org pages which also is very nice. And I can select any folder for the downloaded updates. For example on the external sd card. Love that app. :)
[Samsung Galaxy S 5 Unified Development] tommasa:
Thanks man, I had the same problem. Could you share the post, pls?
[Samsung Galaxy S 5 Unified Development] 10goto10:
This is the thread: https://xdaforums.com/galaxy-s5/development/how-to-microphone-gain-increase-s5-t3190613
[Samsung Galaxy S 5 Unified Development] fipsy:
Just to say: If I got it right, the reason for this is that the TWRP developers simply messed up and forgot to offer the current version 3.1.1 for the S5 for a long time. That's why this old version is still so common.

Laugh! Thank you so much! Trying not to be that cryptographic anymore. :cyclops:

Just starred that issue. I would never have thought that this bug, which I discovered for the first time in March and reported here, would occupy us for so long.
[Samsung Galaxy S 5 Unified Development] fitittome:
I think that's true. BUT I have no idea what other tweaks [MENTION=2693412]haggertk[/MENTION] has done in his own unofficial version. He must have very good reasons for doing this. [MENTION=5795145]javelinanddart[/MENTION] was very clear that we should be using Kevin's version.

Thanks. It's the little things like this that make a big difference. I guess most give up. But I do have a Nexus now to test things on! It runs 'O' but had to downgrade it!
[Samsung Galaxy S 5 Unified Development] jakem742:
Just to clarify, my problem wasn't an outdated TWRP; I was on 3.1.1-0. It was - if you're right - because I wasn't using the unofficial klte version. I've had this problem with an earlier update in Nov, so this was the second time OTA failed me (using the system inbuilt "check for updates" - I didn't have the app installed).

It was fine before Nov builds! Trying to revert to older LOS versions doesn't fix the boot problem, so it isn't anything in the build itself that's the issue (leading me to think you're probably right about the TWRP fix).
[Samsung Galaxy S 5 Unified Development] fipsy:
My trust in the developers of TWRP is also a little shaken. Especially because the official TWRP-Manager App from PlayStore still shows version 3.1.0-1 as the current valid version. So it is certainly not the worst idea to use Kevin's version. :fingers-crossed:
[Samsung Galaxy S 5 Unified Development] mind.inc:
that really saved me hours of sd path changing, thanks!
[Samsung Galaxy S 5 Unified Development] cal002:
IIRC TWRP 3.1.0 didn't check the update command in /misc so you had to install manually.

TWRP 3.1.1 added the /misc handling.

(cm-13 wrote the update command to /cache/recovery/)
[Samsung Galaxy S 5 Unified Development] fipsy:
I am glad that my contribution has been so helpful for you!
[Samsung Galaxy S 5 Unified Development] hellfish89:
hey this is linuxhippy from the s3 forums.....the latest build klte for s902l works great.....lol...everyone if you turn off everything like wifi sync and all other bs most people dont use plus put the battery profile on power saver it works great on stock kerne...with no gapps.... ;) i get 8 hours sot to 1 day 12 hours sot....depending on usagel

---------- Post added at 02:10 AM ---------- Previous post was at 02:03 AM ----------

lol...not that i care to much but incase anyone is wondering ....i lost access to my linuxhippy account so this is my new one.....ive been monitoring these forums for the s5...lol..just been tolazy to re register a new account till now....anyways i have alot of experience in the samsung field...hope i can help many people to come...thank you and smoke up...lol... ;)
[Samsung Galaxy S 5 Unified Development] fitittome:
Lost in the mists of time

TWRP 3.1.0 did handle auto updates! I think this post shaped my thinking and was why I was so surprised that the dev had an unofficial 3.1.1.

https://xdaforums.com/showpost.php?p=72255906&postcount=6766
[Samsung Galaxy S 5 Unified Development] mkosel:
FYI, I just attempted to upgraded my S5 900V using TWRP Official TWRP 3.1.1.-0. I downloaded the 11-23-17 build using the lineageOS downloader in About Phone. I then manually booted into recovery, navigated to the download folder and flashed the upgrade. The phone restarted twice and then got stuck on the LineageOS logo and has been that way for over an hour.

I am going to attempt to flash the "unofficial" TWRP 3.1.1 build and see if that solves my issue
[Samsung Galaxy S 5 Unified Development] fitittome:
Make sure you upgrade the Modem/Bootloader (Firmware) to the latest version in Odin. The dev has a set here for the 900V
[Samsung Galaxy S 5 Unified Development] Servus Pauperis:
I have no network, it is unlocked on all networks and everything should work, but it does not work, is there any solution?

Maybe someone has already had this problem, but I could not find?
[Samsung Galaxy S 5 Unified Development] fitittome:
We need info to help. Model No. Baseband. Nightly installed etc. etc.
[Samsung Galaxy S 5 Unified Development] fipsy:
I'm not so sure this has to do only with the bootloader. I had the same problem with a stuck device when I wanted to downgrade from a higher version to a 2 or 3 releases lower version via TWRP update. I suppose the same thing might happen if you skip too many versions while upgrading. I suppose if the changes are too extensive, this might happen.
[Samsung Galaxy S 5 Unified Development] Servus Pauperis:
Samsung S5, SM-G900F (klte)

G900FXXS1CQAV_G900FVFG1CPJ1_G900FXXS1CQAW_HOME

lineage-14.1-20171116-nightly-klte-signed
[Samsung Galaxy S 5 Unified Development] fitittome:
Flash latest firmware. Check my signature for 900F.
[Samsung Galaxy S 5 Unified Development] fitittome:
[MENTION=2693412]haggertk[/MENTION] can you tell us if the best advice is to use your version of TWRP or the official version 3.1.1? What are the differences?
[Samsung Galaxy S 5 Unified Development] mkosel:
So I just flashed the latest Modem/Bootloader form the link above and I also flashed the unofficial version of TWRP and I still get stuck in a never ending boot (at the lineageOS logo). Is there anything else I can try before I do a factory reset?
[Samsung Galaxy S 5 Unified Development] fitittome:
Wiping cache/dalvik often works if it stops at logo.
[Samsung Galaxy S 5 Unified Development] mkosel:
Thanks for the suggestion. Unfortunately I've already tried this several times.

---------- Post added at 01:58 AM ---------- Previous post was at 01:13 AM ----------

Well, I finally got it to boot. On a whim, I decided to wipe system and reflash the 11-23 LOS update. Strangely enough everything works. I always thought that the update process included a wipe of system.... perhaps I was wrong?

Thanks for your help!
[Samsung Galaxy S 5 Unified Development] cal002:
The install process saves some stuff according to scripts in /system/addon.d/ and restores

it after flashing the system image. It's used by third party addons like su to persist through updates.

---------- Post added at 12:41 ---------- Previous post was at 12:22 ----------

The biggest difference is that official TWRP is compiled in Android 6.0 OmniROM tree (I think),

while Kevin builds it in cm-14.1 source as described here.

The TWRP source is code is the same but the kernel is different and there may be small differences

in device config. Busybox version might also be different.

You can compare

https://github.com/TeamWin/android_device_samsung_klte

https://github.com/LineageOS/android_device_samsung_klte-common
[Samsung Galaxy S 5 Unified Development] shaq1907:
I installed nightly latest version and it works well. Thanks for all developers:good:
[Samsung Galaxy S 5 Unified Development] Servus Pauperis:
First I had a problem with returning stock rom,

but after 20 times it passed.

Now I have the latest version of the system,

but I still cannot register on the network.

The SIM slot works normally.

A network signal also appears, just like it all works,

but when I try to sign up to my operator's network,

it takes a long time and finally I get it: not registered on the network.

Did anyone have a similar problem, is there any solution?
[Samsung Galaxy S 5 Unified Development] fitittome:
I've seen this where the phone has been carrier blocked, reported lost or stolen etc. In the UK we have Checkmend who can check this for a small fee.
[Samsung Galaxy S 5 Unified Development] Servus Pauperis:
Buying is used, but I do not believe the cell phone is lost or stolen,

is it possible that it is another problem?
[Samsung Galaxy S 5 Unified Development] noratroll:
Not really clear what the issue might be. You could try to install the correct modem for your device - more inforamtion about that you'll find here:

http://xdaforums.com/galaxy-s5/development/rom-ane4-kitkat-4-4-2-multi-csc-t2813628/page758

Furthermore I recommend to flash the stock again via odin (the correct firmware for your region)
[Samsung Galaxy S 5 Unified Development] omgbossis21:
Sounds like the sim isn't activated, can you test the sim in another phone?
[Samsung Galaxy S 5 Unified Development] Servus Pauperis:
Thanks for the suggestion, I will try.
[Samsung Galaxy S 5 Unified Development] fitittome:
No, he has the correct modem. Rather than Odin, it may be worth giving the Samsung Super Switch software a shot. That will sort out any efs issues. Its slow but got me out of a hole more than once.

Edit: Well he said it was a 900F. What does it report if you boot into Odin mode?
[Samsung Galaxy S 5 Unified Development] Servus Pauperis:
In ODIN mode it is all common,

Binary: Official (for now)

System: Official ... (for now)

I'll try, thank you.
[Samsung Galaxy S 5 Unified Development] fitittome:
Thanks that's interesting. I wondered where that source was living. But I'm still not clear which version we should be telling people to use. The S5 wiki instructs us to use twrp.me/klte and there is no mention of the unofficial version anywhere. It's just those few users being unable to boot after installing the latest nightly worries me, if its related. Which I guess it might not be.

Edit: Actually, Kevin's version eliminates that annoying 5 second delay before you can use the touchscreen when you first load the official version.

---------- Post added at 06:31 AM ---------- Previous post was at 06:00 AM ----------

It looks like the new versions of KA and 3C now report the CPU frequency properly and the MP-Decision errors seem to have gone away too. Fingers crossed!

Edit: Nope CPU3 still shows at 2.45Mhz whilst idle.

Edit2: Nope, MP-Decision errors are still there.
[Samsung Galaxy S 5 Unified Development] fipsy:
Since the last release I've had it twice that gravity sensor and linear acceleration suddenly don't work anymore. This means that also the orientation does not function anymore and the display is no longer rotated depending on the position of the device. After rebooting the device, everything is working again.

Does anyone have this problem, too?
[Samsung Galaxy S 5 Unified Development] fitittome:
Me permanently. I've got two phones with dicky sensors. :( They start off by intermittently failing, then it just gets worse and worse until they give up completely.
[Samsung Galaxy S 5 Unified Development] fipsy:
Grrrrrr! What a mess! :mad: Does Samsung only use junk? Without a position sensor, the device is no longer worth anything. With my old S3, the WLAN module gave up after 3 years. This was definitely my last Samsung device. I think the future lies with OnePlus for me.
[Samsung Galaxy S 5 Unified Development] fitittome:
Mine took about 2 months to fail completely. It was right at the time when 14.1 first came along and the first releases had gyro problems. I remember being shouted at for whining! :) Just a thought....... You have tried stock, right?
[Samsung Galaxy S 5 Unified Development] fipsy:
I didn't try stock. You think the problem doesn't show up with Stock? The problem only occurs every few days. I can't run Stock Android that long. I need the device to work with! I have never had this problem before. I'm using this device with LineageOS for half a year now.

I am also doing tests with the kernel from fbs. Maybe that's the reason. I don't know if the gravity module is compiled into the kernel. Then it could be related to the kernel, especially since it was created with the Linaro compiler. So I will use the Boeffla kernel again for the time being.

If it's a hardware issue maybe the device can be repaired. However, I'm afraid the sensor is on the motherboard. Then you might have to buy a used device with a broken display.
[Samsung Galaxy S 5 Unified Development] fitittome:
No, but I know you run your device 'hot' with kernels and mods etc. You never know!

They are repairable with a new motherboard. The gyros and other sensors are surface mounted and beyond my abilities to fix.

My eldest just bought a 900F on flea bay for £70 which is about the same as new lcd/digitizer and mid-frame. I have a couple of motherboards spare, but I'm certain they are now the ones where the sensors are broken.
[Samsung Galaxy S 5 Unified Development] fipsy:
Although I have a rework station, I wouldn't dare to repair a smartphone motherboard by replacing SMD components. They're too small for that. You have to replace the whole board. It's not that big a problem.

Sounds like defective sensors are the norm with this phone.
[Samsung Galaxy S 5 Unified Development] t_house:
I'm sorry for asking such a noob question as I don't classify myself as one. I just like to be very clear with what I'm doing before I do it, like the old measure twice, cut once saying. My modem is updated to the current one (for the 900V) but my bootloader is quite old. I believe it's BOD5. I've always left it at that one because before we were able to unlock the bootloader, that was the last bootloader that let you root and were able to downgrade if you wanted to. The link to the modem and bootloader that you've posted....I'm just making sure that is completely compatible with those of use with unlocked bootloaders, aka "developer" phones. Like I said, very noob type question but I just want to be certain. Thanks again for your help.

Sent from my kick ass S5 that Verizon no longer has locked down!
[Samsung Galaxy S 5 Unified Development] thaijunk:
I also had this concern and haggertk relieved that concern a while back. His files are made specifically for the 900V and does not contain the aboot which is the partition that would lock down your bootloader again. The file in that link should be fine for updating your modem. I'll probably update mine at some point this week too.
[Samsung Galaxy S 5 Unified Development] jdm2008315:
I get the error failed to connect to google services and I can't connect to gmail or the play store. I searched the thread and this happened to someone else but they had installed supersu, and I have not. Anybody have a solution. Internet(including WIFI) and data are fine, so it's not that
[Samsung Galaxy S 5 Unified Development] fbs:
I think it's a known issue, but is it so hard to fix it?

If you try to enable WIFI while HOTSPOT is still ON, the gui says WIFI is on but won't turn it really on till I enter Airplane mode.
[Samsung Galaxy S 5 Unified Development] knojap:
Fingerprint Problem in Lineage 14.1:

Device KLTE:

Every time after i delete my fingerprints i can't create new ones. The settings for fingerprint are always crashing?

Can anybody confirm and has got a solution?

Thanks
[Samsung Galaxy S 5 Unified Development] fitittome:
Update Modem/Bootloader combination (firmware) to the latest available version for your device.
[Samsung Galaxy S 5 Unified Development] knojap:
It is the latest one!
[Samsung Galaxy S 5 Unified Development] fitittome:
In that case our are going to need a logcat to see what's going on. Post it to https://vomitb.in/ someone may be able to shed so light on the problem. But, I fear, ultimately you will have to reformat to resolve. :(
[Samsung Galaxy S 5 Unified Development] knojap:
But it happens every time with every Linegae 14.1 Version.

It would be nice if anybody can reconstruct it.

Just create 3 Fingerprints. Delete the and try to create 3 new ones...

Don't know how to make a log???
[Samsung Galaxy S 5 Unified Development] bytes2bits:
When that happens to me I usually remove my google account and then add it back. This resets everything and usually resolves it for me. Menu/settings/accounts... click on Google then 3 dot menu.
[Samsung Galaxy S 5 Unified Development] fitittome:
No it doesn't.

I couldn't.

Worked fine.

How to capture logs
[Samsung Galaxy S 5 Unified Development] knojap:
Ok, I've got al log. But can't load it up because i'm at work.

Can You do me one more favor.

After you delete the 3 fingerprints, can you set the unlockscreen option to swipe an try again to create a new fingerprint?

Thanks
[Samsung Galaxy S 5 Unified Development] fitittome:
Worked OK using a 3x3 pin.
[Samsung Galaxy S 5 Unified Development] knojap:
Thank you very much. So i have a problem :) but don't know what to do. Can you analyze my logcat?
[Samsung Galaxy S 5 Unified Development] fitittome:
Someone will have a look at it and hopefully offer some advice.
[Samsung Galaxy S 5 Unified Development] omgbossis21:
Happened to me 2 or 3 times and the last time I found that privacy guard had turned off access under the playstore and google services!
[Samsung Galaxy S 5 Unified Development] eurohunter:
Worked for me as well using pattern as backup. I tried both Create 3 fingerprints-> delete 3 -> create 3, as well as create 3->delete 3->switch to swipe->create 3. no problems at all. fingerprint worked properly in all occasions. kltedv user
[Samsung Galaxy S 5 Unified Development] fitittome:
My bad, its called Smart Switch. Its the Emergency Software Recovery and Initialisation option.
[Samsung Galaxy S 5 Unified Development] Servus Pauperis:
OK, I'll try.
[Samsung Galaxy S 5 Unified Development] omgbossis21:
Well I can't really recommend using the latest official twrp 3.1.1-0. I'm running Nov 1st build of lineage and have used twrp 3.0.2-2 for much longer. Last night I upgraded twrp and booted recovery to make sure it took. Tonight I went to upgrade boeffla kernel test 15 to 16 (yes my kernel is ahead some) and upon attempted reboot to recovery it never loaded twrp. I was instantly in Odin mode with a "could not normal boot message", manual reboot into twrp and regular boot both proceeded to the same screen. Those who had the boot issue did the updates actually go through or did it boot it straight to the error? Anyway I flashes my original twrp version and could load twrp but no boot. I flashed the new kernel, cleared cache and dalvik and was then able to boot normally.
[Samsung Galaxy S 5 Unified Development] fitittome:
What is it with the followers of the Lord Boffla worshipping ancient relics? :angel:

edit: The very next day after I install [MENTION=516058]fbs[/MENTION] kernel.... again.... I noticed this:- https://review.lineageos.org/#/c/197576/ lol. After all is said and done nothing ever stays still in this game....
[Samsung Galaxy S 5 Unified Development] knojap:
Using official Lineage 14.1 for klte. Is there a way to use the fingerprintunlock after a reboot? Because after reboot i have to use the password. Thanks.
[Samsung Galaxy S 5 Unified Development] fitittome:
That's a hard baked security feature. You need password or pattern after a reset before fingerprint will work.
[Samsung Galaxy S 5 Unified Development] knojap:
But in Samsung Stock 6.01 i can do it withe the help from an xposed module. "Allmy".

And in Resurection Mix 5.8.5 (Nougat) it is also working.

Maybe there is a xposed module. I will have a look.
[Samsung Galaxy S 5 Unified Development] fitittome:
They probably amend things within the OS, maybe this is where you should look if you want to roll your own:-

https://github.com/LineageOS/android_packages_apps_Settings/blob/cm-14.1/src/com/android/settings/ChooseLockGeneric.java

Xposed isn't supported because it can fundamentally change things within the OS in a way that the developers cannot predict.
[Samsung Galaxy S 5 Unified Development] fipsy:
I don't understand any of this. I have been using TWRP 3.1.1-0 for several months now and have never had any problems. I also used the Boeffla kernel beta15 and 16 for one week each and also had no problems. The cause must be somewhere else.

As far as swappiness is concerned, the story is now ancient. Me and many others here have already said many months ago that a swappiness of 100 is nonsense. I always used only 30. fbs then recently said that the swappiness value is completely ignored by the kernel anyway. I have no idea what's right and what's wrong.
[Samsung Galaxy S 5 Unified Development] fitittome:
Going down the pub......

Join the club, I'm just along for the ride! :D
[Samsung Galaxy S 5 Unified Development] mind.inc:
is there a way to force the device to connect to 5ghz wifi if both, 2.4ghz and 5ghz, are available?
[Samsung Galaxy S 5 Unified Development] fipsy:
Unfortunately this seems not to be possible anymore. In earlier android versions you have been able to set the WLAN frequency band. I couldn't find this option anymore. As many other very useful options that have been present in earlier android versions and have simply disappeared.
[Samsung Galaxy S 5 Unified Development] javelinanddart:
I was wondering who would notice that. I remember early in the 14.1 bringup everything was nice and smooth, and it shocked me to see that was no longer the case. Now, of course, I am spoiled by having used devices with more RAM, but Steve's comment in the patch I picked makes me think that raising swappiness to 100 (which was done long after I sold my first klte) is causing this lagging I'm seeing. I was lucky enough to have stumbled across that patch while browsing, and I'm really hoping it will help. If you're interested in testing this, hit me up on hangouts - javelinanddart@gmail.com.
[Samsung Galaxy S 5 Unified Development] mind.inc:
sad to hear, but thanks for your fast reply!
[Samsung Galaxy S 5 Unified Development] fipsy:
This is definitely the case! I already noticed that about half a year ago in my first tests with LOS 14.1. After lowering swappiness to 30 everything ran well.
[Samsung Galaxy S 5 Unified Development] fbs:
My kernel defaults to 20, but even like that I notice too much slowdown when something is swapped. (whatsapp here, after some time, delays like 1-2 minutes to get back). Researching...