Activity log for bug #1590586

Date Who What changed Old value New value Message
2016-06-08 21:56:04 Michael Zanetti bug added bug
2016-06-08 21:56:47 Michael Zanetti bug task added unity-system-compositor (Ubuntu)
2016-06-08 21:56:57 Michael Zanetti bug task added unity8 (Ubuntu)
2016-06-09 02:53:37 Anupam bug added subscriber Anupam
2016-06-09 15:02:39 Pat McGowan canonical-devices-system-image: importance Undecided High
2016-06-09 15:02:39 Pat McGowan canonical-devices-system-image: status New Confirmed
2016-06-09 15:02:39 Pat McGowan canonical-devices-system-image: assignee Michał Sawicz (saviq)
2016-06-09 15:30:44 Michael Zanetti description Dogfooding turbo, it very frequently happens to me that I wake up the device in the pocket (probably home button press) and either launch the emergency call dialer, or enter the wrong pin many times in a row so that the device is then locked for 5 minutes when I want to use it. Also changing all sorts of settings in the indicator has happened a couple of times already. The solution would be to enable the proximity sensor while on the lockscreen (not only during notifications, but in general) and not actually turning the screen on if the sensor is covered. One could argue that the home button should not wake up the device, however, I'm also testing the fingerprint reader and just pressing the home button with my thumb to wake up the device and directly unlock it, is the best thing ever. If we'd disable the home button from waking up the device, it would require me to first press the button on the side, and then move the finger down to the home button to unlock it, breaks the awesomeness of the fingerprint reader. So we should keep the home button enabled, but as proposed above, take the proximity sensor into use to prevent the accidental pocket presses. Also, in the future we might want to wake up the screen by double-tapping on it, which again would require the proximity sensor to guard the situation. Dogfooding turbo, it very frequently happens to me that I wake up the device in the pocket (probably home button press) and either launch the emergency call dialer, or enter the wrong pin many times in a row so that the device is then locked for 5 minutes when I want to use it. Also changing all sorts of settings in the indicator has happened a couple of times already. The solution would be to enable the proximity sensor while on the lockscreen (not only during notifications, but in general) and not actually turning the screen on if the sensor is covered. One could argue that the home button should not wake up the device, however, I'm also testing the fingerprint reader and just pressing the home button with my thumb to wake up the device and directly unlock it, is the best thing ever. If we'd disable the home button from waking up the device, it would require me to first press the button on the side, and then move the finger down to the home button to unlock it, which breaks the awesomeness of the fingerprint reader. So we should keep the home button enabled, but as proposed above, take the proximity sensor into use to prevent the accidental pocket presses. Also, in the future we might want to wake up the screen by double-tapping on it, which again would require the proximity sensor to guard the situation.
2016-06-09 17:45:29 Michał Sawicz bug task added powerd (Ubuntu)
2016-06-09 17:45:37 Michał Sawicz unity8 (Ubuntu): status New Incomplete
2016-06-09 17:45:43 Michał Sawicz canonical-devices-system-image: assignee Michał Sawicz (saviq) Stephen M. Webb (bregma)
2016-06-09 19:09:27 Launchpad Janitor powerd (Ubuntu): status New Confirmed
2016-06-09 19:09:27 Launchpad Janitor unity-system-compositor (Ubuntu): status New Confirmed