| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Settings for brightness/contrast/saturation/sharpness are integers, not
floats. Update API to reflect this.
|
|
|
|
|
|
|
| |
The logic for quiet hours was wrong; this was causing sound & vibration
to be killed when it shouldn't be.
Change-Id: I7f3094de03e46c418f46608d46056005a1fb0684
|
|\
| |
| |
| | |
into froyo
|
| |
| |
| |
| |
| |
| |
| | |
- Reboot options
- Application killed
Change-Id: I6b9db0f9d39cc52feab6aba307728650c010cea5
|
|/
|
|
|
|
|
| |
ProgressBar doesn't correctly invalidate itself when state changes from
indeterminate to determinate and back. This fixes it.
Change-Id: I6d27b4c246eff8ddd8ca33ad662ab1f81d4173d2
|
|\ |
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Introduces a notion of user-defined 'quiet hours'. During this period,
notifications will be: (1) silenced, (2) have vibrations removed, and
(3) have their requested colors muted (to dim the LED on capable hardware).
Note that (3) works well on Nexus One and gracefully degrades on sapphire.
That is, LED colors are reduced, but hardware still displays them the same.
Bug: 2164
Bug: 2252
Change-Id: I66b4dbab8ccc30741b15629fb713ff18b4511b47
|
|\ \ \
| | | |
| | | |
| | | | |
"app_killed_message"" into froyo
|
| | |/
| |/| |
|
|\ \ \
| |/ /
|/| | |
|
| |/ |
|
|/ |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This patch allows the user to force the running foreground application to be
killed. One example use case for this is applications which trap buttons,
leaving the user stuck. Another would be a memory-heavy application that
traps the BACK button (so they user wouldn't want to leave it in memory by
pressing HOME). Browser is a good example of this second use case.
Change-Id: If86b9adebbec6bf88a5682ac612a505d4b26fe66
|
|\ \ |
|
| |/ |
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| | |
Used rectangular probability distribution function before by accident,
depite calculating the high-passed triangular probability density function
I intended to use. This commit rectifies the mistake and also adds
noise-shaped error feedback similar to JACK.
|
|\ \ |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| | |
Terminate the old client connection properly when an ANR occurs and
the user requests to re-launch the camera application.
CRs-fixed: 250354
Change-Id: I9989aa32ff1ecd1a3a49a3155a27d02a18a5a87d
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
If a call to getPrefs is made after weak reference to content resolver
is gone, a new observer will be created and registered at the
resolver. At registration, the resolver will allocate ObserverEntry
objects that will eventually fill the JNI global reference pool.
There is no need to create and register a new observer if one is already
registered.
Change-Id: If8442b3370299980b73d4ea83757c5eae6a85408
|
|\ \ \
| |_|/
|/| | |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Rapidly opening and closing the keyboard slider while playing a
track on the music player and touching the screen to start the key
dispatch timer, an ANR could occur because the 500ms timeout occured
with mWasFrozen true, causing waitedFor to be set to zero and mWasFrozen
to be set to false. If the 500ms timeout then occured again before the
mWasFrozen frozen flag was set to true again, the value of waitedFor
was recalculated and if this indicated that the keyDispatchingTimeout
had elapsed then a "key dispatching" ANR was raised. The intention was
to restart the timeout checks if we were frozen during configuration
change, and this is properly achieved by setting startTime to the
current time so that the subsequent recalculation of waitedFor is from
this new point.
Change-Id: I6626c4bfff82ebe3d3401fed15263d09fe2b69ad
|
|/
|
|
| |
Change-Id: I7394b9f97c82d27fe65e010ef8cfb990ff466b75
|
|\
| |
| |
| | |
into froyo
|
| | |
|
|\ \
| |/
|/| |
|
| |
| |
| |
| |
| |
| |
| |
| | |
NativeDaemonConnector calls onDaemonConnected() callback function.
In case of MountService callback function calls mConnector.doListCommand,
and exception occurs since mOutputStream is not initialized yet.
Change-Id: I5ecd3980a5e5098bce9bae434ac6e3cab9bf7067
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fixed whitespace issues.
Fix moar whitespaces
changed to if else if
Take out tabs
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Also fixes reverb like I originally intended it and tweaks
parameters a little.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Removed a couple color setting that shouldn't be "backed up" here (use xml files instead like everything else)
Added an HDPI-only setting to aid theme builders with battery alignment issues. This will be settable ONLY in xml files.
|
|\ \ \ \ |
|
| | | | |
| | | | |
| | | | |
| | | | | |
Change-Id: I3744e0ea4bd5ca67b5e23287071abb9da1cf2a20
|
|\ \ \ \ \
| |/ / / / |
|
| | |_|/
| |/| |
| | | |
| | | | |
Change-Id: I02752f9ca9f00e504506a45ad2183a4d4532e74c
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
id 21e55b4df85ccadd9809ef188e1de51942f20eb1" into froyo
|
| |/ / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
21e55b4df85ccadd9809ef188e1de51942f20eb1
Revert "Fixed ADB Pulsing when it shouldn't."
This reverts commit 7b41e023a733610c0e34744a3dc6f3682b5318e2.
|
|\ \ \ \
| |_|/ /
|/| | | |
|
| | | | |
|
| |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Subtracting the left and right channels could be argued to
separate the center channel from the left/right channel and the
DSP therefore gets applied to panned sounds only. This halves the
cost of the filtering and eliminates the bass boost issue that bs2b
compensates for with a highboost filter.
I also adjusted the delay-to-level spatial filter to try to get slightly
more consistent perception of panning across the frequency spectrum.
|
| | | |
|
| | | |
|
| |/
|/| |
|
| | |
|
| | |
|