You are not logged in.
When I try to connect my phone to laptop, the phone don't display notification connect usb like when I'm using window.
So I run lsusb and don't see any thing about my phone.
Then I get some info about dmesg.
$ dmesg
...
[ 145.043317] usb 2-1.2: new full-speed USB device number 10 using ehci_hcd
[ 145.109813] usb 2-1.2: device descriptor read/64, error -32
[ 145.296245] usb 2-1.2: device descriptor read/64, error -32
[ 145.485927] usb 2-1.2: new full-speed USB device number 11 using ehci_hcd
[ 145.552474] usb 2-1.2: device descriptor read/64, error -32
[ 145.738730] usb 2-1.2: device descriptor read/64, error -32
[ 145.925169] usb 2-1.2: new full-speed USB device number 12 using ehci_hcd
[ 146.330972] usb 2-1.2: device not accepting address 12, error -32
[ 146.434293] usb 2-1.2: new full-speed USB device number 13 using ehci_hcd
[ 146.840093] usb 2-1.2: device not accepting address 13, error -32
[ 146.865531] hub 2-1:1.0: unable to enumerate USB device on port 2
Can you suggest some solution? Thank you ^^.
Last edited by SuperBo (2012-06-15 14:29:51)
Offline
No suggestions. A few questions.
Make and Model of phone?
Are you using the same cable as that works on Windows?
Is it the same computer and port that works on Windows?
Have you played with any of the Andoid settings? Charge only versus connect as USB storage device. Try enabling USB debugging.
Version of Andoid?
Arch Linux Kernel version?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Phone: Samsung Galaxy S2 GT-I9100, AOKP 4.0.4
Laptop: Linux 3.3.8-1-ARCH
I have already enabled USB debugging mode in android, and set usb connection is MTP.
I use same cable and same port that works on windows.
Offline
Do you have this AUR package installed?
Offline
Yes, I installed android-udev.
I think my problem is that Linux can't enumerate USB port to connect to my phone, not about udev.
I think my device should be list as usb device when I run lsusb without udev rules.
Offline
I have the exact same phone, but not rooted and no ics and everything works fine. One thing I noticed is if the usb cable is plugged into the computer first and then the phone, it doesn't get detected at all. But the other way around does. Plus mine is detected as mass storage, not mtp.
Offline
Yes, I installed android-udev.
I think my problem is that Linux can't enumerate USB port to connect to my phone, not about udev.
I think my device should be list as usb device when I run lsusb without udev rules.
Did you add yourself to the adbusers group too?
Offline
Unfortunately, the OP has a problem at the lowest level of the protocol. The device and the hub are failing to negotiate and are not establishing a connection. None of the endpoints the phone can provide can be established. As such, the services defined by andoid-udev are moot; the endpoints just never appear.
SuperBo: When you make the connection, are there any messages of interest appended to /var/log/everything.log ?
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
I have very similar errors but they are about a logitech USB webcam (one of the cheap models).
It used to work 3 days ago, but I hadn't updated in a few days and I did that yesterday. it still works in windows by the way. The relevant parts of dmesg :
[ 292.184179] usb 1-4.4.3: new full-speed USB device number 15 using ehci_hcd
[ 292.254177] usb 1-4.4.3: device descriptor read/64, error -32
[ 292.427179] usb 1-4.4.3: device descriptor read/64, error -32
[ 292.597178] usb 1-4.4.3: new full-speed USB device number 16 using ehci_hcd
[ 292.667177] usb 1-4.4.3: device descriptor read/64, error -32
[ 292.841178] usb 1-4.4.3: device descriptor read/64, error -32
[ 293.011178] usb 1-4.4.3: new full-speed USB device number 17 using ehci_hcd
[ 293.416648] usb 1-4.4.3: device not accepting address 17, error -32
[ 293.484180] usb 1-4.4.3: new full-speed USB device number 18 using ehci_hcd
[ 293.889980] usb 1-4.4.3: device not accepting address 18, error -32
[ 293.891173] hub 1-4.4:1.0: unable to enumerate USB device on port 3
my USB controller is :
00:0b.0 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3)
00:0b.1 USB controller: NVIDIA Corporation MCP51 USB Controller (rev a3)
Last edited by SammyF (2012-06-17 09:02:03)
Offline
Have you had a look in the AUR repository there's one here
https://aur.archlinux.org/packages.php?ID=41856
and here:
Our enemies are your enemies, Nick. Disorder, war. It's just a matter of time before a dirty bomb goes off in Moscow, or an EMP fries Chicago. --- Alexander Pierce, Captain America: Winter Soldier
Access Denied! De-cryption failed, override denied all files sealed! --- Triskelion, Shield OS
-----
How to ask questions the smart way
Offline
SuperBo: Also, I don't think we have established if that port work for other devices under Arch Linux. I'm wondering if it might be a USB 3.0 port.
Could you post the output of lspci -nn (That is two n's, not m)
Thanks
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
ewaller: I try all port in my computer, but none of them works. My computer only support USB 2.0, .
$ lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Core Processor DRAM Controller [8086:0044] (rev 18)
00:01.0 PCI bridge [0604]: Intel Corporation Core Processor PCI Express x16 Root Port [8086:0045] (rev 18)
00:16.0 Communication controller [0780]: Intel Corporation 5 Series/3400 Series Chipset HECI Controller [8086:3b64] (rev 06)
00:1a.0 USB controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b3c] (rev 06)
00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b56] (rev 06)
00:1c.0 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 [8086:3b42] (rev 06)
00:1c.1 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 [8086:3b44] (rev 06)
00:1c.2 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 3 [8086:3b46] (rev 06)
00:1c.4 PCI bridge [0604]: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 5 [8086:3b4a] (rev 06)
00:1d.0 USB controller [0c03]: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller [8086:3b34] (rev 06)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev a6)
00:1f.0 ISA bridge [0601]: Intel Corporation Mobile 5 Series Chipset LPC Interface Controller [8086:3b0b] (rev 06)
00:1f.2 SATA controller [0106]: Intel Corporation 5 Series/3400 Series Chipset 6 port SATA AHCI Controller [8086:3b2f] (rev 06)
00:1f.3 SMBus [0c05]: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller [8086:3b30] (rev 06)
00:1f.6 Signal processing controller [1180]: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem [8086:3b32] (rev 06)
01:00.0 VGA compatible controller [0300]: Advanced Micro Devices [AMD] nee ATI Manhattan [Mobility Radeon HD 5400 Series] [1002:68e0]
01:00.1 Audio device [0403]: Advanced Micro Devices [AMD] nee ATI Cedar HDMI Audio [Radeon HD 5400/6300 Series] [1002:aa68]
12:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01)
13:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller [10ec:8136] (rev 02)
ff:00.0 Host bridge [0600]: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers [8086:2c62] (rev 05)
ff:00.1 Host bridge [0600]: Intel Corporation Core Processor QuickPath Architecture System Address Decoder [8086:2d01] (rev 05)
ff:02.0 Host bridge [0600]: Intel Corporation Core Processor QPI Link 0 [8086:2d10] (rev 05)
ff:02.1 Host bridge [0600]: Intel Corporation Core Processor QPI Physical 0 [8086:2d11] (rev 05)
ff:02.2 Host bridge [0600]: Intel Corporation Core Processor Reserved [8086:2d12] (rev 05)
ff:02.3 Host bridge [0600]: Intel Corporation Core Processor Reserved [8086:2d13] (rev 05)
I have solved problems ^^. I flashed SiyahKernel and it connect without problems.
This think this problem is about Fluxi kernel.
Thank for all support.
@SammyF
You can try load ohci and uhci and try connect again.
$ modprobe ohci_hcd
$ modprobe uhci_hcd
Offline
SuperBo, I flashed the Siyah Kernel too, and I see my device with lsusb, but I don't see mass storage in file manager... Is there something you did to make it appear in file manager? Will it not mount automatically?
joe@trusktr.io - joe at true skater dot io.
Offline
Did you update your system recently? Because the linux package (the Linux kernel) was updated as well.
Always reboot after a kernel update. Then USB devices will start working again.
I have made a personal commitment not to reply in topics that start with a lowercase letter. Proper grammar and punctuation is a sign of respect, and if you do not show any, you will NOT receive any help (at least not from me).
Offline
SuperBo, I flashed the Siyah Kernel too, and I see my device with lsusb, but I don't see mass storage in file manager... Is there something you did to make it appear in file manager? Will it not mount automatically?
If you want to use it as mass storage, go to System settings -> Storage -> USB computer connection -> Mass storage (default in ICS is mtp).
If you want to use as mtp device you can use libmtp and mtpfs or jmtpfs.
https://wiki.archlinux.org/index.php/Mtp
http://aur.archlinux.org/packages.php?ID=59408
http://forum.xda-developers.com/showthr … ?t=1643757
http://forum.xda-developers.com/showthr … 572&page=2
Offline
trusktr wrote:SuperBo, I flashed the Siyah Kernel too, and I see my device with lsusb, but I don't see mass storage in file manager... Is there something you did to make it appear in file manager? Will it not mount automatically?
If you want to use it as mass storage, go to System settings -> Storage -> USB computer connection -> Mass storage (default in ICS is mtp).
If you want to use as mtp device you can use libmtp and mtpfs or jmtpfs.https://wiki.archlinux.org/index.php/Mtp
http://aur.archlinux.org/packages.php?ID=59408
http://forum.xda-developers.com/showthr … ?t=1643757
http://forum.xda-developers.com/showthr … 572&page=2
I don't have a mass storage setting on my (rooted) S3 with stock firmware and kernel (ICS). I can only switch between mtp and ptp which does not work either.
jmtpfs does not work:
$ jmtpfs /mnt
Device 0 (VID=04e8 and PID=6860) is a Samsung GT P7310/P7510/N7000/I9070/I9100/I9300 Galaxy Tab 7.7/10.1/S2/S3/Nexus/Note/Y.
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
LIBMTP PANIC: failed to open session on second attempt
terminate called after throwing an instance of 'MtpErrorCantOpenDevice'
what(): Can't open device
seems to be the same problem as with mtpfs and libmtp.
Last edited by dieteric (2012-06-27 14:43:49)
Offline
May it be a faulty USB controller and/or driver? Some time ago I began to see similar issues with all of my USB hardware on my old laptop, both on Arch and on OpenBSD. Anyway, all the udev/MTP workarounds are not going to solve the problem anyway, as the USB link is needed for any kind of data transfers.
Last edited by czarkoff (2012-06-27 15:01:47)
Offline
I don't have a mass storage setting on my (rooted) S3 with stock firmware and kernel (ICS). I can only switch between mtp and ptp which does not work either.
jmtpfs does not work:
seems to be the same problem as with mtpfs and libmtp.
Do you install android-udev from AUR
https://aur.archlinux.org/packages.php?ID=51476
Or you can add udev rules manually.
https://wiki.archlinux.org/index.php/An … eal_device
Last edited by SuperBo (2012-06-29 04:55:42)
Offline
None of the above worked for me - installed the mtp and jmtpfs packages and android-udev from AUR. Still nothing ( no automounting) when I plug my S3 into the USB port. Typing "mtp-detect" results in the following:
Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note.
Found 1 device(s):
Samsung: GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note (04e8:6860) @ bus 2, dev 3
Attempting to connect device(s)
... but nothing else.
In the end I had to install the app "SGS3 Easy UMS": http://forum.xda-developers.com/showthr … ?t=1711009 and can now mount my external micro USB card (but not the internal one).
6.5.3.arch1-1(x86_64) w/Gnome 44.4
Arch on: ASUS Pro-PRIME x470, AMD 5800X3D, AMD 6800XT, 32GB, | Intel NUC 7i5RYK | ASUS ux303ua | Surface Laptop
Offline
None of the above worked for me - installed the mtp and jmtpfs packages and android-udev from AUR. Still nothing ( no automounting) when I plug my S3 into the USB port. Typing "mtp-detect" results in the following:
Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note. Found 1 device(s): Samsung: GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note (04e8:6860) @ bus 2, dev 3 Attempting to connect device(s)
... but nothing else.
.
Did you wait a litle bit? Once the device is detected, it will need 15-30 seconds to configure the transport.
MTP is a litle bit fancy, and not so easy to configure on Linux box and with Samsung devices. The MTP protocol was created by windows for windows media player, and is not easily suitable to Linux.
I would suggest this package: qtadb, from the AUR repo. Easy to install, and adb is a 100% reliable protocol to transfer data between your box and your device. I gave up with MTP.
If you still want MTP, give a look at the gmtp package in AUR too. It works good on my box.
On your device, did you to go settings > storage > settings menu (lower left key on my SGS2) > USB computer connection > check Media device (MTP). This is valid for Cyanogenmod ROM. Don't know where settings are for stock ROM.
Last edited by gabx (2012-06-30 10:05:35)
Offline
It takes about 1 minute after the connection attempt to throw the first error (same for mtp-detect, -connect, etc.). Then it tries to reset the usb interface, which doesn't help, so it fails again after another minute.
And yes, MTP is enabled on the phone. android-udev is installed. mtp-connect, mtp-detect, etc. all show the same error messages. jmtpfs, mtpfs, gmtp all do not work and have similar errors.
Offline
It takes about 1 minute after the connection attempt to throw the first error (same for mtp-detect, -connect, etc.). Then it tries to reset the usb interface, which doesn't help, so it fails again after another minute.
And yes, MTP is enabled on the phone. android-udev is installed. mtp-connect, mtp-detect, etc. all show the same error messages. jmtpfs, mtpfs, gmtp all do not work and have similar errors.
It maybe due to some physical issue then. Try to clean and brush your USB port and pin. I have read many times a dirty USB port could trigger weird issues.
Offline
sultanoswing wrote:None of the above worked for me - installed the mtp and jmtpfs packages and android-udev from AUR. Still nothing ( no automounting) when I plug my S3 into the USB port. Typing "mtp-detect" results in the following:
Listing raw device(s) Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note. Found 1 device(s): Samsung: GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note (04e8:6860) @ bus 2, dev 3 Attempting to connect device(s)
... but nothing else.
.
Did you wait a litle bit? Once the device is detected, it will need 15-30 seconds to configure the transport.
MTP is a litle bit fancy, and not so easy to configure on Linux box and with Samsung devices. The MTP protocol was created by windows for windows media player, and is not easily suitable to Linux.
I would suggest this package: qtadb, from the AUR repo. Easy to install, and adb is a 100% reliable protocol to transfer data between your box and your device. I gave up with MTP.If you still want MTP, give a look at the gmtp package in AUR too. It works good on my box.
On your device, did you to go settings > storage > settings menu (lower left key on my SGS2) > USB computer connection > check Media device (MTP). This is valid for Cyanogenmod ROM. Don't know where settings are for stock ROM.
Thanks for the reply. I wish I was as lucky as you in getting it working!
1) Yep - waited a bit, then after about a minute it times out with an error: "Attempting to connect device(s). TP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device" - then nothing.
2) I know - very annoying of Samsung / ICS to change from the more compatible setup - all in the name of windows users being able to have simultaneous access to media files. And this on a linux-based OS (android). Sigh.
3) I don't want MTP, but if it avoids a slightly ugly hack like Easy UMS that'd be preferable. gmtp also doesn't work. I plug in my device, hit "connect" in gmtp and get the following in the terminal I'm running gmtp from:
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note.
nothing happens and I have to ctrl-c the terminal process. It's interesting to note that (like mtp-detect) it doesn't correctly identify the Galaxy S3, which is I9300.
4) Yes - MTP mode is checked. I've also tried debugging and non-debugging modes for USB, and still nada.
5) USB cable and ports are scrupulously clean (and work with everything else)
6) I guess I, like others, will keep waiting/hoping native MTP will work soon!
Last edited by sultanoswing (2012-07-01 02:09:51)
6.5.3.arch1-1(x86_64) w/Gnome 44.4
Arch on: ASUS Pro-PRIME x470, AMD 5800X3D, AMD 6800XT, 32GB, | Intel NUC 7i5RYK | ASUS ux303ua | Surface Laptop
Offline
I wish I could help, as MTP is working, at least with GMTP GUI.
My device is SGS running CM9-Syiahkernel
My Arch box has a very standard setting level, so it may work on your. The mtpfs package IS NO installed on my machine, so it may be part of your isuue.
Please have a look here, and test:
https://github.com/hanwen/go-mtpfs/
Offline
I'd guess that there is an issue with the S3 (stock kernel?) and libmtp. Maybe I'll file a bug report later.
Last edited by dieteric (2012-07-01 10:28:33)
Offline