New phone, gmtp reports no device. I have libmtp9 from the current Ubuntu "Wily" installed. This is a Huawei P9, shows as EVA L09 in Devices. ghpoto2 doesn't see it either; but it does open a 'CDROM' window when attached, containing some windows autorun stuff.
Anonymous
View and moderate all "bugs Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Bugs"
Updated: I find there is a phone option to set 'files' or 'photos' when USB connected; gphoto2 DOES work with 'photo' selected, and gmtp DOES work with 'files' selected. I got an error with gphoto2 after a time but gmtp was perfect!
the original trace is mass storage. it is likely exposing a CDROM interface with some windows drivers or so, as you noticed.
In the other mode it seems to be accessible, is it also recognized by name?
Hi,
I have a Huawei P9 Lite, which is also reconised as follow: ID 12d1:107e
(ID 12d1:107e Huawei Technologies Co., Ltd.)
I'm using Linux Mint 17.2 in compatibility mode (the only version and mode making my "CloudBook" working under Linux)
Due to some issue (all target files = 0 byte) while trying to copy photos, I got to try the same operation as "root" from the CLI. Also, I tried the following: - http://forum.xda-developers.com/showthread.php?t=2055563
At best, I'm getting a mounted partition (must eject the phone prior to run mtpfs) with two items shown my Nemo: 1) ???(I forgot its name and can't see anything any more...) and 2) "Internal Storage". Once opening "Internal Storage", Nemo (=file manager) is re-opening a new window as it triggered an ejection/re-insertion of the device...
I am here because I want to copy the photos (storage full....) by using the CLI.
Problem: Can't access any content from the phone from CLI... :-/
Here is what error message that I'm getting from the CLI:
"
mint@mint ~ $ sudo mtpfs -o allow_other /media/p9/
Unable to open ~/.mtpz-data for reading, MTPZ disabled.Listing raw device(s)
Device 0 (VID=12d1 and PID=107e) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Found 1 device(s):
12d1:107e @ bus 1, dev 10
Attempting to connect device
Android device detected, assigning default bug flags
Error 1: Get Storage information failed.
Error 2: PTP Layer error 02fe: get_handles_recursively(): could not get object handles.
Error 2: Error 02fe: PTP: Protocol error, data expected
Listing File Information on Device with name: (NULL)
LIBMTP_Get_Storage() failed:-1
mint@mint ~ $
"
Any idea about what I could try next ?
Thanks in advance,
HP_
P.S.
I posted there, since it seems to be the most relevant place about Huawei P9 (Lite) Android Mobile Phone...
Should I open a new ticket and move my actual message into it ?
I would like to enquire about the status of this bug. I have a device with this ID (actually a Huawei Nova Youth) and am unable to interface with it in any way from Arch Linux (4.13.4-1-ARCH).
EDIT: I managed to
mtp-detect
and mount the 'Internal Storage' withjmtpfs
-- it seems that the device must be set to have "USB Debugging" disabled and "Allow ADB debugging in charge only mode". Unfortunately, I was unable to get ADB itself to work, but at least it seems like a workaround. It seems that USB Debugging mode causes the device ID (fromlsusb
) to continously change, as it seems the phone is continuously re-connecting to the host for some unknown reason. I hope this helps.Last edit: Throstur Thorarensen 2017-10-11