No, that definitely doesn't sound normal or expected! For the battery OR the clock. Hope you get it all sorted out soon!
Just for an update on this, here’s what it looks like this morning. More than 1.5h slow after 24h! I was keen to buy the planner, but it’s not going to be very useful it time is so poorly handled.
A minute or so drift per day, rarely exceeding 2 minutes total because it corrects itself off the network (if connected)—has been the norm for me.
(I made the Playtime clocks collection, which wouldn't be much use otherwise!)
Might be worth contacting Support to see if you need a swap. Hopefully it's a software fix though!
@james could we not marked this as "solved" until an update is provided? I'm extremely frustrated. I unplugged my device for a moments and now it's stuck at 75%.
The charge value bug is being investigated right now. We should have a fix out for it in either 2.0.2 or 2.1.
I'm sorry this is happening to you. We're getting several reports of the issue and we're investigating it now.
Just wanted to say my new play date is exhibiting this same behavior. Very quickly “charges” to 85% and tops out there. Doesn’t seem to charge past 85% no matter how long it is left charging. Hoping for a fix soon.
My play date also doesn’t seem to charge properly only charging up to 89 percent each time???? Pls fix
Please update to 2.0.3 and see if the battery indicator goes up to 100%. Let us know if you continue to have troubles.
Same here. Mine is up to date. Won’t charge past 84%.
Unfortunately same here. Mine arrived this weekend and won't charge past 83%. I'm running version 2.0.3.
I have the same problem, running v2.0.3. But managed to get it to 100%. I have a cable that displays the wattage being used when charging devices, so here's the process I did:
connected to wall charger. got all the way to 83% in about 10 minutes using the max output provided by the wall charger
At 83% it was stuck for a while. and the cable was showing 1.6 watts for about 20 mins and then it went to 0 W.
I unplugged the cable, replugged, no change.
Changed from my cable to the original playdate cable, and plugged it to a PC. The battery went immediately from 83% to 90%
waited 2 minutes, unplugged and replugged cable, and it immedately went to 100%.
So I think the battery should be getting charged to 100%, and this could be a syncing problem between the battery status and the device, maybe?
I'm led to believe that any modern device's battery doesn't really have a fixed, concrete "charge level" but rather a complex set of factors to measure and estimate in software to come up with the oversimplified number we all like to have. And I think the Playdate lacks a dedicated battery measurement chip, making that even more true. (Correct me or add detail if you know more!)
So the software-displayed NUMBER could be a pretty separate issue from the charge itself and resulting play time.
I have one of the early Playdates and I've seen the charge go up or down quickly after plugging/unplugging cables—or even exiting an app to the launcher. Or at least I saw that a year ago... I kind of stopped paying attention!
Maybe the software for estimating that % number just needs more refinement? (Either way, my Playdate lasts a long while so I'm happy!)
That's exactly it. In my original prototypes I did have a "coulomb counter" chip but somewhere along the way that got removed and I didn't notice, leaving us with only the battery voltage to guess at what the actual State of Charge might be. And the relationship between voltage and SoC is far from a one-to-one mapping--there are lots of extra variables there like how long it's been charging/discharging, how worn out the battery is, random manufacturing differences.. Even if we did have a function that could tell us a percentage from that info we don't have a way to track it all.
So what we have instead is basic voltage->percent mappings for charging and discharging, then some
hackery heuristics so that when you switch between the two the percentage doesn't change wildly--though, as noted above, there are some cases where that isn't doing its job quite right. Added on top of that is the problem we had with some recent boards where the voltage ADC was miscalibrated making it look like the device isn't getting to 100%, though it was actually at max voltage.
If only we had that coulomb counter.
Same problem with my new playdate. Just got it and I found the battery problem. Slowly charging and maximum capacity 83%.
I hope it’s possible to fix with update…
Don’t want to return my device.
I have this exact same issue. v2.0.3
First few days it only charged to 83% after a very long time. I was able to get it to 100% but then it stayed at 90%. Then only 10% after leaving it on the charger for 24 hours. I tried to restart it and it only displays the dead battery image.
I have same problem with charging. I hope fix will be released soon
I got my Playdate on September 21. I haven't played it a whole lot, yet, but I've had to charge it quite often.
Yesterday it was down to 10%. I charged it back up to 100%, and this morning it was back down to 24%.
After charging it back up again, I took a look in Settings to ss if there was something there that may explain it. I had Settings open fore about 15 minutes, and when I exited it was back down to 84%.
I don't know if it's a fualty battery, or what the deal is.
I’m noticing a difference with 2.1.1. Immediately saw charge level jump to 96% after updating, when previously it never went past the 80s. I realize it’s essentially just the displayed level and not an actual battery issue, but it is annoying. Hopefully the reading is a little better now. Will update post later, just updated to 2.1.1
I've had battery issues since 2.1.0. Before that I could leave the console on sleep for days. Now I lose 20% charge in a few hours. Battery charge level behaves so erratically that it's hard to get a sense of what is going on. I'll be at 80%, charge for 5 minutes and be back at 100%. Then I'll leave the console on sleep and 10 minutes later I'm back down to 84% or so. It's worth pointing that I have 2 consoles and both have acted the same since update.