8:17 p.m.
$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
** daemon still not running
error: cannot connect to daemon
$ ps -ef | grep adb
jd 19967 1 0 19:06 pts/3 00:00:00 adb -P 5037 fork-server
server
jd 19983 7405 0 19:09 pts/3 00:00:00 grep --color=auto adb
Android is 4.4.2 (nothing newer is available for my phone.
Developer option set. usb debugging enabled.
yet, when I plug my phone to usb on laptop,
laptop does not mount anything, nor does any icon
appear on the panel as a result of plugging in.
Also, the phone does not pop up a screen asking me
to enable USB in data mode or any other mode.
Any ideas?
9:58 p.m.
Allegedly, on or about 29 December 2015, jd1008 sent:
Android is 4.4.2 (nothing newer is available for my phone.
Developer option set. usb debugging enabled.
yet, when I plug my phone to usb on laptop,
laptop does not mount anything, nor does any icon
appear on the panel as a result of plugging in.
Also, the phone does not pop up a screen asking me
to enable USB in data mode or any other mode.
Recently I've had a few hours playing with an Android tablet (hideous
Laser thing). To get it talking with the computer over USB, I had to
fiddling around with its USB settings, I can't recall whether it was the
general tablet settings, or within its file browser. Go exploring.
--
[tim@localhost ~]$ uname -rsvp
Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64
Boilerplate: All mail to my mailbox is automatically deleted, there is
no point trying to privately email me, I only get to see the messages
posted to the mailing list.
Evolution keeps on telling me that it's refreshing, but I still want to
go and get a drink.
2:46 a.m.
On 12/30/2015 04:58 AM, Tim wrote:
Allegedly, on or about 29 December 2015, jd1008 sent:
> Android is 4.4.2 (nothing newer is available for my phone.
> Developer option set. usb debugging enabled.
>
> yet, when I plug my phone to usb on laptop,
> laptop does not mount anything, nor does any icon
> appear on the panel as a result of plugging in.
> Also, the phone does not pop up a screen asking me
> to enable USB in data mode or any other mode.
Recently I've had a few hours playing with an Android tablet (hideous
Laser thing). To get it talking with the computer over USB, I had to
fiddling around with its USB settings, I can't recall whether it was the
general tablet settings, or within its file browser. Go exploring.
I tried for weeks to get my Moto G connected then finally I tried with
the cable that came in the box with the phone and it worked immediately.
--
1:13 p.m.
On Tue, Dec 29, 2015 at 07:17:43PM -0700, jd1008 wrote:
$ adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
** daemon still not running
error: cannot connect to daemon
$ ps -ef | grep adb
jd 19967 1 0 19:06 pts/3 00:00:00 adb -P 5037 fork-server
server
jd 19983 7405 0 19:09 pts/3 00:00:00 grep --color=auto adb
Android is 4.4.2 (nothing newer is available for my phone.
Developer option set. usb debugging enabled.
yet, when I plug my phone to usb on laptop,
laptop does not mount anything, nor does any icon
appear on the panel as a result of plugging in.
Also, the phone does not pop up a screen asking me
to enable USB in data mode or any other mode.
On F22, my LG tablet connects using the mtp protocol.
However, I had to add it to the udev rules configuration file.
I copied /usr/lib/udev/rules.d/69-libmtp.rules to
/etc/udev/rules.d and edited the copy. I found
rules for tablets similar to my own and duplicated
them but with an appropriate name and with the vendor
and product id's I got from lsusb.
HTH,
Jon
--
Jon H. LaBadie jonfu(a)jgcomp.com
2:12 p.m.
On 12/30/2015 12:13 PM, Jon LaBadie wrote:
On Tue, Dec 29, 2015 at 07:17:43PM -0700, jd1008 wrote:
> $ adb devices
> * daemon not running. starting it now on port 5037 *
> * daemon started successfully *
>
> ** daemon still not running
> error: cannot connect to daemon
>
> $ ps -ef | grep adb
> jd 19967 1 0 19:06 pts/3 00:00:00 adb -P 5037 fork-server
> server
> jd 19983 7405 0 19:09 pts/3 00:00:00 grep --color=auto adb
>
> Android is 4.4.2 (nothing newer is available for my phone.
> Developer option set. usb debugging enabled.
>
> yet, when I plug my phone to usb on laptop,
> laptop does not mount anything, nor does any icon
> appear on the panel as a result of plugging in.
> Also, the phone does not pop up a screen asking me
> to enable USB in data mode or any other mode.
>
On F22, my LG tablet connects using the mtp protocol.
However, I had to add it to the udev rules configuration file.
I copied /usr/lib/udev/rules.d/69-libmtp.rules to
/etc/udev/rules.d and edited the copy. I found
rules for tablets similar to my own and duplicated
them but with an appropriate name and with the vendor
and product id's I got from lsusb.
HTH,
Jon
Tried it.
Still, laptop does not detect phone.
Phone is set to query the user for connection protocol when
usb is plugged in to both phone and laptop.
Phone does not prompt me with that question.
The file /etc/udev/rules.d/69-libmtp.rules,
does not have an entry for my phone model
(LG G Flex D959).
For example, I see the entry:
# LG Electronics Inc. LG G Flex 2
ATTR{idVendor}=="1004", ATTR{idProduct}=="633e",
SYMLINK+="libmtp-%k",
ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
but my phone is the LG G Flex (Generation 1), model D959.
Would a new line like:
ATTR{idVendor}=="1004", ATTR{idProduct}=="d959",
SYMLINK+="libmtp-%k",
ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
correctly represent my phone in this rules file?
2:18 p.m.
On 01/02/2016 01:12 PM, jd1008 wrote:
On 12/30/2015 12:13 PM, Jon LaBadie wrote:
> On Tue, Dec 29, 2015 at 07:17:43PM -0700, jd1008 wrote:
>> $ adb devices
>> * daemon not running. starting it now on port 5037 *
>> * daemon started successfully *
>>
>> ** daemon still not running
>> error: cannot connect to daemon
>>
>> $ ps -ef | grep adb
>> jd 19967 1 0 19:06 pts/3 00:00:00 adb -P 5037 fork-server
>> server
>> jd 19983 7405 0 19:09 pts/3 00:00:00 grep --color=auto adb
>>
>> Android is 4.4.2 (nothing newer is available for my phone.
>> Developer option set. usb debugging enabled.
>>
>> yet, when I plug my phone to usb on laptop,
>> laptop does not mount anything, nor does any icon
>> appear on the panel as a result of plugging in.
>> Also, the phone does not pop up a screen asking me
>> to enable USB in data mode or any other mode.
>>
> On F22, my LG tablet connects using the mtp protocol.
> However, I had to add it to the udev rules configuration file.
>
> I copied /usr/lib/udev/rules.d/69-libmtp.rules to
> /etc/udev/rules.d and edited the copy. I found
> rules for tablets similar to my own and duplicated
> them but with an appropriate name and with the vendor
> and product id's I got from lsusb.
>
> HTH,
> Jon
Tried it.
Still, laptop does not detect phone.
Phone is set to query the user for connection protocol when
usb is plugged in to both phone and laptop.
Phone does not prompt me with that question.
The file /etc/udev/rules.d/69-libmtp.rules,
does not have an entry for my phone model
(LG G Flex D959).
For example, I see the entry:
# LG Electronics Inc. LG G Flex 2
ATTR{idVendor}=="1004", ATTR{idProduct}=="633e",
SYMLINK+="libmtp-%k", ENV{ID_MTP_DEVICE}="1",
ENV{ID_MEDIA_PLAYER}="1"
but my phone is the LG G Flex (Generation 1), model D959.
Would a new line like:
ATTR{idVendor}=="1004", ATTR{idProduct}=="d959",
SYMLINK+="libmtp-%k", ENV{ID_MTP_DEVICE}="1",
ENV{ID_MEDIA_PLAYER}="1"
correctly represent my phone in this rules file?
Looking at udev via systemctl -l
# systemctl -l | grep udev
systemd-udev-settle.service loaded active exited udev Wait for
Complete Device Initialization
systemd-udev-trigger.service loaded active exited udev Coldplug all
Devices
systemd-udevd.service loaded active running udev Kernel Device Manager
systemd-udevd-control.socket loaded active running udev Control Socket
systemd-udevd-kernel.socket loaded active running udev Kernel Socket
Is there another udev service that needs to be running?
5:03 p.m.
On Sat, Jan 02, 2016 at 01:18:55PM -0700, jd1008 wrote:
On 01/02/2016 01:12 PM, jd1008 wrote:
>On 12/30/2015 12:13 PM, Jon LaBadie wrote:
>>On Tue, Dec 29, 2015 at 07:17:43PM -0700, jd1008 wrote:
...
>>>
>>>Android is 4.4.2 (nothing newer is available for my phone.
>>>Developer option set. usb debugging enabled.
>>>
>>>yet, when I plug my phone to usb on laptop,
>>>laptop does not mount anything, nor does any icon
>>>appear on the panel as a result of plugging in.
>>>Also, the phone does not pop up a screen asking me
>>>to enable USB in data mode or any other mode.
>>>
>>On F22, my LG tablet connects using the mtp protocol.
>>However, I had to add it to the udev rules configuration file.
>>
>>I copied /usr/lib/udev/rules.d/69-libmtp.rules to
>>/etc/udev/rules.d and edited the copy. I found
>>rules for tablets similar to my own and duplicated
>>them but with an appropriate name and with the vendor
>>and product id's I got from lsusb.
>>
>>HTH,
>>Jon
>Tried it.
>Still, laptop does not detect phone.
>Phone is set to query the user for connection protocol when
>usb is plugged in to both phone and laptop.
>Phone does not prompt me with that question.
>
>The file /etc/udev/rules.d/69-libmtp.rules,
>
>does not have an entry for my phone model
>(LG G Flex D959).
>
>For example, I see the entry:
>
># LG Electronics Inc. LG G Flex 2
>ATTR{idVendor}=="1004", ATTR{idProduct}=="633e",
SYMLINK+="libmtp-%k",
>ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
>
>but my phone is the LG G Flex (Generation 1), model D959.
>
>Would a new line like:
>
>ATTR{idVendor}=="1004", ATTR{idProduct}=="d959",
SYMLINK+="libmtp-%k",
>ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
>
>correctly represent my phone in this rules file?
Looking at udev via systemctl -l
# systemctl -l | grep udev
systemd-udev-settle.service loaded active exited udev Wait for Complete
Device Initialization
systemd-udev-trigger.service loaded active exited udev Coldplug all
Devices
systemd-udevd.service loaded active running udev Kernel Device Manager
systemd-udevd-control.socket loaded active running udev Control Socket
systemd-udevd-kernel.socket loaded active running udev Kernel Socket
Is there another udev service that needs to be running?
My system has the last 4 lines the same as yours. The first is
not present in my "# systemctl -l | grep udev" output.
A "systemctl status systemd-udev-settle.service" says it is loaded
but not active. A guess, perhaps it becomes active when a new
device is connected.
jl
--
Jon H. LaBadie jonfu(a)jgcomp.com
5:37 p.m.
On 01/02/2016 04:03 PM, Jon LaBadie wrote:
On Sat, Jan 02, 2016 at 01:18:55PM -0700, jd1008 wrote:
> On 01/02/2016 01:12 PM, jd1008 wrote:
>> On 12/30/2015 12:13 PM, Jon LaBadie wrote:
>>> On Tue, Dec 29, 2015 at 07:17:43PM -0700, jd1008 wrote:
...
>>>> Android is 4.4.2 (nothing newer is available for my phone.
>>>> Developer option set. usb debugging enabled.
>>>>
>>>> yet, when I plug my phone to usb on laptop,
>>>> laptop does not mount anything, nor does any icon
>>>> appear on the panel as a result of plugging in.
>>>> Also, the phone does not pop up a screen asking me
>>>> to enable USB in data mode or any other mode.
>>>>
>>> On F22, my LG tablet connects using the mtp protocol.
>>> However, I had to add it to the udev rules configuration file.
>>>
>>> I copied /usr/lib/udev/rules.d/69-libmtp.rules to
>>> /etc/udev/rules.d and edited the copy. I found
>>> rules for tablets similar to my own and duplicated
>>> them but with an appropriate name and with the vendor
>>> and product id's I got from lsusb.
>>>
>>> HTH,
>>> Jon
>> Tried it.
>> Still, laptop does not detect phone.
>> Phone is set to query the user for connection protocol when
>> usb is plugged in to both phone and laptop.
>> Phone does not prompt me with that question.
>>
>> The file /etc/udev/rules.d/69-libmtp.rules,
>>
>> does not have an entry for my phone model
>> (LG G Flex D959).
>>
>> For example, I see the entry:
>>
>> # LG Electronics Inc. LG G Flex 2
>> ATTR{idVendor}=="1004", ATTR{idProduct}=="633e",
SYMLINK+="libmtp-%k",
>> ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
>>
>> but my phone is the LG G Flex (Generation 1), model D959.
>>
>> Would a new line like:
>>
>> ATTR{idVendor}=="1004", ATTR{idProduct}=="d959",
SYMLINK+="libmtp-%k",
>> ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
>>
>> correctly represent my phone in this rules file?
> Looking at udev via systemctl -l
>
> # systemctl -l | grep udev
> systemd-udev-settle.service loaded active exited udev Wait for Complete
> Device Initialization
> systemd-udev-trigger.service loaded active exited udev Coldplug all
> Devices
> systemd-udevd.service loaded active running udev Kernel Device Manager
> systemd-udevd-control.socket loaded active running udev Control Socket
> systemd-udevd-kernel.socket loaded active running udev Kernel Socket
>
>
> Is there another udev service that needs to be running?
My system has the last 4 lines the same as yours. The first is
not present in my "# systemctl -l | grep udev" output.
A "systemctl status systemd-udev-settle.service" says it is loaded
but not active. A guess, perhaps it becomes active when a new
device is connected.
jl
Here is what systemctl -l shows after I connected the phone:
$ systemctl -l | grep udev
systemd-udev-settle.service loaded active exited udev Wait for
Complete Device Initialization
systemd-udev-trigger.service loaded active exited udev Coldplug all
Devices
systemd-udevd.service loaded active running udev Kernel Device Manager
systemd-udevd-control.socket loaded active running udev Control Socket
systemd-udevd-kernel.socket loaded active running udev Kernel Socket
So, it has been about 5-6 minutes since I plugged it in, and the the
udev settle service is still waiting for device init.
So, I disconnected it, and this is what I get from systemctl:
$ systemctl -l | grep udev
systemd-udev-settle.service loaded active exited udev Wait for
Complete Device Initialization
systemd-udev-trigger.service loaded active exited udev Coldplug all
Devices
systemd-udevd.service loaded active running udev Kernel Device Manager
systemd-udevd-control.socket loaded active running udev Control Socket
systemd-udevd-kernel.socket loaded active running udev Kernel Socket
So, no change!!!
6:35 p.m.
From what you've said neither the computer nor the
phone
seem to realize they are connected. Perhaps
it is cable problems? Either a bad cable or the
wrong type. I read about some phone that needed
a "usb serial" cable rather than a standard usb cable.
Other than that, I've got nothing.
Good luck and HNY!
jon
--
Jon H. LaBadie jonfu(a)jgcomp.com
7:56 p.m.
On 01/02/2016 05:35 PM, Jon LaBadie wrote:
From what you've said neither the computer nor the
phone seem to realize they are connected. Perhaps
it is cable problems? Either a bad cable or the
wrong type. I read about some phone that needed
a "usb serial" cable rather than a standard usb cable.
Other than that, I've got nothing.
Good luck and HNY!
jon
Well, these are the same cables I used on my previous phones
and they worked extremely well.
My phone is less than 2 years old, and looks like brand new.
Is there a way to debug the phone's usb DATA port?
Sort of like is there a diag device that can tell if the
USB port responds to queries.... etc?
8:01 p.m.
On 01/02/2016 05:56 PM, jd1008 wrote:
>
Well, these are the same cables I used on my previous phones
and they worked extremely well.
My phone is less than 2 years old, and looks like brand new.
Can you try using your phone with that cable on a different computer, or
borrow a cable to see what happens? One of Jerry Pournelle's laws of
computer troubleshooting is "Check the cables first."
8:11 p.m.
On 01/02/2016 07:01 PM, Joe Zeff wrote:
On 01/02/2016 05:56 PM, jd1008 wrote:
>>
> Well, these are the same cables I used on my previous phones
> and they worked extremely well.
> My phone is less than 2 years old, and looks like brand new.
Can you try using your phone with that cable on a different computer,
or borrow a cable to see what happens? One of Jerry Pournelle's laws
of computer troubleshooting is "Check the cables first."
Fair enough.
I will check that and get back to you.
9:47 p.m.
On 01/02/2016 06:11 PM, jd1008 wrote:
On 01/02/2016 07:01 PM, Joe Zeff wrote:
> On 01/02/2016 05:56 PM, jd1008 wrote:
>>>
>> Well, these are the same cables I used on my previous phones
>> and they worked extremely well.
>> My phone is less than 2 years old, and looks like brand new.
>
> Can you try using your phone with that cable on a different computer,
> or borrow a cable to see what happens? One of Jerry Pournelle's laws
> of computer troubleshooting is "Check the cables first."
Fair enough.
I will check that and get back to you.
have you added simple-mtpfs as one of your packages?
See https://wiki.archlinux.org/index.php/MTP
Until I added the udev rules, my phone would not mount
--
Joseph Loo
jloo(a)acm.org
12:29 p.m.
On 01/02/2016 08:47 PM, Joseph Loo wrote:
On 01/02/2016 06:11 PM, jd1008 wrote:
>
> On 01/02/2016 07:01 PM, Joe Zeff wrote:
>> On 01/02/2016 05:56 PM, jd1008 wrote:
>>> Well, these are the same cables I used on my previous phones
>>> and they worked extremely well.
>>> My phone is less than 2 years old, and looks like brand new.
>> Can you try using your phone with that cable on a different computer,
>> or borrow a cable to see what happens? One of Jerry Pournelle's laws
>> of computer troubleshooting is "Check the cables first."
> Fair enough.
> I will check that and get back to you.
>
have you added simple-mtpfs as one of your packages?
See https://wiki.archlinux.org/index.php/MTP
Until I added the udev rules, my phone would not mount
simple-mtpfs-0.2-3.fc22.x86_64 is already installed.
5:29 p.m.
Hi,
I know a lot of people mentioned about the cable, the only one that seems to
work for me is the cable that came with the phone.
I had this same issue before. Keep trying cables until I found one that worked.
It is a pain, but it happened in windows too with my father.
Regards,
Will W.
http://code-heads.com
12:15 a.m.
Allegedly, on or about 04 January 2016, Will W sent:
I know a lot of people mentioned about the cable, the only one that
seems to work for me is the cable that came with the phone.
With something like that, it makes me wonder whether there's a problem
with the contacts in the phone's socket, and some cables just make poor
connections.
--
[tim@localhost ~]$ uname -rsvp
Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64
Boilerplate: All mail to my mailbox is automatically deleted, there is
no point trying to privately email me, I only get to see the messages
posted to the mailing list.
I'd just like to say that vinyl record crackles and pops are far less
annoying than digigigigital mu-u-u-u-usic hiccicicicups and
yooo-----------------u tu-----be ....... pauses.
3:50 p.m.
On Tue, 5 Jan 2016, Tim wrote:
Date: Tue, 05 Jan 2016 16:45:18 +1030
From: Tim <ignored_mailbox(a)yahoo.com.au>
Reply-To: Community support for Fedora users <users(a)lists.fedoraproject.org>
To: users(a)lists.fedoraproject.org
Subject: Re: Cannot access my phone storage from fc22
Allegedly, on or about 04 January 2016, Will W sent:
> I know a lot of people mentioned about the cable, the only one that
> seems to work for me is the cable that came with the phone
With something like that, it makes me wonder whether there's a problem
with the contacts in the phone's socket, and some cables just make poor
connections.
I agree there but with genernic cables it works sometimes for me. It is weird
tho.
Regards,
Will W
4:41 p.m.
Will W <willw(a)code-heads.com> writes:
On Tue, 5 Jan 2016, Tim wrote:
> Date: Tue, 05 Jan 2016 16:45:18 +1030
> From: Tim <ignored_mailbox(a)yahoo.com.au>
> Reply-To: Community support for Fedora users <users(a)lists.fedoraproject.org>
> To: users(a)lists.fedoraproject.org
> Subject: Re: Cannot access my phone storage from fc22
>
> Allegedly, on or about 04 January 2016, Will W sent:
>> I know a lot of people mentioned about the cable, the only one that
>> seems to work for me is the cable that came with the phone
>
> With something like that, it makes me wonder whether there's a problem
> with the contacts in the phone's socket, and some cables just make poor
> connections.
I agree there but with genernic cables it works sometimes for me. It
is weird tho.
There are "charging-only" cables that intentionally leave out the data
wires. These are a good idea when you don't want some random charger at
a coffee shop or airport to download all your pictures and other data
while your phone is charging.
-wolfgang
5:52 p.m.
On Tue, 5 Jan 2016, Wolfgang S. Rupprecht wrote:
Date: Tue, 05 Jan 2016 14:41:55 -0800
From: Wolfgang S. Rupprecht <wolfgang.rupprecht(a)gmail.com>
Reply-To: Community support for Fedora users <users(a)lists.fedoraproject.org>
To: users(a)lists.fedoraproject.org
Subject: Re: Cannot access my phone storage from fc22
There are "charging-only" cables that intentionally leave out the data
wires. These are a good idea when you don't want some random charger at
a coffee shop or airport to download all your pictures and other data
while your phone is charging.
-wolfgang
Wolfgang,
You are right about that, I completely forgot about that. Thanks for reminding
me.
Regards,
Will W.
http://code-heads.com
12:06 a.m.
Wolfgang S. Rupprecht:
> There are "charging-only" cables that intentionally
leave out the data
> wires. These are a good idea when you don't want some random charger at
> a coffee shop or airport to download all your pictures and other data
> while your phone is charging.
Will W:
You are right about that, I completely forgot about that. Thanks for
reminding
me.
Hmm, if you've got a mixed collection, I'd label the charge-only cables,
and save yourself a bit of grief, later on.
--
[tim@localhost ~]$ uname -rsvp
Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64
Boilerplate: All mail to my mailbox is automatically deleted, there is
no point trying to privately email me, I only get to see the messages
posted to the mailing list.
Evolution keeps on telling me that it's refreshing, but I still want to
go and get a drink.
12:33 p.m.
On 01/03/2016 11:29 AM, jd1008 wrote:
On 01/02/2016 08:47 PM, Joseph Loo wrote:
> On 01/02/2016 06:11 PM, jd1008 wrote:
>>
>> On 01/02/2016 07:01 PM, Joe Zeff wrote:
>>> On 01/02/2016 05:56 PM, jd1008 wrote:
>>>> Well, these are the same cables I used on my previous phones
>>>> and they worked extremely well.
>>>> My phone is less than 2 years old, and looks like brand new.
>>> Can you try using your phone with that cable on a different computer,
>>> or borrow a cable to see what happens? One of Jerry Pournelle's laws
>>> of computer troubleshooting is "Check the cables first."
>> Fair enough.
>> I will check that and get back to you.
>>
> have you added simple-mtpfs as one of your packages?
>
> See https://wiki.archlinux.org/index.php/MTP
>
> Until I added the udev rules, my phone would not mount
>
simple-mtpfs-0.2-3.fc22.x86_64 is already installed.
Hi all,
My laptop is a dual boot (Win 7 and fc22).
Windows 7 connect to the phone with the cable I have.
My fc22 does not connect it. In fact here is what dmesg shows
upon connecting the cable:
[36382.710673] usb 2-1.1: new low-speed USB device number 11 using ehci-pci
[36382.785768] usb 2-1.1: device descriptor read/64, error -32
[36382.950717] usb 2-1.1: device descriptor read/64, error -32
[36383.124740] usb 2-1.1: new low-speed USB device number 12 using ehci-pci
[36383.188774] usb 2-1.1: device descriptor read/64, error -32
[36383.364796] usb 2-1.1: device descriptor read/64, error -32
[36383.538832] usb 2-1.1: new low-speed USB device number 13 using ehci-pci
[36383.940802] usb 2-1.1: device not accepting address 13, error -32
[36384.013791] usb 2-1.1: new low-speed USB device number 14 using ehci-pci
[36384.415828] usb 2-1.1: device not accepting address 14, error -32
[36384.416013] usb 2-1-port1: unable to enumerate USB device
[36408.824705] usb 2-1.1: new low-speed USB device number 15 using ehci-pci
[36408.899735] usb 2-1.1: device descriptor read/64, error -32
[36414.534150] usb 2-1.1: new low-speed USB device number 16 using ehci-pci
[36414.609101] usb 2-1.1: device descriptor read/64, error -32
[36414.786141] usb 2-1.1: device descriptor read/64, error -32
[36414.960190] usb 2-1.1: new low-speed USB device number 17 using ehci-pci
[36415.024181] usb 2-1.1: device descriptor read/64, error -32
[36415.200169] usb 2-1.1: device descriptor read/64, error -32
[36415.374185] usb 2-1.1: new low-speed USB device number 18 using ehci-pci
[36415.776209] usb 2-1.1: device not accepting address 18, error -32
[36415.849241] usb 2-1.1: new low-speed USB device number 19 using ehci-pci
[36416.251248] usb 2-1.1: device not accepting address 19, error -32
[36416.251552] usb 2-1-port1: unable to enumerate USB device
[36417.529364] usb 2-1.1: new low-speed USB device number 20 using ehci-pci
[36417.604360] usb 2-1.1: device descriptor read/64, error -32
[36417.780415] usb 2-1.1: device descriptor read/64, error -32
[36417.956400] usb 2-1.1: new low-speed USB device number 21 using ehci-pci
[36418.031409] usb 2-1.1: device descriptor read/64, error -32
[36418.207428] usb 2-1.1: device descriptor read/64, error -32
[36418.381413] usb 2-1.1: new low-speed USB device number 22 using ehci-pci
[36418.783476] usb 2-1.1: device not accepting address 22, error -32
[36418.856478] usb 2-1.1: new low-speed USB device number 23 using ehci-pci
[36419.258488] usb 2-1.1: device not accepting address 23, error -32
[36419.258686] usb 2-1-port1: unable to enumerate USB device
[36425.722022] usb 2-1.1: new low-speed USB device number 24 using ehci-pci
[36425.796984] usb 2-1.1: device descriptor read/64, error -32
[36425.962026] usb 2-1.1: device descriptor read/64, error -32
[36426.136035] usb 2-1.1: new low-speed USB device number 25 using ehci-pci
[36426.200016] usb 2-1.1: device descriptor read/64, error -32
[36426.376073] usb 2-1.1: device descriptor read/64, error -32
[36426.550028] usb 2-1.1: new low-speed USB device number 26 using ehci-pci
[36426.952102] usb 2-1.1: device not accepting address 26, error -32
[36427.025066] usb 2-1.1: new low-speed USB device number 27 using ehci-pci
[36427.427154] usb 2-1.1: device not accepting address 27, error -32
Seems to me this is a problem with the drivers not my phone and not my
cable.
8:03 p.m.
On 01/02/2016 05:35 PM, Jon LaBadie wrote:
From what you've said neither the computer nor the
phone seem to realize they are connected. Perhaps
it is cable problems? Either a bad cable or the
wrong type. I read about some phone that needed
a "usb serial" cable rather than a standard usb cable.
Other than that, I've got nothing.
Good luck and HNY!
jon
Update:
I turned off USB debugging and suddenly, dmesg shows:
[23307.972810] usb 2-1.1: new low-speed USB device number 9 using ehci-pci
However, no new devices appear.
$ simple-mtpfs -l
No raw devices found.
4:58 p.m.
On Sat, Jan 02, 2016 at 01:12:36PM -0700, jd1008 wrote:
On 12/30/2015 12:13 PM, Jon LaBadie wrote:
>On Tue, Dec 29, 2015 at 07:17:43PM -0700, jd1008 wrote:
...
>>Android is 4.4.2 (nothing newer is available for my phone.
>>Developer option set. usb debugging enabled.
>>
>>yet, when I plug my phone to usb on laptop,
>>laptop does not mount anything, nor does any icon
>>appear on the panel as a result of plugging in.
>>Also, the phone does not pop up a screen asking me
>>to enable USB in data mode or any other mode.
>>
>On F22, my LG tablet connects using the mtp protocol.
>However, I had to add it to the udev rules configuration file.
>
>I copied /usr/lib/udev/rules.d/69-libmtp.rules to
>/etc/udev/rules.d and edited the copy. I found
>rules for tablets similar to my own and duplicated
>them but with an appropriate name and with the vendor
>and product id's I got from lsusb.
>
>HTH,
>Jon
Tried it.
Still, laptop does not detect phone.
Phone is set to query the user for connection protocol when
usb is plugged in to both phone and laptop.
Phone does not prompt me with that question.
The file /etc/udev/rules.d/69-libmtp.rules,
does not have an entry for my phone model
(LG G Flex D959).
For example, I see the entry:
# LG Electronics Inc. LG G Flex 2
ATTR{idVendor}=="1004", ATTR{idProduct}=="633e",
SYMLINK+="libmtp-%k",
ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
but my phone is the LG G Flex (Generation 1), model D959.
Would a new line like:
ATTR{idVendor}=="1004", ATTR{idProduct}=="d959",
SYMLINK+="libmtp-%k",
ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
correctly represent my phone in this rules file?
No, I said I got the numbers from lsusb.
Here is one line of lsusb output:
Bus 003 Device 002: ID 04a9:2206 Canon, Inc. CanoScan N650U/N656U
^^^^ ^^^^
| |
| Product ID
Vendor ID, likely 1004 for your LG vendor
jon
--
Jon H. LaBadie jonfu(a)jgcomp.com
5:20 p.m.
On 01/02/2016 03:58 PM, Jon LaBadie wrote:
On Sat, Jan 02, 2016 at 01:12:36PM -0700, jd1008 wrote:
> On 12/30/2015 12:13 PM, Jon LaBadie wrote:
>> On Tue, Dec 29, 2015 at 07:17:43PM -0700, jd1008 wrote:
...
>>> Android is 4.4.2 (nothing newer is available for my phone.
>>> Developer option set. usb debugging enabled.
>>>
>>> yet, when I plug my phone to usb on laptop,
>>> laptop does not mount anything, nor does any icon
>>> appear on the panel as a result of plugging in.
>>> Also, the phone does not pop up a screen asking me
>>> to enable USB in data mode or any other mode.
>>>
>> On F22, my LG tablet connects using the mtp protocol.
>> However, I had to add it to the udev rules configuration file.
>>
>> I copied /usr/lib/udev/rules.d/69-libmtp.rules to
>> /etc/udev/rules.d and edited the copy. I found
>> rules for tablets similar to my own and duplicated
>> them but with an appropriate name and with the vendor
>> and product id's I got from lsusb.
>>
>> HTH,
>> Jon
> Tried it.
> Still, laptop does not detect phone.
> Phone is set to query the user for connection protocol when
> usb is plugged in to both phone and laptop.
> Phone does not prompt me with that question.
>
> The file /etc/udev/rules.d/69-libmtp.rules,
>
> does not have an entry for my phone model
> (LG G Flex D959).
>
> For example, I see the entry:
>
> # LG Electronics Inc. LG G Flex 2
> ATTR{idVendor}=="1004", ATTR{idProduct}=="633e",
SYMLINK+="libmtp-%k",
> ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
>
> but my phone is the LG G Flex (Generation 1), model D959.
>
> Would a new line like:
>
> ATTR{idVendor}=="1004", ATTR{idProduct}=="d959",
SYMLINK+="libmtp-%k",
> ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
>
> correctly represent my phone in this rules file?
No, I said I got the numbers from lsusb.
Here is one line of lsusb output:
Bus 003 Device 002: ID 04a9:2206 Canon, Inc. CanoScan N650U/N656U
^^^^ ^^^^
| |
| Product ID
Vendor ID, likely 1004 for your LG vendor
jon
$ lsusb
Bus 002 Device 005: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure
Applications Processor
Bus 002 Device 004: ID 0bc2:ab28 Seagate RSS LLC
Bus 002 Device 006: ID 279e:024e
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
I do not see my phone.
I plugged it in and waited about 60 seconds before running lsusb.
Waited another couple of minutes and lsusb still reports the same items.
Also, dmesg after connecting the phone does not show anything about it.
3019
days inactive
3033
days old
23 comments
8 participants
participants (8)
-
JD -
Joe Zeff -
Jon LaBadie -
Joseph Loo -
Philip Brown -
Tim -
Will W -
Wolfgang S. Rupprecht