Status Update
No update yet.
Comments
sa...@chromium.org
I notice the same issue and LogCat shows the following message:
Google Play services out of date. Requires 3159100 but found 3136130
Google Play services out of date. Requires 3159100 but found 3136130
sa...@chromium.org
Same here.
"Google Play services out of date. Requires 3159100 but found 3136130"
"Google Play services out of date. Requires 3159100 but found 3136130"
ja...@goubiq.com
me as well....
Google Play services out of date. Requires 3159100 but found 3136130
Google Play services out of date. Requires 3159100 but found 3136130
[Deleted User] <[Deleted User]>
I was hopeful that the release of API 18 (4.3) would have created a solution to this, unfortunately it includes version 3158130
sa...@chromium.org
Having the same issue:
07-25 00:03:54.998: W/GooglePlayServicesUtil(27293): Google Play services out of date. Requires 3159100 but found 3158130
07-25 00:03:54.998: W/GooglePlayServicesUtil(27293): Google Play services out of date. Requires 3159100 but found 3158130
sw...@chromium.org
same
sw...@chromium.org
SAME ! - Google can't do sth working in 100 percent?
hb...@chromium.org
same issue - Google Play services out of date. Requires 3159100 but found 3158130
ht...@webrtc.org
Having the same issure:
07-26 03:14:00.731: W/GooglePlayServicesUtil(2566): Google Play services out of date. Requires 3159100 but found 3136130
07-26 03:14:00.731: W/GooglePlayServicesUtil(2566): Google Play services out of date. Requires 3159100 but found 3136130
ja...@goubiq.com
API 18 (4.3) same issue
07-26 03:54:03.303: W/GooglePlayServicesUtil(1207): Google Play services out of date. Requires 3159100 but found 3158130
07-26 03:54:03.303: W/GooglePlayServicesUtil(1207): Google Play services out of date. Requires 3159100 but found 3158130
ja...@goubiq.com
Same issue here.
ph...@google.com
Same issue here. How can i fix this bug?
ph...@chromium.org
We're working on this. I don't have an ETA yet other than the maddeningly vague "soon".
is...@google.com
Thanks for the update @sbarta. It is good that you are keeping us informed. This is a very critical and blocking bug for anyone developing with maps.
Description
Steps to reproduce the problem:
1. use getDisplayMedia to capture screen with default constraints (i.e. frameRate: 30)
2. set the SDP to use VP9 codec
3. Framerate is locked to ~5FPS
What is the expected behavior?
The same configuration works for Firefox. It also works as expected for getUserMedia with an extension for screen sharing.
When we change the SDP back to use VP8 with getDisplayMedia, it once again works as expected with the frameRate.
What went wrong?
Capabilities: {"aspectRatio":{"max":1600,"min":0.0008680555555555555},"deviceId":"screen:0:0","facingMode":[],"frameRate":{"max":30,"min":0},"height":{"max":900,"min":1},"resizeMode":["none","crop-and-scale"],"width":{"max":1600,"min":1}}
Settings: {"aspectRatio":1.7777777777777777,"deviceId":"screen:0:0","frameRate":30,"height":900,"resizeMode":"crop-and-scale","width":1600,"cursor":"always","displaySurface":"monitor","logicalSurface":true}
This is what the track provides after using the getDisplayMedia to screen share. However, the chrome://webrtc-internals shows
Statistics RTCMediaStreamTrack_sender_3
timestamp 16/03/2020, 14:34:12
trackIdentifier 67e9620c-84ed-41e5-b1fd-1688047d30c1
mediaSourceId RTCVideoSource_3
remoteSource false
ended false
detached false
kind video
frameWidth 1600
frameHeight 900
framesSent 560
[framesSent/s] 5.061322729276205
hugeFramesSent 2
It appears to be an issue with VP9 on Chrome and getDisplayMedia. Please let me know if there is anything else I can provide.
Did this work before? N/A
Does this work in other browsers? Yes
Chrome version: 80.0.3987.132 Channel: stable
OS Version: 10
Flash Version: