The initial report was a bit unclear but the reset suggested here https://forum.xda-developers.com/t/...y-featured-file-manager.1523691/post-88353705 fixed the issue.
The initial report was a bit unclear but the reset suggested here https://forum.xda-developers.com/t/...y-featured-file-manager.1523691/post-88353705 fixed the issue.
@HootanParsa
Thanks for the new beta with split APK sharing. It's really handy and works great! As for accessibility of checkboxes , in the new 6.62.0 beta the state change is now spoken as "sellected" / "not selected" instead of prior "checked" / "not checked". The older wording is more logical for settings cause they represent enabled / disabled state, not item selection. But the main problem remains: their state is announced only when toggling them, not when navigating between them. In fact, it's not possible for an accessibility user to know that they are checkboxes without trying to toggle them on/off first. Compare this to standard Android checkboxes, which work correctly in all cases.
Thanks for the new beta with split APK sharing. It's really handy and works great! As for accessibility of checkboxes , in the new 6.62.0 beta the state change is now spoken as "sellected" / "not selected" instead of prior "checked" / "not checked". The older wording is more logical for settings cause they represent enabled / disabled state, not item selection. But the main problem remains: their state is announced only when toggling them, not when navigating between them. In fact, it's not possible for an accessibility user to know that they are checkboxes without trying to toggle them on/off first. Compare this to standard Android checkboxes, which work correctly in all cases.
Either of these pairs of descriptors would make the point but in terms of vocabulary, "selected" speaks more accurately to what's going on. To say something is "checked" is a description of a graphic indicator - that there is a check next to it, but the word check means to verify or inspect rather than to choose... and a synonym for choose is "select". Another way of looking at it is that the feature has been selected for use which means you've chosen to use it. To say it has been checked for use implies that it has been inspected prior to use. As I mentioned, functionally it makes no difference to me while using the app but the word selected might be more applicable.
Note: when these phrases are translated into other languages perceptions may vary which is something the developer would take into account but I'm speaking to the English words.
+1 to displaying the the state of the items before we have to interact with the item.
Last edited:
When it comes to checkboxes, the standard words used by accessibility tools on Android and other platforms are "checked" and "not checked". If these settings look like checkboxes with checkmarks, then these terms are the most appropriate, otherwise "on" / "off" are probably the best. "selected" and "not selected" are used mostly for describing cursor/highlight-based selection of, e. g. files or other multiple items. This is what most screen reader users are accustomed to.
How do you "select" a checkbox and its label without toggling it?
For example, See https://support.google.com/accessibility/android/answer/6006598?hl=en. This is how most screen readers work on touch devices these days.
Hello DEV @HootanParsa, I really love your app and appreciate the functionality it provides, as well as the people working on its support and cosmetic features. 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.
More detailed post here where I explain what I'm trying to achieve.
Thanks
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.
More detailed post here where I explain what I'm trying to achieve.
Thanks
Could you please cite this source specifically?
Although I and most users could work with either set of terminology, you have affirmed my point regarding definitions. "Checked" is a description of appearance on screen. "Selected" indicates that an item has been selected or chosen. Regarding the selection of text and other items, yes that is a common use of the word "selected" but the fact that it is common in that context does not preclude its applicability in the other context. We would run out of words quickly if we restricted ourselves to 1-to-1 associations.
If someone says: "What does that checkbox mean?" the answer would be "It means you have selected that item.".
A factor in different perceptions is that though my industry experience "selected" has been used in documentation more frequently than "checked". A reason for this is that when drafting documentation the writers may not know if a radio button or a checkbox or some other method of indicating selection will be used, so the more descriptive and widely applicable term "selected" is used.
That all being said IMO there is definitely something to your case especially if there is a source that can be cited regarding "checked" being the default term in Android or other platforms. Also, when dealing with many languages the word "checked" might be a more common word for some users. Then there would be the average of opinions of MiXplorer users, and most importantly what the developer thinks. Last but not least: Even if "selected" seems to be a more widespread standard, a different terminology might carry more weight if it is attached to accessibility services as you mention (hence my curiosity about that source).
As you can see I can logically argue your case nearly as strongly as I can argue my own personal preference, the point being, let's see what the wider world thinks. Thank you for the food for thought about alternate terminology, or as you might call it primary terminology.
@IronTechmonkey
My point is about consistency and familiarity, not theoretical superiority of any kind. I can't find a single OS / screen reader / app combination where checkbox/switch state is reported as selected / not selected. Therefore, I think, This is probably because these terms are associated with, well, selection of multiple items in a list or with cases where only one option can be selected at a time, like in radio button groups. With TalkBack on Android, standard checkboxes are checked/not checked, switches are on/off and selectable list items are selected/not selected. However, the best way to settle this would be to implement system accessibility interfaces on custom views and entirely get rid of hard coded accessibility strings. This will allow screen readers to consistently present control type/state information the way they want. BTW, the only thing that really maters is correct announcement of state when navigating between these checkboxes. The terminology is not that really important as long as they do this.
My point is about consistency and familiarity, not theoretical superiority of any kind. I can't find a single OS / screen reader / app combination where checkbox/switch state is reported as selected / not selected. Therefore, I think, This is probably because these terms are associated with, well, selection of multiple items in a list or with cases where only one option can be selected at a time, like in radio button groups. With TalkBack on Android, standard checkboxes are checked/not checked, switches are on/off and selectable list items are selected/not selected. However, the best way to settle this would be to implement system accessibility interfaces on custom views and entirely get rid of hard coded accessibility strings. This will allow screen readers to consistently present control type/state information the way they want. BTW, the only thing that really maters is correct announcement of state when navigating between these checkboxes. The terminology is not that really important as long as they do this.
Likewise is my point also about consistency and familiarity however we have different ranges of experience which yields different prespectives.
Nor was I talking about theoretical superiority, in fact adhering to the definition of words is a form of equalization. I’m sharing a different perspective based on different experience (with an admittedly rigid view about vocabulary).
Again, that is to the point of our different experiences. I could produce many examples technical manuals to initial product documentation to end user documentation where the word “selected” is used, and I don’t doubt that in your experience you have seen the word “checked” being used. It’s a big world.
This is where I would defer to accessibility functions regardless of my preferences and opinions (preferences and opinions being different things) … If that is what the native documentation uses and or what the preponderance of users prefer.
That is beyond my experience but seems sensible. Is that the type of thing that gets done in the accessibility services on the device or the individual apps, or both?
Fair point, and agreed. I noticed those odd checkboxes and I’m glad you reported them. I’d be just fine calling them them checked, selected, chosen, those little squares, or whatever, as long as we don’t have to interact with them to discern their current state.
Hi there, I've seen the update and I've digged around, and seems like the fall of speed through SMB3 is still a thing.
I was wondering if there was some kind of update for a fix for that issue.
The main issue is that while other clients (and MiXplorer in the past) use to get full SMB speed, since the Android 12.1 update the speed of transfer fell dramatically.
The other clients (CX Explorer ie) keeps doing 20 to almost 50MB/s through wifi, while MiXplorer keeps stuck on 6 tops.
I don't mean any kind of hars tone on the post, I really love this client as it does exactly what I need how I need, but it is really annoying when I do have to do several GB transfers and I'm stuck at those speeds, partially with the time and battery consequences.
My previous post, just in case:
I was wondering if there was some kind of update for a fix for that issue.
The main issue is that while other clients (and MiXplorer in the past) use to get full SMB speed, since the Android 12.1 update the speed of transfer fell dramatically.
The other clients (CX Explorer ie) keeps doing 20 to almost 50MB/s through wifi, while MiXplorer keeps stuck on 6 tops.
I don't mean any kind of hars tone on the post, I really love this client as it does exactly what I need how I need, but it is really annoying when I do have to do several GB transfers and I'm stuck at those speeds, partially with the time and battery consequences.
My previous post, just in case:
@IronTechmonkey fussy alert: I think If someone says: "What does that checkbox mean?" the answer should be "It means you have selected the option identified by that item.".
Point taken. I was mistakenly describing the check itself rather than the checkbox, and perhaps going a bit too far down the rabbit hole.
It should be done inside an app that uses custom controls. If only standard OS controls are used, there's usually no need for such things. They already provide all type/state info needed for accessibility services to work properly.
" symbol present in the installed apps names creates confusion with the app name.
MiXplorer_v6.62.0-Beta_B23040410:
While opening (more than one) audio file, no duration or progress is shown - only the bar is seen - and after the file completes playing, the title is not changed for the next file. This is regarding the statusbar notification, pl. note.
Attachments
I wonder if it would be possible to add an option "Select Random File" or "Select Random Folder" in the three dots menu?
There's a Random Selection Tool for Windows which does it.
It could be useful when when we don't know which folder with ebooks / audiobooks start reading / listening, or which film start watching. I think such option could be an unique addition that no other file managers for Android have, and the implementation shouldn't be too hard.
There's a Random Selection Tool for Windows which does it.
It could be useful when when we don't know which folder with ebooks / audiobooks start reading / listening, or which film start watching. I think such option could be an unique addition that no other file managers for Android have, and the implementation shouldn't be too hard.
Please tell me how I can save several commands when using the Menu option - Execute? I have to have a separate text file with my favorite one-line commands in order to use them as needed...
It would be great if you could see the command history in the input window (Execute). Thanks
It would be great if you could see the command history in the input window (Execute). Thanks
And more) When viewing images, they can be marked (long tap). Immediately, in the viewing mode, the marked files can be deleted (Menu - Delete) or copied (Menu - Share => Copy to ...).
But I don't understand how I can move these marked photos? Please help.
P.S. It would be great if the images marked (in viewing mode) would remain marked even after exiting Viewing Mode...
But I don't understand how I can move these marked photos? Please help.
P.S. It would be great if the images marked (in viewing mode) would remain marked even after exiting Viewing Mode...
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
10
MiX would have the developer's key and not F-Droid's. F-Droid cannot build MiX, it is not open source and the code is not available. The person setting up the repository also cannot build it for the same reason.
The ( terrible, awful ) idea was that someone ( NOT F-Droid themselves, but the person you quote ) wanted to set up a repository mirroring the developer's drive, copying the builds there ( illegally, since this is proprietary software with a license ) to distribute them.
Edit : And you've just proven one of my points. People will be confused and misled about this whole idea, just as you have. Let it die, stop.
[APP][2.2+] MiXplorer v6.x Released (fully-featured file manager)
[APP][2.2+] MiXplorer (full-featured file...
forum.xda-developers.com
8
The file with "API29" in its name declares itself as using version 29 of the Android API. Sometimes an app that claims it is targetting an older version of the API is allowed to do something that used to be allowed but is no longer allowed.
Use the file that does not mention API. If you have a problem, like being unable to write to an external SD-card, you can try the other version. Or ask here and see if anyone thinks it will help.8
In Name mode (i.e. not Regex, etc), use %A%N as the name, and %01d in Advanced settings > Incremental number format. Preview available from the drop-down menu next to the name field.
Edit: mind the space at the beginning of the default ' (%...d)' format. %01d is equivalent to %d. The 0 enables 0-padding. The digit(s) after the 0 specifies the minimum length of the resulting increment, padding it with zeros where necessary. Feel free to add any alphanumeric or punctuation characters (except /:\$% and maybe more) before % and after d, e.g. 'Picture %03d — '.77
Actually that's not entirely correct as F-Droid will replace the author's key with their own. They use the same key for each and every app in the repo. If you install any app from their repo, and then download an update directly from the original source, Android will refuse to update and you would need to reinstall the app.
It is perfectly possible to get instant updates for MiXplorer (or any other app for that matter) by using Obtainium! It can update your apps from the official (or any other) source directly, such as GitHub/Gitlab/custom F-droid repo's/any HTML page etc.
It will automatically check all available .apks from the configured source and look for the newest version for your architecture. If there is a newer version it will let you know and can update the app. You can even search for any app inside Obtainium and it will automatically search GitHub and then let you pick the right one from a dropdown with results. You only have to do this once per app and then you are set for life.
Obtainium is much faster as you get updates directly from the source and you don't have to wait for e.g. F-droid to sign and put the new version in the repository. Nowadays my updates almost exclusively come from Obtainium and not from Playstore or repo's that always lag behind.
More importantly it is much more secure, and not just because of instantaneous updates. If a third party repo that is distributing multiple self-signed apps gets compromised, so will each one of those apps on your phone, generally giving much wider system access and permissions.
The biggest problem with the F-droid repository is that developers' keys get removed and replaced with F-droid's own key. Thus all apps get signed with the same key. If this ever gets compromised than each single one of the F-droid apps will be. This makes it very attractive for hackers to target such a repository, as they can push updates to millions of users all with the same key.
Downloading from the source avoids this problem as each app will be signed with the developers' own keys, thus even if a malicious actor compromises the source, they would still need the developers' own key or Android will block it. If they only have the key, not control over source, no problem either. There's no single point of failure.
Going after a single developer is much less lucrative, and also harder, because their IP-adress is not publicly linked to the repository (unless self-hosting). Signing happens on a completely different private system, and only the .apk, not the key can be found at the source. In case of F-droid, hackers already know pretty much where they need to penetrate, simply by resolving the URL. The signing happens automatically and continuously on their server as new versions come out.
The app is pretty new, but gaining traction and updates very regularly with new features coming in lightning speed. I haven't had a single app that I couldn't get to work with Obtainium. The only downside is that you'll have to remove any app installed from the F-droid repository and then reinstall with the .apk from the source, as they will have a different key. Removing and reinstalling can be done through Obtainium though.
Upside of using source apk instead of Google Playstore version is that there are no automatically included Google Firebase and other trackers added in without the dev choosing to put it in their build.
Most apps can be found on Github/Gitlab and will be set-up in a few seconds due to their seamless integration(set-up a personal acces token for faster search results). If you're too lazy to confirm / look-up the source for each of your apps you could even import a backup from a user that has already configured all sources (optionally delete any apps from Obtainium that you don't have, and add-in any missing apps).
Of course you can also just add MiXplorer and leave it at that! -
2925Downloads
Download the latest updates from Drive.
The latest MiXplorer (com.mixplorer API-29 & API-33)
Download the latest BETA from here:
Get MiX Silver
from Play Store (com.mixplorer.silver)
to support the development of this project.
Downloads from any other source are not recommended.
FAQ MiXplorer Q&A and FAQ (User Manual)
LOG How to report a bug
If you're going to report a bug, first install the latest BETA, try to reproduce the error, then if it's still happening, write a post and explain the issue with the attached log file from the main menu > Send log. Thank you.
Some Tipes:
• Swipe the left-center edge will open the drawer.
• Allow Background Activity from Android settings + Apps + MiXplorer + Battery usage.
• If user is anonymous in FTP-Client, working directory on the server will be read-only. Default user is Admin. Set a password to prevent your neighbors from even reading your files.
• Themes by @djdarkknight96
• Themes by @TerrorFlatRider
• Themes by Vladimir
• Windows Fluent Design theme by @marciozomb13
• Material Design theme by @marciozomb13
• Theme Corporate
• Guillaume Skins Gallery
• YandLiu Skins Gallery
•Skins by @scohut2383[APP][2.2+] MiXplorer (full-featured file manager)
Hello everyone!
My name is Hootan. I work on XDA in my free time and this file explorer is my favorite Android project!
MiXplorer mix of explorers (SD, FTP, Lan, Cloud and other storage explorers) is a fast, smooth, beautiful, reliable and full-featured file manager with a simple and intuitive user interface.
This app has no ads, is and will always remain free.
It supports Android 2.2+ (Froyo)
I hope you enjoy it.
Features
The best way indeed is to explore yourself. But here's a brief list of essential features:
FAQ MiXplorer Q&A and FAQ (User Manual)
LOG How to report a bug
If you're going to report a bug, first install the latest BETA, try to reproduce the error, then if it's still happening, write a post and explain the issue with the log file from the main menu > Send log. Thank you.
If you have any ideas, suggestions or you found a bug/mistake, feel free and let me know.
Email: [email protected]
Screenshots423Changelog
v6.63.0_B23042410:
• Added 'Extract' option in the main menu inside the opened archive.
• Added 'MoveTo...' option in Image viewer menu.
• Added 'Shuffle' option in Sort menu.
• Some changes to prevent users from executing AutoTasks in a wrong destination.
• Remove OpenWith... from OpenAs... dialog and instead added a new item for all possible activities.
• Some other fixes and optimizations.
v6.62.3_B23041810:
• Fixed some issues with SFTP server.
• Fixed stopping local server.
• Some other fixes and optimizations.
v6.62.2_B23041410:
• Fixed login to mega cloud storge.
• Fixed opening CBZ files with some apps.
v6.62.1_B23041310:
• Added Viber bookmark support.
• Fixed some issues.
v6.62.0_B23041210:
• Added SYNC option for Auto-Task > COPY.
• Added sharing split app from APP category.
• Added 'encrypt_data' option for SMB3 in the advanced settings of the SMB client, and it's disabled by default.
•Disabled 'Show hidden files globally' by default. Change it from VIEW>Options.
•Enabled 'Swipe down to show/hide hidden files' by default. Change it from VIEW>Options.
• Some fixes and optimizations.
v6.61.7_B23032410:
• Fixed external storage issue in Android 6.
• Some other tiny fixes.
v6.61.6_B23031310:
• Some fixes and tiny improvements.
v6.61.5_B23030520:
• Fixed some random crashes.
• Fixed translation issues.
v6.61.3_B23022830:
• This folder '/data/user/<UserID>/com.mixplorer/Home' will be recognized as default Home. You can add it manually or 'Reset defaults' from the bookmarks menu. Or long-press on the tab title of previous Home address and 'Set as Home'.
• Some fixes and optimizations.
v6.61.1_B23022610:
• Fixed some issues with drawing icons.
• Removed the indicator where you can open the left drawer. Now you know how you could swipe the left edge to open the left drawer instead of going back.
v6.61.0_B23022520:
• Added 'Set app icon' in the action menu for folders.
• Added 'Same extension' option in address bar menu in the action mode.
• Added 'Full view thumbnails in gallery mode' option in Toolbar > VIEW > Options. You need to long-press on the address bar and clear the thumbnails cache.
• Added an indicator line at the left side of screen to open the left drawer (Android 29+).
• Added monochrome app icon.
• Fixed overwriting files in Box storage with auto task.
• Fixed logging out Mail.ru when exiting the app.
• Notifications must be enabled for MiX to be able to start the servers, find duplicates and...
• You can add the working directory at the end of the deeplinks for the servers. (https://mixplorer.com/app/ftp/trigger/storage/emulated/0/pictures)
• Fixed some other issues.
v6.60.3_B23021520:
• Added an extra option in the network dialog to make sure if we really want to have an extra lock for the cloud storage or not.
v6.60.2_B23021420:
• Fixed an issue with finding local IP addresses.
v6.60.1_B23021210:
• Fixed restoring split apps.
• Disabled Document provider at first run. You can enable it from the settings > Components, if you need it.
• Fixed an issue with scanning local IP.
v6.60.0_B23021130:
• Added WhatsApp, Telegram, Twitter, Instagram bookmarks. Long-press on the address-bar > Enter path (e.g content://mix/whatsapp) and add to bookmarks. Or Reset Defaults from the bookmarks menu.
• Added supporting images for Convert feature.
• Optimized searching speed.
• Fixed stopping servers.
• Fixed crash due to decoding a type of AVIF image. Update MiX-Image add-on.
• Fixed Yandex login issue.
• Some other fixes and improvements.
v6.59.1_B23020180:
• Fixed searching PDF content.
v6.59.0_B23012940:
• Added a separate option for Recycle bin in the settings page > More settings.
• Added deeplinks to turn the servers on and off:
- https://mixplorer.com/app/ftp/trigger
- https://mixplorer.com/app/sftp/trigger
- https://mixplorer.com/app/http/trigger
- https://mixplorer.com/app/smb/trigger
• Some tiny improvements and bug fixes.
v6.58.8_B22090510:
• Enabled Undo feature by default. You can disable it from the settings > More settings > Undo.
• Fixed some issues and tiny improvements.
v6.58.5_B22090510:
• Fixed accessing to /Android/data and /obb directories in Android 12+.
• Fixed crashing while decoding some types of HEIC images.
• Fixed crashing Code editor because of a bug in a system method used by GBoard app on Android 12+.
• Fixed some issues in SQLite DB editor.
• Changed to use the internal browser to login to DropBox by default.
• Added ID3 version options for MP3 files in Tags editor dialog.
• Added Metadata/Tags/Comment option in Search dialog.
• Some other bug fixes and improvements.
v6.58.4_B22020920:
• Fixed some issues in previous builds.
v6.58.1_B22020120:
• Fixed group of issues was made during compiling the codes.
v6.58.0_B22013120:
• Added SFTP and SMB1 servers. (experimental)
• Added 'Reload' and 'Start at the end of text' menu options in Code/Text editors. And 'Tab with 4 spaces' for Code editor.
• Added AXML editor.
• Added 'Don't show in recent activities' option in app selection dialog.
• Added support for AVIF and multipage HEIC images.
• Removed 'Root directory' from FTP server settings. It will be the same as the 'Working directory'. Added 'Force this directory'.
• Moved Add > 'Document provider' to Add > 'Storage'.
• Improved local IP scanner.
• Fixed some issues with editing SQLite files.
• If user is anonymous in FTP-Client, working directory will be read-only. Default user is Admin.
• Many other fixes and improvements.
v6.57.6_B21121040:
• Improved FTP/Share server performance and compatibility.
• Many tiny improvements, optimizations and fixes.
v6.57.5_B21111410:
• Added the list of current possible IPs for the server, in the Server settings.
• Added sending the list of video files in the current folder to MX Player.
v6.57.4_B21111220:
• Added settings to set the server port for SendTo feature.
• Some tiny fixes and improvements.
v6.57.3_B21110910:
• Fixed some issues with FTP(S-ES) server.
• Fixed reading /data/data directory.
• Fixed some other issues.
v6.57.2_B21110510:
• Added SSL option for Servers again.
• Added Explicit mode and content encryption support for FTP server.
• Added Filter extensions for thumbnails. Long press on the address bar.
• Added custom keystore and key manager in the servers settings page.
• Added 'Archive files separately' option in the Archive dialog, if there are multiple files/folders.
• Added starting FTP/HTTP servers without WIFI.
• Added custom IP input in the servers settings page.
• Added 'nameio/block32' filename encoding support for EncFs.
• Added Multi-user support for the servers. Default user is Admin.
• Removed TCP server. Use FTP/Share server.
• Improved Send-To function and added Archive option.
• Fixed an issue with some compressors. Archive add-on needs to be updated.
• Fixed starting servers on boot.
• Fixed an issue with searching files in the system directories.
• Fixed selecting files from Viber and some other apps.
• Fixed adjusting the new file size when editing MP3 tags.
• Fixed an issue with updating the Android media store.
• Fixed typing lags in Code Editor.
• Fixed opening some type of files from Gmail app.
• Fixed selecting files from some other apps.
• Fixed uploading an empty file to OneDrive.
• Fixed editing a text file in OneDrive with Code Editor directly.
• Fixed opening user home directory for FTP server.
• And some other tiny fixes and changes.
393Languages
See List of v6.x language add-ons
If you want to help to translate to your language, send me an email to [email protected]
