{"push_id":959647249,"size":14,"distinct_size":14,"ref":"refs/heads/mm6.0","head":"7a36b94c4c68fa23d1b5a073036d2363ec420bcd","before":"af955d423c4508048248be8ed3f028a8cc463c23","commits":[{"sha":"7824ab0d9b6019317d0534b28e6de43c50aa3c4b","author":{"email":"c96a8d0c6b1245332496ba67a3fe2b20b0aebd52@htc.com","name":"riddle_hsu"},"message":"Fix wrong focused stack if there are finishing tasks.\n\nWhen there is more than one finishing tasks, topTask()\nmay not match the current finishing task to adjust.\n\nhttps://code.google.com/p/android/issues/detail?id=192090\n\nA sample step:\n1.Launch task T from home.\n2.Press home key.\n3.Launch task A from home.\n4.A launches task B.\n5.B finishes self and A finishes onResume.\n\nWhen adjustFocusedActivityLocked is called from A's finish,\nboth A and B are finishing and B has not destroyed yet,\nso the top task is B that is not satisfy the original condition\nto change focused stack. Then it still uses application stack\nto resume, that is T.\n\nAfter A completed destroy: activityDestroyedLocked ->\nremoveActivityFromHistoryLocked will check if it is over home.\nSo T only shows awile then return to home.\n\nTo handle this case, still check the behind tasks when the\nadjusting task is not top task. If the task is alive, then\nit stays in current stack, and if there is a finishing task\nover home, then it should go home.\n\nFor above example, B is finishing (getTopActivity() will be\nnull) but it is not over home, then check the next which is A.\nAnd because A is over home, then it can adjust to home stack.\n\nChange-Id: Id5d6d58ccdac38bdbebba6df50a063b78182cd4f","distinct":true,"url":"https://api.github.com/repos/Infinitive-OS/platform_frameworks_base/commits/7824ab0d9b6019317d0534b28e6de43c50aa3c4b"},{"sha":"75d3f9d9556c042d79eb4f27827f6900e72a3f29","author":{"email":"5a1adda7246facf4a2c013c871ba72d7cbbb29fc@sonymobile.com","name":"Tobias Lindskog"},"message":"Skip ANR for processes that have been killed\n\nIf a controller is attached and decides to kill a process after an ANR,\nother ANR reports for that app that are queued up won't be handled until\nafter the app has died.  This can create a report without the relevant\ncallstacks because the app is dead by the time the traces are dumped.\nSince the trace file is global, the traces recorded for the first ANR\nare overwritten, leaving us with no clue as to what happened.\n\nAfter the app has been killedByAm, it is not interesting to handle ANRs\nfor that app until it is started again, so killedByAm can be used to\nfilter out these spurious reports.\n\nChange-Id: I34ba790f6d29d563c819dc2f6ac71a3c8955bb76","distinct":true,"url":"https://api.github.com/repos/Infinitive-OS/platform_frameworks_base/commits/75d3f9d9556c042d79eb4f27827f6900e72a3f29"},{"sha":"c3b6f779791a8220ddb09da91cd15edbeb1c3970","author":{"email":"7fb1af48ad3f9a487e1291e1f9cb0d9f90b4f222@htc.com","name":"louis_chang"},"message":"[ActivityManager] Bring up Service if not schedule to restart\n\nSymptom:\n\nA Service which has scheduled to restart, the\nServiceRecord.restartDelay will be set a value which is\ngreater than 0.\n\nAfter the Service is restarted, the Service process got\nkilled again while client application invoked\nunbindService(), there may have chances that results\nDeadObjectException when schedule UnbindService to the\nService process  in removeConnectionLocked().\n\nIn that case, the Service would failed to scheduled restart.\n(serviceProcessGoneLocked() -> serviceDoneExecutingLocked()\nwith finishing = true)\n\nAnd the Service will unable to bring up afterward\nwhenever client applications invoked bindService()\nbecause r.restartDelay > 0.\n\nSolution:\nBring up Service if it was also not in the restarting list\n\nChange-Id: I28b023f0ce36e496bd6b0c69fe71121a083be83b","distinct":true,"url":"https://api.github.com/repos/Infinitive-OS/platform_frameworks_base/commits/c3b6f779791a8220ddb09da91cd15edbeb1c3970"},{"sha":"78c759c7a3c0897551345f142c9baa43325e4dd0","author":{"email":"15fdf4d02bce6e5a1b7b4f39cc2a247185c91ef1@htc.com","name":"kenzyun_chen"},"message":"force to remove window for BinderDied case\n\nSymptom: some Exiting window still exists for a long time\nRoot Cause: unknown\nSolution: force to remove window for BinderDied case\n\nChange-Id: Ib2ecbcc7beb581a3ffe451a5b9d650389b43230d","distinct":true,"url":"https://api.github.com/repos/Infinitive-OS/platform_frameworks_base/commits/78c759c7a3c0897551345f142c9baa43325e4dd0"},{"sha":"0a89e62b909faa3a67f12d8689d833f83f470769","author":{"email":"ab48234c6c2c36125fbe98ba5c77d2a71361801f@htc.com","name":"rhed_jao"},"message":"Stop feeding restore engine if it's already in failed state and exit.\n\nb/24518516\n\nmodified:   services/backup/java/com/android/server/backup/BackupManagerService.java\n\nChange-Id: I371b7e87fa7ba408b1255263c6d23821496916a2\nSigned-off-by: rhed_jao <rhed_jao@htc.com>","distinct":true,"url":"https://api.github.com/repos/Infinitive-OS/platform_frameworks_base/commits/0a89e62b909faa3a67f12d8689d833f83f470769"},{"sha":"d77f42524844dd2468291270fe1e704271133d48","author":{"email":"83435b903d460e70c218b4c2f0b40e8df34a584e@ck-telecom.com","name":"guotao.deng"},"message":"We should notify the foreground activity changes immediately.\n\nFor example, when device bootup, Launcher is foreground activity,\nbut NFC do not register the listener yet when AMS notify the changes.\nSo NFC cannot use beam when device just bootup.\n\nChange-Id: I55ad7947ecbfbbf7c30dabd3b530e5b011b8cb65","distinct":true,"url":"https://api.github.com/repos/Infinitive-OS/platform_frameworks_base/commits/d77f42524844dd2468291270fe1e704271133d48"},{"sha":"724069989134700638f045b98c7eb1eb1582c92d","author":{"email":"e93baac950f19c7ac011a8ef5649da421f4690b8@google.com","name":"Tao Bao"},"message":"Clean up the uncrypted OTA package on bootup.\n\nAn OTA package needs to be uncrypted before rebooting into recovery if\nit sits on an encrypted /data partition. Once uncrypt gets started, we\ncannot re-run it on the package again. Because the file may have been\nfully or particially uncrypted and we may end up with a corrupt file\nunder recovery. Always clean up the package when the device boots into\nthe normal system to avoid that.\n\nBug: 24973532\nChange-Id: I91682c103d1f2b603626c4bf8d818bced71e3674","distinct":true,"url":"https://api.github.com/repos/Infinitive-OS/platform_frameworks_base/commits/724069989134700638f045b98c7eb1eb1582c92d"},{"sha":"25a5ad1a66703732ef47dea0acca80faf1d48998","author":{"email":"825ebca5d33ba68cf4786bdb45f47232ab7b2a05@sonymobile.com","name":"Koji Fukui"},"message":"Avoid a double decrease of reference counter for unstable provider\n\nIn some APIs unstable provider is released twice.\nUnexpected release of unstable provider makes the reference counter\nfor unstable provider invalid state and it causes application crash.\n\nThis change avoids unexpected double decrease of reference counter\nfor unstable provider by setting null to prevent extra release\nin finally block.\n\nChange-Id: Ie2985c316ffcb6a9db7570c46347035c24d226af","distinct":true,"url":"https://api.github.com/repos/Infinitive-OS/platform_frameworks_base/commits/25a5ad1a66703732ef47dea0acca80faf1d48998"},{"sha":"6a079f8d8911de4c4341efb97103c1cccf3ec924","author":{"email":"5a953b41e7c6a45037091dd5a4bb8527940ed2aa@lge.com","name":"Dohyun Lee"},"message":"Assign more reasonable width and height of a window surface\n\nWhen the surface of a window is created during relayoutWindow,\nthere is the case that the width and height of the surface are\nnot given appropriately, e.g. the staring windows.\nIn this case, the width and height are set to 1, which cause\nresizing the size of the surface during setSurfaceBoundariesLocked.\nSince setting the size of a surface is processed synchronously\nin the SurfaceFlinger, there is usually a few milliseconds\ndelay (up to 1 vsync interval) when we launch an application.\n\nTo remove such cases, this patch assign the width and height\nmore reasonably like below:\n\n 1. If FLAG_DRAWS_SYSTEM_BAR_BACKGROUNDS is set then assign\n    the size of the display we can use.\n   (i.e. DisplayInfo.logical[Width|Height])\n\n 2. Otherwise, assign the width and height of the portion of\n    the display that is available to applications.\n    (i.e. DisplayInfo.app[Width|Height])\n\nChange-Id: Ie8265b9ff0fdb6ecc4577687935adf7cfb4439ad\nSigned-off-by: Dohyun Lee <dohyun.lee@lge.com>","distinct":true,"url":"https://api.github.com/repos/Infinitive-OS/platform_frameworks_base/commits/6a079f8d8911de4c4341efb97103c1cccf3ec924"},{"sha":"ea2ed8d7c3df95a0181d758871b08400a5ae1681","author":{"email":"7910fb7fffd740ece1bd23d38783c6a42d2cd4ea@gmail.com","name":"Gabriele M"},"message":"PowerManager: don't pass NULL pointers to power HAL\n\nSending a NULL pointer here is likely going to cause system crashes and\ndoesn't seem to be the correct thing to do, a value equals to zero is\nno different from the others.\n\nChange-Id: I2678387715b3ec1d12627abe2dd5d3e189579dc4","distinct":true,"url":"https://api.github.com/repos/Infinitive-OS/platform_frameworks_base/commits/ea2ed8d7c3df95a0181d758871b08400a5ae1681"},{"sha":"cca3de96dff27ebb0d173e038fc51471c75ad94a","author":{"email":"c6833d607636f16ca49565dfcb7c970394ab64f3@codeaurora.org","name":"Rama Vaddula"},"message":"Remove opaque check in preparing dirty region\n\nSince preserve swap is enabled, we need to clear the color buffer\nwhen the scissor rect is prepared for a new process. This prevents\ngarbage being present from the previous process in the color buffer.\n\nCRs-Fixed: 549755\n\nChange-Id: Icd12ae388077b8c9ed329c37314e896500078543","distinct":true,"url":"https://api.github.com/repos/Infinitive-OS/platform_frameworks_base/commits/cca3de96dff27ebb0d173e038fc51471c75ad94a"},{"sha":"2b3697a7c793180d8a37d97eae2863f5603e1a6f","author":{"email":"01fb3892f39957945220431e7409156544d2f041@gmail.com","name":"AdrianDC"},"message":"MountService: Prevent NPE with DropBoxManager\n\n * \"java.lang.NullPointerException: Attempt to invoke virtual\n    method 'void android.os.DropBoxManager.addText(java.lang.String,\n    java.lang.String)' on a null object reference\"\n\nChange-Id: I418ba99caa4f55b184fabee4ad610ca3e5e7c66f\nSigned-off-by: AdrianDC <radian.dc@gmail.com>","distinct":true,"url":"https://api.github.com/repos/Infinitive-OS/platform_frameworks_base/commits/2b3697a7c793180d8a37d97eae2863f5603e1a6f"},{"sha":"6423913e9306039695779b704b5cb129adf35491","author":{"email":"c76ad1a5417d5e5ec6068289c7ca2032944e4216@google.com","name":"Phil Burk"},"message":"USB MIDI: Fix race condition that causes intermittent connections.\n\nPlugging in a USB MIDI device normally works.\nBut occasionally the device is not seen due to a race condition.\nThis code retries until the device is ready.\n\nChange-Id: Ifba9c9678e6be0c3d139f3467f895307096a2ad8\nSigned-off-by: Phil Burk <philburk@google.com>","distinct":true,"url":"https://api.github.com/repos/Infinitive-OS/platform_frameworks_base/commits/6423913e9306039695779b704b5cb129adf35491"},{"sha":"7a36b94c4c68fa23d1b5a073036d2363ec420bcd","author":{"email":"1a8755ca18bea68fa43e2fa2d5d89fde446d3151@cyngn.com","name":"Tom Marshall"},"message":"storage: Do not notify for volumes on non-removable disks\n\nChange-Id: Ia353ab43fbeba42d7d9c21d926f638f550a3dbbe","distinct":true,"url":"https://api.github.com/repos/Infinitive-OS/platform_frameworks_base/commits/7a36b94c4c68fa23d1b5a073036d2363ec420bcd"}]}