I was wondering if the heat procuded by the TP2 while in android was because of the processor or because the phone is reading from the MicroSD card at all times?
I'm thinking it's the latter, and when we finally get a flashable version the heat issues will dissapear
Thoughts?
The device gets hot while in Android because proper power-management is not completely implemented yet, and the processor works harder than it needs to, heating up the device quickly. This will probably get fixed over time, and long before we ever get a flashable NAND build.
Related
I thought I'd put this together given the amount of questions and apparent lack of knowledge on what you're getting yourself into with overclocking. While it's a one-click-wonder with SetCPU and JuiceDefender, it's not that simple when it comes to what it's actually doing to the phone.
The first thing you need to know is this:
All devices are not created equal!
Even when they come off the production line together they may not be capable of even getting close to each other with an overclock. This is down to numerous variables, the most important of which is the processor itself. Processors are manufactured in batches from something called a wafer (basically a big chunk of silicon), that batch is then tested to a maximum stable speed and then marketed at a slightly lower speed for the sake of rock solid stability. Dual/multicore processors may have a faulty core disabled and be marketed as something else (hence AMD's Tri-Core processors). This is the reason overclocking works, and the long and the short of it is just because Person A can get 1.3Ghz running stable, doesn't mean Person B can.
So, now we know that whingeing that my Desire can get 1300Mhz but yours crashes every time you go above 1100Mhz is irrelevant, we can move on to the risks. Overclocking is dangerous. That's not an exaggeration, so let me reiterate...
Overclocking is dangerous, You can potentially kill your phone stone dead.
But yet again it's not that simple. Yes, in very rare cases a processor will just go bang and give up, but most of the time other things will happen, behind the scenes, that you won't know about until it's too late.
The basic premise of overclocking is to get a faster processor clock speed. A small jump can probably be attained just by upping the speed itself and be perfectly stable. Going higher is where the problems start. If you start getting crashes/freezes/reboots then the next step is to increase the voltage to the processor to make it more stable, but more voltage means more heat, and excess heat is bad. This can either cook the processor as a whole or a group of transistors. This is more of a problem on a device like the Desire as where do you put the extra cooling?
Another problem is that more voltage can fry an IC track, and/or arc across to a track it shouldn't be on. This could do nothing, but it could also kill a single transistor on the processor or other chips in the device, or maybe multiple transistors and it can also lock them open or closed. This takes us back to random reboots, freezes, and crashes - but this time it can't be fixed.
Then theres a twist. Undervolting can also break things. A transistor is either on or off, and if it doesn't get enough power one of three things can happen - it can work fine, it can not work at all, or it can continually switch until it breaks (what an example? go and flick a light switch on and off until it stops - and it might not be the bulb that goes). If it decides not to work when other parts think it should, guess what happens.
So, bear this in mind when overclocking. If you start getting ANY issues test at stock speed. If you still have issues and/or you kill your phone, it's your own fault.
Mods - I've put this here as it's the place most people seem to ask about OCing, please move it if i'm wrong...
Nicely written and informative. Users must always take their own responsibility when trying to do something "out-of-spec" with their device. I didn't know undervolting could break things though.
It's far far less common and it's not the actual undervolting that causes the issue - it's the power requirements of the device. If you're unfortunate enough to have something keep tripping - it's kind of like when a PSU goes and keeps clicking, there's not quite enough power to flick to On permanently so it just ticks at you till you turn it off or it gives up completely. 9 times out of 10 you'd be fine, but theres always that chance.
Very Nice,
I got a question tough,
I experienced a lot of freezes everytime I flash a AOSP-ROM......
Even if I don't overclock.........I have to pull my battery out every time...
With sense-roms I don't get this problem..........
So my question is, Am I so unlucky that my device just can't handle the different kernels? or am I doing something wrong???
Hope someone can give me a helpfull answer
toosif said:
Very Nice,
I got a question tough,
I experienced a lot of freezes everytime I flash a AOSP-ROM......
Even if I don't overclock.........I have to pull my battery out every time...
With sense-roms I don't get this problem..........
So my question is, Am I so unlucky that my device just can't handle the different kernels? or am I doing something wrong???
Hope someone can give me a helpfull answer
Click to expand...
Click to collapse
My phone freezed several times a day with defrost. But no freez with MIUI/OpenDesire. I dont know why but Defrost §$%#s my phone
toosif said:
Very Nice,
I got a question tough,
I experienced a lot of freezes everytime I flash a AOSP-ROM......
Even if I don't overclock.........I have to pull my battery out every time...
With sense-roms I don't get this problem..........
So my question is, Am I so unlucky that my device just can't handle the different kernels? or am I doing something wrong???
Hope someone can give me a helpfull answer
Click to expand...
Click to collapse
It can be that it is your ext3 partition if you have one...i had a user with freezes...and i did not know what it was...i say him...make all new...he flasht a original rom...root again with unrevoked...flasht my rom again and it was the same...freezes...so he formated the card...and maked a new ext3 and now he have no more problems with freezes
with kind regards..Alex
Good write up. Hopefully people will actually read this and understand the risks before they start pushing zip files with overclocked/undervolted kernels. Personally I've never overclocked any mobile device since I'm not comfortable with the risks that may lead to long term damages.
great job! thumbs up! vote for sticky or linking this in one of the stickys
i'm familiar with overclocking since i've been doing it to my PCs for years. i'm wondering if aosp roms push the phone harder or something than sense based ones?
reason i ask is i've tried a few aosp roms (open desire, defrost etc) and all the various kernels i've tried cause a reboot after a while - 30 mins, upto a few hours. now, i tried richard trips sense kernel and OCd with that no problems at all. very weird
p,s all Ocing was on the relatively small 1113mhz.
I just got this tablet yesterday, used off of eBay.
So far, it seems whenever I try playing a game the tablet overheats and even in general use I can feel that it's a bit too hot for comfort.
The previous owner tripped the KNOX flag already so I assume that means the warranty has been voided. So unless there's a way to reset that counter I think repairs will cost a fair bit.
What can I do? eBay is very flexible with refunds and the buyer has all the power when the item has an issue (even though the item listing stated no refunds) but I'd like to fix the tablet without having to get a refund if possible.
Any ideas on how I might fix this overheating problem?
The tablet is on 4.4.2 btw.
Mine is brand new and have 4.4 already. Not rooted, all stock.
Tablet gets hot on the back, to the right of the camera lens, even when not playing games.
I think its the device. Poor heat management.
lanwarrior said:
Mine is brand new and have 4.4 already. Not rooted, all stock.
Tablet gets hot on the back, to the right of the camera lens, even when not playing games.
I think its the device. Poor heat management.
Click to expand...
Click to collapse
So this is perfectly normal? Damn..Never had any other electronics that heated up like this before so it makes me concerned since I keep hearing about exploding Samsung products lol
I had the same problem, so I went ahead and installed the xKat custom Rom and the problem is basically fixed. Only heats up when I do multiwindow stuff with video or playing intense games.
xRift said:
So this is perfectly normal? Damn..Never had any other electronics that heated up like this before so it makes me concerned since I keep hearing about exploding Samsung products lol
Click to expand...
Click to collapse
I think it's just how Samsung phone/tablets are designed. I also have a Note 3 and it gets hot also on the backside, near where the camera is. The temperature can reach about 36 degrees celcius, but so far has not caused any issue. I don't know about battery life though.
You can root and install custom ROM, but I really try not too because rooting Wifi version of this tablet will trip KNOX and I got tired of installing numerous ROM to find the right one that has the most minimal number of problems.
Since your rooted just fine a good CPU app that controls the speed.
This heating issue is most likely due to the Index Services process and S-Finder app trying to index the sd card (I'm assuming you're using a microSD card, but the issue may happen on the device storage as well)
It's been widely reported that with the Kit Kat update apparently this process gets "stuck" trying to index pdf files and causes the processor to overheat.
Try (again, assuming you're rooted) greenifying or freezing with TB these and check your results, worked for me.
scarmona said:
This heating issue is most likely due to the Index Services process and S-Finder app trying to index the sd card (I'm assuming you're using a microSD card, but the issue may happen on the device storage as well)
It's been widely reported that with the Kit Kat update apparently this process gets "stuck" trying to index pdf files and causes the processor to overheat.
Try (again, assuming you're rooted) greenifying or freezing with TB these and check your results, worked for me.
Click to expand...
Click to collapse
what app should i greenifying , i am not rooted and this problem start with me suddenly 2 days ago ?
I got a cheap no-brand Chinese smartphone. We shall gloss over the wisdom of this purchase, but suffice it to say it turns out it isn't the MTK6582 quadcore with a gig of RAM that was promised. A quick peek in the options revealed a Spreadtrum SC8825 dualcore and 512 megs of RAM running 4.0.3 ICS. This was confirmed by other sources. Long story short I got another phone that's now my main one, but the Chinese one was so cheap that I took the loss as a life lesson and didn't even bother sending it back to Hong Kong, figuring a backup crappy phone is better than no backup at all.
I therefore decided to decrapify the cheapie as much as possible. I found a mention in dx's forum of a newer, better ROM for it with less crap, so I downloaded it and flashed it. Proving that I apparently can't make a good decision about this thing at all, what I now have is a phone whose settings show a "MT6582" CPU that reports itself as having four cores, plus a ludicrous 1.5GB of RAM and running Android 4.2.2. Weird thing is, the apps do in fact see this - for instance, Antutu does report four cores and all that RAM, and other benchmark apps do as well - though two of the cores are mysteriously always inactive. I know that the CPU and RAM are wrong, and I suspect the Android version is faked as well. I suspect this is what's causing some apps to misbehave; they expect specs that aren't there, and freak out and crash as a result.
Thing is, because it was showing the correct specs before the ROM flash, I know for a fact that whatever fakery is going on is exclusively at a software level. I don't know if Android does any checking on the hardware or if it just displays what the ROM's reporting, but either the checks are being bypassed or the ROM is simply reporting the wrong data.
Edit: tried cat /proc/cpuinfo in adb and got this, which shows the fakery to extend there as well.
Which brings the question: having rooted the phone and being able to access it via adb, where in the system partition do I go looking for the fakery so as to get rid of it and have, at least, a phone that reports itself as what it actually is?
Bumpy bump.
I'm on Android 13 and was hoping this would sort out the overheating problem I had with Android 12 (I read in a few places that it would), but it did not. The phone gets very warm when charging, and hot when streaming video, and just generally through simple use, nothing particularly demanding. I haven't rooted this phone because I did not see the need, but I would consider it if it was the only way to fix the problem. Is anyone experiencing the same, and does anyone have a solution?
I could be wrong but generally speaking in my experience, going from one major upgrade to another the phone works a bit harder to re-train itself to your use patterns. I just did my upgrade yesterday and experienced some slight to moderate heat as well. I also noticed that battery is draining a bit faster which I think again is part of the process. I'm going to give it a week or so and if I'm right it should improve.
I'm biased because I've had my Pixel 6 Pro rooted (and updated every month) since last November, and I also use Kirisakura custom kernel with its companion apps and currently have the one app set to the maximum battery savings.
So I can't really compare to 100% stock unrooted with the stock kernel, as I'm only briefly on the stock unrooted kernel each month after I manually flash the latest update.
Several others have commented, and I've experienced too, that with Android 13, we've no longer experienced as severe higher temperatures when charging. I don't remember if the others were rooted and using the same custom kernel, or if these were general Android 13 comments, so your mileage may vary. Sorry I can't give you any more concrete information.
Good luck!
Granted this is for my 4a5g but I wouln't be suprised if/when I get a 6 that its battery performance would be less than stellar after a good days use of phone and/or screen and radio/network. i.e. stock. Before I went to Lineage on my 4a5g I think my battery would cut a good 30-50+ percent each day. I put lineage on it and I poop you not, can go from a 75% to around 20% in about 5-6+ days. I tend to have my screen brightness around a little less than 1/4th on the slider bar.
When I had an HTC M8, after around 2 or so years (this was around 2016/7 or so. got phone oct '14) on the stock firmware the phone couln't keep it on for more than a day. Ran ViperRom for a bit then switched to cm/lineage and that stretched my usability of the phone another 5 years. It got to the point where the phone would shut off when it got to around %50 charge and go ding dong and turn off--without pluggin it in I had about 8 hours run time on it. My battery was beyond gone and no way would I have gotten that usability on the stock rom.
So, to answer your question, yes, trying different roms and kernels (rooting) could be to your advantage to prolong the life and performance of your phone.
Even if you choose to run the stock OS, with root, you could disble any bloat running in background. Kill any programs/services leeching CPU (and hence battery) cycles. You could definately make it run more efficient for YOU. Maybe not for the next guy who needs his facebook, twitter, ticktok apis and stuff loaded and at the ready. Everyone is different. But they tend to make the phones (they think) for everyone. in mind and as a result, device performance and lifespan become affected.
I definitely have heating issues and this is on a warranty exchange. The 2 previous P6Ps had all the same issues as this current device.
My phone was hot on A12 (41/45°) and since i clean flashed A13 and wiped it is cold (32/35°) for the same usage.
Greetings.
Good topic.
I have bought this phone a day before. I'm facing device heating even under simple tasks like scrolling messengers, browsing etc.
Previously I had OnePlus 7 Pro (Snapdragon 855), that one was cold all time except while charging or playing games.
However, Pixel looks warm or even hot even upon light using.
I'm a bit confused about that.
Is it a common problem of this device? Or probably exactly my device is affected?
I haven't faced overheating or alerts about that, however, it feels hot for my hands that got used to feel a cold phone while low load.
Currently, I have about 37-38 degrees while browsing on XDA and writing this post.
Just wondering that digits you have?
I did a warranty exchange on my P6P for a different issue and I'm glad I did. My replacement device has much better thermals than my original. My original one would get quite hot while charging and restoring apps and was almost uncomfortable to hold and to the touch. Could always try a warranty exchange and see if the replacement device is better for you. Also, Kiri kernel has been reported to help with the thermals. I've seen several reports of users commenting that their device runs cooler. Good luck!
I had heating issues and battery issues when I first received my P6P. Once I got it out of the box, I set it up and restored backups, rooted it, updated to android 13 without wiping, rooted again, and then flashed the Kirisakura kernel. I decided to try and flash android 13 again but keeping the -w flag to wipe userdata and didnt restore my backups and I've had amazing battery life and no overheating. If you haven't yet, try doing a factory reset. As simple as it sounds it may very well help
My fully stock P6P (on A12) gave an overheat warning yesterday while we were having a day out, it was only 22°C although we were in and out of the sun as the clouds rolled by but the phone was showing 46°C after being sat in my pocket.
I think Google have released the worlds hottest running phone, i have never owned a phone that heats up so much and so fast.
MrBelter said:
I think Google have released the worlds hottest running phone, i have never owned a phone that heats up so much and so fast.
Click to expand...
Click to collapse
Try OnePlus 9 Pro
darkness4every1 said:
Try OnePlus 9 Pro
Click to expand...
Click to collapse
Thing is I have never experienced overheating on any phone (that i have owned) in UK before, using an Exynos as the basis of Tensor and then whacking an extra big core in it was a pretty bad idea unless you live in a fridge.
If you're like me and only intended to change the battery in order to keep it going for a bit longer or bought it 2nd hand then think again. There's a high likelyhood of it having a bad wifi chip in both the S8 and S9 which'll drain the battery like crazy if you have the Exynos variant. And this can easily be tested by just downloading something heavy and turning off wifi to see battery usage drop from 3-6W down to <400mW with something like Accubattery or your fav battery monitoring tool (i.e EX KM or whathaveyou).
I thought I was crazy at first since the CPU was maxing out (or close to) for no apparent reason when I was just refreshing my reading app, but it turns out it's the WiFi IC that is at fault. It didn't go bad during my first 2 years but around 2021 I started having issues so I switched my DD to my XZ2 and only kept my S9 as a backup unit.
Now obviously the other telltale sign is that the phone will overheat and drain the battery rather fast which I always thought was just the Exynos being Exynos but it's actually the Wifi chip. I got an Xperia XZ1/2 as well were the WiFI IC is part of the SOC so there's no actual issue there since Qualcomm make their own chips for everything more or less. If you've ever had a Broadcom moment then you know what you're up against.
I feel sad for letting this device go since it was my fav phone for so long but it's finally time to say goodbye since RAM has become the next issue on my list.
Does it happen in safe mode?
Guess you already tried a network reset and clearing the system cache?
It happens regardless of what I do but it's not the first time I've had issues like these. And anyone with broadcom experience will know exactly what I'm talking about.