Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with hardware
Search options not deleted
user 337943
For questions about the hardware of Android devices. Note that asking for finding or recommending hardware (phones, tablets, accessories, etc.) is off-topic.
1
vote
0
answers
54
views
What algorithm does Android used to translate touchscreen events to scancodes?
At this point, my understanding is this:
With a physical keyboard, the keyboard hardware itself can send a scancode that can be translated to an actual keycode at the kernal level through a simple lookup … With a touchscreen, the hardware device is sending an X/Y position (along with some other data, but not a scancode), which then needs to usually be translated into a scancode by a previously exported virtual …
- 111