This CL makes ExifInterface store the tag values as the original forms
and the format validiation is added that compares the given value and
the data format specificed in EXIF specification in order to keep the
valid tag values only.
Bug: 27583378, Bug: 27614052, Bug: 28075709
Change-Id: If60bbddefe74c4b87b4ce64b5fc79e467e36a5b9
Stop repeating request if any of its output stream is abandoned
and notify that repeating request has been stopped.
Update binder tests for binder interface changes.
Update CameraDeviceImpl to expect an exception when canceling
a repeating request that is already stopped.
Bug: 21270879
Change-Id: I9fa72ae7218948aac88cb1a8e57839bd022c4a5e
Since mnc 00 is represented as undefined it needs to be replaced
with MNC_ZERO 0xffff for retrieving proper resources.
bug:28219719
Change-Id: I7e1630c2f5c31959306d862b10e7987bb449ea9f
Fixes: 27533462
FrameInfo::duration() will remove time spent waiting
in the queue from the duration. This is desired because
that time is otherwise accounted for by the previous frame,
so we don't want to double count it.
This shows up mostly in TestSceneRunner & shadowgrid2
due to a combination of slow frame times and continous rendering.
Change-Id: I27c42d5c24d266de4ada8ea00ec9164d518754f8
Also fix an issue where resize was not called.
And make the translation a bit larger, because the
animation is longer.
Bug: 27870534
Change-Id: Ia6128db8108fe57bee96816fc95fd0811d941ffb
Don't return null from createUserCreationIntent()
Provide a way for apps to query if the device
supports multiple users.
Some additional documentation for UserManager class to
make things clear about the types of users and relationship
with accounts.
Change-Id: I768d816e73a1d7f61cdc415f9e482adc79e2715a
Fixes: 28150359
- Allow SearchView to expand to 48dp height if possible.
- Make the search clear button have 48dp height if possible.
- Expand the search TextView touch target height to 48dp is possible.
Framework version of patch ag/912646
Bug: 19479861
Change-Id: Ibaaef2afa20b8c05eaac8f028df4f616f2f96eb1
Fixes: 28074239
Need to convert from scaled window to screen before
updating position of the SurfaceView
Change-Id: I75dec23408c32ec01e88193ea38b1fb253b3fd6f
This configuration parameter aims to address the following requirement.
a) If the Wifi radio on the UE is in turned on state (and the UE is not
connected to any WWAN) and the user dials 911 and the UE is not
capable of making E911-VoIP over WiFi calls, then the UE shall turn
off its WiFi radio and shall try to attach to one of the WWANs,
depending upon the air interfaces supported by the UE for setting
up the 911 call to the relevant PSAP. After the 911 call ends,and
after the callback period ends, then the UE shall turn on the WiFi radio.
b) If the Wifi radio on the UE is in turned on state and the UE is connected
to a WWAN and the user dials 911 and the UE is not capable of making
E911-VoIP over WiFi calls, then the UE shall turn off its WiFi radio and
shall set up the 911 call over the WWAN to which it is already attached,
if that WWAN is available and able to support 911 calling. If that WWAN
is not available or is not capable of supporting 911 calling, then the UE
shall select an available WWAN for setting up the 911 call. Assumption is
that while a LTE network may not have 911 calling support capability, all
1x, GSM and UMTS networks will be 911 capable. After the 911 call ends,
and after the callback period ends, then the UE shall turn on the WiFi radio.
c) If the Wifi radio on the UE is in turned on state (and the UE is not connected
to any WWAN) and the user dials 911 and the UE is capable of making E911-VoIP
over WiFi calls, then the UE shall not turn off its WiFi radio but shall first
try to attach to one of the WWANs, depending upon the air interfaces supported
by the UE , for setting up the 911 call to the relevant PSAP.
d) If the Wifi radio on the UE is in turned on state (and the UE is also connected
to a WWAN) and the user dials 911 and the UE is capable of making E911-VoIP over
WiFi calls, then the UE shall not turn off its WiFi radio but shall first try to
attach to one of the WWANs, depending upon the air interfaces supported by the
UE,for setting up the 911 call to the relevant PSAP.
Thus,the following address the requirement above.
1) Introduce a parameter (KEY_CONFIG_WIFI_DISABLED_IN_ECBM) to conifgure Wifi disable
in ECBM for the requirement c & d. This key shall be overridden in the specific
carrier overlay configuration file (defaulted to FALSE).
2) Already existing API (setWifiEnabled()) to turn ON/OFF Wi-Fi cater the requirement a & b .
Bug: 27854016
Change-Id: I5af370c143630bdd4b075f4730fd1de1bbe1fe7d
These particular boradcasts need to expose phoneId since they are valid even
when there is no SIM.
ACTION_SERVICE_STATE_CHANGED
- Added phoneId to broadcast.
- Removed TelephonyRegistry non subId call.
ACTION_SIGNAL_STRENGTH_CHANGED
- Added phoneId to broadcast.
- Removed TelephonyRegistry non subId call.
ACTION_PHONE_STATE_CHANGED
- Added phoneId to broadcast.
- The non-subId version is called by Telecomm to communicate overall state.
Telephony sends its own version, so only the Telephony call needs to add
phoneId.
Bug: 27378995
Change-Id: I554f7ee18b9ae19919f4724328dcff3ef9cbd092
When having an app docked and then going home, and then launching
the app from the homescreen, we had a wrong transition because
getTopMost task was already set to the launched app, because
getRunningTasks doesn't exclude the docked stack. Instead of adding
flags for getRunningTasks, which sounds risky, we just pass a "force"
value when we launch recents in this state.
Bug: 27154882
Change-Id: Iee4512fed13115dbbe8b74413ff1fa9b87afa0ef
Because we only "carve" out the area for the IME once it's actually
visible now, we need to relayout the windows when we show it - else
they won't update the insets until the next real layout happens.
Bug: 28175599
Change-Id: Ie0af1225da03905bfcb52044e212812c892c88a9
When tests run for the first time, the list of activities that can
handle ACTION_SEND_MULTIPLE might not be scrollable, which was cause the
scrollForward() method to fail.
BUG: 27431998
Change-Id: I5992bc9fec6291c74c4af7887ee66eb4f96e87c0
Per feature council decision, the multi-endpoint APIs will be @hide for
the N release.
Bug: 28196918
Change-Id: Ia80b089bc754ce87ca208382eb79442b5265844d
Framework edition
Previously we would throw away any stopped LoaderManagers when we went
to retain instances to pass along as nonConfigurationInstances during
config changes or similar activity restarts. This causes loaders to do
more work than they need to when a calling activity starts a new
activity on top, a config change happens (e.g. screen rotation) and
then the top activity is finished, restarting the caller in a new
configuration. The loaders would go through onReset unnecessarily,
potentially throwing away data to be reloaded again after the config
change completes.
Instead of throwing away stopped LoaderManagers in this case, restart
them and retain them across the config change so they can resume where
they left off.
Bug 27176186
Change-Id: Ia52c6448d2ad41dcb25d493770d9ffae20a19d2a
