• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root App2sd problem?

Rotten Ross

Member
ok, so i'm using pyramidmod007 which supports App2sd but for some strange reason when i install an app it does get stored on the sd ext but it also gets put on the internal memory too

here is my quick system info

SD card Storage: Total:13.85 GB, Free 3.29 GB

A2SD Storage Total:1.03 GB, Free 558 MB

Internal Storage:Total: 148MB, Free 18 MB

When i unistalled angry birds (i choose that to test), the info went to

SD card Storage: Total:13.85 GB, Free 3.29 GB

A2SD Storage Total:1.03 GB, Free 578 MB

Internal Storage:Total: 148MB, Free 19.89 MB

i don't understand why stuff is still be put on the internal memory





 
There are a number of components in an app. Some of these (the apk, and in many cases the dalvik cache) are moved to ext, but not all. In particular if an app includes a shared object library this is not moved to ext by an a2sd+ script.

Angry birds includes a 1.9 MB library file, /data/data/com.rovio.angrybirds/lib/libangrybirds.so, which fits your observation rather nicely.
 
There are a number of components in an app. Some of these (the apk, and in many cases the dalvik cache) are moved to ext, but not all. In particular if an app includes a shared object library this is not moved to ext by an a2sd+ script.

Angry birds includes a 1.9 MB library file, /data/data/com.rovio.angrybirds/lib/libangrybirds.so, which fits your observation rather nicely.


thanks for the info, i'm just slightly at a loss as i am getting the message about low memory and finding it hard to update my apps as my internal memory is low, is the any way to stop this?
 
I'm not familiar with that ROM, so don't know whether it moves the dalvik cache by default or whether you need to do something for that. But if uninstalling angry birds only changed the /data usage by 1.9 MB I reckon the dalvik is probably on ext already.

One thing that can help is moving apps with a large lib to SD (via the applications menu). With Gingerbread that does move the lib as well as the apk (didn't with Froyo). Aesthetically it's not pretty, as you then have the app split in 3 places (some data on internal, the dalvik cache on ext, and apk and lib in .android_secure), but it does work and can save space if you are getting short. Doesn't help with all apps, only those with large libs. You could use Quick System Info to see which apps are using most space in /data, and if /data usage doesn't decrease significantly when you move an app, move it back to phone (just to be neat).

Otherwise, use QSI to check that no apps are using unusual amounts of /data space (especially things like Facebook or Contacts Storage) - standard memory usage checks, but rooted phones aren't immune to these issues.

But I suspect that you may have no particular problem - you are using almost 0.5 GB of ext storage, and some /data space is still used by each app, so you may well just be reaching the limit of what you can fit in the 148 MB. So if you can't save enough space by the measures above, one thing left might be to go S-Off and repartition your internal storage (which will need a ROM that can fit in a smaller /system partition). Or go the data2sd/data2ext route, but that needs a fast card and I've no experience of it, so can't really advise.
 
i already have s-off'd using alpharev, but with my rom being a sense 3 rom i highly doubt it will take up little space. how do i find out how much space the rom is using? i will try the other solutions first and see what it comes up with
 
Quick System Info is your friend: on the Basic Info screen look at "System Storage". That's you /system partition (where the ROM lives), and you can see there how much is being used and how much is free.
 
No, not a lot really. Shrinking the /cache partition would gain you more, if that ROM can handle a small cache (i.e. redirect market downloads to somewhere else ). If that were the case I could imagine a custom hboot or mtd giving you an extra 45MB (shrink /system to 240 MB and /cache to 5MB) but if the ROM can't do what I said above you'd not be able to download apps larger than the /cache size.

Otherwise there's the data2sd thing, or just cleaning up any apps you don't need any more.

Clearing app caches might help a bit as well - you can build up a good few MB in there. That and the move to SD thing is about all I can think of.
 
yeah looks like cleaning up is the only option really, don't know much about data2SD and don't fancy messing up my phone if it all goes wronf, cheers for the help mate, might just go back to Leedroid, never had a problem with his rom/
 
Back
Top Bottom