Have searched the forum and Google and haven't found anything yet. Usually good at performing obscure random searches but not this time. First off, I am running stock rooted 4.4.4 NI2. Running xposed and wanam but haven't found anything pertaining to my dilemma there either. Onto my issue...
I noticed after I got the phone a couple of months back that it wouldn't be at 100% when I woke up. Usually would be around 97 or so... No big deal. I tested chargers (my wife has/and had an s5 before I purchased mine) and cables with no real difference that I could see. I figured it was some type of protection built into the phone so when it achieved a full charge, it would stop charging until needed. I was perfectly fine with this, but that wasn't the big issue. I have also noticed that if I plug my phone in to charge and end up having to move to another outlet or get into my vehicle, when I plug it in again it won't charge.
The screen will come on acknowledging that it is plugged in, but it will not charge for an extended amount of time. It is almost like the phone has protection built-in so that if there is an issue with a charger/port connecting and disconnecting continuously, it will inhibit the charging until it has a consistent current. I, for instance, am about to head to the gym and wanted to charge my phone before going. It was at 13%, plugged into my nightstand charging. My wife and son got home and are going to take a nap so I unplug and go into the living room to continue charging. It was at 31% and when i plugged it back up a few seconds later it would not charge. I kept it plugged up as i was typing here and it didn't resume charging until is over halfway through writing this post. (5-10 minutes maybe? Haven't tried counting it exactly... Yet) Haven't heard or seen anything like this previously on multiple devices (Samsung, htc, 3 nexus devices, etc.) and haven't been able to find anything online so thought I'd ask here.
Also, sorry if anything isn't stated in a way to describe things perfectly. If anyone has any questions or thoughts, I would truly welcome them.
Thanks in advance.
Sent from my SM-G900V using Xparent Blue Tapatalk 2
Related
Ok heres my problem,
My phones battery is completely messed up. The phone ALWAYS says that its at %99 battery(and the number never decreases) but after a couple of minutes of use it will turn off by itself, no warning or anything.
I think I know how it happened(as a warning for other ppl). I went on vacation once and I didn't have a charger cuz there were no computers at the hotel, so I brought a random USB wall charger I found laying around(which I later found out it belongs to some spy pen camcorder ).
Unfortunately though it was charging SUUPPERR slow, so I got the crazy idea to charge it while it was off and to my surprise(dramatization) it charged (a lot)faster.
So I kept charging it like that every day and I noticed that every charge took less time than the last. It also started turning off by itself, though not as frequently as now. I thought the problem would fix it self once I charged it on my computer again, but I was wrong. TT_TT
---
Can anyone offer any solutions? I have a G1 with CM5 and clockworks recovery. I know clockworks recovery lets you do something with the battery, but idk how to use that
please help, this is a REAALLY annoying problem thats forced me to go back in time
You need to make sure it's putting out the same amount of power as your regular charger. I'm not 100% sure of this, as all I can do is charge at my computer and I have no idea how that works (as in if computer puts out waaay more power or has a limit of how much to put out) but I've always heard too much can be a bad thing for batterys. Also, don't overcharge.
^^Just posted that in another thread.
sounds like a died battery
I've seen a few people with the exact same problem around the web, but no one has ever posted a solution (if they ever found one).
The kids were playing Angry Birds on the Nook before dinner, when I went to turn it back on after dinner it wouldn't boot (was working when I put it down).
When I plug it in the wall charger the light is always green.
When I plug it into a computer USB port it is momentarily detected as omap 3630 instead of Nook Color like it used to, then windows reports that it's been disconnected.
It had been running CM7 for a few weeks off of emmc, but now I can't even get it to boot from a uSD card into CWM.
When plugged in (computer or wall charger) I can see the backlight turn on and off every few seconds.
No combination of button presses seems to have any effect (power, power+n, power+n+vol+, etc.)
Try holding the power button for a full minute... release and try turning it on again... see if that don't do it.
Thanks for your reply.
I wish that worked, but I don't even see the back light flicker on for a split second unless it's plugged into the wall or a computer.
It's a shame too, I got it as a Christmas present from the wife and our toddlers really loved to play the games on it. They keep asking where "bad birdies" went
Your problem sound similar to an issue I had with charging. I has a bad charger/usb cable. Its a known issue and BN will replace it for free. If you are registered, call BN support a request a new one. I have done this twice. Once when the end bent and a second time when I had a green N but not juice (just flicker and/or a 'plug in the charger' symbol). The NC requires more power than the typical usb charger/cable setup, thus spares usb chargers AND cables around the house do not work.
I hate to do this because it was so maddeningly frustrating to see the same thing posted in the thread about boot problems here and elsewhere, but it turned on today and I have no idea why.
I'd been messing with it for a few days and finally after an unsuccessful morning I left it on my dresser. I was in the kitchen making hot chocolate after playing in the snow with the kids when my two year old comes walking down the stairs with the nook and drops it at my feet. When I went to pick it it, it was in the process of booting. Whether he had done something to it or the short fall jarred something that was loose I can't say, but it now seems to be fine.
It had about 50% battery and the lights on the charging cord now respond like they should.
I have no idea what happened, but I wish I did so I could help others in my boat.
Still could be your charger/usb cable. When the charger/cable start going bad, it takes for ever to charge. Like all day just to get enough juice to boot up. If it dies again and doesnt reboot after its been on the charger for a few minutes or you're only getting a partial charge over night, its the charger and or cable.
It charged fine overnight.
There definitely must be something loose on the inside. If I give it a fairly significant whack (nowhere near a punch, but harder than a tap) it will reboot. I think it was a refurbished unit. The newer units seem to have serial numbers where the first four digits correspond to the year. The first four digits of this one are 2004! Looks like they never fixed what was wrong in the first place.
You just ran it too dead. It won't power on until it's established a decent charge first.
Sent from my MB865 using xda premium
Sorry if this question has been answered somewhere, I couldn't find it, but I didn't know exactly how to word it.
Anyways, I have a galaxy tab 4, the 7.0 one, and it's charging has been strange lately. I would plug it in when it got to around ten percent, and keep it in. Occasionally it would give me the message to plug in the charger despite it being plugged in, so I thought it might be a faulty charger.
Though after leaving it over night and having it only go up one or two percents, I restarted it, and when it came back on, it had 100% and after that, the battery percentage went down at a normal speed. When using the tablet when it was plugged in and didn't charge, it acted like a tablet normally would when it was going to lose battery (giving me the warning, dimming he screen, etc.).
Do you think this is a charger problem, or a problem with the tablet (or both)?
Note: my tablet has been dropped once onto a hard floor, but nothing happened to it that I've noticed other than the sd card popping out of place, which was easily fixed by just putting it back in and restarting. The charger cord has a few bites on it from forgetting it on the floor with my young dogs, but I noticed them quickly and stopped them, so there's only a few ltitle marks and none of them look deep enough to do much damage (though I've never had samung products before, so I don't know how tough their chargers are).
When in doubt, go ahead and get a new charger. (Keep it away from those dogs too.) If you have the same problem with your tablet, then a call to customer support may be in order.
Sent from my Samsung Galaxy Tab 4 8" model using Tapatalk
My 6P on 6.0.1 stock with the march update has had occasional times where it will intermittently charge, then stop, then charge endlessly, changing back and forth about once a second or more often. There's been times I've woken up, like today overnight when I noticed it barely inched up a percent or two on the Google USB-C cable connected to my laptop.
To isolate this from being a defective cable issue, this has also happened with the Google charger that came with the phone. I would see the screen turn on in fact, like when you first plug the phone with the screen off, to indicate charging has begun. That would occur every few seconds.
I'm a little concerned. The time it happened with the charger, a reboot seemed to have calmed it down. But today no matter the restart, the charging just keeps cycling nonstop.
Anyone else had this? Would it be wise to file a problem with the Google forums and contact support?
Thanks for any help!
Same problem here
Dang, good to know I'm not alone!
I've also experienced higher battery drain (twice more I'd say) than normal recently. Even overnight when I used to see hourly drain rates of 0.5%, now I see 1.5% and higher. Getting worried the charging issue may be damaging the battery. But it could also be the patch or a rogue app.
I have the same issue - it started about 3 days ago
Well either the cords bad, the brick is bad, or the receptacle. Or the charging port on the phone, the battery or power control module in the phone. Or if theirs a thick case on your phone.
Sounds like it starts to charge then stops. But I'm no electrician. Oh wait, yes I am.
It starts to charge, then stops as though the cable was disconnected, then resumes within half a second, then disconnects, and so on and so forth non stop.
Case might be a reason. It's a rubber and plastic transparent Spigen one. I'll try removing it when it happens again next time.
But at this rate, sounds like 3 people are having the same issue, and if it's a hardware one, then damn....
This isn't the charger... There is something buggy with the update. I woke up a few days ago after the march update with an almost dead phone, and the charging icon flashing over the battery, as if the phone new it was plugged in but refused to charge. I unplugged and plugged it back in with the same result. I restarted and tried again, same result. I was only able to get it to charge my plugging it into my girlfriend's nexus 5x charger, which instantly started charging my phone. I went back to my charger and all of the sudden no issue and the phone was charging fine. There is definitely something up with this update.
Well then, that makes 4 people now.
What's a good way to report this?
I'm not seeing the same exact issue as you guys, but I AM having charging issues after updating to MHC19I. I can still charge my phone from the stock charger and my other USB-C chargers, but now none of them allow my phone to charge rapidly. Do you guys who can get your devices to charge from a rapid charge compatible charger see the "Charging Rapidly" message on the lock screen? Ever since this recent update, I've noticed that my device isn't (and is taking over 2 hours to charge fully from ~20%).
I have this problem too. It's fixed by a reboot so I'm assuming it's not a hardware problem. It only happens once a week or so.
The first time it happened I didn't notice the charging/not charging and only realised something weird had happened because my phone was off & showing fully charged. My phone is never switched off.
I figured it out the next time when I noticed the screen was still on during the night. Switching from charging to not charging was keeping the screen on.
So glad it's not just me.
flightsimmer said:
I'm not seeing the same exact issue as you guys, but I AM having charging issues after updating to MHC19I. I can still charge my phone from the stock charger and my other USB-C chargers, but now none of them allow my phone to charge rapidly. Do you guys who can get your devices to charge from a rapid charge compatible charger see the "Charging Rapidly" message on the lock screen? Ever since this recent update, I've noticed that my device isn't (and is taking over 2 hours to charge fully from ~20%).
Click to expand...
Click to collapse
I normally see it say that on the USB C charger. That being said, you seem to have an intermediate speed going on, as opposed to super slow normal USB cable speeds and the USB-C fast charger. In my experience most 1-1.5V low amp ports like my Mac's, or the car's USB port will charge at a rate of about 1% per 3-5 minutes. So a full charge would take 8-9 hours from 0%. From the USB-C wall charger it would be about 1%/m so an hour and forty is enough to get it back to full.
Based on that your charger seems to be somewhere in the middle.
But yes it isn't normal. If you are using Google's native hardware, you should see the same charging speed as I am.
I'm just terribly worried this cycling is destroying my battery. I have definitely not gotten the same battery life the last few weeks.
Hey guys!
I experience sort of the same problem as you guys, but i have the Nexus 5x
i copy from my thread at google nexus forum
My phone just randomly die. It will work for like 2 hours. Almost like the battery would been disconnected.
When the phone shutdowns it says the battery is low and try to charge. The Battery icon with a flash is showing, but just for 5-7 seconds, then it shutdown again and it's looping again and again and again.... To get out of the loop i'm booting in to fast boot, then push at start. and it is almost 50/50 if it is working. It can be booting up and you see the red/yellow/green/blue yada yada boot-up sequence then in 5-7 seconds in to the sequence it would shutdown again immediately.
I tried several factory-resets. re-flashed to stock. Nothing helps.
/marcus
Same issue
Just starting having this issue. It constantly says charging then a second later shows no charging and the process keeps repeating itself. I did a reset and the issue seems to be resolved for now. Really hope this isn't a constant issue. Definitely appears to be software related though.
zxphenomenalxz said:
Just starting having this issue. It constantly says charging then a second later shows no charging and the process keeps repeating itself. I did a reset and the issue seems to be resolved for now. Really hope this isn't a constant issue. Definitely appears to be software related though.
Click to expand...
Click to collapse
I hadn't had it for a while then recently it happened again once. I still don't know what triggers it for sure.
The battery drain is also rather random. There are days I can expect the unit to idle and drain at or below 2%/h, but lately it just goes through it way faster, twice that. I am unsure why and how that happens so randomly. Seems the Google Play Services and Google Apps are using up some %s. Not much else I can identify.
I've had this issue since a few days ago, restarted the phone and it's come right for now.
Haven't experienced this in weeks now.
Seems largely gone.
Any updates on this? My Nexus 6P started showing the same symptoms (either won't charge at all, or charging cycles on and off rapidly (< 1 second) and only sometimes charges). The issue appeared out of the blue 4-5 days ago, just before the 1 year anniversary of receiving the phone. I tried different cables and adapters, still no change. Last night at 11pm it was at 50% when I set it to charge and it seemed to charge. This morning at 6:30 am it had only charged up to 83% and was charging on and off. Worried about how to reliably use the phone if it won't charge, and also how this might affect the battery / other circuitry.
Any help/tips appreciated!
Edit: The phone hasn't been dropped or had any other issue that may affect the hardware. Also, no OS update or anything recently (AFAIK - it did not ask me to install anything, not sure if there were any silent updates). It is currently on Android 7.0 Nougat (baseband version angler-03.72, build NBD90X, security patch level Oct 5, 2016).
Have not had this in a long time. It sort of stopped on its own. :S
Solved (for me anyways)
I just had to restart the device.
I'm having the same issue on my LG G5. Started out of the blue and like others, restarting temporarily solves the problem. Anyone solve this yet?
Now that my DT2 updated to 6.0, it has developed a showstopping problem. It instantly powers off at random times, usually when I'm using it. Worse, the power button is ineffective at restarting the phone. The only way to restart it is to plug it into a power source and then press the Power button after it acknowledges that it's charging.
It used to do it only one or twice per day, but now it's doing it constantly.
I've already performed a factory reset and then a cache wipe, with no change.
Verizon confirms that it's happened to others, so it's not just me.
Is it possible to revert my DT2 back to Android 5.1.1?
Has anyone else here experienced this, or have any suggestions, before I tell Verizon to send me a new phone?
Thanks in advance.
Sounds like a hardware issue to me, especially if it did it prior to the update as well.
Sent from my DROID Turbo 2
imnuts said:
Sounds like a hardware issue to me, especially if it did it prior to the update as well.
Sent from my DROID Turbo 2
Click to expand...
Click to collapse
I should have mentioned, it never happened in 5.1.1.
yep, i'm having this issue as well since i updated to 6.0 three weeks ago. started about 3 days after the update, i plugged my phone in over night and i woke up to it dead. couldn't get it to charge worth anything. would only go to 4% and stop. using original charger. won't go into turbo charge. stopped by the store and picked another charger and a portable battery and used the pre-charge on the battery and it finally started charging again, but not at the turbo rate it should have. it drained the pre-charge and got to about 45%. plugged in in once i got home and it still didn't see turbo charge, took about 6 hours to finish charging. over the next few days it was still slow to charge and would randomly lock up and then reboot itself. a few days later i woke up to the phone almost dead again, even though it was plugged and showed charging all night.
did some research, found more people with the same issue. Lenovo/Moto and Verizon support all suggested put it in safe mode, then see if it still does then same thing when all the third party apps are disabled. did this and yes, it still charged slowly, and while plugged in it the battery was still discharging (percentage number was dropping... pretty quickly). the next idea was a factory reset. haven't done that one yet myself.
here is a page to one of the lenovo threads about. seems to be the main on there at this point .
https://forums.lenovo.com/t5/DROID-TURBO-2-by-Motorola/Turbo-2-won-t-charge/td-p/3261260
I just posted this thread in the general forum for the DT2. Wasn't sure if you'd tried this yet or not - but solved many issues for me.
http://forum.xda-developers.com/droid-turbo-2/general/cqatest-app-marshmallow-causes-issues-t3386929
I also had issues with my DT2 charging. After upgrading to MM, the quick charge was sporadic, and it wouldn't work. Then I had issues with the charging port in general. If i barley wiggled the cable it would not charge, or send files via a computer.
I went up to a local Verizon store, explained my issue, and i had a replacement phone in about 3 days. They ran a special test to test all of the hardware on my phone, and sure enough when it got to the last test, which was the usb port, it failed.
I received the replacement phone with MM already installed, and have not had any issues with the usb port...so far. LOL
I ended up sending my phone back to Motorola; just got it back and it's till got 6.0 on it. It repeated this showstopper behavior twice today. NOT HAPPY.