Just trying to gauge everyone else, but for me battery performance has been horrible since the update. It'll lose 5-10% in a matter of an hour. No more apps are running than when I was on 4.4.4. Anyone else experiencing similar issues?
Sent from my HTC One_M8 using Tapatalk
I haven't noticed any excessive battery drain during use, but I did notice this morning that the phone was not fully charged after I left it plugged in overnight.
GrandAdmiral said:
Just trying to gauge everyone else, but for me battery performance has been horrible since the update. It'll lose 5-10% in a matter of an hour. No more apps are running than when I was on 4.4.4. Anyone else experiencing similar issues?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yes I was having the same issues as you. Phone was perfect before the update. Charged quick and discharged normally. After the ota to lollipop everything went down hill. Was not rooted or bl unlocked all stock. Took my phone to att tech repair store and was told that I was not the only one they have seen with this issue. They did try to flash the firmware in store but it failed 3 times. Tech told me that he believes there are still bugs in the firmware. They did a swap for new device but I did not allow them to update it. Think I'll just stay with 4.4.4...
Edit....
Mine however also took almost 5 hours just to charge from 20 percent to 25 percent. I cleared cache factory reset and still did nothing to fix the problem. I tried ruu but unfortunately my win7 pc would not recognize in fastboot. Always had prob with pc in fastboot . But like I said above it prob would not do anything since att could not flash with the flash tool they use...
planetdroid33 said:
Yes I was having the same issues as you. Phone was perfect before the update. Charged quick and discharged normally. After the ota to lollipop everything went down hill. Was not rooted or bl unlocked all stock. Took my phone to att tech repair store and was told that I was not the only one they have seen with this issue. They did try to flash the firmware in store but it failed 3 times. Tech told me that he believes there are still bugs in the firmware. They did a swap for new device but I did not allow them to update it. Think I'll just stay with 4.4.4...
Edit....
Mine however also took almost 5 hours just to charge from 20 percent to 25 percent. I cleared cache factory reset and still did nothing to fix the problem. I tried ruu but unfortunately my win7 pc would not recognize in fastboot. Always had prob with pc in fastboot . But like I said above it prob would not do anything since att could not flash with the flash tool they use...
Click to expand...
Click to collapse
My battery life has sucked since the update thanks to the GPS randomly turning itself on even though I've turned it off.
Here's the thread where I mention it, it was a 4.4.4 thread but various people have had issues with lollipop as well.
http://forum.xda-developers.com/att-htc-one-m8/help/gps-android-4-4-4-update-t3041001/page3
I also tweeted #ATTSucks to twitter and their ATTCares representative has responded although I really don't see how they can fix this.
https://twitter.com/ATTCares/status/586226543212552192
Mine is weird. When idling, discharge is fine. Recharging I'd fine as well. It's when I use the phone when it drops like crazy. Like right now. Unplugged the phone about 25 minutes ago and the phone is already at 96%.
Sent from my HTC One_M8 using Tapatalk
Poor battery life confirmed...
I can confirm that my battery life has absolutely sucked since the update to Lollipop. It was bad enough that AT&T delayed the release of Lollipop for months, but now to finally have it and actually have a worse device than before, is really frustrating.
I have not changed any settings or installed any new apps since the update. I used to not have to worry about charging my phone until 10-11PM at night. But now, I often have to charge it between 5-6PM. Man, do I wish I could revert back to Kit Kat.
This battery issue is seriously making me consider rooting it so that I can install an older boot loader and revert back to stock Kit Kat.
Related
I RUU'd to Jan2012 OTA update, unlocked with HTCDev.com, installed AmonRa, rooted using AmonRa and everything has been fine....for about four days. Then yesterday, after using IM+ Free for a few days and liking it, I decided to buy the Pro version. Coincidentally, my extended battery was running out and I didn't have time to charge it at work, so I powered down, removed the battery, put my charged stock battery in and voila...boot loop. No signal at unlock screen, sits for 10 seconds, and reboots. I can do a factory wipe and it will boot, but if I restore anything...data only, system only, secure only...all 3, 2 of 3...doesn't matter...issue returns. Anyone know why this might be happening?
It's because you can't post in the right section!
Have you tried wiping and flashing a Rom? Not restoring
Edit: its probably because of a bad backup or because of the ota, its been known to bootloop
Sent from my ADR6425LVW using Tapatalk
Can a Mod please move this to general?
OT: Check the bootloop thread that will more than likely give you the answer you're looking for.
http://forum.xda-developers.com/showthread.php?t=1394659
My apologies for posting in the wrong section.
My concern is that it was running fine, and then suddenly wasn't when nothing but an app install (IM+) was done. I don't want to go through setting everything up again only to lost it all again four days from now.
I am having similar issues as you are. Tried to charge a 3.8v stock battery overnight and it bootlooped all night long. It seemed like it settled down after putting back in my 3.7v extended. So I called HTC and created a rma for the battery, no big deal.
Then today listening to music while the phone is in the dock i had a few reboots/bootloops, noticed some odd stuff in logcat so I did a reset permissions in recovery. Seems better so far compared to before where it would only take a few minutes to bootloop.
*mine is not the network issue, but good to hear you fixed yours
joblabbo said:
I am having similar issues as you are.
Click to expand...
Click to collapse
Yes, sounds similar...however, I ran my stock battery for about two weeks with no issues, and ran the extended battery for a good month with no issues, and even ran fine for a few weeks after htcdev.com unlock, AmonRA flash and rooting took place. This all came about out of the blue.
Right now, I am attempting to use the guide specified concerning connecting to the wrong type of network. I'll update when finished.
------
UPDATE: That worked. It was a communication issue, the phone had changed it's connection preferences. The sad part is that I've been without a phone for almost a day over this, and flashed all kinds of kernels and recoveries, and even considered going back to Verizon for a replacement. The even sadder part is that I already knew of this fix and completely forgot about it. Thanks a MILLION to MrSmith317, not only for directing me to the fix, but also for not bashing me for accidentally posting in the wrong area of the forum.
So two days ago my rezound started randomly rebooting...I thought it was the new ICS rom I had just put on (the newest leak) so I desided to nandroid back to an older ICS that ran smoothly before. Same reboots... and the phone gets hot. So I figured I would just let it rest a night and took the battery out. No Joy.
Today, I RUU'd back to stock and things were running ok for a while... but as soon as I plugged it in my car... reboot after reboot.
I bought it at Best Buy as they had a better deal and better insurance. My only concern is that big ReLocked on the bootloader.
Has anyone successfully returned the phone after unlocking? Hoping doing that didn't negate that insurance. I guess I don't mind stepping on accident on it if need be.
Have you tried this fix?
http://forum.xda-developers.com/showthread.php?t=1394659
No, I hadn't until now... will try tonight, but the phone will stay operational for a while... just seems to be when I charge it from the wall or car charger... charging using USB trickle charge, it doesn't reboot as much. I don't hink is has to do with the network connecting thing....as it does boot up and I can make calls... and search online, and use the navigator... until it just gets to hot.
Xsoldier2000 said:
No, I hadn't until now... will try tonight, but the phone will stay operational for a while... just seems to be when I charge it from the wall or car charger... charging using USB trickle charge, it doesn't reboot as much. I don't hink is has to do with the network connecting thing....as it does boot up and I can make calls... and search online, and use the navigator... until it just gets to hot.
Click to expand...
Click to collapse
I know this might be a long shot but since our devices don't have s-off, restoring nandroid backups don't restore the boot.img. did u try flashing the stock kernel? I'd try flashing the latest GB kernel, then flash the latest GB stock ruu? I had a similar issue and found out it was the kernel I was using. Was on anthrax kernel
Sent from my ADR6425LVW using XDA
Well, I RUU'd back to the OTA...renamed the .zip to PH___.zip and rebooted into fastboot and it updated everything. I then restart and everything is back to square one, like I just opened the box and activated it.
I presume the RUU flashes over the right kernel as released by Verizon.
I'm really thinking the battery is crapping out. can't hold a charge more the 42% and gets hot...then run out in like 20 minutes... throw in a couple reboots...and higher blood pressure ensues.
Xsoldier2000 said:
Has anyone successfully returned the phone after unlocking? Hoping doing that didn't negate that insurance. I guess I don't mind stepping on accident on it if need be.
Click to expand...
Click to collapse
I don't have insurance, but I returned a relocked Rezound to VZ online for overheating a couple months ago with no problems.
99 out of 100 times, the rep will not check to see if the phone is relocked, let alone if he knows how to check it.
You're worrying over nothing. If the device is defective due to manufacterer defect, and breaks down becaue of said default. They will honor warranty/exchanges since they are the ones at fault. Now if you fragged your phone because of an oc, bad flash, wrong software, that's your own bad and you're on your own. Unless you have insurance and the phone met its untimely end under your vehicle.
Thanks for all the help... I went and bought a new battery for it, and it does the same thing. Re-locked and bringing it back to best buy today. Fired up my ole OG and flashed the newest MIUI release... the phone is still kicking!
So, two days without the rezound and I'm tweaking..... need to flash a Rom! (Maybe this will be good for me.....)
TL;DR check the last post
Has anyone else been experiencing random reboots lately? Mine seems to be intermittent, i used my phone for three hours straight two days ago and everything was fine. The damn thing just rebooted on me three times in the span of about an hour, two were within ten minutes of each other. I'm running cleanROM v1.4 with no cpu control apps, and I haven't changed anything in about 1.5-2 weeks.
Sent from my ADR6425LVW using Tapatalk 2
Just did it again. I'm about to smash this damn thing against the wall!!
Sent from my ADR6425LVW using Tapatalk 2
I'm running CleanRom 4.5 and have only experienced 1 random reboot. My girlfriend on the other hand is running stock gingerbread and experienced 5 random reboots yesterday. I asked her what she was doing at the time, and she was of no assistance. Definately something to keep an eye on!
I got pissed and wiped everything, then reinstalled CleanROM DE with only the apps I use frequently and everything has been fine so far, haven't had one yet. Maybe it was a buggy app or something else because during this time my extended battery said it was at 80% then after one of the reboots it said 17% and I was like wtf? After the clean install it said 66%!
Sent from my Transformer TF101 using Tapatalk 2
I lied, it just did it again!
Sent from my Transformer TF101 using Tapatalk 2
brando56894 said:
I lied, it just did it again!
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
Are you s-off ? if not make sure you are flashing the boot.img after installing the ROM. Or if you are on GB firmware your installing the firmware patch if installing an ics ROM.
Sent from my ADR6425LVW using XDA
Yea I have, it's nothing that simple sadly. At first I thought it was a buggy app so I wiped /data and only installed a few apps I use constantly, but it still happened. So I did a fresh install of the current rom I was on and didn't install any apps or restore any data, but it still did it. I just flashed another rom without restoring anything to see if it still happened and it did. I had an idea that it may be the latest radio image that caused it so I flashed to the one before the latest leak, but it still does it.
I'm currently in the process of flashing the original GB RUU to see if it still does it. If it does then I know it's definitely a hardware problem. If you couldn't already tell yes I am S-Off
So the RUU didn't fix it but it did lessen the reboots. Now when I wake the phone up while running Gingerbread the data connection will take a minute or two to connect and will drop out sometimes while the screen is on.
It rebooted on me last night. Also during the night it did a factory reset (or I did it in my sleep!) because when I woke up the phone was at the "choose your language" screen and after I left that all my downloaded apps were gone.
I also just got the OTA adr6425lvw_2.01.605.11-1.02.605.6 but it won't stick.
WTF is going on here? Do you guys think I need to do an insurance claim?
casper99801 said:
I'm running CleanRom 4.5 and have only experienced 1 random reboot. My girlfriend on the other hand is running stock gingerbread and experienced 5 random reboots yesterday. I asked her what she was doing at the time, and she was of no assistance. Definately something to keep an eye on!
Click to expand...
Click to collapse
My GF's stock Rezound reboots pretty frequently too... Mine never does, even stock it didn't. After the last fiasco with VZW and sending phones back and forth she's not going to want to swap it out again :-/
brando56894 said:
So the RUU didn't fix it but it did lessen the reboots. Now when I wake the phone up while running Gingerbread the data connection will take a minute or two to connect and will drop out sometimes while the screen is on.
It rebooted on me last night. Also during the night it did a factory reset (or I did it in my sleep!) because when I woke up the phone was at the "choose your language" screen and after I left that all my downloaded apps were gone.
I also just got the OTA adr6425lvw_2.01.605.11-1.02.605.6 but it won't stick.
WTF is going on here? Do you guys think I need to do an insurance claim?
Click to expand...
Click to collapse
While your on the stock unrooted untouched ruu do a factory reset from hboot. Then boot up reboot to recovery and flash your Rom.even though I'm soff I still reflash my kernel in hboot after wiping boot.
Sent from my ADR6425LVW using xda premium
I'm giving it a try now and I'll see what happens, thanks.
Sent from my Transformer TF101 using Tapatalk
Edit: In the past 8 hours I haven't had any random reboots or radio problems (yet), but the battery stats still seem to be wacky (another symptom I forgot to mention). I had the phone off because the battery was dead and I was charging it at my cousin's house. When I left I turned the phone on and in a span of about ten minutes it first reported a reading of 40%, I opened an app for a few minutes and when I looked at it again it was down to 20%, a minute later it was down to 9%. I decided to shut it off for a few minutes, took the battery out and put it back in, then after I booted up it showed 55%! I also had my extended battery with me at the time which I thought was full but when I put it in, my Rezound just went to the white HTC screen and after a battery pull it wouldn't turn back on so I figured it was dead. I just put it back in now and tried to charge it, it's actually at 94%!
I'm currently on GB Firmware, running CleanROM DE v1.4. Before yesterday (?) I have been on ICS Firmware since the initial leak of ICS IIRC.
It just started this crap again about 4 days ago, I was getting one per day on ICS. I ran the original GB RUU four times (twice, tested it out for a few minutes and noticed that data kept dropping out, then ran it again twice) and it still does it.
Before I ran the RUU I was on ConROM when it started so I flashed Nils latest work, when it started to happen again I flashed the kernel in TWRP, when that didn't work I flashed it directly via HBOOT (extracted the PH98IMG from the zip), which still didn't fix it.
I'm beginning to think that I did damage the radios during the S-Off process since I was one of the people that had been trying to run the exploit since v0.01, also during the later tries I realized that I was shorting out the wrong pins at one point After I switched to the correct pins and used v0.02 or v0.03 it works and I had S-Off.
I'm about to go back to S-On and see if it still happens.....
Just came back from Verizon and they're going to replace it for free since it's covered under the MFG warranty since the phone is only 8 months old.
I love how clueless their employees are: I told a guy that my phone was rebooting constantly and that that it keeps losing its connection to 4G (then demonstrated that it had lost it's connection even though mobile data was turned on and when I cycled it it would re-connect), he was about to mention a factory reset but I said I had done about 20 factory resets (didn't mention RUUs or anything) before he even got the words out, so he passed me off to their "tech guy".
Here's the real kicker...
I told him that the data radio keeps shutting off and it reboots constantly. His response was "the what?!" I told him 4G/the internet connection and that I've done numerous factory resets and he then said "we'll ship you a new one."
This is about the 5th time and 3rd different store where Verizon's employees have no idea what the hell I'm talking about. Half the time it isn't even tech related, I've schooled them on their own products and promotions multiple times (namely the 2 month return policy before christmas and the half-off extended battery deal [2 out of 3 employees in the same store didn't know that one])! It's pretty damn sad when a customer who reads Android blogs knows more about the promotions than an official Verizon employee....
brando56894 said:
Just did it again. I'm about to smash this damn thing against the wall!!
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Afaik all android phones do this. Buy an iPhone
Thanks for the helpful response! Ass... I had the original Droid for a year and the incredible for about six months, neither of which did this once. I've also had the Rezound since launch day, I could could the number of times it did this before a month ago on one hand!
Unless you have something useful to contribute STFU.
Sent from my Transformer TF101 using Tapatalk 2
brando56894 said:
Thanks for the helpful response! Ass... I had the original Droid for a year and the incredible for about six months, neither of which did this once. I've also had the Rezound since launch day, I could could the number of times it did this before a month ago on one hand!
Unless you have something useful to contribute STFU.
Sent from my Transformer TF101 using Tapatalk 2
Click to expand...
Click to collapse
If a phone randomly reboots in your pocket, or while you're sleeping... Would you know? I had 7 origional droids, 5 bionics, a rezound, a gnex, and a galaxy tab. I have yet to own an android device that doesn't randomly reboot. I have had devices up tor 11 days without it happening, but inevitability, it happened. I think its related to ram. I never really looked into, but its just a hunch. From what I see on my rezound it is just the shell rebooting and not the device. You are just too much of a fanboy to see that due to many factors, especially fragmentation, that android is super clunky. It is also generally bugged. I am typing this on my bugged sense keyboard, from my bugged WebKit browser. What made android good was open source. It isn't like that anymore.
I upgraded to 5.1 the other day using the package offered on Huawei's own site. Had to use the force upgrade method, which I did while the phone was plugged into an outlet using the factory charger. Since then, my battery has crapped out on me. I left it to charge all night and when I woke up it was still stuck at roughly 30%. In the span of two days I have tried multiple chargers and performed a factory reset. Somehow I managed to charge it up to 78%, but now it's stuck at that percentage. Anyone have a clue what could possible be preventing it from fully charging?
I have not seen this or heard it from anyone else. Maybe your hardware has an issue?
kimtyson said:
I have not seen this or heard it from anyone else. Maybe your hardware has an issue?
Click to expand...
Click to collapse
That's what I was thinking. As 322 rewrites pretty much everything coming from 4.3. The batteries are hard to replace. But it is doable. Someone posted about doing it. And there is a video of it being done on YouTube. You could also try reflashing 322 first.
I've read one other report on the Huawei forum of someone having a similar issue, except he is able to recharge only after the phone has been discharged to 9%. My thoughts are maybe there is some kind of power conservation trigger or something? I've never had any problem charging my phone to 100% prior to installing the update. If it is a hardware issue, it chose the perfect time to malfunction...
I'm gonna try to downgrade back to 4.3 and see if the issue persists.
Rb8623 said:
I've read one other report on the Huawei forum of someone having a similar issue, except he is able to recharge only after the phone has been discharged to 9%. My thoughts are maybe there is some kind of power conservation trigger or something? I've never had any problem charging my phone to 100% prior to installing the update. If it is a hardware issue, it chose the perfect time to malfunction...
I'm gonna try to downgrade back to 4.3 and see if the issue persists.
Click to expand...
Click to collapse
That should work to. First i have heard of it on stock ROM. Still may want to try reflashing 322 first. Then4.3. Some ran into issues reverting to 4.3. The file system changes evidently can screw up. Let us know how you resolve it in case someone else runs into the same issue.
Moody66 said:
That should work to. First i have heard of it on stock ROM. Still may want to try reflashing 322 first. Then4.3. Some ran into issues reverting to 4.3. The file system changes evidently can screw up. Let us know how you resolve it in case someone else runs into the same issue.
Click to expand...
Click to collapse
Just curious, I'm completely new to android, but could you possibly point me in the direction of how to proceed with reflashing 322? Gonna try it when I get back home from work this afternoon.
Rb8623 said:
Just curious, I'm completely new to android, but could you possibly point me in the direction of how to proceed with reflashing 322? Gonna try it when I get back home from work this afternoon.
Click to expand...
Click to collapse
http://forum.xda-developers.com/asc...ex-huawei-ascend-mate-2-updated-2015-t3149530
That thread has everything you may need in it. Just download the 322 update to your SD card and boot holding down all three buttons. Volume up and down and power. Let it run. Here is Huawei official page with the download and the instructions.
https://community.gethuawei.com/sup...15/06/30/mate2-android-l-update-now-available
I think you probably already did that, but want to mention it regardless. Have you tried turn off phone completely, the boot up and charge? Also charge it when phone is off? I am saying this because the other days I learned reboot the phone is different from turn off then turn on.
Tried downgrading to 148 yesterday, woke up with a 25% charge, same as it was when I plugged it in last night. I also tried the above recommendations for charging while the phone is off, restarting, etc. I have scoured other forums for this issue and found similar stories with other model phones. I'm now thinking it's a hardware issue with a mechanism that senses the battery's status.
Rb8623 said:
Tried downgrading to 148 yesterday, woke up with a 25% charge, same as it was when I plugged it in last night. I also tried the above recommendations for charging while the phone is off, restarting, etc. I have scoured other forums for this issue and found similar stories with other model phones. I'm now thinking it's a hardware issue with a mechanism that senses the battery's status.
Click to expand...
Click to collapse
Very odd indeed. Have you tried completely draining the battery? Then charge while phone is off.. Is it still under warranty?
I have had luck disconnecting the battery, rebooting on outlet power and reconnecting the battery.(this WILL VOID your warranty) Not gospel thou, could have been luck. Reflash if you didn't already first. There are some screwy things that happen, I for instance have a phone that I cannot get back to JB for anything. When it boots it uses stock android bootanimation from system/bin not /cust folder.
If you replace the battery peel carefully or you'll break the LCD.
I don't think its battery thou.
Yep. Tried all of the above. After downgrading to 148, the phone wouldn't even charge even while plugged in. Fortunately, it is still under warranty so I'm sending it in to be serviced...
Unfortunately for me, the entire reason I bought this phone is because it is unlocked and I am leaving for Germany next friday. I bought it hoping to be able to plug a sim from a local phone co. overseas and just go. Now I'll probably have to get a relative to ship it to me after they finish repairs.
And by the way, I initially installed B322 using the forced method. I didn't think it would make a difference. Guess I was wrong.
Rb8623 said:
Yep. Tried all of the above. After downgrading to 148, the phone wouldn't even charge even while plugged in. Fortunately, it is still under warranty so I'm sending it in to be serviced...
Unfortunately for me, the entire reason I bought this phone is because it is unlocked and I am leaving for Germany next friday. I bought it hoping to be able to plug a sim from a local phone co. overseas and just go. Now I'll probably have to get a relative to ship it to me after they finish repairs.
And by the way, I initially installed B322 using the forced method. I didn't think it would make a difference. Guess I was wrong.
Click to expand...
Click to collapse
Sorry we couldn't help. Was worth a shot. Stay safe on your trip.
So I recently had Marshmallow firmware version G900TUVU1GPE1_G900TTMB1GPE1_TMB installed and had gotten tired of the update service running and trying to download a firmware update, I used these directions here to root my phone and then install Titanium backup to turn off OTA updating services and ES file explorer to delete the update.zip file
http://forum.xda-developers.com/tmo...l/root-how-to-root-sm-g900t-firmware-t3358190
I recently started having an issue with the phone whenever I would use it with GPS enabled or off, it would reboot and get back to the unlock screen and then go into a reboot loop, which would only stop if the battery were pulled. This happens in Apps too such as Google Play or Facebook, or Accuweather. I figured I'd try to install the Stock KitKat version of G900TUVU1BNH5_G900TTMB1BNH5_TMB, well the reboot loop issue still exists. Is there anyway of resolving this issue as I am thinking of putting GPE1 back In and Redoing the root just to undo it. I know it is forbidden to check NAND Erase All or other firmware options in ODIN. I downloaded a partition/PIT file just i ncase I need it too. I'm pulling my hair out lol.
Thank you
Upate, After I reinstalled G900TUVU1GPE1_G900TTMB1GPE1_TMB, and did a normal system recovery (no TWRP in at this point) I had enabled WIFI and it went into a reboot loop, took the battery out, then I installed TWRP- went to advanced wipe, did not select System, Only Davlik, Internal, Cache. I have not installed SuperSU. I hope this resolves the issue, otherwise I might need a new phone or motherboard...
Did you pull the battery as soon as it boot looped? Mine always loops once after flashing firmware, but boots normally on the second attempt without pulling the battery.
invisiblewave said:
Did you pull the battery as soon as it boot looped? Mine always loops once after flashing firmware, but boots normally on the second attempt without pulling the battery.
Click to expand...
Click to collapse
I have been pulling the battery, plus another oddity is when the phone goes into a loop and I can't get it to stop until after a bit, I can just plug the charger in and then It stops. Someone said the battery could be at fault. I bought a battery and waiting on it between the 14th and 16th, I will definitely follow up if that resolves my issue too.
invisiblewave said:
Did you pull the battery as soon as it boot looped? Mine always loops once after flashing firmware, but boots normally on the second attempt without pulling the battery.
Click to expand...
Click to collapse
Well I believe the Issue has been Resolved, I got the battery yesterday, charged it up over the night and started using it today, so far no random reboots or bootloops.
Differences
The Battery that came with my phone was Made in China, the one I just bought is made in Vietnam.
I will keep yall posted after a few days to see if it has any issues.
Well the battery Fixed my issue.
I'm on my third battery and still looping... Anyone else have any ideas?
workingmomjd said:
I'm on my third battery and still looping... Anyone else have any ideas?
Click to expand...
Click to collapse
go back to stock 4.4.2 rom is the most I can say at this point
The 5th was the charm (I hope!)! Going on day two and at 78%, so the rapid battery drain that started right before the looping is also cured. It's a good thing this is the last of 4 Samsung s5's so cycle the house, so I had lots of spare batteries on hand Thank you!
workingmomjd said:
The 5th was the charm (I hope!)! Going on day two and at 78%, so the rapid battery drain that started right before the looping is also cured. It's a good thing this is the last of 4 Samsung s5's so cycle the house, so I had lots of spare batteries on hand Thank you!
Click to expand...
Click to collapse
i come to notice the battery that came with my phone stated made in china, the new one I ordered said Made In vietnam. I believe batteries made in china is what caused the Note 7s to go up in flames along with Surefire Flashlights to overheat and catch fire too