LinuxMCE Forums

General => Users => Topic started by: golgoj4 on February 12, 2012, 07:01:04 am

Title: Android QOrbiter
Post by: golgoj4 on February 12, 2012, 07:01:04 am
https://market.android.com/details?id=org.linuxmce.qorbiter
http://wiki.linuxmce.org/index.php/Android_Orbiter

==This is a Beta Release==
Things will be broken.

Please read all instructions. Time spent in irc debugging is time spent not coding. I want to fix things, but lets be efficient :)

Please be _clear_ about what is occuring.

Include screenshots if possible.

Learn Qml
Enjoy!

-golgoj4-
Title: Re: Android QOrbiter
Post by: RayBe on February 12, 2012, 09:13:42 am
Hi golgoj4,

A very big Congratulations on your beta release of qOrbiter.
Great work.

br,
Raymond
Title: Re: Android QOrbiter
Post by: bongowongo on February 12, 2012, 09:34:46 am
I uninstalled the earlier version I got from Golgoj4/5 and installed through the app-market.
It says it is installed. When I run it I see that my old settings are still filled in. (I unstalled the app but it saves the settings)
It tries to load default skin and then crashes.

HTC Z Desire 2.4.4.

Also good job for getting it in the app store, thanks for your persistence and hard work.
Title: Re: Android QOrbiter
Post by: golgoj4 on February 12, 2012, 12:04:31 pm
just pushed an updated .apk to the market that hopefully will solve the issue. Seem to be working from my emulator setup. Also, mods seem to be having issues (like cyanogen mod) but ill be working with the users of those mods to find out whats going wrong. i have my suspects but its 3am so ill leave the troubleshooting for later.


Thanks for testing it out bongo!
-golgoj4
also
http://www.youtube.com/watch?v=yGNp1-g0jEE
:) cheers
Title: Re: Android QOrbiter
Post by: m3freak on February 12, 2012, 05:31:37 pm
I will give this a go on my Google Nexus S sometime today.
Title: Re: Android QOrbiter
Post by: huh on February 12, 2012, 05:58:00 pm
Here it is on my galaxy sII skyrocket:
 http://imgur.com/97vRI (http://imgur.com/97vRI)

And
 http://imgur.com/rOR2T  (http://imgur.com/rOR2T)

I too deleted the one I had installed previously and pulled the one from the market.  FWIW, the picture only fills the tip left portion of my screen.
Title: Re: Android QOrbiter
Post by: bongowongo on February 12, 2012, 06:05:54 pm
Here it is on my galaxy sII skyrocket:
 http://imgur.com/97vRI (http://imgur.com/97vRI)

And
 http://imgur.com/rOR2T  (http://imgur.com/rOR2T)

I too deleted the one I had installed previously and pulled the one from the market.  FWIW, the picture only fills the tip left portion of my screen.
Did it also save the setting of the uninstalled version?
Title: Re: Android QOrbiter
Post by: huh on February 12, 2012, 06:29:53 pm
Yes, it did and I have another qorbiter on my core for my desktop skin, so poetry sure it didn't just go to the core and which device id to use.  Should I try deleting the config file and app, then reinstall?
Title: Re: Android QOrbiter
Post by: golgoj4 on February 12, 2012, 06:49:44 pm
Yes, it did and I have another qorbiter on my core for my desktop skin, so poetry sure it didn't just go to the core and which device id to use.  Should I try deleting the config file and app, then reinstall?

nah that wont make much of a difference. the config file mainly saves connection details.

ive gotta get my hands on another android phone so i cant do more in depth testing before i post the .apk...expect an update this afternoon.

-golgoj4
Title: Re: Android QOrbiter
Post by: huh on February 12, 2012, 10:05:54 pm
In the mean time, tried this on my HP Touchpad with cyanogenmod 7 (resolution 1024x768):

http://imgur.com/MR3N7 (http://imgur.com/MR3N7)

and landscape:
http://imgur.com/orn6K (http://imgur.com/orn6K)

Ignore the time at the bottom- clearly having trouble with my touchpad keeping time  :)

BTW- as for performance- can't speak to how the media scrolls as I can't get my NAS to display media, but the EPG scrolls VERY smoothly.  Flicking is exactly what I would expect and it works- clicking a channel forces my USBUIRT to fire the code and cable box changes as expect.  Only problem I've had is getting the orbiter to start after closing...  if I don't go to the "Open/Close App Drawer" and then do a long press on the QOrbiter icon followed by "Application Info" where I can "Force stop" the app.  Oddly, sometimes after doing that, on the next start of the QOrbiter app, the splash screen appears, but gets stuck at "Setting Skin to:default".  Haven't found a work around yet- going to give it a couple minutes then try and restart the app.


Edit:
New picture using new orbiter golgoj4 just pushed out:
http://imgur.com/8Ouks (http://imgur.com/8Ouks)
Title: Re: Android QOrbiter
Post by: golgoj4 on February 13, 2012, 01:46:09 am
New update pushed out, Merkur2k reports good results on his tablet device.

thank you for your patience.

golgoj4
Title: Re: Android QOrbiter
Post by: golgoj4 on February 13, 2012, 06:40:52 am
New update pushed out, Merkur2k reports good results on his tablet device.

thank you for your patience.

golgoj4

Me being a rocket scientist, i forgot to make it active. Both l3top and merkur2k report good things.

-golgoj4
Title: Re: Android QOrbiter
Post by: m3freak on February 13, 2012, 04:28:03 pm
Total fail on my Google Nexus S.  I get a black screen when I start QOrbiter.  Once I managed to get the "config" screen where you input your Core's IP and whatnot, but I couldn't actually do anything on it - the screen was locked up.

I haven't tried rebooting the phone, so I'll try that next.
Title: Re: Android QOrbiter
Post by: cfernandes on February 13, 2012, 05:35:14 pm
i have same issue, when i put core ip  and device id  and  hit go  show a blackscreen than close.
Title: Re: Android QOrbiter
Post by: golgoj4 on February 13, 2012, 08:09:35 pm
i have same issue, when i put core ip  and device id  and  hit go  show a blackscreen than close.

Im assuming you followed all the instructions for preparing for it? Downloading skins, running the qorbiter config, etc.
Title: Re: Android QOrbiter
Post by: cfernandes on February 13, 2012, 08:53:08 pm
yes .

this is a log from DCEroure.log   

[33;1mSocket::ReceiveData 0x831ac50 failed, bytes left 0 start: 7970000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 172 Incoming_Conn Socket 172 192.168.80.145EVENT 84 T=2186 Event #84^[[0m <0x58c99b70>
05      02/13/12 14:31:30.699           ^[[33;1mSocket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 172 192.168.80.145EVENT 84 T=2186 Event #84^[[0m <0x58c99b70>
05      02/13/12 14:31:30.699           ^[[33;1mTCPIP: Closing connection to 84 (Router Dev #0) 0x831ac50 m_Socket: -1^[[0m <0x58c99b70>
05      02/13/12 14:31:30.699           ^[[33;1mSocket::ReceiveData 0x831add0 failed, bytes left 0 start: 7970000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 173 Incoming_Conn Socket 173 192.168.80.145EVENT 84 T=2186 Event #84^[[0m <0x58298b70>
05      02/13/12 14:31:30.699           ^[[33;1mSocket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 173 192.168.80.145EVENT 84 T=2186 Event #84^[[0m <0x58298b70>
05      02/13/12 14:31:30.699           ^[[33;1mTCPIP: Closing connection to 84 (Router Dev #0) 0x831add0 m_Socket: -1^[[0m <0x58298b70>
05      02/13/12 14:31:30.699           ^[[33;1mRouter::RemoveAndDeleteSocket 0x831add0 84^[[0m <0x58298b70>
05      02/13/12 14:31:30.699           ^[[33;1mRouter::RemoveAndDeleteSocket 0x831ac50 84^[[0m <0x58c99b70>
05      02/13/12 14:32:47.664           ^[[33;1mSocket::ReceiveData 0x831ac50 failed, bytes left 0 start: 8070000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 172 Incoming_Conn Socket 172 192.168.80.145EVENT 84 T=2186 Event #84^[[0m <0x58c99b70>
05      02/13/12 14:32:47.664           ^[[33;1mSocket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 172 192.168.80.145EVENT 84 T=2186 Event #84^[[0m <0x58c99b70>
Title: Re: Android QOrbiter
Post by: rages on February 13, 2012, 09:30:44 pm
Very good work !!!!

It's very good for my Sony Tablet S and my HTC Desire HD with miui 2.3.7c

Emanuele
Title: Re: Android QOrbiter
Post by: golgoj4 on February 13, 2012, 10:13:31 pm
Very good work !!!!

It's very good for my Sony Tablet S and my HTC Desire HD with miui 2.3.7c

Emanuele

thanks :) just working hard to support as many as possible. Cfernades im still investigating!

-golgoj4
Title: Re: Android QOrbiter
Post by: golgoj4 on February 13, 2012, 10:17:23 pm
yes .

this is a log from DCEroure.log   

[33;1mSocket::ReceiveData 0x831ac50 failed, bytes left 0 start: 7970000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 172 Incoming_Conn Socket 172 192.168.80.145EVENT 84 T=2186 Event #84^[[0m <0x58c99b70>
05      02/13/12 14:31:30.699           ^[[33;1mSocket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 172 192.168.80.145EVENT 84 T=2186 Event #84^[[0m <0x58c99b70>
05      02/13/12 14:31:30.699           ^[[33;1mTCPIP: Closing connection to 84 (Router Dev #0) 0x831ac50 m_Socket: -1^[[0m <0x58c99b70>
05      02/13/12 14:31:30.699           ^[[33;1mSocket::ReceiveData 0x831add0 failed, bytes left 0 start: 7970000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 173 Incoming_Conn Socket 173 192.168.80.145EVENT 84 T=2186 Event #84^[[0m <0x58298b70>
05      02/13/12 14:31:30.699           ^[[33;1mSocket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 173 192.168.80.145EVENT 84 T=2186 Event #84^[[0m <0x58298b70>
05      02/13/12 14:31:30.699           ^[[33;1mTCPIP: Closing connection to 84 (Router Dev #0) 0x831add0 m_Socket: -1^[[0m <0x58298b70>
05      02/13/12 14:31:30.699           ^[[33;1mRouter::RemoveAndDeleteSocket 0x831add0 84^[[0m <0x58298b70>
05      02/13/12 14:31:30.699           ^[[33;1mRouter::RemoveAndDeleteSocket 0x831ac50 84^[[0m <0x58c99b70>
05      02/13/12 14:32:47.664           ^[[33;1mSocket::ReceiveData 0x831ac50 failed, bytes left 0 start: 8070000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 172 Incoming_Conn Socket 172 192.168.80.145EVENT 84 T=2186 Event #84^[[0m <0x58c99b70>
05      02/13/12 14:32:47.664           ^[[33;1mSocket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 172 192.168.80.145EVENT 84 T=2186 Event #84^[[0m <0x58c99b70>



Is the device number 84?

-golgoj4
Title: Re: Android QOrbiter
Post by: cfernandes on February 13, 2012, 10:22:47 pm
correct  and tablet ip address 192.168.80.145
Title: Re: Android QOrbiter
Post by: golgoj4 on February 13, 2012, 11:03:17 pm
correct  and tablet ip address 192.168.80.145

what version of linuxmce, and are you fully up to date.
Title: Re: Android QOrbiter
Post by: cfernandes on February 14, 2012, 07:17:24 pm
i use 1004  full updated .
Title: Re: Android QOrbiter
Post by: golgoj4 on February 19, 2012, 08:27:15 am
Ok, Ive done an update, hope fully this addresses screen sizing issues and it makes things a bit more stable.

Cfernades i would do the following:
Delete the device in linuxmce
delete it from your phone (including the directory on the sdcard 'LinuxMCE')

Re-add the qorbiter android orbiter from the 'orbiters page'
fill in all the information such as user, location, etc and update
goto  http://dcerouter/lmce-admin/qOrbiterGenerator.php?d=youdevicenumber  to generate the config
reinstall the android app

cross fingers :)

let me know how it goes
-golgoj4
Title: Re: Android QOrbiter
Post by: cfernandes on February 29, 2012, 11:35:00 pm
sorry for delay,   

I followed your instructions but no luck. on SD does not exist in the directory LinuxMCE
 bellow is a DCEROUTER.log

05      02/29/12 19:31:05.318           Socket::ReceiveData 0x994b4d0 failed, bytes left 0 start: 61200000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 173 Incoming_Conn Socket 173 192.168.80.143EVENT 88 T=2186 Event #88 <0xa2cf2b70>
05      02/29/12 19:31:05.318           Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 173 192.168.80.143EVENT 88 T=2186 Event #88 <0xa2cf2b70>
05      02/29/12 19:31:05.318           TCPIP: Closing connection to 88 (Router Dev #0) 0x994b4d0 m_Socket: -1 <0xa2cf2b70>
05      02/29/12 19:31:05.318           Router::RemoveAndDeleteSocket 0x994b4d0 88 <0xa2cf2b70>
05      02/29/12 19:31:05.318           Socket::ReceiveData 0x9959b78 failed, bytes left 0 start: 61200000 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 117 Incoming_Conn Socket 117 192.168.80.143EVENT 88 T=2186 Event #88 <0x57895b70>
05      02/29/12 19:31:05.328           Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 117 192.168.80.143EVENT 88 T=2186 Event #88 <0x57895b70>
05      02/29/12 19:31:05.328           TCPIP: Closing connection to 88 (Router Dev #0) 0x9959b78 m_Socket: -1 <0x57895b70>
05      02/29/12 19:31:05.328           Router::RemoveAndDeleteSocket 0x9959b78 88 <0x57895b70>
Title: Re: Android QOrbiter
Post by: tux-box1 on March 01, 2012, 12:53:12 am
I get this error when I visit that address
Code: [Select]
Connected, Proceeding with OrbiterGen for device: <49>

Fatal error: Uncaught exception 'DOMException' with message 'Invalid Character Error' in /var/www/lmce-admin/qOrbiterGenerator.php:45 Stack trace: #0 /var/www/lmce-admin/qOrbiterGenerator.php(45): DOMDocument->createElement('Orbiter<49>') #1 {main} thrown in /var/www/lmce-admin/qOrbiterGenerator.php on line 45
Title: Re: Android QOrbiter
Post by: golgoj4 on March 01, 2012, 03:25:45 am
I get this error when I visit that address
Code: [Select]
Connected, Proceeding with OrbiterGen for device: <49>

Fatal error: Uncaught exception 'DOMException' with message 'Invalid Character Error' in /var/www/lmce-admin/qOrbiterGenerator.php:45 Stack trace: #0 /var/www/lmce-admin/qOrbiterGenerator.php(45): DOMDocument->createElement('Orbiter<49>') #1 {main} thrown in /var/www/lmce-admin/qOrbiterGenerator.php on line 45

What browser are you using?
Title: Re: Android QOrbiter
Post by: tux-box1 on March 01, 2012, 04:16:34 am
firefox, in the orbiter creation it states description qorbiter # 49
Title: Re: Android QOrbiter
Post by: golgoj4 on March 01, 2012, 04:52:37 am
firefox, in the orbiter creation it states description qorbiter # 49

couldnt duplicate, but im updating to the latest firefox to check again.

-golgoj4
Title: Re: Android QOrbiter
Post by: golgoj4 on March 01, 2012, 07:23:48 am
What browser are you using?


http://192.168.80.1/lmce-admin/qOrbiterGenerator.php?d=84

is what the url should look like. no < or >

-golgoj4
Title: Re: Android QOrbiter
Post by: phenigma on March 01, 2012, 06:01:06 pm
On my Samsung Galaxy Tab 10.1 the qorbiter loads and runs.  I can choose a user.  No scenarios show up, the advanced button works, the power button causes a lock-up.

On my phone Samsung Galaxy S Glide (Captivate Glide in the USA) the app loads to show a black screen only.

Anything I can check or do to help?

J.
Title: Re: Android QOrbiter
Post by: tux-box1 on March 01, 2012, 07:58:46 pm
Thanks, I did get the url wrong, but I tried again with the modified code.
Code: [Select]
http://192.168.3.80/lmce-admin/qOrbiterGenerator.php?d=49 and got this message
Quote
Connected, Proceeding with OrbiterGen for device: 49
Looking for /var/tmp/49conf.xml...found existing conf, overwriting!
Setting FileFormats Sort List Up...Setting Media SubTypes Sort List Up...Finding default user and room........done
Looking up Users now......done!
Looking up Rooms now.. ....done!
Setting Genre List Up.......done!
Setting Attribute Sort List Up.......done!
Starting Lighting Scenarios....done!
Starting Media Scenarios....done!
Starting Climate Scenarios....done!
Starting Telecom Scenarios....done!
Starting Security Scenarios....done!
DB closed
Warning: fclose(): supplied argument is not a valid stream resource in /var/www/lmce-admin/qOrbiterGenerator.php on line 109
Any thoughts?
Title: Re: Android QOrbiter
Post by: golgoj4 on March 01, 2012, 09:51:29 pm
On my Samsung Galaxy Tab 10.1 the qorbiter loads and runs.  I can choose a user.  No scenarios show up, the advanced button works, the power button causes a lock-up.

On my phone Samsung Galaxy S Glide (Captivate Glide in the USA) the app loads to show a black screen only.

Anything I can check or do to help?

J.

Thanks for the info, i will look into that right away.
*I did push an update in the past few days so it may be related to that. Please update from the market and update your qml, i will be firing up the emu and see whats going on.

thanks for reporting back!
-golgoj4
Title: Re: Android QOrbiter
Post by: golgoj4 on March 03, 2012, 12:07:46 am
http://forum.linuxmce.org/index.php/topic,12436.0.html

this should correct an issue l3mce helped me discover that was unique to high end android phones.

-golgoj4
Title: Re: Android QOrbiter
Post by: phenigma on March 03, 2012, 01:31:12 am
Updated qml, rebuilt orbiter.

Runs on both my Samsung Galaxy Tab 10.1 and my Samsung Galaxy S Glide (Captivate Glide in US).  Looks good on the tablet.  Very minimal on the phone, I expect this is different skins, I haven't checked.

Some issues on both but the scenarios show up on both and I can select rooms.  
Sometimes they crash before completing to load the app.
User selection works on the tablet, not on the phone.
Advanced screen works on the tablet, not the phone.
Media grids sometimes crash on both.
I can't seem to 'play' any media with either, no 'play all' button either.
Doesn't appear to be a 'Now Playing' screen available like the original orbiter.

Some of the above is likely known, I'm just passing on my observations.  Coming along nicely!  Let me know if there is anything you'd like me to try.

J.
Title: Re: Android QOrbiter
Post by: golgoj4 on March 03, 2012, 03:12:56 am
Updated qml, rebuilt orbiter.

Runs on both my Samsung Galaxy Tab 10.1 and my Samsung Galaxy S Glide (Captivate Glide in US).  Looks good on the tablet.  Very minimal on the phone, I expect this is different skins, I haven't checked.

Some issues on both but the scenarios show up on both and I can select rooms.  
Sometimes they crash before completing to load the app.
User selection works on the tablet, not on the phone.
Advanced screen works on the tablet, not the phone.
Media grids sometimes crash on both.
I can't seem to 'play' any media with either, no 'play all' button either.
Doesn't appear to be a 'Now Playing' screen available like the original orbiter.

Some of the above is likely known, I'm just passing on my observations.  Coming along nicely!  Let me know if there is anything you'd like me to try.

J.

Yeah the phone UI is very minimal right now.
The way ive been doing the dev of the skins is to do my core development against
lmce-admin/skins/desktop default. Kind of the testbed UI so to speak.
then i port over to
lmce-admin/skin/android/phone/default
 and
 lmce-admin/skins/android/tablet/default

As you can see, i sometimes get my wires crossed :)

Ill be looking into the issues you mentioned, and ive released another update today, not sure if you got that one yet. 2.0.4

Thanks again
golgoj4
Title: Re: Android QOrbiter
Post by: golgoj4 on March 05, 2012, 08:21:47 am
http://wiki.linuxmce.org/index.php/QOrbiter

Prelim skinning guide

golgoj4
Title: Re: Android QOrbiter
Post by: phenigma on March 07, 2012, 02:14:09 am
I'll have a look at that.  Haven't tested in a couple of days, I'll check my version and see where it's at.

J.
Title: Re: Android QOrbiter
Post by: golgoj4 on March 22, 2012, 10:23:26 am
Hello again party people,

I realize things have been slow on updates, and I apologize. But ive really been trying to solve problems instead of band aid them, with some success.

A very important note: this will mark a split into two separate versions. One WITH opengl and one without. From looking at the installation statistics, the vast majority of devices that are installed support open-gl, which means this will only be a plus. My personal android device does not support opengl (a blessing in more ways than one) so there will also be a non open gl version as well. I should be available this weekend if you post in irc or drop by the forums and leave as detailed a message as possible. If you are a tablet user and have some time friday please let me know. I don't have an open gl tablet and I would like to know if there are any issues when its rolled out. earlier maybe but tomorrow could be a very good day *fingers crossed* so i will more than likely be available on friday.

It should also be noted in big freaking billboard lettering that L3mce sent me a phone that supports open gl, which is what is allowing me to even extend opengl to android. So once again, a big thanks to him for providing hardware for me to dev on. The emulator only goes so far. Which, on a side note, is annoying when you have a beast of a machine :)

-cheers
golgoj4
Title: Re: Android QOrbiter
Post by: davegravy on March 22, 2012, 02:48:15 pm
Great news! I should be around today and tomorrow evening to test on my Transformer Prime. Send me a note in IRC when you're ready.
Title: Re: Android QOrbiter
Post by: WhateverFits on March 22, 2012, 05:36:46 pm
That is amazing news! I'll try to be around for this but I'm still unpacking. Just got my LinuxMCE system back online last night.
Title: Re: Android QOrbiter
Post by: kyfalcon on March 22, 2012, 08:27:17 pm
I will try and give it a go on my Galaxy Nexus.
Title: Re: Android QOrbiter
Post by: kyfalcon on March 23, 2012, 03:30:19 pm
Where is the apk for the new orbiter? I went to android market and it shows as installed. I downloaded that one several weeks ago.
Title: Re: Android QOrbiter
Post by: davegravy on March 23, 2012, 03:55:57 pm
Where is the apk for the new orbiter? I went to android market and it shows as installed. I downloaded that one several weeks ago.

As per the wiki, golgoj4 has his nightly builds hosted from his website: http://www.lasmarthomes.com/QOrbiter-release.apk (http://www.lasmarthomes.com/QOrbiter-release.apk)

Title: Re: Android QOrbiter
Post by: davegravy on March 23, 2012, 03:58:56 pm
golgoj4, for us less well informed testers, what (if anything) is required for us to test the latest android qorbiter other than:

* co the latest skins directory
* download and install the latest .apk from your website

Thanks
Title: Re: Android QOrbiter
Post by: golgoj4 on March 23, 2012, 06:14:36 pm
Sorry for being a bit confusing guys

I have not released the new apk yet as of this posting. I took some time to try and fix the issue with needing to double tap for certain functions things to happen.

Testing consists of 2 different things on android

1) QML. This is the ui, and while its kind of weird, think of it literally as CSS style. Thats essentially what the qml is. So, that being said, upgrades, changes, etc to the UI can be gotten by doing the svn update of your qml as its loaded from the network

2) The APK. The apk is the core code which actually runs on your Android device. As was pointed out, I have nightly builds on my website, and updates are pushed to the market after sufficient tests.

I have pushed an update for the QML, which can be grabbed by doing an svn update. The actual APK will be coming a bit later, as I was trying to implement some open gl visual effects. I think im going to save that for the next pass however.

-golgoj4

Title: Re: Android QOrbiter
Post by: golgoj4 on March 23, 2012, 07:16:57 pm
There is a new 'nightly' up at Http://www.lasmarthomes.com/QOrbiter-release.apk

This is the OpenGL version. While you wont see fancy effects as of yet, you _should_ see improved graphics performance. Works on the Droid X I have here, but would like someone with a tablet to give it a before I push it out to the market.

Cheers,
golgoj4
Title: Re: Android QOrbiter
Post by: phenigma on March 23, 2012, 09:06:39 pm
I'll update my phone and tablet when I get home in a couple hours and let you know here or in irc.

J.
Title: Re: Android QOrbiter
Post by: phenigma on March 24, 2012, 12:47:46 am
Updated my skins folder, re-ran the qorbiter-generator.php for my device ids.  Grabbed the new experimental apk on each device.  Results:

The Samsung Galaxy Tab 10.1 4G likes the photos running in the background.  ;)  Nice touch.  Functionality is improved across a lot of the interface.  Maturing well!  Great job!  No 'Play All' button for audio media, have to play tracks individually.  Power menu appears, didn't do anything when I selected an option.  Selecting the 'Room' button at the bottom loads some pictures along the top at the left hand side of the screen that have no text,actually I think the orbiter screen is pushed up off the display by the amount consumed by the Android Os tablet menu along the bottom of the screen, all the screens appear to be missing this chunk of pixels along the top of display.

The Samsung Galaxy S Glide phone (Captivate Glide stateside) is not working.  App starts, gets to 'Setting up Lmce' and freezes.  No response.  Have to kill it from the task manager.  I'll have to remove the app and config folder and re-install to see if this fixes the app load.

Performed a fresh install on my wifes phone, identical, and the app loads.  Go to choose a room and the list appears but we are unable to select a room, the list never closes.  Lights on/off works.  Advanced menu shows, haven't tested buttons on this menu yet.  Video menu brings up a list of videos, some pics show, but all text is showing as small boxes in place of each letter of the titles/names.  Choosing items to play videos works, now playing screen shows text properly.  Volume up/down works in media playback.  Audio list is similar to video list, blocks for letters.  No 'Play All' but playback of individual tracks is working.  Audio track info in the now playing screen is showing blocks for letters in the text.

Icon is great, nicer than the large 'Q' :).

If you want more specifics or real-time feedback in irc let me know.

J.
Title: Re: Android QOrbiter
Post by: golgoj4 on March 24, 2012, 05:03:05 am
I will be investigating the issus with the galaxy S. I have updated and tested the user and room selector for the android phone, they should now be working

*Play all should be coming soon
*im investigating the issue with the text....im very curious as to what thats all about, will report back asap


thanks for testing!

-golgoj4
Title: Re: Android QOrbiter
Post by: golgoj4 on March 24, 2012, 05:39:50 am
ok, i found a potential fix for the text issue. Its been rolled in and is on my website for your download and feedback. :)

-golgoj4
Title: Re: Android QOrbiter
Post by: phenigma on March 24, 2012, 07:31:36 pm
I will be investigating the issus with the galaxy S. I have updated and tested the user and room selector for the android phone, they should now be working

Keep in mind that my phone is the Galaxy S Glide (Captivate Glide in the US) and so it is not the same as the Galaxy S that everyone is used to.  This is a dual-core phone with a slide out keyboard.  Just in case there is confusion (I know most people are about the 'S' line).

Room selection:
User selection:
*Play all should be coming soon

k, I will stop mentioning it until you say it's in.  Just didn't know if was supposed to be there yet or not.

*im investigating the issue with the text....im very curious as to what thats all about, will report back asap
ok, i found a potential fix for the text issue. Its been rolled in and is on my website for your download and feedback. :)

Cool the synopsis and performers lists expand/contrct.  On both the phones and tablet.

Okay, in the Now Playing screen for Audio:

Okay, in the Now Playing screen for Video:

Audio Lists (datagrids):

Video Lists (datagrids) essentially the same as for the audio:

'Power' Menu:
thanks for testing!

You're welcome.  Thank you for all the amazing work you're doing here!  I am only too happy to help!  My wife is really liking the idea of controlling the system from her phone and she is very tolerant of me breaking things if it will ultimately lead to an improved experience.  She's very forgiving.  :)

J.
Title: Re: Android QOrbiter
Post by: golgoj4 on March 24, 2012, 08:11:00 pm
Im happy to hear she's willing to deal with my so so programming!

The issue, as you just helped me confirm, related to devices not reporting their DPI. Now, I have no idea if its the software im compiling with, or the phone, but what I do know is that by setting the text to bold, it forces it to show. Weird I know, but now that you helped me figure that out, the blocks should be going away as I know specfically what to address now.

As for the other issues, im slowly rounding those out as frankly im a little add touched and I bounce back and forth in between the 3 different skins im working on now.

Also, doing some research into the Captivate Glide, it appears that it does support Open GL es. Other users have reported some issues using ministro when it came to downloading the libraries required. If you wouldnt mind please:
*Find the ministro app under setting, and click 'Clear Data'
*re-run qOrbiter

I suspect there was an update or something that wasnt transparent fully with ministro and that the library versions are mismatching. Let me know when you can

-golgoj4

-Thanks again
Title: Re: Android QOrbiter
Post by: ppiszc on March 24, 2012, 10:13:50 pm
golgoj4,

I just installed (first time) qorbiter on my Android (cheap china device - "Leader TAB R70"*) and after "splash screen" qorbiter exits without any message. I can't even put IP of my core.
Is it possible to run qorbiter on my device or I have to buy something like Galaxy tab?.
I can run any app if you want to dig deep into my droid.

Cheers,
ppiszc

*Some info from Android system info app:
BuildInfos
Android version : 2.1-update1-1.0.0
Release Codename : REL
API LEVEL : 7
CPU ABI : armeabi
Manufacturer : unknown
Board : trout
Brand : rockchip
Device : sdkDemo
Display : V0.18.ECLAIR.FH_TONE_8188.20110114.102044
Fingerprint : rockchip/sdkDemo/sdkDemo/trout:2.1-update1/ECLAIR/eng.temp.20110114.102044:user/test-keys
Host : temp-desktop
ID : ECLAIR
Model : rk2818sdk
Memory
Download Cache Max: 112MB/ Free: 96.76MB
data Max: 248MB/ Free: 186MB
External storage Max: 7.39GB/ Free: 4.48GB
Total RAM: 200MB
Free RAM: 82.51MB
Threshold RAM: 16.00MB
Screen
Resolution: 800 x 480
Refresh Rate: 73726.48
X factor for DIP: 1.0
Density: 160 dpi
Pixel per inch X: 25.4 dpi Y: 25.4 dpi
OpenGL
OpenGL Version supported : 0.0
OpenGL Version supported : OpenGL ES-CM 1.0
Vendor : Android
Renderer : Android PixelFlinger 1.2
Extensions :
GL_OES_byte_coordinates GL_OES_fixed_point GL_OES_single_precision GL_OES_read_format GL_OES_compressed_paletted_texture GL_OES_draw_texture GL_OES_matrix_get GL_OES_query_matrix GL_OES_EGL_image GL_ARB_texture_compression GL_ARB_texture_non_power_of_two GL_ANDROID_user_clip_plane GL_ANDROID_vertex_buffer_object GL_ANDROID_generate_mipmap
Title: Re: Android QOrbiter
Post by: cfernandes on March 24, 2012, 10:41:31 pm
i have the same result on my cheap tablet.

i think this issue is related  to android 2.2  and 2.1

i go to upgrade to 2.3 to see  if work

Carlos
Title: Re: Android QOrbiter
Post by: golgoj4 on March 24, 2012, 10:51:56 pm
i have the same result on my cheap tablet.

i think this issue is related  to android 2.2  and 2.1

i go to upgrade to 2.3 to see  if work

Carlos

Did both of you guys install from the market or the website posted? The website is open gl builds only at the moment, until I post the openGL version there.

There non opengl version will stay with us as my phone falls into that category

Installing from the Google Market should work for low end phones though.

And lastly, a preview of whats coming for the onscreen UI

http://www.youtube.com/watch?v=8J3LqfOrugc

Now calling all skin designers!

-golgoj4
Title: Re: Android QOrbiter
Post by: ppiszc on March 24, 2012, 11:05:04 pm
golgoj4,

You are right - I installed app from lasmarthomes.com site.
After install app from market, now I can put the IP of core (I use 192.168.90.1) and #device, but after hit "Go!" the app exits (for the while on the screen there is message "Guessing android phone, Loading Phone skins").
After a few try I observe that app do not remember core IP nor device no. (in the device nomber there is usually some random data).   

Cheers,
ppiszc
Title: Re: Android QOrbiter
Post by: cfernandes on March 24, 2012, 11:18:39 pm
the same on my
Title: Re: Android QOrbiter
Post by: golgoj4 on March 25, 2012, 12:25:49 am
golgoj4,

You are right - I installed app from lasmarthomes.com site.
After install app from market, now I can put the IP of core (I use 192.168.90.1) and #device, but after hit "Go!" the app exits (for the while on the screen there is message "Guessing android phone, Loading Phone skins").
After a few try I observe that app do not remember core IP nor device no. (in the device nomber there is usually some random data).   

Cheers,
ppiszc


Ok thanks guys i will be looking into this further. Quick question Are you on wifi?

-golgoj4
Title: Re: Android QOrbiter
Post by: phenigma on March 25, 2012, 01:07:05 am
I suspect there was an update or something that wasnt transparent fully with ministro and that the library versions are mismatching. Let me know when you can

Everything's working on both my phones and the tablet now.

J.
Title: Re: Android QOrbiter
Post by: ppiszc on March 25, 2012, 01:11:33 am

Quote
Ok thanks guys i will be looking into this further. Quick question Are you on wifi?

I use wifi.

ppiszc
Title: Re: Android QOrbiter
Post by: cfernandes on March 25, 2012, 01:29:53 am
i use wifi too

carlos
Title: Re: Android QOrbiter
Post by: JaseP on March 25, 2012, 01:35:28 am
I am trying out qOrbiter, I too am on WiFi and am getting lock up when trying to load the Orbiter.
Title: Re: Android QOrbiter
Post by: golgoj4 on March 25, 2012, 05:31:47 am
I am trying out qOrbiter, I too am on WiFi and am getting lock up when trying to load the Orbiter.


Im assuming you ran the setup instructions
*What model phone
*What version installed? Google Market Or Website
*If you have the ability to, logcat or some other logging program like DDMS would be really helpful for me to see whats going on in the device.
*for everyone: What is the ip address of your core? Is it different from 192.168.80.1?

-golgoj4

http://developer.android.com/guide/developing/debugging/ddms.html

And look! opengl + shaders for the coming soon onscreen orbiter! http://youtu.be/SH9MMxfCOPY
Title: Re: Android QOrbiter
Post by: golgoj4 on March 26, 2012, 11:04:12 am
Keep in mind that my phone is the Galaxy S Glide (Captivate Glide in the US) and so it is not the same as the Galaxy S that everyone is used to.  This is a dual-core phone with a slide out keyboard.  Just in case there is confusion (I know most people are about the 'S' line).

Room selection:
  • On the Galaxy Tab 10.1: Images are now a little lower on the screen and I can read the names along the top. 
  • On Both: Selection seems to function properly and the scenarios on the screen change accordingly.  The name of the room on the room button does not change and always remains the original room.

User selection:
  • On Both: Selection seems to function properly but I can't actually tell as no user name is displayed anywhere to tell if it has actually changed.

k, I will stop mentioning it until you say it's in.  Just didn't know if was supposed to be there yet or not.

Cool the synopsis and performers lists expand/contrct.  On both the phones and tablet.

Okay, in the Now Playing screen for Audio:
  • On the Galaxy Tab 10.1: Artist Name and Track Name are showing correctly but the Album Name/Year are showing in blocks.
  • On the Galaxy S Glide Phones: Artist Name and Album Name/Year are showing correctly but the Track Name is showing in blocks.  :-p

Okay, in the Now Playing screen for Video:
  • On the Galaxy Tab 10.1: Video Name shows correctly, Genres show correctly, Performers show in all blocks and whatever the text is above the current time is showing in blocks as well.  Synopsis has some strange characters and blocks in it but mostly correct.  The 'image' that loads is not always the correct image it is often showing us the image for the last media track played or the first image loaded only, regardless of how many media tracks we continue to play.
  • On the Galaxy S Glide Phones: Everything seems to be displaying correctly.  The 'image' that loads is not always the correct image it is often showing us the image for the last media track played and not always updating.

Audio Lists (datagrids):
  • Galaxy Tab 10.1:Text seems to show fine for audio, when I choose a track to play and it brings up the info screen for the track the text on that screen is all in blocks except the name of the track. (The play/move/close screen).  Button text is fine.
  • Galaxy S Glide Phones: Images show, text is all blocks.  There are twice the number of actual tracks showing in the list. (16 tracks, shows 32 in the list).  The play/move/close screen shows text properly.

Video Lists (datagrids) essentially the same as for the audio:
  • Galaxy Tab 10.1:Text seems to show fine for video, when I choose a track to play and it brings up the info screen for the track all text on that screen is in blocks except the name of the track. (The play/move/close screen).  Button text is fine.
  • Galaxy S Glide Phones: Images show, text is all blocks.  There are twice the number of actual tracks showing in the list. (16 tracks, shows 32 in the list).  The play/move/close screen shows text properly.

'Power' Menu:
  • On Tab: Power menu opens, pressing buttons (display on/off, MD on/of) doesn't have any affect.
  • On Phone: Selection seems to function properly and the scenarios on the screen change accordingly.  The name of the room on the room button does not change and always remains the original room.

You're welcome.  Thank you for all the amazing work you're doing here!  I am only too happy to help!  My wife is really liking the idea of controlling the system from her phone and she is very tolerant of me breaking things if it will ultimately lead to an improved experience.  She's very forgiving.  :)

J.

*play all implemented across all skins
*some buttons made bigger
*tried to correct as much text as i could find
*made now playing on audio screen more readable
*im sure there is something else but its 2am and broham is tired :)

-cheers
golgoj4
Title: Re: Android QOrbiter
Post by: ppiszc on March 27, 2012, 09:49:58 pm
golgoj4

Please find below link to logcat from my droid made during QOrbiter starts.
h**p://pastebin.com/rP4MhBpn

If you need more logs just let me know.

ppiszc
Title: Re: Android QOrbiter
Post by: phenigma on April 04, 2012, 09:56:50 pm
*play all implemented across all skins
*some buttons made bigger
*tried to correct as much text as i could find
*made now playing on audio screen more readable
*im sure there is something else but its 2am and broham is tired :)

-cheers
golgoj4

Wow!  I'll update and check it out tonight and get back to you.

J.
Title: Re: Android QOrbiter
Post by: JaseP on May 12, 2012, 09:21:21 pm
Testing it out on my Acer Iconia A500...

OpenGL version from golgoj4's website. Runs very fast.

Issues (I don't know how many of these are works in progress and how many just don't work on my device, so I'll just list them all):
• It sometimes fails to load, requiring multiple restart attempts.
• Room selection scroller could use some kind of frame around it, one that indicates that you are suppose to scroll right and left, same for the menu bar during live TV playback.
• There appear to be no channel change buttons in Live TV playback, and the number pad doesn't do anything (additionally, the zero key doesn't register a press).
• Aspect change pop-up remains on screen in Live TV (but works in Video playback).
• Picture viewer screen crashes.

I haven't tried a lot more as I don't have every sub-system fully set up on my installation. So communications is not something I can test.
Title: Re: Android QOrbiter
Post by: WhateverFits on May 15, 2012, 12:36:50 am
Mine always goes to a black screen after the splash screen and, from there, exits. Vizio VTAB1008 on Honeycomb. It doesn't matter which APK I use, market or website, same results. It used to work just fine with only the occasional crash.
Title: Re: Android QOrbiter
Post by: golgoj4 on May 16, 2012, 02:04:05 am
Mine always goes to a black screen after the splash screen and, from there, exits. Vizio VTAB1008 on Honeycomb. It doesn't matter which APK I use, market or website, same results. It used to work just fine with only the occasional crash.

Where did you install the apk from? seems like its the open gl version, but it sounds like your device doesnt support the proper opengl profile

-golgoj4
Title: Re: Android QOrbiter
Post by: gadget on May 16, 2012, 01:28:25 pm
I have built a development environment and can build the qorbiter for desktop but the buttons don't seem to do anything except for users and rooms. What am i missing?

gadget
Title: Re: Android QOrbiter
Post by: WhateverFits on May 16, 2012, 07:22:33 pm
Where did you install the apk from? seems like its the open gl version, but it sounds like your device doesnt support the proper opengl profile

-golgoj4

I've tried both your website and the market versions. The market one used to work correctly. Could a change to the QML have caused this as I get the exact same response from both of the versions? Are there any files that I should delete? I deleted everything I could find and reinstalled but still same thing.

Next steps for me:
1. back date the QML in skins
2. hook up the Android debugger.
Title: Re: Android QOrbiter
Post by: stedaniels on May 18, 2012, 01:18:18 pm
Soo, might manage to get this baby up and running in a dev environment soon!

My first job will however be compiling all the Qt goodies for Android x86 ( I'm running ICS on O2 Jogglers )- the agony! A few people have made good progress on this so it shouldn't be too painful hopefully I'll get any patches needed rolled in upstream so that they can include x86 builds on the Ministro package servers.

I noticed Samsung have some cash to splash and wonder if qOrbiter would make a good entry in their apps competition?

http://www.smartappchallenge.com/eng/main.do

Bah - just read the details - the prizes are consumer judged.. i.e. the winner is based on downloads! Ahh well.

Steve
Title: Re: Android QOrbiter
Post by: ppiszc on May 19, 2012, 10:00:46 pm
golgoj4,

On my cheap tablet there are no directory Linuxmce and file config.xml on sdcard (qorbiter do not create such file and directory).
I've made copy the directory and file from HTC Desire S (where qorbiter works fine) but this do not change the behavior of qorbiter on the tablet - qorbiter do not remember IP nor device number and exits just after hit the "Go!" button.
So my conclusion is that qorbiter has probably problems with sdcard operations (reading and writing) on specific cheap tablets.
Is the source code of android qorbiter on svn ? I can try to dig in this area.

ppiszc.
Title: Re: Android QOrbiter
Post by: golgoj4 on May 20, 2012, 09:03:20 am
golgoj4,

On my cheap tablet there are no directory Linuxmce and file config.xml on sdcard (qorbiter do not create such file and directory).
I've made copy the directory and file from HTC Desire S (where qorbiter works fine) but this do not change the behavior of qorbiter on the tablet - qorbiter do not remember IP nor device number and exits just after hit the "Go!" button.
So my conclusion is that qorbiter has probably problems with sdcard operations (reading and writing) on specific cheap tablets.
Is the source code of android qorbiter on svn ? I can try to dig in this area.

ppiszc.

yep. its located here http://svn.linuxmce.org/trac.cgi/browser/branches/LinuxMCE-1004/src/qOrbiter/qOrbiter_src
I have encountered issues with the rooted devices and devices with custom roms if that of any help when jumping in. It related to the location of '/mnt/SDcard/' being different when thats the standard location for android.

-golgoj4
thanks for taking a look!
Title: Re: Android QOrbiter
Post by: dextaslab on May 20, 2012, 10:57:39 am
I too have a cheap-ass tablet running CyanogenMod 7, I've tried both software and GL versions and they both have failed, but I also noticed that going through the guide in the wiki, that the username for the qOrbiter in the Admin Website is set and as soon as I do a quick reload, it disappears, is this supposed to happen? The room name and other details remain.

The DDMS debugging log, config file contents and DCEROUTER.log for the latest release of the non-market version is here: http://www.modlog.net/wp-content/uploads/2012/05/log.txt
The tablet model is a Pendo Pad: TPC7SLV
It does create the Linuxmce folder when installed, and a default config, and if I change the number in it it does read it.
I have tried both horizontal and vertical modes, and turning off rotation

It loads the splash screen, displays the "Setting up Lmce" screen, if the orbiter number is correct, "go" goes red and it freezes and shutsdown. If the orbiter number is wrong it sudjests the correct device number which can slide up and down the screen, but when you click it "go" goes red and it freezes.

I have tried to set orbiter details in the web admin, run qOrbiterGenerator.php, quick reload, and then specified the username, but it still does the same.

From the DDMS log it looks like a code library related issue? libc.so vs libQtCore.so vs libqorbiter.so ? just a guess.
cheers hope this helps :-)
Title: Re: Android QOrbiter
Post by: golgoj4 on May 20, 2012, 05:36:41 pm
I too have a cheap-ass tablet running CyanogenMod 7, I've tried both software and GL versions and they both have failed, but I also noticed that going through the guide in the wiki, that the username for the qOrbiter in the Admin Website is set and as soon as I do a quick reload, it disappears, is this supposed to happen? The room name and other details remain.

The DDMS debugging log, config file contents and DCEROUTER.log for the latest release of the non-market version is here: http://www.modlog.net/wp-content/uploads/2012/05/log.txt
The tablet model is a Pendo Pad: TPC7SLV
It does create the Linuxmce folder when installed, and a default config, and if I change the number in it it does read it.
I have tried both horizontal and vertical modes, and turning off rotation

It loads the splash screen, displays the "Setting up Lmce" screen, if the orbiter number is correct, "go" goes red and it freezes and shutsdown. If the orbiter number is wrong it sudjests the correct device number which can slide up and down the screen, but when you click it "go" goes red and it freezes.

I have tried to set orbiter details in the web admin, run qOrbiterGenerator.php, quick reload, and then specified the username, but it still does the same.

From the DDMS log it looks like a code library related issue? libc.so vs libQtCore.so vs libqorbiter.so ? just a guess.
cheers hope this helps :-)


And this is what makes me rage about android. After looking around and doing some investigation, there really shouldn't be anything stopping the show except the device maker cut some corners somewhere. the segfault right around the dce initialization is particularly telling. The bad network functions are all me, i take 'credit' for that part. But when it does make it to loading, it seems like its hitting a wall loading some of the more complex libraries.

Lets try an orbital strike...
1) uninstall QOrbiter
2) clear the data from ministro. Under settings->applications->ministro->clear data. Or uninstall it.
3) reinstall qorbiter. Non open gl.
4)please report back.

the crashes i saw in the dump lead me to one of two conclusions: either there is a lib mismatch or the device is running into a wall resource wise. which seems crazy, but ive seen it on my phone.

-golgoj4
Title: Re: Android QOrbiter
Post by: dextaslab on May 22, 2012, 12:18:15 pm
Uninstalled qOrbiter and ministro, deleted Linuxmce folder, and reinstalled from Market, the results are the same, just have to run DDMS to get log.

can I get a confirmation on this: "... the username for the qOrbiter in the Admin Website is set and as soon as I do a quick reload, it disappears, is this supposed to happen? "

Cheers
Title: Re: Android QOrbiter
Post by: dextaslab on May 25, 2012, 03:16:17 pm
Uninstalled qOrbiter and ministro, deleted Linuxmce folder, and reinstalled from Market, the results are the same, just have to run DDMS to get log.

can I get a confirmation on this: "... the username for the qOrbiter in the Admin Website is set and as soon as I do a quick reload, it disappears, is this supposed to happen? "

Cheers
New log is here: http://www.modlog.net/wp-content/uploads/2012/05/log2.txt

Looks pretty much the same :-(
Title: Re: Android QOrbiter
Post by: pedplar on May 26, 2012, 12:07:51 pm
I to cant get user to stick in the webadmin.  As soon as I reload router, the user is blank. 



Title: Re: Android QOrbiter
Post by: dextaslab on June 08, 2012, 02:23:50 pm
After doing a long over due reinstall, the name now sticks in the admin webpage
Title: Re: Android QOrbiter
Post by: dextaslab on June 30, 2012, 08:28:37 am
Got it installed on a Galaxy S2 and HTC Desire XL although it only displays 9 videos (8 of them are repeats) and 4 audio files in the listings and the video genre's are music based: eg; Jazz, Electronica, etc, which the buttons dont work, I'm not sure if these issues are what I should be see'ing or if it's qerk of my setup?

Cheers
Title: Re: Android QOrbiter
Post by: golgoj4 on July 07, 2012, 02:27:21 am
Got it installed on a Galaxy S2 and HTC Desire XL although it only displays 9 videos (8 of them are repeats) and 4 audio files in the listings and the video genre's are music based: eg; Jazz, Electronica, etc, which the buttons dont work, I'm not sure if these issues are what I should be see'ing or if it's qerk of my setup?

Cheers

Stay tuned, some android skin updates this weekend!

golgoj4
Title: Re: Android QOrbiter
Post by: maverick0815 on July 08, 2012, 05:33:26 pm
Hello golgoj4

I wanted to try out one of your nightly builds, but it appears the url is no longer working. did you get another website? www.lasmarthomes.com is no longer available...
Title: Re: Android QOrbiter
Post by: JaseP on July 08, 2012, 05:46:15 pm
He's got a website at:

http://www.langstonball.com/

Title: Re: Android QOrbiter
Post by: maverick0815 on July 08, 2012, 08:53:28 pm
Thank you, but that is his original website, which as it seems, doesn't hold the nightly builds.
Title: Re: Android QOrbiter
Post by: Kezza on July 08, 2012, 11:16:55 pm
Using links from here? Link works for me so maybe site was down.

http://wiki.linuxmce.org/index.php/Android_Orbiter
Title: Re: Android QOrbiter
Post by: golgoj4 on July 09, 2012, 12:33:58 am
site is down, will return shortly

-golgoj4
Title: Re: Android QOrbiter
Post by: polly on July 10, 2012, 01:45:18 pm
Hey ....

just installed Android 4.0.3 in Virtualbox. So far android works great but after installing QOrbiter and Ministro2 i got a
"Ministro can not Satisfy your applications dependencies" while Ministro tried to download required libraries...

this could help maybe ?
https://groups.google.com/forum/#!topic/android-qt/7w1GjZ0lPJA

to be honest, i have no idea where the problem is, but i'm glad to help...

Cheers,
ochorocho
Title: Re: Android QOrbiter
Post by: JaseP on July 10, 2012, 05:37:25 pm
Is your VB instance set up as an Android-x86 VM or as an emulated ARM environment? Golgoj4 hasn't done an X86 target build yet (I don't think), and I get the same error when I try putting qOrbitor on my eee PC running the Android-X86 4.x ICS release candidate.
Title: Re: Android QOrbiter
Post by: polly on July 10, 2012, 05:39:35 pm
yep ... it is setup as an Android-x86 VM ...
Title: Re: Android QOrbiter
Post by: JaseP on July 10, 2012, 06:11:00 pm
yep ... it is setup as an Android-x86 VM ...

Not supported yet,... But it should handle a web orbiter fine... I PM'd Golgoj4 about it a little while back, and he said he look into x86 based Android as a target,... but I told him there was no rush, at the moment.

PS: Old netbooks, especially smaller ones that are sitting unused, make great Android-X86 devices...
Title: Re: Android QOrbiter
Post by: polly on July 10, 2012, 07:20:27 pm
Hey ...
first of all thx, for offering advanced information :-)

Currently i have only a iPad and a iPhone 3GS to test. :-(

So my plan was to use any emulator to get QOrbiter working. But the adnroid emu does a bad job on OS X.
It slows down the whole mac to an almost unusable speed, i don't want to talk about the speed of the android emu. I can slide to unlock but thats it.

If you know how to run an android emu on Mac OS please let me know !

cheers,
ochorocho
Title: Re: Android QOrbiter
Post by: JaseP on July 11, 2012, 12:19:34 am
Don't know about Mac stuff, sorry.

But is possible to emulate ARM on Android-X86,... At least experimentally...

See here:
http://www.buildroid.org/blog/?p=198

Note: I have not tried to duplicate this guy's work, nor was I actually planning to do so. This is advanced kernel rebuilding stuff, not my idea of a free evening's tinkering...

PS: It's apparently possible to use VirtualBox and qemu to emulate ARM in order to build/develop for ARM based Android as well.
Title: Re: Android QOrbiter
Post by: polly on July 11, 2012, 01:31:19 pm
hey ....

my android emulator is up and running with a good performance. :-)
i seems like i did NOT download the macOS version of the Emulator!

MAKE SURE YOU DOWNLOADED THE CORRECT VERSION!! :-)


i've installed Ministro II and QOrbiter app (from here: http://www.lasmarthomes.com/QOrbiter-release.apk ).

on the first run of qorbiter it asks for additional libs to be installed, so i installed the additional libs.
After installing the additional qorbiter goes black and thats it.

I tried with Android 2.3.3, 3.0.1, 4.0.1 .

Any information to get around this issue or debug it is greatly appreciated!

Thanks.

Cheers,
ochorocho

Title: Re: Android QOrbiter
Post by: golgoj4 on July 11, 2012, 02:31:51 pm
hey ....

my android emulator is up and running with a good performance. :-)
i seems like i did NOT download the macOS version of the Emulator!

MAKE SURE YOU DOWNLOADED THE CORRECT VERSION!! :-)


i've installed Ministro II and QOrbiter app (from here: http://www.lasmarthomes.com/QOrbiter-release.apk ).

on the first run of qorbiter it asks for additional libs to be installed, so i installed the additional libs.
After installing the additional qorbiter goes black and thats it.

I tried with Android 2.3.3, 3.0.1, 4.0.1 .

Any information to get around this issue or debug it is greatly appreciated!

Thanks.

Cheers,
ochorocho


you have the skins and such already installed on your core?

-golgoj4
Title: Re: Android QOrbiter
Post by: polly on July 11, 2012, 02:38:16 pm
DOH! ....

i'm currently not connected to the Core ... i'm @work.

i installed skins and stuff as described here:
http://wiki.linuxmce.org/index.php/Android_Orbiter

i will give it another try when i'm back home!

Thx.

Cheers,
ochorocho
Title: Re: Android QOrbiter
Post by: wombiroller on July 24, 2012, 02:03:28 pm
Hey golgoj4,

Thought i'd try out the nightly. Followed the wiki (orb, user, room, size, svn, skins, config generation etc) however after loading briefly - the app just quits (goes back to the homescreen). Using a galaxy S2 (ICS 4.0.4). Logcat shows this if it is helpful:
http://pastebin.com/sHu5bUvL
Code: [Select]
W/Qt      (12640): qrc:android/Splash.qml:35: ReferenceError: Can't find variable: dcerouter
W/Qt      (12640): QObject::connect: Cannot connect DCE::qOrbiter::screenSaverImages(QStringList) to (null)::setImageList(QStringList)
W/Qt      (12640): QObject::connect: Cannot connect (null)::requestNewImage(QString) to DCE::qOrbiter::getScreenSaverImage(QString)
W/Qt      (12640): QObject::connect: Cannot connect DCE::qOrbiter::currentScreenSaverImage(const uchar*,int) to (null)::setImageData(const uchar*,int)
W/Qt      (12640): Object::connect: Attempt to bind non-signal orbiterWindow::close()
D/Qt      (12640): Device Id changed to: -1
D/Qt      (12640): Initializing connection
D/Qt      (12640): No hostname, checking installation
D/Qt      (12640): Found installation, starting
F/libc    (12640): Fatal signal 11 (SIGSEGV) at 0x000002b6 (code=1)
I/DEBUG   ( 3470): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG   ( 3470): Build fingerprint: 'samsung/GT-I9100/GT-I9100:4.0.3/IML74K/XXLPQ:user/release-keys'
I/DEBUG   ( 3470): pid: 12640, tid: 12658  >>> org.linuxmce.qorbiter <<<
I/DEBUG   ( 3470): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 000002b6

Let me know if there is anything else you need/want to help.

Cheers,
WR.
Title: Re: Android QOrbiter
Post by: wombiroller on July 24, 2012, 02:10:36 pm
Umm - nevermind! I noticed that the device id flashes up as -1, though you don't get a chance to change it...

So I manually edited the config.xml on the SD card and it works! Yay! Time to play - thanks again :)
Title: Re: Android QOrbiter
Post by: golgoj4 on July 25, 2012, 08:00:50 am
Hey golgoj4,

Thought i'd try out the nightly. Followed the wiki (orb, user, room, size, svn, skins, config generation etc) however after loading briefly - the app just quits (goes back to the homescreen). Using a galaxy S2 (ICS 4.0.4). Logcat shows this if it is helpful:
http://pastebin.com/sHu5bUvL
Code: [Select]
W/Qt      (12640): qrc:android/Splash.qml:35: ReferenceError: Can't find variable: dcerouter
W/Qt      (12640): QObject::connect: Cannot connect DCE::qOrbiter::screenSaverImages(QStringList) to (null)::setImageList(QStringList)
W/Qt      (12640): QObject::connect: Cannot connect (null)::requestNewImage(QString) to DCE::qOrbiter::getScreenSaverImage(QString)
W/Qt      (12640): QObject::connect: Cannot connect DCE::qOrbiter::currentScreenSaverImage(const uchar*,int) to (null)::setImageData(const uchar*,int)
W/Qt      (12640): Object::connect: Attempt to bind non-signal orbiterWindow::close()
D/Qt      (12640): Device Id changed to: -1
D/Qt      (12640): Initializing connection
D/Qt      (12640): No hostname, checking installation
D/Qt      (12640): Found installation, starting
F/libc    (12640): Fatal signal 11 (SIGSEGV) at 0x000002b6 (code=1)
I/DEBUG   ( 3470): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
I/DEBUG   ( 3470): Build fingerprint: 'samsung/GT-I9100/GT-I9100:4.0.3/IML74K/XXLPQ:user/release-keys'
I/DEBUG   ( 3470): pid: 12640, tid: 12658  >>> org.linuxmce.qorbiter <<<
I/DEBUG   ( 3470): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 000002b6

Let me know if there is anything else you need/want to help.

Cheers,
WR.

interesting, so you just changed the device id to an existing one and it worked?

its supposed to show a popup of the existing qOrbiters.
-golgoj4
Title: Re: Android QOrbiter
Post by: slampt on July 25, 2012, 04:15:26 pm
Just wondering if anyone has got this working on a HP Touchpad w/ android (CM9)?
I have just got my touchpad back, and have been trying to get it to work but to no avail :/
Trying to get debug logs out of it now..

Slampt
Title: Re: Android QOrbiter
Post by: slampt on July 26, 2012, 07:04:53 am
Just an update in the hopes someone may be able to help me.
I have been trying to figure out why qOrbiter would work when it is freshly installed (config changed to suit my setup). But fail every time after...

These are my logs;

Success start : http://pastebin.com/raw.php?i=ss2t5bhQ

When pressing Exit Orbiter : http://pastebin.com/raw.php?i=JDp1idZd

Failed start : http://pastebin.com/raw.php?i=4TAvQUBs

I will keep plodding away and report here if I am successful :P

Cheers
Slampt
Title: Re: Android QOrbiter
Post by: huh on July 27, 2012, 05:56:36 am
I'm having trouble with my touchpad as well- qorbiter is grabbing device id "45" even through only have qorbiter devices "56" and "75".  I don't have a device 45 or anything really even close.  On one occasion, I was able to halt the qorbiter starting and was able to type in "56" as my device id.  I hitting "go" changed the button color to green, but then the app froze.

Any thoughts or suggestions?
Title: Re: Android QOrbiter
Post by: golgoj4 on July 28, 2012, 02:43:53 am
I'm having trouble with my touchpad as well- qorbiter is grabbing device id "45" even through only have qorbiter devices "56" and "75".  I don't have a device 45 or anything really even close.  On one occasion, I was able to halt the qorbiter starting and was able to type in "56" as my device id.  I hitting "go" changed the button color to green, but then the app froze.

Any thoughts or suggestions?


I dont. What should be happening is that device id is set to -1 by default. this should cause it to pop up a list of existing qOrbiter, you select the right one and it starts. it saves the device id so next time it will already have it. Anything else happening is outside of what happens on the android devices i  test. Is there anyways to get a more solid rom onto these touchpads, because its clearly borking up a lot. It should not be setting random device numbers. that means that it cant read from the SD card more than likely, which means you will have to fight with it every time.

-golgoj4
Title: Re: Android QOrbiter
Post by: wombiroller on July 29, 2012, 10:50:28 am
interesting, so you just changed the device id to an existing one and it worked?

its supposed to show a popup of the existing qOrbiters.
-golgoj4
Exactly like that. I didn't get a pop-up that i could see. I could see the -1 but not edit it.. and it would only give me a few sec before crashing. xml edit worked immediately though.
Title: Re: Android QOrbiter
Post by: golgoj4 on July 29, 2012, 03:32:13 pm
Exactly like that. I didn't get a pop-up that i could see. I could see the -1 but not edit it.. and it would only give me a few sec before crashing. xml edit worked immediately though.

your running the most recent update, qml included?

-golg0j4
Title: Re: Android QOrbiter
Post by: wombiroller on August 03, 2012, 07:10:44 am
your running the most recent update, qml included?

-golg0j4

Pretty sure I was - I installed the snapshot and everything else for the first time on the 24th (via wiki instuctions), same day I posted... Happy to uninstall and retest if you want me too?  :)
Title: Re: Android QOrbiter
Post by: Medrawd on September 05, 2012, 01:54:26 am
I can't make user name stick. I've just reinstalled 1004 from beta, recomended snapshot, latest snapshot and now I've done internet installation and on each user name is clear after reloading the router.
Title: Re: Android QOrbiter
Post by: golgoj4 on September 05, 2012, 03:55:44 am
This currently, while nice, is somewhat irrelevant. QOrbiter currently doesnt support any of the user related features on android so while i understand the annoyance, its frankly low on the importance list until users become important.

Right now im trying to solve the media player / embedded ip phone connundrum so its a little low on my list.

The real question is, what phone do you have, and what version of Android are you running. Im running up against an issue where higher end Android devices have issues with our opengl settings, but not mid range and slightly older ones.

so whatcha got?

-golgoj4
Title: Re: Android QOrbiter
Post by: Medrawd on September 05, 2012, 04:56:44 am
I've got Samsung Galaxy S running JellyBean.
Title: Re: Android QOrbiter
Post by: Medrawd on September 05, 2012, 05:07:34 am
Qorbiter on phone some times(5-10%) "works" but all popup menus are empty and buttons for selecting user and room are showing lorem ipsum.
Title: Re: Android QOrbiter
Post by: golgoj4 on September 05, 2012, 08:37:13 am
ok, something sounds like its going very wrong.

you have
1) updated the skins
2) got the latest from the market?

Have you tried doing a qOrbiter Regen? i.e. http://192.168.80.1/lmce-admin/qOrbiterGenerator.php?d=<yourdevice#>

Im very curious because menus are empty because there is nothing in the room / ea. I will look into this further...

-golgoj4
Title: Re: Android QOrbiter
Post by: Medrawd on September 05, 2012, 02:40:37 pm
Yes I've done everything.
Title: Re: Android QOrbiter
Post by: Medrawd on September 05, 2012, 02:41:44 pm
I just have installed nightly insted of the market one and it is working.
Title: Re: Android QOrbiter
Post by: ppiszc on October 02, 2012, 09:54:33 pm
Sorry for very very long delay but I unfortunately flashed device using wrong image and I had my device totally bricked..
I had to find proper flash image to make alive my china android tablet.
I found three issues connected with qOrbiter (Ticket #1585).
Let me know if somene would like to check apk with fixes (I have apk for droid based on armv5).

Cheers,
ppiszc
Title: Re: Android QOrbiter
Post by: _if_ on October 25, 2012, 07:54:52 pm
I'm on a galaxy tab 7" Android 2.2.
I followed the wiki, but get an error when running qorbiter. It can't find the file: "Screen_1.qml".
The file is located in /var/www/lmce-admin/skins/android/tablet/default/screens, thats where it should be right? Is read-access enough or does it want to write as well?

thanks
IF
Title: Re: Android QOrbiter
Post by: tompin2 on October 31, 2012, 01:57:44 pm
Hello to all,

I have a low end COBY kyros MID7014, it as android 2.3.3 and I can't get it to work because I can't find the folder with the config file.  Im unable to use the market version because it says that that software is not compatible with my device so I used the website version.  Why there is no config file on the sd?

Cheers,

T
Title: Re: Android QOrbiter
Post by: polly on October 31, 2012, 02:08:19 pm
hm.... in my case the config.xml was located somwhere on the device....

i will check for the config later ...

EDIT: config.xml is located in /mnt/sdcard/Linuxmce as normal ...
Title: Re: Android QOrbiter
Post by: WhateverFits on October 31, 2012, 07:23:52 pm
I keep getting the same thing on my Galaxy Nexus phone.

I'm on a galaxy tab 7" Android 2.2.
I followed the wiki, but get an error when running qorbiter. It can't find the file: "Screen_1.qml".
The file is located in /var/www/lmce-admin/skins/android/tablet/default/screens, thats where it should be right? Is read-access enough or does it want to write as well?

thanks
IF
Title: Re: Android QOrbiter
Post by: golgoj4 on November 01, 2012, 12:15:25 am
oi vey

ok. im kinda knee deep in dealing with raspberry pi port
but

Questions:
Are any of these running modified versions of android?

I have discovered some nasty low level bugs that im fixing.
*Read Access should be enough
*Config is always installed to /mnt/sdcard/Linuxmce
*I Have tested this on an android 2.3.6 device. I will try and find a 2.2 one. (Note that would be the 4th device ive purchased for tests. this gets expensive!)
*Feel free to riff on my work, but please make it clear when re-distributing _why_ you are re-distributing, i.e. because you have a modded phone. I support only stock Android. Sorry but you see the multitude of problems with sticking with stock versions!

I will try to respond expeditiously. Im normally in irc from 4:00 pst - 10:pm pst m-f
golgoj4
Title: Re: Android QOrbiter
Post by: golgoj4 on November 01, 2012, 12:18:38 am
One other thing. I hate this network loading nonsense. I really do. How would people feel if the skins were installed to the sd card? Remember, it could take up a lot of space eventually. Right now, QOrbiter itself is about 30mb, another 30 for libraries. The android skins are currently about 60 mb. If there is no real opposition this might be in the next release.

-golgoj4
Title: Re: Android QOrbiter
Post by: WhateverFits on November 01, 2012, 12:52:38 am
I'm running completely stock Galaxy Nexus running Jellybean 4.1 as well as a Honeycomb Vizio VTAB1008. The Nexus fails to find the file and the Vizio just crashes. Oh, wait. My Nexus is working right now. It works surprisingly well over the interwebs.

I don't mind the network loading of skins as it makes for easy updates and testing. Having them on the phone is faster though. If you are concerned about space, then the best way would be to only have the files on the device for the skin that the user has chosen. Maybe give a skin selector that then downloads the entire skin from the server. Sounds like a "later" type of issue. Many of the skin managers I've seen so far allow one to install packages from the store for the different skins. A person can just install the skins they want.

Also, can you just emulate the different versions of Android?

One last thing, I noticed that there is a problem triggering the events when a button is pressed. For example, when I click on Video the system powers on my receiver and changes all the inputs correctly. This doesn't happen on this orbiter. Ideas?
Title: Re: Android QOrbiter
Post by: tompin2 on November 01, 2012, 05:01:15 am
hm.... in my case the config.xml was located somwhere on the device....

i will check for the config later ...

EDIT: config.xml is located in /mnt/sdcard/Linuxmce as normal ...
hi, in my case there is no linuxmce folder at the sd card, thar is what is driving me crazy. Can someone ppost the app that is on the market so i can download it?
Title: Re: Android QOrbiter
Post by: _if_ on November 01, 2012, 11:35:47 am
@golgoj4: I'm trying to upgrade my firmware and see if it works there.
I just need to set up a damn windows box for that   ::)
Title: Re: Android QOrbiter
Post by: golgoj4 on November 02, 2012, 01:35:59 am
hi, in my case there is no linuxmce folder at the sd card, thar is what is driving me crazy. Can someone ppost the app that is on the market so i can download it?

Thats a full stop.

What version of Android are you running? Sounds like a modded version as I have no experience the config not being placed in its location on standard android.

-golgoj4
Title: Re: Android QOrbiter
Post by: dextaslab on November 02, 2012, 03:00:26 am
Thats a full stop.

What version of Android are you running? Sounds like a modded version as I have no experience the config not being placed in its location on standard android.

-golgoj4
Agreed, I had the same issue running Android on an N900 - modded version = no config file, I believe it was a permissions issue.
Title: Re: Android QOrbiter
Post by: tompin2 on November 02, 2012, 11:46:18 pm
Thats a full stop.

What version of Android are you running? Sounds like a modded version as I have no experience the config not being placed in its location on standard android.

-golgoj4

Hi,

It is 2.3.  I´ll check if there is a permission issue although it asks for sd writing permission and it says yes.  So probably it is not the version of qorbiter, it is my tablet.

Dextaslab, where you able to solve the permission issue??

Cheers,

T
Title: Re: Android QOrbiter
Post by: golgoj4 on November 03, 2012, 01:40:23 am
Agreed, I had the same issue running Android on an N900 - modded version = no config file, I believe it was a permissions issue.

Its more likely that the standard location was not ported over for whatever reason. The SD card should be writable.

-golgoj4
Title: Re: Android QOrbiter
Post by: golgoj4 on November 04, 2012, 05:31:47 pm
deb.linuxmce.org/QOrbiter-release.apk

download the latest from here from now on

-golgoj4
Title: Re: Android QOrbiter
Post by: golgoj4 on November 13, 2012, 01:39:05 am
http://dl.dropbox.com/u/33136233/Android-ICS-apk/QOrbiter-release.apk

New release, should support more SD card locations.

You will need to update your qml prior to this.

If you dont update the apk, dont update the skins. The api will not match

-Langston
Title: Re: Android QOrbiter
Post by: huh on December 30, 2012, 01:36:01 am
I couldn't get qorbiter to load on my Samsung Galaxy S2- on start it would just say it couldn't find my core.  So went in a manually deleted my config.xml file (that by the time stamp was created months ago even though I just installed the latest qorbiter) and a new config file was created and I can now connect to the core.  FYI for anyone else that may run into this.
Title: Re: Android QOrbiter
Post by: _if_ on December 30, 2012, 10:28:18 pm
Same here - I had qorbiter running at my galaxy tab and then got a popup that an update was available. after that update it wouldn't start anymore.

IF
Title: Re: Android QOrbiter
Post by: WhateverFits on January 09, 2013, 09:49:25 pm
Grabbed the latest skins and orbiter and looking good! I'm running the tablet version on my Galaxy Nexus. Any config way to change the UI? I'd like to test out the phone version too without renaming folders...
Title: Re: Android QOrbiter
Post by: bushtech on January 10, 2013, 12:27:37 am
Reportback: HTC Desire HD (Android 2.3.5) Updated the skins, downloaded apk from dropbox, ran instruction in weborbiter.

Orbiter loads fine, get to the stair screen with the 6 buttons in centre and 4 buttons bottom.

Power & exit buttons work, can only test media, the media buttons come up but clicking on Video or audio has no result, button goes blue but nothing happens

I have not set up a floor plan, don't know if that's important
Title: Re: Android QOrbiter
Post by: maverick0815 on January 13, 2013, 01:35:16 pm
I got an htc evo3d(ICS) running the latest (I hope) version of qorbiter- setup as per wiki-instructions. When I start qorbiter, I get a rotating bar and then a message, that it couldn't connect the dcerouter. The first time I put the devicenumber and it connects, but the initial message always shows first.
Other than a few graphic-glitches I have not much to report....for example the first two buttons at the bottom are garbled.
Title: Re: Android QOrbiter
Post by: golgoj4 on January 20, 2013, 04:25:18 pm
I got an htc evo3d(ICS) running the latest (I hope) version of qorbiter- setup as per wiki-instructions. When I start qorbiter, I get a rotating bar and then a message, that it couldn't connect the dcerouter. The first time I put the devicenumber and it connects, but the initial message always shows first.
Other than a few graphic-glitches I have not much to report....for example the first two buttons at the bottom are garbled.

The initial message is supposed to be there. Its basically searching for your dcerouter because the gui is loaded over the network as opposed to trying to cram the gui in your phone (300+ screens and images per skin!). I apologize for the rockiness, but we are really trying to address these problems i swear :)

-golgoj4

P.S. The latest can always be found @ http://deb.linuxmce.org/QOrbiter-Release.apk
Title: Re: Android QOrbiter
Post by: jeangot on January 28, 2013, 03:31:01 am
Hello,

I hope that I am posting this to the right thread. Wasn't sure if I should start a new one or not.
I am trying to run the latest Qorbiter version 0810410 (downloaded from the URL in previous messages) on an Asus tablet running Android 4.1.1

When launching Qorbiter, it connects to my Core and communicates with it, but eventually just dies (without ever showing me any UI). Here are the logs from my core. Do they tell us what the problem might be? It is saying something about "No streams". Otherwise, are there other logs available on the Android side that I could look at?

05   01/27/13 18:29:42.254      Router::RemoveAndDeleteSocket 0x44176700 271 <0x5e2f8b70>
08   01/27/13 18:29:42.290      Received Message from 271 (Master Bedroom Android Orbiter / Master Bedroom) to 4 (General Info Plug-in / Computer Closet), type 1 id 71 Command:Request File, retry none, parameters: <0x96efdb70>
08   01/27/13 18:29:42.290        Parameter 13(Filename): /var/tmp/271conf.xml <0x96efdb70>
08   01/27/13 18:29:42.547      Received Message from 271 (Master Bedroom Android Orbiter / Master Bedroom) to Orbiter Plug-in(9), type 1 id  59 Command:Set Entertainment Area, retry none, parameters: <0x4ead9b70>
08   01/27/13 18:29:42.547        Parameter 45(PK_EntertainArea): 2 <0x4ead9b70>
05   01/27/13 18:29:42.547      Orbiter_Plugin::FireFollowMe mask M orb 271 user 0 r/e 2 r/e left 2 <0x84ed9b70>
08   01/27/13 18:29:42.548      Received Message from 9 (Orbiter Plug-in / Computer Closet) to 271 (Master Bedroom Android Orbiter / Master Bedroom), type 1 id 26 Command:Set Bound Icon, retry none, parameters: <0xa52bcb70>
08   01/27/13 18:29:42.548        Parameter 5(Value To Assign): 0 <0xa52bcb70>
08   01/27/13 18:29:42.548        Parameter 9(Text):  <0xa52bcb70>
08   01/27/13 18:29:42.548        Parameter 14(Type): media_private <0xa52bcb70>
08   01/27/13 18:29:42.548      Received Message from 10 (Media Plug-in / Computer Closet) to 271 (Master Bedroom Android Orbiter / Master Bedroom), type 1 id 242 Command:Set Now Playing, retry none, parameters: <0xa1ab5b70>
08   01/27/13 18:29:42.548        Parameter 3(PK_DesignObj):  <0xa1ab5b70>
08   01/27/13 18:29:42.548        Parameter 5(Value To Assign):  <0xa1ab5b70>
08   01/27/13 18:29:42.548        Parameter 9(Text):  <0xa1ab5b70>
08   01/27/13 18:29:42.548        Parameter 29(PK_MediaType): 0 <0xa1ab5b70>
08   01/27/13 18:29:42.548        Parameter 41(StreamID): 0 <0xa1ab5b70>
08   01/27/13 18:29:42.548        Parameter 48(Value): 0 <0xa1ab5b70>
08   01/27/13 18:29:42.548        Parameter 50(Name):  <0xa1ab5b70>
08   01/27/13 18:29:42.548        Parameter 103(List PK Device):  <0xa1ab5b70>
08   01/27/13 18:29:42.548        Parameter 120(Retransmit): 0 <0xa1ab5b70>
08   01/27/13 18:29:42.550      Received Message from 271 (Master Bedroom Android Orbiter / Master Bedroom) to Orbiter Plug-in(9), type 1 id  77 Command:Set Current Room, retry none, parameters: <0x4ead9b70>
08   01/27/13 18:29:42.550        Parameter 57(PK_Room): 1 <0x4ead9b70>
05   01/27/13 18:29:42.550      Orbiter_Plugin::FireFollowMe mask LCTS orb 271 user 0 r/e 1 r/e left 1 <0x84ed9b70>
08   01/27/13 18:29:42.552      Received Message from 271 (Master Bedroom Android Orbiter / Master Bedroom) to 4 (General Info Plug-in / Computer Closet), type 1 id 246 Command:Set Device Data, retry none, parameters: <0x96efdb70>
08   01/27/13 18:29:42.552        Parameter 2(PK_Device): 271 <0x96efdb70>
08   01/27/13 18:29:42.552        Parameter 5(Value To Assign): 1 <0x96efdb70>
08   01/27/13 18:29:42.552        Parameter 52(PK_DeviceData): 3 <0x96efdb70>
08   01/27/13 18:29:42.560      Received Message from 271 (Master Bedroom Android Orbiter / Master Bedroom) to 9 (Orbiter Plug-in / Computer Closet), type 1 id 255 Command:Orbiter Registered, retry none, parameters: <0x96efdb70>
08   01/27/13 18:29:42.560        Parameter 8(On/Off): 1 <0x96efdb70>
08   01/27/13 18:29:42.560        Parameter 17(PK_Users): 0 <0x96efdb70>
08   01/27/13 18:29:42.560        Parameter 45(PK_EntertainArea): 2 <0x96efdb70>
08   01/27/13 18:29:42.560        Parameter 57(PK_Room): 1 <0x96efdb70>
08   01/27/13 18:29:42.560      Received Message from 13 (Security Plug-in / Computer Closet) to 271 (Master Bedroom Android Orbiter / Master Bedroom), type 1 id 26 Command:Set Bound Icon, retry none, parameters: <0x9c0fcb70>
08   01/27/13 18:29:42.560        Parameter 5(Value To Assign): 1 <0x9c0fcb70>
08   01/27/13 18:29:42.560        Parameter 9(Text):  <0x9c0fcb70>
08   01/27/13 18:29:42.560        Parameter 14(Type): housemode0 <0x9c0fcb70>
08   01/27/13 18:29:42.560      Received Message from 13 (Security Plug-in / Computer Closet) to 271 (Master Bedroom Android Orbiter / Master Bedroom), type 1 id 26 Command:Set Bound Icon, retry none, parameters: <0x9c0fcb70>
08   01/27/13 18:29:42.560        Parameter 5(Value To Assign): 0 <0x9c0fcb70>
08   01/27/13 18:29:42.560        Parameter 9(Text):  <0x9c0fcb70>
08   01/27/13 18:29:42.560        Parameter 14(Type): monitormode <0x9c0fcb70>
08   01/27/13 18:29:42.561      Received Message from 9 (Orbiter Plug-in / Computer Closet) to 271 (Master Bedroom Android Orbiter / Master Bedroom), type 1 id 26 Command:Set Bound Icon, retry none, parameters: <0xa52bcb70>
08   01/27/13 18:29:42.561        Parameter 5(Value To Assign): 0 <0xa52bcb70>
08   01/27/13 18:29:42.561        Parameter 9(Text):  <0xa52bcb70>
08   01/27/13 18:29:42.561        Parameter 14(Type): follow_light <0xa52bcb70>
08   01/27/13 18:29:42.561      Received Message from 9 (Orbiter Plug-in / Computer Closet) to 271 (Master Bedroom Android Orbiter / Master Bedroom), type 1 id 26 Command:Set Bound Icon, retry none, parameters: <0xa52bcb70>
08   01/27/13 18:29:42.561        Parameter 5(Value To Assign): 0 <0xa52bcb70>
08   01/27/13 18:29:42.561        Parameter 9(Text):  <0xa52bcb70>
08   01/27/13 18:29:42.561        Parameter 14(Type): follow_media <0xa52bcb70>
08   01/27/13 18:29:42.561      Received Message from 9 (Orbiter Plug-in / Computer Closet) to 271 (Master Bedroom Android Orbiter / Master Bedroom), type 1 id 26 Command:Set Bound Icon, retry none, parameters: <0xa52bcb70>
08   01/27/13 18:29:42.561        Parameter 5(Value To Assign): 0 <0xa52bcb70>
08   01/27/13 18:29:42.561        Parameter 9(Text):  <0xa52bcb70>
08   01/27/13 18:29:42.561        Parameter 14(Type): follow_climate <0xa52bcb70>
08   01/27/13 18:29:42.561      Received Message from 9 (Orbiter Plug-in / Computer Closet) to 271 (Master Bedroom Android Orbiter / Master Bedroom), type 1 id 26 Command:Set Bound Icon, retry none, parameters: <0xa52bcb70>
08   01/27/13 18:29:42.561        Parameter 5(Value To Assign): 0 <0xa52bcb70>
08   01/27/13 18:29:42.561        Parameter 9(Text):  <0xa52bcb70>
08   01/27/13 18:29:42.561        Parameter 14(Type): follow_security <0xa52bcb70>
08   01/27/13 18:29:42.561      Received Message from 9 (Orbiter Plug-in / Computer Closet) to 271 (Master Bedroom Android Orbiter / Master Bedroom), type 1 id 26 Command:Set Bound Icon, retry none, parameters: <0xa52bcb70>
08   01/27/13 18:29:42.561        Parameter 5(Value To Assign): 0 <0xa52bcb70>
08   01/27/13 18:29:42.561        Parameter 9(Text):  <0xa52bcb70>
08   01/27/13 18:29:42.561        Parameter 14(Type): follow_telecom <0xa52bcb70>
08   01/27/13 18:29:42.565      Received Message from 9 (Orbiter Plug-in / Computer Closet) to 271 (Master Bedroom Android Orbiter / Master Bedroom), type 1 id 741 Command:Goto Screen, retry none, parameters: <0xa52bcb70>
08   01/27/13 18:29:42.565        Parameter 159(PK_Screen): 204 <0xa52bcb70>
08   01/27/13 18:29:42.565        Parameter 251(Interruption): 0 <0xa52bcb70>
08   01/27/13 18:29:42.565        Parameter 252(Turn On): 0 <0xa52bcb70>
08   01/27/13 18:29:42.565        Parameter 253(Queue): 0 <0xa52bcb70>
08   01/27/13 18:29:42.560      Received Message from 11 (Telecom Plug-in / Computer Closet) to 271 (Master Bedroom Android Orbiter / Master Bedroom), type 1 id 26 Command:Set Bound Icon, retry none, parameters: <0x9f2b0b70>
08   01/27/13 18:29:42.570        Parameter 5(Value To Assign): 1 <0x9f2b0b70>
08   01/27/13 18:29:42.570        Parameter 9(Text):  <0x9f2b0b70>
08   01/27/13 18:29:42.570        Parameter 14(Type): user1 <0x9f2b0b70>
08   01/27/13 18:29:42.570      Received Message from 11 (Telecom Plug-in / Computer Closet) to 271 (Master Bedroom Android Orbiter / Master Bedroom), type 1 id 26 Command:Set Bound Icon, retry none, parameters: <0x9f2b0b70>
08   01/27/13 18:29:42.570        Parameter 5(Value To Assign): 0 <0x9f2b0b70>
08   01/27/13 18:29:42.570        Parameter 9(Text): 0 <0x9f2b0b70>
08   01/27/13 18:29:42.570        Parameter 14(Type): vm1 <0x9f2b0b70>
08   01/27/13 18:29:42.570      Received Message from 11 (Telecom Plug-in / Computer Closet) to 271 (Master Bedroom Android Orbiter / Master Bedroom), type 1 id 26 Command:Set Bound Icon, retry none, parameters: <0x9f2b0b70>
08   01/27/13 18:29:42.570        Parameter 5(Value To Assign): 1 <0x9f2b0b70>
08   01/27/13 18:29:42.570        Parameter 9(Text):  <0x9f2b0b70>
08   01/27/13 18:29:42.570        Parameter 14(Type): user2 <0x9f2b0b70>
08   01/27/13 18:29:42.570      Received Message from 11 (Telecom Plug-in / Computer Closet) to 271 (Master Bedroom Android Orbiter / Master Bedroom), type 1 id 26 Command:Set Bound Icon, retry none, parameters: <0x9f2b0b70>
08   01/27/13 18:29:42.570        Parameter 5(Value To Assign): 2 <0x9f2b0b70>
08   01/27/13 18:29:42.570        Parameter 9(Text): 12 <0x9f2b0b70>
08   01/27/13 18:29:42.570        Parameter 14(Type): vm2 <0x9f2b0b70>
05   01/27/13 18:29:42.585      Socket::ReceiveData 0x441763a0 failed, bytes left 0 start: -2057207296 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 201 Incoming_Conn Socket 201 192.168.78.251 <0x67cdbb70>
05   01/27/13 18:29:42.585      Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 201 192.168.78.251 <0x67cdbb70>
05   01/27/13 18:29:42.585      TCPIP: Closing connection to -1003 (Router Dev #0) 0x441763a0 m_Socket: -1 <0x67cdbb70>
05   01/27/13 18:29:42.585      Router::RemoveAndDeleteSocket 0x441763a0 -1003 <0x67cdbb70>
08   01/27/13 18:29:42.588      Received Message from 271 (Master Bedroom Android Orbiter / Master Bedroom) to 9 (Orbiter Plug-in / Computer Closet), type 1 id 818 Command:Get Screen Saver Files, retry none, parameters: <0x96efdb70>
08   01/27/13 18:29:42.588        Parameter 2(PK_Device): 271 <0x96efdb70>
08   01/27/13 18:29:42.588        Parameter 13(Filename):  <0x96efdb70>
08   01/27/13 18:29:42.747      Received Message from 271 (Master Bedroom Android Orbiter / Master Bedroom) to 10 (Media Plug-in / Computer Closet), type 1 id 68 Command:Get Device Data, retry none, parameters: <0x96efdb70>
08   01/27/13 18:29:42.747        Parameter 2(PK_Device): 0 <0x96efdb70>
08   01/27/13 18:29:42.748        Parameter 5(Value To Assign):  <0x96efdb70>
08   01/27/13 18:29:42.748        Parameter 52(PK_DeviceData): 158 <0x96efdb70>
08   01/27/13 18:29:42.748        Parameter 53(UseDefault): 1 <0x96efdb70>
05   01/27/13 18:29:42.748      An orbiter sent the media handler message type: 1 id: 68, but there's no stream in ea 2 <0x836d6b70>
08   01/27/13 18:29:42.750      Received Message from 271 (Master Bedroom Android Orbiter / Master Bedroom) to 10 (Media Plug-in / Computer Closet), type 1 id 807 Command:Get Attributes For Media, retry none, parameters: <0x96efdb70>
08   01/27/13 18:29:42.750        Parameter 5(Value To Assign):  <0x96efdb70>
08   01/27/13 18:29:42.750        Parameter 13(Filename):  <0x96efdb70>
08   01/27/13 18:29:42.750        Parameter 45(PK_EntertainArea): 2 <0x96efdb70>
01   01/27/13 18:29:42.750      Media_Plugin::CMD_Get_Attributes_For_Media no filename nor valid EA w/ stream 2 (0xb633b898) specified <0x836d6b70>
08   01/27/13 18:29:42.753      Received Message from 271 (Master Bedroom Android Orbiter / Master Bedroom) to 6 (Datagrid Plug-in / Computer Closet), type 1 id 35 Command:Populate Datagrid, retry none, parameters: <0x96efdb70>
08   01/27/13 18:29:42.753        Parameter 4(PK_Variable): 0 <0x96efdb70>
08   01/27/13 18:29:42.753        Parameter 5(Value To Assign):  <0x96efdb70>
08   01/27/13 18:29:42.753        Parameter 10(ID): 1 <0x96efdb70>
08   01/27/13 18:29:42.753        Parameter 15(DataGrid ID): mac_271 <0x96efdb70>
08   01/27/13 18:29:42.753        Parameter 38(PK_DataGrid): 31 <0x96efdb70>
08   01/27/13 18:29:42.753        Parameter 39(Options): 2 <0x96efdb70>
08   01/27/13 18:29:42.753        Parameter 40(IsSuccessful): 0 <0x96efdb70>
08   01/27/13 18:29:42.753        Parameter 44(PK_DeviceTemplate): 0 <0x96efdb70>
08   01/27/13 18:29:42.753        Parameter 60(Width): 0 <0x96efdb70>
08   01/27/13 18:29:42.753        Parameter 61(Height): 0 <0x96efdb70>
08   01/27/13 18:29:42.755      Received Message from 271 (Master Bedroom Android Orbiter / Master Bedroom) to 6 (Datagrid Plug-in / Computer Closet), type 1 id 34 Command:Request Datagrid Contents, retry none, parameters: <0x96efdb70>
08   01/27/13 18:29:42.755        Parameter 10(ID): 1 <0x96efdb70>
08   01/27/13 18:29:42.755        Parameter 15(DataGrid ID): mac_271 <0x96efdb70>
08   01/27/13 18:29:42.755        Parameter 32(Row): 0 <0x96efdb70>
08   01/27/13 18:29:42.755        Parameter 33(Column): 0 <0x96efdb70>
08   01/27/13 18:29:42.755        Parameter 34(Row count): 0 <0x96efdb70>
08   01/27/13 18:29:42.755        Parameter 35(Column count): 0 <0x96efdb70>
08   01/27/13 18:29:42.755        Parameter 36(Keep Row Header): 0 <0x96efdb70>
08   01/27/13 18:29:42.755        Parameter 37(Keep Column Header): 0 <0x96efdb70>
08   01/27/13 18:29:42.755        Parameter 49(Add Up-Down Arrows): 1 <0x96efdb70>
08   01/27/13 18:29:42.755        Parameter 73(Seek):  <0x96efdb70>
08   01/27/13 18:29:42.755        Parameter 74(Offset): 0 <0x96efdb70>
08   01/27/13 18:29:43.203      Received Message from 271 (Master Bedroom Android Orbiter / Master Bedroom) to 4 (General Info Plug-in / Computer Closet), type 1 id 71 Command:Request File, retry none, parameters: <0x96efdb70>
08   01/27/13 18:29:43.203        Parameter 13(Filename): /home/public/data/pictures/2008-08 Lake Powell Houseboat/P1040501.JPG <0x96efdb70>
08   01/27/13 18:29:44.463      Received Message from 271 (Master Bedroom Android Orbiter / Master Bedroom) to 6 (Datagrid Plug-in / Computer Closet), type 1 id 35 Command:Populate Datagrid, retry none, parameters: <0x96efdb70>
08   01/27/13 18:29:44.463        Parameter 4(PK_Variable): 0 <0x96efdb70>
08   01/27/13 18:29:44.463        Parameter 5(Value To Assign):  <0x96efdb70>
08   01/27/13 18:29:44.463        Parameter 10(ID): 2 <0x96efdb70>
08   01/27/13 18:29:44.463        Parameter 15(DataGrid ID): plist_271 <0x96efdb70>
08   01/27/13 18:29:44.463        Parameter 38(PK_DataGrid): 18 <0x96efdb70>
08   01/27/13 18:29:44.463        Parameter 39(Options): 38 <0x96efdb70>
08   01/27/13 18:29:44.463        Parameter 40(IsSuccessful): 0 <0x96efdb70>
08   01/27/13 18:29:44.463        Parameter 44(PK_DeviceTemplate): 9 <0x96efdb70>
08   01/27/13 18:29:44.463        Parameter 60(Width): 0 <0x96efdb70>
08   01/27/13 18:29:44.463        Parameter 61(Height): 1 <0x96efdb70>
05   01/27/13 18:29:44.463      No stream on orbiter: 271 <0x896e2b70>
05   01/27/13 18:29:44.463      The message was not from an orbiter or it doesn't have a media stream on it! <0x896e2b70>
08   01/27/13 18:29:44.466      Received Message from 271 (Master Bedroom Android Orbiter / Master Bedroom) to 6 (Datagrid Plug-in / Computer Closet), type 1 id 34 Command:Request Datagrid Contents, retry none, parameters: <0x96efdb70>
08   01/27/13 18:29:44.466        Parameter 10(ID): 2 <0x96efdb70>
08   01/27/13 18:29:44.466        Parameter 15(DataGrid ID): plist_271 <0x96efdb70>
08   01/27/13 18:29:44.466        Parameter 32(Row): 0 <0x96efdb70>
08   01/27/13 18:29:44.466        Parameter 33(Column): 0 <0x96efdb70>
08   01/27/13 18:29:44.466        Parameter 34(Row count): 0 <0x96efdb70>
08   01/27/13 18:29:44.466        Parameter 35(Column count): 0 <0x96efdb70>
08   01/27/13 18:29:44.466        Parameter 36(Keep Row Header): 0 <0x96efdb70>
08   01/27/13 18:29:44.466        Parameter 37(Keep Column Header): 0 <0x96efdb70>
08   01/27/13 18:29:44.466        Parameter 49(Add Up-Down Arrows): 0 <0x96efdb70>
08   01/27/13 18:29:44.466        Parameter 73(Seek):  <0x96efdb70>
08   01/27/13 18:29:44.466        Parameter 74(Offset): 0 <0x96efdb70>
08   01/27/13 18:29:44.469      Received Message from 271 (Master Bedroom Android Orbiter / Master Bedroom) to 6 (Datagrid Plug-in / Computer Closet), type 1 id 35 Command:Populate Datagrid, retry none, parameters: <0x96efdb70>
08   01/27/13 18:29:44.469        Parameter 4(PK_Variable): 0 <0x96efdb70>
08   01/27/13 18:29:44.469        Parameter 5(Value To Assign):  <0x96efdb70>
08   01/27/13 18:29:44.469        Parameter 10(ID): 3 <0x96efdb70>
08   01/27/13 18:29:44.469        Parameter 15(DataGrid ID): plist_271 <0x96efdb70>
08   01/27/13 18:29:44.469        Parameter 38(PK_DataGrid): 18 <0x96efdb70>
08   01/27/13 18:29:44.469        Parameter 39(Options): 38 <0x96efdb70>
08   01/27/13 18:29:44.469        Parameter 40(IsSuccessful): 1 <0x96efdb70>
08   01/27/13 18:29:44.469        Parameter 44(PK_DeviceTemplate): 9 <0x96efdb70>
08   01/27/13 18:29:44.469        Parameter 60(Width): 0 <0x96efdb70>
08   01/27/13 18:29:44.469        Parameter 61(Height): 1 <0x96efdb70>
05   01/27/13 18:29:44.470      No stream on orbiter: 271 <0x896e2b70>
05   01/27/13 18:29:44.470      The message was not from an orbiter or it doesn't have a media stream on it! <0x896e2b70>
08   01/27/13 18:29:44.477      Received Message from 271 (Master Bedroom Android Orbiter / Master Bedroom) to 6 (Datagrid Plug-in / Computer Closet), type 1 id 34 Command:Request Datagrid Contents, retry none, parameters: <0x96efdb70>
08   01/27/13 18:29:44.477        Parameter 10(ID): 3 <0x96efdb70>
08   01/27/13 18:29:44.477        Parameter 15(DataGrid ID): plist_271 <0x96efdb70>
08   01/27/13 18:29:44.477        Parameter 32(Row): 0 <0x96efdb70>
08   01/27/13 18:29:44.477        Parameter 33(Column): 0 <0x96efdb70>
08   01/27/13 18:29:44.477        Parameter 34(Row count): 0 <0x96efdb70>
08   01/27/13 18:29:44.477        Parameter 35(Column count): 0 <0x96efdb70>
08   01/27/13 18:29:44.477        Parameter 36(Keep Row Header): 0 <0x96efdb70>
08   01/27/13 18:29:44.477        Parameter 37(Keep Column Header): 0 <0x96efdb70>
08   01/27/13 18:29:44.477        Parameter 49(Add Up-Down Arrows): 0 <0x96efdb70>
08   01/27/13 18:29:44.477        Parameter 73(Seek):  <0x96efdb70>
08   01/27/13 18:29:44.477        Parameter 74(Offset): 0 <0x96efdb70>
05   01/27/13 18:29:46.573      Socket::ReceiveData 0x44175ff8 failed, bytes left 0 start: -2057217296 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 197 Incoming_Conn Socket 197 192.168.78.251EVENT 271 T=2186 Event #271 <0x4ead9b70>
05   01/27/13 18:29:46.573      Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 197 192.168.78.251EVENT 271 T=2186 Event #271 <0x4ead9b70>
05   01/27/13 18:29:46.573      TCPIP: Closing connection to 271 (Router Dev #0) 0x44175ff8 m_Socket: -1 <0x4ead9b70>
05   01/27/13 18:29:46.573      Router::RemoveAndDeleteSocket 0x44175ff8 271 <0x4ead9b70>
05   01/27/13 18:29:46.574      Socket::ReceiveData 0x44176130 failed, bytes left 0 start: -2057157296 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 198 Incoming_Conn Socket 198 192.168.78.251EVENT 271 T=2186 Event #271 <0x96efdb70>
05   01/27/13 18:29:46.574      Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Incoming_Conn Socket 198 192.168.78.251EVENT 271 T=2186 Event #271 <0x96efdb70>
05   01/27/13 18:29:46.574      TCPIP: Closing connection to 271 (Router Dev #0) 0x44176130 m_Socket: -1 <0x96efdb70>
05   01/27/13 18:29:46.574      Router::RemoveAndDeleteSocket 0x44176130 271 <0x96efdb70>
Title: Re: Android QOrbiter
Post by: purps on January 29, 2013, 11:45:38 pm
Hi Langston, I finally tried your beta QOrbiter... and it's very exciting!! Thank you.

Cheers,
Matt.
Title: Re: Android QOrbiter
Post by: Esperanto on January 30, 2013, 07:43:24 pm
the latest link had a typo:

http://deb.linuxmce.org/QOrbiter-release.apk
Title: Re: Android QOrbiter
Post by: golgoj4 on February 01, 2013, 08:51:59 am
the latest link had a typo:

http://deb.linuxmce.org/QOrbiter-release.apk

Very odd. Is there a time you might be available for some live debugging?

-langstonius