Re: QtMoko v31
Nice release, love the quick GPS fix. I'm having a problem with QX tho, since the update the mouse handling has become erratic, e.g. sometimes it ignores the first click, and on the second it reacts to both (scrolls two pages at once in FBReader, REALLY annoying) or sees the click somewhere else than where the stylus really is. However it doesn't do this right away, after starting QX the first few clicks are interpreted correctly, after the 6th or so it goes nuts. Any way to debug this? Another thing is that after a cold reset (pulling the battery for a second) the HW clock is reset to 01.01.2000. -- View this message in context: http://openmoko-public-mailinglists.1958.n2.nabble.com/Re-QtMoko-v31-tp6039313p6039313.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v31
--- On Fri, 2/18/11, HeaDCase openm...@psychonautical.org wrote: Another thing is that after a cold reset (pulling the battery for a second) the HW clock is reset to 01.01.2000. That is probably caused by a dried up backup battery. People have replaced it with capacitors, see the archives. Boudewijn ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
qtmoko v31 rtc
Hi Does anyone knows if finally this [1] patch was applied to debian kernel? I cannot set rtc, time is lost in every suspend/restart. The same sympthoms as [2] I know I could boot another distro and reset rtc, but I didn't wanted to erase my qtmoko installation in NAND, and I cannot boot any distro from my uSD [1] http://www.mail-archive.com/community@lists.openmoko.org/msg58236.html [2] http://www.mail-archive.com/community@lists.openmoko.org/msg57473.html signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
QtMoko v31 broken build?
Hello everyone, although someone already mentioned this problem, I couldn't find a solution to it. I build QtMoko from git sources following the guide on the wiki, but when it comes to running it (./runqtopia) I get this error: Use of uninitialized value $word in concatenation (.) or string at bin/../src/build/bin/Qtopia/Opt.pm line 551. ERROR: Invalid value for option skin: Valid values: The default value for skin is invalid! at bin/../src/build/bin/Qtopia/Opt.pm line 252. I tried to move the skin packages in different folders (after looking at the launching script) but with no results? What could I have done wrong to get this errors? Any suggestion on how to fix? As always, many thanks in advance to everyone! -- Marco ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v31 broken build?
Marco wrote: Hello everyone, although someone already mentioned this problem, I couldn't find a solution to it. I build QtMoko from git sources following the guide on the wiki, but when it comes to running it (./runqtopia) I get this error: Use of uninitialized value $word in concatenation (.) or string at bin/../src/build/bin/Qtopia/Opt.pm line 551. ERROR: Invalid value for option skin: Valid values: The default value for skin is invalid! at bin/../src/build/bin/Qtopia/Opt.pm line 252. I tried to move the skin packages in different folders (after looking at the launching script) but with no results? What could I have done wrong to get this errors? Any suggestion on how to fix? I am only cross compiling for ARM as described here: https://github.com/radekp/qtmoko/blob/master/README I didnt have time to look at PC build, cant help now sorry... Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Wrong date/ time in QtMoko v31 and v32
Hey there. Every time I restart the system the date/ time is reseted to the epoch (using v31 and v32 installed on the sd card). While booting I get several suspicious messages like RTC_RD_Time: invalid argument or pcf50633-rtc pcf50633-rtc.0: hctosys: unable to read the hardware clock I attached the output of dmesg at http://pastebin.com/GUKUrCu6 Any hint?, please. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Wrong date/ time in QtMoko v31 and v32
2011-01-30@19:00 Daniel MT Hey there. Every time I restart the system the date/ time is reseted to the epoch (using v31 and v32 installed on the sd card). While booting I get several suspicious messages like RTC_RD_Time: invalid argument or pcf50633-rtc pcf50633-rtc.0: hctosys: unable to read the hardware clock I attached the output of dmesg at http://pastebin.com/GUKUrCu6 Any hint?, please. 1) hctosys and any access to the rtc in general is not possible while the qtmoko's AT daemon is running... stop qpe and kill it! :) 2) it resets to epoch if you remove the main battery and your backup battery is died, but if you do not remove the battery and you have a wrong date at reboot you just have to set correctly the rtc (1). btw I do not understand why the qtmoko's at daemon do not allows the access to rtc and I think this is an issue. I tried also to install the debian version of the at daemon, disabling the qtmoko's one (also creating symlinks to the other command), but I've serious problems with alarm/clock interface in qtmoko... -- ALFA21 IS PROVIDED AS IS AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v31
Hi! thank you for this new release! [...] - a message to confirm that an sms was sent; [...] greetings! Joif Hi, I think that SMS confirmation messages are a service offered by phone company (not for free). Moreover you can check in the draft folder in qtmoko messages application to see if your message has been put there as a consequence of a delivery problem. Cheers PS SMS are not a reliable service nor in term of time or in term of guarantee. __ Do You Yahoo!? Poco spazio e tanto spam? Yahoo! Mail ti protegge dallo spam e ti da tanto spazio gratuito per i tuoi file e i messaggi http://mail.yahoo.it ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v31
On Monday 17 January 2011, giacomo 'giotti' mariani wrote: Hi! thank you for this new release! [...] - a message to confirm that an sms was sent; [...] greetings! Joif Hi, I think that SMS confirmation messages are a service offered by phone company (not for free). Moreover you can check in the draft folder in qtmoko messages application to see if your message has been put there as a consequence of a delivery problem. I understood this to be a request for a notification of the form message sent to GSM provider or couldn't send message so I stuck it in the pending queue/draft folder/wherever so that you don't have to check the draft folder each time to see whether the message actually made it to the network. On the other hand FSO supports a wide variety of message status returns if requested[1] so it could have been for a similar level of support. [1] http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.GSM.SMS.html;hb=HEAD#SendTextMessage ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v31
Yes, this is exactly what I meant! I understood this to be a request for a notification of the form message sent to GSM provider or couldn't send message so I stuck it in the pending queue/draft folder/wherever so that you don't have to check the draft folder each time to see whether the message actually made it to the network. On the other hand FSO supports a wide variety of message status returns if requested[1] so it could have been for a similar level of support. [1] http://git.freesmartphone.org/?p=specs.git;a=blob_plain;f=html/org.freesmartphone.GSM.SMS.html;hb=HEAD#SendTextMessage ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v31
On 12/31/10, Hrabosh zbyne...@volny.cz wrote: BTW ... I§m the only one having difficulties using USB host mode in v31? I don't know about USB host mode, but I can't use usb mass storage with v31. Module g_ether is 'always' busy :) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v31 NeronGPS - trace stops after fix loss
Same problem here, I suppose that we need a patch for NeronGPS. This problem is present from early versions of QtMoko! Greetings Joif Il 15/01/2011 11:46, Philip Rhoades ha scritto: People, When I use this app and have recording On, if I go through a tunnel or something and lose the satellite fix, even very briefly - when I look at the trace of the journey later it is truncated from the point where I lost the fix - shouldn't the trace continue or at least start a new trace file? Thanks, Phil. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v31
Hi! thank you for this new release! Qtmoko v31 with the latest u-boot from Gennady. bugs: - like in v30 the gps remains on, it turns off only after a sospension - an evergreen :) power management bug, I didn't try the workaround from Yoric Kotchukov but IMHO it is not comfortable to do it at every release; - I see console messages when I'm connecting with wifi; pro: GPS fix in less then a minute! :) (also after a sospension); wishlist: - a message to confirm that an sms was sent; - less output during boot; - another evergreen :) bluetooth turned off at boot, for battery saving (well, we could make a poll: how many people need the bluetooth after a boot?) greetings! Joif -- View this message in context: http://openmoko-public-mailinglists.1958.n2.nabble.com/QtMoko-v31-tp5881425p5925210.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v31
Thank you for the hint!. I followed the references and boot v31 with Qi. For this I created the empty file 'noboot-GTA02' and put it to /boot in the partitions for debian and shr-u. This works just fine. But: After I use Debian on the 1st Partition and stopped it later and wanted to start again QtMoko, Qi came in kernel panic. There was the message, that mtdblocck6 can't be read (I don't remember the the exact content now). I suspect that wrong boot options had been created (in mtdblock6?) that do not match with the file system for UBIFS. I had to reflash QtMoko completly again (qi, kernel and filesystem). Currently I do not want to start my alternative distributions again because I fear the problem could occur again. Is there perhaps another way to reconstruct the right Qi boot options in this case than to reflash the freerunner? Thanks in advance! Sferic -- View this message in context: http://openmoko-public-mailinglists.1958.n2.nabble.com/QtMoko-v31-tp5881425p5918157.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v31
On Thursday 13 January 2011, sferic wrote: Thank you for the hint!. I followed the references and boot v31 with Qi. For this I created the empty file 'noboot-GTA02' and put it to /boot in the partitions for debian and shr-u. This works just fine. But: After I use Debian on the 1st Partition and stopped it later and wanted to start again QtMoko, Qi came in kernel panic. There was the message, that mtdblocck6 can't be read (I don't remember the the exact content now). I suspect that wrong boot options had been created (in mtdblock6?) that do not match with the file system for UBIFS. I had to reflash QtMoko completly again (qi, kernel and filesystem). Currently I do not want to start my alternative distributions again because I fear the problem could occur again. Is there perhaps another way to reconstruct the right Qi boot options in this case than to reflash the freerunner? Qi boot options for NAND are compiled in, and can only be modified by flashing a modified Qi. I don't think debian would mess with your bootloader, and it shouldn't mess with the kernel in NAND if booted from iSD. It could be that debian was expecting to see something other than UBIFS on mtdblock6 and managed to mess it up. You probably wouldn't have had cause to check for errors in debian's boot messages though. If that is what's happened you should only need to reflash the rootfs, and the cure would be to tell debian about the UBIFS partition using a combination of extra boot parameters and /etc/fstab entries. I've not tried UBIFS yet, so don't ask me what they need to be, but /proc/cmdline in QtMoko should help. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v31
Saluto! I report: Responses to the USSD-request (*xxx#) in Russian are not displayed correctly Russian input and output in terminal is :;?//::;;: In Notes russian is good. - Thank you for your attention. -- View this message in context: http://openmoko-public-mailinglists.1958.n2.nabble.com/QtMoko-v31-tp5881425p5914280.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Freerunner doesn't boot properly after upgrading to QtMoko v31
I've been running QtMoko v26 from my uSD card (Kingston) more or less successfully. I wanted to upgrade to v31, so I added the qtmoko repository as per the instructions on the wiki, did an apt-get update and apt-get dist-upgrade. When I rebooted the phone, I get only a terminal login prompt. Hi, from your log, it appear that the kernel you are running is Linux version 2.6.29-rc3-v26. I uploaded a new version of the packages that should fix this issue. If not, can you please send me the result of ls /boot/ Regards -- Vincent Meurisse ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Freerunner doesn't boot properly after upgrading to QtMoko v31
On Sat, Jan 8, 2011 at 4:01 PM, Vincent Meurisse openmoko-commun...@meurisse.org wrote: I've been running QtMoko v26 from my uSD card (Kingston) more or less successfully. I wanted to upgrade to v31, so I added the qtmoko repository as per the instructions on the wiki, did an apt-get update and apt-get dist-upgrade. When I rebooted the phone, I get only a terminal login prompt. Hi, from your log, it appear that the kernel you are running is Linux version 2.6.29-rc3-v26. I uploaded a new version of the packages that should fix this issue. If not, can you please send me the result of ls /boot/ Hi, I had a similar issue saying that the modem cannot be initialized. After apt-getting your new packages qpe starts again. Thanks! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Freerunner doesn't boot properly after upgrading to QtMoko v31
Thanks Vincent, I had wondered if that was wrong when I checked with uname. Anyway, I just did another apt-get dist-upgrade, and it upgraded 3 more packages - qtmoko-kernel-images, qtmoko-kernel and qtmoko. This time it requested confirmation to change /boot/append-GTA02 which I'm sure it didn't do when I did the dist-upgrade yesterday. And my phone now boots properly!! Thanks, Bernie ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v31
Hi, I would like to use the new QtMoko v31 as my Dailly-Phone on NAND parallel to two other Distros and a big Documents-Partition on my SD-Card. Till v26 I could boot QtMoko over U-Boot 1.3.2-moko 12 (AUX + Power) and the other two over Qi (Power with or without AUX). With the new v31 this is no longer possible: When I try to boot v31 with U-Boot, I get the Message No kernel Image (or similar, the message shows only very short befor the U-Boot-Menu shows up again). From the Discussion around v28 I have learned, that I have to change the bootargs_base to use the new ubifs. I think, I have done this right (with the parameters from v28) but with no success. When I remove my SD-Card I can boot to v31 (with the new Qi). Please tell me the right parameters for U-Boot to use with v31 (and maybe the right way to set them, when I'm logged into U-Boot? - sorry for this NOOB-Question...), or what else could be wrong? Thanks in advance Sferic -- View this message in context: http://openmoko-public-mailinglists.1958.n2.nabble.com/QtMoko-v31-tp5881425p5898831.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v31
On Fri, 7 Jan 2011, sferic wrote: Hi, I would like to use the new QtMoko v31 as my Dailly-Phone on NAND parallel to two other Distros and a big Documents-Partition on my SD-Card. Till v26 I could boot QtMoko over U-Boot 1.3.2-moko 12 (AUX + Power) and the other two over Qi (Power with or without AUX). With the new v31 this is no longer possible: When I try to boot v31 with U-Boot, I get the Message No kernel Image (or similar, the message shows only very short befor the U-Boot-Menu shows up again). From the Discussion around v28 I have learned, that I have to change the bootargs_base to use the new ubifs. I think, I have done this right (with the parameters from v28) but with no success. When I remove my SD-Card I can boot to v31 (with the new Qi). Please tell me the right parameters for U-Boot to use with v31 (and maybe the right way to set them, when I'm logged into U-Boot? - sorry for this NOOB-Question...), or what else could be wrong? Thanks in advance Sferic I have exactly the same problem. But I even cannot boot into Qt without sdCard. Holding power longer prints some debug messages and the reason is, that the ubifs could not be mounted. The funny thing is, that it worked on another phone with the same set-up. The only difference I found is the 'pcb_rev=0x001' environment setting of u-boot... Alex. -- View this message in context: http://openmoko-public-mailinglists.1958.n2.nabble.com/QtMoko-v31-tp5881425p5898831.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v31
sferic wrote: I would like to use the new QtMoko v31 as my Dailly-Phone on NAND parallel to two other Distros and a big Documents-Partition on my SD-Card. Till v26 I could boot QtMoko over U-Boot 1.3.2-moko 12 (AUX + Power) and the other two over Qi (Power with or without AUX). With the new v31 this is no longer possible The problem is that qtmoko kernel image is now larger then 2MB uboot limit. And it is also recommended to not use uboot from NOR for booting the phone. I dont know the details, but NOR uboot loader was said to be bugged and you will also get worse performance then with qi from qtmoko download page (because of glamo 242 timings). I am afraid that nobody will try to solve problem with old uboot that cant be reflashed, this uboot is only good for dfu-util flashing. You can try new uboot that is maintained by Gennady, it should work good: http://wiki.openmoko.org/wiki/U-boot-gena2x or you can keep with qi and try switching partitions with AUX (which is quite tricky but works). Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v31
В Птн, 07/01/2011 в 03:16 -0800, sferic пишет: Hi, I would like to use the new QtMoko v31 as my Dailly-Phone on NAND parallel to two other Distros and a big Documents-Partition on my SD-Card. Till v26 I could boot QtMoko over U-Boot 1.3.2-moko 12 (AUX + Power) and the other two over Qi (Power with or without AUX). With the new v31 this is no longer possible: When I try to boot v31 with U-Boot, I get the Message No kernel Image (or similar, the message shows only very short befor the U-Boot-Menu shows up again). From the Discussion around v28 I have learned, that I have to change the bootargs_base to use the new ubifs. I think, I have done this right (with the parameters from v28) but with no success. When I remove my SD-Card I can boot to v31 (with the new Qi). Please tell me the right parameters for U-Boot to use with v31 (and maybe the right way to set them, when I'm logged into U-Boot? - sorry for this NOOB-Question...), or what else could be wrong? Thanks in advance Sferic Hi, you should never use NOR u-boot for anything expect dfu-flashing. Reason: bootloader is important because it inits hw on boot and on resume. for example according to my measurements power consumption in suspend with nor-uboot is much higher. some things are really not controlled by kernel: bootloader inits something and kernel uses as it were init (many such things, any serial line is example). This may cause any kind of problems, which you'll never notice on first glance - power consumption, memory timings, anything else. If you really like u-boot, just flash it to nand and enjoy (i am maintaining working version http://wiki.openmoko.org/wiki/U-boot-gena2x ), it should work with all qtmokos or other distros. It is realatively easy to reflash nor u-boot btw. Gennady ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: bugs QtMoko v31
2011-01...@18:07 Radek Polak - I'm no longer able to connect to wifi and while I try I see console messages over the framebuffer graphic screen - gprs does not connect too No longer means that in v30 it worked? I dont see any messages and my wifi connects. Maybe we have different setup? Do you use qi or uboot? I have tested both gprs and wifi and it works, also it works for others. We have to find out what is wrong. Please give as much details as possible. sorry, with wifi I was out of the covered range due of interferences from a cordless phone near the antenna: in other words it's ok! btw I do see console messages through the framebuffer screen (like white terminal line over the graphic gui) every time I enable/disable the wifi connection. maybe it's related to the vt switch? about the gprs the problem is the multiplexer: when it's enabled it's not possible to use the gprs data connection. when you turn off the multiplexer it's ok but it's highly probable to loose sms or calls. - the long awaited rollback for the power profile when locked is still on the to-do list I was trying to look at it and at first sight i havent found what is wrong. I have to find the discussion we had last time to refresh my memory. the culprit is the on lock scenario because all the profiles (general, silent, meeting...etc) could support different power management properties each, but maybe the saved array does not take in account a third choice other than on cable and on battery and so begin the chaos both in the gui and in the actual values used in memory. by now it'd be safe to rollback to the original state and forget about the on lock buggy feature. we can achieve the same feature just configuring ad-hoc different profiles. the current implementation has too much negative side effects. - if you put qtmoko on uSD you cannot use the usb-storage because /opt/qtmoko/bin/usb-mass-storage-on.sh tries to use (and unmount) the whole uSD instead of a single partition and the root with qtmoko is on the same device Any ideas how to solve this? I sent to you an early suggested workaround: in the current on script you have to specify a single partition instead of the whole uSD eg: my current partition table is mmcblk0p1=/media/card (fat32 used as usb storage), p2=/ (qtmoko root), p3=swap (little extra memory). in the script I've specified to use only p1 and commented out / modified all the mount checks because they works only with a whole device in mind. I'm not saying this is a nice solution but at least it does not destroy your qtmoko/root filesystem! (-dangerous only if you have qtmoko on uSD too) kind regards and good year to all folks! -- ALFA21 IS PROVIDED AS IS AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Freerunner doesn't boot properly after upgrading to QtMoko v31
Hi, I've been running QtMoko v26 from my uSD card (Kingston) more or less successfully. I wanted to upgrade to v31, so I added the qtmoko repository as per the instructions on the wiki, did an apt-get update and apt-get dist-upgrade. When I rebooted the phone, I get only a terminal login prompt. My dmesg log is attached. I noticed some glamo errors: [21474538.175000] glamo-mci glamo-mci.0: Error after cmd: 0x8120 [21474538.175000] glamo-mci glamo-mci.0: Error after cmd: 0x120 [21474538.175000] glamo-mci glamo-mci.0: Error after cmd: 0x8120 [21474538.175000] glamo-mci glamo-mci.0: Error after cmd: 0x120 So I tried changing the settings in the max_sd_clk file, and also tried the qi-31.udfu bootloader from the QtMoko Downloads, but neither seemed to make any difference. I found one message suggesting that the errors indicate the SD card is not inserted properly, so I removed and reinstalled it a number of times. It seems to me that if it's not installed properly, I get a kernel panic almost immediately, with an error message about not being able to sync the rootfs or something. What else can I try to get QtMoko up and running again without doing a fresh install? Thanks, Bernie [0.00] Linux version 2.6.29-rc3-v26 (ra...@rp-skunk) (gcc version 4.3.2 (Debian 4.3.2-1.1) ) #1 Sat Aug 28 13:11:14 CEST 2010 [0.00] CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177 [0.00] CPU: VIVT data cache, VIVT instruction cache [0.00] Machine: GTA02 [0.00] Memory policy: ECC disabled, Data cache writeback [0.00] On node 0 totalpages: 32768 [0.00] free_area_init_node: node 0, pgdat c03b3dc4, node_mem_map c0413000 [0.00] Normal zone: 256 pages used for memmap [0.00] Normal zone: 0 pages reserved [0.00] Normal zone: 32512 pages, LIFO batch:7 [0.00] CPU S3C2442B (id 0x32440aab) [0.00] S3C24XX Clocks, (c) 2004 Simtec Electronics [0.00] S3C244X: core 400.000 MHz, memory 100.000 MHz, peripheral 50.000 MHz [0.00] CLOCK: Slow mode (1.500 MHz), fast, MPLL on, UPLL on [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512 [0.00] Kernel command line: loglevel=4 console=tty0 console=ttySAC2,115200 init=/sbin/init ro mtdparts=physmap-flash:-(nor);neo1973-nand:0x0004(qi),0x0004(depr-ub-env),0x0080(kernel),0x000a(depr),0x0004(identity-ext2),0x0f6a(rootfs) g_ether.host_addr=00:1F:11:01:A1:E3 g_ether.dev_addr=00:1F:11:01:A1:E3 root=/dev/mmcblk0p1 rootdelay=1 console=tty0 loglevel=3 rootdelay=1 [0.00] Unknown boot option `g_ether.host_addr=00:1F:11:01:A1:E3': ignoring [0.00] Unknown boot option `g_ether.dev_addr=00:1F:11:01:A1:E3': ignoring [0.00] RCU-based detection of stalled CPUs is enabled. [0.00] irq: clearing pending ext status 000b12f0 [0.00] irq: clearing pending ext status 000902d0 [0.00] irq: clearing subpending status 0180 [0.00] irq: clearing subpending status 0080 [0.00] PID hash table entries: 512 (order: 9, 2048 bytes) [0.00] timer tcon=, tcnt a2c1, tcfg 0200,, usec 1eb8 [21474536.48] Console: colour dummy device 80x30 [21474536.48] console [tty0] enabled [21474536.48] console [ttySAC2] enabled [21474536.48] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes) [21474536.48] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes) [21474536.495000] Memory: 128MB = 128MB total [21474536.495000] Memory: 125624KB available (3456K code, 533K data, 140K init) [21474536.495000] Calibrating delay loop... 199.47 BogoMIPS (lpj=498688) [21474536.595000] Mount-cache hash table entries: 512 [21474536.595000] CPU: Testing write buffer coherency: ok [21474536.60] net_namespace: 936 bytes [21474536.605000] regulator: core version 0.5 [21474536.605000] NET: Registered protocol family 16 [21474536.63] S3C Power Management, Copyright 2004 Simtec Electronics [21474536.63] modem wakeup interrupt [21474536.63] wake enabled for irq 17 [21474536.63] wake enabled for irq 49 [21474536.64] s3c24xx-adc s3c24xx-adc: attached adc driver [21474536.645000] S3C2442: Initialising architecture [21474536.645000] S3C24XX DMA Driver, (c) 2003-2004,2006 Simtec Electronics [21474536.645000] DMA channel 0 at c8808000, irq 33 [21474536.645000] DMA channel 1 at c8808040, irq 34 [21474536.645000] DMA channel 2 at c8808080, irq 35 [21474536.645000] DMA channel 3 at c88080c0, irq 36 [21474536.645000] S3C244X: Clock Support, DVS off [21474536.72] bio: create slab bio-0 at 0 [21474536.73] usbcore: registered new interface driver usbfs [21474536.73] usbcore: registered new interface driver hub [21474536.73] usbcore: registered new device driver usb [21474536.78] NET: Registered protocol family 2 [21474536.835000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes) [21474536.835000]
Re: QtMoko v31 - Debian update packages
Thank you very much urodelo On Wed, 05 Jan 2011 23:11:51 +0100, Vincent Meurisse openmoko-commun...@meurisse.org wrote: Hello, I (finally) uploaded the new Debian packages for QtMoko v31. Make sure you read the releases notes http://qtmoko.org/wiki/Update#Update_to_v31 or you might end-up with no sound during calls. As usual, instructions are located at http://qtmoko.org/wiki/Update. Regards ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: bugs QtMoko v31
BTW ... mine Eyepiece did ask for some aditional libraries on the first run and then succesfully apt-got them. Zb. Radek Polak píše v St 05. 01. 2011 v 10:34 +0100: Nashvin Gangaram wrote: Hi Radek Everything's working great in QtMoko v31... except for Eyepiece. I get an error: Error: cannot load plugin when trying to open PDF files. Is libdjvulibre21 required to view PDF files now? Yup it's needed for PDF files. Eyepiece should install it on the first run, but if that somehow does not work, you can install manually with apt-get from command line. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: bugs QtMoko v31
Nashvin Gangaram wrote: Hi Radek Everything's working great in QtMoko v31... except for Eyepiece. I get an error: Error: cannot load plugin when trying to open PDF files. Is libdjvulibre21 required to view PDF files now? Yup it's needed for PDF files. Eyepiece should install it on the first run, but if that somehow does not work, you can install manually with apt-get from command line. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
QtMoko v31 Voice Notes volume
People, Is there some way to increase the playback volume of recorded voice notes? Thanks, Phil. -- Philip Rhoades GPO Box 3411 Sydney NSW 2001 Australia E-mail: p...@pricom.com.au ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v31 Voice Notes volume
On Thu, 6 Jan 2011, Philip Rhoades wrote: People, Is there some way to increase the playback volume of recorded voice notes? Sorry, no solution but another question: What software are you using for recording voicenotes? I have SHR installed and did not find one single application (out of 5 or so) which worked. I would like to have this feature (maybe separate also on my second phone with Qt instead). Alex. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v31 Voice Notes volume
Philip Rhoades wrote: Is there some way to increase the playback volume of recorded voice notes? You can start recording and play with volumes from ssh in alsamixer. When you are happy, you can save the state like: alsactl -f /usr/share/openmoko/scenarios/capturehandset.state store Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v31 Voice Notes volume
Alexander Lehner wrote: What software are you using for recording voicenotes? I have SHR installed and did not find one single application (out of 5 or so) which worked. I would like to have this feature (maybe separate also on my second phone with Qt instead). QtMoko has voice notes application installed by default. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
QtMoko v31 - Debian update packages
Hello, I (finally) uploaded the new Debian packages for QtMoko v31. Make sure you read the releases notes http://qtmoko.org/wiki/Update#Update_to_v31 or you might end-up with no sound during calls. As usual, instructions are located at http://qtmoko.org/wiki/Update. Regards -- Vincent Meurisse ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: bugs QtMoko v31
- the long awaited rollback for the power profile when locked is still on the to-do list I was trying to look at it and at first sight i havent found what is wrong. I have to find the discussion we had last time to refresh my memory. - Power management still confuses or loses battery/cable settings, only when locked settings work. In $HOME/Settings/Trolltech/qpe.conf paste Lock/External/BatteryPower settings from previously working version, and do not run Settings/Power management. - Thank you for your attention. -- View this message in context: http://openmoko-public-mailinglists.1958.n2.nabble.com/QtMoko-v31-tp5881425p5888394.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: bugs QtMoko v31
Hi Radek Everything's working great in QtMoko v31... except for Eyepiece. I get an error: Error: cannot load plugin when trying to open PDF files. Is libdjvulibre21 required to view PDF files now? Thanks -Nashvin ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v31
Hrabosh wrote: What about replacing these by F1-F10 keys? Good idea. I took a quick and Fn keys are not in the table, so they should be added there and to the layout (keyboardframe.cpp), but i dont feel now like playing with it, so maybe later or patches welcome :) Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
bugs QtMoko v31
2010-12...@16:40 Radek Polak - better layout in docked keyboard you can now remove the folded arrows keys and make the others bigger (home, ins, del...) bugs: - I'm no longer able to connect to wifi and while I try I see console messages over the framebuffer graphic screen - gprs does not connect too - the long awaited rollback for the power profile when locked is still on the to-do list - if you put qtmoko on uSD you cannot use the usb-storage because /opt/qtmoko/bin/usb-mass-storage-on.sh tries to use (and unmount) the whole uSD instead of a single partition and the root with qtmoko is on the same device -- ALFA21 IS PROVIDED AS IS AND WITHOUT WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: bugs QtMoko v31
Alfa21 wrote: you can now remove the folded arrows keys and make the others bigger (home, ins, del...) Well it's just half of normal key, so you can make just one button 50% wider. Maybe the folded are could have some good use - fn keys or something else. Let's give it a few more days what people will come with. But removing that key is for sure good option. bugs: - I'm no longer able to connect to wifi and while I try I see console messages over the framebuffer graphic screen - gprs does not connect too No longer means that in v30 it worked? I dont see any messages and my wifi connects. Maybe we have different setup? Do you use qi or uboot? I have tested both gprs and wifi and it works, also it works for others. We have to find out what is wrong. Please give as much details as possible. - the long awaited rollback for the power profile when locked is still on the to-do list I was trying to look at it and at first sight i havent found what is wrong. I have to find the discussion we had last time to refresh my memory. - if you put qtmoko on uSD you cannot use the usb-storage because /opt/qtmoko/bin/usb-mass-storage-on.sh tries to use (and unmount) the whole uSD instead of a single partition and the root with qtmoko is on the same device Any ideas how to solve this? Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: bugs QtMoko v31
Hi Radek, amazing work as always, this version is as faster as ever. Everything's working fine, except a few glitches when using programs under QX. In particular even if I select Use virtual keyboard in the setting, it still doesn't appear; also, even when selecting use window manager there's no window around the application, so the only way to close the application is pressing the AUX button. Again, thank for all your efforts and support!! -- Marco ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: bugs QtMoko v31
Marco wrote: Everything's working fine, except a few glitches when using programs under QX. In particular even if I select Use virtual keyboard in the setting, it still doesn't appear; It has simple workaround. Go to the textbox (which reads xterm) and switch to docked keyboard there. Now when you launch your app the docked keyboard should appear. even when selecting use window manager there's no window around the application, so the only way to close the application is pressing the AUX button. The default window manager in QX is very simple (just a few lines). It just handles window size so that it does not redraw qtopia toolbar. If you need real window manager, you can select use matchbox in app settings. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v31
Thanks to every one behind this! Happy new year too! Sylvain 2010/12/30 Radek Polak pson...@seznam.cz Hi, new stable qtmoko release v31 is now out. You can download images for SD card and NAND flash from sourceforge [1] and sources from github [2]. QtMoko is distribution for Freerunner based on debian rootfs and qtopia phone stack and GUI. For more info please see [3] and [4]. Changes since previous version: - fixed invisible call button in finximod theme (Joif) - translated to French (Gregoire Juge) - updated Danish translation (Ole Carlsen) - better layout in docked keyboard - commented completion strip in docked keyboard - VT not switch to graphics which fixes X hang in VT_WAITACTIVE (Gennady+Me) - fix QX crash after pause/resume - using openssh-server instead of dropbear again This is first stable release based on kernel 2.6.34. I think nearly all regressions to andy-tracking 2.6.29 are fixed so i will tag last commit with 2.6.29 support and will merge 2.6.34 support in master. Docked keyboard (the one suitable for terminal) is now much better. It has same layout as in SHR, which means you will have cursor keys on main screen. The completion strip was IMO quite useless and wasted only space so it's now disabled. As for the VT fix (or hack ;-) it's now possible to use any X server with QX. So you can install full xserver and use it instead of Xglamo which is default. So happy new year! Regards Radek [1] https://sourceforge.net/projects/qtmoko/files/ [2] https://github.com/radekp/qtmoko [3] http://www.qtmoko.org/ [4] http://activationrecord.net/radekp/qtmoko/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v31
Den 30-12-2010 16:40, Radek Polak skrev: - updated Danish translation (Ole Carlsen) Hi Radek I don't have any comment on v31 in general as I haven't tried it very long yet. I though have some comment on the Danish translation as it looks like some of the files doesn't get build, primarily those with 'Qtopia' in their name and I think there are some 7 files missing as I did translate 88 but there are 'only' 81 in the folder. I will probably do some testing now and return in the new year. :-) -- Ole @ Carlsen-web.dk ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v31
Well done ! As to the keyboard: I really appreciate having arrow keys there (because of command history in Terminal). If you hit the very left key in the second row, another keys (end,home,arrows..) shows up - but the same keys ale already in the default keyboard, so now they are present twice. What about replacing these by F1-F10 keys? BTW ... I§m the only one having difficulties using USB host mode in v31? Zb. Sylvain Paré píše v Pá 31. 12. 2010 v 12:58 +0100: Thanks to every one behind this! Happy new year too! Sylvain 2010/12/30 Radek Polak pson...@seznam.cz Hi, new stable qtmoko release v31 is now out. You can download images for SD card and NAND flash from sourceforge [1] and sources from github [2]. QtMoko is distribution for Freerunner based on debian rootfs and qtopia phone stack and GUI. For more info please see [3] and [4]. Changes since previous version: - fixed invisible call button in finximod theme (Joif) - translated to French (Gregoire Juge) - updated Danish translation (Ole Carlsen) - better layout in docked keyboard - commented completion strip in docked keyboard - VT not switch to graphics which fixes X hang in VT_WAITACTIVE (Gennady+Me) - fix QX crash after pause/resume - using openssh-server instead of dropbear again This is first stable release based on kernel 2.6.34. I think nearly all regressions to andy-tracking 2.6.29 are fixed so i will tag last commit with 2.6.29 support and will merge 2.6.34 support in master. Docked keyboard (the one suitable for terminal) is now much better. It has same layout as in SHR, which means you will have cursor keys on main screen. The completion strip was IMO quite useless and wasted only space so it's now disabled. As for the VT fix (or hack ;-) it's now possible to use any X server with QX. So you can install full xserver and use it instead of Xglamo which is default. So happy new year! Regards Radek [1] https://sourceforge.net/projects/qtmoko/files/ [2] https://github.com/radekp/qtmoko [3] http://www.qtmoko.org/ [4] http://activationrecord.net/radekp/qtmoko/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: QtMoko v31
Keep up the good work and very happy new year Rgds Rp On 12/31/10, Hrabosh zbyne...@volny.cz wrote: Well done ! As to the keyboard: I really appreciate having arrow keys there (because of command history in Terminal). If you hit the very left key in the second row, another keys (end,home,arrows..) shows up - but the same keys ale already in the default keyboard, so now they are present twice. What about replacing these by F1-F10 keys? BTW ... I§m the only one having difficulties using USB host mode in v31? Zb. Sylvain Paré píše v Pá 31. 12. 2010 v 12:58 +0100: Thanks to every one behind this! Happy new year too! Sylvain 2010/12/30 Radek Polak pson...@seznam.cz Hi, new stable qtmoko release v31 is now out. You can download images for SD card and NAND flash from sourceforge [1] and sources from github [2]. QtMoko is distribution for Freerunner based on debian rootfs and qtopia phone stack and GUI. For more info please see [3] and [4]. Changes since previous version: - fixed invisible call button in finximod theme (Joif) - translated to French (Gregoire Juge) - updated Danish translation (Ole Carlsen) - better layout in docked keyboard - commented completion strip in docked keyboard - VT not switch to graphics which fixes X hang in VT_WAITACTIVE (Gennady+Me) - fix QX crash after pause/resume - using openssh-server instead of dropbear again This is first stable release based on kernel 2.6.34. I think nearly all regressions to andy-tracking 2.6.29 are fixed so i will tag last commit with 2.6.29 support and will merge 2.6.34 support in master. Docked keyboard (the one suitable for terminal) is now much better. It has same layout as in SHR, which means you will have cursor keys on main screen. The completion strip was IMO quite useless and wasted only space so it's now disabled. As for the VT fix (or hack ;-) it's now possible to use any X server with QX. So you can install full xserver and use it instead of Xglamo which is default. So happy new year! Regards Radek [1] https://sourceforge.net/projects/qtmoko/files/ [2] https://github.com/radekp/qtmoko [3] http://www.qtmoko.org/ [4] http://activationrecord.net/radekp/qtmoko/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- Ranjit Pillai gnumen.org ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
QtMoko v31
Hi, new stable qtmoko release v31 is now out. You can download images for SD card and NAND flash from sourceforge [1] and sources from github [2]. QtMoko is distribution for Freerunner based on debian rootfs and qtopia phone stack and GUI. For more info please see [3] and [4]. Changes since previous version: - fixed invisible call button in finximod theme (Joif) - translated to French (Gregoire Juge) - updated Danish translation (Ole Carlsen) - better layout in docked keyboard - commented completion strip in docked keyboard - VT not switch to graphics which fixes X hang in VT_WAITACTIVE (Gennady+Me) - fix QX crash after pause/resume - using openssh-server instead of dropbear again This is first stable release based on kernel 2.6.34. I think nearly all regressions to andy-tracking 2.6.29 are fixed so i will tag last commit with 2.6.29 support and will merge 2.6.34 support in master. Docked keyboard (the one suitable for terminal) is now much better. It has same layout as in SHR, which means you will have cursor keys on main screen. The completion strip was IMO quite useless and wasted only space so it's now disabled. As for the VT fix (or hack ;-) it's now possible to use any X server with QX. So you can install full xserver and use it instead of Xglamo which is default. So happy new year! Regards Radek [1] https://sourceforge.net/projects/qtmoko/files/ [2] https://github.com/radekp/qtmoko [3] http://www.qtmoko.org/ [4] http://activationrecord.net/radekp/qtmoko/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
