OI Safe almost always asks me to enter my password twice

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Open OI Safe on a Motorola Droid or Samsung Galaxy Nexus (not sure about 
other Android platforms).
2. The main screen is displayed, and requests your password. Enter it.
3. The screen flickers like it is bringing you to the last password you were 
viewing, or the list of passwords or the category screen, but instead, requests 
your password again.

What is the expected output? What do you see instead?
I expect to be logged into OI Safe and not asked for my password twice.

What version of the product are you using? On what operating system?
1.3 on Samsung Galaxy Nexus running Android 4.04. Was previously on a Motorola 
Droid (original) running 2.2 I believe. Same behavior, only the Nexus is faster.

Please provide any additional information below.

Original issue reported on code.google.com by jlyonm on 28 May 2012 at 2:05

[GoogleCodeExporter]

I tried to repeat the steps but was unable to reproduce the problem on a galaxy 
nexus.

Original comment by VenGeanC...@gmail.com on 16 Jun 2012 at 8:53

[GoogleCodeExporter]

I figured this wasn't a common problem, since I've had it for years and am the 
first one to open a bug report about it.

I would be willing to run a development build and get some debug output if that 
would help understand the problem.

Original comment by jlyonm on 16 Jun 2012 at 9:43

[GoogleCodeExporter]

Original comment by friedger@gmail.com on 4 Jul 2012 at 7:58

• Added labels: Stack-Safe

[GoogleCodeExporter]

I have the same problem, and I'm also willing to do what I can to help debug it.

Original comment by joshua.b...@gmail.com on 12 Jul 2012 at 4:18

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I have the exact same problem on the GNex.  Everytime I enter my password, the 
Master Keypad fades away only to be replaced by another Master Keypad.  The 
second time I enter my pin, it enters the application. It is really annoying.

Additionally, the keypad is infrequently intermittently laggy causing entry 
errors from time to time. 

I LOVE the IO suite of apps and I really appreciate the effort you put into 
them, but such a basic bug going unfixed for over 8 months leaves me wondering 
how safe my passwords are wihin you application. 

Original comment by joe...@gmail.com on 28 Sep 2012 at 5:34

[GoogleCodeExporter]

I have the same problem with OiSafe 1.4.1 on a Google Nexus S running Android 
4.1.2. It doesn't happen *every* time I use OiSafe, but nearly so.

This detail might help - I have noticed that the problem does not seem to 
happen if I manually re-lock using the notification-bar key icon. I *think* I 
only see this problem after OiSafe autolocks (I have auto-lock set to 5-minute 
timeout)

In settings, I have *both* 'lock on screen lock' and and Auto lock timeout 
configured. Perhaps the problem only happens when both conditions trigger a 
lock?

Also: I use the Swype keyboard for my default text input; perhaps that has 
something to do with it? I haven't spent much time with the default android 
keyboard, which I find annoying, but it would be interesting to hear if other 
users that have the same problem also use swype. 

Original comment by jvm...@gmail.com on 9 Nov 2012 at 9:41

[GoogleCodeExporter]

I've got the same problem on my Samsung Galaxy S III.  I'm using Swype 
keyboard, but I also had the problem on my old phone, an HTC Hero, and I was 
not using the Swype keyboard on that, just the standard Android keyboard.

Original comment by ryan.d...@gmail.com on 9 Dec 2012 at 4:23

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

I also have this problem on a Samsung Galaxy S Relay. I'm not using a Swype 
keyboard, and almost always use the hardware keyboard to type my password.

Original comment by jus...@bspk.io on 20 Dec 2012 at 5:22

[GoogleCodeExporter]

I've also had this problem for a few years, across multiple phones and releases.

Original comment by kormat on 25 Dec 2012 at 3:30

[GoogleCodeExporter]

I am also having the same problem on my motorola razr m.

Original comment by spencerl...@gmail.com on 6 Mar 2013 at 9:58

[GoogleCodeExporter]

Hi Users, 

Sorry for the inconvenience happened to you caused by this bug.
Could you please do a small favor for us to figure out whats the exact issue 
here. Since we aren't able to debug the App remotely, Can somebody go through 
below steps and provide us the Android system Log.

[1] Install this App 'aLogcat' into your Device: 
https://play.google.com/store/apps/details?id=org.jtb.alogcat
[2] Open it and Start record the Android system Logcat. [use (>) button]
[3] Reproduce the issue of "OI-Safe" (make sure you demonstrate the expected 
bug at this stage)
[4] Go back to 'aLogcat' App and stop the Log recording.
[5] Save/Email the recorded Log file.
[6] Attach the Log file here.

Thanks, 
Harsha

Original comment by harshaDura on 10 Mar 2013 at 11:37

[GoogleCodeExporter]

Hi again, 

Just FYI, I got to know that Android System logs aren't able to fetch using 3rd 
party Apps starting from Android 4.1 [1] 
So whoever gonna demonstrate the above steps please use Android device powered 
with a version below Jelly Bean - < 4.1 eg: ICS, GB etc

[1] 
http://stackoverflow.com/questions/13243746/read-the-system-log-on-android-4-1

Original comment by harshaDura on 10 Mar 2013 at 12:24

[GoogleCodeExporter]

same here, maybe 90% of the time I have to enter master PW 2x, HTC Rezound 
running stock unrooted ICS

Original comment by john.pen...@gmail.com on 26 Apr 2013 at 1:05

[GoogleCodeExporter]

I only just realised i could just use 'logcat' from the android sdk instead. 
Here's the logs, annotated. I'm wondering however if this issue is already 
fixed by 
https://github.com/openintents/safe/commit/16938b4a93143b60d34bf76b82ce1dc7ed1ba
b18

Original comment by kormat on 28 Jun 2013 at 4:16

Attachments:

• logcat.stream.edit

[GoogleCodeExporter]

I rebuilt OISafe 1.4.1 with the relevant patch applied from 
https://github.com/openintents/safe/commit/16938b4a93143b60d34bf76b82ce1dc7ed1ba
b18 , and i have not had this problem since.

Original comment by kormat on 6 Jul 2013 at 11:21

[GoogleCodeExporter]

Well that's very nice, but for those of us who can't take apart an app and put 
it back together again with shiny new code inside? Seems the fix is there, but 
one of the app devs needs to implement it. Anyone?

Original comment by g.a.hamer on 18 Sep 2013 at 8:36

[GoogleCodeExporter]

The fix is implemented, it just needs to be released.

Original comment by kormat on 23 Sep 2013 at 2:16

[GoogleCodeExporter]

Any update on when this will be released?  I'm still on 1.4.1, and it appears 
to be the most current on Google Play.

Original comment by unkilb...@gmail.com on 2 Apr 2014 at 10:19

[GoogleCodeExporter]

I also would like to know when this fixed will be officially released. 

Original comment by dalelep...@gmail.com on 3 Apr 2014 at 12:18

[GoogleCodeExporter]

Galaxy S4 continues to exhibit this problem as well.
Seems like this has been kicked around long enough by enough users that it 
should have been long ago resolved, no?

Original comment by mightywi...@gmail.com on 22 May 2014 at 7:49

[GoogleCodeExporter]

Looks like the code has been moved to github, so i put a pointer to this thread 
on the github issues tracker: https://github.com/openintents/safe/issues/9

Original comment by kormat on 27 Jun 2014 at 4:44

[GoogleCodeExporter]

FWIW:  I have the same problem but it didn't begin until I switched from the 
alpha-numeric input to the number pad input.  I have switched back and it 
doesn't seem to be an issue now.

Original comment by pobox1...@gmail.com on 11 Sep 2014 at 6:58

[GoogleCodeExporter]

Scratch the above. It still does it. Sorry.

Original comment by pobox1...@gmail.com on 11 Sep 2014 at 10:19