| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| |
| |
| |
| | |
https://android.googlesource.com/platform/frameworks/base into cm-13.0
Android 6.0.1 release 22
Change-Id: I0d31899b234156a91accb61e0a7fb3d8d16d5062
|
| |
| |
| |
| |
| |
| | |
-We add logs to track how much screen time we save with the ungaze feature.
Change-Id: I02bce959ce7ed5bc6c848e51256063c946ff3e87
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Change-Id: I8cc3fc465daa49c9010bdbbf876dae18461d7024
Require: topic:dock_battery
Signed-off-by: Jorge Ruesga <jorge@ruesga.com>
Improve dock battery strings
Change-Id: Iccfa2df4ec608ae02c0bfcef99648788dab95933
systemui: fix battery text level visibility
Use present flag instead of plug-in flag to determine the battery present (only hide the
text level view if the battery is not present)
Change-Id: I8e20e107bbeeecdc846833dc80c1a2754d82a039
Signed-off-by: Jorge Ruesga <jorge@ruesga.com>
systemui: restore space between clock & battery
Initialize dock battery to GONE visibility because isn't update on device not supporting
dock battery.
Change-Id: I23aeafc27db0fc499050a7306e8549293accb507
Signed-off-by: Jorge Ruesga <jorge@ruesga.com>
SystemUI: fix battery icon jump on qs expand
The layouts are slightly different for the header and icon layouts.
Change-Id: I85d3fc007eb9b2c3e2ba09bb761a91b521b89700
Signed-off-by: Roman Birg <roman@cyngn.com>
systemui: move dock battery level views outside systemicons layout
At not the ideal, this at least will match normal battery level view, puttings battery levels
in the correct order. In addition fix two small dock battery bugs:
- BatteryLevelTextView not displayed if mode is TEXT
- Properly hide DockBatteryMetterView for modes NONE and TEXT
- Underline the dock BatteryLevelTextView to differentiate normal from dock text view
Screenshot: https://cloud.ruesga.com/f/74fe240c66/
Change-Id: Idfd3a4bb2f19bd29f9f4dd2b0ea7f645bb531986
Signed-off-by: Jorge Ruesga <jorge@ruesga.com>
|
|
|
|
|
|
|
|
| |
Fixed b/23523554. Logs time duration when the underlying sensor was
turned on to detect camera launch gesture. The goal is to diagnose
the power consumption of the camera launch gesture.
Change-Id: Ie9554e0ba1c5b290c451f951472575289bae85c7
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Issue #22209630: Only allow whitelisted apps to put apps on the temp whitelist
We now check whether the calling app is a system uid or in the whitelist
and, if not, throw an exception.
Issue #22225665: Alarm still goes off in idle mode (doze)
Fix a bug where we were not clearing the calling identity when coming
through the dump command to the service, and as a result when we would
eventually call out to the alarm manager it wouldn't do what we want.
This was only broken when being controlled by the shell.
Also adjust the network policy manager service's handling of device
idle transitions to only toggle the device idle state, which gets rid
of the long delay we have coming out of idle mode. And add in a bit
of logging around going in/out of idle mode to try to understand where
things may be slow in the future.
Change-Id: I4a41f790e9b0bb31330314b94111557d479f2ba5
|
|/
|
|
|
|
|
|
|
|
|
|
| |
Counts may differ from user perception. For example, if notifications arrive
after the shade is open (even if it is only peeking) there will not be another
panel_reveal before the user sees the shade. User perception is more accurately
measured by visibility events.
Peek events will report the notificaiton load as 1.
Bug: 20088581
Change-Id: I10221d4b66a18c223aae21e616615f087c65b1e1
|
|
|
|
|
|
|
|
| |
Only sysui knows the true rank, since it can (and does) reorder things.
The visibility logs are down in the service because it has other bits of data.
Bug: 21395744
Change-Id: Ibf9479dc2306fb27fb5df3bf21e161478d36d587
|
|
|
|
|
| |
Bug: 21242827
Change-Id: I1b8beee5cc12a9cd23e81554f7f2236ddc29e2b6
|
|
|
|
|
|
|
| |
previously, some logs had only some times, and not others.
Bug: 21394955
Change-Id: I0d7af163be23f5a989c35aba6e6f6879672543fc
|
|
|
|
|
|
|
|
|
|
| |
Split out monolithic visibility notifications into individual logs for
each visibility change with longevity and freshness.
Add exposure time to cancelation logs.
Bug: 20122735
Change-Id: I56c112cdb54fb65b41cfbef4c36ce8706729c5cb
|
|
|
|
|
|
|
|
|
| |
Write samples of the old and new state to the binary event log whenever
the user modifies the auto-brightness adjustment. We wait a few seconds
before logging to ensure that the user is satisfied with the adjustment.
Bug: 19786916
Change-Id: I41402decd1034d0839aa0f47495bc00907ab9c08
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Main change is to fix problems in the alarm manager where it
was not doing a good job at scheduling the device idle wakeup
before an alarm. To fix this, we now keep explicit track of
the next "wake from idle" alarm so we can consistently use that
to adjust the time of the device idle alarm if needed.
Also a bunch of debugging stuff to help further diagnose this
problem:
- Alarm summary now includes the last time the alarm went off.
- Improved dumpsys output of alarms.
- New event log tags for changes related to idle state.
Change-Id: Idd2c8d24ae23379f7c75815ddbc6835c2a04656c
|
|/
|
|
|
|
|
| |
Also track the total lifetime in the notificaiton record.
Bug: 20122735
Change-Id: I09668be0161de0e1d8201b069e533a9a2203c83c
|
|
|
|
|
|
|
|
|
|
| |
- Keep track of calls to AudioSystem.getDevicesForStream.
- Report device changes for the base streams to the binary event log.
- Fire internal intent so volume UI can respond to changes.
- Update devices when new routes are reported.
Bug: 19618959
Change-Id: I7bbd497b178d9829accc19e6c951a711aef8590c
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Add a new volume_changed event, reported at the stream level.
- Only include changes to base streams (no aliases).
- Include the caller for each change. A caller is either:
- a pkg name (for external calls or known media sessions)
- a system server class's log tag (for internal calls,
disambiguates "android")
Bug: 19599935
Change-Id: Ia61b68ff1e7e2907a24972790ec052bfe099e665
|
|
|
|
|
|
|
|
|
|
|
|
| |
When SysUI is the only notification listener, drop group children
if there is a group summary in NoMan.
There are two changes needed to achieve this:
1. Cancel children when a summary is posted
2. Drop children if there is a summary
Bug: 18460939
Change-Id: I5a3f30b0b23b2a784783749f58352c05a7fb9e59
|
|
|
|
|
|
|
|
| |
Log whether an enqueued notification updated a previously present
notification.
Bug: 18083122
Change-Id: Ie6ed69f0bf53c668701b44e33282ca74b509a7e3
|
|
|
|
|
|
|
|
| |
In addition to logging cancelation command, also log actually
canceled notifications via the new eventlog tag notification_canceled.
Bug: 18083122
Change-Id: I1e3e1e1368f39519f34c002ae374f318f647a401
|
|
|
|
|
|
|
|
|
| |
Introduce notification_action_click logtag that is logged whenever
the user clicks any notification button. For standard templates, we
also log the index of the pressed action button.
Bug: 18064190
Change-Id: Icb07795ff711729d16bde0b7e03d13c2f466779c
|
|
|
|
| |
Change-Id: I40d9876dad2a8ec98135e3df127950dc3797040b
|
|
|
|
|
|
|
|
|
| |
We've been seeing some really funky behavior when upgrading or
downgrading system apps around OTA time. Put more of these one-time
logs into durable storage to help investigate.
Bug: 17805839
Change-Id: If898d7df229c1f71e598b0d965325c272060e5e7
|
|
|
|
|
|
| |
Bug 16689703
Change-Id: If870f1b7b9cb3929ac1edc38affc688a37c2acfd
|
|
|
|
|
| |
Bug: 16618854
Change-Id: I501f396fa495e1e55a27d7d0b65aac66495418c1
|
|
|
|
|
|
|
|
|
|
| |
Emit notification_clicked log events when a notification
is clicked from SystemUI.
Also refactor the onNotificationClicked method to work with
a key instead of individual notification params.
Change-Id: Iffd15e95d46371b2ae7bfd00b2c348d9f4cf5d14
|
|
|
|
|
|
|
|
|
|
|
| |
Keep track of notifications shown in the notification panel
and log them via eventlog.
Added the following eventlog tag:
* notification_visibility_changed
Bug: 13442201
Change-Id: Ifb74ec2492967dc787b4de86db7d7f00be6c7f74
|
|
|
|
| |
Change-Id: Ie7e15ed15739cb5f057c900e1cadf90824b2b4ef
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Include calling UID/PID in the existing
notification_{enqueue/cancel/cancel_all} event logs.
Include a new "reason" arg for cancel + cancel_all to
identify listener vs noman vs statusbarmgr calls.
Found and fixed a cancelAll path (from statusbarmgr)
that was not logging at all.
Bug:13442201
Change-Id: I2e1f875076a96b1fe3b86e8990641efb1cadfcfb
|
|
Refactored the directory structure so that services can be optionally
excluded. This is step 1. Will be followed by another change that makes
it possible to remove services from the build.
Change-Id: Ideacedfd34b5e213217ad3ff4ebb21c4a8e73f85
|