Related
Introduction
A spinoff thread from the previously-supported-official thread by Atman.
This thread will contain my unofficial builds for violet. On the 16.0 version, the only real fix (so far...) have been the fingerprint scanner sepolicy denials. I aim to do monthly/bimonthly builds to keep up to date with security patches, as so far I haven't encountered any other issues (let me know).
On the 17.1 version, I have slowly figured out how to make it work, but it is highly experimental.
The 16.0 ROM is stable (I use it as my daily driver).
If you find any bugs, please do take screenshots, give a way for me to replicate it on my device, and send a logcat. If you're super smart, use a logcat and filter for the keyword so I don't have to do even more digging
Please don't tell me to use PE/Mokee commits.
Yet another update. I've got 17.1 builds working without having to resort to cheap tricks and commits (sort of).
Flash instructions
Same as usual:
Reboot to fastboot and flash recovery with fastboot (You have to use the TWRP linked below. Other versions likely won't boot.)
Reboot to recovery TWRP
Wipe to format data, wipe again to wipe system and cache (not necessary if you're updating, only if you're switching ROMs)
Flash firmware (ADB sideload) (this step is dated. The newer builds have a higher target firmware so you should try to flash without the firmware first, then flash the firmware if the ROM doesn't work.)
Flash the ROM (sideload)
Flash GApps, Magisk, etc. as necessary
Done
Downloads (16.0) (STABLE)
Firmware (Dated firwmare)
Recovery (TWRP)
11-Jun-2021 build (with 05-May-2021 security patch), and MD5 Digest
For previous builds see below
Downloads (17.1)
Here's the 17.1 ROM. Here's the md5 hash. It has the March security patch.
It currently does not boot. If you would like to try and help with development, flash the ROM, and then flash the Chinese Q firmware on top of it (this can be downloaded from xiaomifirmwareupdater). Be warned that there is a risk that the newest android keymaster may re-encrypt your device, which in the worst case may require you to format data and/or reflash recovery and/or flash a fastboot MIUI rom. So, it's a bit risky, but likely won't be an issue.
Credits, Sources, etc.
Too many to mention. Atman Shah for getting this device supported earlier last year. ThE_MarD (Marc Bougoin) for other help. Various other names I've seen - Bruno Martins, Weikai Kong, Wang Han... all of the Lineage dev team. I'm sure I'm missing many people who have been involved in the project. I am new, and very much a latecomer to all of this.
Device Tree: https://gitlab.com/mzha/android_device_xiaomi_violet
Kernel Tree: https://gitlab.com/mzha/android_kernel_xiaomi_violet
Other things see my gitlab: https://gitlab.com/mzha
A telegram group to discuss development for 16.0/17.1: t.me/lineageos_violet
Previous builds
07-Nov-2020 (incl. Oct-2020 security patch), with 07-Nov-2020 MD5 Hash
13-Jul-2020 (incl. Jul-2020 security patch), with 13-Jul-2020 MD5 Hash
11-May-2020 (incl. May-2020 security patch), with 11-May-2020 MD5 Hash
Good to see some devs showing interest on this os
will you be adding any customisation? or does it continue as pure lineage os?
e2vinay said:
Good to see some devs showing interest on this os
will you be adding any customisation? or does it continue as pure lineage os?
Click to expand...
Click to collapse
Pure LineageOS. There's more than enough customised ROMs for violet already in my opinion... and I also don't have that much time
hcnulma said:
Pure LineageOS. There's more than enough customised ROMs for violet already in my opinion... and I also don't have that much time
Click to expand...
Click to collapse
That's great
by any chance will you consider adding signature spoofing support? that would be really great. it would help many users go for microG instead of gapps
I completely understand you're starter.
great work. good luck.
Thank you
e2vinay said:
will you consider adding signature spoofing support?
Click to expand...
Click to collapse
No, but there are a few alternatives:
Merge the changes from this RFC and build it
Download the spoofer from https://download.lineage.microg.org/violet/, or get the (ed)Xposed module, or other possibilities...
Will be official Lineage Os?
Can we expect los 17 soon?
himanshu fulmali said:
Can we expect los 17 soon?
Click to expand...
Click to collapse
As per OP: I'm waiting on both Android 10 firmware blobs + kernel to be released by Xiaomi... I'm not sure how the other ROM devs get around this, if it's easy to forward-port or not. But for now, only LOS 16.
Heyyo @hcnulma good to see you got your thread up and going!
As for 17.1? You can work with your current kernel and cherry-pick the fixes that other maintainers of violet are using and same for the device tree and vendor blobs.
As an example, LeEco msm8996 devives are using kernel source code from Marshmallow just rebased on a CAF Q Tag for our kernel since we never got anything newer...
Even once Xiaomi release their kernel source code for Android 10? It would probably take quite a bit of work to shave it down to what you specifically need and then importing it on top of a fresh CAF tag for the kernel or even more work to try and inplement it into uour current kernel.
To get official builds of LOS 16.0 going again for violet you would need to show that you are capable of fixing any major bugs that arise as well.
https://wiki.lineageos.org/submitting_device.html
anywho, hope this information helps bud!
hcnulma said:
As per OP: I'm waiting on both Android 10 firmware blobs + kernel to be released by Xiaomi... I'm not sure how the other ROM devs get around this, if it's easy to forward-port or not. But for now, only LOS 16.
Click to expand...
Click to collapse
I am pretty sure you can use the pixel experience device tree and kernel to compile the ROM just like every other rom
Thank you. If he is stable enough I will use it to build RR PIE
Zjh0094 said:
Thank you. If he is stable enough I will use it to build RR PIE
Click to expand...
Click to collapse
It's definitely stable...
prajwal2001 said:
I am pretty sure you can use the pixel experience device tree and kernel to compile the ROM just like every other rom
Click to expand...
Click to collapse
From what I understand, using their kernel tree will mean I'll have to change a lot of references in my own device tree, and using their device tree on top of that is essentially just building PE, not Lineage.
In any case, I did find the Snapdragon 675 (ie sm6150) kernel trees for Q in several places, https://github.com/sm6150-dev/android_kernel_xiaomi_sm6150 and https://github.com/PixelExperience-Devices/kernel_xiaomi_sm6150. I'll take a closer look into this...
I did find the most recent CAF kernel under sm6150 here, but there seems to be an issue of this not showing up in /quic/la... Something will be resolved. Hopefully.
Request to create group for discussion in Telegram
hcnulma said:
It's definitely stable...
From what I understand, using their kernel tree will mean I'll have to change a lot of references in my own device tree, and using their device tree on top of that is essentially just building PE, not Lineage.
In any case, I did find the Snapdragon 675 (ie sm6150) kernel trees for Q in several places, https://github.com/sm6150-dev/android_kernel_xiaomi_sm6150 and https://github.com/PixelExperience-Devices/kernel_xiaomi_sm6150. I'll take a closer look into this...
I did find the most recent CAF kernel under sm6150 here, but there seems to be an issue of this not showing up in /quic/la... Something will be resolved. Hopefully.
Click to expand...
Click to collapse
you won't have to make any changes in the kernel as far as I know and as for the device tree you just have to make some changes according to the ROM
as every ROM uses the same device tree
and you won't be making pe instead of lineage as the same device tree and kernel are used in every Q ROM except EvoX which uses crimson kernel
hcnulma said:
It's definitely stable...
Click to expand...
Click to collapse
Thanks. I will use it as my benchmark to build RR pie.
---------- Post added 15th February 2020 at 12:03 AM ---------- Previous post was 14th February 2020 at 11:57 PM ----------
hcnulma said:
In any case, I did find the Snapdragon 675 (ie sm6150) kernel trees for Q in several places, https://github.com/sm6150-dev/android_kernel_xiaomi_sm6150 and https://github.com/PixelExperience-Devices/kernel_xiaomi_sm6150. I'll take a closer look into this...
I did find the most recent CAF kernel under sm6150 here, but there seems to be an issue of this not showing up in /quic/la... Something will be resolved. Hopefully.
Click to expand...
Click to collapse
/quick/la/msm-4.14
prajwal2001 said:
you won't have to make any changes in the kernel as far as I know and as for the device tree you just have to make some changes according to the ROM
Click to expand...
Click to collapse
It is precisely the device tree that I'm worried about. From experience, PE has a lot of platform-specific stuff that Lineage doesn't (and the same the other way), and also from trying to figure out the fix to 16.0 I realised there's a lot of context/definition differences between the two device trees. I'd still give it a look, but I suspect it might be easier to just modify the current 16.0 device tree.
RupeshRN said:
Request to create group for discussion in Telegram
Click to expand...
Click to collapse
https://t.me/lineageos_violet.
Zjh0094 said:
/quick/la/msm-4.14
Click to expand...
Click to collapse
Yeah I already figured it was msm-4.14. Have already cloned it but am also considering cherrypicking changes that other devs have done to their kernel trees from 16.0 -> 17.1 as opposed to starting with the CAF kernel. A work in progress.
Sir I'm noob but mokee dev released android 10 and i think mokee and los are pretty same, will he not help you if you contact him?
An update on where I am:
I'm not sure whether to use the PE or Mokee vendor trees. Neither of them have much resemblance to 16.0 tree I have so cherry picking changes will be a nightmare.
The PE vendor tree has a lot of device-tree-specific commits, which will make it a headache to untangle later on. The Mokee vendor tree also has a lot of differing firmware files, though is a bit more similar to the LOS tree.
I'm doing a bit of experimentation to figure out which one will last better in the long run, since I can't seem to get my hands on any MIUI Android Q firmware blobs.
An update on where I am:
I'm not sure whether to use the PE or Mokee vendor trees. Neither of them have much resemblance to 16.0 tree I have so cherry picking changes will be a nightmare.
The PE vendor tree has a lot of device-tree-specific commits, which will make it a headache to untangle later on. The Mokee vendor tree also has a lot of differing firmware files, though is a bit more similar to the LOS tree.
I'm doing a bit of experimentation to figure out which one will last better in the long run, since I can't seem to get my hands on any MIUI Android Q firmware blobs.
Yet another update. I've got 17.1 builds working without having to resort to cheap tricks and commits (sort of).
Here's the 17.1 ROM. Here's the md5 hash. Needless to say, it's very experimental, not stable in the least (expect to get past boot maybe 70% of the time) - I'm getting very mixed results when experimenting myself. Nevertheless, try it out, see what you get. Install it the same way as usual. Keen to get as many eyes on this as possible
Hello guys This is AOSP unlegacy android build.
It is a android version-8 (TESTING) .
Sources-
Source code- https://github.com/Unlegacy-Android/android
device- https://github.com/Unlegacy-Android/android_device_asus_grouper/tree/aosp-8.1
kernel- https://github.com/Unlegacy-Android/android_kernel_nvidia_tegra3
vendor - https://github.com/Unlegacy-Android/proprietary_vendor_nvidia/tree/aosp-8.1
Sorry links might be broken or removed
Issues
no camera
does not function with Gapps
no proper otg support
Thanks
@unlegacy android team
@Ziyan
@aosp
Status-testing
This security patches dupes and is faked
****disclaimer
Im not responsible for any kind of damage to device
If you point your finger at us we'll laugh at you
Guys I have got 2021 security patch level at the first flash and at the second flash I found it 2018. Just comment me your security patches.
Works on tilapia and grouper
download Link https://drive.google.com/file/d/10VaRPsRlJTsnKXLkmOiwpcD9pQP9wZNW/view?usp=sharing
Thank you!
I will use it!
edit:How did you write local_manifests?
Also, did you use the Tegra3 hardware tree?
Hey guys how is this rom
few__ said:
Thank you!
I will use it!
edit:How did you write local_manifests?
Also, did you use the Tegra3 hardware tree?
Click to expand...
Click to collapse
Yup I used the normal repo commands (I don't remember properly as I started compiling it 1.5 year ago)
SORRY for if any wrong sources aye!
Hi
Is ROM better than @ud4's 8.1.0 ROM? I currently have @ud4's and there an issue where some apps (like RedReader, Magisk Manager stable, Play Store, etc...) won't launch; they just show a blank screen. Does this ROM also have that issue?
Thanks
Hi guys,
I want to present my port of M-Kernel, which was originally made by Metallice. This port has exactly the same functionality as the latest release from Metallice (a77), but was ported from Android 5.1 to Android 6.0.
Since this is a testing build only, it is currently provided as zImage only. You have to manually concatenate my kernel with the ramdisk of the ROM of your choice to be able to flash and use my kernel. For concatenating, you can use mkbootimg (click here), which is provided in my Github account.
You can get the source code and the kernel binary from Github (click here).
WARNING!!! This software is provided without any warranty. You use it at your own risk, although it is very unlikely for your device to get damaged due to my kernel.
I hope you enjoy my kernel! Feel free to ask questions about it, but please read the original M-Kernel thread before!
Best regards,
Oebbler
Thank you so much!
Something I didn't have the time or the skills to do!
I created an anykernel script for myself.
here
Hello,
If you are using Omnirom 6.0.1 by daniel_hk, you can flash the attached boot.img either with fastboot or with the TWRP image flasher. This boot.img contains my port of M-Kernel and the ramdisk files for Omnirom 6.0.1.
If you are not using Omnirom 6.0.1, you can try this image as well, but it may not work as expected. Please make sure you have a recent backup before modifying your device!
hey everyone i am new in gsi and i want to know how to build gsi from this files here is the link ! https://ci.android.com/builds/submitted/7168534/aosp_arm64_ab-userdebug/latest
please help & thanks.
You can start with this guide.
Edit - Didn't saw you want to build aosp gsi, I would stick with phhussion script as it contains sources from well known rom and if everything is good may proceed building aosp
Hello
I did Bought a Samsung Galaxy Z flip 3 demo version , i want to build TWRP for it
Spoiler: That is Done
yesterday i downloaded the Kernel source code from Samsung , now i just need TWRP Sources and and Create a Device Tree to built it
if you want TWRP for this phone , just comment down below (for some motivation)
Spoiler: that done too , look for the custom working kernel
Now For a The Custom Kernel
I Manage to Get A Custom Kernel Working with A lot Of Optimisations (Thanks @chrisaw and Others) on a Old OneUI (That System That Came with the Kernel) and it work well (it need some minor touches)
the Kernel Cant Work on Newer OneUI and Custom Roms (Pixel EXperience) because Of new Changes in Vendor Are not Compatible with the Kernel
A guess this Need A lot Of Working (Everytime Samsung do it their Way and Dont Care about The Correct Way)
ScreenShot of the Kernel
Spoiler: That is Done too too
now on Focusing on The Custom Rom , i download LineageOS 19.0 Source Code as i will build for 2 separate phones (Galaxy Z Flip3 'snapdragon 888' and UMIDIGI F1 Play 'Mediatek Helio P60') consecutively
this rom will be based on treble gsi patches but working only on Galaxy Z Flip3
i manage to build LineageOS 19.0 for Galaxy Z Flip3 , i will not share it now cause :
1 - it is not daily driver or usable , you can call it pre-alpha
2 - it has a lot of bugs that i saw , it could be other i didn't
3 - it is a Treble gsi just for testing purposes and does not have gapps (gapps needed to be included in the gsi not like a normal rom)
4 - i fix the fingerprint , now it is usable
5 - don't ask me about rear screen , it is perfectly not working at all (if you close the phone , the main display become black , rear screen have just samsung galaxy logo....)
6 - other things i forgot
Any Help will be appreciated
Stay Tune
Thanks
Yeah I'd like to see a fully functional TWRP
yes!
really appreciated!
I'm in
hells yeah
ok so i reinstall my ubuntu setup cause apt went broken , but now im good to start
my initial work is the device tree , it is still WIP
GitHub - shadowofleaf96/android_device_samsung_b2q: For building TWRP for Samsung Galaxy Z Flip 3 5G
For building TWRP for Samsung Galaxy Z Flip 3 5G . Contribute to shadowofleaf96/android_device_samsung_b2q development by creating an account on GitHub.
github.com
the kernel still not building , im working on it
thanks for waiting
GitHub - StarKissed/starkissed-kernel-b2q
Contribute to StarKissed/starkissed-kernel-b2q development by creating an account on GitHub.
github.com
I never finished it, but this may help with getting the kernel to build.
It's based on the ROG Phone 5 changes required for the isolated source.
[SOURCE] ASUS_I005_1-kernel (MacOS / Linux)
WARNING: This is NOT a custom kernel! GPL requires that source is released for Android kernels. It does not, however, require that the source is tracked. https://www.asus.com/supportonly/ROG%20Phone%205%20(ZS673KS)/HelpDesk_Download/ Each...
forum.xda-developers.com
twistedumbrella said:
GitHub - StarKissed/starkissed-kernel-b2q
Contribute to StarKissed/starkissed-kernel-b2q development by creating an account on GitHub.
github.com
I never finished it, but this may help with getting the kernel to build.
It's based on the ROG Phone 5 changes required for the isolated source.
[SOURCE] ASUS_I005_1-kernel (MacOS / Linux)
WARNING: This is NOT a custom kernel! GPL requires that source is released for Android kernels. It does not, however, require that the source is tracked. https://www.asus.com/supportonly/ROG%20Phone%205%20(ZS673KS)/HelpDesk_Download/ Each...
forum.xda-developers.com
Click to expand...
Click to collapse
thanks
samsung released android 12 kernel so i will merge the changes from your kernel to mine
Shadow Of Leaf said:
thanks
samsung released android 12 kernel so i will merge the changes from your kernel to mine
Click to expand...
Click to collapse
That kernel never booted, so that would probably do more harm than good. It does, however, include the changes to make an inline kernel build outside the source. It was more an example than a template.
twistedumbrella said:
That kernel never booted, so that would probably do more harm than good. It does, however, include the changes to make an inline kernel build outside the source. It was more an example than a template.
Click to expand...
Click to collapse
ok
yes that what i will do , i will use the samsung open source kernel (android 12) , fix to boot recovery and boot the system , when it does that i will include your changes and see if it works or not
Thanks for your contribution。
Cyanide_zh said:
Thanks for your contribution。
Click to expand...
Click to collapse
you welcome
some good news
TWRP is Booted on our Galaxy Z Flip 3 (SM-F711B) but touchscreen is not working
i think i have a problem with firmware , stay tuned
Shadow Of Leaf said:
some good news
TWRP is Booted on our Galaxy Z Flip 3 (SM-F711B) but touchscreen is not working
i think i have a problem with firmware , stay tuned View attachment 5671531
Click to expand...
Click to collapse
can you share the non-touch version?
i hope he can find the problem and fix it
Maroshall said:
can you share the non-touch version?
i hope he can find the problem and fix it
Click to expand...
Click to collapse
i think i fix the touchscreen problem and its working
there is some minor problems i will fix them and upload it here
also the kernel does not boot on oneui , i have to fix it
the work is done (or atleast it works)
you can check it here TWRP Thread
@twistedumbrella i build the kernel it works on twrp but no luck with OneUI (even with knox and other security measurements disabled) it does panic (kernel panic) i need to do some investigation regarding this , if you want to help i will upload my kernel source code soon​
I have the US version, which is why I abandoned the kernel. I had no way to test the changes specific to Samsung, which would be OneUI.
Your best bet would be looking into the changes for an S21 / S22 because they are going to have the Samsung specific changes.
twistedumbrella said:
I have the US version, which is why I abandoned the kernel. I had no way to test the changes specific to Samsung, which would be OneUI.
Your best bet would be looking into the changes for an S21 / S22 because they are going to have the Samsung specific changes.
Click to expand...
Click to collapse
ah ok thanks
for now i fix to kernel panic , now kernel boot in OneUI But after the loading icon the screens went black
so thanks again and sorry for disturbing you
No worries. I would rather you know I don't know, if that makes sense. Sounds like you are more than capable either way.