Closed GoogleCodeExporter closed 9 years ago
i'm still having this problem. anyone figured out a fix for this? i'm on my
4th android phone so maybe thats the problem?
Original comment by corey...@gmail.com
on 29 Jan 2012 at 7:27
Just upgraded HTC EVO to 2.3.5 Chrome 2 phone stopped working after that.
Looking for fix, have uninstalled and reinstalled C2P, reset phone. No luck. I
really loved this app makes life much easier. Any ideas? Thanks
Original comment by david.01...@gmail.com
on 30 Jan 2012 at 3:31
An on-going problem for me. Thunderbolt running Skyraider 1.3. I have rebooted,
uninstalled, cleared data etc in various combinations.
Original comment by steven.c...@gmail.com
on 3 Feb 2012 at 2:49
Since I installed the new update for Chrome to Phone today, I get the "Error:
Can't connect" error and I a not able to use the app any longer.
In the logs, I see this:
W/DeviceRegistrar( 7004): Registration error 302
Please fix!
Original comment by eddywitk...@gmail.com
on 3 Feb 2012 at 9:47
Same here. Happened after I changed firmware also. I wonder if the limit of
devices on your chrome account is still not being reset properly. Still waiting
on a solution.
Original comment by email.do...@gmail.com
on 3 Feb 2012 at 10:39
Since this issue is stated "FIXED" - which it clearly is NOT - I opened a new
issue here: http://code.google.com/p/chrometophone/issues/detail?id=423&sort=-id
Original comment by eddywitk...@gmail.com
on 4 Feb 2012 at 3:07
Another point of interest: The first time I started the app. during the
configuration steps (as opposed to the market-installation) it asked me for
access-rights to my Google account (after I selected my main Google account). I
accidentally clicked "deny". Now I get the "cannot connect" instead where I
previously got the access rights request (clearing cache, re-installing both
chrome and telephone app did not help).
Additionally I can confirm that the issue is indeed Google-account related, as
I can connect to my girlfriends account (after adding her account it to my
phone) without any issue.
Original comment by woost...@gmail.com
on 4 Feb 2012 at 7:29
Unable to connect: here.
Original comment by daniel@staticfish.com
on 5 Feb 2012 at 8:09
NOT FIXED, since the latest update the error is back.
Original comment by cole...@gmail.com
on 8 Feb 2012 at 11:51
Unable to connect on Samsung Droid Charge running stock Gingerbread.
Original comment by djmike0...@gmail.com
on 8 Feb 2012 at 1:32
Tested this morning. Was able to connect with a secondary account. My primary
account could not connect.
Tried uninstalling, rebooting then install and tried to connect using primary
account (did not move it to sd card). Still no luck. (Secondary account is
working tho!)
LG Ally, Froyo...
Original comment by jimmy.da...@gmail.com
on 8 Feb 2012 at 7:21
Motorola Droid X
Android 2.3.3 System version 4.5.605.MB810
Chrome to Phone for android 2.3.0
Android device is not rooted.
Unable to connect error using primary [only] account.
Chrome to phone extension installed on Chrome 17 stable build and signed in
All other Google account services connect to phone without issue.
Forced app stop and cleared app data. No effect.
Reset system cache. No effect.
Original comment by mrmar...@gmail.com
on 12 Feb 2012 at 3:02
[deleted comment]
As posted by someone in issue 423:
A workaround - at least for me - was changing my Google password (now hoping
Google will pick it up from here, and this info helps solving the root cause
for all users).
Original comment by woost...@gmail.com
on 13 Feb 2012 at 10:58
Changing password definitely works
Original comment by daama...@gmail.com
on 15 Feb 2012 at 9:09
create a second google account, configured chrome to phone for this one,
removed it and the primary account re-works again!
Original comment by max.licc...@gmail.com
on 16 Feb 2012 at 10:07
Droid X. Same error. No solution.
Original comment by natgr...@gmail.com
on 17 Feb 2012 at 1:34
This app sucks! Better use AirDroid instead
https://market.android.com/details?id=com.sand.airdroid
Original comment by boedim...@gmail.com
on 18 Feb 2012 at 4:34
AirDroid isn't as simple as Chrome to Phone, and also isn't better than Webkey.
We (I) like a simple + useful PC-Browser to Phone link sender, not a full site,
with contracts, file manager, logins, sms...program...and for that purpose, we
have Webkey, better than AirDroid, more useful, free and open source.
Original comment by danidr...@gmail.com
on 18 Feb 2012 at 1:53
Guys,please try change Google password in PC
Should able to resolve the issue
Original comment by fung.har...@gmail.com
on 18 Feb 2012 at 2:06
Guys,please try change Google password in PC
Should able to resolve the issue
Original comment by fung.har...@gmail.com
on 18 Feb 2012 at 2:07
On my device it doesn't work either. About a month or so it just began to show
"unable to connect"
Device MTC 916 (ZTE Racer)
Android 2.3.5 (CM)
Original comment by SeregaKr...@gmail.com
on 19 Feb 2012 at 9:20
If you're using Two-Way-Auth try to revoke your app-specific password and
generate a new one. Android should ask for a new password. Works for me.
Original comment by jsta...@gmail.com
on 20 Feb 2012 at 6:34
I had to do a reset to factory settings on my Samsung Galaxy 2 (Epic 4G Touch
on Sprint) and when I reinstalled Chrome to Phone on the phone, it had this
same issue.
Restarting the phone fixed it though.
Original comment by heisen...@gmail.com
on 20 Feb 2012 at 7:37
[deleted comment]
Was going through options just for other people's sanity.
Wiped phone, installed new rom without logging out of C2P. Re-installed C2P,
got error. Uninstalled, re-installed, same error. Rebooted phone, logged right
in.
Probably won't work for everyone, as I see many restarted and wiped cache. But
for those that haven't rebooted the phone... it's rule #1 in the desktop
support, and may as well be in the phone support.
Original comment by ludici...@gmail.com
on 23 Feb 2012 at 4:13
It worked perfectly for me but I had to hard reset my phone because of another
issue. Now after re-installing I cant log in.
Original comment by Tysonio...@gmail.com
on 2 Mar 2012 at 8:41
Comment 220 Solved my issue!
Thanks so very much..after three months of "can't connect" simply changing
password for Google account solved it.
Thank you!!!!!!!
Original comment by parke...@gmail.com
on 5 Mar 2012 at 4:00
I have two accounts on the phone, one of which (the first one) doesn’t have
correct password (I don’t use it, cause it is my wife’s account, and she
already has another phone — but I unfortunately can’t delete it without
resetting phone to factory defaults). So I mainly use my own account, which is
the 2nd one on the phone. This 2nd account can’t ever connect to
chrometophone extension. I just tried to change my google password — didn’t
help.
Original comment by stansult
on 5 Mar 2012 at 6:58
Comment 220, Thank you!
Original comment by shinya.k...@gmail.com
on 6 Mar 2012 at 1:44
Rebooted phone and pulled battery - no improvement. Changed Google Password -
no improvement. Chrome to Phone still not working - Google Talk now cannot
synch and as it a pre-installed app cannot be removed either. HTC Wildfire.
Original comment by garydym...@gmail.com
on 10 Mar 2012 at 12:34
This isn't fixed. I can't connect using my primary gmail account. I can
connect with no problem using my wife's and my joint gmail account. This is
not optimal, as I'm not normally signed in to that account in my browser. Come
on, Google, fix this for real. Can the OP mark this as not fixed, or does a
project member have to do so?
Original comment by jmcr...@gmail.com
on 25 Mar 2012 at 3:17
For anyone with 2-step authentication who is having this problem, I was able to
fix it by changing my application-specific password for Android on this page:
https://accounts.google.com/IssuedAuthSubTokens
Original comment by dherber...@gmail.com
on 25 Mar 2012 at 5:21
Changing my Google password resolved the issue. SGS with Android 2.3.6
Original comment by dag.ronn...@gmail.com
on 31 Mar 2012 at 7:42
Google, what's up? I see nothing in this huge string of posts about how to
correct this issue from you. I'm having the same issue. It appears to be a
common problem. I don't want to reset my Google password. What gives???
Original comment by jennifer...@gmail.com
on 11 Apr 2012 at 6:21
Changing my pass for google account works fine.
Original comment by zduder...@gmail.com
on 1 May 2012 at 8:03
I have no idea what the problem is, but uninstalling Chrome-to-Phone and
re-installing it fixes it.
Original comment by dbul...@gmail.com
on 1 May 2012 at 7:46
HTC evo 4g on gingerbread and rebooting fixed the issue which was strange
because it was a fresh install after a factory reset and it gave the unable to
connect error. Looks like doing a full reboot with the app installed fixes.
Original comment by WINKLEMA...@gmail.com
on 7 May 2012 at 5:58
I just managed to fix this for my phone by doing the following:
1) Start from the Home Screen
2) Menu -> Settings
3) Accounts
4) Select your Google account
5) Check "Sync Instant Upload" (in my case it was unchecked)
6) Go back to Chrome-to-Phone and it worked on the first try.
I hope this helps others.
Original comment by benjamin...@gmail.com
on 19 May 2012 at 7:21
The only work around I have found for this is to change my Google password and
then launch Chrome to Phone. It will then ask for a new password but this is a
pain to be able to get it working again.
Original comment by joshpeck...@gmail.com
on 22 May 2012 at 3:01
[deleted comment]
Still not working for me, I have two g mail accounts and can only link one of
them. The other gets unable to connect message. unfortunately its the one i
wanted to use chrome to phone with.
Original comment by JerseyBe...@gmail.com
on 3 Jun 2012 at 2:12
changing the password worked for me
Original comment by arunchek...@gmail.com
on 30 Jun 2012 at 1:03
i have tried each and every suggestions provided above, changing password,
trying another account, sync google in settings, etc etc.. but unfortunately
it still showing unsuccessful login on my phone. :(
Original comment by 9ansh...@gmail.com
on 3 Aug 2012 at 8:58
changing pass aplications pass worked for me
Original comment by spike...@gmail.com
on 8 Aug 2012 at 3:06
[deleted comment]
changing password worked for me.
Original comment by bisscuitt
on 13 Aug 2012 at 4:40
No need to change your password on your main Google account. I went to my
security settings and setup 2 Step Verification and set a password for Chrome
to Phone and it works now. Hope this helps.
Original comment by jason.sh...@gmail.com
on 17 Aug 2012 at 3:28
Firefox.
Original comment by Donald.J...@gmail.com
on 6 Sep 2012 at 1:31
Just throwing out my idea:
Anybody tried Safe Mode here?
It reacts differently on my phone:
It keeps on showing "Connecting.." forever after pressing the "Next" button,
like for a half an hour. (I just felt like this wouldn't do anything so I
stopped here. It might have made any change in next one second..)
The part the App having me wait for that long is different because it only
takes around 10 seconds to show "Error: Unable to connect" when it's not
running on Safe Mode.
f.y.e:
After that 30 minutes of waiting for (at least seemingly)nothing, I let it go
back to the home screen, then re-opened the App to try the same thing again,
but it showed me "Connecting.." screen still on going instead of asking me to
press "Exit" or "Next" button. I wanted to shut down the App for once, so I
checked the running app list (Settings>Applications>Manage
Applications>Running) but "Chrome to phone" was not there.
Rebooting finally let the App ask me to do the same connecting process, but it
just acts exactly the same. One thing that went differently was that, right
after opening the App, it showed me "History" screen in a very very brief
moment(like 1/4 sec.)), then it switched to the same screen I see every time.
Spec etc.
htc evo 4G(on Japanese carrier: KDDI)
Android 2.3(not rooted)
Safe Mode: done by pressing on "Vol:Down" button while it says on the wake up
screen that "htc -quietly brilliant"
Gmail apps were running and working just fine(; I got mail notification too)
either on Normal Mode or Safe Mode.
In the end I just decided not to get bothered by not "Connecting" instead of
just tap on "Go Back" button and check "History".
Having said that, I hope anyone who knows the stuff better gets some idea about
solving this thing..
Original comment by conwell....@gmail.com
on 29 Sep 2012 at 3:13
Original issue reported on code.google.com by
kent7...@gmail.com
on 9 Aug 2010 at 1:39