If a print service reports a printer with no capabilities and then
removes and adds the same printer again with no capabilities we can
call layout with invalid attributes. While the print service should
not do that we must not crash. The reason is that the print dialog
code was lacking a check whether something changed before handling
the change of the current printer. This resulted in calling layout
even though we still do not have the printer capabilities resulting
in passing bogus print attributes to the app.
bug:11216402
Change-Id: Icb9161930a70a7f9ead589a0ab0b4eb35091666f
1. Remove Tethering profile for Spain Orange(214-03). Because Orange and Euskaltel use same MCC-MNC but have separate tethering APN.
- Spain Orange(214-03) use "internet" apn.
- Spain Euskaltel(214-03) use "internet.euskaltel.mobi" apn.
2. Remove Tethering profile for Spain Telefonica(214-07). Because Telefonica and Jazztel use same MCC-MNC but have separate tethering APN.
- Spain Telefonica (214-07) use "movistar.es" apn.
- Spain Jazztel (214-07) use "jazzinternet" apn.
3. Remove Tethering profile for France Orange(208-01). Because Orange and Carrefour/NRJ/Tele2/Virgin/use same MCC-MNC but have separate tethering APN.
- France Orange (208-01) use "orange.fr" apn.
- France Carrefour (208-01) use "ofnew.fr" apn.
4. Remove Tethering profile for UK T-Mobile(234-33). Because T-Mobile and Orange were merger so doesn't use "consumerbroadband" apn for tethering anymore.
5. Remove Tethering profile for HK 1O1O(454-00). Because 1O1O and NWMOBILE use same MCC-MNC but have separate tethering APN.
- HK 1O1O(454-00) use "lte.internet" apn.
- HK NWMOBILE(454-00) use "NWMOBILE" apn.
6. Remove Tethering profile for HK 3(454-03). Because 3 LTE and 3G have separate tethering apn.
- HK 3 LTE use "lte.three.com.hk" apn.
- HK 3 3G use "mobile.three.com.hk" apn.
7. Update Tethering profile for Orange(340-01). The format of tethering profile was wrong.
8. Add Tethering profile for Mexico Iusacell(334-050).
9. Add Tethering profile for Portugal Optimus(268-03).
Bug: 11176211
Change-Id: I453ff8b745ee4f483bfdd6c362bd67ce50ba8b7a
Conflicts:
core/res/res/values-mcc234-mnc33/config.xml
Setting config_enableTranslucentDecor to false will not
prevent clients from adding FLAG_TRANSLUCENT_NAVIGATION or
STATUS to the window or using the TransluentDecor themes,
but it will prevent View.STATUS_BAR_TRANSLUCENT and
View.NAVIGATION_BAR_TRANSLUCENT from being propagated to the
SystemUI so these requests will not be honored.
Bug: 11182618
Change-Id: I8be6a3a565acf0987ff12f18f1c7e67c96d563c3
Migrate transient bar mode to IMMERSIVE_STICKY, and
introduce new behavior for IMMERSIVE: namely the
opaque bars are revealed by clearing the flags on swipe.
Remove low-profile optimization that confuses api demos
and other apps using low-profile as a signal.
TransientNavigationConfirmation renamed to
ImmersiveModeConfirmation, and its associated resources,
since the confirmation is now shown when the nav bar is
shown in either of the two immersive modes.
Remove unused Toast.makeBar and associated hidden framework
bits now that the confirmation uses a cling instead.
Bug:11062108
Change-Id: Iae49d31973940b9bee9f5b1827756db5eaa76aa3
Defense in depth:
1. If there's a sticky battery broadcast waiting around for
us, apply its information immediately.
2. If for some reason there is no battery information,
just don't draw anything.
Bug: 11208146
Change-Id: I43e4b55a90a4ca619816ad0315e329f88b529581
The CL that ensured that a dying task must be in front of the user
(ag/374996) only checked that the task was at the top of /a/ stack,
not on top of the frontmost stack. This checks the stack for being
frontmost before switching to home.
Fixes bug 11208762.
Change-Id: I43f6d380e7a880ec19db03711ada6c7437e15f73
