yashsingh1/xdaforums huggingface dataset:
[OnePlus 11] xSnowLeopardx:
Let's say, I accept and know all of this. How come my battery experience got so bad after going from OOS13 to cr. It makes no sense. Really thinking about going back...
[OnePlus 11] kdrv3xc:
well naturally it's expected to have battery life on stock. that's a given. but personally, i'd take 50% battery life over OOS any day. the week or two i was stuck using that i absolutely hated it.
[OnePlus 11] xSnowLeopardx:
We're really different people in that regard then haha.
[OnePlus 11] kdrv3xc:
haha maybe i was being a bit hyperbolic there. i'd probably just get a different phone if that were the case. but stock lacked so many quality of life features that i've grown so accustomed to. style/customizations aside, things like long press for torch, natively being able to change tracks by long pressing volume buttons, acceptable display scaling, the ability to have more than 2(!) columns for QS tiles, no custom lockscreen text, no way to change the function of the alert slider, no clear all button for recents or notifications...like what am i supposed to dismiss every single one of those individually? that's absurd. and i'm sure there's more, but i don't even want to try and remember them.

it has no pulse visualizer. i hate to admit it, but however stupid that might be, that's a deal breaker by itself for me.

edit: ok, i don't think i was being hyperbolic at all. actually might have been a bit too reserved. i'd take 40% battery over stock. especially considering i can charge this thing quicker than i can toast a bagel and eat it.
[OnePlus 11] xSnowLeopardx:
I can imagine your choice then (: but I am glad that none of these things you've mentioned bothered me that much. I will wait for a few days / a week and see how others are experiencing this. I really doubt I'll stay on cr if nothing happens, since I tried doing nothing differently and doing a lot to improve battery -> nothing helped. It's just VERY interesting that I experienced battery drain the moment I changed to this rom lol.
[OnePlus 11] m0han:
@kdrv3xc, @xSnowLeopardx, Have you guys tried the latest build available on SourceForge? Says .... performance improvements, trivial fixes...

Wonder what that recovery is for? Are we supposed to flash that first? Or, for people who don't plan to update the rom, would it be good if this new(?) recovery is flashed over the existing one?
[OnePlus 11] m0han:
You've got company :D
[OnePlus 11] kdrv3xc:
if you're already on crdroid, you shouldn't need to flash the new recovery first. it's probably there because the only other recovery image was in the crdroid-install-v2/3 folders, and they were dated. though i could be wrong here, so don't take this as gospel. flashing the update also flashes the updated recovery anyway.

maybe i'm the outlier then. though to be fair, i've gone hard on optimizing it as much as i possibly can. from underclocking the cpu (which i could probably underclock even more without noticing it to be honest), changing the governors and I/O schedulers, restricting every app that doesn't need to do things by itself.

out of curiosity, if you did install BBS or FKM, what's it reporting your idle drain as? that's a decent metric to go by. it very well could be your phone is just reporting the wrong charge level. you should try giving it completely full discharge then charging it back to 100%. if that's the case that should help it recalibrate.
[OnePlus 11] m0han:
New downloads available - Recovery and ROM.
[OnePlus 11] xSnowLeopardx:
What I'll do:

1) completely full discharge then charging it back to 100%

2) See what the new downloads bring

3) And think about a back up of my files to go back to stock + root. No idea how I can do that efficiently, and how I can get it to work with play integrity / Safety Net, which did not pass before going to cr...
[OnePlus 11] kdrv3xc:
yeah i know, but you won't need to flash the recovery to update. you could also just push the zip to your phone and install it via the built in updater using the local update option.

sounds like a good plan. hope it works out for you.
[OnePlus 11] smokljo:
I can't make it work...i do it all as per instructions, and get a boot loop when the logo starts flying.

Tried crDroidAndroid-13.0-20230830-salami-v9.8.zip and crDroidAndroid-13.0-20230904-salami-v9.8.zip. With and without Gapps. The logo starts flying and then it freezes. And restarts.

Going back to fastboot works, I can redo everything successfully (from step 1), but still can't get it to boot. CN version here, got it as a present. Will try crDroidAndroid-13.0-20230903-salami-v9.8.zip if that works.

Edit:

Same with crDroidAndroid-13.0-20230903-salami-v9.8.zip :(
[OnePlus 11] smokljo:
I guess I messed up big time somewhere in the middle. LineageOS freezes at boot as well.

When i typed fastboot -w I get:

FAILED (remote: 'Erase of userdata is not allowed in snapshotted state')

fastboot: error: Command failed

Also when in Fastboot mode this is the printout:

PRODUCT_NAME - kalama

VARIANT - SM_ UFS

BOOTLOADER VERSION -

BASEBAND VERSION -

SERIAL NUMBER - "the number"

SECURE BOOT - yes

DEVICE STATE - unlocked

Why doesn't it show the bootloader nor the baseband version? Is this ok?

Edit:

I tried again and fastboot -w worked, so i repeated it all...but still same. EDL for me?
[OnePlus 11] Ćwirek:
I think this module does absolutely nothing. I will check something else and share the results in a week or so
[OnePlus 11] AkayamiShurui:
Going to recovery mode and factory reset
[OnePlus 11] xSnowLeopardx:
6-9-'23 | Update on my battery struggles.

- Followed @kdrv3xc 's advice on completely discharging, then charging it back to 100%. It's now sitting on 100% for ~30-40 mins with using it for small things (WhatsApp, bit of browsing, Outlook).

- I also still have the small underclocks active with FKM. I probably won't do this if I end up changing to Arrow OS or OOS.

- Will test for this week and see what I'll do on Saturday (this gives me some days to test, and if I need to change ROMs, it gives me time on Saturday to back up and change).

- If the battery experience is close to or identical to what I had on OOS13 = I'll stay.

- If the battery experience is the same as what I had before fully discharging and testing = I'll switch to either Arrow OS or OOS. Maybe I'll try the former first, and if that gives me back battery experience as well, then I'll go back to OOS.

Will update y'all, since I think it's fair to do so.

_____

Edit

I don't think Arrow OS is available for OP11... Might need to do more research for an alternative, or choose the OOS anyway.
[OnePlus 11] m0han:
FYI: TWRP Recovery seems just around the corner. Test builds and discussion you-know-where.
[OnePlus 11] xSnowLeopardx:
Since I am still a big noob when it comes to all of this: what would that give us? And where is you-know-where haha
[OnePlus 11] m0han:
I understand it makes Android-life a bit easier for us. You can backup and restore data. If we get TWRP-flashable ROMS (which we should), ROM-hopping would be fun; PC would not be required. You-know-where is 'that social media app/platform' that is frowned upon here.
[OnePlus 11] xSnowLeopardx:
That starts with an R? If not, then I am oblivious.
[OnePlus 11] m0han:
Starts with a T :censored::giggle:
[OnePlus 11] xSnowLeopardx:
Oh. The one that basically got a new name that does not have a T in it anymore?
[OnePlus 11] kdrv3xc:
that's what i get too, then what i consider typical drain after it sticking at 100% for longer than seems normal (turns out you can actually charge batteries past 100%...supposedly not the most healthy thing for the battery, but if i could charge myself over 100% i probably would, so why not my battery too?) — though is that an improvement to what you were getting before?

i agree. maybe on non-flagship class phones that will make a difference, but not on this thing.

TWRP would be fantastic, more so pitch black recovery, just tried that on an old samsung tablet i've been meaning to figure out something to do with and was very impressed.

To further elaborate on this, it makes sideloading possible without directly connecting to another device to actually push the .zip. If the .zip is stored on the external storage/sdcard it can be flashed natively in TWRP. Also the backup/restore of any partition (especially /data) is a major quality of life improvement. Other features include native terminal, MTP support and built in file explorer and some other less used things but nice to have.

But pitch black recovery does all that too. and it comes in black.
[OnePlus 11] kdrv3xc:
Does it start with an X?

now i feel compelled to post that picture of jules from pulp fiction asking a similar question but i'm not sure if that behavior would be frowned upon by our wholesome community.

edit: this will have to do
[OnePlus 11] m0han:
Sharing my experience so crDroid users here are aware:

I was running the 30-Aug build and decided to update to the latest build available then (06-Sept). I had flashed TWRP Recovery by then and was already feeling elated thinking I could go rom-hopping at will. Did a full backup (21828 MB in 66 secs.). Cleaned Cache and Dalvik-cache.

Flashed 06-Sept build, but errors were cropping up at every turn. I tried to flash TWRP Recovery to both slots before booting up. Errors galore again. Try as I might I could neither boot up nor save my data. To cut a long story short, I again followed the OP's installation instructions, found myself in crDroid recovery, sideloaded rom and GApps and the device booted fine.

I didn't stop there. Flashed TWRP to both slots, booted into TWRP and restored /data partition alone. Things went well. I'm back up and running almost as before. I say almost 'cos (maybe 'cos) I hadn't logged into my Google account prior to restore, I had to set up GPay again. But, I think if done properly, the new TWRP saves a lot of time and work for custom rom users.

I think I know what to do next time. But, power users and/or devs would help design a better process for this, I hope.
[OnePlus 11] m0han:
Has anyone been able to figure out how the crDroid Recoveries at SourceForge are meant to be used (by users, if at all)? There is one hosted today, but there is no new rom. 06-Sept is still the latest, as of this writing.
[OnePlus 11] kdrv3xc:
sounds like you didn't flash gapps after updating to the 0906 build. you have to reflash gapps, and magisk after every OTA. (twrp now too).

those also aren't official builds...well officially pushed as OTAs. I imagine for a reason. to answer your question, the recoveries are for sideloading the rom, (gapps and magisk) and/or factory resetting (to sideload the rom)
[OnePlus 11] m0han:
Nothing got installed properly. There were too many errors about partitions not mounted. Can you suggest a procedure that uses TWRP recovery for updating to new builds of crDroid by dirty-flashing without errors? Backups can be used for data restore, if needed.
[OnePlus 11] m0han:
This might not be specific to crDroid ROM (and may even be OT for this thread). I am posting here because this is the ROM I am using now. There are three apps for which I wish to enable accessibility permissions (see screenshot attached), but, try as I might, I am not able to get the three dot menu at the top right corner to 'allow unrestricted settings' after which I can enable accessibility permission. Does anyone know how to get around this? I want to allow accessibility permission for True Phone to be able to record calls using the system app without doing anything more in the system app, Nova Launcher to enable double tap for screen off and Screen Master for taking long screenshots with proper stitching.
[OnePlus 11] kdrv3xc:
the app has to declare that permission in its manifest. if you're talking about the "all permissions" screen, that doesn't have anything that can be toggled, that lists what permissions its declared it its manifest. you'll notice that that page doesn't change regardless of what's allowed or denied.

just install the zip via twrp. i'd still suggest using the built in updater over sideloading it every time. you'll still have to flash gapps/masgisk/twrp after every update regardless of what method you use.
[OnePlus 11] xSnowLeopardx:
9-9-'23 | Update

I wanted to say thanks to everyone who helped me with my questions. I have decided to use EDL to go back to stock. Will root it afterwards and see if I still have Play Integrity / SN issues. I would rather not be able to use GWallet than to have battery issues. I really do hope my battery issues are gone when I am back at stock. If not, then I'll have to lock the bootloader and maybe send the phone to OP, or maybe just see if I can find someone in the area to replace it. Oh well. Let's hope it's the rom ^^.

Another update will come telling you all about it. But that will be the last update in this thread (otherwise I am not on topic anymore).

Quick edit

If someone can tell me btw how I can stop the phone (or myself) from (accidentally or not) updating to 13.1, let me know. I have enjoyed 13.0 and maybe the combination of cr + 13.1 gave me the bad battery experience...

Quick edit v2

I disabled the auto system update after reboot. I am now on 13.0 with root. Pass both checks on SN and 2 out of 3 (obv not 3/3) on Play Integrity Checker. GWallet works! ^^ But Netflix does not start. Not gonna use it that much anyway since I have WV L3 only. So far I am happy. If I manage to get Netflix working I will update again. Will also fully drain the battery then charge to 100% and see how my new week (next week) will be with rooted stock.
[OnePlus 11] chocolote4444:
When you sideload the adb update, if you are already on crdroid, will the adb sideload wipe your settings and apps? I haven't seen a clear answer on here about that. In other words, if I go from crdroid 9.7 to 9.8, all my apps and settings will be intact? I'm paranoid of a bootloop and that I'll have to restore all my apps again. 😃
[OnePlus 11] xSnowLeopardx:
Swift Backup (if you have root, you can update data as well)

If you have root -> Magisk Bootloop protector

IMO, an update should not touch your apps + settings, but I am no expert.
[OnePlus 11] kdrv3xc:
no, you'll only lose data by doing a factory reset. upgrading from 9.7 to 9.8 won't affect your data. though, what's everyone's opposition to using the built in updater? actually after sideloading it, you have to sideload magisk again, and then magisk needs to reinstall itself properly, adding a whole extra step that can be avoided by updating normally, and then using magisk app to install itself to the inactive slot. also, it's safer if the update fails; you'll be less likely to get a boot loop, since it can verify itself.
[OnePlus 11] xSnowLeopardx:
Bootloop protector would safe your ass with the last thing you talked about, but yes, always better to do the update method that has no extra steps. Like you said, the built in updater is better for this. (I am back to rooted stock rn, but I do still understand this, that's why I am replying btw).
[OnePlus 11] forever_lol:
I've just updated from 30 Aug To 06 Sep version via built in updater / local uodate. Well it has its downsides:

you can only flash vanilla built (no gapps) - which means you must sideload them afterwards and they don't really work as they should if you did dirty flash.
[OnePlus 11] neobuddy89:
New Update Available

===== 10 September, 2023 =====

- Fixed unlimited storage for Google Photos

- Updated Dialer and keyboard theming

- Other trivial updates

- salami: Updated blobs from CPH2449_13.1.0.591 (EX01)

- salami: Reworked code import from official kernel drop, removed more clutter

- salami: Kernel upstreamed to 5.15.131

- salami: Fixed showing real time current charging info on lockscreen

For download link, telegram discussion link - refer to the first post.
[OnePlus 11] Ćwirek:
I'm still using version from 13.08. Can I just download the latest version and sideload it in recovery via adb commands without loosing any data?
[OnePlus 11] m0han:
Ok. The OP does not mention steps to do an update over a running crDroid rom. Your advice should help people. How about doing a TWRP backup before booting to system and using the built in updater? That way, if data is lost, people can restore. Restore worked for me the last time I tried.

Edit: I tried booting to system and using the built-in updater (my first time). Stuck at 'Finishing package installation' (50%) for more than 25 min. now. What to do? Is this how it is? Can I 'Cancel'? Would the device bootloop? @kdrv3xc
[OnePlus 11] kdrv3xc:
no, there was a firmware update needed for the 0830 build

is that from the notification in the pull down menu? go to settings > system > updater and see what that says.
[OnePlus 11] kdrv3xc:
actually scratch that, mines doing that too. good news is rebooting won't hurt anything, i didn't even bother hitting cancel. just adb reboot recovery, if i got twrp i would just reboot to system, if i got crdroid recovery i would have known the update took and sideloaded gapps/magisk. i'll wait a bit to see if dev has anything to say about it, otherwise i'll try sideloading or installing via twrp.

edit:

actually unscratch that. after rebooting i tried installing the update again, and it was successful. happy to report that correct charging information is displayed.
[OnePlus 11] m0han:
Well, I hit cancel and the system remained working. Checked in About Phone and found it still was on the 06-Sept build. Rebooted to TWRP recovery, tried to install the update and ran into big trouble.

Spoiler content hidden.

If you do an update of crDroid via TWRP please post a (detailed) how-to about:

wiping

backing up

installing rom

installing GApps & Magisk

re-installing TWRP to both slots (as the TWRP dev says)

restoring data...

Well, basically, everything :D. Thanks.

BTW, was your successful attempt at installing the update again done through TWRP?
[OnePlus 11] kdrv3xc:
the successful attempt was via the built in installer. after rebooting to system i just tried the install again then honestly kind of forgot about it for a while, but next time i looked on my phone it was complete. so i can't really say how long it took, but it was less than an hour for sure,

i think it was just hanging out at 50% for abnormally long, i didn't give barely 5 minutes before i said it was stuck. however if i were going to do it via twrp, i'd do it via sideload first, but if you don't have a computer or another android to sideload from and had to use the install function, i'd install the update (probably reflash twrp here, but if i had a computer handy i'd wait till after the following step), reboot to recovery. this should be crdroid recovery. i would then sideload gapps and magisk, then reboot to system then after that was successful (magisk will make you reinstall it via the manager app at this point by now, so i'd do that. then either reboot to boot loader and flash twrp again, or do a normal reboot first if i wanted to be on the safe side.

i've actually just been installing twrp to the current active slot, and it's been working perfectly. i'm trying to build pbrp using nebrassys tree, the build is successful, but it's not booting past the splash screen. adb and everything still works but there's no reason to use it over twrp at this moment. (i think it's something with my fstab). next i'm thinking of a magisk flashable script that will preserve twrp across OTAs but that would actually require having it flashed to both slots, or just having the current image handy but i haven't thought of way to make it less trouble than it's worth.

you don't need to mount any partitions before flashing a zip in twrp, you only need to mount them if you need to access them via file explorer or adb. flashing will mount them automatically. did the update still work via TWRP? if so were the problems after flashing the update? if so then did you reboot back to recovery to relfash magisk and gapps before rebooting to system?

oh and for the backups part, i'd backup right after rebooting to twrp, right before flashing the update.
[OnePlus 11] Ćwirek:
Somehow I must have missed this information. Then the correct method to update, in my case, is this:

1. Flash stock OxygenOS using instructions from this thread:

https://xdaforums.com/t/op11-edl-downloadtool-to-restore-your-device-to-oxygenos-coloros.4607995/ ;

2. Unlocking bootloader;

3. Flash latest crDroid;

4. Root.

Is that corect?
[OnePlus 11] m0han:
I waited close to 30 min., then pressed 'Cancel'.

This is TWRP for me. After I ran into issues, I tried to re-flash TWRP to both slots as advised by the TWRP dev, but sdcard seemed to be 'not mounted'. I couldn't do anything.

So, I've been thinking....

To do a clean install

:

Flash firmware using Update-firmware.bat

In crDroid recovery, do a Factory Reset / Format Data

Sideload ROM

Reboot to crDroid recovery

Sideload GApps

Reboot to System, check everything is well

Reboot to bootloader, flash TWRP to both slots

Restore data from backup (made earlier and saved outside of the device).

Reboot to System and continue using the device as is till the next update.

When next update becomes available

:

Reboot to TWRP recovery

Make a full backup and save it outside of the device

Sideload ROM

Reboot to TWRP recovery

Sideload GApps

Reboot to System, check everything is well

Or

,

Reboot to bootloader, flash latest crDroid recovery from Sourceforge.

Reboot to crDroid recovery and repeat Step 3 to 7 and 9 above.

Hopefully data would be intact and Step 8 would not be necessary.

Please correct or advise if these steps can be streamlined.

After I had to format data and clean install crDroid rom, I 'fastboot-flashed' TWRP without any hitch. The TWRP started, but remained stuck on the loading screen for a long time. adb devices showed my device. I got the working screen only after about 15 min. How can this be resolved? TBH, I'm a bit apprehensive now about rebooting to TWRP if I'm in a hurry.

Step 1/2 was successful I think. It's at Step 2/2 that the errors cropped up. I was able to reboot back to recovery but sdcard seemed to be 'not mounted'. I couldn't do anything. adb devices showed my device, though.

Finally, I had to do a Clean Install from scratch. But, the backup I had made saved me from having to set everything up afresh.
[OnePlus 11] xSnowLeopardx:
11-9-'23 | Update

Back to rooted stock and the battery has been acting way better. See the attached picture.

Removed Netflix from my phone since I don't really use it.
[OnePlus 11] Ćwirek:
What is the battery health percentage?
[OnePlus 11] xSnowLeopardx:
100%
[OnePlus 11] Ćwirek:
@xSnowLeopardx, can you check something for me while you are on stock?

Can you connect a pendrive to your phone using an OTG adapter? From what I remember, the phone often did not want to detect a pendrive connected in this way, and frequently saving data in this way is very important to me
[OnePlus 11] xSnowLeopardx:
I don't think I have an OTG adapter nearby...
[OnePlus 11] kdrv3xc:
i've done that without issue on stock.
[OnePlus 11] m0han:
Just recovered from this (was offline for nearly 30hrs. :mad:): https://xdaforums.com/t/info-forum-down-for-indian-ip-addresses-due-to-ddos-attack.4626569/

Was hoping to hear from @kdrv3xc on this: https://xdaforums.com/t/rom-13-op11-crdroid-v9-8-official-10-sep-23.4610649/post-88989343
[OnePlus 11] m0han:
Saw your post here: https://xdaforums.com/t/recovery-12-unofficial-teamwin-recovery-project.4625181/post-88991673

I'd tried PBRP Recovery on my earlier devices, but didn't find the UI (fonts; not the theme or colour) very appealing. Felt they were not 'proportionate' to the overall UI. Just my thoughts.