Enable DCI-P3 for OP3T with S6E3FA5 display panel

[Didgeridoohan]

Nope, I can't get it working by doing that

It works on stock OxygenOS Oreo. If you're on a custom ROM it's not gonna be that straightforward.

But, I did notice that it now gets reset at boot, so it has to be done after the device has fully booted. Either with something like Tasker or by adding a delay to whatever boot script runs the command (Magisk module, etc). Running the command in Magisk late_start service mode (service.d/service.sh) and adding a 15 second delay does the trick for me...

 

[datvui2211]

It works on stock OxygenOS Oreo. If you're on a custom ROM it's not gonna be that straightforward.

But, I did notice that it now gets reset at boot, so it has to be done after the device has fully booted. Either with something like Tasker or by adding a delay to whatever boot script runs the command (Magisk module, etc). Running the command in Magisk late_start service mode (service.d/service.sh) and adding a 15 second delay does the trick for me...

It works flawless now :laugh:, thank you all!

 

[badlipe]

Thanks guys, based on the info you provided, I was able to get that back working using kernel adiutor instead of the magisk module, that was giving me bootloops.

 

[Paschfire]

A note to others...

I have the a3 panel on my OnePlus 3T running OOS 5.0 Official 28_171116 stock/rooted with Magisk v15.0(1500) beta, the DCI-P3 file is present within /sys/devices/virtual/graphics/fb0/DCI-P3 and when I echo the command via terminal app DCI-P3 colour profile enables instantly.

I can clearly see the changes in colour saturation and warmer tone compared to Default.

So I don't think having the ability to enable DCI-P3 is exclusive to only the a5 panel.

I suggest if you have the either the a3 or a5 panel, first check to see if the DCI-P3 is present within in the above file path, then just echo this command via terminal app;

su
echo "1" > /sys/devices/virtual/graphics/fb0/DCI_P3

If DCI-P3 is working you'll see the changes right away.

 

[MSF Jarvis]

A note to others...

I have the a3 panel on my OnePlus 3T running OOS 5.0 Official 28_171116 stock/rooted with Magisk v15.0(1500) beta, the DCI-P3 file is present within /sys/devices/virtual/graphics/fb0/DCI-P3 and when I echo the command via terminal app DCI-P3 colour profile enables instantly.

I can clearly see the changes in colour saturation and warmer tone compared to Default.

So I don't think having the ability to enable DCI-P3 is exclusive to only the a5 panel.

I suggest if you have the either the a3 or a5 panel, first check to see if the DCI-P3 is present within in the above file path, then just echo this command via terminal app;

su
echo "1" > /sys/devices/virtual/graphics/fb0/DCI_P3

If DCI-P3 is working you'll see the changes right away.

OxygenOS added support for DCI-P3 on both panels during the Nougat open beta phase which I ported into Caesium kernel.

Sent from my Pixel 2 using XDA Labs

 

[murti52]

Hi, can any one provide a pic/snapshot of the before and after screen? i recently got a op3t and i think so my display is a bit faulty, showing a bit bluish feel on white. thanks

 

[NicestRudeGuy]

magisk module for it ?

 

[Immortalis]

magisk module for it ?

Did you ever read first post?

 

[NicestRudeGuy]

Did you ever read first post?

i did but i want a magisk module for it ,my device support it.

 

[Immortalis]

i did but i want a magisk module for it ,my device support it.

Then read it again. Look for text in orange.

 

[NicestRudeGuy]

Then read it again. Look for text in orange.

now i got bootloops

---------- Post added at 11:56 PM ---------- Previous post was at 11:55 PM ----------

Hi all,

I packaged this into a Magisk module for everyone to enjoy. It simply runs the provided command as part of the Magisk late_start service.

Here is a link to the GitHub repo: https://github.com/doubleaykay/DCI-P3_Enabler_OP3T. I have submitted it to the repo.

In the meantime, I have attached a zip you can install in Magisk.

I have tested it on my own device and it works perfectly!

Enjoy!

Edit: Yes, this allows it to persist through reboots!

got bootloop on OOS beta 22

 

[Immortalis]

got bootloop on OOS beta 22

Use jOnePlus Tools app from Play Store

 

[NicestRudeGuy]

Use jOnePlus Tools app from Play Store

i used offline module remover , but its weird that the module gives bootloop but the command doesnt lol

 

[jakobWango]

i used offline module remover , but its weird that the module gives bootloop but the command doesnt lol

Well i suggest you use the jOneplus tools that he wrote, so you don't mess up your ROM as you did now just to use a magisk module for it.

 

[NicestRudeGuy]

Well i suggest you use the jOneplus tools that he wrote, so you don't mess up your ROM as you did now just to use a magisk module for it.

im using magisk since the open beta 20

 

[jakobWango]

im using magisk since the open beta 20

Ahaa yes. but have you been able to change to dcip3 yet?
What im sayin is, it's much easier to just install the app, switch on the dcip3 calibration and your DONE.

But if you want to hassle with making it a magisk module, its up to you.

 

[NicestRudeGuy]

Ahaa yes. but have you been able to change to dcip3 yet?
What im sayin is, it's much easier to just install the app, switch on the dcip3 calibration and your DONE.

But if you want to hassle with making it a magisk module, its up to you.

i am able to do it, also magisk doesnt ruin the rom thats the point of using it

 

[akino553]

work perfect with miuipro

 

[xontax]

Could you rewrite the echo command to small letters at the command? Elseif it will give an error output.

So from DCI_P3 to dci_p3. Thanks for the magisk moduke

 

[agplugged]

Quick update for those of you who don't follow - there's a magisk module now that automatically activates the DCI P3 gammet for you, it is fully automatic and works through reboots. Highly recommended.