News for hackers. Stuff that matters.
Re:Reviving a four year old reMarkable 2 by JohnKemeny on Monday August 10, 2026 @06:53AM (#49242030)
You don't have to "revive" the device in order to use it.

The problem was: out-of-sync device clock prevented software updates which in turn prevented cloud syncing. You don't need software updates or cloud syncing for the device to work.

The fix is to set the clock and do the software updates.

Re:Reviving a four year old reMarkable 2 by nextlevelwizard on Monday August 10, 2026 @09:38AM (#49243511)
And why is time such a hard thing to handle in 2026?
Re:Reviving a four year old reMarkable 2 by 0x6c6f6c on Tuesday August 11, 2026 @08:36AM (#49257320)
Time can be an issue connecting to Wi-Fi. Devices who've lost track of time often can't properly negotiate access to then get NTP updates to their time. Perhaps this could be solved, but it's a common problem for devices left for the batteries to go dry.

It is a bit sensationalist to say this is reviving it though, which makes this sound like some wild issue.

Re:Reviving a four year old reMarkable 2 by yencabulator on Wednesday August 12, 2026 @12:23PM (#49274915)
Frankly, consumer gadgets where time is >10 minutes off of trusted time service should force-set their time, instead of giving up.

Defaults that make sense to servers with dedicated ops don't make sense for consumer products. Don't just run a default-config NTP client in a consumer product.

Re:Reviving a four year old reMarkable 2 by fhn on Thursday August 13, 2026 @11:48PM (#49294538)
why does the date/time matter? Just update the thing.