A2SD Cache with A2SD Apps? - Hero CDMA Themes and Apps

I was wondering why haven't any roms implemented a2sd cache?
http://forum.xda-developers.com/showpost.php?p=6089822&postcount=908
Even with apps2sd the cache installs on the phone i think? but with the patch above, i've noticed a HUGE amount of free internal space..
credits to tkirton

Related

help with dalvik cache or cache.

hello guys,
id like to thank jf for making 1.5 the best experience ever.
ok so im running jf 1.5 and i used the apps2sd app to move my apps and dalvik-cache over,
but i noticed that when i moved the dalvik cache it made my menu super slow. and it takes like 10 seconds to reload all my icons and widgets..
can anyone point me to or help me out in moving the dalvik cache back to the internal memory?
can anyone help??
I would use adb tools for this since it's a lot quicker.
But, you need to use busybox
from terminal or adb shell
busybox cp -a /system/sd/data/dalvik-cache /system/data/data
I would boot into recovery mode after doing the copy.
Then in recovery, I'm pretty sure I did
busybox rm -rf /system/sd/data/dalvik-cache
I'm not giving you exacts, but I had the EXACT same problem, and it's not your Dalvik cache that's the problem, it's either other cache's you set up like browser (not sure) or for sure if you moved /data/data to the SD that's going to slow things down A LOT.
If you have a class 2 that may be a problem.
But I have apps, apps private, and dalvik-cache on my class 4 sd card. Everything is super snappy, with my system overclocked to 527 MHz.
Working great. Try that. Also look for move cache in recovery mode. That's how I put everything back. There's also a thread about moving cache back to internal memory. Or it's called undo cache.
yay bro thanks a lot!
now it doesnt lag as much.
btw i have a class 4 memory card.
i dont get why it was slow though?
i only moved the apps and the dalvik cache with the apps2sd app?
anyone???

[Q] Regarding the system cache after AlphaRev re-partitioning

Hello everyone, this is my first post on these forums!
I have rooted my HTC Desire, installed a Cyanogenmod 7.0.3 stable version, S-Off-'d, and partitioned the internal memory with AlphaRev CM7 r2 image. So far, everything seems to be working well, however, I noticed something curious after the repartitioning.
In quick system info, the stats are like this:
SD card storage - Total 7.05GB, Free 2.14Gb
A2SD storage - Total 457MB, Free: 140MB
Internal storage - Total 288MB, Free 140MB
System storage - Total 145MB, Free 16,38MB
System cache - Total 288MB, Free 140MB
If the CM7 r2 partition image has 5MB cache, why does the system info display a total of 288MB (same as internal storage)? While I had the stock partition, it displayed the correct 40MB of system cache. Again, it works just fine, but I wish to know what it means.
The second much noobier question is this: I use LauncherPro in CM7, since I like it much better than the ADW launcher. Does LauncherPro perhaps use the same system cache for it's caching? If that's the case, could the 5MB of system cache be too small for it to work correctly? I thought that the 5MB only for system cache was a bit small anyways, but I can't seem to find any faults for now and had no problems downloading very large apps from the Android Market as of yet.
I would be grateful if someone could provide me some answers.
P.S. I should also perhaps mention that I had re-partitioned the internal memory after I backed up my CM7 image with all the apps and settings. After the re-partitioning, I restored my nandbackup.
Nevermind, figured it out.

Q: DT Apps2sd (a2sd) hates me

After days and hours of searching and trial'n'error, im about to give up.
I installed DT's apps2sd script on my S5570 mini, and even though it frees up to 171 mb on my 178 mb internal storage, but for some reason it detects the apps2sd partition wrong in all custom roms I tried.
In one rom (emanoN) it detected my /cache partition/directory as sd-ext making it running out of space in 1-3 roms depending on size.
Due to the error with apps2d on this rom lately I then tried with CM7 to test.
In cm7, it detects the sd-ext with 206 mb partiton, even though its setup with 1GB ext4, and oddly doesnt move in size with installing apps. Again it runs out of space after installing a few apps again.
This is even though it should be tested and working on CM7.
Moving dalvik-cache and zipaligning app seems to work fine.
I tried partitioning using most guides online with either ext3 or ext4 without luck. With CWM and with ADB shell partitioning manually with blocks.
A2SD partlist and diskspace shows the partition is setup correctly.
Anything I overlooked and any ideas in getting this to work would be much appriciated.
I can confirm it actually intalls on the ext partition, but just shows it wrong, but before installing on ext partition, its downloads to /cache partition, which have to be cleared manually after an app install to get space for more apps.
The main problem here is im not able to install apps bigger than 20 mb, as thats the size of the cache partition..
Must be someone who got it working, who may know whats wrong?
Now I just need to get umount -l /cache and mount /sdcard/marketcache /cache into my boot..
Man, this is a timekiller..
Try S2E from the Market.
https://market.android.com/details?id=ru.krikun.s2e&feature=search_result
Thank you for the reply.. I tried simple2ext and I actually think this beats a2sd anytime, but it only works for CM.. and CM lacks an option I need for my phone..
But I guess im "stuck" at CM for now.. If you cant get the best, get the nextbest

New to CM7

Hi all,
So last night I decided to give Cyanogenmod7 a try. I came from MIUI.us 2.1.20 - I just love MIUI, but it's a bit too demanding for the Milestone. So I have CM7 up and running, and it is a lot more snappy. But now, I'm having trouble installing some apps.
I tried installing my bank's banking app, but it didn't install - checked the market and it doesn't appear. Same thing with WhatsApp!! If it were working, I might just become a CM7 user..but it's not working.
Am I missing something? I installed after doing a full wipe, after which I installed DT A2SD scripts and then gapps-20111216 (although didn't see gmail or market etc after gapps, so installed those via apk).
What's the deal here?
Thanks.
Sent from my Milestone using Tapatalk
Ok, just wiped again, and reinstalled all. CM7 then gapps then dt a2sd. So far it's working.
Sent from my Milestone using Tapatalk
googleservicesframework.apk and vending.apk are all you need for using market. Try to reinstall them. May you success.
Ok, so now my problem is A2SD. It's not working! A2SDGUI refuses to go in, and when I do a check, I get a segmentation fault...I've never had this issue before. I've tried reinstalling DT A2SD from withing recovery and still, nothing. Please assist, I just need to get set up properly now.
Regards
Sent from my Milestone using Tapatalk
DT scripts dont work ...use an external partition (app2ext)
d.casper.b: CM7 for Milestone already comes with its own ap2ext scripts that are automatically used if there is ext partition present on your sdcard.
You should not install any 3rd party app2ext scripts as they are very likely to be conflicting with the scripts that are already there.
Thanks kabaldan.
I'll check it out.
I was even going so far as trying to use Link2SD from the market..
How'd I know if it's working? By monitoring the available internal storage?
Sent from my Milestone using Tapatalk
d.casper.b said:
Thanks kabaldan.
I'll check it out.
I was even going so far as trying to use Link2SD from the market..
How'd I know if it's working? By monitoring the available internal storage?
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
when you will enable app2ext you will see the total space in your storage rise to 197 mb
I am not winning. I did a factory reset and flashed cm7 and gapps (not dt a2sd).
I did a test, internal storage was at 191mb, then I installed opera mobile and it went down to 182mb. Then uninstalled it again. Went into cyanogenmod settings and set install location to external. Installed opera again, but it was no different. Moving it to sd under 'manage applications' increased the internal memory again, but that's just moving the app to the FAT32 partition of the sd card.
So it's not seeming to work for me for some reason.
Sent from my Milestone using Tapatalk
EDIT: I really don't want to be a nuisance, but now, looking at the available storage using "Quick System Info", I noticed after uninstalling "Opera Mobile", 9mb was freed on internal storage & 13mb on the ext partition.
So, perhaps it is working, and since the dalvik cache is (I assume) on internal storage, the storage is still decreasing. Am I correct? If so, is there a way to also move dalvik cache to the ext partition - I had it like this on MIUI & never looked at available memory ever again.
First of all, have you really partitioned your SD card? Make sure you followed the 3rd step on this guide: http://www.mrmuh.com/2012/01/update-a-motorola-milestone-from-motorola-firmware-to-cyanogenmod-7/ . You should have your SD Card partitioned with two partitions, the first should be FAT32 that's used normally on Android, and the second EXT3 or EXT4. Obviously, make sure you have a backup of your FAT32 partition before partitioning.
Second, you should understand how the apps2ext scripts on CM7 work. Application installs that would be stored on internal memory are rerouted to the EXT3/4 partition on the SDCard. This happens at the underlying system (linux) level, Android (that runs on top of linux) is not aware of this rerouting, so, as far as Android "knows", apps that are rerouted to the EXT partition are on the phone's internal memory. That means that you should make sure that apps you need installed on the EXT partition of the SD card are shown in "Applications > Manage applications" list to be installed on the internal memory. Yep, it's confusing, but once you understand how it works and why it works that way, it makes sense.
Third, the fact that apps are rerouted to the EXT partition doesn't mean that everything about the app will live on the ext partition: it means only the main application package will live on the ext partition, application data is still stored on the internal memory. For most apps, the amount of data used for application data are much smaller than the application package, but in some apps the amount of application data from the app may often surpass the size of the app itself - for example, in my phone, Tweekdeck stores about 9Mb of data, which is about 10 times the size of the application itself (820kb) - presumably this amount of data is cached tweets, pictures, etc. But that case is usually the exception, not the rule, I've just mentioned it so you understand that using apps2ext doesn't mean your internal memory will always stay unused, it just means it will be used (way) less.
Finally, regarding the CyanogenMod Settings location setting, if you understood what I said above, you should now understand that it should actually be set to always install to "Internal", rather than external. However, there's a bug in this that you should be advised, that not all apps will respect this setting: some apps will install to external regardless of how you've configured that setting (meaning the app will use Froyo/Gingerbread native Apps2SD, hence being installed to the FAT partition of the SDCard). So, when you install a new app, check on app management if it didn't get installed to the SDCard, and move it to the internal memory if that's the case. For these kind of apps, you'll have to do it every time you update the app too.
Thanks, I edited my previos post..
I actually have 3 partitions, a FAT32, an ext2 (maybe it's ext3, but doubt it - partitioned some months ago, so my memory's hazy), and a SWAP - which I should get rid of, but am too lazy.
I understand entirely what you've said, I know that internal is really ext if working, and sd is FAT32 partition.
You see, I'm just new to this rom and have to trial and error until I understand, with miui you just flashed the rom and the a2sd scripts and didn't bother again (maybe only to move an app that installed to FAT partition). But it seems CM7 is simply just to flash the rom and you're good to go. But as I was pondering in my previous post...is there any way to move dalvik cache to ext?
Thanks for putting up with me..I'm almost there.
Sent from my Milestone using Tapatalk
d.casper.b said:
Thanks, I edited my previos post..
I actually have 3 partitions, a FAT32, an ext2 (maybe it's ext3, but doubt it - partitioned some months ago, so my memory's hazy), and a SWAP - which I should get rid of, but am too lazy.
I understand entirely what you've said, I know that internal is really ext if working, and sd is FAT32 partition.
You see, I'm just new to this rom and have to trial and error until I understand, with miui you just flashed the rom and the a2sd scripts and didn't bother again (maybe only to move an app that installed to FAT partition). But it seems CM7 is simply just to flash the rom and you're good to go. But as I was pondering in my previous post...is there any way to move dalvik cache to ext?
Thanks for putting up with me..I'm almost there.
Sent from my Milestone using Tapatalk
Click to expand...
Click to collapse
in the market you will find an app called s2e which moves app data, davlik cache to sd
also link2sd also free's up more space and makes cm7 snappier
please don't install such things to CM7 for Milestone unless you know what you are doing and you are able to resolve conflicts with the existing scripts
dalvik-cache is already moved automatically
if you want to free more space in /data, enable lib2ext to move native libraries to ext - it's mentioned in the changelog for 7.1.2 release
app data itself should not be moved as it can cause instability
d.casper.b said:
Thanks, I edited my previos post..
I actually have 3 partitions, a FAT32, an ext2 (maybe it's ext3, but doubt it - partitioned some months ago, so my memory's hazy), and a SWAP - which I should get rid of, but am too lazy.
Click to expand...
Click to collapse
Yeah, get rid of swap, there won't be any use for it (for now anyway) and it's best for you at this point to have a known working structure (two partitions, 1st FAT, 2nd ext3/4) for your SD as you're troubleshooting your problems/questions, it'll make it easier for us too as this will eliminate potential points of failure or inconsistencies. And you should really consider upgrading to a journaled filesystem, either ext3 or ext4. Using ext2 is unreliable because Android doesn't umount the ext partition cleanly on reboot or shutdown, so you may have problems with apps disappearing or misbehaving every other reboot. Using ext3/4 with journal elimitates this problem since the journal is just replayed for the uncleanly umounted partition and the filesystems behaves more consistently.
d.casper.b said:
You see, I'm just new to this rom and have to trial and error until I understand, with miui you just flashed the rom and the a2sd scripts and didn't bother again (maybe only to move an app that installed to FAT partition). But it seems CM7 is simply just to flash the rom and you're good to go. But as I was pondering in my previous post...is there any way to move dalvik cache to ext?
Click to expand...
Click to collapse
The apps2ext script built on CM7 should do this by default - you probably already have your dalvik-cache on the ext partition. To check this, go into OR, enter the console and type: "ls /sddata/dalvik-cache" . If it returns a list of files, you've already got the dalvik-cache on your ext partition. Another option is setting the option dalvik.vm.dexopt-cache-only to 1 in the file /system/build.prop . This will put all dalvik-caches (both from user apps and system apps) on the phone's internal cache partition, thus still freeing space on the internal memory but without using the ext partition, but that's not recommended if you install too many apps because the cache partition may run out space and that will spawn all kinds of weird behavior on Android. The safer route is just using the default configuration anyway (user apps dalvik-cache on sd-ext).
Another option to further reduce internal memory use is using lib2ext, that will move user apps native libraries to the ext partition, but the memory gain in this case is dependent on which apps you use and how big their native libraries (if they even have one) are. To activate it, just go into the Terminal app (with Android booted) and type:
$ su
# lib2ext
And reboot. The libraries will be moved to the ext partition during boot. Make sure you have a big enough ext partition to hold everything (apps, dalvik-cache and apps libs) - the size to recommend is very dependent on how many apps you use and how big they are, but I'd say 512Mb would be the bare minimum.
in the market you will find an app called s2e which moves app data, davlik cache to sd
also link2sd also free's up more space and makes cm7 snappier
Click to expand...
Click to collapse
DON'T! JUST DON'T! These third-party apps will cause all kinds of problems with CM7 builtin apps2ext.
EDIT: Oh well, Kabaldan already put all my rambling much more succintly than I could... I'm way too talky
well i was jus trying to help.. .anyway guys thanks i guess i won't be needing those apps anymore ...sorry for my noobness
Thank you so much guys!
It seems like it's working. I will check out lib2ext & the other suggestions tonight or over the weekend (on my way to work now).
I must say, I thought the move to CM7 would be a temporary one, but the speed gain is just what I needed, & the tweaks I thought I'd miss I am finding hidden in the settings .
Just wondering on the battery now - but I've been fiddling non-stop.
So let me play a bit more the weekend & I'll merge my ext2 and SWAP partition into one ext3 partition.
Thanks all, and kabaldan for your hard work on this rom.
Sent from my Milestone using Tapatalk
Just as I was on my way...
Everything's running fine, A2SD works. But now, I partitioned my SD card with a 2nd partition (ext3, it was ext2), but now widgets are not loading. Checked the apps install location, and it's 'internal', ie. ext3. I never had this before. I think maybe it's due to the filesystem now?
EDIT: Ok, ext2 is doing the same. I can't keep starting from scratch the whole time guys.
EDIT2: It's now suddenly working! Just have a Fat32 and an Ext3 partition. But I don't understand because it's been setup like this twice before with no success. I'll hold thumbs!
PS, CyanogenMod is quite up my alley now, speed is awesome and I'm happy.
Sent from my Milestone using Tapatalk

[q]sgy a2sd hybrid rom

In my a2sd, dalvik cache is on sd ext. Is that correct?
Yup. Absolutely. This helps save a lot of space .
However do NOT boot without the memory card as the app data is on the sd-ext and you'll get multiple force closes
Hit THANKS if this was helpful
Sent from my Blade using xda premium
confirmed

Categories

Resources