{
"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.
Related
{
"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"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 8.1 (Oreo), 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. Linked below is a package that has come from another Android project that restore the Google parts. 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 out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What's special about my build:
Sometimes I pick a few patches from the Lineage Gerrit before they are approved and merged into our trees.
The kernel is based on Lineage's one, but I have upstreamed with the latest patches from linux-stable, added a few things such as performance and battery tweaks, security and stability fixes, SafetyNet spoofing, additional kernel controls.... This kind of things
The device trees will also be improved overtime with various improvements from mixed sources (for example better presets, different HAL solutions and so on).
All the rest is kept as recommended in the maintainer's manifest (including the optional patches).
What's working:
Boots
RIL (Calls, SMS, Data)
Wi-Fi
Bluetooth
NFC
Camera
Video Playback
Audio (Record and Playback)
Fingerprint (with gestures)
Sensors
Flash
Notification LED
SELinux
SafetyNet
What's not working:
VoLTE calls are currently not working
With February security patches, TWRP is unable to decrypt data. The only way to be able to access it is removing any lockscreen PIN or password before entering recovery. This will be addressed by the TWRP guys soon.
Instructions:
Before instaling, make sure you are running the latest Open Beta 3 firmware.
If you are unencrypted take a full backup of all your data, because this ROM enforces encryption and so you will have to format your phone.
If you are encrypted and running an AOSP ROM (8.0 or newer) you're fine. If you come from OOS (both Nougat and Oreo) take a full backup of all your data as there's currently not way to change masterkey without formatting, sorry you should be able to go ahead and flash without formatting the internal storage, just make sure to remove any screen lock before switching ROM.
Download the latest build and GApps (both links are below).
Reboot to a custom recovery (latest unified codeworkx's build works perfectly and supports masterkey3 encryption).
If you are coming from any other ROM (even LineageOS 15.0 or 15.1) wiping /data is strongly recommended
Flash the latest build and GApps.
If you want root, flash it afterwards. If you plan to use Magisk, let the first boot happen and flash it later!
Reboot and enjoy :good:
Downloads:
ROM: lineage-15.1-20180216-UNOFFICIAL-kylothow-dumpling.zip
Google Apps: OpenGapps 8.1 (UNOFFICIAL)
Reporting bugs:
Grab a logcat right after the problem has occurred (please include at least a few pages of the log, not just the last few lines, unless you know what you're doing).
If it is a random reboot, grab /proc/last_kmsg (do not bother getting a logcat unless you can get it just before the reboot, a logcat after a reboot is useless).
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log (only applies to SELinux enforcing builds).
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues.
Credits:
This is a very important note: I am NOT the original developer of the device trees I'm using. Despite I do my best to fix bugs, improve security, stabilty and the performance of the ROM, it's not thanks to me that this is up and running now.
Please, be sure to thank and donate to the developers behind the device trees.
Huge thanks and credits to the NastyAndroidDevs team (https://github.com/NastyAndroidDevs).
@amartinz: https://github.com/amartinz
@codeworkx: https://github.com/codeworkx
@jrizzoli: https://github.com/jrizzoli
@jumoog: https://github.com/jumoog
Sources:
Device Trees (Reference): LineageOS
Kernel Tree (Reference): LineageOS
Manifest (Reference): NastyAndroidDevs
Device Trees (Custom): EvilDumplings
Kernel Tree (Custom): EvilDumplings
Manifest (Custom): EvilDumplings
Announcements/News:
20 December 2017:
The official LineageOS 15.1 dumpling and cheeseburger device trees are being uploaded on LineageOS' official GitHub account.
31 December 2017:
The fist working unofficial LineageOS 15.1 builds are going live
I made all my changes to NastyAndroidDevs' sources public. See the "Sources" section in the OP.
Thanks
kylothow said:
mine
Click to expand...
Click to collapse
Thnks for your hardwork and time. ?
Thanks:good:
downloading
Will you become the official maintainer for lineage OS for the oneplus 5t in the future?
Colday96 said:
Will you become the official maintainer for lineage OS for the oneplus 5t in the future?
Click to expand...
Click to collapse
As I said in the OP, I'm not the developer behind the device trees, it's all thanks to the NastyAndroidDevs (with pretty known names, if you know CyanogenMod/Lineage) who are unifying the OnePlus 5 and 5T sources (with a common tree with most stuff); it's likely one or more of them will maintain the device.
good morning first of all thanks for putting the ROM looks very good pinta.queria know if facial recognition works to unlock with the face. Thanks and greetings
Enviado desde mi ONEPLUS A5010 mediante Tapatalk
Great! It's finally coming to op5t
This is great news. Will we get a LOS 14.1 build then too? LOS 15 is still missing a lot of features unfortunately. It would be nice to have LOS 14.1 until things like the privacy manager and such get incorporated into LOS 15.
Nice to see this here, even if some basic features are still missing.
YAAAAASSS
CommanderROR said:
Nice to see this here, even if some basic features are still missing.
Click to expand...
Click to collapse
The biggest one is camera.
I think I should be able to fix Camera and NFC soon...
Great!
Thanks for your hard work on this.
I'd love an aosp rom on the BEA5T!!
I have a problem, when i flash the rom on twrp ive got error 7: "Rom is for dumpling, your device is: OnePlus 5T".
WTF?!
Kookitza said:
I have a problem, when i flash the rom on twrp ive got error 7: "Rom is for dumpling, your device is: OnePlus 5T".
WTF?!
Click to expand...
Click to collapse
That's because in device tree, ro.product.device property has been set as "dumpling", @kylothow , perhaps, it should be set to "OnePlus5T", the value that TWRP reads from device when the assert is checked while flashing.
EDIT:
In device tree, file BoardConfig.mk:
Code:
TARGET_OTA_ASSERT_DEVICE := [B]dumpling[/B]
...I get a little annoyed because not unified criteria about naming OP5T.
BitOBSessiOn said:
That's because in device tree, ro.product.device property has been set as "dumpling", perhaps, it should set to "OnePlus5T", the value that TWRP reads from device when the assert is checked while flashing.
Click to expand...
Click to collapse
This is something that we can change on build.prop or we should wait for the dev?
Kookitza said:
This is something that we can change on build.prop or we should wait for the dev?
Click to expand...
Click to collapse
You can unzip (or use something like mc...), edit the flashing script (META-INF/com/google/android/updater-script) delete the first two lines (assert...), repack/save zip, and try again...
BitOBSessiOn said:
You can unzip (or use something like mc...), edit the flashing script (META-INF/com/google/android/updater-script) delete the first two lines (assert...), repack/save zip, and try again...
Click to expand...
Click to collapse
Can you upload the right file (Updater-script), cause i think i messed it :/
{
"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"
}
CarbonROM is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.
Please feel free to look, build, and use our code at CarbonROM's GitHub... and at CarbonROM Gerrit.
Pre-Disclaimer:
THIS IS AN DEV PREVIEW BUILD. The intent is to showcase what is coming up soon.
Please keep any problems with those builds in this thread, we don't accept any bugreports for preview builds anywhere else.
Also, we know this works on other treble devices. Please be aware that we can only provide limited support for those.
Disclaimer:
While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash!
Support:
We spend an astonishing amount of time developing this software. We can't spend much time on XDA as a result, so if you need support, please try the following:
1) Search. Search, search, search. Yes, you. I don't care how unique or important your question is, it's very likely someone has adressed it already. Especially if you're even close to new at this.
2) Read our FAQ, which can be found on our website. Carbon FAQ
3) Ask a question in your device forum. Someone will no doubt try to help you. Warning: this help may come in the form of telling you it's a dumb question that has been asked before. See step 1 - such are the perils of asking questions when you haven't done the research yourself. Android is about helping yourself.
4) Join our Discord server! There, you can connect with other Carbon users and our developers, and you can get quicker responses to your bug reports. The invite link is right below.
Notice:
This build includes GApps for now.
Before you flash, make sure you're on the latest 8.x stock builds, then flash the system.img in fastboot.
Download Mirror
Changelog
GitHub
Gerrit
Device and Kernel sources
Remember, every penny you send to us goes right back into the rom. It's used for hardware, server costs, etc - all the things that help us make Carbon better with every release. Your support means the world to us! If you've enjoyed Carbon, please consider a donation toward this goal. Thank you, and we hope you continue to enjoy Carbon!
XDA:DevDB Information
CarbonROM, ROM for the Honor View 10
Contributors
Myself5, CarbonROM, berkeley-dev Team
Source Code: https://github.com/CarbonROM
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
Based On: AOSP
Version Information
Status: Testing
Created 2018-02-22
Last Updated 2018-04-15
Many thanks for bring us this ROM
Enviado desde mi BKL-L09 mediante Tapatalk
Great. Now development has gained speed. Love to see these roms for our beloved v10
Nice job in the release Chris!
Sweet. Nice job
Great one.
Does this have fingerprint based navigation just as in EMUI, so that we could disable the onscreen navigation bar?
Can i flash this via TWRP Recovery??? I see this is not a flashable zip, so can i flash the image ?
shihabsoft said:
Great one.
Does this have fingerprint based navigation just as in EMUI, so that we could disable the onscreen navigation bar?
Click to expand...
Click to collapse
Not yet, but we're working on it.
sam razzy said:
Can i flash this via TWRP Recovery??? I see this is not a flashable zip, so can i flash the image ?
Click to expand...
Click to collapse
I guess you could. I honestly didn't try.
Myself5 said:
Not yet, but we're working on it.
I guess you could. I honestly didn't try.
Click to expand...
Click to collapse
Take look at Lenovo zuk z2 plus it has same FP gestures like honor v10 for back,recent etc and its working on all rom that are present for that device
sam razzy said:
Can i flash this via TWRP Recovery??? I see this is not a flashable zip, so can i flash the image ?
Click to expand...
Click to collapse
U can try flashing like a img in install menu. But idk if it works [emoji17]
Enviado desde mi BKL-L09 mediante Tapatalk
What its caffeine?
When you implement fingerprint gestures?
VivekBhagat said:
Take look at Lenovo zuk z2 plus it has same FP gestures like honor v10 for back,recent etc and its working on all rom that are present for that device
Click to expand...
Click to collapse
Most vendors define those gestures as keyevents. Huawei obviously uses an API to perform them (and not native Linux keyevents support). Anyways, you have a plethora of third party apps that can do this for you.
Excuse me for the noob question, but if this ROM is treble compatible, should I in theory be able to flash it and boot it on my Pixel 2 XL?
I know the 2XL already has CarbonROM but I'm curious about what treble brings to the table.
BadWolfYe said:
What its caffeine?
When you implement fingerprint gestures?
Click to expand...
Click to collapse
Caffeine keeps the screen on for as long as the counter is running, or until you manually disable it. Useful for reading without permanently pressing the screen.
Interceptor777 said:
Excuse me for the noob question, but if this ROM is treble compatible, should I in theory be able to flash it and boot it on my Pixel 2 XL?
I know the 2XL already has CarbonROM but I'm curious about what treble brings to the table.
Click to expand...
Click to collapse
In a very theoretic mind experiment: yes. Practically: No. The 2XL has AVB that would prevent it from booting. I honestly wouldn't know what happens if you disable AVB, but my guess it that it doesn't boot (because the 2XL feels special). If you feel like trying, I won't stop you
BadWolfYe said:
What its caffeine?
When you implement fingerprint gestures?
Click to expand...
Click to collapse
Fingerprint gestures should be in the next build
download link not working...
ink718 said:
download link not working...
Click to expand...
Click to collapse
It's working. Just downloaded.
Myself5 said:
Caffeine keeps the screen on for as long as the counter is running, or until you manually disable it. Useful for reading without permanently pressing the screen.
In a very theoretic mind experiment: yes. Practically: No. The 2XL has AVB that would prevent it from booting. I honestly wouldn't know what happens if you disable AVB, but my guess it that it doesn't boot (because the 2XL feels special). If you feel like trying, I won't stop you
Click to expand...
Click to collapse
Actually AVB can be disabled, it has to be disabled to boot non-stock ROMs. I have a ZIP which can disable it. All it does is give you a popup after boot about a partition mismatch but the phone works fine.
So you think, in theory, with AVB disable, this ROM should be compatible? (in theory ofc)
Interceptor777 said:
Actually AVB can be disabled, it has to be disabled to boot non-stock ROMs. I have a ZIP which can disable it. All it does is give you a popup after boot about a partition mismatch but the phone works fine.
So you think, in theory, with AVB disable, this ROM should be compatible? (in theory ofc)
Click to expand...
Click to collapse
I never said it can't be disabled
As a slight OT: its not mandatory to fully disable AVB on ROMs that are designed for taimen. taimen ROMs ship vbmeta images, that contain the AVB signatures. Due to the design its necessary to disable AVB for /vendor, which is done in the kernel by removing the AVB mount flag in the dtb. Although we're currently looking into properly generating the vendor avb signatures too.
Nonetheless, flashable GApps are likely going to cross those plans and will require to disable AVB on system. Therefore, I'd be happy if you could share that AVB disabler zip me (or release it to the public) so that @frap129 and me can do some testing with seperate GApps.
Now on to your question. I just spent an hour trying to gather some facts for the following statement:
Treble is not supposed to give you "one ROM for all devices", nor will it ever be able to provide just that.
Trebles requirement is that you can use "stock AOSP" on the device. Yes. HOWEVER: That doesn't mean it has to the be same single AOSP image for every device. Treble still requires configurations on that System image.
The system images VNDK is configured to work with an 8.0 treble vendor. That would mean you need to use an 8.0 vendor on your Pixel too.
The compatibility matrix and the manifest.xml on system specify what HAL treble has to expect/load from /vendor. Those likely differ.
There will always be some small overlay differences, features that one device supports which the other doesn't or configs that differ. Auto-brightness steps would be a good example for that.
It is true, that this ROM works on multiple devices, yes. So far, those are pretty much all very similiar in terms of HALs to load and hardware. There is barely any difference between the View 10, Mate 10, Mate 10 Pro and others. Things that are different are handled in the kernel (like the Display Technology) and don't affect HALs.
TL;DR + My personal opinion: Whereas treble ROMs might boot (assuming you match all those requirements) a "common ROM for all devices" (which I am starting to think is what everyone expects from treble) is not what you want to use, nor what treble has been designed for.
A new build (systemCarbon_20180303.img) has been uploaded.
It includes support for the US Model, and Fingerprint Gestures. To enable them, go to Settings -> CarbonFibers -> Buttons and tick enable navbar. That will disable the navbar and automatically enable the FPC gestures.
Additionally some new features got merged to the codebase. Happy flashing
{
"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 16.0 GSIs I've been making since March 2019.
If you clicked in here, I bet you know what LineageOS is already, but just to fill the blank:
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.
Download:
https://sourceforge.net/projects/andyyan-gsi/files/
Compressed as .xz archives - extract first.
Vanilla except for these changes:
Modifications needed to make it build/boot/feature-complete, see below
Revived navbar layout tuning via sysui_nav_bar tunable
Disabled "vendor mismatch" warning on boot
Signature spoofing support from MicroG (preliminary patch for Android 10)
Default stretch-to-fullscreen (force apps to render in 18:9)
Extra tip:
If you have a relatively low-end device and experience UI stutters, try this simple build.prop trick (technically a debug property, so use at your own risk). Thanks @SnapTheRipper for bringing it up!
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 the scripts/patches, where most things should be self-explanatory: treble_build_los, treble_patches (PHH's treble_patches adjusted for LOS). Not the cleanest code, but should help if you need some clues.
Donate?
https://paypal.me/AndyCGYan
Reserved
Couple of things to note:
Even on a device that runs Pie GSIs nicely, it's still possible to get broken media, camera, RIL or even flat-out no-boot on Android 10 ones. You are strongly advised to try PHH's AOSP first and identify/report issues there, before moving onto other GSIs that are based on his work. Please report bugs here only if it's specific to this GSI.
LineageOS 17.x has lost some features in the process of transitioning to Android 10, e.g. Privacy Guard and built-in SU.
If using Magisk on an A-only device, a modified Magisk is required.
exfat SD cards still don't seem to work. Any help related to this would be appreciated.
The feature "Re-enabled lockscreen shortcuts by default" has been dropped - not that it can't be done, but Google again made ugly changes to the lockscreen, and with the shortcuts turned on it looks asymmetric and adds to the ugliness. Lockscreen shortcuts themselves might still come back with a future upstream update, just like how it did in 16.0.
In the 16.0 GSIs I've included changes that allow for automatic front camera actions for Xiaomi Redmi K20 Pro, but these have to be reworked for Android 10, and I'm not interested in doing so (in fact I prefer manual controls). Consider these changes abandoned for now.
Initial builds are based on PHH v204 and November security patches.
Building-related bits will be published when I have more time to clean them up.
EDIT: Due to some missing bits in LOS, the fix from v204 failed to apply. If you are having camera issue specific to this GSI, refer to this post for a temporary fix. Won't make a separate batch of builds just for this one issue.
Warm welcome. :fingers-crossed:
:good:
:good:
Redmi S2 YSL - 8.1 Oreo custom vendor Arm64
stock camera / open camera. /Gcam X
lock screen / FP X
viper4android. ✓
Thanks for this Rom
is it with or wirhout Gapps ?
Any mirrors?, sourceforge is a mess to download from.
Nice work ?
hasni2005 said:
Thanks for this Rom
is it with or wirhout Gapps ?
Click to expand...
Click to collapse
without
look, it have small size. with gapps rom around twice bigger
Hey OP, thanks for this. Just curious what devices you've tested this on?
MishaalRahman said:
Hey OP, thanks for this. Just curious what devices you've tested this on?
Click to expand...
Click to collapse
See my signature
Thanks great work i have at the moment bugs
The recents not working and the battery indicator and camera is not working
Galaxy J710FN
Using ZTE Axon 7.
None of the camera apps work and fingerprint doesnt work. Other than that seems pretty okay for now.
@AndyYan hello
i tried your fresh Los17 arm64ab build on the Mi A2 Lite
and faced with big issue - camera not works at all
and screen recorder, and torch
tried opencamera too
but it works in the AOSP v204 and Havoc 3.0 GSI
Congrads to OP, arm Aonly build working well in moto g6 xt1925-6. Used magisk phh 19.3 to root. Seems very smooth, no noticeable lag and ambient display is bright and easy to see when phone is picked up. Very nice. Cheers
eremitein said:
@AndyYan hello
i tried your fresh Los17 arm64ab build on the Mi A2 Lite
and faced with big issue - camera not works at all
and screen recorder, and torch
tried opencamera too
but it works in the AOSP v204 and Havoc 3.0 GSI
Click to expand...
Click to collapse
Seems the problem lies here:
Code:
02-04 19:00:13.397 827 827 E vndksupport: Could not load /vendor/lib/hw/camera.msm8953.so from default namespace: dlopen failed: library "libnativeloader.so" not found.
02-04 19:00:13.398 827 827 E HAL : load: module=/vendor/lib/hw/camera.msm8953.so
02-04 19:00:13.398 827 827 E HAL : unknown
02-04 19:00:13.398 827 827 E [email protected]: Could not load camera HAL module: -22 (Invalid argument)
However I'm pretty sure this has been fixed by v204 already, which I did include (it fixed FP on one of my devices). Are you really using the 1117 build? If yes I'll consult PHH about it.
(I reckon you're in the Telegram group as well?)
AndyYan said:
However I'm pretty sure this has been fixed by v204 already, which I did include (it fixed FP on one of my devices). Are you really using the 1117 build? If yes I'll consult PHH about it.
(I reckon you're in the Telegram group as well?)
Click to expand...
Click to collapse
yes, I'm sure it is 1117 build and I used same base for test. right now I'm on Havoc 3 by ExpressLuke and camera works fine
i like high speed of this los build, it's like a rocket:laugh:
please, fix this bug)) I'm in phh group too, and can test quick fixes if need (@eternityson)
eremitein said:
yes, I'm sure it is 1117 build and I used same base for test. right now I'm on Havoc 3 by ExpressLuke and camera works fine
i like high speed of this los build, it's like a rocket:laugh:
please, fix this bug)) I'm in phh group too, and can test quick fixes if need (@eternityson)
Click to expand...
Click to collapse
You're likely right - I just checked the only Oreo vendor device I own and I'm seeing libnativeloader-related errors in log as well. Camera doesn't work on this device even on AOSP v204 so I assumed they were bugging out for the same reason; looks like that's not the case. Good thing I still have at least this Oreo vendor device on hand - this libnativeloader problem (and the corresponding fix in v204) was said to only target Oreo vendors.
I'll do some tests and/or consult PHH - the fix might not be immediate so if you need your phone don't hesitate to switch to other ROMs.
{
"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 17.x GSIs I've been making since November 2019.
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.
Download:
https://sourceforge.net/projects/andyyan-gsi/files/
Compressed as .xz archives - extract first.
Vanilla except for these changes:
Modifications needed to make it build/boot/feature-complete
Revived navbar layout tuning via sysui_nav_bar tunable
Disabled "vendor mismatch" warning on boot
Signature spoofing support from MicroG
Default stretch-to-fullscreen (force apps to render in longer than 16:9)
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 the scripts/patches, where most things should be self-explanatory: lineage_build_unified, lineage_patches_unified (where patches_treble_phh contains PHH's treble_patches adjusted for LOS). Not the cleanest code, but should help if you need some clues.
Donate?
https://paypal.me/AndyCGYan
Reserved
Couple of things to note:
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.
As always, you are strongly advised to try PHH's AOSP first and identify/report issues there, before moving onto other GSIs that are based on his work. Please report bugs here only if it's specific to this GSI.
Thanks to patches from @eremitein , Magisk compatibility is partially restored. For devices that still don't play well with it (e.g. kernel restrictions implemented by OEM), use PHH-SU instead. Install the app and you'll get root for apps.
A-only and VNDKLite targets are now generated from AB images instead of built from source, see sas-creator. Kinda hacky and might be buggy. Move on to an AB device if you can.
To mount /system RW on AB devices, refer to this.
exfat SD cards still don't seem to work. Any help related to this would be appreciated.
Initial builds are based on PHH v300.j and December security patches.
Building-related bits have been published, but only for AB targets - I'm not sure if I want to integrate sas-creator yet.
Dear AndyYan. Thank you very much for all your work on these Roms. Do you think that I can flash the latest BitGapps R19 which was available a few weeks ago on the BitGapps website ?
Great job dude! I ammire you
Relesse 18 thank You my friend
Arm64 avS can't flash the beta versions of GApps and NikGApps, otherwise, constantly restart to TWRP.
Test again, it should be GApps problem, SD821 vndk27 Aonly everything is fine. Thank you.
The ROM bootlooped on Moto E6, though this is a very new ROM so I think I'll revert back to your LOS 17.1 ROM until things are a bit more ironed out.
I think this is the only Android 11 GSI so we all greatly appreciate your work. We're rooting for you
koyo said:
I think this is the only Android 11 GSI so we all greatly appreciate your work. We're rooting for you
Click to expand...
Click to collapse
Hey hey, it's still based on PHH's AOSP R, which has been out there for quite a while, just without an XDA thread. Let's all thank him first
Booted up just fine but no mobile data for me even after trying the IMS settings. Great work and thank you for the release!
Works perfectly on xt1962-1 or moto g7 river using LOS17.1 base
'just a report, tried it on oldies J730G booted fine wifi works, sim works, unable to play medias, reboots by itself about every 10mins or so, very snappy though. Thanks. Off to flashing another one, I'm developing a bad habit, just because I can doesn't mean I should
Edited:
Thanks to Phh for fixing ussd on v300L
Successfully installed the a/b-GSI from 2020-12-19 on Xiaomi MI 10T lite (gauguin) via fastbootd (necessary to handle dynamic partitions!).
Camera quality is awefull (;-) ) but the rest i tested so far looks promissing (WiFi works, Fingerprint works ... well see what make problems ;-) ).
Well done guys!!!
Cheers Kurt
Installed it successfuly on my Honor 9 (A/B). Almost everything works. Except:
- SD-Card don't work (as mentioned)
- Can't flash gapps, because of missing twrp for my device
Saftpresse99 said:
Installed it successfuly on my Honor 9 (A/B). Almost everything works. Except:
- SD-Card don't work (as mentioned)
- Can't flash gapps, because of missing twrp for my device
Click to expand...
Click to collapse
For my gauguin, i used root and Franko-Kernel-Manager to flash NikGapps ... had to mount /system rw manually, but at least it worked.
Cheers
Kurt
Kurt Krummbein said:
For my gauguin, i used root and Franko-Kernel-Manager to flash NikGapps ... had to mount /system rw manually, but at least it worked.
Cheers
Kurt
Click to expand...
Click to collapse
Thanks. I now using phhusson gsi. With gapps.
Perhaps it is easier to mount r/w with a vndklite Version.
Does anybody know, if it possible to switch between this rom and phhusson rom, without loose data?
Saftpresse99 said:
Thanks. I now using phhusson gsi. With gapps.
Perhaps it is easier to mount r/w with a vndklite Version.
Does anybody know, if it possible to switch between this rom and phhusson rom, without loose data?
Click to expand...
Click to collapse
Already tested between caosR and los18, just wipe system, cache and dalvik/art via twrp , flash new system img (+gapps if existed before), and reboot.
AndyYan said:
Background:
This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019.
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.
Download:
https://sourceforge.net/projects/andyyan-gsi/files/
Compressed as .xz archives - extract first.
Vanilla except for these changes:
Modifications needed to make it build/boot/feature-complete
Revived navbar layout tuning via sysui_nav_bar tunable
Disabled "vendor mismatch" warning on boot
Signature spoofing support from MicroG
Default stretch-to-fullscreen (force apps to render in longer than 16:9)
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 the scripts/patches, where most things should be self-explanatory: treble_build_los, treble_patches (PHH's treble_patches adjusted for LOS). Not the cleanest code, but should help if you need some clues.
Donate?
https://paypal.me/AndyCGYan
Click to expand...
Click to collapse
AndyYan said:
Background:
This is a natural continuation/extension of the LineageOS 17.x GSIs I've been making since November 2019.
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.
Download:
https://sourceforge.net/projects/andyyan-gsi/files/
Compressed as .xz archives - extract first.
Vanilla except for these changes:
Modifications needed to make it build/boot/feature-complete
Revived navbar layout tuning via sysui_nav_bar tunable
Disabled "vendor mismatch" warning on boot
Signature spoofing support from MicroG
Default stretch-to-fullscreen (force apps to render in longer than 16:9)
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 the scripts/patches, where most things should be self-explanatory: treble_build_los, treble_patches (PHH's treble_patches adjusted for LOS). Not the cleanest code, but should help if you need some clues.
Donate?
https://paypal.me/AndyCGYan
Click to expand...
Click to collapse
Thanks for your work . Your system working very fast , I share your system https://forum.xda-developers.com/t/gsi-11-lineageos-18-x-gsi-all-archs.4211857/ . Thanks for this system.
Sir ur BvS builds never pass safety net for me not even on A10 ur BvN were flawless....can u help please how to pass...I tried phh/secuize, magisk hide, changing fingerprint to various pixel devices, adding secure file but nothing works
I am on 18.1 rn and using Nokia 8.1 sdm 710
Or can u please just switch back to BvN
{
"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!