Related
I am wanting to write a script to change my UV without using Voltage Control, but I have no idea how. Could someone point me to instructions, or possibly write it for me? Thanks in advance.
sixstringsg said:
I am wanting to write a script to change my UV without using Voltage Control, but I have no idea how. Could someone point me to instructions, or possibly write it for me? Thanks in advance.
Click to expand...
Click to collapse
voltage control will write the scrpit and put it in the /system/etc/init.d directory but you need to set that directory to read/write, i use root explorer for this. you can view the script in a text editor via root explorer and you will see what it is doing if you want to mimic it.
Dani897 said:
voltage control will write the scrpit and put it in the /system/etc/init.d directory but you need to set that directory to read/write, i use root explorer for this. you can view the script in a text editor via root explorer and you will see what it is doing if you want to mimic it.
Click to expand...
Click to collapse
But isn't that just the boot settings? Or are the apply now settings there too? I'm trying to change it with tasker.
sixstringsg said:
But isn't that just the boot settings? Or are the apply now settings there too? I'm trying to change it with tasker.
Click to expand...
Click to collapse
oh, mis understood. ok then what is wrong with using voltage control?
ill look into it. not sure off the top of my head,
edit: wait what am i saying i know this. the script is the same. putting it in init.d just is a place to make the phone run it on boot. you can copy that script anywhere and edit it for alternate setting and execute it yourself.
Dani897 said:
oh, mis understood. ok then what is wrong with using voltage control?
ill look into it. not sure off the top of my head,
edit: wait what am i saying i know this. the script is the same. putting it in init.d just is a place to make the phone run it on boot. you can copy that script anywhere and edit it for alternate setting and execute it yourself.
Click to expand...
Click to collapse
Ok sweet. I want it in tasker because I cant UV as much when its plugged in without CD, so I then could lower the UV when it's plugged in, then raise when unplugged. Thank you!
Sent from my CM7 powered captivate
Well I have the script done, but now I don't know how to make tasker run it as root...
Sent from my CM7 powered captivate
there is or used to be an application called sl4a (scripting layer for android) i dont know where to get it but there is a market app called scripter that is essencially the same. if you put the script on the sd card and import it into scripter and it will give you the ability to shortcut to it, you can use taster to open the shortcut automatically under whatever situation you are changing settings or just put the shortcut on the desktop and open it like an application. you should be able to give scripter su permissions to run it. scripter is nice to have because it also adds a support for all file extensions to android. any file extension that doesnt run in another app will just be tagged as a scripter file so you can download any file type in the stock browser of send and recieve them in mms and email with the stock apps.
also i dont know much about scripting, im still learning. i understand the commands and this one is simple just echos some numbers into configuration files, but im not sure of what can be used within the script. it may be possible to add an su command at the start of the script or start each command "sudo". not sure though, if this doesn't work then scripter is definately the way to go.
after years of windows i am more comfortable with a gui that a terminal window, but i get by.
I don't see a way to create a shortcut to my script in scripter....
oh sorry i was mistaken. you can do it in launcher pro activities i thought it shows in shortcuts but i was wrong. im not sure if tasker can use launcher pro activities. let me see if there is an alternate way. did you try putting su in the script and see if that works?
Dani897 said:
oh sorry i was mistaken. you can do it in launcher pro activities i thought it shows in shortcuts but i was wrong. im not sure if tasker can use launcher pro activities. let me see if there is an alternate way. did you try putting su in the script and see if that works?
Click to expand...
Click to collapse
When I tried launcher pro activities, it force closed anyway. And I tried su once, but ill try again.
Edit: yeah, su doesnt work. And tasker doesn't return errors when something fails. I have to check voltage control to see if it worked.
Sent from my CM7 powered captivate
sorry. about that, search google for sl4a. that is what tasker expects you to have when you launch scripts anyway. that is why it wants you to have the script in /sdcard/sl4a/scripts
i would assume sl4a would work better in combinations with tasker. hope that it works! ill try to find it.
running the script from the stock file manager or some other meathods will run scripter and ask for su permissions but i have been trying it as well to see what trouble you are having and for some reason when the script is started by tasker scripter doesn't get launched. i assumed it would work because in most situations scripter acts just like sl4a but in this case i was wrong.
edit: here is sl4a http://code.google.com/p/android-scripting/
trying it now
Dani897 said:
sorry. about that, search google for sl4a. that is what tasker expects you to have when you launch scripts anyway. that is why it wants you to have the script in /sdcard/sl4a/scripts
i would assume sl4a would work better in combinations with tasker. hope that it works! ill try to find it.
running the script from the stock file manager or some other meathods will run scripter and ask for su permissions but i have been trying it as well to see what trouble you are having and for some reason when the script is started by tasker scripter doesn't get launched. i assumed it would work because in most situations scripter acts just like sl4a but in this case i was wrong.
Click to expand...
Click to collapse
Yeah, I found that app. Thanks for all the help! We'll get it eventually.
Sent from my CM7 powered captivate
not working for me. sl4a force closes. i dont know how to get it to use super user, it may need something in the script or maybe there is a super user version, or maybe it is just out dated and doesn't work in froyo. im not really sure. im about to talk to my brother who knows all about bash scripts in linux and sh scripts are similar. maybe he has an idea. unfortunately he doesn't have an android phone but if he did he would be the person to ask.
Yeah, it keeps fcing on me too... I don't know.
Sent from my CM7 powered captivate
It is working for me. I had to wait a while at first for a permission request for anonymous user data... also it could be that you already have a folder made. it gave me an error saying that it could not gain permission to add the folder to my sdcard. I think this might be because I have sdext and a2ext... maybe...
Sent from my HTC Vision using XDA Premium App
TheNewGuy said:
It is working for me. I had to wait a while at first for a permission request for anonymous user data... also it could be that you already have a folder made. it gave me an error saying that it could not gain permission to add the folder to my sdcard. I think this might be because I have sdext and a2ext... maybe...
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Is it working for you with tasker? And I already accepted the anonymous user data prompt.
Sent from my CM7 powered captivate
No clever scripter/tasker people know how?
Sent from my CM7 powered captivate
sixstringsg said:
No clever scripter/tasker people know how?
Sent from my CM7 powered captivate
Click to expand...
Click to collapse
In case anyone was wondering, you can use the script locale plugin and it works wonderfully.
Sent from my CM7 powered captivate
Since I've gotten my Sidekick, I've noticed on most ROMs a horrible tendency to not register key-presses on the physical keyboard. There was one ROM early on that didn't do this (or very little) and one of the versions of RAGE was very good. I'm running GOV3.2 Bulky right now and it's not horrible, but it's noticeable. Does anyone have an idea of what might cause this? Thanks.
ged92781 said:
Since I've gotten my Sidekick, I've noticed on most ROMs a horrible tendency to not register key-presses on the physical keyboard. There was one ROM early on that didn't do this (or very little) and one of the versions of RAGE was very good. I'm running GOV3.2 Bulky right now and it's not horrible, but it's noticeable. Does anyone have an idea of what might cause this? Thanks.
Click to expand...
Click to collapse
I thought my keyboard was going bad or i just did not press the key all the way, now im on stock and i have not had that issue, hope someone finds the rom
ultraprimeomega said:
I thought my keyboard was going bad or i just did not press the key all the way, now im on stock and i have not had that issue, hope someone finds the rom
Click to expand...
Click to collapse
I wonder what the issue is that's causing it to show up on custom ROMs. Though, I've had it on the stock ROMs as well.
Have you tried this version of the kernel? Along with the removal of the keystroke logger, it also contains a patch that allows you to lower the keystroke timer delays... If you are experiencing dropped keystrokes, this could help, as the patch was designed for tht very issue.
http://forum.xda-developers.com/showthread.php?t=1663622
yogi2010 said:
Have you tried this version of the kernel? Along with the removal of the keystroke logger, it also contains a patch that allows you to lower the keystroke timer delays... If you are experiencing dropped keystrokes, this could help, as the patch was designed for tht very issue.
http://forum.xda-developers.com/showthread.php?t=1663622
Click to expand...
Click to collapse
Thank you!!!!!!!! I went ahead and dug into that thread. I do have that kernel already on my phone. I looked at the thread linked in that thread that gives a patch to adjust the timer delay and column delay in the kernel. HOWEVER, I'm not knowledgeable enough to apply that patch to my phone as it's given. Elsewhere in that thread, someone gave the commands to edit the settings manually through a terminal which I did through Android Commander on my PC and it worked wonders! Being the suspicious type, I guessed that the settings might not keep after a reboot. Unfortunately, that is the case and I had to reapply the settings after my phone finished restarting. So, I'll have to play with this a bit more to get it to keep, but thank you for showing me this!
You're welcome! That patch was made just for this issue. And yeah, it doesn't stick after a reboot, so we could either compile the kernel with chosen settings added in, or make a simple init.d script. I never did either one lol, was too lazy to try editing and building the kernel from source, and was on the stock ROM so I thought maybe it had no init.d support. You could probably create a file with those same commands used in Terminal, and throw it in your init.d folder to change the settings at boot.
yogi2010 said:
You're welcome! That patch was made just for this issue. And yeah, it doesn't stick after a reboot, so we could either compile the kernel with chosen settings added in, or make a simple init.d script. I never did either one lol, was too lazy to try editing and building the kernel from source, and was on the stock ROM so I thought maybe it had no init.d support. You could probably create a file with those same commands used in Terminal, and throw it in your init.d folder to change the settings at boot.
Click to expand...
Click to collapse
I set my column delay to 30 and my timer delay to 1 and it now feels like I'm typing on a Sidekick again! I wouldn't know how to correctly compile the kernel myself with these settings changed. So, are there any devs out there willing to make a zip that can be flashed in CWM so these settings will become permanent?
ged92781 said:
I set my column delay to 30 and my timer delay to 1 and it now feels like I'm typing on a Sidekick again! I wouldn't know how to correctly compile the kernel myself with these settings changed. So, are there any devs out there willing to make a zip that can be flashed in CWM so these settings will become permanent?
Click to expand...
Click to collapse
+1
I've noticed this problem and thought it was just me :$
I've had this happen as well as my screen thinking I was pressing it in one location when I wasn't even touching the phone. :s Had me at my wits end.
Sent from my SGH-T839 using xda premium
To those interested in the commands I used to fix the keyboard, see below. If you reboot your phone, these settings will go away and you will need to input these commands again. For a permanent fix, someone will need to add them to a kernel that can be flashed. To use these commands, your phone must be rooted. I've successfully used Android Commander to enter these commands from my PC while my phone is connected via USB.
The current timer delay may be read with:
cat /sys/devices/platform/s3c-keypad/timer_delay
The default is 5 if I remember correctly.
A new timer delay may be set with:
echo 1 > /sys/devices/platform/s3c-keypad/timer_delay
The default 300 µs column delay value may be read with:
cat /sys/devices/platform/s3c-keypad/column_delay
A new delay may be set with:
echo 30 > /sys/devices/platform/s3c-keypad/column_delay
In either command, you may experiment with different values by changing the 1 or the 30 in either command to what you want. I believe the lowest is 1 and the max is 256 for the timer delay. If you damage your phone running these commands, that's on you. I'm just telling you what I did and feel worked for me. YMMV. Also, if you don't want to connect your rooted phone to your PC and want to use Terminal Emulator from the Play store, that will work too. You need to enter 'su' prior to running the above commands and grant the terminal super user permissions for the commands to take.
ged92781 said:
I set my column delay to 30 and my timer delay to 1 and it now feels like I'm typing on a Sidekick again! I wouldn't know how to correctly compile the kernel myself with these settings changed. So, are there any devs out there willing to make a zip that can be flashed in CWM so these settings will become permanent?
Click to expand...
Click to collapse
I'll work on it for the next releases of the Bi-Winning roms and also try to attach flashable zips.
RicAndroid said:
I'll work on it for the next releases of the Bi-Winning roms and also try to attach flashable zips.
Click to expand...
Click to collapse
Thank you!
ged92781 said:
Thank you!
Click to expand...
Click to collapse
You are very welcome! All done, BTW. Posting my updates now.
Permanent Fix(Manual way)
Taking the timer_delay and column_delay tricks shown above...I was able to make an init.d script(pretty easy, tbh) but don't feel it merits an update.zip since it's so easy. What I did was:
1. go to /etc/init.d
2. find the last script(In GOV3.3 it's 18complete) and rename it - adding one to the sequence(In my case I renamed it to 19complete)
3. make a new file name 18keyboardfix(The number depends on your rom, really...like if you renamed the above file to some thing like 33complete, you'd call this 32keyboardfix. Easy? right?)
4. Open the file you just created and put:
Code:
!#/system/bin/sh
echo 1 > /sys/devices/platform/s3c-keypad/timer_delay
echo 30 > /sys/devices/platform/s3c-keypad/column_delay
5. Set the permissions to rwxr-xr-x or whatever the numeric equivalent is. (0755, iirc)
6. Reboot
7. (Optional) Recheck the values with the following commands:
Code:
cat /sys/devices/platform/s3c-keypad/timer_delay
Code:
cat /sys/devices/platform/s3c-keypad/column_delay
I take no credit for this fix. Really, it was all ged92781 for providing the commands. All I did was find a way to make it permanent(Well, it's just reset when the devices is turned off and the init.d scripts set it back to you desired values, but that's debatable on whether it's permanent or not...either way...it works and is a simple fix)
SammaelAkuma said:
Taking the timer_delay and column_delay tricks shown above...I was able to make an init.d script(pretty easy, tbh) but don't feel it merits an update.zip since it's so easy. What I did was:
1. go to /etc/init.d
2. find the last script(In GOV3.3 it's 18complete) and rename it - adding one to the sequence(In my case I renamed it to 19complete)
3. make a new file name 18keyboardfix(The number depends on your rom, really...like if you renamed the above file to some thing like 33complete, you'd call this 32keyboardfix. Easy? right?)
4. Open the file you just created and put:
Code:
!#/system/bin/sh
echo 1 > /sys/devices/platform/s3c-keypad/timer_delay
echo 30 > /sys/devices/platform/s3c-keypad/column_delay
5. Set the permissions to rwxr-xr-x or whatever the numeric equivalent is. (0755, iirc)
6. Reboot
7. (Optional) Recheck the values with the following commands:
Code:
cat /sys/devices/platform/s3c-keypad/timer_delay
Code:
cat /sys/devices/platform/s3c-keypad/column_delay
I take no credit for this fix. Really, it was all ged92781 for providing the commands. All I did was find a way to make it permanent(Well, it's just reset when the devices is turned off and the init.d scripts set it back to you desired values, but that's debatable on whether it's permanent or not...either way...it works and is a simple fix)
Click to expand...
Click to collapse
Uh, oh....I used echo "number" /proc/sys/devices/platform/s3c-keypad in my script. Will I have to change it?
RicAndroid said:
Uh, oh....I used echo "number" /proc/sys/devices/platform/s3c-keypad in my script. Will I have to change it?
Click to expand...
Click to collapse
Idk, honestly. Try and see if your script works first, if not, then use the one I made using the commands ged92781 provided. Now...to find a way to fix the spaztic touch screen...that'll be tricky.
SammaelAkuma said:
Idk, honestly. Try and see if your script works first, if not, then use the one I made using the commands ged92781 provided. Now...to find a way to fix the spaztic touch screen...that'll be tricky.
Click to expand...
Click to collapse
I'm using your commands, dude. I'm very into details....so thanks!
RicAndroid said:
I'm using your commands, dude. I'm very into details....so thanks!
Click to expand...
Click to collapse
Lol. No problem. And good luck with the custom rom cooking.
Hello again xda, today I want to present something tiny, but nontheless important (in my view) for our old TF101 ...
The first working HOTPLUG governor for this device!
Q: What the hell is 'hotplug' ?
Hotplug Governor:
The “hotplug” governor scales CPU frequency based on load, similar to
“ondemand”. It scales up to the highest frequency when “up_threshold”
is crossed and scales down one frequency at a time when “down_threshold”
is crossed. Unlike those governors, target frequencies are determined
by directly accessing the CPUfreq frequency table, instead of taking
some percentage of maximum available frequency.
The key difference in the “hotplug” governor is that it will disable
auxillary CPUs when the system is very idle, and enable them again once
the system becomes busy. This is achieved by averaging load over
multiple sampling periods; if CPUs were online or offlined based on a
single sampling period then thrashing will occur.
Click to expand...
Click to collapse
As you can see, hotplug is able to deliver you the fastest experience and the most fps in game (kernel independant), but it also allows for completely switching off one core to save battery life. In my testings, that worked very well. I also found out, that with this governor, my TF is deep-sleeping like a baby. No governor around here (not even smartassv2 ... could deliver me this performance while maintaining a decent battery life).
Tested on EOS 4.2.1 with EOS4 kernel
But try out yourself:
NOTE: This works on any 2.X kernel available (my Harmony series, ELiTE series, KatKernel series, or any other kernel except my divemaster)
Code:
1) Download a terminal emulator (if you don't have one already)
2) Download the .ko module from [URL="https://dl.dropbox.com/u/31119007/xda/hotplug-tegra-2/cpufreq_hotplug.ko"]here[/URL]
3) Remember the path you saved the module to (or preferably move it into /system/lib/modules)
4) su
5) insmod path-to-module/cpufreq_hotplug.ko
6) Switch to 'hotplug' governor with your favourite tool.
If you were too lazy to read my instructions, this is for you ..
DOWNLOAD
As always, have fun, share, and report back!
I have followed the instructions, do I have to run it every reboot or just this one off?
Nothing really happened when I ran it but I guess it just loads the module.
Cheers buddy
Must say thanks again for all the amazing work!
pops106 said:
I have followed the instructions, do I have to run it every reboot or just this one off?
Nothing really happened when I ran it but I guess it just loads the module.
Cheers buddy
Click to expand...
Click to collapse
Ahaha figured it out, it adds the govenor so we can then change it.
Cheers
---------- Post added at 08:41 PM ---------- Previous post was at 08:36 PM ----------
pops106 said:
Ahaha figured it out, it adds the govenor so we can then change it.
Cheers
Click to expand...
Click to collapse
wouldn't wake up after putting it to sleep, had to hold power button till it rebooted then it is gone from the options.
Soz
Running eos3 and kat69
Cheers
Good work! I was trying to do this same thing the cpusleeper app but couldnt get it to work. Definitely giving this a go.
Edit: installed fine but wont survive a reboot. Any fix for e this?
Sent from my Transformer TF101 using xda premium
Got a reboot while browsing with stock browser for five minutes.
Eos81,kat kernel
The only problem as 2 people discribe abovme is RR or Random Reboot.
Thats only problem.
sounds very promising i'll try it out and report if I get any RR's.
Getting error insmod: Can't open 'path-to-module/cpufreq_hotplug.ko'
Cd to my download folder which is where it is, am I doing something wrong?
morphuex said:
sounds very promising i'll try it out and report if I get any RR's.
Getting error insmod: Can't open 'path-to-module/cpufreq_hotplug.ko'
Cd to my download folder which is where it is, am I doing something wrong?
Click to expand...
Click to collapse
path-to-module should be the path the the module.
st0nedpenguin said:
path-to-module should be the path the the module.
Click to expand...
Click to collapse
Wow I derped that up, thx lol.
Was running fine at 1.2 decided to bump it up to 1.4 hit apply and it rebooted on me, is also didn't stick after reboot like others have said.
In here you may find how to make permanent the governor insmod.
Long story short is "add a script in /system/etc/init.d , it can be something like 91modules. . Add execution permission and it can contain the same code as before. Reboot and it should load your module at boot (be sure that the path to your module is right).
Also, you can do that in one line as root in a terminal. First, be sure that your /system is mounted as rw, not ro. If you don't know how to do that, as root, in a terminal, execute:
Code:
mount -o remount,rw /system
Then:
Code:
echo -e \#\!/system/bin/sh'\n'insmod [B]/path/to/module[/B]/cpufreq_hotplug.ko > /system/etc/init.d/91modules | chmod +x /system/etc/init.d/91modules
"
It should load automatically next time you reboot.
I created the 91modules file and done the editing and file permission in ES File Manager, but the above instructions should work flawlessly.
Don't thank me for this. Thank MapleSyrup
RaymaFX, you always amaze me!:victory:
hunterval said:
RaymaFX, you always amaze me!:victory:
Click to expand...
Click to collapse
Posts like this are keeping my work up and my releases coming.
People like you are the reason I am putting this much effort in this kinda old device .
For those who experience SOD/RR with hotplug and can confirm it's not related to anything else, please gimme a dsmg/ksmg (I recommend using 'Lumberjack' from the playstore (made by Chris Trotman, EOS founder).
*NO* logcat, that isn't any useful for me in this case ..
I do now have 2 days uptime with hotplug governor, not a single SOD/RR, pretty much usage (wifi on all the time, a little Riptide GP, web browsing, most of the time playing music) and still got 20% left with EOS4 kernel while achieving full performance while needed. This thing is deep-sleeping just perfectly.
I have placed the hotplug in the system this morning and my battery life still 99% im using it with dock and dono m8 but if theres any problem but seems my tf101 dont consume energy at all im starting to get scarry lol
Sent from my Transformer TF101 using xda app-developers app
turtlemask said:
In here you may find how to make permanent the governor insmod.
Long story short is "add a script in /system/etc/init.d , it can be something like 91modules. . Add execution permission and it can contain the same code as before. Reboot and it should load your module at boot (be sure that the path to your module is right).
Also, you can do that in one line as root in a terminal. First, be sure that your /system is mounted as rw, not ro. If you don't know how to do that, as root, in a terminal, execute:
Code:
mount -o remount,rw /system
Then:
Code:
echo -e \#\!/system/bin/sh'\n'insmod [B]/path/to/module[/B]/cpufreq_hotplug.ko > /system/etc/init.d/91modules | chmod +x /system/etc/init.d/91modules
"
It should load automatically next time you reboot.
I created the 91modules file and done the editing and file permission in ES File Manager, but the above instructions should work flawlessly.
Don't thank me for this. Thank MapleSyrup
Click to expand...
Click to collapse
I typed all this in and it wont survive uve a reboot. I placed the module in /system/lib/modules and typed that. When i see the | is that a new line or all one line?
Sent from my Transformer TF101 using xda premium
You can make that code in 2 commands, 1st is all before the | and 2nd the command after the |.
In order to work your final 91modules should look like
Code:
#!/system/bin/sh
insmod /system/lib/modules/cpufreq_hotplug.ko
In order to test if it's working you cat try to run it from the terminal (it may need "su" before)
Code:
./system/etc/init.d/91modules
If it's not complaining about not being executable, you may test to see if it's loaded with "lsmod".
If it's loaded it surely will survive the reboot.
I hope that helps you.
Looks like it created the 91modules file in init.d but when i try to set permissions using chmod +x it says bad mode. Maybe thats why it isnt working, wrong permissions.
Sent from my Transformer TF101 using xda premium
Indeed the chmod +x command doesn't work.
You may use ES file explorer to set file permissions but also you need to allow it superuser access, mount /system as writable and "up to root" and mark execute and write to the user. At the end the file should have the following permissions: rwx r-- r--
Ill give that a try and see if that does it. Thanks!
thanks
Thanks RaymanFX, this is a great addition to our device.
Also thanks to all your work, you are keeping this device alive...
Hi Geeks
Somehow many people wont understand how to insatll V6 Supercharger on their Devices
So Came up A Video tutorial,expecting it would help in some way
Original Thread - [V6BlackDog]Hey Hey Launcher, sed The Way U mv, Gonna make U Fast, Gonna make U $mooth!
Thank the OP,-=zeppelinrox=- at post #11 or Here
Rules:
1.Dont call yourself a Noob and do nothing,this is just an excuse! (Words of the OP )
2.Just because you got the OP link dont ask redundant questions there,read read and if you dont get,you may ask
providing proper required files,ill tell ya! Hold on
3.If you notice i got some things wrong,well please help me if you find something
I make it for Beginners so the simple language
4.If you dont like/Undersand it,unsupercharge and move on,SIMPLE!
5.Hacking Services.jar at Post#2
Notes:
1.This Script will work on ANY Rooted Android Device,so please dont ask if it will work on my 'Bla bla bla'
2.I get all this right from the original thread after reading...
Click to expand...
Click to collapse
A Few Explainations
*You may skip these (Coz the script tells you everything,a bit more precisely)
Yet for Beginners,lets read...
1.OOM groupings and priority fixes
v6 actually groups your apps according to the priorities they are used.Like the home Launcher should always
have the highest priority,followed by the soft keyboard and so on...(Sometimes your launcher gets killled
after playing a heavy game,so thats what wont happen after setting actual priorities)
2.Low memory killer values
Linux or android defines certain values the the system Ram should should always keep free for better
functioning of your device
This script will let you set the values,say high(For gamers) or low(MultiTasking) according to your requirement
and Tests/experience
256hp,512 hp,786+(In the script) are all LMK option values you can choose from
There's also a MKF calculator that calculates OPTIMUM minfree valuse based on your device RAM
3.Detailing
This will optimize all sqlite3 databases found on your device.
Resulting in faster database access and less ram usage for smoother performance.
4.Engine Flush-O-Matic
As you use your device,your cache keeps growing and your device becomes slow
In linux RAM never remains FREE,the free ram is always used to store device cache
Flush-o-matic Cleans this cache+Useless RAM usage and allows you to have a device,again with optimum RAM
You can set the time to what this script will run,so it starts automatically in the background & works for you!
5.Fixalign
This fixes permissions of all the apps and then Zipalings them(Simulatneously!The only Script of its kind! )
This basically helps optimize all the apps and less ram consumption,thus a Faster device!
6.Wheelalignment and fix emissions
These zipaling and fix permissions,but separately
7.BulletProof Apps
There are few apps which your frequently use,so this will keep those in memory (Your choice apps)
so they are quickly accessible without them having to start each time!
-=Starter Kit=-(Recommended,not compulsory)
Always use the Latest busybox (Atleast 1.16.2 and above)
contains Recommeded busybox squite3 and zipalign binary
Watch the video in highest available quality
If the Video Thumbnail Dosent show up here's the link [How To][Video Tut] Install/Run V6 Supercharger + Patching Services.jar [1/6/2013]
Links
1.[V6BlackDog]Hey Hey Launcher, sed The Way U mv, Gonna make U Fast, Gonna make U $mooth!
2.Download Page
3.Latest Script (The Best solution for blazing fast updates )
Click to expand...
Click to collapse
This is A video tut,so DONT call it a clone of threads and updated
Will Keep Updated as well
Credits
1.Zeppelinrox(Thank him) For the SCript Of course!
2.gu5t3r (For helping me with things,when i needed a tut like this)
Click to expand...
Click to collapse
If this was helpful hit Thanx and motivate for making things simpler
Would appreciate feedback
Hacking/Patching Services.jar
Need:
The problem with SuperCharging ICS is that ICS doesn't read ADJ values from build.prop or local.prop -
they are hardcoded into services.jar!(From the OP,you see the OP tells us everything!)
Requirements:
1.Java Installed on your PC
2.Your device drivers installed on the pc
3.USB debugging mode enabled on your Device
4.Latest Ultimatic Jar Patcher Tools
Click to expand...
Click to collapse
For ROM Cooks
The files needed are in:
init.d folder
/data/*.sh
/data/V6* folder
build.prop and local.prop (if applicable).
*.rc files (init.rc, etc) are optional.
patched services.jar
Click to expand...
Click to collapse
Dont just watch and move on
Hit Thanx and motivate if things got simpler :good:
Reserve 2
^Coz We dont just Root phones for Fun
ok. 2 questions: 1. i am following along with you in the video, but i never see you activate the starter kit? should i assume you already did this? if so, how can i activate the starter kit?
i am using i9300XXEMB6, OMEGA 43.3 XXEMC3
i already put the starter kit on my INTERNAL SD CARD, and tried to run it from recovery. two times i tried to run the starter kit, it said, "installation failed". so i guess i have not activated the starter kit yet. however, i did down load smanager, and was following you along until you chose the script, and i haven't run the starter kit.
so question 2. can i run the script along with you, or do i need to wait until i run the starter kit?
stevae said:
ok. 2 questions: 1. i am following along with you in the video, but i never see you activate the starter kit? should i assume you already did this? if so, how can i activate the starter kit?
i am using i9300XXEMB6, OMEGA 43.3 XXEMC3
i already put the starter kit on my INTERNAL SD CARD, and tried to run it from recovery. two times i tried to run the starter kit, it said, "installation failed". so i guess i have not activated the starter kit yet. however, i did down load smanager, and was following you along until you chose the script, and i haven't run the starter kit.
so question 2. can i run the script along with you, or do i need to wait until i run the starter kit?
Click to expand...
Click to collapse
You are suppose to install the starter kit exactly the same way you ran the script!
It is not flashable in cwm
Unzip the starter kit,then throught script manager run the script when it again asks you to install
1.busybox(as i said it is not compulsory to install the starter kit)
If your busyboz is 1.16 or greater..you are fine without the kit
If you get errors (segmentation fault) while running fixaling and detailing u need the kit..or start with the scripts
^Coz We dont just Root phones for Fun
ok, so i figured out the starter kit, and tried to run my installation right along with your installation on the video. but mine kept getting faster or slower than yours, and so i would get off of where you were. sometimes my installation went much faster than yours, and while i was waiting for yours to catch up, it chose not to allow the choice i was waiting to find out about, so it was not installed. how can i go back and change those choices?
also, how can you tell if you are fully (100%) supercharged?
stevae said:
ok, so i figured out the starter kit, and tried to run my installation right along with your installation on the video. but mine kept getting faster or slower than yours, and so i would get off of where you were. sometimes my installation went much faster than yours, and while i was waiting for yours to catch up, it chose not to allow the choice i was waiting to find out about, so it was not installed. how can i go back and change those choices?
also, how can you tell if you are fully (100%) supercharged?
Click to expand...
Click to collapse
The script itself tell u how much supercharged u are..
Hit option 30...for changing shoices
Might wanna hit thanx
^Coz We dont just Root phones for Fun
yes of course i hit thanks for you doing this video. but i don't understand where do i hit option 30?
i didn't see what the script said about my supercharge, because it went too fast a lot of the time.
---------- Post added at 03:11 PM ---------- Previous post was at 02:26 PM ----------
i am only 50% because i didn't run ultimate jar patcher tool. but i don't understand how to run it. it says on the op to run through supercharger, but when i run supercharger it just says i haven't run it yet, and sends me back to xda page. i have it down loaded, and on my phone in both the external sdcard, and the 0sdcard (internal) so why isn't supercharger running it?
or how do i run it?
stevae said:
yes of course i hit thanks for you doing this video. but i don't understand where do i hit option 30?
i didn't see what the script said about my supercharge, because it went too fast a lot of the time.
---------- Post added at 03:11 PM ---------- Previous post was at 02:26 PM ----------
i am only 50% because i didn't run ultimate jar patcher tool. but i don't understand how to run it. it says on the op to run through supercharger, but when i run supercharger it just says i haven't run it yet, and sends me back to xda page. i have it down loaded, and on my phone in both the external sdcard, and the 0sdcard (internal) so why isn't supercharger running it?
or how do i run it?
Click to expand...
Click to collapse
To run ultimatic patcher tool,you need a
1.java installed pc
2.Latest utimatic patcher tools from the download page
3.Device connect with usb debugging enabled
then 'Extract' the tools and run the .bat file
Note*-Hacking services.jar (by ultimatic jar patcher tools is for More for multitasking and not for Gamers!)
Read the comments while you run the .bat file,it will tell ya everything
for changing options,
Do as i did in the video..
Run the script
Then you see anything like driver options?
Enter (1-34)
There u enter 30..and select scrolling speed as slow...
You might wanna hit thanx
^Coz We dont just Root phones for Fun
i have run it several times. each time it says that everything is going great. but when i finish, i am still only at 50% sc. so i posted my logs on the v6 thread, as it asked me to do. but there is no comments throughout that execution that says why my launcher is not sc, only that it isn't.
I had replied but it would be good to also note here that if, while patching, the before and after ADJs are the same, nothing is changed.
So in cases of it not working, be sure to only patch a previously unmodified services.jar.
zeppelinrox said:
I had replied but it would be good to also note here that if, while patching, the before and after ADJs are the same, nothing is changed.
So in cases of it not working, be sure to only patch a previously unmodified services.jar.
Click to expand...
Click to collapse
Right said!
i didnt get the reply,
Ahh!the messagin service sometimes behaves that way
MOst Rom makers used your Style services.jar and so the result
So,next ill make a tut for hacking services.jar and also tell people to check if everything was succesful =)
checking adjs and all
Thanx
zeppelinrox said:
I had replied but it would be good to also note here that if, while patching, the before and after ADJs are the same, nothing is changed.
So in cases of it not working, be sure to only patch a previously unmodified services.jar.
Click to expand...
Click to collapse
ok. so here would then be my next question. since it obviously did it successfully at some point for the first time, why didn't it supercharge my launcher at that point? then i would not have patched it again.
zeppelinrox said:
I had replied but it would be good to also note here that if, while patching, the before and after ADJs are the same, nothing is changed.
So in cases of it not working, be sure to only patch a previously unmodified services.jar.
Click to expand...
Click to collapse
i have searched this entire site, and there is nothing on how to find or check adj's. also, how do i choose which services.jar to patch?
ok madaditya, time for another video!!! lol!
Well I think the only tools to check ADJs for groupings are by me
Ultimatic shows them just before applying settings.
You can grab services.jar from your roms flashable zip and put it where ultimatic tells you to.
Problems happen when a rom half asses the patch to services.jar and values are not consistent in both ProcessList.smali and ActivityManagerService.smali
Anyway, I'm working on a workaround/fix so that ultimatic uses the values in PL.smali as a last resort and instead will try and get the values from AMS.smali first.
This lessens the likelihood of it not patching due to different values in the 2 smali files.
stevae said:
i have searched this entire site, and there is nothing on how to find or check adj's. also, how do i choose which services.jar to patch?
ok madaditya, time for another video!!! lol!
Click to expand...
Click to collapse
Ill need some time,got exams :-/
zeppelinrox said:
Well I think the only tools to check ADJs for groupings are by me
Ultimatic shows them just before applying settings.
You can grab services.jar from your roms flashable zip and put it where ultimatic tells you to.
Problems happen when a rom half asses the patch to services.jar and values are not consistent in both ProcessList.smali and ActivityManagerService.smali
Anyway, I'm working on a workaround/fix so that ultimatic uses the values in PL.smali as a last resort and instead will try and get the values from AMS.smali first.
This lessens the likelihood of it not patching due to different values in the 2 smali files.
Click to expand...
Click to collapse
Uummm,yup!
Coz i never came across any script that tells you the ADJ values..
Actully i gotta know everything,it be the ram lesson,sqlite optimization,how scripts work,what init.d does etc only after i Started reading for 'supdercharger'
Ha! Zep's at work!
So eagerly waiting for next update and whatever you have on your minds
With image #7! :thumbup:
^Coz We dont just Root phones for Fun
Tut For HAcking Services.jar and making launcher Super-Strong Check POst#2
Apologies for the Delay
stevae said:
ok madaditya, time for another video!!! lol!
Click to expand...
Click to collapse
stuck on bootloop.. help..
cant even restore the nanddroid backup.. says MD5 mismatch..
Mr Prize said:
stuck on bootloop.. help..
cant even restore the nanddroid backup.. says MD5 mismatch..
Click to expand...
Click to collapse
Strange!
Get Aroma FIle manager from here http://forum.xda-developers.com/showthread.php?t=1646108
1.flash it via cwm and browse to system/etc/init.d and delete all scripts there!
reboot and it should boot..
2.Try supercharging again
3.If the problem continues post the logs from data/ on to the original Supercharger thread(links in OP) thread
Note-Always make sure you use the latest scripts
Hope this helps
I can't connect my phone to charge only. It always connects as a mass storage. Get stuck at "daemon started successfully..."
It's an Xperia GO with CM10.1
arenaboy007 said:
I can't connect my phone to charge only. It always connects as a mass storage. Get stuck at "daemon started successfully..."
It's an Xperia GO with CM10.1
Click to expand...
Click to collapse
Make sure u have ADB drivers for your device installed
And try connecting using the MTP mode...
Try using both modes...
Always the 'latest scripts..
After trying various kernels I m back to stock kernel but I m not able to turn on the thermal throttling, while playing various games the temperature rises to around 75-80 and I find it pretty hot And i don't want to use any app for this.
I have tried changing the N to Y in the /sys/module/msm_thermal/parameters/enabled but the settings does not stick after the reboot.…..can some one help me with this
varuntis1993 said:
After trying various kernels I m back to stock kernel but I m not able to turn on the thermal throttling, while playing various games the temperature rises to around 75-80 and I find it pretty hot And i don't want to use any app for this.
I have tried changing the N to Y in the /sys/module/msm_thermal/parameters/enabled but the settings does not stick after the reboot.…..can some one help me with this
Click to expand...
Click to collapse
What temperature are you reffering to? Battery or CPU temperature?
CPU should throttle at ~75°C
lichti1901 said:
What temperature are you reffering to? Battery or CPU temperature?
CPU should throttle at ~75°C
Click to expand...
Click to collapse
Yea it is the cpu temperature... Earlier when I used to play games the cpu temperature won't rise above 60-62°C on stock kernel but now I see ot around the 75-77°C level and also the file stated Y.....which is now N
Hi,
You need an init.d script to set it at boot...
viking37 said:
Hi,
You need an init.d script to set it at boot...
Click to expand...
Click to collapse
I don't have any idea whats that and what it does....can u explain further
varuntis1993 said:
I don't have any idea whats that and what it does....can u explain further
Click to expand...
Click to collapse
Re,
Does your rom have init.d support? Check in /system/etc to see if you have an init.d folder.
If no, you can use this app: https://play.google.com/store/apps/details?id=com.androguide.universal.init.d&hl=fr (it works, I use it). The app will create the init.d folder and all needed to run init.d scripts.
Then create an init.d script:
Code:
#!/system/bin/sh
echo N > /sys/module/msm_thermal/parameters/enabled
Or:
Code:
echo Y > /sys/module/msm_thermal/parameters/enabled
Or see in attachment. Rename the file without the .zip extension (before editing it or move it) and put the file in /system/etc/init.d and set the correct permissions (rwxrwxrwx) then reboot.
I set it to "N", so change it to "Y".
But in my opinion the problem is elsewhere, here it's just a workaround. Which kernel did you tested?
viking37 said:
Re,
Does your rom have init.d support? Check in /system/etc to see if you have an init.d folder.
If no, you can use this app: https://play.google.com/store/apps/details?id=com.androguide.universal.init.d&hl=fr (it works, I use it). The app will create the init.d folder and all needed to run init.d scripts.
Then create an init.d script:
Code:
#!/system/bin/sh
echo N > /sys/module/msm_thermal/parameters/enabled
Or:
Code:
echo Y > /sys/module/msm_thermal/parameters/enabled
Or see in attachment. Rename the file without the .zip extension and put the file in /system/etc/init.d and set the correct permissions (rwxrwxrwx) then reboot.
But in my opinion the problem is elsewhere, here it's just a workaround. Which kernel did you tested?
Click to expand...
Click to collapse
I m on stock rom with stock kernel with xposed.....I have tried almost every kernel so can't be specific, stock kernel does not support initializing script so ultimately I have to use that app
This work around worked for the time being.....last kernel which I used was the elemental x and also its file was there in the init.d folder which it must have created it which I have deleted it now.....isn't there any other solution....will flashing back the stock files help?
.
.
I hope its something not related to bad memory
Re,
So yes no init.d support here, so yes you need to use the app above. Yes you can try to reflash the original files if you know which files... First maybe this one "thermal-engine-hh" in /system/bin.
viking37 said:
Re,
So yes no init.d support here, so yes you need to use the app above. Yes you can try to reflash the original files if you know which files...
Click to expand...
Click to collapse
I earlier did tried to flash back the system.img and the stock boot.img but it didn't help...do u think its a problem with bad memory at that sector
varuntis1993 said:
I earlier did tried to flash back the system.img and the stock boot.img but it didn't help...do u think its a problem with bad memory at that sector
Click to expand...
Click to collapse
Re,
Hum... It's weird... Are you sure that you have correctly flashed all (how have you flashed them? No errors?)?
No, I doubt there is something wrong with your memory, it's something else in my opinion... But I don't know what
viking37 said:
Re,
Hum... It's weird... Are you sure that you have correctly flashed all (how have you flashed them? No errors?)?
No, I doubt there is something wrong with your memory, it's something else in my opinion... But I don't know what
Click to expand...
Click to collapse
I flashed them with fastboot....will try again to flash them again and report u
viking37 said:
Re,
Hum... It's weird... Are you sure that you have correctly flashed all (how have you flashed them? No errors?)?
No, I doubt there is something wrong with your memory, it's something else in my opinion... But I don't know what
Click to expand...
Click to collapse
I m trying to flash it again.....it is getting failed <remote: partition table doesn't exist>
varuntis1993 said:
I m trying to flash it again.....it is getting failed <remote: partition table doesn't exist>
Click to expand...
Click to collapse
Re,
Wrong command?
Take a looke here: http://forum.xda-developers.com/showthread.php?t=2513701, maybe it could help you...
viking37 said:
Re,
Wrong command?
Take a looke here: http://forum.xda-developers.com/showthread.php?t=2513701, maybe it could help you...
Click to expand...
Click to collapse
holy ****....I had typed fastboot flash systen system.img.......errhhh wrong system spelling
varuntis1993 said:
holy ****....I had typed fastboot flash systen system.img.......errhhh wrong system spelling
Click to expand...
Click to collapse
LOL, yep there were a similar issue here: http://forum.xda-developers.com/showthread.php?p=48455422&highlight=table#post48455422.
viking37 said:
LOL, yep there were a similar issue here: http://forum.xda-developers.com/showthread.php?p=48455422&highlight=table#post48455422.
Click to expand...
Click to collapse
It is still N.. and not Y
I'm sorry but I don't understand why
It should be set to "Y" by default... Now you are full stock, right? No app that could modify the thermal management, right?
viking37 said:
I'm sorry but I don't understand why
It should be set to "Y" by default... Now you are full stock, right? No app that could modify the thermal management, right?
Click to expand...
Click to collapse
yea almost on full stock but I didn't flashed the data, recovery and the userdata.....only system, cache and boot but yea I don't have root access so any app can't affect it.....
I have installed TWRP recovery, I went into its file manager and then copied that file to my internal sd card and when I checked that file it was Y but when I checked back my sys folder it was N......i have no idea whats going on
Re,
Can you try something (you'll need root...).
Install Trickster Mod (Play Store), go to the "Specific" tab and look at the Temperature Throttle (ON or OFF?), if it's set to OFF, turn it ON then apply
Go to to /sys/module/msm_thermal/parameters/enabled and take a look if it's ok, so set to "Y".
Reboot (don't forget to tick the case "Set on boot" for "Kernel settings" in settings), check again following the path above.
If it's always set to "Y" then just uninstall Trickster Mod and check again (after reboot also and check again).
viking37 said:
Re,
Can you try something (you'll need root...).
Install Trickster Mod (Play Store), go to the "Specific" tab and look at the Temperature Throttle (ON or OFF?), if it's set to OFF, turn it ON then apply, reboot (don't forget to tick the case "Set on boot" for "Kernel settings" in settings.
Go to to see if it's ok.
Then reboot, check again following the path.
Then just unistall Trickster Mod and check again (after reboot also).
Click to expand...
Click to collapse
I did that in the morning...didn't work