bypass android usb host permission confirmation dialog
Solution 1
I know it's a bit late, but still...
I had the same kind of problem and I think I've managed to solve it. There's a service that Android uses internally that allows to manage USB devices and accessories. This service is hidden from thrid party developers and is not documented. If you check the source code for UsbPermissionActivity you'll be able to figure out how that service is called. In order to call the service IUsbManager interface and ServiceManager class are employed. These are both hidden too, so you can't use them directly. But what you can do is to create their stubs with exactly the same names and in corresponding namespaces (packages). Then you'll be able to compile that code, while the runtime environment will use the real things.
The only requirement is that your application has to be a system one - that is it has to be located in /system/app/ directory. Since your device is rooted that shouldn't be a problem.
So you will have to add a package to your project: "android.hardware.usb" and put a file in it named "IUsbManager.java" with the following content:
package android.hardware.usb;
public interface IUsbManager extends android.os.IInterface
{
/** Local-side IPC implementation stub class. */
public static abstract class Stub extends android.os.Binder implements android.hardware.usb.IUsbManager
{
/** Construct the stub at attach it to the interface. */
public Stub()
{
throw new RuntimeException( "Stub!" );
}
/**
* Cast an IBinder object into an android.hardware.usb.IUsbManager interface,
* generating a proxy if needed.
*/
public static android.hardware.usb.IUsbManager asInterface( android.os.IBinder obj )
{
throw new RuntimeException( "Stub!" );
}
public android.os.IBinder asBinder()
{
throw new RuntimeException( "Stub!" );
}
public boolean onTransact( int code, android.os.Parcel data, android.os.Parcel reply, int flags ) throws android.os.RemoteException
{
throw new RuntimeException( "Stub!" );
}
static final int TRANSACTION_getDeviceList = (android.os.IBinder.FIRST_CALL_TRANSACTION + 0);
static final int TRANSACTION_openDevice = (android.os.IBinder.FIRST_CALL_TRANSACTION + 1);
static final int TRANSACTION_getCurrentAccessory = (android.os.IBinder.FIRST_CALL_TRANSACTION + 2);
static final int TRANSACTION_openAccessory = (android.os.IBinder.FIRST_CALL_TRANSACTION + 3);
static final int TRANSACTION_setDevicePackage = (android.os.IBinder.FIRST_CALL_TRANSACTION + 4);
static final int TRANSACTION_setAccessoryPackage = (android.os.IBinder.FIRST_CALL_TRANSACTION + 5);
static final int TRANSACTION_hasDevicePermission = (android.os.IBinder.FIRST_CALL_TRANSACTION + 6);
static final int TRANSACTION_hasAccessoryPermission = (android.os.IBinder.FIRST_CALL_TRANSACTION + 7);
static final int TRANSACTION_requestDevicePermission = (android.os.IBinder.FIRST_CALL_TRANSACTION + 8);
static final int TRANSACTION_requestAccessoryPermission = (android.os.IBinder.FIRST_CALL_TRANSACTION + 9);
static final int TRANSACTION_grantDevicePermission = (android.os.IBinder.FIRST_CALL_TRANSACTION + 10);
static final int TRANSACTION_grantAccessoryPermission = (android.os.IBinder.FIRST_CALL_TRANSACTION + 11);
static final int TRANSACTION_hasDefaults = (android.os.IBinder.FIRST_CALL_TRANSACTION + 12);
static final int TRANSACTION_clearDefaults = (android.os.IBinder.FIRST_CALL_TRANSACTION + 13);
static final int TRANSACTION_setCurrentFunction = (android.os.IBinder.FIRST_CALL_TRANSACTION + 14);
static final int TRANSACTION_setMassStorageBackingFile = (android.os.IBinder.FIRST_CALL_TRANSACTION + 15);
}
/* Returns a list of all currently attached USB devices */
public void getDeviceList( android.os.Bundle devices ) throws android.os.RemoteException;
/* Returns a file descriptor for communicating with the USB device.
* The native fd can be passed to usb_device_new() in libusbhost.
*/
public android.os.ParcelFileDescriptor openDevice( java.lang.String deviceName ) throws android.os.RemoteException;
/* Returns the currently attached USB accessory */
public android.hardware.usb.UsbAccessory getCurrentAccessory() throws android.os.RemoteException;
/* Returns a file descriptor for communicating with the USB accessory.
* This file descriptor can be used with standard Java file operations.
*/
public android.os.ParcelFileDescriptor openAccessory( android.hardware.usb.UsbAccessory accessory ) throws android.os.RemoteException;
/* Sets the default package for a USB device
* (or clears it if the package name is null)
*/
public void setDevicePackage( android.hardware.usb.UsbDevice device, java.lang.String packageName ) throws android.os.RemoteException;
/* Sets the default package for a USB accessory
* (or clears it if the package name is null)
*/
public void setAccessoryPackage( android.hardware.usb.UsbAccessory accessory, java.lang.String packageName ) throws android.os.RemoteException;
/* Returns true if the caller has permission to access the device. */
public boolean hasDevicePermission(android.hardware.usb.UsbDevice device) throws android.os.RemoteException;
/* Returns true if the caller has permission to access the accessory. */
public boolean hasAccessoryPermission( android.hardware.usb.UsbAccessory accessory ) throws android.os.RemoteException;
/* Requests permission for the given package to access the device.
* Will display a system dialog to query the user if permission
* had not already been given.
*/
public void requestDevicePermission( android.hardware.usb.UsbDevice device, java.lang.String packageName, android.app.PendingIntent pi ) throws android.os.RemoteException;
/* Requests permission for the given package to access the accessory.
* Will display a system dialog to query the user if permission
* had not already been given. Result is returned via pi.
*/
public void requestAccessoryPermission( android.hardware.usb.UsbAccessory accessory, java.lang.String packageName, android.app.PendingIntent pi ) throws android.os.RemoteException;
/* Grants permission for the given UID to access the device */
public void grantDevicePermission( android.hardware.usb.UsbDevice device, int uid ) throws android.os.RemoteException;
/* Grants permission for the given UID to access the accessory */
public void grantAccessoryPermission( android.hardware.usb.UsbAccessory accessory, int uid ) throws android.os.RemoteException;
/* Returns true if the USB manager has default preferences or permissions for the package */
public boolean hasDefaults( java.lang.String packageName ) throws android.os.RemoteException;
/* Clears default preferences and permissions for the package */
public void clearDefaults( java.lang.String packageName ) throws android.os.RemoteException;
/* Sets the current USB function. */
public void setCurrentFunction( java.lang.String function, boolean makeDefault ) throws android.os.RemoteException;
/* Sets the file path for USB mass storage backing file. */
public void setMassStorageBackingFile( java.lang.String path ) throws android.os.RemoteException;
}
Then another package: "android.os" with "ServiceManager.java":
package android.os;
import java.util.Map;
public final class ServiceManager
{
public static IBinder getService( String name )
{
throw new RuntimeException( "Stub!" );
}
/**
* Place a new @a service called @a name into the service
* manager.
*
* @param name the name of the new service
* @param service the service object
*/
public static void addService( String name, IBinder service )
{
throw new RuntimeException( "Stub!" );
}
/**
* Retrieve an existing service called @a name from the
* service manager. Non-blocking.
*/
public static IBinder checkService( String name )
{
throw new RuntimeException( "Stub!" );
}
public static String[] listServices() throws RemoteException
{
throw new RuntimeException( "Stub!" );
}
/**
* This is only intended to be called when the process is first being brought
* up and bound by the activity manager. There is only one thread in the process
* at that time, so no locking is done.
*
* @param cache the cache of service references
* @hide
*/
public static void initServiceCache( Map<String, IBinder> cache )
{
throw new RuntimeException( "Stub!" );
}
}
Note that interfaces of these classes may change depending on the version of Android. In my case the version is 4.0.3. So if you have another version of Android and this code doesn't work you will have to check the source code for your particular version of OS.
Here's an example of using the service to grant permissions to all FTDI devices:
import java.util.HashMap;
import java.util.Iterator;
import android.content.BroadcastReceiver;
import android.content.Context;
import android.content.Intent;
import android.content.pm.ApplicationInfo;
import android.content.pm.PackageManager;
import android.hardware.usb.IUsbManager;
import android.hardware.usb.UsbDevice;
import android.hardware.usb.UsbManager;
import android.os.IBinder;
import android.os.ServiceManager;
public class LaunchReceiver extends BroadcastReceiver
{
public void onReceive( Context context, Intent intent )
{
String action = intent.getAction();
if( action != null && action.equals( Intent.ACTION_BOOT_COMPLETED ) )
{
try
{
PackageManager pm = context.getPackageManager();
ApplicationInfo ai = pm.getApplicationInfo( YOUR_APP_PACKAGE_NAMESPACE, 0 );
if( ai != null )
{
UsbManager manager = (UsbManager) context.getSystemService( Context.USB_SERVICE );
IBinder b = ServiceManager.getService( Context.USB_SERVICE );
IUsbManager service = IUsbManager.Stub.asInterface( b );
HashMap<String, UsbDevice> deviceList = manager.getDeviceList();
Iterator<UsbDevice> deviceIterator = deviceList.values().iterator();
while( deviceIterator.hasNext() )
{
UsbDevice device = deviceIterator.next();
if( device.getVendorId() == 0x0403 )
{
service.grantDevicePermission( device, ai.uid );
service.setDevicePackage( device, YOUR_APP_PACKAGE_NAMESPACE );
}
}
}
}
catch( Exception e )
{
trace( e.toString() );
}
}
}
}
One more thing - you will have to add the following permission to your manifest (Lint might not like it but you can always change severity level in your project's properties):
<uses-permission android:name="android.permission.MANAGE_USB" />
Solution 2
@d_d_t aswer is great, but it dosen't work on Android > 4.2.2. Use this interface:
public interface IUsbManager extends android.os.IInterface
{
/** Local-side IPC implementation stub class. */
public static abstract class Stub extends android.os.Binder implements android.hardware.usb.IUsbManager {
private static final java.lang.String DESCRIPTOR = "android.hardware.usb.IUsbManager";
/** Construct the stub at attach it to the interface. */
public Stub() {
throw new RuntimeException( "Stub!" );
}
/**
* Cast an IBinder object into an android.hardware.usb.IUsbManager
* interface, generating a proxy if needed.
*/
public static android.hardware.usb.IUsbManager asInterface( android.os.IBinder obj) {
throw new RuntimeException( "Stub!" );
}
@Override
public android.os.IBinder asBinder() {
throw new RuntimeException( "Stub!" );
}
@Override
public boolean onTransact(int code, android.os.Parcel data, android.os.Parcel reply, int flags) throws android.os.RemoteException {
throw new RuntimeException( "Stub!" );
}
static final int TRANSACTION_getDeviceList = (android.os.IBinder.FIRST_CALL_TRANSACTION + 0);
static final int TRANSACTION_openDevice = (android.os.IBinder.FIRST_CALL_TRANSACTION + 1);
static final int TRANSACTION_getCurrentAccessory = (android.os.IBinder.FIRST_CALL_TRANSACTION + 2);
static final int TRANSACTION_openAccessory = (android.os.IBinder.FIRST_CALL_TRANSACTION + 3);
static final int TRANSACTION_setDevicePackage = (android.os.IBinder.FIRST_CALL_TRANSACTION + 4);
static final int TRANSACTION_setAccessoryPackage = (android.os.IBinder.FIRST_CALL_TRANSACTION + 5);
static final int TRANSACTION_hasDevicePermission = (android.os.IBinder.FIRST_CALL_TRANSACTION + 6);
static final int TRANSACTION_hasAccessoryPermission = (android.os.IBinder.FIRST_CALL_TRANSACTION + 7);
static final int TRANSACTION_requestDevicePermission = (android.os.IBinder.FIRST_CALL_TRANSACTION + 8);
static final int TRANSACTION_requestAccessoryPermission = (android.os.IBinder.FIRST_CALL_TRANSACTION + 9);
static final int TRANSACTION_grantDevicePermission = (android.os.IBinder.FIRST_CALL_TRANSACTION + 10);
static final int TRANSACTION_grantAccessoryPermission = (android.os.IBinder.FIRST_CALL_TRANSACTION + 11);
static final int TRANSACTION_hasDefaults = (android.os.IBinder.FIRST_CALL_TRANSACTION + 12);
static final int TRANSACTION_clearDefaults = (android.os.IBinder.FIRST_CALL_TRANSACTION + 13);
static final int TRANSACTION_setCurrentFunction = (android.os.IBinder.FIRST_CALL_TRANSACTION + 14);
static final int TRANSACTION_setMassStorageBackingFile = (android.os.IBinder.FIRST_CALL_TRANSACTION + 15);
static final int TRANSACTION_allowUsbDebugging = (android.os.IBinder.FIRST_CALL_TRANSACTION + 16);
static final int TRANSACTION_denyUsbDebugging = (android.os.IBinder.FIRST_CALL_TRANSACTION + 17);
}
/* Returns a list of all currently attached USB devices */
public void getDeviceList(android.os.Bundle devices)
throws android.os.RemoteException;
/*
* Returns a file descriptor for communicating with the USB device. The
* native fd can be passed to usb_device_new() in libusbhost.
*/
public android.os.ParcelFileDescriptor openDevice(
java.lang.String deviceName) throws android.os.RemoteException;
/* Returns the currently attached USB accessory */
public android.hardware.usb.UsbAccessory getCurrentAccessory()
throws android.os.RemoteException;
/*
* Returns a file descriptor for communicating with the USB accessory. This
* file descriptor can be used with standard Java file operations.
*/
public android.os.ParcelFileDescriptor openAccessory(
android.hardware.usb.UsbAccessory accessory)
throws android.os.RemoteException;
/*
* Sets the default package for a USB device (or clears it if the package
* name is null)
*/
public void setDevicePackage(android.hardware.usb.UsbDevice device,
java.lang.String packageName, int userId)
throws android.os.RemoteException;
/*
* Sets the default package for a USB accessory (or clears it if the package
* name is null)
*/
public void setAccessoryPackage(
android.hardware.usb.UsbAccessory accessory,
java.lang.String packageName, int userId)
throws android.os.RemoteException;
/* Returns true if the caller has permission to access the device. */
public boolean hasDevicePermission(android.hardware.usb.UsbDevice device)
throws android.os.RemoteException;
/* Returns true if the caller has permission to access the accessory. */
public boolean hasAccessoryPermission(
android.hardware.usb.UsbAccessory accessory)
throws android.os.RemoteException;
/*
* Requests permission for the given package to access the device. Will
* display a system dialog to query the user if permission had not already
* been given.
*/
public void requestDevicePermission(android.hardware.usb.UsbDevice device,
java.lang.String packageName, android.app.PendingIntent pi)
throws android.os.RemoteException;
/*
* Requests permission for the given package to access the accessory. Will
* display a system dialog to query the user if permission had not already
* been given. Result is returned via pi.
*/
public void requestAccessoryPermission(
android.hardware.usb.UsbAccessory accessory,
java.lang.String packageName, android.app.PendingIntent pi)
throws android.os.RemoteException;
/* Grants permission for the given UID to access the device */
public void grantDevicePermission(android.hardware.usb.UsbDevice device,
int uid) throws android.os.RemoteException;
/* Grants permission for the given UID to access the accessory */
public void grantAccessoryPermission(
android.hardware.usb.UsbAccessory accessory, int uid)
throws android.os.RemoteException;
/*
* Returns true if the USB manager has default preferences or permissions
* for the package
*/
public boolean hasDefaults(java.lang.String packageName, int userId)
throws android.os.RemoteException;
/* Clears default preferences and permissions for the package */
public void clearDefaults(java.lang.String packageName, int userId)
throws android.os.RemoteException;
/* Sets the current USB function. */
public void setCurrentFunction(java.lang.String function,
boolean makeDefault) throws android.os.RemoteException;
/* Sets the file path for USB mass storage backing file. */
public void setMassStorageBackingFile(java.lang.String path)
throws android.os.RemoteException;
/*
* Allow USB debugging from the attached host. If alwaysAllow is true, add
* the the public key to list of host keys that the user has approved.
*/
public void allowUsbDebugging(boolean alwaysAllow,
java.lang.String publicKey) throws android.os.RemoteException;
/* Deny USB debugging from the attached host */
public void denyUsbDebugging() throws android.os.RemoteException;
}
And modify the code adding user id:
...
service.setDevicePackage( usbDevice, YOUR_APP_PACKAGE_NAMESPACE, ai.uid );
....
Solution 3
i had the same problem with the popup window and nobody to click on it. But i found a different solution (for rooted devices). The popup gets generated by android in the class UsbPermissionActivity (and that UsbPermissionActivity is started by the UsbSettingsManager). Look at the Android Sourcecode to see whats going on. The good thing here is, we can manipulate the bytecode of the UsbPermissionActivity to accept all UsbDevices. You need the tool Smali/Baksmali to do so. https://code.google.com/p/smali/
- Locate the file SystemUI.apk on your device
- Copy it to your computer with
adb pull path/to/SystemUI.apk
- Unzip the apk
- Disassemble the classes.dex file with
java -jar baksmali.jar classes.dex
-
Find the file UsbPermissionActivity and inside of it find the line that says
invoke-virtual {p0}, Lcom/android/systemui/usb/UsbPermissionActivity;->setupAlert()V
Change this by commenting it out and adding two new lines
#invoke-virtual {p0}, Lcom/android/systemui/usb/UsbPermissionActivity;->setupAlert()V
const/4 v0, 0x1
iput-boolean v0, p0, Lcom/android/systemui/usb/UsbPermissionActivity;->mPermissionGranted:Z
invoke-virtual {p0}, Lcom/android/systemui/usb/UsbPermissionActivity;->finish()V
- Assemble it with
java -jar smali.jar -o classes.dex out
- Replace the original classes.dex and zip everything again to SystemUI.apk
- Replace the original SystemUI.apk on your device with
adb push services.jar path/to/SystemUI.apk
or if that doesnt work with a filemanager ap
Solution 4
The solution is to use intent filters and add the android:directBootAware="true"
attribute to the associated activity so that the USB_DEVICE_ATTACHED
event is correctly received after boot / reboot. It is important not to ask for the USB
device permission in code, only using intent filters, like this:
<manifest>
<uses-feature android:name="android.hardware.usb.host" />
<activity
...
android:directBootAware="true">
<intent-filter>
<action android:name="android.hardware.usb.action.USB_DEVICE_ATTACHED" />
</intent-filter>
<meta-data android:name="android.hardware.usb.action.USB_DEVICE_ATTACHED"
android:resource="@xml/device_filter" />
</activity>
</manifest>
With a device_filter XML
resource file similar to this:
<?xml version="1.0" encoding="utf-8"?>
<resources>
<usb-device vendor-id="1234" product-id="5678" />
</resources>
Solution 5
If you have the option to compile the android system, then there's nothing you cannot do.
You can add
public void onStart() {
super.onStart();
mPermissionGranted = true;
finish();
}
to frameworks/base/packages/SystemUI/src/com/android/systemui/usb/UsbPermissionActivity.java
to bypass the the permission confirmation popup.
Comments
-
AliRezza about 4 years
I want to use android in industry,
I can connect to Profilic and Ftdi USB to Serial chips with slickdevlabs.com library without any problem.
The application has a service and it starts on boot,connect to the usb serial port and do the other things.
my problem is that the host device does not have any interaction with user,
so when the android asks
Allow the app "MyAPP" to access the USB device ? [checkmark]Use by default for this USB device Cancel OK
there is no person to click on ok.
even when I check the use by default... checkbox,If I reinsert the USB ,or reboot the host device, it asks again on next boot.
I ran the service and app with SuperUser mode,but no difference,it asks again.
I added intent filter but no difference,it asks me every time.
<intent-filter> <action android:name="android.hardware.usb.action.USB_DEVICE_ATTACHED" /> <action android:name="android.hardware.usb.action.USB_DEVICE_DETACHED" /> </intent-filter> <meta-data android:name="android.hardware.usb.action.USB_DEVICE_ATTACHED" android:resource="@xml/device_filter" /> <meta-data android:name="android.hardware.usb.action.USB_DEVICE_DETACHED" android:resource="@xml/device_filter" />
Any opinion how to bypass or disable it ?
I have root and SU access.
-
AliRezza over 11 yearsI did the same thing,but the background service can not access the dialog-box all the time,and it had error.
-
cnexus over 11 yearsThis has nothing to do with it. The point isn't to be able to connect to the device, which he/she is already able to do, its to prevent the dialog confirmation from appearing.
-
AliRezza about 11 yearsThanks , I will check it and let you know.
-
Alvins over 10 yearsOn 4.2.2 it doesn't work because setDevicePackage() has changed. Check my answer for the code.
-
ashokk over 10 yearsHow can I use it for usb accessory?
-
Basher51 almost 10 yearsThanks for the info.I see you have shared IUsbManager.java interface code.What about the code for ServiceManager.java.Is it also different for 4.2.2? Also, will the usb permission popup not come even when the device is rebooted/app is upgraded?
-
Yeung almost 10 yearsIt work on boot. But if I replug the FTDI devices, the dialog still be shown(although I click "cancel", it still work). I am using FDTI's d2xx library. Is the library somewhere called
mUsbManager.requestPermission(device, mPermissionIntent);
? Then I have nothing to do with it. -
Yeung almost 10 yearsOh, with this intent-filter method. It works if I declare an the invisible activity on the Manifest(Don't know why Receiver and Service not work).Re-Plug the device, the dialog won't be shown.
-
phyatt almost 9 yearsI just now tried this out, and it also seemed to corrupt some other things on the device. SystemUI was under
/system/priv-app
. This is with Android 4.4.2 . -
phyatt almost 9 yearsIt works for an FTDI permission, One other missing step is to do a chmod on the SystemUI,apk when reinstalling it.
-
Milad Metias about 8 yearsI'm trying to find the code suitable for 5.1 for 5 days but i failed please can you help me and post the codes for android 5.1 ?
-
Milad Metias about 8 years
-
Anantha Raju C over 7 yearsthis is a low quality answer
-
Tushar Thakur over 6 yearsI am getting following issue ..... "Neither user XXXXX nor current process has android.permission.MANAGE_USB.". I have already given manage usb permission in android manifest file as follows........ <uses-permission android:name="android.Manifest.permission.MANAGE_USB" /> This exception comes at service.grantDevicePermission( device, ai.uid ); this line
-
AvielNiego about 6 yearsThats worked great! The Smali/Baksmali moved to github.com/JesusFreke/smali and in Smali/Baksmali 2.2 the commands has changed to
java -jar baksmali.jar d classes.dex
andjava -jar smali.jar a -o classes.dex out
-
Rick Sanchez about 6 yearsThanks for this, pointed me on the right direction. Reading the source then found out that there is a config for this named config_disableUsbPermissionDialogs in frameworks/base/core/res/res/values/config.xml
-
user924 over 5 yearsit doesn't work, I've add all this intent-filter to my activity, but it still doesn't have permission
-
user924 over 5 yearsfor newer Android we have to use
/system/priv-app/
instead of/system/app/
directory to get system permissions -
user924 about 5 yearsit's only for filtering devices (by vendor, product id). it has nothing to do with device permissions!
-
PieterAelse about 5 years@user924 "Note: If your application uses an intent filter to discover USB devices as they're connected, it automatically receives permission if the user allows your application to handle the intent. If not, you must request permission explicitly in your application before connecting to the device."
-
user924 about 5 yearsIn all cases a dialog with request permission pops up, just try it yourself (I had all intent-filters, device/vendor ids, my receivers detect that device is connected or disconnect but still requires permission). Anyway I found a way to avoid it using Root and system app
-
user924 about 5 yearsBasically when you delete your app and install it again it will 100% require a permission
-
Jemo Mgebrishvili about 5 yearsit works, but after device restart's, dialog steel shows
-
dazza5000 almost 5 years@RickSanchez - how do you update the config.xml file to use the new value?
-
Rick Sanchez almost 5 yearsModified it in the AOSP tree, and compiled again / flashed the image.
-
user155 almost 5 yearsOn some Android 9 devices it fails with:
java.lang.NoSuchMethodError: No interface method grantDevicePermission(Landroid/hardware/usb/UsbDevice;I)V in class Landroid/hardware/usb/IUsbManager; or its super classes (declaration of 'android.hardware.usb.IUsbManager' appears in /system/framework/framework.jar)
-
user155 almost 5 yearsOn some Android 9 devices (e.g. Xiaomi MI A2 Lite) it fails with:
java.lang.NoSuchMethodError: No interface method grantDevicePermission(Landroid/hardware/usb/UsbDevice;I)V in class Landroid/hardware/usb/IUsbManager; or its super classes (declaration of 'android.hardware.usb.IUsbManager' appears in /system/framework/framework.jar)
-
dazza5000 almost 5 yearsIt is actually cleared on restart too. You would need to setup something that copies the xml file over to the correct directory on boot.
-
user924 almost 5 yearsIt seems it doesn't work on Android 9 at all, not just some devices
-
user924 almost 5 years
model
? What is that?UsbDevice
class can give us productName, deviceName, manufacturerName and others. Does "productName" equal "model"? -
user924 almost 5 years
NAME LIKE ONE REGISTERED IN meta-data in the manifest
and what is that? What are you talking about? Registered where? Which manifest? -
user924 almost 5 yearsand why do you open
<settings>
tag but don't close it? -
Igor Čordaš almost 5 years@user924 It was just missing in the answer, it should be closed. It is not to be copy pasted anyway because of placeholders. Unfortunately I can not fix this since code editor on stackoverflow does not render it but when I try to edit it is there..
-
user924 over 4 yearswell system automatically add devices to that file and connects them to your app but it doesn't mean that your app has permission for devices included in that file
-
user924 over 4 years@RickSanchez well you can't install that AOSP compiled image to any phone (like the latest samsung)
-
user924 over 4 yearsthis is stupid and I want to control a device without activity but from service
-
user924 over 4 yearsAnd that solution doesn't work after rebooting. So yes you can plug/unplug device and it will automatically grant permission but once you reboot the device you need to request or unplug/plug device manually again. Useless!
-
user924 over 4 yearsAndroid doesn't have such file
/etc/udev
. It's not Ubuntu! -
user924 over 4 yearsand this file is used for detecting devices on Ubuntu. You posted a totally random thing here
-
user924 over 4 yearsNo one have access to Xiaomi or Samsung firmware source code
-
user924 over 4 yearsafter rebooting you still need to request it again, intent filters help only for the current boot session
-
user924 over 4 yearsjust a theory answer
-
user924 over 4 yearsfound solution for Android 9 stackoverflow.com/a/57622623/7767664
-
user924 over 4 yearsfound solution for Android 9 stackoverflow.com/a/57622623/7767664
-
Ascari Gh about 4 yearsI suppose not however, they aren't the only ones that use the Open Source Android OS
-
W.M. about 4 years@RickSanchez flashed the whole system image OMG. Why cannot it be automatic. After all GOOGLE ANDROID I PAY FOR HAVING YOUR SECURITY CONCERNED DEVICE!
-
ctd over 3 yearsThanks! This is by far the simplest and fastest solution as of 2020. One issue I still see is that the device is not available after unplugging/replugging, although that is not so significant for my project.
-
Ihdina over 2 yearsits not worked, I'm using sdk 21.