Database Develop

How much heat can the N1 take?

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.

[Q] My phone keeps dying!

In the last week or so I have picked up my phone three times and it has been dead.
The power button doesn't turn it on again.
I have to take the battery out and then restart it.
I'm running a rooted 2.35 JVT.
I have nothing untoward running ...
Settings
Sense analogue clock
DRM content
Software update
SnsService
Google Play Store
Samsung keypad
Apart from Angry Birds, there's almost nothing else, and nothing new for months except Bad Piggies.

deanbilly said:
In the last week or so I have picked up my phone three times and it has been dead.
The power button doesn't turn it on again.
I have to take the battery out and then restart it.
I'm running a rooted 2.35 JVT.
I have nothing untoward running ...
Settings
Sense analogue clock
DRM content
Software update
SnsService
Google Play Store
Samsung keypad
Apart from Angry Birds, there's almost nothing else, and nothing new for months except Bad Piggies.
Click to expand...
Click to collapse
Could it be a dead battery?
otherwise, tried to wipe and (re)flash a rom?

The battery is fine, and the ROM has been there for well over a year with no problems.

Finding the root cause of battery drain...
deanbilly said:
In the last week or so I have picked up my phone three times and it has been dead.
Click to expand...
Click to collapse
There are a number of standard steps to run through to find the root cause of battery problems, assuming the drain is caused by the OS or apps and not actually due to a physically failing battery.
I have been tracking a few battery issues myself recently and this is what I have learned from doing some reading on XDA:
There are two free apps on the app market that are typically used to diagnose battery problems:
Better Battery Stats
CPU Spy
I would recommend installing both apps. The third place to look is in the battery details in the system settings...sorry I can't remember what they look like on Gingerbread because upgraded to Jelly Bean a couple months ago, though I do remember there was less information in the stock battery info on Gingerbread.
IF you are not, indeed dealing with a physically dead battery, then the root of your battery drain is most likely caused by a background process or app that is keeping the processor in a partially active state even though the screen is turned off and one would assume the phone should not be using any power.
Android OS will automatically change the running speed of the processor in the phone based on the demand of the system. If only a few background tasks are running and updating information the speed might be 200 or 400 Mhz. If the system is running full out servicing a graphic intensive game the processor will likely be running at the full 1000 MHz speed. The speed of the processor will directly effect the battery drain.
The expectation is that when we turn the display off (not power down, just put the phone to sleep) the processor should need fewer resources and slow down, tending towards a state known as "Deep Sleep". At this point the processor us using very minimal amounts of power. Any app or process that is active in the background will prevent the processor from getting to Deep Sleep. The CPU spy app will allow you to check how much time the phone runs at various speeds. Once you install it and run it, then reset the timers in the menu and turn your screen off for about 10 or 15 minutes. Then 'refresh' the timers. Normally, you should see most of the time accumulated in Deep Sleep. There are standard background tasks such as syncing with the cell tower, updating time, mail, checking alarms etc. That will engage the processor momentarily but they should be relatively short compared to the deep sleep time. In my case, an errand process was keeping my phone at 100Mhz constantly preventing deep sleep.
Once you know that something is keeping the phone awake in the background, you can use Better Battery Stats to narrow down which process or app it is the cause. This app allows you to track the individual processes that are consuming the most time and preventing 'wakelocks'. Wakelocks are essentially an app preventing the sleep state and are very well explained in this post: http://forum.xda-developers.com/showthread.php?t=1827676
The battery info in the system settings can also be used to give clues though again, I can't remember how much detail was included in Gingerbread..
If your problem only started happening recently, then it could be a new app that you installed recently, a feature or setting you changed recently or possibly a recent update to an app that was already installed. Try to think back at any recent events that could have triggered a change in the system.
Common problem apps I have read about are:
- Facebook - seems to be bad at using lots of background processor time. (Don't run this app but reading several posts shows its a processor hog)
- Google Apps that sync - Gmail, Chrome (syncs browser history, tabs etc.), Google location stats.
The wakelocks link goes into a great deal of detail and is hugely valuable in nailing your issue down.
Good Luck, let use know via a post if you find the root cause...

Sorry, maybe I wasn't clear about it being 'dead'.
The battery is 100% or thereabouts, no problems ever with the battery.
The phone looked as though it was turned off, but wouldn't turn on again with the power button.
I have to take the battery out and put it back again, then it starts on the button.
I've cleaned the contacts, and it still happened.

User error.
Sent from my GT-I9100 using xda app-developers app

To me, it sounds more like a rogue process messing up power managing or response, but it's hard to tell what it could actually be.
For instance, you might come a cross a game that leaves your phone locked in max cpu frequency, draining the battery without explanation.
If it was me, I'd re-flash the rom from Odin, perhaps with an sd card wipe too.
Sent from horseback.

[Q] Nexus 6 Overheating issue

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.

Phone Whirring and then Shut Off

Hello Everyone! My phone has been wonky and I gotta know why
SO my N6 likes to shut off in the middle of doing something, most notably using google maps and the camera, I did some searching and someone suggested its related to the phone using apps that require location (Google Maps GPS / Google Camera Save Location Option), but there wasn't much input on that thread. Have any of you encountered anything like this yourselves? My phone would whir after opening Maps or after taking a picture from Camera (the whir sounds like its coming from near the top part of the phone btw) and then it would shut off, anyone have any clues as to what's the problem?

Yup same here for a long time. It's not related to location.
It's definitely something with voltage and battery.
I'm compiling my kernel and I've tried many things.
1/ Bcl needs to be on.
2/It's happening only on high cpu load. And so with camera and gps active.
Because those will use more voltage from our poor Motorola battery.
Using os monitor I've see my battery go to 3800mv from 3500 without big problem but clearly below 3600 there's a chance for the phone to shut down as you describe the thing.
Bcl start limiting and hotpluging core when battery reach 3800mv.
The default value is 1.9 ghz
But on stock kernel the phone is limited at 1.7. I think it's mpdecision and/or thermal that doing this. But I'm not sure.
Anyway nexus 6 is not made to handle 4 cores at the same time on low battery. + camera gps Bluetooth etc...
So voltage can drop to 3800mv to 3600 and then go back to 3800 because there's voltage work on kernel and rom side to prevent those things.
For exemple I've see my phone after unlocking it. Coming back to home. Have 3500mv and then after one minute. Come back to 3700.
So maybe WiFi and cpu was using the maximum voltage they could to sync then when job was over. Go back to a normal voltage use.
Not every phone are affected.
Cpu binning level is important i think.
Mine is 7.
0 use the maximum voltage and 15 the minimum.
I've use a pvs 5 phone and problem was the same with my kernel. So I've changed some stuff and it worked.
So for me my battery is bugged. I mean on low mv battery send bad info and doesn't have enough juice.
I've try rma my phone but Google send me a refurbish phone (the pvs5 one) which have screen burning on it. Yes they send me phone with a navbar stuck....
So I've send them back and I'm planning to change the battery myself
In the hope it solve the problem.
Also my turbo charger make a weird noise when phone battery is full. So maybe my charger have always be bugged and broke the battery in some way.
I'm still trying to understand this. But it's what I've test and understand from this. More or less because I've probably forgot something in there

dynamo147 said:
Hello Everyone! My phone has been wonky and I gotta know why
SO my N6 likes to shut off in the middle of doing something, most notably using google maps and the camera, I did some searching and someone suggested its related to the phone using apps that require location (Google Maps GPS / Google Camera Save Location Option), but there wasn't much input on that thread. Have any of you encountered anything like this yourselves? My phone would whir after opening Maps or after taking a picture from Camera (the whir sounds like its coming from near the top part of the phone btw) and then it would shut off, anyone have any clues as to what's the problem?
Click to expand...
Click to collapse
You can try https://drive.google.com/open?id=0BwCC2VJYgCavbHEwMk9CSFR4Snc
this is the version of my kernel i use (it says beta because it's not yet release, don't worry it will not break anything)
Make a backup of /system /data /cache /boot through twrp and flash the zip file
default settings will normaly make your phone not shut off. i've just go into 29% without problem
i can ear a noise from top speaker sometimes but i just stop touching the phone and it go back to normal.
Like i said above i still think a need a new battery
also i've see some users report a same problem on 6p after nougat update maybe we're on something

Weird Battery Behavior

I received my Xiaomi Mi 9 yesterday and after setting everything up I started to notice a fast battery drain, even when the screen is off, which I found to be quite weird for this phone.
When I restarted the device however, my battery percentage was back up again. It somehow went from being at 15% to being back at 73% after the reboot!
I am very confused about this, and I have no clue what could be causing this.
So far I've tried to do a factory reset, which didn't seem to help however. I've turned off WiFi, GPS, Sync and I pulled out my SIM Card and left it sitting, screen off, with occasional checks, but still the same drain.
What's even weirder about this is that the drain seems to be constant. I included a screenshot of the battery history graph, where it is visible that the battery "drains" at the same exact speed every time. Every time you see a spike upwards, that is me rebooting the phone. You can also see that WiFi (and also GPS and SIM Card) was turned off at some point, but that didn't affect the drain at all.
The phone isn't running hot or anything either, it's literally doing nothing, just sitting there draining.
I've let it drain down to 0%, at which point it just turned off. I could immediately start it again and it was back at 66%.
MIUI's battery analyzer thingy does also not have any recommendations as to what to do, except "turn on battery saver", which it says only gains 8 minutes.
I'm running the latest update that I could get through the updater in the settings (MIUI Global 10.2.17.0).
I'm really at a loss here as to how to fix this, or even pinpoint what could be causing this. I would've blamed I faulty battery in my unit, but it kind of seems to be more of a software issue? I really don't know.

It seems that a hardware fault (BSI) rather than a software issue
Cause no one report such a problem with this phone

Do you have any idea which part of the hardware could be causing this?

I said bsi or battery
But refer to warranty for replacement

emprazol said:
It seems that a hardware fault (BSI) rather than a software issue
Cause no one report such a problem with this phone
Click to expand...
Click to collapse
But yes.
https://c.mi.com/thread-1891092-1-0.html
Some people helped now flash FW:
https://miblog.co/mi-9-eea-stable-10-2-17-0/