# Mobile Reconnection

**URL:** <https://forum.inductiveautomation.com/t/mobile-reconnection/8598>\
**Category:** Ignition\
**Created:** [June 20, 2014, 5:39pm UTC](https://forum.inductiveautomation.com/t/mobile-reconnection/8598 "2014-06-20T17:39:21Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![WildeKurt](https://avatars.discourse-cdn.com/v4/letter/w/50afbb/32.png) [@WildeKurt](https://forum.inductiveautomation.com/u/WildeKurt)\
**Post date:** [June 20, 2014, 5:39pm UTC](https://forum.inductiveautomation.com/t/mobile-reconnection/8598/1 "2014-06-20T17:39:21Z")

</div>

I have a situation where a user first starts a mobile session at one project and then is redirected to another. However it appears that eventually it disconnects I suppose because the wireless connection goes to sleep with inactivity. Then the user must press a restart button and is directed back to the gateway mobile page and must start the 1st project again, log in and then go back to where they were. Is it possible to either redirect automatically to the project they were on when the click Restart or prevent them from having to restart at all?

Kurt

---

<div class="post-metadata">

**Author:** ![WildeKurt](https://avatars.discourse-cdn.com/v4/letter/w/50afbb/32.png) [@WildeKurt](https://forum.inductiveautomation.com/u/WildeKurt)\
**Post date:** [June 23, 2014, 8:57pm UTC](https://forum.inductiveautomation.com/t/mobile-reconnection/8598/2 "2014-06-23T20:57:38Z")

</div>

An update: I’m not sure that it’s because the device went to sleep. The Wifi is set to stay on even when asleep. I set the session timeout very long (8 hours) and it still seems to need a restart after a while. Anyone know what causes this?

Kurt

---

<div class="post-metadata">

**Author:** ![james.hunt](https://avatars.discourse-cdn.com/v4/letter/j/fbc32d/32.png) [@james.hunt](https://forum.inductiveautomation.com/u/james.hunt)\
**Post date:** [July 21, 2014, 4:26pm UTC](https://forum.inductiveautomation.com/t/mobile-reconnection/8598/3 "2014-07-21T16:26:28Z")

</div>

what browser are you currently using to view the mobile client ?

---

<div class="post-metadata">

**Author:** ![WildeKurt](https://avatars.discourse-cdn.com/v4/letter/w/50afbb/32.png) [@WildeKurt](https://forum.inductiveautomation.com/u/WildeKurt)\
**Post date:** [July 21, 2014, 4:58pm UTC](https://forum.inductiveautomation.com/t/mobile-reconnection/8598/4 "2014-07-21T16:58:37Z")

</div>

Chrome 35.0

---

<div class="post-metadata">

**Author:** ![james.hunt](https://avatars.discourse-cdn.com/v4/letter/j/fbc32d/32.png) [@james.hunt](https://forum.inductiveautomation.com/u/james.hunt)\
**Post date:** [July 21, 2014, 7:46pm UTC](https://forum.inductiveautomation.com/t/mobile-reconnection/8598/5 "2014-07-21T19:46:30Z")

</div>

What is most likely happening is the OS itself is timing out on the connection when it goes to sleep since when an OS goes to sleep if suspends all but core functions which would mean it would suspend the majority of its network connections causing the browser to timeout with the connection to the Gateway server. This would mean you would need to re-establish a connection with the headless-client on the gateway.

---

<div class="post-metadata">

**Author:** ![WildeKurt](https://avatars.discourse-cdn.com/v4/letter/w/50afbb/32.png) [@WildeKurt](https://forum.inductiveautomation.com/u/WildeKurt)\
**Post date:** [July 21, 2014, 7:54pm UTC](https://forum.inductiveautomation.com/t/mobile-reconnection/8598/6 "2014-07-21T19:54:43Z")

</div>

That may be (although according to what I can find, the WiFi connection is supposed to stay active). However, it seems the session on the gateway closes regardless of the session timeout setting.