Android Enthusiasts Stack Exchange is a question and answer site for enthusiasts and power users of the Android operating system. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have two-step verification enabled on my Google Account, and I generated an application-specific password for my Android device (Infuse 4G with custom ROM in case that's relevant), and input it. After about a day, the "Sign-in error for" notification appears and I have to generate a new password and input it again in order to use the account. Is this a known issue with two-step verification or is it just me doing something wrong?

share|improve this question
I have been using two-step verification for nearly a year, and have not have any issues on my Droid Bionic (2.3.3) or Transformer Prime tablet (4.0.3). – TomG May 7 '12 at 2:14
You should only have to change your application-specific password if you change your main password. – TomG May 7 '12 at 2:15
I know that theoretically it should work fine. The problem is that the reality isn't exactly matching up with that. – computergeek6 May 7 '12 at 2:25

This sounds very strange. I've generated a few app-specific passwords (which look like "abcd-efgh-ijkl-mnop") for a few devices and have never heard from them since. Google says: "Application-specific passwords do not expire"

On the other hand, main password, which has to be accompanied with security code ("12345") does expire quite quickly. Please, make sure you use 16-letter app specific passwords, not the main password with security code.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.