I'm having issues with this POS phone that I can't understand. If I use any charger at all, including the provided charger and cable, it used to say something about slow charging and that I should use the stock charger. Now it doesn't even bother warning me 99% of the time, it doesn't even give me a time til complete on the lock screen.
I'm at stock everything and fully updated on the t-mobile version of the One M9.
If I factory reset the phone it charges for a couple weeks but does the exact same thing. I've already had this phone replaced once for the same issue, the replacement behaves exactly the same way. I've used custom roms, deleted apps like facebook, and tried keeping the screen brightness all the way down. Absolutely nothing has helped for more than a couple weeks. Right now it's on extreme battery saver and has been sitting at 27% for 30 minutes. I've also looked into the battery optimization option in the settings and that literally does nothing at all. If I enable it it'll just sits there doing nothing. If I exit and come back it's switched back to disabled.
These are just a couple of the more pressing issues right now, I've had nothing but problems with this horrible phone since I bought it. And I used to love HTC. I've had 5 HTCs, a bunch of Samsungs, an LG, and a few generic Android devices. None have been as bad as this thing. Worst camera I've used since 2009. Slowest boot time, except for the generic tablets. App install times are easily three times longer than any device I've ever used. Oh, god, and updating is always at least an hour long process. I just don't understand how their quality dropped so far in just a few years. Anybody have any tips or ideas as to what might be happening or should I just cut my losses and get another Galaxy?
Related
I had thought I was one of the many SOD sufferers out there, but I'm not 100% sure now based on the symptoms that are happening with my phone versus others, so I wanted to create a new thread and just let you know what happened to me (and what is occurring right now).
I ordered my TP2 the day it was released through T-Mobile. I'd gone two or three weeks without having any issues. I didn't really install too many CABs on there (with the exception of updating Bing, mobile Netflix, Astraware Solitaire, the battery increment fix, and TouchLockPro).
I put the phone on the charger one night, and the next morning, I clicked the Power button to unlock it. It vibrated, indicating it was powering on (versus just unlocking). I thought, Okay, no big deal. Maybe I shut it off by accident.
The next day, it was off the charger, and I clicked on the Power button to unlock, and it wouldn't turn on at all. (This is where my issue seems to differ from the SOD sufferers... their phones are making noise and actually functioning, but their screens are black, so they can't really do anything with the phone until they reset.)
I panicked, but shoved the phone back on the charger. Thought maybe the battery was dead (though I knew the last I looked at it, it was at 82%). Nothing happened. The light did not light up to indicate it was charging or fully charged.
I took the phone off the charger and pressed the Power button again. The red light flickered off and on, but nothing.
I plugged it back into the charger. Kept pressing the power button. Nothing. Then suddenly it turned on. It worked fine.
This happened maybe one more time before I left for vacation two weeks ago. The phone seemed to work just fine until about two days into my vacation. Then that started happening again.
But this time, it was worse. The phone would turn back on, and as soon as it got to the passcode screen to log into the phone, it would shut off. Sometimes, it'd let me get two numbers in, but most of the time, I couldn't even get one digit in before it shut off.
This would happen about six times in a row, and then the phone would just flat out not turn on for an hour or so.
As the vacation wore on (it was tiring, as our itinerary was on our phone, so there were times we didn't know where we needed to be because I couldn't get the phone on... I had a hard copy in the room, but that would mean having to travel back to the room to get it, losing an hour or two, so it wasn't worth it), it started to get worse. More times of getting to the passcode screen. More times of it shutting off before I could enter the number. Then it got to the point where I couldn't turn it on for four or five hours at a time.
No matter what I tried, the phone continued to "die". Everything that seemed to work turned out to be a coincidence.
What I tried:
1. Reset button.
2. Pulling the battery out.
3. Pulling the SD out.
4. Pulling the SIM out. (Would boot up the phone sans SIM. Then put it back in and boot it up again. I THOUGHT this worked, as I went from last Wednesday to yesterday with it working, but alas, it occurred again, even without the SIM in).
5. There were times I even squeezed the phone a certain way because it seemed like the phone responded more when I held it tighter.
6. I was wary that something I installed (like TouchLockPro) was causing the problem, so I upgraded to latest version, still occurred, then removed.
7. Believe me, there was a ridiculous number of OTHER bizarre things I tried (not including a TP2 voodoo doll), but I'm too embarrassed to mention those!
Outside of formatting the phone, I had exhausted all of the possibilities. I even logged on here while I was away to find out if anything had changed with SOD, and it seemed like nothing new occurred.
I had had it when the problem started again yesterday, so I went to a local T-Mobile retailer. Imagine their surprise! The battery was swapped out, and that didn't change anything. Removed the SIM, removed the SD, it occurred over and over again (which was great! I was actually able to prove the issue).
The man I showed it to called Support, and Support was dumbfounded too, so T-Mobile is replacing the phone. I should have it in a few days.
After all that, the phone came back last night. I know it'll die sooner or later, so it's best I'm getting a new one.
I think I probably would have been fine about this experience except it occurred while I was on vacation. Like I said, it had our itinerary. It was our gateway to the pets at home (texts, emails, pictures). It was really our only connection to the outside world. Granted, when you're on vacation, you don't want that, but I definitely want to know our pets are still alive! I also like to know where I'm supposed to eat! It was definitely a black cloud over our trip. (Thank you, though, to xda-developers, for keeping me sane when I DID have access!)
I am still pretty sure it's hardware, based on everything I've done, read, and seen over the past couple weeks. I was hesitant about setting up the phone the way I have it now, but I need to prove to myself that it's faulty hardware first before blaming applications.
But I wanted to share my story (albeit long) with everyone out there. People may be having the same issue but don't want to post, so if you are, you're not alone!
Been coming here a while.. forums are nothing new to meh.. we'll skip the fact I just made this account and immediately made a thread ^^;
We'll get right to the details:
Had her since Autumn last year. Best phone I've ever used. No problems besides freezes I know I caused, etc.. never an issue. Til about October this year. Seen similar issues, looked for two months and found nothing close besides a Nexus 7 that physically needed its battery pulled for it to power on again. Anywho, here's how the moment went down: In the span of an hour or so, my GNex had crashed on me about three times... normally it'll do that maybe three times a day to three a week, depending how hotplugx on leankernel felt that day (having only one core on 90% of the time was pretty sweet). Was running the PA 3.99 based "Built With Love" ROM- the first build to incorporate any Saber stuff afaik- and the flat out 8.0 version of leankernel. Now.. the laast time she froze, the battery was already near dead, so when I popped it back in I plugged it up to the charger. All going as normal, right? Done this plenty from tinkering with kernels and seeing which android ROMs & versions I could hop back and forth to without wiping (had the current said setup for a month straight, surprisingly) Nope. It brings up the charging logo with the lighting bolt in the middle of the battery... and freezes there. Pulled out the cord, waited a bit and everything. Nada. Freaked out, I popped the battery. Went to put the battery back in and power it.. nothing. Okay, maybe that just killed the charge. Nope. Power cord fails to bring up any kind of light or charging animation. No screen activity. Will not boot into odin, recovery, or anything.
The ONLY signs of life still coming from this phone, are heat when it's on the charger, heat after 'USB jumping' the phone -after disconnecting the cord as well, and for at least two hours it continues producing heat- (had to do that when I first got it from Google) , and if I plug her into the laptop via USB WITHOUT a battery, it'll show as "OMAP 4440" for a split second in device manager.
Any more details will come from answering questions. As this happened over two months ago, I'm a little fuzzy on outright recalling details.
Cannot find this problem elsewhere at all. Either it's rare or I suck at looking around.
So I'm coming to you guys. Is she bricked? Stuck in charging.. idk what. Toolkits won't detect a device either, even after the USB jump when I know the battery is discharging and the phone is -technically- powered on.
If you guys could help me out for Christmas, even if it's to tell me she's busted, it would be so indescribably appreciated... <3
[Edit] Nabbed this really quick (attachment). Holding the button combo for download/odin mode has Windows searching this.
No battery inserted, as the dialog disappears and the taskbar pops with a bubble saying "device not recognized" etc. when the battery is put back in or is simply in it when plugged into the laptop.
Also to note: a third party battery yields the same results as the stock one. What kills me is Windows can see it, but aside from that and the heat production, it's essentially dead. What gives? :c
Shameful bump. Need to know if it's completely bricked, or possibly a hardware issue that's repairable or not.
Had to save up for over a year for this phone. Really need to figure out if it's gone or not. If it is, then I'll need to start saving for an N5, which I consider a downgrade ._. Can't beat the community support though, and that extra screen space :3
Aside from irrelevant blabble.. any answer would be appreciated. I can provide any additional information if need be, as well.
Have not seen this issue anywhere.
Bump..? :c
There's almost nothing on charge animation freezes. And what there is, the owner was able to boot their device with some simple workarounds.
If there's anyone who knows what's going on, even to tell me I'm a retard who bricked his phone, please do. Please.
Can't even afford glue to put my shoes back together. Saving up for another phone is impractical this year and probably next as well :\
Would I need the OMAP 4440 driver and some other stuff? If there's some way to push a boot.img to /boot while the phone is in this state, that would fix it..
I'm somewhat sure, at least. Since the kernel's in charge of that from what I understand.. any ideas?
Search for OMAP flash. I think your phone can be revived. i can't search right now but i believe there are some tutorial about OMAP flash of galaxy nexus. Good luck
So for the last few months, my phone would randomly restart itself around once or twice a month. I didn't really care since it was a minor annoyance. Usually it would be when I was trying to do a bunch of things at once so I figured it might be a software problem. However, over the last two weeks or so, it has gotten worse. I usually charge my phone in the morning for about an hour while I get ready for the day. So by the time I leave the house, my phone is at 100%. What'll happen is I'll unplug it from the charger then will get about ten/fifteen minutes of uninterrupted usage before the screen goes black and the LG logo comes on. And the phone turns back on with less battery. Then, as I go to put in my knock code, it crashes again. Turns back on. Now with even less battery. This continues about five or six times until I'm left with anything from 3-15%. I can't make calls without the phone turning off, can't take pictures. Can't really do anything. However, there are no problems when the phone is charging. I can use it fine during that. I'm almost positive this is an issue with the battery (going to order a new one soon), however I just wanted to see if anyone else had this problem too and found a fix?
(rooted D851 with xposed)
khandaboss said:
So for the last few months, my phone would randomly restart itself around once or twice a month. I didn't really care since it was a minor annoyance. Usually it would be when I was trying to do a bunch of things at once so I figured it might be a software problem. However, over the last two weeks or so, it has gotten worse. I usually charge my phone in the morning for about an hour while I get ready for the day. So by the time I leave the house, my phone is at 100%. What'll happen is I'll unplug it from the charger then will get about ten/fifteen minutes of uninterrupted usage before the screen goes black and the LG logo comes on. And the phone turns back on with less battery. Then, as I go to put in my knock code, it crashes again. Turns back on. Now with even less battery. This continues about five or six times until I'm left with anything from 3-15%. I can't make calls without the phone turning off, can't take pictures. Can't really do anything. However, there are no problems when the phone is charging. I can use it fine during that. I'm almost positive this is an issue with the battery (going to order a new one soon), however I just wanted to see if anyone else had this problem too and found a fix?
(rooted D851 with xposed)
Click to expand...
Click to collapse
had this same problem many times. For me it's the battery. The battery really sucks on this phone.
Still_living714 said:
had this same problem many times. For me it's the battery. The battery really sucks on this phone.
Click to expand...
Click to collapse
X2 Same problems, same solution.
This past week, I purchased a 2014 Note 10.1 off Craigslist. I did check it out before buying it, and the device is in pristine condition, including the screen. It booted fine, and I went partway through the setup (the guy had factory reset it) before closing the deal. It is the wifi-only model, 3G RAM, 8-core Exynos version. It's white if that matters.
Anyways, a while later when playing with it some more, completing setup, etc, it just died on me. I wasn't home, and didn't have a place to charge it until I got home, but just figured that despite the device having said the battery was 99% charged, the guy keeping it unused for a long time might have thrown off the battery calibration. My understanding is that a Li-ion battery has one or more cells, plus circuitry that protects against overcharging and undervoltage conditions, as well as tracking the current charge state. With lengthy non-usage, the circuitry's idea of the current charge can get out of sync with reality, so I figured a few charge-discharge cycles would get it back in shape.
However, the situation after I got home turned out to be a little more complex. If I plug in the device to a power source with enough current (like the charger it came with, or my 2.1A USB outlet by my bed), it will run just fine while plugged in. However, upon unplugging, it would die quickly. Naturally, I assumed the battery was probably shot, so resigned myself to spending $50 on one. This is where it started to get a little weird. It seemed that when I booted into either fastboot or Odin mode, it would stay on much longer than normal, while unplugged. I'm talking hours, rather than between several seconds and several minutes while booted into the OS proper.
This lead me to believe that perhaps it wasn't my battery itself, but rather a glitch in the OS that was causing it to shut down. When I say shut down, I mean an immediate full-off state, not a nice shutdown or one preceded by low battery warnings. It just clicks off like a light that's been turned off. However, trying several different firmwares, including a couple custom ones, has not yielded any improvement. The issue remains.
The device was stock 5.1.1 when I bought it. I tried flashing KitKat (various images downloaded from SamMobile), but for some reason, it would still say it was running 5.1.1. I tried xKat, as in this thread. That results in 4.4.2 with the associated customizations, but the shutdown issue remains. I tried CyanogenMod 13, as instructed here. It works fine, notwithstanding the same issue. In between the stock firmwares (pushed to the device with Odin) and the custom ones, I would do a full wipe through TWRP.
I've popped the back off, disconnected the battery, waited a bit, and reconnected it.
Now my question: does anyone have any idea what's going on? If it's a dying battery, then why does the device say it's got a nearly full charge, and why no low battery warnings? Why would Odin mode or recovery (TWRP now) seem to keep the device powered up so much longer? Sure, they draw less power, but hundreds of times less power? I doubt it. If it's some hardware issue with the chipset/motherboard/etc, then why does it only manifest when running on battery, or a low-current USB connection? If it's an issue with Android itself, then why does nobody else seem to have this issue (googling revealed nothing that matched my symptoms), and why did several different versions exhibit the exact same problem?
I really don't want to spend money on a new battery and wait a few weeks for shipping if there's something else I'm missing that could get my device functional for free and a lot faster.
My tablet had a similar issue, in that when you would get to the 15% mark, I had maybe 3-5 minutes before it would get to 0% and abruptly turn off. I used the battery calibrator app for rooted devices, followed the instructions, and now all is good again. For me, I noticed a variance from what the OS was reporting and twrp was showing in between flashing. For what its worth, I'm on the KitKat bootloader, and haven't used an official Samsung firmware since KitKat. Oddly enough, the battery calibration having been off survived through lollipop and into marshmallow. Hopefully you can get your tablet back on track.
Sent from my SM-P600 using XDA Premium HD app
Thanks for your reply.
siralsmooth said:
My tablet had a similar issue, in that when you would get to the 15% mark, I had maybe 3-5 minutes before it would get to 0% and abruptly turn off.
Click to expand...
Click to collapse
That's a bit different from my issue. Even when the device reports full charge, if I unplug it, it usually dies within seconds, and always within 2-3 minutes.
siralsmooth said:
I used the battery calibrator app for rooted devices, followed the instructions, and now all is good again.
Click to expand...
Click to collapse
I don't think that's going to make a difference for me. From what I was reading, all it does is delete the batterystats.bin file (hence the root requirement), which doesn't have anything to do with calibration for most devices. It just contains the stats for how much battery drain various things have caused, during this 'running on battery power' session. It's also reset every time the device is charged. Read here for more info.
Furthermore, even if this were not the case, I'd conclude that wiping the system partition (indeed, all partitions except recovery) would have cleared this data.
Still, that said, it's conceivable (though exceedingly unlikely) that some of these calibration apps might do something else, such as talk to the battery circuitry at a low level. Since I've got nothing to lose, I will probably give a few of them a shot. Do you happen to know which one it was that you tried?
siralsmooth said:
For me, I noticed a variance from what the OS was reporting and twrp was showing in between flashing.
Click to expand...
Click to collapse
In my case, the values seemed to track pretty closely, and with numerous freshly-flashed versions exhibiting the same issue, I'm pretty sure at this point it's not a software glitch. I've resigned myself to ordering a new battery. I just wish I was certain that it would fix the issue.
siralsmooth said:
For what its worth, I'm on the KitKat bootloader, and haven't used an official Samsung firmware since KitKat. Oddly enough, the battery calibration having been off survived through lollipop and into marshmallow. Hopefully you can get your tablet back on track.
Click to expand...
Click to collapse
My understanding is that the bootloader doesn't change with flashing. I might be wrong though; is there a way to check the version?
Just a heads up. I ordered a new battery, which arrived yesterday. It seems to have completely solved the issues I was having.
My guess is that Android itself monitors the battery more diligently, and takes a more conservative approach to preserving battery life by shutting down when the voltage drops too low, while recovery mode would just let it run down completely flat (not good for Li-ion cells).
It's a moot point now, because it all seems good.
So I've had this phone for about a year now, loved it (other than the lack of custom ROMS but that was my own fault for not doing enough research to begin with..) Anyways, to the problem..
The phone ran completely fine for about 6 months, no issues whatsoever. Then, I cracked the screen while working (oops). I consider myself at least a bit knowledgeable when it comes to phone repair, as I have done many in the past successfully. I purchased a new screen off E-bay, and installed it. No issues other than it had a few weird spots on the screen but it was bearable so I was living with it. About a month later I started having charge port issues. I had to prop it up certain ways to get it to charge, etc etc. I looked it up and apparently many people had this problem. It was running fine still for about another month until the strangest thing happened that I've never seen before.
The batter would immediately say 100% when I first plugged it in, and after powered on, it progressively brings itself down to 0% and then dies completely. Never seen it before and couldn't find anything about it on the internet really.
I figured that it was probably just the battery crapping out on me, so I thought, if I'm going to keep this phone (can't really afford a nicer phone right now), that I may as well purchase a new charge port and battery and repair them both.
The repair went flawlessly. The charge port works again perfectly but the battery problem still remains. It still says 100% and gradually goes down to 0% and dies.
What is going on here? Any ideas? I am now trying a system restore (my phone was encrypted so I wasnt able to get into TWRP without remembering the password which I don't even remember putting on there). I did a wipe on the phone and now I am able to access TWRP just fine on my internal storage, is there anything that may be able to fix this? Assuming this is a software issue and not a hardware one? And if it is a hardware one, what could it be??
Thank you for your time!
EDIT:
I forgot to mention. About a day before the battery started doing this. I downloaded the magisk module "ACC" (Advanced charging controller), thinking it may be useful considering how weird my charge port thing was being. It completely made my phone unable to charge when plugged in. I disabled and deleted the module and it went back to the way it was before (it didn't have the weird issue of discharging constantly). The next day or 2 that's when it started discharging immediately and always says its at 100% when I first plug it in. Don't know if that's relevent or not but I figured I would add it.