So I have a very thought out question now I have a 4 core phone right? Well my battery life is below average and I was wondering if I had all my cores running at once would it balance out battery life? I just need some help from someone who knows about all this and are all cores mandatory?
Sent From My Liberated E970
You can select how many active cores are activated with trickster mod and (necessary!) a kernel that supports this.
Sent from my Nexus 7 using Tapatalk 4
I know how to and can with my kernel but I need to know if more cores are activated if the battery life will be better or worse
Sent from my Optimus G using XDA Premium HD app
I would definitely take a look in to what my batter usage is and how to control that before I worry about the cores. Just my two cents.
P.S. I am sorry but I believe the Multi-core in the title is spelled wrong.
mr turtle droid said:
I know how to and can with my kernel but I need to know if more cores are activated if the battery life will be better or worse
Sent from my Optimus G using XDA Premium HD app
Click to expand...
Click to collapse
More cores active would mean more processing power, and more processing power requires more energy(atleast on the same cpu), so disabling most of your cores would result in better battery life, maybe by a little bit though.
Hahaha I didn't realize it said mulit
Sent from my Optimus G using XDA Premium HD app
useful topic
It seems to me that by disabling cores wont make a difference to your battery life, only to your performance. It doesn't matter if 2 cores work for 5 seconds or 1 core works for 10 seconds, it is practically the same power consumption
Play around
I would say download CPU-Z from the Play Store and look how much Cores are active and which clock they're at.
Then flash a custom Kernel, which lets you control the clock, govenor and how much cores are active, undervolting may increase your battery life too.
Play with the settings (PLEASE DO NOT RAMP UP THE CLOCKS or set the voltage to the lowest point you can, it may break your phone, stay reasonable, it's not my fault if your phone bricks) and look what's best for you.
Pro Tip: Take a look at the different govenors and look what they do. Google them!
Greetz Leevee33
I hope I could help you a little
Im using trickster mod and I know about all of this I studied up and have undervolted by 200 MV stable but I'm using the hotplug settings to 1:2 so not all 4 cores are active and I get almost two days on one charge!so I guess that does mean less cores use less power
Sent from my Optimus G using XDA Premium HD app
Related
After calibrating, draining and recharging and wiping stats a thousand times, this is what I get:
https://lh5.googleusercontent.com/-...9zLfSiSGJ_Q/s512/screenshot-1321359229108.png
Wtf is that crap?
Sent from my PocketDock
Rouge app, or bad battery
Sent from AT&T SGS2
Viamonte said:
After calibrating, draining and recharging and wiping stats a thousand times, this is what I get:
https://lh5.googleusercontent.com/-...9zLfSiSGJ_Q/s512/screenshot-1321359229108.png
Wtf is that crap?
Sent from my PocketDock
Click to expand...
Click to collapse
2 hours of screen time there, that seems about normal to me. I'm lucky if I squeeze out 3 hours of screen time throughout the day.
Sent from my MB860 using Tapatalk
It depends entirely on what you are doing. 2 hours of screen time (even in ideal conditions) will most likely get through half of your battery.
What screen brightness settings do you use?
What were you doing with the "screen on"? (i.e. gaming, video etc).
What kernel do you use? Try the Faux 1.0 Ghz kernel (if not already) and consider undervolting.
I imagine with the combo of Faux's stock kernel, undervolting and perhaps reducing screen brightness will see 5ish hours of screen time.
It was on around 85% brightness due to being under direct sunlight.
My kernel is faux's 1.45 for CM
Over 80% of the time the clock was around 200, 400MHZ as stated by SetCPU, and both those clocks are undervolted by 50.
I was browsing the whole time.
Viamonte said:
It was on around 85% brightness due to being under direct sunlight.
My kernel is faux's 1.45 for CM
Over 80% of the time the clock was around 200, 400MHZ as stated by SetCPU, and both those clocks are undervolted by 50.
I was browsing the whole time.
Click to expand...
Click to collapse
Wow no wonder. Roaming for 2 hours with brightness nearly on full will definitely drain your battery.v Plus the 1.45 Ghz kernel overclocks the RAM and GPU also. You might want to get an anti glare screen-protector and flash the 1.3 Ghz kernel and use wifi.
I'm on the nightlie 18
Sent from my MB860 using xda premium
rog1121 said:
Wow no wonder. Roaming for 2 hours with brightness nearly on full will definitely drain your battery.v Plus the 1.45 Ghz kernel overclocks the RAM and GPU also. You might want to get an anti glare screen-protector and flash the 1.3 Ghz kernel and use wifi.
Click to expand...
Click to collapse
Umm... wifi wasn't an option back there, and I don't use screen protectors. BUT I didn't know that bit of fact from faux's kernel, I'll put in the 1.3
BTW, Green power pro does help a ****load on keeping battery alive.
ps: anyway to control RAM and GPU clocks the way we do with SetCPU with the... well... cpu?
msd24200 said:
I'm on the nightlie 18
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Why don't u go to a stable version and see if the battery drain continues there also ? You can always create backups to restore right ..
Sent from my MB860 using Tapatalk
Welcome to cm7. I'm lucky to get 10 hours light usage with faux 1ghz kernel undervolted with a screen off profile of 216-216mhz.
Sent from my MB860 using XDA Premium App
jimmer411 said:
Welcome to cm7. I'm lucky to get 10 hours light usage with faux 1ghz kernel undervolted with a screen off profile of 216-216mhz.
Sent from my MB860 using XDA Premium App
Click to expand...
Click to collapse
Have you tried installing better battery stats and CPU spy to see if you have a rogue app? You should be getting significantly better battery life. How is your cell signal?
Sent from my GT-P7310 using Tapatalk
anupash said:
Why don't u go to a stable version and see if the battery drain continues there also ? You can always create backups to restore right ..
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Lol it is stable and my battery life is great
Sent from my MB860 using xda premium
I don't believe setcpu functions correctly for dual core devices, I remember reading, albeit a while ago, setcpu only effects 1 core, leaving the second untamed.
Please correct me if I'm wrong. Stock cm kernel has plenty of ass behind it, no ones playing bf3 on their handsets....yet...
Sent from my MB860 using xda premium
In all actuality, android isn't optimized for dual core devices either. ICS will be.
Sent from my MB860 using xda premium
termleech said:
Have you tried installing better battery stats and CPU spy to see if you have a rogue app? You should be getting significantly better battery life. How is your cell signal?
Sent from my GT-P7310 using Tapatalk
Click to expand...
Click to collapse
Watchdog shows the suspend process and android media process taking up about 30% usage constantly. Signal is strong when I'm at work, constant 4-5 bars H+
Even after a full wipe and clean install of CM7 those same processes throw up alerts immediately, I will get al alert for the suspend process every few mins.
Background data off, no email syncing or anything. I'm lucky to get 3 hours screen on time or pandora streaming. I bought a new Motorola battery about a month ago and I don't use GPS or wifi.
Running stock, aura or homebase and the drain is gone... they aren't any good IMO tho.
For now I'm carrying a spare charger everywhere I go till the nexus prime is released.
Sent from my MB860 using XDA Premium App
JaronBang said:
In all actuality, android isn't optimized for dual core devices either. ICS will be.
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
ICS is still android lol
I know what you meant though. Just saying
Hi all,
I am using a rooted n7.
I have over clocked my galaxy s2 to 1.5ghz before, but I am not sure what is a safe level to over clock the n7 to.
What is a is is for battery life and performance?
And which kernel do u guys recommend
?
Thanks in advance
Cheers
Corey
Sent from my GT-I9100 using xda premium
fishingfon said:
Hi all,
I am using a rooted n7.
I have over clocked my galaxy s2 to 1.5ghz before, but I am not sure what is a safe level to over clock the n7 to.
What is a is is for battery life and performance?
And which kernel do u guys recommend
?
Thanks in advance
Cheers
Corey
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I run trinity kernel on my Gnex and N7 and on my N7 I keep it stock speeds because I've seen no reason to realistically OC it. Most of the improvements I see are from the kernel software changes over stock. You can OC to 1.6 safely but I'm not sure of the power usage difference but I'm pretty sure the loss in power isn't worth the gain from OCing.
Sent from my Galaxy Nexus using xda app-developers app
I have mine at 1.6 just for the hell of it, I get a good 4 or 5 hours of continuous usage out of it.
brando56894 said:
I have mine at 1.6 just for the hell of it, I get a good 4 or 5 hours of continuous usage out of it.
Click to expand...
Click to collapse
For the benefit of the community, can you tell us any major changes at 1.6 GHz?
Is there anything noticeably faster?
Hi, I have a related question but can't post since I'm new.
Using the glazed rom which i like but it apparently has gpu overclock. I would like to know how to adjust that back to stock setting or at least see what it currently is. I found the CPU section but there is no gpu I can see.
Is there a tool I can use?
Sorry for the hijack...at least its sort of on topic
IMO over clocking is a gimmick, its the kernel build
Sent from my Nexus 7 using xda app-developers app
Harry GT-S5830 said:
IMO over clocking is a gimmick, its the kernel build
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
My thoughts exactly. I play some light games and web browse on my Nexus 7.
For those purposes, my Nexus 7 is already extremely fast, so I don't think I would be able to notice if it was over clocked.
But I guess it depends, maybe there's a big difference when running GPU heavy games.
I have OC mine upto 1640 MHz for bench marking alone for half and hour or probably more and it went fine although the tablet was getting warmer more than usual.
Sent from my Nexus 7 using xda premium
Hi,
I decided to flash trinity kernel.
I am currently OC to 1.5yghz, is that a safe level to keep it at full time? Or can that burn the cpu out?
Thanks again
Cheers
Corey
Edit,
I over clocked my galaxy s2 ages ago, and I noticed a huge difference in performance.
So that is why I want to over clock my n7 too lol
Corey
Sent from my GT-I9100 using xda premium
there is no such thing as a safe overclock. overclocking, by nature, carries some risk. that said, i havent seen anyone brick their device from overclocking.
fishingfon said:
Hi all,
I am using a rooted n7.
I have over clocked my galaxy s2 to 1.5ghz before, but I am not sure what is a safe level to over clock the n7 to.
What is a is is for battery life and performance?
And which kernel do u guys recommend
?
Thanks in advance
Cheers
Corey
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Just wondering
Why do you feel the need to OC?
I go to 1.6 but use the Trinity App to go back to stock when OC not needed
Sent from my GT-I9300 using xda app-developers app
I have not over clocked the Nexus 7 yet but one way to test your devices max is to use setcpu. Make sure you do not have "set on boot" option selected. Then step up your cpu. If your cpu can not handle the over clock it will force restart. If you do not have the set at boot selected it will revert back to the last good state on restart.
Each device is different on what it can handle for over clock.
Sent from my Nexus 7 using xda app-developers app
fishingfon said:
Hi,
I decided to flash trinity kernel.
I am currently OC to 1.5yghz, is that a safe level to keep it at full time? Or can that burn the cpu out?
Click to expand...
Click to collapse
To be honest I doubt you'll notice much increase from oc the CPU since the CPU already is so powerful nothing pushes it to max really.
Only thing worth overclocking is GPU really. And at that, your not going to notice a difference unless your playing some intense games.
Can someone please explain to me why none of the kernel's have OC ability?// I think it's due to quad core overheating but I'm not sure and would really love an actual explanation.. Thanks
Sent from my Nexus 4 using xda premium
they all started with OC ability right at the beginning, then .. a good few number of people had HARDWARE bricked devices, that had a fault with the battery no longer being connected or something
they all had overclocking in common, since then , its been removed on most or all kernels
I'm sure that as time progresses it will be made available again. What's the need to clock anyway its fast enough as it is
Sent from my Nexus 4 using xda premium
zephiK said:
I'm sure that as time progresses it will be made available again. What's the need to clock anyway its fast enough as it is
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
This is true, its a 1.5ghz quad core lol why do we need more ?
Also what was happening in some kernels was that mpdecision (which is qualcomms code that says when the cores should be on and offline, i.e hotplug) was using the hardware maxs of each kernel, so if the kernel was capable of going to 1.8ghz, even if you set the max to 1.4ghz ( using software) , mpdecison would override the software and use the hardware max.. therefore.. .it would ramp all cores up to 1.8.. which caused a major cluster ****..
italia0101 said:
This is true, its a 1.5ghz quad core lol why do we need more ?
Also what was happening in some kernels was that mpdecision (which is qualcomms code that says when the cores should be on and offline, i.e hotplug) was using the hardware maxs of each kernel, so if the kernel was capable of going to 1.8ghz, even if you set the max to 1.4ghz ( using software) , mpdecison would override the software and use the hardware max.. therefore.. .it would ramp all cores up to 1.8.. which caused a major cluster ****..
Click to expand...
Click to collapse
Will I certainly don't need it. Would it be nice to have? Yeah but it isn't on the top of my priority list.
What he's saying about mpdecision is true. If you read the change log for Franco kernel he removed mpdecision and is working towards a open platform for kernels. So we should hopefully be seeing more goodies.
Sent from my Nexus 4 using xda premium
UI still runs super smooth at 128MHz, so will setting it to this have any major positive effect on battery life? If not playing games I'm guessing u won't really need all that GPU power.
Sent from my Nexus 4 using xda app-developers app
bump
Well, in technical terms it *should* give you better battery life because it's reducing stress on a main hardware component so it doesn't have to work as hard (the harder it works, the more battery it takes). Same thing with the screen; the lower the brightness, the better the battery.
Sent from my Nexus 4 using xda premium
What app allow you to change GPU speed?
Sent from XDA app
eksasol said:
What app allow you to change GPU speed?
Sent from XDA app
Click to expand...
Click to collapse
I know faux123's kernel app let's you.
Sent from my Nexus 4 using xda premium
android88 said:
Well, in technical terms it *should* give you better battery life because it's reducing stress on a main hardware component so it doesn't have to work as hard (the harder it works, the more battery it takes). Same thing with the screen; the lower the brightness, the better the battery.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Wouldn't it have to work harder for longer because it can't do anything as fast? It isn't like if you set the GPU clock to 487mhz it runs at 487mhz all the time, so ramping up to 487mhz would allow it to finish whatever it is doing faster wouldn't it?
Sent from my Nexus 4 using Tapatalk 2
joshnichols189 said:
Wouldn't it have to work harder for longer because it can't do anything as fast? It isn't like if you set the GPU clock to 487mhz it runs at 487mhz all the time, so ramping up to 487mhz would allow it to finish whatever it is doing faster wouldn't it?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Then wouldn't it be the same with the CPU? When I answered I was thinking like how a CPU would work. I understand your thinking though.
Sent from my Nexus 4 using xda premium
Well I would like to add that the 540 sgx can power the 720P in the Galaxy Nexus... That dino is significantly weaker than the Adreno 320 even over clocked. I run 128 only and it works fine for games and even HD videos(YouTube). To confirm I tried Most wanted, dead trigger, temple run, riptide,etc and there weren't any issues(also toggled vSync). And if you use benchmarks like Epic cidel or antutu you'll see the frames are still pretty high.
So I'll say that 128 or even 200mhz is sufficient for this GPU and most purposes. However a good I/o scheduler and governor are still recommended.
Sent from my Nexus 4 using xda app-developers app
I think another advantage if it runs what you want at a good frame rate is less heat.
I've seen a few post on how to undervolt but I'm still not 100% sure how or if I should, I'm guessing it gives a little bit more battery life ? Also what app would be the best to use ? And the best values to apply
ROM: MAKO-JB-MR2
Sent from my Nexus 4 using xda app-developers app
ryanraven said:
I've seen a few post on how to undervolt but I'm still not 100% sure how or if I should, I'm guessing it gives a little bit more battery life ? Also what app would be the best to use ? And the best values to apply
ROM: MAKO-JB-MR2
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
you have to install custom kernel for undervolting.. and it does not give you battery life..it reduces how hot your phone gets..
It can increase battery life actually, not hugely but ARM processors used in phones use a few watts, wattage is calculated as voltage * amperage, less volts going through the lower the wattage, ergo lower power consumption resulting in extended battery life. /rant
OP you will need a kernel that supports UV (pretty much all non stock) and a UV interface, I prefer trickster mod. Look for core voltage and knock it down a step (-25mV). Then stress test / benchmark, if you don't freeze / reboot then you can knock another 25mV off, keep doing this until you get the minimum voltage your phone remains stable (for me 1025mV @ 1.5GHz). You can then set for the options to stick on boot.
Sent from my Nexus 4 using xda app-developers app