@d_p my framework is my personal laptop and I use my work laptop much more frequently – usually only running the framework when I take it somewhere on weekends, etc. It’s running Manjaro Linux (with sometimes Windows 11 in VirtualBox but then I always feel dirty!). It’s a Batch 3 i7-1165.
I’m certain I haven’t run my Framework in 4 weeks (because I haven’t used it since I was sick with Covid) and I just powered it up. It hasn’t been plugged in since the time I used it before the last time I used it. Main battery is @ 62% and it started up without any drama. I didn’t notice any problem with the time – although it might’ve reset the time automatically already if it was out. But I definitely didn’t need to open it up to turn it on.
I do feel bad for those of you that are having a serious problem and I really do wish you luck sorting it out with Framework. In my experience they really are interested in making things right so hopefully this is just snafu on the support/communication and you’ll get the attention you need soon.
Do you recall whether you had to plug in the USB-C/PD to power it on after not using it for weeks? i.e. Assuming the laptop was completely unplugged all this time.
Not having to open it up means one thing: You didn’t run into the Intel silicon bug…that time.
Hey @Richard_Lees, that’s great! Just like @Second_Coming said, I have to plug into AC even if mine is at 60%+ internal battery and because Windows is my native OS, the clock must be set manually.
the board is also designed for a rechargeable battery and will attempt to recharge whatever is connected to that connector, I don’t think a non-rechargeable battery would like that.
As I mentioned before, some kind of adapter goes in the battery socket which leads to a larger battery that’s wired to it. That or can the boards be retrofitted to just take power for this from the main battery?
To add to what @Richard_Lees@Senhara and @2disbetter are saying, I have never had a problem with the RTC battery going low and requiring me to open up the laptop.
The longest it’s ever been off the charger is approximately 2 weeks. With the OS shut down, the battery dropped maybe 5-10% in that time. It started up fine and I put it on the charger.
When I put the OS in standby, after 2 days, the battery was completely depleted. I put it on the charger and it started as normal.
So it bears repeating that this issue does not affect everybody.
…and no, Framework doesn’t pay me, I’m not a paid shill.
The time I was just describing (4 weeks not used and not plugged in) I pulled it out of my bag and turned it on - didn’t plug it in. No power on problem and no RTC problem that I noticed.
I guess that’s the main point I was trying to make about this issue – all units might have a fundamental problem with being off for an extended time but there is definitely some variation in how long the laptop needs to be unused before there is a problem, and the people who are having a serious problem if they leave it unused for only a few days are definitely not indicative of everyone’s experience.
During some of my earlier testing when I started seeing the issue, I had actually measured the voltage when the laptop was off and not plugged in, off and plugged in, on and plugged in, and when it was on and not plugged in. I believe the laptop also charges the RTC battery while just being turned on, so that may not be a conclusive test.
In all the posts I’ve seen where people have the issue, they describe leaving the laptop without using it, so it seems like just not charging it for a month, while it would drain the RTC battery voltage some, if you use it for an hour or so during that time, it may not drain to the same levels.
Could this even be due to quality variations of the RTC batteries?
I never had any problems with mine, but I preventively exchanged it with another one I ordered online as a spare because it was slightly bulged right from the beginning.
The spare battery instead was completely plain to my eyes.
Yes quite possibly some are a bit duff. They don’t have that long a shelf life and I wouldn’t dismiss the idea that some where a year old. I don’t see a date stamp on them ??
After dealing with this issue for a couple of days now (and going back and forth with support), I’m glad to have found this thread. It seems odd to me that so many people are popping up with this issue at the same time, while having support say my “RTC battery was not the issue”.
Unfortunately, no. I’ve gone through extensive troubleshooting with support.
Initially they told me to follow this article, and it fixed my issue… for about a week. The next time this happened (this past Saturday), I’ve been told multiple different things.
Initially they told me to update to 3.07 (assuming I was on 3.06)
I told them I’ve been on 3.07, and they then instructed me to bump my battery limit up to 100% (I’d kept it at 80%), and let it charge up for 24h.
I left it on the charger for ~18 hours (just shy of the 24h they’d told me - but this is my primary machine), and upon getting to work the next day had the same issue occur - no PD charging. I resolved it by trickle charging my setup (USB-A to C cable on the righthand side, PD charger on the left). I checked the RTC cell voltage, and it showed 3.10V (support had said “somewhere around 2.6 to 3 volts”), so I assume that’s fine.
This is the point where they said it “appears that your RTC battery was not the issue”. They told me to go through the Full Mainboard Reset process, which resulted in a functional system… but only when charging on the righthand side of it. My left IO ports will deliver power OUT, but now I can’t charge my laptop on that side - Dumb charging or otherwise.
They’re telling me to check the EMI shielding on that side, but I would be under the assumption that if it had been shorted out, I wouldn’t be able to use it for data or outboard charging.
Sorry for the lengthy post, but it seems like I’ve been in a weird moving goalpost situation, and it’s kinda nice to have everything typed out.
It definitely sounds like you are facing a different issue if the RTC battery is charged, and you are still having trouble booting. I hope support is able to get you sorted, so best of luck.
I’m currently asking Support to confirm if this is a design feature or a design flaw. I think that’s a fair question to ask. Buying into a new company and a new product is a trust thing as well as a risk.
I just want to know either way. If its a feature, then I can plan to work around it or sell it on.
If it’s a flaw then I think Framework have a responsibility to fix it or find a way to improve it (happy with either). I was sold this laptop on the idea of being fully repairable.
If after just three months, the first problem I have with it isn’t…well…
So if they cannot, then I think they need to be upfront on the sales page and advise those users that do not live on their laptops day by day, that this is a potential issue.
I note someone has not used the laptop for a month and had left it unplugged during that time and had no problem switching on with having to plug in external power.
So it would seem not a design flaw.
Some people have to plug in the mains after short periods
This maybe as the BIOS/CMOS/RTC ML 1220 battery was not fully charged and or the laptop wasn’t plugged in for long enough even to keep it charged well enough
The third case is where the ML 1220 gets so low that it has to be removed the recover before anything will work, this could be a design flaw
but that is arguable as
a) there is no control over how a person uses the laptop
b) it could just be a faulty ML 1220
In the last situation where there is a repeated failure of the laptop to power on without removing the ML 1220 and that it has has plenty of time to charge then
it could be a motherboard fault in not charging the battery
It could be a duff battery
The simplest solution would be be buy another ML 1220 and see if that works, if not then further analysis of the problem may be helped by contacting Framework.
