yashsingh1/xdaforums huggingface dataset:
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Yeah, eventually. I got a little help with actually figuring out which kernel commits needed reverting to see if it takes care of the issue from bananafunction, and it's just been a super-busy week.

Oh, and I also ended up moving to a new build box...

View attachment 5878431
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
View attachment 5878433
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
There we go, April 1st 9.2 hotfix builds pushed to OTA!

The "April Fools" joke in the kernel string is ... that it wasn't a joke. I really did compile these builds on my new Steam Deck as a CPU & i/o benchmark test before I re-paste it with honeywell ptm7950 and swap the 64GB m.2 eMMC for a 1TB Sabrent Rocket pcie 4.0 x4 NVME m.2230 drive. I'll keep y'all posted how it does on the "after" builds :D

Finally time to re-sync sources now that QPR2 is merged and we seem to be back to mostly feature-complete 9.3 releases happening again. Time to start 9.3 test builds for enchilada & fajita, whoop whoop!
[OnePlus 6 & 6T Cross Device Development] weny_i:
Just now im new member, btw, i try installation via TWRP, sound good dosent work :D. I remember using TWRP on nexus 4 i thought its simlar but no. Coming from stock. Anyway, little help from indian guy YT and i got it :D
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Um, okay; glad you've got it...

But there are good reasons I wrote out all the installation steps, and didn't include TWRP in them.

Hope it works well for you, friend.
[OnePlus 6 & 6T Cross Device Development] alienwolf426:
Hi,

I'm coming for a very old version of crDroid (back from Android 9). So, i'm trying to update the firmware. I installed adb/fastboot and the drivers and used fastboot to boot into the crDroid recovery. Followed the steps to get into the crDroid fastboot and at that point, my computer can't find the device. If i go back to cdDroid recovery i can see my device with adb devices, but when i go under advanced > Enter Fastboot, I get nothing.

And i checked my device manager and it just says "OnePlus A6003" with an exclamation point. I tried to update the drivers from where i installed the drivers earlier and it says no drivers found.

Anyone have any tips for this?

Edit: Nvm, i found these drivers and these work with the crDroid fastboot. https://xdaforums.com/t/guide-fix-f...all-official-driver-in-windows-10-11.4396501/

Edit 2: really wierd. After updating the firmware and the fastboot from eom fastboot doesn't work, so had to switch to the other drivers. I don't understand, but whatever. now it's installing the ROM.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Not gonna lie, I think I just lucked out with having Windows Update able to find the correct drivers most of the time. 😅

Or the last time I bothered "just to make sure", it was after doing MSMTool so I was still using an old build of TWRP like 3.4.x or 3.5.2 that worked with OOS 10.3.x and just installed the OOS 11.1.2.2 zip twice (once per slot) to get back to "now I can put the new stuff back on it".

I think it's something like the Google universal ADB drivers after making the jump to source-built vendor because it's a newer version of bootctl and usb-dwc or something like that. *handwaves*

This is definitely an area where there's not much of a bridge for getting from the ancient pinned guides to the current state of Android 12+ source-built vendor ROMs, with regards to necessary driver versions at each step of the way.

Glad you got it!
[OnePlus 6 & 6T Cross Device Development] alienwolf426:
Also, the problem might have been windows 11. last time, i did the original oneplus 6 rooting and roming, it was back in windows 8 and driver installation was easier, or rather less secure.
[OnePlus 6 & 6T Cross Device Development] prgrr:
Does the ROM come with Pixel Launcher? Does it include the Pocket Mode feature?
[OnePlus 6 & 6T Cross Device Development] gecko8k:
It ships with a launcher called CrDroid Home. It may be build upon Pixel Launcher, maybe others know more.

If you by Pocket Mode mean that the phone checks if it is in a pocket then yes, that feature is here. If you mean the phone pulses notification upon removal from a pocket then also yes.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Our built-in launcher "crDroid Home" is based on the AOSP "Launcher3" source.

The Google Pixel-specific source code is not available; ROMs and Google Apps/addons that include "Pixel Launcher" are repackaging prebuilt APKs extracted from Pixel system images.

