I have a strange issue that my Samsung Focus used to get when it was first released. The Focus was later fixed with a Firmware update.
When I plug in my power cord, SOMETIMES, the screen becomes unresponsive, or glitchy. Also, instead of charging my phone, it starts to drain the battery. I can watch the Diagnosis app (##634#), and it is pulling charge, instead of pushing it. If I unplug and restart my phone, then plug it back in, it starts charging it normally.
Also, when I power off my phone while it's plugged into power, it goes into a reboot loop showing battery empty, even though the battery is fully charged (or, sometimes, it locks up and I have to unplug to restart). I have to unplug the cord and restart, or it never powers back on.
I've already tried multiple Hard Resets, and still happening. I'll keep an eye on this, and see if anyone else is having the same problem. If not, I might exchange it. If others are, then I will expect Nokia to fix it shortly and I won't stress about it yet.
PS: Lumia 900 Black
I had this happen once
Sent from my Lumia 900 using Board Express
Which charger/cable are you using? I found that I had this problem with my e900 using a cheap third party charger. I'm having the same issue with my Lumia now, but on a different charger (that was working fine on the e900). Going to the first party charger or playing around with another one I had at home seemed to solve the issue.
genericasian said:
Which charger/cable are you using? I found that I had this problem with my e900 using a cheap third party charger. I'm having the same issue with my Lumia now, but on a different charger (that was working fine on the e900). Going to the first party charger or playing around with another one I had at home seemed to solve the issue.
Click to expand...
Click to collapse
Yes, I did notice it's mostly a third party charger. But it also does it on the PC USB port. Likely due to low amperage too. I understand the lumia has a large power requirement, but the PC USB port should not cause it. Its not like they will never be used on PC USB power.
Like I said above, my Focus had the same issue, and they fixed it with a firmware update. I'm sure Nokia will do the same.
Good luck. Keep us updated.
I had an issue just now while charging my Lumia 900. The battery was around 15% so I plugged it in for a charge. I went to look at something on the phone a few times while plugged in and the first few it was fine. Then on the third time I couldn't get any response at all from the phone. I unplugged it and had to hold the power button for a long time to get it to come back on. This is the first "issue" that I've experienced with this phone since getting it on Friday. I haven't had any data issues or anything else that some others are seeing. Not sure why it happened but I'm concerned it might not be an isolated incident.
At this point this has only happened once and while charging. Not sure if its related to being plugged in or if it could happen while under normal use yet.
my battery was critically low and the screen became unresponsive..it just froze on whatever I was doing and it wasn't responding to any of the commands..so I had to hold the power button for a long time and restart it..but upon restart it did it again..then I plugged in my charger and it was fine after that...does the lumia charge while off? or is the phone supposed to be on whilst charging?
Those are the exact symptoms my Samsung Focus had until they fixed it via Firmware.
Windows phones only charge while on. If the battery is exceptionally low, it will charge just enough to be able to power itself on, then it will finish charging while on. It's designed that way. I'm looking forward to firmware and software updates, which will only make this phone better. Or, if we get to upgrade to Apollo, woohoo!
Still love this phone though, even w the charging glitches.
Related
Hello people
A couple of hours ago, my phone shut down due to empty battery. I came home, plugged it in and booted it, all was fine. At about 60% I shut it off and went to have lunch, when I came back and tried to turn it on, I couldn't.
Led was orange at the time, I unplugged the power cord but the led stayed on! I removed the battery to be able to reboot it, but when I re-inserted it I still wouldn't boot.
Now no matter how I try to charge it, led stays off like it's not charging. Tried various different cables/chargers, the same. Tried to plug it to the charger without battery but no led flashed. Tried to boot without sim/sd card, still the same.
Any ideas?
My battery has never been changed (for a year now) and has had a bunch of full drains. Could this be a dead battery? :/
Well seems the phone is fried... I tried two more official batteries and no go...
Sorry to hear it. I thought that at first when I read your thread but I thought because I am not the most experienced person here, there might be some kind of fix.
HTC will most likely if not certainly replace this handset for you, seeing as it just happened out of the blue.
Well I certainly hope so, problem is I suspect it's an import (from another European country) and local HTC service generally does not do well with European imports.
Anyway I'll give it a try, meanwhile I'm getting a sensation soon
I have a similar problem.
I'm lucky that my girlfriend has the same handset as I do, the I could compare the phone abnormal behavior tho that of her properly working phone.
The first thing I've noticed, after a while when the charger was attached, was that the phone is very hot and that the battery keeps draining out in a surprisingly high rate.
After a while I've noticed that even when the phone is turned off it wont recharge. Sometimes the Orange LED is on when recharging while it is off, and the LED stays on for a few seconds after removing the charger, as if it was still charging. Note that the affects of connecting the charger to the phone, are mainly the ones listed below (not necessarily altogether)
* The phone indicates as if it recharges.
* Going to an infinite loop of rebooting and crashing.
* Getting hot when power supply is plugged, or at any time when the phone is turned on.
Ultimately the battery was empty, and the only way I had to keep using the phone (mostly to diagnose the symptoms listed here) was to swap the battery with the one of my girlfriend's device, and charge my battery in her device while using her's. That's the place to mention that the battery works just fine and that the phone is draining any battery, no matter what.
I took it apart to have a closer look at the source of all of the heat emitted while the phone is turned on, and it seem to come from the motherboard itself.
That's all I have.
The worst thing is that a friend of mine who helped me opening it up broke the pcb of the volume keys. Now I checked and It turns out that that pcb is actually part of the flex cable, which sort of extension of the motherboard and is mainly the second most important piece of hardware of all the phone parts (not that there are so many). If I would be able to expose the conductors inside the flat cable I might be able to solder an alternative volume pad I'll make out of old some miniature switches I have. The cable is very thin. any Ideas of how to expose the relevant conductors without ripping the cable apart?
Just a (late) update:
It's been almost two years, I had given the phone to a close friend of mine after a couple of weeks since writing the first post, just in case he could resurrect it, nothing.
Then, a couple of months down the road, the phone suddenly woke up! He tried to connect it with the charger, after months of not being able to charge or boot it up and somehow it worked. And it has been working flawlessly ever since.
I just got it back to give to my girlfriend until her sensation is fixed, flashing Viper now
In case something like this happens to any of you, don't give up!
Not sure if anybody has seen this problem when I plug in my phone to charge it doesn't always (once every 2 or 3 days) recognize that I'm charging it. When I shut the phone down it does recognize the charge and can then reboot and it'll continue charging. However if I reboot without plugging the phone into the wall briefly, then it'll continue not realizing that I'm trying to charge it.
This has been going on for about two weeks now (I've had the phone for about a month and a half). The phone is rooted, but otherwise it is stock. I do two small but noticeable scratches in the plastic, so I don't know if verizon will let me get an exchange.
Anyway my question is has anybody seen this before? I found a couple threads on the reverse condition (phone thinks its charging when its not), but nothing on this condition.
What cord are you using to charge it and what is the amps on the little power unit? I was having some trouble on the plug that negri gave me and I use my old HTC 1 amp plug with my new Sammy cord.
A. Try a difft power unit
B. Try a difft cord
Sent from my Galaxy Nexus using XDA App
It's probably the charger. One of my car chargers will do that. Also, this doesn't sound like the case, but be aware that your phone won't charge if it's extremely hot.
Probably the faulty usb port issue. It is no way to fix it without changing the port.
Happened to me once. What fixed it was taking out the battery for 5 min, then replace it, and power up. Someone else was having the problem and another person suggested the long battery pull. Worked for both of us.
I'll try the long pull and report back.
I use three different chargers. The factory samsung charger, a Seido Docking Station (powered by a generic USB charger), and a generic USB cable for charging from my computer. Condition has been present on all three.
Is it recognized by your computer? If not, the USB port is probably the issue. If it is, then the battery pull may fix it. If that doesn't, make a Nandroid and do a full system wipe and see if that helps. Have you installed any apps around the time you noticed the issue? If so, uninstall that app, reboot and see if that solves the issue.
Example, I had TweetDeck kill my GPS once. Literally, I used navigation, got where I was going, remembered I hadn't installed TweetDeck, installed it, tried using navigation and it was busted, uninstalled TweetDeck and Navigation worked fine. I rebooted, reinstalled TweetDeck and all was good. Quirky things happen sometime.
any news on this? my usb port has recently stopped working but it still charges
Matt
I was rooted and running stock att, touchwiz for a while with no issues. It started to get slow and on my nerves (and I was thinking of all the empty promises about this phone like inductive charging, google wallet, JB4.2.2, faster than iphone etc.) so I decided to kick in the bucket and install CM10.1. Install went smoothly, I accidentally installed the wrong google apps, but realized it, reinstalled everything with the correct one, and all is well and dandy.
The entire time, the phone is sitting at 0% battery, so I am assuming I am barely charging enough for the phone to keep up with my usage, but it never actually dies so all is good. The icon says 'charging 0%'. I was messing around in the settings, and got to the LED color settings. Went to change the "low battery" one, and the current active one changes. I go to change the battery charging one, and nothing changes. I unplug the phone, and it immediately goes into shutdown mode due to low battery. I plug it back in and let it sit for like 5 minutes before actually booting it back up, and it boots up but battery is still at 0%.
Basically, battery drained its way down from fully charged to 0, and now won't go back up. The fact that the LED state thinks that it is "low battery" rather than "battery charging" leads me to think it is a bug. I checked the bugs thread that is stickied, and nothing comes up close to what I have. I am using the nightly build from 03-03-2013.
ph7ryan said:
I was rooted and running stock att, touchwiz for a while with no issues. It started to get slow and on my nerves (and I was thinking of all the empty promises about this phone like inductive charging, google wallet, JB4.2.2, faster than iphone etc.) so I decided to kick in the bucket and install CM10.1. Install went smoothly, I accidentally installed the wrong google apps, but realized it, reinstalled everything with the correct one, and all is well and dandy.
The entire time, the phone is sitting at 0% battery, so I am assuming I am barely charging enough for the phone to keep up with my usage, but it never actually dies so all is good. The icon says 'charging 0%'. I was messing around in the settings, and got to the LED color settings. Went to change the "low battery" one, and the current active one changes. I go to change the battery charging one, and nothing changes. I unplug the phone, and it immediately goes into shutdown mode due to low battery. I plug it back in and let it sit for like 5 minutes before actually booting it back up, and it boots up but battery is still at 0%.
Basically, battery drained its way down from fully charged to 0, and now won't go back up. The fact that the LED state thinks that it is "low battery" rather than "battery charging" leads me to think it is a bug. I checked the bugs thread that is stickied, and nothing comes up close to what I have. I am using the nightly build from 03-03-2013.
Click to expand...
Click to collapse
wipe cache/dalvik and reflash. if it does not clear the issue, full wipe and reflash. report back
Neither worked. I thought maybe I'm just playing around with the phone too much and not giving it a chance to charge, so I plugged it into a wall socket a couple rooms over so I wouldn't touch it. 15 minutes later, I turn it on and it is still at 0% charge. The phone is pretty hot at the charger port.
I'm starting to think this is a hardware issue, because it is also unresponsive when it goes into sleep/lock mode... Won't wake, and can't even call it. The only way to get it responsive again is a hard reset.
I should still have some time left on my at&t warranty, and I have a backup from when I was still on the original recovery. Where does CWM store the recovery files on CM10?
When I was using TW, they were just in a folder on the root called clockworkmod. They are actually still there, a couple "0's" down the line in the file structure... Not really sure what that does... Now the root has no clokworkmod folder, but it definitely is storing backups because I just backed up now, and restored to one when I originally installed CM10, and I can see them both when I select "restore" in the recovery menu. Is there any way that I can put one of my backups from my computer into that folder so that I can revert, unroot, and get this thing swapped out?
The battery has been giving me all kinds of issues since I bought it and all they offered last time I went was a new battery. Hopefully with it being unresponsive as well, they will just swap out the handset.
Update:
I was able to use odin to reflash the original rom, so I am back to the non rooted state. Battery seems to be working fine, and I haven't run into a hang on lock, so it is most likely software related. I am going to redownload all of my apps slowly and see if it is one of my apps causing the hang, but the battery issue seems to still be related only to CM10.1. After all that headache, I could care less if I go back to CM10, but I think maybe you guys would want me to troubleshoot this issue, so that you can possibly fix the bug?
Let me know.
ph7ryan said:
Update:
I was able to use odin to reflash the original rom, so I am back to the non rooted state. Battery seems to be working fine, and I haven't run into a hang on lock, so it is most likely software related. I am going to redownload all of my apps slowly and see if it is one of my apps causing the hang, but the battery issue seems to still be related only to CM10.1. After all that headache, I could care less if I go back to CM10, but I think maybe you guys would want me to troubleshoot this issue, so that you can possibly fix the bug?
Let me know.
Click to expand...
Click to collapse
Try AOKP next time
It seems to me...
It seems to me that the charging problem only happens when there are notifications waiting. As long as there are no notifications waiting, the red LED is on and the phone charges just fine. When a notification comes in and the blue LED starts flashing, charging stops or slows to a crawl or starts discharging. The longer this condition continues, the hotter the phone gets. After clearing the notifications, the red LED comes back on and the phone starts charging normally.
This seems to happen with Samsung chargers and off brand chargers.
Again, I don't know if this really happening. It just seems to all coincide.
therapyco said:
After clearing the notifications, the red LED comes back on and the phone starts charging normally.
This seems to happen with Samsung chargers and off brand chargers.
Again, I don't know if this really happening. It just seems to all coincide.
Click to expand...
Click to collapse
I have the same problem with at least 3 sammy based roms. If anybody has a solution please let us know. It is definitely related to the notifications.
how/what are you wiping before each flash?
Follow up...
It no longer seems to me that the flashing blue notification LED is the problem. I've identified two other issues with chargers.
The Samsung charger works well and fast, especially when plugged into the power outlet adapter and not computer's USB. I guess that's typical... something about only one pin being available for charging when the USB cable is connected to the port on the computer. The off brand charger (charger only, not USB/charger combo) was much slower and sometimes wouldn't charge at all.
The first I thing did was look at the tips. They are slightly different, but the thing I noticed is that two little "fangs" on the tips were more prominent/stiff on on the Samsung charger. I used a needle to pry/bend those fangs out on the off branded charger so that they pop out more. That resulted in a much more secure/tight connection to the phone and fixed the problem with the battery actually stopping charging or discharging while plugged into the off brand charger.
Next, I compared the power ratings on the two chargers. The off brand charger accepts 100-240VAC, 47-63Hz and 0.2A. Its output is 4.3-5.0V and a MAX of 0.8A.
The Samsung charger accepts 100-240VAC, 50-60Hz and 0.15A. Its output is 5V and 0.7A (seemingly a constant output no matter the input).
I hypothesize that the off brand charger's output is directly related to its input. So, the output at 120VAC input would be about 0.4A and the output at 240VAC input would be 0.8A. The Samsung charger, seems to have a constant output of 0.7A whatever the input is. So in the US with our approximate 120VAC, the off brand charger would put out maybe 0.4A and the Samsung charger would put out 0.7A or 75% more current than the off brand charger. This would explain the difference in charging rate between the two chargers.
I suppose I could get my multimeter out and verify this idea, but I'm too lazy and I'm satisfied with my hypothesis.
This happens to me once every 4-5 flashes. I usually get everything set up, reboot, then power down, remove battery for 30 seconds, power on (without charger), then plug in and it charges normally. If that doesn't work try enabling fast charge (if your kernel supports it).
Fast Charge FTW
I seem to be having the same issue as found on this thread, can't find anything here though.
https://www.reddit.com/r/lgg7/comments/90zo7k/wireless_charging_stopped_working/
Anyone else have the same issue and found a fix? Guessing this might have to go back to lg.
Thanks!
steveoidm said:
I seem to be having the same issue as found on this thread, can't find anything here though.
https://www.reddit.com/r/lgg7/comments/90zo7k/wireless_charging_stopped_working/
Anyone else have the same issue and found a fix? Guessing this might have to go back to lg.
Thanks!
Click to expand...
Click to collapse
I started getting this issue yesterday a day after I got a software monthly update for Nov. I normally shut the phone off to charge but sometimes leave it on. When plugged into something it doesnt seem to detect its plugged in. I even swapped cables to a slower charger and same thing. It doesnt see it.
When I fully charged it off, It beeps the battery and does a circle hue randomly by the home button but than detected the connection to pc. I ignored it and started up again but without the beeping, just wont charge when on. There is no dirt or anything in the unit,. I have not moved any-wires, they have been sitting in the same spot on the counter since day 1. I'm gonna try a factor reset if it keeps happening a day or 2 from now.
Same problem here, it was behaving strangely few days ago (charging problem right away but worked in the end so let it go) and now it charges only when off or if plugged within 30 seconds after turning on and only on normal charge speed (not quick charge). Tried to wipe apps and everything, did the facrory reset 2 times but still nothing.
I have similar issues with charging my g7, first give me notification of moisture detected on USB port, then can't charge normally need to plug a few times and sometimes get slow charging, i was thinking have faulty USB port, and have poor battery life.
Then I turn off and put the cable and charges normally and realized that it's software issue.
I flash the ULM10i firmware and now everything work flawless the USB port charges when it's turn on and have very good battery life now.
As an update, I called LG and they basically stated that it sounds like a software issue and to send the phone in. I declined hoping to get another update that would fix it.
I have yet to get one from T-mobile. Long story short, it corrected itself and now charges off or on and no longer does the beeping. Whatever it was, was a bug that temporary for me.
same problem here; no moisture errors, aleatory starts charging when it's on, poor battery life; mainly starts charging with the phone off
problem solved! I've forced LG BRIDGE to reflash the ROM and voilà, all working like a charm. Just download from lge.com, install LG BRIDGE, under "software update" ... "update error recovery" and it will download and reflash the working ROM.
Hey everyone,
has anyone experienced something similar and was able to fix it?
My TA-1043 has previously turned off overnight, or simply didn't charge occasionally. This behavior was reported by others as well, and wasn't really that much of a problem for me.
However today not only did it turn off, it also does not turn on or accept a charge anymore at all. I tried several different cables and cleaned out the charging port, but it just will not charge at all from either a power bank or a wall plug.
I ordered a replacement charging board, but if that doesn't work and no one else has had this problem i'm gonna have to get a new phone i reckon... (warranty only covers one year and the place i got it from charged extra for extended warranty)
And yes i also tried holding the power button for 30 seconds, does nothing as expected...
So, has anyone had this problem and knows what causes it?
replaced the charging board and now it works again, let's see if that was the root cause... interestingly, the battery was at 50% charge when it started working again, so i actually believe it's something to do with the mainboard
It's a Software Problem
The same thing happened to my phone recently. What I did was to to click on the power, volume up, and volume down for 40 seconds. It was one of the longest 40 seconds in my life. It turned on and the battery was at 49%. It worked fine after that. I don't know why it happened but the problem was a software one not hardware even though it didn't want to charge anywhere and was always seemingly off.