4 ms·

That is absolutely brutal lag! It would feel like using a 10 year old phone with today's bloatware!

• newnewpdro 8y ago
  It's a devkit running in-development software, for all we know there's thousands of lines of logging being written somewhere while interacting with the display. What's important to take away is that the devkit is stable enough to demo, the touchscreen, display, and backlight control are all working.
  • solarkraft 8y ago
    One one hand: Of course. On the other hand: How good will it ever be? I'm really concerned about the UX.
    • newnewpdro 8y ago
      Doesn't the ability to trivially iterate on the entire software stack running the device allay those concerns? If a good chunk of the GNOME/free software community ends up with a librem5 in their pockets I think userspace progress should be pretty well covered.
      • jancsika 8y ago
        That you can potentially read the code for the entire software stack doesn't mean you can trivially iterate on it. For example, suppose the latency culprit were Firefox's CPU-based repainting. (I don't think it is as I can scroll just fine on my Chromebook with FF.) Changing Firefox to fill the scrolled area using the old Iphone checkerboard-style as someone mentioned above is non-trivial. There's nothing Gnome devs can do to make that happen, short of stopping work on Gnome, becoming FF devs, and submitting a large patch to FF. On the other hand, having access to the entire software stack plus specs (and firmware?) for the entire phone definitely gives them a higher probability of cutting into that touch latency.