No commands after sleep

[DevC]

I have a frustrating issue that I'm trying to figure out. On my test ipad, and also on another ipad (one mini and one ipad 3) I'm using guided access. This prolongs the time it takes for the iPads to turn off their display. The problem is that roughly 1 in 10 times, when I wake it up, the ipad does not send any commands at all. The iviewer app works fine and I can page flip and set joins etc, i.e. the app behaves as its supposed to, but without sending any commands out. The only way to get round this is to quit and close the app, and reload it, after which it works fine again for a while. During these times, I've confirmed that my wifi is working, that the ipad can still browse the Internet (in fact a browser within iviewer still works in this situation) so it's definitely an app issue.

Have you seen this before? I definitely could not put a device into production use that does that

Thanks

[Jarrod Bell]

What versions of iViewer have you tested?
Have you tried the latest iViewer Next v4.0.238?

Regards,

Jarrod Bell
CommandFusion
www.commandfusion.com

[DevC]

im running both the standard iviewer and iviewer next 237. Ive only been using 237 for a few days as testing for the sonos stuff, so ive mainly experienced it in the normal iviewer, but it has definitely just happened to me in 237. Do you think 238 will fix this?

[Jarrod Bell]

Not sure - it's not something I have ever come across personally.

If you are able to narrow it down to a reproducible case, that would help greatly. There might be some process relating to timing, wireless signal strength (speed the wifi reconnects on wake), etc.

How long have you tried waiting before giving up on iViewer reconnecting? Maybe try waiting longer and report back any findings you have.

Regards,

Jarrod Bell
CommandFusion
www.commandfusion.com

--
You received this message because you are subscribed to the Google Groups "CommandFusion Software" group.
To unsubscribe from this group and stop receiving emails from it, send an email to commandfusio...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[DevC]

yeah well thats the interesting thing, ive done a little testing, and i dont know if this is the actual cause, but it seems that upon wakeup, if i press a button quite quickly, ie within 1-2 seconds, it may not respond, but in that case, its not like you wait a few more seconds and it starts working. Its like as soon as you press a button too early, it stops working all together. If you wake up and then wait a few seconds, more often that not it will work fine. LIke i say, that is not proper testing and im sure there have been cases where those scenarios dont happen, but i can try and do some more testing around that area

[Jarrod Bell]

That's exactly the info we're after. If you can reproduce it by following a standardised sequence, and document it, then it will go a long way in finding the issue.

Regards,

Jarrod Bell
CommandFusion
www.commandfusion.com

[Florent Pillet]

iViewer Next 238 (now available on the AppStore) has no additional networking fixes, so it is most likely that the issue you nailed is still present there.

Florent

On Jan 30, 2013, at 3:45 PM, DevC <dchu...@gmail.com> wrote:

im running both the standard iviewer and iviewer next 237. Ive only been using 237 for a few days as testing for the sonos stuff, so ive mainly experienced it in the normal iviewer, but it has definitely just happened to me in 237. Do you think 238 will fix this?

On Wednesday, January 30, 2013 2:12:26 PM UTC, Jarrod Bell wrote:

What versions of iViewer have you tested?
Have you tried the latest iViewer Next v4.0.238?

Regards,

Jarrod Bell
CommandFusion
www.commandfusion.com

--

Florent Pillet - Software Engineering Lead

www.commandfusion.com

[DevC]

ok well ive just done a brief test. In guided access mode, I woke up the ipad with the home button so there is not swipe to unlock. This is how i normally do it. I was swiping on a gesture pad from the second it unlocked and unfortunately (or fortunately depending on how you see it), the commands were sent fine. hmm ill have to keep testing, but it definitely happens i promise!

[JohanJ]

I also see this from time to time but I have never been able to figure out the exact conditions when it occur. I earlier informed Florent about this but I understand that it's little do work with.

No control system react when it happen and one need to restart the app. Wifi is ok and it works fine when restarting.

I planned to add a button for disconnect/reconnect the control systems to see if that "fixes" the connection.

I suspect that it can depend on the sleep state. I have a feeling that it occur more often when the device has been in sleep mode for a longer time. But again, not sure about that.

[Scott Ahlers]

I’m also experiencing the same issue on an iPhone 5 with v4.0.214 build 215. Works fine on a 3GS and a jailbroken 3GS. It’s for our house and you know how the shoe makers kids go shoeless… just haven’t had the chance to troubleshoot.

--

[Florent Pillet]

We fixed an issue with networking being generally unavalaible for 75 seconds after wakeup in some very specific conditions. The fix is in iViewer Next build 237 and up.

Now there *may* be another similar issue lurking, we're going to look deeper into this. DevC did give some interesting bits of information, if you have alternate ways to reproduce please let us know!

An update to iViewer 4 has already been submitted (build 239 will appear in the coming days on the AppStore), but we'll push a hotfix update shortly thereafter in the event there was a remaining issue we could fix.

Florent

--
You received this message because you are subscribed to the Google Groups "CommandFusion Software" group.
To unsubscribe from this group and stop receiving emails from it, send an email to commandfusio...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[DevC]

As JohanJ says, it may be to do with certain sleep states, its a very tricky one to reproduce, but if i try to think back to the times it happens, it may well have been times when it was sleeping for a longer period of time, but id say the difference is minimal, for example ive just left mine for 25-30 minutes and it still works, but im sure there have been instances where i have left it for not much longer than that, say 30-40 minutes, and it hasnt worked. 

All in all its going to take some investigating i think, but at least the problem is not just with me!

[Florent Pillet]

I agree that this class of issue is a tough one to solve, because they are hard to reproduce with certainty -- but be certain that once we can reproduce it, it will get fixed in no time. That's what happened with the 75 seconds reconnection lag: it kept eluding us until someone came up with a 100% reproducable case with certain hardware on the network. Once we could see it happen, it took less than two hours to understand and fix.

So if you keep digging, I'm sure you'll be able to assess the conditions to reproduce this one with certainty.

Florent

On Jan 30, 2013, at 5:51 PM, DevC <dchu...@gmail.com> wrote:

> As JohanJ says, it may be to do with certain sleep states, its a very tricky one to reproduce, but if i try to think back to the times it happens, it may well have been times when it was sleeping for a longer period of time, but id say the difference is minimal, for example ive just left mine for 25-30 minutes and it still works, but im sure there have been instances where i have left it for not much longer than that, say 30-40 minutes, and it hasnt worked.
>
> All in all its going to take some investigating i think, but at least the problem is not just with me!

[DevC]

so ive done a bit more testing. I have guided access enabled and wake up with the home button therefore bypassing the swipe. If i press a macro button after doing waking up quickly, it will only send one of the commands in the macro. This consistently happens so is easy to reproduce, however in this case, it doesnt then stop the app from sending commands at all like with the main issue i raised above, but its something to look at possibly?

[Jarrod Bell]

Is the macro meant to send commands to multiple systems? If so, sounds like just not all the systems have reconnected in time before you fire the macro (and "queue messages when offline" has not been enabled for those systems so the messages are dropped).

Regards,

Jarrod Bell
CommandFusion
www.commandfusion.com

--

[DevC]

yes its multiple systems. Ok ill try those settings, didnt know it existed. However that doesnt sove the original problem that im trying to recreate