H264 not working in some Android

1,973 views
Skip to first unread message

Diego Requena González

unread,
Jun 6, 2018, 7:49:23 PM6/6/18
to meetecho-janus
Hi there.

I recently faced a problem with some Android devices. After creating a new videoroom with H264, some devices (including newer ones like Huawei P10) that has H264 codec in the device specs, can join the room but receive an error when trying to subscribe to a publisher. I've been reading that some devices requires a different profile ID in sdp. Even if in a 2 participants room they are both Android, but different manufacturer, and both have H264, the Huawei P10 in this case, still show the error.

Any advice on how to fix it?

Best regards.
D.

Mirko Brankovic

unread,
Jun 7, 2018, 3:10:09 AM6/7/18
to meetecho-janus
but from ndroid, how do you join room, from some mobile browser, or soma js-native  ?

D.

--
You received this message because you are subscribed to the Google Groups "meetecho-janus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meetecho-janus+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Regards,
Mirko

Diego Requena González

unread,
Jun 7, 2018, 3:46:19 AM6/7/18
to meetecho-janus
With Google Chrome


On Thursday, 7 June 2018 09:10:09 UTC+2, Mirko Brankovic wrote:
but from ndroid, how do you join room, from some mobile browser, or soma js-native  ?
On Thu, Jun 7, 2018 at 1:49 AM, Diego Requena González <dagli...@gmail.com> wrote:
Hi there.

I recently faced a problem with some Android devices. After creating a new videoroom with H264, some devices (including newer ones like Huawei P10) that has H264 codec in the device specs, can join the room but receive an error when trying to subscribe to a publisher. I've been reading that some devices requires a different profile ID in sdp. Even if in a 2 participants room they are both Android, but different manufacturer, and both have H264, the Huawei P10 in this case, still show the error.

Any advice on how to fix it?

Best regards.
D.

--
You received this message because you are subscribed to the Google Groups "meetecho-janus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to meetecho-janu...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Regards,
Mirko

Mirko Brankovic

unread,
Jun 7, 2018, 4:08:56 AM6/7/18
to meetecho-janus
If I remember correctly, Chrome supports only h264 - default profile, witch means it should work for Chrome subscriber listening to Chrome publisher, and most likely you will have to mangle the sdp if you want to publish from IOS 

To unsubscribe from this group and stop receiving emails from it, send an email to meetecho-janus+unsubscribe@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Regards,
Mirko

Diego Requena González

unread,
Jun 7, 2018, 4:32:24 AM6/7/18
to meetecho-janus
But when I join a videoroom with a Windows PC using Google Chrome, I get a profile ID different than the Huawei. Also, I have a Nexus 6P and shows a different profile ID than Huawei, but the Nexus is working with PC while the Huawei device cannot subscribe to PC nor Nexus. Atleast should work with Nexus, they both have the same manufacturer! :(

I've found that Chrome supports H264 and it has an internal encoder/decoder. I did not found if it can be forced to use that software encoder/decoder to check if using it can enable a "common" H264 profile ID in the SDP and all devices with Chrome, except iOS, can work together.

To be clearer: when I join into a room with a PC with Google Chrome and with my Nexus 6P, I believe both use profile-level-id=42e01f;
When the Huawei device wants to join to the party, It shows a WebRTC error and looking into the SDP, I believe that uses profile-level-id=42001f;

I can do a test to show you screenshots/logs if required.

D.

Lorenzo Miniero

unread,
Jun 7, 2018, 4:35:07 AM6/7/18
to meetecho-janus
I think this is a question for discuss-webrtc, as IMHO it's quite clearly not Janus related (codec issue).

L.

Diego Requena González

unread,
Jun 7, 2018, 5:18:34 AM6/7/18
to meetecho-janus
Yea, but I wanted to know if you were aware of something related with this. I don't care about Android - iOS, but I care about Android - Android or Android - PC, which will be the 90% of the videorooms.

I've found a recent post that stills open from Chromium group, that says they didn't implemented an H264 encoder/decoder via software.

In fact, I've been testing right now to join these 2 Android devices into an H264 videoroom. From Nexus, I can see the remote video and local video, from Huawei, I can only see local video and listen remote video, but shows the "No video" content inside the video container. This means no videotracks.

If it is a codec related, then I will report it directly to Chromium.

D.

Diego Requena González

unread,
Jun 7, 2018, 5:19:36 AM6/7/18
to meetecho-janus
Sorry, forgot to mention that the encoder/decoder software is not available FOR ANDROID, but for PC.

Alessandro Amirante

unread,
Jun 9, 2018, 7:27:41 AM6/9/18
to Diego Requena González, meetecho-janus
AFAIK h264 on Android is only supported when the device provides an hardware encoder. No software encoder as of yet.

To unsubscribe from this group and stop receiving emails from it, send an email to meetecho-janus+unsubscribe@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages