Closed Bug 1039990 Opened 10 years ago Closed 10 years ago

Keyboard takes approximately 2 seconds to appear on low memory devices

Categories

(Firefox OS Graveyard :: Gaia::System::Input Mgmt, defect)

ARM
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(b2g-v2.0 affected, b2g-v2.1 ?)

RESOLVED DUPLICATE of bug 1036577
Tracking Status
b2g-v2.0 --- affected
b2g-v2.1 --- ?

People

(Reporter: jlorenzo, Unassigned)

Details

(Keywords: perf)

Build info Device: Flame 273MB Gaia aa4f795b81c6147d67c4f06009e166debcf8856e Gecko https://hg.mozilla.org/releases/mozilla-aurora/rev/0ec0b9ac39f0 BuildID 20140717000201 Version 32.0a2 ro.build.version.incremental=109 ro.build.date=Mon Jun 16 16:51:29 CST 2014 B1TC00011220 STR 1. Launch an app that was not running (like Messages or Browser) 2. Tap a text input field Actual result The response time of the keyboard varies from half a second to no response. It's often around 2 seconds (see video: http://mzl.la/WdDCpk ).
Nominating as a 2.0 blocker as the response time is above the perception of progress time (1 s) and to progress indicator is shown. Moreover, I often see no response with the URL bar of the browser. See this video: http://mzl.la/1mjMQp8
blocking-b2g: --- → 2.0?
Summary: Keyboards takes approximately 2 seconds to appear on low memory devices → Keyboard takes approximately 2 seconds to appear on low memory devices
OS: Mac OS X → Gonk (Firefox OS)
Hardware: x86 → ARM
For it is slow for keyboard to popup, it should be a dupe of bug 1036577. Could you please help check if comment 1, "keyboard not showing up", could be reproduced for 512MB configuration or on other devices? Mark qawanted to check comment 1.
Keywords: qawanted
Or since bug 1036577 has landed, could someone help check that comment 1 could not be reproduced with that patch?
I can confirm it. Alcatel One Touch Fire production (got from T-mobile Poland) B2G version: 2.1.0.0-prerelease master Platform version: 33.0a1 Build Identifier: 20140716160202 Git commit info: 2014-07-16 05:26:00 d29773d2
status-b2g-v2.1: --- → ?
This looks like a dupe. I'll re-open it if the issue persist in tomorrow's build.
Status: NEW → RESOLVED
blocking-b2g: 2.0? → ---
Closed: 10 years ago
Keywords: qawanted
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.