Closed Bug 760966 Opened 11 years ago Closed 11 years ago
Fu] Severe performance difference between using a hardware keyboard or a virtual d-pad
When navigating a web page with the hardware directional controller of my HTC Desire running Gingerbread, and the D-pad emulator of the Eyes-Free keyboard in ICS 4.04 on my Galaxy Nexus, I notice a severe performance lag in ICS. In Gingerbread, navigating native UI or web page content yields an instant response. Vibration, sound, and speech all react almost instantaneously. Comparable to the flicking gesture responsiveness of iOS. In ICS, in the native UI, response is as good as I would expect and is comparable to Gingerbread. In web content, however, response is very very slow. From flicking right to go to the next item, it takes about one to three seconds. The pattern is: 1. It takes one second from flicking to reading, sound, and vibration if the next node is text. 2. It takes two to three seconds if the next item is a link. After one second, one hears a high-pitch sound similar to a small piece of paper being torn apart. Another 1 to 2 seconds later, speech, vibration, and sound are heard and announce the link. None of these behaviours are observed in Gingerbread. I used my blog as an example.
Same poor performance can be observed on the Galaxy Tab with CM9 and the Eyes-Free keyboard.
Could you try a bluetooth keyboard and see if you get the same results? There are some acute issues with the virtual dpad that I am aware of. They are being tracked in bug 755573 and bug 755976.
Summary: [AccessFu] Severe performance difference between Gingerbread and ICS → [AccessFu] Severe performance difference between using a hardware keyboard or a virtual d-pad
(In reply to Eitan Isaacson [:eeejay] from comment #2) > Could you try a bluetooth keyboard and see if you get the same results? Using a hardware keyboard, performance is excellent on ICS as well. Changed summary to reflect this.
Fixed by fix for bug 755976.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Verified in Nightly/Android 2012-06-09.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.