The framework Preference APIs are being deprecated, so removing the
samples will help avoid confusion.
Bug: b/119602280
Test: n/a
Change-Id: Ib3a2c38b8fbb0f1afc9ef6a35963def46ee931f7
Otherwise SDK build will fail because this target puts artifacts to
privileged app dir, which is not expected for samples in the SDK
build.
You can still build MultiClientInputMethod on command line by
explicitly specifying this in the build target.
Bug: 115784148
Test: locally verified as follows:
lunch sdk_phone_armv7-userdebug
make -j PRODUCT-sdk_phone_armv7-sdk
Change-Id: I09282fa39d13f8078881a3b215cad7d3c0e81486
This CL adds a sample multi-client IME. Ahthough there are still many
limitations and missing features in this sample IME, this CL
demonstrates how a multi-client IME can be implemented.
Fix: 115784148
Test: prebuilts/checkstyle/checkstyle.py -f \
development/samples/MultiClientInputMethod/
Test: Manually verified as follows:
1. make -j MultiClientInputMethod
2. adb install -r $OUT/system/priv-app/MultiClientInputMethod/MultiClientInputMethod.apk
3. adb root
4. adb shell setprop persist.debug.multi_client_ime \
com.example.android.multiclientinputmethod/.MultiClientInputMethod
5. adb reboot
6. Try multiple text input scenario
Change-Id: Ide43e16448fa00355a2c08bc45ae94d98553da50
- Added support for multiple launcher activity instances.
- Launcher now shows default wallpaper as background.
- The activity now expands behind system decor windows.
- App drawer can be invoked by clicking on FAB.
- Apps can be pinned on the screen.
- Wallpaper setting flow can be started from launcher.
- UI is optimized for large and xlarge screens.
- Launching a new instance is now optional.
- Other minor UI tweaks.
Bug: 116684201
Bug: 112452592
Bug: 112451761
Test: Manual
Change-Id: I52b5efa4362eab7fcaa5d23923329b68b1783847
For a cononical sample of a media player, see the Universal Music Player:
https://github.com/googlesamples/android-UniversalMusicPlayer
Bug: 33676939
Test: Verified projects compile when code removed.
Change-Id: I56e09ccf85647296c29da9a06b03b0fae98d50e6
Add alphabetic shortcuts to the menu in ActionBarUsage. This mirrors
what is already present in a similar support lib demo.
Bug: 31045453
Test: run com.example.android.apis.app.ActionBarUsage on a device
with keyboard shortcuts enabled (such as Chromebook). Action menu
items should display keyboard shortcuts.
Change-Id: I9e6b04df8e2a6cbc728cb60b3706d054521da7cb
In particular, we have an example of a foreground-service PendingIntent
triggered by a 15-second delayed alarm following a button click. This
is enough time to exercise use cases like swiping the app out of recents
before the alarm fires, therefore entering the "starting a fg service
when the app is not in a fg state" flows.
Bug: 73559697
Test: this is it
Change-Id: If57908ab852c7a0bfab7bb1da8eda0a47493fc6b
Bug: 72696928
Test: Install and open ApiDemos > App > Activity > Max Aspect Ratio > 1:1 / 16:9 / Any
Change-Id: Ie76c8c4babd6b4c281eec8ff977a0c02a868ee0e
ApiDemos has been using private APIs from telephony-common to
demonstrate the Mms feature. However, this is causing link-type check
warning because ApiDemos itself is built with SDK (LOCAL_SDK_VERSION is
set) but telephony-common isn't. As we are working on to promote the
warnings into errors, this warnings must be fixed.
Fixing the warning by copying the PDU classes from telephony-common, so
that there is no need to link to the library. Also the package name for
the copied classes are all changed in order to prevent the collision
with the same classes in telephony-common which is in the boot class
path.
Test: m -j ApiDemos is successful and does not show any link-type check
warning.
Change-Id: Ica508cd4daf3640e4f90fa26dd11dfd03867d717
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: I371bd0b43e66bcc4be1e26decb95c70519ac3342
The lib hasn't been built using SDK and thus has been causing link-type
check warning from SimpleJNI which is built using SDK. Since the warning
will turn into error soon, fixing the warning by correctly building the
lib with SDK.
Bug: 69899800
Test: m -j SimpleJNI is successful and does not show any link-type check
warning
Change-Id: I51edfe296c70ac99ac7698b5e06ec0e0c678945c
android.test.base/runner/mock libraries are shared libraries that are
built without SDK, but with framework interanl libraries (framework.jar,
etc). Apps or libs that are built with SDK (LOCAL_SDK_VERSION is set)
shouldn't use them, but instead the stubs version of the test framework
libraries, which are built using SDK.
This is because, the build system does not allow a module built with SDK
to depend on another module built without SDK. This has been
exceptionally allowed with warnings, but will soon be errors.
In order to prevent the expected build breakage, direct reference to the
shared libraries are all changed to the stubs libraries.
Note: no one has been using these shared libs statically. So, it is
guaranteed that they won't encounter a problem due to missing
<uses-library name="android.test.runner"/> even after this change.
Bug: 69899800
Test: m -j checkbuild
Change-Id: I7f25e0127c52c56adf288163a760f3dc9aee6586
The documentation for android.app.Service includes an example from
LocalServiceActivities.java. This example now better shows and
explains the distinction between binding and connecting. It also
shows the set of conditions that require the client to call
unbindService().
Test: make ds-docs -j16
Bug: 63118511
Change-Id: I1276de3f9421e13e1964039d37db9adc87f3039f
The documentation for android.app.Service includes an example from
LocalServiceActivities.java. This example now better shows and
explains the distinction between binding and connecting. It also
shows the set of conditions that require the client to call
unbindService().
Test: make ds-docs -j16
Bug: 63118511
Change-Id: I1276de3f9421e13e1964039d37db9adc87f3039f
The documentation for android.app.Service includes an example from
LocalServiceActivities.java. This example now better shows and
explains the distinction between binding and connecting. It also
shows the set of conditions that require the client to call
unbindService().
Test: make ds-docs -j16
Bug: 63118511
Change-Id: I1276de3f9421e13e1964039d37db9adc87f3039f
This CL adds a sample IME that demonstrates how an IME can now control
the appearance of bottom navigation bar like typical Activities can
do.
This sample IME covers the following 3 use cases to control the
appearance of bottom navigation bar.
A. (Bottom) navigation bar has solid background color.
Like typical Activities, IMEs can
- call Window#setNavigationBarColor() to change the background
color. (Bug 25706186)
- set SYSTEM_UI_FLAG_LIGHT_NAVIGATION_BAR to tell the SysUI to
optimize the navigation bar button colors. (Bug 69002467)
B. (Bottom) navigation background is seamlessly extended from the main
InputView of the IME, like typical Activities can do with
SYSTEM_UI_FLAG_LAYOUT_HIDE_NAVIGATION. Note that essentially this
is a super set of the mode A, because IMEs (and apps) can also fill
the navigation bar region with a solid color in this mode.
C. The appearance of (bottom) navigation bar is controlled by the
target application, not by the IME.
- This is useful for floating IME (Bug 22564251).
Bug: 25706186
Bug: 69002467
Test: Build and manually test as follows.
1. make -j ThemedNavBarKeyboard
2. adb install -r $OUT/system/app/ThemedNavBarKeyboard/ThemedNavBarKeyboard.apk
3. adb shell ime enable com.example.android.themednavbarkeyboard/.ThemedNavBarKeyboard
4. adb shell ime set com.example.android.themednavbarkeyboard/.ThemedNavBarKeyboard
Change-Id: I4b10a19641bd3ce6c43e7629404b6f202d4186e8
