Unfortunately, what has been proposed on the previous page (the ban starting services in xml) is no longer relevant covsem - "valiant" yandeksovtsy stuffed new slag type "com.yandex.promolib.service.YPLService" in the program - the cards that metro .
There is a proposal to turn off services and receivers directly in the manifest apk - AndroidManifest.xml. Just do not allow the launch services and receivers, adding key android: enabled = "false", and check that the key is not duplicated in the row - otherwise apk not meet. Putting apk any software, such APK-Multitiool.
Next, pull out of the project compiled the AndroidManifest.xml, pushes it to the original file and sign apk (why so - because the cards, for example, normally do not start after assembly, even without changes - perhaps there is a check.)
Samples:
AndroidManifest.xml
For services:
<service android: name = "com.yandex.promolib.service.YPLService"android: enabled = "false"android: permission = "com.yandex.promolib.permission.ACCESS_START_SVC" android: process = ": Promolib">
And for the receivers:
<receiver android: name = "com.yandex.metrika.CampaignReceiver"android: enabled = "false"android: exported = "true">
As the test sample spread 2 Yandex.Metro file version 1.66 - the mute "all" other than checking for updates maps, and a fully disabled services, including updates.
YMetro1.66-NS.apk(2.37 MB)
YMetro1.66-NS-NOUPDATE.apk(2.37 MB)
Cons - if you change the city / card will have to pay a single drop of the program, then everything will be fine. Card is exactly the same procedure.
Post has been editedkkk4 - 29.09.13, 18:57