yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] curiousrom:
Messing Up w/ F2FS & Full Bloated Open GApps

" ...either way it isnt my daily driver" - Good because you have 2 ingredients of the recipe to mess up your S5. :eek:

From [MENTION=2693412]haggertk[/MENTION]'s post, the dev of the Lineage S5 klte + variants here about using the F2FS File System {Bold by me}:

"If you haven't already, try formatting /cache in recovery. And when doing so make sure not to use the mess that is f2fs. Filesystems listed in fstab that are corrupted in such a way that they are unmountable will result in similar symptoms.

When I was foolish enough to use f2fs, this happening to /cache was relatively common for me.

Manually running a fsck on /data from recovery wouldn't be a bad idea."

Flashing the stock Samsung firmware for your S5 & following S5 LineageOS Super Clean Install would be a way to restore the S5's stock Ext4 File System.

"...seems to work way better then ext4 on pie" - Without any S5 data before & after to prove that I am skeptical. :confused:

"...i just flashed gapps full with no problems." - I prefer the smaller Open GApps Pico package & get in Play Store the extra apps I want.

Check Open GApps Package Comparison to see all the extra Google bloat that the Full package includes compared to Pico which will eat the S5's available RAM, run more background Google services + eat the battery with more CPU, GPU & bandwith usage.

You could try to limit the damage with some of the suggestions described in Remove Animations UI Speedup Test - Taming Google & Apps.

***

Downsizing Open GApps

For those who installed a bigger Open GApps package & would like to slim down to a smaller one just reflash the firmware + the smaller Open GApps one after the other & then reboot to system & all your settings & apps will be preserved & any stock Lineage apps that the bigger package removed will be restored.

In TWRP > Advanced wipe of Cache and Dalvik / Art Cache only before doing so is not required but can't hurt.

***
[Samsung Galaxy S 5 Unified Development] dd805bb:
That is real nice. The one who developed f2fs works for Google now. Pie has f2fs embedded in it. Look up Android pie beta f2fs. Mr. Kim's comments are in pie. F2fs is used on the pixel 3. Dev can say all he wants. Pie has f2fs tools built in it. Anyone spouting off should research before being critical and have some actual information to back up their claims. Go look in the comment for pie. Doesn't matter how you port pie, contort it, make it your own, it is part the OS. No way to pull it out unless you start from the ground up. Which they don't. Ram is not going to overload. Cache is not either. Oreo and OS's before had no support for f2fs besides Samsung. Now it is in pie itself. And has been updated with tools they feel their newest flag ship can run on. Now if an open feels their own OS should run on f2fs on their newest flagship, sorry but I will try that out over whining and about problems that don't exist anymore. Out of date information about f2fs. People should go read about it. Because it made my s5 comparable to a stock pixel 2 XL which my GFS has and has everything stock. Both on pie. Pixel 2 ext4. My daily pixel XL ext4. It gives this a run for it money on a bench test for computing. Not cores. But anyways I guess when you don't research and actually know what time it is, it is hard to keep up with the times. Good luck. But I flipped it a few days ago to see if worked before I posted. Audio, video, games all run way better. Netflix doesn't drop resolution running out of resources, ext4 loses in real time computing on mobile platforms. Battery life is insane. Two days of music playing. Also no slow down when playing and viewing other apps. So much to be had from f2fs. And if Dev says not to, he probably should read what Google put it pie. F2fs works. Before nano and Pico were the only packages to install. Others would fail. Hell I am on stock. Didn't fail in TWRP saying not enough system. Read about that too, lineageos 16 and taking anything but nano and Pico. Now I may have found a way to actually get it working because no read what actually went into pie. This six months after release and four months after the pixel3 and no has caught on. Wow.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: Messing Up w/ F2FS

I'm not saying that Lineage 16.0 does not include anything F2FS related or that there is no other devices using it but I won't use it on my S5 klte daily driver @ the present.

Searches in the LineageOS Gerrit that may be relevant:

branch:lineage-16.0 f2fs with several patches not merged yet @ the present.

owner:haggertk@lineageos.org branch:lineage-16.0 f2fs with nothing klte + variants related yet @ the present by the S5's dev.

***
[Samsung Galaxy S 5 Unified Development] dd805bb:
Dev/Pie>Dev/lineagsos

Look, pie was developed not by anyone at lineage. I get what the dev says. There is a lot of different talk about lineagsos 16. One example look at razerloves version for pixel XL. Or other lineage devs. They all pull from the same branch to make there port of lineage. Their branch stems directly from pixel images. IDK about now but the pixel 2 features were showing up in playstore as apps to install on these ROMs. Meaning they were pulled from pixel 2 models. So much and exchange and dev work chasing down what it started with and then this Dev did this or that. But ask any of them they hardly ever pull code out. They put code in. They don't sift out something unless it is a real problem. Lineagsos was defaulting to f2fs for a while on Oreo on a few devices. Then changed it. Well they can't change what the original os is. Oreo was riddled with f2fs problems. Now pie has it deep in it. I understand they feel to keep it ext4 system. Cache and data is questionable as why they would want that. Now of Google apps look for f2fs FS and built using that FS. It is a patch to fallback to ext4. I also believe Google is pushing oems to switch to f2fs. OnePlus switched back to ext4. But sounds like they may switch back again. I may not saying switch the whole system over. Just data and cache. Helps on on the fly decisions. This has been running three days now like this. No crash. No bootloops, no reboots. All problems I have had the experience of having while on lineageos pie, on a pixel XL. Pixel XL doesn't have the option in TWRP to flip to f2fs. I see a huge difference between the two and the pixel XL should smoke this.
[Samsung Galaxy S 5 Unified Development] dd805bb:
Also I have been playing around in the files on my pixel XL. There is a resizing file,"resize2fs". My suspension was correct. Pie is originally made for f2fs. They have a few resizing files in pie to resize to ext4 as oppose to running f2fs. Hence the resize"2fs". It has so many options in there and another file listing ext2toext4 and a bunch of other resizing files. I was looking around for file to force change TWRP on my pixel XL. About to start searching in the s5 lineageos ROM, but I can bet dollars to donuts it is in there too. Meaning it is wasting resources always changing to ext4 and making sure it is ext4 if that is what it is. No other fs mentioned as to resize to other or from any another. Distantly list 2fs to ext4. That is part of pie if you are ext4. If it reads you are f2fs it doesn't need to resize or refile anything. F2FS is part of pie and everything else is patched to work with pie. I am pissed about my s5 being on lineageos and newer apps and os than my pixel XL. Apps are even different. My Gmail is full on material design. No colored top bar. Chrome is 72. Pixel XL hasn't updated to chrome 72 and doesn't have the newest app versions like this s5 has now. Why? Filesystem? Only real difference.
[Samsung Galaxy S 5 Unified Development] dd805bb:
So this is in the s5 bin. Same is in the pixel XL official stock firmware. These were built to use f2fs and have been patched to work with other systems.
[Samsung Galaxy S 5 Unified Development] omercansamali:
SIM card does it work .
[Samsung Galaxy S 5 Unified Development] fitittome:
Concise. Wise words. :good:
[Samsung Galaxy S 5 Unified Development] Supernoobsammyson:
Got an s5 and tried the F2FS. Cache and data to F2FS. Not system because it is formatted ext4. And from what I read about F2FS and Google. They rewrote some great features for F2FS. I also found the bin and located F2FS files and makeext2 to make2fs which is all there. I noticed they dropped the first f to keep that first. See for yourself. I have used it for one day now. No crash. Sprint version which works fine. I did flash stock because I like the pixel set up, bit the launcher is the only thing not working. Everything works. Seems to be faster than my other I left at ext4. Nothing big, just opens faster it seems, also I noticed it has all the newest apps right of the bat. The ext4 version said it had to upload all these updates. Same gapps and F2FS and it didn't update half as many. That was one weird part. F2FS seems to work.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Re: SIM Card Working?

You did not say your exact S5 model but looking at your posting history it seems that you have a SM-G900F, correct?

You also asked in an other thread if Turkish was available & I can see in 16.0 > System > Language & input > Language preferences: Türkçe.

To fix a no SIM or no network problem restoring an EFS partition often solves the problem.

See this post & make sure you have the most recent TWRP, bootloader & modem & after that make a EFS partition backup in TWRP before flashing haggertk's unofficial LineageOS 16.0 as described here: S5 LineageOS Super Clean Install.

You can also screenshot or write down your working APN settings before flashing 16.0 so you can use that info in case of a problem connecting to your network provider.

***
[Samsung Galaxy S 5 Unified Development] fitittome:
If it is Turkey, it maybe an SM-G900FQ, just saying. :eek:
[Samsung Galaxy S 5 Unified Development] curiousrom:
S5 Variants - SM-G900FQ?

That's why I asked [MENTION=7237594]omercansamali[/MENTION] what is his exact S5 model.

[MENTION=4828250]Ibuprophen[/MENTION] posted about SM-G900FQ vs. SM-G900F here.

The number of S5 variants is just crazy. Samsung really dropped the ball on this: https://en.wikipedia.org/wiki/Samsung_Galaxy_S5#Variants and this page says 42 Galaxy S5 models. :eek:

***

BTW users not mentioning their exact S5 model & system setup when reporting a problem is my pet peeve.

It's essential troubleshooting info IMO as what works on a S5 model may be problematic on an other & different solutions may be needed.

***
[Samsung Galaxy S 5 Unified Development] haggertk:
I'll try to make it short and sweet. Our, meaning the one available to 3.4 kernels, f2fs implementation is ancient. It was from before f2fs was merged into mainline (3.8). f2fs has evolved tremendously since that time, and Google using it on NEW devices is a testament to that.

That said, using it on this old device is inviting problems. I know, I've had them. Corruption is much more frequent than ext4, which is essentially as rock solid a filesystem as you will find on Linux (ignoring my actual fav zfs due to the licensing stuff that keeps it out of mainline).

If I were able, when I took over maintainership years ago, I would have ripped f2fs out of the kernel, but we have a rule that data migrations must happen across builds and versions.

I will forever stand by my statement that f2fs is a horrible idea when using kernels of this era. This is not about userland support.
[Samsung Galaxy S 5 Unified Development] dd805bb:
Why is Google choosing it? I understand the newest pixel 3 is on F2FS. I think people are familiar with old F2FS being solely Samsung in-house. Now it has matured and evolved to a point they feel it is good enough to run as oem. Ext4 is more reliable, that is fact due to everything running it and develop for it. I think now we are seeing a push in all directions for a faster more reliable phone and that means file system. Corrupted fs can happen on any fs. One bad apple can spoil the bunch. If you look in bin in pie now, F2FS is what it looks for first. It can read any file fs. Ext4 ext 3 and ext 2 and TMP fs. Along with F2FS. I have a pixel XL and pixel 2 XL. They could and should run F2FS as a first but no supporting it. It is odd that four years ago everyone wanted it when it was a mess and now that Google made into some of it is untouchable. It is kind of backwards that people now reject the idea. Most felt back when it lack self cleaning and support from the kernel. Well if pie has in system the support for it, all those stock kernels do now too and no one wants to flip them. Really odd.
[Samsung Galaxy S 5 Unified Development] haggertk:
We cannot get the mature f2fs. It's in the kernel. The crosshatch kernel is 4.9. The samsung_msm8974 kernel is 3.4.

Please feel free to backport the 4.9 implementation to 3.4. Then I will change my stance.

Alternatively, please feel free to get the Samsung 8974 devices working on a 4.9 kernel. With your knowledge it should be quite simple.
[Samsung Galaxy S 5 Unified Development] dd805bb:
Well this system has the files in it Google references to have F2FS. The kernel version on these is higher than the pixel XL itself. Merge comments for F2FS started four years ago in the Linux kernel itself. From what I read and then what I get on here, is two different stories. Personally I have a little over it. This also is a lineageos modified kernel. Not the last Samsung kernel. So it has been modified in someways. Seeing as Samsung had this developed by the time of the launcher of the s5, I would bet they merged something in there it accommodate that. The newest Linux isn't useable yes. But now that I found how to do it myself. No need for it. Google has so documents and lineage too. Building a base os is simpler than modifying chromeos to run on a Mac. I just read all of lineageos. GSI are Available too. Modding has turned into what I want and if ask about something it's stupid. Well I can do it myself. Good luck F2FS is integrated into pie, so if you merged and migrated from lineageos, the kernel already has support. They put it in years ago.
[Samsung Galaxy S 5 Unified Development] J-Lindo:
Say [MENTION=2693412]haggertk[/MENTION], will Pie+ builds for klte support the new Adiantum encryption, or is that restricted to newer devices?
[Samsung Galaxy S 5 Unified Development] haggertk:
Unsure. We're looking forward to specifics (I personally haven't looked to see if/how much is in master yet), but if there isn't a clean way to migrate from our legacy SW encryption to this new one, then we have to have a longer internal discussion. Remember, one of our charter requirements is that devices be able to retain data across a major version upgrade.

My devices don't leave the house without being encrypted, and while I mostly use mata and crosshatch now, hlte and klte are still in somewhat standard rotation. Having faster encryption would be a boon for this device.
[Samsung Galaxy S 5 Unified Development] SNiPe08:
Did anyone have flashed the latest February build? (lineage-16.0-20190209-UNOFFICIAL-klteduos.zip). I am in S5 kltedous and can anybody confirm that WIFI hotspot is working in this build? I am still on November 2018 latest build as hotspot is working great for me. December build and onward seems broke hotspot functionality. Thanks for helping. (My phone: S5 klteduos with fbs kernel)
[Samsung Galaxy S 5 Unified Development] fitittome:
Hotspot not working on my klte 9-FEB build, so I would guess not.
[Samsung Galaxy S 5 Unified Development] Struppi0815:
I have updated from 09.01.2019 to 09.02.2019. Works just fine. The first start, however, took 10 minutes. So be patient after flashing.

With Boeffla unofficial v19 really great.

Many thanks to the developer. Very good work!
[Samsung Galaxy S 5 Unified Development] fitittome:
Umm, as far as I recall, the device checks the regulatory requirements re 5Ghz band so that the device is rf compliant. I can see that when enabling Hotspot it seems to fail setting the CountryCode. There is a whopping table in the OS somewhere with all this info, I remember seeing it. I know that there has been much re-jiggering with Wi-Fi with Oreo and Pie. I sound likes an interesting thing to investigate even though it will be beyond me to fix.
[Samsung Galaxy S 5 Unified Development] Triviox:
Someone know if LineageOS team plan develop an oficial LOS16 to Galaxy S5 in the future?
[Samsung Galaxy S 5 Unified Development] warism100:
We will get official just we have to wait

---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------

Hi i have installed this latest build from haggertk

and no big issue just some lag with UI

https://androidfilehost.com/?fid=1395089523397887877

(09/02/2019.....KLTE)
[Samsung Galaxy S 5 Unified Development] systemcrash:
5GHz AP (wifi sharing) never worked on S5. Prolly never will. Something proprietary. I asked Kev years ago. Check the 14.1 discussion thread, I think.
[Samsung Galaxy S 5 Unified Development] Rome-Italy:
screen mirroring no work yet and the notifications no work sometimes, for example whatsapp does not report me notifications sometimes then if I open it I find many notifications that appear all together
[Samsung Galaxy S 5 Unified Development] mop09737:
Just one thing to report, when charging the battery the indicator led is off. Thanks.
[Samsung Galaxy S 5 Unified Development] curiousrom:
UI Lag - Cast, Miracast or Wifi Display - WhatsApp & Notifications

Check S5 16.0 optimization tips here including Privacy Guard Advanced: Remove Animations UI Speedup Test - Taming Google & Apps.

***

Added after testing to continuously updated New S5 LineageOS 16.0 haggertk 2019-02-09 Build! - Bug Report.

Google disabled Cast (same as Miracast or Wifi Display) in Android 9.0 Pie but some LineageOS devs are working on it for other devices which may be applied on the S5 in the future.

See this post for detailed explanations: Cast - Miracast or Wifi Display Not Working - Workaround which includes LineageOS Gerrit links & logcat snippets.

For example in this patch submitted but not merged yet @ the present: "Sadly, out-of-the-box Miracast support was killed in P, so we need this to keep Wi-Fi display feature working."

***

Apps Not Showing Notifications

"...whatsapp does not report me notifications sometimes" - Check WhatsApp settings for the individual groups or people for whom you don't get notifications. I have some Groups & people on Mute & their notifications dots only appear when I open WhatsApp in the foreground & never get notifications for those. Check also WhatsApp > Settings > Notifications.

Check > Settings > Apps and notifications > WhatsApp > Notifications.

Make sure in > Settings > Battery > Battery manager > Restricted apps > that WhatsApp is not selected. One can read in the bottom of that panel: "...Restricted apps may not work properly and notifications may be delayed.".

Search Settings with Notifications to find a bunch of stuff you can tweak.

If all the above fails: > Settings > Apps and notifications > Advanced > Special access > Battery optimization > All apps > WhatsApp > select Don't optimize. But then it may use more battery. (screenshot)

Please report back if you fix your notification problem or not. :cool:

***

Battery Charging LED Notification

Thanks :good: :cool: for reporting back.

You are saying that the notification LED does not work when charging the S5 turned off, correct?

If so that's like in the previous 16.0 builds & was added to the 16.0 2019-02-09 bug report. Also if you charge to 100% the S5 turned on, disconnect & reboot if will show 92% on the Status bar.

***

Trimming Huge Quotes

Could you please do me a favor & Edit your post > Advanced & trim the huge quote & do not forget to include [/QUOTE] at the end of the quote as without it, it breaks the quote box & it's link like this for example without the space before ]:
[Samsung Galaxy S 5 Unified Development] mx-5driver:
Hi Folks,

May I please ask what the current Development Status is with this ROM ?

The "What's not working List" in the OP-Thread appears to be empty - does it really mean - no Issues left ?

In Addition what about the Plans & Efforts in getting the ROM into official Status ?

Please excuse my Questions, but the OP-Thread doesn't give much Indication about how mature that ROM currently is.

I am just wondering whether the ROM - although not official yet - may be stable enough to be used as a daily Driver, that I could install it on my Wife's Phone ?
[Samsung Galaxy S 5 Unified Development] kurtn:
Scroll up a few posts for a bug list. I would not install current pie on someone else's phone. As soon as this one gets official, updates of the unofficial ROM will stop and you do all the work again.

Install official Oreo and you will get an easy route to upgrade to pie as soon as that goes official. In the mean time you get Oreo updates.
[Samsung Galaxy S 5 Unified Development] Ibuprophen:
I just wanted to let you all know that the OpenGApps (via Website, Github and Official App) is currently offline.

This was actually an unexpected find... :eek:

I had looked into the following Github message from the Repositories that only have the OpenGApps builds located within them...

View attachment 4703085

... And I did notice that they "Technically" did violate 2 of the "GitHub Terms of Service" and 1 of the "File and repository size limitations" outlined as well.

I'm sure that they are either trying to appeal the Github decision, working on another solution within Github OR in search of an alternative repository host.

Yes, their website accesses the downloads from those areas on Github as well as the same with their app using the Github API.

Let's just be patient with the OpenGApps Team and hopefully an announcement soon.

What a bummer... :(

UPDATE: They are currently working on the issue.

Just keep in mind that, though this issue may reside in Github, remember that BOTH their Website AND Official App does obtain the builds from their Github Repository (Github Directly as well as using the Github API.

Let's (patiently) keep our fingers crossed for a quick resolution. :)

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Enigma Machine {aenigma = Latin for "Riddle"}.
[Samsung Galaxy S 5 Unified Development] curiousrom:
Open GApps Downloads Down - Mirrors - Checking MD5

Edit: All builds of 9 February 2019 are accessible @ the present: https://opengapps.org/

***

Thanks for the pointer. :good::cool:

Actually it's the Open GApps downloads Repo which is offline @ the present (for example Open GApps Pico ARM 9.0) but the Open GApps Wiki & issues is up:

Open GApps Package Comparison

The downloads offline issue: Access to Repo #719

There is no official Open GApps downloads mirror @ the present so I uploaded the Open GApps Pico I am using @ the present here: open_gapps-arm-9.0-pico-20190209.

The folder includes open_gapps-arm-9.0-pico-20190209_zip_md5.txt so you can use a Hash checker or Hash calculator to check the integrity of the downloaded file with MD5.

For example Hash Checker for Windows (screenshot) or Hash Calc (Checksum Utility) for Android.

View attachment 4703240

BTW I had several corrupted downloads from Open GApps as seen in the second screenshot that Windows 10 reported as completed so I always check the MD5 to avoid installation errors & boot loops.

View attachment 4703242

[MENTION=2010892]Nezorflame[/MENTION] posted this in the Open GApps thread:

Edit 2: @ the present in > builds by nezorflame / opengapps / arm / 9.0 you can find a backup of all Open GApps ARM 9.0 builds 2019-02-09 (click on "i" to get the MD5 & SHA1 hash).

Note: Aroma does NOT work on the S5 klte + variants. I tested it myself. See Aroma Package > Issues

You can use older Open GApps packages (not too old!) & the apps & Play Store should update themselves after you log into your Google account.

***