yashsingh1/xdaforums huggingface dataset:
[MTCD Android Head Units General] Pavel-71:
In my opinion, you can't downgrade to android 10 using update.zip, for that you should use some QPST tool and the update.img file, which contains the recovery of android 10. And the installation is done from a computer with a usb cable, but I'm just guessing. I noticed you didn't select wipe data and flash format before updating. Try updating again with 6125 GS16 12.0 20220928, and this time mark data wipe in the table, I think when you installed the GS update on CHS, without data wipe, it gave a mismatch error. The German company M.I.C. it has its updates on Qualcomm Snapdragon and there is also a guide where it recommends wiping the data to remove any errors:

SYSTEMUPDATES für Snapdragon 665

Passt für alle M.I.C.-Geräte mit Prozessor Snapdragon 665 (QCM 6125): AV8V7, AV8V7-Pro, AV8V7-Ultra AV9V2, AV9V2-Pro, AV9V2-Ultra AU10 AU7 AVT7, AVT7-Pro, AVT7-Ultra AVTO7, AVTO7-Pro, AVTO7-Ultra AF7 AO7 AO8 AB9 Bitte beachten Sie, dass die Updates nur für unsere M.I.C.-Markengeräte geeignet...

www.mic-autoradio.com
[MTCD Android Head Units General] yrmomsadic:
Thanks for getting back to me. I looked at that MIC page you linked to, followed the instructions, checked wipe data and did the restore with the above mentioned update.zip file. The update completed successfully, it did erase all my data, apps, and settings. It did NOT fix the version unmatch issue though.

While I'm here, my CPU says, AArch64 Processor rev 2 (aarch64) @1.8GHz (x8)
[MTCD Android Head Units General] Pavel-71:
Too bad it didn't help. Hard to advise now. If the seller doesn't call and send the original GS update, I would try the McuUnmatchUnlock app. If that doesn't help, try updating MTCH_CHS_V3.80. The last option, but I don't know if it's safe, is to try an update from M.I.C. I really don't know how it is with the Qualcomm Snapdragon 665, but firmware from other vendors can be installed on PX processors without any problems, I installed HCT7, HCT4, GS16, M.I.C., CHS, Hal9k firmware on the PX5 without any problems. The problem is with the MCU update, here when using another manufacturer unmatch can occur, sometimes it helps to use the original manufacturer or the McuUnmatchUnlock application. For more serious problems, a special programmer is needed. Try to register on 4pda and ask here, maybe they can give you better advice, CS-X is excellent, it has MCU thread in the message.
[MTCD Android Head Units General] yrmomsadic:
I initially did try the mcuunmatchunlock.apk, and the app quits and fails upon opening. It was one of the first things I tried when I found this forum. I appreciate the effort and attempt, felt a little alone and on my own here until I found this forum.

If I understand what I’ve read in the many pages here, wouldn’t getting another GS android cause the same issue? Correct me if I’m wrong, but if I have a CHS MCU, I either need an android built for CHS & 4G/LTE (from seller), OR attempt to change the MCU to GS, which could potentially brick me if not compatible.
[MTCD Android Head Units General] Pavel-71:
Sorry I wrote it wrong, of course I meant the original CHS firmware. Of course you are right about MCU, you should use CHS.
[MTCD Android Head Units General] yrmomsadic:
Well, the seller (AVIN) finally got back to me, "Sorry for the inconvenience. You can send back the unit for a replacement." I would've rather just installed the correct update.zip file, but this is better than nothing. Thanks for the help, and at least I found a new interesting forum.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
LOGS OR IT DIDN'T HAPPEN​

How to make bug reports (and how not to):​

TL;DR: if you've got adb set up on the computer and authorized on the phone, plug into a USB cable, run adb bugreport from a terminal, and send me the zip file it generates, ALONG WITH A DESCRIPTION OF YOUR PHONE SETUP AND WHAT THE PROBLEM ACTUALLY IS.

Spoiler content hidden.

Other Notes:​

"Supported" status - PLEASE do not do these things if you want help:​

Spoiler content hidden.

Connectivity issues:​

Spoiler content hidden.

OnePlus Camera & Gallery:​

Spoiler content hidden.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Reserved. If I were you, I'd have reservations about this as well. :D
[OnePlus 6 & 6T Cross Device Development] i.Desygner:
One huge ass bug report coming right up 🤡
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Aaaand we're official!

