Hey guys feel free to merge this but I was unsure where to put it.
After following the breaking news yesterday about the 30fps fix for Epson screens I decided to flash the godmode kernel on my fresh 0.3, but I did so without checking what type screen I had. Apparently I have a novatech and the fix didn't work. No biggie I was sort of expecting this. But later that night when I went to charge my phone, it would start to charge then stop. I rebooted it, same, pulled battery, same. So I had to restore a nandroid backup and it fixed itself. So I'm not 100% sure what caused this but just wanted to share my experience.
This happened to me again. This time it was the v8 avalaunch froyo rom with the 1.2 oc kernel. It runs ok till the battery needs to be charged then it will not charge. Again a revert to stock kernel fixed it.
There is something with the cords.
Did you buy a third party cord?
You have to you the exact cable the came with the phone. If it charges off that cable, then your good. That means, you went cheap on buying a crap cable they won't work with this phone.
Just because its says its micro usd, does not mean it will work.
Related
I am running DC v1.0 and i feel like ever since installing this ROM
after being on Fresh 1.1, my batter takes forever to charge via the wall
outlet (AC power). I followed all of the steps on xda as far as properly getting damage's rom to install on my phone. Running 1.6.2 recovery, and i did not upgrade my radio but that really shouldnt have any effect on how long it now takes to charge my phone. I have yet to monitor how long it would take using USB cable. Anyone else experiencing this? When i was running 1.5 while rooted, the phone would charge in no time (could go from 25% to full in about 1.5 hrs). Now it seems that an hour charging will only net me another 15% or so in battery life. Any suggestions on something i can tweak/fix or even monitor why this is happening?
ringer79 said:
I have yet to monitor how long it would take using USB cable.
Click to expand...
Click to collapse
I'm also running DC v1.0 and from what I can tell, if I plug into a USB port and am actually using the phone, it pretty much only "keeps up". Meaning that the battery doesn't go down, but it doesn't seem to be charging significantly either.
Haven't noticed any difference plugged into the wall. I can go from dead to fully charged in a couple hours (haven't timed it, but I'd guess about 2 1/2).
Same here, really annoying. I've been charging the thing all day...
:/
Try this. It allows the phone to sleep properly, and also helps charge time.
this is one of those off the wall things that made me flash back to fresh 1.1...lol there were to many little things that would work. but then wouldnt,, and im sure its a combo of things etc.. but i got tired lol and went back..
spiritcrusher33 said:
this is one of those off the wall things that made me flash back to fresh 1.1...lol there were to many little things that would work. but then wouldnt,, and im sure its a combo of things etc.. but i got tired lol and went back..
Click to expand...
Click to collapse
Haha I read all the positive things, decide I will take the plunge, then this makes me just go right back to fresh...jeez lol
I've was using 5.2.3 for the last several weeks and to begin with, it worked wonderfully.
Until around 10 days ago, I'd never suffered any rapid battery drain problems, then all of a sudden one morning, I woke up and the phone was at 10% charge despite being left on charge overnight.
I figured there was an issue with the ROM and decided to reboot. This seemed to work fine for a day. Then the same charge problem was back.
I thought the ROM was now failing so decided to install the latest version 5.2.6 directly over 5.2.3 but the problem still persisted so the problems didn't seem to be ROM related but could be due to the unwiped areas but this seemed unlikely.
Just as a final test I decided to change the cable. I normally use the cable provided by HTC as it seems pretty sturdy. Turns out it was the cable all along.
The phone is now charging fine with a different cable and it's running fine again.
So, if you're having problems with overnight power drain when your phone is on charge, try changing the cable.
Edit: There is no visible damage to the cable and it has never been stressed in anyway as I take great care not to stress the pressure points.
Thanks for the info mate. Probably not in the right the right section though.
Your response to that post is probably in the wrong section. Oh, wait..! [email protected]*!t now this post is probably in the wrong section, see what you started.
Sent from my Inspire 4G using xda premium
My cable just stopped working yesterday. Or well, it worked before flashing ARHD 5.2.6 and after it stopped working. I didn't believe it had anything to do with the rom and not sure that I still do, but still an interesting coincidence.
Sorry for posting in the wrong thread everyone. I don't create new threads very often so I wasn't thinking clearly.
Diffler said:
My cable just stopped working yesterday. Or well, it worked before flashing ARHD 5.2.6 and after it stopped working. I didn't believe it had anything to do with the rom and not sure that I still do, but still an interesting coincidence.
Click to expand...
Click to collapse
I'm not saying the cable problem was caused by the ROM - I was just explaining how I identified that the ROM I was using wasn't the cause of the battery drain.
Cables breaking are very rare - happened once to a phone cable once after engineers had been called out to check the fax machine about 6 times before someone gave the cable a try.
I have faced an odd issue: I bought a new Z3, and it came with MM. Except, well, my favorite mods (from a Z3C) were all geared towards Lollipop. Easy enough right? It's just, y'know, a downgrade away! So I did just that. Downgraded all the way back to KK, Rooted, backed up my TA/DRM's, Put a recovery and downloaded .264, Making myself a PreRooted.
It installed just fine, and everything went well... Until I left it overnight to charge. And got it with 60% charge on the other day.
Well, after that, I tried just about everything one could think of: .232, Custom Kernels, Custom Roms, Mods, EVERY ******* THING. I even got it under the Sleep of Death (and Back, thanks Rubber Bands!) once! It only charged above 60% in Marshmallow, When Powered Down, or With an AOSP Rom. It was maddening!
...This issue lasted for... (checks proof of purchase...) exactly four weeks, where I flashed something or another, went to work, and tried to charge it either at lunch or coffee breaks, to no effect.
Turns out it was really simple: Retail Demo. Before deleting it, make sure to disable it by dialing *#*#SELLMORE#*#*. Otherwise it locks maximum charge at 60% to protect the battery. Smart, for a Retail device, except... Well, I bought it fully sealed.
I'm just leaving this here in case anyone is facing the same issue. G'night (or day, afternoon, evening... whatever) Guys. Now to debloat, mod and customize and finally get to use my phone how I want it!
Hi, guys. I recently bought a new battery for my 1+ two and after replacing it I've been having some problems. The battery life is actually lower than before and some times my phone suddenly turns off. Is there some way to calibrate or recalibrate a new battery or something I can do to fix this?
First of all, is your battery an official one or a third party battery? If its an official battery, check the manufacturing date. I'm not sure if oneplus is still producing/selling oneplus 2 batteries; it could be quite old. If its a third party battery, then I'd say its fake and of bad quality.
Yeah, I got one too. Manufacturing date is March 2017, and mine is also pretty bad. The turn-off thing happened once to me. But it really seems weaker than the original one. I thought that it needed time to go up to its full potential, but it's been 2 weeks and it's not good. Either we go back to the original battery or we go for a new phone.
Exactly the same problem. You are not alone. I went out yesterday and it just turned itself off and i couldn't turn it on . Didn't have a phone for 5 hours. And not only that MTP doesn't work (I'm not blaming the battery of course). It's not even showing as an unknown device in the device manager I wanted to perform a format, flashing an img via fastboot and I can't. #neveragain
Ok, so I bought a new battery because this one started to drop really fast. I got one from Ebay for $15 (last one was 30 from amazon) and it came really fast and visually it looks exactly like my original battery (the amazon one looked a bit different) only the manufacturing date is 03/2017. SO when I tried to remove the current battery, the connector got stuck to the socket. And I really tought that was going to be the end of this phone, but I removed it after some trying and put the new battery. Hope this one is better, if not I'll go for a new phone.
I recently bought a new battery from here:
https://www.replacebase.co.uk/oneplus-two-replacement-internal-battery-3300mah-fa-p597-original/
They claim its an 'OEM' battery, but its quite clearly a knockoff.
I also experienced some of the issues mentioned in this thread:
Phone powering off when fully charged (80-90% capacity) - and not powering on again until I plug into mains
Fast discharge - I'd struggle to get 12 hours out of a full charge, even with minimal screen-on time.
I'm not entirely sure whether the fast drain and phone powering off was related to the OS / Kernel I was using. For a long time I was using the lineage nightlies, recently I moved to Francos Kernel and also installed the flashable 'v3' zip from this thread: - https://forum.xda-developers.com/oneplus-2/general/power-tweaks-snapdragon-810-devices-t3261790 - which definitely looks to have reduced the idle drain and overall drain quite a lot. Also my phone no longer turns off randomly.
Additionally:
Removed all widgets
Turned off ambient display, turned brightness down
Turned off all gestures
Prevented facebook app from running in background - https://www.xda-developers.com/runinbackgroundsetter-restrict-background-processes/
I need to switch back to my original battery to see if I get better performance than the 'OEM' battery I bought - as potentially the battery drain issues I was having before were purely down to the software / kernel
edit: - still getting phone shutdowns with the 'OEM' replacement battery. Currently using https://www.cmxlog.com/14.1/oneplus2/#lineage-14.1-20170831-nightly-oneplus2-signed.zip and Franco Kernal r11
HELP!!!
I picked up an H918 for my wife to use on T-mobile USA. Since it was used, I also got one of the extended life 4100Mah batteries to hopefully make it last at least the entire day without topping off the charge. She usually averages around 4 - 5 hour SOT, so this seemed like a good option from what I've read, and fits in the original door so I can use the wallet case she wants with it.
But man, her battery life is TERRIBLE! I checked with Accubattery, and it reports that the battery is charging within 99% of it's 4100mah spec, so I don't think its a bad battery. Yet, she can barely go 12 hours with just under 2 hours SOT before the phone dies!
She is unrooted, running stock Oreo.
I installed GSam Battery Monitor and used their ADB commands to give it permission to record deep statistics w/out root (pretty cool, never did that before). I ran it for a little while this morning. Within 3 hours 40 minutes off the charger, she was already down to 72% with barely any SOT. I'm attaching screenshots of the app usage and doze screen (sorry for the phone-snapped-of-phone picture, it's my wifes phone like I said, so it was easier to just snap with my camera than take a screenshot and send it to myself to post).
Maybe I'm not reading this right, but it seems like something is keeping her phone from sleeping. A big culprit seems to be call services, and in my location settings, I noticed it mention that LG IMS was doing a lot of heavy battery drain with location related inquiries.
I thought maybe it was related to WiFi calling, so I turned that off. Cell reception is average.
2 hours later, she's down to 50% so that wasn't it. I don't know what else to try other than hard reset, but we literally just got this and set it up 2 days ago, and its been like this from day one. I don't see why it would be any different the second time around.
It's likely a junk battery. It's really hard to get a good oem replacement battery.
If you shop Amazon look for a Taeozi 4200 or Shemnz 4200. They both have 2 year warranty and decent reviews here on XDA
The Perfine 4100 is also highly recommend
Any Li-polymer should be better
Sent from my ONEPLUS A6010 using Tapatalk
When I bought my wife's phone it had a battery drain/overheat and wakelock issue as well. I fixed it and haven't had an issue since. Here's what I did to fix it:
https://forum.xda-developers.com/v20/help/absolutely-terrible-battery-life-t3531456/post78654160
clsA said:
It's likely a junk battery. It's really hard to get a good oem replacement battery.
If you shop Amazon look for a Taeozi 4200 or Shemnz 4200. They both have 2 year warranty and decent reviews here on XDA
The Perfine 4100 is also highly recommend
Any Li-polymer should be better
Sent from my ONEPLUS A6010 using Tapatalk
Click to expand...
Click to collapse
I did my homework first and got the Perfine from Amazon, not a no-name junk battery. When I couldn't fit it without removing the sticker, the seller was really helpful and actually offered to replace it after checking first that it fit in *THEIR* V20 at the factory. Really solid customer support. And according to Accubattery, it really is the capacity it says. Or at least within 99% of it (I think it estimated 4080 or something like that). So I don't think that's the issue.
pistacios said:
When I bought my wife's phone it had a battery drain/overheat and wakelock issue as well. I fixed it and haven't had an issue since. Here's what I did to fix it:
https://forum.xda-developers.com/v20/help/absolutely-terrible-battery-life-t3531456/post78654160
Click to expand...
Click to collapse
That's actually really interesting- I did take apart the phone to do the thermal mod thing (wiped off the dried up pink gunk and put a thermal pad there), but it seemed pretty clean otherwise inside when I did. How on earth did you figure out that was the problem?
After speaking with some folks on Telegram, Reddit, and other corners of the internet, I have a different theory. A bunch of people told me to let the rom "settle", that battery life is never good after a fresh format or new rom flash. Honestly, the critical thinker in me says that sounds like nonsense. I've never heard of this before and I've been flashing roms for the better half of a decade. I'd think after it takes the time the load up your apps and settings and configure itself, it would be done. But I Googled it, and it seems to be a hotly debated subject.
Those that swear by it claim that whenever you start fresh or flash a new rom, it takes anywhere from one to a few battery cycles before the kernel calms down. Perhaps it is doing some sort of internal calibration based on your battery life and system demands or something like that. The theory seems to be that the Kernel doesn't allow the CPU to fully doze until it is done with this process, which sometimes takes days. I don't know, but the more I read about it, the more it sort of started sound plausible. When I got the phone, I tried out some things on it myself without a SIM card first, just to make sure everything on it checked out before giving it to the wife. Then, I did a hard reset, popped in her SIM card and let it do its thing. That's when we realized battery life was pretty terrible, as after 10-12 hours she already needed to charge... and this was on the 4100mah perfine!
I tried another hard reset, and when that didn't fix it, I decided it was time to root and see if I could get to the bottom of the bad battery. It seemed the kernel was where a lot of it currently went according to battery stat apps. After downgrading my H918 to Nougat so I could install TWRP, I promptly flashed Alpha Omega Oreo 20H and restored her apps. Turns out the next morning we couldn't sync her smartwatch, somehow we broke bluetooth (going into BT settings would crash the phone everytime). So weird, and while we were at it the battery life still wasn't great. So I did a hard reset that evening and found that even with nothing installed, BT was borked. (looking back at it, I think I should have flashed an Oreo rom like the stock 20H rooted first, and THEN the AO rom. I think going straight from nougat might have led to a driver mismatch or something)
Anyway, after that didn't work I flashed the stock rooted 20H rom, and lo and behold bluetooth and everything else is working again! But the battery has been bad all along and is still doing its generally suckiness thing.
BUT... as someone pointed out, if this kernel settle thing is real, I've been pretty much flashing and resetting this thing every other day. If roms need to "settle" first (still a debatable subject), than I never really gave it a chance yet and that's why I'm constantly seeing battery drain from things like Kernel even on different roms! And @pistacios, is it possible that you were having a kernel do the same thing since it was just reset and it just so happened to be that when it calibrated itself you thought you had fixed it by cleaning out the USB port?
All I know is I'm going to give this a couple of days before deciding on a plan B. Seems too simple to be the reason, but hey- I'm desperate.
Dishe said:
I did my homework first and got the Perfine from Amazon, not a no-name junk battery. When I couldn't fit it without removing the sticker, the seller was really helpful and actually offered to replace it after checking first that it fit in *THEIR* V20 at the factory. Really solid customer support. And according to Accubattery, it really is the capacity it says. Or at least within 99% of it (I think it estimated 4080 or something like that). So I don't think that's the issue.
That's actually really interesting- I did take apart the phone to do the thermal mod thing (wiped off the dried up pink gunk and put a thermal pad there), but it seemed pretty clean otherwise inside when I did. How on earth did you figure out that was the problem?
After speaking with some folks on Telegram, Reddit, and other corners of the internet, I have a different theory. A bunch of people told me to let the rom "settle", that battery life is never good after a fresh format or new rom flash. Honestly, the critical thinker in me says that sounds like nonsense. I've never heard of this before and I've been flashing roms for the better half of a decade. I'd think after it takes the time the load up your apps and settings and configure itself, it would be done. But I Googled it, and it seems to be a hotly debated subject.
Those that swear by it claim that whenever you start fresh or flash a new rom, it takes anywhere from one to a few battery cycles before the kernel calms down. Perhaps it is doing some sort of internal calibration based on your battery life and system demands or something like that. The theory seems to be that the Kernel doesn't allow the CPU to fully doze until it is done with this process, which sometimes takes days. I don't know, but the more I read about it, the more it sort of started sound plausible. When I got the phone, I tried out some things on it myself without a SIM card first, just to make sure everything on it checked out before giving it to the wife. Then, I did a hard reset, popped in her SIM card and let it do its thing. That's when we realized battery life was pretty terrible, as after 10-12 hours she already needed to charge... and this was on the 4100mah perfine!
I tried another hard reset, and when that didn't fix it, I decided it was time to root and see if I could get to the bottom of the bad battery. It seemed the kernel was where a lot of it currently went according to battery stat apps. After downgrading my H918 to Nougat so I could install TWRP, I promptly flashed Alpha Omega Oreo 20H and restored her apps. Turns out the next morning we couldn't sync her smartwatch, somehow we broke bluetooth (going into BT settings would crash the phone everytime). So weird, and while we were at it the battery life still wasn't great. So I did a hard reset that evening and found that even with nothing installed, BT was borked. (looking back at it, I think I should have flashed an Oreo rom like the stock 20H rooted first, and THEN the AO rom. I think going straight from nougat might have led to a driver mismatch or something)
Anyway, after that didn't work I flashed the stock rooted 20H rom, and lo and behold bluetooth and everything else is working again! But the battery has been bad all along and is still doing its generally suckiness thing.
BUT... as someone pointed out, if this kernel settle thing is real, I've been pretty much flashing and resetting this thing every other day. If roms need to "settle" first (still a debatable subject), than I never really gave it a chance yet and that's why I'm constantly seeing battery drain from things like Kernel even on different roms! And @pistacios, is it possible that you were having a kernel do the same thing since it was just reset and it just so happened to be that when it calibrated itself you thought you had fixed it by cleaning out the USB port?
All I know is I'm going to give this a couple of days before deciding on a plan B. Seems too simple to be the reason, but hey- I'm desperate.
Click to expand...
Click to collapse
Ive experienced ROMs settling in and battery stabilizing after a few days. But this was pretty far back with the HTC M7 and M8. Most modern phone's I've flashed pretty well settled in within the first few hours. The battery life on this phone was never amazing. It was good to just Ok for most when it was new.
If you flashed the stock rooted rom and still had bad battery life, I still suspect the battery itself. I still recommend one of the battery I listed earlier. If the perfine didn't work out try a different one.
Sent from my ONEPLUS A6010 using Tapatalk
clsA said:
Ive experienced ROMs settling in and battery stabilizing after a few days. But this was pretty far back with the HTC M7 and M8. Most modern phone's I've flashed pretty well settled in within the first few hours. The battery life on this phone was never amazing. It was good to just Ok for most when it was new.
Click to expand...
Click to collapse
Right, with the stock 3200mah battery. With the Perfine 4100, a lot of reports are saying 6-7 hours SOT or at least a full day of regular use. That's good enough, really. Mine is dying at half of that. I'm wondering if I have faulty hardware. I could put the stock battery back in and see if it dies much sooner.
I'm actually wondering if someone can check their mA use per hour with the screen on vs off, and I can see if the numbers make sense on mine. Accubattery is pretty good at the math.
Dishe said:
.....
And @pistacios, is it possible that you were having a kernel do the same thing since it was just reset and it just so happened to be that when it calibrated itself you thought you had fixed it by cleaning out the USB port?
....,
Click to expand...
Click to collapse
Phone was up and running for 2 weeks, so it wasn't due to fresh reset.
GSAM battery monitor showed kennel wakelock, something about USB OTG in the top of the list, so I figured the port was my first check for a problem, and it was. It wasn't obvious that there was dirt or foreign matter in there, because it looked clean. But sure enough, after the light brushing with 94% alcohol, the problem disappeared.
I'm not saying this is definitely your problem, just throwing it out there.