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]

FWIW I just emailed Whitson Gordon at Lifehacker. hopefully he takes notice and 
can get something done. I'd suggest emailing your favorite android blogs.

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

[GoogleCodeExporter]

A friend of mine can't connect from his phone. But today we tried from his 
Galaxy Tab 10.1 and it worked. But still doesn't work on the phone.
So I'm guessing they check what kind of device that is connecting...

I will try and see if I have an old backup and try the suggested 
release-workaround.

Original comment by ted.wal...@gmail.com on 6 Aug 2011 at 11:04

[GoogleCodeExporter]

The backup trick worked! Restored data from Titanium. It looked ok but didn't 
recieve any links. Disconnected the phone. Reconnected and now it works.

Original comment by ted.wal...@gmail.com on 6 Aug 2011 at 11:53

[GoogleCodeExporter]

I think this a a gingerbread issue. Chrome2Phone worked whilst I was on 2.1 & 
2.2, since I upgraded to 2.3 it has stopped with the error "unable to connect"
Google please fix this issue.

Original comment by deejay00...@gmail.com on 9 Aug 2011 at 10:28

[GoogleCodeExporter]

I'm been on Gingerbread for +6(??) months and only got this problem the last 
couple of weeks...

Original comment by ted.wal...@gmail.com on 9 Aug 2011 at 11:53

[GoogleCodeExporter]

It's definitely not a gingerbread thing. I was running GB on my OG Droid for 
months, and I didn't encounter the issue until a few flashes with my 
Thunderbolt. Due to the fact that removing a connection on an old rom allows 
you to connect a new ROM there is almost no doubt that it's an issue of having. 
Too many devices connected. 

Original comment by nicholas...@gmail.com on 9 Aug 2011 at 12:23

[GoogleCodeExporter]

Same problem here. I think it has to do with the number of new ROMs I've 
flashed. Maybe each new activation on a ROM counted as a different device in 
the C2P server and I've hit my limit.

Original comment by prolefee...@gmail.com on 9 Aug 2011 at 11:37

[GoogleCodeExporter]

GOOGLE please reset my chrome to phone id so that I can get it to work again on 
my mobile.

Original comment by deejay00...@gmail.com on 11 Aug 2011 at 1:40

[GoogleCodeExporter]

Same problem for me. HTC Sensation EU.

Original comment by nsi...@gmail.com on 11 Aug 2011 at 11:11

[GoogleCodeExporter]

I'll just reiterate that I think this has to do with having too many IDs 
associated with Chrome to Phone. I work for a carrier and have Chrome to Phone 
associated with 15 or so phones. The Chrome to Phone team would need to provide 
a way (or an automated timeout process) to remove unused IDs.

Original comment by gsy...@gmail.com on 12 Aug 2011 at 7:38

[GoogleCodeExporter]

I am having the same problem and I no longer have backups of old roms to 
restore to remove chrome to phone from.

This feature of android was my favorite feature.  

I have to agree with others, it seems that it is tied to how many devices are 
"attached " to the service and we have no way of removing old devices from this 
magical list.

Original comment by xenoput...@gmail.com on 15 Aug 2011 at 12:57

[GoogleCodeExporter]

I just had the same issue with the Amazon App Store yesterday but was able to 
easily fix it by going to the site and deregistering old copies of my device.  
I hope Google gives us the ability to do this soon!

Original comment by ke...@theketovers.com on 15 Aug 2011 at 1:35

[GoogleCodeExporter]

Some days ago I took a look at the server code and the list of registered 
devices has a maximum of 10 items, at that moment there's a routine to remove 
the oldest one, but it's clear that it's not working correctly for you. 

That's all that I can help here, I don't really know any Java.

Original comment by aml...@gmail.com on 16 Aug 2011 at 5:50

[GoogleCodeExporter]

Is there no way of us getting in contact with someone on the developer team to 
just fix this? It's very annoying.

Original comment by scottym...@gmail.com on 16 Aug 2011 at 5:53

[GoogleCodeExporter]

I would greatly appreciate anything that can be done.  If a developer wants to 
contact me personally to have me run some tests, feel free to contact me via 
email and we can easily setup a phone call or something and we can run through 
some tests or something.

Original comment by xenoput...@gmail.com on 16 Aug 2011 at 6:02

[GoogleCodeExporter]

Do they even look at this?

Original comment by scottym...@gmail.com on 16 Aug 2011 at 6:04

[GoogleCodeExporter]

I think the question should be do they really care ? It doesn't appear so. If I 
was this lackadaisical in responding to a serious bug in the software I 
support, I'd have been fired by now.

Original comment by griffor...@gmail.com on 16 Aug 2011 at 6:58

[GoogleCodeExporter]

they really dont care.. i think part of the reason they bought motorola is to 
have a stronger support infrastructure.

Original comment by ddarv...@gmail.com on 16 Aug 2011 at 7:04

[GoogleCodeExporter]

From the C2DM site (http://code.google.com/android/c2dm/).

"The C2DM server periodically refreshes registration IDs."

Obviously the server is NOT doing that.  Unless by "periodically" they mean 
like once a year or something.

Original comment by lil...@gmail.com on 17 Aug 2011 at 5:25

[GoogleCodeExporter]

Pending the solution:
Install Chromium.
Connect with other Google account.
Switch browsers to use "Chrome(s) to Phone" (Wt...?)
Enjoy

Original comment by naev...@gmail.com on 18 Aug 2011 at 1:32

[GoogleCodeExporter]

@comment 113. You are a project member, why can you not get any of the 
developers to fix this ? It's is CLEARLY a problem, which CLEARLY needs 
addressing. This is shoddy, shoddy work.

Original comment by griffor...@gmail.com on 18 Aug 2011 at 2:10

[GoogleCodeExporter]

I am not a project member, just someone who wants to *help* fix this. I am 
speaking out of turn. That said:

To those who are angry at person X or Google for this: I think we may be making 
a dangerous assumption to how many people are on this project team or the 
company's support for it. This product launched over a year ago, and the 
project is likely closed. However, the extension is still being updated (last 
updated on July 12, 2011). This is a good sign. Google and the Android project 
are expanding like a wildfire, and the team focus is likely on initiating and 
planning other projects, and maintaining products that have issues across the 
entire Android platform. Also, keep in mind that Google Labs is shut down. I do 
not know how this affects C2DM.
Regardless, our bug affects a) users with more than 10 android devices and b) 
users who root their phone and have installed (or wiped and reinstalled) more 
than 10 roms/instances with unique android device ids. We're *absolutely not* 
the majority. The severity and the breadth of the issue is low, and that is 
good for the product but sucks for those afflicted. We have to be patient. But..

