Re: [maemo-developers] [maemo-users] TuxPaint for Nokia 770 2006 edition, released
Thank you, I will try your solution ASAP. Best Regards 2006/8/14, Eero Tamminen <[EMAIL PROTECTED]>: Hi, > When the user press the hardware Home button, TuxPaint continues to run > in the background and the user must kill it through a terminal , if you know > how to solve this, please let me know. Alessandro Pasotti w3: www.itopen.it ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Re: daemon fails at boot but starts from xterm
Guess I'm too stupid to live. Right after I sent this I found out that I asked - and answered - this same question almost two weeks ago :-( Brad. On 8/14/06, Brad Burleson <[EMAIL PROTECTED]> wrote: Ok, I'm sure I've seen some discussion on this before, but I've been working on this daemon and my current problem is that it's failing to start from 'postinst' and at boot. The install log seems fine, but the process doesn't start. I rebooted to see if it would start then, but it doesn't. I can start it no problem as root with "invoke-rc.d diaperd start" from the xterm and it works fine. This program listens to dbus messages and does have a 'diaperd.service' file installed. What did I miss? Thanks, Brad. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] daemon fails at boot but starts from xterm
Ok, I'm sure I've seen some discussion on this before, but I've been working on this daemon and my current problem is that it's failing to start from 'postinst' and at boot. The install log seems fine, but the process doesn't start. I rebooted to see if it would start then, but it doesn't. I can start it no problem as root with "invoke-rc.d diaperd start" from the xterm and it works fine. This program listens to dbus messages and does have a 'diaperd.service' file installed. What did I miss? Thanks, Brad. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] initfs with onscreen boot menu updated
Hello, I have updated initfs hack with onscreen boot menu http://fanoush.webpark.cz/maemo/#initfs Now I think it is pretty usable. changes: - allow also modules and fsoptions per each custom menu item - moved custom items from linuxrc to bootmenu.sh to minimize linuxrc modifications - default root device (set via flasher or cal-tool -R) is preselected in menu - custom menu items can now boot correctly without showing menu when set as default root device - added noatime to mmc, partition 2 item (menu id is mmc2 now) - holding ESC on boot skips executing bootmenu.sh (and boots from flash if default root device is custom and unknown to linuxrc), useful only if modified bootmenu.sh does not boot - show 'booting from xxx ...' when booting without using menu (if bootmenu.sh is not skipped) - evkey.c included Frantisek ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] xmlrpc-c strange error.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Beth wrote: > And better, do you know a xmlrpc library that is tested and works > under maemo/hildon/arm...? I have successfully used xmlrpc-c with maemo/mistral in maemo-blog[1]. I can't really tell what is the problem with your setup though; but xmlrpc-c can be used on maemo 2.0 and nokia 770. The sources[2] for maemo-blog are available too. The deb packages I made and used are in maemo-hackers repository[3]. [1]: http://maemo-hackers.org/wiki/MaemoBlog [2]: http://maemo-hackers.org/browser/maemo-blog [3]: http://maemo-hackers.org/apt/pool/main/x/xmlrpc-c/ - -- Santtu Lakkala -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFE4JGSX9Rc0+po4p0RAsiwAJ4o1450xHF7Yw6IbQAvMTJiLh5ACACgpaXd cyP7bz8xGwFq9CI4pT0XxQc= =FTwc -END PGP SIGNATURE- ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] 770 stopped booting
Hi, > So I /really/ wonder how anything could distort the boot process that > hard? I presume if I were a normal customer, this would be the point > to return the unit as defective :-/ You mentioned that the battery should have been charged enough. The other common reason for a boot-looping is full Flash. The device doesn't boot up properly if Flash is 100% full as bootup process needs to write a few bytes to the Flash also. The builtin software should handle this properly (I hope :)), but later installed software might not. Things that software should handle: - Check whether any file write operations fail because there was no space *AND* inform user about that so that he can do something about that - Remove any extra and partially written files when device run out of space - Not write any files when applications start A lot of software is not very good at this nor in handling memory shortages nowadays. They assume that there's "infinite" amount of memory and disk. AFAIK there's some protection in the device about normal user filling the Flash, but root can still fill the Flash 100%. I.e. worst possible thing in the device is a process run as root which can generate largish log files without severaly constraining their sizes... - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] [maemo-users] TuxPaint for Nokia 770 2006 edition, released
Hi, > When the user press the hardware Home button, TuxPaint continues to run > in the background and the user must kill it through a terminal with > killall -9 tuxpaint > or reset the device. > I've tried unsuccessfully differente approachs (libosso), if you know > how to solve this, please let me know. Below is copy of my earlier mail to the devel list. (I think the info is also in Maemo wiki somewere) It tells how to get back to the application. - Eero I spent a while debugging why I cannot switch back to SDL window from which I've switched away, and noticed that it's actually easy to fix. Application switcher needs to know which window matches to which .desktop file. This is done using the standard WM_CLASS X property. So, e.g. to be able to switch back to the Bomberman game, you need to... Add following line to Bomberman .desktop file for application switcher: StartupWMClass=Bomberman And ask SDL to use that WM_CLASS definition for the Bomberman game window through an environment variable by adding following line to the "launch-bomberman" script: export SDL_VIDEO_X11_WMCLASS=Bomberman I.e. only two lines need to be added and no actual code needs to be changed! ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
Re: [maemo-developers] custom gstreamer plugins
Hi, > Now, ldd must be available on the N770, of course :) ldd is just a script around the dynamic linker, so not having it is not a great trouble. Just use the dynamic linker directly: /lib/ld-2.3.6.so --list /usr/lib/libosso.so.1.3.0 (Note that you need to give the full path to the library or binary you want to inspect!) - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Reboot Cycle
Hi, > Well, it was inevitable, I got myself into a reboot cycle. Using the > no-lifeguard-reset flag seems to bring the system back to a very stable > state, though, so I'm wondering if there's a list of programs that > should be running that the lifeguard will watch for so I can debug what > exactly is failing? The watchdog process is "dsme". If you check it's PID with ps (here 828), you can list which process have it as a parent with something like this: watchdog=828; for i in /proc/[1-9]*; do p=$(grep PPid $i/status|cut -d: -f2); if [ $p -eq $watchdog ]; then cat $i/cmdline; echo; fi; done Because of maemo laucher, I use /proc/PID/cmdline for outputting the watchdogged command name (maemo-launched binaries have the launcher as the process name, 'cmdline' tells which "program" is being "launched"). - Eero ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Laika 2.1 released..
Hi, The maemo2.0 supporting version of Laika Eclipse plugin has been released. The packages are available in http://kooditakomo.cs.tut.fi/projects/laika/ The glade-support has been stripped and gazpacho support is still under way..-Mikko-- If you're too weak of mind to realize the source of your pain you deserve every single bit of it. ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
[maemo-developers] Re: [maemo-users] Streamtuner build 5 available with SHOUTcast support
Olivier ROLAND a écrit : For end users : Try it : https://garage.maemo.org/projects/streamtuner/ New features : * Add Shoutcast channel * Add Italian translation (Thanks to Fabio Viola) * Add Automatic connexion Installation instructions : (1) this version need mplayer binary for nokia770 (garage version) to be present in your Documents folder. (2) you need to remove .streamtuner directory in /home/user before (or after) installation if you have installed a previous version of streamtuner. Maybe usefull for other developers : Adding SHOUTcast support on NOKIA 770 was not easy : iconv -l result is a bit disappointing No native support in maemo libc for Window-1252 =-O So i need to recompile libiconv and i use the libc plug/override mode with LD_PRELOAD hack. That's why the binary of streamtuner is three time bigger (not because of SHOUTcast plugin) Please NOKIA Team, add Window-1252 in the next release. Enjoy and stay tuned. Olivier ROLAND. ___ maemo-users mailing list maemo-users@maemo.org https://maemo.org/mailman/listinfo/maemo-users Update : A regression was found in this release. Fix to come. DON'T USE IT or only for testing purpose. Sorry for the convenience ... Still beta ;-) ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
RE: [maemo-developers] libxv status?
>Daniel Stone wrote: >> It means that the video hardware does not support RGB565 (everything >> on the device, basically) and YUV together. You can't have part of >> the screen being RGB and part being YUV; the problem is a couple of >> layers below the X server. Yes it does and yes you can, as I wrote the support and it works pretty well... ;) >Oh, thanks. Now I understand. From the product brief >http://www.erd.epson.com/vdc/html/contents/S1D13742.htm and >from kernel sources I wrongly guessed that the conversion is >done on the fly (per each update) when moving data from main >memory to videoram. But as it is simple DMA it looks like You understood the kernel sources correctly. Just set the format flag in ioctl() for each update specifying the format for the updated window area. This functionality is independent from the source of the data (be it ARM or C55). - Jussi Laako ___ maemo-developers mailing list maemo-developers@maemo.org https://maemo.org/mailman/listinfo/maemo-developers
