Hi,
i've got an international D855 here. i've tweaked it a lot.
it's overclocked to 2.8ghz (777jon's kernel), and running ressurection remix rom.
i also increased thermal throttling not to act up until 80 degrees celcius.
i use synapse to change kernel settings and core clocks.
i use "cpu temperature" app to monitor everything about my cpu. including clock speed.
when i go ahead and set the minimum speed to 2.8 and the maximum to 2.8, and enable all cores and enable all cores to have boost at the same time. it works for everything.
but when i start antutu, and do a benchmark. "cpu temperature" tells me that while the benchmark was active, the clock speed ramps down for a short moment of the benchmark. but the temperature never got above 65 degrees celcius.
i cannot acces the 3845#*855# code for some reason. if i try to dial that in, and press call. nothing happens. so i cannot deactivate thermal throttling that way.
so my problem here is. i've locked the cpu clock to the maximum. i've also locked the gpu clock to maximum. it all works outside antutu. but when i start an antutu benchmark, halfway through it, the clock speed decreases. and that's weird because i've locked the clock speed, and thermal throttling shouldn't already act up.
can anyone help me with the issue of the clock speed going down?
if i need to give more information, ask please. this is my first post. so i'm also sorry if this is in the wrong forum
edit: i just noticed there's a q&a forum. i'll post my post there. but i don't know how to delete this one. i'm sorry.
Why would you want to fry your phone anyways?
i'm not trying to fry it. i'm a pc overclocker. on pc's i try to get the highest possible benchmark score. and i'm going to do that with phones too. i know the limits of a chip. and i want to push the chip to it's limit to get the highest score.
so far i'm at 50.3k on antutu. but my goal is to beat the galaxy note pro, or maybe the htc one m9.
so yeah, i do know the limits. i know my way around overclocking and cpu configurations. i'm coming from pc overclocking.
but i just can't figure out why it clocks down at a certain point while it's at decent temperatures.
So you want your LG G3 to become the strongest G3 in the universe? Super Prince G3.
Quit the Dragon Ball talk.
You will end up messing up CPU so it will stutter all over the system.
This isn't PC.
why are you making fun of me. i just like to do this stuff.
i bought this lg g3 just for overclocking. and if it breaks, i'm done.
it's not my daily driver or anything.
i'm just doing what i love doing. and that you're making fun of me, doesn't help.
edit: to add to that. i've broken enough pc cpu's. but because of that, i've learned my way around. and now i'm doing the same with phones.
im not saying i'm trying to break the phone. but i'm going as far as it can. and if it happens to break, i've learned from it.
Related
Sent from my PC36100 using XDA App
http://forum.xda-developers.com/forumdisplay.php?f=652
I've had my phone overclocked 15% for months now...I pre-ordered and picked it up on June 4th (the day they were released to the public) and it's never been replaced. I rooted it right away using the engineering hboot method, and I immediately went to a rooted stock rom with a kernel that'd allow overclocking the very first time I saw one posted on this forum. I've never been able to run it at anything higher than 1152 mhz, but I've also never had any stability issues at 1152 mhz. I also allow it to go as low as 128 mhz all the time.
Since then I've played with various roms, and various kernels, but the first thing I've done when changing any rom or kernel, is always set the min and max CPU speeds again, and decide which governor to use. I've also always played with the undervolting strategies, from static to HAVS, and I've always been able to get away with the most agressive stuff posted without any stability issues.
Your mileage may vary, but thats been my experience with an overclocked Evo. I will admit I can barely notice the performance difference from 998 mhz to 1152 mhz, but I actually notice a battery life improvement...get it done faster so the CPU can go back to idling at a low frequency as soon as possible mentality I guess.
please watch what you say here. its not going to get you any help to curse and swear at other members. last warning
@MikeOD, which governor and what governor parameters have you found to work best for you?
I think the whole overclock boils down to what you do with your phone. If nothing overly cpu intensive, then there's likely to be little gain in the amount of saved time.
I actually have mine under clocked at 921 Mhz (came that way in the rom initially). UI was fluid enough and everything still seemed to work well/responsive. I get slightly better battery life too. Noticeable in the rate the batt % declines during active tasks (web browsing).
Okay I have tried searching, but it is a bit hard from my phone, so I'm sorry if I missed a post answering this.
Does anyone know how low UV this phone normally goes? In miui I could go as low as it allowed (750?) at the slowest CPU setting, but I wonder how low others go. I know it differs from one phone to another, but still..
Sent from my HTC Vision using XDA App
Our phone can usually only go down to about 850 but what you'll have to do is test each voltage for each clock speed, so what you would do is set the voltage (TEMPORARILY!!! THIS IS VERY IMPORTANT!) then set your clock speed to be only this speed to see if it is stable. IE: Set ~200 to 850, set clock speed to only ~200 (whatever it is for miui kernel, they are all different by a little bit) and then go around the ROM and look for any HARD lockups (lockups that require a battery pull, lots of lag and lag spikes are to be expected) and then turn screen off for like 30 secs and back on to check it. Do this for all clock speeds (if you want to change them all) For the record, AFAIK if a clock speed has a certain voltage, all clock speeds below it will be stable at that voltage. Once you get up to ~700 MHz also test it with some video. This should work if you want to be SUPER thorough but make sure you always TEMP first (because if it cause's a hard lockup, that will cause major problems...) also do a nandroid first just in case.
For the record, undervolting can be risky, so I am not responsible if you cause damage, just giving you a means of doing it
The lowest I've gone was 750 and works perfect. I don't want to go any lower though, phone's still eating up 32maH with screen off.
Thanks for the explanation. I already know how it works though and I'm being super careful. I was more interested in finding out what settings others use. So what are you at at other CPU speeds?
I test stability with Stability Test (I think its called) and some benchmark apps. Then try different stuff like movies, flash (like in a browser, not flashing anything) and turning the screen on and off. With temp settings in oc/uv beater.
--------------------
Sent from my HTC Desire Z using XDA premium
Does anyone know what scenario causes the most voltage drain from the CPU? Playing HD video? Crunching numbers (pi?)? Shooting pigeons?
Hmm, let me rephrase that
Name the 3 best ways to test stability when tweaking undervoltage
theres an app i found yesterday to test the stability of my SG2 its call "stability test" just set your core at that fixed clock and let it go...i just let it run 3-4 times after that if its good then i move on, but sometimes i feel the phone sluggish, i just increase the voltage on that and its fine again.
too much voltage burn the thing/ kill the battery, not enough voltage it starting to freeze up.
Yes I know the app and it's great! But I'm playing around with my own little app project so I was interested in what everyone use to test stability. That would be +1 to number crunching so far
Although I am starting to feel like I'm talking to myself I'll still post my (hopefully stable) undervoltage results if anyone should be interested:
Code:
245760: 750
368640: 750
576000: 900
768000: 900
806400: 925
902400: 925
1017600: 975
1113600: 1000
1209600: 1050
1305600: 1100
1401600: 1150
1507200: 1225
1574400: 1300
I'm testing a small app I'm coding, to learn more about Android, so the numbers will probably change as I learn more and get better at coding and testing the stability of my phone.
Also please remember your phone is going to be different than mine, even if the hardware is exactly the same, so this is only a rough guide.
Sent from my HTC Desire Z using xda premium
How do you undervolt with the default CM7 kernel?
could anyone suggest a safe clock speed for the play? i want to get a bit more power from the stock 1ghz processor but i don't really want to overdo it
Honestly, clock speeds are phone specific. For example, my phone might do just fine at 1.5, but your phone may not be able to go past 1.3, so you need to find your safe zone yourself.
Get an app that handles overclocking, SetCPU, AnTuTu CPU Master, etc. I use Rom Toolbox Pro. Move your CPU one step up, then play around for a while. If your phone doesn't bug out, go ahead and try the next one, until it won't go any higher without bugging out.
Make sure you don't lock your speeds at boot until you're sure it's safe.
I wouldn't recommend going above 1.6ghz even if your phone supports higher frequencies. It tends to get hot quite quickly at such high frequencies, and could be detrimental to the battery
thank you for the advice... ill try to see how my phone reacts to different clock speeds... and not go over 1.6
seagheart89 said:
could anyone suggest a safe clock speed for the play? i want to get a bit more power from the stock 1ghz processor but i don't really want to overdo it
Click to expand...
Click to collapse
i usually use 1.6 or 1.8 i feel that you should never oc it to the max it is allowed.
Depends entirely on the 'yield' of each individual processor, most can run over 1ghz but some can't, so to be safe all processors are set to the lowest safe speed.
My XP is stable at 1.8ghz. 1.9ghz causes occasional reboots, 2.0ghz is an instant crash.
Remember your unit will only get warm if the CPU is being worked hard, if it's idle then it will stay cool even at higher clock speeds. Using a more active CPU governer such as 'smartass' or 'interactive' will keep clock speed down when not required.
Also remember you can't overclock on the stock kernel.
Same here, I accidently overclocked to 2Ghz, instant crash. But 1.6Ghz is fine, yet eats battery like it's the cookie monster on crack.
Well i have a phone, and in that forum members says that Overclock the cpu shorts the motherboard life, is that true? and for those who are using Overclock, do u really feel something diferent with the performance of the tablet? or do u see something wrong with Overclock? like random reeboots or makes the tablet hot? Im thinking in OC or not my tab, so i wanna see the experience from other members, thx in advance. :good:
Deshabilitado said:
Well i have a phone, and in that forum members says that Overclock the cpu shorts the motherboard life, is that true? and for those who are using Overclock, do u really feel something diferent with the performance of the tablet? or do u see something wrong with Overclock? like random reeboots or makes the tablet hot? Im thinking in OC or not my tab, so i wanna see the experience from other members, thx in advance. :good:
Click to expand...
Click to collapse
I cover this in the guide I wrote in general (which has been pushed down quite a ways) but anyways here goes another version.
Overclocking varies from device to device, even of the same model. Variances in tolerance is on a per chip basis, as long as they pass within a certain range they are sent out for production in devices. Overclocking in general is within means of the chip's abilities, if it isn't, you'll know it. Generally speaking, 1.4 GHz is perfectly fine on our devices. 1.5 GHz is also usually ok, but is the upper end of what the Tegra2 can usually tolerate. Few an go past 1.58 GHz, my old G2x's tegra2 could hit 1.7 GHz,but that's well beyond "normal" range.
Overclocking a device is the same as overclocking a PC, you need to be careful with it. Don't just ramp it to 65% overclock and expect it to run fine. Every chip is different. Do it in steps, and test each step before moving on. Test it in normal usage, test it in heavy usage, gaming, etc.
An overclocked device will certainly run hotter then normal, it's running faster, drawing more power, and that creates a hotter running core, no way around it. Keeping in mind there is no airflow in these things, that makes the biggest enemy to CPUs even more dangerous.Does it run so hot that it can shorten component life? Sure it can. Will you still have the device when it happens? I doubt it. Likely, we'll be on Tegra5 before it even begins to show signs of stress.
One of the nice things, though, is our CPUs range so much in speed according to load that just because your Max is 1.5 GHz, it doesn't always run there. Most times, it won't even be in the overclocked speeds. Does it run faster? Sure does. Benchmarks will raise nicely, and games that maybe got choppy before will smooth out, movies that couldn't play well will be fluid, the heavens will align, mankind will discover world peace and I'll win the lottery.
All that being said, I don't usually overclock, in fact I tend to underclock a little to 800MHz. Its usually sufficient to do normal tablet stuff, and I adjust the speed according to what I require. If my movie is lagging, I'll bump it up until it smooths out. Same for a game if it needs it.
In the end, its all personal choice, really. Just because you CAN overclock, doesn't mean you NEED to. IMO a well tuned governor will give as good a result as overclocking in normal usage, and a good I/O Scheduler will also help alot, without adding anymore heat or stress to your device.
TL;DNR:
Overclocking is fun. It causes more heat. It likely won't explode within the time you own it. Or your children. Your battery will suck.
thanks pio for the answer, thats what i needed to read, cuz usually when u talk about OC its like "yeah dude, OC its "tha greeeeeat doi it dude" or something like "dont do it!!! u will decrease your tablet life" and yes, i know that devices are way to diferent even if they are the same model, and also im agree with u, governors and I/O works better than OC but we dont have many for our device, i miss the smartass v2 governor,or the brazzilianwax too, but well, hope someone can port it for us someday.
Hi guys, here are results of LS970 in antutu Benchmark X.
http://www.mobile-inform.com/content/view/1194/1/
Benchmark X version is a special version of Antutu in wich all the cheats that manufacturers use are disabled. As far as you can see - maximum cpu speed is only 1188 even if 1512 set in SetCpu or CPUMaster.
please do not compare usual version and this one - the results are different - the results on the right - are from the usual version of antutu at 1500 mhz
Ok...
Sent from my LG-LS970 using xda premium
agurzhiy said:
Hi guys, here are results of LS970 in antutu Benchmark X.
http://www.mobile-inform.com/content/view/1194/1/
Benchmark X version is a special version of Antutu in wich all the cheats that manufacturers use are disabled. As far as you can see - maximum cpu speed is only 1188 even if 1512 set in SetCpu or CPUMaster.
please do not compare usual version and this one - the results are different - the results on the right - are from the usual version of antutu at 1500 mhz
Click to expand...
Click to collapse
Our devices automatically lowers the cpu to 1188 when the phone reaches a certain temperature. Try the benchmark when the phone cools down.
Sent from my LG-LS970 using xda app-developers app
it was as cool as ice-cream
i did not feel any heat at all
That's interesting because I have run quadrant in eco mode and had it indicate the clock speed was 1188 and the run it with eco mode and the clock speed register as the expected 1512. Though I'm not sure what is meant by manufacturer tricks. It's not a trick that the cpu can be clocked down when it's not needed.
the trick is any unusual experience.
Usual antutu shows 1,5 , while this one only 1188
another proof is here:http://forum.xda-developers.com/showthread.php?t=2044938
- cpu tweak to enable use of all freqs in high stress times like games and benchmarks
Click to expand...
Click to collapse
It's funny but our stock kernel doesn't support the 1188 frequency we have 1134 then 1242
strange...but you've seen the bench
thunder1979 said:
That's interesting because I have run quadrant in eco mode and had it indicate the clock speed was 1188 and the run it with eco mode and the clock speed register as the expected 1512. Though I'm not sure what is meant by manufacturer tricks. It's not a trick that the cpu can be clocked down when it's not needed.
Click to expand...
Click to collapse
Weird, I've always had the phone tell me it's running at 1188mhz, regardless of whether that setting is on or not.
I hate how the system decides for me when my phone is too hot or not.
Compared to my GNexus, this thing is an ice cube.
I can only guess, but sometimes the GNexus would feel like it was ~120-140°F during movie playback at 50% brightness.
This thing has never reached more than 30 °C (I do have an otterbox)
It really rustles my jimmes how they think anything above a 30°C core temp is outrageously hot, and gives them the right to restrict screen brightness and core frequency.
Just.. I need my AOSP back.
Sent from my LG Optimus Prime G
rsjc741 said:
Weird, I've always had the phone tell me it's running at 1188mhz, regardless of whether that setting is on or not.
I hate how the system decides for me when my phone is too hot or not.
Compared to my GNexus, this thing is an ice cube.
I can only guess, but sometimes the GNexus would feel like it was ~120-140°F during movie playback at 50% brightness.
This thing has never reached more than 30 °C (I do have an otterbox)
It really rustles my jimmes how they think anything above a 30°C core temp is outrageously hot, and gives them the right to restrict screen brightness and core frequency.
Just.. I need my AOSP back.
Sent from my LG Optimus Prime G
Click to expand...
Click to collapse
Amen. Lets hope zv9 update addresses what it thiks heat is. 87° and brightness dims.oh jeez. Also.i achieved 21,968 normal antutu. Was third rank. Was really friggen cool.what a phone. Wish it had dual.radio though.no data while talking and no world capability. Can roam international though
Sent from my LG-LS970 using xda premium
rsjc741 said:
Weird, I've always had the phone tell me it's running at 1188mhz, regardless of whether that setting is on or not.
I hate how the system decides for me when my phone is too hot or not.
Compared to my GNexus, this thing is an ice cube.
I can only guess, but sometimes the GNexus would feel like it was ~120-140°F during movie playback at 50% brightness.
This thing has never reached more than 30 °C (I do have an otterbox)
It really rustles my jimmes how they think anything above a 30°C core temp is outrageously hot, and gives them the right to restrict screen brightness and core frequency.
Just.. I need my AOSP back.
Sent from my LG Optimus Prime G
Click to expand...
Click to collapse
Crwolv said:
Amen. Lets hope zv9 update addresses what it thiks heat is. 87° and brightness dims.oh jeez. Also.i achieved 21,968 normal antutu. Was third rank. Was really friggen cool.what a phone. Wish it had dual.radio though.no data while talking and no world capability. Can roam international though
Sent from my LG-LS970 using xda premium
Click to expand...
Click to collapse
Hey guys, THIS is in the AT&T forum, but I believe it will work here too.
I don't know how risky this could be, I haven't done it, but the option is there.