• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

LineageOS 16.0 Android 9 for GT-N5100 GT-N5110 GT-N5120 STABLE

Search This thread

html6405

Recognized Developer
Jan 15, 2016
1,367
1,240
Update 08.09.2021:
  • Synced with LineageOS sources
  • Some Kernel work
  • Fixed aptX
  • Updated the boot picture, if you don't like it, reboot into recovery and type the following command:
    • adb shell (or use TWRP's terminal)
    • . /data/param_restore.sh
    • reboot
  • Uploaded a prepared package to build your own boot picture
 
Last edited:

cetincelik

New member
Dec 24, 2008
3
0
Hello, I really enjoy the ROM. I haven't use my N5105 for years, but now i'm in love with it once again.

I have an issue though, I have a Samsung Galaxy Dock, and I would like to have an HDMI output via this dock. But unfortunately I couldn't get it. Is there any way to activate HDMI output? I'm sure port and USB is working, cause I managed to connect my keyboard with USB dongle to the deck , and it worked.
 

html6405

Recognized Developer
Jan 15, 2016
1,367
1,240
I have an issue though, I have a Samsung Galaxy Dock, and I would like to have an HDMI output via this dock. But unfortunately I couldn't get it. Is there any way to activate HDMI output? I'm sure port and USB is working, cause I managed to connect my keyboard with USB dongle to the deck , and it worked.
I'm sorry, this possibility is lost since android 7, wen can't use these old blobs anymore and Samsung won't publish the source code.
 
  • Like
Reactions: cetincelik

pohhendry

Member
Aug 23, 2021
5
2
Samsung Galaxy Tab A series
Thank you so much for bringing a 2nd life to our tablets! I enjoyed this rom a lot!

Recently I was trying to connect to bluetooth and realize that
I have an issue with bluetooth.

The bluetooth address is marked as "Unavailable"

The behavior when I try to enable it, it will turn on. When I try to scan and pair, it cannot find anything else.
After like 2 mins, it will switch off and try to switch on again.
Until I manually switch it off.
 

dovshan

Member
Sep 9, 2014
7
3
Hi
I'm using your Rom about 10 days in my N5100 tablet
I installed last update. 2021-09-08
I can say it's Excellent..

I found some problems and I think its better to mention them here
1.as you said Bluetooth head set not working in phone calls.. but in music player is ok
2.when device is off.. if connect charger ... screen shows charging battery but after turning off screen automatically, cant turn on it anymore to see charging status.
3.in recent apps menu clear all button is in the end of apps list.. it should be in the first of list not end!
4.the important problem is here. When I push the s-pen button it acts like back button.
And it make problem in apps like LectureNotes app that use button command for switching pen to eraser.
If there was a menu to set action for s-pen button command we could disable it or do other actions like capture and more...

And I have a question, how to enable external sdcard write access to some apps like camera or LectureNotes?( I rooted device using Magisk)
Thank you.
 
  • Like
Reactions: html6405

html6405

Recognized Developer
Jan 15, 2016
1,367
1,240
1.as you said Bluetooth head set not working in phone calls.. but in music player is ok
2.when device is off.. if connect charger ... screen shows charging battery but after turning off screen automatically, cant turn on it anymore to see charging status.
Ok this is known so far,
3.in recent apps menu clear all button is in the end of apps list.. it should be in the first of list not end!
This is lineage standard.
4.the important problem is here. When I push the s-pen button it acts like back button.
This was introduced by me years ago, I thought better we can use the button as a back event then if it's doing nothing.
I've also programmed the wake up event into the kernel.
But I was thinking about if I should programm a second double click gesture and maybe use this for the back event.
And I have a question, how to enable external sdcard write access to some apps like camera or LectureNotes?( I rooted device using Magisk)
Did you checked the permissions in the app settings?
 

dovshan

Member
Sep 9, 2014
7
3
Did you checked the permissions in the app settings?
Yes I checked no problem in internal memory using..and also no problem in sd/android/data/com.app.id directory..
The problem is like kitkat external sd rw problem..
Apps can't write data in custom directory..
I know It's android 5+ standard not to let apps use other directory's in sd card
In official rom 4.4.4 I fixed it using "Kitkat SDcard fix" app but in this version I can't find any fix for this.
 

dovshan

Member
Sep 9, 2014
7
3
This was introduced by me years ago, I thought better we can use the button as a back event then if it's doing nothing.
I've also programmed the wake up event into the kernel.
But I was thinking about if I should programm a second double click gesture and maybe use this for the back event.
For now I fixed it using Button remapper app to skip one click to back and added back action in double click(in my selected apps only).
 

dovshan

Member
Sep 9, 2014
7
3
I will change this in the Kernel and push a new update soon.
IMG_20210924_022501.jpg

I forgot to say this
When I enable Showing stylus icon in settings, the icon not shown in correct location.. as you see in picture icon is upper left of correct location.
 

html6405

Recognized Developer
Jan 15, 2016
1,367
1,240
View attachment 5417233
I forgot to say this
When I enable Showing stylus icon in settings, the icon not shown in correct location.. as you see in picture icon is upper left of correct location.
This is known, I don't know why for sure yet.
For example on the n80xx devices I'm using the same Kernel source and it's calculated correctly,
this has something todo with the display size im my opinion.
 
  • Like
Reactions: dovshan

mutonic

Member
Feb 17, 2012
31
9
Hi,
I'm allready using this rom for a while and I must say it is very stable and functionnal..
I would like to try either /e/ which is based on same version or LOS18 to update to android 11.
But I saw /e/ wasn't updated as much as this one, what would you recommand?
Is /e/ more degooglised than LOS?
 

html6405

Recognized Developer
Jan 15, 2016
1,367
1,240
Hi,
I'm allready using this rom for a while and I must say it is very stable and functionnal..
I would like to try either /e/ which is based on same version or LOS18 to update to android 11.
But I saw /e/ wasn't updated as much as this one, what would you recommand?
Is /e/ more degooglised than LOS?
/e/ is based on LOS 16 for these devices.
I would wait, because very soon I will publish the official builds.
 

html6405

Recognized Developer
Jan 15, 2016
1,367
1,240
Update 30.09.2021:
  • Introduced new PEN gesture, double click now became the back event, the short press gesture now can configured in the system settings. (This was also a problem for SPen command)
  • Disabled pmf in wpa_supplicant_overlay.conf
  • Fixed some selinux denials
  • Fixed power off charging
  • Created a fix if an app set's a video resolution higher than full HD.
  • Fixed new introduced charging bug
  • Security patch level 05.09.2021
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    Update 30.09.2021:
    • Introduced new PEN gesture, double click now became the back event, the short press gesture now can configured in the system settings. (This was also a problem for SPen command)
    • Disabled pmf in wpa_supplicant_overlay.conf
    • Fixed some selinux denials
    • Fixed power off charging
    • Created a fix if an app set's a video resolution higher than full HD.
    • Fixed new introduced charging bug
    • Security patch level 05.09.2021
    2
    Hi,
    I'm allready using this rom for a while and I must say it is very stable and functionnal..
    I would like to try either /e/ which is based on same version or LOS18 to update to android 11.
    But I saw /e/ wasn't updated as much as this one, what would you recommand?
    Is /e/ more degooglised than LOS?
    /e/ is based on LOS 16 for these devices.
    I would wait, because very soon I will publish the official builds.
    2
    Update 07.10.2021:
    • Fixed MTP connection for Windows.
    1
    Update 07.10.2021:
    • Fixed MTP connection for Windows.
    @html6405, running lineage-16.0-20211007-HTML6405-n5120.zip with complete fresh clean install (wiped everything, factory reset and formatted data).

    There are no gapps or any other sw loaded, just the rom image above. There is no sim inside this tablet. There's also no tombstone data files.

    Since this ANR repeats over and over, it make the UI sluggish at times. No rush to fix, but since it's a complete fresh install with everything reset and format data, it should be easy for you to reproduce?

    Bash:
      2212  10-09 20:30:02.338  2154  2154 W /system/bin/tombstoned: crash socket received short read of length 0 (expected 12)
      2213  10-09 20:30:02.351  2033  2033 I Zygote  : Process 5885 exited due to signal (9)
      2214  10-09 20:30:02.372  5906  5906 I chatty  : uid=1001(radio) com.android.phone expire 11 lines
      2215  10-09 20:30:20.825  5856  5856 I chatty  : uid=1001(radio) /vendor/bin/hw/rild expire 19 lines
      2216  10-09 20:30:22.513  2225  2240 I chatty  : uid=1000(system) ActivityManager expire 14 lines
      2217  10-09 20:30:22.517  2154  2154 I /system/bin/tombstoned: registered intercept for pid 5906 and type kDebuggerdJavaBacktrace
      2218  10-09 20:30:22.518  5906  5912 I chatty  : uid=1001(radio) com.android.phone expire 2 lines
      2219  10-09 20:30:22.845  2154  2154 I /system/bin/tombstoned: received crash request for pid 5906
      2220  10-09 20:30:22.845  2154  2154 I /system/bin/tombstoned: found intercept fd 512 for pid 5906 and type kDebuggerdJavaBacktrace
      2221  10-09 20:30:22.958  2154  2154 W /system/bin/tombstoned: crash socket received short read of length 0 (expected 12)
      2222  10-09 20:30:22.967  2033  2033 I Zygote  : Process 5906 exited due to signal (9)
      2223  10-09 20:30:22.985  5928  5928 I chatty  : uid=1001(radio) com.android.phone expire 24 lines
      2224  10-09 20:30:23.003  2225  2243 I chatty  : uid=1000(system) ActivityManager expire 16 lines
      2225  10-09 20:30:29.848  5855  5855 F libc    : Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x8 in tid 5855 (rild), pid 5855 (rild)
      2226  10-09 20:30:30.281  5951  5951 I chatty  : uid=1001(radio) /vendor/bin/hw/rild expire 1 line
      2227  10-09 20:30:30.531  5928  5928 W SystemConfig: No directory /product/etc/sysconfig, skipping
      2228  10-09 20:30:30.531  5928  5928 W SystemConfig: No directory /product/etc/permissions, skipping
      2229  10-09 20:30:30.540  5928  5941 I chatty  : uid=1001(radio) com.android.phone expire 1 line
      2230  10-09 20:30:30.545  2225  2327 D ConnectivityService: Got NetworkFactory Messenger for PhoneSwitcherNetworkRequstListener
      2231  10-09 20:30:30.570  2225  2327 D ConnectivityService: Got NetworkFactory Messenger for TelephonyNetworkFactory[0]
      2232  10-09 20:30:30.605  2225  2275 D BluetoothManagerService: Trying to bind to profile: 1, while Bluetooth was disabled
      2233  10-09 20:30:30.623  5928  5928 I TelecomFramework: TtyManager: updateUiTtyMode -1 -> 0
      2234  10-09 20:30:30.682  2225  2236 I WifiService: WifiService trying to set country code to 
      2235  10-09 20:30:30.683  2225  2236 I chatty  : uid=1000(system) Binder:2225_1 expire 11 lines
      2236  10-09 20:30:50.581  2225  2240 W ActivityManager: Timeout executing service: ServiceRecord{5e14238 u0 com.android.phone/.TelephonyDebugService}
      2237  10-09 20:30:50.683  2154  2154 I /system/bin/tombstoned: registered intercept for pid 5928 and type kDebuggerdJavaBacktrace
      2238  10-09 20:30:50.685  5928  5934 I chatty  : uid=1001(radio) com.android.phone expire 2 lines
      2239  10-09 20:30:51.137  2154  2154 I /system/bin/tombstoned: received crash request for pid 5928
      2240  10-09 20:30:51.137  2154  2154 I /system/bin/tombstoned: found intercept fd 512 for pid 5928 and type kDebuggerdJavaBacktrace
      2241  10-09 20:30:51.141  2225  2240 E ActivityManager: ANR in com.android.phone
      2242  10-09 20:30:51.141  2225  2240 E ActivityManager: PID: 5928
      2243  10-09 20:30:51.141  2225  2240 E ActivityManager: Reason: executing service com.android.phone/.TelephonyDebugService
      2244  10-09 20:30:51.141  2225  2240 E ActivityManager: Load: 0.0 / 0.0 / 0.0
      2245  10-09 20:30:51.141  2225  2240 E ActivityManager: CPU usage from 15277ms to 0ms ago (2021-10-09 20:30:35.313 to 2021-10-09 20:30:50.590):
      2246  10-09 20:30:51.141  2225  2240 E ActivityManager:   0.5% 2225/system_server: 0.1% user + 0.3% kernel / faults: 20 minor
      2247  10-09 20:30:51.141  2225  2240 E ActivityManager:   0.1% 4677/kworker/0:2: 0% user + 0.1% kernel
      2248  10-09 20:30:51.141  2225  2240 E ActivityManager:   0% 1166/mmcqd/0: 0% user + 0% kernel
      2249  10-09 20:30:51.141  2225  2240 E ActivityManager:   0% 1941/flush-179:0: 0% user + 0% kernel
      2250  10-09 20:30:51.141  2225  2240 E ActivityManager:   0% 1963/logd: 0% user + 0% kernel / faults: 1 minor
      2251  10-09 20:30:51.141  2225  2240 E ActivityManager:   0% 5951/rild: 0% user + 0% kernel
      2252  10-09 20:30:51.141  2225  2240 E ActivityManager: 0.7% TOTAL: 0.2% user + 0.4% kernel
      2253  10-09 20:30:51.141  2225  2240 E ActivityManager: CPU usage from 1931308ms to 1931308ms ago (1969-12-31 17:00:00.000 to 1969-12-31 17:00:00.000) with 0% awake:                                                                                                                                                   
      2254  10-09 20:30:51.141  2225  2240 E ActivityManager: 0% TOTAL: 0% user + 0% kernel
      2255  10-09 20:30:51.144  2225  2240 I ActivityManager: Killing 5928:com.android.phone/1001 (adj -800): bg anr

    Here's the frequency of the anr

    Bash:
    $ adb logcat -C | grep "ANR in com.android.phone"
    10-09 20:30:51.141  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:31:11.751  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:31:32.495  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:32:00.645  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:32:21.350  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:32:41.962  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:33:10.371  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:33:31.130  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:33:51.766  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:34:20.038  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:34:40.823  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:35:01.557  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:35:29.788  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:35:50.497  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:36:11.115  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:36:38.946  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:36:59.335  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:37:19.786  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:37:43.207  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:38:03.857  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:38:24.631  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:38:58.207  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:39:18.679  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:39:39.135  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:40:07.546  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:40:27.913  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:40:48.330  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:41:08.451  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:41:29.292  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:41:50.055  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:42:27.035  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:42:47.414  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:43:07.897  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:43:36.148  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:43:56.778  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:44:17.382  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:44:45.880  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:45:06.506  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:45:27.208  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:45:55.684  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:46:16.443  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:46:37.096  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:47:05.380  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:47:26.140  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:47:46.862  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:48:15.098  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:48:35.728  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:48:56.323  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:49:24.766  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:49:45.587  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:50:06.359  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:50:34.220  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:50:54.844  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:51:15.447  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:51:44.054  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:52:04.761  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:52:25.376  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:52:53.817  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:53:14.583  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:53:35.379  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:54:03.450  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:54:24.157  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:54:44.785  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:55:13.106  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:55:33.880  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:55:54.329  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:56:22.768  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:56:43.246  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:57:03.712  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:57:31.876  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:57:52.298  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:58:12.730  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:58:41.384  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:59:02.083  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:59:22.468  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 20:59:50.908  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 21:00:11.717  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 21:00:32.193  2225  2240 E ActivityManager: ANR in com.android.phone
    10-09 21:01:00.325  2225  2240 E ActivityManager: ANR in com.android.phone
    1
    For now I fixed it using Button remapper app to skip one click to back and added back action in double click(in my selected apps only).
    I will change this in the Kernel and push a new update soon.
  • 35
    Code:
    /*
    * Your warranty is now void.
    *
    * I am not responsible for bricked devices, dead SD cards,
    * thermonuclear war, or you getting fired because the alarm app failed. Please
    * do some research if you have any concerns about features included in this ROM
    * before flashing it! YOU are choosing to make these modifications, and if
    * you point the finger at me for messing up your device, I will laugh at you.
    *
    */


    Hi,

    here you can find my version for the n5120 on LineageOS 16.0.
    At first I want to thank @forkbomb444, @rINanDO, @ChronoMonochrome and all the others who are working on the exynos 4 devices, also big thanks to @prkfsz for donating me a n5120 and also the shipping cost.
    Also big thx to @cngbrick for donating a n5100.

    It already took me a few hundred hours and it will become more and more to support you with great updates.
    it's mostly based on my work on for the Samsung Galaxy Note 10.1 (GT-N80XX) devices.


    Here you can see how far everything is working:

    Boot
    Audio
    Bluetooth
    Graphics
    Main camera
    Wifi
    USB
    Video playback (HW/SW)
    OTA Updates
    RIL
    GPS, not sure if completely
    Tethering via USB, WIFI and Bluetooth
    consumerir transmitter
    Sensors
    • Bluetooth headset in a mobile call
    • Some apps because of decoding issues
    • GPS fix, but navigating is working fine
    • Maybe more
    If you are going to use Gapps,
    I recommend to use the pico package!
    https://opengapps.org/
    For the others, you can use microG if you want, I've enabled signature spoofing.

    If you want to pass the safety net check, root your device with magisk.

    Do you like my work?
    Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
    I'm doing this in my free time and it also costs a lot of money to buy hardware.
    donate

    You could use a gps.conf from https://app.box.com/s/w57s1v1n3hie7l5lk28i for your location and replace /system/etc/gps.conf.
    Or you try GPS Server Optimizer app for a faster 3D fix.
    For both methods you need root rights.
    If you plan to encrypt your device, the first step is to backup all your important stuff.

    Reboot into recovery and choose:

    Wipe->Advanced Wipe->Data (check)
    Choose "Repair or Change File System" and afterwards "Resize File System".
    After this step, choose Reboot System and you can start to encrypt your drive.
    If you can't find this option in the settings by your own, use the search function and type "encryption" and you can start.
    XDA:DevDB Information
    [ROM][9.x][N5100/N5110/N5120][STABLE] LineageOS 16.0, ROM for the Samsung Galaxy Note 8.0

    Contributors

    html6405
    Source Code: https://github.com/html6405

    ROM OS Version: 9.x Pie
    ROM Kernel: Linux 3.x
    ROM Firmware Required: TWRP 3.3.0
    Based On: LineageOS

    Version Information
    Status:
    Stable

    Created 2021-02-09
    Last Updated 2021-09-30
    9
    but I hope this gets fixed.
    I won't promise this, because it's really much work to write down all rules and test everything,
    but we will see.

    Like on my other android 9 roms the people wanted as fast as possible android 11, so it also depends on what all people want to have.
    - The ROM is signed with userdebug keys. This severely reduces security as well, allowing anyone to replace (update) system apps.
    We only can sign it as user build, when we have all selinux rules written, so it depends on point one ;).
    - Encryption did not work for me. The logcat says something along the lines "no space for crypto footer". This is a known problem and I am unsure if the ROM developer can do something about it. Would be nice if it " just works"
    Yes this could be, but I know how to fix this, made this already for the Note 10.1 devices working.
    - I dislike the inclusion of several non-lineage apps in the system. The inclusion of Magisk Manager is not useful, as you still have to flash the install zip, which will install Magisk Manager already. I distrust this "Via" web browser and see it as redundant, as the Lineage browser is included as well
    Magisk Manger is included, because we need Magisk root to pass the safetynet check, it's more as a pointer to show the people how to root.
    (There were hundred questions how to root on my other roms, they dont read the initial post...)

    If we will have selinux enforcing once, I will remove it.

    Via is included because of many complaints of the surfing speed with the jelly browser, maybe I will remove it, I will think about it.

    OpenCamera is included because the gCam (lineage camera) is crashing sometimes, there are still problems with the camera hal, had to overwork it completely to even get the main camera working.
    While no deal braker, I would focus on this phenomenon as well.
    Hmm ok, we could play around with the cpu govenour, but this will influence the battery time as well, but at first I have to fix many other problems.
    Lineage 18.0 / Android 11 ETA wen?
    Haha I know that very soon many people will ask.
    You all will make the choice if i should concentrate on security things or bring android 11 up,
    I exactly know how it runs because I've brought it already to the Samsung Galaxy Note 10.1 devices ;) (same chipset...).
    The firmware makes real fun, but believe me, LOS16.0 runs much more smooth.
    Anyway, I will bring it up sooner or later, for me is more important to provide you a stable LOS16.0.
    6
    Thousand thanks to @cngbrick, he donated a n5100 to facilitate my development on the 3G version! :love:
    6
    Update 10.08.2021:
    • Fixed some more selinux denials
    • Security bulletin 05.08.2021
    5
    Update 22.04.2021:
    • Implemented logic to show the correct SN of the device
    • Security patch level 05.04.2021 update
    Via OTA and AFH.