If you want to help fix the issue: Take a look at the code. If it is in the 
Chrome to Phone (open source 
--http://code.google.com/p/chrometophone/source/browse/) part, we can resolve 
it. If it is in the C2DM part (closed source  -- 
http://code.google.com/android/c2dm/) a C2DM team member will have to resolve 
it. If you don't know how read code, that's ok -- just star the issue and be 
patient. The time may come. Again, they aren't ignoring us, they're probably 
just working on more important/severe issues.

Patient people: Don't forget to take a look at the suggestions by comment120, 
c113, c91. Those fixes may work.

Original comment by cgug...@gmail.com on 18 Aug 2011 at 2:59

[GoogleCodeExporter]

I don't disagree with you; but just because we are the "minority" doesn't mean 
we don't have a large impact. We are the grass roots people and people who help 
advance the android platform and show what unique and cool things can be done. 

This is how Chrome to Phone was created in the first place by people like us! I 
agree with most of your post though; I just don't think you can simply justify 
it by saying we are the minority users when in reality we are just as important 
as the million users who don't contribute anything. 

Original comment by dellybelly on 18 Aug 2011 at 3:10

[GoogleCodeExporter]

I agree with you and thank you for reinforcing that we are pushers of Android 
and love it because it is open and unique and flexible.

I started looking into the C2P code again -- there's a revision here which 
kicks off multiple device support: 
http://code.google.com/p/chrometophone/source/detail?r=155
and another here which updates to using OAuth. This is also where the 
max_devices is set to 10, as comment 113 said. 
http://code.google.com/p/chrometophone/source/detail?r=248
I believe that this specifically is what should automatically delete the oldest 
device: 
http://code.google.com/p/chrometophone/source/diff?spec=svn248&r=248&format=side
&path=/trunk/appengine/src/com/google/android/chrometophone/server/RegisterServl
et.java

Just putting my starting point out there for other interested parties.

Original comment by cgug...@gmail.com on 18 Aug 2011 at 4:26

[GoogleCodeExporter]

Would it be possible to do a logcat to see how the app disconnects our devices 
from their servers? And then from that logcat, possibly create an app that can 
disconnect our device independent of Chrome to Phone. I don't know much about 
programming but it could be possible there are extra commands to remove all 
registered devices and maybe logcat can show how that's done?

Original comment by mtran...@gmail.com on 18 Aug 2011 at 4:40

[GoogleCodeExporter]

I highly doubt that any part of the deactivation of an old device happens on 
the phone side. In theory, once you have 10 devices connected, the new device 
will send the information (name, id, etc) to the server, the server then 
removes the oldest device, and adds the new one. It looks like the code is 
there, per Cgugino's post, but its clearly not working. The relevant code 
starts at line 119 and runs to line 145.

I read through this block and it seems sound, but my code skills are rusty at 
best, and were never very robust to begin with. There do appear to be a few 
dangling brackets, which could be causing an error with the 
pm.deletePersistent(oldest); command. Perhaps someone a little fresher could 
look at this section and provide better insight?

Original comment by nicholas...@gmail.com on 18 Aug 2011 at 4:57

[GoogleCodeExporter]

Just to clarify: I'm one of the two developers of the firefox extension. If you 
have problems with it then Patrick or I will try to help you.
But this is a problem at the server side, I already stated all that I found 
about it and I'm not gonna try to push it to the main developers: 
First, I think that they might be already too busy, this was originally a side 
project. And of course I think that they are already aware of the problem. 
Second, the moment people starts cursing means that I lose all the interest 
that I might have to help them. So you can say thanks to comment 86 and his 
nice behavior in this site.
If you have the problem but don't have anything to help fix it then just star 
it, sending a mail to every one stating "me too" or "fix it" won't help anyone.

Original comment by aml...@gmail.com on 18 Aug 2011 at 5:07

[GoogleCodeExporter]

Why don't we just have our own instance of Chrome to Phone? Does anyone have 
the resources to host it?

Original comment by zanekami...@gmail.com on 18 Aug 2011 at 5:30

[GoogleCodeExporter]

Its not quite that simple. The server side code (arguably the more important of 
the two) is not open sourced, meaning that someone would have to code it by 
hand. Its certainly not impossible, but its not as simple as just grabbing the 
code and setting up your own environment.

Original comment by nicholas...@gmail.com on 18 Aug 2011 at 5:37

[GoogleCodeExporter]

Let's try to keep in mind that C2P was a free gift to us from some Google 
engineers, and most of us here have contributed absolutely nothing to it. So 
let's drop the sense of entitlement and be thankful that it ever worked at all. 
It's counter-productive to insult the people whose help we need. When we behave 
like a bunch of spoiled, entitled toddlers, it makes them not want to help us.

The best you can do is star this issue and encourage everyone else to do the 
same. Eventually, it will get noticed and fixed.

Original comment by ryanboeh...@gmail.com on 18 Aug 2011 at 5:38

[GoogleCodeExporter]

Well it doesn't seem too difficult to write our own implementation of the 
server software. We could implment that and then make a few changes to the 
client application to point it to wherever the new sever is hosted.

Original comment by zanekami...@gmail.com on 18 Aug 2011 at 5:43

[GoogleCodeExporter]

Linkpush on the market,  works for me. Give it a shot.

Original comment by Langkamm...@gmail.com on 18 Aug 2011 at 6:02

[GoogleCodeExporter]

Zamekami... is correct. many different apps suchs as mightytext use their own 
implementation of c2p. the only issue is someone will have to host the server 
which is expensive and takes time to manage. I disaggre with ryan. this wasnt a 
gift. it is a reason why i purchased my android phone. when i buy something 
with said feature i expect that the feautre works and is fully supported. 
google lacks big time with their support which is a big reason why things like 
their google apps suite and google docs wont ever be successful. companies can 
not reply on a forum like this to maybe have their issue fixed. this is also a 
big reason why i bet they purchased motorola besides their huge patent 
portfolio. anyhow if someone is generous enough to host a cloud2phone sever 
that would be awesome. i got lucky and found a nandroid backup that had c2p 
working so while i have it working on my phone it is still not working on my 
tablet

Original comment by ddarv...@gmail.com on 18 Aug 2011 at 6:06

[GoogleCodeExporter]

I am also having the same error. When I registered a new gmail account and ran 
chrome2phone with it, it worked. But my old email (used on 3 different devices 
with multiple roms) started failing yesterday.

in logcat i get 

08-20 17:34:27.086  1520  1520 D GoogleLoginService: onBind: Intent { 
act=android.accounts.AccountAuthenticator 
cmp=com.google.android.gsf/.loginservice.GoogleLoginService }
08-20 17:34:27.547  1520  1529 D dalvikvm: GC_FOR_MALLOC freed 6213 objects / 
439680 bytes in 52ms
08-20 17:34:27.570  1520  2664 D NativeCrypto: Freeing OpenSSL session
08-20 17:34:28.531  2282  2662 D dalvikvm: GC_FOR_MALLOC freed 3399 objects / 
433856 bytes in 45ms
08-20 17:34:28.539  2282  2665 D NativeCrypto: Freeing OpenSSL session
08-20 17:34:28.664  2282  2662 W SingleClientConnManager: Invalid use of 
SingleClientConnManager: connection still allocated.
08-20 17:34:28.664  2282  2662 W SingleClientConnManager: Make sure to release 
the connection before allocating another one.
08-20 17:34:29.047  2282  2662 D dalvikvm: GC_FOR_MALLOC freed 3421 objects / 
186072 bytes in 47ms
08-20 17:34:31.219  2282  2662 W DeviceRegistrar: Registration error 500

Original comment by ard...@gmail.com on 20 Aug 2011 at 9:37

[GoogleCodeExporter]

I've been reading around about this issue. I believe that this is an activation 
issue. I have used ChromeToPhone on many roms and now I can't use it. I suspect 
that it is because I have activated this so many times. I know that this was a 
small project and I don't expect a lot of support for this, but please, this 
problem has been around for ages.

I tried to search around my account to try and delete/revoke access but I 
couldn't find anything. I got the same logcat as ard so I do suspect it's an 
activation issue on the servers.

Original comment by jgogg...@gmail.com on 20 Aug 2011 at 10:00

[GoogleCodeExporter]

I've just pushed a fix to the server that hopefully fixes the issues people 
were seeing where they had flashed and wiped device(s) more than 10 times 
without disconnecting Chrome to Phone. Let me know if it's working for folks 
now.

Original comment by burke.da...@gmail.com on 21 Aug 2011 at 12:10

• Changed state: Accepted

[GoogleCodeExporter]

I can activate again!

Original comment by ricardo....@gmail.com on 21 Aug 2011 at 12:12

[GoogleCodeExporter]

Works for me! Thank you!

connect

people

Original comment by njr...@gmail.com on 21 Aug 2011 at 12:16

[GoogleCodeExporter]

Original comment by burke.da...@gmail.com on 21 Aug 2011 at 12:16

• Changed state: Fixed

[GoogleCodeExporter]

Thank you so much!

Original comment by scottym...@gmail.com on 21 Aug 2011 at 12:17

[GoogleCodeExporter]

Not working for me.  Unable to Disconnect.  And why has this taken so long? 

Original comment by griffor...@gmail.com on 21 Aug 2011 at 12:33

[GoogleCodeExporter]

Working for me. Thank you! 

Original comment by sahilsha...@gmail.com on 21 Aug 2011 at 12:38

[GoogleCodeExporter]

Works great for me!

Original comment by kenneth....@gmail.com on 21 Aug 2011 at 12:39

[GoogleCodeExporter]

oooh!!! also working for me! 

One question; if we flash any ROM another 10 times without logging-out of C2P 
it can happen again?

Original comment by danidr...@gmail.com on 21 Aug 2011 at 12:41

[GoogleCodeExporter]

Working now after data wipe.  1 year and 11 days.  Nice work. 

Original comment by griffor...@gmail.com on 21 Aug 2011 at 12:42

[GoogleCodeExporter]

congrats... it finally happened!

Original comment by ddarv...@gmail.com on 21 Aug 2011 at 12:47

[GoogleCodeExporter]

Works! Thanks so much!

Original comment by ryanboeh...@gmail.com on 21 Aug 2011 at 12:55

[GoogleCodeExporter]

Thank you, I use chrome2phone on a daily basis.  Must remember 2 disconnect 
chrome2phone before wiping phone.  

Original comment by wilma...@gmail.com on 21 Aug 2011 at 12:56

[GoogleCodeExporter]

Thank you!

Original comment by cgug...@gmail.com on 21 Aug 2011 at 1:04

[GoogleCodeExporter]

Thank you very much!

Original comment by dellybelly on 21 Aug 2011 at 3:10