Just in time to merge Android 13.0_r16 qpr1, which is an enormous rebase of android/frameworks/base/ with over 10K commits different, so Neobuddy89 and the rest of the team have been busy trying to redo all our customization/features on top of THAT for a week now. So everything that was finally working is probably broken again, sweeeeeet! 😅
[OnePlus 6 & 6T Cross Device Development] runtosafety:
Thanks again for your work.

I know dirty flash isn't the recommended way, but this worked for me:

OTA 8.10 -> 8.11 -> fastboot flash boot.img to both slots (just in case something's changed since I flashed it the last time) -> reboot to recovery -> dirty flash 9.0 -> flash NikGApps Basic (not the recommended GApps, I know, but I found out too late to switch) - > flash Magisk -> reboot to system.

Last time when I tried to dirty flash 7 to 8, I got a bootloop since I was one version behind unlike this guy, so I figured waiting for the latest 8 release might be the right thing.

So far, so good. System feels much more responsive now and all the minor issues I encountered in crDroid 8 are gone (not sure about RAM management yet, I'll see).

I had a few issues initially, but everything's resolved now:

I had a "Settings Services not responding" pop-up after the first boot, which I fixed by clearing the app's storage

My 6T randomly became completely unresponsive after locking a screen (with a double-tap on the default launcher, I think). I've encountered a similar issue on crDroid 8 several times before, but I think that had something to do with the pocket mode. When it happened on 8, I'd have to force reboot with hardware buttons. This time however long pressing the power button showed me the power menu (although it looked like a standard Android one, with a white background and only 3 options, unlike the crDroid one). This has only happened once and hopefully never will again

My only pet peeves (probably upstream issues and not out device-specific) are:

Weather service doesn't seem to be working (neither OpenWeatherMap nor MET Norway, neither on lockscreen nor the OmniJaws widget). Do I need a custom OWM key?

Mobile icon used to hide when data was off. Now there's a permanent data disabled indicator, which is kinda annoying but I guess I'll get used to it 😅
[OnePlus 6 & 6T Cross Device Development] Adnan Hussaini:
Bluetooth keeps crashing.Any One Experiencing the same?
[OnePlus 6 & 6T Cross Device Development] Awner:
For some reason, the GPS doesn't work (in google maps for example). Gave all of the apps location access and made sure to turn on the "use location" toggle. All location services are turned on as well (e.g. google location accuracy). However, location data does work in the metadata of pictures taken by the camera app.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Can't say I've had that issue, with my fitness tracker, or multiple headphones/headsets, or mouse/keyboard...

See post #3 for how to take logs if you'd like to send me a bug report!
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Depending on how you installed, or Google apps package, or if you did something like clearing storage for Play Store or Play Services, you might need to go into Settings > Apps > "Show all ___ apps" > 3-dot menu > "Show system", find Google Play Services and Google Play Store and re-grant them permissions again (like location).

Never had a problem with GPS working while driving in Waze regularly, or recording locatoin in photos in in OP Camera, Lineage Aperture (the other "camera" app with darker grey icon).

Please see post #3 for details on how to send me a bug report & what kind of logs/information I'll need.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
There's probably permissions issues going on there. You really should plan on backing up your stuff & doing a factory reset (which will wipe internal storage, sorry) or it's just going to have little lingering issues like this that I can't help with.

Pet peeves:

1. The weather service works flawlessly both with MET Norway & OWM even without a custom API key; came right up for me. Likely needs a clean flash/factory reset to work correctly.

2. Not sure what combination of settings caused that bug to happen, but mobile signal strength should be visible even when data is disabled, since calls & SMS still exist. But yeah; lots of UI-related stuff is likely different. Every major release the ROM dev team has to figure out what will actually keep working or not, and tried to bring features back in or drop them because it's buggy now or causes problems elesewhere or so forth. Honestly the statusbar icon customization options were kind of a mess in Android 12 and it does seem like it's more reliable & consistent now than it was before.

But I understand you miss your favorite setup; I get it. Sorry friend.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Meanwhile, having synced Android 13.0_r16 (QPR1/December ASB), the dev team had to redo all our stack of modifications & customizations on top of it again (for the git-savvy, it's because it's a rebase of all the AOSP repos; more than 10K commits difference, can't just merge in monthly changes).

They essentially had to do Android 13 all over again, and now all of us maintainers are checking to see what broke. 😅

It seems not entirely broken though, so I'll probably start putting up December ASB testing builds in the TG group soon!
[OnePlus 6 & 6T Cross Device Development] Awner:
Hi first of all thanks for making this amazing rom! I fixed the issue by formatting my data again. I think everything works now. Really love the device-specific additions that are otherwise missing in other roms. Thank you :)
[OnePlus 6 & 6T Cross Device Development] marcioafoliveira:
I just moved from Rice to this ROM and I feel this ROM is better and more polished.

Thanks @Terminator.J 😁
[OnePlus 6 & 6T Cross Device Development] kmr168401:
Yes, in my humble opinion it is better and J always cool, he answer every question on telegram. 🥰
[OnePlus 6 & 6T Cross Device Development] Samuel_Owolabi:
Hey there's a weird bug that's been going on and it has been happening with all the android 13 ROMs I have been using. The NFC just quits randomly and blanks out the menu in settings until reboot.
[OnePlus 6 & 6T Cross Device Development] mangkoeboemi:
any review compared to LOS20 unoficial? I love LOS but really miss the abilty to customize the rom
[OnePlus 6 & 6T Cross Device Development] imokpd:
Nice work,It suit me well,But i can't get OTA updates,I gess it might be a network issue,so I wonder the OTA adress to find out what's wrong,can some one help?
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Well, so far there aren't any. :D That might be why. I've only ever made one official 9.0 (Android 13) release.
[OnePlus 6 & 6T Cross Device Development] crisontur:
i've upgraded with OTA, but i have the issue before the upgrade....from about 1 week and the previous upgrade was some weeks ago and all was working fine.

i have deleted cache and data of telephone and contacts apps but nothing change
[OnePlus 6 & 6T Cross Device Development] Duvel999:
Should install it by Laptop over existing 9.5?
[OnePlus 6 & 6T Cross Device Development] crisontur:
with 9.5, after upgrade and for some weeks was working....

with 9.5 from about 1 week ago i had the issue

after update to 9.6 with ota the issue remains

do you think that fresh install from pc to 9.6 resolve the issue?
[OnePlus 6 & 6T Cross Device Development] Duvel999:
Hope so...

I"m starting over from 9.5 to 9.6 by pc.
[OnePlus 6 & 6T Cross Device Development] crisontur:
but do you have same issue?

upgrading by pc resets all?
[OnePlus 6 & 6T Cross Device Development] Duvel999:
I 'm upgaded successfully to 9.6 & latest Nikgapps, but got problems with Magisk

So try to uninstall Magisk & install it again.

Fixed it .. did the wrong cmd bij adb.
[OnePlus 6 & 6T Cross Device Development] jeanmarce:
hello thank you for this rom crDroidAndroid-13.0-20230706-enchilada-v9.6 works very well I love it before I had the evolution_enchilada rom(y):love:
[OnePlus 6 & 6T Cross Device Development] jeanmarce:
hello after several days of use very fluid rom - very good network - wifi works very well - very good battery life for the moment no bug found(y)(y)(y)
[OnePlus 6 & 6T Cross Device Development] Ulises31:
In my case with v9.6 the ACC Magisk module doesn`t work as in v9.5. Mainly is the battery idle feature. Battery charging reaches the maximum level, i.e. 85%, and then start discharging up to the fixed limit, i.e. 80%. Then starts charging again and so on.

The charging switch configured is the same as in previous version, besides the option to test the different switches in ACC gives that the charging switch has the battery idle feature as TRUE, but not working.

May it be a kernel issue?

ROM works well, fast and smooth. Thank you so much
[OnePlus 6 & 6T Cross Device Development] gibmadikka:
Thank you for maintaining this ROM, it's the best one and makes our device usable again. :)
[OnePlus 6 & 6T Cross Device Development] jeanmarce:
hello me it's been 2 weeks on version 9.6 no problem with the battery on the contrary very good behavior without installing anything more and magisk ok. I love your work rom very fluid find no problem congratulations to you(y)(y):love:
[OnePlus 6 & 6T Cross Device Development] gecko8k:
I think I discovered a bug with album art in Android Auto using CrDroid.

When I use the music app Tidal on Android Auto on stock OOS the album art shows up just fine:

View attachment 5962721

But when I use CrDroid the album art is missing:

View attachment 5962727

I read a bit about it and someone mentioned that some custom roms can be a bit restrictive, meaning album art might not be send from the phone to the car.

Does anyone know how to solve this? And is it possible to wish for a fix?
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
It's probably because the Lineage (Battery) Health HAL is now implemented, and it actually WORKS properly with battery idle mode now. Might even be enabling by default.

Honestly, I've been a LONG time ACC user just for having battery idle mode support, and between my kernel changes and the new "smart charging" implementation direct from Lineage (better than the old one we had in crDroid framework modifications), I finally stopped using it.

Uninstall the module, uninstall ACCA, just go into Settings > Battery > Charging Control, set it to stop at 85%, and be happy. ;)
[OnePlus 6 & 6T Cross Device Development] Ulises31:
I'll try. Thanks

Edit: After several days charging in that way, it seems work as ACC, including battery idle=true.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Sorry for the radio silence. July ASB has been ready, I'm just busy & tired & hot.

I have the release candidate build that will become official release available to download from the Telegram group (I do test builds there, and then when it's ready enough, push the builds to official OTA release & clean up the commits from my personal github to push to crDroid official organization repos). The links in the first post are of course to the official website with the latest official version; but if you're impatient & don't want to wait for me to get done writing release notes & uploading to OTA & all that jazz, you can do a little self-service that way.
[OnePlus 6 & 6T Cross Device Development] CHV:
I can reproduce FC of Google Play Store as following:

- Open Play Store

- Tap your profile image

- Tap "Play Protect"

- Tap Gear (upper right)

- Tap "Permissions for unused Apps".

Clean flash with NikGapps-crDroid-op6-arm64-13-20230802-signed
[OnePlus 6 & 6T Cross Device Development] JonesL:
Anyone getting Google play store thinking the device is a tablet? 🤔
[OnePlus 6 & 6T Cross Device Development] jeanmarce:
hello I use Google Play Store for software updates no problem:rolleyes:
[OnePlus 6 & 6T Cross Device Development] Duvel999:
How do I remove the date from stock crDroid home launcher?

I would remove the clock .

Any tips?
[OnePlus 6 & 6T Cross Device Development] rocky184:
Home settings/home screen and turn off "at a glance"
[OnePlus 6 & 6T Cross Device Development] Duvel999:
Can I edit missing Icons in crDoid home launcher?

So when I install another Icon pack?
[OnePlus 6 & 6T Cross Device Development] janesz555:
Hi! Tested this rom again a few times (clean install, with and without the recommended NIKGapps) the battery life is only 18 hours regardless of the usage. (exactly as the battery estimation says it). The drain stops only in airplane mode. Tried both SIM slot, and if the mobile data is on or off, it doesn't matter sadly.

Went back to OOS 10.3.8, and it is 3 - 3,5 days(!) standby time with all my apps installed and running in background. So its not the battery.

Does anybody else have this much battery drain? I mean, really regardless of the use, that 18 hours is almost the same if I watch video, and If I put it in my pocket and go for a day without touching it.
[OnePlus 6 & 6T Cross Device Development] jeanmarce:
hello I've been on the rom for a month no problem with the battery consumption I find it very good I love this rom very good job(y);)
[OnePlus 6 & 6T Cross Device Development] cobrax2:
Installed this rom recently, and i have a question: sometimes, frequently, when i press back, or home on nav bar the vibration is double, but the touch is normal. Is there a way to disable this? Thanks

Also, i have 2 sim's but i want to disable one. Is there a way?
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Are you using the release 9.6, or the release candidate 9.7? I had some bad stuff in 9.5 & 9.6 that I rolled back in 9.7 and it seems to have fixed the drain issues again. Am trying to push to OTA shortly.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
There we go, crDroid v9.7 (July ASB) pushed to OTA servers, get it while it's hot!
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
There isn't a way. I could add the software switch, but it won't actually disable it; the hardware doesn't support soft-disable of one SIM slot. You'd have to physically remove it. Sorry.
[OnePlus 6 & 6T Cross Device Development] cobrax2:
9.6, will try 9.7, thanks
[OnePlus 6 & 6T Cross Device Development] cobrax2:
But original oxygenos can disable it..
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
I'm unclear if it's a limitation in newer versions of Android or implementations of DSDS or LineageOS or what. I've asked the upstream devs. They said it doesn't actually disable (as in, it's still talking to towers & using battery) even if we put the cosmetic switch in there to make people feel better.

So either OnePlus had some kind of special hardware control, which is possible since they're the ones paying for the Qualcomm BSP that we don't have access to, or they were just lying to us in OxygenOS, to "hide" it when disabled, which is also possible.

I've asked about implementing the ability, and was told by folks who would know that it would only be cosmetic, but you'd still get the battery usage and would still have calls come in. I'm inclined to believe them.

Sounds like the best option for us right now is to just turn off mobile data & roaming on the "unused" SIM.
[OnePlus 6 & 6T Cross Device Development] cobrax2:
Cool, thank you very much for the answer!
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Currently no, sorry. Not sure what the deal is with icon packs, but it seems to be something that's non-trivial to add to "Launcher3" based launchers that build as part of AOSP projects, and so hasn't made its way into our crDroid Home yet.

Like, custom icon packs are a known format, but there isn't an actual standard implementation for how to add support to USE those to any open-source custom launcher that's based on the AOSP "Launcher3" project. Dunno mate, sorry... definitely above my pay grade at the moment. 😅
[OnePlus 6 & 6T Cross Device Development] CHV:
Playstore still has FC, see #196. It relates to "permissioncontroller". Perhaps it isn't included in ROM?
[OnePlus 6 & 6T Cross Device Development] cobrax2:
Updated, still double vibrate on press nav bar buttons sometimes
[OnePlus 6 & 6T Cross Device Development] jeanmarce:
hello I updated the rom with normal manual ota that it takes 1 hour? it works but i find its slow lol

thanks for the update i love this rom;)
[OnePlus 6 & 6T Cross Device Development] cobrax2:
Yes, it took some time for me too
[OnePlus 6 & 6T Cross Device Development] cobrax2:
Also, the brightness slider is somehow not well balanced? I have to keep it to 90% to be able to use it vs 60% same brightness on oxygenos. On 9.6 was the same, 90%. Thanks
[OnePlus 6 & 6T Cross Device Development] Duvel999:
Just updated by OTA, takes +- an hour.

Disabled Security, VPN etc .

Thanks Terminator.J & crDroid Team for this.
[OnePlus 6 & 6T Cross Device Development] cobrax2:
Another few minor cosmetic bugs i've noticed:

Nav bar doesnt always center vertically the 3 buttons, sometimes they are too high. Also on incoming phone call sometimes the buttons are displayed over the background photo, instead of showing the phone background. Thanks!
[OnePlus 6 & 6T Cross Device Development] huzzug:
Hi guys

I'm on OP6T and tried installing adreno driver package I found online. I did it through Magisk. I'm on crdroid A13 build. After installing and rebooting, the phone's screen has gone black. If I press the power button, I can get a limited option screen with reboot, power off, emergency options, but nothing else. Any way to uninstall the driver. USB debugging is enabled, but it wasn't authorized on the system I have on hand. Anyway to bypass?
[OnePlus 6 & 6T Cross Device Development] espionage724:
Where specifically?
[OnePlus 6 & 6T Cross Device Development] cobrax2:
Hello again!

Is there a way to make the swipe gesture for unlocking the screen shorter? Most of the times it doesn't unlock and it's very annoying to swipe multiple times. Thanks!
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
You could try and boot a recent version of TWRP recovery to decrypt/mount userdata and then you could delete the offending module from the appropriate directory in /data/adb/, but I don't use TWRP and don't know exactly what versions, steps, path names, etc.

You could also just re-flash (adb sideload) the ROM zip from built-in crDroid recovery (which will not process addon.d OTA survival scripts), then reboot recovery and flash (adb sideload) your Google Apps zip, and then there will be no Magisk available to load your modules.

At that point, you can enable "Allow rooted debugging" is enabled in developer options, connect to computer, authorize, and then do `adb root` from terminal, and the next `adb shell` you do will still have root (yay for "userdebug" builds) even though there's no Magisk. Go investigate /data/adb/ to find the directory for the Adreno Drivers module, delete it, and then you can reinstall Magisk safely (adb sideload from recovery).
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Probably, but that's way above my knowledge level. Sorry friend!
[OnePlus 6 & 6T Cross Device Development] jeash:
Clean flashed this ROM yesterday and its been amazing. Its been working flawless and the customization options are overwhelming (First time crDroid user). Only issue I faced was with banking apps detecting root and refusing to work. Followed the Magisk/Magiskhide instructions by OP, but no go. Even though OP had explicitly mentioned not to flash Universal Safety Fix module, I went ahead and did that. BINGO - that resolved all the root hiding issues. Its been only 24 hours, but the ROM has been working like a charm, with no crashes/bugs - which was not the case with the vanilla Lineage OS build.

Thank you OP for keeping this official build live keeping my device alive and fresh.