Ever since I got the Desire HD (which is a little over a week now), I am running MIUI on it as my daily ROM. I replaced the Torch.apk with the one from CyanogenMod 7.1 (just like I did with my old Desire), so I can have the Full brightness mode.
The Full brightness mode never caused any problems. I could use it, and also with strobe -- I was avoiding using it for extended periods of times, to not harm the LEDs. It was not on for more than 30 seconds continuously.
Now, it seems to be causing problems. I try to turn on the LEDs, on full brightness, and the phone would instantly shut down. Same happens with strobe. It's all good if I don't use full brightness, though.
It doesn't reboot or freeze or anything. It just SHUTS ITSELF DOWN!
I tried this with : MIUI with original CM kernel, with LorDModUE kernel, and also with CyanogenMod 7.1.0. I wanted to try with CyanogenMod 6.1.0, to see if that helps (yeah, silly), but it seems like the ROM isn't booting at all.
I went on ROM Manager, in the section for CyanogenMod, and saw some comments of other people who were experiencing the same problem. Some guy was saying that this is because of the battery. Well, I know this for sure : my battery is as good as new.
Anyone... any ideas...?! :/
which MIUI are you using. If you're using freshly sqeezed then i get no problem like that but if you're using other custom ones, it is possible that the customization done to the stock MIUI can cause problems, some scripts maybe? you should try using other MIUI versions..
shad0wboss said:
which MIUI are you using. If you're using freshly sqeezed then i get no problem like that but if you're using other custom ones, it is possible that the customization done to the stock MIUI can cause problems, some scripts maybe? you should try using other MIUI versions..
Click to expand...
Click to collapse
I'm using the UK variant (MIUIAndroid). Since I also tried with CyanogenMod 7.1.0, and it was the same issue... I doubt that matters.
Right now, I am having more serious problems. Phone shuts itself down after boot... It doesn't do that when it's in Hboot or Recovery. I even flashed 3 other ROMs upon full wipe.
Battery : 49%. Phone shuts down.
Going into Hboot. 5 minutes, no shut down.
Going into Recovery. It shows battery is at 25%.
Reboot.
Now it shows that I have 11% left.
I guess LorDModUE's overcharging thing kind of messed up with this battery. Otherwise, I see no reason for it to act like this, since I barely used the phone today, and it was at 80% when I left home this morning (GMT+2, that is).
I'll just charge it now... then I'll have to go out. I'll flash Tiamat kernel, see how it handles THAT.
My battery is very faulty, alright. I'll buy a MOMAX X-Level battery (of 1150 mAh) next week.
what rom are you on?
i had the same problem on a previous rom, i changed over and it was sorted.
not to sure why it happens though.
MrLarner said:
what rom are you on?
i had the same problem on a previous rom, i changed over and it was sorted.
not to sure why it happens though.
Click to expand...
Click to collapse
I am on the latest MIUI (MIUIAndroid, not US). I also tried with CyanogenMod 7.1. I believe it's the battery, which barely holds half of the charge... I'm going to replace it soon, see if THAT solves the problem.
As I originally said, it didn't cause any trouble at all the first few days... just like the battery...
--
EDIT. It really was the battery. Got a new one now and it works to have Torch on full brightness.
I still don't get why it would turn off the phone even with the battery ~fully charged and the charger still connected.
can someone tell me please, where to get this torch-app with full brightness. I've tested it on jellytime, but now I'm on a different ROM.
Loved this heavy brightness... :cyclops:
Related
Hello all. Ever since I got my EVO, I've been experiencing random restarts, even before I was rooted. Right now, I am running CM7.1 and Tiamat from kernel manager, and I probably have to do about 8 restarts and 5 battery pulls a day, no matter how often I use the phone. For instance, today I woke up and had to do a battery pull because the screen would not turn on. The light was also still orange despite the battery being fully charged. I unplugged it at about 8 in the morning and by 10 with no use, I had to pull the battery again because the screen was frozen off once again. Once I got it back on, the battery was down to 80%. I tried using it and half the apps would force close immediately, so I restarted... You get the picture. Some roms have been better than others, and kernels don't seem to make any difference, and I figured it was about normal. Then, I installed what is supposed to be a really buggy CM7 on my touchpad, and have only had to restart it once in the past 2 days, which makes me question how stable my phone actually should be. Does it seem like I should take it in to sprint, or is my experience about normal?
I also never overclock because of my already poor battery life and have tried underclocking, but don't see any noticible difference
bump. should I post somewhere else?
Run an RUU but stay s-off for the moment and see if the problem persists. If your phone begins working properly, then you can flash a recovery and flash whatever rom you want - but don't restore your backup. I'd start totally fresh if RUUing fixes your problems, don't restore your apps and data, just download them from the Market as you need them.
If the RUU doesn't help and the problem continues, take it in to Sprint. It's up to you if you want to s-on before taking it in - I've never heard of anyone getting problems from Sprint with s-off but without root, but I think it's a general rule to do so.
I hope everything works out for you!
Sent from my Evo + MIUI using Tapatalk!
I have heard and seen on here many times that random reboots are caused by battery problems, and bad software installs. Try calibrating the battery, also use battery monitor widget to see what ur batt temps are. Then reinstall all your apps, do not restore them then see if that helps.
Sent from my PC36100 using XDA App
I'll try an RUU when I get enough time to do some thorough testing. I have reinstalled everything directly from the market multiple times since I've had the phone, and also have used a total of four batteries with no change in behavior. I Will try the RUU soon though. Thanks for the replies
Hi,
Today I was using my phone as usual, battery was about 75%, then suddenly while I was using Whatsapp the screen went totally black (I have to add that it has happened before, but I haven't been able to identify what is causing it, it might be Android 4.2,franco kernell and maybe switchpro).
I think it has to do with the brightness control becase the screen still detects the touchs, the phone is certanly working, but with a black screen (Brightness to 0% maybe?) so after I remove the battery it boots fine.
But this time, when it was restarting the phone I noticed the battery went down to 20% from 75%! That's impossible to happen (Phone would have melted) because the restart time was under 5 min!
What is more strange is that the phone stayed with 20% for a very long time, it even "autocharged" itself (I know it's impossible)...
What could it be? Help appreciated!
Thanks
Setup is:
Gnex 4.2.1 stock
TWRP recovery (last version)
Franco Kernel 342
peikojose said:
Hi,
Today I was using my phone as usual, battery was about 75%, then suddenly while I was using Whatsapp the screen went totally black (I have to add that it has happened before, but I haven't been able to identify what is causing it, it might be Android 4.2,franco kernell and maybe switchpro).
I think it has to do with the brightness control becase the screen still detects the touchs, the phone is certanly working, but with a black screen (Brightness to 0% maybe?) so after I remove the battery it boots fine.
But this time, when it was restarting the phone I noticed the battery went down to 20% from 75%! That's impossible to happen (Phone would have melted) because the restart time was under 5 min!
What is more strange is that the phone stayed with 20% for a very long time, it even "autocharged" itself (I know it's impossible)...
What could it be? Help appreciated!
Thanks
Setup is:
Gnex 4.2.1 stock
TWRP recovery (last version)
Franco Kernel 342
Click to expand...
Click to collapse
yap, I have two gnexs both have had this problem.
I can get a screenshot with vol-down + power
but the screen is totally black.
Yeah I've had this screen of death issue too. I've been trying forever to diagnose what is causing the problem. It happens on any kernel including stock. I factory reset, flashed stock images, everything.
I've narrowed it down to the weather channel app, Adobe flash, csipsimple app, or animations being turned off. Still trying to nail it...
i not have restaert using apk franco updater and set :good:
The sudden battery drop is normal when you pull out the battery. Basically, the phone loses it's calibration on the battery capacity. And that " auto charge" is your phone slowly trying to get a better estimate of your phone battery capacity.
Sent from my Galaxy Nexus using Tapatalk 2
I believe that SODs are a common problem faced by many on 4.2 i personally havn't faced it yet =] running arhd with ak kernel
I was able to reproduce this using Velis Auto Brightness https://play.google.com/store/apps/...SwxLDEsImNvbS52ZWxpcy5hdXRvLmJyaWdodG5lc3MiXQ
After messing with the brightness it wents black screen.
I'm sure this has to do with the autobrigtness!
Best regards
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
peikojose said:
Hi,
Today I was using my phone as usual, battery was about 75%, then suddenly while I was using Whatsapp the screen went totally black (I have to add that it has happened before, but I haven't been able to identify what is causing it, it might be Android 4.2,franco kernell and maybe switchpro).
I think it has to do with the brightness control becase the screen still detects the touchs, the phone is certanly working, but with a black screen (Brightness to 0% maybe?) so after I remove the battery it boots fine.
But this time, when it was restarting the phone I noticed the battery went down to 20% from 75%! That's impossible to happen (Phone would have melted) because the restart time was under 5 min!
What is more strange is that the phone stayed with 20% for a very long time, it even "autocharged" itself (I know it's impossible)...
What could it be? Help appreciated!
Thanks
Setup is:
Gnex 4.2.1 stock
TWRP recovery (last version)
Franco Kernel 342
Click to expand...
Click to collapse
the battery losing charge, and the "autocharge", i see often across many devices. that happens to me when flashing different things over a short time period or when benchmarking and crashing its really not losing the charge, it just thinks it did. the batterystats file becomes inaccurate fairly often, maybe it corrupts. and the autocharge or ghostcharge(usually pretty slow btw) is the batterystats slowly becoming accurate again.
klobkelosh said:
I've narrowed it down to the weather channel app, Adobe flash, csipsimple app, or animations being turned off. Still trying to nail it...
Click to expand...
Click to collapse
I think you just helped me pin it on animation off. I have had the black screen happen to me 3 times in the 3 days that I disabled animations (stock rooted ROM, developer options). I kept trying to find an app that caused it but the animation off matches the start of my problem.
EDIT: Well, animation off isn't the cause since I just had another black screen.
simms22 said:
the battery losing charge, and the "autocharge", i see often across many devices. that happens to me when flashing different things over a short time period or when benchmarking and crashing its really not losing the charge, it just thinks it did. the batterystats file becomes inaccurate fairly often, maybe it corrupts. and the autocharge or ghostcharge(usually pretty slow btw) is the batterystats slowly becoming accurate again.
Click to expand...
Click to collapse
Totally agree with you!happened to me many times too,especially when crashing after tweaking\benchmarking.
I flashed a custom ROM [unofficial CM9 ICS4.0.4]. Everything seems to be working fine, but there are a few problems and I'm wondering if this is normal for those using this. It's my first time flashing a ROM on my android and I'm not sure if it's normal. Did some searching in the forum, couldn't find much info too. Maybe I didn't search hard enough!
Anyway, here are some issues, I'm not even sure if it's the ROM.
1. Sometimes, the apps just bring me back to the home screen several times. Example: Running whatsapp brings me to home screen a few times, or when I go into a conversation, it brings me back to the conversation list but eventually it works.
2. On another occasion, every app that I ran would be unresponsive and I needed to end it. Solved it by rebooting.
3. Battery drain is very fast with little usage. I thought running a custom ROM usually provides better battery life.
I've not overclocked it, it's still in it's default value after flashing 1024. So I doubt it's anything to do with that. But since we're on the topic on overclocking. Desire HD didn't have anything beyond Gingerbread. So if we're flashing anything greater, is there a need overclock to be able to work comfortably on a higher OS? Is there a minimum or maximum for it to function comfortably?
Thanks!
Hmm, did more reading up.
Could it be I didn't calibrate my battery after flashing a new ROM?
Just flashed ARHD 6.4, will try to calibrate after that.
Appreciate any other advice though
Hi Guys,
i have a bit of a problem with the battery in my GNex maguro.
I'm an avid Rom flasher, but when i have something that works well i usually settle with it for a while. So i flashed Cataclysm (http://forum.xda-developers.com/showthread.php?t=1995801) sometime in the last months and it was running great. Best bettery life i had so far.
Then with the release of Android 4.4 i looked for a rom to test it. I flashed XP (http://forum.xda-developers.com/showthread.php?t=2539201) and i really like the 4.4 changes.
But since then my battery won't even last a day in standby mode. I thought maybe it's an issue with 4.4. still, but even after flashing back to Cataclysm (newest release) i still had the same issues. I thought it may well be, that the final version isn't what it used to be, so i flashed another rom again. This time Purity (http://forum.xda-developers.com/showthread.php?t=2012706) aaaand... still the same problem. So now i'm pretty much lost. I also tried different kernels (lean kernel specifically) but to no avail.
My battery used to last 2+ days in idle mode. Now i can see my battery drop every minute. It barely holds over 10 hours. I already did a full phone wipe and flashed back to stock before installing cataclysm again but still no improvement.
I hope someone can help me here or point in the right direction.
Sorry if this topic already exists, but the search funtion doesn't seem to work right now and google didn't show something helpfull.
Thank you all in advance.
I don't know why you would still have bad battery life moving back to the original rom you used but.. on 4.4 it is most likely the new Google Now features that constantly listen for voice commands. Disable it by long pressing on an empty part of the home screen and go to settings. Slide Google Now Off and go to voice and turn off hotword detection as well.
I get great standby battery life on 4.4. I'm running the 11/29 ART build of cmetal(toro), 150ish hours of uptime without any issues so far.
Re: Bad Battery Life since KK
What kernel are you running? Are you just using whatever kernels come with each ROM?
I'll try turning off google now and the voice stuff and report back.
It still seems really weird to me, that the problem still persists after flashing back to 4.3. My guess would be, that 4.4 flashes something hidden that messes with the battery. But i don't know where or what.
Especially since it persists after a complete wipe (/data, /system and /cache).
Well, i'll see how it behaves without google now.
What kernel are you running? Are you just using whatever kernels come with each ROM?
Click to expand...
Click to collapse
Well i used mostly lean Kernel with 4.3 roms but i can't find any 4.4 kerneles besides CM. I have XP installed right know which uses CM Kernel.
Re:Bad Battery
Make sure your governor is set to interactive or ondemand...it could be seeing power drain from being set to one of the performance settings.
It's also possible that your battery is just going bad...do you have a backup battery you can try?
Well i used mostly lean Kernel with 4.3 roms but i can't find any 4.4 kerneles besides CM. I have XP installed right know which uses CM Kernel.[/QUOTE]
It could just be that you need to replace your battery. They are only good for so many charges and do degrade.
-----------------------------------------------------
Sign up for COPY with this link, and we'll both get 5 GB of free cloud storage in addition to the usual 15 GB: https://copy.com?r=m3arsR
Free GiffGaff SIM with £5 credit: http://redir.info.giffgaff.com/r/?id=h4d8d850,c0e1337,c0e139c&p1=d3xp2pc
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Reporting back. After deactivating google now yesterday my battery is still ****. It's at 50% after 2h idle and 30 minutes screentime. Before the 4.4 flash it would be at around ~85-90% now. I suspect that 4.4 flashes something in some hidden partition that i don't have access to, that messes with the battery. Users on other boards report the same issues as i have.
dwoods1983 said:
Make sure your governor is set to interactive or ondemand...it could be seeing power drain from being set to one of the performance settings.
It's also possible that your battery is just going bad...do you have a backup battery you can try?
Click to expand...
Click to collapse
Just checked. Governor is set to interactive. It's also the default setting.
I sadly don't have a backup battery.
It could just be that you need to replace your battery. They are only good for so many charges and do degrade.
Click to expand...
Click to collapse
Could be, of course. But it's kinda weird that the decline is so dramatic and it has to be a pretty big coincidence that it just happend after a 4.4 flash. Seems unlikely to me.
edit: I'll order a new battery just to eliminate the battery as the source of error.
Mine is pretty bad but it's running google play to death so maybe gapps flash was bad? dunno
merid14 said:
Mine is pretty bad but it's running google play to death so maybe gapps flash was bad? dunno
Click to expand...
Click to collapse
this maybe issue of ram management.. try some good apps to control those background & foreground app from running without control. dont use any task killer.. please
i recommend using greenify.apk. donate version much better.
sorry for my bad english
galaxy nexus i9250
Same problem here. Since I flashed Kitkat on my phone, battery life isn't enough to last a day on standby. I tried installing another kernel (ASKP) but to no avail. Please keep in mind that I'm not very experienced with custom roms and rooting my phone. Does anyone have some good tips to improve battery life?
Update: After fiddling around a bit with better battery stats, greenify and a bunch of other stuff... i still don't have a solution. I made some screenshots of my stats, but can't post them here because i don't have permission to do that...
So i reflashed swordrune's cm11 rom and it seems to be working better with 1080p kernel w/o art enabled. i'm 11 hrs in with 80% battery on the extended battery (toro btw)
Un4s said:
Update: After fiddling around a bit with better battery stats, greenify and a bunch of other stuff... i still don't have a solution. I made some screenshots of my stats, but can't post them here because i don't have permission to do that...
Click to expand...
Click to collapse
are u sure greenify didnt helping??? already got rooted & exposed installer running??
can u state your screen on time??
usually gnex can handle 3-4 hour screen on depend on battery condition n phone performance... not include idle n stanby time.
galaxy nexus i9250
memaro_maro said:
are u sure greenify didnt helping??? already got rooted & exposed installer running??
can u state your screen on time??
Click to expand...
Click to collapse
Yes, i am rooted, but i didn't have the donate version of greenify. Bought it now and will test again.
Screen on time ~1:30h
Un4s said:
Yes, i am rooted, but i didn't have the donate version of greenify. Bought it now and will test again.
Screen on time ~1:30h
Click to expand...
Click to collapse
that will help.
if u lightweight user, i suggest u to optimized performance. use apps such trickster mod, rom toolbox, or in addition of any light battery saving apps ( for optimization)
should be improve on screen time.
galaxy nexus i9250
Not to hijack your thread, but I'm also experiencing battery issues after flashing the XP 4.4 rom. I did enjoy it but the battery drain was terrible. Not only that, for some reason my charger drains on a 1A charger but charges slowly on a .7A somehow. I only have 1 micro usb cable so I can't test if it's the cable and I can't find any apps to check the current speed. I tried downgrading and flashing to Slimbean but so far it's been no dice.
memaro_maro said:
that will help.
if u lightweight user, i suggest u to optimized performance. use apps such trickster mod, rom toolbox, or in addition of any light battery saving apps ( for optimization)
should be improve on screen time.
Click to expand...
Click to collapse
Ok, back again. hibernated every app and system-app that was running in background. Still wasn't getting better. I then saw the only services still running are google location services. I deactivated them now to see if these are causing it.
The biggest wakelocks i have are "wlan_rx_wake" which seem to be a known problem with KK:
http://forum.xda-developers.com/showthread.php?t=2519294
I then researched again and found several threads in google groups which describe the same problems that i have. Across several devices (though mostly Nexus 4, 5 and 7).
Google seems to be aware of that issue and is working on it.
Not to hijack your thread, but I'm also experiencing battery issues after flashing the XP 4.4 rom. I did enjoy it but the battery drain was terrible. Not only that, for some reason my charger drains on a 1A charger but charges slowly on a .7A somehow. I only have 1 micro usb cable so I can't test if it's the cable and I can't find any apps to check the current speed. I tried downgrading and flashing to Slimbean but so far it's been no dice.
Click to expand...
Click to collapse
Yes, same for me. Charging is really slow since 4.4 as is the bootprocess of my phone. From the first vibrate when switching the phone on it takes ~10 seconds until the google logo pops up.
i dont know any about gapps issues bcoz not running any gapps in my phone since last year.
1. try searching for updated radio.img (baseband/ radio) if got any network issue.
2. try install trickster mod app. this app can help you for tweaking into deep sleep, also help for optimizing.
galaxy nexus i9250
crayjin said:
Not to hijack your thread, but I'm also experiencing battery issues after flashing the XP 4.4 rom. I did enjoy it but the battery drain was terrible. Not only that, for some reason my charger drains on a 1A charger but charges slowly on a .7A somehow. I only have 1 micro usb cable so I can't test if it's the cable and I can't find any apps to check the current speed. I tried downgrading and flashing to Slimbean but so far it's been no dice.
Click to expand...
Click to collapse
try this for helping you go into deep sleep
galaxy nexus i9250
memaro_maro said:
try this for helping you go into deep sleep
galaxy nexus i9250
Click to expand...
Click to collapse
Hmm I don't know if this is going to resolve the charging problem but i will try it and also try and use a battery calibrater and come back.
Alright so I've been doing research online this week and haven't been able to fix it so I'm coming to you guys. I'll give you a little background to hopefully help speed up this process.
So about 3 weeks ago I rooted my Sprint LG Optimus G after having it for almost a year to get some better performance and battery life out of it. After getting it all setup, I noticed a huge difference and was even able to watch the movie Flight and two episodes of Family Guy off Netflix and my battery still lasted 9 hours that day.
Well last weekend after uninstalling some Google apps I soft bricked my phone. Thanks to the help of sawdey21 on the IRC I was able to get it back up and running with LGNPST. After getting it running, I switched launchers (from Holo to Nova) and also unlocked mine phone via FreeGee with TWRP. Since then, my battery life has been terrible. To give you a reference it took my phone 8 hours to fully charge last night while it was off (although since I unlocked it I have a new charging animation and after a few seconds of the animation, instead of shutting the screen off like it use to it now just goes to a black screen but is still on as you can see the brightness. It never shuts off). After unplugging it, an hourly later I was down almost 15% after just listening to music and after 4.5 hrs its at 30% and I just plugged it in. Today I have done nothing but listen to music and just period check/browse my phone.
Is it possible that the bricking messed up my battery? Or the unlock? I switched back to the previous Holo launcher I was using before and it made no difference. I've also unistalled several apps I downloaded since the bricking I thought could be causing it.
Has anyone ran into this or could help? My next step is to boot back into Download Mode and try LGNPST again. I would post pics of Battery Settings, WakeLocker and BetterBatteryStats but I can't since I'm a new comer.
Thanks!
Different roms use a different amount of power...
Sent from my GT-P3100 using xda app-developers app
xSTUDDSx said:
Alright so I've been doing research online this week and haven't been able to fix it so I'm coming to you guys. I'll give you a little background to hopefully help speed up this process.
So about 3 weeks ago I rooted my Sprint LG Optimus G after having it for almost a year to get some better performance and battery life out of it. After getting it all setup, I noticed a huge difference and was even able to watch the movie Flight and two episodes of Family Guy off Netflix and my battery still lasted 9 hours that day.
Well last weekend after uninstalling some Google apps I soft bricked my phone. Thanks to the help of sawdey21 on the IRC I was able to get it back up and running with LGNPST. After getting it running, I switched launchers (from Holo to Nova) and also unlocked mine phone via FreeGee with TWRP. Since then, my battery life has been terrible. To give you a reference it took my phone 8 hours to fully charge last night while it was off (although since I unlocked it I have a new charging animation and after a few seconds of the animation, instead of shutting the screen off like it use to it now just goes to a black screen but is still on as you can see the brightness. It never shuts off). After unplugging it, an hourly later I was down almost 15% after just listening to music and after 4.5 hrs its at 30% and I just plugged it in. Today I have done nothing but listen to music and just period check/browse my phone.
Is it possible that the bricking messed up my battery? Or the unlock? I switched back to the previous Holo launcher I was using before and it made no difference. I've also unistalled several apps I downloaded since the bricking I thought could be causing it.
Has anyone ran into this or could help? My next step is to boot back into Download Mode and try LGNPST again. I would post pics of Battery Settings, WakeLocker and BetterBatteryStats but I can't since I'm a new comer.
Thanks!
Click to expand...
Click to collapse
I'm not 100% sure but it is possible the bricking messed with the battery. LGNPSTing back to stock could have affected it, anytime you flash a new rom it takes a couple of days to "settle in" but you said last weekend so it should be settled by now.
But from your info, it may be the way you are charging it. There is a common misconception that every so often you are supposed to let your battery drain fully and then charge to 100%. This is only true for nickel based batteries, ours is lithium so this is in fact quite detrimental. Lithium batteries are built to be charged often and you should never let it dip too far into the red. Doing so decreases the life and performance of your battery significantly. 5% is as low as I'll let my battery dip before charging and even that is pushing it imo. There is an app in the play store called battery calibration that actually tells you to do this, but like I said, it's only useful for nickel based rechargeable batteries. Also this same app's function is deleting the batterystats.bin file in order to "recalibrate" the battery. This is also completely false as that file has nothing to do with how well your battery performs.
I wouldn't turn the phone off to charge, just charge it while it's still on so the screen actually shuts off. Checking your wakelocks and using greenify on power hungry apps will go a long way. I also turn my capacitive buttons off because I don't need to see them to know left, right, center and what they do. And if I'm not using it, it is always off, sync, gps, brightness when inside, etc. But as I said, it may have been the way you were charging it, it might not affect the battery for months, then all of a sudden your battery doesn't perform as well because it's dying due to improper charging techniques. And when you LGNPSTed back to stock, your system tries to start fresh which is why it may have happened immediately afterwards.
I hope some of this helps you - if using greenify doesnt show improvement you may want to buy a bigger capacity battery and start fresh. Installing the new battery is tricky however, there are youtube videos on how to do it, but it may not be for everyone.
Good luck and I'm sorry if I assumed too much or misread your info!
EDIT: You may also want to try flashing a different stock kernel(I use Viper1.1, my signature has a link to the thread) and using trickstermod to undervolt the cpu. The improvement is minimal but every little bit helps. On average I get a full 24 hours in between charges and usually charge once it hits 10-15%. And it only takes about 60-120 minutes to fully charge.
However the lgog is also very fickle, what works for one may not work on another, even if it's the exact same model. Many people have reported the same security bootloop soft brick after deleting google apps for instance, but I deleted(not frozen or disabled) google apps just fine. The only ones I have on my phone are play store and google search and I'm still on stock zvc.
HPTesta,
Appreciate the response and all the info. To clarify a little more, I've never installed a custom ROM. Just been doing launchers from the Play Store besides having to do the LGNPST. As far as Apps I've been using greenify since I rooted 3 weeks ago as well as CPU Tuner which had both been doing great for me before this.
As far as charging goes, I generally never run my phone compleley dead. I usually charge when its getting low but last night I ran it complete lay dead to use Wake locker (read in the app store to drain bat, recharge full, and use after a couple hrs.
One thing I did find weird is that I don't remember how much battery I had when I bricked it but after doing the LGNPST I had 0 (Don't know if that's normal).
Also, never used the Battery Calibration app.
And based off what your saying would you not recommend doing LGNPOST again?
xSTUDDSx said:
HPTesta,
Appreciate the response and all the info. To clarify a little more, I've never installed a custom ROM. Just been doing launchers from the Play Store besides having to do the LGNPST. As far as Apps I've been using greenify since I rooted 3 weeks ago as well as CPU Tuner which had both been doing great for me before this.
As far as charging goes, I generally never run my phone compleley dead. I usually charge when its getting low but last night I ran it complete lay dead to use Wake locker (read in the app store to drain bat, recharge full, and use after a couple hrs.
One thing I did find weird is that I don't remember how much battery I had when I bricked it but after doing the LGNPST I had 0 (Don't know if that's normal).
Also, never used the Battery Calibration app.
Click to expand...
Click to collapse
Ok well it seems like you follow good battery techniques. Maybe try LGNPSTing back to a full stock zvc(or zvb and then updating to zvc) and charge it to 100%(let it sit at 100% while still charging for 15 mintues or so) before rerooting and unlocking. I would probably also copy your internal to your pc and wipe everything in recovery before doing LGNPST just to make sure it is a completely clean slate. I added an edit in my post above as well.
I had a strange issue a few weeks back where I tried overclocking my cpu with AK kernel - my battery was at 99%. My phone shut off and wouldn't come back on, just had a red blinking light. I later found out it was an issue with AK. I charged it for a few minutes and luckily was able to get into TWRP. The strange part was that when I did get into TWRP my battery read 0%, I did a full wipe and restored my backup, then my battery read 99% in TWRP. It's a different issue from yours but makes me think that it's possible that your softbrick and LGNPSTing affected it somehow.
---------- Post added at 03:52 PM ---------- Previous post was at 03:49 PM ----------
xSTUDDSx said:
And based off what your saying would you not recommend doing LGNPOST again?
Click to expand...
Click to collapse
I honestly have not had or heard of any issues with LGNPST and battery performance. Anytime Ive had to use LGNPST with a full stock .bin, it essentially set my phone back to factory condition, battery performance included. However since this all happened when you did this, maybe try flashing another rom first, even a stock based one and leave LGNPST as a last resort. Just make sure you read the instructions for whatever rom you decide to test and always do a full wipe(data, cache, dalvik and system) before flashing.
EDIT: Sorry if it seems like I gave you conflicting info, if it was me I would probably be weary of using LGNPST again, personally. But if I tried flashing other things, different recoveries, roms and still had the same issue, maybe it was just a slightly messed up LGNPST flash and would try it again as a last resort.
Forgive my ignorance but I've never actually booted into twrp recovery. Its volume up and power but where do you go from their to wipe?
xSTUDDSx said:
Forgive my ignorance but I've never actually booted into twrp recovery. Its volume up and power but where do you go from their to wipe?
Click to expand...
Click to collapse
After holding volume up + power, you then will hit volume down twice and power again. Once in TWRP it is very easy, there is an install button, wipe button, etc. Hit the backup button, pick all available options and then do a backup and reboot into your OS. From there, download a rom(optimus DE is a great stock rom) to your internal and you will probably need gapps as well(depends on rom but almost all of them need gapps or you wont even have the play store - just read the install instructions of the rom). Go back into recovery, This is under the advanced wipe button in the wipe menu - wipe everything except internal storage(if you wipe internal you will lose your backup, pictures, music, etc) and then go to install, pick the rom.zip and flash that, then pick the gapps zip and flash that as well.
Also keep in mind that if you flash an AOSP or CM based rom, the file system will be different. Our internal storage is /data/media but for AOSP based it is /data/media/0. So say for instance you make a backup in TWRP of your stock then flash an AOSP rom, it will look as if your internal is gone as well as your backup. You will just have to use a root file explorer to copy the /data/media/TWRP folder to /data/media/0/TWRP and then you will be able to restore your backup from TWRP.
If you are just going to try LGNPST again then when you get into TWRP pick everything including internal and turn the phone off and put the phone into dl mode(you know what you are doing from there).
One final note, if you are using current FreeGee to unlock then you are most likely using the updated TWRP. Some people have had SEVERE issues with it, for others it works just fine. You need it to install any rom based on Android 4.4 but I personally use TWRP 2.5.0.0 which will flash stock to Android 4.3 roms just fine and it is rock solid stable. So unless you are planning on installing a kit kat rom, I would first download the TWRP 2.5.0.0 zip found here to your internal, go into twrp, pick the install button, find the .zip file and install that, then go to reboot in TWRP's main menu and choose recovery instead of system. TWRP should now read 2.5.0.0.
Sorry for the books I'm writing here but I think it's always best to be thorough!! And I haven't slept in about 30 hours so I am a bit scatter brained.