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.
Note: I tried to make this fully compatible with the prior rmview behavior and older SW versions, but I have not tested it on older SW versions. A quick test or two from folks running a version < 3.6 would be appreciated.
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_VERSIONvalue 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.Note: I tried to make this fully compatible with the prior rmview behavior and older SW versions, but I have not tested it on older SW versions. A quick test or two from folks running a version < 3.6 would be appreciated.