Autofill was reading the WebView's WebSettings on a background thread.
Move it to the UI thread to conform to the WebView API and get rid of a
Strict Mode violation.
Bug: 5072283
Change-Id: Ib0ac60697f1e629ac1ef1743545b5cf0ac2cf52a
Initially we had exposed NEW in the voicemail provider instead of the
IS_READ field. However, NEW is already used in the call log to represent
a missed call for which a notification needs to be shown to the user.
On the other hand, voicemail need both be shown in a notification and
retain their own read/unread state, which is determined by whether the
user has opened the details of the voicemail.
This change introduces the IS_READ field for voicemails and exposes it
also via the call log content provider.
The NEW column in the voicemail content provider will be removed in a
follow-up.
Bug: 5036195
Change-Id: I2f8c04685a82cbf77f4778cf057ff62c7da1256a
In one use case, I see that if we go straight from
wifi client mode to tethering operation, the interface change notifications
are reported in an order that causes to enter tethered state
without actually tethering through connectivity service.
It is because an interface down notification (from wifi going down) comes after
we have started soft ap and we think we have tethered after calling startTethering
and switch to Tethered state
Instead, we should make sure tethering has started before going to Tethered state.
Change-Id: Iba7e8fab0feeb5637d40938862a8638871df8b02
First stage. Get the bones in right now even though
we are not ready on the native side.
Once, we have things underneath working - we will further update the
framework
Change-Id: I4a7dab5cd4267373dc5f8989ae4122f91c384ed5
If suggestedRetryTime is 0x7fffffff then no retry is needed
and the framework should not initiate a retry.
Bug: 4949208
Change-Id: I3756ef6a3e93beec4ee95863cbc111b9952e5e06
The set config will only update hostapd config file right now and we need to restart after that happens.
Also, softap interface is changed to be the regular interface
Bug: 5069108
Change-Id: Ibe80129b58e5339f06f186870bcd8f37569c6db3
The previous approach no longer works with the new USB drivers, since the usb0
interface is no longer enabled by default.
This introduced a chicken & egg problem - usb0 will not be enabled until the
user tries to start tethering, but Settings will not enable the checkbox unless
usb0 is enabled.
To fix this we add an explicit call to start USB tethering in the connectivity manager.
This will enable RNDIS if necessary and then bring up tethering once usb0 is enabled.
Change-Id: Iae1f733366aa6b0dafa66d4c97207794173ef54b
Signed-off-by: Mike Lockwood <lockwood@android.com>
1. Move getSupellcheckerInfo to SpellCheckerSession
2. Change the interface of getSpellCheckerSession
3. Remove a flag in SuggestionsInfo
Change-Id: I3debe09e213fc0ab74618eb3504383f2a9447fd9
1. Event were send in onBindView but since we have fixed the bug
of unattached views firing accessibility events and there is
no guarantee that the view is attached in onBindView no events
were sent. Now posting a runnable so on the next run the UI
tread will send the event i.e. after the view is bound and
attached.
bug:5008841
Change-Id: I4ed914f7fb65d6896f0c55e7c46e6508d2b2f11f
The Surface is already using SurfaceTexture internally and it is parcelable. This
is intended to replace and phase out ParcelSurfaceTexture in favor of creating a
new Surface.java object from an existing SurfaceTexture.
Change-Id: I8e2dd86614523da6abed6403e1d705a68fa19fdf
Some VPN needs more time than others in order to create the secure tunnel.
For example, L2TP/IPSec PSK on average needs 15 seconds on WiFi. On mobile
connection, variation gets larger, and it sometimes needs more than 30
seconds. This change increases timeout period from 30 to 60 seconds.
Change-Id: I6006fd254a7bc91c22f63d2f3f20ea79ee9b05e2
