Just wanted to close the loop on this thread:
This issue is being resolved in Android version 4.1 Jelly Bean and above
with a new CtsVerifier CTS test that will cause a device to fail the test
if it exhibits the behavior discussed above. So, for Android devices Jelly
Bean and above, this issue
StarTrax,
Interesting, you're right, looks like something funky happened with the
embedded URLs for the links in my first post. There also seemed to be an
issue with my first post getting stuck in the moderator queue (so sorry for
the double post), not sure if this is related. If you use the l
OK can follow links. Something quirky in the embedded URL.
On Friday, April 6, 2012 8:52:50 AM UTC+10, StarTraX wrote:
>
>
>
> On Friday, April 6, 2012 8:47:03 AM UTC+10, StarTraX wrote:
>>
>> Hey Sean,
>> Thanks for your post. Seems like there is some intelligence out there
>> after all!
>> I t
On Friday, April 6, 2012 8:47:03 AM UTC+10, StarTraX wrote:
>
> Hey Sean,
> Thanks for your post. Seems like there is some intelligence out there
> after all!
> I tried to follow your links but hit an Office Outlook web access login
> page, so couldn't progress. Is that me or is there a way th
Hey Sean,
Thanks for your post. Seems like there is some intelligence out there after
all!
I tried to follow your links but hit an Office Outlook web access login
page, so couldn't progress. Is that me or is there a way through?
When you refer to "the GPS provider", I wonder what component you
Hi all,
I've been working with the Android platform code lately, and had a chance
to look at this issue of the GPS provider ignoring the minTime parameter on
a number of devices more in depth. The GPS provider has two built-in
scheduling modes, native and platform, that are designed to follow t
Hi all,
I've been working with the Android platform code lately, and had a chance
to look at this issue of the GPS provider ignoring the minTime parameter on
a number of devices more in depth. The GPS provider has two built-in
scheduling modes, native and platform, that are designed to follow t
On Mon, Mar 19, 2012 at 8:28 PM, StarTraX wrote:
> I'm really fed up reading about the min time and min distance being "a
> hint".
Minimum time is a hint. Minimum distance is honored as a filter.
If there's a complex interaction between our parameters and the
> resulting effect, why isn't it do
I'm really fed up reading about the min time and min distance being "a
hint". If there's a complex interaction between our parameters and the
resulting effect, why isn't it documented? Just how the heck does it work?
I'm using the NMEA listener and want to have direct but high level control
over
On Wed, Feb 15, 2012 at 2:51 PM, Kristopher Micinski
wrote:
>> Actually, I got it from the docs, where they added this somewhere
>> along the line to requestLocationUpdates():
>>
>> "This field is only used as a hint to conserve power, and actual time
>> between location updates may be greater or
On Wed, Feb 15, 2012 at 2:46 PM, Mark Murphy wrote:
> On Wed, Feb 15, 2012 at 2:39 PM, Kristopher Micinski
> wrote:
>> I suspected this, but I didn't look at LocationManager's implementation :-(
>
> Actually, I got it from the docs, where they added this somewhere
> along the line to requestLocat
On Wed, Feb 15, 2012 at 2:39 PM, Kristopher Micinski
wrote:
> I suspected this, but I didn't look at LocationManager's implementation :-(
Actually, I got it from the docs, where they added this somewhere
along the line to requestLocationUpdates():
"This field is only used as a hint to conserve p
On Wed, Feb 15, 2012 at 2:37 PM, Mark Murphy wrote:
> On Wed, Feb 15, 2012 at 2:32 PM, Kristopher Micinski
> wrote:
>> The interval is not exact
>
> Moreover, the interval can be completely ignored. The minimum distance
> is a filter; the minimum time is a hint.
>
I suspected this, but I didn't
On Wed, Feb 15, 2012 at 2:32 PM, Kristopher Micinski
wrote:
> The interval is not exact
Moreover, the interval can be completely ignored. The minimum distance
is a filter; the minimum time is a hint.
--
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://com
The interval is not exact: if they come too quickly then you can throw
the unwanted ones away. Are they coming too late?
kris
On Wed, Feb 15, 2012 at 2:25 AM, santhosh b wrote:
> Hi,
>
> I am using below code to send location updates for every 2 min
> interval or 100 meters displacement. Thi
On Wed, Feb 15, 2012 at 1:25 AM, santhosh b wrote:
> This is working fine in Droid2
> Motorola device but when it comes to Google Nexus S
> not working as expected
>
What is it doing that is not "as expected"?
--
Hi,
I am using below code to send location updates for every 2 min
interval or 100 meters displacement. This is working fine in Droid2
Motorola device but when it comes to Google Nexus S
not working as expected
Here is the code snippet:
LocationManager locationManager = (LocationManager)
ge
17 matches
Mail list logo
