O.K., I released 20120531 with the fix applied.
Sorry again for the lapse of memory.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894448
Title:
Unable to access USB storage of ZTE Blade Android ph
I'm deeply sorry to say I did not remember to apply the fix ...
Data package 20120529 has just been released - I am going to make the change
immediately and release 20120531.
Didier, I hope you did not repackage the new release yet ...
--
You received this bug notification because you are a mem
AFAIK, that's fixed in the upstream 20120120 release.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894448
Title:
Unable to access USB storage of ZTE Blade Android phone
To manage notifications abo
Yes, it is about renaming the file inside the
/usr/share/usb_modeswitch/configPack.tar.gz archive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894448
Title:
Unable to access USB storage of ZTE Bla
Hi, some additional information, I found this command is useful on my ZTE-C 600
mobile phone:
usb_modeswitch -W -s 20 -v 0x19d2 -p 0x0083 -V 0x19d2 -P 0x1350 -m 0x01 -M
"55534243f8f9938820008a85010101180101010101"
after that, although last message reports "Mode switch has fai
Hi, I have a ZTE-C N600 CDMA2000 mobile phone. It runs on a linux 2.6.29
kernel and android 2.1-update1 OS. I met exactly the same situation on
my Ubuntu 11.10.
When I plug my phone on my computer and after cold boot my computer,
lsusb got:
Bus 001 Device 002: ID 19d2:1350 ONDA Communication S.p.
Very good. I will change this in the next upstream release of the data
package.
** Changed in: usb-modeswitch-data (Ubuntu)
Status: Incomplete => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Renaming to 19d2:0083:uPr=WCDMA and repacking
/usr/share/usb_modeswitch/configPack.tar.gz seems to work.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894448
Title:
Unable to access USB storage of Z
I think I'm beginning to see the 'logic'. It might have been sufficient
to look at the "dmesg" output, though. It might even give you the USB ID
of new devices.
A second after plugging the device does autoswitch its mode. Look for:
[ 434.700025] usb 1-5: new high speed USB device number 7
...
[ 4
Yes, it's a bit strange.
With the current configuration, usb_modeswitch seems to do exactly the
opposite of what it is supposed to do, it puts my device into install
mode (0083). Without usb_modeswitch, my device ends up in non-install
mode (1350) and things works fine. I uninstalled the usb-modes
> Id 1350 also seems to be the default when neither storage or modem is
> activated.
Now I'm a little confused - I thought product ID 0x0083 is the default
??
So when is the install mode really active ? It has to come in at some
point, or else you wouldn't have run into problems with usb_modeswi
No, it is not possible to use both modem and storage at the same time.
Modem and storage can only be activated when the device is connected.
When I activate modem mode, the device switch Id from 1350 to 1365. Id
1350 also seems to be the default when neither storage or modem is
activated.
ADB mod
Excellent!
Now one last confirmation question:
Are you able to set both modem and storage/adb mode on the device? And - just
out of interest - if that is the case, can you do so only with USB connection
active or can you set it in advance before plugging in?
Anyway, two attributes are clearly
Install mode
Bus 001 Device 005: ID 19d2:0083 ONDA Communication S.p.A. ZTE MF190
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
Storage/ADB mode
Bus 001 Device 012: ID 19d2:1350 ONDA Communication S.p.A.
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
b
Modem mode
Bus 001 Device 017: ID 19d2:1365 ONDA Communication S.p.A.
Device Descriptor:
bLength18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 224 Wireless
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize064
> Also, I found a hint that the product ID of the Blade has changed with the
> update to firmware 2.2, wrongly reusing the ID of the
> MF110
This is likely the case, I have upgraded my device from 2.1 to 2.2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
> Are you sure this is the storage mode which is set on the device? You
should be able to access the storage from Linux as well ...
Yes, I ran the command while accessing the storage.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
Also, I found a hint that the product ID of the Blade has changed with the
update to firmware 2.2, wrongly reusing the ID of the MF110 (which is the
device targeted by the usb_modeswitch rule in question):
http://webcache.googleusercontent.com/search?q=cache:IihdR1Y7GQkJ:www.zte.com.au/ztebb2/vie
Are you sure this is the storage mode which is set on the device? You
should be able to access the storage from Linux as well ...
Maybe I was too short in my explanation. This phone has probably more
than two different modes; so far, I assume there are three:
1. install mode: shows the pseudo CDR
Is this what you want?
$ sudo usb_modeswitch -v 0x19d2 -p 0x1350
Looking for default devices ...
Found devices in default mode, class or configuration (1)
Accessing device 006 on bus 001 ...
Getting the current device configuration ...
OK, got current device configuration (1)
Using endpoints 0x
I think we are closing in now. If it is possible to recognize the
storage mode (set on the device) and to tell it apart from the install
mode, we could leave it alone and switch modes only if the latter is
found.
You have already provided attribute data for the unswitched mode. I
assume that is th
BTW, I did not use the Windows driver on the device, I used one
downloaded from www.zte.com.cn.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894448
Title:
Unable to access USB storage of ZTE Blade
When I connect it to a Windows 7 machine, a fake CD-ROM drive appears
with a driver on it.
When activating USB storage on the device, it will appear as a disk
device in Window, without having to install any driver.
Before installing the driver on Windows, it is not possible to access
the ADB.
Af
O.K., thanks for the info.
I assume you can access the storage on Windows *without* installing the
offered drivers, right?
Now what about the "adb" mode? Can you access the debug interface with the
"adb.exe" tool from the Android SDK?
IIRC, the mode switch was a necessary step to reach this inte
In Windows, it seems to have some drivers what it wants to install.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894448
Title:
Unable to access USB storage of ZTE Blade Android phone
To manage not
$ sudo usb_modeswitch -v 0x19d2 -p 0x0083
Looking for default devices ...
Found devices in default mode, class or configuration (1)
Accessing device 002 on bus 001 ...
Getting the current device configuration ...
OK, got current device configuration (1)
Using endpoints 0x01 (out) and 0x81 (in)
I
** Changed in: usb-modeswitch-data (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894448
Title:
Unable to access USB storage of ZTE Blade Android phone
To m
The simple removal of the device line may break other devices with the
same ID.
A better approach would be to find out which ZTE phone needs the
switching in any case and which doesn't. usb_modeswitch can distinguish
between devices even if the ID is identical; for this purpose we have to
find de
The attachment "Patch for 40-usb_modeswitch.rules" of this bug report
has been identified as being a patch. The ubuntu-reviewers team has
been subscribed to the bug report so that they can review the patch. In
the event that this is in fact not a patch you can resolve this
situation by removing t
** Patch added: "Patch for 40-usb_modeswitch.rules"
https://bugs.launchpad.net/bugs/894448/+attachment/2607150/+files/usb_modeswitch_rules.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/894448
31 matches
Mail list logo