Close

What are you looking for?

cancel
Showing results for 
Search instead for 
Did you mean: 

Original topic:

Charging issue a30

(Topic created on: 13/07/20 13:31)
Rohitnigam
First Poster
Options
Galaxy A Series

When I plugged in charger my phone starts charging and after a few seconds it will stop than after a few seconds again starts charging and then stop...this process is going on from yesterday...guide me a satisfactory response asap....

0 Likes
1 REPLY 1
Je655
Helping Hand
Options
Galaxy A Series

Check the power adapter
The charging process begins at the power adapter or charger. These things are tested before being packed and there’s a very few cases wherein the charger is defective out of the box.

If you were able to use the charger a few times before the problem started, then you already know it was working fine. Perhaps there’s something that obstructs the current. Check the port on the charger to see if there are foreign materials stuck in there. Any form of debris or lint may affect the charging process, especially now that Samsung chargers for flagship devices use the USB-C port.

 

Check the cable
The cable bridges your phone and the power adapter. If it’s broken or something, then the current may not reach your device.

After doing the first step, the next thing you have to look into is the cable. Just make sure that the connectors on both ends aren’t wet or obstructed by any debris or lint.

If they seem dirty, you can always soak them in alcohol and wipe them off with dry cloth. It’s actually easier to clean the cables. It can be helpful to also test your type c cord on another device to ensure its working properly.

 

Check your phone’s charging port
When using a wired charger, the entry point of the current from the charger is the charging port. So make sure it’s clean and that there’s no obstruction in it.

If, for some reason, you notice that it’s wet or has moisture in it, get a small piece of tissue paper and put it in. Leave it there for 5 minutes or so.

 

Force restart your phone
After cleaning the power adapter, cable and the charging port and your Samsung is still not charging, then try doing the forced restart. That is if your phone still has enough power.

There are times when a minor system glitch can cause various kinds of issues including this one.

To force restart your Samsung, press and hold volume down button and the power key for 10 seconds. Your phone will power off.

Once it boots back and you see the Samsung logo, release both keys and wait until your device has finished rebooting.

If your Samsung won’t charge even after this, then try connecting it to a computer using its cable. This will tell you if the problem is with the power adapter or cable. If your phone isn’t detected by your computer, then the problem can be with the cable.

However, if it gets detected and the battery icon doesn’t show that it’s charging, the problem can either be with the power adapter or the charging port.

To further test if it’s with the power adapter, try charging your other devices using your Samsung charger. If they charge, then the problem can be with your phone.

 


Turn off your device and charge
Try turning your phone off and connecting it to its charger. That is if you’ve already proven that the problem isn’t with the power adapter or the cable.

Sometimes, firmware issues may occur that may result in a problem like this. Turning your phone off and connecting it to its charger may somehow make it charge. But if this doesn’t fix the problem as well, then this isn’t just a minor issue.

 

Try using a wireless charger (optional)
This is an optional step. It would be impractical to buy a wireless charger just to see if your phone charges. However, if you already have a wireless charger, then try doing it to see if your phone can charge using the induction process. If it does, then the problem can be with the charging port.

 

But if the wireless charging is also not working, then it’s time that you brought the phone back to the store or to the tech so that it can properly checked. It is now a possible hardware issue.