Related
Hey Guys, I've posted in other conversations about bad battery life with blitzkrieg and it seems pretty split down the middle between those who experience good battery life and those who don't. I did follow the advice and wait several days after I re-flashed blitz and my battery has yet to level out. I keep background data off at night when I go to bed, I went to bed with 93% battery left and woke up 7 hours later with a 23% battery life - while the phone was at rest.
I also have a problem about once every two days my phone will freeze up and restart. When it happens it just gets froze on screen and the whole phone vibrates for 20-30 seconds and then restarts.
Has anyone experiences these problems and found a solution to them? Should I change my settings at all?
I really don't want to get an extended battery but with the life my phone is currently getting I don't see much more of an option.
Thanks guys,
The phone freeze/reboot is a known issue with no known resolution. Before I dropped my last phone it had that problem consistently from stock v4 through every variant of the ota updates, revolt roms, gingervolt roms, kennels, scripts, no scripts, blah blah etc.
Now, however, I picked up a second Revo and have run it through gb and flashed gv 1.3, blitz 2.1 and various scripts and tweaks virtually mirroring my old device. I did that Monday morning and haven't had a single instance yet! These guys here do awesome work..
As for the battery draining, I haven't put my extended battery back on this phone yet because I was curious how the stock would perform with these mods. For the first couple days I was discharging at an even 10% an hour. Yesterday and today its dropped to 7.5%. Why? No damn idea. But I can live with that.
So, nothing terribly helpful here but just a disclaimer that your mileage may vary and a nod to the devs here doing kickass work. Good enough that I actively went looking for another Revo instead of fussing with a second line upgrade. That speaks volumes.
Oh yeah I'm not dissing the devs at all they're great!
The revo is a strange device all the reboots due to GPS and airplane mode I'm sure is a hardware fault because every revo I've had has done it and I'm on my third. I love blitz and can't live without my overclock lol I'm just wondering if there's special settings or CPU governors I'm not using that would help.
Sent from my VS910 4G using XDA App
I've used CPU Master and am on ROM toolbox now. Can't say I've seen a significant difference between the two as far as battery goes. I've used both ondemand and smoothass, same deal.
I did have some luck limiting reboots on my first by bumping up the min to 768 but haven't needed to bother on this phone so its 2 something. No extra settings or anything. : )
Guess it's just the screwy differences in hardware that make some a better build quality than others. Well I said I wouldn't do it, but I lied...
I'm restoring to my GV 1.3 pre-blitz image as I type this. Guess I like battery over performance, we'll see...I may be back to blitz.
Can somebody explain the difference between ondemand and smoothass. I still don't understand them that well. Thanks!
I didn't read the whole thread but seeing profiles for the kernel helps a lot like when my screen is off my phone is set to minimum on the min and max which sometimes causes lag turning on but once the screen comes on it's up and running fine. At that level if I keep the screen off it takes nearly an hour to drop a percent.
Sent from my VS910 4G using xda premium
Perhaps this is not the best reference but here is one about charging your Lion battery:
This link won't paste:
[URL="http://dottech.org/tipsntricks/17705/tip-condition-your-new-cell-phones-battery-to-make-it-last-longer-but-be-sure-to-condition-it-properly/[/URL]
It points out two possible issue:
1) over discharge (perhaps our meters account for this,
2) getting the battery hot, my phone does warm up setting on the charger, sounds like the usb port charging might be better for the battery?
Hi,
I'm experiencing this problem more than 1 month. I'm on CM10 with kowalski kernel. It seems my phone sometimes wrongly read battery status and drop battery level percentage from some value to 0 immidiatelly...and shut down occurs at the moment. I thought it could be caused by old battery, but it's not - I buy the new one and the problem still persist and it's VERY irritating...Any solution?
Thanks Jiri
Hello,
It happens also for me but only when I am around 15% and when somebody call me sometimes it fail down sometimes.
It seems that the deep sleep do not allow the system to read a correct battery value when screen came back and the system shutdown because of a too low voltage.
I did not found any solutions in several type of ROM.
Mike
This is a known problem..if i remember correctly tonyp and pengus will fix it in the neew 4.2.2
Sent from my LG-P990 using xda premium
But it's annoying as hell, for me, it starts when my batter is on 50% and low.... 5 - 10 times a day a have to turn on my phone...I cannot use alarm at all....
Andy HOT said:
This is a known problem..if i remember correctly tonyp and pengus will fix it in the neew 4.2.2
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
Mmmhhhh I actually cant remembet them stating that it will be fixed. I remember tony mentioning that its a low priority rom bug. It might be fixed with 4.2.2 but i am not really sure. Regarding the issue I do experience it too but only once every few weeks.
Sent from my LG-P990 using xda app-developers app
I also have this shut down problem. A lot. Maybe 5 times a day and its also driving me nuts. Mine does not happen while phone is in charger - so its probably the "battery reporting wrong charge" problem. Im on new bootloader. I've seen it go from over 50% to 0% battery in an instant.
It might have happened before but much less frequently than now. I started noticing the problem a few weeks ago on Pengus CM10 rom with kowalski kernel (before reading about it). I reflashed the kernel a few times and upgraded the kernel once or twice during that period.
I switched to PA 2.6 - 10 without improvement (KK-116). No apps installed (except Antutu)
I even had the problem in TonyPs TWRP 2.4.3.0 when trying to backup my rom once. Phone shut down while running the backup. Plugged wall charger in while phone still being off and saw that i still had battery left - probably 30-50%. The LG charging graphics icon showed this (you know, the one that shows up if your phone is off and you plug in the charger).
I Tried the following using AIO v5 tool without luck:
1) Reintalled unlocked ICS bootloader
2) Reverting to Old bootloader / partition - then back to new bootloader. Then installed ROM.
I have also tried installing Django Manouche X 1.6.1 (KOB 0.7 kernel) and running Antutu a few times (right after first boot + reboot) with the same result: shutdown. No apps installed.
I can always reproduce the issue: run Antutu benchmark 1-5 times in a row manually on battery. Plugged in, this does not happen.
It happens with or without OC/UV.
I havent tested it extensively, so I cannot be sure, but it seems to me that the rom/kernel isnt the problem since it also happened (once) in TWRP. Could it be the bootloader? Granted this is only a guess, since i have NO knowledge of Android programming or inner workings. Or maybe this is what happens when the LG battery is dying? I got the phone just as it came out.
Edit: BB 30A
I guess i have the same problem but either worse or something totally different.
Regularly around 70%, my battery just drops to 0% and my phone shuts off. It can happen anytime for me and it usually happens just after about 10-15mn of using my phone.
This morning it shut off at more than 90% and then got stuck in a bootloop i presume because it says it doesn't have battery.
Update:
I tried reflashing 30A BB. Didnt help.
Tried Django Manouche X 1.6.1 with kernel without zRAM or ramhack mod. Didnt help.
I Also tried PA 2.6 - 11 on old bootloader, and the battery-jump shutdowns continued when running antutu.
Flashed (completely stock - no rooting etc) ICS 30A with 30A BB through AIO v5. Didnt help. No tweaks or apps (except Antutu) installed. On Antutu run number 5 the phone restarted (with bootloop). Had about 36% battery. Pulled battery, rebooted, phone shut down before booting ROM. Plugged in charger, booted into ROM, showed 100% battery for 10 seconds before showing 30% battery. Tried with quadrant and 30% battery: phone shut down on run 2. Pulled battery, rebooted. Messed around with camera and gallery for 5mins at 26%: phone shutdown.
Im totally lost ... if its not the battery (as indicated by the first post (OP)) i have no idea whats going on. Maybe some other piece of hardware inside the phone is to blame. A piece of hardware that is only called upon when on battery and not when on charger. Maybe a power regulator (or some such thing) is broken?
Next test: Stock GB with GB BB
Edit: Well, the GB ROM + GB BB didnt work either: Gueste2X GoodBye v2.0R + 20L BB rebooted at 75% battery running Antutu. It showed a pop up about low battery and shut down shortly after. For the first time the battery icon still showed 75% when it shut down though.. And this time it showed 21% (not the usual 0% battery) when rebooting to ROM.
I think Im throwing in the towel regarding the software.
My dad also has an o2x, so i will try and swap the batteries and test both phones. I will ofcourse run antutu several times on my dads phone before swapping the batteries..
Update 2:
So i tried my dads O2X battery in my O2X. I Ran Antutu quite a few times and my phone didnt shut down. So I'm pretty certain my battery is messed up which is the reason my phone shuts off "randomly" showing a sudden 0% battery.
Through a google search i found a guy stating that the battery often starts "bulging" when its messed up like mine. His test was to lay the battery flat on a hard even surface and spin the battery. If it keeps going for a couple of seconds it might be messed up. My battery is definitely "bulging" and spins for much longer than my dads. His spins for less than a second. Mine spins for maybe 2 seconds. Not very scientific, but i could definitely see a difference. And i can see the excessive bulging on my battery if i look at it from the side.
So Im ordering a new battery tonight - the originals dont cost much thankfully.
Hope my walls of text can help others in the same situation.
Last update (promise):
Got the new original battery today. Charged it to 100% and used my phone for various tasks until the battery hit 70%. (This was my old batterys absolutely certain "breaking point" when running Antutu benchmark. On my old battery Antutu would crash on first or second run every time when battery is at 70%.)
On the new battery i quit running Antutu after the 13th run in a row without a "battery low" shutdown. The battery was at 40% after the 13th run.
I lay the old and the new battery flat on my smooth metal mousepad and spun them around. The new battery spun for less than 1 second. The old battery spun for almost 4 seconds on one side - almost 3 seconds on the other side.
Two working batteries (my dads 2+ year old battery and my own brand new one) performing equally and at the same time differently to one defective battery. It lends some credence to "the guys" theory that battery defects might result in "bulging" of the battery.
Which means, your battery can be defective but not "bulge". If however, your battery is "bulging" something likely is or will be defective. Fantastic knowledge to posess, if true.
It might seem like a "well duh, thats obvious" revelation, but Ive held my old battery in my hands a lot the last 2 years (especially lately) and I did not notice the "bulging" at any time.
Hey Everyone! Want to share with all about this problem i have been facing.
This GT-N7000 of mine has a very strange problem that has been bugging me since the beginning.
Be it using stock ROM (the days of being in totally stock ICS and jellybean ROM) or now, when i use CM11 4.4.4 (Created by the nice people here on XDA and cyanogen), if i leave the phone idle (e.g screen locked and turn off, when i don't use it and place it in my jeans pocket or lying on the table), once every few days (basically whenever the phone feels like it), when not connected to the charger, it will:
1) randomly decide to become unresponsive (means you can't wake the phone up when pressing any physical buttons or touching the screen)
2) Phone becomes hot while in this unresponsive state (I assume the processor is fully utilized, but doing something totally irrelevant and silly)
3) Need to do a battery pull before you can turn on the phone again
4) Notice upon boot that x% of battery was used up. The battery stats would indicate a break, and sudden drop from 72% of battery to 48% battery.. In other words, it seems the phone does not know what it was doing when it was unresponsive. The faster you catch the phone in this state, the more battery you'll have left. if this happens and you didn't catch the phone in this state, the phone would happily guzzle all the life out of your battery, to 0%.
Now that i am rooted and running CM11, i Digged a little deeper, and it seems that after each unresponsive state reboot, setCPU will indicate that there was alot of CPU usage at 1.4Ghz. At first i didn't bother about it, until i remembered my CPU settings was only supposed to run at 500mhz Maximum when my screen is off, or at 1Ghz when battery is below 80% and screen is on. My CM11 kernal is standard kernel and has NO overclock/underclock.
This means the phone somehow managed to overide setCPU while being in unresponsive state and remain clocked at 1.4 ghz even though the screen is off, thus draining the battery extremely quickly and becoming hot
I have tried multiple factory resets with Stock rom, then Re-flash stock rom with ODIN, to changing to CM11 ROM, and i still have this issue. I do not have a sim card Or SD Card plugged into this phone. (Even with sim card/sd card connected, it still has this issue)
Any other users that encounter this? And has anyone found a way to solve this? Thanks for your inputs!
My new Nexus 6, is now too hot to start, when booting up it turns off before it can ask for the pattern to decrypt the phone. It loads up fine in Fastboot and Recovery, but the CPU temperature in recovery is displayed ranging between 67-70 degrees Celsius. The phone is a month and a half old.
It was performing well without a glitch (apart from the random reboots and 'not charging' at times when plugged in).
Over the last week it started charging really slowly, showing 9 hours to a full charge when the battery was 15%., and after being on charge for that amount of time, the battery topped charging at 65% each time. I suspected that the Turbo Charger/Cable were faulty but other chargers (turbo/normal) and cables showed the same results. The displayed battery health was shown as good. I figured out that the phone could charge up from )% to full in 1.5 - 2 hrs approximately on any of those chargers and cables including the original ones when in Fastboot or Recovery mode. I started charging my phone in recovery mode. The CPU temperature used to be around 65 C. I had done a complete factory reset/data wipe/cache wipe to try and fix the problem.
The phone is rooted, running stock 5.1 rom, latest official TWRP recovery although no apps that use root.
Since day before yesterday the phone started randomly shutting down every 15 - 60 min, overheating I suspect. The battery health was displayed as 'overheat' and he phone completely refused to charge when powered on, and now shuts down when powering on before it can ask for the decryption pattern, though it runs fine in Fastboot/TWRP Recovery. CPU Temp shows as 70C in Recovery.
Please help.
Ahmer Jamil Khan said:
My new Nexus 6, is now too hot to start, when booting up it turns off before it can ask for the pattern to decrypt the phone. It loads up fine in Fastboot and Recovery, but the CPU temperature in recovery is displayed ranging between 67-70 degrees Celsius. The phone is a month and a half old.
It was performing well without a glitch (apart from the random reboots and 'not charging' at times when plugged in).
Over the last week it started charging really slowly, showing 9 hours to a full charge when the battery was 15%., and after being on charge for that amount of time, the battery topped charging at 65% each time. I suspected that the Turbo Charger/Cable were faulty but other chargers (turbo/normal) and cables showed the same results. The displayed battery health was shown as good. I figured out that the phone could charge up from )% to full in 1.5 - 2 hrs approximately on any of those chargers and cables including the original ones when in Fastboot or Recovery mode. I started charging my phone in recovery mode. The CPU temperature used to be around 65 C. I had done a complete factory reset/data wipe/cache wipe to try and fix the problem.
The phone is rooted, running stock 5.1 rom, latest official TWRP recovery although no apps that use root.
Since day before yesterday the phone started randomly shutting down every 15 - 60 min, overheating I suspect. The battery health was displayed as 'overheat' and he phone completely refused to charge when powered on, and now shuts down when powering on before it can ask for the decryption pattern, though it runs fine in Fastboot/TWRP Recovery. CPU Temp shows as 70C in Recovery.
Please help.
Click to expand...
Click to collapse
Flash factory image, lock bootloader, and RMA.
Evolution_Tech said:
Flash factory image, lock bootloader, and RMA.
Click to expand...
Click to collapse
What is RMA?
Ahmer Jamil Khan said:
What is RMA?
Click to expand...
Click to collapse
Returning the phone to the seller to be exchanged for a new device. RMA https://www.google.nl/search?q=rma&ie=utf-8&oe=utf-8&gws_rd=cr,ssl&ei=sihYVcWrCcyBU-vVgIgM.
gee2012 said:
Returning the phone to the seller to be exchanged for a new device.
Click to expand...
Click to collapse
Thanks a lot. Flashed a stock ROM/Recovery and locked the bootloader again. Will be shipping it off.
Just wondering, what caused this kind of an issue?
Ahmer Jamil Khan said:
Thanks a lot. Flashed a stock ROM/Recovery and locked the bootloader again. Will be shipping it off.
Just wondering, what caused this kind of an issue?
Click to expand...
Click to collapse
Probably a hardware issue, it can happen
Probably not a good idea to charge in recovery as all cores are always maxed out, causing it to be hot anyway.
Reflash the stock kernel using the flashify app from app store. This will rule out software issues
https://play.google.com/store/apps/details?id=com.cgollner.flashify
After looking at thread like these , i am reluctant to use the Quick Charger that came with the phone. I normally charge the phone with USB (PS4) or a normal Samsung Charger
Where people go wrong is using the phone while fast charging. Playing a graphics intensive game or streaming video while fast charging isn't typically good for battery temps
No amount of re-flashing will fix the problem. The Nexus 6 has a known overheating problem. I am using a workaround and so far have not had a single incident. I was getting two or three reboots a day before this. Set the screen resolution to 1080p. Instructions here:
http://nexus5.wonderhowto.com/how-t...xus-6-by-lowering-display-resolution-0159881/
This also works with rooted Marshmallow with Elemental kernel. You will not notice a difference - other than the reboots stopping and your battery lasting longer.
madmartian said:
No amount of re-flashing will fix the problem. The Nexus 6 has a known overheating problem. I am using a workaround and so far have not had a single incident. I was getting two or three reboots a day before this. Set the screen resolution to 1080p. Instructions here:
http://nexus5.wonderhowto.com/how-t...xus-6-by-lowering-display-resolution-0159881/
This also works with rooted Marshmallow with Elemental kernel. You will not notice a difference - other than the reboots stopping and your battery lasting longer.
Click to expand...
Click to collapse
not true. first off, describe "overheating".
i run my cpu set to 3033mhz high and low. no matter what i do, i can not get it to "overheat". when the n6 overheats, it reaches 100C, at which it will either power off or reboot at that point. thus happens to let the cpu cool off.
remember, you are running a quad core cpu, at 2649mhz by default. now i ask again, describe "overheating".
oh, and one more. it has been proven already that lowering your resolution does not save battery. you arent disabling pixels, that where the same amount of the power is lost, no matter what you change your resolution.
anything else? :silly:
simms22 said:
not true. first off, describe "overheating".
i run my cpu set to 3033mhz high and low. no matter what i do, i can not get it to "overheat". when the n6 overheats, it reaches 100C, at which it will either power off or reboot at that point. thus happens to let the cpu cool off.
remember, you are running a quad core cpu, at 2649mhz by default. now i ask again, describe "overheating".
oh, and one more. it has been proven already that lowering your resolution does not save battery. you arent disabling pixels, that where the same amount of the power is lost, no matter what you change your resolution.
anything else? :silly:
Click to expand...
Click to collapse
It solved the problem for me. That is a fact. Others have also posted that it has solved the problem for them. When playing certain graphic-intensive games, the battery would drain quickly and the phone would overheat and reboot. It is of course true that the screen pixels are still lit, however, the system doesn't have to keep track of all that extra data and the app has less work to do, thus it really does save battery and prevent overheating. It's the same as speeding up your fps in a PC game by lowering your game resolution, even though you're still using the same monitor.
madmartian said:
It solved the problem for me. That is a fact. Others have also posted that it has solved the problem for them. When playing certain graphic-intensive games, the battery would drain quickly and the phone would overheat and reboot. It is of course true that the screen pixels are still lit, however, the system doesn't have to keep track of all that extra data and the app has less work to do, thus it really does save battery and prevent overheating. It's the same as speeding up your fps in a PC game by lowering your game resolution, even though you're still using the same monitor.
Click to expand...
Click to collapse
i give you a few points with the gpu, but the amount saved would be extremely minimal. unless thats all you do, play games all day. then you might see an extra 5%, maybe.
I have huge heating issues when bulk-gaming. I even tried capping the GPU at 300 MHz. It's fine just gaming but gaming and charging is a no no for me. It *used* to work fine, but now it just throttles, even though it is only running at maybe 60 Degrees C. (I set my thermal throttle at 75). It's not really so much of an overheating issue as it is a throttling issue. Throttling on this device is poor and hard to work around.
danarama said:
I have huge heating issues when bulk-gaming. I even tried capping the GPU at 300 MHz. It's fine just gaming but gaming and charging is a no no for me. It *used* to work fine, but now it just throttles, even though it is only running at maybe 60 Degrees C. (I set my thermal throttle at 75). It's not really so much of an overheating issue as it is a throttling issue. Throttling on this device is poor and hard to work around.
Click to expand...
Click to collapse
su(press enter)
echo N > /sys/module/msm_thermal/parameters/enabled(press enter)
this always works for me, no throttling issues
simms22 said:
i give you a few points with the gpu, but the amount saved would be extremely minimal. unless thats all you do, play games all day. then you might see an extra 5%, maybe.
Click to expand...
Click to collapse
My results are specific to certain high-battery-drain games. I am seeing my battery usage HALVED while playing certain games after making this change. These games tend to have a lot of animation. General use or "normal" (not unusually high) battery drain games are likely closer to your 5%.
Likewise, I noticed these games use a lot less battery on my older phones (with lower resolution screens).
If a phone is overheating during "normal" (not high drain) situations, then lowering the resolution may not be effective.
my phone only heats up when it is charging goes up to 45c
simms22 said:
su(press enter)
echo N > /sys/module/msm_thermal/parameters/enabled(press enter)
this always works for me, no throttling issues
Click to expand...
Click to collapse
Sorry, missed this post.
Will it survive reboot?
Sent from my Nexus 6 using Tapatalk
danarama said:
Sorry, missed this post.
Will it survive reboot?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
no. it has to be run every time you boot up.
I just replaced my aging iphone 4 with an HTC One M7.
So far, I'm loving having an Android phone, and I'm really glad I switched, but I seem to be having a problem with the phone.
It is getting pretty hot and the battery is draining alarmingly fast.
The phone was reset to factory settings when I received it yesterday, and it is the AT&T software version. It is on Android 4.4.2
Although this is my first Android phone, it is not my first Android device (Xperia Play used as a portable emulator, Nvidia Shield, Asus Memo Pad HD7) so I knew the obvious things to try.
The phone feels slightly warm at all times, even when just sitting in my pocket. When I have a CPU-intensive app (youtube for instance) running, the phone gets pretty hot.
I understand that the aluminum chassis transmits heat very efficiently, and that this phone should feel warmer than a plastic phone, so I installed a CPU temperature app.
I'm getting in the high 40's to low 50's (celsius) with no CPU-intensive apps running.
Looking in my running apps, I don't see anything that looks like it is making heavy demands on the CPU.
While at work today, I put it in airplane mode (but kept wifi on) because I don't get a very good signal at work anyway, and I thought this might be causing the battery to drain quickly.
I forgot about this, and so the phone has been in airplane mode since 1pm today (it is now 8:45).
While browsing the internet just now looking for a solution to the problem, I watched as the last 18% of the battery drained down to 1% in around 15 minutes.
This is in airplane mode, with battery saving mode activated, Blinkfeed deactivated, and the screen on minimum brightness.
Does this sound like abnormal behavior?
I need to know fast, because if there is something wrong with the phone, I need to return it without delay.
DoctorBeat said:
I just replaced my aging iphone 4 with an HTC One M7.
So far, I'm loving having an Android phone, and I'm really glad I switched, but I seem to be having a problem with the phone.
It is getting pretty hot and the battery is draining alarmingly fast.
The phone was reset to factory settings when I received it yesterday, and it is the AT&T software version. It is on Android 4.4.2
Although this is my first Android phone, it is not my first Android device (Xperia Play used as a portable emulator, Nvidia Shield, Asus Memo Pad HD7) so I knew the obvious things to try.
The phone feels slightly warm at all times, even when just sitting in my pocket. When I have a CPU-intensive app (youtube for instance) running, the phone gets pretty hot.
I understand that the aluminum chassis transmits heat very efficiently, and that this phone should feel warmer than a plastic phone, so I installed a CPU temperature app.
I'm getting in the high 40's to low 50's (celsius) with no CPU-intensive apps running.
Looking in my running apps, I don't see anything that looks like it is making heavy demands on the CPU.
While at work today, I put it in airplane mode (but kept wifi on) because I don't get a very good signal at work anyway, and I thought this might be causing the battery to drain quickly.
I forgot about this, and so the phone has been in airplane mode since 1pm today (it is now 8:45).
While browsing the internet just now looking for a solution to the problem, I watched as the last 18% of the battery drained down to 1% in around 15 minutes.
This is in airplane mode, with battery saving mode activated, Blinkfeed deactivated, and the screen on minimum brightness.
Does this sound like abnormal behavior?
I need to know fast, because if there is something wrong with the phone, I need to return it without delay.
Click to expand...
Click to collapse
Is the phone brand new? It runs more the first time you turn it on, I think due to some profiling. If it's still like that the day after turning it on for the first time I'd probably be concerned. It could be due to something you've installed--what have you installed (if you don't mind sharing)?
I've definitely experienced what you're talking about on CyanogenMod, but never that I can recall on the stock ROM. When it happened on CyanogenMod, rebooting generally seemed to fix it.