FORUMS
Remove All Ads from XDA

Nexus 4 turning off when unplugged from charger

224 posts
Thanks Meter: 15
 
Post Reply Email Thread
Hey guys, i have been owning this piece of great phone for almost two years. But it never gave me a big issue.
Nevertheless, few months back i flashed cm12 and it worked great too.. I had been using it gracefully till i decided to update to cm12.1. So i decided to update, but the update always crashed google play services. The update did not happen automatically so i had to flash the zip through custom recovery (already installed) by myself.

I could not come out of that so i went ahead and did a full wipe and flashed cm12.1 along with gapps. Since then when i am unplugged it goes only to about few minutes (on battery) and shuts down. So, i now decided that this piece of update is buggy and did a full wipe and reflashed the original cm12 zip and gapps which i had placed in the first place. But, to my horror even this time it could not go past the bootscreen even and turns itself off when its about to start up. (Battery is full charged, did an overnight charge as well).One very unusual thing i noticed that almost all the the time i try to power it on it showed me "optimising app X of Y" which is weird. This kinda happens only on first boot.

But if i keep my phone plugged in to ac charge then it works fine.. but only last night it hanged and turned off even on charge. So there i decided that the cm thing is not for me. So i followed this tutorial and flashed the stock 5.1.1 rom (did a full wipe, tried oem lock and re unlocked and proceeded too).

But, i find the same problem same issue!! When unplugged my device, it just turns off even on full battery charge.

Can someone explain me the technical parts of the issue and what has gone wrong and how it can be fixed?

Please, Thanks

EDIT

Last time i locked - unlocked bootloader and proceeded with a fresh factory image flash, the device turned off on boot even when plugged in to my mac and it's hot on the back side
 
 
11th June 2015, 03:32 AM |#2  
Planterz's Avatar
Senior Member
Flag Tucson, AZ
Thanks Meter: 837
 
More
Sounds to me like there''s something physically wrong with the phone, probably the battery. Time for a new one anyway. Lithium batteries degrade with use. After ~500 charge cycles it'll have lost upwards of 20% of its original capacity and might show other signs of wearing out like inconsistent voltages. After 2 years of use, you'll be well beyond 500 cycles. A new battery off eBay is pretty cheap, and some sellers include the needed tools.Go to ifixit.com for a tear-down guide. A hair drier can help soften up the adhesive. The fact that it turned off despite being plugged in to your computer also points to the battery being toast - the USB amperage from a computer is less than the typical wall charger.

If it's not the battery giving you woes, I don't know what it could be.

And FYI, the whole "optimizing app" thing is the OS rebuilding the cache. When you flash your GAPPs package or a zipped Titanium backup it has to build the cache for the new apps. Same as when you do the "wipe Dalvik and cache" part of standard flashing procedure to avoid conflicts. In order for apps to load quickly, Android stores a lot of the necessary data in cache, so when you clear it or have new apps, it has to rebuild the cache. On Lollipop this takes a loooooooong time because of the way ART works.
11th June 2015, 06:38 AM |#3  
Nezam's Avatar
OP Senior Member
Thanks Meter: 15
 
More
Quote:
Originally Posted by Planterz

The fact that it turned off despite being plugged in to your computer also points to the battery being toast - the USB amperage from a computer is less than the typical wall charger.

If it's not the battery giving you woes, I don't know what it could be.

How can i be completely sure that it's the battery which needs to be replaced? The battery shows charge. When i plug in and boot up it shows enough battery power left.

Currently, without external power it does not go past the google screen on boot. When i plug in power while device is off, the battery meter shows just a little depletion from full charge. When turned on, battery level is 82 %

After all , all this hardware mess up can be the consequence of a bad cm flash ?

Quote:

the whole "optimizing app" thing is the OS rebuilding the cache.

I know this. Earlier it was happening on each boot. Now it seemed to be stopped.
13th June 2015, 12:17 AM |#4  
Member
Flag Root City
Thanks Meter: 27
 
More
By any chance did you have your phone charging while flashing and booting up your ROM?
13th June 2015, 12:21 AM |#5  
Nezam's Avatar
OP Senior Member
Thanks Meter: 15
 
More
Quote:
Originally Posted by ChainFires Son

By any chance did you have your phone charging while flashing and booting up your ROM?


May be? But not the the first time
3rd September 2015, 04:19 PM |#6  
Senior Member
Thanks Meter: 111
 
More
Quote:
Originally Posted by Nezam

Hey guys, i have been owning this piece of great phone for almost two years. But it never gave me a big issue.
Nevertheless, few months back i flashed cm12 and it worked great too.. I had been using it gracefully till i decided to update to cm12.1. So i decided to update, but the update always crashed google play services. The update did not happen automatically so i had to flash the zip through custom recovery (already installed) by myself.

I could not come out of that so i went ahead and did a full wipe and flashed cm12.1 along with gapps. Since then when i am unplugged it goes only to about few minutes (on battery) and shuts down. So, i now decided that this piece of update is buggy and did a full wipe and reflashed the original cm12 zip and gapps which i had placed in the first place. But, to my horror even this time it could not go past the bootscreen even and turns itself off when its about to start up. (Battery is full charged, did an overnight charge as well).One very unusual thing i noticed that almost all the the time i try to power it on it showed me "optimising app X of Y" which is weird. This kinda happens only on first boot.

But if i keep my phone plugged in to ac charge then it works fine.. but only last night it hanged and turned off even on charge. So there i decided that the cm thing is not for me. So i followed this tutorial and flashed the stock 5.1.1 rom (did a full wipe, tried oem lock and re unlocked and proceeded too).

But, i find the same problem same issue!! When unplugged my device, it just turns off even on full battery charge.

Can someone explain me the technical parts of the issue and what has gone wrong and how it can be fixed?

Please, Thanks

EDIT

Last time i locked - unlocked bootloader and proceeded with a fresh factory image flash, the device turned off on boot even when plugged in to my mac and it's hot on the back side

Exactly same problem is started with my Nexus 4 ... I really wonder, what is causing this. Meanwhile, have it sorted for you ? is that hardware (Battery) issue?
5th September 2015, 07:20 PM |#7  
Junior Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by Nezam

Hey guys, i have been owning this piece of great phone for almost two years. But it never gave me a big issue.
Nevertheless, few months back i flashed cm12 and it worked great too.. I had been using it gracefully till i decided to update to cm12.1. So i decided to update, but the update always crashed google play services. The update did not happen automatically so i had to flash the zip through custom recovery (already installed) by myself...

I too am facing kinda similar problem.
It first started on my stock Lollipop 5.1.1. I had kept it on charge and when I removed it, it got switched off. Thinking that it might be just another of the multitude of bugs in Lollipop, since I already had lots of problems with it, I decided to flash CM 12.1 Stable on it.

Unlocked bootloader, flashed TWRP recovery, created a backup (using TWRP), wiped data, cache, dalvik and started installing CM 12.1. Now comes the problem, I selected 'restart system' and it did restart and CyanogenMod logo was displayed for few minutes before the phone crashed. I switched it on again normally and the Google logo got displayed, and then again phone got off just after the Google logo. I tried flashing again by same procedure, but this time not even the Cyanogen logo was displayed. The Google logo got displayed and the went off.

Then I decided to restore the backup. Restored it but it still had the same problem at the startup Google logo.

Now I have managed to install CM 12.1, which works fine unless I don't open certain apps. When I open certain apps like Phone or Clock (those are some I have tried yet), it crashes the system.

This maybe a hardware or software problem, but pretty sure it isn't battery problem, coz it retains good charge when I switch it back on after crash.
5th September 2015, 08:57 PM |#8  
elonus's Avatar
Senior Member
Flag Oslo
Thanks Meter: 117
 
More
Quote:
Originally Posted by shazR00t

I too am facing kinda similar problem.
It first started on my stock Lollipop 5.1.1. I had kept it on charge and when I removed it, it got switched off. Thinking that it might be just another of the multitude of bugs in Lollipop, since I already had lots of problems with it, I decided to flash CM 12.1 Stable on it.

Unlocked bootloader, flashed TWRP recovery, created a backup (using TWRP), wiped data, cache, dalvik and started installing CM 12.1. Now comes the problem, I selected 'restart system' and it did restart and CyanogenMod logo was displayed for few minutes before the phone crashed. I switched it on again normally and the Google logo got displayed, and then again phone got off just after the Google logo. I tried flashing again by same procedure, but this time not even the Cyanogen logo was displayed. The Google logo got displayed and the went off.

Then I decided to restore the backup. Restored it but it still had the same problem at the startup Google logo.

Now I have managed to install CM 12.1, which works fine unless I don't open certain apps. When I open certain apps like Phone or Clock (those are some I have tried yet), it crashes the system.

This maybe a hardware or software problem, but pretty sure it isn't battery problem, coz it retains good charge when I switch it back on after crash.

Since you already unlocked the bootloader, and therefore already wiped everything, you could try flashing a factory image.
6th September 2015, 08:00 AM |#9  
Junior Member
Thanks Meter: 0
 
More
I also got the same problem. I thought this is battery problem, so I replaced the battery but problem still there. I thought this is problem of lollipop, never installed CM or anything. It is always running stock android. After that I even downgrade to Kitkat stock version still it is not working. One more thing I noticed is If I don't unlock the device than it will be powered on, but as soon as I unlock it and if it is not plugged in to charger it will be switched off. Any suggestion what should I do?
6th September 2015, 11:19 AM |#10  
Member
Thanks Meter: 12
 
More
I have the same thing for several month now.
Always thought it is the dying battery.
6th September 2015, 12:57 PM |#11  
Junior Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by theminikiller

Since you already unlocked the bootloader, and therefore already wiped everything, you could try flashing a factory image.

Just tried flashing Lollipop 5.1.1 (LMY48I) factory image. The same problem still exists. Faced few weird problems on running the first time. Following scenarios explains it exactly...
Not On Charge: Crashes after startup Google logo
Connected to Laptop (USB Charge): Crashes a few minutess after entering "Optimizing apps" screen
On Charger (AC): Completed the install (optimizing apps and setup) without problems

Now I can access the home screen and menu without problems. But when I start any app, phone will go off. Not just apps, at times even when the recent apps menu is opened.
Post Reply Subscribe to Thread

Tags
5.1.1, cm12, lollipop, power

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes