{"push_id":1905913751,"size":8,"distinct_size":2,"ref":"refs/heads/android-7.1","head":"8a7c1092448b8bafce161e8347d69094c5664a29","before":"08c78b3ac40c9f4704bccbc465145a555f1ddd5b","commits":[{"sha":"50c8a78c5262dfd1165992d570b6e3bbdd13ea35","author":{"name":"lambdadroid","email":"2e02d58a7f42fcc18a7df6b86102bb8ffad35315@gmail.com"},"message":"Load serial number from system property when setting device ID\n\nOn some devices (e.g. ASUS Zenfone) the serial number of the device\nis stored in a file in the /factory partition. Consequently, the only\nway to load it is using a user space application during the init\nprocess, and to update the ro.serialno system property.\n\nIn most places, TWRP already uses the system property to get\nthe serial number of the device. However, when generating the\ndevice ID used for the backup folder name it checks the boot\ncommand line directly. On these devices, the serialno is not\nincluded on the command line.\n\nCheck the ro.serialno system property additionally to make\nsure we get the correct one on these devices.\n\nChange-Id: I4a2eeca883f38fdaeb1209507fd8ebe44b1b04a0","distinct":true,"url":"https://api.github.com/repos/me176c-dev/bootable_recovery/commits/50c8a78c5262dfd1165992d570b6e3bbdd13ea35"},{"sha":"05adeabda651acd224b0d979b12e2f31d17e96f0","author":{"name":"lambdadroid","email":"2e02d58a7f42fcc18a7df6b86102bb8ffad35315@gmail.com"},"message":"minuitwrp: drm: Correct mapping of DRM_FORMAT_RGB565\n\nChange-Id: Ibbea79ce6c57452207ccf1137afacefaab3c4b4a","distinct":false,"url":"https://api.github.com/repos/me176c-dev/bootable_recovery/commits/05adeabda651acd224b0d979b12e2f31d17e96f0"},{"sha":"54e5dbd47cefa7d70d34d86e80ce6c441cc39f14","author":{"name":"lambdadroid","email":"2e02d58a7f42fcc18a7df6b86102bb8ffad35315@gmail.com"},"message":"minuitwrp: drm: Use mmap64 for dumb buffers on 32 bit platforms\n\nThe DRM API may return offsets bigger than 32 bit, causing the\ncall to mmap to fail on 32 bit platforms. Use mmap64 to handle\nthem properly.\n\nChange-Id: I426795d6dddff19f6452011c15398d354bf91295","distinct":false,"url":"https://api.github.com/repos/me176c-dev/bootable_recovery/commits/54e5dbd47cefa7d70d34d86e80ce6c441cc39f14"},{"sha":"3871963aa547c8b74269fe6324394f796eb67679","author":{"name":"lambdadroid","email":"2e02d58a7f42fcc18a7df6b86102bb8ffad35315@gmail.com"},"message":"minuitwrp: drm: Await completion of last page flip\n\nIf another page flip is scheduled before the last one has been\ncompleted, the DRM API will return EBUSY, causing TWRP to\ncrash. To avoid this, we can attach an event handler that is called\nwhen the page flip has been completed.\n\nWe wait for completion of the page flip directly after scheduling\nit. Normally, this is not necessary, however with the current\ndouble-buffering the old buffer may be modified by the renderer\nbefore the flip to the new buffer is completed.\n\nA better solution would be to use tripple-buffering, but this is\naddressed in a later commit.\n\nChange-Id: Ic4cfe28bdeaa60da76cf121601c68a2077a081cc","distinct":false,"url":"https://api.github.com/repos/me176c-dev/bootable_recovery/commits/3871963aa547c8b74269fe6324394f796eb67679"},{"sha":"9477863b6067eba51cc3609a7b35822f75e08ed3","author":{"name":"lambdadroid","email":"2e02d58a7f42fcc18a7df6b86102bb8ffad35315@gmail.com"},"message":"minuitwrp: drm: Delay enabling CRTC until we have rendered a frame\n\nWhen drm_blank was called to re-enable the display, it set the\ndisplay to the current buffer. However, at this point the frame\nwas not rendered yet, which means you could slowly see it\nrendering from top to bottom, instead of the full frame directly.\n\nOne option to solve this is to re-enable the display with the frame\nwe have rendered last, and wait until we can flip to next frame\n(when it is ready). Especially for TWRP this looks weird though:\nfor a short time it displays the old, unlocked screen before jumping\nto the screen look after a second.\n\nInstead, we delay enabling the display until we have a frame ready\nto be rendered. That means that the display will react slightly\nslower after pressing the power button, but at least the correct\nscreen is shown.\n\nChange-Id: Iff6673076d585535f889ef867b89b1627e7fc1b8","distinct":false,"url":"https://api.github.com/repos/me176c-dev/bootable_recovery/commits/9477863b6067eba51cc3609a7b35822f75e08ed3"},{"sha":"dadd8d922da6810b280ee601914ef27c7f05b39b","author":{"name":"lambdadroid","email":"2e02d58a7f42fcc18a7df6b86102bb8ffad35315@gmail.com"},"message":"minuitwrp: drm: Render in software memory buffer\n\nAs for the other graphics implementations, rendering is very slow\nwhen rendering directly to the mapped memory. Rendering is much\nfaster if we first use an extra buffer and then use memcpy to copy\nit to the actual surface.\n\nAnother advantage is that we no longer have to wait for the page\nflip to complete before we can start rendering. The old surface\nbuffer isn't modified until we are ready to schedule the next\nsurface.\n\nChange-Id: I5d8d8c26fc3d3bb704f7597ffc85a456ebd2cd3f","distinct":false,"url":"https://api.github.com/repos/me176c-dev/bootable_recovery/commits/dadd8d922da6810b280ee601914ef27c7f05b39b"},{"sha":"59c77f7f6f4a1ef90de4a36fd25ca9bef0a861fe","author":{"name":"lambdadroid","email":"2e02d58a7f42fcc18a7df6b86102bb8ffad35315@gmail.com"},"message":"minuitwrp: drm: Fix drm_destroy_surface\n\nDumb buffers need to be freed using DRM_IOCTL_MODE_DESTROY_DUMB.\nThe old code was incorrectly using the GEM specific call instead\nof the one for dumb buffers.\n\nChange-Id: I6a4d8f54f3c1289ddb487ca6929d27fc31f71c37","distinct":false,"url":"https://api.github.com/repos/me176c-dev/bootable_recovery/commits/59c77f7f6f4a1ef90de4a36fd25ca9bef0a861fe"},{"sha":"8a7c1092448b8bafce161e8347d69094c5664a29","author":{"name":"lambdadroid","email":"2e02d58a7f42fcc18a7df6b86102bb8ffad35315@gmail.com"},"message":"Merge branch 'drm-fix' into android-7.1","distinct":true,"url":"https://api.github.com/repos/me176c-dev/bootable_recovery/commits/8a7c1092448b8bafce161e8347d69094c5664a29"}]}
{"actor":{"display_login":"lambdadroid"}}