Yohei Yukawa 69ceec9045 Re-introduce <uses-sdk> to the main AndroidManifest.xml ... This logically reverts my previous CL [1], which moved <uses-sdk /> from AndroidManifest.xml to AndroidManifest_SdkVersion.xml, which was later accidentally removed during Android.bp migration [2]. Since gradle support in LatinIME is still experimental and not used in official build, it is OK to keep it broken for a while. A more important problem right now is letting LatinIME target API 28. As the first step to let LatinIME target SDK 28, <uses-sdk> will be revived in AndroidManifest.xml [1]: Ib673bca5a31b2f95329c9310a127ec0701bd8fdc 9cd42f39eb [2]: Ib8867d3b74f09fc1d9f95adc9a49a81ac0f7f054 22ebec6e2e Bug: 110741422 Bug: 119489995 Test: manually verified that LatinIME still is functional Change-Id: I8b04caa56fe2431c07e076fb6f97c560d5da8838		2018-11-13 13:49:23 -08:00
..
res	Merge "Import translations. DO NOT MERGE"	2018-11-10 15:02:17 +00:00
src/com/android	Merge "Fix dicttool build" am: a92d0f9262 am: 438a303732	2018-10-31 09:24:08 -07:00
Android.bp	Convert to Android.bp	2018-10-31 21:49:02 -07:00
AndroidManifest.xml	Re-introduce <uses-sdk> to the main AndroidManifest.xml	2018-11-13 13:49:23 -08:00
MODULE_LICENSE_APACHE2
NOTICE
proguard.flags	Create a new KeyboardLayout class to represent the layout.	2015-01-30 17:24:09 -08:00
shared.keystore	Let Android Studio use 'shared' cert to build APK	2018-07-25 18:08:35 -07:00