Root [Verizon] After root "media" is eating battery

[lonewolf411]

So I rooted my s3 earlier tonight and haven't flashed a custom rom yet. I've made a nandroid backup and backed up my apps and data with titanium backup. My battery has started to plummet within the past couple hours. I'm not doing anything out of the ordinary. I've checked battery and "media" is taking up over 30 percent, that's more than the screen! What could be doing this and how can I fix it? There was no problem on 4.1.1 before root.

 

[Metfanant]

So I rooted my s3 earlier tonight and haven't flashed a custom rom yet. I've made a nandroid backup and backed up my apps and data with titanium backup. My battery has started to plummet within the past couple hours. I'm not doing anything out of the ordinary. I've checked battery and "media" is taking up over 30 percent, that's more than the screen! What could be doing this and how can I fix it? There was no problem on 4.1.1 before root.

its a problem with the new way that CWM creates backups (at least on our phones anyway)...CWM uses this new "blobs" folder for redundant data in multiple backups...

unfortunately the media function of our phone scans all file locations for media...well the "blobs" folder contains thousands and thousands of files for the phone to scan...

remedies:

1. change the backup format in CWM
2. put a .nomedia file in the blobs folder

this should quiet down media drainage

 

[lonewolf411]

its a problem with the new way that CWM creates backups (at least on our phones anyway)...CWM uses this new "blobs" folder for redundant data in multiple backups...

unfortunately the media function of our phone scans all file locations for media...well the "blobs" folder contains thousands and thousands of files for the phone to scan...

remedies:

1. change the backup format in CWM
2. put a .nomedia file in the blobs folder

this should quiet down media drainage

Im sorry i dont know how to do this. How would i go about doing these steps?