Closed GoogleCodeExporter closed 9 years ago
What version of Chrome on what OS?
What happens after "Sending link to phone"? Does it just hang or is a message
displayed?
Version number of the Android app can be found in
Settings->Applications->Chrome to Phone. Don't intend to
iterate the version number until launch (currently folks are trying builds from
tip of tree as this is still being
developed...).
Original comment by burke.da...@gmail.com
on 24 May 2010 at 10:44
Chrome browser version: 6.0.408.1 (Official Build 47574) dev (running on linux
goobuntu)
ChromeToPhone version: 1.0
When I first filed this issue, the behavior was that the pop-up would just hang
while
displaying "Sending link to phone..."
Now it sometimes succeeds. The success rate is around 70% now.
Maybe there was some backend latency of an hour or so in getting my device
registered? If so, that should be documented and there should be a way to check
on
the current status during the "wait for registration" period.
Original comment by jim...@google.com
on 24 May 2010 at 10:50
Nothing is working for me either - and no error message.
When I click on the extension icon the dropdown says "Sending link to phone..."
for
about one second and then changes to "Link sent to phone.". As soon as I click
on
anywhere else in the chrome browser, that dropdown disappears.
Nothing appears on the phone. Logcat does not show anything at all either so it
looks
like nothing is reaching the phone at all. Note - I'm connected via wifi and
can
happily use the Maps application in the normal way.
Chrome: 4.1.249.1064 (45376)
ChromeToPhone: 1.0.0
Original comment by mjc1...@gmail.com
on 25 May 2010 at 8:26
Found the problem: Since I updated to Froyo, I noticed my Market downloads were
no
longer working - they would just hang without ever starting.
So I did a factory reset I now both the Market downloads and this ChromeToPhone
app now
work!
Original comment by mjc1...@gmail.com
on 25 May 2010 at 9:27
Original comment by burke.da...@gmail.com
on 25 May 2010 at 11:48
Would be good to run some in-app check to see if Google Sync (I assume that is
what the
problem was) is broken in some way and then warn the user accordingly - because
its
really not obvious at all.
Original comment by mjc1...@gmail.com
on 25 May 2010 at 12:26
Original issue reported on code.google.com by
jim...@google.com
on 24 May 2010 at 5:20