initially worked - now nothing

[GoogleCodeExporter]

What steps will reproduce the problem?
1. installed the chrome extension & the N1(froyo) app
2. worked the 1st day everything was installed
3. couple of days later, nothing working, even after re-registering, 
uninstalling/reinstalling both on chrome and from Nexus one.  Also tried the 
firefox extension and still a no-go. 

Original issue reported on code.google.com by bdavis313 on 2 Jun 2010 at 2:45

[GoogleCodeExporter]

In access.log, I see last message on [01/Jun/2010:21:37:27 -0700], ID: 
id=0:1275453447463872%4af25f24f2615a23

So it seems extension and appengine are working fine. I'll investigate the 
other side.

I assume you're using the same account on the phone as you used to report the 
bug.

Original comment by costin on 2 Jun 2010 at 5:28

• Changed state: Started

[GoogleCodeExporter]

Could this be related to Issue 67? There may be an underlying issue with C2DM 
and 2.2 thats causing this.

Original comment by patrick....@gmail.com on 10 Jun 2010 at 2:26

[GoogleCodeExporter]

I have the same issue, I've used with 2 different computers on different 
networks, and still nothing, it only worked the first day, the first time came 
in quick then last couple times on the first day it lagged by 10 mins now I get 
nothing at all after uninstalling/reinstalling and disconnecting internet as 
well so is not connected to Issue 67

Original comment by davgriff...@gmail.com on 10 Jun 2010 at 2:00

[GoogleCodeExporter]

just reinstalled n1 app again for a 3rd time to day and just received what I've 
been trying to send it, looks like a slight bug in the android app, let you 
know how it works tomorrow

Original comment by davgriff...@gmail.com on 10 Jun 2010 at 2:04

[GoogleCodeExporter]

I have to continuously uninstall and reinstall N1 app, for this to work, once 
it installs everything floods in 

Original comment by davgriff...@gmail.com on 11 Jun 2010 at 7:19

[GoogleCodeExporter]

I am having the same problem as well. I have updated apps for both N1 and 
chrome and have even wiped my phone, still nothing. still getting

Error sending to phone: ERROR (Unable to send link)

Original comment by DCpl...@gmail.com on 1 Jul 2010 at 8:30

[GoogleCodeExporter]

I just wiped my phone and installed the newest CM 6.0-alpha1 and then 
reinstalled this and it now works!

Original comment by DCpl...@gmail.com on 4 Jul 2010 at 12:53

[GoogleCodeExporter]

same here...it never sends the links... and then an hour later they come 
flooding in all at once

Original comment by buddy88...@gmail.com on 12 Jul 2010 at 12:56

[GoogleCodeExporter]

I'm having the same problem with my EVO. I am rooted and running Fusion 2.3 
custom rom (2.2 Froyo stock kernel). When I installed the program it worked ok 
although it took a few minutes for the link to actually get to the phone. Now 
it does not work at all.

Original comment by robne...@gmail.com on 12 Aug 2010 at 11:28

[GoogleCodeExporter]

I am having a similar issue : I am using HTC Desire with Android 2.2 (Froyo). 
It used to work, from Chrome to phone 1.6 to 1.7 with the Firefox extension 
Send To Phone... until recently, for an unknown reason, he says my phone needs 
to have the Chrome To Phone package installed. 

But it is alreayd installed and my account should be syncronised since it is 
there and has been working a few days before. Now he would simply tell me to 
install the Chrome To Phone package when it is already installed. And I am 
logged in with my phone's GMail account. 

Feel free to ask me for more information if I have not provided enough. 

Original comment by thomlottmann@gmail.com on 13 Aug 2010 at 10:33

[GoogleCodeExporter]

Also experiencing the same problem. Signed in to Google running Dolhin Browser 
and Google Chrome installed on my Htc Hero running custom rom Froyo 2.2.
No links have been sent after installing a few hours ago

Original comment by davrave46@gmail.com on 13 Aug 2010 at 10:48

[GoogleCodeExporter]

same issue here, it worked for a few weeks but after reinstall of both 
components nothing is happening at all. modaco r8 (froyo) htc desire

Original comment by zombie...@gmail.com on 27 Aug 2010 at 9:29

