[Q] Tasker or SetCPU: Application-based CPU throttling - Droid Incredible Q&A, Help & Troubleshooting

[Q] Tasker or SetCPU: Application-based CPU throttling - Droid Incredible Q&A, Help & Troubleshooting

Hey guys, sorry if this has been covered elsewhere, I've been searching but haven't been able to find anything. If it has, I'd appreciate a link to the thread, thanks
I'm sure I'm not the first to want this, but I'd like to throttle my Droid Incredible's CPU based on the currently open application. I'd like to do it one of two ways.
The first way is perhaps by using Tasker and the Execute plugin for Locale that I have installed for Tasker. The problem is, I don't know what commands to use in order to set my CPU minimum speed, maximum speed, and scaling type (performance, ondemand, etc.). Do I need to use an external script or program to do that? Or is there something built right into Android that I can use via Terminal / the Execute plugin for Tasker?
The other method would be through a profile built into SetCPU. I know I can just email the dev of SetCPU, but I figured he's gotten the question from someone here already, and perhaps they could pass the info along. Has anyone already asked if he plans on integrating application-based profiles in the future? Or is it possible to set SetCPU's parameters through Terminal somehow?
Thanks

Great question. I've seen some clocking scripts, but haven't tried them out. Here's one link: http://forum.cyanogenmod.com/topic/595-alternative-setcpu-script/
And also, here are clockup/down scripts that I found somewhere, saved on my phone, but never actually used...
clock up:
Code:
#!/system/bin/sh
if [ "$(id -u)" == "0" ]; then
CUR=`cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq`
COUNT=30;
until [ $CUR -lt 1000000 ] || [ $COUNT -lt 1 ];
do
sleep 1;
CUR=`cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq`
COUNT=$((COUNT-1));
done;
echo 1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
else
echo -e "Getting root priveleges\n"
su<$0
fi
clock down:
Code:
#!/system/bin/sh
SPEED=200000
if [ "$(id -u)" == "0" ]; then
CUR=`cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq`
until [ $CUR -le $SPEED ];
do
sleep 1;
CUR=`cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq`
done;
echo $SPEED > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
else
echo -e "Getting root priveleges\n"
su<$0
fi
What I'd personally love to see are the action intents needed to manipulate SetCPU itself from Tasker. The only reason I haven't used the above scripts is that I worry slightly about trying to actively manipulate the CPU both through SetCPU while simultaneously through separate scripts. I worry that the two will step on each others' feet and I won't have a clear idea of what's going on with my CPU. That's why I'd like to see a solution that manipulates SetCPU itself.

chameleon131 said:
Hey guys, sorry if this has been covered elsewhere, I've been searching but haven't been able to find anything. If it has, I'd appreciate a link to the thread, thanks
I'm sure I'm not the first to want this, but I'd like to throttle my Droid Incredible's CPU based on the currently open application. I'd like to do it one of two ways.
The first way is perhaps by using Tasker and the Execute plugin for Locale that I have installed for Tasker. The problem is, I don't know what commands to use in order to set my CPU minimum speed, maximum speed, and scaling type (performance, ondemand, etc.). Do I need to use an external script or program to do that? Or is there something built right into Android that I can use via Terminal / the Execute plugin for Tasker?
The other method would be through a profile built into SetCPU. I know I can just email the dev of SetCPU, but I figured he's gotten the question from someone here already, and perhaps they could pass the info along. Has anyone already asked if he plans on integrating application-based profiles in the future? Or is it possible to set SetCPU's parameters through Terminal somehow?
Thanks
Click to expand...
Click to collapse
Have you considered a kernel that does processor throttling for you, rather than doing it yourself? King has them for AOSP and Sense ROMs. Take a look - those kernels do some amazing stuff, with little to no user input (ie settings or tasker tweaks) needed.

smtom said:
Have you considered a kernel that does processor throttling for you, rather than doing it yourself? King has them for AOSP and Sense ROMs. Take a look - those kernels do some amazing stuff, with little to no user input (ie settings or tasker tweaks) needed.
Click to expand...
Click to collapse
How does the kernel know that when I read on my phone using kindle, I really don't care how fast the page turns, but when I play a game I do care? Or maybe with angry birds, I don't care, because there's no real time component, but with Doom I do care?
How does it know that I'll get to a charger in 2 hours, so at the rate things are going, I don't need to conserve power? Or maybe that I'll get to the next charger in two days, so I need to conserve power maximally?

I wish to do this as well.

Solved!
Good news everyone! Tasker has recently added this to its very very long list of features. Kudos to the dev, and thank you for your amazing program!

chameleon131 said:
Good news everyone! Tasker has recently added this to its very very long list of features. Kudos to the dev, and thank you for your amazing program!
Click to expand...
Click to collapse
If it helps, I've had a go at setting up the CPU Profiles here
It was trial and error, so let me know what you all think!

Related

How to configure the standard kernel scheduler (CFS) to behave more like BFS

First an introduction (sorry, if this got a little long, just wanted to make clear for everybody what we are talking about).
What is a scheduler?
The scheduler is a built-in part of the Linux kernel. It is that part of the kernel which decides how the available cpu power is divided among all running processes. As the cpu can only work for one process at any given time, the scheduler is responsible to assign cpu time-slices fairly to running processes.
Because of this the scheduler (among other things) plays an essential role on how responsive a system "feels" for the user. That's because responsiveness depends among other things on the time how long it takes from user input until the cpu handles the input (i.e. until "your" task/process gets cpu-cycles).
Current state of the art:
The standard Linux kernel uses the so called "Completely Fair Scheduler" (CFS) since some time (October 2007) now and seems to be useful for most use-cases (server, desktop, smartphone..).
As you may have already heard, since August 2009 there is a new player on the field, namely the "Brain **** Scheduler" (BFS). BFS promises some better latency behaviour on smaller platforms with fewer cpu-cores and mobile devices. Altough it wasn't accepted into the official Linux kernel tree, it was used by cyanogen and also adopted by Google into the mainline Android kernel (and as we are having kernel sources now, I'm sure you will see some more BFS-enabled kernels for the Hero, too).
But back to topic:
So, what I am going to talk about applies to those of you who DON'T have a kernel with the BSF scheduler (i.e. which have the standard CFS scheduler) which should be the majority of ROMs at the moment.
Tuning the CFS scheduler:
Even it's said that BFS may be better for small devices it's also possible to configure CFS for our needs:
While searching around I learned that the behaviour of the CFS scheduler can be influenced at runtime by a few parameters. All these settings can be applied at runtime and will be gone after a reboot. So it is safe to play around a little bit.
One interesting parameter I found was "NO_NEW_FAIR_SLEEPERS". As stated by some people on the Linux kernel mailinglist :
NO_NEW_FAIR_SLEEPERS is something that will turn the scheduler into a more classic fair scheduler (like BFS is too)
Click to expand...
Click to collapse
If this is true, maybe it will let the CFS behave better optimized for small devices.
But let's try it out! Let's see if it gives us some improvements.
How to to this:
Code:
# Step 1: Mount debugfs (which is a virtual filesystem like /proc/ or /sys/)
mount -t debugfs none /sys/kernel/debug
# Step 2 (optional): Display the current scheduler flags
cat /sys/kernel/debug/sched_features
# Step 3: Set the flag NO_NEW_FAIR_SLEEPERS
echo "NO_NEW_FAIR_SLEEPERS" > /sys/kernel/debug/sched_features
# Step 4: Unmount debugfs again
umount /sys/kernel/debug
As said before: These changes are NOT PERMANENT. They will be gone after a reboot. But therefore it's safe to play around here.
Testing:
Tuning the scheduler will not give you plain speed improvements, so testing with Linpack is useless here. Instead it changes the way how the system reacts if there is a lot of multi-tasking.
So when you have changed the settings try testing around a little bit when the system is under load (like playing music while doing CPU intensive stuff or things like that) and report if it behaves better/worse than with default settings.
How to undo the setting:
Simple reboot your phone.
Or redo the steps above and replace the command in Step 3 with this one (note that the prefix "NO_" is ommited here):
Code:
echo "NEW_FAIR_SLEEPERS" > /sys/kernel/debug/sched_features
Feel free to test and share your findings!

I guess I can copy paste the lines and use GScript to run them.
Any way to make this permanent? Put something in init.d maybe?

Geochelone said:
I guess I can copy paste the lines and use GScript to run them.
Click to expand...
Click to collapse
Of course. You will find 2 scripts for gscript in the attached zip-file:
enable_CFS_tweak.sh
disable_CFS_tweak.sh
So you can simply switch for easy testing.
For those who don't know GScript: It's an app from the market to easily execute scripts on your phone. Pretty handy if you are testing things before you add them to an init-script.
Instructions:
Install "GScript Lite" from the market
Unzip the 2 scripts and place it on the sd-card into the folder gscript
Launch GScript Lite, press "Menu" -> "Add script" -> "Load file" and select the scripts you just placed into "gscript" folder.
Make sure the "Need SU?" checkbox is checked and press "Save"
Tap on the script to launch it.
Geochelone said:
Any way to make this permanent? Put something in init.d maybe?
Click to expand...
Click to collapse
Correct. You would need to place the commands into an init script, which are located in "/system/etc/init.d" on most ROMs.

Hard to test..
I underclocked my Hero to 245Mhz, started the music player, launched NeoCore benchmark and via adb launched 10 instances of "md5sum /dev/urandom".
Music still not choppy. No matter whether the tweak is enabled or disabled.
The scheduler seems too good to exploit it..
[edit]
just got a NeoCore benchmark if 02.8 FPS Yeahh, that's stresstesting..
[/edit]

is there a way to make this by default in the source?
maybe add the option to the .config file?

MaXo64 said:
is there a way to make this by default in the source?
maybe add the option to the .config file?
Click to expand...
Click to collapse
Yes, you can edit kernel/sched_features.h
and replace
Code:
SCHED_FEAT(NEW_FAIR_SLEEPERS, 1)
with
Code:
SCHED_FEAT(NEW_FAIR_SLEEPERS, 0)

thanks mate, compiling right away..

what is the test result?

Just so you guys know we are basically doing this now on the Eris... via some cool scripts:
http://forum.xda-developers.com/showthread.php?t=784089&page=7

Thanks for the tip will definitively check it out

Wow! Thanks for the tip. After reading it sparked my curiosity in the Linux kernel so I went hunting on the web for more detailed info on this particular parameter (NEW_FAIR_SLEEPERS) but I found no useful info as to what exactly it is or what it does. unfortunately, the name doesnt give too much away either (to the layman).
Anyway eventually I came across a site that a couple of other SLEEPER parameters are mentioned. and it claimed that tweaking these as well as changing the sched_latency and sched_granulairty parameters will enhance android phone performance. Again I searched for explanations of these parameters but to no avail (im obviously not very good at searching!). In the end I thought id just apply the tweaks and see what happened. and voila! the phone is the smoothest I have ever felt it!
As I said I dont know which tweak is responsible for the smoothness or if its just a combination of all three but my phone is really nice to use now. I can scroll long lists and actually see scrolling instead of a stutter from start to finish! I am running elelinux 1.8 and flykernel10a at 528MHz and its smoother than i've had it when running at > 600MHz.
I have no idea what implications the changes have on the overall performance of the phone but its smooth and not overclocked! cant be bad??
so heres the changes I applied: (from ./adb shell or terminal emulator on phone)
$ su
# mount -o remount,rw /system
# echo 'kernel.sched_latency_ns = 600000' >> /etc/sysctl.conf
# echo 'kernel.sched_min_granularity_ns = 400000' >> /etc/sysctl.conf
# echo 'kernel.sched_features = 24188' >> /etc/sysctl.conf
# mount -o remount,ro /system
# sysctl -p
kernel.sched_latency_ns = 600000
kernel.sched_min_granularity_ns = 400000
kernel.sched_features = 24188
# exit
$ exit
the 24188 parameter disables a couple of sleepers and the other two change some timings in the kernel. The changes are supposedly ONLY suitable for non-BFS kernels. but they are supposed to make the CFS kernel behave more like the BFS kernel in general.
Anyway try it and see if you want and report back if it makes your phone any better or worse. Or if there are any Linux gurus maybe you can shed more light on what these parameters actually do.

I know this thread is a little old, but I wanted to report that those settings worked great on my MyTouch Slide! I'm also overclocked/underclocked to 825/245 and using the autokiller memory optimizer, with the settings you suggest my phone is amazingly fast!
I did a little research on these settings as well, and will report back as I do some more testing to see what works best with the specs in this specific phone. At that time I will post a link to a new thread on this in the section for my specific phone.
Thanks for the great tips!

[Q] Setting CPU governor to stop music clicking?

