rahul43210 / futonic-lockscreenswitchwidget

Automatically exported from code.google.com/p/futonic-lockscreenswitchwidget
MIT License
0 stars 0 forks source link

Application forced closed in normal use on Samsung Galaxy i7500 #7

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Install, put widget on screen.
2. Press the widget 3-4 times (interval doesn't matter that much).

After 3rd press the application doesn't respond anymore and Force Close dialog 
appears. After forced close, you can again use the widget by pressing 2 times. 
3rd time the application stalls and has to be forced closed again.

I'm using last version, 2.0. It's installed on an adapted Android 1.6 (Galaxo 
1.6.3.3) on Samsung Galaxy i7500. Hope another Galaxy user can confirm on an 
original Samsung firmware.

Original issue reported on code.google.com by bas...@gmail.com on 19 Nov 2010 at 10:30

GoogleCodeExporter commented 9 years ago
I cannot reproduce this. If you can please trigger the error again and use the 
android error reporting to send me the details.
I'm testing with Nexus One and Motorola Droid.

Original comment by futonred...@gmail.com on 21 Nov 2010 at 3:55

GoogleCodeExporter commented 9 years ago
I don't have the error reporting, but I managed to get a log and trace data 
through adb.

Original comment by bas...@gmail.com on 21 Nov 2010 at 8:18

Attachments:

GoogleCodeExporter commented 9 years ago
I see the problem. It's crashing on reenabling the keyguard.
This appears to be a android system level bug that was fixed in 2.0 or 2.1.

I'm not sure how to fix it but I'll look into it a bit later.

I only started saving published builds awhile ago but I don't have the previous 
version on hand.

Original comment by futonred...@gmail.com on 21 Nov 2010 at 6:47

GoogleCodeExporter commented 9 years ago
Verified that this was not in 1.5 build.

Original comment by futonred...@gmail.com on 21 Nov 2010 at 7:53

GoogleCodeExporter commented 9 years ago
This fix has been applied as changeset 8a8043f624.
It appears to be some thread lock issue that was fixed in Android Eclair.
If you call reenableKeyguard when the keyguard was already enabled the binder 
call will lockup.

Original comment by futonred...@gmail.com on 22 Nov 2010 at 1:25

GoogleCodeExporter commented 9 years ago
Very fast response. Thank you.

Original comment by bas...@gmail.com on 22 Nov 2010 at 7:36