yashsingh1/xdaforums huggingface dataset:
[OnePlus 6 & 6T Cross Device Development] Sacloth:
Hello, I'm currently running the 9.13 version of CrDroid on my OP6 and I don't know enough about the technical details regarding the differences between this version and what I've got.

I suppose what I'm asking is twofold.

1) Is it possible to directly install/update this new version of the ROM from within the Updater app manually without having to wipe the phone?

2) If the answer to the previous question is no, is there a guide for backing up all of my data so that I can reload it back onto the device after following the ROM installation guide?

I'm sorry if these are obvious things to know, I'm not very familiar with how these tools work, just that these tools allow me to use this device that I love for just a little bit longer, so I would appreciate any help/advice that could be provided.
[OnePlus 6 & 6T Cross Device Development] tomasz-c:
Please read this entry, there is a fantastic description prepared by Terminator.J:

[ROM][14.0.0_r35][Official]crDroid Android[v10.5r2][May 2024 ASB]

*** Disclaimer *** I am not responsible for any damage you cause to your device. I hope you like reading. You have been warned. crDroid is built on top of LineageOS, and is designed to increase performance and reliability over stock Android for...

xdaforums.com
[OnePlus 6 & 6T Cross Device Development] Rophoe:
For now it runs smooth. But is there a way to bring back a Oneplus Shelf instead google page? I already installed apk from apkmirror, but doesn't seem to be working. I'm also missing for quick search for apps.
[OnePlus 6 & 6T Cross Device Development] espionage724:
I think I saw a specific "OnePlus Shelf" app in Play Store, but on stock OOS 11 I think the shelf is integrated in OnePlus Launcher. Maybe one or the other works better?
[OnePlus 6 & 6T Cross Device Development] Rophoe:
Yep, but it's not available for my device and raw downloaded apk doesn't work. Maybe there is another launcher with this feature? Can You recommend something?

Edit: also fast gestures don't work with AOD. For example I'm using < and > for changing tracks, but with AOD off i can change only one track cause screen turns on, with AOD on it doesn't work at all. What a shame i really liked this feature on OOS10.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Nope, sorry. I don't have a good way to try and make yet more out-of-date OxygenOS 11 apps work on this ROM under Android 14 (like OP Launcher).
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Sorry, can't help ya there either, friend.

I am not as smart as the LineageOS devs upon whom I depend for a stable base for device-specific trees, and they were not trying to make everything work like OxygenOS.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Yes I know what month it is.

I have literally spent the last 2.5 months, in whatever spare time I've had, trying to fix the power/performance issues in a way that will work going forward (and can potentially be replicated in 4.19-kernel-based builds later if/when we go there).

Meanwhile, crDroid 10.3 eventually appeared with March ASB & 14.0 QPR2 merge included, and as usual the devs had to drop all the features y'all like because Google changed things. A week later the Lineage folks merged April ASB and so crDroid source bumped to 10.4.

I'm literally not going to build 10.3 because everyone will complain about missing features, and will go straight to trying to make 10.4 compile & boot & test to see if everything works.

But I couldn't just leave 10.2 the way it was without an updated official OTA release, so here ya go!
[OnePlus 6 & 6T Cross Device Development] Hai96:
The new 10.2 build is running so much better, thank you very much 👍 Performance and battery life improved significantly. On the the last 10.2 build I had sometimes crashes that forced a reboot, the new build doesn't seem to have this issue.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
So, uh, something to note (it's in the release notes, but I want to put it up here for folks reading):

With having fixed the "can't install big GApps packages because inode counts were wrong" problem that I guess was technically my fault since the beginning but didn't start really showing up until after I added Oneplus Camera & Gallery again in 10.2 r1 (which ate up a lot of free space), um, you should probably install from recovery via adb sideload, then adb sideload the last non-QPR2 Google Apps (current MindTheGapps arm64 14.0 or the 20240307 build of "crdroid-official" NikGapps elite package).

I love Nikhil, he's a great guy and does amazing work; but I really just want to recommend MindTheGapps this release cycle considering how things have been going. It's not him, it's us.

Anyway; yeah. Make sure you actually *have* a complete, correct Google Apps installation for later updated going forward by doing an adb sideload install (dirty flash/update) from recovery, rebooting recovery when prompted to install addons, and adb sideloading your current preferred Google Apps zip, then optionally installing crdroid++ kernel if you want KSU, then rebooting system. You know the drill (I hope).
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
crDroid 10.4 (April 2024 ASB, including QPR2 merge) pushed to OTA!

Get it while it's hot!

Includes re-enabled hardware-accelerated VP9 decoding, so Instagram & YouTube & similar won't slaughter your battery life with software decoding. 🥳
[OnePlus 6 & 6T Cross Device Development] shovit...:
Thank you. Will be trying soon. Cheers 🥂
[OnePlus 6 & 6T Cross Device Development] Mindrel:
Great job ! Thanks 😘
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
So, I screwed something up with doze-related configuration in 10.4 release... Which ends up causing a problem with some duplicates LineageOS toggles that are normally enabled by default but didn't actually do anything...

Now they try to do something and fail and that drains a little extra battery.

Everyone should make sure to set the following:

1) Settings > Display > turn OFF "Prevent accidental wake-up" (use the Pocket Mode in Settings > crDroid Settings > Misc instead)

2) Settings > System > Gestures > turn OFF "Lift to check phone" (use Settings > crDroid Settings > User Interface > Ambient Display > Sensor based doze customization settings instead)
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
*sighs*

Those of you investigating "why is the battery draining faster than it should?" have probably opened up a root shell and ran top or htop and noticed that com.android.systemui and system_server are consistently using a lot more CPU% than they should be.

It's not just this device, it's not just this kernel version, it's not just this memory/performance management configuration.

I captured some logs & straces and forwarded to the dev team, and had a few other maintainers corroborate the reports on other devices.

I don't even know, man. I can't deal with fighting this month in and month out when things get broken behind my back all the time. I'll try to keep folks up-to-date with security patches, but it might just be "heavy battery drain season again" like it was with Android 13. Dunno what else to do.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
I think I know what's going on with unexpected power drain, but testing takes time.

Should I just push 10.5 as-is?

Google has already :poop:-listed the updated device spoofing fingerprint, so we're back to "probably won't work for GPay/Wallet" as usual (10.4 spoofing fingerprint got nuked after Google I/O got done and they had time to get back to their usual shenanigans). >_<

Anyway, it's not like it's WORSE than 10.4, and has a couple fixes I'm sure.

And, for now, it's really performant! 😅 A little too performant, but I digress...
[OnePlus 6 & 6T Cross Device Development] tomasz-c:
I think that you can wait with the release until the power consumption fixes.

By the way, I'm happy to know that there is something wrong with the power consumption ;), because I thought it was only with me that something was consuming the battery excessively, and I couldn't determine what it was.

Can you share what is the cause of power consumption?

Thanks for your work.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
If I knew, I'd tell ya.

Spent a week trying to eliminate possibilities.

Spent all day (and about to end up in a second day) running `git bisect` on 806 commit history in frameworks/base/ to figure out at what point SystemUI starts eating ~40% of one CPU core constantly, even when the screen is off.

That's compiling/flashing/testing 9 test builds now into the process, and there are still two commits left... then trying to figure out if we can live without one or the other (or both) of them, or how to rework things if not.

But I guess we're CLOSE to figuring out the actual source of the problem!
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Been a busy day!

- constant background power drain from SystemUI (introduced after QPR2 merge) is now fixed, huzzah! 🥳

- general performance tuning to make it more battery friendly (but not janky!) - should be as good/better than 10.2 release 2!

- updated pixel-framework stuffs meaning, among other things, Quick Tap should work again!

- progress toward crdroidandroid organization-level implementation for signing builds with release-keys instead of test-keys, AND updating PPU to pull updated spoofing device fingerprint from an apk that can be updated by user as Google blocks spoofing FPs (rather than requiring me to create updated build of entire ROM & release to OTA).

This feels about right... 6-7 months into release cycle to get things really dialed in.

10.5 release candidate builds cooking now. NOT SIGNED YET, so no changes to installation & no additional warnings at this point.
[OnePlus 6 & 6T Cross Device Development] dirtyl0lharry:
Out of curiosity, does the power drain also happen in your CrDroid 9.17 Android 13 builds for Alioth ?

Thank you for your work btw.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Uhh, do I have an evil twin with a ximi sm8250 somewhere?

I have never built anything for alioth, my friend.
[OnePlus 6 & 6T Cross Device Development] dirtyl0lharry:
I was checking another phone's forum and I got my question mixed. I'll start over again:

Is this battery drain problem happening along all CrDroid 14 or is it just device specific as in only Fajita is affected from it ? In case this is an overall CrDroid problem, does it apply to CrDroid 13 as well?

Im asking this because I've seen multiple users ( from different devices ) complain about battery drain from CrDroid 12 and above but you are the only developer that I've seen addressing this problem so yeah, depending on how this battery drain bug goes on, I might update my devices.

Thank you again.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
It was affecting many if not all devices on crDroid Android 14.0 (and other ROMs using enough of the same code commits to implement the same features).

There has been a NON-global issue for enchilada & fajita at least in Android 13 that seems to plague some users but not others, and I have not figured out how to narrow down what's causing it, since I cannot reliably reproduce the issue (and I'm not experienced enough to understand how to figure it out, much less fix it, based on the logs & info I do have).

So when I write things in the changelogs like "hope this fixes it", it's because, in that scenario, I really don't have any idea and am taking fairly random shots in the dark.

Afaik, if alioth has been having power drain/excessive CPU usage since Android 12, that's something more isolated (device specific, or maybe something common to that combination of chipset/kernel/HALs/firmware/vendor blobs). crDroid in general has not had a massive ongoing battery drain bug for >2 years on all devices.
[OnePlus 6 & 6T Cross Device Development] dirtyl0lharry:
I do appreciate your reply. In the meantime while this gets fixed, at least for Fajita, would you say it is safe to stick with latest LineageOS ?

Thank you again and wish you the best with your work!
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
What do you have installed right now?

I have test builds (for enchilada & fajita) available in the telegram group -- I do most pre-release testing there, and provide support for the official releases here.

But if you're not on TG I can go ahead and copy/paste the test build announcement with links.

To answer your question about LineageOS; it does not have the SystemUI excessive CPU usage bug. It's already signed. In order to spoof device fingerprint for purposes of passing Play Integrity, you would need to root & flash something like PIF.
[OnePlus 6 & 6T Cross Device Development] dirtyl0lharry:
A really old Android 10 HavocOS build on my fajita and CrDroid 9.15 A13 on my main device Alioth.

I'd give it a shot but I dont have the time to jump between test builds and being kind of a betatester even though that would help the development a lot.

Thanks a lot again!
[OnePlus 6 & 6T Cross Device Development] Sacloth:
I'm trying to follow these instructions and have completed everything up to step 5 listed here:

crDroid OP6/6T Retrofit Dynamic Partitions installation guide

crDroid OP6/6T Retrofit Dynamic Partitions installation guide - crDroid OnePlus 6 6T Installation Instructions - Dynamic Partitions.md

gist.github.com

Am I skipping step 6 or 9 to avoid formatting the data?

I suspect it's step 6 but just wanted to confirm before I make any mistakes, thanks!
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Actually the part that would wipe data (internal storage) is step 16; that's the one to try & skip it you want to live dangerously.

Step 6 is clearing the current contents of the GPT partitions that will become the "super partition" backing store, and should definitely be done to be on the safe side.
[OnePlus 6 & 6T Cross Device Development] Sacloth:
Everything Worked! Thank you for the help :D
[OnePlus 6 & 6T Cross Device Development] alienwolf426:
This is a weird one, but for some reason none of the apps are sending notifications anymore. I've checked that the Phone is not in DND mode, and because it looks like all apps are not sending notifications, so it can't be battery optimization.

