Re: [debian] Xorg fails to start after upgrade to 1.7.7
Hi, e.waelde a écrit , Le 11/07/2010 09:26: (EE) Error compiling keymap (server-0) (EE) XKB: Couldn't compile keymap XKB: Failed to compile keymap Keyboard initialization failed. This could be a missing or incorrect setup of xkeyboard-config. The culprit is the package x11-xkb-utils. Reverting it to release 7.5+2 from snapshot.debian.org [1] solves the problem. _g. [1] http://snapshot.debian.org/archive/debian/20100315T215308Z/pool/main/x/x11-xkb-utils/x11-xkb-utils_7.5%2B2_armel.deb signature.asc Description: OpenPGP digital signature ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: fso-frameworkd - ogpsd as a gpsd client
Michael 'Mickey' Lauer a écrit , Le 12/05/2010 11:43: thanks for the patch! While that's cool, it's somewhat perverted to use gpsd as source for the gypsy API, especially when almost noone is using the gypsy API anymore (not that it wasn't used at any time). Note that this will also remove the 'A' of our AGPS, i.e. we will not be able to upload any ephemeris anymore to improve location. AFAIK will also limit precision -- or is gpsd able to speak UBX these days? Please note that my intent is just to be able to run gpsd client apps while having ogpsd enabled. As I've stated in a previous email, I don't want to have to switch between ogpsd and gpsd depending on the client GPS app I launch. This patch isn't destructive: it adds a channel and two device types so that one can choose to set ogpsd as a gpsd client. About A(GPS) I must admit I have no idea yet. If gpsd has the API to upload ephemeris then the solution should be obvious. But TBH I don't know right now :/ BTW, with the gpsd client mode I haven't noticed longer fix times than with the standard GTA02Device mode. Cheers, _g. signature.asc Description: OpenPGP digital signature ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
fso-frameworkd - ogpsd as a gpsd client
Hi,
For what it's worth, here is a patch against fso-frameworkd(*) to make
ogpsd a gpsd client.
To use it change these three options in /etc/frameworkd:
[ogpsd]
device = GTA02GpsdDevice
channel = ClientSocketChannel
path = localhost:2947
While it surely needs some polishing - especially regarding the error
handling - it seems functional enough for the Zhone GPS feature.
Please bear with my code: I'm a python noob. Any improvement is welcome :)
BTW I've a doubt about the seed and climb units. AIUI it seems to be
knots, be I'd appreciate if someone could confirm.
Thanks,
_g.
(*) source taken from Debian unstable: fso-frameworkd-0.9.5.9+git20100131.
Index: fso-frameworkd-0.9.5.9+git20100131/framework/subsystems/ogpsd/factory.py
===
--- fso-frameworkd-0.9.5.9+git20100131.orig/framework/subsystems/ogpsd/factory.py 2010-05-12 00:02:43.0 +0200
+++ fso-frameworkd-0.9.5.9+git20100131/framework/subsystems/ogpsd/factory.py 2010-05-12 00:03:35.0 +0200
@@ -20,6 +20,8 @@
from ubx import UBXDevice
from om import GTA02Device
from eten import EtenDevice
+from gpsd import GpsdDevice
+from omgpsd import GTA02GpsdDevice
from gpschannel import *
NEEDS_BUSNAMES = [ org.freedesktop.Gypsy ]
Index: fso-frameworkd-0.9.5.9+git20100131/framework/subsystems/ogpsd/gpschannel.py
===
--- fso-frameworkd-0.9.5.9+git20100131.orig/framework/subsystems/ogpsd/gpschannel.py 2010-05-12 00:02:36.0 +0200
+++ fso-frameworkd-0.9.5.9+git20100131/framework/subsystems/ogpsd/gpschannel.py 2010-05-12 00:03:27.0 +0200
@@ -18,7 +18,7 @@
import socket
import gobject
-import logging
+import logging, traceback
logger = logging.getLogger('ogpsd')
class GPSChannel( object ):
@@ -49,6 +49,68 @@
def send( self, stream ):
raise Exception( Not implemented )
+class ClientSocketChannel ( GPSChannel ):
+Generic socket client
+
+def __init__( self, path ):
+super(ClientSocketChannel, self).__init__()
+logger.debug(ClientSocketChannel opens port %s % path)
+if : in path:
+self.host, self.port = path.split( : )
+self.port = int( self.port )
+else:
+self.host =
+self.port = int( path )
+ self.sock = None
+self.watchReadyToRead = None
+self.watchReadyToSend = None
+self.datapending =
+
+def initializeChannel( self ):
+ if not self.sock:
+ self.sock = socket.socket( socket.AF_INET, socket.SOCK_STREAM )
+ try:
+self.sock.connect( (self.host, self.port) )
+ except:
+ logger.error(%s\n % traceback.format_exc())
+ self.shutdownChannel()
+ else:
+ self.watchReadyToRead = gobject.io_add_watch( self.sock.makefile(), gobject.IO_IN, self.readyToRead )
+
+def shutdownChannel( self ):
+ if self.watchReadyToRead:
+ gobject.source_remove(self.watchReadyToRead)
+ self.watchReadyToRead = None
+ if self.watchReadyToSend:
+ gobject.source_remove(self.watchReadyToSend)
+ self.watchReadyToSend = None
+ if self.sock:
+ self.sock.close()
+ self.sock = None
+
+def suspendChannel( self ):
+pass
+
+def resumeChannel( self ):
+pass
+
+def readyToRead( self, source, condition ):
+data = self.sock.recv(1024)
+if self.callback:
+self.callback(data)
+return True
+
+def readyToSend( self, source, condition ):
+self.sock.send( self.datapending )
+self.datapending =
+self.watchReadyToSend = None
+return False
+
+def send( self, stream ):
+self.datapending = self.datapending + stream
+if self.sock and not self.watchReadyToSend:
+self.watchReadyToSend = gobject.io_add_watch( self.sock.makefile(), gobject.IO_OUT, self.readyToSend )
+
class UDPChannel ( GPSChannel ):
Generic UDP reader
Index: fso-frameworkd-0.9.5.9+git20100131/framework/subsystems/ogpsd/gpsd.py
===
--- /dev/null 1970-01-01 00:00:00.0 +
+++ fso-frameworkd-0.9.5.9+git20100131/framework/subsystems/ogpsd/gpsd.py 2010-05-12 00:03:44.0 +0200
@@ -0,0 +1,93 @@
+#!/usr/bin/env python
+# -*- coding: UTF-8 -*-
+
+Open GPS Daemon - gpsd parser class
+
+(C) 2010 Gilles Filippini gilles.filipp...@free.fr
+(C) 2008 Daniel Willmann dan...@totalueberwachung.de
+(C) 2008 Openmoko, Inc.
+GPLv2
+
+
+__version__ = 0.0.0
+
+from gpsdevice import GPSDevice
+from framework import resource
+from framework.config import config
+
+import logging
+logger = logging.getLogger('ogpsd')
+
+DBUS_INTERFACE = org.freesmartphone.GPS
+
+class GpsdDevice( GPSDevice ):
+def __init__( self, bus, channel ):
+super( GpsdDevice, self ).__init__( bus, channel )
+self.channel.setCallback( self.receive )
+ lines = None
+
+def initializeDevice( self ):
+super
Re: GPS - cat /dev/ttySAC1 returns binary garbage
Hi Timo, Timo Juhani Lindfors a écrit , Le 03/05/2010 16:51: Gilles Filippini p...@debian.org writes: Since a recent upgrade I've not been able to have a GPS fix using gpsd. In such a case I usually monitor /dev/ttySAC1 using cat. But this time it seems useless : * when using the Zhone GPS feature, I have a fix but cat /dev/ttySAC1 returns *nothing* at all ; * when using navit as a gpsd client, cat /dev/ttySAC1 returns binary garbage instead of the usual text records. I assume you are using debian. You assume right :) Make sure that no process is using ttySAC1 and then om gps power 0 om gps power 1 hexdump -C /dev/ttySAC1 This way cat /dev/ttySAC1 delivers correct NMEA records (text). The binary spitting up starts when I launch a gpsd client wrapped with fsoraw. E.g.: $ fsoraw -rGPS navit But I start understanding what's going on: ogpsd initializes the GPS device in binary mode. Hence no problem so far. And when monitoring GPS with gpspipe -r it seems there is a fix after a while. But no gpsd client can see the fix ; I've tried with navit as well as with xgps. So I guess it might be a gpsd bug. I'll give a try downgrading gpsd to 2.92. Thoughts? Thanks, _g. signature.asc Description: OpenPGP digital signature ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
GPS - cat /dev/ttySAC1 returns binary garbage
Hi, Since a recent upgrade I've not been able to have a GPS fix using gpsd. In such a case I usually monitor /dev/ttySAC1 using cat. But this time it seems useless : * when using the Zhone GPS feature, I have a fix but cat /dev/ttySAC1 returns *nothing* at all ; * when using navit as a gpsd client, cat /dev/ttySAC1 returns binary garbage instead of the usual text records. Any clue? Thanks in advance, _g. signature.asc Description: OpenPGP digital signature ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: [Debian] gpsd woes
e.waelde a écrit , Le 23/04/2010 22:35: So I installed gpsd, disabled ogpsd in /etc/frameworkd.conf, You shouldn't have to disable ogpsd. added DEVICES=/dev/ttySAC1 to /etc/default/gpsd and rebootet. It seems I did remove fso-gpsd as well. + the gpspart in zhone will not even start any more. This is expected, since ogpsd/fso-gpsd are not running. - tangogps will still not receive a position, allthough lsof lists an established connection between tangogps and gpsd. This situation does not change if I go outside. The GPS chipset have to be powered on. Do you have omhacks installed? $ sudo apt-get install omhacks Then power on the GPS chipset: $ sudo om gps power 1 Then $ cat /dev/ttySAC1 Sould produce some output such as: $GPTXT,01,01,02,u-blox ag - www.u-blox.com*50 $GPTXT,01,01,02,$GPRMC,,V,,N*53 $GPVTG,N*30 $GPGGA,,0,00,99.99,,*48 $GPGSA,A,1,99.99,99.99,99.99*30 Hope this helps, _g. signature.asc Description: OpenPGP digital signature ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: [Debian] gpsd woes, almost solved.
e.waelde a écrit , Le 24/04/2010 10:00: You shouldn't have to disable ogpsd. Hm, as suggested by Al Johnson in this thread: http://lists.linuxtogo.org/pipermail/smartphones-userland/2010-March/002511.html ... dont ogpsd and gpsd both read from /dev/ttySAC1 and eat each other's characters??? Just wild guessing ... I have both gpsd and ogpsd enabled and I'm not aware of any problem related to this setting so far. I still think, there is a permission problem: r...@neo:~# ls -l /dev/ttySAC1 crw-rw 1 root dialout 204, 65 Apr 24 09:47 /dev/ttySAC1 Same here. 0660 does not look sufficient for gpsd running as nobody r...@neo:~# ps aux | grep gpsd nobody 978 1.5 1.9 5524 2508 ?Ss 09:29 0:17 /usr/sbin/gpsd -F /var/run/gpsd.sock -P /var/run/gpsd.pid /dev/ttySAC1 Same here. I did add rw for all chmod 0666 /dev/ttySAC1 which makes the setup work (tangogps now reading a position). You shouldn't have to chmod 0666 /dev/ttySAC1. While my setup currently works, it is not complete: a. maybe I should add nobody into group dialout, or gpsd should run as another user entirely ... b. the gps icon in trayer fails to switch on/off gps (probably because ogpsd is not available any more). c. same for the button in the menu attached to the [POWER] Button. Any thoughts? You may want to wrap the tangogps launcher with fsoraw. See [1]. $ sudo apt-get install fsoraw It may not mork if ogpsd is disabled. [1] http://lists.openmoko.org/nabble.html#nabble-td2630893 _g. signature.asc Description: OpenPGP digital signature ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: Race condition in ogsmd
Hi, Jose Luis Perez Diez a écrit , Le 03/02/2010 13:43: Now I'm using the following path log level CRITICAL for ogsmd: --- modem.py.oldWed Feb 3 09:04:31 2010 +++ modem.pyWed Feb 3 13:24:31 2010 @@ -194,7 +194,13 @@ if not self._muxeriface.HasAutoSession(): # abyss needs an open session before we can allocate channels self._muxeriface.OpenSession( True, 98, DEVICE_CALYPSO_PATH, 115200 ) -pts, vc = self._muxeriface.AllocChannel( name, self._channelmap[name] ) +else: +sleep(0.1) #0.01 don't work sometimes +try: +pts, vc = self._muxeriface.AllocChannel( name, self._channelmap[name] ) +except Exception, jpde: +logger.critical(Error alocating channel %s : %s, name,jpde) +return return str(pts) def dataPort( self ): I was curious about the need for the sleep statement since I expected the exception handling to be enough since it triggers a retry after 2 seconds. But removing it, ogsmd retries allocating the missing channel in vain: if it doesn't work the first time, it won't work the others. Here is the failure pattern which occurs forever: * Exception: org.freesmartphone.GSM.MUX.NoChannel: Modem does not provide this channel * could not open channel CALL, retrying in 2 seconds I've tried: * setting a sleep between _ModemOn() and the first channel opening, to check whether the muxer need some more time to initialize = no luck; * changing the channels order so that 'ogsmd.call' be opened first = third channel opening fails whatever their order is. Seems that the place you put the sleep statement at is the only one right: the muxer just can't cope opening these 3 channels without waiting a bit between them. So, please, developers, apply the Jose's patch :) BTW, I've a - maybe naive - question: shouldn't the _ModemOn and _ModemOff low level methods be implemented into libgsm0710mux? Thanks, _g. signature.asc Description: OpenPGP digital signature ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Race condition in ogsmd
Hi all, I'm trying to address the race condition which prevent Zhone to initialize the GSM when the frameworkd's loglevel is too low. Please see these threads as a background: [1], [2]. Unfortunately, using the Arne's packages doesn't solve the problem at all for me. So, I've started to dig into the fso-frameworkd code and here is where I am so far: The race takes place in subsystems/ogsmd/modems/ti_calypso/modem.py, in the TiCalypso::pathfactory method at the line: pts, vc = self._muxeriface.AllocChannel( name, self._channelmap[name] ) This line fails silently for the 'ogsmd.call' channel when the loglevel is = INFO. Adding a sleep(1) before this line fixes it reproducibly. I've no more time this evening to track this further down, but I'd appreciate some insights at this point. Thanks in advance, _g. [1] http://www.mail-archive.com/smartphones-userland@linuxtogo.org/msg01959.html [2] http://www.mail-archive.com/commun...@lists.openmoko.org/msg56239.html signature.asc Description: OpenPGP digital signature ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: [debian] Latest xserver 1.7 and touch screen problems
Hi, Timo Jyrinki a =E9crit , Le 11/01/2010 06:30: Is anyone able to figure out what's going on with the new xserver and touch screen? Seems like events are created somehow wrong when pressing down on the screen and moving, causing flickering and jumping of items. Even typing on virtual keyboard somehow gets ghost events from wrong places. I'm experiencing the very same problem. The weird thing is that x and y coordinates seem swapped at some stage. While dragging the cursor along one edge of the screen, it appears flickering both at the right place and on another edge: * left edge - top edge * bottom edge - left edge * right edge - bottom edge * top edge - right edge Moreover, it makes X to randomly segfault[1] when using matchbox-keyboard= : Any idea ? Thanks, _g. [1] Here is the relevant Xorg.0.log part: Backtrace: 0: (vdso) ((nil)+0xbeacb488) [0xbeacb488] Segmentation fault at address 0x1c Fatal server error: Caught signal 11 (Segmentation fault). Server aborting Please consult the The X.Org Foundation support at http://wiki.x.org for help. Please also check the log file at /var/log/Xorg.0.log for additional information. xf86TslibControlProc xf86TslibControlProc xf86TslibUninit xf86TslibControlProc (II) UnloadModule: tslib signature.asc Description: OpenPGP digital signature ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: navit gpsd debian
Hi, A.A. a écrit , Le 21/01/2010 13:51: can I install navit on debian without install gpsd but fso-gpsd? gpsd work with openmoko freerunner? Both gpsd and fso-gpsd work with navit on the FR, modulo one workaround for each of them: * gpsd You'll need to power on/off the GPS by hand or via a home-made script. * fso-gpsd libgps19 (pulled by navit) conflicts with fso-gpsd. See bug #562611[1]. To workaround this bug: - edit /var/lib/dpkg/status - go to the line Package: libgps19 - a few lines below, remove the line Conflicts: fso-gpsd This may not be enough with later gpsd releases. Thanks, _g [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=562611 signature.asc Description: OpenPGP digital signature ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: [Debian] Re: Touchscreen not working
Hi, Steven Jones a écrit , Le 11/01/2010 18:03: Well, I tried downgrading hal to 0.5.11, which was the only previous version (to 0.5.14) I could find in aptitude, but this didn't work, and in the process, I pretty much lost the ability to boot into zhone. A debian login prompt on the screen with no windows. When I tried to install again using the install script, it fails with an error of broken packages in the fso phase. I am not sure what else to try, but I thought I would pass along my update. Try disabling hal, with something like: # update-rc.d -f hal remove Thanks, _Gilles. signature.asc Description: OpenPGP digital signature ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: navit gpsd
Hi, A.A. a écrit , Le 21/12/2009 11:46: what gps daemon should I use between fso-gspd and gpsd?? Can I install navit and gpsd without problem? Both work. But with gpsd you need to manually power on/off the GPS chipset. Thanks, _Gilles. signature.asc Description: OpenPGP digital signature ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
[solved] Date / time not persistent anymore
Hi, Gilles Filippini a écrit , Le 16/12/2009 23:16: A few days ago I started to play both with Qi, the frameworkd config, and using gpsd instead of fso-gpsd. I can't remember when I noticed it first, but the date isn't persistent anymore on my FR: * it is set at 01/01/1970 01:00 at boot time * it is stalled on suspend I'm now back with my old configuration (u-boot + frameworkd.conf) and the problem is still there. This evening I took some time to dig around this bug, and found out the problem was that /sbin/hwclock failed to read/set the hardware clock: debian-gta02:~# LANG=C hwclock -D -r hwclock from util-linux-ng 2.16.2 Using /dev interface to clock. Last drift adjustment done at 1260715062 seconds after 1969 Last calibration done at 1260715062 seconds after 1969 Hardware clock is on UTC time Assuming hardware clock is kept in UTC time. Waiting for clock tick... ...got clock tick RTC_RD_TIME: Invalid argument ioctl() to /dev/rtc0 to read the time failed. Then, searching the friendly web with RTC_RD_TIME: Invalid argument led me to this page[1] from which I tried successfully the command: # hwclock --systohc -D --noadjfile --utc And I've got my hardware clock back \o/ Still I don't understand what could have set it in an undetermined state :/ Thanks, _Gilles. signature.asc Description: OpenPGP digital signature ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: [solved] Date / time not persistent anymore
Gilles Filippini a écrit , Le 17/12/2009 22:22: Then, searching the friendly web with RTC_RD_TIME: Invalid argument led me to this page[1] The link is missing: [1] http://markmail.org/message/do4cyxddlwpqr6u2 Thanks, _Gilles. signature.asc Description: OpenPGP digital signature ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Date / time not persistent anymore
Hi, A few days ago I started to play both with Qi, the frameworkd config, and using gpsd instead of fso-gpsd. I can't remember when I noticed it first, but the date isn't persistent anymore on my FR: * it is set at 01/01/1970 01:00 at boot time * it is stalled on suspend I'm now back with my old configuration (u-boot + frameworkd.conf) and the problem is still there. Any Idea? Thanks in advance, _Gilles. signature.asc Description: OpenPGP digital signature ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: navit debian
Hi, Timo Jyrinki a écrit , Le 09/12/2009 06:28: 2009/12/8 A.A. a...@email.it Why navit on debian is much more slow that shr? A good question, if it's indeed so (are you running the latest update svn2755 from 9 days ago?). There is: ifeq ($(DEB_HOST_ARCH), armel) CONFFLAGS += --enable-avoid-float endif in debian/rules, so at least that part should be correct. Does anyone have any other ideas? There is a whole lot of compilation options, and also of course the navit.xml might be the culprit. Maybe this note on a BeagleBoardDebian wiki page[1] is a part of the answer: Note: Debian armel deb's are compiled for armv4t, this allows debian to support a larger number of arm devices with a single port, at only the sacrifice of speed. Thanks, _Gilles. [1] http://elinux.org/BeagleBoardDebian ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: navit debian
Timo Jyrinki a écrit , Le 09/12/2009 06:28: 2009/12/8 A.A. a...@email.it Why navit on debian is much more slow that shr? A good question, if it's indeed so (are you running the latest update svn2755 from 9 days ago?). There is: ifeq ($(DEB_HOST_ARCH), armel) CONFFLAGS += --enable-avoid-float endif in debian/rules, so at least that part should be correct. Does anyone have any other ideas? There is a whole lot of compilation options, and also of course the navit.xml might be the culprit. FWIW the full log for the Debian armel build of navit are available there: https://buildd.debian.org/fetch.cgi?pkg=navitarch=armelver=0.2.0~svn2755%2Bdfsg.1-1stamp=1259435688file=logas=raw Thanks, _Gilles. signature.asc Description: OpenPGP digital signature ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: How to use fso-usaged?
arne anka a écrit , Le 04/12/2009 11:44: looking at you config, it does not look like the one included. Sure. i am still shocked to learn, fso needs a certain order of sections (fso should be able to read the whole thing and order internally if necessary). anyway, after learning baout the order of the two fsousafed sections, i strongly advise you to take the frameworkd.conf included with the configs package and merge your individual changes, preserving the order of the default file. That's what I've done, of course. And that's what doesn't work: the resulting config file only repeatedly produces Failed to read authentication status. While my unordered old config file does work. I'll try again to narrow the problem this evening. Thanks, _Gilles. signature.asc Description: OpenPGP digital signature ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: How to use fso-usaged?
Gilles Filippini a écrit , Le 04/12/2009 21:46: I'll try again to narrow the problem this evening. OK. I think I have something consistent enough now. *The* difference that makes reproducibly my config to work or not with zhone is the log_level set in the [frameworkd] section: # This one is OK log_level = INFO # This one isn't log_level = WARNING The latter is present in the default configuration file shipped with fso-config-gta02. Thanks, _Gilles. signature.asc Description: OpenPGP digital signature ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: How to use fso-usaged?
arne anka a écrit , Le 04/12/2009 23:02: # This one is OK log_level = INFO # This one isn't log_level = WARNING sounds certainly like one of those beloved race conditions. Please explain. Thanks, _Gilles. signature.asc Description: OpenPGP digital signature ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: How to use fso-usaged?
arne anka a écrit , Le 04/12/2009 23:29: # This one is OK log_level = INFO # This one isn't log_level = WARNING sounds certainly like one of those beloved race conditions. Please explain. well, race condition means two (or more) operations racing each other for a bit of code -- ie non-determinitsic outcome. so, using INFO means, far more operation cause output and every single of these outputs caused a small delay compared to WARNING. ie, it could mean an operation gets more time than intended and wins the race over the one intended to be first. while writing it occurs to me it could simply be an issue of too short timeouts because of slow hardware (or too fast sowftware, for that matter). with INFO the hardware gets more time to do whatever necessary, increasing the chance to get ready just in time. It makes since since zhone fails with log_level settings WARNING, ERROR, and CRITICAL, while it succeeds with DEBUG and INFO. in the latter case an increased timeout will probably help a lot. since it didn't happen with older fso, the fso guys could probably shed some light on that, telling if somewhere a timespan was decreased. Thanks, _Gilles. signature.asc Description: OpenPGP digital signature ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: How to use fso-usaged?
Hi, Sebastian Reichel a écrit , Le 01/12/2009 11:28: On Tue, Dec 01, 2009 at 12:00:57PM +1100, Jonathan Schultz wrote: The latest version has been in use by SHR for quite a while now and seems pretty stable. Yes and it works well for me too so far. The only problem is this is the first I've heard about it. Would it be possible for fso-config-gta02 to be kept updated? Jonathan It will be included in the next fso-config package. I will upload a new version to pkg-fso repository today. I will be asking for sponsoring once you tell me the new package is working :) Doesn't work out of the box here. Zhone says: Failed to read authentication status _Gilles. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: How to use fso-usaged?
Sebastian Reichel a écrit , Le 04/12/2009 00:59: On Fri, Dec 04, 2009 at 12:38:03AM +0100, Gilles Filippini wrote: arne anka a écrit , Le 03/12/2009 23:03: Doesn't work out of the box here. Zhone says: Failed to read authentication status yeah, common issue. just start zhone over again. and again. after a while it will catch on. my personal best is 5 times so far. It's even worse. I need to restart several times both frameworkd + zhone, and it may - rarely - catch on. I don't have this problem at all with my old frameworkd.conf (attached) for which I need maximum 2 tries at launching zhone (when I don't wait enough after [re]starting frameworkd). Thanks, _Gilles. [ogsmd] # choose your muxer, available types are: gsm0710muxd [default], fso-abyss ti_calypso_muxer = fso-abyss Can you try fso-abyss with the new provided configuration? Currently it still uses gsm0710muxd as default. Already tried before. Actually I did try to narrow the problem, without success so far. Attached is one of my last new configuration attempt (failed), where fso-abyss is selected as ti_calypso_muxer. Thanks, _Gilles. [frameworkd] version = 1 log_level = WARNING #log_to = file log_to = stderr #log_to = syslog log_destination = /tmp/frameworkd.log persist_format = pickle rootdir = ../etc/freesmartphone:/etc/freesmartphone:/usr/etc/freesmartphone [odeviced] # set 1 to disable a module disable = 0 [odeviced.kernel26] # set 1 to disable a module disable = 0 # poll capacity once every 5 minutes # (usually, you do not have to change this) capacity_check_timeout = 300 # set 0 to disable FB_BLANK ioctl to blank framebuffer # (if you have problems on Openmoko GTA02) fb_blank = 1 [odeviced.audio] # set 1 to disable a module disable = 0 # set directory where the alsa audio scenarios are stored scenario_dir = /usr/share/openmoko/scenarios # set default scenario loaded at startup default_scenario = stereoout [odeviced.idlenotifier] # set 1 to disable a module disable = 1 # don't read from accellerometers for GTA02 ignoreinput = 2,3 # configure timeouts (in seconds) here. A value of 0 # means 'never fall into this state' (except programatically) idle = 10 idle_dim = 20 idle_prelock = 12 lock = 2 suspend = 0 [odeviced.input] # set 1 to disable a module disable = 0 # don't read from accellerometers for GTA02 ignoreinput = 2,3 # format is keyname,type,input device keycode,report held seconds in addition to press/release report1 = AUX,key,169,1 report2 = POWER,key,116,1 report3 = USB,key,356,0 report4 = HEADSET,switch,2,0 [odeviced.powercontrol-neo] # set 1 to disable a module disable = 0 # disable accelerometer since it uses LOADS of CPU resources [odeviced.accelerometer] disable = 1 accelerometer_type = gta02 [ogsmd] # set 1 to disable a module disable = 0 # choose your modem type, available types are: ti_calypso, freescale_neptune, singleline, muxed4line, option, ... modemtype = ti_calypso # if you have a ti_calypso, you can choose the deep sleep mode. Valid values are: never, adaptive (default), always ti_calypso_deep_sleep = never # if you have a ti_calypso, you can choose the dsp mode for audio enhancement. Valid values are: #short-aec: Short Echo Cancellation (max) #long-aec: Long Echo Cancellation (max) #long-aec:6db: Long Echo Cancellation (-6db) #long-aec:12db: Long Echo Cancellation (-12db) #long-aec:18db: Long Echo Cancellation (-18db) #nr: Noise Reduction (max) #nr:6db: Noise Reduction (-6db) #nr:12db: Noise Reduction (-12db) #nr:18db: Noise Reduction (-18db) #aec+nr: Long Echo Cancellation (max) plus Noise Reduction (max) [default] #none: No audio processing. ti_calypso_dsp_mode = aec+nr # choose your muxer, available types are: gsm0710muxd [default], fso-abyss ti_calypso_muxer = fso-abyss [ogpsd] # set 1 to disable a module disable = 0 # possible options are NMEADevice, UBXDevice, GTA02Device, EtenDevice device = GTA02Device # possible options are SerialChannel, GllinChannel, UDPChannel, FileChannel channel = SerialChannel # For UDPChannel the path defines the port to listen to path = /dev/ttySAC1 [ousaged] # set 1 to disable a module # you need to disable ousaged if you want to use the new implementation: fso-usaged disable = 1 # choose whether resources should be disabled at startup, at shutdown, always (default), or never. sync_resources_with_lifecycle = always [ousaged.generic] [opreferencesd] # set 1 to disable a module disable = 0 rootdir = ../etc/freesmartphone/opreferences:/etc/freesmartphone/opreferences:/usr/etc/freesmartphone/opreferences log_level = WARNING [opreferencesd.opreferences] [oeventsd] # set 1 to disable a module disable = 0 rules_file = ../etc/freesmartphone/oevents/rules.yaml:/etc/freesmartphone/oevents/rules.yaml:/usr/etc/freesmartphone/oevents/rules.yaml log_level = WARNING [oeventsd.oevents] [onetworkd] [onetworkd.network] [ophoned] [ophoned.ophoned] [opimd] # set 1 to disable a module disable = 1
Re: How to use fso-usaged?
Hi, Jonathan Schultz a écrit : [fsousage] lowlevel_type = openmoko [fsousage.controller] [fsousage.lowlevel_openmoko] I have precise settings, and still get the problems I described. Same here. fsousaged has stopped working after an update last week. It worked reliably for about two months before that. I've had to switch back to ousaged to get zhone working again. I attach my frameworkd config file and logs for what it worths. Thanks, [oeventsd] rules_file = ../etc/freesmartphone/oevents/rules.yaml:/etc/freesmartphone/oevents/rules.yaml:/usr/etc/freesmartphone/oevents/rules.yaml disable = 0 log_level = DEBUG [odeviced.powercontrol-neo] disable = 0 [fsousage] disable = 0 lowlevel_type = openmoko [fsousage.controller] [fsousage.lowlevel_openmoko] [ousaged] sync_resources_with_lifecycle = always disable = 1 [odeviced.accelerometer] disable = 1 accelerometer_type = gta02 [frameworkd] log_destination = /tmp/frameworkd.log log_to = file #log_to = stderr log_level = INFO persist_format = pickle rootdir = ../etc/freesmartphone:/etc/freesmartphone:/usr/etc/freesmartphone version = 1 [ogpsd] device = GTA02Device disable = 0 channel = SerialChannel path = /dev/ttySAC1 [opreferencesd] rootdir = ../etc/freesmartphone/opreferences:/etc/freesmartphone/opreferences:/usr/etc/freesmartphone/opreferences disable = 0 log_level = DEBUG [odeviced.kernel26] capacity_check_timeout = 300 fb_blank = 1 disable = 0 [otimed] zonesources = GSM timesources = GPS,NTP [odeviced.audio] disable = 0 default_scenario = stereoout scenario_dir = /usr/share/openmoko/scenarios [odeviced] disable = 0 [opimd] # set 1 to disable a module disable = 1 contacts_default_backend = CSV-Contacts messages_default_backend = SIM-Messages-FSO calls_default_backend = SQLite-Calls dates_default_backend = SQLite-Dates notes_default_backend = SQLite-Notes tasks_default_backend = SQLite-Tasks contacts_merging_enabled = 1 messages_default_folder = Unfiled messages_trash_folder = Trash sim_messages_default_folder = SMS rootdir = ../etc/freesmartphone/opim:/etc/freesmartphone/opim:/usr/etc/freesmartphone/opim [odeviced.idlenotifier] suspend = 0 lock = 0 idle_prelock = 0 idle = -1 disable = 1 idle_dim = 300 ignoreinput = 2,3 [odeviced.input] report4 = HEADSET,switch,2,0 report1 = AUX,key,169,1 report3 = USB,key,356,0 report2 = POWER,key,116,1 disable = 0 ignoreinput = 2,3 [ogsmd] # choose your muxer, available types are: gsm0710muxd [default], fso-abyss ti_calypso_muxer = fso-abyss ti_calypso_dsp_mode = aec+nr disable = 0 ti_calypso_deep_sleep = never modemtype = ti_calypso 2009.11.29 22:59:57.953 root INFO Installprefix is /usr 2009.11.29 22:59:57.963 root INFO Etc directory is /etc/freesmartphone 2009.11.29 23:00:01.905 frameworkd.subsystem INFO subsystem frameworkd took 0.27 seconds to startup 2009.11.29 23:00:01.971 frameworkd.controller INFO launching internal subsystem odeviced 2009.11.29 23:00:02.34 frameworkd.subsystem INFO Scanned subsystem via method 'auto', result is ['accelerometer.py', 'audio.py', 'helpers.py', 'idlenotifier.py', 'info.py', 'input.py', 'kernel26.py', 'powercontrol.py', 'powercontrol_ibm.py', 'powercontrol_neo.py', 'pyglet', '__init__.py', '__init__.pyc', 'accelerometer.pyc', 'audio.pyc', 'helpers.pyc', 'idlenotifier.pyc', 'info.pyc', 'input.pyc', 'kernel26.pyc', 'powercontrol.pyc', 'powercontrol_ibm.pyc', 'powercontrol_neo.pyc'] 2009.11.29 23:00:02.41 frameworkd.subsystem INFO skipping module odeviced.accelerometer as requested via config file. 2009.11.29 23:00:16.180 odeviced.audio WARNING GST can't parse modplug; Not adding mod to decoderMap 2009.11.29 23:00:20.831 odeviced.audio WARNING GST can't parse oggdemux ! ivorbisdec ! audioconvert; Not adding ogg to decoderMap 2009.11.29 23:00:21.664 odeviced.audio INFO ::: using alsa scenarios in /usr/share/openmoko/scenarios, default = stereoout 2009.11.29 23:00:21.670 odeviced.audio INFO Audio 0.5.9.11 initialized. Serving org.freesmartphone.Device.Audio at /org/freesmartphone/Device/Audio 2009.11.29 23:00:21.681 frameworkd.subsystem INFO skipping module odeviced.idlenotifier as requested via config file. 2009.11.29 23:00:21.713 odeviced.infoINFO Info 0.1.3 initialized. Serving org.freesmartphone.Device.Info at /org/freesmartphone/Device/Info 2009.11.29 23:00:22.563 odeviced.input INFO Input 0.9.9.5 initialized. Serving org.freesmartphone.Device.Input at /org/freesmartphone/Device/Input 2009.11.29 23:00:22.612 odeviced.input INFO skipping input node 1 due to it supporting EV_ABS 2009.11.29 23:00:22.630 odeviced.input INFO skipping input node 2 due to configuration 2009.11.29 23:00:22.636 odeviced.input INFO skipping input node 3 due to configuration 2009.11.29 23:00:22.659 odeviced.input INFO opened 2 input file descriptors 2009.11.29 23:00:23.634 odeviced.kernel26INFO Display 0.9.9.9
Re: navit garmin map
Hi, A.A. a écrit : i have installed navit and libgarmin on debian. When i run navit it result: a...@neo:~/Maps$ DISPLAY=:0 navit gui_internal:gui_internal_new:register vehicle_gpsd:vehicle_gpsd_try_open:Trying to connect to localhost:default vehicle_gpsd:vehicle_gpsd_try_open:Connected to gpsd fd=4 evwatch=0xb2b20 :garmin.c:217:1|:libgarmin 0.1 initializing as GPS Backend :garmin.c:471:1|:Loading /home/alex/Maps/europe-garmin.img as disk image [snip] why the garmin map not work? I'm the maintainer for the navit and libgarmin packages in Debian. Unfortunately I don't have any Garmin maps to test it with (I use MG maps). You may want to report your bug to the Navit devs via trac http://trac.navit-project.org/ or IRC (irc.freenode.org channel #navit). Alternatively you could send me a map file and a way to reproduce the problem. Thanks, _Gilles. signature.asc Description: OpenPGP digital signature ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: fso-frameworkd issues
arne anka a écrit : I've experienced the same error when I restart Zhone too early after a frameworkd restart. It seems fso-abyss needs more time to initialize itself. Have you tried waiting about 30 sec and restarting Zhone again? iirc fso-abyss is started first when something accesses gsm -- ie zhone. The behavior I've reported above is reproducible. _Gilles. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: fso-frameworkd issues
Hi, Jonathan Schultz a écrit : Hi again, After much frustration I've given up using my Freerunner as a phone until I can get this framework thing sorted out. Current symptoms include random framework crashes, no sound on phone calls and no connection to the GSM network. Is there any chance of someone posting some usable configuration files to this list? Cheers, Jonathan Jonathan Schultz wrote: I just tried that and things have gotten worse. openmoko-panel-plugin is now chewing around 40% of the CPU and I am unable to use it to turn on the GSM - that is, I can try to turn on the GSM but nothing actually happens. Sorry for all this rambling but I engaged my brain and took a look inside the configuration files at which point it became fairly obvious that I needed to manually tweak the configuration file for my freerunner. It appears to work now, though I haven't time to really test it. I've been experiencing the same kind of frameworkd hangs as you. Today I switched my FSO configuration to use fso-abyss and fso-usaged, and it seems it solves the problem (just tested with a few calls so far). I've had to adapt /etc/framworkd.conf as above: 1- enable fso-usaged: [fsousage] disable = 0 lowlevel_type = openmoko [fsousage.controller] [fsousage.lowlevel_openmoko] 2- disable osuaged: [ousaged] disable = 1 sync_resources_with_lifecycle = always 3- enable fso-abyss: [ogsmd] ti_calypso_muxer = fso-abyss ... Please note that I don't use openmoko-panel-plugin. Hope this helps. _Gilles. signature.asc Description: OpenPGP digital signature ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: [debian] navit in repo now
arne anka a écrit : did anyone check the repo's navit for speed and usability? I found it quite slow but still usable. YMMV. I'd welcome any patch to the package to improve its usability. Thanks, _Gilles. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: [debian] navit in repo now
Hi, [cc-ed pkg-fso-maint] arne anka a écrit : I found it quite slow but still usable. YMMV. I'd welcome any patch to the package to improve its usability. no patch, i simply build navit with the options below added to the configure line in debian/rules (most notably the CCFLAGS, taken from the navit wiki). CCFLAGS=-march=armv4t -mtune=arm920t I guess these flags can't be used for all debian armel boxes because of the wide variety of ARM chips. Is that right? If so, and in case these flags significantly improve usability, would it be appropriate to add openmoko specific binary packages such as navit-openmoko and so on? Thanks in advance, Gilles. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: [debian] navit in repo now
[sending again since I missed replying to the list. sorry about the noise] Hi, arne anka a écrit : while upgrading i notice, navit has made it into the official debian repo. does anyone know, how good it works and what options where used to build that package or where to find that kind of information prior to installing (i won't, since it depends on speechd which i don't need and don't want)? navit depends on libspeechd2 which has an installed size of 116 kB. The lib itself weights 24 kB. There is no daemon involved. Thanks, _Gilles. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: [Debian] right click doesn't work anymore
arne anka a écrit : i had that issue recently and wrote on supp...@om about it. basically it seems to be related to evdev. following a link regarding gentoo on the freerunner i did - comment the whole Section InputDevice of xorg.conf - copied /usr/share/doc/hal/examples/10-x11-input.fdi to /etc/hal/fdi/policy/10-x11-input.fdi and changed accordingly, see patch below - re-enabled gtkstylus (in ~/.xsession) export GTK_MODULES=libgtkstylus.so not really satisfying, at least the gtkstylus part, but works Thanks Arne for the tip. I'll finally go with disabling hal until these changes stabilize a bit. Cheers, _Gilles. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: [Debian] right click doesn't work anymore
Hi, Timo Juhani Lindfors wrote: Gilles Filippini gilles.filipp...@free.fr writes: Is there any known configuration trick I'd have missed? Yes. Remove the line Option Device/dev/input/event1 and read http://bugs.debian.org/xserver-xorg-input-tslib I did mail the pkg-fso people to fix install.sh to not add that Option anymore -- I have not checked if it has been fixed yet. No. It doesn't work as expected. Removing the Device line just makes the xorg.conf InputDevice entry ignored, and so is the EmulateRightButton option. Here is the corresponding excerpt of /var/log/Xorg.0.log: (**) Option SendCoreEvents true (**) Option CorePointer (**) Configured Touchscreen: always reports core events (**) Option Width 480 (**) Option Height 640 ts_open failed (device=(null)) (EE) PreInit returned NULL for Configured Touchscreen = still no right click. Does right click work on your FreeRunner? Thanks, _Gilles. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: [Debian] right click doesn't work anymore
Timo Juhani Lindfors a écrit : Gilles Filippini gilles.filipp...@free.fr writes: Does right click work on your FreeRunner? Sorry, I read left click. No, the xserver-xorg-input-tslib does not support right clicking in debian afaik. Has it supported that in the past? Yes. It does support it officially: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495487 With the Device line in my xorg.conf, right click works perfectly. It's just left click that is unusable. Thanks, _Gilles. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
[Debian] right click doesn't work anymore
Hi all, My last dist-upgrade - two days ago - resulted in an unusable touchscreen. Thinking about recent discussions I've eventually removed my xorg.conf and got my touchscreen working again. But then, no more right-click. * With my old xorg.conf - enclosed - the left-click doesn't work at all, and right-click is ok while I don't attempt any left-click. * With no xorg.conf, left-click is ok but right-click doesn't work. Is there any known configuration trick I'd have missed? Thanks in advance, _Gilles # Xorg confiugration for an Openmoko FreeRunner Section InputDevice Identifier Configured Touchscreen Driver tslib Option CorePointer true Option SendCoreEventstrue Option Device/dev/input/event1 Option EmulateRightButton1 Option Protocol Auto Option Width 480 Option Height640 EndSection Section Device Identifier Configured Video Device Driver fbdev EndSection ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
[Fwd: Re: [Debian] How do I change the ringtone again?]
[ forgot to cc the list ; sorry about that ] Hi Luca, Luca Capello a écrit : Hi Gilles! On Mon, 23 Mar 2009 22:26:53 +0100, Gilles Filippini wrote: Enrico Zini a écrit : I recall that some time ago I changed the ringtone by editing frameworkd's source code, and I know that I can dpkg-divert some files if needed, but what's the clean and easy and suggested way? Everything you need is there: http://wiki.openmoko.org/wiki/FSO_ringtones Can someone please remove the information there? Editing files provided by packages is *not* the right way on Debian (nor on any other distribution). Maybe you refer to /usr/share/sounds where soundfiles have to be stored, but AFAIUI no file has to be edited outside of the /etc tree. Moreover, upstream FSO (thus not Debian) provides a configuration file for this purpose, i.e. /etc/freesmartphone/opreferences/conf/phone/$PROFILE.yaml Cheers, _Gilles. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: [Debian] How do I change the ringtone again?
Hi Enrico, Enrico Zini a écrit : Hello, I've changed microSD card and now I can use the FreeRunner as a phone(ish) a bit more. However, the default FSO ringtone is not something that can be acceptably blasted at full volume in any of the social circles that I associate with[1]. How do I change the ringtone in Debian? I have installed fso-sounds-yue-base and fso-sounds-yue-full but I still get Arkanoid_PSID.sid Neither fso-sounds-yue-base nor fso-sounds-yue-full have any useful information in /usr/share/doc. I recall that some time ago I changed the ringtone by editing frameworkd's source code, and I know that I can dpkg-divert some files if needed, but what's the clean and easy and suggested way? Everything you need is there: http://wiki.openmoko.org/wiki/FSO_ringtones Cheers, _Gilles. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: [debian/fso]: zhone does not connect to gsm anymore
Hello, Joachim Breitner a écrit : Hi, Am Sonntag, den 11.01.2009, 20:27 +0100 schrieb arne anka: dbus-x11_1.2.1-5_armel.deb dbus_1.2.1-5_armel.deb ^ as you spotted, dbus has fixed their insecure default permission, see this CVE for more details: http://lists.freedesktop.org/archives/dbus/2008-December/010702.html The frameworkd dbus configuration has to be adjusted to the new defaults. Are you running zhone as root? It happens on my FR with zhone running as non-root. Adding this line: allow send_requested_reply=true send_type=method_call/ to the dbus policy makes zhone happy again. Cheers, _Gilles. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: [debian/fso] openmoko-panel-plugin 0.6-2.1 not working after upgrade
Michele Renda a écrit : Il 28/12/2008 11:37, Simon Matthews ha scritto: Hi, I have just upgraded my Freerunner with apt-get upgrade and now O-P-P will not start. I think you have to upgrade your o-p-p version. The GetPower method on FSO framework was removed sometime ago. All the programs was using this method need to be modifed (o-p-p, sephora, etc.) to use the new methods. Hi Michele, And what about Sephora? I can't find any update since the 0.2-alpha3 release. Thanks in advance. _Gilles. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
[vala] Calling org.freesmartphone.Device.IdleNotifier.GetTimeouts()
Hello,
I'm trying to retrieve IdleNotifier timeouts in Vala but I'm stuck with
an error I don't understand:
No demarshaller registered for type gpointer
Please see the full test case below.
Anyone with a clue?
I've posted to the Vala mailing list without success so far...
Thanks in advance,
_Gilles.
--%--
debian-gta02:~# cat dict.vala
using GLib;
using DBus;
public class Dict : GLib.Object {
public DBus.Connection conn { get; construct set; }
private dynamic DBus.Object idleNotifier;
private int idle_timeout;
public GLib.MainLoop loop;
construct {
loop = new MainLoop (null, false);
}
public void initialize () throws DBus.Error, GLib.Error {
conn = DBus.Bus.get(DBus.BusType.SYSTEM);
idleNotifier = conn.get_object(org.freesmartphone.frameworkd,
/org/freesmartphone/Device/IdleNotifier/0,
org.freesmartphone.Device.IdleNotifier);
idleNotifier.GetTimeouts(_get_timeouts_reply);
loop.run();
}
private void _get_timeouts_reply(GLib.HashTablestring,int? timeouts,
GLib.Error? err) {
if (err != null) {
warning (err.message);
stdout.printf(Aborting in _get_timeouts_reply\n);
loop.quit();
return;
}
if (timeouts == null)
return;
stdout.printf(size = %u\n, timeouts.size());
timeouts.get_keys();
idle_timeout = timeouts.lookup(idle);
loop.quit();
}
public static void main (string [] args) {
Dict dict = new Dict();
try {
dict.initialize();
}
catch (GLib.Error err) {
dict.loop.quit();
}
}
}
debian-gta02:~# valac --pkg dbus-glib-1 --pkg glib-2.0 -o dict dict.vala
debian-gta02:~# ./dict
** (process:14337): WARNING **: No demarshaller registered for type
gpointer
** (process:14337): WARNING **: No demarshaller registered for type
gpointer
Aborting in _get_timeouts_reply
debian-gta02:~#
--%--
___
Smartphones-userland mailing list
Smartphones-userland@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: [vala] Calling org.freesmartphone.Device.IdleNotifier.GetTimeouts()
Gilles Filippini a écrit : Hello, I'm trying to retrieve IdleNotifier timeouts in Vala but I'm stuck with an error I don't understand: No demarshaller registered for type gpointer [snip] OK. My fault :( I planned to give a try to the upcoming Vala release (0.5.2). So I started to read the previous release notes on the Vala home page to gather information about manual installation. I then dicovered that GHashTable support in DBus client has been introduced in Vala-0.5.1. And Debian unstable ships Vala-0.3.4... I've just tested my code with vala-0.5.1 and now it works as expected :) Thanks, _Gilles. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
IdleNotifier interface
Hello, I'm trying to change the org.freesmartphone.Device.IdleNotifier state using mdbus. For what I can read from framework/subsystems/odeviced/idlenotifier.py I should be able to switch the state to busy with: # mdbus -s org.freesmartphone.frameworkd /org/freesmartphone/Device/IdleNotifier org.freesmartphone.Device.IdleNotifier.SetState busy Unfortunately the only result I get is: /org/freesmartphone/Device/IdleNotifier: SetState failed: org.freedesktop.DBus.Error.UnknownMethod What am I doing wrong? Thanks in advance, _Gilles. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: IdleNotifier interface
Gilles Filippini a écrit : Hello, I'm trying to change the org.freesmartphone.Device.IdleNotifier state using mdbus. For what I can read from framework/subsystems/odeviced/idlenotifier.py I should be able to switch the state to busy with: # mdbus -s org.freesmartphone.frameworkd /org/freesmartphone/Device/IdleNotifier org.freesmartphone.Device.IdleNotifier.SetState busy Unfortunately the only result I get is: /org/freesmartphone/Device/IdleNotifier: SetState failed: org.freedesktop.DBus.Error.UnknownMethod What am I doing wrong? Answering to myself. The right command line is: # mdbus -s org.freesmartphone.frameworkd /org/freesmartphone/Device/IdleNotifier/0 org.freesmartphone.Device.IdleNotifier.SetState busy Cheers, _Gilles. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: milestone4 now in Debian
Hello, Sebastian Reichel a écrit : Hi, I just did the upgrade - MS4's zhone looks pretty nice and works quite good in Debian. Though it seems the configuration has been mixed up - Power LED is not orange anymore when charging / blue when fully charged. Was this change on purpose? IMHO a notification about charging would be nice ;) The same here. Even worse: suspend doesn't work anymore via the power button. Cheers, _gilles. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: milestone4 now in Debian
Oops: I missed replying to the list. Message original Hi Timo, Timo Juhani Lindfors a écrit : Gilles Filippini [EMAIL PROTECTED] writes: The same here. Even worse: suspend doesn't work anymore via the power button. Which version of fso-config-gta02 do you have? 2008-1 has trigger: InputEvent() filters: - HasAttr(switch, POWER) - HasAttr(event, released) - HasAttr(duration, 0) actions: Suspend() OK. I thought I had to press power button for more than 1 sec to trigger suspend. Looking at this new trigger I understood it changed for a simple press/release. And it work. Thanks you, and BTW thanks to Luca for the updated fso-config-gta02 info: power leds are ok now. Cheers, _gilles. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
