search

santhoshsathish94 / notifications-widget

Automatically exported from code.google.com/p/notifications-widget
0 stars 0 forks source link

New version 1.0.3.1 breaks Nexus 4 wake function #173

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
I updated to the new 1.0.3.1 which resulted in a severe bug.  I am often unable 
to wake the phone from sleep.  I was able to fix the problem by removing the 
widget.  I made the sure the widget was the cause of the problem by adding it 
removing it several times.  

Phone: Nexus 4
OS: 4.2.2

Original issue reported on code.google.com by hause...@gmail.com on 30 Apr 2013 at 8:03

GoogleCodeExporter commented 9 years ago 
I have the same problem, even after updating to v1.0.4.1. Please fix this. 
Thanks

Phone: Nexus 4
OS: 4.2.2

Original comment by mark.lew...@gmail.com on 1 May 2013 at 7:14

GoogleCodeExporter commented 9 years ago 
To give a bit more information, the problem seems to happen after several hours 
since the last reboot. I updated to v1.0.4.1 last night, then rebooted to make 
sure the update took, then left my phone charging over night. In the morning I 
pressed the power button to wake the screen, but nothing happened. I had to 
press it several times and eventually the screen came on. I then rebooted it, 
and then the wake function works fine, but I expect in a few hours it will 
start to go wrong again.
This is a serious problem, as it prevents access to the phone. Please can you 
look into this ASAP. Thanks.

Original comment by mark.lew...@gmail.com on 1 May 2013 at 7:26

GoogleCodeExporter commented 9 years ago 
This is exactly what I'm experiencing.  I tried uninstalling and
reinstalling 1.0.3.1.  It worked fine for an hour and then the problem came
back.

Original comment by hause...@gmail.com on 1 May 2013 at 8:00

GoogleCodeExporter commented 9 years ago 
It seems that completely hiding the clock solves the performance issues, even 
after few hours. 
This is a temporary solution until I release a decent fix for this.

Original comment by leo...@gmail.com on 1 May 2013 at 12:09

GoogleCodeExporter commented 9 years ago

Original comment by ad...@roymam.com on 1 May 2013 at 6:16