On Mon, Dec 14, 2015 at 8:50 PM, Dan Williams wrote:
>> The default setup uses a refresh time of 30s, which means that even
>> if the GPS
>> location updates are received at a higher frequency, the DBus
>> interface will
>> still expose at most one update every 30s.
>>
>> This patch includes a new
On Mon, Dec 14, 2015 at 8:57 PM, Dan Williams wrote:
>> Looks mostly good. Though I did get an error attempting to disable a
>> my QMI-based E397 while location gathering was active, which probably
>> wasn't caused by this specific patch:
>>
>> ModemManager[28430]: [1450122321.042945] [mm-broadb
On Mon, 2015-12-14 at 13:50 -0600, Dan Williams wrote:
> On Thu, 2015-12-10 at 23:49 +0100, Aleksander Morgado wrote:
> > The default setup uses a refresh time of 30s, which means that even
> > if the GPS
> > location updates are received at a higher frequency, the DBus
> > interface will
> > still
On Thu, 2015-12-10 at 23:49 +0100, Aleksander Morgado wrote:
> The default setup uses a refresh time of 30s, which means that even
> if the GPS
> location updates are received at a higher frequency, the DBus
> interface will
> still expose at most one update every 30s.
>
> This patch includes a ne
The default setup uses a refresh time of 30s, which means that even if the GPS
location updates are received at a higher frequency, the DBus interface will
still expose at most one update every 30s.
This patch includes a new "SetGpsRefreshTime()" method in the Location
interface, which takes a sin
