summaryrefslogtreecommitdiff
path: root/packages/MtpDocumentsProvider
AgeCommit message (Collapse)Author
2020-12-08Improve OWNERS coverage across frameworks/base/.Jeff Sharkey
As general background, OWNERS files expedite code reviews by helping code authors quickly find relevant reviewers, and they also ensure that stakeholders are involved in code changes in their areas. Some teams under frameworks/base/ have been using OWNERS files successfully for many years, and we're ready to expand them to cover more areas. Here's the historical coverage statistics for the last two years of changes before these new OWNERS changes land: -- 56% of changes are fully covered by OWNERS -- 17% of changes are partially covered by OWNERS -- 25% of changes have no OWNERS coverage Working closely with team leads, we've now identified clear OWNERS on a per-package basis, and we're using "include" directives whenever possible to to simplify future maintenance. With this extensive effort, we've now improved our coverage as follows: -- 98% of changes are fully covered by OWNERS -- 1% of changes are partially covered by OWNERS -- 1% of changes have no OWNERS coverage This specific change is automatically generated by a script that identifies relevant "include" directives. Bug: 174932174 Test: manual Exempt-From-Owner-Approval: refactoring with team leads buy-in Merged-In: I3480ddf2fe7ba3dfb922b459d4da01fa17a2c813 Change-Id: I3480ddf2fe7ba3dfb922b459d4da01fa17a2c813
2019-08-09Migrate MTP components into new project.Jeff Sharkey
Bug: 138999976 Test: manual Change-Id: I440fc37ff7b2be48b415989eb64b528a0c89b833
2019-07-31Merge "Import translations. DO NOT MERGE"Bill Yi
2019-07-30Import translations. DO NOT MERGEBill Yi
Change-Id: Ib6d57181c501602ba5caceaa59d71befe3dec58e Auto-generated-cl: translation import
2019-07-29Merge "Convert more of frameworks/base/packages to Android.bp" into ↵Colin Cross
stage-aosp-master am: ba9073a6a8 am: 97c07ce018 am: 7d089ac5ae am: aa98bac24b Change-Id: Iefbb6eeb03d46753bfc1c2ac4ca793788a4ed7fa
2019-07-24Convert more of frameworks/base/packages to Android.bpColin Cross
See build/soong/README.md for more information. Bug: 122332340 Test: m DynamicSystemInstallationService InputDevices MtpDocumentsProvider SimAppDialog Change-Id: I851b819030a1da6091f5d6125a228bb01a99011b
2019-05-08Import translations. DO NOT MERGEBill Yi
Change-Id: Ibcec31d3dfce3f9fd70666945143dab33ab6083d Auto-generated-cl: translation import
2019-04-07Import translations. DO NOT MERGEBill Yi
Change-Id: I84074fced4dbf54a5f0435e7ffbb8f9db1abf7cc Auto-generated-cl: translation import
2019-02-02Import translations. DO NOT MERGEBill Yi
Change-Id: Ide9284fa5807304d30659604190b6f1470b8d581 Auto-generated-cl: translation import
2018-12-18Migrate frameworks/base/packages/MtpDocumentsProvider/perf_tests to ↵KOUSHIK PANUGANTI
androidx.test See go/jetpack-test-android-migration Test: make checkbuild Change-Id: I17fddb7df14bfb362155bbbd7d177dfac07f8a1b
2018-12-10Merge "Use getCompressedSizeLong to get correct size for 2G file" am: ↵robinz1x
ee1720cffa am: d3ffd42b19 am: 886c64d1e3 Change-Id: I52375b4646d392fb4877a454667897ee43a62bce
2018-09-12Use getCompressedSizeLong to get correct size for 2G filerobinz1x
The MtpObjectInfo#getCompressedSize() returns the value in Java int (signed 32-bit integer), so when the MtpObject size is larger than 2^31-1, use getCompressedSize() will encounter the IllegalStateException error. Use getCompressedSizeLong() instead of getCompressedSize() can get the correct size. Test: manual - connect Android device to Android Automotive Test: manual - select MTP/File Transfer in android device Test: manual - copy a file which is bigger than 2GB from automotive to the android device. bug: 115451170 Change-Id: Idb3529b6d6e8588c59d18aad1eae9c46df2e6fe0 Signed-off-by: robinz1x <robinx.zhang@intel.com> Signed-off-by: Guobin Zhang <guobin.zhang@intel.com>
2018-08-28More robust MTP-to-MIME-type mappings.Jeff Sharkey
Recently in I830717428e72ac37c5ecd1f23d915aa878ef3744, we greatly improved the underlying file-extension-to-MIME-type mappings defined in libcore and used across the OS. Instead of maintaining divergent mappings here in MediaFile, this change delegates all file extension logic down to libcore, and standardizes all MediaScanner internals on using MIME types. To register new file types in the future: 1. Add the MIME-to-extension registration in libcore. 2. Add the MIME-to-MTP mapping here in MediaFile. This change also ensures that unknown MIME types are surfaced across MTP, using constants like FORMAT_UNDEFINED_AUDIO for audio/* until an explicit format is defined. We now surface WMA/WMV file formats, even if the device can't natively play them back, since we still want to offer the ability for users to copy them around, and the user may have a third-party app capable of playing them. Keeps @UnsupportedAppUsage intact for now. Bug: 111268862, 112162449 Test: atest frameworks/base/media/tests/MediaFrameworkTest/src/com/android/mediaframeworktest/unit/MediaFileTest.java Test: atest cts/tests/tests/provider/src/android/provider/cts/MediaStore* Change-Id: I2f6a5411bc215f776f00e0f9a4b7d825b10b377d
2018-04-10Merge "Exempt tests for hidden APIs." into pi-dev am: 0e675bd901Nicolas Geoffray
am: 03ba2d9241 Change-Id: I0e4517312cac9b37537eee55eafd811aff531ea8
2018-04-10Merge "Exempt tests for hidden APIs." into pi-devNicolas Geoffray
am: 0e675bd901 Change-Id: I012a1ce8483f5fdddf60cfd33ea4303d72455fca
2018-04-06Exempt tests for hidden APIs.Nicolas Geoffray
Bug: 64382372 Bug: 74963051 Test: m Change-Id: I5234dd6230f2bdd6ffccbf12b25a02d929d20161
2018-04-04Import translations. DO NOT MERGEBill Yi
Change-Id: I358b72be3d9f7eccf0225df4479eda9bd1d6ae1a Auto-generated-cl: translation import
2018-03-29Merge "Add MtpDocumentsProviderPerfTests to APCT metric" into pi-dev am: ↵jdesprez
208f0ea367 am: 98e30fc7ad Change-Id: Ic8a51f63b726b67ebd4dc379dcf40fea9c17045f
2018-03-29Merge "Add MtpDocumentsProviderPerfTests to APCT metric" into pi-devjdesprez
am: 208f0ea367 Change-Id: I6cc869b0c79b402f3fbf6d34a6783a8d72974ecf
2018-03-29Add MtpDocumentsProviderPerfTests to APCT metricjdesprez
Add it to the suite version of APCT metric instrumentation Test: build device-tests.zip Bug: 77280599 Change-Id: I3a00af2382f4905d84b500b6f5523456d211689f
2018-03-16Import translations. DO NOT MERGEBill Yi
Change-Id: Ic3704f50a3475bdd4deab3e2e9af0a440c5d98c6 Auto-generated-cl: translation import
2018-03-07Merge "Fix issue #72116995: Add permission guarding Service#startForeground" ↵Dianne Hackborn
into pi-dev am: 16268a69d6 Change-Id: I6ef5335e391eb9259ae0dfbf4f88032ad1d2bad4
2018-03-06Merge "Fix issue #72116995: Add permission guarding Service#startForeground" ↵Dianne Hackborn
into pi-dev
2018-03-06Import translations. DO NOT MERGEBill Yi
Change-Id: Id1012c9674dececce42d71b5e50023408faa3aac Auto-generated-cl: translation import
2018-03-05Fix issue #72116995: Add permission guarding Service#startForegroundDianne Hackborn
Now requires permission if targeting P. Note that this is a separate permission from the existing one that is required for instant apps to use foreground services. The reason for this is that their semantics are different (the instant apps permission is associated with an app op for control over what the app is allowed, while the regular app permission is just a normal permission that is always granted and only there for auditing of apps), and there are probably going to be cases where a developer will want to use a foreground service in the full version of their app but not as an instant app. Bug: 72116995 Test: atest CtsAppTestCases Change-Id: I883c9515c307ed8e39f0bf888c4045944c8183ac
2018-02-28frameworks/base: Set LOCAL_SDK_VERSION where possible.Anton Hansson
This change sets LOCAL_SDK_VERSION for all packages where this is possible without breaking the build, and LOCAL_PRIVATE_PLATFORM_APIS := true otherwise. Setting one of these two will be made required soon, and this is a change in preparation for that. Not setting LOCAL_SDK_VERSION makes the app implicitly depend on the bootclasspath, which is often not required. This change effectively makes depending on private apis opt-in rather than opt-out. Test: make relevant packages Bug: 73535841 Change-Id: I4233b9091d9066c4fa69f3d24aaf367ea500f760
2018-02-22Import translations. DO NOT MERGEBill Yi
Change-Id: I899af9662533764d6efb2186c1efe5bfbcb6807e Auto-generated-cl: translation import
2018-02-12Revert "Fix issue #72116995: Add permission guarding Service#startForeground"Ian Pedowitz
This reverts commit a9da85fde4675ed0b03557e448b1cc67f1d391fe. Reason for revert: b/73224471 Bug: 73224471 Bug: 72116995 Change-Id: I1485305f40d47fdb138cb1e484c329cf20892a6b
2018-02-07Fix issue #72116995: Add permission guarding Service#startForegroundDianne Hackborn
Now requires permission if targeting P. Note that this is a separate permission from the existing one that is required for instant apps to use foreground services. The reason for this is that their semantics are different (the instant apps permission is associated with an app op for control over what the app is allowed, while the regular app permission is just a normal permission that is always granted and only there for auditing of apps), and there are probably going to be cases where a developer will want to use a foreground service in the full version of their app but not as an instant app. Bug: 72116995 Test: atest CtsAppTestCases Change-Id: I95afb7185742b82c525e775ca20bb36015510b43
2018-01-25Revert "Fix issue #72116995: Add permission guarding Service#startForeground"Dianne Hackborn
This reverts commit 994b5ad737831854ac3ba119abba533adca774fc. Waiting for Chrome prebuilt. Test: NA Bug: 72116995 Change-Id: Ifcfea94ddefda27267640283038c9d0f933ea1d8
2018-01-24Fix issue #72116995: Add permission guarding Service#startForegroundDianne Hackborn
Now requires permission if targeting P. Note that this is a separate permission from the existing one that is required for instant apps to use foreground services. The reason for this is that their semantics are different (the instant apps permission is associated with an app op for control over what the app is allowed, while the regular app permission is just a normal permission that is always granted and only there for auditing of apps), and there are probably going to be cases where a developer will want to use a foreground service in the full version of their app but not as an instant app. Bug: 72116995 Test: atest CtsAppTestCases Change-Id: If5a79e7ed5ab9e0edc77410315eb4d2df8ac850b
2017-12-08Stop statically including legacy-android-testPaul Duffin
Statically including legacy-android-test leads to duplicate classes which causes build time problems (with Proguard) and runtime problems on older SDK versions. This change: * Stops statically including legacy-android-test. * Adds compile time dependencies on andoid.test.base, android.test.mock and android.test.runner where necessary. * Adds <uses-library android:name="android.test.runner"/> to any affected package to ensure that the classes that were included by legacy-android-test are still available at runtime. That also adds a dependency on android.test.base and android.test.mock. The following change descriptions were generated automatically and so may be a little repetitive. They are provided to give the reviewer enough information to check the comments match what has actually been changed and check the reasoning behind the changes. * apct-tests/perftests/core/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in CorePerfTests results in duplicate classes which leads to build time and compile time issues. Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because CorePerfTests's source depends on its classes and because of these changes they are no longer present on the compilation path. * core/tests/ConnectivityManagerTest/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because ConnectivityManagerTest's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in ConnectivityManagerTest results in duplicate classes which leads to build time and compile time issues. * core/tests/bandwidthtests/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because BandwidthTests's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in BandwidthTests results in duplicate classes which leads to build time and compile time issues. * core/tests/bluetoothtests/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because BluetoothTests's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in BluetoothTests results in duplicate classes which leads to build time and compile time issues. * core/tests/hosttests/test-apps/DownloadManagerTestApp/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in DownloadManagerTestApp results in duplicate classes which leads to build time and compile time issues. Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because DownloadManagerTestApp's source depends on its classes and because of these changes they are no longer present on the compilation path. * core/tests/hosttests/test-apps/ExternalSharedPerms/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in ExternalSharedPermsTestApp results in duplicate classes which leads to build time and compile time issues. * core/tests/hosttests/test-apps/ExternalSharedPermsBT/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in ExternalSharedPermsBTTestApp results in duplicate classes which leads to build time and compile time issues. * core/tests/hosttests/test-apps/ExternalSharedPermsDiffKey/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in ExternalSharedPermsDiffKeyTestApp results in duplicate classes which leads to build time and compile time issues. * core/tests/hosttests/test-apps/ExternalSharedPermsFL/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in ExternalSharedPermsFLTestApp results in duplicate classes which leads to build time and compile time issues. * core/tests/notificationtests/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because NotificationStressTests's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in NotificationStressTests results in duplicate classes which leads to build time and compile time issues. * keystore/tests/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in KeystoreTests results in duplicate classes which leads to build time and compile time issues. * media/mca/tests/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because CameraEffectsTests's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in CameraEffectsTests results in duplicate classes which leads to build time and compile time issues. * media/tests/MediaFrameworkTest/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because mediaframeworktest's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in mediaframeworktest results in duplicate classes which leads to build time and compile time issues. * nfc-extras/tests/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in NfcExtrasTests results in duplicate classes which leads to build time and compile time issues. * packages/CarrierDefaultApp/tests/unit/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because CarrierDefaultAppUnitTests's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in CarrierDefaultAppUnitTests results in duplicate classes which leads to build time and compile time issues. * packages/ExtServices/tests/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because ExtServicesUnitTests's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in ExtServicesUnitTests results in duplicate classes which leads to build time and compile time issues. * packages/MtpDocumentsProvider/tests/Android.mk Added 'android.test.base' and 'android.test.mock' to LOCAL_JAVA_LIBRARIES because MtpDocumentsProviderTests's source depends on their classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in MtpDocumentsProviderTests results in duplicate classes which leads to build time and compile time issues. * packages/SettingsLib/tests/integ/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because SettingsLibTests's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in SettingsLibTests results in duplicate classes which leads to build time and compile time issues. * packages/SettingsProvider/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in SettingsProvider results in duplicate classes which leads to build time and compile time issues. * packages/SettingsProvider/AndroidManifest.xml Add uses-library for android.test.runner because otherwise this change would change the set of files available to SettingsProvider at runtime. * packages/Shell/tests/Android.mk Added 'android.test.base' and 'android.test.mock' to LOCAL_JAVA_LIBRARIES because ShellTests's source depends on their classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in ShellTests results in duplicate classes which leads to build time and compile time issues. * packages/SystemUI/shared/tests/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in SystemUISharedLibTests results in duplicate classes which leads to build time and compile time issues. * packages/SystemUI/tests/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in SystemUITests results in duplicate classes which leads to build time and compile time issues. Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because SystemUITests's source depends on its classes and because of these changes they are no longer present on the compilation path. * packages/WAPPushManager/tests/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because WAPPushManagerTests's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in WAPPushManagerTests results in duplicate classes which leads to build time and compile time issues. * sax/tests/saxtests/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because FrameworksSaxTests's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in FrameworksSaxTests results in duplicate classes which leads to build time and compile time issues. * tests/BrowserPowerTest/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because BrowserPowerTests's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in BrowserPowerTests results in duplicate classes which leads to build time and compile time issues. * tests/CanvasCompare/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because CanvasCompare's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in CanvasCompare results in duplicate classes which leads to build time and compile time issues. * tests/CoreTests/android/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because CoreTests's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in CoreTests results in duplicate classes which leads to build time and compile time issues. * tests/DataIdleTest/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because DataIdleTest's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in DataIdleTest results in duplicate classes which leads to build time and compile time issues. * tests/FrameworkPerf/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because FrameworkPerf's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in FrameworkPerf results in duplicate classes which leads to build time and compile time issues. * tests/HierarchyViewerTest/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because HierarchyViewerTest's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in HierarchyViewerTest results in duplicate classes which leads to build time and compile time issues. * tests/ImfTest/tests/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because ImfTestTests's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in ImfTestTests results in duplicate classes which leads to build time and compile time issues. * tests/Internal/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in InternalTests results in duplicate classes which leads to build time and compile time issues. * tests/MemoryUsage/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because MemoryUsage's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in MemoryUsage results in duplicate classes which leads to build time and compile time issues. * tests/NetworkSecurityConfigTest/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because NetworkSecurityConfigTests's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in NetworkSecurityConfigTests results in duplicate classes which leads to build time and compile time issues. * tests/SoundTriggerTests/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in SoundTriggerTests results in duplicate classes which leads to build time and compile time issues. Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because SoundTriggerTests's source depends on its classes and because of these changes they are no longer present on the compilation path. * tests/SurfaceComposition/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in SurfaceComposition results in duplicate classes which leads to build time and compile time issues. Added 'android.test.runner.stubs' to LOCAL_JAVA_LIBRARIES because SurfaceComposition's source depends on its classes and because of these changes they are no longer present on the compilation path. * tests/TtsTests/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in TtsTests results in duplicate classes which leads to build time and compile time issues. Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because TtsTests's source depends on its classes and because of these changes they are no longer present on the compilation path. * tests/WindowAnimationJank/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in WindowAnimationJank results in duplicate classes which leads to build time and compile time issues. * tests/permission/Android.mk Added 'android.test.base' to LOCAL_JAVA_LIBRARIES because FrameworkPermissionTests's source depends on its classes and because of these changes they are no longer present on the compilation path. Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in FrameworkPermissionTests results in duplicate classes which leads to build time and compile time issues. * tests/testables/tests/Android.mk Removed legacy-android-test from LOCAL_STATIC_JAVA_LIBRARIES because statically including the classes in TestablesTests results in duplicate classes which leads to build time and compile time issues. Added 'android.test.base' and 'android.test.mock' to LOCAL_JAVA_LIBRARIES because TestablesTests's source depends on their classes and because of these changes they are no longer present on the compilation path. Bug: 30188076 Test: make checkbuild Change-Id: Iacfc939c97415314366ed61c5f3b7aa1a40f0ec9
2017-11-26Import translations. DO NOT MERGEBill Yi
Change-Id: Icc0a96079b89c483a584c5ead08850a3328caedb Auto-generated-cl: translation import
2017-11-06Import translations. DO NOT MERGEBill Yi
Change-Id: I8ff039bc24e3f1abf0e558d0cae23f3d8a581288 Auto-generated-cl: translation import Exempt-From-Owner-Approval: translation import
2017-09-18Import translations. DO NOT MERGEBill Yi
Change-Id: Ia04529216b73a44fcf223ec8d5dc065a634bb6f2 Auto-generated-cl: translation import Exempt-From-Owner-Approval: translation import
2017-09-13Import translations. DO NOT MERGEBill Yi
Change-Id: I376d1aed41553abfa1da395947ebf52cf7a6bb2e Auto-generated-cl: translation import Exempt-From-Owner-Approval: translation import
2017-09-06Merge "Import translations. DO NOT MERGE"TreeHugger Robot
2017-09-05Import translations. DO NOT MERGEBill Yi
Change-Id: I8af4273c3f1f52df4af6d193dce3f23e5fc0d5ca Auto-generated-cl: translation import Exempt-From-Owner-Approval: translation import
2017-08-31Update Several Instrumentation AndroidTest files with the correct runner.Simran Basi
Updated the instrumentation runner for: * FrameworksNotificationTests * SystemUITests * MtpDocumentsProvider Bug: 65176822 Test: atest FrameworksNotificationTests atest SystemUITests atest MtpDocumentsProvider Change-Id: I939d890715dce123bd77c5e352d0b01852ddd755
2017-08-25Import translations. DO NOT MERGEBill Yi
Change-Id: Ia94726b14e34c37472e0f1f66cdeab184e56c7bd Auto-generated-cl: translation import
2017-08-11Import translations. DO NOT MERGEBill Yi
Change-Id: I8055d18bddc232a9e589f2d3137b95624cf197d2 Auto-generated-cl: translation import Exempt-From-Owner-Approval: translation import
2017-08-02Add metadata support to MTP docs provider.Steve McKay
Remove convenience method from DocumentsProvider, clients to use MetadataReader directly. Concentrate mimetype checking in MetadataReader.isSupportedType. Update FileSystemProvider to use MetadataReader directly. Test: Updated mtp tests. Other functioanlity manually verified. Change-Id: Ie1e3d3092b53107f6c980c18b1451290dd2a9653
2017-06-22Import translations. DO NOT MERGEBill Yi
Change-Id: Ia12a71360c3933bd577aa5a3d1ed573b5772e251 Auto-generated-cl: translation import
2017-06-21Import translations. DO NOT MERGEBill Yi
Change-Id: Idfbbef02e0d91291816d3bbda4b16bff838f00d4 Auto-generated-cl: translation import
2017-05-18Fix NPE in MtpDocumentsProviderTestsDaichi Hirono
Previous patch ag/2250238 broke MtpDocumentsProviderTests since ServiceIntentSender's constructor refers the context argument which is null in the tests. The CL adds a test version of the constructor which does not use the context argument in it. Bug: 38363487 Test: MtpDocumentsProviderTests Change-Id: I68a1d8cb6997499e5069c33f70fd0f675aaad77c
2017-05-17Merge "Set notification channel to MTP notification." into oc-devTreeHugger Robot
2017-05-17Set notification channel to MTP notification.Daichi Hirono
Bug: 38252594 Test: Manually connect MTP device to Android Change-Id: Ib7ab12b2401d36dbb4cca2fd9c18cbd3505ed9ef
2017-05-16Merge "Don't specify screen orientation for ReceiverActivity." into oc-devJeff Sharkey
2017-05-12Don't specify screen orientation for ReceiverActivity.Daichi Hirono
From O, the framework does not allow to specify screen orientation for translucent acitivity. Bug: 38225950 Test: manually connect MTP device to Android Change-Id: I83c5063f6b85aff3c05906b9d66efbcde9693224
2017-05-01Fix doc flag for device having multiple storagesDaichi Hirono
Previously MtpDocumentsProvider#queryDocument returned FLAG_DIR_SUPPORTS_CREATE for device having multiple storages. This was wrong because if the device has multiple storages, MtpDocumentsProvider places the storages under the device document, thus users cannot create a document just under the device document. Bug: 35700994 Test: MtpDocumentsProviderTests Change-Id: Id73a34a2eaf4e10e23be3c2da7488036cea10000 (cherry picked from commit 66fcb4beae9605cd034c9437e510b21260d6f519)
generated by cgit v1.2.3 (git 2.25.1) at 2025-10-03 02:25:59 +0000