yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] neh4pres:
That sucks, and I'm positive I did nothing. I'm wondering if people with the issue have unsupported our corrupt media on the sd card. It is normal for it to go a few hours after a wipe Rom install. But after that something is up if it don't stop.

Via my Google Galaxy S3 running magic beans
[Verizon Samsung Galaxy S III] reebok_I_3:
Thank you so much! Where or how exactly do I get these files back to where they belong
[Verizon Samsung Galaxy S III] ker2gsr:
So far I think this fix worked for me I'll keep ya posted I need to run a full cycle from full charge to zero to be sure but preliminary trail looks good
[Verizon Samsung Galaxy S III] galchristian:
Pretty simple. Find Titanum Backup on your internal storage and paste the files I have posted. Open up Titanium Backup and all the way on the bottom of the list you should see the files. Just recover them restart done. :)

Am very happy to hear that.
[Verizon Samsung Galaxy S III] AJ26T:
i placed in titanium backup folder but when i launch app doesn't show them there all the way at the bottom
[Verizon Samsung Galaxy S III] suzook:
I have been running clean 4 since day one, and have better bat life than stock tw ics. Why are some having these media issues?
[Verizon Samsung Galaxy S III] AJ26T:
confirm

I can confirm with letting phone sit there charging and battery saver mode on mine dropped from 34% down to 19 and would have kept going if i left it but restored a nandroid just cause

thanks for all the help
[Verizon Samsung Galaxy S III] neh4pres:
I suspect it may be certain media files. Do those having trouble have LOTS of media, video clips? Maybe lots of pictures? Movies of different formats? DivX, wmv, xvid,?

Via my Google Galaxy S3 running magic beans
[Verizon Samsung Galaxy S III] ad78:
Go to apps. Disable media storage then reboot recovery then wipe davlik cache. Reboot, enable media then charge. It will take a few cycke though.

This will not beneficial to flashaholic like me lol. But try, at least a week. The batt life on S3 actually is fantastic!
[Verizon Samsung Galaxy S III] prenedo:
I have a ton of media (on my external sd card) from avi, mkv, flac, mp3/4, as well as 100's of pics synced from Picasa, etc.... The only time I get excessive media drain is when I first flash one of these JB roms. Even from the early jelly wiz leaks, it would happen for like the first day on the ROM, and settle down after a battery cycle. I would assume that a lot of people (not all) are just reacting to the issue too soon after flashing and not giving the ROM a chance to settle.
[Verizon Samsung Galaxy S III] MrBrady:
I don't know if it's been mentioned previously in this thread or others, but the Video Player TouchWiz app may be the issue here. By default it shows the video icons as a few second preview of each video. This takes quite a bit of processing power and perhaps that's what's chewing up Media, if you have a lot of video files. I believe you can turn off the icon preview in the preferences.
[Verizon Samsung Galaxy S III] jyabor91:
If you can figure out how to turn this off please let us know. I believe this is the issue as well but can not find an option to turn the auto preview.
[Verizon Samsung Galaxy S III] tucstwo:
With all due respect to the OP and the theory...this sounds a bit like hocus-pocus. I mean, install the rom, deleted the drain apps, and then re-install the rom WITH the apps? You're not accomplishing anything that the original flash did. What in the world could this possibly be doing? I must be missing something?
[Verizon Samsung Galaxy S III] tomalrocks:
this is a well known bug with touchwiz leaked roms with no proper solution. This is why I am using AOSP roms such as CM 10, eclipse rom etc till the issue is sorted out. The battery life is great on AOSP roms.
[Verizon Samsung Galaxy S III] prenedo:
That's not it. I have a ton of videos and I don't have this issue (after initial sync)... And that would only affect battery when you have the video player open and screen on, and even then that shouldn't eat up much battery.
[Verizon Samsung Galaxy S III] ker2gsr:
Update

It fixed the media drain I think but now my android os is high at 80% with 22 minutes screen time so still got a battery drain running jellybean's build 1ktoon kernel no o/c
[Verizon Samsung Galaxy S III] 17akota:
Whats up bros.

Heres a [How To] video for those that like the visual aspect of things. :)

http://www.youtube.com/watch?v=jbGgoiqhvfE&feature=youtu.be

Maybe post this in the OP?

I'm in the process of a battery cycle charge right now so tomorrow will be the test day of my batter life.
[Verizon Samsung Galaxy S III] Scott:
Interesting... But makes sense... I'll explain in a second what my thoughts are...

No or clean SD card... Easy... Let me explain....

Bingo! It has to rebuild the database that is associated with the media files...

Takes time... Has to index videos and images, etc...

Wont beat CleanROM ;)

(Granted I am a bit biased :cowboy: )
[Verizon Samsung Galaxy S III] galchristian:
Well I based this on the fact that all devs say disable the apps then clear data of them restart re-enable and charge. Well that never worked for me. So I deleted the whole thing and let it sit a bit restarted played around and then re-flashed the same ROM on top of it.

I understand that this doesn't sound like it would do anything. Simple logic vise it makes no sense and I agree on that but I posted snapshots and you can see my media is @ 2% also I do have lots of videos of all kind and it is still calm. I guess this method just confuses the system and fixes the issue after re-flashing clearing cache/dalvik and fix permissions.
[Verizon Samsung Galaxy S III] galchristian:
What a pleasure having you here Scott!

I honestly don't exactly know what causes it but your explanation makes sense. The only thing I know for sure is my experience that I had so I shared since my phone wouldn't even calm down after a day of usage. Media was always high and the phone just warm to touch even when the phone was sitting on my glass office desk for hours.

CleanROM is great I just can't get the missed calls or messages to be seen on my lock screen. Like message unlock or call unlock where it goes directly to the txt or missed call. But hey gotta sacrifice something for an early JB :D and I'm totally fine with that.

Thanks for your input.
[Verizon Samsung Galaxy S III] incubus26jc:
My thoughts on the subject are this...

1. This has been complaint ever since i started porting jellybean leaks.

2. The cause of the issue is indexing of media files after the rom is up and running.

3. The amount of time and battery used to index is based on the amount/size of the files one has on the phone/sd card.

4. I haven't done this fix and battery drain is not an issue because if you allow the phone to do what it needs to do you will be fine.

5. I have Not flashed rpm or jb radio. Still not an issue. Wouldn't be even if i did.

6. I flash a clean build everyday and sometimes multiple times a day when i test something I've added to the rom. So I'll force stop or disable media storage to save some battery. This is NOT a fix but just a delay of the indexing process.

Conclusion...

Sometimes it takes longer than others.

Sometimes it comes back after seeming to be done.

Sometimes it seems to get stuck and never finish. I just reflash if thats the case.

Patience is key. Give it time to index

EDIT: Scrosler beat me to it
[Verizon Samsung Galaxy S III] buzzdroidx:
with all of the above mentioned, I would venture a guess that a class 10 sd card would also help speed the process along since it r/w faster....just sayin. I'm running CR4 with JB radios and TW launcher and most of the options checked and am one of the "lucky" ones. My battery performance has been great since the day I bought this phone, and on every subsequent ROM that has been loaded onto it. Patience truly is a huge key when doing so much with these phones. Heck at some point don't you have to kinda sit back and enjoy the fruit of your labors, right?
[Verizon Samsung Galaxy S III] galchristian:
Thanks for everything guys. As I said I just tried to help since it worked for me and letting my phone sit for hours and use it like it for days didn't do anything for me and this fixed it on two different ROM's actually your ROM Scrosler and Incubus26jc. :)

Now what I'm doing is the following: I keep a backup of my working media and download and install a new JB ROM and replace the media/download with my backup should work. (I hope)

I do have a Class 10 UHS-1 micro sd. But indeed patience is key before any action.
[Verizon Samsung Galaxy S III] bobloblaw1:
Turning off Picasa sync would also likely help as the sd card won't be polluted with umteen cached files and thumbnails. Basically anything that minimizes the amount of crap and amount of file turnover on your card will minimize battery drain by media.

Is .nomedia still respected? That could also minimize the work the scanner has to do.
[Verizon Samsung Galaxy S III] Neverendingxsin:
Easier method, using rom toolbox pro, when you boot your phone up go to rom toolbox pro. Then click "autostart manager" search "media" longpress on "media storage" then click "advanced freezer" then under services at the bottom uncheck the first one, then after a few seconds recheck it. Problem solved.

Media scanner only runs at boot.
[Verizon Samsung Galaxy S III] 17akota:
Doing this did in fact wipe "Media" from my Battery status. But i still have "Android System" and "Android OS" right under my Screen time. :/

I did notice a tiny improvement in battery. 11 hours off charger and 1.5 hours screen on time and sitting at 40%. The screen on time is light useage as well. Majority is texting and a few times on facebook.
[Verizon Samsung Galaxy S III] open1your1eyes0:
I may have found a more thorough solution if anyone is willing to try it.

First make a CWM backup just in case

Go to Setting >Application manager

Go to the "All" section

Go to "Gallery" > Force Stop, Clear Data, then Clear Cache

Repeat the same for any other Gallery type app that you may have downloaded (like Quickpic)

Go to "Google Play Music" > Force Stop, Clear Data, then Clear Cache

Go to "Media Hub" > Force Stop, Clear Data, then Clear Cache

Go to "Music Hub" > Force Stop, Clear Data, then Clear Cache

Go to "Music Player" > Force Stop, Clear Data, then Clear Cache

Go to "Video Player" > Force Stop, Clear Data, then Clear Cache

Repeat the same for any other music or video type app that you may have downloaded (like Poweramp, MXPlayer, etc...)

Finally go to "Media Storage" > Force Stop, Clear Data, then Clear Cache

Reboot into CWM and clear cache and clear dalvik-cache

Reboot your phone and let it sit for a good few hours without doing anything on it and let it charge (probably a good idea right before you go to bed for example)

When you wake up or after a few hours, reboot your phone one last time, let it sit for 5-10 mins after you see the lockscreen and then use it as regular and report back with your results
[Verizon Samsung Galaxy S III] prenedo:
Thanks for your input as well... I got it after flashing (most) all of your releases and also after switching between Verizon based roms. Only happens after a data wipe. For example I had less than 2 hours screen on time and like 10 hours out of battery use yesterday before phone died (media usage was high and I flashed synergy yesterday morning). Today was my second day on the ROM... Here's where I'm at:
[Verizon Samsung Galaxy S III] pchoi94:
so here's my experience for what it's worth...

i have been getting the media drain issue with every single tw based jb rom I've flashed. none of the so called fixes ever seemed to permanently fix the issue. Some of them would seem to work for a while, but they were all only temporary.

what I noticed is that it only seems to happen when I boot up my phone, then stop after about 5% of the battery is gone. The reason I know this is because I reboot my phone a lot. I have the official external charger and spare battery. I rarely plug my phone in. After the initial media scan, my phone sleeps like a baby and is ice cold when I reach for it. Also no media scanner wake locks according to better battery stats.

What I'm wondering is if the people who supposedly think they've fixed the issue (not including freezing media scanner) normally reboot their phone, or if they do, if they check for the media scan wake lock right after boot up? I suspect most people leave their phone on and charge as needed, so they may never see the media drain after the initial boot and "fix" if they never reboot?

maybe not, who knows...
[Verizon Samsung Galaxy S III] Mustang302LX:
I think you hit the nail on the head there. This is exactly my experience but my media scanner scans for more like 10-20 minutes after booting.
[Verizon Samsung Galaxy S III] roalex:
I have notice it too, on my SGS3 int, its related with DRM i think (Digital Rights Management) content and media scanner.

I found it on the Bug tracker
[Verizon Samsung Galaxy S III] dangerou:
I had the High Media drain, yesterday it was at 50% and killed my battery. in 4 hours the media had 1.5hrs of CPU time. I let it go, charged it and today its basically non existent. I guess it just took that long to index my stuff. I did clear the stuff as was recommended above, I think that just made things take LONGER to finally settle in as clearing everything just made it start over.

So guess if you flash a rom daily, you will have high usage all the time.

---------- Post added at 11:47 AM ---------- Previous post was at 11:02 AM ----------

I may have spoken too soon. I did reboot this morning (51 minutes ago), and now my battery is draining fast adn MEDIIA is at 55%.
[Verizon Samsung Galaxy S III] Mustang302LX:
I've said before nothing we do will fix this issue for good. The best current solution is to download this app: https://play.google.com/store/apps/details?id=com.addz.mediascannerroot&feature=nav_other#?t=W10. and disable media scanner. I can now reboot and everything and not have media scanner scan ever. I can reenable it via the same app but I have been leaving it disabled to save my battery from draining.

Also if you don't want to use that app I found removing the external sd card allows media scanner to scan for only 20-40 seconds and then stops after each reboot. I have formatted my card and removed all my music files and anytime I put my sd card back in media scanner goes endlessly again. So I decided to use my sd card and just use the above app.
[Verizon Samsung Galaxy S III] blestsol:
I fixed it by formatting my sd card. Hasn't come back yet.
[Verizon Samsung Galaxy S III] dalepa:
After updating to JB, cpu almost burned a hoe in my s3. I finally had to disable media storage to stop the madness. Butter my a$$
[Verizon Samsung Galaxy S III] flamus:
I never notice this on CM10 ... must be a stock issue or maybe touch wiz. =\
[Verizon Samsung Galaxy S III] Samsung.Galaxy.S3:
I hadn't seen it on CM10 either.
[Verizon Samsung Galaxy S III] mustafaakk:
Disabling Media Storage makes the media files invisible to gallery.

Maybe a simple task will be enough that kills the media storage process at boot completed event.

Tasker is a good solution. I didn't try but it makes sence for me.
[Verizon Samsung Galaxy S III] d1ez3:
I have media scanner run on every single boot on CM10
[Verizon Samsung Galaxy S III] pchoi94:
I think I found the issue...

Well, after reading through countless forums and threads and posts etc etc etc I think I finally found the issue.

First of all, I did download the Rescan Media app, which disables the media scanner on boot, and that is a great workaround. But it just kept bugging me as to why this issue was occurring...

So I decided to finally try to copy off all of my data from my SD card and reformat. One thing I noticed was that the Clockworkmod backup folder, where the nandroid backups are stored, was very large and had a lot of files. Apparently, the older version of CWM nandroid backups put everything into a single large tar file, while the newer version puts everything into blobs as separate small files. The newer method reduces overall backup time and storage usage (across multiple backups) by using de-duplication.

The issue is that it leaves a LOT of files sitting on your SD card. I counted 18,000+ files on my SD card including the blob files! After I copied all of my files to my PC, I deleted the nandroid backups from my SD card and counted about 450 files remaining.

So I did a test: I re-enabled media scanner on boot using the Rescan Media app and rebooted. Using better battery stats, I noticed that the media scanner now runs for only about 2 minutes or so, versus the 10 to 15 minutes it used to run for with every boot. Also, from a cold boot with a freshly charged battery, if I wake the phone up after about 10 minutes after boot, it still reads 100%, whereas before it would read about 95%.

So it appears that the media scanner is not necessarily misbehaving... in fact, it's behaving exactly the way it was intended, which is to scan all the files on your SD card to look for any newly added media files. The problem is that with 18,000+ files to go through, it takes a while and uses CPU.

Did the algorithm change between ICS and JB? Maybe... so maybe there really is an issue. Who knows. But for those of you who are having this issue, check to see how many files you have on your SD card, and if you have a CWM backup that uses the blobs vs tar files, you might want to copy those off.

I think the next CWM backup I do will be in tar format. I don't do backups often enough to reap any benefits of using de-duplication, I pretty much only do a backup before flashing a new ROM and I usually delete older backups as well, and I don't flash that often...

EDIT: By the way, I never do a clean wipe between ROM flashes if they are similar. I went from stock ICS rooted to the I5 leak, to the J1 leak, to the new K1 leak, all without wiping data, only cache and dalvik. I think it's silly to wipe data all the time unless you are going to a completely different base, i.e. from touchwiz to AOSP, or vice versa. Neither Google nor Samsung nor any android manufacturer intends regular users to wipe all data with OTA updates, so why should we? Also, to be clear, I DID NOT end up reformatting my SD card, I left all the files there except for deleting the CWM backup files and blobs, and my problem is now gone without having to disable media scanner on boot.
[Verizon Samsung Galaxy S III] galchristian:
Nice!! Thanks for the great input! Honestly I don't want to advertise any ROM's but it used to happen on every JB leak or port on the GS3 and now I tried the latest leak (CleanRom) and I don't have any media drain at all. So god know what eats battery...but....all IO can say the closer we get to the official release of JB for verizon it gets better and better every leak! So just lets cross out fingers and see what will happen :good::fingers-crossed::laugh::victory:
[Verizon Samsung Galaxy S III] eon69nc:
media and network

Guys, I have noticed that whenever I have dropped to 1x signal or bad location for reception that I have the media issue, once I am back in my normal 4g area this stops and media does not show in the battery information. Has anyone else had this happen. ?
[Verizon Samsung Galaxy S III] pchoi94:
Never happened to me that I know of, that sounds strange...
[Verizon Samsung Galaxy S III] shawn01:
I have actually notice this too. On 4g I get amazing battery life. On 2g/3g I get OK battery life. Strange.
[Verizon Samsung Galaxy S III] bnmohler:
thats not really strange as the LTE antenna is still enabled and using more power to re-connect to a tower. you should get better battery in a good signal environment.

I had some battery drain issues on CR4.5 with the J modem. i didnt know any of this media scan stuff so i just tried the one thing i thought would help. i booted into TWRP and flashed the I radio and rpm. booted up then went back into recovery and flashed the J modem and rpm again. I no longer had excessive battery drain. I dont have many media files on my sd. and i was running cr4.5 with the j modem for 3 days before trying this so it had time to settle. I guess my issue was something else but if this thread is not helping then give that a try.

I am now on cr 5.0 with the K modem and rpm and so far battery is where it should be after 1 day.
[Verizon Samsung Galaxy S III] Metfanant:
i will say...i just deleted my CWM backups off internal and external storage...and instantly Media stopped using CPU cycles...rebooted...and it barely ever made a blip of usage after boot...

seems (at least in my case) that the MASSIVE blobs folder was causing the issue with constantly being scanned...

Edit: seems to have been a temporary fix...as its doing it again
[Verizon Samsung Galaxy S III] ExcludedDroid:
This worked for me. Remember that there could be two different CWM folders on both the internal and external SD card. I had THOUSANDS of damn blobs. :eek: Deleted em all. Remember also that when you charge to 100%, unplug (which wipes batt stats) and reboot, media server will initially seem very high, although it you check it's actual usage, it would have only used the cpu for around 2 minutes, in my case at least. Compared to the 20-ish mins and 15% battery drain later, I'll take the ~1% drain !! :good:

Cheers,

ED :highfive:
[Verizon Samsung Galaxy S III] Boardwalk30:
I have a feeling you're on to something, but a quicker fix would be just to stick a ".nomedia" file in the clockworkmod folder (which is what I just did). Same solution, different method. Good find though!
[Verizon Samsung Galaxy S III] Metfanant:
Over the time since I posted that, in probably should have added another "edit" as media CPU usage has basically come to a halt...

Android OS and Android System are still a little high for my tastes...but even with my phone only being off the charger for less than an hour at this point of the day "media" is nowhere to be found in battery usage

Yeah...this crossed my mind as the process of deleting the folders completes lol...

I assume a .nomedia file would not have any impact on the restore of the backups?

sent from my VZW Galaxy S3 running Synergy Jelly Bean
[Verizon Samsung Galaxy S III] Boardwalk30:
I wouldn't assume so, though that is being said without trying. I have the .nomedia file in place, but have yet to try a restore. Seeing as it's in the root directory for the backups, instead of the backups themselves, I'd have to guess it wouldn't affect them.

Anybody wanna give it a shot? ;)
[Verizon Samsung Galaxy S III] jonnyboiii:
I have a ton (still bit of an understatement) of files on my sdcard as well... Two things though:

1: do I just add the .nomedia file into the clockworkmod folder, not any sub folders?

2: Changing backup format to .tar is done in the "backup format" section of CWM, correct? All that does is make it one massive file easier for media scanner to scan, but slower backing up?

I'll give the .nomedia thing a shot and report back later. :thumbup:

Sent from my Verizon GS3 on Bean's JB ROM
[Verizon Samsung Galaxy S III] xjjk:
I had a similar experience the other day.. .I deleted two backups and suddenly media scan was cut to a very quick run on boot. I had meant to post something about it but got busy and forgot.
[Verizon Samsung Galaxy S III] jonnyboiii:
Booted an hour ago, having placed a .nomedia file in the clockworkmod folder and the media scanner is nonexistent. Literally.

Here's to hoping is stays that way...

Sent from my Verizon GS3 on Bean's JB ROM
[Verizon Samsung Galaxy S III] shawn01:
No problems from deleting nomedia file?
[Verizon Samsung Galaxy S III] jonnyboiii:
Media has really calmed down as well as system for me... .nomedia file is a confirmed fix for me!

Time awake finally matches screen on! :thumbup:

Sent from my Verizon GS3 on Bean's JB ROM
[Verizon Samsung Galaxy S III] shawn01:
Actually .no media file is bs. Media is still out control on my s3.
[Verizon Samsung Galaxy S III] shawn01:
Stock leak k1... stock kernel.
[Verizon Samsung Galaxy S III] dogredwing1:
You should check out this thread it has solved my high android system and media issues.

http://xdaforums.com/showthread.php?t=1977223