Develop Bugs

[ROM][AOSP][4.4/6.0/7.1] Unlegacy Android Project

The Unlegacy-Android Project​Introduction
Unlegacy-Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy-Android was born.
This organization's goal is not to create feature packed ROMs, but to create a base ROM in such a way that custom ROM developers can easily adapt the changes. We're good at (properly) fixing compatibility issues between newer Android versions and older devices, among other core things. The "bells and whistles" like themes we leave to others.
The first public build here had something exclusive for the Galaxy Nexus, yet unseen on any other OMAP4 device: all RAM carveouts reserved for Ducati (the multimedia subsystem of OMAP4, responsible for hardware-accelerated video decoding, encoding and camera functionality) have been switched over to CMA.
A few words for those who see CMA for the first time:
The Contiguous Memory Allocator (CMA) makes it possible for device drivers to allocate big contiguous chunks of memory after the system has booted.
The main difference from the similar frameworks is the fact that CMA allows to transparently reuse memory region reserved for the big chunk allocation as a system memory, so no memory is wasted when no big chunk is allocated. Once the alloc request is issued, the framework will migrate system pages to create a required big chunk of physically contiguous memory.
Click to expand...
Click to collapse
This means that a total of 996 MB physical memory is available to the system, while keeping Ducati fully working - this is a huge step forward, coming from the 694 MB available in the last factory image released by Google (Android 4.3). This gives the OS access to an additional 300MB of RAM.
While CMA was just recently implemented for this device, thanks to one of our developers (let's just call him Luden), it's quite stable: even under heavy memory pressure, the system manages to free up the required memory in order to start up Ducati and launch the requested multimedia functionality in a few seconds at most.
Installation
For Marshmallow (6.0) and below, It's important that /system needs to be unmounted before installing the ROM - some recoveries tend to leave it mounted after performing operations on it.
If you're planning to install GApps, be sure to read the second post!
Aside from these, installation and upgrading is no different than on other ROMs.
Problems
While we weren't able reproduce any CMA-related problems, hidden ones can still arise. In most cases, these problems will be either lost Ducati functionality (no multimedia capabilities) until rebooting, or a kernel panic (hard reboot) - upon noticing any of these, be sure to grab a logcat/dmesg and/or last_kmsg and send it to us (preferably by attaching it to a post in this thread).
Other than that, these are bugs we're aware of in the current build:
- The RIL on LTE devices (toro, toroplus) isn't fully working; calls and texts should be OK, but expect no data.
- Sound pops can be observed, mostly when using touch sounds (this is being investigated)
- Some exotic video formats or camera modes might not be perfect - if you notice any artifacts or green spots (the issue that happened in the past), report the details in this thread
- Inverted colors mode not working
- Tricky connection to some 5 GHz Wi-Fi networks
- SELinux is in Permissive mode (this isn't a problem for most people, just mentioned it here as extra information)
If you notice anything else, be sure to report it in this thread. While we're kind of busy, we usually read the thread and acknowledge the bug reports, even if I don't reply directly to them.
Downloads
See: http://builds.unlegacy-android.org.
As usual, feedback is appreciated
Want to support development? You can consider donating, we've spent countless of hours with this
XDA:DevDB Information
Unlegacy Android Project, ROM for the Samsung Galaxy Nexus
Contributors
Ziyan, MWisBest, Android-Andi
Source Code: https://github.com/Unlegacy-Android/
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Version Information
Status: Stable
Created 2016-03-12
Last Updated 2017-04-07

GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
siealex said:
One more note. DO NOT set up your Google account until you grant all permissions, otherwise you will be stuck on the initial setup.
Click to expand...
Click to collapse
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.

Incredible work! Thank you to ALL the volunteer developers for making this FREE and OPEN SOURCE progress possible! The code is free, but your time is not! Thank you!!!

Out of curiosity, is aosp_mm_tuna_2016-03-12 running DDK1.9 or DDK1.8? I feel like it's 1.9 from your mention of recording artifacts, but I'm not an android developer, so I can't tell.
I'm running this right now, and it's awesome. Marshmallow in general seems to have much better performance than Lollipop on our device. I do miss some custom kernel flags, but I'm sure that'll come with time.

@Ziyan Which recovery do you recommend ?
DRM services not working means also Netflix doesn't work?

PythonNut said:
Out of curiosity, is aosp_mm_tuna_2016-03-12 running DDK1.9 or DDK1.8? I feel like it's 1.9 from your mention of recording artifacts, but I'm not an android developer, so I can't tell.
Click to expand...
Click to collapse
DDK 1.9 of course
Master94ga said:
@Ziyan Which recovery do you recommend ?
Click to expand...
Click to collapse
The latest TWRP should be fine. I might have not mentioned it in the OP, but the ROM supports F2FS as well.
Master94ga said:
DRM services not working means also Netflix doesn't work?
Click to expand...
Click to collapse
Possibly.

Ziyan said:
DDK 1.9 of course
The latest TWRP should be fine. I might have not mentioned it in the OP, but the ROM supports F2FS as well.
Possibly.
Click to expand...
Click to collapse
Thanks, 3.0 unofficial or your last recovery?

You are a god!
I'm downloading and will be testing this, I'm super excited about this work.
EDIT: So, first thing I've noticed is that the phone is struggling with the configuration in the first boot. Either in the "checking connection" or in the "just a sec..." loading frame, it freezes and doesn't get past it. Is it because of google play services?

diogofd8 said:
So, first thing I've noticed is that the phone is struggling with the configuration in the first boot. Either in the "checking connection" or in the "just a sec..." loading frame, it freezes and doesn't get past it. Is it because of google play services?
Click to expand...
Click to collapse
Yes Google Play Services can mess it up - I don't recall how, but I managed to press a skip button or something to easily get past it when it started looping. I guess we should add a mini how-to to the OP about it, as I really don't want to hack the framework for this.

Yep, I'm stuck in "just a sec..."
Edit: I restarted the Phone and now it works.
Netflix works too

Big thanks to @Ziyan and all OMAP4 dev for all your contribution so far ! I'll test this immediately [emoji106]
Sent from my Galaxy Nexus using Tapatalk

Ah, another thing!
When I flash the rom .zip file with all the partitions in f2fs, it auto changes to ext4 and installs. Maybe I'm being noob using TWRP so I'll say what I did here:
1) Full wipe
2) Convert system to f2fs, convert data to f2fs, convert cache to f2fs
3) Adb push rom zip file
4) Flash it
5) Check partition format, it's all on ext4

