Related
MIT student proves by A + B that T-Mobile G2x has hardware issues related to overheating / shutdown / battery
http://www.lgforum.com/forum/boards/carriers/t-mobile/topics/g2x-g2x-gingerbread-2-dot-3-3-shutdown-requiring-battery-pull-due-to-overheat
Let's share this and be social.
Here are some other references for this same post.
#OccupyLg
LG: http://www.lgforum.com/forum/boards/carriers/t-mobile/topics/g2x-g2x-gingerbread-2-dot-3-3-shutdown-requiring-battery-pull-due-to-overheat
XDA-Developers: http://forum.xda-developers.com/showthread.php?t=1433445
T-Mobile: http://support.t-mobile.com/thread/16431
I would assume a hot reboot would work as well if you don't want to install an app killer
Sent from my LG-P999 using xda premium
If you are having issues you need to post more info. Rom? Kernel? Certain apps can cause issues. If you need help ask. Posting a rumor by a "MIT" kid is not overly impressive to me. Egg heads over think things sometimes.
jcbofkc said:
If you are having issues you need to post more info. Rom? Kernel? Certain apps can cause issues. If you need help ask. Posting a rumor by a "MIT" kid is not overly impressive to me. Egg heads over think things sometimes.
Click to expand...
Click to collapse
RG2X with Faux .47 and on .48 kernal. I am getting exactly what the IT guy described. Overheating during deep sleep while on charger. Non-OC'd with nothing major running in the background. Not even Setcpu or Juice Defender. I will assume this guy isn't on RG2X's rom nor on a MIUI rom. Maybe on Faux but I think it would be better to assume he is probably on 2.3.3/4 stock. Also he stated it was on two different phones that he did both of these tests we can assume it's not a rare thing. Noted it's not with every phone this happens but some for sure are getting dead phones upon wake. Because they die probably about half way during sleep by the time the person wakes up they only notice a dead phone that needs a battery pull. The heat is already gone so they wont notice the over heating. I actually felt my phone overheat on the charger so I can tell you what this guy is saying has some weight to it.
I shouldn't assume I should just read "We both a running stock lg g2x gingerbreads and have not tested it on any other roms"
psychoace said:
RG2X with Faux .47 and on .48 kernal. I am getting exactly what the IT guy described. Overheating during deep sleep while on charger. Non-OC'd with nothing major running in the background. Not even Setcpu or Juice Defender. I will assume this guy isn't on RG2X's rom nor on a MIUI rom. Maybe on Faux but I think it would be better to assume he is probably on 2.3.3/4 stock. Also he stated it was on two different phones that he did both of these tests we can assume it's not a rare thing. Noted it's not with every phone this happens but some for sure are getting dead phones upon wake. Because they die probably about half way during sleep by the time the person wakes up they only notice a dead phone that needs a battery pull. The heat is already gone so they wont notice the over heating. I actually felt my phone overheat on the charger so I can tell you what this guy is saying has some weight to it.
I shouldn't assume I should just read "We both a running stock lg g2x gingerbreads and have not tested it on any other roms"
Click to expand...
Click to collapse
If (big if) the overheating observed is due to heat from the battery charging leaching into the phone, wouldn't a quick and easy fix/test be a piece of aluminum foil between the battery and the phone?
Sent from my LG-P999 using Tapatalk
I have no problems at all. Running CM7 Latest Kang / Faux .48 CM battery. The last few versions of Faux's kernel fixed the SOD. I have never done an exchange. I got my G2X the 1st week it was out. I have never had any problems at all once the phone was rooted. Only thing I have problems with is the screen bleed. I am not OCed at all just UVed. When the phone screen is off setcpu sets the cpu at 389min 503 max. I have no overheating problems. So if you have overheating I would say that your phone is broke, you need to lower the OC if you are OCing, or you have done something wrong with the software.
Prod1702 said:
I have no problems at all. Running CM7 Latest Kang / Faux .48 CM battery. The last few versions of Faux's kernel fixed the SOD. I have never done an exchange. I got my G2X the 1st week it was out. I have never had any problems at all once the phone was rooted. Only thing I have problems with is the screen bleed. I am not OCed at all just UVed. When the phone screen is off setcpu sets the cpu at 389min 503 max. I have no overheating problems. So if you have overheating I would say that your phone is broke, you need to lower the OC if you are OCing, or you have done something wrong with the software.
Click to expand...
Click to collapse
Thanks for the report captain obvious.
I am glad your setup is fine. For those that are in stock configuration and non oc'ed yet experience these problems, they have probably come to realize that there is no support from tmobile or LG.
If the words "restart " or "shut down " during your tech support convo, you will be told to suck it up and wait for a software update. An update which will probably not come considering how many months has passed.
erikikaz said:
Thanks for the report captain obvious.
I am glad your setup is fine. For those that are in stock configuration and non oc'ed yet experience these problems, they have probably come to realize that there is no support from tmobile or LG.
If the words "restart " or "shut down " during your tech support convo, you will be told to suck it up and wait for a software update. An update which will probably not come considering how many months has passed.
Click to expand...
Click to collapse
FYI if it does it on all roms then its a hardware issue and software change wont fix it...
Sent from my LG-P999 using xda premium
I also had the dreaded sod at least once every couple of days.
However, after I installed eb kang with faux oc/uv profile with set cpu, I have had no problems since.
I guess its ymmv...
Sent from my LG-P999 using XDA App
No problems at all here with overheating or SOD. I have over 200 apps installed. And yes, I'm seriously still running stock Froyo.
The only problems I've had are sluggishness and freezing after disconnecting the USB (both computer and wall chargers.) I think it's an automatic sync thing, or possibly something reading my 10GB of music files on the SD.
Got mine the first week out too, but from Amazon.
gggirlgeek said:
No problems at all here with overheating or SOD. I have over 200 apps installed. And yes, I'm seriously still running stock Froyo.
The only problems I've had are sluggishness and freezing after disconnecting the USB (both computer and wall chargers.) I think it's an automatic sync thing, or possibly something reading my 10GB of music files on the SD.
Got mine the first week out too, but from Amazon.
Click to expand...
Click to collapse
I don't think anyone is saying this problem effects everyone. It's just with all the bad units out there with this problem, this is probably why it's happening. Right now I'm trying to run some profiles in setcpu to see if it improves my phones sleep. It's only been one day so I will see by the end of the week how this fares
Sent from my LG-P999 using xda premium
Cm7, morfic Trinity kernel, go launcher ex oc'ed to 1.4 ghz. Perfect! No issues!
Sent from my LG-P999 using xda premium
erikikaz said:
Thanks for the report captain obvious.
I am glad your setup is fine. For those that are in stock configuration and non oc'ed yet experience these problems, they have probably come to realize that there is no support from tmobile or LG.
If the words "restart " or "shut down " during your tech support convo, you will be told to suck it up and wait for a software update. An update which will probably not come considering how many months has passed.
Click to expand...
Click to collapse
Posts like this post is the reason why the devs hate the G2X. Most if not all problems most of the time are with android. If you are not using setcpu to control the cpu by setting up profiles for screen on and off. Then you are missing out on what root gives you access to. My phone might have the same problem yours have with overheating but i will never see if because my phone is UVed and runs at a lower CPU speed when the screen is off. If you want to use my setcpu profile look at my last post.
Prod1702 said:
Things like this post is the reason why the devs hate the G2X. Most if not all problems most of the time are with android. If you are not using setcpu to control the cpu by setting up profiles for screen on and off. Then you are missing out on what root gives you access to. My phone might have the same problem yours have with overheating but i will never see if because my phone is UVed and runs at a lower CPU speed when the screen is off. If you want to use my setcpu profile look at my last post.
Click to expand...
Click to collapse
The overheating is not a Android problem it's a LG doesn't know how to product test problem. All my other Android devices didn't have this problem. One did have an SOD problem that was fixed but I never had to deal with overheating. This is on LG not Google.
psychoace said:
The overheating is not a Android problem it's a LG doesn't know how to product test problem. All my other Android devices didn't have this problem. One did have an SOD problem that was fixed but I never had to deal with overheating. This is on LG not Google.
Click to expand...
Click to collapse
My friends amaze 4g has it friends Samsung fascinate has it galaxy s 4g and my old g1 and mt3g had it...
Sent from my LG-P999 using xda premium
mt3g said:
My friends amaze 4g has it friends Samsung fascinate has it galaxy s 4g and my old g1 and mt3g had it...
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I think the term overheating is thrown around too loosely here without more of a description. There's the type of overheating that causes our phones to shut off and stay off until the battery is pulled. There is also the type of overheating that occurs when you plug in an HDMI cable, which may or may not cause your device to die.
I'd assume those two types of overheating are the same, as they result in the same thing: dead device that won't turn on without a battery pull. And the phone gets hot as fsck. Hot as in you'd be scared to keep it in your pocket because (1) it'll burn your leg and (2) you are scared the battery will explode.
Those two types are overheating are different from your phone merely heating up upon use. I'm talking about charging the phone while navigating via GPS at full brightness or playing a graphically intense gaming. That magnitude of that heat is normal. And I'm guessing that's what all your devices have experienced.
And as all the devices get thinner, that battery's going to sit closer and closer to your hand, which equals more heat. And as the glass technology gets thinner (gorilla glass 2.0), your face will probably feel the heat to a greater degree as well.
---------- Post added at 04:18 PM ---------- Previous post was at 04:13 PM ----------
psychoace said:
The overheating is not a Android problem it's a LG doesn't know how to product test problem. All my other Android devices didn't have this problem. One did have an SOD problem that was fixed but I never had to deal with overheating. This is on LG not Google.
Click to expand...
Click to collapse
It's true, it's not android, it's LG.
And to all the people thinking that undervolting and underclocking your phone will fix everything, it won't. Android already underclocks the CPU when it's not in use. SetCPU does nothing in this instance. The only instance they'll see a difference is if they have some sort of rogue app that's maintaining a wake lock. You just can't beat terrible design (referring to the MIT guy's findings). Sometimes it'll work, sometimes you just lose.
LG majorly screwed up with this and I hope that their mobile efforts in the future fail for their lack of follow through.
I think I've avoided the charging SOD by accident....
I don't like the official LG charger since it uses a microUSB cable which I'd rather have as a spare on my computer..... so most of my charging is done with an old charger I just had laying around, which turns out to be 0.7a instead of 1.0a which the LG charger is, or on USB which goes through about 3 different hubs so probably has little power left by the time it gets to the phone.
Sure, charging is a bit slower, but that probably prevents some of the overheating.
Lesson: If you're having overheating during charging, dig through all your old chargers and find one with a lower output rating. Use the higher output ones only if you're in a hurry to charge.
Just wanted to say that this thread has been really helpful to me. Every time I've flashed a custom kernel, my phone has always, within the first 2 nights of installation, turned off in the middle of the night while on the charger. So I've always been stuck with the stock kernel. But then the suggestion to use SetCPU to lower the speed while the screen is turned off worked for me. So far no SOD and my phone has survived Faux's kernel and charging overnight without a battery pull and without overheating.
Now I can try out custom kernels and find all new ways to destroy my battery by doing things I'm not knowledgable enough to be doing!
lotherius said:
I think I've avoided the charging SOD by accident....
I don't like the official LG charger since it uses a microUSB cable which I'd rather have as a spare on my computer..... so most of my charging is done with an old charger I just had laying around, which turns out to be 0.7a instead of 1.0a which the LG charger is, or on USB which goes through about 3 different hubs so probably has little power left by the time it gets to the phone.
Sure, charging is a bit slower, but that probably prevents some of the overheating.
Lesson: If you're having overheating during charging, dig through all your old chargers and find one with a lower output rating. Use the higher output ones only if you're in a hurry to charge.
Click to expand...
Click to collapse
hmm.. I dont doubt you, but I think doing that would not be any different.
BECAUSE, the charger is not constantly charging at 1A rate. If you notice, the phones ramps down the input current after a certain percentage ~90%, and trickles it up to 100. Once at 100, the charging is supposed to be stopped. I've charged mine with my bluetooth 500ma charger, and I didnt see a difference in heat temps; only charging time took longer.
As far as heat, Lion batteries should be able to handle 1C charge (1 x charge capacity) with no problems in heat. That means even at 1.5A charge, it should be OK.
Regarding overclocking, undervolting and overheating. There is a variation of parameters across every silicon wafer; among the 25 or so wafers in a wafer lot; and from wafer lot to wafer lot. This is referred to as the "spread" and parts at the extremes are called "corner parts". Most parts should be in the middle of things, not all. With newer parts and small silicon process geometries, the margins are typically smaller - hopefully improving as the fab gets experience with the new process.
A hardware developer should get corner parts to check their PCBA layout and FW, to see if they have design margin. In the case of DDR (RAM), the voltage, circuit layout and DDR interface timing (from Tegra, in this case) should be checked across some tolerance and with the corner parts. "Fast" parts can draw more current during operation that nominal parts, possible heating up the voltage regulators nearby.
In a good hardware design, everything should work across part variation and the specified operating temperature for the system. When we start playing with the clocking frequency and voltages, there is the risk of FW crashing and HW flipping out. The symptoms can include system shut down (lost), resets, heating, bad effects on other systems (battery, voltage regulator circuits, etc.).
This is why some of us (like me) have little luck Set CPU and others can change it to extreme. What none of us know is how close to the design limits the G2X is - the system and the components like Tegra, the FW control. If due design diligence was not done, the sensitivity to part variation and our hacking is greater than normal.
This is my first Android phone (2nd device overall), I love it, it was my free upgrade option from AT&T, on number 2, the first, I completely bricked trying to upgrade to GB stock..... After I got the taste of flashing ROM's, thanks to TRusselo and his ninja skill, I find myself oriented towards the leaner ones because of memory issues, I run V6 Supercharger , SlimICS :victory:, with JRummy's ROM Toolbox Pro :good: (gotta support the kicka$$ apps), TB, blah blah blah.
My major complaint is that my Cap runs hot, I have OS Monitor on it because I got tired of not knowing the threshold. It bothers me that my phone gets over 110 degrees Fahrenheit , I've even had a brief history of random reboots I attribute to heat when I ran the ICSSGS 4.0.3 ROM (Awesome stuff, but once I bit into Slim, it was over). Is there a way to manage the heat or get a case for the phone that helps to manage the temperature? Or am I S.O.L unless I keep a frozen gel pack nearby?
BTW, first post, I surf the posts often and since I didn't see any questions about overheating for this particular Samsung model thought I'd give this a shot
My gets hot to I think it has to do with the kernel
Sent from my SGH-I897 using xda app-developers app
Mine runs really hot too, mine gf has a cappy and they run the same everything most of the time, but mine is the only one that gets stupid hot. Would love it to be fixed but I think its probably a manufacturing issue. Problem is it wears on the battery. 10-20 of use and you will burn your ear if you want to talk on the phone . The metal back certainly doesn't help either.
Primary reason why your cappy gets hot is because of overclocking if you're clock is high the process of the CPU is high and pay the price of higher battery consume. I'm on 1200 OC and it get's hot hen I'm playing HD games. I suggest that you stay on 1Ghz.
takeoutttt said:
Primary reason why your cappy gets hot is because of overclocking if you're clock is high the process of the CPU is high and pay the price of higher battery consume. I'm on 1200 OC and it get's hot hen I'm playing HD games. I suggest that you stay on 1Ghz.
Click to expand...
Click to collapse
I have the max set at 1Ghz, min 600Mhz, Performance, SIO, I'm sure the fact that the temperature outside being over 100 F doesn't help at al. I have overclocked it before and it started smoldering, not literally, just felt like it.
I've literally taken damp cloth's and set them underneath the phone on occasion to see if that will help, it definitely does, so does setting the gel ice pack under it, so I have found ways around it. I would probably only trade this phone for one of the S3's, but this phone has definitely earned the top place among my favorite devices all time. It's just as tough as a Blackberry, and easier to use than an iPhone.
That's why LOL, 600MHz minimum and 1000MHz max, with performance gov, that keeps it at max clock all the time XD take that off OMG...
b-eock said:
That's why LOL, 600MHz minimum and 1000MHz max, with performance gov, that keeps it at max clock all the time XD take that off OMG...
Click to expand...
Click to collapse
I'm still a NUB, lol, I don't deny it, but I'm all about learning the way of the Droid.... I added some of the Devil Helly Bean Add-On apk's into the Slim Bean, so I have my high points, just have the low ones just as often..
takeoutttt said:
Primary reason why your cappy gets hot is because of overclocking if you're clock is high the process of the CPU is high and pay the price of higher battery consume. I'm on 1200 OC and it get's hot hen I'm playing HD games. I suggest that you stay on 1Ghz.
Click to expand...
Click to collapse
I have never knowingly oc my phone, it would get hot on GB even before I rooted and went to cm. 10-20 mins of web browsing brings my temps up to about 41 C (106 f) I am pretty new to this, where to I check my clock settings?
I'm running helly bean nightly s
I have switched batteries with my gf cappy so I'm pretty sure its not a battery issue
Maybe a bad/defective battery is the cause of the problem since there is no overclockin...???
Sent from my SAMSUNG-SGH-I777 using xda premium
master2828 said:
I have never knowingly oc my phone, it would get hot on GB even before I rooted and went to cm. 10-20 mins of web browsing brings my temps up to about 41 C (106 f) I am pretty new to this, where to I check my clock settings?
I'm running helly bean nightly s
I have switched batteries with my gf cappy so I'm pretty sure its not a battery issue
Click to expand...
Click to collapse
With a metal back of cappy, it will easily heat up because it conducts heat in the metal. Based on my experience it is cause by the user usage depending on how high is the voltage/clock require of each app used to maintain it's smoothness and reached it's maximum clock. You can see your usage at Settings>Battery.
You can use CPU Spy or Voltage Control to see your OC and adjust it. You can check also in Settings> Performance >Processor.
---------- Post added at 02:36 AM ---------- Previous post was at 02:28 AM ----------
brttwilliams said:
I'm still a NUB, lol, I don't deny it, but I'm all about learning the way of the Droid.... I added some of the Devil Helly Bean Add-On apk's into the Slim Bean, so I have my high points, just have the low ones just as often..
Click to expand...
Click to collapse
Yeah, you'll learn in time, just try to search and read throughout the forums. I suggest that you lower your min to 100/200 and max to 1000/1200,
use smartassv2 and sio governor. This settings saves me some battery and to extent that still smooth, slick and good ui/gaming/app performance.
If you're on DEVIL KERNEL, go to recovery>devil>governor profile> tick SMOOTH.
brttwilliams said:
I'm still a NUB, lol, I don't deny it, but I'm all about learning the way of the Droid.... I added some of the Devil Helly Bean Add-On apk's into the Slim Bean, so I have my high points, just have the low ones just as often..
Click to expand...
Click to collapse
Wasn't doggin' you dude, Just letting you know that could be the cause of your problem. Awhile ago I might have flamed you, I have matured and get that not everyone reads (not this situation), and I have to get used to that. People make mistakes, I know I do even if I wanna act like I don't. I am just helping around here now since I have gotten as much knowledge as the some of the users that joined XDA and other hacking forums in the beginning because I was always searching to find out ways to do it on my own, asking for help with stuff that no one talked about. So I am glad that I was able to help you in a way, sorta.
b-eock said:
Wasn't doggin' you dude, Just letting you know that could be the cause of your problem. Awhile ago I might have flamed you, I have matured and get that not everyone reads (not this situation), and I have to get used to that. People make mistakes, I know I do even if I wanna act like I don't. I am just helping around here now since I have gotten as much knowledge as the some of the users that joined XDA and other hacking forums in the beginning because I was always searching to find out ways to do it on my own, asking for help with stuff that no one talked about. So I am glad that I was able to help you in a way, sorta.
Click to expand...
Click to collapse
Thank you both, b and takeout.... I know neither of you were doggin me, b-eock. I've been one of the behind the scenes types but I've seen a few of your posts, I know you know what you're talking about, I definitely appreciate the guidance. Truth be told, I know I'm still a nub here, but I know my way well enough, after you break something a few times, its only natural to pick up a few tricks along the way.
Yeah you'll learn something here just have the patience, experiment, test things out yourself to conclude and rather soon it'll be your hobby reading
And also help others out too.
Sent from my SGH-I897 using xda premium
my gets hot sometimes too. im on helly bean latest 08/08/12 version, also battery gets sucked down quick, barely get 8 hrs and i do virtually nothing. ics cm9 was great on battery.
VashTS said:
my gets hot sometimes too. im on helly bean latest 08/08/12 version, also battery gets sucked down quick, barely get 8 hrs and i do virtually nothing. ics cm9 was great on battery.
Click to expand...
Click to collapse
I know my battery is going quick on the SlimBean 2.0 ROM, but the heat issue still happens, I have noticed with my OS monitoring tool that it gets hotter if you have programs running constantly in background using up high CPU %. I was able to isolate a few of the programs as things I could remove, overall it does still run hot, but it's not as bad.
I use the free version of the OS Monitor on Play Store, you can set it to run under root and to autostart when the device is turned on.
Picked up an 1800 mah battery and my batty life is great! Going to bed with 40ish percent left
Haha, well let me know where you snagged that from
Sent from my SGH-I897 using xda premium
try Smartassv2 gov and change your min from 600 to 100, then note the temps, or run a log of them.
typically my phone runs about 35° C (95° F) and that is with an otterbox commuter case on the phone. When the gps is on in the car, I use a vent mount to keep it at 40° or less, and never have to take the case off.
I read that higher temps, example 45°, really shorten battery life, and you wiil only get 200 charge cycles instead of 500 from the battery.
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
brttwilliams said:
Haha, well let me know where you snagged that from
Sent from my SGH-I897 using xda premium
Click to expand...
Click to collapse
Amazon, was a great purchase, got an oem battery, there is a huge thread in the accessories section about the 1800 mah epic 4G battery that fits in the cappy
Only for i9505.
Hey guys!
I've been experimenting a lot with my S4 and I figured out why many games lag...
The reason is that my gpu clock drops from max clock I set, to 320mhz once the temperature reaches 68C!
Some may say, this doesn't happen because the gpu doesn't thermal throttle on the S4 like on the HTC One...
Well...I used performance governor which is supposed to keep the gpu clock to the max at all times, and guess what?
When the temperature reached 68C my gpu clock went down to 320mhz even with performance governor!
How is that possible...?
Performance governor can't throttle down!
Thermal throttling is to blame. (or something else, that doesn't care about governors? )
It's not a coincidence this happened at exactly 68C like before.
(If anyone wants to argue with me about this I'd appreciate if he/she doesn't spam my thread for the love of god and pm me.)
Anyway, enough with the prologue..
This was a royal pain in the ass for me because I almost regret selling my silky smooth S3.
After tons of random searching and messing with the system of my phone I found the solution!
Here it is!
Sell your S4!
Nah, I'm just joking!
It's a great phone.
Here's the real solution:
I set
/sys/devices/platform/kgsl-3d0.0/kgsl/kgsl-3d0/min_pwrlevel
to 0 out of curiosity, which controls the lowest power level, or clock, that the gpu will use.
By default it's set at 4.
Since max was already 0 which means it's the highest value I set min to 0 too, and guess what?
The gpu clock remained at my set max, 504mhz, all the time, even after 68C!
Tried three games I know this problem happened and all three worked at 504mhz!
(for pure information, it was Modern Combat 4, Gangstar, and Asphalt 8)
How can you try it?
I've attached two scripts, one that sets the value to 0 and uses max gpu frequency all the time and one that sets the value to 4 so that the gpu can use the lower clock states again!
For Script Manager Users, free
Use script manager as root to run these widgets and I'd recommend you put two widgets on the home screen!
One for the first script enabling this tweak, and one for the second that disables it.
For Tasker Users, need to pay
If you have tasker you could use it too and set it to run the content of the first script as root at every heavy game and enable the tweak automatically, after that use tasker again to run the content of the second script when you go to your home screen (or anything else you want to set) and disable the tweak automatically!
Beware!I will not responsible if you damage your hardware!
Recommended prerequisites:
- Custom kernel preferably ktoonsez's or ausdim's, but any kernel with undervolt and thermal throttling control support will do.
Increased heat may be produced after doing this, so I recommend you to undervolt at least a little to reduce the overall heat, plus increase the thermal throttling limits too to prevent the cpu throttling down.
I use 85 as start limit and 82 as stop limit but you don't have to use my values.
I just find them safe enough and high enough so that they don't interfere with my games.
Try it and report back, many games are way smoother now, at least for me.
I'll be waiting for your results!
Have a nice day guys!
P.S. If you need to tune even more your device, take a look at my personal settings found here:
http://forum.xda-developers.com/showpost.php?p=45103847&postcount=1106
The gaming profiles are set at 1242mhz min now, not 1458mhz like before, because the gpu clocks work properly now the cpu doesn't need that much boost to avoid lag.
And the gpu clock I use now is 504mhz instead of the stock 450mhz in the link.
That's it!
You said that the gpu clock remained at my set max, 504mhz, all the time, even after 68C, but you didn't say how hot it got.
Did it get hotter than that? I'm a bit wary of frying the board to squeeze out a few extra frames on my device, but that's just me.
Haw much does it take you to reach 68° ? I have the 9500 version and i didnt face that problem yet.. it s going warm but doesnt lag
Envoyé depuis mon GT-I9500 en utilisant Tapatalk 4
donalgodon said:
You said that the gpu clock remained at my set max, 504mhz, all the time, even after 68C, but you didn't say how hot it got.
Did it get hotter than that? I'm a bit wary of frying the board to squeeze out a few extra frames on my device, but that's just me.
Click to expand...
Click to collapse
You won't don't worry.
Both the cpu and gpu have a tolerance up to 100C, plus the system automatically shuts down before reaching critical high temperature.
For me it didn't get much hotter, only a few degrees.
You can monitor the frequencies and temperature with the Qualcomm Trepn Profiler which is an advanced free monitoring app for Qualcomm devices:
https://developer.qualcomm.com/mobile-development/performance-tools/trepn-profiler
or
you can use this app by senior member @rlorange which is much simpler and gets the job done just right:
http://forum.xda-developers.com/showpost.php?p=44953638&postcount=3547
3ayachi said:
Haw much does it take you to reach 68° ? I have the 9500 version and i didnt face that problem yet.. it s going warm but doesnt lag
Envoyé depuis mon GT-I9500 en utilisant Tapatalk 4
Click to expand...
Click to collapse
Sorry but this is not for the i9500, this is the first thing I wrote.
I don't even know if this happens on your device mate.
Anyway, it doesn't take much, play a heavy game for a few minutes an you'll reach 68C.
Updated link with my settings, now it's correct.
Sorry about that.
Is it possible to change this value without a reboot ? Like in a small app for example ?
Hey buddy...juz chk yu are having any thermald file under /system/etc...??
thanks mate!! It's working perfectly
So this won't work with a rooted s4 on stock rom and kernel?
If not I'm returning my phone. I played vice city today and the lag was terrible. I've only had this phone for two days and I'm dissatisfied with verizon and samsung for gimping it and then locking it down.
imo, companies advertising the power of their chips is false advertising when they set temperature throttle so low
crazysoccerman said:
So this won't work with a rooted s4 on stock rom and kernel?
If not I'm returning my phone. I played vice city today and the lag was terrible. I've only had this phone for two days and I'm dissatisfied with verizon and samsung for gimping it and then locking it down.
imo, companies advertising the power of their chips is false advertising when they set temperature throttle so low
Click to expand...
Click to collapse
No mate, I'm sorry.
But good news is Samsung WILL fix your phone no matter knox 0x0 or 0x1.
(confirmed)
So flash your device and try again!
I must agree, companies are full of crap when advertising their products, it's so furstrating!
This throttling issue happens with any device, including iDevices.
Bootloader is locked. Most likely forever.
Don't have MDK so I cant loki.
Even with safestrap (which doesn't work for my MJ7) you can't flash custom kernels.
This phone is going back :good:
I'm going back to my trusty gnex for now. It would probably play GTA better at s4 resolution because I overclocked it and disabled thermal throttling.
Maybe I'll get a g2 with loki support...
Either way, I would like to give a Linus Torvalds Salute™ to samsung and verizon.
Too bad. :/
Wait for some exynos device or anyone with custom cpu/gpu because qualcomm imho isn't good enough.
I got this to work on my s4. Are there similar settings I can modify to prevent cpu throttling?
Edit: cpu throttling settings exist. But it wasn't throttling... it was changing governer and minimum frequency.
I set the governer to performance with root explorer and it's working perfectly.
Thanks op for the location of the gpu settings. There was no way I would have found it without your post.
I've tested it (works fine) but I have the feeling that somehow the phone is too warm
crazysoccerman said:
I got this to work on my s4. Are there similar settings I can modify to prevent cpu throttling?
Edit: cpu throttling settings exist. But it wasn't throttling... it was changing governer and minimum frequency.
I set the governer to performance with root explorer and it's working perfectly.
Thanks op for the location of the gpu settings. There was no way I would have found it without your post.
Click to expand...
Click to collapse
btmz said:
I've tested it (works fine) but I have the feeling that somehow the phone is too warm
Click to expand...
Click to collapse
Glad it worked guys!
Well, the temperature will definitely increase because of the increased gpu clock speed, but as long as cpu throttling temp is <=85 you should be fine.
That's what I've been searching for all day, I knew this device can handle those games, but the random stuttering was painful.
It lowers the GPU to 128 MHz, I measured that when I played Apshalt 8 and got my TricksterMod set in background. When the game dropped massive FPS I switched to Trickster and saw that the GPU is running 128 MHz, shocking. Ktoon's kernel has a touch boost which works nicely but Asphalt 8 is a racing game that uses the sensors to steer and so I did not touch my screen so often and I need that.
You sir deserve a medal.
GlossGhost said:
That's what I've been searching for all day, I knew this device can handle those games, but the random stuttering was painful.
It lowers the GPU to 128 MHz, I measured that when I played Apshalt 8 and got my TricksterMod set in background. When the game dropped massive FPS I switched to Trickster and saw that the GPU is running 128 MHz, shocking. Ktoon's kernel has a touch boost which works nicely but Asphalt 8 is a racing game that uses the sensors to steer and so I did not touch my screen so often and I need that.
You sir deserve a medal.
Click to expand...
Click to collapse
Thanks man!
I knew something was off the minute I started playing modern combat 3 and saw the same performance as my S3.
I researched quite a bit and found this in the end.
I even got in an argument with a guy at ausdim's kernel thread about this because he was saying I was talking nonsense and he wanted proof in order to believe me.
Well, here it is.
nfsmw_gr said:
Thanks man!
I knew something was off the minute I started playing modern combat 3 and saw the same performance as my S3.
I researched quite a bit and found this in the end.
I even got in an argument with a guy at ausdim's kernel thread about this because he was saying I was talking nonsense and he wanted proof in order to believe me.
Well, here it is.
Click to expand...
Click to collapse
Ah, yeah no one can say to me that the games run buttery smooth without any modification.
A game does not run smooth on 128 MHz.
And all those amateur reboot your device and etc... They are complete nonsense.
I want ask a thing before flashing... Is this only an unlock and gpu scales the frequencies as it needs or I have always gpu freq at max on depending on what I'm doing? I hope this only unlock the max frequency otherwise became e battery drainer hack! Tell me guy!
From universe with my gs4 snapdragon powered!
will try it, nice work!
My HOX running on 4.2.2 Sense 5 stock rom is having heat issues i believe i dont know if its normal
PS default Kernel (still cant get Beastmode,god knows why)
i use "ondemand" as my governor and "noop" as my scheduler with set cpu
i also have trickster mod installed but i use it only for monitoring temp and on what frequency is the cpu running!
when its idle temp is temp of cpu is 35 degrees Celsius and battery 26 degrees Celsius
whenever I am using my phone for internet for benchmarks etc CPU is 40 degrees Celsius and battery is at around 32 degrees Celsius
the phone feels ok
but whenever i start any game no matter how simple it maybe (this applies for a wide spectrum of games ranging from * ball pool to demanding games like Asphalt 8) i notice my backside especially region around my camera getting warmer (now its not very hot but you can tell the difference)
at that time the reading shown is CPU is 45 degrees Celsius and battery becomes 36 degrees Celsius
PS the phone never restarts the game doesn't crash it runs smoothly
is it normal!?
i have read on web that lithium polymer batteries should be kept below 35 degrees Celsius for optimum life and performance
i dot have any background apps running whem i am gaming and the rise is observed in a few minutes or so i usually play a game for max 15 mins after that everything cools down!
this rise is also observed during taking back up through Twrp!
Those temps seem totally normal. Yes, higher temperatures are stressful to Li ion batteries, and hasten capacity loss. But to some extent, you need to try not to worry about it, and enjoy the phone for what it is.
While I don't game much, I do notice the phone getting warm while using Navigation, Netflix, etc. I've had my EVITA since just after release in May 2012, and I haven't noticed any loss in battery life.
redpoint73 said:
Those temps seem totally normal. Yes, higher temperatures are stressful to Li ion batteries, and hasten capacity loss. But to some extent, you need to try not to worry about it, and enjoy the phone for what it is.
While I don't game much, I do notice the phone getting warm while using Navigation, Netflix, etc. I've had my EVITA since just after release in May 2012, and I haven't noticed any loss in battery life.
Click to expand...
Click to collapse
you know the device very well and since u says its normal m glad
thanks u saved me i was thinking of what not like under volting and all those tweaks with the kernel!
Btw redpoint is i know the nature of ondemand governor but in my case it is either the max or min frequency it operates,so is it a good idea to switch over to powersave?
(and does our kernel support that)
redpoint73 said:
Those temps seem totally normal. Yes, higher temperatures are stressful to Li ion batteries, and hasten capacity loss. But to some extent, you need to try not to worry about it, and enjoy the phone for what it is.
While I don't game much, I do notice the phone getting warm while using Navigation, Netflix, etc. I've had my EVITA since just after release in May 2012, and I haven't noticed any loss in battery life.
Click to expand...
Click to collapse
you know the device very well and since u say its normal its gotta be,m glad :good:
thanks u saved me i was thinking of what not like under volting and all those tweaks with the kernel!
Btw redpoint is i know the nature of ondemand governor but in my case it is either the max or min frequency it operates,so is it a good idea to switch over to powersave?
(and does our kernel support that)
Sonone said:
Btw redpoint is i know the nature of ondemand governor but in my case it is either the max or min frequency it operates,so is it a good idea to switch over to powersave?
(and does our kernel support that)
Click to expand...
Click to collapse
Haven't used SetCPU in a while, but pretty sure if the option appears in SetCPU, its supported by the kernel. Depending on what kernel you have installed, more or less governor options will be visible.
Governor seems like a trial and error type of choice. It depends on how you use your phone, and not everyone will get the same results.
Lol those temps are nothing, I've had my battery up to 66° Celsius.
Sent from my Evita
timmaaa said:
Lol those temps are nothing, I've had my battery up to 66° Celsius.
Sent from my Evita
Click to expand...
Click to collapse
66° Celsius. seriously and that too the battery?
like is this normal?
besides the phone doesn't restart or get damaged?
Yep, 66° battery temp. That isn't a normal operating temperature though, that was while my phone was rendering a huge picsphere image from the Focal camera.
There are safeguards in place in case the phone does reach a temperature that would damage the phone. The phone will first warn you it's getting hot by flashing the led red and green, if it continues to heat up it will shut down.
Sent from my Evita
I have never encountered that good m in the safe zone!
Sent from my HTC One XL using XDA Premium 4 mobile app
Hi XDA Community. I use Trinity Kernel by Morfic and i was wondering if it is okay to have an Overclocked Nexus 5 and use the phone at a regular basis like a normal stock clock Nexus. I don't want My phone to just randomly explode because of overclocking it. One of the features the kernel has as said at his/her XDA thread is "Up to 2726MHz (higher clocks will vary from device to device)". Is that frequency trustworthy when just using the phone normally or is that a benchmark frequency?
MaLing15 said:
Hi XDA Community. I use Trinity Kernel by Morfic and i was wondering if it is okay to have an Overclocked Nexus 5 and use the phone at a regular basis like a normal stock clock Nexus. I don't want My phone to just randomly explode because of overclocking it. One of the features the kernel has as said at his/her XDA thread is "Up to 2726MHz (higher clocks will vary from device to device)". Is that frequency trustworthy when just using the phone normally or is that a benchmark frequency?
Click to expand...
Click to collapse
Don't overclock that high. 2419MHz at most. Overclocking too high will cause more heat and throttle earlier, only useful for a short benchmark such as HWBot Prime or Quadrant (Antutu takes longer and will overheat by the time it finishes). Trinity also supports up to 3014MHz, OP hasn't been updated.
MaLing15 said:
Hi XDA Community. I use Trinity Kernel by Morfic and i was wondering if it is okay to have an Overclocked Nexus 5 and use the phone at a regular basis like a normal stock clock Nexus. I don't want My phone to just randomly explode because of overclocking it. One of the features the kernel has as said at his/her XDA thread is "Up to 2726MHz (higher clocks will vary from device to device)". Is that frequency trustworthy when just using the phone normally or is that a benchmark frequency?
Click to expand...
Click to collapse
You don't want to push the phone too much I think the Nexus 5 runs at 2.3 GHz. 2.7 MAY not be too bad but honestly, the phone runs pretty smooth as is. What benefits are you looking for from overclocking?
Thanks guys for sharing your knowledge. You know.. To get the MOST out of the Phone while at the same time being Safe.
if you really wanted, the phone won't explode if you run it at 3015mhz either. the worst that will happen is that your phone won't be able to run that high, and will freeze and reboot.
and don't listen to all.. run your phone how YOU like. yes, it'll cause a little(not much) more heat, and will throttle a little earlier, but that's why people like me disable throttle, so that's a non issue. I run my phone at high CPU speeds all the time, and use 2880mhz high/300mhz low quite often. just because I feel like it, no other reason.
oh, I run trinity as well, and do all of Trinity's testing
MaLing15 said:
Thanks guys for sharing your knowledge. You know.. To get the MOST out of the Phone while at the same time being Safe.
Click to expand...
Click to collapse
It's just what @jsgraphicart said. You're not really getting more out of your phone by overclocking. It's not going to run smoother, and most games don't lag anyway so they probably won't run better. I think most people just do it for benchmarks or just to check if it can run on a certain clockspeed.
Also what @simms22 said. You can do it if you want to, but simply because you want to because as far as I know there aren't really any benefits.
Back in my Palm Pre days, we used to overclock that thing to 1GHz. The default setting was 500MHz. I think it was even pushed to 1.2GHz. And it ran fine. But back then, you could tell the difference between a little lag at 500MHz and smoothness at 1GHz. With this phone and how Android has gotten smoother with every update, it's kind of hard to see any difference when overclocking. It will be smooth regardless.
oh, benefits, not really. a little more speed, yes. bit I would never call it a benefit, unless the speed difference was drastic, and its not.
As mentioned, overclocking the CPU can actually turn out to run slower because of aggressive thermal throttling. You could disable or extend the thermal throttling, but 2.3Ghz is already plenty fast for today's mobile software so you won't notice any difference in day to day usage.
bblzd said:
As mentioned, overclocking the CPU can actually turn out to run slower because of aggressive thermal throttling. You could disable or extend the thermal throttling, but 2.3Ghz is already plenty fast for today's mobile software so you won't notice any difference in day to day usage.
Click to expand...
Click to collapse
Even if you run your phone at 2880MHz/3014MHz/whatever with thermal throttle off, you can't really do anything too intensive as it'll hit 105C and shutoff lol
Lethargy said:
Even if you run your phone at 2880MHz/3014MHz/whatever with thermal throttle off, you can't really do anything too intensive as it'll hit 105C and shutoff lol
Click to expand...
Click to collapse
actually, no, youre wrong. when you run your phone at 2880/300 or 3014/300, you phone will hardly scale up that high, sometimes it will. you wont see any real difference between those high cpu speeds and running it at 2265/300. and battery will be similar. the difference will be if you run it at 2880/2880 or 3014/3014. now i run my phone at 2880/300 very often, and you know i disable thermal throttle. yet, i see no difference in temperatures, except if im doing something thats very cpu intensive.
simms22 said:
actually, no, youre wrong. when you run your phone at 2880/300 or 3014/300, you phone will hardly scale up that high, sometimes it will. you wont see any real difference between those high cpu speeds and running it at 2265/300. and battery will be similar. the difference will be if you run it at 2880/2880 or 3014/3014. now i run my phone at 2880/300 very often, and you know i disable thermal throttle. yet, i see no difference in temperatures, except if im doing something thats very cpu intensive.
Click to expand...
Click to collapse
Ah true. But still, a bit easier to hit it if doing something intensive Not to mention it may be a little unstable on some devices
Lethargy said:
Ah true. But still, a bit easier to hit it if doing something intensive Not to mention it may be a little unstable on some devices
Click to expand...
Click to collapse
on some devices??? on most devices! anyways, stability is overrated
LOL...no explosions on XDA allowed!