PhoneToChrome

[GoogleCodeExporter]

Enchantment request.

Hi, 

Would it be possible to implement a reverse ChromeToPhone using the same 
C2DM system?

I.E. Use can share link in their device browser with ChromeToPhone. The 
link is added to ChromeToPhone's send queue.
When the user is in Chrome they have a second button for PhoneToChrome, 
when clicked, sends a request to the application server, which in turns 
send a receive message to device. The device then responds to the server 
with the queued share links. The application server then pushes the links 
back to Chrome where they appear in the pop-up box.

Yours,
Paddy

Original issue reported on code.google.com by patrick....@gmail.com on 21 May 2010 at 2:18

[GoogleCodeExporter]

Not a bad idea! It would be similar to the implementation in Google TV

Original comment by UndeadOverlord on 24 May 2010 at 1:43

[GoogleCodeExporter]

It's an interesting idea. For now, we want to finish what we've started and 
create a great Desktop->Mobile 
solution that can be launched to general public.

Original comment by burke.da...@gmail.com on 24 May 2010 at 10:54

• Changed state: WontFix

[GoogleCodeExporter]

Issue 24 has been merged into this issue.

Original comment by burke.da...@gmail.com on 24 May 2010 at 11:06

[GoogleCodeExporter]

Issue 89 has been merged into this issue.

Original comment by costin on 22 Jun 2010 at 11:15

[GoogleCodeExporter]

Awesome - would be great to see this get realized as well.

Original comment by nkya...@gmail.com on 23 Jun 2010 at 2:18

[GoogleCodeExporter]

Phone to chrome would be way more useful to me than chrome to phone!

Original comment by iRtra...@gmail.com on 27 Jun 2010 at 3:10

[GoogleCodeExporter]

I know this idea is shelved for the moment however I have had some further 
thoughts on how it could work.

The bit that I couldn't figure out was returning the link to the browser. As 
documented in Issue 67, C2DM suffers from an intermittent lag of an 
undetermined amount of time. If a browser was to make a request to the server 
and try to keep that connection open while waiting for a reply it could easily 
timeout.
The solution I would propose for this would be to:
- make the phonetochrome request to the server
- the server sends a C2DM request to the phone and then sends an 
acknowledgement to the browser
- the browser and server then open a HTML5 websocket connection
- when the phone sends the links to the server, the server pushes the links 
down the websocket connection and closes the connection.
- the browser then fires a "new links" notification

Original comment by smallroo...@gmail.com on 28 Jun 2010 at 11:18

[GoogleCodeExporter]

Issue 82 has been merged into this issue.

Original comment by costin on 12 Jul 2010 at 10:03

[GoogleCodeExporter]

Issue 105 has been merged into this issue.

Original comment by costin on 12 Jul 2010 at 10:04

[GoogleCodeExporter]

Issue 130 has been merged into this issue.

Original comment by aml...@gmail.com on 31 Jul 2010 at 6:07

[GoogleCodeExporter]

Issue 127 has been merged into this issue.

Original comment by aml...@gmail.com on 31 Jul 2010 at 6:07

[GoogleCodeExporter]

Issue 142 has been merged into this issue.

Original comment by aml...@gmail.com on 2 Aug 2010 at 4:30

[GoogleCodeExporter]

"Android2cloud is the inverse of the very cool Chrome to Phone extension, and 
works in similar fashion."

See: 
http://lifehacker.com/5604248/android2cloud-opens-urls-from-your-phone-in-chrome
.

Original comment by edgar.m...@gmail.com on 4 Aug 2010 at 5:19

[GoogleCodeExporter]

Gonna have to check it out. It's up to the devs but it's be awesome to merge 
the projects.

Original comment by patrick....@gmail.com on 4 Aug 2010 at 5:38

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Yep. Just tried it and seems to work nicely. The project itself is located at 
http://code.google.com/p/android2cloud/.

Original comment by edgar.m...@gmail.com on 4 Aug 2010 at 5:55

[GoogleCodeExporter]

Issue 150 has been merged into this issue.

Original comment by patrick....@gmail.com on 4 Aug 2010 at 7:24

[GoogleCodeExporter]

Issue 156 has been merged into this issue.

Original comment by patrick....@gmail.com on 6 Aug 2010 at 8:55

[GoogleCodeExporter]

Issue 179 has been merged into this issue.

Original comment by aml...@gmail.com on 18 Aug 2010 at 9:38

[GoogleCodeExporter]

Issue 183 has been merged into this issue.

Original comment by aml...@gmail.com on 20 Aug 2010 at 11:32

[GoogleCodeExporter]

So now that C2P has been sorted out and released, could the google devs revisit 
this? 

Original comment by agilm...@gmail.com on 20 Aug 2010 at 11:36

[GoogleCodeExporter]

Issue 189 has been merged into this issue.

Original comment by aml...@gmail.com on 24 Aug 2010 at 7:52

[GoogleCodeExporter]

Issue 190 has been merged into this issue.

Original comment by aml...@gmail.com on 25 Aug 2010 at 7:03

[GoogleCodeExporter]

Issue 201 has been merged into this issue.

Original comment by aml...@gmail.com on 4 Sep 2010 at 2:04

[GoogleCodeExporter]

While chrome2phone is nice, I must say that I actually needed and used it... 
just ONCE.

phone2chrome would be so much more useful, I constantly need it, more or less 
once a day.

I've just read here about Android2cloud, tried it, and it works: great.
But... it has funding problems: 
http://blog.android2cloud.org/2010/09/money-spoils-everything-wholesome.html :(

Just to let you know.

Original comment by looris on 18 Sep 2010 at 12:53

[GoogleCodeExporter]

Issue 228 has been merged into this issue.

Original comment by aml...@gmail.com on 9 Oct 2010 at 9:14

[GoogleCodeExporter]

phone to chrome

Original comment by jckerry1...@gmail.com on 13 Oct 2010 at 6:54

[GoogleCodeExporter]

Issue 237 has been merged into this issue.

Original comment by aml...@gmail.com on 27 Oct 2010 at 12:47

[GoogleCodeExporter]

Issue 238 has been merged into this issue.

Original comment by aml...@gmail.com on 27 Oct 2010 at 5:26

[GoogleCodeExporter]

Why is it closed and a WontFix?

Original comment by F.Nieder...@gmail.com on 12 Jan 2011 at 10:33

[GoogleCodeExporter]

Isn't the Desktop->Mobile solution finished by now?
It would be a great improvement to have a two-way app.

I'd be much more encouraged to look at my Twitter and RSS feeds from my phone 
if I knew I had a way to push long articles to Chrome.

I have the feeling that this app isn't receiving any love...
Could at least this issue be re-open so that third party dev could submit 
patches?

Original comment by jeremy.ngl on 29 Apr 2011 at 10:24

[GoogleCodeExporter]

I have never needed or wanted to use Chrome to Phone. I've never found a 
webpage on my laptop that I needed to take with me on a mobile phone.
However, I regularly have webpages I want to view that for whatever reason do 
not work well with mobile browsers. It would be amazing to have a way for those 
pages to be waiting for me on my PC when I get home.

Chrome to Phone is only a fraction as useful as Phone to Chrome could be.

Original comment by chris3...@gmail.com on 30 Jun 2011 at 7:01

[GoogleCodeExporter]

There already is a Phone to Chrome app in the Android Market

https://market.android.com/details?id=com.lg.valle.phone2chrome

In addition, there are other methods, as well, such as ReadItLater, my personal 
favorite:  http://readitlaterlist.com/

There's an app for this too in the Android Market, and it comes in 2 flavors - 
free and pro:  

Free:  https://market.android.com/details?id=com.ideashower.readitlater.free

Pro:  https://market.android.com/details?id=com.ideashower.readitlater.pro

HTH

Original comment by nkya...@gmail.com on 2 Jul 2011 at 1:50

[GoogleCodeExporter]

There should be a (Google) app capable of doing it in both ways.

Right now you have to install 4 stuff :
1 chrome to phone app + 1 chrome to phone browser extension
+ 1 phone to chrome app + 1 phone to chrome browser extension

For such a "basic" functionality that's just insane!

Original comment by jeremy.ngl on 2 Jul 2011 at 1:56

[GoogleCodeExporter]

Wait, so you want to be able to send things like links, file downloads to your 
phone, which is *NOT* a server, and want to be able to do the reverse, which is 
a good bet that the computer at home you're running is also *NOT* a server, and 
you're complaining b/c the 'basic functionality' is not there?

Last I checked, you need to know *some* sort of information and / or have some 
sort of pre-existing connection to a computer in order to be able to get access 
to it.  I mean, I don't think you can upload to a file sharing site, CNN's main 
servers, twitter, etc. without being *logged in*.

There is your access authentication.  Your gonna need the same thing on your 
phone - else someone else will be able to come along and also send you stuff - 
and that's not kewl.

Original comment by nkya...@gmail.com on 2 Jul 2011 at 2:01

[GoogleCodeExporter]

The Chrometophone app is just (or at least mostly) about sharing links, you 
don't need a server for that. The android app and the chrome extension, both 
being logged to your Google account are already able to push links in one way. 
What would prevent sending links the two ways (phone to chrome *and* chrome to 
phone). I don't see why the other way would require more "logged in" or "access 
authentication" stuff.

Original comment by jeremy.ngl on 2 Jul 2011 at 2:14

[GoogleCodeExporter]

Issue 286 has been merged into this issue.

Original comment by aml...@gmail.com on 5 Jul 2011 at 8:54

[GoogleCodeExporter]

Issue 346 has been merged into this issue.

Original comment by aml...@gmail.com on 30 Jul 2011 at 3:21

[GoogleCodeExporter]

C'mon Google!

Despite not being displayed on the "Issues" tab because of the "Won't fix" 
status, this issue actually *IS* the most starred issue (by far) of all!

The "For now, we want to finish what we've started" explanation given up here 
seems quite deprecated by now...

Any chance on re-opening this issue and giving chrometophone/phonetochrome some 
love?

Original comment by jeremy.ngl on 31 Jul 2011 at 5:17