![]() |
2012-09-10
, 05:19
|
Posts: 277 |
Thanked: 235 times |
Joined on Jan 2012
|
#91
|
![]() |
2012-09-10
, 22:26
|
|
Posts: 426 |
Thanked: 374 times |
Joined on Apr 2012
@ Middle East
|
#92
|
![]() |
2012-09-14
, 09:34
|
|
Posts: 426 |
Thanked: 374 times |
Joined on Apr 2012
@ Middle East
|
#94
|
The Following User Says Thank You to flopjoke For This Useful Post: | ||
![]() |
2012-09-14
, 19:38
|
|
Posts: 426 |
Thanked: 374 times |
Joined on Apr 2012
@ Middle East
|
#96
|
![]() |
2012-09-15
, 23:02
|
|
Posts: 426 |
Thanked: 374 times |
Joined on Apr 2012
@ Middle East
|
#98
|
![]() |
2012-09-17
, 08:33
|
Posts: 277 |
Thanked: 235 times |
Joined on Jan 2012
|
#99
|
![]() |
2012-09-18
, 15:45
|
Moderator |
Posts: 5,320 |
Thanked: 4,464 times |
Joined on Oct 2009
|
#100
|
Right. I think I misunderstood your original posting. I thought it was, because of the scanning setting, asking you for internet connection. But it was asking because you had no connection at all (no GSM nor WLAN).
But like you said, it's good to get different experiences on this so that good solutions for different use cases are found (with or without ProfileMatic).
So to help with that, I'll write here what I understand to be the commands to disable and enable WiFi scanning.
Disable WiFi scanning:
Restore WiFi scanning (every 5 minutes):Code:gconftool -s /system/osso/connectivity/network_type/search_interval -t int 0
You should be able to enter these commands directly to ProfileMatic's custom action's to bind them to conditions you wish. Or, of course, run them directly from terminal.Code:gconftool -s /system/osso/connectivity/network_type/search_interval -t int 300