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

[UNOFFICIAL][ROM]BETA LineageOS 18.1 for Galaxy Tab E [SM-T560NU] Nov 7, 2021

Search This thread

kewecuminer

New member
Oct 15, 2021
3
0
Now that i got all my issues squared away, and installed opengapps, this device with this rom is amazing. It has gone from an unusable slog of a brick to my preferred device. Thanks.
 

DJABHipHop

Senior Member
Dec 7, 2017
753
596
pressthemes.freesite.host
Now that i got all my issues squared away, and installed opengapps, this device with this rom is amazing. It has gone from an unusable slog of a brick to my preferred device. Thanks.


 

DJABHipHop

Senior Member
Dec 7, 2017
753
596
pressthemes.freesite.host
PLEASE BEFORE YOU decide to try this rom, you MUST read all of post 1, 2, 3 and 4 (about 10 minute read). If you think this is an unreasonable request, then stop reading now and find another rom. Thank you.

I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this rom.

BACKUP YOUR DATA AND OLD rom BEFORE trying my rom.

If you are NOT an expert in using fastboot, adb, odin, heimdall, twrp, DO NOT use this rom. You must know how to use these tools to revert back to your old rom.

If you are new to flashing custom roms, do NOT attempt this.

If you need your tablet for work and something important, do NOT flash this rom. This rom could result in a bricked device or boot loop or non booting device or you not being able to revert back to your old rom.

What works

1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. audio over bluetooth
8. selinux enforcing

What doesn't work

1. Camera. The stock camera app front camera preview doesn't work. Use opencamera instead. I have no plans to fix the stock camera app as opencamera works fine.
2. Live display. Live display causes a stuck at boot animation/boot loop on SM-T560NU, so I disabled it from the menu option. This feature worked in 17.1, but broken in 18.1.

Thanks
1. LineageOS team for source code.
2. Pre alpha testers for the Samsung Tab A/E roms who provided valuable feedback: lpedia, Schaagi, katochwa, Henrick Grimler
3. Huge thanks to Henrick Grimler https://github.com/Grimler91 for helping me reproduce a major bug in 18.1 which led me to find a solution. Henrick also helped fine tune some of the sepolicy as well.
4. Sebastiano Barezzi https://github.com/SebaUbuntu for giving the msm8916 repo some 18.1 code updates in March 2021.
5. Exynos5420 team for sharing it's knowledge in building roms.
6. msm8916 team for their repos

Great news everyone I manage to fix Camera on both MSM8916 version of the Tab E!!!! The bug was ZSL related

 

Attachments

  • photo1614618371.jpeg
    photo1614618371.jpeg
    37.9 KB · Views: 12
  • screen-10-25-2021 13:58:17.png
    screen-10-25-2021 13:58:17.png
    37.8 KB · Views: 10

retiredtab

Senior Member
Nov 16, 2017
894
467
New build called lineage-18.1-20211107-UNOFFICIAL-gtelwifiue.zip

NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.

Nov 7 release notes
1. Nov 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/318560

2. I enabled zram swap with size 512MB. I noticed that the last couple of months that Clash Royale would crash/close and logs showed

Code:
10-28 14:26:01.412    0    0 I [2:        kswapd0:  91] lowmemorykiller: Killing 'ell.clashroyale' (6730), adj 0,

Hopefully, by enabling zram, that will stop Clash Royale from crashing/closing.

Zswap is enabled on stock Nougat SM-T350 (part of the Samsung Tab A/E family that uses same msm8916 kernel code)

https://github.com/retiredtab/andro...mmit/2a6bf385e6dfe6073fe328b7b1c563ccd60a5ede

https://github.com/retiredtab/andro...mmit/438d5d3ad20cbc98f0f8c18eb610b6268de19395

This code uses the in kernel low memory killer (lmk). I tried using the Android OS lmk, but it doesn't work very well and shows this in the log.

Code:
 E lowmemorykiller: /proc/zoneinfo parse error
 E lowmemorykiller: Failed to get free memory!

3. Whatever LineageOS changed since last Oct release (about 8,000 files had to be recompiled). One of these changes has removed the built in terminal program from LineageOS as AOSP deprecated this app as per

https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/304043
 

DJABHipHop

Senior Member
Dec 7, 2017
753
596
pressthemes.freesite.host

retiredtab

