This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig3B22452A1FCEA8A3E405B137
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable

arne anka schrieb:
quoted text
> there seems to be no use of the workarounds/fixes discussed earlier -- =
=20
quoted text
> does anybody use the ubx-tool or whatever was discussed to feed =20
> informations to the u-blox on startup, thus significantly decreasing tt=
ff?
quoted text
>=20
> http://docs.openmoko.org/trac/browser/developers/alphaone/u-blox
>=20
> there were some pretty promising reports for those attempts (can't find=
 =20
quoted text
> them right now) -- and standing hours on a meadow in the faint hope of =
a =20
quoted text
> fix does not really sound appealing to me ...

Feeding assist data to compensate bad hardware based reception is no=20
real solution, since there are some FRs, which seem not to have any=20
problems to get a fast fix at all. The basic reception has to be better=20
and I cannot rely on fresh assist data at any time I need a fix!

It's a point of qualitiy management on the hardware producers side which =

has to get solved. I'm not willing to disassemble the new hardware at my =

own risk (warranty pp.). I know that I have bought an 'incomplete'=20
smarty regarding the OS and software. That was fine with me, but FIC=20
(as experienced hardware manufacturer) should do basic soldering jobs=20
successful on their products (If this gets verified to be the real=20
problem of this issue, of course).

My only question is: Which time I have left to engage a warranty=20
procedure? I'll ask Trisoft this week.


Greets


--=20

BlueStar88
________________________________________________________
PGPID: 0x36150C86
PGPFP: E9AE 667C 4A2E 3F46 9B69 9BB2 FC63 8933 3615 0C86


--------------enig3B22452A1FCEA8A3E405B137
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIejfh/GOJMzYVDIYRA68qAJoD5wai2qAWlLzfXECeKrVF1RGPsgCgwJl5
PH6Pxz71aQVWF5WT+9aQF6M=
=2+8L
-----END PGP SIGNATURE-----

--------------enig3B22452A1FCEA8A3E405B137--