Searched refs:methods (Results 1 – 25 of 43) sorted by relevance
12
1 # Keep classes and methods that have the @UsedForTesting annotation7 # Keep classes and methods that have the @ExternallyReferenced annotation13 # Keep native methods15 native <methods>;18 # Keep classes that are used as a parameter type of methods that are also marked as keep19 # to preserve changing those methods' signature.
50 Filtering methods used are:52 * T9/dialpad search methods55 * Numeric/dialpad search methods61 * Name/keyboard search methods:
24 # This prevents the names of native methods from being obfuscated and prevents27 native <methods>;41 # These methods are needed to ensure that serialization behaves as expected when
8 # Allows proguard to make private and protected methods and fields public as9 # part of optimization. This lets proguard inline trivial getter/setter methods.
1 # Keep the annotation, classes, methods, and fields marked as UsedByReflection
36 native <methods>;50 # an annotation to mark fields and methods used by native code.66 @android.support.annotation.VisibleForTesting <methods>;
63 int registerNativeMethods(JNIEnv *env, const char *const className, const JNINativeMethod *methods, in registerNativeMethods() argument70 if (env->RegisterNatives(clazz, methods, numMethods) != 0) { in registerNativeMethods()
23 int registerNativeMethods(JNIEnv *env, const char *const className, const JNINativeMethod *methods,
15 …Builder methods names should use setFoo() / addFoo() / clearFoo() style: method org.chromium.net.C…17 …Builder methods names should use setFoo() / addFoo() / clearFoo() style: method org.chromium.net.C…19 …Builder methods names should use setFoo() / addFoo() / clearFoo() style: method org.chromium.net.C…21 …Builder methods names should use setFoo() / addFoo() / clearFoo() style: method org.chromium.net.C…23 …Builder methods names should use setFoo() / addFoo() / clearFoo() style: method org.chromium.net.C…25 …Builder methods names should use setFoo() / addFoo() / clearFoo() style: method org.chromium.net.U…27 …Builder methods names should use setFoo() / addFoo() / clearFoo() style: method org.chromium.net.U…31 Registration methods should have overload that accepts delivery Executor: `getStatus`
4 # Keep classes and methods that have the @VisibleForTesting annotation10 # We want to keep methods in Activity that could be used in the XML attribute onClick.
19 # Keep classes and methods that have the guava @VisibleForTesting annotation28 # Keep methods that have the @VisibleForAnimation annotation
23 # non-private methods. This means we cannot run tests on user builds for the moment.
82 if (simulatorPortalEntryGroup.methods().containsKey(commands[index])) { in execute()83 simulatorPortalEntryGroup.methods().get(commands[index]).run(); in execute()
27 abstract ImmutableMap<String, Runnable> methods(); in methods() method in SimulatorPortalEntryGroup
66 for (Entry<String, Runnable> method : portal.methods().entrySet()) { in onPrepareSubMenu()
2 -keep class com.android.terminal.Terminal { native <methods>; }
1 # Keep classes and methods that have the guava @VisibleForTesting annotation
18 @com.android.camera.OnClickAttr <methods>;
7 native <methods>;
4 # We want to keep methods in Activity that could be used in the XML attribute onClick.
26 @com.android.camera.OnClickAttr <methods>;
20 # Proguard will strip methods required for talkback to properly scroll to
24 native <methods>;