If you don't mind a small black band at the bottom of the screen, the following set up seems to work pretty well (except for some reason drag-and-drop). Note the use of 2104 and 1560 (not 2200 and 1650).
/boot/config.txt:
Quote:
hdmi_cvt=2104 1560 30 1
max_framebuffer_width=2104
max_framebuffer_height=1560
hdmi_group=2
hdmi_mode=87
hdmi_force_hotplug=1
|
(It's probably obvious, but rebooting is necessary after the above are incorporated into /boot/config.txt)
To test the touch capability of the Max 2 with the RPi (tested w/ RPi 2 running Raspbian 9), relevant pieces from the 'Onyx Boox as monitor' thread include:
Quote:
mdp's Monitor Mod 2 (post 409)
the script 'onyx-monitor-move-pointer-hack-6.py' (post 432)
|
1. Install the Monitor Mod 2 apk on the Max 2 and save the script on the RPi.
2. Shave some yaks by doing some installation on the RPi
Quote:
sudo apt-get update
# pre-requisites for the script
sudo apt-get install -y android-tools-adb android-tools-fastboot
sudo pip install pyuserinput
# virtual keyboard if desired
sudo apt-get install florence at-spi2-core # or just matchbox-keyboard
|
3. On the Max 2, ensure Settings -> Developer Options -> USB debugging is enabled
4. Connect the RPi and the Max 2 with appropriate USB and HDMI cables.
5. Get adb running on the RPi with:
and verify the Max 2 is visible via the output.
6. Answer 'OK' or equivalent to the dialog box that should pop up on the Max 2's screen about allowing the USB debugging connection.
7. Start Monitor Mod 2 on the Max 2 -- I often see a dialog box on the screen about power consumption (to which I typically answer 'OK'), but most of the time I haven't noticed power issues.
8. The script on the RPi needs to be coaxed a bit if using it from outside of X with something like:
Quote:
|
DISPLAY=":0.0" python2 onyx-monitor-move-pointer-hack-6.py
|
9. It helps when testing the touch capability to have the RPi running X and showing it -- with that set, try clicking on things with the stylus (e.g. in Raspbian, there are typically some icons along the top edge of the screen). Another test might be to launch 'florence' or 'matchbox-keyboard' and try stylus-entering some text via either of those virtual keyboards.
Some observations:
-The instructions were partially from memory, so there are likely some errors...
-Double-clicking doesn't seem to work as well as when connected to a PC running some Linux distribution
-Haven't had luck with drag and drop yet -- at least via the title bars of windows. Work-around: with focus on the window one wants to move, type alt-space, select 'Move' from the resulting pop-up menu, and then drag the window with the stylus to the ultimate destination.
-It was helpful to have a physical keyboard attached while testing as well as SSH access to the RPi -- but if you've read this far, you probably knew those kinds of things already
