[Script][Mod] Increase vibrator strength - Nexus 5 General

Hi all ,
I found something interesting, at least for me... I think that the vibrator strength is not very strong for the on screen actions like mainly the navbar buttons (even if the vibrator amp is set to 100 and even if the 4.4.1/2 update increased a little the thing).
You need a rooted device with init.d support, if you have not init.d support you can use this app: Universal init.d (tested and it works). Init.d script is made to have the new values will applied on boot.
So to change the value in live with a file explorer (for testing before find the right value to put in the init.d script), go to:
Code:
/sys/class/timed_output/vibrator/driving_ms
And change the value for driving_ms to something like 35/40 (stock is 20) and the vibrator strength is increased (don't forget to save)... Adjust the value to your taste. But I don't think that a higher value than 60 will be a good idea (but it's up to you).
Also (in the same path) the warmup_ms seems to to do almost the same thing but I found that the vibrator strength is not the same by changing this value, It seems for me a little weird. So for now I change only the driving_ms value.
You can use an init.d script to keep the value at boot:
Code:
#!/system/bin/sh
#increase the vibrator strength
#stock value is 20
echo 40 > /sys/class/timed_output/vibrator/driving_ms
Just in case, in attachment the init.d script (remove the .zip extension before putting the script in /system/etc/init.d). Set the correct permissions like this, reboot:
Notes:
This will also increase the vibrator strength for incoming call/SMS-MMS, etc...
It's not the same thing as the vibrator amp...
It should work on all stock/AOSP based rom and stock/custom kernel, I don't know about CM based rom (but if you have the path mentioned above it should work).
I'm not responsible if something goes wrong with the vibrator, avoid values higher than 60 I think...
Hope this help

Hi,
I've been tested with the warmup_ms value in addition to the driving_ms, it seems it produces a more "consistent" vibrator strength, or it is only me?
So for now I ended with this:
Code:
echo 32 > /sys/class/timed_output/vibrator/driving_ms
echo 32 > /sys/class/timed_output/vibrator/warmup_ms
A 40 value as previously is a bit stronger, so for now I set it to 32 (35 is good too)...
Init.d script in attachment, don't forget to remove the .zip extension before putting the script in /system/etc/init.d.
Any feedbacks? CM users?

Doesn't this script set the same value as the apps below?
https://play.google.com/store/apps/details?id=com.dunnow.software.vibrationTuner&hl=en
https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod&hl=en

Hi,
Nope, at least for Trickster Mod (I use it) it only modifies the vibrator amp in /sys/class/timed_output/vibrator/amp... An it seems that it's the same thing for the first app, only the vibrator amp is modified.
Try with the values I modified and you'll see that it's not the same thing..., here you can have a vibrator strength stronger than with only the vibrator amp setting (and even at 100)...
Sent from my LG-D802 using xda premium

Hi,
Any feedbacks?
Some have tested on CM?
Forgot to mention that, obviously, you can change the vibrator amp too if it's not enough for you (and no need for an app):
Code:
/sys/class/timed_output/vibrator/amp
The init.d scrip will be like this (a value of 100 is an example, it's the max):
Code:
echo 100 > /sys/class/timed_output/vibrator/amp
If some wonders if this affects the battery life, I did not notice anything significant, at least for me...

Can you write a how to install this. I'm new to init.d script
Sent from my Nexus 5 using Tapatalk

killajoe said:
Can you write a how to install this. I'm new to init.d script
Click to expand...
Click to collapse
Hi,
I need more information... I thought the OP was clear, but who knows
I assume you are rooted right?
Is your current setup support init.script? For this check the OP of the kernel/rom you're using (or at least check /system/etc/, have you an init.d folder?).
If you are stock (rooted) use the app I mentioned in the op (https://play.google.com/store/apps/details?id=com.androguide.universal.init.d&hl=fr), the init.d scripts needed are in attachment in posts #1 and #2 with "how to"...
If I'm wrong explain better
Thanks

I actually like the vibration that subtle. I had several phones which had a too strong vibration alarm in my opinion. But still a good thing that you can adjust that, I might just try it out. Btw I remember my nokia 6410 was dancing into the sink full of water by the vibration alarm
Sent from my Nexus 5 using xda app-developers app

I just used my Galaxy Nexus yesterday and the vibrator in that is much better. It can handle short blips better and seems to vibrate the entire phone. Nexus 5 can't handle strings either...
Sent from my Nexus 5

Any way to rig this to make the vibration on my Moto X weaker?
Sent from my Nexus 5 using XDA Premium 4 mobile app

_MetalHead_ said:
Any way to rig this to make the vibration on my Moto X weaker?
Click to expand...
Click to collapse
Hi,
Sorry but I don't know for other devices... try to see if you have the path /sys/class/timed_output/vibrator/
If the different setting are presents (driving_ms, warmup_ms, amp) try to change the values and see...
Sent from my LG-D802 using xda premium

Is there any way to do this without root??

hbkekko said:
Is there any way to do this without root??
Click to expand...
Click to collapse
Hi,
Nope, sorry...

Is this strength or just milliseconds? Seems if I put it to 500 it vibrates for half a second at max strength.

viking37 said:
Hi,
I need more information... I thought the OP was clear, but who knows
I assume you are rooted right?
Is your current setup support init.script? For this check the OP of the kernel/rom you're using (or at least check /system/etc/, have you an init.d folder?).
If you are stock (rooted) use the app I mentioned in the op (https://play.google.com/store/apps/details?id=com.androguide.universal.init.d&hl=fr), the init.d scripts needed are in attachment in posts #1 and #2 with "how to"...
If I'm wrong explain better
Thanks
Click to expand...
Click to collapse
I am rooted, unlocked, stock. So I just run those scripts in the program listed and that's it?
Sent from my Nexus 5 using Tapatalk

killajoe said:
I am rooted, unlocked, stock. So I just run those scripts in the program listed and that's it?
Click to expand...
Click to collapse
Hi,
Yes, install the app then run it and choose to run the test (you'll have a Superuser request, accept) then reboot:
After if init.d script works you'll have an init.d folder in /system/etc (and the message like above). Put the init.d script named 01vibratorstrength in the init.d folder and set the correct permissions like in the OP.
Run the app again and activate the init.d script, set to ON like the screenshot:
Reboot again and all will be fine. You'll feel that the vibrator strength is increased (wait about 1-2 seconds after boot). You can check the values are changed by following the path /sys/class/timed_output/vibrator/**** (the vlaue you want check and you have changed).

Hi,
Another feedbacks?
killajoe, did you manage to get it working?
Thanks

Related

Stagefright, VM Heap, SYSCTL and other performance related options

With the recent release of Spz0s rom and Adrynalyne getting this beat over clocked these settings are becoming obsolete. Use at your own discretion.
I recently restored my phone to stock, with basic settings, meaning I did not use any of the settings listed here. I scored a 1013 on a bench with stock everything. Now that I have VTL Launcher as stock again and have everything set back up for me, I'm scoring 1000s and 990s regularly. Again without any of these settings enabled. Which is leading me to believe that a stable system is the fastest thing when it comes to performance and benchmark scores. The settings listed below did help me out, with an unstable system. Now that I am running on a stable system, none of the settings below helped my performance or bench scores, they only hurt them. So these settings below will help anyone with an unstable system to not feel the lag of said unstability. If you try these settings and they don't do anything, or hurt your performance or score, turn them back to stock and revel at how much you rock for having a super stable system! I have also noticed that the app AUTO KILLER MEMORY OPTIMIZER virtually replaces sysctl. If you run AUTO KILLER I would suggest setting sysctl back to stock! I would recommend AUTO KILLER MEMORY OPTIMIZER from the Market to EVERYONE with a Zio. Nice app, set it to Aggressive!
FIRST OFF, THESE SETTINGS ARE ONLY CHANGEABLE IF YOU ARE ROOTED!! If you are not I cannot help you!!
I am making this thread to address performance issues with the Zio. If you have done a benchmark score with just basic settings, it's already apparent to you the Zio is not the best phone. I have found some tweaks to make the phone run faster and score better on benches.
USE THESE SETTINGS AT YOUR OWN RISK. IF YOU SCREW SOMETHING UP, DON'T CRY TO ME.
Stagefright: Stagefright is part of the stock media player that comes disabled on the Zio. Turning on stagefright will increase your benchmark score by a lot, and has also been reported to make Video Playback much better, getting rid of jumpy lagging videos.
You need to make sure you have r/w(read/write) access in your file manager. Root Explorer has r/o(read/only) and r/w. You cannot change any files without r/w access in your file manager.
To Enable Stagefright you open your file explorer(i.e. root explorer, astro, etc.) and navigate to the system folder. Open build.prop in your text editor. Scroll down to where you find stagefright. There are four settings for it grouped together near the bottom of the script. Next to each setting it says =false. You need to edit the false to say true. Once that is done, go up just slightly from that spot, there is also another spot to enable stagefright. Change that to true as well. Also notice that just above this last stagefright script, there is something about the vm.heap and dalvik cache. This is where you change your VM Heap size.
(NOTE: ENABLING THE HTTP SETTING IN STAGEFRIGHT ALLOWS FOR A RICHER HTTP BROWSING EXPERIENCE BUT WILL ALSO PUT A GREEN BAR ON YOUTUBE VIDEOS. KEEPING IT SET TO FALSE WILL AVOID THIS GREEN BAR AND SHOULD NOT AFFECT OVERALL PERFORMANCE!)
VM Heap-Not exactly sure what the technical aspect of it is, but increasing the vm.heap gives the dalvik cache more room to work with, thus making your memory faster. THIS NUMBER SHOULD NOT BE SET BELOW ANDROID DEFAULT WHICH IS 24. And should also not be set above 44. If you want to change this number, add or subtract 4 within the above values, 24-44. This can go down to 16 but you'll see the results and why I said to leave it up pretty fast.
SYSCTL- To edit these settings, open your file explorer, hit the ETC folder. Scroll to bottom and find sysctl.conf, long press and open in text editor. So far I can only say there are three settings here you need to adjust.
To edit SYSCTL settings you must first download and install the app sysctl config from the Market. After you set it up initially it can be uninstalled and leave behind the settings folder for further settings changes by manually editing or you can keep it and just use it to make the changes.
First is MIN FREE KB. This number will not be the same for everyone, although I can tell you setting this number above 4096 seems to slow the system way down. Although you may try any of the following numbers..
1536, 2048, 4096, 5120, 5632, or 6144.
These are the only numbers I would suggest using as they are parameters that came out of the phone itself.
sys/module/lowmemorykiller/parameters. <----DO NOT CHANGE the numbers in this location, they are system defined parameters and are NOT to be changed!
The second setting is vfs.cachepressure. I have this set to 10. Default is 50. Basically what I've read about this, it opens more room by setting it lower, leaving more memory free from constantly checking and clearing the cache. Read more here http://forum.xda-developers.com/showthread.php?t=523707&page=12
The Third setting is oom. It's the last value in sysctl.conf and needs to be set to 1 or 0. Instead of your phone starting to kill apps when it's out of memory, it does something else that I didn't quite understand, which is supposed to boost memory performance. Some people are seeing great results with this setting. Some people say it doesn't do anything. Seems to be specific to the user, and I have yet to find anything in common between two users who say this helps. Although bench scores are higher with it set to 1.
For these settings to take effect you must reboot your phone. Changes to these settings are only applied by a reboot, so any time you change anything, REBOOT!
If you do not know how to change settings manually, there are two apps in the market to help. VM Heap Tool will change your VM Heap for you, no need to manually edit if you don't want to. sysctl config is an app that will allow you to easily change the sysctl settings.
There is an App that will change your stagefright settings for you called Blade Buddy. I did not have a good expeience with this program and would suggest that you edit stagefright manually since it's pretty easy with a superuser file manager.
I can say with certainty that turning on stagefright and adjusting and playing with the rest of the settings that your phone will turn in to a beast compared to how it came out of the box.
As far as battery performance goes, I've noticed a 10-15 percent increase(estimated) over the life of a charge(depending on amount of usage and type). I have noticed more battery use. But not so much that these settings wouldn't be worth using. I gave numerous variations of these settings tries over 2 very long months of restarts and three different benchmark programs. Any additional information or discoveries are welcome.
If this helped, please hit Thanks!!
Muchos Gracias to everyone in #openzio as always. Spz0 n Mattix are always a big part of anything I do. They are always nice enough to save me from myself. And much thanks to anyone that helps out with the Zio at all. Lets own this phone!
Nice write-up bro.
Well, good guide. Hopefully Kyocera calls me back in regards to the kernel source code so we can really overclock this thing.
Sent from my Zio using XDA Premium App
Their lawyer in San Diego got a hold of me on Facebook. Asked me to call her back. Three calls and no dice. Waiting on her response now. Hopefully soon. She said they are "working the bugs out". Which is a load of BS since we have phones in our hands, the source is done. They just have to give it to us and I told her bluntly just that.
Tell them to call me lol, I want the source. Give us the source!
Sent from my Zio using XDA Premium App
So what happened to getting it? Teacher not know the right trick? Have you heard about using git to get the source? I dunno what git is but it may help? Ever heard of it?
Sent from my Zio using XDA Premium App
http://en.wikipedia.org/wiki/Git_(software).
Google is your friend???
Also, I don't have a sysctl.conf file. At least not where you said it is or one that root explorer can find...
Yeah if I actually understood any of that I wouldn't be asking.
Ok here is the best benchmark average I have gotten so far. These are the settings I used to achieve it.
Avg Benchmark - 795
High - 900 (omitted from average)
Low - 710 (omitted from average)
Avg with high and low only changed by 6 points.
Sysctl Support - Enabled ( I am using the Sysctl app form the market.)
Min free Kbytes - 4096
Dirty Ratio - 80
Dirty BG Ratio - 40
Oom Allocating Tasks - Enabled
VM Heap Tool - VM Heap set to 36m
Stagefright settings are all set to "True"
What we need to know now is what setting are going to speed up the UI. Like cutting load times on FB and other apps, what is making the phone just lightning fast? Doesn't seem to matter too much as long as you don't go above 4096. Finally started to see some system lag with 8192. We need to figure out what makes the phone the most responsive, fastest, beast of a phone.
Messing with the radio numbers only seems to slow me down. And still can't really find anything on what vm.swapiness does either.
sinisin said:
What we need to know now is what setting are going to speed up the UI. Like cutting load times on FB and other apps, what is making the phone just lightning fast? Doesn't seem to matter too much as long as you don't go above 4096. Finally started to see some system lag with 8192. We need to figure out what makes the phone the most responsive, fastest, beast of a phone.
Messing with the radio numbers only seems to slow me down. And still can't really find anything on what vm.swapiness does either.
Click to expand...
Click to collapse
Well, I have also downloaded Link2SD from the market and put every app (except system apps) on the SD card and That has given me a little over 100MB free on phone storage and I am using Memory booster lite to free up memory on the phone. All of these things have made a huge difference in the speed and performance of the phone including page load times. (facebook opens and loads almost instantly).
Be careful. Don't move things like Widgets that need to refresh or themes for your launcher or the launcher itself. Seems fine at first until you run for a while and Widgets stop and launcher always reloads.
Sent from my Zio using XDA Premium App
Are you on Wi-Fi while opening apps or 3G and if 3G how many bars?
Sent from my Zio using XDA Premium App
Using Root Explorer /ect/sysctl.conf I'm not seeing this file...
sinisin said:
Serious changes coming soon. New numbers up for min free KB below already.
Stagefright: Stagefright is part of the stock media player that comes disabled on the Zio. Turning on stagefright will increase your benchmark score by a lot, and has also been reported to make Video Playback much better, getting rid of jumpy lagging videos.
To Enable Stagefright you open your file explorer(i.e. root explorer, astro, etc.) and navigate to the system folder. Open build.prop in your text editor. Scroll down to where you find stagefright. There are four settings for it grouped together near the bottom of the script. Next to each setting it says =false. You need to edit the false to say true. Once that is done, go up just slightly from that spot, there is also another spot to enable stagefright. Change that to true as well. Also notice that just above this last stagefright script, there is something about the vm.heap and dalvik cache. This is where you change your VM Heap size. (NOTE: ENABLING THE HTTP SETTING IN STAGEFRIGHT ALLOWS FOR A RICHER HTTP BROWSING EXPERIENCE BUT WILL ALSO PUT A GREEN BAR ON YOUTUBE VIDEOS. KEEPING IT SET TO FALSE WILL AVOID THIS GREEN BAR AND SHOULD NOT AFFECT OVERALL PERFORMANCE!)
VM Heap-Not exactly sure what the technical aspect of it is, but increasing the vm.heap gives the dalvik cache more room to work with, thus making your memory faster. THIS NUMBER SHOULD NOT BE SET BELOW ANDROID DEFAULT WHICH IS 24. And should also not be set above 44. If you want to change this number, add or subtract 4 within the above values, 24-44.
Phone Edit- Found numbers for min free KB. sys/module/lowmemorykiller/parameters. 1536, 2048, 4096, 5120, 5632, 6144. Assuming these are new guidelines. Will edit fully tomorrow. Don't change these settings. They are system parameters and should NOT be changed.
SYSCTL- To edit these settings, open your file explorer, hit the ETC folder. Scroll to bottom and find sysctl.conf, long press and open in text editor. So far I can only say there are three settings here you need to adjust. First is MIN FREE KB. This number will not be the same for everyone, although I can tell you setting this number above 8192 will slow the phone down, most people report anything over 4096 slowing the phone down. The default is 2048, I would suggest going up to 4096 or 8192.
The second setting is vfs.cachepressure. I have this set to 10. Default is 50. Basically what I've read about this, it opens more room by setting it lower, leaving more memory free from constantly checking and clearing the cache. Read more here http://forum.xda-developers.com/showthread.php?t=523707&page=12
The Third setting is oom. It's the last value in sysctl.conf and needs to be set to 1 for everyone. Instead of your phone starting to kill apps when it's out of memory, it does something else that I didn't quite understand, and this should add speed to everything you do, like surfing or Facebook. Everything should load faster and smoother with this setting enabled. Remember stock value is Zero and may only be set to 1 or 0.
If this helped, please hit Thanks!!
Click to expand...
Click to collapse
Try /system/etc micro. Same thing.
Sent from my Zio using XDA Premium App
Current settings.
4096
95
60
50
Oom
VM heap 30
Stqgefright all but http
Running fast and stable. Launcher pro Orientation from portrait to landscape is faster. Home loads instantly even though I am not using a launcher from /system/app
I will be doing some more tweaks to speed this up but maintain some battery life.
Sent from my Zio using XDA Premium App
I have Stagefright fully enabled. Running 2048 Free KB. Stock radio and background. Turned oom to 0. Zoomin right along.
Sin. How did you edit sysctl.conf I can't find it in ETC
Sent from my Zio using XDA Premium App
Thanks! /system/etc still nothing. I have rtecdc_apsta.bin and void.fstab no luck still.
sinisin said:
Try /system/etc micro. Same thing.
Sent from my Zio using XDA Premium App
Click to expand...
Click to collapse
Looks like we need to include sysctl.conf in the next theme update.
Sent from my Zio using XDA Premium App

[MOD] [New Version]CPU Editor Modified for ATRICS or ICSROMs

As promised earlier that I would share my work and yes I stand by that promise. The modified CPU editor script.
CREDITS​smokin1337 The original creator of the script​upnndwn4par For his support
todobarato For suggesting optimization which was really useful​
ONLY FOR ATRIX 4G Running ICSROM or ATRICS
The usual warnings. Do not blame me for bricked phones. This is still under testing phase and I need testers.
Please donot PM me with the results, Post them here in this forum
New Version
Added an optimization suggested by todobarato (thanks!!) Works fine. The only problem still is the sticky bit issue. Still Working on it
Download the New Version Here.
Instructions
1. Flash in CWM
2. Reboot
3. The script should start working on its own (Doesn't Work for now)
Open terminal > "auto-cpu" (Without quotes)
And also please let me know if the CPU frequencies are reverting at boot or not?
Changes Made
1. The original script by smokin1337 is kept intact , so advanced users can still use the script as usual.
2. The modifications automatically shutdown one of the cores when its not required.
So please go ahead test it and let me know results.
Anyone is welcome to help and provide suggestion or even modify this and contribute.
deathscream said:
As promised earlier that I would share my work and yes I stand by that promise. The modified CPU editor script.
CREDITS​smokin1337 The original creator of the script​upnndwn4par For his support​
ONLY FOR ATRIX 4G Running ICSROM or ATRICS
The usual warnings. Do not blame me for bricked phones. This is still under testing phase and I need testers coz I just lost my phone to my girlfriend for a week
Please donot PM me with the results, Post them here in this forum
Download the attachment.
Instructions
1. Flash in CWM
2. Reboot
3. The script should start working on its own (Couldn't test it , Sorry guys)
And also please let me know if the CPU frequencies are reverting at boot or not?
Changes Made
1. The original script by smokin1337 is kept intact , so advanced users can still use the script as usual.
2. The modifications automatically shutdown one of the cores when its not required.
So please go ahead test it and let me know results.
Anyone is welcome to help and provide suggestion or even modify this and contribute.
Click to expand...
Click to collapse
Thanks for your job
I try it..to take off one cpu I have do it manually..on reboot the cpu starts both
andrea_marcello said:
Thanks for your job
I try it..to take off one cpu I have do it manually..on reboot the cpu starts both
Click to expand...
Click to collapse
Yes I got those same results from others. Can you try using SManager and select the script /system/xbin/auto-cpu and let me know of the results.
Thanks!
what is this for?
and how do i know if it is working or not?
mindstorms54 said:
what is this for?
and how do i know if it is working or not?
Click to expand...
Click to collapse
It allows CPU mods without using an app (which of course uses battery).
You can change min/max frequencies on each core individually. You can even take one of the cores offline completely. Running on one core is not noticeably different from two for routine use. I hardly see a difference. I can't give any hard number for the increase in battery life since I have only been using it for less than two days. But battery life is definitely better.
There is some more info here:
http://forum.xda-developers.com/showpost.php?p=34427620&postcount=785
*********************************
deathscream,
I just tried it. The script is not running automatically as far as I can tell. I am not seeing the second core shutting down.
Thanks, and keep up the good work.
I'll look into it. I just got my phone back. Now I can test it without any problems.
Sent from my MB860 using xda premium
Hello,
I am following this and I think you are complicating it to much.
I have test this script and the original and it never disable the 2nd core.
If you will disable it is very easy with the following command as su: echo 0 > /sys/devices/system/cpu/cpu1/online
The only issue is that it comes online very fast again and you have to execute the command again... I have found the script that disable the 2nd core but only when the screen off, this isn't our problem, by CPU-spy it show deep-sleep is working.
I have changed the script to disable the 2nd core when the CPU frequency is under 350Mhz, this check every X second (I use 35seconds, this can be changed) , now the second core is offline when it detects low CPU frequency and stay offline, if you need it again I have observed after switch off and on again the screen it comes back online or by open set-CPU(I have it on widget to check CPU temp) if you have. If you use one very CPU intensive app comes only by itself too.
I put the script on /system/etc change the correct permission, run with SDmanager.
The script is:
--------------------------------------------------------
#!/system/bin/sh
#
#
while [ 1 ]
do
CPU0=`cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq`;
if [ $CPU0 -lt "350000" ]; then && echo 0 > /sys/devices/system/cpu/cpu1/online;
fi;
sleep 35
done
-------------------------------------------------------------
I hope this help, I am using it on CM7 and work better that I have expected.
Sent from my MB860 using xda app-developers app
Thanks a lot. Will try it out.
Sent from my MB860 using xda premium
It' dont work for me automatically after reboot.
I use the terminal to put the values by myself
It's a great tool.
Thanks for the work
Regards
You have a lot of features about OC on Atrix (scripts) here
http://forum.xda-developers.com/showthread.php?p=23715720
And here
http://forum.frandroid.com/topic/93255-autoucuv-forcage-cpu-et-oc-uv-gpu/
And here
http://forum.frandroid.com/index.php?/topic/105205-[APP]-✖-AtrixTweaks-(19/08/12)#entry1701606
it works but not automatically. i noticed a little battery increase. from 12hrs i got about 15 hrs uptime running latest icsrom.
fabianowerner said:
it works but not automatically. i noticed a little battery increase. from 12hrs i got about 15 hrs uptime running latest icsrom.
Click to expand...
Click to collapse
Yes. I tried it . The script doesn't run automatically. The sticky bit setting is driving me nuts. haven't slept the whole night. adding this to userinit also doesn't work , so I guess the only way would be try upacking the booimage, ramdisk and adding to the init.rc . I'll try running that there. That should probably work. But can't say for sure.
relax dude... even with the 2nd core disabled, the battery life had increased just a little almost insignificant hours. im pretty sure that we will have this serious issue solved only if someone can put hands on another ics kernel or this leaked kernel source.
fabianowerner said:
relax dude... even with the 2nd core disabled, the battery life had increased just a little almost insignificant hours. im pretty sure that we will have this serious issue solved only if someone can put hands on another ics kernel or this leaked kernel source.
Click to expand...
Click to collapse
Yeah. Hope for the best . Released a new version. It's not automated but its even better working. The cores are managed better than the original one.
deathscream said:
Yeah. Hope for the best . Released a new version. It's not automated but its even better working. The cores are managed better than the original one.
Click to expand...
Click to collapse
I just released a new version of ICSROM with init.d support.
It might help with your automation.
upndwn4par said:
I just released a new version of ICSROM with init.d support.
It might help with your automation.
Click to expand...
Click to collapse
Perfect. I'll check it. At work now. Thanks!
deathscream said:
Perfect. I'll check it. At work now. Thanks!
Click to expand...
Click to collapse
Thank you for your support!
I'm testing the new version on AOKP (not suggested, I know ) and it seems that doesn't switch well the cores status.....I'm able to set a maximum cpu1 settings but not it doesn't really applies it.
Within my tests I can see that the 2nd core is not so much important....I can play Riptide GP and Shine Runner (heavy games??? ) plus others apps with only 1 core without any noticeable lags...so
I'd like to ask you if you can make a unique profile and cut off other settings:
cpu0 @ 1ghz max, variable
cpu1 @ 456mhz max, variable (enabled only if cpu0 is @ 1ghz more than 5/10 seconds)
screen-off: cpu0 456mhz max, cpu1 disabled.
Thanks a lot for the suggestion. I'll definitely try adding those.
Sent from my MB860 using xda premium
If disabling a core is not fetching significant battery increase in leaked rom(s) then efforts to streamline sampling would we worthless as primary issue of battery drain would not get solved.
This came as a surprise as the second core was suspected to be the mAh drainer. Maybe it could be the GPU that runs at max..
After a long amount of observation, I found out that shutting down a core isn't reducing the battery drain. There is something more to it. Thanks to upndwn4par to release icsrom 1.4.5 so that I could test my scripts... I'm still working on the battery drain issue and will let you guys know the progress soon.
Sent from my MB860 using xda premium

[MOD] Disable Powerdaemon Constraints - Allow custom governor settings to stick

This mod disables the powerdaemon constraints that prevent custom cpu governor settings from sticking. This was developed on my T210R, but should work for others.
Background:
There are 2 files in the /system/etc directory (powerdaemon.xml and powerdaemon_z3.xml) that are used to monitor various states of the system (ie. "booting", "games", "video playback"). Certain constraints are set depending on the system state. Most of these constraints are a variation of the "ondemand" or "performance" governors. These constraints adjust the min/max frequency and set control to a specific governor. This is why you can not get any cpu governor settings to stick.
What I changed:
I changed all system states to be directed to the "normal" constraint. This constraint does NOT change the selected governor and has min/max frequencies of 0/150%. This basically disables any effect the powerdaemon has. The 150% max does not mean your cpu will run at 150%, it simply allows overclocking if your kernel supports it.
In my testing, simply deleting the files or disabling the system states caused higher than normal cpu usage. It seemed to be trying to continually process information that it couldn't find. So, creating a "normal" constraint that did not limit any funtionality seemed to be the best option. The powerdaemon controller still processes everything, but has no real affect.
Installation:
Download and flash the Powerdaemon.disable.zip (with custom recovery). You may want to make a copy of your original files if you are using a different model.
If you want to restore the original xmls, just flash the Powerdaemon.restore.zip. These are from my T210R.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Flash at you own risk. I tried my best to explain what the mod does, so I take no responsibility for what you do with your Tab.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Reserved
nice
Nicely done! What settings are you running your tab with now?
Sent from my SAMSUNG-SGH-I747
hkjr said:
Nicely done! What settings are you running your tab with now?
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
To be honest, I actually use the default settings (with powerdaemon still enabled). I don't really use my Tab very much (except when I travel), so I don't worry much about battery life or performance enhancements.
With the powerdaemon still enabled, I find that I get less lag, because some of the constraints were set to change minimum frequency to a higher value than what it would normally be.
I discovered how this works back when trying to build my own kernel (with additional governors). I could never get the new governors to stick, so I started investigating and discovered the powerdaemon files. I have never really been that interested in changing governors, but I know that there are a lot of people who really like to change them. That's why I decided to put this out there. :good:
I have the t217s that doesn't have a working recovery if I copy the two files to my /system/etc and give them the proper permissions it should work right?
Sent from my SM-T217S using Tapatalk
jbyers5355 said:
I have the t217s that doesn't have a working recovery if I copy the two files to my /system/etc and give them the proper permissions it should work right?
Sent from my SM-T217S using Tapatalk
Click to expand...
Click to collapse
Theoretically, yes. Since you have a different model than what I developed it on, you may want to compare your original files to the "restore" files I provided, to make sure that everything is the same. I know the cpu is a little different with the T217. Let us know how it goes.
Well I looked in /system/etc on my t217s and did not find any powerdaemon files but I did find that if I change the governor settings that they do stick
Sent from my SM-T217S using Tapatalk
You can also simply edit the values in the default files to change cpu config without using an app to do it. The disadvantage is you might not know for certain what is and isn't supported, but I upped my minimum frequency across most system states to 624 mhz, and I switched from the default 'ondemand' governor to 'interactive.' As a result my cpu's frequency, when not in deep sleep, is usually at 624 mhz and occasionally at 1.2 Ghz and rarely at 1.012 Ghz.
I had only owned my tab for a couple days before switching the settings, so I can't provide much of a before/after case study. But I am pleased with performance and battery life is okay, on average usage with 20% screen brightness (occasionally higher) it seems I can get at least 6 hrs screen on time over the course of a day.
Does it increase performance? Game?
Sent my SM-T210 Using Tapatalk
gr9nole said:
Does it increase performance? Game?
Sent my SM-T210 Using Tapatalk
Click to expand...
Click to collapse
It only allows you to change governors and keep those settings from bring overwritten by the system.
Sent from my SCH-I605
Great work, works on T210 WiFi model.
Sir I included your Powerdaemon MOD on my SGYTT210xPerformanceUpgradePack, credits were given to you on the MOD. I cannot send private message to you, I think theres restriction.
V003 great working 4.1.2
SM-T210R cihazımdan Tapatalk kullanılarak gönderildi
@gr8nole is there a way to get this working on tab 4
zach61797 said:
@gr8nole is there a way to get this working on tab 4
Click to expand...
Click to collapse
Depends on which version you are referring to. For the Marvel based 7 in Tab, you need to delete /system/bin/phservice. At least that is what is required on 4.4.2 for the Tab 3 7 in (Marvel-based). On 4.4.2, the don't use the powerdaemon.xml's anymore.
gr8nole said:
Depends on which version you are referring to. For the Marvel based 7 in Tab, you need to delete /system/bin/phservice. At least that is what is required on 4.4.2 for the Tab 3 7 in (Marvel-based). On 4.4.2, the don't use the powerdaemon.xml's anymore.
Click to expand...
Click to collapse
I have the tab 4 8.0 t330nu. I have tried to change the speed but it never lets the speed change. I can go from ondemand or preformance bit the speed stays set i cant make it go up or down
zach61797 said:
I have the tab 4 8.0 t330nu. I have tried to change the speed but it never lets the speed change. I can go from ondemand or preformance bit the speed stays set i cant make it go up or down
Click to expand...
Click to collapse
No clue, sorry.
gr8nole said:
This mod disables the powerdaemon constraints that prevent custom cpu governor settings from sticking. This was developed on my T210R, but should work for others.
Background:
There are 2 files in the /system/etc directory (powerdaemon.xml and powerdaemon_z3.xml) that are used to monitor various states of the system (ie. "booting", "games", "video playback"). Certain constraints are set depending on the system state. Most of these constraints are a variation of the "ondemand" or "performance" governors. These constraints adjust the min/max frequency and set control to a specific governor. This is why you can not get any cpu governor settings to stick.
What I changed:
I changed all system states to be directed to the "normal" constraint. This constraint does NOT change the selected governor and has min/max frequencies of 0/150%. This basically disables any effect the powerdaemon has. The 150% max does not mean your cpu will run at 150%, it simply allows overclocking if your kernel supports it.
In my testing, simply deleting the files or disabling the system states caused higher than normal cpu usage. It seemed to be trying to continually process information that it couldn't find. So, creating a "normal" constraint that did not limit any funtionality seemed to be the best option. The powerdaemon controller still processes everything, but has no real affect.
Installation:
Download and flash the Powerdaemon.disable.zip (with custom recovery). You may want to make a copy of your original files if you are using a different model.
If you want to restore the original xmls, just flash the Powerdaemon.restore.zip. These are from my T210R.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Flash at you own risk. I tried my best to explain what the mod does, so I take no responsibility for what you do with your Tab.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Click to expand...
Click to collapse
Hi Gr8nole,
Thank you for your work on this. I have an issue with my T210R (4.4.2) the settings I make they don't stick after reboot. I used kernel adiutor, EX kernel manager, Performance tweaker.
I've flashed Powerdaemon.disable.zip
I have busybox installed, am I missing something?
Edit: I've found your suggestion about deleting /system/bin/phservice. I deleted the file, rebooted, changed to governor to lionheart. It seemed to keep the settings.
Thanks!

[09.01][Script]schedtune.boost - making pixel (and eas) even more smoother

hello guys and girls,
I am quite sure everyone knows and feels that our pixels are already super smooth. However few of us are never completely satisfied and are looking for ways to make the device even more smoother.
Some of you might be aware, that the sched governor, which is bound to eas, isn´t as customizable as the old interactive governor. This is the main reason we don´t have any scripts or tweaks touching the governor.
So I did some digging and finally found a tunable that allows the cpu to be even more aggressive. This will result (at least for me) in a tremendous effect on overall smoothness. Battery life will take only a slight or a grave hit, depending on the boost you choose. @Alcolawl you are free to do benchmarks
The schedtune.boost (s) reside in the directories /dev/stune, dev/stunde/foreground and dev/stune/background
You can apply values from 0 to 100.
When setting it to 100 your device will run constantly with all cores maxed out.
I found values from 2 to 10 to have the most efficient effect.
I am currently using a boost value of 8. Battery life is still awesome. But oh my god how smooth the device runs now.
Remember: you can also set the values higher yourself
For your convenience I made scripts that you can either put in system/etc/init.d or system/su.d. I am planning to refine and maybe add more tweaks to our pixels. So stay tuned and lets all work together. The script does not look like much, but try it before you judge.
Download links will be in the second post.
Instructions:
1. Download the desired file. sched2 means a boost value of 2 will be applied. sched6 means a boost value of 6 will be applied. I think you get the concept.
2. Extract the script from the download
3. Copy the script to either system/etc/init.d or system/su.d
4. set permissions to 0755 (rwxr-xr-x) via terminal or your preferred root explorer.
5. reboot and wait a minute (there is a sleep timer)
6. profit
7. to check if the script got applied correctly do in terminal on your phone
su
cat dev/stune/schedtune.boost
Attention:
su.d only works when you have working root via supersu from chainfire.
Credits:
google for integrating eas to our pixels
@Alcolawl for letting me use his scripts on the HTC 10 and inspiring me greatly in the process. If he did not exist I probably wouldn´t have looked into finding this
Even if androidfilehost says Google Pixel XL, the script will work just fine on the regular Pixel.
The all-in-one package has all scripts with boost values including 2,4,6,8 and 10.
Download:
https://www.androidfilehost.com/?w=files&flid=140794
09.01.2017
v1:
- decreased the default boost value for top app from 50 to 25
- foreground-app has a boost of 15
- schedtune.boost for all other activities (that are not getting categorized) is set to 10
v2:
- decreased the default boost value for top app from 50 to 25
- foreground-app has a boost of 12
- schedtune.boost for all other activities (that are not getting categorized) is set to 8
I did this when it was posted in the XL forum and it works exactly as described and so very easy to install. I dont think my Pixel has run any faster and with what seems like no battery hit at all even when running the 10 script!
Thanks for this! Everything does seem smoother. Installed the 10 one because of what Archangel said.
Nice, I'll try it out too, and report after a bit of messing around.
For the record: the default boost value is 0
Apparently a 10% boost is already the default on Pixel, at least for the top-app? https://www.linuxplumbersconf.org/2...ations/3693/original/LPC- EAS for Android.pdf
Boosting the foreground thread in addition to top-app may make sense (which this script seems to do), but I think background is best left alone.
I am having a problem when checking to see if this worked, (this directory isn't found) although I've gone in and* checked haha. With the file "schedtune.boost" could we also manually change that value?
Edit: I've change the permissions correctly and have tried it in both places with no luck. :/.
Edit2: placed the file in both locations and changed the filename to include ". rc" and it seems to be working now.
Gonna try out 8
Finally got it work. But it didn't work when I placed it in system/etc/init. Only worked when I put it in Su/su.d
Simer03 said:
Gonna try out 8
Finally got it work. But it didn't work when I placed it in system/etc/init. Only worked when I put it in Su/su.d
Click to expand...
Click to collapse
system/etc/init.d not just init
Freak07 said:
system/etc/init.d not just init
Click to expand...
Click to collapse
I'm not sure why but mine wouldn't work from init.d either. Neither of the two folders mentioned existed on my phone. So, I made an init.d folder, put the file in there and rebooted. In the end, it didn't work. So, I created the su.d folder where it was supposed to be and tried from there. That worked. Go figure.
Can anybody do the same commands for the regular pixel? I only have the XL
[email protected]:/ # cat dev/cpuset/cpus
0-3
[email protected]:/ # cat dev/cpuset/top-app/cpus
0-3
[email protected]:/ # cat dev/cpuset/foreground/cpus
0-2
[email protected]:/ # cat dev/cpuset/background/cpus
0
[email protected]:/ # cat dev/cpuset/system-background/cpus
0-2
[email protected]:/ # cat dev/cpuset/camera-daemon/cpus
0-3
[email protected]:/ #
Freak07 said:
Can anybody do the same commands for the regular pixel? I only have the XL
[email protected]:/ # cat dev/cpuset/cpus
0-3
[email protected]:/ # cat dev/cpuset/top-app/cpus
0-3
[email protected]:/ # cat dev/cpuset/foreground/cpus
0-2
[email protected]:/ # cat dev/cpuset/background/cpus
0
[email protected]:/ # cat dev/cpuset/system-background/cpus
0-2
[email protected]:/ # cat dev/cpuset/camera-daemon/cpus
0-3
[email protected]:/ #
Click to expand...
Click to collapse
I got the exam same values as you on the Pixel. Although I am running Franco kernel if that makes a difference.
ChugJugThug said:
I got the exam same values as you on the Pixel. Although I am running Franco kernel if that makes a difference.
Click to expand...
Click to collapse
Thank you. I was just curious I wonder why google decided to change this. Possibly they had enough reserves battery wise to bump performance a bit.
Freak07 said:
system/etc/init.d not just init
Click to expand...
Click to collapse
Didnt have init.d. only su.d
Yeah I think most on this phone will have that folder only,,,if you put it in su.d and change permission it will work.
Simer03 said:
Didnt have init.d. only su.d
Click to expand...
Click to collapse
Those who are using the 10, still looking good on battery? I'm on 8 currently and so far so good
OTTOREIKU said:
Those who are using the 10, still looking good on battery? I'm on 8 currently and so far so good
Click to expand...
Click to collapse
I've been using 10 since the day this was posted. Can't say I've noticed much change in the battery (if any). Battery life has been good.
robocuff said:
I've been using 10 since the day this was posted. Can't say I've noticed much change in the battery (if any). Battery life has been good.
Click to expand...
Click to collapse
Glad to hear! I'll be loading up 10 shortly. Ty!
Is anyone noticing any appreciable changes in performance using this script at 8 or 10? I've been running it on 8 and can't really see any noticeable changes in performance or battery. i'm just curious what other people are experiencing. (and yes, i checked cat on terminal and I am running on 8)
I am running 20 and only notice a slight decrease in battery but the performance boost is really noticeable. 10 is the best for a mixture of performance increase and battery.
ChugJugThug said:
Is anyone noticing any appreciable changes in performance using this script at 8 or 10? I've been running it on 8 and can't really see any noticeable changes in performance or battery. i'm just curious what other people are experiencing. (and yes, i checked cat on terminal and I am running on 8)
Click to expand...
Click to collapse

[MOD][Interactive Tunables] Excelsior Profile

Hello everyone, here I present to you a stunning profile - Excelsior - optimized for performance, less heat & stunning battery life.​
EXCELSIOR PROFILE​
Explanation & Features
Well, many of you might be using GovTuner mod or Xenon Tweaks, but you might still be expecting Stock Like Performance, so for such people here I bring to you Excelsior Profile - meticulously calculated values for the Interactive tunables. This is brought to public only after a lot of extensive testing by myself & -DM-, for the most part he did stunning battery tests & brought me proof of concept.
The main aim was to achieve stock like performance but with less heat - this was done by making use of the lower & mid-lower frequencies for most tasks without any noticeable lag, which also translates to better battery.
Results are attached below.
Now, obviously everyone might have different results according to the rom used. The above results are gained from RomAur 4.2.1 with Xposed & Greenify, and browsing, messaging, some video, few calls, 2 e-mail accounts always running with imap push, stock messaging and 3rd party messaging app also always running in background with LTE always on, on a E6853 - Z5 Premium.
Installation
Now, for people with init.d support, just copy the file under system/etc/init.d & give permissions 777.
And for those who don't have init.d, you can just add .sh extension to the file & run it with root & on boot with any script manager app.
For people who use Kernel Adiutor - Excelsior.json has been attached, you can just go to Kernel Adiutor > Profile > Import & apply it and select apply on boot.
Downloads
init.d script - https://drive.google.com/open?id=0BzzQ3ZoP3L62WEtoTzNDWWRzaEk
Kernel Auditor Profile - https://drive.google.com/open?id=0BzzQ3ZoP3L62VkFERzI4OXVtUE0
Credits
Me - obviously.
-DM- for extensive testing & results.​
Giving it a go now. Will report back with how it's been running after a few days Thanks
BTW, what theme are you using in the first 2 screenshots?
JonesWTF said:
...BTW, what theme are you using in the first 2 screenshots?
Click to expand...
Click to collapse
Those 2 are mine, status bar mod with flat style bar indicators module, the nav bar is from xstana but I moded one of the theme in the apk itself as I wanted more spacing in between icons...by doing that the touch highlights on the nav bar were off centered so I made a theme to remove those highlights on touch...
The theme apk that I made is here ---->View attachment tmp_7829-gray-dav-1306345171.apk
Now for the Excelsior mod, getting a smooth fast experience all around...great battery life, phone is cooler....the mod is use on RomAur with Zach's Kernel 2_4_7, no thermal mod added (I will test with some in future)
@Christian Fleming did an excellent job with this mod...
Over the last few days, I've had fairly identical results. Everything seem to run super smooth, too.
I had everything same with and without profile.
JonesWTF said:
Over the last few days, I've had fairly identical results. Everything seem to run super smooth, too. View attachment 4017115View attachment 4017116
Click to expand...
Click to collapse
L33Tgod said:
I had everything same with and without profile.
Click to expand...
Click to collapse
Well, if you actually read the OP - the main aim was stock like performance with less heatage, both of you I presume, use the regular Z5 with a 2900mAh battery, you're almost reaching 5 hours - pretty good for a Z5. Thank You again.
Christian Fleming said:
Well, if you actually read the OP - the main aim was stock like performance with less heatage, both of you I presume, use the regular Z5 with a 2900mAh battery, you're almost reaching 5 hours - pretty good for a Z5. Thank You again.
Click to expand...
Click to collapse
but I don't get near 6 hours like you screenshoted, hardly 4 and a half hours.
Christian Fleming said:
Now, obviously everyone might have different results according to the rom used. The above results are gained from RomAur 4.2.1 with Xposed & Greenify, and browsing, messaging, some video, few calls, 2 e-mail accounts always running with imap push, stock messaging and 3rd party messaging app also always running in background with LTE always on, on a E6853 - Z5 Premium.
Click to expand...
Click to collapse
L33Tgod said:
but I don't get near 6 hours like you screenshoted, hardly 4 and a half hours.
Click to expand...
Click to collapse
Could you not read the original post?? It's mentioned there - it depends on your usage, for my own self - I get 5 hrs & 45 mins of SOT cause of games. Try use Greenify - it helps.
Christian Fleming said:
Could you not read the original post?? It's mentioned there - it depends on your usage, for my own self - I get 5 hrs & 45 mins of SOT cause of games. Try use Greenify - it helps.
Click to expand...
Click to collapse
i have greenify combined with xposed for better results and even without games i get low SOT
anyone knows why greenify wont ask me for root? Its donated version
fixed it by disabling xposed module for greenify and than reenable it
New Version for Nougat.
*Recalculated some values.
*Less overheating.
*Better Battery.
*Balanced usage of all frequencies, the usage of frequencies above 1.2 Ghz is reserved for only tedious tasks resulting to better battery life for little cores.
*Frequent throttling of bigger cores to 1.9 Ghz reduced translating to lesser heat.
Still in testing phase.
https://drive.google.com/file/d/0BzzQ3ZoP3L62QUpkYklmdkZsQVU/view?usp=drivesdk
i copied into su.d folder.... root/su.d/
will it still work??
thanks
whalesplaho said:
i copied into su.d folder.... root/su.d/
will it still work??
thanks
Click to expand...
Click to collapse
I haven't tested with su.d, it works fine with init.d/Kernel Aduitor Init.d emulation.
You can also use script manager & set it on boot, just check the changed values in any Kernel Control app you use.
Christian Fleming said:
I haven't tested with su.d, it works fine with init.d/Kernel Aduitor Init.d emulation.
You can also use script manager & set it on boot, just check the changed values in any Kernel Control app you use.
Click to expand...
Click to collapse
im using exkernel manager.....
how do i check, just check the changed values in any Kernel Control app you use?
thanks
whalesplaho said:
im using exkernel manager.....
how do i check, just check the changed values in any Kernel Control app you use?
thanks
Click to expand...
Click to collapse
Yeah just match the values in any app & you'll be fine.
Christian Fleming said:
Yeah just match the values in any app & you'll be fine.
Click to expand...
Click to collapse
okay brov.... i ll double but check now & my settings is still same!
whalesplaho said:
okay brov.... i ll double but check now & my settings is still same!
Click to expand...
Click to collapse
If you use Script Manager, that works, & if you use Root Explorer, navigate to su.d & tap on Excelsior, open with Linux Script Handler & execute the file, this works too.
Christian Fleming said:
If you use Script Manager, that works, & if you use Root Explorer, navigate to su.d & tap on Excelsior, open with Linux Script Handler & execute the file, this works too.
Click to expand...
Click to collapse
i have applied with script manager & keep watch....
thanks
How i import the v2 to kernel adiutor? The file isn't .json (sorry if my english is bad).
Rekon.fs said:
How i import the v2 to kernel adiutor? The file isn't .json (sorry if my english is bad).
Click to expand...
Click to collapse
I haven't yet created a json for V2 yet, you can put the script in system/etc/init.d & emulate init support with Kernel Adiutor if you don't have it.

Categories

Resources