| 205ec5a969963f563b30b37385362ccfebdd5e4c |
14-Nov-2012 |
Daniel Sandler <dsandler@android.com> |
Clean up the Builder test.
Improved vibration coverage
Fixed LED color
Added priority
Added a start delay (for testing LED while screen off)
Change-Id: I3dab0a1a7494f0fe7631d1af49c0fb9a1fdd3f63
otificationBuilderTest.java
|
| b9d36649ca458cb5326a144fd88e26b92efba728 |
19-Oct-2012 |
Daniel Sandler <dsandler@android.com> |
Properly show emoji in the notification ticker.
Add an emoji test to StatusBarTest (working around some
difficulties in actually putting high-Unicode chars in the
layout xml).
Bug: 7378383
Change-Id: Ifce9844b26f67d2799521623e5161aa4dad69ed1
otificationBuilderTest.java
|
| 1e3b98d47df596d0c4eadbdf60143709f8465b28 |
01-Oct-2012 |
Jeff Brown <jeffbrown@google.com> |
New internal API to eliminate poke locks.
Added a new WindowManager.LayoutParams inputFeatures flag
to disable automatic user activity behavior when an input
event is sent to a window.
Added a new WindowManager.LayoutParams field userActivityTimeout.
Bug: 7165399
Change-Id: I204eafa37ef26aacc2c52a1ba1ecce1eebb0e0d9
owerTest.java
|
| 11cf178100e71d3f9f34ab5865e03a277c5eadaa |
27-Sep-2012 |
Daniel Sandler <dsandler@android.com> |
Cleanup internal status bar APIs.
IStatusBarService.collapseQuickSettings is gone;
collapseNotifications is now collapsePanels, which does what
collapse() used to do. Similarly,
IStatusBar.animateCollapseQuickSettings is now simply
IStatusBar.animateCollapse().
Bug: 7245229
Change-Id: Id157d2fdf34926d3c85ffa8b81c741a5359aede4
tatusBarTest.java
|
| e20a177d3f147f3011647c3bdab401f90b2c5d1d |
26-Sep-2012 |
Svetoslav Ganov <svetoslavganov@google.com> |
Adding a global accessibility action to open quick settings.
1. Added APIs for opening the quick settings to the StatusBarManagerService
and the local StatausBarManager. The new APIs are protected by the old
EXPAND_STATUS_BAR permission.
Renamed the expand* and collapse* non-public APIs that are expanding
the notifications to expandNotifications* collapseNotifications* to
better convey what they do given that this change adds
expandQuickSettings* and collapseQuickSettings*.
Added a global action to the accessibility layer to expand the quick
settings which is calling into the new status bar manager APIs.
bug:7030487
Change-Id: Ic7b46e1a132f1c0d71355f18e7c5a9a2424171c3
tatusBarTest.java
|
| 4120375d46091df8527bb701882e056fbb0e6b06 |
31-Aug-2012 |
Dianne Hackborn <hackbod@google.com> |
Remove Binder.getOrigCallingUid().
Replaced all remaining places that used it with explicit user
specification.
While doing this, I ran into stuff that was creating PendingIntent
objects (that now need to specify the explicit user they are for),
which are also posting notifications... but have no way to specify
the user for the notification.
So the notification manager in the system process now also gets a
formal concept of a user associated with the notification, which
is passed in to all the necessary aidl calls. I also removed the
old deprecated aidl interface for posting/cancelling notifications,
since we now always need a user supplied.
There is more work that needs to be done here, though. For example
I think we need to be able to specify USER_ALL for a notification that
should be shown to all users (such as low storage or low battery).
Along with that, the PendingIntent creation needs to be tweaked to
be able to handle USER_CURRENT by evaluating the user at the point the
pending intent is sent.
That's for another change, however.
Change-Id: I468e14dce8def0e13e0870571e7c31ed32b6310c
otificationTestList.java
|
| 9630704ed3b265f008a8f64ec60a33cf9dcd3345 |
28-Jul-2012 |
Jeff Brown <jeffbrown@google.com> |
Power manager rewrite.
The major goal of this rewrite is to make it easier to implement
power management policies correctly. According, the new
implementation primarily uses state-based rather than event-based
triggers for applying changes to the current power state.
For example, when an application requests that the proximity
sensor be used to manage the screen state (by way of a wake lock),
the power manager makes note of the fact that the set of
wake locks changed. Then it executes a common update function
that recalculates the entire state, first looking at wake locks,
then considering user activity, and eventually determining whether
the screen should be turned on or off. At this point it may
make a request to a component called the DisplayPowerController
to asynchronously update the display's powe state. Likewise,
DisplayPowerController makes note of the updated power request
and schedules its own update function to figure out what needs
to be changed.
The big benefit of this approach is that it's easy to mutate
multiple properties of the power state simultaneously then
apply their joint effects together all at once. Transitions
between states are detected and resolved by the update in
a consistent manner.
The new power manager service has is implemented as a set of
loosely coupled components. For the most part, information
only flows one way through these components (by issuing a
request to that component) although some components support
sending a message back to indicate when the work has been
completed. For example, the DisplayPowerController posts
a callback runnable asynchronously to tell the PowerManagerService
when the display is ready. An important feature of this
approach is that each component neatly encapsulates its
state and maintains its own invariants. Moreover, we do
not need to worry about deadlocks or awkward mutual exclusion
semantics because most of the requests are asynchronous.
The benefits of this design are especially apparent in
the implementation of the screen on / off and brightness
control animations which are able to take advantage of
framework features like properties, ObjectAnimator
and Choreographer.
The screen on / off animation is now the responsibility
of the power manager (instead of surface flinger). This change
makes it much easier to ensure that the animation is properly
coordinated with other power state changes and eliminates
the cause of race conditions in the older implementation.
The because of the userActivity() function has been changed
so that it never wakes the device from sleep. This change
removes ambiguity around forcing or disabling user activity
for various purposes. To wake the device, use wakeUp().
To put it to sleep, use goToSleep(). Simple.
The power manager service interface and API has been significantly
simplified and consolidated. Also fixed some inconsistencies
related to how the minimum and maximum screen brightness setting
was presented in brightness control widgets and enforced behind
the scenes.
At present the following features are implemented:
- Wake locks.
- User activity.
- Wake up / go to sleep.
- Power state broadcasts.
- Battery stats and event log notifications.
- Dreams.
- Proximity screen off.
- Animated screen on / off transitions.
- Auto-dimming.
- Auto-brightness control for the screen backlight with
different timeouts for ramping up versus ramping down.
- Auto-on when plugged or unplugged.
- Stay on when plugged.
- Device administration maximum user activity timeout.
- Application controlled brightness via window manager.
The following features are not yet implemented:
- Reduced user activity timeout for the key guard.
- Reduced user activity timeout for the phone application.
- Coordinating screen on barriers with the window manager.
- Preventing auto-rotation during power state changes.
- Auto-brightness adjustment setting (feature was disabled
in previous version of the power manager service pending
an improved UI design so leaving it out for now).
- Interpolated brightness control (a proposed new scheme
for more compactly specifying auto-brightness levels
in config.xml).
- Button / keyboard backlight control.
- Change window manager to associated WorkSource with
KEEP_SCREEN_ON_FLAG wake lock instead of talking
directly to the battery stats service.
- Optionally support animating screen brightness when
turning on/off instead of playing electron beam animation
(config_animateScreenLights).
Change-Id: I1d7a52e98f0449f76d70bf421f6a7f245957d1d7
owerTest.java
|
| e7e9b6e0339f2636afefc8d3f4cd9d807d94b901 |
04-May-2012 |
Daniel Sandler <dsandler@android.com> |
Fix NPEs in StatusBarTest.
Change-Id: I9245a297a9a09c09415dd38e662692665ae7e109
otificationTestList.java
|
| bc5559f1922d72715940f754faffc82da4100eab |
19-Apr-2012 |
Daniel Sandler <dsandler@android.com> |
Expand too-small notifications to fill 64dp.
Also fix NotificationTestList so it runs again.
Change-Id: I2fb28cd9cfad25a7a1b17ccef9ccd741c3aa99b0
otificationTestList.java
|
| c2346134bb519a54d50655cbef940fc3fdec60a9 |
13-Apr-2012 |
Jeff Brown <jeffbrown@google.com> |
Extract Vibrator implementation from interface.
Moved the core logic of Vibrator into SystemVibrator, potentially
allowing for the creation of other Vibrator subclasses.
Fixed several places where we were creating new Vibrator
instances unnecessarily instead of getting it from the Context.
It is safe to make Vibrator abstract because its constructor
was hidden from the SDK so it was not possible to subclass it.
Bug: 6334179
Change-Id: I18ece6544c26a7efb2d5099f8346a10aef8a5e18
otificationTestList.java
|
| 2561b0b10a55841a08e0e1d467e73e10b1bf256d |
14-Feb-2012 |
Daniel Sandler <dsandler@android.com> |
New notification priority and related APIs.
This change introduces a few new bits of data on
Notification that will help the Notification Manager and
System UI route and display them more intelligently:
-> priority: an integer in a predefined range that
indicates the app's best guess as to the relative
importance (to the user, right now) of that information
-> kind: a tag (really, set of tags) indicating the general
type of notification (realtime, asynchronous, etc)
-> extras: a Bundle of additional key/value pairs
associated with this notification (currently @hidden)
The notification manager takes these data into account when
assigning to each notification a score which is passed with
the notification on to the system UI, where it can be used to
affect presentation. For example:
- Spammy apps (identified explicitly by the user or by
some other means) will have their notifications scored
very negatively by the notification manager, allowing
the UI to suppress them
- Notifications of higher score might be shown larger
or in a different way
- Very important notifications (indicated by a very high
score) might interrupt the user during an otherwise
important task (videochat, game, etc)
Implementation note: This replaces/extends the old internal
notion of "priority", which was mostly used to organize
ongoings and system notifications at the top of the panel.
Change-Id: Ie063dc75f198a68e2b5734a3aa0cacb5aba1ac39
otificationTestList.java
|
| a3850b68399ab49032e1fc2a2eab129fe3a7e69e |
06-Dec-2011 |
Daniel Sandler <dsandler@android.com> |
Improve handling of small largeIcons in tablet ticker.
The tablet system bar is too short for a full notification
row, but it will show the largeIcon of a new notification in
its full frame, intruding into the main application content
rectangle a bit. This is a good thing---the notifications
really pop out at you---but it looks a little odd if the
largeIcon is actually *small*: the icon is vertically
centered in the larger (invisible) rectangle, making it look
poorly centered on the system bar.
This change will detect short largeIcons and center them in
the system bar's height instead. Additionally, it applies
the same ticker background all the way to the left
underneath largeIcons that are not full-frame (and therefore
have transparent regions).
Bug: 5708907
Bug: 5560485
Change-Id: I32af45632df164c58fb960110063dbaa08b5536c
otificationBuilderTest.java
|
| dba935659024a9ca83cb6bd3f1a9970e277f7658 |
06-Oct-2011 |
Daniel Sandler <dsandler@android.com> |
Break apart DISABLE_HOME and DISABLE_RECENT.
Additionally, start using setSystemUiVisibility() where
possible in the keyguard to allow activities and dialogs to
re-enable some of the navigation keys (notably: home but not
recents).
Finally, stop disabling MENU for activities atop the keyguard.
Bug: 5380495 // no home in driveabout, clock
Bug: 5396134 // able to show home/recent in keyguard
Change-Id: I04eb224554ee8cff79476b85148c4cda75bb0b62
tatusBarTest.java
|
| 029d5877b0c19af09c6a1cb7d1c3d3507e88430c |
12-Sep-2011 |
Daniel Sandler <dsandler@android.com> |
Hide navigation buttons when they are DISABLEd.
Back is hidden by DISABLE_BACK; Home, Recents, and Menu are
hidden by DISABLE_NAVIGATION.
Bug: 5261576
Bug: 5284740 (confusion about visible inactive icons)
Change-Id: I410c133b737cc11d61bac0318dc24458353ee7b3
tatusBarTest.java
|
| 542f0510d42e225546acc01842adfafb27f627b6 |
11-Aug-2011 |
Daniel Sandler <dsandler@android.com> |
Fix fullScreenAlert test.
Change-Id: I3df0a998347c9e3d21e067381bd22eb9a0862f0d
tatusBarTest.java
|
| 60ee25643e0a7b8841063a4e97b0f18c51807e91 |
22-Jul-2011 |
Daniel Sandler <dsandler@google.com> |
The fullest of fullscreen modes.
View.setSystemUiVisibility() now properly accepts a
bitfield, including:
* SYSTEM_UI_FLAG_LOW_PROFILE: "lights out mode"
(previously known, erroneously, as STATUS_BAR_HIDDEN)
* SYSTEM_UI_FLAG_HIDE_NAVIGATION: for when you need every
single pixel on a device that also has a navigation bar
These flags are painstakingly aggregated across the entire
view hierarchy and carefully delivered to the status bar
service, which in turn gently passes them along to the bar
implementation.
To really get access to the whole screen, you need to use
HIDE_NAVIGATION in conjunction with FLAG_FULLSCREEN and
FLAG_LAYOUT_IN_SCREEN. See development/samples/Overscan for
an example of how to do this.
Change-Id: I5fbfe009d9ceebbbf71db73f14a7008ea7c1d4da
tatusBarTest.java
|
| 6179ea3196e9306d3f14361fe9ef14191b1edba6 |
28-Jun-2011 |
Svetoslav Ganov <svetoslavganov@google.com> |
Adding accessibility support to the Status Bar.
1. Added content description to pretty much all animals
in the zoo including buttons in the navigation bar,
notifications and status icons for battery, signal,
data, etc.
2. Rectored to avoid ovelaying views since they block
touch exploratino. In general overlaying views
cause trouble for touch exploration and accessibility
in general.
3. Avoid sending accessibility events in case the user is
touching outside of the StatauBAr panels to avoid
confusion.
4. Added records to accessibility events in the places where
this would help the presentation. So the event comes from
a given "leaf" view and its predecessor is adding a record
to the event for itself to provide more cotext. It is up
to the accessiiblity service to choose how to present that.
bug:4686943
Change-Id: I1c1bd123d828fb10911bca92130e9a05c1f020b3
tatusBarTest.java
|
| f81c70944ae1c2566a72b3c20c609b8520ad9456 |
04-Jun-2011 |
Daniel Sandler <dsandler@google.com> |
Merge "Fix the status bar test app."
|
| 1d4d30aebd2c22627131819cabfe95f97def2c83 |
28-Apr-2011 |
Daniel Sandler <dsandler@google.com> |
It's lights out for you, navigation bar!
Views requesting lights out mode will cause the navbar to
disappear (this is useful for viewing videos/photos/etc
using every pixel of the screen).
But there's a catch: any user activity at all will cause the
lights to come back on and the navbar to return.
Change-Id: I535ed3ba9ae7fab3282c402be256add765395b6f
tatusBarTest.java
|
| 982cbf1cbc302eb1ee4ab10076533281c6a947c7 |
17-Dec-2010 |
Daniel Sandler <dsandler@google.com> |
Fix the status bar test app.
Change-Id: Ib7d047a5ed21393ea9cbcdc343cb0cfbb7c62ff7
tatusBarTest.java
|
| e40451a89dc91dfd636af7cb32a23b4a4cc93fdc |
03-Feb-2011 |
Daniel Sandler <dsandler@google.com> |
Ongoing notification for GPS use.
This change improves upon the notification priority API
introduced in change I9e738cc4, allowing privileged clients
to set the priority of a notification when posting it
directly to INotificationManager. StatusBarTest is updated
to test this new feature.
The new LocationController in SystemUI uses this facility to
post a high-priority ongoing notification whenever GPS is in
use (replacing the functionality of the legacy GPS status
bar icon).
Also happens to fix http://b/3325472 (adding a log message
when notifications are dropped because of a missing icon).
Bug: 3412807
Change-Id: I523016ffa53bf979be98ddc4a2deb55a6270c68a
otificationTestList.java
|
| 7bb8eeb90cf55f409a282c1f36ca08aa48c10543 |
28-Jan-2011 |
Joe Onorato <joeo@google.com> |
Allow the status bar disable flags to be used as View's system ui visibility fields.
Bug: 3363046
Change-Id: I50ba06ed9a4d2f5d0e0c807437aea9900f44fee9
tatusBarTest.java
|
| 664644d9e012aa2a28ac96f305b1ce6499ec8806 |
24-Jan-2011 |
Joe Onorato <joeo@google.com> |
visibility ("lights out") API.
1. Views may setSystemUiVisibility() to recommend that
the system chrome (status bar or other UI) show or hide
itself. (This functionality was previously available only
via the FLAG_FULLSCREEN window flag for some SystemUI
implementations.)
2. Views may register a OnSystemUiVisibilityChangedListener
on a view, and find out when the system UI actually
appears or disappears, allowing apps to coordinate the
appearance of their own UI if desired.
Bug: 3241144
Change-Id: Ia1758d94099182d49a1e3688ea2738ae4995b829
tatusBarTest.java
|
| 80a44401a22344f7eabce6976372ab144ef22893 |
16-Jan-2011 |
Joe Onorato <joeo@google.com> |
Need to update the largeIcon for notifications when we're reapplying the views.
Bug: 3298062
Change-Id: I6bb72c0b93e00a9de8cc2633ac07add0a572a20f
otificationBuilderTest.java
|
| d070e89396e250782c015bc993bcae6e7e03af7a |
08-Jan-2011 |
Joe Onorato <joeo@google.com> |
Make AppWidgetService handle components enabling and disabling.
Change-Id: Ie6b75cb90be38bbce694ccf2d5a342d7f0172fa4
owerTest.java
|
| 6f6cf3c5e577aa62cfd959fa5ef046531090ce31 |
16-Dec-2010 |
Daniel Sandler <dsandler@google.com> |
Reimplement StatusBarManager.disable(DISABLE_SYSTEM_INFO).
Bug: 3284968
Change-Id: I7171b7770c2972bb56672a771c7ed5ca10fb4dda
tatusBarTest.java
|
| 3e8f5a2c1beb4b918856063880e05125946e4347 |
03-Dec-2010 |
Daniel Sandler <dsandler@google.com> |
Hide navigation buttons and clock on lockscreen.
(This introduces a StatusBarManager disable flag to ask the
status bar to hide just the clock, which might be useful in
other situations, such as clock/dock apps.)
Bug: 3130393
Change-Id: Ia08627508518e2ed3713ffbf856e4ec42952b3a8
tatusBarTest.java
|
| 373a9983742b3d2370c36183aca3cde4614e6185 |
30-Nov-2010 |
Daniel Sandler <dsandler@google.com> |
When updating notifications, always reuse the last row.
Ordinarily, changing the "when" slot when updating a
Notification will move its expanded payload to the bottom of
the notification panel's list. But if it's already at the
bottom, this causes an unsightly out-then-in animation
sequence. We now check for that exact situation.
Bug: 3222274
Bug: 3162218
Change-Id: I8b643b3f8bce64e57a22bdbb06d92c196c2484c2
otificationTestList.java
|
| 8d0b655c496e9125fc8d289c4e5bc9a78297ba3d |
23-Nov-2010 |
Joe Onorato <joeo@google.com> |
Add a better notification test and clean up the flag handling in the notification builder.
Change-Id: I9354ed2c2cda690f53e5f43ad60943b63b02e7d4
otificationBuilderTest.java
|
| 561d3858bb9409b999a19f7ba93f0b12e1db835f |
21-Nov-2010 |
Joe Onorato <joeo@google.com> |
The large icon for notifications.
Change-Id: I8537c602b5b5fca03be8980295bfa28330543669
otificationBuilderTest.java
|
| 3f76aa7755fbb2e77ca6a648bbfa1f75680788c9 |
20-Nov-2010 |
Joe Onorato <joeo@google.com> |
Test for using the right size of notification info text.
Change-Id: Iac8764542ddcd3ef0375f6d6d03225e9f6c2fc1c
otificationBuilderTest.java
|
| 8595a3dd9a6feff70f8ddbad924d79b591d611e4 |
20-Nov-2010 |
Joe Onorato <joeo@google.com> |
Show the number in the expanded notification instead of in the bar.
Change-Id: I248b4fe1732ed290e9f3f9c094de4544a0e396ab
otificationBuilderTest.java
|
| 46439cec0eb0da4d0f853f2d8712d0c00c98475b |
19-Nov-2010 |
Joe Onorato <joeo@google.com> |
Update the look of the notifications. Includes adding a new Notification.Builder class.
Change-Id: I7c57b81c45defe77d6f3d22472e9cf8432bbed03
onfirmationActivity.java
otificationBuilderTest.java
otificationTestList.java
|
| 1a542c7b8ed0be049869a12d1e01e2604d052ac2 |
08-Nov-2010 |
Joe Onorato <joeo@google.com> |
The CHEEK_TOUCH stuff never worked. Remove it.
Bug: 3104906
Change-Id: Ia37236ba1775fc3ec8c111e2e0b85b105e0dea6a
owerTest.java
|
| 4058ba052682129f2d1055116aaffb2e91c2013d |
31-Oct-2010 |
Joe Onorato <joeo@google.com> |
Allow both contentIntent and setOnClickPendingIntent in notifications
From the app developer's request:
Intents assigned to specific views should take precedence over the content intent, but it should not
be required to set the content intent to null in order for the view-intents to work
Bug: 3107945
Change-Id: Ic5282d441277a9a8c8c700ef3f43872f3405b58a
otificationTestList.java
|
| b0cc50de14dc9e2d0d224803bb523aa7f48904ac |
26-Oct-2010 |
Daniel Sandler <dsandler@google.com> |
Notification flyovers.
Hold your finger on an individual notification icon to
quickly show that notification's payload.
Also: Quickly swipe up on any icon to open the tray.
Bug: 2994009
Change-Id: I2ae2b546fcfa62994b63b9376f487289b2d06796
otificationTestList.java
|
| 184498ce5a8d77e1d9c45693363829daaeef9611 |
08-Oct-2010 |
Joe Onorato <joeo@google.com> |
Allow notifications to not specify a contentIntent.
If they don't, the click events will be passed through to the individual
views in the notification view, which may have their own PendingIntents
attached.
Previously, it was against the UX spec to allow this, but now we are
changing that and will have buttons in there.
Change-Id: I674234212f64b2b8802a0708b7eed0614e147ca3
otificationTestList.java
|
| 39b4867d483cc9aba36b26a81074d9f606661671 |
09-Oct-2010 |
Jason Chen <jasonchen@google.com> |
Revert "Merge "Allow notifications to not specify a contentIntent.""
This reverts commit 8885321046622d6a8c0a4214af98dc27eecd48a0, reversing
changes made to 61b8aaadd742f0be708cd37971d2c9e822bf778a.
otificationTestList.java
|
| 80a752c5373cfa906568302c831710b5c22a8155 |
08-Oct-2010 |
Joe Onorato <joeo@google.com> |
Allow notifications to not specify a contentIntent.
If they don't, the click events will be passed through to the individual
views in the notification view, which may have their own PendingIntents
attached.
Previously, it was against the UX spec to allow this, but now we are
changing that and will have buttons in there.
Change-Id: Ie3b2e96c6a1c4449fa86ed571f3ad0f047320d31
otificationTestList.java
|
| 2cddeb4b82d02b540234b7b2ca0e2c0f163fc5d6 |
07-Oct-2010 |
Joe Onorato <joeo@google.com> |
am 2c164747: am f7872780: Merge "PowerManagerService needs yet another flag..." into gingerbread
Merge commit '2c164747d364c3e51964d03ecefc5752c7c0c6ba'
* commit '2c164747d364c3e51964d03ecefc5752c7c0c6ba':
PowerManagerService needs yet another flag...
|
| 2c164747d364c3e51964d03ecefc5752c7c0c6ba |
05-Oct-2010 |
Joe Onorato <joeo@google.com> |
am f7872780: Merge "PowerManagerService needs yet another flag..." into gingerbread
Merge commit 'f7872780ca3dae9584251b1e3495aed12110254c' into gingerbread-plus-aosp
* commit 'f7872780ca3dae9584251b1e3495aed12110254c':
PowerManagerService needs yet another flag...
|
| 8274a0e53630f80ab356f69ddad895ed9638574e |
05-Oct-2010 |
Joe Onorato <joeo@google.com> |
PowerManagerService needs yet another flag...
... to make sure that if you press the power button to turn off the
screen, that the prox sensor won't turn it back on.
Bug: 3011618
Change-Id: Id16c1d65417539d4592f485b1c3efb737540c3cd
owerTest.java
|
| 066b5c5166c1f5342bd42aa0d68f784a5f4c1dd1 |
05-Oct-2010 |
Joe Onorato <joeo@google.com> |
manual merge Merge commit '77e42376' into work
Conflicts:
packages/SystemUI/res/values/colors.xml
packages/SystemUI/src/com/android/systemui/statusbar/StatusBarService.java
Change-Id: I891c8a9f6410037ca7805507e85a17f1655c115e
|
| 77e42376823197ae7fb3cea2afcca734723174a5 |
04-Oct-2010 |
Joe Onorato <joeo@google.com> |
am 87efbbb5: Merge "implement the number bubbles on the status bar" into gingerbread
Merge commit '87efbbb563ef96a74ffd2fbbe5c0865a450254df' into gingerbread-plus-aosp
* commit '87efbbb563ef96a74ffd2fbbe5c0865a450254df':
implement the number bubbles on the status bar
|
| 6c01a11a20d5fc796360e5e97998401a6cc84f27 |
04-Oct-2010 |
Joe Onorato <joeo@google.com> |
implement the number bubbles on the status bar
Bug: 2993482
Change-Id: I73b1f8c39e995fd4f986c25ea04127eb23c3cd07
otificationTestList.java
|
| 7ebd659dbf3aa672cd1a686938f3df22d429be1f |
27-Sep-2010 |
Joe Onorato <joeo@google.com> |
Merge commit 'f9f9e248' into manualmerge
Conflicts:
packages/SystemUI/src/com/android/systemui/statusbar/StatusBarService.java
tests/StatusBar/src/com/android/statusbartest/StatusBarTest.java
Change-Id: Ibbb2fec2d8c6f5d41398272753d271dfae698100
|
| f9f9e248a034b3dd891a7bd9f476b1cad5f33779 |
27-Sep-2010 |
Joe Onorato <joeo@android.com> |
am 6fa4de3c: Merge "If an icon add remove get coalesced, don\'t remove some other icon." into gingerbread
Merge commit '6fa4de3cffe1390f699051fa0c7d21e8058a5ebd' into gingerbread-plus-aosp
* commit '6fa4de3cffe1390f699051fa0c7d21e8058a5ebd':
If an icon add remove get coalesced, don't remove some other icon.
|
| 795f2840b4a70bf188c2f24c8c06f73a492b338c |
27-Sep-2010 |
Joe Onorato <joeo@android.com> |
If an icon add remove get coalesced, don't remove some other icon.
Also adds a test case and turns off the extra logging we added to debug this.
Change-Id: I8640938ae4d1e75c88213177888f363e05ce0fa0
tatusBarTest.java
|
| 091e1b8a86d34d2d51d2a5f7ae3cd903925fa5bf |
27-Sep-2010 |
Joe Onorato <joeo@android.com> |
Implement disable() on the status bar.
This includes adding the new DISABLE_NAVIGATION flag.
Bug: 3000770
Change-Id: I6d1c3586198e13e06b5d26e8b23a9495dc4ba02e
tatusBarTest.java
|
| ddf680bff5bb9bc04ef04667644db8ade0b38c46 |
26-Sep-2010 |
Joe Onorato <joeo@android.com> |
Touching the blue glow should close the system and notification panels.
Bug: 3029373
Change-Id: I96760656dcda20ab238305900f9964083a8e5273
otificationTestList.java
|
| ef1e7763c2dc5b9bac69cc747efe05c81d9fd9fc |
18-Sep-2010 |
Joe Onorato <joeo@google.com> |
Tablet ticker.
Change-Id: Ia3db5cc29eac1703123de3e1c6dc7c22e7d024eb
otificationTestList.java
|
| 9305647eb61bb60a1f42481a0c0d208dc9bbe965 |
10-Sep-2010 |
Joe Onorato <joeo@google.com> |
Plumb lights out mode through from the window manager to the status bar running in the system ui process.
Lights out mode itself isn't implemented.
Change-Id: Ieeef0eb9ae5be23000f770e74e8ee66472f4c673
tatusBarTest.java
|
| 44af754cf0c9ad9a8162e1bd2af60737e81a8beb |
28-Aug-2010 |
Daniel Sandler <dsandler@android.com> |
am d02bdaab: Remove experimental immersive mode support. DO NOT MERGE
Merge commit 'd02bdaab495641ab50e2123fdfd99a819cc40540' into gingerbread-plus-aosp
* commit 'd02bdaab495641ab50e2123fdfd99a819cc40540':
Remove experimental immersive mode support. DO NOT MERGE
|
| d02bdaab495641ab50e2123fdfd99a819cc40540 |
26-Aug-2010 |
Daniel Sandler <dsandler@android.com> |
Remove experimental immersive mode support. DO NOT MERGE
Bug: 2949215
Change-Id: I7d998ef571ef7e149bb96261430e92150b80b77d
tatusBarTest.java
|
| 6cf5eb0606ecdc22e7c431971a0c621413564840 |
20-Aug-2010 |
Daniel Sandler <dsandler@android.com> |
am 3f677b1b: Merge "Fix periodically disappearing status icons." into gingerbread
Merge commit '3f677b1b3e45240728de39d60441d791c0e8d3f8' into gingerbread-plus-aosp
* commit '3f677b1b3e45240728de39d60441d791c0e8d3f8':
Fix periodically disappearing status icons.
|
| 0398bf70e703e89aacb074e4ef9b4a86843e3d06 |
19-Aug-2010 |
Daniel Sandler <dsandler@android.com> |
Fix periodically disappearing status icons.
Occasionally the animation listener wasn't being told that
the ticker animation had completed; this callback was
essential to keeping the status bar's internal state correct
(namely, setting mTicking=false). The safest thing to do is
simply set mTicking to false immediately upon tickerDone()
or tickerHalting().
Bug: 2915280
Change-Id: I997911b12fa2985fa83b42154fb3485220886219
otificationTestList.java
|
| 8a76a9085dbbca87b4c172577ca264d8b5f2ab32 |
30-Jul-2010 |
Jean-Baptiste Queru <jbq@google.com> |
am 9150cff6: Merge "Replaced /sdcard with Environment.getExternalStorageDirectory()"
Merge commit '9150cff64abc79927ade28061ac99a1ebf812905' into gingerbread-plus-aosp
* commit '9150cff64abc79927ade28061ac99a1ebf812905':
Replaced /sdcard with Environment.getExternalStorageDirectory()
|
| 8b85dceadf281705a94d7546556fa5969364a658 |
19-Jul-2010 |
Christian Mehlmauer <FireFart@gmail.com> |
Replaced /sdcard with Environment.getExternalStorageDirectory()
Change-Id: I9a7413f81090b69c82ca6b1e585f5e379b19e60c
otificationTestList.java
|
| b59b94456b3a8fdfdf524a81274839f657fbb65b |
30-Jun-2010 |
Daniel Sandler <dsandler@android.com> |
Fix icon size in intruder alerts.
(Updated test app to confirm the fix.)
Change-Id: Ife56cf07f282786162e2ebc5aaddbb24dac6cafd
tatusBarTest.java
|
| 27a8be4b3526f068e911c8edcd4ee6fa6f492c0f |
29-Jun-2010 |
Daniel Sandler <dsandler@android.com> |
Support for tapping on an immersive-mode priority notification.
When the user taps on an intruder alert (the priority
notification in immersive mode), the .contentIntent in the
Notification object will be sent, just as we handle tapping
on a normal Notification in the windowshade.
Change-Id: Ib6991837b0b2122fe138cddacf347fdbc426b99d
tatusBarTest.java
|
| 8896783dc1d31c5274b277c364da0ffe7cc27cca |
23-Jun-2010 |
Daniel Sandler <dsandler@android.com> |
Updated StatusBar test app for new notifications API.
New actions:
- Toggle activity's immersive mode
- Post a priority notification with fullScreenIntent
that launches an alert-like activity
Change-Id: Ie38372209985577b6db856924c19914c000e1cec
tatusBarTest.java
estAlertActivity.java
|
| 0faeb078cf2bf689eaa69e7041013c5152281b4f |
07-Jun-2010 |
Joe Onorato <joeo@android.com> |
Add a test item the turns on a bunch of extra icons.
Change-Id: Ia5884ef46a5b0fa2d608c7924b3eb12293a1da8b
tatusBarTest.java
|
| 005847b03b2ebe3eb1a974a8a04ad51bca6636cd |
04-Jun-2010 |
Joe Onorato <joeo@android.com> |
Handle errors inflating notifications (and their icons).
On an inflation error, the StatusBarService cleans up, removes / doesn't add
the views, and calls into the StatusBarManagerService, which tells the
NotificationManagerService to remove the notification.
That then calls all the way back into the StatusBarService, but I think being
extra careful is okay. Throughout the status bar, it's all keyed off of the
IBinder key, so if the app comes in with a good notification while we're
cleaning up, we won't lose the new notification or anything like that.
Change-Id: Iea78a637495a8b67810c214b951d5ddb93becacb
otificationTestList.java
|
| d2b1f00e1e34cdce0047af7374aa57b1e4b5b040 |
04-Jun-2010 |
Joe Onorato <joeo@android.com> |
Add some disabled logging and another test case for reapplying the notification views.
Change-Id: I839d7771ab42a5d508ce7d15385f6ac6a4e3be83
otificationTestList.java
|
| 175f79c5a556416817a8f8674b2e0ac3b3cb6e6b |
26-May-2010 |
Joe Onorato <joeo@android.com> |
In fact, switching an item between ongoing and notifications works.
The test just wasn't testing that.
Change-Id: If1af2a7258d2a3764f845d9862a0a0ff62b1d7ed
otificationTestList.java
|
| 871bdb9867f6630d8bb28e5607263e8bf4eac3ba |
25-May-2010 |
Joe Onorato <joeo@android.com> |
Handle bad icon resources.
Change-Id: I87c5fe68ad8016596068ba7889f3b6d36da3386b
otificationTestList.java
|
| 0e26dffd6cfcb09b08a94a857b891fdef7fe2b1e |
24-May-2010 |
Joe Onorato <joeo@android.com> |
updateNotifications works.
Change-Id: I924763a2d42ca1967719f3eb72c57d1cbb912dd7
otificationTestList.java
|
| 4762c2d75a55e0854bbff2f996748116d4ab1a37 |
18-May-2010 |
Joe Onorato <joeo@android.com> |
Add expand and collapse.
Change-Id: I58ad95c59b2c46d3f25349e137d5624aefc6c6cd
tatusBarTest.java
|
| 1bd7597b8cdaf39d1183077c463cb30596eb31b0 |
02-Jun-2010 |
The Android Open Source Project <initial-contribution@android.com> |
merge from open-source master
Change-Id: I8333e295ba6b6ed8e7658ecf3fbf1ebea3537aeb
|
| ef367529f9c7a538d74599b37b49ac309d0a8d8c |
31-May-2010 |
Christian Mehlmauer <FireFart@gmail.com> |
Replaced raw string arguments for Context.getSystemService() with final Context variables
Change-Id: If5139a1526101292e5da557bfad3f4db80fb64a8
otificationTestList.java
|
| 8382068ef2d385183f090373f3b0c6026bd56a99 |
17-May-2010 |
The Android Open Source Project <initial-contribution@android.com> |
merge from open-source master
Change-Id: I139c349b80b2cecfbdc30bd697cba099740293d9
|
| b0fbe297c50df5dcfb81721fd6079dd7125f88e0 |
05-Mar-2010 |
Mattias Östergren <mattias.ostergren@sonyericsson.com> |
Updated RGB LED test cases
The test cases for turning on the RGB LED with persistent light was corrected.
The color for blinking was updated to blue. And finally an option for turning
off the lights was added.
otificationTestList.java
|
| 91e1d0cddaaec5e077ca689744463901f9d5d580 |
05-Feb-2010 |
Daniel Sandler <dsandler@google.com> |
Add support in StatusBarManager for disabling ticker text.
The new flag, DISABLE_NOTIFICATION_TICKER, will be used by
the car dock app (in conjunction with DISABLE_EXPAND) to
minimize distractions to the driver.
It may also be used by the secure lockscreen to avoid
leaking personal information when the screen is on but the
device is locked (e.g. when the desk dock app is running).
Change-Id: Ibc8efde7da7501767163ae0a75f7c369b824e2a2
tatusBarTest.java
|
| 68065e0a1980ab6abf8963b48b011efa017fe1c2 |
04-Feb-2010 |
Joe Onorato <joeo@android.com> |
Fix 1667521 - system process crash after bad notification
The steps to reproduce this were kind of interesting. You needed to have
a notification with a bogus RemoteViews in the first position in the list,
and then have another notification come in with an earlier timestampe. In
that case, it would get a bad index for the new (not bogus) view that was
being added.
otificationTestList.java
|
| c83bb730ec0333e52990a40edf6d54bb66b1d5ba |
20-Jan-2010 |
Joe Onorato <joeo@android.com> |
Add DateTimeView, a widget that shows a time or the date depending on the
current time. Use that for notifications instead of a TextView that
doesn't ever update.
BUG 1563917
otificationTestList.java
|
| e71d9e421da070705a8f37aaf702282467a9fe7f |
05-Nov-2009 |
Joe Onorato <joeo@android.com> |
Another test for StatusBar test.
otificationTestList.java
|
| 32f114b3c73c0c9146d507ac1473be1700eba14b |
28-Mar-2009 |
Joe Onorato <> |
AI 143279: am: CL 142828 am: CL 142827 Fix a typo that made the blink rate of the LED incorrect.
(and add a test that helped me debug it)
Original author: joeo
Merged from: //branches/cupcake/...
Original author: android-build
Merged from: //branches/donutburger/...
Automated import of CL 143279
oastTest.java
|
| 36197e77c34b33135b4a3dc89d36ce80320dcd72 |
25-Mar-2009 |
Joe Onorato <> |
Automated import from //branches/master/...@141000,141000
owerTest.java
|
| 105925376f8d0f6b318c9938c7b83ef7fef094da |
19-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //branches/cupcake_rel/...@140373
otificationTestList.java
|
| 4df2423a947bcd3f024cc3d3a1a315a8dc428598 |
05-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@136594
otificationTestList.java
|
| 9066cfe9886ac131c34d59ed0e2d287b0e3c0087 |
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
otificationTestList.java
owerTest.java
tatusBarTest.java
estActivity.java
oastTest.java
|
| d83a98f4ce9cfa908f5c54bbd70f03eec07e7553 |
04-Mar-2009 |
The Android Open Source Project <initial-contribution@android.com> |
auto import from //depot/cupcake/@135843
otificationTestList.java
owerTest.java
tatusBarTest.java
estActivity.java
oastTest.java
|
| f013e1afd1e68af5e3b868c26a653bbfb39538f8 |
18-Dec-2008 |
The Android Open Source Project <initial-contribution@android.com> |
Code drop from //branches/cupcake/...@124589
otificationTestList.java
owerTest.java
tatusBarTest.java
estActivity.java
oastTest.java
|