I'm not sure what happened. My US Galaxy Player was working fine yesterday, but this morning when I went to wake it from sleep it was acting like it had a dead battery. I plugged it into a charger and rebooted it, and the battery manager said I had 45% charge. I unplugged it and it shut down. Not a soft shutdown, like when you select the option from the power menu, but a hard shutdown, like when you pull the plug on a computer.
I'm running the ROM, Kernel, and GApps found here: http://forum.xda-developers.com/showthread.php?t=2264671
(the first two downloads)
It's been a few days since I last flashed it, so I'm wondering if there might be a hardware issue.
PS: I also am noticing that when I do power it on while plugged into the wall, it skips the Samsung Galaxy S & CyanogenMod screen (and the one before that, I can't remember what it says), and goes straight to the CyanogenMod loading wheel. Every time I've tried to start it up, I've been unable to do so before it shows the Battery Charging icon (for charging when shutdown). I haven't noticed an animation for the charging icon, but my Player is now reporting that it's at 60% charge, so it seems to be working.
I've tried leaving the microUSB end of the charging cable in and unplugging the wall part, but it shut down as well (not totally unexpected, but I'm asking for help so I figure I should include as much info as possible).
Thanks in advance for any help you can give!
Fixed it (at least for now). Re-flashing the kernel was all it took.
JUST FYI
AFAIK, All of the newer kernels out there for the YP-G70 have this problem where, if you boot your device plugged in and then unplug it, it shuts off. If you boot your device not plugged in and then plug it in afterwards it's fine. I could be wrong but I think it's a problem in the kernel that everyone is using for a base (CM 10.1) . It's not really that big of a deal but it's something to keep in mind.
Boot with cable connected -> Shutdown before disconnecting cable.
Boot without cable -> Everything is normal...
Related
My Aria was running CM 6.1.1 fine 'till all of a sudden it won't charge.....
Only when it's connected to a charger I'm able to turn it on and it goes straight to Recovery mode. After turning it off and on couple of times i manage to get it work but when i disconnect the charger it turns back off.
What should I do? I don't know what can be the problem. I tried to flash new ROM, including my backups but it didn't help.
Thank you!
did you run your battery completely down to 0%? clockwork has a known bug where if you plug the phone in while its turned off, it will load into a faulty version of clockwork.
i'd recommend leaving the phone plugged in, let clockwork show up, hit reboot now, and just leave it plugged in to see if it maintains a charge.
Hey,
Ive tried it. it won't charge and even if it does, the battery lasts for an hour or so ...
So the problem is with my battery?
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"
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?
I bought the Anker charger/2 batteries set in this thread awhile back - http://forum.xda-developers.com/showthread.php?t=1632718
Had not used them before, but hurricane Sandy is coming through so I figured I would test them out. I put one in the charger last night and put it in the phone this morning, and now the phone will not boot up all the way - it shows the Samsung bootscreen, then the KingKangers logo screen, and then shuts off. I've had this same issue with both of the new batteries along with my original Samsung battery.
I have tried to put it into recovery and download mode, at one point it showed the download mode screen and then shut off again. Recovery mode has not worked at all. Tried holding power for 30 seconds while both plugged in and not plugged in, no luck. Saw a recommendation to take out SIM, SD card, and battery for 10 mins and then put them back, and that didn't work as well. Tried to see if ODIN would "wake it up", but ODIN does not recognize it (tried two cables from two different computers). Computer also doesn't recognize my phone to look at my files, etc.
Also, when I plug it in to charge with the battery in place, it does small vibrations - I have noticed this is the same thing the phone does if I plug it in to charge it without a battery in...worried this may mean my phone is not recognizing the battery for some reason??
Any ideas? Any help is MUCH appreciated...
FWIW, running AOKP and Dagr8's KingKangers kernel, been running it for the last week or so with no real issues other than occasional reboot.
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.