Re: AM_VALAFLAGS and fsodeviced plugins
Am Freitag, 24. Januar 2014, 16:07:49 schrieb Lukas Maerdian: thanks for spotting this! Could you please test the attached patch for fsodeviced and confirm that it fixes the problem for you? The patch is tested to compile, but I don't have a setup at hand to test it at runtime. If you succeed I can push the patch to cornucopia master and we can integrated it in the Debian packages. Thanks, it works at least on GTA02 running Debian. Rico signature.asc Description: This is a digitally signed message part. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: AT commands via FSO
Am Sonntag, 30. Juni 2013, 11:04:54 schrieb Rico Rommel:
Am Sonntag, 30. Juni 2013, 10:23:48 schrieb Rico Rommel:
Hi,
is there a way to send AT commands to the modem using dbus and fsogsmd?
It seems, my sim card isn't initialized correctly at poweron ( $QCSIMSTAT?
givesunknown) and I need to send _ORESET to the modem.
update:
sim card becomes initialized, but later, and fsogsmd doesn't care about it
and stays in modem status initializing. So it seems to be a bug in fsogsmd.
I've found a, maybe dirty, workaround. If the modem stays in status
initializing for more then 5s, fsogsmd should re-initalize the modem.
From e50a9988e24038644f539662f2d53b440643fca1 Mon Sep 17 00:00:00 2001
From: Rico Rommel r...@bierrommel.de
Date: Fri, 12 Jul 2013 15:31:40 +0200
Subject: [PATCH] fsogsmd: re-initialize modem after 5 s when modem status
doesn't advance
---
fsogsmd/src/lib/at/atchannel.vala | 13 +
1 file changed, 13 insertions(+)
diff --git a/fsogsmd/src/lib/at/atchannel.vala b/fsogsmd/src/lib/at/atchannel.vala
index 761167b..a9cfb2a 100644
--- a/fsogsmd/src/lib/at/atchannel.vala
+++ b/fsogsmd/src/lib/at/atchannel.vala
@@ -27,6 +27,7 @@ public class FsoGsm.AtChannel : FsoGsm.AtCommandQueue, FsoGsm.Channel
private bool isInitialized;
private bool isMainChannel;
private bool isUrcChannel;
+private uint timeoutID;
private FsoGsm.Modem modem;
public AtChannel( FsoGsm.Modem modem, string? name, FsoFramework.Transport transport, FsoFramework.Parser parser, bool isUrcChannel = true )
@@ -46,10 +47,13 @@ public class FsoGsm.AtChannel : FsoGsm.AtCommandQueue, FsoGsm.Channel
public void onModemStatusChanged( FsoGsm.Modem modem, FsoGsm.Modem.Status status )
{
+if (timeoutID 0 ) Source.remove( timeoutID);
+
switch ( status )
{
case Modem.Status.INITIALIZING:
initialize();
+timeoutID = Timeout.add (5000, onInitTimeout);
break;
case Modem.Status.ALIVE_SIM_READY:
simIsReady();
@@ -65,6 +69,15 @@ public class FsoGsm.AtChannel : FsoGsm.AtCommandQueue, FsoGsm.Channel
}
}
+
+private bool onInitTimeout()
+{
+modem.logger.debug( Initializing timed out, re-initializing );
+initialize();
+return true;
+}
+
+
private async void initialize()
{
assert( modem.logger.debug( @Initializing channel $name ... ) );
--
1.7.10.4
signature.asc
Description: This is a digitally signed message part.
___
Smartphones-userland mailing list
Smartphones-userland@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
AT commands via FSO
Hi, is there a way to send AT commands to the modem using dbus and fsogsmd? It seems, my sim card isn't initialized correctly at poweron ( $QCSIMSTAT? givesunknown) and I need to send _ORESET to the modem. I cannot use chat or femtocom, because fsogsmd is claiming ttyHS*. Rico signature.asc Description: This is a digitally signed message part. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: AT commands via FSO
Am Sonntag, 30. Juni 2013, 10:23:48 schrieb Rico Rommel: Hi, is there a way to send AT commands to the modem using dbus and fsogsmd? It seems, my sim card isn't initialized correctly at poweron ( $QCSIMSTAT? givesunknown) and I need to send _ORESET to the modem. update: sim card becomes initialized, but later, and fsogsmd doesn't care about it and stays in modem status initializing. So it seems to be a bug in fsogsmd. Rico signature.asc Description: This is a digitally signed message part. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: fso and gta04: need working configurations (and maybe a pointer to the well-hidden documentation?)
Am Samstag, 25. Mai 2013, 01:36:03 schrieb arne anka: hi, in case there's indeed still someone out there using FSO with the GTA04 (and debian), can you please post your configs? i started a new attempt with the FSO in debian/sid (0.11) and confs from SHR, but don't get anything. at least i'd expect the AUX and PWR keys to trigger something (minimal entries in the logs) -- but no can do. since FSO for ages now suffers from bad documentation and arcane values and keys in its config files (without helpful commens, of course), it's basically impossible to figure out, waht exactly that bunch of configs and key/value pairs actually does (does 0 equal no? why is there still fsodevice.kernel26? what with kernel 3.x being out for years now? what units have entries like delay=500?), let alone get it working by trial and error ... The configs shipped with Debian should basically work. Try installing mdbus2 package and run mdbus2 -s -l. If you press aux or pwr, you should see something happen. And again, there are packages prepared for fso 0.12, which should work out of the box: http://lists.linuxtogo.org/pipermail/smartphones-userland/2012-December/003252.html Rico signature.asc Description: This is a digitally signed message part. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: volume control in FSO
Am Freitag, 5. April 2013, 01:44:36 schrieb Lukas Märdian: Am 03.04.2013 22:28, schrieb Lukas Märdian: Unfortunately I had to find out, that there is another bug: FSO assumes the volume to be linear, whereas this isn't true for the human ear. I hope to have a look at this soon. Just for the reference, the difference between linear percentage (aka amixer) and human percentage (aka alsamixer) is described here: http://mailman.alsa-project.org/pipermail/alsa-devel/2012-March/050074.html FSO is currently using the aplay/linear percentage, whereas it would probably be convenient to use the alsamixer/human percentage. What do you think? I think, the linear control is enough, but somebody else could see it differently. Rico signature.asc Description: This is a digitally signed message part. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: volume control in FSO
Am Mittwoch, 3. April 2013, 22:28:44 schrieb Lukas Märdian: I've finally found some time again and coded a (pretty huge) helper function to translate the ID from the alsa CONTROL interface (scenario) to the alsa MIXER interface (which is used to set the volume). Thanks, it works perfectly. Rico signature.asc Description: This is a digitally signed message part. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
fso vibrator-plugin
Hi,
I created a plugin for fsodeviced, which uses force feedback, as provided by
3.7 kernel for gta04. Due to my limited vala-knowledge and missing ff-support
in vala, i had to implement some parts in c.
Maybe somebody can help to convert the c part into vala.
Note, that there is a new .gitignore file in the plugin directory, which
prevents git from ignoring vibration.c.
RicoFrom 5a4dc55adf5816074b352ce341a70ffc005dc3e8 Mon Sep 17 00:00:00 2001
From: Rico Rommel r...@bierrommel.de
Date: Thu, 28 Mar 2013 18:20:47 +0100
Subject: [PATCH 1/1] fsodeviced: add vibrator forcefeedback plugin for use
with 3.7 kernel on gta04
---
fsodeviced/configure.ac|1 +
fsodeviced/src/plugins/Makefile.am |1 +
.../src/plugins/vibrator_forcefeedback/.gitignore |1 +
.../src/plugins/vibrator_forcefeedback/Makefile.am | 34 +
.../src/plugins/vibrator_forcefeedback/plugin.vala | 148
.../src/plugins/vibrator_forcefeedback/vibration.c | 49 +++
6 files changed, 234 insertions(+)
create mode 100644 fsodeviced/src/plugins/vibrator_forcefeedback/.gitignore
create mode 100644 fsodeviced/src/plugins/vibrator_forcefeedback/Makefile.am
create mode 100644 fsodeviced/src/plugins/vibrator_forcefeedback/plugin.vala
create mode 100644 fsodeviced/src/plugins/vibrator_forcefeedback/vibration.c
diff --git a/fsodeviced/configure.ac b/fsodeviced/configure.ac
index 321f6e0..4fff6b6 100644
--- a/fsodeviced/configure.ac
+++ b/fsodeviced/configure.ac
@@ -259,6 +259,7 @@ AC_CONFIG_FILES([
src/plugins/vibrator_ledclass/Makefile
src/plugins/vibrator_omapvibe/Makefile
src/plugins/vibrator_timedoutputclass/Makefile
+ src/plugins/vibrator_forcefeedback/Makefile
tests/Makefile
])
AC_OUTPUT
diff --git a/fsodeviced/src/plugins/Makefile.am b/fsodeviced/src/plugins/Makefile.am
index 94f5060..20ef29f 100644
--- a/fsodeviced/src/plugins/Makefile.am
+++ b/fsodeviced/src/plugins/Makefile.am
@@ -34,6 +34,7 @@ SUBDIRS = \
vibrator_ledclass \
vibrator_omapvibe \
vibrator_timedoutputclass \
+ vibrator_forcefeedback \
\
gta04_quirks \
herring_quirks \
diff --git a/fsodeviced/src/plugins/vibrator_forcefeedback/.gitignore b/fsodeviced/src/plugins/vibrator_forcefeedback/.gitignore
new file mode 100644
index 000..bd659de
--- /dev/null
+++ b/fsodeviced/src/plugins/vibrator_forcefeedback/.gitignore
@@ -0,0 +1 @@
+!vibration.c
diff --git a/fsodeviced/src/plugins/vibrator_forcefeedback/Makefile.am b/fsodeviced/src/plugins/vibrator_forcefeedback/Makefile.am
new file mode 100644
index 000..31827a5
--- /dev/null
+++ b/fsodeviced/src/plugins/vibrator_forcefeedback/Makefile.am
@@ -0,0 +1,34 @@
+include $(top_srcdir)/Makefile.decl
+NULL =
+
+AM_CFLAGS = \
+ -DG_LOG_DOMAIN=\fsodevice.vibrator_forcefeedback\ \
+ $(NULL)
+AM_VALAFLAGS =
+
+modlibexecdir = $(libdir)/cornucopia/modules/fsodevice
+modlibexec_LTLIBRARIES = vibrator_forcefeedback.la
+vibrator_forcefeedback_la_SOURCES = plugin.vala vibration.c
+vibrator_forcefeedback_la_VALAFLAGS = \
+ --basedir $(top_srcdir) \
+ --vapidir $(top_srcdir)/fsoframework\
+ --pkg glib-2.0 \
+ --pkg fso-glib-1.0 \
+ --pkg fsoframework-2.0 \
+ $(DEBUG_VALAFLAGS) \
+ $(NULL)
+vibrator_forcefeedback_la_CFLAGS = \
+ -I$(top_srcdir) \
+ $(FSO_CFLAGS) \
+ $(DEBUG_CFLAGS) \
+ $(NULL)
+vibrator_forcefeedback_la_LIBADD = \
+ $(FSO_LIBS) \
+ $(top_builddir)/src/lib/libfsodevice.la \
+ $(NULL)
+vibrator_forcefeedback_la_LDFLAGS = -no-undefined -module -avoid-version
+
+CLEANFILES =
+MAINTAINERCLEANFILES = \
+ Makefile.in \
+ $(NULL)
diff --git a/fsodeviced/src/plugins/vibrator_forcefeedback/plugin.vala b/fsodeviced/src/plugins/vibrator_forcefeedback/plugin.vala
new file mode 100644
index 000..39b166d
--- /dev/null
+++ b/fsodeviced/src/plugins/vibrator_forcefeedback/plugin.vala
@@ -0,0 +1,148 @@
+/*
+ * Copyright (C) 2013 Rico Rommel r...@bierrommel.de
+ *
+ * This library is free software; you can redistribute it and/or
+ * modify it under the terms of the GNU Lesser General Public
+ * License as published by the Free Software Foundation; either
+ * version 2.1 of the License, or (at your option) any later version.
+
+ * This library is distributed in the hope that it will be useful,
+ * but WITHOUT ANY WARRANTY; without even the implied warranty of
+ * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
+ * Lesser General Public License for more details.
+
+ * You should have received a copy of the GNU Lesser General Public
+ * License along with this library; if not, write to the Free Software
+ * Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
+ *
+ */
+
+
+
+using GLib;
+
+namespace Vibrator
+{
+
+internal const string PLUGIN_NAME = fsodevice.vibrator_forcefeedback;
+internal const string DEFAULT_DEVICE_NODE = /dev/input/rumble;
+
+class ForceFeedback : FreeSmartphone.Device.Vibrator, FsoFramework.AbstractObject
+{
+
+FsoFramework.Subsystem subsystem
Re: volume control in FSO
Am Montag, 18. März 2013, 17:48:28 schrieb Lukas Märdian: Am 17.03.2013 20:31, schrieb Lukas Märdian: So there's definitely something wrong in the alsa router. Can you or somebody else provide a patch? I have no idea how to solve this. I'm not sure how to fix this either, but I'll try to have a deeper look before my vacation (still few days left). I hope I'll be able to provide a patch for it soon. Hi Rico, attached is a patch, which should apply cleanly atop of the 0.12 branch of cornucopia. I do not yet understand all the alsa stuff, but this first patch seems to fix the issue on my laptop. Could you please try, if it fixes your use case as well? Please comment on any problems you see. I'll try to clean it up and push it into git after my vacations. It basically works now, good job. But I wonder, if I have to set volume now in the range of the mixer element absolute or as a percentage. Rico signature.asc Description: This is a digitally signed message part. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: volume control in FSO
Am Montag, 18. März 2013, 17:48:28 schrieb Lukas Märdian: Am 17.03.2013 20:31, schrieb Lukas Märdian: So there's definitely something wrong in the alsa router. Can you or somebody else provide a patch? I have no idea how to solve this. I'm not sure how to fix this either, but I'll try to have a deeper look before my vacation (still few days left). I hope I'll be able to provide a patch for it soon. Hi Rico, attached is a patch, which should apply cleanly atop of the 0.12 branch of cornucopia. I do not yet understand all the alsa stuff, but this first patch seems to fix the issue on my laptop. Could you please try, if it fixes your use case as well? Please comment on any problems you see. I'll try to clean it up and push it into git after my vacations. Thanks, i will try it next days. Rico signature.asc Description: This is a digitally signed message part. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: volume control in FSO
Am Donnerstag, 7. März 2013, 10:30:30 schrieb Lukas Märdian: Maybe you can use this command, to export your current scenario and compare them? mdbus2 -s org.freesmartphone.odeviced /org/freesmartphone/Device/Audio org.freesmartphone.Device.Audio.SaveScenario stereoout For further information you could read this document: http://wiki.freesmartphone.org/index.php/AlsaScenarios That doesn't point the problem. I did some debugging in alsa.vala: I set main_volume = 2 and expect in setVolumeForIndex() as mixerelement 'DAC1 Digital Fine Playback Volume', but I get 'Analog Left AUXL' main_volume = 3 expected: 'DAC2 Digital Fine Playback Volume' got: 'Analog Left Carkit Mic' main_volume = 4 expected: 'DAC1 Digital Coarse Playback Volume' got: 'Analog Left Headset Mic' ... mel.next() returns mixerelements in this (alphabetical) order so they don't match the control ids in the scenario-config: Analog Analog Left AUXL Analog Left Carkit Mic Analog Left Headset Mic Analog Left Main Mic Analog Right AUXR Analog Right Sub Mic Carkit CarkitL Mixer AudioL1 CarkitL Mixer AudioL2 CarkitL Mixer Voice CarkitR Mixer AudioR1 CarkitR Mixer AudioR2 CarkitR Mixer Voice Codec Operation Mode DAC Voice Analog Downlink DAC Voice Digital Downlink ... One Problem may be, that setVolumeForIndex() and volumeForIndex() are using Alsas Simple Mixer Interface while scenario settings are using the usual mixer interface. Btw, does it work in SHR? Rico signature.asc Description: This is a digitally signed message part. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: volume control in FSO
Am Donnerstag, 7. März 2013, 18:28:41 schrieb Lukas Märdian: Ouch, that doesn't look good. Could you describe a simple test case, so I can try it in SHR? mdbus2 -s org.freesmartphone.odeviced /org/freesmartphone/Device/Audio org.freesmartphone.Device.Audio.GetVolume returns 0 mdbus2 -s org.freesmartphone.odeviced /org/freesmartphone/Device/Audio org.freesmartphone.Device.Audio.SetVolume 50 mdbus2 -s org.freesmartphone.odeviced /org/freesmartphone/Device/Audio org.freesmartphone.Device.Audio.GetVolume returns 0 again another one: in /etc/freesmartphone/GTA04/alsa.conf # PCM [scenario.stereoout] main_volume = 7 (this should be 'DAC2 Analog Playback Volume') mdbus2 -s org.freesmartphone.odeviced /org/freesmartphone/Device/Audio org.freesmartphone.Device.Audio.GetVolume returns 0 mdbus2 -s org.freesmartphone.odeviced /org/freesmartphone/Device/Audio org.freesmartphone.Device.Audio.SetVolume 50 mdbus2 -s org.freesmartphone.odeviced /org/freesmartphone/Device/Audio org.freesmartphone.Device.Audio.GetVolume returns 0 again signature.asc Description: This is a digitally signed message part. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: volume control in FSO
Am Dienstag, 5. März 2013, 20:41:44 schrieb Rico Rommel: Hi, SetVolume via fsodeviced doesn't work for me on GTA04 , beacuse there is no / a wrong main volume setting. In the source code of router_alsa I found an option called main_volume. But I'm not quite clear, where to set this option. Do I have to set this in alsa.conf for each scenario? I'm answering myself: It has to be set for each scenario. But now there is a bigger problem: The number in the scenario file does'nt match the number in class Alsa.Mixer. It seems, Alsa.Mixer contains a alphabetical ordered list of controls, while scenario settings are numerical ordered. So the index of one control in both list isn't the same and it doesn't work at all or you have to find out, which number in Alsa.Mixer hits the one in the alsa/scenario-settings. It looks like a bug in lib/alsa.vala. Rico signature.asc Description: This is a digitally signed message part. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
volume control in FSO
Hi, SetVolume via fsodeviced doesn't work for me on GTA04 , beacuse there is no / a wrong main volume setting. In the source code of router_alsa I found an option called main_volume. But I'm not quite clear, where to set this option. Do I have to set this in alsa.conf for each scenario? Thanks Rico signature.asc Description: This is a digitally signed message part. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: GTA04 FSO kernel 3.5
Am Samstag, 22. Dezember 2012, 17:03:42 schrieb Denis 'GNUtoo' Carikli: On Sat, 22 Dec 2012 16:29:33 +0100 Rico Rommel r...@bierrommel.de wrote: [...] I hope, it helps. Thanks a lot. What doesn't work with that setup? What is handled by debian packages instead of FSO? For instance we handle wifi in FSO in SHR: We use iliwi+fso for wifi. We use emtooth2+fso for bluetooth(doesn't work yet in SHR for GTA04). Everything is handled via fsodeviced+(only) rfkill plugin and seems to work. For GPS-poweron/off i'm using a gpsd hook: #!/bin/dash case $2 in DEACTIVATE) POLICY=disabled ;; ACTIVATE) POLICY=enabled ;; *) echo no action specified exit 1 ;; esac dbus-send --system --print-reply --dest=org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.SetResourcePolicy string:GPS string:$POLICY but i think, that's not really necessary with kernel 3.5. Rico signature.asc Description: This is a digitally signed message part. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: status fso for gta04?
Am Donnerstag, 22. November 2012, 21:34:58 schrieb arne anka: is there a debian repository with recent fso packages? Currently i'm working on packages for fso 0.12-rc2. They are in the corresponding 0.12 branches. I hope, i can finish this weekend. Rico signature.asc Description: This is a digitally signed message part. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
accelerometer plugin for gta04
Hi, I did some work on the bma180 acceleroemter plugin for fsodeviced. Unfortunately i don't know, if axis orientation is really correct. Maybe reverse and normal are swapped in landscape mode. Can somebody have a look at this? RicoFrom be2dbf80b7e0f954d63051c446eae3dbe76cc780 Mon Sep 17 00:00:00 2001 From: Rico Rommel r...@bierrommel.de Date: Sun, 18 Nov 2012 17:10:38 +0100 Subject: [PATCH] fsodeviced: add accelerometer plugin bma180 for gta04 --- fsodeviced/conf/GTA04/fsodeviced.conf |8 ++ fsodeviced/configure.ac|1 + fsodeviced/src/plugins/Makefile.am |1 + fsodeviced/src/plugins/accelerometer/plugin.vala |3 + .../src/plugins/accelerometer_bma180/Makefile.am | 40 ++ .../src/plugins/accelerometer_bma180/plugin.vala | 137 6 files changed, 190 insertions(+) create mode 100644 fsodeviced/src/plugins/accelerometer_bma180/Makefile.am create mode 100644 fsodeviced/src/plugins/accelerometer_bma180/plugin.vala diff --git a/fsodeviced/conf/GTA04/fsodeviced.conf b/fsodeviced/conf/GTA04/fsodeviced.conf index 683f9bb..ff368cc 100644 --- a/fsodeviced/conf/GTA04/fsodeviced.conf +++ b/fsodeviced/conf/GTA04/fsodeviced.conf @@ -9,6 +9,14 @@ log_destination = /var/log/fsodeviced.log [fsodevice.kernel26_leds] ignore_by_name = twl4030:vibrator +[fsodevice.accelerometer] +device_type = bma180 +deadzone = 50 +delay = 500 + +[fsodevice.accelerometer_bma180] +inputnode = /input/event1 + [fsodevice.gta04_quirks] [fsodevice.gta04_quirks/info] diff --git a/fsodeviced/configure.ac b/fsodeviced/configure.ac index d984b1e..4dc0161 100644 --- a/fsodeviced/configure.ac +++ b/fsodeviced/configure.ac @@ -229,6 +229,7 @@ AC_CONFIG_FILES([ src/plugins/accelerometer/Makefile src/plugins/accelerometer_kxsd9/Makefile src/plugins/accelerometer_lis302/Makefile + src/plugins/accelerometer_bma180/Makefile src/plugins/audio/Makefile src/plugins/backlight_omappanel/Makefile src/plugins/gpio_input/Makefile diff --git a/fsodeviced/src/plugins/Makefile.am b/fsodeviced/src/plugins/Makefile.am index 1a09e42..94f5060 100644 --- a/fsodeviced/src/plugins/Makefile.am +++ b/fsodeviced/src/plugins/Makefile.am @@ -7,6 +7,7 @@ SUBDIRS = \ accelerometer \ accelerometer_kxsd9 \ accelerometer_lis302 \ + accelerometer_bma180 \ \ audio \ router_alsa \ diff --git a/fsodeviced/src/plugins/accelerometer/plugin.vala b/fsodeviced/src/plugins/accelerometer/plugin.vala index e83beb0..6f5bc80 100644 --- a/fsodeviced/src/plugins/accelerometer/plugin.vala +++ b/fsodeviced/src/plugins/accelerometer/plugin.vala @@ -88,6 +88,9 @@ class Accelerometer : FreeSmartphone.Device.Orientation, case kxsd9: typename = HardwareAccelerometerKxsd9; break; +case bma180: +typename = HardwareAccelerometerBma180; +break; default: logger.error( Unknown accelerometer device type '%s'.printf( devicetype ) ); return; // don't call me again diff --git a/fsodeviced/src/plugins/accelerometer_bma180/Makefile.am b/fsodeviced/src/plugins/accelerometer_bma180/Makefile.am new file mode 100644 index 000..134006c --- /dev/null +++ b/fsodeviced/src/plugins/accelerometer_bma180/Makefile.am @@ -0,0 +1,40 @@ +include $(top_srcdir)/Makefile.decl +NULL = + +AM_CFLAGS = \ + -DG_LOG_DOMAIN=\fsodevice.accelerometer_bma180\ \ + $(NULL) +AM_VALAFLAGS = + +modlibexecdir = $(libdir)/cornucopia/modules/fsodevice +modlibexec_LTLIBRARIES = accelerometer_bma180.la +accelerometer_bma180_la_SOURCES = plugin.vala +accelerometer_bma180_la_VALAFLAGS = \ + --basedir $(top_srcdir) \ + --vapidir ./ \ + --vapidir $(top_srcdir)/src/lib \ + --pkg linux \ + --pkg glib-2.0 \ + --pkg gee-1.0 \ + --pkg fsoframework-2.0 \ + --pkg fso-glib-1.0 \ + --pkg fsodevice-2.0 \ + $(DEBUG_VALAFLAGS) \ + $(NULL) +accelerometer_bma180_la_CFLAGS = \ + -I$(top_srcdir)/src/lib \ + $(GLIB_CFLAGS) \ + $(FSO_CFLAGS) \ + $(DEBUG_CFLAGS) \ + $(NULL) +accelerometer_bma180_la_LIBADD = \ + $(top_builddir)/src/lib/libfsodevice.la \ + $(GLIB_LIBS) \ + $(FSO_LIBS) \ + $(NULL) +accelerometer_bma180_la_LDFLAGS = -no-undefined -module -avoid-version + +CLEANFILES = +MAINTAINERCLEANFILES = \ + Makefile.in \ + $(NULL) diff --git a/fsodeviced/src/plugins/accelerometer_bma180/plugin.vala b/fsodeviced/src/plugins/accelerometer_bma180/plugin.vala new file mode 100644 index 000..3d860a9 --- /dev/null +++ b/fsodeviced/src/plugins/accelerometer_bma180/plugin.vala @@ -0,0 +1,137 @@ +/* + * Copyright (C) 2012 Rico Rommel r...@bierrommel.de + * + * This library is free software; you can redistribute it and/or + * modify it under the terms of the GNU Lesser General Public + * License as published by the Free Software Foundation; either + * version 2.1 of the License, or (at your option) any later version. + + * This library is distributed
Re: Basic good configuration of Debian on GTA02
Am Montag, 29. Oktober 2012, 01:52:41 schrieb Dima: Hi. I have installed Debian on GTA02 (SD card). Following the wiki page, I did: apt-get remove --purge openmoko-panel-plugin apt-get install e17 foxtrotgps gpsd navit omhacks monav midori wicd lxterminal phoneui-apps and 'enlightenment_start' in /root/.xsession Now I have a half working enlightenment :) No phone related program ssucceed to start. How do I configure the system to work well? I only need phone and SMS... No GPS,accelerometers etc. The Debian page on openmoko.org seems pretty old... (zhone). Any other suggestions ? Or better use FSO1 and Zhone currently? Try installing package fso-gta02. It depends on all needed configs and fso-packages. Rico signature.asc Description: This is a digitally signed message part. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Is fsogsmd killing my app?
Hi all, I have a very strange problem: My application connects to fsogsmd to make calls, show available networks etc. A few minutes after registering to a network the application exits without any reason. It doesn't crash, it receives a kill signal from a unknown sender and closes. To debug i made the app ignore the kill signal and noticed, that the signal is repeated from time to time, approximately every minute. It appears only when registered to a network, without registration every thing is fine. Btw, the application is written in qt4. Rico signature.asc Description: This is a digitally signed message part. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: [Shr-Devel] About the future of the freesmartphone.org middleware
Am Sonntag, 22. Juli 2012, 12:03:38 schrieb Neil Jerram: But your wider problem is that you're working in a vacuum, because there's no reasonably widely used phone distribution that uses FSO and that is also regularly and safely updated. That means you have no users for your incremental improvements. I think that's not true. There are users outside distributions using FSO for own applications, like me. Big thanks to Simon (and Mickey) Rico signature.asc Description: This is a digitally signed message part. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
TiCalypsoModem 4C: No handler for URC ATE0Q0V1
Hi, after upgrading to fso-gsmd 0.11.2 modem on GTA02 doesn't work anymore. fsogsmd.log says: TiCalypsoModem 4C: Opening the modem device... 2000-01-01T00:46:34.526901Z [DEBUG] fsogsmd : GLib fsogsm.lowlevel_openmoko: plugin.vala:81: --- while loop ENTER; i = 1 2000-01-01T00:46:38.566653Z [DEBUG] TiCalypsoModem 4C: Will open 4 channels... 2000-01-01T00:46:40.623789Z [DEBUG] TiCalypsoUnsolicitedResponseHandler : Dispatching AT unsolicited 'AT-Command Interpreter ready', '' 2000-01-01T00:46:40.624289Z [DEBUG] TiCalypsoModem 4C: Congratulations Madam, it's a channel! 2000-01-01T00:46:40.647760Z [DEBUG] TiCalypsoUnsolicitedResponseHandler : Dispatching AT unsolicited 'AT-Command Interpreter ready', '' 2000-01-01T00:46:40.648099Z [DEBUG] TiCalypsoModem 4C: Congratulations Madam, it's a channel! 2000-01-01T00:46:41.824520Z [DEBUG] TiCalypsoUnsolicitedResponseHandler : Dispatching AT unsolicited 'AT-Command Interpreter ready', '' 2000-01-01T00:46:41.824864Z [DEBUG] TiCalypsoModem 4C: Congratulations Madam, it's a channel! 2000-01-01T00:46:43.024401Z [DEBUG] TiCalypsoUnsolicitedResponseHandler : Dispatching AT unsolicited 'AT-Command Interpreter ready', '' 2000-01-01T00:46:43.024744Z [DEBUG] TiCalypsoModem 4C: Congratulations Madam, it's a channel! 2000-01-01T00:46:44.209945Z [DEBUG] FsoGsmGenericWatchDog P:|KR:false: onModemStatusChange FSO_GSM_MODEM_STATUS_CLOSED - FSO_GSM_MODEM_STATUS_INITIALIZING 2000-01-01T00:46:44.211375Z [DEBUG] TiCalypsoModem 4C: Initializing channel call ... 2000-01-01T00:46:44.211773Z [DEBUG] TiCalypsoModem 4C: Main channel not initialized yet... waiting 2000-01-01T00:46:44.212390Z [DEBUG] TiCalypsoModem 4C: Initializing channel main ... 2000-01-01T00:46:44.215094Z [DEBUG] TiCalypsoModem 4C: Initializing channel urc ... 2000-01-01T00:46:44.215579Z [DEBUG] TiCalypsoModem 4C: Main channel not initialized yet... waiting 2000-01-01T00:46:44.216106Z [DEBUG] TiCalypsoModem 4C: Initializing channel data ... 2000-01-01T00:46:44.216477Z [DEBUG] TiCalypsoModem 4C: Main channel not initialized yet... waiting 2000-01-01T00:46:44.226671Z [INFO] TiCalypsoModem 4C: Modem Status changed to FSO_GSM_MODEM_STATUS_INITIALIZING 2000-01-01T00:46:44.227301Z [INFO] DBusServiceDevice : Modem opened successfully 2000-01-01T00:46:45.515619Z [DEBUG] TiCalypsoModem 4C: Main channel not initialized yet... waiting ... 2000-01-01T00:46:48.516539Z [DEBUG] TiCalypsoModem 4C: Main channel not initialized yet... waiting 2000-01-01T00:46:49.517455Z [DEBUG] TiCalypsoUnsolicitedResponseHandler : Dispatching AT unsolicited 'ATE0Q0V1', '' 2000-01-01T00:46:49.517971Z [WARN] TiCalypsoModem 4C: No handler for URC ATE0Q0V1 w/ rhs , please report to Mickey smartphones-userland@linuxtogo.org 2000-01-01T00:46:49.518436Z [DEBUG] TiCalypsoModem 4C: Main channel not initialized yet... waiting ... 2000-01-01T00:46:58.516592Z [DEBUG] TiCalypsoModem 4C: Main channel not initialized yet... waiting 2000-01-01T00:46:59.516937Z [DEBUG] TiCalypsoUnsolicitedResponseHandler : Dispatching AT unsolicited 'ATE0Q0V1', '' 2000-01-01T00:46:59.517320Z [WARN] TiCalypsoModem 4C: No handler for URC ATE0Q0V1 w/ rhs , please report to Mickey smartphones-userland@linuxtogo.org 2000-01-01T00:46:59.517761Z [DEBUG] TiCalypsoModem 4C: Main channel not initialized yet... waiting ... What's going wrong here? After a downgrade to fso-gsmd 0.5+git20120305 it works again. Rico signature.asc Description: This is a digitally signed message part. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: debian + phoneui-apps
Am Dienstag, 27. März 2012, 05:09:19 schrieb Brendon Schumacker: 2012.03.26 14:32:18.787663 [phonefsod] WARNING: failed to connect to /org/freesmartphone/GSM/Device: Error calling StartServiceByName for org.freesmartphone.ogsmd: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freesmartphone.ogsmd timed out 2012.03.26 14:32:28.378662 [phonefsod] CRITICAL: !!! ouch, phoneuid is gone - telephony won't work anymore !!! Then in Ubuntu I did a apt-cache search fso and installed everything that looked relevant there. Only one of them updated. And with ps aux it seems that everything is running as it should be, so the problem seems beyond me at this point. Please make sure, fso-gta02 and fso-frameworkd-gta02, phoenuid and e17 are installed. Theydepend on all needed packages and install them. If the PIN-Dialog doesn't show up, insert something like dbus-send --system --dest=org.freesmartphone.ousaged /org/freesmartphone/Usage org.freesmartphone.Usage.RequestResource string:GSM into ~/.xsession Basically, there is no additional configuration needed. /usr/share/phoneuid/phoneui-wrapper.sh If everything is correct, this isn't needed. You can swap out xfce with enlightenment and it still works which is great. Although I couldn't close Contacts after opening it because there was no close button, that might also be a SHR specific trait. If you are using illume1 tap on top-panel and then on X to close or load module illume-softkey. On illume2 you can install shr-e-gadgets (It's not in Debian yet) git://anonscm.debian.org/pkg-fso/shr-e-gadgets.git and then echo shr_elm_softkey.desktop ~/.e/e/applications/startup/.order If you tap on top-panel, you should be able to switch and close windows. Rico signature.asc Description: This is a digitally signed message part. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: debian + phoneui-apps
Am Dienstag, 27. März 2012, 15:19:08 schrieb Timo Jyrinki: Sound works from FreeRunner to the other phone, but I don't seem to get audio from FreeRunner with the default settings (nor the speaker switch works). Please check, if the symlink /etc/freesmartphone/conf/GTA02/alsa-default points to the correct kernel version. Rico signature.asc Description: This is a digitally signed message part. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: openmoko neo --- Debian install from scratch now works
Am Donnerstag, 18. August 2011, 21:31:30 schrieb Roland Mas: I'd suggest an extra step (unless Timo has updated the install.sh again): take the xorg.conf listed at http://kerneltrap.org/mailarchive/openmoko-community/2010/12/29/14355 and substitute glamo with fbdev in there, otherwise the X server will start eating your CPU as soon as you touch the screen and keep chomping on it until you end the X session. I don't think, that's a problem with glamo. It seems to be a conflict between tslib and evdev. My solution is to use evdev for touchscreen events: 1. remove xserver-xorg-input-tslib 2. my xorg.conf # Xorg confiugration for an Openmoko FreeRunner Section Device Identifier Configured Video Device Driver glamo EndSection # complementary information on the touch screen as the # input device is provided by udev Section Screen IdentifierDefault Screen DeviceConfigured Video Device DefaultDepth16 SubSection Display Depth16 Modes 480x640 640x480 ViewPort 0 0 Virtual 640 640 EndSubSection EndSection 3. swap axis of touchscreen /etc/X11/Xsession.d/89ts_calibrate: xinput set-int-prop S3C24XX TouchScreen Evdev Axis Calibration 32 107 918 911 98 xinput set-int-prop S3C24XX TouchScreen Evdev Axes Swap 8 1 Rico signature.asc Description: This is a digitally signed message part. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: gps powercontrol
Am Montag, 8. August 2011, 23:11:00 schrieb Timo Juhani Lindfors: Hi, Rico Rommel r...@bierrommel.de writes: Except of one all of my SD-Cards are usable. I'm using u-boot and kernel from git://gitorious.org/shr/linux.git branch: shr-2.6.37-nodrm config is attached. Thanks. I'm packaging qi for debian since it seems that we don't have enough people to merge the u-boot patches to debian. If you have many SD cards I'd like to know if they work with qi from Sorry, at the moment I can't test with the other sd-cards, because they are in use by other devices. Btw, I had much trouble with qi. From time to time modem and gps stopped working and a reboot, or even removing battery, didn't help. To make it work again i had to boot into NOR. Currently I'm using u-boot (http://wiki.openmoko.org/wiki/U-boot-gena2x) without that problems . Rico signature.asc Description: This is a digitally signed message part. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: gps powercontrol
git commit patch is attached. I hope, it's right.
Rico
From c0005afadd848a86db0f94cc291b6ff35f533c76 Mon Sep 17 00:00:00 2001
From: Rico Rommel r...@bierrommel.de
Date: Thu, 28 Jul 2011 08:43:20 +0200
Subject: [PATCH] fsodevice: add gps powercontrol
---
.../src/plugins/openmoko_powercontrol/plugin.vala | 25
1 files changed, 20 insertions(+), 5 deletions(-)
diff --git a/fsodeviced/src/plugins/openmoko_powercontrol/plugin.vala b/fsodeviced/src/plugins/openmoko_powercontrol/plugin.vala
index 111354f..f1a7f73 100644
--- a/fsodeviced/src/plugins/openmoko_powercontrol/plugin.vala
+++ b/fsodeviced/src/plugins/openmoko_powercontrol/plugin.vala
@@ -24,16 +24,16 @@ namespace Openmoko
public static const string CONFIG_SECTION = fsodevice.openmoko_powercontrol;
/**
- * Bluetooth power control for Openmoko GTA01 and Openmoko GTA02
+ * Common device power control for Openmoko GTA01 and Openmoko GTA02
**/
-class BluetoothPowerControl : FsoDevice.BasePowerControl
+class DevicePowerControl : FsoDevice.BasePowerControl
{
private FsoFramework.Subsystem subsystem;
private string sysfsnode;
private string name;
-public BluetoothPowerControl( FsoFramework.Subsystem subsystem, string sysfsnode )
+public DevicePowerControl( FsoFramework.Subsystem subsystem, string sysfsnode )
{
base( Path.build_filename( sysfsnode, power_on ) );
this.subsystem = subsystem;
@@ -134,15 +134,16 @@ public static string fso_factory_function( FsoFramework.Subsystem subsystem ) th
var drivers = Path.build_filename( sysfs_root, bus, platform, drivers );
var ignore_bluetooth = config.boolValue( Openmoko.CONFIG_SECTION, ignore_bluetooth, false );
+var ignore_gps = config.boolValue( Openmoko.CONFIG_SECTION, ignore_gps, false );
var ignore_wifi = config.boolValue( Openmoko.CONFIG_SECTION, ignore_wifi, false );
var ignore_usbhost = config.boolValue( Openmoko.CONFIG_SECTION, ignore_usbhost, false );
if ( !ignore_bluetooth )
{
-var bluetooth = Path.build_filename( devices, neo1973-pm-bt.0 );
+var bluetooth = Path.build_filename( devices, gta02-pm-bt.0 );
if ( FsoFramework.FileHandling.isPresent( bluetooth ) )
{
-var o = new Openmoko.BluetoothPowerControl( subsystem, bluetooth );
+var o = new Openmoko.DevicePowerControl( subsystem, bluetooth );
instances.append( o );
#if WANT_FSO_RESOURCE
resources.append( new FsoDevice.BasePowerControlResource( o, Bluetooth, subsystem ) );
@@ -150,6 +151,20 @@ public static string fso_factory_function( FsoFramework.Subsystem subsystem ) th
}
}
+if ( !ignore_gps )
+{
+var gps = Path.build_filename( devices, gta02-pm-gps.0 );
+if ( FsoFramework.FileHandling.isPresent( gps ) )
+{
+var o = new Openmoko.DevicePowerControl( subsystem, gps );
+instances.append( o );
+#if WANT_FSO_RESOURCE
+resources.append( new FsoDevice.BasePowerControlResource( o, GPS, subsystem ) );
+#endif
+}
+}
+
+
if ( !ignore_usbhost )
{
var usbhost = Path.build_filename( devices, gta02-pm-usbhost.0 );
--
1.7.5.4
signature.asc
Description: This is a digitally signed message part.
___
Smartphones-userland mailing list
Smartphones-userland@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: gps powercontrol
Am Dienstag, 26. Juli 2011, 09:59:32 schrieb Timo Juhani Lindfors: Hi, Rico Rommel r...@bierrommel.de writes: since ogpsd is more or less useless because nobody uses gypsy and conflicts with gpsd, I think it's a good idea to include gps powercontrol into fsodeviced. Which kernel versions does this support? It's supported by 2.6.37 signature.asc Description: This is a digitally signed message part. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
[solved] Re: phoneuid crashes
It was my fault. libphone-ui was on branch gdbus. After checking out master und recompile everything works. Rico signature.asc Description: This is a digitally signed message part. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
Re: phoneuid crashes
Am Sonntag, 30. Januar 2011, 13:36:10 schrieb Klaus Kurzmann: Am Sonntag, 30. Januar 2011, 12:58:59 schrieb Rico Rommel: Am Sonntag, 30. Januar 2011, 11:10:37 schrieb Timo Juhani Lindfors: Rico Rommel r...@bierrommel.de writes: 0x403d768c in free_smartphone_pim_messages_query (self=0x0, query=0x87120, self=0x0 is bad :P looks like opimd is not there? opimd is up and running. opimd-cli shows all messages. Rico signature.asc Description: This is a digitally signed message part. ___ Smartphones-userland mailing list Smartphones-userland@linuxtogo.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/smartphones-userland
