[Q] Charging Current Abysskernel - Galaxy Note GT-N7000 Q&A, Help & Troubleshooting

Hi guys,
can somebody explain, why the charging current is limited to 750mA in the Abysskernel?
Is it possible to adjust the setting to a higher current on a rooted Note?
Haven't found a setting in setcpu or voltage extreme.
When I'm playing games the phone is slowly losing charge due to the less current no matter which charger is use (1A Samsung/1,2A Nokia)?
I use the kernel because there is an 100Hz step in it and BLN.
Thanks in advance.
Regards

I have no knowledge in electricity so i don't know what you're saying, is it that with abyssnote kernel we loose battery (much?) more quickly? Only when there's heavy cpu usage (game) or all the time?

He talks about charging. It seems if the speed of charging the battery is lower then in other Kernels.
Gesendet von meinem GT-N7000 mit Tapatalk

As I've said elsewhere, I would be very surprised if code were controlling the charging levels. I would expect this to be a hardware control.

You can use cpu profile, when charges set at low cpu.

The question remains...
It isn't the low speed, but the fact that it isn't charging/getting enough current to load the battery.
So the battery gets drained even connected to the AC power supply.
Setting a lower cpu speed doesn't really help cos the games begin to stutter.
One even stuttered at full cpu speed.
The fact of the reduced current is even mentioned in the Abyssthread, but not the cause for it.
And I'm not allowed to ask/post in the thread because of the 10-postings-rule.
It's almost similiar to the original car charger not feeding enough current while navigating in the car.

Yes, the kernel decides the maximum charging current. Would be cool if there was a fast charge kernel a it takes forever!
Sent from my superior GT-N7000 using Tapatalk

thor2001 said:
It isn't the low speed, but the fact that it isn't charging/getting enough current to load the battery.
So the battery gets drained even connected to the AC power supply.
Setting a lower cpu speed doesn't really help cos the games begin to stutter.
One even stuttered at full cpu speed.
The fact of the reduced current is even mentioned in the Abyssthread, but not the cause for it.
And I'm not allowed to ask/post in the thread because of the 10-postings-rule.
It's almost similiar to the original car charger not feeding enough current while navigating in the car.
Click to expand...
Click to collapse
Than use different kernel ore older abyss. I think they have higher charge voltage.

thor2001 said:
And I'm not allowed to ask/post in the thread because of the 10-postings-rule.
Click to expand...
Click to collapse
make some more posts here - problem solved.
---------- Post added at 11:48 PM ---------- Previous post was at 11:47 PM ----------
Rigby2011 said:
Than use different kernel ore older abyss. I think they have higher charge voltage.
Click to expand...
Click to collapse
I still don't think the code (kernel) controls that. If it did, how would it work charging when off, anyway? Logic tells me the physical circuits would do the management, That is normal.
---------- Post added at 11:50 PM ---------- Previous post was at 11:48 PM ----------
Zamboney said:
Yes, the kernel decides the maximum charging current.
Click to expand...
Click to collapse
Do you have any evidence or citations for this assertion? Also, without wishing to be rude, do you understand the physics involved? The current is a product of the voltage (fixed) and the resistance (a product of hardware).

thor2001 said:
I use the kernel because there is an 100Hz step in it and BLN.
Click to expand...
Click to collapse
BTW
Apparently on the galaxy note 200 mhz is more energy efficient than 100 mhz even though it is clocked higher.

Tell us why sayinh so
Sent from my R800i using XDA

