Closed
Bug 1026511
Opened 10 years ago
Closed 10 years ago
Touch screen input device has changed on Flame from event6 to event0
Categories
(Testing Graveyard :: Eideticker, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: davehunt, Assigned: davehunt)
References
Details
Attachments
(1 file)
760 bytes,
patch
|
wlach
:
review+
|
Details | Diff | Splinter Review |
After updating my Flame to the latest base build, I found that Eideticker was no longer interacting with the device. It turns out that the touchscreen input is now event0 and no longer event6. Here's the output from adb shell getevent: add device 1: /dev/input/event8 name: "msm8x10-skuaa-snd-card Headset Jack" add device 2: /dev/input/event7 name: "msm8x10-skuaa-snd-card Button Jack" add device 3: /dev/input/event5 name: "qpnp_pon" add device 4: /dev/input/event4 name: "compass" add device 5: /dev/input/event3 name: "bma2x2" add device 6: /dev/input/event2 name: "stk3x1x-ps" add device 7: /dev/input/event1 name: "stk3x1x-als" add device 8: /dev/input/event6 name: "gpio-keys" add device 9: /dev/input/event0 name: "Goodix-TS"
Assignee | ||
Comment 1•10 years ago
|
||
Attachment #8441372 -
Flags: review?(wlachance)
Comment 2•10 years ago
|
||
Comment on attachment 8441372 [details] [diff] [review] Update touch screen input device to event0 on Flame devices. v1.0 Review of attachment 8441372 [details] [diff] [review]: ----------------------------------------------------------------- lgtm
Attachment #8441372 -
Flags: review?(wlachance) → review+
Assignee | ||
Comment 3•10 years ago
|
||
Landed in: https://github.com/mozilla/eideticker/commit/6d4ea85912399cf3ccb2edaacf5c54f47a2a4438
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•7 years ago
|
Product: Testing → Testing Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•