-
-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
3.0 out of beta #496
Comments
it may take a while |
Hi, I didn't test this new version. What is better than the old version with DDVK hacks? What is missing compared to the hacked version? I'm afraid to miss ddvk hacks! |
@zelomel I'm writing a video on just that right now, but I did an initial impressions video when the beta came out if you're curious. https://youtu.be/xPEqzmU5-xg |
@brandonkboswell , thanks for your video above. Hadn't discovered your channel and just subscribed! Question: what happens when you 1) save your document as PDF and 2) print your document when you've extended the page with the infinite feature? Thanks! P.S. Fellow lefty here who HATES that close button in the upper left corner! Written to rM several times to no avail. |
It renders at 1:1. So it will have the width of a typical sheet, but then has variable height (with a minimum of your typical sheet size). From there you can decide in your print driver how to deal with it. Maybe one day they will let us lefties have our menus open ;) |
Same! I wish there was a way on the ddvk left handed layout to move the the bookmark feature away from the top left corner. I keep hitting it every time by accident. |
I end up needing to toggle off the bookmark feature for this reason. Would love it if the bookmark icon could move to the middle of the upper edge. |
@Tridens92 I ended up doing the exact same ^^ |
Yeah, maybe that's something we can suggest to @ddvk to change in future releases. |
|
Sorry for the excessive email requests and really appreciate your efforts, will await. |
sorry for the delay, just holidays and stuff. i'll try to find time this week. |
great, thanks! |
Just switch back and disable automatic updates. |
A huge thanks for your work! The DDVK hack makes a huge difference. It actually helped me to finally start using my reMarkable 1 in all areas of my life and to properly enjoy it. |
So I did play with the new version (which I kind of hate), the Adjust View missing being a major show stopper. I find the zoom/pan, infinite canvas thing laggy. |
I agree with you. |
@ddvk have you looked into the 3.x changes yet to know where contributions might help? |
Thanks for the warning, I did not know this essential feature went missing. The reMarkable website suggests otherwise. I'll put off updating to 3.0 until there is a hack that fixes this. I'd also very much like to be able to turn off enlarging ('infinite') pages. This silly feature breaks the notebook concept and I wouldn't want to accidentally trigger it. Having said that, fast tool switching and bookmarks alone would suffice to make me reinstall the hacks on 3.x, once available. Thanks, @ddvk! |
It is explicitly stated on reMarkable website:
|
I'm still on version 2, and Adjust View is available only for PDFs there as well. Am I missing the point? |
I'll check whether 3.10 is any better. right now you have to zoom a pdf with pinch in order to adjust the view, and it being laggy is cumbersome. |
Not much better in 3.1.1.11415. It's bit less laggy, but essentially the same function as 3.0. |
Guess I will hold back before making that update. Personally I would only care for the hacks if v3 is as snappy as v2, but I get why people don't want to downgrade to v2. |
@ddvk thank you so very much for putting your time and effort in, especially if you yourself don't even like the new update! I just unthinkingly started to update, and while waiting went to download this hack only to realize JUST in time that it wasn't ready for 3.0 and managed to stop the update! Would it still be possible to 'downgrade' these days if I wanted to check out the 3.0 update, but then go back to 2.15 with ddvk-hack ? Because I'm quite certain I prefer the old version + hack to the new version, but I am curious to test it. I believe long ago it was possible to run your own fake 'update server' in order to downgrade, but I don't remember the details of what I did. |
you can downgrade, but any documents you open on 3.x will be converted and not be usable when you revert to 2.x . you can use the switch.sh script in the update repo to go back to the previous version |
Holy crap, really? Any you open? Will they be accessible again once you do
go back to v3 (when ddvk hacks are available)?
I don't want to lose docs, but I am fed up with v3 turning all my pages
into infinity scroll without asking first. It's way too easy to initiate
that, and then you can't get the original page to ever realign correctly.
From the thumbnail view, pages with additional space, even if unused, show
up scrolled to the top. It's not an option to prevent the added space OR to
reset the original page size once it's been created, even if blank.
…On Fri, Jan 20, 2023, 5:18 AM Dobrin von Känel ***@***.***> wrote:
you can downgrade, but any documents you open on 3.x will be converted and
not be usable when you revert to 2.x .
—
Reply to this email directly, view it on GitHub
<#496 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AJ3N6BMJ4B7P7AJRLMB27R3WTJYADANCNFSM6AAAAAAS6WVR6E>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Actually, that doesn't surprise me. That is pretty typical when a file format changes. When you are running 3.x, the device expects the file to follow the new file format. If it is an older file format, it will convert it (on the fly) to the latest version and then resave it so it doesn't need to convert it again. You typically should never be "rolling" back to an older version (in the companies eyes that is.) Again, this is all pretty typical when going from one major version of software to another. I am sure that if you open a 2.x file with V3 of the software, and then "roll-back" the device to V2, when you roll the device forward to V3 again the V3 converted file will be fine. Now, that being said, I did not test it (I don't want to risk mucking any of my files, sorry!) I would be VERY nervous about going BACK to a older MAJOR version though, as it won't know how to handle a file with a newer version number (again, how could it know about the future.) If you try opening a V3 file with V2 of the software, it MAY not do anything worse then tell you it can't open the file, or wors, it could TRY to open the file, mis-interpret it because it is an newer file version then it knows how to work with, and then corrupt the file. Hopefully they wrote the firmware to do the former, not the latter. I think for your sanity, I would not try and go back and forth between MAJOR software versions of the firmware on the device (V2<->V3). I am pretty sure if you get a corrupted file from doing that, rM support would be well within their rights to tell you that what you did is NOT supported. Just my .02 of course. |
Guess this renders this project officially dead. I already consider to sell my device and get something else at this point. |
That's an odd take. I'm on 2.15, and I'm happily using rmfakecloud. This is the first I've heard about 2.15 not working with the official cloud anymore. @forpascal my guess is that you encountered this, and didn't actually have to update: https://remarkable.guide/faqs.html#my-device-is-connected-to-wifi-but-can-t-sync-or-check-for-updates-how-can-i-fix-this |
I'm still able to connect to the rM cloud in v. 2.15. All functions still working. |
Would sponsoring the project help with updates to 3.6? |
@brb Not sure about that lol |
I just ordered A rm2 yesterday and I'm waiting for its arrival, but I'm seriously intrigued by the hacking space around this device and have wondered if the switch.sh script you guys are mentioning to downgrade will work on the latest version 3.6? if theoretically my rm2 would arrive at said version? |
I cannot confirm for 3.6, but I can say it worked for me to revert from 3.5 back to 2.15. I had attempted it a few times and assumed it was not working, but tried again last week and managed to boot up in 2.15. This is great for now, but I still hope to have the hacks updated at some point in case we are forced to update. |
well I truly hope I can manage that, but just for confirmation this process should be relatively safe right? as long as I dont run software breaking commands in the ssh? I have a lot of experience in hacking iphones and xboxs and ps4 and many different devices so I just want to know that im not going into some risky territory here, this device is really not cheap and im not in the mental state for bricking it... |
Switch will always work to switch between whatever two versions are installed. Sometimes they come from the factory with only one version installed, so I don't recommend using it without knowing for sure that the fallback partition is good. |
I was already planning to probably go to the latest ddvk can support https://github.com/ddvk/remarkable-update if I would follow these instructions to a tea I probably wouldnt face any major issues right? |
I would recommend using codexctl to simplify the process instead. If you need further help, ask on the community discord. Any documents opened in 3.x cannot be opened in 2.15, as the format used to store lines was upgraded. |
A month ago I decided to update to newest ReMarkable 2 firmware. Today I'm currently on the latest version 3.6.1.1894. |
I understand that you don't have time for an update and that version 3 doesn't really appeal to you. The only plus point of version 3 is the TypeFolio, but it is a very good point. I confess to being a switcher, I use rM2 as a planning device during the week and nothing beats your hacks! I don't want to be without them. Then on Friday I switch to the 3 version and write my book with rM2. Of course, it's only a matter of time before I accidentally convert a version 2 notebook. I'm already thinking about buying a 2nd reMarkable because of this, so just wondering, is there anything we can do to motivate you to keep maintaining these hacks? Could a little CrowdFunding help? I would contribute $50 right away. Who else is worth contributing to? |
Hi Guys, let me start by saying that I am a very happy user of reMarkable 1 device with the ddvk's hacks applied. Lately I have been thinking how much effort and what is needed to prepare such hacks :) I will share with you what I currently know:
A little bit of a sneak peek attached :P @ddvk, I very appreciate all the work you have put into this project - it is both very useful and inspiring :) I am looking for a soulmate who would like to work with me on the topic for science purposes ;) |
@mb1986 you are on the right track, but I promised the rm guys that I won't make the tools that I use public. @dreadful-brain thanks for support, it's not about the money. i've fallen behind the updates so much that I dread starting again, as I know it will take me a couple of days to reintegrate everything. Sorry for pulling a George R.R. Martin. |
I am in. Not very skilled but willing to follow, give suggestions and why not code a bit. ;) |
I also am sitting with 2.15 because I can't imagine being without the hacks (I'm also a left-hander and dread that close button right where my hand will be!). However, I'm concerned that there is a reason we might need to upgrade: data loss... https://support.remarkable.com/s/article/Tech-bulletins I've experienced this troubling data loss. The loss is "invisible". In other words, I don't notice there's a problem until I open a notebook that had the issue. By that point the corruption (usually many lost pages) has replicated to the cloud. I then have to call rM support and wait (usually) weeks to get an older version of my notebook restored from backup. @ddvk, I hear you re: dreading integrating all the changes from 2.15 to current. Is there any way you could decouple the remarkable-stylus hack from the your hacks, so those of us who are still with rM1 could use a stylus with an eraser button on it? While I would be really sad to leave your hacks behind, working without your eraser hack would be a huge productivity loss for me (I'm writing on my tablet for around 25 hours a week!). Either way, I'm very thankful for how you've made my life easier for many years with your hacks! |
As far as I understand it the other package created by @ddvk is responsible for translating Lamy Stylus button presses into key press events: https://github.com/ddvk/remarkable-stylus/blob/66028ede0dafff10a6df6d4afe41f25c0c782e9a/qevdevtablethandler.cpp#L77-L97 The next part is to use those key press events: // authored by @ddvk
// ...
} else if (event.key === Qt.Key_U && !event.isAutoRepeat && (event.modifiers & Qt.ControlModifier)) {
if (Values.holdToErase)
drawingArea.currentBrush = drawingArea.lastEraserTool
else
switchTool()
}
// ... Adding the pen eraser button feature is the first thing which I would like to revive. |
The invite appears invalid. |
Interesting. I tried it 4 times, and all four it said the invite was invalid. I JUST tried it again, and this time it let me in. |
I'm also getting invalid invite, tried a few times 2 hours ago and now again now. (EDIT: Worked after a few more tries) |
Same here - invalid invite.cheersDirkAm 20.09.2023 um 15:14 schrieb Roman Gaufman ***@***.***>:
I'm also getting invalid invite, tried a few times 2 hours ago and now again now.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>
|
Hi All, we have been able to bring a couple of ddvk's features back to 3.6.1.1894: https://github.com/mb1986/rm-hacks |
https://github.com/timower/rM2-stuff did anybody check out this already? does it work? |
Please use that repository to talk about it instead of asking something off topic here. |
Any updates on this? I just updated my rM2 after not using it for a while, assuming I could just install the hacks again. That was clearly a mistake. |
Use rm-hacks which were linked earlier in this thread. |
3.0 is now slowly rolling out. The version number is 3.0.4.1305.
The text was updated successfully, but these errors were encountered: