Re: Sound quality in calls.
On Tue, 16 Sep 2008, Daniel Hedblom wrote: If anyone has a good /usr/share/openmoko/scenarios/gsmhanset.state where sound incalls is good i really would love to have it. Ive been fiddling with it in every way possible, tried all the distributions there is (debian, FSO mk II and III, OM2008.x and qtopia ) and almost sacrificed a small mammal just to be sure. I just want to make sure the hardware on my phone isnt broken since everyone i talk to mentions appalingly bad sound when i talk to them. Not just echo but the volume they hear when i talk to them on the FR is very low. you can find mine at http://www.teaparty.net/technotes/openmoko-2.html#Audio-to-other-mobiles . i basically sacrificed speaker volume for mic gain; other people can hear me much better, but i can only hear them if there's not too much background noise. i experimented yesterday with turning on the hardware echo cancellation, and that worked for one call (allowed me to increase Speaker Playback Volume to 117) but then things went back to being very echoey. so unless i'm willing to have a minicom session at the beginning of every call, that's not usable right now; i'll have to wait until the AT%N0187 is integrated into qtopia's call-handling logic. i have tried florian hackenberger's patched qtopia-phone-x11-phonevendor-ficgta01vendor (see http://docs.openmoko.org/trac/ticket/1267 ; thanks, florian!) but it doesn't apply cleanly against the latest 2008.08 (version too old), and when i used -force-downgrade my qpe's CPU usage went to 100% for 40 minutes, while the phone failed to register with the network. so i backed it out :( . hope some of that helps. -- Tom Yates - http://www.teaparty.net ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sound quality in calls.
Hi, Thanks! Now i get pretty decent volume. Albeit with static bzz but people can atleast hear me. I think this would be nice to have on the Wiki since most references about mic talks about changing mic2 in alsa and nothing about Mono Playback Volume. Maybe someone with more insight could write up a quickie? //danielh 2008/9/17 Tom Yates [EMAIL PROTECTED]: On Tue, 16 Sep 2008, Daniel Hedblom wrote: If anyone has a good /usr/share/openmoko/scenarios/gsmhanset.state where sound incalls is good i really would love to have it. Ive been fiddling with it in every way possible, tried all the distributions there is (debian, FSO mk II and III, OM2008.x and qtopia ) and almost sacrificed a small mammal just to be sure. I just want to make sure the hardware on my phone isnt broken since everyone i talk to mentions appalingly bad sound when i talk to them. Not just echo but the volume they hear when i talk to them on the FR is very low. you can find mine at http://www.teaparty.net/technotes/openmoko-2.html#Audio-to-other-mobiles . i basically sacrificed speaker volume for mic gain; other people can hear me much better, but i can only hear them if there's not too much background noise. i experimented yesterday with turning on the hardware echo cancellation, and that worked for one call (allowed me to increase Speaker Playback Volume to 117) but then things went back to being very echoey. so unless i'm willing to have a minicom session at the beginning of every call, that's not usable right now; i'll have to wait until the AT%N0187 is integrated into qtopia's call-handling logic. i have tried florian hackenberger's patched qtopia-phone-x11-phonevendor-ficgta01vendor (see http://docs.openmoko.org/trac/ticket/1267 ; thanks, florian!) but it doesn't apply cleanly against the latest 2008.08 (version too old), and when i used -force-downgrade my qpe's CPU usage went to 100% for 40 minutes, while the phone failed to register with the network. so i backed it out :( . hope some of that helps. -- Tom Yates - http://www.teaparty.net ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: (om2008.8-update)(gta02) qpe hogs 80% of cpu, kills battery
On Wed, 17 Sep 2008, [EMAIL PROTECTED] wrote:
Help!
Woke up today with a dead phone. After recharging, I saw qpe is
permanently hogging all the CPU.
i have the same, currently fully-updated to angstrom version P1-Snapshot-
20080916:
root 1724 92.0 22.9 95072 28404 ?Rl 06:56 313:04 qpe
the 'phone's been up 6 hours 14 minutes; qpe has used 5h13m of CPU in
that time, which has got to be all the spare cycles i've had.
i am using gsm0710muxd, which i thought might be responsible, but calling
out, calling in, SMS etc. are working fine, so i don't really know what to
think. it makes the 'phone very slow!
strace on the qpe process shows it stuck in what looks a lot like a tight
loop; any thoughts?
[pid 1724] SYS_298(0x10002, 0xbefaf024, 0x2, 0x1, 0x18fb68) = -1 ERANGE
(Numerical result out of range)
[pid 1724] stat64(/home/root/.config/Trolltech/qtmail_account.conf,
{st_mode=S_IFREG|0600, st_size=3419, ...}) = 0
[pid 1724] open(/home/root/.config/Trolltech/qtmail_account.conf,
O_RDONLY|O_LARGEFILE) = 33
[pid 1724] close(33) = 0
[pid 1724] stat64(/home/root/.config/Trolltech/qtmail_account.conf,
{st_mode=S_IFREG|0600, st_size=3419, ...}) = 0
[pid 1724] stat64(/home/root/.config/Trolltech/qtmail_account.conf,
{st_mode=S_IFREG|0600, st_size=3419, ...}) = 0
[pid 1724] stat64(/home/root/.config/Trolltech.conf, {st_mode=S_IFREG|0600,
st_size=4470, ...}) = 0
[pid 1724] stat64(/home/root/.config/Trolltech.conf, {st_mode=S_IFREG|0600,
st_size=4470, ...}) = 0
[pid 1724] stat64(/opt/Qtopia/etc/default/Trolltech/qtmail_account.conf,
0xbefaed98) = -1 ENOENT (No such file or directory)
[pid 1724] stat64(/opt/Qtopia/etc/default/Trolltech/qtmail_account.conf,
0xa385f8) = -1 ENOENT (No such file or directory)
[pid 1724] stat64(/opt/Qtopia/etc/default/Trolltech.conf, 0xbefaed98) = -1
ENOENT (No such file or directory)
[pid 1724] stat64(/opt/Qtopia/etc/default/Trolltech.conf, 0x4cd618) = -1
ENOENT (No such file or directory)
[pid 1724] SYS_298(0x10002, 0xbefaef2a, 0x1, 0x1000, 0x18fb68) = -1 ERANGE
(Numerical result out of range)
[pid 1724] timer_delete(0x1) = 0
[pid 1724] timer_delete(0x1) = 0
[pid 1724] SYS_298(0x10002, 0xbefaf024, 0x2, 0x1, 0x18fb68) = -1 ERANGE
(Numerical result out of range)
[pid 1724] stat64(/home/root/.config/Trolltech/qtmail_account.conf,
{st_mode=S_IFREG|0600, st_size=3419, ...}) = 0
[pid 1724] open(/home/root/.config/Trolltech/qtmail_account.conf,
O_RDONLY|O_LARGEFILE) = 33
[pid 1724] close(33) = 0
[pid 1724] stat64(/home/root/.config/Trolltech/qtmail_account.conf,
{st_mode=S_IFREG|0600, st_size=3419, ...}) = 0
[pid 1724] stat64(/home/root/.config/Trolltech/qtmail_account.conf,
{st_mode=S_IFREG|0600, st_size=3419, ...}) = 0
[pid 1724] stat64(/home/root/.config/Trolltech.conf, {st_mode=S_IFREG|0600,
st_size=4470, ...}) = 0
[pid 1724] stat64(/home/root/.config/Trolltech.conf, {st_mode=S_IFREG|0600,
st_size=4470, ...}) = 0
[pid 1724] stat64(/opt/Qtopia/etc/default/Trolltech/qtmail_account.conf,
0xbefaed98) = -1 ENOENT (No such file or directory)
[pid 1724] stat64(/opt/Qtopia/etc/default/Trolltech/qtmail_account.conf,
0x4cd618) = -1 ENOENT (No such file or directory)
[pid 1724] stat64(/opt/Qtopia/etc/default/Trolltech.conf, 0xbefaed98) = -1
ENOENT (No such file or directory)
[pid 1724] stat64(/opt/Qtopia/etc/default/Trolltech.conf, 0xa385f8) = -1
ENOENT (No such file or directory)
[pid 1724] SYS_298(0x10002, 0xbefaef2a, 0x1, 0x1000, 0x18fb68) = -1 ERANGE
(Numerical result out of range)
[pid 1724] timer_delete(0x1) = 0
[pid 1724] ioctl(7, FIONREAD, [0]) = 0
[pid 1724] timer_delete(0x1) = 0
[pid 1724] timer_delete(0x1) = 0
[pid 1724] select(54, [3 7 8 9 10 11 12 19 21 24 25 26 27 31 36 38 39 41 43 49
53], [9], [], {0, 0}) = 2 (in [3], out [9], left {0, 0})
[pid 1724] timer_delete(0x1) = 0
[pid 1724] read(3, \0, 16) = 1
[pid 1724] read(3, 0xbefb05e4, 16) = -1 EAGAIN (Resource temporarily
unavailable)
[pid 1724] SYS_296(0x9, 0xbefafb0c, 0x4040, 0, 0) = 256
[pid 1724] SYS_296(0x9, 0xbefafaa4, 0x4040, 0, 0) = 256
[pid 1724] timer_delete(0x1) = 0
[pid 1724] write(4, \0, 1) = 1
[pid 1724] SYS_298(0x10002, 0xbefaf024, 0x2, 0x1, 0x18fb68) = -1 ERANGE
(Numerical result out of range)
--
Tom Yates - http://www.teaparty.net
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
Re: (om2008.8-update)(gta02) qpe hogs 80% of cpu, kills battery
On Wed, Sep 17, 2008 at 5:21 PM, Tom Yates [EMAIL PROTECTED] wrote:
[pid 1724] stat64(/home/root/.config/Trolltech.conf,
{st_mode=S_IFREG|0600, st_size=4470, ...}) = 0
[pid 1724] stat64(/opt/Qtopia/etc/default/Trolltech/qtmail_account.conf,
0xbefaed98) = -1 ENOENT (No such file or directory)
[pid 1724] stat64(/opt/Qtopia/etc/default/Trolltech/qtmail_account.conf,
0xa385f8) = -1 ENOENT (No such file or directory)
[pid 1724] stat64(/opt/Qtopia/etc/default/Trolltech.conf, 0xbefaed98) = -1
ENOENT (No such file or directory)
[pid 1724] stat64(/opt/Qtopia/etc/default/Trolltech.conf, 0x4cd618) = -1
ENOENT (No such file or directory)
Hope you won't mind a possibly silly question, but: is your Qtopia
rootfs on SDcard or on NAND flash?
Cheers
Ed.
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
Re: Sound quality in calls.
On Wednesday 17 September 2008, Daniel Hedblom wrote: Hi, Thanks! Now i get pretty decent volume. Albeit with static bzz but people can atleast hear me. I think this would be nice to have on the Wiki since most references about mic talks about changing mic2 in alsa and nothing about Mono Playback Volume. Maybe someone with more insight could write up a quickie? Controls affecting handset mic volume for GSM: Control 48: Mic2 Capture Volume Control 12: Mono Sidetone Playback Volume Control 5: Mono Playback Volume Controls affecting wired headset mic volume for GSM: Control 49: Mic1 Capture Volume Control 12: Mono Sidetone Playback Volume Control 5: Mono Playback Volume ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: (om2008.8-update)(gta02) qpe hogs 80% of cpu, kills battery
Citando Edgar D' Souza [EMAIL PROTECTED]:
On Wed, Sep 17, 2008 at 5:21 PM, Tom Yates [EMAIL PROTECTED] wrote:
[pid 1724] stat64(/home/root/.config/Trolltech.conf,
{st_mode=S_IFREG|0600, st_size=4470, ...}) = 0
[pid 1724]
stat64(/opt/Qtopia/etc/default/Trolltech/qtmail_account.conf,
0xbefaed98) = -1 ENOENT (No such file or directory)
[pid 1724]
stat64(/opt/Qtopia/etc/default/Trolltech/qtmail_account.conf,
0xa385f8) = -1 ENOENT (No such file or directory)
[pid 1724] stat64(/opt/Qtopia/etc/default/Trolltech.conf,
0xbefaed98) = -1 ENOENT (No such file or directory)
[pid 1724] stat64(/opt/Qtopia/etc/default/Trolltech.conf,
0x4cd618) = -1 ENOENT (No such file or directory)
Hope you won't mind a possibly silly question, but: is your Qtopia
rootfs on SDcard or on NAND flash?
It's in NAND. Only the /home dir is in the sdcard.
It is OM2008.8-upd (ex-ASU), not Qtopia itself.
Cheers
Ed.
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support
Re: [Om2008.8 - testing] - alsa: No soundcards found...
i updated now, to the testing version of Om2008.8. there is still this message in dmesg: Only GTA01 hardware supported by ASoc driver i know that my sound worked a few weeks ago. And yes i have installed a gta02 kernel. So i think there is a bug in the gta02 kernel buildhost, or my opkg upgrade didn't update the runnnig kernel image? how could i check, if my system is realy booting the right kernel? Benedikt Schindler schrieb: i now found in dmesg this: ASoC version 0.13.1 wm8753: WM8753 Audio Codec 0.16 Only GTA01 hardware supported by ASoc driver but if i do a lsmod he sayed i have installed: snd_soc_neo1973_gta02_wm8753 i also have installed a gta02 kernel. so does annyone have suggestions what module is in the wrong version? and where do i get the right one? Benedikt Schindler schrieb: Device: GTA02 Distro: om2008.8 version: unstable Last update/upgrade: today does someone know this problem: --- [EMAIL PROTECTED]:~# opkg upgrade Configuring alsa-state System startup links for /etc/init.d/alsa-state already exist. /usr/sbin/alsactl: load_state:1327: No soundcards found... postinst script returned status 237 Collected errors: * ERROR: alsa-state.postinst returned 237 ___ Openmoko community mailing list [EMAIL PROTECTED] http://lists.openmoko.org/mailman/listinfo/community ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
What's wrong with gpsd
These happened with FSO milestone 2 and 3 Case 1:I turn on GPS, start gpsd and start Tango gps. Even if I read the NMEA stamps with cat /dev/ttySAC1, TangoGPS still reports 0 satellites and gps tome of 1 Jan 1970 Case 2: Turn on GPS, start gpsd, run xgps 192.168.0.202, and xgps hangs Case 3: Turn on GPS, instead of running gpsd, shovel NMEA using nc 192.168.0.200 /dev/ttySAC1 and run gpsd on my PC, then xgps runs normally. So something is definitely wrong with gpsd on FR. Am I the only one with this? -- - Bu mesaj UTF-8 ile kodlanmıştır - Atilla Filiz Technische Universiteit Eindhoven Embedded Systems, Master's Programme ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: What's wrong with gpsd
On Wednesday 17 September 2008, Atilla Filiz wrote: These happened with FSO milestone 2 and 3 Case 1:I turn on GPS, start gpsd and start Tango gps. Even if I read the NMEA stamps with cat /dev/ttySAC1, TangoGPS still reports 0 satellites and gps tome of 1 Jan 1970 Case 2: Turn on GPS, start gpsd, run xgps 192.168.0.202, and xgps hangs Case 3: Turn on GPS, instead of running gpsd, shovel NMEA using nc 192.168.0.200 /dev/ttySAC1 and run gpsd on my PC, then xgps runs normally. So something is definitely wrong with gpsd on FR. Am I the only one with this? The problem is that you're running gpsd on FSO! As part of the framework FSO provides a gps daemon (ogpsd?) that uses the gypsy dbus interface. There's a compatibility package that lets it output in gpsd format so that apps expecting gpsd will also work - you should be able to find it with: opkg list |grep gps If you run gpsd at the same time as the FSO daemon they will compete for the serial port, probably breaking them both. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: (om2008.8-update)(gta02) qpe hogs 80% of cpu, kills battery
Citando Tom Yates [EMAIL PROTECTED]: Hope you won't mind a possibly silly question, but: is your Qtopia rootfs on SDcard or on NAND flash? NAND flash, as is /home/root. i have the SDcard mounted on /media/card, and i only keep audio tracks and OSM tiles on it. So we both have our OSM tiles in the sdcard... (naturally!) QPE is clever enough to know which partition is a card; when my sdcard was a FAT partition in /media/card, it created it's qtopia_db.sqlite file there; now that the card is an ext2 mounted at /home, it creates the file there (I deleted it to check). So it may have a special fetish about media cards... and index all files on them, independently of mount point (my theory). If you strace qpe 21 | grep open and wait 5 minutes, do you see QPE opening your /media/card files a lot? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: (om2008.8-update)(gta02) qpe hogs 80% of cpu, kills battery
Citando Yaroslav Halchenko [EMAIL PROTECTED]: if you have lots of files on your /media/card -- then you are doomed to wait for qpe to finish scanning them on start or just edit Storage.conf which is I believe under /opt/Qtopia/etc/default and say that your /media/card has nothing interesting for qtopia ;-) PS more details could be found in earlier posts on the lists Thanks for the hint! The file is /opt/Qtopia/etc/default/Trolltech/Storage.conf ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sound quality in calls.
On Wed, Sep 17, 2008 at 6:07 AM, Al Johnson [EMAIL PROTECTED]wrote: Controls affecting handset mic volume for GSM: Control 48: Mic2 Capture Volume Control 12: Mono Sidetone Playback Volume Control 5: Mono Playback Volume Controls affecting wired headset mic volume for GSM: Control 49: Mic1 Capture Volume Control 12: Mono Sidetone Playback Volume Control 5: Mono Playback Volume I've written a python mixer to control the mic volumes for the various headsets. The speaker volumes will be added when I trace their path through the wolfson. It'll currently control handset, wired headset and bluetooth volumes. You currently need to tell it which to control as I have not found any dbus signals to tell what alsa state you are currently in. The displayed vaolumes may be wrong if you start the volume control before the alsa state change. One you use a control to set its volume it will reflect the state of the underlying hardware. You'll need these 3 files http://handheldshell.com/python-pyalsaaudio_0.3-ml0_armv4t.ipk http://handheldshell.com/pymixer.py http://handheldshell.com/volume.desktop install pyalsaausdio and pygtk copy pymxer /usr/bin copy volume.desktop /usr/share/applications You can now control mic volume. Angus ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sound quality in calls.
Angus, we owe you a big THANKS for writing this one. :D Just a small remark: isn't Handset supposed to control Mic2 (and not Mic1)? Vasco. Angus Ainslie wrote: On Wed, Sep 17, 2008 at 6:07 AM, Al Johnson [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Controls affecting handset mic volume for GSM: Control 48: Mic2 Capture Volume Control 12: Mono Sidetone Playback Volume Control 5: Mono Playback Volume Controls affecting wired headset mic volume for GSM: Control 49: Mic1 Capture Volume Control 12: Mono Sidetone Playback Volume Control 5: Mono Playback Volume I've written a python mixer to control the mic volumes for the various headsets. The speaker volumes will be added when I trace their path through the wolfson. It'll currently control handset, wired headset and bluetooth volumes. You currently need to tell it which to control as I have not found any dbus signals to tell what alsa state you are currently in. The displayed vaolumes may be wrong if you start the volume control before the alsa state change. One you use a control to set its volume it will reflect the state of the underlying hardware. You'll need these 3 files http://handheldshell.com/python-pyalsaaudio_0.3-ml0_armv4t.ipk http://handheldshell.com/pymixer.py http://handheldshell.com/volume.desktop install pyalsaausdio and pygtk copy pymxer /usr/bin copy volume.desktop /usr/share/applications You can now control mic volume. Angus ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
[FSO] GPRS not functioning in M3
Has anyone else had their GPRS stop working since flashing FSO M3. It was working for me in M2. I've filed a bug about it[1] but no action so far. [1] http://trac.freesmartphone.org/ticket/140 -- Dylan Type faster. Use Dvorak: http://dvzine.org ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sound quality in calls.
On Wed, Sep 17, 2008 at 6:36 PM, Vasco Névoa [EMAIL PROTECTED] wrote: Angus, we owe you a big THANKS for writing this one. :D Just a small remark: isn't Handset supposed to control Mic2 (and not Mic1)? Vasco. Ooops I fixed that and added input volumes. Angus ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sound quality in calls.
On Wed, Sep 17, 2008 at 8:45 PM, Vasco Névoa [EMAIL PROTECTED] wrote: I can't see the differences online... have you uploaded the file yet? It helps if I put it in the right directory on the server. Should work now. Angus ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
