Fedora & Android

Paul Cartwright pbcartwright at gmail.com
Wed Jan 7 17:35:15 UTC 2015


On 01/07/2015 11:01 AM, poma wrote:
> On 07.01.2015 16:35, Paul Cartwright wrote:
>> On 01/07/2015 09:55 AM, poma wrote:
>>>>> List of devices attached
>>>>> 32009c90b9b96000    device
>>>>> e9139440    offline
>>>>>
>>>>> not sure what that means...
>>> /etc/udev/rules.d/100-adb.rules 
>>> SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ATTRS{idVendor}=="0bb4", MODE="0666"
>>>
>>> $ su -c "udevadm trigger --action=add"
>>>
>>> $ adb kill-server
>>>
>>> $ adb get-state
>>> * daemon not running. starting it now on port 5037 *
>>> * daemon started successfully *
>>> device
>>>
>>> $ adb devices
>>> List of devices attached 
>>> <Serial no.>	device
>>>
>>> $ adb shell
>>> shell@<Product>:/ $ uname -a                                                 
>>> Linux localhost 3.4.67 #1 SMP PREEMPT <build date> armv7l GNU/Linux
>> I didn't have that file, so I created it with that line...
>>
>> adb get-state
>> unknown
>> [root at localhost log]# adb devices
>> List of devices attached
>> e9139440    offline
>>
>> yet file manager shows the phone folder and I can browse my pictures...
>>
> ADB connection differs from USB_STORAGE/MTP/PTP.
> It's about managing devices, not just about sharing files.
>
>
> Ref.
> http://developer.android.com/tools/help/adb.html
>
so I disabled developer options, enabled it again, checked the USG
debugging box, and tried again. I still get:
adb: unable to connect for backup
adb: unable to connect for backup
adb: unable to connect for backup



-- 
Paul Cartwright
Registered Linux User #367800 and new counter #561587



More information about the users mailing list