yashsingh1/xdaforums huggingface dataset:
[OnePlus 6 & 6T Cross Device Development] Nuxelrod:
Hello, is this ROM officially discontinued ?:/

I mean, i just instaled it 2 months ago ^^'
[OnePlus 6 & 6T Cross Device Development] Luke92s:
This rom is amazing! Stable and customizable, the crdroid launcher is excellent and, thanks to the Gcam installed as a system app, it is possible to record videos, both in 4k and Full HD, at 60 FPS like the stock rom! As well as having many cool features! Excellent for now, hoping that it will be updated since it is stopped in July 2023... I think it is the best so far tested on the Oneplus 6T (I come from the Pixel Experience, where there was no way to record at 60 FPS).
[OnePlus 6 & 6T Cross Device Development] truquete:
@Terminator.J according to crdroid download page, this amazing ROM is not supported any longer. Is this a mistake on their side, or have you quietly phased it out? I think many of us would appreciate some heads-up. In any case, thanks for your contribution to this great port.
[OnePlus 6 & 6T Cross Device Development] mrjuniork:
For you and others who've been wondering, let me take the liberty to share a message from the dev, in his typical short and sweet style 😉

Spoiler content hidden.
[OnePlus 6 & 6T Cross Device Development] Nuxelrod:
Thank you !
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Yes, thank you @mrjuniork for keeping folks updated here! 🍻

I've been super-stressed with real life stuff, and trying to keep things balanced meant walking away from volunteering time & attention to maintaining for a month or so.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
ONLY A MONTH LATE! (which is to say, a month behind my usual "month-late-is-normal" release cadence)

crDroid v9.8 pushed to OTA servers.

If you were on the 9.8rc1 zip, this is the same file. Just finally uploaded it.
[OnePlus 6 & 6T Cross Device Development] jeanmarce:
thank you for update 9.8 install no problem faster than version 9.7 thank you(y)
[OnePlus 6 & 6T Cross Device Development] Duvel999:
Thanks Terminator.J & crDroid Team for this update to 9.8 👍
[OnePlus 6 & 6T Cross Device Development] Fornacis:
Hi.

I noticed a problem after updating 9.8 from 9.7.

Well, after the screen is automatically blanked, it stays off for several seconds and wakes up, it goes back to the last screen fired up, it is not the lock screen that activates when you use the power button to blank the phone. The situation repeats indefinitely, expires, awakens, expires, awakens, until manually locking with power.

Anyone, anything? :)
[OnePlus 6 & 6T Cross Device Development] asripath:
Upgrade to latest 9.9 to see if resolves the issue
[OnePlus 6 & 6T Cross Device Development] Fornacis:
Where can I find version 9.9?

I looked to see if there was an update and found nothing.
[OnePlus 6 & 6T Cross Device Development] asripath:
crDroid.net - Download crDroid v9 for MI9T Pro (raphael)

official crDroid v9 for MI9T Pro (raphael)

crdroid.net
[OnePlus 6 & 6T Cross Device Development] Fornacis:
Okay, and you are saying that the version with MI9T Pro will work elegantly on OP6? I don't think so.
[OnePlus 6 & 6T Cross Device Development] asripath:
Ah... wrong thread

Release enchilada_cr9.9_test3 · TJ-Releases/enchilada

*** crDroid v9.9 (Android 13.0_r75) Test 3 - therm-mcdlite-ioctl *** September 2023 ASB Builds Changelog: — Test 1 - Changes since v9.8 Official Release: September 2023 Android Security Bulletin m...

github.com
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Pre-release test builds are linked in the Telegram group.

Release versions are linked here & on the official website.

9.9 is now in release candidate status, and I'll probably push it here in the next day or so.

9.10 sources are available upstream, and now that they fixed a nasty bug that was forcing people to need to do clean flashing or fail to be able to get beyond a black "Phone is starting..." screen, I'll finally be able to sync & start building 9.10 test builds.

Whee!
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
crDroid v9.9 is now live on OTA, woo! 🎉

See full release notes in 2nd post, but anyway, highlights:

- Should fix the battery drain after a few days of uptime.

- "Merge" button for creating conference calls exists again in built-in dialer.

- Should be a bit more smooth under load without sacrificing (much?) battery and with better thermals (Golf Blitz no longer stutters during a match once throttling kicks in if you disable GPU Thermal Throttling in DeviceExtras, yayyy).

If you use the recommended "elite" build NikGapps, you should probably get the newer zip for that and do an update install with the new Nik zip from recovery.
[OnePlus 6 & 6T Cross Device Development] jeanmarce:
hi thank you for the update I love your work installing version 9.9 no problem well done;)(y)
[OnePlus 6 & 6T Cross Device Development] alk753:
Thank you for keeping the OP6 alive and well. Donation sent. Keep up the great work.
[OnePlus 6 & 6T Cross Device Development] Rockishi:
I've moved over to this ROM from Unofficial Lineage OS.

Note for future installers: I had the hardest time trying to install the OS from the fastboot and adb like the instructions said. Eventually my ADB access showed as "unauthorized". I was stuck and had spent 4 hours. But then I installed TWRP via fastboot and was able to install the ROM zip quickly.

Now I have a problem where the contacts won't sync with my Google accounts. I've attempted many solutions. Now I think the only option is to factory reset and install a NikGapps package that has Google Contacts baked in. Other than that the ROM seemed to be running smoothly.
[OnePlus 6 & 6T Cross Device Development] Duvel999:
Try this for adb

Thread '[TOOL][WINDOWS] ADB & Fastboot++ | February 2023' https://xdaforums.com/t/tool-windows-adb-fastboot-february-2023.3944288/

Take you time

Don't use TWRP & read the instructions carefully.
[OnePlus 6 & 6T Cross Device Development] Rockishi:
Thanks. However, since it was a new install I completely reinstalled with Nikgapps Basic and that fixed the problem. Having Google Contacts built in solved any syncing issues.

I did:

1. Fastboot flash TWRP temporary recovery.

2. TWRP zip install crDroid.

3. TWRP zip install TWRP permanent recovery.

4. Reboot to TWRP recovery.

5. TWRP zip install Nikgapps Basic.

6. Reboot system. Worked!
[OnePlus 6 & 6T Cross Device Development] alk753:
I came from OOS11 and after updating my adb/fastboot toolkit and OP drivers, I followed instructions to the letter... All great.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Well, that's certainly *a* way to do it.

Not a supported installation configuration, since TWRP doesn't factory reset/format userdata and set up encryption keys correctly.

Not sure what's wrong with contact syncing; it has worked pretty flawlessly with the recommended NikGapps "elite" build for everyone else to-date.

Glad you've got something going on that works for you!
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Note to future installers:

Please follow the correct instructions, and avoid TWRP, if you want to submit bug reports & receive support.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Meanwhile, 9.10 pushed to OTA!

...

Read the release notes. But anyway, apparently PixelPropsUtils (our safetynet spoofing framework addition) was, uh, causing GMS (Google Play Services) to try and find an update after the security patch level got a little old... and, um, that would lead to massive battery drain. It doesn't do that now.

Thanks to whoever on the core dev team figured that one out.

I'm gonna go sit for a while and contemplate a beer. It's been quite a day/week/month/year/decade.
[OnePlus 6 & 6T Cross Device Development] ISkyFireI:
Not sure if am i doing something wrong or is the fingerprint/face unlock is missing for work profile?
[OnePlus 6 & 6T Cross Device Development] jeanmarce:
hello install update 9.10 no problem found for the moment

on my oneplus 6 no problem fingerprint

thank you for this update(y):love:

I found a bug impossible to call when my oneplus 6 is connected via bleutoot the keyboard closes by itself error message without the bleutoot connected it works on the rom version v9.9 it works well
[OnePlus 6 & 6T Cross Device Development] T2000T2000:
My OTA Update from 9.9 to 9.10 hangs at "package installation will be finalized" at 0% :(

Not sure if I can cancel it or in which state my phone now is :(

Edit: It took a loooong time (probably 10mins) until this started and eventually finished. Not sure if I even had to put the updater "in the background" by doing something in another app, but when I did that aber about 10mins, the progress started and succeeded.

I am now just hoping that the bluethooth bug mentioned by jeanmarc doesnt happen for me with my car audio as bluethooth problems (infinite bluetooth restart) where the reasons to switch from the unofficial lineage 13 to this rom...
[OnePlus 6 & 6T Cross Device Development] alk753:
Just updated from 9.9 to 9.10 using the built-in updater as per instructions.

In my case the package install progress bar took about 2-3min for it to jump from 0% to 23% and then onward to complete the process in about 6min total time. As recommended, I have the updater process prioritized in settings and caffeine tile ON during the whole process. Just rebooted... on to testing!!!

My NikGapps are the recommended Elite ones from 20231010.

Thank you @Terminator.J!!!
[OnePlus 6 & 6T Cross Device Development] jeanmarce:
hi I just did the test I installed the rom version venchilada_cr9.10_rc2 the same problem impossible to make a call when the oneplus 6 is connected via bluetooth on the rom version v9.9 it works well
[OnePlus 6 & 6T Cross Device Development] alk753:
I can't reproduce the issue. I paired my BT headphones (Anker Soundcore) and placed a WiFi call on cr9.10 (release) wihout issue.

Can you elaborate on your setup?
[OnePlus 6 & 6T Cross Device Development] jeanmarce:
salut quand je suis connecté via bluetooth je veux faire un appel à l'aide de l'appel j'ai un message d'erreur clavier il disparait je ne peux rien plus rien faire dans la version 9.9, ça marche

sinon, pas de chance, je reviens à la version 9.9

ps

Je viens d'installer la version 9.9 fonctionne bien
[OnePlus 6 & 6T Cross Device Development] sonudhillon:
My phone is not rooted. After updating to 9.10 secure apps have stopped working and throwing rooted device error.
[OnePlus 6 & 6T Cross Device Development] 1to1:
Where can I find the instruction?

I like following your step-by-step instruction to the letter, but without an instruction, I'm lost...

I doubt that I use the "elite" build, because I installed NikGapps in May.

In my download folder, I have NikGapps-crDroid-op6-arm64-13-20230501.zip - perhaps this means that I have NikGapps-T?

How can I migrate to the "elite" build?
[OnePlus 6 & 6T Cross Device Development] jeanmarce:
hi question when I install the ROMs with the installer provided with the ROM internally I never update NikGapps it could come from my problem? Bluetooth call? because I am staying in v9.9 because v9.10 is giving me problems
[OnePlus 6 & 6T Cross Device Development] momenti1337:
Hi, thanks for the room it's awesome 👍 some days ago google pay stopped working, i get a message that device is modified or rooted. I run the latest build with recommended gapps and no root. Does anyone have the same issue? I must add that before google pay worked with no issues
[OnePlus 6 & 6T Cross Device Development] jeanmarce:
hi I have just done a clean installation of the v9.10 rom still the same problem the keyboard on call disappears when I am on bluetooth I don't understand that no one has my problem I would like to understand the reason if possible

momenti1337​

I have no problem with google pay
[OnePlus 6 & 6T Cross Device Development] alk753:
Tried again, and my dialer keyboard is OK while connected to bluetooth using Google's Dialer (Phone app)

Which Gapps are you using?

Have you tried the recommended TJ Elite Nikgapps? https://nikgapps.com/Terminator-J

I've been running v20231010, just saw there's a newer 20231107...
[OnePlus 6 & 6T Cross Device Development] jeanmarce:
hi I use the good NikGapps-crDroid-op6-arm64-13-20231107-signed.zip I Don't Under stand since I use This rom Never a problème no problème I stay on the 9.9 rom Suits me Welle. because every time that you want to go back to the previous version required full wipe otherwise the OnePlus no longer wants to boot
[OnePlus 6 & 6T Cross Device Development] alk753:
Are you using Google's Dialer or the dialer that came with the ROM?
[OnePlus 6 & 6T Cross Device Development] jeanmarce:
hello the one in the rom I did a test by installing another dialer it does the same thing

alk753​

no problem I'm staying on v9.9 which works well for me I'll see when Android 14 is released if I have the same problem thank you
[OnePlus 6 & 6T Cross Device Development] nihiLichen:
The same thing has happened on PixelExperience 13. I believe this is actually an update Google has done that has completely broken this across custom ROMs.
[OnePlus 6 & 6T Cross Device Development] alk753:
Same here... "your phone may be rooted or running uncertified software, blah, blah..."

Google Pay down, YASNAC passes OK.
[OnePlus 6 & 6T Cross Device Development] no_limiz:
https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/ solved the Google Pay Problem for me.
[OnePlus 6 & 6T Cross Device Development] momenti1337:
Shure if you want to use root that's an option.
[OnePlus 6 & 6T Cross Device Development] CHV:
Use this app from Playstore to check Google Play Integrity:

gr.nikolasspyr.integritycheck

YASNAC is checking SafetyNet, not Google Play Integrity.
[OnePlus 6 & 6T Cross Device Development] momenti1337:
View attachment 6033601
[OnePlus 6 & 6T Cross Device Development] alk753:
Thank you for pointing that out!
[OnePlus 6 & 6T Cross Device Development] alk753:
Thank you! Went down the rabbit hole and learned a ton about the integrity checks.

Module installed and GPay working now.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Yeah, sorry I've been working a lot of hours IRL and taking care of family stuff.

Again.

As always.

ANYWAY it's been a big day for, like, everyone with regards to SafetyNet. We keep changing the device fingerprint in PixelPropUtils in framework, and Google keeps moving to block them. This is happening for *every* custom ROM, not just oneplus 6, not just crDroid. It's pretty wild today, and I don't have a recommendations that y'all aren't already talking about.

I've got some fixes for a couple issues identified in 9.10 official release, and I'm about done screwing around with addressing another bug report, and should be pushing 9.11 official soon.

If you want to help do some release candidate testing, or get an emergency "oh crap, this should fix things" kernel zip to flash from recovery, or want to try out the script-kiddie-flavor "crDroid++" kernel installer zip (KernelSU support! Overclocked GPU frequencies! TCP congestion governors you'll never use!) check out the TG group as linked in the first post.

I will of course keep primary support & documentation for the official monthly releases happening here in XDA, but most of the "sausage making" that goes into figuring out issues as they happen, testing fixes, testing features, working out what will become the updated documentation, etc. takes place there.

ALSO, in case anyone was wondering, 14.0 boots! 🥳 There's an alpha build in the TG group, which doesn't even have feature overlays set up yet.

Working on a beta release once I get the Android 13 (crDroid 9.x) branch hammered into shape for November.

My plan is to shift to dynamic partitions for Android 14, in order to gain a little more space in the system partition to support larger GApps packages & have less risk of bootloops/update problems down the road due to running out of available room. But don't panic; I'm keeping system as ext4 (rather than switching to erofs or something) which means you can still mount system as r/w in recovery and flash whatever your choice of Google Apps, microG, or even *nothing* and just run vanilla if desired.

Don't panic; the conversion is a one-time process, and then updates work exactly the same as they have in Android 13 (either use built-in updater in Settings > System > Updates, or flash from recovery by rebooting recovery/adb sideload rom zip/reboot recovery/adb sideload gapps/reboot system).

MSMTOOL IS NEVER REQUIRED TO CONVERT TO OR FROM DYNAMIC PARTITIONS. ANYONE TELLING YOU OTHERWISE IS EITHER IGNORANT OR JUST BEING LAZY. It's just a couple extra fastboot commands to run from your computer, and two extra files to download, and you do the process one time when you convert. If you can read the kind of novel-length instructions I write, you can do this. I believe in you. 🖤
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Google has changed how they treat different device fingerprints that we have been spoofing TWICE now in the last week, on their end.

It's not you, it's not something wrong with this ROM. It's trying to stay one step ahead of Google.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
I keep the instructions/documentation for various things under the "Spoilers" buttons so that it's not such a big wall of text. :D

NikGapps "elite" build is linked in the 2nd or 3rd post, under the "Google Apps" section.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
The issue isn't so much that you updated to 9.10, but that ANY flash at this point will trigger it to refresh SafetyNet/"Play Integrity" attestation, which is now failing on any current builds.

You didn't do something wrong, an older version won't work better, it's ... Google.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
I'm sorry that the Dialer has been giving you problems. It's giving EVERYONE problems right now, sadly.

The Lineage team has some folks working very, very hard to bring the ancient (Android 11-era) AOSP dialer code up to current standards/permissions/implementation/whatever, but the changes aren't quite ready yet.

Google literally deprecated the open-source Dialer and Messages apps in AOSP source, without contributing their Pixel-specific changes back to the AOSP project. So there is no more baseline for generic dialer & text messaging apps now. They're on a big "if we can't control everything about how you use your phone, then you can't do ANYTHING with it!" kind of supervillain vibe right now, and it sucks.

All I can recommend is to use something like the "Google Phone" dialer app from the Play Store for now, and I'll try to merge fixes to the built-in dialer as soon as possible. Sorry for the headaches!
[OnePlus 6 & 6T Cross Device Development] jeanmarce:
Terminator.J​

hi I also tested the dialing application "Google Phone same problem with bluethoot but the rom version 9.9 suits me well no problem thanks again;)(y)
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
If you feel like living dangerously, I have a release candidate build of 9.11 that I'd really love to get your feedback on.

I'm hoping that people who have been having Dialer app & bluetooth problems can test it out and tell me if things have been fixed.
[OnePlus 6 & 6T Cross Device Development] jeanmarce:
hi I would like to test the release candidate version build of 9.11 the problème if it does not work correctly I have to format all my data if I want to go back to version 9.9 otherwise my oneplus 6 no longer wants to reboot a bit annoying because it needs to my phone lol
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Think I've got a 9.11 build that's good to release for November. Will throw it at the testing group and then probably push tomorrow if all is well.

Also getting ready to put up 10.0 beta (Android 14) and all the infrastructure/overhead that comes with that. Whee.

I know there were some broken things in 9.10, whoops. Sorry it always takes me so long. Lots of things in real life, and then there's always "one more thing" to tweak & see if it makes it better.
[OnePlus 6 & 6T Cross Device Development] jeanmarce:
hi I just installed the enchilada_cr9.11_rc2 rom on my oneplus 6 the problem with the dialer in bluetooth call is fixed thank you(y):giggle:
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
For those keeping score at home, I just pushed 9.11 to OTA.

If you were using the 9.11 rc2 builds, it's the same zip file.

If you want KernelSU support (currently built again KSU release tag v0.7.1), you can flash one of these installer zips from recovery:

Release crDroidPlusPlus_kernel-cr9.11_rc2 · TJ-Releases/crDroidPlusPlus_kernel

In sync with kernel changes in crDroid 9.11 release candidate 2 build KernelSU support integrated (updated to tag v0.7.1) OC Adreno GPU frequencies (max freq at 812MHz) Also a KernelSU-only build w...

github.com
[OnePlus 6 & 6T Cross Device Development] jeanmarce:
hi thanks for the update
[OnePlus 6 & 6T Cross Device Development] Duvel999:
Thanks Terminator.J & crDroid Team for this update to 9.11👍
[OnePlus 6 & 6T Cross Device Development] T2000T2000:
Update to 9.11 went smooth this morning. Also in the changelogs I saw that you fixed the safetynet issues (for now at least ;-)) Thank you very much!
[OnePlus 6 & 6T Cross Device Development] davix3f:
Flashed the latest build; the rom is really cool, feels fast and OOSCamera is great.

However, google wallet won't let me add cards because of "Device incompatbile because it's running unsecure software or rooted" blah blah. The thing is, I didn't even root the phone, and installed google wallet with few apps installed. What do?
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Yeah, um, about that... I guess I need to update the first posts.

Google is currently going absolutely nuclear against all custom ROMs that use any kind of device signature spoofing. We can't pass SafetyNet Play Integrity API checks right now.

Nobody can.

They're blocking device fingerprints that used to work without hardware-backed attestation ("Strong Integrity"), which is how everyone did it (by spoofing device fingerprint for Google Play Services & Play Store).

It seems Google Pay/Wallet no longer trusts the Play Store "device is certified" attestation, and instead does its own check, and requires "Strong Integrity" to be willing to enable.

For now, you'll need something like this to work:

GitHub - chiteroman/PlayIntegrityFix: Fix Play Integrity (and SafetyNet) verdicts.

Fix Play Integrity (and SafetyNet) verdicts. Contribute to chiteroman/PlayIntegrityFix development by creating an account on GitHub.

github.com

Which means root (either Magisk, or KernelSU + KSU Zygisk module - explained in that link).

It sucks. I'm sorry, you need to carry your cards with you for now.
[OnePlus 6 & 6T Cross Device Development] rickesh1:
Hi

Does this Rom have the original OOS gestures?
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Which ones? As in, swipe up from corners for "back" navigation action?

I wish, I truly wish.

Alas, no.

Don't think anything does now.

We have the same screen-off gestures as LineageOS (with the same caveats where some of them... don't actually work quite correctly... ¯\_(ツ)_/¯ ).
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
ZOMG I should just stop rebuilding & rebuilding and post the current beta build of 14.0 somewhere to download so that I can hurry up & create the XDA post already.

But *inhales & exhales* I'm trying to be good about getting all my documentation & links & stuff looking pretty so that I'm abiding by the forum rules properly (like, no "coming soon" posts with no actual download links & current kernel sources directly linked for GPL compliance -- which are perfectly reasonable rules I'm happy to follow!). 😅

...

BUT THE CORNER SPACING IN THE STATUSBAR ISN'T GOING TO FIX ITSELF, ARGLEBARGLE. 🤪