Error: Unable to connect

[GoogleCodeExporter]

Please answer the questions about build version and network, will save
developers a lot of time !

What steps will reproduce the problem?
1. Starting up Chrome to Phone
2. Select account to use. (I only have one.)
3. Press "Next" button to register the phone for Chrome.

What is the expected output? What do you see instead?
I would expect to see something along the lines of the phone being registered 
for the Chrome to Phone features. Instead I get the error message that it's 
"Unable to connect." I do have WiFi running and am able to browse the internet 
via a browser and get Gmail messages.

What version of the android, in Settings -> About phone -> Build number (
ex. FRFxx ) ? If less than FRF50 - see the FAQ.
Android 2.2
Build FRG01B

Is the phone using WiFi or mobile network when problem occurs ? If Wifi,
are you behind a firewall that blocks outgoing connections ?
WiFi and nothing else appears to be blocked by the Firewall so I do not think 
this is the issue.

Can you open "Gmail" application ? Do you see new messages without hitting
'refresh' ?
Yes.
Yes.

Can you open "Talk" application ? Do you see incoming chats ?
No. Will not let me sign in.
(Note: Do not often use this feature so I cannot say if this is "typical" for 
me or not.)

Please provide any additional information below.

Original issue reported on code.google.com by kent7...@gmail.com on 9 Aug 2010 at 1:39

[GoogleCodeExporter]

Same exact issue. Tried with Wifi on and with Wifi off using the verizon 
network.  Refuses to connect to my Google account.  Gmail however works fine.

Original comment by floa...@gmail.com on 11 Aug 2010 at 1:52

[GoogleCodeExporter]

I ended up clearing the cache and doing a full wipe and reinstall of the OS and 
now it's working great.

A rather drastic requirement in order to get it to work I think. Definitely 
seems that something is off, but maybe it's just my phone.

Original comment by kent7...@gmail.com on 11 Aug 2010 at 2:15

[GoogleCodeExporter]

I am having the same problem getting it to connect to my Gmail account. I tried 
it with WiFi and 3G and it just fails to connect. Need a solution since I know 
I'm not a Google Apps account!

Original comment by flamb...@gmail.com on 12 Aug 2010 at 6:35

[GoogleCodeExporter]

I a also having the same problem.  I have both a google account and a google 
apps account and have tried with 3g and wifi, and the result is always the same 
(stuck on "connecting").  This means that the connection process isn't even 
getting far enough to realize that the google apps account is not supported (no 
error message).  I have a first generation Motorola Droid Running 2.2

Original comment by TWentwo...@gmail.com on 13 Aug 2010 at 1:56

[GoogleCodeExporter]

I was having the same issue - I have Froyo 2.2 on a Moto Droid. I installed 
Chrome to Phone on my computer and then on my phone from the Market. I kept 
getting the "Unable to Connect"  error when trying to finish up the install on 
the phone app. 

Tried repeatedly on 3G and wifi both with no luck.

I finally turned my phone off for about 30 seconds, turned it back on and went 
to the Chrome to Phone app. It finished up everything perfectly and now is 
working great. 

Hope that will help somebody else too because I was getting very frustrated 
trying to find a fix.

Original comment by netamtx on 13 Aug 2010 at 6:01

[GoogleCodeExporter]

rebooting my phone also worked for me - evo on 2.2

Original comment by pla...@gmail.com on 13 Aug 2010 at 8:38

[GoogleCodeExporter]

Identical issue. Tried with Wifi on and with Wifi off using the Verizon 
network.  Refuses to connect to my Google account.  Gmail however works fine.

Also tried on different machine with fresh install of Chrome and Chrome to 
Phone extension.  Did not work.

Original comment by MRex21Z@gmail.com on 16 Aug 2010 at 4:02

[GoogleCodeExporter]

MRex21Z, did you try re-booting your phone? That's what eventually worked for 
me.

Original comment by netamtx on 16 Aug 2010 at 4:08

[GoogleCodeExporter]

I understand it's frustrating to get it to work, but it's also frustrating to 
try to reproduce it without enough information. I got an EVO as well, tried it 
on Nexus and Moto Droid - they all work for me. 

Please include more context. Is everyone using the 'official' Froyo builds ? 
Could you include the build number ? If it's a 'rooted' phone - can you include 
a link to the rom/flashing instructions ? 

It also helps to know what is the status of the connection - can you see a web 
page ? Can you open Google Talk and see the status of your friends ? 

Original comment by cos...@google.com on 16 Aug 2010 at 4:56

[GoogleCodeExporter]

I can confirm this. I installed the Chrome extension, then I launched the 
Chrometophone app. The app. continually gave me an unable to connect error, so 
I rebooted the phone and it work perfectly. Thanks.

Original comment by jring...@gmail.com on 18 Aug 2010 at 2:46

[GoogleCodeExporter]

cos, i use the 'official' froyo build, i buy nexus one on google.com/phone 
months ago. the build no. is FRF91. I use 3G in China. I can open gmail, gtalk, 
chrome lite, and get them work.

Original comment by tianxiao...@gmail.com on 19 Aug 2010 at 9:53

[GoogleCodeExporter]

Nothing is impossible @ China.

Original comment by jacke...@gmail.com on 24 Aug 2010 at 3:00

[GoogleCodeExporter]

unable to connect in China  because of  chrometophone.appspot.com  has been 
blocked .
try make your phone accessible with the appspot domain .

Original comment by lvscar on 24 Aug 2010 at 5:01

[GoogleCodeExporter]

Reboot your phone, it fix this issue. Worked on EVO Android 2.2 Iusacell Mex 
under EVDO.

Original comment by ffavel...@gmail.com on 7 Sep 2010 at 4:46

[GoogleCodeExporter]

Hi,
 Sorry it too my so long to respond.  I am using a modded version of froyo 2.2.  My build number is "voles-userdebug 2.2 FRFxx 49593 test-keys", Kernel version is "2.6.32.9-P3Droid".  (yes it actually says FRFxx, there are no numbers there).  I am not sure if that is the information you were looking for.  I rooted my phone about a week or two after the root became available. So far no other programs have had any connectivity problems and all of the fixes mentioned above do not work for me.

Original comment by TWentwo...@gmail.com on 7 Sep 2010 at 7:14

[GoogleCodeExporter]

I have the exact same issue, and I have tried rebooting and no luck.

I am using Motorola Droid, v. 2.2 , phone hasn't been messed with in any way. 
I've tried using both the Verizon network and my wifi. My connection is fine, 
and no other apps are complaining, but I keep seeing "Error: Unable to connect."

The first time I tried rebooting the phone froze. This may not be related, but 
on the other hand it has never happened before.

Original comment by sfentr...@gmail.com on 14 Sep 2010 at 11:35

[GoogleCodeExporter]

Duplicate of Issue #97

Original comment by mtgo...@gmail.com on 25 Sep 2010 at 4:10

[GoogleCodeExporter]

@17: in case it wasn't clear from the comments that refer to Verizon, many of 
us that had this problem were in the States. So it's not a duplicate of the 
"unable to connecting China" bug.

I finally got mine working, btw, on the third reboot.

Original comment by sfentr...@gmail.com on 26 Sep 2010 at 4:06

[GoogleCodeExporter]

Same problem.... turning phone off and back on worked.

Original comment by crys.sti...@gmail.com on 28 Sep 2010 at 9:01

[GoogleCodeExporter]

I received the "Unable to connect" error many times on my Droid X with 2.2.  
Rebooted, tried again, and still received that error many times.  However, 
after the reboot, on the third or fourth try, it finally connected.

I noticed that my phone was often in "1X" data mode instead of "3G", so it 
might have been intermittent Verizon network trouble.

Original comment by jmccabe....@gmail.com on 7 Oct 2010 at 6:39

[GoogleCodeExporter]

I also experienced this problem (in china) and can confirm that unblocking the 
appspot domain via a VPN fixed the problem. This should only fix it for people 
in countries/places where that domain is bocked such as China.

Original comment by lawre...@gmail.com on 26 Jan 2011 at 6:03

[GoogleCodeExporter]

Rebooting works!

Original comment by agrawal....@gmail.com on 25 Mar 2011 at 7:53

[GoogleCodeExporter]

I can confirm that it does not work (is blocked by the GFW) in China.

Original comment by fabian.f...@gmail.com on 9 Jun 2011 at 12:31

[GoogleCodeExporter]

Same problem here using HTC ThunderBolt with GB 2.3.4 port.  
I have this same issue when using a stock rom as well.  So I can't say it is 
ROM related.
This has been an ongoing issue for me for the past month or so.
I really love this app and just want it to work.

Original comment by cartact...@gmail.com on 12 Jun 2011 at 7:32

[GoogleCodeExporter]

Same issue here...cannot connect. However I added another of my gmail accounts 
and it works. But I need it to work with my main account.

Original comment by kingf...@gmail.com on 19 Jun 2011 at 4:49

[GoogleCodeExporter]

Uninstall, reboot, and reinstalling didn't work for me. I live in America, and 
on stock with Nexus S 4G. I miss this app! :(

Original comment by ddpacino on 20 Jun 2011 at 1:25

[GoogleCodeExporter]

This problem seems to be account related.  I created a new account and it 
chrome to phone works fine.  But with my main account it does not.  I went 
through all the security settings and still I can not find anything to make it 
work.  
WHAT GIVES

Original comment by cartact...@gmail.com on 22 Jun 2011 at 10:22

[GoogleCodeExporter]

Can you provide more details - phone version, network info, if talk works or no 
? 

Original comment by costin on 22 Jun 2011 at 11:14

[GoogleCodeExporter]

Nexus S 4G, OS: 2.3.4, GRJ22 software version. Talk works flawlessly, gmail 
works. No FCs or errors of any kind for anything. Nothing else appears to be 
wrong accept this app. Doesn't work over cellular or wifi. Reboot or 
reinstallation doesn't work either, and I am not creating a new account just 
for this...

Original comment by ddpacino on 22 Jun 2011 at 11:43

[GoogleCodeExporter]

I'm also having this issue, OS: 2.3.4, talk works, gmail push works too, al 
other google services work ok, chrome to phone just stopped working about 03/06 
this year, prior to that it was flawless, it says at the bottom: Error: Unable 
to connect.
Ps: Tried another Google acc that is not my main acc and it connects! why does 
it refuse to work with mine?? I think the problem is in the app authentication 
or something, hope this gets fixed soon!

Original comment by ricardourbinav@gmail.com on 24 Jun 2011 at 5:23

[GoogleCodeExporter]

Error: Unable to connect
For me not working since 1 month ago or so, before working perfectly fine

I'm on 2.3.4 (i9000), but I tried to wipe data, to install a new stock ROM... 
but still same error :(

Original comment by rafale...@gmail.com on 24 Jun 2011 at 10:54

[GoogleCodeExporter]

same here motorola atrix 2.2

Original comment by goodlifechris@gmail.com on 27 Jun 2011 at 12:42

[GoogleCodeExporter]

Have the same issue on my captivate and transformer. Multiple roms have been 
tried. Is there anything we can do to help?

Original comment by keith...@gmail.com on 27 Jun 2011 at 12:47

[GoogleCodeExporter]

i m able to connect with my other google accounts but not with my primary 
account i use for my i897

Original comment by zeroa...@gmail.com on 27 Jun 2011 at 6:42

[GoogleCodeExporter]

Occuring for me also on my new Sensation Tmo. Works fine on my old Nexus one 
still. Tried over 4G full bars with no luck, so it doesn't appear to be a 
network issue on the phone side. 

Running android 2.3.3 with sense 3.0 (Software1.29.531.2)

Original comment by dellybelly on 28 Jun 2011 at 2:14

[GoogleCodeExporter]

Same issue here. Happened with CyanogenMod 7.0.3.1 and still happening with 7.1 
RC1.
Uninstalled and reinstalled app. Rebooted. Total wipe and reinstall. Server 
side issue, it seems.

Original comment by kea...@gmail.com on 28 Jun 2011 at 3:43

[GoogleCodeExporter]

I, too, now have this issue. Samsung Galaxy S, 2.3.3 JVO. Tried everything, but 
it simply won't work with my primary gmail account.

Original comment by meesterl...@gmail.com on 28 Jun 2011 at 6:36

[GoogleCodeExporter]

I have the same issue. used to work fine until 10 days ago. I am using a 
Motorola Droid 2, with CM4D2 unofficial nightlies. Tried stock ROM and Liberty 
ROM. Tried reboot re-install. Nothing works. Works fine with my second gmail 
account.

Original comment by udaykir...@gmail.com on 28 Jun 2011 at 10:54

[GoogleCodeExporter]

I also have this issue.  Even though "Chrome to Phone does not currently 
support Google Apps accounts" I never had a problem with mine until earlier 
this month.

Epic 4g - midNIGHT ROM v5.5

Original comment by ke...@theketovers.com on 29 Jun 2011 at 3:28

[GoogleCodeExporter]

Seriously? It's going on a year and no fix for this problem?
This was touted as a huge feature when it was released and it doesn't work.

Original comment by kea...@gmail.com on 29 Jun 2011 at 5:54

[GoogleCodeExporter]

Had same problem.  Uninstalled.  Noticed i had a gmail login failure notice in 
my alerts bar.  Clicked it to log back in and had to enter a captcha.  After 
that I reinstalled Chrome To Phone and was able to sign in.

Original comment by Freetime...@gmail.com on 1 Jul 2011 at 1:34

[GoogleCodeExporter]

No connection possible since 6-8 weeks. Was working fine and very fast before.

Samsung Galaxy S, Galnet Miui 3.2 (Android 2.3.4)

Original comment by soeren.k...@gmail.com on 4 Jul 2011 at 1:25

[GoogleCodeExporter]

DroidX, using stock blur Froyo, stock blur Gingerbread, or CyanogenMod 7 
nightlies -- just as others have said: it used to work well, now it will not 
connect with my main @gmail.com account.  Switching to another account works.  
Since I FREQUENTLY flash&reinstall&reactivate I imagine there is a VERY long 
list of activations in Google's servers, as there have been in Market and 
Amazon, but unlike those, there's no place to delete old activations through 
Dashboard--could this be the problem?

Original comment by rynosau...@gmail.com on 6 Jul 2011 at 4:14

[GoogleCodeExporter]

Any idea if this is going to be accepted? Seems to be a growing pool of people 
affected. It's been unusable for me for a few weeks now :( Hope it's sorted 
soon especially since there are no alternatives at the moment. 

Original comment by dellybelly on 6 Jul 2011 at 4:47

[GoogleCodeExporter]

I've been having the same issue for a few months. I'm on a Thunderbolt with 
CM7. It works fine with my work gmail account, but not my personal account 
(both are on my phone). Gmail & Talk both work fine. I would really like to be 
able to connect CtP to my personal account!!

Original comment by jeff.a.a...@gmail.com on 7 Jul 2011 at 11:42

[GoogleCodeExporter]

I also have this issue.Tried diferent roms on Motorola DEFY,but with no luck.On 
previous LG Optimus One was working perfect...:(

Original comment by mcmaus...@gmail.com on 8 Jul 2011 at 10:17

[GoogleCodeExporter]

I am having the same issue with three different phones...something wrong with 
the app I think. Unable to connect on my wife's Epic, my Nexus S 4G, and my Evo 
3D.

Original comment by jerbec...@gmail.com on 9 Jul 2011 at 2:28

[GoogleCodeExporter]

Same problem here.

Phone : Samsung Galaxy S
Android Ver. : 2.3.3
Network : Both wifi and mobile network
Gmail & G-Talk : work fine

Original comment by pclo...@gmail.com on 11 Jul 2011 at 6:36

[GoogleCodeExporter]

I am having the same issue on my Droid Charge using a leak GB 2.3.4 with my 
main Google account. If I select my other Google account, it works just fine. I 
can not find in account settings in my main Google account for Chrome to Phone 
settings. I really do not want to use my other Google account to send links.

Can anyone else confirm their second Google account works?

Original comment by groovygr...@gmail.com on 11 Jul 2011 at 10:12

[GoogleCodeExporter]

yeah it worked with a secondary account. my guess that its not clearing out old 
devices that are used with the app and that there might be a limit of how many 
it can have.  would be great if we could clear that data out.

Original comment by goodlifechris@gmail.com on 13 Jul 2011 at 3:12