Chrome to Phone - LONG Delay #103

New Issue

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

fergalmoran commented

2025-08-09 16:57:10 +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. Go to any website
2. Sent with Chrome to Phone

What is the expected output? What do you see instead?
1. I expect to have the site sent to the phone within seconds( or maybe 1 min 
tops )

2.) What I see is most times it takes 5 - 15 minutes, or sometimes doesn't send 
at all.


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

Using Blazer 4.1 ROM ... But this also happens on the stock kernel with the 
Epic 4G Touch on Sprint

Is the phone using WiFi or mobile network when problem occurs ? If Wifi,
are you behind a firewall that blocks outgoing connections ?

Using WIFI, no firewall ... it's a local home connection


Can you open "Gmail" application ? Do you see new messages without hitting
'refresh' ?

Yes

Can you open "Talk" application ? Do you see incoming chats ?

I don't have the "Talk" application


Please provide any additional information below.

Sometimes signing out of Chrome to Phone and back in, then uninstalling and 
reinstalling the app on my Samsung Galaxy 4G Touch will resolve the issue for a 
little while, and I'll get the sends within 5 - 10 seconds( which is awesome! ) 
... But the issue always comes back after an hour or two

Original issue reported on code.google.com by AYapejian on 4 Mar 2012 at 5:34

*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. Go to any website 2. Sent with Chrome to Phone What is the expected output? What do you see instead? 1. I expect to have the site sent to the phone within seconds( or maybe 1 min tops ) 2.) What I see is most times it takes 5 - 15 minutes, or sometimes doesn't send at all. What version of the android, in Settings -> About phone -> Build number ( ex. FRFxx ) ? If less than FRF50 - see the FAQ. Using Blazer 4.1 ROM ... But this also happens on the stock kernel with the Epic 4G Touch on Sprint Is the phone using WiFi or mobile network when problem occurs ? If Wifi, are you behind a firewall that blocks outgoing connections ? Using WIFI, no firewall ... it's a local home connection Can you open "Gmail" application ? Do you see new messages without hitting 'refresh' ? Yes Can you open "Talk" application ? Do you see incoming chats ? I don't have the "Talk" application Please provide any additional information below. Sometimes signing out of Chrome to Phone and back in, then uninstalling and reinstalling the app on my Samsung Galaxy 4G Touch will resolve the issue for a little while, and I'll get the sends within 5 - 10 seconds( which is awesome! ) ... But the issue always comes back after an hour or two ``` Original issue reported on code.google.com by `AYapejian` on 4 Mar 2012 at 5:34

fergalmoran referenced this issue

2025-08-09 17:45:40 +00:00

chometophone chome extention missing #386

fergalmoran referenced this issue

2025-08-09 17:47:03 +00:00

cant find chrome to phone #389

fergalmoran referenced this issue

2025-08-09 17:47:35 +00:00

Chrome Extension "Not Found" #390

fergalmoran referenced this issue

2025-08-09 17:52:02 +00:00

Chrome to Phone Extension Missing from Extension Page #399

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 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

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: fergalmoran/chrometophone#103