foreground app should keep wakelock open until actual suspend happens (aka camera takes ~5 seconds to be responsive after waking phone)
Bug #1309915 reported by
Oliver Grawert
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical System Image |
Fix Released
|
Critical
|
Unassigned | ||
qtmir (Ubuntu) |
Fix Released
|
Critical
|
Gerry Boland | ||
qtmir (Ubuntu RTM) |
Fix Released
|
Critical
|
Michał Sawicz | ||
unity8 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
unity8 (Ubuntu RTM) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
while apps that you put in the background are properly SIGSTOPed
(this is easy to verify with a music streaming website atm (while the browser does not use media-hub it will/should stop playback)).
An app that is in the foreground will try to play on when the system is suspended (easy to verify with the same method, music plays on but becomes stuttery if the browser was in the foreground. This indicates the system tries to suspend but the running app tries to keep it alive.
Unity should send s SIGSTOP/SIGCONT sequence on suspend/resume to the app in foreground when the system goes into suspend and resumes.
Related branches
lp:~gerboland/qtmir/acquire-wakelock
- Michael Zanetti (community): Approve
- PS Jenkins bot (community): Approve (continuous-integration)
-
Diff: 1098 lines (+814/-2)16 files modifiedsrc/common/abstractdbusservicemonitor.cpp (+101/-0)
src/common/abstractdbusservicemonitor.h (+68/-0)
src/modules/Unity/Application/CMakeLists.txt (+2/-0)
src/modules/Unity/Application/application.cpp (+20/-0)
src/modules/Unity/Application/application.h (+4/-0)
src/modules/Unity/Application/application_manager.cpp (+8/-0)
src/modules/Unity/Application/application_manager.h (+3/-0)
src/modules/Unity/Application/sharedwakelock.cpp (+168/-0)
src/modules/Unity/Application/sharedwakelock.h (+50/-0)
tests/modules/Application/CMakeLists.txt (+25/-0)
tests/modules/Application/application_test.cpp (+122/-0)
tests/modules/CMakeLists.txt (+3/-1)
tests/modules/SharedWakelock/CMakeLists.txt (+22/-0)
tests/modules/SharedWakelock/sharedwakelock_test.cpp (+170/-0)
tests/modules/common/mock_shared_wakelock.h (+44/-0)
tests/modules/common/qtmir_test.h (+4/-1)
lp:~unity-team/qtmir/rtm-20150116
- Gerry Boland (community): Approve (functional)
- Mir development team: Pending requested
-
Diff: 1107 lines (+798/-3)17 files modifieddebian/changelog (+14/-0)
src/common/abstractdbusservicemonitor.cpp (+101/-0)
src/common/abstractdbusservicemonitor.h (+68/-0)
src/modules/Unity/Application/Application.pro (+4/-0)
src/modules/Unity/Application/application.cpp (+20/-0)
src/modules/Unity/Application/application.h (+4/-0)
src/modules/Unity/Application/application_manager.cpp (+8/-0)
src/modules/Unity/Application/application_manager.h (+3/-0)
src/modules/Unity/Application/session.cpp (+1/-1)
src/modules/Unity/Application/sharedwakelock.cpp (+168/-0)
src/modules/Unity/Application/sharedwakelock.h (+50/-0)
tests/modules/Application/Application.pro (+16/-0)
tests/modules/Application/application_test.cpp (+122/-0)
tests/modules/SharedWakelock/sharedwakelock_test.cpp (+170/-0)
tests/modules/common/mock_shared_wakelock.h (+44/-0)
tests/modules/common/qtmir_test.h (+4/-1)
tests/modules/modules.pro (+1/-1)
Changed in unity-mir (Ubuntu): | |
status: | Invalid → Confirmed |
Changed in unity8 (Ubuntu): | |
status: | Invalid → Confirmed |
Changed in unity8 (Ubuntu RTM): | |
importance: | Undecided → Critical |
assignee: | nobody → Michał Sawicz (saviq) |
Changed in qtmir (Ubuntu RTM): | |
status: | New → In Progress |
summary: |
foreground app should keep wakelock open until actual suspend happens + (aka camera takes ~5 seconds to be responsive after waking phone) |
Changed in qtmir (Ubuntu): | |
importance: | Undecided → Critical |
status: | New → In Progress |
assignee: | nobody → Gerry Boland (gerboland) |
Changed in qtmir (Ubuntu RTM): | |
status: | In Progress → Triaged |
assignee: | Gerry Boland (gerboland) → Michał Sawicz (saviq) |
Changed in unity8 (Ubuntu RTM): | |
assignee: | Michał Sawicz (saviq) → nobody |
status: | New → Invalid |
Changed in unity8 (Ubuntu): | |
status: | Confirmed → Invalid |
Changed in unity8 (Ubuntu RTM): | |
importance: | Critical → Undecided |
Changed in qtmir (Ubuntu RTM): | |
milestone: | none → 14.09-ota-2 |
Changed in qtmir (Ubuntu RTM): | |
milestone: | 14.09-ota-2 → 14.09-release |
Changed in canonical-devices-system-image: | |
status: | Confirmed → In Progress |
Changed in qtmir (Ubuntu RTM): | |
status: | Triaged → In Progress |
Changed in qtmir (Ubuntu): | |
status: | In Progress → Fix Released |
Changed in canonical-devices-system-image: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
I don't think there's anything unity8 should do here, we already unfocus on locking, or did we lose that in the process?