unav-devs team mailing list archive

Re: Fwd: Re: testing: issues i found

To: Joerg Berroth <joergberroth@xxxxxx>
From: Costales <costales@xxxxxxxxxx>
Date: Sun, 3 Apr 2016 21:51:34 +0200
Cc: unav-devs@xxxxxxxxxxxxxxxxxxx
In-reply-to: <57015CEC.2010508@web.de>
Sender: Costales <costales.marcos@xxxxxxxxx>
User-agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.5.1

Hi :)

> The bbox you are using might not be the best approach, see below. Ifwe can keep this box smaller we will have less pois to analyze.

Think that you're exiting in the oposite way in the city, you have tosee all possible speed cameras.


I'll play with a call in background, I'm not happy with it either.

I don't see this as that critical. More critical for example is memory

handling of oxide ;-) ...


In my test a few months ago playing to call a lot between QML and HTML was crazy.

Yes, it's not a freeze but the loss of GPS.


100% Device issue :( GPS or oxide, I don't know.

That's why I was thinking the process treatment on our side is not that perfect.


I assure you that is perfect now (improved this week). Honestly, uNav can't do more. It's is parsing already a few things of the GPS.

A hug :D