[GoogleCodeExporter]

same issue here, worked fine for a month or so, now doesnt work any more - open 
desire rom on desire

Original comment by nfors...@gmail.com on 13 Sep 2010 at 7:46

[GoogleCodeExporter]

worked fine for a few months, and now nothing when upgraded both components to 
2.0.0

Original comment by saama...@gmail.com on 14 Sep 2010 at 8:20

[GoogleCodeExporter]

Could you try on a new chrome profile ( or on a different machine ) ? 

Original comment by cos...@google.com on 15 Sep 2010 at 12:04

[GoogleCodeExporter]

Tried on three different browsers with chrome, nothing worked. I'm using 
nightly CM6, so maybe it's a problem with my phone. Are there any logs?

Original comment by saama...@gmail.com on 15 Sep 2010 at 1:54

[GoogleCodeExporter]

Issue 202 has been merged into this issue.

Original comment by costin on 15 Sep 2010 at 7:57

[GoogleCodeExporter]

same issue. After i updated my rom, chrome to phone stopped working. I'm now 
running SkyRaider 3.0, i have installed the latest chrome and chrome to phone 
app on my phone.  Someone said it's because i didn't disconnect the phone on my 
old rom.. is this true and is there a way to fix it?

Original comment by albli...@gmail.com on 15 Sep 2010 at 11:11

[GoogleCodeExporter]

I'm using chrometophone with both Firefox (latest public build) and Chrome Dev. 
After the latest update of chrometophone on my Droid (stock 2.2) the phone 
force closes every time I send a link to it (from either chrome or Firefox).

I've tried uninstalling/reinstalling everything, nothing seems to work.

Original comment by schleppy on 16 Sep 2010 at 3:44

[GoogleCodeExporter]

Logcats ? 

Original comment by costin on 16 Sep 2010 at 4:13

[GoogleCodeExporter]

i got an update to chrome to phone 2.1 yesterday. Now it works!

Original comment by albli...@gmail.com on 16 Sep 2010 at 5:48

[GoogleCodeExporter]

Same error here. It worked with the 2.0 Version of Chrome to Phone. After the 
update it doesn't send any links. Also turning back to 2.0 didn't fix this. It 
seems that my google account isn't conneced. When I try to disconnect my 
account in the app I get an "Error: Unable to disconnect". I will post a log 
later.

Original comment by Jakob.Ch...@gmail.com on 18 Sep 2010 at 7:05

[GoogleCodeExporter]

I too am running Cyanogen 6, I am unable to get anything on the phone now, i 
think i have too many instances of device ids or something of that nature since 
im testing new builds frequently maybe old stuff is in the cloud, i am unable 
to push anything to my phone now, a manual way to reset everything fresh would 
be nice.

Original comment by Rainfox....@gmail.com on 20 Sep 2010 at 10:02

[GoogleCodeExporter]

I have the same problem, and none of the fixes here work.  Also: When I look at 
my Google account's list of authorized sites, I don't see Chrome to Phone 
listed there anymore.  Could this be related?

Original comment by Chad.Hae...@gmail.com on 20 Sep 2010 at 8:23

[GoogleCodeExporter]

Same issue. Works fine initially, then the links came over minutes later. Now 
nothing is working. Use the newest Chrome+Extension and a Desire with newest 
Extension.

Original comment by killerby...@gmail.com on 22 Sep 2010 at 7:56

[GoogleCodeExporter]

I have have uninstalled --> reinstalled chrome on my desktop, wiped everything 
on my phone ( HTC EVO 4G ) , fresh everything with google account 
rainfox.wolfstone@gmail.com tried sending http://news.google.com/ to phone , 
nothing happens on phone, is there something stuck on the google side of 
things?, I love this feature wish i could get it working again.

Original comment by Rainfox....@gmail.com on 22 Sep 2010 at 2:59

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Also same issue. Worked when I first installed it and now nothing happens. I 
tried to uninstall both on phone and chrome, tried with Firefox, tried to clear 
the davik cache, still doesn't work. 

Original comment by incon...@gmail.com on 22 Sep 2010 at 3:07

[GoogleCodeExporter]

Same here, don´t understand why they relese this, it´s like a beta

Original comment by asl.sthlm08@gmail.com on 22 Sep 2010 at 8:04

[GoogleCodeExporter]

I tried after doing a clean install and it still didn't work. It did however 
work with another gmail account. I think the links are being sent somewhere in 
limbo after trying to connect to the same account multiple times?

Original comment by incon...@gmail.com on 23 Sep 2010 at 3:38

[GoogleCodeExporter]

I made a log file.
I downloaded chrome to phone from the market, connected my account and tried to 
send a link. Nothing worked so I disonnected my account.

I hope the log helps.

Original comment by Jakob.Ch...@gmail.com on 23 Sep 2010 at 11:54

Attachments:

• log.txt

[GoogleCodeExporter]

What I found so far: the problem seems to be on chrome and extension side. 
Someone who had this problem was able to fix it by starting chrome with a clean 
profile. 

Could people who have this problem try:
- run chrome with a new profile ( on linux: --user-data-dir=/tmp/mydir - the 
dir must be created, not sure about other OSes)
- try a different computer, maybe a different version of chrome 
- maybe try in firefox, with the firefox chrome to phone extension

If any of this helps - please update the bug, and include details about the 
version of chrome where it wasn't working and one where it worked.

Also good to know if this was a fresh install or an upgrade.

Original comment by costin on 23 Sep 2010 at 5:15

[GoogleCodeExporter]

I have the feeling there are diffrent problems described in this Thread, mine 
would be similar to those:

I have a HTC Desire 2.2.
Chrome to Phone worked with Foxtophone. 
I had to do a Factory reset (becouse of some other problems), after that 
foxtophone said that links were sent but i didnt receive anything on the phone.

I tryed to use Official Chrome to phone with a fresh installion of Chrome on 
the PC,still same problem.
I deleted app data on the Phone, didnt help.
I reinstalled app on Phone, didnt help.
Tryed to use it with foxtophone again, also didnt work.
The only thing i didnt try is to do factory reset again.

I have the feeling the links are beeing send, but to the id of my phone which 
was registred before the factory reset.

Is there a way to reset or to delete the phones registerd in googles servers? 
Does anyone know how Chrome to phone reacts in case u have more than one mobile 
with the same account?

Feel free to ask me questions, if i missed to write some kind of important 
information.

Original comment by saraj.as...@gmail.com on 23 Sep 2010 at 8:25

[GoogleCodeExporter]

Yes, a factory reset will give the phone a new ID. The extension is sending 
messages - but they're targeted to the old identity of the phone. 

What happens when you open the ChromeToPhone app on the phone ? Does it show up 
as registered ? If yes, can you unregister and register again ? This should 
create a new registration id.

Maybe we should add some web tool to help debugging - like a servlet to show a 
user's registration and allow sending a URL from the web.  

Original comment by cos...@google.com on 23 Sep 2010 at 8:51

[GoogleCodeExporter]

how would you unregister? it I can disconnect my phone, but that doesn't change 
anything. Still doesn't work.

Original comment by incon...@gmail.com on 23 Sep 2010 at 8:59

[GoogleCodeExporter]

I also made a factory reset. When I start the app, it doesn't show that I'm 
connected. I can connect my phone but it doesn't work. Also if I disconnect and 
connect again nothing changes.

Original comment by Jakob.Ch...@gmail.com on 23 Sep 2010 at 9:01

[GoogleCodeExporter]

It works now!! Had to open it up on the Droid and hit disconnect then re-add 
and now it works... 

Original comment by JESSEB.MAIL on 23 Sep 2010 at 10:06

[GoogleCodeExporter]

thx for the fast rply. 

I can register and unrigister my phone, but i still cant receive any messages.
btw i forgot to mention that talk and mail are working normaly.

Original comment by saraj.as...@gmail.com on 23 Sep 2010 at 10:07

[GoogleCodeExporter]

And you updated from the market and Chrome Extensions site? I did not know 
about the updates. 

Original comment by JESSEB.MAIL on 23 Sep 2010 at 10:13

[GoogleCodeExporter]

I would uninstall all C2P from the Chrome and the phone. Then install for 
Chrome then install for phone and see if it works. Just thinking out loud.. 

Original comment by JESSEB.MAIL on 23 Sep 2010 at 10:16

[GoogleCodeExporter]

I deinstalled all C2P from phone and chrome, i even deinstalled chrome now. 
Then installed Chrometophone app and after that Chrome plug in. Also i 
disconnechted and connected the Phone app about 5 times after that but it still 
dosnt receive anything. 

The strange thing is there is no error. The phone app says everything is fine 
and so does the plug in.

Original comment by saraj.as...@gmail.com on 23 Sep 2010 at 10:32

[GoogleCodeExporter]

Sent this to the list instead of the bug:

Jakob ( or anyone else experiencing this problem and with a SDK around) : could 
you also:
- "adb shell setprop log.tag.C2DM VERBOSE"
- disconnect / connect 
- grab an "adb logcat" and upload it  ? 

I also want to confirm that when you click the extension you see a small pop-up 
with "Sending link to phone" - if not this is a chrome/extension problem.

Original comment by costin on 23 Sep 2010 at 11:18

[GoogleCodeExporter]

I know at least for me it's not a chrome/extension problem since it works with 
I link it to another account, just not my original account. I had also done a 
factory reset.

Original comment by incon...@gmail.com on 24 Sep 2010 at 2:04

[GoogleCodeExporter]

Factory-reset my phone to test it - added the initial account, installed c2p 
app again, it asked me for an account - than all worked.

Anything you did differently ? Did you go trough registration again, after the 
factory reset ? Was the c2p app re-installed manually or did you get it from 
backup or did you have it on sdcard ? 

The normal behavior: 
- factory reset will wipe the /data partition - including the c2p settings
- you will also get a new phone ID
- you must register with c2p. If c2p thinks it's still registered ( i.e. 
doesn't show the initial screen ) - something was wrong with the factory reset. 
- workaround should be to register/unregister again - this should put all in a 
good state

Original comment by costin on 24 Sep 2010 at 9:45

[GoogleCodeExporter]

After factory reset App asked for account.It wasnt registerd after reset. I 
installed the app from the market. I tryed ur suggestion for the workaround 
like 20 times now. I still cant receive anything.

Do i rly have to do facktory reset again to bring c2p back to life?

Original comment by saraj.as...@gmail.com on 24 Sep 2010 at 10:57

[GoogleCodeExporter]

Saraj: I see one registration record in the c2p database, timestamp is 9/19. 

Do you have 'adb' ( android SDK ) ? If yes, see comment #42. 

No, another factory reset won't help - we need to be able to repro the problem 
and to fix it. 

Original comment by cos...@google.com on 24 Sep 2010 at 11:43

[GoogleCodeExporter]

I tried this adb thing and now it works again. Let's see how long.
I was connected according to the app. Then I typed in the adb thing, opened the 
app and tried to disconnect. I got an error that disconnecting is not possible. 
I tried to disconnect again and then it worked. I closed the app and stated it 
again, connected and after that I can receive links again. Thanks!

Here's the log from adb logcat.

Original comment by Jakob.Ch...@gmail.com on 25 Sep 2010 at 2:13

Attachments:

• log.txt

[GoogleCodeExporter]

I also tried the adb thing and it worked for me as well. Thanks!

Original comment by incon...@gmail.com on 25 Sep 2010 at 9:46

[GoogleCodeExporter]

that fixed mine too, i wonder what that changes by doing this command
- "adb shell setprop log.tag.C2DM VERBOSE"

it looks just like im telling it to make a log, how would this change the 
outcome of what happens , but it did , it fixed it for now, hope this lasts (-: 
did not get a log of what happened since the phone restarted right after i did 
that.

Original comment by Rainfox....@gmail.com on 26 Sep 2010 at 11:14

[GoogleCodeExporter]

Thanks for the help - the bug was on server side, Dave pushed a new build of 
the server yesterday. 
No magic in setting the C2DM log to verbose - you can see the code affected by 
that flag in the chrometophone sources, it's jost for printing more logs. 

For people affected by this: unregistering/registering again should solve the 
problem. No need to reinstall the app. If it still doesn't work - please update 
the bug. 

Note that this fix is for the case where the chrome extension is working - i.e. 
you get asked to login, and you see a popup when the message is sent. 

Original comment by costin on 26 Sep 2010 at 4:00