Hello,
First thing i did after i got this phone i flashed LineageOS on it - did not really bother checking stock ROM. However, only after some time (i usually charge phone at night, so didn't see it earlier) i noticed that either Quick Charge or Warp Charge are not working - regardless of charger i use, my USB power meter will always show max or 5V/1.4A. Did anyone had that happen with this phone before? Is there a way to fix it, or is it the high power sensing circuit(?) in phone broken?
Related
My GS2 was on charge and when I took it off charge the screen was apparently "frozen" and the phone was unresponsive to all inputs (touch screen, power button, recover mode, download mode), nothing work. So I took the battery out to restart the phone and now there is no response. The battery wont charge at all.
My phone is rooted and I had been running Resurrection Remix ics v1.0 for about 3 weeks so I know it was not a bad flash.
Since the battery would not charge, I ran some tests with a multimeter and though the battery is showing an output voltage of 3.7v, when I put the multimeter on the battery terminals in the phone whilst on charge, it was only giving 2.5v. (obviously not enough to charge the battery).
I did purchase another battery just to double check whether the battery might have been dead, but nothing.
Having had the phone for less than 12 months it is under warranty, but I don't want to return it until I have reflashed the stock ROM and unrooted, to avoid any issues. Obviously I can't reflash if I can't get it to power up.
Anyone have any ideas that might help?
Oh, and I do have a USB jig which I have tried to no avail.
Sorry if this has been addressed elsewhere in the forums, but I couldn't find any information to help.
can anyone help
anyone experience similar problem?
Hi all,
I have recently come across a problem which I cannot overcome by myself and I would really appreciate your help on this!
Phone:
Galaxy S2 (3 UK)
FW:
CM9.0.0
Description of problem:
My phone will not charge the battery. When connected to a charger, it turns itself on and immediately turns back off as there is not enough charge in the battery.
Events leading to problem:
My phone has been functioning perfectly for about 5 months (on CFW) before this happened. I had noticed that my phone ran out of charge abnormally quickly one day before this problem occurred. I did not suspect anything, and put it to charge overnight. The next morning when I woke up, the battery was out of charge (while plugged to the charger!) and the phone was abnormally hot at the area above the battery connectors. During this time, the phone would not turn on. I then unplugged the charger, and let the phone cool down. After cooling down, the phone was able to boot into the OS, but turns off immediately after that due to low charge in the battery.
What I have done so far:
Following suggestions on this thread: forum.cyanogenmod.com/topic/36648-galaxy-s2-empty-battery-boot-loop/
I suspected that my phone's firmware/kernel had somehow been corrupted. I then stripped a USB wire according to the thread, and attached it to the appropriate battery connectors allowing me to power my phone and flash the FW+Kernel via ODIN. I have since then flashed various firmwares in this order in attempt to recover my phone: Lite'ning v3.6 > Stock (3 UK Branded) > CF-Root Kernel > CM9.1.0.
Current state of phone:
I managed to charge my battery a little via my stripped USB cable, and started up my phone. After booting into OS on battery without charger connected, I have found that the phone will not charge the battery when connecting the charger while the phone is on.
However, if the OS boots automatically when connecting the charger while the phone is off, the battery status will be "Charging", but the charge goes up very slowly. (6% in 20 minutes?) What's even more weird is that if I take the charger off during this time, the phone immediately turns off. While the phone is sort of "functional" now, I'm really afraid that it will recur if my battery ever goes flat again.
I'm sorry this is such a wall of text, but I'd really like to hear your opinions on this. Thank you so much for reading
Did you solved the problem?
I'm with the same problem.
tim8871 said:
Hi all,
I have recently come across a problem which I cannot overcome by myself and I would really appreciate your help on this!
Phone:
Galaxy S2 (3 UK)
FW:
CM9.0.0
Description of problem:
My phone will not charge the battery. When connected to a charger, it turns itself on and immediately turns back off as there is not enough charge in the battery.
Events leading to problem:
My phone has been functioning perfectly for about 5 months (on CFW) before this happened. I had noticed that my phone ran out of charge abnormally quickly one day before this problem occurred. I did not suspect anything, and put it to charge overnight. The next morning when I woke up, the battery was out of charge (while plugged to the charger!) and the phone was abnormally hot at the area above the battery connectors. During this time, the phone would not turn on. I then unplugged the charger, and let the phone cool down. After cooling down, the phone was able to boot into the OS, but turns off immediately after that due to low charge in the battery.
What I have done so far:
Following suggestions on this thread: forum.cyanogenmod.com/topic/36648-galaxy-s2-empty-battery-boot-loop/
I suspected that my phone's firmware/kernel had somehow been corrupted. I then stripped a USB wire according to the thread, and attached it to the appropriate battery connectors allowing me to power my phone and flash the FW+Kernel via ODIN. I have since then flashed various firmwares in this order in attempt to recover my phone: Lite'ning v3.6 > Stock (3 UK Branded) > CF-Root Kernel > CM9.1.0.
Current state of phone:
I managed to charge my battery a little via my stripped USB cable, and started up my phone. After booting into OS on battery without charger connected, I have found that the phone will not charge the battery when connecting the charger while the phone is on.
However, if the OS boots automatically when connecting the charger while the phone is off, the battery status will be "Charging", but the charge goes up very slowly. (6% in 20 minutes?) What's even more weird is that if I take the charger off during this time, the phone immediately turns off. While the phone is sort of "functional" now, I'm really afraid that it will recur if my battery ever goes flat again.
I'm sorry this is such a wall of text, but I'd really like to hear your opinions on this. Thank you so much for reading
Click to expand...
Click to collapse
Whew that was long.. but anyway, i suggest you get the external battery charger, maybe it will do you good.
Have you tried going back to stock and doing a full reset?
Sent from my GT-I9300 using xda premium
Have you tried a different battery?
guys, i have a question,
1. i cant get wifi hotspot to work, but usb shaing works fine
2. charging takes way to long since yesterday, in 1 night from 14% to 43% ,but it charge the battery to100% but slow
i have an rooted sgs3 with siyath kernel
as for wifi, well regular wifi always gave a problem staying connected on both sgs3's i had so i actualy didnt even investigate to slove that , i even disabled psm in 0011 but no changes it acted the same , i just about wifi to on side note, the main problem is charging , dunno if its the battery or the phone ,bcuz chargers do not get hot for charging unlike when i 1st had this phone so i think either the phone dont accept the power or the battery dont want to charge , i also tryed modding charging settings in the kernel via STweaks but same results
need some advice or help with this
Slow charging questions posted many times. Usual fixes are: replace charger and lead, go back to fully stock, replace battery, phone internal charging circuit is faulty.
Hi,
long story short: I connected my Z5C to a bad (apparently, I don't want to test ) charger and now I have some strange issues. Is there any change that my h/w isn't fried?
Full story: As I said I connected my Z5C (newest CyanogenMod provided here) to a charger and it instantly did a hard reset. Afterwards it did turn on and continued to work for some time. As I was on the road at that time I could not charge it elsewhere and later that day it ran out of power. When I tried to charge it with a known good charger some days later, it did not boot. I suspect the boot process to healthd or whatever draws this cool animation takes more power than my working but small charger provided.
It did charge at my laptop, especially when I put it into fastboot mode.
Now thats where I am stuck; the phone won't turn off completely and keeps rebooting when I turn it off (via os menu or hard reset, no chance).
I can charge it after it runs out of power (managed to charge to 100%), but it won't charge if I unplug and replug it. It is not recognised by a pc after I reconnect it one or two times (checked with device manager and lsusb), only chance to get to fastboot or flash mode again is drain the battery to 0%. It does show a loading animation and I can boot into android from there. Battery drain in Android seems to be a little higher than usual (100 to 0 after 2 1/2 days of pure standby without any radio stuff on).
I have already reflashed the original Sony firmware and erased everything that came to my mind (cache, data....).
Any hope that I did not kill some piece of hardware?
Thanks for your answers, any help appreciated
tell me more about your z5c's software, why you mentioned Cynogenmod? did you flash it with cynogenmod?
seems to me that z5c was running on custom rom and did not support fast chargers and bricked your device!
if that so, try flashing it using flashtool with original stockrom.
i don't wana go in to details however there is possiblity that battery.sys file is corrupt and atleast I was never able to fix my LT18i when it got bricked and battery status use to become zero in 2 seconds and android keep rebooting, later it got silent for good! no charge no nothing and i still have the device sitting. I was running it on coconut (cynogenmod) when all this happened!
Thanks for your reply.
The charger was no kind fast charger, just a common 12V to USB adapter with an output of 800mA (when it worked). I was running CM 13 when I connected it to the bad charger, but as I mentioned I have since then reflashed it with Stock ROM. No real improvement.
I have continued trying and I found out that the device seems to believe it is still connected via usb.
Code:
cat /sys/class/power_supply/usb/present
gives me "1" with nothing connected, can you check if this is normal?
The file is -rw-r-- r--, would changing its value change anything or is it just some kernel thing (can't check, don't have root permissions now as I flashed Stock ROM)?
Also after I charged it on my PC today it still shows me the notifications for USB connection and adb (I can add a screenshot if necessary), also looks like it still believes to be connected.
It seems I found the solution: I was playing a bit with a USB-OTG adapter (the ones to connect regular usb devices like keyboards or storage to your phone). After I connected a USB keyboard I tried (just for fun) if the Linux "Magic" SysRq hotkeys were enabled. So I did press Alt-Print-o, which is the Linux hotkey for "turn off now". It did not turn off, it also stayed off (no instant reboot). After I started the phone again it also properly turned off via the power menu!
I will have to test whether the charging issues are fixed, too, but as far as I can tell the problem seemed to be something software-related
Sadly did not work for long. I think I will go for official repair, think this is still cheaper than buying a new phone (after completely killing it with some DIY "repair" attempt). This annoying brick simply does not turn off, no matter what I do (apart from draining battery to 0%). Guess its my fault, still to afraid to try that broken charger again.
Brought my unlocked S9+ home from BestBuy Friday (the first day they became available in the US). I successfully charged it up a couple times with the provided Samsung quick charger (wired) and a cheap wireless charger I grabbed at Walmart. However last night, having the phone on the charging stand I noticed the phone's red LED remained on too long even though the charging stand light indicated it was charging the phone. Finally early this morning I checked the battery level and it had gone down. The phone was not charging. I plugged the phone into the Samsung charger for the rest of the morning. After an hour or so I checked again and the level had drop a few more percentage points! WTF?? Anyway I shut down the phone and then tried again with the wired quick charger. This time it charged fine.
I wonder if this is a pending future problem. To be honest I was watching a YouTube tutorial last night on how to bring up the diagnostic screen (using a series of phone pad key presses). I wonder if that messed with the phone somehow (I did not knowingly make any changes. Just tried some of the "tests").
Anyway, hopefully this was just a one time issue...... If not, I'll report back.
I haven't noticed any issues. Maybe it was just a one off. The only thing that will truly tell is time I guess
what temperature had the battery?
Above 45°C?
I've had this issue. I caught it when the charging failed -- had an error about CPU being too high/hot. It would not charge until I re-sat the device on the wireless charger.
wifiguru said:
I've had this issue. I caught it when the charging failed -- had an error about CPU being too high/hot. It would not charge until I re-sat the device on the wireless charger.
Click to expand...
Click to collapse
I did not notice an error message. By "re-setting" the phone on the charger do you mean moving it around?
i have this same issues. It says Fast Charging, But battery level gone down. Any one notice, Its simply say Fast Charging. But whenever its says Fast Charging and in Bracket (Its says how much time it take to complete) in that time charging works fine. I think its a software issue. Because i tried click Fast Charging turned off and on again.....then charging works fine. Some way in Software blocking this. I hope so.