I was running quadrant when I first got the S3 before changing anything to get a good base line. Well after disabling Verizon's bloat which was only four or five apps including the kindle app I noticed after running quadrant again I went from hitting scores above 5000 to barely over 3000 with no other changes. After re enabling the same apps my scores jumped back to over 5000 again. Also the CPU was showing that it was topping out at 1100 to 1200 and after I enabled the Verizon apps it went back up to the full 1500. Any thoughts on how their bloat disabled could affect the CPU in this way?
M.yA.nD.droidS3
Mine didn't change at all. I get around 4500 with or without the bloat disabled.
Related
I use System Panel pretty religiously to keep an eye on things, mostly in an effort to save battery life or figure out what apps are using battery. One thing I noticed right away, which may explain the complaints people are having with shorter battery life and warmer running.
On 2.1, if I leave System Panel open and just watch CPU clock speed, it will idle in the 200-300 MHz range. With the leaked Froyo OTA, it never goes below 600 while idle, and averages 700-800. I went ahead and closed down all third party apps and even some non essential built in processes just to make sure, but nothing got the CPU speed below 600. Now CPU *load* percentage was minimal, less than 10%. So why won't Froyo let the speed drop down at idle?
bast525 said:
I use System Panel pretty religiously to keep an eye on things, mostly in an effort to save battery life or figure out what apps are using battery. One thing I noticed right away, which may explain the complaints people are having with shorter battery life and warmer running.
On 2.1, if I leave System Panel open and just watch CPU clock speed, it will idle in the 200-300 MHz range. With the leaked Froyo OTA, it never goes below 600 while idle, and averages 700-800. I went ahead and closed down all third party apps and even some non essential built in processes just to make sure, but nothing got the CPU speed below 600. Now CPU *load* percentage was minimal, less than 10%. So why won't Froyo let the speed drop down at idle?
Click to expand...
Click to collapse
Good catch. I'm looking at it now, it gets down to 448mhz while downloading an APP from the market over the mobile network. Once downloaded and installed, it stays between 600-900mhz?? Rebooted and it still never goes below 6, and mostly stays in the 7-800's. Not good! I have a fresh install of Skyraider 2.01 with sense removed, using launcher pro.
I found this really interesting but I think systempanel is reading incorrectly. I say this because if you watch set CPU read the processor you can see that it drops down to 245mhz when idle even though systempanel reads 600-700mhz.
Sent from my ADR6300 using XDA App
Ok after bricking one phone, i got a new one and loaded voodoo and dirkks SV1200 kernal. also oc'd to 1200. everything has been perfect and had scores in the 18 or 1900s. this morning i was using my phone and noticed it was very laggy. i checked quadrant scores again and it scored in the 14's. as i ran the benchmark, i noticed it hangs on the I/O 3of4 for longer then usual. i have restarted the phone, no luck. even reflashed the kernal, no luck. I cant think of any new programs or changes to the phone. any ideas?
Jeff5886 said:
Ok after bricking one phone, i got a new one and loaded voodoo and dirkks SV1200 kernal. also oc'd to 1200. everything has been perfect and had scores in the 18 or 1900s. this morning i was using my phone and noticed it was very laggy. i checked quadrant scores again and it scored in the 14's. as i ran the benchmark, i noticed it hangs on the I/O 3of4 for longer then usual. i have restarted the phone, no luck. even reflashed the kernal, no luck. I cant think of any new programs or changes to the phone. any ideas?
Click to expand...
Click to collapse
Well the 3rd I/O test does take the longest to complete. If you are having I/O issues this certainly would give you a fluctuating Quadrant score since so much is I/O affected especially on a voodoo'd SF. Have your other benchmarks taken a dip as well? Does the phone lag in regular use? If its just a Quadrant issue I would not overly panic. Cross check with other benches
My phone did that with voodoo too, I installed dirrks lv 1200, and when I upgraded it started acting up. I did remove the fix before I updated, did everything right, but it still lagged so I just glassed back to stock and did all the steps for remove lagfix. Still on stock kernel now but will install birdman optimized tonight.
Adrynalyne is the man BTW. Ok, as to the OP, have you reset the CPU in SetCPU after you restart your phone? If I don't, I get a score of 1400 ish too.
that would make sense as I believe it resets to 800 instead of 1200
thestigwins said:
that would make sense as I believe it resets to 800 instead of 1200
Click to expand...
Click to collapse
Yes, it resets to 800. 1.2 ghz is nice, I would like to see 1.6. G2 OC'ed at 1450 I believe... Ugh, one day, one day.
No luck with OC kernels
I have tried a few, everytime I get issues. Seems like setcpu just does not play well with this phone. I get 1800 on stock voodoo .2. Don't see a need for the extra conservative 200mhz that an OC can provide. Good luck with the kernels though.
Anyways, as stated, make sure set CPU is set to 1.2 GHz and not 800 MHz which is where it defaults. I use the widgit and crank up the speed any time I'm using the phone, else, I leave it at 800 when charging / idle etc.
Also, go into System Panel (best app killer around) and do an END ALL - it will kill everything... THAN run quadrant. If your scores skyrocket, don't be alarmed. Quadrant likes to have a very clean system to run on, if you have a lot of cached or running applications, Quadrant seems to suffer, I'm assuming due to the delay between it requesting more RAM from Android and the time it takes for it to release it. Seems to make sense as to why it would slow down to me at least based on what I know about how Android handles RAM.
Just make sure to reboot your phone after to restore your normal app library of running apps.
With a 1.2 GHz overclock on jt's voodoo kernel most of us are/were getting about 1925 . I've not ran dirrk's LV kernel, the undervolting is very minimal and I'd rather error on the side of stability, YMMV.
Accused: Everyone flaming & veering off-topic (You know who you are)
Charge: Violation of XDA Anti Spamming, Trolling & Flaming Rules
Verdict: GUILTY
Resolution: All violating posts have been deleted
Warning: Further transgressions might result in a BAN!
COURT'S ADJOURNED!
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?
(((("The devices range seems to be huge. Not being interested into scores that much I had not tried Antutu on my S4 to date but did a few minutes ago:
On my rooted stock Vodafone Rom the Antutu score with Faux 3m stock settings and stock CPU clocks is 24.413.
Lowering the CPU clocks to between 324-1674 and changing to mpdecision off and intellidemand it is 24.221...
No problems with Antutu - both scores fine...
Edit: taking a closer look it seems to me as if Antutu overwrites the upper CPU clock limit somehow. The 1674 before running Antutu popped back to 1892 when checked after Antutu had finished. The lower limit remains untouched though - strange... At least the resulting scores are consistent - 2nd run with the second settings setup ended with equal 24.370.)))
How are you able to do the test???
As soon as I start Antutu, It bounces out from antutu and no mather if I lower the frequency ,still same result.
i think it is an antutu problem my galaxy s3 was getting lower scores while i was overclocking :/ maybe when the app gets updated it will be fixed
ilcabrone said:
(((("The devices range seems to be huge. Not being interested into scores that much I had not tried Antutu on my S4 to date but did a few minutes ago:
On my rooted stock Vodafone Rom the Antutu score with Faux 3m stock settings and stock CPU clocks is 24.413.
Lowering the CPU clocks to between 324-1674 and changing to mpdecision off and intellidemand it is 24.221...
No problems with Antutu - both scores fine...
Edit: taking a closer look it seems to me as if Antutu overwrites the upper CPU clock limit somehow. The 1674 before running Antutu popped back to 1892 when checked after Antutu had finished. The lower limit remains untouched though - strange... At least the resulting scores are consistent - 2nd run with the second settings setup ended with equal 24.370.)))
How are you able to do the test???
As soon as I start Antutu, It bounces out from antutu and no mather if I lower the frequency ,still same result.
Click to expand...
Click to collapse
Yea it's a problem with AnTuTu, after you play with your phone's frequencies, it force closes. Sometimes with Quadrant too. It's weird because benchmarking apps are almost ment for testing your phone with overclocking, you (we) should contact the dev!
Thanks for you reply.
Yes,Antutu seem to be the culprit.
Funny though some are able to do the Benchmarking without a problem.
I do enjoy the smoothness and stability I find in FAUX Kernel for my Galaxy s4 9505,dont really need a benchmark to tell me if its good or not.
Anyway would be fun for comparison.
Regards,
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.