Re: [SHR-U] WiFi-related memory leak
What additional info I can gather? Use slabtop to monitor kernel memory pools. It may be interresting. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Voice quality on FreeRunner A7 ?
With the right volume settings my FR is on a par with my k700i. After having buzz-fixed the phone, I followed all discussions about mixer settings and I managed after many tries to raise sound quality (for other end) from inaudible to barely audible. I would be very interrested in your settings, although I suspect this depends most on the phone than on the settings. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [SHR-U] WiFi-related memory leak
Denis Shulyaka shuly...@gmail.com writes: It writes output of `ps auxf`, `free` and `df -h` to a corresponding file every 5 minutes. Hmm, you are using swap. I do not know how to see how many bytes each process has in swap. This would let us see which process is the one whose memory usage steadily increases. Now we only see that RSS (number of bytes each process has in RAM) decreases when the bytes are moved to swap. Can you try the same test again without swap? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian] new kernel package
On 21 February 2010 02:34, Sebastian Reichel elektra...@gmail.com wrote: Hi, Hi Sebastian, I just uploaded a new kernel package to the pkg-fso repository. Please note, that you need to load 'neo1973kbd' for the buttons to work and 'leds-neo1973-gta02' for the leds to work. You probably want to add these to your /etc/modules. Apart from factoring out those modules, is the new kernel improved in some way? And is it built without the debug settings? Regards, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian] new kernel package
2010/2/21 Neil Jerram neiljer...@googlemail.com: ' Apart from factoring out those modules, is the new kernel improved in some way? And is it built without the debug settings? It's the latest upstream andy-tracking, mostly meaning that if compared to July snapshot Bluetooth, GPS etc. should handle suspend better among else. Debug is disabled. WLAN should work, but because of the debug being disabled one usually hits this bug quite soon: http://docs.openmoko.org/trac/ticket/2327 Also unfortunately due to some refactoring of touch screen code in andy-tracking, this happens from time to time, but luckily quite rarely: http://docs.openmoko.org/trac/ticket/2328 -Timo ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[debian] ssh hangs
a long time ago i used to experience frequent hangs with ssh connections, when using that infamous dropbear. after i while i got fed up and replaced that crippled thing with a full good sshd, which worked well until a few weeks ago. but with an upgrade of sshd a few weeks ago the exact same issue was introduced again, after a few lines of output the ssh shell freezes and there's nothing to be done excpet killing -- and that's not that easy since i usually have several connections open and there's no easy way to determine which one is the frozen one. so, 1.5 questions: - what happens? i never found any log entries shedding light. does anyone else experience that? - is there a way to make ssh connections easily distinguishable with ps or so? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] ssh hangs
arne anka openm...@ginguppin.de writes: a long time ago i used to experience frequent hangs with ssh connections, when using that infamous dropbear. Does this happen when you ssh to localhost? but with an upgrade of sshd a few weeks ago the exact same issue was introduced again, after a few lines of output the ssh shell freezes and there's nothing to be done excpet killing -- and that's not that easy Does the client respond to escape sequences? (man ssh and read ESCAPE CHARACTERS) - what happens? i never found any log entries shedding light. does anyone else experience that? - is there a way to make ssh connections easily distinguishable with ps or so? ps axuf should make it easy to associate ssh server processes to the programs that you are using over ssh and netstat -alpn should tell you which tcp ports these server processes are talking to. If you then run netstat -alpn on the client side you can figure out which client uses the port associated with the frozen connection. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
ar6000 (FR's wifi) bugs, workarounds and CLI usage tips, read this for stable wifi
Hi,
I've got involved in some wifi configuration recently and so tested FR
with different APs and settings. As a result, several interesting
observations were made, i hope you'll find them useful.
1. Weird SSID bug
Thanks to the hint by Werner i found out that i can never connect to
my WPA+RSN AP when its SSID is Paul-g700ap. wpa_supplicant
associates but 4-way handshake times out after sending 2/4. Every
time. Changing SSID to e.g. Paul-g700af and power-cycling ar6000
reliably makes it work. Changing it back reliably makes it not work.
To sum up: if WPA authentication times out, try changing SSID.
2. Do not hurry to start up wpa_supplicant, add some pause after
powering on the chip:
fsoraw -r WiFi -- bash -c sleep 5; wpa_supplicant -ieth0 -Dwext
-c/etc/wpa_supplicant/wpa_supplicant.conf
3. It's recommended to power-cycle the chip after every wpa_supplicant
invocation, the fsoraw method does that automatically, if you're
using any other way, you might need to do that manually.
4. With some APs to get reliable (sometimes any) operation, you need
the maxperf trick:
wmiconfig -ieth0 --power=maxperf
5. Suspend/resume works just fine but you need some additional trick
to get DHCP lease again after resume. For that you can start
wpa_cli -G100 -a /usr/local/bin/wifi-dhcp.sh
with wifi-dhcp.sh:
#!/bin/sh
[ $2 = CONNECTED ] {
dhclient $1
pkill -f wpa_cli -a
wpa_cli -a $0 -B -G100
}
The need for restarting wpa_cli comes from a kernel bug (the driver
fails to notify the userspace about disconnection), the fix is
available on the kernel ML and will be committed soon; after that you
won't need pkill wpa_cli lines any more.
With Debian (no idea if that's applicable to OE, sorry) after applying
the fix you should be able to use standard /etc/network/interfaces
configuration methods, it should invoke wpa_cli, wpa_action and
ifupdown on its own, but i haven't tried to make that work yet, please
try it yourself and report the results.
HTH
--
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercer...@gmail.com
___
Openmoko community mailing list
community@lists.openmoko.org
http://lists.openmoko.org/mailman/listinfo/community
Re: ar6000 (FR's wifi) bugs, workarounds and CLI usage tips, read this for stable wifi
please, explain power cycling. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: ar6000 (FR's wifi) bugs, workarounds and CLI usage tips, read this for stable wifi
Em 21-02-2010 15:50, arne anka escreveu: please, explain power cycling. rebooting ar6000 (one of Freerunner's computers). Rui ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: ar6000 (FR's wifi) bugs, workarounds and CLI usage tips, read this for stable wifi
please, explain power cycling. rebooting ar6000 (one of Freerunner's computers). that i did understand -- the question is, how to do that. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: ar6000 (FR's wifi) bugs, workarounds and CLI usage tips, read this for stable wifi
Am Sonntag, den 21.02.2010, 17:14 +0100 schrieb arne anka: please, explain power cycling. rebooting ar6000 (one of Freerunner's computers). that i did understand -- the question is, how to do that. On FSO via releasing/requesting the WiFi resource. :M: ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] ssh hangs
a long time ago i used to experience frequent hangs with ssh connections, when using that infamous dropbear. Does this happen when you ssh to localhost? nope. and not with other targets. only the fr, which makes me suspect it has something to do with usb networking. but it has not been an issue before with debian ssh. it seems to happen only when th fr outputs something, frinst when doing qdbus --system (even with mdbus) or when compiling via ssh. Does the client respond to escape sequences? (man ssh and read ESCAPE CHARACTERS) have to check next time. as usual it does not freeze while watched now :-) ps axuf should make it easy to associate ssh server processes to the programs that you are using over ssh and netstat -alpn should tell you which tcp ports these server processes are talking to. If you then run netstat -alpn on the client side you can figure out which client uses the port associated with the frozen connection. yes, but i kind of hoped for a simpler solution. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian] new kernel package
On Sun, Feb 21, 2010 at 10:01:56AM +, Neil Jerram wrote: On 21 February 2010 02:34, Sebastian Reichel elektra...@gmail.com wrote: Hi, Hi Sebastian, I just uploaded a new kernel package to the pkg-fso repository. Please note, that you need to load 'neo1973kbd' for the buttons to work and 'leds-neo1973-gta02' for the leds to work. You probably want to add these to your /etc/modules. Apart from factoring out those modules, is the new kernel improved in some way? And is it built without the debug settings? I already disabled debug with my last upload, but this time I also disabled SYSFS_DEPRECATED, which results in a working udev again. Apart from this there is now ubifs support. I also changed some more built in stuff to modules, but these will be loaded by udev (e.g. lis302dl) -- Sebastian signature.asc Description: Digital signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: ar6000 (FR's wifi) bugs, workarounds and CLI usage tips, read this for stable wifi
With small variations upon your script I have: 1) ~/wpa dir with the following contents: r...@om-gta02 ~ $ ls wpa/ amigos.wpacasa.wpa gomaxperf spot.wpa wifi-dhcp.sh (the .wpa files are wpa config files with special setups). 2) maxperf is for the weird cases: r...@om-gta02 ~ $ cat wpa/maxperf #!/bin/sh wmiconfig -ieth0 --power=maxperf 3) go just glue's Paul's commands (but required a bit more of sleep time in order to work reliably, and using sh instead of bash): r...@om-gta02 ~ $ cat wpa/go #!/bin/sh CONF=$1 set -x fsoraw -r WiFi -- sh -c sleep 5; wpa_supplicant -i eth0 -D wext -c $CONF sleep 10 wpa_cli -a /home/root/wpa/wifi-dhcp.sh -B -G100 4) and wifi-dhcp.sh is slightly modified (for instance, I don't have dhclient): r...@om-gta02 ~ $ cat wpa/wifi-dhcp.sh #!/bin/sh if [ $2 == CONNECTED ] ; then udhcpc $1 pkill -f wpa_cli -a wpa_cli -a $0 -B -G100 fi 5) running the following works, and recovers wifi when resumed after suspend: cd wpa ; ./go casa.wpa Rui ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: ar6000 (FR's wifi) bugs, workarounds and CLI usage tips, read this for stable wifi
arne anka openm...@ginguppin.de writes: that i did understand -- the question is, how to do that. If you are not using FSO in debian you can use om wifi power 0 om wifi power 1 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] ssh hangs
arne anka openm...@ginguppin.de writes: nope. and not with other targets. only the fr, which makes me suspect it What if you ssh to localhost on FR itself? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[debian] phonfsod/phoneuid: fso-deviced killed when calling
investigating my core issue of the fr not suspending anymore after a call, i see now that fsodeviced dies the moment i hit either call (outgoing) or accept (incoming). since fso-deviced is dead, nothing, in terms of idle notification at least, happens anymore. i try to track it down, but if anyone could point out, where it and what happens (and how to track efficiently -- i surely miss something like java's stacktraces or even python's exceptions) ... ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Voice quality on FreeRunner A7 ?
On Sunday 21 February 2010, Gand' wrote: i have a very annoying buzzing sound with the latest SHR for the caller on my openmoko A7 i hear everything pretty well and clear, but the other side is hearing a mettalic buzz ... The default setting for control 12 is 7, the maximum, which is too high for many people. The signal overloads the amp and gets distorted, giving what is often described as a buzz when you are speaking. In /etc/freesmartphone/alsa/default/gsmhandset you can drop it to 6 or 5. The distortion can also stop the echo cancellation working correctly. i think this is the awful here ... can you share your tweaked volume settings ? As the other reply demonstrates, everyone has different needs. The important thing isn't my settings, but knowing how to get a sensible combination of the three controls so that you get the right volume level without distortion. Last time I looked the wiki had what I think is a good description of one way to do this. I didn't write it, and it may only seem like a good explanation to me because I already understand it. If you find any of it confusing then ask about it, and we can work on a better explanation. I put another method in code as fso-simplemixer.py (also mentioned in the wiki) which may be worth a try. I think it may need a small fix for save to work with recent fso versions, and there are a few bugs that i never managed to fix. Please back up your alsa settings before using it as some once reported a corrupted alsa state, though we were never able to repeat it. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Voice quality on FreeRunner A7 ?
On Sunday 21 February 2010, ri...@happyleptic.org wrote: With the right volume settings my FR is on a par with my k700i. After having buzz-fixed the phone, I followed all discussions about mixer settings and I managed after many tries to raise sound quality (for other end) from inaudible to barely audible. I would be very interrested in your settings, although I suspect this depends most on the phone than on the settings. please see my other reply regarding how to get a sensible set of settings. My settings would be no use to you as I turn down from default not up. I suspect the variations in how loudly people speak and how they position the phone relative to their head have more to do with the need for different settings than variations in the handsets themselves. We would need to do a lot of measurements to find out though. Normally phone handsets get around this problem by using automatic gain controls. There is one in the Wolfson audio codec, but I have never managed to get it to help. I think one of the openmoko hardware guys said it isn't any use for the signal levels we have, but I haven't checked the datasheet of poked the board with a scope to be sure. There is probably also such a control in the Calypso, but we have no means of using it (unless the project for an open calypso firmware makes some sudden and unexpected progress). ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Voice quality on FreeRunner A7 ?
Al Johnson openm...@mazikeen.demon.co.uk writes: My settings would be no use to you as I turn down from default not up. I suspect the variations in how loudly people speak and how they position the phone relative to their head have more to do with the need for different settings than variations in the handsets themselves. We would need to do a lot of measurements to find out though. I currently have an asterisk setup that lets me record calls so that I can compare calls made with openmoko against calls made with other phones. Is there some standardized test suite that I could play and then investigate the recordings? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] phonfsod/phoneuid: fso-deviced killed when calling
On Sun, Feb 21, 2010 at 07:21:19PM +0100, arne anka wrote: investigating my core issue of the fr not suspending anymore after a call, i see now that fsodeviced dies the moment i hit either call (outgoing) or accept (incoming). since fso-deviced is dead, nothing, in terms of idle notification at least, happens anymore. i try to track it down, but if anyone could point out, where it and what happens (and how to track efficiently -- i surely miss something like java's stacktraces or even python's exceptions) ... you can do it like this: $ ulimit -c unlimited $ my-program program died with segfault (core dumped) $ gdb my-program core % bt -- Sebastian signature.asc Description: Digital signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] phonfsod/phoneuid: fso-deviced killed when calling
you can do it like this: $ ulimit -c unlimited $ my-program program died with segfault (core dumped) $ gdb my-program core % bt ok, below's the output -- anyone able to make head or tail from it? # gdb fsodeviced core GNU gdb (GDB) 7.0.1-debian Copyright (C) 2009 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as arm-linux-gnueabi. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/sbin/fsodeviced...(no debugging symbols found)...done. Reading symbols from /usr/lib/libfsoresource.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libfsoresource.so.0 Reading symbols from /usr/lib/libfso-glib.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libfso-glib.so.0 Reading symbols from /usr/lib/libfsoframework.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libfsoframework.so.0 Reading symbols from /usr/lib/libdbus-glib-1.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libdbus-glib-1.so.2 Reading symbols from /usr/lib/libasound.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libasound.so.2 Reading symbols from /usr/lib/libfsobasics.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libfsobasics.so.0 Reading symbols from /lib/libdbus-1.so.3...(no debugging symbols found)...done. Loaded symbols for /lib/libdbus-1.so.3 Reading symbols from /lib/libpthread.so.0...(no debugging symbols found)...done. Loaded symbols for /lib/libpthread.so.0 Reading symbols from /lib/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/librt.so.1 Reading symbols from /usr/lib/libgio-2.0.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgio-2.0.so.0 Reading symbols from /usr/lib/libgmodule-2.0.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgmodule-2.0.so.0 Reading symbols from /usr/lib/libgee.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgee.so.2 Reading symbols from /usr/lib/libgobject-2.0.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgobject-2.0.so.0 Reading symbols from /lib/libglib-2.0.so.0...(no debugging symbols found)...done. Loaded symbols for /lib/libglib-2.0.so.0 Reading symbols from /lib/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /usr/lib/libgthread-2.0.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libgthread-2.0.so.0 Reading symbols from /lib/libm.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/libm.so.6 Reading symbols from /lib/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /lib/libgcc_s.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libgcc_s.so.1 Reading symbols from /lib/ld-linux.so.3...(no debugging symbols found)...done. Loaded symbols for /lib/ld-linux.so.3 Reading symbols from /lib/libpcre.so.3...(no debugging symbols found)...done. Loaded symbols for /lib/libpcre.so.3 Reading symbols from /lib/libresolv.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libresolv.so.2 Reading symbols from /lib/libselinux.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libselinux.so.1 Reading symbols from /lib/libnss_compat.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libnss_compat.so.2 Reading symbols from /lib/libnsl.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/libnsl.so.1 Reading symbols from /lib/libnss_nis.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libnss_nis.so.2 Reading symbols from /lib/libnss_files.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libnss_files.so.2 Reading symbols from /usr/lib/cornucopia/modules/fsodevice/accelerometer_lis302.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/cornucopia/modules/fsodevice/accelerometer_lis302.so Reading symbols from /usr/lib/libfsodevice.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libfsodevice.so.0 Reading symbols from /usr/lib/cornucopia/modules/fsodevice/accelerometer.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/cornucopia/modules/fsodevice/accelerometer.so Reading symbols from /usr/lib/cornucopia/modules/fsodevice/player_alsa.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/cornucopia/modules/fsodevice/player_alsa.so Reading symbols from /usr/lib/cornucopia/modules/fsodevice/player_canberra.so...(no debugging symbols
Re: [debian] phonfsod/phoneuid: fso-deviced killed when calling
installed libgee2-dbg and got that (probably not of much use): Core was generated by `fsodeviced'. Program terminated with signal 11, Segmentation fault. #0 gee_map_get_keys (self=0x0) at map.c:353 353 map.c: No such file or directory. in map.c (gdb) bt #0 gee_map_get_keys (self=0x0) at map.c:353 #1 0x409295e0 in ?? () from /usr/lib/cornucopia/modules/fsodevice/router_alsa.so #2 0x409295e0 in ?? () from /usr/lib/cornucopia/modules/fsodevice/router_alsa.so Backtrace stopped: previous frame identical to this frame (corrupt stack?) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] phonfsod/phoneuid: fso-deviced killed when calling
ok, third: since it has something to do with alsa_router, i checked th config files and found in fsodeviced.conf [fsodevice.audio] # Which Audio Player variant plugin to use: none (default), alsa, canberra, gstreamer player_type = alsa # Which Audio Router variant plugin to use: none (default), alsa router_type = alsa replacing alsa with none lets fsodeviced survive. - what do these options do? - what's the difference between als and none? - i guess some checking is necessary instead of relaying on whatever. in my frameowrkd.conf, there's a section (disabled by me) [odeviced.audio] # set 1 to disable a module disable = 1 # set directory where the alsa audio scenarios are stored scenario_dir = /usr/share/openmoko/scenarios # set default scenario loaded at startup default_scenario = stereoout where scenario_dir and default_scenario are defined, none of the two do i find in fsodeviced.conf. is that somewhat related and where should i set at least the default scenario (while i am at it)? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Mic volume extremely soft after buzz fix with SHR unstable
Hi, after I got my gta02 A06 a hardware buzz fix late December last year the mic is very soft with the newest SHR unstable. So I had a look at all the different tips around and carefully read all emails of the thread Experiment: better sound on remote end and all links mentioned in there and tried all the suggested tweaks and got rid of any static or noise, but the mic still is so soft that I literally have to yell at my phone from close distance in order to be hardly understood by the callee. What could be the problem? Any suggestions on what I could try to set the mic volume to a usable level? Could the problem be related to the buzz fix? After fiddling around with the settings for a long time I ended up with setting the controls in the gsmhandset.state file back to these values. The other values are untouched. * control.48: 3 * control.63: 'Mic 2' * control.12: 7 * control.5:115 btw: What is the difference between /etc/freesmartphone/alsa/default/gsmhandset and /usr/share/shr/scenarii/gsmhandset.state ? Both are mentioned on the wiki pages I read and latter is mentioned to be the one used by SHR although the first one exists on my install as well. Need any more info to help me out? Thanks Jan 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: [debian] phonfsod/phoneuid: fso-deviced killed when calling
fsodeviced provides different plugins for audio routing. You want the alsa one for the FreeRunner. You're running debian, right? Do they ship the new alsa data files for fsodeviced? Cheers, :M: ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Mic volume extremely soft after buzz fix with SHR unstable
btw: What is the difference between /etc/freesmartphone/alsa/default/gsmhandset This one is used by fsodeviced, i.e. the new stuff that's being used on SHR. and /usr/share/shr/scenarii/gsmhandset.state ? That's from the old days where we used to call alsactl to do the work. :M: ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] phonfsod/phoneuid: fso-deviced killed when calling
fsodeviced provides different plugins for audio routing. You want the alsa one for the FreeRunner. well, as written, alsa kills fsodeviced. what kind of audio routing? call seems to work even with none (at least i hear something when i call my box). You're running debian, right? Do they ship the new alsa data files for fsodeviced? what alsa data files? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] phonfsod/phoneuid: fso-deviced killed when calling
Am Sonntag, den 21.02.2010, 21:45 +0100 schrieb arne anka: fsodeviced provides different plugins for audio routing. You want the alsa one for the FreeRunner. well, as written, alsa kills fsodeviced. Probably because of the missing alsa data files (see below). what kind of audio routing? call seems to work even with none (at least i hear something when i call my box). audio routing is necessary i.e. to switch between ring tone and in-call audio. You might hear the ring tone, if that's the default routing, but you will not have in-call audio without routing. You're running debian, right? Do they ship the new alsa data files for fsodeviced? what alsa data files? http://cgit.openembedded.net/cgit.cgi/openembedded/tree/recipes/freesmartphone/fso-alsa-data/om-gta02 Those have to be copied to /etc/freesmartphone/alsa/. Next week, I'll make fso ship them instead of putting them into OE. Cheers, :M: ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] phonfsod/phoneuid: fso-deviced killed when calling
On Sun, Feb 21, 2010 at 09:59:38PM +0100, Michael 'Mickey' Lauer wrote: Am Sonntag, den 21.02.2010, 21:45 +0100 schrieb arne anka: fsodeviced provides different plugins for audio routing. You want the alsa one for the FreeRunner. well, as written, alsa kills fsodeviced. Probably because of the missing alsa data files (see below). what kind of audio routing? call seems to work even with none (at least i hear something when i call my box). audio routing is necessary i.e. to switch between ring tone and in-call audio. You might hear the ring tone, if that's the default routing, but you will not have in-call audio without routing. You're running debian, right? Do they ship the new alsa data files for fsodeviced? what alsa data files? http://cgit.openembedded.net/cgit.cgi/openembedded/tree/recipes/freesmartphone/fso-alsa-data/om-gta02 Those have to be copied to /etc/freesmartphone/alsa/. Next week, I'll make fso ship them instead of putting them into OE. Cheers, :M: Hi, I included these alsa files in 'fso-config-gta02' in Janurary. -- Sebastian signature.asc Description: Digital signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian] new kernel package
with that new package, the fr doesn't vibrate on incoming call. something missing in the kernel itself or do i need yet another module? btw: why is there a cdrom.ko? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] phonfsod/phoneuid: fso-deviced killed when calling
fsodeviced provides different plugins for audio routing. You want the alsa one for the FreeRunner. well, as written, alsa kills fsodeviced. Probably because of the missing alsa data files (see below). nope. they are there. what kind of audio routing? call seems to work even with none (at least i hear something when i call my box). audio routing is necessary i.e. to switch between ring tone and in-call audio. You might hear the ring tone, if that's the default routing, but you will not have in-call audio without routing. no idea, what in-call means, but with player_type = none router_type = none i hear and am heared in a call. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: Mic volume extremely soft after buzz fix with SHR unstable
Am Sonntag, den 21.02.2010, 21:33 +0100 schrieb Michael 'Mickey' Lauer: btw: What is the difference between /etc/freesmartphone/alsa/default/gsmhandset This one is used by fsodeviced, i.e. the new stuff that's being used on SHR. Good to know. So far I did all changes to both files, but will discard the old one now. Jan 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: [Debian] new kernel package
On Sun, Feb 21, 2010 at 10:50:10PM +0100, arne anka wrote: with that new package, the fr doesn't vibrate on incoming call. something missing in the kernel itself or do i need yet another module? Actually I compiled the vibrator support into the kernel because the module wasn't working for me. First of all you could check if the following file exists: /sys/class/leds/neo1973:vibrator/brightness Apart from this I currently don't know how FSO activates the vibrator, but probably you should load 'ledtrig_timer'. btw loading 'ledtrig_heartbeat' module and then echo 'heartbeat' /sys/class/leds/neo1973:vibrator/trigger animates your freerunner - it's quite cool :D btw: why is there a cdrom.ko? I did not change anything containing the keyword cdrom, but there are usb cdrom drives, so I think it should stay there as a module. -- Sebastian signature.asc Description: Digital signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] phonfsod/phoneuid: fso-deviced killed when calling
On Sun, Feb 21, 2010 at 11:01:08PM +0100, arne anka wrote: fsodeviced provides different plugins for audio routing. You want the alsa one for the FreeRunner. well, as written, alsa kills fsodeviced. Probably because of the missing alsa data files (see below). nope. they are there. what kind of audio routing? call seems to work even with none (at least i hear something when i call my box). audio routing is necessary i.e. to switch between ring tone and in-call audio. You might hear the ring tone, if that's the default routing, but you will not have in-call audio without routing. no idea, what in-call means, but with player_type = none router_type = none i hear and am heared in a call. I just installed fsodeviced and I can confirm it crashing on incoming call with default settings. I cannot confirm that there is still sound when setting router_type to none. It's a pity, that Heiko did not build a -dbg package for fso-deviced itself. I will try to build one now. -- Sebastian signature.asc Description: Digital signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] phonfsod/phoneuid: fso-deviced killed when calling
I cannot confirm that there is still sound when setting router_type to none. does that mean, you didn't test or you did not hear something? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] phonfsod/phoneuid: fso-deviced killed when calling
On Sun, Feb 21, 2010 at 11:24:52PM +0100, arne anka wrote: I cannot confirm that there is still sound when setting router_type to none. does that mean, you didn't test or you did not hear something? I heard no ringtone and no sound during the call on both sides. I tried calling as well as being called. -- Sebastian signature.asc Description: Digital signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian] new kernel package
arne anka openm...@ginguppin.de writes: with that new package, the fr doesn't vibrate on incoming call. something missing in the kernel itself or do i need yet another module? ls /sys/class/leds? lsmod? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] phonfsod/phoneuid: fso-deviced killed when calling
On Sun, Feb 21, 2010 at 09:29:49PM +0100, Michael 'Mickey' Lauer wrote: Am Sonntag, den 21.02.2010, 19:21 +0100 schrieb arne anka: investigating my core issue of the fr not suspending anymore after a call, i see now that fsodeviced dies the moment i hit either call (outgoing) or accept (incoming). since fso-deviced is dead, nothing, in terms of idle notification at least, happens anymore. A backtrace would be splendid. Could you install -dbg packages as well as gdb, change params to have apps emit a coredump and then get us a backtrace? Or just run fsodeviced directly under gdb and once it dies get us a backtrace. Cheers, :M: Here is a backtrace with -dbg packages: (gdb) bt #0 gee_map_get_keys (self=0x0) at map.c:353 #1 0x40b415d8 in router_lib_alsa_real_isScenarioAvailable (base=value optimized out, scenario=0x6b128 gsmhandset) at plugin.c:434 #2 0x40863fc4 in fso_device_base_audio_router_isScenarioAvailable (self=0x0, scenario=0x6b128 gsmhandset) at audiorouter.c:294 #3 0x40864a98 in fso_device_audio_router_isScenarioAvailable (self=0x16918, scenario=0x6b128 gsmhandset) at audiorouter.c:128 #4 0x40b4e600 in hardware_audio_manager_real_push_scenario_co (base=0x1a8a8, scenario=0x6d6e8 gsmhandset, _callback_=0x400be224, _user_data_=0x6f8c0) at plugin.c:826 #5 hardware_audio_manager_real_push_scenario (base=0x1a8a8, scenario=0x6d6e8 gsmhandset, _callback_=0x400be224, _user_data_=0x6f8c0) at plugin.c:799 #6 0x400aee18 in free_smartphone_device_audio_push_scenario () from /usr/lib/libfso-glib.so.0 #7 0x400b0a84 in free_smartphone_device_audio_dbus_message () from /usr/lib/libfso-glib.so.0 #8 0x40b4ed20 in hardware_audio_manager_dbus_message (connection=0x1f118, message=0x1f4b0, object=0x1a8a8) at plugin.c:1431 #9 0x40357cd4 in ?? () from /lib/libdbus-1.so.3 #10 0x40357cd4 in ?? () from /lib/libdbus-1.so.3 -- Sebastian signature.asc Description: Digital signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] phonfsod/phoneuid: fso-deviced killed when calling
On Sun, Feb 21, 2010 at 09:29:49PM +0100, Michael 'Mickey' Lauer wrote: Am Sonntag, den 21.02.2010, 19:21 +0100 schrieb arne anka: investigating my core issue of the fr not suspending anymore after a call, i see now that fsodeviced dies the moment i hit either call (outgoing) or accept (incoming). since fso-deviced is dead, nothing, in terms of idle notification at least, happens anymore. A backtrace would be splendid. Could you install -dbg packages as well as gdb, change params to have apps emit a coredump and then get us a backtrace? Or just run fsodeviced directly under gdb and once it dies get us a backtrace. Cheers, :M: Hi, You fixed this already in [1]. fso-deviced in Debian is still from Janurary 2010, because of the added libnl2 depdendency [2] from libfso* in newer versions. I just uploaded a new fso-deviced package adding a -dbg package and the referenced patch. -- Sebastian [1] http://git.freesmartphone.org/?p=cornucopia.git;a=commit;h=4c7979f5c19ab74c7c161d1d393677cb98f560d4 [2] http://ftp-master.debian.org/new/libnl2_1.99+git20091216-1.html signature.asc Description: Digital signature ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [debian] phonfsod/phoneuid: fso-deviced killed when calling
Am Sonntag, den 21.02.2010, 19:21 +0100 schrieb arne anka: investigating my core issue of the fr not suspending anymore after a call, i see now that fsodeviced dies the moment i hit either call (outgoing) or accept (incoming). since fso-deviced is dead, nothing, in terms of idle notification at least, happens anymore. A backtrace would be splendid. Could you install -dbg packages as well as gdb, change params to have apps emit a coredump and then get us a backtrace? Or just run fsodeviced directly under gdb and once it dies get us a backtrace. Cheers, :M: ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
