I understand that the solution to this question may already exist in the forums, however, I did check high and low for it, and was unable to locate one.
Here goes:
I like (as I'm sure others do) to install apps2sd, something I'm able to do thanks to the actively-rooted and cyanogen-modded N1 that I use.
Unfortunately, the actual *install* files *themselves* from all Market-downloaded apps seem to remain in the phone's internal memory, clogging up preciously limited space. How do I get rid of these install files? I tried using a file manager to go into the mnt/asec directory to get rid of *.pkg's, but these seem to be uninstall-protected (I'm not even sure if I'm making a mistake from the get-go in trying to purge the *.pkg's), so I'm kind of back to the drawing board on this one.
Any help on this would be pretty invaluable folks.
Thanks,
Eli
If you've installed a lot, your dalvik cache will grow pretty big. That's found in /data/dalvik-cache.
Thanks Rusty - but my /data dir is completely empty (unless there are invisible folders; if there are, who you know how I can make them visible?).
Best,
Eli
You need SU access to view /data, make sure what you're using to browse it supports that.
Ahh, thanks Rusty - will do that
Your DATA folder is inaccessible, unless you use Root Explorer or other file explorer with root privileges (ES Explorer, for example - but it doesn't work with all ROMs).
There are no PKGs. There are APKs. And you're wrong in your assumption that they aren't used. This is no PC, this is Android, forget what you used to know, you need to learn again. APKs are the actual applications being ran, without them you can't execute anything, and using old Apps2SD, AKA Apps2EXT, you can move your /data/data to SD (EXT partition) and /data/dalvik-cache to /cache. CM doesn't support Apps2EXT, but it can be easily installed and used, following the guide in DarkTremor's thread. Read Wiki in my sig, it'll point you in the right direction. You can start by reading FAQ, question 9.
seekingandroid said:
I understand that the solution to this question may already exist in the forums, however, I did check high and low for it, and was unable to locate one.
Here goes:
I like (as I'm sure others do) to install apps2sd, something I'm able to do thanks to the actively-rooted and cyanogen-modded N1 that I use.
Unfortunately, the actual *install* files *themselves* from all Market-downloaded apps seem to remain in the phone's internal memory, clogging up preciously limited space. How do I get rid of these install files? I tried using a file manager to go into the mnt/asec directory to get rid of *.pkg's, but these seem to be uninstall-protected (I'm not even sure if I'm making a mistake from the get-go in trying to purge the *.pkg's), so I'm kind of back to the drawing board on this one.
Any help on this would be pretty invaluable folks.
Thanks,
Eli
Click to expand...
Click to collapse
1) The .apk isn't the install file it _is_ the application. The are no "install only" parts to an android app
2) Anything on /mnt/asec is already on your sdcard using froyo-style a2sd
3) .so files in /data/data/xxx/lib and /data/dalvik-cache are the primary causes of full /data partitions
Related
Tried firefox for android beta2 today and it freezed my phone, so I uninstall it only to realise that it locked 13MB of my internal memory permanently probably due to bad uninstall. Tried to reinstall it so that I can uninstall it again but it didn't allow me to install again saying that I don't have enough memory (though i still have ~45 MB free internal memory).
Anyone knows where does firefox install to? I couldn't find it in any of the app directory (not in data\app or system\app, nothing in dalvik cache and data\data as well). having 14MB memory locked is really a paint considering how small our milestone memory is.
Please help.
Thanks
en0203 said:
Tried firefox for android beta2 today and it freezed my phone, so I uninstall it only to realise that it locked 13MB of my internal memory permanently probably due to bad uninstall. Tried to reinstall it so that I can uninstall it again but it didn't allow me to install again saying that I don't have enough memory (though i still have ~45 MB free internal memory).
Anyone knows where does firefox install to? I couldn't find it in any of the app directory (not in data\app or system\app, nothing in dalvik cache and data\data as well). having 14MB memory locked is really a paint considering how small our milestone memory is.
Please help.
Thanks
Click to expand...
Click to collapse
bump. please can someone help. thanks
en0203 said:
bump. please can someone help. thanks
Click to expand...
Click to collapse
1.Do you have a recent nandroid backup? that would be a simple fix?
2. What rom and kernel are you using?
3. Is your phone rooted? Probably yes...All the apps go to /system/app, unless you have apps2sd installed
4. If it's not there and it's not in "manage applications" then probably it's a an error of your rom showing erroneous available space.
Hi,
Thanks for your reply.
1) I am using XT720, we don't have nandroid backup tools yet
2) Stock EU rom and kernel for XT720
3) yes, rooted. I am sure it's not in /system/app (mine has got apps2sd)
4) I guess I'll probably need to reflash the rom to get rid of it then. a bit troublesome but no choice I guess.
Something about the firefox is that if you install it you'll find that the space taken up by the firefox is much bigger than the .apk+dalvik cache+data in the normal app installation path. some portion gets installed into somewhere else which nobody knows where. My friend with a Nexus one try to move it to sd but it simply won't move the whole thing because part of it does not install to the /app.
Anyway, thanks for the help. I'll wait another day or two before I flash it to stock again.
Many thanks
en0203 said:
Hi,
Thanks for your reply.
1) I am using XT720, we don't have nandroid backup tools yet
2) Stock EU rom and kernel for XT720
3) yes, rooted. I am sure it's not in /system/app (mine has got apps2sd)
4) I guess I'll probably need to reflash the rom to get rid of it then. a bit troublesome but no choice I guess.
Something about the firefox is that if you install it you'll find that the space taken up by the firefox is much bigger than the .apk+dalvik cache+data in the normal app installation path. some portion gets installed into somewhere else which nobody knows where. My friend with a Nexus one try to move it to sd but it simply won't move the whole thing because part of it does not install to the /app.
Anyway, thanks for the help. I'll wait another day or two before I flash it to stock again.
Many thanks
Click to expand...
Click to collapse
Can you go into recovery? ADB commands actually work as root there.
You also said you have app2sd - I'm guessing the ext version. You can browse around the ext partition if you have something that can read it (like Ubuntu) and delete it from the card as well.
- Look into your /cache partition and delete every download*.apk
- Look into /data/app and look if there is still an apk left
- Look into /data/data and see if a Firefox-folder is located there - delete it!
You can do all this with RootExplorer
Then you should be fixed
Milestone isn't supported. I think I read it somewhere on the mozilla site. There's some known issue logged somewhere
Sent from my Milestone using XDA App
Check if there is any "*.tmp" files under /data/app ?
I was locked some memory due to unsuccessful install of "Pocket Legends", and found out that the apks were stored in both "/cache/downloadfile.apk" and "/data/app/vmxyzxyz.tmp".
ok, so maybe im slow or stupid & yes ive searched & searched, but no luck for me.
im trying to make some "flashable" update,.zip files to install to the system/app section of my htc cdma hero, & ive read & read, & researched, but im still at a loss.
so can anybody please in "noob/dummies" terms explain on how to do this, what files i need, b/c i see these "manifest.mf, cert.sf, & cert.rsa" files inside the update.zip files, & then theres the update-script file, & the apk.
how/where do i make/get these files, etc.
im ADHD & dyslectic, so please make it as simple as possible to follow.
also, how do i uninstall system apps & all the apps folders/cache files w/ adb, ive tryed but get "failed" error, i mean i can go in w/ root explorer & delete these, but it seems like a pain to track it all down, i just dont want to remove the app, but uninstall them completely, & not leave any junk behind.
thanks a million!
im trying to swap out some system apps (same apps), just different versions & size, & i tryed to just replace them w/ root explorer & reboot, but it doesnt work.
im on cm6.1 stable if that helps
jcj77d said:
ok, so maybe im slow or stupid & yes ive searched & searched, but no luck for me.
im trying to make some "flashable" update,.zip files to install to the system/app section of my htc cdma hero, & ive read & read, & researched, but im still at a loss.
so can anybody please in "noob/dummies" terms explain on how to do this, what files i need, b/c i see these "manifest.mf, cert.sf, & cert.rsa" files inside the update.zip files, & then theres the update-script file, & the apk.
how/where do i make/get these files, etc.
im ADHD & dyslectic, so please make it as simple as possible to follow.
also, how do i uninstall system apps & all the apps folders/cache files w/ adb, ive tryed but get "failed" error, i mean i can go in w/ root explorer & delete these, but it seems like a pain to track it all down, i just dont want to remove the app, but uninstall them completely, & not leave any junk behind.
thanks a million!
im trying to swap out some system apps (same apps), just different versions & size, & i tryed to just replace them w/ root explorer & reboot, but it doesnt work.
im on cm6.1 stable if that helps
Click to expand...
Click to collapse
Check out http://wiki.cyanogenmod.com/index.php?title=Barebones for a great guide on using adb to uninstall system apps.
As for update.zip info, I'm just starting to break into it myself. For a noob, I would suggest using the attached update.zip template (a read me is included ), and then you will need to sign the update. Two easy options:
1) Search the market for signapktic by Stericson.
2) Check out this amazing program: http://forum.ppcgeeks.com/android-development/126517-pc-ppcgeeks-android-apk-zip-signer.html
jcj77d said:
so can anybody please in "noob/dummies" terms explain on how to do this, what files i need, b/c i see these "manifest.mf, cert.sf, & cert.rsa" files inside the update.zip files, & then theres the update-script file, & the apk.
how/where do i make/get these files, etc.
Click to expand...
Click to collapse
Those three files are created when you sign the zip. If you just want the apks flashed to the system then you don't need to modify the script file in that template - as for the framework.jar/apk part of the instructions, you can ignore those because that part was added bc the zip was initially created for themers
If you're interested in doing more than flashing to /system, such as flashing to /data or /sdcard, or removing items with a flash zip then check out my old post HERE - as a forewarning some of the stuff can get pretty technical
Otherwise follow the above post and you should be set both signers he/she listed are pretty easy to use
kyouko said:
If you're interested in doing more than flashing to /system, such as flashing to /data or /sdcard, or removing items with a flash zip then check out my old post HERE - as a forewarning some of the stuff can get pretty technical
Click to expand...
Click to collapse
LOL, I wasn't sure exactly where I got that .zip template from (That was a looong night of Google'ing and reading ) And the blog that you linked to is where I learned a lot of what I was after. Thanks! Now, if I can just figure out a way to create an update-script that will flash MY memory with all there is to know about Linux...
The Fer-Shiz-Nizzle said:
Check out http://wiki.cyanogenmod.com/index.php?title=Barebones for a great guide on using adb to uninstall system apps.
As for update.zip info, I'm just starting to break into it myself. For a noob, I would suggest using the attached update.zip template (a read me is included ), and then you will need to sign the update. Two easy options:
1) Search the market for signapktic by Stericson.
2) Check out this amazing program: http://forum.ppcgeeks.com/android-development/126517-pc-ppcgeeks-android-apk-zip-signer.html
Click to expand...
Click to collapse
thanks, i know how to sign
I found on another post:
http://forum.xda-developers.com/showthread.php?t=1341514
that the User: Rick#2 suggested using paid programs to which I've found free alternatives. I'd have posted as a direct reply there, but as "noob", I'm unable.
Anyways:
First thing that I noticed was this comment: "Unzip the attachment from the first post to the root of your sdcard, ie: don't unzip it into any folders after browsing to your phone on your PC, just put them in the root of the drive." <==Suggesting that users unzip and then stating to not unzip becomes a contradiction. I think what you meant to say was more along the lines of "Unzip the files directly into your SDCard, as there's no need to do it on you PC".
It would also be wise to state that some "NooB" users might not realize that there's more than one version of an SDCard for this phone, the Droid 3, available to be putting the files into. Standard transfer methods go to the EXTERNAL SDCard, not the internal one, so this alone could cause some users to fail at being able to do this procedure. Since this is likely the case to happen, a suggestion to verify that it's in the /sdcard and not the /external/sdcard might be of note, and those users reading this attempting this mod with the "no file in this area" problem simply need to use a file manager like File Expert (free) to do move the files from the External SDCard to the SDCard.
Next up, the apps needed to do this:
You suggested SetCPU (not free)
I suggest AnTuTu CPU Master Free
You suggest Root Explorer (not free)
I suggest Mount /system (rw / ro) (free, does the same thing, with a lot more ease than Root Explorer's way)
You suggested Better Terminal Emulator (not free)
Don't know the how much benefit of this might be over the free Terminal Emulator you thankfully suggested might be, but I can't imagine it'd be worth paying for.
Otherwise, I'd like to thank you for your post. Very nice work, and happy to say that I personally got mine to work without error the first time via your instructions.
There's a new method to overclock on rootzwiki I would suggest using. It uses a kernel module rather than a binary. Although it's in a boinic forum it is availabe for many other devices including the droid 3. It's not that difficult to accomplish and can also be done with free apps. Antutu will show the correct frequency and the min frequency does not have to be maxed out.
do you have to unzip via pc?
Do you have to unzip to sd via pc or can you just dl to your phone and unzip to sd is there a diff?
jwood3535 said:
Do you have to unzip to sd via pc or can you just dl to your phone and unzip to sd is there a diff?
Click to expand...
Click to collapse
There's a few extra steps if you unzip on a pc, you have to push more, usually have to set permissions.
Honestly, if you wanted to tell this to Rick#2 you could have done it in a pm, there's no guarantee he'll even read this here...
Hi all,
And yet another noob question...
The problem of being this ignorant, is that it is also hard to ask a good question. So I'll have to tell the story in full...
I started to use custom ROMs only one month ago. I installed and configured CWM 6.0.4.5, and through ADB PUSH to /sdcard/ I put the files for CyanogenMod 11 "cm11.zip" and "cm11_gapps.zip" into my phone. I was able to install this ROM, so no issues there.
After some time of playing around, I felt that some bugs in the ROM were unacceptable to me. I also got errors that stated that my memory was full, although, when I looked into ES file explorer or even the standard 'Storage" tool in android, my phone appeared far from full (+5 Gb free!). To me, that was the drop to remove this ROM (althoug I already found out that it was not the ROM's fault...).
So I installed another ROM, CM10.1.3. Again, I ADB pushed the files "cm1013.zip" and "cm1013_gapps.zip" to /sdcard/ , rebooted into recovery. There I did the following:
- install zip
- choose zip from /sdcard
At this point, I thought I would find my files "cm1013.zip" and "cm1013_gapps.zip", but I didn't! Instead, I did find the previous files "cm11.zip" and "cm11_gapps.zip"!
However, I did see a folder "0/", so when going into that one, I did find my files... So I continued the installation of my ROM, no issues.
But now, when I use ES File Explorer, I can't find these "cm11.zip" and "cm11_gapps.zip" anywhere! It seems like once I'm in my ROM, I can't access a complete part of my memory.
This means I lost a big chunck of my internal memory!
What did I do wrong, and more important, how can I resolve??
I tried my best to search this forum, but all I came up with was this thread:
http://forum.xda-developers.com/showthread.php?t=2304138
Interesting, but not a solution to me, as I'm unable to even find the files in the first place.
All help much appreciated, and sorry for the (too) long explanation.
By the way, when installing my second ROM "CM10.1.3", I used every "wipe" option in the recovery mode I could find:
wipe data/factory reset
wipe cache partition
wipe dalvik
I thought that was the cleanest I could get...
When wandering through ES file Explorer, I always end up at the same location for sdcard... There are so many ways to get to my memory. I understand the principle of symlinks, but I don't understand the meaning of "emulated".
All of these paths, end up on the same location:
/mnt/sdcard
/sdcard
/storage/sdcard0
/storage/emulated/0
/storage/emulated/legacy
What is the "emulated" locations for?? But the files I'm looking for "cm11.zip", can't find it anywhere (see post above)...
after looking for some more, I finally found the files I was looking for. They were stored under /data/media/
So, when booting into recovery mode with CWM, and choosing "Install zip", this is the folder you look into.
I'm still puzzled by the fact that while doing ADB push to send files it ended up under 2 different locations while running another ROM...
I recently unlocked my bootloader using sunshine and installed TWRP. After rebooting into recovery, I immediately made a backup of my phone. When I plug my phone in, I can see the TWRP folder, but it shows as empty. None of my file explorers can see anything, either. TWRP, however, is able to see it when I go into the file manager. I can't get ADB to see the device when hooked up to my computer while in TWRP. MTP also doesn't work. Chmod 755 and 777 doesn't do anything. I was able to initially copy the TWRP folder into the downloads folder in the TWRP file manager, but now it just hangs there if I try to move it again.
How do I get access to my backup?
evanft said:
I recently unlocked my bootloader using sunshine and installed TWRP. After rebooting into recovery, I immediately made a backup of my phone. When I plug my phone in, I can see the TWRP folder, but it shows as empty. None of my file explorers can see anything, either. TWRP, however, is able to see it when I go into the file manager. I can't get ADB to see the device when hooked up to my computer while in TWRP. MTP also doesn't work.
How do I get access to my backup?
Click to expand...
Click to collapse
http://forum.xda-developers.com/droid-turbo/help/twrp-backup-file-location-t3259060
6Binford said:
http://forum.xda-developers.com/droid-turbo/help/twrp-backup-file-location-t3259060
Click to expand...
Click to collapse
Unfortunately, there aren't any solutions in that thread.
evanft said:
Unfortunately, there aren't any solutions in that thread.
Click to expand...
Click to collapse
There are two solutions in the first 4 posts:
ruledrbrt1 suggests http://forum.xda-developers.com/showpost.php?p=64048593&postcount=2
And GeoFX has the great : http://forum.xda-developers.com/showpost.php?p=64049328&postcount=5
Both work on my phone so they should work on yours too.
Have you given file explorer root privileges?
josephpalozzi said:
There are two solutions in the first 4 posts:
ruledrbrt1 suggests http://forum.xda-developers.com/showpost.php?p=64048593&postcount=2
And GeoFX has the great : http://forum.xda-developers.com/showpost.php?p=64049328&postcount=5
Both work on my phone so they should work on yours too.
Have you given file explorer root privileges?
Click to expand...
Click to collapse
I didn't even see GeoFX's post for some reason. That looks like it worked. Thanks!
TWRP and NAND Backups
I had the same question, and found the previous thread too. So what's the difference between these 2 locations?
/data/media/0/TWRP
and
/sdcard/TWRP
From my point of view, they are duplicates - same data in both folders, just duplicated into separate partitions. If this is true, then my 7.5 GB NAND backup, is really taking up 15GB of memory. Can that be true? I'm doubting it, but you never know.
I started to dive into this, because I was also wondering if NAND backups made copies of my media or not (photos, music, etc). After digging into it a bit, it looks like it does NOT make a backup of anything in the root folder "/data/media" in order to prevent it from non-stop backing up in a loop (you can't back up the location your backing up to, at the same time). This is also noted on github: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/276 Logically, this would make sense since I currently have 25 GB of data in my /sdcard/ location. That's one helluva compression if you were able to get this down to 7.5GB! So I'm guessing this isn't included, which is also why I'm guessing that these are really the same. /sdcard/ must be a shortcut to the /data/media/0/ location, that's my best understanding.
So my original question still stands. What's the reason for these 2 locations, and is there a difference?
This also brings up the next question, what's the best way to make an all-encompassing backup? NAND + Titanium Backup + copy all the contents of your /sdcard/ over to your computer (or OTG drive)?
Florestan2 said:
I had the same question, and found the previous thread too. So what's the difference between these 2 locations?
/data/media/0/TWRP
and
/sdcard/TWRP
From my point of view, they are duplicates - same data in both folders, just duplicated into separate partitions. If this is true, then my 7.5 GB NAND backup, is really taking up 15GB of memory. Can that be true? I'm doubting it, but you never know.
I started to dive into this, because I was also wondering if NAND backups made copies of my media or not (photos, music, etc). After digging into it a bit, it looks like it does NOT make a backup of anything in the root folder "/data/media" in order to prevent it from non-stop backing up in a loop (you can't back up the location your backing up to, at the same time). This is also noted on github: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/276 Logically, this would make sense since I currently have 25 GB of data in my /sdcard/ location. That's one helluva compression if you were able to get this down to 7.5GB! So I'm guessing this isn't included, which is also why I'm guessing that these are really the same. /sdcard/ must be a shortcut to the /data/media/0/ location, that's my best understanding.
So my original question still stands. What's the reason for these 2 locations, and is there a difference?
This also brings up the next question, what's the best way to make an all-encompassing backup? NAND + Titanium Backup + copy all the contents of your /sdcard/ over to your computer (or OTG drive)?
Click to expand...
Click to collapse
The way I understand it, and I might be wrong, is that before Android 4.0 (or maybe 5.0), the partition containing user data was called /sdcard and apps were stored in a separate partition. The partition where apps went was significantly smaller, which could result in people running out of space for apps while still having a ton of free user data. To remedy this, the newer version of android places apps and user data in the same partition (called media). The /sdcard that you see is a symlink (shortcut) to this new partition, and is included so that older apps that were designed to expect the /sdcard partition to be there will still work.