Enable DCI-P3 for OP3T with S6E3FA5 display panel - OnePlus 3T Guides, News, & Discussion

Update: Thanks to @MishaalRahman for the great summary article. More discussion there.
Update: Thanks to @GR0S for the app solution, available in this post
Update: Thanks to @doubleaykay for the magisk module, available in this post
I am no developer but I was researching the OP5 DCI-P3 calibration, saw that some international users were able to activate the calibration on their OP3T, and thought I would share what I have found so far. Long story short, this probably works if your device is a OP3T with the S6E3FA5 display panel, but not if your device is a OP3T with the S6E3FA3 display panel.
Note: I believe this changes the actual calibration for the "Default" selection in the display settings, but you will not see the name "Default" change to "DCI-P3"
Sources:
Credit to @rquandt on Twitter for getting the ball rolling: Tweet
Proposed command-line solution from ITHome: Link
Proposed modified apk solution from OnePlusBBS: Link
More discussion from OnePlusBBS: Link
Even longer thread (86 pages) from OnePlusBBS: Link
Even longer thread (583 pages) from OnePlusBBS: Link
This post to Weibo discusses S6E3FA5 vs S6E3FA3 compatibility: Post
Procedure:
Find out if your display panel is compatible (looking for S6E3FA5)
Install AIDA64 and check Display > "Panel ID"
(optional) I also checked to see if the profiles were available on my OP3T running Oxygen OS Open Beta 9 using a file explorer.
Open Terminal Emulator on your phone and enter these two commands:
Code:
su
echo 1 > sys/devices/virtual/graphics/fb0/DCI_P3
The changes will revert to previous configuration on reboot, so this must be re-applied after reboot.
To revert changes
Open Terminal Emulator on your phone and enter these two commands:
Code:
su
echo 0 > sys/devices/virtual/graphics/fb0/DCI_P3

I'm on VertexOS and DCI-P3 profile is not available in said location. Will flash OB9 and report back.
---------- Post added at 03:53 PM ---------- Previous post was at 03:20 PM ----------
It works perfectly, no need to reboot. Looks great, think I will keep it for a while.

I have S6E3FA5. DCI-P3 file is available in it's location. Just tried on Freedom OS 4.1.6, and nothing. Phone switches back to sRGB after reboot... not sure how to actually confirm it's DCI-P3....

twoxa said:
I have S6E3FA5. DCI-P3 file is available in it's location. Just tried on Freedom OS 4.1.6, and nothing. Phone switches back to sRGB after reboot... not sure how to actually confirm it's DCI-P3....
Click to expand...
Click to collapse
You can immediately see the difference in color after issuing the command on Terminal Emulator, especially if sRGB is enabled. DCI-P3 is a lot more colorful, but not quite as the default calibration, which is borderline psychodelic. The selected calibration will still read "sRGB" though, as this new standard isn't officialy included in OP3T software. And yes, after a reboot, calibration will return either to standard values, or sRGB.

Yup got it now, thanks. Looks nice. Too bad it doesn't stick after reboot.

twoxa said:
Yup got it now, thanks. Looks nice. Too bad it doesn't stick after reboot.
Click to expand...
Click to collapse
Yup, that's a shame. Nothing a quick script in Tasker can't fix, though.

redsmith said:
You can immediately see the difference in color after issuing the command on Terminal Emulator, especially if sRGB is enabled.
Click to expand...
Click to collapse
Cool, sounds like it works even if you don't select "Default" before running the commands. Thanks!
redsmith said:
It works perfectly, no need to reboot. Looks great, think I will keep it for a while.
Click to expand...
Click to collapse
twoxa said:
Phone switches back to sRGB after reboot...
Click to expand...
Click to collapse
redsmith said:
after a reboot, calibration will return either to standard values, or sRGB.
Click to expand...
Click to collapse
I'll update the instructions accordingly. Thanks!

redsmith said:
Yup, that's a shame. Nothing a quick script in Tasker can't fix, though.
Click to expand...
Click to collapse
So i think it's useless for now!
Let's hope for a magisk module,maybe...

Still trying to see if there's a way to enable a setting to allow this to work on S6E3FA3 display panels.
Found this mention of a "OPScreenColorMode.java" configuration file on the OP3T but I can't find where that would be on the device.
I decompiled the Settings.apk and couldn't find the file, but I did see a mention of that synonym (as well as OPNightMode and OPReadingMode) inside "display_settings.xml":
Code:
<PreferenceScreen android:title="@string/oneplus_night_mode_enabled_op" android:key="oneplus_night_mode" android:fragment="com.oneplus.settings.better.OPNightMode" />
<PreferenceScreen android:title="@string/oneplus_reading_mode" android:key="oneplus_reading_mode" android:fragment="com.oneplus.settings.better.OPReadingMode" />
<PreferenceScreen android:title="@string/oneplus_screen_color_mode_title" android:key="screen_color_mode" android:fragment="com.oneplus.settings.better.OPScreenColorMode" />
Not sure where to go from here, though.

soccerwuedo5 said:
Not sure where to go from here, though.
Click to expand...
Click to collapse
It won't be there on not supported devices as there is a condition to remove that preference as shown in your attached screenshot.

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!

nicesoni_ash said:
It won't be there on not supported devices as there is a condition to remove that preference as shown in your attached screenshot.
Click to expand...
Click to collapse
Thanks for taking a look! It seems the guys on OnePlusBBS have overridden that removal for compatible devices to add the menu items back in on the OP3T. It's over my head but maybe someone can replicate their efforts here.

Root required
Will add srgb button tomorrow

GR0S said:
Root required
Will add srgb button tomorrow
Click to expand...
Click to collapse
I have an A3 display and I still see a change when using DCI-P3!

vampire36 said:
I have an A3 display and I still see a change when using DCI-P3!
Click to expand...
Click to collapse
That's awesome! I tried the app and saw no change but maybe there's some other variable involved.

Magisk module isn't working for me, but the command is

Navi44 said:
Magisk module isn't working for me, but the command is
Click to expand...
Click to collapse
You could at least be more specific and include OxygenOS version and Magisk version for him/her to compare. . .

I have the A5 panel on my 3T, and magisk module isn't working for me. Currently running FreedomOS 2.11.2 with Blu_Spark kernel r151 and Magisk v13. Let me know if there's any other information I should add.

tzbigworm said:
I have the A5 panel on my 3T, and magisk module isn't working for me. Currently running FreedomOS 2.11.2 with Blu_Spark kernel r151 and Magisk v13. Let me know if there's any other information I should add.
Click to expand...
Click to collapse
That is bizzare, maybe it's an issue with Magisk v13. Could you post your Magisk log?
I am using Magisk v12, the stable release, and it works perfectly fine for me.... odd.
Could we have more people test the Magisk module to make sure it works?

GR0S said:
Root required
Will add srgb button tomorrow
Click to expand...
Click to collapse
This works like a charm! The colours take a bit of getting used to though.

Related

[Work In Progress] Install Ubuntu 16.04.3 Nexus 9

DON'T FORGET TO HIT THE THANKS BUTTON
!!!DISCLAIMER!!!!
You are solely responsible for whatever shtuff happens to your device by installing either of the two files to your device.
!!!DISCLAIMER END!!!
So this still needs a lot of work but I am providing a working boot.img and root filesystem archive for all Nexus 9 variants? (not sure needs others to test and confirm).
Will be edited as things start working
What's working:
WiFi. (Must use 'nmcli dev wifi con "SSID" password "passwd" ')
GPU @ anywhere from 900-2000 FPS
Sound works just needs reconfiguring
Screen rotation works best with minimal issues as desktop taskbar widgets command to turn clockwise into landscape:
Code:
sudo xrandr -o right; sudo xinput set-prop 7 "Evdev Axis Inversion" 0, 1; sudo xinput set-prop 7 "Evdev Axes Swap" 1
&
Code:
sudo xrandr -o right; sudo xinput set-prop 7 "Evdev Axis Inversion" 0, 0; sudo xinput set-prop 7 "Evdev Axes Swap" 0
For normal portrait orientation
However DO NOT USE THE DISPLAY SETTINGS TO ROTATE IT MESSES UP THE LOGIN ROTATION AND SCREEN GOES BLACK AND SOMETIMES SHOW BACK UP IN LANDSCAPE AND WILL NOT DEFAULT BACK INTO PORTRAIT ORIENTATION. SO YOU MUST DO IT MANUALLY!!!!! See screenshot below
Swipe gestures (Chromium-browser only).
Bluetooth: WORKING!!! Install package bluetooth-touch and set this command into a shell script or enter manually the ENTIRE string:
Code:
brcm_patchram_plus --enable_hci --use_baudrate_for_download --scopcm=0,2,0,0,0,0,0,0,0,0 --baudrate 3000000 --patchram /lib/firmware/bcm4354.hcd --no2bytes --enable_lpm --tosleep=50000 /dev/ttyTHS2
Also using a Bluetooth audio sink works by itself without keyboard connected. I've found it still needs work but, connecting to a keyboard still flawless in its function file transfer locks it up when sending not receiving. Pairing and connecting are all good but functionality of Bluetooth is down to one device at a time for best results
What's not working:
Cameras (Neither front nor rear camera works at all. Needs work).
NFC? (I have no idea how to check for this. Needs work).
Probably other things I missed.
What you will need:
Any Nexus 9 with an unlocked bootloader & latest TWRP recovery installed
USB keyboard
OTG cable
Instructions:
MAKE A BACKUP! Just in case.
1.) Enter into recovery go to wipe and format Data partition as Ext4
2.) Reboot into recovery and with the boot.img and rootfs on a flash drive or, push them to device via ADB.
3.) Go to terminal command in recovery issue the commands: cd /data; mkdir linux; cd linux
4.) tar xvjf /sdcard/rootfs.tar.bz2 -C /data/linux
5.) Flash N9boot.img with install image in TWRP Install submenu.
6.) Reboot into the new Linux system.
7.) If the Kernel panics and boot loops, go back into recovery and format the data partition again it will ask are you sure type yes & repeat steps 2-4
You will need to use a USB keyboard & OTG cable to install the necessary packages and connect to WiFi/Bluetooth.
It's much easier to install on device than in a chroot environment as I have had problems in the past. And some people have different favorite Desktop Environment's. However Gnome and KDE both do not work correctly and crash.
Fluxbox, Mate, XFCE, LXDE, all work as they should with Lightdm.
If there's anything I missed you can add it below, PM me and ask, whatever and I'll try to answer as soon as I am able.
If you are interested in building the entire thing from start to finish here are the original sources
https://forum.xda-developers.com/nexus-9/general/guide-linux-nexus-9-t2985958
https://forum.xda-developers.com/nexus-9/general/guide-linux-nexus-9-t2985958/page14
And thanks to @sonicadvance1 for his original guide & @Vartom for his work on porting some of the necessary Kernel drivers. And @Vartom again for his contributions to the Bluetooth and everything else to get us this far :good::good::good::good::good::good::good::good:
Xubuntu-Desktop Preinstalled 21.5 Drivers 1GB username=ubuntu password=ubuntu
https://drive.google.com/open?id=0B8NgGANYGMhOZS1OenNzZl94bEE
rootfs base only necessary packages root password=toor
https://drive.google.com/file/d/0B8NgGANYGMhOMjVObElVVnBWamM/view?usp=drivesdk
boot.img
https://drive.google.com/open?id=0B8NgGANYGMhOZXAwZHVrUUotZ0k
In order to get the preinstalled to fix login if having issues use the command as root in virtual terminal Ctrl+Alt+F1/F2, etc
Code:
chown ubuntu:ubuntu /home/ubuntu
.
This should fix the login issues, if you want you can create a different user and remove the premade user using these commands as root in virtual terminal.
Code:
deluser username
adduser username
addgroup username adm
addgroup username sudo
Additionally if you have an error when running glxgears there is a fix
Code:
xauth list
It should output something similar to this
Code:
localhost.localdomain/unix:0 MIT-MAGIC-COOKIE-1 a4f6256398303725763c5595f404afbb
You will need to export the display and add that MIT-MAGIC-COOKIE you got from xauth list
Code:
export DISPLAY=":0"; xauth add $DISPLAY . a4f6256398303725763c5595f404afbb
This should fix the display error.
And finally,
Enjoy Ubuntu on your Nexus 9
Video of it booting
https://youtu.be/PIGm47pwzj0
Booted fine.... However a username and password would help...lol
---------- Post added at 10:30 PM ---------- Previous post was at 09:45 PM ----------
andyroidking said:
Booted fine.... However a username and password would help...lol
Click to expand...
Click to collapse
Found the root password in the other thread. toor
Now on to getting wifi up so i can get a de installed....
Reserved
andyroidking said:
Booted fine.... However a username and password would help...lol
---------- Post added at 10:30 PM ---------- Previous post was at 09:45 PM ----------
Found the root password in the other thread. toor
Now on to getting wifi up so i can get a de installed....
Click to expand...
Click to collapse
sk1tch said:
Ha! Sorry I updated the guide above to include that little tidbit of info. Sweet I'm excited to read it worked so far. Hope the guide is simple enough for everybody who wants to try it out
Click to expand...
Click to collapse
Yeah now that I got wifi working I'm off to study how to get xfce4 installed. Everyone says Arch is hard but I'll tell you their repo's are extensive. Now I have to learn about ppa's...
Also, I'm over 50 and because we have a 2048 x 1536 display everything is very tiny making all of this more of a challenge... I tried a couple things to bump the font size but they don't work....
andyroidking said:
Yeah now that I got wifi working I'm off to study how to get xfce4 installed. Everyone says Arch is hard but I'll tell you their repo's are extensive. Now I have to learn about ppa's...
Also, I'm over 50 and because we have a 2048 x 1536 display everything is very tiny making all of this more of a challenge... I tried a couple things to bump the font size but they don't work....
Click to expand...
Click to collapse
I knew you were old school. I did get Arch Linux running on the original guide but it was choppy at best and only ran in the framebuffer but this was the aarch64 version. I do think it could be done because it's my preferred distro these days as well. I think we'd have to change a few things in the CPIO init scripts.. You know point to what it needs but, that's a little too advanced for me.
Also try setting a custom dpi in the settings menu if you're using XFCE I know there's the option there
and to install it you need to uncomment all the extra repos in /etc/apt/sources.list then do apt update && apt install xubuntu-desktop
it should look like in the picture
Well, I'm stuck. X won't start... I'll have to pull the log and see what up. Unfortunately I'm back to work tonight so it will be a while before I get to play again. Don't fret, I'll be back. :silly:
Edit: Pulled logs:
As root user:
https://pastebin.com/3bJE7HkJ
As reg user:
https://pastebin.com/ZVBrCAuM
They look the same to me...
andyroidking said:
Well, I'm stuck. X won't start... I'll have to pull the log and see what up. Unfortunately I'm back to work tonight so it will be a while before I get to play again. Don't fret, I'll be back. :silly:
Edit: Pulled logs:
As root user:
https://pastebin.com/3bJE7HkJ
As reg user:
https://pastebin.com/ZVBrCAuM
They look the same to me...
Click to expand...
Click to collapse
They look identical to me as well. Um try apt install xorg xubuntu-desktop lightdm-gtk-greeter.
then reboot it should automatically enable it with systemd while installing
Error 404
The links to the downloads are no longer working.
sk1tch said:
They look identical to me as well. Um try apt install xorg xubuntu-desktop lightdm-gtk-greeter.
then reboot it should automatically enable it with systemd while installing
Click to expand...
Click to collapse
I'll give that a shot. Sounds like solid advice. Probably not until Thursday or Saturday. Busy week kids back to school
a such...
humannequin777 said:
The links to the downloads are no longer working.
Click to expand...
Click to collapse
I fixed the links but the rootfs.tar.bz2 is down as I am uploading a preinstalled image archive with the XFCE4 DE w/ onscreen keyboard, still ironing out Bluetooth made good progress so hopefully I will have that finished soon
Cameras are not included in the kernel. I did not check their performance in this kernel.
Linux Inside... Nice. Well I found a few minutes and got this far.... https://imgur.com/a/VuDEN Xauthority issue? I'll check into it later. I assume suspend doesn't work? I tried once but didn't want to crash it right now. also changed scroll bar width... easier to tap. Border width is next.
Scroll bar width:
Open the .gtkrc-2.0 file, add the following to a new line starting at the bottom of the file:
Code:
style "myscrollbar"
{
GtkScrollbar::slider-width=XX
}
class "GtkScrollbar" style "myscrollbar"
How's the performance ?
Can I use it as a desktop?
Yes indeed it does work as a desktop I got screen rotation down to two three command scripts with desktop widgets. Most things work as of now Bluetooth sucks no matter what I do but, touchscreen works fine WiFi works fine no Cameras yet Sound only through headset. Hardware acceleration works at anywhere from 800 FPS - 2000 FPS. Videos like on YouTube stutter a little if you are doing other things while watching. Swipe gestures work in Chromium browser only. (Still working on installing multifunction swipe gestures) Your best bet would be to buy one of those $11 Micro-B USB wired tablet keyboards or just use the Onboard keyboard if its already in a rugged case or whatever. Those two green arrows at the top of the desktop are my rotate widgets
andyroidking said:
Linux Inside... Nice. Well I found a few minutes and got this far.... https://imgur.com/a/VuDEN Xauthority issue? I'll check into it later. I assume suspend doesn't work? I tried once but didn't want to crash it right now. also changed scroll bar width... easier to tap. Border width is next.
Scroll bar width:
Open the .gtkrc-2.0 file, add the following to a new line starting at the bottom of the file:
Click to expand...
Click to collapse
Yes there is an .Xauthority error when I flashed it as well that was why I said it's difficult to make a working install and that it was easier to install on device but either try chown ubuntu:ubuntu /home/ubuntu as root and it may fix your issue or you have to create a new user
Vartom said:
Cameras are not included in the kernel. I did not check their performance in this kernel.
Click to expand...
Click to collapse
I added the configs for the camera to my custom config to no avail... I dont have a headset jack debug cable so I can't see what going on during boot
sk1tch said:
I added the configs for the camera to my custom config to no avail... I dont have a headset jack debug cable so I can't see what going on during boot
Click to expand...
Click to collapse
Porting the cameras was not 100% complete. Therefore, simply adding lines to the config is not enough.
---------- Post added at 02:14 PM ---------- Previous post was at 02:08 PM ----------
Porting the cameras was not 100% complete. Therefore, simply adding lines to the config is not enough.
For bluetooth work, you need to download the corresponding firmware.
with some similar string
exec /usr/sbin/brcm_patchram_plus --enable_hci --use_baudrate_for_download --scopcm=0,2,0,0,0,0,0,0,0,0 --baudrate 3000000 --patchram /lib/firmware/bcm4324.hcd --no2bytes --enable_lpm --tosleep=50000 /dev/ttyTHS2
this can be added to the nvwifibt.conf config file.
Vartom said:
Porting the cameras was not 100% complete. Therefore, simply adding lines to the config is not enough.
---------- Post added at 02:14 PM ---------- Previous post was at 02:08 PM ----------
Porting the cameras was not 100% complete. Therefore, simply adding lines to the config is not enough.
For bluetooth work, you need to download the corresponding firmware.
with some similar string
exec /usr/sbin/brcm_patchram_plus --enable_hci --use_baudrate_for_download --scopcm=0,2,0,0,0,0,0,0,0,0 --baudrate 3000000 --patchram /lib/firmware/bcm4324.hcd --no2bytes --enable_lpm --tosleep=50000 /dev/ttyTHS2
this can be added to the nvwifibt.conf config file.
Click to expand...
Click to collapse
So just add this too the sbin config file??
sk1tch said:
So just add this too the sbin config file??
Click to expand...
Click to collapse
brcm_patchram_plus this package was not found. Add it to the fast failed.

[GUIDE] How to properly change / remove zoom error in eui/miuipro

Guys as we all know when we root our eui we get stuck with zoom sheeting on every app.
But I have found out a fix.
First things first tools required:
1:terminal emulator
2:build prop editor / root file manager
Fix:
Go ahead and open terminal emulator.
Enter the following code
Su
And click enter
wm density ###
### us where you input the amount of DPI you want 420 is normal DPI
-1st part done!
Now open build prop editor
Next Look for "ro.sf.lcd_density=###"
Change ### to previous value which you have set in terminal emulator.
Reboot!
Done!
Now you may think I might have done this in some DPI app but it will make more problems than solving it . believe me!
Special thanks my friend: snehashish
For providing me the fix
Hit thanks if you like my work!
Cheers:highfive:
Guys you can also use this to properly change DPI in eui and miui pro without font or clock glitches.:good:
Gautham V said:
Guys as we all know when we root our eui we get stuck with zoom sheeting on every app.
But I have found out a fix.
First things first tools required:
1:terminal emulator
2:build prop editor / root file manager
Fix:
Go ahead and open terminal emulator.
Enter the following code
Su
And click enter
wm density ###
### us where you input the amount of DPI you want 420 is normal DPI
-1st part done!
Now open build prop editor
Next Look for "ro.sf.lcd_density=###"
Change ### to previous value which you have set in terminal emulator.
Reboot!
Done!
Now you may think I might have done this in some DPI app but it will make more problems than solving it . believe me!
Special thanks my friend: snehashish
For providing me the fix
Hit thanks if you like my work!
Cheers:highfive:
Click to expand...
Click to collapse
The first part works. The second part does not: there is no ro.sf.lcd_density setting in the build.prop. And the settings app still reports the display as zoomed.
emkorial said:
The first part works. The second part does not: there is no ro.sf.lcd_density setting in the build.prop. And the settings app still reports the display as zoomed.
Click to expand...
Click to collapse
It does still say zoomed in settings but it is not
emkorial said:
The first part works. The second part does not: there is no ro.sf.lcd_density setting in the build.prop. And the settings app still reports the display as zoomed.
Click to expand...
Click to collapse
You wil fund the line ro.sf.lcd_density in all ROM except eUI, in eUI you can search for persist.ro.sf.lcd_density
Or similar to this one but that line start with persist
after doing this trick in miui pro rom i am continuously getting an error that system stopped
Rajashekar0675 said:
after doing this trick in miui pro rom i am continuously getting an error that system stopped
Click to expand...
Click to collapse
You must have messed somewhere
I tried the fix and didnt get any errors, but it still randomly switches from zoom mode to normal when opening apps. I really only notice it in gmail and chrome.
Guess changing the DPI has resulted in zoomed in pictures when cropping, cropping happens right as the markers indicate but the crop preview is zoomed in which makes it impossible to edit pictures. Is there a solution/hack for this?

Enable Quick Capture in India (by disabling Emergency Affordance Service)

Hi Guys
So, as you all know, Quick capture is disabled in devices connected to an Indian network and this had me pissed off for a very long time.
I looked into the Emergency Affordance Service which is responsible for identifying Indian SIMs and found a way to disable it (at least on the 5t).
But a word first.
DISCLAIMER: The Govt of India has stated that it is mandatory for all phone manufacturers to add this functionality for the right reasons. By disabling the feature you will NOT be able to use the triple-press power button for emergency call. I do not take responsibility for any damage caused due to the actions described in this post.
Alright, lets jump into it.
Step 1. Install a terminal emulator app (or connect via adb shell)
Step 2. Enter the following command without quotes:
"settings put global emergency_affordance_needed 0"
(You may use the "settings get global emergency_affordance_needed" command to confirm if it worked.)
Step 3. Check the OnePlus Camera app - the Quick capture option should be there.
Step 4. Profit!?
Notes:
My 5t was rooted with magisk, but I ran the command on a normal ($) prompt so I'm not sure if this requires root or not. Please try it on unrooted devices and let me know so I can update this post accordingly. Also, I haven't checked if it persists after a reboot.
Not working on non rooted device.
It works in adb shell after su command..however it resets back to default after reboot...Could someone make this into a magisk module?
abhishek0704 said:
Not working on non rooted device.
Click to expand...
Click to collapse
dsjd said:
It works in adb shell after su command..however it resets back to default after reboot...Could someone make this into a magisk module?
Click to expand...
Click to collapse
Yeah even I saw that it goes back to normal even without a reboot.
The EmergencyAffordanceService periodically scans the MCC of the SIM and sets that value to 1 if the MCC is 404 or 405.
So I tried spoofing the MCC in many different ways, but none of them worked for me.
This section of the config file sets the list of the MCC codes for which EmergencyAffordance is enabled.
Code:
<!-- Do not translate. Mcc codes whose existence trigger the presence of emergency
affordances-->
<integer-array name="config_emergency_mcc_codes" translatable="false">
<item>404</item>
<item>405</item>
</integer-array>
If we can somehow modify this array, I think it should be permanently disabled. But I guess that would require an Xposed module or apk editing (areas I know nothing about)
There are other methods I'm sure, maybe one involving an Xposed module which hooks the method that checks for the MCC codes and makes it return false.
If anyone has any ideas, please do chime in.
any idea how the phone detects that its india? Could we spoof that?
Failure transaction error in OB2 even after su command.
---------- Post added at 03:17 PM ---------- Previous post was at 03:15 PM ----------
Failure calling service settings: Failed transaction (2147483646)
zeeshanonlyme said:
Failure transaction error in OB2 even after su command.
---------- Post added at 03:17 PM ---------- Previous post was at 03:15 PM ----------
Failure calling service settings: Failed transaction (2147483646)
Click to expand...
Click to collapse
Use ADB shell instead of doing in on your phone
Any update? I literally had to stop using oos because of this..there was an XDA developers on reddit who was trying to solve this issue but I can't seem to find it
Edit: Found It
https://www.reddit.com/r/oneplus/comments/6ur1ma/double_tap_power_button_setting/
The devs name is Mishaal Rahman ...Maybe he could help us out.
abhishek0704 said:
Not working on non rooted device.
Click to expand...
Click to collapse
dsjd said:
It works in adb shell after su command..however it resets back to default after reboot...Could someone make this into a magisk module?
Click to expand...
Click to collapse
dsjd said:
Any update? I literally had to stop using oos because of this..there was an XDA developers on reddit who was trying to solve this issue but I can't seem to find it
Click to expand...
Click to collapse
I've (kind of) figured out a few ways to resolve this, but not the implementation part.
This Xposed module should be able to solve the issue by making the method check return false, but I cant seem to get the module working on my device.
Anyone with Xposed, could you see if the module is working for you? It FCs whenever I open it.
dsjd said:
Any update? I literally had to stop using oos because of this..there was an XDA developers on reddit who was trying to solve this issue but I can't seem to find it
Click to expand...
Click to collapse
I've (kind of) figured out a few ways to resolve this, but not the implementation part.
This Xposed module should be able to solve the issue by making the method check return false, but I cant seem to get the module working on my device.
Anyone with Xposed, could you see if the module is working for you? It FCs whenever I open it.
Sorry for bumping an old thread but has anybody figured out how do get this working permanently with xposed or magisk ? I bought a OP6 and miss this feature coming from a Nokia 7+
MAGISK Module!
Hi,
Was able to create a magisk module to do this automatically every boot and also got wifi auto turn on to work, check out the thread here.
kashyapha1994 said:
Yeah even I saw that it goes back to normal even without a reboot.
The EmergencyAffordanceService periodically scans the MCC of the SIM and sets that value to 1 if the MCC is 404 or 405.
So I tried spoofing the MCC in many different ways, but none of them worked for me.
This section of the config file sets the list of the MCC codes for which EmergencyAffordance is enabled.
Code:
<!-- Do not translate. Mcc codes whose existence trigger the presence of emergency
affordances-->
<integer-array name="config_emergency_mcc_codes" translatable="false">
<item>404</item>
<item>405</item>
</integer-array>
If we can somehow modify this array, I think it should be permanently disabled. But I guess that would require an Xposed module or apk editing (areas I know nothing about)
There are other methods I'm sure, maybe one involving an Xposed module which hooks the method that checks for the MCC codes and makes it return false.
If anyone has any ideas, please do chime in.
Click to expand...
Click to collapse
Might be possible to override this with an overlay (non-root Substratum.)

[ROM][PORT][9.0.0][dumpling]Pixel Experience for 5T[05.09.2018]

What's this?
First of all, I'm not the original developer.
He post it on other Chinese forum, and I am just to ask for his permission and post it here.
All credits to Coolapk user: Tutoo.
This is an unofficial build of Pixel Experience Pie for Oneplus 5T (dumpling).
The original is for Oneplus5, you can find it here : Click here
The dev make a port version of this
What's working :
Boots
RIL (Calls, SMS, Data)
Fingerprint
WiFi
Bluetooth
Camera (but same as other Pie ROM, a little laggy in third apps)
Flashlight
Camcorder
Sound / vibration
GPS
AOD
Hotspot
NFC
VPN
And device specific addition (same as OP5 thread)
Known issues:
Permissive
or other issue same as OP5
Fingerprint gesture to view notification also not working
But you can try the solution provide by @Sabissimo at #16
Although that didn't work for me, some report they success, still looking into the problem
If that work for you, don't forget to give him a thank
If you find any bugs, you can PM me or leave comments below, I'll reported it to original dev
Instructions :
First, backup your data to PC or laptop
Second, you HAVE TO wipe data,system,cache AND INTERNAL STORAGE (some reported that it didnt boot if no wipe internal storage)
Third, flash the ROM and No verity zip (In my case, I use v3, but it seems with no problem)
Now you can boot up your device, it'll boot up TWO TIMES, and this is normal
CAUTION !!!
Version1 already include Gapps,Magisk (16.7), firmware, gcam and Redflare kernel (1.13 build)
So it is unnecessary to flash other zips
But in Version2, it didn't have firmware, but with Magisk (17.1) and Redflare kernel (1.16 build)
you guys need to take notice of this
Downloads:
Because original was on Baidu Cloud, and it may block some countries IP (Example: Taiwan)
So I upload it to Google Drive
If it is needed to upload to AFH or other cloud, just PM me, I'll upload it when I'm free
Here is the GD link:Version1
Version2
Credits:
Coolapk user "Tutoo" for his awesome work
and XDA user @bhageerathreddyy for help testing
Because of the forum rule, TG group link are not allow to post publicly here.
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.4.152, RedFlare EAS kernel
ROM Firmware Required: TWRP, Unlocked bootloader
Based On: AOSP
Version 2 changelog:
VoLTE reset on reboot Fixed
Proximity Sensor Fixed for FP and Gestures (Now phone won't start dialling numbers when in your pocket )
Added more Off screen Gestures and fixed V gesture
Improved OMNI slider switch
RedFlare kernel 1.16+
Linux 4.4.154
(Well... I copied these from original 5's thread. Don't forget to thank him for fix !!)
thanks
Thanks
Sent from my ONEPLUS A5010 using Tapatalk
This was much faster than expected for this rom, been swapping between this and OOS, will have to test this tonight and Pie for the first time, ty for fast release.
HI, just flashed this. Looks and feels good but the fingerprint swipe gesture doesn't seem to work properly, It treats it like arrow keys and navigates around the UI.
rijads said:
This was much faster than expected for this rom, been swapping between this and OOS, will have to test this tonight and Pie for the first time, ty for fast release.
Click to expand...
Click to collapse
Can u tell me dose it includes the adaptive battery and gcam ? And how are the animations ? And notification slider options
ROM is awesome! Adaptive battery, gcam, slider - all working
To make fingerprint gestures work, put this file in /system/usr/keylayout , and give it 755 permissions
https://drive.google.com/file/d/1Nhjs7YWulTHy-6d-AM1R1cLN_TfK-ieY/view?usp=sharing
MyStyle0714 said:
What's this?
First of all, I'm not the original developer.
He post it on other Chinese forum, and I am just to ask for his permission and post it here.
All credits to Coolapk user: Tutoo.
Click to expand...
Click to collapse
THREAD MOVED TO HOW-TO
Per the Device Forum Rules, all threads posted in the Development section must be your own work. ROM shares may be posted in the How-To section.
@Sabissimo how long does the boot took for you ? im on google bootanimation but nothing has happened since last 5 minutes ! can you also explain your installation process !
didn't help
Sabissimo said:
ROM is awesome! Adaptive battery, gcam, slider - all working
To make fingerprint gestures work, put this file in /system/usr/keylayout , and give it 755 permissions
https://drive.google.com/file/d/1Nhjs7YWulTHy-6d-AM1R1cLN_TfK-ieY/view?usp=sharing
Click to expand...
Click to collapse
i did what you wrote,
now swiping doesn't do anything
tids2k said:
@Sabissimo how long does the boot took for you ? im on google bootanimation but nothing has happened since last 5 minutes ! can you also explain your installation process !
Click to expand...
Click to collapse
First boot took about 1 min max. You have to be decrypted, flash rom, flash noverity (I flashed v3) - and you should be good.
---------- Post added at 11:06 AM ---------- Previous post was at 11:00 AM ----------
korm85 said:
i did what you wrote,
now swiping doesn't do anything
Click to expand...
Click to collapse
Well, it's definitely working for me tho, be sure to give it permissions.
Also, don't know if it matters, but I've searched for "swipe" in settings, and got in "Swipe fingerprints for notifications" menu, which is (weirldy) not available in "Gestures", there was no toggle there, tho, just instructions video. Maybe just entering that menu enabled that, try it out.
@Sabissimo did you update your firmware to 5.1.5 ? and have you installed vendor partition data ?
tids2k said:
@Sabissimo did you update your firmware to 5.1.5 ? and have you installed vendor partition data ?
Click to expand...
Click to collapse
I was on OB15, so whatever firmware it uses - I have it And had vendor of OB15, but I don't think that vendor matters, since this is not treble rom, and doesn't use /vendor, it uses /system/vendor
Sabissimo said:
Well, it's definitely working for me tho, be sure to give it permissions.
Also, don't know if it matters, but I've searched for "swipe" in settings, and got in "Swipe fingerprints for notifications" menu, which is (weirldy) not available in "Gestures", there was no toggle there, tho, just instructions video. Maybe just entering that menu enabled that, try it out.
Click to expand...
Click to collapse
Well... the dev said that the ROM doesnt have that function, but how can you enable ? I also follow your steps and give them permission then reboot again, but nothing happen.
Step-by-step of what I did:
1. Wiped everything except internal storage
2. Flashed ROM
3. Flashed no-verity v3
4. Rebooted, it rebooted twice, then started booting up with google animation
5. Noticed that fingerprint is working as cursor, went to settings, searched for "swipe", entered that menu, there's no toggle there
6. Pasted gf_input.kl in /system/usr/keylayout, gave it 755 permissions
7. Rebooted and everything is working!
Try doing it in the same sequence (First try to to enter swipe menu before pasting gf_input.kl, then paste it), maybe that did the trick.
Sabissimo said:
Step-by-step of what I did:
1. Wiped everything except internal storage
2. Flashed ROM
3. Flashed no-verity v3
4. Rebooted, it rebooted twice, then started booting up with google animation
5. Noticed that fingerprint is working as cursor, went to settings, searched for "swipe", entered that menu, there's no toggle there
6. Pasted gf_input.kl in /system/usr/keylayout, gave it 755 permissions
7. Rebooted and everything is working!
Try doing it in the same sequence (First try to to enter swipe menu before pasting gf_input.kl, then paste it), maybe that did the trick.
Click to expand...
Click to collapse
Confirm this was the exact process I followed and works like a charm. Just need a couple of days with it to test battery life.
just have one thing to say thankyou so much and this rom is just smooth
For anyone that wants to flash this ROM, don't worry about your firmware. This ROM's .zip file contains a firmware ALREADY so it will flash the necessary firmware itself!
Sabissimo said:
Step-by-step of what I did:
1. Wiped everything except internal storage
2. Flashed ROM
3. Flashed no-verity v3
4. Rebooted, it rebooted twice, then started booting up with google animation
5. Noticed that fingerprint is working as cursor, went to settings, searched for "swipe", entered that menu, there's no toggle there
6. Pasted gf_input.kl in /system/usr/keylayout, gave it 755 permissions
7. Rebooted and everything is working!
Try doing it in the same sequence (First try to to enter swipe menu before pasting gf_input.kl, then paste it), maybe that did the trick.
Click to expand...
Click to collapse
where is this gf_input.kl?? why should i do this for the pill gestures?

[Guide][nonroot] Fix AndroidQ no UI sound bugs

Since I originally wrote this I have found an even easier way that works 100% without root using Setting database editor so I've updated this guide to the better method.
as a few of us 2XL owners will know Google derped sounds on the factory image of Q and our nice charging sound has been replaced with a horrible Error sound (Google Bug tracker.)
after a few weeks of waiting & trying to fix the issue myself I have finally managed to figure it out...
turns out they're trying to access sounds from the WRONG location
UI sounds on factory Q image seem to trigger from /product/media/audio/ui but this directory only has boot animations, no audio as these files are actually located in /system/media/audio/ui
it's probably why upgrading from 9 to 10 keeps the audio settings but factory flashing doesn't.
https://play.google.com/store/apps/details?id=by4a.setedit22
Install the settings database editor (link above)
Code:
open a terminal app and type(or copy paste) the line below;
pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
or using adb:
Code:
adb shell
pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
using setedit go to the global tab and look for each of the UI audio settings, switch /product/media/audio*.* to /system/media/audio/*.*
Restart your phone to apply the settings.
car_dock_sound /system/media/audio/ui/Dock.ogg
car_undock_sound /system/media/audio/ui/Undock.ogg
desk_dock_sound /system/media/audio/ui/Dock.ogg
desk_undock_sound /system/media/audio/ui/Undock.ogg
lock_sound /system/media/audio/ui/Lock.ogg
low_battery_sound /system/media/audio/ui/LowBattery.ogg
trusted_sound /system/media/audio/ui/Trusted.ogg
unlock_sound /system/media/audio/ui/Unlock.ogg
wireless_charging_started_sound /system/media/audio/ui/ChargingStarted.ogg
Minor notes:
I'm unsure why the charging sound is dictated by wireless_charging setting.
I've had a report that settings revert after a few reboots, I've not had this myself and I've rebooted a lot but if it happens just reapply the changes in setedit.
You can also change the sounds to files on your system, I've not had luck pinpointing my sdcard folder but I have been able to change Lock.ogg to Dock.ogg as a test.
(/Sdcard/download didn't work)
_________( Old method )_________
This is my first write up so please bear with me
please note I'm not responsible for any messups you make doing this
it can be done on a terminal emulator, I prefer ADB shell
in order to sucessfully do this you will need HiddenSettings magisk module
Thank you skittles9823
I'm unsure if you need busybox but the module certainly looks for it
Code:
[B][COLOR="red"]adb shell[/COLOR][/B] or launch your [I]TerminalApp[/I]
taimen:/ $[B][COLOR="red"]su[/COLOR][/B]
taimen:/ [I]#[/I] [B][COLOR="red"]hidden[/COLOR][/B]
4 - All settings
[CHOICE]:[B][COLOR="red"]4[/COLOR][/B]
3 - Modify settings
[CHOICE]:[B][COLOR="red"]3[/COLOR][/B]
===== Modify Settings =====
[Search?]:[B][COLOR="Red"]wireless_charging_started_sound /system/media/audio/ui/ChargingStarted.ogg[/COLOR][/B]
press enter & reboot your phone.
That is pretty much it, hopfully the android team fix this next patch.
I'll add some notes from what I have found through tinkering
you must reboot after modifying EACH setting.
you can see the "=" is not added when changing the settings wireless_charging_started_sound=/system/media/audio/ui/ChargingStarted.ogg (wrong)
wireless_charging_started_sound /system/media/audio/ui/ChargingStarted.ogg (Right)
Here are all the settings i can find
car_dock_sound /system/media/audio/ui/Dock.ogg
car_undock_sound /system/media/audio/ui/Undock.ogg
desk_dock_sound /system/media/audio/ui/Dock.ogg
desk_undock_sound /system/media/audio/ui/Undock.ogg
lock_sound /system/media/audio/ui/Lock.ogg (this causes an error on my phone)
low_battery_sound /system/media/audio/ui/LowBattery.ogg
trusted_sound /system/media/audio/ui/Trusted.ogg
unlock_sound /system/media/audio/ui/Unlock.ogg
wireless_charging_started_sound /system/media/audio/ui/ChargingStarted.ogg
Awesome job figuring this out. Hopefully Google will fix this in the November system images since You've done all the work for them.
Great job and thanks for it, so this works with the charging sound issue but not the locking/unlocking sound?, As for the charging sound i already have a workaround for it as i have gravitybox and edxposed installed and gravitybox have a option to change charging sound, hoepfully google will fix both in upcoming noember update
Nightf0x_007 said:
Great job and thanks for it, so this works with the charging sound issue but not the locking/unlocking sound?, As for the charging sound i already have a workaround for it as i have gravitybox and edxposed installed and gravitybox have a option to change charging sound, hoepfully google will fix both in upcoming noember update
Click to expand...
Click to collapse
I have found an even easier way that works 100% using setedit:
https://play.google.com/store/apps/details?id=by4a.setedit22
Install the app open a terminal app
pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
Job done easier to edit
Out of habit I typed su to enable root before granting write permissions so if it doesn't work without enabling su try that
co4 said:
I have found an even easier way that works 100% using setedit:
https://play.google.com/store/apps/details?id=by4a.setedit22
Install the app open a terminal app
pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS
Job done easier to edit
Out of habit I typed su to enable root before granting write permissions so if it doesn't work without enabling su try that
Click to expand...
Click to collapse
Does settings revert back after multiple reboots ? Cause this happened to me
Nightf0x_007 said:
Does settings revert back after multiple reboots ? Cause this happened to me
Click to expand...
Click to collapse
I've yet to have anything revert yet if it does happen I'll post, I guess you can reapply the settings? Or once they revert can they be re changed?
Awesome it worked I have all my sounds back!!!!
krolla03 said:
Awesome it worked I have all my sounds back!!!!
Click to expand...
Click to collapse
I'll add that it's been reported that setting may revert and reapplying will fix it again
co4 said:
I'll add that it's been reported that setting may revert and reapplying will fix it again
Click to expand...
Click to collapse
so far so good
Thank you SOOO much! :highfive: It works on my Pixel 2. Had to reset it to factory after the December update killed my Pixel launcher app. After the reset I faced this horrible charging sound and the lack of lock sounds, too.
God this was driving me crazy on a warranty replacement Pixel 2. 3rd replacement and finally it boots and the battery is decent.
I don't know if I would have noticed but for having 2 phones side by side. After that, I couldn't un-hear it.
What about Effect_tick.ogg? Is there any way to set this custom sound?
Hi,
I've tried the first method, but I couldn't grant permissions in the Terminal app, it fails!
I don't have root.
Can anyone help?
Thank you so much
All these sounds work on my Pixel 1, but I get the error sound whenever I get a notification while in call. Does anybody know where I can find that sound? It's not in SetEdit.
Mandrutz said:
All these sounds work on my Pixel 1, but I get the error sound whenever I get a notification while in call. Does anybody know where I can find that sound? It's not in SetEdit.
Click to expand...
Click to collapse
I have this also on my pixel 2 does anyone know the ADB script for that?

Categories

Resources