Just looking for a definative answer. One I didn't know about the HTC one m8. I'm in the process of rooting the phone be doing it later when I get home. But I downloaded viper Rom anyway to have it on the Phone to save flashing time. It downloaded onto internal memory as normal. But I cannot move it to my external ad card. Using es file explorer. After a little searching from what I can grasp is I have to do it through pc. Is it true
I also found out that I can easily do it after rooting. But if I root I loose the file. Yes I know I can save it to pc and transfer later but I find it strange I cannot moves files like normal on any other phone and this is me coming from the galaxy s4
snwman said:
Just looking for a definative answer. One I didn't know about the HTC one m8. I'm in the process of rooting the phone be doing it later when I get home. But I downloaded viper Rom anyway to have it on the Phone to save flashing time. It downloaded onto internal memory as normal. But I cannot move it to my external ad card. Using es file explorer. After a little searching from what I can grasp is I have to do it through pc. Is it true
I also found out that I can easily do it after rooting. But if I root I loose the file. Yes I know I can save it to pc and transfer later but I find it strange I cannot moves files like normal on any other phone and this is me coming from the galaxy s4
Click to expand...
Click to collapse
Why do you lose the file after rooting? All files stay intact after rooting on my device. It's unlocking the bootloader that wipes everything.
ashyx said:
Why do you lose the file after rooting? All files stay intact after rooting on my device. It's unlocking the bootloader that wipes everything.
Click to expand...
Click to collapse
Well I still have to unlock bootlader yet forgot to mention that
Just got the h815 (cze with rom v10aEURxx) .
It seems that some apps cannot write to external sd (e.g. Solid Explorer) .
Since I am not rooted yet (did not even attempt to unlock bootloader) I cannot use apps to correct external sd permissions (such as SDfix which requires root) .
Meanwhile I manage external sd writes with MyFiles and with ES Explorer.
Can someone suggest how to enable Solid Explorer SD card access without root?
I still wait for an xda developed root method which is reversible.
Thanks
You can't, but root explorer will let you manage files on external card though.
smaberg said:
You can't, but root explorer will let you manage files on external card though.
Click to expand...
Click to collapse
Thanks.
I'll wait for a reversible Root
root will be resolve, or ask the app developer to fix it.
zolom said:
Just got the h815 (cze with rom v10aEURxx) .
It seems that some apps cannot write to external sd (e.g. Solid Explorer) .
Since I am not rooted yet (did not even attempt to unlock bootloader) I cannot use apps to correct external sd permissions (such as SDfix which requires root) .
Meanwhile I manage external sd writes with MyFiles and with ES Explorer.
Can someone suggest how to enable Solid Explorer SD card access without root?
I still wait for an xda developed root method which is reversible.
Thanks
Click to expand...
Click to collapse
Just did this on my H815:http://www.androidexplained.com/galaxy-note-4-fix-external-sd-card-write-access/
Now all my apps are working fine with the external SD.
Cheers
wadken1 said:
Just did this on my H815:http://www.androidexplained.com/galaxy-note-4-fix-external-sd-card-write-access/
Now all my apps are working fine with the external SD.
Cheers
Click to expand...
Click to collapse
Even Google Photos?
polfrank said:
Even Google Photos?
Click to expand...
Click to collapse
Fair point. G.Photos is certainly reading the external SD perfectly well but it can't delete things there. You need to use Gallery of a a suitable file explorer for that.
The stock camera does store photos to the SD now. It's just offered me that option.
For me the important thing was that my FX Explorer and TI Backup etc be able to write to the ExtSD and they now do.
Cheers
That fix will not work for him as he is NOT rooted mate.
And that fix came from one I did and submitted to cyanogen more then 2 years ago when we first got KitKat. Lol
http://forum.xda-developers.com/showthread.php?p=47393405
Sent from my LG-H811 using Tapatalk
A good idea for Photos is Xposed + XInternalSD.
I have a question. Does Cyanogen use the same motif as stock roms for r/w permissions ? What is the primary SDcard on CM, internal or external?
Hi!
Sorry for my bad english, I used google translate.
Take a step 1 from this.
Then, look at this.
Do this.
And this
My current Nexus 10 is on it last legs and I decided to pick up a Galaxy Tab T800 10.5 inch wifi only in good/Used condition on ebay and should receive it next week.
While I await it, I'm starting to look at its rooting process and if I should root it not. I assume it is coming unrooted, but won't know for sure till I get it and what version of Android it currently has. I'm not completely new to rooting as I have done it before on my Nexus 10 and Note 2 phone (yeah, time to upgrade). Its just been a while since I need to root something.
But do you think rooting it and going with a custom Rom is that much better than the Stock Rom?
Also, I did only buy a 16GB version, as the majority of all of my video's are on a home server and I use either XBMC/Kodi and BSPlayer to connect and watch things. But I remember with my Nexus 10 it was also possible to Map a Folder to a local server. Does anyone know if that is possible with Galaxy Tab? The ability to map a folder/drive is great to navigate and view pdf's, pictures etc.
Thanks
PT
ptmuldoon said:
My current Nexus 10 is on it last legs and I decided to pick up a Galaxy Tab T800 10.5 inch wifi only in good/Used condition on ebay and should receive it next week.
While I await it, I'm starting to look at its rooting process and if I should root it not. I assume it is coming unrooted, but won't know for sure till I get it and what version of Android it currently has. I'm not completely new to rooting as I have done it before on my Nexus 10 and Note 2 phone (yeah, time to upgrade). Its just been a while since I need to root something.
But do you think rooting it and going with a custom Rom is that much better than the Stock Rom?
Also, I did only buy a 16GB version, as the majority of all of my video's are on a home server and I use either XBMC/Kodi and BSPlayer to connect and watch things. But I remember with my Nexus 10 it was also possible to Map a Folder to a local server. Does anyone know if that is possible with Galaxy Tab? The ability to map a folder/drive is great to navigate and view pdf's, pictures etc.
Thanks
PT
Click to expand...
Click to collapse
Previous to my S1 10.5" I had a rooted Nexus 10. I rooted without tripping Knox to retain my warranty. Although I had my S1 for several months without rooting (5.0.2) there will a few things I missed:
- Viper4Android (superior audio replacement)
- GMD Gesture Control (including immersion mode)
- Enhanced Power menu
- Titanium backups
- Full RW access to the internal microSD card
- The ability to theme the TouchWiz UI
There are more reasons to root but those are the first few that I desperately missed from the N10.
The free ES File Explorer can map CIFS/SAMBA network drives and with root can access the entire internal storage with RW permissions. I use Plex/MXPlayer to access my NAS video collection without transcoding but the setup you mentioned would also work well even if you didn't root.
I found that after having full RW access to my MicroSD card (64GB) that you could do what ever you wanted as far as mapping is concerned. I get Titanium Backup to write straight to the mSD card and have never seen my 16GB device as too small, it just does not happen. With that said I am not a gamer so take the comment with a grain of salt. My mSD card is mainly filled with backups and music files.
As you are likely to no longer be under warranty I would advise rooting using the CF method which includes TWRP then you can try which ever custom ROM catches your fancy and switch safely as long as to take nandroid backups with the enhanced recovery.
Sent from my SM-T800 using XDA Premium HD app
3DSammy said:
Previous to my S1 10.5" I had a rooted Nexus 10. I rooted without tripping Knox to retain my warranty. Although I had my S1 for several months without rooting (5.0.2) there will a few things I missed:
- Viper4Android (superior audio replacement)
- GMD Gesture Control (including immersion mode)
- Enhanced Power menu
- Titanium backups
- Full RW access to the internal microSD card
- The ability to theme the TouchWiz UI
There are more reasons to root but those are the first few that I desperately missed from the N10.
The free ES File Explorer can map CIFS/SAMBA network drives and with root can access the entire internal storage with RW permissions. I use Plex/MXPlayer to access my NAS video collection without transcoding but the setup you mentioned would also work well even if you didn't root.
I found that after having full RW access to my MicroSD card (64GB) that you could do what ever you wanted as far as mapping is concerned. I get Titanium Backup to write straight to the mSD card and have never seen my 16GB device as too small, it just does not happen. With that said I am not a gamer so take the comment with a grain of salt. My mSD card is mainly filled with backups and music files.
As you are likely to no longer be under warranty I would advise rooting using the CF method which includes TWRP then you can try which ever custom ROM catches your fancy and switch safely as long as to take nandroid backups with the enhanced recovery.
Sent from my SM-T800 using XDA Premium HD app
Click to expand...
Click to collapse
Thank's for the great info and feedback. I'll plan to root it when it arrives (hopefully this weekend). But have 2 more general questions as you seem pretty familiar wit the tablet.
I know its personal preference. But have you found a preferred custom Rom you like? And are you sure you ESFile Explorer can actually Map a network CIFS/Samba share location? I can use ESFileExplorer to access my server and navigate the network shares. But I have not figured out how to actually map the shares to a local folder on the tablets. I'll have to revisit that ability separately though as its not big deal as XBMC/Kodi and others can still access the shares.
But when the shares are actually mapped to local folder, you can navigate them from pretty much any native app.
ptmuldoon said:
... But have you found a preferred custom Rom you like? And are you sure you ESFile Explorer can actually Map a network CIFS/Samba share location? I can use ESFileExplorer to access my server and navigate the network shares. But I have not figured out how to actually map the shares to a local folder on the tablets. I'll have to revisit that ability separately though as its not big deal as XBMC/Kodi and others can still access the shares.
But when the shares are actually mapped to local folder, you can navigate them from pretty much any native app.
Click to expand...
Click to collapse
As I rooted but preserved my warranty by not tripping the Knox counter (I can return to pure uprooted stock), I must keep the Samsung locked bootloader. The means I have limited choices in custom ROMs and no choice in custom kernels. The only ROM I could flash is Ironman. With all that said I decided to stay with stock 5.0.2 and just augment it with root apps that I listed in my previous post. That gave me all the custom ROM features I regularly use.
I think now I understand better what you wanted from mapping. So ES File Manager would not give you what you wanted as its cifs/samba maps are usable by other apps only when you use the ES file manager UI. For example click on a CIFS mapped video file in the ES file Manager UI and an associated video player plays the video. In the past I used XBMC on Android and that version included CIFS/Samba drivers that allowed me to access my network attached video collection. I suspect that feature still exists.
Now if you had video files on either the internal storage or external microSD card and wanted those directories available to XBMC the internal storage would be no issue but I think you need to use an app like Stick mount for the microSD. Stick mount creates a symbolic link on the internal storage (\sdcard) to directories on the microSD card allowing any app to access those files as if they were located on internal storage. That may accomplish what you want.
I still maybe misinterpreting what your trying to accomplish with mapping but I'm fairly sure one way or another you can get what your looking for especially as you'll be rooted.
Sent from my SM-T800 using XDA Premium HD app
3DSammy said:
I think now I understand better what you wanted from mapping. So ES File Manager would not give you what you wanted as its cifs/samba maps are usable by other apps only when you use the ES file manager UI. For example click on a CIFS mapped video file in the ES file Manager UI and an associated video player plays the video. In the past I used XBMC on Android and that version included CIFS/Samba drivers that allowed me to access my network attached video collection. I suspect that feature still exists.
I still maybe misinterpreting what your trying to accomplish with mapping but I'm fairly sure one way or another you can get what your looking for especially as you'll be rooted.
Sent from my SM-T800 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah. It was tricky on the Nexus 10 to mount a CIFS/Samba share and needed specific cifs.ko and other modules. It was sorta of hit and miss and I remember most said it worked best when you mounted them to the /mnt/obb system file folder location. If you google it, you'll find bunch of topics leading back to posts on xda about it.
Its the same concept of mapping a share with a PC, etc. Once done, any program/app should see that information as a local system folder. So you could launch any app and if needed, navigate to your network share files to open a document., text file, pdf viewer, and so depending on what the app was looking for. Even ESFile Explorer would then see your network shares as a local system directory. And you could actually save your titanium backups directly to your NAS or network server, if you wanted to.
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