I have a small question regarding setting a CPU Governor. I searched for a while but couldn't find any answer.
I am running AcesMod007-Lite, which has the cpu governor set to smartass. It seems to be okay, but especially when playing music it has some trouble, because it is trying to save too much battery. The music has a small click now and then. And i'm hoping changing the governor will help (if it won't please say so, then I can stop trying ).
So I want to change it to Interactive. This should be possible according to the ROM description (- Available Freqs: CPU interactive, smartass, powersave, ondemand, performance - by snq-)
What I tried to change it:
In recovery (after mounting system):
adb shell echo "interactive" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
(Here I got an error: The system can't find the specified path)
adb echo "interactive" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
(Same error)
adb pull /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor G:\
(This wrote a file with userspace? I changed it to interactive, then pushed it)
adb push G:\scaling_governor /sys/devices/system/cpu/cpu0/cpufreq/
(Upon reboot I checked it, and it was set back to smartass)
When the phone was on:
I tried thesame as in recovery, and got the same errors, only when using adb pull, the content of the file was "smartass".
Does anybody have an idea how to make this work?

I don't have Ace on my phone at the minute, but from what I remember I'm pretty sure there's a scaling script in the system/etc/init.d folder. Use root explorer or similar and long press, open with text editor, then change smartass to the governor you want.
Reboot the phone and it should now be using the one you selected, I hope

Use ondemand governor. Also had problems with music playing with smartass governor in other roms. After switching to ondemand they never occurred again.
Swyped from Oxygen with Transparent XDA App

@mick
Thanks! You were right. Now it automatically switches to ondemand (thanks MatDrOiD).
But for some reason the music still clicks . Should I increase the processor max freq for screen off, or does anybody know any other solutions?

I dont really know any other solution other than to ask, did you change both governors, screen on and screen off?
btw the screen off I use "min 128000" and "max 384000"
yes, try upping the max til the clicking stops

Yes I did changed them both.
My frequencies are for screenoff (in that same file):
SLEEP_GOVERNOR_FREQUENCY_MIN="245000"
SLEEP_GOVERNOR_FREQUENCY_MAX="384000"
So I think that should be okay.
Somewhere I read that it was an possible issue with every Sense HD ROM, because there was an error in the HTC code. Then it would be unsolvable.
I am going to try setting the min to 128, maybe that magically helps.

PerfectLight said:
Somewhere I read that it was an possible issue with every Sense HD ROM, because there was an error in the HTC code. Then it would be unsolvable.
Click to expand...
Click to collapse
I use insertcoin at the moment and don't notice it.
It might not be the cpu settings, I don't know what else is tweaked in the rom, but if there are other things then it could possibly be that, memory etc.
I'm pretty sure I read in the thread when I used Aces that installing setcpu would disable the scaling script. Maybe install it and see if your problem clears, nothing to lose

It has been solved! I now use a different build.prop, which seems optimized in some way.
The clicking is gone, and the entire phone seems more responsive .
Thanks for the great help!

[[Speed Improvements]] Brainstorming & Testing Thread!!

Hey guys,
Seems there's a lot of ways you can improve the speed of Android in general. Some seem to be snakeoil... others, work quite well and there's proof to back it up.
I'm only interested in discussing the latter .
A lot of people have helped me gather a better understanding of Android (hyc, stinebd to name a few) in addition to a lot of Google searching. I am going to compile a list of what I have done, I would like to hear what you guys have done! Most app killer apps / app control will already be addressed, so those tools need not apply... I'm looking for real, permanent fixes here without adding more apps!
I am also trying to have topics that are easy working up to advanced. Obviously the more advanced topics are going to be harder to do. You've been warned.
So here's the disclaimer.
****DISCLAIMER****
Speed is as always relative. That basically means I don't want arguments about which build is faster. I want to argue about how to make every build faster .
Also, these tips should apply to any build, any device... they are pretty generic tips, but are obviously specific to Android, with some idiosyncrasies that apply to our port that wouldn't apply to native Android devices. Some is common sense, others are real ways to tear into the system. Hope you enjoy it!
Topic 1
Difficulty Easy - Apps/Widgets
I've noticed the number of widgets i have on my screens, or the number of apps that I have installed/are running in the background to greatly effect performance, in an obviously negative way.
Once I removed all the widgets (I only have the basic analog clock widget & the Google search widget on one desktop...) this seemed to improve general speed. One minor thing to check is if apps are set to auto/background sync. Only enable the ones you really want syncing, others just check manually.
On this same topic, replacing the launcher (the stock launcher in Android, Launcher2 is quite slow) can help immensely. I like ADW, but I've used LauncherPro in the past and it is good. Zeam also seems like a good launcher. I haven't used Go Launcher EX, I've heard good and bad things about it. Use what works best for you, try 'em all!
The last thing on this topic I would like to mention is animations. Settings -> Display -> Animation -> No animations can make the phone feel quite a bit snappier, obviously at the expense of the look/feel of the OS.
Topic 2
Difficulty Easy - Controlling app 'net Access
This leads me into the next topic, DroidWall. I've noticed that blocking apps from accessing the internet has been a very good thing - it's not so much a performance booster (although it probably does provide a little bump) it's mostly about battery life. Just be warned, if you block an app that is set to background sync, it will probably have very negative effects. Only disable an app's access to the internet with DroidWall after you've checked that app's background sync feature is disabled. I have a few apps allowed in DroidWall, and the rest are blocked. You can "whitelist" everything and check apps you want to block, or "blacklist" everything and check the apps you want to allow. It's a little annoying to remember to enable/disable DroidWall (I use the DroidWall widget to enable/disable it globally) but if you do, it is much better - you have complete control over how apps access the 'net on your device. It is available on the Market.
Topic 3
Difficulty Moderate - SD cache/readahead tweaking
The only reason I'm calling this one 'moderate' is the number of choices you have for settings for this... It's basically telling the SD card how much to hold on to or... read "ahead" if you will . This was turned way up in FRX07, (from 256kb to 2048kb or 2mb...) and I think this might be the source of a lot of the complaints of 'mini-resets' if you will where the boot animation is suddenly seen after a long system hang...
So some cards will work better with a larger setting - I've heard some with spankin new C6 cards that said 3072kb or 3mb was a good setting. Others have found a sweet spot at 256kb or 1024kb (1mb).
There are two ways of doing this - you can hack the init in the rootfs and adjust the setting manually, or be lazy like me and use SD Booster (from the Market). Adjusts the same settings, and they are applied immediately!
I would like to find a "sweet spot" - a good default if you will. Can folks test out 512kb and 1024kb, see if you have any more mini-resets within Android or any other slowness, etc... Obviously this isn't a cure-all for the slowness or the mini-resets, what we're looking to do is mitigate the effects. So let's focus on that, thanks!
Topic 4
Difficulty Moderate - Overclocking
Overclocking is obviously one relatively easy way to improve the speed of Android. In your startup.txt, add a line
Code:
acpuclock.oc_freq_khz=710400
for example to overclock to 710.4mhz. How did I find this value? I actually put in 714000, but if you look at dmesg near the beginning you'll see "ACPU running at ..." - that's what clock is the actual maximum. It goes in 19.2khz increments.
Feel free to experiment with how high your phone can go, just be warned that the higher you go the potential for failure goes up as well . Phone shouldn't blow up, but it might not work correctly or at all. Rebooting and scaling it back will fix it.
Here's the full *example* startup.txt:
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2292
set KERNEL zImage
set initrd initrd.gz
set cmdline "lcd.density=240 msmvkeyb_toggle=off gsensor_axis=2,1,3 pm.sleep_mode=1 physkeyboard=rhod400 acpuclock.oc_freq_khz=710400"
boot
You can put the command anywhere in the cmdline section, just make sure it's between the quotes and at least one space between each command.
Topic 5
Difficulty Advanced - How Android Manages Memory/apps
Ok, I'm going to take two approaches to this. The first, is the full explanation on how Android manages memory.
Please feel free to read the post I originally read that inspired me to start looking at this stuff - How to configure Android's *internal* taskkiller. It was very helpful for me to grasp how Android manages applications. This is the reason why application killers are not a good thing...
If you want to do it manually, Starfox suggests:
Code:
echo "1536,3072,8192,10240,12288,20480" > /sys/module/lowmemorykiller/parameters/minfree
To try to do these commands, adb is very useful. Once you get adb shell working, then you just need to "su" (provides 'super user' privileges (root)) and put in the echo command above ^^.
I had another user (thanks icevapor) suggest this script -
[Script] V6 SuperCharger! HTK & BulletProof Launchers! The ONLY Android MEMORY FIXER!
I tried it myself, and it works very well. This thread is a little overwhelming, but the jist of it is this:
Install Script Manager (on the Market)
Run the V6 SuperCharger script. I use "Aggressive 1 Settings" (#2) and then I use the OOM Grouping Fixes & "Hard to Kill" launcher (#17)
Point Script Manager to run /data/99SuperCharger.sh to run as root & on boot. This will ensure the tweaks are reapplied after a reboot.
Topic 6
Difficulty Advanced - Managing Apps that auto-start on boot
This is one of the most annoying things in Android. When you have no apps installed, it seems very fast. Then you install apps, and you never seem to get that original speed back... Now you can!
This is kind of difficult to do, I am still getting the hang of it... but here goes. All credit goes to hyc, his original post.
The basic idea here is you run a logcat (adb logcat is easiest here, or you can use GetLogs to pull logcat...) Look in this log for "for broadcast" and find apps that start on boot. For example,
Code:
Line 41: I/ActivityManager( 1394): Start proc nextapp.systempanel for broadcast nextapp.systempanel/.monitorservice.BootReceiver: pid=1752 uid=10060 gids={3003, 1015}
Notice there are two sides of the "for broadcast". The name of the package (nextapp.systempanel) and the name of the service, "nextapp.systempanel/.monitorservice.BootReceive". I made the mistake of disabling the app (the left side). Do not do this, you want to disable the right side!
So in the shell,
Code:
pm disable nextapp.systempanel/.monitorservice.BootReceive
This will be persistent across boots, it will go with your data.img.
Obviously this was just one example of an app to disable. So long as you disable the right side (after the 'for broadcast') you shouldn't disable anything that will cause a serious problem. The apps should still work, but for example if you disable Google Voice you won't get messages until you open the app. So think about that... You disable Titanium Backup schedules.BootReceiver, the schedules for Titanium Backup (if you have any) won't run. Stuff like that. Disable calendar, you won't get calendar events... Disable clock no alarms. Get it? Good. I have been rebooting several times, and I keep checking what is set to start on boot. I'm not quite happy with it yet, but there's some things I'm leery of disabling. Just be wary, if you do disable something and don't like it - just pm enable <whatever you disabled>.
Now experiment away! The one caveat is if you do break something with pm disable (and it's serious) you might get a failure to boot. It really depends on how bad you mess up. If you make a copy of your data.img before you start making these changes, you can revert to that data.img and start back there.

Alright guys. Going to use this thread as a way to brainstorm about ways to improve the speed. Read up what I've posted, let me know if I did anything wrong... Also let me know what you guys do to improve speed!
Don't care about what build you're running, this thread isn't about what build is fastest - this is a how do I make every build faster thread.
I also realize I posted this in the Rhodium section - I want to see if there's any RAPH-specific tweaks that others should be made aware of!

Slightly off topic post
I do realize all of us are looking for ways to improve over all performance but what about a means to restore these settings or even possibly a means to run a script to apply the setting(s)? Perhaps something like XDA_UC for winomo but for Android. Or should there be something like this available already and I'm just the last person getting to the party (or not)?

R^7Z said:
I do realize all of us are looking for ways to improve over all performance but what about a means to restore these settings or even possibly a means to run a script to apply the setting(s)? Perhaps something like XDA_UC for winomo but for Android. Or should there be something like this available already and I'm just the last person getting to the party (or not)?
Click to expand...
Click to collapse
I guess you didn't read the first post... I wanted to do all this without apps.
You can find an app to tweak almost all of these things. If you read the article, there's an app to adjust the values for minfree. As for the pm disable stuff, there's an app out there but hyc said the one he found was a paid-for only app. One of those task killer apps that with the paid version has a startup manager - he didn't mention which one, but I agree with him... I'd rather just do it myself.
So the two 'advanced' topics can easily be handled with an app. I don't want to do it with apps, if you do more power to you.

Not really looking for an app but I guess my post mentioned XDA_UC. Either case, I am just looking for a way to add commands without having to redo the command for each re-run start over of XDAndroid; like the froyo.user.conf file?
I usually remove the androidapps and media folders for the initial start. Seems to really boot much faster for both of my RAPHs (100 and 110)

R^7Z said:
Not really looking for an app but I guess my post mentioned XDA_UC. Either case, I am just looking for a way to add commands without having to redo the command for each re-run start over of XDAndroid; like the froyo.user.conf file?
I usually remove the androidapps and media folders for the initial start. Seems to really boot much faster for both of my RAPHs (100 and 110)
Click to expand...
Click to collapse
...Do you put the folders back in afterwards?
The pm disable stuff is persistent, as I said. The minfree stuff, in lieu of an app I would think either putting the echo command in froyo.user.conf, or I think you would be able to make the change directly to the init.rc (or init.cfg/init.froyo.rc for our port/FRX builds). Definitely easier to just put the echo command in the user.conf file.

Correct! Either that or I compress/zip the folders (again only for the initial start/boot) and uncompress after the boot. Quite obviously, the latter would require more space but you wouldn't require a reboot, less you wanted use of the androidapps folder(drag-n-drop app/XDAndroid supported method).
That PM stuff makes my head swirl; bad enough I stare at numbers each day for about 8 hours

R^7Z said:
That PM stuff makes my head swirl; bad enough I stare at numbers each day for about 8 hours
Click to expand...
Click to collapse
Yea, it took me a while to sort it out. I'm definitely doing it correctly now, but it took a few 'oh crap' issues before I got it right. I also think I can trim it more, but I want to dedicate more time to testing it. The first batch I romped thru, I knew I didn't want things like Pandora starting at boot. You might want to take a look at it, and just look for the stuff that sticks out at first. Don't mess with it if you don't know what it does, and you'll be safe.
The issue that the pm stuff solves is having a lot of apps - a lot of these apps are designed to start on boot, whether you want them to or not. This gives power users true control over the startup of apps... It definitely helped my phone out. All of the 'tweaks' combined have helped tremendously in fact. I have been on a mission the last few days, and I've definitely narrowed down some things that really seem to make a difference on my device. There is a lot of fluff & BS around how to make a phone faster/run better, I wanted to have a thread where all the facts were laid out, without any fluff (hopefully).

cpu freq of 710400 is working well on my raph800 so far, havent noticed too much change in setting minfree but i usually keep as much programs killed as possible.
About to issue the following pm disable commands
Code:
pm disable com.android.voicedialer/.VoiceDialerReceiver
pm disable com.pandora.android/.api.bluetooth.AutoStartReceiver
pm disable com.paxmodept.palringo.android.main/com.palringo.android.integration.AndroidTaskScheduler$Receiver
pm disable com.rechild.advancedtaskkiller/.AutoStartReceiver
pm disable com.google.android.apps.maps/com.google.googlenav.friend.android.ServiceReceiver

runs fine as hell yo.

We should test out: http://forum.xda-developers.com/showthread.php?t=991276
I use it on my epic4g... I'll have to stick it on my wifes tp2.

icevapor said:
We should test out: http://forum.xda-developers.com/showthread.php?t=991276
I use it on my epic4g... I'll have to stick it on my wifes tp2.
Click to expand...
Click to collapse
Hrm. There's some interesting topics there that I haven't addressed.
Not sure that script as-is should be applied to our phones, but most of it sounds pretty good.
Wow. I am impressed with that script. Kinda wish I had found that earlier to be honest... I can pretty much remove all the minfree discussion from my post in lieu of this script .
I ran it, and everything seems fine. I already had values that were pretty similar to what he had, so I haven't really noticed a huge difference in the other things the script did, but time will tell. I'm also curious if it gets reapplied correctly on boot.
Thanks for the link tho, assuming I can get it to work well (which so far it seems to work just fine) I will integrate it into the first post and probably remove all the blather on minfree. I'll keep the links up in case people want to read it, but having this script definitely circumvents any need to understand it yourself .
Well, it seemed to work... but I need to sort out how to get it persistent across reboots.
Alrighty, got it all sorted using Script Manager.
I've updated the first post with the details on how to use this script. Thanks again icevapor!

not sure if its placebo effect (haven't been testing it long yet) but i set the following settings and it felt even faster on RAPH800 (note: only deviations from defaults are listed)
froyo.user.conf -> compcache -> cc_disksize=86
froyo.user.conf -> compcache -> cc_memlimit=58
froyo.user.conf -> custom_shells -> echo "1536,3072,8192,12288,16384,24576" > /sys/module/lowmemorykiller/parameters/minfree
startup.txt -> acpuclock.oc_freq_khz=710400

Hi,
sorry for the noob question but...how can I check if an application is set to auto/background sync? And how I can enable/disable it for a single application?
Thanks

automatic_jack said:
Hi,
sorry for the noob question but...how can I check if an application is set to auto/background sync? And how I can enable/disable it for a single application?
Thanks
Click to expand...
Click to collapse
It's all app-specific. In Google Voice for example, you hit menu, more, settings, sync & notifications - this app has two options, "background data" and "synchronize inbox". To properly sync the inbox, bg data must be enabled.
Every app is different, and not all apps have these options - or even similar options. Just poke around the apps you have in question and see what settings are available.

arrrghhh said:
It's all app-specific. In Google Voice for example, you hit menu, more, settings, sync & notifications - this app has two options, "background data" and "synchronize inbox". To properly sync the inbox, bg data must be enabled.
Every app is different, and not all apps have these options - or even similar options. Just poke around the apps you have in question and see what settings are available.
Click to expand...
Click to collapse
ah, ok...thanks for the reply

Squirrels said:
froyo.user.conf -> custom_shells -> echo "1536,3072,8192,12288,16384,24576" > /sys/module/lowmemorykiller/parameters/minfree
Click to expand...
Click to collapse
Do you have compcache enabled or disabled?

This may seem slightly askew from the current conversation but hear me out.
So far, with what builds I've made for myself, I have been able to "strip" the entire build down to just bare essentials just by removing apps from the /system/app or /data folder BEFORE installing a build.
Non-essentials for me would be:
Car Home
Google Search (same as built in search anyway)
Music (I tend to use a different player for this)
Talk
Voice Dialer
and any pre-installed apps that may come with the build.
LauncherPro plus is my launcher of choice, with eye candy enabled.
Of course this is a slightly different platform (HTC Kaiser), but should work the same way for HaReT or XAndroid builds as well. Also, some of the commands entered could be done with Terminal Emulator, giving you a POSIX terminal with "su" already enabled.
Just my $.02

Hi all,
Launcher2 and ADW are both open source so I can use them...but, who is faster?
Thanks

automatic_jack said:
Hi all,
Launcher2 and ADW are both open source so I can use them...but, who is faster?
Thanks
Click to expand...
Click to collapse
I like ADW myself. Launcher2 doesn't seem so great...
I especially like a launcher that can rotate with the phone. Plus the other options ADW provides are very nice IMHO.
Try both, use what works best for you .

[[Speed Improvements]] Brainstorming & Testing Thread!!

Alright guys. Going to use this thread as a way to brainstorm about ways to improve the speed. Read up what I've posted, let me know if I did anything wrong... Also let me know what you guys do to improve speed!
Don't care about what build you're running, this thread isn't about what build is fastest - this is a how do I make every build faster thread.
I also realize I posted this in the Rhodium section - I want to see if there's any BLAC-specific tweaks that others should be made aware of!

Thanks. Great posting. Will try some of the topics I never used (because I didn't know about them).

ThaiDai said:
Thanks. Great posting. Will try some of the topics I never used (because I didn't know about them).
Click to expand...
Click to collapse
I'm sure there are more as well... These are just the ones that I found made the most difference on my device.
I'm also curious about the minfree setting. I've only tried a few settings, they seem good. I haven't done any drastic number changing, it seems like changing these values should be done with a lot of caution and testing. There are definitely some values that should not be touched and others that can take some more fudging with numbers .

Added Topic 3 and Topic 4 to startup.txt and rootfs.img.
Just booting. Let's see if this is stable.
Software options I do not test now because I only test the new versions now. So specific app optimization only necessary when ThaiDai Android Loader and installation procedure reaches v2
Ok, boot ok, started Android (NeoFROYO build(, will tell tomorrow if stable.
If so I will use this options as standard for Blacky and I will add software like Droid firewall.
Thanks and good night

Update - I redid topic 4, feel free to re-read it.

Thanks
Enviado desde mi FROYO BLUE CWM1.9 usando Tapatalk

Hi Arrrghhh!
Can a squashfsed and odexed apk boost speed inside Android OS?

john_matrix said:
Hi Arrrghhh!
Can a squashfsed and odexed apk boost speed inside Android OS?
Click to expand...
Click to collapse
No clue. What does that have to do with the Speed Improvements thread?
I'm guessing you tried and it didn't work? What APK!?!
I guess I don't really follow your train of thought. Does sqshfs'ing and odexing an APK make it run faster...? I'm pretty new to Android in general. Never even used a native Android device .

http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/
http://forum.xda-developers.com/showthread.php?t=709630

farukb said:
http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/
http://forum.xda-developers.com/showthread.php?t=709630
Click to expand...
Click to collapse
I still don't get what that has to do with our builds. ODEX and DEODEX have nothing to do with our builds... That stuff only applies to native devices, or builds that are ported from native devices (I would think).
Perhaps I'm missing something here... please tell me if I am .

Maybe they mean something else like: oxidized or deoxidized (reduced) apps. With these modified apps you can speed up the transfer of electrons, resulting in more performance without overclocking your cpu. And more: it will not reduce your battery capacity measurable. I used it in some of the builds I tried. You will get a nice small benefit also: because of the electron transfers you will get a small induced massage in your fingers for free.

ThaiDai said:
Maybe they mean something else like: oxidized or deoxidized (reduced) apps. With these modified apps you can speed up the transfer of electrons, resulting in more performance without overclocking your cpu. And more: it will not reduce your battery capacity measurable. I used it in some of the builds I tried. You will get a nice small benefit also: because of the electron transfers you will get a small induced massage in your fingers for free.
Click to expand...
Click to collapse
LOL!
Epic.

OK. I cant get V6 SuperCharger script to work! I downloaded the script and run it but I cant find /data/99SuperCharger.sh after I run it

x12CHRIS18x said:
OK. I cant get V6 SuperCharger script to work! I downloaded the script and run it but I cant find /data/99SuperCharger.sh after I run it
Click to expand...
Click to collapse
Did you make the choices in the script, or did you just exit the script?
You have to make sure ScriptManager is running as root too. There's a setting for it. "Browse as root" - make sure that is enabled. You won't be able to see /data without browsing as root.
...You have a TouchHD? I always thought you had a RHOD, lol.

"PROJECT:PLACEBO" - For E4GT Optimization

This article is about the Android Script.
For other uses, please search Placebo; Disambiguation
Op under construction,
Should become read-able soon.
Placebo 3.0 is here! Failed, 3.0.1 may work. lmao
View attachment Placebo3.0.1.zip
Placebo3.0.1-Dropbox
Placebo3.0.1-AmazonCloud
Now supports hotplug governor !
Now makes it's own tweak directory to cut down on overhead !
Now screenstate + CPU1_ON is working better than ever !
Now generates a list of kernel default settings for governors !
SHOULD now flash onto other phones without issue !
DOWNLOAD NOW AFTER READING MORE HERE
The setup I've been using lately uses two scripts; one script that has all of the tweaks and settings, and one small script for screenstate awareness.
Here are some details about installation and use.
1) Download the zip package you intend to install.
2) Boot into recovery with your preferred method. ( I personally just type "reboot recovery" into terminal. I hate holding the buttons...)
3) Navigate to the zip you downloaded and install it.
4) Assuming all went correctly, you will have the quickest flash you've seen, with the least "blahblahblah" possible.
This is normal.
TO VERIFY: Try switching gears. Open terminal emulator and type one of the following.
( you must first type "su" and hit enter )
ondemand
peqasus
conservative
interactive
smartass
lulzactive
If it installed correctly then this will effectively switch you to another governor with optimized settings.
Enjoy.
If this didn't switch you to a new governor, chances are there was a permission or mount failure on my part.
I will be posting additional tools to assist with this part, plus I'm getting a little better at preventing these issues.
To fix it yourself, try setting a governor after typing the following into terminal emulator. (these can be copy pasted if exact)
If it isn't working due to mount; the terminal emulator solution is
busybox mount -o remount,rw rootfs /
busybox mount -o remount,rw `busybox realpath /dev/block/platform/dw_mmc/by-name/FACTORYFS` /system
If if it was a permission related failure; the terminal emulator solution is
for i in ondemand conservative pegasus lulzactive interactive smartass;do
chmod 0755 /system/xbin/$i; done
If you have a problem that neither of these fix feel free to ask me or anyone else in this thread.
Latest scripts
Please read HERE before installing Beta3.1 (technically this NOT Placebo 3 )
PlaceboBeta3.1
Placebo(HEXEN)
(1-10-13 reposted with a couple minor issues fixed)
PegasusQ and dual cpu screenstate plus an SQL settings script
Here's a temp link to placebo2.0
http://db.tt/rsb7tAmY
Here's a sort of greatest hits type of link.
There isn't really any info on them ecxept buried in the thread but I tested to make sure they were all stable
http://db.tt/5KTUtews
A special thanks to:
Hakcenter:
This guy is extremely knowledgeable; willing to help improve others' understanding; has helped me on several occasions (although makes fun in the process ) despite my noobish questions, lack of attention span, and general stubbornness when I'm told I can't do something.... despite us meeting by me posting "Why is thread in the development section" in his apps thread LMAO (sorry, man...)..
For those of you who aren't familiar with Hakcenter, he has an application that applies tweak packages. I liked it when I gave it a lot. I changed some values... but that's not the point! TRY HIS APP. thanks...
Placebo Regulars; Dude, you guys... You guys are absolutely awesome. I honestly think that this is one of the most helpful (as in users helping other users) threads I've seen anywhere on XDA.
Zeppelinrox; His V6SuperCharger was my initial inspiration and his KickAssKernelizer was my initial template... way before Placebo was born.
Calkulin - Im sure I would know nothing if not for your easy to understand scripts having piqued my interest in the first place..
Thank you, sir.
(used nothing directly, but without his contributions....you get the picture..)
TDunham; Always friendly, always helpful, always has good and practical ideas.. never (publicly) judges me too harshly for my lack of ADHD medication...
Can't thank you enough for your kindness... but I can try.
Thank you, sir.
FreeCharlesManson; Your spit-balling and insight led me to a few realizations that altered the effectiveness of Placebo exponentially.
Thank you, sir.
Scarmon; also always helpful and friendly... and makes (at least one that I know of) badass roms that I would recommend to anybody (that I like..).
Thank you, sir.
BlackCanopy...
Two of the most willing-to-help people that I have the pleasure of knowing.. I can't thank you guys enough for keeping this place together.
MiguelHogue....
Team (all of them...) Seriously I still don't know why we aren't all on Teamusxdaguys.... Can't think of anybody in any crew that hasn't been helpful at one time or another.
A word for the wise.. Watch out for that Lickarock... sharp as a tack that one is.. as soon as he buckles down and puts to practice the knowledge slash resources that he already has..
I expect good things will come of it.
Problems?
I've got far more than 99 of em... IO aint one.
j/k
hit me up.... yue noe eye luuuhh yue.
Remember!
If you help one, you have helped us all.
+Good day, sirs+
+ENJOY Placebo+

Repos
..The Pharm..
Welcome. This is a repository with a few of the Placebo1 formats.
Be careful with them, I cannot guarantee them to be universal.
Obviously, of they say Univ then there have no reports of From specific issues. Similarly, if they say TW, don't bother trying on an AOSP build.
Here are some new items for your tool chests...
Format 12 & 7 and a persistent busybox
\\________//
Enjoy
Placebo-Black
Heres a little more info
http://forum.xda-developers.com/showthread.php?p=30348571
"This IS THE DROID you're looking for!!" Come to the black side...
Placebo Black was written on and for
BLACK ROM,
by Team Rejects!! AND Team Nocturnal!!
Works on every rom its been tested on, including JB builds.
PlaceboCmX-1
Placebo Pi. Nice and balanced build.
Nice and balanced. 8/09/12
Placeboπ
DietPill revision 1 (a big hit, simple, effective)
DietPillR1
DietWifiHERE
Placebo-FHV: 8/5 (balance)
http://db.tt/wFL0qtJy
So smooth.... that...
I should call it Santana or Thomas.. Eeer something
http://db.tt/XE2DWzst
Placebo set to Ondemand (performance)
PlaceboOnDmnd
Sugar Pill was an earlier one that was very well received. Stable, simple, gets work done, son!
Crazy Pill was around the same time as Sugar Pill. Can't remember much, except I think I was still adding transitions animations.
There's your warning.
View attachment dietpill-FHI.zip
View attachment SugarPill.zip
View attachment PlaceboFGXVII.zip
View attachment PlaceboFGXXII.zip
View attachment CrazyPill.zip
View attachment PlaceboFGXXVI.zip
View attachment PlaceboFGXX.zip
View attachment ServicesOptAOSKCMP9.zip
View attachment ServicesOptTouchWiz.zip
Check out my new JB compatible Odex Station
#
# RECOMMENDED: PHAKE_SETTINGS
#
dalvik.vm.heapstartsize=12m
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.heapsize=192m
ril.hsxpa=2
ril.gprsclass=['dc 10 mul 4 sub 10';]
ril.hsdpa.category=['dc 8 mul 4 sub 8']
ril.hsupa.category=6\2
windowsmgr.max_events_per_sec=< >
debug.gr.swapinterval=0
RLIMIT_NICE 1
HOME_APP_ADJ -5
HOME_APP_MEM 5688
VISIBLE_APP_ADJ 1
VISIBLE_APP_MEM 11366
#
#

Thank you, you have clearly put allot of time into this... Im gonna check this out.
Sent from my SPH-D710 using xda premium

lolwut

Thank you ! 1st page.

What other scripts have you tested with this master piece?...Is it known to bump heads with any other scripts?
Sent from my SPH-D710

Placebo; Defined
A good reference for governors, definitions of their settings, extweaks, io schedulers, and a whole lot of other things.. can be found
Here, and thank OP of this thread if you like their info
Frequent Questions
My head hurts???
Click to expand...
Click to collapse
So, wait,... what does it do?
Click to expand...
Click to collapse
Here's a little info I prepared about the virtual memory aspect.. this is not complete.. and it's my half assed interpretation...
-------------------Virtual Memory------------------
dirty_background_ratio (threshold at which background data becomes 'dirtyable'
dirty_ratio (threshold at which data becomes 'dirtyable'
dirty_expire_centisecs (time, in hundredths of seconds, before dirty data expires
dirty_writeback_centisecs (time, in hundredths of seconds, before old data is allowed to be written by PDflush Daemons ( a value of ZERO disables flush, out of fear I haven't tried this.
drop_caches (self explained, but the values are | 1=PageCache; 2=InodeCache; 3=both
highmem_is_dirtyable (I don't fully understand this, but my take is it can prevent random/unnecessary I/O within known/mapped files
laptop_mode (determines the time, in seconds, between "disk" I/O and a flush of all dirty data
lowmem_reserve_ratio (ratio of total pages-to-free-pages for each memory zone
min_free_kbytes (this number is used to compute a pages_min value for each lowmem zone
How do I know which configuration is right for me???
Click to expand...
Click to collapse
- Well, that's the real point... you actually have to get your hands dirty here. No way around it.
Is it safe to flash this on ONEROM that is identical to ANOTHEROM?
Click to expand...
Click to collapse
Which one is the best one
Click to expand...
Click to collapse
Well,,, let's start from when you were 3. Go over in detail every decision you've ever made so I can graph what you will like best.

Have no idea how to use this but clearly you put in a lot of effort and it shows (look at the Quadrant! ). Thank you for your contribution and I believe this should go in the Development Section aswell

Lol i have no idea what im doing.. I unzipped it and put it in system bin folder n tried to run it in term emu and got log error so created a log in data log and it did something and log is full of garble but i know im doing it wrong. It was worth a try wish i had some instruction so i could get those scores! Mines under 3000
Sent from my SPH-D710 using XDA

Wish I could figure out how to use this lol, thanks for you hard work! :good:

Placebo:
It's hard to summarize Placebo quickly and in an easy to understand way.
Placebo is a script, or set of scripts, that changes Linux kernel settings in your Android.
It is hard to stay caught up, because the number of potential combinations is almost without limit,
and placebo is constantly changing as I learn/dabble with new/existing modifications.
Some will be for better battery (though all will probably help a little), some will be to make your phone
scream louder than Jenna J.
I would be more than willing to provide more technical information to anybody that requests it.
It's almost pointless to post specific values that are set, as no two Placebos make every adjustment the same,
but there are some constants, for example:
Every Placebo implements a sysctl.conf (or equiv.) which will adjust (at least some of) the following settings:
(The following is a brief breakdown of tunable virtual memory settings, as I understand them.
I do not claim to know a lot about Linux. If you notice something that I have misunderstood,
Please correct me. Flaming will not be responded to. Helpful knowledge will be appreciated.)
-------------------Virtual Memory------------------
dirty_background_ratio (threshold at which background data becomes 'dirtyable'
dirty_ratio (threshold at which data becomes 'dirtyable'
dirty_expire_centisecs (time, in hundredths of seconds, before dirty data expires
dirty_writeback_centisecs (time, in hundredths of seconds, before old data is allowed to be written by PDflush Daemons ( a value of ZERO disables flush, out of fear I haven't tried this.
drop_caches (self explained, but the values are | 1=PageCache; 2=InodeCache; 3=both
highmem_is_dirtyable (I don't fully understand this, but my take is it can prevent random/unnecessary I/O within known/mapped files
laptop_mode (determines the time, in seconds, between "disk" I/O and a flush of all dirty data
lowmem_reserve_ratio (ratio of total pages-to-free-pages for each memory zone
min_free_kbytes (this number is used to compute a pages_min value for each lowmem zone

PhAkEer said:
Honestly I dont see why you would have a problem trying a term.
Is your phone rooted? What commands did you attempt and what was the log output that it returned?
Curiosity; what Rom/kernel are you are using?
Click to expand...
Click to collapse
Not sure what to type lol and what to show you in the log but i am rooted on the universe rom with agats kernel.. I just typed in placebo. It has a ton of info in the log.. Also the universe does have kobridge tweaks which i see it in the logs lol
Sent from my SPH-D710 using XDA

Re: [TWEAK] placebo [$ETTINGS]
Just pm a copy of the log if yoy can... Im at work but will take a look.

Alright, I had hoped to wait until page 3..page 3 is always a safe place... Oh well....
This is a config Im currently working on. If it plays out well, its a big boost in a couple departments.
I cant very well get this thing universal with only one test phone...
Placebo: SugarPill
http://db.tt/in7LAmRN
This one almost effects the battery as much as a new ROM. It will probably take a short cycle before it balances itself out.
These settings are a little aggresive, but Im still taking it easy because I dont want anyone to break anything...
Come on guys, I thought we could all evolve this together =)
FREEBIE:
Ever gone into the supplicant scan's config file? Its pretty useful if you were to... say... Idk... Change the interface to uwbr0.
Your welcome.
(pictures unrelated to above tip)
Sent from my SPH-D710 using xda premium

Much better on the OP. Are you able to provide the download link to the file using the regular xda method (I added one below)? It is easier to see the link and it provides 2 very useful things: it has a built-in download counter (views) and you can remove or update it to new file(s) whenever you like.
Edit: Please put a brief note on the OP with what this script is known to work with (ROMs). And also do yourself a favor and put a disclaimer that you do not plan to support all the roms that are out at this time, try at your own risk stuff. That will save you a lot of headache there are so many different roms out there.

Is there a reason you're leaving /system writable?
Also, this seems to effectively replace kobridge's 41tweaks script, but doesn't address his ondemand scheduler, or build.prop or wifi sleep tweaks. Is that accurate? Can you see any potential conflicts if I kept those?

b1g.p0ppa said:
Is there a reason you're leaving /system writable?
Also, this seems to effectively replace kobridge's 41tweaks script, but doesn't address his ondemand scheduler, or build.prop or wifi sleep tweaks. Is that accurate? Can you see any potential conflicts if I kept those?
Click to expand...
Click to collapse
Actually it was by design to leave those alone, and since I have no scheduler in Placebo, no conflict there. (I smaaawt sah ntine) .
I didnt ask kobridge for permission to insert his work into placebo, so WifiSleepWait is left alone.
If you look for the "*tweaks" youll see what it is.. placebo will interact only with things having "tweak" in their name in its current config.
And about system, thats just a preference of mine. Feel free to add anything (including unmount) to it.
@ Tdun,
Forgive my XDA noobiness, but no actually, I dont know how to make that little tab. Lol
Thanks for all of your constructive criticism/advice. Its much appreciated.
(lol typos when noob=nofun)

Anyway this will work on GB?
Im on Calk's el29 and would love to see if this works on it.

PhAkEer said:
Actually it was by design to leave those alone, and since I have no scheduler in Placebo, no conflict there. (I smaaawt sah ntine) .
I didnt ask kobridge for permission to insert his work into placebo, so WifiSleepWait is left alone.
If you look for the "*tweaks" youll see what it is.. placebo will interact only with things having "tweak" in their name in its current config.
And about system, thats just a preference of mine. Feel free to add anything (including unmount) to it.
@ Tdun,
Forgive my XDA noobiness, but no actually, I dont know how to make that little tab. Lol
Thanks for all of your constructive criticism/advice. Its much appreciated.
(lol typos when noob=nofun)
Click to expand...
Click to collapse
Awesome! So awesome it inspired me to edit my sig. Here's how I'm incorporating your script into my rig:
Code:
echo "SugarPilling"
test -f /system/etc/init.d/41tweaks_kobridge && rm /system/etc/init.d/41tweaks_kobridge
cp /sdcard/gscript/SugarPill /system/etc/init.d/41SugarPill && chmod 755 /system/etc/init.d/41SugarPill
---------- Post added at 03:11 PM ---------- Previous post was at 03:10 PM ----------
apatcas said:
Anyway this will work on GB?
Im on Calk's el29 and would love to see if this works on it.
Click to expand...
Click to collapse
Sure it would. If nothing else, run it interactively and check the log. (I'm pretty sure) the tweaks get reset back to default when you reboot.

lol Im scatter-brained and trying to get out the door for work,
As for GB, I dont see why there would be any issues. I havent tried it, but these are the same things that were in scripts long before I was playing witb them so Id guess that its safe.
Sent from my SPH-D710 using xda premium

Develop Bugs

welcome