Q. "I'm going to set scaling min freq as 100 mhz because my kernel supports it. Hope there's nothing wrong in doing that."
A. Wait! You may want to stay away from using 100mhz during screen-off or screen-on states for three reasons 1) It seems 100 mhz uses more power than 200 mhz. According to tests, 100 mhz accounted to 1 W / GHz and 200 mhz to 0.7 W / GHz, when both the cores were online. 2) 200 mhz can finish same task faster compared 100 mhz and thus hit deep idle soon. 3) 200 mhz is the 'sweet spot' of frequency in SGS II. ie, the frequency used in the calculations based on the optimal energy to run (Ex: In Milestone it's 550 MHz). So , 'energetically efficient' frequency for our CPU is 200 mhz.
Click to expand...
Click to collapse
From this thread

@dude18
I know this thread, I have read it before. It felt like the Note saved more battery with the 100mHz-step. Maybe the governor had something to do with it.
-----------------------------------------------------------------------------------
Anyway, I've gone back to stock kernel with root (and waiting for the official ICS, May 2012?).
The charging problem is still there, even with shown 1000mA (cf-root) and current widget.
For example, I've just installed "Shark Dash", while my battery was showing 15% and a battery warning.
I plugged the original samsung charger in and started the game. After 2 or 3 round I quited the game.
The battery has gone down to 13% and would have gone deeper, if I continued playing.
If you do that, after some amount of time the battery jumps to 100% while on charger,
but after unplugging it falls back down to 15% or less. This can't be good for the battery!
Same behavior with Jelly Defence, which even frooze my Note for 1 minute.
It doesn't depend on the game, but the fact that the Note sucks to much voltage and cannot charge
the battery while using it.
Regards

Related

[Q] Overclocking: @ What Mhz R U Running 4 Peak Performance?

Just got my Note
Want to overclock it badly...had my previous HD2 running at 1.5 and it never had a problem occasionally it would overheat and auto reboot but not often...
How fast have people gotten it up to and what seems to be the safe zones? I found that at 1.35 on the HD2 wouldnt overheat no matter what you thru at it....
Have we found any sweet spot overclock speeds yet?
i have seen in many post. its 1700Mhz..
Dear TopOfNewYork,
We have two kernels for overclock; FM Kernel v1.6 and AbyssNote Kernel v3.0... I prefer AbyssNote since it has much more features and updated often...
For both kernels, 3 choices of overclock speed 1600,1664 and 1704...
I use 1600 @ 1300mV daily and heat can reach up to 50c while charging and playing demanding games... On normal use it is around 36c. @1300 mV my cpu is stable...
I dont use 1664 and 1704 since there will be more heat and instability...
For me, the best is using stock clock speed undervolted 1400 @ 1175 mV. Phone doesnt get hot and performance is still impressive...
Kind regards,
Sent from my GT-N7000 using xda premium
that temp speed balance sounds perfect PROTO I used to try to keep my hd2 under 49C what do you think of going with the highest clock speeds and just setting profiles and governors based on temp and battery levels w setcpu?
or will I still experience instability simply by using the higher clocked kernels, I think no but I dont have that much kernel knowledge when it comes to setting the speeds in the kernel itself, i usually leave that up to experienced & trusted chefs
Dear TopOfNewYork,
I dont use profiles since they can cause deep sleep issues( screen off profile i mean )... I overclock with Voltage Control app...
Phone reaches around 50 c while charging and playing demanding games at the same time @1600 Mhz so overclocking to 1600 can be the best choice when not charging and 1400mhz is best for charging... If u use SetCpu app, u can use charging profile and set the clock to 200-1400 Mhz...
I also did 1664 and 1704 with various voltages but got some stability issues so i revert back to 200-1600 as my default...
Here is my voltage settings:
Rom: 4lph4 n3v3r d135 v1.2.2 http://forum.xda-developers.com/showthread.php?t=1424401
Kernel: AbyssNote v3.0 Final http://forum.xda-developers.com/showthread.php?t=1362424
100 ( dont use - makes phone wake-up slow )
200 - 825 mV
500 - 825 mV
800 - 925 mV
1000 - 1000 mV
1200 - 1075 mV
1400 - 1175 mV
1600 - 1300 mV
1664 ( dont use - stability issues )
1704 ( dont use - stability issues )
These are my numbers that my cpu can do... Values may vary phone to phone , cpu to cpu so it is better to test and find the best value for your phone... Hope these helps...
Kind Regards,
is that a commadore logo avatar! wow sick havent seen that in ages but i like it
I can remember getting a "sprite" to bounce around on the 64 as a pup wonderful day
anyway
good post proto...really helpful, and thanks for the links definitely going to try your load out sounds like you tested it properly will let you know if I find any interesting tweaks
TopOfNewYork said:
is that a commadore logo avatar! wow sick havent seen that in ages but i like it
I can remember getting a "sprite" to bounce around on the 64 as a pup wonderful day
anyway
good post proto...really helpful, and thanks for the links definitely going to try your load out sounds like you tested it properly will let you know if I find any interesting tweaks
Click to expand...
Click to collapse
Dear TopOfNewYork,
Commodore; the soul changed my life... Amiga, my forever girlfriend... Memories... Golden age of computing.... And YESSSS we are getting older...
Kind Regards,
and here i thought that when my phone reaches 50 degrees, it is in overheat mode.
nice to know that such temperatures are well within normal expectations when doing heavy tasks.
Hasseno said:
and here i thought that when my phone reaches 50 degrees, it is in overheat mode.
nice to know that such temperatures are well within normal expectations when doing heavy tasks.
Click to expand...
Click to collapse
Dear Hasseno,
I dont advice to run device long time when it reaches over 50c... I guess around 50c-55c is a little bit risky...
Kind Regards,
Hasseno said:
and here i thought that when my phone reaches 50 degrees, it is in overheat mode.
nice to know that such temperatures are well within normal expectations when doing heavy tasks.
Click to expand...
Click to collapse
I have a profile active that it gives me a warning when it reaches 50, and it will downclock too.
PROTOCHIP,
How do you test stability with 1.4Ghz @ 1175mV?
EDIT:
I tried 1.6Ghz @ 1300mV the phone is just too hot to hold
EarlZ said:
PROTOCHIP,
How do you test stability with 1.4Ghz @ 1175mV?
EDIT:
I tried 1.6Ghz @ 1300mV the phone is just too hot to hold
Click to expand...
Click to collapse
Dear EarlqZ,
To Test Stability:
1- Run 3 times "Antutu Benchmark"
2- Run 3 Times "NeoCore Benchmark"
3- Run 3 times "Nenamark1"
4- Run 3 times "Quadrant Standart"
5- Run 30 minutes "StabilityTest"
6- Play 10 minutes of 1080p TS and MKV movies in SW mode with bsplayer or mxplayer
If all these tests passed and if phone doesnt lock then i confirm the Mhz and mV...
For [email protected] , Yes PHONE MAY REACH over 50c while charging and playing demanding games at the same time... While on mobile, phone temperature is between acceptable ranges around 38-46c when playing demanding games... On idle, temp is around 22-28... Best choice is using phone [email protected] or [email protected] depending on the cpu; test and find out if ur cpu can handle this mV... Hope all these helps...
Kind Regards,
What do you use to monitor CPU temps?
EarlZ said:
What do you use to monitor CPU temps?
Click to expand...
Click to collapse
Dear Earlz,
You can use SetCpu widget or "System Panel" app to observe temps. Day by day, u get more experience and can guess the aprox. temp by touching
Also "StabilityTest" app shows temp while running...
Kind Regards,
I have System Panel app and it only shows battery temps, is that a mislabeled CPU temp ?
EarlZ said:
I have System Panel app and it only shows battery temps, is that a mislabeled CPU temp ?
Click to expand...
Click to collapse
Dear EarlZ,
Actually, we all call it as CPU temp... AFAIK, apps can only measure batt temp but it is a clue for us to determine how hot cpu is...
Kind Regards,
PROTOCHIP said:
Dear EarlZ,
Actually, we all call it as CPU temp... AFAIK, apps can only measure batt temp but it is a clue for us to determine how hot cpu is...
Kind Regards,
Click to expand...
Click to collapse
So its really battery temperature and not direct CPU temp?
EarlZ said:
So its really battery temperature and not direct CPU temp?
Click to expand...
Click to collapse
Dear EarlZ,
I guess so... I think batt. temp is parallel with cpu temp...
Kind Regards,

[Q] Undervolted

I've undervolted my device and right now I have
100mhz - 825 mah
200mhz - 825 mah
500mhz - 800 mah
for some reason the 500mhz setting is stable and if I undervolt 100mhz/200mhz even more, I crash.
If I set my minimum processor power to 500mhz would I consume less batter than if I were to use 100mhz/200mhz?
Your phone spends most of its time in the lowest and highest cpu frequencies and just a small amount of time at the intermediate levels. Your undervolt for 500mhz probably isn't stable but it doesn't crash because it's only at that frequency for a very short amount of time. If you set the minimum to 500mhz at that voltage it will probably start playing up.
http:/ /db.tt/iy1bKVoB
graph of my cpu levels
Abit offtopic but what the hell!
I was wondering if there's any risks involved with undervolting?
I don't meen the crashes and freeze ups, but rather more like if there's any risk
to really damage your phone from it?
I have and still do alot of OC in the computer world, and do know what overvolting can do. But i'm still curious about what uv can do to your system.
Maskell said:
Your phone spends most of its time in the lowest and highest cpu frequencies and just a small amount of time at the intermediate levels. Your undervolt for 500mhz probably isn't stable but it doesn't crash because it's only at that frequency for a very short amount of time. If you set the minimum to 500mhz at that voltage it will probably start playing up.
http:/ /db.tt/iy1bKVoB
graph of my cpu levels
Click to expand...
Click to collapse
It's been my minimum even before posting this thread. I just started to wonder.
I've been on it for 10 hours now. I have 45% battery life left. Probably due to my 1700mhz being @ 1350mah right now.
I can assure you, it's VERY stable. It's so SMOOTH. Smoother than just having rocketrom and all that stuff. NO LAGS, NO SHUTDOWNS. ALL STABLE.
I can see better battery life, and CPU Spy says it used up 47% 1700mhz and 40% 500mhz. I think it's giving me better battery life.
It's evenly splitted up probably because I was using lulzactive governor.
but then again I didn't log my previous battery life without undervolting.
Some more insight would be nice.
SweCrow81 said:
Abit offtopic but what the hell!
I was wondering if there's any risks involved with undervolting?
I don't meen the crashes and freeze ups, but rather more like if there's any risk
to really damage your phone from it?
I have and still do alot of OC in the computer world, and do know what overvolting can do. But i'm still curious about what uv can do to your system.
Click to expand...
Click to collapse
There are alot of risks. Minor chance that you will cause hardware damage to your phone but I'm saying VERY minor. Just don't be stupid with voltages, like just suddenly overdropping the voltages. Your processor might die.
It's scary as hell, it crashes alot while testing and all that ****.
Feels good when you get it stable though.
TL;DR
Very slight chance to damage your hardware; only if you're very daring.
It should increase your battery life by atleast 20% if you reach the peak of your processors limit.
Bump, are there no other insights on this? Am I like, the only one who undervolted his/her note?
help
clairenix said:
Bump, are there no other insights on this? Am I like, the only one who undervolted his/her note?
help
Click to expand...
Click to collapse
I want to run 1700mhz as permanent and also wanted to undervolt but i wasnt sure how much by and what the risks are. Reason being is my phone gets hot with heavy usage running at 1400mhz so didnt want to go to 1700. I'll watch this thread with interest
kaos_king said:
I want to run 1700mhz as permanent and also wanted to undervolt but i wasnt sure how much by and what the risks are. Reason being is my phone gets hot with heavy usage running at 1400mhz so didnt want to go to 1700. I'll watch this thread with interest
Click to expand...
Click to collapse
I'm running 500-1700mhz.
Indeed it does get hot at 1700mhz, when I'm playing games but I've only at most played for 4 hours straight.
For what reason would you want to run 1700mhz-1700mhz?
clairenix said:
I'm running 500-1700mhz.
Indeed it does get hot at 1700mhz, when I'm playing games but I've only at most played for 4 hours straight.
For what reason would you want to run 1700mhz-1700mhz?
Click to expand...
Click to collapse
No sorry i meant running it at 1700 max, leaving it stock for the min. I just wanted to know how much i can safely undervolt 1700 by.
I actually have a question. I undervolted my note with SetCPU and I read that Tegrak Overclock Ultimate should be used as well together with SetCPU.
What does Tegrak Overclock do? GPU settings?
Would like to learn that part if anyone has any info.
kaos_king said:
No sorry i meant running it at 1700 max, leaving it stock for the min. I just wanted to know how much i can safely undervolt 1700 by.
Click to expand...
Click to collapse
I undervolted mine by about 100mah. I think I can tone it down by about 25mah more but I'm having a hard time getting it to stabilize.
1350 for my device is completely safe though.
Though, all processors are different. Yours could be better than mine and can withstand more UV-ing.
Goodluck!
liutszho said:
I actually have a question. I undervolted my note with SetCPU and I read that Tegrak Overclock Ultimate should be used as well together with SetCPU.
What does Tegrak Overclock do? GPU settings?
Would like to learn that part if anyone has any info.
Click to expand...
Click to collapse
It's basically the same with SetCPU aside from its voltages.
I do not know if it should be used with SetCPU with the note because from what I've researched. It's only a common practice with SGSII.
Tried setting 100 and 200 mhz to 825. Crashed my phone twice in one day using it, gonna revert back to 875
clairenix said:
I undervolted mine by about 100mah. I think I can tone it down by about 25mah more but I'm having a hard time getting it to stabilize.
1350 for my device is completely safe though.
Though, all processors are different. Yours could be better than mine and can withstand more UV-ing.
Goodluck!
Click to expand...
Click to collapse
Many thanks!
I will just experiment then, i didnt want to do that and then cause hw damage. I'll let you know how my processor gets on

Overclocking the Nexus 4 - Benchmark of application load time = BIG difference

A lot of people say that overclocking the Nexus 4 is useless as it's so fast to begin with, but that turns out to be false, yes, it's useless for making e.g. games run smoother, as they all already do, but it's very useful for reducing loading times, and it turns out that the % of time saved is close to the % of increased clock speed.
My setup: Nexus 4, franco.Kernel updater v9.3.3, Franco Kernel #666, Jelly Bean 4.2.2 JDQ39, Governor Interactive. Angry pigs HD 1.1.0 app loading. Fresh reboot for each speed. I did three measurements for each clock speed and left voltages at Franco's defaults. I would suggest looking into the undervolting threads to figure out how low you can go with voltages, undervolting is good underclocking is usually not.
1026 Mhz 1025mV default Franco
15.4s
15.9s
15.7s
1512 MHz 1150 mV default Franco
11.5s
11.3s
11.3s
1620 MHz 1175mV default Franco
11.1s
10.6s
10.6s
1674 MHz 1175mV default Franco
10.3s
10.6s
10.7s
1728 MHz 1200mV default Franco
10.5s
10.3s
10.3s
Conclusion
12.5% faster clock speed = 8.85% faster load time, which means increasing clock speed is 70% effective at reducing load time going from 1512 Mhz and upwards.
40% faster clock speed = 35% faster load time, meaning that people who think running their device at 1026 Mhz is as good as 1512 Mhz are wrong. Nearly doubling clock speed nearly halfens load time.
The reduction in loading time is reduced a bit as you reach higher frequencies, but it's still 70% effective so every extra Mhz helps cut down the wait. Overclocking the Nexus 4 is meaningless in terms of increasing smoothness IN APP, but meaningful in reducing load times significantly and in increasing the responsiveness of your system.
please tell me for saving the battery and still maintaining a little smoothness
the settings to use
i use faux123 kernel.. i just need the voltage,cpu clock n governer settings
so overclocking makes things faster.. really? who would have thunk. and you just found this out?
my brother uses a galaxy s3, and after using it for a few months he tried my n4... he was amused how fast things open and how smooth everything was, and it was all stock frequencies. i think it makes no sense overclocking this beast, it is already fast enough. +/- a few seconds doesnt make that much of a difference but drains the battery significantly more. just sayin'.
zakoo2 said:
my brother uses a galaxy s3, and after using it for a few months he tried my n4... he was amused how fast things open and how smooth everything was, and it was all stock frequencies. i think it makes no sense overclocking this beast, it is already fast enough. +/- a few seconds doesnt make that much of a difference but drains the battery significantly more. just sayin'.
Click to expand...
Click to collapse
Sorry but little OC can help you save more battery in day to day usage. (If you are not playing only games on your phone).
Sent from SpeedMachine i9100
alen1901 said:
Sorry but little OC can help you save more battery in day to day usage. (If you are not playing only games on your phone).
Sent from SpeedMachine i9100
Click to expand...
Click to collapse
not according to my experiences, and i did play with oc/uc and voltage quite a bit. i always ended up going back to stock on the n4 (not on my old motodefy though) because of the drainage.
So, a 50% increase in clock cycles pushes the performance by a bit.
Who would've thought...?
well that's normal, overclocking = more power draining, more speed; just like with CPU or ram on pc, no rocket science here.
alen1901 said:
Sorry but little OC can help you save more battery in day to day usage. (If you are not playing only games on your phone).
Sent from SpeedMachine i9100
Click to expand...
Click to collapse
OC? Don't you mean Downclocking or Undervolting?
sigma392 said:
OC? Don't you mean Downclocking or Undervolting?
Click to expand...
Click to collapse
Nope , also OC can (in theory) improve battery life because the CPU finishes its task faster.
a pigeon delivered this message.... ** your welcome **
gohan040 said:
Nope , also OC can (in theory) improve battery life because the CPU finishes its task faster.
a pigeon delivered this message.... ** your welcome **
Click to expand...
Click to collapse
But er... Wouldn't it would theoretically need more power and therefore generating more heat than stock frequencies which in turn will have a negative effect on battery life?
sigma392 said:
But er... Wouldn't it would theoretically need more power and therefore generating more heat than stock frequencies which in turn will have a negative effect on battery life?
Click to expand...
Click to collapse
It REALLY depends. I'd say most day-to-day usage, an overclock can actually help save battery by 'racing' to sleep (hurry up, finish, drop to deep sleep on cpu AND radio). I think being on 3g makes it even more pronounced because you're letting the radio drop back down to a lower power state as well as the CPU. So if you need to quickly open an email attachment, and cpu is the limiter, it can help it finish, get off the network, and back to idle state faster and save some battery. Now if you go on running benchmarks instead where you just keep throwing more work at it that's a seriously different story. There is also a point of diminishing returns (usually 1 or 2 steps before the absolute limit, in our case about 1670mhz) but in general, a moderate overclock can help.
sigma392 said:
But er... Wouldn't it would theoretically need more power and therefore generating more heat than stock frequencies which in turn will have a negative effect on battery life?
Click to expand...
Click to collapse
I agree with u, but remember its a theory.. U finish faster so the time it uses more power is less....
^^Look at the post above me, he got a good example^^
The best of both worlds (if your phone is capable to do this) is when u UV and OC. U would use less power on a higher frequency. Win-win in theory.
But I know what u mean and its hard to believe, but I think that's what @alan1901 wanted to say.
a pigeon delivered this message.... ** your welcome **
If you are lucky, you can overclock using STOCK voltage for the maximum clock.
IE, i see many undervolting their phones by alot. I would just try 1150mV (default voltage for 1.5ghz) for your highest speed (OC as high as you can with this voltage), which means you are not using more power, but still making your phone faster.
Haven't tried on mine, but say 1.6-1.7ghz should be possible with 1150mV for a few at least.
No, 50% OC is not = 50% reduced load time
Let me summarize:
OVERCLOCKING > UNDERCLOCKING FOR THE AVERAGE (POWER) USER
You load a lot of apps, you don't play games or watch videos for hours, productivity is your focus. Depending on use you could save probably 1 - 6 hours a year (see assumptions below). Battery gains won't be significant, but spending less time with the LCD/Wifi etc on could give you some gains as the CPU is one of the lower power drain components.
UNDERCLOCKING > OVERCLOCKING FOR THE 3D GAMER
You spent a lot of time playing CPU intensive games, keeping the CPU cores at max clock speed for extended periods of time. In that case you could get some battery life gains at the cost of responsiveness and app loading times - your call.
IN MORE DETAIL
-------------------------------------------------------------------------------------
UNDERCLOCKING + UNDERVOLTING PROs/CONs
+ Reduces CPU temperature, if that matters to you.
+ IF keeping the CPU at max clock speed for extended periods of time, a lower max voltage could give you enough extra battery life to negate the time lost waiting for apps to load - your call.
- Increased load times - even on the Nexus 4 a lot of apps take > 10 seconds to launch, and don't forget in-app load times, reboots etc.
- No significant battery saving in most cases, potential for loss (if doing a lot of app loading you could even get worse battery life as the screen, wifi etc has to stay on for longer, and the screen is the main battery drain).
- Time spent finding stable voltages.
OVERCLOCKING PROs and CONs
+ Potential small battery life gain, as your device spends less time with the screen/wifi etc ON.
++ SAVES YOU TIME. I'm estimating 1 - 5 hours a year depending on usage.
- Times spent finding stable voltages and clock speeds.
-/- Apps does not RUN smoother.
Why 50% CPU does not = 50% reduced load time and why you test things
---------------------------------------------------------------------------------------------------------------------
It'd be more like 40-30% depending on relative clock speed. I did a simple test as we did NOT know that app loading was mainly CPU limited, could have been memory. And If load times didn't go down there wouldn't be ANY reason to OC and underclocking would be a good idea.
Assumptions behind an estimated 1 - 6 hours saved a year by overclocking
---------------------------------------------------------------------------------------------------------------------
Say that you're on average waiting 4 minutes a day waiting for apps to load, rebooting your phone, waiting for web pages to load, waiting for in-app content to load etc.
Overclocking can cut down that wait time up to 10%, that's nearly 1/2 a minute saved every day, 3 1/2 minutes a week, 3 hours a year. This means you can get a good return on the time it took you to overclock your device, assuming you'll keep it for a couple of years. So if that's the case, why not do it? You'll save some time and you'll enjoy using your device a bit more.
Currently I'm OCd at max 1674 Mhz @ 1225mV, otherwise using default Franco voltages and interactive governor. Stable and very snappy Might be able to reduce voltage and retain stability but this is fine.
zakoo2 said:
not according to my experiences, and i did play with oc/uc and voltage quite a bit. i always ended up going back to stock on the n4 (not on my old motodefy though) because of the drainage.
Click to expand...
Click to collapse
sigma392 said:
OC? Don't you mean Downclocking or Undervolting?
Click to expand...
Click to collapse
I said little OC. Example. Stock cpu clock is 1000mhz and 1000mv. Now, you OC your phone to 1200,1300mhz without changing voltage, or by increasing it a little bit(+25, +50mv, to make phone stable), it will use higher cpu frequency with the same voltage like on lower frequency or with a little higher voltage. So it would finish tasks faster, going to idle faster without getting any heat and give you more battery. On my nexus s and galaxy s3, galaxy s2, i tested it, and it helped (about 30min more screen on time for me). But if you play games a lot and doing some heavy tasks then underclock and undervolt are best for you. But on that beast of phone, i woldnt underclock it beyond 1.2, 1.3, not sure what frequencies are there. If you UC that phone a lot, you can easyly go with some weaker phone.
Sent from SpeedMachine i9100
is there any kernel that can overclock with 4.3?
Andre_Vitto said:
is there any kernel that can overclock with 4.3?
Click to expand...
Click to collapse
yes, most of them. some even overclock up to 2052mhz :victory:
simms22 said:
yes, most of them. some even overclock up to 2052mhz :victory:
Click to expand...
Click to collapse
like?
Check the Development sections.
This thread makes my head hurt.

Question about CPU governors

I am looking for a CPU governor I can use with just the root that our AT&T Note 3's currently have. What I would like to do is have a governor so when certain games that are really draining my battery are running that it will lower the CPU and give me better battery life. Is this possible with our current root only? I read that SetCPU had this feature with app based profiles but the recent reviews are stating that the app based profiles are not working correctly. Does anyone have any suggestion of what I could use?
Set cpu is working for me, I have the paid version though. I put it on performance governor and it held 1 core wide open at 2265. I then changed it to ondemand and the core dropped to 300. There's also a conservative, interactive, user space and power save governors. Search governors for explanation of each governors settings/purpose.
Sent from my SAMSUNG-SM-N900A using xda app-developers app
kitsinni said:
I am looking for a CPU governor I can use with just the root that our AT&T Note 3's currently have. What I would like to do is have a governor so when certain games that are really draining my battery are running that it will lower the CPU and give me better battery life. Is this possible with our current root only? I read that SetCPU had this feature with app based profiles but the recent reviews are stating that the app based profiles are not working correctly. Does anyone have any suggestion of what I could use?
Click to expand...
Click to collapse
You can set a profile to lower CPU when your battery gets above a certain speed. That would be your best. Another alternative is to set a max speed for x condition or y. Doing all of the above will lower the performance of your game. It would be best to try different max speeds that still allow you to play your game enjoyably and go from there. Games are just a battery hog, even if you lower your speed it will still take milliamps than you'd prefer. I think off hand to just try, is set max speed at the 15xx speed and just use on demand or interactive. Power save will lower performance too dramatically and possibly kill more battery. Performance is really for the most demanding of games or benchmarking.
Sent from my SM900T.
@rbiter said:
You can set a profile to lower CPU when your battery gets above a certain speed. That would be your best. Another alternative is to set a max speed for x condition or y. Doing all of the above will lower the performance of your game. It would be best to try different max speeds that still allow you to play your game enjoyably and go from there. Games are just a battery hog, even if you lower your speed it will still take milliamps than you'd prefer. I think off hand to just try, is set max speed at the 15xx speed and just use on demand or interactive. Power save will lower performance too dramatically and possibly kill more battery. Performance is really for the most demanding of games or benchmarking.
Sent from my SM900T.
Click to expand...
Click to collapse
so this may be a dumb question, but is 300MHz the lowest clock speed it can reach? I just installed Better Battery Stats on my Nexus 7 (2012) and it can get down to 50MHz. Just looking to conserve more battery. Thanks!
Just get a Zerolemon 10000 mah battery and never worry about what is using your battery again. They are only 50 bucks and that includes the special case/protector to house the phone and the battery.
Solarenemy68 said:
Just get a Zerolemon 10000 mah battery and never worry about what is using your battery again. They are only 50 bucks and that includes the special case/protector to house the phone and the battery.
Click to expand...
Click to collapse
That's not really an option for me. I often rock the phone with no case at all and like it in its 168g form. I already have 30-40 hour batterly life with 3-4 hrs of screen time. But I just noticed the lowest clock speed it 300Mhz and I think it can be lower!
Solarenemy68 said:
Just get a Zerolemon 10000 mah battery and never worry about what is using your battery again. They are only 50 bucks and that includes the special case/protector to house the phone and the battery.
Click to expand...
Click to collapse
Yes! This is my solution. No worries when mpdecision gets stuck on 4.4.2 and stops sleeping cores, who cares?! Pry-Fi running continuously in War mode, booyah.

Undervolting vs Underclocking vs Hotplugging for battery life

Can anyone explain to me what is better?
I know that underclocking reduces cpu frequency, which means lower temperatures and also better battery, but performance is worse, so it takes longer to complete tasks...but if it takes longer to complete tasks, it means it will also have screen on for a longer time right?so it saves power from the cpu, but keeping the screen on for that extra time also means it will consume extra power right?
About undervolting, is it better to undervolt or to underclock when it comes to battery life?i know that with undervolting there is less heat produced because of the reduced voltages. From what i have read (i dont know if it is correct) the power consumption is given by this equation: P = f*c*(V^2) where f is frequency, c is capacitance and v is voltage. It makes sense that reducing voltage means less heat, but if i reduce CPU frequency it also produces less heat because it reduces power. Most of the time i read that underclock is better for battery because it uses less power, but like i said earlier, it takes longer to complete tasks and in result i have to keep the screen on for a longer time.
About hotplugging, i have seen some users with good battery life screenshots, and mentioning that they disabled hotplugging, because they said that turning cores on and off also wastes energy. So is it better to hotplug or not?
would really like to get some answers because i know nothing about this..I also know that i could test each setting and and see which is better, but i dont use my phone the same way everyday so its kind of hard to determine...
Short version and after extending testing (2 cores max, -175Uv, underclocking at 1000 or 1300mHz) with different kernels and always on stock Rom,
the result was that there was no noticeable difference at the battery life with a normal setup of using of 4 cores at normal max freq of 1512mhz.
A custom kernel in comparison to the stock kernel makes more sense cause of the optimization they offer for performance and battery life.
Unleashed from Onda v957m on TDT
RASTAVIPER said:
Short version and after extending testing (2 cores max, -175Uv, underclocking at 1000 or 1300mHz) with different kernels and always on stock Rom,
the result was that there was no noticeable difference at the battery life with a normal setup of using of 4 cores at normal max freq of 1512mhz.
A custom kernel in comparison to the stock kernel makes more sense cause of the optimization they offer for performance and battery life.
Unleashed from Onda v957m on TDT
Click to expand...
Click to collapse
nice to have some feedback from someone that tested=p. what about hotplugging? Today i disabled hotplugging and had always 4 cores on and it does not seem to be wasting more battery than with hotplugging enabled
These studies were done by bedalus on the Nexus S, but alot pertains today. Alot of useful information here
http://forum.xda-developers.com/nexus-s/general/ref-battery-drain-benchmarks-t1478406
Sent from my Nexus 4
n2d551 said:
These studies were done by bedalus on the Nexus S, but alot pertains today. Alot of useful information here
http://forum.xda-developers.com/nexus-s/general/ref-battery-drain-benchmarks-t1478406
Sent from my Nexus 4
Click to expand...
Click to collapse
Also lot of discussion about Uv here
http://forum.xda-developers.com/showthread.php?t=2137034
Unleashed from Onda v957m on TDT
n2d551 said:
These studies were done by bedalus on the Nexus S, but alot pertains today. Alot of useful information here
http://forum.xda-developers.com/nexus-s/general/ref-battery-drain-benchmarks-t1478406
Sent from my Nexus 4
Click to expand...
Click to collapse
totally forgot about bedalus experiments!i had a Nexus S at the time and saw that post, but back then i didnt mess around with anything on my phone so i completely forgot=p.thanks!
The only thing he doesnt adress is hotplugging(the Nexus S was single core so he couldnt even if wanted=p). Anyone care to shed some light on hotplugging?is it really worth it or there are minimal gains?
migueldbr said:
totally forgot about bedalus experiments!i had a Nexus S at the time and saw that post, but back then i didnt mess around with anything on my phone so i completely forgot=p.thanks!
The only thing he doesnt adress is hotplugging(the Nexus S was single core so he couldnt even if wanted=p). Anyone care to shed some light on hotplugging?is it really worth it or there are minimal gains?
Click to expand...
Click to collapse
There are different hotplugging methods.
The stock one as a boost feature, as soon as u touch the screen ur decvice goes to dual core 1026mhz for a couple seconds even if the load is super low.
Custom kernels have many variants on the hotplugging "style". Most of them dont have the touch boost included to save battery (but u can have the same kind of touch boost enabled by the governor, ex: franco kernel). Others simply advise u to turn off hotplugging == less calculation of the load to decide if the device needs to plug it or not + no waiting time to get the performance boost of many cores online (since all 4 are already online) + somewhat more heat since all cores are allways draining battery.
Im no expert and i hope all i said is right, at leats its what i know.
What i personally look for is:
Min core 1
Max cores 4
No touch boost (no heat while u are simply texting via sms on 2G with data and wifi OFF)
sent from my diabetic Nexus 4 (too many KitKats).
C4SCA said:
There are different hotplugging methods.
The stock one as a boost feature, as soon as u touch the screen ur decvice goes to dual core 1026mhz for a couple seconds even if the load is super low.
Custom kernels have many variants on the hotplugging "style". Most of them dont have the touch boost included to save battery (but u can have the same kind of touch boost enabled by the governor, ex: franco kernel). Others simply advise u to turn off hotplugging == less calculation of the load to decide if the device needs to plug it or not + no waiting time to get the performance boost of many cores online (since all 4 are already online) + somewhat more heat since all cores are allways draining battery.
Im no expert and i hope all i said is right, at leats its what i know.
What i personally look for is:
Min core 1
Max cores 4
No touch boost (no heat while u are simply texting via sms on 2G with data and wifi OFF)
sent from my diabetic Nexus 4 (too many KitKats).
Click to expand...
Click to collapse
actually touch boost and hotplugging are different things...touch boost is a feature where as soon as you touch the screen, the cpu ramps up the frequency to the specified touch boost frequency. Hotplugging is a different thing, where cores of the cpu are turned on and off when the phone does not need them to be on all at the same time. I know that touch boost drains more battery, but i dont know about hotplugging...would like to see some tests/benchmarks, but i dont think there are any...
migueldbr said:
actually touch boost and hotplugging are different things...touch boost is a feature where as soon as you touch the screen, the cpu ramps up the frequency to the specified touch boost frequency. Hotplugging is a different thing, where cores of the cpu are turned on and off when the phone does not need them to be on all at the same time. I know that touch boost drains more battery, but i dont know about hotplugging...would like to see some tests/benchmarks, but i dont think there are any...
Click to expand...
Click to collapse
Different things but on stock kernel touch boost is implemented on the hotplug and not the governor.
Any difference btw 4 cores online or hotplugging must minor, and have draw backs on heat wich affects the battery capacity.
Eventhough u can say that hotplugging may drain an amount of battery to plug and unplug cores, i would say its minor.
Talk to @simms22 , he is the "trinity kernel guy", four cores online is a must for him
sent from my diabetic Nexus 4 (too many KitKats).
From my experience, under clocking as well as running a 2 core setup doesn't change anything for the better. Most times for the worst due to a worse user experience.
Undervolting is something that, solely from the physical side, cannot make things worse (unless you under clock too much). Undervolting will make your CPU cores use less current. Less current running through an electric circuit always means less heat, too.
To put it simple:
If my regular voltage at 384mhz is 950mv and I lower the voltage to 800mv and after testing it proves to run stable my device now uses 150mv less on that frequency.
Sent from my Nexus 4 using XDA Free mobile app
Oxious119 said:
From my experience, under clocking as well as running a 2 core setup doesn't change anything for the better. Most times for the worst due to a worse user experience.
Undervolting is something that, solely from the physical side, cannot make things worse (unless you under clock too much). Undervolting will make your CPU cores use less current. Less current running through an electric circuit always means less heat, too.
To put it simple:
If my regular voltage at 384mhz is 950mv and I lower the voltage to 800mv and after testing it proves to run stable my device now uses 150mv less on that frequency.
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
no matter what you do , its still going to be a mediocre battery life , best leave it as it is because the way nexus 4 is designed its still going to be getting annoyingly warm on games
Well, from my own experience undervolting definetly reduced heat and made the battery last longer. Don't expect 2 hours more sot, though. Its most notably while the device is idle.
Sent from my Nexus 4 using XDA Free mobile app
nice man
very helpful...
Help pls..
Can any1 help me undervolting Unleashed kernel.. providing tips or the link ll be vry helpfull..

Categories

Resources