Re: battery on Qtopia 4.4.2
François de Ryckel wrote: Hi everyone, The lifespan of a battery charge on my FR is no more than one night. Anything one can do about it? I'm a newbie in the Opemoko community - I'm a linux user since a few year but definetely not a computer geek! I'm just a big opensource software user fan - so go easy with the explanations :) Welcome to the openmoko community. We're like a dysfunctional family with a love/hate relationship to the device. I've never managed to get more than that much battery life out of mine. It's one of the biggest issues affecting usability. Some folks claim to have had better luck, hopefully one of them will answer, but AFAICT you haven't done anything wrong, it just eats power *that* fast. -- View this message in context: http://n2.nabble.com/battery-on-Qtopia-4.4.2-tp2155202p2156371.html Sent from the Openmoko Support mailing list archive at Nabble.com. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: battery on Qtopia 4.4.2
with debian/fso when using suspend i get usually 48 to 72 hours standby time (but i very seldom make or receive calls). anyway, even qtopia should have suspend, or am i wrong here? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: OpenMoko + Exchange
By the way, for clarification, I don't think there has ever been native support for MS exchange in evolution, and anyways the binary protocol only works within your Lan. Evolution Exchange is a wrapper around the Web Interface of Exchange server. Today it works quite reliably, but it's still a little intensive on network and memory. Also, MS Exchange is not IMAP compatible without alteration of the server. For sure with a PIM support in FSO we will be more equipe to integrate mail backends like Exchange. Nicolas Le mardi 13 janvier 2009 à 23:39 +0100, Petr Vanek a écrit : i've done a decent amount of searching around. i have not found any direct answer to my question: does OpenMoko allow/support communication with an Exchange server. besides all the other posts on this topic, i think the issue it that the real pim support is so far being planned. after storage is fixed, we can look at synchronization. this is my understanding. -- Petr Vaněk ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: battery on Qtopia 4.4.2
I can speak for OM2008.x FSO and SHR. FSO and SHR have basically the same battery life. Without going to suspend you'll have 8+ hours, in suspend you'll get the 48 ours (72 is pushing it, but it could happen). I currently am experiencing issues making and receiving calls reliably with SHR and FSO. OM2008.x has fairly reliable call making and text message capabilities, however the call quality needs improvement. I cannot speak for Debian. On Wed, Jan 14, 2009 at 6:51 AM, arne anka openm...@ginguppin.de wrote: with debian/fso when using suspend i get usually 48 to 72 hours standby time (but i very seldom make or receive calls). anyway, even qtopia should have suspend, or am i wrong here? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- Paul Email - pault...@gmail.com There were moments when he looked on evil simply as a mode through which he could realize his conception of the beautiful. Oscar Wilde - The Picture of Dorian Gray ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Call Volume on wired headset
I'm using the latest testing milestone of FSO, and am trying to get the wired headset working better on zhone calls. The earbud volume is rather weak. I've altered gsmheadset.state control.3 values to 1 (from 87). It's turned up the volume a bit, but still not enough. I also changed the value of control.6 to 1 as well. Maybe I'm not getting how this works. I tried the maximum value of control.3 (120 or something), but that seemed to make it quieter. Can someone guide me on how to make the wired headset louder. It's now a law in Ontario that you have to use hands-free while driving, and right now, I won't be able to hear anything with noise created driving on the highway. Thanks, Marcus ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: OpenMoko + Exchange
On Wed, Jan 14, 2009 at 2:45 PM, Nicolas Dufresne nicolas.dufre...@gmail.com wrote: Evolution Exchange is a wrapper around the Web Interface of Exchange server. Are you sure of that? I thought it was based on Exchange's WebDAV access, which is a bit different. Sure it's still tied to web technologies, and needs OWA to be enabled on the server, but it's much more efficient than wrapping around a web interface, and should work well over the internet (you can proxy it through HTTPS frontends or anything, if you want). There was another connector-like-thing named Brutus, who forced MAPI commands through CORBA. But it needed some code at both side (a daemon on the server side, and libbrutus on the device/application). I don't know if it's still active, though. There's also some opensource code regarding ActiveSync over the air in Zarafa/ZPush projects. This implements part (only server part, sadly) of Microsoft's protocol for synchronizing devices over HTTP(S) connections, supporting even idling connections (branded as DirectPush) to avoid constant polling. Maybe someone can guess the client part of the protocol by looking at ZPush. It's PHP code, so if anyone is brave enough ;) Another way, which sounds much more practical for desktop than embedded use, is the wonderful work of OpenChange's guys : namely a bunch of code to emulate several parts of the Exchange architecture within an AD/Samba4 environment. Though it should be pretty effective in a LAN, I guess it would need some heavy tweaks to be used over the internet. Any other ideas? -- Olivier ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: battery on Qtopia 4.4.2
Salut Francois, I'm also using QtE 4.4.2, and I get something more than 48 hours of battery. I think the trick is enabling suspend - I think it's off by default - if you go into settings, select 'Power Management', and make sure that something reasonble is set for the suspend timeout - I have mine set as 20s to dim, 30s to display off, and 40s to suspend. The big difference with QtE vs. the 2008.X distro's I've used is that the phone unsuspends quickly enough that you can reliably answer incoming calls - when I was using the 2008.X based distros I regularly missed calls... Hope this helps. Warren On Wed, Jan 14, 2009 at 12:01 AM, François de Ryckel f.deryc...@gmail.comwrote: Hi everyone, The lifespan of a battery charge on my FR is no more than one night. Anything one can do about it? I'm a newbie in the Opemoko community - I'm a linux user since a few year but definetely not a computer geek! I'm just a big opensource software user fan - so go easy with the explanations :) Thanks in advance for your help. Francois ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: battery on Qtopia 4.4.2
Am Mittwoch 14 Januar 2009 schrieb arne anka: with debian/fso when using suspend i get usually 48 to 72 hours standby time (but i very seldom make or receive calls). anyway, even qtopia should have suspend, or am i wrong here? Yeah, you can get up to that many hours from QTe, too. Just go to settings - power management and set a time after Suspend at the settings when on battery. Works good here. QTe wakes up on calls or when you press power. It just takes one or two seconds. -- j�...@home ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: battery on Qtopia 4.4.2
Am Mittwoch 14 Januar 2009 schrieb Joerg Lippmann: Am Mittwoch 14 Januar 2009 schrieb arne anka: with debian/fso when using suspend i get usually 48 to 72 hours standby time (but i very seldom make or receive calls). anyway, even qtopia should have suspend, or am i wrong here? Yeah, you can get up to that many hours from QTe, too. Just go to settings - power management and set a time after Suspend at the settings when on battery. Works good here. QTe wakes up on calls or when you press power. It just takes one or two seconds. Oh, and don't forget that the suspend settings are tied to the profiles. So if you change the suspend timeout, use the options button on the lower left to add them to your current profile. -- j�...@home ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
[FSO] Re: Call Volume on wired headset
On Wednesday 14 January 2009, Marcus Stong wrote: I'm using the latest testing milestone of FSO Please quote the actual version number to avoid confusion. As I understand it 'latest milestone' is currently 4.1. It also helps to know whether you have gta01 or gta02 as the mixer channel numbers are apparently different. , and am trying to get the wired headset working better on zhone calls. The earbud volume is rather weak. I've altered gsmheadset.state control.3 values to 1 (from 87). It's turned up the volume a bit, but still not enough. That's odd - setting it to 1 should give almost no output, at least on a gta02. Mine is at 96 and maxmum is 127. I also changed the value of control.6 to 1 as well. From what? Mine is at 7 (maximum) Maybe I'm not getting how this works. I tried the maximum value of control.3 (120 or something), but that seemed to make it quieter. That's very strange. It seems as though you are editing the correct controls, and the differences should be obvious given the large level changes you seem to be making. I can't test it myself until I've resoldered my headset, but I've not had any problems with it in the past when changing audio settings. i haven't checked to see that FSO does actually use the gsmheadset.state when the headset is plugged in. I assume you are editing the file, saving the changes then starting a new phone call to test the settings. Can someone guide me on how to make the wired headset louder. It's now a law in Ontario that you have to use hands-free while driving, and right now, I won't be able to hear anything with noise created driving on the highway. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: OpenMoko + Exchange
I might show how 'green' I am (in regards to all things Linux), but Ubuntu 8.10 ships with Evolution Email (don't recall which version), but it works near perfect with Exchange servers (cannot pull up shared calendars being its 1 fault - this is NOT a show stopper for me). My question (in a nutshell) was basically 'is there a portable version of Evolution Email was available for OpenMoko?' Because, the Evolution Email guys got it working right, and that would be an absolutely ideal platform for me. During the setup process for the mail account within Evolution Email, you do specify the HTTPS server hosting your Exchange account, but Outlook works the exact same way. So again, if Evolution Email is available on OpenMoko, then I believe that YES there is a way to get Exchange email on a OpenMoko device... Does that make sense? :) Olivier Migeot wrote: On Wed, Jan 14, 2009 at 2:45 PM, Nicolas Dufresne nicolas.dufre...@gmail.com wrote: Evolution Exchange is a wrapper around the Web Interface of Exchange server. Are you sure of that? I thought it was based on Exchange's WebDAV access, which is a bit different. Sure it's still tied to web technologies, and needs OWA to be enabled on the server, but it's much more efficient than wrapping around a web interface, and should work well over the internet (you can proxy it through HTTPS frontends or anything, if you want). There was another connector-like-thing named Brutus, who forced MAPI commands through CORBA. But it needed some code at both side (a daemon on the server side, and libbrutus on the device/application). I don't know if it's still active, though. There's also some opensource code regarding ActiveSync over the air in Zarafa/ZPush projects. This implements part (only server part, sadly) of Microsoft's protocol for synchronizing devices over HTTP(S) connections, supporting even idling connections (branded as DirectPush) to avoid constant polling. Maybe someone can guess the client part of the protocol by looking at ZPush. It's PHP code, so if anyone is brave enough ;) Another way, which sounds much more practical for desktop than embedded use, is the wonderful work of OpenChange's guys : namely a bunch of code to emulate several parts of the Exchange architecture within an AD/Samba4 environment. Though it should be pretty effective in a LAN, I guess it would need some heavy tweaks to be used over the internet. Any other ideas? -- Olivier ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- View this message in context: http://n2.nabble.com/OpenMoko-%2B-Exchange-tp2152518p2158278.html Sent from the Openmoko Support mailing list archive at Nabble.com. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [FSO] Re: Call Volume on wired headset
Hey Al, Phone's gta02 with FSO milestone 4.1. I changed the values back up to 127 and 7, and rebooted, and then made a call, with no difference. I wonder does FSO or zhone not use the .state files? Just to be clear, I'm changing the gsmheadset.state file at /usr/share/openmoko/scenarios Marcus On Wed, Jan 14, 2009 at 12:13 PM, Al Johnson openm...@mazikeen.demon.co.ukwrote: On Wednesday 14 January 2009, Marcus Stong wrote: I'm using the latest testing milestone of FSO Please quote the actual version number to avoid confusion. As I understand it 'latest milestone' is currently 4.1. It also helps to know whether you have gta01 or gta02 as the mixer channel numbers are apparently different. , and am trying to get the wired headset working better on zhone calls. The earbud volume is rather weak. I've altered gsmheadset.state control.3 values to 1 (from 87). It's turned up the volume a bit, but still not enough. That's odd - setting it to 1 should give almost no output, at least on a gta02. Mine is at 96 and maxmum is 127. I also changed the value of control.6 to 1 as well. From what? Mine is at 7 (maximum) Maybe I'm not getting how this works. I tried the maximum value of control.3 (120 or something), but that seemed to make it quieter. That's very strange. It seems as though you are editing the correct controls, and the differences should be obvious given the large level changes you seem to be making. I can't test it myself until I've resoldered my headset, but I've not had any problems with it in the past when changing audio settings. i haven't checked to see that FSO does actually use the gsmheadset.state when the headset is plugged in. I assume you are editing the file, saving the changes then starting a new phone call to test the settings. Can someone guide me on how to make the wired headset louder. It's now a law in Ontario that you have to use hands-free while driving, and right now, I won't be able to hear anything with noise created driving on the highway. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
bad time_and_date from gpsd again
The following shows some strange behaviour from gpsd. The current time is 19.18 and year 2008-01-14. Why is the time incorrect from gpsd? r...@om-gta01:~# telnet localhost 2947 d GPSD,D=1999-11-30T23:59:46.00Z signature.asc Description: Detta är en digitalt signerad meddelandedel ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: OpenMoko + Exchange
On Wed, Jan 14, 2009 at 7:03 PM, not12listen not12lis...@gmail.com wrote: Does that make sense? :) It does. But it's not the faint hearted. Getting Evolution to run on Neo won't be too easy, but it should be reasonnably doable (in a perfect world, it might compile directly on arm... maybe it already does, btw). Then having it running everyday would start to be a pain in some lower parts : Evolution, as nice as it is, needs a _lot_ of resource compared to what a Freerunner can offer. The screen size might be a pain too. Well it's surely possible to run Evolution. Now whether that would be the solution to not12listen's problem or not is another whole debate. And if it were that easy, it'd be done already (Evolution can do much more than Exchange connectivity, and _many_ people would love those too). Our guy asked if he _can_ read Exchange mail's on OM. Not within the year, nor in an unknown future, but _now_. And _now_, he can't. We got too many people disappointed by the Freerunner, we don't need another one. -- Olivier ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Once a whiner
2009/1/9 Marcus Stong sto...@gmail.com I'd just like to say, for all the whiners using om 2008.x (I've been one just recently, too), try FSO testing. I've been using it for a few days, and everything seems to work like a charm compared to OM2008.x. Umh... it seems it's not so stable...I was missing for the last 3 weeks so perhaps I'm outdated on some informations ;) However I installed the latest testing fso-image (14 jan), but it seems it has no X server, on the download page it seems as that from 13 Jan the image size is smaller than before. Is it something to be fixed or am I missing sometingh? The image from 13 jan is not able to mount root device, and that from 8 jan on the first boot freezed on the illume initial setup. I always thinked FSO is an hacker image to develop and test the framework, and that the FSO team is not focused on the pure image stabilization, please correct me if I'm wrong, but I think that now SHR is actually the only alternative to Qtextended and 2008.12 to be used both for production and for developing new applications in a quite stable system environment ? Nicola ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: battery on Qtopia 4.4.2
About QT Extended. Anyone experiencing the Echo Bug? Is there a resolution to it without turning down the volume? Thanks. -- Paul Email - pault...@gmail.com There were moments when he looked on evil simply as a mode through which he could realize his conception of the beautiful. Oscar Wilde - The Picture of Dorian Gray ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: OpenMoko Webcam
Hello,
Fantastic that worked - thank you very much (I needed a make
prepare before running make sound and I also needed to dig out a modpost
script which I had premade), I used xawtv and luvcview to try out my camera
(Philips SPC630NC) - I too had the poor resolution you described. I'm
testing it out to see if it is good enough for me but I suspect that it will
not be :(.
Cheers,
Neil
2009/1/14 Rask Ingemann Lambertsen r...@sygehus.dk
On Sun, Jan 11, 2009 at 02:51:07PM +0100, Neil Benn wrote:
Hello,
I am trying to enable support on my OpenMoko for Webcams. I
have
followed the instructions to install debian by using the installation
script
described at : http://wiki.debian.org/DebianOnFreeRunner. I then
followed
the instructions for openmoko and webcam at :
http://wiki.openmoko.org/wiki/Webcam.
I found that those instructions don't work, presumably because they are
outdated. Here's how I got it to work:
--- begin HOWTO ---
This is a description of how to use
a USB webcam on a Neo Freerunner running the Debian distribution as of
2009-01-01. There are three parts to it:
1) Compiling the necessary kernel modules,
2) Installing utilities for changing USB mode (host/device).
3) Installing a video program.
Throughout, commands prefixed with # should be run as root while commands
prefixed with $ should be run as a normal user.
1. Compiling the necessary kernel modules,
# echo 'deb-src http://pkg-fso.alioth.debian.org/debian unstable main'
/etc/apt/sources.list.d/pkg-fso.list
# apt-get update
# apt-get install dpkg-dev bzip2 gcc make xutils-dev libc6-dev
libncurses5-dev
$ cd ~
$ mkdir download source build
$ cd source
$ dpkg --list | grep -F -e linux-image-
ii linux-image-2.6.24-openmoko-gta02 20081[...]
$ apt-get source linux-image-2.6.24-openmoko-gta02
You should now have an unpacked linux kernel tree. Make note of the extra
version
string in the directory name, which in this particular case it is
'-20081103.git7172ec57'. For example, use your terminal's copy/paste
facility to
make a copy of it before the 'make menuconfig' command below.
$ cd ~/build mkdir linux-2.6-openmoko-20081103.git7172ec57 cd
linux-2.6-openmoko-20081103.git7172ec57
(making use of TAB-completion to save some typing)
$ lndir -silent ../../source/linux-2.6-openmoko-20081103.git7172ec57
$ cp /boot/config-2.6.24-20081103.git7172ec57 .config
$ make menuconfig
In 'General setup', 'Local version' enter the version string from above.
Nothing bad will happen to your Neo if you get it wrong, you'll just be
sorry
in an hour or so when your modules won't load.
Most new USB cameras comply with the USB Video Class standard, for which no
driver was included in the 2.6.24 kernel, and the other drivers have since
been updated. We'll download and compile the camera drivers separately.
Some cameras include a microphone as a standard USB audio device. Enable it
here:
Device Drivers - Sound - Advanced Linux Sound Architecture - USB devices
- USB Audio/MIDI driver (type m)
Exit the menus all the way back to the shell, saving your new kernel
configuration.
$ make M=sound modules
(10 minutes go by)
Install the sound modules:
$ su root
# make M=sound modules_install
# exit
Now we'll build the camera drivers.
$ cd ~
$ su root
# ln -sf ${PWD}/source/linux-2.6-openmoko-20081103.git7172ec57
/lib/modules/2.6.24-20081103.git7172ec57/source
# ln -sf ${PWD}/build/linux-2.6-openmoko-20081103.git7172ec57
/lib/modules/2.6.24-20081103.git7172ec57/build
# exit
$ cd ~/source
$ wget
http://linuxtv.org/hg/~pinchartl/uvcvideo/archive/tip.tar.bz2http://linuxtv.org/hg/%7Epinchartl/uvcvideo/archive/tip.tar.bz2-O
- | tee ~/download/uvcvideo-tip.tar.bz2 | tar -jxf -
$ sed -i -e 's/-type/-xtype/' uvcvideo-bb383c9099da/v4l/Makefile
$ cd ~/build mkdir uvcvideo-bb383c9099da cd uvcvideo-bb383c9099da
$ lndir -silent ../../source/uvcvideo-bb383c9099da
$ make menuconfig
Disable (type n) all the radio, tuner, DVB and DAB support unless you
have devices which use it. Under 'Video capture adaptors', you can disable
the
teletext and debug options. Under 'V4L USB devices' leave all the drivers
enabled unless you already know which one(s) you'll need. Exit, saving your
configuration.
$ make
(may take as much as 45 minutes)
# su root
# make install
# exit
2. Installing utilities for changing USB mode (host/device).
Starting with version 0.7, openmoko-panel-plugin can do this for you.
You can also install the usbmode tool found here (dpkg --force-architecture
...):
http://www.opkg.org/package_42.html
Usbmode needs to run as root, however. Either you know how to make a sudo
setup for it, or you'll make it setuid root:
# chmod u+s /usr/bin/usbmode.py
3. Installing a video program (UNDER CONSTRUCTION).
guvcview
cheese
And all of this without needing to reboot.
--- end HOWTO ---
I tried it with a
Re: Once a whiner
Nicola Mfb wrote: 2009/1/9 Marcus Stong sto...@gmail.com mailto:sto...@gmail.com I'd just like to say, for all the whiners using om 2008.x (I've been one just recently, too), try FSO testing. I've been using it for a few days, and everything seems to work like a charm compared to OM2008.x. Umh... it seems it's not so stable...I was missing for the last 3 weeks so perhaps I'm outdated on some informations ;) However I installed the latest testing fso-image (14 jan), but it seems it has no X server, on the download page it seems as that from 13 Jan the image size is smaller than before. Is it something to be fixed or am I missing sometingh? The image from 13 jan is not able to mount root device, and that from 8 jan on the first boot freezed on the illume initial setup. I always thinked FSO is an hacker image to develop and test the framework, and that the FSO team is not focused on the pure image stabilization, please correct me if I'm wrong, but I think that now SHR is actually the only alternative to Qtextended and 2008.12 to be used both for production and for developing new applications in a quite stable system environment ? That's my experience. After more than enough frustration with basic stuff in 2008.x and FSO, I tried SHR (image 08.12.16) and I'm quite happy with it. Mind you, I'm not an intensive neither extensive phone user but I can easily pin the GSM code, call and add contacts. I love the screen keyboard although I could not find it by myself initially. I'm now playing with GPS, and it works but I'm getting long fix times (tried only a night in a single place). Plenty of apps to try out yet. Nicola ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: bad time_and_date from gpsd again
2009/1/14 Daniel Willmann dan...@openmoko.org Since you talked about gpsd (I am assuming you're not using FSOs ogpsd and compatibility layers) the aiding stuff will not work and you will need to wait for the right time for some while after powering on the GPS. That's wrong. I'm using SHR, I have disabled the gps stuff from fso and I'm using the gpsd from 2007.2. I use the aid-data from ublox and I get 12/5 satellites (or more) within 60 seconds. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
