I'm running the UnNamed rom v.1.3.1. One of the reasons I'm using this rom is because it unlocks the Display settings for Screen Mode. Here you can choose between 3 modes:
Dynamic: SUPER saturated colors!!!
Standard: very saturated colors
Move: a bit oversaturated colors
I was hoping to be able to tweak these settings, but I can't find any definitive information on how to change them. I believe their settings are stored in 3 files in /system/etc
mdnie_tune_ui_dynamic_mode
mdnie_tune_ui_standard_mode
mdnie_tune_ui_movie_mode
There's a Color Saturation setting that difffers between them all. I tried to update the value the saturation in the Standard file to 0 to see if I could tone down the saturation. But edits to the file seems to have no effect. I even copied the content of the "movie" file to the "standard" file, and it doesn't change anything. Does anyone know how I can get these changes to take effect? Thanks.
Hi Guys.. I've been searching for ways to change the default color of Home Button of our Ray. Been on decompiling/compiling framework, settings... but got nothing or don't know exactly what xml/smali that controls the color of the buttons. So, by doing some trials-and-errors...:crying: Maybe this time I hit it.
First of all I want to thank:
JJDOCTOR for giving the hint to enable the light of Home button.
boy*racer*- max echo value is 20000
and all of you GUYS here on xda..
So here it is, navigate to system/etc/pre_hw_config.sh using ROOT EXplorer and find these lines:
echo 1000 > $dev/red/max_current
echo 1000 > $dev/green/max_current
echo 1000 > $dev/blue/max_current
and change to anything you want, I made it to
echo 1000 > $dev/red/max_current
echo 2000 > $dev/green/max_current
echo 9000 > $dev/blue/max_current
THE HIGHER THE VALUE, THE BRIGHTER THE LED.
Save changes....
For color preferences calculations: Go here. Thanks to Xtremy.
The above is nearly ICS Blue... You can put any values you want til 20000(?) except ZERO (0). By putting zero, that color will not be used by the system notifications ( I think)...
THIS WOULD NOT MAKE ALL OF THE NOTIFICATIONS COLOR TO THE COLOR YOU HAVE SET, ONLY THE DEFAULT HOME BUTTON COLOR IS AFFECTED. Sorry if the first flash of notification is not the COLOR you desired, only the succeeding flashes... I'm not a developer, I don't know how to do this correctly.
I THINK THIS WOULD NOT WORK ON CM-BASED ROM, BECAUSE THE HOME BUTTON LIGHT IS DISABLED (automaticbrightness is already set to FALSE). If somebody can make it to work, just apply it.
SOME DEFAULT COLOR WOULD NOT BE THE CORRECT APPEARANCE AFTER CHANGING THOSE LINES.. example, Violet is not violet when you use it as message notifications, still ICS Blue(?). Just raise the values.
REBOOT IS A MUST... Hope it won't bootloop...
adulfo said:
......................but got nothing or don't know exactly what xml/smali that controls the color of the buttons..........................:
Click to expand...
Click to collapse
XML is used to create user interface and the components used in app and java is used to create executable codes that will make apps functionality.
XML and smali are created automatically in app development.Though notepad++ is best to type XML.Best and easiest way to create a xml file is just write code in notepad++ and save it with extension of .xml.If you are developing an application of android then xmls are created by software itself. You will just need to specify name and add it to project as xml file...
thank you! i was just looking for this:good:
This is a nice mod adulfo! :good:
I wrote a little tutorial for finding your color value:
Go to this Color Wizard website.
Choose the color of your choice in de color bars.
In the #box you find the hex value for your color.
For this tut i use a nice orange E45F13 hex value.
Split de value in three pieces E4 5F 13.
1st byte E4 xx xx is for the Red value. (#FF0000)
2nd byte xx 5F xx is for the Green value. (#00FF00)
3rd byte xx xx 13 is for the Blue value. (#0000FF)
Open windows calculator set it in Scientific Mode.
1) Hit F5 to select HEX.
2) Type in your first hex (if HEX is 00, decimal is 0)
3) Hit F6 to convert to decimal.
Do this for all three hex values and write down the numbers...
1st byte E4 xx xx E4=228
2nd byte xx 5F xx 5F=95
3rd byte xx xx 13 13=19
As we know "max echo value is 20000" or 255 so:
20000 / 255 X 228 (your 1st above number)= 17882 for the Red Value
20000 / 255 X 95 (your 2nd above number)= 7450 for the Green Value
20000 / 255 X 19 (your 3rd above number)= 1490 for the Blue Value
Change the values in system/etc/pre_hw_config.sh for red, green and blue save & exit, reboot!
---------- Post added at 12:48 AM ---------- Previous post was at 12:37 AM ----------
I use the Tron Legacy Cyan color: 00DFFC
1000 for the Red Value.
17490 for the Green Value.
19764 for the Blue Value.
also note:
I set the first byte for Red to zero
after reboot it went to 1000 value,
so I think 1000 is the lowest value.
Thanks mate.. To those also having problems converting those values, you can google HEX to RBG converter.
wow it is very great and i change it
works perfect
4.0.4 587
psp1987 said:
wow it is very great and i change it
works perfect
4.0.4 587
Click to expand...
Click to collapse
Would be nice if you will read my signature...
what does this change ? the light shown when the phone is switched on and had no notification ?
-Jesco- said:
what does this change ? the light shown when the phone is switched on and had no notification ?
Click to expand...
Click to collapse
This would only change the default color of your Home button ( if only it is enabled), hitting any of your physical keys.
i changed all the values to 10000, all the colors are the same but a lot brighter, default 1000 is too dim for me.
@adulfo thanks for the tip buddy, can happily report that it is also working on my ray
Sent from my ST18i using xda premium
This values as depicted on the lines itself maybe clear, raising it, means raising LED current, more current more power,more power so much brighter... If you want color other than WHITE, don't make the values nearly equal.
Xtremy said:
also note:
I set the first byte for Red to zero
after reboot it went to 1000 value,
so I think 1000 is the lowest value.
Click to expand...
Click to collapse
Zero doesn't work, i try 0001, it works.
for RED color, the value is 10000,0001,0001.
Try again to see the values on your pre_hw_config.sh if it did not changed after reboot. Then all of your notifications will turn to RED.. By setting the lowest value to 1000, still the GB colors has still a good current value.
Flashable zip for Holo style Blue
Not made by me but jjdoctor...
had this zip tho
lokenok said:
Flashable zip for Holo style Blue
Not made by me but jjdoctor...
had this zip tho
Click to expand...
Click to collapse
I think this will make all of your notifications to LIGHT BLUE?.. Correct me if I'm wrong... Doing that also.. Better to put those values on pre_hw_config.sh..
adulfo said:
Try again to see the values on your pre_hw_config.sh if it did not changed after reboot. Then all of your notifications will turn to RED.. By setting the lowest value to 1000, still the GB colors has still a good current value.
Click to expand...
Click to collapse
so is there any value that change the LED to RED but not affect to other notification color???
luckkonku said:
so is there any value that change the LED to RED but not affect to other notification color???
Click to expand...
Click to collapse
Just don't put those values on hw_config.sh, only on pre_hw_config.sh I think....
hi guys this is my first comment so, i've changed these values in pre_hw_config.sh and of course i've got the color i want (nearly ICS blue). BUT here is my problem: other notifications like charging (instead of red it's nearly pink, instead of orange it's nearly green...) not working properly. I'm using light flow led and its notifications also miss the right color. Is there a solution for this? I'm not a developer but i think the phone calculates the values of notifications by this three values and must be an algorithm for this somewhere in the phone, so maybe we can manipulate that. Tell me if I'm wrong. Sorry for my english it's not my native language.
bobo023 said:
hi guys this is my first comment so, i've changed these values in pre_hw_config.sh and of course i've got the color i want (nearly ICS blue). BUT here is my problem: other notifications like charging (instead of red it's nearly pink, instead of orange it's nearly green...) not working properly. I'm using light flow led and its notifications also miss the right color. Is there a solution for this? I'm not a developer but i think the phone calculates the values of notifications by this three values and must be an algorithm for this somewhere in the phone, so maybe we can manipulate that. Tell me if I'm wrong. Sorry for my english it's not my native language.
Click to expand...
Click to collapse
Try to raise the values of the other color, I stated that on my OP last part that if you make the other values extremes (1000 and 20000), the the colors will be affected.. If for instance, Blue will have 20000 value, the notifications color that contains blue (violet...) will have dominant blue and other colors will be suppressed, so VIOLET will turn out to be more on BLUE.
DPI Settings for ASUS ZenFone 3 Ultra [Android 6.0/Marshmallow]
I have just bought my new ZF3U and as with my previous Huawei P8 Max, which was of the same screen size, I went ahead to find the optimum DPI scaling for enabling Tablet Mode and wanted to share my findings with you. As always, use the following ADB commands to achieve the desired change [Remove brackets and simply replace the below number with your desired DPI and use the second code if you want to revert to your default factory DPI.] Rest assured I have tried all the possible DPI settings and depending on your taste and desired experience, the following DPI choices are the only ones worth trying UNLESS you don't like the Tablet Mode, which in that case don't try practicing any of the settings below or if you want objects bigger then simply increase the DPI until you are happy with your DPI scaling to make objects larger. Enjoy!
adb shell wm density [241] && adb reboot
adb shell wm density reset && adb reboot
DPI 217: Full Tablet Mode- Dual SIM Settings Menu inside Phone Settings and Stock Camera Functionality Lost
DPI 241: Medium Tablet Mode- Stock Camera Manual Mode Functionality Lost and Loss of Tablet Functionality for some Applications such as eBay.
DPI 264: Medium Tablet Mode- As DPI 241 but also shows full name of contacts on the ASUS Contacts application whereas other modes will not show complete Contact Name in Portrait mode.
DPI 289: Limited Tablet Mode-High/Near Stock Scaling of Items/Menus which may defeat the whole point of rescaling the UI DPI.
NOTE: On all the four DPI modes listed above, the Tablet mode is enabled on the ASUS Contacts application with the side menu as well as the tablet mode enabling on the phone settings menu.
Hi there! Just a bit surprised, because I also just bough ZF3U to replace faulted P8 Max
Thanks for your observation... Honestly, I like that it have higher density by default and this time I decided to stay with default DPI for now...
Question: what's exactly meant under "Stock Camera Functionality Lost"?
Does that mean it stopped working or something different?
Yes, it means at the lowest dpi the stock camera will not work at all and at 264 you lose the manual settings inside the camera app so the camera app will have limited functionality. I am hoping to revise these dpi tests when Android 7 is eventually released which I very much hope will be soon.
DPI Settings for ASUS ZenFone 3 Ultra [Android 7.0/Nougat]
Hello everyone. Following the release of the latest Android 7.0 Firmware update [WW-14.1010.1703.42] for the ZF3Ultra which I have now installed on my 2nd ZF3U (1st one died following the initial faulty firmware which ASUS withdrew from release), I went ahead to find out once again (as I did with my previous Huawei P8 Max) the optimum DPI scaling for enabling Tablet Mode and wanted to share my findings with you. As always, use the following ADB commands to achieve the desired change [Remove brackets and simply replace the below number with your desired DPI and use the second code if you want to revert to your default factory DPI.] With Android 7.0 you can also scale the DPI using the Display option in setting but this will only change the dpi within the parameters that ASUS has specified and this will not enable full tablet mode. However, if you want to practice the dpi scaling on the go without any adb code then there is good news for Android 7.0 users. Under device settings-go to About-Software Information-tap on Build Number multiple times until the message pops up stating that your are now a developer, then go back to the main list of options and click on Developer options-then go all the way down on the list of developer options to heading Drawing-under that heading you will find Smallest width-click on it and change the number to 795 and this will give you the equivalent dpi of 217. OR if you want to try different DPIs then you can change the number accordingly. The higher the number, the smaller the UI objects will be, the lower the number, the bigger the UI objects will be.
Rest assured I have tried all the possible DPI settings and depending on your taste and desired experience, the following DPI scale of 217 is the only one worth trying UNLESS you don't like the Tablet Mode, in which case don't try practicing any of the settings below or if you want objects bigger then simply increase the DPI until you are happy with your DPI scaling to make objects larger.
adb shell wm density [217] && adb reboot
adb shell wm density reset && adb reboot
Observations:
DPI 217: (You can also find my findings on Android 6.0 DPI scaling for the ZF3U on my related post in the forum. In that post you will find details of my findings on additional dpi scales)
-The scale number of 217 will enable FULL Tablet mode on the ZF3U,
-All Tablet Mode compatible apps will be fully operational,
-Dual Sim Functionality will be fully operational (This did not work on Android 6.0 scaling),
-Google has removed the Tablet Mode side menu inside device options so no matter which dpi you use, the side menu is no longer there (It was available in Android 6.0) -I wish Google could bring back all the precious Tablet mode options previously available and even better would be to bring all the tablet UI features of the well respected Paranoid Android ROM (i.e bottom status bar, status bar pop-up options like Windows etc.... those of use who have been using it back in the days know what I am talking about),
-DISADVANTAGE: Stock Camera functionality is lost and the image does not display properly so if you love the dpi and can do without stock camera functionality then stick to this dpi and install a camera app of your choice (I am using Camera MX)-If anyone finds a fix to keep the stock camera operational at dpi scale of 217 without any issues then please do share your workaround.
Enjoy!
Thanks for this awesome tips! Im using Zenfone 3 ultra too and l been finding way to take full advantage of this screen size. This really helps a lot! ?
actually the dial pad, contacts and alarm dont work well with those settings. adjust to 540 or 579 smallest width.
I found a way to activate the automatic white balancing of google. (Like on the Pixel 4).
Based and thanks to the guide of droidwin: https://www.droidwin.com/how-to-remove-navigation-bar-gesture-pill-on-non-rooted-pixel-6-pro/
You need the fabricate overlay and Shizuku.
In the overlay app: Add overlay ->Android-System->Add->config_displayWhiteBalanceAvailable set to enabled ->apply / config_displayWhiteBalanceEnabledDefault set to enabled-> apply
Close and save it.
After it enable the overlay. Then it appers in settings->Display an d you can turn it on.
That's all.
Is Automatic White Balancing useful? Does it improve the display?
Droidwin based off XDA thread from Nov 6
Also I have it toggled and if doesn't change wb when forcing different colour hues
https://forum.xda-developers.com/t/...l-and-more-for-non-rooted-pixel-6-pro.4357937
I haven't done a test. Do you know how fast the wb change on the pixel 4? Maybe it's too slow on this device?
Can someone post a picture of what this looks like? Even if it's from the pixel 4 or something. Just would like to see it so I can decided if I should care enough to do this....