Surface 3 charging issues

Anonymous
2015-05-06T14:21:00+00:00

I'm sure the Surface 2 and other models suffered from this problem...

After getting my Surface 3 yesterday, I plugged it in as it was delivered with about 24% batter life.  The little white light on the micro-USB charger than comes with the Surface lit up.  I assumed all was well, and started the Windows Updates.  It was taking a while so I left it and went to bed.

The next morning the Surface was off, and when I tried to switch it on the battery symbol appeared that indicates it had no juice.  It was still plugged in to the charger and the plug was still lit.

I removed it a couple of times and eventually it must have started to charge as it allowed me to boot, and I could see it was charging.

However, whenever I plug it into any other USB port to charge it (such as on my PC), I get the "Plugged in, not charging" message).

I suspect a faulty micro-USB connector (a poor replacement for the old magnetic ones), but wanted to see if anyone elese was having trouble with either the supplied charger or charging from other USB ports.

Surface | Other

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2015-12-17T00:35:26+00:00

MA_905,

Thanks for the update and sorry for the delay in following up.

I am reaching out to find out if your issue is now resolved and if not, I would like for you to please give the two button shutdown a try.

Here’s how:

Step 1: Press and hold the power button on your Surface for 30 seconds and then release it.
Step 2: Press and hold the volume-up button and the power button at the same time for at least 15 seconds and then release both.        <br> <br><br>The screen may flash the Surface logo, but continue holding the buttons down for at least 15 seconds.
Step 3: After you release the buttons, wait 10 seconds.
Step 4: Press and release the power button to turn your Surface back on.

 Once done, please proceed to fully charge the device and let us know your outcome.

Was this answer helpful?

200+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2015-05-06T16:58:56+00:00

what's more likely is that the USB ports that you've used can't provide enough power to charge the device.

Was this answer helpful?

40+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Barb Bowman 80,805 Reputation points MVP Volunteer Moderator
2015-07-22T16:55:03+00:00

On Wed, 22 Jul 2015 16:31:18 +0000, quadtek wrote:

>> This is a surface 3, not a pro3

take a look at

http://www.microsoft.com/surface/en-us/support/warranty-service-and-recovery/surface-wont-turn-on#shutdown

  • this applies to your Surface 3

__________________________________________________________________________________________________

Barb

Windows Experience MVP

My Blog - http://digitalmediaphile.com/

Please mark as answered if this answers your question

Was this answer helpful?

3 people found this answer helpful.
0 comments No comments
Answer accepted by question author
Barb Bowman 80,805 Reputation points MVP Volunteer Moderator
2016-03-05T11:51:47+00:00

did you try the solutions at https://www.microsoft.com/surface/en-us/support/warranty-service-and-recovery/surface-wont-turn-on-battery-wont-charge?os=windows-10 ?

If yes, your best option is to go to a physical retail Microsoft Store if you are near one in the US, and if not near a store https://www.microsoft.com/surface/en-us/support/contact-us

Was this answer helpful?

0 comments No comments
Answer accepted by question author
Anonymous
2015-12-17T00:48:32+00:00

I contacted MS and they helped me in this one. I had to do a current update. when this did not fix it I had to a a factory reset. then do the update battery life is now as expected.

Was this answer helpful?

0 comments No comments

337 additional answers

Sort by: Most helpful
  1. Anonymous
    2016-01-09T17:51:04+00:00

    It would be helpful if Microsoft would publish specs about their devices' charging behavior, but they don't that I can find.

    I agree with your net conclusion that a single 2.4A charger with a decent cable should suffice for all my Android devices and the S3.  As you say, it will be nice as more and more devices coalesce on a single standard.

    The cable AWG could have an impact, but a decent cable of reasonable length is unlikely to have enough resistance for V-IR to be significant.  As you say, an "inadequate" cable could cause an issue, but the takeaway there is to avoid really cheap cables.

    I agree a 2A charger will charge a device slower than a 2.4A, assuming the device can use the extra amps, which the S3 likely can (since its charger provides that).  But, I doubt the "not charging" message is inaccurate.  An alternate explanation could be that MS used a threshold, and below that threshold, they use charger power to lessen battery draw, but don't attempt to charge.  I think Occam's razor likely applies here.

    One other assertion at various points in this thread (and others) is that too big a charger can damage the device, or over-consumption by the device can damage the charger.  As long as they follow specs, that doesn't happen, and each device protects itself.  If the device tries to draw more amps than the charger can provide, the charger will drop voltage, which should cause the device to reduce its draw.  If the charger's full capacity isn't drawn by the device, no problem.  If a charger or device damage one another, someone wasn't following the specs (e.g., putting 12v on a 5v spec'd pin).

    The Quick Charge documentation indicates it uses negotiation between the charger and device to be charged, and as you note, the supported device list doesn't list any Microsoft device, so there won't be any advantage to using a QC charger.  It doesn't explicitly say it won't damage a non-QC device, but it seems very unlikely it would.

    Was this answer helpful?

    0 comments No comments