Little File Explorer – File Manager for Android 1.0 and above
github.com
github.com
I find an on-device file manager really useful. I really like that Cx File Explorer has a built-in text editor and can access my WebDAV files: https://play.google.com/store/apps/details?id=com.cxinventor...
It is the glue that makes my phone much more productive, and not just a consuming device.
On a phone it's fine, but on a tablet, being able to copy things between the two screens is a game changer.
I still prefer Cx because, for some reason, it's about 2.5x faster than Solid when copying files from an SMB volume.
I never ever saw anyone doing it for desktop or server applications.
You can manually remove dependencies or.. I think in the Android world you specify what classes can be reflected on and then strip unused code with Proguard (though I could never get it working with Clojure)
Would love to be corrected if I got any of it wrong
I’m pretty sure that’s exactly what the Google Closure Compiler does: https://developers.google.com/closure/compiler/docs/limitati...
Though it has a ton of restrictions on how you write code and how you can use reflection.
Even C++ you mention does that - you have explicit __attribute__ calls to avoid linker from dropping code you want to keep for reflection purposes.
Like JavaScript?
If you are limiting tooling to subsets, you can also compile subsets of Python or Javascript to machine code.
On Java's case, all AOT toolchains and embedded deployment workflows have supported similar capabilities.
If your app wants to use features which behave differently depending on the OS version, you have to if/else over the OS version. Also, note that the platform's Fragment implementation is deprecated and you might miss ViewModel.
Though it's not without compromises — because of Google's stupid policy that "nothing goes into the system unless it needs direct access to privileged or private system components", RecyclerView, ViewPager, and some other basic UI components are still AndroidX libraries that depend on AppCompat for no good reason. I had to fork them to rid them of that dependency: https://github.com/grishka/LiteX
Is this a supported thing to do? No. Do I care about it being unsupported? Also no.
IME biggest dependencies are not compat libraries or _typical_ dependencies that Android apps need (like image loaders), but anything that involves native code. Media capabilities is one thing, but also solutions for analytics/user monitoring/SDKs for integration with Important Companies are more often than not _massive_, and companies like to track the user from many angles ¯\_(ツ)_/¯
I think android studio even warns you if you call a function from an api level newer than your minimum outside of an if statement checking that you're on a newer version.
Supporiting all file operations via SAF while keeping compatibility back to Android 1.0 with old APIs would also be quite a hellish operation.
Indeed, never looked back after trying FX.
Natively you can use a different theme depending on which Android version the app is running on. The 2.x one on 2.x, Holo on 4.x, and Material on 5 and newer.
It looks like Tibor and Naveen are still in command:
Moving the conf file to it, then picking finding and selecting it wasn't for the faint of heart. Once imported though, WireGuard works perfectly.
I used this to write myself some bash functions so I can pause the chromecast from the CLI. Once connected (with for example `adb connect 192.168.1.243`), you can send a play/pause through adb with just:
adb shell input keyevent KEYCODE_MEDIA_PLAY_PAUSE
I can also trivially start an app like Jellyfin with: adb shell am start -a android.intent.action.VIEW -n org.jellyfin.androidtv/.ui.startup.StartupActivity
If it's helpful to anyone, I threw my bash functions into a gist. These were only intended for private use so don't expect it to be pretty: https://gist.github.com/FreedomBen/8ea4cd890621521fb9bb2bf36...After sourcing, you can use the aliases like `adbplaypause` or call the functions directly. I normally use the aliases
(Which I guess is why it's not available on Play Store).
are you just attempting a low effort gpl3 FUD or are you honestly confused at something concrete that you failed to describe?
Either way, the GPL 3 was designed with signing already being a thing, GPG had been out for 5+ years. And if signing broke the GPL, I imagine Stallman would have been raising a huge fit about it for decades.
or a closed source including a gpl3 Library in its packaging.
both have nothing with the license and are a common FUD argument by people who do not like the implied freedoms of the gpl when arguing for more permissively comercial licenses, so apologize if i wrongly mistook you for the more probable case.
>Currently under 40 KB.
Only 40kb in Java? I am impressed
Only complaint is the format of a date in the README.
>Date : 28-11-2023 dd-mm-yyyy
Please observe RFC 3339.
There is no need to buy a copy of ISO 8601, particularly as I prefer the more specific date formats defined in RFC 3339.