yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] fipsy:
Smile! I think only someone like haggertk or Lord Boeffla perhaps also fbs, who has a deep insight into the source code, can really do something useful. We can only determine where the error is and how it is reproducible.

---------- Post added at 11:09 PM ---------- Previous post was at 10:51 PM ----------

As MTP is based on the content of the media provider, you have to manually initiate a media scan (via shell, script or Boeffla Config) after every copy or delete. When the scan has finished, everything is synchronized again:

am broadcast -a android.intent.action.MEDIA_MOUNTED -d file:///sdcard
[Samsung Galaxy S 5 Unified Development] j1gga84:
Anybody running latest LOS has the problem with apk files and greyed out install button?

That means if you want to install an app manually (for example from apkmirror.com) it is not possible to install it immediately. The install button is greyed out and you have to turn off the screen and turn it on again, after that the installation works without any issues.

Some users have this problem on ResurrectionRemix, that is build on latest LOS commits, so I ask myself if this was also observed in latest LOS build.

This issue does not only occur on klte device.

Regards

Sent from my SM-G900F with Tapatalk
[Samsung Galaxy S 5 Unified Development] fipsy:
If I tap in LOS filemanager on an APK file I get the normal dialog with "abort" and "install". So everything is okay. But I use the Boeffla Kernel Mod from fbs with latest LOS from October 4th.
[Samsung Galaxy S 5 Unified Development] Amirk365:
Used the latest on KLTEVZW and didn't have that error. Due to battery drain I changed back to CM13. I think I will give up on AOSP until I can muster a new phone. Great job by the devs though.
[Samsung Galaxy S 5 Unified Development] haggertk:
Don't worry about it, it's disabled, at least for now: https://review.lineageos.org/192587
[Samsung Galaxy S 5 Unified Development] fipsy:
A wise decision! Apart from slight speed advantages, nobody could explain to me what the advantages of sdcardfs are for the normal user. For me it looks more like a weirdness from Google, in order to further restrict the possibilities for users.
[Samsung Galaxy S 5 Unified Development] revjamescarver:
That works for now.

Back in the day when I was writing code for microcontrollers we would run the code exhaustively using emulator hardware where we could see the code as it was executed line by line and see all the system calls and functions being called as it happened, with hex code and basic assembly a lot of time that was the only way to catch some of the subtle logic errors that would crop up, took a bit of time so if we want sdcardfs to work it's going to take patience and probably a lot of coffee and coding time
[Samsung Galaxy S 5 Unified Development] fipsy:
You always have to keep in mind that Google sets the direction for Android. All the others are just working after them. I doubt that anyone at Google is really interested in a fairly flawless system. It's about having a product with which you can quickly gather a lot of data and earn a lot of money and which is just as good that the normal users use it. No more and no less. It doesn't even have to be nearly perfect as long as there is no competitor that is much better. Something like diligence, programmers' honor or perfectionism are completely foreign words in companies like Google, Apple or Microsoft. As long as it's going on somehow. The overview has already been lost for a long time anyway.
[Samsung Galaxy S 5 Unified Development] fbs:
for coincidence I was reading this article, it seemed interesting.. https://www.xda-developers.com/diving-into-sdcardfs-how-googles-fuse-replacement-will-reduce-io-overhead/

Can't we double check how sdcardfs was implemented in pure AOSP itself ? I doubt it still has any bugs. All newer devices are using it.. :confused:
[Samsung Galaxy S 5 Unified Development] fipsy:
Smile! This is exactly the article I came across yesterday. :cyclops: The essence of the article is that sdcardfs reduces the overhead and is therefore faster. But apart from that, I could not see any significant advantages. No doubt, if sdcardfs would work properly, it would be a step forward. Unfortunately, it doesn't.
[Samsung Galaxy S 5 Unified Development] revjamescarver:
Yep

Yeah I read that article, and from what it looks like Google just released what they had for us to debug for them, as always, using the ASOP to test code. They aren't even putting it into official kernels yet. (at least not enabling it)
[Samsung Galaxy S 5 Unified Development] haggertk:
Why ask if you can and just do? Pick your version of choice:

https://android.googlesource.com/kernel/common/+/android-3.10/fs/sdcardfs/

https://android.googlesource.com/kernel/common/+/android-3.18/fs/sdcardfs/

