[ROM][OFFICIAL] RattlesnakeOS [Android 9.0] - Google Pixel 3 ROMs, Kernels, Recoveries, & Other

Intro
This is a bit different than most postings here, as I'm not providing any binaries to install on your phone and instead providing a simple tool, rattlesnakeos-stack, to build your own OS based on AOSP on a regular basis, with your own signing keys, and your own OTA updates. This probably will be interesting to a small subset of users as it does cost money to run this infrastructure in AWS.
What is RattlesnakeOS
RattlesnakeOS is a privacy and security focused Android OS for Google Pixel phones.
Features:
Based on latest AOSP 9.0 (Android P)
Support for Google Pixel, Pixel XL, Pixel 2, Pixel 2 XL, Pixel 3, Pixel 3 XL
Monthly software and firmware security fixes delivered through built in OTA updater
Maintain verified boot with a locked bootloader just like official Android but with your own personal signing keys
Latest Chromium browser and webview
Latest F-Droid client and privileged extension
Free of Google’s apps and services
Advanced build customization options
What is rattlesnakeos-stack
Rather than providing random binaries of RattlesnakeOS to install on your phone, I've gone the route of creating a cross platform tool, rattlesnakeos-stack, that provisions all of the AWS infrastructure needed to continuously build your own personal RattlesnakeOS, with your own signing keys, and your own OTA updates. It uses AWS Lambda to provision EC2 spot instances that build RattlesnakeOS and upload artifacts to S3. Resulting OS builds are configured to receive over the air updates from this environment. It only costs a few dollars a month to run (see FAQ for detailed cost breakdown).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How do I set this up?
Head over to the github repo and take a look at the README for full setup, build, and flashing instructions.

It is actually interesting.
Can we get in a chat or something to discuss this in detail. ?
Thanks for the help !

Looks cool! Probably wouldn't work on Project FI, though.

derelicte said:
Looks cool! Probably wouldn't work on Project FI, though.
Click to expand...
Click to collapse
It definitely won't work by default, but you can pin to a carrier like T-Mobile with APN settings if you are OK with losing the multi carrier feature of Fi.

Can we have screenshots of rom

Can you code the rom to tether over VPN, that would be a ultimate feature to add to your rom being that it is privacy based.

Do I need to be development savvy to do this? I know about as much to flash custom roms; is this above my skill level?

PistolSlap said:
Do I need to be development savvy to do this? I know about as much to flash custom roms; is this above my skill level?
Click to expand...
Click to collapse
It depends. While the rattlesnakeos-stack tool automates all of the build process for RattlesnakeOS, it is a bit more involved than your standard rom flashing and you will need to at least learn some of the basics of AWS in order to setup the prerequisites.

First of all, thanks a lot for working on such a niche but vital project.
I always wondered if we could ever have a simplified solution of building ROM directly from AOSP. Although, the architecture is AWS dependent (as of now), it's nevertheless a GREAT option for a lot of folks who have some familiarity with AWS and are AOSP enthusiasts.
I was able to successfully build the ROM a couple of times with a combination of some community patches. Tried out custom key signing with AVB as well.
Definitely, one of my favourite projects on XDA. Thanks again for your efforts, @dantheman78 !

A6020

dantheman78 said:
Intro
This is a bit different than most postings here, as I'm not providing any binaries to install on your phone and instead providing a simple tool, rattlesnakeos-stack, to build your own OS based on AOSP on a regular basis, with your own signing keys, and your own OTA updates. This probably will be interesting to a small subset of users as it does cost money to run this infrastructure in AWS.
What is RattlesnakeOS
RattlesnakeOS is a privacy and security focused Android OS for Google Pixel phones.
Features:
Based on latest AOSP 9.0 (Android P)
Support for Google Pixel, Pixel XL, Pixel 2, Pixel 2 XL, Pixel 3, Pixel 3 XL
Monthly software and firmware security fixes delivered through built in OTA updater
Maintain verified boot with a locked bootloader just like official Android but with your own personal signing keys
Latest Chromium browser and webview
Latest F-Droid client and privileged extension
Free of Google’s apps and services
Advanced build customization options
What is rattlesnakeos-stack
Rather than providing random binaries of RattlesnakeOS to install on your phone, I've gone the route of creating a cross platform tool, rattlesnakeos-stack, that provisions all of the AWS infrastructure needed to continuously build your own personal RattlesnakeOS, with your own signing keys, and your own OTA updates. It uses AWS Lambda to provision EC2 spot instances that build RattlesnakeOS and upload artifacts to S3. Resulting OS builds are configured to receive over the air updates from this environment. It only costs a few dollars a month to run (see FAQ for detailed cost breakdown).
How do I set this up?
Head over to the github repo and take a look at the README for full setup, build, and flashing instructions.
Click to expand...
Click to collapse
My first OTA update build ran today but failed.
Complete log attached. Any clues?
RattlesnakeOS Build FAILED
Device: blueline
Stack Name: rattlesnakeos-blueline-d0w1hujjra
Stack Version: 9.0.21
Stack Region: us-east-1
Release Channel: blueline-stable
Instance Type: c5.4xlarge
Instance Region: us-east-2
Build Date: 2019.01.10.00
Elapsed Time: 1hrs 25min 30sec
AOSP Build: PQ1A.190105.004
AOSP Branch: android-9.0.0_r30
Chromium Version: 71.0.3578.99
F-Droid Version: 1.5.1
F-Droid Priv Extension Version: 0.2.9
Build Reason: 'AOSP build PQ1A.181205.006 != PQ1A.190105.004' 'F-Droid version 1.5 != 1.5.1' 'F-Droid privileged extension 0.2.8 != 0.2.9'
face `android.text.Spannable` not found. It's needed to make sure desugaring of `android.support.v4.text.PrecomputedTextCompat` is correct. Desugaring will assume that this interface has no default method.

Alfa90 said:
My first OTA update build ran today but failed.
Complete log attached. Any clues?
RattlesnakeOS Build FAILED
Device: blueline
Stack Name: rattlesnakeos-blueline-d0w1hujjra
Stack Version: 9.0.21
Stack Region: us-east-1
Release Channel: blueline-stable
Instance Type: c5.4xlarge
Instance Region: us-east-2
Build Date: 2019.01.10.00
Elapsed Time: 1hrs 25min 30sec
AOSP Build: PQ1A.190105.004
AOSP Branch: android-9.0.0_r30
Chromium Version: 71.0.3578.99
F-Droid Version: 1.5.1
F-Droid Priv Extension Version: 0.2.9
Build Reason: 'AOSP build PQ1A.181205.006 != PQ1A.190105.004' 'F-Droid version 1.5 != 1.5.1' 'F-Droid privileged extension 0.2.8 != 0.2.9'
face `android.text.Spannable` not found. It's needed to make sure desugaring of `android.support.v4.text.PrecomputedTextCompat` is correct. Desugaring will assume that this interface has no default method.
Click to expand...
Click to collapse
Sorry about that. It was unfortunate timing because F-Droid Priv Extension managed to sneak in an update from 0.2.8 -> 0.2.9 that ended up causing build failures. I released a new version of tool v9.0.22 to fix it. You'll need to grab the latest to tool, deploy it, and then manually kick off a build.

Thanks. It's fixed with v9.0.22. :good:

dantheman78 said:
Sorry about that. It was unfortunate timing because F-Droid Priv Extension managed to sneak in an update from 0.2.8 -> 0.2.9 that ended up causing build failures. I released a new version of tool v9.0.22 to fix it. You'll need to grab the latest to tool, deploy it, and then manually kick off a build.
Click to expand...
Click to collapse
Can confirm that 9.0.22 fixes the build error. Thanks!

Alfa90 said:
I was able to successfully build the ROM a couple of times with a combination of some community patches. Tried out custom key signing with AVB as well.
Click to expand...
Click to collapse
Hello can you (or anyone else) provide a download link to your version of the ROM? Or a tutorial on how to build it? I looked at the resources and I have to admit it's way beyond my comprehension :"( but I wish there were more custom ROMs for pixel 3 there is only one other than this one.
Thanks!

PistolSlap said:
Hello can you (or anyone else) provide a download link to your version of the ROM? Or a tutorial on how to build it? I looked at the resources and I have to admit it's way beyond my comprehension :"( but I wish there were more custom ROMs for pixel 3 there is only one other than this one.
Thanks!
Click to expand...
Click to collapse
Sure mate. PM'd.

Alfa90 said:
Sure mate. PM'd.
Click to expand...
Click to collapse
Thanks dude! You rock!

First of all huge thanks to @dantheman78 for creating this awesome project! Working flawlessly so far.
Over at https://github.com/martepato/community_patches I added some patches. "00005-allow-unifiednlp-location-provider.patch" in particular could useful for people not wanting to install MicroG completely (and signature spoofing inevitably) but still be able to use UnifiedNLP.

hi all help me please i need micromax Q3001 custom rom

Hey @dantheman78 as of today I am not able to build RattlesnakeOS. Tried twice with the same result:
buildTypes.debug defaultConfig.versionCode 1005150
File /home/ubuntu/.android/repositories.cfg could not be loaded.
Checking the license for package Android SDK Build-Tools 27.0.3 in /home/ubuntu/sdk/licenses
Warning: License for package Android SDK Build-Tools 27.0.3 not accepted.
Checking the license for package Android SDK Platform 27 in /home/ubuntu/sdk/licenses
Warning: License for package Android SDK Platform 27 not accepted.
FAILURE: Build failed with an exception.
* What went wrong:
A problem occurred configuring project ':app'.
> Failed to install the following Android SDK packages as some licences have not been accepted.
platforms;android-27 Android SDK Platform 27
build-tools;27.0.3 Android SDK Build-Tools 27.0.3
To build this project, accept the SDK license agreements and install the missing components using the Android Studio SDK Manager.
Alternatively, to transfer the license agreements from one workstation to another, see http://d.android.com/r/studio-ui/export-licenses.html
Using Android SDK: /home/ubuntu/sdk
Click to expand...
Click to collapse
Hope you can help to resolve this
EDIT: 9.0.23 fixes this. Thank you Dan!

Related

Lineage OS -- Lineage OS Android Distribution

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I will update this thread when news will be available
Links:
Web Site:http://lineageos.org/
Gerrit reviewhttps://review.lineageos.org/#/q/status:open
Statushttp://status.lineageos.org
Facebook:https://www.facebook.com/LineageAndroid/
Twitter:https://twitter.com/lineageandroid
Google Plus:https://plus.google.com/109462427896521371620
Google Plus:https://plus.google.com/113897076738126120764
GitHub:https://github.com/lineageos
Reserved for changelogs, nightlies,...
How to install
Installing LineageOS from recovery
Make sure your computer has working*adb. Setup instructions can be found*here.
Download the*LineageOS install package*that you’d like to install.
•Optionally, download 3rd party application packages like*Google Apps
Place the LineageOS*.zip*package, as well as any other .zip packages on the root of*/sdcard:
•Using adb:*adb push filename.zip /sdcard/
•You can use any method you are comfortable with.*adb*is universal across all devices, and works both in Android and recovery mode, providing USB debugging is enabled.
If you aren’t already in recovery, boot into recovery:With the device powered down, hold the Volume Down and Power buttons.
(Optional, but recommended): Select the*Backup*button to create a backup.
Select*Wipe*and then*Factory Reset.
Select*Install.Navigate to*/sdcard, and select the LineageOS*.zip*package.
Follow the on-screen prompts to install the package.
(Optional): Install any additional packages using the same method.
Once installation has finished, return to the main menu, select*Reboot, and then*System.
Downloads: https://download.lineageos.org/oneplus2
First experimental build to upgrade from CM to LOS
https://mirrorbits.lineageos.org/fu...4.1-20170125-experimental-oneplus2-signed.zip
Changelog: https://www.cmxlog.com/14.1/oneplus2/
SuperSU: https://download.lineageos.org/extras
OTA Folder/data/data/org.lineageos.updater/app_updates
Fix alert slider
Open terminal
Code:
su
settings --cm put secure cm_setup_wizard_completed 1
News 24/12/2016
Yes, this is us.
You’ve probably read the news articles today. If you haven’t, please see the following:
https://cyngn.com/blog/cyanogen-services-shutting-down
https://www.cyanogenmod.org/blog/a-fork-in-the-road
So, yes, this is us. LineageOS will be a continuation of what CyanogenMod was. To quote Andy Rubin, this is the definition of open. A company pulling their support out of an open source project does not mean it has to die.
Check back for more information on Tuesday.
Written on December 24, 2016
News 28/12/2016
Infrastructure Status & Official Builds
We’re working on getting everything operational and would like to thank everyone who’s reached out offering assistance.
If you haven’t heard back from us, you should in the next week or so.
Current needs:
Build SlavesMust be able to finish (and upload)*make clean && make dist*within an hour, and be capable of running docker.Build MirrorsMinimum 100mbit network connectivity, 1gbit preferred.Minimum 500GB storage space.As a note, we’d prefer non-capped connections with static IPs, and they must be in some sort of professional hosting company (ie, datacenter, colocation facility, ISP, university, etc). While we appreciate the offers from people with gigabit at home, it’s slightly too hard to manage.
Please contact*[email protected]*if you are willing to provide either build slaves or build mirrors.
As a reminder: we have not started doing official builds yet. One of the benefits of this being an open source project is that anyone can build it, but please be careful flashing builds you’ve downloaded from other sources. We will have some more information on when weeklies (or possibly nightlies) will be starting soon.
Thanks!
LineageOS Team
Written on December 28, 2016
News 20/01/2017
Update & Build Prep
Alright, alright, alright - it’s nearly ‘go time’ for builds to start flowing. Before everyone gets excited and rushes to download, we want to cover a few important points.
First, we want to thank everyone that stepped forward to assist with the infrastructure (and offers continue to pour in). Thanks to you all, all infrastructure pieces are lighting up ‘Operational’ on our lovely status page.
Additionally, our Download Portal, Install stats page (yep, that’s 50k+ unofficial installs already!) and Wiki are all live. Notably, all three of these sites (and this blog) are open sourced - you can contribute to them via our Gerrit instance! Bear with us if these sites look bare at the moment, they will grow with content and design as we continue marching forward.
On to the fun stuff - build roster, release process and other details:
The build roster is ever growing, but we are supporting Marshmallow and Nougat capable devices.We’ll list the 80+ devices in a separate post.Our release cadence will be ‘weekly’ by default (to be nice to all the donated hardware).We will NOT be shipping root baked into the ROM.Root will be a downloadable zip based install similar to gapps installation (only need to flash it once).Home builders that want to bake su back into the ROM can use the command ‘export WITH_SU=true’ prior to building.Our official builds will all be signed with a private key for authentication and signature permission controlThis will not break, prevent or stop any ‘unofficial’ builds.Key verification info can be found on the wiki Verifying Build Authenticity page
Regarding installation, we recommend that users wipe when switching to LineageOS, and reinstall their gapps. However, we recognize that this can be time consuming, so we are offering an EXPERIMENTAL (read as, if it fails, you’ll have to wipe anyways) solution.
Alongside the ‘weekly’ release for your supported device, we’ll provide an EXPERIMENTAL data migration build.This build will allow you to ‘upgrade’ from CM to the signed LineageOS weeklyThis build may wipe permissions (you’ll have to re-allow app permissions), but should retain all user dataThis build will be watermarked with an ugly banner to ensure that you don’t permanently run this EXPERIMENTAL release, and upgrade to a normal weekly after.The process for this installation will be as follows:Install EXPERIMENTAL migration build on top of cm-13.0 or cm-14.1 build (don’t try to install LineageOS 13.0 on top of CM 14.1, that will not work).RebootInstall LineageOS weekly buildRebootRe-setup your application permissions
Given the EXPERIMENTAL nature of this process, we are going to remove this option in two months time.
Look for builds to start rolling out this weekend!
LineageOS Team
Written on January 20, 2017 by ciwrl
News 13/02/2017
Last week in LineageOS
WRITTEN ON FEBRUARY 13, 2017 BY HARRYYOUD
Lots of people have been asking for changelogs, so we’ll be making one for people who don’t want to trawl through Gerrit. If you want to know everything that’s changed in the last week or so, check*our Gerrit. We will refrain from adding changes for each device, as this would take too much time. Instead, things that have changed for everybody, new devices added to the roster, or*major*changes to devices (eg cm13->cm14.1, or massive breaking bug has been fixed) will be reported.
What’s changed then?
Removed AOSP Soundrecorder and CyanogenMod Screen Recorder, which have been replaced with our homegrown app, dubbed “Recorder”. This handles both sound and screen recordingCM*Lineage Wallpapers have returnedNew touchscreen gestures interface for devices that support it with customizable actionsA new website design, courtesy of*Aykut Yilmaz
It really doesn’t look like much, but*lots*of changes are happening, but most are behind the scenes things, and little edge bug fixes
Build roster
Added 14.1 devices
Samsung Galaxy Tab S2 8.0 (Wi-Fi) (2016) (Snapdragon) – gts28vewifiSamsung Galaxy Tab S2 9.7 (Wi-Fi) (2016) (Snapdragon) – gts210vewifiHTC 10 – pmeZTE Axon 7 – axon7Samsung Galaxy Tab S2 9.7 (LTE) (Exynos) – gts210ltexxSamsung Galaxy Tab S2 9.7 (Wi-Fi) (Exynos) – gts210wifiSamsung Galaxy S7 – herolteSamsung Galaxy S7 Edge – hero2lte
Added 13.0 devices
Motorola Moto X - ghostSamsung Galaxy Tab 2 7.0 / Tab 2 10.1 (GSM) – espresso3gSamsung Galaxy Tab 2 7.0 / Tab 2 10.1 (Wi-Fi / Wi-Fi + IR) – espressowifi
Where is the donation link?
Anxiously awaiting the future thanks to all who carry on the CM Legacy.
Added more info in first post
Enviado desde mi ONE A2003 mediante Tapatalk
Rad.
Anxiously waiting for the lineage OS. CM is a dead bull so we need someone to carry that legacy.
Update! Lineage OS for oneplus 2!!!?
Updated post 3 with more news.
They need servers
Enviado desde mi ONE A2003 mediante Tapatalk
I have send mail to internal maillist of my university. Maybe they want to bring infra support.
Salu2
What can we do to help?
Lineage OS for oneplus2 is out. Thanks Daktak :
https://www.google.fr/amp/www.cyano...ic/oneplus-2-lineage-14-1-nougat-7-1-rom/amp/
Envoyé de mon ONE A2001 en utilisant Tapatalk
hanslip said:
Lineage OS for oneplus2 is out. Thanks Daktak :
https://www.google.fr/amp/www.cyano...ic/oneplus-2-lineage-14-1-nougat-7-1-rom/amp/
Envoyé de mon ONE A2001 en utilisant Tapatalk
Click to expand...
Click to collapse
Is there the bootanimation etc from lineage OS or it's the old CM thing?
Nizur said:
Is there the bootanimation etc from lineage OS or it's the old CM thing?
Click to expand...
Click to collapse
There is actually no bootanimation, just a shinny "Android".
Possible to flash this over the latest Official cm14.1 Nightly or a clean start needed?
timebandi said:
Possible to flash this over the latest Official cm14.1 Nightly or a clean start needed?
Click to expand...
Click to collapse
Since it's partially the same, with only changes to display names from cyanogenmod to lineage os and removal of the boot animation, you can flash it like any other CM nightly. Not much has changed though, as the development has slowed down a bit because of focus being put on setting up new infrastructure for compiling and distribution of nightlies using sponsored or free servers/storage solutions now when we can't count on paid Cyanogen Inc servers.
Unofficial @Grarak's build
https://mirror.srvr.gdn/?dir=grarak/oneplus2
Enviado desde mi ONE A2003 mediante Tapatalk
I don't know if this is the best place to ask this kind of thing but I'm gonna wing it..
OP hasn't release an official N for OP2 yet so cm14 isn't using an N kernel/bootloader built by OP whatever etc etc..
Obviously I haven't updated to cm14 and won't update to an N system until afore mentioned issue is resolved by OP official updates..
Once OP has officially dropped an N update will Lineage OS build from that kernel and release an official build in the development section? Or is our N stuck to this informal general discussion release?
Has anyone tried this build?
Is it stable for daily usage?

[ROM][Samsung Galaxy S4][7.1.1[jfltespr]Team OctOs Oct-N

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer: OctOs is a WIP. It has been evaluated as being stable, and is suitable for daily use in most cases. While it may be considered stable, there may be unknown bugs. The development team is not responsible for any damage to your device or your information.
Click to expand...
Click to collapse
Team OctOs presents Oct-N.​
We maintain a current release record and change-log on our website: http://www.teamoctos.com
We have Gapps here.
http://opengapps.org
***USE Gapps of your choosing, we prefer Open Gapps***
- Please Do Not Mirror our files without talking to us. We can do that ourselves should we desire to. -​
Feature List
Substratum rootless theme engine support (must install Substratum from play store)
Tentacles settings!
Pixel Launcher Included
OmniSwitch
Power menu options
Screenshot
Screen record
DPI settings
Status bar time and date options
Status bar network traffic indicator
Status bar notification settings
Quick tile settings
Volume button playback control
Volume button wake
DUI (fling, pulse, smartbar)
Screen record
And much more!!!!
Click to expand...
Click to collapse
Frequently Asked Questions
Q: Is this Android 7 (Nougat)?
A: Yes, this is Android 7.1.1
Q: What code is Oct-N based on?
A: This version of Oct-N is based on LineageOS 14.1
Q: Why isn't there XYZ feature?
A: Shoot us a Suggestion if you want to see something added. While we are not going to promise to implement, we will always look into it
Q: But all the others have..
A: ROM developers, build something they want to use. The ROM developer that includes something they won't run implies less than 100% effort to ensure it does work. As a team, we have similar goals and objectives. If XYZ ROM has a feature you want, and we don't include (or don't want to include), feel free to use XYZ ROM, or build your own custom version of Oct-N.
Q: What about root?
A: Root is removed by default (user will be able to flash which ever root zip they want)
Bugs:
Bugs happen. Our testers are very good at breaking things, but no where near as good as the rest of the Android public. In order to investigate and fix issues, we need the help of the users who are going to report them. The Android OS has many nifty features to help us in this, but only if we can engage the user to assist us.
Logs, Logcat, and the Android Debugging Bridge (ADB)
Like any other OS, Android has multiple log files that are generated and record the goings-on of the system. As a user, you have two basic ways to view and pull these to send to us. Without the information in the logfiles, there simply is not a whole lot of information to go on.
Log file APKs
Team OctOs recommends SysLog from the Android Market. This application will allow you to selectively pick any (or all) of the system logs, compress them into a .ZIP file, and allow you to save, email, move to your Copy/DropBox/Cloud Storage account, etc.
ADB Logcat
The Android Debugging Bridge (ADB) is a powerful tool available from Google as part of the Android Software Development Kit (SDK). Used for many things, being able to selectively see, in real-time, what your device is doing cannot be downplayed. While there is more setup involved, if you are doing consistent ROM flashing, you really should invest the time to get setup properly to do it.
ADB Logcat tutorial here: How to create a logcat log
Basic Instructions:
Download ROM .zip file and MD5 file, and grab your favorite Open Gapps package http://opengapps.org
Reboot to Recovery (Note: Use Reboot to Recovery from Power Menu, Hardware-based boot to recovery, or adb reboot recovery - ROM Manager or similar software is NOT supported)
--- TWRP is the ONLY recovery Team OctOs uses - We do not support flashing on CWM ---
The Oct-N ROM installation script will automatically wipe /system, /cache, and /dalvik-cache. There is no need to do these before or after flashing the ROM unless you are instructed to by your Gapps Provider. When dirty flashing weekly updates, you MUST reflash Gapps along with any other files, apps, custom mods or kernels etc.. (anything that resides in system partition)
Flash ROM, GApps and any additional .ZIP files
Reboot
Download
Download from Team-OctOS web site!
Change log
View change log on Team-OctOS web site!
The foundation of the Android OS is the fact that is it open-source. We have all code we use internally in the creation of Oct-N available on our GitHub repositories.
Unless otherwise specified, all Oct-N builds kernel souce can be found on github at Team-OctOS.
Team OctOs GitHub - http://www.github.com/Team-OctOs
Team OctOs Gerrit Review - http://www.teamoctos.com:8080
Team OctOs GPLv2 License - http://www.teamoctos.com/license/
Team OctOs Patreon Campaign - https://www.patreon.com/TOctOs
Donate to OctOS Development (PayPal)
Want To Build Your Own?
Check out the ReadMe on our GitHub for Instructions
Special thanks to
Our testers, without which, there would be no public releases for OctOs
We would also like to thank
AOSP
Open Gapps
LineageOS
Anyone else who has ever submitted Open-Source code
Click to expand...
Click to collapse
Follow Team-OctOS!
XDA:DevDB Information
Oct-N, ROM for the Sprint Samsung Galaxy S4
Contributors
manfromgta, canodroid15
Source Code: https://github.com/Team-OctOS
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOS
Version Information
Status: Beta
Created 2017-01-13
Last Updated 2017-03-12
RESERVED
Weekly build will be released tonight.
Weekly 01/14
Weekly build and changelog are up on website!!!! Enjoy!!
https://www.teamoctos.com/oct-n-weekly-lineageos-base/
As with other LOS 14.1 builds for this device, cell service is dropping out constantly on my phone.
Same here, dropping and connects long enough to send a text, but not get the info that it sent it, so it sends the same text over and over every 30 seconds or so
bmccoy11 said:
As with other LOS 14.1 builds for this device, cell service is dropping out constantly on my phone.
Click to expand...
Click to collapse
Dokbot said:
Same here, dropping and connects long enough to send a text, but not get the info that it sent it, so it sends the same text over and over every 30 seconds or so
Click to expand...
Click to collapse
Which carriers are you guys with?
manfromgta said:
Which carriers are you guys with?
Click to expand...
Click to collapse
I'm on FreedomPop.
This hands down is the most stable (first build comparison), over all other 7.1.1 or 7.0 roms for this device. Everything works out of the box, albeit, some issues, like the photo of the acc not sticking and a couple other things (still looking.). But so far I'm loving it, it's already become my daily driver rom. Hopefully we get to see even more updates improving it.
Also a wee bit of a question, how do we handle OTA updates? system notified or do we have to look on the site for them? (latter would be a pain, I personally prefer system notifications.). Although I understand fully if it's not implemented yet.
Good job, OTC-OS!
We are on a weekly build system. They will commence Friday afternoon est. time. We will post here when they are up on site. However ota commits were merged today. If all goes well it will be ota after Fridays weekly.
So far everything works except the video camera, it can't connect to the camera when I switch from picture to video.
Update jan 20/17
New weekly is up on site
https://www.teamoctos.com/download/oct-14.1/jfltespr/OCT-N-WEEKLY-20170120-2146-jfltespr.zip
ROM works pretty well. Good enough for daily driver.
Running OctOs 01/20/2017 weekly
Sph-L720T
Boost Mobile (MVNOSlayer's APNs)
OK3 baseband
Cell, MMS, LTE, 3g work fine
Only issue is Bluetooth "phone" will not connect to my pioneer truck head unit. Audio through music, Pandora, etc. Work just fine but no Bluetooth calling.
Under "paired devices"
Pioneer Head Unit (no phone)
Even though phone is enabled in options
Pushing the call button on the head unit makes the unit try and connect and crashes Bluetooth all together.
Works with no problem under stock TW.
I believe this may be a CM/ Lineage upstream issue but I believe its an unknown issue
Any of you guys willing to join our test team on hangouts? We're looking for a few (2) actual Sprint testers (on Sprint not an mvno) Other carriers are welcome too of course.
If interested please email us at [email protected] & mention your device model number & carrier in the email.
Must be willing to use hangouts to test for us. We don't hand out test builds publicly for obvious reasons. We're looking for testers who are willing to hang around & test when needed. If we don't have testers we can't keep support up.
Thanks fellas!
canodroid15 said:
Any of you guys willing to join our test team on hangouts? We're looking for a few (2) actual Sprint testers (on Sprint not an mvno) Other carriers are welcome too of course.
If interested please email us at [email protected] & mention your device model number & carrier in the email.
Must be willing to use hangouts to test for us. We don't hand out test builds publicly for obvious reasons. We're looking for testers who are willing to hang around & test when needed. If we don't have testers we can't keep support up.
Thanks fellas!
Click to expand...
Click to collapse
Great, emailed
Update jan 27/17
New Weekly Available
OTA Updates
Dynamic Headers
Fab Recents
Check changelog for complete update
Download:
https://www.teamoctos.com/download/oct-14.1/jfltespr/OCT-N-WEEKLY-20170127-2006-jfltespr.zip
Running OCT-N-WEEKLY-20170127-2006-jfltespr / open_gapps-arm-7.1-pico-20170129
Sph-L720
Sprint carrier
OK3 baseband
Clean flash
No service, nothing.. Have to go back to previous rom. Don't know why I'm not getting any service.
Version
Hello , is this for both versions , SPH-L720 and SPH-L720T ?
Edit: Reason I asked is I have the regular model , not the Triband . I see Mavrikmeercat proclaiming success on telephony , LTE etc up above with a Tri-band . I did clean flash the rom . The telephony signal indicator flashes on and off about every 2 to 3 seconds like it's polling bands . When it flashes on it stays on less than a second but it does have signal for that split second . This is why I'm wondering about models . It's not just this rom , another cm based rom is exhibiting the same exact behavior . Thanks
stephaniee said:
Running OCT-N-WEEKLY-20170127-2006-jfltespr / open_gapps-arm-7.1-pico-20170129
Sph-L720
Sprint carrier
OK3 baseband
Clean flash
No service, nothing.. Have to go back to previous rom. Don't know why I'm not getting any service.
Click to expand...
Click to collapse
Please read: from OP
Bugs:
Bugs happen. Our testers are very good at breaking things, but no where near as good as the rest of the Android public. In order to investigate and fix issues, we need the help of the users who are going to report them. The Android OS has many nifty features to help us in this, but only if we can engage the user to assist us.
Logs, Logcat, and the Android Debugging Bridge (ADB)
Like any other OS, Android has multiple log files that are generated and record the goings-on of the system. As a user, you have two basic ways to view and pull these to send to us. Without the information in the logfiles, there simply is not a whole lot of information to go on.
Log file APKs
Team OctOs recommends SysLog from the Android Market. This application will allow you to selectively pick any (or all) of the system logs, compress them into a .ZIP file, and allow you to save, email, move to your Copy/DropBox/Cloud Storage account, etc.
ADB Logcat
The Android Debugging Bridge (ADB) is a powerful tool available from Google as part of the Android Software Development Kit (SDK). Used for many things, being able to selectively see, in real-time, what your device is doing cannot be downplayed. While there is more setup involved, if you are doing consistent ROM flashing, you really should invest the time to get setup properly to do it.
I'm actually having problems with the power switch. I have had the phone for years, guess it's time to finally put it to rest. I wish you luck with this rom! Going to be getting an LG V20.
I was planning on a re-install of the rooted stock OS. Before I did that I thought I'd test out this ROM. First impression is, I really like it. After installing the ROM everything was working great, but then all of a sudden SMS and MMS would no longer send. I am not sure what happened. It was working perfectly for the first few minutes.
I installed the ROM, GAPPS and TING APNs. I can't recall where I got the TING APNs from, but next I'll try the MVNOSlayer's APNs and see how it performs.
I do have LTE. I can use Chrome over LTE, but messages will not send about 5 minutes after the phone has re-booted.

[ROM][GNU/Linux][OTA][3.4.0.24] Sailfish OS for OnePlus 5T

This work is released under the permissive MIT license.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(click above image for higher resolution and quality images!)
Code:
#include <std_disclaimer.h>
/*
* I am NOT responsible for data loss, you getting fired because the alarm app failed or if you brick
* your device. Please do some research if you have any concerns about features included in this OS
* port before flashing! YOU are choosing to do these modifications, and if you point the finger at me
* for messing up your device, I will laugh at you.
* BOOM goes the dynamite!
*/
Hello, fellow XDA developers & users alike!
I think it's been long enough that we've not had alternative non-Android operating systems in a usable state for the popular OnePlus 5* devices, so here is a Sailfish OS port after over 6 months in development!
I'd really appreciate it if you give feedback and report bugs so I can attempt to fix them as best I can
Features
Slick and clean Sailfish OS UI/UX
Fully gesture driven navigation of the OS
Ambiences: a combination of system background, primary UI colors, sounds & volume levels
Sleep mode gestures e.g. double-tap to wake, music controls, 'V' for toggling flashlight etc
Ability to control configurable ambiences with the notification slider
Independent & alternative OS not based on Android (droid base is only used for drivers & HAL in SFOS)
Run regular GNU/Linux (armhf) tools and utilities natively out of the box from Jolla, OpenRepos, other custom repositories or direct binary format
Privacy-first OS with no spyware or bloatware pre-installed
Dual-booting between LineageOS & Sailfish OS with a simple zip flash in recovery (boot-switcher, linked below)
OS version OTAs, look at the merproject wiki page (see 'OTA updates' below)
A stable hardware adaptation (port) with basically everything working, but please also read about the problems right below
And more to explore...
Problems
No Android apps (APK) will run inside Sailfish OS as is the norm with community ports; you can just dual-boot with LineageOS (see FAQ below)
There is no VoLTE / VoWiFi support in SFOS at the moment (see FAQ below)
Even though NFC works, it's implementation is quite basic in Sailfish OS currently
Produced video recordings from the camera are unusable right now due to corruption of the beginning in recordings & artifacts when moving even slightly
Flashlight misbehaves for picture taking by taking too long to activate and causing nearly pitch black images (it also turns on/off rapidly a few times when disabling)
Some audio does not get routed properly to/from (Bluetooth) headsets
Sailfish OS Developer mode (SSH via USB cable) doesn't work
Rarely waking up from sleep mode can take a long time (up to about 15 seconds)
How to install
Backup all your data from the device to a computer
Download Pie Firmware 9.0.11, TWRP 3.4.x image, the LineageOS 16.0 base ROM & a Sailfish OS release
Install device firmware version 9.0.11 (not the ROM!)
Flash TWRP 3.4.x as your recovery
Reformat /data to ext4 and check it for issues
Reboot to recovery
Wipe cache & dalvik
Flash LineageOS 16.0
Flash anything else you normally flash for Android e.g. GApps, Magisk, no dm_verity etc
Flash Sailfish OS (the zip that contains rootfs.tar.bz2) from inside CI artifacts archive
Reboot and enjoy!
You can also flash my boot-switcher zip (or switch between hybris-boot and droid-boot images created on /sdcard) afterwards for simple dual-booting of the 2 operating systems!
Links & source
sailfishos-oneplus5: All project repos & source
important: Info and detailed guides about flashing, self-building etc
android_kernel_oneplus_msm8998: The used kernel source
sailfishos.org: General info about the OS as well as contributing, translation, app development etc
Changelog
wiki.merproject.org: Place with general info about the port status, OTAs etc
droid-config commits: Stuff modified on the Sailfish OS side
OTA updates
See "OTA (Over-the-Air) update" section under the libhybris adaptation wiki page.
Special thanks to
kimmoli for gesture-daemon & triambience
nathanchance for maintaining the OP5 linux-stable merged kernel tree
Mister_Magister, mal, r0kk3rz, rinigus, PiggZ, spiiroin, jusa, vknecht, NotKit and everyone else at #sailfishos-porters
The port was made possible thanks to you all!
FAQ
What does "SFOS" mean?
Sailfish OS; it's simply a common abbreviation.
Can I run [insert name here] Android app in Sailfish OS?
If there is no currently maintained client or similar app in the Jolla Store or (my preference) OpenRepos, then probably not. I may look into bringing Android app support via Anbox or similar project much later on; no ETAs.
Does VoLTE or VoWiFi work in Sailfish OS?
As of SFOS 3.4.0, these are still not implemented, but should be coming later in perhaps Sailfish OS 4.
How can I skip the SFOS beginner tutorial?
Tap each corner of the screen once starting from top-left going clockwise.
I found a bug, what can I do?
See "Report bugs" section under the libhybris adaptation wiki page.
XDA:DevDB Information
[ROM][GNU/Linux][OTA][3.4.0.24] Sailfish OS for OnePlus 5T, ROM for the OnePlus 5T
Contributors
deathmist
Source Code: https://github.com/sailfishos-oneplus5
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: 9.0.11 (Pie)
Based On: LineageOS 16.0
Version Information
Status: Stable
Current Stable Version: 3.4.0.24 (Pallas-Yllästunturi)
Created 2020-01-17
Last Updated 2020-12-10
Reserved
Excellent friend. I will try it
This is super exciting!!!
There has been a long-standing issue with NFC always getting re-enabled after a reboot in SFOS. Obviously this is not what you'd want as it causes unnecessary battery drain even when NFC is entirely unused.
This was happening due to a directory ownership issue and should be fixed in the next Sailfish OS release officially.
For now though I fixed this manually on the new uploaded Sailfish OS image (zip), BUT if you already have the OS installed (flashed build <=20200117), you can just reinstall nfcd from a terminal & toggle the option once in Settings to fix the same issue:
Code:
devel-su zypper in --force nfcd
Hi, excellent work. I took it for a test. Great rom and it's nice to see this alternative on this device. Love the concept of a Google free OS and it has a nice UI. First boot didn't take a long time at all for me. Camera issues and not being able to install apps via F-droid or apkmirror is a minor set back. I'd love to run this as my DD, but it requires some workarounds for me.
I was considering using my old phone (nexus 6) for the missing apps and games to avoid dual booting.
Looking forward to seeing what the future brings with this OS. Keep up the good work ??
For the amount of bugs we usually see in SailfishOS ROMs, this is pretty stable! Thanks for your hard work
Very exciting, once the camera issues are sorted out I would love to give this a try as a DD ?. Nice work I am genuinely very excited.
Will this be able to work on any other OS aside from LOS?
jasonsas102 said:
Will this be able to work on any other OS aside from LOS?
Click to expand...
Click to collapse
Doubt it, but currently you could try any other Oreo-based ROM too if you want to see (I'm not providing any kind of support though for anything other than the LineageOS base). I answered this previously on the OP5 thread post #21.
Very cool! I used early SFOS builds on my Nexus 5 years ago. I'll have to try this out at some point! Great work on porting it. I'll be keeping an eye on the thread for future updates.
deathmist said:
Doubt it, but currently you could try any other Oreo-based ROM too if you want to see (I'm not providing any kind of support though for anything other than the LineageOS base). I answered this previously on the OP5 thread post #21.
Click to expand...
Click to collapse
alright well if I decide to go that route I'll make sure to tell you if it works or not
Well something new.
How to take screenshots of the desktop?
Dgonix said:
How to take screenshots of the desktop?
Click to expand...
Click to collapse
To take a screenshot in Sailfish OS you can simply press and hold volume up & volume down, you should see a notification once this happens
For a delayed screenshots there is a "Screenshot" app in the Jolla Store as well
If you have to have LineageOS 15 - are you able to update to LOS16after Sailfish is installed or are you stuck on 15? Thanks.
anarchotaoist said:
If you have to have LineageOS 15 - are you able to update to LOS16after Sailfish is installed or are you stuck on 15? Thanks.
Click to expand...
Click to collapse
Nope, this Sailfish OS port for 15.1 Oreo firmware only currently as that is the LineageOS version the port's Android kernel and HAL parts are built around; anything else will result in a non-booting device (using the SFOS hybris-boot image anyway).
Upgrade to Sailfish OS 3.3.0 (Rokua)
Hello everyone!
The port has now been upgraded to SFOS 3.3.0 and HAL components are now all based on Android 9 Pie!
Check out the details of this release here!
deathmist said:
Hello everyone!
The port has now been upgraded to SFOS 3.3.0 and HAL components are now all based on Android 9 Pie!
Check out the details of this release here!
EDIT: I know the LineageOS downloads site is sadly down currently (as is the merproject wiki), you could perhaps scavange the internet for a mirror of some older build or just wait a while till the problems are resolved on their ends :fingers-crossed:
Click to expand...
Click to collapse
can i ask that fingerprint it works?
JR Bautista said:
can i ask that fingerprint it works?
Click to expand...
Click to collapse
Still a nope sadly. Looking at kernel logs / logcat the hardware seems to be ready, we just need the middleware pieces from Jolla that are currently closed source and only working on some of their official Sony Xperia ports I even asked about it and apparently there is no news currently.

[GSI][12] LineageOS 19.x GSI (A64B/64B)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Background:
This is a natural continuation/extension of the LineageOS 18.x GSIs I've been making since 2020.
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS GitHub repo. And if you would like to contribute to LineageOS, please visit Gerrit Code Review.
Click to expand...
Click to collapse
Disclaimer:
This is still mostly a LineageOS team / PHH @phhusson effort, credits to them and all associated for making all this possible.
No flashing instructions will be offered. If you're here in this forum, you should know what you're doing.
No guarantees that everything would work. This is a GSI, bugs are bound to happen.
Must-read:
You are STRONGLY ADVISED to try PHH's AOSP of equivalent version FIRST and identify/report issues there, before moving onto other GSIs that are based on his work, including this one.
If you do find bugs on this GSI and want to report, then you MUST try reproducing on AOSP, and ONLY proceed to report here when it's specific to this GSI. This filters out bugs common to all PHH-based GSIs, which you should let PHH know, not me. I might silently ignore your report if you skip this.
Download:
https://sourceforge.net/projects/andyyan-gsi/files/
Compressed as .xz archives - extract first.
Stuff on GitHub (builders-only):
Since builders' stuff aren't really interesting to end users, I decided not to separately document the modifications needed in this post; instead just check out these repos, where most things should be self-explanatory. Not the cleanest code, but should help if you need some clues.
lineage_build_unified - my unified script for building
lineage_patches_unified - my unified patches for building, including patches from PHH
sas-creator - generates VNDKLite and secure variants, can be used without a building environment
Donate?
https://paypal.me/AndyCGYan
Reserved
Notes:
I now have a rather taxing day job, and can't devote nearly as much time/effort into this as I did as a student.
GAPPS builds are offered as-is without guarantees. Read #10 for more.
/system is RO on regular builds and RW on VNDKLite builds. VNDKLite builds can be used on most non-VNDKLite devices as well.
ADB is intentionally insecure, even on first boot (turned on by default and no authentication needed). GSIs are more fragile compared to device-specific custom ROMs, both on first boot (no-boot issues) and on subsequent boots (after tuning certain Treble settings), and I insist that no-auth ADB is a must-have for debugging and general fail-safe.
Signature spoofing (MicroG) is supported, but only for priv-apps. This is a security consideration from PHH.
Magisk support should be on par with A11 (thanks @eremitein). The "abnormal state / unsupported SU" warning can be ignored. For devices that still don't play well with Magisk (e.g. kernel restrictions implemented by OEM), use PHH-SU instead. Install the app and you'll get root for apps.
Initial builds are based on PHH v400.c and November security patches.
Sigh, I don't really want to make a thread this early...
BTW, 32-bit and A-only users, you should really move on.
Big work thank You
Hey How to flash this Gsi Guys can someone answer me????
Thank you so much. Are gapps included ?
walid77dz said:
Thank you so much. Are gapps included ?
Click to expand...
Click to collapse
From an earlier post...
AndyYan said:
32*/A32* users, I'm not stopping your monthly builds just yet, but 32-bit is getting phased out, and you should upgrade soon. Similar goes for A-only. Ideally in the future we'll only have 64B, making room for other much needed variants such as GAPPS.
Click to expand...
Click to collapse
Their deprecation does seem likely now, so I'll try a GAPPS build or two when I have time.
Do you consider this alpha usable as daily driver?
And, does it require clean installation from LOS 18 GSI?
Avraham Tsaban said:
Do you consider this alpha usable as daily driver?
And, does it require clean installation from LOS 18 GSI?
Click to expand...
Click to collapse
I am using it as my daily driver - I enabled Gallery and LiveDisplay for just that purpose.
Out of curiosity I did try a dirty install from 18.1. It booted and most apps work, to my surprise, but Messaging won't allow me to select contacts properly no matter what, and that was a blocker, so don't.
People who love LOS, insist on using GAPPS with it, and had been asking me for such builds all this time - I now have a lil something for you, a test LOS19 build with GAPPS built-in. It's intentionally in the "personal" flavor to discourage use as your daily driver, but also shared-blocks (unlike previous "personal" builds) to save some space.
It was more trivial to build than I thought, but that doesn't mean I'll build it alongside vanilla yet...
Every variant takes disk space and build time
The image itself is huge and won't fit in even slightly older devices
Too many archs/variants confuse users
I cannot make any guarantees about it
I've seldom mentioned the last point, yet it's critical - I'm in China and I don't use GAPPS at all, so I have little idea about what counts as "properly working" for GAPPS and how to troubleshoot them. Even if I do eventually build with GAPPS, I can only provide builds as-is, and you'll have to help each other out on GAPPS-related/-induced issues. At the end of the day, I still recommend using other ROMs that are built around GAPPS, e.g. @ponces ' PE, for a more cohesive experience and better support.
For now, all I know is this test build logs in (after registering the device here), can open Play Store and download apps, nothing beyond that.
Huawei P20L mobile data doesn't work
confirmed working on huawei mediapad m5 (cmr-w09 model name)
thx so much AndyYan
first degoogled android 12
su working via phh su app - magisk wasn't working proper
I do the installation through fastboot, because I don't have twrp, The installation is successful, but when I start to start the installation it gives an error: Invalid sparse file format at header magic, and after that it installs normally, but when I start the system, it gets stuck in the logo of the manufacturer of my device, Any solution?
Flashed this ROM on my Oneplus 9 Pro and was surprised how great and smooth it is.
I read on a thread how to fix fingerprint issue on GSI ROM by editing /vendor/build.prop, tried it and ended up in bootloop and I have to start all over.
What's the right way to do this?
Thanks in advance.
Geoz said:
fix fingerprint issue on GSI ROM
Click to expand...
Click to collapse
You don't - no A12 GSIs support UDFPS yet.
AndyYan said:
You don't - no A12 GSIs support UDFPS yet.
Click to expand...
Click to collapse
Good to know. I appreciate you taking the time to explain this.
Thanks.
Geoz said:
Good to know. I appreciate you taking the time to explain this.
Thanks.
Click to expand...
Click to collapse
BTW, I believe most OPlus devices have read-only vendor, so even in the future you probably shouldn't head down that road.
AndyYan said:
BTW, I believe most OPlus devices have read-only vendor, so even in the future you probably shouldn't head down that road.
Click to expand...
Click to collapse
What of if I use Lineage OS as the base?
Thanks again.
Geoz said:
What of if I use Lineage OS as the base?
Thanks again.
Click to expand...
Click to collapse
That depends on your maintainer (LuK), and also PHH only deals with issues with stock vendors.
Speaking of which, looks like someone else also can't wait for LuK's 19.0, hehe...
AndyYan said:
That depends on your maintainer (LuK), and also PHH only deals with issues with stock vendors.
Speaking of which, looks like someone else also can't wait for LuK's 19.0, hehe...
Click to expand...
Click to collapse
First time on GSI ROM but I'm really impressed. I've learned a lot from you in a very short time. All information I read on the internet is not valid rather from a developer like you.
I appreciate you.

[OFFICIAL] LineageOS 20 for OnePlus 5T (dumpling)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Introduction
LineageOS, an open-source Android distribution, is available for several devices,
with more being continuously added thanks to the biggest, yet ever growing, Android open-source community.
Join us and breathe new life in your device, be it old or new.
Click to expand...
Click to collapse
If you don't know LineageOS and would like to read about it before installing it you can take a look at the official Website.
Features
Individuality
Customization is paramount to productivity.
That’s why LineageOS promises to push for user personalization and preference.
Everyone is unique and your device should be too.
Click to expand...
Click to collapse
Security
Trust will help you understand the security of your device and warn you about possible threats.
We take security very seriously: that’s why we deliver security updates every month to all our supported devices.
And to make your device more secure, lock everything behind an enhanced lock screen.
Click to expand...
Click to collapse
Longevity
LineageOS extends the functionality and lifespan of mobile devices from more than 20 different manufacturers thanks to our open-source community of contributors from all around the world.
Click to expand...
Click to collapse
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended recovery in the official installation instructions link below.
If you are coming from stock or other ROMs, you need to do a factory reset.
As always, make sure to backup before installing this ROM.
More detailed instructions at:
Install LineageOS on dumpling.
Downloads
Download LineageOS 20
Source code
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
The device specific source code can be found in the LineageOS Github repo.
OnePlus 5T device tree
OnePlus MSM8998 kernel
Bug reports:
Please submit bugs and other errors in this thread
Donate to support development:
Donate via PayPal to vware
Contributors
Georg Veichtlbauer
And of course all LineageOS & Android contributors
OS Version: Android 13
Kernel: Linux 4.4.302
Version Information
Status: Stable
Created 2022-09-17
Last Updated 2022-12-31
Major Changes (December 4):
- Kernel updates
- SELinux improvements
I've been using this as my daily driver for almost a week. Everything works fine. Thank you dev
qsnc said:
Okay guys, initial release. This should work just fine, but keep in mind that many LineageOS specific features are not available yet!
Click to expand...
Click to collapse
What features are missing?
I'm using version 19.1, what will I lose by upgrading to 20?
Wow this realy works fine! Amazing work und doesnt feel experimental at all.
My list of problems:
system color scheme (material you) is not customizable
Paypal not working
Gpay not working
Backup for system settings on gdrive not working
Thank you!
Works fine, thank you! Anyone able to successfully install a stable gapps version?
marmotz said:
What features are missing?
I'm using version 19.1, what will I lose by upgrading to 20?
Click to expand...
Click to collapse
no, upgrading from 19 should be fine. do be careful with gapps though, as usual.
maltumbo said:
Wow this realy works fine! Amazing work und doesnt feel experimental at all.
My list of problems:
system color scheme (material you) is not customizable
Paypal not working
Gpay not working
Backup for system settings on gdrive not working
Thank you!
Click to expand...
Click to collapse
as mentioned, some features are still missing. paypal/gpay likely a gapps issue not related to android itself - i've had the same trouble and been in contact with paypal, but they're sort of slow.
new build with quite a lot of improvements is up, try it out
New build works fine. Thanks for the colors!
Auto hide centered clock in status bar works as intended now. Pretty cool.
Thanks again
Thx for the update
New build is just phenomenal. Thanks.
shariful.sourav said:
New build is just phenomenal. Thanks.
Click to expand...
Click to collapse
That much ?
With your build i get twrp error. Twrp can't mount data.
of course it can't - its android 13, twrp does not support decryption for that.
anyhow, just sideload the zip files in recovery, twrp is not really a supported scenario anyway i am afraid
I'd like to suggest a moratorium on all Android 12/13 development. Seems to me Android 11 is just fine, and Android 12 sucks badly. Android 13 is just more of the same nonsense.
I'm not against progress, but I am against pointless "version inflation".
YES to fixes and improvements. A big NO to endless mindless dead-end "enhancements".
Just as financial inflation makes a suitcase of banknotes worthless, version inflation leaves you worse off than you were before.
But the thing with banking apps and PayPal freaks me out! Any suggestions or hope for future updates on this matter?
Greetings and eyes up guardian!
new build is up, again with plenty of changes, LineageOS team is hard at work!
regarding banking/paypal: there are ways around this, but i can't support this officially here as it has nothing to do with lineage itself. try looking into magisk and it's zygisk functionality, i am sure google can help you (or other threads on xda), but please not in this one
I built LineageOS from source some time ago but I gave it up because it was full of analytics baked deep within the ROM.
Is it still the case or are LineageOS ROMs free of analytics nowadays?
what in the world are you talking about...?
About a dirty flash
Initial setup: latest official LOS 19.1 recovery/build + MindTheGApp + ih8sn ... (No root so no magisk)
About ih8sn (bypassing Safetynet attestation without Magisk): see this post
Prerequisites:
1- Download latest unofficial LOS 20 build (see OP)
2- Download Latest MindTheGapp (13 arm64)
3- Optional: download ih8sn for OP5T (here) ... if you don’t want to rely on Magisk to pass SafetyNet attestation!
Procedure:
1- Boot to LOS recovery
2- Optional (but recommended): Factory reset > Format cache and system partitions
3- Apply Update from ADB or USB OTG in sequence ... LOS build, MindTheGapp and ih8sn (optional)
4- Reboot system now
5- Enjoy
See attached files
Note: works with a locked or unlocked bootloader ...
Many thanks to @qsnc and @T1mb3 !
update now live, plenty of changes yet again. see post #1 and #2
give it a good whirl and try to find problems!

Categories

Resources