Re: /dev/dsp
Hi! GTick is seriously cool for musicians, especially if it is on a n770/800 Excellent idea :) I can see from the source that GTick only works with OSS. Unfortunately, OSS is not supported... Extra work will be needed. An application can use GStreamer, ALSA or esd: http://maemo.org/development/documentation/how-tos/3-x/multimedia_architecture.html Is your progress already published on a git branch, or garage? Cheers, On Sat, 2007-09-08 at 20:17 +0200, ext Detlef Schmicker wrote: Hay, I tried to port gtick (metronom application). I need to enter the sound device, but there is no /dev/dsp availible. Is there an easy way to install one?! Thanks Detlef ___ 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: Porting fltk-app
Hi, ext Tapani Pälli wrote: I am trying to port an FLTK (www.fltk.org) application to N770/N800. I got FLTK compiled and the application as well, but when I run the application, it is not managed by Matchbox. That is, the program is not shown in the taskbar and the keyboard will not pop up. I have tried to hack FLTK according to the code snippets https://garage.maemo.org/snippet/detail.php?type=snippetid=3 and https://garage.maemo.org/snippet/detail.php?type=snippetid=4 but without luck. What do I need in order for Matchbox being aware of my program? The window is being managed by matchbox. Maemo input-methods (keyboard, hwr) use their own protocol to communicate directly with gtk-widgets. You have to implement this protocol in text-entry fltk-widgets. Basically it means sending an X to the input method window when the widget wants the input method to show itself. In the Maemo Gtk this happens when user taps to a widget. Maemo Input Method framework was just opened, so now other widget sets like Fltk or Qt can be fully ported to Maemo. The IM protocol source for widget - input method communication is here: https://stage.maemo.org/svn/maemo/projects/haf/trunk/hildon-input-method-framework/src/ In order to get program shown in taskbar (which is a pager, not a component of window manager) you have to provide valid .desktop file. Instructions to do this is in maemo.org documentation. - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Possible libosso bug?
I encountered the following unexpected behaviour while testing my application, and I wanted to run it past the people on this list to see if this is a known feature. My application opens the browser as part of its normal operation. On application exit, the browser is closed. The call used to do this is: osso_rpc_run_with_defaults(mvarAppCtx, osso_browser, OSSO_BROWSER_EXIT, NULL, DBUS_TYPE_INVALID); Now, if the browser is open when this call runs, it closes down exactly as expected. However, if it has already been closed by the user, the above call OPENS it! Given that the call is telling the browser to exit, I would expect one of two things to happen if the browser is not open: 1) The call is ignored, because it is asking for a browser state that already exists 2) The call fires up the browser and immediately closes it (because the OSSO_BROWSER_EXIT request has to be dealt with by the browser itself). Instead, what actually happens is that the browser opens and stays open (on its default home page). Is this a known feature of libosso or the Browser? If not, should I report it as a bug? David Hazel ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
webkit based browser for 770/N800?
As Nokia is using a webkit based browser for some Symbian60 mobile phones, is there any specific reason, why they don´t use it for the 770/N800? Does anybody work on this somewhere? TIA. Hannes Wolf (CyBear). ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: webkit based browser for 770/N800?
On 9/10/07, Hannes Wolf [EMAIL PROTECTED] wrote: As Nokia is using a webkit based browser for some Symbian60 mobile phones, is there any specific reason, why they don´t use it for the 770/N800? Does anybody work on this somewhere? A quick googling gave the following news items saying that something is happening... http://arstechnica.com/journals/linux.ars/2007/08/07/new-webkit-backend-under-development-for-n800-web-browser http://www.atoker.com/blog/2007/09/05/webkitgtk-at-linuxconf-europe-2007/ TIA. Hannes Wolf (CyBear). /Bergie -- Henri Bergius Motorcycle Adventures and Free Software http://bergie.iki.fi/ Skype: henribergius Jabber: [EMAIL PROTECTED] Jaiku: http://bergie.jaiku.com/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
bluetooth service found by PC but not by the 770 - why?
I run the rfcomm_server.py script [1] on my N70 with PyS60: it creates a service with name jurgen on a free serial port. If i scan for services from the Python console on my PC (with a bluetooth dongle), I can see a jurgen service is present on port 4. These is what I write in the python console in order to look for services: from bluetooth import * devices = discover_devices(lookup_names = True, flush_cache = True, duration = 20) for addr, name in devices: ... print find_service(address = addr) Then, I load the Python 2.5 console on my 770, and with the very same lines I look for the services from it, but... the list looks the same, while the jurgen service is not present there. Anyway, if I try connecting to the service on the N70 from the 770, using the serial port number I can read with PC, the bluetooth communication N70-770 takes place: host = my N70's address port = 4 sock = BluetoothSocket(RFCOMM) sock.connect((host, port)) ...the N70 receives the connection from the 770, and asks for a string, which I can easily read and display with the 770. So, why I can't see the created service with the find_service() command from the 770? [1] http://www.mobilenin.com/pys60/resources/rfcomm_server.py -- Antonio ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Possible libosso bug?
Hi, ext David Hazel wrote: I encountered the following unexpected behaviour while testing my application, and I wanted to run it past the people on this list to see if this is a known feature. My application opens the browser as part of its normal operation. On application exit, the browser is closed. The call used to do this is: osso_rpc_run_with_defaults(mvarAppCtx, osso_browser, OSSO_BROWSER_EXIT, NULL, DBUS_TYPE_INVALID); Now, if the browser is open when this call runs, it closes down exactly as expected. However, if it has already been closed by the user, the above call OPENS it! Given that the call is telling the browser to exit, I would expect one of two things to happen if the browser is not open: 1) The call is ignored, because it is asking for a browser state that already exists The messages are answered by the co. processes, not D-BUS itself. If the message is sent with auto-activation flag, the co. process is started. Otherwise the message is lost (I think). I think all these libosso functions use the D-BUS auto-activation flag. 2) The call fires up the browser and immediately closes it (because the OSSO_BROWSER_EXIT request has to be dealt with by the browser itself). Instead, what actually happens is that the browser opens and stays open (on its default home page). Is this a known feature of libosso or the Browser? If not, should I report it as a bug? I would say that it's a bug in the Browser. You might also use the co. D-BUS message directly _without_ auto-activation. - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Possible libosso bug?
Eero Tamminen wrote: The messages are answered by the co. processes, not D-BUS itself. If the message is sent with auto-activation flag, the co. process is started. Otherwise the message is lost (I think). If you pass something as retval, you will get error code and something like No such service in the retval s-field. I think all these libosso functions use the D-BUS auto-activation flag. True for osso_* -- muali -functions seem not to. I would say that it's a bug in the Browser. I agree. You might also use the co. D-BUS message directly _without_ auto-activation. That should do it (or you could ask dbus if the service is running or not). OTOH telling the browser to exit is not nice, the user might be using it for something else too. -- Santtu Lakkala ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: bluetooth service found by PC but not by the 770 - why?
devices = discover_devices(lookup_names = True, flush_cache = True, duration = 20) Note: of course this is on the same line. -- Antonio ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
2007 HE and usb mouse
Every few months I take another run at getting a USB mouse working with my Nokia 770. After hooking up the self-powered hub and who ha, I can see the mouse is recognized and working via cat /dev/input/event3 and moving the mouse generates lots of characters. So, now I would like the Xomap server to use it as input currently the Xomap server does something like this (in /etc/init.d/x-server) $ Xomap -mouse tslib ... I was hoping that $ Xomap -mouse /dev/input/event3 ... would bring me joy... alas no joy. Does anyone have any ideas about how to cause the Xomap server to use the usb mouse and not the touch screen? Or how to configure tslib to use both the touch screen and the real mouse (say via a /etc/ts.config module perhaps?) Thanks! -bob ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Python + GTK event question
I know this is likely more of a Python + GTK question, but I'm banging my head against the wall and was hoping someone could help. I've written a blog post about it as well: http://www.maro.net/ossramblings.php?itemid=369 It's regarding the GTK kinetic scrolling widget I released last week. Basically, without getting too deep into the code, here's what I do: Create a kinetic scrolling widget. It's a descendant of a DrawingArea. I extend that and I allow the new component to hook to some of it's own events (probably a bad idea, but oh well) so that the new component knows when the user clicks or drags. It watches button_press, button_release and motion_notify events. When it's realized, it starts a timer for drawing itself - kind of a framerate timer. In the button_release_event, I might pass a callback to the application telling it the user clicked a selection. In that callback, I destroy the widget and create a new identical widget. I then show the new widget, with a new list. When the widget gets the realize event, it starts an internal timer (which I remove when the widget is destroyed) using gobject.timeout_add(75, self.updateme) I've tested the updateme function and it takes about .04 to .09 seconds to execute. Because timeouts don't block other things and don't try to make up time, I don't get a solid frame rate, but I should get at least .075 seconds between each event. Now, when you run the first widget, everything does fine. I get all the mousemove events, to the tune of 1 to 15 between each tick. I set a print statement in the updateme event so I get a line printed every tick, and you can watch them fly by. When you click an item, it triggers the callback in the application that destroys the widget (which removes the timer just fine). Then new widget will then get realized and works almost as expected, except that you can visibly see that the updateme routine is being called at about half the speed that it was called the first time, and you only get one pointer motion event between every tick. This means that as much as 30 seconds after you let go of the screen, the app might be getting notified of pointer motion events still. Have I gone wrong at some basic level somewhere? The widget creation is done identically both times. Here's the sample code from the application (not the widget): http://pastebin.org/2151 The only thing I can think of is that it must have something to do with deleting and creating a new widget from inside the callback of the first widget. If I start the process all over again with the same instance of the app, it's back to normal speed with the first widget, so it's not something that's hogging CPU. In fact, top output shows almost no activity during the slowdown. -- Tony Maro http://www.maro.net/ossramblings.php ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
plugin nokia N800 kernel report access beyond the end of device
http://bugzilla.kernel.org/show_bug.cgi?id=9005 Description From Dave Young 2007-09-10 18:33 [reply] Most recent kernel where this bug did not occur: Dont know Distribution:Slackware Hardware Environment:Dell desktop (x86) Software Environment: Problem Description: When I plugin the nokia N800, kernel reports some error messages : Sep 10 17:17:22 darkstar kernel: usb 1-2: new high speed USB device using ehci_hcd and address 5 Sep 10 17:17:22 darkstar kernel: usb 1-2: configuration #1 chosen from 1 choice Sep 10 17:17:22 darkstar kernel: scsi2 : SCSI emulation for USB Mass Storage devices Sep 10 17:17:27 darkstar kernel: scsi 2:0:0:0: Direct-Access NokiaN800 0316 PQ: 0 ANSI: 2 Sep 10 17:17:27 darkstar kernel: sd 2:0:0:0: [sdb] 246016 512-byte hardware sectors (126 MB) Sep 10 17:17:27 darkstar kernel: sd 2:0:0:0: [sdb] Write Protect is off Sep 10 17:17:27 darkstar kernel: sd 2:0:0:0: [sdb] 246016 512-byte hardware sectors (126 MB) Sep 10 17:17:27 darkstar kernel: sd 2:0:0:0: [sdb] Write Protect is off Sep 10 17:17:27 darkstar kernel: sdb:7usb-storage: queuecommand called Sep 10 17:17:27 darkstar kernel: sd 2:0:0:0: [sdb] Attached SCSI removable disk Sep 10 17:17:27 darkstar kernel: sd 2:0:0:0: Attached scsi generic sg1 type 0 Sep 10 17:17:27 darkstar kernel: attempt to access beyond end of device Sep 10 17:17:27 darkstar kernel: sdb: rw=0, want=250722, limit=246016 Sep 10 17:17:27 darkstar kernel: attempt to access beyond end of device Sep 10 17:17:27 darkstar kernel: sdb: rw=0, want=250723, limit=246016 Sep 10 17:17:27 darkstar kernel: attempt to access beyond end of device Sep 10 17:17:27 darkstar kernel: sdb: rw=0, want=250724, limit=246016 Sep 10 17:17:27 darkstar kernel: attempt to access beyond end of device Sep 10 17:17:27 darkstar kernel: sdb: rw=0, want=250725, limit=246016 Sep 10 17:17:27 darkstar kernel: attempt to access beyond end of device Sep 10 17:17:27 darkstar kernel: sdb: rw=0, want=250726, limit=246016 Sep 10 17:17:27 darkstar kernel: attempt to access beyond end of device Sep 10 17:17:27 darkstar kernel: sdb: rw=0, want=250727, limit=246016 Sep 10 17:17:27 darkstar kernel: attempt to access beyond end of device Sep 10 17:17:27 darkstar kernel: sdb: rw=0, want=250728, limit=246016 ... Steps to reproduce: Just plug the device into host usb port. Regards dave ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
