Develop Bugs

[ROM+kernel][WIP] [4.4.4][CM11][OS2SD][f2fs][EXPERIMENTAL]bigsuperROM-thunderc-4.4.4

This is unofficial cm11 kitkat android 4.4.4 for the Virgin Mobile Optimus V (runs on Sprint Optimus S as well)
Uses my 3.08 kernel.
I'm offering this over here because skinbark has been busy for quite a while and my builds are way more updated these days.
Purely experimental builds. No real support, I'm sharing my personal builds plus making equivalent internal builds for those of you who like them.
newest builds offering f2fs os2sd!
also fixed camera, and kernel updated to 3.0.101 with HardLight's patchset.
second post mostly outdated, now it's opengapps instead of pa for example. I haven't been updating this in literally years.
now using some of
[COMMIT] [AOSP] JustArchi's ArchiDroid Optimizations - Increases performance up to 6x
go thank justarchi for source of optimizations.
not right now said:
now built with linaro gcc 4.7 (kernel is built with homebrew ct-ng armv6k tweaked linaro gcc 4.7) with -O3 optimizations, except -Os thumb.
Click to expand...
Click to collapse
Wifi AP will reboot if turned on/off/on.
Everything else should work, tell me if it doesn't.
OS2SD /data mounting tweaks from HardLight's OS2SD version.
Smaller, more limited, standard nand-flashable internal builds offered for backwards compatibility or the less adventurous.
Use only THIS RECOVERY (info) (download)
archived said:
OS2SD friendly TWRP recovery, handles partitioning of sd card for OS2SD thanks techvendetta
Click to expand...
Click to collapse
download folder for internal builds:
download folder for OS2SD builds:
here's partitioning info for the OS2SD recovery.
advise: whatever leftover on your card for VFAT/sdcard, either 1Mb or 864Mb swap, 512Mb-768Mb for system, 1Gb or more for data.
expand /sdcard and/or /data as preferred if you use a bigger card. more space in /system? dunno why. doubt there's enough armv6 system apps to fill 512Mb.
current internal build: cm-11-20141014-EXPERIMENTAL-bigsuperROM_internal-thunderc.zip
current OS2SD build: cm-11-20141018-EXPERIMENTAL-f2fs_os2sd_bigsuperROM-thunderc.zip
this should be considered a dev thread since it's on XDA, there's an earlier and discussion thread here.
Sprint and Verizon fix zips attached. Flash in recovery after the ROM before first boot.
OS2SD info in 2nd post.
almost forgot: source
https://github.com/bigsupersquid/android_roomservice
Gapps:
advise: Skinny_4.4_Gapps_new_internal.zip for easy gapps. From here Optimus S won't fit the larger Skinny_4.4_Gapps-new.zip but the V should.
Be patient on first boot. Some reports are as long as 10 min to get past the bootanimation. Takes me at least 5 min.
Carrier Fixes:
Sprint and Verizon. Want another? Got an apns-conf.xml, then post it and your other carrier info.
Basic instructions for internal install:
in twrp, wipe internal data, internal system, and cache.
flash rom, internal carrier fix, gapps.
reboot system.
androidarmv6 turned on TLS in the kernel, and swapped the /system and /data partitions for more room on /system, so you have to use the newest TWRP-multi now as well.
thanks androidarmv6, cyanogen, aosp, thekraven for TheJBC and help, skinbark for initial booting and much work on kitkat for these phones, and techvendetta for his TWRP port. Thanks androidarmv6 and thunderg devs for 3.08 kernel I ported over to thunderc, and HardLight for f2fs in kernel and fstab flags.

OS2SD
OS2SD information
I have been playing with rom-from-sd for quite a while.
kitkat and cm11 make it easy, just by changing the fstab you can mount the ext partitions instead of the mtd partitions in init.*.rc
OS2SD (skinbark named it, it was my mod) uses the regular VFAT plus 3 extra ext4 (or one linux-swap and 2 ext4) partitions on the SD card to hold /swap, /system, /data. Recommend in order: leftover after other 3, 512MB, 512Mb, 1024Mb.
This allows virtually unlimited storage without link2sd methods of any kind. /system can handle whatever you want to flash to it without running out of space, which is handy because kitkat has to be trimmed down to fit an Optimus S or V with their respective 15*Mb or 165Mb of /system space.
when android is running from the card, mount external storage allows manipulation of /system and /data from your linux file manager.
Yeah, yeah, it's all a security hole, but I don't care. It's experimental and fun, and you can fit hundreds of apps on this four year old phone that is labelled 'obsolete' by LG and Qualcomm both.
I still need to remove the 'format sd' and 'unmount sd' from the storage menu in settings to avoid crashes.
Gapps:
advise: Skinny_4.4_Gapps-new.zip for easy gapps. From here
if you want a REAL gapps package...
I made pa_gapps flashing facilitator for twrp/os2sd.
Go get current micro pa_gapps, don't touch the zip.
flash after rom, pa_gapps_modular_micro*.zip no reboot needed.
then after flashing pa_gapps you flash the facilitator (it gets rid of armv7 keyboard libs and installs compatible play services framework.)
Click to expand...
Click to collapse
if you want to use any bigger pa_gapps packages (and you can even install the 200+Mb Stock package on os2sd!) you'll have to follow the instructions for the pa_gapps remover zip TKruzze posted up to remove Google+ (or you'll have fc'ing nightmares) and don't let it install Chrome either (there's another text file needed on the card like the remover, TKruzze left instructions.)
Remember, if you install Google Now (Search) go as quickly as possible into app drawer>Google settings>Search and Now>Voice>Hotword Detection and turn it off, then back up one submenu to Voice again and turn off all the checkboxes.
You can install voice search and talkback from market (enable talkback in accessibility settings) for those functions without fc. (and voice search wrapper from xda if you want voice control over Search.)
or just go the easy way on os2sd and use the Skinny_4.4_Gapps_new.zip which don't need a facilitator. But it's harder to get current Google Search that way since Play thinks we can't handle it.
Basic instructions for OS2SD install:
Use NEW twrp.
Wipe system, data, cache. Flash ROM carrier fix, gapps.
reboot.

reserved

Thanks for this! Just got this as a replacement phone, good to see support. Any recommended gapps? And is art supported?
Edit: Neither Banks nor PA gapps seem to work past setup. slimgapps or whatever its called in the other forum is all that goes then it seems.
Sent from my LG-LS670 using xda app-developers app

I cannot believe this phone is still going. You are the man, bss!
Sent from my SPH-L710 using xda app-developers app

Maestertk said:
Thanks for this! Just got this as a replacement phone, good to see support. Any recommended gapps? And is art supported?
Edit: Neither Banks nor PA gapps seem to work past setup. slimgapps or whatever its called in the other forum is all that goes then it seems.
Sent from my LG-LS670 using xda app-developers app
Click to expand...
Click to collapse
I forgot to link gapps. the skinnygapps from ac are the basic model.
I just tried pa gapps and they work ok without onetimeinitializer and setupwizard,
I haven't seen reference to art running on any armv6. I tried to walk it thru compilation early on, but ran out of free time to keep translating the thumb2 asm to thumb1 (or finding source where others had already done so) so it'd work.

new os2sd build.
zram turned on, p500 ami304d to match their kernel drivers (long-standing whoops there.)
probably other cm changes. I don't track em I just build and use it.

update. new builds up.

Excellent rom, but every so often it will freeze up and reboot. Is this normal? Im doing nothing but basic tasks like listening to music and then it freezes and reboots itself....
Sent from my GT-N5110 using xda app-developers app

ghostswagking said:
Excellent rom, but every so often it will freeze up and reboot. Is this normal? Im doing nothing but basic tasks like listening to music and then it freezes and reboots itself....
Sent from my GT-N5110 using xda app-developers app
Click to expand...
Click to collapse
check your overclock, if it's too high you'll get random reboots. Best way I've found is run gallery while OC'd and play with it until it reboots. Set OC down on notch below where it doesn't reboot in gallery or camera.
If you're not OC'd then I'm not sure why it's doing that. some apps cause issues. logcat or /data/tombstones may have stuff you can pastebin if you want me to look into why.

4.4.3 update later today .

bigsupersquid said:
4.4.3 update later today .
Click to expand...
Click to collapse
bump... rom update, carrier fixes need updated but should work as long as you don't mind settings showing old build.

bump for really new release.
now using
[COMMIT] [AOSP] JustArchi's ArchiDroid Optimizations - Increases performance up to 6x
go thank justarchi for source of optimizations.
now built with linaro gcc 4.8 (kernel is only linaro gcc 4.7) with -O3 optimizations.

4.4.4
Looks like next rev be along here soon.
4.4.4
Gotta see if anything really changed.

big update
requires new recovery.

carrier fixes updated to 4.4.4

new release.
BUG:
ADB debugging needs toggled off and on to recognize cable.
Otherwise, optimized, with linaro kernel.
Might need to update your TWRP (since this is experimental, after all, things change.)

bugfix release.
takes care of adb toggle to connect cable issue.
adds armv6k-specific toolchain optimizations.

bump
new kernel toolchain (I built a linaro 4.7.4 with crosstool-ng with armv6k-specific flags)
p500 config imports... zram reenabled and selinux enforcing.
probably other upstream changes.

no screenshot

[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

🤖 FLUENCE UHD PATCH 🤖 // SOSP 22.02.18 🤖

The Inventor of the Android Patch System presents​WELCOME TO FLUENCE UHD SOSP​HINT​See Post: https://forum.xda-developers.com/showpost.php?p=78928919&postcount=25 For the latest Update and News​
INDEX​POST 1 - INFOS
POST 2 - DOWNLOAD
POST 3 - INSTRUCTIONS​
ABOUT​My Projects are always aiming on delivering a clean and fluent Operating System, with the maximum level of quality in all views. Fluence UHD is back, and now bigger and better as before! Expierence the optimizations and secrets i discovered and collected over all the Years with My Work.
Enjoy the options of the AROMA Installer and get a optimized Google Stock System with 4K HDR Video Playback, better Audio Quality and even better Performance and Effiency on all Parts of the System. Forget Mods, Modules and Bootloops. The Fluence UHD Patch comes with all You need! GApps, Busybox, Magisk, init.d Support, and the hugest Collection of Android Build Optimizations... You will feel the Love i put in My Work. WORD <3
XDA:DevDB Information
🤖 FLUENCE UHD PATCH 🤖, ROM for the Google Pixel 2 XL
Contributors
Miustone, Miustone, Miustone, Miustone
Source Code: https://github.com/Miustone/SOSP
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Google Factory Image: https://developers.google.com/android/images /AND Deuces Script 4.5: https://forum.xda-developers.com/pixel-2-xl/development/tool-deuces-bootloop-recovery-flashing-t3704761
Version Information
Status: Stable
Current Stable Version: 1.5
Stable Release Date: 2019-02-19
Created 2019-02-13
Last Updated 2019-02-21

DOWNLOAD

Instructions:
FOLLOW THIS THREAD TO GET THE LATEST STOCK OS:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Fully boot Your Pixel into the Stock OS
Skip the Google Setup Wizard
Place the Patch on Your Device Storage
Reboot in to TWRP
Wipe Data and Dalvik Cache
Flash the Patch
Reboot in to System
Done
SOSP RELEASES
Visit my Repository from the Thread
Download the Master Branch as zip
Repack the Patch zip
Make sure META-INF and everything else is on root of the zip
Use it with the Instructions from above
Done

Upload for todays build takes still one hour for now. You can select with Drive also older Versions of the ZIP (Acutal is V2, Uploading is V3) btw. Enjoy!
EDIT:
New Device new trouble. Got bootloops with the uploaded Version so do i have to revert some Things. Stay tuned!

I am looking forward to testing this out. I am happy we are finally getting a ROM that is based off the stock ROM. I will keep an eye out when you fix the bootloop issue. I will then download and install it on my phone and give you feedback.. Thank you!

encephalon9986 said:
I am looking forward to testing this out. I am happy we are finally getting a ROM that is based off the stock ROM. I will keep an eye out when you fix the bootloop issue. I will then download and install it on my phone and give you feedback.. Thank you!
Click to expand...
Click to collapse
I'm still fighting with Treble (A/B System // Vendor), and there is a some unusable stuff like the Debloat Part in AROMA which was needed for the Standard OEM Bloat from SONY, LG and Others. But i think i can push a clean and good working Build at the end of this Week...
Stay tuned
EDIT: Slightly updated Build will come in some Hours! I reverted my latest changes and cleaned everything up. Looks like the Kernel Patching does not work that nicely. I will try the famous Elemental Kernel for My needs...

Miustone said:
I'm still fighting with Treble (A/B System // Vendor), and there is a some unusable stuff like the Debloat Part in AROMA which was needed for the Standard OEM Bloat from SONY, LG and Others. But i think i can push a clean and good working Build at the end of this Week...
Stay tuned
EDIT: Slightly updated Build will come in some Hours! I reverted my latest changes and cleaned everything up. Looks like the Kernel Patching does not work that nicely. I will try the famous Elemental Kernel for My needs...
Click to expand...
Click to collapse
Sounds good. My fiance and I just planned a random Valentine's day trip to Nashville, TN so hopefully I will be able to try it out today or tomorrow! Got a 10 hour drive coming up soon.

encephalon9986 said:
Sounds good. My fiance and I just planned a random Valentine's day trip to Nashville, TN so hopefully I will be able to try it out today or tomorrow! Got a 10 hour drive coming up soon.
Click to expand...
Click to collapse
Sweet, have a good One :angel: Wish i had the Time with Mine. We have both to work early tomorrow

Is it absolutely necessary to wipe Data if your already running stock? Should I flash patch now or wait for the update.

mookiexl said:
Is it absolutely necessary to wipe Data if your already running stock? Should I flash patch now or wait for the update.
Click to expand...
Click to collapse
Most of the final Content is missing but You can go thru AROMA without Problems. The DPI May be also a bit low which means a Mini Setup Wizard but You can adjust that over the Display and Text Size Settings for now. It was running stable for me so far but i own my Pixel not that long and have to Test more Things Out.
BR
Oh and Yes, Data should be wiped since many Essential Things get changed on the System Part like the Multi Tasking (RAM Management) Audio Rendering, UI Rendering and so on. A Clean Start means less or even No Problems. A Backup of Stock would be also a smart move which saves Time. A compressed Image including Vendor, boot and System should Take Up under 5gb of Storage ..

Miustone said:
Most of the final Content is missing but You can go thru AROMA without Problems. The DPI May be also a bit low which means a Mini Setup Wizard but You can adjust that over the Display and Text Size Settings for now. It was running stable for me so far but i own my Pixel not that long and have to Test more Things Out.
BR
Oh and Yes, Data should be wiped since many Essential Things get changed on the System Part like the Multi Tasking (RAM Management) Audio Rendering, UI Rendering and so on. A Clean Start means less or even No Problems. A Backup of Stock would be also a smart move which saves Time. A compressed Image including Vendor, boot and System should Take Up under 5gb of Storage ..
Click to expand...
Click to collapse
Cool bro. I'll elect to to wait while you get adjusted to this device. I know your work is superb based off what you've done on devices past.

Will this work on walleye (Pixel 2)?

bassguy60 said:
Will this work on walleye (Pixel 2)?
Click to expand...
Click to collapse
Yes
Can aynone tell Me btw why there is no MTP in TWRP? Reovering the Device after testing a Patch means always a full flash with Factory Image for Me. Followed by a boot in the System where i have to use PTP to copy my ZIP. Cruel to develop like that TWRP is the other painful Point. Wish the Pixel would have a classical Recovery Partition...
EDIT: Seems like we have to boot once after flashing Stock to be able to flash Magisk and get a booting System!? That could be the Reason why my full stock rom wasn't booting. Feeling me a bit dumb right now...
EDIT2: I will push more Time in a full Stock ROM to get a Monthly updated Base for my Changes. Once i got a fully working ROM can i start with adding AROMA Options and Stuff like that. I think the only Problem with My ROM was the patched Kernel which don't wanted to boot and not the deodexing or the Updater Script... Any help with it is welcome

Miustone said:
Expierence the optimizations and secrets i discovered and collected over all the Years with My Work. Enjoy the options of the AROMA Installer and get a optimized Google Stock System with 4K HDR Video Playback, better Audio Quality and even better Performance and Effiency on all Parts of the System. Forget Mods, Modules and Bootloops. The Fluence UHD Patch comes with all You need! GApps, Busybox, Magisk, init.d Support, and the hugest Collection of Android Build Optimizations... You will feel the Love i put in My Work. WORD <3
Click to expand...
Click to collapse
Uh.. secrets? Maybe you're a non-native English speaker and used the wrong word, but what 'secret optimizations' can there be in something that is opensource?
Could you elaborate on the collection of Android Build Optimizations you are using? Can't see for ourselves because the link to source code is 404.

bobbarker2 said:
Uh.. secrets? Maybe you're a non-native English speaker and used the wrong word, but what 'secret optimizations' can there be in something that is opensource?
Could you elaborate on the collection of Android Build Optimizations you are using? Can't see for ourselves because the link to source code is 404.
Click to expand...
Click to collapse
Hey,
Secrets is maybe not the right Word. It's more like many Developers and even OEMs don't know about all the Stuff of Android. I discovered Bug fixes, functions and Features which are now used in a wide range of Mods and ROMs and even OEM Firmwares, and while never getting Credits for it am i aware about where it popped up first in the Web ? I was the First One for example who got all real Pixel Features on a non Pixel Device by porting a lof of System Stuff and Not only by changing one or two Files. I also ported MIUI in the past which was mind opening for Me Back in that Time...
The Secrets i use here are just a greatly tested bunch of Configs for the Hard and Software of our Android Devices in other Words.
And yeha, sorry for My English! It's not the best ?

What should I do if my phone freezes? I have this issue everytime. If I reboot into TWRP and then flash the Patch again, I get an error

gogixx said:
What should I do if my phone freezes? I have this issue everytime. If I reboot into TWRP and then flash the Patch again, I get an error
Click to expand...
Click to collapse
I discovered this issue only with attached USB Cable, have you tried it without? As usual can you just press the bottom right edge a few times and you will complete the installer without Problems when this happens.
I'm still working on a full stock zip... Possible that i end up with raw images :/

Sorry if I sound as a noob, but what does it means "press the bottom right edge"? It stucks on 82% and there is nothing to press. ?

gogixx said:
Sorry if I sound as a noob, but what does it means "press the bottom right edge"? It stucks on 82% and there is nothing to press.
Click to expand...
Click to collapse
It's the spot where You clicked to go to the next Page in AROMA. Press it 4 or 5 Times and it will exit AROMA to TWRP. It's a ugly AROMA bug which never got fixed in the last 4 Years...

Alright, just to let You know Guys. Making Stock ROMs from actual Google Images is cruel. There is almost no benefit against flashing with a PC except for the need to have a PC. The Patch will be the only Thing that works just fine if we want Stock Edits...
I'm actually ripping everthing out of the Patch and i'm redoing the Scripts and hope it will work. Cross the Fingers!
Can anyone tell me btw how to create a working backup of stock with TWRP? Looks like my backups won't start..

OmniROM Android R (11) for Pi 4

OmniROM
Download
Images taged with MICROG contain a pre-installed ready to use
microG setup https://microg.org/
Images tagged with WEEKLY can be used to setup
official Google gapps
64bit build
Tablet mode configuration (not Android TV)
At least 4GB model recommened
No HW accelerated video playback
Mesa support for V3D is WIP so expect some graphic issues (especially on higher resolutions - HD 1920x1080 in general should be fine)
Support of booting from SD or USB by just changing config.txt (check README below)
GPIO support - monitor and set README.gpio
chrome (ium) is broken use alternative browser (firefox, edge)
for screen issues check https://www.raspberrypi.org/documentation/configuration/cmdline-txt.md
if you experience black bars connect to HDM1 or add disable_fw_kms_setup=1 to config.txt files
how to do updates? - check README.update
Adjust screen resolution:
To force a different screen resolution edit in /system/build.prop the line
#debug.drm.mode.force=1280x800
Remove the leading # comment and adjust to the screen resolution you want e.g.
debug.drm.mode.force=1280x720
Make sure to also check the README.txt in there
For questions please also use our official Telegram channel
https://t.me/OmniROM_Community
For current progress and how to build yourself check
README.build
XDA:DevDB Information
OmniROM, ROM for the Raspberry Pi 4
Contributors
maxwen, maxwen
Source Code: https://github.com/omnirom/android_kernel_brcm_arpi/
ROM OS Version: Android 11
ROM Firmware Required: 64bit
Based On: AOSP
Version Information
Status: Stable
Created 2020-10-28
Last Updated 2020-10-28

Builds
https://dl.omnirom.org/tmp/rpi4/
The plan is to have about weekly builds - at some point it will be part of all the other OmniROM devices with regular weekly builds
once the Android 11 cycle starts
20201016
Just a snapshot of the current state
Non microG builds will come later
20201028
WEEKLY and MICROG build
20201105
TWRP included
IMPORTANT
Check new recovery section in README for all the details
EVEN MORE IMPORTANT as posted before to get a working TWRP I had to disable userdata encryption for the moment
that means IF you try to boot this with your old userdata you will get an unpleasent surprise. You must start with
a fresh userdata partition (mkfs + tune2fs). You CAN (if you know what you do) create an backup BEFORE
updating by using adb shell and e.g. create a copy of userdata on an external USB device and copy that back afterwards.
But after all of that hassle from now on updating will be much easier since with TWRP you can create
userdata backups on an external USB device very easy
So going from this release an update could work like this.
1) boot your current install into TWRP
2) create an userdata backup on an external USB device
3) flash the new build - you dont need to care about userdata
just do whatever you always do with it e.g. resize
4) boot new build
5) go into Advanced settings and switch boot mode to recovery and restart
6) in TWRP restore the backup you created before from external USB device
7) flash switch_boot_rom.zip and reboot system
8) enjoy
add boot mode switch in Advanced settings
add audio output switch in Advanced settings
whatever has been done since the last build
20201115
fixed 5GHz WiFi AP
fixed Fondar USB touch screen
actual development
20201122
switch to new kernel base - big thanks to Konsta - with update to 5.4.77
update mesa to v20.2
initial work to support pi camera - not yet working but close
initial work to support gpio - IF you want to use gpio please contact me on tg cause I was too lazy to create a README for this yet
all core system updates and fixes
20201128
performance tuning
November security update
gpio support update
all core system updates and fixes
20201206
added gpioi-fan
cpufreq config in advancded settings
all core system updates and fixes
20201214
property persist.debug.drm.mode.force to adjust screen resolution
all core system updates and fixes
20201224
added disable_fw_kms_setup=1 to config.txt files. This should remove unneeded black bars for some screen when connected on HDM1. I did not see any problems on screens that have no issue with that anyway so I enabled by default. If you face issues remove line and report back please
enabled showing BT device battery level if applicable
all core system updates and fixes
Best Xmas wishes for those who care about it and looking forward to 2021
20201231
add WiFi firmware for p400
kernel update 5.4.85
add userdata resize and project quota enable script in TWRP
reduce dB of max media volume
all core system updates and fixes

Does this build support the original RPI 7" touch screen?

elhennig said:
Does this build support the original RPI 7" touch screen?
Click to expand...
Click to collapse
Not out of the box since I dont have one of those to test myself
BUT it should contain the needed overlays so if you know your way around
give it a try and report back if there is something missing.

Regarding "No HW accelerated video playback", is there a chance this is coming anytime soon?
Thinking about using this for MS xCloud gaming.

maxwen said:
Not out of the box since I dont have one of those to test myself
BUT it should contain the needed overlays so if you know your way around
give it a try and report back if there is something missing.
Click to expand...
Click to collapse
I am afraid I have no idea how to build my own ROM or configure overlays respectively. I guess you just notice from my answer that this is the sad truth

ich_mind said:
Regarding "No HW accelerated video playback", is there a chance this is coming anytime soon?
Thinking about using this for MS xCloud gaming.
Click to expand...
Click to collapse
Depends mostly on mesa development - but nothing I would hold my breath for

elhennig said:
I am afraid I have no idea how to build my own ROM or configure overlays respectively. I guess you just notice from my answer that this is the sad truth
Click to expand...
Click to collapse
well - the thing is that this does not have anything to do with building ROMs
should all be possible by modifying config.txt
Looking at the LOST OS builds might give some hints since I think he supports it

Just one word of wisdom here from me since I saw in some reports as something negative
"It’s stuck in “tablet mode” instead of Android TV mode"
I really dont think a raspi is a well equipped device to be used for ATV when you get
a ATV USB stick from e.g. Xiaomi for about 40E that simply works without issues and
has official google support.
So while everyone feel free to use our repostories to create an ATV build dont ask me for it cause I wont do it.

please help after propper flash to my sd card all i get is the no input screen as if nothing is connected to my tvs hdmi port

Thanks a lot for the work you put into this.
I'm really looking forward to how this project will develop.
If I may I have a stupid question - is there a way foreseen to safely shutdown the pi? I mean I know how to setup a safe shutdown in e.g. raspbian but I doubt it's the same in android.

Growking99 said:
please help after propper flash to my sd card all i get is the no input screen as if nothing is connected to my tvs hdmi port
Click to expand...
Click to collapse
I think you hit me already in TG - but just to reiterate here again - as it is in also the README
Using latest firmware is MANDATORY - 64bit support has been added a few months ago
without you will get the described no boot
Best is to flash latest firmware (which also includes USB boot even if you dont need it)
There are a long list of pages describing how to update. Just linking one here for reference
https://www.tomshardware.com/how-to/boot-raspberry-pi-4-usb
You MUST do that in e.g. Raspberry OS so best do it before even starting with Android

lernfaehig said:
Thanks a lot for the work you put into this.
I'm really looking forward to how this project will develop.
If I may I have a stupid question - is there a way foreseen to safely shutdown the pi? I mean I know how to setup a safe shutdown in e.g. raspbian but I doubt it's the same in android.
Click to expand...
Click to collapse
Long press the power button in the navigation bar -> shut down

That's pretty cool, thanks for hard work.
But it's still not usable for daily use as a media center since there is no HW accelerated video playback.
All Android builds on raspberry pi have the same issue .. :/
I think that these builds are just proof that you can have Android on raspberry pi than anything else.

flyl0 said:
That's pretty cool, thanks for hard work.
But it's still not usable for daily use as a media center since there is no HW accelerated video playback.
All Android builds on raspberry pi have the same issue .. :/
I think that these builds are just proof that you can have Android on raspberry pi than anything else.
Click to expand...
Click to collapse
Welcome captain obvious - tell us something new...

maxwen said:
Welcome captain obvious - tell us something new...
Click to expand...
Click to collapse
It's just an observation lol what I don't understand is that there are almost no differences between Android 9, 10 or 11 for pi, they are all the same.
I wonder what's the real point to make all these builds which all lack the same features.. No disrespect, I'm just wondering.
Captain obvious

flyl0 said:
It's just an observation lol what I don't understand is that there are almost no differences between Android 9, 10 or 11 for pi, they are all the same.
I wonder what's the real point to make all these builds which all lack the same features.. No disrespect, I'm just wondering.
Captain obvious
Click to expand...
Click to collapse
You are just too focused on what you want to do with the device

does it have google apps out of the box

vedforeal said:
does it have google apps out of the box
Click to expand...
Click to collapse
of course not - this would be illegal
We are not in China here ...
PS: I did not find any android-11 gapps out there that would work currently
So the only way is anyway microG for now - which is enough for most people

i tried to boot off 32gb usb and it wont work
and first thing before you say anything about my bootloader being out of date its not here is the bootloader output BCM2711 detected
Dedicated VL805 EEPROM detected
BOOTFS /boot
BOOTLOADER: up-to-date
CURRENT: chu 03 set 2020 12:11:43 UTC (1599135103)
LATEST: chu 16 abr 2020 17:11:26 UTC (1587057086)
FW DIR: /lib/firmware/raspberrypi/bootloader/critical
VL805: up-to-date
CURRENT: 000138a1
LATEST: 000137ad
when i try to boot the build (from the website i didnt compile it) with either the microg or the weekly build after flashing the pi just simply wont start and the green and red light just keeps flashing and nothing happens i was able boot twisterOS just fine off this same usb so its this build i dont know if i did something wrong but the file system was present in gparted and i tried booting it without expanding the partition and with doing so. also i tried to "fix" all the partitions using gparted and that did nothing also i noticed that the /boot directory in this build seems a bit empty compared to my manjaro build i know your working hard on this but this might be a bug in your build and id be willing to help you fix 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.