deepskydiver
Lurker
The wifi sometimes disconnects and reconnects very quickly in succession at work. This sometimes causes a weird issue where I can see the home screen but nothing responds. (I lock the phone when not on wifi.)
To attempt a fix I had added a 20 second delay into the task triggered when wifi disconnects so that if it connects again during that time, I can stop it running the rest of the sequence it runs on a real disconnect. So when wifi connects the first thing I do is kill the disconnect task and only continue with the connect task if necessary.
But that's not what's happening, the sequence is below, starting with the exit state.
state exit -> task #2 |------delay-------|
state entry -> task #1
Here's what surprised me: Until task #2 finishes, the task triggered by the entry state #1 won't start. The entry trigger isn't happening on wifi-connected-entry, it's happening when the wif connects and the exit task has completed. Basically after the delay no matter what it is.
Is that expected and is there any way around it?
To attempt a fix I had added a 20 second delay into the task triggered when wifi disconnects so that if it connects again during that time, I can stop it running the rest of the sequence it runs on a real disconnect. So when wifi connects the first thing I do is kill the disconnect task and only continue with the connect task if necessary.
But that's not what's happening, the sequence is below, starting with the exit state.
state exit -> task #2 |------delay-------|
state entry -> task #1
Here's what surprised me: Until task #2 finishes, the task triggered by the entry state #1 won't start. The entry trigger isn't happening on wifi-connected-entry, it's happening when the wif connects and the exit task has completed. Basically after the delay no matter what it is.
Is that expected and is there any way around it?