Droid Turbo 2 Shutting Off Randomly with Battery Life Left
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have seen other topics on this in this thread but no real answers. One thread only had an answer of "my replacement phone seems to be working." Well That is not a good enough answer. It seems this is plaguing a lot of T2 users.
My phone will randomly shut off anywhere from 30-15% battery life left. Sometimes it happens when opening or performing an action in an app, sometimes it's when I wake up the screen to use the phone. Sometimes it shuts down and I can reboot and it keeps going, other times it shuts down and blinks the drained battery image at me and will not reboot until I plug it in. When I plug it back in, it goes back to 20+% battery life immediately. I use 2 chargers, a wireless Qi charger at night, and the OEM turbo charger during the day. I used to be able to go a full day without charging, now I am lucky if I make it through lunch. The quick battery draining happened post the Marshmallow update, and eventually the Nougat update. The OS is definitely the biggest consumer of battery life.
I have tried with not change whatsoever:
Wiping the Cache Partition (many times)
Resetting the battery tables (many times)
Running in Safe Mode to Test 3rd Party apps (it's not the apps)
Factory Reset (same issue)
What is going on with the update and these Turbo 2's?? I'm now encountering issues with my SD card because I think an improper voltage is being delivered to the phone and the SD card won't read if it does not receive a steady voltage. So now I have no external memory in my phone.
I am currently running:
Android 7.0
System Version: 25.11.10.kinzie_verizon.verizon.en.US
Build #: NCK25.118-10
Configuration Version: I15.MOT.XT1585.0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am having the exact same problem.
Android 7.0
System Version 25.201.6.kinzie_verizon.verizon.en.US
Build #: NCKS25.118-10-6
Configuration Version: I15.MOT.XT1585.0
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Even with the latest update I received over the weekend, still shutting down for no reason. I am seeing that EVERYTIME an app needs to update, my phone shuts down. If this can't be fixed, I WILL BE BUYING a different phone from a different maker. Find this totally disappointing from Motorola.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm having the same issue after doing the latest security update (did the update two days ago). This is my 3rd Droid Turbo 2 phone. My original one got plagued with the vertical line down the screen so got a replacement. That replacement had a massive and noticeable burn in. So now I'm on my third phone and I'm dealing with the random reboot issue and I have to plug it into a charger to boot back up. It has happened to me twice in the last 8 hours, and I know the latest reboot I was using Snapchat and had 61% battery.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am having the same problem with 2 of the three T2 we have in our home. It's started shutting off at 20-25% and now they shut down at 65%. I have they find a solution soon.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
That isn't something that should be happening. I would recommend all users that have this issue to get a warranty replacement. There are 2 ways to get it free of charge. One is to use your one year warranty if you have purchased your device in the past year. If not, then use tje insurance for the line of you bought it for it. It seems like you have tried all troubleshooting steps, so a warranty replacement sees like tour best option. I hope you can get this fixed!
J.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I would guess that most of these Droids are out of factory warranty, and insurance replacement is not really a free of charge option. This seems like a major flaw with this phone model, when will the root cause be determined from all the returned phones? Will there be a recall that doesn't require an insurance deductible? (I'm assuming you are a Verizon representative based on your username.)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am actually not a Verizon rep, but I actually own a Droid turbo 2 myself. I would contact customer service and say that many phones are having this issue and demand a free replacement. That's all that can probably be done IF your phone is out of factory warranty. If any phone's we're bought under a year ago and having this issue, get a warranty replacement before the warranty runs out.
I don't have this issue but I can understand the possibility of this happening especially with reports with the same under previous iPhones.
J
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Unfortunately your only option is to keep going through replacement devices as long as your warranty will cover a manufacturers defect.
I bought this device a month after it launched. Within a year I had it replaced 4 times. I spoke with a Verizon representative using this sites chat now feature. They openly acknowledged that Verizon is aware of this manufacturers defect. They also then contacted Lenovo, who now owns Motorola, with me online seeing if they had any suggestions. They admitted to being aware of this defect as well but wanted me to send in my now 3rd replacement device so they could further investigate and fix it. I still have the transcript saved in my email.
The fact that Verizon still promotes a device that has a known and acknowledged critical defect like this is just wrong. If you have total device protection on the line just keep replacing it and filing claims until they have to give you a different device.
I personally just upgraded a month ago and will never again purchase a Motorola device for this very reason. I'd file a report with the BBB but it's just not worth the time and hastle at this point. Verizon isn't what they once were.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
FWIW, same issue here/same solutions tried, same end result. Verizon csr at the store offered a refurb/no solutions. Poor support all the way around.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mine has been doing this since the 6/9 security update. Had zero problems before hand. If I see that it dies at 15-20% I plug it in for a few (it reads 15-20%) and reboot it. When it comes back on after the reboot it says 3-4%. It's clearly not reporting the right battery life. It also isn't holding the charge/draining. I can go from 100 to 50 in 4 hours with it sitting in my purse with it set to DND.
The security update is what [Removed] up my phone.
inappropriate content removed as required by the Verizon Wireless Terms of Service
Message edited by Verizon Moderator
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am having the same problem too. Noticed it right after the update. Never had it prior to the update. It's ridiculous and so frustrating!!!!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Mine does it too...along with WiFi disconnects, Bluetooth turns itself off when phone is restarted, Bluetooth disconnects while listening to music or during phone calls.
All and all since the upgrade this phone is JUNK! I've already replaced it once and same issues...whoever QA'd Nougat for this phone should be fired!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Funny...I can't edit my post...
DionM_VZW is ANYTHING in the works to get these phones where they are reliable again? I have 3 of these devices and am ready just to pay everything off and leave VZW because of these issues and the lack of support received. All of these issues started with Nougat...wish I had NEVER upgraded and there's no way back!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
There is a five minute edit window for posts on this community.
I'm most definitely NOT a VZW employee. If a post answered your question, please mark it as the answer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am also having the same issue, contacted Verizon and they will not cover it under the extended warranty because the phone is not physically broken. Called Motorola and they want me to purchase another phone, the phone started having a problem after the last software update, the phone at that time was out of warranty by 2 months. The question we need to ask is why is the consumer responsible for out of pocket expense when the manufacture (Motorola) and the cell phone provider (Verizon) had a part in the software update. The tech support agreed with me that the software and the phone are not compatible or that a specific number of phones built are having a problem with the last software update. I suggest that those of us having this issue ban together and start a class action suit and hold Verizon and Motorola responsible for this issue. I suggest everybody having this issue call Motorola and Verizon and voice your concerns.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've been having the same issue, over and over again |
chat transcription removed as required by the Verizon Wireless Terms of Service
Message edited by Verizon Moderator
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I was also told this morning that the most recent Security update should have fixed this problem. It obviously has not. Thanks Verizon.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Basically what I was informed of is that can use my warranty replacement or pay in full the amount due for the Droid Turbo 2. I'm not willing to pay for a known DEFECTIVE device. I told the SR that I would not take a Droid Mini as it would be a downgrade and I would in turn still be responsible for paying off a Droid Turbo 2 that's not able to power on. I also told the SR that I would not pay for overnight shipping as it implicitly the responsibility of Verizon Wireless that they will take care of their customers for a manufacturers defect. A customer is not responsible for the speedy delivery of a product. I sincerely hope this does not violate terms.....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have the same issue now since the last update. Fix it Verizon. Too much competition out there to let your long time customers flail in the wind with an unreliable product. We'll talk soon.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've been having the same issue. I noticed occasionally I would pull my phone out of my purse or pocket and it would be off and wouldn't turn on. I thought maybe it had had low battery without me noticing, but when I would put it back on the charger it would start up with about 20%.
This week it took a dive off the deep end. Sudden shut offs at around 80-90% battery. Wouldn't turn on unless charging for the first two days, now I've had it sitting on the charger for an hour and hasn't rebooted still... All completely random. Sometimes shuts off when using an app (google search, camera, other various apps), sometimes I just barely have swiped the screen to wake it up and it dies.
Verizon and Motorola need to fix this!
