)]}' { "commit": "3a2bb594df4b48c6afb1f029041dd6db0735de58", "tree": "6459344ce70a011cbf3352b6ebc872e808a0a93d", "parents": [ "9db7964834694e10ce0945e17ac7fefc066d8deb" ], "author": { "name": "Tao Bao", "email": "tbao@google.com", "time": "Thu Feb 25 12:38:53 2016 -0800" }, "committer": { "name": "Tao Bao", "email": "tbao@google.com", "time": "Wed Mar 02 23:23:32 2016 -0800" }, "message": "uncrypt: Communicate via /dev/socket/uncrypt.\n\nWe used to rely on files (e.g. /cache/recovery/command and\n/cache/recovery/uncrypt_status) to communicate between uncrypt and its\ncaller (i.e. system_server). Since A/B devices may not have /cache\npartitions anymore, we switch to socket communication instead.\n\nWe will keep the use of /cache/recovery/uncrypt_file to indicate the OTA\npackage to be uncrypt\u0027d though. Because there is existing logic in\nShutdownThread.java that depends on the existence of the file to\ndetect pending uncrypt works. This part won\u0027t affect A/B devices without\n/cache partitions, because such devices won\u0027t need uncrypt service (i.e\nthe real de-encrypt work) anyway.\n\nBug: 27176738\nChange-Id: I481406e09e3ffc7b80f2c9e39003b9fca028742e\n", "tree_diff": [ { "type": "modify", "old_id": "2a32108a3888c3d9fde1963abfd8ef61074e5462", "old_mode": 33188, "old_path": "uncrypt/uncrypt.cpp", "new_id": "e783b9e7a2a7250ba87b460432e1f890334818b9", "new_mode": 33188, "new_path": "uncrypt/uncrypt.cpp" }, { "type": "modify", "old_id": "d5d803b9f9978d3ada47aacefe7786ddbfca729d", "old_mode": 33188, "old_path": "uncrypt/uncrypt.rc", "new_id": "52f564eb6cf8885e83049b0a2216b3c637705cbe", "new_mode": 33188, "new_path": "uncrypt/uncrypt.rc" } ] }