Re: Who have an internal GPS application demo?
dumganhar ([EMAIL PROTECTED]) wrote: I am developing a GPS application! have found many informations about GPS with bluetooth ,but I still can't find how to use interal GPS!Could someone help me and give me a demo written by C? There is sample gps code available as well as documentation. http://maemo.org/maemo_release_documentation/maemo4.1.x/node10.html#SECTION001027000 is a good starting point. Have fun, Simon -- [EMAIL PROTECTED] http://simon.budig.de/ [EMAIL PROTECTED] http://www.kernelconcepts.de/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Memory card mmc changed status to Read only file system (30)
Hi, ext Darius Jack wrote: OS2007HE worked fine, run shell scripts, applications. Recently run wget in recursive mode. Download to flash memory. Learned how to recorsive download to media memory card (MMC). Copied downloaded html files from flash to memory card to make room on flash. And finally tried to remove wget downloaded files from media memory card and found out any, every, each file to be asterisked and can not be deleted. run mount from command line one entry for /media/mmc1 /dev/mcblk0.. on /media/mmc1 type vfat (rw, noauto, nodev, noexec, nosuid, utf8, uid=2, shortname=mixed, dmask=000) chmod -x /media/mmc1 chmod: /media/mmc1: Read-only file system I gvet used media card to save maps in maemo mapper, today nbo chance to run maemo-mapper. Please tell me how to have /media/mmc1 back read-write file system, as changed nothing exceptionally to change status of media file system. Only known reason for this is that the memory card file system has gotten corrupted. When kernel notices this[1], it remounts the file system as read-only so that user cannot corrupt it more. The file system can get corrupted if: - You disconnect the USB cable from PC without safely remove - You take the memory card out when it's reported as being in use (when you open the card cover) - You take the battery out - Device HW watchdog resets the device while the card is being written or it otherwise has data which hasn't been completely written to the card when above things are done. For example streaming flash/video, browser/package downloads, downloads to mail folder that's on memory card, map tile downloads configured to be saved on memory card etc can use memory card extensively. From XTerm you can run dosfsck -n /dev/mcblk0.. to check the file system. Repair can be done in the device from the File manager[2] (or as root with dosfsck), or from PC either using a card reader or when the device USB cable is connected (at least with Linux it's better to unmount the card from PC side before repair though). - Eero [1] Kernel notices the corruption only when some information in the file system is clearly wrong. File system consistency is not checked when the card is mounted (neither in Linux nor Windows either for removable devices). [2] With large full card consistency check / repair can take several minutes and fail because it requires more memory than is available on the device. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: PIL and camera.py
Alex, please don't fool us and don't attach any clause on privacy, confidentiality or the like in your mail as archives of the mailing list are public. (cut for clarity) ~ This message (including any attachments) is for the named addressee(s)'s use only. It may contain sensitive, confidential, private proprietary or legally privileged information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. Any use, disclosure, copying, or distribution of this message and/or any attachments is strictly prohibited. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers Send instant messages to your online friends http://uk.messenger.yahoo.com ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: How to get he WLAN MAC address?
Am Mittwoch, den 13.08.2008, 10:51 +0800 schrieb dumganhar: I will use this for registration!Thanks for helps! Settings - Control Panel - About Product andre -- Andre Klapper (maemo.org bugmaster) ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: PIL and camera.py
please don't fool us and don't attach any clause on privacy, confidentiality or the like in your mail as archives of the mailing list are public. This is most likely not Alex' fault. Some company mail servers add this kind of stuff to every outgoing mail. Martin 2008/8/13, Darius Jack [EMAIL PROTECTED]: Alex, please don't fool us and don't attach any clause on privacy, confidentiality or the like in your mail as archives of the mailing list are public. (cut for clarity) ~ This message (including any attachments) is for the named addressee(s)'s use only. It may contain sensitive, confidential, private proprietary or legally privileged information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. Any use, disclosure, copying, or distribution of this message and/or any attachments is strictly prohibited. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers Send instant messages to your online friends http://uk.messenger.yahoo.com ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: PIL and camera.py
Hi,
I am looking for original camera.py but I can't find it... could
somebody provide a link for it?
Thanks nad best regards,
2008/8/13 Alex T. W. LEUNG [EMAIL PROTECTED]:
Hi maemo developers,
I notice that there was an email with the captioned subject from D.
Scott Brown last email.
The below code fragment works from me, see if it helps for anyone who
are interested in enhancing the camera.py example.
def buffer_cb(pad, buffer):
# Here you have a chance to do something with the image buffer
w,h=320,240
print buffer.size
im = Image.frombuffer('RGB', (w,h), buffer.data, 'raw', 'RGB',
0, 1)
im.save(foo2.jpeg, JPEG)
return True
Alex Leung.
~
This message (including any attachments) is for the named
addressee(s)'s use only. It may contain sensitive, confidential,
private proprietary or legally privileged information intended for a
specific individual and purpose, and is protected by law. If you are
not the intended recipient, please immediately delete it and all copies
of it from your system, destroy any hard copies of it
and notify the sender. Any use, disclosure, copying, or distribution of
this message and/or any attachments is strictly prohibited.
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
--
J. Manrique López de la Fuente
http://www.jsmanrique.es
___
maemo-developers mailing list
maemo-developers@maemo.org
https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: PIL and camera.py
Darius Jack wrote: Alex, please don't fool us and don't attach any clause on privacy, confidentiality or the like in your mail as archives of the mailing list are public. Send instant messages to your online friends http:// Could you refrain from posting advertisements to this list? Ralph pgp36pmgGqFdO.pgp Description: PGP signature ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Qemu Error on Maemo
Hi, I am working on Chinook and after I am launching my application built for ARMEL target, it crashes with this strange error. qemu: Unsupported syscall: 307 qemu: Unsupported syscall: 268 qemu: Unsupported syscall: 238 qemu: uncaught target signal 11 (Segmentation fault) - exiting What could be wrong? Is it that my installation is not perfect? Please help. Thanks Regards, Deepak DISCLAIMER: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. ---___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Qemu Error on Maemo
Hi, ext Deepak Kr. Sharma, Noida wrote: I am working on Chinook and after I am launching my application built for ARMEL target, it crashes with this strange error. qemu: Unsupported syscall: 307 qemu: Unsupported syscall: 268 qemu: Unsupported syscall: 238 Scratchbox ARMEL target is mainly intended for building binaries and packages, not for testing the produced binaries (it may work, but qemu user-space emulation by necessity cannot be complete[1]). You need to test your code on the device. qemu: uncaught target signal 11 (Segmentation fault) - exiting What could be wrong? Is it that my installation is not perfect? Does it crash also in the x86 target or on the device? - Eero [1] System Qemu emulates more, but it's not included to or supported by the maemo SDK. Setting it up requires a lot of effort, but if you're interested, you can find it with Google. ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
RE: Qemu Error on Maemo
Thanks for your prompt reply. It doesn't crash on x86. In the early stages of development it used to work for ARMEL, but now it doesn't. So once the application has been tested for x86, the app should be built for ARMEL and tested on the device? Regards, Deepak -Original Message- From: Eero Tamminen [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 13, 2008 7:20 PM To: Deepak Kr. Sharma, Noida Cc: maemo-developers@maemo.org Subject: Re: Qemu Error on Maemo Hi, ext Deepak Kr. Sharma, Noida wrote: I am working on Chinook and after I am launching my application built for ARMEL target, it crashes with this strange error. qemu: Unsupported syscall: 307 qemu: Unsupported syscall: 268 qemu: Unsupported syscall: 238 Scratchbox ARMEL target is mainly intended for building binaries and packages, not for testing the produced binaries (it may work, but qemu user-space emulation by necessity cannot be complete[1]). You need to test your code on the device. qemu: uncaught target signal 11 (Segmentation fault) - exiting What could be wrong? Is it that my installation is not perfect? Does it crash also in the x86 target or on the device? - Eero [1] System Qemu emulates more, but it's not included to or supported by the maemo SDK. Setting it up requires a lot of effort, but if you're interested, you can find it with Google. DISCLAIMER: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. --- ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Memory card mmc changed status to Read only file system (30)
Thanks Eero, fs is FAT32 (/media/mmc1 ) File manager doesn't have any repair tool. One option is Memory card Kingston Format/ Rename (I don't want just to format) Tools Backup/Restore Search or Help dosfsck -a /dev/mmcblk0p1 FAT 32 File system has -7 clusters but only space for 5830 FAT entries (2GB mmc card) dosfsck -a /dev/mmcblk0 FAT32 Logical sector size is zero. Darius --- On Wed, 13/8/08, Eero Tamminen [EMAIL PROTECTED] wrote: From: Eero Tamminen [EMAIL PROTECTED] Subject: Re: Memory card mmc changed status to Read only file system (30) To: [EMAIL PROTECTED] Cc: maemo-developers@maemo.org Date: Wednesday, 13 August, 2008, 8:57 AM Hi, ext Darius Jack wrote: OS2007HE worked fine, run shell scripts, applications. Recently run wget in recursive mode. Download to flash memory. Learned how to recorsive download to media memory card (MMC). Copied downloaded html files from flash to memory card to make room on flash. And finally tried to remove wget downloaded files from media memory card and found out any, every, each file to be asterisked and can not be deleted. run mount from command line one entry for /media/mmc1 /dev/mcblk0.. on /media/mmc1 type vfat (rw, noauto, nodev, noexec, nosuid, utf8, uid=2, shortname=mixed, dmask=000) chmod -x /media/mmc1 chmod: /media/mmc1: Read-only file system I gvet used media card to save maps in maemo mapper, today nbo chance to run maemo-mapper. Please tell me how to have /media/mmc1 back read-write file system, as changed nothing exceptionally to change status of media file system. Only known reason for this is that the memory card file system has gotten corrupted. When kernel notices this[1], it remounts the file system as read-only so that user cannot corrupt it more. The file system can get corrupted if: - You disconnect the USB cable from PC without safely remove - You take the memory card out when it's reported as being in use (when you open the card cover) - You take the battery out - Device HW watchdog resets the device while the card is being written or it otherwise has data which hasn't been completely written to the card when above things are done. For example streaming flash/video, browser/package downloads, downloads to mail folder that's on memory card, map tile downloads configured to be saved on memory card etc can use memory card extensively. From XTerm you can run dosfsck -n /dev/mcblk0.. to check the file system. Repair can be done in the device from the File manager[2] (or as root with dosfsck), or from PC either using a card reader or when the device USB cable is connected (at least with Linux it's better to unmount the card from PC side before repair though). - Eero [1] Kernel notices the corruption only when some information in the file system is clearly wrong. File system consistency is not checked when the card is mounted (neither in Linux nor Windows either for removable devices). [2] With large full card consistency check / repair can take several minutes and fail because it requires more memory than is available on the device. Send instant messages to your online friends http://uk.messenger.yahoo.com ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Qemu Error on Maemo
FWIW, the below link has a reference to Usage Examples (http://maemo.org/development/documentation/how-tos/4-x/maemo_debugging_guide.html) which doesn't exist. Frank On Wed, Aug 13, 2008 at 9:30 AM, Eero Tamminen [EMAIL PROTECTED] wrote: When testing the code on x86, I would recommend using Valgrind[2] to check for memory access errors and leaks in your code. [2] http://maemo.org/development/tools/doc/diablo/valgrind/ ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Flipping camera image, getting mirrored video
I have written a simple video conferencing application that streams video from one Nokia n8x0 device to another. I have each device streaming from the camera to the other device and the other device displaying in a large frame the incoming video, and the outgoing video being displayed in a small frame of what the other person is seeing. What I would like to do is display a flipped or mirrored version of the outgoing video so that the person can orient themselves appropriately to the camera for the conference. Anybody know how to do this in GSteamer? Please let me know your ideas. I have heard of a Flip plug-in of the Good GST plug-ins, but I can't find any information on how to use it or program it. Thanks. MFonnesbeck ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Qemu Error on Maemo
Deepak Kr. Sharma, Noida wrote: qemu: uncaught target signal 11 (Segmentation fault) – exiting What could be wrong? Is it that my installation is not perfect? Someone pointed me at this: http://lists.gnu.org/archive/html/qemu-devel/2006-03/msg00202.html HTH David ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Qemu Error on Maemo
On Wed, Aug 13, 2008 at 6:47 PM, David Greaves [EMAIL PROTECTED] wrote: Someone pointed me at this: http://lists.gnu.org/archive/html/qemu-devel/2006-03/msg00202.html This information is obsolete: qemu now supports ARMv6 and v7 instruction sets. Laurent ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Battery drain with Diablo 4.2008.23-14
Hello Kimmo Hamalainen wrote: On Mon, 2008-08-11 at 12:26 +0200, ext Juan A. Suarez Romero wrote: Hello, maemoers! The battery of my N810 lasts a day after reflashing it with Diablo version 4.2008.23-14. ... Any clue about why this happens? Do you have the RD mode enabled? It can drain the battery in a day. BR; Kimmo I have exactly the same problem but the RD mode is disabled on my device! Have you got another idea ? -- Philippe ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Battery drain with Diablo 4.2008.23-14
On Wed, 2008-08-13 at 21:25 +0200, Philippe Midol-Monnet wrote: I have exactly the same problem but the RD mode is disabled on my device! Have you got another idea ? I had also rd-flags=serial-console and usb-host-mode enabled. Check also if you have swap enabled (maybe it is corrupted). ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
dsp-sbc and video output problems
Hi everyone, As at least some of you know, the dsp-sbc task works (for all the music I've tried anyway, but I know there are some oddities, which I'm going to investigate - e.g. qwerty's music ;). This is all well and good, but we don't gain much, except possibly better battery life if we scale the CPU speed right back while we decode (and even then I don't know if it will be more efficient). The goal had been to offload sbc encoding to the DSP to allow e.g. mplayer to use more cpu to do video decoding. I and others have done some testing with the dsp task, and with the cpu at 400MHz, although the sbc encoding works fine, the video stutters quite severely (producing 1fps output). This is obviously not workable, so it needs fixing if possible. I've converted the existing task, which uses bulk transfers (where the copying is done in the kernel) to use shared memory and word transfers for synchronisation. This should cut the amount of time the kernel spends doing memory copying by some significant margin (i.e. ~4 bytes data copied rather than 512+78 bytes per transfer, of which there are 375/sec). This hasn't improved things though, the video is still at 1fps. Before I look at DMA or other exotics, I thought I'd ask if anyone knows about the bandwidth limitations of the memory controller/memory? The dsp mp3 task which works with mplayer while displaying video consumes (not quite sure how to work out exact bitrate here), let us say a 5Mb file in 3min or so, which gives 28.4kb/sec (kilobytes that is). My sbc encoder eats 48000hz stereo 16bit data, which equates to 187.5kb/sec input. It also spits out 78 bytes for every 512 bytes it reads in, which adds an extra 28.5kb/sec to the total bandwidth requirement. So, am I running up against a fundamental limitation of the memory architecture? Cheers, Simon ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
Re: Qemu Error on Maemo
From: David Greaves [EMAIL PROTECTED] To: Deepak Kr. Sharma, Noida [EMAIL PROTECTED] Cc: maemo-developers@maemo.org Sent: Wednesday, August 13, 2008 9:47 AM Subject: Re: Qemu Error on Maemo Deepak Kr. Sharma, Noida wrote: qemu: uncaught target signal 11 (Segmentation fault) – exiting What could be wrong? Is it that my installation is not perfect? Someone pointed me at this: http://lists.gnu.org/archive/html/qemu-devel/2006-03/msg00202.html HTH David Hi David, you're right that was an issue in 2006, but fortunately resolved and Qemu now supports ARM v6 v7 There are a few small glitches with some instructions though. qemu/scratchbox is a different branch from the normal qemu, unfortunately that means scratchbox is a little behind in terms of getting bugs fixed. I've found a couple of emulation problems myself, and have switched to real hardware. See if you can locate the instruction that's causing the problem? Ian ___ maemo-developers mailing list maemo-developers@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-developers
