On user-debug and eng builds, you can set the
"db.log.slow_query_threshold" system property to queries that
take longer than the specified number of milliseconds.
Set it to 0 to log all queries.
This property has been around for a while but it was implemented
poorly. In particular, it *changed* the behavior of the query
by calling getCount() while holding the Db connection.
In normal operation, the query will not actually run until later.
By putting the timing logic into fillWindow() instead, we ensure
that we only measure queries that actually ran. We also capture
cases where the cursor window gets filled multiple times.
Bug: 5520301
Change-Id: I174f5e1ea15831a1d22a36e9a804d7755f230b38
Swiping the home screen causes the WindowManagerService to do
a bunch of work to keep the wallpapers in sync. First, it lays out
and places all windows. Also, it notifies the SystemUI process that
the wallpaper position has changed.
The layout/place operation is too much work - we only need to set
the position values for the wallpaper, not relayout the whole system.
The notification mechanism must exist, but should be optional. Most
wallpapers don't care (especially static ImageWallpapers). So we'll
give them a new API (WallpaperService.Engine.setWantsOffsets()) to
allow wallpapers to opt out of this process and avoid the performance
overhead.
Change-Id: I66c38375438937f14f6f5550565b28eb204b1e06
We used the paddingTop parameter in the rot90 layout to
pretend that there was a status bar shifting all the
navigation icons down; by setting this to 0 we now spread
the navigation icons evenly across the entire display.
Bug: 5530481
Bug: 5459659
Change-Id: I7f8663049c597300818549f18d7a419537f44b96
1. AccessibilityInteractionConnection was non-static inner
class, hence keeping a handle to the enclosing ViewRootImpl
resulting in leaking activities.
bug:5525412
Change-Id: Ie438861663d623d503995844125d9e15d677fc32
AAPT fix printf %zd crash on Windows.
There's no printf %zd on Mingw/Cygwin so the verbose
printf crashes aapt.
SDK bugs: 20395, 20986
Change-Id: Ic201faffd871bd4c1b7d173d84b089e09750cd85
A recent patch taking scroll into account was applied at the wrong
level. isVisible() expects positions that already take scroll into
account. isOffsetVisible() is where the initial bug was.
Cherry pick of 144415 from master.
Change-Id: I06ceebfb3d7b24aa4adba886c24fcf9d8dd39d2e
The assembly expects arguments to live at fixed offsets from the stack pointer
which are invalid if the code is inlined.
Change-Id: Ie93e93c5c69774079112345754fbc85896fc2f64
Still needs integration with Settings (for persistence) and VolumePanel UI.
Change-Id: I9eca92c4b1ef2df2564411006a35753ab9618dce
Signed-off-by: Mike Lockwood <lockwood@android.com>
If post processing is not disabled, we end up translating LF to CRLF, which
makes binary protocols sad.
Change-Id: I43ddd0c690c0d00f5e9416a2397b43d5153491d3
Before HW came in, when doing SW clock recovery, gain had been set to
produce a correction expressed in PPM from [-100, 100] PPM. The HW
local clock HAL has been spec'ed to take a drive range from MIN_INT_16
to MAX_INT_16. This changes the PID recovery loop to use a range from
MIN_INT_16 to MAX_INT_16, and adjusts the P and I gains to be the same
as they were before, but adjusted for the scale change.
Change-Id: Ia636fd1bc6c5c1117ddfdc5289c51286cb874c23
Change the definition of the panic threshold for the time sync service
to take the round trip time of the packet producing the discipline
action into account. The idea here is that, in the worst case, the
error in the measurement of the clock sync error might be as high as
the round trip time of the packet used to measure the error. If a
packet says we are 50mSec fast, its RTT is 75mSec, then we could be
anywhere from 25mSec slow to 125mSec fast.
This change basically makes it so that the error measurement must be
greater than the RTT + the fixed panic threshold before we panic. IOW
we don't panic unless we absolutely sure that our error must be
greater than the fixed panic threshold. Also, lower the current value
of the panic threshold from 50mSec down to 20. Now that the
definition takes into account the RTT, we can afford to be much
tighter in our definition of the fixed panic threshold.
Change-Id: Id801f6b59545ee52d59944dfa3d545d108f88b0e
Client's of Masters who disappear before the client has processed even
one timesync response should not enter the Ronin state. Since they
have never synced to the old Master's timeline, by becoming Ronin they
run the risk of defeating other new Ronin's in the master election,
even though they don't have any idea what time it is on the old
Master's timeline and therefore are unsuitable to serve as the new
Master. Instead, they should transition to the Initial state, where
other new Ronins (who do know what time it is) have the chance to step
in and serve as master of the old timeline. If there are no other
Ronin who can do the job, then the old timeline is dead and by
transitioning to Initial, a new one will be generated.
Change-Id: Iaa95313bfe68a971be2764e252ebf4b34313013d
Signed-off-by: John Grossman <johngro@google.com>
We need to pass an RpcContext with information
such as the caller's certificate. I also modified
the compiler so it does not use Container anymore
and uses Context
Change-Id: Ib54b774f9c7b5cb3e0a014ce91548b817efcb72b
When a cable was unplugged, we were telling the driver to release the
ip address so if a cable on a different network was plugged in, it would
still try to use it's old ip address on the new network, which probably
didn't work.
Also, we didn't notify ConnectivityService about the state change in
the unplug case. Some of this was done in the interface removed case,
but we never remove the interface in Tungsten, just unplug. So refactor
the common disconnect code into a disconnect() function that's called
by both the link status change (unplug) and interface removal (only applies
to things like USB ethernet dongles) cases.
Change-Id: I19d7ceb540d6a0e24df1b55314a13af78f1e593d
Signed-off-by: Mike J. Chen <mjchen@google.com>
