Ricoh Theta V webSocket connection Fail

Ricoh Hardware and Software
1

I’m experiencing an issue in Ricoh Theta V.
I’m using wifi in client mode.
When I start the ThetaEnumerator and ThetaCapturer (for webRTC streaming) the Theta Camera emit 4 bips and reset it self. In vysor I see black screen, the camera emit 4 rapid bips, the red light over the camera button is shown and the camera seems shutdown it self. Also Wifi connectivity is turned off.

Could you explain what happens and what can I do to overcome to this developing issue?

Regards

2

I’m going to ask other people at RICOH about this.

Are you using the code base below as a reference?

NOTE: This is for RICOH’s Cloud service, but shows a good representation of WebRTC for this API.
https://api.ricoh/docs/ricoh-cloud-api-reference/live-streaming/

You can start with that code, get it working with the RICOH Cloud, then move to your own implementation.

The other good reference is this:

That’s not webRTC, but is widely used.

3

It seems that the websocket connection fails (web socket is not in local, but remote).
The Web socket is up and running, the same Android app in other device is working.
It is likely when camera is working the internet connecitivty is not reachable.

4

I’m adding other information:
I was developing on 3.10.1 FW version,
now I’ve updated to 3.21.1 FW version but issue is still present

5

As Reference I’m Using the following projects:

for Theta WebRTC:

for AWS Kinesis WebRTC:

At the current stage I’ve a project fully integrated with the both references that work on Android Devices but not on Theta V camera.

6

I also see these intresting logs:

    2020-02-08 20:53:57.850 20780-20780/com.test.thetaplugin.kinesis I/org.webrtc.Logging: WebRtcAudioEffectsExternal: ctor@[name=main, id=1]
2020-02-08 20:53:57.878 20780-20780/com.test.thetaplugin.kinesis W/VideoCapabilities: Unrecognized profile 2130706433 for video/avc
2020-02-08 20:53:57.878 20780-20780/com.test.thetaplugin.kinesis W/VideoCapabilities: Unrecognized profile 2130706434 for video/avc
2020-02-08 20:53:57.887 20780-20780/com.test.thetaplugin.kinesis W/Utils: could not parse long range '175-174'
2020-02-08 20:53:57.892 20780-20780/com.test.thetaplugin.kinesis W/VideoCapabilities: Unrecognized profile 2130706433 for video/avc
2020-02-08 20:53:57.892 20780-20780/com.test.thetaplugin.kinesis W/VideoCapabilities: Unrecognized profile 2130706434 for video/avc
2020-02-08 20:53:57.896 20780-20780/com.test.thetaplugin.kinesis W/VideoCapabilities: Unrecognized profile 2130706433 for video/avc
2020-02-08 20:53:57.896 20780-20780/com.test.thetaplugin.kinesis W/VideoCapabilities: Unrecognized profile 2130706434 for video/avc
2020-02-08 20:53:57.898 20780-20780/com.test.thetaplugin.kinesis W/VideoCapabilities: Unrecognized profile/level 0/3 for video/mpeg2
2020-02-08 20:53:57.905 20780-20780/com.test.thetaplugin.kinesis W/VideoCapabilities: Unrecognized profile/level 0/3 for video/mpeg2
2020-02-08 20:53:57.950 20780-20780/com.test.thetaplugin.kinesis I/VideoCapabilities: Unsupported profile 4 for video/mp4v-es
2020-02-08 20:53:57.957 20780-20780/com.test.thetaplugin.kinesis W/Utils: could not parse long range '175-174'
2020-02-08 20:53:57.958 20780-20780/com.test.thetaplugin.kinesis W/VideoCapabilities: Unrecognized profile 2130706433 for video/avc
2020-02-08 20:53:57.958 20780-20780/com.test.thetaplugin.kinesis W/VideoCapabilities: Unrecognized profile 2130706434 for video/avc
7

Hi,

it seems that when I turn on the camera capability the network is going down.

8

The guy that wrote the webrtc plug-in on ricohapi github repo is @shrhdk on this forum. I’ll send him a note.

Just to confirm, does the webrtc sample plug-in not work as well? That’s the one that producing the ThetaEnumerator and ThetaCapturer errors, right?

9

Hello,

I write down already done tests:

Tried to run as is the aws sample here:

Note: with standard android mobile device (Samsung S7, Note 10) works perfectly.

On theta camera we do two differents kind of tests:

  1. we done some source code modification

    • do cognito login programmatically, without user interaction
    • change Activity type to theta PluginActivity
    • change CameraEnumerator and CameraCapturer to Theta one’s

  2. Run as is the source code mentioned just changing the login, to be programmatically.

The both way fail with timeout on aws websocket.

The other tests that we did is to integrate aws signaling and cognito login to Theta sample code for webRTC, with the same result: aws web socket fail with time out.

This seem not strictly conneted to aws kinesis video streams, but seems camera related.
Could you help us to investigate the problem?

Thank you