Let me just say that the Remarkable also runs linux.
Not only that, but I've been blown away by the ongoing results from the team at Remarkable. I only have the Remarkable 1 but they continue to ship updates for it, and these updates are often really substantive with sometimes profound new features. Their cloud service is free, no aggravating subscription stuff and even though they have the remarkable 2 now, they continue to kill it with the updates to improve my experience with the remarkable 1. They, as of right now, have my undying loyalty and appear to be a truly customer focused company. I'd love to buy their entire team a couple beers.
Don't get me wrong, I love pine64 too, but they're way more oriented to us hacker types than ordinary people and I don't want to have to hack together a functioning device with everything I own, though I think they're doong good work none-the-less.
And they give root access to the device along with GPL compliance statements, allowing for a flourishing developer community that creates tons of useful programs that can run on the embedded device. See for example https://github.com/reHackable/awesome-reMarkable for a list.
There is also an opkg-based package manager and repo with many packages: https://toltec-dev.org/
Especially: Write down your root password and DO NOT factory reset the device if you want to go back to the original state.
If you follow these steps and you know a bit about linux you'll be fine.
Factory reset on the rM2 will mess with the community framebuffer service and reset your root password, effectively locking you out unless you go the fiddly way over the external port.
The rM1 is very resilient as you can directly access the internal storage without special tools.
Remarkable 2 requires a bit of parts and possibly soldering (but not required, just might make things easier if you don't have pogo pins with handles available).
Both are fully recoverable unless you do something really impressive.
Physically breaking the hardware through software, for example. I believe there's some fun possible in most embedded designs like the one used in RM1/RM2. Like manipulating power management circuitry, or maybe forcing overheat with disabled throttling, and the like.
If this e-ink device is usable as a secondary display for my laptop, I'm in.
I'd love to get work done in sunny locations, like gardens. But these LCD screens make me squint. e-ink would be THE solution to this, but the e-ink displays are too expensive, to well supported and not very big.
In the rM1 you just write to a framebuffer device in /dev/fb0 to write on the screen. It's so easy you could probably write an application that does that, compile it for ARM, load it via scp and run it. All in 15 minutes even if you know nothing about the Remarkable itself.
The rM2 is a lot trickier. A full reverse engineering of the drawing routines is still unfinished, as far as I know. So you either manipulate the memory of their closed source application or reuse big binary chunks of it. There are of course abstraction layers built over that by the community but as of today I believe it's much less refreshing than the rM1.
The rM1 used the chip electrophoretic display controller directly , while the rM2 has a software controller which is closed source. Hence much of the complications
Do note that Remarkable is not as rosy as it looks like. Due to the fact that most of the builtin software is proprietary, actually modifying it to run anything other than the stock features requires binary monkey patching the main executable. It's as fragile as it sounds.
If they were to add a simple plugin system, that would take them 0 effort with Qml, it would be significantly better.
Actually, it's better than you describe it, I think. Most components are FOSS. The default GUI and the framebuffer driver are proprietary closed source. However, the framebuffer driver has been extracted from the GUI service by github user ddvk and faciliates the development of independent interfaces (look for "launchers") that can launch further independent programs, e.g. harmony https://rmkit.dev/apps/harmony
There is also an opkg-based package manager and repo with many packages: https://toltec-dev.org/
The binary patching that you talk about is only one mod that can be installed to improve the functionality of the original GUI. It is true that it would be awesome if that had plugin support, as you stated, though.
> However, the framebuffer driver has been extracted from the GUI service
Extracted? Last time I look at it, they were inserting a patch in the main (and only) binary of the proprietary GUI via LD_PRELOAD, and then all other programs which wanted to draw _anything_ to the screen would basically _directly alter the memory_ of the proprietary GUI binary in order to modify its internal framebuffer. You have to do that whether you want to integrate with the main GUI or not -- since you need this hack to draw anything to the screen.
Literally every other Remarkable update so far has killed all of this.
> Most components are FOSS.
The usual thing: most 3rd party components which they are forced to open anyway are FOSS. Anything that may even be remotely interesting is NOT FOSS. I do not understand why people try to claim this as a positive, cause it isn't.
I wouldn't look at the mouth of a gifted horse. Their closed source binary is not huge.
Also I don't worry about updates. Why would I connect my notebook to the Internet anyway? I just don't install them.
I guess it's a matter of time before fully open source display drivers are available and I can do my part too to make it happen.
When it happens I will have an ownable very nice, thin and responsible e-notebook. It will never be connected to the Internet and I will patch it myself if I will happen to want a new feature.
Maybe you are right and it could be more FOSS than it is, but in a world where you don't really own anything valuable anymore I am so elated about the hackability of this device that I'll take a bit of tinkering with binary files.
xochitl (the rM GUI) doesn't need to be run when other GUI programs are running. I don't fully understand the way this works but for anyone interested, here is the link for the framebuffer workaround: https://github.com/ddvk/remarkable2-framebuffer
On rM1 it was possible to write to the framebuffer directly, on rM2 it is not exposed as a device file directly.
The link you are sharing explicitly mentions you need xochitl running with the LD_PRELOAD hack, which is what becomes "the framebuffer server". In fact,
> To do their job, both the client and the server need to know the address at which a number of functions reside in the Xochitl binary. These addresses change from one release to the next.
This is absurdly fragile. In fact, it's even worse than I was guessing :/.
Kobo and Kindle both run Linux too. Kobo still updates every single model they've released except for the first two non-touch models and the 5" mini stretching back a decade. And Amazon is pretty good with updates too.
Kobo is pretty similarly hackable to the Remarkables but they are not nearly as open and free as the Pine stuff. I take a look at what remarkable has updated, and they just still haven't gotten ePub support anywhere close to where it should be. I belive it technically converts ePubs to PDF and displays that?? With large books taking minutes to change font sizes. That to me has completely turned me off their devices. Writing may be better but reading is IMO equally important for devices like these.
I have an original Kobo WiFi (no touch) and the internal storage is a microSD card. You can literally just take it apart, remove the SD and stick new programs on it, start an SSH server, etc.
I also have the non-WiFi version, and it has eMMC soldered on, so it's more of a pain. There's an exposed UART on the board though, so getting a shell is pretty easy there too.
I like the idea of Remarkable but the thing that bothers me a lot is that it doesn't have a backlight. I'd really like to use it to read at night and no backlight kinda kills that.
Do you not use it at night or do you use some other solution for nighttime lighting (like bright ceiling lights)?
If the use case is just reading at night, a Kindle with a backlight is probably a better bet.
That said - I like the Remarkable a lot more, and tend to carry it with me more. The kindle has essentially just become my "vacation" reading device since I stopped taking the train for work.
It definitely doesn't need bright lights to read (well, depending on your eyesight). If I want to read/write before bed, I'll keep my side table light on at 25%, and it works fine. If my wife is still watching a show, the tv alone is bright enough I can generally read/write fine.
Love my Remarkable 2, it's replaced the endless amount of paper pads I used to have - I even sketch on it, which is taking some adjusting to (it ends up being closer to etching than pencil sketching).
But it hasn't replaced my e-reader. I read myself to sleep every night, and 80% of mornings wake up with the e-reader lying on the pillow next to me. If I tried that with the Remarkable I'd smack myself in the face every night. I have a hand-size e-reader (Tolino, a German brand) with a backlight, which I use in dark mode so less light to keep the gf awake. Works great.
I could see myself reading a technical manual on the Remarkable, but I'd still need the e-reader. Two different use cases.
I would also already own a remarkable-2 if it had a builtin light. I do about 20% of my reading with the lights off, and while I can (and do) use a booklight, there's considerable light-spillage compared to most builtin lights and the lights I've tried all either have arms so short as to be hard to position right, or arms so long that the weight of the light overcomes the elasticity of the arm.
What about a normal book light that you’d use with a traditional book? I find that even the Kindle light can be uncomfortable when in complete darkness, so I try to always keep a little bit of ambient light, which is usually enough to read by.
I use a book light with my Remarkable. It works well, but I'd still prefer an integrated frontlight, as long as it didn't affect the writing experience.
Ah yes... that's probably why we won't see one then. The frontlight adds some space between the surface and the panel. That would probably be distracting for writing.
My Remarkable 2 is the best note taking, writing, sketching device I've ever owned. I appreciate the competition in the space and hope it drives more innovation but I don't want to hack on my Remarkable tablet. I just want to write and sketch on it for the moment.
Totally agree. But I've got to the point where I'd like to start hacking on mine.
I have a folder full of startup ideas. I really want a Lean Canvas page template to go with that (and be able to mix page types in a single notebook would be cool, but I'm not sure that's possible yet).
I want to create a "meeting notes" type of notebook, that automatically adds today's date, and lives in a "meeting notes" folder organised by date.
I'd love to be able to sketch in white on a black background.
I keep meaning to get around to learning how to do this stuff... but life has been getting in the way. Doesn't mean I don't want to ;)
I got my wife a Remarkable 2, and for as many Pine devices I own, I think she'd make fun of me for struggling with a PineNote. I'm glad there's more open source development going on in the space though.
I would say if you want a web browser, it's probably not the right device for your use case.
I have a Remarkable 2, and I really enjoy it, but it's more like an upgraded replacement for the legal pad/notebook I would carry around at work.
It does notes and sketches really well. But there's no browser by default on the device. I appreciate it, since it keeps me focused on what I'm doing without distractions (like HN :D ).
There is no web browser on the ReMarkable. On purpose. Their mentality is that the device should be a distraction-free note-taking, idea-sketching tool.
There's no web browser, but in theory there's a "send to remarkable" plug-in for other browsers (basically print to pdf;sync to remarkable). It's not really usable, for various reasons imnho.
I also like the large sized reader. It's not something I need anyone but when you find a technical manual or text book as a pdf only the remarkable is a pretty good reader. I do like the Kobo for most of my reading but it's nice not for the oddly shaped big stuff.
I own several of the Pine devices. They are all alpha in different ways but that's fine, I'm paying for the future.
The thing that worries me is that they are launching a lot of products. They are all adjacent in some ways.
But, should I as a customer, or Pine as a company, be worried about the cost of supporting all these different kinds of devices?
I recall reading a long time ago that Google intentionally offers products where they can get away without offering support from a real person. That's obviously not true anymore but many of their products are entirely self supported (or GTFO...). The obvioys reason is that support is so incredibly costly and you never recoup a penny of that cost because it only happens after the purchase is made in most cases.
Is this the true brilliance of Pine, that they've created a community of people around them that are willing to help get all these products to the next level and they can avoid this costly facet of any organization? Or, is this a fatal mistake that will kill Pine?
I'm super excited about all their products and some of them will undoubtedly sit in my closet after the initial use. But, is that ok for the second wave of users who will demand something better?
I've had many of the same thoughts as you, and I have some theories. I'm not affiliated in any way with Pine other than I love (and buy) a lot of their stuff.
My theory is that they view themselves as the hardware people, not the makers of consumer devices. They follow an "if we build it they will come" approach. They have dipped a toe in consumer-facing stuff but the bulk of their stuff is "we make the open hardware, let the software people figure it out and support it, etc." I'm very comfortable with that, especially given that it allows them to make things really affordable (which IMHO is a super important aspect). It especially seems as though Manjaro is answering the call. I know there are some Fedora community members that are as well.
Don't worry about Pine getting spread so thin that they can't support these devices. The reason being that they don't support them (from a software standpoint) currently! The brilliance of their business model is they are very up front about only producing and supporting the hardware. The software support is entirely on the open source community.
As far as the hardware, their support generally only extends as far as defective hardware. Think DOA battery/display/etc. If a particular revision of a device has a hardware bug, but is otherwise functional, they will tend to fix the bug in a future revision. Customers bothered by a given bug typically have to buy a future revision if it really bothers them. For example, I got the first public version of the Pinephone which has a USB-C bug that only works with dumb chargers. The next revision of the Pinephone fixed that bug and they offered a discounted board replacement for those bothered by the bug.
Their main target customers are (hardware and software) hackers who should understand what they're signing up for.
They are moving to a model where you can buy direct from china and no support; or from in country resellers for more money and support provided. If they can get the second wave to move to the resellers (pay for it) the model looks good.
I have a Boox Note Air--it runs Android, and can do cool stuff to apps to make them work better on e-ink (mostly tweaking the contrast).
It's still kind of slow in practice, like all e-ink. Page turns will take longer than a tablet or of course a book.
It comes with a stylus, but the only note-taking app that works well with it is the built-in one, which is not great though at least it can sync your notes off the device. But standard Android apps that support pen input are unusable.
If you want to read PDFs on an e-ink screen, I think this is probably the best option. You need a much larger screen than Kindles have of course, and the Android ecosystem has some ok apps for PDFs and comics (the Boox has a decent PDF reader but I'd suggest using a different app that syncs).
When it comes down to it, though, I've never really been happy with e-ink. Tablets are just so much faster and more versatile, and for reading in the sun and so forth I'd rather just take a book.
I have Boox Note Air too, it is being used 70/30 as a note-taking device and tablet. It runs fastmail, k9mail, kindle app, firefox and wallabag just fine.
I wasn't trying to replace built-in note taking app, I think I may have gotten used to it? Honestly at this point I quite like it; it's fast (seriously, there is 0 lag when talking notes), it's capable and it honestly works just fine. I love the UI. I totally understand why you would want to replace it with one note or something like that - I'm just saying that current version works for me :).
I don't trust it yet however - I am using Onyx's sync servers, so my content is backed up without encryption to someone's else servers... Since we are talking about syncing - it also works with syncthing without any special integration; my notes are backed up immediately as pdfs on my other devices.
It is slow, if you think of it as a tablet. There are few options in "app optimizations" menu that allows you to switch between ghosting and page refresh speed.
I'm not sure if you can root it / if the bootloader is unlocked.
I'm using it with different stylus - the one from boox max - it doesn't have that magnetic lock, but it's larger and it feels like stylus tip has lower friction on the display.
I have a Boox Note Pro (small one) and I also find it great for taking big PDFs around for reading outside or while traveling. I recently found out about Onyx's GPL violations, though, which kind of sours me on the company and product. There's a discussion on reddit [0], a discussion about that thread on HN [1], and some other stories here and there about the issue as well [2].
Really cool to see a cheap e-ink android device but bummer that the company isn't compliant with the licenses of the open source software it uses.
I also own a Boox Air and I agree with everything you wrote. It is a device built for specific purposes. I get a ton of use from mine. It sits next to me all day for note taking, and I have my Kindle, Instapaper, and Safari Books apps for reading. I don't use it for anything else but that isn't the intent of the device. If you are looking for something all purpose, as you say, look for something other than eink.
This reminds me of another HN thread today about ncurses and text based UIs. Writing software for e-ink displays could be an efficient interface hybrid that included Ncurses-like navigation.
From a general SaaS product perspective, your product comes down to the value of the data you provide, and the best possible user experience is in fact an API (imo), which customers integrate into their own systems, and it just sticks there and generates revenue. If you can develop a SaaS that works on an e-ink display, that's valuable data. It's choosing and solving for an arbitrary constraint, which is inferior to just finding out what people want and making it for them, but it requires us to build a meaningful tool instead of just another dazzling representation. In terms of refining ideas, that it should work in lynx could be an interesting enhancment to the creative process.
Calling it a notebook is a bit of a stretch. It doesn't take notes.
If you’re looking to buy a PineNote in the first batch, you must expect to write software for it, not to write notes on it. The software shipping from the factory for the first batch will not be suitable for taking notes, reading e-books, or writing your dissertation [...]
Edit: It looks like tuxphones is the one calling it a notebook. Pine 64 never calls it a notebook on their site. It's named PineNote, but it's marketed as an "e-ink device" that may be a non-functional prototype on delivery. From their press release: It may not even boot to a graphical environment.
This is pretty much how all Pine devices ship, and they’re up front about it. They’ve always been very explicitly that the Pine devices aren’t meant to be fully formed consumer devices and that it’ll take quite a bit of elbow grease and community effort to make the most out of the hardware.
Not everyone follows Pine devices closely. I was quite surprised to see someone announce a device and call it a notebook, when it lacks the all of the software that defines the category.
This is probably a persistent enough problem that Pine64 probably does need to put a bit more effort into communicating who they cater to. They should be making it clear that nothing they sell is appropriate for a typical consumer looking for a 'just works' experience. Their products are geared toward hardware and software hackers.
It’s worth noting that this is a bit more powerful than Pine64’s other hardware releases, in part because it’s using the same base chipset as its Quartz64 SBC, released earlier this year: https://wiki.pine64.org/wiki/Quartz64
Perfect! Thanks for the link, I was thinking that was going to be about the supported OS status only and didn't think to check it. Looks like all of the boxes I needed are checked except PCIe which already has a tiny patchset in linux-next :D.
Interesting. As an aside the Remarkable runs Linux too and it's somewhat hackable, but its main application is closed source, as is the drawing of the screen (accomplished with temperature dependent waveforms via software).
Its hardware specs are much worse but it's thinner at 4.7 mm.
I appreciate this new product but if it were dependent on me I would have invested in color eInk instead of powerful CPU with an NPU. I guess the build on the community providing a nice environment and handwriting recognition (otherwise I cannot explain the NPU)
Cool. I just dream someone will also create a DE and apps designed specifically for e-ink, on the principle that no piece of screen should be re-drawn unless it actually is to show (or hide) some [important] updated information.
So does the Kindle. I like the idea of a "freer" device but it is worth note to any current Kindle user that with a jailbreak you can get the same Linux shell.
I was hoping for an affordable competitor to the Remarkable, but seems like it is just a competitor not necessarily affordable like a lot of the other Pine products. Not to say it won't be great or it is a bad thing, but had my hopes up when I saw the title. I cannot justify spending that amount for that type of product. Again not a knock as it is nice to see them get into this market just not what I thought when I originally saw that title.
As long as the E-Ink licensing remains the way it is, there won't really be an affordable competitor in this space.
I find it pretty unfortunate, because E-Ink really, really shines in terms of battery life and readability, and I think the current fees are leaving the tech only in niche and high end markets.
I mean simply that E-Ink (EPDs) remains incredibly patent incumbered, and the primary holder does not sell screens cheaply.
Your format and incredibly late reply make me think you're asking some sort of "Gotcha" question here, and I have no idea why.
see:
About E Ink
E Ink is the recognized leader and innovator in electronic ink technology, with over 600 U.S. patents, and 1,374 worldwide patents. E Ink continues to aggressively fund and place corporate priority on innovation, invention, and the *defense of its extensive intellectual property holdings*.
E Ink Corporation was spun out from MIT’s Media Lab in 1997 to commercialize electronic ink and electronic paper display (EPD) technology. In 2009, E Ink Corporation was purchased by Prime View International (PVI), a leading small and medium sized TFT-LCD and EPD provider. PVI was later renamed E Ink Holdings, Inc.
E Ink Holdings Inc. (8069.TWO) is now the world's largest supplier of EPD displays to the eReader market. It has transformed and defined the eReader market and is redefining the signage, architecture and design, mobile, wearable and retail markets with its ePaper technology, enabling a new multi-billion dollar market in less than 10 years. Its corporate philosophy aims to deliver revolutionary products, user experiences, and environmental benefits through advanced technology development. This vision has led to its continuous investments in the field of ePaper displays as well as expanding the use of its technologies into a number of other markets and applications, including smart packaging and fashion. Its EPD products make it the worldwide leader for ePaper. Its Fringe Field Switching (FFS) technologies are a standard for high-end LCD displays and have been licensed to all major liquid crystal display makers in the world. E Ink Holdings is listed in Taiwan's Taipei Exchange (TPEx) and the Luxembourg market. For more information please visit www.eink.com.
---
Edit - I see from your other replies this is clearly intended as a "gotcha" question, but I think you're incorrect in your assumption that volume is the problem. I'd argue that much like 3d printing, the issue is not really costs, but rather patents and licensing... as I clearly alluded to above.
For comparison, Amazon alone is shipping 20+ million EPD products a year through kindles. Most LCD TV manufacturers ship around the same volume, and the industry total is only around 200 million. see: https://www.statista.com/statistics/668519/lcd-tv-shipments-...
Basically - I'm claiming your argument is bullshit. The cost difference is driven by IP protections, not by volume of sales.
Wonder why 2016 saw a rapid increase in EPD devices? It's because they lost that 2015 case in the EU.
-----
So your whole argument boils down to - "they don't do the volume". Which is true but meaningless: Clearly there is demand for these devices, why is the volume not ramping up to match? And I'm saying "Patents and IP restrictions". What are you claiming?
> But there is plenty of evidence, you simply ignore it and then make claims based on your evidence-less "insider" knowledge.
Lets go through the "evidence" you've provided.
> Wired discusses patent restriction here
It doesn't. That paragraph is a quote from Yashar Behzadi, the disgraced ex-CEO of Popslate that stole the money of their indiegogo funders. "Popslate shuts down after raising $1m on Indiegogo". http://oaxis.com/en/popslate-shuts-1m-indiegogo/
> Just look at the relevant patents still being filed by the company here (mostly trash)
I'm not going to debate that with you. But I'm sure you'll consider a patent filed by IBM on linked lists as innovative?
> See patent suits across the globe - Germany:
Yes, good, they lost a patent suit against a 3rd party buyer. I think that indicates the legal system is working properly.
> Here is the position for their patent lawyer,
And what is wrong with that? What exactly is objectionable there?
> Here are articles discussing the 115k yearly buy-in for their tech
Except you've managed to confuse E Ink with the MIT MediaLab Consortium. "MIT Media Lab's News in the Future group and its Things that Think consortium, which consists of about 40 companies, including Microsoft and other heavyweights.
Each of the participating corporations paid up to €115,000 per year and thus obtains the right to use any patents awarded to MIT without paying additional royalties. "
> Wonder why 2016 saw a rapid increase in EPD devices? It's because they lost that 2015 case in the EU.
I haven't seen such a rapid increase.
I remember you used the term "bullshit" to describe my opinions. I've read through your initial claims that were presented with such confidence that any reader would assume they were gospel truth. It is clear to me now that Dunning Kruger is quite in effect with your claims.
When the project was initially announced, Pine was claiming a 60Hz refresh rate, which sounded amazing but is essentially impossible for e-ink at full dynamic range. They've since clarified this:
>Edit August 16 00:09 UTC: A previous version of this post listed the e-ink panel’s refresh rate at 60Hz. This number requires much more context. It takes multiple frames to display most images on an e-ink panel. The visual performance of the panel also depends on the method of converting the screen image to data the panel understands. We will be unable to make estimates of the panel’s true performance in frames per second without much more testing and development. So we’ve removed the 60Hz figure for now. We apologize for any misunderstanding.
Realistically, the best you can do with e-ink is 1-bit with ~120ms refresh (just over 8 frames per second). If you want shades of grey it slows considerably. Dasung and now Boox Mira both support alternative modes that compromise on dynamic range, number of shades of grey, and amount of ghosting to be able to display video somewhat adequately.
> Realistically, the best you can do with e-ink is 1-bit with ~120ms refresh
I'm curious, why is that so? Can't the control algorithm boost the speed by sending higher voltages when switching, then going back to "holding" voltage?
No it can't. (voltage is applied to entire row - select cells - at once) The algorithm can realistically only affect timing. (have the voltage applied to the entire row longer, but that's not very useful if you have varying shades of gray within the row)
How about a PWM-like approach? E.g. select one row with high voltage, and activate the columns with a much higher frequency (where "longer on" results in more effective power into the cell)?
Will this have a OneNote client? That missing feature makes the remarkable a nonstarter for me and the fact they still don't seem interested in adding one baffles me.
No I'm not interested in the "just email it to yourself" workflow. I want and need to be able to directly interact with OneNote.
Big plus to the relatively open ecosystem of the remarkable is that it's not that hard* to implement yourself. (*hard being a function of tech familiarity here, if you can run/install linux, you're probably fine tinkering)
In my case, I have a few custom scripts that push my notes/notebooks up to a self-hosted Bookstack instance (https://www.bookstackapp.com/). Not something a commercial company is ever likely to make, but workable on a remarkable.
If you're referring to the Microsoft product, OneNote's capabilities are... extensive. I highly doubt any company other than Microsoft has written full-featured clients for it.
The only option I see is getting an e-ink tablet that runs Android. Even then, I don't know if the pen will work.
Not sure from reading the post, but does it have a backlight? I love my Remarkable 2 to death, but the only thing that bugs me is I cannot read something at night when the lights are off. A backlight will make it perfect.
And still has zero actual videos of the device in action, which makes it really hard to get excited about it rather than cautiously apprehensive.
$400 might be cheap compared to, say, a remarkable2, but not if the display turns out to be flat-out mediocre. Then that's $400 better spent on "saving up for a remarkable2".
I think a lot of people missed that only the early adopters batches will come with the pen and magnetic case included:
> We will be making the PineNote available for early adopters later this year for $399. The early adopter’s PineNote batch will ship with a magnetic cover (working with an on-board hall sensor, putting the device to sleep) as well as the EMR pen. Following the early adopter’s batch, both the cover and the pen will be sold separately.
The Remarkable 2 costs $547 USD with a pen and magnetic cover. So right now the PineNote is ~$150 cheaper, but once they start selling the accessories separately, I'm expecting it to be around $50-$100 cheaper than the R2. Still a good difference, but it's not as competitive price-wise as people think.
Edit: Not that price is all that matters, I'm super excited to have a proper Linux e-ink device!
If you had read the sibling comment to your own posted four hours previous, you would have seen that that will also be true of the Pine Note on general release.
