summaryrefslogtreecommitdiff
path: root/packages/SystemUI/src/com/android/systemui/UiOffloadThread.java
AgeCommit message (Collapse)Author
2020-08-166/N Move everything into SysUIComponent.Dave Mankoff
It is far easier to move _everything_ into SysUIComponent, and then selectively promote things back to GlobalScope and/or WMScope than it is to try to do it one at a time. With this change, though lots of files are touched, very little actually changes structurally. After this change goes in, folks should stop using @Singleton quite so freely. Most things should live in @SysuiSingleton. @Singleton is due to quickly be replaced by @GlobalScope. Bug: 162923491 Test: atest SystemUITests && manual Change-Id: Idc31d3d83b030581fb1fa869f7fafc4f2d3a8828
2019-12-23Start removing Dependency.get(UiOffloadThread.class)Dave Mankoff
This actually begins the process of deprecation and removing UiOffloadThread in favor of using Executors directly. This CL hits the easiest spots in the code. There are a few more remaining calls that should be in their own independent CLs. Bug: 146567476 Test: atest SystemUITests Change-Id: I2542cc61653f330a1931b15a57e3b7c77d18e2e6
2018-12-21Clean up DependencyProvider a bitJason Monk
Create DependencyBinder which is abstract and can tell dagger how to convert directly between interfaces and implementations without requiring code for it. Test: compile (which runs dagger) Change-Id: I7013ee12d37172441e2c70cf2fe36f707975c821
2017-05-18Optimize latency when unlocking phoneJorim Jaggi
Latency when unlocking the phone regressed a bit for two reasons: - For lockscreen -> app we now have to create a full starting window containing the snapshot, while previously this was just showing a surface. - For lockscreen -> home, we can't use the saved surface anymore because currently we don't support snapshotting translucent activities. However, in the long term, we want home screen to be more involved into transitions anyways, so we'll have to wait for the first frame draw anyways. However, crystal ball trainee developer Jorim added some artificial latency in this transition 3 years ago, because he knew that it is going to be an issue at some point so we have some headroom to improve! Genius! On a more serious note, it was because he didn't understand how to read systraces with binders involved (to be fair, there was also no binder tracing). Now, we can completely fix the introduces latencies above by removing this latency of 100ms, and we are 30-70ms better than before! However, this requires a lot of discipline in SystemUI. Currently, the callback to dismiss Keyguard takes around 30ms. By moving all non-essential binder calls of the main thread or to the next frame, we bring this down to 5ms, such that window animation and Keyguard animation starts about at the same time. Test: Take systrace, unlock phone...profit! Change-Id: I3ea672bc2eca47221bc6c9f3d7c56b6899df207d Fixes: 38294347