Eeems
Joined 6 years ago
Karma
117
Submissions
52
Member since
Nov 17
[ my public key: https://keybase.io/eeems; my proof: https://keybase.io/eeems/sigs/1LCMfMThdo3_VJN3ycHxRYpAniCSy4Nd-4DQ2uZh_I8 ]
View on Hacker NewsRecent submissions
Comment · 6 months ago
This is not publicly available information in Canada. One very real concern here is that domestic abusers will now be able to find their victims: https://www.cbc.ca/news/canada/edmonton/edmonton-city-counci...
Comment · 1 year ago
A factory reset would result in it being regenerated
Comment · 2 years ago
They release software updates for both devices at the same time. There was no hacked version with all the same feature upgrades, it was, and always has been the official software update. They to this day still release all the same features to both devices.
Comment · 2 years ago
3.x support will come to toltec, I've been blocked by stuff outside of my control a couple of times. Including things happening in my life that I won't get into.
You can see the current progress here: https://github.com/toltec-dev/toltec/issues/820
As for the comment on the kernel change, that was actually an ask by someone in the community: https://github.com/reMarkable/linux/issues/8
Comment · 2 years ago
Thanks for mentioning oxide :) kinda cool to see people find my stuff exciting.
As for the statement that they don't respond to requests for source that they are obligated to release. They have everything that they are obligated to release on GitHub, and they have always released updated toolchains (that include a bunch of source) when. requested of them. They have been kinda late with the latest request, so yes they aren't timely right now. I've been poking what contacts I have, but I think a bunch of people had some extended vacations around the holidays or something.
Comment · 2 years ago
I usually have a macro called __RIGHT_HERE__ that prints a large arrow, the file name, and the line number.
Comment · 3 years ago
Could you provide a source on the software updates being more frequent, as well as clarify what you mean by rM being bad at updates? rM has been pushing out updates fairly regularly this year, especially if you include their beta channel.
Comment · 3 years ago
Not exactly true. there is an experimental display driver that does not require xochitl[0]. There hasn't been enough need for replacing the current rm2fb solution yet to drive completing it yet.
Comment · 3 years ago
Half as many cores, half the ram, and way less battery life due to higher power draw during suspend for some reason. It doesn't support the keyboard folio either. Depending on your criteria, one, or the other, is the better device.
Comment · 3 years ago
Usually the reason is that people want to continue using the built-in interface with just some additions, instead of replacing and maintaining a separate installation.
It would be nice if someone were to start working on an aftermarket linux distribution/ecossytem that targets eink devices. It's a lot of work to do, though, so I'm not surprised that nobody has picked up that torch yet.
Some notes on the reMarkable, it is running a custom linux distribution that is based on Openembedded Core[0]. The company publishes their modifications to the linux kernel[1], so one person has created their own linux distribution for the original reMarkable tablet [2]. The reMarkable 2 currently has no native framebuffer driver for the screen, due to it being software controlled by the UI application, which requires a workaround for custom applications[3].
0. https://www.yoctoproject.org/software-item/openembedded-core... 1. https://github.com/reMarkable/linux 2. http://www.davisr.me/projects/parabola-rm/ 3. https://github.com/ddvk/remarkable2-framebuffer
Comment · 3 years ago
https://remarkable.guide/ has a bunch of current information on the state of hacking your device. You have root access out of the box, which means how invasive it is depends on how you go about it. The community is trying their best to stick to a set of standards that keeps things from being too brittle, and "just works".
Comment · 3 years ago
> I didn't know there's different kinds of bricking.
There are two types of bricking[0]. A hard brick, where the device no longer functions, and may not be recoverable, and a soft brick, where the device is still working, but fails to boot to a usable state.
> It does NOT sound like having root access.
Could you clarify what you mean by this not sounding like you have root access? You have the ability to sign in to the device as the root user out of the box, which is exactly what root access is.
> This big warning is on the front page: > > > Warning: Toltec does not support OS builds newer than 2.15.1.1189. You will soft-brick your device if you install before support is released. See remarkable2-recovery for information on how to recover your device if you have done this.
Yes, I know about the warning, I wrote it. When it was less strongly worded, way too many people were ignoring the warning, trying to install toltec on an OS version that didn't have the offsets required for rm2fb yet, and did not write down their SSH password or set up an SSH key.
Comment · 3 years ago
Better in what way?
Comment · 3 years ago
Some of their stuff is open source[0], others, like the UI, are not.
Comment · 3 years ago
You can run your own reverse engineered implementation of their cloud: https://ddvk.github.io/rmfakecloud/