I've tried and everything is quiet good. But the sound come dirty. Maybe my local network problem i think. Nice Job. 

Thanks

6 Mart 2013 Çarşamba 22:38:40 UTC+2 tarihinde Punyabrata Ray yazdı:

We have released WebRTC support, sitting behind a flag, as part of the M26 Chrome Beta for Android release.

This is an early release - many things will not work well or at all. There is much work left  and challenges to overcome. Additionally, we have only had a chance to test this on a limited set of devices. So, please bear with us as we work towards enabling WebRTC by default on Chrome for Android.

Our hope is that with this release, developers can begin to see how WebRTC on Chrome for Android will shape up in the coming months, and get a sense of how their WebRTC-enabled websites and web apps will need to evolve for mobile platforms.

To enable WebRTC on Chrome Dev for Android (screenshots below):
1. Type in “chrome://flags” in the omnibox to access the flags
2. Scroll about a third down and enable the "Enable WebRTC" flag
3. You will be asked to relaunch the browser at the bottom of the page in order for the flag to take effect.

Known issues:
At the time of this posting, Chrome Beta for Android was failing a permissions check on Nexus 7, therefore failing to install on this particular device. This has been addressed and should be pushed out to the Android Play store today or tomorrow.

1. Audio sounds choppy and warbled especially on devices where the CPU is heavily loaded
2. Acoustic echo cancellation on mobile platforms is not working well
3. Chroma components received from the Galaxy S3 camera drivers are swapped (colors look inverted)
4. DTLS via OpenSSL on Android fails and needs to be disabled
5. General stability and complexity issues

Tips on making calls with AppRTC on Chrome Beta for Android:
1. To disable DTLS (see known issue #4), please add “compat=false” to the AppRTC link (ex: https://apprtc.appspot.com/?r=<roomname>&compat=false)
2. The default resolution used by AppRTC is 640x480, which is too complex for certain mobile devices. Therefore if you notice a low frame rate or a loaded CPU, we recommend using the "maxre" parameter to set the call to a lower resolution, such as 320x240 (ex: https://apprtc.appspot.com/?r=<roomname>&compat=false&maxre=320x240)
3. To debug connection issues, you can always try a call in loopback mode. (ex. https://apprtc.appspot.com/?debug=loopback&compat=false&maxre=320x240)

3 Screenshots:

1. Enabling the WebRTC flag in chrome://flags

2. Accepting camera and mic permissions

3. Loopback call

Thank you.

Ray on behalf of the WebRTC team.

--

 
---
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.
 
 

--

 
---
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.
 
 

--

 
---
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.
 
 

Hi,

This work great ! Thanks for the update. By the way, does this version allow us to select the camera (for example, switching to the back camera on a S3) ?

On Thursday, March 7, 2013 2:26:06 PM UTC+1, Warren McDonald wrote:

We have also tested our new WebRTC web app and the code proven on desktop runs very nicely without any modifications on Android, even on the first beta. We have  a presentation to an important audience later today, and this news will add to the impact :)

Warren  

On Thu, Mar 7, 2013 at 7:09 AM, Philipp Hancke <philipp...@googlemail.com> wrote:

> To disable DTLS (see known issue #4), please add “compat=false” to the AppRTC link (ex: https://apprtc.appspot.com/?r=<roomname>&compat=false)

This would be unneccessary if you added a simple navigator.userAgent.indexOf('Android') != -1 check that removes the DtlsSrtpKeyAgreement constraint ;-)

--

 
---
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.
 
 

That wouldn't work because then one side of the call would use DTLS (desktop) and the other side of the call would use SDES (Android). 

 

Of course, the proper fix is to support DTLS on Android, which we are working on right now.

--

 
---
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.
 
 

• I boot up my phone from being turned off.
• I launch Chrome Beta
• I go to chrome://version/ and confirm that under 'Application' it reads 'Chrome Beta 27.0.1453.49'
• I go to chrome://flags/ and the 'Enable WebRTC' section has a white background with the link 'Disable'
• I go to my page and try to create the peer connection, and get the error 'Error: NotSupportedError: DOM Exception 9'

Hello. Is there any changes with camera selection possibilities and color inversion?

On Thursday, March 7, 2013 5:38:25 PM UTC+1, Punyabrata Ray wrote:

No, camera selection is still a bit down the road. 

In addition to reporting issues on this list, it would be helpful to actually create issues in the WebRTC issue tracker. If you are reporting an issue specific to Chrome for Android, I recommend adding "Chrome Android:" in the title/one-line summary. This way it could be easier for others to quickly sort through these issues. 

Thanks,

Ray

On Thu, Mar 7, 2013 at 6:17 AM, Pierrick Grasland <pierrick...@gmail.com> wrote:

Hi,

This work great ! Thanks for the update. By the way, does this version allow us to select the camera (for example, switching to the back camera on a S3) ?

On Thursday, March 7, 2013 2:26:06 PM UTC+1, Warren McDonald wrote:

We have also tested our new WebRTC web app and the code proven on desktop runs very nicely without any modifications on Android, even on the first beta. We have  a presentation to an important audience later today, and this news will add to the impact :)

Warren  

On Mon, Mar 10, 2014 at 7:09 AM, Anders Both <and...@basechat.com> wrote:

Is WebRTC still behind a flag today ?

--

---
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/d/optout.