Messages

1

Installation issues / Re: MySQL failure. Any advice?

« on: November 01, 2011, 02:43:01 am »

Thanks for the suggestions guys. Thought I would come back with an update....

fsck - was clean
posde - your suggestions rely on mysqld running which it isn't - but I may need those as the next step anyway.

The failure seems to be on applying the binlog when attempting to recover from a crash. The system was obviously left in this state from the power failing. It seemed to be stuck trying to apply the logs. Tried lots of different command line options to mysqld and running through debugger etc but nothing really worked.

At the last minute last night I thought I might just remove the binlog files so that it can't  apply them. This worked to an extent - in that it now allows mysqld to start. It has quite a lot of DB errors now with things being out of sync and missing which I figure is a side effect of removing the files. Went to bed after that as I couldn't keep my eyes open.

Will now try putting the binlog files back to see what happens. If it is still not happy then will follow posde suggestion and re-install the DB's.

Regards
Darren

2

Installation issues / MySQL failure. Any advice?

« on: October 27, 2011, 01:10:11 am »

Hi all,

My core power supply was having problems last night which meant that the core was instantly losing power and would need to be manually restarted. This happened a few times before I realised what was happening. I have now replaced the power supply and seems to be stable from that perspective - but it looks to have corrupted the databases.

mysqld will not start and when attempts are made to start it manually it fails after attempting to recover, blurts out a stack trace and advises to look at a couple of websites for more info. The websites just take me through attaching symbols to the stack trace etc which don't really help me at the moment.

Question is; can I somehow reinstall mysql without upsetting the rest of the system and having to do a reinstall? Anyone done anything like this?

regards
Darren

3

Users / Re: Customize /etc/asound.conf

« on: October 25, 2011, 07:06:52 am »

There is a template file that is used to generate it. If you change the template (it is only for that MD) then it will generate the working one each time.

Can't remember filenames and locations and I am at work at the moment so I can't check. But if you have trouble finding it let me know and I will look up on the MD that I changed at home.

Looks like a similar change to what I had to do. What sort of machine?

4

Installation issues / Re: [Solved] Generic Proxy Orbiter

« on: August 31, 2011, 06:51:57 am »

Screen resolutions won't change too much visually as the Android touch orbiter scales the image received to your device resolution (This happens in both orientations, hence the squashed effect when orientated vertically).

My suggestion would be to have a resolution which is relative to your actual  device (eg: 1/4 of each dimension). You will get some graining depending upon how low you go but you will also get benefit from less data transfer.

Skins are best left at the ones based on the basic UI1 skin for touch devices...

5

Installation issues / Re: [Solved] Generic Proxy Orbiter

« on: August 30, 2011, 07:09:57 am »

With the web orbiter now working you should also be able to use the Android native app as well. Search for the Android Touch Orbiter thread for details .....

6

Installation issues / Re: Orbitor screen resolutuion on Flytouch 2

« on: August 22, 2011, 02:49:18 am »

Hi Marper,

I am guessing then that it is an issue with Honeycomb tablets - and from the looks of it you are the only one with one.

I had a quick go at running on 3.1 Emulator the other day - it didn't run at all when I tried and I didn't have time to investigate. Will try and find some time this week to look into it further (and hopefully release a new version as well). If you want to upload your logcat somewhere and post the link that might be useful as well.

regards
Darren

7

Users / Re: Android Touch Orbiter

« on: August 19, 2011, 02:30:17 am »

I take it you are changing the "LMCE Server" setting to something clever in order to achieve this? Is that all you have to do for this approach to work, or do you have to SSH into the core separately from a terminal or something before you fire up the touch orbiter?

Cheers,
Matt.

Yes, need to connect and authorise to core via SSH first - via terminal or something. Add a tunnel to a local port and then change the settings in the touch orbiter to your local IP address and whatever port you have setup. I think I used connectbot when I did the test but I believe there is dedicated SSH tunning apps that might simplify the process if you were doing it often - and I think they can run by default as a proxy if you have a rooted device.

I was using the same technique to access lmce admin  and mythweb from my phone or laptop on the bus on the way home.

8

Users / Re: Android Touch Orbiter

« on: August 18, 2011, 03:02:51 am »

I'm experiencing firewall issues. your orbiter works only when I disable the fire wall on the core. the web orbiter works just fine with out any firewall changes. Am i missing something?
I added an exception for the correct port on the firewall config tab. Shouldn't this port be open by default?

I can only assume that you are either trying to access the orbiter from an external network, either 3G or Wi-Fi somewhere other than your home.

If that is the case then it is behaving as expected. It is built to establish a socket based connection to the server. If you want an external network to access this server then you will need a path through your firewall. If this is what you are trying to do then I have tested it by tunnelling it over an SSH connection which I would recommend  rather than just exposing or port forwarding the proxy orbiter port.

If you are not accessing from external network then as some others have suggested you have a setup issue. Check what IP address your device has received via DHCP should be 192.168.80.X address is everything setup as default. If it is then connection should have no problem to core running on 192.168.80.1 and whatever port is used.

9

Installation issues / Re: Orbitor screen resolutuion on Flytouch 2

« on: August 15, 2011, 12:38:06 pm »

The flytouch2 is working now isn't it - I thought the only problem was now with the screenshot that Marper posted?

10

Developers / Re: 2nd display as Touchscreen

« on: August 15, 2011, 06:10:51 am »

If you already have the touchscreen and just want to use it as an orbiter you could attach a small machine to it and just run orbiter on it.

Depending upon how adventurous you are might guide your options. There are certainly sub $100 Android STB type devices available that you could mount to the back of the touchscreen.
There are other SoC type options that you can buy/build that can run small linux distros and then you could compile orbiter for it.
 
You could get an older Atom based box second hand and install it as an MD with onscreen orbiter running Orbiter v1 on it.

All these options might involve a bit of messing around to get the touchscreen drivers etc working but I think they would all be doable.

Anyway - just some suggestions

Darren

11

Installation issues / Re: Orbitor screen resolutuion on Flytouch 2

« on: August 15, 2011, 05:57:26 am »

Marper,

Your tablet (A500) is running Honeycomb (Android 3.0) right?

Has anyone else run the app on 3.0 (or above) and can verify if it is the same behaviour?

I know honeycomb has changes to to cater for tablets running multiple apps on the same screen and part of that change might mean that the scaling no longer functions as prior.

I will try it on a simulator and see what behaviour I get - if it is the same then I will find a fix for you and get a release out. I have been trying to release a new version for a while with the enhanced UI scrollable lists but a couple of bugs and a weeks holiday have delayed this - but should be close.

Regards
Darren

12

Developers / Re: LinuxMCE wants you - to help with the new Orbiter!

« on: August 04, 2011, 03:52:31 am »

I would love to be involved.

I am currently trying to get rid of some bugs in the updated Android Touch orbiter (with dynamic grids) but would love to see this working as well.

I will setup necessitas and get the dev environment going and then get back to you.

My ability to commit time is quite sporadic but will do what I can.

regards
Darren

13

Installation issues / Re: Orbitor screen resolutuion on Flytouch 2

« on: July 18, 2011, 06:36:34 am »

Are you using the web orbiter or the android touch orbiter?

The android touch orbiter will scale whatever image it gets to the resolution of the device ( in its current orientation)

14

Developers / Re: 2nd display as Touchscreen

« on: July 13, 2011, 08:24:51 am »

If you were doing display mirroring then I think that this should work, however I don't think you will get a desirable result.

UI2 basically came about due to UI1 not being desirable for the onscreen orbiter (ie: on your TV/projector etc) and to allow control with pointing devices or remote controls.

UI1 is still the best UI suited to touch screen type interfacing.

So basically you would need to run UI1 on your Media Director and that would get displayed (mirrored) on both displays which I think you will find is not desirable.

A cheap tablet or mobile phone is much better as you get a separate orbiter instance from your on-screen orbiter (which can be set to UI2)
If your budget doesn't extend to a separate touch device then I believe that a remote control or wireless mouse etc are your next best options and indeed the beauty of the system is that they can be used in combination (ie: Whilst the wife is trying to select some crappy video/audio/TV with the remote - use your phone to put what you want on....)

Hope that make sense

Darren

15

Users / Re: Preview of new Touch Orbiter UI Capabilities (video demo)

« on: July 05, 2011, 01:05:44 am »

Andrew,

Does that mean the code is ready and available?

Regards
Darren