yashsingh1/xdaforums huggingface dataset:
[OnePlus 8 / 8 Pro & 8T Cross Device Development] AlDollaz:
Not OOS12, but 11 did. Try installing DarQ. It's an Xposed module that works very well for forcing apps into dark mode.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] genica:
Try using CMD not PowerShell
[OnePlus 8 / 8 Pro & 8T Cross Device Development] petes:
Hi @AnierinB I just wanted to say thanks for fixing the night light scheduled on/off in the latest build.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] firoz3321:
I always use CMD. the issue however was with the ADB. downloaded v33 from google and that worked however it corrupted my device as mentioned in previous posts.

had to again MSM, unlock bootloader, fastboot to latest EvolX, Magisk Root.

unfortunately again now banking apps are not working. dont know what worked before. tried all combinations but this stupid app doesnt work (iMobile and Axis)
[OnePlus 8 / 8 Pro & 8T Cross Device Development] firoz3321:
iMobile working with AirFrozenmethod. Need to freese rhe magisk app and then Run the iMobile app. Wonder how iMobule is detecting the Magis
[OnePlus 8 / 8 Pro & 8T Cross Device Development] star7827:
Is anyone experiencing any green background instead of black? Ive been noticing a sudden change while using my phone on a daily basics and it's been happening many times where the screen would just change to green-like tint instead of the normal dark. I only restart everytime it happens to fix it but issue still exists. And no Night light turned on.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] star7827:
It's working fine here too.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] devsk:
Doesn't work on accubattery, that's why I asked. OOS 11 was able to.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] Melcore127:
Anierin Bliss thanks for the rom u did really good almost perfect . Hope u can keep up the frequent updates.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] nordurljosahvida:
Hi, I'm coming from AOSP extended, which I flashed coming from stock OOS11 + "fastboot update image.zip". Do I need to MSM-unbrick before I install this rom or can I flash right away without having to do any prior re-stocking first? Thanks!
[OnePlus 8 / 8 Pro & 8T Cross Device Development] AlDollaz:
Got it. FYI, OOS12 doesn't have the force apps in dark mode feature anymore. So I doubt the developer would add it since there's already apps available. I'm sorry it doesn't work for a specific app, but you'd probably have better luck reporting the issue to the creator of DarQ.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] AnierinB:
This is due to watching HDR content. A fix is in the works however I'd refrain from watching anything HDR until it is resolved.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] devsk:
hmm...that's interesting. So, they took away a feature! Typical, OnePlus...loll
[OnePlus 8 / 8 Pro & 8T Cross Device Development] AlDollaz:
Exactly. Stock OOS12 is awful, IMO.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] Melcore127:
Is anyone having this rare bug where the lock screen bugs out and it's all black. I get this like every blue moon. But when it comes i can't get the screen to show anything sometimes even tho I've pressed the power button multiple times . And then out of no where it magically shows everything as if nothing happened all the the haptic feedback is there when the bug happens so ik it's just the screen not showing up
[OnePlus 8 / 8 Pro & 8T Cross Device Development] enjoy_life:
I haven't seen this personally.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] Melcore127:
Hmm ig it's maybe a me problem lemme check my settings and stuff thanks
[OnePlus 8 / 8 Pro & 8T Cross Device Development] devsk:
Do you have AOD on? I have experienced this multiple times myself. Since the time I have turned off AOD, it hasn't happened.

I think AOD has couple of issues:

1. Pull the phone out of pocket, AOD screen shows but you can't press anything.

2. Once in a while, the phone goes black, haptic feedback is there, notifications work, if you call from another phone, the screen lights and you can receive the call, but without that, you can press all the buttons you want, it won't wake up the screen. Then, suddenly wakes up on its own after some time!

Instead of AOD on, I have moved to "Single Tap" to AOD screen, which gives me a quick peek at time and any notifications using a single tap of the screen. Battery lasts much longer and no annoyance with touchscreen or black screen.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] AlDollaz:
Turn off pocket mode.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] devsk:
Turning pocket mode off did not completely resolve the issue for me. I would still get black screen once in a while.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] ewong3:
weird issue on new build :

when connecting phone to pc, windows does not seem to recognise phone anymore despite default usb config set to 'file transfer' and usb debugging enabled

has anyone come across this issue also?

tried and seems this happens to two separate phones with latest evo builds. same pc still sees another phone on LOS18.1

any thoughts to fix this appreciated
[OnePlus 8 / 8 Pro & 8T Cross Device Development] devsk:
Sideload from adb again
[OnePlus 8 / 8 Pro & 8T Cross Device Development] AdmiralKirk:
If memory serves, the black screen issue is a well known one, and as previously mentioned, it has to do with AOD. This issue has existed since A11 (Evo 5), and I suspect it's just a difficult one to track down (I also don't think AOD is much of a priority for the devs, which is reasonable since it's kind of a niche feature). If it happens, just spam the power button a few times and then wait, it generally always wakes up within a minute or so. Either that or just disable AOD, get yourself a cheep smartwatch if you need to know the time :P (I've found my FitBit to be invaluable for time and notifications, way better than getting my phone out of my holder).

As for the Connecting to PC issue, I'm going to make a guess here. It hasn't been proven yet, but I strongly suspect that this issue, along with several others (such as failing OTA's), is caused by unexpected configuration data in some of the phones partitions. There are something like 30 ish image files that get flashed with stock (plus a/b versions), and of those only about 8 or so are re-flashed by this or other 3rd party ROM's. The rest of those partitions are expected to contain the data in use by the latest version of OOS 11. So that said, I believe that a possible solution for many of these odd issue is to MSM back to the latest version of OOS 11 offered by MSM, then OTA up to the latest version of OOS11 itself (do NOT take the OOS12 OTA). At that point, you should go through the ADB sideload method to flash this ROM and I strongly suspect at that point you'll see far fewer issues. Again, this is an educated guess on my part at the moment, although with some effort I think it could be proven (partition checksums of working vs non-working phones... Actually, this sounds like an interesting project, perhaps I'll look into it. Also, holy crap, Magisk makes a mess of the mount table).
[OnePlus 8 / 8 Pro & 8T Cross Device Development] petes:
That's the approach I always tend to take if I switch ROMs and it certainly seems to minimise odd glitches. One additional thing I do is to flash the OOS11 build twice - to make sure both slots are the same. Download it as a local zip and load it twice. Never sure if it makes a difference, but certainly doesn't do any harm.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] ewong3:
thank you but problem being adb does not detect device, meaning sideloading is not possible:

adb: sideload connection failed: no devices/emulators found

adb: trying pre-KitKat sideload method...

adb: pre-KitKat sideload connection failed: no devices/emulators found

but anyway problem went away when i tried a different cable - still bizarre given the LOS phone is attached to the same USB hub, and both are using OP cables... perhaps it is just one of those inexplicable hardware quirks?
[OnePlus 8 / 8 Pro & 8T Cross Device Development] firoz3321:
Hi guys i am facing this weird but critical issue. The touchscreen of bottom portion of screen doesn't woek after unlock. Mostly after a long sleep period.

Unable to type on keyboard but noticed few keys would work like A, L and a few others. I didn't worry too much as locking and unlocking the screen a few times would make it work again. But today i was getting a call early in the morning. I wasn't able to pick the call as the portion of screen where i can pick or reject the call was not responding. I could access the notification panel.

After a few lock and unlock i was able access the touch again.

This is really frustrating. Please let me know what information is required
[OnePlus 8 / 8 Pro & 8T Cross Device Development] firoz3321:
Same issue. Didn't find response to this. Any solution
[OnePlus 8 / 8 Pro & 8T Cross Device Development] firoz3321:
How was this resolved, i am having this issue too. No AOD. Locking and unlocking multiple times works but this is happening all the time. Share what resolved, if it did
[OnePlus 8 / 8 Pro & 8T Cross Device Development] firoz3321:
Anyone? Pocket mode off same issue.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] qriozum:
Hi.

I read the first post and the second too. However, I would like to make sure about the firmware on which you can install Evox 6.4 on OnePlus8Pro.

Can this Evox version be installed on an Android 12 (Build C.20) company with OnePlus8Pro?

Do I have to make a roolback for Andoid11?

It is true that in this Roma there is a mention of A11, but the author could not fully update the entries, because for OP8PRO in the second post he has completely mistaken links to files:/

regards

q.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] AnierinB:
You need to be on the latest OOS 11 before flashing this ROM. Also, all the links in the second post are accurate and not "mistakenly linked". 🙄
[OnePlus 8 / 8 Pro & 8T Cross Device Development] qriozum:
Thank you.

The first link for "OP8PRO" to be directed to Recovery moves to:

https://sourceforge.net/projects/evolution-x/files/instantnoodle/evolution_instantnoodle-ota-sp2a.220505.002-052111066-nsigned.zip/download

Should it not be a link to:

https://sourceforge.net/projects/evolution-x/files/instantnoodlep/recovery/Recovery.img/download

?

The third link for "OP8PRO" indicates:

https://sourceforge.net/projects/evolution-x/files/instantnoodlep/evolution_instantoplep-ota-sp2a.220505.002-05211029-unsigned.zip/download

should he not direct us to Stock Bootimage which is here:

https://sourceforge.net/projects/evolution-x/files/instantnoodlep/bootimage/stock_boot.img/download

greetings

q.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] AnierinB:
Check again. P.s Not hard to navigate a directory tree and find the files yourself
[OnePlus 8 / 8 Pro & 8T Cross Device Development] DevastatorTNT:
Hi there, very nice ROM.

A collection of bugs I've been experiencing over the past two months:

1. FPS animation glitches, makes lower part of the touchscreen unusable. Happens when face unlock and fingerprint scanner are being used at the same time; locking the phone and unlocking being careful not to use face unlock solves the issue

2. The camera cutout has been shifted towards the bottom (~30 pixels) for the last few builds. Makes the status bar taller, can't seem to address this even with developer settings (display cutout)

3. Lockscreen stays black after waking the phone. Can't seem to reproduce this consistently, but I have no aod and pocket mode didn't seem to matter.

4. Lag when waking the phone from sleep. There's a split second lag when using the power button to turn the screen on, like it's waiting for a second input. Deactivating the camera shortcut didn't help, although it disappears when using pocket mode

Is number 3 happening to anyone else? It's kind of annoying lol. I was on the suggested A11 build previous to flashing Evolution X. Have been updating via OTA since
[OnePlus 8 / 8 Pro & 8T Cross Device Development] nneves:
Hi,

Does this ROM has this bug in the Dialer that shows a small menu what choosing output device or replying with a SMS when a second call is coming?

The device is a 8T.

Thanks
[OnePlus 8 / 8 Pro & 8T Cross Device Development] enjoy_life:
I don't experience the issue #3 on my phone. Also, I'm not sure about any others you mentioned, maybe I didn't pay enough attention, but everything seems to be working great. Waiting for the fix of HDR video and then I'll donate! Can someone tell me how to donate?
[OnePlus 8 / 8 Pro & 8T Cross Device Development] firoz3321:
Any solution please?
[OnePlus 8 / 8 Pro & 8T Cross Device Development] hon2838:
Hi everyone, currently has used this rom for two weeks already many things are smooth sailing.

However,I would like to report a few bugs that hoped can be addressed soon.

1. HDR Video,

For some reason,if I try to play anything in Netflix or YouTube HDR,the display turns very dim,then will stuck there until I restart the phone

2.Weird status bar if you have too much icons.

If the network speed monitor is enabled,sometimes It will hide behind the notification dot when there are too much notification or enabled items.

Feature suggestions

May I ask is there a way for me to adjust the left right balance of the speaker though.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] enjoy_life:
I don't have this issue on my phone. Maybe try dirty flashing the ROM again?
[OnePlus 8 / 8 Pro & 8T Cross Device Development] capt.ron:
I believe your issue #1 is addressed in post #2197 (couple pages back)
[OnePlus 8 / 8 Pro & 8T Cross Device Development] hawk1500:
Yeah, waking it up sometimes 3 presses of the power button. I am guessing the first one doesn't work somehow, the second press turns it off again, and then the 3rd press finally turns the screen on. It started doing this maybe since the last 2 updates? It had stopped doing it for maybe 5 updates, and then it came back.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] AlDollaz:
Turning off pocket mode fixed the screen issue for me.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] Agimax:
Turning off 'prevent accidental wakeup' seems to fix it for me. Pocket detection didn't matter on or off.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] JayDz:
After installing this rom my oneplus 8 is not recognized by my pc. Tried installing the right drivers, adb fastboot and media is all not working. Don't even hear a sound when plugging the phone into my pc. How can I possibly fix this? Or how can I go back to oxygen OS without using my pc? I can only install a update from adb which is not working...
[OnePlus 8 / 8 Pro & 8T Cross Device Development] justanutt:
Idk what you have your phone set up like, but make sure that you have file transfer checked under developer options or it is also in the evolver settings under miscellaneous. Also try to use a usb to usb type c cord. I just tried and the type c to type c would not work. I also have the usb 2.0 fast charge checked and the usb-otg checked under device extras.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] JayDz:
File transfer is selected. I am using the original oneplus cable. I tried enabling 2.0 and usb-otg buy did not help. Also just did a factory reset but my different pc's still don't detect my phone.

On a new pc it did detect the phone (before factory reset). Adb worked. Went to recovery and adb stopped working. Booted the phone and now the phone is not detected anymore....
[OnePlus 8 / 8 Pro & 8T Cross Device Development] justanutt:
Have you reinstalled the driver
[OnePlus 8 / 8 Pro & 8T Cross Device Development] JayDz:
My phone won't even show up in device manager so can't reinstall that driver. But did try to reinstall adb/fastboot/oneplus drivers but did not help
[OnePlus 8 / 8 Pro & 8T Cross Device Development] justanutt:
Idk. Good luck.🤔. Have you tried restarting your computer?
[OnePlus 8 / 8 Pro & 8T Cross Device Development] JayDz:
Thanks! Been trying for hours maybe someone else can help here 😅
[OnePlus 8 / 8 Pro & 8T Cross Device Development] AdmiralKirk:
Is your phone rooted? If so, I might use something like Magisk to reboot to the bootloader and see if anything shows up in your device manager (Or if you're really good, you can use the button dance to do it without root). This would help you rule out the ROM itself to determine if perhaps your issue is the computer/cable/physical phone instead. I know you said it "worked before" but that's never a good reason to discount a given troubleshooting step. Two unrelated problems can absolutely show up at exactly the same time, I've seen it happen way too often to discount.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] QuiDC96:
Where is the settings to set up the double tap on home screen to turn the screen off?
[OnePlus 8 / 8 Pro & 8T Cross Device Development] hawk1500:
I'll give it a shot, thanks (but does it mean this setting wasn't working before when leaving it on didn't do this?)
[OnePlus 8 / 8 Pro & 8T Cross Device Development] Throg:
I know where it is bit I can't remember the settings option name. Do me a favor and send me a screen shot of the first page of settings. I also had a Hella time finding it.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] Throg:
Okay. I spoke too quickly. I'm with you, I think that feature was removed it not included in this build. However, if you use Nova launcher, you can define gestures to do pretty much anything. I have double tap set to lock screen.

Sorry if I got your hopes up.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] AnierinB:
That feature was never included in my builds
[OnePlus 8 / 8 Pro & 8T Cross Device Development] funnoam:
@AnierinB Hi!

Congratz on this fantastic ROM.

Few issues and blazing fast, including awesome improvements coming from OOS. Can't go back now once you tasted it.

I just have this specific issue. Noticing a very very huge loss of Bluetooth quality with the same headphones and car speakers and same phone, coming from OOS android 11.

Basically Bluetooth audio quality is terrible with the standard AAC codec. But it's not an AAC issue, it's a ROM/bluetooth/audio config issue since it was working perfectly fine on OOS.

I did try messing with developers Bluetooth settings, absolute volume and avrcp version. No changes and issue still here.

Is it related to DRC ?

I'll try some magisk modules to disable it and some others to improve the sound.

It might be related to the Dolby Atmos implementation? Sadly, there's no change if I disable it.

Related to android 12 Bluetooth/audio implémentation maybe ?

Could you acknowledge the issue?

Thank you for your hard work.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] devsk:
Tried the latest OTA. After I enter my PIN for login, it says rebooting to Recovery and reboots to recovery.

I will try the dirty flash from adb sideload to see if that works. But this is the 3rd time OTA has failed for me...:-(
[OnePlus 8 / 8 Pro & 8T Cross Device Development] devsk:
hmm...looks like the stock boot image linked from the main page is bugged. We should take that link down.

If I use that stock boot image, patch it with magisk and flash it, it drops me back into recovery saying my data is corrupt.

If I use the payload dumper and dump stock boot.img from the ZIP's payload.bin, patch it with magisk and flash it, it works fine.

I repeated this twice to be sure. The md5sum of two images differs.

@AnierinB The stock boot image upload is bugged. Please look into it.

$ md5sum stock_boot-06092022-payload.img stock_boot-06092022.img
7a33db69167dfb6b4921295cd162459a stock_boot-06092022-payload.img
4d940702c48f4666a9c93ee874b9b587 stock_boot-06092022.img
[OnePlus 8 / 8 Pro & 8T Cross Device Development] devsk:
I also made sure that the download was not the problem. The md5 matches with what is shown on the download folder at the website.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] d3viou5:
I have just updated using the OTA and it worked fine. To retain Magisk patched boot, once the updater has finished do not reboot. Instead go to Magisk and install to the inactive slot. Then reboot.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] devsk:
That's exactly what I did this time. But it rebooted it back to recovery with "your data is corrupt" message.

I manually sideloaded the whole ROM from recovery and proceeded to magisk to install again by patching the stock boot image. That's when I found that the stock boot image on the website is bugged. Its different from what is in the ROM, as can be seen from the md5sums.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] AnierinB:
The boot image in that folder on sf is older than the current builds. Hence the md5 mismatch
[OnePlus 8 / 8 Pro & 8T Cross Device Development] Ramrod71:
Since the last update I'm having issues with the music widget crashing pixel launcher when I press the music control buttons on the widget. Same thing with both Poweramp and VLC player widget. Any ideas or fixes?
[OnePlus 8 / 8 Pro & 8T Cross Device Development] jdfrye2:
Has anyone tried degoogle-ing this ROM specifically? This has been my daily driver for over a year now, and rather not move to lineage if I can stick with EvoX
[OnePlus 8 / 8 Pro & 8T Cross Device Development] devsk:
We should rectify it. To avoid another person running into the same issue.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] quimbexa:
Cool ROM! Would it be possible to request the inclusion of a quiet mode for thoseof us that use the wireless warp charger?
[OnePlus 8 / 8 Pro & 8T Cross Device Development] WhisperPntr:
Can confirm the following was fixed post dirty flashing latest build:

1) Random blackout screen that stays blacked out until reboot

2) slow, and unresponsive fingerprint sensor

Can also confirm following issues some already reported:

1) (already reported) Low bluetooth sound quality with hissing and popping

2) Battery drain is much faster now.

Will update as I keep using. Appreciate the hard work involved in maintaining this Rom!

Thank you!
[OnePlus 8 / 8 Pro & 8T Cross Device Development] xinseo:
I OTA updated yesterday to the latest build. Since then, widgets have been problematic. For example, when i try to skip to the next song using the Spotify widget, Pixel launcher crashes and restarts. This was working fine on the last build. It also crashes when i try to open any news story through the BBC widget.

Anyone else experiencing this?
[OnePlus 8 / 8 Pro & 8T Cross Device Development] AnierinB:
Already fixed and will be available on the next build.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] xinseo:
Perfect. Thank you. I was on OOS for 2 years and this ROM has been a life changer.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] revird9:
hello, how can i root this rom?

edit: done, read it in telegram
[OnePlus 8 / 8 Pro & 8T Cross Device Development] Bowery_King:
Does anyone know where is the option to show WiFi Speed on status bar? I cannot find it anywhere.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] funnoam:
I can confirm that disabling DRC or any audio improvements module or disabling Dolby audio doesn't solve the issue and still results in very bad audio quality over Bluetooth specially with the AAC codec. SBC sound "okay" but still under performing comparing to OOS.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] d3viou5:
I have a similar issue. I disable Dolby in favour of v4a, but the issue persists. It's like the connection with the BT device is unstable - like the devices are too far apart even though they are inches away from each other.

To be fair, when they are next to each other it works fine - it also works fine in my car. But if I move my phone more than 4 inches away from the soundbar on my desk I get this issue.
[OnePlus 8 / 8 Pro & 8T Cross Device Development] afrob101:
I am on Stock oxygen OS 11.0.13.13.KB05BA

Before Installing this Rom with fastboot ROM Installer should i unlock the Bootloader?
[OnePlus 8 / 8 Pro & 8T Cross Device Development] justanutt:
I think that you have to unlock it. That is how you install custom ROMs.