Develop Bugs

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

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/

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

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

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

sillycat98 said:
Do you use opengapps or mindthegapps?
Click to expand...
Click to collapse
I tested opengapps pico and micro-g on the 16.0 build, but not on the 171. build.

retiredtab said:
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.
Click to expand...
Click to collapse
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.

sillycat98 said:
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.
Click to expand...
Click to collapse
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.

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?

sillycat98 said:
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?
Click to expand...
Click to collapse
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?

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.

retiredtab said:
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?
Click to expand...
Click to collapse
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.
retiredtab said:
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.
Click to expand...
Click to collapse
I'll try to get a logcat later.

sillycat98 said:
It is what I was trying and it didn't with 16 .
Click to expand...
Click to collapse
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

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.

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.

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.

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.

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.

retiredtab said:
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.
Click to expand...
Click to collapse
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.

sillycat98 said:
but is there any way to turn on the on-screen nav bar?
Click to expand...
Click to collapse
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.

retiredtab said:
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.
Click to expand...
Click to collapse
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.

Tab S3 T820 security version

So yesterday I installed LineageOS 17.1 on my Tab S3 (T820). Installation went without a lot of problems, but when I booted into the system for the first time, I got a notification about the security version. I clicked the notification to see what's up. Turns out I'm running a security patch from February 5, 2020
(See screenshots in link)
imgur (dot) com/a/yBfDlnH
I already tried updating via several buttons, but no luck.
Is there any way for me to update this manually to a new security patch? Or is it not needed?

MrDanMan said:
So yesterday I installed LineageOS 17.1 on my Tab S3 (T820). Installation went without a lot of problems, but when I booted into the system for the first time, I got a notification about the security version. I clicked the notification to see what's up. Turns out I'm running a security patch from February 5, 2020
(See screenshots in link)
imgur (dot) com/a/yBfDlnH
I already tried updating via several buttons, but no luck.
Is there any way for me to update this manually to a new security patch? Or is it not needed?
Click to expand...
Click to collapse
It's not about patch level. It says "signed with public keys" that's typical for unofficial builds.
The patch levels can only be updated by building a new installation zip. Vendors patch level only if manufacturer releases an update and developer includes updated components.

kurtn said:
It's not about patch level. It says "signed with public keys" that's typical for unofficial builds.
The patch levels can only be updated by building a new installation zip. Vendors patch level only if manufacturer releases an update and developer includes updated components.
Click to expand...
Click to collapse
So there is no way for me to update to a newer security version (for example September 2020)?

MrDanMan said:
So there is no way for me to update to a newer security version (for example September 2020)?
Click to expand...
Click to collapse
Way 1 - search
Way 2 - wait
Way 3 - build

[UNOFFICIAL]LineageOS 15.1 For Nexus 9 (WIFI) (Feb 24, 2022)

BEFORE YOU decide to try this rom, please read all of post 1, 2 and 3.
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 this rom.
What works
I only test what I use. There could be other things that work or don't work. Let me be clear since there are people who don't seem to understand this. I cannot test things that I don't have like paid streaming/gaming, NFC, miracast or apps that I don't use. They may work or they may not work.
If you want to know if something works that's not listed here, then you need to try it for yourself. If that's not an acceptable or reasonable answer, then stop reading and find another rom that meets your requirements. I built this rom for myself to use and thought that some in the community might benefit by sharing it. If this rom doesn't meet your requirements, then delete it and use whatever does.
1. audio over bluetooth
2. wifi
3. brightness
4. external audio
5. GPS - a bit slow to get a fix/lock
6. audio through headphone jack
7. camera
What doesn't work
1. screen recorder. The current sepolicy doesn't allow screen recorder to work. While adding code to allow sepolicy to work
Code:
#============= mediacodec ==============
allow mediacodec camera_device:chr_file { ioctl open read write };
The [email protected] crashes. A mp4 file is created, but it doesn't seem to be in the correct format? Possibly related to ??
https://review.lineageos.org/c/LineageOS/android_device_htc_flounder/+/210609
FAQ
Q1) Does the build work on Nexus 9 LTE?
A1) I have no idea. I only have the Nexus 9 wifi so I don't know if it will work on LTE. If you have the LTE, you can build your own LTE rom. If you try the wifi build on the LTE, you may end up with a bricked device. Questions regarding LTE will go unanswered.
Q2) Application xyz doesnt' work. Can you fix it?
A2) I only fix what I use. If you use app xyz and it doesn't work, then try 14.1 or going back to the last rom that worked for you. In addition, some of the code is not open source and in proprietary blob format so it's not possible to make changes.
Q3) My tablet hangs or crashes with 15.1. This build is slow and buggy. Can you fix it?
A3) Go back to the last working stable rom for you. 15.1 is a work in progress and will have bugs and frequent changes. In addition, some of the code is not open source and in proprietary blob format so it's not possible to make changes.
Q4) Do you plan to update the rom?
A4) Yes as long as I have high speed Internet, I wil try to release the rom monthly to incorporate the security patches.
Q5) What TWRP should I use?
A6) TWRP 3.3.1 or higher. Get it from
Download TWRP for flounder
Download TWRP Open Recovery for flounder
dl.twrp.me
Q6) What is the difference between this rom and variants?
A6) Use whatever fits your needs. This is a stock LineageOS build with no modifications. I only offer this as an option for those who want or need a new rom and can't build it themselves.
Q7) Will there be a 16.0, 17.1 or 18.1 build?
A7) I tried building 16.0, but the rom get's stuck at the very begining of the boot process and I haven't investigated too much. Do not ask if there is progress on this. I'm an unpaid volunteer building this on my own time. Any questions regarding ETAs will go unanswered.
I suspect that one or two LineageOS developers have a working 16.0 build, but they are not ready to share their code? The repos have been updated to 16.0 at
LineageOS
A free and open-source operating system for various devices, based on the Android mobile platform. This is a mirror of https://review.lineageos.org/ - LineageOS
github.com
on Nov 4, 2020.
If you are a rom builder or developer and want to help get 16.0 going, please contact me.
Q8) Should I upgrade from stock or 14.1 to 15.1?
A8) It's entirely up to you. If you do upgrade, you will need to backup your data, wipe dalvik/art cache, system, data and internal storage in TWRP. You must also format data in TWRP. You cannot dirty flash from stock or 14.1 to 15.1, it must be a completely clean fresh install.
Q9) Can I build this rom myself? Where can I find the source and/or kernel source code?
A9) This is one of the few roms where it required no edits or changes to make it work. Follow the instructions at
Flounder
Build for flounder | LineageOS Wiki
wiki.lineageos.org
Flounder_lte
Build for flounder_lte | LineageOS Wiki
wiki.lineageos.org
and you will get a working 15.1 image. You will need to apply (hw video patch)
https://review.lineageos.org/268654
The roomservice.xml only consists of 3 repos. The roomservice.xml points to all the source code including the kernel source code. That is,
GitHub - LineageOS/android_kernel_htc_flounder
Contribute to LineageOS/android_kernel_htc_flounder development by creating an account on GitHub.
github.com
GitHub - LineageOS/android_device_htc_flounder
Contribute to LineageOS/android_device_htc_flounder development by creating an account on GitHub.
github.com
GitHub - TheMuppets/proprietary_vendor_htc
Contribute to TheMuppets/proprietary_vendor_htc development by creating an account on GitHub.
github.com
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_htc_flounder" path="device/htc/flounder" remote="github" revision="lineage-15.1" />
<project name="LineageOS/android_kernel_htc_flounder" path="kernel/htc/flounder" remote="github" revision="lineage-15.1" />
<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="lineage-15.1" />
</manifest>
I changed the fstab.flounder from forceencrypt to encryptable.
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,nosuid,nodev,errors=panic wait,check,latemount,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check,latemount,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
Normally, monthly builds go smoothly, but every once in a while, the monthly changes break something. This happened with the Nexus 9 for the May 5 security patches. While compiling, it was giving
"SSL error when connecting to the Jack server."
After some dead ends and research, I found
Rebuild android code with error “SSL error when connecting to the Jack server. Try 'jack-diagnose”
System: ubuntu 18.04 environment：VirtualBox The first time I compiled the AOSP source code on Ubuntu 18.04, it passed, and the second time I compiled it failed. Here is an error message. [ 10% 538/...
stackoverflow.com
To fix this, you need to "Remove TLSv1, TLSv1.1 from jdk.tls.disabledAlgorithms in /etc/java-8-openjdk/security/java.security" file.
Q10) Why is my question not answered?
A10) It's likely because it's in the FAQ or it's off topic or you are asking something that I cannot answer for the reasons stated in this FAQ.
Q11) How is this 15.1 build different from the ones already on XDA?
A11) The 15.1 roms built before Nov 4, 2020 didn't include this patch
flounder: Patch libraries that rely on arm libm intrinsics · LineageOS/[email protected]
* Force-pick https://review.lineageos.org/268655, build "libm" target, rename "libm.so" to "libw.so", and then: `sed -i 's/libm.so/libw.so/g' libw.so...
github.com
Also, some of the 15.1 roms may not have included the hw video patch. It's not part of the repository and requires the builder to pick and apply that patch manually.
For some, depending on how the device is used, having the hw video patch isn't necessary and will work fine without it.
Q12) Is the video hardware accelerated in 15.1?
A12) Yes. The March 9, 2021 and all future builds include this patch
https://review.lineageos.org/268654
for video hardware acceleration.
Q13) Is encryption enabled by default?
A13) Some people say the Nexus 9 lags over time and supposedly removing encryption improves performance. The Nexus 9 is not a daily driver for me so I don't know, but reading the older 14.1 and 15.1 threads, I decided to change the default behavior starting with the March 13, 2021 build so that encryption is disabled by default.
If you want encryption enabled, goto settings, security and privacy, encryption and credentials, encrypt tablet and follow instructions.
Q14) Can you build a variant like slimrom, crDroid, etc?
A14) No, but you can following the instructions and source code above that has been provided.
Q15) What gapps should I use?
A15) I personally am moving away from all google apps and technology. If you must use gapps, pick the smallest one which is pico ARM64.
Q16) Where can I download this rom?
A16) See
retiredtab - Browse /Nexus 9/15.1 at SourceForge.net
sourceforge.net

Feb 24, 2022 release notes
1. Incorporates UNOFFICIAL Feb 5 security patches as per https://review.lineageos.org/q/topic:O_asb_2022-02
2. Whatever LineageOS changed since Jan 5, 2022 (about 2,900 files had to be recompiled).
Jan 28, 2022 release notes
1. Incorporates Jan 5 security patches as per https://review.lineageos.org/q/topic:O_asb_2022-01
2. Whatever LineageOS changed since Dec 2021 (about 1,200 files had to be recompiled).
Dec 9, 2021 release notes
1. Incorporates Nov 5 and Dec 5 security patches as per https://review.lineageos.org/q/topic:P_asb_2021-11 and https://review.lineageos.org/q/topic:n-asb-2021-12. Specifically
Nov 5th
Code:
https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/318648
https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/318649
https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/318650
https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/318651
https://review.lineageos.org/c/LineageOS/android_packages_apps_Contacts/+/318654
https://review.lineageos.org/c/LineageOS/android_packages_apps_Settings/+/318655
https://review.lineageos.org/c/LineageOS/android_build/+/318658
Dec 5th
Code:
https://review.lineageos.org/c/LineageOS/android_external_tremolo/+/319986
https://review.lineageos.org/c/LineageOS/android_frameworks_av/+/319987 --> slight problem merging due to 14.1 and 15.1 code differences
https://review.lineageos.org/c/LineageOS/android_frameworks_base/+/319988
https://review.lineageos.org/c/LineageOS/android_packages_apps_Contacts/+/319989
https://review.lineageos.org/c/LineageOS/android_packages_apps_KeyChain/+/319990
https://review.lineageos.org/c/LineageOS/android_packages_apps_Settings/+/319991
2. Whatever LineageOS changed since Oct 2021 (about 4,300 files had to be recompiled).
3. This build is based on "stock" and not using Andrea's repos as it was reported to cause some slowness in operation.
Oct 11, 2021 release notes
1. Incorporates Oct 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/317622
2. Whatever LineageOS changed since September 2021 (about 2,400 files had to be recompiled).
3. This build is based on "stock" and not using Andrea's repos as it was reported to cause some slowness in operation.
Sept 24, 2021 release notes
1. Incorporates Sept 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/316179
2. Whatever LineageOS changed since August 2021 (about 1,800 files had to be recompiled).
3. This build is based on "stock" and not using Andrea's repos as it was reported to cause some slowness in operation.
Aug 9, 2021 release notes
1. Incorporates Aug 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/314577
2. Whatever LineageOS changed since July 2021.
3. This is the second build using Andrea's repos.
July 18 release notes
1. First build to incorporate changes by Andrea.
2. Incorporates July 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/313627
3. Whatever LineageOS changed since June 2021.
June 13, 2021 release notes
1. Incorporates June 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/312243
2. Whatever LineageOS changed since May 2021.
May 11, 2021 release notes
1. Incorporates May 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/309566
2. Whatever LineageOS changed since April 2021.
April 15, 2021 release notes
1. Incorporates April 5 security patches as per https://review.lineageos.org/c/LineageOS/android_build/+/307722
2. Removed livedisplay option from menu as it doesn't work on Nexus 9 Tegra SoC according to those more knowledgeable and experienced than I.
3. I recommend that you wipe cache/dalvik after you flash new build. Supposedly, the Nexus 9 internal flash file system gets slower over time and that wiping the flash and keeping as much free space available helps avoid the slowdown.
Release notes for March 13, 2021
1. Changed encryption to be disabled by default.
Release notes for March 9, 2021
1. Initial build for 15.1 Nexus 9 wifi only.
2. March 5, 2021 security patches
3. Built from LineageOS 15.1 repos with no changes or edits and includes the hw video patch.
4. Please be patient on first bootup.
For those that downloaded the March 8 build, please delete it. While it works, there was a problem with the build missing a hw video patch that I didn't notice at first. I will upload a March 9 build. Sorry for the trouble.

Reserved

For those that downloaded the March 8 build, please delete it. While it works, there was a problem with the build missing a hw video patch that I didn't notice at first. When I did a clean repo sync, I forgot to apply the hw video patch at
https://review.lineageos.org/268655
in the March 8 build. The March 8 build works as I tested it, but it wasn't until a few hours later that I realized I forgot to reapply the hw video patch.
The March 9 build includes the above hw patch. Sorry for the inconvenience.

I did notice a weird behaviour of voice match (the "ok google" service)
It keeps trying to update the voice model, shows a notification, then goes away for a bit.
Opening the voice match settings on google settings causes flickering on the window, as if it fails and restarts repeatedly. It also failed to initialize during the first boot, so I skipped it.
All other google apps seem to work fine. I've tried both Micro and Stock Gapps

AgentCain said:
I did notice a weird behaviour of voice match (the "ok google" service)
It keeps trying to update the voice model, shows a notification, then goes away for a bit.
Opening the voice match settings on google settings causes flickering on the window, as if it fails and restarts repeatedly. It also failed to initialize during the first boot, so I skipped it.
All other google apps seem to work fine. I've tried both Micro and Stock Gapps
Click to expand...
Click to collapse
Me too

I don't use or load gapps and I never use ok google. I'm degoogling everything in 2021.

New build lineage-15.1-20210313-UNOFFICIAL-flounder.zip has force encryption disabled by default.
Some people say the Nexus 9 lags over time and supposedly removing encryption improves performance. The Nexus 9 is not a daily driver for me so I don't know, but reading the older 14.1 and 15.1 threads, I decided to change the default behavior.
Since 15.1 will never be official, I changed the fstab.flounder from forceencrypt to encryptable.
Code:
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data f2fs noatime,nosuid,nodev,errors=panic wait,check,latemount,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check,latemount,encryptable=/dev/block/platform/sdhci-tegra.3/by-name/MD1
If you want encryption enabled, goto settings, security and privacy, encryption and credentials, encrypt tablet and follow instructions.
If you want encryption disabled, backup all your data, goto TWRP, wipe dalvik/art cache, system, data and internal storage in TWRP. You must also format data in TWRP. Then install the March 13 build and encryption will be disabled by default. You can also change the cache and data to f2fs if you want for potentially better performance.
Going forward, all monthly security builds will have encryption disabled unless you enable it.
PS. That's the only change from the March 9 build. The above has been added to the FAQ now.

bought a nexus9 yesterday, went the noob path (outdated toolkit to unlock bootloader/ root+twrp... updated twrp to 3.5.9.0) then flashed your current rom... (9march) feel smooth and nice!
thanks for continuing working on this device! its a real upgrade from my previous tab (8" tab 3).. we cant all spend money on fancy device, nexus9 is still relevant today with this nice custom rom!
edit2: stupid me of course... now build 2021.03.13 is working well without encryption problem! (was trying to remove encryption following your tutorial with the previous rom)

I think there is a problem with accout registration. Ok google not working but it's impossible to register some account. I try microsoft one for word. It say internet connection is not present. Maybe this can help to solve the problem

Wow! Thanks for this! Since the new XDA update, it has been so awful I stopped using it. I just popped back on after 2 months away from XDA and found this rom! Going to try it soon.
One problem I had was with stadia not working. I don't mean to ask if it does now, but it does seem that the chrome browser version works now (vatrom's version). Can you at least take an educated guess if the new hardware acceleration patch in the repo might help get stadia working properly? I suspected it was either an unsupported codec or an issue with hardware acceleration being the culprit. Thanks

gk1984 said:
One problem I had was with stadia not working.
Click to expand...
Click to collapse
Never heard of stadia and I don't use google chrome browser.

Google Stadia is Google's cloud gaming platform. And no, I didn't ask about Chrome. I simply was trying to ask some clarity about Lineage's hardware acceleration patch vs Barron's, but included context to my situation. I clear8 stated I wasn't exactly asking if Stadia was working, but if the new hardware acceleration patch could impact it and why.
It's pretty unprofessional to blanket statement "I don't use x" and ignore the question. It also hurts your credibility as a developer if you can't explain what's being parched into the code if you directly mention it in the OP. You could simply respond with "I'm not an experienced developer and can't articulate X or Y, I'm just capable of building from source and distributing." We don't know you, we don't know your skill level or knowledge. I'm used to ROM developers or at least those building them to know what they're working on. But your. Blanket statement suggests otherwise.

back again.. and it fixed now! of course, i've downloaded the 20210309 build and couldnt figure a proper way to remove encryption on data partition... I've managed to flash gapps (use an old 16go usb key with microusb connector)..and come back to read CORRECTLY your post and understood my mistake... it was an old build!
Did a clean flash and flashed 0313 build, no more encryped data now! (flashed some nano gapps + magisk) setting up the device, so far so good!

It's great to see some people still have this tablet! They are under $50 used now, but it's a shame about stock performance...

Just some personal screenshoot...

AgentCain said:
I did notice a weird behaviour of voice match (the "ok google" service)
It keeps trying to update the voice model, shows a notification, then goes away for a bit.
Opening the voice match settings on google settings causes flickering on the window, as if it fails and restarts repeatedly. It also failed to initialize during the first boot, so I skipped it.
All other google apps seem to work fine. I've tried both Micro and Stock Gapps
Click to expand...
Click to collapse
I found a solution. Install the Google app from ApkMirror.com and restart the tablet. Should work after that. Looks like it's a common problem with open gapps I. General.

Hey thanks for sharing your rom
Can I dirty flash this rom from the other lineage os 15.1 build?

I'm not the developer, but I wouldn't recommend it. That usually leads to Android being unable to boot. Best to factory reset.

gk1984 said:
I found a solution. Install the Google app from ApkMirror.com and restart the tablet. Should work after that. Looks like it's a common problem with open gapps I. General.
Click to expand...
Click to collapse
Thanks it work for me

[UNOFFICIAL][ROM]ALPHA LineageOS 19.1 for Galaxy Tab E [SM-T560NU] May 7, 2023

This ROM is ONLY for SM-T560NU, NOT SM-T560. I CANNOT make a SM-T560 build as they are different CPU/SoCs.
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
What doesn't work
1. Camera. The stock camera app video recording doesn't work. Use Simple Camera 5.3.1 from https://f-droid.org/en/packages/com.simplemobiletools.camera/ . I have no plans to work on camera.
2. selinux is permissive. I have tried to make this build enforcing for weeks, but when I do, the OS doesn't boot and there is no adb logcat output despite making an "eng" build. Without adb logcat output, it's virtually impossible to determine what is wrong and I'm not spending anymore time on it. If having enforcing mode is important to you, use my 18.1 builds.
3. keyboard bug workaround. When prompted to enter something like a Bluetooth pin or text based password, sometimes the keyboard is not shown on the screen or off screen. The workaround is to goto settings, system, languages & input, on-screen keyboard, Android Keyboard (AOSP), appearance & layout, theme and choose "Material - follow system settings".
This keyboard bug is a LineageOS bug as per
https://review.lineageos.org/c/LineageOS/android_packages_inputmethods_LatinIME/+/325438
4. gapps. Some of you require gapps for whatever reason. I use Aurora Store for my purposes and thus have NO KNOWLEDGE of the current state of gapps.
There are various gapps projects (at least 5 in 2022). Each has pros and cons. It's your job to do the research and find a suitable gapps project. I suggest you allocate at least a couple of hours doing your own research. My rom works by itself fine without gapps. DO NOT talk about gapps in this thread. As a courtesy to gapps users, if you want to talk about gapps, I have opened a new thread at
https://forum.xda-developers.com/t/...m-t35x-sm-t550-sm-t560nu-and-sm-p550.4479285/
so you may discuss gapps wrt to the msm8916 platform. I will NOT be participating in that thread as I do NOT use gapps.
Thanks
1. LineageOS team for source code.
2. Kyle Harrison
- looking through the adb logcat and suggesting that my binder code was too old to work with Android 12's keystore2 code
- for the graphics and legacy camera patches to allow msm8916 to work with Android 12
- for his Motorola LineageOS 19.1 device trees so I could use his patches as a template for msm8916
3. @tarkzim
- adding back audio hal 2.0 and legacy camera hal 1.0 into the LineageOS trees
- helping me think through the msm8916 random reboots which was due to the TCP/IP patches
- maintaing and updating his repos so I can study them for learning purposes
4. pre ALPHA testers @RDS5 and @Sigster for willing to test pre ALPHA builds and leaving feedback.

FAQ - I spent hundreds of hours building this rom. It was frustrating process from Nov 2021 to Aug 2022 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
https://github.com/retiredtab/android_kernel_samsung_msm8916
The device tree files are at
https://github.com/retiredtab/android_device_samsung_msm8916-common/tree/lineage-19.1
https://github.com/retiredtab/android_device_samsung_gtelwifiue/tree/lineage-19.1
https://github.com/retiredtab/device_samsung_gte-common/tree/lineage-19.1
The vendor tree files are at
https://github.com/retiredtab/vendor_samsung_gtelwifiue
https://github.com/retiredtab/vendor_samsung_msm8916-common/tree/lineage-19.1
The manifest.xml (or roomservice.xml) and build instructions for 19.1 are at
https://github.com/retiredtab/LineageOS-build-manifests
Q2. Is this ALPHA 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 2022 with no major issues. I suggest you do a clean install, see FAQ 11, and flash this 19.1 ROM BY ITSELF (no gapps, magisk, etc) and see if you like it. If you do like it and want to add gapps then see FAQ 12.
Q3. What if my app, xyz, doesn't work?
A3. If your app doesn't work, then go back to your old rom.
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. 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 TWRP 3.5.2_9. Get it from
https://sourceforge.net/projects/retiredtab/files/SM-T560NU/TWRP/
Q6. Why should I use this rom?
A6. If you don't like this rom, then don't use it.
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. I don't have the time to help newbies, so please 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
# attach the problem.txt ZIPPED as text files don't seem to get attached properly
Q10. Will you still build 18.1 for this device?
A10. Yes, for rest of 2022, but I will make a decision in January 2023 on how 18.1 and 19.1 will be maintained. If you like to help by building 18.1/19.1, please let me know.
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 19.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.
Let me by crystal clear. YOU NEED TO DO YOUR OWN HOMEWORK selecting between the various gapps offered. There are 5: opengapps, nikgapps, mindthegapps, flamegapps and bitgapps. Each one will have it's own installation instructions. The only recommendation I will offer to use the SMALLEST version of gapps.
Don't be surprised that whatever gapps you use might have problems like "Just a sec", voice not working, updating google play store please wait, etc. These are NOT problems of the OS as the OS will run fine without gapps. These are gapps problems and you must ask in the gapps forum why it doesn't work.
In addition, some of the gapps may not install properly when using TWRP and say "cannot /mnt/system". For those cases, please use the LineageOS recovery.img you can download from
https://sourceforge.net/projects/retiredtab/files/SM-T560NU/LineageOS-recovery/
By flashing the LineageOS recovery.img, it will overwrite the existing TWRP and you will get a different UI.
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. Android does not depend on gapps in order to work.
Questions about gapps, for your courtesy, should be asked at
https://forum.xda-developers.com/t/...m-t35x-sm-t550-sm-t560nu-and-sm-p550.4479285/
Q14. Why isn't my post answered or ignored?
A14. Questions already answered in the FAQ will be completely ignored. Again, I do not use Windows OS or gapps.
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.
7. Remove all unused quick setting "bubbles" from the quick pull down menu. I only need and have 6.
Q17. Does this rom support Magisk for root?
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. With 19.1, legacy devices like ours will NEVER be official due to lack of ebpf support. See https://lineageos.org/Changelog-26/
Also, I don't want the responsibilities that come with being an official maintainer.
Q19. What is the difference between this rom and others?
A19. This rom tries to be pure LineageOS with little to no modifications.
Q20. Will there be any major 19.1 code modifications in the future?
A20. I don't anticipate any major modifications. There may be some 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 19.1 is working.
Q21. Why did you fork the device and vendor trees for 19.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-T357W, 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 have completely decommonized and rearranged the 19.1 msm8916-common tree so it's easier for me to maintain and build.
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. What major code changes are in 19.1 vs 18.1.
A24.
- iptables has been removed in favour of ebpf
- keystore v1 has been replaced with keystore v2 which requires that the binder calls have some built-in security
- audio hal 2.0 has been deprecated
- legacy camera hal 1.0 and snap app have deprecated
Q25. I don't like the taskbar, how do I turn it off?
A25. Choose settings, type task into the search bar. Choose enable taskbar and disable taskbar. This will leave the on screen nav bar. If you want to disable that, go to settings, system, gestures, system navigation, gesture navigation.
Q26. Will this run on the SM-T560 or SM-T561?
A26. No, the SM-T560 and SM-T561 use a different CPU/SoC. The SM-T560NU rom will NOT work on SM T560/SM-T561.
Q27. Okay, I understand the consequences and that this is ALPHA rom and willing to take the risks outlined, now where can I find the rom?
A27. You can download it from https://sourceforge.net/projects/retiredtab/files/SM-T560NU/19.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 in TWRP. This is known has a clean install. Backup your data before a clean install.
19.1 has been my daily driver since March 2022.
May 7, 2023 release notes
1. May 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-05
2. Whatever LineageOS changed since Apr 5 patches. About 7,400 files had to be recompiled.
Apr 12, 2023 release notes
1. Apr 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-04
2. Whatever LineageOS changed since Mar 5 patches. About 23,000 files had to be recompiled.
March 19 , 2023 release notes
1. Mar 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-03
2. Whatever LineageOS changed since Feb 5 patches. About 24,500 files had to be recompiled.
Feb 12, 2023 release notes
1. Feb 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2023-02
2. Whatever LineageOS changed since Jan 5 patches. About 12,500 files had to be recompiled.
Dec 9, 2022 release notes
1. Dec 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-12
2. Whatever LineageOS changed since Nov 5 patches. About 7,100 files had to be recompiled.
Nov 11, 2022 release notes
1. Nov 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-11
2. Whatever LineageOS changed since Oct 5 patches. About 5,400 files had to be recompiled.
Oct 6, 2022 release notes
1. Oct 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-10
2. Whatever LineageOS changed since Sept 5 patches. About 4,300 files had to be recompiled.
Sept 11, 2022 release notes
1. Sept 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-09
2. Switched to different timekeep repo that works with Android 12 and up.
3. Whatever LineageOS changed since Aug 5 patches. About 4,600 files had to be recompiled.
Aug 10, 2022 release notes
1. Aug 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-08
2. Initial ALPHA release to public.

Reserved.

Works great, thank you for your hard work.
My only problem so far is getting Dropbox to work in Mixplorer which I had no problems with in 18.1, but that could be unrelated and there's a way around it either way.

New build called lineage-19.1-20220911-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 in TWRP. This is known has a clean install. Backup your data before a clean install.
19.1 has been my daily driver since March 2022.
Sept 11, 2022 release notes
1. Sept 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-09
2. Switched to different timekeep repo that works with Android 12 and up.
3. Whatever LineageOS changed since Aug 5 patches. About 4,600 files had to be recompiled.

retiredtab said:
This ROM is ONLY for SM-T560NU, NOT SM-T560.
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
What doesn't work
1. Camera. The stock camera app video recording doesn't work. Use Simple Camera 5.3.1 from https://f-droid.org/en/packages/com.simplemobiletools.camera/ . I have no plans to work on camera.
2. selinux is permissive. I have tried to make this build enforcing for weeks, but when I do, the OS doesn't boot and there is no adb logcat output despite making an "eng" build. Without adb logcat output, it's virtually impossible to determine what is wrong and I'm not spending anymore time on it. If having enforcing mode is important to you, use my 18.1 builds.
3. keyboard bug workaround. When prompted to enter something like a Bluetooth pin or text based password, sometimes the keyboard is not shown on the screen or off screen. The workaround is to goto settings, system, languages & input, on-screen keyboard, Android Keyboard (AOSP), appearance & layout, theme and choose "Material - follow system settings".
This keyboard bug is a LineageOS bug as per
https://review.lineageos.org/c/LineageOS/android_packages_inputmethods_LatinIME/+/325438
4. gapps. Some of you require gapps for whatever reason. I use Aurora Store for my purposes and thus have NO KNOWLEDGE of the current state of gapps.
There are various gapps projects (at least 5 in 2022). Each has pros and cons. It's your job to do the research and find a suitable gapps project. I suggest you allocate at least a couple of hours doing your own research. My rom works by itself fine without gapps. DO NOT talk about gapps in this thread. As a courtesy to gapps users, if you want to talk about gapps, I have opened a new thread at
https://forum.xda-developers.com/t/...m-t35x-sm-t550-sm-t560nu-and-sm-p550.4479285/
so you may discuss gapps wrt to the msm8916 platform. I will NOT be participating in that thread as I do NOT use gapps.
Thanks
1. LineageOS team for source code.
2. Kyle Harrison
- looking through the adb logcat and suggesting that my binder code was too old to work with Android 12's keystore2 code
- for the graphics and legacy camera patches to allow msm8916 to work with Android 12
- for his Motorola LineageOS 19.1 device trees so I could use his patches as a template for msm8916
3. @tarkzim
- adding back audio hal 2.0 and legacy camera hal 1.0 into the LineageOS trees
- helping me think through the msm8916 random reboots which was due to the TCP/IP patches
- maintaing and updating his repos so I can study them for learning purposes
4. pre ALPHA testers @RDS5 and @Sigster for willing to test pre ALPHA builds and leaving feedback.
Click to expand...
Click to collapse
Hello. I wanted to thank you for this amazing custom ROM here. I flashed it onto my grandma's old Tab E. It works very well!
Thanks again!

New build called lineage-19.1-20221006-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 in TWRP. This is known has a clean install. Backup your data before a clean install.
19.1 has been my daily driver since March 2022.
Oct 6, 2022 release notes
1. Oct 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-10
2. Whatever LineageOS changed since Sept 5 patches. About 4,300 files had to be recompiled.

Thank you for this ROM. Can you recommend a good media player for this ROM? I've always used VLC, but VLC has no audio on this ROM (Gallery can play videos with audio just fine). I'd like to have a decent media player. I'm using Aurora like you recommended.

zswielder said:
Thank you for this ROM. Can you recommend a good media player for this ROM? I've always used VLC, but VLC has no audio on this ROM (Gallery can play videos with audio just fine). I'd like to have a decent media player. I'm using Aurora like you recommended.
Click to expand...
Click to collapse
I also build 19.1 T710/T810 and just had this question re VLC and it should work for 19.1 SM-T560NU. See post #20 from @lpedia
https://forum.xda-developers.com/t/...or-sm-t710-oct-10-2022.4480065/#post-87625761
Aurora Store is down for me right now so I can't verify by downloading VLC on 19.1 SM-T560NU.

retiredtab said:
I also build 19.1 T710/T810 and just had this question re VLC and it should work for 19.1 SM-T560NU. See post #20 from @lpedia
https://forum.xda-developers.com/t/...or-sm-t710-oct-10-2022.4480065/#post-87625761
Aurora Store is down for me right now so I can't verify by downloading VLC on 19.1 SM-T560NU.
Click to expand...
Click to collapse
Thank you for the info. The audio output sort of fixed the issue, but the sound cuts out for a second every now and then when playing a video file, so there seems to be an issue still.

zswielder said:
Thank you for the info. The audio output sort of fixed the issue, but the sound cuts out for a second every now and then when playing a video file, so there seems to be an issue still.
Click to expand...
Click to collapse
I don't use the SM-T560NU on a regular basis, but I downloaded VLC from Aurora Store, now that it works again, and played a video for 20 minutes and have no sound cuts at all.

retiredtab said:
I don't use the SM-T560NU on a regular basis, but I downloaded VLC from Aurora Store, now that it works again, and played a video for 20 minutes and have no sound cuts at all.
Click to expand...
Click to collapse
Do you think a resolution of a video file should affect that at all? Before I upgraded to this ROM, I was on Lineage 16, and my tablet couldn't handle 1080p files, so I was only watching 720p. With this ROM, it can play 1080p fine (no issue with the native Gallery player), but when I play 1080p video with VLC, the sound cuts off momentarily here and there. If you have any suggestions, I'd very much appreciate it.

zswielder said:
Do you think a resolution of a video file should affect that at all? Before I upgraded to this ROM, I was on Lineage 16, and my tablet couldn't handle 1080p files, so I was only watching 720p. With this ROM, it can play 1080p fine (no issue with the native Gallery player), but when I play 1080p video with VLC, the sound cuts off momentarily here and there. If you have any suggestions, I'd very much appreciate it.
Click to expand...
Click to collapse
The video I was watching is 1080p (h.264) with audio aac encoding. It actually played 40 minutes after I wrote the initial reply with no audio dropouts.
I suggest you look for a DRM free 1080p video somewhere on the Internet that's public domain and shows this problem so I can download and see if it happens on my tablet.
Also, download an app called MediaInfo (8MB file) by MedaArea.net from Aurora Store. It's ad-free and contains no privacy trackers according to Aurora Store. Use that app to see what audio encoding is being used in your 1080p video.
If there's no obvious answers to VLC dropping audio, I guess you will have to find another player if native Gallery player works fine.

Hello. Is there a chance to make this rom to sm t560?

New build called lineage-19.1-20221111-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 in TWRP. This is known has a clean install. Backup your data before a clean install.
Nov 11, 2022 release notes
1. Nov 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-11
2. Whatever LineageOS changed since Oct 5 patches. About 5,400 files had to be recompiled.

New build called lineage-19.1-20221209-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 in TWRP. This is known has a clean install. Backup your data before a clean install.
19.1 has been my daily driver since March 2022.
Dec 9, 2022 release notes
1. Dec 5 security patches as per https://review.lineageos.org/q/topic:S_asb_2022-12
2. Whatever LineageOS changed since Nov 5 patches. About 7,100 files had to be recompiled.

Hi, is there any chance to make it also work for SM-T560?
Thanks a lot

cannabis4711 said:
Hi, is there any chance to make it also work for SM-T560?
Thanks a lot
Click to expand...
Click to collapse
SM-T560/SM-T561 doesn't support this rom.

cannabis4711 said:
Hi, is there any chance to make it also work for SM-T560?
Thanks a lot
Click to expand...
Click to collapse
those use a spreadtrum SoC (sc8830) and the source code for their kernels isnt up to date, and the latest port was android 7.1.2 however whoever ported it violated the GPL and didnt release the source code, so the most recent i could find for the SM-T560's kernel is this
device tree, vendor.
the T560NU however has much better community support as it uses the MSM8916 SoC, so thats why this rom supports it.

[UNOFFICIAL][ALPHA] LineageOS 16.0 For Nexus 9 (WIFI) [June 21, 2023]

BEFORE YOU decide to try this rom, please read all of post 1, 2, 3 and 4 (about 10 minute read). If you think this is unreasonable, then stop reading and use 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 this rom.
What works
I only test what I use. There could be other things that work or don't work. Let me be clear since there are people who don't seem to understand this. I cannot test things that I don't have like paid streaming/gaming, NFC, miracast or apps that I don't use. They may work or they may not work.
If you want to know if something works that's not listed here, then you need to try it for yourself. If that's not an acceptable or reasonable answer, then stop reading and find another rom that meets your requirements. I built this rom for myself to use and thought that some in the community might benefit by sharing it. If this rom doesn't meet your requirements, then delete it and use whatever does.
1. audio over bluetooth
2. wifi
3. brightness
4. external audio
5. GPS - a bit slow to get a fix/lock
6. audio through headphone jack
7. camera
8. deep sleep
9. DRM (level 3)
10. selinux enforcing
What doesn't work
1. The hardware composer doesn't work properly in 16.0. This commit below
https://github.com/linckandrea/andr...mmit/884e66dee68d906ff8b228bf47db533edecaab38
turns on the GPU to do all the graphics work. Depending on your apps, this may work well or cause lags. If it lags, I CANNOT fix this. If your app lags, go back to your old rom. Keep this in mind if you find your apps laggy and slow. For me, I can play Clash Royale for 30 minutes with no lag thanks to some slight code changes that I made from @linckandrea's repos.
Source code
The kernel is at
https://github.com/linckandrea/android_kernel_htc_flounder/tree/lineage-16.0
The other source code and build instructions are in the FAQ 9.
Thanks
1. LineageOS for source code
2. @linckandrea for 16.0 source code
3. @MSe1969 for backporting the monthly security patches to the 16.0 branch and making them publicly available on gerrit.

You must read the FAQ before posting questions.
FAQ
Q1) Does the build work on Nexus 9 LTE?
A1) I have no idea. I only have the Nexus 9 wifi so I don't know if it will work on LTE. If you try the wifi build on the LTE, you may end up with a bricked device. Questions regarding LTE will go unanswered.
Q2) Application xyz doesnt' work. Can you fix it?
A2) I only fix what I use. If you use app xyz and it doesn't work, then go back to the last rom that worked for you. In addition, some of the code is not open source and in proprietary blob format so it's not possible to make changes.
Q3) My tablet hangs or crashes. This build is slow and buggy. Can you fix it?
A3) Go back to the last working stable rom for you. Some of the code is not open source and in proprietary blob format so it's not possible to make changes.
Q4) Do you plan to update the rom?
A4) Yes as long as I have high speed Internet, I wil try to release the rom monthly to incorporate the security patches.
Q5) What TWRP should I use?
A6) You must use 3.5.0_9-0 from
https://dl.twrp.me/flounder/
Q6) What is the difference between this rom and variants?
A6) Use whatever fits your needs. This is a stock LineageOS build with no modifications. I only offer this as an option for those who want or need a new rom and can't build it themselves.
Q7) Will there be a 17.1, 18.1, 19.1 or 20 build?
A7) Do not ask for higher versions. I'm an unpaid volunteer building this on my own time. Any questions regarding ETAs will go unanswered. If you want a newer version, then you can build it yourself.
Q8) Should I upgrade from stock or 14.1/15.1 to 16.0?
A8) It's entirely up to you. If you do upgrade, you will need to backup your data, wipe dalvik/art cache, system, data and internal storage in TWRP. You must also format data in TWRP. You cannot dirty flash from stock or 14.1/15.1 to 16.0, it must be a completely clean fresh install.
Q9) Can I build this rom myself? Where can I find the source and/or kernel source code?
A9) This is one of the few roms where it required no edits or changes to make it work. Follow the instructions at
https://wiki.lineageos.org/devices/flounder/build
The device tree is at
https://github.com/retiredtab/android_device_htc_flounder
The kernel tree is at
https://github.com/linckandrea/android_kernel_htc_flounder/tree/lineage-16.0
The vendor tree is at
https://github.com/TheMuppets/proprietary_vendor_htc/tree/lineage-16.0
Here's the manifest.xml
XML:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="retiredtab/android_device_htc_flounder" path="device/htc/flounder" remote="github" revision="lineage-16.0_update" />
<project name="linckandrea/android_kernel_htc_flounder" path="kernel/htc/flounder" remote="github" revision="lineage-16.0" />
<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="lineage-16.0" />
</manifest>
You will also need to download the remove-liboemcrypto.diff if you're building from source because I couldn't get Disney+ to work with liboemcrypto.so. If you are NOT building from source, you don't need this patch file as it's already included in the 16.0 code.
To apply this patch,
Bash:
# cd into your code directory
# now cd into vendor
cd vendor/htc
# apply the patch
patch -p1 < ~/remove-liboemcrypto.diff
# that will remove the command to copy liboemcrypto.so to the final rom build
If you are building from source, then you need to apply the monthly security patches as shown below. Otherwise, the security patches are already built into the rom.
Bash:
# sync everything
repo sync
# now get all the 16.0 security patches that were not merged into LineageOS gerrit starting with
repopick -t P_asb_2022-05
repopick -t P_asb_2022-06
repopick -t P_asb_2022-07
repopick -t P_asb_2022-08
repopick -t P_asb_2022-09
repopick -t P_asb_2022-10
repopick -t P_asb_2022-11
repopick -t P_asb_2022-12
repopick -t P_asb_2023-01
repopick -t P_asb_2023-02
# and so on until you reach the current month
Q10) Why is my question not answered?
A10) It's likely because it's in the FAQ or it's off topic or you are asking something that I cannot answer for the reasons stated in this FAQ.
Q11) How is this 16.0 build different from the ones already on XDA?
A11) I modified linckandrea's code to meet my needs mainly for playing Clash Royale without lag. Without my modifications, the game would lag/slowdown after 15 minutes. With my modifications, I can play 30 minutes or more without lag.
Q12) Is the video hardware accelerated in 16.0?
A12) No. Hardware composer is broken in 16.0 and the GPU is used to do all the graphics.
Q13) Is encryption enabled by default?
A13) Some people say the Nexus 9 lags over time and supposedly removing encryption improves performance. The Nexus 9 is not a daily driver for me so I don't know, but reading the older 14.1 and 15.1 threads, I decided to change the default behavior so that encryption is disabled by default.
If you want encryption enabled, goto settings, security and privacy, encryption and credentials, encrypt tablet and follow instructions.
Q14) Can you build a variant like slimrom, crDroid, etc?
A14) No, but you can following the instructions and source code above that has been provided.
Q15) What gapps should I use?
A15) I use Aurora Store and have no idea what gapps works. You MUST DO YOUR OWN HOMEWORK in picking gapps. If you must use gapps, pick the smallest one to get best performance.
Q16) Where can I download this rom?
A16) See
https://sourceforge.net/projects/retiredtab/files/Nexus 9/16.0/

Release notes
June 21, 2023
1. All UNOFFICIAL 16.0 security patches including June 5th, 2023 as per https://review.lineageos.org/q/topic:P_asb_2023-06
May 11, 2023
1. All UNOFFICIAL 16.0 security patches including May 5th, 2023 as per https://review.lineageos.org/q/topic:P_asb_2023-05
Apr 18, 2023
1. All UNOFFICIAL 16.0 security patches including Apr 5th, 2023 as per https://review.lineageos.org/q/topic:P_asb_2023-04
Mar 23, 2023
1. All UNOFFICIAL 16.0 security patches including Mar 5th, 2023 as per https://review.lineageos.org/q/topic:P_asb_2023-03
Feb 19, 2023
1. Initial 16.0 ALPHA release.
2. All UNOFFICIAL 16.0 security patches including Feb 5th, 2023.

Reserved.

New build called lineage-16.0-20230219-UNOFFICIAL-flounder.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 in TWRP. This is known has a clean install. Backup your data before a clean install.
Release notes
Feb 19, 2023
1. Initial 16.0 ALPHA release.
2. Includes all UNOFFICIAL 16.0 security patches including Feb 5th, 2023.

Thanks you very good rom great performance! except camera doesn't work

frixed18 said:
except camera doesn't work
Click to expand...
Click to collapse
Just tested camera and it works fine on my device (front and back).

What Android version is this?

9

Thanks for your work! On my device the camera also doesn't work and the YouTube app doesn't load properly. The YouTube kids app works fine so my kids are happy anyways. The camera app just stays black, it doesn't ask for any permissions. That's usual the case when you first start the app.

S213752 said:
On my device the camera also doesn't work and the YouTube app doesn't load properly.
Click to expand...
Click to collapse
As I mentioned on March 5, stock camera photo and video works for me and I just tested it again today (March 22) and both still work.
S213752 said:
The YouTube kids app works fine so my kids are happy anyways. The camera app just stays black, it doesn't ask for any permissions.
Click to expand...
Click to collapse
I don't use youtube. I use newpipe and it works fine. I won't be troubleshooting why youtube doesn't work.

New build called lineage-16.0-20230323-UNOFFICIAL-flounder.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 in TWRP. This is known has a clean install. Backup your data before a clean install.
Release notes
Mar 23, 2023
1. All UNOFFICIAL 16.0 security patches including Mar 5th, 2023 (about 25,000 files had to be recompiled).
2. Stock camera works. If it doesn't work, try going into settings, apps, camera, storage, and clear both cache and storage and REBOOT the device. Open camera 1.51.1 (87) also works fine. I already verified that camera works in the initial Feb 19 release and it works in Mar 23, 2023. I will not be troubleshooting this at all.

retiredtab said:
As I mentioned on March 5, stock camera photo and video works for me and I just tested it again today (March 22) and both still work.
I don't use youtube. I use newpipe and it works fine. I won't be troubleshooting why youtube doesn't work.
Click to expand...
Click to collapse
There are a few more apps that won't start right, but if things work fine for your device I can understand you won't do troubleshooting. I've found an older los16 build (16.0-20210622) where the camera and Youtube app seems to work fine. I'm also using your 15.1 build and there everything also works fine. So there is something going on.
So if there are more people with these issues they can use the 15.1 build or use the old 16 build.

please help
After flash this latest ROM using recommened TWRP version, once it finish the boot up process, it is always factory data reset and reboot into TWRP, this process is looping back and forth without enter to the system?
What could I do to fix it?

Format data

Formated multiple times and no way to boot into system

New build called lineage-16.0-20230418-UNOFFICIAL-flounder.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 in TWRP. This is known has a clean install. Backup your data before a clean install.
Release notes
Apr 18, 2023
1. All UNOFFICIAL 16.0 security patches including Apr 5th, 2023 (about 25,000 files had to be recompiled) as per https://review.lineageos.org/q/topic:P_asb_2023-04

Anyone can help please ？it will automatic factory reset data each time after reboot and no way to enter to the system.

Did you format data (follow the installation instructions)?

SirRGB said:
Did you format data (follow the installation instructions)?
Click to expand...
Click to collapse
Format data in TWRP, I did this part and what else I need to follow ?