Are there any updates on touchscreen for Framework 16? I read that the MB supports touch input but there is can find no information weather it is being worked on.
I am looking for a new laptop and Framework 16 looks like a good fit for me except for lack of touchscreen option.
1 Like
Welcome to the forum.
Framework makes all announcements on their blog, and because they don’t reveal anything ahead of time, the forum should never have info about upcoming products which is not on the blog.
You can search the blog with something like: site:https://frame.work/blog touchscreen. Or better, subscribe to their newsletter (bottom of the page), or blog RSS feed.
Framework has not announced anything regarding a FWL16 touchscreen yet. But they normally will not announce anything until they are fairly far along and can ensure there are no showstoppers left.
The mainboard does indeed have both usb and i2c touchscreen pins on the internal eDP connector. But the current cable is not a touchscreen cable, so it doesn’t / can’t carry those lines to the other end.
1 Like
Thank you very much 
.
I am currently holding off purchasing a Laptop to see if Framework add a touchscreen (and have been for about six months now). It would be nice if they do add a touchscreen before I end up buying a less-repairable laptop (for the touchscreen).
4 Likes
Yes, I’m waiting on a Framework 16 Touch too, just like the Framework 12 Touch! With matching stylus!
1 Like
Ditto, waiting for anything with an AMD CPU to get a touchscreen, either the 16 or even the 13 should be fine to be frank. And my old HP 745 G5 is still holding, but is getting very rusty now, even with all the upgrades, so not sure how much more it will bear. Already used my wife’s 13 for a month while the HP was at a service center, and it is just fantastic (regardless of all the Linux issues I’ve had), but would still like my touchscreen option to jump the wagon 
Tried the new BIOS update. No B160UAK01.5 support, unfortunate.
In theory, this is a mint plan. Drop-in replacement for the screen, just swap cables and re-glue display. No such luck.
Ironicaclly this display might work on the 13, due to a lack of a display MUX.
As an early user of the Framework 16, I also have been eagerly awaiting the advent of the touchscreen. As more of us express interest it may move the project along!
I’ve also been eagerly awaiting touchscreen support for the Framework 16, but I’m starting to give up hope after 2 years and two separate releases with no touchscreen support even mentioned. I did buy a Framework 16 already, but I’m sad that touchscreen support has been dragged along to the point that the community has been trying without any help from Framework still unsuccessfully due to the complexity of the 4 lane display cable that is installed by default, but doesn’t have touchscreen lanes included.
That is not fair - Framework have said right from the beginning that there is an I2C lane wired to the display connector to take a possible future touchscreen sensor, but at this point in time I doubt there is code in the EC to handle a touch sensor.
1 Like
Based on what I read elsewhere, there is likely not firmware present to support touchscreen for the Framework 16. Yes, the connector on the main board has support physically, but the display cable does not. They would need to bundle a new cable and display. Installing that will be more work than just replacing the screen. That is what I meant.
Why would you expect the cable to the screen to have the relevant wiring when neither the screen or base machine supports a touch screen? Wires and pins are not a no-cost option.
I don’t know if the cable is supplied by Framework or by the screen manufacturer, but when a touch screen does become available I would expect it to be supplied with an appropriate cable.
Framework is marketed as an upgradable platform. Unless the connectors on the screen side are incompatible eg. 30 vs 40 pin It would be reasonable to include those two additional wires as upgrading to touchscreen, or even adding something custom on the I2C bus are some of the expected courses of action.
They are.
The screen uses one of a few quasi-standard display-side LCD pinouts, shared with many other screens. The pinout has no place for touchscreen pins.
Internal displays are not like external ones. They aren’t no-setup, no-configuration plug-and-play, they don’t all use the same connectors, or the same pinouts even if the connectors match. And touchscreens can be a separate complication. If it’s i2c connected, that is not plug-and-play in the slightest. Each different touchscreen controller may need to be talked to in it’s own way.
Tried, but got stuck with the display MUX.
Here’s hoping they add a touchscreen eventually. I don’t know how well touchscreens work on linux, so maybe that’s a challenge somehow? Either way, I can’t wait for it to happen. I’ve owned this laptop for some time and I still am looking for improvements.