Author Topic: What devices are you running Web orbiter 2.0 on? (Read 102121 times)

Viking · « **Reply #105 on:** August 30, 2010, 04:42:18 pm »

Quote from: maverick0815 on August 15, 2010, 07:46:55 pm

has anyone tried it on the htc hd2? So far no matter what resolution I put (currently n770) it never fits on the screen. Opera always zooms in...if I zoom out again, I can see that there is some cropping on the right side too.

Hi,

On my HTC desire I had to set zoom to "far away" (or something like that as my HTC is danish) in the browser settings to show it full screen.

Viking

totallymaxed · « **Reply #106 on:** August 31, 2010, 08:05:47 am »

Quote from: Viking on August 30, 2010, 04:42:18 pm

Quote from: maverick0815 on August 15, 2010, 07:46:55 pm
has anyone tried it on the htc hd2? So far no matter what resolution I put (currently n770) it never fits on the screen. Opera always zooms in...if I zoom out again, I can see that there is some cropping on the right side too.
Hi,

On my HTC desire I had to set zoom to "far away" (or something like that as my HTC is danish) in the browser settings to show it full screen.

Viking

It would be useful if device/browser specific work around's or tips were added to a device/browser section of the Web Orbiter 2.0 wiki page http://wiki.linuxmce.org/index.php/Web_Orbiter_2.0 for others to take advantage of.

All the best

Andrew

Viking · « **Reply #107 on:** August 31, 2010, 08:40:27 am »

They already were

but mostly noone looks there - easier to ask ...

http://wiki.linuxmce.org/index.php/Web_Orbiter_2.0#Google_Nexus_One_or_HTC_Desire_.28Android.29

totallymaxed · « **Reply #108 on:** August 31, 2010, 10:45:41 am »

Quote from: Viking on August 31, 2010, 08:40:27 am

They already were but mostly noone looks there - easier to ask ...

http://wiki.linuxmce.org/index.php/Web_Orbiter_2.0#Google_Nexus_One_or_HTC_Desire_.28Android.29

Yeah...including me ;-)

My comment was not really aimed at you but was a more general one to anyone reading this thread.

All the best

Andrew

Viking · « **Reply #109 on:** August 31, 2010, 09:26:25 pm »

No problem

Thanks for doing a good job in helping others here

Viking

phenigma · « **Reply #110 on:** September 04, 2010, 09:43:06 pm »

Seems to work well in Opera on the WebDT 366. Sucks to need a keyboard to login all the time. Not quite as responsive as the padOrbiter but pretty good. Not showing elapsed track time display in the remote screen.

J

totallymaxed · « **Reply #111 on:** September 05, 2010, 11:33:59 am »

Quote from: phenigma on September 04, 2010, 09:43:06 pm

Seems to work well in Opera on the WebDT 366. Sucks to need a keyboard to login all the time. Not quite as responsive as the padOrbiter but pretty good. Not showing elapsed track time display in the remote screen.

J

Performance would be improved by porting Touch Orbiter to the WebDT 366. Anyone up for that? ;-)

All the best

Andrew

purps · « **Reply #112 on:** September 06, 2010, 10:41:32 am »

Can I just ask; is there a way to change the default room on the web orbiter? Whenever I open the orbiter, it seems to default to "Closet" (I assume because it's the first in the list of rooms alphabetically?) - can I change it to "Living Room" for example?

Or another suggestion/question, could it be set up to display the room selection screen first, so that you can choose? This would be useful for my mobile phone, as I could be anywhere when I use that.

MarcoZan · « **Reply #113 on:** September 06, 2010, 12:18:27 pm »

Hi Purps

I think the default room is the one where core/hybrid is located as the proxy orbiter is a core device.

Nevertheless it would be nice to be able to define the "starting room" for each instance of web orbiter, but so far I could not find a way to do it.

Regards.
Marco

totallymaxed · « **Reply #114 on:** September 06, 2010, 03:49:42 pm »

Quote from: purps on September 06, 2010, 10:41:32 am

Can I just ask; is there a way to change the default room on the web orbiter? Whenever I open the orbiter, it seems to default to "Closet" (I assume because it's the first in the list of rooms alphabetically?) - can I change it to "Living Room" for example?

Or another suggestion/question, could it be set up to display the room selection screen first, so that you can choose? This would be useful for my mobile phone, as I could be anywhere when I use that.

Hi Purps,

This is a bug in proxy_orbiter that we plan to fix soon...the bug makes the Web Orbiter default to the 'Room' that the Core or MD that has your ZWave interface is located in...it should default to the Room that the Orbiter has been set to default to of course.

All the best

Andrew

totallymaxed · « **Reply #115 on:** September 06, 2010, 03:54:46 pm »

Has anyone tested Web Orbiter 2.0 on a Blackberry Storm touch based mobile phone? Let me know if you have...I'd be interested to hear your experiences.

All the best

Andrew

purps · « **Reply #116 on:** September 06, 2010, 04:02:50 pm »

Quote from: totallymaxed on September 06, 2010, 03:49:42 pm

Quote from: purps on September 06, 2010, 10:41:32 am
Can I just ask; is there a way to change the default room on the web orbiter? Whenever I open the orbiter, it seems to default to "Closet" (I assume because it's the first in the list of rooms alphabetically?) - can I change it to "Living Room" for example?

Or another suggestion/question, could it be set up to display the room selection screen first, so that you can choose? This would be useful for my mobile phone, as I could be anywhere when I use that.

Hi Purps,

This is a bug in proxy_orbiter that we plan to fix soon...the bug makes the Web Orbiter default to the 'Room' that the Core or MD that has your ZWave interface is located in...it should default to the Room that the Orbiter has been set to default to of course.

All the best

Andrew

OK, thanks. Out of interest, what happens if you don't have z-wave? Would it then just default to the room containing the core?

totallymaxed · « **Reply #117 on:** September 06, 2010, 04:09:02 pm »

Quote from: purps on September 06, 2010, 04:02:50 pm

Quote from: totallymaxed on September 06, 2010, 03:49:42 pm
Quote from: purps on September 06, 2010, 10:41:32 am
Can I just ask; is there a way to change the default room on the web orbiter? Whenever I open the orbiter, it seems to default to "Closet" (I assume because it's the first in the list of rooms alphabetically?) - can I change it to "Living Room" for example?

Or another suggestion/question, could it be set up to display the room selection screen first, so that you can choose? This would be useful for my mobile phone, as I could be anywhere when I use that.

Hi Purps,

This is a bug in proxy_orbiter that we plan to fix soon...the bug makes the Web Orbiter default to the 'Room' that the Core or MD that has your ZWave interface is located in...it should default to the Room that the Orbiter has been set to default to of course.

All the best

Andrew

OK, thanks. Out of interest, what happens if you don't have z-wave? Would it then just default to the room containing the core?

Ignore that... I answered another question and got both responses mixed together! Your problem has nothing to do with ZWave :-)

But the bug is in proxy_orbiter and we are looking at a fix for it asap.

...note to self...do not answer two questions at once lol!

All the best

Andrew

purps · « **Reply #118 on:** September 08, 2010, 11:35:49 am »

Haha, no worries. Leave the multi-tasking to the women I say.

RayBe · « **Reply #119 on:** October 06, 2010, 10:32:45 am »

hi Andrew,

been using your weborbiter with great pleasure on my iphone 3GS,
the thing i noticed is that the images get blurry,
for instance the green area around a trackname gets 'artifacts' and the text isn't always readable,
i did set the standard iphone resolution,

is there anyway to get this better?

br,
Raymond

News: