I have recently setup the mobile app on my droid X2. But, every time that I exit the app, the following error is flagged:

. Error: C_ControlSysXMLServer::ScheduleTermination
TimeStamp: 20:35:35 4-24-13 UpTime: 2 days 00:19:21.71 Task: TCP_Read
Total Errors Logged = 1

My guess would be that something simple or stupid was missed when I set it up. Any input is greatly appreciated.

It works fine this just happens when you exit?

On my Droid I would have to go into application manager and close the services or it would kill my battery in 40min. On my new Note II it works flawlessly.

Exactly. The app runs perfectly, but once I hit the home or back button to exit the error comes up. It does not matter which android device I use, as the same error comes up with either a phone or a tablet. Which, leads me to think I setup something wrong. Any advice regarding setup?

I would think it would be on the SIMPL side of things as setup on the Android is so basic.

yeah. that was my thought also. The mobile logic is currently setup as:

IP ID: 05

string size: 1d

web port: 8081 (web port is set this way, so that I am able to port forward for remote access)

CIP port: 41797

Project: test

passcode: 1234

Did I miss anything?.... the logic block for the mobile is connected to the exact same points as my TPMC-10. Do I need any additional logic for the mobile panel, such as a TCP/IP client or server to make this operate properly?

Thats funny as ive seen these from time to time on my AV2, but couldnt trace it. So I just checked the error log which was clean, then ran my Crestron on my Galaxy S3. I went to a few pages, then hit the back button til it exited the app, then refreshed the error log and found this:

3. Error: C_ControlSysXMLServer::ScheduleTermination
TimeStamp: 20:29:53 4-25-13 UpTime: 0 days 04:05:40.91 Task: TCP_Read

Tried it again and instead used the home button to exit, and the error popped up again. I have the Crestron Mobile symbol setup correctly in the program (pretty much like yours, but perm string size at 255) and have never noticed any performance issues. Maybe should call TB and see what they say about it. At least we can reproduce it.

Gonna try my ipad later when its available. Wanna see if it comes up with that too.

yeah, like I had mentioned before. It flags the same error regardless if it is being run on a different phone, or if it is being run on an android tablet. Still flags the error when you exit the app.