How to: test GStreamer-droid based camera support in Ubuntu Touch (for Halium 7.1 based port)

  • This post is deleted!

  • @Flohack Hello, i have already connected via USB cable and then i run what you send me but when i put the password it doesn t work, i get a message. Screenshot from 2020-08-04 23-20-18.png

  • Hello @Stef7773 see the documentation about how to enable SSH access on your phone:

  • @Fla Hello, thank you. But i still having problems. this time:
    ~$ ssh phablet@
    ssh: connect to host port 22: Connection refused

    But i check it and everything seems right: ssh service is up etc...
    Why i have a Connection refused ?

  • @Stef7773 add -v to the ssh command to make it verbose and be able to debug. Also, we're pretty off-topic there, maybe you want to join the Telegram group to have real time support and not pollute that topic?

  • Getting this while trying to open camera on Kagura:

  • @konradybcio said in How to: test GStreamer-droid based camera support in Ubuntu Touch (for Halium 7.1 based port):

    Getting this while trying to open camera on Kagura:

    Same output for me on Kagura. Camera loads but all black.

  • Just out of curiosity; what is keeping the xenial_-_gst-droid from being merged for the OnePlus 3T images?

    Because the camera app on the 3T is completely broken. It can't take pictures and it can't record videos. But in order to have that working, one has to give up system-image updates, which is also not desirable.

    There's only an edge channel for the 3T anyway, so it would make sense to me to just merge this at least for that channel.

    For reference, it has also been merged for the PinePhone's development channel. The stock camera app still worked there, although the gstdroid version linked in the OP works better. But on the 3T currently nothing works, other than taking screenshots of the viewfinder.

  • The OnePlus 3(T), among other aarch64 devices, now has an RC channel. After switching to it and re-installing xenial_-_gst-droid with ubports-qa, I found that the camera wasn't working, even though I was still using the 3.1.3+gstdroid Camera app. It just showed the blue spinner infinitely like what happens without using gst-droid.

    After reverting to the Development channel and installing xenial_-_gst-droid again, I was able to take pictures like before.

    The RC channel only seems to be a couple of days behind on Development. Why isn't it possible to use this branch on RC?

    I also read that @Flohack said elsewhere that gst-droid will not be merged in OTA-13, which would be the first stable image for the OnePlus 3(T). If gst-droid doesn't work on RC and then probably also not on Stable, does that mean I have to keep using the Development channel for the next months?

    Like I posted a couple of weeks ago: why don't we merge this branch at least for the devices that have zero working camera support without gst-droid? The OnePlus 3T can't even take pictures on the stock RC, Development and edge images, which is quite limiting.

    When I look at /etc/apt/sources.list.d/ubports.list on my PinePhone, I see the following:

    deb xenial main
    deb xenial_-_edge main
    deb xenial_-_edge_-_pine main
    deb xenial_-_edge_-_wayland main

    This is because the PinePhone needs those branches to function, even though they're not stable and not suitable for all other devices.

    On the 3T it's only

    deb xenial main

    If we'd add

    deb xenial_-_gst-droid main

    on the image overlay, the images could probably just be built with gst-droid support integrated. It's not like we have much to lose on the 3T. Without it the camera doesn't work at all. This is likely true for other Halium 7.1 / aarch64 devices as well.

    I understand that gst-droid may cause regressions on older devices, but now we're shipping images with broken basic functionality for newer devices - that people are more likely to use in the current day - to avoid breaking the older ones. That doesn't seem right to me.

  • @peat_psuwit can you elaborate a bit? Thx!

  • By the way you could install the branch on RC or stable as well, did you try it?

  • @Flohack I tried it on RC and it did not work. It installed, but the camera app didn't take pictures. It just showed the spinner and got stuck.

    That is also what happens without gst-droid.

    There are no Stable images yet for the OnePlus 3T. See here.

    But am I correct that OTA-13 is expected to be the first stable image for all the phones here? I can't speak for all of them, but I do have two OnePlus 3T's, and without gst-droid the camera does not work at all. Not for pictures and not for videos.

    We'd be shipping a "Stable" release with a completely broken basic functionality - the ability to take pictures - without adding the gst-droid branch to at least the op3t images.

  • With the delays on OTA-13, can this maybe be included after all on the OnePlus3/3T image by default?
    Since the images are device specific I don't see any disadvantage on enabling this on these devices like @kkeijzer was already saying, or am I missing something?

  • @poVoq The problem is we only have one common rootfs, so this would need to be added specifically for only one device or 2. We can have a discussion about it how this can be solved, but no ETA on it, sorry.

  • out of curiosity, does this have any effect on the devices that are already supported?

  • @tigerpro yes, unfortunately we had some regressions with that, thats one of the reasons it takes so long to get into the main rootfs.

  • @peat_psuwit said in How to: test GStreamer-droid based camera support in Ubuntu Touch (for Halium 7.1 based port):

    UPDATED: If you're running arm64 image, please also run apt install gstreamer1.0-droid nemo-qtmultimedia-plugins.

    This seems to be unnecessary as of OTA-13.
    I have installed this on my OnePlus3 and it seems to be working fine for photos.
    Only that the orientation of the photo seems to be always stuck in landscape instead of how the picture was actually taken is a bit annoying.
    Trying to record a video crashes the app, but that was expected according to the OnePlus3 device page.

  • @poVoq Yes this is unnecessary meanwhile @peat_psuwit can you take out this sentence for arm64 devices in the first post? Thx!

Log in to reply