980785 - USB (including charging and adb) doesn't work when B2G is running (unless I enable USB tethering)

Status: RESOLVED WORKSFORME

(Firefox OS Graveyard :: Vendcom, defect)

Description

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

My hamachi (or is it a buri?) is in a state where USB doesn't work at all when the OS is booted.  This means:
 * no charging
 * no ADB
(I didn't test any other uses of USB.)

For example, if the phone is powered off and I plug it into a USB charger, the blue charging light will come on briefly as the phone starts to boot, and then turn off.  (I think -- I'm remembering from this morning.)  And if I leave it in that state overnight it will have 25% battery instead of having charged.

This started after nhirata flashed my hamachi with a new image from the vendor on Tuesday so that I had the necessary low-level graphics fixes to run v1.4 -- at least after that plus my updating Gecko and Gaia to master and restoring my profile data -- although it didn't quite start immediately after that either, but maybe only because I didn't reboot.  So it seems likely to be a function of some of my settings, but I don't know which.


Workaround #1 (horrible, and for charging battery only):
 - take the battery out
 - plug the phone into a USB cable, and let it keep trying to boot until it gives up (it disconnects its own power source, after all!) and stabilizes at the mostly-white boot screen
 - then put the battery in

Workaround #2 (simple and easy, and fixes everything until the next reboot):
 - enable USB tethering in Settings, even for one second (and then disable)

Comment 1

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

I found out that I had issues with low voltage USB hubs which also showed a similar situation with multiple devices.  I think though this may be a different issue because you can enable and disable USB tethering and make it work.

I can't seem to reproduce this in the current build with a v1.2-devices.cfg base build and the latest gecko/gaia on top...

I think the only other thing I can think of is that there are ties to the gonk layer when building gecko.  Perhaps that might have something to do with it?

Comment 4

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

(In reply to Naoki Hirata :nhirata (please use needinfo instead of cc) from comment #1)
> I think the only other thing I can think of is that there are ties to the
> gonk layer when building gecko.  Perhaps that might have something to do
> with it?

I did a build on an updated backup-hamachi directory (after clobbering objdir-gecko and out), and the problem still remains.

Comment 5

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

May I try reflashing the device with the OEM build using the Teleweb tool next time we're both in the office?  Just a warning, it can take up to 1/2 hr or so to flash in this manner.

Comment 6

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

Yeah, this works with the latest reflash.

Comment 7

[Ben Kelly [:bkelly, not reviewing]]

I am seeing this again on my v2.0 dogfood device:

Flame v122
aurora update channel
Build Id: 20140716000201
Gaia Rev: 5f8b1b8a

Will dupe bug 1039864 to here.

Comment 8

[Ben Kelly [:bkelly, not reviewing]]

David suggests we just continue with bug 1039864 instead of duping.