[How-To] GSI Definitive Guide (ROM+GApps+Bluetooth+GCam+90HZ+V4A)

[How-To] GSI Definitive Guide (ROM+GApps+Bluetooth+GCam+90HZ+V4A) - Realme X2 Pro Guides, News, & Discussion

Hello everybody:
GSI ROMS finally have Fingerprint on display (fod) support, so I decided to try it today.
It was quite difficult to make everything work, since there are a lot of guides in X2 Pro forum and XDA, so I decided to create this thread to make things easier to other users that want to use GSI ROMS.
My device is a Realme X2 Pro Chinese, but this should work on any X2 Pro.
The guides I used as references are these ones:
https://forum.xda-developers.com/realme-x2-pro/how-to/how-to-flash-aosp-android-10-gsi-realme-t4036825
https://forum.xda-developers.com/realme-x2-pro/how-to/how-to-flash-havoc-evolution-gsi-t4040607
https://forum.xda-developers.com/realme-x2-pro/how-to/how-to-flash-aosp-android-10-gsi-realme-t4036825
https://forum.xda-developers.com/project-treble/trebleenabled-device-discussion/guide-fix-bluetooth-audio-a2dp-aptx-gsi-t3950938
And probably other ones I found at internet that I can't remember at this point
1. Pre-requisites
- Unlocked bootloader
- TWRP Installed (I use Orange Fox)
- Color OS Firmware A08+ or A13+ (chinese)
Don't do it being on Realme UI, there are some features that won't work with the new firmware/vendor, FP included (Ironically, bluetooth gets fixed).
- Any software that can uncompress .xz files (most of GSI comes in this format)
2. Choosing your ROM
The first step is to find any rom that you like, it must has these features:
- It has to be based on phh's AOSP v214 or newer.
- It must be A/B ARM64.
You can look for one here:
https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-%28GSI%29-list
{
"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 would suggest to pick phh's AOSP ROM or LOSQ Project which is really close to phh's source.
https://github.com/phhusson/treble_experimentations/releases
https://github.com/eremitein/treble-patches/wiki/LOSQ-Project
Bugs as of March 03, 2020
At this time, every phh's based rom has the following bugs:
- In-call bluetooth
- Bluetooth media playback (can be solved)
- Auto brightness
- Securize (I tried to use it but never done anything)
And there may be more bugs included on the rom you're using (lineage, havoc, evo, losq, posp, etc)
3. GApps (Optional)
Note: many roms has 2 variants, one with GApps included and one vanilla, depending on the one you choose, you'll have to do this step.
If you need Google Services and the ROM you downloaded does not include them, you need to pick a Gapps package.
Personally, I like BitGapps, but you can choose any you like as long as they are made for ARM64 Android 10.
BitGApps
FlameGApps
OpenGApps
4. Bluetooth fix
Before flashing the ROM, you have to delete the file BluetoothResCommon.apk from your vendor. You may want make a copy of it.
For this, you can do this action in the following ways:
- using a file explorer
Search in the root (/) the path /vendor/overlay
Search the file BluetoothResCommon.apk
Make a backup of the file
Delete the file
- adb and root
Connect your phone to your PC and run these commands from terminal or cmd:
adb pull /vendor/overlay/BluetoothResCommon.apk
adb shell
su
rm /vendor/overlay/BluetoothResCommon.apk
- adb and twrp
Enter in recovery mode
Mount vendor partition
Connect your phone to your PC and run these commands from terminal or cmd:
adb pull /vendor/overlay/BluetoothResCommon.apk
adb shell
rm /vendor/overlay/BluetoothResCommon.apk
This section is based from this guide. Only the first step is needed, X2 Pro build.prop has already some working configurations.
5. Flashing ROM and Gapps
- Download the ROM file (if you haven't)
- If ROM it's compressed (xz), then uncompress the file and copy the rom_name.img file to your phone
- Copy GApps to your phone (optional)
- Enter in TWRP
- Choose the file rom_name.img
- Flash it as "System image"
- If you're flashing GApps, follow this steps:
- Go to Partitions
- Select system
- Resize partition
- Flash GApps package
If this steps shows you errors, you can reboot to recovery and try again- Format data
- Reboot system
Note: according to many guides and people, certain roms like havoc won't boot if you don't set your selinux to permissive.
I tried havoc some weeks ago and I didn't needed to do that, but in case the rom you picked doesn't boot, flash Permissiver_v5 from this thread:
https://forum.xda-developers.com/realme-x2-pro/how-to/how-to-flash-havoc-evolution-gsi-t4040607
6. Magisk
As of March 15, 2020, phh's Magisk works, yes, but it has the following issues:
- App installation becomes slower
- Internal storage becomes read and append only, you can't modify files or delete them.
For those reasons I do not recommend to install it at this moment. Whenever it gets fixed, I'll update the guide with the proper links.
7. First steps in your new ROM (including 90hz)
Now that your rom has booted (I think), there are some basic configs that you may want to do:
- Get LTE working:
In my case, by default the ROM were locked on WCDMA, which is 3G+ in my operator, follow this steps to change it
- Go to Settings
- Open Network & internet
- Select Mobile network
- Look for Preferred network type
- Choose the one that works better for you. I selected global.
- Enable device features:
By default, some of our device features come disabled, lets change it
- Go to Settings
- Open Phh Treble Settings
- Open Oppo features
- Select Enable DT2W
- Select Enable Game Mode
- Select Enable USB OTG- Open Misc features
- Select Expose Aux cameras
- Select Force Enable Camera2API HAL
- Enable 90HZ!
And finally, for enabling 90HZ:
- Go to Settings
- Open Phh Treble Settings
- Open Misc features
- Select Force FPS
- Choose 90.0 (or 60.0 if you don't want it)
- Nice
8. Google Camera (GCam)
Get a funcional GCam was really hard, I tried several versions like Urnyx, Tiger, BSG and Arnova. They didn't work, whenever I made a picture or video the app closed, even loading the config.xml
After a lot of effort, I found one that is working pretty well, including features like night mode! It's a very specific version, GCam_5beta6.200105.0445build-7.2.018.apk others didn't work
Just download and install it:
https://www.celsoazevedo.com/files/android/google-camera/f/changelog955/
Note: You probably will need to download Google Photos app, I already use it, so it worked from the first run.
9. Viper4Android (V4A)
And last but not least, for people that uses V4A, these are the steps to making it work without Magisk.
1. You will have to set your selinux to permissive, if you haven't, flash Permissiver_v5
2. Go to this site https://zackptg5.com/android.php#viper and download Rootless Driver Installer
3. Flash the file
4. Reboot and install Viper4Android 2.7.0.1 or newer
5. Profit!
There are some screenshots at the attachments
Many thanks to all the devs, contributors and XDA Users that made possible to have AOSP GSI in X2 Pro, some of them:
@phhusson @natedogg20050 @ospeto @SrCDA @Jerry08 @mauronofrio

Auto brightness and aptx hd also not working out of the box . But aptx hd can be enable with a magisk module. Thanks for this guide.

is volte working?

@EdgardoSchiffer Good stuff, did you use a specific config for the Gcam?
Also you could add Youtube Vanced to your guide I've found that the non-root works best https://vanced.app/

Does Google Pay work? How to get root access like magisk stable?

onlyoneaamir said:
is volte working?
Click to expand...
Click to collapse
Can't tell, no VoLTE in my country
exadeci said:
@EdgardoSchiffer Good stuff, did you use a specific config for the Gcam?
Also you could add Youtube Vanced to your guide I've found that the non-root works best https://vanced.app/
Click to expand...
Click to collapse
I ran GCam with stock config, It does a great Job
Aj.GaLaxY aCE said:
Does Google Pay work? How to get root access like magisk stable?
Click to expand...
Click to collapse
GPay probably not, by default even Netflix does not appear on Play Store
You can get root with Magisk, but you will have the bugs I wrote on thread. I don't know if there is any other root method

I just use latest magisk from official website and have no bugs like you mentioned. I am on phh latest gsi.

ospeto said:
I just use latest magisk from official website and have no bugs like you mentioned. I am on phh latest gsi.
Click to expand...
Click to collapse
There is a root, but system files cannot be changed or deleted, check for yourself through the file manager

Ah yes, it become read only file system. But magisk modules working OK right? We can use twrp for deleting or modifying system file.

This is cool, though LOSQ tends to freeze and reboot from time to time. It's happened to me 4-6 times since yesterday.

How to go to stock. Do we need any Bluetooth fix?

Aj.GaLaxY aCE said:
How to go to stock. Do we need any Bluetooth fix?
Click to expand...
Click to collapse
Flash stock ozip from recovery, you don't need any fix since the it will override the changes you've done in vendor

EdgardoSchiffer said:
Flash stock ozip from recovery, you don't need any fix since the it will override the changes you've done in vendor
Click to expand...
Click to collapse
U need to flash vbmeta.img if it stuck at bootlogo.

Don't forget that all those ROMs that we can use on our phones are because of one guy and he just added fingerprint reading on Realme phones a few days ago, so go and Sponsor him on Github!
https://github.com/sponsors/phhusson
I just did and for a year Github matches the donation:
To supercharge community funding, GitHub created the GitHub Sponsors Matching Fund, which matches up to $5000 USD total per sponsored developer in their first year, or 12 months, of sponsorship.
Click to expand...
Click to collapse

exadeci said:
Don't forget that all those ROMs that we can use on our phones are because of one guy and he just added fingerprint reading on Realme phones a few days ago, so go and Sponsor him on Github!
https://github.com/sponsors/phhusson
I just did and for a year Github matches the donation:
Click to expand...
Click to collapse
Wonderful suggestion, just did the same

Great work guys!!!
ist it possible to fix the Bluetooh Audio issue (Headphones are connected, but music is played with the speakers of the phone) after installation of the ROM?
Furthermore, left swipe does not show the Google Discover feed and 'o.k. Google' doesn't respond to my voice.

runner2003 said:
Great work guys!!!
ist it possible to fix the Bluetooh Audio issue (Headphones are connected, but music is played with the speakers of the phone) after installation of the ROM?
Furthermore, left swipe does not show the Google Discover feed and 'o.k. Google' doesn't respond to my voice.
Click to expand...
Click to collapse
Read the guide, mount Vendor in TWRP or OrangeFox and you'll be able to find it in the file manager in the recovery.
Can't help with the last part though.

Thanks, that works
Anyone else, who has an idea why 'O.K. Google' isn't working? It's not possible to set it up in the Google App.

For me, Bluetooth for media audio didn't work. I've remove Bluetoothres.apk before flashing. How to do? Flash last version 215, is it value to do?

Many thanks for the great effort, OP.
I haven't had any luck in installing any GSI on my Gloabl X2 Pro and I have been trying for a week now. I noticed every thread has different method, which got me very confused. I would like to thank you for stating the system Pre-requisites, not many HOW-TO guides state the firmware requirement.
Before i ask my question, i didn't have any luck with your method either. The question is, in the reference links you provided, they talk about vbmeta and pushing fstab.qcom, but you didn't mention anything about them in the steps. Am i missing something?
i just want to install a GSI, i don't care about any fix. I just want a GSI to boot because after SUCCESSFULLY installing the image then wiping data, i get into a bootloop. So my priority is just getting a GSI to boot.
I am on RMX1931EX_11_A.10
I appreciate anyone's input into solving my issue

Related

[ROM][Share][Unofficial][LVM] CM 14.1 for Oppo Find 5 by Wuxianlin

Downloading. Thank you.

So, i flashed the rom. Been using this for a day already.
Difficulties I faced:
1. Losing signal oftenly and sim car lock-out's (propably something wrong with my phone, or maybe it is software thing. If anyone know how to fix this, please don't be shy )
2. Random reboots.
3. Freezes when taking photos using instagram.
I'm not using LVM either.

Thanks for linking to this ROM !
My Find5 has been on jejecule's crDroid (Android 6.0.1) with LVM enabled sofar.
I was not expecting an Android 7 build anymore since few developers/builders use this phone.
So I tried a dirty flash from crDroid to this ROM (no harm trying, can always do a clean flash later) and lo-and-behold that worked out fine !
I have just been testing to see what works, I found no show-stoppers yet.
Thanks !

Hotspot Portable Error
I Turn On but Problem...no connect in PC and all device
please fix

Great rom
I have ,no problems at all!

Build from 17-12 dramatically improved stability for me. No more random reboots since then. I'm not experiencing any major issues myself using LVM. Can confirm hotspot doesn't work, not an issue for me though. New daily ROM
Verstuurd vanaf mijn Find 5 met Tapatalk

i've installed latest cm 14.1 on my oppo find 5 and everything is working really fine except the microphone.
mic only works in telephone app so that phone calls are possible but it doesn't work in any
other app like voice record, google search, chrome, ...
i've already tested different language settings and permission settings but without success...
...any ideas?

Thnks for ROM, I install 17.12 rom with LVM and I want ro report some problems:
1. Microphone does not work in apps, only in phone
2. File manager can't modify files in root (hosts for example). I switch on root acess for apps in developer options and in FileManager settiongs. May be I need to do somthing else?
3. Live display (switching color temperature and manual adjusting of colors) does not work.
4. USB tethering and portable hotspot does not work too.

Andre-2 said:
Thnks for ROM, I install 17.12 rom with LVM and I want ro report some problems:
1. Microphone does not work in apps, only in phone
2. File manager can't modify files in root (hosts for example). I switch on root acess for apps in developer options and in FileManager settiongs. May be I need to do somthing else?
3. Live display (switching color temperature and manual adjusting of colors) does not work.
4. USB tethering and portable hotspot does not work too.
Click to expand...
Click to collapse
Looks like Wuxianlin has released a new build ('lineage-14.1-20161230-UNOFFICIAL-find5.zip'). :good:
Anyone tried this yet to confirm if the problems Andre has noted have been resolved? (Hopefully it's not simply a CM to Linage rebrand release.)

Mateus109 said:
Looks like Wuxianlin has released a new build ('lineage-14.1-20161230-UNOFFICIAL-find5.zip'). :good:
Anyone tried this yet to confirm if the problems Andre has noted have been resolved? (Hopefully it's not simply a CM to Linage rebrand release.)
Click to expand...
Click to collapse
Installed the 1230 build. It's mostly a rebrand. Most CM strings haven't even been removed yet lol.
Andre-2 said:
Thnks for ROM, I install 17.12 rom with LVM and I want ro report some problems:
1. Microphone does not work in apps, only in phone
2. File manager can't modify files in root (hosts for example). I switch on root acess for apps in developer options and in FileManager settiongs. May be I need to do somthing else?
3. Live display (switching color temperature and manual adjusting of colors) does not work.
4. USB tethering and portable hotspot does not work too.
Click to expand...
Click to collapse
1. Microfone does not seem to work in apps (tried build in sound recorder)
2. I use other apps and root works for me.
3. Works
4. Does not work

Mateus109 said:
Looks like Wuxianlin has released a new build ('lineage-14.1-20161230-UNOFFICIAL-find5.zip'). :good:
Anyone tried this yet to confirm if the problems Andre has noted have been resolved? (Hopefully it's not simply a CM to Linage rebrand release.)
Click to expand...
Click to collapse
I've installed 1230 ROM today.
File manager works in root,
LiveDisplay works,
portable hot spot works, but USB tethering dos not work unfourtunately.
microphone dos not work in apps, but it is not so big problem for me.

Andre-2 said:
I've installed 1230 ROM today.
File manager works in root,
LiveDisplay works,
portable hot spot works, but USB tethering dos not work unfourtunately.
microphone dos not work in apps, but it is not so big problem for me.
Click to expand...
Click to collapse
I'm so sorry, my frends, portable hotspot does not work in 1230 ROM.

Wuxianlin's released another update!

Mateus109 said:
Wuxianlin's released another update!
Click to expand...
Click to collapse
no significant changes as I can see. portable hotspot, usb tethering and microphone (in apps, sound recorder was tested) are not working.
Screens with some initial adjustments, wich are visible just after instalation, were changed from cyanogenmod old ones to new lineage.

help......
i can't turn on my wifi, can any one help me plz. i don't know what i have to do with this problems !!

hauhuyhoang said:
i can't turn on my wifi, can any one help me plz. i don't know what i have to do with this problems !!
Click to expand...
Click to collapse
I have the same problem, anyone please help us

Dear members,
I am using the January 26 2017 (1250) build and experience 'random' reboots. Mostly when I use the camera. To get Nougat running again most of the times I have to start TWRP en choose reboot system. I really hope this gets fixed.

vpn does not work
VPN does not work.

So guys, i get my Find 5 back to life. Which rom do you prefer this or [Nougat 7.1.2 Alpha] [LVM] AOKP Unofficial - 22nd May, 2017 - LVM. With one of them I had the last time problems, but do not know with what ...

NitrogenOS Megathread

{
"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"
}
Welcome to the NitrogenOS Q&A Megathread. Here you can find answers for the most popular problems and questions about NitrogenOS. I started this thread, so that new users don't repeatedly ask the same questions multiple times. While I am fairly new to coding in Java, I can definitely say I know a lot about Android phones and NitrogenOS, but you'll have to trust me on that. If you need any more help, you can even PM me and I'll try to reply as soon as I can.
You can find the original NitrogenOS thread here.
ROM info
Developer: xyyx
Latest Android version: 8.1 Oreo
NOS Download (latest): https://sourceforge.net/projects/nitrogen-project/files/kenzo/kenzo_test/8.1/
Bugs and updates
- A (very) small amount of users reported Google Dialer not working properly while installed through OpenGapps or the Play Store, you can still use stock dialer
1. Test or stable?!?!
Test in this case doesn't mean less stable. xyyx named the two versions a little confusingly.
Test means Oreo (Android 8.0 and 8.1) and Stable means Nougat (Android 7.1.2).
So let's make this a little less confusing:
Oreo (8.0) builds -> Download from here
Oreo (8.1) builds -> Download from here
Nougat (7.1.2) builds -> Download from here
2. Youtube PiP (Picture in Picture mode)
Google has patched PiP a long time ago, so it doesn't work with the latest Youtube releases. The last official release working with PiP is 12.34.55, which you can download from ApkMirror.
My preferred option however is iYTBP (injected YouTube Background Playback), a modified version of Youtube, but it gets a little confusing as there are multiple options.
You can download it from this thread.
Now the tricky part - choosing the right version. I always prefer the Vanced version, which can be found in the 2nd post. Again you have multiple options, but I will not go through all of them since they are explained pretty good in the post itself. While iYTBP enables PiP, it also blocks ads and adds a lot of useful settings and new updates come very frequently. There are multiple installation methods, but I prefer the Magisk one, since it offers options like detaching the Youtube app from Play Store. What this means is, that you don't have to disable auto-updates and it will not bug you to constantly update it.
You can try these methods:
Magisk Module (Easiest):
1. Open Magisk Manager
2. Go to Downloads
3. In the search bar type "Youtube", you should see two results
4. Choose either the normal or the black theme (I personally prefer the black one)
5. Press the download arrow and then "Install"
6. Wait for a while (it's a big package to download and unpack)
7. Reboot
This is by far the easiest option and the module is updated fairly often.
Manual:
1. Delete or uninstall any previous release of Youtube. If you installed it as a system app, disable it or delete the /system/app/YouTube folder. If you had to delete the folder, reboot.
2. Download the Youtube apk
3. Make a folder called YouTube (watch the caps!)
4. Move the apk to this folder and rename it as YouTube (again with the caps)
5. Copy/move the folder to /system/app (The directory should look like this: /system/app/YouTube/YouTube.apk)
6. Reboot
Magisk (manual):
1. Download the Youtube apk, the iYTBP universal installer and the use_this_settings.sh file. Check that they are in the downloads folder.
2. Edit the use_this_settings.sh file if you want. Since we're installing from Magisk, you'll need to set MAGINSTALL to YES (MAGINSTALL="YES"). I usually also enable detach (DETACH="YES"). This will make the Play Store think Youtube isn't installed and it will not bug you for updates.
3. Open Magisk Manager, go to Modules and press the + button. Now select the universal installer zip and flash it in Magisk.
4. Reboot
Recovery method:
Same as for Magisk, but MAGINSTALL is set to NO (MAGINSTALL="NO"). In case you didn't read the Magisk method, here is the recovery method...
1. Download the Youtube apk, the iYTBP universal installer and the use_this_settings.sh file. Check that they are in the downloads folder.
2. Edit the use_this_settings.sh file if you want. I usually enable detach (DETACH="YES"). This will make the Play Store think Youtube isn't installed and it will not bug you for updates.
3. Reboot to recovery, go to Install and choose the universal installer zip, flash it.
4. Reboot
If you open a video in fullscreen mode and press the home button, it should open it in PiP mode. If you want to change some advanced settings, you can go to your Account (the round icon with your profile picture) -> Settings -> iYTBP Settings
3. Goodix & FPC - What are they
Goodix and FPC are two different types of fingerprint sensors (or rather sensor manufacturers). They both work in Android 8.1 builds. Custom kernels or mods may break the fingerprint sensor functionality.
4. Rooting
tl;dr: rooting NitrogenOS is the same as rooting any other custom rom, just flash Magisk, SuperSU, phh's superuser or anything else.
Now for the extended version.
Magisk:
Magisk is a great open-source root manager, developed by topjohnwu. It features a feature rich app, but most people prefer it because of it's "modules", packages which can do a bunch of things, from installing apps like Viper4AndroidFX or Dolby Atmos, to modifying system settings, like the volume steps increase. Magisk also features an option called "Magisk Hide", which can bypass Android's SafetyNet.
Check out the Magisk thread.
You can directly download the latest version of Magisk from https://tiny.cc/latestmagisk
SuperSU:
SuperSU is an alternative root manager. It used to be developed by Chainfire, but has recently been purchased by another company. I still prefer Magisk, but SuperSU is a great alternative for new users. My problem with it though is, that it is not open-source and the new buyer is pretty secretive so I don't really trust them.
Check out the SuperSU website for the download link.
phh's SuperUser:
Another open-source root manager, but the great thing about this one is, that it's very minimalistic and very small in size.
Check out the SuperUser thread and phh's Build Bot.
5. Google Apps (gapps)
Google apps are a vital part of custom roms. You might not know this, but AOSP and CM based roms are made from Google source code. Google actually makes Android open-source, but the Play Store and other Google apps are not. That's why roms like NitrogenOS do not come with the Play Store preinstalled. That is where Open Gapps come in. They are prepackaged apps, updated almost daily. They come in various sizes and versions, but they can all be flashed in TWRP like a normal zip file.
Platform: arm/arm64/x86/x86_64 - RN3 has an arm64 processor (Think of it as a 64-bit CPU for phones)
Android: 8.0/7.1/7.0... - This is the android version, NOS is Oreo based so choose 8.0 (Or 7.1 for Nougat) [Check below for OpenGapps 8.1]
Variant: This is where it gets complicated. There are a LOT of versions to choose from. For more in-depth resources check the OpenGapps' package comparison.
But OpenGapps are a lot more customisable, to the level where you can choose individual apps you want installed. The easiest way to do this, is to flash the Aroma package, which enables you to choose exactly which packages you want installed. Another option is to configure any of the selected packages using a gapps-config.txt file. You can learn more about that in the Advanced Features and Options section.
You can download daily builds for any Android version from https://opengapps.org/
6. TWRP (Recovery)
A recovery is a partition, used to flash files like ROMs, gapps and any other modifications. You do (in most cases) need an unlocked bootloader to use it. Unlocking your bootloader will not be described on this thread, as there are a lot of resources for our device.
Official TWRP - This is the official TWRP (Team Win Recovery Project) for our device
You can find the latest updates for TWRP on their website.
Red Wolf - This is a modified version of TWRP, my absolute favourite because of it's custom features.
Flashing TWRP:
If you don't have a custom recovery installed and you have unlocked your bootloader, then download the latest version of your preferred recovery and follow these steps:
1. Download Minimal ADB and Fastboot on Windows, or use sudo apt install android-tools-adb android-tools-fastboot if you're on Linux.
2. Enable USB Debugging (Settings -> About phone -> Press "Build number" 7 times to enable Developer options). You should find the Developer options in settings above "About Device". Find USB Debugging and enable it.
3. Connect your PC to the phone via a cable. Open Minimal ADB and Fastboot (which will open CMD) or Terminal on Linux and type this (same for both OSs): adb devices. Select "Always allow on this computer" and confirm access on your phone.
4. Reboot your phone to fastboot/bootloader (By holding Power and Vol-, releasing the power button after a vibration and holding the Vol- button until you see the Xiaomi mascot).
5. Type (In CMD/Terminal): fastboot devices, to confirm if the phone has been recognised, then fastboot flash recovery /path/to/recovery.img
6. After it has succesfully finished, remove the cable and reboot directly to recovery (Power and Vol+, release power after vibration, but keep holding the Vol+ button until you see the TWRP or RedWolf logo).
If you do already have a custom recovery installed and just want to update it, flash the .img or .zip file in your already installed recovery and select "Reboot to recovery".
7. NOS asks me for a password after flashing?!!?!?
This is actually not NitrogenOS's fault, it's a byproduct of your previous rom, most often MIUI. What this means is, that your internal storage is encrypted and the only way to fix this, is to backup everything on your internal storage, which you can do by connecting your phone to your pc while in recovery. You should be able to access the phone's storage and move the files from there. If you for some reason can't do that, you can still put in an sdcard and copy the files to it in TWRP. Bottom line, backup the files and then go to "Wipe" and find the "Format data" button. You might see a "wipe data" button, but this is not the same. When you "wipe data" you are wiping your system, cache, dalvik cache and data partitions, but formatting data will format your internal partition as well and thus remove the encryption.
You can finally reflash NOS and gapps or whatever other modification you want.
8. Firmwares
Check out this link to download the latest firmware for our device.
What is firmware? - It's what connects hardware to software (don't confuse it with a kernel). It's what, for example, makes the camera work.
Do I really need firmware - Yes (but it's already installed, even after completely wiping the stock rom, since it's on separate partitions).
Do I need the most up-to-date firmware - Actually no, the only difference you will notice is in the signal and WiFi strength. If yours are good enough, you don't need to update, otherwise feel free to download the newest version from the link above.
What is emmc_appsboot.mbn? - It's a bootloader update. Bootloader or fastboot is the partition in which you have unlocked your bootloader and flashed the recovery. If you have officially unlocked your bootloader, then you can flash firmware with emmc_appsboot.mbn, but if you have unofficially unlocked your bootloader, do not flash these files as they will re-lock it. But you can still flash the version without emmc_appsboot.mbn.
Kenzo? Kate? - Kate devices are the same as kenzo ones but are a little bigger.
Some comparisons:
Kenzo
Size: 150 * 76 * 6.85 mm
Weight: 164g
Kate
Size: 152 * 76 * 6.85 mm
Weight: 167g
Model numbers:
Kenzo: 2015116
Kate: 2015161
Kate devices are 32/3 GB, and some kenzo devices are as well (some are 16/2 GB), not really sure about this part.
Global stable or developer? - Most people use developer roms, but again, this is not the actual ROM, just the firmware extracted from the rom, it doesn't really matter which one you choose.
When do I need to flash firmware? - If you're coming from MIUI8 (or 9), then you probably have the newest firmware. In this case you don't need to flash it, because MIUI roms already have firmware included in the update. If you're coming from a CM or AOSP based rom you also probably don't have to flash it, but I suggest you update it just in case. If your signal is good enough though, there really is no need.
9. How to flash the rom
Flashing is pretty straight forward. Just go to the Install section of TWRP and flash it like any normal zip, nothing special.
If you're coming from MIUI, then the full procedure is this:
1. Unlock your bootloader (google it, useless explaining it here)
2. Flash TWRP
3. Make a full device backup (Nandroid backup)
4. Copy or move all important files from the internal storage to an sdcard or your pc
5. Format data, or in other words, wipe EVERYTHING (excluding external storage) - This will delete all your photos and anything else in internal storage
6. Flash the latest NOS "test" build (Oreo)
7. Flash gapps (I recommend opengapps.org, check above)
8. Reboot to system
10. OTA?
What is OTA? - OTA means Over The Air (Update)
Does NOS have OTA? - Actually yes and no, newer updates (from March 2018 on) do have partial OTA (it does check for updates and notify you, while also giving a direct download link to SourceForge, but you will have to manually flash every update in your recovery.
What about incremental updates? - Sorry, but no. You'll have to download full packages every time. If you have a bandwidth cap then just download an update every week or two, you can check the changelog to see if you think it's worth updating to.
11. Google Camera
If you're having problems with the official Google Camera or just want some added features then look no further than modded camera apps. Check out this thread by emime12, it's very frequently updated and features a lot of different camera mods, including Google Camera, MIUI Camera, MOTO Camera and many more.
Recommended settings:
3x3 Grid - For better photos
I usually disable "Save location" and "Camera sounds"
Model: Pixel XL (corr) - default
Config camera HDR+: NEXUS 6
HDR+ parameters: Default
Panorama resolution: High
Advanced: Enable both
Experimental: I usually leave this disabled but it's your choice.
Back camera video resolution: UHD 4K (30 fps)
In case your camera doesn't work check if you have these two files and delete them:
/System/framework/com.google.android.camera.experimental2016.jar
and
/System/etc/permissions/com.google.android.camera.experimental2016.xml
Credits go to: @emime12 and Njaiker.
You can find more info about problems and updates on emime12's thread.
Settings may differ a lot, so check emime12's recommended or just test until you find ones that work for you
12. RAM Management - Low free RAM
Android's RAM (Read Only Memory) management doesn't work like Windows'. Android manages RAM very well, "Free RAM is wasted RAM" is a very common expression on XDA. Android loads the first couple of apps into the RAM and priorities the open one. More used ram means more apps loaded in ram which means faster load times. Don't worry about it too much and just enjoy the fast loading speeds.
13. VoLTE?
VoLTE should work on Android 8.1. Magisk, Viper or any other mods may break it.
14. Custom kernels
While there are a lot of custom kernels, I suggest you stick with the stock one, as it is made specifically for NOS and thus it is the most stable. If you still want a custom kernel, you can try Radon or Agni but they might break VoLTE or your fingerprint sensor.
Agni XDA Thread - By psndna88
Radon XDA Thread - By Umang96
15. Daily driver or not?
Yes, NitrogenOS Oreo is very stable, definitely enough for a daily driver. It is the best Oreo rom for our device (in my opinion), as it offers just the right amount of customization and stability.
15. GPS
Some users have reported low accuracy, but you should be fine if you turn on High Accuracy mode and/or install Faster GPS.
Update: In recent updates GPS shouldn't be a problem anymore as xyyx has fixed it, but some users have still reported low accuracy.
16. Viper4Android FX
(There may be other ways, but I haven't tested them yet so I can't confirm if they work) By far the easiest way to install Viper4Android FX is using Magisk. There is Magisk module called ViPER4Android FX Materialized. Download and install that module from the Magisk repo, choose your preferred installation option (By pressing Vol+ or Vol- to select which version you want installed and if you want it materialized - for newest materialized version press Vol+ 2 times) and finally reboot. Try playing some music and open the Viper app. Turn on the "Master Power" switch and the "Playback Gain Control" (the easiest way to tell if it worked). If after a little time the volume increases, it means that Viper4Android FX works. If not, press the three dots and choose "Exit" (without turning off the master power or gain control). Now open the app again and it should work. You can also check that in the side menu under "Driver status", if it's enabled and processing, then everything works.
You may or may not have to exit and re-enter the app after reboot to enable processing (in my case I had to).
I would show you my recommended settings (as requested), but to be honest I only use:
Headset
Viper Bass (Natural bass, 40 HZ frequency, 8 dB)
Viper Clarity (Natural, 6 dB)
Sometimes I use Field surround with default settings
Phone speakers
eXtra loud (Slight, 4x max gain, -1.9 dB max output)
Bluetooth device
Playback gain control (Moderate, 6x max gain, -1.9 dB max output)
If I'm at a party with my bluetooth speaker I pump it up to Extreme and 8x max gain
Viper Bass (Natural, 40 HZ frequency, 8 dB), 17 dB for parties
Viper Clarity (Natural, 3.5 dB)
I don't use equalizers or if I do, they are song-specific. I also don't USB/Dock, so I can't recommend anything there.
Of course these settings can vary depending on the song, so choose those, which you like the most and don't stick with just those I chose, try all the functions to see which you prefer.
17. AdAway (Root)
AdAway is a great open-source root ad blocker, which can automatically download and update sources and works by adding those to the hosts file. It work well on the internet, but also inside apps (most of the time).
Check out the official AdAway website. You can also download it from F-Droid.
Adaway v3.2 (60) (direct download link)
Adding custom host sources:
Go to "Host sources" and add your own sources or check out these: AdAway's host sources
Be careful when adding all of them, since some can block legitimate links like goo.gl.
AdAway also offers an option to scan for Adware, which can be found under "Scan for adware". This will bring up a new window, press "Start scanning". If you don't need/want the mentioned apps you can uninstall them, but AdAway can't block their ads.
You can also check out my recommended settings:

wow,really appreciated that sir., it is very helpful specially for those who wanted to try, flashing rom or any mods on their device like me. thanks and keep up the good work sir God bless!

i think i can add up little bit here.
1) u r on miui & u want to flash nitrogen so u go to recovery and backup ur current rom in case if u dont like nitrogen u can restore back to miui with all ur setting & app. now assume u r on nitrogen, after 4-5 days u dont like nitroge & u decided to come back to miui, so u go to recovery and restore yr backup that u have taken earlier. after success booting the screen with pin or password will appear. so u would enter/guess any previous password, pin u used earlier but it will not open. here the real problem come. i have also faced same issue & got upset searching endless solution on google . u will get mad on u. security bypass will also not work. after spending endless hour i come with solution. download aroma zip search on net. flash it through recovery this will help u to get in system its ike file manager. then head to data, system and delete all file u see below
locksettings.db, locksettings.db-shm, locksettings.db-wal, gatekeeper.password.key, gatekeeper.pattern.key
and then restart, yr problem would be solve.
2) nitrogen os does not support video calling via jio. none custom rom other then then miui support.
3)xposed is not available for oreo.
4)i have used nitrogen oreo for about 2 weeks it is stable but not as miui. some time r net would not work, jio call drop, lagging u have to restart on every time u faced problem. i suggest that wait for some time to roll out nought port for kenzo with zero bug & this will happen soon.

saifuk said:
i think i can add up little bit here.
1) u r on miui & u want to flash nitrogen so u go to recovery and backup ur current rom in case if u dont like nitrogen u can restore back to miui with all ur setting & app. now assume u r on nitrogen, after 4-5 days u dont like nitroge & u decided to come back to miui, so u go to recovery and restore yr backup that u have taken earlier. after success booting the screen with pin or password will appear. so u would enter/guess any previous password, pin u used earlier but it will not open. here the real problem come. i have also faced same issue & got upset searching endless solution on google . u will get mad on u. security bypass will also not work. after spending endless hour i come with solution. download aroma zip search on net. flash it through recovery this will help u to get in system its ike file manager. then head to data, system and delete all file u see below
locksettings.db, locksettings.db-shm, locksettings.db-wal, gatekeeper.password.key, gatekeeper.pattern.key
and then restart, yr problem would be solve.
2) nitrogen os does not support video calling via jio. none custom rom other then then miui support.
3)xposed is not available for oreo.
4)i have used nitrogen oreo for about 2 weeks it is stable but not as miui. some time r net would not work, jio call drop, lagging u have to restart on every time u faced problem. i suggest that wait for some time to roll out nought port for kenzo with zero bug & this will happen soon.
Click to expand...
Click to collapse
Thanks for the tip, will update the thread.

@JustMeErazem volte on 2nd sim works well. I myself use it. After flashing magisk just v need to hide root from all system apps to make sure volte works flawless even after reboot. Plz edit it in the description. I hav been using nos since many time so with experience i am giving my feedback. Thanks?

@saifuk what kind of nougat port u are expecting of ?

Aditya1011 said:
@JustMeErazem volte on 2nd sim works well. I myself use it. After flashing magisk just v need to hide root from all system apps to make sure volte works flawless even after reboot. Plz edit it in the description. I hav been using nos since many time so with experience i am giving my feedback. Thanks
Click to expand...
Click to collapse
I haven't rooted my phone, VoLTE still not working.
---------- Post added at 03:37 PM ---------- Previous post was at 03:34 PM ----------
@justmerazem Change VoLTE point again to previous. I installed NOS on mine & my other two friends' phone. They've not used magisk or superSU nor me. But VoLTE doesn't work on 2nd Sim for us.

AtomR said:
I haven't rooted my phone, VoLTE still not working.
---------- Post added at 03:37 PM ---------- Previous post was at 03:34 PM ----------
@justmerazem Change VoLTE point again to previous. I installed NOS on mine & my other two friends' phone. They've not used magisk or superSU nor me. But VoLTE doesn't work on 2nd Sim for us.
Click to expand...
Click to collapse
Flash latest firmware of developer rom. And volte is sure shot working.

Aditya1011 said:
Flash latest firmware of developer rom. And volte is sure shot working.
Click to expand...
Click to collapse
Mate, I'm already on 7.9.22 firmware. Lots of people are reporting it. Yours is working, must be some kind of random.

@Aditya1011 Mate, what happened? No reply? Huh. Latest firmware. No magisk, no any kind of root. No sound mod. Still Volte not working on 2nd Sim on 3 different Kenzos.
@JustMeErazem Please include in your post that VoLTE is indeed buggy.

how to install via dualboot patcher as secondary rom?

AtomR said:
@Aditya1011 Mate, what happened? No reply? Huh. Latest firmware. No magisk, no any kind of root. No sound mod. Still Volte not working on 2nd Sim on 3 different Kenzos.
@JustMeErazem Please include in your post that VoLTE is indeed buggy.
Click to expand...
Click to collapse
Idk bro y that happening to u. Flash miui EU rom n thn the nos rom. Mayb that should work.... Bcuz I had done that for the 1st time whn my volte wasn't working at any cost. Best of luck.

smjhh said:
how to install via dualboot patcher as secondary rom?
Click to expand...
Click to collapse
I don't think dual boot patcher supports oreo roms. Try asking on their thread to see if it does.

Google HDR camera 5 or 5.1 work with this ROM??

sagar13190 said:
Google HDR camera 5 or 5.1 work with this ROM??
Click to expand...
Click to collapse
Read op!

I tried google HDR camera v5 n v5.1 on lineage Oreo, MAOSP Oreo nitrogen Oreo ROM bt its not working...bt in ROM based on nogut 7.1.2 its work great

sagar13190 said:
I tried google HDR camera v5 n v5.1 on lineage Oreo, MAOSP Oreo nitrogen Oreo ROM bt its not working...bt in ROM based on nogut 7.1.2 its work great
Click to expand...
Click to collapse
It works for many users. Did you flash my zip or install an apk?

Sim card detection issue
Sometimes nitrogen os Oreo does not detect sim cards after reboot so I changed ROM and installed aosp extended. I know that Xyyx has already mentioned this as bug. Due to this bug it is not daily driver. Hope xyyx will fix this as soon as possible. If you have solution, please share it.

dhavalmehta said:
Sometimes nitrogen os Oreo does not detect sim cards after reboot so I changed ROM and installed aosp extended. I know that Xyyx has already mentioned this as bug. Due to this bug it is not daily driver. Hope xyyx will fix this as soon as possible. If you have solution, please share it.
Click to expand...
Click to collapse
Dude, it's really not a big problem, it detects it like 95% of the time. Just reboot and you're done. Or wait about 2 min and it should detect it. You could also just remove the sim and reinsert it. But since the latest few updates for me it gets detected 100% of the time. So update to 28/10/2017 build and you should be fine.

@JustMeErazem You're giving flase info. to others saying that VoLTE works on both sim. Actually, it works only on first sim. Tried, tested on 3 different Kenzo's. Clean flashed.
Conclusion: VoLTE doesn't work on 2nd sim.

[UNOFFICIAL] LineageOS 18.1 for Xiaomi Mi Note 10 Lite (toco)

Note that these builds include Google Apps. A vanilla version will be available later.
This project does not rely on MIUI vendor, the vendor image is being built with the ROM and huge parts of it are being built from source.
Changelog
Here you can find all changelog's.
2021-05-20
Code:
* Fixed Dynamic system updates -> You can now launch the Android 12 DSU from developer settings (Note that it does not have much of the new design yet. If you look for that go for other GSIs).
* Update vendor security patch level to 2021-05-01
* Removed unused notification light settings
2021-05-18
Code:
* Reverted default Pixel Blue accent colour back to lineage teal (pixel blue can be selected from styles and themes now)
* Fixed Microphone during calls
2021-05-14
Code:
* Fixed brightness during FOD
* Updated to may Android Security Bulletin

Great work! Thank you, Arian!

simplytb said:
Great work! Thank you, Arian!
Click to expand...
Click to collapse
I have uploaded a new build.
Download: https://sourceforge.net/projects/ep...ge-18.1-20210514-UNOFFICIAL-toco.zip/download
Changelog:
* Fixed brightness during FOD
* Updated to may Android Security Bulletin

Thanks for your work sir

Good job.

thanks!

Hi NeoArian problem with microphone

@NeoArian Hi! I tried the rom, and everything is great! thanks! But the rom has problems with the microphone seems to not be working properly. It doesn't work on the Phone dialer, but it works on video camera and other apps but with bad audio quality and low volume on the microphone. I decided not to go back to MIUI, cause this is way way better, so I'll just wait when the fix comes up. Cheers!

Good evening!
Thanks for the reports about the microphone issue. I have fixed it and uploaded a new build: https://sourceforge.net/projects/ep...ge-18.1-20210518-UNOFFICIAL-toco.zip/download
Changelog:
• Reverted default Pixel Blue accent colour back to lineage teal (pixel blue can be selected from styles and themes now)
• Fixed Microphone during calls
Greetings, Arian.

Would it be possible to provide a list of the included Gapps?

Jisaka said:
Would it be possible to provide a list of the included Gapps?
Click to expand...
Click to collapse
Sure. My repository with the GApps can be found here.
The exact list of google apps can be found here. All the files from this list are extracted from the latest Google Pixel 5 factory image (which can be found here: https://developers.google.com/android/images).

NeoArian said:
Good evening!
Thanks for the reports about the microphone issue. I have fixed it and uploaded a new build: https://sourceforge.net/projects/ep...ge-18.1-20210518-UNOFFICIAL-toco.zip/download
Changelog:
• Reverted default Pixel Blue accent colour back to lineage teal (pixel blue can be selected from styles and themes now)
• Fixed Microphone during calls
Greetings, Arian.
Click to expand...
Click to collapse
Thanks for the update @NeoArian! Everything works fine already. Thanks alot!

please users of this rom I have a question. does the fast charge function work? Thank you

MKey_CZ said:
please users of this rom I have a question. does the fast charge function work? Thank you
Click to expand...
Click to collapse
Good Morning,
Fast Charging does not work correctly. It's limited to 15-20W instead of the possible 30W. The bad thing about it is that xiaomi has been doing something in system which i'm not aware of currently. Fastcharging does not work at all with MIUI vendor + MIUI kernel with an AOSP system image, i have at least got to the same state with OSS kernel and built vendor image but i didn't figure out what unlocks the real fastcharging.
Greetings, Arian.

Good Evening.
I have uploaded a new build. https://sourceforge.net/projects/ep...ge-18.1-20210520-UNOFFICIAL-toco.zip/download
Changelog
* Fixed Dynamic system updates -> You can now launch the Android 12 DSU from developer settings (Note that it does not have much of the new design yet. If you look for that go for other GSIs).
* Update vendor security patch level to 2021-05-01
* Removed unused notification light settings
Greetings, Arian.

Thanx a lot for the effort but i have a qst do i have to reflash the phone for Every update toi make ? Or there IS another way to update thanx again

Aymenbekkari6s said:
Thanx a lot for the effort but i have a qst do i have to reflash the phone for Every update toi make ? Or there IS another way to update thanx again
Click to expand...
Click to collapse
You can flash the new updates without any wipes. Just go into recovery and flash the new zip. If you use lineage recovery connect your phone to your computer and use adb sideload.
I will setup automated weekly build with OTA functionality later.

NeoArian said:
You can flash the new updates without any wipes. Just go into recovery and flash the new zip. If you use lineage recovery connect your phone to your computer and use adb sideload.
I will setup automated weekly build with OTA functionality later.
Click to expand...
Click to collapse
Thanx bro ^^ do you suggest that i use TWRP or lineage recouvert ?

Aymenbekkari6s said:
Thanx bro ^^ do you suggest that i use TWRP or lineage recouvert ?
Click to expand...
Click to collapse
I would recommend lineage recovery if you are able to use ADB sideload to update. TWRP would probably also work fine but I did not confirm that.

[ROM][13.0][OFFICIAL] SparkOS [AOSP][STABLE][30/05/2023]

{
"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"
}
SparkOS is an AOSP based ROM, packed with many features without sacrificing stability and performance.
In short a fully functional operating system as stable and customizable as it should be.
Code:
/* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Device Specific Issues:
• None
Requirements
• You must be on Latest firmware v11.0.3.0 or v11.0.2.0
• You must use any of the recommended recovery (links are given below).
Downloads
Get the latest SparkOS Build for vince: Download
Firmware: https://xiaomifirmwareupdater.com/firmware/vince/
Nikgapps: https://nikgapps.com/
Mindthegapps (Use arm64 only): http://downloads.codefi.re/jdcteam/javelinanddart/gapps
Magisk: https://github.com/topjohnwu/Magisk/releases
Recommended Recoveries:
- TWRP by Starlight
- Orangefox R11.0 Beta
- Read the latest changelogs from: Here
Notes
• Build type: User
• Encryption not supported, Decrypted by default
• Selinux is Enforcing
• FMRadio Included
• Do not flash recovery.img available on the spark download website
Flashing Instructions:
Clean flash (Coming from a different ROM):
• Download ROM
• Download Custom Google Apps Package (Like Nikgapps core/basic or Mindthegapps) if the ROM is Vanilla variant (On GApps ROM variant Google Apps are included, don't flash a separate Custom Google Apps package)
• Reboot to Recovery.
• Wipe System, Data, Vendor, Cache, Dalvik/ART cache partitions
• Flash latest stable firmware v11.0.3.0 before flashing ROM
• Flash ROM zip
• Flash Custom Google Apps Package if the ROM is Vanilla variant
• Reboot to system
To get root access, Reboot to recovery after ROM setup and flash Magisk.zip
BOOTLOOP SITUATION: If you are coming from stock/custom MIUI or any ROM which had data ENCRYPTION, you will face bootloop and can not boot into the system. In such case you need to FORMAT data after flashing the ROM. Otherwise the ROM won't boot (Read detailed instructions from here)
Dirty flash (Updating to a newer build):
• Download the new update ROM zip
• Reboot to recovery
• Do not wipe anything
• Flash the new update ROM zip
• Flash the same Custom Google Apps Package again you flashed before (For vanilla users)
• Flash Magisk again if you are rooted before (For rooted users)
• Wipe Cache and Dalvik/ART cache
• Reboot to system
Important note regarding SparkOS 13.6 update
This is a huge rebase of the ROM's source code after the March update, So Clean flash is MANDATORY for all users. Some bugs from previous versions have been fixed in this version and some new features can be noticed. Some customizations have been temporarily removed (eg: Smart charging, QS row & column customisation etc) and will be added in future releases (Read official community post).
You should be aware of some known source bugs in this release before updating to 13.6. These bugs are not device specific and are present in all Spark official devices which will be fixed in the next update.
Known bugs are;
1. Launcher settings are crashing with light theme (works fine with dark theme). You can use a different Launcher but I think Pixel launcher Extended will not work anymore as spark is now completely based on lineage
2. Shortcut buttons glitches in recent panel.
3. Visual glitch on Quicksettings/Statusbar after a reboot (Restarting SystemUI fixes it for now)
Join our Telegram Group https://t.me/SparkOSChannel
Buy me a Coffee https://paypal.me/spyroskal
See our website https://spark-os.live/
Device Support Group https://t.me/anandhansprojects_chat
Source Code
SparkOS http://github.com/Spark-Rom
Device Tree and Vendor Tree https://github.com/Spark-Devices
Kernel Tree https://github.com/aospa-vince/android_kernel_xiaomi_vince
ROM OS Version: Android 13.0
Spark-OS Version: Android 13.6
Security Patch Level: May 2023
ROM Kernel: Linux 4.9.x
Stable Release Date: 30.05.2023
Latest Release Date: 30.05.2023

This is great. Seems to run well - but can't get it to play nice with Viper4Android.

droident said:
This is great. Seems to run well - but can't get it to play nice with Viper4Android.
Click to expand...
Click to collapse
No issues with viper4Android here.
Check if you've rooted properly?
Or maybe you are using a mod version of viper4Android.

Been using it for half a year and it's the best Android 13 rom I tried (not that there's many that are up to date)

anandhan07 said:
No issues with viper4Android here.
Check if you've rooted properly?
Or maybe you are using a mod version of viper4Android.
Click to expand...
Click to collapse
I used the repackaged v4a from github. Clearly something went wrong here if it's working at your end. I'll try again later when I'm home as I'll need to install from scratch having reverted to A12. Guessing maybe I just needed to reboot again or something. Here's the version I used:
GitHub - programminghoch10/ViPER4AndroidRepackaged: A refined ViPER4Android installer.
A refined ViPER4Android installer. Contribute to programminghoch10/ViPER4AndroidRepackaged development by creating an account on GitHub.
github.com
I have to say the smooth responsiveness on these new A12/A13 ROM builds is surprising given how often A11 would lock up for me. Maybe my device just finally needed a reset idk.

OK. Mystery solved. Turns out that Viper4Android does indeed work - it just needed an extra reboot.
So I flash it > reboot > v4a App appears on next boot but doesn't work > reboot again > v4a works.
Weird but makes sense. Sorry for the confusion.

I couldn't receive this kind of google login authorization on this rom "is it you trying to sign in". Device wasn't appearing in google account double verification. No problem in a13 elixir.
Also sadly no option 2g connectivity.
Rom itself seems smooth. ATM moved back to A10

I have problem, the screen show on/ off at redmi boot logo

CPU cores seam to be locked to 1400 mhz

Hello İ installed latest Spark OS gapps build on my a205f i loved the rom but it has a bug phone screen freezes cant close the screen no reaction to calls,notifications,holding down the power button the only solution is to wait for the battery drain it happened 2 times what can i do i guees this build is laggy

This is possibly a long shot but any chance of modified files for higher quality audio on Bluetooth SBC (or AAC)? It used to be you could patch it in via Magisk but the module no longer works on newer android versions and if I'm correct the edits need to be made before a ROM is built. If you're able to, any chance of some experimental files for me to try out?
I think the values are in a2dp_sbc_encoder for SBC, a2dp_aac for AAC. A2DP_XXX_DEFAULT_BITRATE 000 where XXX is SBC or AAC and 000 is the bitrate in kbit/s.

Mr.Bra said:
Hello İ installed latest Spark OS gapps build on my a205f i loved the rom but it has a bug phone screen freezes cant close the screen no reaction to calls,notifications,holding down the power button the only solution is to wait for the battery drain it happened 2 times what can i do i guees this build is laggy
Click to expand...
Click to collapse
This is sparkos for vince aka Redmi 5 plus. Not for a205f

droident said:
This is possibly a long shot but any chance of modified files for higher quality audio on Bluetooth SBC (or AAC)? It used to be you could patch it in via Magisk but the module no longer works on newer android versions and if I'm correct the edits need to be made before a ROM is built. If you're able to, any chance of some experimental files for me to try out?
I think the values are in a2dp_sbc_encoder for SBC, a2dp_aac for AAC. A2DP_XXX_DEFAULT_BITRATE 000 where XXX is SBC or AAC and 000 is the bitrate in kbit/s.
Click to expand...
Click to collapse
will see

Latest Vince just got released yesterday - thank you
https://sourceforge.net/projects/sparkosofficial/files/vince/Spark-13.3-Official-vince-20230105-gapps.zip/download

Hi,
I installed this rom, until I see it I'm liking it, but the screen rotation doesn't work.
Any idea?
Thanks...

Hello everyone, just flashed this ROM on my Vince (coming from Elixir 3.3 - A13).
Since I use this phone to debug my apps, I need to connect Chrome DevTools to it.
What I've done so far:
- wiped everything
- installed Spark-13.3-Official-vince-20230105-gapps
- installed Magisk 25.2
- registered my Google account
- updated all apps (through Play Store)
- enabled Developer options, then USB debugging
Now, when I launch Chrome DevTools on PC, I can see the phone but the webpages list is empty; it also doesn't show any WebView instance (see the screenshot below).
Remote debug was working with Elixir 3.3 on the same phone and PC, so I suppose the difference is in some ROM setting... something to be changed here, but I'm out of ideas...
Does anyone have any suggestions about this?

maxi_power said:
Hi,
I installed this rom, until I see it I'm liking it, but the screen rotation doesn't work.
Any idea?
Thanks...
Click to expand...
Click to collapse
First, make sure you have enabled auto rotate screen option. It is disabled by default.
If it's enabled send a screenshot from sensor test app (available in playstore). ROM doesn't have issues auto rotates screen.

nicorac said:
Hello everyone, just flashed this ROM on my Vince (coming from Elixir 3.3 - A13).
Since I use this phone to debug my apps, I need to connect Chrome DevTools to it.
What I've done so far:
- wiped everything
- installed Spark-13.3-Official-vince-20230105-gapps
- installed Magisk 25.2
- registered my Google account
- updated all apps (through Play Store)
- enabled Developer options, then USB debugging
Now, when I launch Chrome DevTools on PC, I can see the phone but the webpages list is empty; it also doesn't show any WebView instance (see the screenshot below).
View attachment 5804415
Remote debug was working with Elixir 3.3 on the same phone and PC, so I suppose the difference is in some ROM setting... something to be changed here, but I'm out of ideas...
Does anyone have any suggestions about this?
Click to expand...
Click to collapse
Can you send logcat?
I am not using this feature. I will test this later.

anandhan07 said:
First, make sure you have enabled auto rotate screen option. It is disabled by default.
If it's enabled send a screenshot from sensor test app (available in playstore). ROM doesn't have issues auto rotates screen.
Click to expand...
Click to collapse
Hi, thanks for the answer.

maxi_power said:
Hi, thanks for the answer.
Click to expand...
Click to collapse
Seems like you messed up persist
So flash persist.img via recovery (in persist partition) and reboot into system. Do not wipe anything.
Link of pesrist.img: https://t.me/anandhansprojects_chat/15693

[ROM][12.1][UNOFFICIAL] LineageOS 19.1 for Lenovo P2

Installation Instructions
Remember, making a backup of your data before proceeding is recommended
If you are coming from Stock ROM, please refer first to the instructions below:
Install LineageOS on kuntao
If you are coming from astridxx previous build (aka lineage-19.1-20220822-UNOFFICIAL-kuntao) or my initial build (aka lineage-19.1-20230222-UNOFFICIAL-kuntao) or any version of LOS18.1 or below, you must perform a clean flash. Clean flash instructions:
0- Make a backup (optional, but recommended)
1- Reboot to recovery
2- Format data (will delete all your data!)
3- Reboot to recovery again
4- Wipe > Advanced Wipe:
- Dalvik
- System
- Vendor
- Data
- Cache
- Internal Storage (optional, but recommended)
5- Flash ROM ZIP, Gapps, Gapps add-ons, Magisk add-on, etc
6- Reboot to system
7- Wait until it boots for the first time (may take some minutes)
Update Instructions
NOTE: Dirty flash from any of the aforementioned builds is not supported, device trees were changed. You have been warned!
For updating from one of my builds to another (aka dirty flashing), please do the following:
1- Download ROM ZIP and copy it to the phone
2- Reboot to recovery
3- Flash ROM ZIP
4- Clean cache
5- Reboot to system

Known Issues- Storage encryption is partially broken (if your /data partition is unencrypted, trying to encrypt it using ROM menu will result in a dead OS; if already encrypted, storage encryption may or may not work. IFAIK, it's a kernel side issue)
- Device may not go to deep sleep
- Storage forceencrypt flag is disabled (to encrypt /data partition follow the instructions below)
- TWRP backups are broken (read notes below)
- You tell
Google Play Store Update Bug
If Google Play Store app keeps failing to find updates for apps with message "Something went wrong. Try again.", just clear its data and then it should work again
SafetyNet Check Fails
If your device is rooted, please, follow the instructions contained here
Magisk is Gone After First Boot
Please, just reflash Magisk again (i.e. Reboot to recovery > Flash ZIP > Reboot back to system)
How to encrypt data partition
0- Backup your files (this process will erase everything)
1- Boot to TWRP recovery
1.1- Wipe > Format data > Reboot to system
2- Settings menu > Security > Encryption & credentials > Encrypt phone
3- Reboot to system again
Error restoring TWRP system backups
It looks like TWRP backups are broken for now, so please, if this is a must have for you, you can try to install OrangeFox recovey and follow these instructions (thanks @Zdeslav for that)
ROM Change logs
Code:
02/22/2023
- Initial release
02/27/2023
- Sync latest LOS sources
- Device Tree change: Use old A12L dt instead of los
- Add Lenovo Parts menu (fp gestures, USB fast charge, in-call audio gain, screen kcal)
- Updates phone vibration strength
- Add fix to device deep sleep issue
- Many more changes
03/29/2023
- Fetch latest Device Tree sources
-- vendorsetup.sh: Add Trebuchet patch
-- AOSP WFD doesn't support protected Wi-Fi Display buffers
-- Overlays:
--- Enable voWIFI support
--- Disable IMS features for Turkiye networks
-- Don't warn user about FC in Vanced microG
-- DT rootdir:
--- Add cpuset for the camera daemon
--- Remove permission restrictions to the socket file
--- Restore iio sensor device6 on boot
-- Bump graphene camera version to 60
-- Don't force enable ims features
-- sepolicy: Address sensor hal denials
- Update LOS components
-- Manifest: Sync x86_64 webview prebuilts again
-- Update zlib source
- Sync latest LOS source
- Merge March security patch
04/09/2023
- Fetch latest Device Tree sources
-- Add navbar enable/disable support
-- fs: Revert sdfat update for OTG
-- block: Add zen io scheduler
-- dts: Decrease BCL low battery threshold to 5%
-- DeskClock:
--- Wallpaper based text coloring for digital
--- Adapt digital clocks to S style
--- Remove night mode
-- Trebuchet:
--- Kill haptics in recents
--- Make overview scrim transparent again
-- Nfc: Fix Mifare Classic reading
- Update LOS components:
-- lineage: Track the FMRadio App and dependencies
- Sync latest LOS source
04/19/2023
- Fetch latest Device Tree sources:
-- sepolicy: Silence tracingproxy_service neverallow denial
-- sepolicy: Allow system_app to access storaged via IPC
- Sync latest LOS source
- Merge April security patch
05/09/2023
- Fetch latest Device Tree sources:
-- Bump graphene camera version to 62
-- devicesettings: Protect broadcast to fingerprint gestures
-- rootdir: Remove permission restrictions to the socket file
- Sync latest LOS source
- Merge May security patch
06/11/2023
- Fetch latest Device Tree sources:
-- parts: Update few parts icon
-- vendorsetup.sh: Use depth=1
-- Remove pixel_2016_exclusive
-- Bump graphene camera version to 63
- Sync latest LOS sources:
-- Additional zstd cmdline tools
-- zstd compression support for rsync
-- 2023-06 ASB patching: packages/apps/Traceur
- Merge June security patch

ROM Screenshots
Attached below. Others are available here.

February 27th 2023 Release
Changelog:
- Sync latest LOS sources
- Device Tree change: Use old A12L dt instead of los
- Add Lenovo Parts menu (fp gestures, USB fast charge, in-call audio gain, screen kcal)
- Updates phone vibration strength
- Add fix to device deep sleep issue
- Many more changes
Download URLs: GDrive | SF
Dirty flash still not supported (tree changed), please make a clean flash

Thank you so much for keepng Lineage alive, its very much appreciated.

@leo_97 thank you for this new build! Installed it straight away and now the phone is running since then and also, I've flashed with battery at 67% and atm, after a quite hard usage to test out the new features, I'm on 13%. Basically, so far so good!
p2a42, twrp 3.7, rooted, unencrypted

Thank you @leo_97 !
I was frustrated that Lineageos 18.1 was no longer maintained when I saw this update!
It's amazing
To all users and developers who tested and created this ROM, is it time to switch on this version ?
Or is it better to wait ?
For example, automatic update is possible after install ?

bidulez said:
automatic update is possible after install ?
Click to expand...
Click to collapse
No

bidulez said:
Thank you @leo_97 !
I was frustrated that Lineageos 18.1 was no longer maintained when I saw this update!
It's amazing
To all users and developers who tested and created this ROM, is it time to switch on this version ?
Or is it better to wait ?
For example, automatic update is possible after install ?
Click to expand...
Click to collapse
You are welcome
If it's time to switch, I believe it's a matter of personal decision. Maybe you could wait the next build and then decide...
If with "automatic updates" you mean OTA updates, then the answer (as already pointed out by @utwer ) is no. But once the trees are stable enough, I hope every user will be able to just update to the newer versions flashing ROM ZIP through TWRP (just like it's done on LOS18.1)
BTW, IDK if you already saw it, but we are maintaining a monthly build of LOS18.1 which you can download from here. The source tree used there is far more tested (as it's older) than this one. Anyway, except by the encryption thing, you shouldn't have any problems using this LOS19.1 ROM as our amazing developers made an excellent job here.

Reg, Ive installed it and I may say it is quite good. Not tried to root it yet. Dont have direct problems with ROM and functionality, for me everything works. Camera, Location, GSM, Data, WiFi. With developer options I've turned off Animation scale on three options to OFF, and is good. Stable reliable.
MindTheGapps-12.1 works every app from Google, Phone, Contact, Gmail, maps...etc...
What I need root mostly is for Call recording (Skvalex) and Viper4Android.
Some words about twrp-3.7.0_9-0-kuntao.img,
With this I have only problems, so far I lost a few backups and I need to install it all over again a few times allready. Disappointed very. I can't rally on this when I make a nandroid ba.ckups.
Also lost backups for LOS18.1 and I am been very pis....ed off. Error 255 on System recovery, other Data, Boot, EFS, Vendor, etc.. recovery is good.
So I've installed OrageFox for Kuntao. Tried several backups to restore already and I may say I am very satisfied. Puh
What is on my mind, when I installed a Magisk 25.2, no matter of LOS 18.1 or 19.1 with very few modules, after 7-8 reboots I've got boot loops which is beyond repairable.. Try to remove modules in TWRP in file manager, uninstall whole magisk, no way, but what it is seems that DATA got corrupted some how, everytime.
There were also installed TWRP mentioned above.
Now I am with OrangeFox and I will try tomorrow to Root it and see is there any connection between Magisk and recovery software (OrangeFox or TWRP).
Reg

Tried quickly this ROM yesterday. In general all working, but didn't test much.
Few feedbacks:
-Scaler for brightness level is weird, very different from the original Lenovo roms. Anyway, not really important, but something that I noticed.
-Missing haptic feedback when using the fingerprint reader as a gesture button. Again, not critical, but I am really accustomed to it and thus I noticed immediately.
-Missing haptic feedback intensity regulation, or could not find it. It's there for general call/notification vibration, but if I remember correctly lineage could also change haptic.
Impressed that you could integrate also some lenovo features, even if of course not all of them
If you want me to test something more specific, please let me know. Ah, my model is the 4 GB/ 64 GB combination.
Cheers!

leo_97 said:
You are welcome
If it's time to switch, I believe it's a matter of personal decision. Maybe you could wait the next build and then decide...
If with "automatic updates" you mean OTA updates, then the answer (as already pointed out by @utwer ) is no. But once the trees are stable enough, I hope every user will be able to just update to the newer versions flashing ROM ZIP through TWRP (just like it's done on LOS18.1)
BTW, IDK if you already saw it, but we are maintaining a monthly build of LOS18.1 which you can download from here. The source tree used there is far more tested (as it's older) than this one. Anyway, except by the encryption thing, you shouldn't have any problems using this LOS19.1 ROM as our amazing developers made an excellent job here.
Click to expand...
Click to collapse
So for 18.1 we can just flash the newer versions via TWRP and do not have to reinstall the entire ROM?

Zdeslav said:
Reg, Ive installed it and I may say it is quite good. Not tried to root it yet. Dont have direct problems with ROM and functionality, for me everything works. Camera, Location, GSM, Data, WiFi. With developer options I've turned off Animation scale on three options to OFF, and is good. Stable reliable.
MindTheGapps-12.1 works every app from Google, Phone, Contact, Gmail, maps...etc...
What I need root mostly is for Call recording (Skvalex) and Viper4Android.
Some words about twrp-3.7.0_9-0-kuntao.img,
With this I have only problems, so far I lost a few backups and I need to install it all over again a few times allready. Disappointed very. I can't rally on this when I make a nandroid ba.ckups.
Also lost backups for LOS18.1 and I am been very pis....ed off. Error 255 on System recovery, other Data, Boot, EFS, Vendor, etc.. recovery is good.
So I've installed OrageFox for Kuntao. Tried several backups to restore already and I may say I am very satisfied. Puh
What is on my mind, when I installed a Magisk 25.2, no matter of LOS 18.1 or 19.1 with very few modules, after 7-8 reboots I've got boot loops which is beyond repairable.. Try to remove modules in TWRP in file manager, uninstall whole magisk, no way, but what it is seems that DATA got corrupted some how, everytime.
There were also installed TWRP mentioned above.
Now I am with OrangeFox and I will try tomorrow to Root it and see is there any connection between Magisk and recovery software (OrangeFox or TWRP).
Reg
Click to expand...
Click to collapse
So,
Resolved issue of bootloops:
after you install SU like Magisk, and wan to freeze apps by Titanium Backup or Neo-Backup, Apps which causes bootloops are ROM's Phone and Massages (In my case, for 16.1, 18.1, 19.1), I freeze Audio.apk who need to be shutdown for Viper4Android app who takes audio management and freezing is OK.
But Phone and Massages which are frozen cause bootloops, so you need to return from freeze state somehow in TWRP or OrangeFox with file management or revert backup. Revert backup is easier .
Camera; found issue when suddenly is out of work and cannot be connected to app. Also have problems with video cast Skype, Viber, Whatsapp, Telegram video is frozen. Hardly switch in Camera app from Camera mode to Video mode and vice-versa.
Clock & Info; missing dock icons and info, can't "capture" moment for reason when they disappear but after a while all is returned again.
P2oggle, left switch button work okey in form of 0.4 version.
Reg,
thanks on the development for this 19.1 ROM.

Zdeslav said:
Camera; found issue when suddenly is out of work and cannot be connected to app. Also have problems with video cast Skype, Viber, Whatsapp, Telegram video is frozen. Hardly switch in Camera app from Camera mode to Video mode and vice-versa.
Clock & Info; missing dock icons and info, can't "capture" moment for reason when they disappear but after a while all is returned again.
P2oggle, left switch button work okey in form of 0.4 version.
Reg,
thanks on the development for this 19.1 ROM.
Click to expand...
Click to collapse
Hello,
I've been using this ROM as my daily driver and couldn't confirm this camera bug, could you please give a few extra details? I tested on Telegram app. Which version are you using? The Play Store's one or the one from Telegram's official website? Did you give the app "While using app" permission or "Ask every time" permission for camera? Are you sure the QS Tile "Camera access" is activated (available) when the mentioned bug occurs?
Regarding the Clock widget, yes, there's a small glitch and I'm not sure on how to fix it, if it doesn't load at all, a system reboot should fix it.
P2oggle v1.2 is 100% working as far as I can tell, so you guys can try it too if you want.
MKbis said:
-Scaler for brightness level is weird, very different from the original Lenovo roms. Anyway, not really important, but something that I noticed.
-Missing haptic feedback when using the fingerprint reader as a gesture button. Again, not critical, but I am really accustomed to it and thus I noticed immediately.
-Missing haptic feedback intensity regulation, or could not find it. It's there for general call/notification vibration, but if I remember correctly lineage could also change haptic.
Click to expand...
Click to collapse
I'm not sure if it's possible to "fix" the brightness slider.
If with "haptic feedback" you mean the phone vibration, you can just adjust it to your liking in Settings > Lenovo parts > Vibration strength, it should affect fp reader too, dunno if it affects call vibration but IFAIK it should.
Regards

Leo_97
I've been using this ROM as my daily driver and couldn't confirm this camera bug, could you please give a few extra details? I tested on Telegram app. Which version are you using? The Play Store's one or the one from Telegram's official website? Did you give the app "While using app" permission or "Ask every time" permission for camera? Are you sure the QS Tile "Camera access" is activated (available) when the mentioned bug occurs?
Click to expand...
Click to collapse
Yes on latest Telegram app from web site, tried with Google Meet, Whatsapp, Viber.., always breaking connection with API/drivers. Yes I gave all permissions to Camera. If I am not giving permissions for camera, I have always noticed to confirm what I am giving, so I am excluded from this solution. And clean storage and cashe from app regular but not prevail.
But, in a while after installed a new ROM without giving SU/Root I noticed this behavior, right after I wrote earlier post up. My bad .
Choppy startup of camera, can't easily transfer from video 2 camera and vice-versa, so I tell to my self to test intensively.
Regarding the Clock widget, yes, there's a small glitch and I'm not sure on how to fix it, if it doesn't load at all, a system reboot should fix it.
Click to expand...
Click to collapse
Yes after a while it is returned back without reboot. weird.
P2oggle v1.2 is 100% working as far as I can tell, so you guys can try it too if you want.
Click to expand...
Click to collapse
Didn't know about P2oggle v1.2 app, thx

March 29th 2023 Release
Changelog:
- Fetch latest Device Tree sources
- Update LOS components webview & zlib
- Sync latest LOS source
- Merge March security patch
- Many more changes
Full change log available on the bottom of this post
Download URLs: GDrive | SF
Note: Please, before flashing, carefully read the instructions from the 3rd post above to avoid breaking your system.
Enjoy!

Big Thank you for this release. Will try it. - test

Great job, dude.
Previous versions had some buggy charging driver that left a wakelock running after each charging, and u had to restart phone each time or leave it to slowly drain battery by not going to sleep.
Somehow this problems seems to be gone in your build and that is awesome.
I've been using the build for about 2 weeks now and so far everything seems to be working fine.

April 09th 2023 Release
Change log:
- Fetch latest Device Tree sources (lots of changes)
- Update LOS components:
-- lineage: Track the FMRadio App and dependencies
- Sync latest LOS source
- Many more changes
Full change log available on the bottom of this post
Download URLs: GDrive | SF
Note: Dirty flash is unsupported for this build, please make a clean flash
Enjoy!

Database Users

welcome