Related
SUPREME Mods v1.5
For CM9/ICS!
FEATURES:
Code:
-wifi speed increases
-changed bluetooth name to "Touchpad"
-increased quality of photos and videos
-added initial dalvik heapsize for better start up
-changed the wifi scan interval to 180 (save battery when not connected to wifi)
-kernel tweaks for less debugging/more RAM
-higher events per second for the window manager (smoother scrolling)
-overall performance boost and responsiveness increase with higher cache values
-disable sending usage data (not sure if functional but it was a property listed in the documentation)
-deeper sleep during the night hours for better battery life
-disables error checking
-faster media streaming
-changed device info to that of a SGH-T989 from Samsung so most Gameloft games are compatible to download the SD files
-270 degree rotation
-uses image dithering for faster performance
-keeps launcher in memory for faster launcher performance
-better battery management in terms of percentage and associated kernel actions
-better sqlite management for apps
-better sqlite management for apps
-faster app switching between google apps
-defragmentation of database files
-cleaner of temporary files at bootup that are no longer in use
If you want support, either post here or ask me on twitter: http://twitter.com/rohanXm
COMPATABILITY: Tested on Cyanogenmod Alpha 2 and the CM9 nightlies, may/may not work on other ROMs!
If you install this with ROMs other than CM9, then you will see many side effects in the Settings app, such as it displaying you are running CM9 when really you are running some other ROM. The build.prop is built off of the latest official nightly, 20120404.
DOWNLOAD:
Choose the DPI you want and download the respective one!
160 DPI: supreme-rohan-v1.5-160dpi.zip
120 DPI: supreme-rohan-v1.5-120dpi.zip
If you don't know what DPI is, download the 160 DPI version.
DOWNLOAD IS HERE: http://goo-inside.me/devs/rohan/tenderloin/SUPREME Mods
Current version is v1.5
Click to expand...
Click to collapse
INSTRUCTIONS
WARNING: Make a nandroid backup before downloading this!
If something goes wrong (even though it has been tested numerous times) its always good to have a backup! I am not responsible for anything that happens to your device as a result of this!
1. Download the .zip from goo-inside.me linked below
2. Reboot into ClockworkMod
3. Install zip from SD Card -> Browse for zip you just downloaded
4. Wipe Dalvik cache (in advanced menu)
4. Reboot
5. Heres the decision point: you can either end here, or you can continue on to install the V6 ICS Supercharger script. The process is a little bit involved, so if you don't want to continue, you don't have to. I reccomend you do continue though, as the Supercharger script makes a very big difference in terms of speed! For those of you who choose not to continue, thanks for installing the SUPREME Modpack! Enjoy your Touchpad! For those that want the ICS Supercharger too, continue below!
=======================================================
6. Download the latest Supercharger script from this post: http://forum.xda-developers.com/showthread.php?t=991276 to your /Download folder (the file is called "V6_SuperCharger_for_Android-update8.sh.txt") (Note: the name might change if a new release of the script comes out)
7. Continuing to install the supercharger script... open up a file manager and rename the file to get rid of the .txt extension (so that it becomes a .sh extension)
8. Open up the app called Terminal Emulator on your Touchpad. If its not already installed (it should have come with CM9) then just install it from the market.
7. In the Terminal, type the following.
Code:
su
Then accept the Superuser request that opens up.
8. Then type:
Code:
sh /Download/V6_SuperCharger_for_Android-update8.sh
(Note: the name might change if a new release of the script comes out)
9. The screen will display some text as the script loads up. Be patient and wait.
10. After loading, it will come to a thing where it detects what launcher you are running. Press the enter key to confirm your launcher.
11. The script will do some more stuff and then ask for what type of scrolling you want. Type in "1" without quotes to confirm you want fast scrolling to make the install process quicker and then press enter.
12. It will do some more stuff and then ask about integration. Type "y" without quotes confirming you want integration and then press enter.
13. It will do some more stuff and then ask about animations. Type "y" without quotes confirming you want to disable the animation and then press enter.
14. It will do some more stuff and then ask about what type of Supercharger you want. Type "9" without quotes confirming you want the highest and most aggressive tweaks (they work the best for the Touchpad) and then press enter.
15. The script will finish up and then ask if you want to super clean your system. Type "y" without quotes and then press enter. Your system will reboot.
16. Go to this link: http://android.mimic.ca/
17. Upload your services.jar file from the /system/framework/ directory
18. Patch the file using the online patcher
19. Download the CWM file it gives you (the .zip). Don't worry about what it says about being for Nexus S.
20. Reboot to recovery and flash the CWM file it just gave you.
Congrats, you have the SUPREME Modpack and the ICS Supercharger scripts installed! Reboot normally and enjoy!
To update, just follow the same instructions as the install directions! You will also need to install every time you install a new ROM.
Click to expand...
Click to collapse
Changelog:
4/05: -Removed the ICS Supercharger script as its creator respectfully asked for it to be removed from the package. You may still install it separately though using the instructions I posted though.
-Cleaned up the init.d file thanks to tweaks made by archrival
4/1: -Includes the ICS Supercharger Script from zepplinrox! Original thread is here: http://forum.xda-dev...44#post16635544
-Cleaned up the init.d tweak file and removed conflicting code
-Updated the build.prop to the latest official nightly
-Added database defragmentation
-Added removal of temporary system files at bootup
3/10: -MANY new tweaks!
-Fixed some wifi issues due to some unruly init.d tweaks
-better sqlite management for apps
-faster app switching between google apps
3/3: -Added an init.d tweak file!
-270 degree rotation
-uses image dithering for faster performance
-keeps launcher in memory for faster launcher performance
-attempts to always keep the home button on
-better battery management in terms of percentage and associated kernel actions
-kernel tweaks for less debugging/more RAM
2/27: -Added comments to build.prop file so that you guys can customize it easier if you want to
-increased quality of photos and videos
-added initial dalvik heapsize for better start up
2/26: -Initial release
this sounds amazing but i am just wondering if i could edit this so it doesnt touch the dpi at all? i use 132 right now and dont want to mess with it, other then that this sounds amazing
First time posting in the touchpad forums...
I applied this mod and attempted to install 9mm but still got a "not compatible with this device" error. Unless I'm in error of some sorts I believe this game still has issues running on our devices. I at least had to give this a shot to maybe see if it would help with me getting this game installed.
Nonetheless excellent work and thank you for your contribution!
slyr114 said:
this sounds amazing but i am just wondering if i could edit this so it doesnt touch the dpi at all? i use 132 right now and dont want to mess with it, other then that this sounds amazing
Click to expand...
Click to collapse
I added the build.prop text in the OP near the bottom, in a pastebin link. Copy the text from there, paste it into your build.prop, and then find the line for the density and edit that back to 132 before saving.
freaktractor said:
First time posting in the touchpad forums...
I applied this mod and attempted to install 9mm but still got a "not compatible with this device" error. Unless I'm in error of some sorts I believe this game still has issues running on our devices. I at least had to give this a shot to maybe see if it would help with me getting this game installed.
Nonetheless excellent work and thank you for your contribution!
Click to expand...
Click to collapse
I don't own the game so I was not able to test it, sorry! I know this change has worked for Modern Combat 3, Asphalt, and a couple other games. I will look into making 9mm work, since this might be a problem across multiple games!
Testing now, will let you know how it goes over the next few days
apply dalingrin's 120dpi
Click to expand...
Click to collapse
Sorry for the n00b question, but how do you apply this ? By just installing the Alpha 2 or is there a standalone zip ?
JohnKoffee said:
Sorry for the n00b question, but how do you apply this ? By just installing the Alpha 2 or is there a standalone zip ?
Click to expand...
Click to collapse
Install the zip file from the link in the first post in clockwork recovery mode after you have installed Alpha 2.
I'm on Classicnerd Butta 0.1.1-v3.2 and will definitely flash this at work to test it out.
Sent from my SAMSUNG-SGH-I727 using XDA App
Im really looking forward to a smoother scrolling experience. I love my tp immensely but I've always found the very subtle studder of scrolling to be a little displeasing when it comes to scrolling in between home screens. Does this "smooth scrolling" enhancement effect web browsing scrolling?
I am definitely going to give this a shot bud, brb with thoughts and opinions. Thanks again for your work in this community.
---------- Post added at 03:05 AM ---------- Previous post was at 02:39 AM ----------
Anyone have a link to dilinger's 120dpi fix?
Please help me to fix usb storage fix
Please help me to fix usb storage fix.Because when i connecting my touchpad to computer, nothing is happening.Touchpad memory is not opening.
i tried turning off developer mod.then also same.How to fix this
please help me
thanks
bentech4u said:
Please help me to fix usb storage fix.Because when i connecting my touchpad to computer, nothing is happening.Touchpad memory is not opening.
i tried turning off developer mod.then also same.How to fix this
please help me
thanks
Click to expand...
Click to collapse
Lmao.
Plug in your device. Then Go to: settings, then click on storage on the left. then on the top right you will see 3 vertical dots, click it for more options. "USB computer connections" will be available. Select it. Then check mark the "media device (MDP)" field.
If you're using windows, ignore the driver installer error prompt. Your TP should still be visible when you go to my computer.
Push Thanks if I helped. i hope I did. >.> lol
thanks it's working now.
freaktractor said:
First time posting in the touchpad forums...
I applied this mod and attempted to install 9mm but still got a "not compatible with this device" error. Unless I'm in error of some sorts I believe this game still has issues running on our devices. I at least had to give this a shot to maybe see if it would help with me getting this game installed.
Nonetheless excellent work and thank you for your contribution!
Click to expand...
Click to collapse
its the dpi change to 160 9mm works just fine i beat the game on my TP i use PG86100 on the build prop evo 3d
What changes did you make to make better media streaming?
I don't want to make all the changes.
Sent from my cm_tenderloin using Tapatalk
Can someone point me to dalingrin's dpi fix? Can't find it anywhere. thanks!
grukko said:
Can someone point me to dalingrin's dpi fix? Can't find it anywhere. thanks!
Click to expand...
Click to collapse
Taken from Alpha 0.6 thread on rootzwiki.
LCD Density Updates:
120: http://goo.gl/2vd7h
Revert to 160: http://goo.gl/mndEs
Click to expand...
Click to collapse
This really works! I was stuck using 160dpi on Alpha2 because 120 or 132dpi both were not smooth, they had a small skip or judder when transitioning screens. Bugged the heck out of me so I set it to 160dpi where it is smooooth.
I flash this build.prop this morning and 132 is now just as smooth! Not sure what else it fixed but it didn't break anything which is always a good thing. Me happy
Thanks Rohan!
Nice one
Changed the build.prop in notepad to 160dpi then saved over the top and just flashed, now I'm playing BackStab HD! Thank you very much!
Thanks for doing this but I have a question. In your OP, you listed:
disables error checking (may have side effects)
Does this affect the SD card error checking (fsck_msdos) that the TP does on boot, which shows up as Preparing SD card on notifications?
Btw, just a suggestion that it might be a good idea to put a line in your OP and recommend doing a nandroid backup or at least backing up of the original build prop file before flashing this. Thanks again.
Mike T
Hi guys, sorry, just got back from school. I've answered some of your questions below.
Also, just wanted to say that tonight I will be adding a whole boatload of improvements via the init.d file. I worked on it at school today for a little bit at lunch and it should bring a whole host of speed improvements and smoother aspects to CM.
@Mr.Quipster Yes, this also affects the web pages. It increases the screen's refresh rate when scrolling, thus allowing a "smoother" experience.
@ruthienu I've changed it so that StageFright, the media streaming tool in Android 2.2+ scans meta tags, as well as HTTP filesystems for media. It doesn't hurt to have these lines in there if you aren't using media streaming. It also doesn't interfere with anything else. If you want to delete it, flash the zip and delete lines 101-104 [the ones starting with media.stagefright(...)]
@webdroidmt Nope, this disables something called CheckJNI. It basically scans the system every now and then for things such as invalid variables and arrays, bad buffers, and some UTF-8 errrors. None of the errors it catches are system-threatening and disabling it frees up a substantial amount of RAM. If you do not want this to be enabled as a feature then simply flash the zip, then edit your build.prop and delete the line "ro.kernel.android.checkjni=0". And thanks for the suggestion, added a warning
So guys, I finally managed to get fix for quick toggles bar and notification bar after changing DPI .
changing DPI will make notification bar and quick settings toggle bar look weird , distorted and not usable .
below is the screen shot which explains what i meant !
Now i am still not able to solve the shutdown pull down menu , but rest all works . ( anyway i use advanced reboot options app for these , as stock doesn't provide ).
Instructions :
1. Firstly u need root and xposed
2. download EASY DPI changer app
3. change DPI to whatever u want and reboot
4. now go to xposed
5. download app settings module
6. enable the module and reboot
7. open app settings
8. search for System UI
9. enable its settings
10. now add 480 DPI value instead of 0 in first column
11. save its settings
12. reboot
DONE !!
Now u can make per app basis DPI change , so customize as per your preference. changing DPI makes app icons smaller and makes H2 OS launcher apps misaligned .then if you try to change H2 OS launcher DPI , it makes system apps look normal but not downloaded apps, SO i recommend any third party launcher like Nova.
BUT MOST IMPORTANT THING : BOTH NOTIFICATION AND QUICK TOGGLE BAR WORK FLAWLESSLY .
Special Thanks @RajGopi ( xposed module Idea )
you can change your DPI by just deleting the # before lcd_density row
p.s. just read the post again and understand what you mean, good job.
slowsunset said:
you can change your DPI by just deleting the # before lcd_density row
p.s. just read the post again and understand what you mean, good job.
Click to expand...
Click to collapse
You didn't get what he meant.
---------- Post added at 06:25 AM ---------- Previous post was at 06:18 AM ----------
BTW, big thanks @kunalshah912. The DPI problem for me in H2OS is finally solved. ?
Hi guys;
I found a way to enable the double tap to wake up in LineageOS and RR for the mi mix.
Here it comes:
1: Donwload the Root Explorer and the QuickEdit;
2: With Root Explorer, go to sys/bus/i2c/12-0038/wakeup-mode;
3: Open that with Quick Edit and change the value "0" to "1";
4: Save it;
5: Have fun.
This is my first post here, take easy guys. I searched here for a solution for this problem, but didn't find anything about this two roms.
Thanks if it works!
PS: The only problem is that when you reboot the system, the system automatically returns to "0", so you will have to do the whole process again every time you restart the device. Does anyone know the solution to leave this fixed by default?
I'll add that to init process in ramdisk and enable it in source again. In build 0412 it is disabled, but it seems to work anyway Thx for finding it out.
pappschlumpf said:
I'll add that to init process in ramdisk and enable it in source again. In build 0412 it is disabled, but it seems to work anyway Thx for finding it out.
Click to expand...
Click to collapse
No problem! This is a tweak that I cant live without! And, congratulations for the amazing job. The ROM is perfect to me, Im using as my daily driver. The only 2 problens that I found, is this one and the low volume in Calls. Thanks to provide this ROM, I really appreciated.
Great! Is working fine...
Hello ,
works fine , but after reboot it is back to"0"
mfg , hjf
hjfisch said:
Hello ,
works fine , but after reboot it is back to"0"
mfg , hjf
Click to expand...
Click to collapse
As I said
Couldn't i just change the value and save the file as read only? I'm kind of afraid to try it out but wouldn't that work?
Blackphantom said:
Couldn't i just change the value and save the file as read only? I'm kind of afraid to try it out but wouldn't that work?
Click to expand...
Click to collapse
Will work. Just change the value to 1, save and exit. But, every time that you reboot the device, u will need make the process again.
I understand that. My question was if i save the file as read only wouldn't that "deny" the system from changing the value even after rebooting?
Blackphantom said:
I understand that. My question was if i save the file as read only wouldn't that "deny" the system from changing the value even after rebooting?
Click to expand...
Click to collapse
Dont know. Could you try and post the result?
Blackphantom said:
I understand that. My question was if i save the file as read only wouldn't that "deny" the system from changing the value even after rebooting?
Click to expand...
Click to collapse
NO, as /sys is just a mountpoint for a virtual Filesystem (type sysfs)
So basically, everything under /sys/ is virtual, so no real Files, so no persistance after a reboot. At least not by interacting with sysfs.
This is the Linux way of making runtime live adaptations of certain hardware or software features.
Let me give you an example.
On a regular Dektop-Linux, if you do:
>> echo "1" > /sys/block/sda/device/delete
on the command line, you tell the kernel to flush the caches of the sda disk and spin it down. (so you could safely hotswap)
and if you do not replace your disk, but now want to get that disk spinning again, you put:
>> echo "0 0 0" > /sys/bus/scsi/devices/host1/scsi_host/host1/scan
into console.
So some of the Files there are read only (in like nothing happens when you change the content) , and others can be tampered with, but every change is gone after reboot.
except when you can manage to let some startup-skript make those changes, or you can edit the kernel-source default initialisation variables.
rootgremlin said:
NO, as /sys is just a mountpoint for a virtual Filesystem (type sysfs)
So basically, everything under /sys/ is virtual, so no real Files, so no persistance after a reboot. At least not by interacting with sysfs.
This is the Linux way of making runtime live adaptations of certain hardware or software features.
Let me give you an example.
On a regular Dektop-Linux, if you do:
>> echo "1" > /sys/block/sda/device/delete
on the command line, you tell the kernel to flush the caches of the sda disk and spin it down. (so you could safely hotswap)
and if you do not replace your disk, but now want to get that disk spinning again, you put:
>> echo "0 0 0" > /sys/bus/scsi/devices/host1/scsi_host/host1/scan
into console.
So some of the Files there are read only (in like nothing happens when you change the content) , and others can be tampered with, but every change is gone after reboot.
except when you can manage to let some startup-skript make those changes, or you can edit the kernel-source default initialisation variables.
Click to expand...
Click to collapse
Yeah that makes sense. I tried it and realized that it was set back to zero every time i restarted so i figured it would be something like that. Luckily DT2W works now in the build so we don't have to do that anymore.
Thanks for the explanation though. Really appreciated.
Hey there
i followed your steps but i cant seem to find the 12-0038 folder after i2c. Any thoughts?
If you're using Lineage just install the DragonXiaKernel. Double Tap To Wake is working fine.
Tiago A said:
Hi guys;
I found a way to enable the double tap to wake up in LineageOS and RR for the mi mix.
Here it comes:
1: Donwload the Root Explorer and the QuickEdit;
2: With Root Explorer, go to sys/bus/i2c/12-0038/wakeup-mode;
3: Open that with Quick Edit and change the value "0" to "1";
4: Save it;
5: Have fun.
This is my first post here, take easy guys. I searched here for a solution for this problem, but didn't find anything about this two roms.
Thanks if it works!
PS: The only problem is that when you reboot the system, the system automatically returns to "0", so you will have to do the whole process again every time you restart the device. Does anyone know the solution to leave this fixed by default?
Click to expand...
Click to collapse
I installed "lineage-14.1-20170415-UNOFFICIAL-X3". I only get path till sys/bus/i2c/
There is no 12-0038/ folder. Can you help me out on this? I need it badly.
same here, no 12-0038
running smooth with 14.1-20170725-NIGHTLY-hammerhead though
Same for me on 14.1 LG g4 can't t find the file
Ls .../i2c/devices/
0-0006
0-a004
0-a006
1-0051
10-0048
11-003b
...
There iz no 12-0038 in both /i2c/ and /i2c/devices/
:crying:
Vipxpert said:
Ls .../i2c/devices/
0-0006
0-a004
0-a006
1-0051
10-0048
11-003b
...
There iz no 12-0038 in both /i2c/ and /i2c/devices/
:crying:
Click to expand...
Click to collapse
DT2W is working in RR (Oreo) just fine and I assume it's the same for Lineage 15.1 (Oreo). Which ROM are you using?
gavin19 said:
DT2W is working in RR (Oreo) just fine and I assume it's the same for Lineage 15.1 (Oreo). Which ROM are you using?
Click to expand...
Click to collapse
RR oreo as u said !
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.
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?