this post was submitted on 28 Oct 2023
1 points (100.0% liked)

Remarkable

56 readers
1 users here now

Useful Links

founded 11 months ago
MODERATORS
 

I just got the reMarkable 2 some days ago. I noticed the battery drops by 1% for like every 10 minutes of use (wifi turned off), and I think this is a bit too fast for the two weeks period everybody is talking about.

Is this normal ?

you are viewing a single comment's thread
view the rest of the comments
[–] StockMarketCasino@alien.top 1 points 10 months ago (4 children)

Mine drains excessively fast since their later firmware revisions. I've had mine since 2021.

Originally it would last 2 solid weeks with regular daily use.

Whatever the updates did to the Wi-Fi, it relentlessly consumes the battery. Even if the unit is idle in my bag and the Wi-Fi is on, I'll lose 40%.

If the unit is asleep, the Wi-Fi should be off and not aggressively searching for a network.

I love my RM2 and it's one of the best work tools I have, but I'm not keen on needing to be near a charger when not in the office.

[–] exophades@alien.top 1 points 10 months ago (3 children)

If you turn off the Wi-Fi do you still notice excessive battery drain ? Is there any way to optimize battery use and reverse the changes after updates ?

[–] StockMarketCasino@alien.top 1 points 10 months ago (1 children)

The battery still drains, but not nearly as fast. Though it shouldn't be draining at all given the screen isn't on and Wi-Fi is in airplane mode. I have a feeling it's still trying to sync or call out to cloud services that aren't activated.

[–] exophades@alien.top 1 points 10 months ago (1 children)

Then they probably messed up something in the latest update. I read somewhere that the screen refreshes (when it turns black and then white again) make the tablet reach peak consumption for a moment and drain the battery. I am wondering how one can minimize these refreshes while writing on the tablet.

[–] StockMarketCasino@alien.top 1 points 10 months ago

It's def something firmware related as this problem was happening in earlier version, then fixed, then came back.

load more comments (1 replies)
load more comments (1 replies)