Re: to Moderators
Hello, On Mon, 2011-02-21 at 16:58 +0300, DmitryTurin.narod.ru wrote: Adjust your server of mailing list, that it automatically append the following into EACH letter: 1) [MeeGo] into topic of letter. Now i'm subscribed to not one mailing list, and i cannot distinguish your letters from others. 2) http://; with address of page, where i can unsubscribe 0) please be polite (hello, please, thanks, etc.) 1) there are many headers for the mailing-list, especially this one :List-Id: for maemo developers maemo-developers.maemo.org 2) look at the bottom of the mail. Cheers, Xav ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Low Latency Audio Capture on the N900, QAudioInput BUG: has 5000msec latency, Meego audio future
On Wed, 2010-06-16 at 01:27 +0200, Benno Senoner wrote: So my advice to Nokia, while still in time, cosider switching to JACK as an audio server for future versions of Meego, The N900 already sucks batteries like mad. JACK is a no-compromise low-latency pro audio server, and does it at the expense of some processor time. You don't want it on an N900, otherwise the poor battery life would be even worse. Xav ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Low Latency Audio Capture on the N900, QAudioInput BUG: has 5000msec latency, Meego audio future
On Wed, 2010-06-16 at 11:56 +0200, Benno Senoner wrote: Hi, Can you back up your claims that pulseaudio uses less CPU than JACK ? pulseaudio cannot do wonders, if mixing is required the code must sum up the inputs, jack does this already in the most efficient manner and one can easily add ARM vector code to speed it up. The typical use case is only one sound played at the same time. In that case the sound server needs to: - not do mixing - use as few interrupts as possible, i.e. having the biggest acceptable latency possible. Otherwise the sound hardware keeps waking up the processor to fill a tiny buffer again and again. I don't know for the first, but I'm pretty sure JACK isn't designed to do the last. Xav ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Is maemo.org web site down?
Hi, On Mon, 2010-03-29 at 09:22 +0300, Sascha Mäkelä wrote: Is it only me or is the maemo.org site down? I only get a blank page. A general answer to this kind of question: http://downforeveryoneorjustme.com/ Xav ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: German Maemo OS on US device?
Le samedi 13 mars 2010 à 14:13 +0100, Christopher Intemann a écrit : Hi, is it possible to install the German localisation of Maemo-OS on a US device? I'm wondering how open Maemo *really* is. I've just set my US N900 to French, and it all works well. Just don't forget to keep the keyboard set to English/Netherlands (it's not autodetected). Xav ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Hildon Input Method
Hi, Le lundi 08 mars 2010 à 19:38 +0100, Cornelius Hald a écrit : Hi, I have two questions regarding Hildon Input Method. 1) Is it possible to deactivate the word completion for a complete window or for a Hildon/GtkEntry? I think so. 2) Is it possible to tell HIM, that it should capitalize the next typed letter, even if it is not the beginning of a new sentence? It's possible to autocapitalize, I don't know if the reverse works. Would be great if someone could point me in the right direction. Start here: http://maemo.org/api_refs/5.0/5.0-final/gtk/GtkIMContext.html#HildonGtkInputMode HTH, Xav ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Maemo 5 PR1.2 and Extras
On Wed, 2010-02-24 at 17:48 +, Graham Cobb wrote: On Wednesday 24 February 2010 17:18:29 Thomas Tanner wrote: On 24.02.10 18:04, Graham Cobb wrote: Why do I think many people will not upgrade? This device is a phone. The N900 is a mobile computer. I am talking about the people who perceive it to be a phone. Like the iPhone. I don't think iPhone owners really have the choice to not update. Xav ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Conversation Facebook plugin
Hi, On Thu, 2010-02-11 at 17:34 +0100, Xavier Bestel wrote: On Thu, 2010-02-11 at 10:01 +, Jonny Lamb wrote: On Wed, Feb 10, 18:42:48 -0600, Kahlil Johnson wrote: Facebook recently change to XMPP protocol and this might affect the Facebook addition to Conversations that used to rely on JSON. Would love to see an update soon I intend to do this today or tomorrow. Thank you very much for this. Do you intend to migrate the contacts automatically ? Any news about that ? Xav ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: N900 Charging Issue
Le samedi 20 février 2010 à 23:08 +1300, Charles a écrit : Hi all, has anyone had this kind of charging issues for N900? My problem was when I plugged in the USB cable into N900 it did not show up the mode selection dialogue and did not show any charging indication either. The same happened with the wall-charger as well. Also, when i turned the phone off and plugged in the USB cable, the front LED flashed yellow twice and nothing happens. I am so annoying by this issue as I cannot charge the phone properly. Is this something related to the Maemo software? Maybe it's a hardware problem, I know there has been troubles with the µUSB connector for some. I hope you didn't buy your N900 overseas. Mine was bought in the US, and Nokia Europe refuses to take it under warranty because of that. Now I'm stuck with a dead pixel, and I hope nothing worst will happen. Xav ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Conversation Facebook plugin
On Thu, 2010-02-11 at 10:01 +, Jonny Lamb wrote: On Wed, Feb 10, 18:42:48 -0600, Kahlil Johnson wrote: Facebook recently change to XMPP protocol and this might affect the Facebook addition to Conversations that used to rely on JSON. Would love to see an update soon I intend to do this today or tomorrow. Thank you very much for this. Do you intend to migrate the contacts automatically ? Xav ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to capture ALL key events, no focus/No-GUI
On Thu, 2010-01-28 at 09:33 +0100, Stefan Iwanowitsch wrote: Hi everybody, I've tried to figure out for some days, how I can capture ALL key events even if I have no focus on my window or if my app is running without GUI. Failed sofar :( Using Fremantle/Hildon/GTK Any suggestions are welcome! Have a look at the XTEST extension. Xav ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: gtk clutter tearing
On Wed, 2009-12-30 at 14:44 +0200, Eero Tamminen wrote: Hi, ext Claudio Saavedra wrote: El mar, 29-12-2009 a las 17:17 +0200, Eero Tamminen escribió: This is not really fixable due to how Gtk painting is arranged, parts of the window are painted in application callbacks. This is not totally correct. Application callbacks can only cause GTK+ to *invalidate* regions. In sane code, redrawing *never* happens in a user callback but only in expose event callbacks, which are triggered by GTK+ *only* when the time for redrawing comes. Application (expose event) callbacks implement painting for application's own widgets and treeview cell renderers. But where inside the application process they happen (app or Gtk code) is not so important. The issue is that Gtk (AFAIK) has no mechanism to synchronize this drawing with the compositor and doesn't offer applications any mechanism for it either. If painting/redrawing takes too long (there's some delay between the X draw commands due to what application does internally), it doesn't go the the same boxed XDamage event to the compositor. AFAIK GTK+ redraws are double-buffered, so if it takes too long to redraw a frame it's simply delayed until the next one. Xav ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Fw: Re: gtk clutter tearing
On Wed, 2009-12-30 at 15:40 +, Mark Clarkson wrote: - Original message - off on the *compositor*. My own apps are tear free until I turn off.. Ah. Is there some way that this will help me - the original poster? Does clutter bypass the compositor by making its opengl calls? Do I need to somehow render clutter output to an offscreen buffer and let the compositor smooth things for me as I blit them back on screen? That's true. You could try playing with the CLUTTER_VBLANK env var (set it to none, dri or glx) to see if it helps. Xav ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: N900 usb host + power charge
Le samedi 19 septembre 2009 à 15:44 +0300, Matan Ziv-Av a écrit : BTW, since webcams don't have a USB standard, and need a driver anyway, you can implement such driver over existing transports such as serial or ethernet. Webcams do have such a standard, it's called UVC (USB Video Class). They don't need a driver (at least under a recent Linux kernel). Xav ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How much are Nxxx open?
Hi, On Mon, 2009-08-31 at 18:27 -0400, Jason Edgecombe wrote: I'm not sure how open the phone part is because they haven't come out yet. I can tell you that the non-phone predecessors are very open. There are two things that aren't open: the OpenGL video drivers and the wifi drivers. Apparently there's a bit more than that: http://wiki.maemo.org/Why_the_closed_packages Xav ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How much are Nxxx open?
On Tue, 2009-09-01 at 10:54 +0200, Ralph Angenendt wrote: On Tue, 2009-09-01 at 09:52 +0200, Xavier Bestel wrote: On Mon, 2009-08-31 at 18:27 -0400, Jason Edgecombe wrote: I'm not sure how open the phone part is because they haven't come out yet. I can tell you that the non-phone predecessors are very open. There are two things that aren't open: the OpenGL video drivers and the wifi drivers. Apparently there's a bit more than that: http://wiki.maemo.org/Why_the_closed_packages Although it is not clear at all which of those packages are still closed in Fremantle, this looks more like a maemo 4 list. Yes, that's what Jason talked about: non-phone predecessors are very open. Xav ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
