touch-packages team mailing list archive

[Thomas Voß <1507474@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

The location infrastructure should offer a way for applications to setup
and maintain geo-fences (see [1]).

As usual, the respective functionality should be guarded by app confinement and require the user to approve the
respective transaction via our trust infrastructure. In addition, the location infrastructure should be clever in filtering
out requests that would enable an app to escape its lifecycle boundaries.

For that, the following changes would be required throughout the stack:

[1.] Geo-fencing capabilities of h/w should be exposed via the platform-
api HW interfaces: See
http://androidxref.com/5.1.1_r6/xref/hardware/libhardware/include/hardware/gps.h#1014

[2.] The location-service should expose geo-fencing capabilities on the
location::Service::Session objects.

[3.] The platform-api should expose an app-facing itf modelling geo-
fencing functionality.

[4.] qtubuntu-sensors should provide an implementation of
http://doc.qt.io/qt-5/qgeoareamonitorsource.html

** Affects: location-service (Ubuntu)
     Importance: Medium
         Status: Confirmed

** Affects: platform-api (Ubuntu)
     Importance: Medium
         Status: Confirmed

** Affects: qtubuntu-sensors (Ubuntu)
     Importance: Medium
         Status: Confirmed

** Description changed:

  The location infrastructure should offer a way for applications to setup
  and maintain geo-fences (see [1]).
  
- As usual, the respective functionality should be guarded by app confinement and require the user to approve the 
- respective transaction via our trust infrastructure. In addition, the location infrastructure should be clever in filtering 
+ As usual, the respective functionality should be guarded by app confinement and require the user to approve the
+ respective transaction via our trust infrastructure. In addition, the location infrastructure should be clever in filtering
  out requests that would enable an app to escape its lifecycle boundaries.
  
  For that, the following changes would be required throughout the stack:
  
  [1.] Geo-fencing capabilities of h/w should be exposed via the platform-
  api HW interfaces: See
  http://androidxref.com/5.1.1_r6/xref/hardware/libhardware/include/hardware/gps.h#1014
  
  [2.] The location-service should expose geo-fencing capabilities on the
  location::Service::Session objects.
  
- [2.] The platform-api should expose an app-facing itf modelling geo-
+ [3.] The platform-api should expose an app-facing itf modelling geo-
  fencing functionality.
  
  [4.] qtubuntu-sensors should provide an implementation of
  http://doc.qt.io/qt-5/qgeoareamonitorsource.html

** Also affects: platform-api (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: platform-api (Ubuntu)
       Status: New => Confirmed

** Changed in: platform-api (Ubuntu)
   Importance: Undecided => Medium

** Also affects: qtubuntu-sensors (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: qtubuntu-sensors (Ubuntu)
       Status: New => Confirmed

** Changed in: qtubuntu-sensors (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to location-service in
Ubuntu.
https://bugs.launchpad.net/bugs/1507474

Title:
  Provide geo-fencing functionality

Status in location-service package in Ubuntu:
  Confirmed
Status in platform-api package in Ubuntu:
  Confirmed
Status in qtubuntu-sensors package in Ubuntu:
  Confirmed

Bug description:
  The location infrastructure should offer a way for applications to
  setup and maintain geo-fences (see [1]).

  As usual, the respective functionality should be guarded by app confinement and require the user to approve the
  respective transaction via our trust infrastructure. In addition, the location infrastructure should be clever in filtering
  out requests that would enable an app to escape its lifecycle boundaries.

  For that, the following changes would be required throughout the
  stack:

  [1.] Geo-fencing capabilities of h/w should be exposed via the
  platform-api HW interfaces: See
  http://androidxref.com/5.1.1_r6/xref/hardware/libhardware/include/hardware/gps.h#1014

  [2.] The location-service should expose geo-fencing capabilities on
  the location::Service::Session objects.

  [3.] The platform-api should expose an app-facing itf modelling geo-
  fencing functionality.

  [4.] qtubuntu-sensors should provide an implementation of
  http://doc.qt.io/qt-5/qgeoareamonitorsource.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1507474/+subscriptions