This CL needs to be reverted after the issue is fixed, as it clutters
the code a lot.
Bug: 17439581
Change-Id: I548fdd73bbcd6d6ce727901f9dcd9f3f7268db9d
The print preview UI owns and drives the lifecycle of several objects.
These objects were torn down too late resulting in an attempt to use
the activity as a context when it was no longer valid and service unbind
resulting in causing a crash.
Fixed a bug where if the back button is pressed mutiple times when
the print UI is being initialized a crash occurs.
bug:17454041
Change-Id: Ic1455b467586f0ad65f907e2160ec5cfb2d17d05
Instead of pulsing every 30 seconds to mimic the LED, use
a function that pulses more frequently for new notifications,
decaying to a slower pulse, and eventually stopping.
Specifically, the step function for the interval is:
- 10 seconds for the first minute
- then 30 seconds until the five minute mark
- then 60 seconds until the 30 minute mark
- then no pulsing at all
- Since we pulse more frequently on new notifications, remove
the "multi-pulse" concept.
- Move all doze-related duration parameters to a new helper,
backed by config, overridable by sysprops, include in dump.
- Wake up from dozing when hitting volume keys during a pulse.
-
Bug:17393939
Change-Id: Ica86f08b25c738338fced165c77faf3dfccd0343
If the user input in the print UI is invalid we show an error icon
next to it. The design requires no error message being shown in a
popup but TextView does show the popup all the time.
bug:16966145
Change-Id: I7aa1ec8093bc76e2f440bcb243609e92e049786b
Saves us some memory and more importantly, prevents layer trashing
and some skipped frames when building the layers.
Bug: 17287256
Bug: 16513124
Change-Id: Ief7c9a892da57bc77264de016f5118277e648f45
Cloning of settings to managed profiles could fail due to security restrictions. This caused
Settings app crash. Instead the exception is now caught inside SettingsProvider, logged,
and we leave the app running.
Bug:17450158
Change-Id: I7525d634e57701db304117f4b2035faf53977836
Currently, when we are connected to a wifi network without
Internet connectivity (e.g., a captive portal, or an access
point that's not connected to the Internet), we display the wifi
icon and hide the mobile network type icon. This is incorrect,
because all traffic is in fact going over mobile data. This
could cause nasty surprises if mobile data is metered.
Instead, make the icons reflect the true state of affairs:
- A wifi icon means device traffic goes through wifi.
- A wifi icon with ! means wifi is connected but has no
Internet and traffic is not going through wifi.
- Mobile bars with a network type (e.g., "LTE" means device
traffic goes through mobile data.
- Mobile bars without a network type mean that mobile data is
connected but device traffic is not going through mobile data.
- Mobile bars with ! mean that cell is not connected.
Bug: 17237507
Change-Id: I923edbeab3013f10314633c01922c8684591b15c
When loading DocumentsUI in management mode (for Downloads), we
normally focus on a single authority and let the other providers
keep loading async. However, when one of the providers kicks a
change notification, we end up blocking the main thread.
Simple fix is to move the blocking into the AsyncTask.
Bug: 17452691
Change-Id: Ie5212ad825b7df719690b29941c9ae9ba2cabe4b
1. Leftover code was setting the state to configuring
before initialization is complete.
2. We were not cancelling the print job if cancelled
when initializing.
3. The remote print document was cancelled even if
doing nothing.
bug:17451600
Change-Id: I79a80b723af8537da260012470748b4e8831fd9e
