Re: [pymaemo] hildon-desktop: getting D-Bus?
On Tue, 2010-04-13 at 23:19 +0200, ext Thomas Waelti wrote: (Crossposting to maemo-devel, hoping for a Hildon-Desktop or D-Bus expert to pick this up. Original thread is at https://garage.maemo.org/pipermail/pymaemo-developers/2010-April/001444.html ) Thanks for a very interesting input. Unfortunately, it didn't work for my needs, as I must get my hands on the SYSTEM bus, not the Session one. I tried your example, changing it to self.bus = dbus.bus.BusConnection(unix:abstract=/var/run/dbus/system_bus_socket) However, I get this error: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused Isn't this the correct address of the system dbus? Or do I have a permission (or other) problem when trying to get on the system-dbus from hildon-desktop? You mean hildon-home (hildon-desktop does not have plugins). I found some code from http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html#connecting-to-the-bus = import dbus from dbus.mainloop.glib import DBusGMainLoop dbus_loop = DBusGMainLoop() bus = dbus.SessionBus(mainloop=dbus_loop) = Just replace SessionBus with SystemBus, yes? -Kimmo Thanks all -Tom As a follow-up to the discussion about d-bus from a hildon widget a few days ago that I found out while having the same problem, I've finally managed to get something that seems to be working for me: # Create a session bus. import dbus from dbus.mainloop.glib import DBusGMainLoop dbus.mainloop.glib.DBusGMainLoop(set_as_default=True) from os import environ bus = dbus.bus.BusConnection(environ[DBUS_SESSION_BUS_ADDRESS]) And then bus can be used as usual. I haven't done a whole lot of testing, as I just found this out, but it appears to be working both in command line mode and as a home widget. Yves. ___ pymaemo-developers mailing list pymaemo-develop...@garage.maemo.org https://garage.maemo.org/mailman/listinfo/pymaemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: PC Suite communication
Hi, I do not know much about you actual question about obex etc. I just wondered why you don't just setup USB/BT networking between Maemo device and host with Maemo PC Connectivity. After that you can use standard TCP/IP between host PC and device. http://maemo.org/news/announcements/maemo_pc_connectivity_2nd_edition_final_released/ Cheers, //Jarmo Date: Wed, 14 Apr 2010 03:34:21 +0200 From: Andr? H?nsel an...@webkr.de Subject: PC Suite communication To: maemo-developers@maemo.org Message-ID: 001901cadb72$9bc7fcd0$d357f6...@de Content-Type: text/plain; charset=iso-8859-1 Hi list, I am currently evaluating my chances to use the PC Suite connection to connect from an application running on the host to a daemon running on the N900. For this I'm having a look at e.g. syncd and in particular obexd. As far as I understand, when using bluetooth connection, the PC Suite application talks to one of the bluetooth COM ports. The virtual serial connection is somehow taken by BlueZ and forwarded to a socket of type PF_BLUETOOTH on which obexd listens and answers the connection. So far I don't understand how the Windows application instructs BlueZ to forward the data to a certain socket and not just to a virtual serial port. Apparently it's not an rfcomm connection since there is no rfcomm device and it doesn't show up in rfcomm output. As for the USB side I know even less. The data is probably transmitted using one of the Wireless Communication Devices (Nokia N900 USB Generic, Nokia N900 USB OBEX, Nokia N900 USB Phone Parent) and received by the g_nokia module, but how do they get to obexd? Can someone provide me with any information on these matters? Regards, Andr? ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: missing dependencies on autobuilder
Autobuilder isn't working right : it's building for Maemo PR 1.2, but our devices are on 1.1. We have no idea when PR 1.2 will be released. You can try explicitly specifying the dependencies in your control file, it might work or might not. I kinda sorta had it working but gave up and simply posted a deb file built on my machine to my project's garage page. - ianaré sévi 2010/4/14 Aapo Rantalainen aapo.rantalai...@gmail.com: Hi, I'm maintainer of this package: http://maemo.org/packages/package_instance/view/fremantle_extras-devel_free_armel/jammo/0.5.0/ There are Warning: This package has missing dependencies! And missing are: libgstreamer0.10-0 (= 0.10.25) mp-fremantle-generic-pr (= 3.2010.02-8) My application is heavily using audio processing and it is NOT working on older firmware (from year 2009). I try to be sure, that user has new firmware and new gstreamer (autobuilder has 0.10.23). 1) Is this 'Warning' stopper to promote it to extras-testing (or why I don't see promote button on package page, even I have logged in) ? 2) Why autobuilder is not using new (same) versions of libgstreamer0.10-0 or mp-fremantle-generic-pr than my N900-device? 3) Can I make this dependency check in some other way? (thus they are runtime dependencies, not compile time) -Aapo Rantalainen ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Size mismatch on the extras-devel repository
It seems there is something wrong with the extras-devel repository (at least for the armel architecture): [sbox-FREMANTLE_ARMEL: ~/git/maemo-mapper/src] apt-get install libclutter-1.0-0 Reading package lists... Done Building dependency tree... Done The following extra packages will be installed: libclutter-1.0-dbg libclutter-1.0-dev The following packages will be upgraded: libclutter-1.0-0 libclutter-1.0-dbg libclutter-1.0-dev 3 upgraded, 0 newly installed, 0 to remove and 300 not upgraded. Need to get 413kB of archives. After unpacking 123kB disk space will be freed. Do you want to continue [Y/n]? WARNING: The following packages cannot be authenticated! libclutter-1.0-dbg libclutter-1.0-dev libclutter-1.0-0 Install these packages without verification [y/N]? y Get:1 http://repository.maemo.org fremantle/free libclutter-1.0-dbg 1.0.8-0maemo1 [57.8kB] Get:2 http://repository.maemo.org fremantle/free libclutter-1.0-dev 1.0.8-0maemo1 [105kB] Get:3 http://repository.maemo.org fremantle/free libclutter-1.0-0 1.0.8-0maemo1 [250kB] Fetched 450kB in 1s (301kB/s) Failed to fetch http://repository.maemo.org/extras-devel/pool/fremantle/free/c/clutter/libclutter-1.0-0_1.0.8-0maemo1_armel.deb Size mismatch E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing? Ciao, Alberto -- http://blog.mardy.it - geek in un lingua international! ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: [pymaemo] hildon-desktop: getting D-Bus?
Thanks to all of you! Based on your feedbacks, I was able to find a solution :-) So here is on how to get your hands on a dbus system object in a python-based hildon-home widget in a way that you can attach callbacks. from dbus.mainloop.glib import DBusGMainLoop dbus.mainloop.glib.DBusGMainLoop(set_as_default=True) dbus.mainloop.glib.threads_init() class YourHomePlugin(hildondesktop.HomePluginItem): def __init__(self): self.bus = dbus.bus.BusConnection(unix:path=/var/run/dbus/system_bus_socket) This means that auto-recording now works in my Recaller widget... I'll post a new version to Extras-Devel during the next days. Thanks again to everybody! -Tom 2010/4/14 Kimmo Hämäläinen kimmo.hamalai...@nokia.com: On Tue, 2010-04-13 at 23:19 +0200, ext Thomas Waelti wrote: (Crossposting to maemo-devel, hoping for a Hildon-Desktop or D-Bus expert to pick this up. Original thread is at https://garage.maemo.org/pipermail/pymaemo-developers/2010-April/001444.html ) Thanks for a very interesting input. Unfortunately, it didn't work for my needs, as I must get my hands on the SYSTEM bus, not the Session one. I tried your example, changing it to self.bus = dbus.bus.BusConnection(unix:abstract=/var/run/dbus/system_bus_socket) However, I get this error: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused Isn't this the correct address of the system dbus? Or do I have a permission (or other) problem when trying to get on the system-dbus from hildon-desktop? You mean hildon-home (hildon-desktop does not have plugins). I found some code from http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html#connecting-to-the-bus = import dbus from dbus.mainloop.glib import DBusGMainLoop dbus_loop = DBusGMainLoop() bus = dbus.SessionBus(mainloop=dbus_loop) = Just replace SessionBus with SystemBus, yes? -Kimmo Thanks all -Tom As a follow-up to the discussion about d-bus from a hildon widget a few days ago that I found out while having the same problem, I've finally managed to get something that seems to be working for me: # Create a session bus. import dbus from dbus.mainloop.glib import DBusGMainLoop dbus.mainloop.glib.DBusGMainLoop(set_as_default=True) from os import environ bus = dbus.bus.BusConnection(environ[DBUS_SESSION_BUS_ADDRESS]) And then bus can be used as usual. I haven't done a whole lot of testing, as I just found this out, but it appears to be working both in command line mode and as a home widget. Yves. ___ pymaemo-developers mailing list pymaemo-develop...@garage.maemo.org https://garage.maemo.org/mailman/listinfo/pymaemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Squeeze devkit to be installed to autobuilder
Hello all, As part of the plan to fix the PR1.2 SDK dependency issues in the autobuilder [1], we plan to upgrade the Debian devkit in the Fremantle autobuilder to the Squeeze version [2] (from the current etch one), and start using improved shlibdeps [3] (a.k.a. .symbols files) to version dependencies on a much more granular basis (minimal required version of libraries will be calculated per symbol instead of per library). We plan to ship .symbols files for most of the SDK libraries [4]. This means that packages built in the PR1.2 SDK using no PR1.2-introduced functions will work on a PR1.1 device and even on a 1.0 device. Unfortunately, this approach doesn't include Qt packages as there are more problems to that, but we hope the Qt API to be more stable in future releases. Of course, upgrading to Squeeze _will_ cause compatibility problems to some packages. We have been rebuilding many of them in a test environment [5, 6] and analyzed the common issues -- in fact, we have talked to a few maintainers about those. If your package doesn't build when we move the autobuilder to Squeeze and you don't know how to fix it, don't hesitate to ask. We find that most of the compatibility problems are caused by stricter checks, and that is always a Good Thing (TM). If you want to swap your local SDK to squeeze, you have to 1. Install the squeeze devkit from [2] 2. Replace debian-etch devkit with debian-squeeze in scratchbox target 3. Inside target, apt-get install maemo-sdk-symbols cdbs man-db dpatch [1] http://wiki.maemo.org/Task:PR1.2_autobuilder [2] http://scratchbox.org/debian/dists/stable/main/binary-i386/scratchbox-devkit-debian-squeeze_1.0.3_i386.deb [3] http://wiki.debian.org/Projects/ImprovedDpkgShlibdeps [4] http://maemo.org/packages/view/maemo-sdk-symbols/ [5] https://garage.maemo.org/builder/.fremantletest/ [6] https://garage.maemo.org/builder/.fremantletest/__packages__/ -- Javier ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Squeeze devkit to be installed to autobuilder
Hello all, Hi, As part of the plan to fix the PR1.2 SDK dependency issues in the autobuilder [1], we plan to upgrade the Debian devkit in the Fremantle autobuilder to the Squeeze version [2] (from the current etch one), and start using improved shlibdeps [3] (a.k.a. .symbols files) to version dependencies on a much more granular basis (minimal required version of libraries will be calculated per symbol instead of per library). We plan to ship .symbols files for most of the SDK libraries [4]. This means that packages built in the PR1.2 SDK using no PR1.2-introduced functions will work on a PR1.1 device and even on a 1.0 device. As part of this task we need to decide with the 'broken' or affected packages which have been built on the PR1.2 SDK and have gotten PR1.2 dependencies. We can automatically import all rebuilt packages into extras-devel or we can decide to let developers re-submit their packages after the builder has been switched to the new setup. Thoughts? -- Javier -- Niels Breet maemo.org webmaster ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Squeeze devkit to be installed to autobuilder
First off, a big thanks for this effort. My package (soon to be two ;-) uses Qt, so I'm not sure how much this will help me personally, it is definitely an important step in the right direction. For those packages that are OK, importing them automatically is fine. However for those that do have problems, the developer should be able to control when it gets moved. I think the major lesson learned here is to try hard not to replace a working package with a broken one. It would be unwise to do the same thing again. Scenarios include abandoned packages, long developer response times, etc ... - ianaré sévi 2010/4/14 Niels Breet ni...@maemo.org: Hello all, Hi, As part of the plan to fix the PR1.2 SDK dependency issues in the autobuilder [1], we plan to upgrade the Debian devkit in the Fremantle autobuilder to the Squeeze version [2] (from the current etch one), and start using improved shlibdeps [3] (a.k.a. .symbols files) to version dependencies on a much more granular basis (minimal required version of libraries will be calculated per symbol instead of per library). We plan to ship .symbols files for most of the SDK libraries [4]. This means that packages built in the PR1.2 SDK using no PR1.2-introduced functions will work on a PR1.1 device and even on a 1.0 device. As part of this task we need to decide with the 'broken' or affected packages which have been built on the PR1.2 SDK and have gotten PR1.2 dependencies. We can automatically import all rebuilt packages into extras-devel or we can decide to let developers re-submit their packages after the builder has been switched to the new setup. Thoughts? -- Javier -- Niels Breet maemo.org webmaster ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: j2me
I was just trying to compile phoneME by myself. Since I'm using fedora on my desktop, I installed the maemo SDK virtual image (based on Ubuntu) from http://maemovmware.garage.maemo.org/2nd_edition/installation_vbox.html in VirtualBox. I subsequently updated the java sdk to version 1.6, as recommended on http://java.sun.com/javame/reference/docs/sjwc-2.2/pdf-html/html/build/introduction.html#50458631_pgfId-474483 . Now I'm looking for the *MontaVista Application Developer Kit (ADK) 5.0*. However, this seems to be non-free-software: http://www.mvista.com/product_detail_tools.php Is there any free version of the toolkit applicable for download? Any other suggestions to compile phoneME for maemo? Thanks for any hint. Chris On Sat, Apr 10, 2010 at 4:23 AM, Demetris demet...@ece.neu.edu wrote: True it does not but it has been fairly reliable at least for my application testing - I run p2p, web services, containers software under it and it has been pretty stable. But like you said no one has done extensive studies on its stability for maemo so I won't make any such claims (yet). Look here: http://wiki.java.net/bin/view/Mobileandembedded/PhoneMEAdvancedPlatformsNokia800 http://sites.google.com/site/thehereweb/runningosgionthenokian800 Also I found a few other sites that discuss building newer version of PhoneME but I cannot locate them right this minute - I will search and repost. Give these a shot and let me know how it works out. Gunter Ohrner wrote: Demetris G. Galatopoullos wrote: Not sure how much this will help you but I have been running PhoneME (J2ME CDC) on the N800 and N810 devices for a while now without any issues. The PhoneME project does not list Maemo as a reliably supported platform, is there any information on how to build PhoneME for Maemo and how to run it? I'd imagine PhoneME to be somewhat lighter on ressources than MicroEmu... Greetings, Gunter ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: [pymaemo] hildon-desktop: getting D-Bus?
As a final status update: a vastly improved version of Recaller has been built and uploaded - it will show up in extras-devel during the next hours :-) Thanks for all the inputs and have fun -Tom Thanks to all of you! Based on your feedbacks, I was able to find a solution :-) So here is on how to get your hands on a dbus system object in a python-based hildon-home widget in a way that you can attach callbacks. from dbus.mainloop.glib import DBusGMainLoop dbus.mainloop.glib.DBusGMainLoop(set_as_default=True) dbus.mainloop.glib.threads_init() class YourHomePlugin(hildondesktop.HomePluginItem): def __init__(self): self.bus = dbus.bus.BusConnection(unix:path=/var/run/dbus/system_bus_socket) This means that auto-recording now works in my Recaller widget... I'll post a new version to Extras-Devel during the next days. Thanks again to everybody! -Tom 2010/4/14 Kimmo Hämäläinen kimmo.hamalai...@nokia.com: On Tue, 2010-04-13 at 23:19 +0200, ext Thomas Waelti wrote: (Crossposting to maemo-devel, hoping for a Hildon-Desktop or D-Bus expert to pick this up. Original thread is at https://garage.maemo.org/pipermail/pymaemo-developers/2010-April/001444.html ) Thanks for a very interesting input. Unfortunately, it didn't work for my needs, as I must get my hands on the SYSTEM bus, not the Session one. I tried your example, changing it to self.bus = dbus.bus.BusConnection(unix:abstract=/var/run/dbus/system_bus_socket) However, I get this error: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoServer: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused Isn't this the correct address of the system dbus? Or do I have a permission (or other) problem when trying to get on the system-dbus from hildon-desktop? You mean hildon-home (hildon-desktop does not have plugins). I found some code from http://dbus.freedesktop.org/doc/dbus-python/doc/tutorial.html#connecting-to-the-bus = import dbus from dbus.mainloop.glib import DBusGMainLoop dbus_loop = DBusGMainLoop() bus = dbus.SessionBus(mainloop=dbus_loop) = Just replace SessionBus with SystemBus, yes? -Kimmo Thanks all -Tom As a follow-up to the discussion about d-bus from a hildon widget a few days ago that I found out while having the same problem, I've finally managed to get something that seems to be working for me: # Create a session bus. import dbus from dbus.mainloop.glib import DBusGMainLoop dbus.mainloop.glib.DBusGMainLoop(set_as_default=True) from os import environ bus = dbus.bus.BusConnection(environ[DBUS_SESSION_BUS_ADDRESS]) And then bus can be used as usual. I haven't done a whole lot of testing, as I just found this out, but it appears to be working both in command line mode and as a home widget. Yves. ___ pymaemo-developers mailing list pymaemo-develop...@garage.maemo.org https://garage.maemo.org/mailman/listinfo/pymaemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: j2me
Hey Chris, unfortunately I have been using the already compiled version that the links I sent you below were advertizing. I have not tried to compile newer versions of it so your best source would be the web. I will also dig around and let you know if I find anything that can help you out. Christopher Intemann wrote: I was just trying to compile phoneME by myself. Since I'm using fedora on my desktop, I installed the maemo SDK virtual image (based on Ubuntu) from http://maemovmware.garage.maemo.org/2nd_edition/installation_vbox.html in VirtualBox. I subsequently updated the java sdk to version 1.6, as recommended on http://java.sun.com/javame/reference/docs/sjwc-2.2/pdf-html/html/build/introduction.html#50458631_pgfId-474483. Now I'm looking for the /MontaVista Application Developer Kit (ADK) 5.0/. However, this seems to be non-free-software: http://www.mvista.com/product_detail_tools.php Is there any free version of the toolkit applicable for download? Any other suggestions to compile phoneME for maemo? Thanks for any hint. Chris On Sat, Apr 10, 2010 at 4:23 AM, Demetris demet...@ece.neu.edu mailto:demet...@ece.neu.edu wrote: True it does not but it has been fairly reliable at least for my application testing - I run p2p, web services, containers software under it and it has been pretty stable. But like you said no one has done extensive studies on its stability for maemo so I won't make any such claims (yet). Look here: http://wiki.java.net/bin/view/Mobileandembedded/PhoneMEAdvancedPlatformsNokia800 http://sites.google.com/site/thehereweb/runningosgionthenokian800 Also I found a few other sites that discuss building newer version of PhoneME but I cannot locate them right this minute - I will search and repost. Give these a shot and let me know how it works out. Gunter Ohrner wrote: Demetris G. Galatopoullos wrote: Not sure how much this will help you but I have been running PhoneME (J2ME CDC) on the N800 and N810 devices for a while now without any issues. The PhoneME project does not list Maemo as a reliably supported platform, is there any information on how to build PhoneME for Maemo and how to run it? I'd imagine PhoneME to be somewhat lighter on ressources than MicroEmu... Greetings, Gunter ___ maemo-developers mailing list maemo-developers@maemo.org mailto:maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org mailto:maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
