¿Cómo obtener el nombre del paquete desde cualquier lugar?

Soy consciente de la disponibilidad de Context.getApplicationContext () y View.getContext () , a través del cual puedo llamar a Context.getPackageName () para recuperar el nombre del paquete de una aplicación.

Funcionan si llamo desde un método al que está disponible un objeto View o Activity , pero si quiero encontrar el nombre del paquete desde una clase totalmente independiente sin View o Activity , ¿hay alguna manera de hacerlo (directa o indirectamente?) )?

Una idea es tener una variable estática en su actividad principal, instanciada para ser el nombre del paquete. Entonces sólo referencia esa variable.

Tendrás que inicializarlo en el método onCreate() la actividad principal:

Global a la clase:

 public static String PACKAGE_NAME; 

Entonces..

 @Override public void onCreate(Bundle savedInstanceState) { super.onCreate(savedInstanceState); setContentView(R.layout.main); PACKAGE_NAME = getApplicationContext().getPackageName(); } 

A continuación, puede acceder a ella a través de Main.PACKAGE_NAME .

Si utiliza el gradle-android-plugin para crear su aplicación, puede utilizar

 BuildConfig.APPLICATION_ID 

Para recuperar el nombre del paquete desde cualquier ámbito, incl. Una estática.

Si con la palabra "en cualquier lugar" quiere decir sin tener un Context explícito (por ejemplo de un hilo de fondo), debe definir una clase en su proyecto como:

 public class MyApp extends Application { private static MyApp instance; public static MyApp getInstance() { return instance; } public static Context getContext(){ return instance; // or return instance.getApplicationContext(); } @Override public void onCreate() { instance = this; super.onCreate(); } } 

A continuación, en su manifest , debe agregar esta clase al campo Name de la ficha Application . O editar el xml y poner

 <application android:name="com.example.app.MyApp" android:icon="@drawable/icon" android:label="@string/app_name" ....... <activity ...... 

Y luego desde cualquier lugar que puedas llamar

 String packagename= MyApp.getContext().getPackageName(); 

Espero eso ayude.

Si utiliza gradle build, use esto: BuildConfig.APPLICATION_ID para obtener el nombre del paquete de la aplicación.

 private String getApplicationName(Context context, String data, int flag) { final PackageManager pckManager = context.getPackageManager(); ApplicationInfo applicationInformation; try { applicationInformation = pckManager.getApplicationInfo(data, flag); } catch (PackageManager.NameNotFoundException e) { applicationInformation = null; } final String applicationName = (String) (applicationInformation != null ? pckManager.getApplicationLabel(applicationInformation) : "(unknown)"); return applicationName; } 

Cree un módulo java que se ejecute inicialmente al iniciar su aplicación. Este módulo ampliará la clase de aplicación android y inicializaría cualquier variable de aplicación global y también contendrá rutinas de utilidad para toda la aplicación,

 public class MyApplicationName extends Application { private final String PACKAGE_NAME = "com.mysite.myAppPackageName"; public String getPackageName() { return PACKAGE_NAME; } } 

Por supuesto, esto podría incluir lógica para obtener el nombre del paquete desde el sistema android; Sin embargo, lo anterior es un código más pequeño, más rápido y más limpio que obtenerlo desde android.

Asegúrese de colocar una entrada en su archivo AndroidManifest.xml para indicarle a android que ejecute su módulo de aplicación antes de ejecutar cualquier actividad,

 <application android:name=".MyApplicationName" ... > 

A continuación, para obtener el nombre del paquete desde cualquier otro módulo, escriba

 MyApp myApp = (MyApp) getApplicationContext(); String myPackage = myApp.getPackageName(); 

El uso de un módulo de aplicación también le da un contexto para los módulos que necesitan pero no tienen un contexto.

Puede obtener el nombre de su paquete así:

 $ /path/to/adb shell 'pm list packages -f myapp' package:/data/app/mycompany.myapp-2.apk=mycompany.myapp 

Aquí están las opciones:

 $ adb Android Debug Bridge version 1.0.32 Revision 09a0d98bebce-android -a - directs adb to listen on all interfaces for a connection -d - directs command to the only connected USB device returns an error if more than one USB device is present. -e - directs command to the only running emulator. returns an error if more than one emulator is running. -s <specific device> - directs command to the device or emulator with the given serial number or qualifier. Overrides ANDROID_SERIAL environment variable. -p <product name or path> - simple product name like 'sooner', or a relative/absolute path to a product out directory like 'out/target/product/sooner'. If -p is not specified, the ANDROID_PRODUCT_OUT environment variable is used, which must be an absolute path. -H - Name of adb server host (default: localhost) -P - Port of adb server (default: 5037) devices [-l] - list all connected devices ('-l' will also list device qualifiers) connect <host>[:<port>] - connect to a device via TCP/IP Port 5555 is used by default if no port number is specified. disconnect [<host>[:<port>]] - disconnect from a TCP/IP device. Port 5555 is used by default if no port number is specified. Using this command with no additional arguments will disconnect from all connected TCP/IP devices. device commands: adb push [-p] <local> <remote> - copy file/dir to device ('-p' to display the transfer progress) adb pull [-p] [-a] <remote> [<local>] - copy file/dir from device ('-p' to display the transfer progress) ('-a' means copy timestamp and mode) adb sync [ <directory> ] - copy host->device only if changed (-l means list but don't copy) adb shell - run remote shell interactively adb shell <command> - run remote shell command adb emu <command> - run emulator console command adb logcat [ <filter-spec> ] - View device log adb forward --list - list all forward socket connections. the format is a list of lines with the following format: <serial> " " <local> " " <remote> "\n" adb forward <local> <remote> - forward socket connections forward specs are one of: tcp:<port> localabstract:<unix domain socket name> localreserved:<unix domain socket name> localfilesystem:<unix domain socket name> dev:<character device name> jdwp:<process pid> (remote only) adb forward --no-rebind <local> <remote> - same as 'adb forward <local> <remote>' but fails if <local> is already forwarded adb forward --remove <local> - remove a specific forward socket connection adb forward --remove-all - remove all forward socket connections adb reverse --list - list all reverse socket connections from device adb reverse <remote> <local> - reverse socket connections reverse specs are one of: tcp:<port> localabstract:<unix domain socket name> localreserved:<unix domain socket name> localfilesystem:<unix domain socket name> adb reverse --norebind <remote> <local> - same as 'adb reverse <remote> <local>' but fails if <remote> is already reversed. adb reverse --remove <remote> - remove a specific reversed socket connection adb reverse --remove-all - remove all reversed socket connections from device adb jdwp - list PIDs of processes hosting a JDWP transport adb install [-lrtsdg] <file> - push this package file to the device and install it (-l: forward lock application) (-r: replace existing application) (-t: allow test packages) (-s: install application on sdcard) (-d: allow version code downgrade) (-g: grant all runtime permissions) adb install-multiple [-lrtsdpg] <file...> - push this package file to the device and install it (-l: forward lock application) (-r: replace existing application) (-t: allow test packages) (-s: install application on sdcard) (-d: allow version code downgrade) (-p: partial application install) (-g: grant all runtime permissions) adb uninstall [-k] <package> - remove this app package from the device ('-k' means keep the data and cache directories) adb bugreport - return all information from the device that should be included in a bug report. adb backup [-f <file>] [-apk|-noapk] [-obb|-noobb] [-shared|-noshared] [-all] [-system|-nosystem] [<packages...>] - write an archive of the device's data to <file>. If no -f option is supplied then the data is written to "backup.ab" in the current directory. (-apk|-noapk enable/disable backup of the .apks themselves in the archive; the default is noapk.) (-obb|-noobb enable/disable backup of any installed apk expansion (aka .obb) files associated with each application; the default is noobb.) (-shared|-noshared enable/disable backup of the device's shared storage / SD card contents; the default is noshared.) (-all means to back up all installed applications) (-system|-nosystem toggles whether -all automatically includes system applications; the default is to include system apps) (<packages...> is the list of applications to be backed up. If the -all or -shared flags are passed, then the package list is optional. Applications explicitly given on the command line will be included even if -nosystem would ordinarily cause them to be omitted.) adb restore <file> - restore device contents from the <file> backup archive adb disable-verity - disable dm-verity checking on USERDEBUG builds adb enable-verity - re-enable dm-verity checking on USERDEBUG builds adb keygen <file> - generate adb public/private key. The private key is stored in <file>, and the public key is stored in <file>.pub. Any existing files are overwritten. adb help - show this help message adb version - show version num scripting: adb wait-for-device - block until device is online adb start-server - ensure that there is a server running adb kill-server - kill the server if it is running adb get-state - prints: offline | bootloader | device adb get-serialno - prints: <serial-number> adb get-devpath - prints: <device-path> adb remount - remounts the /system, /vendor (if present) and /oem (if present) partitions on the device read-write adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program. adb reboot sideload - reboots the device into the sideload mode in recovery program (adb root required). adb reboot sideload-auto-reboot - reboots into the sideload mode, then reboots automatically after the sideload regardless of the result. adb sideload <file> - sideloads the given package adb root - restarts the adbd daemon with root permissions adb unroot - restarts the adbd daemon without root permissions adb usb - restarts the adbd daemon listening on USB adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port networking: adb ppp <tty> [parameters] - Run PPP over USB. Note: you should not automatically start a PPP connection. <tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1 [parameters] - Eg. defaultroute debug dump local notty usepeerdns adb sync notes: adb sync [ <directory> ] <localdir> can be interpreted in several ways: - If <directory> is not specified, /system, /vendor (if present), /oem (if present) and /data partitions will be updated. - If it is "system", "vendor", "oem" or "data", only the corresponding partition is updated. environment variables: ADB_TRACE - Print debug information. A comma separated list of the following values 1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp ANDROID_SERIAL - The serial number to connect to. -s takes priority over this if given. ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed. 
  • Estructura del paquete Android Mejor práctica
  • Crea un objeto java personalizado Parcelable en Android
  • Mostrar mensaje después de instalar el paquete
  • ¿Cómo puedo modificar y volver a publicar una aplicación AOSP?
  • Utilice Parcelable para pasar un objeto de una actividad de android a otra
  • Cambiar los datos del paquete de intenciones antes de volver a crear una actividad después del cambio de orientación
  • EditText no guardado automáticamente en el cambio de orientación de la pantalla
  • com.android.support:appcompat-v7 y versión de diseño 23.2.0 error de paquete de bloqueo
  • Enviar paquete con transacción de fragmentos
  • Averigua si la aplicación está instalada
  • ¿Qué es diferente de putSerializable y putParcelable en Java?
  • FlipAndroid es un fan de Google para Android, Todo sobre Android Phones, Android Wear, Android Dev y Aplicaciones para Android Aplicaciones.