yashsingh1/xdaforums huggingface dataset:
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
So, without doing too much behind-the-scenes, what happened is at some point you booted without GApps installed, then failed to factory reset after installing them before booting again.

Android will only properly set some runtime permissions for some privileged apps on "first boot"; and refuses to grant them after.

But! You can fake it out by resetting runtime permissions & convince it that an upgrade happened and force it to reevaluate everything (without wiping the contents of internal storage by doing a factory reset).

TL;DR:

- Enable developer options if you haven't already, and allow ADB debugging & rooted debugging toggles.

- Disable cloned apps and/or work profiles, and delete any additional users you've set up if you enabled multiple users or persistent guest user.

- Remove your Google Account from the phone, under "Settings > Passwords & accounts".

- Plug phone into computer, open a terminal window, and run adb root, which will (re)start the adb server in root mode. Authorize communication with the computer on the phone if needed.

- Run adb shell on terminal, and you should get a root (#) prompt.

- Run pm uninstall-system-updates, which will remove any updated APKs to system apps from the data partition (we don't want updates to uninstalled apps lying around being confusing).

- Run find /data/misc_de -name 'runtime-permissions.xml' | xargs sed -i -E 's/fingerprint="[^"]+"/fingerprint="dummy-value-force-upgrade-path"/', which will replace the stored fingerprint in every user's runtime-permissions.xml with a dummy value. This will ensure that the package manager service will think an Android update has happened on next boot.

- (Optional) If you've been wanting to change GApps packages, now is the time to reboot to recovery, adb sideload the ROM zip, reboot recovery again, and flash a different Google Apps zip, and reboot system. If you're just trying to fix up the current install, you can skip the recovery & flashing stuff in this step and just reboot normally to system.

- For a second time, run find /data/misc_de -name 'runtime-permissions.xml' | xargs sed -i -E 's/fingerprint="[^"]+"/fingerprint="dummy-value-force-upgrade-path"/', which will replace the stored fingerprint in every user's runtime-permissions.xml with a dummy value. This will ensure that the package manager service will think an Android update has happened on next boot.

- Reboot, and now you should be able to grant evey permission to Play Store and Google Play services, including making sure they're allowed to "modify system settings" and they should finish healing themselves within 24 hours.

- Reboot again, and now you should be good to re-add your Google account, and go back to running all your apps and re-granting permissions.
[OnePlus 6 & 6T Cross Device Development] soulnull:
I actually love that the tl;dr is longer than the initial post 😁 I know I know, you meant long as in the documentation, not the post...

Thank you for the correct fix. I absolutely did boot without gapps initially. Actually a lot of really good info in here not just relevant to this specific issue as well. It's similar enough to Linux to be deceiving, which has definitely bitten me more than once.

As were mine, no worries
[OnePlus 6 & 6T Cross Device Development] Haxival:
Just booted into the ROM. Had no issues whatsoever installing it. It is very snappy and responsive, but all notification sounds seem to get cut off. Any reason why? Also I've decided to run f2fs idk if that accounts for anything....
[OnePlus 6 & 6T Cross Device Development] Haxival:
Rom is rather unstable.... very snappy in the menus but so many of my apps are having issues of some kind.... volume slider isn't responsive and takes a few seconds to pop up.... perhaps OP6 was never ready for android 13

EDIT: This is very early review and testing, clearly I need to cut some slack and bear a little bit more patience... perhaps some of the issues will fix themselves with a few days time.

Only bug that really concernes me is call notification sounds, those seem to be broken.

By the way... happy Easter folks and devs
[OnePlus 6 & 6T Cross Device Development] Haxival:
Glad to inform everyone that spoofing Play Integrity works as intended, very satisfied of this 👍🏻

View attachment 6086322
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
December update:

The ROM team is still keeping "9.0" as the version number for the Android 13.0_r16 December 2022 ASB (security patch), since it's the QPR1 release which meant rebasing everything with over 10K commits difference in AOSP upstream to try and apply all of the LineageOS changes and then crDroid customizations on top of. So there's been a lot of redoing things that were already done in the 9.0-November release, and trying to get bugs ironed back out.

It's looking pretty good now though, and I'll probably try to push a release of 9.0-December *while it's still December*. Feel free to check out the test builds in the TG group and let me know how it's working for you!
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Yep, it has. NFC dies when the screen goes off & device enters deep sleep.

If you actually USE it regularly & prefer to leave it on, then the best thing is probably to just remove the QS Tile from being visible so it doesn't make the rest of the QS tiles unresponsive for 5-8 seconds.

For what it's worth, I tried a couple test builds bringing back the prebuilt NFC stack from 12.1 (lineage-19.1 base), which only made things worse, and half the folks who tried it couldn't even switch NFC on in that state (never had that problem personally).

So we're likely all waiting on the fine folks upstream at LineageOS to figure out how to un-fsck NFC on enchilada & fajita, if that's even possible. At least Google Wallet/Pay still seem to work for contactless payements, yay.
[OnePlus 6 & 6T Cross Device Development] Samuel_Owolabi:
Yea I do use it regularly and just leave it on all the time. I'll try what you mentioned and hopefully it'll stop the NFC quitting bug. Appreciate the recommendation.

I had a feeling it had something to do with modem or NFC stack. I experienced similar issued with the old LG V20 I had before this where if the wrong/outdated bootstack or modem was there it would cause connectivity issues and FCs.
[OnePlus 6 & 6T Cross Device Development] runtosafety:
I've fixed my issue with the weather service. I remember lurking the Telegram group where someone mentioned they fixed some issue they had by flashing the ROM to the seconds slot, which I've just done.

After rebooting, it still didn't work. But then I found out that network access for OmniJaws was disabled. I think I tried to turn in off and on during the initial troubleshooting (to no success) and just forgot to turn it back on.

Another possible explanation is I might've just bamboozled myself and had it disabled this whole time for some reason (I doubt it though).
[OnePlus 6 & 6T Cross Device Development] gecko8k:
Does anyone know if I can flash CrDroid using the mentioned clean flashing instructions over Evolution X? I ask because the flashing instructions for Evolution X is quite different and maybe changes too much of the phone, see https://gist.github.com/AnierinBliss/dfae19e6c21fde039f8edceeda4bc576
[OnePlus 6 & 6T Cross Device Development] kmr168401:
Evox is retrofit partition, but crdroid is default A/B partition scheme so you have to use msm tool to go back to normal partition scheme after that you can flash crdroid, this is my understanding when i used evox rom, because of retrofit partition it is not possible at all. I hope you can understand my poor English well enough to clear your doubt.
[OnePlus 6 & 6T Cross Device Development] gecko8k:
Thank you very much, that was perfectly understandable 😎. I'll go thtough MSM before I flash CrDroid.
[OnePlus 6 & 6T Cross Device Development] javier87gav:
Is this ROM implementing the necessary changes for getting unlimited Google photos backup?
[OnePlus 6 & 6T Cross Device Development] sebcio2804:
Will boot to TWRP and flash OOS latest zip to both slots do the same?
[OnePlus 6 & 6T Cross Device Development] Awner:
It does!View attachment 5802267
[OnePlus 6 & 6T Cross Device Development] Lacster:
Hey guys,

It's been a few years since flashed a custom ROM so maybe I did something wrong, everything is working smoothly for me besides for the below:

Chrome isn't downloading from the play store - downloaded an apk, play store detected that it's installed and there's an update. I tried to update and it doesn't update, just keeps saying 'Pending'

When connected to my laptop, I select file transfer from the USB menu but my phone never appears. I've tried playing around in device manager, restarting both phone and laptop. The only option that shows on my laptop is the 'PTP' option.

I finished installing crDroid a few hours ago but so far these are the only things that I've picked up.

Is anyone else experiencing this?

Thank you!
[OnePlus 6 & 6T Cross Device Development] maxwell80:
@Terminator.J

Thank you so much for this rom!

I was waiting (and hoping) for something like this - I like it a LOT.

Thanks again!

some feedback:

OP6T, flashed like recommended, no Magisk (yet)

1) I had an issue with my fingerprint sensor. Even though it worked flawlessly immediately after set-up, it could not use it to unlock my phone after longer phases of deep sleep. Changing the battery settings for the system app "SecureElementApplication" from optimised to not optimized seems to have fixed this. (I haven't double checked, but it is working NOW)

Problem came back after ten days....

2) Turn on WIFI automatically ("turn on" - not "connect"!) does not work on my device (location service and always scanning for WLAN on)

3) 3rd party apps like Signal Messenger and Firefox don't adapt to the display setting black design (just light or dark), but this might be connected to the known issue you mentioned in post #2.

