🐛 Using pixelFormat="yuv" in Frame Processor crashes on Samsung A53
#1947
Comments
|
Does it work if you don't set |
|
Yes, but MLKit does not work without YUV format. |
|
Does your |
|
If yes, this is an issue I need to investigate and spend time on. I currently have many other things to do |
Stills the same 😢 |
|
It's always Samsung man. I don't know, the stacktrace isn't very precise, I don't have that phone myself so I can't really develop a fix for that.- |
mrousavy
changed the title
pixelFormat="yuv" in Frame Processor crashes on Samsung A53
|
Hey - @danieloprado if you want this fixed please try to figure out what the problem here is:
Also, you can try to replace Maybe that format is just broken, idk. |
|
I've tested on another Samsung model (m52) and it worked, I'll close the issue for now. Thanks! |
|
Wait why are you closing the issue? Doesn't it still crash on the Samsung A53? |
|
I dont know, I dont have this phone anymore so will not able to reproduce. I'm closing just to keep in history and If anyone have this problem can open again. But If tou want I can open it again to keep track of It. |
|
I have a parent with this phone, I'll generate a release build of the new lib version and try to see If it Stills happens. |
|
I have issue on the Samsung A14 |
|
I have the same in Samsun A10,
With pixelFormat Native it works fine, but the frameprocessor plugin cannot read the image and convert to bitmap for example. It worth mentioning, that it's not a but in Samsung, I am currently using this package in android https://github.com/natario1/CameraView with frame processing and it works just fine in all android devices I am using in natario1/CameraView |
|
can you guys check if this patch solves this issue? |
This fixes the crash on my Samsung A53 |
|
Thanks @mrousavy for such an awesome library! On my end it works perfectly w/Zebra devices.. but not with Samsung Galaxy A14 5G (It even reboots when this happens) |
|
I'm encountering this as well on a OnePlus 8T as up-to-date as possible (running on Android 13) using the latest release vision-camera release (3.6.15), the device first shows a black rectangle instead of the camera and then reboots (like @kjimenezdev) after a few seconds. The crash/reboot seems to be triggered by the combination of Here is a couple of logcat before the reboot: https://gist.github.com/mgcrea/677ad9677886c7f67c259dd9b6141238 Looks like this could be the issue: If I remove the https://gist.github.com/mgcrea/c70ced11674827124c26fb1cd8e39c0d Extract of possibly relevant lines: Happy to help if there is anything I can do. |
|
i still have the same problem on my samsung a40 |
how do you implement it on a react native project using this library? @meabed |
|
Testing again using the lastest release, it's working properly, may you can close this issue. |
|
Great, thanks! |
What's happening?
I want to use the frameProcessor with
pixelFormat='yuv'but the app crashes.Bundle output:
Reproduceable Code
Relevant log output
Camera Device
{ "sensorOrientation": "landscape-right", "hardwareLevel": "limited", "maxZoom": 8, "minZoom": 1, "supportsLowLightBoost": true, "neutralZoom": 1, "physicalDevices": [ "wide-angle-camera" ], "supportsFocus": true, "supportsRawCapture": false, "isMultiCam": false, "name": "BACK (0)", "hasFlash": true, "hasTorch": true, "position": "back", "id": "0" }Device
Samsung A53
VisionCamera Version
3.3.1
Can you reproduce this issue in the VisionCamera Example app?
Yes, I can reproduce the same issue in the Example app here
Additional information
The text was updated successfully, but these errors were encountered: