Unable to connect after update #114

New Issue

fergalmoran · 2025-08-09T16:57:31Z

fergalmoran commented

2025-08-09 16:57:31 +00:00

Originally created by @GoogleCodeExporter on 1/3/2016

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 the phone being registered for the Chrome to Phone 
features. Instead I get the error message that it's "Unable to connect." 

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

Is the phone using WiFi or mobile network when problem occurs ? If Wifi,
are you behind a firewall that blocks outgoing connections ?
I do have WiFi running and am able to browse the internet via a browser and get 
Gmail messages and any other internet app works. I have also tried on 3G, same 
result.

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


Can you open "Talk" application ? Do you see incoming chats ?
Yes, no problem.


Please provide any additional information below.
Seems to be the same as Issue 158, but since that has the "fixed" status, I am 
opening a new one.



This happened to me after I installed the update of Chrome to Phone 2.3.0.
I was using the app with no problems before the update.


I have logged the app and saw this error:

W/DeviceRegistrar( 7004): Registration error 302

Original issue reported on code.google.com by eddywitk...@gmail.com on 3 Feb 2012 at 11:21

*Originally created by @GoogleCodeExporter on 1/3/2016* ``` 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 the phone being registered for the Chrome to Phone features. Instead I get the error message that it's "Unable to connect." What version of the android, in Settings -> About phone -> Build number ( ex. FRFxx ) ? If less than FRF50 - see the FAQ. Android 2.3.7 GWK74 Is the phone using WiFi or mobile network when problem occurs ? If Wifi, are you behind a firewall that blocks outgoing connections ? I do have WiFi running and am able to browse the internet via a browser and get Gmail messages and any other internet app works. I have also tried on 3G, same result. Can you open "Gmail" application ? Do you see new messages without hitting 'refresh' ? Yes, everything works fine. Can you open "Talk" application ? Do you see incoming chats ? Yes, no problem. Please provide any additional information below. Seems to be the same as Issue 158, but since that has the "fixed" status, I am opening a new one. This happened to me after I installed the update of Chrome to Phone 2.3.0. I was using the app with no problems before the update. I have logged the app and saw this error: W/DeviceRegistrar( 7004): Registration error 302 ``` Original issue reported on code.google.com by `eddywitk...@gmail.com` on 3 Feb 2012 at 11:21

Sign in to join this conversation.

No Label auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated auto-migrated Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Priority-Medium Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect Type-Defect

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: fergalmoran/chrometophone#114