You are not logged in.
Pages: 1
[jon@gm112 ~]$ lsusb
Bus 001 Device 007: ID 045e:0291 Microsoft Corp. Xbox 360 Wireless Receiver for Windows
Bus 003 Device 033: ID 046d:0825 Logitech, Inc. Webcam C270
Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 005 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 004 Device 004: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 004 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
Everything else on the hub shows up, but I cannot seem to find my Nexus 4. I have android-udev installed and I had no issues until around May when I reinstalled ArchLinux on the newer spin.. since then, I hadn't really had any luck with getting my Nexus 4 showing up. My issue is, because it's not being recongized by Linux itself, libmtp simply cannot communicate with my device.
Any suggestions as to what I can do? Help would be much appreciated
Offline
I've had "success" with other Nexus devices on Linux, but only with gomtpfs...
What is the output of
# mtp-detect
Also, make sure that your phone is set to use MTP and not PTP. And I don't know if it makes a difference (since I've always had it enabled on all of my devices), but see if having USB debugging enabled under the developer options makes any difference. Otherwise I have no clue if it's your system or Android keeping it from being detected.
One last thing, what exactly do you mean by
...I reinstalled ArchLinux on the newer spin
Edit: Forget what I said about making sure it's in MTP mode and having USB debugging enabled. I just tested with my Galaxy Nexus and lsusb showed it's connected even in PTP mode with USB debugging off...
Last edited by SolarBoyMatt (2013-06-19 21:34:19)
Offline
If you use kde, give kio-mtp a try, is a bit slow, but works out of the box for every device i've tested.
Offline
Standard stuff - check dmesg, try other ports, no hubs, etc.
If you are sure that it worked with some earlier kernel you can try git-bisect.
Offline
mtp-detect:
[jon@gm112 ~]$ mtp-detect
Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6
Listing raw device(s)
No raw devices found.
dmesg output: http://pastebin.com/vQUu9zKt
Alright well -- dmesg isn't showing anything regarding the phone so that confirms the OS does _not_ see the device at all (or unless I missed it). What is odd however, MTP does not work even on Windows 8 on the same computer with all of my ports tested. Yet, on my ultrabook it works just fine. Perhaps this is related to Android itself?
What I might do is reflash my phone's firmware and see if that gives me any luck. I'm starting to think that it's an Android issue, rather than anything else.
Thank you all for your help so far by the way.
Offline
Yeah, if you're using a custom rom, that could be an issue possibly. My Galaxy Nexus with stock Android 4.2 is detected just fine... However you say it works on another computer? If it wasn't detecting other USB devices fine, I'd say it's faulty USB ports... Very strange.
I did notice the wiki page for MTP says to run mtp-detect as root (not sure why), but I doubt that will change anything.
Offline
You tried connecting it on every usb port on your computer?
Asus M4A785TD-V ;; Phenom II X4 @ 3.9GHz ;; Ripjaws 12GB DDR3-1600 ;; 128GB Samsung 830 ;; MSI GTX460 v2 w/ blob ;; Arch Linux + KDE 4.x
Offline
[jon@gm112 ~]$ sudo mtp-detect
Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6
Listing raw device(s)
No raw devices found.
And no, this is actually stock Android. I figured there was no need to flash a custom ROM since stock was essentially vanilla Android + gapps anyways.
It's not that either. Everything else on the USB ports work perfectly fine. It's literally just my phone, which is why I am so puzzled. I was under the belief that maybe my front panel wasn't supplying the proper amperage to sustain a data connection, but nope. It's every USB port that seems to refuse the phone.
boast: Yes, I did. =\ OS doesn't seem to make a difference, but trying on a different computer does. I'm starting to suspect that there's something wrong with Android itself.
Oh and not even USB Debugging mode works. Literally it's power-only.
Offline
Can you try my udev rules?
SUBSYSTEM=="usb",ATTR{idVendor}=="18d1",ATTR{idProduct}=="4ee1",MODE="0666",SYMLINK+="mako_mtp"
SUBSYSTEM=="usb",ATTR{idVendor}=="18d1",ATTR{idProduct}=="4ee2",MODE="0666",SYMLINK+="mako_mtp+adb"
SUBSYSTEM=="usb",ATTR{idVendor}=="18d1",ATTR{idProduct}=="4ee0",MODE="0666",SYMLINK+="mako_fastboot"
SUBSYSTEM=="usb",ATTR{idVendor}=="18d1",ATTR{idProduct}=="d001",MODE="0666",SYMLINK+="mako_clockwork"
For ADB you need proper rules and build that supports 4.2.2. adb-git from aur works fine.
And flash CyanogenMod and Franco kernel, you will do yourself a favour.
Offline
Load a liveCD and see if its detected then?
Asus M4A785TD-V ;; Phenom II X4 @ 3.9GHz ;; Ripjaws 12GB DDR3-1600 ;; 128GB Samsung 830 ;; MSI GTX460 v2 w/ blob ;; Arch Linux + KDE 4.x
Offline
Pages: 1