As a side note to everyone, I've been revisiting how I currently perform the screen "keep-alive", which also keeps the cpu from sleeping. In the next version, I want to split this between two options:
1) Keep Screen On
2) Keep CPU On
The default for keeping the screen on will be while viewing songs. This won't use extra cpu though, as it will allow the cpu to sleep if needed, unlike the current version. The default for "Keep CPU On" will be "Never". I'm now going to use a different mechanism for keeping the screen on versus keeping the CPU on (as recommended by Google). For people with bluetooth pedal connection issues, they will want to keep the CPU on while viewing scores, or always. My hope is that this may inadvertently fix some of the bluetooth connection issues, as it's more similar to what the Bluetooth Keepalive app does (based on my understanding). Here's hoping... I'll be seeking out feedback when the update is released.
Mike
1) Keep Screen On
2) Keep CPU On
The default for keeping the screen on will be while viewing songs. This won't use extra cpu though, as it will allow the cpu to sleep if needed, unlike the current version. The default for "Keep CPU On" will be "Never". I'm now going to use a different mechanism for keeping the screen on versus keeping the CPU on (as recommended by Google). For people with bluetooth pedal connection issues, they will want to keep the CPU on while viewing scores, or always. My hope is that this may inadvertently fix some of the bluetooth connection issues, as it's more similar to what the Bluetooth Keepalive app does (based on my understanding). Here's hoping... I'll be seeking out feedback when the update is released.
Mike