LineageOS 16.0 Android 9 for GT-N8000 GT-N8010 GT-N8013 GT-N8020 FINAL VERSION EOL

[html6405]

For RAM it's probably better to tweak LMK, because Z-RAM kills performance.

I'm with you on that, you know what, I will remove the swap on my device and test it with high RAM consuming apps etc.
If it will pass, I will remove it for all.
I just have to take care whats best for all users.

 

[FanboyStudios]

I had the best stability with pegagsusq in my tests.

I had a really bad battery experience with ondemand, but everybody can change the default governour with kernel aduiator for example.

This is why I've set the value to 16000 MHz.

I had this in the early stages, but people wanted that I unlock higher frequencies.
Some devices run more stable with higher values, some not, I wouldn't recommend it.

Well, people claimed because of running out of RAM and I had many last_kmsg's because of that, it was necessary, maybe not for everybody, but for most.
Maybe we would be safe if I set the device to low_ram, but then some functions would be missing like pip,
multiuser support etc.
It's not easy to make a ROM perfect for everybody .

For this you will have to modify the ramdisk and delete

swapon_all /fstab.smdk4x12

in the init.target.rc.

Also, you could delete the
/dev/block/zram0

line in the fstab.

Modifying these files in FX File Manager with root did not work.
The ****ty settings return upon reboot.


Having to fork the ROM to fix it would suck on my 3 mbps or worse internet.

 

[html6405]

Modifying these files in FX File Manager with root did not work.

Well because you have to modify the ramdisk like I've told you, every modification you do in /
isn't permanent.

 

[html6405]

I've tested the device now without swap and if I filled the RAM up, it become partly unresponsive.
As a workaround, I've set the swappiness to the minimum, doesn't look so bad with that.

 

[FanboyStudios]

RAM usage is very low, but my device is almost always unresponsive with Z-RAM enabled, 100 swapiness, pegasusq. CPU is often at high usage as well. The worst stutters occur when attempting to switch apps. Battery drains pretty quick too.

With swapiness at 20, it's much more responsive... but still lags and stutters a lot, and that's also with the performance governor and deadline set instead of cfq (cfq is fine but i prefer deadline, since it gives more performance), and a more aggressive LMK.

Setting LMK more aggressive keeps the RAM from filling up as much, and also keeps more resources freed up for the CPU. Less programs running, less CPU usage.

Pretty much any device would become somewhat unresponsive if the RAM is filled, but having to constantly compress and decompress software (especially with an older weaker CPU like we have) will result in more stutters, even in general use.

 

[FanboyStudios]

The whole job of LMK is to keep the RAM from filling up. I mean it's literally called the Low RAM Killer.

With this properly set, we shouldn't run out of RAM so easily... and we won't need Z-RAM.


I have another device that has 2 GB of RAM, a Samsung Galaxy S5 Sport, and it runs well without Z-RAM.

 

[FanboyStudios]

My Samsung Galaxy S5 Sport's RAM usage for example.

Higher, but still plenty of free RAM.

 

[FanboyStudios]

 

[FanboyStudios]

Modified my boot image. Much better performance. No RAM issues even without Z-RAM!

Vivaldi browser with a few tabs, Blackplayer EX playing music, and playing Sky Gamblers Storm Raiders running while recording the screen in 360p. Not exactly a light workload... but it works.

 

[FanboyStudios]

If anyone else wants to try my modified BOOT image, you can find it in this post.

Make a copy of your old BOOT, and paste the modified one in /dev/block/platform/dw_mmc/by-name/BOOT
remove the extension, then reboot.

Performance Governor as default and no Z-RAM.

 

[gtrs36]

When im installing play store or Gapps its force close.
why?

 

[html6405]

When im installing play store or Gapps its force close.
why?

Could you explain more detailed what have you done?

 

[gtrs36]

hello friend,
i installed "twrp-3.5.0_9-0-n8000.img" with odin, then facotry reset with your insturoduction install "lineage-16.0-20211007-HTML6405-n8000" and Gapps "open_gapps-arm-9.0-pico-20211028" and i got google play force close.
im triyed to insall Gmicro and apk of google strore and its same..

 

[html6405]

hello friend,
i installed "twrp-3.5.0_9-0-n8000.img" with odin, then facotry reset with your insturoduction install "lineage-16.0-20211007-HTML6405-n8000" and Gapps "open_gapps-arm-9.0-pico-20211028" and i got google play force close.
im triyed to insall Gmicro and apk of google strore and its same..

Restart from zero (do also the wipes) and try an older gapps package, some people reported problems with the most recent version.

 

[kingdba]

The system has been successfully accessed. It works well. How can I obtain the root permission?

 

[html6405]

The system has been successfully accessed. It works well. How can I obtain the root permission?

Download magisk.apk and flash it in TWRP.

 

[raichea]

I've been running this firmware for a few weeks now and it works very well. There is one issue that I keep running into. I use the tablet for music and use a Bluetooth page turning pedal that sends keystrokes when a button is pressed. It pairs fine and turns the pages in my music app as expected. After a music session (often two or more hours) I turn the pedal off and recharge the tablet.

When I next go to use the pedal, the tablet claims the pedal is connected but keystrokes aren't reaching the app. I have to forget the pedal and pair again to get things working. With the old stock (4.4.2) firmware, the pedal reconnected correctly each time.

Any thoughts?

 

[html6405]

Any thoughts?

Hmm, disable / enable bluetoot or the pedal doesn't change anything?
Does it also not work if you close the app in the background and reopen it?

 

[raichea]

I tried all of those before I resorted to forgetting the device and repairing. Just to check, I tried these ideas again but no change.

One thing I noticed is that, even though the tablet says the pedal is connected, the two little dots that usually appear one each side of the BT symbol when a device is connected are not displayed. If I forget and repair, the dots appear as expected. After disconnecting by either turning the pedal or the BT off, it's back in the state where it says it's connected but isn't really.

 

[html6405]

If I forget and repair, the dots appear as expected. After disconnecting by either turning the pedal or the BT off, it's back in the state where it says it's connected but isn't really.

Hmm ok, I will try to check if my device is reconnecting BT devices and maybe I can find the reason.