just tested my tablet.
The first time, I left the browser on STW, then rebooted. The browser re-opens on STW, logged in.
The second time, I left the browser on another site, then rebooted. The browser reopened on the other site. On going to STW, I had to re-log in.
So that got me thinking…
I log in to STW, then go to another site. With that site running, I force close the chrome session and relaunch chrome browser. Browser opens in the “other site”. I go to STW and I have to re-log in again.
To corroborate, I log in to STW, force close the browser session with STW as last site, reopen chrome browser, and I am logged in.
In all of this I have not touched the Cache.
So, in summary, the STW session cookie is not being stored/operating correctly unless it is running on browser session close.
Cougar – see if you can recreate that on your android device. I doubt iDevice does it the same way, but someone might want to try.