yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Android Development] zeppelinrox:
FYI... all 3 are updated... and still 100% untested by me :p

http://xdaforums.com/showpost.php?p=15948434&postcount=1127

Updated September 12

: - 3G TurboCharger Installer Update 3 test 11

Tweaked - The interface a little

Updated September 12

: - Kick Ass Kernelizer Installer Update 3 test 5

All-In-One - io scheduling tweaks are optional

Data Foler - is now used for stock roms

Errors - are now hidden so no need to worry about unknown keys showing up ;)

Enhanced - user interface greatly

Tweaked - some io scheduler commands - should be safer than before

Updated September 12

: - V6 SuperCharger Update 9 Beta 4

Massive - Changes lol

Changed - All the names/presets. More options for higher ram devices.

Added - Help Menu Item (launches help file on sd card)

Added - Help Online - Opens up XDA thread in the browser!

Added - Re-SuperCharger! Restore Prior V6 Settings from SD Card

Added - Saftey nets - Checks for BusyBox, it's version (and if it's too high), an error check, and if running as root

Checks RAM - And recommends which horsepower settings to use

Build.prop - is now used. No more local.prop. This enhances stickiness.

Extra - build.prop integration in case you have /system/bin/build.prop

Milestones - More stickiness - init.d script and build.prop are now used as well as the *rc file

Tweaked - some user prompts/information

Numerous - enhancements

\\\\\\\\ V 6 S U P E R C H A R G E R - M E N U ////
==============================================
1. SuperCharger & Launcher Status for Update 9
==============================================
2. 256HP Ledded {6,8,22,24,26,28 mb}
3. 256HP UnLedded {6,8,26,28,30,32 mb}
4. 256HP Super UnLedded {6,8,28,30,35,50 mb}
==============================================
5. 512HP Ledded {6,12,40,60,80,100}
6. 512HP UnLedded {6,12,55,75,95,125}
7. 512HP Super UnLedded {6,12,75,100,125,150}
==============================================
8. 768HP Super UnLedded{6,12,150,175,200,250}
9. 1000HP Super UnLedded{6,12,200,225,250,300}
===============================================
10. Cust-OOMizer Settings {Create Or Restore!}
===============================================
11. OOM Grouping Fixes + Hard To Kill Launcher
12. OOM Grouping Fixes + BulletProof Launcher
===============================================
13. UnKernelizer - UnDo Kernel/Memory Tweaks
14. UnSuperCharger
===============================================
15. BulletProof App! {Hit or Miss}
16. Engine Flush - Quick Boost & Eliminate Lag!
17. Nitro Lag Nullifier {Experimental}
18. Use V6 SuperCharger with Terminal Emulator!
===============================================
19. Help File!
20. Help Online!
21. Options
22. Re-SuperCharger!{Restore Prior V6 Settings}
23. REBOOT! (WARNING - There is NO Warning!)
24. Exit
[Touch Pro2, Tilt 2 Android Development] hl41:
Topic 6 doesn't persist for reboots?

I can't seem to get the pm disable trick to persist for reboots.

Maps, Gmail, Market all keep appear to be started without my using them. I see these apps in the running list and I still see "for broadcast" messages in the logcat data.

Is there a command to check what is disabled? I looked at the pm command and can't find one that will show me this info.

Other things that might be relevant...

1) I'm not running pm disable as root. I tried and it didn't seem to help.

2) If I start an app manually and then kill it, it seems to now be able to start up again when it wants to. i.e. the pm disable only effects auto start on boot?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
1. I think you should be running it as root, yes...

2. Yes, this is correct. The pm disable only effects apps on boot AFAIK.

It certainly does persist for me after a reboot tho - are you deleting you data.img? I'm pretty sure that's where this setting gets saved. Honestly not sure how to check which apps are "disabled", other than checking logcat on boot for "for broadcast"...
[Touch Pro2, Tilt 2 Android Development] teemo:
I googled.

PM seem to work on everything :)

Try

pm list packages

then

pm disable your.app.to.be.disabled

Will be remembered after boot.

And yes, you need su:

export PATH=/data/local/bin:$PATH
$ $ pm enable net.andchat
[1] Killed pm enable net.andchat
$ pm enable net.andchat
[1] Killed pm enable net.andchat
$ su
# pm enable net.andchat
Package net.andchat new state: enabled
#
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Perhaps I should try this "google" sometime! lol, thanks teemo.

Edit - Ah - I see now. So there's two things - my method ensures you disable the entire for broadcast message. If you're careful, you will only disable the boot process. Your method that you found on Google will actually remove the app completely - not the goal here.

So be careful! If you pm disable the entire app, you won't be able to use that app again! That's definitely not what I want, I still want to be able to run the app - I just don't want it to run on boot.

Because that's the approach I'm taking, there might be some apps you can't disable. I can't say which ones work and which don't, people will have to figure it out for themselves - there's simply too many apps...

See what I say in the first post:

So when I originally did this, I was dumb and disabled the apps themselves. However, before I mucked with anything I backed up my data.img, so that was smart :D.

Be careful with that step folks! It's not as straightforward as it seems.
[Touch Pro2, Tilt 2 Android Development] teemo:
Lol yes always be careful when messing with Linux :D

I was aware of this, but assume people have learned to backup, might be wrong about that though.

I did say that it seem to work on everything.

Disable does not remove the app, it only denies access to it. Easy to get back again with the enable switch.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well, that is true. But when you're in the UI, it sure as heck does seem like the app has been removed/uninstalled considering you can't use it :p.
[Touch Pro2, Tilt 2 Android Development] hl41:
Thanks. Definitely need root. I did not notice in my adb shell that when I executed su, it actually said permission denied.

To get su to work in adb I found this:

http://www.droidforums.net/forum/dr...hell-su-permission-denied-rooted-phone-2.html
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Yes, of course... You need to "allow" root access thru the SU app.
[Touch Pro2, Tilt 2 Android Development] torrent_2004:
Froyo 7.1 + LauncherPro + SuperCharger + SD Booster combination saves my day.

Quite snappy afterward.

I gave up on WM 6.5 on Tilt2.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Heh, everyone has...

Glad you like it! I decided to go a little nutso and I tried the 512mb "MEGA RAM" setting... the first one (6,12,40,60,80,100 mb). This basically sets the values way high - so it will kill apps pretty quickly, but I haven't had any issues. Other than great performance! I'd assume that it pretty much closes anything when it's not open tho. Fine by me, it seems we need all the free RAM we can get.
[Touch Pro2, Tilt 2 Android Development] fortunz:
I actually tried mega ram 1 the other day to see if I could get Fieldrunners HD to get past wave 25 without crashing. Still crashed once there were enough towers/runnners on screen, but honestly, I was surprised it ran at all. I reverted to one of the aggressive settings afterward, never really considered just leaving the mega setting on. I might try that.
[Touch Pro2, Tilt 2 Android Development] großa:
Using 512MB now (option 7 Super [aggressive]) working fine so far :)
[Touch Pro2, Tilt 2 Android Development] torrent_2004:
Running this MEGA RAM 512MB option for the last 1 1/2 day - so far so good.

Thanks.
[Touch Pro2, Tilt 2 Android Development] ACoolGuy:
I have done most of the tweaks in this thread(except the Startup programs and firewalling) and had always had issues with SOD's(frozen black screen with no response to buttons/screentaps). I had been overclocking to 768mhz and thought it may be that(Even tho WINMO handles 768mhz like a champ), so I stepped it down to 710.4mhz. This didnt fix the SOD's so I Stepped down to 600Something(dont remember exactly) and still SOD's. Finally I completely disabled my overclock and the SOD's persisted.

The thing that FINALLY(Thank AndGOD!) stopped the SOD's was disabling CompCache. For some odd reason after trying numerous kernals and settings and tweaks formatting and deleting data.img countless times, I am SOD free.

My next step is to re-enable overclocking to see how that goes, but so far a week with no SOD's has been GREAT!

My Question is: Has anyone been experiencing Their devices becoming non-responsive at random and requiring a reboot? And are you using CompCache?

Using Rhod400 on Sprint Running FRX07.1 on latest Kernal and RootFS.
[Touch Pro2, Tilt 2 Android Development] großa:
Hmm no. I'm still using Starfoxes latest test kernel, used compcache with his settings since he mentioned it in the forums. The original compcache settings are buggy. So that could explain your problem.

Using a swapfile (128mb) since a week or so and it seems to run a little bit better as with compcache.
[Touch Pro2, Tilt 2 Android Development] [ACL]:
maybe because you are calling them kernals.. :D
[Touch Pro2, Tilt 2 Android Development] ACoolGuy:
HAH! Nice Catch. The hilarious thing is that I am eating a bag of popcorn right now.

Back on topic, I tried am currently using 672mhz overclock and so far so good. I have also begun using the first MEGARAM 512MB setting for SuperCharger and so far today I have not had a SoD. I'll have to give it a couple of days to call it good tho.

As far as the pm.sleepmode is concerned, I remember having to set it to 2 to get overclock to work properly. And I believe I had remembered seeing someone state that pm.sleepmode=1 is now used for non-OC and OC. Can someone clear this up please. Thanks.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
You are correct, on both fronts.

Mode 2 used to be required when overclocking, no longer. Everyone should be using 1 now.
[Touch Pro2, Tilt 2 Android Development] zeppelinrox:
FYI... :D

Changelog:

Updated October 3

: - V6 SuperCharger Update 9 Beta 6.2.2

Added -

2 OOM Sticks!

zOOM

(quick) and

vrOOM

(verbose) versions. (yeah yeah... I shoulda made Four Sticks! get it?)

Added -

PowerShift Scripts!

(make quick widgets for different minfrees!)

Added -

Bullet_Proof App One-Shots!

(you can make it a widgetable script whenever you bulletproof an app!)

Added -

(S)97BulletProof_Apps boot script

(you can add to it whenever you bulletproof an app!)

Added -

Fast Engine Flush

- You can make a widget for it or put it on a schedule!

Improved - Re-SuperCharger - When you copy settings from sd card, it will load 99SuperCharger

Added - Support for devices that use S*(not numbered) boot scripts so S99SuperCharger is created instead of 99SuperCharger

Added - Support for com.htc.launcher (knows it's locked status automatically)

Added - Support for devices with /system/etc/hw_config.sh

Remembers - If you're using local.prop or build.prop (you can change setting in Options)

Improved - Test on startup (Test Drive)

Enhanced - The interface all over the place (the menu is a "Driver's Console") :)

Added - Check to see if you selected an inappropriate setting (256 mb can't choose 8 or 9)

Fixed - A bug where it would mess up a milestone's init.mapphone_umts.rc file if V6 ran twice... /me n00b :o

Added - Another 1,050 lines of code :eek:

The file is V6_SuperCharger_for_Android-update9_beta_6.2.2.un.zip

It has 2 OOM Sticks... so... Come Get Some!
[Touch Pro2, Tilt 2 Android Development] vinceweis:
I've been having some problems with DroidWall recently. With the recent kernel releases, I get an error that the iptables and filter does not exist and it recommends an update. If I use the kernel that comes with FRX07.1, it works fine. Was iptables removed from recent kernels for some reason? Am I doing something else wrong that someone has run into before?
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Huh, I don't think so...? Have you pinpointed which kernel in particular where it first breaks..?

There's a few modules that I modprobe in the user.conf (I know, not the best solution...) - are they still in there? I believe these are the two that are necessary for Droidwall:

modprobe xt_owner
modprobe ipt_REJECT

Make sure those are enabled...
[Touch Pro2, Tilt 2 Android Development] vinceweis:
DroidWall and kernel conflict

The 8/19 kernel works fine. I think the problem started with the 9/14 kernel and persists with the 10/01 kernel.

I don't change the froyo.user.conf file, only the kernel. The modprobe lines are still in there. I will try testing again later today to see if I can narrow it down.

Update: With the 8/19 kernel, DroidWall works fine. I can change the applications in the white list, save them, and enable the firewall. I changed to the 9/14 kernel. When I try to change the white list, it claims to save the list but when I re-enable the firewall, I get the following message:

Error applying iptables rules

Exit code: 2

iptables v 1.4.10

iptables v 1.4.10: Cant initialize

iptables Table 'filter': Table

does not exist (do you need to

insmod?)

Perhaps iptables or your kernel needs to be upgraded.

When I revert back to the 8/19 kernel, I can disable the firewall, save new rules, re-enable the firewall, and get a brief message about rules applied with success. Nothng changed except for the zimage and modules.

Update: The 10/17 kernel is the same. Still won't run DroidWall. Went back to 8/19 and all is well.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I've been lost in test-land, so I haven't given any of the newer (autobuild) kernels a shot. I'm booting now with 10/1, I'll let you know what happens.
[Touch Pro2, Tilt 2 Android Development] vinceweis:
Just a reminder in case you forgot about me. I'm not pushing since I found the kernel that works. I know your SD card blew up when you were testing this so I figured that was a distraction. I just want to be sure that if I am not doing something wrong, a message gets back to the kernel devs.

Sent from my Tilt2 running XDAndroid
[Touch Pro2, Tilt 2 Android Development] zeppelinrox:
FYI... I have RC1s... :D

http://xdaforums.com/showthread.php?t=991276&page=503

Before Updating,

Wipe Caches!

This is just a precaution in the event that you experience any lag...

Updated October 24

: - V6 SuperCharger Update 9 RC1

Improved - Cust-OOMizer - redid all the code (can now do a quick charge with current minfrees)

Improved - Engine Flush - shows before and after stats (It's really :cool:)

Improved - Re-SuperCharger - won't ever overwrite existing system files with old ones from a different rom and with an easy workaround for that.

Added - Option to wipe dalvik cache and cache partition!

Tweaked - Minfrees - Presets above 256HP are now more multitasking friendly

Tweaked - init.rc support - now optional to copy a supercharged init.rc to root on boot.

More - Lenient busybox recommendations v1.16.2 and up (excluding versions greater than 1.18.2 and lower than 1.19.0)

ReWrote - ALOT of the code - It's ALOT more efficient and smarter :)

Enhanced - the interface all over the place...

Added - something fun... :cool:

Added - something controversial... :eek:

Updated October 24

: - 3G TurboCharger Installer Update 3 RC1

Added - Wi-Fixer - Try and fix wifi issues after applying 3G tweaks...

Added - 6th setting (uses less battery)

Added - Market Link in menu - Opens up to speedtest.net app

Added - something fun... :cool:

Updated October 24

: - Kick Ass Kernelizer Installer Update 3 RC1

Added - Uninstaller

Added - sio scheduler support

Added - vm.oom_dump_tasks=1, vm.laptop_mode=0, vm.block_dump=0, fs.lease-break-time=10

Changed - vm.min_free_kbytes=4096 (was 8192), vfs_cache_pressure=20 (was 10)

Enhanced - IO Scheduler information/display

Enhanced - Interface

Added - something fun... :cool:

Updated October 12

: - V6 SuperCharger Update 9 Beta 6.3

Added - init.rc support! (a supercharged copy gets copied to root on boot - it might not work but it does make for easy baking!)

More - Lenient busybox recommendations v1.16.2 to v1.18.2 (still testing 1.19.2)

Renamed - HTK Launcher to

Die-Hard Launcher!

Added - A 3rd Launcher for Gingerbread roms and higher! (HTK is the 3rd one - no HTK on Froyo and below)

Changed - OOM grouping/adj parameters

Improved - BulletProof Apps routine - loops so you can bulletproof more than one at a time - plus better error handling.

Improved - Test Drive

Mounts - rootfs rw as well as system - should solve some issues :)
[Touch Pro2, Tilt 2 Android Development] großa:
Can't wait to test it :)
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Thanks dude! I like the new layout, very cool. Seems to be a much better method overall as well.

The 'controversial' things you added were a little odd, but hey to each their own. I still love the script :p.
[Touch Pro2, Tilt 2 Android Development] ethanpil:
I found this to be an interesting, and relevant, study of this matter:

Install and Memory usages of popular launchers
[Touch Pro2, Tilt 2 Android Development] teemo:
System Tuner

Found an app that may be a good replacement for several other apps.

It does OOM changes (stick after boot).

SD cache changes (stick after boot)

Simple terminal with history.

Disable/enable apps (PM disable)

Backup apps/system

Logcat with easy filtering

Measure...analyze... etc etc

Currently playing around with it, looks pretty nice :cool:
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Does it actually make adjustments to Android's built-in settings, or...?

The whole reason for the script is Android already has a great method for handling memory/apps. Just need to make the settings a little more aggressive for our phones ;).
[Touch Pro2, Tilt 2 Android Development] teemo:
Yes yes, it use the Android method :)

I assume you talk about the lowmemorykiller settings - oom.

It is not just a lame application killer, it applies the "minfree" values to the system.

The app can write to \system\init.d for permanent effect, but I don't think it will work here. The alternate way, is writing to

/sys/module/lowmemorykiller/parameters/minfree

which is what it does.

I checked

# cat /sys/module/lowmemorykiller/parameters/minfree

- works fine. Settings are applied at next boot too.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Cool! Seems like you found a spiffy app thar.
[Touch Pro2, Tilt 2 Android Development] zeppelinrox:
It used to be called Process Monitor Widget... I still use it for it's original intention as well as the SD Card tweak for now... until I put the SD speed into my script lol

The same dev also has the best battery monitor widget that you can imagine...
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
First, I LOVE that you stop by our bastard-child section of the forums.

Second, be honest - does your script improve on this app at all? Is there any reason to use your script over this app...? Just curious. I love your script, but a well-designed app would be easier to interact with (no offense).
[Touch Pro2, Tilt 2 Android Development] zeppelinrox:
Of course I want to make it an app... and it would be the only app to guarantee that you'll never get launcher redraw and quite frankly, it can't be more snappy than when it's supercharged.

There are lots of ways to change minfrees (apps, scripts), but only the supercharger fixes the groupings so that the minfrees work the way you want them to.

You can have the same amount of free ram before supercharging than afterwards but afterwards, you'd be a very happy camper.

In fact, one person commented that his free ram went down (default minfrees were aggressive I suppose) after supercharging but the phone was amazingly faster... I believe he called it voodoo... lol
[Touch Pro2, Tilt 2 Android Development] teemo:
As Arrrghhh, I am very happy to see you here. Used your script with success, but "uninstalled" for the moment, to learn about other ways to add speed and get an understanding about which changes do what.

I actually found this monitor because I wanted a simple CPU % indication in notification, to let me see when the Rhod is busy. Turned out I found a multi-tool, so I decided to give it a shot.

My problem with your script is simply that I don't understand what it is doing, and was too lazy to read your thread :rolleyes:

Will give it a shot more, but need to supercharge my brain first. Will dive into your sig.-threads, they look interesting. Do you have a short bulletproof introduction or will I need to read it all :D ?

Well, go ahead, what's holding you back :p

Tried it a while ago - it's awesome, but does not work on our build. Sure it will show the % it get from kernel, but it's not accurate. In some situations Voltage is correctly reported but in most it will fluctuate between empty and full. Ampere is way off.

Oh, and huge thanks for all the efford you make on the script. Appreciated!
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
I would read it all to be honest. Also read that thread I link in my Speed Improvements thread. It kind of gives you a background on why tweaking these values is important.

I think he's saying he used that app until he incorporated the SD tweaks ;). Now they are incorporated, and there's no need for the app (for him). Hope I'm reading that correctly.

That's a bummer. I wonder if jonpry's work on SCBS fixes that? I hope one day someone will pickup that work and flesh it out so all devices can enjoy it. Oh well.... maybe Rhodium's can split once flashing to NAND gets stable enough and then it won't matter if we put RHOD-only stuff in the build.
[Touch Pro2, Tilt 2 Android Development] teemo:
Didn't he leave the project with a modern mobile in hand?

The SCBS did not support voltage last I asked.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Ah crap. I didn't noticed you asked in that thread... Maybe I can bug him and convince him to at least "finish" it for RHOD's. Other devices, not sure if that'll ever happen...

He has moved on, but AFAIK he still has the TP2. Just not spending much time on it. He's been involved TouchPad development...
[Touch Pro2, Tilt 2 Android Development] auburnham:
When I was running a rootfs.img from ~8/31/11 to 9/2/11, I ran the V6 SuperCharger script with the most aggressive 512mb setting and started with ~90mb free. I updated my rootfs.img to 10/19/11, and it's as if the V6 SuperCharger script has no impact since I'm now starting with ~40mb free. There is a noticeable slowdown as well, so I don't think it is a error reading the free memory. Running the script again, it shows the minfrees are correct. I've now tried the System Tuner app instead, and there isn't much difference. I've already mentioned this to arrrghhh in another forum, but I wanted to see if anyone else had an idea of what might have changed in the rootfs.img between 8/31 & 10/19 that would cause this behavior.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Well there are now minfrees set in the rootfs, but you should still be able to configure manually.
[Touch Pro2, Tilt 2 Android Development] auburnham:
I think minfrees were set in the rootfs before 8/31. I did a quick comparison of the init.froyo.rc files and they were the same in that section. Let me know if I should be looking somewhere else, but that doesn't appear to be the cause of the problem.
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Make sure Script Manager runs the 99SuperCharger.sh on boot. It's working fine here.
[Touch Pro2, Tilt 2 Android Development] zeppelinrox:
Hey I just mentioned this thread here http://xdaforums.com/showthread.php?p=19716750#post19716750

Wonder if freezing services would be suitable in SuperCharger
[Touch Pro2, Tilt 2 Android Development] arrrghhh:
Makes me feel good that you learned of pm disable's coolness from my post ;). Thanks to hyc for showing me that!!

There have been a few apps recommended in this thread that some have said that handle this. Would be cool for sure. Have you considering writing an app for this too? IMHO it would be much easier to operate all of these fancy options in an app. Just sayin :p.