Installing Pixel Launcher in a way that overwrites the stock crDroid launcher is not recommended; but it does work to install it as an addon with NikGapps (needs to be installed as part of clean flash I thnk) in a way that doesn't overwrite existing launcher.

The incompatibility has been resolved, but the color theming overlays might not look good with it, if you use the QuickSearchBox at the bottom of the dock a lot.
[OnePlus 6 & 6T Cross Device Development] cmert:
is there any news for v9.3 or newer versiyon?
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Yeah.

Pushing now.

I've been busy.

I will continue to be busy.

QPR2 took a long time, which means it takes me even longer to try and iron out device-specific kinks when there are big under-the-hood changes to Android itself like that.
[OnePlus 6 & 6T Cross Device Development] GheoLei:
Switched to crDroid today, thanks for maintaining the rom :)
[OnePlus 6 & 6T Cross Device Development] dhemker:
Deactivated apps still re-appear after latest OTA. Saw sth. about that in the changelog.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Hidden & protected apps maintain status after rebooting now. Try setting it via Settings > Security, if doing it from the crDroid Home (launcher) settings doesn't work for you.

It's fixed as of 9.3, honest.

If that's not working for you, I would respectfully recommend clearing some Settings app storage or possibly re-flashing ROM & GApps via recovery.

If you flashed an addon installer zip that replaced crDroid Home (Launcher3) with a third-party launcher like PixelLauncher, then I can't help with that.

But even in that case, the framework-based protection should require authentication before allowing you to launch it even from third-party launchers.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
I realize that "BlackScreenOS" has kind of made a comeback for fajita (6T) users as of 9.3.

I think I finally have that fixed for good again, and am working on release candidate builds for 9.4.

...

Of course, the dev team already merged the May ASB so now crDroid sources are updated to 9.5, so ... even if I can't fix it, I might just push 9.4 anyway and then sync 9.5 sources to keep working on it. 😅

¡Feliz Cinco de Mayo! ¡Viva México!
[OnePlus 6 & 6T Cross Device Development] ajmi3:
Hi @Terminator.J

My device is OnePlus 6 on latest 9.3 release.

There seems to be white areas visible on top left and right of lock screen for any wallpaper.

It seems the curve on top left and right is not perfectly aligned to the curve in the display. This is new in 9.3 and I did not face this on prior builds.

The image below is a screenshot of the lock screen.

View attachment 5906369
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Ah yes.

You can fix that by not using light theme. 😜

*sighs*

I'll make sure it's fixed in 9.4, ugh.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Well that took an extra two weeks, but hey.

Pushed 9.4 to OTA last night, including fixes for the white corners peeking out from under the curve on enchilada.

The white corners will still be there in screenshots, because... reasons.

Look, there are kind of two ways to get to a similar place with rounded corners & a notch & status bar spacing.

