Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - darrenmason

Pages: 1 [2] 3 4 ... 36
Feature requests & roadmap / Re: Android@Home - something to watch
« on: June 23, 2011, 01:20:42 am »
Interesting.... but Google would have to buy it and open it up a bit more for it to provide a real alternative.

From the Synapse website "Synapse Wireless Inc. provides patented hardware and software technology that helps tie together devices for
remote monitoring and control."

So in terms of an application layer free of patents - not at the moment. But perhaps google will but the company, open source the stack and donate the patents to one of the open consortium's.

We're still in for a bit of waiting it seems.


Users / Re: black screen on orbiters?
« on: June 22, 2011, 03:04:16 am »
If it was just the Android orbiters or Web Orbiters dropping connections then I would say look at the ProxyOrbiter logs on the core, however that would not effect the webdt orbiters as they are native....

See what is happening in DCERouter log when you go black or lose the connection.

When the android orbiters fail does doing a reload router help or do you definately have to reboot core? Do each of them connect to different instances of ProxyOrbiter or all to the same one (do they all talk to different ports or the same one?)

Users / MythTV Database out of sync
« on: June 14, 2011, 01:09:02 am »
Hi All,

Weird problem occurred yesterday. Went to update recording schedule via MythWeb last night and got SQL error when saving the recording. Error complains about column not existing.
Additionally, Upcoming recordings is blank.

Then on lounge MD tried to go into TV and myth frontend complains that DB version is not what is expected (it is newer/ later) than expected by 10 (sorry don't have exact numbers at the moment).

Planning to look through the logs etc but I am puzzled about why this has occurred.

The only things I have done that might be relevant are;
* Got a new networked TV which has DLNA support and tried to play a file from MythTV from it (unsuccessfully)
* Tried a similar thing from networked BlueRay player

Could the act of using a DLNA/upnp client have cause the MythTV backend to do a DB upgrade ???

Just looking for direction to track this down - if anyone has seen something similar. Ways to fix?


Users / Re: Android Orbiter
« on: June 10, 2011, 10:05:52 am »
Sorry posde didn't realise. Additionally sent the post from work where is blocked but is not....

Users / Re: Android Touch Orbiter
« on: June 10, 2011, 01:57:48 am »

Sorry must have missed this post when it was originally made....

But definitely interested in updating with increased functionality and to utilise additional Proxy_Orbiter features. Send me whatever you have or post whatever is available as I might get some time this weekend to spend on this....


Developers / Re: New Touch Orbiter & Proxy_Orbiter in development
« on: June 10, 2011, 01:53:25 am »

Let us know if there are any updates here. Might have some time this weekend to do the Android equivalent since I have a long weekend and no plans as yet.
Even if source is not terribly stable might be worth posting it somewhere so I can get an idea of what you are trying to achieve and where you are heading.


Users / Re: Android Orbiter
« on: June 10, 2011, 01:47:43 am »
The work that was done in this thread did not progress much further. Instead I developed a ProxyOrbiter client in Android that was simpler to develop and utilises existing backend functionality. This provides a reasonable user experience and is suitable for performing most interactions.

See this thread for details

And the code for this is here

Hoping to update this with increased functionality in line with the work that Andrew and the Dianemo guys are doing.


Users / Re: WebOrbiter 2.0
« on: May 27, 2011, 02:31:08 am »

Have you tried the Android orbiter on the mini6410? If so, does it work well?


Users / Re: Two Android Orbiters - pros and cons ?
« on: May 27, 2011, 02:28:24 am »
Out of interest - with this version and not locking it to Landscape - does it still crash on rotate? I made a couple of little changes that I thought might fix it but I couldn't replicate the problem with any hardware I had or the emulator.

Users / Re: Android Touch Orbiter
« on: May 17, 2011, 02:30:44 am »
Andrew - What is the refresh indicator? Not sure that I know what you mean. Do you mean like an on-screen animated icon whilst a refresh is occurring?

Feature requests & roadmap / Re: Android@Home - something to watch
« on: May 13, 2011, 02:16:46 am »
Doesn't seem to be anything 'real' available yet so it is hard to make heads or tails of it and weather/how it will fit with linuxMCE.

There are API's ready for the USB accessory stuff which is interesting but it appears that the @Home stuff might still be a fair way off.

Andrew - I actually looked at it more the other way around, rather than interfacing to @Home devices I thought it would be more interesting coupling the control interfaces to the devices that we already have interfaces for. ie; an @Home plugin for linuxMCE that would allow linuxMCE device discovery and control and tie it to whatever control API's they develop.

But until there is more info released everything is speculation.

Still, something to watch.


Users / Re: Android Touch Orbiter
« on: April 12, 2011, 01:35:40 am »
Out of interest (this is a question for Thom I guess), why is the N800 orbiter so responsive (in terms of volume control, skipping forward/back, any repetitive button presses) in comparison to the touch orbiters? Also the N800 ALWAYS displays the correct screen, in that it never needs to be refreshed - is there some fundamental reason for this?

I assure you this isn't a dig at your work darrenmason, I am just curious.


The Orbiter runs natively on N800. By that it connects directly to the server, responds to and creates its own DCE messages and then renders the user interface to the N800 using native libraries.

The android orbiter or any of the touch orbiters that have been developed and also the web orbiter rely on a proxy orbiter. What this is, is the same orbiter described above that runs natively on the N800 is running on another linuxMCE machine (typically the CORE). This orbiter is not rendering it's user interface to local libraries but is instead rendering to a bitmap - which is effectively a snapshot of the screen.
The touch orbiters then connect (typically via wireless) to the proxy orbiter and retrieve the bitmap. It is then displayed on the remote device which listens for touch commands on the bitmap. Those touches are sent back to the proxy orbiter which then reacts by updating the UI and rendering a new bitmap. This is then sent back to the touch device.

So each touch will at a minimum involve the rendering of a new bitmap and transferring that to the remote device. This takes time and introduces the lag that you are seeing in interactions that involve a lot of repetitive key presses.
There is also some code in the proxy orbiter that allows a flag to be set when the display updates independant of a user touch. The problem is that the remote device needs to poll for this flag as the communications with the proxy obriter as essentially client server. Depending upon this polling interval - there will be a lag associated with these updates. Additionally if that flag is not being set correctly then there may be inconsistencies with what is on the screen and what has been rendered.

Ways to improve;
* Write a native orbiter for the device or more correctly port the orbiter code to a device. This is easier on devices that support the same runtime libraries as Orbiter has already been built with. The N800 platform is better suited to this than Android and/or iOS.
* Reduce the work that the proxy orbiter is doing. This can be done by reducing your resolution and therefore decreasing the bandwidth required to transfer the bitmaps back and forth. This could also be done by not sending bitmaps but instead send markup that would be natively drawn.
* Reduce your 'AnyNews' polling interval so that refreshes occurr quicker when the updates are from independent events

Keep telling people what is not working the way you want it to though as it will be input for any changes that do get done.



Users / Re: Android Touch Orbiter
« on: April 06, 2011, 02:00:48 pm »
New version uploaded.

See for the latest apk.

Change log:
Added configuration and related code to allow locking the screen orientation in either landscape or portrait. Still allows default behavior as well
Added a couple of lines of code to give some feedback on touch. This is more playing around at the moment as I don't think it will meet the needs of the people that requested this. But see how it goes and feel free to give some more feedback. It should click and also give haptic feedback (if haptic feedback is on in config)

Anyway - please try and give me some feedback.


Users / Re: Android Touch Orbiter
« on: April 06, 2011, 01:03:26 pm »
I do have live wallpaper, yes, but disabling it didn't make any difference unfortunately. Should I do the log again without the live wallpaper?

Do I remember correctly you saying that a feature would be included to lock the orbiter to landscape?


Might as well do the log again - it was the only thing present that seemed to be going on at the same time.

Yeah the lock landscape feature is done - just testing some more. You might find that your issue goes away as well as it will no longer reload on rotation.
Try and get the new app uploaded as soon as possible.

Users / Re: Android Touch Orbiter
« on: April 06, 2011, 12:59:49 pm »

is there a deeper reason why you are not working off the svn repo? I see that you haven't done a commit to people/ for 5 month.

Another thing: Could you add a readme file detailing what is needed to get the android touch orbiter build on our builder? That way we could incorporate the output into our repo, and people would have it available from the web admin login page.

No reason - I havn't done any changes to the orbiter in 5 months. Only started doing some changes just the last couple of days.

At the time someone on the irc channel said put the stuff in people so that's where I stuck it.

wrt. building - shouldn't be too hard I guess. It will need the android SDK and probably has a few other dependencies but I will look into it.

Pages: 1 [2] 3 4 ... 36