Develop Bugs

[Q] Zimperium "Anti" appeared on Dinc over night

This morning I woke up, and Zimperium's "Anti" app was on my phone. I did not download it. I did not even know what it was until it was there.
I'm running MIUI ROM v. 1.11.18 on my Dinc. I just updated from 1.11.11 last night, however this application is not in their changelog.
I've never experienced this before, and the application is not listed as a downloaded application in the marketplace when I choose "My apps".
I have not downloaded any other applications within the past week.
Considering the nature of this application (Network toolkit) I am concerned it has unauthorized permissions.
Any recommendations?

usatf1290 said:
This morning I woke up, and Zimperium's "Anti" app was on my phone. I did not download it. I did not even know what it was until it was there.
I'm running MIUI ROM v. 1.11.18 on my Dinc. I just updated from 1.11.11 last night, however this application is not in their changelog.
I've never experienced this before, and the application is not listed as a downloaded application in the marketplace when I choose "My apps".
I have not downloaded any other applications within the past week.
Considering the nature of this application (Network toolkit) I am concerned it has unauthorized permissions.
Any recommendations?
Click to expand...
Click to collapse
if you have root explorer you can navigate to data/apps and manually delete it. i have no clue as to why it was installed on your phone without your permissions. that is a new one to me. talk to the MIUI supporter for our device and ask them.
---------- Post added at 11:36 AM ---------- Previous post was at 11:34 AM ----------
usatf1290 said:
This morning I woke up, and Zimperium's "Anti" app was on my phone. I did not download it. I did not even know what it was until it was there.
I'm running MIUI ROM v. 1.11.18 on my Dinc. I just updated from 1.11.11 last night, however this application is not in their changelog.
I've never experienced this before, and the application is not listed as a downloaded application in the marketplace when I choose "My apps".
I have not downloaded any other applications within the past week.
Considering the nature of this application (Network toolkit) I am concerned it has unauthorized permissions.
Any recommendations?
Click to expand...
Click to collapse
also if you still have the zip on your phone i would look through it and see if, for some reason, it was put in it by accident. if it came form the update then it would be in system > app

Our MIUI maintainer, leeech decided to put it in the latest update for the Inc only which is why it isn't in the changelog. If you don't want it, remove it with either Root Explorer or Titanium Backup.

I'm having a difficult time finding where this .apk is located. What's more interesting, is that the application is the FULL "Anti", not the "AntiLite" on the android market.
Also, I downloaded the MIUI from ROM manager, did a backup, dalvik cache wipe, and updated. I'll be able to upload that .zip here around 5 PM EST today.
The details of this app are as follows:
version: 2.3.1
size: 788KB
permissions: storage (modify/delete), net. comm.(full, and market billing service), phone calls (read phone state and identity), system tools (change wi-fi state, prevent phone from sleeping), and discover known accounts.
I'm not sure if that's helpful at all, but i figure the more details i give, the better possibility of an explanation.

usatf1290 said:
I'm having a difficult time finding where this .apk is located. What's more interesting, is that the application is the FULL "Anti", not the "AntiLite" on the android market.
Also, I downloaded the MIUI from ROM manager, did a backup, dalvik cache wipe, and updated. I'll be able to upload that .zip here around 5 PM EST today.
The details of this app are as follows:
version: 2.3.1
size: 788KB
permissions: storage (modify/delete), net. comm.(full, and market billing service), phone calls (read phone state and identity), system tools (change wi-fi state, prevent phone from sleeping), and discover known accounts.
I'm not sure if that's helpful at all, but i figure the more details i give, the better possibility of an explanation.
Click to expand...
Click to collapse
You won't be able to remove it from the Application pane in settings since it's in the system folder.
Like I said above, if you have Root Explorer or Titanium Backup, you can remove it. In root explorer, go to the /system/app folder and delete the filecalled "Anti-2.3.1-Miui.apk"
If you have Titanium Backup, just search for "Anti," click on it when it loads up in the list and click uninstall. It will ask if you are sure you want to remove a system app, just say yes, and voila, it's gone.

TheWhiteBandito said:
You won't be able to remove it from the Application pane in settings since it's in the system folder.
Like I said above, if you have Root Explorer or Titanium Backup, you can remove it. In root explorer, go to the /system/app folder and delete the filecalled "Anti-2.3.1-Miui.apk"
If you have Titanium Backup, just search for "Anti," click on it when it loads up in the list and click uninstall. It will ask if you are sure you want to remove a system app, just say yes, and voila, it's gone.
Click to expand...
Click to collapse
yeah what you said. or you can put the zip on your pc. use zip and remove the apk then flash the rom over. my way is harder but yea.

I just saw this app in my ROM as well. Haven't been on MIUI in a while but looks like a pretty interesting app if you do some research on it and are into hacking at all.
I'm thinking of giving it a go.

KlugN said:
I just saw this app in my ROM as well. Haven't been on MIUI in a while but looks like a pretty interesting app if you do some research on it and are into hacking at all.
I'm thinking of giving it a go.
Click to expand...
Click to collapse
Strange. I just found it on my phone too. It appeared after I installed Meraki WiFi Stumbler. The program is written in my data folder as Anti-2.3.1-MIUI. Unable to install in Android itself, but Titanium Backup took care of it.

As mentioned above. Leeechmiui who maintains the port added it in a few weeks back. I believe he has been working with the app developer and they let him include it with 2 free credits.

Gallery+Music not working on CM9

The gallery detects no images and the music player finds no music. I have many folders full of images and "music" folder filled with music. ES file manager can detect and view/play image-/music files.
I recently installed the latets version CM9 and I have never had this issue before. Third party music apps are also unabe to detect music. Factory reset does not help. Deleting cache and data in settings does not help. There is no issue with .nomedia files.
Don't know what to do really. Any answer is greatly appreciated.

re-flash the rom

Charl96 said:
The gallery detects no images and the music player finds no music. I have many folders full of images and "music" folder filled with music. ES file manager can detect and view/play image-/music files.
I recently installed the latets version CM9 and I have never had this issue before. Third party music apps are also unabe to detect music. Factory reset does not help. Deleting cache and data in settings does not help. There is no issue with .nomedia files.
Don't know what to do really. Any answer is greatly appreciated.
Click to expand...
Click to collapse
Its very obvious!
If reflashing doesnt work, try putting all the music files in the root of the sd card and not in folders as you did now!

gire.prasad said:
Its very obvious!
If reflashing doesnt work, try putting all the music files in the root of the sd card and not in folders as you did now!
Click to expand...
Click to collapse
Horrible option. Makes the whole "hierarchical filesystem"-thing pointless, and the SD-Card looking extremely confused (I like having a /sdcard/music/ folder, and even more folders in that. And camera also saves pictures to subfolders of /sdcard/.). There has to be another way. On my GNex CM9 doesn't have this problem, so it isn't ROM-related, and Gingerbread isn't making this trouble, too. Just as a start to exclude options on the "why".
(But, yes, I've tried that with one file, and it works. For people interested in shabby workaround and not in real fix it'll probably do the trick. (Except for (camera) pictures. Camera saves in /sdcard/DCIM/blabla. No way to change that.))

abnah said:
Horrible option. Makes the whole "hierarchical filesystem"-thing pointless, and the SD-Card looking extremely confused (I like having a /sdcard/music/ folder, and even more folders in that. And camera also saves pictures to subfolders of /sdcard/.). There has to be another way. On my GNex CM9 doesn't have this problem, so it isn't ROM-related, and Gingerbread isn't making this trouble, too. Just as a start to exclude options on the "why".
(But, yes, I've tried that with one file, and it works. For people interested in shabby workaround and not in real fix it'll probably do the trick. (Except for (camera) pictures. Camera saves in /sdcard/DCIM/blabla. No way to change that.))
Click to expand...
Click to collapse
I'm gonna try putting 1 mp3 file on root and delete any .nomedia file too see if it works, if not I'll reflash.
Same with gallery, it can't hurt..
By the way I noticed the gallery shows pictures taken after I deleted the ROM but if I place old photos in that same folder they don't show up...
Thanks for all the answers
PS. I did full wipe before installing the ROM and will wipe everything again..

dammit I ****ed up, did wipe and didn't root again so when I flashed the ROM it didn't boot. Flashing 2.3.4 Stock FTF file now. Thanks anyway.

Just FYI: Putting files to the root of /sdcard is not a longterm solution, after reboot they don't show up again. Niether clearing Media Storage's data nor wiping cache nor dalvik cache, nor fixing permissions works as a solution. That is really f*cked up.
Edit: No changes in ongoing nightlies on that. Hopefully: Yet. But I wouldn't bet on it.

SOLVED!
This is not a ROM problem! It could happen to anyone using ROM Manager!
How-to fix:
1. Download and install the latest ROM Manager APK from their website.
2. Delete the .nomedia file in /sdcard/android/data/ (ROM Manager 5.0.1.3 put a bad one there, the new version will be good).
3. Clear the data for Media Storage in Settings > Apps.
4. Reboot.
5. Wait. Re-indexing can need a while.
Credits go to the guys from the awesome Galaxy Nexus forum. Especially to Dragn4rce for creating this thread and kyokeun1234 for pointing out aboves easier solution.

abnah said:
This is not a ROM problem! It could happen to anyone using ROM Manager!
How-to fix:
1. Download and install the latest ROM Manager APK from their website.
2. Delete the .nomedia file in /sdcard/android/data/ (ROM Manager 5.0.1.3 put a bad one there, the new version will be good).
3. Clear the data for Media Storage in Settings > Apps.
4. Reboot.
5. Wait. Re-indexing can need a while.
Credits go to the guys from the awesome Galaxy Nexus forum. Especially to Dragn4rce for creating this thread and kyokeun1234 for pointing out aboves easier solution.
Click to expand...
Click to collapse
Thank you tremedously, and your credits!
*Pressing Thanks* Cheers!

YES!
abnah said:
This is not a ROM problem! It could happen to anyone using ROM Manager!
How-to fix:
1. Download and install the latest ROM Manager APK from their website.
2. Delete the .nomedia file in /sdcard/android/data/ (ROM Manager 5.0.1.3 put a bad one there, the new version will be good).
3. Clear the data for Media Storage in Settings > Apps.
4. Reboot.
5. Wait. Re-indexing can need a while.
Credits go to the guys from the awesome Galaxy Nexus forum. Especially to Dragn4rce for creating this thread and kyokeun1234 for pointing out aboves easier solution.
Click to expand...
Click to collapse
Thanks a lot, this was really helpful for me!

Lt15i

lavenderdl said:
Lt15i
Click to expand...
Click to collapse
Was this a question? If yes: Yes, the solution is exactly the same across devices.

[Q] Delete SystemUI data

SystemUI keeps crashing when it tries to restart, making my phone completely unusable. I'm not able to flash another ROM at the moment so what I'd like to try is deleting the app data for SystemUI (wiping cache and dalvik didn't work). I have Team Win Recovery so I'm able to access the filesystem to delete files.
Can anyone suggest which file(s) I should look for?

restore a backup

beekay201 said:
restore a backup
Click to expand...
Click to collapse
I want to keep my most recent files. I took some photos today and they didn't get a chance to instant upload. I can wait a few days until I get to a computer I can use ADB on to push a ROM.

Sounds like you don't need a working device.
a maguro wrote this.

Use adb to remove /data/data/com.android.systemui/ folder

Hey guys! Big news!
I've fixed the problem, well.. sort of.
I will edit the post If I had something else to test.
1. Uninstalled Android System Webview and installed the one that is present in the Play Store (I can't select it for Webview Implementation though)
2. Launched YouTube app and showed a green screen no matter what the quality is.
3. Tried Chrome and the video works well without any freezes.

Gallery keeps crashing after update open beta 6

I have recently upgraded to open beta 6 with a clean install from beta 5. Wiped. The gallery worked fine at first as far as I know. But now it's directly crashing on opening. Another open 6 version was released today and I thought this one would fix the issue but not.
Cleaned cash and data already and also tried to disable and re-enable. No luck so far.
Running with magisk 16.3.
Anyone with the same problem? I don't feel like wiping it again just for a broken gallery app but I do want to get it working again.

I don't have the problem but it could be a corrupt image file.
To eliminate this possibility put an empty file called
Code:
.nomedia
In the root directory of your internal ("SD Card") storage. Clear Gallery app data and cache again and then open the Gallery. No images should load. If the Gallery app works again then you know you need to hunt down the corrupt file (you can do this by moving that .nomedia file around to different folders or even create more of them). If this trick doesn't work then sorry I have no further suggestions (don't forget to delete the .nomedia file).

I had the same issue and the @djmcnz method didn't work for me. I fixed it by doing everything @djmcnz did (.nomedia and deleting app cache and data), going to the Google Play store and uninstalling updates from Gallery app and than updating it back.

[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