Free Space - Internal Vs. External Storage

WiFi File Explorer displays a number of statistics in the top right corner of its web UI; battery, WiFi signal and free space. The free space on the device is shown via two filled bars representing the external and internal storage, as well as the actual numerical figures underneath.

The confusion lies in what these actually mean; what is the external and internal storage - flash? SD card? Internal memory? Connected drives? Well, that differs depending on the device and the version of Android, so it's quite a hard question to answer. Basically, those free space statistics are retrieved from the Android OS using a couple of lines of code that are supposed to give the "external" and "internal" storage for the system. Because each Android device may implement its storage solution in a different way, depending on the device manufacturer and version of Android, you may find that what the Android OS thinks of as being external, you may think of as internal, or vice versa. Or it may show the same statistics for external and internal. Or you may not have external, yet it tells you that you do. Confusing, huh? I know... my Nexus 4 does not have what I consider to be external storage, i.e. an SD card, yet it tells me that I have 5.67GB of internal storage AND 5.67GB of external storage.

What's even more confusing is that on my old Nexus S and many other devices I have owned over the years, it would give exactly the statistics I would have expected for external and internal storage. The moral of the story is that those couple of lines of code to retrieve these statistics work on some devices, but don't make an awful lot of sense on others. And as far as I know, because of the many different ways storage is implemented across all Android devices, there is no other universal way that should give accurate readings for external and internal storage.

So it's that old Android case of "works on some, but not on all, and some is better than none". If any developers know of a better way of retrieving these statistics, please get in contact with me and let me know.

The Ping Test

A number of my applications (WiFi File Explorer, SECuRET LiveStream and BabyCam Monitor) are all web server based applications (i.e. your Android device acts as a mini web server).  They start up and then prompt you to enter a web address into a web browser on a device on the same network to access the web interface.  Simple enough, but a common problem users email be about is not being able to connect to the application when they actually go to enter the address they have been given.

There are a number of reasons this can happen, and I have already listed out most of those at an article I wrote here at this link.  It's a very useful article and I'd urge you to read it, especially since there are many useful comments from users that have solved the problem in different ways.  However, it's over two years old now, and since writing it I have become better at recognising the cause of problem and finding a much quicker way for you to diagnose it.  So before reading the article linked to above, please read the following...

By far and away, the most common cause of not being able to contact the app when entering the address is simply that your network/router is not configured correctly.  The easy way to determine this is to perform a ping test and the results of this will confirm that or not.  If you don't now how to ping, then read this article.  So just ping the IP address of your Android device from your PC (search Google for how to find out your particular Android device's IP address) and if you don't get a reply, then we can say for certain that your network is not allowing communications between your PC and Android device.  And because these apps all use your local network, this will prevent them from being accessed... so not the apps fault at all!!  If you do get a reply, then your network appears to be OK, and so go back to reading the original article I mentioned in the previous paragraph.

More than likely though, you didn't get a reply in your ping test and the devices can't communicate on your particular network.  In that case, I am afraid it is up to you to figure out what is up with your router/network.  I can't really support you in this case because I have no idea what your network is set up for or what your particular use case for it is, not to mention the many different types of routers on the market than I am not familiar with (I usually forget how to use even my own router!), so I am in no position to offer expert support.  I can however say that a lot of users (more than you probably think) "fix" the issue simply by switching the router off and back on again (I know, right!).  Another common cause can be that you have "Wireless Isolation" (or something named similarly - basically, preventing wireless devices from communicating) enabled on your router, so check that option on your router settings.  Beyond that, I am sure a quick search on Google ("can't ping ip address") will yield enough results to help solve your network configuration problem (that's what I would do anyway).

Hopefully I have provided enough information between this article and the article here for you to be able to support yourself on this one, but if you are still stuck after that or your just need help understanding anything I have already written about, then please feel free to contact me again and I'll try to give you some personal support as soon as I am available.

There Are Just Some Things I Can't Help You With

If you are reading this, then more than likely I have just sent you here after you have emailed me for some support.  Now, I hope you don't think I am being rude or lazy, but sometimes I am just not in a position to help with your request - it's not that I don't want to help you, it's just that in this situation, I can't.

More often than not, the reason I can't help you is because you have asked about something to do with the actual purchasing and downloading of one of my applications from one of the various app stores they are available from.  So you could be having trouble completing the order, or maybe you are getting an error from the app store when you try and download, or perhaps you are being told the app store can't verify your purchase.  The fact is that I am an independent developer and so can only support my own applications; I don't work for any of the app stores and so I don't know how any of those systems work from a users point of view.  Therefore, I can't offer support for them and can only suggest to you to contact the support team for that particular app store.

There is one small exception in that for the Google Play Store, if you provide me with an order number, I can actually see the status of your order (and refund it if necessary).  So if you'd like me to do that then I am more than happy to; just email me with the order number and I'll see if I can help you out.  But also remember that you can see the information you need yourself simply by logging into your Google Wallet account online and looking at your transaction history.  I am afraid I can't offer the same service for any of the other app stores because I just don't have access to that information on an individual order basis.

Another typical reason you may have ended up here is that you are asking questions relating to the general operation of a particular device.  I only have a handful of Android devices myself, so although I may be able to answer a few questions, you are far better off contacting the manufacturer's support team for that particular device.

So sorry I can't be of more help to you in this situation, but hopefully this has prompted you to contact the support team that can resolve your issue in the quickest way possible.  Of course, you may still think I can help you, so please don't hesitate to contact me again and I'll see what I can do.  But just remember, I can only support my own applications... I may occasionally be able to help beyond that in some situations where my applications are a factor, but you are most likely reading this blog post because I already think I am not best person to contact for your issue.

The Dreaded "Server (IO) Error"

Occasionally, there are times when trying to upload a file using WiFi File Explorer PRO that the file won't upload.  If your eyes are in the right place of the screen (the upload section, on the box representing the file to be uploaded) and you are quick enough (before the page refreshes) you may just see the words "Server (IO) Error" and wonder just what on earth that means.

Well, it's a bit of a generic error and as you can see, not very descriptive on its own.  But luckily it only actually occurs in a handful of situations, and after reading descriptions of those below, you should be able to quickly work out which one refers to what you are doing.

So here are the ways in which you can cause the "Server (IO) Error":

1. You are attempting to upload to a read-only area of storage.  Remember that not everywhere you can view on your Android device's storage can be written to (even if you are rooted, as WiFi File Explorer does not support root operations).  If you are unsure of what areas are read-only or not, then I suggest searching the internet for information relating to your device as it can vary greatly.  Also, remember some SD cards have a read-only physical slider on the actual SD card itself and this may have been accidentally (or purposefully) switched on.

2. Your storage is full, or, you would fill it if you upload that particular file.  Not much to explain here other than to check how much storage you are using and delete as necessary if that is the issue.

3. You are uploading a file bigger than 4GB.  I am afraid that is the limit that the Flash plugin used to upload the files is able to handle (perhaps linked to the limit of a FAT32 based file system).

4. Your storage is not correctly mounted.  This doesn't just mean physically mounted correctly into the device, but also logically by the Android OS.  Switching the device off and back on again should ensure it is logically mounted again correctly, but it could also be another app doing something strange to it.

The only other time someone has reported this error, but unrelated to the scenarios above, was to do with his particular Flash installation.  He could get it working on one PC, but not the other.  However, this is purely anecdotal and I can't confirm the validity of his claim that it was to do with the Flash install.  It may be worth bearing in mind though if you can't link the error to any of the descriptions above, so perhaps try updating to the latest version of Flash.

And as always, if you still have trouble after reading this, then please feel free to email me for personal support.

SECuRET SpyCam Video Recording Length

One of the settings that is often questioned by users of SECuRET SpyCam is the Video Recording Length.  It specifies the length of the time you want to record for when you are capturing videos based on a motion trigger occurring.  So for example, the app detects a motion and then it will capture a video for 5 minutes, at which point it will stop and then resume to processing and detecting motion.

The first thing I should point out is why it has to be based on a length of time at all; why can't it just stop recording a video when the motion has stopped?  Well, the reason for that is simply that it is not possible to perform the motion processing on each individual frame coming in from the camera at the same time as video is recording - the two events are mutually exclusive.  So we can't detect when motion has stopped; instead we have to record for the length of time that we think we are going to expect, based on the scene you are detecting motion in.

The range of time you can set the Video Recording Length to be is from 5 seconds to 10 minutes.  So then why is the maximum only 10 minutes - that isn't as long as I want to record for?  Well, firstly there has to be a maximum of some kind, otherwise if it were unlimited there is potential for major problems.  Imagine if you had the ability to set the recording time to infinite, i.e. keep going until there is no storage left.  Sounds like a good idea on paper, but what if you intended to monitor for a very long time (a couple of days maybe) and in the first few seconds of monitoring someone just walked past the camera for a couple of seconds and then nothing else happened   Nothing at all for the next 24 hours.  What are you going to get?  A video of someone walking across the screen and then, depending on how much storage you had left, a really long, boring video of a completely still and uninteresting scene.  Then, when something does actually happen of interest on the second day, you have no storage left to record that all important piece of motion you were trying to detect.

