Hi
Does anyone Chrome crash when they download any APK, PDF files etc in Chrome? (for example betterbatterystats.apk)
A .nomedia is always created in the downloads folder, when I delete it, it stops crashing when I download something through chrome but after I restart my phone, it reappears again.
How do I get it to stop creating a .nomedia in downloads or stop it from crashing...
This happened to someone else as well but no fixes was shown in comments
https://support.google.com/chrome/thread/24873165?hl=en
Related
Hello everybody!
I got an issue on my Froyo (LeDroid) rom.
When i download a picture from my Dropbox folder (or from the EX-Explorer via lan-network), the picture does not show up in the gallery, where i can chose it as my wallpaper.
The File is defenitly there (i see it in the file-explorer) but it does not show up in the gallery apps.
How can i fix this?
Someone noticed something simmilar ?
Maybe the Gallery is a little "lazy", if so then SDrescan might help:
http://www.appbrain.com/app/com.bero.sdrescan
I had the same issue, in completely same steps.
On my PC on the dropbox I dropped a ringtone, the placed it in /sdcard/media/ringtones/ with the file manager, but the ringtone showed up nowhere.
Reboot of phone helped
Edit: I get "installation unsuccessful" for sdrescan.
I just unmount and the remount the SDCard.
Every time I reboot my GNex, I receive the error process android.process.media has stopped, usually at least twice.
I've searched and tried some of the solutions that have been suggested (fix permissions, clear data/cache of Market, clear data on Media Storage)
So far, no joy. This isn't a custom ROM, I've only rooted the 4.0.2. I'm also running Nova Launcher, but this problem started prior to adding the new launcher.
Any other suggestions? Or any suggestions what I can do to troubleshoot? I've seen suggestions of reformatting the SD card for other models that have this issue, but that isn't really a viable alternative to the cardless Galaxy Nexus.
I've had the same problem as well, and nothing suggested online worked for me. Anyway I had to play around with it a while until I found a "solution".
First thing first I believe that the problem is arising from the Media Scanner getting force closed when it tries to scan a file with "corrupt" data or filename (it's probably not a corrupt file as such and the problem probably lies with the Media Scanner itself. Hopefully Google will fix it soon).
What I did was first putting a .nomedia file in every folder in the /mnt/sdcard directory. Basically this will tell the Media Scanner not to scan the content of any of the folders. Now wipe the data for Media Storage (I also wiped the data for the Gallery and Music apps just to be safe) and then restart the phone. Now if my theory is correct then you won't get a android.process.media force close.
(Also to add the .nomedia files I used an app called Super Manager which you can get on the market. Maybe you can do it with other file manager apps too. Normally you can also do this by plugging the phone into a computer but it seems that with MTP not all of the folders will show up.)
Now you can remove the .nomedia file from the folders that you have musics/pictures/videos/ringtones/notifications in one by one. Once you remove the .nomedia file from one folder, reboot and make sure you don't get a force close, then repeat the same thing for the next folder until you have all the folders you store media files in. If at any point, you reboot and get a force close then you know where the problem file is stored. Personally I didn't find the file that was the problem (it was probably in one of the folders that I left a .nomedia file in) but if you do then I guess you can try backing up the content of that folder, deleting it and copying it back to the phone again. Don't forget to wipe Media Storage again, reboot and see if that fixes the problem.
Hope that's useful!
Chrono_Tata said:
I've had the same problem as well, and nothing suggested online worked for me. Anyway I had to play around with it a while until I found a "solution".
First thing first I believe that the problem is arising from the Media Scanner getting force closed when it tries to scan a file with "corrupt" data or filename (it's probably not a corrupt file as such and the problem probably lies with the Media Scanner itself. Hopefully Google will fix it soon).
What I did was first putting a .nomedia file in every folder in the /mnt/sdcard directory. Basically this will tell the Media Scanner not to scan the content of any of the folders. Now wipe the data for Media Storage (I also wiped the data for the Gallery and Music apps just to be safe) and then restart the phone. Now if my theory is correct then you won't get a android.process.media force close.
(Also to add the .nomedia files I used an app called Super Manager which you can get on the market. Maybe you can do it with other file manager apps too. Normally you can also do this by plugging the phone into a computer but it seems that with MTP not all of the folders will show up.)
Now you can remove the .nomedia file from the folders that you have musics/pictures/videos/ringtones/notifications in one by one. Once you remove the .nomedia file from one folder, reboot and make sure you don't get a force close, then repeat the same thing for the next folder until you have all the folders you store media files in. If at any point, you reboot and get a force close then you know where the problem file is stored. Personally I didn't find the file that was the problem (it was probably in one of the folders that I left a .nomedia file in) but if you do then I guess you can try backing up the content of that folder, deleting it and copying it back to the phone again. Don't forget to wipe Media Storage again, reboot and see if that fixes the problem.
Hope that's useful!
Click to expand...
Click to collapse
I am trying this out. Question. How do I create the .nomediafile? NVM. Figured it out. Hope this will work.
Just a bump.
Clearing data in Media Scanner worked for me and rebooting. Didn't have to do that other stuff. YMMV.
Thanks to Chrono for the info.
Chrono_Tata said:
I've had the same problem as well, and nothing suggested online worked for me. Anyway I had to play around with it a while until I found a "solution".
First thing first I believe that the problem is arising from the Media Scanner getting force closed when it tries to scan a file with "corrupt" data or filename (it's probably not a corrupt file as such and the problem probably lies with the Media Scanner itself. Hopefully Google will fix it soon).
What I did was first putting a .nomedia file in every folder in the /mnt/sdcard directory. Basically this will tell the Media Scanner not to scan the content of any of the folders. Now wipe the data for Media Storage (I also wiped the data for the Gallery and Music apps just to be safe) and then restart the phone. Now if my theory is correct then you won't get a android.process.media force close.
(Also to add the .nomedia files I used an app called Super Manager which you can get on the market. Maybe you can do it with other file manager apps too. Normally you can also do this by plugging the phone into a computer but it seems that with MTP not all of the folders will show up.)
Now you can remove the .nomedia file from the folders that you have musics/pictures/videos/ringtones/notifications in one by one. Once you remove the .nomedia file from one folder, reboot and make sure you don't get a force close, then repeat the same thing for the next folder until you have all the folders you store media files in. If at any point, you reboot and get a force close then you know where the problem file is stored. Personally I didn't find the file that was the problem (it was probably in one of the folders that I left a .nomedia file in) but if you do then I guess you can try backing up the content of that folder, deleting it and copying it back to the phone again. Don't forget to wipe Media Storage again, reboot and see if that fixes the problem.
Hope that's useful!
Click to expand...
Click to collapse
I have to tell that through your solution, I found mine (that was for JellyBean).
Thanks for it! I'll spread your word.
While surfing in chrome, every time I see a picture that I like I usually long tap on it and save it to my phone. For the past month or so it will successfully download the picture,but it will also automatically name the file "images.bin". I can go in with root explorer and rename the file to the correct file extension and everything will be fine...... so it's not a game changer....more of an aggravation. When I use the built in browser it works just fine...so it appears to be an issue with how chrome handles getting files from the web.
Just wondering if anyone else has had this phenomena.
thanks.
info -
AOKP rom 4.1.1
1.0.40 franco kernel
chrome browser for android
As I face this issue, I did a huge search to find the solution, Tried full wipe, custom kernel to disable logger, sdrescan. ....etc...
Finally, I'm quite sure the problem,
1. Rom manager fail update, they put .nomedia at root .
Just uninstall it, and reintall it from market, they fixed it as well.
And the very important second things I found,
2. 360 Camera's Photos! !!!!!!! They make a bad jpg header, u can view it in explorer or file manager but, in ics and jb, media scanner just cause repeating scanning!!!!!
Please, don't use camera 360 and uninstall it after they known fix it
Use any file explorer, rename all C360*.JPG to C360.bak in dcim\camera folder
Or search all c360*.jpg zip them and delete all the jpg named c360 in front.
Clear mediascanner settings in application.
Reboot, after 2 to 3 mins,access gallery. Or play music, u will be happy as well.
Sent from my Galaxy Nexus using xda app-developers app
I used to be able to but haven't done so since March/April on account of the summer holidays but with school having now started again I need to download pdfs.
Basically I tried yesterday to download a pdf, the first red flag was that it wouldn't let me change the destination to the external storage, the external sd card wasn't showing as if there wasn't one in. I thought little of this thinking I'll just move it later.
Once downloaded however it won't move (using ES file explorer) and won't open, Adobe says its not a valid PDF document. I can download and open etc. on my phone (2011 Note). And I also managed to download the file on my computer and transfer it via USB, this also works no problem, I can open it and move it around etc. on the tablet.
I've tried a few files multiple times and the same thing is happening so I don't think its a case of the download being incomplete.
I'm using Dolphin and the firmware updated a few days ago.
Any ideas?
Thanks.
@dtst Have you tried deleting and downloading adobe again?
If its not a personal pdf document I will happily try download it from my tablet to test it. I kniw for certain I can download files no problem as I downloaded loads of PDF files a few weeks back.
Yeah uninstalling/reinstalling Adobe didn't work.
Thanks for the offer unfortunately its on the colleges moodle site so I can't link it.
I've had issues with pdfs that had copy protection on them, I couldn't save them or move them
Should have tried this earlier tbh but it seems to be a problem with Dolphin.
I have successfully downloaded the same pdf using Chrome, Opera and the stock browser just annoying since Dolphin is my preferred browser and the others don't give the option to change destination on a file by file basis (afaik).
Hopefully this will be fixed in an update by Dolphin but for now its just a minor inconvenience.
Also ES file explorer seems to have a problem, when I try moving the newly download file it fails, again the stock file explorer is moving the files fine. Hopefully this too will be fixed soon.
I'm just glad I can download files to my tablet in class now without having to wait to use my laptop and transferring later.