Develop Bugs

JellyBean SD Card issue

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!

[Q] [LINE] Can't use SD card. Please confirm SD card settings

Dear All,
This is my desperate attempt after days of googled with a dead end.
Recently, out of nothing i have encountered a major error after years. It all of sudden. Bombarded with "google play service is stopped" then decide to reboot then never up again with "acore stopped working'' on the very first screen after samsung logo where you have unlock the screen.
I did wipe data/factory reset. All good. reinstalled all essentials. SuperSU and Rootchecker report im still rooted. Then noticed LINE app (by Naver) has a bizarre behavior. All image related operations is not working with message "Cant use SD card, please confirm SD card settings"
All other chat messengers all working flawlessly (BBM, Whatsapp, you name it) but this one. To be detailed, affected operations are downloading stickers, themes, chat image attachments, chat photos wont came out, trigger camera, attach/send photo..
Submit a ticket to Naver but returned with they have no support for rooted device.
Device detail:
N7100 4.4.2 (rooted)
SuperSU / Knox disabled
modified platform.xml (extsdcard write access)
Failed Attempts:
- format ext SD card from inside, issue still exist
- install / reinstall LINE app, issue still exist
any kind of idea/helps would greatly appreciated as most of my contacts and communication are mainly using this app. I hope you guys have knowledge to be shared for pinpoint the issue based on the error message above. I believe the solution can be a great value as there are currently none in the net.
Thanks

try to apply kitkat sdcard fix
click

I have the Xperia Z3 running on Lollipop.
Same issue, all apps such as whatsapp, fb, etc can access the SD card except for line.
The error message when trying to send a photo to someone in Line is "Can't use SD card. Please confirm SD card settings"
Reinstalled the app several times, unmounted and remounted the SD card, even moved the app to the SD card with the app itself still working fine. But still cannot send or receive photos or download stickers.
Also applied the suggested that sd card fix even though it wasn't really needed since all other apps can access the SD card just fine..anways it didn't help.
Any other ideas?
Oh yeah, even tried installing a Line version which was 6 months old - didn't help either.

mcdimm said:
Dear All,
This is my desperate attempt after days of googled with a dead end.
Recently, out of nothing i have encountered a major error after years. It all of sudden. Bombarded with "google play service is stopped" then decide to reboot then never up again with "acore stopped working'' on the very first screen after samsung logo where you have unlock the screen.
I did wipe data/factory reset. All good. reinstalled all essentials. SuperSU and Rootchecker report im still rooted. Then noticed LINE app (by Naver) has a bizarre behavior. All image related operations is not working with message "Cant use SD card, please confirm SD card settings"
All other chat messengers all working flawlessly (BBM, Whatsapp, you name it) but this one. To be detailed, affected operations are downloading stickers, themes, chat image attachments, chat photos wont came out, trigger camera, attach/send photo..
Submit a ticket to Naver but returned with they have no support for rooted device.
Device detail:
N7100 4.4.2 (rooted)
SuperSU / Knox disabled
modified platform.xml (extsdcard write access)
Failed Attempts:
- format ext SD card from inside, issue still exist
- install / reinstall LINE app, issue still exist
any kind of idea/helps would greatly appreciated as most of my contacts and communication are mainly using this app. I hope you guys have knowledge to be shared for pinpoint the issue based on the error message above. I believe the solution can be a great value as there are currently none in the net.
Thanks
Click to expand...
Click to collapse
I have the exact same issue after a full wipe and re-flashed custom ROM. The naver LINE app have the same issue as mentioned above. All other apps functions normal. Anyone found a solution to this yet?
HTC One M7
Vipeone sense-based ROM 9.0.0.

Hi. I've encountered a similar problem recently. The interesting thing is that my telephone does not have SD card at all. So my first thought was that the problem is in permissions or cache.
I checked the permissions - app had full access.
Then I cleared programm cache on my phone. both inner memory cache and telephone memory cache (at least that's what they are called in my native language)
After that I tried to upload the image, yet it gave another error. something like: "cannot perform the action now, try again later"
I was quite short on the inner memory on my phone (around 70 MBs free), and thought it can be the problem. I deleted the biggest app and was able to upload the screenshots again.
Probably worth mentioning: I did not reinstall the Line app.
My device:
Telephone called ImSmart C471. China at it's best. Assembled in Ukraine though, company called Impression.
Android 4.4.2

In the latest build, Line apk cant send photo from internal/sdcard..it said line cant use sdcard..?

i had the same problem when i moved to new phone ( Xiaomi Mi4 ). I solved that. Just find the application permission setting in application manager. Try to find permission to stroarge. Change the permission to allow. That's it. That worked for me.

where's the settings?
andrew_susanto said:
i had the same problem when i moved to new phone ( Xiaomi Mi4 ). I solved that. Just find the application permission setting in application manager. Try to find permission to stroarge. Change the permission to allow. That's it. That worked for me.
Click to expand...
Click to collapse
I can't find any setting for permission to storage from the application manager, is there any? did I overlooked?

Try updating the app in play store. I had the same issue but solved with the updated version.

I had the smale problem. I deleted some pictures and videos and then restarted the phone. Works like magic

android.process.media keeps stopping - so annoying

Dear all,
I have been using RMN5 for a while and this is the most f**cking annoying error in this phone (or MIUI's error - i got it in my LG F180L running MIUI7 a long time ago and it happened too)
Every time i connected the phone to PC, i got this problem, I've followed the tips on XDA about disable media storage and download (force stop only in RMN5) and reboot, ok it fixed for a while, but not for long, next time i connect, it happen AGAIN.
I'm so tired of this sh*t and want to get rid of it.
Please, somebody please show me the way.
Thank you

Don't disable those apps instead go to the app settings media storage and download and clear both cache and data, hopes this will solve the problem and move this post to question and answer thread. It belongs there.

you disabled critical system app and complained why you get error messages

This is the Android Media Scanner, looking for files to index on your storage.
Some options are:
Try creating a file called '.nomedia' in every folder, and the problem should dissapear. In that case you may have a corrupted file somewhere, so try to delete the .nomedia file in some of the suspected folders to see if the problem comes back (or google something like 'android.process.media .nomedia' for a better explanation or solution.
You can also enable debuggind (via developer options), to inspect the problem with adb logcat, or to install a logcat related app from Play Store, in case the dump that should appear at the time of the error contains some hint.

rgawenda said:
This is the Android Media Scanner, looking for files to index on your storage.
Some options are:
Try creating a file called '.nomedia' in every folder, and the problem should dissapear. In that case you may have a corrupted file somewhere, so try to delete the .nomedia file in some of the suspected folders to see if the problem comes back (or google something like 'android.process.media .nomedia' for a better explanation or solution.
You can also enable debuggind (via developer options), to inspect the problem with adb logcat, or to install a logcat related app from Play Store, in case the dump that should appear at the time of the error contains some hint.
Click to expand...
Click to collapse
I'm having this issue after updating my Samsung GT-N8013 to lineageos 16.0. When you say to put a .nomedia file in every folder, do you litterally mean every single folder on both the tablet and sd card or a certain level of folder?

tcfulmer said:
I'm having this issue after updating my Samsung GT-N8013 to lineageos 16.0. When you say to put a .nomedia file in every folder, do you litterally mean every single folder on both the tablet and sd card or a certain level of folder?
Click to expand...
Click to collapse
The .nomedia flag file will stop the scan in the directory it's placed and all of the directories contained in it.

I ended up reinstalling the the OS 16.0 rom for my Samsung N8013. It took a total of running the installation 3 times but it finally became stable.

[Q] SDCard write issue with 3rd party apps (0 byte files)

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

Cann't install apps anymore on Pixel 2XL

Hello all,
I cann't find a solution to install apps in sideload on my Pixel 2XL.
It was after flashing version 10 in the beginning of september.
After a lot of trying I give up and hope someone else here can help me.
My Pixel 2XL is unlocked but not rooted.
Normally I do the sideload by transfer an apk to my dropbox. After that I start it up and do what the system tells me.
Nowadays I got a return of a message in dropbox that -it is impossible to open the apk and download an app to open the apk-.
After that I download the apk to my download folder to try again. Then, when trying to startup, I get a popup with the name off the apk, the version nr, the size and packagename.
There is also a button to view apk content. When I push that button the right folders of the apk are indeed visible.
There are also 3 options. One to install, one to go to playstore and one to stop further actions and go back.
When I try to use the button install the result is that nothing happened, no signal, no message from the system, no popup, really nothing.
You all know that this is not what I want. I just want to install the apk. I have tried it with a few other apk's with the same results. :crying:
Before the last OTA upgrade to android 10 it was normal to install with these methods.
Thanks for who can helping me and others for trying to help me.
Greetings.

retaliator said:
Hello all,
I cann't find a solution to install apps in sideload on my Pixel 2XL.
It was after flashing version 10 in the beginning of september.
After a lot of trying I give up and hope someone else here can help me.
My Pixel 2XL is unlocked but not rooted.
Normally I do the sideload by transfer an apk to my dropbox. After that I start it up and do what the system tells me.
Nowadays I got a return of a message in dropbox that -it is impossible to open the apk and download an app to open the apk-.
After that I download the apk to my download folder to try again. Then, when trying to startup, I get a popup with the name off the apk, the version nr, the size and packagename.
There is also a button to view apk content. When I push that button the right folders of the apk are indeed visible.
There are also 3 options. One to install, one to go to playstore and one to stop further actions and go back.
When I try to use the button install the result is that nothing happened, no signal, no message from the system, no popup, really nothing.
You all know that this is not what I want. I just want to install the apk. I have tried it with a few other apk's with the same results. :crying:
Before the last OTA upgrade to android 10 it was normal to install with these methods.
Thanks for who can helping me and others for trying to help me.
Greetings.
Click to expand...
Click to collapse
Have you enabled install apps from unknown sources? You'll also need to enable apps to install apps from what I can see in android 10. If you pull up an apps indignation you can expand the options and there will be an option to allow it to install apps, which Dropbox may need. The first one needs to be enabled to install apks from the download folder.

wgrant said:
Have you enabled install apps from unknown sources? You'll also need to enable apps to install apps from what I can see in android 10. If you pull up an apps indignation you can expand the options and there will be an option to allow it to install apps, which Dropbox may need. The first one needs to be enabled to install apks from the download folder.
Click to expand...
Click to collapse
Thanks for helping me.
I did all these settings before.
Now I tried to open another filemanager (Google Files) and that did the job.
I don't know why installing in dropbox or installing in es file explorer doesn't do the same with equal settings.
Maybe an idea to uninstall and re-install these apps?
Anyway, a lot of thanks for your answer.
grts

retaliator said:
Thanks for helping me.
I did all these settings before.
Now I tried to open another filemanager (Google Files) and that did the job.
I don't know why installing in dropbox or installing in es file explorer doesn't do the same with equal settings.
Maybe an idea to uninstall and re-install these apps?
Anyway, a lot of thanks for your answer.
grts
Click to expand...
Click to collapse
Android 10, install from unknown sources is like an app permission now, you have to grant it to things like chrome (download apk and install) and file managers rather than a global setting for phone. Safer as you trust an app o do it rather than letting some malware in background filling your phone with crap.

retaliator said:
Maybe an idea to uninstall and re-install these apps?
Click to expand...
Click to collapse
Uninstalling and reinstalling will not work, as I've done that with my modded version of ES File Explorer. This is a change in Android itself.
Go to Settings > Apps & Notifications > Special App Access > Install Unknown Apps. A list of apps will appear. Select an app and toggle the switch.
NOTE: Dropbox is on the list, but at least on my device my modded version of ES File Explorer is not.