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.
Related
So the other day, I forgot to close an app down--the Schwartz Unsheathed, if you are curious--and when I fished my phone out again, it was hot. Very, very hot. Battery information indicated 41C which, in the grand scheme of things, isn't that high (wouldn't worry me with a PC's graphic card, for example, or CPU) but it felt incredibly warm to the touch. Fine, I shut the app down, removed the battery cover and let the phone cool down. No problem.
It might be the apps I've been trying since then, but I have been experiencing performance and stability issues. Things slow down sometimes. On the Desire ROM, Rosie kept force-closing every now and again. On Enomther's which as we all know is just about the stablest thing that ever stabled, Launcher2 does ditto (the Launcher Dock may be the culprit, though, as it seems to do some weird **** and I've removed it since. Fiddling around with BetterCut also seems to cause force-closes). So could that be it? Did the phone overheat (but if so, shouldn't it have shut itself down) and now something's broken? Getting antsy. :/
41°C should not be a problem, but consider that this was a measurement from the battery pack and that a sensor like that can easily go +/- 5 to 10 degrees.
so well, some chip on the nexus could have gotten way hotter than 41°C. maybe something fried, some defect that was already there and now its really broken.
still, this can be a bit subjective, the phone will seem broken if you think it's broken you can always do a factory reset, reflash the current rom and try from there.
Yeah, could just be my own jitters--I'd experienced issues before, usually caused by a ROM or whatever--and lately my PC's been having problems, so it might well be some kind of placebo effect. Unless it and my N1 magically entered a symbiosis or something.
Thanks for the quick reply.
once my phone accidently fell onto my bed and under my pillow while i was charging it over night and i woke up at 4 am and found a burning out nexus under my pillow. i unplugged it and nothing seemed damaged but it still worried me.
I think if you are worried about it and you are rooted you should install SetCPU. It has a profile designed so that is you his a preset temp it will down clock your CPU.
I use setCPU to save my batterylife ie.
100% - 50% run full cpu on demand.
Idle/Standby downclock to 400Mhz
50% or less down clock to 600Mhz on demand
20% or less down clock to min.
I also complement this with locale for low bat. dimness, wifi off, bluetooth off. etc.. etc.. ( a little off topic I know)
Well, looks like updating More Icons Widget was what did it; things seem to work okay now.
Was wondering what the maximum advisable temperature is?
Maybe the phone has protection for the CPU? but Li-ion batteries dont like heat, it shortens their effective life.
my battery reached 44.3C yesterday on a 4 hour journey in the car using co-pilot and the phone actually net discharged despite the fact it was on a 1A USB charger for the entire journey - about 80% at start of journey and 20% at end.
I've installed setcpu now and set the temperature profile to drop the max speed to 768 if temp is >44C and another one to drop the speed if power is less than 30%, may need further tweaking though. This was not in my car and the back of the phone was effectively unventilated, in my car I have an open backed holder near an air vent.
Hi, I bought a SGS a few days ago. Everything was fine at first, but then it started to overheat even for a few minutes of use. It is around 32 degrees celsius when the screen is off, but even if I do nothing and keep the screen on for some time, it shows 41 degrees celsius. If I open a game or the music player it becomes 48.Not occasionally, every time I do the same thing. If it was a graphically intensive game it would probably be 55 easily. I deleted everythng and did a data factory reset, it slowed down the speed of the heating but the same thing happens eventually. I've checked similar threads and someone said even a temperature of 55 degrees is normal, but that can't be true since when the temp is 48-49 the phone becomes really sluggish, and apps stop working. Any ideas?
The most important thing is though, I dropped the phone once. However, it wasn't an issue that day and the day after. I don't think they are related, what do you think? Is there a cooling system that might be damaged? I don't want to send the phone back because there are small scratches around the silver part of the phone because of it and they might resend the phone saying it is the user's fault.
Lastly, the Froyo is installed now. If I upgrade to Gingerbread is there a chance that it will help the temperature stay normal?
I have had temperature of 60 degrees. It's pretty normal, I don't think gb would change anything from it.
When the temperature is about 50, the phone starts to lag badly, the browser lags and the games freeze. Before this, the highest I saw was 36 when playing a game.
As far as I know, when it hits 60 degrees, the phone turns off automatically, are you sure? It becomes very ucomfortable to hold too.
Definitely normal when the phone is doing something intensive. Phones don't have cooling systems - do you want a fan at the back of the device? Also, the phone can go beyond 60 degrees - it doesn't turn off when it reaches 60. If there is a defense mechanism it goes beyond that point. The battery on the other hand stops charging if the phone reaches a certain temperature. I don't recall any sluggishness with the phone at high temperatures or at least nothing like games freezing. One thing to do is to reduce to minimum the brightness of the screen coz Super AMOLED screens tend to produce a lot of heat at high brightness levels and that's what mainly heats the phone so much. Also, you can get a kernel with which you can undervolt the cpu - that will keep the cpu cooler.
Inagalaxyfaraway said:
Hi, I bought a SGS a few days ago. Everything was fine at first, but then it started to overheat even for a few minutes of use. It is around 32 degrees celsius when the screen is off, but even if I do nothing and keep the screen on for some time, it shows 41 degrees celsius. If I open a game or the music player it becomes 48.Not occasionally, every time I do the same thing. If it was a graphically intensive game it would probably be 55 easily. I deleted everythng and did a data factory reset, it slowed down the speed of the heating but the same thing happens eventually. I've checked similar threads and someone said even a temperature of 55 degrees is normal, but that can't be true since when the temp is 48-49 the phone becomes really sluggish, and apps stop working. Any ideas?
The most important thing is though, I dropped the phone once. However, it wasn't an issue that day and the day after. I don't think they are related, what do you think? Is there a cooling system that might be damaged? I don't want to send the phone back because there are small scratches around the silver part of the phone because of it and they might resend the phone saying it is the user's fault.
Lastly, the Froyo is installed now. If I upgrade to Gingerbread is there a chance that it will help the temperature stay normal?
Click to expand...
Click to collapse
I've never monitored internal temperatures, but....
Mine very rarely feels hot to the touch. If I played Dungeon Hunter for a half hour it would get pretty warm (not hot though) but that's normal I'd say. Send it back to Samsung Service Center - this phone costs half a grand, don't chance that it's slowly cooking itself to death!
Oh and I didn't find gingerbread to make a dramatic difference, wouldn't expect it to solve all your problems. Sorry dude.
try uc/uv-ing the phone, might help:\
I told you there was something wrong . It might be normal, but the beginning of it was definitely not normal. The thing is, when I set the alarm, the phone starts overheating. It goes to 40 without starting any apps, and sees 45-48 under 5 minutes of use depending on what I am doing. When I turn it off, it hovers around 36. I've never seen it past 38 even when there are three apps working. I've noticed this a few hours ago and still am still testing it, so I am not 100% sure, any of you had a problem with the alarm? It sounds even more reasonable because the time the phone started to do this roughly coincides with the time I set the alarm for the first time.
Hopefully the alarm is to blame, I can live without that .
I overclocked mine and It gets hot as hell. even when I charge the phone? Is there anyone who knows how to solve it?
DeaDman594 said:
I overclocked mine and It gets hot as hell. even when I charge the phone? Is there anyone who knows how to solve it?
Click to expand...
Click to collapse
What program did you use to OC?
DeaDman594 said:
I overclocked mine and It gets hot as hell. even when I charge the phone? Is there anyone who knows how to solve it?
Click to expand...
Click to collapse
Undervolt or reduce overclock, simples!
GTi9000 insanity cm012/glitch
Hello everyone, im here to share my future experiences with seeing just how far i can push my battery and share how i did it with everyone.
Backstory:
I'm going hiking in Virginia tomorrow for a week, and would really like to have a camera without carrying extra devices, so..... its time to mod my nexus 5 as low power as possible!
here are some of the "prep steps" that ive done in order to obtain my battery life, i'll update the thread to let everyone know how it worked out!
Rooted
CM stable installed. (up to date as of this post)
Screen Brightness set to low as possibe.
Elemental X Kernel installed (Using TricksterMOD, these are my settings)
Multicore power saving = 2
CPU Freq. Lock= Min( 652800) Max( 652800) Max.screen off(300mhz)
Google Now/voice anything turned off
Home screen has only one page
Airplane Mode
Greenify Installed, Using Xposed Module for advanced/better control
Hibernating almost everything 3rd party, esp things like Facebook,KiK etc.)
BootManager xposed module installed, everything disabled that isn't needed.
Installed gsam for more meaningful data logging.
Unchecked Auto Sync Data in the Data Usage settings
Changed CPU clock min/max 652800
Installed Deep sleep battery saver Xposed module. (on slumber profile) buts phone into deep sleep when screen is off.
If i remember anything else i did on here, i'll post it.
(sorry its taking so long for replies/updates, "new user status" prevents my posts 5 minutes in between.) (hard to believe, been a member since 2011, just lurked alot.)
*May have found lower limit on the CPU, no instability as of yet, however phone is acting a bit erratic, looking into this currently. (booting takes FOREVER. this is a problem.)
*Trickster seems to pick and choose sometimes whether it wants to listen to me, sometimes CPU freq. on sreen off is changing to 652800 on its own. :/ anyone know of a way to get it to respect my settings?
*Changed CPU freq. to min max 652800 based on advice of the community.
Usage scenario:
I'll be using my phone mainly for pictures throughout the trip and possibly listening to some music, anytime its not in use, ill be turning it outright off, however, id really like to see just how far i can take this.
Anyone have any other suggestions for longevity?
gh0stpirate said:
Hello everyone, im here to share my future experiences with seeing just how far i can push my battery and share how i did it with everyone.
Backstory:
I'm going hiking in Virginia tomorrow for a week, and would really like to have a camera without carrying extra devices, so..... its time to mod my nexus 5 as low power as possible!
here are some of the "prep steps" that ive done in order to obtain my battery life, i'll update the thread to let everyone know how it worked out!
Rooted
CM stable installed. (up to date as of this post)
Screen Brightness set to low as possibe.
Elemental X Kernel installed (Using TricksterMOD, these are my settings)
Multicore power saving = 2
CPU Freq. Lock= Min(960000) Max(stock) Max.screen off(157440)
Google Now/voice anything turned off
Home screen has only one page
Airplane Mode
Greenify Installed, Using Xposed Module for advanced/better control
Hibernating almost everything 3rd party, esp things like Facebook,KiK etc.)
BootManager xposed module installed, everything disabled that isn't needed.
If i remember anything else i did on here, i'll post it.
Usage scenario:
I'll be using my phone mainly for pictures throughout the trip and possibly listening to some music, anytime its not in use, ill be turning it outright off, however, id really like to see just how far i can take this.
Anyone have any other suggestions for longevity?
Click to expand...
Click to collapse
Don't forget Google Now and Auto Syncs. (uncheck Auto Sync Data in the Data Usage settings).
Check out this thread here for some more suggestions.
I've been able to push it pretty far even with an active internet connection, though most of the usage comes from reading Reddit or forums with Tapatalk. That was on stock with no root access.
It's possible that it will take less power to just put your phone to sleep when not using than booting it up every time you need it. Depends on how often you boot though.
bblzd said:
Don't forget Google Now and Auto Syncs. (uncheck Auto Sync Data in the Data Usage settings).
Check out this thread here for some more suggestions.
I've been able to push it pretty far even with an active internet connection, though most of the usage comes from reading Reddit or forums with Tapatalk. That was on stock with no root access.
Click to expand...
Click to collapse
Thanks for the tips! heres what i changed:
installed gsam for more meaningful data logging.
unchecked Auto Sync Data in the Data Usage settings
changed CPU clock min/max 300mhz
Zainiak said:
It's possible that it will take less power to just put your phone to sleep when not using than booting it up every time you need it. Depends on how often you boot though.
Click to expand...
Click to collapse
I was thinking that as well, however it would be difficult to find that "mid point" if i had an emergency backup of battery bank to test this theory, i would. However, im going to be stuck in the mountains and would rather have the ability to take the pictures i want rather then pure data log expedition. Great insight/hivemind though.
gh0stpirate said:
I was thinking that as well, however it would be difficult to find that "mid point" if i had an emergency backup of battery bank to test this theory, i would. However, im going to be stuck in the mountains and would rather have the ability to take the pictures i want rather then pure data log expedition. Great insight/hivemind though.
Click to expand...
Click to collapse
Based off my experiments, it takes less than 1% of battery to reboot the phone though I would guess somewhere in the 0.5% range. In airplane mode with all of these functions disabled and in deep sleep, 1% would probably get you 6 hours of idle time or even more. Therefore I would only power it down if you won't be using the phone for at least the next 6 hours. Rough estimations of course, I think either way it would be pretty similar.
If the phone is not powered down you might be inclined to use more than you would otherwise.
bblzd said:
Based off my experiments, it takes less than 1% of battery to reboot the phone though I would guess somewhere in the 0.5% range. In airplane mode with all of these functions disabled and in deep sleep, 1% would probably get you 6 hours of idle time or even more. Therefore I would only power it down if you won't be using the phone for at least the next 6 hours. Rough estimations of course, I think either way it would be pretty similar.
If the phone is not powered down you might be inclined to use more than you would otherwise.
Click to expand...
Click to collapse
Extremely interesting/relevant! do you still have any screenshots or data logs on these restarts anymore?? if thats the case, then yes, id only turn it off while im sleeping then!
gh0stpirate said:
Extremely interesting/relevant! do you still have any screenshots or data logs on these restarts anymore?? if thats the case, then yes, id only turn it off while im sleeping then!
Click to expand...
Click to collapse
Unfortunately I do not, just speculation based off what I've seen when monitoring current draw (using Current Widget) and the battery percentage before and after a reboot.
I do have shots demonstrating low idle drain with Auto Syncs and Locations disabled. On average I'd say my drop is about 1% over 5 hours of deep sleep, but it's always hard to tell because there's no way for me to know exactly when it drops without active logging which would interfere with the phone's deep sleep.
Generally speaking a reboot uses ~1% of your battery. If you're locking your CPU to run at only 300mhz I would just leave it on the entire time. Especially if mobile data is off and so is WiFi. Make sure you go into Settings > WiFi > *Touch the 3-dot menu* > Advanced > Disable "Scanning Always Available". I lose about 1-2% in airplane mode overnight over clocked with high quality sound driver from Viper4Android. Plus the Google now hotword activated everywhere but lock screen.
A while back I did a test with my N5 to purposely nerf its power to see how long of a SoT I could get with it. I did pretty much everything you mentioned in the OP. Locked max CPU frequency to match min. Lowest screen brightness, airplane mode, etc. I was able to get over 12 hours SoT. So if the N5 can get 12 hours with the screen on using the same setup you plan in using with the phone getting nice and warm... I don't think a week standby time is too farfetched as long as it's idle most of the time except for pictures. Depends on how much music you listen to I guess. Only problem is even with music saved on the device itself, running at 300mhz you're going to run into skips and pops. Especially when the screen is off. Music playback will be kinda iffy.
Good luck though and let us know how it goes.
Edit: Actually I was mistaken. I just disabled everything like location, sync, etc. Default kernel parameters except switching to ondemandplus governor. This was on an older release of Uber kernel. 12+ hours SoT with ~30% battery remaining!
Here's my post;
http://forum.xda-developers.com/showthread.php?p=52133394
You'll suffer Lag I would think with CPU at 300mhz max. And likely use more battery than your saving with the phone struggling to process anything.
May have instability issues too. I'd rethink that.
KJ said:
You'll suffer Lag I would think with CPU at 300mhz max. And likely use more battery than your saving with the phone struggling to process anything.
May have instability issues too. I'd rethink that.
Click to expand...
Click to collapse
I agree, but I think that if the phone isn't used at all besides some pictures here and there, it should be fine. If he plans on music playback he's going to have to raise the max frequency, no question. Music playback won't work reliably that low. I don't think lag will be an issue for him considering what's he's trying to accomplish with the phone, but I can't speak to instabilities with 300mhz as max as I've never tried it.
RoyJ said:
I agree, but I think that if the phone isn't used at all besides some pictures here and there, it should be fine. If he plans on music playback he's going to have to raise the max frequency, no question. Music playback won't work reliably that low. I don't think lag will be an issue for him considering what's he's trying to accomplish with the phone, but I can't speak to instabilities with 300mhz as max as I've never tried it.
Click to expand...
Click to collapse
Currently Using Apollo music player, can confirm Zero issues using music playback, confirmed CPU freq. using cpu frequency app. most of these things are using hardware decoders
RoyJ said:
I agree, but I think that if the phone isn't used at all besides some pictures here and there, it should be fine. If he plans on music playback he's going to have to raise the max frequency, no question. Music playback won't work reliably that low. I don't think lag will be an issue for him considering what's he's trying to accomplish with the phone, but I can't speak to instabilities with 300mhz as max as I've never tried it.
Click to expand...
Click to collapse
But if the phone is sleeping soundly as it should.... The max CPU is irrelevant if not being used. The lag and strain to run processes may hurt a lot though.
You let the music play while the screen was off for a few minutes or did you just play it for a few seconds? I have music stutter on screen off with frequencies higher than 300mhz. I get it with 729mhz. If it doesn't happen to you, awesome. Not sure why though. Do you have time to purchase an OTG charger? Might be worth looking into and they aren't that expensive.
http://www.amazon.com/Best-Sellers-...-Phone-Battery-Packs/zgbs/wireless/7073960011
Currently listening with screen off/on full songs. No issues. no time to purchase an OTG charger however :/
Updated main post to reflect newest enhancements.
Trickster seems to pick and choose sometimes whether it wants to listen to me, sometimes CPU freq. on sreen off is changing to 652800 on its own. :/ anyone know of a way to get it to respect my settings?
It can be done
Sent from my Nexus 5 using XDA Free mobile app
I seem to remember a thread somewhere on xda regarding a CPU's "race to finish". Basically a cpu will work as much as it can (or better said "is allowed) to finish each task after which go to a low power state, like a marathon runner accelerates on certain portions and then "coasts" to conserve energy or a a car running on a near empty gas stank. Since you have a couple of days left I would try raising the frequency (600,800 and 1000) and see what happens to the power drained. It would definitely help with usability, as well as enable using photosphere or panorama ( which take quite a few seconds even at full speed to process) if needed. If the power drain would increase by less than 10% I would call that an acceptable trade-off.
While there is nothing wrong with finding the limit of your device, I think that an external battery pack would be a much better solution. There are ones available for less than $20 that could fully charge your device twice,
Flukzr said:
I seem to remember a thread somewhere on xda regarding a CPU's "race to finish". Basically a cpu will work as much as it can (or better said "is allowed) to finish each task after which go to a low power state, like a marathon runner accelerates on certain portions and then "coasts" to conserve energy or a a car running on a near empty gas stank. Since you have a couple of days left I would try raising the frequency (600,800 and 1000) and see what happens to the power drained. It would definitely help with usability, as well as enable using photosphere or panorama ( which take quite a few seconds even at full speed to process) if needed. If the power drain would increase by less than 10% I would call that an acceptable trade-off.
While there is nothing wrong with finding the limit of your device, I think that an external battery pack would be a much better solution. There are ones available for less than $20 that could fully charge your device twice,
Click to expand...
Click to collapse
I remembered a discussion along those lines, ill bump the freq. to 652800 min max, and update the main post. An external pack would be great, but i unfortunately just don't have the cash at the moment. between the trip and i just ordered a triple monitor stand and a new wifi usb to play with nethunter
gh0stpirate said:
Screen Brightness set to low as possibe.
Airplane Mode
Click to expand...
Click to collapse
This is basically all you need, the phone will idle for a week or so in airplane mode.
ever since i have updated to lollipop firmware, i am facing strange overheat and sudden battery drain problem on my c6902. it does not happen always but sometimes and restarting fixes it. and also faux clock shows continuous use of first and last core of cpu. do you have the same? any help?
harman_preet72 said:
ever since i have updated to lollipop firmware, i am facing strange overheat and sudden battery drain problem on my c6902. it does not happen always but sometimes and restarting fixes it. and also faux clock shows continuous use of first and last core of cpu. do you have the same? any help?
Click to expand...
Click to collapse
did you did a factory reset after install?
Mine is draining so fast. Even when turned off. I didn't do a factory reset after install because i dont want to lose any data. My maximum charge is 11% after 3 hours. I dont even know if i can flash anything because it's lowbat.
for me is ok. the battery life is good, and i got overheathing only when i did a first start after i installed it. try to install kernel aduitor and see if all governors are on "ondemand", and if all freqs are ok.
reinstalled and did everything as it should be but stll gets hot and quickly drains out battery sometimes not always
without using battery drains to 50% in few hours
Possible Solution to Over heating after lollipop install
I had the same issue of Xperia Z1 Compact over heating after lollipop install. I backed up all my data using Sony Companion and reset my phone to factory. After that my phone is working like a champ. No more over heating and battery life last over a day and half. Hope this help.
guys,
I had the same issue and im thinking to downgrade to kitkat for real
I have tried it.. No use. It will heat up in kitkat too. Really annoying.
harman_preet72 said:
I have tried it.. No use. It will heat up in kitkat too. Really annoying.
Click to expand...
Click to collapse
How old is your device? Looks like the battery is having issues. Or maybe the motherboard is supplying over current to the processor.
Its about 2 yrs old. But the heating started just after lollipop update. Before it was ok, no problem was there.
having the same issue since update to lollipop. really annoying thing. battery drained in an half hour down to 89%. that just cant be normal.. phone is not rooted or anything.
Hi,
For those who are rooted and with a custom kernel, I have faced the same problem recently and after playing a bit with CPU configuration on "Pimp My Z1" app it seemed to work again.
First thing I did was reboot the device, that way I was sure that no app I've opened was draining my battery.
Second I opened the "Pimp My Z1" app and changed the configuration of CPU to:
Maximum: 1958MHz
Minimum: 300MHz
Governor: lionheart
Click to expand...
Click to collapse
Also set the max clock of GPU to 320MHz.
As for the power management config, I've set this way:
Multi Core Power Saving: Aggressive.
Hotplug Driver: Intelliplug
Eco Mode: On
Power Suspend: On
Click to expand...
Click to collapse
Today I'm with 82% battery but with 59 minutes of screen on time (~70% brightness) and some more of music playing. Also using Stamina Mode. Heats a bit, but doesn't show any draining symptom.
If you still face overheating problems, I suggest downloading the Greenify app and hibernating many apps. That worked for me on S4 when it was with a similar problem.
All the best,
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Xperia Z1
Worked for me
I have the LG Leon for MPCS w/ 5.0.2 root-TWRP. I began experiencing this after flashing a sound engine mod. I also noticed my charging port pin was bent slightly. Another possibility was changing CPU gov-I/O-min. freq.
I flashed mod remove zip, then restored from Nandroid prior to, and fixed pin. Still had it.
BUT: I kept my phone on top of my AC unit vent for roughly 13 hours while it was on & plugged in, set brightness to night mode, 15 sec time out, and disabled daydream.
PROBLEM GONE.
Also set CPU back to reg. settings.
CPU has been steady 28-30 deg. C all day.
Hope this helps.
drakeheart77-XDA
drakeheart77 said:
I have the LG Leon for MPCS w/ 5.0.2 root-TWRP. I began experiencing this after flashing a sound engine mod. I also noticed my charging port pin was bent slightly. Another possibility was changing CPU gov-I/O-min. freq.
I flashed mod remove zip, then restored from Nandroid prior to, and fixed pin. Still had it.
BUT: I kept my phone on top of my AC unit vent for roughly 13 hours while it was on & plugged in, set brightness to night mode, 15 sec time out, and disabled daydream.
PROBLEM GONE.
Also set CPU back to reg. settings.
CPU has been steady 28-30 deg. C all day.
Hope this helps.
drakeheart77-XDA
Click to expand...
Click to collapse
My stock unrooted LG Leon has has an overheating problem as well
Sent from my LGMS345 using Tapatalk
Hi guys, long time since I've been on here.
I have a S4 i9500, and I was having mega drainage issues. I installed Novalaunch, and disabled the samsung touchwiz crap - battery usage is SOO much better already. I have had lollipop for a few months now, and I did factory reset it, twice, and install all the apps manually via google play. It got so bad, that i HAD to run my phone with power save on ALL THE TIME, and even then, it would be pretty hungry. the other day, I ran it on full power(1.6ghz) and it chewed 40% in around 1 hour. All I was doing was had Pandora music on.
I have a tool called 'Cool Tools', and I monitored the IO activity bfore, and it show pretty high utilization all the time, even with the screen off. With Novalauncher, its hitting rock bottom(low), even while using it..
Its soo good now, to give you an idea - I charged my phone last night(around 9pm), and restarted it and unplugged the charger. I ran it on full power(power save OFF), over night, with data on, and it only chewed 15%. MASSIVE difference. I'm at 60% now, and I've been running Pandora for at least 3 hours now, and using some other apps as well. Its been 14 hours or so already.
hybridtheory said:
Hi guys, long time since I've been on here.
I have a S4 i9500, and I was having mega drainage issues. I installed Novalaunch, and disabled the samsung touchwiz crap - battery usage is SOO much better already. I have had lollipop for a few months now, and I did factory reset it, twice, and install all the apps manually via google play. It got so bad, that i HAD to run my phone with power save on ALL THE TIME, and even then, it would be pretty hungry. the other day, I ran it on full power(1.6ghz) and it chewed 40% in around 1 hour. All I was doing was had Pandora music on.
I have a tool called 'Cool Tools', and I monitored the IO activity bfore, and it show pretty high utilization all the time, even with the screen off. With Novalauncher, its hitting rock bottom(low), even while using it..
Its soo good now, to give you an idea - I charged my phone last night(around 9pm), and restarted it and unplugged the charger. I ran it on full power(power save OFF), over night, with data on, and it only chewed 15%. MASSIVE difference. I'm at 60% now, and I've been running Pandora for at least 3 hours now, and using some other apps as well. Its been 14 hours or so already.
Click to expand...
Click to collapse
Even I faced fast battery drain with Touchwiz launcher.
Now running custom ROM and seeing that CPU usage is lesser and battery stays longer.
However, nothing can beat Kitkat's battery usage. Lollipop, according to me, is a battery killer wrapped in material design for disguise.
Xperia z1 battery drain issue or problem
I FOUND THE MAIN CULPRIT FOR BATTETY DRAIN AFTER 5.1.1 LOLLIPOP UPDATE. Its the overheat control app. As you all may know that after first update from jellybean 4.2 to kitkat 4.4, the phone tends to get overheated while multitasking. Thus overheat control app eats up the battery and drain it when the phone starts getting hot.
I REQUEST ALL THE DEVELOPERS TO CHECK IT AND PROVE IF I M WRONG.
I m sure that Google will find the answer to the battery drain issue fix in overheat control app.
XxLordxX said:
Hi,
For those who are rooted and with a custom kernel, I have faced the same problem recently and after playing a bit with CPU configuration on "Pimp My Z1" app it seemed to work again.
First thing I did was reboot the device, that way I was sure that no app I've opened was draining my battery.
Second I opened the "Pimp My Z1" app and changed the configuration of CPU to:
Also set the max clock of GPU to 320MHz.
As for the power management config, I've set this way:
Today I'm with 82% battery but with 59 minutes of screen on time (~70% brightness) and some more of music playing. Also using Stamina Mode. Heats a bit, but doesn't show any draining symptom.
If you still face overheating problems, I suggest downloading the Greenify app and hibernating many apps. That worked for me on S4 when it was with a similar problem.
All the best,
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Xperia Z1
Click to expand...
Click to collapse
thanks bro
this solved my problrme on cm12.1 kernel M5 v10.2
sent from my xperia z1
Sir just try flashing some other Rom... I make sure u have better battry life
XxLordxX said:
Hi,
For those who are rooted and with a custom kernel, I have faced the same problem recently and after playing a bit with CPU configuration on "Pimp My Z1" app it seemed to work again.
First thing I did was reboot the device, that way I was sure that no app I've opened was draining my battery.
Second I opened the "Pimp My Z1" app and changed the configuration of CPU to:
Also set the max clock of GPU to 320MHz.
As for the power management config, I've set this way:
Today I'm with 82% battery but with 59 minutes of screen on time (~70% brightness) and some more of music playing. Also using Stamina Mode. Heats a bit, but doesn't show any draining symptom.
If you still face overheating problems, I suggest downloading the Greenify app and hibernating many apps. That worked for me on S4 when it was with a similar problem.
All the best,
~Lord
"This Story Ends Where It Began" - Octavarium (Dream Theater)
Sent from my Xperia Z1
Click to expand...
Click to collapse
i've tried this
but seems the battery managent only have multi core power seving and hotplug driver
theres no eco or something like that
mine is lockedbootloader :/
but i think its woorking tho
For the past couple of weeks, my rooted Nexus 6 (64GB, rooted, unencrypted user partition, carrier Verizon) was running hot for no apparent reason, thus, poor battery performance. I literally cannot figure out what was causing it, and start turning down the application notification down to a minimum. That helped a bit, but does not resolved the issue. I also cannot figure out why I was running out of storage space.
A couple of days ago I noticed that cache usage on storage uses 17GB. After I cleared it, everything seems to run much better. The unit no longer runs hot for no apparent reason, and battery power retention works better. Anyone else experiencing this?
Not with the cache, but one day (only once thank god) my phone overheated and shut off on me. Just had the nexus in my pocket and when I went to look at the time it was almost to hot to touch. I turned it back on after it cooled down and haven't had a problem since. The phone also was having programs crash a lot on me as well right before this happened. My phone is rooted and I did the update to 5.1.1. I haven't had the issue or crashing since. I doubt that's what stopped it from happening again but still.
...
MisterChuffy said:
Once mine did this too I charged and it God really hot. It wasnt able to touch it really. Unfortunately I wasn't able to see the temperature but it has to be something about higher than 60*°C. I turned it after a while and had to wait like 20 minutes then it was normal. I started again and since then no issue.
Click to expand...
Click to collapse
i get mine to 90C all the time, on purpose, and i can hold it fine. 60C+ is easy to hold. and it takes seconds for it to cool down.
My N6 gets very hot occasionally -- almost too hot to handle. I've never had a phone behave this way. In spite of some assurances that it has an auto-shutdown mechanism if it gets dangerously hot, I'm still concerned.
Isn't heat bad for electronic components? I've read that Li-Ion batteries degrade faster when hot.
RealDogBoy said:
My N6 gets very hot occasionally -- almost too hot to handle. I've never had a phone behave this way. In spite of some assurances that it has an auto-shutdown mechanism if it gets dangerously hot, I'm still concerned.
Isn't heat bad for electronic components? I've read that Li-Ion batteries degrade faster when hot.
Click to expand...
Click to collapse
If getting that hot have rogue app or something else locking CPU wide open. I know having Bluetooth enabled with nothing to pair to will cause this. It is your setup and not a regular issue with device.
prdog1 said:
If getting that hot have rogue app or something else locking CPU wide open. I know having Bluetooth enabled with nothing to pair to will cause this. It is your setup and not a regular issue with device.
Click to expand...
Click to collapse
It's not Bluetooth -- I keep that off unless I'm using it. I don't think it's a rogue app either. One incident that I remember: I was updating a lot of apps over wi-fi and charging (Qi wireless) at the same time. My thought was that the Qi charging was generating some of the excess heat (since it's not as efficient as just plugging in the micro-usb) plus the CPU was working hard with the updates.
RealDogBoy said:
It's not Bluetooth -- I keep that off unless I'm using it. I don't think it's a rogue app either. One incident that I remember: I was updating a lot of apps over wi-fi and charging (Qi wireless) at the same time. My thought was that the Qi charging was generating some of the excess heat (since it's not as efficient as just plugging in the micro-usb) plus the CPU was working hard with the updates.
Click to expand...
Click to collapse
Yes QI charging causes heat and will eventually eat your battery. Should never download and QI charge at same time. Looking to execute your device. Lol