NotificationAction when keyboard is locked
Status: Alpha
Brought to you by:
jonfroehlich
Menu
▾
▴
#30 NotificationAction when keyboard is locked
Has anyone noticed a problem where MyExperience does not come to the foreground when a phone is in "locked" mode?
Over the weekend, I noticed this behavior on an HTC Dash. I could hear the MyExperience NotificationAction prompt, but MyExperience was not in the foreground.
It may be that the screen is not being refreshed when the device is locked or that applications cannot come to the foreground. After unlocking it, I didn't get the MyExperience prompt back again, but I may have been too slow to catch it.
Further testing is required, but thought I'd ask if anyone else has encountered this issue.
An update - we have confirmed that when the HTC is device locked, the phone desktop is displayed and all applications are sent to the background. On a NotificationAction prompt, the phone will play a sound/vibrate, but the application is not brought to the foreground.
If you try to unlock the phone during the notification, MyExperience remains in the background.
To address this problem, we have added code to monitor the device lock status in the registry during a NotificationAction.
If the device was locked, on unlock, we bring the application to the foreground and re-start the notification.
We have experimented with programmatically unlocking the phone by changing the registry values and by sending key presses to the phone. We can change the registry successfull, but that change is not reflected by the UI. We only partially succeeded with the key press solution. Either way, it may make more sense to let the user deliberately unlock the phone, to reduce inadvertant key presses. Our current solution assumes this approach, and then brings the application to the foreground (if unlocked during the NotificationAction.
To address this problem, we have added code to monitor the device lock status in the registry during a NotificationAction.
If the device was locked, on unlock, we bring the application to the foreground and re-start the notification.
We have experimented with programmatically unlocking the phone by changing the registry values and by sending key presses to the phone. We can change the registry successfull, but that change is not reflected by the UI. We only partially succeeded with the key press solution. Either way, it may make more sense to let the user deliberately unlock the phone, to reduce inadvertant key presses. Our current solution assumes this approach, and then brings the application to the foreground (if unlocked during the NotificationAction.