search

sleepercode / dashclock

Automatically exported from code.google.com/p/dashclock
0 stars 0 forks source link

Pressing widget buttons does not unlock device (HTC One) #589

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Set Dashclock as "Widget lockscreen" under security settings.
2. Configure Dashclock as desired.
3. Have Dashclock alert(i.e. GMail, missed call, etc)
4. Tap on the alert.

What is the expected output? What do you see instead?
The expected output is that the lockscreen should unlock or prompt for 
passcode/gesture/whatever to unlock it.  Instead, it waits until you pull up on 
the Sense lockscreen to do either of those.

What version of the product are you using?
Dashclock version 1.5

Which device and Android version are you experiencing this issue on?
HTC One, Android 4.3, Sense 5.0, Software version 3.04.651.2, running on Sprint.

Are you using a custom launcher or ROM? If so, which one? Note that custom
launchers and ROMs are not supported.
Stock Sense launcher and lockscreen.

Please provide any additional information below.
It seems HTC uses their own call for unlocking the device that is separate from 
the standard Android calls.  I found the link below that has some HTC 
Lockscreen specific methods.  It may be useful in resolving this issue.
http://www.htcdev.com/devcenter/opensense-sdk/api-reference/?package=http://htcd
ev.com/api/addon-docs/reference/com/htc/lockscreen/open/phone/package-summary.ht
ml

Original issue reported on code.google.com by rougeg...@gmail.com on 7 Oct 2013 at 4:16

GoogleCodeExporter commented 8 years ago 
I have this same issue with an At&t HTC One with the 4.3 update. Also, tapping 
on any widgets (Gmail, etc) does nothing as well.

Original comment by mil...@gmail.com on 10 Oct 2013 at 1:36

GoogleCodeExporter commented 8 years ago 
Yeah, the issue seems to be that HTC's lockscreen uses different commands from 
the standard one.  So most widgets are coded to work with the expected setup 
and not HTC's specific setup.  The two fixes for this would be to either wait 
for HTC to switch to the normal calls(could be a while) or add in the calls for 
HTC devices.  The downside to this is that each and every developer with a 
lockscreen widget will have to apply the fix.

It should be noted that I'm completely guessing about this.

Original comment by rougeg...@gmail.com on 10 Oct 2013 at 3:07