Related
Wondering if anyone can help...
on JB, stock google apps and system apps won't recognize my SD Card at all, while outside apps have no problem recognizing it...?
for example, stock Gallery app won't bring up my pictures, however Quick Pic has no problem. Root Explorer has no problem, Titanium Backup has no problem...but trying to access music or custom notifications for gmail/sms won't show up in the system apps (gmail, mms, etc).
another thing is when I plug my phone into my computer, none of my old files are there (but like I said they show up just fine with Root Explorer or any other file explorer).
I've tried every JB Rom available for Toro, yes I've tried SuperWipe, I've done it all.
Any ideas, fellas? Any help would be greatly appreciated. Thanks
philsfan said:
Wondering if anyone can help...
on JB, stock google apps and system apps won't recognize my SD Card at all, while outside apps have no problem recognizing it...?
for example, stock Gallery app won't bring up my pictures, however Quick Pic has no problem. Root Explorer has no problem, Titanium Backup has no problem...but trying to access music or custom notifications for gmail/sms won't show up in the system apps (gmail, mms, etc).
another thing is when I plug my phone into my computer, none of my old files are there (but like I said they show up just fine with Root Explorer or any other file explorer).
I've tried every JB Rom available for Toro, yes I've tried SuperWipe, I've done it all.
Any ideas, fellas? Any help would be greatly appreciated. Thanks
Click to expand...
Click to collapse
have you logged in to your account??? Cause I know sometimes if you are not logged in then your stock photo gallery will not show your photos....as far as not seeing them in your pc I don't know you might be shif out of luck cause if they are not there they not be there at all
Sent from my Galaxy Nexus using Tapatalk 2
Same issue here....looking for a solution...
The files are definately there...I can open them from the device but not via USB and not using Gallery. Its as though its a permission issue but I ran a fix permissions using ROM Manager but no joy....
having the same issue too. hope to get solution soon.
aidanbree said:
Same issue here....looking for a solution...
The files are definately there...I can open them from the device but not via USB and not using Gallery. Its as though its a permission issue but I ran a fix permissions using ROM Manager but no joy....
Click to expand...
Click to collapse
logged in.
files are definitely still there bc, as i said in OP, I can view them with Root Explorer and other file managers. Only with stock apps and system apps it seems to not see them.
i think it's a media server issue but i'm not educated enough on how to fix it
aidanbree said:
Same issue here....looking for a solution...
The files are definately there...I can open them from the device but not via USB and not using Gallery. Its as though its a permission issue but I ran a fix permissions using ROM Manager but no joy....
Click to expand...
Click to collapse
Try this.
Hi efrant
Thanks for the suggestion. Gave it a go (tried it twice) but unfortunately it hasn't made any difference.
I'm having the same problem... I did notice that not everything under /data/media had media_rw as the owner/group but fixing it didn't fix the media server issue.
It's definitely a media server issue though as from what I've read it's responsible for listing the files when connected via MTP/USB so I haven't found a fix for it.
I've always thought MTP was flaky. I use ADB to transfer any files back and forth.
Downloading any SDCard rescan app doesn't seem to work... but what I have noticed that if you go to Settings -> Apps -> Running and look under Media, you should see that the service is stuck in the restarting state...
I/ActivityManager( 336): Process android.process.media (pid 2148) has died.
W/ActivityManager( 336): Canceling start item Intent { cmp=com.android.providers.media/.MediaScannerService (has extras) } in
service ComponentInfo{com.android.providers.media/com.android.providers.media.MediaScannerService}
W/ActivityManager( 336): Canceling start item Intent { cmp=com.android.providers.media/.MediaScannerService (has extras) } in
service ComponentInfo{com.android.providers.media/com.android.providers.media.MediaScannerService}
W/ActivityManager( 336): Scheduling restart of crashed service com.android.providers.media/.MediaScannerService in 1440256ms
W/ActivityManager( 336): Scheduling restart of crashed service com.android.providers.media/.MtpService in 5000ms
I/ActivityManager( 336): Start proc android.process.media for service com.android.providers.media/.MtpService: pid=2249 uid=10013 gids={1015, 1023, 1024, 1028, 2001, 3003, 3007}
Click to expand...
Click to collapse
Sejanus,
Mine is restarting too.
I have noticed that if I use a file manager to duplicate an old file (e.g. photo) then I can access it...It looks like some sort of weird permission issue although I have tried all sorts of things to sort the permissions.
I'm using the GNex Toolkit V7.0 to pull everything from my virtual SD card /sdcard and then I'm going to delete everything, reboot, then push everything back to it, reboot, then see if that fixes it.
efrant said:
Try this.
Click to expand...
Click to collapse
I just tried, and it didn't work. Double checked, there was no file with a different user/group.
It seems that now my Media is not restart anymore, however I still can't see my files, neither through Google Music / Galery (although some show up), nor using USB to computer (only a few folders show up).
Therefore, nothing yet.
Any clues guys ?
Probably a solution! (at least it did work for me)
Guys, for those having issues with Media process, where Pictures & Musics don't show up, here's the solution that worked for me:
I got it from http://forum.xda-developers.com/showpost.php?p=21746289&postcount=2 (thanks Chrono_Tata).
Based on what Chrono_Tata wrote, I decided to create a ".nomedia" file in my main personal directory, where contains pictures, musics, personal files and so on.
(For those not familiar with Linux, the ". (dot)" in the beginning of the filename is very important! It means that it's a hidden file. You can create it through ES File Explorer)
For testing purposes, I copied some musics / pics to directories out of that my structure.
Then, stopped and cleaned data for: Gallery, Google Music and Media . Afterwards, restarted phone.
Bingo. It did work, and I could see the pics/musics outside my main directory (although it takes a while to re-scan everything, so wait! Gallery and Music will show nothing until scan is complete).
Well, after I realized it did work, I continued in the following way:
1) Delete the previous ".nomedia" file that I created
2) Create a new one under some sub-directory.
3) Repeat process for re-scan
I did it until I found which directory had an issue (btw, my pictures directory).
I think it might be related to thumbs.db file created by Win, but I'm not sure. Anyway, I still have to check carefully my structure to find the issue.
Hope it helps.
Regards,
Adriano.
Nice one!
For some reason the same worked with me. I seemed to have some 0k files that were perhaps causing issues. I used your process to clear things out.
Thanks Adriano!
aidanbree said:
Nice one!
For some reason the same worked with me. I seemed to have some 0k files that were perhaps causing issues. I used your process to clear things out.
Thanks Adriano!
Click to expand...
Click to collapse
Basically resolved this by
1) Creating a new directory in /sdcard/DCIM and moved all photos from /sdcard/DCIM/Camera to this directory
2) Placed .nomedia files in almost every directory in /sdcard except the obvious ones (/sdcard/DCIM/Camera being one of them)
3) Copied a months worth of photos from /sdcard/DCIM/Camera_bkup to /sdcard/DCIM/Camera, rebooted the phone, checked the gallery to see if all the photos now appeared
4) Repeated until /sdcard/DCIM/Camera_bkup was empty... in the process I removed a bunch of older pictures that were legacy from a non-Android cellphone that I copied over from my first phone
This was after I fixed the media_rw/media_rw permissions that I found as when I used the GNex Toolkit to dump my SDCard and then tried to restore it, all the files had root/root user/group permission set.
There was also an issue with timestamps of some photos where they were actually placed in the future by a few days, which was annoying because as I slid back from a picture I had just taken to the gallery it would show me some other picture then the one I had just taken. This got resolved as the wrong timestamped photos entered the past.
I was on an MCR JB build... I hope I don't have to go through all these hoops when CM10 comes out.
efrant said:
I've always thought MTP was flaky. I use ADB to transfer any files back and forth.
Click to expand...
Click to collapse
It definitely is. I'll have files missing from the MTP listing, but when I go in and look on my phone, the files are clearly there. MTP is janky at best.
This has been driving me nuts, since when the I/O update came out I flashed and had the same issue, just reverted to AOKP from nandroid.
I have partially fixed the issue by going into Recovery and fixing permissions, now I can see and select ringtones and most my camera pictures. Still many files are not showing on gallery, but I guess its progress .
Edit: Forgot to mention that I tried 4.1.1 and still had the issue, I just reverted to a nandroid b/u of ICS.
i think this issue is caused because the storage is named "sdcard0" the normal should be "sdcard" i tried to change the storage name but "sdcard0" is reed only, so i can't change the name with root explorer maybe someone can try to rename it and see if this issue will be fixed.
any thing let us know because this issue is being annoying.
raidy said:
i think this issue is caused because the storage is named "sdcard0" the normal should be "sdcard" i tried to change the storage name but "sdcard0" is reed only, so i can't change the name with root explorer maybe someone can try to rename it and see if this issue will be fixed.
any thing let us know because this issue is being annoying.
Click to expand...
Click to collapse
Having the same issues... wasting the WHOLE day troubleshooting this issue w/o any luck so far... I think I will end up going back to ICS and be happy with it until a solution is apparent. So annoying...! Jelly Bean is sooo fast!
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
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!))
Issue:
When using Open Camera, ES File Explorer or Amaze file explorer files are created with zero bytes. i.e. Copying a file will create a 0 byte file or if file storage location set to the SDCard, the Open Camera app will fail to record video or take pictures.
Initially write operations on the SDCard did seem to work for a while (recorded one video before fail using Open Camera and copied files across without errors).
All operations are fine on internal memory.
There is no issue using the built-in file manager and camera apps. Will update as I check though other apps affected by this.
Setup:
The phone was on MIUI 9, then updated to the MIUI 10 OTA update (from beginning of Oct2018):
GLOBAL Version 10.0.1.0 (OEDMIFH)
Android 8.1.0 OPMI.171019.019
Kernel 4.4.78-pref-ge3e6edb
I then performed a factory reset from the boot recovery before installing everything from my previous phone. I didn't try MIUI 9 with an SDCard.
System Apps and Apps up to date.
I then started with the SDCard (128GB Class 10) cleanly formatted on PC, FAT32, and then when inserted into the phone formatted again. Looked for option to mount as Internal Storage, but noted that this isn’t available on this device (probably for the best), and no obvious option for encryption???
Troubleshooting:
Initially I thought, OK failed SDCard (this was before I found built-in apps worked OK). So I removed the card formatted it and checked using a test program to write/verify the whole card and it checked out OK. Still same issues back in the phone.
Next I pulled SDCard from another phone and tried that, and I get the very same issues. Thinking less likely it is a failed SDCard now, perhaps it is a hardware issue with the phone. Although it did write some files before.
After reading a few places, mention of an issue on MIUI 9 but this was fixed in later update. The steps don't match with anything in MIUI 10.
There is also mention of a bug with Android Orio which is similar, where apps need Storage permissions. Checked and I'd given the apps this permission and I had.
Following this, I tried the standard apps (Camera and File Manager) and discovered that these wrote files without errors (using the very same files which fail before/after on the other apps). Right so looking less like a hardware issue (hopefully!).
For ES Explorer, first time you write to the SDCard you have to select the SDCard root (“Please choose the root directory (XXXX-XXXX) of ext-SDCard…”). In this step, the SDCARD is referred to as BOOT and ES Explorer mounts it with the ID of SDCARD. The internal memory is mounted as /storage/emulated/0 and the SDCard as /storage/XXXX-XXXX/.
Additional testing with the apps, has shown that the data is actually written by ES Explorer since the 0 byte file shown in ES Explorer after a copy, is the correct size and opens from the standard file manager. This is further confirmed when performing a reboot or remount of the SDCard, ES Explorer then reads the file as it should… Any file copied/moved by the standard file manager is shown and works correctly, even from ES Explorer.
I get just the same behaviour with alternative file explorers such as Amaze. Also I think many of the other apps suffer from the same issue since they can't open the 0byte photo or video until there is a remount/reboot.
With regards to Open Camera, this has the option to Use Storage Access Framework, which I think I had to enable for it to select the SDCard for storage (otherwise I think it returned a “serious error” when a few seconds into recording). I suspect something similar is happening on this app, but perhaps not consistently. As mentioned before, the first time I noticed a problem was after it had recorded a video (which was fine) and the next one I recorded was 0 bytes. The fact that it recorded without complaining, in retrospect, suggests to me that it was only reporting 0 bytes for the file (and if I’d remounted the card I would have the video OK) – since it’d have to been writing the data somewhere.
So it may be that the issue isn't writing to the SDCard, but correctly reading the data afterwards without remounting the SDCard (or reboot).
I've noticed there is a new version of MIUI 10 released yesterday, so may pick that up to see if it magically solves things (nothing mentioned on change log).
Questions:
Anyone else experienced anything similar? Ans: Apparently yes, it is a "feature", aren't we lucky.
Am I missing some special setting? Ans: No.
Any thoughts on what the issue could be or if there is a fix? Ans: It can be fixed using root magisk.
Are your mount points similar/different? Ans: Guessing not and isn't related to the problem.
Did you do a factory reset after update (one possibility is that whatever made it work in MIUI 9 remained for most people if they didn't factory reset)? Ans: Not the cause of the problem.
Thanks
meltwater.
i thought i was the only one with zero bytes files. and when you transfer them back- all good
The only way I could find an alternative solution was to install "ExSDCard Access Enabler" module in magisk.
Then point the direction to /mnt/media-rw/XXXX-XXXX/* and you can carry on as usual.
But this only works for apps that allow you to enter or select a path where you can enter the directory path by typing or open a gui to browse to this directory.
Or a file manager such as Root explorer, just go back back back to / directory and go to /mnt and you'll find the folder from there.
Apps such as OpenCamera when selecting the save path you can manually either enter this path or choose to use the Android framework to go to this folder.
But if the app only has an option to "save to external sd card" it assumes the sdcard is mounted to /storage/XXXX-XXXX/* with write permissions.
A bit of a shame..but I don't use any apps that asks for this permission so I can live with it.
I like to mention that this behavior is the same on Treble roms too, Pie or Oreo.
dvijetrecine said:
i thought i was the only one with zero bytes files. and when you transfer them back- all good
Click to expand...
Click to collapse
Awesome, helps to know it isn't something terminal. Will update if I manage to get to the bottom of it.
SUPERUSER said:
The only way I could find an alternative solution was to install "ExSDCard Access Enabler" module in magisk.
Then point the direction to /mnt/media-rw/XXXX-XXXX/* and you can carry on as usual.
But this only works for apps that allow you to enter or select a path where you can enter the directory path by typing or open a gui to browse to this directory.
Or a file manager such as Root explorer, just go back back back to / directory and go to /mnt and you'll find the folder from there.
Apps such as OpenCamera when selecting the save path you can manually either enter this path or choose to use the Android framework to go to this folder.
But if the app only has an option to "save to external sd card" it assumes the sdcard is mounted to /storage/XXXX-XXXX/* with write permissions.
A bit of a shame..but I don't use any apps that asks for this permission so I can live with it.
I like to mention that this behavior is the same on Treble roms too, Pie or Oreo.
Click to expand...
Click to collapse
Interesting, not come across it before, very odd behavior. Very glad I don't have to throw the card or return the phone.
I've seen magisk mentioned elsewhere, shall look into it. Does that require root? How easy is the Mi Max 3 to root? That sounds like that should be enough to make it work.
Also thanks for pointing out it is on other roms too, saves chasing down a fix through that. I assume then it does it on MIUI 9 too.
Thanks!
meltwater said:
Awesome, helps to know it isn't something terminal. Will update if I manage to get to the bottom of it.
Interesting, not come across it before, very odd behavior. Very glad I don't have to throw the card or return the phone.
I've seen magisk mentioned elsewhere, shall look into it. Does that require root? How easy is the Mi Max 3 to root? That sounds like that should be enough to make it work.
Also thanks for pointing out it is on other roms too, saves chasing down a fix through that. I assume then it does it on MIUI 9 too.
Thanks!
Click to expand...
Click to collapse
Magisk is the new "supersu" standard when it comes to root.
So it is the root per say. Yes you need root. But you root your phone by installing Magisk, its kind of a multi-tool.
You need to unlock your bootloader, if not already unlocked if you bought it that way like I did from Tradingshenzhen.
It will say Unlocked on the bootloader mi splash screen when you turn the phone on if the bootloader is unlocked.
And then you need to properly flash TWRP. Other than that you can stay on stock rom and use Magisk
Magisk thread https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
ExSDCard Write Access Enabler module thread https://forum.xda-developers.com/apps/magisk/module-exsdcard-write-access-enabler-t3670428
I see something I did not see before.
In the thread OP mentions:
Since the v3.3 ZIP version, a feature has been added especially for Oreo (Android 8) users, on this Android version, several special permissions can be used by any app.
For exemple, theses specials permissions are used to get access to reading logs, managing the power of the device.
If you want to use this special feature, you just have to follow theses easy steps:
- creating a simple file named "ExSDCard_Oreo_apps" in the module path, so: /sbin/.core/img/ExSDCard/ExSDCard_Oreo_apps (remove any extension).
- Write all the apps package names that require a special permissions, one by line, for exemple:
Click to expand...
Click to collapse
So with this you can apparently create custom rules for apps that don't support selecting the external SD card path.
Maybe you should look in to that and experiment
This bug happened across android 8.0 in various brand.
Since I familiars with ES File Explorer, I solved by root the phone, convert ES File Explorer into System app via Titanium Backup, then everything work perfectly fine. No more 0 bytes copy file.
ES File Explorer still work even I un-root my phone by uninstall Magisk.
If you're really not want to root your phone or any other reason. Just copy file that you want then restart your phone. Copied file will now become usable file.
My bootloader isn't unlocked and for now I'd rather avoid rooting my phone (may well do so later).
Good to know there are work-arounds, and that my device hardware is ok.
Will have an experiment and see if I can live with it until I have a go at rooting. Even if I do the temp fix of ES explorer.
Thanks for the info and tips.
Same **** for me. 1 year to solve this stupid bug and they dont have fix this **** yet
Say thanks to xiaomi[emoji108][emoji867]
Enviado desde mi MI MAX 3 mediante Tapatalk
Hmm i'm getting an SD card tomm for my Mix Max 3, i use the Asus File Manager. I wonder if that problem happnes with other file manager apps. Tried the Samsung Evo and another one and that 0byte bug there. No bueno.
Wmateria said:
Hmm i'm getting an SD card tomm for my Mix Max 3, i use the Asus File Manager. I wonder if that problem happnes with other file manager apps. Tried the Samsung Evo and another one and that 0byte bug there. No bueno.
Click to expand...
Click to collapse
Yep, looks like it is a solid bug. For now, I'm living with it and use the space I have on internal memory to transfer data to before using a System file manager to transfer to SDcard.
Been trying some app development and now found the "Install via USB" bug.
Again can work around it, but it does spoil debugging with Android Studio.
There are certainly some odd bugs on this phone, I suspect down to Xiaomi going "off plan".
meltwater said:
Issue:
When using Open Camera, ES File Explorer or Amaze file explorer files are created with zero bytes. i.e. Copying a file will create a 0 byte file or if file storage location set to the SDCard, the Open Camera app will fail to record video or take pictures.
Initially write operations on the SDCard did seem to work for a while (recorded one video before fail using Open Camera and copied files across without errors).
All operations are fine on internal memory.
There is no issue using the built-in file manager and camera apps. Will update as I check though other apps affected by this.
Setup:
The phone was on MIUI 9, then updated to the MIUI 10 OTA update (from beginning of Oct2018):
GLOBAL Version 10.0.1.0 (OEDMIFH)
Android 8.1.0 OPMI.171019.019
Kernel 4.4.78-pref-ge3e6edb
I then performed a factory reset from the boot recovery before installing everything from my previous phone. I didn't try MIUI 9 with an SDCard.
System Apps and Apps up to date.
I then started with the SDCard (128GB Class 10) cleanly formatted on PC, FAT32, and then when inserted into the phone formatted again. Looked for option to mount as Internal Storage, but noted that this isn’t available on this device (probably for the best), and no obvious option for encryption???
Troubleshooting:
Initially I thought, OK failed SDCard (this was before I found built-in apps worked OK). So I removed the card formatted it and checked using a test program to write/verify the whole card and it checked out OK. Still same issues back in the phone.
Next I pulled SDCard from another phone and tried that, and I get the very same issues. Thinking less likely it is a failed SDCard now, perhaps it is a hardware issue with the phone. Although it did write some files before.
After reading a few places, mention of an issue on MIUI 9 but this was fixed in later update. The steps don't match with anything in MIUI 10.
There is also mention of a bug with Android Orio which is similar, where apps need Storage permissions. Checked and I'd given the apps this permission and I had.
Following this, I tried the standard apps (Camera and File Manager) and discovered that these wrote files without errors (using the very same files which fail before/after on the other apps). Right so looking less like a hardware issue (hopefully!).
For ES Explorer, first time you write to the SDCard you have to select the SDCard root (“Please choose the root directory (XXXX-XXXX) of ext-SDCard…”). In this step, the SDCARD is referred to as BOOT and ES Explorer mounts it with the ID of SDCARD. The internal memory is mounted as /storage/emulated/0 and the SDCard as /storage/XXXX-XXXX/.
Additional testing with the apps, has shown that the data is actually written by ES Explorer since the 0 byte file shown in ES Explorer after a copy, is the correct size and opens from the standard file manager. This is further confirmed when performing a reboot or remount of the SDCard, ES Explorer then reads the file as it should… Any file copied/moved by the standard file manager is shown and works correctly, even from ES Explorer.
I get just the same behaviour with alternative file explorers such as Amaze. Also I think many of the other apps suffer from the same issue since they can't open the 0byte photo or video until there is a remount/reboot.
With regards to Open Camera, this has the option to Use Storage Access Framework, which I think I had to enable for it to select the SDCard for storage (otherwise I think it returned a “serious error” when a few seconds into recording). I suspect something similar is happening on this app, but perhaps not consistently. As mentioned before, the first time I noticed a problem was after it had recorded a video (which was fine) and the next one I recorded was 0 bytes. The fact that it recorded without complaining, in retrospect, suggests to me that it was only reporting 0 bytes for the file (and if I’d remounted the card I would have the video OK) – since it’d have to been writing the data somewhere.
So it may be that the issue isn't writing to the SDCard, but correctly reading the data afterwards without remounting the SDCard (or reboot).
I've noticed there is a new version of MIUI 10 released yesterday, so may pick that up to see if it magically solves things (nothing mentioned on change log).
Questions:
Anyone else experienced anything similar?
Am I missing some special setting?
Any thoughts on what the issue could be or if there is a fix?
Are your mount points simlar/different?
Did you do a factory reset after update (one possibility is that whatever made it work in MIUI 9 remained for most people if they didn't factory reset)?
Thanks
meltwater.
Click to expand...
Click to collapse
no need for this post. erased.
I want know why xiaomi dont fix this ****?
Think that mi max 3 will die with this bug. Never buy a xiaomi phone more
jorgeepelos said:
I want know why xiaomi dont fix this ****?
Think that mi max 3 will die with this bug. Never buy a xiaomi phone more
Click to expand...
Click to collapse
Get a Mi Mix 2S
Wmateria said:
Get a Mi Mix 2S
Click to expand...
Click to collapse
Phone with 3 month since release and they dont solve bugs and i have to buy more expensive phones?
All xiaomi phones its ****, policies, comunity,software and bugs that the dont solve
And People like you its the problem=sh it comunity guys that likes get fuked the ass by xiaomi[emoji108][emoji6]
Enviado desde mi MI MAX 3 mediante Tapatalk
jorgeepelos said:
Phone with 3 month since release and they dont solve bugs and i have to buy more expensive phones?
All xiaomi phones its ****, policies, comunity,software and bugs that the dont solve
And People like you its the problem=sh it comunity guys that likes get fuked the ass by xiaomi[emoji108][emoji6]
Enviado desde mi MI MAX 3 mediante Tapatalk[/QUOTE.
It's people like you who make the community bad when you out your hatred in the forums or is not knowledgeable enough because main post talks about THIRD PARTY FILE MANAGER APPS not 1ST PARTY Xiaomi File Manger APP and thinks it's the end of the world on here and the Xiaomi forums. And trust me there is plenty of you people around pushing Devs and OP here by complaining when other people already stated the fact many times on a thread, and trust me, I hardly take offense. "Read", it works.
Click to expand...
Click to collapse
I've a Xiaomi Mi 10T Lite, but all my music and pictures get randomly removed all the time and then I need to download them again.
I don't remove them myself for clarity.
I guess the cleaner app removes it but there is no option to add them to exceptions and there is also no option to turn off auto clean.
This is a very annoying problem and I'm tired to download all my music and pictures over and over again so how can I solve this?
Googole said:
I've a Xiaomi Mi 10T Lite, but all my music and pictures get randomly removed all the time and then I need to download them again.
I don't remove them myself for clarity.
I guess the cleaner app removes it but there is no option to add them to exceptions and there is also no option to turn off auto clean.
This is a very annoying problem and I'm tired to download all my music and pictures over and over again so how can I solve this?
Click to expand...
Click to collapse
Maybe your device has something like "storage manager" active?
Go into settings and then storage, see if you find something suspicious.
Uninstall or disable cleaning app... you really need to play with your device more.
That cleaner app sounds more like malware
blackhawk said:
Uninstall or disable cleaning app... you really need to play with your device more.
That cleaner app sounds more like malware
Click to expand...
Click to collapse
I've found out that Cleaner is useless and is just a waste of space so I removed it.
I hope my problem is solved.
User699 said:
Maybe your device has something like "storage manager" active?
Go into settings and then storage, see if you find something suspicious.
Click to expand...
Click to collapse
I've made a screenshot of the Storage page.
Screenshot_2021-04-19-11-09-51-509_com.miui.securitycenter.jpg
drive.google.com
I don't know if it is suspicious but Other is 8,61GB
Removing Cleaner didn't solve my problem.
I download my music from Google Drive and all music downloaded from there is gone now.
The songs that I didn't download from Google Drive aren't removed.
The most of the pictures are removed too, but some didn't.
Googole said:
Removing Cleaner didn't solve my problem.
I download my music from Google Drive and all music downloaded from there is gone now.
The songs that I didn't download from Google Drive aren't removed.
The most of the pictures are removed too, but some didn't.
Click to expand...
Click to collapse
Well If so, have a look at gdrives settings.
Also: Are gdrive files in another folder than those not being removed?
Could be malware... you know odd behavior.
The OS or an app may have been corrupted.
A factory reset be a good idea at this point.
Self destructing files aren't normal.
Is it just Google stuff that's vaporizing?
If so maybe deleting/recreating your Google account might solve it.
I'm leaning towards a full nuke of that OS though.
I don't trust Google with any of my data management other than Gmail. I backup and load everything from the SD card, flash stick and hdds.
blackhawk said:
Could be malware... you know odd behavior.
The OS or an app may have been corrupted.
A factory reset be a good idea at this point.
Self destructing files aren't normal.
Is it just Google stuff that's vaporizing?
If so maybe deleting/recreating your Google account might solve it.
I'm leaning towards a full nuke of that OS though.
I don't trust Google with any of my data management other than Gmail. I backup and load everything from the SD card, flash stick and hdds.
Click to expand...
Click to collapse
True, could be malware.
A malware checking app would be a first step. If you can run adb on your computer you can check for modifications made on the file system (as you operate as "shell" instead of "root" (unless you are rooted) you won't be able to read everything. Actually you'll get "access denied" very often. But if you find system directories/files with another date then the 'standard recovery date' this could be a sign for malicous activity)
User699 said:
True, could be malware.
A malware checking app would be a first step. If you can run adb on your computer you can check for modifications made on the file system (as you operate as "shell" instead of "root" (unless you are rooted) you won't be able to read everything. Actually you'll get "access denied" very often. But if you find system directories/files with another date then the 'standard recovery date' this could be a sign for malicous activity)
Click to expand...
Click to collapse
There's another possibility, a malware jpeg.
I ran into two in the last 15 years, one a year ago on my N10+. Downloaded from a site into the download folder it corrupted many files in that folder. Some only had damage to the file name and were easily repairable, some were not.
Deleted all I couldn't repair or was in doubt about especially the tainted jpeg.
If that jpeg would have been moved to another folder the same thing would have happened.
The only way to stop this type of malware is to find the infected jpeg. It may not show up on many or any virus/malware scans. I found this one because I noticed the damage immediately after viewing it in downloads. If one one these gets in your database they are little nightmare. One reason I keep downloads in the Download folder for examination, especially jpegs, are these little nasties.
Not real common but they're out there.
blackhawk said:
Could be malware... you know odd behavior.
The OS or an app may have been corrupted.
A factory reset be a good idea at this point.
Self destructing files aren't normal.
Is it just Google stuff that's vaporizing?
If so maybe deleting/recreating your Google account might solve it.
I'm leaning towards a full nuke of that OS though.
I don't trust Google with any of my data management other than Gmail. I backup and load everything from the SD card, flash stick and hdds.
Click to expand...
Click to collapse
I've done a factory reset earlier but it didn't solve the issue.
All music and the most of the pictures downloaded from Google Drive are removed all the time.
User699 said:
True, could be malware.
A malware checking app would be a first step. If you can run adb on your computer you can check for modifications made on the file system (as you operate as "shell" instead of "root" (unless you are rooted) you won't be able to read everything. Actually you'll get "access denied" very often. But if you find system directories/files with another date then the 'standard recovery date' this could be a sign for malicous activity)
Click to expand...
Click to collapse
I'll check for malware and I'll let you know what the results are.
blackhawk said:
There's another possibility, a malware jpeg.
I ran into two in the last 15 years, one a year ago on my N10+. Downloaded from a site into the download folder it corrupted many files in that folder. Some only had damage to the file name and were easily repairable, some were not.
Deleted all I couldn't repair or was in doubt about especially the tainted jpeg.
If that jpeg would have been moved to another folder the same thing would have happened.
The only way to stop this type of malware is to find the infected jpeg. It may not show up on many or any virus/malware scans. I found this one because I noticed the damage immediately after viewing it in downloads. If one one these gets in your database they are little nightmare. One reason I keep downloads in the Download folder for examination, especially jpegs, are these little nasties.
Not real common but they're out there.
Click to expand...
Click to collapse
All my pictures are in the .jpg format
Create a folder in the root directory (not in any other folder) of your storage
In this folder create another two folders - one for music & one for pictures
Move all pictures & music to these folders
This will eliminate sync from apps deleting anything as they shouldn't have access to these folders
If they are still being deleted after this then the user is telling an app to delete them (intentionality or unintentionally)
TheFixItMan said:
Create a folder in the root directory (not in any other folder) of your storage
In this folder create another two folders - one for music & one for pictures
Move all pictures & music to these folders
This will eliminate sync from apps deleting anything as they shouldn't have access to these folders
If they are still being deleted after this then the user is telling an app to delete them (intentionality or unintentionally)
Click to expand...
Click to collapse
Thanks for your suggestion, I'll try it and let you know what the result it.
I've downloaded MalwareBytes, scanned my phone but it didn't find any malware @blackhawk
Googole said:
I've downloaded MalwareBytes, scanned my phone but it didn't find any malware @blackhawk
Click to expand...
Click to collapse
Since you said you did a factory data reset there must be an app somewhere which is responsible for that.
I would check Google Drive – I don't even have a google account so I can't check it, but maybe GDrive is deleting files automatically.
Is it ONLY GDrive files being deleted?
User699 said:
Well If so, have a look at gdrives settings.
Also: Are gdrive files in another folder than those not being removed?
Click to expand...
Click to collapse
I've looked at the Gdrive settings, but I couldn't find anything related to the problem.
The Gdrive files are on Google Drive and those not being removed and removed are in my internal storage.
User699 said:
Since you said you did a factory data reset there must be an app somewhere which is responsible for that.
I would check Google Drive – I don't even have a google account so I can't check it, but maybe GDrive is deleting files automatically.
Is it ONLY GDrive files being deleted?
Click to expand...
Click to collapse
I've checked the Google Drive settings but I couldn't find anything related to the problem.
Only files downloaded from Gdrive are deleted.
Files downloaded from other places aren't deleted.
Googole said:
I've checked the Google Drive settings but I couldn't find anything related to the problem.
Only files downloaded from Gdrive are deleted.
Files downloaded from other places aren't deleted.
Click to expand...
Click to collapse
And GDrive downloads them into Downloads folder?
If not you could try to move these things into another folder and see whether they will be deleted again or not.