I like this idea…but not sure if it poses any security related risk / issue.
(e.g. In the case of a password protected BIOS…anyone with physical access can reset your board with the power button…and no password needed?) A matter of able to reset with 45seconds physical access, vs 90 seconds (unscrew / pull / put back / screw)…
I’m not exactly clear on what information is stored by the use of RTC battery other than time, vs what’s in the NVRAM.
If the main battery is fully charged there is every chance, if the RTC|CMOS battery is fine you will have no problem. My 1165 dual boot Win1 and Ubuntu 22.04 doesn’t use any power when off, and the ML 1220 only requires around 1mA/hour and requires 17mAh to be fully charged
With a main battery of 55,000mAh you can see that if could charge the ML 1220 it would last ‘forever’ 3000 full charges of the ML 1220 from the main battery 
Didn’t occur to me at all - that might be a problem, I agree.
Just chiming in to say this just happened to me, again. Laptop wouldn’t power on until connected to a charger, then went through a lengthy boot process, and Windows had forgotten the time (it was two weeks in the past). As a result a lot of web services wouldn’t work presumably because of certificate security issues, until I corrected the time manually.
I cannot recommend the Framework laptop to anyone until this issue is resolved in some way. I suppose I should be thankful I haven’t yet had to do the full mainboard reset routine and interfere with the fragile CMOS battery holder.
I can’t imagine spending £1,495 on a laptop and not using it for two weeks, I use it for over 6hrs a day
But yes a fix would be usefull and I’m sure is in the wind.
You’re lucky…for now.
Happened to @Christopher_Yarch today:
Laptop Fails to Turn On - Community Support - Framework Community
My laptop wouldn’t boot at all, even when connected to charger.
In the time ive had it, it only happened twice, and I suspect it was due to a Microshaft Winblows 10/11 update because both occurrences (for me anyways) happened when updates were scheduled and in progress.
Do you have the laptop powered on regularly, at least an hour or two a day or 7 hours a week etc. so when the update occurs the battery is ‘fully’ charged and powered on.
I have my battery set to 78% max, I use it plugged in most of the time and often 6 hours a day and no problem with Win 10~11 or updates and no powering issues.
Wanted to add to this thread by saying I’ve also started seeing this issue. I had a flight yesterday and the laptop wouldn’t power on despite fully charging the battery before leaving. Remembering this thread I tried plugging it into one of the USB outlets in the seat, and doing that for just a couple of seconds was enough to get it to power on, and the main battery was fully charged as expected. The same thing’s been happening since then, though I haven’t had a chance to leave the laptop charging for a significant amount of time yet.
The last few months were the first time in this laptop’s life where I’ve used it almost exclusively plugged in with a 60% charge limit, so I’m wondering if that could have anything to do with this issue. It’s also possible that the fact I wasn’t using it unplugged hid the problem rather than caused it, but it’s something worth considering I think.
For now I’ll try leaving it plugged in for a long time and see if that helps. In regular usage it’s easy enough to work around by just increasing the Windows sleep-to-hibernate battery threshold to a large enough value such that the laptop doesn’t actually ever turn off, but an actual resolution would be nice since this has a significant effect on battery life.
What’s the word on this being an issue on the new 12th gen models? I see this topic pop up too much on the forums to not ask.
No report seen in the forum yet. No news is good news.
Already addressed in post 43.
For a summary of that post relevant to @Firestorm980’s question, they planned to reduce the power draw on the RTC battery, and implemented a bandage solution of a clear CMOS button to address potential silicon bugs requiring a full mainboard reset. The RTC battery would theoretically last 2 months after 24 hours on the charger with the proposed changes.
EDIT:
They also added a path to charge the RTC battery from the main battery, so it should stay charged as long as the laptop battery has charge, so no real worry if it works as proposed.
The relevant section of nrp’s post is quoted in my previous reply?
I’ve given up on the issue myself. As power costs have shot up I’ve now switched to using my Framework hooked to a Dell Dock as my daily general machine rather than my X99 chipset workstation.
One runs on around 8 watts and the other runs at 100W+ no brainer really.
…and I said this in another thread:
We’re in the desktop replacement laptop market…we just didn’t know about it.
Yeah I even downclocked my other half’s PC with a FX8350 in it to 2GHz. She hasnt noticed…
Update on this:
Leaving the laptop charging for 24+ hours at 100% main battery charge didn’t help, so I tried opening it up and inspecting the RTC battery immediately after the laptop failed to power on in this way. I was measuring an OCV of a little over 2.5 V, which indicated that it was probably not completely discharged as per @amoun’s post here:
On closer inspection there seemed to be some corrosion on both the cell itself and the negative terminals of the holder on the mainboard like in the picture below (you can’t actually see it super well because in my infinite wisdom I took a picture of brown corrosion against a brown wooden table, but it’s there on the bottom right side):
So I just wiped off both the cell and the holder with some isopropyl alcohol and reinstalled the cell. That was two days ago, and I haven’t had the problem occur since even after longer periods of shutdown than before. It looks like in my case at least the issue was caused by a poor connection to the battery, so if someone else has symptoms this extreme it might be worth trying to just clean and reinsert the RTC battery to see if that fixes it.
I just had the same ‘rust’ problem on another device which created a low voltage
Well, I didn’t spend quite that much on the laptop since I don’t use it as my daily driver (evidently) but I did need a portable device for occasional use. Though the value of that is diminished due to this particular issue…
Great that it seems like the issue should be mostly resolved on the 12th gen. boards. Unfortunately I don’t see how any solution could be implemented for the 11th gen. boards unless the BIOS can somehow be patched to route power from the main battery to the CMOS battery - though I’m not sure how that could be effected while the system is powered off or in standby and of course is impossible if the board circuitry isn’t in place. It seems to me to be a solely hardware issue.
