Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - sambuca

Pages: 1 ... 26 27 [28] 29 30 31
Developers / Re: Java/ J2ME mobile orbiter
« on: November 29, 2008, 06:27:53 pm »

I did a few changes to some of the gui classes also. Also I added a common logging method, which could be extended more. I guess some static logger class might be the way to go. (I use this concept in J2EE). This would allow us to set it up to log to screen, file, another bluetooth connection, or whatever.

Btw, have you checked if there exists some kind of logging support already in J2ME?

Sorry if I am holding you up, I'll see if I can make a patch tomorrow.


Developers / Re: Java/ J2ME mobile orbiter
« on: November 29, 2008, 12:35:37 am »

I've made some progress. I've implemented handling of repeated key presses. I uploaded the files to the same location as previously.
(Also added preliminary handling of the left soft key of my SE phone)

crudpuppy: I plan on making a patch for the current SVN as soon as I get the time.

My next task after that will be adding a working key mapping for my SE W580 phone (and K800i). I also have some problems with the orbiter disconnecting (both at the phone/server side and at the MD/client side), which I haven't solved yet.

Regarding jsr075:
If I understand correctly, won't the VMC need to store files on the phone also? (Maybe that's what you were referring to in your last post, hari.) Haven't really looked into what VMC is, but my understanding is that it uses WAP for communications and displays pictures stored at the phone. Am I imagining things, or am I on to something  ;)


Developers / Re: Java/ J2ME mobile orbiter
« on: November 28, 2008, 11:02:12 am »

I guess the phone you are using (SE P1?) has a touch screen, since your log reports mouse events. I haven't looked at the bluetooth dongle side of things (yet), so I can't really say why it only works sometimes. Maybe someone with more knowledge of the BD can comment? Or maybe anyone that uses another touch screen phone can try it out too?

Haven't had as much time to work on this as I would have liked, but I have looked into optimizing the performance more. Anyone who has done similar knows it can be a pain. Which is how it is now. There are some buffer copies in the code that I am trying to take out, but I must have messed up cause now it wont display anything any more. I'll keep looking. I hope to have it sorted out and cleaned up enough to make a patch for hari maybe next week.

hari, when you say that repeated keypresses are not implemented, is that in the JavaMO, or in the BD library?


Developers / Re: Java/ J2ME mobile orbiter
« on: November 26, 2008, 10:17:36 pm »
I had to edit CLDC-1  to read CLDC-1.1
Otherwise my P1i complained (inompatible application).

Oops, I probably mis-edited the jad file.

There are still problems with connecting to lmce from the phone.
Sometimes it just not work (Waiting for connection).
This problem have nothing to do with libBDCommon, patched or not.
Have tried this before so. It is something else.
Maybe the bluetooth_dongle log file can shed some light on this? As the JavaMO is just listening for incoming connections, I am not sure we can do anything to help the situation from this side.

Things that do not work:
* Media list only show text. Which is not to bad. Maybe that is the way forward and just add some graphics around it so it look nicer. Instead of shuffling images between phone and core.
The media list uses the phones default list implementation, so there is limited possibilities to change it. This, I guess, is to save data transfer. But it is possible to use an image for each item in the list (a small image on the left of the text I think). This might require some changes to the bluetooth_dongle to send the images, and of course would require much more data transferred. Our best chance would be to first display the list, and them add images to the list as they are transferred. I fear this is too much work to implement and would be dead slow (my 600+ list of artists already takes 5 seconds + to display).

*Pause/Play button do not work when playing video. (have not tested audio yet).
Can you check the bluetooth_dongle log file, and see if the button press is received from the phone?

*Do not seem to reconnect to core if router is reloaded. However there is debug output when it happen (disconnect is shown on screen with some more text). This probably mean that javamo detect when it is offline so if we handle that...
Don't know if the JavaMO receives any notification about router reload. But anyway, I am trying to make it survive bluetooth reconnects, so this would probably help.

Another thing I remember that I changed in this version; Because the image transfer took so long, the screen saver kicks in, thus I wont see when the image was finally loaded. I added some code to flash the display to hopefully turn it on again. Let me know if it is for the better or worse.

Developers / Re: Java/ J2ME mobile orbiter
« on: November 26, 2008, 04:26:50 pm »
I should really thank you all for this great system.

That said, I hope I am able to contribute more in the future. Just figured this was a good starting point.


Developers / Re: Java/ J2ME mobile orbiter
« on: November 26, 2008, 03:43:41 pm »
You can download my modified version from Just point your mobile browser to the JavaMO.jad file and it should download and install. Depending on your phone you will have to confirm the installation.

niz32, do you think the P1 is faster Java-wise than other phones? I think the Java speed might be a factor in the random crashes, since did not crash as much when it worked much better when I reduced image quality.

On a general note: This version does display more logging messages to start-up screen. While I probably will look into debugging my Sony Ericsson phone using a method similar to what hari described on the wiki, I think it might be useful to get some feedback from other phones without the users needing to set up any debugging.

Developers / Re: Java/ J2ME mobile orbiter
« on: November 26, 2008, 01:53:58 pm »
I did some tweaks to the JavaMO code a few days ago.
* Changed image quality
 It seems that transferring a 100k + image over bluetooth takes too much time. Changing the image quality setting from 100 (png) to 30 radically improved responsiveness. Image size is now below 10k, and usually around 6k.
* Added quite a bit of logging
 Trying to work out the mysterious crashes and malfunctions of the JavaMO on my phone, I added more logging to find out where the problem is.
* Some more exception handling.
 Sometimes the JavaMO just quits on my phone. I suspect that some major unhandled exception causes this. I am trying to add handling and logging to work out this problem.
* Added a explicit exit button to the media list, as my phone had no way of returning from the media list.

Still to do (from a stability perspective):
* Debug the media list
  My phone shows no text for the audio list entries (the last entry has text), while other lists (pictures for instance) shows the texts correctly.
* Debug the connection stuff, to find out what makes the MO crash and/or drop the connection.

I don't feel that I am finished by any means, but if someone is interested in testing this version of the JavaMO, I can put it up for download.
Not sure if it will work on more phones, but the improvement in responsiveness might help a bit, and the extended logging might give us a better idea of what the problem might be.

I can also make a patch for the current SVN tree. Hari, can you comment on how (and when) you would like a patch?

I will continue working on the stability of the mo, and maybe some of the other issues mentioned here if I get the time. The repeated key presses might be the next thing on my list, but my primary goal is making it usable first. (What are the repeated key presses for anyway?)



To the best of my knowledge, that is what I did. I checked out the 710 branch (on a 710 hybrid) and compiled using instructions scattered around the wiki. It was not easy to find any step-by-step instructions for compiling 710, and I might have used the wrong instructions. But in short: I used the 710 branch, it compiled successfully on a 710 hybrid. The resulting .so was a different size than the original file, and crashed the router when I tried to use it. (No changes were made to the code, so I would guess the size should have been the same).



No, I did not manage to recompile the Mythtv plugin. Or rather, it did compile, but when I tried to replace it on the core, it just crashed the DCERouter. I never got any good advice on how to fix it.

As it happens, they've switched to DVB-T in my region (of Norway) now, so I haven't used Myth for a while (problems with viewing encrypted channels, H264 encoded broadcast not working in myth etc.). I didn't get around to try the "Don't auto-configure" setting either, so I can't tell you if it will work. I suppose it's worth a try, you can always change it back later.


Users / Re: web orbiter
« on: November 17, 2008, 11:23:22 am »
You could do what Zaerc said, or...

I have noticed the same when I tried the web orbiter. From my experience, it seems that you cannot click two times in the same place, you need to move the mouse a bit for the orbiter to register the click as a new click. Maybe you can try that?

Installation issues / Re: First time user: Help before install
« on: November 11, 2008, 01:00:01 pm »
Note that "works with lmce" can mean different things:
* Most basic interpretation is that the linux driver is included in lmce. This means that your device will be usable for linux.
* The other aspect is that lmce autodetects your device and sets it up more or less automatically. Not valid for all types of devices, but at least for some.
If you have a specific device, you should search the wiki and the forums for any information, and post a question if you cannot find any.

But in most cases hardware with linux drivers will work with lmce. A problem could be that the driver is brand new and has not been included in the linux kernel version used in lmce.

I did myself put off the compiling for quite some time, even though I have a few years of Linux experience, so I can understand your concern. I would say it is about 5 on the scale for my part. The main problem with this driver was that there were several different drivers (or variants thereof) to choose from. Besides that, the compiling were pretty straight-forward.
But lately there seems to have been quite a few changes to the driver development, and that this driver will be included in the 2.6.28 kernel. They have also removed the source I built the driver from, so I really cannot say how easy/difficult it would be to  build it today.
To build the driver today, I think you need to download the whole v4l source tree. is a good starting point.

I used the 4000 mainly for DVB-S. I think the S2 part was not supported by the driver at the time I built it. I did test DVB-T also, and it seemed to work fine. Reading the linuxtv wiki, it seems that S2 will not be supported until kernel 2.6.28 is released.

Installation issues / Re: First time user: Help before install
« on: November 07, 2008, 09:10:07 pm »
and welcome

1. The specs. look good for a first setup. If you plan on extending the system with any media directors (MDs), you might consider changing the hybrid to a core to ease the load, but I would not worry about that just yet.
Be warned: the HVR-4000 is not supported by default in LMCE. There exists a driver, but you will need to compile it yourself (See the site for more information). On the other hand, I do use this card in my setup, and it works fine once you got the setup right.
Sorry, don't know anything about the sound card.

2. You will find some forum posts regarding MKV. I suggest searching the forums, as I have not tried MKV files myself.

3. There is an option to install the dvdcss library which allows you to play DVDs. I did have problems with playing a few DVDs.

4. Dont know for sure, but since it uses the Symbian OS, it might be possible. Check the wiki for mobile orbiters. If not, the JavaMO might be a possibility, although it is now quite finnished yet.

Regarding blu-ray, there have also been some forum posts. Don't have a drive myself, so I suggest doing a search in the forum.


Users / Re: New in the Wiki: Alx9r's Sample Setup
« on: November 06, 2008, 01:20:44 pm »
My curiosity got the best of me, and I did some googling  ;)

I found a script which will receive RSS and submit the torrents for download to mldonkey.
Most likey someone can create a similar script to do the same for podcasts.

I haven't tried this setup, and have not tried deluge either. Just wanted to let you know of a possible alternative. And I think from what I have seen of mldonkey, that it allows for  easy integration into lmce, it having a command line interface, a remote protocol and more. Then again, don't know what Deluge is capable of..


Users / Re: New in the Wiki: Alx9r's Sample Setup
« on: November 05, 2008, 10:27:22 am »

Have you looked at mldonkey ? It's been a while since I looked at it, but I think it supports downloading bittorrent and http downloads. Don't think it can handle RSS though...

It uses a remote protocol to allow the client to communicate with the daemon (it's headless). It also has a telnet interface...
There exist many different clients I suppose the protocol or the telnet interface could be used from within LMCE to start downloads of different kinds.

It can also run a command when a file download is done (i.e. LMCE sql insert)


Installation issues / Re: Is anyone using JavaMo sucessfully?
« on: October 31, 2008, 02:23:37 pm »
Where can one find the source code for the JavaMO these days ? I see that they are no longer available at the URL mentioned in the wiki ( any more.


Pages: 1 ... 26 27 [28] 29 30 31