Closed LoopIssuer closed 1 year ago
Hey @LoopIssuer , can you share the full, unfiltered logs from logcat
? The underlying reason for the exception will get logged before this exception. And just to confirm, it only happens on Android 9?
Debug.txt verbose.txt I confirm that it is only on Android 9 - tested on 2 phones: Samsung Galaxy S8 and Red mi note 5.
Can you try running only on the CPU?
var configuration = new MLEdgeModel.Configuration();
configuration.computeTarget = MLEdgeModel.ComputeTarget.CPU;
var predictor = await MeetPredictor.Create(configuration);
@olokobayusuf It works on Samsung Galaxy S8. But on Red mi note 5 - still no camera image.
This is log from Red mi note 5, where there is no camera image. I can see this in log: Access denied finding property "vendor.camera.aux.packagelist" and double-checked that camera permission was granted.
This is log from Red mi note 5, where there is no camera image. I can see this in log: Access denied finding property "vendor.camera.aux.packagelist" and double-checked that camera permission was granted.
This seems to be a device-specific issue, from the logs:
W/System.err: java.lang.RuntimeException: Fail to connect to camera service
W/System.err: at android.hardware.Camera.<init>(Camera.java:629)
W/System.err: at android.hardware.Camera.open(Camera.java:451)
W/System.err: at com.unity3d.player.UnityPlayer.nativeRender(Native Method)
W/System.err: at com.unity3d.player.UnityPlayer.access$300(Unknown Source:0)
W/System.err: at com.unity3d.player.UnityPlayer$e$1.handleMessage(Unknown Source:95)
W/System.err: at android.os.Handler.dispatchMessage(Handler.java:102)
W/System.err: at android.os.Looper.loop(Looper.java:201)
Since the original issue is fixed, I'm closing this out.
@olokobayusuf Just one question: by "device-specific issue" you mean: a) this specific device is sth wrong with camera as a hardware b) this device model could have sth wrong with camera as a hardware c) this device model has sth weird with camera, that is stopping to work with NatML
I am asking, because the same device has a camera working in the another Unity apps.
I think it's the specific device you're testing on, not the device model. You could try restarting the device to see if that helps.
Ok, thanks, we will try (device is at our tester only). Really last question - are there any cons of this configuration with MLEdgeModel.ComputeTarget.CPU? Like performance or quality drop? I'm wondering whether to add a condition like if AndroidOs=9.
This change MLEdgeModel.ComputeTarget.CPU
We tested now with restarting on xiaomi - still no camera image.
In the other applications like Meets, Messanger, our application with previous implementation of background cropping (homuler's Mediapipe Unity plugin) - camera is working ok.
Also tested with Huawei P20 Lite Android 9 - camera image is ok.
@LoopIssuer can you open a new issue for the camera issue on the Redmi Note 5?
Hi I am using Natml VideoKit + NatML Meet sample. Only on Android 9 I get an issue (sometimes crash), that there is no camera image. I get this crash stack trace:
I use this code:
Please help I use
"ai.natml.videokit": "0.0.13", "ai.natml.vision.meet": "1.0.6",