Error: Unable to connect

GoogleCodeExporter commented 9 years ago

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 commented 9 years ago

Don't listen to all the ingrates, thanks for the fix guys!

Original comment by nicholas...@gmail.com on 21 Aug 2011 at 3:15

GoogleCodeExporter commented 9 years ago

Take note of what the engineer said. Be sure to disconnect your C2P install 
before wiping!

Original comment by kea...@gmail.com on 21 Aug 2011 at 3:31

GoogleCodeExporter commented 9 years ago

Finally, it works again! Thank you so much!

Original comment by thatbi...@gmail.com on 21 Aug 2011 at 10:11

GoogleCodeExporter commented 9 years ago

thank you so much :)

Original comment by soeren.k...@gmail.com on 21 Aug 2011 at 10:12

GoogleCodeExporter commented 9 years ago

Verified, it sure does work again! Thanks a lot! #veryhappy

Original comment by nic.de.m...@gmail.com on 21 Aug 2011 at 10:18

GoogleCodeExporter commented 9 years ago

YES :-) thank you very much it works well.

Original comment by tamp...@gmail.com on 21 Aug 2011 at 3:44

GoogleCodeExporter commented 9 years ago

Fixed !!!
 Thanks SOO MUCH!

Original comment by arme...@gmail.com on 22 Aug 2011 at 6:22

GoogleCodeExporter commented 9 years ago

Works again for me

Original comment by bfundar...@gmail.com on 22 Aug 2011 at 12:43

GoogleCodeExporter commented 9 years ago

working on phone and tablet again. THANK YOU!

Original comment by keith...@gmail.com on 22 Aug 2011 at 12:49

GoogleCodeExporter commented 9 years ago

Hi

not sure if this is the correct thread to post in, so please move if needed.

This could be due to Firefox upgrade (V6), but when I try to send to phone, it 
comes up with another tab telling me that I need to install it on my phone 
(along with the QR code).  When I try to install on the phone, I get 
"installation unsuccessful", "Package file was not signed correctly".

when I go into the software on my phone, it says the device is registered.  
clicking on 'unregister device' does nothing...after a while it comes back as 
'device registered' again.

gmail works fine, with refresh no problem.  

talk opens up, status online, but I never use it, so not sure what to check here

phone is nexus one, stock, 2.3.4, GRJ22

Original comment by g.mbir...@gmail.com on 30 Aug 2011 at 8:25

GoogleCodeExporter commented 9 years ago

took a risk and uninstalled chrome2phone on my Nexus.  install then worked, and 
now sending to phone works fine.

please disregard above message.

thx!

Original comment by g.mbir...@gmail.com on 31 Aug 2011 at 6:12

GoogleCodeExporter commented 9 years ago

not working for me also - HTC Sensation

Original comment by mike.liv...@gmail.com on 5 Nov 2011 at 3:00

GoogleCodeExporter commented 9 years ago

Still getting unable to connect error on a HTC sensation with custom ROM

Original comment by rajac...@gmail.com on 7 Nov 2011 at 9:15

GoogleCodeExporter commented 9 years ago

Not working on new, stock rom samsung galaxy s 2. Tried clearing data, 
unisntalling, reinstalling, and still UNABLE TO CONNECT message appears :(

Original comment by carlos...@gmail.com on 7 Nov 2011 at 11:12

GoogleCodeExporter commented 9 years ago

It just stopped working on my phone for no reason at all after having worked 
just fine since the day I installed it, wtf?

Original comment by thelosts...@gmail.com on 7 Nov 2011 at 11:29

GoogleCodeExporter commented 9 years ago

No longer working on official Samsung Galaxy S2 2.3.4 release.

Original comment by OzzyDoug...@gmail.com on 7 Nov 2011 at 1:16

GoogleCodeExporter commented 9 years ago

Same here "Unable to connect" HTC Sensation.

Original comment by tiskara....@gmail.com on 7 Nov 2011 at 1:18

GoogleCodeExporter commented 9 years ago

Same here.

"Unable to connect" HTC EVO 3D GSM

Original comment by venusa...@gmail.com on 7 Nov 2011 at 1:39

GoogleCodeExporter commented 9 years ago

just stopped working. wtf. changing to Pulse

Original comment by summerbr...@gmail.com on 7 Nov 2011 at 1:41

GoogleCodeExporter commented 9 years ago

W/SingleClientConnManager( 1120): Invalid use of SingleClientConnManager: connec
tion still allocated.
W/SingleClientConnManager( 1120): Make sure to release the connection before all
ocating another one.

Looks more like a Java Poblem to me ... The response context is not properly 
consumed by the application...

Original comment by sebak...@gmail.com on 7 Nov 2011 at 1:42

GoogleCodeExporter commented 9 years ago

This is also not working for me.  It was working this morning, I then decided 
to see if I could get the same problem as everyone else, so i disconnected my 
phone and then attempted to reconnect.  Got the error "Unable to Connect".

Original comment by xenoput...@gmail.com on 7 Nov 2011 at 1:49

GoogleCodeExporter commented 9 years ago

OK, a whole bunch of people had C2P errors starting today! Me too. Mine were 
(are) on Chrome side "Device not registered for user," and on C2P side, "Unable 
to Connect." Hopefully, this is a short-lived problem ... ya think?

Original comment by dukeste...@gmail.com on 7 Nov 2011 at 2:37

GoogleCodeExporter commented 9 years ago

Hm use this daily, never happened before. I can confirm it's not working 
anymore (nexus s).

Original comment by versluyssander on 7 Nov 2011 at 3:23

GoogleCodeExporter commented 9 years ago

Just tried to use chrometophone today on Gingerbread 2.3.7 - "Error:unable to 
connect" when trying to connect to my google account. I did install Android 
market(3.3.11) the other day and haven't used c2p since.

Original comment by jnot...@gmail.com on 7 Nov 2011 at 3:44

GoogleCodeExporter commented 9 years ago

Same issue - using Cyanogenmod 7.1 on Samsung Galaxy S2.  Have tried switching 
accounts, uninstall/reinstall phone app, clearing data/cache.  Would welcome 
other ideas :-/

Original comment by samdonal...@gmail.com on 7 Nov 2011 at 3:55

GoogleCodeExporter commented 9 years ago

I'm experiencing the same problem on my Samsung Vibrant.

Original comment by rick...@gmail.com on 7 Nov 2011 at 4:26

GoogleCodeExporter commented 9 years ago

Phone = "unable to connect"
Browser = a redirect to the Chrome to Phone 'Help' page

First noticed on November 7, 2011 @ 07:00 EST.

Original comment by kjtrab...@gmail.com on 7 Nov 2011 at 4:41

GoogleCodeExporter commented 9 years ago

I'm experience the same "unable to connect" today.

Original comment by mobilech...@gmail.com on 7 Nov 2011 at 4:46

GoogleCodeExporter commented 9 years ago

Unless you have new information to add, please "star" this thread rather than 
the "me too" posts. Thanks.

Original comment by kea...@gmail.com on 7 Nov 2011 at 4:49

GoogleCodeExporter commented 9 years ago

[deleted comment]

GoogleCodeExporter commented 9 years ago

[deleted comment]

GoogleCodeExporter commented 9 years ago

Hello, I had to hard reset my samsung galaxy S2, and after reinstalling Chrome 
2 Phone,  I get this message "unable to connect".

I don't know if it can help to know it's after Hard reset... I hope yes, 
because I miss it a lot !!
Thank you

Original comment by guy...@gmail.com on 7 Nov 2011 at 6:09

GoogleCodeExporter commented 9 years ago

@182 same phone, but no hard reset SGS2 e4gt. Started today! Worked yesterday!

Original comment by Capitol...@gmail.com on 7 Nov 2011 at 6:12

GoogleCodeExporter commented 9 years ago

Stock ROM on an HTC Thunderbolt running Gingerbread. Just stopped working 
today. Reboot, uninstall/reinstall. Nothing doing. "unable to connect". 
Fiddlesticks. :o)

Original comment by dpenderg...@gmail.com on 7 Nov 2011 at 7:05

GoogleCodeExporter commented 9 years ago

Why does the Status say Fixed? It obviously isn't fixed. Please reopen the 
issue and fix it.

Original comment by pasc...@gmail.com on 7 Nov 2011 at 7:10

GoogleCodeExporter commented 9 years ago

The previous incident was widespread to ROM-flashing users. The device history 
list per user was maxing at 10. This appears to be a new issue as it's 
happening to stock users.

Original comment by kea...@gmail.com on 7 Nov 2011 at 7:14

GoogleCodeExporter commented 9 years ago

Im on a Galaxy S2 running custom 2.3.5 Cognition v1.6 and have the same issue, 
have only flashed three other ROMs since purchasing the phone and disconnecting 
from a working nandroid backup didn't work. ISSUE:Starred.

Original comment by tristanj...@gmail.com on 7 Nov 2011 at 7:22

GoogleCodeExporter commented 9 years ago

New error message today:

Error sending to phone:
App Engine Error

Over Quota

This Google App Engine application is temporarily over its serving quota. 
Please try again later.

Original comment by kea...@gmail.com on 7 Nov 2011 at 7:25

GoogleCodeExporter commented 9 years ago

That could be a good sign, I get that message now too! To me that says 'We're 
working on it!' ;o)

Original comment by tristanj...@gmail.com on 7 Nov 2011 at 7:29

GoogleCodeExporter commented 9 years ago

Same for me another time ...

Original comment by danidr...@gmail.com on 7 Nov 2011 at 7:45

GoogleCodeExporter commented 9 years ago

Thank you so much !! I don't know what happened now, but I can connect !!
SO... thank you so much for the person who did something !!!!!!

Original comment by guy...@gmail.com on 7 Nov 2011 at 7:56

GoogleCodeExporter commented 9 years ago

Just tried activating Chrome 2 phone with my account and it registered straight 
away!! Pages are now sending to my phone perfectly!!! Give it another try 
people!! Whoop!!! ;o)

Original comment by tristanj...@gmail.com on 7 Nov 2011 at 7:56

GoogleCodeExporter commented 9 years ago

Yep, they fixed it! Bravo Google, BRAVO! (you shouldn't have broken it, but 
hey, we love you when you fix it :-)

Original comment by pasc...@gmail.com on 7 Nov 2011 at 9:22

GoogleCodeExporter commented 9 years ago

Working for me OP 182

Original comment by Capitol...@gmail.com on 7 Nov 2011 at 10:22

GoogleCodeExporter commented 9 years ago

Fixed for me .. thanks..Droid 1 Froyo

Original comment by Eugene.G...@gmail.com on 8 Nov 2011 at 1:04

GoogleCodeExporter commented 9 years ago

fixed for me

Original comment by zulfika...@gmail.com on 8 Nov 2011 at 10:30

GoogleCodeExporter commented 9 years ago

Fixed for me today.

Original comment by OzzyDoug...@gmail.com on 8 Nov 2011 at 11:46

GoogleCodeExporter commented 9 years ago

happy days. hope they keep the fix method lol

Original comment by leecavtu...@googlemail.com on 8 Nov 2011 at 7:17

GoogleCodeExporter commented 9 years ago

Still have it reproduced on my G2.
Error: Unable to connect

Original comment by stansult on 25 Jan 2012 at 3:56

GoogleCodeExporter commented 9 years ago

hi there,
didn't used ChromeToPhone for a couple of months -
but now i wanted to connect again, but got errors:

"Unable to connect" HTC desire with Android 2.2.2

Same error on Samsung GalaxyTab 10.1N with Android 3.2

Thanx for any hints.

Original comment by r.zin...@gmail.com on 27 Jan 2012 at 7:14

ZAD-Man / chrometophone

Error: Unable to connect #158