Status Update
No update yet.
Comments
pe...@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
ph...@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"
va...@gmail.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
on...@gmail.com
I was hopeful that the release of API 18 (4.3) would have created a solution to this, unfortunately it includes version 3158130
sh...@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
ph...@chromium.org
same
za...@gmail.com
SAME ! - Google can't do sth working in 100 percent?
za...@gmail.com
same issue - Google Play services out of date. Requires 3159100 but found 3158130
zm...@chromium.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
zm...@chromium.org
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
su...@google.com
Same issue here.
su...@google.com
Same issue here. How can i fix this bug?
zm...@chromium.org
We're working on this. I don't have an ETA yet other than the maddeningly vague "soon".
[Deleted User] <[Deleted User]>
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.
su...@google.com
FYI also getting same with PlusClient sign in, so this is not just a maps issue:
ConnectionResult.SERVICE_VERSION_UPDATE_REQUIRED
07-30 12:35:50.059: W/GooglePlayServicesUtil(16054): Google Play services out of date. Requires 3159100 but found 1013
ConnectionResult.SERVICE_VERSION_UPDATE_REQUIRED
07-30 12:35:50.059: W/GooglePlayServicesUtil(16054): Google Play services out of date. Requires 3159100 but found 1013
on...@gmail.com
Same page here!
07-31 22:47:40.277: W/GooglePlayServicesUtil(1009): Google Play services out of date. Requires 3159100 but found 3158130
Thing is: we work under timelines too, and we need this fix quick! I cannot go wondering around asking for cellphones all over the place... I used to have this fixed with my emulators!!
07-31 22:47:40.277: W/GooglePlayServicesUtil(1009): Google Play services out of date. Requires 3159100 but found 3158130
Thing is: we work under timelines too, and we need this fix quick! I cannot go wondering around asking for cellphones all over the place... I used to have this fixed with my emulators!!
al...@nvidia.com
[Deleted User] <[Deleted User]>
The Play Services team knows about this issue and is working on it with a high priority. The fix for this will go in the same emulator image in the same timeframe. Sorry I'm being vague about when it'll go out; I don't want to tell you something and then have us miss it. I'll update this bug when I know more.
[Deleted User] <[Deleted User]>
Just would like to add that we are experiencing this on device as well, not just in AVD. Not sure if that matters...
za...@gmail.com
Any ETA on this fix? Appreciate your reply.
ra...@microsoft.com
There's no ETA yet. I think a new version of the Google Play Services add-on in the SDK manager is going out today, but this doesn't help the issue of needing to update the emulator system images.
on...@gmail.com
Any update on this?
Any chance you could put a note in the tutorial/setup documentation as it is infuriating (not to mention a waste of time) to follow steps exactly as described and not get something working. Resorting to Stack Overflow to find a load of hacks (and a lot of incorrect answers) for manually installing the required .apks and finally a link here to see that the issue is at least 3 weeks old with no target fix date.
Any chance you could put a note in the tutorial/setup documentation as it is infuriating (not to mention a waste of time) to follow steps exactly as described and not get something working. Resorting to Stack Overflow to find a load of hacks (and a lot of incorrect answers) for manually installing the required .apks and finally a link here to see that the issue is at least 3 weeks old with no target fix date.
on...@gmail.com
I agree, please update the documentation while it is not working.
ra...@microsoft.com
Agreed on updating the documentation. I wasted two days on this issue and it pains me to see it repeated Ad nauseam.
on...@gmail.com
I lost hours on this problem thinking it was my fault.
Is ridiculous that a company like google do shit like that.
Is ridiculous that a company like google do shit like that.
af...@chromium.org
This should go out today.
su...@google.com
@howardb Thank Jah!
on...@gmail.com
I just updated Android in Eclipse via the SDK Manager. The first launch of my previously working application on the emulator (using Google APIs - API Level 17) generated the following error:.
GooglePlayServicesUtil(1105): Google Play services out of date. Requires 3159100 but found 3136130
Only using a new Emulator (using Google APIs - API Level 18) does the application run.
Will the older API Level 17 be updated with a new Google Play services?
GooglePlayServicesUtil(1105): Google Play services out of date. Requires 3159100 but found 3136130
Only using a new Emulator (using Google APIs - API Level 18) does the application run.
Will the older API Level 17 be updated with a new Google Play services?
zm...@google.com
Sorry, we're only committing to keeping the latest API up-to-date.
is...@google.com
How to fix this?
Google Play services out of date. Requires 3225100 but found 3136130
Google Play services out of date. Requires 3225100 but found 3136130
Description
Steps to reproduce the problem:
1. Utilized two monitors as an extended desktop
2. Open a Chromium window on the 2nd monitor and browse to content which can be displayed full screen (picture lightbox, YouTube video, etc)
3.Activate the full screen mode of the content. The window goes haywire after a few seconds
What is the expected behavior?
The content (picture, video, etc) displays normally without going haywire
What went wrong?
This is a problem specific to Chromium. I can reproduce it consistently in Chrome, Brave and Chromium-based Microsoft Edge. It never happens with Firefox and it never happens with EdgeHTML-based Edge. It has been happening for quite a while now (months, at least). I've hoped somehow the problem would surface and get enough attention to get fixed and have been using Firefox in the meantime but evidently many people aren't having this problem.
It occurs with hardware acceleration enabled, only. If I disable hardware acceleration full screen seems to work fine (but taxes my CPU since my fans accelerate when I go full screen) Basically anything which has a full screen mode (such as viewing photos on portfolio websites with a lightbox mode or watching videos like YouTube will result in this issue occuring. I've included screenshots showing how my 2nd monitor is initially fine with going full screen on a YouTube video, then what happens a few seconds later. I've also included a Windows Crash report from the event occuring. It's via Chromium-based Edge but again, the same thing happens consistently regardless of which Chromium browser I use. Since the issue doesn't occur with Firefox on the exact same setup and with consideration of it evidently being related to the use of hardware acceleration, I'm more suspicious of the issue being with Chromium rather than my GPU driver.
Did this work before? Yes I don't remember. It has been several months since this stopped working. I figured it would've been realized and fixed by now.
Chrome version: 80.0.3956.0 Channel: stable
OS Version: 10.0
Flash Version:
I'm running two NVIDIA GeForce RTX 2080 Ti in SLI. My primary monitor is an HDR and G-Sync-enabled monitor and full screen always works on that on that monitor. My secondary monitor is also G-sync-enabled but is not HDR-capable. The issue occurs exclusively on the secondary monitor (you can see the effect in the attached screenshots). There was definitely a time when this worked. I've used Chrome and Brave in the past with videos playing fullscreen on both monitors without issue on this very setup. Sometime on the order of months ago this started occurring. When it does occur, the only way to get the monitor to return to normal (even if I close the browser) is to temporarily change the resolution (and if Chromium is still in full screen mode it'll just go hwywire again after a few seconds) or restart my computer.
Let me know if you need any additional information.