Re: [maemo-developers] problem with dspmp3sink (was: problem with gstreamer and dsppcm)
On Monday 21 August 2006 18:34, Charles 'Buck' Krasic wrote: > Just in case you have not done it already, enabling swap in your device > can help a lot to prevent out-of-memory errors.Maybe this will help > with mplayer/gstreamer stability. > > I personally suspect a design flaw in the current Linux VM subsystem. > I've observed that if an application allocates memory rapidly, the > kernel may fail to reclaim pages quickly enough from the page and buffer > caches (they are only caches after all), so it actually denies the > allocation request. For example, with zero swap, on a machine with > 1G of ram, and >500M of it pseudo-free (used by caches), I've seen > moderate allocations fail--like when starting an application like > firefox.Enabling even a small amount of swap seems to dramatically > change this behaviour. Thanks for the information, this is interesting. I tried swap a long time ago on IT2005, that was done in order to make gcc work on Nokia 770 to try compiling something before I installed scratchbox :) Anyway, I did not like the stability as gcc started to fail with internal compiler errors. So I decided not to use swap as long as it is enough memory for what I need. Also there was some swap related report about the problem with mplayer: http://www.internettablettalk.com/forums/showpost.php?p=20068&postcount=96 But maybe I should give swap another try on IT2006 and see if it helps to improve stability. By the way, I already asked this question in the mailing list long time ago, but are there any tools for hardware diagnostics on Nokia 770? Something like memtest86 could probably be very useful. Though availablility of hardware diagnostics tools could probably result in more devices getting returned for replacement with otherwise undetected problems and have negative impact on Nokia profit (just joking). ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] automatic byte order check
On Monday 21 August 2006 10:45, Detlef Schmicker wrote: > I had a look at the vncviewer and saw, that it is working in the sandbox > in connection with vino (gnome vnc server). On the device the CoRRE > encoding does not work. > > Probably it is a byte order problem. The code has a lot of byte order > (e.g. GUINT16_TO_BE). Is there a way to automaticaly warn critical > points at compilation? Are there any tools? I'm not completely sure if understood your post correctly, but cpu used in Nokia 770 is little endian (the same as x86). So it is unlikely to have byte order or endian problems here. But ARM is alignment sensitive, so you may have problems because of bad alighment, I started making a page on wiki describing this issue (still very incomplete): http://maemo.org/maemowiki/PortingFromX86ToARM I also tried to search for tools that could identify alignment problems automatically, but did not find anything useful. Probably the most easy way to make such tool is to modify valgrind to track alignment for each memory access operation. But don't know, I ended up finding and fixing such problems in my code manually without the help of any tools :) ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] custom rootfs creating problems
Hi This part is solved: After this modifications I was able to continue with downloading and building rootfs. This error message is found after downloading all packages: Setting up passwd & groups /home/ondrej/rootfs/rootimagescripts/make_rootimage.sh: line 271: /usr/sbin/update-passwd: cannot execute binary file update-passwd is a ARM executable and I don't have ARM emulation, because /proc/sys/fs/binfmt_misc directory doesn't exists. I'm mount binfmt to another direcotory and register helpers. -- Ondrej Ivanic ([EMAIL PROTECTED]) ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Error with gtk_text_buffer_insert_at_cursor () for unicode string
Title: Error with gtk_text_buffer_insert_at_cursor () for unicode string I wrote from home, but the message never appeared... Well, here we go again: I bought nokia 770 and the bluetooth keyboard, but my mother language is portuguese and I wasn´t capable to activate deadkeys for the funny chars ã, ç, ê and so on (xmodmap doesn´t work for that, no xorg.conf, etc). So I hacked maemopad 1.5 to enforce accents. With maemopad I developed my own GTK text editor for prototype, and after the buffer receive "^" and then an "A" char the program is supposed to write "Â" in the screen. My prototype running x86 Linux GTK works fine for gtk_text_buffer_insert_at_cursor (buffer, "\u00E2", -1), but when I try this for my gtk_signal for "key_press_event" in maemopad nothing happens. Nokia 770 displays funny chars, in fact the screen keyboard has dead keys for portuguese, but the same is not true for Bluetooth keyboard. The only and last problem for my Maemopad hack for accents with bluetooth keyboards is this single line: gtk_text_buffer_insert_at_cursor (buffer, "\u00E2", -1); If you try ASCII char, it works! gtk_text_buffer_insert_at_cursor (buffer, "a", -1); And for my x86 Linux GTK prototype unicode works too! Some idea? Alessandro Essa mensagem é destinada exclusivamente ao seu destinatário e pode conter informações confidenciais, protegidas por sigilo profissional ou cuja divulgação seja proibida por lei. O uso não autorizado de tais informações é proibido e está sujeito às penalidades cabíveis.This message is intended exclusively for its addressee and may contain information that is confidential and protected by a professional privilege or whose disclosure is prohibited by law. Unauthorized use of such information is prohibited and subject to applicable penalties. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] custom rootfs creating problems
Hi I was tried to build rootfs according to the howto at the maemo website [1]. Files (rootfs.packages and sources.list, rev 4) from subversion repository are out of date. I was changed repositories in sources.list to maemo 2.0 repositories: deb http://repository.maemo.org/ maemo2.0 free non-free deb-src http://repository.maemo.org/ maemo2.0 free I was made many changes in rootfs.packages files. Here is a diff --- rootfs/rootfs.packages 2006-08-23 19:16:23.0 +0200 +++ /scratchbox/users/ondrej/home/ondrej/rootfs/rootfs/rootfs.packages 2006-08-23 19:10:58.0 +0200 @@ -8,11 +8,8 @@ bme-dbus-proxy busybox certs -codelockui -codelockui-l10n-3.0-engb -dbus-1 +dbus dbus-1-utils -dbus-glib-1 debconf debconf-english defoma @@ -23,36 +20,30 @@ dsme fakeroot-net fontconfig -gcc-3.3-base +gcc-3.4-base gconf2 gdb gtk2-engines-sapwood hildon-base-lib0 hildon-control-panel -hildon-control-panel-l10n-4.0-engb -hildon-fm-l10n-3.0-engb +hildon-control-panel-l10n-engb +hildon-fm-l10n-engb hildon-fm1 hildon-initscripts -hildon-input-method -hildon-input-method-framework -hildon-input-method-l10n-3.1-engb -hildon-input-method-ui -hildon-input-method-widgets-l10n-3.1-engb -hildon-input-method-widgets0 -hildon-lgpl-l10n-3.0-engb +hildon-input-method-sdk +hildon-input-method-framework-sdk +hildon-input-method-l10n-engb +hildon-input-method-widgets-sdk0 hildon-lgpl0 -hildon-libs-l10n-3.0-engb +hildon-libs-l10n-engb hildon-libs0 hildon-status-bar-battery -hildon-status-bar-battery-l10n-3.0-engb +hildon-status-bar-battery-l10n-engb hildon-status-bar-display -hildon-status-bar-display-l10n-3.0-engb +hildon-status-bar-display-l10n-engb hildon-status-bar-lib0 initscripts iptables -kdbusd -ke-recv -ke-recv-l10n-3.0-engb klogd lessertunjo0 libatk1.0-0 @@ -76,28 +67,17 @@ libgtk2.0-common libgwobex0 libice6 -libimengines0 +libimengines-sdk0 libimlayouts0 libipt-idletimer -libiw27 libjpeg62 libmatchbox1 libncurses5 -libogs0 -libopenobex-1.0-0 +libopenobex1 libosso-certman1 -libosso-common-error-l10n-3.0-engb +libosso-common-error-l10n-engb libosso-common-error0 libosso-dbus-conf -libosso-email-al -libosso-email-cl -libosso-email-common -libosso-email-dbusutils -libosso-email-imap -libosso-email-interface -libosso-email-pop -libosso-email-smime -libosso-email-smtp libosso-filemanager-interface libosso-gnomevfs2-0 libosso-gnomevfs2-common @@ -115,7 +95,6 @@ libsm6 libsqlite0 libssl0.9.7 -libstdc++5 libtiff4 libvte-common libvte4 @@ -137,7 +116,7 @@ libxtst6 lsof maemo-af-desktop -maemo-af-desktop-l10n-4.1-engb +maemo-af-desktop-l10n-engb makedev matchbox-window-manager mawk @@ -150,25 +129,22 @@ osso-af-startup osso-af-utils osso-app-killer -osso-applet-certman-l10n-4.0-engb +osso-applet-certman-l10n-engb osso-applet-display -osso-applet-display-l10n-3.0-engb +osso-applet-display-l10n-engb osso-application-installer -osso-application-installer-l10n-4.0-engb +osso-application-installer-l10n-engb osso-backup -osso-backup-l10n-3.2-engb +osso-backup-l10n-engb osso-bttools osso-connectivity-ui-conndlgs osso-connectivity-ui-connmgr -osso-connectivity-ui-gwdialogs osso-connectivity-ui-gwwizard osso-connectivity-ui-iapsettings -osso-connectivity-ui-l10n-4.0-engb +osso-connectivity-ui-l10n-engb osso-connectivity-ui-statusbar osso-core-config osso-dsm -osso-email-engine -osso-email-l10n-4.0-engb osso-esd osso-gnomevfs-extra osso-gwconnect @@ -181,18 +157,8 @@ osso-screenshot-tool osso-sounds-ui osso-systemui -osso-systemui-actingdead -osso-systemui-actingdead-l10n-3.0-engb osso-systemui-conf -osso-systemui-devlock -osso-systemui-devlock-l10n-3.0-engb -osso-systemui-modechange -osso-systemui-modechange-l10n-3.0-engb -osso-systemui-powerkeymenu -osso-systemui-powerkeymenu-l10n-3.0-engb osso-systemui-splashscreen -osso-systemui-tklock -osso-systemui-tklock-l10n-3.0-engb osso-thumbnail osso-thumbnail0 osso-update-category-database After this modifications I was able to continue with downloading and building rootfs. This error message is found after downloading all packages: Setting up passwd & groups /home/ondrej/rootfs/rootimagescripts/make_rootimage.sh: line 271: /usr/sbin/update-passwd: cannot execute binary file I'm running on Gentoo AMD64 (64bit profile). [1] http://www.maemo.org/platform/docs/howtos/howto_use_flasher_rootfs.html ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Future features for Maemo?
Ola, Here is *my* top 10...there is every chance that some/all of these are implemented/thought about already and I just haven't discovered them yet but like you say we are shooting for the stars,no . 1.Everything that is visible on the screen should pertain to the task at hand...desktop icons,nokia images etc etc need to go 2. I want working virtual desktops. 3. I want to be able to project the 770 screen ...s-video out? 4. I want a hardware button called copy and another one paste 5. I want good diagnostic tools...when i can't get a wireless network connection I want to know why 6. Add a download manager - for example gwget2 - by default 7. I want the UI in Portuguese as well as English 8. I want a user-friendly,P2P-social-tagging-capable wiki embedded into the OS. It is not only the basic Wiki features, but also the collaborative features, social tagging and the ability to see the Wiki in a hastily formed network thats important. This would allow Nokia to focus some 770 marketing on small groups (children, teaching, family, friends etc) and the need for collaboration on their activities. Sort of like a collaborative tomboy http://www.beatniksoftware.com/tomboy/ based on tribe.net 9. Most 'social software' is just a web service where people write or publish for other peopletheir diary, their images, their boomarks etc. Other people watch it, use it, or read it. Actually meeting some of these peopletalking/collaborating with them on the Web would be something I would call 'social'...sort of like meeting in a bar or something. Building something like Web Mobs (http://www.webmobs.de) into the 770 would be (i think),cool. It shows real people on Web pages. (from what i can make out this is just a concept and not (yet) a technological implementation you could use) 10. Where is that microphone hidden on the 770 again? []'s Ian -- .''`. : :' : `. `'` `- Orgulhoso ser MetaRecicleiro http://manaus.metareciclagem.org/ ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Maemo alarms ==> retutime
Hi, Devesh Kothari wrote: > - currently it is in legal check for approval to open. Once that is > done, the project would most probably move to garage > - I am hoping as soon that happens, it possibly appear in sardine that's great news! I guess there are quite some people here looking forward to it :-) Greetings Florian -- The dream of yesterday Florian Boor is the hope of todayTel: +49 271-771091-14 and the reality of tomorrow.Fax: +49 271-771091-19 [Robert Hutchings Goddard, 1904][EMAIL PROTECTED] 1D78 2D4D 6C53 1CA4 5588 D07B A8E7 940C 25B7 9A76 ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Maemo alarms ==> retutime
ext Igor Stoppa wrote: > On Mon, 2006-07-31 at 10:34 -0400, ext Michael P. Lococo wrote: > > I think what Chris, me and others are really looking for is the > alarm > > framework for application notification, not the mere RTC alarm. > > >>> > > >>> There is no alarm framework > > >> > > >> I would have expected such framework after the longish discussions on > > >> the mailinglist some time ago (effectively more than half a year > ago). > > > > > > Since there isn't any calendar application in the 2006 software > edition, > > > management didn't really prioritise a sane alarm interface. > > > > There is is substantial user demand, though, and there are three > different > > community-based or third-party calendaring applications that are all > > hamstrung by the lack of an alarm facility. It seems fairly clear > at this > > point that: > > > > 1) The need for an alarm framework is not a passing fancy. > > 2) In order to be done sanely, it must be centralized... either as a > > single community project or as a Nokia supported part of the product. > > Applications cannot reasonably be expected to handle it without tripping > > over each other and killing battery life with polling. > > > > Mike > > I think Devesh is the proper interface for this sort of discussion, > since he takes care of harmonizing this sort of internal/external > needs/demands/activities. > > And he's your best chance to get any statement ;-) > Ok, the status - based on mailing list discussion about alarm requirements, it was pushed as a requirement to be delivered. It is accepted and, as i understand implemented (framework etal). What was also at design time agreed that the alarm framework/alarmd could be installed standalone and compatible to IT OS 2006 (so it is not tied with future product release) - currently it is in legal check for approval to open. Once that is done, the project would most probably move to garage - I am hoping as soon that happens, it possibly appear in sardine Best Regards Devesh > -- > Cheers, >Igor > > Igor Stoppa (Nokia M - OSSO / Tampere) > ___ > 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