All posts by DaveW

Android Beta Testing

By Google - File:Android robot.svg, https://android.com, CC BY 3.0, https://commons.wikimedia.org/w/index.php?curid=44801497It took a while but it got there in the end !

I’ve submitted the first version of the Android app to the Play Store for beta testing. I’ve tested the app myself but I only have a single Android device to test with so feedback, both positive and negative from the beta testers is encouraged.

Please make sure any results from the beta test are accompanied by your Android device details as well – Model, Android version and so on. The more information I have the quicker I can resolve any issues.

This is my first Android project so please be gentle with me…

All those that have contacted me previously regarding an Android version of the app should receive an invitation email from Google in the next 24 hours. If you’d like to sign up for beta testing use the contact form or leave a comment on this post.

Android App Progress

Android app map viewI’ve managed to get some more time to work on the Android app this last week or so and made some real progress. It’s very close to being ready for beta test now with just one more settings page to complete.

The bulk of the work has gone into the map view handling from both the main screen and the saved stockades screen. The app now passes all the unit tests I’ve created for these so I can now move onto the last two outstanding items.
All those that have requested beta access or expressed an interest in the Android version will be notified as soon as it is available for testing. I’d anticipate the app being made publicly available within a couple of weeks of the beta test starting, providing feedback is favourable !

Android App Started

Android App ScreenshotI’ve spent my spare time during the last couple of weeks starting the development of an Android version of the TKController App. I’m targeting it to run on any device running API 16 or higher (Jelly Bean). I only have a single real device to test and develop it on (Samsung S5) and so far development is progressing well.

I’m not sure what the timescales will be to release as this is very much a hobby app and work and other commitments will mean that the amount of time I can devote to it will vary.

The Android App will have pretty much the same functionality as the iOS App. The two apps will also share the device data so as new device support is added or amended then the apps on both platforms will update.

iOS Version 1.4

1.4 has been available for beta testers for a while now and seems to be stable and hopefully existing users will not see much immediate difference from the old version.

There are, however, a large number of changes in the core of the app that will allow me to add new devices and roll out new definitions in a much better way than previous methods that were a bit hit and miss due to caching problems.

This also lays the foundation for functions that will allow users to customise their own device definitions. I’m still working on the UX for that and am still not sure if this should be offered as part of the “pro” version or the current free version.

I’m submitting version 1.4 to the app store for review this evening so it should start rolling out to end users in the next week or so.

Android support ?

It is very much in the early stages but work has started on an Android version of the app. I’ll be making the Android version available for testers in the next few months.

The Android version of the app is expected to have the same functionality as the existing iOS app although Google’s map licensing restrictions may mean some of the user interface options have to be dropped – I’m still investigating alternatives at the moment.

The Android version of the app will use the same device definitions as the iOS app so the two apps will support exactly the same range of devices and will “auto update” as and when new devices are added or existing ones changed.

If you’d like to be added to the Android test group, please use the contact us page with the subject “Android Testing” and you’ll be notified as soon as a suitable test build is available. If you can include your device type(s) in the request and the Android version number you are running, that will be a great help.

Device Definition Changes

The latest version of iOS TKController is nearing completion and should be submitted to the app store in the next week or so. This is very much a “behind the scenes” update  as the vast majority of the changes are to do with the way the app loads it’s device definitions rather than anything immediately visible to the end users.

The new device definitions and the way they are stored and updated should lay the foundation for new features in the future including user custom devices.

China TK 106

Screen Shot 2014-10-29 at 18.59.18This device is from an unknown manufacturer and uses a strange form of the Xexun command set. The command format differs from the Xexun though in that it sends the password as the first part of the SMS message instead of after the command.

Other than that it appears to be very similar to the TK 102 in terms of functionality.

The manual used to configure this device type is: TK106 Manual

The stockade command for this device looks like:

password+stockade 22589155N,113.827732E;22. 559000N,113.897111E

The shock alarm command looks like:

password+shake 5

 

Byte TK 104

Screen Shot 2014-10-29 at 18.45.30This is a very similar device to the Byte TK 102B and uses almost all the same commands.

The main difference from the app’s point of view is that, being specifically for use in vehicles, it has the ability to remotely switch a relay. With the correct installation the relay can be used to enable and disable the vehicle by cutting power to the fuel pump or another circuit that the engine relies on to run.

The primary difference between using the TK 102B device and the TK 104 device type is that, with the latter, you get stop engine and start engine buttons.

A manual for the supported device is here: TK-104 Manual

The command for the stockade looks like this:

stockade+password+space+latitude,longitude;latitude,longitude

The commands to stop and start (resume) the engine via the relay are:

stop+password
resume+password

The shock command is:

shock+password

 

Pro Version ?

I’d be interested in feedback and suggestions regarding a possible “pro” version of the app.

My current “wish list” is this…

The “pro” app would be a paid for app, a small amount, say £0.49 or equivalent. Hopefully the revenue from this would cover the cost of the Apple developer license and web site hosting.

It would not have banner advertising.

Users of the pro app would be able to create their own custom devices and commands within the app. This would include the ability to define the use, visibility and title of all the buttons.

Users of the pro app can submit their custom device definitions for other app users (pro and free) to use. These would be checked prior to being made publicly available.

Users of the pro app will be able to share their custom devices, via email or posted on forums, with other pro users (possibly free users too) who can install them  in their app.