[APP][2.2+] MiXplorer v6.x Released (fully-featured file manager)

[Exameden]

Reading about the search, I would like to share my experience
I personally rarely like internal search of sites for plenty of reasons, using instead google with the site operator so for this thread it's

[ {your search} site:https://forum.xda-developers.com/t/...released-fully-featured-file-manager.1523691/ ]

Here the square brackets represent google search field, {your search} is your terms. I recommend using quotes for mandatory words and phrases so google won't try to correct you or ignore them. The terms here are before the site operator in order to be easily accessed for correction after the search is performed. An example about the mentioned search

[ "data/data" root site:https://forum.xda-developers.com/t/...released-fully-featured-file-manager.1523691/ ]

 

[IronTechmonkey]

Reading about the search, I would like to share my experience
I personally rarely like internal search of sites for plenty of reasons, using instead google with the site operator so for this thread it's

[ {your search} site:https://forum.xda-developers.com/t/...released-fully-featured-file-manager.1523691/ ]

Here the square brackets represent google search field, {your search} is your terms. I recommend using quotes for mandatory words and phrases so google won't try to correct you or ignore them. The terms here are before the site operator in order to be easily accessed for correction after the search is performed. An example about the mentioned search

[ "data/data" root site:https://forum.xda-developers.com/t/...released-fully-featured-file-manager.1523691/ ]

Yes, external google searches for internal XDA posts can be surprisingly effective (seriously this is often underrated - thanks for the tip) but since the recent XDA changes not as many good results are being found that way as in the past. Maybe it will take time for the site to be fully re-indexed. That all being said the fact remains that a most basic search of the using obvious search term would have returned the answers people were seeking.

 

[J.Michael]

That is a very good question! I always thought that a factory reset would reset a phone to the same state as purchased new and someone in another thread on XDA recommended that I reset my phone to downgrade from Android 11 to 10, but your question just provoked me to look into it a bit more and it seems that a factory reset will wipe your data, but will not downgrade the software version. Apparently, I am stuck on Android 11, unless anyone knows differently.

The thread on rooting the SM-T290 (or maybe the SM-T295) talked about mixing pieces of two stock ROMs. In that case the goal was to keep an older bootloader. The same principle could be applied here: If you can't flash the older Android you want, you might get away with feeding Odin the BL.tar of your current system, with all other files coming from the older ROM.

Look for posts by @gcrutchr and @Talich52

 

[WiraHy]

There is still a beta version in the OP of this thread and, AFAIK although the beta versions seem to contain components of the Silver version I don't think it is distributed on the same track. I'm not doubting that you may be seeing something atypical but could you please clarify. I have Silver and could test.

Before, mixplorer silver have a beta version at play store by "join beta tester" button. Ive joined and have "mixplorer silver (beta)" version. Now it no longer have the (beta) mark and it doesnt have "leave beta tester" button (thats why i ask). Because of that i cant give rating to mixplorer silver (at least happened to me yesterday). What ive do is download "beta maniac" app and "leave beta tester" from there. Then i can give mixplorer silver 5 star rating.
Im not pushing the dev to re-release the silver beta version, its the dev decision and i always support it.

 

[IronTechmonkey]

Before, mixplorer silver have a beta version at play store by "join beta tester" button. Ive joined and have "mixplorer silver (beta)" version. Now it no longer have the (beta) mark and it doesnt have "leave beta tester" button (thats why i ask). Because of that i cant give rating to mixplorer silver (at least happened to me yesterday). What ive do is download "beta maniac" app and "leave beta tester" from there. Then i can give mixplorer silver 5 star rating.
Im not pushing the dev to re-release the silver beta version, its the dev decision and i always support it.

Thanks for the explanation. I did not even know there was a beta group available for MiX at play store as I always tested the beta from this thread. The changes probably have to do with the issue HP mentioned about the Silver package a few pages ago. Thanks again.

 

[rsngfrce]

Mixplorer v6.54.2_B21040310 running on Android 11 (Oneplus 7T Pro).
The program has root permission and can operate with this permission:
View attachment 5272399View attachment 5272401

However when going to /data/data only Mixplorer folder is displayed:
View attachment 5272405

Root Explorer shows everything in the same time:
View attachment 5272403

Same for Total Commander:
View attachment 5272459

What is going on? Is switching to outdated version the only solution?

Regardless of all the discussion of searching for this commonly asked question, I felt your post asked the question in by far the most comprehensive manner I've seen.

 

[IronTechmonkey]

Regardless of all the discussion of searching for this commonly asked question, I felt your post asked the question in by far the most comprehensive manner I've seen.

https://forum.xda-developers.com/t/...y-featured-file-manager.1523691/post-84753071

 

[DiamondJohn]

I like people who acts as porter in female campus dormitory trying rather to point on one's mistakes than to help.

However it looks like the problem in SDK30 implementation of Mixplorer.
Looking into logs one can see the problem in ls -lnApSr "/data/data" output already.
At the same time in terminal:
...snip...
It is a real pity Hootan decided to combine Mixplorer for sdk30 and sdk29 together because sdk30 really still at beta stage.

The way Android acts within a root shell is different to how it acts in java.

Just because two apps are both targeted for SDK 30, does not mean they both are using the java interface provided by Android. For example, one app may be using a root shell, while the other is using Java directly.

SDK 30 is not considered BETA by Google, its live. However, it is still being developed. Which, is also a reason to stop using SDK29, as its no longer being developed (or not having as much time expended on it). The restriction you have come across is not because SDK is less in any way than SDK29, but BECAUSE it is more developed in line where google have chosen to direct Android and in particular, its security. Remember, you are performing ROOT tasks which are considered questionable from a security perspective. There are numerous things that were possible under previous versions of android (and the directly associated SDK) whch are no longer allowed / supported.

 

[Operator404]

hello please add the service TeraBox (Dubox.com) it provides free 1024gb

 

[temporarium]

The way Android acts within a root shell is different to how it acts in java.

Just because two apps are both targeted for SDK 30, does not mean they both are using the java interface provided by Android. For example, one app may be using a root shell, while the other is using Java directly.

SDK 30 is not considered BETA by Google, its live. However, it is still being developed. Which, is also a reason to stop using SDK29, as its no longer being developed (or not having as much time expended on it). The restriction you have come across is not because SDK is less in any way than SDK29, but BECAUSE it is more developed in line where google have chosen to direct Android and in particular, its security. Remember, you are performing ROOT tasks which are considered questionable from a security perspective. There are numerous things that were possible under previous versions of android (and the directly associated SDK) whch are no longer allowed / supported.

You have noticed that Google's definition of "security" is not related to security at all? That applies to Android. They're making it harder to bypass their tracking. That's all they are doing. Root, by definition, should be able to do everything, even rm -rf /* .

 

[DiamondJohn]

Root, by definition, should be able to do everything, even rm -rf /* .

HOWEVER, as new versions of android occur, things are done differently, including HOW root things are done. Root is not about keeping everything the same. What works one day, is possibly done differently the next. Your example (ie rm), still works the same. Its a SHELL command, NOT an app Java call. You are confusing the issue, as this thread is about a Java application, not a shell command runner.

[OT]I have been using Android since Gingerbread, and I cant really think of much that I could do before (using root), that I cant do now, more so the other way. The only one that bugs me is that mediaserver (i think that was what it was called) is now not available in AOSP shell. And yes, it was a BIG security issue[/OT]

You have noticed that Google's definition of "security" is not related to security at all? That applies to Android. They're making it harder to bypass their tracking. That's all they are doing.

Do not "throw out the baby with the bathwater". Your statement is emotional charged and people can easily be carried away with it. I personally dont do banking or other too private operations on my device (partly because of all the tracking), but the greater population (i.e. not US) do use the added security; and are possibly blind to the tracking/privacy issues. Google do not build phones/OS's for XDA members, we are the very small minority, the big $$$ is in everyone else.

Getting back on topic, this all started with me explaining how we now have to configure our root (ie Magisk), to access folders on A11, that we could see previously in our FM by default (ie before A11). The HOW changes, that is a given, otherwise, do not upgrade the OS or your Apps. If you wish to complain about the direction android is headed, then google should be your target for complaints. its wasted here and OT.

 

[asliaral]

Videos are freezing. İ downloaded Mix codec. Some mp4 videos are fixed if İ choose Sw. But İ am taking a new video (mp4) and it still freezing.

Do you have any solution?

 

[Ultramanoid]

... google should be your target for complaints. its wasted here and OT.

FMs have to deal with Google's restrictions more than any other piece of software, so I'd argue it is on-topic. If you talk to Material Files' developer ( who works at Google ) he would probably tell you how he develops around Google's guidelines and when asked to break those "good practices" for the benefit of users, he won't. But if you head over to FX's thread here in XDA instead you'll see the multiple complaints the developer has about, as it has been called, "Google's direction", and that's the developer himself raising these points once and again in that thread -- and to Google, who consistently ignore him. This is pretty much THE topic, with file managers.

 

[IronTechmonkey]

Boogle!

 

[IronTechmonkey]

Videos are freezing. İ downloaded Mix codec. Some mp4 videos are fixed if İ choose Sw. But İ am taking a new video (mp4) and it still freezing.

Do you have any solution?

If it is a "new" video which you have not viewed before then there could be an issue with it or it may have excessively high requirements to play smoothly. On the other hand, if this is a video which did not have the issue in a previous version of MiXplorer but does have the issue now then it may be a bug.

In any event, more details about the system and the file itself would be helpful in determining if the issue is with the file or the MiX player, and if it seems like an issue with the player then logs would be helpful. Testing the file in other players for comparison and having other people test it (if it's not private) would also be helpful.

 

[asliaral]

If it is a "new" video which you have not viewed before then there could be an issue with it or it may have excessively high requirements to play smoothly. On the other hand, if this is a video which did not have the issue in a previous version of MiXplorer but does have the issue now then it may be a bug.

In any event, more details about the system and the file itself would be helpful in determining if the issue is with the file or the MiX player, and if it seems like an issue with the player then logs would be helpful. Testing the file in other players for comparison and having other people test it (if it's not private) would also be helpful.

İt is a new video, İ have created yet on the phone. İ am new on this app so İ don't know old versions.

İ sent the video to my friend on Telegram and he told me he could watch normally.


İ downloaded a mp4 video for trying. İt works. But if İ save with my phone, it doesn't work.


So it seems like a bug on app. İs there anyone have this problem?

 

[Mariner55]

Since MiXplorer_v6.54.2_B21040320 (silver, too) I'm not longer able to log into my encfs-folders on OneDrive. MiXplorer asks for my encfs-password over and over.
MiXplorer's encfs-feature works flawlessly with other cloud storages and locally.
The encfs-folders on OneDrive are accessible by MSWindows software without any problem.

Samsung Note 3, LineageOS 17.1 (Android 10)
Log-file:

MiX-B21040320_2021-04-09_17-29.txt

Shared with Dropbox

www.dropbox.com

 

[Keror0]

Thank you. Try the latest build in the second post, if it's possible on Chrome OS and tell me the result.

Under ChromeOS when attempt to create a file under "My files/", it end up created under a subfolder under it. "My files" is the root internal storage folder as seen from stock ChromeOS file manger.

"My files/" MiX seen as
/storage/0000000000000000000000000000CAFEF00D2019/

"Internal storage/" MiX seen as
/storage/emulated/0/

Reload the folder view at this point "New file under My files.txt" disappeared and it can only be found under the "Keys" subfolder. Related logs as follow:

##### MiX-B21032910_2021-04-09_23-47.txt ************************

MiXplorer v6.53.8-Silver-B21032910
Device: Google Samsung Chromebook 3, Brand:Google
Android Target: 9.0 (Pie, API 28)
CPU ABI: x86, armeabi-v7a, armeabi
------------------------------------
I/STARTUP> Loading started...
I/MiX> Storage: 3 /storage/0000000000000000000000000000CAFEF00D2019
I/MiX> Storage: 2 /storage/emulated/0
I/MiX> Storage: 1 /
I/STARTUP> STORAGE: 163 ms
I/STARTUP> SKINS: 47 ms
I/DB> Refresh DB...
I/STARTUP> DB LOADED: 48 ms
D/THUMB> HEAP SIZE >> 14.34 MiB / 190.38 MiB
I/STARTUP> ICONS: 32 ms
I/STARTUP> ADDONS: 151 ms
I/STARTUP> CLEAR CACHE: 16 ms
D/Storage> --- Documents -----------------------------
D/Storage> /storage/0000000000000000000000000000CAFEF00D2019
D/Storage> -------------------------------------------
I/ROOT> *********************** Not rooted. 66 ms
I/ROOT> Access to root is disabled in the settings.
I/ROOT> ls -lnApSr "/data/data/com.mixplorer.silver/home"
E/ROOT> STD-ERR >> /system/bin/sh: <stdin>[1]: /data/app/com.mixplorer.silver-Uzv7fvY_PZs6ktx2zgg-OA==/lib/x86/libbb.so: not found

D/BR_REC> Received: Intent { act=android.intent.action.PACKAGE_REMOVED dat=package:com.alphainventor.filemanager flg=0x4000010 (has extras) } with action 'android.intent.action.PACKAGE_REMOVED'
I/BR_REC> Package uninstalled > package:com.alphainventor.filemanager
I/ROOT> ls -lnApSr "/data/data/com.mixplorer.silver/home"
E/ROOT> STD-ERR >> /system/bin/sh: <stdin>[2]: /data/app/com.mixplorer.silver-Uzv7fvY_PZs6ktx2zgg-OA==/lib/x86/libbb.so: not found

D/BR_REC> Received: Intent { act=android.intent.action.PACKAGE_FULLY_REMOVED dat=package:com.alphainventor.filemanager flg=0x5000010 (has extras) } with action 'android.intent.action.PACKAGE_FULLY_REMOVED'
D/BR_REC> Received: Intent { act=android.intent.action.PACKAGE_FULLY_REMOVED dat=package:com.alphainventor.filemanager flg=0x5000010 cmp=com.mixplorer.silver/com.mixplorer.BroadcastReceiver (has extras) } with action 'android.intent.action.PACKAGE_FULLY_REMOVED'
D/BROWSE> INTENT > Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10210000 cmp=com.mixplorer.silver/com.mixplorer.activities.BrowseActivity }
D/TAB_BAR> TN 40:1366:12
D/BROWSE> Init Tabs...
I/STARTUP> PAGES: 85 ms
I/STARTUP> UPDATE UI: 221 ms
I/STARTUP> TOTAL: 80942 ms *********
I/MiX> RESUMED
D/HUB> ITEM >> /storage/0000000000000000000000000000CAFEF00D2019
I/ROOT> stat -c %Z "/storage/0000000000000000000000000000CAFEF00D2019"
stat -c %X "/storage/0000000000000000000000000000CAFEF00D2019"

I/ROOT> du -s "/storage/0000000000000000000000000000CAFEF00D2019"
E/ROOT> STD-ERR >> /system/bin/sh: <stdin>[7]: /data/app/com.mixplorer.silver-Uzv7fvY_PZs6ktx2zgg-OA==/lib/x86/libbb.so: not found

I/ROOT> du -s "/storage/0000000000000000000000000000CAFEF00D2019"
E/ROOT> STD-ERR >> /system/bin/sh: <stdin>[8]: /data/app/com.mixplorer.silver-Uzv7fvY_PZs6ktx2zgg-OA==/lib/x86/libbb.so: not found

D/HUB> ITEM >> /storage/0000000000000000000000000000CAFEF00D2019/Downloads
D/STORE> Scan media /storage/0000000000000000000000000000CAFEF00D2019/New file under My files.txt
D/STORE> CURRENT /storage/0000000000000000000000000000CAFEF00D2019/New file under My files.txt
D/STORE> Scanner waiting...
D/LocalServer> Started. Port: 48593 Timeout: 0 sec
D/IntentHelper> START com.mixplorer.silver
D/IntentHelper> URI content://com.mixplorer.silver.file/500!/temp/MiX-Log-B21032910.txt
D/IntentHelper> INTERNAL
I/MiX> PAUSED
I/DB> Refresh DB...
D/MediaHelper> Result: /storage/emulated/0/Android/data/com.mixplorer.silver/cache/temp/MiX-Log-B21032910.txt
I/CodeEditorActivity> Uri: /storage/emulated/0/Android/data/com.mixplorer.silver/cache/temp/MiX-Log-B21032910.txt
I/CodeEditorActivity> INDEX 0
D/CodeEditorActivity> readable: true, path: /storage/emulated/0/Android/data/com.mixplorer.silver/cache/temp/MiX-Log-B21032910.txt
I/CodeEditorActivity> Auto charset > UTF-8
D/CodeEditorActivity> Text > 1
D/CodeEditorActivity> Syntax > 4
D/STORE> Correctly finished > 1
D/STORE> Scanner finished.
I/MiX> RESUMED
D/HUB> ITEM >> /storage/0000000000000000000000000000CAFEF00D2019/Keys
I/ROOT> du -s "/storage/0000000000000000000000000000CAFEF00D2019/Keys/New file under My files.txt"
E/ROOT> STD-ERR >> /system/bin/sh: <stdin>[9]: /data/app/com.mixplorer.silver-Uzv7fvY_PZs6ktx2zgg-OA==/lib/x86/libbb.so: not found

I/ROOT> stat -c %Z "/storage/0000000000000000000000000000CAFEF00D2019/Keys/New file under My files.txt"
stat -c %X "/storage/0000000000000000000000000000CAFEF00D2019/Keys/New file under My files.txt"

I/ROOT> du -s "/storage/0000000000000000000000000000CAFEF00D2019/Keys/New file under My files.txt"
E/ROOT> STD-ERR >> /system/bin/sh: <stdin>[14]: /data/app/com.mixplorer.silver-Uzv7fvY_PZs6ktx2zgg-OA==/lib/x86/libbb.so: not found

 

[IronTechmonkey]

İt is a new video, İ have created yet on the phone. İ am new on this app so İ don't know old versions.

OK, it's a new situation and there is no baseline to compare it to, in other words no situation where you've seen mixplorer on your current device play this file properly. That's good to know. Moving on

İ sent the video to my friend on Telegram and he told me he could watch normally.

That's on a different device, probably downloaded by a different method with other possible variables. Is that even the same version of mix with the same add-ons? This is why details about the device and the file are significant. That may indicate that the original file is not corrupt but does not speak to the download onto your device and play back in MiXplorer.

İ downloaded a mp4 video for trying. İt works. But if İ save with my phone, it doesn't work.

When you save with your phone does it work with other players? This is not to doubt that there could be a bug in mixplorer but with the minimal details you've provided so far this looks like an issue with the downloaded file or available memory on the device. Those two factors are more likely to be the differences between your device and your friends device assuming that both of you attempted to play the file the same version of mix.

If you think it is a bug please see post 7 of the FAQ for advice about how to log and report bugs... or just wait to see what other users and the developer might have to say.

 

[asliaral]

OK, it's a new situation and there is no baseline to compare it to, in other words no situation where you've seen mixplorer on your current device play this file properly. That's good to know. Moving on



That's on a different device, probably downloaded by a different method with other possible variables. Is that even the same version of mix with the same add-ons? This is why details about the device and the file are significant. That may indicate that the original file is not corrupt but does not speak to the download onto your device and play back in MiXplorer.



When you save with your phone does it work with other players? This is not to doubt that there could be a bug in mixplorer but with the minimal details you've provided so far this looks like an issue with the downloaded file or available memory on the device. Those two factors are more likely to be the differences between your device and your friends device assuming that both of you attempted to play the file the same version of mix.

If you think it is a bug please see post 7 of the FAQ for advice about how to log and report bugs... or just wait to see what other users and the developer might have to say.

İ have tried with another app now. İt is working.

So it is a bug for Mixplorer

Thank you