I dealt with this problem by turning on Bluetooth whenever I
disconnect from my home or work Wi-Fi networks (since I'm using
leaving one or the other in my car). I also turn on BT automatically
whenever a call comes in. In any case, I also use a timeout so that
BT will be turned off automatically in two minutes if I don't connect
to anything. The actual implementation is a little complicated
because I use some variables to interact with other profiles:
1. I have two variables, %NEARHOME and %NEARWORK, which I set based on
Cell Near (for lowest power usage).
2. On Variable Set event for either of those, I turn on Wi-Fi
3. When connected to my home or work access points, I set %ATHOME or
%ATWORK (cleared when not connected).
4. On Variable Cleared for %ATHOME or %ATWORK (ie. I disconnected from
the Wi-Fi), I turn on Bluetooth, because odds are that I'm leaving
home or work in my car.
5. My "turn on bluetooth" action sets %BTTIMEOUT = %TIMES + 120.
6. I have another "watchdog" action that checks if BT is not connected
and %BTTIMEOUT is set and %TIMES > %BTTIMEOUT, then turn off bluetooth
and clear %BTTIMEOUT. If BT is connected, then reset %BTTIMEOUT to
%TIMES + 120.
--Dave
On Jan 31, 2:11 am, Dario Piantanida <
dario.piantan...@gmail.com>
wrote: