Re: [Debian -FSO -GPS] No Fix
Daniel asked for a _complete_ log just 3 hours after the initial bug report (Ticket #265). But no answer until now... well, i assumed, the op would have provided one. anyway. i did a grep ogpsd over my frameworkd.log (almost 100.000 lines since 2008.11.29 00:07:12) and there still are about 40.000 lines -- i cannot check them all for maybe private information (should be none, but who knows), so i won't attach it publicly viewable. shall send it to you as pm? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Optimization team update (11/23 ~ 11/29)
Dear Community, As Sushama (our new testing team member) indicated in http://lists.openmoko.org/pipermail/devel/2008-November/003493.html , we won't have a release in Nov. Currently the testing team is going to do a full test on the latest testing image. It has all the goodies we did and a lot of improvements over Om2008.9, so please try it and report any error you find. Upgrade howto: From Om2008.9 it's recommanded to upgrade with the following steps: sed -i -e 's%Om2008.8%testing%' /etc/opkg/*.conf /etc/init.d/xserver-nodm stop screen -DR opkg update opkg -force-overwrite upgrade # (please ans Y to all questions) # (the sshd (dropbear) will restart, so you need to reconnect and do # 'screen -DR' again) opkg upgrade shutdown -r now To get the fastest boot time you also need to remove the following packages: opkg remove task-base-nfs task-base-smbfs task-base-bluetooth \ task-base-usbgadget avahi-daemon avahi-autoipd blueprobe \ usb-gadget-mode portmap exquisite exquisite-theme-freerunner \ exquisite-themes Known issues: * GTK redraw problem * some obsolete kernel modules still left in system * must remove 'ro' in kernel boot parameter if you use sd boot. * will purge your incompatible e config, so you might need to set stuffs like suspend time again. Echo: Since there are different hw versions out there (a5, a6, a7), it's impossible to provide one alsa state file that suits all models. However, it seems you can always find appropriate values for your neo. My way is to adjust control.4 Speaker Playback Volume in /usr/share/openmoko/scenarios/gsmhandset.state the max value is 127, 95 works best on my a5. With volume level 3 or 4 in qtopia dialer, the other side can hear no echo while I get good audio quality. Team update: Tick helped to put his touchscreen improvement into stable-tracking, he will work on opkg internals next. Olv moved to look into kernel and fso. Erin will try bluetooth. Julian is working on the GTK redraw issue, please help him out. Jeremy will fix some qtopia bugs and keep working on suspend/resume issues. Regards, John ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
great news, but can't the opkg upgrade detect which hw revision we have and install the best alsa state file? afterall, good call quality is something almost everybody wants y On Sun, Nov 30, 2008 at 12:50 PM, John Lee [EMAIL PROTECTED] wrote: Dear Community, As Sushama (our new testing team member) indicated in http://lists.openmoko.org/pipermail/devel/2008-November/003493.html , we won't have a release in Nov. Currently the testing team is going to do a full test on the latest testing image. It has all the goodies we did and a lot of improvements over Om2008.9, so please try it and report any error you find. Upgrade howto: From Om2008.9 it's recommanded to upgrade with the following steps: sed -i -e 's%Om2008.8%testing%' /etc/opkg/*.conf /etc/init.d/xserver-nodm stop screen -DR opkg update opkg -force-overwrite upgrade # (please ans Y to all questions) # (the sshd (dropbear) will restart, so you need to reconnect and do # 'screen -DR' again) opkg upgrade shutdown -r now To get the fastest boot time you also need to remove the following packages: opkg remove task-base-nfs task-base-smbfs task-base-bluetooth \ task-base-usbgadget avahi-daemon avahi-autoipd blueprobe \ usb-gadget-mode portmap exquisite exquisite-theme-freerunner \ exquisite-themes Known issues: * GTK redraw problem * some obsolete kernel modules still left in system * must remove 'ro' in kernel boot parameter if you use sd boot. * will purge your incompatible e config, so you might need to set stuffs like suspend time again. Echo: Since there are different hw versions out there (a5, a6, a7), it's impossible to provide one alsa state file that suits all models. However, it seems you can always find appropriate values for your neo. My way is to adjust control.4 Speaker Playback Volume in /usr/share/openmoko/scenarios/gsmhandset.state the max value is 127, 95 works best on my a5. With volume level 3 or 4 in qtopia dialer, the other side can hear no echo while I get good audio quality. Team update: Tick helped to put his touchscreen improvement into stable-tracking, he will work on opkg internals next. Olv moved to look into kernel and fso. Erin will try bluetooth. Julian is working on the GTK redraw issue, please help him out. Jeremy will fix some qtopia bugs and keep working on suspend/resume issues. Regards, John ___ 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: Optimization team update (11/23 ~ 11/29)
Or one could create a statefiles-metapackage and make the user choose his model upon installation - or do this in package setup/configuration scripts... -- Marcel Am Sunday 30 November 2008 13:01:47 schrieb Yorick Moko: great news, but can't the opkg upgrade detect which hw revision we have and install the best alsa state file? afterall, good call quality is something almost everybody wants y On Sun, Nov 30, 2008 at 12:50 PM, John Lee [EMAIL PROTECTED] wrote: Dear Community, As Sushama (our new testing team member) indicated in http://lists.openmoko.org/pipermail/devel/2008-November/003493.html , we won't have a release in Nov. Currently the testing team is going to do a full test on the latest testing image. It has all the goodies we did and a lot of improvements over Om2008.9, so please try it and report any error you find. Upgrade howto: From Om2008.9 it's recommanded to upgrade with the following steps: sed -i -e 's%Om2008.8%testing%' /etc/opkg/*.conf /etc/init.d/xserver-nodm stop screen -DR opkg update opkg -force-overwrite upgrade # (please ans Y to all questions) # (the sshd (dropbear) will restart, so you need to reconnect and do # 'screen -DR' again) opkg upgrade shutdown -r now To get the fastest boot time you also need to remove the following packages: opkg remove task-base-nfs task-base-smbfs task-base-bluetooth \ task-base-usbgadget avahi-daemon avahi-autoipd blueprobe \ usb-gadget-mode portmap exquisite exquisite-theme-freerunner \ exquisite-themes Known issues: * GTK redraw problem * some obsolete kernel modules still left in system * must remove 'ro' in kernel boot parameter if you use sd boot. * will purge your incompatible e config, so you might need to set stuffs like suspend time again. Echo: Since there are different hw versions out there (a5, a6, a7), it's impossible to provide one alsa state file that suits all models. However, it seems you can always find appropriate values for your neo. My way is to adjust control.4 Speaker Playback Volume in /usr/share/openmoko/scenarios/gsmhandset.state the max value is 127, 95 works best on my a5. With volume level 3 or 4 in qtopia dialer, the other side can hear no echo while I get good audio quality. Team update: Tick helped to put his touchscreen improvement into stable-tracking, he will work on opkg internals next. Olv moved to look into kernel and fso. Erin will try bluetooth. Julian is working on the GTK redraw issue, please help him out. Jeremy will fix some qtopia bugs and keep working on suspend/resume issues. Regards, John ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [GENTOO] updates?
2008/11/24 Nicola Mfb [EMAIL PROTECTED]: Are there some news about gentoo for freerunner? There is a project on http://projects.openmoko.org/projects/gentoo to provide a cross-compilable overlay for the Freerunner. So if you are interested you can try this one (we always need testers ;-)). Best regards, Sven ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [GENTOO] updates?
On Mon, Nov 24, 2008 at 18:19, Nicola Mfb [EMAIL PROTECTED] wrote: Hi! Are there some news about gentoo for freerunner? It would be nice if mantainers would produce a ready to go stage4 tarball for fast and simple deploying. The underlying software is working (cross-compiler, libc, busybox, ssh, even python, X and gtk), now we need ebuilds for phone parts. (see http://lists.projects.openmoko.org/pipermail/gentoo-devel/2008-November/40.html ) -- Damien Thebault ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian] TSLIB_TSDEVICE no longer getting set
Hi, Am Sonntag, den 30.11.2008, 02:09 + schrieb Christopher J. White: AFAIR, it is not necessary anymore to set this variable, if /etc/X11/xorg.conf and/or the udev rules are set up correctly – did you by any chance modify that? I was running Xglamo at the time, so I had modified xorg.conf to point to Xglamo as the display device. I thought Xglamo does not need any xorg.conf? But maybe that’s just rumors. However, something happened that screwed that up, both for Xglamo as well as fbdev. Right now neither will work. In fact, it's rather strange. If I start xinit manually after setting TSLIB_TSDEVICE, it works: $ export TSLIB_TSDEVICE=/dev/input/event1 $ /usr/bin/xinit /etc/X11/Xsession However, when I run it in a fashion similar to /etc/init.d/nodm, it fails: $ /bin/su --login --command /usr/bin/xinit /etc/X11/Xsession root This is despite putting the export command in .bashrc and verifying that it's set. I even tried verifying that it was getting TSLIB_TSDEVICE: $ /bin/su --login --command printenv root [...] TSLIB_TSDEVICE=/dev/input/event1 However, it still fails to work. I removed and then reinstalled xserver-xglamo, and the error messages changed, but it still does not work. This is the original xorg.conf, as installed by the install.sh script: # Xorg confiugration for an Openmoko FreeRunner Section InputDevice Identifier Configured Touchscreen Driver tslib Option CorePointer true Option SendCoreEventstrue Option TslibDevice /dev/input/event1 Option Protocol Auto Option Width 480 Option Height640 EndSection Section Device Identifier Configured Video Device Driver fbdev EndSection You still have problems with that file? Anything interesting in the X log file? Greetings, Joachim -- Joachim nomeata Breitner Debian Developer [EMAIL PROTECTED] | ICQ# 74513189 | GPG-Keyid: 4743206C JID: [EMAIL PROTECTED] | http://people.debian.org/~nomeata signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
On Sun, 30 Nov 2008 19:50:22 +0800 John Lee [EMAIL PROTECTED] wrote: Echo: Since there are different hw versions out there (a5, a6, a7), it's impossible to provide one alsa state file that suits all models. However, it seems you can always find appropriate values for your neo. My way is to adjust control.4 Speaker Playback Volume in /usr/share/openmoko/scenarios/gsmhandset.state the max value is 127, 95 works best on my a5. With volume level 3 or 4 in qtopia dialer, the other side can hear no echo while I get good audio quality. Does this mean the fix is only through alsa? So the fix mentioned here: http://n2.nabble.com/FSO-M4---nice-GSM-sound-tp1486414p1518726.html is not ok? Since that fix is the only real fix for my echo issues (and it seems to come from 2008.8). Franky ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: A light for the Freerunner
Hello William, that sounds great :D Perhaps you find more ideas on this wiki-page about alternate cases = http://wiki.openmoko.org/wiki/Wish_List_-_Hardware#Casing with kind regards Patrick Am Sonntag, den 30.11.2008, 11:15 +0900 schrieb William Kenworthy: Yes, they are brighter. I am actually thinking of using your idea, but adding an extension and small camera so the light can be used in confined areas with the FR as the screen. When I get the time ... BillK On Sat, 2008-11-29 at 14:09 +0100, Patrick Beck wrote: Hello, it's not comparable to this solution ;) This two leds are twice or more brighter than the display. with kind regards Patrick Am Samstag, den 29.11.2008, 12:42 +0900 schrieb William Kenworthy: I use flashlight - turns the screen backlight up to max. Touch to turn off ( return screen to previous setting). Its actually quite bright and useful, and no soldering involved. BillK On Fri, 2008-11-28 at 22:56 +0100, Patrick Beck wrote: Hello, because i like my light on my older phone, a Sony Ericsson W800i, i added a light on the miniusb - connector. Perhaps anybody like it or has any improvements for me :D Here you can find a wiki article about the light http://yourse.de/wiki/doku.php?id=openmoko:usb_light And here two videos http://www.youtube.com/watch?v=iK5w-OHSm9g http://www.youtube.com/watch?v=f2H4QZq2xxE It was a proof-of-concept and it works! Perhaps Openmoko likes the idea and adds a light directly into the case in the next generation of devices :) At least manufacutring at one's own risk ;) Have fun! with kind regards Patrick Beck ___ 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 signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
On Sun, Nov 30, 2008 at 07:50:22PM +0800, John Lee wrote: Echo: Since there are different hw versions out there (a5, a6, a7), it's impossible to provide one alsa state file that suits all models. However, it seems you can always find appropriate values for your neo. My way is to adjust control.4 Speaker Playback Volume in /usr/share/openmoko/scenarios/gsmhandset.state the max value is 127, 95 works best on my a5. With volume level 3 or 4 in qtopia dialer, the other side can hear no echo while I get good audio quality. This is interesting, I have an a5 and the default value of FSO M4.1a: control.4 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 127' iface MIXER name 'Speaker Playback Volume' value.0 116 value.1 116 } Sometimes I ask people on the other side: do you hear echo? The answer has been no. Rui -- Hail Eris, Hack GNU/Linux! Today is Prickle-Prickle, the 42nd day of The Aftermath in the YOLD 3174 + No matter how much you do, you never do enough -- unknown + Whatever you do will be insignificant, | but it is very important that you do it -- Gandhi + So let's do it...? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
SD boot freeze, hang at boot time, why ?
Hello, Sometimes my GTA02 freeze at boot time on the SD card, and I should remove the battery to shutdown the phone. It freeze sometimes on the OpenMoko SPLASH screen, no error message except the, beautiful, splash ! The screen is freezed on, when SD booting : freeze Card Type: SD 2.0 SDHC Manufacturer: 0x02, OEM TM Product name: SDG08G, revision 3.8 Serial number: 3282648718 Manufacturing date: 7/2008 MMC/SD size:3MiB reading uImage.bin 1760128 bytes read ## Booting kernel from Legacy Image at 3200 ... Image Name: Debian FreeRunner Kernel Created:2008-11-13 0:18:20 UTC Image Type: ARM Linux Kernel Image (uncompressed) Data Size: 1760064 Bytes = 1.7 MB Load Address: 30008000 Entry Point:30008000 Verifying Checksum ... OK Loading Kernel Image ... OK OK Starting kernel ... /freeze Someone can tell me what's happening ? Or give me any clues to repair that, and a place to report the bug. Regards, Maelvon ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
ALSA state ringtone volume
Hi all, Does anybody knows which alsa statefile, and which control should I edit to raise/lower the volume of the ringtone when receiving gsm calls? thanks, leonardo. -- http://leonardo.lilik.it Key fingerprint = 2C20 A587 05AC 42E5 1292 D0D4 3EED CFB5 52FD AD1E ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Audio format
What would be a convenient place to store ringtones in such a way that selecting a new one can be done from the same directory as the default ringtones without changing to exotic paths? I'm looking for a 'home' for ringtones, notifications, etc. and for alternative places where they could be expected and link from there to the ringtone home. For example, store the ringtones somewhere here: /opt/Qtopia/etc/SystemRingTones/custom.ogg ... /opt/Qtopia/etc/SystemRingTones/alarm.wav /opt/Qtopia/etc/SystemRingTones/phonering.wav /opt/Qtopia/sounds/alarm.wav And from here links (in FDOM) to the new ringtones so that in this case linphone can also access them /usr/share/sounds/linphone/rings/custom.ogg - /opt/Qtopia/etc/SystemRingTones/custom.ogg ... /usr/share/sounds/linphone/rings/oldphone.wav /usr/share/sounds/linphone/rings/synth.wav /usr/share/sounds/linphone/rings/bigben.wav /usr/share/sounds/linphone/rings/toy.wav /usr/share/sounds/linphone/rings/sweet.wav /usr/share/sounds/linphone/rings/rock.wav /usr/share/sounds/linphone/rings/tapping.wav /usr/share/sounds/linphone/rings/orig.wav /usr/share/sounds/linphone/ringback.wav Who can give some advice in this matter? Thanks, Pander Leonti Bielski wrote: I would recommend ogg too. I'm was using ogg file as my ringtone without any problems. Not sure about your distribution... Leonti On Sat, Nov 29, 2008 at 5:29 PM, Pander [EMAIL PROTECTED] wrote: Hi all, What is the best audio format for offering ringtones, notifications, etc.? I'd prefer .ogg because of its easy license and small file size. The .wav and .mp3 I'd shun for these reasons. Is this correct and is the phone capable of using .ogg as ringtones and notifications in both the OM part and the Qt part. Thanks, Pander ___ 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: [Debian] TSLIB_TSDEVICE no longer getting set
On Sun, 2008-11-30 at 14:14 +0100, Joachim Breitner wrote: Hi, Am Sonntag, den 30.11.2008, 02:09 + schrieb Christopher J. White: AFAIR, it is not necessary anymore to set this variable, if /etc/X11/xorg.conf and/or the udev rules are set up correctly – did you by any chance modify that? I was running Xglamo at the time, so I had modified xorg.conf to point to Xglamo as the display device. I thought Xglamo does not need any xorg.conf? But maybe that’s just rumors. I had to change the Section Device, Driver fbdev to Driver Xglamo to make the switch to Xglamo, but I have also heard that Xglamo ignores other config options, such as the TslibDevice option. Supposedly Xglamo is hardcoded to use TSLIB_TSDEVICE. This is the original xorg.conf, as installed by the install.sh script: # Xorg confiugration for an Openmoko FreeRunner Section InputDevice Identifier Configured Touchscreen Driver tslib Option CorePointer true Option SendCoreEventstrue Option TslibDevice /dev/input/event1 Option Protocol Auto Option Width 480 Option Height640 EndSection Section Device Identifier Configured Video Device Driver fbdev EndSection Yes, this is what my xorg.conf currently looks like, and no luck. Running just /usr/bin/xinit or /usr/bin/startx as root, I get: X.Org X Server 1.4.2 Release Date: 11 June 2008 X Protocol Version 11, Revision 0 Build Operating System: Linux Debian (xorg-server 2:1.4.2-9) Current Operating System: Linux debian-gta02 2.6.24-20081103.git7172ec57 #1 PREEMPT Wed Nov 12 23:54:02 UTC 2008 armv4tl Build Date: 18 November 2008 01:48:08PM Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Sun Nov 30 09:17:54 2008 (==) Using config file: /etc/X11/xorg.conf No raw modules loaded. ts_config failed (EE) PreInit returned NULL for Configured Touchscreen using tslib [config/hal] couldn't initialise context: (null) ((null)) X starts up, but no pointer action. So...I took the next step and started defining all the TSLIB variables: $ export TSLIB_TSDEVICE=/dev/input/event1 $ export TSLIB_CONFFILE=/etc/ts.conf $ /usr/bin/xinit [] (==) Log file: /var/log/Xorg.0.log, Time: Sun Nov 30 09:30:47 2008 (==) Using config file: /etc/X11/xorg.conf xf86TslibControlProc xf86TslibControlProc [config/hal] couldn't initialise context: (null) ((null)) And *now* I get successful pointer action. Now that I figured this out, I can put those two exports into my .bashrc for root, but the same trick for my normal user doesn't work. Trying to start xinit or startx manually gives permission errors on /var/log/Xorg.log.0. So this tells me something changed that used to set the TSLIB vars before starting Xserver. Can you grep for TSLIB for all files in /etc/X11 and below and see if you see it there anywhere? ...cj ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
German dictionary for Raster's keyboard with frequencies?
Moin! I just found out that the wordlist needs to have a .dic file extension to get recognized by Raster's keyboard - now it dicts quite well, except that some often used (internet) slang words are missing... Has anyone got a german word list with word frequencies yet? The one I got (debian package wngerman, /usr/share/dicts/ngerman) only has the words, but no frequencies which makes finding the right word difficult sometimes, especially I can't get the wordlist on the keyboard to scroll (is this even implemented?) without selecting a word accidentally. Another suggestion to Raster: I think it would be useful to have the whole word getting deleted on backspace while one has a language dictionary activated (in contrast to a terminal/programming one) because mostly the whole word gets wrong instead of just some single characters. -- Marcel ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian] TSLIB_TSDEVICE no longer getting set
On Sun, 2008-11-30 at 15:23 +, Christopher J. White wrote: Now that I figured this out, I can put those two exports into my .bashrc for root, but the same trick for my normal user doesn't work. Trying to start xinit or startx manually gives permission errors on /var/log/Xorg.log.0. Doh...this was due to reinstalling the Xorg server (just in case) and I needed to make /usr/bin/Xorg suid. So this tells me something changed that used to set the TSLIB vars before starting Xserver. Can you grep for TSLIB for all files in /etc/X11 and below and see if you see it there anywhere? Putting TSLIB vars in the per-user .bashrc gets the pointer working for both root and my standard user, so I can move forward, but it's still very strange. ...cj ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: German dictionary for Raster's keyboard with frequencies?
In the Netherlands you have http://opentaal.org, that is where I got the information for the Dutch dictionary which will be released real soon. Perhaps a german speaking country has a similar organisation that has this data from harvesting documents and compiling an extensive word list. Marcel wrote: Moin! I just found out that the wordlist needs to have a .dic file extension to get recognized by Raster's keyboard - now it dicts quite well, except that some often used (internet) slang words are missing... Has anyone got a german word list with word frequencies yet? The one I got (debian package wngerman, /usr/share/dicts/ngerman) only has the words, but no frequencies which makes finding the right word difficult sometimes, especially I can't get the wordlist on the keyboard to scroll (is this even implemented?) without selecting a word accidentally. Another suggestion to Raster: I think it would be useful to have the whole word getting deleted on backspace while one has a language dictionary activated (in contrast to a terminal/programming one) because mostly the whole word gets wrong instead of just some single characters. -- Marcel ___ 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: us network and Uuntu 8.10 - is there a better way?
On Sat, Nov 29, 2008 at 3:26 PM, Torfinn Ingolfsen [EMAIL PROTECTED] wrote: On Tue, Nov 25, 2008 at 10:33 PM, Torfinn Ingolfsen [EMAIL PROTECTED] wrote: For now, I'm back to the manual method. Today there were (X)ubuntu updates for NetworkManager and more. After these updates (which included a necessary restart), even the manual method doesn't work anymore. [EMAIL PROTECTED]:~$ ifconfig usb0 usb0 Link encap:Ethernet HWaddr 12:ed:86:b0:6c:4c inet6 addr: fe80::10ed:86ff:feb0:6c4c/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:936 (936.0 B) [EMAIL PROTECTED]:~$ sudo ifconfig usb0 down [sudo] password for tingo: [EMAIL PROTECTED]:~$ ifconfig usb0 usb0 Link encap:Ethernet HWaddr 12:ed:86:b0:6c:4c BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:12 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:936 (936.0 B) [EMAIL PROTECTED]:~$ sudo ifconfig usb0 up [EMAIL PROTECTED]:~$ ifconfig usb0 usb0 Link encap:Ethernet HWaddr 12:ed:86:b0:6c:4c inet6 addr: fe80::10ed:86ff:feb0:6c4c/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:15 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:1174 (1.1 KB) What is wrong here? What you've shown is a correct operation as far as I can see. May be you wanted ifup/ifdown instead of ifconfig up/ifconfig down? Former are scripts which parse interfaces file and setup things as described, while latter are simple commands to bring interface up/down. PS And consider using ip addr and friends instead of venerable ifconfig. ip command is newer way of operating network interfaces. -- Regards, Alexander Chemeris. SIPez LLC. SIP VoIP, IM and Presence Consulting http://www.SIPez.com tel: +1 (617) 273-4000 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD boot freeze, hang at boot time, why ?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Starting kernel ... | /freeze | | Someone can tell me what's happening ? Or give me any clues to repair | that, and a place to report the bug. Best thing is figure out if it's a kernel issue or just userspace... fiddle with your U-Boot env to add console=tty0 loglevel=8 on the kernel commandline, then you should see the whole boot process fly by up to userspace starting. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkky35QACgkQOjLpvpq7dMoSBACgjA3y2mpXn8HFHmQExqonu6V1 x7kAn2lAyFIdu5xBi9H3PI33t0T5lr9q =JZeN -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: Hi John - | * some obsolete kernel modules still left in system If we didn't do it already, the packaged kernels need to move to having /lib/modules path that is specific to the kernel device and build, similar to what the ./build script does: /lib/modules/2.6.28-GTA02_andy-tracking_d0aa5acc0be7c573-mokodev/ The branch and hash stops any conflict about module versions, and the device tag GTA02 allows multiple kernels to be installed on the same rootfs, so you can share the SD Card between GTA01 and GTA02 say, both times with SD Card boot to the right kernel. | * must remove 'ro' in kernel boot parameter if you use sd boot. At the moment Qi has ro boot everywhere by default, is this restriction just a temporary workaround for something? | he will work on opkg internals next. Olv moved to look into kernel | and fso. Erin will try bluetooth. Julian is working on the GTK | redraw issue, please help him out. Jeremy will fix some qtopia bugs | and keep working on suspend/resume issues. Just a thought, it can be worth Olv and Jeremy bouncing what they're planning on doing off the kernel list. For example some advice for Jeremy about suspend / resume issues would be don't waste your time doing any suspend / resume work on 2.6.24 kernel, only on andy-tracking. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkky4dwACgkQOjLpvpq7dMrSTACeNaM2tQ5kn+rvzlTJC0nD5N5L s8wAnAn/GDMCXyBN8ODnY2sq5XhheRn/ =/Ytn -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
GTK Redraw Issues (was: Optimization team update (11/23 ~ 11/29))
John Lee [EMAIL PROTECTED] wrote: Julian is working on the GTK redraw issue, please help him out. Be sure to see my previous analysis sent upstream: http://bugzilla.gnome.org/show_bug.cgi?id=561591 The problem arises because gtk_window_move_resize() temporarily freezes redraws on the assmption that gtk_window_configure_event() will be called shortly afterwards, but this never happens. It could be that the expected configure_event is actually happening _before_ the move_resize, but I don't know what the expected order is. In fact, I think it might not even required to be in any particular order. I think this arises from an interaction of the specific way Enlightenment manages things combined with the assumption mentioned above. This would also explain why running GTK programs on Neo via X forwarding works for me (with xfwm4 on my laptop). It also explains what someone described to me on IRC: that with Debian the same problems appeared only after changing WM to Enlightenment. They were going to add a comment to the ticket, but don't seem to have done so yet. Tom ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
Hi, Andy Green [EMAIL PROTECTED] writes: For example some advice for Jeremy about suspend / resume issues would be don't waste your time doing any suspend / resume work on 2.6.24 kernel, only on andy-tracking. I'm very sorry to jump in this thread. But this advice of yours is so much surprising! It implicitly suggests that Jeremy might be unaware of the fact that every sane person knows for like 2 months. Do i understand it right? How can it be possible at all? Everybody's so excited about this Optimization team and you say they might waste some time just because they don't lurk on -kernel mailing list? No offence meant, but that is sooo strange... -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:[EMAIL PROTECTED] ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD boot freeze, hang at boot time, why ?
Am Sonntag, den 30.11.2008, 18:46 + schrieb Andy Green: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Starting kernel ... | /freeze | | Someone can tell me what's happening ? Or give me any clues to repair | that, and a place to report the bug. Best thing is figure out if it's a kernel issue or just userspace... fiddle with your U-Boot env to add console=tty0 loglevel=8 on the Maelvon, I had a similar issue with a 16GB card. Resolution was to add some sleep(1) time before mmcinit is called. Works fine after after adding 2 seconds of sleep. See: http://wiki.openmoko.org/wiki/SanDisk/SDSDQ-016G-E11M and reference to original post: http://lists.openmoko.org/pipermail/community/2008-November/035412.html HTH, Marian ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Hi, | | Andy Green [EMAIL PROTECTED] writes: | For example some advice for Jeremy about suspend / resume issues | would be don't waste your time doing any suspend / resume work on | 2.6.24 kernel, only on andy-tracking. | | I'm very sorry to jump in this thread. But this advice of yours is | so much surprising! It implicitly suggests that Jeremy might be unaware of | the fact that every sane person knows for like 2 months. Do i Every sane person :-) No a lot of people are still using 2.6.24, all the distros are shipping it, it is in a branch called stable, it's not nuts if somebody tries to work on it. But there are multiple known issues with suspend / resume solved on 2.6.28 stuff and for sure unless they are solved first debugging suspend resume will be exercise in chasing one's tail. If he already knows it then fine, but people have been targeting stable in the last weeks for stuff that needs to be done on 2.6.28. | understand it right? How can it be possible at all? Everybody's so | excited about this Optimization team and you say they might | waste some time just because they don't lurk on -kernel mailing list? | | No offence meant, but that is sooo strange... I fear I've missed your point... John Lee wrote that two folks in Taiwan are going to be working specifically on kernel stuff... ''Olv moved to look into kernel and fso. ... Jeremy will fix some qtopia bugs and keep working on suspend/resume issues.'' I write to suggest they might get advantage if they coordinate kernel work on the kernel list -- at least we might not duplicate work on the same thing and there is a pretty fair amount of knowledge about Openmoko suspend / resume stuff on that list. What's sooo strange about that? - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkky+doACgkQOjLpvpq7dMo4GQCfSRrSFPE8WSACxUIgaXrBBzn6 C8wAn3nEoVN9VPjEMd9zQ2mukdo2D666 =1qaJ -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Survey about the Touchscreen
2008/11/22 Anton Persson [EMAIL PROTECTED]: it would be interesting to know which type of touch-screen that people would prefer to use on their future OpenMoko device. A not so scientific survey can be found at: http://www.733kru.org/~pltxtra/OpenMoko/survey.html is it possible to source a screen that has both capacitive and pressure interfaces? this way we (may) get best of both worlds or, is there any reason why one would clash with the other? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
Andy Green [EMAIL PROTECTED] writes: Somebody in the thread at some point said: | Hi, | | Andy Green [EMAIL PROTECTED] writes: | For example some advice for Jeremy about suspend / resume issues | would be don't waste your time doing any suspend / resume work on | 2.6.24 kernel, only on andy-tracking. | | I'm very sorry to jump in this thread. But this advice of yours is | so much surprising! It implicitly suggests that Jeremy might be unaware of | the fact that every sane person knows for like 2 months. Do i Every sane person :-) No a lot of people are still using 2.6.24, all the distros are shipping it, it is in a branch called stable, it's not nuts if somebody tries to work on it. A lot of people are using, sure. But all the real work is done on *-tracking, it was obvious long ago from the commits, from the discussions, from the letter you posted earlier with the clear explanation about every branch's purpose. If he already knows it then fine, but people have been targeting stable in the last weeks for stuff that needs to be done on 2.6.28. That is strange. If they read the kernel list, then they already know what's going known and where you're heading. If they don't, how can they do kernel development then? Out of the context, in isolation? Just like samsung with their huge outdated patchsets, that can never be accepted upstream and therefore can be considered being dead before they born? | understand it right? How can it be possible at all? Everybody's so | excited about this Optimization team and you say they might | waste some time just because they don't lurk on -kernel mailing list? | | No offence meant, but that is sooo strange... I fear I've missed your point... John Lee wrote that two folks in Taiwan are going to be working specifically on kernel stuff... ''Olv moved to look into kernel and fso. ... Jeremy will fix some qtopia bugs and keep working on suspend/resume issues.'' I write to suggest they might get advantage if they coordinate kernel work on the kernel list -- at least we might not duplicate work on the same thing and there is a pretty fair amount of knowledge about Openmoko suspend / resume stuff on that list. What's sooo strange about that? Oh, you seem to be repeating the same thing you said earlier just to explain to me what's going on. I'm sorry for wasting your time. I think i understand you. The problem is that i'm not a native speaker and i tend to construct too complex sentences even in my native language. What i'm trying to explain is that i see it as plain obvious that anybody who wants to work on a kernel stuff should coordinate their efforts on the kernel list. That anybody targeting fixing bugs in suspend/resume knows about 2.6.24 deficiences long time ago. What you said to Jeremy sounded to me like: Hey, don't cross the street on red light, you might get hit by a car and die, you know. I was surprised that you treat a kernel developer from the optimization team like a child. If he is not experienced in kernel development why then didn't he ask you what kind of help was needed and decided to choose a task himself? And why the optimization team is still trying to fix bugs in Qtopia and derivitaves? Let Nokia do their work, if they really want to. Wouldn't it be better for the optimization team to hack on FSO or at least (as they are in Taiwan, that should be easy for them) get those bloody 100uF capacitors in place to finally provide the users with a decent bass? I don't want to sound too harsh to the optimization team. I just don't see them being public enough, coordinating their efforts with the main developers (of FSO and kernel) enough, going forward enough. I'm just afraid that they are somewhat like that mythical interface design department that never publicly communicates and demands technical nonsense from the real developers. (btw, i still remember the idea of taking a screenshot before suspending, oh boy, that was a bad sign from the optimization team) No personal offense meant. -- Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software! mailto:[EMAIL PROTECTED] ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian] TSLIB_TSDEVICE no longer getting set
Hi, Am Sonntag, den 30.11.2008, 15:38 + schrieb Christopher J. White: So this tells me something changed that used to set the TSLIB vars before starting Xserver. Can you grep for TSLIB for all files in /etc/X11 and below and see if you see it there anywhere? Putting TSLIB vars in the per-user .bashrc gets the pointer working for both root and my standard user, so I can move forward, but it's still very strange. $ fgrep TSLIB -r /etc/ $ something’s very weird at your side. Greetings, Joachim -- Joachim nomeata Breitner Debian Developer [EMAIL PROTECTED] | ICQ# 74513189 | GPG-Keyid: 4743206C JID: [EMAIL PROTECTED] | http://people.debian.org/~nomeata signature.asc Description: Dies ist ein digital signierter Nachrichtenteil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | What i'm trying to explain is that i see it as plain obvious that | anybody who wants to work on a kernel stuff should coordinate their | efforts on the kernel list. That anybody targeting fixing bugs in The fact is I don't know what Olv and Jeremy are planning on doing in the kernel because it hasn't appeared on the kernel list or anywhere else for me. But that's all... I have no problem with their experience level and will be interested to see what they're coming up with, and if I can help. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkkzCCgACgkQOjLpvpq7dMpopQCeNgUq6HhK1UOpUG44b9ltDZkm OesAnihKj1eUuuJCCfozUU2kqDFJDxk5 =kUyy -END PGP SIGNATURE- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
On 30.11.2008 at 12:50:22, John Lee wrote: Since there are different hw versions out there (a5, a6, a7), it's impossible to provide one alsa state file that suits all models. Just a short question: What is a7? Can you please update the wiki article about the GTA02 revisions? -- Fabian ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: GTK Redraw Issues (was: Optimization team update (11/23 ~ 11/29))
On Sun, 30 Nov 2008 19:26:46 + Thomas White [EMAIL PROTECTED] babbled: John Lee [EMAIL PROTECTED] wrote: Julian is working on the GTK redraw issue, please help him out. Be sure to see my previous analysis sent upstream: http://bugzilla.gnome.org/show_bug.cgi?id=561591 The problem arises because gtk_window_move_resize() temporarily freezes redraws on the assmption that gtk_window_configure_event() will be called shortly afterwards, but this never happens. It could be that the expected configure_event is actually happening _before_ the move_resize, but I don't know what the expected order is. In fact, I think it might not even required to be in any particular order. I think this arises from an interaction of the specific way Enlightenment manages things combined with the assumption mentioned above. This would also explain why running GTK programs on Neo via X forwarding works for me (with xfwm4 on my laptop). It also explains what someone described to me on IRC: that with Debian the same problems appeared only after changing WM to Enlightenment. They were going to add a comment to the ticket, but don't seem to have done so yet. e definitely does things differently to other wm's - it has a state machine that it leaves to settle and then evaluates it on idle - and THEN sends fake events and configures windows etc. as such under ICCCM this is something the wm is free to do - not every configure request from an app will necessarily be honored. -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: German dictionary for Raster's keyboard with frequencies?
On Sun, 30 Nov 2008 16:34:11 +0100 Marcel [EMAIL PROTECTED] babbled: Moin! I just found out that the wordlist needs to have a .dic file extension to get recognized by Raster's keyboard - now it dicts quite well, except that some often used (internet) slang words are missing... Has anyone got a german word list with word frequencies yet? The one I got (debian package wngerman, /usr/share/dicts/ngerman) only has the words, but no frequencies which makes finding the right word difficult sometimes, especially I can't get the wordlist on the keyboard to scroll (is this even implemented?) without selecting a word accidentally. Another suggestion to Raster: I think it would be useful to have the whole word getting deleted on backspace while one has a language dictionary activated (in contrast to a terminal/programming one) because mostly the whole word gets wrong instead of just some single characters. actually - what i need to do is have short and long stroke. short is delete 1 char, long is delete the whole word you are composing... :) -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)[EMAIL PROTECTED] ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Pre-made debian image?
i was wondering if there is a pre-made debian image available that I can copy directly to my memory card. All I can find are guides on installing it through an existing OS on my phone but I can't connect my phone to my computer (for internet, ssh) because the xp driver doesn't work. -- View this message in context: http://n2.nabble.com/Pre-made-debian-image--tp1596711p1596711.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
auxlaunch ver 0.6
Hello, Here's info on an update to auxlaunch, (finger-friendly app launcher and window switcher). Download at [1] and wiki page at [2]. Version 0.6 changes include: - New '-noaux' option as alternative to claiming the AUX button. - At startup, if another auxlaunch instance is running, signal it (to appear) then exit current instance. - Use rc file in user's home directory. - Use fork and execvp to launch apps. - Bug fix: mode now set to WIN on gaining focus. - Started using version control (at http://code.google.com/p/auxlaunch/). - Removed pesky /r's. (Thanks to Timo for the alert.) - DMS: Shortened 'Applicatons' to 'Apps'. Comments and patches always welcome. Many thanks to Joachim nomeata Breitner, chrysn, and ben for their contributions and advice. [1] http://code.google.com/p/auxlaunch/downloads/list [2] http://wiki.openmoko.org/wiki/Auxlaunch - aliasid ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Pre-made debian image?
On Sun, Nov 30, 2008 at 6:19 PM, abatrour [EMAIL PROTECTED] wrote: i was wondering if there is a pre-made debian image available that I can copy directly to my memory card. Check out hackable1.org. They're based on Debian and you install by copying directly to SD card. I was able to install it and so far, so good. -aliasid ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SD boot freeze, hang at boot time, why ?
Marian Flor a écrit : Am Sonntag, den 30.11.2008, 18:46 + schrieb Andy Green: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Starting kernel ... | /freeze | | Someone can tell me what's happening ? Or give me any clues to repair | that, and a place to report the bug. Best thing is figure out if it's a kernel issue or just userspace... fiddle with your U-Boot env to add console=tty0 loglevel=8 on the Maelvon, I had a similar issue with a 16GB card. Resolution was to add some sleep(1) time before mmcinit is called. Works fine after after adding 2 seconds of sleep. See: http://wiki.openmoko.org/wiki/SanDisk/SDSDQ-016G-E11M and reference to original post: http://lists.openmoko.org/pipermail/community/2008-November/035412.html HTH, Marian Thanks Andy and Marian, I'll try to add the loglevel=8 to the U-Boot, not tested for now. First I have tested the Marian solution, and I understand now the difference between the NAND and NOR. NAND can be modified with the configure-uboot.sh script file. The NOR cannot be modified. I'm testing Hackable:1. I've installed Debian before Hackable:1, and modified the NAND menu a few weeks ago but always boot in NOR, so I don't know if it work with the default configure-uboot.sh and Debian in NAND. Testing the Marian solution, I've modified the NAND boot, added the sleep 2; but on NAND boot it say now : boot Failed to mount ext2 filesystem... ** Bad ext2 partition or disk - mmc 1:1 ** Wrong image format for bootm command ERROR: can't get kernel image! /boot I'm using the Hackable:1, so I think it was the problem as it boot Hackable:1 normally in the NOR (fat+ext2), with allright the freeze problem for Flash and MicroSD. I've done a fsck.ext2 -v -y -f /dev/mmcblk0p2, but no changes. Any clues, Regards, Maelvon ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[OM-testing] change default dialer volume
Hello list, I've been playing around with the daily testing image and found it to be reasonably good. The only thing that I've not found how to do i to set the default in-call volume (the qtopia-dialer one) since on every call the volume starts at 0 so, as you can imagine, i can barely hear anything. Anyone knows where to set the default value? regards, Tom ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: ALSA state ringtone volume
leonardo wrote: Hi all, Does anybody knows which alsa statefile, and which control should I edit to raise/lower the volume of the ringtone when receiving gsm calls? Until you answer the stereoout.state file is used. I guess you should set the 'PCM Volume' and 'Headphone Playback Volume' controls. Bye -- Treviño's World - Life and Linux http://www.3v1n0.net/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [OM-testing] change default dialer volume
Tomas Riveros Schober wrote: Hello list, I've been playing around with the daily testing image and found it to be reasonably good. The only thing that I've not found how to do i to set the default in-call volume (the qtopia-dialer one) since on every call the volume starts at 0 so, as you can imagine, i can barely hear anything. Anyone knows where to set the default value? As I've written in the bug #2140 two days ago, to avoid this issue the openembedded PhoneProfile.conf should have been updated, but it seems that it hasn't been. Btw you can easily fix your problem by editing the file /opt/Qtopia/etc/default/Trolltech/PhoneProfile.conf Adding, for each profile, a line like: CallVolume = 3 More infos at [2]. [1] http://docs.openmoko.org/trac/ticket/2140#comment:6 [2] http://git.openmoko.org/?p=qtopia.git;a=commit;h=1819dc7a500d51083b8871cd55b5e4507da329a5 -- Treviño's World - Life and Linux http://www.3v1n0.net/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [OM-testing] change default dialer volume
Marco Trevisan (Treviño) wrote: Tomas Riveros Schober wrote: Hello list, I've been playing around with the daily testing image and found it to be reasonably good. The only thing that I've not found how to do i to set the default in-call volume (the qtopia-dialer one) since on every call the volume starts at 0 so, as you can imagine, i can barely hear anything. Anyone knows where to set the default value? As I've written in the bug #2140 two days ago, to avoid this issue the openembedded PhoneProfile.conf should have been updated, but it seems that it hasn't been. Btw you can easily fix your problem by editing the file /opt/Qtopia/etc/default/Trolltech/PhoneProfile.conf Adding, for each profile, a line like: CallVolume = 3 More infos at [2]. [1] http://docs.openmoko.org/trac/ticket/2140#comment:6 [2] http://git.openmoko.org/?p=qtopia.git;a=commit;h=1819dc7a500d51083b8871cd55b5e4507da329a5 wow, thank you very much for the information, that was precisely what i was looking for (however, the bug is not exactly the same, since the phone is configured to ring, not to silence or vibrate only) Tom ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [OM-testing] change default dialer volume
Tomas Riveros Schober wrote: Marco Trevisan (Treviño) wrote: Tomas Riveros Schober wrote: Hello list, I've been playing around with the daily testing image and found it to be reasonably good. The only thing that I've not found how to do i to set the default in-call volume (the qtopia-dialer one) since on every call the volume starts at 0 so, as you can imagine, i can barely hear anything. Anyone knows where to set the default value? As I've written in the bug #2140 two days ago, to avoid this issue the openembedded PhoneProfile.conf should have been updated, but it seems that it hasn't been. Btw you can easily fix your problem by editing the file /opt/Qtopia/etc/default/Trolltech/PhoneProfile.conf Adding, for each profile, a line like: CallVolume = 3 More infos at [2]. [1] http://docs.openmoko.org/trac/ticket/2140#comment:6 [2] http://git.openmoko.org/?p=qtopia.git;a=commit;h=1819dc7a500d51083b8871cd55b5e4507da329a5 wow, thank you very much for the information, that was precisely what i was looking for (however, the bug is not exactly the same, since the phone is configured to ring, not to silence or vibrate only) Yes, but that's in that bug that I posted the patches that fixed that issue (no caller audio if not ringing - that was present in the first git revision containing the volume slider); and there I posted also a diff to complete the patchset and fixing the side effect you've mentioned... -- Treviño's World - Life and Linux http://www.3v1n0.net/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
On Sun, Nov 30, 2008 at 10:56:47PM +0100, Fabian Henze wrote: On 30.11.2008 at 12:50:22, John Lee wrote: Since there are different hw versions out there (a5, a6, a7), it's impossible to provide one alsa state file that suits all models. Just a short question: What is a7? Can you please update the wiki article about the GTA02 revisions? -- Fabian I think it's not shipped yet, so maybe it exists only inside openmoko. I don't know about the details. - John ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
On Sun, Nov 30, 2008 at 02:16:48PM +0100, Franky Van Liedekerke wrote: On Sun, 30 Nov 2008 19:50:22 +0800 John Lee [EMAIL PROTECTED] wrote: Echo: Since there are different hw versions out there (a5, a6, a7), it's impossible to provide one alsa state file that suits all models. However, it seems you can always find appropriate values for your neo. My way is to adjust control.4 Speaker Playback Volume in /usr/share/openmoko/scenarios/gsmhandset.state the max value is 127, 95 works best on my a5. With volume level 3 or 4 in qtopia dialer, the other side can hear no echo while I get good audio quality. Does this mean the fix is only through alsa? So the fix mentioned here: http://n2.nabble.com/FSO-M4---nice-GSM-sound-tp1486414p1518726.html is not ok? Since that fix is the only real fix for my echo issues (and it seems to come from 2008.8). Franky That fix is already in testing repo, maybe over 1 month now. However even with this patch there is still chance you can hear echo. Let's say A calls B, and B is using a neo with this fix. 1. The receiver (handset speaker) is loud enough and the mic is sensitive enough, so gsm won't turn off the mic. 2. A starts speaking right after B, but gsm needs a little time to turn off mic. In either case you can still here a little echo. Much better then before, of course, but still a little. I was talking about 1. in my previous post. - John ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[no subject]
[EMAIL PROTECTED] ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
On Sun, Nov 30, 2008 at 01:32:20PM +, Rui Miguel Silva Seabra wrote: On Sun, Nov 30, 2008 at 07:50:22PM +0800, John Lee wrote: Echo: Since there are different hw versions out there (a5, a6, a7), it's impossible to provide one alsa state file that suits all models. However, it seems you can always find appropriate values for your neo. My way is to adjust control.4 Speaker Playback Volume in /usr/share/openmoko/scenarios/gsmhandset.state the max value is 127, 95 works best on my a5. With volume level 3 or 4 in qtopia dialer, the other side can hear no echo while I get good audio quality. This is interesting, I have an a5 and the default value of FSO M4.1a: control.4 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 127' iface MIXER name 'Speaker Playback Volume' value.0 116 value.1 116 } Sometimes I ask people on the other side: do you hear echo? The answer has been no. Rui 116 was the old value I use before I updated the alsa state file from FDOM. There was no/very little echo, but the other side always complains they cannot hear me very well. I also feel the receiver (handset speaker) is unnecessarily loud sometimes. The new alsa state file uses 116, but boosts the mic path a little bit more, so it solved the can't hear me problem while makes the echo even easier to happen. With the new state file, 95 is the best value for me because I can always make it louder if necessary with Tick's volume bar in qtopia. - John ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Optimization team update (11/23 ~ 11/29)
On Sun, Nov 30, 2008 at 06:56:28PM +, Andy Green wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: Hi John - | * some obsolete kernel modules still left in system If we didn't do it already, the packaged kernels need to move to having /lib/modules path that is specific to the kernel device and build, similar to what the ./build script does: /lib/modules/2.6.28-GTA02_andy-tracking_d0aa5acc0be7c573-mokodev/ The branch and hash stops any conflict about module versions, and the device tag GTA02 allows multiple kernels to be installed on the same rootfs, so you can share the SD Card between GTA01 and GTA02 say, both times with SD Card boot to the right kernel. Yup, but it won't make opkg remove the unnecessary modules. It's a problem that needs to be solved in OE. | * must remove 'ro' in kernel boot parameter if you use sd boot. At the moment Qi has ro boot everywhere by default, is this restriction just a temporary workaround for something? I think it's related to Olv's new boot scripts. I have rough idea about why but this can be better explained by him. | he will work on opkg internals next. Olv moved to look into kernel | and fso. Erin will try bluetooth. Julian is working on the GTK | redraw issue, please help him out. Jeremy will fix some qtopia bugs | and keep working on suspend/resume issues. Just a thought, it can be worth Olv and Jeremy bouncing what they're planning on doing off the kernel list. For example some advice for Jeremy about suspend / resume issues would be don't waste your time doing any suspend / resume work on 2.6.24 kernel, only on | andy-tracking. Thanks for the reminder. :) - John ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community