Why be impressed? It’s unused for 12 weeks, and wouldn’t turn on.
There’s no indication from the post to say when it first won’t turn on. It could be 3 weeks, 6 weeks, 9 weeks…etc. No one knows. What we know is that it’s been unused for 12 weeks, and on that 12 weeks mark, it won’t turn on.
It’s as if you’re thinking: I didn’t touch that fried egg for 5 years…and it tastes bad now. You’re thinking the egg tasted good up until 4 years and 364 days?
It should just boot up like 99.999% of other laptops would. 
I wonder if in this case the complete loss of power led to an effective motherboard reset, and the memory had to train again, like the first time you ever turned it on.
I’m coming across this more and more on system board replacements and it’s even starting to pop up in documentation.
In some cases, systems that don’t have a RTC battery or that require the motherboard to be separated from it for replacement. Some were just unplugged for a really long time. And there’s others - unexplained motherboard failure - where sometimes instructions are to perform a “deep reset” that’s surprisingly effective.
This whole issue has whispers of that. I don’t think it’s FW specific. Might be exacerbated by the rechargable RTC though…
Right…okayyyyy 
I’m with @Jason_Dagless on this one. It shoudn’t have to be a fantasy for a device to work as expected of almost all laptops for decades have.
As long as I’m not the only one not taking ‘crazy pills’. 
You do tend to find on any tech forum for a product that there is always a totally committed 3 or 4 folks that will defend every mistake, screw up and bad decision by said company to the death. Whatever dumbness happens it’s never the fault of company or the product.
“Yes they put razor blades around the screen bezel, why wouldn’t they?”
Is this true? I could get a 12th gen and just remove this stupid coin cell altogether?
Well, CMonkey is NRP so I guess the answer is yes
Didn’t know that was nrp. Good to know then
I’d be curious how the laptop would fair in terms of the clock. I’m assuming that the RTC would not function along with the BIOS settings being impossible to save if the RTC battery was outright removed. Stuff like Windows time being incorrect on boot might become an issue at that point.
It would be nice to get some clarification on that from someone at Framework, or a helpful tester though.
Well, that directly contradicts what someone from the Framework team said in this Reddit post about the 12th gen mainboard.
You options are are, suck it up or sell it (the laptop or the board) and move on.
No one. They are the options for the 11th Gen battery issue. You live with it or sell.
There wont be a fix so…
After umpteen pages I’m just simply distilling down the reality of the situation. Doesn’t have to be directed at anyone.
There wont be a fix, you live with it or move on. Simple as that.
I’m living with it. Others can too.
The thread can be closed really.
As the song goes “Don’t stop beleeeevin’…”
I’ll leave it there.
To mitigate this issue, I decided to solder on a larger 65mAh ML2032 battery to replace the original 17mAh ML1220.
I’m happy to report that all is working well so far and the larger battery can sustain the mainboard RTC and BIOS settings in between the weeks when I don’t use the machine.
Link to more details: Review, usage and repair of the Framework laptop - YKM's Corner on the Web
…and you only have Intel UHD graphics…and not Iris Xe? (single channel RAM)
Worthy tradeoff for my use case 
It’s actually a real good idea. For my use case though, it’s in my 3D-printed enclosure so this wouldn’t work for me.
The remote battery hack is a great idea – almost something that Framework could / should provide for those whose use case makes this a serious problem!
