hey guys
I had a bunch of pics that I received via MMS and I needed to use, so I just long click on it and selected to save do sd card. But when I connect the phone to the pc on mass storage mode, I can't find them anywhere.
So I installed the app SaveMMS and saved all the pics to a folder with the same name. Still nothing showed up when I connect the phone to my PC.
Using ASTRO, I can see all the pictures on the download folder and I can also access the SaveMMS folder (and actually some other folders that I cant see from my PC).
I tried to copy to somewhere else and even that didnt work.
I ended up emailing myself the pics...
Any idea on whats happening?
I got root and im using opendesire with a partitioned sd card (and no, there's no pictures on the ext partition).
many thanks
Does any file names or folders on your phone look like, for example, this ".hello"
If so, get rid of the full stop at the start of the name via Astro, as it will not show up on your computer
Thread moved to Q&A.
delete my post
thanks for the reply
the first thing I checked was for hidden folders, and it wasnt that.
the folders ended up showing up on the desktop as well, out of nowhere.
but it just seemed some random, dont know what was the issue.
This is usually because you are using a2sd which makes the SD card do strange things. Changes are only actually saved to the card for the computer to see when restarting the phone
The problem is well documented, and a fix have been made which should fix it
Well, its really weird.
But better weird with A2SD than normal without it ;p
Hi everyone,
In panic mode right now...
I downloaded an app that helps you find all your apps that can be moved to the sd card. So it found 150 or so. After an hour of manually moving each one, I had over 400mb of free internal space and only like 40 apps left on the main phone storage. Awesome... but then this morning I noticed that things were running real slow... so I rebooted my phone. When it came back up I noticed some of my home screen shortcuts had become generic android icons. I went to my launcher & lots of apps were missing. I have a LOT of apps so I can't quite confirm yet whether its all the apps I moved to sd but it seems that way.
When I go to the market I see apps that I had yesterday as not installed. I have astro but I'm not quite sure what folder to look in to see if the apps are all still there, just not being seen by the android system maybe?
I've been driving all morning so I haven't gotten to research this much yet. Just rebooted a couple times hoping to fix it but no luck yet.
Any help is majorly appreciated. As soon as I'm at a computer ill be working on this all day. Freakin disaster!
Dave
Sent from my T-Mobile G2 using XDA App
update to my question
so now that i'm in to work i can mess with this... quick update...
when i go to manage applications and go to "on SD card" i get a big list of apps that have the names like "cn.miren.browser" instead of Miren Browser and "com.alphonso.pulse" instead of Pulse which is kinda normal except usually they then refresh with the regular name and the size listed underneath. well it's been sitting here for 5 minutes now and hasn't change and it still says "Computing..." under each one and instead of the normal icons, its sort of a grayed out generic Android icon with an SD in the bottom right corner of the icon.
so clearly it still knows that these apps are there. it just maybe can't access them? i dont know. could it be the sd card? this is the original 8gb sd card that came with the g2...
any thoughts?
???
so i found out that the sd card had some errors in the file system. so i let windows fix the errors. no help (although my phone boots WAAAAAYYYYYY faster now).
so then i found that i have an extra 8gb microsd laying around (which also happened to be a better, class 6 one too). so i cleared it off and copied over alllll the files to it. booted up. STILL NO GO.
anyone have any ideas here? i'm really running out of ideas here.
when i boot, everything runs great, but all my apps that are installed to sd are gone. also it never says "preparing sd card" in the status bar when booting. then if i go to manage applications it never finishes "computing" the size of apps. if i go to "on sd" it shows all my apps, but says computing, and i can't access them, uninstall them, move them, etc. i'm totally out of ideas here and i really don't want to have to do a system restore.
anyone?
think im having the same problem . has ur market gone too?
fix?
ok so i ended up getting mine fixed using these steps that someone from a company that makes an apps2sd app sent me... the only difference i had to do was since my phone also wouldn't recognize my pc, i had to pop the sd card into my pc directly to delete the .android_secure folder... i don't want to mess up your phone or anything so make sure to read around a bit more before trying this, but this is what worked for me. after i started adding all my apps back one by one i've been fine ever since.:
"I guess the problem is ".android_secure" is not recognized by Android.
Would you try the following steps (I am not sure if it works)?
1. mount phone with PC
2. backup all files under .android_secure
3. delete .android_secure directory
4. unmount
5. try to move an app (any app) to SD card (it forces Android to
create .android_secure on SD)
6. mount phone with PC
7. restore all backuped .android_secure/* files to .android_secure
8. unmount => check if it recognized the apps that you moved to the SD card"
***SOLUTION FOUND! I CAN NOW ACCESS THE FOLDER. SEE POST BELOW.***
Android File Transfer was working great up until a few days ago when it started to bug out, only for when trying to access the Camera folder on my exSD Card.
I can access everything else except when clicking on this folder the message pops up, which makes no sense because my screen isn't locked. (Screenshot attached.)
Could it be that the amount of pictures/videos on the exSD card is too much to handle for AFT? After all, it is a 64GB card...which is a lot of land to cover and load....hmmmm
I've tried this, but no luck.
Note: I'm aware of AirDroid etc...Personally I prefer to be plugged in direct via USB.
iunlock said:
Android File Transfer was working great up until a few days ago when it started to bug out, only for when trying to access the Camera folder on my exSD Card.
I can access everything else except when clicking on this folder the message pops up, which makes no sense because my screen isn't locked. (Screenshot attached.)
Could it be that the amount of pictures/videos on the exSD card is too much to handle for AFT? After all, it is a 64GB card...which is a lot of land to cover and load....hmmmm
I've tried this, but no luck.
Note: I'm aware of AirDroid etc...Personally I prefer to be plugged in direct via USB.
Click to expand...
Click to collapse
Not really a theme Or app question but I'll give it a swing.
Can you access it on your phone fine?
Did you try using a card reader an see if you can access it that way?
If it's stating locked, it may have set permissions on your folder that inhibit access? Check those in a root explorer an see what they say too
Sent from my SM-N900T using Tapatalk 2
Mod, can you move this over to the proper forum. Thanks.
Possible causes / Things I've tried:
I do have some pictures in an App called: KeepSafe, where you have to enter in a pin code to access those pics, so then I was thinking maybe this was causing the problem. So I entered the App and tried connecting, but darn...same old thing. Doesn't work and I keep getting the same error message as the pic I have attached to the original thread.
I have also tried to reboot in Recovery (twrp) and tried to mount the exSD, but still nothing. Here's the message it gave me:
E: Unable to mount '/usbstorage'
This is driving me crazy. Anyone?
cbucz24 said:
Not really a theme Or app question but I'll give it a swing.
Can you access it on your phone fine? - Yes I can access it just fine through ES File Explorer. I've also checked the permissions.
Did you try using a card reader an see if you can access it that way? - I'm sure it'll work fine with a card reader, but that's not my preferred method. It's just frustrating for something to have worked and out of the blue stop.
If it's stating locked, it may have set permissions on your folder that inhibit access? Check those in a root explorer an see what they say too - I've uploaded a screen shot of the message that I'm receiving.
Sent from my SM-N900T using Tapatalk 2
Click to expand...
Click to collapse
Try moving the KeepSafe files to another directory.
Frank
Update 6/30/14
SUCCESS!
From the gallery on your phone, you can create folders and move (not copy) over pictures/videos and it'll be default save it to your phones internal SD card.
I didn't want to move all 4,000+ pics/vids so I just did it in little batches of 20 here 50 there and made just a few folders.
Then I connected the phone to my computer and accessed the Camera folder and....bam there it OPENS!
My theory:
If you have more than ~50% of your external SD card filled up then chances are your computer (Android File Transfer, for Mac users) will have a hard time trying to access that huge folder that is < 30+GB's ...
Therefore, you just have to lighten up the load on that folder so that it can be accessed with ease...
Pretty straight forward and simple.
Update 6/30/14
***SOLUTION FOUND! I CAN NOW ACCESS THE FOLDER. SEE POST BELOW.***
From the gallery on your phone, you can create folders and move (don't copy) over pictures/videos and it'll by default save it to your phones internal SD card.
I didn't want to move all 4,000+ pics/vids so I just moved about a couple hundred pictures to varies folders.
Then I connected the phone to my computer and accessed the Camera folder and....bam there it OPENS!
My theory:
If you have more than ~50% of your external SD card filled up then chances are your computer (Android File Transfer, for Mac users) will have a hard time trying to access that huge folder that is < 30+GB's ... (Windows wouldn't open it either.)
Therefore, you just have to lighten up the load on that folder so that it can be accessed with ease...
Pretty straight forward and simple. Hope this helps.
iunlock said:
My theory:
If you have more than ~50% of your external SD card filled up then chances are your computer (Android File Transfer, for Mac users) will have a hard time trying to access that huge folder that is < 30+GB's ...
Click to expand...
Click to collapse
It is more likely that they thought it very unlikely that there would be more than the old limit of 2,000 files in a directory so they didn't allow for it in the program code.
Frank
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