I'm having battery issues with my Galaxy S III, it doesn't boots ROM while not charging, i'm getting bootloop on Galaxy S III bootlogo, but recovery works (still have flashing problems when charger isn't plugged) . Also when i plug out charger when phone is on, phone shut downs immediately or after some time (forced one). When charging phone, operator gets unavailable sometimes and sometimes i see weird things on screen and it shuts down or reboots. I'm using ArchiDroid 3.X with ArchiKernel.
P.S Battery level isn't reliable, it changes after reboot.
First flash stock firmware and factory reset, then see how many problems remain.
Madness. said:
I'm having battery issues with my Galaxy S III, it doesn't boots ROM while not charging, i'm getting bootloop on Galaxy S III bootlogo, but recovery works (still have flashing problems when charger isn't plugged) . Also when i plug out charger when phone is on, phone shut downs immediately or after some time (forced one). When charging phone, operator gets unavailable sometimes and sometimes i see weird things on screen and it shuts down or reboots. I'm using ArchiDroid 3.X with ArchiKernel.
P.S Battery level isn't reliable, it changes after reboot.
Click to expand...
Click to collapse
Can you also try using another battery?
Madness. said:
I'm having battery issues with my Galaxy S III, it doesn't boots ROM while not charging, i'm getting bootloop on Galaxy S III bootlogo, but recovery works (still have flashing problems when charger isn't plugged) . Also when i plug out charger when phone is on, phone shut downs immediately or after some time (forced one). When charging phone, operator gets unavailable sometimes and sometimes i see weird things on screen and it shuts down or reboots. I'm using ArchiDroid 3.X with ArchiKernel.
P.S Battery level isn't reliable, it changes after reboot.
Click to expand...
Click to collapse
simply you have to buy another battery
Sent from my GT-I9300 using XDA Free mobile app
Related
hello...i hope that someone can help me....when i try to turn off the device,it shut down and after few seconds reboot?why?
also simetime the phone don't turn on and on screen i see a green battery with a thermo....someon can help me?
Did you find the answer to this? i am sending my SGS2 back for replacement. i have the same errors plus the following.
Phone selects speaker rather than earpiece as default for incoming/outgoing calls
Phone on ocasions randomly starts Kies and Voice commands even if there is no physical contact with the phone
sometimes the phone defaults back to a launcher i have never seen before (it is not touchwiz) and i have no idea how to launch it without it doing it automatically.
The faults you mentioned can be bypassed with a battery pull but they are annoying, I didn't have these problems until i upgraded my firmware through Kies to KE7.
I have an O2 branded device.
woody_2k said:
Did you find the answer to this? i am sending my SGS2 back for replacement. i have the same errors plus the following.
Phone selects speaker rather than earpiece as default for incoming/outgoing calls
Phone on ocasions randomly starts Kies and Voice commands even if there is no physical contact with the phone
sometimes the phone defaults back to a launcher i have never seen before (it is not touchwiz) and i have no idea how to launch it without it doing it automatically.
The faults you mentioned can be bypassed with a battery pull but they are annoying, I didn't have these problems until i upgraded my firmware through Kies to KE7.
I have an O2 branded device.
Click to expand...
Click to collapse
same issues to me... I'm trying to fix it flashing a stock rom without good results yet In the meantime I'm waiting for a USB jig from ebay before to send it to technical service
I have a I9100M(BELL) flashed with cognition 1.32 with same problem.
Randomly my phone will:
-go into driving mode
-answer calls in speaker phone mode
-start alarm clock
-think its charging when the cable is not plugged in
-Reboot it self/turn it self on when its off
-wont connect to computer or charge even when cable is plugged in.
I need to send it in for repairs what should i flash? there is no bell branded firmwares or roms.
jinxedsoul said:
I have a I9100M(BELL) flashed with cognition 1.32 with same problem.
Randomly my phone will:
-go into driving mode
-answer calls in speaker phone mode
-start alarm clock
-think its charging when the cable is not plugged in
-Reboot it self/turn it self on when its off
-wont connect to computer or charge even when cable is plugged in.
I need to send it in for repairs what should i flash? there is no bell branded firmwares or roms.
Click to expand...
Click to collapse
Exactly the same to me
How do you flash congnition? just over the stock rom with odin?
did you flash modem?
Absolutely same here, since coming from CM7 to VillainRom.
Never had that before.
I´m waiting and watching it and your results!
Thanks for this thread.
That's why I don't root the phone..it works fine.
---
- Sent from my iPad using Tapatalk
pachi72 said:
That's why I don't root the phone..it works fine.
---
- Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
This has nothing to do with root access.
I cannot believe that any problem related just because you have access to your system.
Back to topic, flashed back to cm but problem persists.
It's getting really bad near to flashing stock and bring it back to change device if someone knows what it is could be helpful.
I also have this problem. I think it has something to do with the usb port.
Because sometimes it just scans for media, or it thinks it is charging. Really weird! Then i just put in the charger and it stops for a while. Turning off will just reboot the device. And removing battery and plugging it back it also just reboots the phone.
I hope it is not hardware related...
I was looking for help for a problem I have but this seems to cover most of the problems I'm having.
Mine has recently started going into a strange mode after shutting it down. I get the battery charging symbol alternating with the "battery overheating" symbol.
The only way to stop it is to remove the battery for at least a couple of hours (if you put it straight back in it automaticly starts up and goes back to flashing the battery warnings) or pressing Power, Vol+ and Home and choosing Reboot.
I have also noticed its very slow to respond to plugging the charger in or out. It doesn't always wake-up and bleep when the charger is put in and it stays showing its charging for some time after the charger has been removed.
I was told that the charger should be removed as soon as charging is compleated but surely overnight is the only time we have available to charge these phones!
Depending on the custom rom or kernel you are using, it might not support off mode charging.
To avoid having a "problem" with charging the phone in off mode, some developers decided to make the phone boot up when the phone is been charged when the phone is off.
Going back to an official stock ROM fixes this problem.
cyanogen mod 7 said:
cm_galaxys2_full-23.zip (2011-08-15 08:48:18)
Enable power off charging (LPM) (android_device_samsung_galaxys2)
Click to expand...
Click to collapse
As for Cyanogen, since built 23, you can charge the phone when it is in the "off" state. Please wipe out your userdata partition before flashing. Do not restore from a previous backup.
I fixed my reboot problem (rebooting instead of turning off) by letting the battery drain all the way so it couldn't boot anymore. Tried turning it on to see if it really doesn't go on anymore. After that I plugged in the charger and I got the charging-symbol and it did not turn on so I kept it charging overnight while turned off and in the morning it was finished and turned it on.
I also cleaned the usb-port on the phone with a toothpick. It had alot of dust stuck in it which I couldn't see. After that no more problems...for now. They haven't returned for 2 days now.
WoollyBully said:
I was looking for help for a problem I have but this seems to cover most of the problems I'm having.
Mine has recently started going into a strange mode after shutting it down. I get the battery charging symbol alternating with the "battery overheating" symbol.
The only way to stop it is to remove the battery for at least a couple of hours (if you put it straight back in it automaticly starts up and goes back to flashing the battery warnings) or pressing Power, Vol+ and Home and choosing Reboot.
I have also noticed its very slow to respond to plugging the charger in or out. It doesn't always wake-up and bleep when the charger is put in and it stays showing its charging for some time after the charger has been removed.
I was told that the charger should be removed as soon as charging is compleated but surely overnight is the only time we have available to charge these phones!
Click to expand...
Click to collapse
What kernel and rom are you using? I have not seen the battery overheating symbol on the sgs2.
No, there is no need to remove the phone from charger, when the phone gets to what is considered full, the battery will stop charging by itself.
Are you using the original samsung charger that came with the phone, or are you using a after market charger? Most of these USB chargers do not send a signal on the data lines. When using these chargers, the phone becomes laggy and unresponsive, there is also a delay to register anything on the touch screen. Stay away from these chargers.
For lithium batteries just charge it whenever you feel like it. Lithium batteries have a few thousand deep charge cycles, meaning if you use up all the power, then charge it,you use 1 deep charge cycle. However, if you use the micro cycles for charging, you can charge the batteries a few million times. Leaving the battery on empty for too long will damage the lithium battery.
Can any one confirm if this is a hardware or software issue as i now have the problem when i try and switch the phone off it will just reboot?
The Same issue occurs in my sgs2
hi everybody,
i just got my sgs2 ten days ago
everything seems good at first
then i realized screen standby lock lag problem, there exist a lag between 1 second to 2.5 seconds.
i ignore that due to it cannot be named as a problem, it seems like a bad characteristic
then yesterday , i have faced with another problem
after i have docked the phone to the original vehicle dock kit,
phone cannot be closed via power button , i hold it 1.5 seconds then chose turn off among list, phone looks like to be turned off then after a little while it just vibrates and reboots. That is phone cannot be turned off, it s somehow turn itself on again.
Whats the reason of this problem ?
In another forum one faced with the same problem said that it turned out to be normal when the battery is erased but the problem is occured again after docking.
micro usb connector
I droped my phone in the water, got it alive again, but with all the error(overheat battery symbol, no stable usb connection, reboot when i power off, 100% charged not going away) replaced the micro usb connector with a new one.
Some problems are gone but i still can't connect to pc (kies, debug etc), poweroff problem still happen sometime.
Conclusion: It is not only the usb part of the phone that are causing this problem.
But I do belive its a hardware problem.
Have you phone maybe got to much to drink too..
usb port???
I've recently been experiencing the same problem
When I turned off my phone it switched on again!
And removing battery and plugging it back it also just reboots the phone.
Sometimes the USB connector and charger are confused
Do solved the problem by changing the USB port?
plz help me
Thank you in advance for helping me
This is definately a hardware issue. Clean the usb connector, failing that it will need replacing
On Behalf of SamsungCarla:
"Hello,
Samsung takes all product related issues seriously. We invite the customer to contact us so that they can examine the phone to determine the cause of this incident. If you send us your name, phone number, phone IMEI, where the product was purchased, and email address to [email protected], we will contact you to see how we can help.
Sincerely,
SamsungCarla
Samsung Support"
Okay guys and guyettes, I flashed the Siyah 3.0.1 kernel to my lovely S2 but my battery died overnight and now the darned thing won't boot. Due to an issue with the kernel, it automatically tries to boot when the phone is plugged in to charge, but not having enough power to boot up the thing dies and tries again. Continuously. It won't go to recovery mode and if I try to launch download mode it tells me it can't because of the low battery and then starts bootlooping again. Please please help, I've been without my phone for a day and I'm away from home with limited internet access so I REALLY NEED IT D:
pull out the battery keep sometime out, and put back and leave it for 1-2 hours for charging....then boot and restore your previouse kernel
I've tried leaving the battery out overnight, but whenever I put it in and try to charge it just does the same thing. Automatically tries to turn on, doesn't have enough power to power on, shuts down, and tries again :-/
You need a new charger battery or find some way of charging your battery outside of the phone.
jje
Sent from my GT-I9100 using xda premium
cherryduck said:
Okay guys and guyettes, I flashed the Siyah 3.0.1 kernel to my lovely S2 but my battery died overnight and now the darned thing won't boot. Due to an issue with the kernel, it automatically tries to boot when the phone is plugged in to charge, but not having enough power to boot up the thing dies and tries again. Continuously. It won't go to recovery mode and if I try to launch download mode it tells me it can't because of the low battery and then starts bootlooping again. Please please help, I've been without my phone for a day and I'm away from home with limited internet access so I REALLY NEED IT D:
Click to expand...
Click to collapse
Did you use SetCPU or Voltage Settings app to tweak with the frequencies/voltages? Theres a high chance that the Siyah you flashed doesn't support the frequency you have on your device. Id tell you to go into that app and restore defaults.
I was on NEAK before and flashed Siyah on top of it and it constantly kept rebooting and then i realized that if you get constant reboots, they mention to play with the voltage settings.
Try it out, maybe lower it from 1200Hz to 1000Hz being the max.
Let me know if it helps!
Happened to me once when I let battery run down too much. I left it charging in bootloop for a while, then unplugged charger, boot the phone, and replugged charger.
Well that was the issue of the kernel but it was solved later. For ur problem try to charge ur battery using master charger. Also try to go to recovery mode while charging and charge for a while and reboot ur phone.
Sent from my GT-I9100 using xda premium
jzmtl said:
Happened to me once when I let battery run down too much. I left it charging in bootloop for a while, then unplugged charger, boot the phone, and replugged charger.
Click to expand...
Click to collapse
I've left it "charging" in bootloop overnight but it still won't turn on enough to set it charging properly :-( it also won't enter recovery mode so I can't leave it charging at that. My housemate back home has an S2 so it looks like I'm stuck without a phone until I can get back and borrow his phone to charge my own :-/
Hmmm. This is a long shot, but try this: plug the phone in. Then, while it is booting and the phone is still plugged in, take the battery out. (this used to work with my old Motorola Milestone - it would stay on even when the battery was out)
If it stays on, put the battery back in and hope for the best. Otherwise, you'll need to either acquire an external battery charger, or wait til you can borrow your buddy's phone to charge your battery.
Plese change such headings.....
A request to the members to change such headings...which directly give a bad impression of a product wich is an outcome of very hardwork of some dedicated devs....this may be only your case with Siyah kernel which might be a result of your earlier config, whereas thousands of users are using the same flowlessly....
thank you
The title says it all. My brothers Note 2 will only boot past the Galaxy Note 2 boot screen if it is connected to the charger. It doesn't matter if it is a USB or wall charge. If the phone is connected to a power source it boots into the system fine, however, once you remove it from the power source it turns off. I was wondering if it could be a bad battery but the charge is showing it at almost 80%. Has anyone ran into something like this before? If I try to boot the phone without it being connected, it sits at the Note 2 screen for about 15 seconds and then shuts itself off.
I'm not really sure but it sounds like the internals of the battery are closing up (shorting). Are you able to get another battery to test and see if it is the battery?
Note 2 - Boots , Loops, No SDS Detected as per eMMC checker on play store
chrisjm00 said:
The title says it all. My brothers Note 2 will only boot past the Galaxy Note 2 boot screen if it is connected to the charger. It doesn't matter if it is a USB or wall charge. If the phone is connected to a power source it boots into the system fine, however, once you remove it from the power source it turns off. I was wondering if it could be a bad battery but the charge is showing it at almost 80%. Has anyone ran into something like this before? If I try to boot the phone without it being connected, it sits at the Note 2 screen for about 15 seconds and then shuts itself off.
Click to expand...
Click to collapse
Having same issues
Seems it hardware plus software issue.
Running 4.1.1 Jelly Bean
Happened after installing few games .
Goes in constant boot loop
Can start by attaching power cord only to socket.
With USB attached to Laptop .. still goes in loop
Powerbank is workaround.
Seems to reboot when saving to sd card ..
Will keep posted
technoracy said:
Having same issues
Seems it hardware plus software issue.
Running 4.1.1 Jelly Bean
Happened after installing few games .
Goes in constant boot loop
Can start by attaching power cord only to socket.
With USB attached to Laptop .. still goes in loop
Powerbank is workaround.
Seems to reboot when saving to sd card ..
Will keep posted
Click to expand...
Click to collapse
The problem, after getting a stock image back on the phone, ended up being a bad battery. The phone wouldn't hold a charge even though the charging image showed otherwise. Once you get a working image on there, try replacing the battery. I ordered an eight dollar cheapo battery from Amazon and it worked like a charm.
chrisjm00 said:
The problem, after getting a stock image back on the phone, ended up being a bad battery. The phone wouldn't hold a charge even though the charging image showed otherwise. Once you get a working image on there, try replacing the battery. I ordered an eight dollar cheapo battery from Amazon and it worked like a charm.
Click to expand...
Click to collapse
I second this. My phone went down Saturday. Thought it was something with CyanogenMod 11, but flashing back to stock did nothing. Replaced the battery, haven't had any problems since.
chrisjm00 said:
The problem, after getting a stock image back on the phone, ended up being a bad battery. The phone wouldn't hold a charge even though the charging image showed otherwise. Once you get a working image on there, try replacing the battery. I ordered an eight dollar cheapo battery from Amazon and it worked like a charm.
Click to expand...
Click to collapse
Thats first thing i did .. checked different battery ..
Battery is fine .. its not battery issue .. atleast in my case ..
i checked for SDS .. my phone has no SDS insane bug either .. though symptoms were same .
I have backup phone, using it.
I showed for mobile repair.
Said he will solve it .
So plan to take tomorrow.
I can root and all..
But after this booting dont want to brick it ..
So plan to do it via the mobile repair shop
Had same issue. Solved after replace the battery.
I have the same issue right now as well. I was on stock for awhile and used casual one click method, switched between a few roms. Than it started happening after that. So I flashed back to stock on odin and still have that issue. Havent figured it out yet.
Sent from my SCH-I605 using XDA Free mobile app
Boot cycle loop
DX.Deception said:
I'm not really sure but it sounds like the internals of the battery are closing up (shorting). Are you able to get another battery to test and see if it is the battery?
Click to expand...
Click to collapse
I have had this issue and replacing the battery did the trick. I was having issues with the battery beforehand. once the battery showed as being at 17% the phone would start the reboot cycle and not fully boot until it was plugged in.
Have same problem here.....All these started when I replaced my bulge battery. New battery doesn't hold power below 20%. Phone goes off in boot cycle until plugged in a charger
Try to boot on USB/PC data connection
When connected t PC-system will boot to a point. PC indicates new connection then looses it and Note 2 returns to flash screen. Problem start when using corporate email and encrypted data. Works w/o error connected to wall charger. Disconnect crashes system. Flashes screen forever. No diagnostics. Did all SW reboots. Doubt battery, but will try.
suntreepops said:
When connected t PC-system will boot to a point. PC indicates new connection then looses it and Note 2 returns to flash screen. Problem start when using corporate email and encrypted data. Works w/o error connected to wall charger. Disconnect crashes system. Flashes screen forever. No diagnostics. Did all SW reboots. Doubt battery, but will try.
Click to expand...
Click to collapse
Did you ever test a new battery/figure it out?
Mine is doing the same thing I think. I only boots if connected to a wall charger. If connected to PC with USB it will boot to the [T-Mobile in my case] boot screen, connect to PC for a split second (long enough to make the connection sound in windows, then I can't find it) and it stays on that screen. Without being connected to either, or after pulling plug, it turns off.
Same problem here with mine
can't be just the battery because it will stay on w/o charger when in download/recovery mode or if it gets stuck on the Verizon screen.
___________________________
Verizon Galaxy Note II
model SCH-I605
android 4.4.2
kernel 3.0.31
build KOT49H.I605VRUFND7
hardware version I605.06
I'm having the same issue but i can boot into recovery without the charger.
I've been trying to find a definitive answer on this and did several searches of the forum. I found one issue which was similar here: http://forum.xda-developers.com/showthread.php?t=2413998 but, am not sure if it is really the same thing.
My battery has 100% drained on my Galaxy Player 5.0 . I am running a 4.3 ROM and Kernel, though I can't remember which off the top of my head.
Whenever my Galaxy Player is fully drained or is turned off, I cannot charge it properly through USB. I get a clocking/refresh screen, a white empty battery and then the system restarts and the same process starts over again. This has happened no matter which kernel or ROM I have used in the past as well, and only goes away when using the factory default ROM and Kernel. This loop happens regardless of using the wall charger or just the USB wire to computer.
I have tried timing the removal of the USB cable between the loops to get the device booted up but, when the battery is dead there is not usually enough juice to jump-start the player. The only way to fix it is to let the thing sit for hours and hours and hope that maybe the battery has somehow managed to get enough charge despite the looping.
Whenever the Galaxy Player is in this dead battery or powered off loop you can't get into download or recovery. Luckily, if the device is just turned off and still has battery power you can just remove the USB and turn it on. This obviously does not work when the battery is dead.
The biggest problem is not when the device is powered off but, when the battery is dead. It is nearly impossible to charge through the constant loop.
So, I have a couple of questions:
Has anyone come up with a definitive way to get out of these kind of loops other than installing the factory standard ROM/Kernal?
Is this something that has been fixed in any of the 4.4 kernels or roms?
That sounds really bad man I don't know if that's odd internal problems with your Galaxy Player or something
Sent from my YP-G70 using XDA Free mobile app
Well, I was able to get it working after plugging it in to a wall charger and some luck. However, it still doesn't explain why the looping happens whenever the device is off and the USB is plugged in instead of just charging. It also doesn't explain why when the battery dies and I plug it in, it loops instead of charging.
troy5890 said:
That sounds really bad man I don't know if that's odd internal problems with your Galaxy Player or something
Sent from my YP-G70 using XDA Free mobile app
Click to expand...
Click to collapse
Try to change to rjs kernel if u have stock kernel.
Sent from my YP-G70 using XDA Free mobile app
This is why you don't let the battery drain 100%.
ctlw83 said:
I've been trying to find a definitive answer on this and did several searches of the forum. I found one issue which was similar here: http://forum.xda-developers.com/showthread.php?t=2413998 but, am not sure if it is really the same thing.
My battery has 100% drained on my Galaxy Player 5.0 . I am running a 4.3 ROM and Kernel, though I can't remember which off the top of my head.
Whenever my Galaxy Player is fully drained or is turned off, I cannot charge it properly through USB. I get a clocking/refresh screen, a white empty battery and then the system restarts and the same process starts over again. This has happened no matter which kernel or ROM I have used in the past as well, and only goes away when using the factory default ROM and Kernel. This loop happens regardless of using the wall charger or just the USB wire to computer.
I have tried timing the removal of the USB cable between the loops to get the device booted up but, when the battery is dead there is not usually enough juice to jump-start the player. The only way to fix it is to let the thing sit for hours and hours and hope that maybe the battery has somehow managed to get enough charge despite the looping.
Whenever the Galaxy Player is in this dead battery or powered off loop you can't get into download or recovery. Luckily, if the device is just turned off and still has battery power you can just remove the USB and turn it on. This obviously does not work when the battery is dead.
The biggest problem is not when the device is powered off but, when the battery is dead. It is nearly impossible to charge through the constant loop.
So, I have a couple of questions:
Has anyone come up with a definitive way to get out of these kind of loops other than installing the factory standard ROM/Kernal?
Is this something that has been fixed in any of the 4.4 kernels or roms?
Click to expand...
Click to collapse
This was a problem on all 5.0 ROMs before kk. It has been fixed in all kk ROMS.[emoji6]
Hi guys,
Yesterday, I have encountered a strange problem with my S3. I was using CM 12- Beta 1. I had a strange bug with charging. Unless I enable unstable charging power, the charging rate falls down to 100mA. So, I have used @JustArchi's ArchiKernel ( @Moster2's build ) for LP. I have used kernels like Archi Kernel, Boeffla Kernel with unstable charging power enabled since past few months and had no problems previously.
I, then kept my phone for charging and when I saw it after 5-10 min, a charging animation with 0% battery shown up and the device got hot. I took off the charger and tried to switch on but it didn't work. I'm only able to switch on the device when it is connected to charger. But, it got stuck at Samsung logo. I have quickly entered the download mode and flashed a stock rom via odin.
I'm trying to switch on while charger is connected but the phone keeps on switching off at Samsung logo or even before the appearance of Samsung logo. When I left it for charging, the same thing started happening. Charging animation shows up and suddenly it becomes like a dead phone and restarts again to show up charging animation. Once, I was able to get past the boot screen to Samsung's lock screen but it switched off within fraction of seconds. What could be the problem? Is this an end to my S3? Please help me to find out the problem.
chvenkatf said:
Hi guys,
Yesterday, I have encountered a strange problem with my S3. I was using CM 12- Beta 1. I had a strange bug with charging. Unless I didn't enable unstable charging power, the charging rate is falls down to 100mA. So, I have used @JustArchi's ArchiKernel (@Moster version) for LP. I'm using this kernel with unstable charging power enabled since past few months and I have no problems previously.
I, then kept my phone for charging and when I saw it after 5-10 min, a charging animation with 0% battery shown up and the device got hot. I took off the charger and tried to switch on but it didn't work. I'm only able to switch on the device when it is connected to charger. But, it got stuck at Samsung logo. I have quickly entered the download mode and flashed a stock rom via odin.
I'm trying to switch on while charger is connected but the phone keeps on switching off at Samsung logo or even before the appearance of Samsung logo. When I left it for charging, the same thing started happening. Charging animation shows up and suddenly it becomes like a dead phone and restarts again to show up charging animation. Once, I was able to get past the boot screen to Samsung's lock screen but it switched off within fraction of seconds. What could be the problem? Is this an end to my S3? Please help me to find out the problem.
Click to expand...
Click to collapse
You need battery replacement.
JustArchi said:
You need battery replacement.
Click to expand...
Click to collapse
Thank you Archi. Is it because I have enabled unstable charging power?
chvenkatf said:
Thank you Archi. Is it because I have enabled unstable charging power?
Click to expand...
Click to collapse
Can't tell you. It may be that, or your battery simply ended it's life. Nobody will assure you that unstable charging is secure, moreover, under certain circumstances it may NOT be secure.