https://android.googlesource.com/kernel/common/+/android-4.4/fs/sdcardfs/

Oh, 3.4? That died with M.
[Samsung Galaxy S 5 Unified Development] 10goto10:
Solid explorer can act as an FTP server though (free add on from the play store.) I prefer it over samba because it's simpler.
[Samsung Galaxy S 5 Unified Development] fitittome:
'Files' app issue

Tell me about it! :)

There is one issue that is still outstanding. I think it is very important that the 'simple' LOS supplied apps should work reliably, out of the box. Although 'Files' is root deficient, it is perfectly sufficient for most users.

The thing is, it is emulating this sdcardfs problem perfectly on Fuse! It cost me so much time. :( Being as though you have sdcardfs disabled on your device can you just test that newly released and newly consumed space is not being reflected properly in the 'Files' app without sdcardfs being involved?

I have prepared a JIRA to submit when the next BUGBASH is opened, if you could glance over that too, I am getting punch drunk with it all!
[Samsung Galaxy S 5 Unified Development] revjamescarver:
Works under FUSE (sort of)

I spent most of the night moving files back and forth to make sure filer is working properly under FUSE, and it still doesn't report the right free space until you kill the app, wait a minute or two and then reopen it, settings and other files managers report the correct free space immediately. So there is a delay, but filer will still copy a file back to internal storage that is larger than what it reports as free space, so filer seems to have an error under FUSE in that it doesn't "show" it until you kill and restart it, but I have copied about 100 gig or so back and forth last night under FUSE and have not had to restart my phone at all. Both df - h and settings have consistently showed the proper values under FUSE through the night. So while filer has a delay in refreshing its display of those values and sometimes doesn't show the correct values until it decides it wants to, it's not a bug I can pick up with a logcat on this end, the major culprit is more on the end of that sdcardfs, but you are correct that filter has a bug in it somewhere, both under FUSE and sdcardfs
[Samsung Galaxy S 5 Unified Development] fitittome:
Geez... OK, so what I am saying is valid.

But

, if you wait a minute or two it sorts itself out. I wasn't waiting. :( I agree with df. I cannot see anything in logcat either, I guess because there just isn't an error condition... if it sorts itself out. I think I will reference your comments here in the JIRA.

The thing is, the 'Files' app is just the AOSP DocumentsUI. It was meant to be a super simple replacement for CMFM. https://review.lineageos.org/#/c/156347/ From what I can understand this bug seems to go right back to at least last December!

Thanks for helping. :)
[Samsung Galaxy S 5 Unified Development] revjamescarver:
Samsung

Samsung has been using sdcardfs for several years in their kernels, Google got it from them to begin with, sdcardfs is in the Android O kernel, but I think that it's implementation in our kernel is problematic at best.

To quote the article,

"Some users are expecting to see these changes officially implemented in Android 8, but it’s possible for any future OTA on a Pixel device to bring the Linux kernel version 4.1 that Google has been working on."
[Samsung Galaxy S 5 Unified Development] fipsy:
I can't reproduce this with the LOS file manager. For me, the free memory space is always shown wrong. Even if I've waited ten minutes. Also, quitting the file manager with a task killer didn't work! Only after a reboot the free disk space was accurate again. So I think it's more of a bug in the file manager than in the file system.

Another thing: I formatted my external SD card a few days ago freshly with exFAT. Since then I haven't had any crashes, reboots or other unusual things. Nevertheless, a check of the file system on my PC with Windows resulted in errors on the SD card and 5 "lost files" with more than 1 GB of "lost space". This suggests that the implementation of exFAT also has fundamental errors. The whole file system seems more than doubtful and faulty to me.

But not for me! I can wait for an hour without any success. What's your Filemanager Version (DocumentsUI)? Mine is 7.1.2. Which is actually only the version number of Android. But I wonder if there are different versions of the file manager?
[Samsung Galaxy S 5 Unified Development] revjamescarver:
Kernel version

I'm running the latest lineage build and kernel is still 3.4.113, so 3.4 is still not dead lol. Just kidding, thanks for your hard work and time spent on this project

---------- Post added at 10:11 AM ---------- Previous post was at 09:49 AM ----------

I'm running the same version, the file Manger just does it when it feels like it, I killed it over and over and it shows the same wrong values, work on something else for a while and come back to it and sometimes it shows T the correct values, sometimes not, but Ali the other file manager apps I have installed are always showing the correct values, a definite bug somewhere in the filer app with that.
[Samsung Galaxy S 5 Unified Development] fitittome:
Umm, I'm not seeing this either, I've waited a looonnngg time. I can only get it to report the correct space after a reboot. Maybe after a dismount/mount if I were testing an SD-Card but this is on internal so cannot do that.
[Samsung Galaxy S 5 Unified Development] fipsy:
Exactly the same here. Had no success even if waiting a VERY long time. Except after rebooting...

It's possible to remount the internal sdcard:

mount -o remount /mnt/runtime/default/emulated
mount -o remount /storage/emulated
[Samsung Galaxy S 5 Unified Development] revjamescarver:
Try this

It does the same thing on me most of the time, one thing I did notice was that if I closed filer (showing the wrong values) and then opened ES file explorer, went back to the builtin file app, it magically showed the correct values. I tried this same thing with a couple other file managers and got the same results, so there is definitely a bug in filer somewhere, but logcat doesn't show me anything.
[Samsung Galaxy S 5 Unified Development] fitittome:
Ah, that I can understand. 3rd party apps must do their own thing to force a refresh. Its probably something about this sort of process that's either missing or broken in 'Files'
[Samsung Galaxy S 5 Unified Development] DragonQ:
I think I found a bug in profiles - can someone else check this for me to confirm? The problem is that I can set the ring mode to "mute" via a profile but a profile that should set it back to "normal" doesn't actually work, meaning my phone stays on "Do not disturb - alarms only" mode unless I manually turn it off.

This definitely used to work but I am not sure when. I'm still running 20/09.
[Samsung Galaxy S 5 Unified Development] PorchSong:
I get misreporting with most file explorers but total commander seems to handle better than most. It usually reports size properly after moving/deleting files and caches. Usually only have to hit the home icon.

Just my observation.
[Samsung Galaxy S 5 Unified Development] fipsy:
Even with sdcardfs? It didn't work for me.
[Samsung Galaxy S 5 Unified Development] dezzo77:
To anyone here intimately familiar with the hardware capacitive button settings in Lineage 14, could you please verify something for me?

My S5 has defective capactitive buttons, so I need to disable them and use on-screen Navbar instead.

Using Resurrection Remix, I can do the following specific config:

- Enable on-screen Navbar

- Disable hardware Back/Recents buttons by setting "no action"

- Disable hardware button backlight

- Disable hardware button vibration

- Keep Home button enabled for wakeup device

When I attempted this on LineageOS 14 some months ago, I recall one of the above not being possible leaving me with only a partial fix... but I can't remember which part didn't work, because faulty brain.

I also recall I tried editing build.prop to enable Navbar, change button settings etc. but none of it worked and countless hours were wasted trying.

Is this config now possible with native settings in the more recent Lineage builds?
[Samsung Galaxy S 5 Unified Development] Bleiz:
Hey guys, after some time on stock ROM, I want to flash this ROM. Could someone be kind to list me some of known bugs, big and small, doesn't matter, I have read last 20-25 pages, including main ofc. but I want to hear from people who use it. Thanks in advance.
[Samsung Galaxy S 5 Unified Development] Immortal0907:
Im using it normally, I use instagram, few chatting apps, I play some game, listen to music... No problems for me. Last 20 pages are about mostly low memory killer which is problem to some people that are more advanced users but if you use your phone for everyday stuff like I do, you have nothing to worry about... If youre having trouble installing twrp and this rom check out my signature you have tutorials on my channel
[Samsung Galaxy S 5 Unified Development] fitittome:
It's great for day to day, not really any problems. Ignore the last 20 pages it is not representative! Besides, the S5 is the only LOS phone powered by hot air! lol. :)

edit: One thing though, I suppose it depends of the variant. I have noticed that locked Verizon bootloaders and oddities with Sprint seem to throw up few issues for people when they first install. But, it always worth remembering there are 36,000 active installs of klte vs. 2300 kltspr, 2000 klteduos and a smattering of the others. https://stats.lineageos.org/

---------- Post added at 12:25 PM ---------- Previous post was at 11:33 AM ----------

