You are not logged in.
Pages: 1
Hello,
My problem is, that after some time (ie. if I leave the pc on overnight) my system stops recognizing every Android device as adb-debugable. If I reboot my system it works as expected, but this is annoying.
I want to get to the core reason why this happens, because I haven't this problem on my other arch systems. I hope someone can give me a clue on what happens.
I'm using xfce4 desktop.
I have the android-udev package installed with rules like this:
# Skip this section below if this device is not connected by USB
SUBSYSTEM!="usb", GOTO="android_usb_rules_end"
LABEL="android_universal_rule"
ENV{ID_USB_INTERFACES}!="*:ff420?:*", GOTO="android_usb_rules_begin"
ACTION=="add", SUBSYSTEM=="usb", ENV{DEVTYPE}=="usb_device", ENV{ID_USB_INTERFACES}=="*:ff420?:*", MODE="0660", GROUP="adbusers", SYMLINK+="android/$env{ID_SERIAL_SHORT}"
...
# Google
ATTR{idVendor}!="18d1", GOTO="not_Google"
ENV{adb_user}="yes"
# Nexus, Pixel, Pixel XL, Pixel 2, Pixel 2XL (4ee2=mtp,adb 4ee4=rndis,adb 4ee6=ptp,adb 4ee7=adb 4ee9=midi,adb 2d01=accessory,adb 2d03=audio_source,adb 2d05=accessory,audio_source,adb)
# See [url]https://android.googlesource.com/device/google/wahoo/+/master/init.hardware.usb.rc[/url]
ATTR{idProduct}=="4ee2", SYMLINK+="android_adb"
ATTR{idProduct}=="4ee4", SYMLINK+="android_adb"
ATTR{idProduct}=="4ee6", SYMLINK+="android_adb"
ATTR{idProduct}=="4ee7", SYMLINK+="android_adb"
ATTR{idProduct}=="4ee9", SYMLINK+="android_adb"
...I'm currently in that state, so I post some outputs that might help:
Plugged in a Pixel3a.
lsusb:
Bus 003 Device 002: ID 8087:8000 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 004: ID 2109:0812 VIA Labs, Inc. VL812 Hub
Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 005: ID 0bda:0184 Realtek Semiconductor Corp. RTS5182 Card Reader
Bus 002 Device 041: ID 18d1:4ee7 Google Incudevadm monitor
KERNEL[86153.580810] add /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.1/2-3.1.3 (usb)
KERNEL[86153.587265] add /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.1/2-3.1.3/2-3.1.3:1.0 (usb)
KERNEL[86153.587381] bind /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.1/2-3.1.3 (usb)
UDEV [86153.595529] add /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.1/2-3.1.3 (usb)
UDEV [86153.596603] add /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.1/2-3.1.3/2-3.1.3:1.0 (usb)
UDEV [86153.600583] bind /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.1/2-3.1.3 (usb)dmesg:
L88016.212590] usb 2-3.1.3: new high-speed USB device number 47 using xhci_hcd
[88016.319377] usb 2-3.1.3: New USB device found, idVendor=18d1, idProduct=4ee7, bcdDevice= 4.40
[88016.319382] usb 2-3.1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[88016.319385] usb 2-3.1.3: Product: Pixel 3a XL
[88016.319388] usb 2-3.1.3: Manufacturer: Google
[88016.319390] usb 2-3.1.3: SerialNumber: 947AX0CWY8ls -l /dev/bus/usb/002/047 :
crw-rw----+ 1 root adbusers 189, 174 Jun 27 10:38 /dev/bus/usb/002/047groups:
http lock network power localusers adbusers systemd-journal users disk audio wheel dialoutcommon "solutions" do not work, like replugging, or toggling usb-debugging settings in the device
I need to restart now, but If there is something I can post beeing in that state I will do next time I'm in it.
Last edited by Ruffman (2019-06-27 22:08:35)
Offline
this is what changed after a fresh restart:
lsusb:
Bus 003 Device 002: ID 8087:8000 Intel Corp.
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 003: ID 2109:0812 VIA Labs, Inc. VL812 Hub
Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 005: ID 0bda:0184 Realtek Semiconductor Corp. RTS5182 Card Reader
Bus 002 Device 011: ID 18d1:4ee7 Google Inc.udevadm monitor
KERNEL[423.007785] add /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.1/2-3.1.3 (usb)
KERNEL[423.010514] add /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.1/2-3.1.3/2-3.1.3:1.0 (usb)
KERNEL[423.010606] bind /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.1/2-3.1.3 (usb)
UDEV [423.017286] add /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.1/2-3.1.3 (usb)
UDEV [423.018681] add /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.1/2-3.1.3/2-3.1.3:1.0 (usb)
UDEV [423.023663] bind /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.1/2-3.1.3 (usb)
KERNEL[423.207698] bind /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.1/2-3.1.3/2-3.1.3:1.0 (usb)
UDEV [423.208834] bind /devices/pci0000:00/0000:00:14.0/usb2/2-3/2-3.1/2-3.1.3/2-3.1.3:1.0 (usb)Last edited by Ruffman (2019-06-27 22:09:07)
Offline
Please edit your posts and use [ code ] tags when posting output.
https://wiki.archlinux.org/index.php/Co … s_and_code
https://bbs.archlinux.org/help.php#bbcode
Offline
Thanks, somehow I looked and wasn't able to find the bbcode. Am not using forums frequently ![]()
I updated my post and readability is day n night. Maybe I'm lucky and someone is familiar with my problem
Offline
Hmm,
Is there something wrong with my post? Are Logs/programm outputs missing? Something I can do better?
I would be happy about any clue someone might have...
Offline
Ruffman,
First an aside -- a link to BBCode information is located below message post boxes on the forums right under the lower left corner.
I don't have any rules specifically for Android, and it just works. Why do you need a rule for Android?
Edit: And, no, your posts are fine. I have a feeling that no one else (myself included) can replicate the issue.
Last edited by ewaller (2019-06-28 15:14:50)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
The shortest way to ruin a country is to give power to demagogues.— Dionysius of Halicarnassus
---
How to Ask Questions the Smart Way
Online
Pages: 1