Re: GPS Problem (maybe antenna?)

2008-09-03 Thread Ole Kliemann
On Wed, Sep 03, 2008 at 03:59:02AM +0200, Marco Trevisan (Treviño) wrote:
 Sebastian M. wrote:
  Quoting Marco Trevisan (Treviño) [EMAIL PROTECTED]:
  Which distributor will give you them as warranty fixes?
  In Germany (and the whole European Union, I guess) the retailers are  
  forced to give a 2 years warranty and because of that they have to  
  replace goods which have problems like an advertised feature not  
  working (like the Freerunners GPS [-hardware] in my case).
  
  As far as I know the same thing applies to distributors (in Germany  
  and maybe EU as well).
 
 I'm in EU too: Italy, but I've bought the Freerunner in Germany 
 (HandHeld-Linux) I was just wondering if they could replace/fix the 
 phone if I'll send them for a gps/gsm fix...
 Cause this is a common problem for all the first-stock freerunners.

Bought mine from handheld too. :) I already asked them about GPS. If
it's not working they'll fix it. With GSM it will be the same I think.
As I said, just waitin' for the GSM fix to send them my FR.

Ole


pgp271Eba7YRe.pgp
Description: PGP signature
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support


Re: GPS Problem (maybe antenna?)

2008-09-03 Thread Ole Kliemann
On Wed, Sep 03, 2008 at 01:40:44PM +0200, Joachim Ott wrote:
 2008/9/3 Ole Kliemann [EMAIL PROTECTED]
 
  On Wed, Sep 03, 2008 at 03:59:02AM +0200, Marco Trevisan (Treviño) wrote:
  ...
 
 
 I wonder what the date code of your Neo's are. Mine is 20080619, and I have
 GPS working ok (with tangoGPS in 2007.2) and with the SD-card in place.

20080617 is my date code. GPS is working for most people. I guess it's
an individual problem with my device.


pgpmwxvmrAfzz.pgp
Description: PGP signature
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support


Re: Alternate Keyboard(s) on 2008.8

2008-08-08 Thread Ole Kliemann
There is only one possible solution. There must be easy customizable
keyboard files so that everybody is able to use the keyboard he likes.
Besides there must be an option to switch between different keyboards.
It's a simple idea: one tool for one job. 

The predictive text with the right dictionary can be very powerful when
writing SMS. You don't really need to aim for the letters, just hit
somewhere close to them. 

Still the Qtopia keyboard like it comes with Om2008.8 now is pretty
flawed lacking punctation signs. You have to switch two layouts further
to find a comma or period. Despite the fact that there is a lot of space
left on the alphabet keyboard.

And certainly for everything except SMS and maybe sometimes writing
notes the layout alone is a disaster; not to mention the predictive
text.

As I understand, there has been a long discussion about why not using
the illume keyboard. I have not completely followed that discussion and
I do not claim to have an understanding for the problems of development
that may be connected to this issue.

But I'd like to stress at this point that I believe the customizability
of input methods - i.e. the possibility of individually communicating
with the device - is a kind of freedom that many people are seeking with
the FR.

Ole


pgpKupNw21yrF.pgp
Description: PGP signature
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support


Re: Buzzing sound

2008-08-05 Thread Ole Kliemann
On Tue, Aug 05, 2008 at 11:25:56AM +0100, Andy Green wrote:
 Somebody in the thread at some point said:
 | 2008/8/5 Joerg Reisenweber [EMAIL PROTECTED]:
 | Only thing you may try for now is changing GSM-provider, as it seems
 to be
 | very clear the issue is to be found on some GSM-networks, and not (or
 less)
 | on some others. Generally the 1800/1900 networks seem to be more
 likely to
 | cause this problem than the 850/900 networks. For Germany I got reports f
 | noise only for E+ network (and resellers)
 |
 | My experience on Blau (E+) is that I hear the caller excellently - but
 | the caller complains that buzzing is very bad.
 
 Do they say the buzzing is consistent, or it comes and goes?

For me using Simyo (E+) the far-end buzzing is consistent as long as the phone
lies still. It varies depending on:
- where you touch the phone
- in which orientation you hold it
- whether you move around with the phone

BTW: Near-end buzzing I think is dependent on alsamixer. At least I had
images with only far-end buzzing.


pgp4aTcc6w22w.pgp
Description: PGP signature
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support


Re: Buzzing sound

2008-08-05 Thread Ole Kliemann
On Tue, Aug 05, 2008 at 07:49:51PM +0800, Joerg Reisenweber wrote:
 Am Di  5. August 2008 schrieb Jeffrey Ratcliffe:
  2008/8/5 Andy Green [EMAIL PROTECTED]:
   Like Ole says when I started looking at it, by calling a landline in the
   same room and listening to its receiver lying on the desk, it varied
   tremendously and not in a repeatable way.  Eg, it appeared to vary by
   orientation of the phone, but when I traced the path backwards, the buzz
   did not return.
  
  OK. Confirming this - the buzzing seems to come and go in waves of
  varying frequency. Even without touching the phone, the buzzing just
  comes and goes.
 
 I noticed the buzz come and go in discrete steps. I guess that's basestation 
 sending PCF commands to mobile, to level up/down the TX-power.
 BS decides on this depending on signal-quality of MS as BS sees it.
 It would be *very* helpful to confirm this, by using some RF-meter (e.g. 
 microwave leakage tester?), and/or reading the battery current, while 
 observing the noise come and go-

I can only observe: I did this test some weeks ago at my home. The FR
has signaficantly better signal when held out of the window. 

When holding out of the window during a call, it takes a short moment
then buzzing disappears quite suddenly. Going back into the room again
after a moment the buzzing returns suddenly.

So it comes and goes in discrete steps and it lags behind the change of
position.

BTW: Not that I would know anything about these things. But would it be
possible to lower the TX-power of the FR to see how far down you can go
without loosing connection? 

I have active speakers in my room that catch GSM signals. I noticed
several times that the noise in the speakers when the phone is
registering is louder with the FR than with a Motorola V3x with the same
SIM.


pgpzcz4peRhUl.pgp
Description: PGP signature
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support


Re: Qtopia Questions/Bugs/Suggestions

2008-07-31 Thread Ole Kliemann
Using newest kernel through opkg upgrade and newest Qtopia snapshot[1]
some things are fixed.

The message read/unread count is now ok. The big `new message' symbol in
the homescreen now works and opens the new message.

Also resume when receiving SMS seems to work. 

But a new problem has appeared. When resuming after long suspend I only
get a white screen. It can sometimes be fixed by pressing something.
Maybe something that forces full redraw?

This problem was not when using the kernel that came with the Qtopia
image form 20080724.

[1] 
ftp://ftp.trolltech.com/qtopia/snapshots/qtopia-opensource-src-4.3.2-snapshot-20080731.tar.gz


pgpwBPmnj4ewp.pgp
Description: PGP signature
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support


Re: Qtopia Questions/Bugs/Suggestions

2008-07-30 Thread Ole Kliemann
On Tue, Jul 29, 2008 at 08:19:47AM -0700, Charles Hill wrote:
 
 I'm currently running Qtopia on my FreeRunner.
 Version: 4.3.2 snapshot 07221045 Submitted Date 2008/7/24
 
 1. Question: When going into the System Info on the phone it says Qtopia
 Version 4.3.3, built by lpotter@ on July 22.  Which is it, 4.3.2 or 4.3.3?
 
 2. Bug: Speed Dial has no visual feedback of selection.  Clicking icons on
 the home screen, Main Menu, and sub-menus gives feedback in the way of a
 colored highlight or enlarging icon.  When clicking anything in the Speed
 Dial, nothing happens until the program pops up.  The top item in my Speed
 Dial list always stays highlighted.
 
 3. Question: In Power Management, it is possible to set Suspend faster than
 Display Off or Dim.  Is it really supposed to allow that?
 
 4. Suggestion: When playing music, if you place a call, the music stops
 until the call is finished.  Cool.  However, it would be better (IMHO) if
 you PAUSED the music, so the song doesn't restart at the beginning when the
 call is done.
 
 5. Suggestion: When playing music, if you get a call, the music stops.  It
 would be slick if the music volume simply dropped to 10% or so while the
 phone was ringing -- both at once.  Then, if the person chose to ignore the
 call, the music volume ticks back up to where it was.  If they choose to
 answer the call, pause the music until the call is done.
 
 6. Bug: I have one MP3 that Media Player insists on playing in Chipmunk mode
 -- 2x speed.  It plays fine on my desktop.  Now that I look at it, it is the
 only MP3 I have encoded at 64 Kbps.  Hmmm
 
 7. Question: When playing music, after the screen dims/turns off due to
 Power Management settings, it undims/turns on when a song changes.  Is this
 the desired behavior?

If I may just quickly add:

I do not receive SMS when in suspend. FR does not wake up. But I do not
receive the SMS immediately when I wake up the phone. It sometimes takes
hours until I get it.

Calls wake up the device everytime I tried.

Ole


pgpTEbZQXJhWl.pgp
Description: PGP signature
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support


Re: Qtopia: customize keyboard, select input language

2008-07-28 Thread Ole Kliemann
On Mon, Jul 28, 2008 at 01:43:00PM +0200, arne anka wrote:
  Well, it can be done. Get the Qtopia source[1], and look into this file
 
  src/plugins/inputmethods/predictivekeyboard/predictivekeyboard.cpp
 
  At line 132 there is
 
  mKeyboard-addBoard(QStringList()  QWERTYUIOP  ASDFGHJKL   
  ZXCVBNM, KeyboardWidget::UpperCase);
  mKeyboard-addBoard(QStringList()  qwertyuiop  asdfghjkl   
  zxcvbnm, KeyboardWidget::LowerCase);
 
 if you found that already, it should be easy to implement reading a file  
 w/ keyboard definition instead and put the content in that QStringList.

Sure. I just have no clue of Qt-API. So I just left it like this for
now.

I'm more after GPRS right now anyway. ;)

Ole


pgpUUkUBmNKhi.pgp
Description: PGP signature
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support


Re: Keyboard not working on latest ASU

2008-07-23 Thread Ole Kliemann
On Tue, Jul 22, 2008 at 04:29:39AM +1000, Carsten Haitzler wrote:
 i'm in the middle of a full kbd rewrite... it's all functional now... with
 latest svn (rev151) for sure, but dictionary lookup is not working (havent 
 done
 that yet).

Was working well at one point. Could change the keyboards with menu and
my own layout was working. Thumbs up for the customizable .kbd files.
Especially that you can change the size of the keys. These are the
things I got an FR for. :)

But right now[1], I don't get a keyboard at all.

[1] 
http://buildhost.openmoko.org/daily/freerunner/200807/20080722/openmoko-qtopia-x11-image-om-gta02.jffs2
illume is rev152 in this image.

Ole


pgpKtXsfobAYM.pgp
Description: PGP signature
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support


Re: Keyboard not working on latest ASU

2008-07-23 Thread Ole Kliemann
On Wed, Jul 23, 2008 at 01:07:22PM +0200, Torfinn Ingolfsen wrote:
 Hello,
 
 On Wed, Jul 23, 2008 at 2:13 PM, Ole Kliemann
 [EMAIL PROTECTED] wrote:
  But right now[1], I don't get a keyboard at all.
 
  [1] 
  http://buildhost.openmoko.org/daily/freerunner/200807/20080722/openmoko-qtopia-x11-image-om-gta02.jffs2
 illume is rev152 in this image.
 
 I can confirm this - I just did an 'opkg upgrade -force-overwrite'
 even after I was warned. And no the keyboard never shows up (test with
 PIN code dialog, contacts application).
 Is there a way to roll back to a known working version?

I guess the problem is with illume. I think rev151 worked. I don't know
if there are still binaries (e.g. an ipkg) to find for this rev. You
could check out rev151 from svn and compile yourself, I guess. 

But probably this will be fixed pretty soon. It was working just
yesterday or so. 

Ole


pgpzp2NX1YJWQ.pgp
Description: PGP signature
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support


Re: Keyboard not working on latest ASU

2008-07-23 Thread Ole Kliemann
On Wed, Jul 23, 2008 at 10:28:08PM +1000, Carsten Haitzler wrote:
 On Wed, 23 Jul 2008 13:07:22 +0200 Torfinn Ingolfsen [EMAIL PROTECTED]
 babbled:
 
  Hello,
  
  On Wed, Jul 23, 2008 at 2:13 PM, Ole Kliemann
  [EMAIL PROTECTED] wrote:
   But right now[1], I don't get a keyboard at all.
  
   [1]
   http://buildhost.openmoko.org/daily/freerunner/200807/20080722/openmoko-qtopia-x11-image-om-gta02.jffs2
   illume is rev152 in this image.
  
  I can confirm this - I just did an 'opkg upgrade -force-overwrite'
  even after I was warned. And no the keyboard never shows up (test with
  PIN code dialog, contacts application).
  Is there a way to roll back to a known working version?
 
 and it will continue to be there/not there between svn versions. qtopia has 
 its
 own vkbd and illume has one - they conflict and right now i can only turn off
 the illume one in code. so depending what svnrev u get it may or may not be
 enabled or conflict etc. etc. - u'll have to wait for dust to settle.

I see. Sitting tight... :)


pgpRHLAohdjEp.pgp
Description: PGP signature
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support


Re: Keyboard not working on latest ASU

2008-07-23 Thread Ole Kliemann
On Wed, Jul 23, 2008 at 03:50:44PM +0200, Torfinn Ingolfsen wrote:
 Hi,
 
 On Wed, Jul 23, 2008 at 2:28 PM, The Rasterman Carsten Haitzler
 [EMAIL PROTECTED] wrote:
  and it will continue to be there/not there between svn versions. qtopia has 
  its
  own vkbd and illume has one - they conflict and right now i can only turn 
  off
  the illume one in code. so depending what svnrev u get it may or may not be
  enabled or conflict etc. etc. - u'll have to wait for dust to settle.
 
 In the future, could it be possible to have a configurable keyboard?
 - I install three keyboards I like (or all available keyboards)
 - I configure somewhere (a .conf file in /etc maybe?) which keyboard I
 prefer, this is the keyboard that appears whenever a keyboard i needed
 Additionally, all keyboards have a way to switch to another keyboard
 (menu?, extra key?) so that I can switch whenever I want, even in mid
 sentence.

Try the image I posted. You can change the keyboard via menu.

Look into /usr/lib/enlightenment/modules/illume/keyboards/

Check out the .kbd files. It's pretty easy to modify them/make your own.

Ole


pgpHMfupzEfx4.pgp
Description: PGP signature
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support


Re: Qtopia: customize keyboard, select input language

2008-07-22 Thread Ole Kliemann
On Mon, Jul 21, 2008 at 03:41:19PM +, Ole Kliemann wrote:
 I want English as
 language displayed, but German as input-language. I have chosen as
 language U.S. English but checked the `use for input' box for German.
 Still the predicative keyboard seems only to use English.

Workaround for this is:
cd /opt/Qtopia/etc/dict
mv en_US _en_US
ln -s de en_US

Ole


pgpf5cFwrbzw7.pgp
Description: PGP signature
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support


Re: Qtopia

2008-07-22 Thread Ole Kliemann
On Tue, Jul 22, 2008 at 10:15:32PM +0200, Thomas B. wrote:
 Alternatively, you can try to persuade U-Boot to tell the kernel to use
 ext3. I described how I did that here (didn't have time to put it in the
 wiki yet... 

There as a wiki entry on this already:
http://wiki.openmoko.org/wiki/Booting_from_SD#Add_uboot_boot_entry

Ole


pgp9GkLySBO0V.pgp
Description: PGP signature
___
support mailing list
support@lists.openmoko.org
https://lists.openmoko.org/mailman/listinfo/support