Hi I presume you are referring to the fact that the RTC discharges so quickly that it can’t support a power on.
That
a) it requires external power to up the voltage on the RTC to enable power on and
b) in the exteme case that the RTC voltage drops very low it needs removing, replacing and the latop put on charge for 24 hours to get the RTC up and running.
I want to be sure as I have this other topic trying to clarify that it is all down to the rechargable RTC not being fit for purpose, when the latop is switched off for a week or two.
This is the exact issue. Is there unusually high idle drain from the main board that made framework choose this rather than a traditional multi-year design that other computer makers use? I don’t understand why they won’t admit this is a problem.
Compare to a 12 year old ThinkPad and it’s pretty embarrassing.
Exactly. It is one of the questions I am going to ask. How come the RTC can be drained so quickly ~ it must be a flaw.
More that 2 to 3 years with a non rechargeable 2 weeks with a rechargable. Apart from tottaly inconvienient the RTC will wear out very quickly so where is the advantage?
Totaly user unfriendly.
But given how quickly they designed and made an otherwise oustanding machine I suppose something had to go wrong.
I don’t want to take away from this. I wanted this to be a machine I keep for a really long time and support the framework mission of transparency and repairability. The build quality is great but my experience with CMOS and laptop clock batteries has been that it’s so rare that I have to replace them that I just can’t understand what is going on here. I’ve never had to manually set time on any tech I’ve ever owned as much as I have had to on the framework laptop. It’s just a super poor user experience so much so that I don’t even want to use the machine anymore.
The transparency… Or lack there of is the biggest concern I have given how framework started.
I think most people won’t find the RTC thread by searching and instead will find this one when searching for the symptoms of the framework laptop not powering up unless it is connected to AC power. Since the discussion is continuing in the other thread, I thought we probably need to link to it again:
I had an unusual issue that occurred with my Framework laptop.
I have not used my Framework laptop for almost a month. Last night I decided I wanted to charge the battery the format a external drive to use as I want to dual boot with Windows and Linux with the laptop. I connected the power supply and noticed immediately the battery charge light didn’t turn on. So I attempted to turn on the laptop and nothing, not even the power light on the finger print reader/power button came on.
I removed the modules except for 1 and nothing… Tried connecting the adapter directly to the port and nothing. Next I thought it was the battery so I took the keyboard off but also check the connection on it and it was good. Disconnected the battery and reconnected the power and nothing. So I look at the CMOS battery thinking it could have gone bad and I need a replacement but then I saw it said rechargeable. I decided to take the CMOS battery out and waited 10 seconds to take a gamble and see if the CMOS needed to clear.
Put the CMOS battery back in and connected power back and the charge light came back on and I can turn on the laptop but it take a little for POST to kick in but it is working now.
I just found it odd. Could the reason be is because I had it not used it for so long and the CMOS battery needed to be recharged and/or reset by removing it?
This CMOS battery pull is required in the case where the Intel processor is in that ‘stuck’ state, caused by low CMOS battery voltage…if I’m not mistaken.
In some cases, the processor doesn’t get into a stuck state, and the CMOS battery pull is not required. Just need to plug in the USB-PD.
Current known workaround to avoid either cases all together is to make sure that you:
Charge the CMOS battery fully to start with, by having the laptop plugged in for 24-hours. AND
Plug in the laptop at least once a week, for 8 hours.
I have no problems with the product. The issue I have is not knowing before hand that the RTC battery may discharge in little over a week in some circumstances which encumbers the user to effect a workaround.
It’s the lack of prior information from Framework before purchase that see as being irresponsible given I consider many may not use a laptop for weeks and on occasion for weeks.
However this doesn’t effect me as I use it daily.
Where the problem will arise for me is as time passes and the RTC dies of it would happen more often and if I buy a future laptop I can’t happily put this away and bring it out a few years later to use it, as I can will my 25 year old Dell.
So yes I agree there is a lack of prior information but that’s all and of course you don’t seem to have a problem with that as you encourge to pass this lack of concern on.
What may be worse is you and anyone who acts in the way you suggest may be even more questionable as Framework can argue they never let the prototypes sit around for a week or two to see what happened, so they were ‘ignorant’.
I also wanted to add to this. The reason the laptop takes more time than usual to load on first boot after reseating the RTC battery is that it has to retrain the RAM. This also happens on desktops when changing RAM, or I believe when clearing CMOS on those as well, and will take longer the higher RAM capacity is in the system.
Below is someone’s blog about this issue. Thanks, someone! I plan to use this page as a secondary reference source (it’s like a second option, not a primary source) for this topic on the Framework Wikipedia.
Yeah, I agree! In the case of the Framework, while many things happen in this community forum or outside the community every day, it’s important for someone or a web media to write an article about a specific topic as a second opinion. Wikipedia encourages adding a secondary source to the content on the page. Adding only a primary source (= article by Framework) is not enough.
I actually already added the blog page above to the Wikipedia page.
I quoted your post with the review link in another thread with a call to action. I believe the issue has been summarized quite well in that thread, and it’s the thread that @nrp has already responded to before Framework, and their support team started ignoring the issue.
My wording definitely wasn’t the best. To clarify, the message I was trying to get out was more along the lines of “For those that want to continue expressing their dissatisfaction with the way Framework, as a company, is handling their own proposed resolutions to the issue that several users are claiming to have, here are some options to continue bringing this to their attention through multiple avenues.”
That just wouldn’t roll off the tongue though, so I decided to simplify my argument. A little too much apparently.