chrome beta android up to M27

188 views
Skip to first unread message

Alexandre GOUAILLARD

unread,
Apr 11, 2013, 1:33:11 AM4/11/13
to discuss...@googlegroups.com
shall we expect any webrtc-related changes in this new beta?

Punyabrata Ray

unread,
Apr 12, 2013, 2:01:20 AM4/12/13
to discuss...@googlegroups.com
Hi,

No major announcements, however, here are some things that we have fixed in the past few weeks:
1. Neon detection was failing on some mobile devices - fixed
2. Our acoustic echo suppressor was failing on wideband codecs - fixed
3. Audio buffer overflow in our audio pipeline - fixed
4. Use the MODE_IN_COMMUNICATION for WebRTC voice calls set by SetMode - partially fixed (this might still be failing on some Samsung phones that we are investigating)

Thanks,
Ray

Alexandre GOUAILLARD

unread,
Apr 12, 2013, 2:43:01 AM4/12/13
to discuss...@googlegroups.com
thanks.


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

Bryan

unread,
Apr 12, 2013, 12:28:05 PM4/12/13
to discuss...@googlegroups.com
Does the iOS version also have webrtc available behind a flag?  (I don't have an iDevice)

PhistucK

unread,
Apr 12, 2013, 12:29:23 PM4/12/13
to WebRTC-discuss
No. WebRTC is not supported in the WebKit version of Mobile Safari and Chrome uses that WebKit on iOS.


PhistucK


On Fri, Apr 12, 2013 at 7:28 PM, Bryan <bryand...@gmail.com> wrote:
Does the iOS version also have webrtc available behind a flag?  (I don't have an iDevice)

--

Bryan

unread,
Apr 12, 2013, 12:37:53 PM4/12/13
to discuss...@googlegroups.com
I guess it is no surprise that Apple does not include native support.  I assumed there was some way for the browser to extend baseline support through native code and polyfills.  It will be a happy day if 3rd party browsers can ever use their own engines on iOS.


PhistucK

unread,
Apr 12, 2013, 12:38:37 PM4/12/13
to WebRTC-discuss
Indeed. :(


PhistucK


On Fri, Apr 12, 2013 at 7:37 PM, Bryan <bryand...@gmail.com> wrote:
I guess it is no surprise that Apple does not include native support.  I assumed there was some way for the browser to extend baseline support through native code and polyfills.  It will be a happy day if 3rd party browsers can ever use their own engines on iOS.

Justin Uberti

unread,
Apr 13, 2013, 12:45:46 AM4/13/13
to discuss-webrtc
The previously mentioned WebRTC improvements for desktop M27 are also present in the Android version.


--

Shachar

unread,
Apr 14, 2013, 3:20:52 AM4/14/13
to discuss...@googlegroups.com
There is no datachannel though...?

Vikas

unread,
Apr 15, 2013, 2:06:09 PM4/15/13
to discuss-webrtc
I think datachannel should work fine on android, i tested on M28 dev
but i think should be working on M27 as well. You can test the demo
below :-
webrtc-demos.appspot.com/html/dc1.html

/Vikas

On Apr 14, 12:20 am, Shachar <shach...@gmail.com> wrote:
> There is no datachannel though...?
>
>
>
>
>
>
>
> On Saturday, April 13, 2013 7:45:46 AM UTC+3, Justin Uberti wrote:
>
> > The previously mentioned WebRTC improvements for desktop M27 are also
> > present in the Android version.
>
> > On Thu, Apr 11, 2013 at 11:01 PM, Punyabrata Ray <punya...@webrtc.org<javascript:>
> > > wrote:
>
> >> Hi,
>
> >> No major announcements, however, here are some things that we have fixed
> >> in the past few weeks:
> >>  1. Neon detection was failing on some mobile devices - fixed
> >> 2. Our acoustic echo suppressor was failing on wideband codecs - fixed
> >> 3. Audio buffer overflow in our audio pipeline - fixed
> >> 4. Use the MODE_IN_COMMUNICATION for WebRTC voice calls set by SetMode<http://developer.android.com/reference/android/media/AudioManager.htm...)> -
> >> partially fixed (this might still be failing on some Samsung phones that we
> >> are investigating)
>
> >> Thanks,
> >> Ray
>
> >> On Wednesday, April 10, 2013 10:33:11 PM UTC-7, Alexandre GOUAILLARD
> >> wrote:
>
> >>> shall we expect any webrtc-related changes in this new beta?
>
> >>  --
>
> >> ---
> >> You received this message because you are subscribed to the Google Groups
> >> "discuss-webrtc" group.
> >> To unsubscribe from this group and stop receiving emails from it, send an
> >> email to discuss-webrt...@googlegroups.com <javascript:>.
> >> For more options, visithttps://groups.google.com/groups/opt_out.

Shachar

unread,
Apr 16, 2013, 3:28:35 PM4/16/13
to discuss...@googlegroups.com
That demo doesn't work on my chrome beta - 27.0.1453.49; Android 4.2.2; Galaxy nexus

Vikas

unread,
Apr 16, 2013, 6:52:19 PM4/16/13
to discuss-webrtc
Hi,

I tested on nexus 4 (Android 4.2.2) with the data channel demo on
chrome 28 dev & it worked fine. Can you try with chrome 28 dev? I have
not got a chance to test with M27 but will let you know, i think it
should work fine.

/Vikas

Shachar

unread,
Apr 17, 2013, 3:22:16 AM4/17/13
to discuss...@googlegroups.com
can't find the dev channel on the play store, you have a link?

Shachar

unread,
Apr 17, 2013, 3:57:34 AM4/17/13
to discuss...@googlegroups.com

Punyabrata Ray

unread,
Apr 17, 2013, 4:27:51 AM4/17/13
to discuss...@googlegroups.com
Sorry, I believe the dev channel Vikas is referring to is an internal build. We will test with the Chrome Beta M27 and get back to you guys.

Sincerely,
Ray


--
 
---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.

Shachar

unread,
Apr 18, 2013, 9:23:21 AM4/18/13
to discuss...@googlegroups.com
my bad, it works (webrtc is under a flag in M27 on android).
in M28 it won't be under a flag?
Reply all
Reply to author
Forward
0 new messages