we are waiting for the Thom tips and tricks to improve the skin =)

I post here some problems,

1) I followed 1:1 (as Hari said) the wiki instruction to build the dev envinroinment (http://wiki.linuxmce.org/index.php/JavaMO) but when i make, it return ERROR:Cannot find java.lang
 Anyway i create a Nokia6233.java class inside "com/linuxmce/javamo/devices" with some Keytranslation and i need a working env to test it.

  This "road" is ok? and which other file we need to change to add the nokia6233 class?  Maybe in the phone detenction in JavaMO.java?

Code:

    private PhoneDevice detectPhone() {
83                 String platform = System.getProperty("microedition.platform");
84                 MOLogger.log(5, "Device:" + platform);
85                 if (platform != null) {
86                         if (platform.toUpperCase().indexOf("NOKIA") >= 0) {
87                                 MOLogger.log(5, "Detected as Nokia");
88                                 return new NokiaPhone();
89                         } else if (platform.toUpperCase().indexOf("SONYERICSSON") >= 0) {
90                                 MOLogger.log(5, "Detected as SonyEricsson");
91                                 return new SEPhone();
92                         }
93
94                 }
95                 return new NokiaPhone();
96         }

2) With KeyCodes.jar (as u see in the previous post in the previous page) i have too few button to control the orbiter. I need at least, in addiction to the numeric pad and the directional pad, a OK button and a BACK button. But i have only one (the green Take Call Button).  We should implement the square button in the center of the additional pad but i don't even know where to start to do this.

3) We need a custom skin variation i guess, the MO is all inside the folder "Mobile Orbiter" inside the skins/basic folder?

TNX for helping,
Martino.

I think so  , maybe i can do it.

Here the keymap of my Nokia6233

Guy's let's get started porting only the Orbiter, then we could work on MediaDirector.

We can create a template for Eutelia  - Italian Provider.

If you thing it could be valueable please let me know what should I do so it fits LinuxMCE. It's my first open source active participation so please excuse any "faux pas"

You can start pointing us to the code to see how you implemented this, so we compare your EIB-java with the existing EIB-eibd  interface (written in c++) and reach the best result.

Best Regard, and thank for your helping.

Massabuntu.

Glad to hear we have another EIB/KNX user! See u in the other post.

To program the phys addr of  an interface u need another interface.

Well done for the implementation, tomorrow i'll update it on my core and i'll test some others telegram type.

yeah, so let me understand, now we are ok with dimming and temp?

Later we have to discuss about the much higher number of KNX Object and the few who are handled by LinuxMCE.

Massabuntu.

Look at http://svn.linuxmce.org/trac.cgi/attachment/ticket/278/Telegram.cpp

It's difficult to explain it in english but i try.
Look at

Code:

220 void Telegram::generate_head()
221 {
222         _data[2] = _data[0];
223         _data[0]=(_type>>8) & 0x3;
224
225         if(_type==EIBWRITE && _length==0)
226         {
227                 _data[1]=(_type & 0xff) | (_shortdata & 0x3f);
228         }else{
229                 _data[1]=_type & 0xff;
230         }
231 }

I added the row 222, because the 1 byte value was stored in data[0] and   after

Code:

_data[0]=(_type>>8) & 0x3

;  we lost this value because data[0] become "0x00"

In  1 bit telegram (<6bit), our _length is 0,so we go on the if block, and data[1] become "0x80" in off case and "0x81" in the on case and the telegram total lengh is 9 byte (XX XX XX XX XX XX XX XX VV) VV could be 0x80 or 0x81.

In 1 byte telegram , we go on the else, our _data[1] become "0x80" but we need another byte to complete the Telegram ( That in >6 bit case is almost 1 byte longer than the <6 bit one)

So at the and we have a Telegram like:
XX XX XX XX XX XX XX XX 80 VV ( where VV is _data[2])

Sorry fer the raw explanation.

PS:Now the challenge is for the other DTP.

*hmm* no.

This is just the Orbiter.

It's intended to run on lightweight touch screen based devices to provide an orbiter panel. If you know what you're doing, you can extend it to be a full media director, but that's not what I intended.

-Thom

This is what i meant,
1) Port "only" the Obriter on ARM devices with x11
2) Port "ony" the  Orbiter on ARM devices on FB
3) Port a complete Media Director an a ARM Cortex v8 with OpenGLES and DSP like the BeagleBoard (this is gonna take muuuuccchhh time i think, and a lot of skill) maybe a device with PoE.... just dreaming.

Anyway, let get it started, where i found the code to begin cross-compiling?

 

Thom, let me understand.

You made the port on FB, but the os running under should be a media director or could be a simple linux?

Because i could, on a fisrt step install the X11 anyway on the BeagleBoard, and when this works, move everything on FB.

If i get it, you have cut off all the dependencies in addiction to port it on the framebuffer. So i could run it on every distro =) Hope i get it well

I have a BeagleBoard to test iT!

YES! I saw  the problem and i found a way to fix it.

It's a little bit dirt beacuse it could don't work with other data type but now we know where we had the problem.