[ROM][9.0][UNOFFICIAL] [G800F/M/Y] LineageOS 16.0 [Beta] [16-12-2020]

[spookcity138]

Hi, I have the same problems. The phone slows down with every app I used, and was freezing in the end. After I detected, that it was fast again after closing the used apps, I activated “Don 't keep activities“ in the apps-section of the developer options and set the background limit to “2“. Seems to work so far.
The behaviour reminds me of problems I had with Linux with not enough Ram and little Swap-space. Just a suggestion...
I installed Matlog as recommended by spookcity and hope to get a useful log, if I get a freeze again.

Interesting,a log would indeed be helpful if at all possible. I can say that I did notice this a few times recently, but not nearly as bad as you've had. Perhaps I've made a mistake in pinning a few things into memory in the build. It could also be the fact that HW composition is broken. I'm not real sure. The symptoms do seem like a RAM issue as you said.
Since I last had this problem I decided to create a 250mb swap file to use. So far no issues, but we'll see. If I have it again I'll try to grab a log as well.

Sent from my SM-G800F using Tapatalk

 

[Brummschaedel]

Creating a swap file sounds interesting. Do you know a guide how to do it?

 

[spookcity138]

Creating a swap file sounds interesting. Do you know a guide how to do it?

Well, you can do it via the terminal, but that becomes a bit complicated. I recommend an app. I believe there's an app called swapper that was somewhat popular. I personally used apps2sd pro. It is not specifically for swap as the name implies, but has a lot of features. Creating a swap file being one of them. I have the paid version though. I'm not sure what the limitations are of the free version.
I really just wanted to try to use a swap file for a bit and see if this issue stopped so I could determine if the root cause was indeed a RAM issue. Although, as I said I've only had this problem a few times and not so severe.

Perhaps if you're able to create a swap file and test out as well we'll be able to determine if this is the cause.

Sent from my SM-G800F using Tapatalk

 

[Brummschaedel]

Thanks for the info. I'll try.

 

[Brummschaedel]

Thanks for the info. I'll try.

Okay, maybe I got something helpful.
I removed the options I chose in the "developer settings" and created a swap-file with swapper this morning. Then I began to play a game that tends to make my phone freeze. Went very smooth in the beginning, but after some time it became really slow and I switched to Matlog (needed about 15 seconds) and saved the log.
As the file was to big to upload, I removed most of it, hope I give you the part that is needed. I saved the whole file for sure.
Thanks in advance for looking into it!

 

[spookcity138]

Okay, maybe I got something helpful.
I removed the options I chose in the "developer settings" and created a swap-file with swapper this morning. Then I began to play a game that tends to make my phone freeze. Went very smooth in the beginning, but after some time it became really slow and I switched to Matlog (needed about 15 seconds) and saved the log.
As the file was to big to upload, I removed most of it, hope I give you the part that is needed. I saved the whole file for sure.
Thanks in advance for looking into it!

Thanks a lot for the log! After just a quick glance and some quick thoughts: I see all of the looper warnings and I believe ( I could be very wrong though) that this partly has to do with touch events,screen redraws etc. This leads to to think that this is due to our broken HW composition. Therefore,everything is relying on our GPU...which like our phone is rather old at this point. This especially makes sense when it comes to playing games. Although,I rarely play any and have also had this issue. Perhaps its a combination of low memory and this.

Sadly,as far as the HW composition issue is concerned I am really unsure of how to solve this at this point. I keep hoping it will somehow be resolved within the LOS sources at some point,but in my searching I've not found any other phones with this problem. That leads me to believe that the only fix may be to hex edit one of our proprietary display blobs. This is something that I would really need to look into. I will build without the patch to disable HWC soon and grab some fresh logs and see if I have a better understanding of whats happening. I will probably also revert some of services I pinned into memory during last build (surfaceflinger,dialer,SystemUI) This also may just be too much to ask from our old phone with 1.5gb of memory.

 

[mongo0]

I also found that additional swap improved performance and reaction time a bit.
I made a swap partition on the external_sd and I also switched the zswap compressor from lz0 to lz4. Also, I set vm.swapppiness to 10 and vm.vfs_cache_pressure=50. However, zswap.zpool (CONFIG_ZPOOL) does not seem to exist on this kernel...

I think it is doing at least some good

 

[Ti64CLi++]

When you say that SELinux isn't working, does that mean that it's permissive or enforcing, or none of them?

 

[spookcity138]

I also found that additional swap improved performance and reaction time a bit.
I made a swap partition on the external_sd and I also switched the zswap compressor from lz0 to lz4. Also, I set vm.swapppiness to 10 and vm.vfs_cache_pressure=50. However, zswap.zpool (CONFIG_ZPOOL) does not seem to exist on this kernel...

I think it is doing at least some good

Thanks for the info. There are many commits needed in order for all of this (zram/zswap) to work correctly on our device. I Have been looking into backporting ZRAM/ZSMALLOC from the 3.10 kernel as they have done on the KLTE kernel. Sadly,this is not as easy as just cherry picking the needed commits. I will continue to look into it.

When you say that SELinux isn't working, does that mean that it's permissive or enforcing, or none of them?

It is permissive and switching it to enforcing will break many things on the ROM.

 

[Brummschaedel]

Hi! I also made a Swap partition on SD-card and had no freeze since then. It's okay, but surely it was even better, if the issue could be fixed. Thanks for all your work!
The only thing that annoyed me the last two days is the laggy WIFI connection. Using the browser works, sometimes I have to wait for some seconds, but then the data comes in. But with other apps, especially the XDA-app, there's often no connection. I have to close the app, swipe it out of the recent apps, and reopen it. It does not happen on mobile data.
You had a boot.img to fix this. Was it included in the last build of the Rom? Or do I have to flash it seperetly?

 

[spookcity138]

Hi! I also made a Swap partition on SD-card and had no freeze since then. It's okay, but surely it was even better, if the issue could be fixed. Thanks for all your work!
The only thing that annoyed me the last two days is the laggy WIFI connection. Using the browser works, sometimes I have to wait for some seconds, but then the data comes in. But with other apps, especially the XDA-app, there's often no connection. I have to close the app, swipe it out of the recent apps, and reopen it. It does not happen on mobile data.
You had a boot.img to fix this. Was it included in the last build of the Rom? Or do I have to flash it seperetly?

The boot.img I released a bit ago was to solve video playback issues in whatsapp,Instagram and Facebook (which in my testing has worked) Your WiFi issue seems annoying indeed. My WiFi is very stable so its weird. Perhaps you can provide me with a log of this if you are able and I will look it over.

 

[Brummschaedel]

The boot.img I released a bit ago was to solve video playback issues in whatsapp,Instagram and Facebook (which in my testing has worked) Your WiFi issue seems annoying indeed. My WiFi is very stable so its weird. Perhaps you can provide me with a log of this if you are able and I will look it over.

Oh sorry, maybe I should re-read the old posts before writing.
So for me video Playback in Whatsapp-posts works. I don't do much with Wathsapp, so I can't say, whether it did so with elder versions of the Rom, but now it sure does.
So here is a log of a failed attempt to receive data with the XDA-app over WIFI-connection. One minute later I got a connection via LTE (not logged).
And a little suggestion: You once created a kernel for lineage 14 that could overclock the CPU. Would it be useful to integrate it into the ROM, leaving 1.4 M as the standard?

 

[Ti64CLi++]

If it doesn't bother you, could you tell me which part of which file is for selinux? I'd try perhaps to fix this bug by myself, and learn how it works

 

[spookcity138]

Oh sorry, maybe I should re-read the old posts before writing.
So for me video Playback in Whatsapp-posts works. I don't do much with Wathsapp, so I can't say, whether it did so with elder versions of the Rom, but now it sure does.
So here is a log of a failed attempt to receive data with the XDA-app over WIFI-connection. One minute later I got a connection via LTE (not logged).
And a little suggestion: You once created a kernel for lineage 14 that could overclock the CPU. Would it be useful to integrate it into the ROM, leaving 1.4 M as the standard?

Thanks for the log. I will look it over when I have the time. I have moved the android.hardware.wifi hidl back to version 1.0. I kinda dont think this will solve the issue,but it should at least kill some of the logcat spam we are getting as newer version offer support for things we don't have.
AS far as OC the CPU. I have done this and used a version on this ROM. I am hesitant to just include it in the ROM as some people had issues with it before and I don't want confusion about what is ROM related and related to the OC. I don't really feel like creating a thread on here for a new kernel...At least not at this point. Perhaps in the future. Maybe I will release an OC'd version on github or something. I also don't just want to post it here and "muddy up" this thread with this.

If it doesn't bother you, could you tell me which part of which file is for selinux? I'd try perhaps to fix this bug by myself, and learn how it works

No bother,but sadly it is not just a file. Here's a Link all about this if you wish to look it over. It is a fairly time consuming process to get this all working. Especially if you are not very familiar with SELInux (like me)

 

[aelfinn]

Maybe I will release an OC'd version on github

I’d love to test that.

 

[spookcity138]

I’d love to test that.

Ask and you shall receive
It is fairly easy and straightforward to do,so it was no problem. Overclocked from 1.4 - 1.6. Also enable the lower frequencies 200 and 300 MHz for possible battery saving? You'll need to use kernel adiutor or similar if you don't wish for it to scale down this low. No other changes to the kernel. Please,no comments about the kernel in this thread. It will only confuse things. If you have a comment please do so Here

Download - 1.6 overclock

 

[Asgabat]

how to root?

 

[spookcity138]

how to root?

I use Magisk Works good. I haven't tried v 19.0. I've been using 18.1. It should probably work as well though. Just can't say for sure.

 

[liquidraver]

Anyone knows how to turn off Ambient display from ADB? In the ROM, when I tap on Ambient display settings, it's just force closes the settings.

 

[Eightball2]

First off: @spookcity138 thank you so much for still supporting this crappy old phone!

After sticking with lineage 13 or so for way too long and not really caring about my phone, I finally started flashing roms again when this thread came up.
With the first few releases I experienced the same issue with writing to sdcard that many people also reported here. The most annoying was WhatsApp not being able to download photos. Gladly this was fixed in the latest release!

Another issue that I kept stumbling upon and took me some googling to figure out was the Samsung Smart Cover (or: flip cover). I'm not using the actual cover, but the setting is enabled by default, which made my phone randomly enter some kind of locked state with the display half blue and only the time displayed. I couldn't do anything but restarting the phone. The solution for this is to go to Settings -> Connected devices -> Connection preferences -> Smart cover and just disable it.

I was kinda happy with my phone, but sometimes had huge performance issues that are also reported in more recent posts of this thread. I could counter the lockups by setting the performance governor in Kernel Adiutor, but this was not a long-term solution. Also there was no recent kernel with different governors or overclocking available that I wanted to try.
Finally I was also able to solve this problem, and here is how. In Magisk Manager I downloaded and installed LKT ('Legendary Kernel Tweaks'). The phone's CPU is not listed in the compatibility list, but nevertheless it works fine for me. In LKT I set the 'Balanced' profile, which so far works very well for me. I haven't tested for too long now, but battery life seems still quite fine and the phone is running reasonably smooth. Maybe one could even go for 'Performance' mode.

With these minor problems solved, I would like to repeat how overall happy I am now with this rom, smoothly running the latest Android on an I-don't-even-know-how-old phone and want to thank @spookcity138 again for the effort! I will see if I can find someone with a Paypal account...