Not an option on klte without editing the build.prop file directly. How far you will get after doing that I am not sure.

---------- Post added at 12:42 PM ---------- Previous post was at 12:25 PM ----------

Umm, same on 04OCT. That was confusing to test! But moving from a profile where mute was confirmed and tested to a new user the phone remained muted despite the ringer volume set to halfway. You will need to establish when it worked, if it was recent you can file a Regression otherwise wait for a Bugbash. https://wiki.lineageos.org/bugreport-howto.html

edit:Curiously, when I came to delete the test user, I noticed an option to turn their phone calls & SMS on! It seemed to be defaulted to off. Umm. I think you may need to investigate a bit further yourself!
[Samsung Galaxy S 5 Unified Development] fipsy:
Why don't you repair those buttons? They only cost a few bucks. ;)
[Samsung Galaxy S 5 Unified Development] Pally01:
True the parts are cheap. However the display needs to be removed and that is a risky procedure. I have repaired lots of S5's and it is all-too-easy to break the display.
[Samsung Galaxy S 5 Unified Development] fipsy:
If you do it carefully, it works. For example, with a playing card. You just have to be careful not to damage the ribbon cables. I find it rather difficult to fix the display properly. The adhesive masks you can buy are not really good.
[Samsung Galaxy S 5 Unified Development] fitittome:
Excuse me that's bollocks. I have the proper machine to do that and the proper molybdenum wire and it is 50:50 at best. You are better off with one of these It is virtually a complete unit, then just transfer the motherboard over. You end up with a brand new case and become one of the privileged few who has a functional USB cover! :cool:

edit: my bad I thought you were talking glass replacement with a playing card...... this won't fix 'broken' capactitive buttons!
[Samsung Galaxy S 5 Unified Development] fipsy:
I've never had any problems removing the display glass. I haven't broken a single one. Even without any machine. If I buy the display glass in England, I'll be fine. Because the pound is practically worth nothing anymore in the EU or the US. But if I buy it in other countries, I can also buy a used S5. That doesn't cost much more on eBay than a display glass.

The (new!) playing card is well suited to detach the display glass from the frame. They are thin, soft and flexible, yet stable. Often they are also made of plastic and no longer of paper. If you have a preheater or hot-air hairdryer, you can also heat the display glass very carefully to about 80-100°C. That makes things easier. Then the glass almost drops off on its own. This is the prerequisite for replacing the capacitive buttons that are glued to the display glass.
[Samsung Galaxy S 5 Unified Development] fitittome:
:) its my fault, I was talking about separating the glass from the LCD panel! Often it is just the front most glass that cracks, not the LCD panel bonded to it. My bad. There are numerous youtube videos about it! We were at cross purposes!
[Samsung Galaxy S 5 Unified Development] SalsifiPourri:
ui
[Samsung Galaxy S 5 Unified Development] revjamescarver:
Great for day to day use

I use the hell out of it trying to stress the system and find the bugs, and aside from the bugs with the low memory killer, scardfs, and the builtin file manager not showing the correct values on free space, the rom works great. Phone, messaging, Bluetooth, it all works as it should. For 99.9% of users I would say that this rom is great for daily use. If you are a "power user" I would suggest installing the su addon for root so you can use kernel auditor to disable sdcardfs and the adaptive low memory killer, and definitely install a different file manager.

These guys put a ton of work into this rom and it shows, boots fast, smooth, definitely recommended

EDIT:

The newest build is supposed to have sdcardfs and AMLK disabled in the rom so you shouldn't have to be concerned with that, enjoy the rom
[Samsung Galaxy S 5 Unified Development] haggertk:
As an aside almk was not the cause of the problems being exhibited. It will probably return... As will sdcardfs.
[Samsung Galaxy S 5 Unified Development] fipsy:
I understand. :) I never tried to separate the glass from the touch panel. That would have been too dangerous for me. But if the glass has already been broken it doesn't really matter what happens to the glass. I would also be concerned because the new glass must be attached with a UV glue. But the glass itself ist really cheap, that's right.

---------- Post added at 05:25 PM ---------- Previous post was at 05:20 PM ----------

I would like to add that it can be useful to install the Boeffla Kernel Mod from fbs. At least if you have any problems with killed apps.

