Closed
Bug 970022
Opened 10 years ago
Closed 6 years ago
Can't unlock PIN SIM, keyboard doesn't show up after restart
Categories
(Firefox OS Graveyard :: Gaia::System, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: flod, Unassigned)
References
Details
(Whiteboard: LocRun1.3)
Attachments
(1 file)
3.76 KB,
text/plain
|
Details |
It happened already two or three times while testing my Keon on master. Everything works fine, I enable PIN SIM to do some tests, enter the PIN and restart the phone (which is set to Italian, but I also tried to switch language). When phone restarts, I'm unable to digit anything: keyboard doesn't show up, not just in the PIN field (Numbers), but also in messages (full keyboard).
Reporter | ||
Comment 1•10 years ago
|
||
First 3 times I just moved the SIM to another phone (Keon running 1.3) to unlock it. This morning I discovered that, If I flash again Gaia on the device, I can unlock the SIM without problems.
Updated•10 years ago
|
Keywords: steps-wanted
Reporter | ||
Comment 2•10 years ago
|
||
I've just flashed the latest Nightly image available from Geeksphone (nightly-images-keon-master-2014-02-09.Gecko-c3810d9.Gaia-b8e6475), and I can't reproduce it anymore, even after pushing my own version of Gaia on the device a couple of times. Previous build from Geeksphone was probably about a week older. Marking as WORKSFORME, eventually reopening if it happens again.
Comment 3•10 years ago
|
||
I ran into this bug during LocRun1.3 and found that it's not a 100% repro for all languages. Some languages I have not been able to reproduce it on at all. You can go back and forth from SIM Pin to the language selection screen and get the issue to repro about 70% of the time with the affected languages. Steps are (with Sim Pin enabled): 1. Reset phone to factory settings 2. Select an affected language 3. Tap Next to go to Sim Pin Repeat Steps 2 & 3 until you see the issue of no keyboard being called. The issue persists after FTE if it reproduced initially. Got a logcat of it reproducing after getting into settings and turning on Developer Options then attempting to go into dialer. Affected Languages: Hungarian French Catalan Czech Bulgarian Bengali Macedonian Netherlands Romanian Russia Slovak Serbian Cyrrilic and Latin Turkish Chinese Simplified Languages that appear to be unaffected: Spanish Greek Chinese Traditional English v1.3 Environmental Variables: Device: Buri v1.3 MOZ BuildID: 20140303004002 Gaia: d51d2e0963d9b761d5ea96243dfb13d9a220d521 Gecko: e5e02efda8ad Version: 28.0 Firmware Version: v1.2-device.cfg
Updated•10 years ago
|
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Whiteboard: LocRun1.3
Comment 5•10 years ago
|
||
Following steps from comment 3: Issue does NOT repro on latest 1.1 on Buri Issue DOES repro on latest 1.4 Master on Buri 1.1 Environmental Variables: Device: Buri v1.1 Mozilla RIL BuildID: 20140306041201 Gaia: 44a2ddf63373f8e95c784faf4ed4d60081699c61 Gecko: 1421a6b7fc51 Version: 18.0 Firmware Version: v1.2-device.cfg 1.4 Environmental Variables: Device: Buri v1.4 Master Mozilla RIL BuildID: 20140306040204 Gaia: 9cb35e701df44766d9b3560b0defe0a401a0ecdd Gecko: 8122ffa9e1aa Version: 30.0a1 Firmware Version: v1.2-device.cfg
Keywords: qawanted
Updated•10 years ago
|
QA Contact: bzumwalt
Comment 6•10 years ago
|
||
Isn't this because since 1.1, you have to enable keyboards for certain locales? I believe that for example in cases when the SIM's not locked, this is also why you don't get a keyboard to show up in other parts of the phone too (sms, contacts), for the same locales.
Keywords: regression
Updated•10 years ago
|
Keywords: regression
Updated•10 years ago
|
Flags: needinfo?(dflanagan)
Comment 7•10 years ago
|
||
(by enable, I mean customizing the GAIA_KEYBOARD_LAYOUTS)
Reporter | ||
Comment 8•10 years ago
|
||
(In reply to Delphine Lebédel [:delphine - use needinfo] from comment #6) > Isn't this because since 1.1, you have to enable keyboards for certain > locales? If the problem is exactly the same I reported, that shouldn't be the case: you could not enter PIN after a reboot, nothing changed between setting the PIN and the next boot (keyboard was set and working correctly when you entered PIN). I haven't seen this lately to be honest, so it could be a different issue.
Comment 9•10 years ago
|
||
The STR in comment 3 is slightly unrealistic. Can we nail down the STR a bit deeper to something doesn't involve repeating steps 2 & 3?
Keywords: steps-wanted
Comment 10•10 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #9) > The STR in comment 3 is slightly unrealistic. Can we nail down the STR a bit > deeper to something doesn't involve repeating steps 2 & 3? I think Delphine is correct in Comment 6, after further investigation it seems this is an outcome of Bug 968961. User cannot enter a Sim PIN (Number Keyboard missing) when selecting a language that does not have an associated language keyboard. The steps: 1. After a fresh reset to Factory Settings with a SIM that has a Pin setup 2. Select Hungarian 3. On next screen SIM Pin is requested but no number keyboard is displayed this also occurs after setup when trying to activate dialer. Workarounds: Restarting phone does not recover, Go to Settings> Keyboards: Note only (Number Keyboard) is enabled, activate a language keyboard. Now the number keyboard shows for Sim Pin.
Keywords: steps-wanted
Comment 11•10 years ago
|
||
I'm not sure what info is needed from me here at this point... If I understand the comments this happens for builds that have locale support for a language but not keyboard support for that language. Do we ever produce production builds like that? If so that seems like a bug in the build process. But perhaps this means that we should be falling back to the english keyboard somewhere and we are not? (I say english as a fallback because that one has lots and lots of accented characters defined.) Of course that might cause english autocorrection which would be bad. Setting needinfo for Rudy to get this on his radar and also for Mihai because he has worked on related parts of the keyboard before.
Flags: needinfo?(rlu)
Flags: needinfo?(mihai)
Flags: needinfo?(dflanagan)
Comment 12•10 years ago
|
||
(In reply to David Flanagan [:djf] from comment #11) > But perhaps this means that we should be falling back to the english > keyboard somewhere and we are not? (I say english as a fallback because > that one has lots and lots of accented characters defined.) This issue does sound familiar, I remember we had this fallback in place at some point. I'll have a look, Rudy feel free to jump in with more details.
Flags: needinfo?(mihai)
Comment 13•10 years ago
|
||
Is this bug related to FTU (First time user experience) app? We only change the enabled keyboard layout during FTU setup - see Bug 913784 for the details. (In settings, it will enable more keyboard layouts, but never disable the ones has been enabled.)
Flags: needinfo?(rlu)
Comment 15•6 years ago
|
||
Firefox OS is not being worked on
Status: REOPENED → RESOLVED
Closed: 10 years ago → 6 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•