Details

    • Type: New Feature
    • Status: Closed
    • Priority: High
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: Release 7.1.0
    • Component/s: Android
    • Labels:
      None
    • Story Points:
      21
    • Sprint:
      2017 Sprint 14 SDK, 2018 Sprint 04 SDK

      Description

      As described in this article, the current implemented solution for Ti.GeoLocation with LocationManager is not recommended:
      http://developer.android.com/reference/android/location/package-summary.html

      Instead there is a FusedLocationProviderApi, part of Google Location Services API / Google Play services:
      https://developers.google.com/android/reference/com/google/android/gms/location/FusedLocationProviderApi
      An Example usage: http://javapapers.com/android/android-location-fused-provider/

      I've been using a closed-sourced 3rd party Module for quite some time now, and the update of Fused Location is clearly much faster, identical to Google Maps App location updates. Ideally this feature should be part of Titanium's Geolocation for Android. On another note, using that closed-sourced 3rd party module, creates issues now with Ti 5.2.0.GA, as indicated in this ticket: https://jira.appcelerator.org/browse/TIMOB-20377

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                gmathews Gary Mathews
                Reporter:
                underlabs Joseph Sachs
                Reviewer:
                Joshua Quick
                Tester:
                Lokesh Choudhary
              • Watchers:
                35 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Backbone Issue Sync

                  • Backbone Issue Sync is enabled for your project, but we do not have any synchronization info for this issue.

                    Git Source Code