Announcement

Collapse
No announcement yet.

Purism Shows Off The Librem 5 Linux Smartphone In Action

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #41
    Originally posted by QwertyChouskie View Post
    Oh cool, didn't realize this was a thing! What OS runs on it?
    Just Ubuntu 19.10, no special kernels or drivers.

    Comment


    • #42
      Originally posted by tildearrow View Post
      OK, so I watched the video... and I have one big complaint.

      Where is my 60FPS scrolling?
      Are widgets being drawn on the CPU, or is the GPU this weak?
      It doesn't look smooth as a 2019 smartphone. It looks like an early smartphone from the 2000's.
      1. Indeed, GTK3 draws its widgets with CPU. GPU acceleration comes with GTK4, which isn't released yet.
      2. Currently Pixman doesn't even have accelerated codepaths for aarch64. There's already a patch for that being incorporated to PureOS, but the videos were made before that happened.
      3. There's some small glitch somewhere in the kernel which makes everything incorrectly vsynced to 55Hz (the display is 60Hz), leading to tearing even though otherwise it would be perfectly smooth. It will be fixed.
      4. WebKitGTK so far has seen only moderate amount of attention when it comes to tuning it for good performance on mobile. There's still a lot that can be done there.
      5. There's also a lot of low-hanging fruits in compositor (phoc) when it comes to rendering optimization and input latency minimization. It just hasn't been done yet due to other things being higher priority for now

      This phone will become faster over time.
      Last edited by dos1; 29 September 2019, 02:10 PM.

      Comment


      • #43
        Originally posted by dos1 View Post

        1. Indeed, GTK3 draws its widgets with CPU. GPU acceleration comes with GTK4, which isn't released yet.
        Wow. I thought GTK+3 already brought some sort of GPU acceleration but after seeing this I pretty much can say it's similar to Qt 5 in this regard...

        Originally posted by dos1 View Post
        2. Currently Pixman doesn't even have accelerated codepaths for aarch64. There's already a patch for that being incorporated to PureOS, but the videos were made before that happened.
        I would like to see a video of its performance after the patch.

        Originally posted by dos1 View Post
        3. There's some small glitch somewhere in the kernel which makes everything incorrectly vsynced to 55Hz (the display is 60Hz), leading to tearing even though otherwise it would be perfectly smooth. It will be fixed.
        You must be kidding, right? Why can't open-source get fluid video right?
        - KWin uses a freaking timer
        - RetroArch devs set the default rate to 59.95Hz, 0.01Hz higher than the NTSC standard 59.94Hz
        - Compiz also uses a timer
        - mplayer only uses a single thread for playback which pretty much means you'll have to go through constant audio desync/extreme catch-up
        - KDE still draws some of its animations in 30Hz! And I have not figured out how to change that rate.

        Originally posted by dos1 View Post
        4. WebKitGTK so far has seen only moderate amount of attention when it comes to tuning it for good performance on mobile. There's still a lot that can be done there.
        I see.

        Originally posted by dos1 View Post
        5. There's also a lot of low-hanging fruits in compositor (phoc) when it comes to rendering optimization and input latency minimization. It just hasn't been done yet due to other things being higher priority for now
        They need to raise the priority of performance improvements as doing these may improve battery life.

        Originally posted by dos1 View Post
        This phone will become faster over time.
        I know.

        Comment


        • #44
          Originally posted by tildearrow View Post

          Wow. I thought GTK+3 already brought some sort of GPU acceleration but after seeing this I pretty much can say it's similar to Qt 5 in this regard...



          I would like to see a video of its performance after the patch.



          You must be kidding, right? Why can't open-source get fluid video right?
          - KWin uses a freaking timer
          - RetroArch devs set the default rate to 59.95Hz, 0.01Hz higher than the NTSC standard 59.94Hz
          - Compiz also uses a timer
          - mplayer only uses a single thread for playback which pretty much means you'll have to go through constant audio desync/extreme catch-up
          - KDE still draws some of its animations in 30Hz! And I have not figured out how to change that rate.



          I see.



          They need to raise the priority of performance improvements as doing these may improve battery life.



          I know.
          Good thing we have you and roman working on kwin :P

          Comment


          • #45
            Originally posted by Baguy View Post

            Good thing we have you and roman working on kwin :P
            I have somewhat stagnated due to being very busy with other things but I have to come back to that project now before 5.17.

            Comment

            Working...
            X