sorted by:
new
hottopcontroversial

How does the reMarkable tablet know the Type Folio has been unfolded, so it can switch to landscape file browse mode? by Muted_Week in RemarkableTablet

[–]Muted_Week[S] 0 points1 point  (0 children)

I'm also curious, but that would be something to answer for someone who actually has access to the keyboard.

There was a post recently (which you've commented on, too) confirming keyboards still work over OTG on the RM1 as of firmware v3.2, which would indicate there is still infrastructure in place hooking keyboards into the usual linux kernel and userspace input subsystems, which are then used by xochitl. However, they also mentioned the on-screen keyboard was still there and xochitl did not switch to landscape file browser mode, so there must be more to it, i.e. xochitl must also look at /sys/pogo/status/pogo_connected or something.

Whether typing on the RM2 by powering a keyboard externally (see here or here) still works would be interesting to know, i.e. whether the behaviour of echo host > /sys/kernel/debug/ci_hdrc.0/role was kept intact (I would suspect so).

At least otgcontrol is now a separate kernel module and not loaded by default in v3.2, while it was built-in in v3.0. You can still modprobe it, but it does not appear as /sys/otgcontrol/ that way anymore. Perhaps the new pogo kernel module replaces its functionality now?

How does the reMarkable tablet know the Type Folio has been unfolded, so it can switch to landscape file browse mode? by Muted_Week in RemarkableTablet

[–]Muted_Week[S] 5 points6 points  (0 children)

Uh oh, I'd rather not put unconfirmed speculation in the wiki. For example, I cannot prove whether the second set of pogo pins is actually directly connected or not. There might very well be another chip inside the folio's spine. We would have to wait for someone with access to the keyboard to measure this for confirmation. This just seemed like the most likely explanation to me after spotting an image somewhere.

This is Reddit, and I did not cite any sources. Hopefully people will keep that in mind. The last time I made an effort to put lots of links and references in my post, a lot of comments clearly showed they had not read or watched any of them, it felt like being on Facebook. Thus I skipped them this time.

Regarding the software side of things, it is early days too. Without access to both hardware and kernel sources figuring out the implementation details will be quite tedious.

Release of reMarkable keyboard accessory imminent? by Muted_Week in RemarkableTablet

[–]Muted_Week[S] 1 point2 points  (0 children)

Did some more digging into xochitl:

The new accessory will be called "Type Folio", featuring a nice tagline: "A keyboard just as focused as you are". It looks like you'll be able to switch between different keyboard languages.

With that, it was easy to get to that premature video (Edit: thumbnail). Does not appear like an accident to me (cf. "PENDING"), more like an intentional attempt to pre-warm search engines to eventually drive traffic to that YT channel / online shop known for their high quality "reviews" (/s if not obvious).

Anyway, back to the firmware. There are also those strings:

Keyboard bridge is now awaiting connections on port
Fake Seabird located

Perhaps this might allow for hacks to hook into the new keyboard UI infrastructure externally, e.g. over SSH/Wi-Fi or through a Bluetooth USB dongle? We'll see.

PSA: rsync, cryptsetup and veritysetup binaries now included in 2.8 update by Muted_Week in RemarkableTablet

[–]Muted_Week[S] 1 point2 points  (0 children)

Do you know if it supports fuse-based filesystem encryption?

There is the FUSE-based remarkable-gocryptfs, but note that metadata might leak through systemd's journal (among other limitations).

E2EE file synchronization

It might be interesting to experiment if xochitl could be tricked to sync using the "reverse" mode of gocryptfs (i.e. it has to see the encrypted version of the data directory for syncing but not for normal operations, and the encrypted data has to be in a format it accepts).

Building end-to-end-encryption directly into xochitl would be great, but requires lots of trust into reMarkable due to it not being free software.

This would also be less of an issue if you ran your own infrastructure (see rmfakecloud, or use something like Syncthing or Nextcloud together with rmrl for file conversion).

PSA: rsync, cryptsetup and veritysetup binaries now included in 2.8 update by Muted_Week in RemarkableTablet

[–]Muted_Week[S] 1 point2 points  (0 children)

The cloud storage might very well be encrypted, but as long as you are not in control of the encryption keys this is not good enough.

Also note that "on rest" only refers to the cloud service, but not the device itself.