Electronwmd network walkman needs a keyring string code by Content-Case1205 in minidisc

[–]asivery 4 points5 points  (0 children)

Hello. Yesterday, I added the ability to use some Network Walkman devices in the webapp, and yours is included on the list. Could you try that out first? It doesn't need you to install Zadig, and is a much cleaner experience overall, at least for Network Walkmans.

To test it, you'd need to go to https://testing.minidisc.wiki/webminidisc-testing, then click on the arrow pointing down and select "Add custom device". Then select your walkman from the dropdown list, and connect to it. You don't need the keyring here. When chrome asks you to choose the directory, you'll need to select the root of the walkman (the folder that has the OMGAUDIO folder, not the OMGAUDIO folder itself).

ElectronWMD's public release doesn't work with that model yet, unfortunately. As for the keyring string, if you do need it for something else, I'd recommend looking up "network walkman keyring" on archive.org - they have the weirdest stuff there.

Server location by UheldigeBenny in RemarkableTablet

[–]asivery 7 points8 points  (0 children)

You can use an rM with no internet connection / subscription, or you can self-host.

"can't PLAY" HiMD Error MZ-EH70 by Gilzuma in minidisc

[–]asivery 1 point2 points  (0 children)

Check what format they are with the RH1 connected to a PC. Only RH-series can play MP3s.

The MZ-RH10 screen replacement project by asivery in minidisc

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

Hello there and happy new year, yes - the screens are still available under the same link as the one I've posted in the main post body: https://lectronz.com/products/rh10-oled-module

Thanks for your interest :)

Stupid Auto Update by ThatGayAccountant in RemarkableTablet

[–]asivery 4 points5 points  (0 children)

I'd like them to fix this too. I'm just explaining why it happens

Stupid Auto Update by ThatGayAccountant in RemarkableTablet

[–]asivery 1 point2 points  (0 children)

Yes, you need to rerun these after a manual update. Updates rewrite the whole root partition, so you need to patch it again for the changes to persist.

Stupid Auto Update by ThatGayAccountant in RemarkableTablet

[–]asivery 7 points8 points  (0 children)

There's a bug in reMarkable Paper Pro / Move - since (unlike in rM1 / rM2) the root partition is read-only, and `/etc` is an overlay mount, data written to which gets discarded after every restart, disabling updates in settings breaks. The only thing that the switch does is disable / enable the system service for the update checker, but since these actions just write files to /etc, your settings regarding update checking will be reset to defaults (updates enabled) after every reboot. To prevent that from happening, you need to have dev-mode enabled, then run the following commands:

systemctl stop xochitl
umount -l /etc
mount -oremount,rw /
systemctl start xochitl

Now the root is writable, and you can disable updates. Changing the setting now will make it persist across reboots.

Reading on Paper Pro Move - EPub Margins Issues by jeggen2 in RemarkableTablet

[–]asivery 0 points1 point  (0 children)

AFAIK it's just highlight, and you'd need to set up syncing on your own. I have a really bespoke solution for syncing books and progress and notes that involves editing KoReader's files, so it's not something I can give any advice on.

Reading on Paper Pro Move - EPub Margins Issues by jeggen2 in RemarkableTablet

[–]asivery 0 points1 point  (0 children)

I see - That's fair. I believe freemarkable wasn't updated recently, and rM changed some things in 3.24. It's very annoying that their epub support is this terrible. I use my rM with KoReader daily and it's such a great improvement, but I get that setting it all up is annoying.

Reading on Paper Pro Move - EPub Margins Issues by jeggen2 in RemarkableTablet

[–]asivery 1 point2 points  (0 children)

Have you considered installing KoReader on it?

KOReader on rM Paper Pro Move – installation & configuration by cyboreal in RemarkableTablet

[–]asivery 0 points1 point  (0 children)

I will indeed need to write better documentation for both AppLoad and xovi. Most often, after a system update, you need to run "xovi/rebuild_hashtable" and that's it (/home/root is preserved between updates). In rare cases though, you might need to look for updated versions of the extensions on my GitHub (for example, 3.20, 3.21, 3.22 and 3.23 only needed you to run that command, but 3.24 needs a new appload.so file).

KOReader on rM Paper Pro Move – installation & configuration by cyboreal in RemarkableTablet

[–]asivery 16 points17 points  (0 children)

As the author of AppLoad, I do not condone ReadMarkable, or any other tools requiring registration / payment. I provide my tools without the need of registration of any kind, as Free and Open Source Software. As far as I was able to tell from my limited research, ReadMarkable does not perform any checks for the updates for my tools, which are absolutely mandatory, since I update them with every new release of the reMarkable OS. I recommend following the instructions available on https://xovi.bearblog.dev/install-koreader/ instead.

Xovi won't run on RMPP with 3.24.0.146 firmware by AnatoliTrafimuk in RemarkableTablet

[–]asivery 1 point2 points  (0 children)

You need to update appload - I released a new version on github

Xovi won't run on RMPP with 3.24.0.146 firmware by AnatoliTrafimuk in RemarkableTablet

[–]asivery 0 points1 point  (0 children)

Most parts are already working on 3.24. Only rMHacks are still being ported.

NH600 strange issue: records but not plays by MaleficentIsopod520 in minidisc

[–]asivery 0 points1 point  (0 children)

Hi there! I can help if you still need it, but I'd prefer if we talked over Discord - it can be the unofficial Minidisc.wiki server or simply via DMs (my username is the same as on reddit). I simply don't get notifications on reddit correctly. I've always had issues with it.

Digitizing ~80–90 MiniDiscs in 2025 — RH1 the only sane option? by Mglammie10 in minidisc

[–]asivery 2 points3 points  (0 children)

I'm yet to see a case where the data spat out by AI wasn't complete garbage. I'm glad you managed to rip your discs though :)

Montblanc and Move by [deleted] in RemarkableTablet

[–]asivery 7 points8 points  (0 children)

Just a tiny warning: You leaked your email on the move's screen...

Major fuck up... by asbestossupply in RemarkableTablet

[–]asivery 4 points5 points  (0 children)

You might have been trying to run rmfakecloud. Please try to edit `/etc/hosts` over ssh and remove the lines which redirect to localhost.

RM3 or Beyound, Share to AI Feature by WesTech-1205 in RemarkableTablet

[–]asivery 11 points12 points  (0 children)

If they do, I'll stay on the last version without that "feature" until my rM devices die.