GitHub PushEvent at 2014-06-24 10:16:52
Repository: android_frameworks_base
Actor: Evisceration
Payload: {"shas":[["3a2bee828cf66732a05732602dd01dbb20004a88","6970b8b6ed99ea26be75acb1906a90d18b9da5c5@sonymobile.com","Activity chooser \"Always\" button is not working\n\nWhen ResolverActivity is created with a custom list of matching\napplications (rList) as in NFC case, and the alwaysUseOption is\nset to true, the prferredActivity is not saved even if the user\npresses the \"always\" button.\n\nWhen a list is provided the variable mBaseResolveList will be\n!= null. This will set mOrigResolveList = null.\n\nWhen an activity is choosen and one of the buttons are pressed\nonIntentSelected is called. The first thing this method does\nis to check mAdapter.mOrigResolveList != null, however in this\ncase mOrigResolveList is always null, and the value is not\nsaved as PreferredActivity.\n\nThis problem was introduced in\n6d8dfbd8149942f25f2b9643a12f1fb38f3be834.\n\nChange-Id: I9eac41b7861b5e68ad3978af0dc0285f2a34eb88","Xiong Li",true],["e91b1d43ae508bac5a100bd621c6bc614e58a8a2","4bceda912b479e46f041c22bcc2c9ed75fe8d5cc@web.de","Fix frontOfTask assignment.\n\nIf all activities of a given stack were finishing, no activity was\nmarked as front-of-task. This confused ActivityManager, so make sure\nthere's always exactly one activity marked as front-of-task.\n\nChange-Id: I087cbe10280d4a60aa5ccfaefe24a223523fb3f2","Danny Baumann",true],["f4cea1c5e2a43feee9c24161528af55bc3b4d4c3","c5563b592d47b496bda4566f2ec92a6cdaf96eb3@gmail.com","Theme IME switcher alert dialog\n\nChange-Id: I5344e9ddbacb1520080532d9cc1a7a5f5428e131\nSigned-off-by: Dirk Rettschlag <dirk.rettschlag@gmail.com>","Dirk Rettschlag",true],["59edc5dc57cf79926bdbabd4031ce79af127b47b","2c4256676acc36e079a3fd9141786c2938cdfa49@cyngn.com","Themes: Use INSTALL_LOCATION_INTERNAL_ONLY for legacy icon packs\n\nIf an icon pack is currently applied and is installed using forward\nlocking, the system will crash when the pack is updated.  Several\napplications can have the pack attached to their resources and this\ncauses the system to crash because it cannot unmount the asec container\nto finish the post install process.  Installing these packs to internal\nstorage without forward locking alleviates this issue.\n\nThis is done with theme packs as well, including legacy themes.\n\nChange-Id: I155fc0bd671f3f9baaf2565d1c4d654a0a5348dc","d34d",true]],"size":4,"ref":"refs/heads/android-4.4","head":"59edc5dc57cf79926bdbabd4031ce79af127b47b"}