nexus 5 not stable



  • @nexus5
    When switching from photo to video there is a little issue. You just have to swipe from left (like if you wanted to switch apps), wait a couple of seconds (when the snap from the camera app turns black), then you can switch back to the camera app.

    And as @Alter mentioned the hadware acceleration is responsible for the behavior with high quality video streaming.

    The Nexus5 is fairly stable, I'd like to remember that this is maintained by a small group of people who did an amazing job with the little ressources available.
    So I encourage people to contribute how they can to improve everybody's experience with UT.



  • @nexus5

    Please do it more stable. It's awesome, analog android! Now I see only two os, which can be analog android. It's Ubuntu and sailfish, but all two not stable:(

    So you can contribute to make it better, more stable 😉
    For me N5 is one of the most stable, so everything depends of what you expect.



  • @Alter said in nexus 5 not stable:

    I guess this will also improve web video.

    It will not. The browser engine is currently unable to use hardware acceleration for decoding or rendering. Halium 7.1 doesn't change that.



  • Guys, I mean stable channel have a lot of issues. Today I tested pre release ota 13. Have some minor issues. Good job mainters!



  • @dobey Sorry, I didn't know that.
    Is there currently anyone working on the browser engine so it can make use of hardware acceleration?



  • @Alter said in nexus 5 not stable:

    @dobey Sorry, I didn't know that.
    Is there currently anyone working on the browser engine so it can make use of hardware acceleration?

    This has been asked a few times before. But the tl;dr is no, as it only works with Wayland and not the current old Mir backend used in Halium based devices. On the PinePhone it works already as it uses the new Mir on Wayland instead. Hard to say if and when Mir on Wayland will reach Halium based devices.



  • @poVoq
    Okay, thanks for the answer!



  • @poVoq It really has nothing to do with Wayland. On Pinephone, it's standard upstream Linux with open source drivers, and Chromium can thus actually access the hardware. On Android based devices, Chromium does not support using libhybris on Linux to access hardware, and so it cannot access the hardware.

    Also, I think it only gets GPU acceleration for rendering when doing so, not necessarily for decoding, so even on Pinephone where GPU accel may work, it might still lag behind other platforms in terms of video encoding/decoding performance.



  • @dobey said in nexus 5 not stable:

    @poVoq It really has nothing to do with Wayland. On Pinephone, it's standard upstream Linux with open source drivers, and Chromium can thus actually access the hardware. On Android based devices, Chromium does not support using libhybris on Linux to access hardware, and so it cannot access the hardware.

    Also, I think it only gets GPU acceleration for rendering when doing so, not necessarily for decoding, so even on Pinephone where GPU accel may work, it might still lag behind other platforms in terms of video encoding/decoding performance.

    Odd, I asked the same question previously on an official Q&A and the answer was that qtwebengine has GPU acceleration only implemented for Wayland and the reason it works on the Pinephone is that it is already using Wayland...



  • @poVoq It has nothing to do with Wayland really. Chromium simply just cannot access the GPU on Android based devices, from the GNU/Linux side, because it doesn't use libhybris.