diogofd8 said:
Ah, another thing!
When I flash the rom .zip file with all the partitions in f2fs, it auto changes to ext4 and installs. Maybe I'm being noob using TWRP so I'll say what I did here:
1) Full wipe
2) Convert system to f2fs, convert data to f2fs, convert cache to f2fs
3) Adb push rom zip file
4) Flash it
5) Check partition format, it's all on ext4
Click to expand...
Click to collapse
There are a couple things going on here. The system ROM is an ext4 image, so it doesn't matter what you format it to, because it'll always become whatever is in the image.
Furthermore, only /data benefits from being F2FS, but it's not you fault for not knowing this because it wasn't mentioned in the documentation!
The other thing is that I don't know of a TWRP build that isn't buggy. When I tried to format to F2FS, it didn't work because my particular version of TWRP had a bug. So maybe your /data format failed for the same reason. I personally do not know what version of TWRP will reliably work for this. But this is a discussion for the TWRP thread.

2) Convert system to f2fs
Click to expand...
Click to collapse
Don't do this! F2FS is not supported on /system.

Wifi is extremely slow.
I can't do anything.
Google Play store can't install apps.

vipelp said:
Wifi is extremely slow.
I can't do anything.
Google Play store can't install apps.
Click to expand...
Click to collapse
Wifi works perfectly fine here ....with 2.4ghz
you using 5ghz or 2.4 ghz ?

I already tried both and it doesn't matter.
Browser times out opening google.com.
Play store doesn't load images and can't download apps
Wifi automatically disconnects....

rohitchouhan07 said:
Wifi works perfectly fine here ....with 2.4ghz
you using 5ghz or 2.4 ghz ?
Click to expand...
Click to collapse
WiFi working fine for me on 5GHz as well.
To other people: when this ROM boots, you may see the Google splash screen, then the screen will go black, and the device will act like it has died. It hasn't. Just give it a minute and the regular Android boot animation will appear.

OK i'm trying a reflash now. Complete wipe.

For me all work correctly, no problem with google play store or wifi

[ROM] [9] GlassROM

Glassrom is for people who know what they are doing with their devices and know how to fix issues themselves if something goes wrong. Do NOT flash glassrom if you do not know what you're doing with your device. Glassrom will not take responsibility for any mishap, any good or any bad thing that happens to your device
Kernel hardening tip: kptr_restrict is useless on glassrom release builds as an attacker can easily extract kernel pointer data from the release build's image. If you want security you have to recompile the kernel (preferably the whole ROM by yourself
Glassrom recommends that you build it yourself with dm-verity and lock your bootloader to be fully secure instead of flashing release builds. The open-source version has full support for dm-verity. The closed source version does have support but doesn't enable verity. Anykernel2 can be used to inject a kernel with dm-verity enabled
This ROM has dm-verity. Learn how to handle verity before you flash or you will end up in a bootloop
Flashing GlassROM will encrypt your device. If you don't know what that means stop at this instant. Make sure you have backups
Glassrom can take a long time to boot. So be patient and don't freak out thinking it's bricked
Glassrom is based on lineageos
Glassrom respects your rights as a user (but will still be that shady guy who won't release the source code) and has very strict data protection and privacy rules. Please read our privacy policy for more details
Get support almost instantly! Such wow, very nice https://discord.gg/UF9qnts
Safetynet:
Update: as of oreo no longer "bypasses" safetynet. Follows CTS the way a proper ROM should in order to pass safetynet checks
-------
Features: support for microg out of the box
OMS added, adapted for support with lineage's accents
Heavily optimized:
-O3 for ROM
-Ofast graphite and other optimisations for kernel
Odexed whole ROM in speed mode to reduce strain on JIT
EAS
Undervolted
Stripped down kernel configuration to a minimum
Full AOT forced at boot
Secure:
Selinux hardening, yama, several security patches to ensure that the system is secure.
Privileged permission whitelisting
Linux-hardened
Hardware-accelerated forced encryption
Dm-verity entorced
Supports dm-verity (compile it yourself for dm-verity, we can't enforce it on release builds)
Upstreamed kernel
Audio:
V4a and jamesdsp drivers + sepolicy included. Just install the app as a user app and enjoy! No installation or root required
Alsa sound control for headphones (use kernel adiutor to control)
High performance audio support
Pdesireaudio 10.1
Filesystem:
Disabled file and directory access time for /data
Quota support to prevent apps from abusing device storage and faster storage statistics
Support for sdfat
Miscellaneous:
Wireguard support
TCP fast open enabled by default for shadowsocks
The ROM installer verifies each partition after flashing to prevent bad flashes
Note: this is kind of a modular ROM
It supports substratum but doesn't ship the APK. It's the same for v4a and jamesdsp. This is intentionally done so that people who don't want these apps will never have them and the feature would just never be used
-------
Download here
From glassrom server (no logging) (ipv4 and ipv6):
ROM: https://glassrom.pw/glassrom-release.zip
Recovery: https://glassrom.pw/recovery.img
Download from CDN (see privacy and GDPR notice below) (ipv4 only):
ROM: https://cdn.glassrom.pw/glassrom-release.zip
Recovery: https://cdn.glassrom.pw/recovery.img
ROM source: https://github.com/GlassROM
Device config files: https://github.com/GlassROM-devices/android_device_oneplus_oneplus2
Toolchain: https://bitbucket.org/anupritaisno1/aarch64-linux-gnu
Kernel source: https://github.com/GlassROM-devices/android_kernel_oneplus_msm8994
Verifying builds: https://github.com/GlassROM/glassrom-verification
------
Flash instructions:
Flash the recovery first
Go to the mounts and make sure "mount system partition read-only" is ticked otherwise the ROM will bootloop after the flash
If asked to allow system modifications, do NOT swipe to allow them. Tick "never show this screen on boot again" then press "keep read-only"
Do NOT mount your vendor partition unless you know what you are doing. This is NOT supported and will lead to a bootloop on the next boot
If this is your first time flashing the recovery then prepare the fakecache by reading the how to flash incremental section and reboot recovery before starting the process
Do not format data when the fakecache is mounted! This is not supported and will break things
(If coming from another ROM, factory reset is needed)
Backup data to PC
Mount the fakecache partition with
Code:
mount /data/fakecache /cache
If you get a "failed to update system image" error please reboot recovery and try again
Flash the ROM. Strongly Recommended to enable zip file signature verification while flashing the ROM and the firmware
At this stage you have 2 choices. Either flash the gapps addon to be able to boot with dm-verity or flash a dm-verity disabler and flash your gapps. For users that don't use gapps this is not much of a concern
Reboot
Notice for TWRP flashing errors: the error codes themselves are useless. The message above the error is what truly helps diagnose the issue
Below advisory only for people coming to glassrom from another ROM. Contact support if you upgraded from a previous build and a newer build doesn't boot
Starting from the February 2019 release encryption is no longer in place and formats the data partition. Please be careful and have backups of your data
Unlike other ROMs you don't need to clean flash every new build or even wipe caches after every flash. Just flash the new build and reboot. Nothing to worry about unlike other ROMs
--------
You want to use our kernel in your project?
clone the kernel and run bash travis.sh and the kernel will be automatically built for you. We don't really care if you give us credits but if you do we'd appreciate it.
Glassrom believes that rebasing kills any kind of collaboration that could happen so we don't rebase our repositories unless it is impossible to make a change without rebasing
----------
Some notes for posting here:
Keep your appreciation for the work to other threads. Get to the point when reporting a bug so that it can be fixed faster
Bug reports should have proper logs or a way to reliably reproduce the issue
Magisk causes issues. Please do not report bugs with magisk installed
-------------
About us:
This started as a small project, now it's known as glassrom, which is funded by RX Group LLC. Glassrom doesn't make any profit from this (see below)
Privacy policy: we do not collect any personal data at all. Not even analytics. The download server is totally anonymous and doesn't log anything. We do not use adverts of any form. No registration of any sort is ever required to download the ROM. Our provider does watch out for abuse patterns like DDoS and takes action accordingly
How we profit from this: glassrom was made to provide a stable ROM at no charge. Short answer: we don't and we probably never will. RX Group LLC has given us enough to be able to build glassrom for a while and we don't see any need to annoy our users with donation reminders. No advertisements either. Everything is provided free to use and modify without any restrictions whatsoever and we never intend to profit from it
Support: we've already stated that certain mods like magisk or xposed might cause us to refuse support however anything unrelated to the issue being reported will be ignored. This is for users who use shady apps who steal other dev's work. While we don't support nor condone the usage of such apps we can't bring personal issues into our product as an organisation either and will not refuse support if we see these apps in logs. We believe in user freedom and we are not like other ROM teams who declare what users should do on their phones. If you see a maintainer refusing support for
your device due to these issues please take it directly to the notice of @anupritaisno1. We also don't use automated ban bots that ban based on a list in our support for the same reasons.
Security: glassrom always is looking at ways to increase the security of the download server and the ROM. If you find any security issues please report them to us and we'll fix them immediately
T&C: Glassrom is not liable for any damages. Everything is available free of cost and you're making these modifications yourself. We did not tell you to do these modifications and you should be aware of your actions
If you're reporting a bug and would like glassrom to discard all data (logs, screenshots and other details) after the bug is fixed please let us know about it any time. We'll gladly discard all data (note that we usually discard log data once a bug is fixed in about 2 days)
Please read lineageos' privacy policy here: https://lineageos.org/legal/ so that you know what you're agreeing to
We use bunnycdn. Read their privacy policy here: https://bunnycdn.com/privacy
https://bunnycdn.com/gdpr
Note that if you access the server with glassrom.pw you bypass bunnycdn and connect to the server directly. If you don't want to use the CDN use https://glassrom.pw which directly connects to the server
--------
How to flash incremental:
anupritaisno1 said:
Added recovery-fakecache.img
It'll be used for the upcoming incremental OTAs
A full explanation:
Incremental OTAs are computed on the /cache partition
Incremental OTAs often ask for a lot of space on /cache
Op2 doesn't have that much of space on /cache
Why incremental OTAs are computed on /cache and not on /system and /vendor (and boot) directly? Because if this were a stock ROM there is a likelihood of the user interrupting an incremental OTA so Google added a failsafe for this so that an interrupted incremental OTA can be resumed if the device was rebooted by the user. Can't be helped really
What we do? Create a fake cache partition large enough to hold these bits so that incremental OTAs can be flashed. After a lot of testing, 512 MB seems to be the optimal size for a fake cache
First we need to create the fake cache
Boot to TWRP and decrypt data
Make sure data is mounted
Run these commands in terminal by going to advanced > terminal
Code:
dd if=/dev/zero of=/data/fakecache bs=1G count=1
mke2fs /data/fakecache # type "yes" and hit enter to confirm
Note that TWRP is hardcoded to only accept /data/fakecache. Other filenames will be rejected when you flash the ROM
Reboot recovery after creating the fakecache
If you accidentally flash the ROM and forgot to mount the fakecache before flashing you have to reboot recovery, mounting it after a failed flash won't work at all
The following additional directories will be added to the server:
full (no longer available, dm-verity has been enforced on release and full now is equivalent to a release build)
incrementals
Full: for full zips, exactly the same as the release zip but won't contain backuptool so that incremental OTAs can be flashed
Incrementals: will have a filename glassrom-release-incremental-from-source-to-target.zip
Example current glassrom release is july release
The August release would be something like
glassrom-incremental-from-july-release-to-august-release.zip
The file naming for the full zips will be
glassrom-release-full-target.zip
Example August release would be glassrom-release-full-august.zip
Likewise if there is more than one build in a given month you might see something like
glassrom-incremental-from-august6-release-to-august9-release.zip in the incrementals and glassrom-release-full-august9.zip
What to do? First flash the full zip and chain the installation of each incremental zip. Note that you can't be on, say July release and upgrade to September release without flashing the August release
So if you want to go from July to September release (say), you'd probably go something like
backup-script.zip (will be provided, necessary to backup gapps and other mods before flashing the new ROM)
glassrom-release-full-july.zip
glassrom-incremental-from-july-release-to-august-release.zip
glassrom-incremental-from-august-release-to-september-release.zip
.......
gen_verify.zip (optional, see FAQ)
restore-script.zip (will be provided, necessary to restore gapps and mods that were on the old ROM)
Remember that the flash order matters and incremental OTAs can take up to 30 minutes to flash so the larger you make your flash chain the longer you'll have to wait
Myth: aren't full OTAs always better?
No, if you think so you're free to verify the hash of the system with a full OTA and an incremental one. They will match which means that the contents are exactly the same
FAQ: also do I need to change anything else?
You might want to go to TWRP > mount and tick mount system read-only if you're having problems flashing incremental OTAs.
Why do I need to flash the full zip everytime? Can't I just flash the incremental OTAs? ****** ROM allows me to do so with delta OTAs!
First off, incremental OTAs move blocks of data around instead of files and write/erase blocks instead of touching the filesystem. The incremental OTA system isn't even aware of the filesystem being used. This is because the only way to recreate the entire filesystem is to operate at a level below the filesystem. Doing something as simple as even mounting system will disturb the order of the blocks the way they appear to the incremental OTA patcher, even though the filesystem didn't change. So you need to flash the full zip and all incremental OTAs in a chain and you can't flash them directly
Wait! This is different from the Delta OTAs I've used! Stop messing around
Delta OTAs take an existing zip and create a new ROM zip out of it. Incremental OTAs patch your partitions live. Incremental OTAs are also much smaller than Delta OTAs
For comparison:
A "typical" incremental OTA: 8 mb (actual releases should be around 80-200)
It's Delta counterpart: 140 mb (actual releases would be 60-70% of the size of the new ROM)
What's the gen_verify.zip?
Used to verify if an incremental OTA chain (or a full OTA) was correctly flashed. The zip will return valid results and will only log errors and always report a success regardless of whether there is an error or not. It will show you verifying partition... Where partition can be boot, system, vendor or recovery. It will say failed for recovery, that is expected but it should show verified partition for every partition other than recovery. Has to be redownloaded for every new release. It will just verify the partitions and not write anything to any partition. The script will also always return success even if verification fails so read that the script's output actually reports that verification passes and not TWRP's output that the zip flashed successfully
Can I flash normal release zips and skip incrementals and still use this TWRP to flash?
Yes
What's the difference between this TWRP and recovery-vendor?
Nothing except the fakecache addition
Availability: sometimes lineage will make really huge changes that might make it impossible to upgrade through an incremental OTA so you shouldn't rely solely on incremental OTAs. Anything can happen. In such a case I can only say sorry and give you a full OTA
You have to store these incremental OTA files! Glassrom will delete old releases
Click to expand...
Click to collapse
anupritaisno1 said:
Oh I forgot to mention this
Source means your current system
Target means the system you're upgrading to
So your target becomes the source for the next (incremental) OTA
Click to expand...
Click to collapse
Enjoy the incremental OTAs!
Locking your bootloader:
This is dangerous. Glassrom takes absolutely zero responsibility if you try this
Flash the recovery and glassrom
Boot to fastboot and issue this command
Code:
fastboot oem lock

IMPLEMENT
Please add full oms support in this ROM.And VOLTE support too...thanks

Ooo very nice will try soon m8 but micro G support is always interesting to me on mm, now on nougat without manually patching very nice and always appreciated by me... Also safety net patches where will you stop... :victory:

Shrinath0071 said:
Please add full oms support in this ROM.And VOLTE support too...thanks
Click to expand...
Click to collapse
Look volte is not my priority
And I may accidentally break ril completely trying to implement it
I am indeed trying but I can't guarantee a successful implementation
Is is impossible to add substratum to cm
You can add it to cm-based ROMs like RR, aicp, fh but not the pure LineageOS

Dr_DjEnder said:
Ooo very nice will try soon m8 but micro G support is always interesting to me on mm, now on nougat without manually patching very nice and always appreciated by me... Also safety net patches where will you stop... :victory:
Click to expand...
Click to collapse
There are many more features but I don't know because it's been quite a while since I've been testing
I can guarantee you, no unnecessary bloat
There's a commit that allows you to set a password longer than 16 characters and also another one to set a separate encryption password and an unlock password
Can someone test it out?

Interesting.. Thank you. Will flash and report after usage
Sent from my Pixel XL using Tapatalk

anupritaisno1 said:
There are many more features but I don't know because it's been quite a while since I've been testing
I can guarantee you, no unnecessary bloat
There's a commit that allows you to set a password longer than 16 characters and also another one to set a separate encryption password and an unlock password
Can someone test it out?
Click to expand...
Click to collapse
I can confirm that separate passwords work. When you set your screen password it changes your encryption password, but you can change that separately very easily.

will flashing this rom encrypt my device?

yuva_cool said:
will flashing this rom encrypt my device?
Click to expand...
Click to collapse
Interesting little feature but no

Damn! This ROM is butter smooooth. Great work @anupritaisno1
Sent from my Pixel XL using XDA-Developers Legacy app

yuva_cool said:
Damn! This ROM is butter smooooth. Great work @anupritaisno1
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Working with xos devs, tugapower and some of my own tweaks to make it better
The next build will be even faster

anupritaisno1 said:
Working with xos devs, tugapower and some of my own tweaks to make it better
The next build will be even faster
Click to expand...
Click to collapse
One question though. Using Ok Google, assistant keeps asking me to train the voice model again and again. How to make the model stick?
Sent from my Pixel XL using XDA-Developers Legacy app

yuva_cool said:
One question though. Using Ok Google, assistant keeps asking me to train the voice model again and again. How to make the model stick?
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Maybe flash a new gapps package?

anupritaisno1 said:
Maybe flash a new gapps package?
Click to expand...
Click to collapse
Which is more compatible? Or did u just mean latest?
Sent from my Pixel XL using XDA-Developers Legacy app

yuva_cool said:
Which is more compatible? Or did u just mean latest?
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Opengapps super will work on my ROM
You have freedom of choice here. I have merged all the gapps patches from upstream
Pick whatever package you like and flash

anupritaisno1 said:
Opengapps super will work on my ROM
You have freedom of choice here. I have merged all the gapps patches from upstream
Pick whatever package you like and flash
Click to expand...
Click to collapse
I flashed open gapps the first time.
Also, the MSM hotplug cant be tweaked with kernel aduitor, the max cores online cannot be changed. It always reverts back to 4. That is causing fps lag and spotify stutter while locking and unlocking.
Sent from my Pixel XL using XDA-Developers Legacy app

yuva_cool said:
I flashed open gapps the first time.
Also, the MSM hotplug cant be tweaked with kernel aduitor, the max cores online cannot be changed. It always reverts back to 4. That is causing fps lag and spotify stutter while locking and unlocking.
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thats because 4 is the max value. (This max core per cluster) So if its set to, say 3, it means max 3 for little cores and max 3 for big cores.

suraj.das said:
Thats because 4 is the max value. (This max core per cluster) So if its set to, say 3, it means max 3 for little cores and max 3 for big cores.
Click to expand...
Click to collapse
No if I enable the Hotplug all the cores of Big cluster are plugged out except for one and 3 cores of little cluster work.
Please check it
Sent from my Pixel XL using XDA-Developers Legacy app

yuva_cool said:
I flashed open gapps the first time.
Also, the MSM hotplug cant be tweaked with kernel aduitor, the max cores online cannot be changed. It always reverts back to 4. That is causing fps lag and spotify stutter while locking and unlocking.
Sent from my Pixel XL using XDA-Developers Legacy app
Click to expand...
Click to collapse
Then disable the hotplug?
Hotplug is just to avoid some heat. It doesn't help at all when it comes to battery life

suraj.das said:
Thats because 4 is the max value. (This max core per cluster) So if its set to, say 3, it means max 3 for little cores and max 3 for big cores.
Click to expand...
Click to collapse
Oh hey welcome

[MAGISK MODULE] [SM-G920P] [DEBLOAT] TDH-JR (Just enough Remains) [v1.1.20180512]

Description
TDH-JR is a Magisk Module for extremely debloating ROMs based on the G920P stock nougat Android. The debloating is quite complete, so as little of your ROM actually runs after flash installing this module.
Screenshots
Coming . . .
Features
The entire debloat operation is systemless (i.e., no modifications occur to your base ROM, Magisk systemless overlays are used to prevent bloat from installing and running.
Extreme Debloat (Just enough ROM to Use, add your own apps)
The resulting debated system passes SafetyNet as long as your kernel also passes (suggest using @tdhite's SkyHigh Kernel).
Downloads
TDH-JR v1.1.20180512. (debloating based on Firrmware version G920PSPT4DRC2):
Android File Host Download
MD5: fcc0410e48d254be48c311a804ba271b
Updated for Magisk 16.40.
Updated for DRC2 stock firmware.
TDH-JR v1.0-20180101 (debloating based on Firrmware version G920PVPS4DQK1):
Android File Host Download
MD5: 5ffc47cae4dcd67bb38cb5afae17a8bb
How to Install -- FOLLOWING IN ORDER IS REQUIRED!
READ THE DISCLAIMER BEFORE INSTALLING!.
Assure you are on the appropriately similar base (stock) firmware.
Download the module from any of the download links above and place it in your /sdcard directory.
Strongly suggest downloading the latest @tdhite SkyHigh Kernel flash (installer) and place the zip in your /sdcard directory
Reboot to recovery (TWRP)
Make a backup of your existing ROM (TWRP nandroid is best)
Wipe Data, Dalvik, Cache (standard factory reset)
Strongly suggest installing (flashing) the latest @tdhite SkyHigh Kernel. That will install the kernel, root the phone with Magisk and install the kernel's support module. Note: if you do not install the SkyHigh kernel, you will have to manually install Magisk before installing the TDH-JR debloating module.
Dirty flashing coming from pure stock cannot debloat your ROM -- the bloat software is already installed and setup.
Dirty flashing over a system in which you previously installed this module cleanly (per instructions above) should work fine.
Flash (i.e., Install in TWRP) the flashable module zip file.
Reboot (to System)
Enjoy!
After cleanly installing (post a factory reset wipe) this module, the initial boot will take many minutes and may reboot once during the initial setup sequence. Many operations are taking place (e.g., Dalvik regeneration, activation, etc.).
Special Thanks and Credits
[MENTION]topjohnwu[/MENTION]@xda (For the venerable Magisk root)
XDA:DevDB Information
TDH-JR Debloating Magisk Module, Tool/Utility for the Sprint Samsung Galaxy S6
Contributors
tdhite
Source Code: https://github.com/TeamSPR/magisk-module-tdhjr
Version Information
Status: Stable
Current Stable Version: v1.1.20180512.
Stable Release Date: 2018-05-12
Created 2018-01-01
Last Updated 2018-05-13

Disclaimer
*** Legal Disclaimer -- READ ALL OF THE FOLLOWING ***
If you use any software from download links provided anywhere within this thread, or convey the same to someone else, you and all subsequent conveyees are bound by the following:
LEGAL DISCLAIMERS AND ASSUMPTION OF THE RISK BY THE USER OF THE PROGRAM
Assumption of the Risk of Use
YOU ASSUME, AND AGREE TO ASSUME, ALL THE RISK OF HARM BY USING THE PROGRAM. THE PROGRAM MAY VOID YOUR WARRANTY WITH A THIRD PARTY, IT MAY IMPROPERLY OPERATE AND DAMAGE YOUR DEVICE, IT MAY CAUSE ANY MYRIAD OF HARMFUL OUTCOMES REGARDING YOUR DEVICE OR THE USE OF THE DEVICE ON WHICH IT GETS INSTALLED. YOU ACKNOWLEDGE THAT YOU ARE AWARE OF THOSE RISKS, UNDERSTAND THOSE RISKS, AND VOLUNTARILY AND INTELLIGENTLY ELECT TO ENGAGE THOSE RISKS BY USING THE PROGRAM.
Disclaimer of Warranty
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME ALL LIABILITY AND AGREE THAT IN NO EVENT WILL YOU SEEK ANY FORM OF RECOMPENSE, WHETHER LEGAL OR EQUITABLE, INCLUDING BUT NOT LIMITED TO NECESSARY SERVICING, REPAIR, CORRECTION OR OTHERWISE.
Disclaimer of Title Warranty
THERE IS NO WARRANTY OF TITLE FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING ANY CONVEYOR OF THE PROGRAM MAKES NO WARRANTY OF ANY KIND THAT HE OR SHE HAS ANY TITLE OR THE RIGHT TO TRANSFER ANY TITLE TO THE PROGRAM TO YOU. YOU ACCEPT THAT, IN FACT, YOU RECEIVE NO TITLE TO ANY OF THE PROGRAM.
Limitation of Liability
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM, PERMITTED OR NOT, BE LIABLE TO YOU FOR LEGAL DAMAGES OR EQUITABLE RELIEF, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Reserved

Thanks for this! Looking forward to testing between football games. (A guy has to have priorities.)

works great
works great love the update thanks so much no problems so far lags a little during initial setup but no lag after all set up

Nice, thanks! Am I going crazy, or are the links to the module missing?

nostrings said:
Nice, thanks! Am I going crazy, or are the links to the module missing?
Click to expand...
Click to collapse
This? https://www.androidfilehost.com/?fid=673791459329070582

I do not understand this module at all, do we have to install it once we install a new stock rom? Or can i install it whenever i want? (Im on bigdaddys rom, can i install this right now?)

Ryan-sv said:
I do not understand this module at all, do we have to install it once we install a new stock rom? Or can i install it whenever i want? (Im on bigdaddys rom, can i install this right now?)
Click to expand...
Click to collapse
You can try -- I have no idea what BigDaddy loads or does not load from the stock kernel, much less its base. Whatever you do, follow the instructions.

tdhite said:
You can try -- I have no idea what BigDaddy loads or does not load from the stock kernel, much less its base. Whatever you do, follow the instructions.
Click to expand...
Click to collapse
Oh, i also have your kernel, but ok, i'll make a backup before try this

Working great, thanks @tdhite. Kernel seems to be offering support for Synapse, is that correct?

koop1955 said:
? . . Kernel seems to be offering support for Synapse, is that correct?
Click to expand...
Click to collapse
Yup. Just install Synapse and tune to your heart's content.
Sent from my iPad using Tapatalk

koop1955 said:
This? https://www.androidfilehost.com/?fid=673791459329070582
Click to expand...
Click to collapse
Yes. The XDA Labs app wasn't showing the link (see screenshot)

I installed this and i don't have the auto rotate or portrait icon when i pull down the top of phone! It is in auto rotate and i want it in portrait mode! Any help would be much appreciative??

I cannot for the life of me get Sprint Launcher or Sprint ID uninstalled. Anyone have any ideas? The phone restarts when I try to uninstall them.

_Epic said:
I cannot for the life of me get Sprint Launcher or Sprint ID uninstalled. Anyone have any ideas? The phone restarts when I try to uninstall them.
Click to expand...
Click to collapse
Have you tried adding those packages to the list of the directories in the module? It should be in the `config.sh` script. Or just post the paths here, and I am sure someone (or @tdhite) will add them to the list for the future.

nostrings said:
Have you tried adding those packages to the list of the directories in the module? It should be in the `config.sh` script. Or just post the paths here, and I am sure someone (or @tdhite) will add them to the list for the future.
Click to expand...
Click to collapse
I haven't gotten that far into it yet. I may check it out later.

Just a note for future reference - you should really not "uninstall" anything if you are using this module ... just add whatever you don't want on the list, and start again. This will ensure you are can receive OTA updates (though, these may not come anymore, as Samsung is probably abandoning this device for good now), and redo/reapply the magisk module again.

nostrings said:
Just a note for future reference - you should really not "uninstall" anything if you are using this module ... just add whatever you don't want on the list, and start again. This will ensure you are can receive OTA updates (though, these may not come anymore, as Samsung is probably abandoning this device for good now), and redo/reapply the magisk module again.
Click to expand...
Click to collapse
Actually there's a rumor from two Samsung support reps that s6 may actually get oreo! Not a reliable source, but worth holding out hope!
@tdhite Thanks for this module! I just switched over from the tdhjr Rom without a hitch. Feels clean and proper. Definitely a brilliant alternative to the tdhjr rom.
I do have one question, and anyone else who might know is welcome to chime in, which package that was debloated is responsible for how Google assistant works? I thought it was just the Google app, so i installed that (and the Google Assistant app)... But i cant use smart unlock (ya know, unlock with your voice) Does it need to be installed as a system app? Or was there another google related app/package that I'm forgetting about?

Nye-uhls said:
Actually there's a rumor from two Samsung support reps that s6 may actually get nougat! Not a reliable source, but worth holding out hope!
Click to expand...
Click to collapse
That would be super, but judging by past devices and the software they got, I'd say with 99% certainty that this is it. I'd love to be proved wrong, though ?

[DISCONTINUED][TWRP BACKUP-ROM][10] Lightheart 1.0 Galaxy S10 [24.10.2020]

Lightheart 1.0 - Efficiency is key.​
Hi everyone. My name is Skulldron and for those of you who do recognise me, know me as the creator of Project Pixel, another one of the greatest ways to emulate the Pixel Experience, whilst keeping all the benefits of using OneUI and its stock optimized drivers as its base. Today I'm going to be introducing something, different. Over the years of working on Touchwiz based ROMs, I've learnt the description of every little apk, every little permission, what it accepts and what it rejects, its pros and its cons. As a result of this experience, I have one of the best debloat lists out there, with each item on the debloat list, being tested, literally through trial and error for over 4 years, and it goes over every file and every partition known in the OneUI OS. This exact same debloat script was used in Project Pixel, which has recieved positive review after positive review for how efficient and how lightweight OneUI became after the debloat. Today however, I present to you Lightheart OS, a new project that I will be building myself and updating monthly (as I do own an actual Galaxy S10). Lightheart, is essentially built equal to Project Pixel, except that instead of Pixelifying and adding another gigabyte worth of apks, permissions and modules, just stops after the debloating and optimization bit. I have done something similar with the Galaxy Tab S2, and it was called Performante, but it was even more stripped on features than I would have liked myself, so today I showcase Lionheart, the Lineage OS to my Cyanogenmod.
Features:
1. Heavily Debloated System Size - The overall size of the system partition has dropped from 5.2 GB to 3.2 GB, along with RAM consumption dropping from 4.2 GB on stock, to 3.1 GB on Lightheart.
2. Heavily Debloated Product Partition - All bloat has been removed/deprecated from the Product Partition dropping its size from 592 MB to 78 MB
3. Better Battery Performance due to Efficiency - With the removal of an incredible amount of bloat, along with better performance and lesser services, you should be looking at better SOTs and better standby times.
4. Better Performance due to the Cruel Custom Kernel - The Cruel Kernel Team have been kind enough to give me permission and access to their kernel, which in itself has many optimizations, along with the allowance to achieve higher system speeds and overclockabilty via Mtweaks (Needs to be installed seperately, I will provide a link)
5. Preloaded Magisk with Cruel - Cruel Kernel comes preloaded with Magisk, all you have to do is install the Magisk Manager
6. October Patch with the promise of updates every month - As I use this rom as my own daily driver, i will update it every month to keep up with optimizations by Samsung and security patches.
7. Restored some stock Google Permissions - Some stock google framework was restored, such as the default setup wizard.
8. All Essential Samsung Features have been kept - All essential OneUI features have been kept alive, for the sole purpose of necessity.
9. Completely Deknoxed - It is covered under the debloat
Changelog:
1.0 - Initial Release
TWRP Install Instructions:​
1. Download the latest available TWRP Image from Ianmcd's thread (the current supported version is 3.4.0.3 and will be linked at the bottom of the thread)
2. Download the custom VBmeta file and install 7Zip.
3. Rename the downloaded TWRP Image as recovery.img.
4. Highlight both the vbmeta.img and recovery.img, then right click while selected, 7Zip and then add to archive.
5. Once your in the 7zip interface, choose .tar and do not change any of the configurations and build the .tar file.
6. For this next bit, you'll need to download Odin 14.4 (links will be provided)
7. Open Odin, and then connect your device via USB.
8. Select AP, and then select the newly made recovery.tar.
9. Once it is loaded, press start, and when it reboots, hold the recovery combination (Power + Volume Up + Bixby) to boot into TWRP.
You have now successfully installed the latest TWRP for your S10 and can now proceed to actual install. Remember that if you are coming from stock you will need to flash the MultiDisabler, linked at the end of the thread.
Install Instructions (THIS ROM IS NOT FLASHABLE!):
1. Download Lightheart 1.0.
2. Open the zip and extract the folder.
3. Switch off your phone, and go into twrp via the button combination.
4. Make a backup of your cache (This will make the directory to TWRP's recovery system)
5. Boot back into the OS and head to where you stored Lightheart 1.0.
6. Cut the entire Lightheart Folder and move it to TWRP/BACKUPS/Random Number/
7. Now boot back into TWRP and wipe system, data, dalvik, cache.
8. Go to the restore option, and you should see Lightheart as a restorable ROM.
9. Restore Lightheart and once your done, boot into system
And thats about it for the install process. It is a bit unconventional, but I have been unable to procure or manufacture a working installer script as of this moment, so please bear with me for now.
Download Links:
1. TWRP Galaxy S10 Series:
https://forum.xda-developers.com/ga...ecovery-twrp-3-3-0-galaxy-s10-exynos-t3924856
2. TWRP 3.4.-03 (Ianmcd):
https://androidfilehost.com/?fid=8889791610682934970
3. Custom vbmeta:
https://drive.google.com/file/d/1MBQ1iIei6a-RoURS6k6q_xwQOjG4jR-a/view?usp=sharing
4. Lightheart 1.0:
https://drive.google.com/file/d/1U3WcjUSZh3jWCjfoq8vLex83E8D1r8zA/view?usp=sharing
5. Odin 14.4:
https://odindownload.com/download/Odin3_v3.14.1.zip
6. Magisk Manager:
https://github.com/topjohnwu/Magisk/releases
7. MTweaks 17.3:
https://androidfilehost.com/?fid=8889791610682894841
Credits and kernel source:
1. @evdenis for their remarkable Cruel Kernel
2. Kernel Source: https://github.com/CruelKernel/samsung-exynos9820
XDA:DevDB Information
Lightheart 1.0, ROM for the Samsung Galaxy S10
Contributors
Skulldron
ROM OS Version: Android 10
ROM Kernel: Linux 4.x
ROM Firmware Required: TWRP 3.4.0.3 Ianmcd
Based On: OneUI
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2020-10-24
Created 2020-10-23
Last Updated 2020-10-31

Reserved

Reserved

Hi first thnx for your work but if this rom are make for S10 only why the tread is on cross device development ?

thanks for the rom is there the recording call

Random-Tester said:
Hi first thnx for your work but if this rom are make for S10 only why the tread is on cross device development ?
Click to expand...
Click to collapse
Hi. The plan is to slowly extend the ROM to the Galaxy s10+ and s10e, hence why the thread is in cross development

Skulldron said:
Hi. The plan is to slowly extend the ROM to the Galaxy s10+ and s10e, hence why the thread is in cross development
Click to expand...
Click to collapse
When you have done the above please feel free to report this thread and request it to be moved. For now it will be moved to the appropriate S10 only section.

Negan said:
When you have done the above please feel free to report this thread and request it to be moved. For now it will be moved to the appropriate S10 only section.
Click to expand...
Click to collapse
Noted. Thread has been updated with corrections and a link to a telegram group I have made, in case ya'll need further support. Thankyou ^_^

Skulldron said:
Noted. Thread has been updated with corrections and a link to a telegram group I have made, in case ya'll need further support. Thankyou ^_^
Click to expand...
Click to collapse
I encourage you to ensure to provide sufficient support on XDA. Please check the telegram sticky for more info. Also since this is essentially a TWRP backup I've edited your thread title to indicate this as this should be clear from the get go. Do not re-edit that again unless you're able to have the rom be flashable. Thank you and all the best of luck with your project.

Awesome !! Love it so far. Nice performance, genshin impact is not dropping frames like on other oneui ROMs.
Keep up the good work

Waiting for the s10e
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 08:49 PM ---------- Previous post was at 08:47 PM ----------
Waiting for the S10e
Sent from my [device_name] using XDA-Developers Legacy app

Hi,
I would like to use your rom if it means longer battery life. However I have no knowledge of rooting or flashing a galaxy S10 phone. I'm not afraid of the terminal but I'm afraid of loosing access to KBC mobile or Google Pay or any other app that is financially or government involved.
Is it because you say deknoxed that it will have problems with such apps or quite the opposite ?
Another question is, Can Jodin3 be used as well? I only have access to MacOS.
Forgive my English, it's not my mother language.
Kr,

Don't do anything with your phone then if you don't want to loose Google pay etc...

hi ,thx 4 ur hard work,sorry 4 a NOOB question: i have an s10 which is G973N, can i flash this rom?

HannibalHu said:
hi ,thx 4 ur hard work,sorry 4 a NOOB question: i have an s10 which is G973N, can i flash this rom?
Click to expand...
Click to collapse
As long as its not G973U, it should work but I advise caution when flashing a ROM which is not the same model

So far this Rom ist great, the lack of the samsung account makes setting up some apps a bit difficult, but other than that this is awesome!

How are temperatures on this debloated rom?

Pro

Skulldron said:
Hi. The plan is to slowly extend the ROM to the Galaxy s10+ and s10e, hence why the thread is in cross development
Click to expand...
Click to collapse
does it mean it would work for s10e or we need to wait a while?

Hi, this rom works with the latest bootloader?

[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.