---------- Post added at 05:31 PM ---------- Previous post was at 05:25 PM ----------

You mean the missing consideration of zcache in the lowmemorykiller may have been responsible for the LMK problems? (https://review.lineageos.org/#/c/192510/)
[Samsung Galaxy S 5 Unified Development] haggertk:
Yes. That was the only questionable difference (others were from Google's "recommend" kernel/common) between the old and new kernel.

Not accounting for the fact that we have extra zcache pages quite well explains the seeming return to early 2016 time frame memory management.
[Samsung Galaxy S 5 Unified Development] fitittome:
Yhea, its crusifiying me. The mother-in-law is visiting twice a year now. :(
[Samsung Galaxy S 5 Unified Development] Pally01:
Been there, done that many times. I use good quality playing cards (stiffer) to remove the display from the phone and also to remove the glass from the digitizer.

Patience, a heat gun and infra-red thermometer are what I consider "essential" in the process if seperating glass from digitizer. There are many different tweaks to the process; some use wire instead of cards; some use a hair dryer instead of heat gun etc etc etc. At the end of the day so to speak, it is a risky procedure in my experience.

Using LOCA to adhere new glass to the digitizer is also an art form in order to become proficient. I have done enough S3's, S4's and S5's that I would consider myself knowledgeable (NOT a pro though).
[Samsung Galaxy S 5 Unified Development] fipsy:
Laugh! Where does she come from?
[Samsung Galaxy S 5 Unified Development] fitittome:
Well just thrashing the 11OCT nightly. Using the RAM Fill program mentioned, to crash the device, it yields a 266% improvement. I need to test a little more but I am seeing negligible difference between LMK - ALMK.

Edit: I am seeing that LMK is the better bet, ALMK only yields a 200% improvment., but I guess it may be better with a different type of test. Either way this is a huge step forward!

edit: off topic, fipsy, Texas, Republican. It's bad. Trust me.
[Samsung Galaxy S 5 Unified Development] revjamescarver:
I'm sure that is true

I'm sure that is true, however my app killing problems went away with ALMK disabled, and sdcardfs just needs some work to get it to work properly. Everything works great other than the issues with filer. As soon as I get a bigger drive for my Linux box I'll be able to spend a little of my excess of free time helping a little on some code

---------- Post added at 01:59 PM ---------- Previous post was at 01:34 PM ----------

I just installed it myself, along with today's build of gaps, after I get through with doctors appointments I'll be trying to kill it, haven't messed with it too much yet but I'll do the best I can to stress the hell out of it and see how it goes

---------- Post added at 02:01 PM ---------- Previous post was at 01:59 PM ----------

LOL, that is always bad news, ouch..
[Samsung Galaxy S 5 Unified Development] dezzo77:
That's what I was told when I took it to a repair shop. They said opening the screen quite often damages the screen.

In my case, the corner of the screen has lifted causing the button backlight to bleed into the screen area.

Why would Lineage not include a native option to enable the Navbar when they include the options to disable the hardware buttons? Odd choice. As I said, I tried the build.prop method and followed several guides and it did not work.

Looks like I'm stuck with Remix.
[Samsung Galaxy S 5 Unified Development] haggertk:
I have two commits I'm testing from a professional kernel developer (also an S5 user) that seem to resolve the free space leak. It's all due to whether access is against the parent or child filesystems... Changes directly to the parent aren't currently being relayed to the child. We have a test for this that doesn't involve relying on janky Android apps.
[Samsung Galaxy S 5 Unified Development] fipsy:
Well, I applied my heavy stress test to the new LOS version. With ALMK switched ON! Everything's all right! No apps are killed anymore. This confirms your opinion that it had nothing to do with the ALMK, but only with the consideration of zcache. And it also fits with my previous observation that the problem was completely independent of whether the ALMK was switched on or off. Therefore, a reactivation of the ALMK would have the green light from my side. :) It's really great that we finally found and fixed this very unpleasant bug! :good:

So there is only something left to do at the sdcardfs and the Lineage file manager in order to calculate and display the free disk space correctly.
[Samsung Galaxy S 5 Unified Development] jpereira23:
How is the camera?
[Samsung Galaxy S 5 Unified Development] fipsy:
I wouldn't make my decision dependent on the stock camera app. I always use Open Camera App and it works fine.