Closed GoogleCodeExporter closed 9 years ago
when you say lock widget you are talking about a third part app?
We can't support third part apps contact the developer of the app
Original comment by jbirdve...@gmail.com
on 8 May 2012 at 7:15
Yes correct. I am talking about a 3rd party app. I understand where you are
coming from but to be clear it is happening on every single 3rd party app
not just one or 2 but I've tried almost every screen off apps repeats the
same issue... and they are all doing the same thing which sorry it makes me
think it is a bug with 1.35
Original comment by brycebur...@gmail.com
on 8 May 2012 at 7:29
your probably right it may well be a problem with our lockscreen but the
lockscreen we use is a highly customized version of the stock lockscreen not
just in add more targets and colors but the code really then entire controlling
class is different.
...I have no idea how they interface with the lockscreen to even begin to fix
it. I'm sorry but without the source code for the app it's hard to debug
anything.
Original comment by jbirdve...@gmail.com
on 8 May 2012 at 7:41
Thank you for getting back to me. I really appreciated it. I understand how
your lock screen is a customized. I know that if I do turn off your lock
screen and try the apps, they work flawlessly. So I could do that. If I
find anything I will let you know, Thanks.
Original comment by brycebur...@gmail.com
on 8 May 2012 at 10:11
Can I ask you one more question please? what is the latest version you
offer for the GSM nexus and how can I tell on the phone if I have
the latest. I believe 1.35 is the latest either way.
Thank you very very much!!!!!
Original comment by brycebur...@gmail.com
on 8 May 2012 at 10:20
To add to my comments I have tried even a "shake to screen off" app and the
same problem appears like the other screen of apps per above. F.Y.I.
Original comment by brycebur...@gmail.com
on 9 May 2012 at 8:16
yes 1.35 is the latest version so far
Original comment by jbirdve...@gmail.com
on 10 May 2012 at 3:15
Thanks!
Original comment by brycebur...@gmail.com
on 10 May 2012 at 9:59
Original issue reported on code.google.com by
brycebur...@gmail.com
on 4 May 2012 at 5:59