MiXplorer: Q&A and FAQ (User Manual)

[Spannaa]

I think this is what you want.

Be sure you don't have an extra space in front of the percent sign.

Not sure this is exactly what @roxion22 was after.

Pretty sure renamed file a0010.jpg ought to be a010.jpg and your screenshot doesn't show the renamed file before a001.jpg but it would be a.jpg

Name 'a' with Incremental number format '%3d' would give three digits for all files, but the first file renamed would still be a.ext

I think this needs a regex.

 

[Spannaa]

How to rename all files to a001.txt,a002.txt,a003.txt..... instead a(1).txt, a(2).txt.

Just looked at this again and it's less complicated than I thought:

 

[09kkthxbb]

Hello. Is there any chance for MiXplorer to have BLAKE3 support? I've heard that it is faster file hashing method than MD5 and SHA. Thanks

 

[IronTechmonkey]

Hello. Is there any chance for MiXplorer to have BLAKE3 support? I've heard that it is faster file hashing method than MD5 and SHA. Thanks

Interesting question, it would get more exposure to the developer and other knowledgeable Android users if you post in the main thread as well. It's always okay to start with the FAQ but, whether the developer says yay or nay, this is a good question for the development thread .

 

[TimAnd]

HI again. When I click Image, I don't see Viber images. I see that from A11 there's some new complication called Scoped Storage, I guess that's the cause. Is there is way to access Viber received/sent images as files?

Viber migrates to scoped storage for better app, user data protection

When Android 10 was released, it came with a concept called scoped storage, and Google hinted that Android 11 will require all apps – existing and new – to use Scoped Storage. Developers stil…

androidcommunity.com

Edit: LineageOS 18.1.

 

[IronTechmonkey]

Creating Document Providers = Google's Infinite Loops in a Room Full of Mirrors

With thanks again @Testing33 for persistence and @Ultramanoid for coaching, additional methods of selecting document provider have been clarified (in spite of Google having effectively locked us in a room full of mirrors in this regard). I think it’s likely that other people have attempted to report this or done this on their own thinking it was the default. In addition to the wide variation of behavior across different devices, the native file picker may remember which drive was previously selected then in future offer it in a way where users may not even realize there are other options.

The native OS picker in which we navigate to and select a folder to assign document provider offers one item each for internal and external storage. Additionally, it offers MiXplorer specific internal and external storage. If I recall correctly (which is not a certainty on this topic) most people have reported on their attempts to navigate through the OS default drive, but the MiXplorer specific drives can yield different results, in some cases to the successful granting of a document provider at root of internal storage but in other cases, such as external storage on the tested device it can create an inaccessible storage item. Here is the walk-through on a rooted stock moto A11 device which is more restrictive than many others.

00 document provider options.png: diagram of OS and MiXplorer “drives” for document provider navigation.


01 OS internal.png: This is what might be seen when navigating for document provider to OS internal SD on a device that does not allow selection at top of internal storage but allows some degree of selection in /internal SD/Android. “Use this folder” (root of drive) is greyed out.


02 OS external.png: This is what might be seen when navigating to OS external SD on a device that does not allow selection at top of external storage or anything in /external SD/android/. “Use this folder” (root of drive) is greyed out.


03 MiX external.png: This is what might be seen when navigating through MiXplorer’s external SD card option. This was an incidental discovery made when testing the reported mechanism for internal SD card. Note the incongruity of “can’t load content at the moment” and “use this folder” being live (not greyed out). Proceeding from here may create an inaccessible “phantom” drive and associated bookmark.


04 MiX internal.png: This is what might be seen when navigating through MiXplorer’s internal SD card option and, to the point of @Testing33's (and likely other people’s) reports, this might allow the assignment of document provider at root of internal storage when that is not available by selecting OS internal storage item. Note the list of folders and the live “use this folder” button. This did indeed seem to allow for the successful creation of a document provider on root of internal storage when that was not possible in the native OS internal storage item.


05 MiX Added Storage.png: both the previously described successful attempt to add document provider at root of internal storage and the unsuccessful attempt to add document provider at root of external storage appear as new storage volumes in MiXplorer but not in other apps or parallel versions of MiXplorer. IIRC this does not occur when adding document providers for individual folders but that may depend on the nature of restrictions and document providers on the drive and at the folder. To remove the drives that were created by MiXplorer: MiX app properties > Storage > clear access.

 

[IronTechmonkey]

HI again. When I click Image, I don't see Viber images. I see that from A11 there's some new complication called Scoped Storage, I guess that's the cause. Is there is way to access Viber received/sent images as files?

You may be correct about this being due to scoped storage but more information would be required, such as the details of the device and the specific location of the files, to determine that for sure, and there is a more effective way of testing than using the "image" bookmark. The "image" and other built-in bookmarks are effectively searches which will show what is found but will not reveal information about the location of expected items if they are not found.

For testing purposes navigate to the directory through one of the paths. Also, to access such locations we may need to create document providers or use an alternative path depending the location. Typically that is the order which the developer suggests we attempt solutions, first try document provider then try alternate path (for the locations where alternate path is viable) but the Google and OEM universe in this regard is wildly variable even within individual android versions. It's also worth noting that this is to establish access to the raw location but I do not know what effect that will have on the search bookmark.

This is based on the premise that this is an issue with document provider access to the app directory.

See the first 2 links below for description of document provider configuration and troubleshooting respectively. See the 3rd link (which should go to the post before this one) regarding alternate methods of creating document provider which may help in some cases, and see the 4th link for a description of the extreme variability that I witnessed within android 11 on a few devices.

1) MiX Nugget - Document Provider: https://forum.xda-developers.com/t/mixplorer-q-a-and-faq-user-manual.3308582/post-85878051

and

2) MiX Nugget: Troubleshooting SD card & USB OTG access, accessing /android/data, creating Document Providers, accessing folders on Andriod TV or Google TV, accessing folders in Android 13 and up, other things: https://forum.xda-developers.com/t/mixplorer-q-a-and-faq-user-manual.3308582/post-87626419

3) Creating Document Providers = Google's Infinite Loops in a Room Full of Mirrors
https://forum.xda-developers.com/t/mixplorer-q-a-and-faq-user-manual.3308582/post-88279387

4) Google restrictions highly variable even within one Android version:
https://forum.xda-developers.com/t/...y-featured-file-manager.1523691/post-88252365

 

[TimAnd]

You may be correct about this being due to scoped storage but more information would be required, such as the details of the device and the specific location of the files..

I'm not familiar with document providers but it seems that I don't have that problem of access.
I didn't know where Viber images are, not in /viber/media/images.
Seems they are now in /Android/data/com.viber.voip/files/.image (with . ) I can see them when browsing with Mix.
So question is: why are those images not read in Image. Is it because of .nomedia there?

 

[IronTechmonkey]

I'm not familiar with document providers but it seems that I don't have that problem of access.
I didn't know where Viber images are, not in /viber/media/images.
Seems they are now in /Android/data/com.viber.voip/files/.image (with . ) I can see them when browsing with Mix.
So question is: why are those images not read in Image. Is it because of .nomedia there?

Yep, I believe so; check for .nomeedia and .nosearch in that folder and in all folders along the path. You could see what happens if you rename .nomedia, then refresh the android media store for that drive (in mix go to top of drive > long press location > refresh media store).
If after fiddling around don't see those pictures even though you can read and write to the directory it might be worth reporting in the main thread with a log.

BTW, If you are on android 11 and not familiar with document providers then count your blessings. You may have been saved from that madness because LOS being more friendly than my stock motos.

 

[IronTechmonkey]

This material is so frequently needed that I'm thinking of posting it daily, and maybe renting some skywriting planes, or projectors that display it on the sides of large buildings, maybe attach it as a rider to every known EULA. Also, t-shirts, mugs hats and other merchandise. Perhaps a touring pop-group named "Document Provider" who's hit song is "I Love Your /Android/Data Content" with lyrics that describe how to configure document providers (who will later be found to have been lip-synching i-phone users who know nothing of document providers.).

1) MiX Nugget - Document Provider: https://forum.xda-developers.com/t/mixplorer-q-a-and-faq-user-manual.3308582/post-85878051

2) MiX Nugget: Troubleshooting SD card & USB OTG access, accessing /android/data, creating Document Providers, accessing folders on Andriod TV or Google TV, accessing folders in Android 13 and up, other things: https://forum.xda-developers.com/t/mixplorer-q-a-and-faq-user-manual.3308582/post-87626419

3) Creating Document Providers aternate method = Google's Infinite Loops in a Room Full of Mirrors
https://forum.xda-developers.com/t/mixplorer-q-a-and-faq-user-manual.3308582/post-88279387

4) Google restrictions highly variable even within one Android version:
https://forum.xda-developers.com/t/...y-featured-file-manager.1523691/post-88252365

 

[Senliast]

I am not able to open files, that are accessible only with root, in external apps from MiXplorer. See video. Like shown, it works from any other file manager. Does someone have an idea?

94.76 MB file on MEGA

mega.nz

 

[IronTechmonkey]

I am not able to open files, that are accessible only with root, in external apps from MiXplorer. See video. Like shown, it works from any other file manager. Does someone have an idea?

94.76 MB file on MEGA

mega.nz

The video is hard (for me) to follow as the events occur quickly (compounded by non-English UI* which makes it harder for some people to determine which screen elements are flashng by quickly) Also it does not inform about the state of the device. A brief appearance of a hash-mark (#) might indicate that the device is rooted, but does not speak specifically to what's going on in MiXplorer, and there are other possible factors. More detail may be required.

First, in addition to requiring SU access through your SU manager, MiXplorer has its own in-app toggle which can disable root functions in MiXplorer even on a rooted device (but it does not gain root on a device that is not otherwise rooted). Check: Menu > Settings > More settings > Allow root to make sure it is enabled.

If root is enabled in MiXplorer then please log this as you reproduce what you are doing in your video, then share the log with step-by-step list of what actions you took while capturing the log. At minimum the log will inform about the state of the device and at best it might provide an answer. If that does not work then the log and associated details could be brought to the main thread so the developer might see it.

More information about MiX logging: https://forum.xda-developers.com/t/mixplorer-q-a-and-faq-user-manual.3308582/post-65157367

* There is no implied criticism about the UI not being in English. That is just a limitation of my ability to understand what is happening in the video. I can discern some of it by context if I go frame by frame but, IMO it's not worth doing that until other details are confirmed by looking at a log.

 

[OfOtherWorlds]

Is it possible to change the default folder for Mixplorer's one tap download, AKA DownloadActivity, or do I just have to disable it and use "copy to" to save things to my SD card? I've circled what I want to modify.

 

[IronTechmonkey]

Is it possible to change the default folder for Mixplorer's one tap download, AKA DownloadActivity, or do I just have to disable it and use "copy to" to save things to my SD card? I've circled what I want to modify.View attachment 5875075

I believe that one tap download option is dedicated to the system download folder just as most downloads are from other apps... unless the app offers a way to select a download location, and it is my understanding that the reason the copy to option exists is to give us that choice in MiX but you should not have to disable anything in order to use it. It's an extra tap but that is part and parcel of being able to select a download location.

 

[IMXEren]

Hello everyone, I'm currently working with content URIs on Tasker. However, I've encountered an issue where sending an Intent or launching an activity to open a content URI image from another app in ImageViewer results in a blank image being displayed. Strangely, if I manually share the image and open it in ImageViewer, it gets displayed correctly. Furthermore, if I send an Intent after that, the image is also displayed correctly without any issues.

I'm not sure what I'm doing wrong, or if this behavior is expected. Also, my main objective is to copy the image to a specific location, which can only be achieved if the URI is valid. I'm experiencing an issue with this as well, as when using the "Copy to.." activity, it goes into an infinite copying loop if the URI is invalid.
Thanks

 

[IronTechmonkey]

Hello everyone, I'm currently working with content URIs on Tasker. However, I've encountered an issue where sending an Intent or launching an activity to open a content URI image from another app in ImageViewer results in a blank image being displayed. Strangely, if I manually share the image and open it in ImageViewer, it gets displayed correctly. Furthermore, if I send an Intent after that, the image is also displayed correctly without any issues.

There are a few notes about Tasker intents in MiX. Links to them should be easy to find by searching the first page of this thread in a web browser (browser search, not XDA search) for Tasker. Some items are about managing servers but there might be others, worth a quick look. Beyond that, this might be worth logging and reporting with more detail in the main thread where it will get more exposure to the developer and other knowledgeable users.

I'm not sure what I'm doing wrong, or if this behavior is expected. Also, my main objective is to copy the image to a specific location, which can only be achieved if the URI is valid. I'm experiencing an issue with this as well, as when using the "Copy to.." activity, it goes into an infinite copying loop if the URI is invalid.
Thanks

I've had some interesting escapades doing similar things in Tasker on a particular device that had atypically restrictive drive permissions. Before taking this to the main thread, try testing manual copy or move operations in the MiXplorer UI in the applicable locations. Likewise give Tasker a quick test of those locations by having it create or write to an existing text file in that location. If you encounter permissions errors while doing that then there might be workarounds, and if you do not then take it to the main thread.

 

[IronTechmonkey]

disregard, testing links

link

 

[IMXEren]

There are a few notes about Tasker intents in MiX. Links to them should be easy to find by searching the first page of this thread in a web browser (browser search, not XDA search) for Tasker. Some items are about managing servers but there might be others, worth a quick look. Beyond that, this might be worth logging and reporting with more detail in the main thread where it will get more exposure to the developer and other knowledgeable users.

Thanks for your response & yes, I did look on them (FAQs) before attempting to ask the question. Okay, I'll try to ask this in the main thread after I finish the conversation here.

I've had some interesting escapades doing similar things in Tasker on a particular device that had atypically restrictive drive permissions. Before taking this to the main thread, try testing manual copy or move operations in the MiXplorer UI in the applicable locations. Likewise give Tasker a quick test of those locations by having it create or write to an existing text file in that location. If you encounter permissions errors while doing that then there might be workarounds, and if you do not then take it to the main thread.

May I know, is there a way to view file using content URI in MiXplorer? (sorry if it's a silly question)
Just like I wrote above, if the file is in a content URI format then until it is opened manually in ImageViewer, no copy or move functions will work in Tasker & MiXplorer. Copying and other operations are a success in case of file paths (idk about the content URI as idk the way to open them in MiX). As far as I know, I gave Tasker access to all permissions and it can operate in the desired destination of copying the image.



Let me explain you my whole process of what I'm trying to achieve which would be better for both of us. I am using Imgur API to upload images in Tasker by AutoShare-ing (Plugin; populates variables with the file paths/content URI/links). It's working when I try to use the file path/links but that's not the case with content URIs. The issue is that Tasker is unable to access all content provider but if I use MiXplorer content provider (URI) of that original content URI (OC URI in short) Tasker is able operate actions without any errors. So, I thought of replacing the content:// with content://com.mixplorer.file/24! in the OC URI to obtain the MiX URI.

OC URI: content://com.laurencedawson.reddit_sync.pro.provider/external_files/Android/data/com.laurencedawson.reddit_sync.pro/cache/shared/124f1f01935749881f64374bf9a82e99.jpg
MiX URI: content://com.mixplorer.file/24!com.laurencedawson.reddit_sync.pro.provider/external_files/Android/data/com.laurencedawson.reddit_sync.pro/cache/shared/124f1f01935749881f64374bf9a82e99.jpg

Then using the MiX URI in either Copy To.. or ImageViewer Activities but to my surprise, it doesn't function (infinite copying progress & blank image display) until shared manually and opened in ImageViewer (tested in Bromite, Mull Browser, Sync for reddit) even though file is created (specifically for Sync for Reddit) in Android/data/com.package_name/cache/shared/ABC.jpg. Also, I can't use the file path because if the file is in the Android then Tasker can't access it, so preferred MiX URI to temporarily copy the file > Upload to imgur > Delete the temp file.


So, I enabled logging to see where the error actually occurs after sending the intent to open in ImageViewer.

1. First Log, when I shared to AutoShare to send intent; unsuccessful.
2. Second Log, when shared to ImageViewer manually; successful.
3. Third Log, when shared to AutoShare to send intent after it was opened; successful.

Thank you for bearing with me until this point.

 

[IronTechmonkey]

Thanks for your response & yes, I did look on them (FAQs) before attempting to ask the question. Okay, I'll try to ask this in the main thread after I finish the conversation here.

When you're done with this you should write an article about forum etiquette. It would be nice if more people, especially myself, hashed stuff like this out in a FAQ before going to the development thread.

May I know, is there a way to view file using content URI in MiXplorer? (sorry if it's a silly question)
Just like I wrote above, if the file is in a content URI format then until it is opened manually in ImageViewer, no copy or move functions will work in Tasker & MiXplorer. Copying and other operations are a success in case of file paths (idk about the content URI as idk the way to open them in MiX). As far as I know, I gave Tasker access to all permissions and it can operate in the desired destination of copying the image.



Let me explain you my whole process of what I'm trying to achieve which would be better for both of us. I am using Imgur API to upload images in Tasker by AutoShare-ing (Plugin; populates variables with the file paths/content URI/links). It's working when I try to use the file path/links but that's not the case with content URIs. The issue is that Tasker is unable to access all content provider but if I use MiXplorer content provider (URI) of that original content URI (OC URI in short) Tasker is able operate actions without any errors. So, I thought of replacing the content:// with content://com.mixplorer.file/24! in the OC URI to obtain the MiX URI.

OC URI: content://com.laurencedawson.reddit_sync.pro.provider/external_files/Android/data/com.laurencedawson.reddit_sync.pro/cache/shared/124f1f01935749881f64374bf9a82e99.jpg
MiX URI: content://com.mixplorer.file/24!com.laurencedawson.reddit_sync.pro.provider/external_files/Android/data/com.laurencedawson.reddit_sync.pro/cache/shared/124f1f01935749881f64374bf9a82e99.jpg

Then using the MiX URI in either Copy To.. or ImageViewer Activities but to my surprise, it doesn't function (infinite copying progress & blank image display) until shared manually and opened in ImageViewer (tested in Bromite, Mull Browser, Sync for reddit) even though file is created (specifically for Sync for Reddit) in Android/data/com.package_name/cache/shared/ABC.jpg. Also, I can't use the file path because if the file is in the Android then Tasker can't access it, so preferred MiX URI to temporarily copy the file > Upload to imgur > Delete the temp file.


So, I enabled logging to see where the error actually occurs after sending the intent to open in ImageViewer.

1. First Log, when I shared to AutoShare to send intent; unsuccessful.
2. Second Log, when shared to ImageViewer manually; successful.
3. Third Log, when shared to AutoShare to send intent after it was opened; successful.

Thank you for bearing with me until this point.

Not a silly question at all, just one that I cannot answer but the developer might be able to provide an answer. Try this, post in the main thread the general gist of your question with some basic details and a link to your well detailed post in this thread. Note, the developer is sometimes away from the threads for periods of time but is good about following up upon return.

 

[TimAnd]

I wish there were detailed explanation on connecting with 'servers'. Something is obvious, start server, use client, and it all works with clients like FileZilla, Cyberduck, or browser for HTTP.

Problem I have is how to map as drive in Windows. I tried WebDAV in 8.1 and 10, no luck. Tried to map \\IP\@[email protected] nothing, \\IP\@[email protected]\DavWWWRoot unexpected arror.
Not sure if it's about self-signed certs or some Windows quirk. ( I wish I don't use Windows, but I'm lazy to totally discard it or I'd have to reinstall Linux and worse set up details for a few devices ).

Here in https://forum.xda-developers.com/t/...fully-featured-file-manager.1523691/page-1869 @hudson4351 said:

when "Authentication" is set to either "Basic" or "Digest", I am able to map the HTTP/WebDav Server to a network drive in Windows Explorer after being prompted for and entering the correct username and password.

So it should be possible, just how.

Similar problem with SMB. Don't know how to map it to Windows. How and where to set smb://IP/sharename and what is sharename here.
SMB 1.0 Client is enabled, I see SMB 1 and SMB 2 as enabled in the system.
This is OK (but cannot use custom port in Windows Explorer): Test-NetConnection -ComputerName 192.168.1.2 -Port 4450 -InformationLevel "Detailed"
This is NOK (when I set Server port to 445): Test-NetConnection -ComputerName 192.168.1.2 -Port 445