I kinda hopped over to a different one than what LineageOS uses, because it played better with burn-in protection a few months ago (that's what was up with stuff wandering around), while setting "rounded_corner_radius[_top|_bottom]" plus "rounded_corner_content_padding" gets ignored more?

I dunno, it's a moving target and I'm tired of it.

I need to sort out my dimens overlay commits and then try A/B testing again to see if it's even necessary still on A13 now. Heh, "need to". I need to stop having to worry about little stuff like that, and get on with life.

ANYWAY! crDroid 9.4 pushed to OTA, second post has updated changelog (and link to 01 May updated release of my custom config NikGapps, recommended package going forward).
[OnePlus 6 & 6T Cross Device Development] ajmi3:
This new update 9.4 has been really good. It is visibly a lot smoother, no stutters and the overall experience is great. Thanks!
[OnePlus 6 & 6T Cross Device Development] JonesL:
Percentage for the battery has gone from the expanded notifications
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
I believe you!

Lots of layout changes thanks to Google/AOSP in Android 13 as QPR merges happen, which break old customizations we used to be able to apply.

#changesabovemypaygrade
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
... Now was that while plugged in and charging? Or just in general?
[OnePlus 6 & 6T Cross Device Development] JonesL:
The percentage will stay on screen whilst charging, but will disappear when the charger is removed. It still displays the battery level in the settings.
[OnePlus 6 & 6T Cross Device Development] faabiano7:
is it not possible to disable blur? like when unlocking the screen?
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Settings > System > Developer Options > Toggle off "Allow window-level blurs".
[OnePlus 6 & 6T Cross Device Development] gecko8k:
Hi Terminator.J

Thanks for creating CrDroid, it is a really great rom and my go to the last couple of years.

Two features you could consider to implement, both were present in CrDroid 8/A12 which may/may not make them easier to implement.

Swipe statusbar to change brightness. This is such a nice and easy to use feature where you don't have to pull down the Quick Settings to change brightness.

Battery estimates. It's just nice to know for how long the battery will probably last.

Thanks for your work no matter what.
[OnePlus 6 & 6T Cross Device Development] gecko8k:
I think I found a bug where Quick Settings transparency does not function as intended on the lock screen. I am on a OnePlus 6 with CrDroid 9.4.

Under CrDroid Setting > Quick Settings you are able to set the background transparency. I put mine at 60 % which looks like this:

View attachment 5925793

Now, when I pull down the Quick Settings from the lock screen it looks like this with a grey background instead of a transparent background:

View attachment 5925795

If I set background transparency to 1 % the background is black and if I set it to 100 % the background is white:

View attachment 5925797View attachment 5925799

Could you maybe look into this and see if the background could become transparent as I guess it is intended?
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Features like that are usually framework-dependent and worked on by the actual ROM dev team -- I'm a device maintainer, not part of the core team.

Sometimes I try to help, when possible, to bring back missing things (and often find out WHY they were removed in the process). But I'm not actually a software developer by trade/experience, so it's frequently a lot of hair-pulling and interesting intellectual exercises, without actually being able to come up with something that will work perfectly for everyone.

I can ask, but right now I don't have a whole lot of time to work on such things myself, since summer is usually crazy busy in my life. Work on features rather than just security updates is going to be severely limited until late September, I'm afraid.

That said, I'll see what I can do. Thanks for sticking around! :D
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
I think the background transparency is fixed in 9.5, which I'm about to push to OTA tonight.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Working on bringing that back in next month's release (9.6, June ASB presumably).
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Meanwhile, official 9.5 OTA update is out! Check out those release notes in Post #2, as well as updated custom-config NikGapps based on 31 May releases.

If anyone feels like they're bored of being stable, check out the TG channel for a highly experimental kernel build including OC GPU frequencies, KernelSU support, and pointless extra TCP congestion algorithms for that circa-2019 gaming kernel flavor!
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Oh yeah, almost forgot to mention:

While we wait for features to get merged back into crDroid sources after the QPR3 merge, 9.5-r2 is out and live on OTA!

Check release notes & install instructions & known issues in Post #2, which I update every time I put out a release. ;)

Should be a little less battery-hungry again. As always, if you run into bootloops or massive battery drain after updating, make sure you have the most recent stable version of your preferred Google Apps (or microG, or Magisk, or whatever) install zips, download the ROM zip, and do a dirty flash from recovery:

- reboot to recovery

- adb sideload the ROM zip

- REBOOT RECOVERY RIGHT NOW BEFORE YOU DO ANYTHING ELSE

- adb sideload GApps zip(s)

- NOW you can reboot to system.

- [optional if using Magisk] run the Magisk app and direct install when it says some additional setup is needed, and reboot again.

That takes care of just about every single issue people complain about; whether it's A/V playback stuttering when Hotword Detection is enabled, or massive battery drain resulting in only 3-hour screen-on time, or bootloops because some priv-app permission didn't get copied directly because the booted Updater script is having a bad month.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Oh yeah, I was gonna mention earlier:

At some point I want to switch us over to using retrofit dynamic partitions, because I've had a couple scares once or twice with not having enough room leftover on the system partition to safely flash a complete Google Apps package.

The goal is to make sure we've got lots of room for flashing any Google Apps you want (or microG, or nothing) for the foreseeable future.

IF I DO, here's what that looks like:

It does not require a clean flash to convert; the only reason a clean flash would be required would be for changing major Android versions.

I'm not switching to a read-only filesystem for the system partition, because it's important to me that people can run vanilla or use microG if they desire an alternative to Google (vendor will likely be zstd-compressed squashfs to free up a little room).

Converting is a one-time process, much like flashing the ROM in the first place; you'd need to download a couple specific files, put the device in bootloader mode, run some specific fastboot commands from computer, reboot into recovery, then flash some things in a particular order. Then it's back to business as usual and updates from Settings > System > Updater (or dirty flash from recovery). Relatively painless, same steps as it has always been.

I've tested with a dynamic partition retrofitted build: both the System > Updater and recovery installation of the retrofit ROM zip from a "normal" install will fail gracefully, without triggering a slot switch and rendering the device unbootable. It'll just stop, and won't finish, and you can keep using the phone. So there's no risk of "accidentally accepting the dynamic OTA update and then it ruins my bootable system". Not sure if it will clobber the contents of the other slot, so folks dual-booting be warned (you're already in your own special unsupported category, but I'm trying to be nice here).

If you want to switch back to a different ROM, dynamic or not, ignore any silliness that you've heard regarding Optimu* ROMs and needing to use MSMTool: just reboot to bootloader and follow the ROM install instructions for clean flashing (make sure it has some steps about using fastboot to erase the odm, system, and vendor partitions to clear super partition superblock metadata, in case you're transitioning to another dynamic partition ROM).

If you're worried about using TWRP, well, that's up to you. I'm not supporting TWRP and not going to let TWRP support stop me from doing the best thing for this ROM for this device to make sure it works long-term. That being said, snnbyds has a working dynamic-enabled TWRP build that he ships alongside his Pixel Experience Android 13 builds for OP6/T that should let you continue making bad choices about custom recoveries. ;)
[OnePlus 6 & 6T Cross Device Development] solidsnake_119:
Just wanted to say a huge thanks for this amazing work! I have been using this ROM for months and it's great!

Quick (and dumb, sorry) question @Terminator.J - If I do a dirty flash as described here (my battery life is not great lately), can I use the GApps provided here: https://sourceforge.net/projects/nikgapps/files/Elite-Releases/crDroid-op6/NikGapps-T/ ? When I clean flashed for the first time I used MindTheGapps 13.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
I honestly have not tried switching between MindTheGapps and my NikGapps packaging without a factory reset.

It might work just fine, it might not and you would have to struggle with getting everything backed up and factory resetting (which will wipe internal storage) and having to do all the setup all over again.

Guess I should actually try that out sometime with the tester enchilada, but summers are stupid busy for me irl. I'm always stupid busy. If you want to be the brave soul who backs up all their data and tries it out, please do report back!
[OnePlus 6 & 6T Cross Device Development] jeanmarce:
hello thank you for the rom update for my oneplus6(y)
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Anyone?

Thoughts/questions/concerns about the potential change to dynamic partitions?
[OnePlus 6 & 6T Cross Device Development] tomasz-c:
I have a question. If I don't use and don't intend to use gapps, do I also need to switch to dynamic partitions? It's not a problem for me, just asking.

If there are steps on how to switch to dynamic partitions, could you also describe here how to reverse it? I think less people would be afraid of it then :)

I am for any change that will reduce the number of problems with the preparation of new images by you. Thank you for your work, thanks to it we can enjoy the news on the phone that works well and smoothly all the time.

