yashsingh1/xdaforums huggingface dataset:
[Verizon Droid Charge] maurogg84:
I got KAK 3.1 working. This is what I did. I still had a copy of the KAK in the data folder I deleted the 2 #'s after the comment to activate the log. Made a copy of the script and pasted it in the init folder, deleted the .sh after 98kickasskernel, gave the file execute permissions with script manager. Restarted the phone, verified the settings and my phone is kicking ass. I'm not getting any bootloops anymore, which doesn't help you at all, since the problem stars when the script is installed.

I did this because if I installed the script the regular way, I wouldn't have enough time to go edit the file to activate the log before the phone starts to bootloop.

Droid Charge

Edit: I forgot to mention that at the time of the boot loops, I had the busy box you recommended, since I had to reinstall the ROM because of the loops it went back to busybox 1.19.0 I think. I installed v6 supercharger successfully with that busybox.
[Verizon Droid Charge] Cilraaz:
I pre-set /data/98KickAssKernel.sh to not run on boot in Script Manager, installed KAK, and managed to delete the init.d script before it booted (it did boot shortly after, though). Once it loaded up from the boot, I enabled debugging in the /data/98KickAssKernel.sh script and waited a few minutes to ensure the phone wasn't going to reboot. It didn't, so I ran the script. I checked the log immediately after and it showed that the script had completed. Shortly after, the phone rebooted. After loading without the /data or init.d scripts running, it stayed up and running without any unexpected reboots.

I poured through the debug log for any errors at all. A few lines in, the script attempted to run "busybox sysctl -p" and returned "sysctl: /etc/sysctl.conf: No such file or directory". The sysctl edits ran without any errors. The remounts ran without any errors.

I'm not sure if any of this helps, but let me know if you'd like me to try anything else.
[Verizon Droid Charge] xfloggingkylex:
I have been absolutely hating the charge since I got it last week.

I am currently running Eclipse 1.2 with PBJ 0130 kernel, used Imoseyon's to convert to EXT4.

I use v6 SC option 7. Everything seems to run great switching through apps and home screens, but if I play a game like Tiny Tower or start browsing picture heavy web pages, the phone locks up usually requiring a battery pull (or at least a couple minutes idle).

I'm not running KAK or the 3g turbo, and when I un supercharge I dont seem to have the crashing issue, but the redraws and general laggyness is annoying.

Any idea whats going on?
[Verizon Droid Charge] maurogg84:
Try option 6 or lower with v6. Also if you overclock to 1200 mhz, it would make a big difference

Edit: which version of v6 are you using?
[Verizon Droid Charge] nismology:
Try a less aggressive setting.
[Verizon Droid Charge] xfloggingkylex:
I've been running 5.2. Picked up the new 6.

I was overclocked but disabled it because I didn't want that factoring into the crashing.

I'll try a lower option.
[Verizon Droid Charge] maurogg84:
1200 mhz it's pretty safe, anything above that can give you some trouble, use voltage control app.
[Verizon Droid Charge] xfloggingkylex:
Thats what I have been using. Just wanted to eliminate as many variables as I could.
[Verizon Droid Charge] maurogg84:
which home launcher are you using? Make sure is not locked in memory. That would create lag with v6
[Verizon Droid Charge] xfloggingkylex:
Hey, I am using ADWex and as far as I know it isn't locked in memory. On my droid 2 I never changed any ADW settings related to memory and it ran great with v6.

I'll take a look to double check though, thanks.

EDIT: What is everyone using for I/O schedule and Governor?

Also, any recommended voltages? Im currently using -125, -100, -100, -100 , -50 , -50 for 100-1200.

Thanks for all the help.
[Verizon Droid Charge] Cilraaz:
I had the same issues under option 7 (more with heavy apps like Tiny Tower or Plants vs Zombies restarting themselves or lagging... not so much hard locks). With update 9 RC5.2 of the V6 script, I'm using the suggested/calculated values (6, 8, 41, 48, 56, 63) with great success.

I'm using sio and smartassV2. My voltages are -150, -125, -100, -100, -75, -50, -50, -50 for 100-1400 (my typical OC is only to 1300, though).
[Verizon Droid Charge] xfloggingkylex:
Yeah, while option 7 ran amazing on my Droid 2, it seems they are too aggressive for the charge...

I'm currently on option 6 and it is doing much better. I will try the suggested values next.

So what about KAK and 3G? worth using those scripts as well?
[Verizon Droid Charge] maurogg84:
don't use the KAK I believe there is conflict between imnutz kernel and KAK that causes bootloops, and the 3g has like 5 different choices, try all of them and test the speed to verify which one is the best.
[Verizon Droid Charge] xfloggingkylex:
Well I tried the customized settings like cilraaz and tried to leave the minfree stuff alone so it would be what the phone uses stock, they all have issues when streaming music and playing tiny tower. It is definitely the fact that the phone can't get enough free ram, whether that is because the launcher doesn't die or because of the new groupings, the phone runs solid, though with launcher redraw, without v6.

Huge pain because v6 makes the phone feel faster, but the crashes make it un usable for now. If anyone has any ideas I am all ears. I plan on trying some things over the next few days.

Thanks for all the help.
[Verizon Droid Charge] zer0space1:
I just tried to remove v6 by using this method

"You can also go to /system and delete build.prop and rename build.prop.un3g to "build.prop". I would then reboot your phone."

the thing is ( and this is probably where I fail) there was no build.prop.un3g. it was build.prop.unsuper that I renamed because that was the last action I performed with the script.

Now my phone is hanging on the blank screen right after it says " now loading". Did I just "brick" my phone?

Rooted Casio c771 build 2.3.3
[Verizon Droid Charge] maurogg84:
Which ROM and kernel where you on?

Eclipse 1.2 ROM

KAK & Supercharged!
[Verizon Droid Charge] Cilraaz:
build.prop.un3g would be for zeppelinrox's 3G script. build.prop.unsuper is for the V6 Supercharger script. Moving that back into place would remove V6's build.prop tweaks, though I'm not sure how that would interact with other tweaks the script made. Why wouldn't you just use the "Unsupercharge" option within the V6 script?

If you just moved the build.prop.unsuper back to build.prop, the phone should boot, so far as I know. It might not boot if you typo'd the filename or something (actually, I'm not sure if android will boot without a build.prop or not... doubt it though). If it doesn't boot, you may have to re-flash your ROM.
[Verizon Droid Charge] xfloggingkylex:
The only way I was able to get my phone stable under heavy multitasking (streaming music and playing a game) was to not use v6. A damn shame considering how fast the phone feels under normal use. Unfortunately it seems that the script does too good of a job at preventing some apps from closing and the phone just stops responding. I have tried every setting but I can force a lockup every time.
[Verizon Droid Charge] zeppelinrox:
Here's hoping the updated KAK is okay with imnutz
[Verizon Droid Charge] xfloggingkylex:
I'm scared to try now that I have v6 working. I've missed it so much.

EDIT: to clarify, have v6 working using the new 6.1 RC
[Verizon Droid Charge] Cilraaz:
I'm going to try it here shortly. I'll report back then.

[edit: Unsupercharged (Update 9 RC5.2) and re-supercharged (Update 9 RC6.1) fine, though there are some errors. In particular, when the menu is displayed along with current status, I see:

Launcher issh: bad number
sh: bad number
sh: bad number
sh: bad number
HARD TO KILL! ie. SUPERCHARGED!

I'm seeing "bad number" in a few other spots also, like just before the "Press the Enter Key... and Come Get Some" prior to the menu loading.

Also, right after the busybox check, I'm seeing the message "grep: /data/system/packages.xml: No such file or directory". I assume this is just an internal check that can be pushed to /dev/null.

Otherwise, V6 appears to be fine.

Also, zeppelinrox, if you want input somewhere other than this thread, please let me know.]

[edit2: V6 also seems to refuse to acknowledge my launcher as ever being on any setting higher than Hard to Kill. I ran Bulletproof, rebooted, and it still says Hard to Kill. Trying KAK now.]

[edit3: Same KAK test as before. Pre-set /data/98KickAssKernel.sh to not run on boot. Installed KAK. Removed init.d script. Phone booted within 3 minutes of installing. After boot, loaded up fine and ran for a while with no reboots. Manually ran /data/98KickAssKernel.sh and the phone rebooted within a minute or so. Looks like there's still something unhappy going on.]
[Verizon Droid Charge] Blanco954:
Hello,

So I tried this out and I feel the phone improved. I also ran the 3g and kickass scripts but as I started exploring and running different apps I noticed that my youtube streams will not run from widget or browser. I replaced the build.prop file with backup and rebooted that did not fix youtube stream. I ran the v6 script and selected the unkernel option and rebooted and had same result youtube streams will not run black screen on widget ie buffering on browser I get an error "this file cannot be played" this is after trying to load. All was fine before any tweaks. Other services like Slacker, Tunein Pro work fine. Anyone else having this issue or recommend a fix.

My setup:

Droid Charge

ROM: Eclipse v1.3.1

Kernel: IMNUTS PBJ OTB latest & OC 1200 via SetCPU OC manager
[Verizon Droid Charge] zeppelinrox:
That would have to be a specific youtube issue since everything else is fine.

Who knows, maybe they had a temporary glitch?

The only thing I can think of is to clear youtube caches.
[Verizon Droid Charge] Blanco954:
Ok let me try that I appreciate the quick response from dev. I hope it is just a glitch. I enjoy watching my subs on YT favorite is =3 that's some funny stuff.
[Verizon Droid Charge] kvswim:
The youtube issues are from the latest update fromthe APK. Roll it back to the stock version and it will be fine.

Sent from my Droid Charge running GummyFroyo 1.9.1
[Verizon Droid Charge] Rythmyc:
Ran the script, rebooted, and re-ran the script. The min-free values didn't not stick. Went into System/Etc/ and could not find the init.d file. You say to check in /data, but when I try to go into /data, Script Manager tells me it's forbidden? Am I doing something wrong?
[Verizon Droid Charge] fortesquieu:
I pmed OP to put the fix regarding this, so people can benefit from it.

Basically, you'll need to download gscript from market, then run an autostart script for that v6 script to stick.

Here's the link to it.

xdaforums.com/showthread.php?t=1017291

Let me know if you need help.
[Verizon Droid Charge] Blanco954:
As kvswim posted the recent youtube update broke app. I uninstalled the update (rolled back) and this fixed my issue. Looks like user community is voicing their concerns to Google support on help forums.

Now back to original scheduled program lol :-)
[Verizon Droid Charge] zeppelinrox:
That works on the Charge? That's not a motorola phone though...

If it does, that's pretty awesome...

It would still work with script manager though :)
[Verizon Droid Charge] kvswim:
op has some "run on boot" stuff that makes it work?

Sent from my Droid Charge running GummyFroyo 1.9.1
[Verizon Droid Charge] Piercing Heavens:
For the 3G TurboCharger & Kick Ass Kernel Tweak Installers In my system I have a "build" file and a "build.prop" file. Only the "build" file has the

"Check to see if they work:

1. /system/build.prop should have these entries:

ro.ril.hsxpa=3

ro.ril.gprsclass=12

ro.ril.hep=1

ro.ril.enable.dtm=1

ro.ril.hsdpa.category=28

ro.ril.enable.a53=1

ro.ril.enable.3g.prefix=1

ro.ril.htcmaskw1.bitmask=4294967295

ro.ril.htcmaskw1=14449

ro.ril.hsupa.category=9"

portion while the build.prop does not have the new changes. Is it safe to delete the build.prop? Or would I have to rename the build to build.prop? Or would having both still give me the edits either way?
[Verizon Droid Charge] hazard209:
Are you on the stock ROM? I need some information on that even though this will work on stock ROMs. You can try what fortesquieu has recommended if you are having troubles.

OP has been updated. Thanks again.

I don't know what the plain old "build" file is. I don't have that on my phone. What you can do is copy and paste those values straight into build.prop just make sure there is a blank line at the end!
[Verizon Droid Charge] 1.4hitachi:
I tried this once and it worked fine, but I installed EP1Q Humble but didn't like it and went back to EE4 Humble, installed this script and it boot loops. I tried 3 different times any suggestions?
[Verizon Droid Charge] hazard209:
What version of busybox are you running?
[Verizon Droid Charge] PeterGunz:
I successfully ran this script before on Froyo, but last night I switched to Gingerbread and I can't get it to run. I'm on the correct BusyBox version and followed your instructions, but when I select 16 to reboot, it says "reboot not found."

And when I manually reboot, minefrees won't stick.
[Verizon Droid Charge] hazard209:
Try going to the init.d folder and running the 99SuperCharger script as root and on boot, then run the original V6 and try rebooting manually.
[Verizon Droid Charge] PeterGunz:
First of all, I apologize for not reading your OP more closely. I should have attempted Installation B before asking for help but didn't notice the part about checking Data if System/etc/init.d doesn't exist.

Data is forbidden, so I am going to try Gscript. I can't believe it ran so flawlessly before, but now I am running into trouble.

Update: It worked, thank you!

Oh and for the record, I had to upgrade busybox to the latest version of 1.19 in order to ensure Gscripts performed correctly. I forgot to downgrade it to the older version of Busybox before running SuperCharger, and everything worked just fine and everything stuck.
[Verizon Droid Charge] fortesquieu:
Yea, it was the only way for my GB leak ROM to get the minfrees to stick.
[Verizon Droid Charge] zeppelinrox:
I don't get why you would have a mot_boot_mode file if it's not motorola :p
[Verizon Droid Charge] hazard209:
Glad to hear it. The newer versions of busybox have been known to be finicky, that's why it's recommended that you roll back to an older version.

Actually we don't... I'll have to check Gscript and look into why it works with sammy.
[Verizon Droid Charge] fortesquieu:
Oh I think we have a misunderstanding! From that thread, stock roms need to run that autostart script in order for the minfrees of V6 script to stick.

I should have been clear on this, Samsung users only need to read the bottom part of that thread.

Sorry for the confusion.
[Verizon Droid Charge] LANAtron:
Could part of the issue be running the stock ep1q kernel? I had issues until I used the Nameless kernel, which supports init.d changes.
[Verizon Droid Charge] Danzanzio:
This is in the OP but you should add that you must go to the menu in script manager then to advanced settings>config and then make sure "browse as root" is checked. Doing that will let you go into the data folder to find the 99supercharger file and run it on boot.
[Verizon Droid Charge] hazard209:
OP has been updated. Thanks for the reminder. It has always been checked whenever I go into config, so I didn't even think of it.
[Verizon Droid Charge] zeppelinrox:
hazard, have a look at the html help file on your sd card.

I think it has most of the bases covered already (it does say to do what Danzanzio just recommended) so it may help you with any other possibly additional tips :)

I really think nobody reads that help file.... LOL
[Verizon Droid Charge] hazard209:
I'll admit, I've never read it. Lol. Never had a need to though, I've always figured out a way to get it to work. Or antagonized your thread until I've gotten help.
[Verizon Droid Charge] zeppelinrox:
That's cool.

I did make the script itself pretty self explanatory :)

So, get a load of this...

[SCRIPT]Jupa Engine V3.0.0 - How to tweak android the easy way

Feel free to share your thoughts about stealing in that thread....

I'm freaking flabbergasted...
[Verizon Droid Charge] hazard209:
I have no words... I mean, he did give credit to every dev, which is has usually been the major issue. But this is taking the work, giving credit, but not bothering to ask if they can use it for themselves. I don't know if I've ever seen this before. I understand why you're flabbergasted. This guy is a piece of work.

EDIT: I didn't even think of your work with the V8.. Wow. That just adds something else against this guy..
[Verizon Droid Charge] billku:
Hey Hazard, how familiar are you with the Loopy smoothness tweak? I followed all the instructions in the OP of the Loopy Smoothness thread, but if you look at the script, there seems to be some other things you need to do (enter the number of processes you want checked, etc.) Any ideas on this? I'd post this question on that thread, but it seems to have been somewhat of a ghost town the last few days... thanks!
[Verizon Droid Charge] kvswim:
That guy has balls the size of Uranus (teehee). Sounds like a problem we JUST got through with right here on the Charge forums...

Sent from my Droid Charge running GummyFroyo 1.9.1
[Verizon Droid Charge] kvswim:
It says in the OP that he's working on a guide.

Sent from my Droid Charge running GummyFroyo 1.9.1
[Verizon Droid Charge] billku:
Thanks for that, hoping maybe he can give me a quick response on my question in the meantime, if he can't, that's fine too.
[Verizon Droid Charge] hazard209:
Yeah, but I've been lazy and haven't put it up yet... Give me an hour or so and I'll have it up with some additional build.prop tweaks you can manually add.

I believe that you can continue to add the number of processes that you want stored in the cache (number of PNAME's). But too many and it becomes redundant and it won't help anything. Let me get the walk through up and I'll do some more tinkering with Loopy Smoothness.
[Verizon Droid Charge] billku:
Thanks, man, it's all good!
[Verizon Droid Charge] hazard209:
OP has been updated.
[Verizon Droid Charge] 24BlackMamba:
speedy phone!!!

I have all of these tweaks and scripts on my phone thanks to hazard!!! And i must admit my phone feels MUCH snappier and very smooth. I have also noticed that my 4g speeds have also improved since i added all these tweaks. Once again thanks to hazard for helping me get these on my phone!! :)
[Verizon Droid Charge] kvswim:
Are we supposed to run 97_loopy on boot?

Sent from my Droid Charge running GummyFroyo 1.9.1
[Verizon Droid Charge] hazard209:
If you had to for the 99SuperCharger file, then yes.
[Verizon Droid Charge] PeterGunz:
For Loopy, total noob question for the launcher: Do I erase the quotes and the following # and instructions? Or do I simply input the name of the launcher between the quotes and leave it?
[Verizon Droid Charge] hazard209:
You just have to enter the launcher's process name in between the quotes.
[Verizon Droid Charge] PeterGunz:
So I had to go back and do just that for the 99SuperCharger file. And I understand that if I did, I must do so for Loopy as well. What about 3G and Kickass? I just ran them as Root and let them be.
[Verizon Droid Charge] hazard209:
3g just edits build.prop, so that's fine. There should be a 98kernel file in init.d, so do the same for that file.
[Verizon Droid Charge] chiahead52:
I have a question. What if I want to undo the script changes? I want to do some tests. I realize I can unsupercharge the V6 supercharger one but what about undoing the others....Loopy smooth and the 3g and kernel hack ones? Any way I can do this without wiping data?

BTW.. the scripts seem to stay when flashing multiple ROM's as long as the data is not wiped
[Verizon Droid Charge] hazard209:
You can delete the 98kickasskernel, 97_loopy_smoothness_tweak, and 99SuperCharger files. You can also delete build.prop and rename build.prop.un3g to build.prop
[Verizon Droid Charge] PeterGunz:
I applied V6, Kickass, 3G, and the Loopy scripts and they are all working great.

Just curious, other than a launcher (I put in ADW EX) what apps are people adding to Loopy?

Also, if you added a different SMS app like Go SMS, did you replace the stock one under system apps (at least I think I saw it there)?
[Verizon Droid Charge] billku:
I did replace the stock sms app with Handcent, though I'm not sure if it's working well or not, it seems to start reloading at some point despite the tweak, though I'm not 100% sure. I tried loading facebook into this tweak, but again, it seems to be reloading at some point (even the static pages), that may be just the nature of constantly updating social sites.

Another question for Hazard: Thanks for clarifying that we need to edit the number of processes. That whole first section seems to be designed to be edited -- to debug or not, user processes number, etc. Do we need to do anything with the following variables? Or just leave them be?

NUMBER_OF_CHECKS=0	# Total number of rechecks before ending 1st loop

SLEEP_TIME=0	# Number of seconds between rechecking processes

Thanks again for all your help on this!
[Verizon Droid Charge] hazard209:
Glad to hear that they're all serving you well. As for other apps, I put voltage control and task manager because I'm in and out of those constantly. I tend to not replace the stock processes just because when you do get FCs they tend to be for the stock apps.

I haven't used it for social networking sites, so I'm unsure how it will it affect them. I'm not the facebook junkie I was a few years ago. Some you can edit and some you shouldn't. I use the following settings for those two variables:

NUMBER_OF_CHECKS=60

SLEEP_TIME=3
[Verizon Droid Charge] galaxyuser88:
What about the 98tweaks and 99swap files? do those need to be running?

I have these root and boot.

1. 98kickass

2. 99 supercharger

3 s_loopy_smoothness_Tweak

Thank you.
[Verizon Droid Charge] hazenberger:
hmmm. I'm having an odd issue. I just ran the V6 script and upon reboot, I'm stuck at the phone Searching for Service. When I unlock the phone, it says I've got a force close on com.android.phone. Any ideas? Thanks so much!!

Update: I booted into CWM and wiped cache and dalvik and I'm now able to boot but it appears the script didn't take... Going to try again now.
[Verizon Droid Charge] hazard209:
Don't worry about the 98tweaks and the 99swap files. They're installed with your ROM.

If that didn't fix it, check which version of busybox you are using.
[Verizon Droid Charge] immaage:
I ran installation steps B and then A and now it seems that my phone is boot looping. I am running the latest Eclipse EE4.

Is there an easy way to undo the changes?
[Verizon Droid Charge] hazard209:
I'm afraid that if your bootlooping you'll have to flash over a new ROM.
[Verizon Droid Charge] billku:
Any idea what the process name for the stock camera app is? Can't seem to find it in the data/data file...
[Verizon Droid Charge] hazard209:
com.android.camera
[Verizon Droid Charge] billku:
Thanks, don't know how I missed that...
[Verizon Droid Charge] hazard209:
No worries.
[Verizon Droid Charge] Tucknology:
FWIW I am on Humble 1.51 and busybox was installed in /system/bin which is slightly different than the op.
[Verizon Droid Charge] hazard209:
Thanks for the heads up. OP has been updated with the change.

EDIT: For those that were asking about what the KickAssKernel changes, the OP has been updated with a link that will lead you to everything that the script does. Hope that clears up any questions.
[Verizon Droid Charge] Birthofahero:
Hazard, what do you mean by this regarding the build.prop tweaks?

Are you only supposed to add one line?
[Verizon Droid Charge] hazard209:
There are two blocks of code on that post. Just add one block of code, not both. Either the one with all of the false values or the one with all of the null values.