Database Develop

[Discussion, FAQ and Help Thread] ROM: [WIP]AOSP Nougat 7.0 by SanthoshM

Discussion Thread for AOSP Nougat ROM (SanthoshM) ​
Hi all,
See the main development thread here
Please consult the FAQ/Issues/Changelog list below before posting, some of your problems might have been solved already!
Since the main thread for the still-WIP Nougat 7.0 ROM by @santhoshm was getting very cluttered with the same questions and answers, making new updates by the OP difficult to find, I thought we could use this thread to discuss bugs, issues anyone is having installing the ROM and configuring apps, and answering general frequent questions without clogging the main thread.

This gets updated at least once per day
Useful Utils
-----------------------------------------------------------------
Nexus 5 Google soundkit and Pixel Launcher Flashable ZIPs by @edwaine (link to APK by @occtec)
If you're tired of the AOSP sounds and/or want the leaked Pixel Launcher as a flashable ZIP, see this post.
Debloater Scripts by @androcraze
Updated link to separate thread: you're now welcome to discuss any issues or feedback with the debloater scripts or DeltaDroid's GApps packages over there.
Selection of flashable ZIPs that remove some/all of the preinstalled (old) AOSP apps from the ROM completely. You can choose to remove them all, or keep some, plus we recommend great FOSS alternative apps for the Google equivalents. Choose from Maximum, Medium or Minimum debloating.
FAQs
-----------------------------------------------------------------
Send a "thanks" to @androcraze for his additional collation of FAQs and notes integrated into this post!
Please read this section before posting a question or bug, it might already be answered here!
Changelogs for FAQs
Code:
[LIST]
18 September 2016
[*] New build added
8 September 2016
[*] Added YouTube fix
[*] New links to debloat script
[*] New build available
7 September 12PM
[*] Added fix for phone crashing
3 September 3pm SAST
[*] New build (see changelog)
1 September 12PM SAST
[*] Added new build info
30 August 5pm SAST
[*] Added potential fix to green screen on video recording
30 August 12am SAST
[*]Added info on battery drain solution
[*]Added info on root access
29 Aug 12am SAST
[*] Added "debug-only private cache fix
[*] Added green-screen flicker issue
[*] MultiROM fixes!
28 Aug 12am SAST
[*] Modified FAQ with the new build
[*]Added tip on keeping Night mode active
27 Aug 7pm SAST
[*] Fixed broken link to green line fix on video
27 Aug 12PM SAST
[*] Improved GApps install instruction (See Installation FAQ)
[*]Added solution to TimeService issue (See Usage FAQ)
[*]Added solution to Boot animation missing (See Installation FAQ)
[*]Added possible solution for green line (see Apps FAQ)
[/LIST]
Installation FAQ
Q: Which recovery should I use for this ROM?
A: TWRP 3.0.1 or 3.0.2 is required.
Q: Does Busybox work?
A: Yes, check here.
Q: How do I get root?
A: As you would normally - download this SuperSU ZIP (latest 2.77 beta works fine) and copy it to your device storage. Reboot into TWRP and flash the ZIP, then reboot the device. If the boot loops once or twice, that's normal. Once it's done, you can confirm by checking for the "SuperSU" app in your app tray.
Q: Which GApps to use?
A: Check out pico, nano or micro GApps on the Open GApps page. Some have had luck with Mini but this varies by build.
Q: Can I use MultiROM to install this ROM?
A: Update 29 Aug : MultiROM fixes here Courtesy of @blade
Q: Procedure to install ROM with GApps
A: Note: Latest ROM build allows flashing ROM + GApps in one queue without crashes
(For older builds) A: Don't flash the ROM together with GApps in the same ZIP queue because this will cause the Installation Wizard to run on first boot. Due to Google Play permissions errors the Wizard will keep crashing and you won't be able to bypass this. Solution:
1. Enter TWRP, wipe as needed, install the ROM via TWRP
2. Reboot the phone to Android (configure WiFi and APN info).
3. Reboot back to recovery
4. Install GApps via TWRP
5. Boot to System (Yes, you'll probably get Play Services "FC" messages until you perform #6, below)
6. Immediately toggle application permissions to "ON" under:
Settings -> Apps -> ... -> System show
For:
- Google Contacts Sync
- Google Play Services
- Google Play Store
7. Reboot the phone
8. Add your Google Account via "Settings -> Accounts -> Add account -> Google"
9. Verify that Contacts are synced and Play Services is functional.
Q: Why does Settings > Backup and restore shows "debug-only private cache" instead of my Google account?
A: There's a fix (Tested as working!) that you can try here
Q: After flashing TWRP says "No OS Installed?" Note: This has been fixed in the latest build)
A: Ignore this message. If the ROM flash indicated as being successful, you can swipe to reboot and the OS should boot.
Q: After flashing the ROM I've lost TWRP, what gives?
A: Since this was a stock AOSP image it includes stock recovery. Do this to get TWRP back;
Enable developer options on your device by pressing the build number 7 times on Settings > About Phone
Enable USB debugging in developer options
Connect your device to your PC and issue
Code:
adb reboot-bootloader
from wherever your ADB is installed
Place the TWRP image in the ADB folder.
Your phone should restart to the fastboot interface. Now issue
Code:
fastboot flash recovery <twrp.img>
where <twrp.img> is the name of the TWRP file
When that's done, issue
Code:
fastboot reboot-bootloader
and choose "Enter recovery" to go into your TWRP
Ensure TWRP performs the one-time step of setting itself to read-write permissions, by else it'll disappear again on next boot.
Newer builds are being reported to preserve TWRP on reflash.
Apps FAQ
Q: My Google Play Store / Google Play Services / Apps keep crashing?
A: This is a permissions issue. Go to System Settings > Apps (top right menu button) > Show System
Set the following to resolve most crashes:
Google Contacts sync > Contacts permission
Google play services > all permissions
Q: My contacts aren't syncing?
A: Give the contacts app contacts permission and try Settings > Accounts > Google > Contacts (uncheck and recheck)
If this doesn't work, uninstall the GApps contacts APK, and install this Google Contacts APK as an update to the system one. Perform the step above and contacts should sync.
Q: What if I want to use the setup wizard to copy apps, accounts and data after install?
A: Install the ROM and GApps as advised in the Installation section, once you've set up everything and permissions etc. do a factory reset. This should fix it (thanks @devilsadidas for the tip).
Q: Where is the System Tuner UI?
A: Enable Developer Options (under "About Phone", tap "Build Number" seven times), then long-press the settings icon in the notification shade/bar.
Q: How do I get rid of the green screen flickering in video recording?
A: This is a known issue (See Known Issues). Update - @nisby reports (confirmed) that using Footej Camera solves the problem. If you per sé want to us Google Camera or the AOSP Camera, @chrisk44 reports the 25/08 build doesn't have that problem.
Q: My YouTube Videos don't play or throw an error
A: This can be fixed by flashing the 16/09 build.
Usage FAQ
Q: My date and time keeps resetting on successive boots?
A: Solution is to install the Qualcomm TimeService app (a proprietary application)
- the 6.0.1 version (tested successfully with 7.0) is available HERE
Q: Does this build support Vulcan?
A: No. Vulcan does not provide support the Nexus 5.
Q: Does doze work in this build?
A: Yes. You do not have to enable anything; it is active by default.
Q: Can I use this ROM with Android Pay?
A: No. Only approved factory ROMs from Google can use Android Pay. If you want Android Pay on the Nexus 5, install a Marshmallow factory image.
Q: Where can I get the Nougat bootanimation?
A: Try Post #1 in this Boot Animation Collection. Or flash 16/09 build.
Q: If you can't install apps from Play Store: (error code DF-DLA-15)
A: Go to Settings/Apps/Google Play Services/Storage/Manage space/Clear all data.
Then go back to:
Settings/Apps/Google Play Services/Permissions and turn on all permissions (thanks to @BazingaOG for this tip)
Q: My battery charges slowly. Now what?
A: This is a known issue. See "Known Issues" below and check the Changelog below for any updates on this. (Thanks to @olivercervera )
Q: How is battery life with Nougat on the Nexus 5?
A: It should be comparable to Marshmallow. If you're having battery drain issues and are rooted, try this solution.
Q: Why is the font scaling on the date/time quick settings pulldown weird?
A: Known issue. Switch "Display size" (NOT "Font size") in Settings to "Small". (Thanks @Nick80835 for the tip)
Q: Where can I find your build tree?
A: It will be posted once the ROM is stable.
Q: Can you add new features?
A: The goal of this ROM is to get a clean build under AOSP. "Features" aren't a priority.
Q: Night mode won't stay enabled if I try to toggle it?
A: Touch the "on" label on the left to turn it on, NOT the toggle switch on the right (thanks @smartboy0668 for the tip)
Known Issues
As of 8 September:
YouTube doesn't play for some. 16/09 build apparently fixes this.
Some users report crashes, blank-screening in-call and permissions issues with Google Play Phone app despite setting permissions. Confirmed solution here. (Thanks @DVDandroid and @jokerclown)
Settings > Backup shows "debug-only private cache" instead of Google account (Solution under Installation FAQ) Fixed in 08/09 build
Video green-screen flickering (discussed here) - App fix here . Use 25/08 build for working Google Camera. (Thanks to @chrisk44 for the tip)
Carriers such as Sprint have no signal (confirmed by @famewolf)
Changelogs for ROM
16 September
Changelog :
Updated to android 7.0.0_r6 (NRD90U)
Should fix youtube issues for some users
Security vulnerability CVE-2016-2059 patched (as reported by a user)
AOSP nougat bootanimation added
Other non AOSP features ( UItuner features & others) continue to remain
Click to expand...
Click to collapse
8 Sept @ 11PM SAST
Changelogs :
Updated to android 7.0.0_r4 (NRD90S)
September security patch
"debug-only private cache" in settings-backup should be fixed now (thanks @Rapper_skull for the patch )
About phone will now reflect Nexus 5 instead of "AOSP on hammerhead"
Other non AOSP features ( UItuner features & others) continue to remain
Click to expand...
Click to collapse
3 Sept @ 3pm
Changelogs : (03/09/2016)
Implemented webview patch based on @Rapper_skull patch and discussion with @osm0sis
(device boots now even when there is no gapps flashed. I haven't tested flashing with gapps nor tested if the webview implementation works correctly ! Would be nice if someone does)
Switched from eng build to userdebug build
Added support for gesture swiping in keyboard.
Enable/disable toggle to hide brightness in quick settings is now available and is there in systemui tuner menu ( It's just a aosp feature and was just hidden and i have unhided it)
Click to expand...
Click to collapse
1 Sept @ 12pm
Fix settings FC on boot
Disable data roaming by default
Advanced reboot feature ( reboot is a must needed thing and hence )
Previous hidden systemui tuner features continue to remain
Click to expand...
Click to collapse
27 August @11pm
Released a new build (27/08/2016)
Nothing much, just goodies and improvements. Previous hidden systemui tuner features continue to remain
Goodies :
* Double tap on statusbar to sleep
Improvements :
* Gapps permission grant patch included in the OS
* Fix the "No OS installed" message when you try to reboot after flashing the ROM via twrp
Click to expand...
Click to collapse
25 August @ 7pm
Issues fixed :
* Camera pictures not getting saved ( Have checked video recording too )
* Enabled the power modes doze flag
Additional goodies :
Both these will be available in systemui tuner
* Enabled night mode ( i am loving it )
* Nav bar customization
Download link available in OP
Click to expand...
Click to collapse

I flashed this ROM today and installed OpenGApps Aroma package. Then after the first boot I did all the permission stuff i.e. provided all the permissions to Play Services and related apps.
But I am still unable to load up my Google Account, Play Services still Force Close on adding a account. Any Help is appreciated.

CrashOverride1995 said:
I flashed this ROM today and installed OpenGApps Aroma package. Then after the first boot I did all the permission stuff i.e. provided all the permissions to Play Services and related apps.
But I am still unable to load up my Google Account, Play Services still Force Close on adding a account. Any Help is appreciated.
Click to expand...
Click to collapse
I'm not sure if this will help, but did you flash the ROM and then GApps straight after it? That caused issues for me. I flashed the ROM, booted into it once without GApps, then rebooted to TWRP and installed GApps, which suppressed the installation screen and allowed me to add Google accounts without crashes.

CrashOverride1995 said:
I flashed this ROM today and installed OpenGApps Aroma package. Then after the first boot I did all the permission stuff i.e. provided all the permissions to Play Services and related apps.
But I am still unable to load up my Google Account, Play Services still Force Close on adding a account. Any Help is appreciated.
Click to expand...
Click to collapse
MattDN93 said:
I'm not sure if this will help, but did you flash the ROM and then GApps straight after it? That caused issues for me. I flashed the ROM, booted into it once without GApps, then rebooted to TWRP and installed GApps, which suppressed the installation screen and allowed me to add Google accounts without crashes.
Click to expand...
Click to collapse
Exactly what @MattDN93 says, also make sure you give all Google Apps which you have installed all needed permissions, just to be sure that they all work as they should. I had the same problem but after checking and allowing the needed permissions everything worked just fine. I use the the OpenGapps Micro Package, you might want to try a clean flash with the suggested flashing order (First the ROM, boot up and then flashing Gapps after) and try the Micro Package, maybe that will work better for you. :good:

Thanks for making this thread!
Could you tell me if Santosh's latest build is more stable than cdesai's or not?

Karan_Brar said:
Thanks for making this thread!
Could you tell me if Santosh's latest build is more stable than cdesai's or not?
Click to expand...
Click to collapse
No problem! From what I can see Santosh was updating his build to fix the camera saving issues that CDesai's build already had sorted. However, check the changelog above - Santosh has added Night mode and fixes for Doze, so theoretically his build should be as stable as CDesai with extra features. I haven't flashed the latest one yet but I will report back here (or you could, whoever flashes it first ).

How do I get the setupwizard after i install the gapps? I need it so it can sync all my app data and settings
Thank you for all your work

gabel160 said:
How do I get the setupwizard after i install the gapps? I need it so it can sync all my app data and settings
Thank you for all your work
Click to expand...
Click to collapse
A factory data reset should do it
Sent from my AOSP on HammerHead using Tapatalk

I'm running the latest build of SanthoshM and it's very stable at the moment but I have a issue on something
I can enable battery percentage in system UI tuner but sometimes battery percentage disapears and I have to enable it back in system UI tuner. Last time, it disapeared after a reboot. Other persons who have this issue?

Great, thanks for this thread, It may be useful to most. people.
@MattDN93, you may want to add the only known issue so far: slow battery charging, @ 0.75A, measured with a tester.

olivercervera said:
Great, thanks for this thread, It may be useful to most. people.
@MattDN93, you may want to add the only known issue so far: slow battery charging, @ 0.75A, measured with a tester.
Click to expand...
Click to collapse
No prob I've PMed Santhosh to add this thread to the OP perhaps so people will find it easier. Thanks for the heads up on that, will add to post now.

It loses permission if I factory reset, so the problem persists

gabel160 said:
It loses permission if I factory reset, so the problem persists
Click to expand...
Click to collapse
Try to wipe all and do a fresh install. It ran setup wizard for me first try. Using pico gapps
Sent from my AOSP on HammerHead using Tapatalk

Is it just me or it happens with everyone that Google Now on Tap FCs the Google App??
Sent from my Nexus 5 using Tapatalk

devilsadidas said:
Try to wipe all and do a fresh install. It ran setup wizard for me first try. Using pico gapps
Sent from my AOSP on HammerHead using Tapatalk
Click to expand...
Click to collapse
Can you describe your whole installation process? Did you use 7.0 gapps?
I did it like this and it doesnt work:
1. Install the ROM
2. Reboot into ROM
3. Reflash recovery and install 7.0 micro gapps
4. reboot ROM and enable all permissions for Contact Sync, Google Framework service , Google Play Store , Google Play services and Setup Wizard
5. Factory reset in Twrp
and then I still get the problem with the wizard that the Google play services force close.

CrashOverride1995 said:
Is it just me or it happens with everyone that Google Now on Tap FCs the Google App??
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Me either.

someone knows that the process is called VARIOUS spending 41 % of battery? spends more battery than the screen
{
"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 have little bug...after enabling bluetooth for my Moto360, the Bluetooth icon is doubled on the status bar. If I disable bluetooth, one icon is disappearing but the other is still there

gabel160 said:
Can you describe your whole installation process? Did you use 7.0 gapps?
I did it like this and it doesnt work:
1. Install the ROM
2. Reboot into ROM
3. Reflash recovery and install 7.0 micro gapps
4. reboot ROM and enable all permissions for Contact Sync, Google Framework service , Google Play Store , Google Play services and Setup Wizard
5. Factory reset in Twrp
and then I still get the problem with the wizard that the Google play services force close.
Click to expand...
Click to collapse
Actually your right, i did not go through the setup wizard and it wouldn't go through it after the data reset either. i guess for that you may just have to wait till more is ironed out. sorry to mislead you

[ROM][UNOFFICIAL][microG][root][OTA][WireGuard][enchilada][9] LineageOS 16.0

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 9 (Pie), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
This build includes microG, a free and open implementation of the Google Play Services Framework. It allows applications calling proprietary Google APIs to run on AOSP-based ROMs like Replicant and LineageOS. Acting as a replacement for the closed-source Google Apps (GAPPS), it is a powerful tool to reclaim your privacy while enjoying Android core features such as Google Cloud Messaging.
It also includes WireGuard, a next generation secure VPN tunnel for the Linux kernel, with modern yet conservative cryptography and simple design principles. It is meant as a replacement for OpenVPN and for IPsec, and generally has better performance and security characteristics than both. It also is much easier to use. The whitepaper was peer reviewed for NDSS17 and the protocol itself has been formally verified. Since it lives in the kernel, it not only is very fast, but it is able to integrate in clever ways that are quite nice for battery life and overall smoothness. There are already commercial VPN providers offering services using WireGuard, and it is very easy to run your own WireGuard servers as well.
I probably won't do other types of builds unless somebody has a really terrific suggestion. These builds exists for my own convenience and I thought I'd share it with the XDA community where I've been lurking and leeching for years.
Features
Embedded root (can be enabled in Developer Settings)
Restricted (system-only) signature spoofing
microG (FakeStore, GmsCore, GsfProxy, legacy mapsv1 implementation)
Mozilla Location Services + Nominatim for network-based location
FDroid (+Privileged Extension)
WireGuard-enabled LineageOS kernel
Monthly automagical OTA updates (signed builds, https)
Reporting Bugs
I just build using the latest official LineageOS (also see this thread), wireguard patch, TheMuppets proprietary files and microG prebuilts. Report any "regular" bugs to those threads and/or Git pages unless you're sure the problem is unique to these builds.
Initial installation
NOTE: TWRP gets replaced by the stock recovery every time you install a ROM zip. Either use fastboot to boot TWRP or flash the TWRP zip file every time after you flash a ROM zip.
OnePlus firmware must be installed on your device on both A/B slots. Hence the instructions below tell you to flash OxygenOS twice.
Wipe system, data and cache.
Flash latest OxygenOS using TWRP.
Reboot to TWRP
Flash OxygenOS again using TWRP.
Reboot to TWRP
Flash the newest build using TWRP.
Reboot to TWRP.
Flash the newest build using TWRP again.
Reboot and enjoy!
OTA Updates
For OTA updates, use the built-in Updater app. Everything should JustWork(TM) without any TWRP/recovery magic.
Downloads
https://lineage.darwinkel.net/builds/full
Delta/partial updates are not supported.
I recommend Aurora Store if you want to download and install apps from Google Play.

Hi,
Many thanks!
What's the process if we want to install opengapps, magisk and custom kernel?
Will they survive to OTA?

Cygnust said:
Hi,
Many thanks!
What's the process if we want to install opengapps, magisk and custom kernel?
Will they survive to OTA?
Click to expand...
Click to collapse
This build has a free software alternative to opengapps baked-in. This ROM is probably not what you're looking for if you want to install the regular Google Play Services. No clue about Magisk or a custom kernel surviving OTA.

Thanks for the ROM (and the nice presentation!). Do you know if Magisk work properly with your ROM since it has embedded root? Is there any "interference"?

Tomatot- said:
Thanks for the ROM (and the nice presentation!). Do you know if Magisk work properly with your ROM since it has embedded root? Is there any "interference"?
Click to expand...
Click to collapse
I don't use Magisk so I'm not certain, but I don't think it should cause any problems. Do give it a try!

perhaps it's a stupid question but i can install google play to log in my games or restore the apps after install?

AndroidBolder said:
I don't use Magisk so I'm not certain, but I don't think it should cause any problems. Do give it a try!
Click to expand...
Click to collapse
I would have omitted embedded root, to be taken care of by Magisk instead, because of certains apps that just do not work on rooted phones (that's what Magisk Hide is for).
Can somebody please try how it does with embedded root disabled in Developer Settings and Magisk installed?

Master One said:
I would have omitted embedded root, to be taken care of by Magisk instead, because of certains apps that just do not work on rooted phones (that's what Magisk Hide is for).
Can somebody please try how it does with embedded root disabled in Developer Settings and Magisk installed?
Click to expand...
Click to collapse
I'm not that fond of Magisk and neither are the LineageOS devs. I don't use any apps that use SafetyNet and this works for me personally (I mainly use root for Yalp Store and WireGuard). I have, however, tested it. I enabled DroidGuard and microG's SafetyNet attestation and tested it with an app. Unfortunately, it didn't seem to pass even with root disabled in developer settings. Magisk Hide might help, though.
Toni Moon said:
perhaps it's a stupid question but i can install google play to log in my games or restore the apps after install?
Click to expand...
Click to collapse
I'm pretty sure you can install a Google Play Store APK, but you would have to disable or remove FakeStore for it to work, I think. I personally use Yalp Store to download apps from Google Play (including paid ones).
EDIT: download speeds have been fixed.

1 Question, how to get snapchat and chromecast work?

TheMellowOne said:
1 Question, how to get snapchat and chromecast work?
Click to expand...
Click to collapse
I don't use either of those apps, no clue.

Can I use blue Spark twrp?

noky76 said:
Can I use blue Spark twrp?
Click to expand...
Click to collapse
You can.

@AndroidBolder, I have done some extended research concerning VoLTE & VoWiFi today. I have found a way to explicitly enable VoLTE & VoWiFi using build.prop and both are working on LineageOS, but the problem is that it does not show the VoLTE & VoWiFi symbols in the display (which is a problem if you are abroad and can not be sure if you are indeed using VoWiFi without going to airplane).
FYI It's fully working on OOS, partly working on HAVOC OS (only VoLTE, but not VoWiFi) and not working at all on OmniROM.

@AndroidBolder, what's the easiest way to remove su from your build? Can the file addonsu-remove-15.1-arm64-signed.zip from the offical Extras repo be used (although it's for 15.1)? Or would you be so kind to create a flashable su removal for your build?

This is exactly what I've been waiting for. One question though before I flash it, how is the battery life?

Master One said:
@AndroidBolder, I have done some extended research concerning VoLTE & VoWiFi today. I have found a way to explicitly enable VoLTE & VoWiFi using build.prop and both are working on LineageOS, but the problem is that it does not show the VoLTE & VoWiFi symbols in the display (which is a problem if you are abroad and can not be sure if you are indeed using VoWiFi without going to airplane).
FYI It's fully working on OOS, partly working on HAVOC OS (only VoLTE, but not VoWiFi) and not working at all on OmniROM.
Click to expand...
Click to collapse
Sounds really interesting, but the way you're putting it, it seems somewhat unstable/unreliable. VoLTE works fine with my carrier so I have no way to test it. If multiple people can confirm it works without causing instability then I'll consider changing build.prop.
Master One said:
@AndroidBolder, what's the easiest way to remove su from your build? Can the file addonsu-remove-15.1-arm64-signed.zip from the offical Extras repo be used (although it's for 15.1)? Or would you be so kind to create a flashable su removal for your build?
Click to expand...
Click to collapse
I presume addonsu remove would work, no clue if the 15.1 version works on Pie. Did a quick search but I can't find one for LOS16. Bingo! uploaded by Luk1337, one of the LOS devs.
admiralderp said:
This is exactly what I've been waiting for. One question though before I flash it, how is the battery life?
Click to expand...
Click to collapse
Like most custom roms slightly worse than OxygenOS, but completely fine otherwise!

Noob question, need forgiveness, does google maps work with it as I've tried microg on other roms but maps were not working. That's all I need from google(maps).

nksonfire said:
Noob question, need forgiveness, does google maps work with it as I've tried microg on other roms but maps were not working. That's all I need from google(maps).
Click to expand...
Click to collapse
It works on most custom ROMs as long as you use Maps 9.82.1

Thank you a TON for providing these builds. This finally gives me a path to move off of OxygenOS. Installed, tested, everything working beautifully *including VoLTE and VoWiFi* (on U.S. T-Mobile).
TheMellowOne said:
1 Question, how to get snapchat and chromecast work?
Click to expand...
Click to collapse
I have managed a way to get at the very least Snapchat working on this ROM.
Flash as normal.
After that, flash Magisk from TWRP.
Add the *Nanodroid*, not official, microG repo to F-Droid and install the DroidGuard Helper from there. You'll have to web-search "nanodroid fdroid repo" as I cannot provide external links on this new account.
(I've not tested any of this with the official repo's DroidGuard Helper, but there are issues on microG's Github repo suggesting that SafetyNet will only pass with Nanodroid's version of DroidGuard Helper.)
Install a file manager with root capability (such as Amaze on F-Droid) and navigate to /data/app where you will find the DroidGuard Helper under "org.microg.gms.droidguard-randomstringhere". Move this folder to /system/priv-app and reboot.
Make sure SafetyNet is on in microG Settings and ensure it is using the official server (by hitting the three dots in the corner, selecting Advanced and selecting "Use official server".)
Enable Magisk Hide in Magisk Manager and enable hiding for Snapchat and DroidGuard Helper.
Try SafetyNet attestation under Magisk Manager. Hopefully both checks should pass.
Enjoy.
I did a test OTA (the current 1/30/19 version is available there, so I just downloaded and installed it again) and the only changes to be made were to re-flash TWRP and Magisk then re-install DroidGuard Helper and move it to /system/priv-app. All microG and Magisk Manager settings were retained.

As your post says, I have a really terrificant suggestion.
Why don't you try to port Sailfish Os on op6?
If you think that my suggestion is not terrificant I will understand. I would like to port it but I can't do that. For many reasons. Bye and congrats for this build. it looks like great.
Ceers

[ROM][10][ARM64][J530] crDroid v6.21 for Galaxy J5 2017 - Pro [10.08.2021]

{
"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"
}
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
Features (click here)
Screenshots in the next post.
Flashing Instructions:
Pre-installation & other downloads:
OrangeFox R11.0 (it's MANDATORY) - Download from here
AOSP Repartition script - Download from here
GApps: ARM64 > 10 > Pico - Download from here
Magisk 21.4 or newer for root - Download from here
Installation:
Enter to recovery mode and make a backup of your EFS & Modem (recommend).
Go to the Files tab and flash "Repart-AOSP10-exynos7870-20210810.zip". The recovery will auto-reboot.
Now, go to the Trash Bin and then go to the "Format data" tab, type yes and the tick to format data.
Go to the Wipe tab, select SYSTEM, CACHE, DALVIK, VENDOR, DATA and INTERNAL STORAGE, then swipe the bar.
Install the crDroidAndroid-10.0-xx-xx-v6.xx.zip
Install the GApps zip
Install Magisk (optional)
Reboot and wait. Without GApps, it boot in 15s. With Pico GApps, it boot on 1min 5s.
Done!
Download:
ROM: https://www.androidfilehost.com/?fid=7161016148664783751
Known issues:
- Frontal Flash
- Bluetooth Calls
- VoLTE (impossible on Samsung devices)
- Miracast
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/samsungexynos7870/android_kernel_samsung_exynos7870/
ROM OS Version: Android 10
ROM Kernel: Linux 3.18

IMPORTANT, PLEASE READ THIS
This is a ROM built from source and not a GSI!​
Fix Camera stretch & force close for some camera apps
You can do it editing /vendor/build.prop file using MiXplorer (you’ll need ROOT).
Search for the line “vendor.camera.hal1.packagelist”
After the = are the name of different apps. Delete one of these and put the package name of the app that you want to fix. For example, com.facebook.orca is the Facebook package name.
Per default, the ROM comes with Whatsapp, ZOOM, Snapchat and Instagram added. Maximum 4 Apps are allowed in this line and must be separated by comma ",".
If you don’t understand, open this link to see visual steps.
Fix Camera stuck
Sometimes, the camera can get inaccessible if an app was failed. If it happen, follow this:
Install this app. Open it and tap "Kill camera", then give it ROOT permissions. Done! Camera is working again.
Take in mind that if the camera is broken and you didn't do this, the audio in calls maybe not work.
GCam
This ROM can run GCam. Download a modded version for Exynos HERE. Thanks to Leonardo Estacio for his mod.
Games: this ROM works so good for gaming and can run ARM64 apps/games. If you feel lags, go to Settings > Battery > Battery Saver and performance > Performance Profile and set it to High Performance.
Video Review: if you want to see gaming performance and how this ROM are, you can watch this review video of the ROM in the J7 2016 (the ROM is the same for other Exynos7870 variants):
For close, i want to give a huge thanks to @Astrako - Without him this ROM haven't be possible <3

Changelog:
android_vendor_crDroidOTA/changelog_j7xelte.txt at 10.0 · crdroidandroid/android_vendor_crDroidOTA
OTA configuration for crDroidOTA (make your device official) - android_vendor_crDroidOTA/changelog_j7xelte.txt at 10.0 · crdroidandroid/android_vendor_crDroidOTA
github.com
===== 10-08-2021 =====
- Update to crDroid 6.21 - August security patch
- Fixed SafetyNet attestation (enable Magisk Hide if Magisk is installed)
- ROM now fits on smaller system partitions [min 2,26GB]
- Bluetooth & Bluetooth Audio fixed (j5y17lte)
===== 17-04-2021 =====
- crDroid 6.17
- Fixed Live Display
- Added Night Light
- April Security Patch
- Deleted ConfigStore hal
===== 24-01-2021 =====
- Fixed offline charging
- Added vibration intensity control
- Latest crDroid sources (v6.14 with January security patch)
- Initial j5y17lte private build for testing

Can you please give a link to AreskernelV8.0?
The most recent I've found is AresKernel-V7.0-UNIVERSAL7870.zip, and the former AresKernel-V7.0-J530X-TREBLE.zip.
Kind regards
Edit: found. Never mind.

A really fast and beautiful Rom. Unfortunately I had to find out that the SIM card is not recognized no matter what I try. I tried version 6.12 and 6.15 and I couldn't use the SIM card on either of the two Roms. Too bad.
My device is the Galaxy SM-J530F (j5y17lte)

Hello,
very nice work, thanks.
Unfortunatly it is not possible to hear Audio over bluetooth.
Any idea?
Thanks

Hey cr droid 6.18 is released in may 2021 so how can you have a cr droid 6.18 ROM from 18 April 2021

justinh99 said:
Hey cr droid 6.18 is released in may 2021 so how can you have a cr droid 6.18 ROM from 18 April 2021
Click to expand...
Click to collapse
@GonicTEAM

perfect rom, one of the few that works on my j5 j530f

Everything works perfectly except one thing wifi issue on 6.21. when connect to mobile hotspot it works well when connect to router wifi connected but internet not working I tried everything but same issue with SM-J530F.

gmkhamisani786 said:
Everything works perfectly except one thing wifi issue on 6.21. when connect to mobile hotspot it works well when connect to router wifi connected but internet not working I tried everything but same issue with SM-J530F.
Click to expand...
Click to collapse

Hi, thanks for a great rom.
I cant use my ipods, BT does connect , no audio output.
Any fix to this ?
Battery does not charge the right way.
It only goes to 70%.
What kernel is recommended ?

I flashed this ROM but my SIM Card (both) aren't detected. Baseband and IMEI are reported unknown as well. I have restored previously backed Modem and EFS partition but still no luck. How do I fix this? Please help.
Edit: I revert it to stock and my SIM is working again it seems there is issue with the ROM.

Great ROM. until now no problems, since i dont use SIM card in this one anyways.

I tried to install this ROM, but the following error occured:
My devide is J530F
What is wrong?

GonicTEAM said:
IMPORTANT, PLEASE READ THIS
This is a ROM built from source and not a GSI!​
Fix Camera stretch & force close for some camera apps
You can do it editing /vendor/build.prop file using MiXplorer (you’ll need ROOT).
Search for the line “vendor.camera.hal1.packagelist”
After the = are the name of different apps. Delete one of these and put the package name of the app that you want to fix. For example, com.facebook.orca is the Facebook package name.
Per default, the ROM comes with Whatsapp, ZOOM, Snapchat and Instagram added. Maximum 4 Apps are allowed in this line and must be separated by comma ",".
If you don’t understand, open this link to see visual steps.
Fix Camera stuck
Sometimes, the camera can get inaccessible if an app was failed. If it happen, follow this:
Install this app. Open it and tap "Kill camera", then give it ROOT permissions. Done! Camera is working again.
Take in mind that if the camera is broken and you didn't do this, the audio in calls maybe not work.
GCam
This ROM can run GCam. Download a modded version for Exynos HERE. Thanks to Leonardo Estacio for his mod.
Games: this ROM works so good for gaming and can run ARM64 apps/games. If you feel lags, go to Settings > Battery > Battery Saver and performance > Performance Profile and set it to High Performance.
Video Review: if you want to see gaming performance and how this ROM are, you can watch this review video of the ROM in the J7 2016 (the ROM is the same for other Exynos7870 variants):
For close, i want to give a huge thanks to @Astrako - Without him this ROM haven't be possible <3
Click to expand...
Click to collapse
Good morning warriors, can anyone help me? I installed this rom, it was great, but when it turns off and locks the screen it takes a while to turn on the screen, it only presses the home key several times, if anyone can help me, thank you.

I have problem with sim card in slot 2, When someone calls me they can't hear me, I can hear them for 5 seconds and then I can't hear any sounds and they can't too

Med0x said:
I have problem with sim card in slot 2, When someone calls me they can't hear me, I can hear them for 5 seconds and then I can't hear any sounds and they can't too
Click to expand...
Click to collapse
SIM2 Calling Bug work around (by kamran4malik2) :
You will face the calling issue with SIM2 every time you restart your device so to fix this issue just make a phone call from your SIM1 to any number (even if you don't have balance) then SIM2 calling issue will be fixed until you restart your phone again. ( Repeat the process every time your restart your phone )

I know I'm a little off-topic, but I don't have any more ideas.
If I understood it correctly, I need to install TWRP on my J5 to afterward install OrangeFox.
But if I see it correctly with Android 9 on an J5 there is no freaking button to get oem unlock.
So therefore I can't install twrp or anything else using odin.

[ROM][13.0][RK30SU/MI10T/MI10TP][APOLLON][OFFICIAL] crDroid v9.5 [29/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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/13.0/README.mkdn
Flashing Instructions:
Pre-installation:
1. Download and install this custom recovery (TWRP)
2. Download ROM (Go to download section bellow)
3. Download any Android 13 compatible gapps (Recomendation)
4. (Optional) Magisk 25.0 or newer for root (Download from here)
First time installation:
1. Go to TWRP.
2. Go to the advanded wipe section, wipe cache & dalvik cache.
3. Go to the install section.
4. Flash ROM file, gapps and magisk (if you wanted root).
5. Go back, go to wipe section, click on format data and type yes.
6. Reboot.
Update installation:
1. Go to TWRP.
2. Go to the advanded wipe section, wipe cache & dalvik cache.
3. Go to the install section.
4. Flash the ROM update.
5. Flash Magisk (if you previously have root).
6. Reboot.
Sources:
ROM: https://github.com/crdroidandroid
Device tree: https://github.com/crdroidandroid/android_device_xiaomi_apollon
Vendor tree: https://github.com/crdroidandroid/android_vendor_xiaomi_apollon
Kernel tree: https://github.com/crdroidandroid/android_kernel_xiaomi_sm8250/tree/13.0-apollon
Download:
ROM: https://crdroid.net/apollon
Changelog: https://crdroid.net/apollon/9#changelog
Known issues:
- Chromium based browsers scrolling not as expected.
Visit official website @ crDroid.net
crDroid apollon Telegram
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs

thanks

thanks

MartHyr said:
thanks
Click to expand...
Click to collapse
Welcome, now it's Official

Encryption ???.... flashing instructions ???

Sandeep Jakkampudi said:
Encryption ???.... flashing instructions ???
Click to expand...
Click to collapse
Use Twrp whyle
Flash fw
Flash rom
Flash gapps
Format data
Reboot system

Everything is running good, except clock/alarm apk - error, not opened (for me on my device). And battery drain is little bigger than when i was on Fluid 1.5

Axident1973 said:
Everything is running good, except clock/alarm apk - error, not opened (for me on my device). And battery drain is little bigger than when i was on Fluid 1.5
Click to expand...
Click to collapse
There's no way you can measure battery in such a short time - too many variables.
Give logs for the clock crash please

Axident1973 said:
Everything is running good, except clock/alarm apk - error, not opened (for me on my device). And battery drain is little bigger than when i was on Fluid 1.5
Click to expand...
Click to collapse
Maybe gapps issue, Which gapps?
I have faced same issue after flashing Bit Gapps Clock add-on.

RiazulRumy said:
Maybe gapps issue, Which gapps?
I have faced same issue after flashing Bit Gapps Clock add-on.
Click to expand...
Click to collapse
NikGapps 11 omni. But error, probably, is not in ROM, maybe some mistake, when i flashed. Now I try last release ForkLineage.

I tried to follow the steps provided here, used latest NikGapps Basic Arm64 and when the OS started it says "Google Play services keeps stopping".

I did an upgrade, through the updater and now stuck in a bootloop. Has anyone had sucess updating without a bootloop?
edit: I managed to update by downloading and installing it manually, but after using nikgapps, i get FC got Google PLay Services

Apparently pixel experience was discontinued for this device im considering switching to this rom, why does it require firmware(vendor) this was never a requirement for pixel experience.
Is there a way to check my current firmware version?? From TWRP or inside Pixel experience rom...

Hi,
as of now, I tested several of the ROMs listed here.
This one suits my needs & taste much better than the others, almost perfect
I did not fully test yet, but for now the only issues I found are :
- when installing the ROM, it's been blocked several times (even wiping cache/data), the install also emptied internal storage (the other ROMs did not)
- I installed NikGapps Core (with a reduced subset) : I can't change the google play services permissions for SMS access & call log. This is also the case on all the other ROMs I tested. It is preventing me to setup Signal application which does not allow manual code check as Whatsapp does. [Edit : somehow after some time I've been able to allow SMS access and then disable it]
- I did not fnd how to change the date/time size in the notif bar.
Edit 1: I installed gcam and the app crashes at every launch.
Edit2 : 25% battery used during an 8 hours night with the phone in airplane mode.
Edit3: the "recent apps" nav button takes time to show the apps

Hi,
There is an update available.
On the changelog I see "Switched to Gapps build".
Does that mean they are now including gapps to the ROM ?
If so, I'll have to look for another ROM
Too bad, that one was ok for me.

Yes Gapps including now,so no need to flash Gapps file

RiazulRumy said:
Yes Gapps including now,so no need to flash Gapps file
Click to expand...
Click to collapse
but no way to choose the set of gapps to install and it usually comes with many gapps stuff I don't want.
I'll have to move to another Rom, that one was good but ...

Gapps including

Hi,
has someone installed this new version ?
If so :
- can someone run from a windows command window or linux shell : adb shell pm list packages so that we can see what google stuff, bloatware and spyware has been added ?
- is there a power management improvement (having ~ 20% drain over 8 hours night in airplane mode)
- have you identified improvements in any way ?
Thanks

wiz.wiz said:
Hi,
has someone installed this new version ?
If so :
- can someone run from a windows command window or linux shell : adb shell pm list packages so that we can see what google stuff, bloatware and spyware has been added ?
- is there a power management improvement (having ~ 20% drain over 8 hours night in airplane mode)
- have you identified improvements in any way ?
Thanks
Click to expand...
Click to collapse
Core Gapps more details https://gitlab.com/crdroidandroid/android_vendor_gapps
Also Battery drain issue fixed,

[ROM][OFFICIAL][instantnoodlep][13] LineageOS 20

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of Android 13, which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions :
https://wiki.lineageos.org/devices/instantnoodlep
Downloads :
https://download.lineageos.org/instantnoodlep
GPL compliance :
https://github.com/LineageOS/android_kernel_oneplus_sm8250
Reporting Bugs
DO NOT Report bugs if you're running a custom kernel or you installed Xposed
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues. Any bug not reported in the bug report format below may be ignored.
Code:
What is your--
LineageOS version:
LineageOS Download url:
Gapps version:
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
Are you using--
a task killer:
a non-stock kernel:
other modifications:
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:

Thank for the new release!
Just flashed it. No issues so far.
I have just noticed that the "unlocked bootloader" message returned after flashing latest oos13 firmware. So, every time i restart my device i get the following "your device has been unlocked and can't be trusted". Just wanted to make sure that this is normal (since it was gone in oos12 firmware) and to alert other people about it.
For people who will root and need to pass safetynet the good old methods work however i was unable to find an android13 fingerprint using propsconfig. Instead i used a fingerprint for android 12 and i was able to pass all safetynet checks.

desosav said:
I have just noticed that the "unlocked bootloader" message returned after flashing latest oos13 firmware. So, every time i restart my device i get the following "your device has been unlocked and can't be trusted". Just wanted to make sure that this is normal (since it was gone in oos12 firmware) and to alert other people about it.
Click to expand...
Click to collapse
It's normal:
[Unlocked Bootloader][OOS13/OOS 13 based ROMs] How to remove bootloader unlocked message for OnePlus 8 Pro
This is a guide to remove the ugly "Your device has been unlocked and can't be trusted" or "The bootloader is unlocked and software integrity cannot be guaranteed" for OP8 Pro. This message was removed on OOS 12 which was one great thing by OP...
forum.xda-developers.com

desosav said:
For people who will root and need to pass safetynet the good old methods work however i was unable to find an android13 fingerprint using propsconfig. Instead i used a fingerprint for android 12 and i was able to pass all safetynet checks.
Click to expand...
Click to collapse
I want to ask about this
I've been using magisk, and have been unable to pass safety check on the stock ROM and thought Magisk stopped trying to beat safety net, so I stopped trying also.
It seems you have resolved this.
Can I ask you for direction on how to do this myself after I move to lineageos?
I don't necessarily need full instructions and would appreciate any guidance you can offer me.
Thanks

JustinChase said:
I want to ask about this
I've been using magisk, and have been unable to pass safety check on the stock ROM and thought Magisk stopped trying to beat safety net, so I stopped trying also.
It seems you have resolved this.
Can I ask you for direction on how to do this myself after I move to lineageos?
I don't necessarily need full instructions and would appreciate any guidance you can offer me.
Thanks
Click to expand...
Click to collapse
I haven't tried on 20 yet, but:
root with magisk then add the following modules:
propsconfig and change the fingerprint to a pixel 6 pro
kdragons safetynet patch
Make sure play store and other services are on the magisk deny list.
There are more detailed instructions in various threads specific to each step, but this is the gist of it.

No issues with following the lineage os version upgrade procedure to keep from needing to format data? The upgrade procedure didn't have about needing oos13 firmware beforehand, so I wasn't sure if it'd make a difference.
-update-
No issues yet after following the upgrade procedure without flashing oos13 stock fw first.
I still have some weird issue where it makes me have to sign in to the T-Mobile network. I think it's because I had a Verizon sim in sim slot 2 at one point.. it'll probably require a network settings reset to fix..

Is the 48MP sensor on the camera still locked? Just wondering considering the changes with the camera app and API with LOS 20.

d3viou5 said:
I haven't tried on 20 yet, but:
root with magisk then add the following modules:
propsconfig and change the fingerprint to a pixel 6 pro
kdragons safetynet patch
Make sure play store and other services are on the magisk deny list.
There are more detailed instructions in various threads specific to each step, but this is the gist of it.
Click to expand...
Click to collapse
hi, @d3viou5 how did you root?
I've updated from LOS19 to LOS20, following the official procedure.
Now. I've
- Installed Magisk (tried both canary and stable)
- extracted the boot.img with Payloader-Dumper-Go
- patched boot.img with Magisk
- flashed patched boot.img, system is NOT rooted
- tried to boot (not flash) the patched boot.img, again system NOT rooted
I'm missing something?
thx!

Installed manually coming from LOS 19.1. Did not update firmware, but did the DTBO and VBMETA flashing to be on the safe side. No issues and running very smooth so far. New camera app gets good pics with good lighting. Low light is 2014 quality.

miramax001 said:
hi, @d3viou5 how did you root?
I've updated from LOS19 to LOS20, following the official procedure.
Now. I've
- Installed Magisk (tried both canary and stable)
- extracted the boot.img with Payloader-Dumper-Go
- patched boot.img with Magisk
- flashed patched boot.img, system is NOT rooted
- tried to boot (not flash) the patched boot.img, again system NOT rooted
I'm missing something?
thx!
Click to expand...
Click to collapse
If you go into recovery, sideload magisk apk. That's what I did with 25.2 and it's rooted.

mattgyver said:
If you go into recovery, sideload magisk apk. That's what I did with 25.2 and it's rooted.
Click to expand...
Click to collapse
Thanks @mattgyver
The problem WAS the WORK profile (with SHELTER).
I had to remove my WORK PROFILE (from SETTINGS->ACCOUNT)
And then, sideload magisk.apk (renamed as magisk.zip) and now I'm rooted again.
ThX!

roaringcrown said:
Installed manually coming from LOS 19.1. Did not update firmware, but did the DTBO and VBMETA flashing to be on the safe side. No issues and running very smooth so far. New camera app gets good pics with good lighting. Low light is 2014 quality.
Click to expand...
Click to collapse
Hi, I'm guessing you "dirty flashed" LOS 20 over 19.1 through the LOS recovery?
I was hoping to avoid factory resetting/formatting...
Thanks!

Kuronosu said:
Hi, I'm guessing you "dirty flashed" LOS 20 over 19.1 through the LOS recovery?
I was hoping to avoid factory resetting/formatting...
Thanks!
Click to expand...
Click to collapse
yes, just follow the official guide
Upgrade LineageOS on instantnoodlep | LineageOS Wiki
wiki.lineageos.org

How to install the rom with twrp? i.m using oneplus 8 pro global varient ty

@LuK1337
Thanks for the great work!
I'm currently trying to build LOS 20 myself and as far as I can tell everything compiled properly.
However in the last steps of the build I receive the following error:
Bash:
The following HALs in device manifest are not declared in FCM <= level 4:
[email protected]::IEffectsFactory/default
[email protected]::IDevicesFactory/default
[email protected]::IBootControl/default
[email protected]::IMediaCasService/default
[email protected]::ICryptoFactory/wfdhdcp
[email protected]::ICryptoFactory/widevine
[email protected]::IDrmFactory/wfdhdcp
[email protected]::IDrmFactory/widevine
[email protected]::ICryptoFactory/clearkey
[email protected]::IDrmFactory/clearkey
[email protected]::IHealth/default
[email protected]::IDevice/qti-default
[email protected]::IDevice/qti-dsp
andro[email protected]::IDevice/qti-gpu
[email protected]::IDevice/qti-hta
android.hardware.power.IPower/default (@1)
[email protected]::IRadio/slot1
[email protected]::IRadio/slot2
[email protected]::ISecureElement/SIM1
[email protected]::ISecureElement/SIM2
[email protected]::ISecureElement/eSE1
[email protected]::ISoundTriggerHw/default
[email protected]::IUsb/default
android.hardware.vibrator.IVibrator/default (@1)
android.hardware.wifi.hostapd.IHostapd/default (@1)
android.hardware.wifi.supplicant.ISupplicant/default (@1)
[email protected]::IWifi/default
INCOMPATIBLE
stderr:ERROR: files are incompatible: Runtime info and framework compatibility matrix are incompatible: No compatible kernel requirement found (kernel FCM version = 5).
For kernel requirements at matrix level 5, For config CONFIG_DEBUG_FS, value = y but required n
For kernel requirements at matrix level 6, For config CONFIG_ANDROID_PARANOID_NETWORK, value = y but required n
: Success
Any idea why this is happening?

sToRm1nG said:
@LuK1337
Thanks for the great work!
I'm currently trying to build LOS 20 myself and as far as I can tell everything compiled properly.
However in the last steps of the build I receive the following error:
{code}
The following HALs in device manifest are not declared in FCM <= level 4:
[email protected]::IEffectsFactory/default
[email protected]::IDevicesFactory/default
[email protected]::IBootControl/default
[email protected]::IMediaCasService/default
[email protected]::ICryptoFactory/wfdhdcp
[email protected]::ICryptoFactory/widevine
[email protected]::IDrmFactory/wfdhdcp
[email protected]::IDrmFactory/widevine
[email protected]::ICryptoFactory/clearkey
[email protected]::IDrmFactory/clearkey
[email protected]::IHealth/default
[email protected]::IDevice/qti-default
[email protected]::IDevice/qti-dsp
[email protected]::IDevice/qti-gpu
[email protected]::IDevice/qti-hta
android.hardware.power.IPower/default (@1)
[email protected]::IRadio/slot1
[email protected]::IRadio/slot2
[email protected]::ISecureElement/SIM1
[email protected]::ISecureElement/SIM2
[email protected]::ISecureElement/eSE1
[email protected]::ISoundTriggerHw/default
[email protected]::IUsb/default
android.hardware.vibrator.IVibrator/default (@1)
android.hardware.wifi.hostapd.IHostapd/default (@1)
android.hardware.wifi.supplicant.ISupplicant/default (@1)
[email protected]::IWifi/default
INCOMPATIBLE
stderr:ERROR: files are incompatible: Runtime info and framework compatibility matrix are incompatible: No compatible kernel requirement found (kernel FCM version = 5).
For kernel requirements at matrix level 5, For config CONFIG_DEBUG_FS, value = y but required n
For kernel requirements at matrix level 6, For config CONFIG_ANDROID_PARANOID_NETWORK, value = y but required n
: Success
{code}
Any idea why this is happening?
Click to expand...
Click to collapse
You seem to be doing something wrong, e.g. building -user instead of -userdebug or something else.

LuK1337 said:
You seem to be doing something wrong, e.g. building -user instead of -userdebug or something else.
Click to expand...
Click to collapse
Yeah, you're right... I was building user isntead of userdebug.

Thank you so so much for this! ♥ It works like a charm and it's so so much better than OxygenOS 13 (I can minimize notifications omg!!!1!).
The only thing I personally am missing, is the classic LOS 18 style quick shortcuts in the pull-down notification menu. I always used 1 row with 6 circles, but since LOS 19 it changed to 2 rows with only 4 large shortcuts. But oh well, I guess you can't have everything!
Thank you for maintaining this device @LuK1337 !

@LuK1337
Thank you for your great work.
Not only for your work for this great Oneplus 8 Pro device, but also for other devices before!
You are really one of the most important and best device maintainers.

haxorinjector said:
How to install the rom with twrp? i.m using oneplus 8 pro global varient ty
Click to expand...
Click to collapse
TWRP is only available for A11 and lower. It does not work on A12 or A13.