missytake/fdroiddata
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Clarification of dictionary provider conflict

Browse source
This commit is contained in:
David Black 2014-01-18 14:10:17 +00:00
parent 87976f9c0e
commit b2acbe11ea
1 changed files with 6 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

16
metadata/com.android.inputmethod.latin.txt
View file

@ -18,10 +18,9 @@ in the repository but they'd need to be compiled.
Of course, you can't install this if you have a ROM that already has
the com.android.inputmethod.latin package installed.
You could build it yourself with a different package name, but on Android 4.3
it still couldn't be installed as a user app, unless the original allowed
the dictionary provider to be exported, which is unlikely.
So, you'd have to remove the original from /system/app (and dalvik-cache)
You could build it yourself with a different package name, but you might need
to change the authority string for dictionary packs too; this may be fixed in the next builds.
Otherwise, you'll have to remove the original from /system/app (and dalvik-cache)
via root, before installing this.
.
@ -76,12 +75,9 @@ Maintainer Notes:
Note that, like other AOSP apps, there are now special tags with 'sdk' in them;
not sure what the difference is.
Possible tweaks:
Could compile with dictionary provider exported to allow access from other apps, but
of course it's only relevant if installing other similar packages ''after'' this; see,
https://developer.android.com/guide/topics/manifest/provider-element.html
sed -i 's/exported="false"/exported="true"/g' AndroidManifest.xml && \
Todo for next versions:
Change authority string in res/values/dictionary-pack.xml, à la
android:authorities="@string/authority" to allow for installation on top of other apps.
Split up packages based on user dictionaries.
.