That sucks. I’m going to give that a try in a moment.
Update:
What’s the model of your TV? So others will be aware of this particular compatibility hiccup.
I tried on an Asus monitor, a Samsung TV, a Marantz AVR, and an LG projector. They got audio from from Framework HDMI expansion card…in my case.
Were you expecting audio playback directly into the TV…or did you setup your TV to passthrough the HDMI audio to some other external devices / DAC/AMP / AVR…etc?
My TV is a Sony KD-49X8505B. I live in the UK, it’s a UK model.
I just wanted sound with a video from the TV, via an online app.
Wi-Fi has been fine for me. The only issue I’ve seen is its slow to pick up sometimes when you boot up. The World icon takes a few seconds to switch to the Wi-Fi icon in Windows 11. But as I’m not actually using the internet those 2-3 seconds not a biggie.
One thing I have noticed in my many years of IT Support tech guy is that on the very rare occasion you do get a Wi-Fi chip in a laptop and a WAP/Router that just do not like each other. They do not play well. I just swap the Wi-Fi chip and bingo, all good. Maybe some folks are just using ancient Wi-Fi routers. I see a lot of folks in their homes using 15 Wi-Fi devices off a router that has just 300Mbps of bandwidth!
The RTC battery issue? Well I’ve just decided to live with it. I’ll make sure I use my laptop more and just be careful if I leave it for more than 10 days not using it.
As for the other issues, well a lot of those are just a result of the want for thinner and lighter. I’d like to see the next gen of Frameworks 2-4 mm thicker/deeper so better cooling, thicker cases and larger batteries can be fitted.
The one (actually two) buggers for me:
I admit it could be because of the bad cables that came with my monitor (which otherwise is great), and they aren’t to-spec.
Echoing two issues,
If everyone treated software and hardware bugs like this, they would never get fixed. Just imagine Windows Update bricking 1% of Windows installs. That’s a lot of people, but it’s not everyone. Now imagine the people who have never seen this issue themselves saying that it doesn’t matter, and Microsoft shouldn’t feel any need to fix it.
Speaking as someone who was having the RTC Battery issue for months before Framework even addressed it, it matters. My only use case for a laptop is weekly at best, because otherwise, I am on a work or personal desktop, and if I don’t use the laptop for a week, it makes it that much more likely that the following week, I won’t be able to turn on my 60% charged laptop.
Exactly this.
Look at the BIOS fix for the audio jack polarity. It was for a case of oscilloscope music. I personally don’t have a use case for it, but I appreciate the fix to address an implementation error.
I’m wondering what issue you had that was fixed. Luckily I use the laptop on average 6 hours a day so the RTC|CMOS battery will hopefully stay charged.
There are examples on this forum, sure it’s hearsay, but of people going for weeks without having to plug in to charge the ML1220, so by those accounts if you use the laptop for, say 6 hours a week there should be no problem.
However I am not going to test out the theory 
I was talking about the RTC battery issue. It wasn’t fixed, it was a month or two before the issue was talked about by Framework for clarification. I did explain in the post you replied to that I use the laptop at most once a week, and can occasionally skip weeks, so it is not difficult for me to run into that issue.
Ok so by ‘address’ you mean acknoweldged not fixed
I got the once a week bit, so it’s down to how many hours each week to keep the ML1220 topped up
Yes scary not to use it for two weeks 
Of course you only have to plug it in, not use it, well that was the case before the 3.09 BIOS where the main battery can not be charged whilst powered down/off
There’s no evidence or talk around whether that also means the ML 1220 is not being charged, so now it seems the safe thing to do is power it on to charge it once a week for six hours even if you don’t want to use it.
OH worse it’s not a Gen 11 | Gen 12 issue motherboard issue it’s an ML1220 issue
magnifying corner cases helps no one, and especially it doesn’t help getting them fixed.
Sorry for this thread. I dont meant to make people fight on what is and what is not a problem on the current FW.
I was thinking of 20 years agonwhen Inwas building a PC for a friend of mine… I had decided for thi build to switch tonan Asus mainboard… At this point in time everyonen would have blue screens on windows 98… And allnkinds of bugs…
Sudenly I and my friend realised this Asus mainboard with intel CPU was so well made that those “windows” bugs didn t exist anymore… This Asus mainboard product was very robust piece of hardware!
And as somone mentionned there was maybe 100 small bugs afecting people on other hardware…but Asus decided to solve them all.
I think framework is heading for a very good product by solving every little glitch!
Never had a blue screen since 1996, but then I never built a laptop, that wasn’t really an option and I didn’t use desktops. So the problems you had may not be a s common as you think
Try reading the post you quoted again, and see if your reply even made any sense.
What I did was use a piece of logic to point out a hypothetical situation with a larger user base to point out that corner cases are in fact still highly relevant to some people, even if others like to talk trash about others’ priorities. It’s a basic form of logic used to prove a point, and unfortunately not everyone understands that.
Depends how you look at it. It’s somewhere between a hard brick and a soft brick…depends on whether you run this into the Intel silicon bug. If that’s the case, then the opening of the device (to do a reset) is an internal hardware intervention…which would classify it closer to a hard brick (but not truly a hard brick as no ‘re-programming’ is required).
It’s also beyond a soft brick…because there’s no on-screen instruction even when the main battery has charged. The state of the RTC battery at this point is low or depleted. And the laptop does not power up to even show an error message of “Low CMOS battery” (or to that effect). So by classification, that’s beyond a soft brick.
The cause of the low / depleted RTC battery state being cause by, what seems to be, high RTC drain is either an electrical or firmware related matter. This puts the “not able to power up” into a “brick” classification bucket.
Put it this way:
What other laptop do you know that can’t be powered up after sitting on the shelf for one month, with a healthy main battery charge, that came from the manufacturer within 2 months of product arrival?
Not sure about that as the designed drain is 0.03mAh so 0.03 x 24 is about 0.72 and there is only 17 available. So 17/0.72 = 23 days and 23 days does seem acheivable if the ML 1220 is fully charged.
On other laptops they may
a) use a larger CMOS battery and
b) more relevant the CMOS battery may get charged from the main battery
It is this last part b) that seems to be a ‘failing’ and hopefully can be ammended.
The question I have (may not be a correct question) is whether the 0.03 figure is the designed drain rate capability of the ML1220… Does that implies an upper-bound drain limit, or a nominal drain expectation? If it’s the former…and the Framework Laptop is constantly draining at the upper-bound…then I would think it’s a poor design.
It’ s called “Continuous Standard Drain (mA)”
That implies 0.03mA is more than OK but common
Other laptops use the same battery.
30µAh is really quite little
but
Most modern chipsets can keep the RTC running with less than 10uA of current from the battery, with 6uA being a typical requirement.
Note for ref:
Good day PC masters/expert/etc, can I ask something? about my computer, the cmos battery of my motherboard just last with in a week what should I do? need some help or tips, thanks a lot.
Now that is even more scary
With the 10µ they only mention the RTC not the CMOS drain so I’m not confident about the claim though it may well be relevant.
Still looking for a reasonable comparrison.
The design can be wanting in terms of drain or that it is not charged by the internal battery.
The drain even if a bit on the high side wouldn’t be a problem if the overall design allowed charging from the main battery. I’m sure there is a way to resolve that myself if it was an issue.
Agree. Someone will have to see if this has been implemented on the 12th gen board.
I’ll say it more clearly this time. I was not referencing the Intel silicon bug with my previous post, but a hypothetical situation. I was only trying to use this hypothetical situation to prove that these “corner cases” are very important for some people.