Re: [maemo-developers] docpurge in maemo 2.1
On Wed, 2006-12-13 at 14:33 +0200, ext Marius Vollmer wrote: ext Miko Nieminen [EMAIL PROTECTED] writes: - Why is docpurge executed when installing packages in scratchbox environment in the first place? You don't really need (or want) to remove documentation there. I agree it is not needed, but osso-ai metapackage depends on it and that is the reason why it's in there, I suppose. Actually I think it's wrong that osso-ai depends on docpurge, maybe it should rather suggest or recommend it? osso-ai is a meta package that should only be used when creating product flash images. It should not be in the SDK. Thanks guys, osso-ai and docpurge will be removed out of rootstrap in the next release. Cheers, Hoang ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Re: [maemo-users] 770 on the way
Hi again, Have you tried disabling the Flash plugin (and restarting Browser)? No, its not only flash related - although you're right flash seems to make crashes more frequently. e.g. today I tried to access gamil twice - soon after logging in opera crashed. I fired up minimo and everything worked fine. Some of the Flash content on the web is not really ... well ... No thats not how the rules are. Bad content may not crash applications, especially if you can't trust the guy how created the content. If a flash file is broken it may not be loaded, not crash the browser. And all the other crashes that happen from time to time, imagine your mobile would crash that often... lg Clemens - Eero PS. It's enlightening to run top when browsing the net with and without Flash enabled... ___ maemo-users mailing list maemo-users@maemo.org https://maemo.org/mailman/listinfo/maemo-users ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Unreliable Large Network Transfers
Not had any problem with the network as we don't transfer big files. I think Frantisek might be on to something. We defiantly had the problem writing files to the MMC and they don't even have to be big. If you attempt to write data at a significantly faster speed than the MMC can actually do, then it just fills up the buffer, so if you carry on for a while it looks like it uses all the available memory (slowing you down), then in our case the program writing the file slowed down and things reached an equilibrium somewhere around the point of not really being usable. (we were testing a low level driver logging everything to a file). If you want to prove (although perhaps not conclusively) it is a network issue then find some way of transferring the same files but don't store them anywhere (e.g. pipe to /dev/null) so it never hits the MMC bottleneck, or perhaps put a 250MB file on an MMC and send it the other way (although presumably this will be the speed ot the MMC bottleneck from the beginning but see if it gets worse). Shame the drivers are not open source as the others have said, because if you do 'prove' it is the wireless driver there is not a lot that can be done. If it is an MMC bottleneck then perhaps best to find a way to drop the transfer speed down to that of the MMC bottleneck so your device doesn't slow down (also try faster MMC cards with the fast drivers, although I'm not sure they are stable yet). Regards Simon At 07:57 15/12/2006, Frantisek Dufka wrote: 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 -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.409 / Virus Database: 268.15.19/587 - Release Date: 14/12/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.409 / Virus Database: 268.15.19/587 - Release Date: 14/12/2006 ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] API changes from Maemo 2.1 (Scirocco) to 3.0 (Bora), and Herring
Hi, As promised, here is an overview of the API changes made from Maemo 2.1 (Scirocco) to 3.0 (Bora): http://maemo.org/maemowiki/ApiChangesSciroccoBoraHerring Many of them can already be found in Herring. In fact, you can use Herring to get a good approximation of how your app will port to Maemo 3.0 Bora. Please note that this is still a draft and incomplete. We are still collecting and verifying this information. Br, Carlos ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Re: [maemo-users] 770 on the way
Hi, Some of the Flash content on the web is not really ... well ... No thats not how the rules are. Bad content may not crash applications, especially if you can't trust the guy how created the content. If a flash file is broken it may not be loaded, not crash the browser. What I meant is that some Flash content may happily (try to) consume 100MBs of RAM. I guess Flash and Opera deal with running out of memory OK, but Gtk (with which the application UIs are done with) most definately does not. For Gtk, the Glib allocations abort the process if Glib allocation fails[1] (and even if Glib alloc functions would be changed to return NULL when alloc fails instead of aborting, Gtk widgets don't have additional code to handle this gracefully[2]). [1] Mentioned e.g. in my ancient Gtk study: http://www.movial.fi/client-data/file/movial_gtk1.pdf [2] By e.g. showing only half of the UI? :-) - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] How to play a WAV from command line in 770?
(Sorry for the broken name; Exchange has a habit of furiously breaking our mail.) On Thu, Dec 14, 2006 at 07:39:28PM -0500, ext [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? Hi, It's just a rebuild in Scratchbox. You can't use pre-compiled packages from Debian, until Debian catches up with EABI, which we're already working to fix. ITMT, you'll need to rebuild any external packages. 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 play a WAV from command line in 770?
Hello! There is gstreamer on the device but no command-line gstreamer utilities like gst-launch, which you can compile (using scratchbox) and install yourself if you like. Playing a wav file should be as simple as: `gst-launch-0.10 filesrc location=whatever.wav ! wavparse ! dsppcmsink` IIRC, wavparse is installed on the device but in case it's not, you can get it compiled from the source (gst-plugins-good). On 12/15/06, [EMAIL PROTECTED] [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] ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers -- Regards, Zeeshan Ali Design Engineer, SW Open Source Software Operations Nokia Multimedia ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] python + osso_browser does work.
On 12-Dec-2006, at 17:15 , Osvaldo Santana wrote: Would it be possible to package readline.so separately so that Python developers can apt-get install python-readline, while regular users can save half a meg? It's possible to make another package with the readline.so module, but the Python interactive mode will not use it. Why is this? This isn't a problem on other platforms. For instance, on the Mac readline used to be a separate distribution because of licensing issues. -- Jack Jansen, [EMAIL PROTECTED], http://www.cwi.nl/~jack If I can't dance I don't want to be part of your revolution -- Emma Goldman smime.p7s Description: S/MIME cryptographic signature ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] root image scripts appear to be unavailable
The root image scripts that are referenced by the Using the flasher utility and creating the referencfe root file system how-to no longer appear to be available. According to this Web page, they can be retrieved at https://stage.maemo.org/svn/integration/trunk/rootimagescripts/ , but this link does not work at the moment. I also looked for the scripts in the maemo SVN tree but didn't locate them there as well. Thanks, Aaron ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Create a FIASCO image?
Using flasher --unpack, it is possible to unpack a FIASCO image. However, how does one go about creating a new FIASCO image that can be used with the Windows Software Update Wizard? I can certainly flash a new rootfs using flasher, but there are legitimate reasons why it might be necessary to provide a complete FIASCO image to clients with a custom rootfs. There is some information about FIASCO images at http://maemo.org/maemowiki/HardWayToBecomeRoot . This page provides source code for extracting the components of a FIASCO image and reassembling them later, but these instructions are quite old, and I'm not sure if they will continue to work with the latest images. Official support from Nokia for creating, not just unpacking, FIASCO images would be helpful. Thanks, Aaron ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] How to play a WAV from command line in 770?
2006/12/15, Zeeshan Ali [EMAIL PROTECTED]: Hello! There is gstreamer on the device but no command-line gstreamer utilities like gst-launch, which you can compile (using scratchbox) and install yourself if you like. Or just install the gstreamer0.10-tools debs from repository.maemo.org: http://repository.maemo.org/pool/maemo2.1/free/g/gstreamer0.10/ -- Kalle Vahlman, [EMAIL PROTECTED] Powered by http://movial.fi Interesting stuff at http://syslog.movial.fi ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] Unreliable Large Network Transfers
Hi Folks, I'm finding that large (200MB) transfers of data via the wifi network are extremely unreliable. Are you sure network is a problem? Are you writing data somewhere? Both MMC card and iternal flash are really slow when writing. This is the issue. I can reproduce both the slow write speed (~150KB/s) and the GUI unresponsiveness with (from memory, please forgive any typos): dd if=/dev/zero of=/media/mmc1/test.file bs=1M count=250 which doesn't involve the network at all. I may do some playing with multiblock write kernels at this point, although it's not so much the (average) speed that's the problem. I think the real issue is that the CPU doesn't seem to be able to service requests from other subsystems in a timely manner once the write cache fills up. Userspace programs are getting regularly starved for CPU time for several seconds at a time, which causes the wildly fluctuating transfer rates, the unresponsive GUI, the Unison sessions dropping, and possibly the reboots (as programs aren't responding to the watchdog promptly?). The Unison failures, in particular, are disappointing. It is such an awesome program for syncing the 770 to a desktop system, but if you have a large MMC (and you change its contents regularly) it isn't usable at all. Thanks, Mike ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
