yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] strawhat67:
I have custom rom,so I should go to system/etc/init.d/99supercharger and set "at boot" and "as root" right?
[Android Software/Hacking General [Developers Only]] defiant07:
haha...luv that video...it's classic...some people are perpetual noobs I guess?!?!?

Your English seems pretty good to me...I think you are just being lazy...peep the VIDEO Zep posted a link to...try searching and reading :p.
[Android Software/Hacking General [Developers Only]] zeppelinrox:
I'm pretty sure the bulletproof apps info/instruction is in English.

Actually that's not true.

Disable the viper minfree tweak, genius.

ya you do that.

for good measure, also do it for everything else in the init.d folder.

Oh what the heck, since you're gonna be doing useless things, also do it for /data/99SuperCharger.sh and /system/xbin/99super.

And you're close to ignoramus listville.
[Android Software/Hacking General [Developers Only]] hisname:
i was on viper rom before,the viper minfree tweak can't be disabled.
[Android Software/Hacking General [Developers Only]] brxx1:
=========================================

\\\\\ -=Super DeDuper Snooper=- /////

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

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

Data DeDuping KSM is On But No Data!

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

Current KSM Values:

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

full_scans - 0

pages_shared - 0

pages_sharing - 0

pages_to_scan - 128

pages_unshared - 0

pages_volatile - 0

run - 1

sleep_millisecs - 6000

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

System Awake Time is 24:10:07

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

System Idle Time is 18:34:47

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

System Deep Sleep Time is 61:35:50

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

System Up Time is 85:45:57

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

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

WARNING: Kernel MIGHT Have A Deep Sleep Bug!

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

The above stats are an APPROXIMATION...

...based on timestamps which reflect boot time.

Below is what is likely happening...

...based on info in the /proc/uptime file!

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

System Awake Time is 24:10:07

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

System Idle Time is 18:34:47

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

System Deep Sleep Time is 0:00:00

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

System Up Time is 24:10:07

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

$ export PATH=/data/local/bin:$PATH

$ cat /proc/stat | grep btimebtime 1376979566

$

$ cat /proc/uptime

87100.68 66921.01

$

$ uptime

up time: 3 days, 13:46:15, idle time: 18:35:30, sleep time: 2 days, 13:34:24

$cat /proc/stat | grep btime

btime 1376979829

$

$ cat /proc/uptime

87133.77 66942.50

$

$ uptime

up time: 3 days, 13:51:02, idle time: 18:35:43, sleep time: 2 days, 13:38:47

$

Hope i did it right this time (i runner the 3 command a little after the sniper because i needed to paste the output and then copy the command)

Before posting something under this, read the OP. It's scientifically demonstrated that the 98% of the problems that affect xda average user it's caused by the lack of reading. the 2% left is caused by aliens hacking your phone.
[Android Software/Hacking General [Developers Only]] zeppelinrox:
A viper ROM dev specifically pointed out that it can be when another user said the same thing.

1 btime does indeed change when it shouldnt

2 /proc/uptime stops updating with the screen off.

3 the uptime command seems to work properly. I wonder where it gets the info from since I thought it read from /proc/uptime.

4 obviously ksm doesn't work. Its turned on (run = 1) but there's 0 activity.
[Android Software/Hacking General [Developers Only]] lowpro3210:
whoever made that video deserves a pat on the back..its epic and made me LOL
[Android Software/Hacking General [Developers Only]] hisname:
it was me

just joking:D
[Android Software/Hacking General [Developers Only]] GermainZ:
Has that changed recently? I thought the zoom/boom stick only listed running programs?
[Android Software/Hacking General [Developers Only]] zeppelinrox:
FTFY

heh

months ago.

You can do it even without lookin at running processes.
[Android Software/Hacking General [Developers Only]] pitastrudl:
so, after running this beast of a supercharger on my DHD for 1 year I moved to the S4 and just remembered that I could get more out of those 2 gigs of wasted ram. So after 15mins of reading the freakishly cleaned and updated OP(as far as i remember zep didn't update it for a looong time :p) I was 100% supercharged and couldn't keep up with the phone.

edit: oh im running 4.3 google edition ROM
[Android Software/Hacking General [Developers Only]] bilal1947:
sms sent issue

using cm7 rom can't send sms. it was working fine before, god knows what happened after v6 script.

tried flashing the rom again and run v6 script and again stuck into this issue.

tried puting sim in to another phone and adjusting the smsc number which i have noted for this day, had also tried dialing *#*#4696#*#* and putting the number which is +96895001016 and udpate it. still didnt work.

need help here

Only Go sms is sending smsg, why the default or other sms apps not sending sms. any idea.

thanks
[Android Software/Hacking General [Developers Only]] zeppelinrox:
Apples and oranges.

Stick with gosms.

Problem solved.

Got a lolcat?
[Android Software/Hacking General [Developers Only]] brxx1:
Oook it's something that i can resolve or the problem is ununderstandable (like it seems to me) or something that (since i don't have any visible issue) i should just live with?

Before posting something under this, read the OP. It's scientifically demonstrated that the 98% of the problems that affect xda average user it's caused by the lack of reading. the 2% left is caused by aliens hacking your phone.
[Android Software/Hacking General [Developers Only]] pitastrudl:
So i was 100% supercharged, and the boom stick kept saying that the system.process.acore was my home launcher which wasnt, but was nova. so re-patched the service.jar and now it's fixed. But something still confuses me. The script says im 100% supercharged but it says that the OOM groupings are not in effect, so i chose the 99supercharge.sh to run at boot with root by scriptmanager and it still says the same, even though im 100% supercharged. Is it becuase in drivers options i didnt choose the kernel tweaks?

i also found this in the thread, by zep:

but in the script it says that the supercharger adj entries are patched in

i hope im not missing something important.

edit: in the ran_superchargerlog it shows that it ran from boot, and when i manually started the 99supercharger.sh, the ran_supercharger.log in the new entry, it said that there is no need to apply settings.

edit2:And suddenly, the vroom stick says, that the home launcher is android.process.acore and in the status it shows that the launcher is bulletproffed, even though the services that got supercharged, i selected hard-to-kill. on the start of the script it asks me "erm, is your launcher home.teslaswl.launcher?" so ofc i select yes. nova launcher is in visible_app oom grouping ADJ=1.
[Android Software/Hacking General [Developers Only]] zeppelinrox:
just forward the info to whatever dev for your ROM/kernel.

I'd imagine that theyd at least address the borken ksm.

post a screen shot of the inconsistency and the broomstick log im /data

Btw which v6 and busybox builds are you using?
[Android Software/Hacking General [Developers Only]] error404:
Here is the log.
[Android Software/Hacking General [Developers Only]] pitastrudl:
im using the latest V6 9 RC12 53457_fix and busybox is 1.20.2-linusyang

this is what asks me at the start,

saying that the launcher is bulletproof and the oom grouings are not in effect

100%supercharged

here are the boom sticks

https://www.dropbox.com/s/40p8titfrhn5a2j/!bOOM_Stick_COOKED.log

https://www.dropbox.com/s/478jbf6phhqbyzo/!bOOM_Stick_RAW.log

im on 4.3 google edition rom
[Android Software/Hacking General [Developers Only]] mrjoy:
Is this mod only for powerful multitasking? then can i use other mods too if those mod would not conflict with super charger?
[Android Software/Hacking General [Developers Only]] Daniel D.:
You won't need another "tweak".
[Android Software/Hacking General [Developers Only]] Jar3112:
Other stuff shouldn't conflict as long as isn't touching ram usage, entropy or cache flushing.

Be warned, though, that using many script/mods at the same time usually doesn't speed up your phone, instead they are willing to slow it down after some time.

A custom kernel with v6 mods integrated or a stock kernel with the manual addition of v6 supercharger is generally more that enough. My opinion though.

Sent from my Galaxy Nexus
[Android Software/Hacking General [Developers Only]] zeppelinrox:
try rc7t6.

services.odex should be almost the same size as before

Ya weird.

Try a different busybox
[Android Software/Hacking General [Developers Only]] pitastrudl:
tried the 1.21 from stericson, updated with the busybox app . It seems it works, since it shows correctly with the vroom stick. And it detects the launcher correctly, thus in the staus check, it says its DIE-hard, not bulletproofed. But it still says, that the OOM groupings are not in efect, but i checked the ran_supercharger log and it did run. Even though it says that the OOM groupings are not in effect, im 100% supercharged ::confused:
[Android Software/Hacking General [Developers Only]] zeppelinrox:
OK do:

cat /sys/module/lowmemorykiller/parameters/adj
[Android Software/Hacking General [Developers Only]] IT_Fan:
Should I use this along with Greenify ?
[Android Software/Hacking General [Developers Only]] defiant07:
'Should' is subjective :p. However, you can,

should

you desire to do so, use this along side greenify...I do ;).

The only stuff you really need to avoid is ram related stuff, but V6 has mechanism for dealing with those :D.
[Android Software/Hacking General [Developers Only]] demoncamber:
Hey guys, I have a slight issue: So I decided to retry v6 and ultimatic again after a while, and I've narrowed it down to getting stuck at the splash screen whenever doing a super clean and restart or engine flush then reboot. Any ideas?

It'll only boot back up if I backup then restore a nandroid, but there has to be some way around this.

It will then repeat the issue if I do the above again.

This is on all latest scripts and stock rooted t989 jellybean, with Tiberius kernel.

Sent from my SGH-T989
[Android Software/Hacking General [Developers Only]] zeppelinrox:
OK well oom grouping is in effect I'll have to scrutinize the syntax for checking that.

Makes no sense at all lol

using latest ultimatic and v6?

If you patch and reboot without doing superclean its fine then?

Using link2sd?

Try getting a logcat if it bootloops again.
[Android Software/Hacking General [Developers Only]] error404:
Still bootlooping... =(
[Android Software/Hacking General [Developers Only]] zeppelinrox:
No errors show up this time but the new services.odex is a lot smaller than original.

If you want to try again, copy and paste all the info from the console window as some errors may not show up in the log.

Don't reboot tho.

Restore original services.odex before rebooting again.

It may even be a smali bug where some folders aren't put back in services.odex which is why the new one is smaller.
[Android Software/Hacking General [Developers Only]] error404:
if the error is in odex files, if i deodex my rom?
[Android Software/Hacking General [Developers Only]] zeppelinrox:
That should work.

Haven't had any similar issue with deodex
[Android Software/Hacking General [Developers Only]] demoncamber:
Yes Zepp, funny right? It will work fine and tell me I have 100% supercharger status if I install everything and do not do a superclean, but a regular reboot.

No link2sd and all latest black dog v6 and ultimatic.

However, if I patch everything then do a superclean, go into recovery then do a nandroid, then just restore that very nandroid, it will boot up fine and report 100% supercharge.

My stock rom isn't deodexed, could that have something to do with it?

I'll report back when my phone is in a working state due to a separate issue with logs :D :D
[Android Software/Hacking General [Developers Only]] zeppelinrox:
Say can you run supercharger with debugging on like so?

sh -x /sdcard/V6*.sh

Yeah that's weird...

Does wiping dalvik in recovery cause any issue?
[Android Software/Hacking General [Developers Only]] hisname:
bad news, found a bug.... :(

well, whenever you see me, there is a bug in your script :p
[Android Software/Hacking General [Developers Only]] pitastrudl:
Yeah, I ran that cat command trough adb shell. this current one started the v6 script, though it ran like it ran for the first time, taking me to the driver options right away, and its displayin what the script manager doesnt, i assume.
[Android Software/Hacking General [Developers Only]] zeppelinrox:
Feel free to continue keeping it to yourself

Yeah I'd need to see the output of the sh -x command as it shows what it's doing behind the scenes.
[Android Software/Hacking General [Developers Only]] demoncamber:
Not before or after the installation of your scripts, no.
[Android Software/Hacking General [Developers Only]] zeppelinrox:
Ok run this and post the output:

echo /*/dalvik-*
[Android Software/Hacking General [Developers Only]] pitastrudl:
[MENTION=3357461]zeppelinrox[/MENTION] here is the output, could have put it on pastebin, but my chrome froze(lol). https://www.dropbox.com/s/gdrpsm90iqxjb1p/Document_2.rtf
[Android Software/Hacking General [Developers Only]] zeppelinrox:
It's indeed 100% and I see my fubar :o

Funny how that's been unreported lol
[Android Software/Hacking General [Developers Only]] pitastrudl:
glad to be of help.
[Android Software/Hacking General [Developers Only]] hisname:
bug 1:look at this

bug 2:i have not patched my services.jar yet, but the script says I patched it.

here's the boom stick
[Android Software/Hacking General [Developers Only]] zeppelinrox:
Both are irrelevant, really.

I don't even see a real launcher running.

Did you kill it just to be a pita?
[Android Software/Hacking General [Developers Only]] hisname:
I did no killing
[Android Software/Hacking General [Developers Only]] zeppelinrox:
So what's your launcher.

Have it running then see what it says.
[Android Software/Hacking General [Developers Only]] hoholee12:
Hey zepp,

i found a more accurate way of detecting homelauncher by looking at process threads.

# Launcher detector
fail=1
for i in $(ls /proc | grep -v "[a-zA-Z]"); do
for j in $(ls /proc/$i/task | grep -v $i); do
fail=0
if [ $(cat /proc/$i/task/$j/comm) == launcher-loader ]; then
break
fi
fail=1
done
if [ $fail -eq 0 ]; then
break
fi
done 2>/dev/null
if [ $fail -eq 1 ]; then
echo could not detect your launcher.
else
echo your launcher name is $(cat /proc/$i/cmdline) and pid is $i
fi

Hope this helps:)

Sent from my
[Android Software/Hacking General [Developers Only]] riotaruna:
hello bro Zep, how would i know if i have managed to patch services.jar, because i visited web android.mimic.ca and it automatically....
[Android Software/Hacking General [Developers Only]] hisname:
grrr, can't seem to replicate the bug. but the vroom stick still have those no files or directories thingy popping up
[Android Software/Hacking General [Developers Only]] zeppelinrox:
Just so you don't feel bad, your buggin had me look into making vrOOM Stick quicker - by doing away with busybox find and searching packages.xml instead - easier than I thought and I kanged my fix emissions/fixalign code for the packages.xml bit.

heh.

You ain't my bro.

First of all, my bro knows how to read.

Reboot and try again.

Didn't know about the launcher-loader thing but it don't work on gingerbread as far as I can tell.

Not sure about ICS.

On JellyBean I can have any number of hits for "launcher-loader" if there is more than one launcher running.

I used to grope all the numerical proc/folders but found it more efficient to just get a list installed launchers from packages.xml and see if those are running with pgrep.

This code is quicker tho:

for i in `busybox ps | awk '!/]/{print $1}'`; do
if [ -f "/proc/$i/oom_adj" ] && [ "`awk '/launcher-loader/' /proc/$i/task/*/comm`" ]; then
echo "`cat /proc/$i/cmdline` is a launcher with adj `cat /proc/$i/oom_adj` and PID $i"
launcherloader="$launcherloader `cat /proc/$i/cmdline`"
fi
done
if [ ! "$launcherloader" ]; then echo "No launcher detected... sucks to be you! lulz :p"; fi

I'll add $launcherloader like so...

for launchers in $launcherloader `awk -F [\"\/] '/set.*\/*.Launcher/{print $2}' /d*/system/packages.xml` `awk -F \" '/package name/&&/adwfreak|zeam|tw3|tw4|tw5|nextgen|shell|home|trebuchet|launcher/{print $2}' /d*/system/packages.xml` adwfreak zeam tw3 tw4 tw5 nextgen shell home trebuchet launcher acore; do
validlauncher=`pgrep -l $launchers | awk '!/\/|notification|gowidget|downloadservice/{print $2}'`
if [ "$validlauncher" ] && [ ! "`echo $llist | grep $validlauncher`" ]; then llist="$llist $validlauncher"; fi
done

Just to future proof I guess in the even some launcher has a weird name that doesn't contain "launcher" or "home".

Having said all that, finding a running launcher is easy.

Finding out if it's supercharged is the hard part.
[Android Software/Hacking General [Developers Only]] hisname:
FTFY
[Android Software/Hacking General [Developers Only]] jasonkhoo87:
I see. It work now. So everytime need to reboot if i encounter write error.
[Android Software/Hacking General [Developers Only]] zeppelinrox:
Must be a female android.

Those ones get moody 12 times a year and they prefer to not be tweaked at those times.
[Android Software/Hacking General [Developers Only]] hisname:
#women
[Android Software/Hacking General [Developers Only]] zeppelinrox:
Sooo... a lil status update...

little snippets of the main screen

================================================
Whoah... Your Entropy-ness is THIS BIG => 4096
================================================
[COLOR=Red] Super Duper DeDuper is NOT In Effect!
================================================
Data DeDuping UKSM savings - 2.40 MB!
================================================
0.65 = Benefit/Cost Ratio -> HIGHER IS BETTER!
7.32 Benefit Ratio x Shared 0.33 MB = 2.40 MB
11.32 Cost Ratio x 2.40 MB = 27.20 MB (Unique)
================================================
1 - Full Scans SINCE BOOT - Check Option #22![/COLOR]
================================================

=============== Start Up Scripts ===============
16. BulletProof Apps {Hit or Miss}
17. Engine Flush-O-Matic {ReCoupe RAM Booster}
18. Detailing {Vacuum & Reindex SQL DBs}
19. Wheel Alignment {ZipAlign APKs}
20. Fix Emissions {Fix FCing Errors}
21. Fix Alignment {ZipAlign & Fix FCs}
}
============== Moar Toolz 'n Stuff =============
[COLOR=Red]22. Super DeDuper Snooper {UKSM Analyzer Tool}[/COLOR]
23. Nitro Lag Nullifier {Experimental}
24. System Installer {Terminal Usage}

Stuff done so far...

tweak zipalign/fix emissions/fix align fix bugs and asec compatibility
tweaked dalvik heapsize and heapgrowthlimit - heapsize is now 20% of RAM (up from 16%) and heapgrowthlimit is 10% (was the same as heapsize ie. 16%)
better logging (ie. recording errors)
if init.d exists check for bootlogs and if init.d works
display last rans for all boot scripts just like BPApps and FOM
tweak frandom code - now it also enables frandom if available but not enabled.
get rid of init.${ro.hardware}.rc
sdtweak behaviour
many code tweaks
faster vrOOM Stick!
tweak userinfo
check if root and /system are mounted read only (gives a yellow flag and returns to menu if so)
Added Super Duper DeDuper (KSM tweak - enable/disable/make battery friendly)
Added Super DeDuper Snooper to menu (KSM Stats/Analyzer)
experimental status bar "fix"?

Still gotta test tho.

I wanna throw in the auto bulletproof current app idea and tweak the init.d bootscript checking...

Attached an updated deduper snooper... just tweaked the code and interface a bit.
[Android Software/Hacking General [Developers Only]] eushaun99:
Here ya go

=========================================
\\\\\ -=Super DeDuper Snooper=- /////
=====================================

================================================
Data DeDuping KSM savings - 42.38 MB!
================================================
22.38 = Benefit/Cost Ratio -> HIGHER IS BETTER!
29.01 Benefit Ratio x Shared 1.46 MB = 42.38 MB
1.30 Cost Ratio x 42.38 MB = 54.93 MB (Unique)
================================================
3 - Full Scans SINCE BOOT.
4 min 37 secs (277 seconds) Needed Per Scan
KSM Executes 197.86 Times Per Full Scan
================================================
KSM Per Minute Summary (Based on Awake Time)
KSM Executes 42 Times.
9.18 MB - Scanned Beneficially Per Minute.
11.90 MB - Scanned Wastefully Per Minute.
================================================

Current KSM Values:
===================

full_scans - 3
pages_shared - 374
pages_sharing - 10850
pages_to_scan - 200
pages_unshared - 14171
pages_volatile - 84426
run - 1
sleep_millisecs - 1400

================================================
System Awake Time is 0:18:30
================================================
System Idle Time is 0:21:21
================================================
System Deep Sleep Time is 0:00:00
================================================
System Up Time is 0:18:30
================================================
[Android Software/Hacking General [Developers Only]] otterbvrn:
=========================================
\\\\\ -=Super DeDuper Snooper=- /////
=====================================

================================================
Data DeDuping UKSM savings - 36.87 MB!
================================================
7.16 = Benefit/Cost Ratio -> HIGHER IS BETTER!
14.00 Benefit Ratio x Shared 2.63 MB = 36.87 MB
1.96 Cost Ratio x 36.87 MB = 72.14 MB (Unique)
================================================
3 - Full Scans SINCE BOOT.
57 min 44 secs (3464 seconds) Needed Per Scan
UKSM Executes 34640.00 Times Per Full Scan
================================================
UKSM Per Minute Summary (Based on Awake Time)
UKSM Executes 600 Times.
0.64 MB - Scanned Beneficially Per Minute.
1.25 MB - Scanned Wastefully Per Minute.
================================================

Current UKSM Values:
===================

abundant_threshold - 10
cpu_governor - [full] medium low quiet
cpu_ratios - 20 40 MAX/4 MAX/1
ema_per_page_time - 9370
eval_intervals - 1000 500 200 50
full_scans - 3
hash_strength - 64
max_cpu_percentage - 95
pages_scanned - 565002
pages_shared - 674
pages_sharing - 9438
pages_unshared - 18469
run - 1
sleep_millisecs - 100
sleep_times - 23144
thrash_threshold - 50

================================================
System Awake Time is 3:50:59
================================================
System Idle Time is 1:59:14
================================================
System Deep Sleep Time is 10:03:16
================================================
System Up Time is 13:54:15
================================================
[Android Software/Hacking General [Developers Only]] pitastrudl:
So after I've searched the thread and google, I cant really put my finger on what Super DeDuper Snooper is about. My guess is that it detects how much time the device is in deep sleep and KSM efficiency? As far as i've looked up, KSM efficiency is basicly taking same processes and merging them in to one, thus increasing RAM space which is a must for low-end devices, so there is a bit of a performance boost?
[Android Software/Hacking General [Developers Only]] hisname:
am I missing something? how come this thread says not to activate 3G turbo charger if you aren't living in the USA?
[Android Software/Hacking General [Developers Only]] mstdzw:
HI, some of this settings is for lower devices.

What of this tweaks is best for MTK6589 1GB RAM? I have V6 installed but realy don't know what of this is settings may help.:eek: