-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: Add "Take WiFi Lock" button to SeattleOnAndroid #9
Comments
A workaround is available using system tools: Settings > Wireless & networks > Wi-Fi settings > press Menu button and choose "Advanced" > Wi-Fi sleep policy > select "Never". |
Turns out setting the WiFi sleep policy doesn't solve the problem on all devices. I tested by "Never sleep" works on a ZTE Blade phone running Android 2.3.7, and a Galaxy Tab (GT-P3110) running 4.1.2. Both devices have pretty generous WiFi "tails" even in early-standby modes: The Blade remains pingable for 16 minutes (and seems to disassociate from the WiFi after 20 mins); the Galaxy Tab 19 mins / 24 mins. It doesn't work however on a Sony Tablet S running 4.0.3. Here's the (in)activity pattern I saw when pinging it.
(0) 50 seconds fully on No wonder |
I tried with Sensibility Testbed app on the Sony Tablet S with an open-source app named WiFi-Fixer which unfortunately did not fix the problem; Advanced Wifi Lock did manage to keep WiFi on virtually uninterruptedly on this device. My own attempts adding a user-controlled WiFi lock to our app did not succeed yet, see SensibilityTestbed@7ee9b5c62455f095a8ae5b3908eb1b9eba11deda for details of how I think the implementation should look like. |
It should be possible for researchers using local Android devices running their customized installer to make sure the devices stay on WiFi and not drop into power-saving mode. This would ease the development cycle.
Technically, this would involve making the SeattleOnAndroid app take the WiFi Lock when requested by the user, e.g. by tapping a button in the GUI.
The text was updated successfully, but these errors were encountered: