Messages

Like you say, when you open reopen the app it has to reconnect to the proxy_orb which is why the splash-screen gets displayed. I'm wondering if the reconnect can be bypassed somehow.

When RoamingOrb is backgrounded maybe it can tell the core "i've been backgrounded" so that the core doesn't think it's dead when it stops responding to pings (I'm assuming this is how the protocol currently works). When re-opening RoamingOrb, the app can resume functioning as if it was never closed (maybe it just does a screen refresh).

Again, I don't know the details of the communication protocol, so this may be impossible without major structural changes. Thanks for listening to my ideas!

Hmmm ... When you start the app it opens a connection to the core and that connection keeps open until you exit the app, or until it is broken (example: quick reloading the dce router).

What i probably could do is backgrounding the app and keeping the connection open (not sure if that is possible as long as i don't have a corresponding device). But you have to keep in mind that the app can also be used over 3G where disconnections are not rare.

Anyhow, i will investigate in that direction as soon as i have a multitasking enabled device ....

Another factor is that on a 3G connection where the user may have limitations on their mobile dataplan they might leave the App open but in the background and chew up a lot of their data plan allowance - without realising it. On the other hand the amount of data we're moving when the app is idle and no screen changes are happening is pretty tiny so this may not really be an issue. On a Wifi connection this is not a problem of course.

I still think the big win with multi-tasking is the ability for a future version of the App to alert you, when its in the background, to some system event...eg the door bell was pressed, A security alert has been triggered...if the App is sitting their it can alert the user and bring the event to the users attention etc.

All the best


Andrew

I am investigating with push notifications for that, so even if your app is not started you could be notified of such events.

Concerning the data plan: I am atm evaluating another technique together with uplink. We try to use weborbiter_command and weborbiter_image instead of directly speak to the proxy_orb plugin.
This will then work on standard http port (future remote access) and this may touch battery life. It will also make backgrounding easier as you simply don't poll while in background, but you don't have to disconnect and reconnect everytime.
I am just concerned if this have the same performance. I will do first tests on weekend and let you know.

Serge

Like you say, when you open reopen the app it has to reconnect to the proxy_orb which is why the splash-screen gets displayed. I'm wondering if the reconnect can be bypassed somehow.

When RoamingOrb is backgrounded maybe it can tell the core "i've been backgrounded" so that the core doesn't think it's dead when it stops responding to pings (I'm assuming this is how the protocol currently works). When re-opening RoamingOrb, the app can resume functioning as if it was never closed (maybe it just does a screen refresh).

Again, I don't know the details of the communication protocol, so this may be impossible without major structural changes. Thanks for listening to my ideas!

Hmmm ... When you start the app it opens a connection to the core and that connection keeps open until you exit the app, or until it is broken (example: quick reloading the dce router).

What i probably could do is backgrounding the app and keeping the connection open (not sure if that is possible as long as i don't have a corresponding device). But you have to keep in mind that the app can also be used over 3G where disconnections are not rare.

Anyhow, i will investigate in that direction as soon as i have a multitasking enabled device ....

Hi Andrew,

Been playing a bit more with this yesterday and today. Still very much enjoying the new toy

A couple questions that should not be taken to mean that I'm complaining about what you've provided or suggesting you need to do more work:

1) Is multitasking support possible? You'd obviously want to avoid battery drainage from constant polling by doing a suspend-state type thing if the protocol allows. The splash screen on reopening the app is pretty quick, but I'm wondering if it could be eliminated or made faster.

2) Is there any possible future for follow-me via blue-tooth in this app?

Thanks again!

Hi !

Multitasking would be possible. I will get an iPhone 4 in about 3 weeks. I can't test it on my existing iPhone3, but until now i did not see the interest in multitasking. What should the app do in the background ?

Concerning the splash screen: It does not take any time. in fact the system shows the screen while reconnecting to the proxy_orb on your core. Of course we could eliminate the splash screen, but that would give you an empty screen :-) It's not that the splash has a 5 seconds timer to show our nice logo or something like that.

I find your follow-me idea great. We will investigate in that direction. I think some core modifications would need to be done, but nothing is impossible ;-)

Thank you for your feedback.

Wow!  From the screenshots this looks great!

Any chance you could get it working on iOS 3.1.3?  I'd love to use it on my first generation phones.

Hi !

We have a version running on 3.1.3. now mainly for older iPod's. I will submit it to the app store today. Of course i can't tell you when apple will review and authorize it :-) Keep looking for updates ... :-)

As your ticketing system is nearly impossible to use (spamfilter ways to sensitive) i post my ticket here:

When using Safari5 on OSX and on W7 the "Phones" link on the left menu shows me the master Z-wave device. Not the children (like lightnings, climate, ...) but only the master parent device.

Using the Top menu "Wizard / Devices / Phones" does work without problems and shows me my orbiters and SIP phones ...

See atached screenshot.

Using Firefox on both platforms works like a charm ...

Greetings,

Foxi352

Hi !

Greetings to the community !

I'm relatively new @ LinuxMCE but have some Linux and coding experience. I wanted to dip into LinuxMCE dev and, as everyone should do when new, followed the Building Wiki Page. I installed a clean Kubuntu 8.10 into a parallels machine on my Snow Leopard, but i don't think this changes anything.

What i feel about my first experience:

• The prepare scripts adds the avenard repo to the sources.list. The wiki page has been modified telling that this repo is no longer used, so i removed the line.
• The e-tobi repo is not added by the prepare scripts altough that one is needed. Added that one.
• Got an error (don't remeber the step where it was) telling it can't find the libvdpau. Added the avenard repo again solved the problem, that means it is nevertheless needed ??

Feel free to correct me if i am wrong...

The compile error i initially added to this post was already solved by niz23 tonight, so this is all i remember ...

Cheers.

Hi all,

I am new with LinuxMCE. I managed to get a Hybrid working witz ZWAVE Lightning Control, WebOrbiter and MD Netboot with the latest 8.10 snapshot (i think 13 july) ISO.

I bought a SkyStar HD2 and followed the instructions on http://www.linuxtv.org/wiki/index.php/Azurewave_AD_SP400_CI_(VP-1041)#Drivers.

That means i installed the mantis multiproto driver. I loaded the mantis module and see the devices under i2c module.

I added the mantis module to /etc/modules and rebooted. I checked the module was loaded with lsmod. Unfortunately LinxuMCE does not find a new plug & play dvb-s card.

Has someone managed to get this working ?

Regards,

Serge