Out of curiosity, what could be different about the included USB cable versus "any other standard" cable?

Thanks

sole

On 01/12/2014 05:17, Chris Mills wrote:
It also makes a difference when you power directly via a mains adapter, versus 
a USB cable connected to your computer.

So if the latter isn’t giving any joy, try the former.

Best,

Chris Mills
    Senior tech writer || Mozilla
developer.mozilla.org || MDN
    [email protected] || @chrisdavidmills



On 30 Nov 2014, at 21:11, Tucker McKnight <[email protected]> wrote:

Update for anyone that finds this later:

I'm not sure why I even tried this, but I just tried charging it with the USB 
cable that came with the phone. I hadn't even taken this cable out of the 
package because I already had like a dozen other micro USB cables lying around. 
After trying to charge it with the included cable, though, it works! It charged 
up all the way and has been working just fine for the last two days.

So, if you can't get it to charge or turn on, try the included USB cable. 
There's something special about it. :)

On 11/26/2014 03:42 PM, Tucker McKnight wrote:
Hi Andre,

No, adb devices and lsusb don't show anything.

On Nov 24, 2014 5:07 PM, "André Jaenisch" <[email protected]> 
wrote:
Hello,

I had a similiar behaviour on my Alcatel OneTouch Fire and contacted my carrier
for repair.
However, as I checked it via Computer (lsusb and adb devices) it was
recognised.
Have you tried that?
That is, does it respond to your computer?

Best regards,


André Jaenisch

Tucker McKnight <[email protected]> schrieb am So, 23.Nov.14 22:22:
A couple of days ago, my Flame turned off, and it won't turn on. I can't get
a boot screen or anything.

It has done this a couple of times in the past; both times I took the
battery out, then put the battery back in, and it was fine. This time that
didn't work. I've tried plugging in the USB cable, but there is no
indication that it is charging. It also doesn't show up with adb devices or
fastboot devices. Holding volume up + power, or volume down + power doesn't
do anything, either.

I'd had 2.0-prelease on it for a few weeks, and I hadn't recently changed
anything about it. I'm hoping it's just the battery. Does anyone have any
ideas as to what could be going wrong, or what I could do about it?

_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g
_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g

--
//
// http://soledadpenades.com   //  @supersole //
// GIF HACKTIVIST // Mozilla Apps Engineering //
                                              //

_______________________________________________
dev-b2g mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-b2g

Reply via email to