2

I am facing very unclear behaviour on Motorola devices w.r.t. setting its password in non-english language (Hebrew). Let me explain scenario:

  1. Settings -> Language & input -> Google Keyboard -> Input Language -> under 'Active input methods' -> Hebrew checked.
  2. Now, Move back to Settings -> Screen Lock -> password -> choose your password -> Password contains illegal characters. (After typing few Hebrew words, so unable to set password)

    illegal character in English

  3. Settings -> Language & input -> Language -> Set 'Hebrew' as phone language.
  4. Now (All in Hebrew language), move back to Settings -> Screen Lock -> password -> choose your password -> Password contains illegal characters. (After typing few Hebrew words, so unable to set password)

    illegal character in Hebrew

I am not getting why it's showing me this behaviour. In fact, after changing phone language, I should be allowed to set password based on my desired language.

0

In fact, after changing phone language, I should be allowed to set password based on my desired language.

Your assumption here is wrong, at least for stock Android.

Based from AOSP source code that handles the password input for lock screen, ChooseLockPassword.java, inside validatePassword(), here is a snippet that will show the "illegal character" message:

// allow non control Latin-1 characters only
if (c < 32 || c > 127) {
    return getString(R.string.lockpassword_illegal_character);
}

It means that the input only allows characters with code between 32 and 127 (exclusive). They are A-Z, a-z, 0-9 and basic punctuations.

ASCII table taken from http://www.asciitable.com/

Other than those characters, Android won't accept the password and notify the user there is an illegal character.

  • :: Roger that, Now, Motorola's Market released devices, legacy phones and phones to be launched(On which i am working) inherits these generic thing from Android, So this features has to be removed causing confusion & it is bug don't you think so. – Pawankumar Dubey Nov 27 '14 at 10:58
  • Well, I can't say whether it's a bug or not. There is no standard to password validation, so I don't think this is Google/Motorola's fault, if it's considered an issue at all. – Andrew T. Nov 27 '14 at 11:06

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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