Database Develop

[GUIDE] Tweak the built in task killer

UPDATE: Use Appkiller to do the same thing if you're not into the whole modding scene
Hi all.
So, I'm a new user to this part of XDA (Those HTC Hero forums have taken quite the dip lately) - received my milestone on Friday, and wow, what can I say - truly blown away from the performance I can get out of it, especially since it is getting along in it's days now too. However, I'm always hungry for as much power as possible .
Something that really shocked me though is that it doesn't seem to me that anyone has played around with the automatic internal memory killer of Android. Basically, it eliminates the need of having a task killer program running at all - allows you to have Android kill your unnecessary tasks for you. But, before I repeat an already-written informational post on this, here's the link to read up about it for yourself: How to configure Android's *internal* taskkiller.
Anyway, here's a quick guide on how to add this to your wonderful Milestone (PLEASE NOTE - THIS METHOD REQUIRES ROOT):
WARNING - Playing around with system files is always dangerous. MAKE SURE YOU DO A NANDROID BACKUP JUST IN CASE. I take no responsibility for any damage what so ever (even though there cannot really be any with this ).
This guide also requires you to know about ADB Commands - google is your best friend in this case. Right now, I'm too lazy to post a guide for that .
Well, now that the formalities are out of the way...
1) Firstly, you need to have the G.O.T Open Recovery. I'm pretty certain I don't have to go into anymore details with this step - it's posted all over the place
2) (OPTIONAL FOR SAFETY. If you don't care much for safety, you may skip this step) Start your phone up as normal (if it's off) and then run the following commands from Terminal/Command Prompt on your computer, using ADB:
Code:
adb shell
su [B][U](Look out on your phone for the Root dialog)[/U][/B]
cat /sys/module/lowmemorykiller/parameters/minfree
This should return a few values that look like this:
Code:
1536,2048,4096,5120,5632,6144
TAKE NOTE OF THESE VALUES. Although it's pretty simple to remove this if it causes problems, keep these values handy somewhere. Never hurt anyone to have another back up plan
3) Mount your SD Card so that you may access it on your computer
4) Browse to OpenRecovery/GOT/bin/boot_script on your SD Card
5) Open the file "71_overclock.sh" with a text editor or something you can use to edit the shell script.
PLEASE NOTE: THIS IS USING THE OVERCLOCKING SCRIPT FROM THE G.O.T OpenRecovery. I AM USING THIS AS IT IS USUALLY RUN AT BOOT, PROVIDING YOU HAVE OVERCLOCKED YOUR PHONE TO ANY OF THE VALUES IN THE G.O.T OVERCLOCK MENU. So, long story short, you need to have selected at least one of the overclocking settings in OpenRecovery for this to work.
6) At the bottom of the file, add the following lines of code:
Code:
echo "1536,2048,4096,5120,15360,23040" > /sys/module/lowmemorykiller/parameters/minfree
THIS IS FOR THE AGGRESSIVE MODE. You can read up yourself for your own desired values in the thread link I posted above, and replace them in the above line of code as desired.
7) Save the file and close. Turn off your phone. Boot into OpenRecovery (You should know how to do this by now).
8) Go back to the overclocking menu and reset your desired clock speed. If you haven't set one before, now's the time to select
9) Restart your phone. To test if your new values have worked, boot your phone as normal, and once it's booted, connect it to your computer again, and load up Terminal/Command Prompt once again. Then, as we did in the beginning, run the following commands:
Code:
adb shell
su [B][U](Look out on your phone for the Root dialog)[/U][/B]
cat /sys/module/lowmemorykiller/parameters/minfree
This should return your newly set values. And voila! Your phone is ready to fly. Although I haven't tested speed differences on the Milestone as such, it really helped on my hero. So, post some feedback and let me know.
-----------------------------------------------------------------------------------------
IF YOU RUN INTO ANY PROBLEMS LIKE BOOTLOOPS/STUCK BOOTS:
Bootloops/stuck boots usually happen when the phone doesn't like the modification you've added to it I have no idea how this will react on other phones. It worked 100% for mine, but if you cannot run this mod, then you can remove it by doing the following:
1) Boot back into OpenRecovery.
2) Go to the G.O.T Modding menu, and then to the Restore Menu.
3) Select to restore the mot_boot_mode file.
4) Restart your phone - this time it should start, but you might notice a drop in speed. This is normal, as we have reset the overclocking to normal.
5) Mount your SD Card again, open the file "71_overclock.sh" again with a text editor or something you can use to edit the shell script.
6) Remove the line you added previously. Save and close. Unmount the SD Card.
7) Turn your phone off and boot back into OpenRecovery. Apply your overclocking again, and reboot your phone. It should boot up fine.
8) Breathe.
----------------------------------------------------------------------------------------
I'll be updating this guide in the near future to possibly include a way of doing this without having to use any overclocking, as well as a more noob friendly version, including ADB How-to's etc. For now, the extra boost in power isn't going to hurt anyone
Credits: androcheck for his original guide on this feature.
Happy speeding,
MrP.

Great job! I will be trying this on my Milestone shortly.
Hopefully this helps with the low amount of RAM our Milestones have.

free market app called autokiller
used for a while on agressive settings , stopped using it 2 weeks ago , I dont see any diffrences at all , great guide tho !

I know - I realised that there's a market app Silly me, seeing as I've used that app on my hero before. *stupid slap*
But, I prefer things like this to be incorperated into the system files as opposed to being set by an app - just one less thing to worry about I suppose. With that said however, either way will work
MrP.

MrPadie said:
I know - I realised that there's a market app Silly me, seeing as I've used that app on my hero before. *stupid slap*
But, I prefer things like this to be incorperated into the system files as opposed to being set by an app - just one less thing to worry about I suppose. With that said however, either way will work
MrP.
Click to expand...
Click to collapse
Great thread!! I was acually thinking about this a couple of days ago, I thought it wasn't possible because we need to modify the init.rc in the boot.img to initialize it... But of course we have our mot_boot_mode that can do that

[TWEAKS][UPDATED 1/05/2011 - Flashable .zips] Performance and battery tweaks

In this thread you'll find a compilations of tweaks and settings to improve your phone's performance and battery.
It isn't a walk in the park, I'll strongly advise against trying these tweaks if you don't know what you're doing. I'm not responsible for any bricked device or any kinds of problems you may have when applying the following changes. If you don't know what you're doing then simply DON'T.
Changelog 1/05/2011:
Reverted few changes, and everything should work correctly and easily. Instructions how to delete the previous version below.
Fixed the files permissions. Now you don't have to do it manually for it to work.
Download:
Tweaks .zip
Patched libsqlite .zip:
(don't use this on andy's 2.3.3 and latest CM7 from mik 6.3 roms or you'll end in a bootloop or your phone will drain a lot of battery according to some users)
libsqlite.so
Data2ext: http://forum.xda-developers.com/showthread.php?t=1042828 (thanks ungaze).
Very important:
libsqlite.so is a patched sqlite library file to turn sync off. With that change I/O should be waaay faster during db writes and reads. It only works with 2.3.x ROMs, don't bother flashing if you're with Froyo or you'll end up with a boot loop.
Instructions:
To delete the previous versions (thanks 32bits):
If you've installed any of the previously tweaks then you'll have to roll back. You have to do the following steps (this includes every possible locations):
1. Remove /system/etc/tweaks.sh
2. Remove /system/etc/init.d/00script
3. Remove /system/etc/init.d/99a
4. Remove /system/etc/init.d/99tweaks
5. Remove /data/local.prop
6. Reboot your phone.
For the .zips:
1. Download the .zips.
2. Enter recovery.
3. Flash them.
4. Reboot.
5. Done.
Prop settings, you can add them to your build.prop or local.prop:
Code:
wifi.supplicant_scan_interval=300
windowsmgr.max_events_per_sec=260
ro.lge.proximity.delay=25
mot.proximity.delay=25
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960
ro.HOME_APP_ADJ=1
ro.mot.eri.losalert.delay=1000
video.accelerate.hw=1
ro.ril.disable.power.collapse=0
pm.sleep_mode=1
Don't forget to nand backup first in case something goes wrong. I'm not responsible for any problem from your part.
Thank you for your donation:
- Momaro
franciscofranco said:
Battery life increase for Dummies
Do you want some extra juice in your battery life? Does it seem that you lose your battery too fast? Then you came to the right
place.
Over the time I've gathered some information about our battery and while this isn't 100% proof (because all of us use the phone for different purposes)
I think it's most accurate:
The myth of having the lowest possible frequency on your CPU while it's asleep:
Having the lowest frequencies (122 or 248) set up, it's not good. Our phone doesn't change voltages while underclocking or overclocking (as far as I know overclocking
doesn't change voltages as well) so, and only talking about underclocking, having such a low frequency is bad for your phones battery and performance. For the battery
that's because it takes longer to wake up from sleep and the time that the cpu takes to scale from 122/248 to maximum instead of using it for processing power eats
your battery away. About the performance hit, well that's pretty obvious and it takes longer to idle up, so again, more battery drain.
Having read about this the last few days actually running in Performance Governor is pretty beneficial to your battery: it wakes up faster, it performs every task faster,
then it idles up faster. Yeah during "sleep" time having 122 frequency or 806 it's the same thing because it's not using its power for anything, it's just there idling.
In any case what I always suggest is TEST it up and see for yourself. If you don't want to run with Performance governor at least run with 480 minimum frequency, it really helps.
---
Why do you run with auto-sync, gps, wifi, 3G, firewalls, anti-virus, background apps killing your battery? That's bull****. Most of you complain that your battery doesn't last as long
as it should...well that's not ROMs fault, I've been running with CM7 buils since the first builds and I never, ever, ever had battery problems even when everyone complained. Why?
Because I'm careful. If you don't need auto-sync at that time, disable it...if you don't need gps, disable it and so on. I don't know why people leave this stuff on even when they are not
using them. Firewalls? That's bull**** as well along with anti-viruses. They eat up your resources for nothing. Same goes for background apps that eat it up. Google Maps = bull****. If
you used it go kill it after you're done with it. Same with Music app. Kill it after you've listened to your 1315618 songs. But DON'T use task killers. I can't repeat this enough, just
DON'T use them for your own sake. Same goes for 3G...just don't enable it all time if you're not using it.
No Live Wallpapers as well, nor 3D app drawers, these blow your battery away easily without you knowing how or why. Don't bother tuning your brightness down...you have a device, and
that's to be used. Why buying a mobile for 200€ and not using it's screen propely? It's there to be used, full brightness looks better, it's not by decreasing it down and hurting your
eyes that you'll get 21564561 more battery hours.
---
Do you want even more battery? Flash my tweaks along with local.prop. I'm running 2.3.3 without any modification except my tweaks + local.prop + libsqlite + LauncherPro as a launcher
(this is where most of the performance comes from).
So these are my "secrets". As you can see this is not really secret and I can easily run my device without charging for 1 day and a half, 2 days max with moderate usage.
AH there's something important. After flashing a ROM be sure to charge it to 100%, enter recovery and wipe battery stats, then reboot and only when the phone is up and running you then
unplug it.
Have fun reading, I laughed a lot while writting it ​​
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------
Different method to apply the tweaks. Make sure you thank ungaze for this script
Visit this thread for a completely new method to apply these tweaks: SD Tweakz
Code:
What does it do?
-mounts SD
-checks if "scriptz" folder exists
-copies scripts from "scriptz" folder to /data partition
-sets permission to scripts
-runs all the scripts
-deletes "scriptz" folder from /data partition
-unmounts SD
-done
P.S.- Everything is pretty clear, I won't be answering anything that is specifically stated above in my post or in the following ones.

in case u dont have root explorer
1. mount -t yaffs2 -o remount,rw /dev/block/mtdblock1 /system
2. echo 4096 > /sys/devices/virtual/bdi/179:0/read_ahead_kb
PS: u cud have integrated that read_ahead_kb in your script too..and dont u have to mount /system rw first ???
EDIT: found something !!! busybox has crontab ..Guess we can schedule the above script to execute like every half and hour or so !!!

franciscofranco said:
debug.sf.hw=1 // activates hardware acceleration
Click to expand...
Click to collapse
Lol . How is that and battery life or performance , even remotely equivalate ?

" ls -1 /sys/block/mtdblock* " u need to use cut and tr with it..DOesnt work
Here's My script :
mount -t yaffs2 -o remount,rw /dev/block/mtdblock1 /system
echo 4096 > /sys/devices/virtual/bdi/179:0/read_ahead_kb
for i in `ls -l /sys/block/mtdblock* | tr -s " "| cut -d " " -f 6`
do
echo "noop" > /sys/block/$i/queue/scheduler
done
echo "noop" > /sys/block/mmcblk0/queue/scheduler

Zerobarat1 said:
Lol . How is that and battery life or performance , even remotely equivalate ?
Click to expand...
Click to collapse
It increases performance and I'm sure a lot of people doesn't even remotely know how to activate HW acceleration.

sarfaraz1989 said:
" ls -1 /sys/block/mtdblock* " u need to use cut and tr with it..DOesnt work
Here's My script :
mount -t yaffs2 -o remount,rw /dev/block/mtdblock1 /system
echo 4096 > /sys/devices/virtual/bdi/179:0/read_ahead_kb
for i in `ls -l /sys/block/mtdblock* | tr -s " "| cut -d " " -f 6`
do
echo "noop" > /sys/block/$i/queue/scheduler
done
echo "noop" > /sys/block/mmcblk0/queue/scheduler
Click to expand...
Click to collapse
That's a variation, but my script works as well, been using it for a good while, but thanks anyway

sarfaraz1989 said:
in case u dont have root explorer
PS: u cud have integrated that read_ahead_kb in your script too..and dont u have to mount /system rw first ???
Click to expand...
Click to collapse
As far as I know there is no need to mount /system rw with any of those scripts, never did it before and always worked fine.

franciscofranco said:
build.prop edit:
windowsmsg.max_events_per_sec=60 // makes the ui more fluid and snappy
Click to expand...
Click to collapse
Are you sure it is not:
windowsmgr.max_events_per_sec
?

freddysam said:
Are you sure it is not:
windowsmgr.max_events_per_sec
?
Click to expand...
Click to collapse
Yes it is, it was a typo, thank you.

Some observations:
If you want to use "-1" option with ls, you'll need to use busybox's version. The stock ls doesn't support it.
The Linux sysfs file system (as mounted in /sys) is by design a read-write virtual file system. No need to do anything extra to play with it, other than be root.
These commands shouldn't be run from cron, they belong in some init script, perhaps /init.rc or other appropriate startup location.

My class 4 Kingston can achieve something like 40 mb/s with this tweak, but it may vary from card to card, this is just my experience.
Click to expand...
Click to collapse
with which benchmarking tool/app? Using SD tools but no apparent change.
@franciscofranco
sent you a PM

ungaze said:
with which benchmarking tool/app? Using SD tools but no apparent change.
@franciscofranco
sent you a PM
Click to expand...
Click to collapse
SD Tools indeed
First post updated with new tweaks.

cud somebody post differences before and after applying the patch..SOmebody benchmark 'em !!!

franciscofranco said:
SD Tools indeed
First post updated with new tweaks.
Click to expand...
Click to collapse
so we just add the new scripts from Ungaze?
and let the previous one as is....
using GScript, these folders are missing?
silly question but, do we need to create this folders?
-----------
and also, will this work in general for all android devices regardless of ROM?

franciscofranco said:
This thread contains some tweaks that I've found and tested myself to improve performance and battery of your ROM.
It isn't a walk in the park, I'll strongly advise you to try these tweaks if you don't know what you're doing. I'm not responsible for any bricked device or any kinds of problems you may have when applying the following changes, if you don't know what you're doing then simply DON'T.
build.prop edit:
wifi.supplicant_scan_interval=200 // interval of seconds that wifi scans for another networks
mot.proximity.delay=25 // proximity sensor tweak to make it more responsive
windowsmgr.max_events_per_sec=60 // makes the ui more fluid and snappy
debug.sf.hw=1 // activates hardware acceleration
System files tweaks using Root Explorer (paid app from the Market):
Change /sys/devices/virtual/bdi/179:0/read_ahead_kb value to 4096, it improves the reading speed from the SD card. My class 4 Kingston can achieve something like 40 mb/s with this tweak, but it may vary from card to card, this is just my experience.
I/O schedulers:
To check which scheduler is used:
Code:
adb shell
~ # cat /sys/block/mtdblock0/queue/scheduler
[noop] cfq // in this case noop scheduler was selected
To select a different scheduler:
Code:
adb shell
~ # echo "noop" > /sys/block/mtdblock0/queue/scheduler
// you can change the schedulers for all your blocks, which, more likely will be mtdblock1,2,3,4,5,6,7,8 and 9. then mmcblk0 for the SD card.
This settings won't last through reboots, so either you create a shell script to run it every reboot or you change then manually. Same applies when changing read_ahead_kb file, it resets on reboot.
This is the script I'm using to run every reboot to change the scheduler:
Code:
for i in `ls -1 /sys/block/mtdblock*`
do
echo “noop” > $i/queue/scheduler
done
echo “noop” > /sys/block/mmcblk0/queue/scheduler
#[b]new line[/b] echo "noop" > /sys/block/dm-0/queue/scheduler
EDIT: ungaze kindly sent me a bunch of shell scripts and after researching, modifying them, and testing I'll suggest you to run them to increase general performance:
Code:
DM=`ls -d /sys/block/dm*`;
MTD=`ls -d /sys/block/mtd*`;
LOOP=`ls -d /sys/block/loop*`;
RAM=`ls -d /sys/block/ram*`;
for j in $DM $MTD $LOOP $RAM;
do
echo 0 > $j/queue/rotational;
done
This one tells the kernel that all those devices are not "spinning disks" to it treats them as flash memory, because that's exactly what they are.
Code:
echo 0 > /proc/sys/vm/swappiness;
echo 10 > /proc/sys/vm/dirty_ratio;
echo 1000 > /proc/sys/vm/vfs_cache_pressure;
echo 4096 > /proc/sys/vm/min_free_kbytes;
These are tweaks to kernel Virtual Memory management.
Use GScript Lite from the market, it works fine.
If you want to know about the i/o schedulers I suggest you google it.
P.S.- Everything is pretty clear, I won't be answering anything that is specifically stated above in my post.
Click to expand...
Click to collapse
Thanks. any chance of making it flashable for us troglodytes...

bluviper said:
so we just add the new scripts from Ungaze?
and let the previous one as is....
using GScript, these folders are missing?
silly question but, do we need to create this folders?
-----------
and also, will this work in general for all android devices regardless of ROM?
Click to expand...
Click to collapse
Yes just add the scripts, don't need to mess with the previous ones.
If it says a directory was not been found don't worry about it, sometimes dm-0 is mounted, sometimes it is not, I still haven't found out when.

sarfaraz1989 said:
cud somebody post differences before and after applying the patch..SOmebody benchmark 'em !!!
Click to expand...
Click to collapse
You won't notice benchmark improvements, instead you'll notice it in the normal usage. Benchmark don't measure real life scenarios.

Omnichron said:
Thanks. any chance of making it flashable for us troglodytes...
Click to expand...
Click to collapse
I don't know how to do it I'm sorry.
EDIT: I'll have a loot at it.

to tell my experience, after installing the scripts, screen transitions is now snappy.
not like before that youll have to wait half a sec or something near that... now its instant and snappy, its cool to look at. returning to homescreen is abit faster now.
opening files on my ES explorer, unzipping etc etc. works faster now.
exploring and changing files on Root Explorer is quite faster than before.
im using LG Optimus P500....
so again my question goes... will this also work with other android phones under different ROMS?

bluviper said:
to tell my experience, after installing the scripts, screen transitions is now snappy.
not like before that youll have to wait half a sec or something near that... now its instant and snappy, its cool to look at. returning to homescreen is abit faster now.
opening files on my ES explorer, unzipping etc etc. works faster now.
exploring and changing files on Root Explorer is quite faster than before.
im using LG Optimus P500....
so again my question goes... will this also work with other android phones under different ROMS?
Click to expand...
Click to collapse
Awesome
It will probably work on most devices but most likely with some adjustments, nothing I can really predict unless taking a look over the phone and it's filesystems.

[HOW-TO] Enable USB Charging

This guide is to enable USB charging on your Samsung Galaxy Tab.
Requirements:
- Any rooted ROM with Pershoot's kernel
- ScriptManager (free market app)
- USB Charging Script
Procedures
- Ensure you have a rooted rom/custom rom with pershoot's kernel like task650 and PhantomHacker's In Paris rom. Download and install ScriptManager from Android Market. Download the script using the link above and store it anywhere on your tab.
- Open script manager
- Navigate to wherever you stored the script and choose it. Tick run as root and run on boot. Press run.
- If it asks for superuser/root access, please allow it.
- you're done. Press home to exit. Reboot.
Note
Please read and follow all instructions and I am not responsible if anything goes wrong. this should not damage your battery. the reason why samsung disabled usb charging is not because they were worried it would damage the battery. it is because the tab charges very slowly over usb, so they didnt want people to leave a zero battery tablet charging overnight on their pc usb to wake up and find that its only charged 50%.
The common USB connections provide 5 volts DC and between 500mAh to 1,000mAh at most whereas the main power supply provides 12 volts DC and between 1200mAh to 2400mAh. Our Samsung Galaxy Tab needs about 2,000mAh for normal charging. This mod just lets you charge using that low voltage and current from the usb anyways. It is useful for someone like me who never lets the battery drain to zero and I am almost always next to a laptop so when I am watching tv or doing something else, it is always charging.
thanks to pershoot for his kernel, developers on this forum for their excellent roms.
thanks to Giblet-dono for his help and pointers in this thread

dpakrr said:
This guide is to enable USB charging on your Samsung Galaxy Tab. Please read and follow all instructions and I am not responsible if anything goes wrong.
Requirements:
- Any ROM with Pershoot's kernel
- Samsung Mobile drivers (most of you should already have them)
- Latest Android SDK (download the zip file)
- ADB files
Procedure:
- Dont plug in your Galaxy Tab via USB yet. Make a nandroid backup just incase something goes wrong. (Boot into clockworkmod recovery -> backup and restore -> backup)
- Install the Samsung Mobile drivers
- Extract the contents of the sdk zip file onto your desktop. you should get a folder called android-sdk-windows.
- Open this folder and copy all its contents. Go to your C: drive and create a folder called androidsdk and paste the files into this folder.
- Extract the contents of the ADB files zip file you downloaded to C:\androidsdk\tools
- On your tablet, go to Settings->Applications->Development and enable USB debugging. Plug in your Galaxy Tab now.
- On your Windows computer, click on Start and type in cmd in the search bar and press enter.
- type the following and press enter after each line
cd\
cd androidsdk\tools
adb devices
- you should see a combinations of letters and numbers followed by the word device. this means that the adb can interact with your tablet.
- type in the following to enable usb charging (ensure that command prompt is still in the C:\androidsdk\tools folder). again press enter after each line.
adb shell
echo 1 > /sys/class/power_supply/battery/force_usb_charging
exit
you should now be able to charge your tablet via usb.
thanks to pershoot for his kernel, developers on this forum for their excellent roms, and a whole bunch of online guides i looked up on how to access adb lol
Click to expand...
Click to collapse
Will this work on my viewsonic gtablet as well?

hi sorry. like i said in the "requirements", for this to work you need a kernel made by a developer called pershoot. i dont know if hes made any for the viewsonic tablets. please visit his website and see if he has kernels for viewonic tablets and if he has included the option to enable usb charging on them

thats amazing, will try it as soon as possible

SamerBerjawi said:
thats amazing, will try it as soon as possible
Click to expand...
Click to collapse
thanks. let me know how you go.

I do this on tab with terminal emulator every time I reboot. No need to plug in and ADB.
Just su before echo...
Sent from my SPH-D710 using Tapatalk

halmo20 said:
I do this on tab with terminal emulator every time I reboot. No need to plug in and ADB.
Just su before echo...
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Hi thanks. If there's an easier way of ddoing this can you please tell us the steps. I did what you suggested but it says permission denied. Thanks

I have put the line in a init.d script which automatically runs on boot!
You can also use script manager (free) to make a script which does this on boot !
Goodluck!

Giblet-dono said:
I have put the line in a init.d script which automatically runs on boot!
You can also use script manager (free) to make a script which does is on boot !
Goodluck!
Click to expand...
Click to collapse
Hi thanks. So did you jjust created a script with the following line -
echo 1 > /sys/class/power_supply/battery/force_usb_charging
OK figured it out thx

Work work work, thank you bro .

uomoto said:
Work work work, thank you bro .
Click to expand...
Click to collapse
Your welcome. Are you following the old instructions or the new ones? If you follow the new instructions the usb charging is always set to on even after you restart

Giblet-dono said:
I have put the line in a init.d script which automatically runs on boot!
You can also use script manager (free) to make a script which does this on boot !
Goodluck!
Click to expand...
Click to collapse
Adding to an existing script works for me. Could not get it working for a new script. Must be missing something. Ironically I just made two cables up tonight with resistors as per other forums. Both hardware and software setups work well! Screw you Samsung
Oh and, THANK YOU for the tip. Go Blacks!

Do you leave the #!... Line in there or delete that?
Keep getting permission denied when I run it. A superhero issue?

tallgrasshawk said:
Do you leave the #!... Line in there or delete that?
Keep getting permission denied when I run it. A superhero issue?
Click to expand...
Click to collapse
Yep leave that line there. Press enter to go to the next line. Then type in
su
Press enter again. It should ask for superuser permission which requires root. Allow it root access. Now type in
echo 1 > /sys/class/power_supply/battery/force_usb_charging
And save it and follow the rest of the steps in OP

I'm not getting a su request when I'm typing the script. Getting a notification when I run it, then says su isn't found

tallgrasshawk said:
I'm not getting a su request when I'm typing the script. Getting a notification when I run it, then says su isn't found
Click to expand...
Click to collapse
Make sure of the following -
- your tablet is rooted
- you have busybox v1.18.2 or lower by downloading busybox installer from market

running in Paris, so that's taken care of.
Su gave permission now. It's just sitting there saying it's running [email protected]:/ #. should it stay like that or will it finish at some point. Thanks for the script, once I figure this out it'll be great.

tallgrasshawk said:
running in Paris, so that's taken care of.
Su gave permission now. It's just sitting there saying it's running [email protected]:/ #. should it stay like that or will it finish at some point. Thanks for the script, once I figure this out it'll be great.
Click to expand...
Click to collapse
Yep its supposed to just sit there. Once you have saved it, just press the back key and choose the file you created. Tick run as root and run on boot and click run. Again it won't do much and it will just show you a command prompt screen. Press home. It should work.
If its getting too complicated for you to follow, I just uploaded my script in the OP. just download it to your tab and run it using ScriptManager. Just tick run as root and run on boot and run it. Thats all. Dont need to type anything.

I tried it, it's working. Thanks for the mod

I'm curious about one thing regarding this mod.
Would it be possible that this can hurt the battery? I mean, what happends to the battery if it gets fed with a current and voltage that is not the current and voltage it was made for? Could that damage the cells?
I'm a computer engineering student but unfortunately we do not study much electronics, perhaps someone with deep electronics and/or chemical knowledge could write something about this? Would be awesome to know more on why/why not it can/can not harm the battery.

[Script]Swap2cache (make use of unused Memory)

i finally get it to work.
this script (if kernel support) create a swapfile on mostly unused /cache partition
-copy the script to phone
-chmod
-add it to end of hw_config.sh (or any other way of bootexecute)
have fun
inteks
update:
new version creates own loopdevice (thx to hygge)

pls guider install ??

niceee.
Does this work on rooted and locked 2.3.4 Arc ?

dubist said:
niceee.
Does this work on rooted and locked 2.3.4 Arc ?
Click to expand...
Click to collapse
sorry but you need a kernel with swap support ...

le_manhpro said:
pls guider install ??
Click to expand...
Click to collapse
the easiest way is to use i.e. rootexplorer to run the script but then you have to do it after every reboot.
maybe a good idea for testing

will it work on ray?

What's benefits we have using swap file?
Thx for answer

inteks said:
sorry but you need a kernel with swap support ...
Click to expand...
Click to collapse
So what kind of kernel, is DoomKernel support? why you dont give a sameple?

Interesting idea, I have setup swap as descriped but I had to change loop device to /dev/block/loop18 which was the only unused loop device on my mobile.
It was wierd, because all new loop devices I created was quickly reserved for the same app by the system, rather annoying. But luckily I had one unused allready available.
I will let you know how it works, how the system performance is percieved after some testing. I would think it could slow down the device, the memeory is increased but it will be on slower memory.

donghungx said:
So what kind of kernel, is DoomKernel support? why you dont give a sameple?
Click to expand...
Click to collapse
yepp, doomkernel support swap
Sent from my MT15i using Tapatalk

Hi inteks
Thanks allot for your script, it actually feels like its memory has been increased with 64MB. I have a few times experienced a slight lag when starting up memory hungry games but the homescreen no longer has to redraw when returning from the game
It is usually problematic in the Order and Chaos game to chat as the game loads the default keyboard which takes some time as it is removed from memory again as soon as you have send your message. The swap makes the keyboard stay in memory and open up instantly
I am also able to keep more applications open during normal use, I would normally have problems having mail, web and other document open at the same time.
I had to modify your script and manually create a new loop device, all loop devices from loop0 to loop38 was allready used.
# mknod -m640 /dev/block/loop50 b 7 50

hygge said:
Hi inteks
Thanks allot for your script, it actually feels like its memory has been increased with 64MB. I have a few times experienced a slight lag when starting up memory hungry games but the homescreen no longer has to redraw when returning from the game
It is usually problematic in the Order and Chaos game to chat as the game loads the default keyboard which takes some time as it is removed from memory again as soon as you have send your message. The swap makes the keyboard stay in memory and open up instantly
I am also able to keep more applications open during normal use, I would normally have problems having mail, web and other document open at the same time.
I had to modify your script and manually create a new loop device, all loop devices from loop0 to loop38 was allready used.
# mknod -m640 /dev/block/loop50 b 7 50
Click to expand...
Click to collapse
pls guider install tks

le_manhpro said:
pls guider install tks
Click to expand...
Click to collapse
Here is the script with my modifications manually creating a new loop devices. I have used loop50 as 0-38 was allready in use and it would leave some room for new loop devices.
I am using scriptmanager to either run the script manually or run it at boot.
Have marked my changes with bold
#!/system/bin/sh
if busybox [ ! -f /cache/swap/swapfile.swp ]
then
echo "Create Swapfile"
mkdir /cache/swap
busybox dd if=/dev/zero of=/cache/swap/swapfile.swp bs=1M count=64
busybox mkswap /cache/swap/swapfile.swp
busybox chmod 0600 /cache/swap/swapfile.swp
else
echo "Swapfile Exist"
fi
echo "connect loop devices"
mknod -m640 /dev/block/loop50 b 7 50
losetup /dev/block/loop50 /cache/swap/swapfile.swp
echo "use loopdev for swap"
swapon /dev/block/loop50
echo "raise swappiness 2 "
echo 90 > /proc/sys/vm/swappiness
cat /proc/sys/vm/swappiness
free

Thanks a lot for the script. What is this loop anyways?

matus201 said:
Thanks a lot for the script. What is this loop anyways?
Click to expand...
Click to collapse
It is a device driver in linux, the loop device driver is created as a block device which functions as disc device. The loop device driver are used to loop back into local imagefiles on the existing filesystem.
You then use losetup to point the loop device file towards an imagefile on the existing memory devices. In this case it is configured to point towards the new empty 64MB file that are created in the beginning of the script.
You now have a small 64MB filesystem attached that we can use as linux swap

Why not making a 128 swap file to improve even more?!
I'm a noob... So I just intested to know how it works...
Sent from my LT15i using XDA App

must this be added for your kernel to start swapping inactive applications from the RAM to the cache partition ?!
thanks man
---------- Post added at 09:30 PM ---------- Previous post was at 09:29 PM ----------
haimelf said:
Why not making a 128 swap file to improve even more?!
I'm a noob... So I just intested to know how it works...
Sent from my LT15i using XDA App
Click to expand...
Click to collapse
the cache partition is only 100mb

yes
Sent from my MT15i using Tapatalk

i heard that swap would wear the cache partition in time thus making it un-useful @ all for it's original use , i believe that cache is used for stuff like downloading apps from market !
thanks

What is "chmod" ??
Sent from my LT15i using xda premium

12/4/2017 [] war_mod [] Axon 7 (msm 8996) [] CPU, GPU, VM, RAM, IO "Tune"

************
This mod' has been updated to support AOSP only if you are running freeza's latest BEAST MODE KERNEL which contains a folder named "gnfre3" in the /system/etc directory. The methods of installation are the same. The file you are replacing for AOSP (after flashing his kernel) is /system/etc/gnfre3/war_mods.sh
So, see below for instructions. And any commands applicable to file paths for the /system/etc/init.qcom.post_boot.sh file, just change to the AOSP-specific ones above.
Make sure you download the correct variant... for both AOSP and stock ROMs, you'll have a 4 GB and 6 GB option
***************
Well, this device is a breath of fresh air? Wouldn't you guys say? 128 GB ROM, 6 GB RAM and a monster of a processor!
That being said, custom tuning for a device is always a necessity. "Canned" settings will get you by, but they are certainly never optimized for a specific device. In fact, Linux typically takes a general approach to find harmonic balance in default settings that will, for the most part, work in an acceptable manner for just about any device. There are a lot of resources available on this device, so we should utilize it in a manner appropriate to squeeze out as much battery life and performance as possible without sacrificing much of those outputs, don't you think? This is going to fix that for you.
Here is what is required of you before you begin:
1. Must be rooted
2. Must have the ZTE Axon 7 OR a device running the Snapdragon 820, as this modification is not so much device specific, but hardware specific. The important aspect being the snapdragon 820 and the RAM disk size.
3. Must have write protection disabled.
Using adb shell:
Code:
adb reboot disemmcwp
Using Linux terminal (from your phone, for example):
Code:
reboot disemmcwp
The above command can also be executed in recovery terminal.
IT IS IMPORTANT THAT YOU USE THE CORRECT VERSION (RAM), AS THIS COULD HAVE UNDESIRABLE PERFORMANCE IMPACTS OTHERWISE... however, nothing will be permanently damaged, this won't turn your device into a paperweight.
Let's begin.
Getting right to it, here's what I've done:
- modified parameters of the interactive governor, and quite extensively at that (search some of my threads if you want a little bit of a breakdown of the general approach I take)
- reconfigured input_boost parameters - disabled
- reconfigured vm parameters (again, the device has a lot of RAM resource, this will utilize it and give you a far better user experience. Basically, I've adjusted dirty_ratio and dirty_background_ratios, set swappiness value to 100, and other parameters of the virtual machine have also been adjusted, such as vfs_cache_pressure.)
- (Above) you will have as much available RAM as possible for your apps. This will reduce redraws if you are a heavy user. If you'd like to test this, reboot, and check your available RAM in the settings
- Enabled zRAM for all variants
- remapped minfree parameters for LMK (low memory killer) for 6 GB variants only
- Set scheduler to CFQ
- Tuned CFQ scheduler for flash storage devices
- Turned off core_ctl for BEAST MODE kernel.. you can enable this if you'd like, just know what you are doing. There are commented out lines of code near the bottom of my scripts to enable or disable it.
- Added an option to change GPU governor to simple_ondemand (again there is a commented out line at the bottom of each script, just remove the "#" symbol and blank spot right before the line. simple_ondemand is more power-friendly GPU governor, with a very small hit on performance
In a nutshell, that's what we're looking at here. I can guarantee you this will have a significantly positive impact on your device. Turbo time, homies.
How to install????
There are two main folders found in the unzipped package. One for the 4 GB variant, one for the 6 GB variant. Only use files from the appropriate folders for your device. Each of those two folders has 3 sub-folders: ondemand, conservative, interactive… this is where you will find the various init.qcom.post_boot.sh files
Note: magisk users, see this post https://forum.xda-developers.com/showpost.php?p=72144888&postcount=286
Easy. First, the file we are replacing is found in /system/etc... it is the "init.qcom.post_boot.sh" file - this file is basically shell scripts, which are applied at boot via this particular shell file.
All you have to do is download the zip file to your device, open up a file explorer (must have root capability) unzip the package, grab the file you want to use, navigate to the /system/etc folder with said file explorer, mount your /system as RW (read write), delete your stock "init.qcom.post_boot.sh" file, and replace it with mine.
After you've successfully done this, change the new file's permissions to rw-r--r-- (0644), and then reboot!
Or, if you are brave, you can do it manually via a terminal app and get your fingers wet... if you choose to do that, see below:
Make sure the file is located on the root of your internal sdcard in /sdcard, open your terminal app (again, must have root) and type the following commands, hitting enter after each one (be careful to pay attention to the spacing).
Code:
su
Code:
cd /
Code:
mount -o remount,rw /system
Code:
cd /system/etc
Code:
rm init.qcom.post_boot.sh
Code:
cd /sdcard
Code:
mv init.qcom.post_boot.sh /system/etc
Code:
chmod 0644 /system/etc/init.qcom.post_boot.sh
I don't want credit, don't need you to give or offer donations, this is purely for the community in the spirit of Linux ideology. All I ask is for you to hit the thanks button :good:
That's pretty much it, guys. Enjoy!
Links below
STOCK
6 GB
4 GB
AOSP (Using Latest Beast Mode Kernel with the /System/etc/gnfre3 folder present)
6 GB
4 GB

This is absolutely awesome! I have the 4GB model so I'm curious to take it for a spin once you upload. Happy to see devs cranking out goodies for this device! Thank you sir!
Sent from my ZTE A2017U using Tapatalk

dcscorpio76 said:
This is absolutely awesome! I have the 4GB model so I'm curious to take it for a spin once you upload. Happy to see devs cranking out goodies for this device! Thank you sir!
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
Gotcha, bro. Its up... check it out

warBeard_actual said:
Gotcha, bro. Its up... check it out
Click to expand...
Click to collapse
Awesome. I'm on it. I'll report back tomorrow! Thank you bro!
Sent from my ZTE A2017U using Tapatalk

warBeard_actual said:
Well, this device is a breath of fresh air? Wouldn't you guys say? 128 GB ROM, 6 GB RAM and a monster of a processor!
That being said, custom tuning for a device is always a necessity. "Canned" settings will get you by, but they are certainly never optimized for a specific device. In fact, Linux typically takes a general approach to find harmonic balance in default settings that will, for the most part, work in an acceptable manner for just about any device. There are a lot of resources available on this device, so we should utilize it in a manner appropriate to squeeze out as much battery life and performance as possible without sacrificing much of those outputs, don't you think? This is going to fix that for you.
Here is what is required of you before you begin:
1. Must be rooted
2. Must have the ZTE Axon 7 OR a device running the Snapdragon 820, as this modification is not so much device specific, but hardware specific. The important aspect being the snapdragon 820 and the RAM disk size.
IT IS IMPORTANT THAT YOU USE THE CORRECT VERSION (RAM), AS THIS COULD HAVE UNDESIRABLE PERFORMANCE IMPACTS OTHERWISE... however, nothing will be permanently damaged, this won't turn your device into a paperweight.
Let's begin.
Getting right to it, here's what I've done:
- modified parameters of the interactive governor, and quite extensively at that (search some of my threads if you want a little bit of a breakdown of the general approach I take)
- reconfigured input_boost parameters
- reconfigured vm parameters (again, the device has a lot of RAM resource, this will utilize it and give you a far better user experience)
- disabled zRAM (RAM compression, again, not needed on this device really, this mod will save you CPU cycles and power)
- remapped minfree parameters for LMK (low memory killer)
In a nutshell, that's what we're looking at here. I can guarantee you this will have a significantly positive impact on your device. Turbo time, homies.
How to install????
Easy. First, the file we are replacing is found in /system/etc... it is the "init.qcom.post_boot.sh" file - this file is basically shell scripts, which are applied at boot via this particular shell file.
All you have to do is download the file to your device, open up a file explorer (must have root capability), navigate to the /system/etc folder with said file explorer, mount your /system as RW (read write), delete your stock "init.qcom.post_boot.sh" file, and replace it with mine.
After you've successfully done this, change the new file's permissions to rw-r--r-- (0644), and then reboot!
Or, if you are brave, you can do it manually via a terminal app and get your fingers wet... if you choose to do that, see below:
Make sure the file is located on the root of your internal sdcard in /sdcard, open your terminal app (again, must have root) and type the following commands, hitting enter after each one (be careful to pay attention to the spacing).
Code:
su
Code:
cd /
Code:
mount -o remount,rw /system
Code:
cd /system/etc
Code:
rm init.qcom.post_boot.sh
Code:
cd /sdcard
Code:
mv init.qcom.post_boot.sh /system/etc
Code:
chmod 0644 /system/etc/init.qcom.post_boot.sh
I don't want credit, don't need you to give or offer donations, this is purely for the community in the spirit of Linux ideology. All I ask is for you to hit the thanks button :good:
That's pretty much it, guys. Enjoy!
6GB VARIANT
4GB VARIANT
Click to expand...
Click to collapse
This will compliment my kernel nicely bro. Thanks.

freeza said:
This will compliment my kernel nicely bro. Thanks.
Click to expand...
Click to collapse
My bro freebro over here just quoting entire OP because he literally just doesn't gaf.
I swear if you don't drop me a link tonight we're fighting to the death, bro.

Dont have the file .I have only this file init.qcom.bt.sh .Is it right?

Thank you , Getting excited about all Devs coming to this device

Kevinkuensken said:
Dont have the file .I have only this file init.qcom.bt.sh .Is it right?
Click to expand...
Click to collapse
same here

Guido83 said:
same here
Click to expand...
Click to collapse
Are either of you on LOS? If so, that could be why.

warBeard_actual said:
Are either of you on LOS? If so, that could be why.
Click to expand...
Click to collapse
Resurrection Remix

Guido83 said:
Resurrection Remix
Click to expand...
Click to collapse
Well that's why. The file doesn't exist on that build. You won't be able to use it, unfortunately.

Im on aokp

Installed via ssh.
Everything seem to work great. i didn't really see a difference till now. But i'm sure it's a good mod. Thank you

awesome! glad to see more devs on this device. also, funny line you added at the beginning of the file. thanks? i guess....

after this command "mount -o remount,rw /system", the terminal says "mount:Read-only file system"
I don't know if my unit was rooted systemless or not. does it matter?
update: nevermind post above.. i just did the steps using TWRP terminal..
Thanks OP!
BTW, will this mod affect AKT Profiles? I am using project zhana battery atm.

@warBeard_actual could it work if put on /data/local renamed as userinit.sh? Seems on LOS (and other maybe based on aosp) there is a file in /system/etc/init.d/*userinit that would run that script post boot - http://android.stackexchange.com/questions/6558/how-can-i-run-a-script-on-boot
Or this script should work only on official ROM? Thanks

I'm curious about the AKT as well. I'm also on Zhana project?
Sent from my ZTE A2017U using XDA-Developers Legacy app

Does this work on LineageOS? or only on B15(stock)?

I immediately notice snappier response from phone. Number of my apps open much more quickly