Re: QtMoko v24
Thanks for v24! On Tue, Jun 01, 2010 at 08:11:10AM +0200, Radek Polak wrote: 6/ Disable logging. Either from GUI in Settings-Logging or from command line: update-rc.d -f klogd remove update-rc.d -f sysklogd remove I've gone for a less radical approach, as most of the loglines came from qtopia: in /etc/init.d/qpe.sh change the line that starts qpe in qpe 21 | logger -p local5.debug -t 'Qtopia' than use /etc/syslog.conf to only log important info (see man syslog.conf) Gyelt -- Arbeitstagebuch http://ergoarte.ch/arte/blog/de_index.html ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Qtmoko] v23 doesn't recognize when headphone gets plugged in
Answering myself after getting an answer from radekp by irc: On Wed, May 19, 2010 at 10:51:13AM +0200, g...@ergoarte.ch wrote: I found that qtmoko [v23] doesn't recognize when I plug in the headphones: sound comes from the headphones as well as the speakers. The scenario-files seem to be oke (a diff gsmhandset.state and gsmheadset.state shows the volumes that should be changed). Is this a known problem? It is a known problem, for kernel 2.6.32 it is unknown how to use the trigger event. Workaround: manually switch using these commands: # for headset sound alsactl -f /usr/share/openmoko/scenarios/headset.state restore # for speakersound alsactl -f /usr/share/openmoko/scenarios/stereoout.state restore Of course this means that the phone rings via the headset only. Gyelt -- Arbeitstagebuch http://ergoarte.ch/arte/blog/de_index.html ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[Qtmoko] v23 doesn't recognize when headphone gets plugged in
Hi, I'm trying out qtmoko (v23) for the first time and I like it so far. I found that qtmoko doesn't recognize when I plug in the headphones: sound comes from the headphones as well as the speakers. The scenario-files seem to be oke (a diff gsmhandset.state and gsmheadset.state shows the volumes that should be changed). Is this a known problem? I didn't find anything in the archive, the wiki or google about this. As I understand, a different scenario should be loaded on the plugin event, but I don't know by which programm. I'd be happy to provide more info if needed. Gyelt -- Arbeitstagebuch http://ergoarte.ch/arte/blog/de_index.html ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [Debian] Zhone no longer working
On Sat, Apr 24, 2010 at 11:14:13AM +0100, Neil Jerram wrote: On 23 April 2010 16:17, g...@ergoarte.ch wrote: 2010-04-23T14:48:16.961873Z [ERROR] UsageController 7 R: Resource GSM can't be enabled: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.. Trying to disable instead What happens if you kill zhone and start it again? For example, in a terminal: # killall zhone # zhone It may just be that the FSO subsystems weren't ready when zhone started the first time, and so restarting it will help. Thanks for the suggestion, but it doesn't make a difference. Neither does restarting dbus, fso-deviced and fso-frameworkd. What to think of the following; shouldn't it be possible to switch the gsm on/off without the rxerr? Is this related? [1]+ tail -f /var/log/syslog debian-gta02:~# cat /sys/bus/platform/devices/neo1973-pm-gsm.0/power_on 0 debian-gta02:~# echo 1 /sys/bus/platform/devices/neo1973-pm-gsm.0/power_on Apr 24 13:02:29 debian-gta02 kernel: [21474792.29] rxerr: port=0 ch=0x00, rxs=0x000c Apr 24 13:02:29 debian-gta02 kernel: [21474792.345000] modem wakeup interrupt Apr 24 13:02:31 debian-gta02 kernel: [21474793.73] modem wakeup interrupt debian-gta02:~# echo 1 /sys/bus/platform/devices/neo1973-pm-gsm.0/power_on debian-gta02:~# cat /sys/bus/platform/devices/neo1973-pm-gsm.0/power_on 1 debian-gta02:~# echo 0 /sys/bus/platform/devices/neo1973-pm-gsm.0/power_on debian-gta02:~# Apr 24 13:02:45 debian-gta02 kernel: [21474807.99] rxerr: port=0 ch=0x00, rxs=0x000c debian-gta02:~# echo 0 /sys/bus/platform/devices/neo1973-pm-gsm.0/power_on debian-gta02:~# cat /sys/bus/platform/devices/neo1973-pm-gsm.0/power_on 0 debian-gta02:~# echo 1 /sys/bus/platform/devices/neo1973-pm-gsm.0/power_on Apr 24 13:03:15 debian-gta02 kernel: [1.60] rxerr: port=0 ch=0x00, rxs=0x000c Apr 24 13:03:15 debian-gta02 kernel: [1.655000] modem wakeup interrupt Apr 24 13:03:16 debian-gta02 kernel: [3.025000] modem wakeup interrupt debian-gta02:~# echo 1 /sys/bus/platform/devices/neo1973-pm-gsm.0/power_on debian-gta02:~# Gyelt -- Arbeitstagebuch http://ergoarte.ch/arte/blog/de_index.html ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[Debian] Zhone no longer working
Hi, I would be thankful for a pointer as to how get Zhone working again. I am currently running a vanilla Debian unstable with kernel 2.6.29-20100118.gita15608f2 on my Freerunner (from SD-card). /etc/frameworkd.conf has ti_calypso_muxer = fso-abyss Zhone seems to hang at requesting GSM. It's logfile says: [...] 2010-04-23 16:47:51,725 DEBUG failcount = 0 2010-04-23 16:47:51,732 DEBUG dbus_objectInitOK! 2010-04-23 16:47:51,770 DEBUG Requesting resource list 2010-04-23 16:47:51,858 DEBUG Requesting resource GSM 2010-04-23 16:52:01,031 INFO IDLE STATE = busy Fsousaged says: [...] 2010-04-23T14:47:51.873840Z [DEBUG] UsageController 7 R: Current users for GSM = [] 2010-04-23T14:48:02.633852Z [DEBUG] UsageController 7 R: org.freesmartphone.omuxerd disappeared. checking whether resources are affected... 2010-04-23T14:48:02.643641Z [DEBUG] UsageController 7 R: :1.19 disappeared. checking whether resources are affected... 2010-04-23T14:48:16.961873Z [ERROR] UsageController 7 R: Resource GSM can't be enabled: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.. Trying to disable instead I don't understand what to check from the error-text. Google only had one reference (http://www.mail-archive.com/shr-u...@lists.shr-project.org/msg02867.html) but that thread about SHR didn't offer a solution Syslog reports a kernel error, don't understand what that means either... Apr 23 16:45:44 debian-gta02 kernel: [ 998.57] s3c2440-sdi s3c2440-sdi: powered down. Apr 23 16:45:45 debian-gta02 kernel: [ 998.57] s3c2440-sdi s3c2440-sdi: powered down. Apr 23 16:47:55 debian-gta02 kernel: [ 1132.00] modem wakeup interrupt Apr 23 16:47:56 debian-gta02 kernel: [ 1133.38] modem wakeup interrupt Apr 23 16:48:00 debian-gta02 kernel: [ 1136.615000] rxerr: port=0 ch=0x00, rxs=0x000c Apr 23 16:48:17 debian-gta02 kernel: [ 1154.30] rxerr: port=0 ch=0x00, rxs=0x000c I'm happy to provide more info... Thanks in advance Gyelt ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: FatFingerShell vt with fullscreen keyboard
Hi, On Fri, Mar 27, 2009 at 04:03:29AM -0300, Rafael Ignacio Zurita wrote: Hello people, it is a new virtual terminal for Openmoko, with a complete fullscreen keyboard and sound. How to test: - download the package: http://fz.hobby-site.org/om/fatfingershell/fatfingershell_0.1.tar.gz - install libsdl, libsdl_mixer, libsdl_ttf packages - add export TERM=vt100 into ~/.bashrc - you need installed bash tar xvzf fatfingershell_0.1.tar.gz cd fatfingershell/ ./fatfingershell.sh If you have problems check fatfingershell.sh script to realize out how to run this version manually. I like shell :-) After following the instructions, I tried: debian-gta02:/usr/local/src/fatfingershell# ./fatfingershell.sh snd_pcm_oss45352 0 snd_mixer_oss 15080 1 snd_pcm_oss snd_pcm75084 3 snd_soc_s3c24xx,snd_soc_core,snd_pcm_oss snd49988 9 snd_soc_neo1973_gta02_wm8753,snd_soc_wm8753,snd_soc_core,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer dark1!=3 ./fatfingershell: invalid option -- 'e' 0-0-73-124-w-w-1 75-1-125-123-q-Q-2 129-0-180-123-w-W-1 [...] 422-381-476-479-.--4 478-381-561-478-b-b-3 563-381-638-479-f-f-4 No se pudo iniciar el modo grafico No video mode large enough for 640x480 debian-gta02:/usr/local/src/fatfingershell# I am running Debian with Xglamo and xfce4. Hmm, xrandr doesn't want to change the display, exits with 0 though. It used to work - will get back to you. Gyelt ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [ogsmd] Out-of-spec GSM number - who should I report to?
Hi, On Thu, Jan 15, 2009 at 04:54:36PM +0100, Michael Lauer wrote: See #215, which I have just fixed in master. #215 in trac.freesmartphone.org is a suspend issue - I don't understand the relation to the ogmsd warning? Gyelt ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: [ogsmd] Out-of-spec GSM number - who should I report to?
Hi, Thanks for responding! On Mon, Jan 12, 2009 at 12:46:34PM +0100, Daniel Willmann wrote: On Wed, 7 Jan 2009 09:28:09 +0100 g...@ergoarte.ch wrote: I am seeing this error: Jan 7 09:08:52 debian-gta02 2009.01.07 09:08:52 ogsmdWARNING Out-of-spec GSM number type seen: 160. Please report. This is binary b1010 which means according to GSM 03.40, page 35 type-of-number: National Number, numbering-plan-identification: Unknown It's definitely not out of spec and probably not even that unusual. The phonebookTupleToNumber function in gsm/const.py doesn't seem to be very smart. I started working on some functions for GSM addresses in the PDUAddress class in gsm/sms.py. In any case this shouldn't have any impact on functionality since it just prints out the warning. I would like to report this, but where? What extra information would be of interest? All FSO related bugs should go to http://trac.freesmartphone.org/ Done, ticket #316 I experienced the same hangs that you mentioned recently. I'm unable to answer the phone and the phone will keep ringing forever. I'm not sure these are related. I get a forever ringing phone just by dailing it and cancelling the call just before or after the neo starts ringing/vibrating. Seems it doesn't receive/process the cancelation. Please try to reproduce the problem with log_level set to DEBUG in [ogsmd] and post your log. I attached it to the ticket. Gyelt ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[ogsmd] Out-of-spec GSM number - who should I report to?
Hi, I am seeing this error: Jan 7 09:08:52 debian-gta02 2009.01.07 09:08:52 ogsmdWARNING Out-of-spec GSM number type seen: 160. Please report. I would like to report this, but where? What extra information would be of interest? Gyelt ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
[Debian] ogsmd: Out-of-spec GSM number as cause of hangs?
Hi, I'm seeing the error ogsmd WARNING Out-of-spec GSM number type seen: 160. Please report. in my logfiles. Might this be the cause of the hangs on incoming calls I am consistently getting today? After a reboot, as the call comes in, Zhone shows the screen incoming, but does not react to input. The neo then is pingable by usb, but established ssh-sessions hang on any filesystem access, like sync, which may be because of the error (see below) at the end: kernel: glamo-mci glamo-mci.0: Error after cmd: 0x8312 Shutdown by 10sec powerbutton works. I'm using Debian as is installed on an SD card: # uname -a Linux debian-gta02 2.6.24-20081103.git7172ec57 #1 PREEMPT Wed Dec 17 18:06:43 UTC 2008 armv4tl GNU/Linux I'm not sure how to continue tracing this problem and not sure how long it exsist as I use my phone mostly for very infrequent incoming calls. Please let me know if I should provide more info / where I can get more info. As this is my first post here: I'm not a big-time programmer, but am using linux in a small home network for many years now. Gyelt Tuinstra -- The relevant part of the logfile: Dec 27 15:02:24 debian-gta02 2008.12.27 15:02:24 oeventsd INFO Receive IdleState, status = idle Dec 27 15:02:24 debian-gta02 last message repeated 2 times Dec 27 15:02:31 debian-gta02 2008.12.27 15:02:31 ogsmdINFO subsystem PHB readyness now True Dec 27 15:02:31 debian-gta02 2008.12.27 15:02:31 ogsmd.objects INFO sim ready status True Dec 27 15:02:31 debian-gta02 2008.12.27 15:02:31 ogsmdINFO full readyness now True Dec 27 15:02:34 debian-gta02 2008.12.27 15:02:34 ogsmdWARNING Out-of-spec GSM number type seen: 160. Please report. Dec 27 15:02:44 debian-gta02 2008.12.27 15:02:44 odeviced.idlenotifier INFO odeviced.idlenotifier state change to idle_dim Dec 27 15:02:44 debian-gta02 2008.12.27 15:02:44 oeventsd INFO DebugAction : dbus trigger test Dec 27 15:02:44 debian-gta02 2008.12.27 15:02:44 oeventsd INFO Receive IdleState, status = idle_dim Dec 27 15:02:44 debian-gta02 2008.12.27 15:02:44 oeventsd INFO Receive IdleState, status = idle_dim Dec 27 15:02:44 debian-gta02 2008.12.27 15:02:44 oeventsd INFO call dbus signal /org/freesmartphone/Device/Display/pcf50633_bl SetBrightness((20,)) Dec 27 15:02:44 debian-gta02 2008.12.27 15:02:44 oeventsd INFO Receive IdleState, status = idle_dim Dec 27 15:02:44 debian-gta02 2008.12.27 15:02:44 oeventsd INFO signal SetBrightness responded : () Dec 27 15:02:48 debian-gta02 2008.12.27 15:02:48 ogsmd.objects INFO org.freesmartphone.GSM.Network.SignalStrength: 75 Dec 27 15:02:56 debian-gta02 2008.12.27 15:02:56 odeviced.idlenotifier INFO odeviced.idlenotifier state change to idle_prelock Dec 27 15:02:56 debian-gta02 2008.12.27 15:02:56 oeventsd INFO DebugAction : dbus trigger test Dec 27 15:02:56 debian-gta02 2008.12.27 15:02:56 oeventsd INFO Receive IdleState, status = idle_prelock Dec 27 15:02:56 debian-gta02 last message repeated 2 times Dec 27 15:02:56 debian-gta02 2008.12.27 15:02:56 oeventsd INFO call dbus signal /org/freesmartphone/Device/Display/pcf50633_bl SetBrightness((0,)) Dec 27 15:02:56 debian-gta02 2008.12.27 15:02:56 oeventsd INFO signal SetBrightness responded : () Dec 27 15:02:58 debian-gta02 2008.12.27 15:02:58 odeviced.idlenotifier INFO odeviced.idlenotifier state change to lock Dec 27 15:02:58 debian-gta02 2008.12.27 15:02:58 oeventsd INFO DebugAction : dbus trigger test Dec 27 15:02:58 debian-gta02 2008.12.27 15:02:58 oeventsd INFO Receive IdleState, status = lock Dec 27 15:02:58 debian-gta02 last message repeated 2 times Dec 27 15:03:03 debian-gta02 2008.12.27 15:03:03 odeviced.idlenotifier INFO odeviced.idlenotifier state change to busy Dec 27 15:03:03 debian-gta02 2008.12.27 15:03:03 oeventsd INFO DebugAction : dbus trigger test Dec 27 15:03:03 debian-gta02 2008.12.27 15:03:03 oeventsd INFO Receive IdleState, status = busy Dec 27 15:03:04 debian-gta02 2008.12.27 15:03:04 oeventsd INFO call dbus signal /org/freesmartphone/Device/Display/pcf50633_bl SetBrightness((90,)) Dec 27 15:03:04 debian-gta02 2008.12.27 15:03:04 oeventsd INFO Receive IdleState, status = busy Dec 27 15:03:04 debian-gta02 2008.12.27 15:03:04 oeventsd INFO Receive IdleState, status = busy Dec 27 15:03:04 debian-gta02 2008.12.27 15:03:04 oeventsd INFO signal SetBrightness responded : () Dec 27 15:03:14 debian-gta02 2008.12.27 15:03:14 odeviced.idlenotifier INFO odeviced.idlenotifier state change to idle Dec 27 15:03:14 debian-gta02 2008.12.27 15:03:14 oeventsd INFO DebugAction : dbus trigger test Dec 27 15:03:14 debian-gta02 2008.12.27 15:03:14 oeventsd INFO Receive IdleState, status = idle Dec 27 15:03:14 debian-gta02 last message repeated 2 times Dec 27 15:03:25 debian-gta02 2008.12.27 15:03:25 ogsmd.objects INFO org.freesmartphone.GSM.Network.SignalStrength: 86 Dec 27
