@Xray2000 Yes it was. I have a problem with my server setup which causes files to be randomly truncated. The file is now fixed and should be 475k (or so) in size.
@Luksus I know why the file gets that large and I still want to look into it (a large amount of that size is a binary file gets hex-printed). Maybe you could compress it and upload it somewhere (if not here)?
@ernest The update is in the xenial_-_gst-droid repo mentioned in the instruction. You should get it automatically via apt.
I've just updated the camera app to fix the issue with the rotation of the front camera. Grab the new binaries at the same link in the first post.
@Luksus Turns out the log doesn't tell much. Please try again, but increase the log level to 5 i.e. GST_DEBUG=5.
@Emphrath Unfortunately this won't go into the next OTA. This still needs some refining for stability and I want to make sure it won't affect the existing ports.
@ziggutas The trouble with video on OP3T (and devices using 64-bit rootfs) is known. However, my only 64-bit device is not working right now and is in the repair shop. And, yes, system image upgrade will wipe this out. I suggested using apt to update the phone. Make sure you have another phone before doing that.
@Luksus Video recording works fine here on my FP2 with an old camera module. Could you please post the log? Follow the instruction above, but replace GST_DEBUG="droidcamsrc:4" to just GST_DEBUG="4".
@Emphrath Well, turns out that patch isn't needed anymore. I'll remove it from the instruction.
@Luksus Does the flash work when taking a picture normally in the camera app?
@Emphrath No. I meant that I've included a (possible) fix in the latest version of lxc-android-config debian package. If you've followed the gst-droid install instruction and upgraded your phone with apt (not system image!), the fix should be installed.
The flash in the camera app does work on my old module (at least, until I burnt it 
). If even that doesn't work on the new module, then I'll probably have to find the new camera modules somewhere. 
Sorry, get occupied with some other stuff. I'll look into the Aethercast problem. However, that's not the top priority.
Although I've never tested the new camera module (I don't have one), I think that the stack should work with both versions. If you have the new modules and care to compile the Halium part from source, I encourage you to try it out.
For the flashlight (via the battery indicator), there's a possible fix available as the latest lxc-android-config package in xenial_-_gst-droid. Again, if you care to compile the Halium part from source, you could try that on the old and the new camera module. However, there's a possibility to burn your flash. So, please make sure you have a spare module before trying it out. I've burnt mine during my fiddling, and I have no spare module, old or new. So, I'll not be able to test it myself.
@pbt100 @tigerpro The wake lag without minimediaservice should be fixed by including this commit into your Halium tree: https://github.com/Halium/android_frameworks_native/pull/6 (And if it works please add some voice to the PR. Thanks!)
@Luksus You've compiled Halium-7.1 image yourself? Also, is it with the old or new camera modules? I don't have new camera modules myself, so I would like to know how that works.
@walidham Hmm, according to my research, android_getCpuFeatures is supposed to be compiled into the binary using it. If you can make it link to libskia.so (which seems to be available on normal Halium installation), then it might work. Also, seem like you'll have to remove libandroid.so too.
@ComLarsic It's hard to revert changes made by lxc-android-config, one of the packages updated. It's cleaner to just re-install Ubuntu Touch. You can do that by using the UBports Installer or by running sudo system-image-cli -b 0 --progress dots from an ADB or SSH session (not in the terminal app though).
What device are you testing with?
@dR0W Ok. It seems like Pulseaudio is unable to enable "voice call mode" on your BT headset for some reason. To help investigate this, please follow this:
echo 'exec pulseaudio --start -vv --log-target=syslog' >~/.config/upstart/pulseaudio.override to enable additional logging on Pulseaudio.initctl stop pulseaudio then initctl start pulseaudio. Note that restarting it won't take the settings above into effect./var/log/syslog. I'm not sure if it contains sensitive information or not, so you can PM me if you want.rm ~/.config/upstart/pulseaudio.overrideAlso, if possible, could you please retry this with the old version of Pulseaudio?
@jezek Accelerometer works as the screen rotates correctly. LED doesn't work, probably due to the permission issue. SensorStatus doesn't show values from the compass, but I'm not sure if it's due to the port or other problem.
@ComLarsic I've updated the instruction to include the arm64 binary and the link to my modification. Thank you for raising that up!
@walidham said in How to: test GStreamer-droid based camera support in Ubuntu Touch (for Halium 7.1 based port):
First note is camera.msm8996 driver can't load without added libjnigraphics.so, libandroid-runtime.so and 17 others blobs files. I extracted them from cm-14.1 rom and added it to my system.img to make driver HAL camera happy and load.
I tried remove dependencies with patchelf but not work (got methods unknown errors).
Notice that libandroid-runtime.so = ART i.e. the Java language runtime. It's unusual for a HAL library to link into it. What method does it say is missing when you tried patchelf it (and what library do you patchelf out)?
Second note :i tested camera with gst-inspect-1.0 got this error
** ERROR:gstamchybris.c:1286:scan_codecs: code should not be reached ** ERROR:gstamchybris.c:1286:scan_codecs: code should not be reached No such element or plugin 'androidmedia'
How did you test camera with gst-inspect-1.0? Do you mean gst-launch-1.0? Also, that error doesn't come from gst-droid.
With droidmedia logcat show me this
ServiceManager: add_service('SurfaceFlinger',9) uid=1000 - ALREADY REGISTERED, OVERRIDE ServiceManager: service 'SurfaceFlinger' died ServiceManager: add_service('media.player',10) uid=1013 - ALREADY REGISTERED, OVERRIDE ServiceManager: service 'media.player' died
Did you also add minimediaservice and minisfservice? It seems like minisfservice conflicts with built in minisf in Mir and minimediaservice conflicts with normal mediaserver. Please remove both of them. If not, then what do you mean by "with droidmedia"?
@Flohack @nanu-c Testing the new camera with GStreamer-droid is highly appreciated. I believe that using 7.1 should solve issues with the new camera modules due to no need for any wrapper.
This is a Halium 7.1 based port for Fairphone 2. The current port is based on Android 5.1 and has quite a few band-aids and workarounds. This port is completely new and isn't based on the current port.
Sources:
Kernel: https://github.com/Halium/android_kernel_fairphone_msm8974/tree/halium-7.1
Device: https://github.com/Halium/android_device_fairphone_FP2/tree/halium-7.1_ubuntu
Manifest: https://github.com/Halium/halium-devices/blob/halium-7.1/manifests/fairphone_FP2.xml (This manifest doesn't point to the Ubuntu Touch additions. Add revision="refs/heads/halium-7.1_ubuntu" to the device tree tag to retrieve them.)
Status:
Install:
No prebuilt image has been made yet. Thus, you're required to build the image from source.
@dR0W Thank you for the information. I see something incorrect in the "in calling" case. However, I'm unable to pin it down yet. Could you please give me the output of pacmd list-cards while in the call?
@walidham Could you please try without camera_service? camera_service comes from libhybris and contains some camera services. However, they're designed for 4.4 devices. The way gstreamer-droid works should not require this service anymore.
Not to be confused with cameraserver. cameraserver is an Android service which splits from mediaserver starting from 7.0 and is required for camera to work.
@walidham Which device are you working on and based on Halium 5.1 or 7.1? IIRC, android.media.IMediaRecorderFactory is something I've seen only in Halium 5.1 port by Canonical's custom patch. In case I recalled it wrong, could you also share the result of ps ax -H too?
@ernest Could you please follow the instruction in "How to debug" and share the result with me? It will produce more debug information that could be useful for me.