Activity log for bug #1335102

Date Who What changed Old value New value Message
2014-06-27 12:14:49 Thomas Voß bug added bug
2014-06-27 12:15:06 Thomas Voß bug task added platform-api
2014-06-27 12:15:13 Thomas Voß platform-api: status New Confirmed
2014-06-27 12:15:17 Thomas Voß platform-api: importance Undecided High
2014-06-27 12:15:19 Thomas Voß platform-api: assignee Thomas Voß (thomas-voss)
2014-08-19 18:58:40 Thomas Voß platform-api: status Confirmed In Progress
2014-08-19 18:58:44 Thomas Voß location-service: status Confirmed In Progress
2014-08-19 19:05:46 Thomas Voß affects location-service location-service (Ubuntu)
2014-11-14 13:00:34 Thomas Voß bug task added location-service (Ubuntu RTM)
2014-11-14 13:03:18 Launchpad Janitor branch linked lp:~thomas-voss/platform-api/fix-1335102
2014-11-14 13:03:46 Thomas Voß location-service (Ubuntu RTM): status New In Progress
2014-11-14 13:03:48 Thomas Voß location-service (Ubuntu RTM): importance Undecided High
2014-11-14 13:03:51 Thomas Voß location-service (Ubuntu RTM): assignee Thomas Voß (thomas-voss)
2014-11-14 13:04:04 Thomas Voß location-service (Ubuntu): status In Progress Invalid
2014-11-14 13:04:06 Thomas Voß location-service (Ubuntu RTM): status In Progress Invalid
2014-11-14 13:04:13 Thomas Voß bug task added platform-api (Ubuntu)
2014-11-14 13:04:33 Thomas Voß bug task added platform-api (Ubuntu RTM)
2014-11-14 13:04:42 Thomas Voß location-service (Ubuntu): assignee Thomas Voß (thomas-voss)
2014-11-14 13:04:45 Thomas Voß location-service (Ubuntu RTM): assignee Thomas Voß (thomas-voss)
2014-11-14 13:04:48 Thomas Voß platform-api (Ubuntu): importance Undecided High
2014-11-14 13:04:50 Thomas Voß platform-api (Ubuntu RTM): importance Undecided High
2014-11-14 13:04:52 Thomas Voß platform-api (Ubuntu): assignee Thomas Voß (thomas-voss)
2014-11-14 13:04:54 Thomas Voß platform-api (Ubuntu RTM): assignee Thomas Voß (thomas-voss)
2014-11-14 13:04:58 Thomas Voß platform-api (Ubuntu): status New In Progress
2014-11-14 13:05:02 Thomas Voß platform-api (Ubuntu RTM): status New In Progress
2014-11-14 13:14:02 Thomas Voß description The GPS provider implementation takes a wake-lock on behalf of the GPS chipset driver whenever the positioning engine is enabled. We have to make sure that the wake-lock is released as early and as aggressively as possible such that we do not prevent the device from going to deep sleep. The GPS provider implementation takes a wake-lock on behalf of the GPS chipset driver whenever the positioning engine is enabled. We have to make sure that the wake-lock is released as early and as aggressively as possible such that we do not prevent the device from going to deep sleep. From a user's perspective: Battery life is likely to suffer as we do not ensure on this level that the respective wake lock is given up.