Database Info

Cyanogized Compache nocturna.JacHeroz (jachero 2.7.3MOD with compache support)

THIS HAS NOTHING TO DO WITH JAC 2.7.4 This is different!!
JacHeroski cyanagized with compache swap
07/21/09 1:27PM
download rename to update.zip and put on the phone flash as normal requires special spl and new radio
also requires ext2/3 swap and linux swap partitions
Nocturna.JacHeroZ cyanogized 1.0b
Much thanks to: justanothecrowd,cyanogen,ccyrowski,haykuro,jesufreke,D.b. hates you,drizzydrakerogers,h.nocturna, and jasherai
H.NOCTURNA! thanks for those .ko files or i wouldve been up till like 5 am looking
Im at work right now so i cant really put this all together quite yet but ill give you the rundown of how it will be done
if you dont wanna use the precompiled update.zip to avoid wipe
First download and flash Jachero 2.7.3
Then download jacheroski 1.4c and unzip in the folder you will need to things the "boot.img" in the main folder then jump into the /system folder and go ahead and copy the "modules" folder as well then open up /system/lib/modules/ and copy the wlan.ko
also youll need /system/bin/a2sd.sh
you should have 4 files pulled from this rom:
Modules
Boot.img
wlan.ko
a2sd.sh
heres what you do with those things:
Take modules and
adb push modules /system/modules/
take boot.img
adb push boot.img /sdcard/
wlan.ko
adb push wlan.ko /system/lib/modules
then please check this post and download the .ko files zipped attached to post
right here!!!
youll need to put these two files onto /system/modules/
one should be ramzswap.ko and xvmalloc.ko
Now for the a2sd.sh .. this script is ran on boot to do apps2sd but you can add to the end of it wich is what we are going to do
you will need to open this i used a word processor on my mac so it worked i duno about windows but you need to add these lines of code and then save it as a seperate document KEEP THE ORIGINAL!
#!/system/bin/sh
insmod /system/modules/xvmalloc.ko;
insmod /system/modules/ramzswap.ko memlimit_kb=32000 backing_swap=/dev/block/mmcblk0p3;
mknod /dev/ramzswap0 b 253 0;
echo 20 > /proc/sys/vm/swappiness;
swapon /dev/ramzswap0;
exit;
THEN adb time agian
adb push a2sd.sh /system/bin/
adb shell chmod 755 /system/bin/a2sd.sh
ok after this is done we need to change over to cyanogens boot.img wich contains his kernel that works with compache
so you either need to do this in adb or in terminal from the phone
$su
#flash_image boot /sdcard/boot.img
#exit
$exit
bingo bango cyanogized now!
ok now its time to reboot the phone
should start up as normal "may take a bit the first boot"
after fully booting up open up terminal app and type the following
$su
#free
(this should display your swap line with numbers in it)
IF YOU GET ZEROS HERE STOP WHAT YOUR DOING AND SKIP TO THE BOTTOM FOR INSTRUCTIONS TO FIX THAT
if you dont get zeros everything is going good
now type the following
$su
#cat /proc/ramzswap
you should get a list of things if it says not found stop what your doign skip to the bottom for instructions to fix it
if it gave you a list of numbers great everythings good enjoy your new faster jachero!
IF YOU GOT ZEROS IN YOUR SWAP LINE OR NO READING FOR ramzswap!!!
Do the following,
take your original a2sd.sh and get in adb
adb push a2sd.sh /system/bin/
adb shell chmod 755 /system/bin/a2sd.sh
adb shell reboot
now....
i suggest doing this in adb but you can type it all in terminal if you want...
type the following to enable compache
$su
#insmod /system/modules/xvmalloc.ko
##insmod /system/modules/ramzswap.ko memlimit_kb=32000 backing_swap=/dev/block/mmcblk0p3
#mknod /dev/ramzswap0 b 253 0
#echo 20 > /proc/sys/vm/swappiness
#swapon /dev/ramzswap0
#cat /proc/ramzswap
should show a list of numbers probably all at 0.. this is good
reboot phone now (the insmod and swap on stick after reboot)
tada!!
whenever i get off work ill compile this and post the update.zip for those who dont feel like doing this much work
this is not a SUPER customized rom or anything i just put together pieces i wanted to enable the compache swap on this... i feel it increases responsivness ALOT and alot smoother interface using compache and linux swap
lmk about any bugs or anything
h.nocturna said:
I actually have my update.zip completely finished. I threw it together last night, but I lost multi-touch as well as the weather update for the "Current City" everywhere else would update, but it would say no weather information for my current location. =/ I can throw the update.zip up if you guys want. I have basically the exact same changes that Zarboz had since I followed his instructions... lol
EDIT: Uploading now...
http://depositfiles.com/files/k449ghyxq
If anyone knows how to fix the weather problem or get multi-touch back, let me know and I'll update, and resign for you guys.
Compcache set up: push userinit.sh from zip to /system/sd/
-or-
Code:
#!/system/bin/sh
insmod /system/sd/xvmalloc.ko;
insmod /system/sd/ramzswap.ko memlimit_kb=32000 backing_swap=/dev/block/mmcblk0p3;
mknod /dev/ramzswap0 b 253 0;
echo 20 > /proc/sys/vm/swappiness;
swapon /dev/ramzswap0;
exit;
Click to expand...
Click to collapse
'
TODO LIST!
Multitouch on Cyanogens kernel
optimize compache script on boot (reading jasherais posts like crazy)

wow thanks for this, will wait for ya update.zip! out of curiosity, how much automation will your update.zip have? example, after flashing with Jachero 2.7.3, will your update.zip take care of everything else?

trying this now, will report back if it works after im done
Edit: ill quickly compile an update.zip for this, might take a while to upload though

the only problem i encountered when i did this was editing the a2sd.sh and getting it to work after i put it back in the system
if you have to get into terminal and do
su
chmod 755 /system/bin/a2sd.sh
exit
just to be safe
this script also enables the linux swap partition on boot
so your using compache highspeed swap as piramry and linux swap as secondary the compache swap is stored on your ext2/3 partition

Zarboz said:
the only problem i encountered when i did this was editing the a2sd.sh and getting it to work after i put it back in the system
if you have to get into terminal and do
su
chmod 755 /system/bin/a2sd.sh
exit
just to be safe
this script also enables the linux swap partition on boot
so your using compache highspeed swap as piramry and linux swap as secondary the compache swap is stored on your ext2/3 partition
Click to expand...
Click to collapse
I wish I wasn't at work so that I could do this right now!! I guess that I will have to wait a few hours (Plus by then I'm sure someone will have an update to flash. If not I'll make on when I get home and upload it)

i'm gonna try this now. will report back

Diceman4 said:
I wish I wasn't at work so that I could do this right now!! I guess that I will have to wait a few hours (Plus by then I'm sure someone will have an update to flash. If not I'll make on when I get home and upload it)
Click to expand...
Click to collapse
yah when i get off a t 9pm central time ill make a update.zip and get it put up somewhere

I actually have my update.zip completely finished. I threw it together last night, but I lost multi-touch as well as the weather update for the "Current City" everywhere else would update, but it would say no weather information for my current location. =/ I can throw the update.zip up if you guys want. I have basically the exact same changes that Zarboz had since I followed his instructions... lol
EDIT: Uploading now...
http://depositfiles.com/files/k449ghyxq
If anyone knows how to fix the weather problem or get multi-touch back, let me know and I'll update, and resign for you guys.
Compcache set up: push userinit.sh from zip to /system/sd/
-or-
Code:
#!/system/bin/sh
insmod /system/sd/xvmalloc.ko;
insmod /system/sd/ramzswap.ko memlimit_kb=32000 backing_swap=/dev/block/mmcblk0p3;
mknod /dev/ramzswap0 b 253 0;
echo 20 > /proc/sys/vm/swappiness;
swapon /dev/ramzswap0;
exit;

NguyenHuu said:
wow thanks for this, will wait for ya update.zip! out of curiosity, how much automation will your update.zip have? example, after flashing with Jachero 2.7.3, will your update.zip take care of everything else?
Click to expand...
Click to collapse
itll basically be 2.7.3 wiht some minor structure changes
all i really did was add compache support i didint rewrite the whole thing

h.nocturna said:
I actually have my update.zip completely finished. I threw it together last night, but I lost multi-touch as well as the weather update for the "Current City" everywhere else would update, but it would say no weather information for my current location. =/ I can throw the update.zip up if you guys want. I have basically the exact same changes that Zarboz had since I followed his instructions... lol
EDIT: Uploading now...
Click to expand...
Click to collapse
sweet lmk when it gets up and ill put a link on main page
i might crack it open and do some other minor changes i might know why the current city isnt working
##edit## it works on mine .......
MULTITOUCH WILL NOT WORK ON THIS BUILD! due to cyanogens kernel
i dont use it anyway....
lmk when its up

Zarboz said:
sweet lmk when it gets up and ill put a link on main page
i might crack it open and do some other minor changes i might know why the current city isnt working
##edit## it works on mine .......
lmk when its up
Click to expand...
Click to collapse
Its up now. Out of curiosity, do you still have multi-touch on yours?
EDIT: HAHAHAHAHA!! Looks like we got one-upped. JACHero2.7.4 w/ compcache is being uploaded now.

h.nocturna said:
Its up now. Out of curiosity, do you still have multi-touch on yours?
EDIT: HAHAHAHAHA!! Looks like we got one-upped. JACHero2.7.4 w/ compcache is being uploaded now.
Click to expand...
Click to collapse
PSHH dangit
o well wahts the link ill still put it up

Zarboz said:
PSHH dangit
o well wahts the link ill still put it up
Click to expand...
Click to collapse
I added the link to my other post on page 1

h.nocturna said:
I actually have my update.zip completely finished. I threw it together last night, but I lost multi-touch as well as the weather update for the "Current City" everywhere else would update, but it would say no weather information for my current location. =/ I can throw the update.zip up if you guys want. I have basically the exact same changes that Zarboz had since I followed his instructions... lol ..snip..
Click to expand...
Click to collapse
I just set this up myself using the directions in the first post, and I can get weather info for my current location...
EDIT: And it flies now... Here's my info...
Code:
# free
free
total used free shared buffers
Mem: 97908 96472 1436 0 92
Swap: 94672 14208 80464
Total: 192580 110680 81900
# cat /proc/ramzswap
cat /proc/ramzswap
DiskSize: 32000 kB
NumReads: 1946
NumWrites: 3848
FailedReads: 0
FailedWrites: 0
InvalidIO: 0
PagesDiscard: 0
ZeroPages: 276
GoodCompress: 75 %
NoCompress: 7 %
PagesStored: 3572
PagesUsed: 1135
OrigDataSize: 14288 kB
ComprDataSize: 4510 kB
MemUsedTotal: 4540 kB

BombaMyte said:
I just set this up myself using the directions in the first post, and I can get weather info for my current location...
EDIT: And it flies now...
Click to expand...
Click to collapse
i think that rosie girl likes the compache dope makes her go real fast

My system is not utilizing compcache, instead preferring to use my swap. I'm now testing my system with swap partition disabled:
# swapoff /dev/block/mmcblk0p3;

coolbho3000 said:
My system is not utilizing compcache, instead preferring to use my swap. I'm now testing my system with swap partition disabled:
# swapoff /dev/block/mmcblk0p3;
Click to expand...
Click to collapse
The way h.nocturna coded the userinit.sh for this made it prefer compache over linux swap partition for speed issues then linux swap is secondary
lmk how it runs with no linux swap partition on
EDIT
my system didnt use the compache swap till after reboot then it was FAST

Zarboz said:
i think that rosie girl likes the compache dope makes her go real fast
Click to expand...
Click to collapse
LMAO! Hell yeah she likes that compcache dope! Got a friend that's been trying *not* to root his phone for a few months now. He will once he sees this...

BombaMyte said:
LMAO! Hell yeah she likes that compcache dope! Got a friend that's been trying *not* to root his phone for a few months now. He will once he sees this...
Click to expand...
Click to collapse
i need to change the scripting the swap is getting slow after a day or two there was some info in the compache thread about this ... ill let yall know whtas goin on

I realized you need to turn on the swap on sd after compcache has initialized.

[HACK] (!update 04/26/2010) JIT enabled Dalvik VM on Android 1.6 (Dusted Donuts)

Update (fix for /cache/dalvik-cache 04-26-2010): Really only use this if your having issues using the symbolic link fixes posted by other members or are just out of free space on /cache. First the new issues people are experiencing is in cm-based-kernels from 4.2.15.x and not JIT enabled DalvikVM and people using danger/death spl will experience problems faster. Lack of space on /cache is a problem and will cause market downloads to fail as well as email attachments. The other problem is the kernel fails for various and unknown reasons to mount bind /cache/dalvik-cache to /data/dalvik-cache.
The other issue is the use to dalvik-cache clearing scripts and options in RA recovery, stop clearing your dalvik-cache, the .dex files are created when missing and you do not get any benefits by doing so and cause more wearing leveling of NAND, plus the script in RA recovery doesn't appear to look at /cache/dalvik-cache for dex files. This little update script (when installed correctly).
Understand that /cache/dalvik-cache is a newer option as a means to free up space on /data is by using /cache/dalvik-cache as a first storage of dex files then using the standard /data/dalvik-cache for over flow of dex files and newer installed apps. Somewhere along the way something may throw this and you get douplicate dex files in both locations, one way to check is to boot into recovery and
Code:
mount -a
and check dalvik-cache directories in both /cache and /data for douplicate dex files.
The script will fix these issues, or should at least:
Endless loop FCs on boot
broken /cache/dalvik-cache mount
no binded mount
missing user apps
missing system apps
failed market downloads
non-working symlink patches and installers (no need to run these, they will break this patch)
fixes duplicate dex files in both /cache/dalvik-cache and <target>/dalvik-cache (because it deletes /cache/dalvik-cache)
Will not Fix:
your ignorance
your unwillingness to read
your unwillingness to learn
your compulsive ROM flashing disorder
your compulsive dalvik-cache clearing syndrome
version 1.1.1(updated 4/27/2010 @ 10:10 PM) is current and was slapped together from Phonekenstein, it doesn't look for the existance of /cache/dalvik-cache it assumes it's there and deletes it wether it's a directory, a symlink or a file, re-creates a new empty /cache/dalvik-cache with Android default permissions and mount binds it to /data/dalvik-cache (be it a directory, a symlink or another binded mount) /cache/dalvik-cache will follow the target /data/dalvik-cache (no worries for apps2sd users or non-apps2sd users).
Script will turn on the blue LED when booting so you know it executed (if it annoys you then edit the script and make it pink)
Tested on Cyanogen MOD 4.2.15.1 and SuperD 1.10.3:
with and without apps2sd
with and without a /dev/block/mmcblk0p2 (apps2sd script nulled)
with and without a custom /dev/block/mmcblk0p4
with mount binded /ext/dalvik-cache (mmcblk0p4) to /data/dalvik-cache
with /data/dalvik-cache as a symbolic link to /ext/dalvik-cache (mmcblk0p4)
All scenarios experienced no failures as long as you set your permissions correctly on all targets and files and /cache/dalvik-cache followed and binded flawlessly.
install is simple and can be done through terminal:
1. download 86dalvik-cache-fix <--Long press and chose "save link as" (also attached to this post)
2. open terminal and issue these commands:
NOTE: COMMANDS ARE CASE sensitive in LINUX and as such ANDROID!!!!!!
ALL OFF THESE COMMANDS ARE IN lower case. SO Turn off your Auto-Caps options in your keyboard options. These command assume you downloaded the script using your the web browser on your G1/Magic whatever phone and the file is located in /sdcard/download (the default location for web browser downloads).
Code:
su
mount -o rw,remount /system
cp /sdcard/download/86dalvik-cache-fix.txt /system/etc/init.d/86dalvik-cache-fix
chown 0:2000 /system/etc/init.d/86dalvik-cache-fix
chmod 755 /system/etc/init.d/86dalvik-cache-fix
sync
reboot
Why 86dalvik-cache-fix? We want the script to execute after all scripts in /system/etc/init.d/ including /system/sd/userinit.sh (if you are using one) and before script 99. 86 because in 1987 everything got 86'd.
If you are having a problem getting the script to execute, copy it or merge it into /system/sd/userinit.sh (even if you aren't using a mmcblk0p2(ext partition)) it may make it work with FastTest builds, however the permissions on his builds appear to be root everything and I have problems getting the script to execute out of /system/etc/init.d even with root permissions.
--------------------------------------------------------------------------------------------------------------
Primer: Read this about Dalvik VM http://en.wikipedia.org/wiki/Dalvik_virtual_machine
Read this to: Google Groups post about JIT compiler for Dalvik VM from Android-Platform Link
From the post we see that this particular compiled library is ALPHA, so results can vary, but from reading most posts in this thread the results are right near the talked about 3x faster code, stability is going to vary on what apps and or widgets are running. More Widgets = slower performance as these have processes that are eating cycles. When testing with Linpack wait for the advertisement to load first then tap the benchmark button and remove your finger from the touch screen. Background process such that interrupt or having auto-rotate enabled while testing is going to give you slower benchmarks.
In short your apps should load faster and run faster, particularly 3D games. The web browser is faster and you can actually scroll through pages even while graphics are still loading.
The reboot when enabling it is long even appearing to hang at the G1 Screen for 5 minutes or more but once it starts booting past this you will know that your ROM is compatible. The cause is that the dex files are being optimized, after about a third reboot, your ROM should feel pretty snappy and launching apps should be quicker as well as switching apps. The snappiness lasts as well and as some may have said that it's a placebo effect are wrong. Bench mark readings prove it and more importantly a few ROM builders have included this in their 2.1 ROMs as experimental.
The libdvm.so that t3steve cross compiled for the DROID at the time was for Android 2.0, the library works for with newer ROMs Android 1.6 that have some eclair pieces built into the kernel, CyanogenMOD has been using bits and pieces for a while now, if other ROM builders have been using his kernel and framework than a good chance it will work for your phone as well.
I have nothing to do with the compiling of this or the exact functions of enabling JIT except that I had a hunch that the combo might work and it did, so I'm sharing it.
If you aren't good at typing in commands, or don't know how to extract a zip file and understand that a sub folder may or may not exist where you have extracted said zip file to, well.... you may run into some issues, maybe a video tutorial for basic command line on youtube would be a good place to learn.
I wanted to make a very detailed post on www.andoidonroids.com about how to mash the JIT enabled Dalvik VM library into Android 1.6 Donuts I'm calling the hack "Dusted Donuts" and take from the name for what you will. I have been using the JIT enabled Dalvik VM for about two weeks and i runs decent but not perfect. Anyhow a death in the family Sunday has kept me from making a decent post and haven't had the time to get to the website and post and cross post and give credit where due.
No doubt that aaraya1516 broke the news on http://forum.xda-developers.com/showpost.php?p=5703076&postcount=193 as he was first to break the hack on FastTest, not taking anything away from him on that.
My testing goes back two weeks or more even during the 580mhz & 780mhz hack, I was waiting for someone to compile a boot.img with some 2.x stuff and sure enough the carlospants boot.img from ctso worked with enabling JIT for Dalvik VM, but as we know now the overclocking doesn't work at the moment.
Thank Cyanogen and t3hSteve of which may not know that this was entirely possible. Cyanogen mixed in enough Eclair into his Donuts (he's like Willy Wonka) that makes it possible to use the cross compiled JIT enabled Dalvik VM library from 2.1 for the Motorola DROID 2.0.1 libdvm.so that t3hSteve of www.alldroid.com compiled for the custom roms on Droid.
WARNING: Using other methods supplied from other forum members that include replacing the build.prop may cause problems, using the build.prop from the original VMLIBS.ZIP (which is here for reference and original source for libdvm.so) is definitely going to cause ROM and application problems. Hello....use your head here... the VMLIBS.ZIP is for Motorola DROIDS, why would you put the build.prop file for a DROID on your G1 and expect your apps or ROM to work afterwards? It's so simple, you need 1 file, it's called libdvm.so it goes in /system/lib a file by the same name already exists there and it's in your best interest to at least back it up before overwriting it and gives you the ability in the event that your system doesn't boot up you can restore it through recovery console and get your phone to boot past the G1 screen.
FYI: Some ROMs have the option dalvik.vm.execution-mode=int:fast in the /system/build.prop file, this would need to be changed to dalvik.vm.execution-mode=int:jit or commented out or deleted. If you want to play with advanced options create /data/local.prop and fiddle in there with options available from typing dalvikvm -h in your console or terminal app.
Required:
1. Android 1.6 ROMS with a bit Eclair stuff in the Kernel and framework such as Cyanogen ROM 4.2.x, Super D 1.8 - 1.92, WG Y2.6, FastTest, KingKlick Eclair and more.. This libdvm.so works on Android 2.1 as well as it seems it should.. 1 st bootup is slow and I recommend you let it sit even when desktops are up for a couple of minutes and then reboot it, 2nd and 3rd bootups are faster and smoother response overall even for long durations, days.
FIX YOUR FILE SYSTEM FIRST !!!!!! Got to do it from Recovery Console, It's partly the cause of poorly running ROMS and takes seriously longer to type the command than to fix your unknowingly faulty file system. EXT2 is the worst offender and the built in function to repair falls short, even more so when checking EXT4.
Code:
#e2fsck -fcpDC0 /dev/block/mmcblk0p2
#reboot recovery
For the lazy fingers
#e2fsck -fcpDC0 /*/*/*0p2
#reboot recovery
1. Download www.androidonroids.com/dusted-donuts (File has 3 scripts backup, install, restore, 2 folders, 1 libdvm.so)
2. Extract zip to root of /sdcard or where ever you like (the zip has a folder containing the files named dusted-donuts)
3. Open Terminal or go to Recovery Console
FYI when running the install through Terminal your system may freeze or reboot and if it does I highly recommend that you prepare to enter Recovery Mode and check your file system. EXT2 corrupts quickly choosing this for apps2sd to use is not the best option especially if you are using custom ROMs that may lockup or reboot, basically that's a crash.
Code:
$su
#mount -o rw,remount auto /sdcard
#cd /sdcard/dusted-donuts
#sh backup
#sh install
#sync
#reboot
Check the Dalvik VM execution mode. look at the bottom line with_jit means the it is installed , and look at all of those options that can be jammed into your build.prop and local.prop files
Code:
$su
#dalvikvm -h
Phone won't boot past G1 screen? Go to recovery console and restore libdvm.so (give it at least 5 minutes first before giving up)
Code:
#mount -o rw,remount auto /sdcard
#cd /sdcard/dusted-donuts
#sh restore
#sync
#reboot
---------------------------------------------------------------------------------------------------------------------
prefer to use VMLIBS.ZIP from t3hSteve? This is how you can install using that.
Required:
1. Android 1.6 ROMS with a bit Eclair stuff in the Kernel and framework such as Cyanogen ROM 4.2.x, Super D 1.8 - 19.2, WG Y2.6, FastTest, KingKlick Eclair and more.. This libdvm.so works on Android 2.1 as well as it seems it should..
How to install: (easier to go in recovery mode but can be done through terminal)
1. Download the VMLIBS.ZIP from t3hSteve of allroid.com http://alldroid.org/download/file.php?id=1374
2. You only need the libdvm.so file of which appears to be JIT enabled by default.
3. Backup the original libdvm.so #cp /system/lib/libdvm.so /sdcard/libdvm.so
4. Copy the JIT enabled libdvm.so #cp -f /sdcard/vmlibs/libdvm.so /system/lib/libdvm.so
5. Set permissions on the file #chmod 644 /system/lib/libdvm.so
Optional for disabling: (easier to do vi through recovery console, since the back key escapes out of terminal)
To disable JIT MODE but want to keep the libdvm.so create a local.prop in /data and add dalvik.vm.execution-mode=int:fast
#vi /data/local.prop
press the i key to enter vi interactive mode
type dalvik.vm.execution-mode=int:fast
press back key to exit vi interactive mode
to write the file out and quit vi type :wq
or
restore your backed libdvm.so file from the sdcard.
-----------------------------------------------------------------------------------------------------------------------
Enjoi! the dusted donuts,
-Licknuts (me? I'm like Varuca Salt, I want another pony)
Vendor G1 roms around 1.2 Mflops, Custom G1 roms are around 2.4 MFlops/s and with JIT compiled Dalvik VM 3.6 MFlops/s. At most you will see 3.5 MFlops/s fairly consistently with a minimal load on your system and highs at 3.7 Mflops/s. Test before and after using Linpack from the Market, it's free.
The 13.236 Mflops/s is not normal and you will probably not see with your testing, I have seen 5.x & 7.x but these are far and few between and this took a while with tweaked configurations/settings with a persistent app to kill processes, it is attainable and I hope a ROM developer finds the sweet spot to exploit.

Looks nice.
Pre-JIT enabled: 2.194 Mflops/s
Post-enabled: 3.459 Mflops/s
Not quite getting the results you have there.
Running SuperD 1.9.2 Black W/ Nexus Theme. I copied it twice to make sure that the libdvm.so was copied correctly to the directory. Rebooted the phone, same results. Looks very promising though. If I did something wrong, lemme know.
Managed to get #10 on G1 Benchmarks with 3.583 Mflops/s... still nowhere near 13.~ Mflops/s

same here. Running Super D 1.9 on my magic
before JIT I got 1.xxxx Mflops/s
after i have 2.xxxx Mflops/s
how do you get the 13 Mflops/s ?
-edit-
with swap disabled i'm getting 3.5 Mflops/s

h.nocturna said:
Looks nice.
Pre-JIT enabled: 2.194 Mflops/s
Post-enabled: 3.459 Mflops/s
Not quite getting the results you have there.
Running SuperD 1.9.2 Black W/ Nexus Theme. I copied it twice to make sure that the libdvm.so was copied correctly to the directory. Rebooted the phone, same results. Looks very promising though. If I did something wrong, lemme know.
Managed to get #10 on G1 Benchmarks with 3.583 Mflops/s... still nowhere near 13.~ Mflops/s
Click to expand...
Click to collapse
I got 9 seconds on the pi benchmark

What will this do??

samsara00 said:
same here. Running Super D 1.9 on my magic
before JIT I got 1.xxxx Mflops/s
after i have 2.xxxx Mflops/s
how do you get the 13 Mflops/s ?
-edit-
with swap disabled i'm getting 3.5 Mflops/s
Click to expand...
Click to collapse
So I guess this only works with Swap off?
sabin123 said:
What will this do??
Click to expand...
Click to collapse
Speed your *hit up!

it works with and without swap.
Just the benchmark result is better when swap is turned off.
Got nearly the same as samsara00:
Rom: SuperD 1.9.2
Before (swap off): ~ 2.3 MFlops/s
After JIT enabling (swap off): ~ 3.5 MFlops/s
But the increase to 13.x seems so unreal, why is there only one result that high in the toplist of greene.com!?

Now to find out if this actually speeds up everyday use lol
CM4.2.14.1
Before: 2.3
After: 3.5
Wow! This made my 3G connection faster too. Was only getting 1500kbps before, now getting on average 3200kbps. Awesome. I'm located in Toronto, on Rogers.
Question: Is this Google's JIT? Will Myraids Dalvik Turbo be faster?

Doesn't boot past the G1 screen when using Dwangs 1.17.1 Assume thats because it has no Eclair in it, but it was worth the dream .

Waw!! great works!!
left is before - right one is after
on CM 4.2.14.1, enabled Swap 64MB, CC ON, RAM Hacked

So do we copy the zip to the root of our sd card? Do I extract it first and just copy the one file? The instructions are kind of vague.

G1ForFun said:
So do we copy the zip to the root of our sd card? Do I extract it first and just copy the one file? The instructions are kind of vague.
Click to expand...
Click to collapse
Not to be rude, but if you don't understand those directions, this isn't the sort of thing you should try to do yourself. Wait for a ROM builder to add this in. The directions are perfectly clear, you just need to understand command line use.
If you want to learn something about CLI use, install Linux on your computer and learn to use it without the GUI. If you don't want to do that, google for "cygwin" and use the bash shell they provide for Windows based machines.

Personally, I used adb and just pushed the darn file lol works perfectly fine, like everything else I've ever pushed. Just don't forget to set the permissions for the file.

tried in a terminal and with adb getting read-only file system when trying to copy over the libdvm.so file

SilentTweak said:
Personally, I used adb and just pushed the darn file lol works perfectly fine, like everything else I've ever pushed. Just don't forget to set the permissions for the file.
Click to expand...
Click to collapse
Nothing wrong with adb. Hell, I used SSH to do it. Just about anything will work, you just have to know what you're doing.
Damn.... I just rebooted and it took about half the time it used to.
Tried the Linpack benchmark, getting about 3.5 with SuperD 1.9.2 w/Compcache 16M swappiness=10. Fresh reboot, obviously. Lock your CPU to 528 (min and max) for more consistent results. When I have 128min 528max, it gives different results depending on the current CPU speed. SetCPU or Overclock Widget helps a lot here. No instability noticed yet, but this should probably be considered an unstable hack for now till we all get more experience with it. I know OpenEclair removed the JIT VM because of stability problems.

Sgt.EddieWinslow said:
tried in a terminal and with adb getting read-only file system when trying to copy over the libdvm.so file
Click to expand...
Click to collapse
Do "adb remount" first

ttabbal said:
Not to be rude, but if you don't understand those directions, this isn't the sort of thing you should try to do yourself. Wait for a ROM builder to add this in. The directions are perfectly clear, you just need to understand command line use.
If you want to learn something about CLI use, install Linux on your computer and learn to use it without the GUI. If you don't want to do that, google for "cygwin" and use the bash shell they provide for Windows based machines.
Click to expand...
Click to collapse
Obviously they are not clear to me. Why argue the point?
I have worked plenty with cmd type interfaces...so please...put down your know it all stick and be helpful.
edit: hope this helps somebody else...look better instructions posted in the fasttest thread!
download files here and copy them on the sdcard
created a folder /sdcard/jit and put the three files in it
make a folder /sdcard/dalbk and copy the original files
adb pull /system/build.prop .
Open in WordPad/Textpad and add as the last line: dalvik.vm.execution-mode=int:jit
SAVE IT, copy/push it on the /sdcard/jit folder

Sgt.EddieWinslow said:
tried in a terminal and with adb getting read-only file system when trying to copy over the libdvm.so file
Click to expand...
Click to collapse
Code:
C:\Android\tools>adb shell
# su
su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# chmod 777 /system/lib/libdvm.so
chmod 777 /system/lib/libdvm.so
# cp -f /sdcard/vmlibs/libdvm.so /system/lib/libdvm.so
cp -f /sdcard/vmlibs/libdvm.so /system/lib/libdvm.so
# chmod 644 /system/lib/libdvm.so
chmod 644 /system/lib/libdvm.so
# reboot
Damn.... I just rebooted and it took about half the time it used to.
Click to expand...
Click to collapse
Indeed
Licknuts result : 3.1-3.5 (with Super-D 1.9.2)

My method of installing it:
adb remount
adb push libdvm.so /system/lib/libdvm.so
Then open console and type:
su
chmod 644 /system/lib/libdvm.so
reboot

I'm about to try this myself.. has anyone noticed an overall increase in speed? Benchmarks are great but it's all about how it actually performs!
I'll post my own findings in a bit.

[DEV] Script for tweaks (version 1.02) 18-12-2010

Here is a script i've made (had nothing to do, so...).
Phone must be rooted and have busybox installed.
What first menu looks like:
1 - enable/disable hardware acceleration
2 - enable/disable jit
3 - enable/disable stagefright player
4 - change heapsize
s - show status
r - revert to original configuration
q - quit (don't forget to reboot your phone!)
==================
enter your option:
Click to expand...
Click to collapse
Download:
http://www.4shared.com/file/gApTB6EG/tweaks.html
md5 b0865d9de67a82215913512cb644211d
Just copy the file to your sdcard. Then in a terminal emulator run:
su
cat /sdcard/tweaks > /data/tweaks
rm /sdcard/tweaks
cd /data/
./tweaks
If it doesn't run, type first:
chmod 755 /data/tweaks
Additional notes:
Script does not work if run from sdcard, must be in /data/ or /system/ (this one goes to allsalvati for testing)
---
If anything is wrong i will fix it, but only if you give me feedback
If you know any good tweaks, say it and i'll add them.
---
Changelog:
version 1.02:
backup/restore added
version 1.01d:
working again. sorry for the mess...
version 1.01c:
nothing new. just rearranging code
version 1.01b:
messages were not staying in output. fixed
version 1.01a:
small fix. v1.01 was not working
version 1.01:
added status menu

ruigui said:
Here is a script i've made (had nothing to do, so...). Phone must have busybox.
Download:
http://www.4shared.com/file/gApTB6EG/tweaks.html
md5 ea568c399c67ecd87db0dd790cdf0e93
Just copy the file to your sdcard. Then in a terminal emulator run:
cd /sdcard/
./tweaks
If it doesn't run, type first:
chmod 777 /sdcard/tweaks
Please give me some feedback. I don't own the phone so i can't test.
Click to expand...
Click to collapse
what the script does?

So script should be able to do:
enable/disable hw acceleration
enable/disable jit
enable/disable stagefright player
change heapsize

Yes. For now it's what it does.
The ideia is to be able to enable/disable a certain tweak, without reflashing zips, and rewriting files in phone.
But i need some feedback to know if it is working. I can't test it.
It will only change values in /data/local.prop, nothing else.

It seems that it is well written, so I will try that and let you know what's happened.

Thanks for testing. I'm still waiting to have some money so i can buy this phone...
Meanwhile, i'm "playing" with ROMs and files. I'm not good at scripting, but i'm trying to learn while doing something useful.

How much did you increase the heap size?

domenic_s said:
How much did you increase the heap size?
Click to expand...
Click to collapse
I didn't increase it. Script shows this message:
"default=24, recommended=32"
"enter new heapsize value (1-64): "
You can enter any value between 1 and 64.
If you enter any other value, or a string, character, symbol... script will show this message:
"wrong value"
"please input a value between 1 and 64"

For those who don't feel like editing this themselves this is great. Thanks for releasing it for people to try out more tweaks on stock ROMs.

i'm trying to run this script and gives me the following message: ./tweaks: permission denied
Before anything i typed su, then chmod 777 and it gave me error.

It should work be working...
Anyone else confirms this issue? Is this script running or not?
If it is working and there are more tweaks, i can easilly add them to the script.
If this is an isolated case, i really can't help. I don't own an android phone (yet), so i can't test....
allsalvati do you have busybox installed?

No, i don't.
Sent from my LG-P500h using XDA App

That may be your issue.
You must mount /system/ as read-write, then copy busybox binary to /system/xbin/, then run these commands in terminal emulator:
su
cd /system/xbin
/system/bin/chmod 755 busybox
./busybox --install -s /system/xbin
After that you can mount /system/ as read only again, and reboot your phone.
I don't know if there is another way to install it that is easier.

I downladed busybox installer from market and the app says that was installed. The. /tweaks gives me the same message.
How do i test if busybox was installed right?
Sent from my LG-P500h using XDA App

I found this:
That is a problem, you cannot chmod a script to executable on the SD card. (well some things can, but 99% no) the system is designed to prevent u executing scripts from an SD card
cp it to /system/xbin or /system/bin.
Or if u hate to see it in system', use /data/
THEN chmod it. should be fine to run
Click to expand...
Click to collapse
Try to copy the file to /data/ (so you don't mess with /system/), and then try to run it with:
cd /data/
chmod 777 tweaks
./tweaks
It should not need to be run as root

Moved to /data and worked.
I changed heap size to 32 and disabled hardware accelaration just to test.
With hw acc - 981 on Quadrant
Without - 820
So i think this is working.
Perhaps you should print the values so the user can see what is enabled or not before apply.
Thanks for your help
Sent from my LG-P500h using XDA App

Can you test something for me?
Make sure you have hardware acceleration disabled, and reboot you phone.
Then open terminal and run:
getprop | grep hw (see what it outputs)
then run the script, enable hardware acceleration on it, but DON'T reboot your phone yet.
Then exit script, and run again:
getprop | grep hw
Has the value changed, or is it the same?
I need to know if the system assumes immediately any changes (although they may not be functional until reboot).
This is needed to work on your request.
allsalvati said:
Perhaps you should print the values so the user can see what is enabled or not before apply.
Click to expand...
Click to collapse
I'll work on that and post an update after someone tries what i asked above.
Thanks for testing
EDIT: to test benchmarks, enable/disable jit. It gives greater differences in values

I tried what you say and both outputs are the same:
$getprop | grep hw
[debug.sf.hw]: [0]
[hw.keyboards.65537.devname]: [7k_handset]
[hw.keyboards.65540.devname]: [thunder_keypad]
[hw.keyboards.65541.devname]: [touch_mcs6000]
[hw.keyboards.65542.devname]: [atcmd_virtual_kbd]
Edit: Tested disabling JIT and it worked. Linpack Before 7.35 - After 4.3

So i can't rely on getprop to check current values...
If anything is changed, getprop won't give the right output till reboot.
Damn... Script was almost updated. Now i must find a new way and redo this section.
Thanks for testing again
EDIT:
New version for download at first post. status menu added.
I think it's all ok.

It seems work fine on my phone. But I can't see the status. When I choose to see current status or status after reboot, the screen of my emulator returns too fast to the selection menu (show curent status or after reboot) and I can't see anything !

[HOW-TO] Some tweaks to sweeten your life with the Infinity a little

Hi everybody, I would like to share my experiences with the Infinity and ask you guys to share your opinions, thoughts and ideas on tweaking it. Hopefully we can sort something out together.
Please remember that you can brick your tablet with any of these methods and lose your warranty too and be the one solely responsible for it. I have not bricked mine, so I am writting all of this with best intentions . Proceed with caution and only if you are sure that your Infinity not booting will not lead you to jumping off a high building! Seriously.
Ok, here it goes.
Hit [THANKS] if it helps.
Seems this thread somehow got to the News, so special thanks go to Joe and those of you who have reported it newsworthy. I'm glad I could've helped you with this!
Remember 1) you'll have to do most of these each time you update firmware / change ROM and 2) go back to stock /system files every time before you apply an OTA update, as it does various checks on /system integrity now.
1. ROOT
Don't use ASUS Device Tracker! (see point 6. below)
Install SuperSU and follow these steps before updating to the Jelly Bean to preserve root (thanks to nooktablet for posting this). Others said that Superuser app combined with RootKeeper sufficed, so do as you wish.
DroidEris1981 has reported that in his case on the .30 firmware he was only able to root his Infinity using an older version of Debugfs and only when pausing it at each reboot, waiting for the device to fully boot up before the next step.
So far the only rooting method that works is the Debugfs method by sparkym3. By rooting you can boost your Infinity's performance a bit, including its poor I/O results, and much, much more (see threads on reasons for rooting and apps).
Once again: ROOT BEFORE UPDATING TO THE JB!
If you've failed to do this, however, there is still a way to work things out - see the first few posts in this thread if you're under unrooted JB now.
In case you experience problems using this method, you may try one of the solutions described in this thread, but as there is a new 2.2 version now, you should be good just using it.
Some need to RUN the Superuser app first before it starts working. And remember about BusyBox, it comes handy in many situations, especially if you are going to use the shell. And you can use SuperSU instead of the "default" Superuser app.
RootKeeper might come in handy when updating firmware on a rooted Infinity.
1.1. We have the unlocking tool now, and a few custom ROMs in the development section.
2. I/O scheduler [only after rooting your device] OBSOLETE
Since the .26 update and under the JB as well cfq is the default scheduler and better than non-stock sio, so no reason to change the scheduler at this point already on >= 9.4.5.26 firmware!
After a day of using JB I can say that (stock) noop is slightly faster than cfq for most uses.
[REMOVED]
3. build.prop tweaks ("/system/build.prop" file)
These are for the ICS. We'll all have to see how these perform under the JB. So far changing the DPI via build.prop has been confirmed to be obsolete.
EDIT 22.12.2013 Deleted several obsolete entries, see LaraCroft304's post for reference.
I have used various suggestions as a reference, incl. demandarin's tweaks for the Prime (just search "build.prop tweaks" on xda and read about what these tweaks do). I am still unsure of some of them, e.g. the proper heap size instead of the default 256m (or maybe we should leave it be?). The tweaks I'm using are the following.
Edit: I'm leaving the default heap size, I think it's better for the games.
Lines to EDIT:
#an old proposal, which seems to be of no use
#dalvik.vm.dexopt-flags=m=v,o=y
dalvik.vm.dexopt-flags=v=n,o=a,u=y
#In case you experience problems with some apps after this, try (unhash) this instead:
#dalvik.vm.dexopt-flags=v=a,o=v,u=y,m=y
#(you can also see, for example, this thread for instructions)
# optional: CHANGE SCREEN RESOLUTION / PIXEL DENSITY (so that your screen can become more capacious)
# ro.sf.lcd_density = 160
Lines to ADD:
# BATTERY SAVING
pm.sleep_mode=1
wifi.supplicant_scan_interval=180
# UI & GENERAL PERFORMANCE
ro.kernel.android.checkjni=0
persist.sys.strictmode.visual=0
persist.sys.strictmode.disable=1
dalvik.vm.execution-mode=int:jit
com.ti.omap_enhancement=true
# MEDIA QUALITY & PERFORMANCE
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
ro.media.enc.jpeg.quality=90
ro.media.enc.hprof.vid.bps=8000000
persist.sys.use_dithering=1
# NETWORK PERFORMANCE
# there are different types of advice here, you can try what work's best for you out of the latter two (just delete all the spaces which xda keeps adding!):
net.tcp.buffersize.default=4096,87380,256960,4096,16384,256960
#net.tcp.buffersize.wifi=4096,87380,256960,4096,16384,256960
net.tcp.buffersize.wifi=262144,524288,1048576,262144,524288,1048576
# SWITCHING SOME NOTIFICATIONS OFF
# disable sending usage data
# disable adb notifications
persist.adb.notify=0
# FAST REBOOT
persist.sys.purgeable_assets=1
# you can also unhash this and disable boot animation for faster boot:
# debug.sf.nobootanimation=1
# This is for current, Wi-Fi only version of Infinity of course:
ro.carrier=wifi-only
# Just for those who need it - unhash the following line to make your device run all ADB shell and terminal emulator commands as ROOT by default (use with caution)
# ro.secure=0
3.1. You can edit the build.prop file manually, you can use one of a few apps out there to manage it, but I have found manually mounting the system r/w (and r/o again after changing the file) and editing it through a PC (you can use Dropbox) or the Infinity with the dock most helpful - you can just cp the new file to (remember to make a backup copy of the old file just in case!).
If you like using the term, you can just 'su' and write these commands:
a) R/W before edit:
mount -o rw,remount /system
b) R/O after edit (remember to run 'chmod 644 /system/build.prop' as root before remounting /system R/O):
mount -o ro,remount /system
3.2. Remember to reboot your device after changing the file. Clearing dalvik-cache won't hurt either.
Edit: Actually I highly recommend wiping dalvik cache to avoid bootloops (as root: rm /data/dalvik-cache/*) <- and then.reboot
4. Minfree tweaks:
You can either change the values in /sys/module/lowmemorykiller/parameters/minfree (remember these are pages, so 1024 means 4MB!) or use any of the apps from the Playstore meant for that. I'm using System Tuner for things like that (look for Tweaks / Auto-Kill in the app). You might set anything you like, possibly 8,16,200,220,240,275 MB proposed by the author of the (messy) SuperCharge script for the 1GB RAM devices (based on a minfree calculator by another XDA member). I have it currently set on 8,16,32,128,192,192 MB, which seems aggressive enough.
You can read more about it and what these values mean here.
You can also have a look at my thread on battery life.
5. Disable "smart dimmer", which is the reason you can see some screen flickering when changing between light and dark backgrounds that many find annoying (described by some as "dynamic contrast", which it resembles):
Can be done through SYSTEM SETTINGS under the JB, so no need to do this manually anymore.
To disable:
echo 0 > /sys/devices/tegradc.0/smartdimmer/enable
To re-enable echo 1 to the this file or simply reboot.
Be sure to include this in a script so that rebooting won't change it (just make an .sh script with the above line in it, you can use either SManager or system .sh scripts (you can use my simple solution posted here if you don't like editing files yourself). See also jtrosky's hints on changing the brightness settings.
Please note that it may negatively affect your battery life, although with brightness set low it shouldn't be much worse.
All credit goes to those who have found out about it - see this post for details.
6. Disable remote management that allows ASUS (or anybody in charge of their servers) to track, lock or wipe your device over-the-air or steal your data, which has been confirmed ASUS is doing: read the whole story about warranty voided because of rooting here.
7. Install Volume+ or a similar app to boost your device's sound level (you can register here to get the full version for free, but if it helps, support the developer). And remember to change the audio device in the system audio settings to Volume+!
8. Other tweaks, init.d, scripts etc.
See the development section for custom ROMs which include various tweaks and for custom recoveries.
9. Some keyboard solutions:
Re-map the browser keyhttp://forum.xda-developers.com/showthread.php?t=1497624 in the dock in order to be able to use your favourite browser or do some custom re-mappings.
In case of problems with diacritics when docked, be sure to use KLSwitcher for setting your locale.
Finally, not really a tweak, but something that a lot of users find helpful: KEYBOARD SHORTCUTS.
10. Remove bloatware (see the first few posts with further links here).
11. Set background processes to max. 4 in the dev. settings for better stability (that's true for the ICS at least).
<----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------->
And remember, at the end of the day, when you're done tweaking, you should disable USB debugging if you don't want to get hacked.​
Hit [THANKS] if it helps.

Thank you for this! I'll have to try some of these out when I pick up my tablet.

i remember reading about some 300 users using, browser2ram (i think that's what its called) for a better internet browsing experience.

denniegst said:
i remember reading about some 300 users using, browser2ram (i think that's what its called) for a better internet browsing experience.
Click to expand...
Click to collapse
Can you give us a link? Google is not helpful with this name you mentioned (browser2ram).

http://forum.xda-developers.com/showpost.php?p=25286407&postcount=61
i think it only works on stock browser, but i could be wrong. and since everything is sent to the ram, once the tablet resets everything will be lost: browser history settings etc

denniegst said:
http://forum.xda-developers.com/showpost.php?p=25286407&postcount=61
i think it only works on stock browser, but i could be wrong. and since everything is sent to the ram, once the tablet resets everything will be lost: browser history settings etc
Click to expand...
Click to collapse
Thanks, that sounds interesting, but I am not sure there is a need for it on the Infinity. Dolphin HD performs exceptionally well (thanks for the info, ray3andrei: http://forum.xda-developers.com/showthread.php?t=1752809&page=2).
Edit: Can't recommend Dolphin anymore due to serious privacy issues.

Hi
Correct me if i'm wrong:
1. install the drivers if they are not installed allready
2. tick usb debugging
3. tick unknown sources
4. unzip DebugfsRoot_v1.8
5. connect tab to pc
6. run RootDebugfs.bat
7. select option 1 -Root
8. since haven't go further this step, i don't know what's next till rebooting
that's it? device rooted?
i have a little experience in rooting cause i have rooted my galaxy s a few times, but that phone is almost unbrickable
i just want to be sure i'm doing it right
thanks

dobranszky said:
Hi
Correct me if i'm wrong:
1. install the drivers if they are not installed allready
2. tick usb debugging
3. tick unknown sources
4. unzip DebugfsRoot_v1.8
5. connect tab to pc
6. run RootDebugfs.bat
7. select option 1 -Root
8. since haven't go further this step, i don't know what's next till rebooting
that's it? device rooted?
i have a little experience in rooting cause i have rooted my galaxy s a few times, but that phone is almost unbrickable
i just want to be sure i'm doing it right
thanks
Click to expand...
Click to collapse
Yep, that's basically it
Then it reboots a few times while pushing some files through adb, you get the Superuser program installed etc. After a few minutes you should have a rooted Infinity.
However, it will be much more fun after installing BusyBox from the Market/Play. It gives you a bunch of commandline tools to play with.
Just remember to charge your device and not to connect any other Android device while rooting.

I don't understand why you are using the 1.8 version when the 1.9 is there. I used 1.9 to root without any problems.

Alkzn said:
I don't understand why you are using the 1.8 version when the 1.9 is there. I used 1.9 to root without any problems.
Click to expand...
Click to collapse
There are links to both in the thread I was referring too. Actually I don't see any harm in using 1.8, as 1.9 is just updated Superuser app, which will update itself from Google Play anyway (they had some problems uploading the file to xda btw)

Hi fellow Infinity-Users!
I tried both versions (1.8/1.9), and both equally worked/failed with my (european) TF700.
The issue that actually broke the batch-script was adb wait-for-device, which just seemed to catch a timeout after waiting for the tablet to reboot.
As there is little magic in that script, you can safely execute all it does by hand (basically all the lines involving adb). That's the way I just rooted my TF700 and it worked like a charm.
Alternatively, if you don't feel comfortable with executing the adb actions by hand, you might want to just replace all occurrences of
Code:
adb wait-for-device
with
Code:
pause
(or something like that.)
Then you will have to hit enter (or some other key) each time once the tablet has rebooted.
What is actually needed for rooting:
Wait for your tablet to be fully booted up.
In a terminal execute the following commands in the folder you unpacked the rooting stuff to:
Code:
adb kill-server
REM as we are not rebooting and we don't hit a timeout, the first wait works
adb wait-for-device
adb push debugfs /data/local/
adb push su /data/local/
adb push debugfsinput /data/local/
adb shell mv /data/local/tmp /data/local/tmp.bak
adb shell ln -s /dev/block/mmcblk0p1 /data/local/tmp
adb reboot
REM Wait for the tablet to reboot
pause
adb shell chmod 777 /data/local/debugfs
adb shell "/data/local/debugfs -w /dev/block/mmcblk0p1 < /data/local/debugfsinput"
adb shell rm /data/local/tmp
adb shell mv /data/local/tmp.bak /data/local/tmp
adb shell rm /data/local/su
adb shell rm /data/local/debugfs
adb shell rm /data/local/debugfsinput
adb reboot
pause
REM Wait for the tablet to reboot
Now check the if you've got a rootshell - thus the given uid and gid of the are indeed root (0). make sure to remove the REM from the first or second part, if needed
You do this eg. by executing:
Code:
adb shell "/system/xbin/su -c id"
If you are root, install the Superuser Management Toolpack:
Code:
adb install Superuser.apk
adb reboot
Else cleanup:
Code:
adb shell /data/local/nachoroot.bin --undo > nul
adb reboot
Hope this cleared things up a little!
(all commands are taken from the script. If someone feels this is undesirable to post here, please let me know, I'll remove that immediately. Thanks to sparkym3, miloj and viperboy for giving me root-power !)

Thanks, that's interesting, I have the "European" version, as you called it, or rather WW firmware, and the script worked perfectly for me.

d14b0ll0s said:
Thanks, that's interesting, I have the "European" version, as you called it, or rather WW firmware, and the script worked perfectly for me.
Click to expand...
Click to collapse
True, I'm running WW_epad-9.4.5.21-20120601. From what I've seen so far, the issue seems not to be related to the tablet, but seems to be some issue with the OS adb is run on. In my case this is win7x64. What OS are you running? Would be interesting to track this down for others who may run into this issue in the future .

burningcf said:
True, I'm running WW_epad-9.4.5.21-20120601. From what I've seen so far, the issue seems not to be related to the tablet, but seems to be some issue with the OS adb is run on. In my case this is win7x64. What OS are you running? Would be interesting to track this down for others who may run into this issue in the future .
Click to expand...
Click to collapse
Good point. Unfortunately, the OS version trace seems to lead to nowhere, as I'm on Win 7 x64 too... perhaps something else then?

Run on balanced no matter what, everything runs better, and the tablet seems to not get stuck anymore or lag while downloading... so for the love of your infinity run on balanced instead of performance
Sent from my Jelly Beaned GNexus

ray3andrei said:
Run on balanced no matter what, everything runs better, and the tablet seems to not get stuck anymore or lag while downloading... so for the love of your infinity run on balanced instead of performance
Click to expand...
Click to collapse
I had good experience with "balanced" too, but if you compare it to benchmarks you can see that actually some operations are faster in "performance": mostly GPU, but not only that - RL Benchmark (SQLite Performance) is 110 in balanced instead of <90, reading & writing speeds are often faster in "performance" etc. But I agree it is the best mode to be running in everyday use, mostly because of power/battery *balance* and governing the CPU.

d14b0ll0s said:
I had good experience with "balanced" too, but if you compare it to benchmarks you can see that actually some operations are faster in "performance": mostly GPU, but not only that - RL Benchmark (SQLite Performance) is 110 in balanced instead of <90, reading & writing speeds are often faster in "performance" etc. But I agree it is the best mode to be running in everyday use, mostly because of power/battery *balance* and governing the CPU.
Click to expand...
Click to collapse
i really cant seem to get better gpu performance,,, quite the contrary i get better o balanced
Sent from my Asus Transformer Pad Infinity

I used sparky root on my prime and my tf300. Question. Can I use sparky root on my tf700 or will I need to do the debugfs method? If I have to use the debugfs method is there a step by step link?

leroybrute said:
I used sparky root on my prime and my tf300. Question. Can I use sparky root on my tf700 or will I need to do the debugfs method? If I have to use the debugfs method is there a step by step link?
Click to expand...
Click to collapse
So far only Debugfs has been confirmed to be working.
You might find either of these useful:
http://forum.xda-developers.com/showthread.php?t=1706588
http://forum.xda-developers.com/showpost.php?p=28490040&postcount=8

Thank you

[LOS][SWAP][MEM] Snappier than ever

NOTE: BEFORE SAYING "yet another memory swapping evangelist", WATCH THE VIDEO: https://youtu.be/sdeKuPiR4II
I have been doing some research on system responsiveness with my good old Mofo Z. Then arrived at this.
24 hours after having configured:
LineageOS 15.1 (root enabled)
Swap file size = 4GB (in /data/swap)
vm.swap_ratio = 100 (default)
vm.swap_ratio_enable = 1
vm.swappiness = 75
I have achieved the readings contained in the attached screenshots, and the system acts snappier than ever. It's actually running pretty cool.
First I enabled init.d processing by adding an RC file to init, then created userinit.sh with the necessary systcl and swapon commands.
No system files were changed (new files were added only), so after an update the configuration won't revert to the original state (swap-less).
The least used pages (some [almost] never used) are being written to the swap file and therefore more room for active code (and cached apps) is made available.
It's almost like I had an 8GB RAM bastard in my hand. This with around 130 apps loaded.
STEPS USED
File init_d.rc was created (as described in https://forum.xda-developers.com/lineage/general/how-to-enable-init-d-to-function-t3810355)
Executed:
Code:
$ su
# cd /data
# mkdir swap
# cd swap
# dd if=/dev/zero of=swapfile bs=1048576 count=4096
# mkswap swapfile
Created /data/local/userinit.sh (called from within already existing /system/etc/init.d/90userinit) with the code:
Code:
#!/system/sbin/sh
# vm_swap_ratio=100 is default, no need to set
sysctl vm.swap_ratio_enable=1
sysctl vm.swappiness=75
swapon /data/swap/swapfile
Rebooted and let the system run for a few hours. Things only get better with uptime/usage.
The best part is that you can unroot afterwards and have it still working.
Merry Christmas!

thanx 4 ur work but i m newbie i dont understand what is for , what makes this for this device

murteci said:
thanx 4 ur work but i m newbie i dont understand what is for , what makes this for this device
Click to expand...
Click to collapse
It's for making your device multitasking better. Watch the video: https://youtu.be/sdeKuPiR4II

Guess what? The Galaxy Note 9 (SM-N9600, 6GB/128GB version) employs memory swapping. It has a 2GB active swap file right out of the box.
I received mine last friday, updated Android and went to check it out after I noticed it behaved and reported much like LineageOS with my mod applied. Then I installed a terminal emulator (no root needed) and ran "free -m".
Bang! The swapping is there!
Can't wait to root it and verify that the swappiness is set to... 75. Kinda keen those Samsung guys, huh? Heheheh.

Whammamoosha said:
Guess what? The Galaxy Note 9 (SM-N9600, 6GB/128GB version) employs memory swapping. It has a 2GB active swap file right out of the box.
I received mine last friday, updated Android and went to check it out after I noticed it behaved and reported much like LineageOS with my mod applied. Then I installed a terminal emulator (no root needed) and ran "free -m".
Bang! The swapping is there!
Can't wait to root it and verify that the swappiness is set to... 75. Kinda keen those Samsung guys, huh? Heheheh.
Click to expand...
Click to collapse
Can Make this tutorial to Video Tutorial on Youtube ?

Whammamoosha said:
It's for making your device multitasking better. Watch the video:
Click to expand...
Click to collapse
it looks fantastic, but does it wear the internal storage after time?

JuniorCaesar said:
it looks fantastic, but does it wear the internal storage after time?
Click to expand...
Click to collapse
Yes it does, everything is a trade-off, there's no such thing as a free lunch.
But the wear level added is roughly same as on a computer SSD, so we're talking about decades of use before everything wears out.

emrebozkurt99 said:
Can Make this tutorial to Video Tutorial on Youtube ?
Click to expand...
Click to collapse
I could, but everything is so simple that it's pretty unnecessary.
. Install terminal emulator app from Play Store
. Run terminal emulator app
. Type "free -m"
. Done!
As for the swap configuration for LOS I'm writing a shell script (BIG) that will handle the configuration as user-friendly as possible. Stay tuned!

Could this be used on a stock rom as well?

SlashSpeed said:
Could this be used on a stock rom as well?
Click to expand...
Click to collapse
This is for LineageOS. For stock ROMs (once rooted) one may make the necessary adaptions.

im noob
Hi, im noob and I followed your instructions (at least what I understood) n_nU
I hope that I did it right, the question is, how can I know that?

old thread, but this may not work for most because the script has a slight error:
Code:
#!/system/sbin/sh
It should be:
Code:
#!/system/bin/sh
then all is well.

justle said:
im noob
Hi, im noob and I followed your instructions (at least what I understood) n_nU
I hope that I did it right, the question is, how can I know that?
Click to expand...
Click to collapse
https://gist.github.com/iGlitch/be70d403ad1cfa42ac7e1d46f1b546db Amend a script to a script to track whether or not it executes. Note: You need to manually create the log folder and logs file in /storage/emulated/0 in order for it to work.
Code:
# Push a semi-needed log to the internal storage with a "report" if the script could be executed or not;
# Script log file location
LOG_FILE=/storage/emulated/0/logs
echo $(date) > /storage/emulated/0/logs/script.log
if [ $? -eq 0 ]
then
echo "Script executed. Enjoy!" >> /storage/emulated/0/logs/script.log
exit 0
else
echo "Script failed!" >> /storage/emulated/0/logs/script.log
exit 1
fi
# Done!

Thanks! Worked like a charm.
I use a bunch of fat apps and this caused a few seconds of load times with almost every app switch.
I'm running LOS 17.1 on gemini with 3GB RAM; swap file defaults to 0.5GB.
I've left
Code:
vm.swap_ratio_enable = 0
vm.swappiness = 60
as it was. Simply adding a new 4GB swap file fixed my daily pain.

I have to provide an update on the charm part. (I've tried other settings from first post too).
Previously system was stuck at fully utilized 500 MB default swap. Every app change (I'm using hungry ones) was a pain.
Now system uses ~300 MB more in swap, and for some use cases user experienced have gotten bettter.
I don't feel like this mode would be complete without changing app killer configuration. Would it even be efficient considering the memory read speed in mi5 (or at all)? Idk.
Bottom line.
If you are unhappy with the performance of your hardware and it's because of RAM and your system are using 100% of swap, then it is probably worth increasing the paging file size.

SyraAB said:
Thanks! Worked like a charm.
I use a bunch of fat apps and this caused a few seconds of load times with almost every app switch.
I'm running LOS 17.1 on gemini with 3GB RAM; swap file defaults to 0.5GB.
I've left
Code:
vm.swap_ratio_enable = 0
vm.swappiness = 60
as it was. Simply adding a new 4GB swap file fixed my daily pain.
Click to expand...
Click to collapse
Hi SyraAB.
I am glad that you successfully create swap and make swap service work, which I think now you are the only one who can solve my problems.
So I did every step that Whammamoosha said. However, I failed. When I check whether there was swap created using free -m in Termux there was nothing. Then I dig something out from some research. Here is my question:
1)
Whammamoosha said:
Created /data/local/userinit.sh (called from within already existing /system/etc/init.d/90userinit) with the code:
Click to expand...
Click to collapse
It appears that I don't have file 90userint under /system/etc/init.d (by the way I believe Whammamoosha meant /system/etc/init here because init.d does not exist in android). Also I notice your ROM is Lineage OS 17.1, which is the same as mine. So I am curious how did you make that work without file 90userinit.
2)
To my best knowledge that sysinit is killed in Los 17.1. There is a post on Reddit regarding to enable init.d on Los 17.1. Link is here. What makes me more curious is that how did you manage to make all things work without some key files? If you don't mind could you tell me how did you successfully create swap?
My phone is HTC m8 running on Lineage os 17.1.
Thanks in advance

Hello mrdet,
I didn't configure applying new swap on startup at all, so I didn't dance around absent init.d.
Increasing the paging file consist of two steps.
1. Create a file to be used as swap. This needs to be done once, as file persist after reboot.
Spoiler: mkswap example
Bash:
cd /data
mkdir swap
cd swap
# create swap file
dd if=/dev/zero of=swapfile bs=1048576 count=4096
mkswap swapfile
2. Activate it. This needs to be done after every reboot.
Spoiler: swapon example
Bash:
swapon /data/swap/swapfile
Hope this helps.