yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] Computoncio:
Download 98ZepEntropyFix and copy to /etc/init.d

Check the permission and owners on the other files that is in there and apply the same.

Usually is 777 root.shell always works :p

If your rom doesn't have init.d directory run the scrip after boot you have a app to do that but can't remember the name, lack of sleep :D

You can run it on terminal just don't forget to execute "su" before "sh 98ZepEntropyFix" but this way you will have to do it everytime you boot your phone.

Phone: Samsung Galaxy SII - GT-I9100

Kernel: Dorimanx kernel v7.38

1st ROM : RR JB v3.1.3 (Online)

2nd ROM : Empty

MODEM: Modem+RIL - XXLPS

ROOT APP: SuperSu v0.99

MODS: My mods, ASUL v4.2 and JusTunBeam v6.1.3
[Android Software/Hacking General [Developers Only]] m1trand1r:
[OT]no...really? Siyah kernel avatar?...:D...lol[/OT]

Sorry for OT @zep:)....it was intentional:p...:)

Sent fom my S-II running CM-10 by mcm811 powered with DorimanX kernel 7.38
[Android Software/Hacking General [Developers Only]] gu5t3r:
Tried, can't say I feel any difference...

(Maybe because my launcher had Hw Acc enabled when made with HomeCustomizer?)
[Android Software/Hacking General [Developers Only]] Chairmansaab:
Hi, i followed exactly what you said but unfortunately i can't open 98zepentropyfix.

Permissions rxw rxw rxw are given to the same.

Pics:

Q: is there any way to make seeder as foreground app so it wouldn't get killed after some time.

Typing commands in terminal is everyreboot is annoying.

Q: okay so i downloaded the supercharger starter kit. Rc12.zip from post #5021 and then i went into terminal emulator and typed

Su

Sh /sdcard/super*/start*

And got same messege as 98zepentropyfix

Help please
[Android Software/Hacking General [Developers Only]] m1trand1r:
just rename zepentropy fix.txt to .sh and try again...that should run the script:)...

edit: as per supercharger kit i think you have to unzip it before....and just a tipv every time you are trying to run a "script" it has .sh at the end...not .txt or .zip only .sh will do:)

edit2: or just try to remove .txt at the end of script...

Sent fom my S-II running CM-10 by mcm811 powered with DorimanX kernel 7.38
[Android Software/Hacking General [Developers Only]] Chairmansaab:
I tried before by removing .txt from the end but no luck

However this code works fine but its kinda slower than seeder to fill the entropy pool

busybox sysctl -w kernel.random.read_wakeup_threshold=1376

& Yes i extracted the supercharger starter kit.zip to /sdcard

And run the command but terminal said it can't initiate it :(

can't open /sdcard/super..... :( is i am missing something ?
[Android Software/Hacking General [Developers Only]] m1trand1r:
maybe you need SManager apk from playstore....i think that's the one zep couldn't remember be4..and with it all is much easier to do then with TE....try it:) says zep in his famous V6 script:D

Sent fom my S-II running CM-10 by mcm811 powered with DorimanX kernel 7.38
[Android Software/Hacking General [Developers Only]] Chairmansaab:
Hey, i have downloaded SManager . But i am getting this after running Smanager .

You are not running it as root blah blah

Is everything is okay ? Should i proceed with reboot ?
[Android Software/Hacking General [Developers Only]] phonetool:
In SM you MUST elect to run the script as su. Otherwise, NOTHING.

sent via DInc2 on Aerobean
[Android Software/Hacking General [Developers Only]] Chairmansaab:
NSt

Oh yea, i figured it out. I didn't tap that Superuser icon before run. Just completed installation few secs ago.

I didn't install su binaries, will it effect anyway ? I installed everything except su binaries (cause i think supersu always update binaries on its own so why bother ?)
[Android Software/Hacking General [Developers Only]] zeppelinrox:
So far, the only thing that current stays running in the background is the BulletProof_Apps if you've bulletproofed anything with option 16

Update will have a new option (1-9) for the Detailing/database optimizing script tho, if you choose to have it run on boot.

If you pick 1, it runs every boot. If you pick 9, it runs every 9th boot.

Came up with some nifty logging for that too :cool:

I've thought about moving the bootable scripts (detailing, fix emissions, wheel alignment and the new fix alignment) to a submenu but been too busy to bother lol

So... I'm only adding the boot interval option to the Detailing and not the others because zipalign, when it runs on boot, skips previously zipaligned apps so that's fast and fix emissions will apply permissions every run, but that does it super fast too.

There's just more overhead to the detailing script and running it every boot isn't necessary unless you reboot only once a week lol.

Like I said in the other thread, you can just add it to any existing boot script.

Another test to try is the disable it in dev options, and test with only egl.cfg file changes - with and without the edit.

chown 0.0 98ZepEntropyFix
chmod 777 98ZepEntropyFix

But I dunno why some users are using both the seeder and the sysctl tweak.

If you have the sysctl run on boot, it will be full by the time you get around to doing anything - and it stays full without having to run a binary in the background all the time.

Not needed for SuperSU
[Android Software/Hacking General [Developers Only]] Chairmansaab:
Okay , so now i am running Supercharger starter kit, whats next ?
[Android Software/Hacking General [Developers Only]] zeppelinrox:
I have no clue as to what you wanna do.

All you had to do was add the sysctl command to an existing boot script.

I see you have SSS1TCPtuner so why not just add it into there?

Add it to the bottom, make sure there's a blank line at the end, and save.

Doubt it will do anything with seeder running anyway.

It's like shoveling snow off your driveway twice - in the summer.
[Android Software/Hacking General [Developers Only]] Chairmansaab:
Ri

i have a problem. I had seeder and SSSITCPTuner before running perfect but now they are empty 0bytes files:(

I have init.d.bak folder too which was created when i deleted init.d files from recovery.(siyah recovery)

Whenever i transfer any file from init.d.bak folder to init.d they show 0bytes and they are actually empty files now (check using textpad)

So i can't put any script now.

I think you misunderstood, i was talking about Supercharger V6 not sysctl command.

I want to know what to do next ? You had mentioned on #5023 post that it does NOT include any supercharger script so it means i have to download script now ?

Where i can get latest script ?
[Android Software/Hacking General [Developers Only]] hoholee12:
Hey zepp, do you think & command will do?

It runs on my phone. except it doesnt appear on smanager but i think it works:)(values change)

maybe this was the solution what you were talking about?(bootloop thing)

I love potatoes:D
[Android Software/Hacking General [Developers Only]] zeppelinrox:
When copying to init.d make sure system is mounted r/w.

Well SuperCharger... just run the script.

Patch services.jar with ultimatic patcher... that's about it lol

Yep "& blahblah" will execute blahblah in a separate process.

That way, the first script doesn't wait for blahblah to finish and keeps on going.
[Android Software/Hacking General [Developers Only]] Chairmansaab:
T from te

I already have that option ticked.

LMAO. so that was the script. I thought i need to download something and execute it from terminal or what not,

Anyway that was quite simple then.

Patch services :eek: OMG i dunno have pc right now. Can you help please ?
[Android Software/Hacking General [Developers Only]] a-id:
Why every 3 hours? I think must be a choice: 3, 6, 12 and 24 hours...

But why when I used Supercharger with vac, zepalign and fixfc boot time always increased a lot? And when I deleted all scripts boot time became fast?

Отправлено с моего GT-I9000 через Tapatalk
[Android Software/Hacking General [Developers Only]] Daniel D.:
Just a question: When will the new update be released (only SuperCharger or both scripts)? Just asking if I should wait one or two days or create a new ROM version now.
[Android Software/Hacking General [Developers Only]] hoholee12:
Bro your op is very big

xda app force closes even before i get to read the changelogs.

lol:p

I love potatoes:D
[Android Software/Hacking General [Developers Only]] m1trand1r:
:what:...my xda app doesn't fc when looking at OP...:eek:....looks like you have RAM problems on your phone...when i was using my galaxy 3 aka apollo gt-i5800 with 256mb of ram....xda app fc'ed too...due to low ram on loading OP....now it doesn't....so...OP is just fine and allways was...:D

Sent fom my S-II running CM-10 by mcm811 powered with DorimanX kernel 7.38
[Android Software/Hacking General [Developers Only]] mumaster20:
Sounds awesome! Testing it now on my good old Galaxy S :D
[Android Software/Hacking General [Developers Only]] eddydc1:
same problem for me :D
[Android Software/Hacking General [Developers Only]] zeppelinrox:
By how much?

Things may take a bit longer because there's more stuff going on at boot but if it takes 5 minutes to run the 3 scripts separately, boot time shouldn't be prolonged that long as you'd see the desktop before all the scripts are finished.

You can test by running the 3 scripts with script manager and see how long all 3 take to run.

Boot time shouldn't be prolonged by the same amount of time - it should be much less.

edit: oh yeah about the engine flush - it would be user selected but I was thinking from 1 to 9 hrs.

SuperCharger, KAK, 3G TurboCharger, SuperCharger Starter Kit, BusyBox installer with BusyBox 1.21 are all due for updates soon.

Some by Monday... maybe Sunday... heh...

Oh that's due to the thanks in the OP :P

Can you load it with a regular browser?
[Android Software/Hacking General [Developers Only]] BootloopedMillennials:
So I added this command to the 99SuperCharger script so it runs upon boot (instead of me running the command in terminal emulator every reboot). Problem is now things have become extremely slow upon boot and RAM has dropped considerably (down to 40MB's free). Think I screwed something up, any ideas why zeppelinrox?

About 5 minutes after boot the speed is back to normal but apps take forever to open (this is due the drop in RAM down to 40MB's).
[Android Software/Hacking General [Developers Only]] zeppelinrox:
Sounds like 99SuperCharger didn't run.

Check if the minfrees match and OOM grouping fixes are in effect.

It shouldn't use up ram or effect free ram.

When editing scripts, make sure to leave a blank line at the end.

Safest bet is to add it in where the other sysctl settings are and do it on the phone itself so the file remains in *nix format.
[Android Software/Hacking General [Developers Only]] BootloopedMillennials:
That was exactly the issue. Had to rerun V6 Supercharger, Guess I can't add that command to that specific script.

I added the command in the kernel section of that script (where the other sysctl commands were) and did leave a space at the end. Followed the same format as well.
[Android Software/Hacking General [Developers Only]] phonetool:
That line is already in the kak script, just have to edit it for 1376 from 128 (or whatever it was).

Running it once should be enough, right? Or does it have to run every boot?

-CM7 on DInc2
[Android Software/Hacking General [Developers Only]] GermainZ:
When my xda app doesn't crash straight away, the space taken by the thanks is more than the total space taken by all the first page. Then it crashes. ;)

Ended up opening it in a browser (works great).
[Android Software/Hacking General [Developers Only]] morris2003:
With regard to tweak TCP in build.prop, I saw that some recommend:

# Net tweaks
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.lte=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.hsdpa=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.umts=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.hspa=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.gprs=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.edge=4096,87380,256960,4096,16384,256960

but in V6 Supercharger in build.prop adding:

#V6 SuperCharger Tweak
net.tcp.buffersize.default=6144,87380,110208,6144,16384,110208
net.tcp.buffersize.wifi=262144,524288,1048576,262144,524288,1048576
net.tcp.buffersize.lte=262144,524288,3145728,262144,524288,3145728
net.tcp.buffersize.hsdpa=6144,262144,1048576,6144,262144,1048576
net.tcp.buffersize.umts=6144,87380,110208,6144,16384,110208
net.tcp.buffersize.hspa=6144,87380,262144,6144,16384,262144
net.tcp.buffersize.gprs=6144,8760,11680,6144,8760,11680
net.tcp.buffersize.edge=6144,26280,35040,6144,16384,35040

Which ones are more correct?

Should have a larger buffer?
[Android Software/Hacking General [Developers Only]] GermainZ:
Supercharger's entries are optimized on a per network basis.

The other one is just maxed out.

---------- Post added at 02:07 AM ---------- Previous post was at 02:04 AM ----------

Hey zep, I think the teaser has a slight bug. When applying the Misc. & 3G tweaks, it tries to use the local.prop file even when it's told to use the default.prop file.

I noticed it because I don't have a local.prop file, so it outputted errors (I can't run it right now, but it's something like this; the error itself shouldn't be relevant, but just in case):

sed: couldn't find local.prop
[Android Software/Hacking General [Developers Only]] zeppelinrox:
Makes no sense to have the same values for all connections when some are real slow and some are real fast.

I'll have a look.

Did it write to build.prop tho?

Use lower settings like calculated.

Why would you pick aggressive 512 when you don't even have 400?
[Android Software/Hacking General [Developers Only]] DroidofSpades:
Just to confirm..

Thanks by the way for the prompt reply, Zeppelinrox. I appreciate it.

Just to confirm, you are talking about using the "Quick V6 Cust-OOMizer" (option 10), right? Then use the recommended values for me.

Apart from that, do you think I missed any steps considering I don't notice the difference?

In your second post on this thread, I found this "So the mod below is for getting the Launcher at a SuperCharged Priority on ICS!

This is akin to the ADJ entries in build.prop or local.prop on earlier Android ROMS which don't work on ICS."

Is this necessary for me?

Anyway, thanks again. :)
[Android Software/Hacking General [Developers Only]] mixednuts:
I believe you've already done that when you ran the Ultimatic Patcher. :p
[Android Software/Hacking General [Developers Only]] zeppelinrox:
Hey I came up with a new trick!

It's mainly applicable to stock roms without init.d boot scripts tho.

If you run /data/97BulletProof_Apps.sh, you no longer have to keep it running.

Run it once, wait 30 seconds, then the script kills itself after relaunching itself.

You can close script manager and the new instance stays running just like it was launched with a boot script lol

Same trick will come in handy for the automatic fast engine flush...
[Android Software/Hacking General [Developers Only]] hoholee12:
im guessing while and if and ps and killall and sleep command?

I love sweet potatoes:D
[Android Software/Hacking General [Developers Only]] Westnile:
I wish I could do the battery calibration on my phone but stupid built in battery
[Android Software/Hacking General [Developers Only]] zeppelinrox:
What do you mean?

I no longer need the while loop anyway ;)

Well you can use the caibration script to make sure it charges properly.

That's the main point of it anyway.
[Android Software/Hacking General [Developers Only]] Kitschki:
Meh still waiting for official jb to be released –_–... Supercharging will be #1 on my list :cool:
[Android Software/Hacking General [Developers Only]] DroidofSpades:
Cool!

Thanks man. But how come it says:

================================================

Nitro Lag Nullifier is NOT Installed!

================================================

BulletProof Apps Script is NOT Installed!

================================================

I haven't seen any speed improvements yet..

Thanks again!
[Android Software/Hacking General [Developers Only]] Kitschki:
Because u didnt install either one of them i guess. You can install them with the script
[Android Software/Hacking General [Developers Only]] morris2003:
Thanks for your answer.

Looking at your values ​​are optimized.
[Android Software/Hacking General [Developers Only]] zeppelinrox:
Yeah... I leave no stoned unturned and leave fingerprints everywhere ;)
[Android Software/Hacking General [Developers Only]] mixednuts:
Experiencing the same. Attached is my build.prop
[Android Software/Hacking General [Developers Only]] Stevethegreat:
Everyone seems to care about the launcher but I never cared about that damn thing. I mean it's completely useless once you have the apps you're working on open and it eats too much memory and to top it off it's too damn hard to kill. I love supercharger but I'm not using unless and untill I'd find a way to reverse some of its function (I.e. to *always* kill that ram hungry bloat called the launcher), is there sonmething I can do?

Thanks for your hard work btw...
[Android Software/Hacking General [Developers Only]] DroidofSpades:
No change

lol, I did what Zepp said and used the Quick V6 Cust-OOMizer option and using the values the calculator told me, still no speed improvements.

I mean, I like this script, but just wondering how to actually improve my Xperia U's performance (no wake up lag, no delay in launching apps..etc).
[Android Software/Hacking General [Developers Only]] mixednuts:
Did you try the Hard-to-Kill setting?

---------- Post added at 05:07 PM ---------- Previous post was at 05:06 PM ----------

Did you run his KAK as well?
[Android Software/Hacking General [Developers Only]] Stevethegreat:
Yeah but how can I reverse its usage (I.e. make it "easy to kill")?
[Android Software/Hacking General [Developers Only]] Computoncio:
Sorry about the ot but i have no words for this. :eek::confused::sly:

Phone: Samsung Galaxy SII - GT-I9100

Kernel: Dorimanx kernel v7.38

1st ROM : RR JB v3.1.3 (Online)

2nd ROM : Empty

MODEM: Modem+RIL - XXLPS

ROOT APP: SuperSu v0.99

MODS: My mods, ASUL v4.2 and JusTunBeam v6.1.3
[Android Software/Hacking General [Developers Only]] zeppelinrox:
unsupercharge is what you want
[Android Software/Hacking General [Developers Only]] m1trand1r:
he obviously wants tons of launcher redraws, and battery eating stuff back:D:eek::what:...lol..

Sent fom my S-II running CM-10 by mcm811 powered with DorimanX kernel 7.38
[Android Software/Hacking General [Developers Only]] Stevethegreat:
I do not use the launcher why would I? Initially I open the apps I use the most and then go from one to another using recent apps menu. It's far faster to work that way but the launcher eats too much ram so I kill the damn thing but it keeps ressurecting :eek: .

I do not have launcher redraws because I do not use it (apart from the very first time). The launcher is a very innefecrive and slow way to do things on tablets, I've even raplaced the home button with the recents button... now all its left is to kill it completely and let it never to be resurrected again, an "easy to kill" switch....

I would but I like the the benefits of supercharger, now all I need is to reverse what the hard to kill script does. In other words I want it to kill the launcher everytime it finds him lurking about, up in the roof, down to the hallway, strolling in the neighbourhood... kill 'im.

To be serious for a bit, my tablet has little ram and using it as wisely as possible would greatly enhance my experience, since I never use the launcher it's wise to have him being easily killed, no?
[Android Software/Hacking General [Developers Only]] mixednuts:
Hard-to-Kill is the killable launcher... other than that, do what zep said: unsupercharge.

Or, change the boomstick to make something else appear as your launcher. :p
[Android Software/Hacking General [Developers Only]] zeppelinrox:
1. Replace the launcher with the lightest one you can find

2. If ICS or above, don't patch services.jar

3. If pre-ICS, edit your prop file's SuperCharger entry so it reads: ro.HOME_APP_ADJ=15
[Android Software/Hacking General [Developers Only]] Stevethegreat:
My undestandibg is that enabling hard to kill makes the launcher unkillable as it is in my case. Since the supercharger script is so adapted at killings apps (and retaining others), I would like to know if it's possible to subvert it and instead use it to keep the launcher always dead. Even without supercharcher he redraws eventually but keeping him dead would ensure he would be out of mind..

If we can somehow put him first in the pool of killable apps so if the os is to kill sth to always choose the launcher first. I'm far from an expert in those matters, but I think that's possible, no?
[Android Software/Hacking General [Developers Only]] zeppelinrox:
Hard to Kill is the weakest of the 3 strengths... which is killable... just not easily.

BulletProof Launcher is the unkillable one
[Android Software/Hacking General [Developers Only]] Stevethegreat:
Thanks for the heads up still somehow I think that modifying the script to do the opposite (I.e. killing the launcher) would had been the best though, I mean if that's possible at all...
[Android Software/Hacking General [Developers Only]] Tomislav Veličanstveni:
still same problem...when I install KAK my phone run into bootloop, I have latest test version of V6 which is great, excellent job, everything is working normal...also I have installed 3G turbocharger, same thing, working great but my phone doesn't like KAK...It won't work even with earlier versions of v6...earlier I have been using GingerDX ROM deodexed and same problem...now I have cm7 alpha 8.3 odexed...I/O tweaks enabled or disabled it doesn't matter, phone won't boot -.- please help :)
[Android Software/Hacking General [Developers Only]] DorianX:
What kind of device do you have? Launcher never has been a problem for me... even on my old g1, you're fighting for about 15-20mb?

Enviado desde mi LG-E730 usando Tapatalk 2
[Android Software/Hacking General [Developers Only]] Stevethegreat:
Mine is in 80s-90s it helps -I guess- that it draws 2.5mpixels (my Res is 1920x1280) in each of its instances...that's more than any other of my apps
[Android Software/Hacking General [Developers Only]] DroidofSpades:
Still the same

Yeah, that's all I did. Btw, I ran Nitro Lag, but caused my values to mismatch, so I un-nullified it. But still...same old Xperia U speed. >.<
[Android Software/Hacking General [Developers Only]] zeppelinrox:
Screw that.

It's easier if you do it yourself.

Just because you have a self important name, nobody cares and the world doesn't in fact revolve around you.

I've entertained you're weird thoughts enough as it is.

You're lucky I even told you what to do. In case you missed the post, go back to make sure you saw it.

Read the comments at the top of 98kickasskernel to turn on debugging.

Then post the log file.
[Android Software/Hacking General [Developers Only]] Stevethegreat:
Heh, my username was/is rather random it doesn't mean anything, my name is not Steve either...

Anyhow I've asked for direction given that you are more accustomed to this type of stuff, if you're not willing to give it I can respect this...

As for my "weird request" your own signature refers to the very same thing "android is everything we need it to be", different needs, different uses; I find weird why people whould need the launcher to something that isn't a phone but I'm not making an issue out of it ;)
[Android Software/Hacking General [Developers Only]] zeppelinrox:
Like I said, I did give you direction.

I also said to go back and make sure you saw the post.