Skip to main content

WiFi File Transfer : Access your phone/tablet storage via WiFi

Have you tried transferring files from your phone or tablet to your PC but just could not get hold of that micro USB cable? If you are the type of person that needs file transfer every now and then but always forget the cables, as long as you have WiFi access, this application can make your life better. The WiFi File Transfer apps allows shares your phone or tablets drive over the air allowing you to transfer data to and from the device through a simple web interface.


To start transferring files, open the application in your mobile device. The start screen will show a basic interface that will let you touch the START button to enable sharing.


After selecting START , the app will display the IP address that you can use to access your phone or tablets drive in a web browser.


In this example, to access my device drive I have to type the address http://10.0.0.19:1234  on my web browser. This  may vary depending on how your network is setup. The PORT NUMBER used can also be configurable. You can also protect the share with a password. All of these settings can be accessed via the apps setting page.


After typing the access address at your favorite browser, the page will ask for a password ( if set ) to continue.


The web interface is easy to use, the folders are listed similar to windows file explorer. Music, photos , videos have their own tab. Users has the option to download, delete, move , make a zip file, create new folder. As an added bonus, the drives memory usage and current battery level is also displayed.


Overall, the application is simple and straight forward to use. It has features for security and the web interface is not bad. You can download the app at the Google Play Store.

Download this application at  
Labels:

Comments

Post a Comment

Popular posts from this blog

Getting Started with Stateless : A Lightweight Workflow Library Alternative for .NET

Image Credit: https://www.pioneerrx.com A year ago, I was looking for a simple workflow manager for a project I was working. Its a medium sized application that involves tracking the state of assets in the system. Back in 2008, Microsoft (MS) introduced new technologies along with the release of Visual Studio 2008: Windows Presentation Foundation (WPF), Windows Communication Foundation (WCF), and  Windows Workflow Foundation (WF). Having worked in a company utilizing mostly MS products for development, my first option was to go with WF. After doing some time reading and studying the library, I paused and decided it was too complex for my requirement. Using WF would be an overkill and the fact that it has, a rather, steep learning curve, there has to be another option. My mind toyed with the idea of developing a simple workflow library myself. It would be a learning experience but it might end up consuming a lot of time. Why reinvent the wheel? So I started querying the ...
Post a Comment
Read more

Hiding Unwanted Python Folders and Files in Visual Studio Code

Visual Studio Code is a universal editor and pretty good at it. However, the explorer view maybe cluttered with the automatically generated folders and files confusing developers. Python is no different. Below are example files and folders generated by Python. The __pycache__ folder and *.pyc files  are totally unnecessary to the developer. To hide these files from the explorer view, we need to edit the settings.json for VSCode. Add the folder and the files as shown below: Copy and paste the lines below : "**/*.pyc" : { "when" : "$(basename).py" }, "**/__pycache__" : true
Post a Comment
Read more

How to Kill a Slow Process using DOS Batch File Script with TaskKill and TaskList

If you are still trapped in the era of batch files and command lines in Windows environment, here is something you can add to your DOS cheat codes.  Lucky for us here, we are still using DOS batch file to implement installation of some updates to our system. Here is a simple batch file script that is designed for slow systems that requires a significant amount of time to kill a particular process. The requirement is simple,  do not start any copying or moving of files until  the process ( i.e. MyProcess.exe) is totally killed by DOS. The simplest solution would be to use TASKKILL to kill the process, wait for a few seconds  then start copying/ moving of files there after. Unfortunately, while we were testing this simple step on a slow machine, DOS would take an awful lot of minutes to kill the process in question. Thus, when our delay is reached, we would encounter error on copying/moving files that is currently used by the unkilled process causing a failure on ...
1 comment
Read more