Unofficial LineageOS 15.1 - Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth

FINALLY got my source working, after a few frustrating derps on my part. Linked will be the changelog for Lienage, but nothing for our device. They've made changes to our Taimen tree, so there's a positive. This build is updated to the latest July patch, and you will not get any vendor mismatch thing. I made sure to fix that issue before even posting this. 8.1.0 (OPM2.171026.006.H1, Jul 2018) from the Google Gods.
I completely started over and flashed that firmware before flashing my Lineage build. No idea what will happen if you update, but I'm sure the firmware will complain. Vendor mismatch and TWRP might encrypt. I didn't just update Vendor image and flash a build that's on July. Root is working and Flash Kernel is too Stock kernel is forked from Carbon's ROM. TWRP seems to be decrypted (no passcode, fingerprint, etc)
I AM NO DEVELOPER! I just compile from Lineage's source and bless the community with an updated build! I have an Iphone (and Pixel 2XL), so I will try to keep up with any changes from Lineage. Maybe a weekly update, if I don't kill my source again LOL! OH!! Do NOT setup Google Now via setup wizard because you first need to update it via Play Store! Then you can hold down the home button and configure "OK Google" Cellular data should work, but I have my SIM in an Iphone, and I'm too lazy to swap.
https://www.lineageoslog.com/15.1 <---Changes of Lineage
https://developers.google.com/android/images <--- Factory Images (H1, regardless if you have T-mobile)
https://www.androidfilehost.com/?fid=5862345805528049535 <--- Current build
https://forum.xda-developers.com/pixel-2-xl/development/taimen-flash-kernel-1-00-t3702057 <---- Flash Kernel
Edit: Looks like restoring JUST data from an old Lineage build should be okay. You'll have to update all your apps VIA Play Store, but that's if you're as lazy as I am, and don't wanna restore all your apps

This is great! I'm running this now, only bugs I think are worth noting are related to the Google Camera, it's crashing at launch, but other camera applications work fine. Bluetooth works but I'm having trouble pairing an android wear device.
Thank you for compiling this, I'll keep testing new builds if you keep posting them!

First of, my apologizes to @RaymanFX , as I unintentionally hijacked the original thread. Obviously that was not my intention. I apologize, sir!
So, that camera issue is fixed, along with "now playing" working. I think it was due to jumping around with manifests, in hopes to stay current. I know the Taimen tree is current and Wahoo is a bit behind. I think I will try learning how to merge fixes and staying up to par with LineageOS. I tried to Frankenstein it. I really have a good friend, @deedwar to thank for this build. I kept having crashes at the start of the setup. I asked if he could help me and build Lineage, and he did just that, with Lineage's official trees.
I realized that I probably had to reflash factory images to get it to boot. I realized this, after I couldn't boot another ROM.
So what can I provide, moving forward?
- Well, an apology to Ray. Look, I'm not that type of guy to steal the spotlight. I understand the need for a separate post
- Compile a build when I notice changes to our device.
- Try to figure out how to fix things, or at the least, merge bugs fixes via a few bug tracking sources.
- Make a github (well I have one) but that has changes to whatever I may do.
- See if I can include Lineage's setup wizard without conflicting with GAPPS that are built in. Couldn't produce a build without GAPPS, as when you go to flash them, it won't stick.
I am simply a builder, if that's the right term aha. I just sync and build. No fiddling with folders or coding, as I don't know how to.
So, without further delay: Here goes the current build!
https://www.androidfilehost.com/?fid=5862345805528056608
July fingerprint
No vendor mismatch
Now playing and camera fixed
Android 8.1.0 r41
Up to date with Lineage's sources
GAPPS built in. You'll have to hold the home button to setup OK Google because it's not part of the setup.

@draymond1987
Thank you for sharing.:good:

Waiting for two builds to finish, which I'll post, tomorrow. Updated with latest Lineage changes. Seen they did something to our device tree. Can't see any commits that happened, soooo ¯\_(ツ)_/¯
It looks like the usual things. Code clean up, updates to certain things in the build. Like I said, I just sync and compile, so I am a bit oblivious.
One build is gonna be compiled with Clang and have Flash Kernel baked in, if all goes right!
Other build is just straight up Lineage and it's changes. Oh, and the kernel is forked from Carbon. I'll obviously give credit once the builds are up. Don't want to @ somebody and then the build doesn't work. That would be rude, in my opinion.

Thread closed as per OP's request.

Related

[ROM][6.0.1] UNOFFICIAL CyanogenMod 13.0

Presenting CM13 unofficial. Built from mostly pure CyanogenMod sources, with a few tweaks that I try to keep updated on my github. This is only possible due to the work of Ziyan and MWisBest.
Instructions
First time flashing CM13 to your toroplus (or coming from another ROM)?
Unlock & install a recovery
Wipe data & cache partitions
Flash CyanogenMod.
Optional: Install the Google Apps addon package.​
Updating from a previous build?
Just install the latest ROM zip. If you had Google Apps installed, they will be reinstalled automatically.​
Click to expand...
Click to collapse
Downloads
Latest cm-13.0 build: https://www.androidfilehost.com/?fid=24588212152305191
Final cm-12.1 build: https://www.androidfilehost.com/?fid=24438995911970260
All builds: https://www.androidfilehost.com/?w=files&flid=23531
Unofficial TWRP recovery: https://www.androidfilehost.com/?fid=24459283995311440
Google Apps: http://opengapps.org/
- Platform: ARM
- Android: 6.0
- Variant: pico (recommended), or nano
Bugs
LTE Data does not work. (3G works)
XDA:DevDB Information
UNOFFICIAL CyanogenMod 13.0 (DDK 1.9), ROM for the Samsung Galaxy Nexus
Contributors
musical_chairs
Source Code: https://github.com/CyanogenMod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2014-09-25
Last Updated 2016-07-15
now with Marshmallow!
Will this be updated to work with the new GPU drivers? Thank you!
Sent from my LG-LS980 using XDA Free mobile app
illinoissparks18 said:
Will this be updated to work with the new GPU drivers? Thank you!
Sent from my LG-LS980 using XDA Free mobile app
Click to expand...
Click to collapse
Short answer: yes. I'm going to try grabbing the relevant code from MWisBest's githib. If it turns out to be too involved for my limited skills, it will have to wait until Ziyan submits the changes to CM.
musical_chairs said:
Short answer: yes. I'm going to try grabbing the relevant code from MWisBest's githib. If it turns out to be too involved for my limited skills, it will have to wait until Ziyan submits the changes to CM.
Click to expand...
Click to collapse
OK I am going to be on board with testing for sure. I left a post in the now no longer current official thread that I flashed the last official build yesterday and I had perfect 3G to LTE to 3G handoff, rock solid WiFi strength, basically everything seemed to work very well. I am looking forward to seeing how things progress. I haven't been able to keep any of the official CM builds from bootlooping until now. Hopefully you stick with it because I am getting better performance from this device than I have seen in a long while
Sent from my Galaxy Nexus using Xparent Gray Tapatalk 2
musical_chairs said:
Short answer: yes. I'm going to try grabbing the relevant code from MWisBest's githib. If it turns out to be too involved for my limited skills, it will have to wait until Ziyan submits the changes to CM.
Click to expand...
Click to collapse
Awesome!! Thank you!!
Sent from my LG-LS980 using XDA Free mobile app
I should've had a machete to hack through the jungle of build errors from pulling a modified OmniROM device tree into a CyanogenMod build. Looks like the build is rolling now though, with any luck it might just complete successfully - who knows, it might even boot.
The only thing slower around here than me is my poor old computer.
Its kind of ironic that the Galaxy Nexus was the first official LTE device for Sprint and I am only just recently starting to get LTE on a semi regular basis.
@musical_chairs, take your time with your builds. I assure you that they are appreciated. Now that this device is actually getting decent (for Sprint) signal and still has current builds makes it more enjoyable to use than just about any time I can remember....I just miss Imoseyon's Lean kernels. I got GREAT battery on those. They were compiled in the now deceased (I think) CMRemix ROMs but the LTE is definitely a plus
Update: For now, I have stopped working on building CyanogenMod with the DDK 1.9 drivers. I was ending up with a completely unsustainable mess of a device tree, and was still running into build errors. If new drivers are what you want, use FML. I'll focus on keeping the regular CM builds updated for the time being.
musical_chairs said:
Update: For now, I have stopped working on building CyanogenMod with the DDK 1.9 drivers. I was ending up with a completely unsustainable mess of a device tree, and was still running into build errors. If new drivers are what you want, use FML. I'll focus on keeping the regular CM builds updated for the time being.
Click to expand...
Click to collapse
Link to toroplus build for fml?
Zeinzu said:
Link to toroplus build for fml?
Click to expand...
Click to collapse
I'm following its developements, but haven't had time to try it personally yet.
http://forum.xda-developers.com/galaxy-nexus/sprint-develop/rom-fml-fork-life-10-13-2014-t2903695
Thanks for trying anyhow. I'm glad cm11 still has a fighting chance with the GNex, thanks to you, and all the others who are able to help out.
We're all waiting for cm12 to get to a buildable state. In the meantime, I've been working on upgrading my build box. My old machine was just barely capable of building android, the 'new' one isn't new but it was a real beast in its day. Time for a clean build has dropped from a day and a half to two and a half hours. I'm happy...
jd14771 said:
just curious, how difficult is it to compile roms? Do you need to know how to write your own code or is it over glorified copy and pasting with packages and stuff?
Click to expand...
Click to collapse
I do a lot of copying and pasting, a lot of reading guides, and a whole lot of google-ing. I don't know how to write my own code, but I have lots of experience with applying patches. Compiling roms is not that hard if you're a Linux user, have a working knowledge of the command line, and have a basic understanding of git. Take away any one of those things and it becomes a whole lot harder.
jd14771 said:
Yeah i haven't gotten to play with linux, nor do i know what git's are (i think they are large batch's of code posted in plain text?) . always wanted to try but don't have the time.
Click to expand...
Click to collapse
git is the software the devs use to keep track of changes in the code. Most Android devs have their git repositories on Github, those are probably what you are thinking of. Every little change (called a 'commit') has its own unique hash number. It's pretty amazing, you can look through somebody else's commits and find one that fixes a bug you are working on, or split tens of thousands of changes in half, then in half again, then in half again, etc., and pinpoint the exact commit that causes a bug on your system - though that's more useful in Linux kernel development than in Android.
I don't really have the time either, but it's such a fun hobby...
Using quickboot?
Coming from Vanir. Really like the facility quickboot gives. Anyone "enabled" it? I can't seem actually show the field to turn it on. Settings search finds it, but that's it... Noticed Dev options is hidden also. What's up?
Props for keeping CM11 updated. Really like I can actually use SMS in Hangouts.
I haven't been following the nightly changes since toroplus went dark, but I ran a build today--nothing special, just the latest cm...whatever changes they are. I could post it but don't know if I should make another thread or just link to it in here.
Anything substantial get added to general cm in the last few months?
I tried to run a build of cm12 but it looks like things still aren't ready for building yet, either that or I'm not sure how to switch back and forth between the cm11 repo and cm12 without getting repo update errors.
yotvb531 said:
I tried to run a build of cm12 but it looks like things still aren't ready for building yet, either that or I'm not sure how to switch back and forth between the cm11 repo and cm12 without getting repo update errors.
Click to expand...
Click to collapse
I got cm12 built and booting for toro for the first time today. I'm trying to get mobile data working on that, then I'll give toroplus a shot. Looks like it shouldn't be too much trouble. Feel free to post any of your builds here, or start your own thread if you prefer.
Here's my cm11 build from yesterday--equivalent to a plain nightly. It's been running fine since I dirty flashed it last night. Md5sum is linked as well and noted below.
https://www.dropbox.com/s/lp4j3yayuktmlot/cm-11-20141227-UNOFFICIAL-toroplus.zip?dl=1
https://www.dropbox.com/s/z1b72j7oh70eg5w/cm-11-20141227-UNOFFICIAL-toroplus.zip.md5sum?dl=1
MD5 Sum: e6c265c57e00b4949362d6ff53c9a799
Well I got cm12 built and booting on toroplus, unfortunately the RIL is completely borked, so no cell service at all at this point. I'll keep working on that, in the mean time check out the updated cm11 build in the post right above this one.

[Q] Building unofficial AOSPA ROM - Need Help

Good morning,
as per thread title I'm trying to build my first custom ROM.
As it is my first time ever trying this, instead of starting from scratch I decided to port an existing ROM to our device.
I decided to go for Paranoid Android (AOSPA) ROM, for two reasons: I previously used and liked very much the KitKat version, and there is currently no port of this ROM.
I read a lot of guides on how to do this, and while I learnt a lot, I'm still not quite sure on how to properly do this. So I thought I might ask for some help.
What I learnt so far is this:
1) Fork Paranoid Android's manifest and add compatible device and kernel repositories (I chose @MWisBest's device repo)
2) Fork Paranoid Android's vendor_pa project and add device support
3) Fork device tree and adapt some makefiles
What I still don't quite get is:
1) Apart for device-specific fixes, is this enough to TRY a build?
2) Regarding device, are there some specific fixes to make a working ROM? (e.g. I knew something about block-based OTAs so I disabled them following ParanoidAndroid's change #68 on Gerrit)
You can see my work on GitHub, search for my username Bruno3589 (I'm not allowed to insert URLs right now, I need to make >10 posts).
I'll try a build ASAP, but it might take a while since I'm limited in terms of internet connection and time.
Any help or suggestion is really appreciated!
Thanks in advance and have a good day
P.S. I know MWisBest's device unifies all variants (tuna) instead of making separate ones (maguro,toro,toroplus), I thought it would be useful to have a single build.

Unofficial build help?

I'm trying to build for a device that has no known Android 10 device trees that I can find. I think I fleshed out the trees pretty well by following some sister/cousin devices and extracting a lot of stuff from the rooted phone itself, but my build fails at 2% due to a missing output file. The missing libdss.so file should be built as part of the kernel (whose source I have), but the build clearly isn't happening (or isn't happening in time to be recognized by the build system.)
I tried to build the kernel as a standalone module to see what might be wrong, and in trying to do that I can't seem to resolve all the issues with dependencies for cross-compilation to arm64. I've built for devices with existing trees by cherry-picking what I needed, but I've never built for something from the ground-up like this. I don't want to make the ROM with a pre-built kernel as the end-goal would be to become official. The attached image is the exact error I'm receiving, and the following links are to all of my source repositories that I'm using in addition to the Lineage17.1 base. Any help would be appreciated. I work as a full-time dev by day, I don't mind slogging around in some code if that's what I takes, I've just reached the end of my troubleshooting knowledge here and am not sure what the next step might be.
https://github.com/polaarbear/android_device_motorola_troika_sprout
https://github.com/polaarbear/android_device_motorola_universal9610-common
https://github.com/polaarbear/android_vendor_motorola_universal9610-common
https://github.com/polaarbear/android_kernel_motorola_universal9610

[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][ROM]ALPHA LineageOS 20 for Galaxy Tab E [SM-T560NU] June 23, 2023

This ROM is ONLY for SM-T560NU, NOT SM-T560. I CANNOT and WILL NOT make a SM-T560/SM-T561 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
8. camera
9. selinux enforcing
10. DRM L3
11. deep sleep
What doesn't work/What isn't tested
1. 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.
2. full disk encryption has been deprecated in Android 13 (LineageOS 20).
Source Code
The build instructions, source code and manifest are listed in post #2 FAQ #1. The kernel source code is at
https://github.com/retiredtab/android_kernel_samsung_msm8916/tree/lineage-20.0
Thanks
1. LineageOS team for source code.
2. LineageOS-UL team for merging, maintaining the legacy patches needed for old devices into one common reposistory so everyone can benefit.
https://github.com/orgs/LineageOS-UL/people
3. 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. If you think it's unreasonable to read this FAQ, then don't use this rom. Thank you.
Q1. Where are the source and kernel source files?
A1. The kernel source files are at
https://github.com/retiredtab/android_kernel_samsung_msm8916/tree/lineage-20.0
The device tree files are at
https://github.com/retiredtab/android_device_samsung_msm8916-common/tree/lineage-20.0
https://github.com/retiredtab/android_device_samsung_gtelwifiue/tree/lineage-20
https://github.com/retiredtab/device_samsung_gte-common/tree/lineage-20
The vendor tree files are at
https://github.com/retiredtab/vendor_samsung_gtelwifiue/tree/lineage-19.1
https://github.com/retiredtab/vendor_samsung_msm8916-common/tree/lineage-20
The manifest.xml (or roomservice.xml) and build instructions for 20 are at
https://github.com/retiredtab/LineageOS-build-manifests/tree/main/20/msm8916
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 Jan 2023 with no major issues. I suggest you do a clean install, see FAQ 11, and flash this 20 ROM BY ITSELF (no gapps, magisk, etc) and see if you like it.
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. Do I need to erase everything and format my data?
A10. 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.
Q11. What gapps should I use?
A11. 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.
Q12. I'm having problems with gapps, can you answer why it's not working?
A12. 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.
Q13. Why isn't my post answered or ignored?
A13. Questions already answered in the FAQ will be completely ignored. Again, I do not use Windows OS or gapps.
Q14. What speed up/optimization tips do you suggest?
A14.
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.
Q15. Does this rom support Magisk for root?
A15. 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.
Q16. Will this rom ever become official?
A16. Starting 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.
Q17. What is the difference between this rom and others?
A17. This rom tries to be pure LineageOS with little to no modifications.
Q18. Will there be any major 20 code modifications in the future?
A18. 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 20 is working.
Q19. Why did you fork the device and vendor trees for 20?
A19. 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 20 msm8916-common tree so it's easier for me to maintain and build.
Q20. Can you build a variant of this device? For example, a LTE or S-pen version.
A20. 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.
Q21. Can I load this rom on a variant devivce like LTE or S-pen version?
A21. 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!
Q22. I don't like the taskbar, how do I turn it off?
A22. 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.
Q23. Will this run on the SM-T560 or SM-T561?
A23. No, the SM-T560 and SM-T561 use a different CPU/SoC. The SM-T560NU rom will NOT work on SM T560/SM-T561. I CANNOT and WILL NOT build SM-T560 and SM-T561.
Q24. 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?
A24. You can download it from https://sourceforge.net/projects/retiredtab/files/SM-T560NU/20/
Release notes
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.
June 23, 2023
1. Initial 20 ALPHA public release.
2. Incorporates June 5th security patches as per https://review.lineageos.org/q/topic:"T_asb_2023-06"
Reserved.

Categories

Resources