{"push_id":926020102,"size":1,"distinct_size":1,"ref":"refs/heads/aosp","head":"58b885c6fae7c9bbb7970f7ac1a7b0e866aad04d","before":"7336a40130564cd2c53f20dbe3dc342278f4553a","commits":[{"sha":"58b885c6fae7c9bbb7970f7ac1a7b0e866aad04d","author":{"email":"90b51f8a5079017e81711ae9317c35b0575b34e1@gmail.com","name":"Christopher R. Palmer"},"message":"intel: Pick the best ABI based on number of libs, not just priority\n\nThe normal package loading will open the APK and find the highest\npriority ABI that contains one or more native libraries.\n\nThis works well for 64-bit vs. 32-bit but doesn't work very well\nfor ARM vs. Intel ABIs.  There are many broken apps in the market\nwhich fail to run when installed as x86.\n\nI believe that there are so many apps because an app that doesn't\nitself have native x86 libs but imports a 3rd party lib that does\nsupport x86 will end up installin the x86 libs for the support\nlibrary which fools the package installer.\n\nAs a simple heuristic, pick the ABI that contains the most shared\nlibraries.  That works around the common case of missing the\napp's own shared libraries.\n\nNote: the consequences of picking incorrectly are actually quite\nsmall since the app should still run, although it will run\nless efficiently because it is emulated.\n\nNote: if two ABIs have the same number of libs, we pick the higher\npriority one as a tie-breaker.\n\nChange-Id: Ie4880810f46875869ce054b3c46acac64b953996","distinct":true,"url":"https://api.github.com/repos/AOSP-Zenfone2/frameworks_base/commits/58b885c6fae7c9bbb7970f7ac1a7b0e866aad04d"}]}