[FDOM FSO] no sound in calls
Hi all, I have my freerunner since around a month, and sound has always worked. As I've got FDOM in the flash, I tried to install the raster image, along with FSO. very nice peace of work ! but I hadn't any sound in zhone, like some others in the mailing lists, so I switched back to my FDOM. Now I neither haver sound in FDOM this used to work like a charm ! I tried to replace the state files in /usr/share/openmoko/scenarios, but this does'nt work either ... Anyone has an idea on how to solve it ? Thomas ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FDOM FSO] no sound in calls
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Hi all, | I have my freerunner since around a month, and sound has always worked. | As I've got FDOM in the flash, I tried to install the raster image, | along with FSO. very nice peace of work ! | but I hadn't any sound in zhone, like some others in the mailing lists, | so I switched back to my FDOM. | Now I neither haver sound in FDOM this used to work like a charm ! | I tried to replace the state files in /usr/share/openmoko/scenarios, but | this does'nt work either ... | Anyone has an idea on how to solve it ? Confirm in dmesg that your audio is recognized in Alsa, something interesting seems to be going on around that. Bad: ~ ALSA device list: ~ No soundcards found. Good: ~ ALSA device list: ~ #0: neo1973-gta02 (WM8753) - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjzOGYACgkQOjLpvpq7dMpCvQCghnBcKaGOTRHvkvSWAQc+ffv6 bPAAn3iooYBdkcMHHZiXv20bK2jOgu2p =+Xxb -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FDOM FSO] no sound in calls
there is no mention of alsa. neither of neo1973-gta02 ... will that be a kernel problem ? 2008/10/13 Andy Green [EMAIL PROTECTED] -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Hi all, | I have my freerunner since around a month, and sound has always worked. | As I've got FDOM in the flash, I tried to install the raster image, | along with FSO. very nice peace of work ! | but I hadn't any sound in zhone, like some others in the mailing lists, | so I switched back to my FDOM. | Now I neither haver sound in FDOM this used to work like a charm ! | I tried to replace the state files in /usr/share/openmoko/scenarios, but | this does'nt work either ... | Anyone has an idea on how to solve it ? Confirm in dmesg that your audio is recognized in Alsa, something interesting seems to be going on around that. Bad: ~ ALSA device list: ~ No soundcards found. Good: ~ ALSA device list: ~ #0: neo1973-gta02 (WM8753) - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjzOGYACgkQOjLpvpq7dMpCvQCghnBcKaGOTRHvkvSWAQc+ffv6 bPAAn3iooYBdkcMHHZiXv20bK2jOgu2p =+Xxb -END PGP SIGNATURE- ___ 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: [FDOM FSO] no sound in calls
more infos on this problem. I tried to play a sound : [EMAIL PROTECTED]:/# aplay ./opt/Qtopia/sounds/alarm.wav ALSA lib pcm_direct.c:1479:(_snd_pcm_direct_get_slave_ipc_offset) Invalid value for card aplay: main:546: audio open error: No such device then I checked the loaded modules and there is no one ! [EMAIL PROTECTED]:/# lsmod Module Size Used by How do I reload all the needed modules ? 2008/10/13 Thomas des Courières [EMAIL PROTECTED] there is no mention of alsa. neither of neo1973-gta02 ... will that be a kernel problem ? 2008/10/13 Andy Green [EMAIL PROTECTED] -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Hi all, | I have my freerunner since around a month, and sound has always worked. | As I've got FDOM in the flash, I tried to install the raster image, | along with FSO. very nice peace of work ! | but I hadn't any sound in zhone, like some others in the mailing lists, | so I switched back to my FDOM. | Now I neither haver sound in FDOM this used to work like a charm ! | I tried to replace the state files in /usr/share/openmoko/scenarios, but | this does'nt work either ... | Anyone has an idea on how to solve it ? Confirm in dmesg that your audio is recognized in Alsa, something interesting seems to be going on around that. Bad: ~ ALSA device list: ~ No soundcards found. Good: ~ ALSA device list: ~ #0: neo1973-gta02 (WM8753) - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjzOGYACgkQOjLpvpq7dMpCvQCghnBcKaGOTRHvkvSWAQc+ffv6 bPAAn3iooYBdkcMHHZiXv20bK2jOgu2p =+Xxb -END PGP SIGNATURE- ___ 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: [FDOM FSO] no sound in calls
Well, I reflashed a older kernel, and the sound is back. and in dmesg I see : [3.87] ALSA device list: [3.875000] #0: neo1973-gta02 (WM8753) so everything's back ok ! could it be that putting fso on the sdcard and upgrading it, it overwrote the kernel in the flash ? because I see that the times are back before the log line ... 2008/10/13 Thomas des Courières [EMAIL PROTECTED] more infos on this problem. I tried to play a sound : [EMAIL PROTECTED]:/# aplay ./opt/Qtopia/sounds/alarm.wav ALSA lib pcm_direct.c:1479:(_snd_pcm_direct_get_slave_ipc_offset) Invalid value for card aplay: main:546: audio open error: No such device then I checked the loaded modules and there is no one ! [EMAIL PROTECTED]:/# lsmod Module Size Used by How do I reload all the needed modules ? 2008/10/13 Thomas des Courières [EMAIL PROTECTED] there is no mention of alsa. neither of neo1973-gta02 ... will that be a kernel problem ? 2008/10/13 Andy Green [EMAIL PROTECTED] -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Hi all, | I have my freerunner since around a month, and sound has always worked. | As I've got FDOM in the flash, I tried to install the raster image, | along with FSO. very nice peace of work ! | but I hadn't any sound in zhone, like some others in the mailing lists, | so I switched back to my FDOM. | Now I neither haver sound in FDOM this used to work like a charm ! | I tried to replace the state files in /usr/share/openmoko/scenarios, but | this does'nt work either ... | Anyone has an idea on how to solve it ? Confirm in dmesg that your audio is recognized in Alsa, something interesting seems to be going on around that. Bad: ~ ALSA device list: ~ No soundcards found. Good: ~ ALSA device list: ~ #0: neo1973-gta02 (WM8753) - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkjzOGYACgkQOjLpvpq7dMpCvQCghnBcKaGOTRHvkvSWAQc+ffv6 bPAAn3iooYBdkcMHHZiXv20bK2jOgu2p =+Xxb -END PGP SIGNATURE- ___ 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: NetworkManager in Intrepid breaks my FreeRunner's Internet connection
On Mon, Oct 13, 2008 at 6:14 AM, Jeffrey Ratcliffe [EMAIL PROTECTED] wrote: 2008/10/13 digger vermont [EMAIL PROTECTED]: Recently something changed with NetworkManager in Intrepid, don't know what. With the auto usb0 line in the interfaces file NM decided that They started using the 0.7 version of NetworkManager, which isn't quite finished. it to make it the default route when I plugged it in. I could see the nm-applet going around and then a notification that I was connected to the Freerunner. Looking at connections with nm-applet there were tabs for both the wireless and usb0 with usb0 marked as default. I kinda remember an Ubuntu bug-report concerning the default route in NM. There are plenty of those. I can post them if anyone is interested. Any way my solution was to comment out auto usb0 and manually use ifup usb0 (actually sudo ifdown usb0 sudo ifup usb0 is what I use). Are you saying that you type sudo ifdown usb0 sudo ifup usb0 every time you plug in your FR? I'm beginning to conclude that I will have to remove NM and set up everything manually. Regards Jeff ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support have you tried replacing network manager with Wicd[1]. i think it has better frontend and will not have the same issue as NM. azmodie [1] http://wicd.sourceforge.net -- Due to the speed of light being faster than the speed of sound people often look bright until they speak ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Re-registering to GSM network
Ok, thank you! On Mon, Oct 13, 2008 at 1:36 PM, Michael 'Mickey' Lauer [EMAIL PROTECTED] wrote: This is Openmoko bug #1024, which essentially seems to be a bug in the TI firmware. It depends on the TI Calypso sleep mode, the traffic in the cell you're logged into, and probably also your network operator's software running on the cell towers. We're experimenting with a band-aid atm (see bug-report for the entire gloryness...). -- :M: ___ 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: closing apps in FDOM
tap on the top bar arrow and then tap remove to close the actual focused app El lun, 13-10-2008 a las 23:19 +1300, anthony winter escribió: How do you do it? What am I missing here? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Re-registering to GSM network
This is Openmoko bug #1024, which essentially seems to be a bug in the TI firmware. It depends on the TI Calypso sleep mode, the traffic in the cell you're logged into, and probably also your network operator's software running on the cell towers. We're experimenting with a band-aid atm (see bug-report for the entire gloryness...). -- :M: ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: closing apps in FDOM
2008/10/13 anthony winter [EMAIL PROTECTED] How do you do it? What am I missing here? 1. Tap on the little triangle in the upper middle of the screen. A pulldown menu appears, the current app will the be the one at the bottom of this menu. 2. Tap on REMOVE in the lower left corner of that pulldown menu. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
closing apps in FDOM
How do you do it? What am I missing here? -- anthony winter ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: NetworkManager in Intrepid breaks my FreeRunner's Internet connection
On Mon, 2008-10-13 at 07:14 +0200, Jeffrey Ratcliffe wrote: 2008/10/13 digger vermont [EMAIL PROTECTED]: Recently something changed with NetworkManager in Intrepid, don't know what. With the auto usb0 line in the interfaces file NM decided that They started using the 0.7 version of NetworkManager, which isn't quite finished. ... Any way my solution was to comment out auto usb0 and manually use ifup usb0 (actually sudo ifdown usb0 sudo ifup usb0 is what I use). Are you saying that you type sudo ifdown usb0 sudo ifup usb0 every time you plug in your FR? You have to decide where you want to spend your time. For me it isn't NM at the moment. So yeah its a a drag but I type it in. digger signature.asc Description: This is a digitally signed message part ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Re-registering to GSM network
Michael 'Mickey' Lauer wrote: This is Openmoko bug #1024, which essentially seems to be a bug in the TI firmware. It depends on the TI Calypso sleep mode, the traffic in the cell you're logged into, and probably also your network operator's software running on the cell towers. We're experimenting with a band-aid atm (see bug-report for the entire gloryness...). I would say it has more to do with firmware. I have a gta01 that does this, a gta02 prototype that does it and a production FR that does not. All using the same gui, same sim, same tower, same operator, same network traffic. Using sleep mode on my production FR, stops it from properly waking up on phone calls and sms, so this is not reliable in stopping the bouncy calypso. -- Lorn 'ljp' Potter Software Engineer, Systems Group, Qt Software, Nokia Pty Ltd ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Re-registering to GSM network
On Tue, 14 Oct 2008 04:58:51 +1000, Lorn Potter [EMAIL PROTECTED] wrote: Michael 'Mickey' Lauer wrote: This is Openmoko bug #1024, which essentially seems to be a bug in the TI firmware. It depends on the TI Calypso sleep mode, the traffic in the cell you're logged into, and probably also your network operator's software running on the cell towers. We're experimenting with a band-aid atm (see bug-report for the entire gloryness...). I would say it has more to do with firmware. I have a gta01 that does this, a gta02 prototype that does it and a production FR that does not. All using the same gui, same sim, same tower, same operator, same network traffic. Using sleep mode on my production FR, stops it from properly waking up on phone calls and sms, so this is not reliable in stopping the bouncy calypso. I'm assuming that said firmware is field-upgradeable, right? :) So once a fix is devised it won't be just for newly-produced handsets, as might be the case with 'ordinary' cellphones. ;) I'm seeing this issue on a GTA02v6 (August production) with frameworkd and zhone. Don't recall ever observing it on my previous (pre-RMA, June production) GTA02v5, but it's possible that it's just frameworkd+zhone making it more visible to me. Inquiry shows me HW: GTA02BV5, GSM: gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko8, though /proc/cpuinfo lists revision 0360. Carrier is T-Mobile in US, but I'm permanently roaming on either Suncom (being folded into T-Mobile now) or Cingular/ATT, and I've seen this happening on both roaming networks. j ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: closing apps in FDOM
Thanks for the information. Is it actually written down anywhere? But it doesn't work with 'Contacts'. If I have just 'Home' and 'Contacts' in the list it 'Contacts' does not get closed. Extra questions: 1) what is the quickest way of shutting down the neo completely? At present I am using a terminal and entering init 0. 2) What do the three little + signs at the bottom of the screen do? 3) What is the * at the bottom left for? 4) What does the (possibly) spanner-like symbol at the top right do? In other words - where is there a description of this user interface!? On Tue, 14 Oct 2008, you wrote: 2008/10/13 anthony winter [EMAIL PROTECTED] How do you do it? What am I missing here? 1. Tap on the little triangle in the upper middle of the screen. A pulldown menu appears, the current app will the be the one at the bottom of this menu. 2. Tap on REMOVE in the lower left corner of that pulldown menu. -- anthony winter ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Re-registering to GSM network
Joel Newkirk wrote: On Tue, 14 Oct 2008 04:58:51 +1000, Lorn Potter [EMAIL PROTECTED] wrote: Michael 'Mickey' Lauer wrote: This is Openmoko bug #1024, which essentially seems to be a bug in the TI firmware. It depends on the TI Calypso sleep mode, the traffic in the cell you're logged into, and probably also your network operator's software running on the cell towers. We're experimenting with a band-aid atm (see bug-report for the entire gloryness...). I would say it has more to do with firmware. I have a gta01 that does this, a gta02 prototype that does it and a production FR that does not. All using the same gui, same sim, same tower, same operator, same network traffic. Using sleep mode on my production FR, stops it from properly waking up on phone calls and sms, so this is not reliable in stopping the bouncy calypso. I'm assuming that said firmware is field-upgradeable, right? :) So once a fix is devised it won't be just for newly-produced handsets, as might be the case with 'ordinary' cellphones. ;) I'm seeing this issue on a GTA02v6 (August production) with frameworkd and zhone. Don't recall ever observing it on my previous (pre-RMA, June production) GTA02v5, but it's possible that it's just frameworkd+zhone making it more visible to me. Inquiry shows me HW: GTA02BV5, GSM: gsm_ac_gp_fd_pu_em_cph_ds_vc_cal35_ri_36_amd8_ts0-Moko8, though /proc/cpuinfo lists revision 0360. Carrier is T-Mobile in US, but I'm permanently roaming on either Suncom (being folded into T-Mobile now) or Cingular/ATT, and I've seen this happening on both roaming networks. This bug seems to be much worse with ATT than T-mobile. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