ad logs: 1) would be a ~two hours log, I don't think you'd like it ;)

I could make a log for 2) if you want

regards

m.
[OnePlus 6 & 6T Cross Device Development] kmr168401:
Hi, I don't like ask this but have you flashed oos11 on both the slots, as well did you format the data after flashing crdroid, may be if you did format the data, have you installed gapp because you have to install gapps before first time booting into system because it creates so many wired problems.
[OnePlus 6 & 6T Cross Device Development] maxwell80:
I had this laptop - connecton problem too, but at some point it started to work and it still does, just checked. I have no idea why.
[OnePlus 6 & 6T Cross Device Development] dpkmui8:
can someone provide instructions for installing from PixelExperience_enchilada-12.1-20220725-2315-UNOFFICIAL to this crdroid? currently have PE recovery installed thanks.
[OnePlus 6 & 6T Cross Device Development] Lacster:
Yes, I previously had oos11 installed so it was on both slots. I formatted the data after flashing and installed gapps before booting for the first time.

I actually have everything working now besides being able to pick up my phone on my laptop when I want to do a file transfer.

@Terminator.J Thank you so much for such a lovely ROM, enjoying it loads! Surprised how well it runs on the OP6T :D
[OnePlus 6 & 6T Cross Device Development] dhemker:
@Terminator.J thanks so much for this kickass rom. Works very smoothly and fixes for me the issue with the non-persistent pick-up-phone-to-show-ambient-screen issue from Lineageos 19.1.

I am experiencing issues with apps using the NFC functionality, but I'm not sure whether it's the apps having problems or the NFC stack. It's happening with apps that use NFC for checking my identity card. If it helps, I can provide logs. Anyone else having those issues?

Dennis
[OnePlus 6 & 6T Cross Device Development] faabiano7:
where is the option to disable the blur effect?
[OnePlus 6 & 6T Cross Device Development] Samuel_Owolabi:
So I may have figured out a fix for the NFC. Ive been able to get at least a two days without NFC crashing and dissapearing from settings. It involves modifying the /system/etc/libnfc-nfc.conf file. I modified the two green highlighted options to the noted default settings.

Originally they were set to what the picture with red highlight show and they caused issues. However I believe it's the screen off power state being set wrong that may have cause the actual issue. Someone with the same problem I had could probably confirm by only change the power state option and seeing if that fixes it.
[OnePlus 6 & 6T Cross Device Development] dhemker:
I can give it a try, but from what I can see from your screenshots is that setting the duration poll has no effect, as the line is still commented out with #
[OnePlus 6 & 6T Cross Device Development] Samuel_Owolabi:
Completely missed that. But yea I didn't believe that had anything to do with the NFC problem to being with.
[OnePlus 6 & 6T Cross Device Development] gecko8k:
Thanks for creating an amazing rom, good work!

One (small?) feature request if you need something to develop on. Could you design the media player in quick settings so it has a big play button like this. It makes it somewhat easier to pause and play music. A couple of other Android 13-roms that I have tried has this design.

View attachment 5807119
[OnePlus 6 & 6T Cross Device Development] giantflash:
Is anyone else having an issue with high battery usage? Android reports "Android System" as 50% of that usage, and BetterBatteryStats didn't show any major wakelocks or similar stuff, so I don't know what I am doing wrong here. Battery lasts half of what it did using the latest lineageOS (Android 12 based)
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Wow, you folks have been busy here while I've been away ...

I'm getting ready to push the long-overdue December update (Android 13.0_r16 QPR1). A lot of the aforementioned issues should be resolved, especially NFC stack no longer crashing when device enters deep sleep (and everything that impacts, like Google Pay/Wallet, or other QS tiles lagging while it polls NFC status and realizes the stack has crashed & tries to restart NFC).

A huge time-suck has been the statusbar icons/corner spacing & padding.

The "burn-in protection" feature in 9.0-Dec was going overboard and there are still some issues with how spacing/padding is calculated; stuff was trying to spread out wider, and the *battery* meter was getting cut off without reaching the right edge (like it's inside a viewport that doesn't extend to the edge of the screen, due to the privacy indicator "green dot" chip), while the left side (or carrier name chip on lockscreen) was going too far toward the left edge and getting lost under the rounded corner mask.

I had to rework the padding, and ... I'm not happy with it, but it's even & consistent now, even if it's too far from the outside edges now for my liking. At least it's not spreading too far to the sides & getting text/icons cut off after the screen has been on for 15-20 minutes any longer.

Nobody's going to like it, but I need to be able to push SOMETHING to release for now, and keep working on different combinations of padding & corner masking & such for the 9.1 release later.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
I don't think you actually need to use MSMTool, since the actual GPT layout doesn't change when switching to dynamic partition retrofit.

I actually made some test builds with the DPR patches (we're both talking with jabashque, one of the Lineage devs for enchilada/fajita, who likes to play with stuff like that, or setting zram to use 100% of system ram and let God figure it out, or use DPR and then set system & vendor to be squashfs ramdisk images on top of it... good times), but it didn't seem like it was worth it for us, for a couple reasons:

1) The whole point of retrofitting dynamic partitions is to share free space, if one of three filesystems needs more room for putting more stuff in. The way it works is that the three GPT partitions per slot (currently system, odm, and vendor) are now treated as a raw storage pool, and there are "soft" filesystems that span across those three chunks of storage, than can be expanded as needed.

2) crDroid doesn't ship with GApps inline, so that people who want to go Google-free have the option... but you can't ship a read-only system partition filesystem (like squashfs, or erofs like EvoX) if you need to be able to flash a GApps zip.

3) There's plenty of room to install the recommended GApps (MindTheGapps) in the available system partition space as-is.

4) For now anyway, OnePlus Camera & Gallery seem to work okay being compiled into /vendor/priv-app/ with a couple sepolicy hacks, so really, there's no 3rd-party bloat in the system partition to try and work around.

Should be okay with just the clean flash instructions.

It still might not be a bad idea to switch to retrofitting dynamic partitions for crDroid as well, since that means I could put OP Camera & Gallery back in /system/priv-app/ and the sepolicy & permissions for it would be a lot less hacky. But it works fine for Android 13 at the moment, and I don't want to waste hours & hours redoing it again, just to make the initial installation procedure more difficult.

(On the other hand, it might cut down on unneccessary questions from people who can't be bothered to follow the installation instructions... and people insisting on trying to use TWRP for installing from recovery, muahaha :devilish: )
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
1) Usually the system log is automatically truncated. Not sure how many lines it saves, but it's a FIFO buffer that keeps it to a somewhat reasonable size; otherwise you'd just die from out of memory errors after a day or two of uptime. :D So capturing a log after the problematic event has happened is still useful, even if you can't reproduce it immediately after a reboot.

But for all of your points... if you're on the 9.0-Nov ASB release (the only "official" 9.0 release so far) and not one of the 9.0-Dec test builds/release candidates I've linked in the TG group, then ... it's probably outdated info and wouldn't help anyway. I've been trying to get the Dec ASB release together, but it took FOREVER to reinvent the wheel on statusbar/corner spacing & padding, and there are still interactions I don't understand, and I hate how it looks now, but it's not running off the sides anymore after the burn-in protection kicks in, so that's an improvement.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
crDroid v9.0-December has been released to OTA, go get it!

TONS of changes other than the name, check post #2.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Also, Test 1 build of crDroid 9.1 - Android 13.0_r20 is now available. Testing builds are linked in the TG group!
[OnePlus 6 & 6T Cross Device Development] maxwell80:
Thank you for the new build!

There is still an issue I already mentioned in post #32:

Turn on WIFI automatically ("turn on" - not "connect"!) does not work on my device (location service and always scanning for WLAN on)

regards M.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Hmm, seems to be working in 9.1, thankfully!

I made sure wi-fi scanning was on (I don't even have bluetooth scanning enabled), turned off wifi, turned on "automatically turn on wifi" feature toggle... waited 30 seconds, nothing changed.

So then I turned on airplane mode & waited a few seconds then turned it off figuring that would trigger a location refresh, and it popped up the location privacy green dot and a second later wifi came back on.

This is with the recommended MindTheGapps 13.0 arm64 installed on tester phone.

Looks like it's fixed now in January testing builds; come check it out (links in the TG group), or hang tight for January ASB release. :)
[OnePlus 6 & 6T Cross Device Development] dhemker:
I'm still facing an issue that all apps using the eID via NFC (reading data from the identity card) report a "card removed" error during transmission. In contrast, mobile payment is working. Logcat does not report any errors in libnfc. So I'm unsure where to investigate the problem further and possibly providong logs. Anyone else having this issue?
[OnePlus 6 & 6T Cross Device Development] maxwell80:
Good to hear

I think I will wait for the official release
[OnePlus 6 & 6T Cross Device Development] truquete:
Amazing ROM. I couldn't be happier. Everything working smoothly. I feel as if I had just bought a new 1000 USD flagship phone.

I am wondering about the new photo gallery picker of Android 13 where you give individual photo permissions to each app. Do we need to install it manually? By looking at instructions online it looks different from the standard picker from crdroid.
[OnePlus 6 & 6T Cross Device Development] Steccas:
Hello, does someone use this version with minmicrog? I don't want to use gapps. I'm an happy user of crdroid 7 and they work perfectly with that specific version.
[OnePlus 6 & 6T Cross Device Development] maxwell80:
I use the NoGoolag Edition and it does it's job.

However, I had an issue with Signal messages always being delayed (though push notifications in general were working with microg), so I use Signals push notification service now (which works flawlessly), but I don't know if it's a microg or Signal or whatever problem ( and I don't care :) ).

m.
[OnePlus 6 & 6T Cross Device Development] truquete:
In my experience very stable. I use it as mainly driver. Google play no issues. I use mind the gaps. Can't say about call screening, but you can install any call app you want.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
So, quick update on 9.1:

I'm all but ready to release it to OTA. We've had some issues off & on with inexplicable battery drain and occasionally losing permissions (location, usually) or network access both after updating using built-in updater AND clean flash from recovery, over the last month or two that I've actually tracked down to the current MindTheGapps 13.0 arm64 release.

Nobody seems to have had these issues with NikGapps, so I went ahead and modified the permissions, default-permissions, and sysconfig XMLs (and changed one pathname) to include additional allowances for things from NikGapps. In less than a day after dirty-flashing to switch to my modified build, two people who were having severe battery drain issues reported the % per hour drain had already dropped dramatically and their phones were no longer running hot.

I'll update the second post with links & instructions on how to switch to my modified MindTheGapps build, which I'm recommending for everyone to use for Google Apps now until I get fixes narrowed down a little more and can get a pull request submitted upstream to resolve things for everyone everywhere.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
FINALLY, crDroid 9.1 is officially released to OTA servers.

Get it while it's hot!

Also updated my unofficial build of MindTheGapps with more priv-app permissions pulled from NikGapps T for the rest of the packages that it bundles (see 2nd post).
[OnePlus 6 & 6T Cross Device Development] maxwell80:
@Terminator.J

"automatically turn on wifi" still doesn't work on my phone as you describe above.

Quote:"...and it popped up the location privacy green dot and a second later wifi came back on."

No green dot when I do the same.

OP6T

Install as recommended

updated to cdroid 9.1

minmicrog nogoolag system install

no magisc

stock kernel

Settings:

- wlan - timeout after 15 sec without conn. on

-autom. turn on wlan on

-wlan scanning on

-bluetooth scanning off

-location service on alll microg location modules (deja vu, gsm loc, mozilla loc serv, wlan loc serv) exept apple wifi on and running (checked)

Expected behaviour:

- wlan turns off 15 sec after disconnecting (working)

-wlan turns on when known connection accessible

-wlan connection established

Actual behaviour:

-wlan does not reactivate

-and therefore does not connect

I attach a log file - perhaps you find some time to have a look.

Thank you,

m.