rm 3.0 compatibility issues? Screen view not functioning #146
Comments
|
You're not the only one, i have the same issue. |
|
Manually compiling resolved the issue for me. (Installed the rmview-git version on the AUR and manually installed the dependencies.) |
|
Was not working on my side. Still not working, so I launched it with debug and I noticed something interesting So I tried removing that |
|
Screen sharing is not working for me either after my reMarkable updated to version 3.0.4.1305. I get the following error when I try to connect using |
|
@marozols your issue was fixed in 7fbcc7c make sure you are running on the latest commit. I'll add a release to point to the latest version. As for compatibility with v3: I have not updated yet so I cannot test rmview on the new version. PRs are welcome if anybody finds tweaks that make it work well with it. |
|
Thanks, @bordaigorl! I managed to fix it in the meantime. The
and now everything works! |
|
I can't get it to work. The window says "Connecting to reMarkable" und on the tablet I see "Accept connection in the desktop app..." After closing the window: |
|
Log on the PC side for me is : I can see that activate screen shearing on the device still open port 5900 Sniffing packets on the PC side, I can see that the device is broadcasting UDP packages to port 5901, 51bytes data |
|
Is there any news for this issue? Does someone needs more information to identify the origin of the problem? On my side, I have the same logs and I can see the cursor on the "connecting screen":
Thank you for your help! |
|
@tillwf was screensharing working before updating? Have you tried with the official app? |
|
I didn't try |
|
@tillwf thanks, that confirms it's not a problem with closed ports. |
|
any news? Just tried running on v3.4 and having the same issue as described by @tillwf (same console output) |
|
+1 having the same issue as well |
|
+1 connection works and can see cursor in rmview with pen movements made on the tablet, but not image is received. |
|
Just reporting that I installed rmview from scratch on Fedora 38 with Python 3.11.4 and have Remarkable 1 with version 3.5.2.1807 and rmview is working fine. Works with both password and ssh keys. I start the "Present with Screen Share" on Remarkable first and then run [I'm having an issue where sometimes it stops connecting and it will timeout when trying to connect. After some time it works again. But I think this may be something with my test computer/network (which has some issues) because when this happens, I'm also unable to ssh and ping the remarkable independent of rmview] |
|
EDIT: FIXED ---------------------------/EDIT If I stop Screen Share on the remarkable I get these logs: So, I think it is connected. And it is successfully ssh'ing to the device, using the key and adding the key to the known_hosts. I think these are the interesting lines: |
|
@meelash thank you so much for your report! |
|
I do have the same issue, any solution so-far? |
|
To summarize: this issue has many reports of different nature (most of which were resolved some time ago); the current status is that version to overwrite on the tablet the version number with something sensible. |
|
Edit: The issue was actually solved by the version reset. The problem left was the UPD Port. I was hoping that the issue is resolved by changing |
|
I tried implementing the mentioned feature (enforcing authentication) here: https://github.com/rsoeldner/rmview/tree/rmv3-auth I get the following output: But it will not pass the authentication. Maybe @bordaigorl can confirm, using the |
|
@rsoeldner yes |
|
@bordaigorl Unfortunately, this does not work for me ... The mentioned change should be implemented in my fork. Any ideas how to debug thus further? |
I just did it today with my RM2 with firmware 3.6, and I can confirm it does work, no issues connecting. |
|
thank you for the version-overwriting workaround! confirm that it works for me. |
|
I've just got my remarkable with 3.6 firmware and have the connection problem. Part of it was fixed by the mentioned update of The config mentioned there seems to be /etc/remarkable.conf, indeed, I don't see any devicetoken value there... Edit: got, I had to register the device first :) now it works fine! |
|
Thanks @assaron for the report, it would definitely be better for rmview to detect whether you still need to register and give a more informative error... |
Thanks a lot! I also confirm, that this worked for me (Firmware Version: 3.6.1.1894). |
This worked for me as well! |
|
Hello everyone, I had the same problem and changed the IP from the default (10.11.99.1) to the one written in the Help/Copyrights and licenses (e.g. 192.168.2.120) when I was logging into rmview. Hope that it helps. Disclaimer: You need to have your WiFi open and your PC has to be logged to the same WiFi. |
|
Yeah, this worked for me as well. I just sshed into the remarkable machine and then ran the echo command. This resolved the libcrypto issue. |
|
reMarkable has started to use reproducable builds for their OS releases, so /etc/version will no longer be unique per-version. At least that's what was indicated in discord by one of their staff. So going forward, a new mechanism will be required for determining the OS version. |
|
Hi, I am just starting to try using rmview, and I was getting the libcrypto error, which went away when I changed the /etc/version as told above. But, my rmview screen is now stuck as described in this comment with the console log stuck at "Authenticating, please wait". Did I miss something? I am using remarkable 2 with version 3.7. I have also opened my ports 5900 and 5901 as mentioned on wiki. |
|
I fixed this issue for myself by getting the the software version from Replacement for # Add `from datetime import datetime` to top of file
def _getSwVersion(self):
_, out, _ = self.client.exec_command("cat /etc/version")
version_ts = int(out.read().decode("utf-8"))
try:
_, out, _ = self.client.exec_command('xochitl --version 2>/dev/null | tail -n 1 | cut -d" " -f2')
xochitl_ts = int(datetime.fromisoformat(out.read().decode("utf-8").strip()).strftime("%Y%m%d%H%M%S"))
version_ts = max(version_ts, xochitl_ts)
except:
pass
return version_ts |
|
It might be better to standardize on the OS version number you can find with |
This does seem like a more reliable source. I updated my fix to use this instead. I'm now representing versions with tuples instead of timestamp integers, and reversing |
It's not documented anywhere that I'm aware of, but from the list of version numbers I have, that does appear to be the version scheme. Side note, for anybody interested in the source on the reproducible builds comment I made previously: https://discord.com/channels/385916768696139794/834359134870568982/1149409895486083123 |
The issue arises due to the reMarkable software version no longer being accurately reflected in `/etc/version`. This causes rmview to think it is connecting to an older version. I've fixed this by switching rmview's SW version logic over to the semantic versioning scheme used by recent releases. The SW version is taken from the `REMARKABLE_RELEASE_VERSION` value in `/usr/share/remarkable/update.conf`, as suggested by @Eeems. Support for older versions is to be maintained by mapping the older timestamp version numbers back to the corresponding semantic versions.
|
Created PR #158, containing my fix for this issue. Please give it a look. |
|
@kjyager thank you so much for contributing the PR! |
The issue arises due to the reMarkable software version no longer being accurately reflected in `/etc/version`. This causes rmview to think it is connecting to an older version. I've fixed this by switching rmview's SW version logic over to the semantic versioning scheme used by recent releases. The SW version is taken from the `REMARKABLE_RELEASE_VERSION` value in `/usr/share/remarkable/update.conf`, as suggested by @Eeems. Support for older versions is to be maintained by mapping the older timestamp version numbers back to the corresponding semantic versions.
|
Now merged! Thanks @kjyager :) |
|
Hey all, I am also having this issue on the latest Firmware version (3.10) (Can even see the red dot, but it is stuck at [Authenticating]. The file in /etc/version is up to date, too. How can I get this to work? |
I suspect this is an unrelated issue. I just updated my device to 3.10, and rmview is still working for me. It is probably worth making sure the rmview version is recent, and that you're not encountering another common issue. |
and others
Was wondering if I was the only one whom rmview stopped functioning once I updated my remarkable to 3.0 Hoping this can be resolved soon
The text was updated successfully, but these errors were encountered: