yashsingh1/xdaforums huggingface dataset:
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
9.12 available for testing; I cleaned up device tree a little more, think it's good to call it "done" and move into maintenance releases while I turn my attention to Android 14 now.

If I don't hear of any game-breaking regressions, I'll likely send this off to OTA on/after the 26th.

_____

*** crDroid v9.12 (Android 13.0_r75 Test 1 ***

December 2023 ASB Builds

Release notes, changelogs, known issues, things to test, installation instructions, and downloads:

— Enchilada —

Release enchilada_cr9.12_test1 · TJ-Releases/enchilada

*** crDroid v9.12 (Android 13.0_r75) Test 1 *** December 2023 ASB Builds Changelog: — Test 1 - Changes since v9.11 Official Release: December 2023 Android Security Bulletin merged. Whatever upstre...

github.com

— Fajita —

Release fajita_cr9.12_test1 · TJ-Releases/fajita

*** crDroid v9.12 (Android 13.0_r75) Test 1 *** December 2023 ASB Builds Changelog: — Test 1 - Changes since v9.11 Official Release: December 2023 Android Security Bulletin merged. Whatever upstre...

github.com

Other links:

— crDroid++ kernel for KernelSU support & OC GPU —

Release crDroidPlusPlus_kernel-cr9.12_test1 · TJ-Releases/crDroidPlusPlus_kernel

In sync with kernel changes in crDroid 9.12 test 1 build KernelSU support integrated (updated to tag v0.7.1) OC Adreno GPU frequencies (max freq at 812MHz) Also a KernelSU-only build without OC GPU

github.com

— Google Apps / microG / Magisk —

NikGapps (recommended; use latest Android 13 build).

NikGapps Elite

MindTheGapps (official releases, use latest).

Releases · MindTheGapps/13.0.0-arm64

Contribute to MindTheGapps/13.0.0-arm64 development by creating an account on GitHub.

github.com

MinMicroG (Shane just updated, use stable release until further notice, woo).

Releases · FriendlyNeighborhoodShane/MinMicroG_releases

Prebuilt flashable zip RELEASES for the MinMicroG project. - FriendlyNeighborhoodShane/MinMicroG_releases

github.com

Magisk (recommend latest stable/beta).

GitHub - topjohnwu/Magisk: The Magic Mask for Android

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com

KernelSU apk (requires KSU-enabled crDroid++ kernel flashed from recovery):

https://github.com/tiann/KernelSU/releases/download/v0.7.1/KernelSU_v0.7.1_11366-release.apk
[OnePlus 6 & 6T Cross Device Development] jeanmarce:
hello someone to test the enchilada_cr9.12_test1 version because I don't want to have a big bug otherwise I would have to go back and I would have problems again with the banking applications having to re-recognize my oneplus 6 at near the bank it becomes really annoying:mad:
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
I mean I tested it for a couple days on my tester enchilada... seems fine, really. It's not a huge change from 9.11.
[OnePlus 6 & 6T Cross Device Development] jeanmarce:
hello thank you for the update enchilada_cr9.12_test1 no problem for the moment(y);)
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
I pushed 9.12_test1 to OTA as the release build for December 2023 ASB. 🥳

Also updated the optional crDroid++ kernel installer (links in post #2) to match, with updated KernelSU v0.7.2 driver now included.

Happy New Year!
[OnePlus 6 & 6T Cross Device Development] Duvel999:
You too😀🍻

Thanks Terminator.J & crDroid Team for this update to 9.12
[OnePlus 6 & 6T Cross Device Development] jeanmarce:
hello my best wishes for this new year 2024
[OnePlus 6 & 6T Cross Device Development] jeanmarce:
I just installed crDroidPlusPlus_kernel-cr9.12-KSU-OCGPU.zip

thank you for your work no problem(y):love:
[OnePlus 6 & 6T Cross Device Development] lm089:
@Terminator.J - I apologize for this highly off-topic post: this is a followup on this post from you (over at the LOS20 thread):

in your OP here you mention that you included OOS camera app V3.14.40; I pulled it from apkmirror but can't get it to work: camera screen stays black, and the adjustment icons at the screen top are just dead, no matter what I try. I can get V3.2.106 to work more or less; just switching to PORTRAIT mode crashes the app.

Any hint on what I could try to get "your" version to run (apart from flashing your ROM :p)?

(Yes I tried BSG's GCAM flavour but that again is missing some features I like in the OOS camera app).
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Using the unmodified APK requires extensive modification to several things in the ROM to make it work.

Sorry mate.
[OnePlus 6 & 6T Cross Device Development] lm089:
Got it, Thx, and a happy New Year
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Sorry, I screwed up folks; I forgot that system_server will still go nuts after a few days of uptime on Android 13 if it can't find debugfs, and accidentally brought back commits disabling it in an effort to unify 13 & 14 trees (instead of just leaving things well enough alone 😓 ).

I have a 9.12 hotfix1 build ready, couple folks have tested it and they're not seeing the "system_server_wtf_xxx.log" files in /data/system/dropbox/ now, so I'll go ahead and get that pushed to OTA so it will show up as an available update in the next day or so when I get the chance.

In the mean time, you can download it to manually install (and the optional crDroid++ kernel for KSU support) from the following links:

Release enchilada_cr9.12_hotfix1 · TJ-Releases/enchilada

*** crDroid v9.12 (Android 13.0_r75) Hotfix 1 *** December 2023 ASB Builds Changelog: — Hotfix 1 - Changes since v9.12 Official Release: Reverted the "PRODUCT_SET_DEBUGFS_RESTRICTIONS" commits. It...

github.com

Release fajita_cr9.12_hotfix1 · TJ-Releases/fajita

*** crDroid v9.12 (Android 13.0_r75) Hotfix 1 *** December 2023 ASB Builds Changelog: — Hotfix 1 - Changes since v9.12 Official Release: Reverted the "PRODUCT_SET_DEBUGFS_RESTRICTIONS" commits. It...

github.com

Release crDroidPlusPlus_kernel-cr9.12_hotfix1 · TJ-Releases/crDroidPlusPlus_kernel

In sync with kernel changes in crDroid 9.12 hotfix 1 build KernelSU support integrated (updated to tag v0.7.2) OC Adreno GPU frequencies (max freq at 812MHz) Also a KernelSU-only build without OC GPU

github.com
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
crDroid v9.13 (Android 13.0.0_r75) Test 1 -- January 2024 ASB test build now available!

Release notes, changelogs, known issues, things to test, installation instructions, and downloads:

— Enchilada —

Release enchilada_cr9.13_test1 · TJ-Releases/enchilada

*** crDroid v9.13 (Android 13.0_r75) Test 1 *** January 2024 ASB Builds Changelog: — Test 1 - Changes since v9.12 Hotfix 1 Release: January 2024 Android Security Bulletin merged. Whatever upstream...

github.com

— Fajita —

Release fajita_cr9.13_test1 · TJ-Releases/fajita

*** crDroid v9.13 (Android 13.0_r75) Test 1 *** January 2024 ASB Builds Changelog: — Test 1 - Changes since v9.12 Hotfix 1 Release: January 2024 Android Security Bulletin merged. Whatever upstream...

github.com

— crDroid++ kernel for KernelSU support & OC GPU —

Release crDroidPlusPlus_kernel-cr9.13_test1 · TJ-Releases/crDroidPlusPlus_kernel

In sync with kernel changes in crDroid 9.13 test 1 build KernelSU support integrated (updated to tag v0.7.5) OC Adreno GPU frequencies (max freq at 812MHz) Also a KernelSU-only build without OC GPU

github.com

KernelSU apk (requires KSU-enabled crDroid++ kernel flashed from recovery):

https://github.com/tiann/KernelSU/releases/download/v0.7.5/KernelSU_v0.7.5_11434-release.apk
[OnePlus 6 & 6T Cross Device Development] jeanmarce:
hello thank you for the update install with crDroidPlusPlus_kernel-cr9.13_test1-KSU.zip on my oneplus 6 for the moment no problem(y);)
[OnePlus 6 & 6T Cross Device Development] 1to1:
No new updates found.

Should the 9.12 Hotfix 1 be available to the updater by now?
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
No, I haven't pushed it since 1) I'm planning on releasing 9.13 very soon anyway, and 2) half the battery life issues right now are most likely due to running an old security patch.

I have faith in your ability to download the 9.12 hotfix 1 zip file from the provided link and use the "Local update" button in Settings > System > Updater > (overflow menu) to install it, if you don't want to wait for 9.13 in the meantime.
[OnePlus 6 & 6T Cross Device Development] 1to1:
The instructions tell you to verify that there isn't anything hiding in your /system/addon.d/ directory that shouldn't be there before applying an update.

I see a bunch of files in the directory - is this normal? (Screenshot attached)
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Good looking out! You get a gold star. ⭐

Yeah, that looks about right for my recommended NikGapps package + Magisk, should be just fine. 👍
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
I am so sorry that everyone has been stuck with battery drain on official 9.12 for a month.

Not my plan at all, but I've been basically sick, or working in crunch time on an emergency video editing project the entire month.

The good news is... 9.13 might fix the awful battery drain problem.

The bad news is, it might not.

I re-enabled debugfs in 9.12_hotfix1. I tried to disable it again in 9.13 a couple times, including having applied a kernel update that should fix what was *one* underlying aspect of the drain (system_server freaking out because it can't find /d/wakeup_sources or /proc/wakelocks, and spamming logfiles about it).

But it still runs into awful battery drain anyway after a while, and htop shows system_server pegging a single core at 100% utilization after ~3 days of uptime.

But only for some people! And I canNOT figure out what difference is making it do that on their phones. All the settings I would guess are not the issue. One of them is on microG even, not even Google Apps.

The difference in device-specific sources between 9.12 hotfix 1 and 9.13 is one single prop (the fix for the OpenGL "could not match desired swap behavior" logspam), and it wasn't even there before so it's most assuredly not the source of the drain.

I give up.

If it's happening to you, I'm sorry. Back up your stuff, and factory reset.

If it's still happening, time to upgrade to crDroid 10 and Android 14, where this isn't happening.

I'm done fighting with Android 13 about it. I can't get help from the other devs & maintainers on this one, and I don't have the time or ability to figure it out myself.

Pushing 9.13 rc1 to OTA servers now as the release version; hopefully it fixes battery drain for most of you.

I really hope it helps, because I'm out of ideas and have no bandwidth to work on it and no hot leads to chase down in figuring it out.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
I'm sorry it's been so long.

I keep trying new things and the "massive battery drain after 100 hours of uptime" bug for people who are affected by it seems to keep happening.

I've been incredibly busy with real-life work projects & haven't been able to work on anything with the ROM for many weeks, and I know there are a lot of people still actively using Android 13.

I'd like to encourage everyone to back up their stuff & migrate to Android 14 since it doesn't have that problem and that's where all the active development work is right now, however...

Android 14 is about to hit the wall with not being able to continue booting with kernel 4.9 after March ASB (with 14.0 QPR2 merge) hits, and the migration path to incorporate EdwinMoq's 4.19 patches *REQUIRES* a factory reset & formatting userdata.

So.

Might as well wait a month while we find out what the LineageOS team is gonna do with these devices.

We FINALLY got 9.14 (February ASB) merged, and I have one more idea to try out for the power drain issue.

If that doesn't fix it, well, keep rebooting every 2-3 days I guess.

Sorry. No idea what to do any more.

If it's going to require a factory reset to make it possible to boot Android 14 with March ASB/QPR2 merged, then you might as well wait until that release to consider upgrading to Android 14 (which, otherwise, really HAS been very solid the last few months now -- it's what I've been daily driving since early December last year).
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
For those who want to try out the current testing build of 9.14, here's a copy of the announcement:

Quick, quick notes (really; click the links & read the changelogs there!)

- Boots & works, yay.

- February ASB so you can't just go back to 9.13 release without a wipe, so backup your stuff if you're gonna test on a daily driver.

- Trying yet another thing to see if we can beat the some-people-get-battery-drain-after-100h-of-uptime bug (already switched to debugfs & /proc/wakelocks, already switched to using libperfmgr & lmkd instead of QTI perfd & lmk kernel driver, already stopping statsd service on boot complete; now also disabling compilation of WIL6210 & MSM 802.11ad support in kernel since the hardware doesn't exist and some people were having wifi trouble & logspam about those things).

- Updated kernel commits from upstream LineageOS and bananafunction's backported fixes repos.

- crDroid++ kernel now has KernelSU v0.8.1 driver merged.

(official crdroidandroid github sources will of course be updated once I'm ready to push to OTA; personal repo is always a hot mess 😁 )

_____

*** crDroid v9.14 (Android 13.0.0_r75) Test 1 ***

February 2024 ASB Builds

Release notes, changelogs, known issues, things to test, installation instructions, and downloads:

— Enchilada —

https://github.com/TJ-Releases/enchilada/releases/tag/cr9.14_test1

— Fajita —

https://github.com/TJ-Releases/fajita/releases/tag/cr9.14_test1

Other links:

— crDroid++ kernel for KernelSU support & OC GPU —

https://github.com/TJ-Releases/crDroidPlusPlus_kernel/releases/tag/cr9.14_test1

— Google Apps / microG / Magisk —

NikGapps (recommended; use latest Android 13 build):

https://nikgapps.com/Terminator-J

MindTheGapps (official releases, use latest):

https://github.com/MindTheGapps/13.0.0-arm64/releases

MinMicroG (use latest "Updately" abuse-ci build, and disable use of Mozilla Location Database in microG Settings):

https://github.com/FriendlyNeighborhoodShane/MinMicroG-abuse-CI/releases

Magisk (recommend latest stable/beta):

https://github.com/topjohnwu/Magisk#downloads

KernelSU apk (requires KSU-enabled crDroid++ kernel flashed from recovery):

https://github.com/tiann/KernelSU/r...KernelSU_v0.8.1-20-gdbe43b1_11583-release.apk
[OnePlus 6 & 6T Cross Device Development] Duvel999:
Test this build for fajita
[OnePlus 6 & 6T Cross Device Development] soulnull:
While I cannot be useful for providing feedback for problems since this is the third completely different rom I've dirty flashed between (and some adb remount,rw rm -rf action on /system to clean up the wrong gapps being flashed, which was fine up until 9.14 but catastrophically blew up earlier tonight when I did the update.. all fixed, still haven't factory reset in over a year... but remounting system and wiping it to reflash over it fixed one of my bank apps that hasn't worked since I was on awakenos.. what can I say, I live dangerously), I do want to say that since jumping on board about a month ago, i've been enjoying the crdroid experience (believe it or not, despite all the above, I haven't had any showstopping issues, even have wallet+tap to pay working, lol). I greatly appreciate that terminator_j gives very good documentation and engages with his users (I did read them, I just kinda did my own thing).. So I do want to at least send some love

I'll be sad when 13 ends, as I will not be joining the 14 party since a discontinued app I use heavily targets too low of an android version and I'm not smart enough (yet?) to recompile it. but at least for now, thank you. If this is the end of the road for me, at least this road lead me to a good destination.. thanks for your efforts, they're appreciated.
[OnePlus 6 & 6T Cross Device Development] Duvel999:
@Terminator.J ,

Thank You for this great Rom & development.

How can I safely go back to stock, to unroot, safely lock the bootloader and return to 100% Stock device?
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Um, so, that whole wiping of system does... nothing for you on an A/B device, generally speaking.

For your own info:

- OTA packages (a "ROM zip") always install to the inactive slot.

- Lineage-based recoveries (including crDroid, which gets flashed when you follow the instructions that say "fastboot flash boot path/to/boot.img" from OEM bootloader then start recovery) do not process /system/addon.d/ from the active slot, and they're not delta updates; so every time you flash a ROM zip from recovery, it completely overwrites the contents of the target partition filesystems.

- The booted Updater *will* process addon.d OTA survival scripts, hence the recommendation to reboot to bootloader & flash a boot.img from the ROM you're trying to move to for a clean install (and possibly dtbo.img & vbmeta.img if you're moving to a different kernel or 2-stage init).

- Don't use TWRP for installing anything Android 12 or newer. Just don't.

So if you mount system & wipe it from recovery... well... great. You wiped the current slot, then the installer flashed the new system.img from the payload into the *other* slot like it always does, and sets the flag to trigger a slot switch on next boot; which is why you always need to reboot to recovery BEFORE flashing Google Apps (which installs to *current* slot, as it is not an OTA payload). It didn't really do anything, except possibly some versions of TWRP still process current-slot-system/addon.d/ OTA survival scripts (which might be what was screwing up your Google Apps installation).

Anyway, I'm glad 13 has been working for you. It does seem rather random who has the issue and who doesn't; and most people do not. I just do not have the time to keep dealing with multiple major Android versions, and 9.15 is apparently failing to boot for multiple devices post-merge, so... I don't know how long I'll be able to keep up with it. I'm doing my best to avoid burning out and having to walk away entirely.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
MSMTool.

Look for the "Collection of Unbrick Tools" thread in the "OnePlus 6/6T News, Guides, and Discussion" section.

I have a link in the 2nd post of this thread as well to help you get there.

Be sure you run an update at least once after going back to stock with MSMTool, so that it overwrites the contents of the "B" slot; since MSMTool only flashes slot A and then flags B as invalid contents.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Except you didn't... unless you deliberately mounted the INACTIVE slot's GPT partition as system (so if recovery shows you booted into slot A, you would have needed to mount /dev/block/bootdevice/by-name/system_b to /mnt/system/ and then rm -rf /mnt/system/* to preemptively clear stuff that was about to get nuked anyway).

Which is pointless, because it gets nuked anyway. I do not make block-based delta updates, it is not file-by-file; it replaces the filesystem inside the parition whole cloth -- or in the case of my Andorid 14 builds, wherein we moved to using retrofit dynamic partitions, it replaces the logical system filesystem (which lives inside the super-partition which spans multiple GPT partitions as a backing store) whole-cloth.

Not file-based, not block-based.

You sound like you're used to an "A-only" device with no slots. This does a filesystem-level replacement; always to the inactive slot. There is literally no point in erasing the current slot's system partition, because you're never touching it during installation. All that does is make sure that you cannot possibly switch back to the current working slot in case of a failed update.

That's what I'm trying to explain.

Go check the "everything you never wanted to know about slots" in the first couple posts.
[OnePlus 6 & 6T Cross Device Development] soulnull:
Initially I mounted /mnt/system, deleted, and it came back after a reboot. I don't recall exactly which partition I mounted (the system_b one doesn't seem familiar, but maybe?), but it seemed the right size and had a system folder with a bunch of Google stuff in it, so. I know you're saying it won't work, but... It went from every single app crashing on boot to everything working again. I don't have an answer, but it solved the problem somehow. Maybe it's temporary, maybe I did something in the wrong order that just masked the problem, but multiple flashes before that didn't fix it.

Really really not trying to argue here. I concede that you absolutely unequivocally know Android stuff better than I do, no question whatsoever, I'm nowhere near proficient here. I literally just wanted to thank you for the rom and toss in an amusing aside at how disgustingly dirty my process is (that apparently wasn't actually that amusing). That said, ricedroid required a dynamic partition modification that I did apply, and I haven't clean reflashed since.. maybe that's the disconnect we're having here? I don't know enough about how Android handles the filesystem stuff to know if it is or not. And also why I insisted I wasn't here for support.. because this is a very very dirty system and I know I'm sorta on my own. You don't need to waste time or resources on my horrific device. It's working, and working quite well now. All I can do is shrug and be happy I don't have to clean flash yet. I will have to eventually I'm sure, because I absolutely don't know enough to keep this going (this is how I learn.. and I'm certainly trying).. but for now? It's working great, and I appreciate the rom.. even if I'm using it extremely wrong (sorry)

I did read the a_b tutorial you wrote. I'll read it again. I'm trying to figure this stuff out, but it's a lot.. and I tend to break stuff anyways. But I'm trying.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
I wasn't upset or anything, or taking it like an argument, if that helps...

Just having that "I'm tired, I'm trying to write this quickly; I can tell this is a technically proficient person who is used to some paradigms and they're actually potentially going to cause themselves problems if they carry that into this new territory, so let's see if I can explain this quickly... greaaaat and now my technical-fixation-spectrum-related tendencies are showing."

I can wholeheartedly appreciate wanting to do a clean install; and figured you'd want to know what's going to facilitate that, vs what's actually potentially UNhelpful... that is, there's going through motions because it's good practice even if not always required, vs. actually "doing it wrong". In the case of this device's peculiar hard-A/B-slot-switching configuration, erasing the contents of current slot's system & vendor partitions is "doing it wrong"; and you seem far too technically astute to be caught doing that. ;)

That's all I was trying to convey; "here, have some useful info as to why!"

Sorry I missed that it was supposed to be "amusing anecdote"; Google Apps and slot switching is... like that sometimes, yeah.

No need to apologize; you didn't do anything wrong by trying to talk about it!

I'm very glad you're enjoying things!