3

This question is broken into two parts:

  • Are there guides on which touchscreens 'work out of the box' with Raspberry Pi3 + Android Things? Its easy enough to stick HDMI screen on get output, but touchscreen is not so clear. I'm reading conflicting things about user-drivers and peripheral IO. But one things is clear, we can roll our own kernel-level HAL driver.

  • Second this likely depends on the answer above, is it correct to say that we can use the standard android UI classes for capturing motion and input?

Bernard
  • 56
  • 1
  • 4
  • from the docs "But one things is clear, we can roll our own kernel-level HAL driver." is wrong. The docs say: `Note: You cannot customize the behavior of device drivers in the Linux kernel or Hardware Abstraction Layer (HAL) to add new functionality to a device.` – Blundell Jan 18 '17 at 09:33
  • I didn't have any problems with a `Waveshare HDMI` display with an additional USB/power-input for touchscreen. – Onik Jan 26 '17 at 01:04
  • Sorry I meant to say we cannot use roll our own HAL driver. Really bad typo! – Bernard Feb 12 '17 at 19:14

1 Answers1

1

  • We successfully tested the official Raspberry Pi touchscreen with the simpleui sample.

  • Yes standard android UI class could be used to capture motion and input, you can also combine those with external peripheral (like push buttons, capacitive sensors, joysticks) with input user-drivers.

proppy
  • 10,495
  • 5
  • 37
  • 66
  • Thanks for that feedback, good to know that touchscreen works. Is that because it uses the DSI interface and Android Things library works with that 'out of the box'? I have another touchscreen by Kuman, but does not use DSI. It's not clear to me if there needs to be a driver that to work. The simplui sample has a button listener for the various checkboxes, so the assumption is there is already events being picked up somewhere by the OS. – Bernard Feb 12 '17 at 19:17