yashsingh1/xdaforums huggingface dataset:
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] SLAlmeida:
I reset the phone, and did all the recommended operations again, including all downloads.

The problem still remains, but there is a way to solve it:

1. Settings - System - System navigation - Gesture navigation - Uncheck the Navigation Tips option.

2. CrDroid Settings - Navigation - Check the Navigation Bar option.

Just like that, I made the navigation bar disappear from the screen, and the gestures work again.

To me, as a beginner it seems to be a bug.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] gap30:
oops realised my error I did not follow instructions on screen to to boot to recovery and navigate to to advanced
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] theslam08:
You must use an app like AccuBattery to investigate. I just did a base test to help show the ROM is fine and has excellent battery life. Something else is going on, non-ROM related.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] theslam08:
Not sure what ROM you were coming from but unless it was the previous build of this ROM, you always need to [unfortunately] wipe data when installing these ROMs. Some have success jumping from one ROM to another without wiping but you will most likely run into problems doing so. Many factors in play like different android bases, different cherry picked features (so different code), different kernels, etc. etc.

Seeing how you "formatted data" (which is a wipe), you should be good to go. Following the OP (original post) guide on the first page for a "Clean Install" (when coming from another ROM) is basically required. If you're updating you don't usually need to wipe, which the OP states how to do this.

Also just going to throw this out there (because I feel like you may not have read the instructions on the first post), hopefully you flashed the firmware file it says to flash and followed those instructions fully. Otherwise, you'll have other issues.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] draentor:
Thanks for your detailled answer.

My answers are purely based on my observations. I was using Crdroid 7 (non-rooted, MicroG with flashed .zip) for a long time, and 3 weeks ago, I wanted to try Crdroid 9.

I tried LineageOS+MicroG 19, LineageOS+MicroG 20, Crdroid 8 and Crdroid 9 in a span of three weeks.

LineageOS+MicroG 19, stock, obviously no gapps, OOS 11 Firmware

LineageOS+MicroG 20, stock, the same, OOS 12 Firmware

CrDroid 8, rooted with Micro Revived Magisk Module, OOS 11 Firmware

CrDroid 8, rooted with Micro Revived Magisk Module, OOS 12 Firmware

And from all those tests, with the same daily usage, CrDroid 9 is draining battery faster than usual. But I don't have precise numbers to show you, I'm just look at my phone, remember the battery percentage before going to bed and check it out when I wake up to see there is something that's not working as usual. I do the same thing during the day, and when I saw the battery percentage drop in idle, then losing 2% at a time while using it, it confirmed my suspicions.

For now, I'm gonna MSN my phone, go back on a clean CrDroid 8, then upgrade to OOS 12 and CrDroid 9 in a few weeks :)
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] theslam08:
Hm yeah I'm not entirely sure. All I can say is to save you time/headache/hassle, just do yourself the favor and try using the AccuBattery app and see if the phone is going into deep sleep like it should. I utilize it on every ROM I use - as some ROMs are not as well optimized as others and can cause the phone to not deep sleep like it should and I like to see that, number/statistic wise.

But maybe it's the gapps you're using. Try the nikkgapps linked in the OP (or HERE). You can use the omni version I believe (maybe just check the .config file in the azn folder that PixelLauncher is not =1) or smaller (like basic/core). Or download the full and use my config file HERE.

And yeah it may be worth starting over with the MSM tool, as I'm not sure how good it is to be bouncing back and forth between OOS 11 and 12 firmware like that - the partition data might have gotten mixed up.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] an_cr:
Thanks

Thanks for the explanation. I updated from OxygenOS 11 and flashed the firmware via the firmware update tool provided by the OP. I previously only flashed Lineage OS on an old Xiaomi device and the process was somewhat different so I was put off by the data wipe right before booting into system. Anyways, everything works fine now.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Firetop:
No, this is actually incorrect. What I actually mean, was it was a rom specific bug, which was later "fixed".

Please look at the report before assuming: https://github.com/crdroidandroid/issue_tracker/issues/46

Feedback was asked by the developers, I casually gave my feedback I still had issues, and the bug report was closed anyways. Now I don't care about the fact that it was closed because the original reporter confirmed an improvement. However as I originally said, I was merely saying if everyone else is also having issues to open another so the developers are aware it's not fully fixed. Is that not the correct process? The answer is yes it is...

As for this AccuBattery recommendation, this is great! Many thanks. :)

Maybe in the future the developers can add this as a suggestion in with any reports of battery issues? At least before completely closing it. If people are still complaining, basic logic says they might want some help identifying root cause and troubleshooting the issue, maybe throw a recommendation like this in to help troubleshoot the issues instead of assuming a "rouge app" with literally no evidence of that yet.

Let's be honest here; It's kind of dumb to expect everyone reporting bugs to be a genius at also troubleshooting them, a bug can be experienced without any coding or programing knowledge, so lets drop the expectation of only complete bug reports from someone who already troubleshooted the entire issue, which is unrealistic and stupid to be honest.

For the battery questions at hand; I currently have the ROM fresh installed.

Was installed net new yesterday evening after I returned my phone to OOS10.

Yes I restored my apps to see if it was a rouge app, and installed accuBattery as recommended.

Charged to 90% and left it unplugged all night. and I go decent results I guess?

But I don't see anything about deep sleep being used unless im not looking in the right spot?:

Maybe I'll give it more try tonight and also let it charge fully to 100% instead of 90.

Incase that makes a difference for calibration of the app.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Firetop:
As for this error, this is a common mistake for someone coming from a different ROM and is somewhat new.

Because the instructions in the primary post are not clear at all as found below:

What the heck does that mean? Put yourselves in the shoes of a new person?

If I flashed the firmware first, as it's legit one of the first steps, then I'm supposed to skip to an undetermined step?

Does that highlighted sentence mean to start at the factory reset step? No. It says to start at the install crDroid.zip step exactly as mentioned?

Clearly to anyone with knowledge already, the answer is start at the factory reset step, but no where does it specifically say that, it says to start at install crDroid.

And no, it does not specifically say a factory reset/wipe is required on a clean flash, it's just a mentioned step which could potentially be skipped if your new to all this? Esspecially if you don't know what the firmware flash tool does, considering the typos in the script saying:

ECHO "You will not get redirected to recovery in order to install crDroid" instead "you will now get redirected"

Maybe as a new person you assume it also wipes at the end? considering no instructions clarify this in the firmware flashing bat file or the primary post. All it says is to start at "install crdroid" which will cause you to get the error he mentioned after the flash. Things can still be improved for sure
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] LedgendaryEpics:
Same thing here, it was great when I first flashed the rom, and afterwards would drop 2 to 3 percent at a time. Ex. I'm at 97% for about 10 minutes (great!) Then on minute 11 I'm at 94% (not great!)
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] turbotorsten:
I saw this mentioned elsewhere to be due to the Device source (reporting the battery in those intervals?).

So those results are pretty wild to me (on a positive note). I'm using AccuBattery too all the time, but I'm getting "average battery usage" for screen on: 16,7%/h and screen off 4,0%/h. This could very well be to (social media) apps I'm using.

What is more interesting though is that the discharge rate with screen off. Mine is 9,0%/h "awake" and 1,9%/h in deep sleep, where yours is literally 0.0%. This might be a wrong reading due to the fresh install, but leads me to believe I have some kind of wakelock that is causing issues.

Does anybody know how to identify / find wakelocks?

Edit:

I just saw the post by @theslam08 with his stats and your deep sleep drainage would calculate to 0.74%/h I believe. This is 1/3 of the one I'm getting. Now I don't know how wakelocks count into this (normally they should reduce deep sleep and don't affect deep sleep drainage, right?), because my phone is going into deep sleep overnight as expected.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] an_cr:
I agree, instructions for people new to this space are unclear which is why it took me 2h longer to install this ROM compared to LineageOS.

But overall, these instructions are better than for most other ROMs I've checked out here at xda. I learned something new and everything works alright now so thanks to the dev for making an awesome ROM.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] LedgendaryEpics:
It took you two hours? For me it took me 15 min, the instructions couldn't get clearer for a seasoned enthusiast, for most maybe an hour at best? What were you having issues with? So in the future we can include the issues in future Roms.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] an_cr:
Well I'm a complete beginner in this space which is likely a big reason it took so long. For a season enthusiast it is probably quite clear.

I had an issue where I flashed gapps but when I loaded the ROM it didn't have any gapps. I don't know why that happened but anyways I had to revert back to OxygenOS. That part probably took the longest.

Then later I had the issue I described previously with formatting data after installing gapps and rebooting into system. I researched a while about it on the internet but eventually went for it.

I don't think the installations steps are very unclear, as previously mentioned, they are better than most on xda. However, for complete beginners there could have been 2 more lines e.g. after firmware tool the recovery is flashed so you can skip that but do a factory reset. But I guess we all have to learn it one way or another.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] turbotorsten:
there is this:

guide to install which is pretty good I think, and for gapps you can use the tutorial by @theslam08 a few pages earlier.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] draentor:
May I suggest ?

Step 1 : Backup and prepare

Backup your data on your computer

Reboot to Bootloadermode

adb reboot bootloader

Or rebooting with the dedicated menu, if it exists.

Step 2-A - I don't have OxygenOS 12 Firmware

Download the firmware on the dedicated download page.

Extract it in the platform tools folder, used to send command in adb and fastboot modes

If asked, replace the files.

Double-click on Update-firmware.batto launch the process

It will install the recovery for you

Ask you if you want to update the modem as well

then you will need to reboot to recovery

by using the volumes keys on your phone

and select Recovery by pressing the power button

In the newly installed Recovery,

Navigate with the volumes keys to Advanced

then Enter Fastboot

When it's done, press Enter in the command prompt and let the script finish.

You will be redirected to the main menu of the recovery

Step 2-B - I have OxygenOS 12 Firmware

So, you already have OxygenOS 12 Firmware

Flash our boot.img in fastboot

You will find it under Recovery on the dedicated download page.

To do that, make sure the CrDroid Boot file is in the platform tools folder

fastboot flash boot nameofthebootfile.img

Replace Nameofthebootfile.zip by the name of the version of the ROM .zip you downloaded earlier.

then you will need to reboot to recovery

by using the volumes keys on your phone

and select Recovery by pressing the power button

Step 3 - Finish the installation

In the newly installed recovery, go to Factory Reset

You can navigate with the volume keys and confirm with the power key.

Confirm the factory reset

Back to the main menu by pressing the little arrow at the top.

Go to Advanced, and select Reboot recovery

Select Apply Update then Apply from ADB

You will now use the command prompt to send the CrDroid rom to your phone.

To do that, make sure the CrDroid ROM file is in the platform tools folder

In the command prompt, type

adb sideload Nameoftheromfile.zip

Replace Nameoftheromfile.zip by the name of the version of the ROM .zip you downloaded earlier.

It takes a moment, don't panic and let it work.

Once completed, if you don't want to install Google Apps, go back to the main menu and press Reboot system.

Step 4 - Install Google Apps

Once completed, you can install Google Apps, if you want

You will find dedicated Google Apps here.

Look for the most recent version

To understand the differences between packages, you can check here.

To do so, go to Advanced, and select Reboot recovery

Select Apply Update then Apply from ADB

You will now use the command prompt to send the Google Apps .zip file to your phone.

To do that, make sure the Google Apps .zip file is in the platform tools folder

In the command prompt, type

adb sideload Nameofthegappsfile.zip

Replace Nameofthegappsfile.zip by the name of the version of the ROM .zip you downloaded earlier

It takes a moment, don't panic and let it work.

Once completed, go back to the main menu and press Reboot system.

And, it should be okay ! :)

If someone wants to add, modify, comment, let me know !
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Jeffrrey:
Hello,

Crdroid13 works great but I found two details that do not work properly.

1. Messenger from Facebook is not showing pictures when I want to send them/not showing emojis. Only camera and voice recording are working. After clicking I have to go back two times like it went to "choose a picture to send" but nothing really happens. Using Messenger Beta but older versions have the same problem.

2. I have a problem with sync. It's on but sometimes It only starts syncing when I wake up the screen. Sometimes I got tons of old notifications like I would suddenly turn on the internet but It was on all along and I already seen them.

Are there any advices what to do?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] gwolfu:
Build 20230127 is ready

Changelog: https://crdroid.net/guacamole/9#changelog

Download: https://crdroid.net/guacamole/9
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] theslam08:
4%/hr is not great at all with screen off (and 9%/hr while awake but screen off is definitely not good). Can you take a scrolling screenshot of AccuBattery (Discharge) after charging from like 75% or less to 100% and going like 8hrs with it off the charger? It will be helpful to see the numbers it says for how long it's been in deep sleep and how much mAh was used out of the 8 hrs. Also if you can take the scrolling screenshots [one] with the "battery usage" and [one with the] "discharging speed" apps list showing. It will show more accurately which app has been draining more battery throughout the 8hrs.

Wakelocks happen when apps like facebook (just as an example) is constantly updating in the background - causing the phone to always be bumping the CPU. That's why Google implemented the "network optimization" or whatever it's called - it dials the app updates back by like half so the CPU can sleep more when it should. But that is the exact reason why the disclaimer about it says "delays in notifications can happen with this enabled". If you find a rouge app (an app constantly updating) you could look into an app that will help freeze/sleep these apps when you want - I read in the past of this app many claimed worked well I think called IceBox that will allow you to stop the app from updating when you want. Like throughout the night while your sleeping, or at work or something. But you have to find this rouge app first. Looking at (and posting the screenshot to) AccuBattery will help pinpoint this.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] draentor:
@theslam08 From which version of OxygenOS did you came ? How did you flashed CrDroid 9 ?

I can try to upgrade the stock Oneplus 7 pro with official updates and Oxygen updater, then flash the firmware and retry Crdroid 9.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] theslam08:
👍

A very good guide/tutorial. You covered every point I think (including the part of reminding them to make sure the file is in the platform-tools folder - I think many don't understand that part). It doesn't cover the basics of getting the phone unlocked and all that but that is perfectly fine - there are many guides out there that explains that. For getting going on this ROM, this is great..

I'd only like to point out (just because you were so thorough anyway) that maybe just reminding them to:

Select Apply Update then Apply from ADB

in the step 4 you have there. I mean they should be able to gather that from the previous step, but to be thorough, maybe adding that would be good.

Maybe tag the dev with that guide and he could put it as OP instructions - might help him with less confused members.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] theslam08:
I have the T-Mobile branded version so when I MSM I have to start with the conversion to global every time - which is OOS 9.

Then I go through the OTA for each Android version, OOS 10, OOS 10 again, then OOS 11.0.9. I stop there and bootloader unlock. I think OTA is better than just flashing straight to A11, but I could be wrong and may make no difference.

Then I just flash the firmware file (provided in this ROM OP) for A12 and proceed from there - just like your instructions you just posted earlier.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] turbotorsten:
I was planning on charging my phone to 100% before going to bed so I can show what i meant, as the stats were reset because I charged a little during the day. Sadly AccuBattery only shows foreground app usage, but I'll take a look at IceBox to see if I can sort out a few suspicions.

As you said, 4% / 9% per hour is not good, but can totally be due to me using the phone mainly for social media. The really weird thing is the deep sleep/ over night drain as I always put my phone into flight mode, which should (?) sort out the network optimization thing, unless the apps still wake the device to check for internet, which would then be visible in less deep sleep I guess.

Anyways I will return with statistics once I got some usable ones :D
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] LedgendaryEpics:
To flash gapps with this ROM you would have to download nikogapps from front page, boot to recovery on phone, then use adb sideload to flash it to device.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] theslam08:
Yeah unfortunately if you charge even for a minute the stats change 🫤. But I guess it makes sense - it's just how the app works. A history page of the that info would be greatly helpful.

As for the "only shows the foreground app usage" there are button/tabs you can click labeled "Battery Usage" and "Discharge Speed". I will attach an image outlining what I mean. Take a scrolling screenshot with the battery usage showing there and another with the discharge speed showing there. They are both helpful to determine if you have apps that are draining a lot of mAh.

As for the "flight mode" - that is an interesting one. I'm not actually sure what happens to the apps when you do that. I suppose, logically, the apps constantly "trying" to connect to the service (like the facebook network or instagram network, etc.) could cause it to drain more. That is why those numbers that AccuBattery show are so valuable, you can try enabling airplane mode and check the discharge speed numbers for those apps (cuz I'm sure they'll be at the top of the list as those apps are notorious for battery drain) then check those numbers again without airplane mode enabled (after a some time of course, like maybe a few hours). See if the numbers are higher or lower. I can't test that theory as I don't have those apps installed on my phone (I use the computer for that). But interesting.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] theslam08:
Yup he was talking about my post HERE. Which I did explain the nikgapps are needed.

I had only showed that you can use the full version then modify the script to get the apps you want. Because for me, the "core" or "basic" don't have the apps I want - full has what I want. But we can't use the full the way it is because we don't have enough space so the config file has to be modified (+ I wouldn't want to anyway as it has apps I don't want). Which works fine with this ROM. As explained in my post I just linked to.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] LedgendaryEpics:
Why would you want more apps?! I think having gplay shipped is too many google apps! Google, Facebook and Microsoft Edge are all viruses in my eyes and should legally be listed as such!
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] LedgendaryEpics:
Spoiler content hidden.

I think my hotspot was chewing a lot of the battery, but what absolutely killed it was leaving it on idle.

The dip in the graph was when I was asleep.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Epic028:
Different panel modes missing in new build.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] turbotorsten:
So I am currently using battery historian to look through the adb report and I noticed that network connectivity, bluetooth and wifi is always on, even when the device was in airplane mode. Is this an intention by android or is there something wrong going on?

Edit:

I guess this is probably due to Wifi and Bluetooth search being turned on in location settings. Disabled that now. It would be nice if someone with lower doze drain than me could report if they had similar settings turned on during their tests.
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Firetop:
Thank you for the detailed reply.

It's nice to find people still willing to openly discuss things on XDA. :)

As requested, here is a rolling screenshot after fresh re-flashing the ROM and letting it charge to 100% overnight and then using it all day.

I should say It did manage to make it to the end of the day but it was used what I would consider to be fairly lightly compared to how I would use it on a work day.

Any feedback or insights is appreciated (from anyone with more knowledge in this than me).

Seems that my deep sleep used about 3.5%/h at 143 mA
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] Rinku4747:
Is it support warp charging???
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] NqX:
How to install magisk after update ROM?
[OnePlus 7 Pro ROMs, Kernels, Recoveries, & Other D] The_V0id_V0yag3r:
Hi,

I recently flashed crdroid 9.1 (Build date: 2023-1-27) on my oneplus 7 pro gm1913. Everything is working correcty except video playback. YouTube and instagram videos take a long time to load. Even videos stored inside the internal storage dont play.

It seems that it has to do something with codecs. I plan to use crdroid as a daily driver bc i loved it! So any help apreciated...