You want your capacitive buttons more dim, but don't want to go through the trouble of flashing a kernel? Fear not! Team Xposed has you covered.
It's a very simple process actually. (Thank you to joe85 and mwalt2 for their sources!)
There are three ways to achieve this.
-One of them requires init.d (the script will change the value upon boot)
-Second of them can be inserted into the kernel ramdisk
-Third of them can be done manually.
Let's start with the easiest, which is manually. With your phone connected to ADB, OR in a terminal emulator, simply type this in:
echo 2 > /sys/devices/platform/leds-pm8058/leds/button-backlight/currents
After tinkering for a bit, I've found that 2 is the dimmest it'll go. 1 turns them off, or makes them so dim that I can't tell between them being turned off or not. I don't know what the largest value is that you can use either, but this is for dimming, so who cares how bright you can do?
I've taken the steps to insert it into my kernel ramdisk, and you can too. Just insert that line in bootcomplete.rc or where ever you feel comfortable in ramdisk.
Now, for those who want to use it as an init.d script, I've attached a flashable zip at the bottom, or you can do it yourself by using root explorer to edit any current scripts in your /system/etc/init.d folder and placing the same line in there.
I'd tinker with values in ADB first to find a value that fits you best. The flashable zip I'm attaching has the value set at 2.
NOTE: Make sure your kernel supports init.d if you choose to flash the zip. (Most of them do, it's just a disclaimer to cover my ass for the "it doesn't work" replies)
This was exactly what I was looking for, thanks for all the awesome tutorials Freeza!
Thanks man! Worked perfect.
Sent from my PG86100 using Tapatalk
Is there anyway, using the first method, to have it persist through reboots?
faugnom1 said:
Is there anyway, using the first method, to have it persist through reboots?
Click to expand...
Click to collapse
If the rom supports init.d, it will persist past reboots. It gets loaded each time the phone boots.
the flashable zip worked great thank u!!! i did try adb and i wouldnt work is there something im missing?i am normally pretty good with adb
This would be great to bake into a rom. Thanks for this script
I actually did the opposite. Since a few kernels or ROMS have the led dimmed already. I use this and change the value to 20 to keep it bright. Haha
I modded my leds green. So that makes them dimmer already.
Anyways, thanks for this!
freeza said:
You want your capacitive buttons more dim, but don't want to go through the trouble of flashing a kernel? Fear not! Team Xposed has you covered.
It's a very simple process actually. (Thank you to joe85 and mwalt2 for their sources!)
There are three ways to achieve this.
-One of them requires init.d (the script will change the value upon boot)
-Second of them can be inserted into the kernel ramdisk
-Third of them can be done manually.
Let's start with the easiest, which is manually. With your phone connected to ADB, OR in a terminal emulator, simply type this in:
echo 2 > /sys/devices/platform/leds-pm8058/leds/button-backlight/currents
After tinkering for a bit, I've found that 2 is the dimmest it'll go. 1 turns them off, or makes them so dim that I can't tell between them being turned off or not. I don't know what the largest value is that you can use either, but this is for dimming, so who cares how bright you can do?
I've taken the steps to insert it into my kernel ramdisk, and you can too. Just insert that line in bootcomplete.rc or where ever you feel comfortable in ramdisk.
Now, for those who want to use it as an init.d script, I've attached a flashable zip at the bottom, or you can do it yourself by using root explorer to edit any current scripts in your /system/etc/init.d folder and placing the same line in there.
I'd tinker with values in ADB first to find a value that fits you best. The flashable zip I'm attaching has the value set at 2.
NOTE: Make sure your kernel supports init.d if you choose to flash the zip. (Most of them do, it's just a disclaimer to cover my ass for the "it doesn't work" replies)
Click to expand...
Click to collapse
Freeza your mod has caused my phone to lag tremendously and battery life has suffered a lot since using this rom. Please fix!
Lulz
It Works like a charm
Thanks !
It works like a charm.
At first, i've tested with adb to find the correct value for my needs.
And now with starting script my default value is now set to 6.
Sheers
cobraboy85 said:
Freeza your mod has caused my phone to lag tremendously and battery life has suffered a lot since using this rom. Please fix!
Lulz
Click to expand...
Click to collapse
That's just plain erroneous. Period. SteelROM has been running with the lights set at 2 for weeks, and battery life is fantastic. Simple logic will tell you less amps to a light results in less battery drain. So, if anything, dimming those LEDs will INCREASE your battery life!
freeza said:
echo 2 > /sys/devices/platform/leds-pm8058/leds/button-backlight/currents
After tinkering for a bit, I've found that 2 is the dimmest it'll go. 1 turns them off, or makes them so dim that I can't tell between them being turned off or not. I don't know what the largest value is that you can use either, but this is for dimming, so who cares how bright you can do?
Click to expand...
Click to collapse
0 = off, 2 = dim. Same results I found a while back. However, 20 is the highest you could/should go. (it actually does matter!) This setting is for mA (AKA milliamps for those less electrically knowledgable). SO setting to over 20 could result in excess current going to the LEDs meaning unecessary heat and shortened battery life.
SteelH said:
That's just plain erroneous. Period. SteelROM has been running with the lights set at 2 for weeks, and battery life is fantastic. Simple logic will tell you less amps to a light results in less battery drain. So, if anything, dimming those LEDs will INCREASE your battery life!
Click to expand...
Click to collapse
you didn't think i was being serious did you....
hahaha
cobraboy85 said:
you didn't think i was being serious did you....
hahaha
Click to expand...
Click to collapse
I noticed after the lulz part haha
cobraboy85 said:
Freeza your mod has caused my phone to lag tremendously and battery life has suffered a lot since using this rom. Please fix!
Lulz
Click to expand...
Click to collapse
wipe data/system/boot/wimax/sd/sd-ext/a window or two
Then flash a kernel from the EVO 4G section. You'll be as good as new!
freeza said:
wipe data/system/boot/wimax/sd/sd-ext/a window or two
Then flash a kernel from the EVO 4G section. You'll be as good as new!
Click to expand...
Click to collapse
Bro... I was kidding lol. The sarcasm was because people always do that right after flashing a rom..... because they are retarded
cobraboy85 said:
Bro... I was kidding lol. The sarcasm was because people always do that right after flashing a rom..... because they are retarded
Click to expand...
Click to collapse
I know, as was I
Are these values supposed to stick after a reboot if done manually? I was just wondering because I tried the manual way and reset my phone and the leds went back to the normal brightness.
jstn76rs said:
Are these values supposed to stick after a reboot if done manually? I was just wondering because I tried the manual way and reset my phone and the leds went back to the normal brightness.
Click to expand...
Click to collapse
They stick if you add a script to init.d or init.post_boot.sh or kernel ramdisk
freeza said:
They stick if you add a script to init.d or init.post_boot.sh or kernel ramdisk
Click to expand...
Click to collapse
thanks for the response. I have one little request would you be able to make a flashable zip for me with it set to 4.
Related
Idea for App:
Basically what I am looking for the app to do is incrementally raise the min and max settings for the CPU, change CPU governor to performance, and run stress test for 30 seconds to 1 minute. It would then repeat until all speeds are verified as good or the phone freezes or reboots. If either occurs then the app would tell the user the last speed that was stable. See here for what I posted in the Vipermod thread for more info of what I am talking about.
Is this possible? Has it already been made and I just can't find it?
qwerty017 said:
Idea for App:
Basically what I am looking for the app to do is incrementally raise the min and max settings for the CPU, change CPU governor to performance, and run stress test for 30 seconds to 1 minute. It would then repeat until all speeds are verified as good or the phone freezes or reboots. If either occurs then the app would tell the user the last speed that was stable. See here for what I posted in the Vipermod thread for more info of what I am talking about.
Is this possible? Has it already been made and I just can't find it?
Click to expand...
Click to collapse
stop being a cheapo and buy SetCPU... it has all that plus more. >.>
onl difference is you gotta step up... just do a native test per step... just because your phone can hit the frequency and survive doesnt mean that the CPU can have a load off with that step and then poof... . but yea... buy SetCPU, no more thread response.
Ok...?
Tilde88 said:
stop being a cheapo and buy SetCPU... it has all that plus more. >.>
onl difference is you gotta step up... just do a native test per step... just because your phone can hit the frequency and survive doesnt mean that the CPU can have a load off with that step and then poof... . but yea... buy SetCPU, no more thread response.
Click to expand...
Click to collapse
Ok. Not helpful at all but thanks, I guess. Already own SetCPU. Looking for something that will do it automatically like I initially said.
qwerty017 said:
Ok. Not helpful at all but thanks, I guess. Already own SetCPU. Looking for something that will do it automatically like I initially said.
Click to expand...
Click to collapse
really? you cant tell if your phone can run on a certain frequency by moving a slider while on performance governor? Good luck with finding any help.
Sigh...
Tilde88 said:
really? you cant tell if your phone can run on a certain frequency by moving a slider while on performance governor? Good luck with finding any help.
Click to expand...
Click to collapse
I was hoping you would at least do what you said and not reply to this thread anymore since you offer nothing. But since you can't I will explain. If you still don't understand then please follow your own advice.
I am requesting an app. Whether I can or cannot do the same thing with SetCPU is irrelevant. Not just me but a bunch of people are using the flashable overclock daemon for whatever the reason may be. I know I can manually change the settings to find out. I do not want to and I expect it is the same for others. Just as I use Battery Calibrator to remove the batterystats.bin file because it is easier to push a button and have it do the work, I want a program that will do what I am asking by just pushing a button rather than having to go through the terminal or install SetCPU.
qwerty017 said:
I was hoping you would at least do what you said and not reply to this thread anymore since you offer nothing. But since you can't I will explain. If you still don't understand then please follow your own advice.
I am requesting an app. Whether I can or cannot do the same thing with SetCPU is irrelevant. Not just me but a bunch of people are using the flashable overclock daemon for whatever the reason may be. I know I can manually change the settings to find out. I do not want to and I expect it is the same for others. Just as I use Battery Calibrator to remove the batterystats.bin file because it is easier to push a button and have it do the work, I want a program that will do what I am asking by just pushing a button rather than having to go through the terminal or install SetCPU.
Click to expand...
Click to collapse
yea i know what you mean... sorry, i really was being a bit of an ass now that i reread it. what you want is something to go to next step, benchmark, go to next step benchmark, and continue to do so until the phone cant handle it.
the problem is, [now this im not 100% but its an assumption], that the daemon is specifying a max value. So I can come up with two scenarios.
1.Though it isn't INSMOD (like the LoadableKernelModule) , it is defaulted on boot through init.d script. The only way to reload those scripts, would be to reboot. Perhaps a hot boot may work. So you would need the app to rewrite wake_max_freq, then reboot... then somehow test it (just a cpu load test app). the script would then need to change the default value to a higher one from a list [the one it just stepped up to], and then tell it if AndroidBoot=Fail to revert to last step (which it probably wont be able to do since the phone would lock on boot since you can default a frequency that is too high). Seems like alot of time to me...
2.I took too long to type this and forgot #2
i know it will eventually be done through a real OC'ing script ... but seriously... whats so bad about testing your device?i can test every step (starting at 192) in less than two minutes. Idk i may just be being a hardass since I find that a user should always test his labors. a computer can only say or show so much, your eyes and intuition cannot be processed.
Ok. Didn't realize it requires a reboot. From what it looked like to me it just read the 6 text files and ran it in real time. If it does require a reboot then I can see the problem you are talking about with having it boot loop every time it starts up after the bad setting is ran. Going to have to look some more into how the init.d is set up. Looks like I may just need to learn some shell scripting.
Sent from my PG86100 using Tapatalk
qwerty017 said:
Ok. Didn't realize it requires a reboot. From what it looked like to me it just read the 6 text files and ran it in real time. If it does require a reboot then I can see the problem you are talking about with having it boot loop every time it starts up after the bad setting is ran. Going to have to look some more into how the init.d is set up. Looks like I may just need to learn some shell scripting.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
im just assuming not 100% so dont get your hopes down
28 August 2011
Alright I tried this out already. You just have to follow the instructions, and also don't use other memory apps like auto killer memory optinizer, or task killers like advanced task killer. It really makes your phone run more smoothly.
Simple instructions are in post #18 by molohov.
molohov said:
I just ran the script with Aggressive 2 settings (6, 8, 25, 30, 35, 35)
Very easy to apply and run. It's a little difficult to weave through Zepp's writing, but essentially it boils down to this:
1. Download V6_Supercharger_for_Android-update8.sh.txt (at the bottom of the first post) to the sdcard
2. Download Script Manager Market Link
3. Open Script Manager and open the .txt file you just downloaded. Make sure Run as Root is selected.
4. Pick one of the many presets!
5. Reboot
Have yet to do some more testing with the current preset, but I'm sure it'll be good
Click to expand...
Click to collapse
You need busybox 1.18.2 or lower for this script to work properly. Below is the Market link to busy box installer. Thank LibertyMonger for suggesting to me to add this into the OP!
https://market.android.com/details?id=com.jrummy.busybox.installer
In the script manager, its a little like using terminal or command prompt. Just load up the txt and run as root. They will ask you to choose your scrolling speed (just type 0 so the text appears fastest inside the script manager) so you have to tap the screen for the keyboard to appear. You need the on screen keyboard to choose the presets too. Just choose one of them. I chose option 2 (aggressive setting 2) and currently my phone feels very fast.
ive found a video tutorial on how to install this script on youtube. http://www.youtube.com/watch?v=WADt5tK6Ths
Issues:
(PM me or leave a reply so I can put them here and warn the others not to use unsuitable presets)
------------------------
21 August 2011
hi guys, i saw this supercharger on a lg optimus one subforum. claims it works on all android phones.
it says
"What's it do?
It makes your phone FAST... super snappy with better multitasking!
It rearranges and fixes the OOM Groupings and Priorites and lowmemorykiller values.
So basically, it's a COMPLETE MEMORY MANAGEMENT FIX!
It's the ONLY one of it's kind "
heres the link http://forum.xda-developers.com/showthread.php?t=991276
dont know whether it will work or whether it will give us much improvement to our phone. any one?
eejin2 said:
hi guys, i saw this supercharger on a lg optimus one subforum. claims it works on all android phones.
it says
"What's it do?
It makes your phone FAST... super snappy with better multitasking!
It rearranges and fixes the OOM Groupings and Priorites and lowmemorykiller values.
So basically, it's a COMPLETE MEMORY MANAGEMENT FIX!
It's the ONLY one of it's kind "
heres the link http://forum.xda-developers.com/showthread.php?t=991276
dont know whether it will work or whether it will give us much improvement to our phone. any one?
Click to expand...
Click to collapse
Im thinking of giving this a try. It also has an androidiani recovery zip. Hmm...
Looks great. Anyone tried yet?
Sent from my MilestoneXT720 using XDA App
I'll have look when i get home, sounds promising though.
But even better is if one of our devs check this out to really see what's up..
Sent from my XT720 [MZ - CM 6.3.0]
You just as well use minmod open recovery it has a very similer memory managment.
Sent from my XT720 using XDA Premium App
mchlbenner said:
You just as well use minmod open recovery it has a very similer memory managment.
Sent from my XT720 using XDA Premium App
Click to expand...
Click to collapse
I suggest you read the OP, it specifically says that it is NOT the same as minmod, minfree, auto killer or all that..
JiroPrinz8 said:
I'll have look when i get home, sounds promising though.
But even better is if one of our devs check this out to really see what's up..
Sent from my XT720 [MZ - CM 6.3.0]
Click to expand...
Click to collapse
so how's it? does it work?
edit
wait i just saw that they talked only about gingerbread, and the linked tutorial said too that it was only for cm7 (he might have wanted everyone to play safe and not risk screwing up their phone)... anyone tried this yet?
It says for Milestone only, so does that mean what it says? For milestone only? We have the Xt720 (well I'm sure you know that lol)
Yeah and you're right eejin2 looks like it's for CM7. So maybe if we get CM7 then it won't be for milestone only
But while on the subject of speed, with the Special's governors fixed and overclocked at 1200, wow dude it's super fast! don't think this is even needed! lol
haha. yeah its fast of course.. but im currently on cm6.3 and im very satisfied. not a single hang since i flashed 6.1.2. only overclocked at 900, and underclocked at 500 sometimes. never had to do a battery pull at all. wont long term running overclocked at 1200mah damage your processer?
eejin2 said:
haha. yeah its fast of course.. but im currently on cm6.3 and im very satisfied. not a single hang since i flashed 6.1.2. only overclocked at 900, and underclocked at 500 sometimes. never had to do a battery pull at all. wont long term running overclocked at 1200mah damage your processer?
Click to expand...
Click to collapse
Long term heat will damage your processor. Obviously if OC'd at 1200 and running intensive apps, your temp will shoot up. SetCPU or any other profile mgr has profiles to ramp up or down you CPU speed accordingly. I have run 1100/74 sinceI first installed MSOC but I have SetCPU profiles to throttle it back when I don't need that much power and speed.
Woodrube said:
Long term heat will damage your processor. Obviously if OC'd at 1200 and running intensive apps, your temp will shoot up. SetCPU or any other profile mgr has profiles to ramp up or down you CPU speed accordingly. I have run 1100/74 sinceI first installed MSOC but I have SetCPU profiles to throttle it back when I don't need that much power and speed.
Click to expand...
Click to collapse
Yeah I use setcpu as well but only for temperature. I let it run natural otherwise. But like i said, I have been on so many ROM's and I like to put them to the test so I have been at 1200 since march for the most part and never have any overheat issues. No reboots. And if it does burn up I have a year and a half left on my warranty lol. CBW gives 2 year warranties. I don't need it clocked that high, it will run well at 800, I just like to put it to the test. And being at 1200 on the special now has made the biggest difference out of all that I have tried. But of course haven't tried it long enough to really compare with cm6.
Seems like 1200 since march is pretty much long term lol. My phone is still like new!
Anyone tried this yet? Any comments?
Sent from my MilestoneXT720 using XDA App
It works very well with phones having limited memory. Must try. Zepp is good.
Sent from my GT-I9100 using Tapatalk
sileshn said:
It works very well with phones having limited memory. Must try. Zepp is good.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
isnt it for gingerbread only? i read it in the post...
eejin2 said:
isnt it for gingerbread only? i read it in the post...
Click to expand...
Click to collapse
No. It is for a variety of phones with different OS. He started of by creating it for the milestone and then made it universal.
Sent from my GT-I9100 using Tapatalk
so is it 100% safe to use it on our phone? im currently on cm6.3.
eejin2 said:
so is it 100% safe to use it on our phone? im currently on cm6.3.
Click to expand...
Click to collapse
Backup and try. You can even undo its effects as it backs up the files it modifies. Ask Zepp about the best settings for your phone by giving your phone details.
Sent from my GT-I9100 using Tapatalk
I just ran the script with Aggressive 2 settings (6, 8, 25, 30, 35, 35)
Very easy to apply and run. It's a little difficult to weave through Zepp's writing, but essentially it boils down to this:
1. Download V6_Supercharger_for_Android-update8.sh.txt (at the bottom of the first post) to the sdcard
2. Download Script Manager Market Link
3. Open Script Manager and open the .txt file you just downloaded. Make sure Run as Root is selected.
4. Pick one of the many presets!
5. Reboot
Have yet to do some more testing with the current preset, but I'm sure it'll be good
Running the multi-tasking option (no.7); for me it is quite smooth but will wait and see.
I saw it long time ago but never had the confidence in trying this out
MilestoneXT720 - CM 6.3.0 by MZ
molohov said:
I just ran the script with Aggressive 2 settings (6, 8, 25, 30, 35, 35)
Very easy to apply and run. It's a little difficult to weave through Zepp's writing, but essentially it boils down to this:
1. Download V6_Supercharger_for_Android-update8.sh.txt (at the bottom of the first post) to the sdcard
2. Download Script Manager Market Link
3. Open Script Manager and open the .txt file you just downloaded. Make sure Run as Root is selected.
4. Pick one of the many presets!
5. Reboot
Have yet to do some more testing with the current preset, but I'm sure it'll be good
Click to expand...
Click to collapse
Wow thanks man, you made it seem much easier than the original post! lol. Very useful bro thanks again
I apologize if this has been asked and/or answered, but I could not find the answer on XDA or in this thread. Not even in a Google search. If I missed it, could someone direct me to it? I really did look. LOL
I was wondering if it would be possible for me to increase the brightness of the capacitive buttons on my Rezound permanently. I've installed NilsP ICS Business Sense ROM (I absolutely love it), but the buttons are too dim for my usage. I can go in and change the file "currents" in the /sys/devices/platform/leds-pm8058/leds/button-backlight directory, but it reverts back to a value of "2" after a reboot. Also, if I change the file "01tweaks" in the /system/etc/init.d directory, after a reboot, it also reverts back to a value if "2". Where in the system could I change that value so that it would become permanent? Or is it possible? Or would it be possible, even though I would prefer the above solution, to remove it completely so that it's back to stock values that the system controls?
Sent from my ADR6425LVW using xda premium
Personally, I would be careful how high you bump it. HTC sets that level for a reason.
You might burn them out over time with more current, and also your battery life will take a hit.
But if you can figure it out, go experiment. I haven't heard of anybody doing this before.
I'm not sure that that file is referring to the current in amperage. It's in with other files like "brightness" (value of 60) and "maximum" (value of 255). Also, if you look at the file "01tweaks", there is a section called "#dim-leds" that has an echo value of "2" that appears to be written to the file "currents".
I could be all wrong about this. And if someone knows, please let me know.
Other than that, I'm still looking for a fix for this issue.
Sent from my ADR6425LVW using xda premium
Anyone else have any ideas? I'm running out. LOL!
Sent from my ADR6425LVW using xda premium
I saw this app the other day, and by looking at the screen shots of it, you can do some tweaking of the Capacitive button brightness
http://forum.xda-developers.com/showthread.php?t=1719934
GrayTheWolf said:
Personally, I would be careful how high you bump it. HTC sets that level for a reason.
You might burn them out over time with more current, and also your battery life will take a hit.
But if you can figure it out, go experiment. I haven't heard of anybody doing this before.
Click to expand...
Click to collapse
They're just LEDs. They don't really burn out unless you physically damage them or give them way too much voltage.
---------- Post added at 07:46 PM ---------- Previous post was at 07:45 PM ----------
mclass55 said:
I saw this app the other day, and by looking at the screen shots of it, you can do some tweaking of the Capacitive button brightness
http://forum.xda-developers.com/showthread.php?t=1719934
Click to expand...
Click to collapse
Doesn't work on mine on CM9.
scy1192 said:
They're just LEDs. They don't really burn out unless you physically damage them or give them way too much voltage.
Click to expand...
Click to collapse
That's what I said, is it not?
You could try this. This file, when placed in the /system/etc/init.d folder will change the leds to a dimmer value than stock. Maybe if you play with changing the shecho number you can achieve what you are after. I believe that a value of "0" is off, but not sure and I haven't played with it to find out.
Just unzip and let us know how it works out for you.
View attachment dimleds.zip
GrayTheWolf said:
That's what I said, is it not?
Click to expand...
Click to collapse
No, you said that HTC set the normal level for a reason. Running it at 100% all the time would not damage the LEDs though.
Drop this file in your /system/etc folder, replacing the stock one. Cleaned up, and modified to work with a stock kernel or lean kernel.
Please open up the file, and read some of the notes I added, so you know what this does and how to change it if you so desire. It is very basic and straightforward.
Also, please remember one thing, if you want to go to the stock kernel, simply change any words in the scripts from "interactiveX" to "interactive".
Recommended lean kernel 3.16 with these scripts.
Designed to work with ALL Galaxy Note 3's running touch wiz 4.4.2 ROMs and running lean kernel or stock kernel. Other kernels are not guaranteed due to the voltages applied.
This will make a huge difference in performance and battery. Been using this (developed by me) for a long time now.
Summary:
*I/O optimization
*tuned interactive parameters
*fixed sysfs permissions for cpu's (root now has full control of sysfs tuneables)
*GPU sysfs identified for user to customize
*screen off frequency set to 1.2 GHz (can be changed by user)
*custom voltage set for bin 2 device. (Read instructions within file to adjust for others bins accordingly)
*custom mpdecision tuning and other relevant instruction regarding mpdecision binary
*general CPU tweaks for better performance, responsiveness and battery life (yes all 3 can be achieved, and are)
Again, open the file with a file explorer (or notepad+ in windows). Read it, understand it, adjust what you want, or leave it be. These settings are very much dialed in for the interactiveX governor of LK. It won't get much better. I'd say take a look at the voltage portion and mpdecision for now (found at the end).
Once more, drop file into the /system/etc directory... Replace the existing one, and reboot.
FILE DOWNLOAD
Updated today... many useful changes, and fixes (set up for stock kernel for now)
https://www.dropbox.com/s/tjlygujptls3lks/init.qcom.post_boot.sh?dl=0
Thanks man!
Thanks man best Antutu score.
Best. Disclaimer. Ever.
Sent from my SM-G900V using XDA Free mobile app
Hahahahahahah I love the disclaimer.
Thanks! Helps a lot
Sent from my SM-N900V using xda app-developers app
I've noticed my phone lags alot less now and some things I had going wrong (if I turned torch on more than 15 seconds it would freeze and Multiwindow didn't like to work) work now. I don't know why or how or even if it is supposed to do anything to those things and it's just a very odd coincidence. But I've noticed my battery life is horrible now. Running it with Alliance 2 and with my ZeroLemon I used to get 10-11 hours on screen time and that's down about half to 5 or 6 hours. I know you said you could tweak stuff but I have no idea about that. Any recommendations for me to change in the script? Thanks again if for anything my phone running smoothly again!
amebiasis said:
I've noticed my phone lags alot less now and some things I had going wrong (if I turned torch on more than 15 seconds it would freeze and Multiwindow didn't like to work) work now. I don't know why or how or even if it is supposed to do anything to those things and it's just a very odd coincidence. But I've noticed my battery life is horrible now. Running it with Alliance 2 and with my ZeroLemon I used to get 10-11 hours on screen time and that's down about half to 5 or 6 hours. I know you said you could tweak stuff but I have no idea about that. Any recommendations for me to change in the script? Thanks again if for anything my phone running smoothly again!
Click to expand...
Click to collapse
If you aren't using lean kernel, you need to change the governor in the script to NOT say "InteractiveX"... Stock, or all other kernels need "interactive"... Otherwise the governor will be stuck on performance.
That is likely your issue.
Most people don't know that the note 3 boots with the performance governor enabled. The /system/etc/init.qcom.post_boot.sh file executes after the boot complete flag and changes the governors, among other things.
Edit the file, change the governor call out to "interactive".
Should fix it.
Thank you sir!
Running amazing after changing things over to "interactive" in the script with the stock kernel. Much more fluid speed on Eclipse with the battery life a bit better. Thanks for sharing! :highfive:
Wow night and day difference by changing that script to just interactive. Been flying all day playing games and watching movies total SOT (with my ZeroLemon) is just over 5 and a half hours screen brightness at about 65% using Lux and Bluetooth and I'm only at 67% awesome job man and thank you for steering me in the right direction!
Is the 300 slot removed from this script?
Also to my understanding this is mainly for the dev edition and lean kernel correct. But most of us r on the retail. Is there anything else to change besides the interactive for better performance?
Sent from my SM-N900V using xda app-developers app
stalls said:
Is the 300 slot removed from this script?
Also to my understanding this is mainly for the dev edition and lean kernel correct. But most of us r on the retail. Is there anything else to change besides the interactive for better performance?
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
I can tell you for sure...this scripts works fine for plain jane stock kernel (because that is all you can use on retail Verizon N3) as long as you change the "interactiveX" to just plain "interactive"
Obviously you need root to swap out the script.
Sent from my Note 3 via Tapatalk
donc113 said:
I can tell you for sure...this scripts works fine for plain jane stock kernel (because that is all you can use on retail Verizon N3) as long as you change the "interactiveX" to just plain "interactive"
Obviously you need root to swap out the script.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
Big difference in battery life when i changed interacticeX to interactive. Thanks for this OP. :thumbup:
Just want to provide my stats after using the script on eclipse rom 2.2./interactive. Screen on time was 6.5 hours with the phone. Before the script I would average about 4 hours. I want to thank the OP, this was a great tweak. Thumbs up.
Just giving you all a heads up.... I think there may have been a few errors in the stock init.qcom.post_boot file (they are human too, remember).
I am testing a few small changes to certain lines in the "factory" script to make sure. A brief explanation of it is that there are certain lines I removed from the one you all are using right now, and I did so because the file paths being called out did not exist!
However, I was going over this again tonight, getting ready for the official LP release and decided to review this odd discrepancy one more time. After doing some digging, I found that the file that some of those values were intended to be written to, were actually somewhere else!
Doh! - Sammy/QC. It is very possible that this location changed from a previous design or fs structure and somebody simply forgot to modify the script. Very interesting indeed.
Anyways, after I run this for a couple of days and do a little bit more investigating, I'll post the updated script for all of you.
Updated link and file. Please update if you were using this before, as there are many changes that were critical to stability and performance (errors made in this stock script)
Other devs, I recommend working this into your ROMs, given that fact.
red_can_soda said:
Updated link and file. Please update if you were using this before, as there are many changes that were critical to stability and performance (errors made in this stock script)
Other devs, I recommend working this into your ROMs, given that fact.
Click to expand...
Click to collapse
Question. So if this new file is set up for stock kernel for now, is it set to interactive or do we still need to change from interactiveX on retail?
Edit: was being lazy. Went ahead and went through script. Didn't see interactiveX anywhere.
red_can_soda said:
Updated link and file. Please update if you were using this before, as there are many changes that were critical to stability and performance (errors made in this stock script)
Other devs, I recommend working this into your ROMs, given that fact.
Click to expand...
Click to collapse
I'm not so sure the latest script is good or not....on my stock kernel Verizon N3 (NC4 firmware and kernel with NK1 radio) using the new script seems to have killed my battery life. I went from 33% to 20% in about 20 to 30 minutes.
I reset by restoring original script...rebooting...restoring your original script (interactiveX changed to interactive)...rebooting
I had to charge the phone so can't give a real check until I get back to 33% or so.
Sent from my Note 3 via Tapatalk
donc113 said:
I'm not so sure the latest script is good or not....on my stock kernel Verizon N3 (NC4 firmware and kernel with NK1 radio) using the new script seems to have killed my battery life. I went from 33% to 20% in about 20 to 30 minutes.
I reset by restoring original script...rebooting...restoring your original script (interactiveX changed to interactive)...rebooting
I had to charge the phone so can't give a real check until I get back to 33% or so.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
Same here on battery drain. Not as smooth either running biggins rom "possible reason". I might try this on a stock Rom to see if that makes a difference. Hard to beat untouched biggins right now though.
I was perusing the OP3 forums and stumbled on this.
Since our Axon 7s use the same CPU, would the same principles used by them apply to us as well? I would be more than happy to spend time tweaking and sharing my results if this is the case.
Update: Works great for the Axon 7. There's even an app to handle everything if you don't want to get your hands dirty!
Update: Took the dive and flashed the Project Zhana profile from the thread. So far so good! I'll upload some battery stats when I get the chance.
I guess that I will take the plunge also. I used a couple of these profiles with my Nexus 5x and they working wonders especially paired with a nice custom kernel.
Great find! I'm taking the plunge as well.
I took the plunge too! Installed the zip and found that the profile was created in the init.d folder. I'm using Freeza's BeastMode Kernel vR12, and it has init.d support, but for some reason, it wasn't working for me, and the setting were getting reset and not getting applied on boot. So ended up setting init.d emulation in kernel aduitor, and that worked. My phone's been up for 15 hours, with 1.5 hours of sot with moderate use, and there's 78% left.
I tried it. Now I am missing my ext sdcard. Will check the install script when I get home.
Sent from my ZTE A2017U using XDA-Developers mobile app
JeromeLeung said:
Update: Took the dive and flashed the Project Zhana profile from the thread. So far so good! I'll upload some battery stats when I get the chance.
Click to expand...
Click to collapse
Does exkm show the profile being applied? Flashed the zip and I'm not seeing anything modified that stands out.
tzbigworm said:
Does exkm show the profile being applied? Flashed the zip and I'm not seeing anything modified that stands out.
Click to expand...
Click to collapse
I'm using kernel adiutor and it shows the changes in governor tunables. I've also been monitoring CPU frequency with cool tools. Might be worth mentioning I'm using beastmode kernel 09.
JeromeLeung said:
I'm using kernel adiutor and it shows the changes in governor tunables. I've also been monitoring CPU frequency with cool tools. Might be worth mentioning I'm using beastmode kernel 09.
Click to expand...
Click to collapse
I think my turntables are showing me the stock values, though. I'm not sure.
tzbigworm said:
I think my turntables are showing me the stock values, though. I'm not sure.
Click to expand...
Click to collapse
Here's what I'm seeing for target_loads
JeromeLeung said:
Here's what I'm seeing for target_loads
Click to expand...
Click to collapse
Definitely not seeing that. Stock values confirmed. I flashed the zip from that 5X but I didn't have kernel adiutor installed. Should I flash it again? I'm running Beastmode R12.
tzbigworm said:
Definitely not seeing that. Stock values confirmed. I flashed the zip from that 5X but I didn't have kernel adiutor installed. Should I flash it again? I'm running Beastmode R12.
Click to expand...
Click to collapse
Sounds like you forgot to run the script, lol. If you flashed the zip for the zhana profile you have to go to the terminal (I use terminal emulator from the play store) and run
Code:
su
PXZ
JeromeLeung said:
Sounds like you forgot to run the script, lol. If you flashed the zip for the zhana profile you have to go to the terminal (I use terminal emulator from the play store) and run
Click to expand...
Click to collapse
Ahaha! I'm too use to exkm and just loading profiles lol! Thank you sir!
No problem. Let me know how it works out for you. I myself am seeing better battery life and I run my screen at full brightness all the time, haha
JeromeLeung said:
No problem. Let me know how it works out for you. I myself am seeing better battery life and I run my screen at full brightness all the time, haha
Click to expand...
Click to collapse
Nice! Which if the profiles are you using? I'm using the third profile, which I was zana battery, I think. I don't know how extreme the extreme profile would go lol. Would it be save to say that we could use profiles from the 3T forum because it's the same SoC?
tzbigworm said:
Nice! Which if the profiles are you using? I'm using the third profile, which I was zana battery, I think. I don't know how extreme the extreme profile would go lol. Would it be save to say that we could use profiles from the 3T forum because it's the same SoC?
Click to expand...
Click to collapse
I'm using the zhana balanced one. If I remember correctly it's the first option. As far as if these profiles are safe or not, I'm no expert, but I haven't come into any issues yet (knock on wood)!
JeromeLeung said:
I'm using the zhana balanced one. If I remember correctly it's the first option. As far as if these profiles are safe or not, I'm no expert, but I haven't come into any issues yet (knock on wood)!
Click to expand...
Click to collapse
I would think, at the worst, it'd bork the kernel, forcing a reflash of the kernel, or dirty flashing the rom.
tzbigworm said:
I would think, at the worst, it'd bork the kernel, forcing a reflash of the kernel, or dirty flashing the rom.
Click to expand...
Click to collapse
I think this zhana/xanah profile is done via init.d so if I understand this correctly, these tweaks to the governor are applied on boot (meaning we'll be able to boot at the least). I think if we run into any trouble, all we have to do is delete the 75PXZ script in etc/init.d and everything will go back to stock.
JeromeLeung said:
Here's what I'm seeing for target_loads
Click to expand...
Click to collapse
Yep, that's showing for me too. Nice! You running Xposed by chance?
JeromeLeung said:
Here's what I'm seeing for target_loads
Click to expand...
Click to collapse
Thanks to your (both) heads-up, I've been running X.A.N.A.-Balanced for the last day & all is well!