Document rM Paper Pro #74
Labels
documentation
Improvements or additions to documentation
enhancement
New feature or request
help wanted
Extra attention is needed
Comments
Eeems
added
documentation
Relevant pastebins |
|
Enum values for pen colors on the new tablet. I.e., this part of rmscene defines the values 0 - 8 as black, gray, white, etc. https://github.com/ricklupton/rmscene/blob/ca34c8a2b3337f5968ba6b60d39fc57c2a994fc1/src/rmscene/scene_items.py#L59 |
|
|
python3 --version Python 3.10.13 |
|
Some info generated by evtest: |
|
Hall Effect Sensor Data: |
|
Accelerometer info: |
|
Seems to be using https://www.kernel.org/doc/html/next/iio/iio_devbuf.html |
|
USB info: |
File system
Systemd services
Scripts are in Xochitl
|
Direct Rendering Manager
|
Security |
Cross-compiling for the device
For mason & ninjaFor cmake |
|
You can also run a aarch64 debian docker image and static compile things for the device natively to avoid the complexity of cross compilation. |
KMSCube graphic POC
Debugging information
|
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
|
|
|
Using a Y splitter adapter(to power it) with a USB keyboard and the below command lets you use it in xochitl
Note: seems like it auto changes to “device” mode if you plug the rM to power afterwards, so you only need to do the initial command to swap the roles Video of it working My.Movie.17-720p30.mov |
I also made my keyboard work but not with that path. Interesting that the I used |
|
@bedw8 Wonder if it switches to Device or Gadget in your path after you reconnect to power |
Avoid overlay fsany modification on this can be avoided by running then replacing On the next boot Note: this doesn't disable the |
unexpectedly (for me) connecting the device to power reverts the role in the path I used to apparently doesn't matter which path to use. both work and both get reverted to their original states after plugging the rMPP |
These are the indexed colours used by drawj2d. https://sourceforge.net/p/drawj2d/code/HEAD/tree/trunk/src/net/sf/jtikz/ReMarkablePage.java#l197 |
|
The FCC Equipment Authorization Database lets you look up and download some of the paperwork that reMarkable had to file with the FCC in order to be able to legally sell devices in the US. This includes things like which radio frequencies the devices use, and the lab test reports which certify that their wifi and bluetooth radios are using more power than they're legally allowed to. ⇒ Grantee Code: There are currently 30 different device authorizations on the list, with ten of them referring to Note that the FCC allows manufacturers to request "non-public" status for some documents. reMarkable has done this for documents containing information they feel would be useful to their competitors. |
|
Can somebody run evtest on /dev/input/event3? I only see the output from event1 and event2 above. |
@Evidlo I don't have evtest in the rMPP. you have to install it? But, printing the the events output with |
I believe he's interested to know what capabilities are reported, as well as the min/max values, which evtest would print out. |
First a quick touch with one finger, then a touch with two fingers, then a short swipe downwards. |
|
@Tiebe Thanks. Can you repeat that experiment for touch X direction and pen X/Y directions? I'm just trying to figure out the new coordinate system when the tablet is held in portrait orientation. For example, here is the coordinate mapping for the rM1 and rM2: |
|
Touch x left to right: Marker X left to right: Marker Y up to down: |
|
@Tiebe Thanks. This is what I think coordinates look like: Anyone know the device model in |
"reMarkable Ferrari" /sys has a trailing newline, while /proc doesn't |
Merged
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
|
|
|
full partition table, courtesy of UID 0 in the discord: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Start tracking information here about the device that may be useful to document, and PRs can be created to start integrating it into the correct place.
The text was updated successfully, but these errors were encountered: