Closed
Bug 1031535
Opened 10 years ago
Closed 7 years ago
[Flatfish] Improve USB Drivers Experience for Windows users connecting to the device for development and flashing builds
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: caspy77, Unassigned)
References
Details
(Whiteboard: [TCP] [Flatfish][POVB])
Currently the only method to flash new builds onto Flatfish devices is via a USB connection and Windows users must have the proper drivers for this to work.
It has been a lot of hit and miss as some PCs come with the proper drivers installed while others do not. And finding the proper drivers in those cases has also been problematic - sometimes the PC manufacturer will have drivers available for download and sometimes they will detect and install properly.
In some cases it leaves us trying to install drivers for other devices hoping it will work for ours.
Optimally there will be a driver download just for Flatfish devices.
Comment 1•10 years ago
|
||
The Geeksphone driver works great, only thing is that you need to actually point Windows to the .inf file and not the folder. It's a bit complicated, but gets the job done.
Comment 2•10 years ago
|
||
Hi Caspy, have you had the PhoenixSuit tool installed on Windows? It will install the chip vendor's driver at these time. We've tested that on Windows 7/8. adb and fastboot works fine so far.
The other two things worth to note: 1. If our contributors are using the PhoenixSuit to burn the fastboot image for a brick device, make sure that the PC USB host controller works in USB 2.0 mode. (USB 3.0 causes some problem when doing this operation.) 2. It is suggested to use the original USB cable come with the Flatfish device. Other cables with 'good enough' quality should also work.
Updated•10 years ago
|
Flags: needinfo?(caspy77)
Yes, I have PhoenixSuit installed. Though I had adb/fastboot working before that. Based on what you said it sounds like this gets us the drivers we need. I would like to not stop at "good enough" though, having people install the PhoenixSuit when all they need are those drivers seems excessive. William can you confirm there there is no separate download or installer for just the necessary USB drivers?
Thanks Andrew, that's good to know, I'll keep that in the tool belt. Still looking to reduce steps and complexity, but it sounds like we have an additional viable workaround.
Flags: needinfo?(caspy77) → needinfo?(william.wyliang)
Comment 4•10 years ago
|
||
(In reply to Caspy7 from comment #3)
> Yes, I have PhoenixSuit installed. Though I had adb/fastboot working before
> that. Based on what you said it sounds like this gets us the drivers we
> need. I would like to not stop at "good enough" though, having people
> install the PhoenixSuit when all they need are those drivers seems
> excessive. William can you confirm there there is no separate download or
> installer for just the necessary USB drivers?
>
We will check whether the windows PC can recognize flatfish with only Google USB driver installed.
Eva, please help on this.
Flags: needinfo?(eva.chen.fx)
Comment 5•10 years ago
|
||
We've tried to installed Google USB Driver. It works for 'adb.exe' when the following information has been added into the file usb_driver\android_winusb.inf, in both [Google.NTx86] and [Google.NTamd64] sections for 32 & 64 bits Windows, respectively.
;Flatfish
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0003
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0003&MI_01
However, fastboot doesn't work. (This issue has also been added into our to-do list.)
As a result, so far we still suggest the contributors to install PhoenixSuit, which can also be used to recover the system when it becomes brick.
Thanks.
Flags: needinfo?(william.wyliang)
Updated•10 years ago
|
Flags: needinfo?(eva.chen.fx)
My "android_winusb.inf" settings:
[Google.NTx86]
;Flatfish
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0003&MI_01
[Google.NTamd64]
;Flatfish
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0003&MI_01
Both "adb.exe" & "fastboot.exe" on Windows XP work well.
Updated•10 years ago
|
Whiteboard: [TCP] [Flatfish] → [TCP] [Flatfish][POVB]
Comment 8•7 years ago
|
||
Firefox OS is not being worked on
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•