Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App crash when answer call #3

Closed
GoogleCodeExporter opened this issue Jun 18, 2015 · 3 comments
Closed

App crash when answer call #3

GoogleCodeExporter opened this issue Jun 18, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1. Start MyLock in background mode
2. Call your cell
3. Answer the call

What is the expected output? What do you see instead?
Normally no error would appear as the call was answered.  Instead, as the 
call is answered a box appears stating 
Sorry!
 The application myLock (process i4nc4mp.myLock) has stopped unexpectedly. 
Please try again.
Force Close

What version of the product are you using? On what operating system?
I am using http://mylockforandroid.googlecode.com/files/myLock_alpha2b.apk 
downloaded 1/5/2009.  My OS is the Greek 2.1.041 on a rooted droid.

Please provide any additional information below.
The crash seems to occur whether the phone is locked or not.  Also it will 
continue unlocking automatically until it crashes twice, then the auto-
unlock feature no longer works.

Original issue reported on code.google.com by shawndr...@gmail.com on 5 Jan 2010 at 11:07

@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

The latest public version seems to correct this bug.

http://mylockforandroid.googlecode.com/files/myLock_alpha2c.apk

It no longer crashes on my phone (2.1.041greek).

Original comment by shawndr...@gmail.com on 7 Jan 2010 at 5:28

@GoogleCodeExporter
Copy link
Author

Version 2c implemented a fix for this. The cause was a redundant request to 
disengage 
from lockscreen interface. The force close would happen since we were trying to 
refer 
to something that no longer existed on the 2nd disengage request.

Original comment by myLockan...@gmail.com on 8 Jan 2010 at 3:50

  • Changed state: Fixed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant