make build uses 'shared' cert in build/make/target/product/security/.
If LatinIME APK built with AndroidStudio doesn't use the same signing
cert, then you cannot install the APK into AOSP image, which is not
convenient.
With this CL, AndroidStudio build also uses the same signing cert.
Note that shared.keystore was built as follows.
$ openssl pkcs8 -inform DER -nocrypt \
-in build/make/target/product/security/shared.pk8 \
-out shared.pem
$ openssl pkcs12 -export \
-in build/make/target/product/security/shared.x509.pem \
-inkey shared.pem -out shared.p12 \
-password pass:android -name AndroidDebugKey
$ keytool -importkeystore -deststorepass android \
-destkeystore shared.keystore -srckeystore shared.p12 \
-srcstoretype PKCS12 -srcstorepass android
Fix: 110741422
Test: made sure that the APK built with Android Studio can be
installed to an AOSP build
Change-Id: I471a87e190b15ff02bb06849e4660ed7898897a5
This should be the most convenient way for both make build and Android
Studio build to share the same version code.
Bug: 110741422
Test: tapas LatinIME LatinIMETests arm64 userdebug && make -j
Change-Id: I35f850c392553b2640a4c3c7398441ac28e90eca
Basically Android Studio does want targetSdkVersion to be specified in
build.gradle rather than AndroidManifest.xml. To make both make build
and Android Studio build happy, this CL splits <uses-sdk /> from the
main AndroidManifest.xml to a different file and let them merged in
make build.
There should be no behavior change.
Bug: 110741422
Test: Manually verified that there is no difference in
AndroidManifest.xml in the APK.
Change-Id: Ib673bca5a31b2f95329c9310a127ec0701bd8fdc
PersonalDictionaryLookup has never been used. Usually proguard can
remove this class but it also makes it difficult to run unit tests.
We should just remove this unused class.
Bug: 111164993
Test: compile
Test: No new test failure
Change-Id: I732db94cb3aac4ed9c6b5954679b896334a12a9c
This layout file was copied from Settings app but in LatinIME it has
never been used. Also, android:onClick attributes in that layout file
are pointing to non-existing method in LatinIME, which causes lint
warnings.
Since tihs files has never been used in LatinIME, there should be no
user-visible behavior change.
Bug: 110757803
Test: tapas LatinIME && make -j
Change-Id: Ib51744979df333ac432aefc54ef7d0f413cf6161
This is a preparation to deprecate frameworks/opt/inputmethodcommon
repository.
Currently repository 'inputmethodcommon' is used only from LatinIME.
Having such a repository only for one project is overkill. Also, to
add gradle build support to LatinIME project, it would be much easier
LatinIME didn't have such a dependency.
This CL mechanically copies files in 'inputmethodcommon' repository to
'LatinIME' repository. In theory there should be no behavior change.
Bug: 110741521
Test: tapas LatinIME && make -j
Change-Id: I3fabb038be9a944dcd9ef79ffcc89800a5f0bf5a
This CL a logical revert of a previous CL [1], which separated Java
files into common ones and overridable ones. Now that that overriding
concept is no longer used, there is no need to keep having separate
directory structure.
[1]: Ic734bd4d20aa050c688a3158b1a382ae0ac18991
fb74ab15c1343084740d65ef8744cad33a678e82
Fix: 79323502
Test: make -j aosp_taimen-userdebug && make -j
Test: tapas LatinIME && make -j
Change-Id: I2090bc25d18e6d4f24e91c2cbfe832755cbb4e8f
