droid app for apex?

I've asked a bunch of times if anyone wants to help add features but never really got any takers.

There are a few other bugs such as Force-Close if you reload a page while it is processing a current request that are on the list too.

You can call it Beta or whatever you like. It is what it is.

Thanks for the explanation. I have checked my devices and haven't found any special characters in the names, etc.

That said, I have setup Eclipse and the Android SDK a while ago, wouldn't mind taking a stab at fixing some of these issues.
 
Sorry, the list of problems is getting longer...

I never coded for the PFx states. I only have support for AON, AOF, ON & OFF.

I will see if I can get reenergized to fix this this weekend.
 
No don't post a paypal account here. The thread will get locked for sure and Henry will be banned.
Henry, thanks for your support. Keep the spirit alive.
 
That said, I have setup Eclipse and the Android SDK a while ago, wouldn't mind taking a stab at fixing some of these issues.
I can make this open-source and a free app if you'd like to help fix the bugs and develop new features.

I just don't have the time.

It is very easy if you know any java or C++.

We just can't talk about the app here on this forum unless we make it free.

Let me know, I can post the code and point you to exactly where the handful of known problems are. The fixes should be easy but take some time and energy to implement and test.

If you knew about open source code sharing sites that allow check-in/out that would be even sweeter but I don't.
 
FWIW,

I use Henrys app on my Droid-x and it works very well. Every now and then it will hang, but so do plenty of other apps on my Droid.

John
 
I sent all of the source code to a CompSci student who was going to work the bugs and add features as part of a class project. Haven't heard from him in a couple of days though.

Current Bug List:
  • Certain characters in outlet names cause problems: Encode the URI segments used for database access so that if the user has an outlet name with a slash, dash, asterisk, etc it does not cause errors. The problems come from two areas; 1) any character that could mess us the URI string. Format is something like content://segment/segment/segment and there could be chars that impact URI matching or 2) any characters that mess up the final SQL string that does the insert/updates.
  • Profiles Status on Outlets Not supported: Code currently only expects AON, AOFF, ON or OFF for outlet status. Now that people are using LEDs more and ramp profiles there are more instances of PF1 that cause problems.
  • Force-Close if Refresh during Update: Disable 'update' during a current update. This causes a force-close.
  • Update Widget Data: When user manually updates data via the full app, it does not push the new data to the widget.
  • Rotating the screen causes a refresh. Annoying but not a critical failure.
In my opinion the first two bugs are very significant especially the second.

And a couple of important enhancements:

  • Do a daily update that pulls history data at the full 5-minute resolution rather than rely on the x interval polling. Also during this daily job do some database cleanup/purging according to the preferences setting.

Then the wish list items:
  • User settable background image
  • Manual parameters such as alk/ca/etc
  • Notes
  • Export xml data via email
  • Inhabitants database with pics.
 
Finally, with a lot of patience and the help of you guys especially HeneryH and of course a good buddy who devoted 4 hours on my computer, I was able to get this thing properly working.

Thanks everyone.
 
HenryH,
Thanks fort all that you do with this app. It's a great app..but does have a few issues. I hope that others begin to help out. This app has the potential to be great. I wish that Curt would do more to reward those that make huge contributions to the Neptune community like you, Ken, Alan, and so many others that I can't remember. You guys really make the Neptune products 100% better by supporting the Neptune customers. Thanks guys!

--AJ
 
I have my Apex set up where it's accessible through my home wireless IP address, but when trying to use the Android app I just get "Error: HTTP connection failed." I'm using dyndns.com as my host and having issues with that as well, so don't know if they are connected or not.
 
The best test before using the app is to test if you can reach your controller with the regular browser on your phone while in 3g mode (ie not wifi). If your browser work then you are well on your way to getting the app to work. If not, then you need to debug internet connectivity first.
 
Just wanted to give my input, the widget/app is great, does the most basic features and is a good starting point for us all to keep in contact with our tanks while away from home. I just setup my "true" networking last night and it does a good job as before I had nothing, so let's not complain too much. I think that with a little polishing, reworking and especially for Android, establishing a minimum required platform to make it work is essential (2.2+). If I could code, I would volunteer, so since I can't, I will support and have patience for the forth coming updates, great job HeneryH!!
 
Back
Top