[UNOFFICIAL][ROM] LineageOS 17.1 for Galaxy Tab E [SM-T560NU]

[retiredtab]

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.

I spent hundreds of hours building this rom. The least you can do is spend a few minutes reading posts 1, 2, and 3 before posting.

Try this build at your own risk. It's likely to have bugs and is EXPERIMENTAL as 17.1 is a work in progress. It boots and seems to work fine on my SM-T560NU, but I have only tested it for 24 hours. Problems will likley surface later?

BACKUP YOUR FILES and have a copy of your working image BEFORE trying my build.

I built a new image of SM-T560NU following the instructions at

https://wiki.lineageos.org/devices/gtelwifiue/build

What works.

1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. Google play store (using gapps pico)

Known problems.

1. stock camera

Stock LineageOS camera app back camera does not display properly. It is split into 8 frames. Use opencamera apk from

https://f-droid.org/en/packages/net.sourceforge.opencamera/

I will not be spending anytime trying to fix the stock camera problem. I never use it and opencamera works.

2. The stock Jelly browser crashes a lot. Use a different browser. There's lots of better options that are more stable and reliable than the built in Jelly browser.

3. FM Radio is not support since this device doesn't have the LTE functionality.

4. text on home screen looks funny. This only seems to affect the home screen and nowhere else. Problem is with stock trebuchet launcher and/or its fonts. I have seen the same problem on the SM-T350, SM-T560NU, SM-P550 and Nexus 7 2013.

I tried rootless pixel launcher from fdroid as a quick and simple test and see no problems with home screen text. Rootless pixel uses a different font though. A future LineageOS update could resolve the problem?

https://f-droid.org/en/packages/amirz.rootless.nexuslauncher/

 

[retiredtab]

Dec 14, 2021 release notes
1. Dec 5 security patches as per https://review.lineageos.org/q/topic:Q_asb_2021-12
2. Whatever LiineageOS changed since last November release (about 4,400 files had to be recompiled).

Nov 8, 2021 release notes
1. Nov 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/318647
2. Whatever LiineageOS changed since last October release (about 5,100 files had to be recompiled).

Oct 10, 2021 release notes
1. Oct 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/317410
2. Whatever LiineageOS changed since last Sept release (about 4,200 files had to be recompiled).

Sept 16, 2021 release notes
1. Sept 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/316083
2. Whatever LiineageOS changed since last August release (about 49,000 files had to be recompiled).

Aug 7, 2021 release notes
1. August 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/314572
2. Whatever LiineageOS changed since last July release (about 5000 files had to be recompiled).

July 12, 2021 release notes
1. July 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/313448
2. Whatever LiineageOS changed since last June release (about 4500 files had to be recompiled).

June 15, 2021 release notes
1. June 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/312240
2. Whatever LiineageOS changed since last May release (about 6000 files had to be recompiled).

May 9, 2021 release notes
1. May 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/309564
2. Whatever LiineageOS changed since last April release.

April 12, 2021 release notes
1. April 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/307454
2. Whatever LiineageOS changed since last March release. Nearly 59,000 out of the 70,000 files had to be recompiled due to the last set of changes.

Release notes for March 7, 2021
1. Mar 5 security patches.
2. Whatever LiineageOS changed since last February release.

Release notes for Feb 11, 2021
1. Feb 5 security patches.
2. Whatever LineageOS changed since last Jan 2021 update.
3. fixed audio over bluetooth. Problem was one variable pointing to the wrong audio directory which was changed in 17.1.

Release notes for Jan 14, 2021
1. Jan 5 security patches.
2. Whatever LineageOS changed since last Dec 2020 update.

Release notes for Dec 14, 2020
1. Dec 5 security patches
2. Changed some error messages to verbose to stop spamming log files
3. Whatever LineageOS changed since last Nov update

Release notes for Nov 7, 2020
1. Nov 5 security patches

Release notes for Oct 8, 2020
1. Oct 5 security patches

Release notes for Sept 15, 2020
1. Sept 5 security patches
2. added on screen nav buttons (you can change via settings)

Release notes for Aug 26, 2020
1. add fix for missing some play store apps (I have removed the Aug 20 build)
2. changed build fingerprint to a stock fingerprint

Release notes for Aug 20, 2020
1. initial release
2. initial testing, have no idea about long term stability
3. bug with hal hwbinder vibrator that causes tablet to be stuck at boot logo animation (have removed hal vibrator for now)
4. msm8916 kernel overclocked CPU to 1.6Ghz in kernel with 17.1 by default
5. incoporates aug 5 security patches

 

[retiredtab]

FAQ - I spent hundreds of hours building this rom. The least you can do is spend a few minutes reading everything before posting.

Q1) What TWRP should I use?
A1) Use 3.2.3 found at

https://msm8916.com/?view=downloads&dist_name_short=TWRP&codename=gtelwifiue

Or use 3.5.2_9 that I built.

retiredtab - Browse /SM-T560NU/TWRP at SourceForge.net

sourceforge.net

Q2) Does the build work on xyz?
A2) I have no idea. I only have the SM-T560NU. It will not work on the SM-T561 and SM-T560 as it uses a different SoC (CPU).

Q3) Application xyz doesnt' work. Can you fix it?
A3) I only fix what I use. If you use app xyz and it doesn't work, then try 16.0 or going back to the last rom that worked for you.

Q4) My tablet hangs or crashes with 17.1. This build is slow and buggy. Can you fix it?
A4) Go back to the last working stable rom for you. 17.1 is a work in progress and will have bugs and frequent changes.

Q5) Do you plan to update the rom?
A5) Yes as long as I have high speed Internet, I wil try to release the rom monthly to incorporate the security patches.

Q6) Can you build this for the SM-T560?
A6) No, I don't have the SM-T560.

Q7) Can I turn off the on screen navigation keys?
A7) To turn off on screen navigation, go to settings, system, advanced, gestures, system navigation, gesture navigation.

Q8) Can I build this rom? Where are the source and kernel source files?
A8) Yes. The kernel source files are at

Samsung MSM8916 Devices

Samsung MSM8916 Devices has 68 repositories available. Follow their code on GitHub.

github.com

I have attached the repo diff and roomservice.xml file that I have used. The repo diff are all the changes I have made to the "stock" msm8916 code.

Q9) Where can I download this rom?
A9) The 2020 builds are at

https://www.androidfilehost.com/?w=files&flid=315153

I'm moving to sourceforge for all 2021 uploads. The main reason is that I would like to see the stats of where this rom is being downloaded from worldwide. All 2020 builds will remain on androidfilehost.

2021 builds at

retiredtab - Browse /SM-T560NU/17.1 at SourceForge.net

sourceforge.net

 

[sillycat98]

Thanks for building this, downloading it now. Do you use opengapps or mindthegapps?

 

[retiredtab]

Do you use opengapps or mindthegapps?

I tested opengapps pico and micro-g on the 16.0 build, but not on the 171. build.

 

[sillycat98]

Q5)This build is slow and buggy. Can you fix it? A5) Go back to the last working stable rom for you. 17.1 is a work in progress and will have bugs and frequent changes.

Isn't everything on this tablet slow and buggy? Even the stock rom was horrible for me. Think I might try mindthegapps when I get home. Any problems I'll swap over to opengapps.

 

[retiredtab]

Isn't everything on this tablet slow and buggy? Even the stock rom was horrible for me. Think I might try mindthegapps when I get home. Any problems I'll swap over to opengapps.

This tablet isn't my daily driver so I have no reference if it's slow. I just got it and it happens to share some of the same code base as the SM-T350.

If this tablet is slow, it could be due to google services (gapps). You can always try microg. It's a way of running some Google services, but with a lighter set of software and some privacy.

https://microg.org/

I ran microg on this tablet with 16.0 and it seemed to work fine.

 

[sillycat98]

Runs great, the only problem I'm having is with one magisk module to spoof the props. It bootloops if I use it to change the fingerprint and I can't figure out why. Any ideas?

 

[retiredtab]

Runs great, the only problem I'm having is with one magisk module to spoof the props. It bootloops if I use it to change the fingerprint and I can't figure out why. Any ideas?

I have only seen the need to change fingerprint to pass google's CTS. Is this what you are trying to do?

Does it bootloop with 16.0?

 

[retiredtab]

For boot loops, undo your changes.

Then unlock developer options, enable adb debugging and adb root. Then reboot tablet, re-enable your changes, reboot again and get a logcat while it's booting. It should show error messages in the logcat.

That's how I was able to figure out the vibrator hal causing a bootloop on the 560NU.

 

[sillycat98]

I have only seen the need to change fingerprint to pass google's CTS. Is this what you are trying to do?

Does it bootloop with 16.0?

It is what I was trying and it didn't with 16 but I can live without it, I'll just have to download what I want to my phone and extract the apks then transfer when over.

For boot loops, undo your changes.

Then unlock developer options, enable adb debugging and adb root. Then reboot tablet, re-enable your changes, reboot again and get a logcat while it's booting. It should show error messages in the logcat.

That's how I was able to figure out the vibrator hal causing a bootloop on the 560NU.

I'll try to get a logcat later.

 

[retiredtab]

It is what I was trying and it didn't with 16 .

For 17.1, it's possible that a lineageos change in the future will fix the boot loop since 17.1 is still a work in progress.

Or what we did for the sm-t350, is we used a stock fingerprint and over rode the fingerprint to pass CTS. If I can get a stock SM-T560NU fingerprint, I can look at putting it into the 17.1 code. It's a single line of code in one of the mk files. It looks like this for the 350.

BUILD_FINGERPRINT=samsung/gt58wifixx/gt58wifi:7.1.1/NMF26X/T350XXU1CQJ1:user/release-keys

That spoofs play store into thinking its "certified" Samsung device.

Source:

https://github.com/Evervolv/android...mmit/5ad790d570e1c18e0706a7b2ce121e5c58ba79ba

 

[retiredtab]

BTW, if it works on 16.0, I plan to do monthly security patch builds for 16.0 as well, so you can stay on 16.0 if that makes life easier for you.

I'm likely to run 17.1 just to keep testing and again because 17.1 is a work in progress by the Lineageos team.

 

[retiredtab]

As I mentioned, this is NOT my daily driver tablet and I just got it and I wanted to run only microg and not use any gapps. As such, I didn't test gapps. Now that I loaded gapps and google plays store, I do see a problem. I will try to fix it over the next few days. I will update post #1 to reflect potential problems with google play store.

Google play store works in my 16.0 build. So if you need Google play store, use 16.0 for now.

For future builds, I will test goolge play store before releasing another build.

 

[retiredtab]

Looks like this is a known issue with the msm8916 team as per github (June 25th, 2020).

https://github.com/Galaxy-MSM8916/android_device_samsung_msm8916-common/pull/43

"Google PlayStore not showing some apps fix #43" Thanks for continuing, there is a fix on the way.

 

[retiredtab]

The fix at

https://github.com/ArbabAliRajper/a...mmit/73e686a841cb282299b97c133f097dfa2256706b

# Google Play Store
PRODUCT_PROPERTY_OVERRIDES += \
ro.opengles.version=196608

works. I can see more apps at the play store. I'll build this fix into the next September build after all the security patches are incorporated.

I don't know when msm8916 team will incorporate it or do something different.

 

[retiredtab]

I uploaded an Aug 26 build with the play store fix as per above and changed the build fingerprint. If I just use Magisk and enable hide Magisk, it passes CTS and shows as a "device is certified" in play store.

You may have to delete the files and cache in google play services and google play store to get rescanned for CTS.

I removed the Aug 20 build.

 

[sillycat98]

I uploaded an Aug 26 build with the play store fix as per above and changed the build fingerprint. If I just use Magisk and enable hide Magisk, it passes CTS and shows as a "device is certified" in play store.

You may have to delete the files and cache in google play services and google play store to get rescanned for CTS.

I removed the Aug 20 build.

Sorry for the delay, been busy the last few days. I appreciate you looking at it, this is the best this tablet has worked since I bought the thing. The main reason I wanted to go to 17.1 is Android 10 supports Bluetooth dual shock for remote play and 16 didn't. So I really appreciate everything you are doing. I wish I could afford to give you a little something, you deserve it, but unfortunately I can't at the moment. Let me know if you need anything from me though.

Edit: I hate to keep bothering you but is there any way to turn on the on-screen nav bar? I hate those buttons at the bottom and disabled them but I'm having some difficulty with XDA's navigation gestures, I'm used to my Pixel and I can't quite get it setup correctly.

 

[retiredtab]

but is there any way to turn on the on-screen nav bar?

I'll add

qemu.hw.mainkeys=0

to the September security patch build.

For now, if you have Magisk installed, the easiest way to get on screen nav bar is goto Magisk Manager, menu, downloads, search for props, dowload and install and reboot.

Once rebooted, go settings, about tablet, tap build number 7 times to enable developer settings. Then system, advanced, developer options, enable local terminal.

Then go home, choose terminal app and type "props".

Choose 5 (add custom props), n (new), qemu.hw.mainkeys, enter, 0, enter.

Screen should say this will set qemu.hw.mainkeys to: 0

Press y to accept and reboot.

Your screen nav bar should appear after reboot.

Then goto settings, system, advanced, gestures, system navigation.

navigation bar settings are at buttons menu to let you swap (invert) the back and recent menu buttons to match hardware buttons.

Yes, I tested the above and there are no boot loops while adding this prop or use the prop editor that is downloaded from Magisk.

 

[sillycat98]

I'll add

qemu.hw.mainkeys=0

to the September security patch build.

For now, if you have Magisk installed, the easiest way to get on screen nav bar is goto Magisk Manager, menu, downloads, search for props, dowload and install and reboot.

Once rebooted, go settings, about tablet, tap build number 7 times to enable developer settings. Then system, advanced, developer options, enable local terminal.

Then go home, choose terminal app and type "props".

Choose 5 (add custom props), n (new), qemu.hw.mainkeys, enter, 0, enter.

Screen should say this will set qemu.hw.mainkeys to: 0

Press y to accept and reboot.

Your screen nav bar should appear after reboot.

Then goto settings, system, advanced, gestures, system navigation.

navigation bar settings are at buttons menu to let you swap (invert) the back and recent menu buttons to match hardware buttons.

Yes, I tested the above and there are no boot loops which adding this prop or use the prop editor that is downloaded from Magisk.

Thanks again, this worked a treat. I had used props to change the fingerprint before but had never messed with the custom option. I finally have a reason to use this tablet again thanks to you.

You rock.