Reef Angel Forum

I've got the features included in the app. I have to update the version and complete the changelog. If all goes well, we are looking at a release in the next few days. So far everything is testing out well on my end. I'm running it on my Galaxy Nexus and Nexus 7 full time and it's functioning like it is supposed to. I just added in the service stopping when the app is not running (with a couple exceptions). So far, so good.

Awesome news. I can't wait to get the update notification and see all this effort for myself!

If anybody wants to help me test it out, I have uploaded the release candidate to my server.
http://curtbinder.info/apps/
It's called AndroidStatus-0.9.0.RC1.apk

It's what I am testing and running on my devices. Also, so you are aware, it's exactly the same signature as the one in the Play Store and when the official release comes out, it will just replace this version. So there's no uninstalling issues and data/settings are the same. You don't have to test things out, but just thought I'd mention it to people. And yes, I will be doing another release for the official build to be uploaded.

I uploaded it to my phone. LOVE the layout. so smooth and practical.
phone is samsung note 2

just uploaded it to my samsung note tablet and it is perfect.

Just loaded it on my Nexus 7 and its great!!!

awesome. let me know if you guys find any issues. i will most likely be releasing it this weekend.

Downloaded on my s3 will let you know of any issues

I works fine on my HTC One X and my new generic 7" tablet, AKA "Reef Angel 7" LCD Touch Control Panel"

Thanks for the hard work!

--Colin

Have downloaded to my Samsung S3 and it seems to work fine but will need to test properly when I get home, am behind a proxy at work and the app is timing out on the away settings.

But looks like a nice upgrade thanks

**Update

Tested from home all functions work great,,,,very nice

Thanks for the effort you must have put in

Curt, I recently upgraded to the Reef Angel 1.0.6 libraries. I just installed AndroidStatus-0.9.0.RC1.apk on my LG-P999 smartphone running Android version 2.3.4. When I attempt to update the main "Controller" view in the Last Updated: I receive Error 23: XML SAX Parser.

My smartphone was working correctly with the released version of the Reef Angel Status application. Not related but I can communicate with the Reef Angel through the Portal application correctly, so Wifi is working.

Any ideas why I am getting Error 23: XML SAX Parser? Is any further configuration required for the RC1 version?

I'm getting this same error code. It worked this morning.

mudcat1 wrote:Curt, I recently upgraded to the Reef Angel 1.0.6 libraries. I just installed AndroidStatus-0.9.0.RC1.apk on my LG-P999 smartphone running Android version 2.3.4. When I attempt to update the main "Controller" view in the Last Updated: I receive Error 23: XML SAX Parser.

My smartphone was working correctly with the released version of the Reef Angel Status application. Not related but I can communicate with the Reef Angel through the Portal application correctly, so Wifi is working.

Any ideas why I am getting Error 23: XML SAX Parser? Is any further configuration required for the RC1 version?

Curt, I can turn relays on and off on the "Main Relay" view so some things are working correctly with the Android app.

I have the EXACT same issues. Plus, the portal is stuck on "Connecting..." Maybe an issue with 1.0.6?

--Colin

cosmith71 wrote:I have the EXACT same issues. Plus, the portal is stuck on "Connecting..." Maybe an issue with 1.0.6?

--Colin

I may have had a similar issue with the dev version, but I was surrounded by buckets, hoses, and in water changing mode, so I dismissed it and went back to the 1.0.5 version...

cosmith71 wrote:I have the EXACT same issues. Plus, the portal is stuck on "Connecting..." Maybe an issue with 1.0.6?

--Colin

Colin,
The Portal application is stuck on "Connecting..." for me too. And the orange lights on my Wifi are flashing furiously.

Bug
It is counting the value 0 as a 0 length number instead of 1 and the HTTP protocol is getting corrupt.

Can you test if this fixes it? This should replace the function inside Globals.cpp

That seems to have fixed it.

Cool beans!!!

Looking at the code again, I think I'll change to this:

rimai wrote:Can you test if this fixes it?

Code: Select all

byte intlength(int intin)
{
	if (intin==0) return 1;
    byte digits = 0;
    if (intin < 0) digits = 1; // "-" counts as 1 character
    while (intin) {
    	intin /= 10;
        digits++;
    }
    return digits;
}

This should replace the function inside Globals.cpp

Roberto, that Globals.cpp change definitely improved things. But I notice another unusual problem. When I updated custom memory location 111 using the Android application it updated the display for Custom 4 memory location on the "Custom Variables" screen in the Android application (as it should), but it does not update the Custom 4 memory location correctly on the Portal. I also notice when I manually switch a relay on the Main Relay view of the Android application it displays a green ball next to the relay. When I turn it off the green ball continues to be displayed. In the old version the green ball would disappear.

mudcat1 wrote:

rimai wrote:Can you test if this fixes it?

Code: Select all

byte intlength(int intin)
{
	if (intin==0) return 1;
    byte digits = 0;
    if (intin < 0) digits = 1; // "-" counts as 1 character
    while (intin) {
    	intin /= 10;
        digits++;
    }
    return digits;
}

This should replace the function inside Globals.cpp

Roberto, that Globals.cpp change definitely improved things. But I notice another unusual problem. When I updated custom memory location 111 using the Android application it updated the display for Custom 4 memory location on the "Custom Variables" screen in the Android application (as it should), but it does not update the Custom 4 memory location correctly on the Portal. I also notice when I manually switch a relay on the Main Relay view of the Android application it displays a green ball next to the relay. When I turn it off the green ball continues to be displayed. In the old version the green ball would disappear.

Roberto,
Disregard the custom variable 4 problem. It just took the Portal some time to respond. Sorry for the confusion.

Thanks for your help,
John

Tap the green ball to make it disappear and turn off the override.

--Colin

cosmith71 wrote:Tap the green ball to make it disappear and turn off the override.

--Colin

That worked. Thanks Colin.

i put the second code in the global.cpp and it worked thanks Roberto

so are all the issues taken care of so far? is there anything that i need to investigate with the pending new release?

it wasn't on you're side Curt it was the new libraries release.

Ademster wrote:it wasn't on you're side Curt it was the new libraries release.

cool. that's what I thought but just wanted to be sure.

binder wrote:so are all the issues taken care of so far? is there anything that i need to investigate with the pending new release?

Curt,
After play with the new code I see a few things that look suspicious. When going into Setting -> Controller Information -> Controller:Labels, the item listed in the 4th position after Temp Sensor 3 says @2131427826 if I select it, it defaults to pH.

When going into Setting -> Controller Information -> Controller:Visibility, the Temp Sensor 1 item is missing. The item in the first position is Temp Sensor 2.

Other than that everything looks great so far. I really like the improvements. One question is there a way to display the current status of the ATO Low and ATO High float switches on the Android Controller display screen?

Thanks,
John