New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 628956 link

Starred by 11 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Feb 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

can't reach Play on Pixel LS when re-enabling Android apps

Reported by henry.sc...@gmail.com, Jul 18 2016

Issue description

Version 53.0.2785.15 dev (64-bit)
Platform 8530.13.0 (Official Build) dev-channel samus
ARC Version 3050391
Firmware Google_Samus.6300.174.0

Repro steps:
- Go to settings, click "Enable Android Apps"
- On popup, click "Agree"
- On welcome screen, click "Sign In"

Results:
- "This may take up to a minute or so."
- "Couldn't reach Google Play. Try again now."

Trying again doesn't matter, tried disabling/enabling Android and restarting.

Finally, some context to note. I did successfully enable Android Apps previously, but after installing a few I ran out of space so I disabled Android apps. Now the space issue is under control and the problem is occurring now that I am attempting to re-enable Android apps.
 
Labels: OS-Chrome
Components: -UI>Settings Platform>ARC
Labels: -Proj-MaterialDesign-WebUI

Comment 3 by uekawa@chromium.org, Jul 19 2016

can you please file feedback report (alt-shift-I) ?

There might be some stale files left over from previous run (although disabling Android apps should remove them), you might want to try recreating your profile as a last resort.

Comment 4 by uekawa@chromium.org, Jul 19 2016

Cc: uekawa@chromium.org
I sent a feedback report, referencing this issue number.

Is it possible to recreate the profile without powerwashing? Or are the Android files in a nice and tidy directory that I can delete from the shell?
Cc: dspaid@chromium.org hashimoto@chromium.org nya@chromium.org
You can remove the user and add the user back (unless that user is the only user).

By the way, 8530.13.0 53.0.2785.15 dev is the initial public version that got out, why are you using such an old version?
We had 3 updates since then.


Well, by now I'm on 53.0.2785.36; the problem has persisted. I'll try refreshing the profile.
I posted about this issue or closely related issue in the wrong area, but this is a better place.

What steps will reproduce the problem?
(1) Switch to Beta or Dev channel, powerwash, restart
(2) Enable (if not already enabled) and Open Play store app
(3) Sign in

What is the expected output?
The Play store

What do you see instead?
Error: GMS services are not available

Please provide any additional information below.
So this issue is still happening GSM services unavailable. Here's the TL;DR:

This is some wifi issue with Android apps. If I connect to a hotspot from my Fi phone, Play store and Android apps see wifi, but with my home router, no. Chrome OS has no trouble, just Android. Now here are the details:

I have a Netgear 7550 router (said it was Linksys in the feedback, oops) provided by Frontier communications connecting to their DSL internet service. It supports 802.11b/g/n. My Chromebook has no problem with it but Play store can't connect.

I've tried everything, Powerwashing, Beta channel, Dev channel, restart the router many times, limited router to wifi channels 1, 6, 11, reset to all, limited to 802.11b, g and n, reset to all, powerwashing and changes channel for each. My router has no parental controls options. I had Google DNS, but deleted those, removed all port forwarding (just had Skype and VNC). Learned about different settings Frameburst, various intervals, played with them, no change set back to defaults.

Chrome OS is fine with any variation of wifi, on stable, beta and dev channels, but Play store won't load. Play store and Android apps only see wifi when I connect to my phone's hotspot.

Any suggestions would be greatly appreciated. There are a few Android apps that are essential to my work and then I could move almost entirely to my Chromebook.

I've sent feedback with a screen shot on Sep 2nd. I updated to 54.0.2840.13 dev a few minutes ago and see the issue persists, so I'll send another feedback in a moment with a referesnce to this bug report.
I have the same problem on a Pixel LS, I have sent the report too. 

For me it always shows 'GMS Services are Unavailable' independently from being on an Hotspot or home Wifi connection. 

Version 53.0.2785.103 beta (64-bit)
Platform 8530.81.0 (Official Build) beta-channel samus
ARC Version 3251841
Firmware Google_Samus.6300.174.0
So the issue seems to be corrected for me. I hope you all have the same experience. There was no update, but I tried something then powered off and back on and it worked. I don't know if what I did made the difference, but it's worth a try if you are having this error and your Chromebook seems to connect to wifi when not using Android.

I was digging around in the Android preferences and found GMS services and was able to shut it down. You can find it by going to Chrome OS settings, scroll down to the part about enabling the Play store and click the link for Android preferences. Then click Apps, click the 3 dots at the top, choose show system and then stop the GMS system apps. Power off and on and try it again.

As I said, this may be a coincidence, nothing to do with stopping GMS and restarting the Chromebook, but I don't have a way to test it again now that it is working.

Comment 12 by gken...@gmail.com, Jan 22 2017

I am having the same problem with my ASUS C302 Flip 2. Android will not work when connected to my home network but if I connect to a open wifi hotspot it will connect. But then I can't use some of the apps I want becasue I need to be on my home network for them to work....example Roku and AV Controller need to be on my home network for them to work. If I stay on the open wifi hotspot it does me no good. I tried what the above user suggested but I can't find the GMS system apps to stop under Android preferences/Apps/System...I love my new chromebook but I have had nothing but problems when trying to activate Android apps on the beta channel. Sometimes it will just restart my chromebook for no reason. I'm using Chrome version 56 beta. I would love to know how other people are using Android apps with no issues on their Chromebooks.
My android preferences wont work.  Its highlighted to click but nothing happens.  This is an acer 13.3 that was supposed to have the right from the box.
I was able to fix this issue. I was receiving the "GMS Services are unavailable" error when trying to launch the Play Store. I have the Asus Chromebook Flip C302. I actually had this problem on my home wifi. Not a school or work. 

Earlier today I took it to Starbucks just to see if I could get it to work on their wifi. I had no issues there. While I was there I downloaded some apps first and then took it home. After I got home, I discovered apps that needed to connect to the internet for whatever reason didn't work. I also wasn't able to connect back to the Play Store. At that point I thought it was either having a problem with my wifi network itself or my Chromebook was having a problem with something settings related. Here's what I did.

1) This step may not be needed because I didn't make any changes to my router. I checked my firewall settings and it was already set to allow all traffic (since it seems like most people think that they're having a block related issue). I switched it to the "maximum security setting", but then switched it right back to the "no security" setting.

2) I disconnected from my wifi. I just went to my wifi connection in settings and clicked on disconnect.

3) I went to my wifi settings and selected my connection to look at the settings. I checked the box next to "Prefer this network". It's right above "automatically connect to this network". I then reconnected to my wifi.

After I made the 3rd change, I was able to open the Play Store and it instantly connected. My apps were working too that required any sort of network access. I restarted just to see if it would stick and everything is still working. I find it odd that simply "preferring my network" was enough to fix this, but then again... it's still in beta.
Cc: abhishekbh@chromium.org
Status: WontFix (was: Unconfirmed)
We have fixed a number of startup failures in version 56, I'd invite folks earlier in this bug to try again.  Closing this bug obsolete (which was about this failure on Pixel LS) for now because it's a very old bug and is likely resolved.  If this original problem persists, open a new bug.

The latest failures sound like they are network config related.  Right now we have problems if the local network is configured to the 192.168.254.0/24 subnet.  We're working on a change to fix this, but it's being tracked internally ATM.

Sign in to add a comment