Closed GoogleCodeExporter closed 8 years ago
I am having the same problem using the pin locking.
Original comment by wilma...@gmail.com
on 22 Aug 2013 at 7:07
I am also experiencing the same problem when either a pin or password is set
on. If I turn it back off dashclock shows back up on the lock screen.
Dashclock cannot be added if security is turned on as the lock screen is locked.
Samsung GS4
4.2.2
Original comment by dkolek...@gmail.com
on 23 Aug 2013 at 5:26
I am having the same problem with PIN security enabled.
Samsung Galaxy S4 (Sprint)
Android 4.2.2
Original comment by irv...@gmail.com
on 3 Sep 2013 at 12:16
I have PIN security enabled because of my corporate email app. DashClock can't
be turned on .
Original comment by mike.me...@gmail.com
on 13 Sep 2013 at 2:22
Same problem fix this please
Original comment by vangelma...@gmail.com
on 15 Sep 2013 at 3:24
Did anybody figure this out yet??
Original comment by slyanks...@gmail.com
on 15 Sep 2013 at 2:57
Can this be updated to work when PIN/pattern/password security is enabled?
Original comment by ponnuran...@gmail.com
on 17 Sep 2013 at 10:01
[deleted comment]
+1 here. when i try on my samsung galaxy s4 mini you cannot use the built in
lockscreen widgets when using pattern/pin lock. it works with swiping to unlock.
as far as i can see android 4.2 (at least on samsung) does not allow using
lockscreen widgets if you use secure lockscreens like pin/pattern/password!
so the whole app at this time makes sense only if you can use lockscreen
widgets at all. it only works with simple security. but why?
other apps like "executive assistant" (it is a usual app, not a lockscreen
widget!) manage to show up before the lockscreen and show calendar stuff and so
on. could the developers provide the app working in the same way to use
dashclock not in a lockscreen widget manner but as a app which integrates
between the power switch and the lockscreen?
Original comment by 2...@gmx.de
on 27 Sep 2013 at 11:45
This is not something developers have control over.
Original comment by roman.nurik
on 10 Oct 2013 at 6:02
Original issue reported on code.google.com by
Cohe...@gmail.com
on 12 Aug 2013 at 8:14