Related
Here are the init.d scripts that I have been using for Siyah. Please note that 95% of the scripts were done by Pikachu's thunderbolt scripts and I have modified then to my liking. Thanks to Pikachu for the hard work he has put in for the developement of our devices. For those that will use these scripts please use them with caution! I am not responsible for any damage done to your phone! You are free to use these as you wish, adjust them to your liking. The s70darkyzipalign, s98cfs, s98systemtweak should be universal for all setups and you do not need to adjust these init.d scripts. The one you need to be aware of is the s98bolt1 and screenstate_scaling script. The s98bolt1 script has cpu freq. steps set at max 1504 min 100. Scaling @ max 1304 min 200. The voltages for these steps are pretty aggressive and may not work for your device so please PLEASE adjust them accordingly. This script will also set ondemand/sio as default. You can replace those as you wish. GPU is set for 40, 133, 267mhz. (Andreilux's settings, Thanks Andrei) Sched_mc and AFTR have been enabled for some extra power saving.
Screenstate_scaling have been modified to set as Ondemand as wake governer and Powersave as sleep governer. You can adjust these as well. The scripts are pretty self explantory and you can adjust these values using root explorer and using the menu in root explorer to "open in text editor". Or you can you wordpad or notepad++ on your pc and adjust them. Save the scripts to your phone. Using root explorer copy the init.d scripts to /etc/init.d. Paste in this directory and set permissions as rwx,rwx,rwx and reboot.
I am sure I missed some things as I'm kind of in a hurry. Please pm me if you have any questions or need help. I have used this setup for quite some time now without any problems. Battery life has been amazing without sacrificing performance. Oh please do not use VC to save boot settings as these will clash. Everything in the init.d scripts will do the same as VC as long as you adjust them accordingly. Good luck and happy flashing/modding!
P.S. After downloading the file remove the .txt extension in the files before using. Thanks!
Here is the link to the Originator and Creator of these awesome scripts. Thanks Pikachu!
http://forum.xda-developers.com/showthread.php?p=18285859
PHP:
I just want to make sure before I utilize these. I need to use a file manager to place these in /etc/unit.d folder without the .txt correct?
Should I remove the existing scripts as well?
Edit: do these scripts completely take the place of voltage control and setcpu? I wanted to get all of my questions out of the way
These seem awesome. Can't wait to try them out
moustro said:
I just want to make sure before I utilize these. I need to use a file manager to place these in /etc/unit.d folder without the .txt correct?
Should I remove the existing scripts as well?
Edit: do these scripts completely take the place of voltage control and setcpu? I wanted to get all of my questions out of the way
Click to expand...
Click to collapse
Everything you posted is correct. Please keep in mind the voltage settings are a little extreme. If you think or know your phone can handle the UV then just drop them in without modifying. But if you're not sure add +25 mv to each step.
I almost gaurantee your phone will sleep like a baby. And fly like the wind when in use.
Thanks for the scripts!
I've also found an interesting script at 9100 Siyah Kernel topic ( http://forum.xda-developers.com/showthread.php?t=1263838&page=1813 )
I got sleep of death by using below script so you may want to check voltages setting before using it.
Code:
#!/system/bin/sh
# ******************
# 1°) I/O Schedulers
# ******************
# Set i/o scheduler (Valid values are: noop, deadline, cfq, bfq, sio, vr, anticipatory)
echo bfq > /sys/block/mmcblk0/queue/scheduler;
# ************************************************
# 2°) Scaling Governor & Smooth Scaling Parameters
# ************************************************
# Set scaling governor, according to available governors in your kernel
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor;
# Smooth scaling parameters to control any governor jumping to higher frequency directly.
echo 2 > /sys/devices/system/cpu/cpu0/cpufreq/smooth_target;
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/smooth_offset;
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/smooth_step;
# ****************************************************************
# 3°) Deepsleep Levels
# cpulevel = 4 (100Mhz - 800Mhz, default), 5 (100Mhz - 500Mhz)
# buslevel = 0 (400MHz, default), 1 (266MHz), 2 (133MHz)
# ****************************************************************
# Set deep sleep frequency & bus speed:
echo 5 > /sys/devices/system/cpu/cpu0/cpufreq/deepsleep_cpulevel;
echo 2 > /sys/devices/system/cpu/cpu0/cpufreq/deepsleep_buslevel;
# ****************************
# 4°) CPU Frequency & Voltages
# ****************************
# Set frequency steps according to the number of steps in your kernel.
echo "1600 1400 1200 1000 800 500 200 100" > /sys/devices/system/cpu/cpu0/cpufreq/freq_table;
# Set voltages for frequency steps. Changes possible at +/-25mV steps
echo "1350 1275 1150 1050 950 900 850 800" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table;
# Sets global scaling min&max frequencies as 100 and 1000 mhz
echo 100000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq;
echo 1200000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;
# ************************************
# 5°) GPU Clock, Voltages & Thresholds
# ************************************
# Set GPU clocks (Valid values are: 100 114 133 160 200 267 300 400 )
echo "40 133 267" > /sys/class/misc/gpu_clock_control/gpu_control;
# Set GPU Up and Down thresholds
echo "90% 25% 90% 45%" > /sys/class/misc/gpu_clock_control/gpu_control;
# Set GPU voltages (Changes possible at +/-50mV ie at 50000 steps)
echo "850000 900000 950000" > /sys/class/misc/gpu_voltage_control/gpu_control;
# ======================================================
# 6°) Hot Plug Thresholds, Sampling Interval & Frequency
# ======================================================
# Set second core kick-in threshold for screen-on state
echo 35 > /sys/module/pm_hotplug/parameters/loadl;
echo 80 > /sys/module/pm_hotplug/parameters/loadh;
# Set second core kick-in threshold for screen-off state
echo 90 > /sys/module/pm_hotplug/parameters/loadl_scroff;
echo 100 > /sys/module/pm_hotplug/parameters/loadh_scroff;
# Set hot plug sampling intervals for screen-on state
echo 400 > /sys/module/pm_hotplug/parameters/rate;
echo 400 > /sys/module/pm_hotplug/parameters/rate_cpuon;
# Set hot plug sampling intervals for screen-off state
echo 1000 > /sys/module/pm_hotplug/parameters/rate_scroff;
# Set frequency below which second core will not be turned on, regardless of thresholds.
echo 524288 > /sys/module/pm_hotplug/parameters/freq_cpu1on;
# ===================
# 7°) Bus Frequencies
# ===================
# Set bus frequencies for highest-to-lowest cpu frequencies and enable static bus frequency scaling
#echo "0 0 0 1 1 2 2 2" > /sys/devices/system/cpu/cpu0/cpufreq/busfreq_static;
#echo enabled > /sys/devices/system/cpu/cpu0/cpufreq/busfreq_static;
# ====================================
# 8°) Schedule Multi Core & Idle Modes
# ====================================
# Enable sched_mc
echo 1 > /sys/devices/system/cpu/sched_mc_power_savings;
# Enable AFTR
echo 3 > /sys/module/cpuidle/parameters/enable_mask;
# =============================
# 9°) Brightness Curve Settings
# =============================
# Brightness settings (Possible values for min_bl = 0 to 255 | min_gamma = 0 to 24 | max_gamma = 0 to 24)
echo 20 > /sys/class/misc/brightness_curve/min_bl;
echo 1 > /sys/class/misc/brightness_curve/min_gamma;
echo 24 > /sys/class/misc/brightness_curve/max_gamma;
# =================================
# 10°) Touch Sensitivity Parameters
# =================================
# Set touch sensitivity (Possible values are between 40 to 80. Lower value = higher sensitivity)
echo 40 > /sys/devices/virtual/sec/sec_touchscreen/tsp_threshold;
# ===================
# 11°) Charge Current
# ===================
# Set AC, Misc & USB charge current (Do not set Ac & Misc more than 1000mA or Usb more than 450)
echo "950 950 450" > /sys/devices/virtual/misc/charge_current/charge_current;
# =======================================
# 12°) Switch Hotplug/DualCore/SingleCore
# =======================================
# Set Dynamic hotplug mode
echo on > /sys/devices/virtual/misc/second_core/hotplug_on;
echo on > /sys/devices/virtual/misc/second_core/second_core_on;
# ===================
# 13°) Disable logger
# ===================
if [ ! -d /data/.siyah ];
then
mkdir /data/.siyah;
chmod 777 /data/.siyah;
fi;
touch /data/.siyah/disable-logger;
# ====================
# 14°) Graphic tunings
# ====================
setprop debug.sf.hw 1; # HARDWARE RENDERING (GPU)
setprop video.accelerate.hw 1;
setprop debug.performance.tuning 1;
# Set deep sleep frequency & bus speed:
echo 5 > /sys/devices/system/cpu/cpu0/cpufreq/deepsleep_cpulevel;
echo 2 > /sys/devices/system/cpu/cpu0/cpufreq/deepsleep_buslevel;
See the echo 5, change that to 4. And your SOD's will be gone!!
Steve you are the man! Thank you for bundling these scripts all in one place. Everything is smooth and my phone is sleeping like a baby so far.
moustro said:
Steve you are the man! Thank you for bundling these scripts all in one place. Everything is smooth and my phone is sleeping like a baby so far.
Click to expand...
Click to collapse
What ROM are you using?
Can these scripts be used on Unnamed?
Unit.d generator in the i9100 forum works great for this.
Must script manager be used to give these scripts root access to work?
Sent from my i777.
desiromeo719 said:
What ROM are you using?
Can these scripts be used on Unnamed?
Click to expand...
Click to collapse
Miui 2.1.13
I believe these scripts are universal and can run on siyah or entropy dd. Can someone else confirm this?
Sorry guys for the late reply. Busy at work. Yes these scripts are universal for any ROM. Just make sure your kernel supports init.d. Siyah and Entropy both support them.
moustro said:
Miui 2.1.13
I believe these scripts are universal and can run on siyah or entropy dd. Can someone else confirm this?
Click to expand...
Click to collapse
No, some of them depend on tunables in Siyah I haven't ported over yet.
Personally, I would not recommend putting voltage settings in a script that you distribute to the public, as voltages are device-unique.
I'm also a firm believer in a number of small separate scripts with descriptive names, instead of a "megascript" that does it all - harder to analyze and harder to pick and choose.
I'll take a look at the specific script contents when I have some time.
thx for clarifying entropy. i did state specifically about the voltages and they have been modified to my likings. so for now use for siyah kernel. and once again pls adjust the voltages to values that your phone can handle. some phones can only take a -25 mv from stock voltages. s98bolt1 and screenstate should be used as a base only. adjust them to your liking. the other scripts are system tweaks and are universal for most roms.
Sent from my SGH-I777 using xda premium
Thanks for this post Steve. Im sure once I get a handle on these tweaks and applying them I will greatly benefit from them!
No problem. Trying to help out anyway I can. I know all these scripts can be confusing and a headache. I noticed a lot of people asking how to make scripts and OC and UV settings so why not make them avail for the general public. It's just a good base to start off with for siyah users. If anyone has or needs any help in reading the scripts and how to adjust them let me know.
I could ask ya a million questions..but I wont lol. Just trying to do lots of reading here..and on Google to learn about scripts..init.d..OC and UV. Sometimes I think I got it...but then i get all confused. The only script I have now is the V6. That one just seemed like I could handle since it basically walks ya through the entire process. And to be honest..not even sure i notice a difference.
jasvncnt1 said:
I could ask ya a million questions..but I wont lol. Just trying to do lots of reading here..and on Google to learn about scripts..init.d..OC and UV. Sometimes I think I got it...but then i get all confused. The only script I have now is the V6. That one just seemed like I could handle since it basically walks ya through the entire process. And to be honest..not even sure i notice a difference.
Click to expand...
Click to collapse
Trust me, it made a difference. It's nothing flashy, and nothing some people would notice, but it did.
Nice post stevehkim, I may give these are try.
Sent from my SGH-I777 using xda premium
If I may..s70darkyzipalign, s98cfs, s98systemtweak...Are theses kinda like OC and UV or just minor system tweaks? I tried opening them and taking a look...but have no idea what im looking at. I admit, I am not the smartest person thats for sure
They, from their titles, are system tweaks. I haven't looked through them, so I can't tell for sure.
Edit: Steve, you might want to post a brief description of what each script does, which can be run independently, which need to be run together, and most importantly how to implement them.
Just a suggestion to cut back on confusion and potential fights
Sent from my SGH-I777 using xda premium
Hey guys,
To those who are still yet unlocked but rooted, I thought I share my experience after tweaking and fine tuning my ATP. I have tested these settings for the last 3 weeks and it appears to be stable and fast. Most of these tweakings are based on various mods/suggestions found on this forum but I have changed some values/settings and picked and mixed others during the fine tuning process.
Tweak 1:
The sio.sh scheduler.
Possibly the best scheduler for my experience. Less lags and less apps complaining of anr's. Our ATPs run noop by default.
To do it (using automated script to be run as startup; e.g. using SManager)
insmod /system/lib/modules/sio-iosched.ko
echo sio > /sys/block/mmcblk0/queue/scheduler
The tweaked script is attached (which combined Tweak 1 and Tweak 2)
Thank you to batoo for compiling this (I think this is by far a big lifesaver) – and to the original developer which I believe the name is Miguel Bolton.
Tweak 2:
Various VM values
The suggested workaround were these (the tune.sh)
swappiness = 0
dirty background ratio =50
dirty ratio = 70
dirty expire centisecs = 20000
dirty writeback centisecs = 20000
However I have changed mine to (with my added comments after //)
swappiness = 0
dirty background ratio =5
dirty ratio = 5
//don't want to be waiting until there are lot of processes' dirty caches before pdflush is done. So we handle this in a more graceful way by chewing a little at at time considering we already have slow io
dirty expire centisecs = 1000
//let's write dirty page to the disk and not wait too long if the ratio above has not been achieved
dirty writeback centisecs = 1000
This is reflected in the script as below:
VM values changed
echo 0 > /proc/sys/vm/swappiness
echo 5 > /proc/sys/vm/dirty_background_ratio
echo 5 > /proc/sys/vm/dirty_ratio
echo 1000 > /proc/sys/vm/dirty_expire_centisecs
echo 1000 > /proc/sys/vm/dirty_writeback_centisecs
The tweaked script is attached.
Thank you to batoo for first sharing tweaks.
Tweak 3:
Changing the default values we run Powersave – Balanced – Performance. What I think is, because core throttling is a clever thing, pushing up current Powersave to 1.2, Balanced to 1.4 and Performace to 1.6 shouldn't affect battery life that much. I am running Balanced on battery and I seemed not to lose that much battery life < 1.30hour loss and most of the time much less.
To do this, I modified the scripts in /system/etc so the appropriate one is “invoked” when the respective mode is chosen (changed scripts uploaded).
Tweak 4:
build.prop.
I have only cherry picked and commented out other settings which I think wouldn't confer any additional benefits. My modified build.prop (for ww sku) that is, is attached.
Thank you to seanzscreams for first sharing this tweaks.
It would be good to have some input from experts/devs in here on what they think especially the vm tweaks above.
Disclaimer:
I am not an android expert or a developer. It works well for me. Whilst I don't think how any of these scripts can brick your Prime, the advice is of course, do it at your own risk.
maxfac1234 said:
Hey guys,
To those who are still yet unlocked but rooted, I thought I share my experience after tweaking and fine tuning my ATP. I have tested these settings for the last 3 weeks and it appears to be stable and fast. Most of these tweakings are based on various mods/suggestions found on this forum but I have changed some values/settings and picked and mixed others during the fine tuning process.
Tweak 1:
The sio.sh scheduler.
Possibly the best scheduler for my experience. Less lags and less apps complaining of anr's. Our ATPs run noop by default.
To do it (using automated script to be run as startup; e.g. using SManager)
insmod /system/lib/modules/sio-iosched.ko
echo sio > /sys/block/mmcblk0/queue/scheduler
The tweaked script is attached (which combined Tweak 1 and Tweak 2)
Thank you to batoo for compiling this (I think this is by far a big lifesaver) – and to the original developer which I believe the name is Miguel Bolton.
Tweak 2:
Various VM values
The suggested workaround were these (the tune.sh)
swappiness = 0
dirty background ratio =50
dirty ratio = 70
dirty expire centisecs = 20000
dirty writeback centisecs = 20000
However I have changed mine to (with my added comments after //)
swappiness = 0
dirty background ratio =5
dirty ratio = 5
//don't want to be waiting until there are lot of processes' dirty caches before pdflush is done. So we handle this in a more graceful way by chewing a little at at time considering we already have slow io
dirty expire centisecs = 1000
//let's write dirty page to the disk and not wait too long if the ratio above has not been achieved
dirty writeback centisecs = 1000
This is reflected in the script as below:
VM values changed
echo 0 > /proc/sys/vm/swappiness
echo 5 > /proc/sys/vm/dirty_background_ratio
echo 5 > /proc/sys/vm/dirty_ratio
echo 1000 > /proc/sys/vm/dirty_expire_centisecs
echo 1000 > /proc/sys/vm/dirty_writeback_centisecs
The tweaked script is attached.
Thank you to batoo for first sharing tweaks.
Tweak 3:
Changing the default values we run Powersave – Balanced – Performance. What I think is, because core throttling is a clever thing, pushing up current Powersave to 1.2, Balanced to 1.4 and Performace to 1.6 shouldn't affect battery life that much. I am running Balanced on battery and I seemed not to lose that much battery life < 1.30hour loss and most of the time much less.
To do this, I modified the scripts in /system/etc so the appropriate one is “invoked” when the respective mode is chosen (changed scripts uploaded).
Tweak 4:
build.prop.
I have only cherry picked and commented out other settings which I think wouldn't confer any additional benefits. My modified build.prop (for ww sku) that is, is attached.
Thank you to seanzscreams for first sharing this tweaks.
It would be good to have some input from experts/devs in here on what they think especially the vm tweaks above.
Disclaimer:
I am not an android expert or a developer. It works well for me. Whilst I don't think how any of these scripts can brick your Prime, the advice is of course, do it at your own risk.
Click to expand...
Click to collapse
Nothing against, but my recommendation is try to read something about dirty ratio function.
Btw my opinion for this is that advance user will change these values without advice and beginner or non linux skilled user will not modify ATP sources...
BTW guys ALL of you who has not unlocked device (like me) I really DON'T recommend you to modify build.prop at all.
This post is not offensive or personal, only my opinion.
Sent from my Transformer Prime TF201 using Tapatalk 2
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.
Here I am presenting the five different brightness mod to adjust brightness of capacitive button's backlight. Requirements, Procedure and mods are given below.
Requirement-
1 Root explorer or any similar explorer
2 Sharp mind
Procedure-
1 Open the root explorer and go to system/etc. Here you will find a script named as" hw_config.sh ".
2 Open the script or file as the text in text editor with the help of root exploprer.
3 Now scroll down to the last line and after that line add one of the required brightness mod line which one you like into it as given below. (Don't add all lines of different mods. )
4 Now reboot and done.
Five Different brightness mods-
1 Very High Brightness mod-
echo 10000 > $dev/button-backlight/max_current
Click to expand...
Click to collapse
2 High Brightness mod-
echo 7000 > $dev/button-backlight/max_current
Click to expand...
Click to collapse
3 Medium Brightness mod-
echo 4000 > $dev/button-backlight/max_current
Click to expand...
Click to collapse
4 Low Brightness mod-
echo 1000 > $dev/button-backlight/max_current
Click to expand...
Click to collapse
5 Zero Brightness mod-
echo 1 > $dev/button-backlight/max_current
Click to expand...
Click to collapse
Important note:- If any line similar to these lines already exists in script or file then first delete that line or replace it with one of mods.
Recomended and tested successfully with stock kernel, can't say about custom kernels.
Press thanks if you thinks this post is useful to you.
Great
Is this applicable to ray
Sent from my ST18i using xda app-developers app
dheeraj.nijghal said:
Is this applicable to ray
Sent from my ST18i using xda app-developers app
Click to expand...
Click to collapse
Yes, for sure.
i'm using cm10 on my sk17. and in there is a line in the file "echo 500 > $dev/button-backlight/max_current" by default. and the brightness is very high. Tried various times and found that the minimum value that can be given is 150 on cm10. If you want more light, just increase in small steps...
shivamcheat said:
i'm using cm10 on my sk17. and in there is a line in the file "echo 500 > $dev/button-backlight/max_current" by default. and the brightness is very high. Tried various times and found that the minimum value that can be given is 150 on cm10. If you want more light, just increase in small steps...
Click to expand...
Click to collapse
ok thanks.
why this is not f**king working for me ...?!?
ok, had this problem and dont know wheres here the problem
1. i hate bbl (=buttonbacklight) so i disable it with Mini-Ultrabrightness mod and all was fine!
but after changing kernel to kappa kernel (1.6) the bbl was very bright AND NO way to disable it...?!?
---> edited hw_config file like here = no changes
---> flashed Mini-Ultrabrightness second time = no changes
---> make a script with value echo 1 > $dev/button-backlight/max_current / and also tested values for 1 button etc.. = no changes
before it was no problem changing the bbl, but after usig kappa kernel the bright backlight persist, even after flash diffrent kernels
..... MY QUESTION IS: anbody knows whats happenning there?? or haw to diable bbl with a diffrent (safe ) method??
it would be really nice.
thanks. and SFBE (=sorry for bad english)
bejunk said:
ok, had this problem and dont know wheres here the problem
1. i hate bbl (=buttonbacklight) so i disable it with Mini-Ultrabrightness mod and all was fine!
but after changing kernel to kappa kernel (1.6) the bbl was very bright AND NO way to disable it...?!?
---> edited hw_config file like here = no changes
---> flashed Mini-Ultrabrightness second time = no changes
---> make a script with value echo 1 > $dev/button-backlight/max_current / and also tested values for 1 button etc.. = no changes
before it was no problem changing the bbl, but after usig kappa kernel the bright backlight persist, even after flash diffrent kernels
..... MY QUESTION IS: anbody knows whats happenning there?? or haw to diable bbl with a diffrent (safe ) method??
it would be really nice.
thanks. and SFBE (=sorry for bad english)
Click to expand...
Click to collapse
u need to create or edit pre_hw_config.sh
Nice tutorial...
Will try when I get time...
Sent from my Sony Ericsson Xperia Mini Pro(SK17i) using Tapatalk 2
hey guys
wont this only apply to back button????
Not working in mine Xperia mini pro with kappa kernel 1.6
Please help me...
Sent from my Sony Ericsson Xperia Mini Pro(SK17i) using Tapatalk 2
rockstardeepaksharma said:
Not working in mine Xperia mini pro with kappa kernel 1.6
Please help me...
Sent from my Sony Ericsson Xperia Mini Pro(SK17i) using Tapatalk 2
Click to expand...
Click to collapse
Strange because kappa 1.6 is the only custom kernel with which I have tested all these mod and they all work fine with this kernel[kappa 1.6 for simultron].
Mankotialovely said:
Strange because kappa 1.6 is the only custom kernel with which I have tested all these mod and they all work fine with this kernel[kappa 1.6 for simultron].
Click to expand...
Click to collapse
i was using zero brightness trick but it doesnt helped me :'(
rockstardeepaksharma said:
i was using zero brightness trick but it doesnt helped me :'(
Click to expand...
Click to collapse
Under LMU AS3676 Configuration add these lines-
echo 1 > $dev/button-backlight/max_current
echo 0 > $dev/button-backlight/max_brightness
echo 1 > $dev/button-backlight-rgb1/max_current
echo 1 > $dev/button-backlight-rgb2/max_current
Now reboot 2-3 times and between every reboot provide some time also delete any previous lines which are similar to these or simply replace there value with these one.
Interesting thread...
Is there any way guys for the capacitive buttons to have backlight ONLY when we press them, not only every time the screen is on?
Alternative: can we change their backlight timeout?
thx
Mankotialovely said:
Here I am presenting the five different brightness mod to adjust brightness of capacitive button's backlight. Requirements, Procedure and mods are given below.
Requirement-
1 Root explorer or any similar explorer
2 Sharp mind
Procedure-
1 Open the root explorer and go to system/etc. Here you will find a script named as" hw_config.sh ".
2 Open the script or file as the text in text editor with the help of root exploprer.
3 Now scroll down to the last line and after that line add one of the required brightness mod line which one you like into it as given below. (Don't add all lines of different mods. )
4 Now reboot and done.
Five Different brightness mods-
1 Very High Brightness mod-
2 High Brightness mod-
3 Medium Brightness mod-
4 Low Brightness mod-
5 Zero Brightness mod-
Important note:- If any line similar to these lines already exists in script or file then first delete that line or replace it with one of mods.
Recomended and tested successfully with stock kernel, can't say about custom kernels.
Press thanks if you thinks this post is useful to you.
Click to expand...
Click to collapse
i have been facing a problem,i have installed "OpenSEMC-mr2-alpha2"
when i control my brightness the illumination bar light remain full
but in stock ROM when i reduce my brightness the intensity of that illumination bar light also decreases .
it is very annoying if you are doing something in night with low brightness and the illumination bar light is full.
please help
how tot enable ultrabrightest ?
Can anyone tell me how to get the Vivid Display (the Vivid Settings from Agni Kernal ) on any Kernel using Darkness Control/ Kernel Auditor..etc. What Setting should I set to get so.
There you go bud.
RGB palette - 35
Saturation - 45
Screen value - 129
Screen contrast - 137
This is not agnis vivid mode, but I like this settings