{"push_id":667768287,"size":10,"distinct_size":10,"ref":"refs/heads/lp9","head":"00fc56e6915c697c78c9453bf1cf1b86f23597de","before":"36e8ebe8262a628216353382a0340a208825bc53","commits":[{"sha":"e3afd0cd3e416f3e9ca612176b1ff65464b1da42","author":{"email":"7fb1af48ad3f9a487e1291e1f9cb0d9f90b4f222@htc.com","name":"louis_chang"},"message":"[ActivityManager] Avoid NullPointerException if no\ncrash info\n\nSymptom:\nThis issue happens because the ANR process got killed\n(because it crashed) before the ANR dialog dismissed.\nIn that case, the process record is marked as crashed\n(ProcessRecord.crashing = true). When the ANR dialog\ndismissed by user, it will cause NullPointerException\nwhen writeToParcel while performing IPC because there\nis no crash info (ApplicationErrorReport.crashInfo = null)\n\nSolution:\nCheck crashinfo before access it\n\nChange-Id: I2995de57684c1e13aab8297f5eea1e82ca3b7ad8","distinct":true,"url":"https://api.github.com/repos/liquid0624/android_frameworks_base/commits/e3afd0cd3e416f3e9ca612176b1ff65464b1da42"},{"sha":"2a3d8dfd68e7424ce9b6b523b8bf602bb5bdb4a8","author":{"email":"0df773411399da712c68d794dbc79cdefac85f9a@gmail.com","name":"Alexander Mironov"},"message":"Fragment animations are not being saved across configuration changes\n\nAs per comment #5 in issue #25994:\n\nThe problem here is not that the state isn't saved and restored, the problem is how the BackStackRecord is rebuilt.  The ops themselves do save and restore the state, the problem is in BackStackRecord#addOp.\n\n    void addOp(Op op) {\n        if (mHead == null) {\n            mHead = mTail = op;\n        } else {\n            op.prev = mTail;\n            mTail.next = op;\n            mTail = op;\n        }\n        op.enterAnim = mEnterAnim;\n        op.exitAnim = mExitAnim;\n        op.popEnterAnim = mPopEnterAnim;\n        op.popExitAnim = mPopExitAnim;\n        mNumOp++;\n    }\n\nThe enter, exit, popEnter and popExit animations are overwritten with whatever is currently in the record, which during the restoration process these are 0 so the values which were saved in the ops is lost.\n\nChange-Id: I095cc7ff4ae65581d728f34217fb873ad2f0c574","distinct":true,"url":"https://api.github.com/repos/liquid0624/android_frameworks_base/commits/2a3d8dfd68e7424ce9b6b523b8bf602bb5bdb4a8"},{"sha":"d8bb38ce1edab702d56e7eae62cf6826b92dd488","author":{"email":"817f44a60cecc769780565298912cd8f8045a54f@gmail.com","name":"Kang Zhang"},"message":"Fix the bug in replacing a fragment with itself.\n\nSummary:\n\nWe are facing a bug that some fragments in our app got removed\nrandomly. We debugged the app and it seems there is a bug in\nthe fragment API.\n\nWhen we we are trying to replace a fragment with itself. We will\ntry to make the operation a null op, then both `op.fragment` and\n`f` will be reset to null.\n\n  op.fragment = f = null;\n\nBut since it's inside a loop, if the list `mAdded` still have\nitems to be visited, the code will continue to the next\niteration. Then it will compare the fragment with null, and\nreach the line:\n\n  mManager.removeFragment(old, mTransition, mTransitionStyle);\n\nEventually it will delete all left fragments in the list `mAdded`.\n\nThis diff adds a break to abort the searching after we null\nthe operation.\n\nTest Plan:\n\n1) Tested with our app. No fragment is randomly removed.\n\nRevert Plan:\n\nChange-Id: I5dc2c07a1bb1d1da1b0fd4e5610d970d55a81e86\nTags:\nSigned-off-by: Kang Zhang <kangzhang.cn@gmail.com>","distinct":true,"url":"https://api.github.com/repos/liquid0624/android_frameworks_base/commits/d8bb38ce1edab702d56e7eae62cf6826b92dd488"},{"sha":"ac2c3c4a2de7d54e8a8b0294429f689125c3e7e9","author":{"email":"7f5bb03cf507c861269be561971108be8f37d832@chemlab.org","name":"Steve Kondik"},"message":"storage: Don't list removed volumes in storage list\n\n * Don't tell apps that USB storage or empty SD slots are available for\n   use. This fixes errors about trying to create dirs in vold as well\n   as the relevant CTS cases.\n\nChange-Id: Ic763d40c19b0bb9f7497cc1515baf1661d76e9ee","distinct":true,"url":"https://api.github.com/repos/liquid0624/android_frameworks_base/commits/ac2c3c4a2de7d54e8a8b0294429f689125c3e7e9"},{"sha":"ca103170e7cc42376d29413133cc384af0aa13ee","author":{"email":"238a1843d81dd7fbe80b5c1b99515c4ba8c94d0d@cyngn.com","name":"Roman Birg"},"message":"frameworks: implement system-wide Torch service\n\nAllows Torch and any camera to coexist peacefully. When torch is active\nand a camera is opened, the torch will be first shut down, and the\ncamera will be allowed to continue opening, instead of displaying\n\"Cannot connect to camera.\"\n\nAlso a squash of the following commits:\n\n    add framework torch service\n\n    Change-Id: I0c7a055b33fdebe697f23d207b20408e06eb74a8\n    Signed-off-by: Roman Birg <roman@cyngn.com>\n    Fully fix interaction between torch and camera usage.\n\n    For doing this, two things are necessary:\n    - The torch shutdown needs to be synchronous, so that the torch app has\n      a chance to release the camera before the camera app tries to use it.\n    - The torch service needs to track camera usage, so that it can notify\n      the torch app if a camera is busy.\n\n    Change-Id: I521091d255ff4c251d97a0e8d65c9d2a80b9dae4\n\n    Fix camera usage tracking.\n\n    When a Camera object is finalized, it notifies the torch service that\n    it's no longer using the camera. This call used to not check whether the\n    caller actually is still using the camera and called release() before,\n    so depending on timing of the finalizer, it could happen that e.g. the\n    camera app released the camera user record of the torch app, leading to\n    the torch usage not being detected on next usage of the camera app.\n\n    Fix that by checking whether the caller of onCameraClosed() actually\n    owned the camera prior to releasing the record.\n    Also fix synchronization between accesses.\n\n    Change-Id: Ic01cbc3c89ab8d855e4613bfa1b2f548de919b73\n\n    frameworks: extend TorchService to be able to handle sysfs torch config\n\n    Some devices are still using a sysfs node to control the torch. Let's\n    support those configurations and properly shut the torch down.\n\n    Change-Id: I5fa1cccdcffad26dbfef4b2ee0eafe1218a5308b\n    Signed-off-by: Roman Birg <roman@cyngn.com>\n\n    frameworks: move TorchService to new services location\n\n    Change-Id: I392f37dfefe41686388811069999eb031f7eb92c\n    Signed-off-by: Roman Birg <roman@cyngn.com>\n\nChange-Id: I37a265ec98391936a6c19e8bcdf8da1efb57d45d\nSigned-off-by: Roman Birg <roman@cyngn.com>\n\nConflicts:\n\tcore/java/android/app/ContextImpl.java\n\tcore/res/AndroidManifest.xml\n\tcore/res/res/values/cm_strings.xml\n\tpackages/SystemUI/src/com/android/systemui/statusbar/phone/KeyguardBottomAreaView.java\n\tpackages/SystemUI/src/com/android/systemui/statusbar/phone/PhoneStatusBar.java","distinct":true,"url":"https://api.github.com/repos/liquid0624/android_frameworks_base/commits/ca103170e7cc42376d29413133cc384af0aa13ee"},{"sha":"1c7261bf98971e157fab59679591502aea4b71f4","author":{"email":"a1e17a20e93e5da710685444df3ad038ac66e2c9@rom1v.com","name":"Romain Vimont (®om)"},"message":"Avoid duplicate call to onLoadFinished()\n\nWhen a loader is initialized in Fragment#onActivityCreated(Bundle), then\nLoadersCallback#onLoadFinished() was called twice on device orientation\nchange:\n - once during fragment start();\n - once during loader finishRetain().\n\nReported as bug 63179:\nhttps://code.google.com/p/android/issues/detail?id=63179\n\nThis commit prevents to call onLoadFinished() when the data has already\nbeen delivered.\n\nChange-Id: I893013049f819dd5543a8079ce9d8025a5fdb2f1","distinct":true,"url":"https://api.github.com/repos/liquid0624/android_frameworks_base/commits/1c7261bf98971e157fab59679591502aea4b71f4"},{"sha":"c16f9883ca13be115447d919346e3c612d89e7f8","author":{"email":"1764441d64441ae9c2c2810d604764d28c91425a@gmail.com","name":"Sean Barbeau"},"message":"Keep deleteIntent when copying Notification attributes\n\nEnsures that any previously registered deleteIntent is retained after a call\nto Notification.setLatestEventInfo().\n\nCurrently, a call to setLatestEventInfo() effectively erases a previously\nregistered Notification.deleteIntent, which results in the app never being\nnotified when the user dismisses the notification.\n\nThis issue is described in detail in #73720:\nhttps://code.google.com/p/android/issues/detail?id=73720\n\nChange-Id: Ie58bf6a310058d40beb0d1af6506e9e1f4324b37\nSigned-off-by: Sean Barbeau <sjbarbeau@gmail.com>","distinct":true,"url":"https://api.github.com/repos/liquid0624/android_frameworks_base/commits/c16f9883ca13be115447d919346e3c612d89e7f8"},{"sha":"6d7b5bb236b1b0ecd8df661940fa230aa6b7e3d4","author":{"email":"f16bed56189e249fe4ca8ed10a1ecae60e8ceac0@mortimer.me.uk","name":"Sam Mortimer"},"message":"[1/2] frameworks/base: Battery and Notification Lights\n\nPS2: *) Add back a few missing pieces\n     *) Do not clear light state in onPanelRevealed(),\n        update lights on ACTION_SCREEN_ON instead\n\nPS3: *) Wrap long lines\n     *) Disable config_multiColorNotificationLed by default\n     *) Revert config_defaultNotificationLedOff\n        from 1000 back to AOSP default of 2000\n\nPS4: *) Clear lights in onPanelRevealed() if\n        keyguard is not active.\n\nPS5: Coding style tuning\n\nPulled together from:\n\nAuthor: DvTonder <david.vantonder@gmail.com>\nAuthor: Ricardo Cerqueira <cyanogenmod@cerqueira.org>\nDate:   Mon Nov 4 00:57:51 2013 +0000\nFramework: Port CM9 features to CM10\nChange-Id: Ibd63116df90b06f6ce6adb8a0343059bbb999bfb\n\nAuthor: Pawit Pornkitprasan <p.pawit@gmail.com>\nDate:   Sun Dec 8 15:24:41 2013 +0700\nBatteryService: fix FC on boot until battery stat is present\nupdateLightsLocked() can be called from CM's added SettingsObserver\nwhen battery stat is not present, causing an FC and a loop until\nbattery stat is present.\nChange-Id: Ic4438fe50e98f1aa05ae1d0d26240bf9410fd92f\n\nAuthor: Sam Mortimer <sam@mortimer.me.uk>\nDate:   Tue Dec 31 16:22:05 2013 -0800\n[2/2] Framework: instant led test\nAdds support a new notification extra boolean\nEXTRA_FORCE_SHOW_LIGHTS.  Used by settings\nnotification light picker to force lights on\nwhen the screen is on.\nChange-Id: If0a42d32b28fe8c02ef5f7dd148db7eb478fac17\n\nAuthor: Danny Baumann <dannybaumann@web.de>\nDate:   Wed Apr 24 11:09:55 2013 +0200\nAllow creating custom dialogs in DialogPreference.\nThis allows creating non-AlertDialogs while still using the click and\nstate handling of DialogPreference.\nChange-Id: I54fd7d6d6b9f6a49fef1ae95e0178838b3edfa56\n\nAuthor: Michael Bestas <mikeioannina@gmail.com>\nDate:   Mon Aug 18 04:56:28 2014 +0300\nAdd support for single color notification LED (1/2)\nChange-Id: I367af77036da9e87c6dd0df552ce4c56d945a44d\n\nChange-Id: I564fdb6ca6c5bbcf890afa4b9a2f9fa7bf8b9604\n\nConflicts:\n\tcore/res/res/values/cm_arrays.xml\n\tcore/res/res/values/symbols.xml","distinct":true,"url":"https://api.github.com/repos/liquid0624/android_frameworks_base/commits/6d7b5bb236b1b0ecd8df661940fa230aa6b7e3d4"},{"sha":"862e990cc38d3a0c0bc20a795d0f761ae9e4a0e3","author":{"email":"f070c521785a59dccb0378122e90643a6b96e5ef@lge.com","name":"jinchul.kim"},"message":"keep mDefaultDisplayMetrics from concurrent modification.\n\ngetDisplayMetricsLocked can be invoked concurrently, it can cause\nconcurrent issues like ArrayIndexOutOfBoundsException.\n\nChange-Id: I816eb4b276e7872c8a1964b6389a6f1238f51e48\nSigned-off-by: Jinchul Kim <jinchul.kim@lge.com>","distinct":true,"url":"https://api.github.com/repos/liquid0624/android_frameworks_base/commits/862e990cc38d3a0c0bc20a795d0f761ae9e4a0e3"},{"sha":"00fc56e6915c697c78c9453bf1cf1b86f23597de","author":{"email":"554b754803887f12488421a109f1aee8970ec7b1@gmail.com","name":"You Kim"},"message":"NPE in SearchManager.triggerSearch\n\nmAssociatedPackage field is never initialized and cause NPE.\n\nChange-Id: Ibf0d44b2170b7cbfe4a883008254a086e03579c5","distinct":true,"url":"https://api.github.com/repos/liquid0624/android_frameworks_base/commits/00fc56e6915c697c78c9453bf1cf1b86f23597de"}]}