I made a script to move application cache from data to microSD.
The reasons:
- Internal memory of TF201 lags and make annoying ANR
- I don't want to use the data2sd version that keep SD always inserted
- browser2ram show the way but only for browser and consume RAM
Version 2.x use an EXT4 partition on your SD:
- This version needs an additional EXT4 partition on your MicroSD to works
- First primary partition is your usual NTFS, FAT32 or exFat, and second one must be at least 768Mb or 1Gb
- You must be root, have a unsecured kernel, have a proper busybox build and using STOCK 4.1 rom
- I also include a second script "obb2sd" in this zip, it will bind big OBB database from internal to external
but only activate if your MicroSD is at least 32Gb (bind /sdcard/Android/obb/ to /Removable/MicroSD/.obb/)
Benefits of using an EXT4 partition instead:
- No more permissions errors that cause FC in some application (1.x version of my script)
- Better speed, EXT4 is tweaked for cache utilization
- Works with symlinks instead of bind mount
- No options to script just run "cache2sd", all application cache is moved to SD
- EXT partition not visible from media scanning, so less battery drain
Limitation of using EXT4 partition:
- MicroSD should not be removed but you could do it
- New installed apps will not set up automatically cache to SD
=> So every time you umount/mount your MicroSD, install a new app, just run command "cache2sd" and "obb2sd" or let an app like Tasker do it for you !!! Or reboot device !!!
How to use / it works:
- Coming from 1.x version, please uninstall it before (see 2nd post)
- Flash "TF_stock4.1_cache2sd.ext.zip" from recovery and it will activate itself if a second partition is present on MicroSD
- At first run the second partition will be erased and formatted as EXT4 and aligned to sector if needed
- /cache mount point to internal memory (mmcblk0p2) is replace during boot by MicroSD ext partition (mmcblk1p2)
- It will make a symlink from app cache (/data/data/app.name/cache) to your ext SD newly mounted as /cache
FAQ:
- Will it work on other rom like ported 4.2 or AOSP 4.4?
maybe it should but I haven't tested it, don't flash zip as it include binary for 4.1,
just download xbin_binary.zip and put cache2sd script to /system/xbin/
and before running it check that your rom have these binary installed e2fsck, mke2fs, tune2fs in /system/bin/
check log in /data/local/link2sd.log !!!! and let me know
- Gain will not be the same for each app as they use or not cache, but overall performance is really improved
you can say goodbye to almost all lags with a stock rom !!!
- Old version 1 is still available at 2nd post and don't use ext4 partition and have some bugs
Without running my script:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
With cache2sd activated on EXT4 partition:
.
XDA:DevDB Information
CACHE2SD Boost system by moving app's cache to SD, Tool/Utility for the Asus Eee Pad Transformer Prime
Contributors
meldrak
Source Code: http://forum.xda-developers.com/showpost.php?p=40887418&postcount=2
Version Information
Status: Stable
Current Stable Version: 2.1
Created 2013-10-15
Last Updated 2014-12-11
Version 1.x
Here is the old version 1.5 with no needs of additionnal ext4 partition
How it works:
Cache2sd is a binary to be called in a terminal or adb
Works on stocks ROM JB 4.1 and 4.2
Works on SD formated in EXFAT, NTFS and FAT32
you must be root and have a proper busybox build
it will make a bind from app cache (/data/data/app.name/cache) to your external SD (Android/cache/app.name)
If you remove your SD, application are still useable if you reboot your device or disable cache2sd by command line
Configuration:
- Just flash the one of the zip in TWRP recovery
TF_cache2sd_autostart.zip with init.d autostart (by default only browsers are cache2sd until you configure it)
TF_cache2sd_binary.zip (you'll have to run it manually)
- First time type cache2sd -c to configure it
Code:
sh-3.2# cache2sd -c
Cache2sd for Internet (browsers, playstore, downloads) is enable
Activate it Y/N : y
Cache2sd for Google Apps (maps, gmail, youtube, etc...) is enable
Activate it Y/N : y
Cache2sd for All Apps (except system's apps) is disable
Activate it Y/N : n
Android Data (/sdcard/Android/data/) to extSD is enable
Activate it Y/N : y
sh-3.2#
use All Apps with caution, it may cause FC with some apps, you should consider using data2sd kernel if you can
- Activate it with cache2sd -m
Code:
sh-3.2# cache2sd -m
Cache2sd enable
sh-3.2#
- Check current active binds cache2sd -a
Code:
sh-3.2# cache2sd -a
/data/data/com.google.android.apps.maps/cache
/data/data/com.google.android.apps.plus/cache
/data/data/com.google.android.gm/cache
/data/data/com.google.android.googlequicksearchbox/cache
/data/data/com.google.android.music/cache
/data/data/com.google.android.youtube/cache
/data/data/com.android.browser/cache
/data/data/com.android.vending/cache
/data/data/com.android.providers.downloads/cache
sh-3.2#
- and desactivate it with cache2sd -u
Code:
sh-3.2# cache2sd -u
Cache2sd disable
sh-3.2#
Bugs:
- downloads from playstore don't begin or block (generaly after 10 consecutive downloads)
resolve it by clearing cache of app "Download Manager" in Android settings (rebooting or doing the same as below will work too)
- some apps may Force Close with cache2sd enable
try to resolve it by disabling it with cache2sd -u run again your app and reactivate it with cache2sd -m
if FC again tell me wich app, I'll add it to exclude list
- running apps with cache2sd enable and MicroSD umounted may cause a reboot (depends of apps)
so if you need to use tablet without your sd for a moment disable it with cache2sd -u or see tips
To report me a problem:
- provide me the log, get the file with command "cache2sd -l"
- give me your SD details with command "adb shell mount | grep vold"
- give me your ROM version with command "adb shell cat /system/build.prop | grep ro.build.version"
To remove the autostart script:
- 1st reboot without SD inserted, so script will revert cache to internal
- remove the script with command "adb shell rm -f /system/etc/init.d/S99cache2sd"
- type cache2sd -r to disable/erase all cache and revert to internal memory
Tips:
you can change SD mount point with command cache2sd -sd
/system must be ReadWrite access before doing it
Code:
sh-3.2# cache2sd -sd
MicroSD mount point is set to /Removable/MicroSD
If you need you can change it to:
1. /Removable/MicroSD (stock rom)
2. /storage/sdcard1 (cyanogen rom)
Your choice (1 by default) :
Better to use script with tasker and set "cache2sd -m" with event sdcard is mounted
and "cache2sd -u" when sdcard umount or ejected. You'll nerver have to reboot tablet in this case
You also can create desktop shortcuts with script manager
(Don't forget to run script as root with tasker, script manager and other like apps)
If you have FC on a app, maybe some sub folders have been created with wrong permissions
so disable cache2sd et re enable it, to auto apply good permissions to folders
- Check log with cache2sd -l
Code:
sh-3.2# cache2sd -l
Starting on Wed Aug 21 16:33:52 CEST 2013
SD found after 0 sec. in /Removable/MicroSD
com.google.android.apps.books doesn't exist yet
com.google.android.apps.currents doesn't exist yet
Binding com.google.android.apps.maps
Binding com.google.android.apps.plus
com.google.android.apps.unveil doesn't exist yet
Binding com.google.android.gm
Binding com.google.android.googlequicksearchbox
com.google.android.keep doesn't exist yet
Binding com.google.android.music
com.google.android.videos doesn't exist yet
Binding com.google.android.youtube
com.google.earth doesn't exist yet
Binding com.android.browser
com.android.chrome doesn't exist yet
Binding com.android.vending
Binding com.android.providers.downloads
Finished on Wed Aug 21 16:33:52 CEST 2013
sh-3.2#
v1.1 changelog - v1.2 changelog - v1.3 changelog - v1.4 changelog - v1.5 changelog
meldrak said:
I made a script to move application cache from data to microSD.
The reasons:
- Internal memory of TF201 lags and make annoying ANR
- I don't want to use the data2sd version and must have the
- browser2ram show the way but only for browser and consume RAM
How it works:
- detect if MicroSD is present (90s of delay)
- make a backup of current cache in data
- copy it to microSD in a new forlder named cache (the 1st time)
- symlink cache application to microSD (the 1st time)
- other time will just check if symlink and folders are present
So if you eject your SD just reboot tablet and cache will revert to internal data
or if your are not using one of these apps while umouting SD you can still use the tablet until you remount the SD
Application that will be cached to sd (if installed):
Browser >> com.android.browser
Chrome >> com.android.chrome
Downloads >> com.android.providers.downloads
Gmail >> com.google.android.gm
GoogleNow >> com.google.android.googlequicksearchbox
Youtube >> com.google.android.youtube
Google+ >> com.google.android.apps.plus
Street >> com.google.android.street
Dropbox >> com.dropbox.android
Amazon AppStore >> com.amazon.venezia
Works on stocks ROM and maybe others, you must have a kernel with init.d support and be rooted
Just flash the zip in TWRP recovery
Click to expand...
Click to collapse
works fine here just had to clear the data from all those apps after or they just crash.
---------- Post added at 11:48 AM ---------- Previous post was at 11:39 AM ----------
actually its not working it doesnt create the folder but it says its enabled...
Good to see this. Cant wait to try it. Just a few questions
-When you say speed up. Do you mean as in how long it takes to load the app, the device itself, gaming and etc?
-how do we verify if it works. for example if I have a few games should I uninstall them then reinstall to see if the data shows up on card?
Thanks!!
@joeyddr could you provide me the cache2sd.log in /data ?
tell me the rom version you are using, and the filesystem used on your microsd
@Lyvewire this script will not speed-up games, but only apps that use cache to render web content
the device will boot the same as before, not longer, no better
to check if enable, read the cache2sd.log in /data and you also have a folder named /cache on your microsd
and to verify just load some web page in browser and you should navigate into it without any hangs !!
or a mail in gmail with many images in atachment
I did the test on my TF201 ROM and my microSD 32Gb Kingston class 10 formated in exFat
and now I didn't see anymore ANR popup while browsing
ATTENTION the script don't touch the data of the app !! but only the cache !!!
meldrak said:
@joeyddr could you provide me the cache2sd.log in /data ?
tell me the rom version you are using, and the filesystem used on your microsd
@Lyvewire this script will not speed-up games, but only apps that use cache to render web content
the device will boot the same as before, not longer, no better
to check if enable, read the cache2sd.log in /data and you also have a folder named /cache on your microsd
and to verify just load some web page in browser and you should navigate into it without any hangs !!
or a mail in gmail with many images in atachment
I did the test on my TF201 ROM and my microSD 32Gb Kingston class 10 formated in exFat
and now I didn't see anymore ANR popup while browsing
ATTENTION the script don't touch the data of the app !! but only the cache !!!
Click to expand...
Click to collapse
I couldnt find that folder in file folder. I checked Internal Android Data folder and regular data folder. I also checked ext card data and only titanium data was in there. When I flash the zip it seems like it flashes so fast that its not flashing but says finished like it did. Maybe I'm missing something?
why are you talking about ext, regular data ??? are you using a rom with data2sd?
the log is in /data so you need a root explorer or do it with adb to check
and to check if zip correctly flashed just verify in /system/etc/init.d if the file 90cache2sd is present
OP your script works great, however once I reboot, I get a bunch of force closes and crashes. The only way to fix it is by wiping the dalvik and cache in recovery, but then every time I reboot I get the crashes and force closes again.
I'm running Hairy Bean 2.11 if that helps.
Thanks for doing this by the way, it's a great feature for our tablet!
thanks for your feedback
tell me wich app have FC, and filesystem used on your SD
meldrak said:
why are you talking about ext, regular data ??? are you using a rom with data2sd?
the log is in /data so you need a root explorer or do it with adb to check
and to check if zip correctly flashed just verify in /system/etc/init.d if the file 90cache2sd is present
Click to expand...
Click to collapse
Ok I get you. I didnt realize I should be checking via root explorer folder. Strange thing happened. I cut my tablet off at work and then when I got home and cut it back on a whole list of things started force closing. I ended up rebooting deleting cache and dalvik and everything was fine. However when I did a regular reboot it all these force closes came back. Basically anything google related or bloatware. Playstore, frame work, Gmail, Browser and some other things. I ended up wiping rom and starting over. I'm using Energy Rom from Dec. 22nd. I'm not sure if this ROM is compatible but I'll find out after I redo custom ROM and back it up b4 hand I flash this, this time ..
ok it should work on this rom as it is the same base as mine ...
so maybe the filesystem is the cause I have to do some tests
I'm using exfat and I think most users use ntfs or fat32
I updated the 1st post with information to give me for debugging
and the way to do a rollback
meldrak said:
ok it should work on this rom as it is the same base as mine ...
so maybe the filesystem is the cause I have to do some tests
I'm using exfat and I think most users use ntfs or fat32
I updated the 1st post with information to give me for debugging
and the way to do a rollback
Click to expand...
Click to collapse
I'll reformat my card to EXfat and see if that works. Also I wasnt sure if you replying to me using Energy or the other member that asked about Hairybean pertaining to what your using.
sorry but by answer was for you, new energy and hairybean are 4.2 version so not the same as mine
I add a new script that will only move browser cache to sd instead of all apps it will limit problems
Hi Just tried this on Androwook 2.2, browser only version, runs very quick and smooth, thanks
Sent from my Transformer Prime TF201 using Tapatalk HD
boldnuts said:
Hi Just tried this on Androwook 2.2, browser only version, runs very quick and smooth, thanks
Sent from my Transformer Prime TF201 using Tapatalk HD
Click to expand...
Click to collapse
There was a Browser2Ram script under tweaks in the installation for the 2.2 release that should have worked faster than this.
What you have done is move the cache to the External SD. What the script included does it move the cache to ram.
Ram should be faster than External SD.
In other words I don't recommend that script but if you are happy with it then all is good
Hi flumpster
I do not agree with you .. exept for RAM that is faster than SD
I was using browser2ram before and that's why I made this script because of the 50mb of RAM used and lost for other apps
and if you reboot the device, cache is lost and need to be rebuilt and finally become sometimes slower ...
with a good SD (class 10 in my case) you'll have same speed result as browser2ram
exept in case of your wifi/internet is faster than your SD write speed
and with this method you can also move cache from other apss than browser
you should give a try
meldrak said:
Hi flumpster
I do not agree with you .. exept for RAM that is faster than SD
I was using browser2ram before and that's why I made this script because of the 50mb of RAM used and lost for other apps
and if you reboot the device, cache is lost and need to be rebuilt and finally become sometimes slower ...
with a good SD (class 10 in my case) you'll have same speed result as browser2ram
exept in case of your wifi/internet is faster than your SD write speed
and with this method you can also move cache from other apss than browser
you should give a try
Click to expand...
Click to collapse
Hi mate..
I was only referring to the browser version that the other person was commenting on above.
I have not tried your full script as that would basically be the equivalent of running a data2sd version of my rom and it is fully dependent on the speed of the SD card as you said.
I personally have a class 10 UHS-1 but most people do not. Hence the browser2ram script being far faster for most people.
I am not picking on you in any way and wouldn't dream of doing so.
I think your main script would work wonders for people who do not use data2sd and a reasonable class card but as I said most people do not have this and some don't even use a micro sd card.
I will do a test out of curiosity tho as I have class 2,4,6, and 10 here and will let you know but there is no way this is going to be faster than ram.
Again, this is just my personal opinion and not to be taken as fact.
Please don't take this the wrong way :angel:
edit... hell of a lot of I's in there lol
Also one last thing.. When you say you was using browser2ram before was you talking about the apk? That doesn't even work on 4.2.1 and had to be implemented as a script similar to what you have.
don't worry I'm not taking this the wrong way, my english is not perfect so I hope I don't offend you
as I say my script is for people that don't want to use data2sd, but it isn't an equivalent ...
data2sd is really faster but you can't eject the SD and you'll need a fast one
for the browser2ram, yes it was an apk but I'm still on 4.1 so it was working fine
but my tests give me the same results between cache to sd or cache 2 ram
but I only have a 4Mbs/s internet connexion with a card that can write up to 12Mbs/s :laugh:
so it could be interesting to have some other feedback ans tests
I'm on the ParanoidAndroid ROM and this doesn't work, most likely because it microSD is at a different location (/storage/sdcard1 rather than /Removable/MicroSD). You might want to use an array to look for the MicroSD slot rather than just one location since I know other ROMs uses different mounting points as well.
Checking the final mount point is to be sure SD is ready
That's why I set the mount point as a variable that can easily be modified in the script
In any case could you give me the result of the "mount" command to be sure it's the same dev point used
Envoyé depuis mon Transformer Prime TF201 avec Tapatalk
Good day , I have a general question about these and hope someone could explain me what exactly happens there:
So , I played around with some props values ( also looked a bit into the aosp code / dev docu ) and set these values with magisk as system.prop
dalvik.vm.isa.arm64.features=Default
dalvik.vm.isa.arm.variant=cortex-a76
dalvik.vm.isa.arm.features=Default
dalvik.vm.heapstartsize=16m
dalvik.vm.heapgrowthlimit=256m
dalvik.vm.heapsize=512m
dalvik.vm.heaptargetutilization=0.5
dalvik.vm.heapminfree=8m
dalvik.vm.heapmaxfree=32m
dalvik.vm.dex2oat64.enabled=True
dalvik.vm.dex2oat-flags=--debuggable
dalvik.vm.dex2oat-filter=everything
dalvik.vm.image-dex2oat-flags=--debuggable
dalvik.vm.image-dex2oat-filter=everything
dalvik.vm.dex2oat-Xms=16m
dalvik.vm.dex2oat-Xmx=512m
persist.dalvik.vm.dex2oat-threads=8
dalvik.vm.dex2oat-threads=8
dalvik.vm.image-dex2oat-threads=8
dalvik.vm.boot-dex2oat-threads=8
dalvik.vm.jitmaxsize=128m
#extrem values ! Default would be 10000
dalvik.vm.jitthreshold=2500
dalvik.vm.jittransitionweight=333
dalvik.vm.jitprithreadweight=333
pm.dexopt.install=speed
pm.dexopt.bg-dexopt=speed
Note here that I used first dalvik.vm.dex2oat-Xmx=256m instead of 512m , after a Dalvik clean up and rebuild I had 248m of Dalvik cache , no noticable performance impacts etc , I though It would be better to raise the value. In the same reboot process to enable the changes I also did an update , now my Dalvik cache is empty and can't be rebuilt , the interesting part is that my system is now quicker ? Especially in games I can notice a significant boost in startup time and menu transitions , but firefox (the only app atm) doesn't like this but can be used normaly after 3 "crashes-to-launcher"
Side Note: I don't need answers how to repair anything , I'm curious what's going on
So my questions is first how can it be faster if it presumably uses the default java JiT in memory instead of creating Dalvik cache + odex files
And what happend that Dalvik etc can't be normaly initiated ? Does it not like the settings and simply crash , or is this the right behavior for my settings and I have simply no idea what I'm doing ?
Thank you for reading and any helpfull response
Both the Dalvik ( uses Just-In-time compiler, JIT ) and the ART ( what uses Ahead-Of-Time compiler, AOT ) are a Android runtime. ART is the default runtime since Android Lollipop. Knowing this you have to clarify what Android OS you are trying to hack.
jwoegerbauer said:
Both the Dalvik ( uses Just-In-time compiler, JIT ) and the ART ( what uses Ahead-Of-Time compiler, AOT ) are a Android runtime. ART is the default runtime since Android Lollipop. Knowing this you have to clarify what Android OS you are trying to hack.
Click to expand...
Click to collapse
Right it would probably good to know my setup , I use the Mi 9T with Miui 12.3 on android 11 , ram is 6gb , cpu/gpu is SDM730
Thank you for the first clarification , so does this mean the JiT is on newer OSs ineffektiv ? Or just a backup technique