Ok here we go...No, it's apart of the firmware flashing steps. It prompts at some point to enter "Y" to flash and update the modemA format should not be required.
[ROM][13][OP7Pro] crDroid v9.3 [01.04.2023]
- Thread starter gwolfu
- Start date
Done!Ok here we go...
You guys are the best! Thanks a lot! Not only video play but the phone became faster! It now boots at a fraction of the time that it did before! Flashed magisk again and now it's perfect. By the way what camera app do you suggest?
Done!
I generally stick with the GCam Camera App with the Camera Enhancing Module in Magisk.. Links below:
Google Camera for the OnePlus 7 Family (7, 7 Pro, 7T, 7T Pro)
These are stable Google Camera versions compatible with the OnePlus 7 family of devices released in 2019: OnePlus 7 OnePlus 7 Pro OnePlus 7T OnePlus 7T Pro OnePlus 7T Pro 5G McLaren These recommended versions are based on the work of the telegram group for this phone. Props to Sir Tavares...
Magisk Module for Enhancing OP7 (T, T PRO, PRO) Camera on Google Camera
This is a magisk module that replaces some vendor camera files with modified variants. Created by John Galt. List of changes: Rear Main Camera: – Killed around 100 global registers added by OnePlus. These harm picture quality in one way or another, including adding blurring that remove detail...
How to Load & Save XML Configs in Google Camera Ports
How to import and export settings/configs on Google Camera versions that support this feature.
Thanks!I generally stick with the GCam Camera App with the Camera Enhancing Module in Magisk.. Links below:
Google Camera for the OnePlus 7 Family (7, 7 Pro, 7T, 7T Pro)
These are stable Google Camera versions compatible with the OnePlus 7 family of devices released in 2019: OnePlus 7 OnePlus 7 Pro OnePlus 7T OnePlus 7T Pro OnePlus 7T Pro 5G McLaren These recommended versions are based on the work of the telegram group for this phone. Props to Sir Tavares...www.celsoazevedo.com
Magisk Module for Enhancing OP7 (T, T PRO, PRO) Camera on Google Camera
This is a magisk module that replaces some vendor camera files with modified variants. Created by John Galt. List of changes: Rear Main Camera: – Killed around 100 global registers added by OnePlus. These harm picture quality in one way or another, including adding blurring that remove detail...www.celsoazevedo.com
How to Load & Save XML Configs in Google Camera Ports
How to import and export settings/configs on Google Camera versions that support this feature.www.celsoazevedo.com
I seem to be getting similar results (posted a rolling screenshot on the last page) I didn't use social media that much in my instance, I mostly used Google maps for about 2 hours that day to drive somewhere and back, which I know is a heavy drainer but according to Accubattery thats 610 mAh on a battery reporting 3300 mAh of health?
I also have both these settings on. I turned them off now and will report back in a few.
Does this only impact the apps wifi and bluetooth scanning or the device as a whole?
I don't want really want to impact the speed for things like Wireless Android auto works for example.
No idea, but I can confirm the Wifi being always on is caused by that setting. BLE Scanner is still on, which might be caused by some "nearby" setting, though it was said to have a negligible impact on battery.
I attached the AccuBattery screenshot I promised, though this is after turning said settings off.
Right now I'm testing battery usage on a "naked" install to see if thats just what the battery drainage is or if it is caused by some of my apps.
But dash charging is 15 w and warp charging is 30w what is the time consuming in 100% charge??Yes
Hmmm I though that was cause I was using the power brick from my OnePlus 6, but I just plugged into the power brick that came with my OnePlus 7 Pro and it stays at Dash changing... At first I thought maybe the ROM just calls it Dash changing even if it's warp charging, but looking at the stats it seems to be about 12W to 15W so I guess i was wrong, doesn't seem to support full 30W changing, to be honest I didn't even notice lol.
great to hear man! i actually had so much trouble before i found out too. Glad we could help! Out of curiosity which magisk modules do you use?Done!
edit: added magisk sentence
I use viper4android repackaged, safety net fix and op7 pro camera enhance. For now...
No problem that is what this forum is for, discussions and helping one-anotherThank 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
So from what I can tell, it don't look too bad. I can only "guesstimate" what is good or bad from the "Screen off" time and % used. As screen on % is highly dependent on actual app usage, screen brightness enabled connectivity features (BT, WiFi, etc.) etc..
But looking at the numbers:
- it says you had the test done within 13h 25m
- out of 13h 25m the screen was off for 9h 53m
- out of 9h 53m it was in deep sleep for 8h 19m
- out of 9h 53m it was awake for 1h 33m
- it says it used 3.1%/hr while in deep sleep with screen off
- it says it used 5.8%/hr while awake but screen off
- it says it used 3.5%/hr with awake/deep sleep while screen was off
The 9% "awake" number is kind of high I'm thinking. Though maybe not too bad...it says only 366 mAh was used - which isn't bad IDT. Problem is this is dependent on if you were turning the screen on to do something before or after the phone went into "deep sleep" for the 8h 19m.
See doze won't kick in for probably 15 minutes I think (if it is working correctly and not having wakelocks). So if the screen is off for a few minutes then turned back on then off then back on, like that all day it will never go into deep sleep. So it's slightly hard to tell what the "awake" could be from.
As for "rouge" apps, nothing really looks out of the ordinary. I assume you were using maps, messenger, spotify & facebook throughout this test? If so then yea, nothing really looks bad, like it drained a bunch of battery.
The 3.5%/hr was a combined deep sleep and awake while screen was off, 3.1% was just deep sleep. But TBH, I think 3.1%/hr is high. While in deep sleep it should be closer to 1.5% maybe 2%/hr tops.
Though some of the deep sleep % is also dependent on enabled connectivity as well - like WiFi constantly trying to connect to a bad signal, BT, NFC... there is a feature in the DevTools called "WiFi Scan Throttling" which will help reduce the amount of times the WiFi is looking for a network (while WiFi is enabled) and I believe reduce how much it scans while connected to a poor signal (looking for a better signal). Enabling that may help. Also the "Mobile data always active" you could turn off (if it's on). It will be slower to connect back to your cell network when leaving the WiFi connection but this way while connected to a WiFi network the cell/modem won't be in use. This will help with power drain.
Another way to see what is going on is to wait like an hour of not using the phone and check adb logcat (already have logcat running). If you see a constant same lines spamming the log, it could be something that you understand and might be able to resolve (maybe it IS some app doing something). If the log is slow, not doing much, then that is weird. I feel like something is going on there to have it at 3.1%/hr while in "deep sleep". With some more changes/research that should be able to come down some.
I still think the best test you could do is to do this while overnight, like don't use the phone from 10PM to 7AM then at 7AM take the screenshot and check the numbers. This way, the stats will be clearer and there won't be "daily use" skewing the numbers. If you get something like 1.5% overnight, then something during the day is causing background drain and most likely adb logcat will be your best help in pinpointing what is really going on while it is sleeping.
Yikes...these long posts lol. But hopefully this was thorough enough to help...
Oh and a side note: jeeze it looks like you got yourself a great battery still! Looks like it's still around the original 4000mAh. That's really good for a 3+yr old phone. (I can tell because it says you used 3577mAh and it was at 88% - which I guesstimate from those numbers to be around 4k at 100% used).
lol you don't understand the point of the config file then. As I explained in the comment I linked to, the full does indeed include ALL apps - BUT our phone does not have the space to add them all. So I explained that the config file is used to SELECT the apps you want. The core gapps does not have specific apps I want (installed in system partition), the full does. So, while going through the config file, you can CHOOSE the apps you want, from 1 app to like 15. You can choose to install only 1 if you want. That is the point to the config file.
TBH, the stock/built-in android battery usage charge is useless I think. As your screenshot shows there, I have no clue what went on. It shows everything used 3% or less battery, and you also have a battery increase halfway through the graph. Not sure when the "lowest" point was, maybe 20hrs in? IDK. But I can't personally help in any way with that screenshot, sorry.
Oh jeez you went scientific with it hu? lol I unfortunately can't really understand what that graph is saying. It's showing things active the whole time it looks like but some of it looks to be needed. Maybe too much info there...
As for the WiFi/Bluetooth turned on during my test, I had mentioned I had Data and WiFi only turned on. I didn't think of mentioning location (always forget something 🫤) but I have that turned off (and did during my test). That I'm sure makes a big difference - location is always scanning the cell towers (triangulation) and reporting back to some network (google, etc.).
lol, uhhh you obviously havn't been reading the last few pages. Several of us are posting all about the battery right now (kind of odd, coincidence? idk). Please read what we've all been posting, it could help you (or help you post more better info for us to help you). And just to be slightly informative right now - 3-4hr screen on time isn't great but isn't "abnormal". Screen on time is very highly dependent on what you are using the phone for, screen brightness, is WiFi/BT/NFC turned on, etc. etc. ...use an app like AccuBattery to diagnose better.
Alright well, that was a bit tough trying to figure out this screenshot as I only speak English lol. But thanks for posting the full AccuBattery image. I like AccuBattery, it is somewhat clear-cut. I'm no expert with it but it basically makes sense to me (and seems to be true to its name, pretty accurate I think - though they do say it might take a few charges to get more accurate - so a fresh ROM install and test might not be 100% on point).
Anyway,
So you used 43% in 11h 14m? That seems pretty good TBH. At that rate your battery would last like 25hrs.
It looks like:
- screen off - 9h 52m
- 8h 8m was deep sleep (12.7% used during this time)
- 1h 44m was awake (screen off) (9.3% used)
- 1.6%/hr battery drain during deep sleep
- 5.3%/hr battery drain during awake (screen off)
- 2.2%/hr combined (awake/deep sleep) while screen off
The stat that is most important to me is the 1.6%/hr while in deep sleep. That is the target and a really good number.
According to these stats, I would say there is nothing wrong with the battery drain while you're not using your phone.
With screen on it says it uses 15.2%/hr which I don't think to be too bad either, average maybe. At that exact usage you'd get around 6.5hr of battery life (screen on time).
It looks like you have quite a bit of IG usage, some snapchat and a tiny bit of clash of clans. Maybe a light day or normal day? If it's that's normal usage, then I'm thinking that's not too bad.
But the main point is the deep sleep. It's quite low (in the range of great) and the fact it's activating for just about as long as the screen was off is really good as well. Meaning, there doesn't appear to be any wakelocks.
Also, unfortunately the actual battery health looks like it might be a slight hinderance to how long before it hits 0% during the day. From my guesstimation, it being at 43% and at 1525mAh already, that means you'd be around maybe 3400mAh with 100% used (0% left). So unfortunately, it seems your battery might have degradation (cycles or wear) on it and just simply won't hold as much of a charge as a new battery (4000mAh). We have to understand that length of battery use on these phones will only get worse as time progresses unfortunately (unless of course we replace the battery). But seeing deep sleep being as low as it was + 8hr out of 10hr screen off I think is pretty good. It means doze is working properly I think. I don't believe you have any rouge apps, otherwise "awake" would be much much higher (and as you can see much more of a battery drain than deep sleep as the awake % battery used was almost as much as deep sleep % battery used for 1/8 the time - 9.3% used to 12.7% used).
In the end, I think you're good. Keep the screen brightness down, keep the connectivity services off only when you need them (WiFi, BT, NFC, location etc.) and I think your battery life will be as best as it can be. As I had mentioned to @Firetop, you can try turning on "WiFi Scan Throttling" and turning off "Mobile data always active" in dev tools if you use WiFi a lot - this will help with your battery as well.
Hopefully this will be of some help and you'll be able to enjoy just using the ROM more instead of worrying about "is the battery usage correct?".
Yeah, as I said battery is really good, just the drop overnight got me to worry as airplane mode made seemingly no difference. Anyways, tonight I got as low as 0,86%/h drain in deep sleep with a fresh install, so I am done with my testing and will now setup my phone again. That was a fun little adventure, but it's over now
Nice, glad to hear you've been able to get it resolved (0.86%/h is really good!)Yeah, as I said battery is really good, just the drop overnight got me to worry as airplane mode made seemingly no difference. Anyways, tonight I got as low as 0,86%/h drain in deep sleep with a fresh install, so I am done with my testing and will now setup my phone again. That was a fun little adventure, but it's over now
Hi,
Does CrDroid have the option to hide the navigation pill at the bottom? I know it can be done with magisk but i dont want to root.
Thanks!
Does CrDroid have the option to hide the navigation pill at the bottom? I know it can be done with magisk but i dont want to root.
Thanks!
Yes it has an option under crdroid settings>navigation
I was making a joke lol, battery stats was for three day period as I just purchased this device. ... Also, update fixed my battery drainage so now I'm back up to 10h per day without overnight drainage, than the 5.5 from before. I still have the issue where every so often battery goes down by two percent at a time, but phone still only drop at 10 per hour now.
Hi! What is the best camera app for crdroid 9.1 OnePlus 7 pro?
(Originally: GM1913. After firmware flash: GM1911)
I tried several versions of GCam with different xmls but none seems to have all features and many of them crash randomly.
(Originally: GM1913. After firmware flash: GM1911)
I tried several versions of GCam with different xmls but none seems to have all features and many of them crash randomly.
Similar threads
Top Liked Posts
-
5Build 20230401 is ready
Changelog: https://crdroid.net/guacamole/9#changelog
Download: https://crdroid.net/guacamole/9
Join the chat on Telegram @ https://t.me/crDroidOP7Pro1
From Telegram:
"That's the reason
Your gapps replaced stock launcher and recents control is part of launcher
Up to now (at least as far as I read), pixel launcher is not working properly with qpr2"
Later confirmation from nikgapps dev:
"Yes, Pixel Launcher needs an update if we're on QPR2 builds. Those who cannot wait for the official release they can either flash the latest canary release and disable pixel launcher in the process or simply flash this (https://forum.xda-developers.com/t/android-13-gapps-nikgapps-arm64.3915866/post-88352313) addon
The easiest way to remove Pixel Launcher (if installed accidentally or intentionally) would be deleting /system/addon/##-PixelLauncher.sh file and performing an OTA update.
This will not restore Pixel Launcher with dirty flash of Rom or OTA update and will get stock launcher back."
And my suggestion that was also confirmed as working:
"Think you should be able to modifiy gapps installer to remove pixel launcher
Then dirty flash same build again and gapps without pixel launcher" -
6Build 20230312 is ready
Changelog: https://crdroid.net/guacamole/9#changelog
Download: https://crdroid.net/guacamole/9
Join the chat on Telegram @ https://t.me/crDroidOP7Pro5Build 20230303 is ready
Changelog: https://crdroid.net/guacamole/9#changelog
Download: https://crdroid.net/guacamole/9
Join the chat on Telegram @ https://t.me/crDroidOP7Pro5Build 20230401 is ready
Changelog: https://crdroid.net/guacamole/9#changelog
Download: https://crdroid.net/guacamole/9
Join the chat on Telegram @ https://t.me/crDroidOP7Pro2
Yep, fully agree.
Clean flash with H.38 here. Great ROM - smooth, many options for personalization, just does it's job. GCam works great as well. Since installing it on 26.02.23 I have found only one problem, the battery indicator is not working properly e.g. it sticks to 61% and suddenly falls to 58%. I hadn't observed such issue earlier on this phone on any other ROM. It's not a game changer, so I will stick to that ROM for longer.2
Make sure your on the latest firmware. A new version is required as of the previous release, and ota doesn't cover that. -
24
Code:*** Disclaimer I am not responsible for any damage you made to your device You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/13.0/README.mkdn
Flashing Instructions:
Pre-installation:
- OOS 12 H.36 firmware is mandatory (can update via firmware update tool found on download page, firmware button)
- Download recovery (from download page, recovery button)
- Optional NikGapps core (download - note that you may also need setup wizard addon if you rely on Google restore)
- Optional Magisk (boot.img used to patch with Magisk in order to get root, can be found in recovery folder from download page)
- Backup your data to PC, OTG flash drive
- Make sure you have OOS 12 firmware installed (if used firmware flash tool from download page, proceed straight to install crDroid.zip)
- Enter fastboot
- Flash our boot.img in fastboot
-
Code:
fastboot flash boot boot.img - Boot to recovery (can do from bootloader or with buttons from power off state)
- Now in recovery go to factory reset and confirm the reset
- Reboot to recovery
- Choose apply update and Apply from ADB
- Now install crDroid zip via sideload
-
Code:
adb sideload crDroid.zip - Go back to main menu and reboot to recovery to install gapps (if you don't want gapps, reboot to system)
- To install gapps, simply reboot to recovery again and sideload gapps.zip the same way you installed crDroid.zip then reboot to system
Via recovery (recommended way):
- Boot to recovery
- Choose apply update and Apply from ADB
- Now install crDroid zip via sideload and reboot
-
Code:
adb sideload crDroid.zip - If you had gapps, reboot to recovery and sideload gapps.zip and reboot
- Go to Settings -> System -> Updater and download latest build
- Choose install and let it finish
- If you have Magisk installed, don't click reboot when prompted and go to Magisk and choose install to inactive slot
- Reboot
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/crdroidandroid/android_kernel_oneplus_sm8150
Download:
ROM https://crdroid.net/guacamole/9
Visit official website @ crDroid.net
crDroid OnePlus 7 Pro Telegram
crDroid Community Telegram
If you like my work, consider a donation > My Paypal12Build 20221126 is ready
Changelog: https://crdroid.net/guacamole/9#changelog
Download: https://crdroid.net/guacamole/9
Join the chat on Telegram @ https://t.me/crDroidOP7Pro11Build 20221226 is ready
This build includes lots of goddies, so check changelog
Changelog: https://crdroid.net/guacamole/9#changelog
Download: https://crdroid.net/guacamole/9
Join the chat on Telegram @ https://t.me/crDroidOP7Pro10Build 20221230 is ready
Changelog: https://crdroid.net/guacamole/9#changelog
Download: https://crdroid.net/guacamole/9
Join the chat on Telegram @ https://t.me/crDroidOP7Pro
