Closed Bug 1077336 Opened 10 years ago Closed 7 years ago

Keyboard triggering to appear, but nothing can be typed

Categories

(Firefox OS Graveyard :: Gaia::Keyboard, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: clement.lefevre, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:32.0) Gecko/20100101 Firefox/32.0 Build ID: 20140923175406 Steps to reproduce: Just opened Messages application to type a message. Actual results: When I touched the input field, keyboard triggered so than I can type on it, but then when I tried to type on, nothing happened : keys were not pushed (no one) and field wasn't filled. Expected results: Be able to type on the keyboard and fill the input.
Just as an adds-up I forgot : after this, I check other applications like the browser, problem was the same, meaning it came from keyboard, not app. Had to restart the phone to end the problem (have it going to sleep then wake up changed nothing).
Mark QA wanted to check each branch as I cannot repro with current master.
Keywords: qawanted
Can we get the Build ID and gaia commit?
Flags: needinfo?(clement.lefevre)
(In reply to Jan Jongboom [:janjongboom] (Telenor) from comment #4) > Can we get the Build ID and gaia commit? That's the stock ROM of a ZTE Open C. Here are the informations I got on it : Software : FFOS_FR_ZTE_OPENCV1.0.0B01 System version : 1.3.0.0 Version ID : 20140625152014 Git commit : 2014-06-27 08:12:34 I have no idea on how to reproduce it, it happened only one time and I had to reboot, never got this bug another time.
Flags: needinfo?(clement.lefevre)
I've done some checks on the Flame device which is our test device. I noticed this seems like a really old build you are using? June 27th. Does it still happen on a recent build if you can get it? I checked with 4 different keyboards English,Number, Portugues, Espanol. I checked Browser and Messages app. Checked phone going to sleep then waking up. NO REPRO. Going to remove QAWanted for now. If this bug occurs on a current build then we can look into this again. This bug does NOT repro on Flame kk build: Flame 2.2 KK, Flame 2.1 KK, Flame 2.0 KK Actual Result: Keyboard functions as expected. Repro Rate: 0/12 Environmental Variables: Device: Flame Master KK BuildID: 20141006064312 Gaia: 470826d13ae130a5c3d572d1029e595105485fb0 Gecko: e0d9ad4be606 Version: 35.0a1 (Master) Firmware Version: L1TC10011800 User Agent: Mozilla/5.0 (Mobile; rv:35.0) Gecko/35.0 Firefox/35.0 ----------------------------------------------------------------- Environmental Variables: Device: Flame 2.1 KK BuildID: 20141006062615 Gaia: 778ebac47554e1c4b7e9a952d73e850f58123914 Gecko: bc87917b3b95 Version: 34.0a2 Firmware Version: L1TC10011800 User Agent: Mozilla/5.0 (Mobile; rv:34.0) Gecko/34.0 Firefox/34.0 ----------------------------------------------------------------- Environmental Variables: Device: Flame 2.0 KK BuildID: 20141006044157 Gaia: 26670a3193b57ead978ef2faefc2a679ea57f8d4 Gecko: c06b369ccda7 Version: 32.0 (2.0) Firmware Version: L1TC10011800 User Agent: Mozilla/5.0 (Mobile; rv:32.0) Gecko/32.0 Firefox/32.0
QA Whiteboard: [QAnalyst-Triage?]
Flags: needinfo?(jmitchell)
Keywords: qawanted
QA Whiteboard: [QAnalyst-Triage?] → [QAnalyst-Triage+]
Flags: needinfo?(jmitchell)
This phone is mainly used as a demonstration one for some events so I plan to keep it on 1.3 for the moment. It's supposed to still have some updates for bug fixes and so on (one landed a short time ago, didn't updated yet, I should do it), while FFOS 2.X isn't ready for commercial launch yet, and shouldn't be before 2015 from what I heard from devs.
This might be the same issue bug 1019360, which we decided "wontfix" and fix it on v1.4. If possible, please help provide a video if you can reproduce it again. Thanks.
I don't exactly know if it's the same issue, but I did not have the same bug another time since this bug report.
Since yesterday (2014-10-18) the same issue occurred to me, same device: >ZTE Open C / FFOS_EU_EBAY_OPENCV1.0.0B06; >OS-Version: 1.3.0.0 >Hardware-Version: P821A10B01; >Plattform-Version: 28.0 >Build-ID: 20140523093151 >Git-Commit: 2014-05-26 05:55:18 The Touchscreen (and opened apps) does well as long as no keyboard is envoked; if so, there is no further input possible. The first time it occurred, there was even more a whole blocking of the opened app (unable to close it, until I kicked the device to sleep). Will now try to restart the phone in order to (hopefully) regain full functionality...
Firefox OS is not being worked on
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.