Related
Here it is :
1. How exactly are updates pushed to aosp? Are they pushed only when they announce a release like the new 4.0.4? Looking at this page https://android-review.googlesource.com/ it appears the updates are in real time but why is it that we are waiting for 4.0.4?
2. Let's say I build from the latest aosp now including the proprietary drivers specific to my nexus device. Is the result exactly the same as factory ota image? Or does Google make some small specific changes specific to devices?
3. Why is it that non nexus devices that get ICS unofficial roms even after the official release from the manufacturer still lack some functionally? Why is it not possible to use the proprietary libraries and drivers from the official update?
4. Does this page https://android-review.googlesource.com/ include all the changes the Google makes to aosp? What are the important ones compared to 4.0.3?
5. How do rom developers like teamkang or gummy etc port their 4.0.3 roms to 4.0.4? Do they have to add their extra code manually to each file or do code management tools like git take care of everything?
Sorry about the long questions I'm just really curious.
Thanks!
ArmanUV said:
Here it is :
1. How exactly are updates pushed to aosp? Are they pushed only when they announce a release like the new 4.0.4? Looking at this page https://android-review.googlesource.com/ it appears the updates are in real time but why is it that we are waiting for 4.0.4?
2. Let's say I build from the latest aosp now including the proprietary drivers specific to my nexus device. Is the result exactly the same as factory ota image? Or does Google make some small specific changes specific to devices?
3. Why is it that non nexus devices that get ICS unofficial roms even after the official release from the manufacturer still lack some functionally? Why is it not possible to use the proprietary libraries and drivers from the official update?
4. Does this page https://android-review.googlesource.com/ include all the changes the Google makes to aosp? What are the important ones compared to 4.0.3?
5. How do rom developers like teamkang or gummy etc port their 4.0.3 roms to 4.0.4? Do they have to add their extra code manually to each file or do code management tools like git take care of everything?
Sorry about the long questions I'm just really curious.
Thanks!
Click to expand...
Click to collapse
1. All Nexus OS versions are AOSP. We are waiting for the OTA because Google only sends the update to a few people at a time, because sending it to everyone all at once would make their servers very unhappy.
2. You'd just be missing the radio I believe.
3. The proprietary stuff is for their skinned OS versions, and is not necessarily usable for vanilla Android.
4 and 5 are beyond me :/
Sent from my Galaxy Nexus
I s it possible the rooted Galaxy Nexus to get the OTA ICS 4.0.4?
ragnarokx said:
1. All Nexus OS versions are AOSP. We are waiting for the OTA because Google only sends the update to a few people at a time, because sending it to everyone all at once would make their servers very unhappy.
2. You'd just be missing the radio I believe.
3. The proprietary stuff is for their skinned OS versions, and is not necessarily usable for vanilla Android.
4 and 5 are beyond me :/
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
thanks. you misunderstood my first question though. I know that nexus images are based off aosp. What I meant is that the changes on android gerrit review system are public and in real time. So why is it that a release like 4.0.4 is a big deal?
CakraMas said:
I s it possible the rooted Galaxy Nexus to get the OTA ICS 4.0.4?
Click to expand...
Click to collapse
Not the best place to ask this question but I think if you're on yajuko and you have stock bootloader (not cwm) then you may be able to get ota but you'll lose root.
4.0.4 ota is compiled by google from it's internal tree.
What you see in gerrit is the reviewing process for the master branch (and a few others), where everyone can submit, which should be updated (merged) with google internal tree everytime a ota/source gets released.
ArmanUV said:
thanks. you misunderstood my first question though. I know that nexus images are based off aosp. What I meant is that the changes on android gerrit review system are public and in real time. So why is it that a release like 4.0.4 is a big deal?
Not the best place to ask this question but I think if you're on yajuko and you have stock bootloader (not cwm) then you may be able to get ota but you'll lose root.
Click to expand...
Click to collapse
Because those sources are actually not released until google starts the ota update. They develop behind closed doors then release all new code at once with the ota. Some people dont like this but i dont think it matters prrsonally.
---------- Post added at 06:53 AM ---------- Previous post was at 06:51 AM ----------
5. Github has a diff function that can compare any two files and even merge the code together. So the devs likely use diff to check all new code and merge.
4. You can look thru all the commits to actually see the newest code changes to see whats important etc.
bk201doesntexist said:
4.0.4 ota is compiled by google from it's internal tree.
What you see in gerrit is the reviewing process for the master branch (and a few others), where everyone can submit, which should be updated (merged) with google internal tree everytime a ota/source gets released.
Click to expand...
Click to collapse
so Gerrit commits are just a very small percentage of all the changes, right?
and does that mean that ota updates may be (slightly) different from aosp compiles?
and that they are no changes to aosp between releases?
thanks!
ArmanUV said:
so Gerrit commits are just a very small percentage of all the changes, right?
and does that mean that ota updates may be (slightly) different from aosp compiles?
and that they are no changes to aosp between releases?
thanks!
Click to expand...
Click to collapse
gerrit commits to the master branch are most of time submitted by people working outside of google.
yes, compiling from the master branch of aosp is slightly diferent than from compiling through release tags (4.0.3_r1, 4.0.4_r1.1).
tagged releases are the same as an OTA, except it doesn't have radio/bootloader images, since they're binaries. they don't change, ever. now the builds compiled from aosp master branch do change, even if it is only under the hood changes.
I want to know if there is any app or feature that allows to only download the updated changes of each build so we do not have to download the full file, most likely for betas. When i was a CM user they had a tool called CyanDelta i think.
So any relative in PA?
We do not have deltas at this time
#stayparanoid
Hoping to have it soon!
Not really a big deal considering we only release once a week
#stayparanoid
Droidkit OnePlus One Windows
Hey guys iTechy21 here and I am glad to announce I have a NEW project I'm working on to make an open source toolkit made from c# to allow easy development for other devices. This project will aim to support as many devices as possible with different toolkits for different devices therefore unifying the experience between them.
This will also be 100% open source when fully complete and is released under the GPLV3 licence (apart from the stuff I did not develop e.g. Custom Recoveries, root.zip, adb / fastboot and stock software all rights go to their respective owners).
Features
Support for any android version and Rom
Full Backup and Restore of apps + data (Nandroid is in the works...)
Unlock / Lock your bootloader (removed locking due to possible issues)
Flash a custom recovery (all supported including stock)
Shows attached device(s) in status bar
Advanced CMD mode for power users - type any ADB Command you want!(Will be reimplemented!)
Booting the device into and out of fastboot with a button click
Flash back to stock (Lollipop!) and keeps your bootloader unlocked
To come
Flash 100% stock DONE!
Save backups with custom names DONE!
Install APK's through ADB DONE!
Flash zip via recovery commands DONE!
Improve UI to make it look cleaner...
Backup the EFS Partition (will be coming Soon) DONE!
Log screen to help amateurs with adb learn (and also output errors to be more verbose) Abandoned due to too many issues
Ability to change colour theme from light to dark and the colours (coming Soon™)
Improve OTA system (continuous)
I am accepting requests if they are not too obscure to find out (even better if you find a way to do it as it cuts down on my research time which I don't have a lot of )
Legal
This is an unofficial toolkit made by an independent developer who has no association with oneplus apart from the fact that he owns a 64gb Sandstone black phone. I cannot be held responsible for anything that may happen to your phone! Even if it is just exploding, catching fire or just voiding the warranty.
Changelog
Material 0.0.1.5 ) - Major Milestone! - Untested Oxygen OS flashing. Do-so at your own risk! (Might not work not fully tested)
Improved theming
Updates to internal .dll's
Stability improvements
UI Tweaks
More verbosity via dialogue messages
System requirementsTo run this needs an x86 or x64 based system (Not supported on Windows RT)
And version 4.5 of the .NET framework (which is installed upon install if missing (needs testing!) and requires Windows 7 or Higher (sorry XP users )
DownloadsNo Download as no longer maintained and buggyQR for nerds
[QRCODE]http://repo.itechy21.com/toolkit.html[/QRCODE]
Known issuesYou tell me...
XDA:DevDB Information
DroidKit | OnePlus One Windows *STABLE*, Tool/Utility for the OnePlus One
Contributors
itechy, All the helpful folks over at Stack Overflow
Source Code: https://github.com/Droidkit/OnePlus-One/tree/master
Version Information
Status: No Longer Updated
Current Stable Version: V0.0.1.5
Stable Release Date: 2015-09-17
Created 2015-03-16
Last Updated 2015-12-06
FAQ
Q: How do I do X?
A: You click the button corresponding to the action
Q: How do I flash to stock and then unlock the bootloader?
A:
You put your device into fastboot mode.
Once done select your device model (16Gb or 64Gb) and then click flash to stock.
The Bootloader should stay unlocked after the flashing process...
Q: What Roms do this ToolKit support?
A: Any android based ROM with the ADB Debugging interface!
Q: Help it's not working!
A: Try 3 things.
Re-installing the toolkit to re-install the drivers
Enable ADB in the developer settings (tap on build number (in about phone) x times until you get a toast notification)
Update the ToolKit
I found a Bug!
Great and thanks for finding one! I can now hopefully track it down and fix it if you provide the following:
The Computer's OS
What you were doing
How you can reproduce this
Your device
The code from the message that appeared
This will help me track down and hopefully fix the error. And once open sourced these can be reported via GitHub!
Please be aware that messages that just say "HELP" or "IT CRASHED" will be ignored as they don't help...
GOOD JOB .....Bro
kishorparmar said:
GOOD JOB .....Bro
Click to expand...
Click to collapse
Thanks
I hope it isn't too buggy and it works for you
Anyone already try this tool? I want download, but size so damn high
zipperX said:
Anyone already try this tool? I want download, but size so damn high
Click to expand...
Click to collapse
I knew that would be an issue. That's due to the fact it includes all the stock files for CM11S. However I will make it possible by downloading it within the app unzipping it and then flashing the device. But I'm fairly novice at c# and I don't have a lot of time to develop at this moment in time...
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
timmaaa said:
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Click to expand...
Click to collapse
Thank you I'll finally get noticed for something XD
... It works great but the size is a big deal.
Also, i suggest that ... you show what version of recovery you will flash - TWRP ( is generic and the filename does not gives you clue, the same for the others )
Also, for the Stock firmware ( wich version is it ?! )
SuperSU is not updated ... you could improve and use the last stable from chainfire
all the other things looks great so far.
itechy said:
Hey guys iTechy21 here and I am glad to announce I have a toolkit I have made. This is my first toolkit and is currently still being developed (adding / tweaking features) to allow you to easily do basic adb stuff and more advanced things are coming when I have time to develop this :silly:
This will also be 100% open source when fully complete but is released under the GPLV3 licence (apart from the stuff I did not develop e.g. Custom Recoveries, root.zip, adb / fastboot and stock software all rights go to their respective owners).
Click to expand...
Click to collapse
Can we have more mirrors (faster ones)? Like MEGA? Google Drive is kind of slow :cyclops: Great work!:good:
ygor.almeida said:
... It works great but the size is a big deal.
Also, i suggest that ... you show what version of recovery you will flash - TWRP ( is generic and the filename does not gives you clue, the same for the others )
Also, for the Stock firmware ( wich version is it ?! )
SuperSU is not updated ... you could improve and use the last stable from chainfire
all the other things looks great so far.
Click to expand...
Click to collapse
Thanks for the feedback. I may improve that make to another form with information on the specific versions (along with a built in download tool). Along with updating the SuperSU.zip
The first thing I'll do is work on that once all the basic features are there. But generally its the latest version of TWRP that is stable along with the other recoveries...
As for the stock I think the one I included was 44s but it may be 5Q (ew). Ill be implementing a downloader for the stock images to download whatever the latest version is from cyanogen...
sabrefresco said:
Can we have more mirrors (faster ones)? Like MEGA? Google Drive is kind of slow :cyclops: Great work!:good:
Click to expand...
Click to collapse
I'll see what I can do but the size will be reduced in the next update as it will remove the stock zip and replace it with a downloader which will download the stock images and then flash them reducing the size massively... (but I use Gdrive as its easy to find the download link unlike with Dev-host...)
I can´t flash twrp with this toolikt any one have a clue?
Do you have the adb drivers installed? Or is it throwing an error?
Updated to fix issues, add ota support, install APK's and improve performance
Sent from my A0001 using Tapatalk
Is "fully complete" v1.0.0? I'd love to stretch my C# muscles a bit.
EDIT: I can't read. Sorry.
dont worry about it
we always have moments... Its almost ready but I don't have a lot of time to develop so it may take me a while to get everything in there....
Just improving the ota updater now as its throwing exceptions...
Download link is not working. Please re-up. Thanks
godzulu said:
Download link is not working. Please re-up. Thanks
Click to expand...
Click to collapse
+1
If anyone has this file, send it to me and I can host it on one of the servers I rent. If we use a Dropbox link, it's going to get so much traffic that the persons account will get suspended.
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
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.