Re: [maemo-developers] How to determine if the screen has turned off?
Johan Bilien wrote: http://maemo.org/platform/docs/api/libosso/html/index.html You can register a callback with osso_hw_set_event_cb, set the system_inactivity_ind flag in the osso_hw_state_t argument. Will this callback be called even without processing gtk/glib loop? If not is there other way how to check for blanked display e.g. from SDL app? How SDL games shipped with device do that? Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
RE: [maemo-developers] How to determine if the screen has turned off?
>> http://maemo.org/platform/docs/api/libosso/html/index.html >> >> You can register a callback with osso_hw_set_event_cb, set the >> system_inactivity_ind flag in the osso_hw_state_t argument. >> > >Will this callback be called even without processing gtk/glib loop? >If not is there other way how to check for blanked display >e.g. from SDL app? How SDL games shipped with device do that? > >Frantisek Hi, Shipped SDL games use wrappers to get some useful callbacks. It is not documented anywhere AFAIK (but sure enough we do have a howto for SDL_net that is about 100% useless for the device). Br, --jakub ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] How to determine if the screen has turned off?
On Wed, 2006-12-13 at 15:22 -0800, ext Aaron Levinson wrote: > On Wed, 13 Dec 2006, Johan Bilien wrote: > > > On Wed, Dec 13, 2006, Aaron Levinson wrote: > > > In the Maemo coding style and programming guidelines document on > > > maemo.org, it states the following: "Avoid updating the GUI when the > > > application running on the background and when the screen has been turned > > > off. Remove unnecessary graphical elements or constantly updated screen > > > components." Now, it appears that hildon_window_get_is_topmost() or > > > hildon_program_get_is_topmost() can be used to determine if an application > > > is running in the background, but how does one programmatically determine > > > if the screen has been turned off? I see in the latest version of libosso > > > in SVN that there is a muali API that provides the ability to access the > > > information via a callback, but it is unclear how to determine this on 2.0 > > > or 2.1. Perhaps I can use XScreenSaverQueryInfo() ? > > > > http://maemo.org/platform/docs/api/libosso/html/index.html > > > > You can register a callback with osso_hw_set_event_cb, set the > > system_inactivity_ind flag in the osso_hw_state_t argument. > > Well, I had already examining the libosso APIs before sending the e-mail, > and I did notice the system_inactivity_ind flag in the osso_hw_state_t > struct. However, according to the libosso documentation, if the callback > is called for system inactivity, this means that "the application should > reduce its activity". I didn't directly associate this text with the > screen being blanked, which I think is understandable, since screen > blanking is not the same thing. > > What are the conditions that result in the callback for the system > inactivity indicator being called? The statement "the application should > reduce its activity" is somewhat open-ended, and perhaps this callback is > used for more than just to indicate that the screen has been blanked. It's not clear to me either, but you can use the system_inactivity_ind for the display on/off information as well (I added that to the trunk libosso.h). I have verified this from the MCE guys some time ago. I'll ask for comments about the new 'muali' API at some point. Now I'm pondering about the API to replace the osso_rpc_* functions. BR; Kimmo > > Thanks, > Aaron > > ___ > maemo-developers mailing list > maemo-developers@maemo.org > https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] How to determine if the screen has turned off?
ext Frantisek Dufka wrote: > Johan Bilien wrote: >> >> http://maemo.org/platform/docs/api/libosso/html/index.html >> >> You can register a callback with osso_hw_set_event_cb, set the >> system_inactivity_ind flag in the osso_hw_state_t argument. >> > > Will this callback be called even without processing gtk/glib loop? Yes > If not is there other way how to check for blanked display e.g. from > SDL app? How SDL games shipped with device do that? > Nope, but this shouldn't be problem. Just include libosso.h and use the functions. > Frantisek > > ___ > maemo-developers mailing list > maemo-developers@maemo.org > https://maemo.org/mailman/listinfo/maemo-developers > // Tapani ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] How to determine if the screen has turned off?
Hi, >> http://maemo.org/platform/docs/api/libosso/html/index.html >> >> You can register a callback with osso_hw_set_event_cb, set the >> system_inactivity_ind flag in the osso_hw_state_t argument. > > Will this callback be called even without processing gtk/glib loop? > If not is there other way how to check for blanked display e.g. from SDL > app? How SDL games shipped with device do that? I think the app loses focus when the screen is blanked. So, the SDL app could catch screen focus events and do some additional checks when that happens. Can the device state be checked e.g. from some file on the filesystem (it would be better if SDL apps wouldn't need to use/link D-BUS)? Whether app is top one can be checked from a Matchbox maintained (root?) window X property I think. Or SDL app could always pause when it loses focus... - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] How to determine if the screen has turned off?
On Thu, Dec 14, 2006 at 11:16:02AM +0200, ext Eero Tamminen wrote: > I think the app loses focus when the screen is blanked. > So, the SDL app could catch screen focus events and do > some additional checks when that happens. Right: as far as I can tell, a big black window covers the entire screen. This will trigger the usual FocusOut/VisibilityNotify=VisibilityFullyObscured chain of events. This should be used anyway, since drawing to the screen when someone's switched to the browser or whatever and away from your app, isn't wildly useful. > Can the device > state be checked e.g. from some file on the filesystem > (it would be better if SDL apps wouldn't need to use/link > D-BUS)? There is indeed a file in sysfs somewhere. Cheers, Daniel signature.asc Description: Digital signature ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] How to determine if the screen has turned off?
On Thu, 2006-12-14 at 11:16 +0200, ext Eero Tamminen wrote: > Hi, > > >> http://maemo.org/platform/docs/api/libosso/html/index.html > >> > >> You can register a callback with osso_hw_set_event_cb, set the > >> system_inactivity_ind flag in the osso_hw_state_t argument. > > > > Will this callback be called even without processing gtk/glib loop? > > If not is there other way how to check for blanked display e.g. from SDL > > app? How SDL games shipped with device do that? > > I think the app loses focus when the screen is blanked. > So, the SDL app could catch screen focus events and do > some additional checks when that happens. Can the device > state be checked e.g. from some file on the filesystem > (it would be better if SDL apps wouldn't need to use/link > D-BUS)? AFAIK, it's not possible. MCE has D-Bus interface only. D-Bus is used so much in Maemo that it's quite hard to not use it :P BR; Kimmo > > Whether app is top one can be checked from a Matchbox > maintained (root?) window X property I think. > > Or SDL app could always pause when it loses focus... > > > - Eero > ___ > maemo-developers mailing list > maemo-developers@maemo.org > https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] binary kernel module packages
Hi, I have been trying to find a solution about how to pack nfs-client kernel modules properly and clean way. Does anyone here know any way of building binary module package from exiting kernel source tree? To put it another way, how to build nfs-client-modules debian package from kernel source package? I looked make-kpkg, but it really doesn't provide any ways to do this and I didn't find any other way either. In Debian Etch they have been thinking something related to this, but I was able to find only one article: http://swik.net/Debian/Planet+Debian/Daniel+Baumann:+Kernel+Modules +Packaging/q089 If you have any ideas, please let me know. Thanks, -- Miko Nieminen <[EMAIL PROTECTED]> ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] extras repository
On Thu, 2006-12-07 at 13:14 +0200, Marius Vollmer wrote: > Hmm, careful here. We have to think about the relationships between > distributions as well, such as what happens when you change your > /etc/apt/sources.list and then do apt-get dist-upgrade. Also, the > point of unstable and testing is that package migrate _as_binaries_ > from one to the other based on certain criteria. (Sardine and herring > are past that point already, I think. Herring is actually already the > new stable and in an ideal world would be named bora.) > Isn't Bora supposed to be SDK release name and Herring is a code name for HAF development branch (more stable than Sardine). If so, wouldn't it be incorrect to call current Herring as Bora? SDK is more than HAF. Sorry about my pedantic nature in some cases :) Sincerely, -- Miko Nieminen <[EMAIL PROTECTED]> ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] How to determine if the screen has turned off?
On tor, 2006-12-14 at 11:01 +0200, ext Kimmo Hämäläinen wrote: > On Wed, 2006-12-13 at 15:22 -0800, ext Aaron Levinson wrote: > > On Wed, 13 Dec 2006, Johan Bilien wrote: > > > > > On Wed, Dec 13, 2006, Aaron Levinson wrote: > > > > In the Maemo coding style and programming guidelines document on > > > > maemo.org, it states the following: "Avoid updating the GUI when the > > > > application running on the background and when the screen has been > > > > turned > > > > off. Remove unnecessary graphical elements or constantly updated screen > > > > components." Now, it appears that hildon_window_get_is_topmost() or > > > > hildon_program_get_is_topmost() can be used to determine if an > > > > application > > > > is running in the background, but how does one programmatically > > > > determine > > > > if the screen has been turned off? I see in the latest version of > > > > libosso > > > > in SVN that there is a muali API that provides the ability to access the > > > > information via a callback, but it is unclear how to determine this on > > > > 2.0 > > > > or 2.1. Perhaps I can use XScreenSaverQueryInfo() ? > > > > > > http://maemo.org/platform/docs/api/libosso/html/index.html > > > > > > You can register a callback with osso_hw_set_event_cb, set the > > > system_inactivity_ind flag in the osso_hw_state_t argument. > > > > Well, I had already examining the libosso APIs before sending the e-mail, > > and I did notice the system_inactivity_ind flag in the osso_hw_state_t > > struct. However, according to the libosso documentation, if the callback > > is called for system inactivity, this means that "the application should > > reduce its activity". I didn't directly associate this text with the > > screen being blanked, which I think is understandable, since screen > > blanking is not the same thing. > > > > What are the conditions that result in the callback for the system > > inactivity indicator being called? The statement "the application should > > reduce its activity" is somewhat open-ended, and perhaps this callback is > > used for more than just to indicate that the screen has been blanked. > > It's not clear to me either, but you can use the system_inactivity_ind > for the display on/off information as well (I added that to the trunk > libosso.h). I have verified this from the MCE guys some time ago. (MCE guys -- that'd be me, I guess?) Basically, the system_inactivity_ind should not be used for display on/off information, since activity is supposed to be tied to user activity, not screen state; the system can be inactive but still have the display on (however, MCE will not report it as inactive in that case). Sadly some applications relies on the display <-> activity connection, so MCE reports display on as activity, and it will still remain supported for a few releases to come. However, I want to make it clear that this is not the proper way to do it, and that such an assumption will be incorrect in the long run. I guess the big problem is that there really hasn't been any proper way to do things... The next version of MCE will introduce a new D-Bus signal for this purpose (display_status_ind, and the companion method-call get_display_status), and one or two releases later the old behaviour will no longer be supported. Hopefully these signals will also be taken in use by libosso. [snip] Regards: David ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] How to determine if the screen has turned off?
Eero Tamminen wrote: I think the app loses focus when the screen is blanked. So, the SDL app could catch screen focus events and do some additional checks when that happens. Good idea, thanks. Or SDL app could always pause when it loses focus... This is good for video updates but sometimes not good for sound or AI code in games. Of course when the device is really inactive (whatever that means exactly) sound and other stuff should be stopped too. Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] How to determine if the screen has turned off?
ext Frantisek Dufka wrote: > Eero Tamminen wrote: >> I think the app loses focus when the screen is blanked. >> So, the SDL app could catch screen focus events and do >> some additional checks when that happens. > > Good idea, thanks. > >> >> Or SDL app could always pause when it loses focus... >> > > This is good for video updates but sometimes not good for sound or AI > code in games. Of course when the device is really inactive (whatever > that means exactly) sound and other stuff should be stopped too. > HW independent idea : a timer that pauses the game when user has not pushed button/screen for x seconds. Not very good for chess or civilization but very good for a gauntlet clone. > Frantisek > > > ___ > maemo-developers mailing list > maemo-developers@maemo.org > https://maemo.org/mailman/listinfo/maemo-developers > // Tapani ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Libbattery.so can I find the src?
Hello, I'm actually working on the Nokia N770 but I have a problem, i don't find information about battery information access. Can you help me t osolve my problem please? thanks ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Re: binary kernel module packages
On 14/12/06, Miko Nieminen <[EMAIL PROTECTED]> wrote: I looked make-kpkg, but it really doesn't provide any ways to do this and I didn't find any other way either. In Debian Etch they have been thinking something related to this, but I was able to find only one article: http://swik.net/Debian/Planet+Debian/Daniel+Baumann:+Kernel+Modules +Packaging/q089 To correct my self, actually that article doesn't deal this particular issue, but instead out-of-tree module case, which is quite different than this one. I really wouldn't like to build whole kernel and tell people to flash that image, but instead I would like to build just that one module and create debian package which can be easily installed to product. -- Miko Nieminen [EMAIL PROTECTED] ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] [PATCH] hildon-window.c Rev 8761
Hi,
just found a bug in hildon-window.c. This patch fix it and should
speed Maemo up a bit since hildon_window_is_topmost_notify is called
way too many times:
Index: hildon-window.c
===
--- hildon-window.c (Revision 8761)
+++ hildon-window.c (Arbeitskopie)
@@ -777,7 +777,7 @@
hildon_window_update_title (window);
}
-else if (strcmp (param->name, "is-topmost"))
+else if (strcmp (param->name, "is-topmost") == 0)
{
hildon_window_is_topmost_notify (window);
}
Best Regards,
:M:
--
Michael 'Mickey' Lauer | IT-Freelancer | http://www.vanille-media.de
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] [PATCH] hildon-window.c Rev 8761
On Thu, Dec 14, 2006, Michael 'Mickey' Lauer wrote:
> Index: hildon-window.c
> ===
> --- hildon-window.c (Revision 8761)
> +++ hildon-window.c (Arbeitskopie)
> @@ -777,7 +777,7 @@
>
> hildon_window_update_title (window);
> }
> -else if (strcmp (param->name, "is-topmost"))
> +else if (strcmp (param->name, "is-topmost") == 0)
> {
> hildon_window_is_topmost_notify (window);
> }
Thanks, good catch!
___
maemo-developers mailing list
maemo-developers@maemo.org
https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Unreliable Large Network Transfers
Hi Folks, I posted an earlier version of this comment on maemo-users a few days ago and got one confirmation from another person experiencing similar behavior, but no useful advice (they simply stopped using the network for transfers)... so I thought I'd try again here. I'm finding that large (>200MB) transfers of data via the wifi network are extremely unreliable. They start out running at a reasonable speed (350KB/sec-600KB/sec), but within a few moments slow to less than 100KB/sec. The rates become very erratic, and the device GUI becomes very unresponsive. I've reproduced the problem in a variety of scenarios: - unison over SSH with a variety of connection settings - wget from a local webserver - using the bundled webbrowser from a local webserver - All of the above while connected to my wrt54gc access point at home on which I'm the only user, have strong signal levels, and no history of interference problems. - All of the above on whatever enterprise level access points are used in the Cornell University wireless infrastructure. Again, strong signals, familiar locations, no history of interference. - All of the above in situations in which other wireless clients are able run the same download at high-speed without mishap. Does anyone have advice about how I could further troubleshoot or isolate this issue? Is anyone pushing substantial amounts of data over the network without these problems? Thanks in advance for any advice, Mike ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] How to play a WAV from command line in 770?
I am trying to play a .WAV file from the Nokia 770 command line, without triggering a GUI audio player. In principle, this seems like the simplest thing in the world. Normally, I'd just use "aplay" and that would be it. However, although the Nokia 770 has alsa, it does not have aplay. So I went to install aplay. It's part of the alsa-utils package, and installing alsa-utils on the Nokia 770 is even discussed somewhat on this page: http://maemo.org/maemowiki/EnablingGstreamerSupport So I thought it would be simple to install alsa-utils. However, using the ARM build, I get this error message: dpkg: error processing alsa-utils_1.0.8-4_arm.deb (--install): package architecture (arm) does not match system (armel) Errors were encountered while processing: alsa-utils_1.0.8-4_arm.deb Looking around, I gather that the Nokia 770 (at least the 2006 edition) uses the "armel" architecture, which is distinct from the "arm" architecture listed on the Debian stable download options. I looked around for "armel" in the testing and unstable branches of Debian, and using google, but found nothing informative that way. Question 1: Is there a way to get alsa-utils working on the Nokia 770, 2006 operating system? Question 2: Is there any other way to play a .WAV file from the Nokia 770 command line? I suppose it might be possible to write a driver, or tap into the alsa, esd or gstreamer libraries in some fashion. I don't have experience doing this, but am willing to learn if there is something possible along these lines. But it seems rather excessive, as playing a .WAV file is about as simple as it gets, and it would be surprising if there is no more direct way to achieve this goal. --- Terence [EMAIL PROTECTED] ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Unreliable Large Network Transfers
I don't have any advice for you...but I do want to say proprietary wireless drivers suck, and this is a very real example of why. Shame on Conexant for not working with the Prism54 guys, and shame on Nokia for using proprietary drivers. It sounds like the driver needs fixed, and no one can do that except for Conexant or Nokia. /Andrew On Thu, 2006-12-14 at 19:16 -0500, Mike Lococo wrote: > Hi Folks, > > I posted an earlier version of this comment on maemo-users a few days > ago and got one confirmation from another person experiencing similar > behavior, but no useful advice (they simply stopped using the network > for transfers)... so I thought I'd try again here. > > I'm finding that large (>200MB) transfers of data via the wifi network > are extremely unreliable. They start out running at a reasonable speed > (350KB/sec-600KB/sec), but within a few moments slow to less than > 100KB/sec. The rates become very erratic, and the device GUI becomes > very unresponsive. > >I've reproduced the problem in a variety of scenarios: > > - unison over SSH with a variety of connection settings > - wget from a local webserver > - using the bundled webbrowser from a local webserver > - All of the above while connected to my wrt54gc access point at home > on which I'm the only user, have strong signal levels, and no > history of interference problems. > - All of the above on whatever enterprise level access points are > used in the Cornell University wireless infrastructure. Again, > strong signals, familiar locations, no history of interference. > - All of the above in situations in which other wireless clients are > able run the same download at high-speed without mishap. > > Does anyone have advice about how I could further troubleshoot or > isolate this issue? Is anyone pushing substantial amounts of data over > the network without these problems? > > Thanks in advance for any advice, > Mike > ___ > maemo-developers mailing list > maemo-developers@maemo.org > https://maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Re: How to play a WAV from command line in 770?
[EMAIL PROTECTED] wrote: I am trying to play a .WAV file from the Nokia 770 command line, without triggering a GUI audio player. In principle, this seems like the simplest thing in the world. Normally, I'd just use "aplay" and that would be it. However, although the Nokia 770 has alsa, it does not have aplay. So I went to install aplay. It's part of the alsa-utils package, and installing alsa-utils on the Nokia 770 is even discussed somewhat on this page: http://maemo.org/maemowiki/EnablingGstreamerSupport So I thought it would be simple to install alsa-utils. However, using the ARM build, I get this error message: dpkg: error processing alsa-utils_1.0.8-4_arm.deb (--install): package architecture (arm) does not match system (armel) Errors were encountered while processing: alsa-utils_1.0.8-4_arm.deb Looking around, I gather that the Nokia 770 (at least the 2006 edition) uses the "armel" architecture, which is distinct from the "arm" architecture listed on the Debian stable download options. I looked around for "armel" in the testing and unstable branches of Debian, and using google, but found nothing informative that way. Question 1: Is there a way to get alsa-utils working on the Nokia 770, 2006 operating system? Question 2: Is there any other way to play a .WAV file from the Nokia 770 command line? I suppose it might be possible to write a driver, or tap into the alsa, esd or gstreamer libraries in some fashion. I don't have experience doing this, but am willing to learn if there is something possible along these lines. But it seems rather excessive, as playing a .WAV file is about as simple as it gets, and it would be surprising if there is no more direct way to achieve this goal. --- Terence [EMAIL PROTECTED] Answer 2: mplayer would be my guess ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Unreliable Large Network Transfers
Mike Lococo wrote: I'm finding that large (>200MB) transfers of data via the wifi network are extremely unreliable. They start out running at a reasonable speed (350KB/sec-600KB/sec), but within a few moments slow to less than 100KB/sec. The rates become very erratic, and the device GUI becomes very unresponsive. Are you sure network is a problem? Are you writing data somewhere? Both MMC card and iternal flash are really slow when writing. I had similar problem when writing to MMC card. First it is fast because data is buffered in RAM but then RAM is filled and as you say 'GUI becomes very unresponsive'. You can use 'top' in osso-xterrm to see cpu usage. If it is mmcqd of something like that then it is MMC writing. Enabling multiblock writes helps (a bit experimental feature). Only when multiblock writes in MMC driver are enabled then wi-fi driver really becomes a bottleneck. It theory it should be the fastest way how to get data into the device (g wlan does normally > 2MB/s speeds) but sadly only ~600kb/s is reality with N770 and current driver. I wonder where exactly the bottleneck wih wi-fi is (hardware of software). Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
