I've recently posted this to support but thought I'd share here too. It's quite a techie issue but bottom line is IMO the sonos app is causing battery drain on mobile
I'd be interested if anyone can confirm/reject ...
I have had the 4.1 sonos app installed on two mobile devices
- Samsung S4 running android 4.3
- Samsung Note 10.1 running android 4.1.2
The app basically works well and I love sonos :-)
HOWEVER I'm observed quite a significant issue.
When the sonos app is running, the device does not sleep properly. By this I mean the phone appears to work/sleep normally but the processor is kept running rather than stopped due to what I believe is the phone listening to network broadcasts (probably relating to uPNP)
The impact of this is significant battery loss in "sleep". This can be seen through tools like "better battery stats" which can display "wakelocks". In this case "wlan_rx_wake" is the most significant, showing 10-15% of the monitored time without sonos running, but 30-60% of the time with it running.
The figures will vary on the business of the wireless network. Sonos required to be on same subnet as home, so is subject to pc network broadcasts etc. These figures are after disabling many home broadcasts and are due to I believe the sonos application enabling broadcast/multicast and due to the way the app remains running all the time it is installed - even killing it doesn't help as it restarts.
This behaviour is repeatable and seen with multiple devices. There appears a clear difference between having sonos installed, and not installed.
As above the clear impact here is on standby battery life - it's no trivial and not something I've seen in other apps.
Happy to explain more. I am a software engineer (albeit not android) and it's quite a techie subject that needs further verification/isolation
IMO
a) Unsure why the sonos processes need to run when the app is exited
b) the device should only need to listen to broadcasts/multicast (at this level - arp is already offloaded) when awake. that is the default device behaviour which I don't think the app should change
thanks
I'd be interested if anyone can confirm/reject ...
I have had the 4.1 sonos app installed on two mobile devices
- Samsung S4 running android 4.3
- Samsung Note 10.1 running android 4.1.2
The app basically works well and I love sonos :-)
HOWEVER I'm observed quite a significant issue.
When the sonos app is running, the device does not sleep properly. By this I mean the phone appears to work/sleep normally but the processor is kept running rather than stopped due to what I believe is the phone listening to network broadcasts (probably relating to uPNP)
The impact of this is significant battery loss in "sleep". This can be seen through tools like "better battery stats" which can display "wakelocks". In this case "wlan_rx_wake" is the most significant, showing 10-15% of the monitored time without sonos running, but 30-60% of the time with it running.
The figures will vary on the business of the wireless network. Sonos required to be on same subnet as home, so is subject to pc network broadcasts etc. These figures are after disabling many home broadcasts and are due to I believe the sonos application enabling broadcast/multicast and due to the way the app remains running all the time it is installed - even killing it doesn't help as it restarts.
This behaviour is repeatable and seen with multiple devices. There appears a clear difference between having sonos installed, and not installed.
As above the clear impact here is on standby battery life - it's no trivial and not something I've seen in other apps.
Happy to explain more. I am a software engineer (albeit not android) and it's quite a techie subject that needs further verification/isolation
IMO
a) Unsure why the sonos processes need to run when the app is exited
b) the device should only need to listen to broadcasts/multicast (at this level - arp is already offloaded) when awake. that is the default device behaviour which I don't think the app should change
thanks
