• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Problem with ES File Explorer

markdoc

markdoc

Android Expert
Lately (prior to Lollipop) I have had a problem with ES File Explorer (ES). I can move mp3 sound files in and out of my "Alarms" folders. The issue is when I move them in, they do not appear in any selection list on my phone. This includes my phones "Settings" and all apps. When I move the same files with other file explorers, they show up as expected. I wrote ES support 5 times and their last answer to creating new alarms was,
"Hi. If you want to add new ringtones,you should:
1.Root your device 2.Mount /system path as RW 3.put music files into /system/media/audio/alarms/"
Obviously, not a reasonable answer. The others were just as bad. If anyone else has/doesn't have the same problem, please let me know. A fix would be great too, but I believe it's in the programming.
TIA
 
possibly you have to reboot your phone after moving the files so they are detected as media files during startup scan. just a thought.
 
Many times a simple reboot will resolve the issue. As far as rooting and sticking them into the /system/media/audio/alarms folder you would still need to reboot before the system will see them.
 
Android doesn't rescan the media automatically. It only does so on system boot, or when it's forced to do so. Some file managers instruct the OS to rescan media after every file operation, others don't.

Look in the play store for an app that forces media rescan. There are many. Just search for "rescan media".

Good luck!
 
Thanks for the suggestions. Here is what I have tried so far and the results:
Uninstall & reinstall no good
Rebooted phone no good
Tried Media Re-scan no good
Rings Extended is for ringtones
Installed Androzip works fine
Installed X-plore works fine
It is strange that re-scanning and rebooting doesn't help when all the "File Explorers" show the mp3 file in the correct "Alarms" folder but "Settings" don't.
Normally I would uninstall ES File Explorer and find another app, but I've been using ES for 3 years and like it. It sucks that support doesn't want to recognize there's a problem. Is there any way I can put pressure on ES to fix it?
TIA
 
Last edited:
I am sorry for not including my phone. I was originally going to post in my phone's forum then decided here would be better. I have an HTC One M8 with Android 5.0.1 from Verizon. Thanks for reminding me. As far as forcing mediaserver, it did run when I used the re-scan app and (if I understand it's function) it must be running properly because when I use the other explorers, the mp3 files appear without an issue.
 
HTC uses "Sense" I would be interested to see if others with this phone are having this issue with ES. I have moved my ringtones and notifications several times through ES and can not repeat your issue with My Device (Google Nexus 5) I don't know but It could be a communication issue between ES and Sense and not ES and Android. If others of your device don't have the issue then you have another app that may be interfering.
 
I don't think it's an es file explorer problem. assuming the files have been moved into desired directory (maybe double check that you can play the moved files at their be location from within a file explorer) then es has done it's job, right?

I think you need to look at media scanning some more. some directories can be hidden from the scanning process if they contain a .nomedia file. there may be an app you check this.
 
If this problem started after the Lollipop update for your M8, have you done a backup, factory data reset, and restore?

If this is really about the typical Android caches being tangled after an OTA, we could be here for eternity while issue after issue crops up, if you haven't tried that yet.

No guarantees but a factory data reset is known to cure most post-OTA bugs ok.
 
followup to my previous message:
connect the phone to pc.
view the directory in pc file explorer.
find file .nomedia
delete file.nomedia
 
First, it's not about nomedia files. All the explorer's show hidden files and if there was a nomedia file, I'd have the same problem with the other explorers.
Second, the problem started before the Lollipop update. I know a reset may fix it. I just hate resetting my phone. It's not rooted so I can't do a complete backup. It's a struggle to get my phone just right, to start over is a real pain. Does anyone know of another explorer with multiple windows? I found X-plore, that has two, any others?
 
Thanks for the tip. I'm using X-plore while working on ES. I like "X", but it's a little clumsy moving and copying files. I just downloaded "Solid" to try. What didn't you like about "Solid"?
 
If ES successfully copies your file, then in my mind the problem must have to do with phone media service not "seeing" the file. Maybe the other explorer programs do more to help that media service notice the changes than ES file explorer does. This media business is a little unpredictable in my experience,

I did some experiments:
1 - Add file .nomedia with ES Explorer into my directory NOTIFICATIONS
2 - Observed that files in NOTIFICATIONS directory no longer show up in list of available notifications [EXPECTED]
3 - Delete .nomedia with ES File explorer and reboot
4 - Observed that files in NOTIFICATIONS directory STILL don't show up in list of available notifications [UNEXPECTED]
5 - Connect to pc - verify no .nomedia file present.
6 - Reboot and repeat observation 4... those files in my notification directory still don't show up in list of available notifications even though there is no longer any trace of .nomedia file in ES file explorer (showing hidden files) or on pc [UNEXPECTED, like item 4... and I'm starting to worry if I'm ever going to be able to restore my own custom notification files!
7 - Move my files to another directory. Delete NOTIFICATIONS directory. recreate NOTIFICATIONS directory. Copy my audio files back in.
8 - Observe that the sounds associated with files in NOTIIFCATIONS directory are now available to choose as notifications.

So my previous advice to check with pc was bad. I would suggest what I did.. copy the files to another directory, delete and recreate your notificaitons (or alarms or ringtones or whatever) directory. Copy the files back into the directory. Reboot. Your sounds should now be available to choose.
 
markdoc said:
Thanks for the tip. I'm using X-plore while working on ES. I like "X", but it's a little clumsy moving and copying files. I just downloaded "Solid" to try. What didn't you like about "Solid"?
Click to expand...
Absolutely nothing, I liked it.

At the time I gave it up, I was on a phone with less storage, I was running out of room and had to slim down.

I basically forgot about it after I got this phone on account of I forgot - remembered it when you asked the question.
 
Electricpete, thanks for all your work. Now I know it's not just me. One question, did you use ES for the entire procedure or did you use another explorer to delete "Notifications" and move things back. That's very important since the other explorers don't have a problem.
Vosg- Thanks for the suggestion. File Commander looks good, but it only has one window. I'm use to 3,4 or more with ES. FYI, "X-Plore" writes to external SD cards also. You just have to follow the instructions the first time you try. The same with "Solid". I just tried both. Maybe a new version.:)
 
Big thanks to EarlyMon for suggesting "Solid". It's got a lot of nice features. It is larger than the others I've tried, but worth it.
 
markdoc said:
Electricpete, thanks for all your work. Now I know it's not just me. One question, did you use ES for the entire procedure or did you use another explorer to delete "Notifications" and move things back. That's very important since the other explorers don't have a problem.
Vosg- Thanks for the suggestion. File Commander looks good, but it only has one window. I'm use to 3,4 or more with ES. FYI, "X-Plore" writes to external SD cards also. You just have to follow the instructions the first time you try. The same with "Solid". I just tried both. Maybe a new version.:)
Click to expand...
I used ES File explorer.

To my simple thinking, ES File Explorer does what I expect. The Android system does not. So the "fault" lies with Android not ES. But maybe I am missing something about the inner workings. And I understand as a practical matter someone might consider this a strike against ES if problem doesn't show up for other explorers.
 
You must log in or register to reply here.
Back
Top Bottom