I got javamo to install on my phone. I am getting can't access JSR082. Where would I look to troubleshoot. If you need more info let me know.

Which phone are you using? If you check the wiki there is a link to a list of phones that support JSR-082. My current mobile is a Samsung SGH-U900 SOUL that advertises that it support Bluetooth and Java, yet you can't install 3rd party apps and it doesn't have JSR-082. I'll never buy Samsung again.

I've obtained a free SIM from one of the networks here in the UK and I'm using my old SE-K750i as my MO - it works a treat!

I am using the LG Rumor. It rus java so I said what the hell i'll give it a shot. I figured it would may run it even though it was not in the list. I was thinking maybe I misread something in the wiki or forgot to install something extra that maybe is not included in the wiki. Thats ok i'll just scrap that idea and wait till my contract with my service runs out and get one that is known to work. but at the price they are now, i just cant budget for one of them now. Thanx for the feedback.

It is a phone which is to be an IPhone killer.Since the IPhone won't allow for 3rd party apps to be installed easily...why not focus on the Omnia and get it as not only an orbiter... but also the best way to control linux MCE

Since the FIIRE cheif is no longer available, I have been looking for a way to get a bluetooth gyration remotefor linux and the Omnia seems to have everything required to replace the Cheif with the follow ME option.

The omnia has all of the following built in... Accelerometer, Bluetooth, Touchscreen,JAVA + FLASH CAPABLE, does it need more to control linux MCE as well as the cheif?

As you may know LinuxMCE supports smartphones under Symbian OS 1st edition, Windows Mobile 2003 and Treo as mobile Orbiters to control your home. It uses Bluetooth to communicate with smarthome system. So, it’s too difficult port every time the code to the new version of mobile OS.

The Mobile orbiter itself, is a very simple program that grabs images from the server, and transmits a simple packet format representing button presses and touch coordinates. The packet format is called BD, and is transmitted over an RFCOMM channel (up until the JavaMO, this was a hard-coded channel # 9, with the JavaMO, Hari patched the BD comms library to do SDP lookups to ask the phone for a free channel and negotiate this on a per-phone basis.), as such the client itself is very simple, and all of the processing is done by the DCE device Bluetooth_Dongle, which is in itself a subclass of Orbiter.)

For Symbian and Windows Smartphone, the code is built as an amalgam of code in src/PlutoMO, and src/VIPShared. src/PlutoMO provides the basic mobile orbiter shell, while VIPShared provides BDcommon and the VMC (VIP Menu Container) decoding which allows the phone to be used in offline mode.

The Windows Smartphone versions run atop the SMARTPHONE_2003 and SMARTPHONE_2005 variants, which are the only two SDKs of this type that microsoft has released. Porting this to new versions of Windows Mobile basically would entail #ifdefs to most commonly work around differences in core API (as the Windows CE core in these systems change like crazy from release to release), while it's not dead easy, it's not difficult, either. I am working on a port to WM5 and WM6 for the standard Orbiter. But I need hardware to test the results of the code.

Your comments about the Symbian variant were also incorrect, in that Hari has revamped the code to work on Symbian v2 (sis) and Symbian v3 (sisx). It took Hari roughly a weekend to do this, which makes me more mad that someone else didn't step up and do this sooner. Given the utter simplicity of the code, and the fact that Symbian's SDK is pretty consistent below, other ports to UIQ and other variants of Symbian are very possible. People, step up and do it!