ROM[OFFICIAL][enchilada][10.0]**crDroid**[V6.16]

Search This thread

tomasz-c

Member
Sep 25, 2020
12
1
Hey sorry for only replying now. I'll put it on my to-do list for the next update and try my best to add it then. :)

Thank you! :)
Maybe there would still be a chance to return the default gallery application? As for me, it was better, but it was replaced by the Oneplus application. I think it could have been both, if someone doesn't need it, maybe turn it off.
 

MaWalla99

Member
Jan 21, 2018
31
42
Berlin
@MaWalla99
It seems that there are no new things in this update. Maybe you can add them in the next update? :)
Let me remind you that this is DC Dimming and the default gallery application.
I remember, but crDroid 6 is more or less end-of-life now and I just wanted to make the december security patch available. Now I'll try to focus my Energy on getting crDroid 7 running somewhat usable on our devices. Then I can consider DC Dimming. As for the Gallery, idk yet. I'm fairly happy with the OOS one. But I'd probably do a poll in the Telegram group when its time.
 

tomasz-c

Member
Sep 25, 2020
12
1
I remember, but crDroid 6 is more or less end-of-life now and I just wanted to make the december security patch available. Now I'll try to focus my Energy on getting crDroid 7 running somewhat usable on our devices. Then I can consider DC Dimming. As for the Gallery, idk yet. I'm fairly happy with the OOS one. But I'd probably do a poll in the Telegram group when its time.

I understand, thank you for the information. In that case I am waiting patiently for crDroid 7.

In my opinion, the main advantage of the built-in gallery is Open Source. In case of OOS Gallery you never know what's inside, for people who don't install gapps it's important.
Providing the default gallery application would be consistent with other default applications (dialer, calendar, contacts, messages).
There is another difference: OOS Gallery can be installed by anyone from Play or apk, and the default gallery application is probably not available as apk?
(I took the liberty of giving an opinion here because I don't use the telegram)
 

MaWalla99

Member
Jan 21, 2018
31
42
Berlin
I understand, thank you for the information. In that case I am waiting patiently for crDroid 7.

In my opinion, the main advantage of the built-in gallery is Open Source. In case of OOS Gallery you never know what's inside, for people who don't install gapps it's important.
Providing the default gallery application would be consistent with other default applications (dialer, calendar, contacts, messages).
There is another difference: OOS Gallery can be installed by anyone from Play or apk, and the default gallery application is probably not available as apk?
(I took the liberty of giving an opinion here because I don't use the telegram)

crDroid 7 is there, DC Dimming is still not there but I haven't forgotten it. It's just that I wanted to get the release out for now, so we have an up-to-date crDroid, then the features will come, so stay tuned!
 
Okay, so it wasn't just me; I could've sworn that DC Dimming wasn't working on crDroid6 without going to a custom kernel and fooling around with things. Anyway, hi!

My name's Jordan, all I wanted was a custom ROM for my wife's Pixel 3a that had unlinked notification & ringtone volume, but it wasn't available at the time, so I tried to see if I could get one to compile, but I couldn't take her phone away, so I had to practice on my OnePlus6, and accidentally practiced a lot and @MaWalla99 wanted to stop maintaining and now I've got USERS. Ugh.

Anyway.

I'm mostly working on crDroid7 for enchilada/fajita right now, but as long as the crDroid devs keep merging Android Security Bulletin patches for 6, I'll keep the builds coming using the existing device trees. It is extremely unlikely that I'll do any modifications to try and add DC dimming or anything (as far as I can tell, it requires kernel nodes we don't HAVE in the stock crDroid/LineageOS kernel, because luk1337 didn't add them when the OOS Q source drop came out, and he's got lots of better things to do in life than go back a year and a half to try and rebase a whole freaking kernel tree for 3-year-old devices while he's got sm8150 & sm8250 to try and work all of OnePlus' bugs out of) to the older device trees, but you never know.

There are days where I get so sick of Google's mess in A11 that I'm about ready to jump ship back to only maintaining crDroid6 and just do blind builds of 7 with vanilla LineageOS device trees (so no fancy features) until after there's been an A11 OxygenOS source drop and there are real updated DTs & kernels to build with, instead of the various stages of "making it up as we go along" that we've all dealt with.
 
Last edited:
I got PM'd some questions, but I'm going to paste the questions & my answers here for the benefit of the entire class:
_____

Hello,

Sorry if I hope you don't mind i'm contacting you through private message ...

I'm looking at CrDroid with interest for my OnePlus6 (actually running OmniRom with microG)

But I wonder ... Should I go direct for CrDroid 7 or for CrDroid 6 and wait for CrDroid 7 to be more "stable" (I guess when OnePlus will release Oxygen11 for OP6 ans Vendor will be available).

Is there's still OTA for CrDroid 6 ? Security Patch ?

If I go for CrDroid 6 will it be easy to upgrade for CrDroid 7 or will I have to do a clean install ?

By advance, thanks for your answers !

Regards,
I don't mind, although I'll copy & paste this info into the crDroid6 thread so everyone can learn the answers and maybe it'll be useful information to help someone else make decisions as well.

Honestly, there are days where I have no idea why I'm bothering with trying to bring up crDroid7 (Android 11) for our devices. It's a collossal pain in the ass. Things that used to work because they were part of the framework (i.e. available due to the actual crDroid ROM devs) had to get removed because it doesn't work correctly in 11 any longer. And the kernel itself doesn't support a lot of the pieces because the official LineageOS maintainer didn't redo years' worth of work to re-do modifications to the LOS kernel when the OxygenOS Q kernel sources dropped -- and I don't blame him! he's busy with four or five newer OnePlus devices to maintain and fix all the crappy stuff in the OnePlus kernel sources for those devices now; that's a boatload of work. At least sm8250 (OP8 series) even HAS Android 11 source available; OP7 wouldn't compile and they pulled the A11 beta program; I don't think we'll be seeing an OOS A11 release for enchilada/fajita for a loooong time yet.

There are no official lineage-18.1 based device trees that actually compile, without going to their gerrit and pulling unmerged bringup hacks that aren't official yet, and a lot of it is just beyond my ability. I don't know much about fixing a broken DT or converting between LineageOS & Omni & AOSP conventions to make things work or changing HALs or so forth.

None of that is to mention the absolute flaming pile of poop that Google itself is responsible for forcing on everyone in Android 11, in forcing Scoped Storage and Storage Access Framework on us. Even on a Pixel with first-party tools, file access is dog slow, and no real security benefits. File managers like Mixplorer and backup/restore solutions like Titanium Backup and SwiftBackup are all boned because even with root, they aren't able to restore files to another app's private /sdcard/Android/data/ dir in a way that's readable by the app you're trying to restore data for.

There are days where I almost talk myself into giving up on working on A11 builds, and just doing small tweaks & merging monthly security updates for crDroid6 (Android 10). I'm not a dev, this is never going to be on the level of PiXeN-OS unless drpradsms decides to take over maintaining for me (fat chance).
So we have fewer working features on crDroid7 than we did on crDroid6 right now, and all the challenges of Android 11 file access shenanigans.

That said, it's still a stable daily driver, battery life is good, and hopefully things will improve slowly but surely.

Alternatively, the crDroid devs are still merging monthly Android Security Bulletins into the crDroid6 trees, and I'm doing blind builds of those (not gonna flash back & forth to test them both, sorry) and releasing them with the device trees just as they were when Max stopped maintaining (so inline twrp, but it's older, but it works).

I honestly don't know how well it works to dirty flash update from crDroid6 to 7. Someone said it worked pretty well for them, but you're likely to want to clean flash at that point anyway just to be on the safe side. I mean, it's a major Android version change. At the minimum you'd want to still do all the work to back up your important data, remove any PIN/pattern/fingerprints (so Device Protection gets disabled), make sure you're on the latest underlying OOS (10.3.9 as of this writing) & TWRP & magisk (so dirty flash latest crDroid6 with all that), before trying to make the jump. And it still might not work well.

crDroid6 isn't being actively SUPPORTED per se, like; I'd be relying on users to make bug reports & test builds, and I have very little free time to work on crDroid7 as it is. But it's also relatively mature, the DTs work there, and I'll keep building it as long as they keep merging monthly security updates. You might even get a couple surprise new features ROM-side as the devs work on things.

It's pretty solid either way, and one of the only ROMs for enchilada/fajita that actively supports microG usage (yes to package signature spoofing, no to built-in GApps) with halfway-decent customization & functionality. If it helps with your decision-making, I should be releasing an April update within a week that, I'm hoping, will bring back the DeviceSettings functionality ("OnePlus Settings") we've been missing for months & months now in crDroid7.

Cheers,
Jordan ("Terminator J on the wheels of steel!")
 

bre75

Senior Member
Jun 30, 2017
68
4
Thx a lot for @Terminator.J for all your answers and details.

I'd like to switch to CrDroid 6 with microG and with Bromite System Webview.

Except the fact I need to refresh my mind on how to flash both slots and not scared myself as last time i did it, what would be the best practice to do this ? Flash Nanodroid microg + Nanodroid Bromite ? Or something else ?

Thanks for any feedback/answers!

Regards,
 
Thx a lot for @Terminator.J for all your answers and details.

I'd like to switch to CrDroid 6 with microG and with Bromite System Webview.

Except the fact I need to refresh my mind on how to flash both slots and not scared myself as last time i did it, what would be the best practice to do this ? Flash Nanodroid microg + Nanodroid Bromite ? Or something else ?

Thanks for any feedback/answers!

Regards,
I honestly don't remember; make sure you've got latest OOS official full OTA zip (for latest firmware in both slots), latest official TWRP installer, latest magisk installer (I use canary but release or beta should be fine if they're v22.1 or higher), and then yeah... essentially you're going to remove any pin/pattern/fingerprint/face unlock and go back to swipe to unlock, reboot bootloader, boot into TWRP via USB cable & `fastboot boot path-to-twrp-filename.img` (replace that last part with the actual path/name of the official TWRP bootable image you downloaded from twrp.me), wipe data (not format), flash OOS + crDroid + TWRP (remember you can "select additional zips" when installing), reboot recovery, flash OOS + crDroid + TWRP, reboot recovery, flash magisk + nanodroid microg + nanodroid bromite, wipe dalvik, and finally reboot system.

I know it takes FOREVERRRRR to flash the official OOS OTA zip; you only need to do that once per OxygenOS update thankfully. From then on, until the next OOS update gets released, just do the crdroid.zip + twrp.zip for the first part, reboot recovery, flash magisk+microg/nanodroid/gapps/whatever you're using, wipe dalvik, reboot system to do updates.
 
Hey folks, just wanted to let you know I haven't forgotten about crDroid 6. I'm working on a rebase to updated lineage-17.1 trees/kernel source to tidy up some things, and I'll update the OP soon. I have a WIP build of 6.17 with April security update I can push as official if you want for now, should work pretty well, and includes updated TWRP inline.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    I got PM'd some questions, but I'm going to paste the questions & my answers here for the benefit of the entire class:
    _____

    Hello,

    Sorry if I hope you don't mind i'm contacting you through private message ...

    I'm looking at CrDroid with interest for my OnePlus6 (actually running OmniRom with microG)

    But I wonder ... Should I go direct for CrDroid 7 or for CrDroid 6 and wait for CrDroid 7 to be more "stable" (I guess when OnePlus will release Oxygen11 for OP6 ans Vendor will be available).

    Is there's still OTA for CrDroid 6 ? Security Patch ?

    If I go for CrDroid 6 will it be easy to upgrade for CrDroid 7 or will I have to do a clean install ?

    By advance, thanks for your answers !

    Regards,
    I don't mind, although I'll copy & paste this info into the crDroid6 thread so everyone can learn the answers and maybe it'll be useful information to help someone else make decisions as well.

    Honestly, there are days where I have no idea why I'm bothering with trying to bring up crDroid7 (Android 11) for our devices. It's a collossal pain in the ass. Things that used to work because they were part of the framework (i.e. available due to the actual crDroid ROM devs) had to get removed because it doesn't work correctly in 11 any longer. And the kernel itself doesn't support a lot of the pieces because the official LineageOS maintainer didn't redo years' worth of work to re-do modifications to the LOS kernel when the OxygenOS Q kernel sources dropped -- and I don't blame him! he's busy with four or five newer OnePlus devices to maintain and fix all the crappy stuff in the OnePlus kernel sources for those devices now; that's a boatload of work. At least sm8250 (OP8 series) even HAS Android 11 source available; OP7 wouldn't compile and they pulled the A11 beta program; I don't think we'll be seeing an OOS A11 release for enchilada/fajita for a loooong time yet.

    There are no official lineage-18.1 based device trees that actually compile, without going to their gerrit and pulling unmerged bringup hacks that aren't official yet, and a lot of it is just beyond my ability. I don't know much about fixing a broken DT or converting between LineageOS & Omni & AOSP conventions to make things work or changing HALs or so forth.

    None of that is to mention the absolute flaming pile of poop that Google itself is responsible for forcing on everyone in Android 11, in forcing Scoped Storage and Storage Access Framework on us. Even on a Pixel with first-party tools, file access is dog slow, and no real security benefits. File managers like Mixplorer and backup/restore solutions like Titanium Backup and SwiftBackup are all boned because even with root, they aren't able to restore files to another app's private /sdcard/Android/data/ dir in a way that's readable by the app you're trying to restore data for.

    There are days where I almost talk myself into giving up on working on A11 builds, and just doing small tweaks & merging monthly security updates for crDroid6 (Android 10). I'm not a dev, this is never going to be on the level of PiXeN-OS unless drpradsms decides to take over maintaining for me (fat chance).
    So we have fewer working features on crDroid7 than we did on crDroid6 right now, and all the challenges of Android 11 file access shenanigans.

    That said, it's still a stable daily driver, battery life is good, and hopefully things will improve slowly but surely.

    Alternatively, the crDroid devs are still merging monthly Android Security Bulletins into the crDroid6 trees, and I'm doing blind builds of those (not gonna flash back & forth to test them both, sorry) and releasing them with the device trees just as they were when Max stopped maintaining (so inline twrp, but it's older, but it works).

    I honestly don't know how well it works to dirty flash update from crDroid6 to 7. Someone said it worked pretty well for them, but you're likely to want to clean flash at that point anyway just to be on the safe side. I mean, it's a major Android version change. At the minimum you'd want to still do all the work to back up your important data, remove any PIN/pattern/fingerprints (so Device Protection gets disabled), make sure you're on the latest underlying OOS (10.3.9 as of this writing) & TWRP & magisk (so dirty flash latest crDroid6 with all that), before trying to make the jump. And it still might not work well.

    crDroid6 isn't being actively SUPPORTED per se, like; I'd be relying on users to make bug reports & test builds, and I have very little free time to work on crDroid7 as it is. But it's also relatively mature, the DTs work there, and I'll keep building it as long as they keep merging monthly security updates. You might even get a couple surprise new features ROM-side as the devs work on things.

    It's pretty solid either way, and one of the only ROMs for enchilada/fajita that actively supports microG usage (yes to package signature spoofing, no to built-in GApps) with halfway-decent customization & functionality. If it helps with your decision-making, I should be releasing an April update within a week that, I'm hoping, will bring back the DeviceSettings functionality ("OnePlus Settings") we've been missing for months & months now in crDroid7.

    Cheers,
    Jordan ("Terminator J on the wheels of steel!")
  • 34
    BE3pE0l.png




    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



    First time installing crDroid to your Op6, or coming from another ROM:
    - Be on the latest stable firmware
    - Flash it to both slots
    - Disable your screenlocks
    - Make sure you're running latest TWRP
    - Copy GApps and crDroid zip to your internal storage
    - Boot into Recovery
    - Wipe data and dalvik
    - Flash crDroid zip
    - Flash TWRP zip
    - Reboot to recovery
    - Flash GApps zip
    - Reboot system
    - Setup Rom
    - Reboot to recovery
    - Flash Magisk zip
    - Reboot system


    Don't expect any support if you:
    - are not running stock crDroid-kernel
    - have installed any mods such as Xposed!
    - have modified system files


    DONATE


    crDroid Website


    Telegram Oneplus6/6t group

    Source Code Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sdm845

    XDA:DevDB Information
    ROM[OFFICIAL][enchilada][10.0]**crDroid**[V6.13], ROM for the OnePlus 6

    Contributors
    MaWalla99, neobuddy89, gwolfu
    Source Code: https://github.com/crdroidandroid

    ROM OS Version: Android 10
    ROM Kernel: Linux 4.x
    Based On: LOS

    Version Information
    Status:
    Testing
    Current Stable Version: 6.13
    Stable Release Date: 2020-12-18

    Created 2020-10-07
    Last Updated 2020-12-18
    14
    new build up !
    12
    a new build is up , read the OP for instructions
    12
    a new v6 build is up !
    october security and statusbar padding are new
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone