blocks|key|2924057|text|从/etc/udev/rules.d/51-android.rules更改此行中的权限，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2924058|#Motorola+
SUBSYSTEM=="usb",+ATTR{idVendor}=="22b8",+MODE="0664",+GROUP="plugdev"|code-block|syntax|javascript|2924059|致，|2924060|#Motorola+
SUBSYSTEM=="usb",+ATTR{idVendor}=="22b8",+MODE="0666",+GROUP="plugdev"|2924061|以不需要以根用户身份运行adb的方式解决了此问题。|2924062|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Q|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|R|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Changing permissions in this line from /etc/udev/rules.d/51-android.rules,

<pre><code>#Motorola 
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0664", GROUP="plugdev"
</code></pre>

to,

<pre><code>#Motorola 
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666", GROUP="plugdev"
</code></pre>

resolves this issue in a manner that DOES NOT require running adb as root.

blocks|key|2711270|text|长话短说，我在Prestigio+PMP5570C平板电脑上也遇到了同样的问题，|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2711271|你所要做的就是在你的平板电脑上确认你想要将数据复制到你的计算机或者从你的计算机复制数据(我忘了)，然后添加@portsample写的2行代码。|2711272|您可以通过键入以下命令找到设备的idVendor|2711273|2711274|+lsusb|blockquote|2711275|2711276|2711277|在UBUNTU+12.04中，你会得到：|2711278|2711279|总线001设备011:+ID+2207:0010，|2711280|2711281|2711282|其中2207是您的供应商id。总结了问题和答案。|2711283|entityMap^0|7|I|0|0|0|0|0|0|0|0|0|F|4|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@$9|11|A|12|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|13|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|14|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|15|8|@]|D|@]|E|$]]|$1|K|3|L|5|M|7|16|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|17|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|18|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|19|8|@]|D|@]|E|$]]|$1|R|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]|$1|S|3|T|5|M|7|1B|8|@$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|U|3|-4|5|6|7|1E|8|@]|D|@]|E|$]]|$1|V|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]|$1|W|3|X|5|6|7|1G|8|@]|D|@]|E|$]]|$1|Y|3|-4|5|6|7|1H|8|@]|D|@]|E|$]]]|Z|$]]

Long to short,
I had the same problem with a Prestigio PMP5570C tablet,

all you have to do is to confirm on your tablet that you want to copy data to/from your computer (what i forgot), and add the 2 lines that @portsample wrote.

You can find the idVendor of your device typing 

<blockquote>
 lsusb
</blockquote>

in UBUNTU 12.04, then you get:

<blockquote>
 Bus 001 Device 011: ID 2207:0010,
</blockquote>

where 2207 is your vendor id.
Summed up the question and answer...

blocks|key|138301|text|我找到了一个对我有效的简单答案：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|138302|adb+kill-server
sudo+adb+start-server
sudo+adb+devices|code-block|syntax|javascript|138303|然后你就会找到你的设备。希望这能有所帮助。|138304|参考：http://itsfoss.com/fix-error-insufficient-permissions-device/|offset|length|138305|entityMap|0|LINK|mutability|MUTABLE|url|http://itsfoss.com/fix-error-insufficient-permissions-device/^0|0|0|0|3|1P|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|X|8|@]|9|@$K|Y|L|Z|1|10]]|A|$]]|$1|M|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

I found a simple answer that worked for me: 

<pre><code>adb kill-server
sudo adb start-server
sudo adb devices
</code></pre>

You will find your device then. Hope this helps.

Reference: <a href="http://itsfoss.com/fix-error-insufficient-permissions-device/" rel="noreferrer">http://itsfoss.com/fix-error-insufficient-permissions-device/</a>

blocks|key|139632|text|我在使用运行Android+5.1的Nexus4的Linux机器时遇到了这个问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|139633|修复方法是启用'debug+over+USB‘和'connect+as+MTP’。然而，当使用相同的设备和OSX上的Android+Studio和adb时，情况正好相反-为了允许Android+Studio识别手机，我需要禁用'connect+as+MTP‘。|139634|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I had this while using a Linux machine with a Nexus 4 running Android 5.1

The fix was to enable both 'debug over USB' and 'connect as MTP'. The opposite is true when using the same device and Android Studio and adb on OSX though - to allow Android Studio to recognise the handset, I need to disable 'connect as MTP'.

blocks|key|2711436|text|对于我和其他许多人来说，这个问题与机器上设备的访问权限有关。既然已经在android文档中详细记录了这一点，我认为最好的解决方案就是here。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2711437|在基于Debian的系统上，如果给定列表中不存在您的供应商，则可以运行lsusb或dmesg来获取供应商id|style|CODE|2711438|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.android.com/studio/run/device.html^0|1U|4|0|0|Z|5|15|5|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@$A|U|B|V|F|G]|$A|W|B|X|F|G]]|9|@]|C|$]]|$1|H|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

For me and possibly many others the issue is to do with access rights to devices on the machine. Now that this is well documented in the android documentation, I think the best solution is <a href="https://developer.android.com/studio/run/device.html" rel="nofollow">here</a>

On Debian based Systems you can run <code>lsusb</code> or <code>dmesg</code> to get vendor id if your vendor does not exist on the given list

blocks|key|2924232|text|在my+phone+Symphony+W75中，option+USB+->+selecting+Connect+as+Media+device(MTP)解决了此问题。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|2924233|entityMap^0|A|C|V|4|1C|S|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]|$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|O|8|@]|D|@]|E|$]]]|G|$]]

IN my phone Symphony W75, 
in option USB computer connection-> selecting Connect as Media device(MTP) has solved the problem.

blocks|key|138397|text|我也遇到过同样的问题，我已经通过将your_android_sdk_path的路径添加到环境变量中解决了这个问题，例如|type|unstyled|depth|inlineStyleRanges|entityRanges|data|138398|sudo+export+$PATH:/your_android_sdk_path/platform-tools/adb|code-block|syntax|javascript|138399|如果您想添加到系统范围访问，您希望如何通过编辑这些文件、~/.bashrc文件或~/.profile或/etc/profile,+/etc/bash.bashrc,+or+/etc/environment将此文件添加到您的帐户或系统范围。|offset|length|style|CODE|138400|然后在bin中创建它的链接|138401|sudo+ln+-s+/your_android_sdk_path/platform-tools/adb+/bin/adb|138402|如果您使用了adb设备或任何命令，则首先终止服务器，如下所示|138403|adb+kill-server|138404|然后像这样启动服务器|138405|adb+start-server
adb+devices|138406|现在您可以看到您的设备已正确列出，没有任何问题|138407|entityMap^0|0|0|S|9|14|A|1F|1F|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|13|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|14|8|@$I|15|J|16|K|L]|$I|17|J|18|K|L]|$I|19|J|1A|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|1B|8|@]|9|@]|A|$]]|$1|O|3|P|5|D|7|1C|8|@]|9|@]|A|$E|F]]|$1|Q|3|R|5|6|7|1D|8|@]|9|@]|A|$]]|$1|S|3|T|5|D|7|1E|8|@]|9|@]|A|$E|F]]|$1|U|3|V|5|6|7|1F|8|@]|9|@]|A|$]]|$1|W|3|X|5|D|7|1G|8|@]|9|@]|A|$E|F]]|$1|Y|3|Z|5|6|7|1H|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]]|11|$]]

I have face the same problem and i have resolved this by 
Adding the path of your_android_sdk_path to the environment variable like

<pre><code>sudo export $PATH:/your_android_sdk_path/platform-tools/adb
</code></pre>

its your wish how you want to add this to your account or system wide by editing these file <code>~/.bashrc</code> file or <code>~/.profile</code> 
or
<code>/etc/profile, /etc/bash.bashrc, or /etc/environment</code> if u want to add to system wide access.

and then create the link of that in bin 

<pre><code>sudo ln -s /your_android_sdk_path/platform-tools/adb /bin/adb
</code></pre>

if you have used adb devices or any command then first kill the server like

<pre><code>adb kill-server
</code></pre>

then start the server like

<pre><code>adb start-server
adb devices
</code></pre>

now you can see your devices are listed properly without an issue

blocks|key|139690|text|我更新了之前连接正常的设备(Nvidia+Shield)，因此我知道PC设置已经正确。开发者设置似乎在Android7.0上有了新的布局。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|139691|它位于设置>首选项>开发人员选项>网络>选择USB配置下|139692|在这里，我需要选择PTP，一切都可以正常工作了：|139693|​|139694|📷|atomic|offset|length|139695|139696|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/726624037eb4fc27d1aa01ccdf27ab21.png|imageAlt^0|0|0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Z|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|10|8|@]|9|@$K|11|L|12|1|13]]|A|$]]|$1|M|3|G|5|6|7|14|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U|V|-4]]]]

I updated my device (Nvidia Shield) that was previously connecting fine, so I knew that the PC setup is correct already. The developer settings seem to have a new layout on Android 7.0.

It is under Settings > Preferences > Developer options > Networking > Select USB configuration

Here, I needed to select PTP and everything works fine again:

<a href="https://i.stack.imgur.com/RifOR.png" rel="noreferrer"><img src="https://i.stack.imgur.com/RifOR.png" alt="Selecting USB configuration mode "></a>

blocks|key|2924323|text|正如错误消息所说，这是一个权限不足的问题。根据我的经验，它只发生在我的Linux机器上，并且在MacOS和Windows上运行得很好。使用root权限启动Android+Studio可以避免这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2924324|$sudo+/your_android_studio_path/bin/studio.sh|code-block|syntax|javascript|2924325|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

As the error message said, it is a permission insufficient problem. In my experience, it only happened on my Linux machine, and works well on MacOS and Windows. Launching your Android Studio with root permission could avoid this problem.

<pre><code>$sudo /your_android_studio_path/bin/studio.sh
</code></pre>

blocks|key|138431|text|这很简单。只需更改您的USB模式为文件传输模式，然后它就可以工作了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|138432|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

It's simple.
Just change your USB mode to File Transfer mode then it works.

blocks|key|140760|text|安卓8|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|140761|MTP不再可用。在我的android+8上，“传输文件”选项不起作用。|140762|"Transfer+photos“工作正常，Studio显示设备名称。|140763|140764|Steps+on+your+|unordered-list-item|140765|140766|1.+Open+the+developer+options
2.+Enable+USB+debugging.
3.+change+USB+connection+to+PTP|code-block|syntax|javascript|140767|​|140768|Linux上的|140769|步骤|140770|140771|1.+on+console+run+`sudo+usermod+-aG+plugdev+$LOGNAME`|140772|140773|安卓9|140774|对于Android9，使用选项File+Transfer。|CODE|140775|entityMap^0|0|3|0|0|0|0|0|0|0|0|0|0|0|0|0|0|3|0|F|D|0^^$0|@$1|2|3|4|5|6|7|1A|8|@$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1D|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|1E|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]|$1|K|3|L|5|M|7|1G|8|@]|D|@]|E|$]]|$1|N|3|-4|5|6|7|1H|8|@]|D|@]|E|$]]|$1|O|3|P|5|Q|7|1I|8|@]|D|@]|E|$R|S]]|$1|T|3|U|5|6|7|1J|8|@]|D|@]|E|$]]|$1|V|3|W|5|6|7|1K|8|@]|D|@]|E|$]]|$1|X|3|Y|5|M|7|1L|8|@]|D|@]|E|$]]|$1|Z|3|-4|5|6|7|1M|8|@]|D|@]|E|$]]|$1|10|3|11|5|Q|7|1N|8|@]|D|@]|E|$R|S]]|$1|12|3|U|5|6|7|1O|8|@]|D|@]|E|$]]|$1|13|3|14|5|6|7|1P|8|@$9|1Q|A|1R|B|C]]|D|@]|E|$]]|$1|15|3|16|5|6|7|1S|8|@$9|1T|A|1U|B|17]]|D|@]|E|$]]|$1|18|3|-4|5|6|7|1V|8|@]|D|@]|E|$]]]|19|$]]

Android 8

MTP is no longer available. On my android 8 "Transfer Files" option did not work.

"Transfer photos PTP" Is worked, and Studio showed the device name.

<ul>
<li>Steps on your cell phone

<ol>
<li>Open the developer options</li>
<li>Enable USB debugging.</li>
<li>change USB connection to PTP</li>
</ol></li>
<li>Steps on Linux

<ol>
<li>on console run <code>sudo usermod -aG plugdev $LOGNAME</code></li>
</ol></li>
</ul>

Android 9

With Android 9 use the option <code>File Transfer</code>.

