| ffc42b0b7be29ee4118e0515d5ab024927bcb8ca |
|
29-Jul-2015 |
Lorenzo Colitti <lorenzo@google.com> |
Stop supporting legacy ConnectivityManager routing methods in M.
The methods startUsingNetworkFeature, stopUsingNetworkFeature and
requestRouteToHost were @removed in all the M preview builds, but
internal and external developers have noted that this imposes
additional burden for applications that need to work across
multiple platform versions because it causes compile-time errors.
We switched from @removed back to @deprecated to avoid these
problems. In order to effectively deprecate these methods, which
are error-prone and insecure, make them throw
UnsupportedOperationException if the app's target SDK is M or
above.
Because there are still one or two places in system code that use
these APIs, exempt Process.SYSTEM_UID and the OMA-DM client from
the check for now.
Bug: 22728205
Change-Id: I790bd32f3aa8067cbb625962a209bb9232f4b58c
/frameworks/base/core/java/android/app/SystemServiceRegistry.java
|
| 47abda576e06612b8af7b80504fafdfc076aff2d |
|
17-Jul-2015 |
Ricardo Garcia <rago@google.com> |
Fix for MidiManager bug
Returning null if MidiManager service can't be created instead
of crashing with NPE.
bug: 22087661
Change-Id: Ia27835ea1197af2db04c3e7f1d2e7c9f32fddbd0
/frameworks/base/core/java/android/app/SystemServiceRegistry.java
|
| e0a6ca64fac5bd4f10139321604031816e90adb4 |
|
04-Jun-2015 |
Mike Lockwood <lockwood@google.com> |
MidiManager: proxy all requests to open devices through MidiService
Previously when a MidiManager client opened a virtual or Bluetooth device,
the client bound directly to the virtual device's MidiDeviceService
or BluetoothMidiDevice's IMidiDeviceServer for the given BluetoothDevice.
Only USB devices were opened in MidiService.
Now opening any type of MIDI device is done via IMidiManager.openDevice() or
IMidiManager.openBluetoothDevice(). MidiService tracks all connnections between
clients and devices.
Services that implement virtual devices must now require android.permission.BIND_MIDI_DEVICE_SERVICE
so only MidiService can bind to these services.
Bug: 21044677
Change-Id: I7172f7b1e0cbfe4a2a87dff376c32dc9b41aa563
/frameworks/base/core/java/android/app/SystemServiceRegistry.java
|
| e3383cc4539921756232ae4f3f54e99b95fb20cc |
|
08-May-2015 |
Paul McLean <pmclean@google.com> |
Changes as per API council review.
Bug: 20887665
Change-Id: I1da7a2c69d8cf20682c767294b1647beef33f90c
/frameworks/base/core/java/android/app/SystemServiceRegistry.java
|
| 6711f3b34c2ad9c622f56a08b81e313795fe7647 |
|
07-May-2015 |
Adam Powell <adamp@google.com> |
Move PhoneWindow and friends back into internal package
PhoneWindow, PhoneLayoutInflater and PhoneFallbackEventHandler decided
to @hide out over in the android.view package after the policy jar was
disbanded. Give them a more appropriate home over in framework that
doesn't imply that they should be accessed from other internal layers
of abstraction.
Bug 19606548
Change-Id: Id07b791d178fa447010b49b24726b52208838e88
/frameworks/base/core/java/android/app/SystemServiceRegistry.java
|
| 16a16899505ec0a9ede5b76650bfb8817b3227c7 |
|
16-Apr-2015 |
Svet Ganov <svetoslavganov@google.com> |
Add OP_READ_PHONE_STATE app op - framework
The READ_PHONE_STATE permission protects PII information and
is in the Phone group. This change is adding the corrseponding
app op for gating access to the API guarded by READ_POHNE state
which will be used instead as an access control for legacy apps.
Change-Id: I2ff895a5a0e529f26ec0ad706266a30d829268ba
/frameworks/base/core/java/android/app/SystemServiceRegistry.java
|
| 9a1c9b67c4b2426884deb60c1ff84130ab47333c |
|
25-Feb-2015 |
Jonathan Basseri <misterikkit@google.com> |
Adding Carrier Config API.
UICC privileged carrier apps will extend CarrierConfigService to provide
carrier-specific configuration. Apps/services will use
CarrierConfigManager to read the current configuration.
CarrierConfigManager also defines the set of configuration variables and
their default values.
Bug: b/19483786
Change-Id: I027211b43276afd6fe893ae50048c52f2aed5cf5
/frameworks/base/core/java/android/app/SystemServiceRegistry.java
|
| a33be211e768746745a0deeba71f8c6b65e72442 |
|
20-Feb-2015 |
Paul McLean <pmclean@google.com> |
Audio Devices Enumeration/Notification API
Change-Id: I4eecfa43e4fecfe309ddd805ed193d078b10d5e6
/frameworks/base/core/java/android/app/SystemServiceRegistry.java
|
| ebbf205bc6e8292f74d8fc4652c70274a445f907 |
|
01-Apr-2015 |
Jim Miller <jaggies@google.com> |
Prepare to make Fingerprint API public.
- move fingerprint support files into hardware area
- move jni into services/core
Change-Id: I48a8e43d6d328fb66d79919c255e4c44e984b4d1
/frameworks/base/core/java/android/app/SystemServiceRegistry.java
|
| 4887789e44cdb16b042a35e8ec03983213e88ac6 |
|
18-Mar-2015 |
Jeff Sharkey <jsharkey@android.com> |
Progress towards dynamic storage support.
Storage devices are no longer hard-coded, and instead bubble up from
whatever Disk and VolumeBase that vold uncovered, turning into
sibling Java objects in MountService. We now treat vold events as
the source-of-truth for state, and synchronize our state by asking
vold to "reset" whenever we reconnect.
We've now moved to a model where all storage devices are mounted in
the root mount namespace (user boundaries protected with GIDs), so
we no longer need app-to-vold path translation. This also means that
zygote only needs to bind mount the user-specific /mnt/user/n/ path
onto /storage/self/ to make legacy paths like /sdcard work. This
grealy simplifies a lot of system code.
Many parts of the platform depend on a primary storage device always
being present, so we hack together a stub StorageVolume when vold
doesn't have a volume ready yet.
StorageVolume isn't really a volume anymore; it's the user-specific
view onto a volume, so MountService now filters and builds them
based on the calling user. StorageVolume is now immutable, making
it easier to reason about.
Environment now builds all of its paths dynamically based on active
volumes. Adds utility methods to turn int types and flags into
user-readable strings for debugging purposes.
Remove UMS sharing support for now, since no current devices support
it; MTP is the recommended solution going forward because it offers
better multi-user support.
Simplify unmount logic, since vold will now gladly trigger EJECTING
broadcast and kill stubborn processes.
Bug: 19993667
Change-Id: I9842280e61974c91bae15d764e386969aedcd338
/frameworks/base/core/java/android/app/SystemServiceRegistry.java
|
| 9c5dfa5c79fff17f96bf977b86c0c9ceb8c3cf9b |
|
23-Feb-2015 |
Zoltan Szatmary-Ban <szatmz@google.com> |
Data Usage public API
Added new API consisting of android.app.usage.NetworkUsageManager and
android.app.usage.NetworkUsageStats. Through them data usage on a
network interface can be programmatically queried. Both summary and
details are available.
Bug: 19208876
Change-Id: I0e0c4b37ae23ad1e589d4b0c955b93f28ba4333e
/frameworks/base/core/java/android/app/SystemServiceRegistry.java
|
| 2035ac85f61b0e7fa384d52fcfa99766424c122c |
|
06-Mar-2015 |
Eric Laurent <elaurent@google.com> |
broadcast radio API
Initial implementation of system APIs for broadcast
radio framework. Added manager and interfaces to control
a broadcast radio function exposed by the radio HAL.
- RadioManager: contains data structures and definitions as well as
top level API for feature discovery and tuner interface instantiation.
- RadioTuner: interface to control a broadcast radio tuner.
- RadioModule: framework component implementing the RadioTuner interface
and controlling a HW radio module via the radio HAL.
- RadioMetadata: representation of radio meta data (Station name, PTY,
song title, artwork, etc...) communicated by the framework to the client.
Change-Id: Iee42a185c694503e25f0b2dcfa417d88f5e9549b
/frameworks/base/core/java/android/app/SystemServiceRegistry.java
|
| 6e53931f49f49245deef8622eb8e7dc6ccf04536 |
|
25-Feb-2015 |
Jeff Brown <jeffbrown@google.com> |
Add Context.getSystemService(Class<?>).
Added an overload of getSystemService() that takes a class instead of a
service name to eliminate the extra cast and provide more type safety.
Cleaned up docs.
Removed the default constructor of BatteryManager which should not have
existed.
Change-Id: I9da46b20641fc83ecd3342560e5b94cb721f289c
/frameworks/base/core/java/android/app/SystemServiceRegistry.java
|