Develop Bugs

Camera won't save pictures, can't dl whatsapp-images

Hey Guys,
I'm having a problem since i first rooted my Nexus GSM: When using the camera, the clicking sound appears, but there is no new thumb in the corner and no picture saved in the DCIM/Camera folder. If I'm trying to do a video, the app crashes.
If somebody sends me a picture in Whatsapp, I see the litte thumb, but if i click it, nothing happens (and of course - no picture is saved on the phone).
I check the permessions for the camera and the DCIM-folder and I let the RecoveryMod fix all permissions. Do you have any idea what could have gone wrong?
First I installed Revolution HD ROM, today I did a reset and installed AOKP ROM. Problem stays the same.
I hope you can help me!
EDIT: Checked data & media, too.. everything is rwxrwx--x

Ok, I fixed it.
If anybodye else got this problem: I simply deleted the DCIM & WhatsApp-Folder.
Don't know why i didn't try that before -.-
Sorry guys

permissions the cause
hi, i had the same problem. PERMISSIONS SEEM TO BE THE ISSUE....
I backed up and restored my memory with the tool kit.
Under "BACK UP OPTIONS" i selected "3. backup you Internal Storage [virtual SD Card]"
The only way i have been able to get around it is by changing the name of the dcim folder as i was unable to delete it.
note: i have also had various other problems with other apps. these apps had folders that were restored via the toolkit. in some cases all i had to do was rename the permission locked application folders. in other cases i had to rename their folder and create a new one with the original naming and sub folders

[Q] Couldn't capture screenshot. Storage may be in use.

Verizon Galaxy Nexus.
I was running 4.0.4 IMM30B leak. The new leak/possible update came out, I decided to flash it. Saw that it was only good for updating from 4.0.2 (ICL53F), so I wiped, formatted, and reinstalled it. Re set up my phone (titanium backup, homescreens, android market updates for a few apps, the basics). Everything seemed fine, though I didn't try saving anything. Ran the update to the new 4.0.4, and everything seemed fine and dandy.
The next day, titanium backup runs (scheduled) and fails. Says not enough storage or something despite the fact that it also shows ~14GB free space...
Tried to take a screenshot of the issue, and I get a notification that it "Couldn't capture screenshot." "Couldn't save screenshot. Storage may be in use."
Curious, I tried to take a picture with the system camera app, and it doesn't seem to save pictures either. Though no error messages tell me such things.
Caching seems to work, updating apps seems to work, using 'most' apps seems to work, but saving data to the virtual SDcard has no such luck.
Assuming that it's a permissions issue, I went into CWM Recovery and did a 'fix permissions.' Though that has not fixed anything.
Various searches have shown me that others have experienced this problem, but I haven't seen anyone with a solution. Also, they seem to be experiencing it in various AOKP roms (specifically for the Transformer tablet).
Question: Anyone know what I can do to fix it?

Haha this happened to me and no1 could answer it happened when i went from aokp m4 to m5.. Was odd, but what i did to fix was relock and unlock the bootloader and then get all my stuff back with titanium.. At least that worked fine for me
Edit: well i relocked restarted system and boot android, then reboot into bootloader and unlocked again, then boot into android (fresh new system) and im writing this from my fixed phone 1 week ago.. No problems so far
Sent from my Galaxy Nexus using xda premium

msedek said:
Haha this happened to me and no1 could answer it happened when i went from aokp m4 to m5.. Was odd, but what i did to fix was relock and unlock the bootloader and then get all my stuff back with titanium.. At least that worked fine for me
Edit: well i relocked restarted system and boot android, then reboot into bootloader and unlocked again, then boot into android (fresh new system) and im writing this from my fixed phone 1 week ago.. No problems so far
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Glad to hear that there is a fix. I may end up doing this tonight... I'm hoping that a quicker, simpler fix is available (something like boot an insecure.img and change permissions of these folders via adb, or something).
Thanks for that though, as I now know that it should work.

Happening on GSM Galaxy Nexus as well. I tried a rom over milestone 5, then reinstalled milestone 5 and restored my backup, and then got this problem. Seems sdcard is not writable to at all. Gonna try out the bootloader locking stuff i guess.

I ended up using the Galaxy Nexus Toolkit (for time and automated simplicity) to wipe the device, reflash 4.0.2 (signed by Google), reroot, CWM reccovery, and restore the virtual sdcard backup saved with the toolkit.
Once the virtual sd was restored, I restored my apps (but no system apps) with titanium backup. Haven't had the time since to reupgrade to 4.0.4, but 4.0.2 seems to be working for me nicely.
I am able to screenshot, and nice things like that, but sometimes titanium backup is giving me errors about not being able to save due to insufficient space (still 14GB free). Gonna dive into that issue today.

4.0.2 works good.. What its bad about it its the lag, the ROM its laggy and also the battery life and the photo quality.. ICS now its much better than 4.0.2
Sent from my Galaxy Nexus using xda premium

No fix?
I'm also getting this problem and only since installing android 4.3 from CM 10.2
I have also noticed that when I connect by USB to my PC I can't see anything but the external sd card whereas in the past I've been able to see 3 devices - ext sd, int sd and system. This makes me think it's permissions but I'm not sure what to change and where.
I need a screenshot to send a picture of an mms issue I'm having and can't re-install/restore whatever as this deletes the mms with the problem so I need a fix that leaves the phone as it is except for this repair.
Any help appreciated.

Redscorpian said:
I'm also getting this problem and only since installing android 4.3 from CM 10.2
I have also noticed that when I connect by USB to my PC I can't see anything but the external sd card whereas in the past I've been able to see 3 devices - ext sd, int sd and system. This makes me think it's permissions but I'm not sure what to change and where.
I need a screenshot to send a picture of an mms issue I'm having and can't re-install/restore whatever as this deletes the mms with the problem so I need a fix that leaves the phone as it is except for this repair.
Any help appreciated.
Click to expand...
Click to collapse
Dat gravedig.
Just try reflashing your device from a stock image.

Beauenheim said:
Dat gravedig.
Just try reflashing your device from a stock image.
Click to expand...
Click to collapse
And do you think that'll be leaving it as it is?

I fixed this deleting the "pictures" folder with RootExplorer.

jwiegand said:
I fixed this deleting the "pictures" folder with RootExplorer.
Click to expand...
Click to collapse
Tried booting in t recovery fixing permissions, tried delete the screenshot folder and tried wiping the dalvik... Never thought of deleting the Pictures folder. Solved it for me to! (This problem just occurred without me flashing a new rom or anything. A ~9 month old AOKP and the error just came up after a reboot)
Thanks jwiegand!

bergmanman said:
Tried booting in t recovery fixing permissions, tried delete the screenshot folder and tried wiping the dalvik... Never thought of deleting the Pictures folder. Solved it for me to! (This problem just occurred without me flashing a new rom or anything. A ~9 month old AOKP and the error just came up after a reboot)
Thanks jwiegand!
Click to expand...
Click to collapse
I'm on a different phone, but I fixed this issue by clearing the defaults for the program that launched pictures. In my case, I use Gallery, so in Program Info under Settings, I reset defaults and everything worked fine. I guess this is the same thing as deleting the Pictures folder since I believe it is an issue of 'releasing' the memory that remains in use by your respective program. For all future requests as to which program should be used to launch a file (or picture in this case), I never select the option that binds future requests to one specific program. Hope that helps .

My fix: re enable the media scanner!
Like many others, I have disabled the DRM and media scanner services because of the bug that caused ridiculous cpu usage (particularly on boot). Re enabling the media scanner fixed this problem right up. If you want a free and easy utility to do this, check out: "Rescan Media ROOT"
https://play.google.com/store/apps/details?id=com.addz.mediascannerroot
Disclaimer: I am not associated with the author of that app.

On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.

TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
I tried all the previous solutions without success, but manually creating the Pictures/Screenshots folder worked flawlessly on my LG 4X.
Thanks TulsaDavid!

TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
Thanks alot! Worked for me!!

Thanks, TulsaDavid!
Making screenshots folder solved it for me aswell.

Unable to take Screenshot, USB storage maybe in use
TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
I have tried using home+power button, turned on swipe and had difficulty in using the S PEN to make the screenshot - still doesnt work.
I also tried making a new folder but still doesnt work.
My unit is Samsung Note 8.0

/sdcard permissions broken
Just had this happen on my Nexus 5.
The cause was using adb push to copy files to /sdcard when I was booted into recovery. All the files and folders were owned by root:root. I had to reboot to recovery, adb shell, and then
Code:
chown -R media_rw:media_rw /data/media/0
It might be possible to do this while booted in android with Connectbot or something, but I didn't try that.

TulsaDavid said:
On some devices (such as Infuse, as was in my case), the only solution was to manually create Pictures/Screenshots (full path: /sdcard/Pictures/Screenshots or /storage/sdcard0/Pictures/Screeshots). I created them with Root Explorer.
Had tried all other solutions, but they did not work. Seems that the power button Screenshop would neither create Pictures nor Pictures/Screenshots.
Click to expand...
Click to collapse
Thank you TulsaDavid. This helped me tremendously. You're a deity!
Sent from my SGH-T989 using Tapatalk

[Q] Can't access my old files after switching ROM from AOKP to CM

Initially I thought this was a problem with Google Play / Apollo, but I realize now that when I plug in my phone via USB, I can't see any of the many, many folders and files present on /sdcard that I could see previously.
If I copy a "new" mp3 onto my Galaxy Nexus, it's recognized just fine by both Google Play and Apollo. However, none of my old mp3s (or files, for that matter) are recognized. They were placed in /sdcard/Music, a folder that I cannot see when I plug in my phone, only from the file manager running on the phone. The issue persists if I move an "old" mp3 from my music folder out into the sdcard root, it's still not recognized. This makes me think this might be permission related, but the file manager says that all files are readable and writable.
I've tried running "fix permissions" in both ROM manager and the CWM recovery, but it makes no difference. Any idea what has happened, and how to fix it so that I can use all my old files again?
edit If it's any help, I just ran ls -al in a terminal emulator and I can't see any difference at all between folders I can and cannot see. Example: I can see /sdcard/media just fine, because I created that folder from Explorer in Windows. Music in that directory works. I cannot see /sdcard/music. Here's the permissions:
Code:
drwxrwxr-x root sdcard_rw 2012-09-18 media
drwxrwxr-x root sdcard_rw 2012-09-16 music
This is a bit confusing.
When I try pulling and pushing a file with adb like so:
Code:
adb pull file.tar
adb push file.tar file2.tar
I get
Code:
failed to copy 'file.tar' to 'file2.tar': Read-only file system
I've tried remounting /sdcard in root terminals both on the phone and via adb, but I get mount: Operation not permitted. I'm thinking this might be because /sdcard isn't the actual path but I've tried /storage/sdcard0 and /mnt/sdcard as well and I get the same error.
Thanks in advance for any suggestions.
(This question was also posted on android.stackexchange)

adb push /sdcard/file2.tar
also, cm doesnt have root access enabled by default for adb.
/sdcard/ is already rw, otherwise apps couldnt place anything there. nor could we.
Sent from my i9250

Didn't realize I needed an absolute path, thanks! I now managed to push the file, but it does not show up under the "Galaxy Nexus" unit in My Computer. It does show up when I do an ls in adb shell though. Any ideas?

bajsmumsaren said:
Didn't realize I needed an absolute path, thanks! I now managed to push the file, but it does not show up under the "Galaxy Nexus" unit in My Computer. It does show up when I do an ls in adb shell though. Any ideas?
Click to expand...
Click to collapse
try disabling mtp on the device; or rebooting, if you want to stick with mtp. maybe it has to refresh file list?

bk201doesntexist said:
try disabling mtp on the device; or rebooting, if you want to stick with mtp. maybe it has to refresh file list?
Click to expand...
Click to collapse
Switching from MTP to PTP does nothing, the same files are shown ("new" files). I'd like to stress that if I take a picture for example, that pictures does show up both with MTP and PTP. New files work fine. It's the old files that I can see in the file explorer in the actual phone that just refuse to show up when I connect to my computer, and they are obviously also not recognized by apps in the phone (such as Apollo or Google Play).
I realize that I could work around this issue by just removing everything from my sd card and then putting it back, but I really want to figure out how this can even happen.

I'm no expert by far, but it sounds like when you changed ROM the"index"file for mtp isn't updates. Have you tried to run the media scanner?
Swype'ed on my CM10 Galaxy Nexus

Herman76 said:
I'm no expert by far, but it sounds like when you changed ROM the"index"file for mtp isn't updates. Have you tried to run the media scanner?
Click to expand...
Click to collapse
If I've understood correctly, power cycling the device should trigger the media scanner. I just tried restarting, and it made no difference. (I've restarted the device several times since this problem occurred).
Opening the Gallery app still only shows me two pictures (I've taken two photos since the ROM flash), interestingly the thumbs are for other pictures lying around and after a while Gallery crashes. I use QuickPic more often though and that app behaves well, and shows all photos.
edit As a final resort, I tried doing a full wipe and reinstalling CM10 M1 completely, without restoring any settings or apps from any old installations. The issue still persists! Any files created with my now "old" CM10 installation no longer appear, even when they are moved within a folder where other "new" files are shown and working. This is starting to annoy me, but since this obviously is a bug in CM10 M1 I see no point in trying to spend time solving it, I'm just going to switch back to AOKP. Thank you for any answers and attempts at solving this.
edit2 Formatting /sdcard in CWM recovery fixed this, even though it might not be the most elegant solution.

Have you seen this?http://forum.xda-developers.com/showthread.php?p=30288268
Basically what it suggests is that you go to apps via settings, find the "Media Storage" app (it's a system app) Clear data/cache, then reboot. This was my problem.
Sent from my Galaxy Nexus using xda premium

[Q] android media process high cpu

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!))

android.process.media keeps stopping - so annoying

Dear all,
I have been using RMN5 for a while and this is the most f**cking annoying error in this phone (or MIUI's error - i got it in my LG F180L running MIUI7 a long time ago and it happened too)
Every time i connected the phone to PC, i got this problem, I've followed the tips on XDA about disable media storage and download (force stop only in RMN5) and reboot, ok it fixed for a while, but not for long, next time i connect, it happen AGAIN.
I'm so tired of this sh*t and want to get rid of it.
Please, somebody please show me the way.
Thank you

Don't disable those apps instead go to the app settings media storage and download and clear both cache and data, hopes this will solve the problem and move this post to question and answer thread. It belongs there.

you disabled critical system app and complained why you get error messages

This is the Android Media Scanner, looking for files to index on your storage.
Some options are:
Try creating a file called '.nomedia' in every folder, and the problem should dissapear. In that case you may have a corrupted file somewhere, so try to delete the .nomedia file in some of the suspected folders to see if the problem comes back (or google something like 'android.process.media .nomedia' for a better explanation or solution.
You can also enable debuggind (via developer options), to inspect the problem with adb logcat, or to install a logcat related app from Play Store, in case the dump that should appear at the time of the error contains some hint.

rgawenda said:
This is the Android Media Scanner, looking for files to index on your storage.
Some options are:
Try creating a file called '.nomedia' in every folder, and the problem should dissapear. In that case you may have a corrupted file somewhere, so try to delete the .nomedia file in some of the suspected folders to see if the problem comes back (or google something like 'android.process.media .nomedia' for a better explanation or solution.
You can also enable debuggind (via developer options), to inspect the problem with adb logcat, or to install a logcat related app from Play Store, in case the dump that should appear at the time of the error contains some hint.
Click to expand...
Click to collapse
I'm having this issue after updating my Samsung GT-N8013 to lineageos 16.0. When you say to put a .nomedia file in every folder, do you litterally mean every single folder on both the tablet and sd card or a certain level of folder?

tcfulmer said:
I'm having this issue after updating my Samsung GT-N8013 to lineageos 16.0. When you say to put a .nomedia file in every folder, do you litterally mean every single folder on both the tablet and sd card or a certain level of folder?
Click to expand...
Click to collapse
The .nomedia flag file will stop the scan in the directory it's placed and all of the directories contained in it.

I ended up reinstalling the the OS 16.0 rom for my Samsung N8013. It took a total of running the installation 3 times but it finally became stable.