blocks|key|138447|text|他妈的是什么..。！:)注:我在One%2B5t上的Android8.1上见过它...|type|unstyled|depth|inlineStyleRanges|entityRanges|data|138448|即使我们做了以上所有的事情，在你的android设备上制作一些东西也是必要的。除了进入开发选项菜单(usb调试)(不要犹豫重置“取消授权”或类似的东西(我是法语版本;)+)|138449|如果有些人遇到了和我一样的问题，也许这对你也很有用:不要忘记授权你手机中的设备(如果你不选择always框，每次在android设备上进行usb连接)。此外，您可以在手机上禁用旧的授权设备，并从适当的参数开始，以便在您的android设备上清晰地授权您的pc|138450|当您连接android设备时，弹出窗口或通知要求对设备的mac地址或等效地址进行授权:如果您要授权linux+pc与android设备之间的连接，请对其进行授权。|138451|当你使用连接usb数据线时，有必要在你的android设备上获得自动认证(如果你不是一直接受，但如果这是第一次出现在你的设备上)如果你不这样做，adb设备会显示unauthorized，即使所有权利都是好的(666，UDEV等)|138452|备注:感谢您的宝贵帮助。最后一件事，对不起，我的英语|138453|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

What the F... ! :)
Note : I have seen it on android 8.1 on a One+5t...

Even we do all of above, it is necessary to make something on your android device .. in addition to go in dev options menu (usb debug) (don't hesitate to reset "cancel authorization" or something like this (I am in french version ;) )

If some people meet the same problem than me, maybe it could be usefull for you too :
Don't forget to authorize devices in your phone (each time of usb connect on the android device if you don't select always box). Beside, you can suppress the old authorized devices on your phone and start with proper parameter to authorize clearly your pc on your android device

When you connect the android device, a pop up or notification ask to authorize a mac address or equivalent to the device : authorize it if you want to authorize connection between your linux pc and your android device.

It is necessary to obtain autorisation on your android device when you use connect the usb cable (if you don't accept all the time but if it is the first time this box is going to appear on your devices) if you don't do it, adb devices show unauthorized even all rights are good (666, UDEV etc)

Note : thank you for your precious help.
A last thing, sorry for my english

blocks|key|141968|text|我为这个错误写了一个脚本。对我来说，它在Fedora28中工作得很好，但它应该可以在许多Linux发行版中工作。只需使用自展开脚本的内容创建一个文件。我管它叫usbDebbugingAndroidStudio.sh|type|unstyled|depth|inlineStyleRanges|entityRanges|data|141969|向他授予执行权限：chmod+%2Bx+usbDebbugingAndroidStudio.sh|offset|length|style|CODE|141970|然后运行它：sudo+./usbDebbugingAndroidStudio.sh|141971|之后，检查命令lsusb显示的列表，并介绍您的设备Id。|141972|脚本：|141973|#!/usr/bin/env+bash


#This+script+configure+Android+Debug+Bridge+permissions+to+solve+the+following
#error:+com.android.ddmlib.AdbCommandRejectedException:+insufficient+permissions+for+device
#This+error+is+produced+when+you+try+to+install+an+APK+from+Android+Studio+in+your+device.
#You+can+check+the+vendorId+here:
#https://developer.android.com/studio/run/device#setting-up
#If+your+device's+brand+isn't+listed+check+the+info+displayed+by+the+command+lsusb

lsusb
#My+output+was:
#Bus+006+Device+002:+ID+05c6:9091+Qualcomm,+Inc.
#The+id+for+this+line+is+05c6
echo+-n+"Enter+the+id+of+your+mobile+device:+"
read+usbProviderId
cd+/etc/udev/rules.d/
sudo+touch+51-android.rules
(
sudo+cat+<<+_EOF_
SUBSYSTEM=="usb",+ATTR{idVendor}=="$usbProviderId",+MODE="0666",+GROUP="plugdev"
_EOF_
)+%7C+sudo+tee+51-android.rules

#Give+read+and+write+permissions+to+the+file
sudo+chmod+a%2Br+/etc/udev/rules.d/51-android.rules

#Kill+the+Android+Debug+Bridge+server+to+restart+it
cd+$HOME/Android/Sdk/platform-tools
sudo+./adb+kill-server

#If+this+still+doesn't+work+unplug+the+usb+cable+and+connect+again.
#And+repeat+the+last+step+Kill+the+ADB+server.|code-block|syntax|javascript|141974|entityMap^0|0|9|11|0|6|Z|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@$D|W|E|X|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|Y|8|@$D|Z|E|10|F|G]]|9|@]|A|$]]|$1|J|3|K|5|6|7|11|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|12|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|13|8|@]|9|@]|A|$Q|R]]|$1|S|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|T|$]]

I made a script for this error. For me it works fine in Fedora 28, but it should work in many Linux distributions. 
Just create a file with the content of the selfexpanied script. I called it usbDebbugingAndroidStudio.sh 
Give him execution permission with: <code>chmod +x usbDebbugingAndroidStudio.sh</code> 

And run it: <code>sudo ./usbDebbugingAndroidStudio.sh</code>

After that check the list displayed by the command lsusb and introduce the Id of
your device.
For example:
My output was: <code>Bus 006 Device 002: ID 05c6:9091 Qualcomm, Inc.</code>
So I type <code>05c6</code> and press enter.

The script:

<pre><code>#!/usr/bin/env bash


#This script configure Android Debug Bridge permissions to solve the following
#error: com.android.ddmlib.AdbCommandRejectedException: insufficient permissions for device
#This error is produced when you try to install an APK from Android Studio in your device.
#You can check the vendorId here:
#https://developer.android.com/studio/run/device#setting-up
#If your device's brand isn't listed check the info displayed by the command lsusb

lsusb
#My output was:
#Bus 006 Device 002: ID 05c6:9091 Qualcomm, Inc.
#The id for this line is 05c6
echo -n "Enter the id of your mobile device: "
read usbProviderId
cd /etc/udev/rules.d/
sudo touch 51-android.rules
(
sudo cat &lt;&lt; _EOF_
SUBSYSTEM=="usb", ATTR{idVendor}=="$usbProviderId", MODE="0666", GROUP="plugdev"
_EOF_
) | sudo tee 51-android.rules

#Give read and write permissions to the file
sudo chmod a+r /etc/udev/rules.d/51-android.rules

#Kill the Android Debug Bridge server to restart it
cd $HOME/Android/Sdk/platform-tools
sudo ./adb kill-server

#If this still doesn't work unplug the usb cable and connect again.
#And repeat the last step Kill the ADB server.
</code></pre>

blocks|key|2924514|text|在我的情况下：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2924515|cd+/etc/udev/rules.d/
sudo+chmod+a%2Br+./*.rules++#the+name+of+your+rules+files.|code-block|syntax|javascript|2924516|然后，我可以使用adb而不会出现这个错误。|2924517|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

In my situation:

<pre><code>cd /etc/udev/rules.d/
sudo chmod a+r ./*.rules #the name of your rules files.
</code></pre>

Then,I can use adb without this error.

blocks|key|141976|text|如果被接受的答案对你不起作用，那么只需简单地遵循以下步骤:打开你的android演播室终端：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|141977|adb+kill-server|141978|adb启动-服务器|141979|这对我很管用。|141980|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

if accepted answer not worked for you then just simple follow steps:
 Just open your android studio terminal:-

adb kill-server

adb start-server

it worked for me.

blocks|key|2924534|text|这个过程为我解决了这个问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2924535|-+On+the+Android+device,+drag+the+top+menu+and+select+"USB+for+file+transfer"
-+Press+"Run"+again|code-block|syntax|javascript|2924536|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This procedure solves the problem for me:

<pre><code>- On the Android device, drag the top menu and select "USB for file transfer"
- Press "Run" again
</code></pre>

blocks|key|2924565|text|启用USB+debugging|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|2924566|Use+USB+to+transer+file|unordered-list-item|2924567|
+|2924568|2924569|2924570|entityMap^0|2|D|2|D|0|B|C|B|C|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|D]]|E|@]|F|$]]|$1|G|3|H|5|I|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|D]]|E|@]|F|$]]|$1|J|3|K|5|6|7|Z|8|@]|E|@]|F|$]]|$1|L|3|-4|5|I|7|10|8|@]|E|@]|F|$]]|$1|M|3|-4|5|6|7|11|8|@]|E|@]|F|$]]|$1|N|3|-4|5|6|7|12|8|@]|E|@]|F|$]]]|O|$]]

<ul>
<li>Enable <code>USB debugging</code></li>
<li>Use USB to <code>transer file</code></li>
</ul>

blocks|key|140926|text|转到Developer+Options+->+Default+USB+Configurations并更改为PTP|type|unstyled|depth|inlineStyleRanges|entityRanges|data|140927|在终端中运行这两个命令|140928|+sudo+adb+kill-server
+sudo+adb+start-server|code-block|syntax|javascript|140929|应该行得通！|140930|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|O|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Go to Developer Options -> Default USB Configurations and Change to PTP

Run these two commands in terminal

<pre><code> sudo adb kill-server
 sudo adb start-server
</code></pre>

Should Work!

blocks|key|2711982|text|在不运行Linux+sudo+apt-get的情况下安装adb。不要忘记启用USB调试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2711983|参考：https://developer.android.com/studio/run/device|offset|length|2711984|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.android.com/studio/run/device^0|0|3|1B|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

Without running Linux
sudo apt-get install adb. Don't forget to enable USB debugging.
Ref: <a href="https://developer.android.com/studio/run/device" rel="nofollow noreferrer">https://developer.android.com/studio/run/device</a>

blocks|key|140941|text|当我从android+studio+4.1运行flutter应用程序时，我遇到了这个问题，我确实拔掉了usb电缆，并插入了第二个usb端口，它正在工作:)，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|140942|我写这篇文章，如果有人遇到同样的问题，他们可以得到帮助。|140943|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I'm facing this issue while run flutter app from android studio 4.1, i did remove usb cable and plug into second usb port and its working :),
I'm writing this if someone face same issue then they can get help.

blocks|key|140955|text|在Fedora32上也有同样的问题，要解决这个问题，可以尝试这样做：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|140956|adb+kill-server
adb+start-server|code-block|syntax|javascript|140957|entityMap^0|1|8|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|P|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|L|$]]

Same issue on Fedora 32, to fix this try this:
<pre class="lang-sh prettyprint-override"><code>adb kill-server
adb start-server
</code></pre>

I have a rooted Motorola Defy+ running a Cyanogenmod v11 custom ROM (nightly build) created by <a href="http://quarx2k.ru/">Quarx</a>. Using Android Studio Workspace,(ASW) v.1.1.0, when I try and debug on this device, I get 

<pre><code>????????????[null]
</code></pre>

listed in the Choose Device window, with the Logcat window showing 

<pre><code>insufficient permissions for device
</code></pre>

I would really like to use this device and ROM for debugging purposes.

When I enter <code>lsusb</code> from the command line I get,

<pre><code>Bus 002 Device 002: ID 22b8:431d Motorola PCS
</code></pre>

This is the correct device id for Motorola units. I have installed 51-android.rules and 71-android.rules in <code>/etc/udev/rules.d/</code> with the correct Motorola ids in these files.

I've also tried Revoke USB debugging authority, from Developer Options on the device, with no luck.

I have not tried running ASW as root hoping that there might be another option; is there?

Update: I was able to get in and access ADB by

<pre><code>uvachem-gsmith2:/home/greg/Android/Sdk/platform-tools # ./adb
</code></pre>

I then did a kill server, did an SU to root user and restarted the server. I then tried to connect to the device from Android Studio. Got a message on the device about accepting the RSA key from the PC, said "Yes" and then was able to deploy the app to the device. So back to my original question, Is there another way to access this device without logging in as root? It seems as if there is a permission issue on the phone file system that is preventing this...

Update #2 The core problem here was a permission thing. Even though running ADB as root will allow access to the rooted Android device, a better solution is to change permissions in the udev file for this device...resetting 664 to 666, (see answer below). This allows the PC to access the file system on the device.

Insufficient permissions for device in Android Studio Workspace running in openSUSE 13.2

Android Studio

文件系统

服务器

Android

Windows

Debian

Linux

MacOS

我有一个有根的摩托罗拉Defy+运行一个由创建的Cyanogenmod v11自定义ROM (夜间构建)。使用Android Studio Workspace，(ASW) v.1.1.0，当我尝试在这个设备上调试时，我得到????????????[null]在选择设备窗口中列出，并显示Logcat窗口insuffici...

问在openSUSE 13.2中运行的Android Studio Workspace中的设备权限不足
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在openSUSE 13.2中运行的Android Studio Workspace中的设备权限不足EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在openSUSE 13.2中运行的Android Studio Workspace中的设备权限不足
EN