View Single Post
Posts: 171 | Thanked: 337 times | Joined on Jul 2010
#409
Originally Posted by mautz View Post
but could someone check the content of /usr/bin/bt-sleep-monitor?
If this is the formatting issue you mentioned, I think I got it, too.

Code:
$ diff bt-sleep-monitor /usr/bin/bt-sleep-monitor
3c3,4
< #description     : Bluetooth 'LowPowerMode' monitor for SailfishOS ports that face a bluetooth wakelock bug.
---
> #description     : Bluetooth 'LowPowerMode' monitor for SailfishOS ports 
> that face a bluetooth wakelock bug.
8c9,10
< #notes           : Can be used as standalone program or as systemd service
---
> #notes           : Can be used as standalone program or as systemd 
> service
10c12,13
< #How it works... : A dbus-monitor process is listening for different dbus events in parallel:
---
> #How it works... : A dbus-monitor process is listening for different 
> dbus events in parallel:
14,18c17,26
< #                  When an event is triggered the program will decide whether to enable/disable 
< #                  or temporarily disable bluetooth suspend (low power mode).
< #                  If bluetooth is powered and in low power mode, a display event will disable suspend mode for a given time.
< #                  In case there is no bluetooth connection after that time, suspend mode is enabled again. See $BTACTIVE.    
< #Monitor...      : After having launched the script in a console, you can follow a log, as long the console stays open. 
---
> #                  When an event is triggered the program will decide 
> whether to enable/disable 
> #                  or temporarily disable bluetooth suspend (low power 
> mode).
> #                  If bluetooth is powered and in low power mode, a 
> display event will disable suspend mode for a given time.
> #                  In case there is no bluetooth connection after that 
> time, suspend mode is enabled again. See $BTACTIVE.    
> #Monitor...      : After having launched the script in a console, you 
> can follow a log, as long the console stays open. 
23c31,32
< BTPOWER=$(connmanctl technologies | sed -n -e '/bluetooth/,+5p' | grep Powered | awk '{print $3; exit}')
---
> BTPOWER=$(connmanctl technologies | sed -n -e '/bluetooth/,+5p' | grep 
> Powered | awk '{print $3; exit}')
52c61,62
<     if [ "$BTPOWER" == "True" ] && [ "$BTCONNECT" == "" ] && [ "$SLEEPTIMER" == "0" ] ; then
---
>     if [ "$BTPOWER" == "True" ] && [ "$BTCONNECT" == "" ] && [ 
> "$SLEEPTIMER" == "0" ] ; then
84c94,95
<     WATCH1="path='/net/connman/technology/bluetooth',interface='net.connman.Technology',member='SetProperty'"
---
>     
> WATCH1="path='/net/connman/technology/bluetooth',interface='net.connman.Technology',member='SetProperty'"
86c97,98
<     WATCH3="interface='com.nokia.mce.signal',member='display_status_ind'"
---
>     
> WATCH3="interface='com.nokia.mce.signal',member='display_status_ind'"
104c116,117
<     pkill -P $(cat /var/run/bt-sleep-monitor.pid) && rm /var/run/bt-sleep-monitor.pid
---
>     pkill -P $(cat /var/run/bt-sleep-monitor.pid) && rm 
> /var/run/bt-sleep-monitor.pid
113c126,127
<        echo Bluetooth Sleep Monitor is running, pid=`cat /var/run/bt-sleep-monitor.pid`
---
>        echo Bluetooth Sleep Monitor is running, pid=`cat 
> /var/run/bt-sleep-monitor.pid`
123c137,138
< # check for a command switch and call different functionality if it is found
---
> # check for a command switch and call different functionality if it is 
> found
 

The Following 2 Users Say Thank You to dubliner For This Useful Post: