I would love to buy the 16 as a replacement to my Dell XPS 9500 (loaded) 4 years old. I found framework a week ago and love the concept. Last night I watched the Netflix special ‘Buy Now’ which Nirav Patel is in.
The deal breaker for me is:
No Touchscreen
No Wi-Fi 7 802.11be without paying for another card…
No Windows Camera Hello
Hopefully framework is listening and can provide a update
Keeping in mind that I am just an end user, with no insight into the roadmap, I would say that you may be waiting a while. A new webcam module was released not long ago, so presumably any changes there will be a ways off. There have been calls for touchscreens for a while, but nothing has come about. My guess is that the addressable market does not justify one at this point in time. Finally, the expense to swap to a newer card is minimal. The universe of wifi 7 devices at this time is small, but over time that will expand, at which point a wifi 7 card might become standard in the machine.
The wifi 7 issue is easy. Framework only sells 6E cards at the moment, but you can absolutely bring your own.
Mediatek MT7925 is widely available for under $30, sometimes way less. It’s what I’m running in my FW13 at the moment. Decent support on Linux, though some Wifi7 features like MLO are still a bit of a work in progress.
BE200 is not compatible with AMD mainboards AFAIK due to, well, Intel. Enough said.
There’s two or three Qualcomm chipsets out there, NCM865 for sure but I have heard of others. Driver support should be researched thoroughly first though.
Hey and welcome! I’ve upgraded from 9700 three months ago when I fried its USB ports after suffering with that piece of crap for 4 years (I’ve had the one where mobo would discharge the batter even when plugged-in and no warranty so I could participate in the recall).
It heavily depends on how you use the laptop.
For me 1 and 3 were also a concern, but my FW16 is mostly plugged into my workplace where I’ve got wired ethernet, two monitors and a Windows Hello-capable camera, so most of the time I don’t have a problem.
Still, miss the touchscreen every time I use the laptop on my lap, especially in confined spaces. And the fingerprint sensor is less convenient than the Windows Hello camera for sure as well.
I’ve heard somewhere on the forums here that FW16 is capable of supporting the touchscreen digitizer if ever Framework or community make one. I would definitely put down 500 bucks for a glass-covered touchscreen LCD or OLED, and hope they’ll release something in the next several years
Yes. The FWL16 and FWL13 both have touchscreen pins on the motherboard display connector. Both i2c and usb.
But using those touchscreen pins yourself would be rather hard currently. Trouble is that there isn’t a standard for motherboard-side display connectors. So only the FW cable is compatable with the motherboard-side. But since the current screen isn’t touch, the display-side of the cable doesn’t have touch pins, there is no place for them on the non-touch connector. And I understand custom cables are prohibitively expensive for individuals to have made. So we effectively can’t access those motherboard-side touchscreen pins at a reasonable price. Someone could maybe find a touchscreen which uses usb for touch and feed it with usb from elsewhere.
They shoulda routed them out to a pad or a JST connector on the display-side PCB. Probably, wouldn’t have cost much, but as with the removable wall on the back of expansion bay, would have enable more crude community mods.
Still, this fills me with more hope for a first-party touchscreen at some point which I would anyway want because I want a glass-covered one
The FW16 does have a fingerprint sensor that supports Windows Hello, so if you’re just looking for some support of that feature it is in there (and works decently well in my experience)
Thanks for all the responses. Still up in the air. Not sure I want to pay for another loaded XPS (16). The Samsung Galaxy Book Ultra 5 will be high on the list and the 16. ASUS is out, they just bought back their flagship router and two mesh nodes…