Closed Bug 776412 Opened 12 years ago Closed 3 years ago

Latest nightly takes a really long time to load keyboard

Categories

(Firefox for Android Graveyard :: Keyboards and IME, defect)

ARM
Android
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: jwir3, Unassigned)

Details

This seems happens on my galaxy s2 with the Darkside Evolution ROM (Darkside Kernel v3.0.8-perf) and the Swype keyboard installed. Note that it might be something to do with the ROM/keyboard interaction, too, since I've noticed slowness with the phone app as well (although that doesn't use the keyboard, but it does exhibit similar problems). 

I didn't originally notice this on my phone. It's only been in the last ~5 days that the nightlies have been exhibiting this behavior.

STR: 

1. Launch nightly (or utilize a nightly already launched, as it isn't specific to new instances).
2. Click on awesome bar.

Expected Results:
Awesome bar comes up, brings up keyboard immediately for typing.

Actual Results:
Awesome bar comes up, displays a list of historical sites visited, but the keyboard takes ~10 seconds to come up, so I can't search for what seems like a long time.
Anything happening in logcat during the invocation?
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.