I want to know the power consumption of Qualcomm MSM7227A, on 1 GHz.
I have the power_profile.xml info, obtained via this program - BatteryViewer by TKY.
For my Galaxy Mini 2 with MSM7227A (800 MHz) this is the information:
245 MHz - 30 mA
320 MHz - 50 mA
480 MHz - 80 mA
600 MHz - 100 mA
800 MHz - 180 mA
I want to overclock it to 1000MHz but I want to know if it's worth it. If the power consumption is too high, it would better to leave it at 800 MHz.
So, if there is anyone with Sony Xperia J, HTC Desire V, Galaxy Ace Plus, or LG Optimus L7 (all of them have MSM7227A at 1GHz) can you please tell me the declared power consumption of this CPU at 1GHz.
Anyone is welcomed to share their info so we can know the general power consumption of different CPU's.
I have a galaxy ace plus overclocked to 1.3GHz, and it seems to consume up to 600 mA. How to find out consumption at lower frequencies? I have to set max freq to lower, use it for a couple of days and check the stats? Or is there any simpler way?
The only way that I know of checking power consumption on Android is via factory written data in power_profile.xml.
Go to PlayStore, find BatteryViewer by TKY, install it. Then click the left button for options and click Power Profile.
For example you'll see something like this:
...
cpu.active 0 180.0
cpu.active 1 100.0
cpu.active 2 80.0
cpu.active 3 50.0
cpu.active 4 30.0
...
cpu.speeds 0 800000.0
cpu.speeds 1 600000.0
cpu.speeds 2 480000.0
cpu.speeds 3 320000.0
cpu.speeds 4 245760.0
....
How did you found out that your Ace uses 600mA at 1.3GHz?
=========
EDIT!!!
This version of Antutu didn't work properly on my phone. It didn't took into account the SD card speed, so the I/O result is much lower, and so is the overall result. But you can still see the implications of overclocking on cpu, gpu and ram.
=========
I also noticed that performance of the whole system is not scaling linearly with frequency. It's possible on some higher frequencies the system to be slower overall.
These are tests of my Galaxy Mini 2 with Antutu benchmark:
--------------
AnTuTu v.3.0.2
--------------
Frequency - 600 MHz
Total: 3155
CPU: 610
GPU: 2216
RAM: 259
I/O: 70
Frequency - 800 MHz
Total: 3427
CPU: 819
GPU: 2192
RAM: 326
I/O: 95
Frequency - 857 MHz
Total: 3283
CPU: 893
GPU: 1954
RAM: 341
I/O: 95
Frequency - 876 MHz
Total: 3327
CPU: 904
GPU: 1978
RAM: 350
I/O: 95
Frequency - 896 MHz
Total: 3389
CPU: 923
GPU: 2010
RAM: 356
I/O: 100
Frequency - 934 MHz
Total: 3370
CPU: 959
GPU: 1962
RAM: 349
I/O: 100
Frequency - 953 MHz
Total: 3464
CPU: 987
GPU: 2016
RAM: 356
I/O: 105
Frequency - 972 MHz
Total: 3471
CPU: 1002
GPU: 2012
RAM: 357
I/O: 100
Frequency - 992 MHz
Total: 3433
CPU: 1019
GPU: 1933
RAM: 366
I/O: 115
Frequency - 1011 MHz
Total: 3414
CPU: 1045
GPU: 1884
RAM: 375
I/O: 110
Frequency - 1083 MHz
Total: 3609
CPU: 1119
GPU: 1960
RAM: 415
I/O: 115
Strafeb said:
How did you found out that your Ace uses 600mA at 1.3GHz?
Click to expand...
Click to collapse
I use Battery Monitor widget, it lays out a plot of mA (usage) for a specific duration. In the plot the mA value peaked at 600.. Probably those were the times when I was using processor intensive apps.
mon_iker said:
I use Battery Monitor widget, it lays out a plot of mA (usage) for a specific duration. In the plot the mA value peaked at 600.. Probably those were the times when I was using processor intensive apps.
Click to expand...
Click to collapse
That is probably battery draing for the whole system including cpu, radio, wifi, screen...
Can you please check the data with BatteryViewer and post them here.
Thank you.
cpu.active 0 0.2
cpu.speeds 0 400000.0
The rest are empty. I get the same values whether I oc or not. So what info can I decipher from this?
mon_iker said:
cpu.active 0 0.2
cpu.speeds 0 400000.0
The rest are empty. I get the same values whether I oc or not. So what info can I decipher from this?
Click to expand...
Click to collapse
As far as I know, this file contains values from which the OS approximates power consumption for various components. They are fixed, factory predefined values.
Those values that you saw are default ones. It doesn't look your factory defined them. I have seen that on some phones there are no predefined values, so I don't know what's the deal.
What phone do you have?
Related
Hi guys
I downloaded the quadrant standard application on my Captivate. Looking into the system info i observed the following
1. CPU : samsung cortex v7. I thght the processor was a v8? I dunno whether the processor info is right.
2. The processor speed is displayes as "800 MHz"
Max freq ; 1000 MHz
MIN freq : 800 MHz
Whatz going on here?
Can someone explain this?
Please run the benchmark and lef me know!
Sent from my SAMSUNG-SGH-I897 using XDA App
carporsche said:
Hi guys
I downloaded the quadrant standard application on my Captivate. Looking into the system info i observed the following
1. CPU : samsung cortex v7. I thght the processor was a v8? I dunno whether the processor info is right.
2. The processor speed is displayes as "800 MHz"
Max freq ; 1000 MHz
MIN freq : 800 MHz
Whatz going on here?
Can someone explain this?
Please run the benchmark and lef me know!
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
the 800mhz I would assume means it is throttled down.
My results...
Name: ARMv7 Processor rev 2 (v71)
Current freq: 800 MHz
Max req: 1000MHz
Min freq: 100 MHz
-JChao
Just ran the benchmark and got the same thing. Please don't tell me this thing is underclocked. if so is there a program out there that will bring it up to speed?
The processor is a Samsung S5PC110 Cortex-A8 and uses the ARM v7 instruction set. It's not a version 8.
there is an APp to change your CPU clock. Don't do it though, nothing on android requires those extra 200 MHz yet. If your thinking about UI Lag, this is a software issue and not a consequence of the throttled cpu. Hang tight for a fix from developers.
With the software fix and throttled down cpu, this phone is still faster than the newest phones running 2.2 (Froyo)
SetCPU will let you force the frequency. But you shouldn't need to use it, 800MHz just seems to be the Hummingbird's idle frequency. The CPU probably just idled while the graphical benchmarks were being run.
CPU in phones never runs at 100% at all times that would kill battery , you can force it if you root your phone but that is counter productive , as it goes from anywhere from 1% to 100% of its speed when it needs to , during intensive usage or benchmarking it will reach 1000mhz , but if all you do is read text it will conserve battery.
Its obvious from this info below
Current freq: 800 MHz
Max req: 1000MHz
Min freq: 100 MHz
Yes, the Cortex A8 is an ARM7 processor. The older CPU's used were ARM11 processors.
Thankx for the info guys..
I checked again and for some reason i got confused with the processor and was writing the post from memory (my memory ). it says ARMv7 Processor rev 2 (v71).
And yes i do think the 800 MHZ is pretty fast.
I just need to get rid of the samsung UI and switch to stock android.
-------------
itzz(AN)dRoiD
The spec sheet lists 1 GHz, and spec sheets show the operating frequency so I would assume that the CPU can run at different speeds for different workloads. Try running a couple heavy applications in the background and check it again. If all is well in the world it should clock upto 1 GHz.
carporsche said:
Thankx for the info guys..
I checked again and for some reason i got confused with the processor and was writing the post from memory (my memory ). it says ARMv7 Processor rev 2 (v71).
And yes i do think the 800 MHZ is pretty fast.
I just need to get rid of the samsung UI and switch to stock android.
-------------
itzz(AN)dRoiD
Click to expand...
Click to collapse
The processor is NOT 800mhz it's just throttled down to 800mhz cause of not needing the full 1ghz speed. That saves power and battery life gets extended. Laptops and desktops do the same thing.
so in other words it basically adjusts oh and also maybe the ARMv7 infrastructure is better then the 11 one
yes i do get the idea
tbae2 said:
The processor is NOT 800mhz it's just throttled down to 800mhz cause of not needing the full 1ghz speed. That saves power and battery life gets extended. Laptops and desktops do the same thing.
Click to expand...
Click to collapse
I do get the idea!.. i inquired about it bcoz nowhere it was mentioned that the processor was underclocked.. So basically the ideal processor speed is 800MHz and it can be overclocked to 1GHz is the way i see it!
sorta like that more like the speed auto adjust to your needs i think
So what kind of scores does this phone get in comparison to other new Android phones with or without 2.2. I am curious between the Quandrant scores of Hummingbird (Galaxy S), OMAP (Droid X), Snapdragon (HTC HD2/EVO 4G).
Thanks.
well the hummingbird beat the evo 4g in graphics and cpu power just search captivate benchmarks on youtube the channel name is androidandme
with mimocans lag fix ive seen people get scores as high as 1700(nexus one on 2.2 gets about 1250).
cognition 6.1 XXJVQ 2.3.4 gingerbread on my 1897 captivate
http://www.google.com/url?sa=t&sour...q93aAw&usg=AFQjCNFXnK6kfMAUUHmLjWnrNt4Mx-pZXw
Just started playing around with UV/OCing tonight and am pretty happy so far with the results. I'm just currently looking at getting some extra battery life with UVing.
Just curious what everyone else has achieved.
And yes I know, and everyone else should know, that just because someone else was able to get a certain OC/UV doesn't mean you will. So is the game of OCing anything.
Please post the full details of what you have achieved and/or what you run as a daily driver.
In this format:
(My current results, so far)
1120Mhz @ -125
1000Mhz @ -125
900Mhz @ -125
800Mhz @ -125
600Mhz @ -125
400Mhz @ -125
200Mhz @ -125
100Mhz @ -125
Rom: Continuum v4
Kernel: Onix - 2.0.1 #7
(I'm curious what the lowest voltage has been attained at stock/1120 clock)
bnevets27 said:
Just started playing around with UV/OCing tonight and am pretty happy so far with the results. I'm just currently looking at getting some extra battery life with UVing.
Just curious what everyone else has achieved.
And yes I know, and everyone else should know, that just because someone else was able to get a certain OC/UV doesn't mean you will. So is the game of OCing anything.
Please post the full details of what you have achieved and/or what you run as a daily driver.
In this format:
(My current results, so far)
1120Mhz @ -125
1000Mhz @ -125
900Mhz @ -125
800Mhz @ -125
600Mhz @ -125
400Mhz @ -125
200Mhz @ -125
100Mhz @ -125
(I'm curious what the lowest voltage has been attained at stock/1120 clock)
Click to expand...
Click to collapse
I have mine oc. to compensate with battery drain I was undervolting also here is my specs:
1400- 0 Quadrant - 2258 Linpack - 20.1
1000- 50
800 - 100
400 -125
200 -125
100 -150
Here's what I got
1400 @ -25 Quadrant ~1900 Linpack ~19
1200 @ -50
1000 @ -50 Quadrant ~1600 Linpack ~14
800 @ -75
400 @ -75
200 @ -100
100 @ -100
EDIT: I use Voltage control app, some people seem to have issues with set CPU
______________________
Samsung Captivate
ROM: designgear's Cognition v4.2.2
Kernel: eXistZ's KB1 #7 beta
i envy you guys that can run stable at those numbers. my results are
1280 -50
1000 -25
800 -100
400 -100
200 -50
100 -50
with less over clock i can get much lower voltages across the board and without over clock i can go lower still.
having the actual voltage the same for 1000 and 1280 seems to help stability. my chip deosn't seem to like voltage fluctuations. also the difference between the upper and lower voltage seems to be a problem. my phone is stable at -100+ across the board if i dont over clock. for that reason i tend to test things by undervolting from the upper frequencies down, if i go from the low frequencies i will see instability with very little undervolt untill the upper frequencies are also undervolted.
CM7 03182011, Kernel du Jour v4.2
Just UV, with governor set to "conservative"
1000: -100
800: -100
600: -125
400: -125
200: -150
100: -150
Cognition 4.3
Voltage Control App
Stability Test
Neocore
Linpack
Mhz UV Temp. Linpack
1300 -50 (20c/42c) 17.8~
1000 -50
800 -75
400 -100
200 -100
100 -100
Serendipity 6.3
Paragon 6 kernel @ 1344mhz
Linpack = ~18.8
1344 - 0
1000 - 50
800 - 75
400 - 100
200 - 125
100 - 125
I'm liking your numbers... I wonder if having 100 and 200 enabled makes a big difference. Eliminating 1200 and going from 1000 to 4000 seems quite a bit snappier.
Idk. Paragon kernel defaults the states.
jgrnght said:
I'm liking your numbers... I wonder if having 100 and 200 enabled makes a big difference. Eliminating 1200 and going from 1000 to 4000 seems quite a bit snappier.
Click to expand...
Click to collapse
Interesting thread...would be great to see what people are using for different roms..
I can't get 1400 stable, even at stock voltage.... but at 1300 I can get down to -75:
1300 @ -75
1000 @ -100
800 @ -100
600 @ -100
400 @ -100
200 @ -100
100 @ -100
Last time I tried going down to -125 it wasn't stable, but that was on a different kernel... gonna give it a try when I get a chance.
CM7 and The Escapist's kernel with Noop scheduler and 1300mhz limit enabled
1300 -50
1200 -75
1000 -75
800 -100
600 -100
400 -125
200 -125
100 -125
Nice to see everyone posting their numbers.
I'm finding that the UV setting I have are causing the phone to lock up once and a while. I did pass 50 passes of stability test and 30min of neocore. So are those programs really that accurate at testing stability? Is there anything better out there?
Playing Cordy for a bit seems to effectively stress the system, as I can get it to lock quickly even when seeming stable in the synthetic tests.
Cordy spends almost 100% of the time in top frequency state from what I've seen, plus its pounding the GPU.
bnevets27 said:
Nice to see everyone posting their numbers.
I'm finding that the UV setting I have are causing the phone to lock up once and a while. I did pass 50 passes of stability test and 30min of neocore. So are those programs really that accurate at testing stability? Is there anything better out there?
Click to expand...
Click to collapse
I've found that stability test is only accurate on the Mhz it is testing at. What i did was lock my Mhz at 1400, then 1300, then 1200, 1120, 1000, lastly 800. I had to have 5 frequencies ticked to get 800 to even work. I did each level to find the max UV for each level... then used those numbers.
I found having 1000 being my 2nd highest frequency, makes for a much snappier interface. Right now I have 1300, 1000, 800, 400, 200, 100.
Although I was able to use stability test all the way down to 800, I really couldnt test the lower frequencies with it. I found 125 was stable on the lowest 3 while doing benchmarking, however when moving back and forth quickly through settings options, mainly the drop down menus, it would cause it to lock up. So I raised the lower number up to 100 and no longer got crashes in option menus.
Here are the numbers I've settled with and get the quickest overall feel with.
noop scheduler.
1300 -50
1000 -50
800 -75
400 -100
200 -100
100 -100
Cognition 4.3 btw.
Tryng to underclock now. Blah, such a pain!
noop scheduler.
1200 -100
1000 -100
800 -100
400 -100
200 -100
100 -100
On Phoenix Ultimate Special Edition with Onix 2.0.3 kernal
No one else wants to brag?
Anyone aware of (or maybe could make?) an app that can test at each frequency? It would be very helpful to be able to test UV settings for frequencies in the 100-800 range. So far it seems the only "test" is once the phone locks up while navigating thew menus, bump up the voltage to all of the frequencies bellow 800.
(Thanks jgrnght for the suggestion on how to test each frequency 800+)
bnevets27 said:
No one else wants to brag?
Anyone aware of (or maybe could make?) an app that can test at each frequency? It would be very helpful to be able to test UV settings for frequencies in the 100-800 range. So far it seems the only "test" is once the phone locks up while navigating thew menus, bump up the voltage to all of the frequencies bellow 800.
(Thanks jgrnght for the suggestion on how to test each frequency 800+)
Click to expand...
Click to collapse
lol...nothing can beat with hands on experience...you can download cpu spy from the market it will tell you how your cpu stays in every frequency/states you have. From that data you will know which fequency needs more undervolting or tweaks.
Has anyone noticed a definite increase in battery life as a result of undervolting? Common sense points to that it would (less voltage needed, less battery power needed to power it) but does it really translate into solid real life results?
I'm hoping that all this UV business doesn't just give me an extra 15 minutes or something and that it actually translates into an hour or 2.
I got on CM7 TheEscapist's kernel:
1000: -125
800: -125
600: -125
400: -125
200: -150
100: -150
Scheduler: noop
Governor: Conservative
What are the best settings of SETCPU for the galaxy fit?
(i have the Cyanogenmod 7.2)
122 - 480 Mhz : Battery life really good ! performance really bad
122 - 604/600 Mhz : Battery good ! performance stable !
122 - 745 Mhz : Battery reduces faster , but performance is Great !
122 - 801 Mhz : Battery drains faster, but performance is F***** good !
Battery Saver
122 - 480 Mhz : Good !
245 - 480 Mhz : Battery drops litte slower
320 - 480 Mhz : Not really good
Performance Blower
480 - 604/600 Mhz : Stable !
480 - 745 Mhz : Performance increased !
604 - 801 Mhz : Your Fit turned into a low-class F1 !
745 - 901 Mhz : Your Fit turned into a med-class F1 !
Blow Your Mind
600 - 600 Mhz : Never drops your performance !
745 - 745 Mhz : Never slow down !
801 - 801 Mhz : No slowdown !
901 - 901 Mhz : Your Fit turned into a super fast motorcycle !
Never think like this
901 - 982 Mhz : Your Fit turned into a hot pan !
1000 - 1120 Mhz : Your Fit exploded !
1500 Mhz - 2000 Mhz : Faster than a SIII !
4000 Mhz - 8000 Mhz : You are crazy !
10000 Mhz - 11000 Mhz : You are fastest low-end device !
13421 Mhz - 15293 Mhz : You burn your house !
31931 Mhz - 78832 Mhz : You burn 4 house !
39239 Mhz - 88392 Mhz : You destroyed your city !
99999 Mhz - 100000 Mhz : You destroyed your country !
source
What i have to do with the governator and the other settings?
Inviato dal mio GT-S5670 con Tapatalk 2
Best for performance and battery ,for me, min 122- max 710 and as governator SMARTASSV2.
PRESS THANKS IF I HELPED YOU.
Sent from my GT-S5670 using xda app-developers app
Harryhades said:
122 - 480 Mhz : Battery life really good ! performance really bad
122 - 604/600 Mhz : Battery good ! performance stable !
122 - 745 Mhz : Battery reduces faster , but performance is Great !
122 - 801 Mhz : Battery drains faster, but performance is F***** good !
Battery Saver
122 - 480 Mhz : Good !
245 - 480 Mhz : Battery drops litte slower
320 - 480 Mhz : Not really good
Performance Blower
480 - 604/600 Mhz : Stable !
480 - 745 Mhz : Performance increased !
604 - 801 Mhz : Your Fit turned into a low-class F1 !
745 - 901 Mhz : Your Fit turned into a med-class F1 !
Blow Your Mind
600 - 600 Mhz : Never drops your performance !
745 - 745 Mhz : Never slow down !
801 - 801 Mhz : No slowdown !
901 - 901 Mhz : Your Fit turned into a super fast motorcycle !
Never think like this
901 - 982 Mhz : Your Fit turned into a hot pan !
1000 - 1120 Mhz : Your Fit exploded !
1500 Mhz - 2000 Mhz : Faster than a SIII !
4000 Mhz - 8000 Mhz : You are crazy !
10000 Mhz - 11000 Mhz : You are fastest low-end device !
13421 Mhz - 15293 Mhz : You burn your house !
31931 Mhz - 78832 Mhz : You burn 4 house !
39239 Mhz - 88392 Mhz : You destroyed your city !
99999 Mhz - 100000 Mhz : You destroyed your country !
source
Click to expand...
Click to collapse
Hahaha lol...suicide attack is dat much easy
tbh as long as u use smartass v2 i put 480-729 or 749 , becouse smartass have profile in it to put sleep clock max 245 or 320 not sure , and there is no need to phone bumping from 122 to 750 when screen is on, just put it at 2 clocks 480 and whatever max u want, ul get stable phone and battery is not really afected, btw 122 use more battery than 245 , and 245 to 480 are same.
Max:- 748-767
Min:- 245 (doesn't matter)
Governer:- On demand
I/O scheduler:- Sio
Overclocking beyond 767 is unstable for FIT in most cases & your phone will restart with default C.P.U. values or even bootloops (it depends...)
Sent from my GT-S5670 using xda premium
My battery is getting old and along with that its life length. So I decided to undervolt and found it stressful but fun (lol weird huh?).
I'm currently stress testing it using SetCPU's stress test, so far it has not crashed.
My undervolt settings:
100 MHz - 950
200 MHz - 950
300 MHz - 975 *
400 MHz - 1000
500 MHz - 1025 *
600 MHz - 1050 *
700 MHz - 1075 *
800 MHz - 1100
900 MHz - 1125 *
1000 MHz - 1150
1100 MHz - 1175 *
1200 MHz - 1200
* - I'm just assuming SetCPU sets this automatically since it skips some clock speeds.
However I set the voltages increment by 25, so far the stress test has not shown any crashes.
What are your settings?
I run about -75 I think across the board using AndroidTuner, no stress test, but seems stable.
what is difference between T-760 MP6 and T-760 MP8 ? ( except Number of cores and Maximum Frequency )
edit : less power consumption
what is T-760 MP8 lithography ?
edit: its 14nm