I usually do updates via adb sideload (it's more convenient for me) and sometimes I also use adb for other purposes. I use Linux on a daily basis, so it's not a problem for me to execute a few commands, but I think that it won't be for other people who use this ROM either, because everyone who decides to change the ROM is at such a level to do it.

I've been here since crDroid 7 and I've done all updates as dirty (don't follow me) and everything works fine (sometimes it needed to clear cache for some apps). Thanks again for your work. 🥇
[OnePlus 6 & 6T Cross Device Development] Ulises31:
It's more difficult flashing first time. When I was, some time ago, in a DP ROM and get back to non DP ROM I followed that I heard from "Optimu* ROMs" and used the MSMTool with all that involves. If you say it's not necessary then great. But, please, say step by step the way to go a non DP ROM or switch to another DP ROM.

Thanks
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Oh you know I love writing step-by-step novels, don't worry. 😅 There will be documentation!

I just tried it myself a few days ago, to go back from a dynamic build on the testing enchilada to standard partitioning build of 9.5-r2 (I've been playing with a few things involving NFC and telephony).

To give an overview, whether you're converting TO or FROM dynamic partitioning, it just takes a couple extra steps with flashing the "destination ROM" boot.img (which contains kernel & recovery) and vbmeta.img files to the correct partitions in both slots, a copy & paste fastboot command string to wipe odm/system/vendor (to make sure there's no leftover old super-partition metadata), reboot recovery, adb sideload the destination ROM zip, and if you need to flash GApps (if they're not included), then reboot recovery & adb sideload GApps zip (or microG if using, or Magisk if using, etc etc).

If you don't know how to extract a vbmeta.img, then there will be a little aside for how to get "payload-dumper-go" and use that to extract the needed stuff from the ROM zip.

And again; in the case of moving to the "dynamic-enabled" version of this ROM, I'll build it with the same security patch level as the existing release, and no clean flash/formatting data/wiping internal storage would be required.
[OnePlus 6 & 6T Cross Device Development] abdulhamid1978:
Hope someone can help. If I am on Evolution X 7.9, how do I install this crDroid Rom? Evolution X 7.9 has retrofit dynamic partitions.
[OnePlus 6 & 6T Cross Device Development] rbariviera:
I've been using Stock OxygenOS since I bought the phone (5 years ago).

There are some features that I really like and I would like to know if it is possible to activate in this version of crDroid.

1 - Pull to notification panel: I can pull notification panel by dragging from the middle of the screen (I think it's a feature of Oneplus launcher)

2 - Expanded/Scrolled Screenshot: When I take screenshot, a button called "Expanded Screenshot" appears below the thumbnail

Is it possible to activate these features?
[OnePlus 6 & 6T Cross Device Development] rbariviera:
Now I see that "pull for notifications" already working but not over the clock widget :)
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
expanded screenshot already exists, too ;) it's the little button with the up & down arrows at the top and bottom of the square.
[OnePlus 6 & 6T Cross Device Development] Duvel999:
I'm now using ROM 13 Unofficial LOS 20 by Kitch2400.

What is the best or safest way to install this crDroid ROM?

Can I install it on my phone, by downloading the files on it ?

I'm Unlocked & Rooted, I use Magisk
[OnePlus 6 & 6T Cross Device Development] BratHuhn:
The ROM looks really promising. Currently running the latest official OOS and want to give it a try! Is there any kind of feeling regarding battery drain in comparison? Thanks!
[OnePlus 6 & 6T Cross Device Development] Duvel999:
I m doing a fresh install..

I got a OnePlus 6T.

I use Windows 11 & coming from Unofficial LOS 20.

I got some problems that I encounter..

The dynamic partions A & B are new for me.

which programs are advised for ADB & Fastboot?

what are the Fastboot commands?

what are the ADB commands?

I backed everything up to my PC.

Hope someone can help me or point me in the right direction.

Regards

D
[OnePlus 6 & 6T Cross Device Development] Ulises31:
The best thing you can do at the beginnig is read, read and read.

You have in the first post all the instructions to flash this ROM. Then read it, do it and in the case you find any trouble post it here.

Regards
[OnePlus 6 & 6T Cross Device Development] Duvel999:
Yes I know .

I read it several times.

Downloaded all the files & tried it.

Googled for ADB, Fastboot and sideload, but I managed recovery & boot.img on the device.

This to special TWRP, by Unofficial LOS20 Rom.

Hope you can help me.

I fixed it out ...LoL
[OnePlus 6 & 6T Cross Device Development] Spirit_of_Eli:
Hello,

short question.

Is it possible to durty flash NikGapps with Magisk to solve the battery drain problems?

Or do i need to remove NikGapps, flash the ROM and then reflash NikGapps with the newst version?

Last time with durty flash broke my installtion with the A/B partions 😢.

Thanks very much for your work!!! Have an nice weekend.
[OnePlus 6 & 6T Cross Device Development] 0kti:
Testing 9.6 RC1 so far without issues