At this point I think it would be fair to consider the 12th gen abandoned. When a product no longer receives security updates, that tells me the product is at the end of its lifecycle and needs to be retired.
Pretty absurd given these released just last year. It’s ironic that this laptop has become the shortest-lived laptop I’ve ever owned.
If they do ever release a working patch, I wouldn’t even call that continued support – I’d call it a resurection.
This echoes my feelings exactly.
Based on my feelings, most of their dev team is focused on framework 16 and 13th gen framework 13. They simply don’t have enough people to support 12th Gen. In contrast, they have the full team to work on 11th Gen bios update when there is only one bios need to be updated. However, I will expect at least one more bios update in the worst case because of the battery support. My suggestion for Framework is to hire more people.
The fact that what you posted is your impression, speaks volumes. If there is a lack of support and the product is dead 1 year after arrival (not that I’m saying it is, because there is no written policy that states how long support will last) then any press about R2R or more specifically how “green” the product is amounts to little more than greenwashing.
Framework is fortunate to have a tech savy userbase, who will test those Beta bios for them, knowing it can lead to issues.
For my part i install these versions, because i want it to come out of beta asap and be as stable as possible.
Code is written by humans and humans make mistakes - thats fine.
What is not fine with me, is putting a Beta Bios out there, that has some serious issues, is not downgradeable and then not release anything (not even a new Beta) for 8 months.
Didnt know if i should laugh or cry, when you talked about realistic expectations here…
Sure weekly updates probably dont make sense, but just coming out every few months and saying “we are working on it” is simply not enough anymore.
I realize that there are growing pains inside the company, releasing 3 models this year.
Specially in this situation you should focus on delivering the initially promised feature set.
Instead you want to include the 61WH battery support and seemingly some other features, taking additional time.
Please stop treating your active and supportive community like that, or one day they might be gone .
Well, since Framework is quite blunt in this thread that bios support for the 11th gen will be discontinued after just two years, or at least massively scaled back after all, I have increasingly less hope for this and future Gen 12 updates.
Since the Gen-11 bios issue is about the usability of Intel wifi cards, and a complete mainboard update is advised as solution, I would also call this greenwashing. Then I can better buy cheaper devices with hard-wired Wifi cards and batteries and exchange them when they are older (and after a few Bios updates 
)
But the sales success of the 16" devices seems to prove Framework right. Maybe they can just do without us few „demanding people“ here in this thread as customers?!
In any case, I’m still curious how Framework will provide the announced business support with such “dedication”.
Sorry if this sounds increasingly frustrated, but currently I am. Both with the lack of updates and with the very questionable information policy. I can’t and don’t want to imply anything with this, but I find it very hard to understand by now that there were two internal test versions and it wasn’t possible to bring out an at least partially corrected beta version in 8 months.
My understanding is that they are currently crazy busy for the FL16 & AMD launches, and they’ll have more time after that.
Now if everybody could stop being so dramatic about it… (and the reality is really deformed in your words, like for example NO nobody from FW is being “blunt” that I can tell)
And no, nothing is being discontinued.
Hell, they even recently released a hardware fix for the 11th gen!
So software will even more continue to be supported, and fixes are expected to be released.
Sure they havent publicly dropped support for the 12th gen, but I almost wish they would explicitly drop support instead of leaving it riddled with vulnerabilities and still calling it supported.
@Mapleleaf :
My own initial wording was „frankly“ when writing about the 11th-Gen-Post, but google translate suggested „blunt“ when I checked my text there and so I used that. English is not my first language so I don‘t always catch all nuances of word meanings. Sorry for that.
Aside from that I don‘t see any deformed reality. I was simply trying to sum up my current impressions and trying to explain why I have them. That these arise from a certain frustration caused by (too?) high expectations I was trying to say in my last sentences.
I can understand why some are being dramatic…one beta release in a year for the 12th gen Intel boards, does not cut it. It is a problem, and I think some may believe that by being dramatic it might actually get the attention it needs. I don’t believe that is the case, but yes continued commenting on having issues with the current state of things is the only outlet customers have left to voice their displeasure with the situation.
None of which are remotely exploitable without extended direct access, so not a huge deal, but yes it absolutely should be taken care of.
Folks, if you have specific, detailed questions you’d like answered about BIOS updates, list them and I will ask the appropriate team.
That said, the linked thread I said I did not forsee a feature update to BIOS happening on that generation is was not stated as fact. It was my assumption. I did not state this as a done deal, that is an engineering question.
I should have been clearer on this. But the issue on that thread was a feature request.
Now, if we can focus on specific concerns, please list them and I will ask the appropriate team for clarification.
If you are experiencing a specific error or another related issue, feel free to open a ticket.
The specific concerns that I am aware of are:
I personally care more about that last one (and any other potential bug fixes or stability fixes), as that is likely to be the most impactful for my use-case.
Going to let this build up over the weekend, I have a reminder to check this Monday.
In addition to what @serisman said:
To me, the thermal throttling issues are by far my #1 issue, and make the laptop pretty much useless to me for gaming (even light/old gaming; think Stellaris or Age of Empires II). Framework support has been unable to help, even after shipping me a new mainboard. It’s pretty clear to me that this is a firmware issue (or something even lower level if the firmware isn’t responsible).
Some specific questions from me:
If there isn’t any answer available for those questions, then I have a followup:
Been following this for potential fixes with USB-C power negotiation under CPU load changes.
Many threads about the laptop randomly charging/discharging when the CPU spins up seem to nebulously lead to this one, but there’s no clear answer if the BIOS update is expected to fix.
This class of bugs seems to make usb-c useless if plugged into anything that can provide power (hub/monitor), even if it’s also plugged into an official power brick from another usb-c port.
Thank you.
For your issue, please see [RESPONDED] Excessive CPU thermal(?) throttling on 12th-gen - #13 by Matt_Hartley
Just replied there, let’s keep that on that thread. Issues an fixes already in that thread need to remain there or we end up with a spider web of mismatched threads.
If you have specific questions, as in security updates or features found on 12th gen, but not 11th, please list your questions as others have done here.
For issues found on other threads, please update your experience or issue there on those affected threads to keep this thread from going off the rails with side-topics.
Again, to keep this thread open:
Security and desired feature questions are welcome. Per: 12th Gen Intel Core BIOS 3.06 Beta - #298
Bug or issues experienced, please keep those to their original threads as they may have been resolved for the original op(s). That is to be determined on the existing thread.