What is responsible for UVC USB webcam? SAMSUNG or ANDROID?

[Android Central Question]

I have a few month trying to figure out what is wrong with my J3(6) j320fn mobile because OTG functionality seems to be ok, I can use pendrive, keyboard, mouse. The problem comes with OTG compatible webcamera. It is recognised by all apps but is not showing image (balck screen).

Updates are not available in such matter and SAMSUNG support is .... awesome=0.

I tried custom OS and they are not having this capability either.

After I've been left down by the phone's manufacturer the only thing remains to address the software, not being able to find out what is the problem, with the solely question:

QUESTION: HOW CAN I MAKE THE USB UVC WEBCAM I HAVE TO WROK WITH MY MOBILE I HAVE?

I really hope in a more "at point" answer than I've been used with samsung support.

Thank you.

P.S. I have another issue with an OMIZ BT keyboard but let's go one step at a time.

 

[Rukbat]

1. You need an OTG adapter or cable.

2. Try https://play.google.com/store/apps/details?id=com.svprdga.usbwebcamera&hl=en

(The camera needs a driver, which you can't install in an Android device, so the app has to be written with the webcam API. An app written for older webcams, without UVC, won't work.)

Whose fault is it? I'd put the blame at the feet of the webcam manufacturer. They should have a Windows driver, an Android app and an iPhone app on their site. It's not Samsung's fault, because they didn't develop either the webcam or Android. Android (Google, actually) provides the library that any app developer can use, so it's not their fault. If the camera developer chooses to not write an app you can use on an Android device to run their camera, I'd blame them.

 

[zeeproduction]

Thanks a lot for your detailed and fast answer.

First of all I was not asking the question to find who to blame to but rather to find a solution because I feel a huge frustration in this "wonderful" world we live in inside a maze of programming languages and this is exactly what makes me think that people are more and more underpaid and with huge rush and/or lack of time to peacefully read a question and really understand its correct meaning.

"1. You need an OTG adapter or cable."
I consider this redundant information and a bit of waste of time because I already said "...OTG functionality seems to be ok, I can use pendrive, keyboard, mouse..." and I will add that I connected a USB to UART 323 with an arduino having serial monitor on the phone.

I am unaware if is acceptable a follow up question but I suppose somebody will put me in my place if a do something wrong and I promise I'll do my best to not happen again.

But after I passed the registering filters to be able to do this I must say again that I am really interested in a solution and therefore I will come with more details that could help me to obtain an even more helpful answer. I am completely blank about linux & CO so please have mercy.

I tested the app you mentioned in your answer and I had a white screen. Tested different resolutions and both encoding modes. Nothing.

I connected the camera to windows os laptop and it was recognised and worked flawlessly. After all it is a standard UVC USB webcam. I tested not only this camera but another one that is also UVC compliant and I understand that technically there is no need for a specific driver being a UVC class compliant device. The other camera behaves exactly the same.

Making a diagonal at respect to this matter on Internet I see that this is a known issue and is not only my problem but one of many others. As far I understand is a system node that puts the connected device in the correct USB list or something like this something related to V4L-DVB or V4L2 kernel device driver or alike to correctly enumerate the connected external devices according to many forums talking about this issue in the android OS for mobile phones.

Until now I managed to change the firmware to a custom 7.1 and 6.0 Android OS and tested the camera only with the core and after I added the gapps standard, TV(oops) and lite.

None of the above combinations worked. So please if you can tell me how can I build in a simple manner (if there is one) a pack to burn it on my phone to have the correct configuration to make that camera work. I am sure there has to be a way but it's not going to be me to discover this on my own because I only ha one life and I am in the 50s already.

Just to add up, both cameras plugged on Galaxy S5 worked immediately with the same apps I tested on my phone J3(6) J320FN lollipop 5.1.1 samsung stock firmware. Now I put back the stock ROM hoping to obtain some smart updates from Samsung but very low hopes.

So, after a long story made as short as possible I will rephrase my own question:

How can I make that UVC USB compliant camera (proved and sure thing) to work with my J3(6) phone, whit whatever ROM could be available or patch or module or app or something?

Thank you so much for your precious time.

 

[Rukbat]

"1. You need an OTG adapter or cable."
I consider this redundant information and a bit of waste of time because I already said "...OTG functionality seems to be ok

My error, then. I wasn't sure if you meant that it worked on the phone, or if you meant that you used the cam with an OTG adapter.

I tested the app you mentioned in your answer and I had a white screen. Tested different resolutions and both encoding modes. Nothing.

Then evidently it doesn't include a UVC driver.

I connected the camera to windows os laptop and it was recognised and worked flawlessly. After all it is a standard UVC USB webcam. I tested not only this camera but another one that is also UVC compliant and I understand that technically there is no need for a specific driver being a UVC class compliant device.

Oh, there is, but Windows includes it.

As far I understand is a system node that puts the connected device in the correct USB list or something like this something related to V4L-DVB or V4L2 kernel device driver or alike to correctly enumerate the connected external devices according to many forums talking about this issue in the android OS for mobile phones.

Probably, but that would be a driver running in Linux (the OS in which Android runs).

None of the above combinations worked. So please if you can tell me how can I build in a simple manner (if there is one) a pack to burn it on my phone to have the correct configuration to make that camera work. I am sure there has to be a way but it's not going to be me to discover this on my own because I only ha one life and I am in the 50s already.

Sorry, no. You'd need a Linux driver written to run in an ARM processor, and I haven't seen any. (As for age, I wish I could even remember being 50.)

Just to add up, both cameras plugged on Galaxy S5 worked immediately with the same apps I tested on my phone J3(6) J320FN lollipop 5.1.1 samsung stock firmware.

Then there's evidently a UVC driver in the S5 firmware but not in the J3 firmware.

How can I make that UVC USB compliant camera (proved and sure thing) to work with my J3(6) phone, whit whatever ROM could be available or patch or module or app or something?

I'm afraid I don't have an answer - someone would have to run a full debug through the J3 to see where the video signal gets lost, then write a driver for the camera.

Thank you so much for your precious time.

Oh, it's not that precious. Being retired and living alone gives one a lot of it. But you're welcome (for whatever information I was able to give you).

 

[zeeproduction]

Thank you again for your reply and answers.

Looks like as long as I won't find a ready made solution or a driver that could be included in a ROM image all this gets over my head.

Thanks.