Re: Buzz Fix
2011-03-08@21:04 Wesley Frazier > Anybody have any tips on mitigating the buzz? > > If I have a model with the buzz, will grabbing the GTA04 motherboard > when it comes out correct it? try to low the gain of your mic with alsamixer during a call and if you like the result save the status in the "scenario" file(s) the drawback is you have to speak loud about gta04: it's a completely different hardware to be put inside your case, not an "upgrade" module for gta02 board... the only thing you keep from your current phone is just the plastic case and the display ;) (+the battery, maybe) (and I hope we don't have similar hw issues in the new gta04 too! ^_^) -- 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 v33
Thanks Radek, for all the great work! I have a suggestion, and don't know if it will be a popular one: Can Eyepiece be included in the default base installation? -Nashvin On Fri, Mar 4, 2011 at 8:37 AM, Radek Polak wrote: > Hi, > i have uploaded new qtmoko v33 images to sourceforge now [1]. They are > still > called experimental, because a few things are still not perfect. > > For more information about qtmoko please see [2][3]. > > Here is list of changes since v32: > > * new theme "faenqo" (cyberspirit) > * qtmoko and it's applications are packaged as debian packages > * compiled natively on ARM with debian toolchain > * new web with applications and themes [4] > * applications are now installed from web browser > * new icon for installing qtmoko apps in Applications > * you can easily install new themes in appearence settings > * fixed usb mass storage script (thanks to Alfa21) > * omhacks are installed as debian package from sid > * qmplayer installs mencoder in debian > * mencoder uses ac3 codec for audio > * orange led brightness should be fixed (only in sources) > * moved all apps from qtmoko-apps git to qtmoko git > * updated docs for building and compiling > > The list is quite short on how much of work it was. > > Most of the effort was to package everything with debian package system. > This > should be done now except for kernel which is on the list for next release. > > For installing qtmoko with apt there is new line now in > /etc/apt/sources.list: > > deb http://qtmoko.sourceforge.net/debian/ / > > Applications and themes are right now not in that repo. They can be > installed > from web browser from url below [4]. Applications are put in categories, > they > have tags and screenshots for easy searching and navigation. Please let me > know if you have ideas or patches for improving this. The application web > is > generated from .xml files with xsltproc and bash scripts so it should be > quite > easy to change look or improve it. > > Btw .deb packages for most of the apps are still building right now so > please > be patient - i will upload them as soon as the build is finished. > > Applications in this version can be still installed with old qtopia package > system, but i am going to disable this for next release if new packaging > will > be ok for you. > > My plan for next version is to fix regression if you find any, package > properly > also kernel and release it as stable. > > Plans for future is FSO framework in qtmoko. > > Don't forget to try new faenqo theme or use older themes (asthromod) which > were only in git until now. They are really nice. > > Thanks for supporting qtmoko > > Regards > > Radek > > > > [1] http://sourceforge.net/projects/qtmoko/files/Experimental/ > [2] http://qtmoko.org/ > [3] http://qtmoko.sourceforge.net/ > [4] http://qtmoko.sourceforge.net/apps/ > [5] https://github.com/radekp/qtmoko/tree/master/web/qtmoko-apps > > ___ > 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: Have I fried my freerunner?
On Fri, 4 Mar 2011, Chuck Norris wrote: > 04.03.2011 06:27, John O'Hagan пишет: > > On Tue, 1 Mar 2011, Thomas HOCEDEZ wrote: > >> On Tue, 1 Mar 2011 13:16:54 + > >> > >> "John O'Hagan" wrote: > >>> Hi, > >>> > >>> After a couple of years of fairly trouble-free > >>> qtmoko-FR use, I used a cheap in-car charger on a > >>> recent trip. The charger died, and the FR itself > >>> began exhibiting a number of odd behaviours such > >>> as not coming back from suspend, indicating > >>> charging status when it was not charging, > >>> crashing, and after a couple of days, not booting > >>> into qtmoko at all. > >>> > >>> Instead, I get an error like "debugfs dir creation > >>> failed -19", then a Debian login prompt. > >>> Unfortunately, I haven't been able to ssh into the > >>> FR to investigate, as it doesn't show up on my > >>> debian laptop as usbX or ethX, only as /dev/ACM0, > >>> so I'm stuck as to how to get the USB networking > >>> going. > > > > [...] > > > >> Woo, don't smells good. > >> But I would try to reflash it with QtMoko once again. or with a > > > > totally > > > >> different distro such as Android. The secodn one has an > > > > installer that > > > >> verbose the output of the flashing progress. This way, you can > > > > see if it > > > >> fails to write on some clusters on the flash. > >> > >> Let us know the results ! > > > > Thanks for your reply. I'm a little confused about what is going on > > in my FR. The fact that I'm getting a Debian login prompt means it > > is actually booting, right? So the problem must be in subsequent > > stages of initialising Qtopia? > > > > Because it's not showing up as /dev/ethX or /devusbX as I > > mentioned, I haven't been able to re-flash it or even back it up > > with neotool, which doesn't find the device. To be honest it's > > been a long time since I flashed it because I've been updating > > qtmoko using apt-get, so I may be doing it wrong. Any advice how > > to ssh into the freerunner in theses circumstances? I needed to reflash both Qi and the rootfs to get a bootable phone, but to no avail: although the reflashing went fine, the FR will no longer charge, although the battery indicator showed charging status. Both my batteries are now dead. Looks like my poor FR took quite a beating from that cheap charger. Any advice how to diagnose/repair this? Thanks. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Buzz Fix
I seem to have had the missofrtune of picking up an A5. My first few calls were fine but now Ive had a lot of complaints about strange background noiseses. The revision number of /proc/cpuinfo is 0350. So I think I am running an A5. Anybody know of anyone who still does the fix here in the U.S. ? I am of course willing to pay. Anybody have any tips on mitigating the buzz? If I have a model with the buzz, will grabbing the GTA04 motherboard when it comes out correct it? -- Wes Frazier "Nationalism is an infantile disease. It is the measles of mankind." - Albert Einstein ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: qtmoko33 regression in qtmaze (was: [cutemaze] on [qtmoko 33] howto control moves?)
> > ouch! you're right: qtmaze regression, the ball stuck firmly in the initial > position! > :-) I'm glad someone else reported that! I try to use a script to switch between usb networking and mass storage but it is not possible to rmmod g_ether I saw this problem reported way back and it seemed to have been fixed, but is certinly biting me in v33 -- David Matthews m...@dmatthews.org ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
qtmoko33 regression in qtmaze (was: [cutemaze] on [qtmoko 33] howto control moves?)
On Tuesday, March 8, 2011 21:32:55, Joif wrote: > Hi! > Are we talking about QtMaze? If so I noticed that in the v33, and at least > in QtMaze, the accelerometers do not work. Instead, the new game Gottet (a > tetris clone) that I found in the apps page, seems to not have any kind of > control buttons. I don't know if in previous version of QtMoko it worked ouch! you're right: qtmaze regression, the ball stuck firmly in the initial position! but no, cutemaze is a different game affected by the same issue you have found in gottet. regards ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[qtmoko33] wifi wpa2-psk issue (was: qtmoko v33)
2011-03-05@17:14 Alfa21 > 2011-03-05@12:42 Radek Polak > > > > * unable to connect wifi wpa2-psk > > > > Was is working in some older versions? It can be bug either in > > wpa_supplicatant or in qmoko wifi plugin that creates configuration for > > wpa_supplicant. Does it work when you setup wpa_supplicant from command > > line? > > I am trying to connect WPA2-psk here and it does not work too :( > > previously I had v31 and it was ok, but only on the first attempt and then I > needed to reboot > (rebooted also because wifi didn't stop and battery drain empty in few hours) > the blue led in v31 did never turn on while connected. > before v31 it was all ok... IIRC hi, I tried to manually configure the wifi link: as you can read below, seems to be something different with the wpa driver in v33... Initializing interface 'eth0' conf '/etc/wpa_supplicant/test.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A' Configuration file '/etc/wpa_supplicant/test.conf' -> '/etc/wpa_supplicant/test.conf' Reading configuration file '/etc/wpa_supplicant/test.conf' ctrl_interface='/var/lib/wpa_supplicant' ctrl_interface_group='0' eapol_version=1 fast_reauth=1 ap_scan=1 Priority group 0 id=0 ssid='A21_net' Initializing interface (2) 'eth0' Interface eth0 set UP - waiting a second for the driver to complete initialization SIOCGIWRANGE: WE(compiled)=22 WE(source)=13 enc_capa=0x0 capabilities: key_mgmt 0x0 enc 0x3 flags 0x0 ioctl[SIOCSIWESSID]: Invalid argument WEXT: Operstate: linkmode=1, operstate=5 Own MAC address: 00:XX:XX:XX:XX:XX wpa_driver_wext_set_wpa wpa_driver_wext_set_key: alg=0 key_idx=0 set_tx=0 seq_len=0 key_len=0 ioctl[SIOCSIWENCODEEXT]: Operation not supported Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE wpa_driver_wext_set_key: alg=0 key_idx=1 set_tx=0 seq_len=0 key_len=0 ioctl[SIOCSIWENCODEEXT]: Operation not supported Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE wpa_driver_wext_set_key: alg=0 key_idx=2 set_tx=0 seq_len=0 key_len=0 ioctl[SIOCSIWENCODEEXT]: Operation not supported Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE wpa_driver_wext_set_key: alg=0 key_idx=3 set_tx=0 seq_len=0 key_len=0 ioctl[SIOCSIWENCODEEXT]: Operation not supported Driver did not support SIOCSIWENCODEEXT, trying SIOCSIWENCODE wpa_driver_wext_set_countermeasures wpa_driver_wext_set_drop_unencrypted RSN: flushing PMKID list in the driver Setting scan request: 0 sec 10 usec -- 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: [cutemaze] on [qtmoko 33] howto control moves?
Hi! Are we talking about QtMaze? If so I noticed that in the v33, and at least in QtMaze, the accelerometers do not work. Instead, the new game Gottet (a tetris clone) that I found in the apps page, seems to not have any kind of control buttons. I don't know if in previous version of QtMoko it worked with the accelerometers, but in v33 the game does not respond to any kind of input. Regards Joif -- View this message in context: http://openmoko-public-mailinglists.1958.n2.nabble.com/cutemaze-on-qtmoko-33-howto-control-moves-tp6098568p6140519.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: [qtmoko33 regression] segfaults moving items in star menu (was: qtmoko v33)
segfault in qtmoko v32 too On Tue, 8 Mar 2011 19:39:36 +0100, Alfa21 wrote: > 2011-03-05@17:14 Alfa21 > >> > > * got some segfaults changing the theme and then opening the dialer >> > >> > IIRC it crashed here to, but after restart it was ok. >> >> yeah, the same here... it's not a show stopper bug. > > > another segfault always reproducible and no workaround available AFAIK to > sort items in preferred menu: > > - long pres aux button > - in starred tab, long press on the item you want to move up/down > - select in contextual menu "move" > - select its final position in the list > => segmentation fault, qpe restarts, items keeps old positions > > this was ok in the previous qtmoko release I had (v31) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[qtmoko33 regression] segfaults moving items in star menu (was: qtmoko v33)
2011-03-05@17:14 Alfa21 > > > * got some segfaults changing the theme and then opening the dialer > > > > IIRC it crashed here to, but after restart it was ok. > > yeah, the same here... it's not a show stopper bug. another segfault always reproducible and no workaround available AFAIK to sort items in preferred menu: - long pres aux button - in starred tab, long press on the item you want to move up/down - select in contextual menu "move" - select its final position in the list => segmentation fault, qpe restarts, items keeps old positions this was ok in the previous qtmoko release I had (v31) -- 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 and FSO (was: qtmoko v33)
Dmitry Chistikov wrote: > I'm afraid it's too early to ask, but could you give an estimate on how > much time it'll take to enable the use of FSO framework? Just something > like "about a year" or, say, "not less than four months". Writing simple dialer application could be matter of days/hours. Integrating all the functions so that it looks like qtmoko now will be much more difficult (i cant even guess how much). We also need FSO running on debian - i'd prefer current git version. I am not aware if there are debian packages for recent FSO. Anyone knows? Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
QtMoko and FSO (was: qtmoko v33)
Radek Polak, Mar. 04, 2011, 07:37 +0100: > i have uploaded new qtmoko v33 images to sourceforge now [1]. [...] > The list is quite short on how much of work it was. Hello, Radek! Thank you for the work you are doing. > Most of the effort was to package everything with debian package system. This > should be done now except for kernel which is on the list for next release. > [...] > My plan for next version is to fix regression if you find any, package > properly > also kernel and release it as stable. > > Plans for future is FSO framework in qtmoko. I'm afraid it's too early to ask, but could you give an estimate on how much time it'll take to enable the use of FSO framework? Just something like "about a year" or, say, "not less than four months". Thanks once more. -- Dmitry Chistikov ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: performance testing of UNWIND kernel option
Ok, it is reasonable to keep CONFIG_ARM_UNWIND enabled when this option have no practical effect on performance or latency in kernel. So, keep it enabled. :-) Martin 'Martix' Holec openmoko.cz / openmobility.cz 2011/3/8 Gennady Kupava : > Hi, > > 1. UNWIND do not influence performance, so enabling it should make no > harm (according to kernel doc, i trust em 99.9%). > 2. ability to get stack trace is widely accepted bare minimum of debug > info, this is info is _really_ (not like other hardly usable debugging > stuff were enabled earlier) invaluable for fixing and identifying > problems found. > > So, no reason remove both. It is even kind of switch in kernel config > turn on UNWIND -> FRAME_POINTER turns off. No affect on performance, add > ability to identify problem -> must have IMO. > > Gennady. > > В Втр, 08/03/2011 в 16:40 +0100, Martix пишет: >> Hi, >> thanks for comparison. >> I miss test with both CONFIG_ARM_UNWIND and CONFIG_FRAME_POINTER >> disabled, theoreticaly it could be faster. Anyway, why regular user >> (no developer, nor tester) needs to have CONFIG_ARM_UNWIND or >> CONFIG_FRAME_POINTER enabled? I suggest to disable CONFIG_ARM_UNWIND >> in stable kernel images. Stable I mean (in this case) kernel versions >> which is well tested in SHR-t and stable revisions of Qt Moko. >> >> Thanks Denis and Gennady. >> >> Martin 'Martix' Holec >> openmoko.cz/openmobility.cz >> >> >> 2011/3/8 Gennady Kupava : >> > Hi, list. >> > >> > Today I noticed the following change in SHR: >> > http://git.openembedded.org/cgit.cgi/openembedded/commit/?id=1516588acd3c4b4dd4add71d06ab8ce0d1bafa02 >> > (by Denis 'GNUtoo' Carikli ) and decided to lmbench it. >> > >> > Here are results: http://www.bsdmn.com/lmbench/unwind_summary.txt >> > >> > You can see comparison of: >> > >> > 34def -> kernel with CONFIG_FRAME_POINTER >> > unwind -> kernel with CONFIG_ARM_UNWIND >> > default -> for reference, old debugging kernel >> > >> > The unwind option provide clear benefit of 5%-10% in almost every area. >> > >> > Nice spot Denis! >> > >> > Gennady. >> > >> > >> > ___ >> > 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: [qtmoko33] usb storage issue and kernel panic (was Re: qtmoko v33)
Alfa21-mobile wrote:
> hi radek,
> I modified the last line in "on" script like:
> #modprobe g_file_storage file=${DEV_NAME} stall=0
> modprobe g_file_storage file=${DEV_NAME} stall=0 removable=y
Oki, i have commited this change.
Thanks!
Radek
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: performance testing of UNWIND kernel option
Hi, thanks for comparison. I miss test with both CONFIG_ARM_UNWIND and CONFIG_FRAME_POINTER disabled, theoreticaly it could be faster. Anyway, why regular user (no developer, nor tester) needs to have CONFIG_ARM_UNWIND or CONFIG_FRAME_POINTER enabled? I suggest to disable CONFIG_ARM_UNWIND in stable kernel images. Stable I mean (in this case) kernel versions which is well tested in SHR-t and stable revisions of Qt Moko. Thanks Denis and Gennady. Martin 'Martix' Holec openmoko.cz/openmobility.cz 2011/3/8 Gennady Kupava : > Hi, list. > > Today I noticed the following change in SHR: > http://git.openembedded.org/cgit.cgi/openembedded/commit/?id=1516588acd3c4b4dd4add71d06ab8ce0d1bafa02 > (by Denis 'GNUtoo' Carikli ) and decided to lmbench it. > > Here are results: http://www.bsdmn.com/lmbench/unwind_summary.txt > > You can see comparison of: > > 34def -> kernel with CONFIG_FRAME_POINTER > unwind -> kernel with CONFIG_ARM_UNWIND > default -> for reference, old debugging kernel > > The unwind option provide clear benefit of 5%-10% in almost every area. > > Nice spot Denis! > > Gennady. > > > ___ > 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: performance testing of UNWIND kernel option
Em 08-03-2011 14:01, Gennady Kupava escreveu: Hi, list. Today I noticed the following change in SHR: http://git.openembedded.org/cgit.cgi/openembedded/commit/?id=1516588acd3c4b4dd4add71d06ab8ce0d1bafa02 (by Denis 'GNUtoo' Carikli) and decided to lmbench it. Here are results: http://www.bsdmn.com/lmbench/unwind_summary.txt You can see comparison of: 34def -> kernel with CONFIG_FRAME_POINTER unwind -> kernel with CONFIG_ARM_UNWIND default -> for reference, old debugging kernel The unwind option provide clear benefit of 5%-10% in almost every area. Nice spot Denis! It does feel faster! OpenMoko Freerunner, probably the only "obsolete" phone that keeps getting better :) Rui ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
performance testing of UNWIND kernel option
Hi, list. Today I noticed the following change in SHR: http://git.openembedded.org/cgit.cgi/openembedded/commit/?id=1516588acd3c4b4dd4add71d06ab8ce0d1bafa02 (by Denis 'GNUtoo' Carikli ) and decided to lmbench it. Here are results: http://www.bsdmn.com/lmbench/unwind_summary.txt You can see comparison of: 34def -> kernel with CONFIG_FRAME_POINTER unwind -> kernel with CONFIG_ARM_UNWIND default -> for reference, old debugging kernel The unwind option provide clear benefit of 5%-10% in almost every area. Nice spot Denis! Gennady. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Freifunk@FreeRunner: OLSRD
Hi Vinc, Instead of compiling it over SHR can you try it over QTMoko or H1 if you have any of them flashed either in your NAND or in SDcard. Just try it once. Thanks Shamsul On Tue, Mar 8, 2011 at 2:46 PM, Vinc.be wrote: > Hello, > > I'm trying to use olsrd on my FreeRunner but I cannot compile it. When I > type "make", I get a error : > > src/unix/ifnet.c: In function 'chk_if_up': > src/unix/ifnet.c:551: error: 'tos' undeclared (first use in this function) > src/unix/ifnet.c:551: error: (Each undeclared identifier is reported only > once > src/unix/ifnet.c:551: error: for each function it appears in.) > make: *** [src/unix/ifnet.o] Error 1 > > > Complete log here : http://www.geosharing-project.org/logs/log_olsrd-1.txt > > Do you have an idea why I cannot compile it ? I'm using SHR on my > FreeRunner. > > Thanks a lot ! > > Vinc.be > > -- > View this message in context: > http://openmoko-public-mailinglists.1958.n2.nabble.com/Freifunk-FreeRunner-OLSRD-tp15412p6126189.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: Freifunk@FreeRunner: OLSRD
Hello, I'm trying to use olsrd on my FreeRunner but I cannot compile it. When I type "make", I get a error : src/unix/ifnet.c: In function 'chk_if_up': src/unix/ifnet.c:551: error: 'tos' undeclared (first use in this function) src/unix/ifnet.c:551: error: (Each undeclared identifier is reported only once src/unix/ifnet.c:551: error: for each function it appears in.) make: *** [src/unix/ifnet.o] Error 1 Complete log here : http://www.geosharing-project.org/logs/log_olsrd-1.txt Do you have an idea why I cannot compile it ? I'm using SHR on my FreeRunner. Thanks a lot ! Vinc.be -- View this message in context: http://openmoko-public-mailinglists.1958.n2.nabble.com/Freifunk-FreeRunner-OLSRD-tp15412p6126189.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
[qtmoko33] usb storage issue and kernel panic (was Re: qtmoko v33)
On Fri, Mar 4, 2011 at 10:16 PM, Alfa21 wrote:
>> * fixed usb mass storage script
>
> I like the added logic to use the whole sdcard or a specific partition!
>
> btw why in fstab you consider swap on p4? is there any doc about use of p3 in
> qtmoko?
> (I usually set uSD's p1 as storage, p2 as rootfs, p3 as swap)
>
> ah, about fs type... do you consider for future releases using btrfs or ext4?
> I know they have optimizations for flash memory kind of storage.
hi radek,
I modified the last line in "on" script like:
#modprobe g_file_storage file=${DEV_NAME} stall=0
modprobe g_file_storage file=${DEV_NAME} stall=0 removable=y
this because otherwise (at least with a specific single partition
scenario) the usb drive is not usable with windows.
with linux and my home tv-set and home theater is always accessible,
with or without the "removable=y" directive.
this change just add the compatibility with windows OS (tested on winXP).
btw, both now and before, I get kernel panic changing usb mode back
and forth storage/ethernet more than twice... :(
I'm not able to tell more on this issue because on reboot do not see
anything interesting inside logs :S
regards
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
[qtmoko] email client bug with multipart/mixed
I think qtmoko's email client program does not support mixed multipart. when I receive an email of that kind i see: Name 0 multipart/alternative Type multipart/alternative No viewer available no problem with multipart/alternative kind of email. you can see pasted below selected email headers of booth OK and NOT_OK kind of emails. Content-Type: multipart/alternative; boundary="Boundary-01=_5xhdN/yWqqx2+tj" Content-Transfer-Encoding: 7bit Message-Id: <201103081309.29361.cyberesp...@cyberesprit.fr> --Boundary-01=_5xhdN/yWqqx2+tj Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Type: multipart/mixed; boundary="===0406204840==" Sender: community-boun...@lists.openmoko.org Errors-To: community-boun...@lists.openmoko.org --===0406204840== Content-Type: multipart/alternative; boundary="Boundary-01=_uufdNynmOmBH6MN" Content-Transfer-Encoding: 7bit --Boundary-01=_uufdNynmOmBH6MN Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
GPRS and QTMoko
If I boot my freerunner up from a cold boot and manually start GPRS it works fine. But if I am idle too long on GPRS it seems to stop working, Aurora wont be able to connect and my email will stop checking. Regardless of whether or not it is set to "On Demand" or not. WiFi does not seem to have this issue. Any suggestions? -- Wes Frazier "Nationalism is an infantile disease. It is the measles of mankind." - Albert Einstein ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [cutemaze] on [qtmoko 33] howto control moves?
2011/3/8 Radek Polak > These games can be controlled with keyboard only (probably). It would be > nice > if someone made patch for accels/touchscreen. > > Regards > > Radek > It would be nice! By the way, how can I bring up keyboard in the game ? There's no option... Thanks! -- Marco aka Delian # On IRC freenode my nickname is: /marco -- "I would love to change the world, but they won't give me the source code" -- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [cutemaze] on [qtmoko 33] howto control moves?
On Monday 07 March 2011 20:05:42 Alfa21 wrote: > hi, > I've installed cutemaze on my qtmoko33 from the apps web page. > > someone can explain me how to control my direction in the game, pls? > > what's the binding of up/down/left/right/space? > ...no touchscreen, no accelerometers... > > tia! These games can be controlled with keyboard only (probably). It would be nice if someone made patch for accels/touchscreen. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: messages through background [was Re: qtmoko v33]
On Monday 07 March 2011 19:46:01 Alfa21 wrote: > again on this topic: I can see painted over the background image "^@" for > each time I press the AUX button This is because commented out lines with getty in /dev/inittab. It can be fixed with command: stty -F /dev/tty1 -echo I'll add it to qtmoko init script. Regards Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Faenqo theme] date/time
And time alone in the bar with only the date on the main page? Le mardi 08 mars 2011 12:56:30, Alfa21-mobile a écrit : > I'm sorry for the name error (I've just copy/pasted it from the apps page) > > about the theme, personally, I'd like the both small and big (huge) > clock solution in the two positions. > they should be both visible also when the lock and key are showed on > screen... maybe lateral place or vertical if possible. > > kind regards and good work. > > On Tue, Mar 8, 2011 at 10:49 AM, cyberesprit wrote: > > Hello! > > > > Thanks Joif for your help ^^ > > > >> Well, it could be an interesting idea to have a date/time indicator that > >> > >> appears in the titlebar only when you are not at the homescreen. > > > > Excellent ! > > > > If I removed the date and time, it is because I found it unnecessary to > > see all the time .. but you're not alone in asking this question. > > > > In some applications, the time may be obscured by the widget that lets > > you change keyboard. > > > > Now, if the possibility of giving the choice to the user in configuring > > the theme would be possible .. it would be great > > > > Volunteers? ^^ > > > > Le mardi 08 mars 2011 09:57:48, Francesco De Vita a écrit : > >> Hi! > >> > >> He is cyberesprit not cyberspirit ;) About the position of the date/time > >> > >> it is possibile to move it near the carghe indicator. But because we > >> > >> have much space in the homescreen, do you prefer to have the date/time > >> > >> indicator only in the titlebar (in the top) or to have it also in the > >> > >> homescreen (it is a redundancy, but a bigger date/time indicator here is > >> > >> easier to read)? > >> > >> Well, it could be an interesting idea to have a date/time indicator that > >> > >> appears in the titlebar only when you are not at the homescreen. > >> > >> > >> > >> Regards > >> > >> Joif > >> > >> > >> > >> ___ > >> > >> 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: [Faenqo theme] date/time
I'm sorry for the name error (I've just copy/pasted it from the apps page) about the theme, personally, I'd like the both small and big (huge) clock solution in the two positions. they should be both visible also when the lock and key are showed on screen... maybe lateral place or vertical if possible. kind regards and good work. On Tue, Mar 8, 2011 at 10:49 AM, cyberesprit wrote: > Hello! > > Thanks Joif for your help ^^ > >> Well, it could be an interesting idea to have a date/time indicator that > >> appears in the titlebar only when you are not at the homescreen. > > Excellent ! > > If I removed the date and time, it is because I found it unnecessary to see > all the time .. but you're not alone in asking this question. > > In some applications, the time may be obscured by the widget that lets you > change keyboard. > > Now, if the possibility of giving the choice to the user in configuring the > theme would be possible .. it would be great > > Volunteers? ^^ > > Le mardi 08 mars 2011 09:57:48, Francesco De Vita a écrit : > >> Hi! > >> He is cyberesprit not cyberspirit ;) About the position of the date/time > >> it is possibile to move it near the carghe indicator. But because we > >> have much space in the homescreen, do you prefer to have the date/time > >> indicator only in the titlebar (in the top) or to have it also in the > >> homescreen (it is a redundancy, but a bigger date/time indicator here is > >> easier to read)? > >> Well, it could be an interesting idea to have a date/time indicator that > >> appears in the titlebar only when you are not at the homescreen. > >> > >> Regards > >> Joif > >> > >> ___ > >> 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: [Faenqo theme] date/time
Hello! Thanks Joif for your help ^^ > Well, it could be an interesting idea to have a date/time indicator that > appears in the titlebar only when you are not at the homescreen. Excellent ! If I removed the date and time, it is because I found it unnecessary to see all the time .. but you're not alone in asking this question. In some applications, the time may be obscured by the widget that lets you change keyboard. Now, if the possibility of giving the choice to the user in configuring the theme would be possible .. it would be great Volunteers? ^^ Le mardi 08 mars 2011 09:57:48, Francesco De Vita a écrit : > Hi! > He is cyberesprit not cyberspirit ;) About the position of the date/time > it is possibile to move it near the carghe indicator. But because we > have much space in the homescreen, do you prefer to have the date/time > indicator only in the titlebar (in the top) or to have it also in the > homescreen (it is a redundancy, but a bigger date/time indicator here is > easier to read)? > Well, it could be an interesting idea to have a date/time indicator that > appears in the titlebar only when you are not at the homescreen. > > Regards > Joif > > ___ > 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] faenqomod updated
On Monday 07 March 2011 19:43:52 Tiago Bortoletto Vaz wrote: > Great! Please one more: > > http://tiagovaz.org/archive/0001-Faenqo-add-DebianGold-background.patch > > This add that nice Debian gold background now adjusted to not remain behind > the main screen icons. Also converted to jpg. > > Upstream, please merge! :) Done, thanks! Radek ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Faenqo theme] date/time
Hi! He is cyberesprit not cyberspirit ;) About the position of the date/time it is possibile to move it near the carghe indicator. But because we have much space in the homescreen, do you prefer to have the date/time indicator only in the titlebar (in the top) or to have it also in the homescreen (it is a redundancy, but a bigger date/time indicator here is easier to read)? Well, it could be an interesting idea to have a date/time indicator that appears in the titlebar only when you are not at the homescreen. Regards Joif ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
