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!!!
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org
