| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Bug: 17128331
Change-Id: I81a94510ef51b99916f314c0dd65852426a1fbeb
|
|
|
|
|
|
| |
b/16405976
Change-Id: Ic982ea2467d116585780c20c2fa7e974e50f8345
|
|
|
|
|
|
| |
b/16463499
Change-Id: I5dde8a2737d9345eb7f77edc64ab7286254a65e4
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Align the GPS framework with the GPS HAL
b/16374800
Remove localTime field from API
b/16241708
Update Property containers for measurements to use bit masks
b/16238371
Change-Id: Id4db16c3153d0020bf2edb5a67f59353662762d0
|
|
|
|
|
|
| |
b/16348349
Change-Id: I1f85283c86130b86389a1be7da49904658b0558c
|
|
|
|
| |
Change-Id: I7c4fff3526583475a5edf1f4ba8fede4e9419ead
|
|
|
|
| |
Change-Id: Ib4feca004b53fa89dcece4299974ab08913455a0
|
|\
| |
| |
| |
| |
| |
| | |
message."
* commit '812de6f6d75f71d1c2fd9cd319a78389c5adb703':
Fix typo in the exception message.
|
| |
| |
| |
| |
| | |
Change-Id: I5e8c089dfd406af40c4eb3aa76af13398c05b7e6
Signed-off-by: Masaki Muranaka <monaka@monami-software.com>
|
| |
| |
| |
| | |
Change-Id: I9531fba75bc1fee7d0e7c1dc179e3d05fb3e8a42
|
| |
| |
| |
| |
| |
| |
| |
| | |
correctly into the framework.
b/14118906
Change-Id: I4723a3b9cad99aacc70bd3b7b5b5e034aa6c033d
|
| |
| |
| |
| |
| |
| | |
- Bug: 13279850
Change-Id: I0fd1e60b2a56c45776963c29bbae6f176fdf1bea
|
| |
| |
| |
| |
| |
| | |
- Bug: 10696351
Change-Id: I4f1612ce10587728e71277587144fdcb59445b3f
|
| |
| |
| |
| | |
Change-Id: I5a84e8e93ac99b5ed0212b37bf66efa5e53864be
|
|/
|
|
| |
Change-Id: Ia1f99bd2c1105b0b0f70aa614f1f4a67b2840906
|
|
|
|
|
|
|
|
| |
- LocationManager.isProviderEnabled() no longer throws SecurityException:
the caller could already circumvent the permission check by calling
Secure.isLocationProviderEnabled()
Change-Id: I5abd04264299671ed35ce4594b5be46d86378767
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Split getStatus() into onGetSummary() and onGetEnabled()
- Call them on app's UI thread
- Allow runtime exceptions to propagate up
- Make a couple of more methods final to prevent subclasses from playing
around with the intent
- Remove explicit timing requirement from javadoc
- Mention that this will be restricted to system-image apps (will be
enforced by the actual settings code)
- b/10461474
Change-Id: Id22dd7a707c05de396ae4c5810e839ca734714c0
|
|
|
|
|
|
|
|
|
| |
- Currently redundant with PROVIDERS_CHANGED_ACTION, but that may
change in the future
- Part of fix for b/10409275
Change-Id: I12daaf20e6546fd9e9dc71c599967fa0ad95e27f
|
|
|
|
|
|
|
|
| |
- Add timing for getStatus() call to encourage implementors to be fast
- Affects b/10461474
Change-Id: I503cbae5cf27008c587a39ab4e60d8e09daedecc
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Fix additional getInt() path, restores the location settings screen
functionality.
- Should fix "unresolved link" build breakages in
git_klp-dev-plus-aosp-without-vendor, which is much more persnickety than
klp-dev for some reason.
- Add warning that we may add additional location modes in the future.
- Finish fix for b/10461763 and b/10461474
Change-Id: Id7155e3a0d7526a377d446018ef3bdb057bad3a6
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Escape < and > in javadoc
- Constructor does not take log tag
- Start intent rename
- Comments for Status.summary and enabled
- Bonus fixes:
- Start renaming STATUS_KEY to SUMMARY_KEY
- Send message back even if getting the status fails so we don't have
to wait for the fetch to time out
- Add comment about setting activity being invoked when disabled
- Partial fix for b/10461474
Change-Id: I025e7e0782c2873a4eda20ab4793bc6145daf8db
|
|
|
|
| |
Change-Id: I4ac0b864f55992242b6a3b0d8ffb328f23f6b645
|
|
|
|
|
|
| |
- Move UPDATE_INTENT to SettingInjectorSErvice
Change-Id: I9c8f8dc0878647a051cb852721b3436e9d55b391
|
|
|
|
|
|
|
| |
Document their purpose and permissions required in case
this is unhidden in a different code line.
Change-Id: I42f6f950157f488cf51b361e3411861ff98794e8
|
|\
| |
| |
| | |
This seems to be the standard usage, and there are rare reports of requestLocationUpdates giving NullPointerExceptions on the first call to requestLocationUpdates but not on subsequent calls (b/10207898)." into klp-dev
|
| |
| |
| |
| |
| |
| |
| |
| | |
This seems to be the standard usage, and there are rare reports of
requestLocationUpdates giving NullPointerExceptions on the first call
to requestLocationUpdates but not on subsequent calls (b/10207898).
Change-Id: If7a873fba5a2cd77b836ff3fda89105da20104ac
|
|/
|
|
|
|
|
|
| |
Helps to make sure the service doesn't throw a
SecurityException for not having the UPDATE_DEVICE_STATS
permission.
Change-Id: I9be0302f1378d2c4441e6b7d5ce472ed0d5fbd80
|
|\ |
|
| |
| |
| |
| |
| |
| | |
- Partial fix for b/10287745
Change-Id: Ie998ce0a7b350e4183fce5753bfac3eb51238ff4
|
| |
| |
| |
| | |
Change-Id: I0fb0e276d3a06322697bb5d46323779aca1f78c5
|
|/
|
|
| |
Change-Id: I50889599fdc5938a19b8bff4f11e64f44bcebdbf
|
|
|
|
| |
Change-Id: Ia3a57d869dfb3f067a1b95fa66d54f311ddcfdc3
|
|
|
|
|
|
|
| |
Move icon to right side of the screen and synchronize status with
AppOpsManager.OP_MONITOR_HIGH_POWER_LOCATION.
Change-Id: Iea2570501cb18be0489669fd4ea240dc63f9567a
|
|
|
|
|
|
|
| |
AppOps monitoring as long as the client as the appropriate
permission (UPDATE_DEVICE_STATS).
Change-Id: I7223a53bc1551e6498302a22eb310c8c5b5684b0
|
|
|
|
| |
Change-Id: I0fbbad0879b87ecc75a503bf7963356595bf4b96
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
One problem this turned up is, because FastPrintWriter does
its own buffering, a lot of code that used to use PrintWriter
would fail -- if it pointed to a StringWriter, there was no
buffering, so it could just immediately get the result. Now
you need to first flush the FastPrintWriter.
Also added some new constructors to specify the size of buffer
that FastPrintWriter should use.
Change-Id: If48cd28d7be0b6b3278bbb69a8357e6ce88cf54a
|
|
|
|
| |
Change-Id: Ic7983418d9577343817d5a80ebb0847804d2a1b2
|
|\
| |
| |
| |
| |
| |
| | |
"Android U: Making Apps Location-Aware" into jb-mr1.1-docs
* commit '39069b6e82fa848608d56b4efc8f28785816fe27':
Android U: Making Apps Location-Aware
|
| |\
| | |
| | |
| | |
| | |
| | |
| | | |
Apps Location-Aware" into jb-mr1.1-docs
* commit 'efb3726c226001149c92d48fa50da7031c231490':
Android U: Making Apps Location-Aware
|
| | |
| | |
| | |
| | | |
Change-Id: I8f44c6ca6d797ceb8ada5b2c723a8cca0081cf0a
|
| | |
| | |
| | |
| | |
| | |
| | | |
Add support for doing geofencing in hardware.
Change-Id: I6d5015190e8d84e1f4beb1010ed977a71c1622d0
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
LocationManagerService now annotates incoming Location objects that
have come from mock location providers. The new isFromMockProvider()
method can be called on any Location to determine whether the
provider that supplied the Location was a mock location provider.
Bug: 6813235
Change-Id: Ib5140e93ea427f2e0b0036151047f87a02b4d23a
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Initial implementation, tracking use of the vibrator, GPS,
and location reports.
Also includes an update to battery stats to also keep track of
vibrator usage (since I had to be in the vibrator code anyway
to instrument it).
The service itself is only half-done. Currently no API to
retrieve the data (which once there will allow us to show you
which apps are currently causing the GPS to run and who has
recently accessed your location), it doesn't persist its data
like it should, and no way to tell it to reject app requests
for various operations.
But hey, it's a start!
Change-Id: I05b8d76cc4a4f7f37bc758c1701f51f9e0550e15
|
| | |
| | |
| | |
| | | |
This reverts commit 578081f9da7ddb056b9b98524c639acd9194ecb6.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
Move location provider lib to frameworks/ex so it can be re-used in
GmsCore.
This is the frameworks/base part of the change (1).
Change-Id: Ifc31a6809876e9c9afb6ed841b66cf06de7e8964
|
|\ \
| |/
| |
| |
| |
| |
| | |
ranges" into jb-mr1.1-dev
* commit '4b77660b38cfff2ffb67c15db4c9e20adaac41d7':
clarify Geofence.createCircle() param ranges
|
| |
| |
| |
| |
| |
| |
| |
| | |
This commit adds the valid ranges to the latitude/longitude
parameters in Geofence.createCircle()'s javadoc.
Bug: 7172696
Change-Id: Iff6e3c3723d3fd9b6393bbc827ec5755c0d034af
|
|\ \
| |/
|/|
| |
| | |
* commit '768d9e1a72ceee7d4a5f608776b87b62d6ce4a04':
Correct executable bit for source files
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Many media files and source code files were marked as executable in Git.
Remove those.
Also a shell script and python script were not marked as executable.
Change-Id: Ieb51bafb46c895a21d2e83696f5a901ba752b2c5
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The Settings.Secure value locationPackagePrefixBlacklist and
locationPackagePrefixWhitelist contains comma seperated package-name
prefixes.
Location & geo-fence updates are silently dropped if the receiving
package name has a prefix on the blacklist. Status updates are
not affected. All other API's work as before.
A content observer is used so run-time updates to the blacklist
apply immediately. There is both a blacklist and a whitelist.
The blacklist applies first, and then exemptions are allowed
from the whitelist. In other words, if your package name prefix
matches both the black AND white list, then it is allowed.
Change-Id: I4ea2ad56fa6bd75d32151bc250ac25c26a5777c4
|