com.android.process.media (Android Media Process is (ab)using CPU)
so, I've tried:
Settings -> Apps -> ALL -> Media Storage -> “Force stop” & “Clear data”
That didn't really help at all(((
community's users suggests following:
* its due to corrupted music/pictures (I don't have any music/pictures on my phone).
* suggestion to reformat sdcard, but toro doesn't have SD card, although through recovery I was able to check filesystem of /userdata mount point (see below):
~ # e2fsck -n /dev/block/platform/omap/omap_hsmmc.0/by-name/userdata
e2fsck 1.41.11 (14-Mar-2010)
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata: clean, 53630/1875968 files, 1921615/7493115 blocks
~ #
Click to expand...
Click to collapse
aside the fact that phone works extremely slow upon boot (due to com.android.process.media) all that high CPU eating a lot of battery (battery life isn't that great to begin with) but thanks to this bug I get to use even less.
after deleting nanodroid's backup (ROM manager), I'm seeing following (through logcat):
D/MediaProvider( 6784): object removed 71054
D/MediaProvider( 6784): object removed 71055
D/MediaProvider( 6784): object removed 71056
D/MediaProvider( 6784): object removed 71057
D/MediaProvider( 6784): object removed 71058
Click to expand...
Click to collapse
i read that if you have folders with a lot of media/picture files, it will sometimes hang while scanning. start fresh, factory reset/reflash google factory images.
bk201doesntexist said:
i read that if you have folders with a lot of media/picture files, it will sometimes hang while scanning. start fresh, factory reset/reflash google factory images.
Click to expand...
Click to collapse
i dont want to loose my /data so doing factory reset won't work for me
I had an issue with this at the beginning of the week.
I had read that it was corrupted media files, so I began investigating. I was able to fix the problem by browsing through my pictures and deleting some images that had somehow become corrupted. The corrupted files were just washed out black squares. No SD format / factory reset was needed.
t3h_g3n3r4l said:
I had an issue with this at the beginning of the week.
I had read that it was corrupted media files, so I began investigating. I was able to fix the problem by browsing through my pictures and deleting some images that had somehow become corrupted. The corrupted files were just washed out black squares. No SD format / factory reset was needed.
Click to expand...
Click to collapse
i thought that would be a problem) i found one and i delete, restarted my phone and still android media process is at least 20% cpu(
I had about half a dozen across several folders that were corrupt. I was looking at the android media process consuming my battery in about 3 or 4 hours until I deleted the bad images. I can now make it through most of a day without any problems.
Somewhere in your phone, a corrupted file lurks. It may not be where you're thinking, but it's there. And it's hungry.
t3h_g3n3r4l said:
I had about half a dozen across several folders that were corrupt. I was looking at the android media process consuming my battery in about 3 or 4 hours until I deleted the bad images. I can now make it through most of a day without any problems.
Somewhere in your phone, a corrupted file lurks. It may not be where you're thinking, but it's there. And it's hungry.
Click to expand...
Click to collapse
i went through all of my gallery and deleted those, yet after restart still doing something and by the time it's done something whatever it was doing i have 90%-70% left!!! AAAAA
is there a way to find those files some other way? can i see some debug information of gallery/android media process and see where hiccup is?
it really kills my battery( anyone has any ideas?
So yesterday I've had it and copy ask of my pictures from my phone to computer and delete them from my phone...
Reboot... and guess what?
It's still using 40/50% of cpu for about first 15 min after I reboot my phone which kills my battery big time(
I need help, anyone??
Sent from my Galaxy Nexus using Tapatalk 2
is there a way to turn on some detailed debug to figure out what's causing this exactly?!
a1exus said:
com.android.process.media (Android Media Process is (ab)using CPU)
so, I've tried:
Settings -> Apps -> ALL -> Media Storage -> “Force stop” & “Clear data”
That didn't really help(( Any other ideas? I keep reading that users saying its due to corrupted music (I don't have any music on my phone).
People are also suggesting to reformat sdcard, but we don't have SD card. Please advise, as one thing it uses CPU the other thing it uses battery and battery life isn't that great to begin with. Is there a way to do fsck or something to make sure there is no corruption of any kind?
*** UPDATE ***
I went into recovery and using adb shell got into a system can I do something like this?
Click to expand...
Click to collapse
I am having the same issue. I found this article but it says the same as the others here.
http://www.transformerforums.com/fo...help/24279-solved-media-using-94-battery.html
If I find anything else out or if you figure something out, let me know also.
a1exus said:
i dont want to loose my /data so doing factory reset won't work for me
Click to expand...
Click to collapse
Your pics and stuff are not in the /data folder. You won't really lose anything important. That is the directory a factory reset/data does. It just basically gets rid of the apps that you had installed. If you are already rooted just get titanium backup to restore. I assure you, I had the same problem up until yesterday. The factory reset was the only thing that fixed it.
The /data wipe is not going to get rid of your pics taken with the phone.
If you do a backup first you have nothing to lose by trying.
On a side note, your Galaxy Nexus does have an "sd card" it's just an internal partition.
Hope you get this resolved.
rushter said:
Your pics and stuff are not in the /data folder. You won't really lose anything important. That is the directory a factory reset/data does. It just basically gets rid of the apps that you had installed. If you are already rooted just get titanium backup to restore. I assure you, I had the same problem up until yesterday. The factory reset was the only thing that fixed it.
The /data wipe is not going to get rid of your pics taken with the phone.
If you do a backup first you have nothing to lose by trying.
On a side note, your Galaxy Nexus does have an "sd card" it's just an internal partition.
Hope you get this resolved.
Click to expand...
Click to collapse
I deleted manually all of my pictures/music yet I still having this issue((
I do have Titanium Backup and I backup my phone regularly, I may try do that...
Do the wipe, trust me. A few installs of programs is not an issue. Your personal data is not lost. Just reinstall your shops that you need and if the days is missing restore with titanium backup.
You will keep having these issues until you do.
Sent from my Nexus 7 using Tapatalk 2
Im having the exact same problem.. Media is 50% CPU, and my S3 gets hot until I stop the Media process after each reboot.
I would like to find a fix before going threw a wipe.
rushter said:
Do the wipe, trust me. A few installs of programs is not an issue. Your personal data is not lost. Just reinstall your shops that you need and if the days is missing restore with titanium backup.
You will keep having these issues until you do.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I was having the same problem and the phone was burning a hole in my pocket.
I found that the problem only seemed to occur on a reboot with android.process.media consuming 96% of the CPU for approximately 40minutes.
I attempted to add a .nomedia file to every single directory on the root of my internal SDCARD. - This made no difference.
I discovered that if I killed the process via the terminal it was eventually restarted by zygote and the same issue occured.
I found the only way to stop this from occuring was to Freeze the "Media Storage" app using Titanium Backup. But (not surprisingly) other things did not work - eg being able to capture a screenshot.
I also discovered that if I went into Titanium Backup and issued a "Clear Cached Data" for the Media Storage app, this resulted in the process ceasing it's CPU consumption - useful - but hardly a silver bullet and an annoying step to take after every reboot. (Additionally I do not know if the scan process might of kicked off automatically at some later stage anyway).
Interestingly I discovered that the phone did not overheat when it was plugged into a power supply - completely unrelated but none the less I found this interesting cause I always thought it was the CPU causing the overheating - when in actual fact it was the battery being emptied - unrelated to the issue at hand but none the less a nice tangent
Now this is what I discovered:
I have an application called NZ Topo Maps, it creates a absolutely massive directory structure to download all the tiles of NZ and cache them locally. Each directory can have many sub directories which in turns has many more and can have many many files in each.
So I deleted the entire tilecache. The result - after a reboot android.process.media consumed 5seconds of CPU.
Not convinced I browsed some maps and "cached" ~64MB of tiles - rebooted - 2:33mins of CPU time consumed... hmmmm.
So I cached ~128mb of tiles - 7:44mins of CPU time consumed after a reboot - diffidently onto something here....
Of interest - every single directory which the NZ Topo Maps program creates has a ".nomedia" included and all of the files are labelled with a *.jpg_ suffix.
So I decided to do some more research - Under the structure I had 425 sub-directories and 10615 files that ended with the suffix .jpg_
Out of curiosity I deleted all the files (including the .nomedia) and left the directory structure completely intact.
After a reboot the media process consumed 32sec of CPU time.
For the final test I deleted the directory structure:
CPU consumed: SIX seconds!!!!
Solved: Why android.process.media is consuming so much battery.... for me atleast.
So in conclusion it seems that:
1) The .nomedia directive applies only to the current directory - android.process.media will still recurse into sub directories
2) The .nomedia does not make any difference to the time it takes media to process the contents of a directory - eg - it was still doing "something" with the files in the directory.
3) The naming of files .jpg_ does not make any difference either, the process will still look at them - not sure if it is supposed to or not.
Where to from here - I would really like to find the source for this process and have a look at it's logic, but right now I just don't understand the android internals enough to be able to determine where the source is located in the source tree! I have posted another thread about this - http://forum.xda-developers.com/showthread.php?p=34326153#post34326153 hopefully someone will give me an answer because this situation is less than ideal.
Hopefully this helps someone else and sends them in the right direction?
Rowan
All,
I found this link. I would post a click-able link but I am not allowed as I am a new forum member - so I am afraid you'll have to type it in the old fashioned way from the image below.
Please head over and "STAR" the bug and/or add your own comments / experience, the more visibility it gets the more likely it is to be fixed.
Cheers.
-Rowan
I have a new HTC One X+ running JB 4.1.1 Sense+. I noticed this happens off and on that the phone gets hot and battery plummets. Using Android Task Manager, realtime process viewer and showing system processes setting turned on, I discovered also it is android.process.media consuming the CPU.
I have over 2,800 mp3 files, most are highquality high bitrate, 16GB worth. They are all put into a directory structure based on artist and album name. I'm sure this is what the process is choking on.
The question is, is it some sort of indexing that just takes days or is it going to happen every time I reboot the phone? The USB charge can't even keep up with the batter drain when it is doing this.
every reboot, so don't reboot your phone)
jazee said:
The question is, is it some sort of indexing that just takes days or is it going to happen every time I reboot the phone? The USB charge can't even keep up with the batter drain when it is doing this.
Click to expand...
Click to collapse
It happens every reboot. The following workarounds are available:
a) not reboot
b) reboot only when you are connected to power
c) use TitaniumBackup to Freeze "Media Storage" (requires root)
d) Settings -> Apps -> ALL -> Media Storage -> “Clear data”. NB: A Force Stop will result in the process being restarted by Zygote at a later time.
e) delete the large directory structure and directories with 1000's of files.
(c) works indefinitely but things stop working - eg - screenshot fails
(d) seems to work until the next reboot but all of your media is gone from the native library - but this may not effect third-party players/apps
If you're using too much power when charging via USB, you might want to get a plug in wall adapter which can supply more current.
It's a really bad situation and seems to be effecting every build of JellyBean - it's a defect in the core software.
Things which do not work:
.nomedia - placing .nomedia files in all directories, some of the directories or the root directories has no noticeable effect.
renaming files - renaming media to an unknown extension (e.g., picture.jpg -> picture.abc) has no effect
-Rowan
I personally went through:
deleting broken images inside of my gallery
deleting my music
deleting my pictures
checking filesystem on my /sdcard partition
deleting some large directories that contains a lot of files
placing .nomedia inside of some directories
bloging about this: Android Media Process (high CPU) | alexus' blog
about to commit suiside #$%#&@!)
and almost every time when i (re)boot my phone and i'm not plugged in, i'll lose about 10% of battery in first 10min of my phone is doing something...
Google! fix it already!))
Related
What I need...
Someone to repackage a boot.img for me. Specifically, I need a boot.img unpacked, replace the file "/init.inc.rc" with my version, and repack it. (I'm stuck on all Windows, and cygwin is not an option.)
Purpose/Goal
Fix the annoying fact that /emmc is not accessible to almost all market apps, without resorting to using the modified media scanner from CyanogenMod or anything else drastic.
Do not change fstab. /mnt/emmc and /mnt/sdcard will not change.
NOTE: I am not trying to create a symlink on the FAT32 of the SD card.
My idea
Modify /init.inc.rc to change the EMMC settings. (Changes made, need someone with tools. See above.)
Modify /system/etc/vold.fstab to relocate EMMC mount point.
Directory structure
/sdcard (unchanged)
/sdcard/emmc (new location of emmc)
/emmc (Retarget the symbolic link to new location.)
/mnt/emmc (Change to symlink for compatibility, just in case.)
What I want to know...
This arrangement makes /emmc redundant. Can it be safely removed?
When you connect to a PC, how/what does Android map to USB drives? (I assume it is the mount blocks, not the symlinks.)
What odd behaviors may occur? (e.g. will "Settings->SD & phone storage" freak out?)
Maybe, just maybe: How to bottle this into a flashable .zip? (I'll worry about that later.)
If anyone has any pull with the ROM devs (i.e. Koush, rmk40, et al.), I really want to hear from them.
+1. I'd love to make emmc usable in Winamp
Bzzzt... Sorry.
ARGH!
The internal storage is VFAT also. No symlinks allowed.
Blast you, HTC!
What??
I hate doing this, but editing the original post doesn't bump the thread.
I did not want to create a new thread, but what I need has completely changed.
So. BUMP.
Why HTC, WHY?!
Would there be a way to format emmc to NOT be VFAT?
Progress!!!!
I'm close to getting a boot.img ready to test out on my phone.
I spent yesterday hacking away. I've made a Windows tool for handling boot images. I'm about 80% done with the required features. I have all the unpacking finished. I've repacked the ramdisk. I can generate the SHA hash to sign the image. It's just a matter to gluing the last stages together.
ppd0526 said:
Why HTC, WHY?!
Would there be a way to format emmc to NOT be VFAT?
Click to expand...
Click to collapse
I'm sure it could be done, but this is way more work/hassle that I want to deal with. Major obstacle here is that ALL data on emmc is wiped, and I'm not willing to that.
Assuming there are no hidden "features," my approach should be invisible to the Android layer (i.e. will not break any HTC software). HOWEVER... I'm pretty much Senseless, so I'm not too concerned (for my own use) about HTC's apps.
My biggest concern is that the media scanner will generate duplicates of all files found on emmc. But a/the big motivator for this work is to use Winamp, so I don't really give a whoop.
This was tried by koush when we couldn't get cm6 to scan emmc. It didn't work.
Sent from my ADR6300 using XDA App
distINCtINC said:
This was tried by koush when we couldn't get cm6 to scan emmc. It didn't work.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
What didn't work? Or how did it not work?
I'm not sure. I wasn't involved in the effort. Koush would be the person to talk to but island how to get a hold of him. I just think the OS rejected mounting a physical drive within a physical drive. But don't let that discourage you. It might be still be possible.
Sent from my ADR6300 using XDA App
Any progress on this? I really would love to have /emmc accessible as /sdcard.
Why HTC decided to make /data/data so small and put the rest of the space as /emmc is still a mystery to me. This is my only gripe with this phone.
Progress update
I made my first attempt on Friday, which resulted in a boot loop. So, obviously, I'm missing something important. (Battery pull and recover boot fixed the problem.)
I couldn't work on it this weekend. But I'm going to start digging into it some today.
More info:
It didn't get past the slash screen. Since I'm flashing a boot image, this is obviously where the problem is located. I just don't have any error logging to read over. Since I'm cooking on Windows, I'm wondering if my file permissions and ownership are messed up.
Also, while running my update, I observed that the boot image flashing did not seem to take long at all. So, I'm concerned that I didn't even get a complete flash.
weareallkosh said:
I made my first attempt on Friday, which resulted in a boot loop. So, obviously, I'm missing something important. (Battery pull and recover boot fixed the problem.)
I couldn't work on it this weekend. But I'm going to start digging into it some today.
More info:
It didn't get past the slash screen. Since I'm flashing a boot image, this is obviously where the problem is located. I just don't have any error logging to read over. Since I'm cooking on Windows, I'm wondering if my file permissions and ownership are messed up.
Also, while running my update, I observed that the boot image flashing did not seem to take long at all. So, I'm concerned that I didn't even get a complete flash.
Click to expand...
Click to collapse
That doesn't bode well so far.
just some info
i'm not sure if this will help any of you, but i read before that it said koush tried to get the emmc mounting.. etc... and it didn't work. but - i'm running cm 6.1 stable and winamp can and does read my music found on the internal memory. so it seems to work for me. however - i cannot take picture and have them stored on the internal memory. anyway, good luck.
OK.... I got the ramdisk sorted out. The boot loop is gone. But it doesn't progress past the splash1. sigh.
I need to see the kernel messages, and typically ADB is not available.
drwndphish said:
just some info
i'm not sure if this will help any of you, but i read before that it said koush tried to get the emmc mounting.. etc... and it didn't work. but - i'm running cm 6.1 stable and winamp can and does read my music found on the internal memory. so it seems to work for me. however - i cannot take picture and have them stored on the internal memory. anyway, good luck.
Click to expand...
Click to collapse
CM6 uses a modified media scanner (Android layer) that uses '/mnt' as its base directory, instead of '/mnt/sdcard.' And, as you say, it has its own problems.
I am trying to modify the underlying file system to make hopefully all software work (e.g. HTC stock, Winamp and other media players, 90% of the apps I've played with).
It "works!"
Alright... I have all the tools made, and bugs squashed. So, I can correctly mod a boot image. (Tip: The boot process has a zero warning or error tolerance.)
It fully booted. BUT... A permanent notification "Preparing phone storage.../Checking for errors." did not go away. All emmc directories were absent.
So, I've found a problem. Google didn't return any useful information... Especially annoying is the face that I don't even get a link to the Android source to even get a hint where this notification comes from.
AHA! Fixed that problem. Now, emmc is visible on the sdcard.
NEXT problem (this one I expected):
Media scanner picked up 2 copies of my pictures (I have them on emmc). So, my thought is to start removing links (and references) to emmc in its new location until things clear up.
weareallkosh said:
Alright... I have all the tools made, and bugs squashed. So, I can correctly mod a boot image. (Tip: The boot process has a zero warning or error tolerance.)
It fully booted. BUT... A permanent notification "Preparing phone storage.../Checking for errors." did not go away. All emmc directories were absent.
So, I've found a problem. Google didn't return any useful information... Especially annoying is the face that I don't even get a link to the Android source to even get a hint where this notification comes from.
AHA! Fixed that problem. Now, emmc is visible on the sdcard.
NEXT problem (this one I expected):
Media scanner picked up 2 copies of my pictures (I have them on emmc). So, my thought is to start removing links (and references) to emmc in its new location until things clear up.
Click to expand...
Click to collapse
The double items in media scanner seems like a small issue compared to what it fixes.
More problems created than fixed. (And WHY this is a mess to begin with.)
Postmortem thus far...
Touching ANY code related to where emmc appears will cause Setting to FC if you view the SD & phone storage usage.
Makes media visible to "other" applications, but shows duplicates in HTC's music and gallery apps.
I didn't look too closely at it, but I question that the camera was playing nice with the new config.
ppd0526 said:
The double items in media scanner seems like a small issue compared to what it fixes.
Click to expand...
Click to collapse
SO... I took some time to understand the double items, and why EMMC is such a problem to begin with.
HTC did not modify the media scanner/provider to support EMMC. They modified their APPS. Do a dump of HTC's music and gallery apps. You'll find a LOT of extra code, and a lot of added symbols/strings for handling the phone storage.
In other words, they didn't create a "public" solution. They just made their own private patch, and brushed it under the rug. (How dare we not use THEIR apps???)
Media Scanner/Provider:
I looked at Koush's code changes. I don't understand his changes. I'm not sure how/why it "works." I don't know why it reportedly breaks the HTC apps. I am also not sure that their is a way to mod it to actually fix the issue... Google's code was not written to be extensible. But, I think it may be the way to go in the long run.
What other phones have EMMC? Do they have a fix?
My tools...
There is a lot of code duplication, no GUI, or options. It ain't exactly pretty, but it works.
I'm posting this here for future reference by others wishing to work with boot.img.
Note: This specifically targets 1 file on the ramdisk (init.inc.rc), but with some changes this could do almost anything you would want.
License... Oh. GPL. If you make changes, please send me a patch.
REQUIRES: AutoHotkey (Hey.... it's all I had available, but the code should be easy for anyone to follow and port to another language.)
Runs on Windows (XP). Does not require cygwin. Native GZIP included.
Good afternoon, dear xda-developers forum members.
I really hope to find some help here.
In last two months I had the following issues:
1. This one happened two times already: after using my phone as a flash in windows 7 and "safely removal" of it, all my applications which were installed on SD card were saying that "Application is no longer installed" when I tried to run it, although other documents and files were readable from ASTRO File Manager, i.e. SD card was mounted. In Settings->Applications all these applications had black icons with SD card image on it and rather with package name than regular application name(for example com.navitel instead of regular Navitel, etc.). I've restored all these applications from Titanium Backup, but I'm afraid that there is something more disappeared also which I don't know about.
2. My "Android" folder on sd card became a file with weird contents(this folder was used for NFS Shift data only). I couldn't restore it. Again: if this folder corrupted, then there is definitely something else also corrupted.
After I saw these things for the first time, I used Windows checkdisk with auto-fix errors. It found a lot of files and put it into "FOUND.000" directory. I recognized in these files few apk-files of installed applications from SD and also few images from my SD. Then I restored applications to SD card and for some time it seemed ok. But one time it happened again.
My assumption is that Android fails to re-mount SD card after I disconnect it from PC.
I don't know what to do... is it Android bug or is it Desire bug or what? I swear that I ALWAYS make "safe USB removal" in Windows before disconnect the USB-cable and I ALWAYS wait for the message "It's now safe to disconnect your device".
I'm very disappointed with all that Please, advise me something useful...
P.S.: If needed I can give you any debug information you want, I'm a programmer, so I've been around
You could try to format your SD card, just backup the contents first, see if that works. As for Android, it does a pretty good job of mounting straight after. What version of Android are you running?
GoogleJelly said:
You could try to format your SD card, just backup the contents first, see if that works. As for Android, it does a pretty good job of mounting straight after.
Click to expand...
Click to collapse
I will, but strange that it happened, because I formatted the flash before using it for the first time...
I have two assumptions:
Maybe I shouldn't press power button to switch the screen off just after disconnecting USB cable from PC. I was doing that as a habit, because every time you disconnect your phone from PC, the screen turns on.
Maybe I shouldn't try to run application which is installed on SD just after disconnecting phone from PC. Maybe I should have waited for a minute. I've tried to do it once, because I wanted to see the result as soon as possible, so the phone said that "Application is no longer installed", I though that Android haven't mount SD yet and tried later. It worked. But next time when I used USB cable, all SD-card apps became uninstalled.
GoogleJelly said:
What version of Android are you running?
Click to expand...
Click to collapse
I'm sorry, forgot to mention. I'm using HTC Desire with Android 2.2(2.10.405.2).
Fast Boot option may be the culprit
In case anyone checks this old thread...
CUT TO THE SOLUTION BELOW -- SEARCH FOR ////
Some (not all) of my apps moved to SD (all by Titanium Backup Pro) have begun to disappear and (sometimes) reappear without warning after I began to add and delete large Virtual Machines created in QEMU from my 16GB SanDisc class 10 microSD card on my HTC Droid Incredible running rooted stock Verizon Android Froyo 2.2.3. I know this thread is far from my phone's "home base", but from what I can tell this problem with disappearing apps located on an sdcard is NOT determined by hardware or even Android version.
I also happen to use LauncherPro by Federico Carnales instead of the built-in HTC Sense launcher. I noted elsewhere on XDA that a user had suggested that because at least some (maybe all) launchers start before the SD Card that this may be a problem, especially if changes are made to the sdcard that the launcher did not perform, or was not active during their performance by other apps such as Titanium Backup. That fits my situation, because I unmounted the SD, physically removed it to a PC, and added/deleted large VM files to save (lots) of time. No problems of this sort before I did this, so there must be some connection.
I noted that other users have tried reformatting SD, substituting different brands of SD, using newer/older SD etc. None of these reliably helped. So I skipped these options.
//// The (simple!) solution I tried that SEEMS to work (only time will tell!) is buried in the main Android Settings (accessed from the Menu button while in Home screen). Under "Applications" there is a setting "Fast Boot" that I checked long ago and forgot about (it seemed like a good thing to do at the time). The text warns "Turn off to use some Market apps" (that shows the age of my 2-yr old used phone and Android OS -- ohmygosh!-- because it refers to Market rather than Google Play Store!) Anyway, I unchecked the option and rebooted the phone.
Yes, it took a bit longer to boot (maybe a whole minute!), but after waiting about another minute ALL my home screen apps had normal icons and loaded properly. Titanium Backup Pro batch scenarios confirmed there were no apps in a forced uninstalled state (i.e. I had not done the deed, the system somehow had done it or at least rendered the apps "invisible" to Titanium, which decided they needed reinstallation).
The only odd behaviour was that auto brightness was turned off after I unchecked Fast Boot and rebooted. Going into Android Settings > Display and rechecking "auto brightness" took care of that. No other oddities or strange behaviours thus far (but it has only been about an hour).
I will report back here on this thread only (Samsung Fascinate > Fascinate Q&A > What just happend? apps on sdcard) if anything else requires reporting. Silence implies success!
link: http://forum.xda-developers.com/showthread.php?t=1873670
(I am copying this post to other relevant threads, but will not post anything further elsewhere -- only there. This is a bit arbitrary (although this thread appears to be the most recent active one on this topic), but I hope this approach pleases the XDA sysops/admins) :angel:
I have E4GT with Caulkins 2.9.1.
I have the following storage available on my device:
SD Card 24.25GB
USB Storage 3.25 GB
Device Memory 1.23 GB
I get the following error when trying to update apps, or install new apps:
"There is insufficient space on this device"
I have gone into settings>apps>google play> clear cache. -> no change
I have downloaded App Cache Cleaner app and cleared all cached files. -> no change
The error message is a lie written by a lazy programmer. What's actually happening is that the installation is trying to copy or move a file and can't. To circumvent this problem I have to enter root explorer and look for files related to the program I'm trying to upgrade and delete them. Sometimes I just find dangling files which aren't really needed; other times I have to delete the whole shebang and reinstall the program from scratch. One process that I've noticed can sometimes cause this problem is the auto-Odex routine that is available in the Development folder.
Bottom line though is that this problem has NOTHING to do with your available memory space.
Henri Blanche said:
The error message is a lie written by a lazy programmer. What's actually happening is that the installation is trying to copy or move a file and can't. To circumvent this problem I have to enter root explorer and look for files related to the program I'm trying to upgrade and delete them. Sometimes I just find dangling files which aren't really needed; other times I have to delete the whole shebang and reinstall the program from scratch. One process that I've noticed can sometimes cause this problem is the auto-Odex routine that is available in the Development folder.
Bottom line though is that this problem has NOTHING to do with your available memory space.
Click to expand...
Click to collapse
How do I find dangling files in explorer. Is there a was for me to determine which ones are wasted files?
before i read your reply i went into recovery and wiped cached and dalvik cache, thought it worked, because i was finally able to install or update about 3 apps, but then got the same error on the 4th app.
so those steps that have been suggested by others on different devices but with similar errors, did not resolve this issue on E4GT.
thanks for any additional help.
This may help http://bit.ly/GNQOZh take a read. I fought this a while ago and went nuts till I did what I describe.
It's usually, but not always, as simple as looking for files with the name of the program imbedded. The most recent program for me was AudioGalaxy.... so I just searched for and deleted any reference to the program that didn't look essential.
If you're REALLY stumped, then download a program from the Market like Log Viewer, which shows you the real-time system log of your Android operating system. That's how I discovered that a failed file copy was being misinterpreted as a full disc in the first place. It also will show you the name of the file being copied or moved and into which directory. Helpful hint: cut and paste the log into something like Notepad for easier reading.
By all means empty out your caches... but only to remove a potential file that's causing you a problem. Like I said, you haven't run out of free space.
Good luck!
A common source for this error is also that there are partitions on your phone that are not visible in the system settings, but which can fill up too.
If you open a console on your device, i.e. with terminal emulator, and type "df" you should see every partition and how much space is free on it.
leaderbuilder said:
This may help take a read. I fought this a while ago and went nuts till I did what I describe.
Click to expand...
Click to collapse
I did this earlier, and then downloaded App Cache Cleaner app and cleared all cached files which did not result in a solution...
im working on other suggestions from this thread
CandyIsYum said:
I did this earlier, and then downloaded App Cache Cleaner app and cleared all cached files which did not result in a solution...
im working on other suggestions from this thread
Click to expand...
Click to collapse
App Cache Cleaner isn't really that thorough.
Try SD Maid.
CandyIsYum said:
I did this earlier, and then downloaded App Cache Cleaner app and cleared all cached files which did not result in a solution...
im working on other suggestions from this thread
Click to expand...
Click to collapse
You 'cleared data' on the media and still had this issue? http://mikemartinezonline.com/blog/wp-content/uploads/2012/02/03.png I've had this issue a few times with a few people- again it just happed to me yesterday! Seems that the media storage, media hub, oovoodo, and some others were taking up huge amounst of space. In fact my media storage was at 800MB until I cleared it. Especially noticed this for me after adding and removing media and swapping different sd cards.
leaderbuilder said:
You 'cleared data' on the media and still had this issue? ] I've had this issue a few times with a few people- again it just happed to me yesterday! Seems that the media storage, media hub, oovoodo, and some others were taking up huge amounst of space. In fact my media storage was at 800MB until I cleared it. Especially noticed this for me after adding and removing media and swapping different sd cards.
Click to expand...
Click to collapse
I cleared the app cache there, and still had the issue. I also went into recovery and cleared cache, dalvik cache.
I didn't try the SDMaid method, so if someone else has this same problem, that may be a place to try.
I ended up starting with scratch with my device, and just upgraded to calkulin 2.9.2.
now my device is functioning as expected, and i can finally install angry birds space...
Well same problem shows up again.
updated to Calkulin 3.0, in hopes to resolve the problem, but still no go.
insufficient space when trying to install or update app from google play.
SD Card: 3.25GB Free / 29.7 GB
USB Storage: 7.29 Free / 11.50 GB
Device: 1.29 GB Free.
It's kind of annoying, is this something that would be resolved by going back to stock. This is getting a bit annoying.
thanks again.
Which app?
Edit: Have you tried clearing data for google play in settings/applications/all yet?
Sent from my SPH-D710 using XDA
So...
I've had this problem for a while now, getting worse from day to day. I've asked about this before, but it wasnt solved.
Basically my phone is taking up data in the background. Probably updating, downloading something. Its so bad, that if i dont turn off data on the go, my 1.5GB are used in a day. Sync is turned off at all times
And another side effect of that is, that all that data probably has to be stored somewhere. So Im getting the storage space running out error. Kinda annoying cause I cant use gmail, Cant install any apps(insufficient storage available) etc.
I really have no idea where all that data is(after searching through all the folders for a while now)..
I'm on the latest AOKP Milestone(4.2)
Thanks!
There are a couple things I recommend doing in your position. First thing I would do would be to get an app that allows for more informative breakdown of what is using the storage. Something like diskusage should do the trick. This will allow you to see exactly where data is going, opposed to "misc" Perhaps this will show exactly what is taking up the storage, since you are rooted perhaps backups are the problem.
If that doesn't tell you what you want to know, or if you think an app may be using data behind the scenes then the next step I would do is to use some sort of data usage monitor. The built in one may suffice, settings > data usage. If not there may be better apps out there, although to be honest I have zero experience with those.
cupfulloflol said:
There are a couple things I recommend doing in your position. First thing I would do would be to get an app that allows for more informative breakdown of what is using the storage. Something like diskusage should do the trick. This will allow you to see exactly where data is going, opposed to "misc" Perhaps this will show exactly what is taking up the storage, since you are rooted perhaps backups are the problem.
If that doesn't tell you what you want to know, or if you think an app may be using data behind the scenes then the next step I would do is to use some sort of data usage monitor. The built in one may suffice, settings > data usage. If not there may be better apps out there, although to be honest I have zero experience with those.
Click to expand...
Click to collapse
Uploaded a pic what diskusage says. When i hit media it only opens the file manager and directs me to sd storage
BTW this what Onavo says has been consuming data this month:
Market Downloader - 800MB mobile, 2.4Gb Wifi, all in background - and no, i didnt download anything from the play store on the go and hardly anything on wifi - havent updated my apps in weeks b/c of missing storage
Android OS + Others - 530MB mobile and a whooping 12GB on Wifi! All in Background too.
Timoooo said:
Uploaded a pic what diskusage says. When i hit media it only opens the file manager and directs me to sd storage
Click to expand...
Click to collapse
It looks like you have some nested 0 folders in that pic. Perhaps cleaning that up will clear up some space. Side note, if you haven't updated your custom recovery in a long time it may not be a bad time to look into that.
BTW this what Onavo says has been consuming data this month:
Market Downloader - 800MB mobile, 2.4Gb Wifi, all in background - and no, i didnt download anything from the play store on the go and hardly anything on wifi - havent updated my apps in weeks b/c of missing storage
Android OS + Others - 530MB mobile and a whooping 12GB on Wifi! All in Background too.
Click to expand...
Click to collapse
If I were in your situation, I would probably just get a clean start. This also would get rid of the nesting problem I mentioned above.
- I would make a backup of my current setup, probably just using Titanium Backup.
- Backup everything I want to keep from my phone to my PC, going through the 0 folders.
- Use fastboot to flash factory images, allowing it to wipe everything in the process. The .bat file should do this automatically.
- Use fastboot to install a recent custom recovery.
- Push the sdcard backup from my PC to my phone.
From here you have a couple options, root and reinstall Titanium backup and restore some of your apps (no system data) or go back into custom ROMs. You could flash AOKP again, or pick a different ROM.
A bit heavy handed, but I think that would be the least time consuming option considering the problem(s).
cupfulloflol said:
It looks like you have some nested 0 folders in that pic. Perhaps cleaning that up will clear up some space. Side note, if you haven't updated your custom recovery in a long time it may not be a bad time to look into that.
Click to expand...
Click to collapse
Yeah I noticed that like half a year ago, had no idea why that happened. At one point I felt like everytime I flashed a new rom a new 0 folder appeared.. How does that happen?
cupfulloflol said:
If I were in your situation, I would probably just get a clean start. This also would get rid of the nesting problem I mentioned above.
- I would make a backup of my current setup, probably just using Titanium Backup.
- Backup everything I want to keep from my phone to my PC, going through the 0 folders.
- Use fastboot to flash factory images, allowing it to wipe everything in the process. The .bat file should do this automatically.
- Use fastboot to install a recent custom recovery.
- Push the sdcard backup from my PC to my phone.
From here you have a couple options, root and reinstall Titanium backup and restore some of your apps (no system data) or go back into custom ROMs. You could flash AOKP again, or pick a different ROM.
A bit heavy handed, but I think that would be the least time consuming option considering the problem(s).
Click to expand...
Click to collapse
I was actually thinking about a clean start, googleing how to wipe everything and I read that thats kinda not possbile. But thanks for those steps, I'll do that when I have time!
Thanks
Timoooo said:
Yeah I noticed that like half a year ago, had no idea why that happened. At one point I felt like everytime I flashed a new rom a new 0 folder appeared.. How does that happen?
Click to expand...
Click to collapse
Basically when 4.2 came out, it brought along multi-user functionality. Custom recoveries at the time, when wiping and installing ended up creating the nesting problem. Recoveries then were updated, which doesn't create a bunch of /0 folders (one existing is correct). This was a super common problem about a year ago when 4.2 came to be. There were hundreds of threads about this problem, with more detailed info about what happens, why, and how to fix it. Wiping everything is one of the solutions, and since this isn't your only problem, this would probably be the recommended solution.
I was actually thinking about a clean start, googleing how to wipe everything and I read that thats kinda not possbile. But thanks for those steps, I'll do that when I have time!
Thanks
Click to expand...
Click to collapse
I am not sure where you read that a wiping everything isn't possible, but whoever said that is all sorts of wrong. There are multiple ways to wipe things.
Just did what you said and it looks like everything worked! Everything is deleted, I have almost 13 gigs of free space, rooted my phone again and I'll probably install aokp or paranoid in a couple days.
No 0 Folders anymore and I'm sure as hell hoping that my data consumption will be fine now. I'll keep you updated on that in a few weeks again, but thanks for the help!
looks good thanks bud
I bought this Samsung Galaxy Tab 3 SM-T210R for my mom its currently running kitkat 4.4.2 non rooted which I am about to fix here soon.
The problem is my mom hardly does anything on this facebook some books recipes and maybe 1 or 2 games and her church stuff and for some ungodly reason it keeps telling her she has low memory around 775mb left and it wont install anything else.
I put a 16gig sd in it for her and moved everything possible over to the SD cleared all the cache from all apps and have gone to the extent of restoring it to factory and it still keeps doing the same thing.
My only thoughts are root it with custom recovery and wipe it that way and reinstall the firmware but that is a extreme I would only do in a worst case scenario.
If anyone has any idea's I would appreciate it this isnt my first rodeo with android devices I am not a complete novice I have rooted my phones in the past including my current galaxy s4 so I am open for any and all ideas.
Thanks,
West
Need like 1 gig left on device on samsung device if that come from playstore.
nannaniel said:
Need like 1 gig left on device on samsung device if that come from playstore.
Click to expand...
Click to collapse
Yea I am aware of that part my problem is I keep wiping the tablet and restoring to factory and within a couple hours it tells me it has full memory or low storage space again.
I went to the extent of deleting the non needed folders such as downloads images dcim etc and letting the system remake them assuming they were the culprits I also went into the Android\Obb
and also Android\Data and cleaned out the stuff that did not need to be there on my last factory restore.
And No matter what I do upon resetting back to factory the space gets consumed within a couple hours and that's only just browsing the web and clearing the cache when done.
W,
hi, if you have a large amount of pictures/video, it may be gallery
generating/regenerating thumbnails in /sdcard/DCIM/.thumbnails.
Check the size of that directory, if that's the case delete the directory and replace it
with a dummy file named .thumbnails an set it's permissions to read-only
i ask because if your moms got hymns etc. that are actually in an image format instead of text
those will have thumbnails, the same with some ebooks.
Replacing .thumbnails with a fake .thumbnails will only make gallery run a little slower.
Many apps do the same thing, generating images in hidden folders on your sdcard for caching ads etc.
m