Has anyone noticed deteriorated display performance after DI08? I see this most-notably when switching applications, opening the notification drawer, and sliding between TW home screens. It didn't do this nearly as badly, at least according to my perception, before DI08. I just opened Quadrant, and the highest I've ever seen "Current freq" is 800MHz - I can't seem to get it to stick at 1GHz no matter how much I load the CPU. That being said, Quadrant and Linpack scores are high as ever...
I also noticed that it drops down to 400MHz very quickly. So, is it possible that the display sluggishness is linked to a more aggressive clock throttling to save battery? Or am I just seeing things?
Related
Does anyone know if the desire hd has any sort of processor throttling enabled on it? Am running Linpack benchmarks on my phone and am getting some very weird results.
My linpack benchmark changes between ~35Mflops and ~62Mflops seemingly at random, this is a fresh install of cyanogen 7.0 with LorDMod V4.0 kernel. Also have the google apps installed (are any of these known to cause high cpu-usage?) I have checked the background CPU usage using SystemPanel and there appears to be no other processes using the CPU.
Phone is running at 1.996ghz at 1300mv, have run mutiple stress tests over several hours and its rock solid in terms of stability, the max temperature i've seen is 37 degrees which also seems perfectly fine (I've heard from other threads that the processor temperature is normally around 5 degrees higher than the battery, so this doesn't seem to be an issue)
Have also tried increasing the voltage at 1.996ghz all the way up to 1475mv (incase of strange stability issues) however, as expected this has no impact on the linpack readings.
Basically i'm at a complete loss to explain this myself and therefore am wondering if any of you guys can come up with any other ideas?
Thanks.
What CPU govenor are you running the benchmarks with? You should use Performance, as it will lock your CPU at the maximum allowed frequency
I hope your not running your processor at that speed all day
Sent from my Desire HD using XDA App
Wait wait wait...You are running 2GHz @1300mV?What the F*CK?Mine needs 1450mV to run @1.8GHz,maximum is a really unstable 1.9GHz with 1500mV,and this only for some seconds!
Anyway...You could try killing some apps.It's normal that tests aren't consistent however.
This thread is Meant to display my results from "battery" testing "performance" benchmarks etc. to show its fullest potential.
I've ran "quadrent, linepack and some other benchmark" results vary.
QUADRENT I usually get depending on how many widgets, background task are open about 1900-2300 and Used "SET CPU" To performance mode "926 MHZ - 1000 MHZ
Eagerly waiting on a OC For the tegra 2 chipset on the iconia "xoom" has already achieved great speeds of 1.5 (1500) GHZ
I made a short brief 6 minute video of me running a few benchmarks, to show the speeds it achieves. "video proccessing will be watchable in about 5 minutes"
http://www.youtube.com/watch?v=6CN2bZisCvg
Next test i will be running on this device is battery life, something lots of people are converned about should have results in qbout 48 Hours, will keep update will run many test on this device, from straight playing games battery life to just movies web browsing etc. the whole 9 yard.
Will continuasly post updates on new things i found out from overclocking testing everything you can imagine.
I also ask that we all as a community can share our expieriences with the device from batterly life to performance to enchancements.
"l3giticonia out"
Wow I wish you had kept this thred up I would have loved to see this before I purchased.
hmmmm
Correct me if I am wrong, please: but by using setCPU to set a "performance" option and setting the speed lower then stock clock speed (926 mhz?) you have now disabled the systems ability to lower the clock speed and are underclocking the system.
Am I mistaken in assuming that you are going to get rather useless data on the overall performance of the system by setting these options? By underclocking, you have installed a custom kernel on the device and any results you get are going to be subject to the performance of that kernel, which is not what the a500 stock is running.
Why 926 mhz? Stock is 1.0 ghz, I generally run at 1.4ghz+. Am I missing something? Again, by setting SetCPU to "performance" any data you come up with is going to be on a system that cannot lower clock speed during low use periods, so your battery life stats will be lower then a normal users experience.
ARM based chips are built to scale the speed depending on load. By setting performance mode, you disable the chipsets ability to scale, right?
Was wondering if anyone might of experienced it (although it's kind of hard to tell if it's even happening).
I noticed earlier I was playing a game that my tablet was pretty warm, and then I immediately went to Rom Toolbox. My governor was set at Performance, and both sliders at 1.7GHz, but I noticed the clock speed going down in increments of 100MHz (1.7GHz to 1.6GHz to 1.5GHz to 1.4GHz) and then back up to max, and it did this a few times and then finally stuck at 1.7GHz, when the tablet was a little bit cooler (I think).
While running StabilityTest (the CPU+GPU Stability Test on Full Details), clock speeds are constantly changing between 1400MHz, 1500MHz, 1600MHz, and 1700MHz with the Performance governor in-use. The top-left of the tablet is also noticeably warm.
Edit: It drops to 1300MHz and even 1200MHz at times too as the test goes on. Might drop lower depending on how long it's ran.
Very interesting, that would explain some of the slowdowns I am seeing whilst playing Asphalt 7.
Please note that the Stability Test is not a "CPU Burner" test, it does other things as well (checking the RAM, testing the GPU, etc.). So it's to be expected that it doesn't run at full speed all the time.
I've done some intense gaming on mine, and while it does get a little warm in a small spot on the upper left side, it's nothing abnormal. Now if you want warm, try the Acer A700, that guy gets hot on the back due to a poor heat spreading solution.
So I usually use CPUSpy to monitor my CPU usage. This comes in handy once the device is rooted and I can see how custom kernels and settings affect battery life and cpu cycles. My LG G4 is the tmobile variant and obviously not currently rooted. I notice through CPUSpy that my cpu speed literally never exceeds 1440mhz.
I don't have any problems with that per say, everything on the device still runs buttery smooth without anything more than the occasional hiccup or lag. I'm curious if anyone else has monitored their CPU speeds and noticed the same thing? I just find it a little interesting.
CPU spy can't even see the A57 cores so there's no way it can see what speed it's running at.
4 cores are limited to 1.44 the rest are 1.8
I have not used CPUSpy. But CPU-Z will show you the speed of each of the 6 cores. As mentioned, the last 2 are the only ones I've seen reach 1.8GHz, the first 4 seem to top out at 1.4 GHz.
Ok.. Using cpu-z..
That's how mine looks "at rest". When it's sitting quietly, saving the battery. Crank up some apps, and you should see those clock speeds rise.
But, trying to improve my battery life, and keep the temps down, I've been hoping to see those numbers stay low, not actually show how high they can go
I agree.. As ive stated, the device runs great i just found it odd. It even calls it a 1.44ghz cpu in the cpu profile and mostly no matter how hard i push the device i cant break that speed
Right as CPU-Z opens, the clock speeds spiked briefly. I was able to get a screenshot quickly.
Do yours also jump up for a second or two right as the app opens?
This has been discussed already. As the previous post shows, they do get to 1.8Ghz when required.
Is it safe to change my CPU governor to "performance" to force max clock speed?
I don't want to overclock my Note 4, don't worry, not talking about that. But I am talking about MAX clocking it - forcing it to run at maximum rated speed. I've already tested out SetCPU and used it to change my governor to performance which forces the clock to max, and it nearly doubled my framerate in many games, especially the ones that struggled to play on this device like Xcom:EW.
But I quickly turned it off because I wasn't sure it was safe to do in the new era of smartphones, what with their DVFS and all. I'm worried that I'm going to overheat the CPU, and it's not going to be able to downclock because of temperature anymore. I'm only modifying the governor, but what if I actually used SetCPU to just change the CPU clock to max, without even touching the governor?
Can I hurt my phone by doing this? Can I safely start forcing my CPU to run faster while playing games, knowing that the only thing I risk is my battery draining faster, or am I actually risking damaging components by doing this?
Hello and thank you for using Q/A,
your CPU will not be damaged, but the battery life time will be shorted.
Regards
Trafalgar Square
RC
I personally have used Performance governor on Moto X 2013 for almost the whole 8 months I had it, 24x7 I mean. Never had a problem, yeah maybe battery life was little less than normal but I never did really care about it. Then I ran the same governor for a good period of time on my Note 3 too, same, no problem at all. Like you said, in games the frame rate difference is massive, but I don't play much games, I simply used that governor because it gets rid off all those micro lags and jitters which are Android's trademark, I simply can't them, with default Interactive the micro lags are very apparent.
However with Note 4 I am pretty happy with the BluActive governor, it makes most of the micro lags to go away, so sticking with it.
In any case unless you plan to use a mobile phone for maybe 5 years or so, I don't see any problem at all with it, other than a slightly increased heat, and maybe a little less battery backup, but you will find so many comments which might scare you, that chip burns off if you run it and all that, but those mainly are BS.