Related
I have done a reasonable amount of searching on this and have not found anything specific to my problem so figured I should post a question.
I have an issue with my Dimaond when it gets hot generally either using Wifi or Phone Data connection that the screen goes out. Basically everything goes to the left side of the phone so if you hit the Task Icon in the top right corner you get the Start Menu. Phone is basically useless at this point and you have to wait for it to cool down. Has happened since day one and is generally worse when using it when charging. I was watching Utube on it the other night 5min video while on AC charge and it went out. I am running Dutty 2.5 Rom and 25.07 radio have tryed 25.08 and 25.05 no difference was happening when the phone had orginal HTC ROM as well. Also will happen on a long call if the screen is on.
Basically feel issue is hardware related and maybe faulty screen still under warrenty so wanted to know peoples opinion on weather I should send back. Problem is will take a couple of weeks and I don't really wnat to wait that long if I can help it. Also assume it would be best to flash standard ROM back, should I do anything with HARDSPL eg should this be changed back as well if I send it back.
And before anyone says it I have tryed searching this topic and have found lots about HOT dimaonds but nothing related to screen going out at the same time :-(
Thanks
I had this issue in my JasJam (Hermes) whre the screen would simply go white after a while of use and I would have to leave it for a while for it to work again.
Unfortunately it sa hardware issue and you should claim a warranty repair on it
I can't see how this could be a software problem so I figured it must be the screen eg hardware related. Would be nice to know if anyone has had the same issue with a dimaond... Seems we may be spending some time apart, just hope it doesn't take long to fix..
I've had the same issue
http://forum.xda-developers.com/showthread.php?t=428976
My first device had been replaced recently (i.e. today) by my network provider (o2) and the new device seems to work without any problems now even if it's "hot".
(i.e. default screen adjustment + creating heat by activating the phone, wlan, bt + recharging it)
I sent an email to HTC regarding the fault and they said it would have to go back for a warrenty repair. I brought it through a resellar so has to go back to HK from NZ so will be away three weeks uurggghhh... Just seems odd I don't have any physical damage on the screen but hte problem has been around since day one as I remember having the problem the first day I got it. Juyst seems to be getting worse and is easily reproduced by usiung utube over wifi gets hot and it is all over. Just wondering if I should put an offical ROM from HTC back on the device before I send it back as I currenty am running Dutty ROM, what do you think....
i put the original rom back on and they still found out the the rom had been flashed, and would not repair on warranty
yep, i also asked about this problem
http://forum.xda-developers.com/showthread.php?t=438733
there are some youtube video's of how the phone behaves
my phone seems to do it less frequently since stopping using panosha's rom
im using alpha zero 7 at the moment..
i've also noticed that it isnt necessarily a heat issue, my phone does it completely at random
yesterday i found though, that when the phone did the alignment issue, i gave it a good shake.. and hey.. its all aligned again?!
maybe it was just a fluke, it hasnt freaked out since..
holding thumbs
Hey,
I also have the same screen problem, but my Alignment goes to right.
If I press on the left side, a press on the right side is recognized.
Good to know that Im not the only one with this problem.
greets doena
I got my phone back a week ago replaced the screen has been away for over two months, complete disaster, anyway all sorted now and I have not had the problem since....
I had this exact same issue (out of the box).
It was a hardware fault and I exchanged it for another one.
Haven't had any problems since.
Minus-1 said:
I had this exact same issue (out of the box).
It was a hardware fault and I exchanged it for another one.
Haven't had any problems since.
Click to expand...
Click to collapse
Hardware's fault ? Most likely not. I will give u an example of why I think it was software related. My device ran hot as well but I simply switched roms and now it's the complete opposite. Your most recent device most likely come with a different Rom in the phone.
I am facing the problem recently last 2 3 days
my Xperia restarts automatically
sometimes there is 30% to 40% charging left still its shut automatically and never been start.. i have to change new battery
any solution for this or anyway to find the problem?
regards
anybudy would like to answer this please?
I'm having a similar problem...my x1 sometimes shuts down while in the middle of doing something, like opening apps, sliding out the keyboard or even navigating touchflo. I suspect it could be a battery problem, as someone in the forum discovered, having also shut down problems, that his battery is loose and the connectors are not properly met so he stuck a bit of hard paper to fix it, but I checked mine and the battery is not loose. I don't want to spend on a new battery if these shut downs weren't really cause by faulty batteries, so yeah anyone has a clearer understanding on this?
Hi all
I am also having a similar problem the past 2 days and as of now i cant use the qwerty keyboard because just as i begin to slide the qwerty out the screen goes black and the phone need to be rebooted.
I have just changed to Valkyrie 2.4 yesterday thinking that maybe its was software problem with Touch X but the problem still persists. Only difference is that with Touch X the phone would reboot itself.
Anyone else having any similar issues and what would the fix be, or shall i be off to my nearest service provider for repairs?
Thanks
Uhm.. about that problem when you slide it out and the device turns off.. i had that too and i send it in to repair.. it will probably be fixed under warranty, and stock rom or custom rom doesnt matter the problem was still there... and it happend to me 5 days ago..
knufh said:
I'm having a similar problem...my x1 sometimes shuts down while in the middle of doing something, like opening apps, sliding out the keyboard or even navigating touchflo. I suspect it could be a battery problem, as someone in the forum discovered, having also shut down problems, that his battery is loose and the connectors are not properly met so he stuck a bit of hard paper to fix it, but I checked mine and the battery is not loose. I don't want to spend on a new battery if these shut downs weren't really cause by faulty batteries, so yeah anyone has a clearer understanding on this?
Click to expand...
Click to collapse
'When i slide the thing out it sometimes restarts'
I used to have that with the stock ROM so this all might be more software related...
yeah I am having the same problem, No Water Damage btw. i found that if i sometimes in portrait mode if pressure is applied to the top right region, it will shutdown and/or restart. When I slide my screen up to landscape mode it screen is just black. I'm going to contact Sony Ericsson to see what they have to say about this.
SyntheticDistortion said:
'When i slide the thing out it sometimes restarts'
I used to have that with the stock ROM so this all might be more software related...
Click to expand...
Click to collapse
It resets when the phone freezes. Sometimes it freezes so bad you have to manual reset.
My phone is doing the same thing but when i slide it up. The screen goes blank and then it restarts by itself. I never flashed my phone so I thought it was a firmware issue. I finally updated to the R3A firmware and lo and behold the same results, but instead it didn't restart, it just turned off or the screen goes blank. I've sent the phone to Sony Ericsson and they told me that I would have my phone back in 7 to 10 business days, but they're liars!!! It's been 13 business days and counting and no word as to whether the phone can be fixed or updates on status other than it's in "work in process". So then I called again today and complained to SE and the result is that they are "awaiting parts and Xperia parts are on back-order". After further probing SE told me that they would call me on Monday to officially let me know what the hell is going and why it's taking so long to repair my phone. I paid $800 usd for the phone and I would expect that their repair service would be a lot better and quicker than what it is! During my wait time for my phone, my PS3 broke down, I sent it in, got it fixed and returned already. That was within a week. There is definitely something wrong I tell you! They just need to send me a new phone!
Sorry about my rant guys, but I'm pissed!!!
My damn phone has the same issue, Until now, this hasn't been repaired for it's crack. And I'm almost out of warranty days, I think I bought it 2md day after the xperia was released. I'll try testing abou the presuure point though. I give you update
I did have the same problem..
Hi... I did have the same problem n I couldn't find any solution... So i send it to repair...
U can check my threads..
http://forum.xda-developers.com/showthread.php?t=520143
n
http://forum.xda-developers.com/showthread.php?t=519322
mca
EDIT : It seems that is an XPERIA PROBLEM!!!! LOOK!!! : http://forum.xda-developers.com/showthread.php?t=550242 !!!!! , many people is having the SAME problem...
I'm disappointed..
About 2 months ago I was drunk and fell down with my phone in my pocket. I cracked the screen and that seemed to be the only damage. Touch screen still worked fine.
I had just gotten layed off about 2 weeks before so I didn't want to pay the copay/deductible whatever you wanna call it to get it replaced for just cosmetic damage.
Well not too long afterwards I realized my phone wouldn't mount via usb and I had an odd issue of when I slid the keyboard open while with an active text entry box the leeter 'x' would appear.
I upgraded my rom and both issues ended up disappearing (although they didn't appear with the same rom for weeks until the incident). Well now with cyanogens latest rom the problem with the x appearing is back. No one has mentioned in any of the cyanogen threads the same problem.
So basically, without trying to clutter his thread, has anyone else had similar problems? To me it seems like it is just time to pay for drinking too much and get it replaced, but if its a certain problem that happens randomly I can still deal with just some cosmetic damage.
I had the problem running cm 4.2.1 and now with 4.4 it seems to not have the issue anymore. This is just messing with my mind, I can't tell if it is a hardware issue or rom specific for me. No one seems to have the problem but it comes and goes with the builds I use.
Hey guys,
Does anybody who ever or being suffered from the call issue like hearing nothing from the receiver during phone calls??Sometimes it work,but sometimes it doesn't!!And the speaker works in most of the cases,whereas sometimes it also breaks down liked the receiver.Moreover,I can hear some cracks from the receiver in some cases.
I am totally freaked out because I am sure that the receiver is good (no problems with skype and wechat,and I also have checked it by using "*#0*#" when the situation happens) and it seems impossible to be solved after wiping and flashing different firmware(both by cwm and odin),and so do the modems.
Any solutions or suggestions will be totally appreciated!!!:crying:
Edit: I've tried to flash the Perseus and disable the dac direct,it seems that the cases happen less frequent.
Update:
I found sth strange about the call issue by chance: when I lock the screen maybe for more than 5 mins,then wake it up and make a phone call soon,the receiver can't work every times.However, when I put it into use(light the screen) for more than 3 or 4 mins,and then the receiver works again during calls.
What I want to say is: maybe there are sth wrong with the cpu setting or the power management?
I actually got the static phone call issue today (first time) after installing ripper rom yesterday but im sure it was just a once off issue because I could not reproduce the same result
Change roms ect but if the issue persists then your only option is to jump on triangleaway, stock firmware and dial away to Samsung or your telco
Sent from my GT-I9305 using xda premium
takooo said:
Hey guys,
Does anybody who ever or being suffered from the call issue like hearing nothing from the receiver during phone calls??Sometimes it work,but sometimes it doesn't!!And the speaker works in most of the cases,whereas sometimes it also breaks down liked the receiver.Moreover,I can hear some cracks from the receiver in some cases.
I am totally freaked out because I am sure that the receiver is good (no problems with skype and wechat,and I also have checked it by using "*#0*#" when the situation happens) and it seems impossible to be solved after wiping and flashing different framekworks(both by cwm and odin),and so do the modems.
Any solutions or suggestions will be totally appreciated!!!:crying:
Edit: I've tried to flash the Perseus and disable the dac direct,it seems that the cases happen less frequent.
Click to expand...
Click to collapse
It's a hardware issue. I had the same thing with my i9300; You have to take it to a repair center for motherboard replacement. It's the audio chip that goes bad (on the i9300 the component number is U604). Happened to me twice, with both my new and replacement motherboard, but it happened to go away for me the 2nd time.
Product F(RED) said:
It's a hardware issue. I had the same thing with my i9300; You have to take it to a repair center for motherboard replacement. It's the audio chip that goes bad (on the i9300 the component number is U604). Happened to me twice, with both my new and replacement motherboard, but it happened to go away for me the 2nd time.
Click to expand...
Click to collapse
Thanks!! I've saw your thread and now I have nothing to do with it except considering repair.If the issue happens again,i will probably send it back to the company which I bought this phone.
BTW,are you sure both your phones are now preforming good during the calls?You have said that the issue happened again a month later after it got the first repaired? If you have some news with your phones,please notice me~~~
Magik_Breezy said:
I actually got the static phone call issue today (first time) after installing ripper rom yesterday but im sure it was just a once off issue because I could not reproduce the same result
Change roms ect but if the issue persists then your only option is to jump on triangleaway, stock firmware and dial away to Samsung or your telco
Sent from my GT-I9305 using xda premium
Click to expand...
Click to collapse
Yep!! Last time I had flashed the ripper rom and then I found this issue.First I thought it was the problems that come from the rom,but after several tries then I thought it probably due to the hardware issue that I cant solve....
Anyway,thanks for your suggestions!!
takooo said:
Thanks!! I've saw your thread and now I have nothing to do with it except considering repair.If the issue happens again,i will probably send it back to the company which I bought this phone.
BTW,are you sure both your phones are now preforming good during the calls?You have said that the issue happened again a month later after it got the first repaired? If you have some news with your phones,please notice me~~~
Click to expand...
Click to collapse
I've had the phone for about 6 months total. The first time the issue happened, I had owned the phone for 3 months. The phone came from a company in Germany, and I live in the US (purchased through Amazon). The i9300 is not sold or repaired in the US (because the US version has different components), so I had to ship it to the seller, to ship to a repair center on my behalf. The phone itself carries a 2 year warranty, which is good because in the US phones only have a 1 year warranty. However, it cost me $80 to ship the device to Germany, and about a month total time before I got it back.
Anyways, I got a paper back in German that detailed the issue and said they had to replace a component, which turned out to be the entire board. They also copied over the original IMEI number to the new board. The second time this issue started happening was literally on New Year's Day (on 12:00 AM EXACTLY). I tried to call a car service place for my girlfriend and her family, and my phone had no audio going in or out for calls. My phone was working perfectly before that and I hadn't flashed anything new for over a month (I was on Omega ROM 35 with Siyah kernel 1.8.6). Immediately I knew the issue had come back again. For whatever reason, the issue went away maybe 4 days later and hasn't come back. I flashed the latest modem (for the i9300 it's XXELLA), but I'm still on Omega ROM v36. I don't think me flashing anything fixed anything; more likely that it went away on its own since it's 100% a hardware issue.
To clarify, sometimes an incorrect modem for your region CAN cause there to be issues with calls, but if it happens out of the blue, and flashing anything doesn't help, it's a hardware issue. Take it to a Samsung repair center for sure. The i9300 and i9305 use the same parts except for the modem and a few other things. Other than that they're the same exact device.
Product F(RED) said:
I've had the phone for about 6 months total. The first time the issue happened, I had owned the phone for 3 months. The phone came from a company in Germany, and I live in the US (purchased through Amazon). The i9300 is not sold or repaired in the US (because the US version has different components), so I had to ship it to the seller, to ship to a repair center on my behalf. The phone itself carries a 2 year warranty, which is good because in the US phones only have a 1 year warranty. However, it cost me $80 to ship the device to Germany, and about a month total time before I got it back.
Anyways, I got a paper back in German that detailed the issue and said they had to replace a component, which turned out to be the entire board. They also copied over the original IMEI number to the new board. The second time this issue started happening was literally on New Year's Day (on 12:00 AM EXACTLY). I tried to call a car service place for my girlfriend and her family, and my phone had no audio going in or out for calls. My phone was working perfectly before that and I hadn't flashed anything new for over a month (I was on Omega ROM 35 with Siyah kernel 1.8.6). Immediately I knew the issue had come back again. For whatever reason, the issue went away maybe 4 days later and hasn't come back. I flashed the latest modem (for the i9300 it's XXELLA), but I'm still on Omega ROM v36. I don't think me flashing anything fixed anything; more likely that it went away on its own since it's 100% a hardware issue.
To clarify, sometimes an incorrect modem for your region CAN cause there to be issues with calls, but if it happens out of the blue, and flashing anything doesn't help, it's a hardware issue. Take it to a Samsung repair center for sure. The i9300 and i9305 use the same parts except for the modem and a few other things. Other than that they're the same exact device.
Click to expand...
Click to collapse
Ok,thanks a lot for telling me these!!! I've sent a email to the customer service and hope to get respond soon.Anything news i will update it.
Had my Nexus 6 for 4 months now - originally had it on stock for a couple of months, it would constantly power off, usually when battery was less than 20% or when trying to access the stock camera or random apps.
So to try and resolve the issue I rooted the device and have now tried practically every ROM available and still have the same problem
Currently running SaberMod 5.1 with Vindicator kernel and the problem still happens.
Tried PA, CM12, PAC, Vanir, Chroma, Euphoria, LiquidSmooth, Terminus....you name it I've tried it.
Will probably be returning it to supplier but before I do would like to know if anyone has had similar issues - is this because of a bad batch of Nexus 6 phones? I guess it's hardware/battery related - but wondered if any software fixes were available?
I have started to face the same problem, mine shuts off usually below 10% but it's only a month old, so disappointed with nexus 6,not only was it effing expensive, it's not the premium device that Google boasted about with so many bugs, which include the speaker crackles and random shutdowns
Totally agree, why pay for a premium device to be plagued with problems?
I was going to try and find if there was a fix but might just return the device.
Really disappointed I expected a lot better for such a high end device.
FWIW, I've had the 6 since November 26th and don't have any issues. I'm sorry you've had issues but that doesn't mean the whole lot is bad. RMA and get a new one. There are issues with every device after it's launched, go to any forum and you'll see what I mean. You can't label the whole line defective just because of a few isolated problems.
I wasn't suggested all Nexus 6 devices were faulty, I was querying whether or not there is a faulty batch, as this is definitely an issue and seems others are havin g it too.
Seems as if the battery dies at certain times and when using apps such as the camera.
Will definitely be returning it now
thx1971 said:
I wasn't suggested all Nexus 6 devices were faulty, I was querying whether or not there is a faulty batch, as this is definitely an issue and seems others are havin g it too.
Seems as if the battery dies at certain times and when using apps such as the camera.
Will definitely be returning it now
Click to expand...
Click to collapse
I had the same problem as well (especially when I used the camera), and I believe that there was a batch of phones made in December and early January that had a bad batch of batteries. I am only speculating this because when I called into Motorola support, they asked me when I bought my phone (I bought it at the end of December and received it the first week of January), and then they asked me if I had a bulging back issue as well. If you search around this forum and other places on the internet, quite a few people who bought the N6 in December had issues relating to power or the physical battery in one way or another.
Motorola and Google acknowledge that there is an issue with the batteries in some of the Nexus 6 phones, and when I sent my device back to Motorola, they sent me a replacement device without issue once they looked the phone over.
Diocat said:
I had the same problem as well (especially when I used the camera), and I believe that there was a batch of phones made in December and early January that had a bad batch of batteries. I am only speculating this because when I called into Motorola support, they asked me when I bought my phone (I bought it at the end of December and received it the first week of January), and then they asked me if I had a bulging back issue as well. If you search around this forum and other places on the internet, quite a few people who bought the N6 in December had issues relating to power or the physical battery in one way or another.
Motorola and Google acknowledge that there is an issue with the batteries in some of the Nexus 6 phones, and when I sent my device back to Motorola, they sent me a replacement device without issue once they looked the phone over.
Click to expand...
Click to collapse
Thanks for getting back to me with this - I guessed there was an issue but didn't want to return the phone unless I was totally sure, so thank you again for clarifying this.
I am not happy to be returning it but looks like this is my only option.
I have the very same problem with my N6 bought in December 2014. Have tried factory reset multiple times without luck. I just gave it for service. The guy there said they would try reflashing the firmware and if that doesn't work I'll be given a replacement. I'm from India btw.
I'm having a similar problem.. I could have 100% charge, take a picture and the phone will shut off and tell me it's dead when trying to turn it back on. After waiting about 2 minutes, it will attempt to boot. It goes through the whole "Optimizing apps 1/xxx" thing, then goes to "Finishing boot" and shuts off again, and repeat. The phone will not fully boot until it's plugged in. Also the phone is acting sluggish. This started on Euphoria ROM, but I since have flashed stock 5.0.1 and locked the bootloader, then accepted the OTA to 5.1. The issue still persists with stock, and factory resetting a few times after the fact.
I also noticed the back cover is lifting away from the frame of the phone, so the battery is probably swelling.
On a bright note, I've contacted Motorola and described this issue, plus a couple of more I'm experiencing (burn-in, odd sounds when the phone vibrates) and I'm now waiting on my replacement phone with no questions asked.
Here's a screenshot of the battery issue (36 minutes of Screen-on time)
drkboze said:
I'm having a similar problem.. I could have 100% charge, take a picture and the phone will shut off and tell me it's dead when trying to turn it back on. After waiting about 2 minutes, it will attempt to boot. It goes through the whole "Optimizing apps 1/xxx" thing, then goes to "Finishing boot" and shuts off again, and repeat. The phone will not fully boot until it's plugged in. Also the phone is acting sluggish. This started on Euphoria ROM, but I since have flashed stock 5.0.1 and locked the bootloader, then accepted the OTA to 5.1. The issue still persists with stock, and factory resetting a few times after the fact.
I also noticed the back cover is lifting away from the frame of the phone, so the battery is probably swelling.
On a bright note, I've contacted Motorola and described this issue, plus a couple of more I'm experiencing (burn-in, odd sounds when the phone vibrates) and I'm now waiting on my replacement phone with no questions asked.
Here's a screenshot of the battery issue (36 minutes of Screen-on time)
Click to expand...
Click to collapse
Almost exactly what happened to mine: http://forum.xda-developers.com/nexus-6/help/refused-repair-moto-uk-device-rooted-t3077271/page2
TL;DR:
Dear xxx,
Thank you for contacting Motorola.
I have now heard back regarding your Nexus 6 unit. After carrying out the initial repair the engineers at our repair centre then discovered a more serious fault with the battery on the phone as it started to swell during their testing.
Click to expand...
Click to collapse
So if your phone is randomly shutting down when their is plenty of battery, and/or does the optimising 0/xxx apps at start up - get ready to RMA because you don't want a swelling battery and a possible explosion/fire...
I've submitted the device to their service centre and awaiting replacement.
Sent from my iPhone using Tapatalk
My device has been returned and will be replaced, no questions asked, as it is a recognised faulty phone.
So to re-iterate, all I was wanting to clarify was if there was a bad batch of Nexus 6 phones and whether or not mine could be one of them - and it looks like that seems to be the case.
I wasn't in any way saying the whole line of phones are bad but it's good to clarify that there is a bad batch out there and the suppliers are willing to replace them
Same exact symptoms
100% charged phone. Start doing something...anything...and it just blanks off. No warning. On startup, it does the app optimization, all the wifi passwords are reset, and unless it is plugged in, it will probably restart before optimization completes.
I had the google nexus case with stand, and didn't notice anything, but after removing the case, the base is noticeably bulging in the center but not at the top and bottom.
For $800, my even with a repaired phone which I hope rectifies the issue, my expectations are higher for a flagship google phone that I paid full price for. This is indeed either a design or manufacturing defect of the piece part or he assembly if it has to do with the charging process...IMO
rocket808 said:
100% charged phone. Start doing something...anything...and it just blanks off. No warning. On startup, it does the app optimization, all the wifi passwords are reset, and unless it is plugged in, it will probably restart before optimization completes.
I had the google nexus case with stand, and didn't notice anything, but after removing the case, the base is noticeably bulging in the center but not at the top and bottom.
For $800, my even with a repaired phone which I hope rectifies the issue, my expectations are higher for a flagship google phone that I paid full price for. This is indeed either a design or manufacturing defect of the piece part or he assembly if it has to do with the charging process...IMO
Click to expand...
Click to collapse
Yes on all points there. The random turn off when doing anything, app optimisation (very long) wifi passwords gone (very annoying) and restart again while optimising. And the resultant swelling battery..
It seems very few of us have experienced this, thankfully, but very worrying, I certainly wouldn't get another moto device after this.
Sounds like the very common battery calibration problem, which can be reset by following a set of instructions in the bootloader. Look around for them.
Bumping this as I think I've found the root cause of this problem. Are you guys using Google Fit? The replacement that I got was working fine till two days ago when I initialized/started using Google Fit. Device turned off twice. Then I disabled the app and the shutdown hasn't happened till now. If you guys are using Google Fit, try disabling the app and monitor it for a couple of days.
Well I managed to get a replacement phone from GiffGaff and guess what - same issue again!
Battery overheats, crashes on Camera App, resets WiFi, random app crashes
Have tried several ROMS including Android M to see if there is an improvement but unfortunately not - will try disabling Google Fit now and see if that helps but so far I'm really disappointed.
This device is supposed to be top of the range flagship Google model but for me it is a resounding fail.
I have got the same problem , but i cracked the top of my screen when i had the phone after a month , when i called Motorola they said they could take to repair but would cost £120 to fix screen as they cant send back with screen damage. Really frustrating as i know the screen isn't the fault. Anyone got any ideas ?
I know this is an old thread but I've had my nexus for quite a while and it just started doing this when I flashed a 7.1.2 rom. Went back to complete stock and still have the issue. I noticed on the 7.1.2 roms that the battery wouldn't read correctly on the indicator and now back on stock it reads correctly but still crashes. I think the battery may be dying or be damaged after almost 2 years.
goinovr said:
I know this is an old thread but I've had my nexus for quite a while and it just started doing this when I flashed a 7.1.2 rom. Went back to complete stock and still have the issue. I noticed on the 7.1.2 roms that the battery wouldn't read correctly on the indicator and now back on stock it reads correctly but still crashes. I think the battery may be dying or be damaged after almost 2 years.
Click to expand...
Click to collapse
Boot into fastboot, find bootloader logs and hold power for ~10seconds (till it resets by itself), best done on full battery, may help, if not you can try to calibrate the battery (requires root tho). If all this fails only thing left is to change the battery. Takes about 20mins and costs like 20-25usd (easy to do by yourself