So, the maximum of 10 minutes is there as it feels like a sensible amount of time to expect motion to be occurring or not.  In one video, at best you get 10 minutes of constant motion or at worst you only get 9 minutes and 59 seconds of stillness.  But the beauty of it is that after 10 minutes, if motion is still occurring in your scene, then it will trigger again and start recording another video, and another after that and so on, and so on.  In practice then, the Video Recording Length settings is of little consequence as it will essentially keep recording video for as long as motion is occurring and there is ample storage left - as long as motion is occurring  you will be sure to capture it (albeit over multiple video files).

I hope that clears up the confusion over the limit of the Video Recording Length and why it even exists in the first place.  It basically protects the amount of storage you are using in the most efficient way possible and ensures you don't miss a thing - you can record as much motion as possible and as little stillness as possible.

But I HAVE Already Upgraded!

A common problem when upgrading from the free version of WiFi File Explorer to the paid PRO version is that users try to use one of the features in the PRO version but they are told they still need to upgrade. Typically, this involves trying to perform an upload after upgrading (which is only available in the PRO version) and the user again receives a message saying they need to upgrade to use this functionality.

"But I HAVE Already Upgraded!"

Yes, you have, and you haven't been conned out of money or tricked into paying for something that doesn't exist, or any of the other nonsense I have been accused of over the years. The truth is that if you see this message then you are most likely still using the free version by accident. The other explanation is that your order failed on the Google Play Store (or other app store) and you haven't yet upgraded to the PRO version, so always check that as the first thing.

So assuming that your order was successful and you have paid for the PRO version and you are suffering from this problem, the first thing to do is to uninstall the free version. Like I mentioned earlier, you are most likely still running the free version and that's probably my fault for calling it an "upgrade"; that can imply that you are just adding something to the free version, but it's actually a separate app you are upgrading to. So, as you don't need the free version any more, uninstall it from your Android device (the free version has a white WiFi symbol on the icon and the PRO version has an orange WiFi symbol on the icon with the word "PRO" at the end of the app name) and then you know for certain that when you do run the app it is definitely 100% the PRO version you are running.

And just to make doubly sure that everything is working, close your web browser if you already had WiFi File Explorer open in it while suffering from this problem. It may be that the web page currently in the web browser was one that was served while you were running the free version, so just to make sure it isn't left in there or the cache, close it down and start it up again ready to use with the PRO version.

So very simply:

1) Check your order was successful and you have upgraded to the PRO version;
2) Uninstall the free version;
3) Close your web browser;
4) Start the PRO version (and as you uninstalled the free version, you know you are definitely launching the PRO version);
5) Start your web browser again and enter the address given to you by the app... and enjoy the PRO version!


As always, any questions or if it still isn't working, please contact me at pauldyble82@gmail.com.

Aaaaannnnnd... That's 100,000 Applications Sold!

Over the weekend I managed to pass another massive milestone on the Android development odyssey on which I embarked almost 3 years ago now... as the title and picture imply, I have now managed to sell paid apps (i.e., people actually parting with money!) to the tune of 100,000 units.  And that's just on the Google Play Store - my apps have sold thousands of copies on the Amazon Appstore, SlideME, AndroidPIT, GetJar and even on BlackBerry App World!

I'm extremely proud of that figure and it was certainly not a goal I even dreamed to set myself when I started.  I was surprised when I got to 10,000 and even more surprised when I got to 50,000, so 100,000 apps sold is something I never even imagined I would achieve when I started.

Not quite sure how I got to this landmark and I feel very lucky.  Actually, I do know how I got here, and it wasn't just dumb luck; spending hours of my free time coding away and answering support email after support email at every hour of the day... basically, blood, sweat and tears.  But it's not all bad of course, I've had lots of fun along the way and had the chance to meet some fantastic people who have really helped me out... and a lot of the time they do it for absolutely free.

So what now then?  Press on to chase the next 100,000 sales?  Errr, no thanks!!  As fun and rewarding as it is, the stresses and the pressure of dealing with so many users is not something I really want to have on my shoulders - this is all in my spare time still and I have a full time job and parenting responsibilities to consider.  Checking comments and reviews everyday, looking at my sales statistics, dealing with users that have no right to own a "smart" phone... I am trying to share some of those responsibilities, but still, these are all things that have taken over my life and my free time, and I quite frankly would like my life and my free time back.

And I have already started distancing myself from it for the last few months.  If you have one of my apps, then you have probably noticed that rather than an update every couple of weeks, it's now more like every couple of months.  I also don't (or rarely) obsessively check the comments and reviews for my apps any more - although the majority of them are good, the needlessly abusive ones are just not worth even looking at.  I also have no idea where my apps sit in the charts now, whereas before I would check it pretty much daily.

So I haven't exactly quit - I still support the apps and I have just released a load of cool new features (with some more to come in a couple of weeks)  - but I am certainly sitting back and letting the hard work I have already put in propel it all from now on as it starts to tail off.  I have achieved and experienced more than I had hoped for already, so put it this way, I wouldn't be (too) upset if it all stopped tomorrow...

... but it won't, and this Android stuff can be dangerously addictive.  I hope to receive the new Nexus 7 in a couple of days and I may end up getting a whole new wave of motivation when I get that in my hands.  I am also working on a couple of genuine business opportunities based on the technology in my apps that is away from the model of selling them on app stores, and this is certainly where I have a greater interest now and is where I will focus my energy.  They may fizzle out to nothing, and I get contacted all the time about possibly using something I have written in some fantastic new Android-based product, but the projects I am working on at the moment seem to have real potential... and even if they do fizzle out, it's actually pleasant to be doing some work which isn't rated on a scale of 1 to 5 stars for once!

There's also a project coming up in my full time job where I will need to develop a fairly complex Android app, so it all seems to have been beneficial and worthwhile learning how to develop Android apps in the first place.  So although I am winding down my activity with selling Android apps for a handful of pennies on various app stores, it certainly looks like green robots are going to be entwined with my professional and personal life for a good while longer, be it playing with my new Nexus 7 or writing apps in my real job.

And all this because I decided one lunchtime, in an unusual rush of motivation, that I should stop wasting time reading gadget websites and actually try doing something for myself.  Who'd have thought it, eh!?

Dropbox Support in SECuRET SpyCam

SECuRET SpyCam has recently been updated to provide Dropbox support so that you can automatically upload your captures to your Dropbox account.   For those that aren’t aware, Dropbox is a service that is free to use and allows you to store you files in the cloud so they can be accessible anywhere on a variety of devices, both mobile and desktop.

The exciting thing is, this applies to all captures; photos and videos at all resolutions!  Now, that may not seem that exciting to you at first, but to users who used older versions of SECuRET SpyCam, the only option to automatically send your captures somewhere other than the SD card was to either email or Tweet them... and due to restrictions in both mechanisms, this was limited to only lower resolution photos.

So with this new Dropbox support allowing you to upload photos and videos at all resolutions, this will be a really useful addition for anyone that wants to view their captures remotely.  As the main use case for SECuRET SpyCam is to hide or position your Android device running the app somewhere where you are not able to directly use it, this ability to view all types of captures without having to wait until you recover your device from its hiding place will prove invaluable.

For example, you can position your device somewhere you want to monitor something valuable, like the amazing triple-decker sandwich you just made.  Set SECuRET SpyCam up to record videos on motion detection and enable the Dropbox support to automatically upload your files, and then wait.  You’ll now be able to sit and watch for a video to appear in your Dropbox account of that pesky housemate who keeps stealing your food tucking into your sandwich as they are doing it – caught in the act!  Obviously you would eat the delicious sandwich yourself before anyone else had the chance in this scenario, but I am sure you can think up your own scenarios, depending on what you are spying on!

How do you set it up then?  Easy - just go to General settings in the app and scroll down to the bottom.  Make sure you have Save Captures ticked so that your captures are saved to the device storage, and then click on Dropbox.  Here you can enable the automatic uploads and link your Dropbox account, and if you don’t have a Dropbox account already there is a handy link to sign up from within the app.  Now when you start the app and any motion triggered captures occur, they will upload to your Dropbox account into the SECuRETSpyCam directory which is in the Apps directory.  If you have Dropbox installed on your PC then you can see these new captures appear moments after they have occurred (depending on your network speed of course).

I think this is a really great addition and helps cement SECuRET SpyCam’s position as the ultimate security camera for Android.  I hope you find some interesting ways to use it and I am always keen to hear from users how they are using the app and if they managed to catch any criminals with it, so please contact me if you do.