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 problem here on the Thunderbolt on CM7. Can use my secondary gmail account 
but not my primary account.

Original comment by luniz7@gmail.com on 13 Jul 2011 at 10:36

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Also have this issue, SGS i9000, running CM7 (Insanity mod). Cache wipes won't 
fix it.

Original comment by francois...@gmail.com on 14 Jul 2011 at 2:21

[GoogleCodeExporter]

Same issue Droid Charge Running 2.3.4 GummyCharge GB 1.5

Original comment by Langkamm...@gmail.com on 14 Jul 2011 at 5:58

[GoogleCodeExporter]

I think comment 43 has an excellent idea on this. I see a lot of custom ROMs 
here, which makes me want to assume (dangerous!) that we wipe and re-install a 
lot, and may be adding new AndroidIDs every time we wipe and install fresh, and 
have filled the list of possible IDs that C2P will recognize.

A good test that someone (sadly, I cannot) do would be to find an old nandroid 
backup that C2P worked on, restore it, and copy down the AndroidID from that 
install. 
Then, restore/wipe to a instance of Android where C2P does not work and change 
the AndroidID to the one from where C2P was working and see if C2P works.
If it does, then we know what is probably causing the issue and can contact the 
devs and hopefully have them put a LIFO method on the ID list, or wipe it, 
something. 

I believe Android ID Changer can do the AndroidID things for us.

If you want to use sqlite manually, the ID is also in:

- /data/data/com.android.providers.settings/databases/settings.db
-- table [secure] android_id as a 16 long HEX
-- table [gservices] android_id as a decimal

- /data/data/com.google.android.googleapps/databases/gls.db
-- table [meta] androidId as a decimal

Original comment by cgug...@gmail.com on 14 Jul 2011 at 9:13

[GoogleCodeExporter]

I have the same problem on my Nexus S GRJ22 on T-Mobile. I have uninstalled the 
extension and the app, even did a factory reset of my phone. This should be a 
high-priority issue, it renders the app completely useless for affected users.

Original comment by addison....@gmail.com on 16 Jul 2011 at 5:24

[GoogleCodeExporter]

Chrome to phone does not work anymore.  Gmail and Talk work fine on my phones.

I can't figure out how to derigister devices which has to be the issue.  I 
removed access from my main google account don't you think at least that would 
remove all the devices listed?

I have used a ton of roms and phones.  Chrome to phone doesn't work anymore on 
any new device.  I have had four personal devices, and can't use it on any new 
phones.  Stock 2.2, rooted 2.3 or otherwise.  

Original comment by Yianaki@gmail.com on 18 Jul 2011 at 1:33

[GoogleCodeExporter]

Same problem (Desire Z)

but! i once restored from an old backup, and C2P worked fine, (I wasn't able to 
connect at that time with a newly installed ROM) 
I think Comment 55 is right. I've lost the backup long since then, and haven't 
been able to connect. I Really miss the feature.

Tried with dozens of ROMs - Sense, MIUI, AOSP etc ... 

Original comment by arme...@gmail.com on 19 Jul 2011 at 1:29

[GoogleCodeExporter]

Same problem Samsung GS2 (Cognition ROM). It works with different accounts, but 
not with my main Google account.

Original comment by tamp...@gmail.com on 19 Jul 2011 at 7:10

[GoogleCodeExporter]

Dont know if its gonna help any but I have those two lines from logcat.

 07-20 12:35:27 .992: WARN/SingleClientConnManager(5164): Invalid use of SingleClientConnManager: connection still allocated.
 07-20 12:35:27 .992: WARN/SingleClientConnManager(5164): Make sure to release the connection before allocating another one.

Original comment by m8jus...@gmail.com on 20 Jul 2011 at 10:39

[GoogleCodeExporter]

Same here. Used it since beginning. Stopped working couple of days ago on 
Samsung SG2 with Lightening ROM. Now rolled back to Official firmware and yet 
cannot connect.

Original comment by lord.pho...@gmail.com on 21 Jul 2011 at 11:09

[GoogleCodeExporter]

The funny thing about this issue is I've had C2P on 3 different phones and a 
tablet all at once and it worked flawlessly. For some reason, just in the last 
month I've had severe issues with it working when switching ROMs, and even 
nandroids with it working have stopped working. Device in question is Droid 
Incredible 2 on CM7 nightlies and OMFGB nightlies

Original comment by brosep...@gmail.com on 22 Jul 2011 at 7:13

[GoogleCodeExporter]

I provided a complete logcat to the developers in my post about this issue so 
they could see what's going on but no reply yet. I'm thinking this project is 
dead because with the number of people having problems you would think that the 
application and/or server would have been updated by now to address this issue.

Original comment by netw...@gmail.com on 24 Jul 2011 at 7:29

[GoogleCodeExporter]

I've read that this seems to happen to people who do a lot of flashing. It 
seems that the Chrome-to-phone stores every new rom as a new device, but it 
doesn't delete your previous device. So, you probably have lots of devices 
attached to your chrome-to-phone account. What I can't figure out is how to 
delete these devices. 

Original comment by rybl...@gmail.com on 24 Jul 2011 at 10:26

[GoogleCodeExporter]

the same here.
@google: please give us the possibility to delete no longer used device id's.

Original comment by Merlin...@gmail.com on 25 Jul 2011 at 4:47

[GoogleCodeExporter]

same issue here. c2p no longer works since CM ROM was installed on my DX. 
Google, please allow users to delete all their DeviceID's per account. 

Original comment by andrew....@gmail.com on 25 Jul 2011 at 5:16

[GoogleCodeExporter]

Haven't been able to connect for 2 months. Issue using Samsung captivate stock 
and Samsung galaxy tab 10.1.

Need to delete old connections from custom roms

Original comment by aaronm...@gmail.com on 25 Jul 2011 at 5:45

[GoogleCodeExporter]

Same issue... would love to get a way to unregister a device ID or at least 
reset all the IDs so we can start over from scratch.

Original comment by Mindless...@gmail.com on 25 Jul 2011 at 5:46

[GoogleCodeExporter]

This needs to be high priority. Google please fix this, the service is useless 
for us!!

Original comment by negropla...@gmail.com on 26 Jul 2011 at 5:36

[GoogleCodeExporter]

Same exact issue here.

Original comment by mcl...@gmail.com on 26 Jul 2011 at 5:52

[GoogleCodeExporter]

been having this issue, i tried 3 phones and the same thing. i have two 
accounts and my main one doesnt want to connect but my other one will connect. 
inspire 4g rooted

Original comment by blui...@gmail.com on 27 Jul 2011 at 5:52

[GoogleCodeExporter]

Is anyboby from Google reading this? Would you please give us a feedback?

Original comment by tamp...@gmail.com on 27 Jul 2011 at 11:30

[GoogleCodeExporter]

Same problem here. I was working fine till I reflashed my ROM, and now it's 
dead. I successfully used a different Google account and was able to instantly 
log in.

Original comment by markric...@gmail.com on 27 Jul 2011 at 7:40

[GoogleCodeExporter]

I have the same issue with my main account, but for some reason it works fine 
with an alternate account. Tried clearing cache, data, reinstalling, but to no 
avail.

Original comment by hama...@gmail.com on 28 Jul 2011 at 12:44

[GoogleCodeExporter]

I have the same issue. I have two accounts, one works and one doesn't. The one 
I have all my Google services added to is the one that doesn't work. So my 
question to all of you is, do you have Google+ (or some other service) added to 
the none functional accounts?

Original comment by tao2qu...@gmail.com on 28 Jul 2011 at 9:42

[GoogleCodeExporter]

I have the same issue, when is the expected fix?
I do not want to create a new google account and I just want this account to 
get fixed. Can this issue be fixed?
Thanks

Original comment by ashishla...@gmail.com on 29 Jul 2011 at 2:32

[GoogleCodeExporter]

I would like to see some feed back or a fix for this issue. I am having this 
issue on all my phones except for the Xoom. It is a PITA and I am kind of 
peeved that Google is not providing or fix or feedback for this..........

Original comment by jay.gottschalk on 30 Jul 2011 at 12:30

[GoogleCodeExporter]

Issue 343 has been merged into this issue.

Original comment by aml...@gmail.com on 30 Jul 2011 at 3:25

[GoogleCodeExporter]

Issue 341 has been merged into this issue.

Original comment by aml...@gmail.com on 30 Jul 2011 at 3:26

[GoogleCodeExporter]

Issue 326 has been merged into this issue.

Original comment by aml...@gmail.com on 30 Jul 2011 at 3:29

[GoogleCodeExporter]

Issue 330 has been merged into this issue.

Original comment by aml...@gmail.com on 30 Jul 2011 at 3:31

[GoogleCodeExporter]

Would be nice to disable my previous IDs, since I cannot use this app anymore.

Original comment by njr...@gmail.com on 31 Jul 2011 at 7:50

[GoogleCodeExporter]

@ #75: I'm having trouble login in and I have G+.

A frind of mine, also G+, was logged in on his phone and it was working. He 
signed out and when he tried to login again he got the same error...

Original comment by ted.wal...@gmail.com on 31 Jul 2011 at 11:19

[GoogleCodeExporter]

I tried on a different phone with different ROM today, same result.
But I added an other account, with G+, to that phone and it worked.

Original comment by ted.wal...@gmail.com on 31 Jul 2011 at 3:11

[GoogleCodeExporter]

Same here.. a few days ago, it worked fine... :(

Original comment by aiaki...@gmail.com on 1 Aug 2011 at 8:34

[GoogleCodeExporter]

fucking google reply to this. hello anyone home? let us reset our android ID's

Original comment by ddarv...@gmail.com on 2 Aug 2011 at 5:53

[GoogleCodeExporter]

Adding my voice to this bug, this is one of the features I truly adore (and use 
to show off android on a regular basis ^^ ).  Everything else google-wise works 
like a charm.
Please google, figure out what changed in June to our accounts, this is an 
unfortunate change :s

Original comment by nic.de.m...@gmail.com on 2 Aug 2011 at 6:38

[GoogleCodeExporter]

Anyone know anyone in Engadget or any of the major Android sites like 
AndroidCentral, AndroidSpin, etc? Might have a better chance of getting their 
attention if this becomes more public like all the other issues that they seem 
to ignore.

I've been using Android for a while now and its sad that no one from Google can 
even acknowledge an issue as big as this one from an app created by themselves. 
I'm sure there are a lot more like this one. Might even get a better response 
if you uninstall it and say its a malicious app or some sort from the Market. 
Maybe that'll get their attention faster.

Original comment by mtran...@gmail.com on 2 Aug 2011 at 6:51

[GoogleCodeExporter]

Looks like they're not acceppting new users/phones :) ... just speculating. 
Same problem here.

Original comment by miguelfe...@gmail.com on 2 Aug 2011 at 2:58

[GoogleCodeExporter]

Seems to be (as I think others have stated) that too many devices have been 
connected. This typically occurs when someone flashes ROMs frequently. We need 
a way to remove old IDs so that we can continue to use this wonderful feature.

Original comment by nicholas...@gmail.com on 2 Aug 2011 at 8:02

[GoogleCodeExporter]

I have a potential work around for those of you with a ROM backup or, better 
yet, a titanium backup of a working chrome to phone installation;

Restore c2p and run it. Though it's not functional server-side, the app thinks 
all is good. Now go to settings and press the disconnect button. If you're 
lucky your account will now be removed from c2p server-side allowing you to 
reconnect.

I've succeeded with this trick a few times now. Maybe it'll work for a few of 
you.

Original comment by meesterl...@gmail.com on 2 Aug 2011 at 8:56

[GoogleCodeExporter]

Adding my voice to this HUGE bug as well. Using the same Google email address, 
but now unable to connect. Can connect using a different email address. Poor 
show from Goog.

Original comment by griffor...@gmail.com on 3 Aug 2011 at 5:11

[GoogleCodeExporter]

I can confirm meesterlars sugestion: (#91)

I've hit disconnect in the app prefs on the old phone, and was able to connect 
on my new phone :)

Thanks!!!

Original comment by miguelfe...@gmail.com on 3 Aug 2011 at 6:51

[GoogleCodeExporter]

Just to confirm, I am able to restore an old ROM backup, disconnect from C2P 
then restore my current ROM and connect just fine to C2P. Goog, this should be 
an easy fix, just give us a web interface in the Chrome extension where we can 
manage our connected devices!

Original comment by nicholas...@gmail.com on 3 Aug 2011 at 7:37

[GoogleCodeExporter]

well im sorry that i had to do this and some people may not agree with my style 
but i just submitted 10 different posts to the website basically spamming them 
so they get the fucking point that this is unacceptable. I need chrome to phone 
to work and such a simple fix is taking forever

Original comment by ddarv...@gmail.com on 4 Aug 2011 at 8:19

[GoogleCodeExporter]

Samsung moment with android 2.1 and cant find it in the market

Original comment by jon...@gmail.com on 4 Aug 2011 at 8:58

[GoogleCodeExporter]

@ddarv...@gmail.com

10 emails of you ranting and swearing over an issue is not spam just an 
annoyance that can be deleted, honestly a single post and explaining your issue 
is more than sufficient and possibly an update, and in three hours im not sure 
how quickly they could fix it, ever programmed before? not the easiest thing to 
fix quickly even with a good understanding of programming and how connections 
are supposed to be made between computer and phone.

HAVE A GREAT DAYYYYY! 

Original comment by nlaperri...@gmail.com on 5 Aug 2011 at 12:11

[GoogleCodeExporter]

while i respect your opinion, i disagree that they havent had enough time to 
fix it.. see the first time this problem was brought up was aug of 2010.. that 
is exactly a year with NO solution yet. and yes i paid for a phone that has the 
ability to do chrome to phone and it aint working. id called android tech 
support but they dont have one. so this was the nxt best thing

Original comment by ddarv...@gmail.com on 5 Aug 2011 at 12:25

[GoogleCodeExporter]

I'm more puzzled that it hasn't been acknowledged as a defect yet :/ kinda 
disheartening. However spamming e-mails is never a productive thing as it 
generally turns a bad situation worse and turns the devs against the users 
(never a good thing). 

Believe me im as disappointed as you are about this, and since it is now an 
actual Google product and not a side project it's possible that there's 
something bigger coming, but all would be needed here is a simple note saying 
we acknowledge the bug and will work on it or go away we will fix it when we 
get to it even :) 

I actually AM a developer, so I know some issues get put on the back burner, 
but this one seems to be rapidly making it's way to the front and if peoples 
guesses are correct it's going to happen to a lot more people as more people 
start tinkering. 

Original comment by dellybelly on 5 Aug 2011 at 1:25

[GoogleCodeExporter]

I agree this problem is only going to grow as people get new devices, flash 
roms and perform more and more hard resets. I unfortunately cannot restore a 
backup on my Atrix so i can't even disconnect my old profile. its been months 
since I've been able to use this app.

Original comment by goodlifechris@gmail.com on 5 Aug 2011 at 6:31