Senior Member
Nov 16, 2017
894
467
@DJABHipHop , thanks for sharing your repo. I saw your commit last week and tried to apply it to my repo on the weekend of Nov 6 and 7, but it doesn't compile in 18.1. Once I fixed line 223

https://github.com/LOSSG-8916/andro...3743820cbeff1a5/camera/CameraWrapper.cpp#L223

it compiled, but then it produced HAL errors and even opencamera, which works, couldn't see the camera HAL. What's worse is that your proposed code change broke the camera HAL even after I reverted your changes. Luckily, I had a hard drive backup and I was able to restore my working configurations.

I then used dd to clone my working configuration and tried your changes again. I got the exact same camera HAL error again and it also messed up my working configuration again despite reverting the changes. I spent 2 days trying to get it to work, but it doesn't.

People who want to use the camera with my builds can use opencamera as I mentioned in post #1.
 

DJABHipHop

Senior Member
Dec 7, 2017
753
596
pressthemes.freesite.host
@DJABHipHop , thanks for sharing your repo. I saw your commit last week and tried to apply it to my repo on the weekend of Nov 6 and 7, but it doesn't compile in 18.1. Once I fixed line 223

https://github.com/LOSSG-8916/andro...3743820cbeff1a5/camera/CameraWrapper.cpp#L223

it compiled, but then it produced HAL errors and even opencamera, which works, couldn't see the camera HAL. What's worse is that your proposed code change broke the camera HAL even after I reverted your changes. Luckily, I had a hard drive backup and I was able to restore my working configurations.

I then used dd to clone my working configuration and tried your changes again. I got the exact same camera HAL error again and it also messed up my working configuration again despite reverting the changes. I spent 2 days trying to get it to work, but it doesn't.

People who want to use the camera with my builds can use opencamera as I mentioned in post #1.
I fix it on 17.1
 

DJABHipHop

Senior Member
Dec 7, 2017
753
596
pressthemes.freesite.host
@DJABHipHop , thanks for sharing your repo. I saw your commit last week and tried to apply it to my repo on the weekend of Nov 6 and 7, but it doesn't compile in 18.1. Once I fixed line 223

https://github.com/LOSSG-8916/andro...3743820cbeff1a5/camera/CameraWrapper.cpp#L223

it compiled, but then it produced HAL errors and even opencamera, which works, couldn't see the camera HAL. What's worse is that your proposed code change broke the camera HAL even after I reverted your changes. Luckily, I had a hard drive backup and I was able to restore my working configurations.

I then used dd to clone my working configuration and tried your changes again. I got the exact same camera HAL error again and it also messed up my working configuration again despite reverting the changes. I spent 2 days trying to get it to work, but it doesn't.

People who want to use the camera with my builds can use opencamera as I mentioned in post #1.
@retiredtab I fix the 18.1 camera wrapper & it now works 100% Can you test it for me?

 

DJABHipHop

Senior Member
Dec 7, 2017
753
596
pressthemes.freesite.host
Yes, the front camera preview works now. Thank you for fixing it and submitting the patch. I will incoporate it into the 18.1 Dec 5 security patch build.

NP, Also feel free take a look my source as my 17.1 source since boots time are between 38-40s, Plus I have working repo for the SM-T377P
 

Attachments

  • Screen Shot 2021-10-02 at 11.44.02 AM.png
    Screen Shot 2021-10-02 at 11.44.02 AM.png
    44.7 KB · Views: 6
Last edited:

starc2k

Member
Aug 13, 2009
14
1
sorry for my noob question, but... there`s any chance to get this roms working on t-560 (not NU) thanx in advance
 

DJABHipHop

Senior Member
Dec 7, 2017
753
596
pressthemes.freesite.host
I only have the SM-T560NU and no SM-T377P so I have no idea.
I have both A SM-T560NU & A SM-T377P I can test with, But is broken mobile data on my SM-T377P & my SM-T560NU still show traces of Mobile data crap & both my SM-T560NU & my SM-T377P still show traces of FM_Radio data crap on my 17.1 build

12-01 09:03:31.032 652 652 E NotificationPrefHelper: createDefaultChannelIfNeededLocked - Exception: android.content.pm.PackageManager$NameNotFoundException: com.android.fmradio
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    New build called lineage-18.1-20210909-UNOFFICIAL-gtelwifiue.zip

    NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.

    18.1 continues to be my daily driver since March 2021.

    Sept 9 release notes
    1. Reverted the patch to https://github.com/retiredtab/andro...mmit/a32c7a0bed536281d20b7c1cf8d41c84a268cc80
    Removing systemUI from pinner services causes a 4 to 6 delay in bringing up the home screen. This is seen when loading or playing a game for about 20 minutes and then either hitting the recents or home button. By reverting this commit, pressing recents or home button brings up the systemUI right away.
    2. Sept 5 security patches as per https://review.lineageos.org/c/LineageOS/android/+/315661
    3. Whatever LiineageOS changed since last August release (about 6,000 files had to be recompiled).
    2
    New build called lineage-18.1-20211010-UNOFFICIAL-gtelwifiue.zip

    NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.

    18.1 continues to be my daily driver since March 2021.

    Oct 10 release notes
    1. Oct 1 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/317001
    2. Added https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/316839 to fix landscape mode system UI as reported in post #5 by @Fruse . This patch is not yet officially merged as of Oct 10 release.
    3. Whatever LiineageOS changed since last September release (about 7,200 files had to be recompiled).
    1
    FAQ - I spent hundreds of hours building this rom. It was frustrating process from Nov 2020 to March 2021 running into bug after bug. The least you can do is spend a few minutes reading everything before posting.

    Q1. Where are the source and kernel source files?
    A1. The kernel source files are at


    The device tree files are at


    The vendor tree files are at


    In addition, there is a repo diff file for device specific tweaks needed to work and a roomservice.xml (local manifest file) file so you can build this rom yourself.

    Q2. Is this BETA rom suitable as a daily driver?
    A2. It can be depending on your requirements. I can't test every app so you try it yourself to see if it's suitable. I've been using this rom myself since mid March 2021 with no major issues.

    Q3. What if my app, xyz, doesn't work?
    A3. I won't answer questions regarding why your app doesn't work. If your app, whatever it is, doesn't work, then go back to your old rom. It's difficult enough building and maintaining these roms. Remember, I'm an unpaid volunteer making a rom for free for your benefit.

    Q4. Your rom is laggy and buggy.
    A4. If you find the above, then go back to your old rom. There's only so much software can do on a 2015 budget level tablet. Remember a budget tablet will have the slower SoC/CPU and less DRAM than a top of the line model. Your tablet will also run slower when you use gapps (google apps). You can run a lot of software without using gapps. Research fdroid, newpipe, Aurora store etc.

    Q5. What TWRP should I use?
    A5. You MUST use 3.2.3 below


    OR my 3.5.2_9 TWRP build

    https://sourceforge.net/projects/retiredtab/files/SM-T560NU/TWRP/

    Q6. Why should I use this rom?
    A6. You don't. If you don't like this rom, then don't use it. Yes, it's that simple.

    Q7. Will you offer monthly updates with security patches?
    A7. I will try to offer monthly security patches, but that all depends on if I continue to have high speed Internet in the future.

    Q8. Can you help me? I'm a newbie. Can you provide step by step instructions?
    A8. Do your own research. There are lots of tutorials, videos, etc on how to flash roms. Newbie questions must be posted in the Questions and Answers forum, not here.

    Q9. Can I report a bug with respect to the rom?
    A9. Yes, but you need to supply the following information. If you don't, I won't look at it.

    You must provide an adb logcat of the problem and tell me how to reproduce it. Note I will not be downloading any apps that require money or an userid/password. For example, if you have problems with Netflix, I cannot help you since I don't have a paid subscription. If you use some app that requires an userid/password, I cannot help you as I'm not willing to create another userid/password even if it's free.

    To get a logcat, open up a terminal window.
    Code:
    # clear the logcat first
    adb logcat -c
    # start logcat trace
    adb logcat > problem.txt
    # reproduce problem
    # wait until problem has occured, then stop trace by hitting ctrl-c

    Q10. Will you still build 17.1 for this device?
    A10. Yes, for now, but I will probably discontinue building 17.1 at the end of 2021. I will likely be trying to build 19.0 once it's released so I don't want to maintain 3 releases.

    Q11. Do I need to erase everything and format my data?
    A11. Yes, you MUST erase all the partitions (system, data, dalvik/art cache, cache) using TWRP and MUST format your data before installing 18.1 when you are coming from stock or an earlier version of LineageOS or from another custom rom. If you get stuck at the boot animation for more than 5 minutes, it's likely because you didn't follow the instructions I just wrote. Dirty flashes from stock, other custom roms or older LineageOS versions are not supported and not likely to work.

    Q12. What gapps should I use?
    A12. I don't use gapps anymore. I use Aurora Store. As of Nov 6, 2021, I no longer make recommendations on which gapps to use as your mileage may vary. It's reported that opengapps does no testing on their daily builds and some version results in bootloops, bitgapps may run out of disk space will installing apps and Mindthegapps as causing overall slowdown of the system.

    The only recommendation I can make is to use the SMALLEST version of gapps which is PICO or equivalent naming convention. DO NOT use anything other than PICO. That is, do not use nano, mini, stock, etc.

    If you are going to install gapps, flash the rom first, reboot into system/OS, reboot to recovery, flash gapps, reboot into system/OS. That is, do not flash/install the rom and gapps at the same time.

    Q13. I'm having problems with gapps, can you answer why it's not working?
    A13. I will not answer any questions regarding gapps. This thread is about the rom, not gapps and I don't use gapps so I cannot help you. Android does not depend on gapps in order to work.

    Q14. Why isn't my post answered?
    A14. It's probably because it's answered in the FAQ or not relevant to the rom. Again, I do not run Windows OS or use gapps. Questions already answered in the FAQ will be completely ignored.

    Q15. Can I turn off the on screen navigation keys?
    A15. To turn off on screen navigation, go to settings, system, advanced, gestures, system navigation, gesture navigation. It's enabled by default because I find it useful. If you don't like it, you only need to disable once and your preference will be remembered. If you want to invert the onscreen keys, goto settings, system, buttons and enable invert layout

    Q16. What speed up/optimization tips do you suggest?
    A16.

    1. Turn off animations. Go into developer settings, scroll down to the drawing section, and set window, transition and animator scale all to "off".
    2. If you don't have a google account, don't install gapps. Use Aurora Store to get your apps as you can get all the same apps from the play store using an anonymous login.
    3. Dont' run more than 2 apps at the same time. You can probably listen to music in the background and use a web browser at the same time, but don't expect great performance from a 2015 entry level tablet.
    4. Use a web browser like Brave that has built in adblock and privacy features.
    5. Use newpipe to watch your streaming content. It has built in adblock so you don't have to watch forced ads.
    6. Look for apps that are open source, ad free and lightweight.

    Q17. Does this rom support Magisk?
    A17. I don't use Magisk myself so I don't know and Magisk is always being updated to fool Google's certification process. Others have reported Magisk as working, but I won't answer any questions regarding it.

    Q18. Will this rom ever become official?
    A18. Never. I don't want the responsibilities that come with being an official maintainer. In addition, I know my device trees, code organization and git commits will NOT meet LineageOS standards. Remember, I'm an unpaid volunteer doing this in my free time and sharing my work with you for free so you can get hundreds of hours of enjoyment from this tablet.

    Q19. What is the difference between this rom and others?
    A19. This rom tries to be pure LineageOS with little to no modifications. Other roms may have different UI, different bundled apps, etc. Use whatever meets your requirements.

    Q20. Will there be any major 18.1 code modifications in the future?
    A20. I don't anticipate any major modifications. There may be some slight tweaking to the sepolicy, small bug fixes and minor code cleanup, but all the hard work in getting the rom up and running and fixing all the major bugs have been done completed. This doesn't mean the code is perfect or well organized, but I won't be doing any major changes now that 18.1 is working. Any major changes will be done in 19.0.

    Q21. Why did you fork the device and vendor trees for 18.1?
    A21. The msm8916 repos seem geared towards phones and sometimes do not work or cause boot animation loops for tablets so I decided to fork their repos. In other words, what's deemed as msm8916-common code isn't common to all devices.

    In addition, since I'm building SM-T350, SM-T550, SM-P550 and SM-T560NU (all use the same msm8916 code), it seems easier to maintain all of them if I can control my own code repos and not worry if my changes affects the phones or not. I still have not figured out the best way to manage all my repos and it's a work in progress.

    Q22. Can you build a variant of this device? For example, a LTE or S-pen version.
    A22. If I don't physically have the device, I cannot and will not build it unless I can boot and test it myself. Even then, there's no guarantee that I can get those variant features working.

    Q23. Can I load this rom on a variant devivce like LTE or S-pen version?
    A23. The rom is built for the device explicitly listed. If you are an advanced user and understand TWRP, adb, odin, heimdall, you can try loading it on a LTE or S-pen variant by modifying the updater-script, but it may cause a bricked device, bootloops or non functionality of LTE/S-pen. You have been informed and warned!

    Q24. Will this run on the SM-T560 or SM-T561?
    A24. No, the SM-T560 and SM-T561 use a different CPU/SoC. The SM-T560NU rom will NOT work on SM T560/SM-T561.

    Q25. Okay, I understand the consequences and that this is BETA rom and willing to take the risks outlined, now where can I find the rom?
    A25. Downloads are at

    1
    NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data. This is known has a clean install. Backup your data before a clean install.

    18.1 continues to be my daily driver since March 2021.

    Nov 7 release notes
    1. Nov 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/318560

    2. I enabled zram swap with size 512MB. I noticed that the last couple of months that Clash Royale would crash/close and logs showed

    Code:
    10-28 14:26:01.412    0    0 I [2:        kswapd0:  91] lowmemorykiller: Killing 'ell.clashroyale' (6730), adj 0,

    Hopefully, by enabling zram, that will stop Clash Royale from crashing/closing.

    Zswap is enabled on stock Nougat SM-T350 (part of the Samsung Tab A/E family that uses same msm8916 kernel code)

    https://github.com/retiredtab/andro...mmit/2a6bf385e6dfe6073fe328b7b1c563ccd60a5ede

    https://github.com/retiredtab/andro...mmit/438d5d3ad20cbc98f0f8c18eb610b6268de19395

    This code uses the in kernel low memory killer (lmk). I tried using the Android OS lmk, but it doesn't work very well and shows this in the log.

    Code:
     E lowmemorykiller: /proc/zoneinfo parse error
     E lowmemorykiller: Failed to get free memory!

    3. Whatever LineageOS changed since last Oct release (about 8,000 files had to be recompiled). One of these changes has removed the built in terminal program from LineageOS as AOSP deprecated this app as per

    https://review.lineageos.org/c/LineageOS/android_vendor_lineage/+/304043

    Oct 10 release notes
    1. Oct 1 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/317001
    2. Added https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/316839 to fix landscape mode system UI. This patch is not yet officially merged as of Oct 10 release.
    3. Whatever LiineageOS changed since last September release (about 7,200 files had to be recompiled).

    Sept 9 release notes
    1. Reverted the patch to https://github.com/retiredtab/andro...mmit/a32c7a0bed536281d20b7c1cf8d41c84a268cc80
    Removing systemUI from pinner services causes a 4 to 6 delay in bringing up the home screen. This is seen when loading or playing a game for about 20 minutes and then either hitting the recents or home button. By reverting this commit, pressing recents or home button brings up the systemUI right away.
    2. Sept 5 security patches as per https://review.lineageos.org/c/LineageOS/android/+/315661
    3. Whatever LiineageOS changed since last August release (about 6,000 files had to be recompiled).

    Aug 8 release notes
    1. Fix battery status icon. When you plug in AC adapter, settings, battery does not show it charging even though it is. This is due to the sepolicy being too restrictive. I added https://github.com/retiredtab/msm89...mmit/c1eca9f7740b6a384d4fab8a1e8d812f59c17a99
    2. Aug 5 security patches as per https://review.lineageos.org/c/LineageOS/android/+/314477
    3. Whatever LiineageOS changed since last July release (about 23,000 files had to be recompiled).

    July 9 release notes
    1. Initial public release to XDA. This is an ALPHA build.
    2. July 5 security patches as per https://review.lineageos.org/q/topic:"android-11.0.0_r39"+(status:eek:pen OR status:merged)
    3. Small bug in settings, battery where the charging lightning symbol is not displayed when AC adapter is plugged in. This will be fixed in the August security patches.
    1
    I just found out that the stock camera is partially working (Both 17.1 and 18.1) but still recommended to use Open Camera.
    What works on stock camera:
    • Panorama
    • QR code scanning
    What partially works:
    • Video capturing (Recorded videos are broken)
    What does not work:
    • Taking pictures