any one got any ideas about this?
[OnePlus 6 & 6T Cross Device Development] Sacloth:
I spoke too soon.

I'm experiencing 2 bugs:

One where the install/update button does not function when I attempt to update apps from outside the play store or install apk files. The Cancel button works consistently, but the install/update button will not work.

Also one where I cannot grant accessibility control of the device to any apps. Every time I attempt to allow an app the permission, it returns the error:

"Because an app is obscuring a permission request, Settings can't verify your response"​

I went into my settings and have disabled display over other apps for all of my apps except the ones I want to allow and still get the same error message.

Is there anything left that I can do short of clean flashing the ROM and formatting the data?
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Dunno, I guess you could try doing something like enabling developer options, allowing rooted debugging, then hook up the USB cable, open a root shell (do `adb root` then `adb shell` and you should have a `#` prompt), and do something like `pm list package | grep -i settings` to return a list of all settings-related packages, and then do `pm clear <packagename>` for all the ones that look relevant (like, ignoring the overlays & RRO packages).

Maybe even clear runtime permissions and re-grant permissions for stuff afterward.

But you don't need to re-do the flashing process if you decide to factory reset, just... back up everything, reboot to recovery, factory reset (formats data & will erase internal storage), and reboot to system.

If you decide to go that route.
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
(stupid bbs code doesn't turn do markdown & turn `__` into inline code formatting *grumble*)
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
Anyway, so now there's some kind of potentially grody wifi-related battery-draining bug, but it's -- again -- across multiple kernel versions & multiple SoCs and doesn't appear to be related to having GApps installed (happens on microG as well), so... or maybe it's fixed since the last release candidate of 10.5 I built.

Honestly I can't even tell anymore.

I should just push the last release candidate so y'all can enjoy Play Integrity passing again and the SystemUI power-draining bug being fixed for the next few weeks while everything goes to hell in a handbasket upstream because of 14.0 QPR3 getting merged... :P
[OnePlus 6 & 6T Cross Device Development] Sacloth:
I attempted to get started, but I cannot re-enable USB Debugging for some reason.. The same bug affecting all of the update and installation prompts is also affecting the dev setting.

The setting and button to enable it are unresponsive when I tap it.

Is it possible to enable the USB Debugging setting if I can connect to the phone via wireless debugging?
[OnePlus 6 & 6T Cross Device Development] meMohanR:
Boy oh boy this rom is become my favorite after using a single day. Just installed few hours ago.

I got 2 minor bugs for now lets say.

1. Snapchat is not logging in

You might think there's something wrong with my account! No. This happened with me before with evolution x, superior Extended os. If I use Official Oxygen OS then it let me login perfectly. This problem might be local I can agree but this is what is going on with my account.

Error is saying too many login attempts even I tried 1st time after installing. After 10.5 update this is issue has been resolved for me (OnePlus 6). While 2nd one is still not working 👇🏼

2. WhatsApp is not letting me login.

It's saying it's not official WhatsApp App, download official one. Same issue as above.

On stock rom it works perfectly. With custom rom I don't know what's the issue.

This problem appeared to be fix since I can login into WhatsApp now after 10.5v2

These problem might be local to me. But if there is something buggy in rom you might wanna check.

Other I'm loving it. The customization and everything is perfect.

Thank to awesome devs for keeping this device alive.

Edit : After July 2 update both problem are gone for good. Again these problem might be local to me to still now it's fixed.
[OnePlus 6 & 6T Cross Device Development] shaca:
hello guys

the battery problem is solved?
[OnePlus 6 & 6T Cross Device Development] Mindrel:
Hello, I think it will be in the next update.
[OnePlus 6 & 6T Cross Device Development] Mindrel:
Hi!

Enchilada or Fajita? Sorry but on my device (Fajita) I have no problem with WhatsApp.
[OnePlus 6 & 6T Cross Device Development] meMohanR:
Enchilada. I've researched a lil bit and found that some custom rom had that problem including those I've mentioned above. I think somehow WhatsApp checks kernel or rom or something and just don't let the user login. And same with Snapchat.

Though I've successfully logged in using my friend android device to login WhatsApp then sync it to my laptop. Then uninstalled it from that device. I know it'll ask to confirm someday but for now at least I can access for few days or so.

Same with Snapchat. I can login using web. Just app is non responsive. Hope dev will find the way around to that problem.
[OnePlus 6 & 6T Cross Device Development] Mindrel:
OK, I see.

Maybe you could try rooting it, hiding Magisk from WhatsApp and using "play integrity fix"?
[OnePlus 6 & 6T Cross Device Development] meMohanR:
Hmmm. I didn't think of that. But question : if play integrity is some how broken or something I shouldn't be able to use any other banking apps or like that, right?

Well I'm gonna try for sure. If it fixes the problem that's another win.

Thanks for the suggestion. :D(y)

Edit: Didn't work with play integrity fix also.
[OnePlus 6 & 6T Cross Device Development] shaca:
Hello, tnks for the reply.

Any idea when that version will be out? just asking because i was thinking about installing this rom, maybe i will wait for the next version.
[OnePlus 6 & 6T Cross Device Development] Mindrel:
Sorry about that. That's what I thought, but I had to try anyway.

I'm out of ideas. 🤷🏻‍♂️ It must be specific to this device/rom.

Hello,

No, I'm sorry, that's all I know. The developer maintains this ROM in his spare time and has a busy life.

I'm sure he'll let you know soon 😉

His latest message is recent.
[OnePlus 6 & 6T Cross Device Development] meMohanR:
If you wanna try it just try it. Don't have to wait for the update if there isn't any specific reason. After a long time this rom become one of my fav like having navigation customization similar to evolution x with 2 button only. Multiple customization options from any other rom you might have seen.
[OnePlus 6 & 6T Cross Device Development] meMohanR:
Yup thanks any way. I'm also out of idea 😅.

Yes seems like device specific. I had same problem with evolution x after last EOL update. But I kept it because of it's customization. But I always prefer lastest security patch also so I switched to Superior Extended and boom I was able to use WhatsApp but snap chat had same issue.

Oh boy I got so much trouble for almost week with my device with nv error, imei removed etc etc.

Long story short I flashed official rom and every apps was working perfectly.

But yet I needed a custom rom. So I searched and tried some but love this rom.

Hope this issue will be fixed in future by dev if they got chance.

Thank for reading a long story 😅
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
I'm always busy, and part of my "not burning out" strategy is to take care of family & real-life work first.

There's a good release candidate in the Telegram tester group (link in first or second post).

I'll upload it "when I have time", but I have three school-age kids and am married to a teacher, and school just got out, and the temperatures just shot up from "Junuary" to "SUMMERTIIIIIME" so I'm trying to get our little backyard pool rehabilitated so the kids don't die of boredom/heat, and my little worker-owned event production company is shifting into busy season so it's my turn to spend even less time than usual on the ROM. 😅

I do want to get the May ASB release out there though; it's really solid I think.

Part of the delay has been tracking down TWO major power drain issues in frameworks/base/ (that affected all devices using crDroid), and then I didn't manage to take care of pushing updates OTA builds on my OWN devices. Whoops. Thank you everyone for your patience, you helped make life better for everyone else. 😁
[OnePlus 6 & 6T Cross Device Development] meMohanR:
We are glad for your time. Everyone appreciate 🤩. Thanks TERMINATOR.J in Cap obviously. 😅
[OnePlus 6 & 6T Cross Device Development] shaca:
Sorry mate, didnt want to make extra pressure, enjoy your family, ill install the ROM when you have time to release it... tnks for your time!
[OnePlus 6 & 6T Cross Device Development] Terminator.J:
It's not extra pressure; I appreciate the sentiment, and I wanted to let folks know the current status.

Thanks everyone for being gracious about family & real life coming first!

Speaking of "current status", I'm getting things ready to upload now...

Perfect timing since LineageOS merged their June ASB (Android 14.0 QPR3 trunk merge/rebase) earlier this evening... 🤪