Database Info

Fresh Toast 2.1 - OC Widget vs. SetCPU

Could anyone help me out with this? I was using SetCPU, but I had heard about its constant processor use and "instability" (jumping down to 19MHz?). So I switched to OC Widget, but I'm having some issues with battery life. I had it set to 767MHz max/min when the screen was on and 245? max/min when the screen was off (I always had SetCPU on "performance"). However, I seem to lose battery like crazy with this for some reason! I switched to 245min/767max with the screen on, and I seem to lose battery much slower, but I will get a bit of lag sometimes (especially when typing something). Any assistance?

TheBiles said:
Could anyone help me out with this? I was using SetCPU, but I had heard about its constant processor use and "instability" (jumping down to 19MHz?). So I switched to OC Widget, but I'm having some issues with battery life. I had it set to 767MHz max/min when the screen was on and 245? max/min when the screen was off (I always had SetCPU on "performance"). However, I seem to lose battery like crazy with this for some reason! I switched to 245min/767max with the screen on, and I seem to lose battery much slower, but I will get a bit of lag sometimes (especially when typing something). Any assistance?
Click to expand...
Click to collapse
Via Flipz's website:
Overclock Widget vs SetCPU: Up until now toast and I have been pushing SetCPU because it allows us to create a custom file that tells it what clock speeds the rom is capable of running at which makes things nice and easy. However a couple of bugs have come up lately. First off is that it is constantly using 10-15% of the processor when it shouldn’t even be doing anything. That doesn’t sound like a lot but that’s pretty extreme. The second issue is that it doesn’t seem to be honoring the settings you pick. I could tell it that I want the minimum to be 245mhz but I would catch it at 19mhz. Or vice-versa I tell it that I want the max to be 650mhz and I catch it at 767mhz. With that said, toast took the time to program settings in to the kernel that will now allow you to pick “automatic” off of the device selection rather than custom. This may resolve the issue, so just keep an eye out for it if you use SetCPU. In OC Widget just go in to settings and click “Detect frequencies” to have it read them. If you have no preference then I’m personally saying to use Overclock Widget. It isn’t quite as user friendly as SetCPU, but it gets the job done right. Additionally as a 3rd reminder: make sure if you are running Fresh Toast that you DO use one of these applications, and if you are running Fresh Rom that DO NOT run one of these. Doing so can cause slowdowns.
Click to expand...
Click to collapse

drummingfool said:
Via Flipz's website:
Click to expand...
Click to collapse
Yes, I read that. That is where I got the information about SetCPU being funky.

I wish I could help, but I'm in a "noob-state-of-mind" right now...how the hell do I find OC Widget? I see it no where!
Thanks,
Tee Jay

I wish I could help, but I'm in a "noob-state-of-mind" right now...how the hell do I find OC Widget? I see it no where!
Thanks,
Tee Jay
Click to expand...
Click to collapse
"Overclock widget" in the Market.
-------------------------------------
Sent via the XDA Tapatalk App

Thank you, I might take a look!

I don't know how much you use your phone, but to say I use mine heavily is like calling Rosie a bit chunky. The settings I use are min:652.8 max:767 while on
min:19.2 max:247 while sleeping. I get roughly 6 hours batter life. But I literally use my internet for around 6 hours every day, plus calling, texting, email etc.
I'd imagine, if you use it less, you'd get much better battery life.
Edit: Oh! And I run MUCH more stably with OC widget than setcpu.

[Kernel]Experimental 2.6.35 with Automatic Voltage Scaling (AVS)

This kernel is based on Thalamus's Oxygen Kernel but with AVS and he's given me permission to post it here for testing.
I implemented AVS from scratch (based on the Code Aurora kernel) and it seems to work well for me.
AVS uses some hardware to emulate the longest gate delays through the CPU datapath. If the delay is longer than expected, the CPU voltage can be decreased, if shorter then it can be increased. This means that the CPU is always running near the minimum voltage it requires and because power consumption rises with the square of voltage this is a good thing.
Here are the results of some initial tests (full load, no idle):
Clock Speed, Without AVS, With AVS
1113600,234mA,223mA
998400,207mA,190mA
768000,158mA,138mA
499200,111mA,93mA
384000,90mA,79mA
245000,70mA,64mA
So there are power savings of about 8-15%
All patches are initially pushed here:
https://github.com/dzo/kernel/tree/2.6.35-bravo-exp
and should end up here:
https://github.com/thalamus/kernel/tree/2.6.35-bravo-exp
You can see the current status of AVS by doing:
Code:
cat /sys/module/avs/parameters/status
Doing:
Code:
echo 1 > /sys/module/avs/parameters/debug
will put lots of debugging info in the kernel log.
To disable AVS do:
Code:
echo 0 > /sys/module/avs/parameters/enabled
The minimum voltage is set to 900mV but you can change this using e.g.:
Code:
echo 850 > /sys/module/avs/parameters/vdd_min
Putting too low a value in here will crash your phone because AVS seems to have trouble with low frequencies.
I also added some extra frequency steps, 76.8MHz and 192MHz.
Don't expect huge power savings, the CPU is only one of the things using power on our devices.
I think AVS is a nice idea and I'd like to know how stable it is on other people's phones.
To install, flash the attached update zip from recovery.
Please don't use this kernel unless you are fairly well informed about what you are doing.
15/4/12: Updated kernel with higher vdd_min

Going to give this a test now, I'll report back later.
How did you produce those mA readings btw?

have you tried using other kernels like Eviolets one? does it really save much more battery than EVs?
is it 100% stable??
with the kernel using some hardware to calculate the voltages needed wouldnt it take some more power to get the calculations done?

cez10 said:
have you tried using other kernels like Eviolets one? does it really save much more battery than EVs?
Click to expand...
Click to collapse
Why don't you try it and find out instead of asking questions.
is it 100% stable??
Click to expand...
Click to collapse
I think the words '[Kernel]Experimental' in the thread title are a clue.
with the kernel using some hardware to calculate the voltages needed wouldnt it take some more power to get the calculations done?
Click to expand...
Click to collapse
The overhead of the calculations is negligible.

So this is only for gingerbread AOSP ROMs or works on Sense as well?

lvnatic said:
So this is only for gingerbread AOSP ROMs or works on Sense as well?
Click to expand...
Click to collapse
Oh my...people just want to be spoonfed on XDA these days.
This kernel is based on Thalamus's Oxygen Kernel
Click to expand...
Click to collapse
As Oxygen is an AOSP ROM it's fairly clear that it's not going to be a sense kernel isn't it?

Thanks for sharing this.
What are the available governors? I can't find this information on github.
Will switching between governors (depending on phone state) cause any issues with the voltage change, that aren't advised?

_thalamus said:
Oh my...people just want to be spoonfed on XDA these days.
As Oxygen is an AOSP ROM it's fairly clear that it's not going to be a sense kernel isn't it?
Click to expand...
Click to collapse
He never mentioned it is specifically for AOSP or Sense ROMs. I was wondering if this is just a separate script, not kernel dependent. But if I give it a 2nd read then yes, it seems indeed it is an entire kernel, my bad, no need for a spoon...or w/e it means.

lvnatic said:
He never mentioned it is specifically for AOSP or Sense ROMs. I was wondering if this is just a separate script, not kernel dependent. But if I give it a 2nd read then yes, it seems indeed it is an entire kernel, my bad, no need for a spoon...or w/e it means.
Click to expand...
Click to collapse
Don't listen to Thalamus. He has no time for people less "knowledgeable" than him. There was a time where I thought a kernel was a kernel.
I thought I had escaped his unhelpful comments when I left Oxygen thanks to his attitude (if you don't like his attitude, then tough is the general gist of it). If he was a shop owner he would go bankrupt, quickly, as he has no people skills whatsoever.
If he wasn't a dev, he would be labeled a troll, yet he is allowed to get away with being nasty to people. When will XDA introduce a -thanks button?
I think the saying goes, if you don't have anything nice to say, then don't say anything at all.

Thanks, this one looks like a good project
As to stability: i've been using this kernel for a couple hours without issues, with very small draining btw; anyway a few minutes ago the phone became unresponsive: i was just typing a message with whatsapp, clocked 192x806, and a freeze occurred. A soft reset did the trick.
Keep up the good job
Edit: i'm on beta 2 fyi...

chronicfathead said:
Don't listen to Thalamus. He has no time for people less "knowledgeable" than him. There was a time where I thought a kernel was a kernel.
I thought I had escaped his unhelpful comments when I left Oxygen thanks to his attitude (if you don't like his attitude, then tough is the general gist of it). If he was a shop owner he would go bankrupt, quickly, as he has no people skills whatsoever.
If he wasn't a dev, he would be labeled a troll, yet he is allowed to get away with being nasty to people. When will XDA introduce a -thanks button?
I think the saying goes, if you don't have anything nice to say, then don't say anything at all.
Click to expand...
Click to collapse
Hahahahahaha.
That cheered me up, I'm having a crap day.
Happy to be of assistance.
Edit: You prove how little you know about me by saying that I have no time for people less knowledgeable than me. That is totally untrue. I spend a lot of time helping people who are less knowledgeable than me. What I have no time for is laziness, people who won't help themselves or idiots. There is a big difference.

_thalamus said:
Hahahahahaha.
That cheered me up, I'm having a crap day.
Happy to be of assistance.
Edit: You prove how little you know about me by saying that I have no time for people less knowledgeable than me. That is totally untrue. I spend a lot of time helping people who are less knowledgeable than me. What I have no time for is laziness, people who won't help themselves or idiots. There is a big difference.
Click to expand...
Click to collapse
I only base my observation on posts of yours that I have read. Rather than shooting people down, advise them so they can improve their knowledge.
sent by touching my Desire

In Airplane mode i had 2mA battery usage all night without AVS and 5mA usage with AVS. This is via Battery monitor widget.

Xinot said:
In Airplane mode i had 2mA battery usage all night without AVS and 5mA usage with AVS. This is via Battery monitor widget.
Click to expand...
Click to collapse
AVS has nothing to do with power consumption while the device is asleep. When the phone sleeps, the CPU is power collapsed, i.e. is completely powered down. AVS only changes the voltage while the CPU is awake.

The Kernel work great on Miui 1.4.8 since 2 days! No reboot or freeze... and in idle with JiuceDefender, 652Mhz max ondemand over 3h the device lost only 2% accu
Thanks for your work
Sent from my HTC Desire using XDA App

I've just updated the kernel in the first post to increase the minimum voltage and remove some possibly unstable frequencies.
Should be more stable now.

dzo said:
AVS has nothing to do with power consumption while the device is asleep. When the phone sleeps, the CPU is power collapsed, i.e. is completely powered down. AVS only changes the voltage while the CPU is awake.
Click to expand...
Click to collapse
OukkiDoukki! So i have something else going on here...

Thanks running sweet keep up the great work using on GV 2.0
Sent from my HTC Desire using XDA Premium App

cez10 said:
have you tried using other kernels like Eviolets one? does it really save much more battery than EVs?
is it 100% stable??
Click to expand...
Click to collapse
Just a quick post to say that I've been testing this kernel for 2/3 days (actually the version that Thalamus has in his experimental github) and find the battery usage to be the same. But the AVS code seems much cleaner than the implementation I have.
As for stability, I haven't had a single crash yet. And overall speed seems better than on my kernel.
Quadrant also confirms this.
Regards,

EViollet said:
Just a quick post to say that I've been testing this kernel for 2/3 days (actually the version that Thalamus has in his experimental github) and find the battery usage to be the same. But the AVS code seems much cleaner than the implementation I have.
As for stability, I haven't had a single crash yet. And overall speed seems better than on my kernel.
Quadrant also confirms this.
Regards,
Click to expand...
Click to collapse
Do you think you will be compiling ManU 1.5 from this source then?

[Q] Kernel suggestion for underclock

I am running Cognition 4.4.8, which will not allow OC/UC. I actually just want to UC. What recommendation would you have for a kernel compatible with Cognition 4.4.8 for Captivate that would allow me to UC?

Don't you mean oc/uv? I don't think you know what you are talking about.

Yeah its UV (undervolt). Find any kernel that allows it and is working with your ROM. Maybe ask in that thread as others could be using a custom kernel for that exact reason.
Sent from my SGH-I897 using XDA Premium App

UC is a real term, maybe he meant he wants to limit his clock speed to 800mhz. What's that called if not UC?
Although undervolting and underclocking to save battery is a waste of time. The cpu doesn't use that much battery in the first place, the screen and the modem use the most power, you want the charge to last switch to the lowest brighteness and 2g, that will give way more battery than uc/uv will.

studacris said:
UC is a real term, maybe he meant he wants to limit his clock speed to 800mhz. What's that called if not UC?
Although undervolting and underclocking to save battery is a waste of time. The cpu doesn't use that much battery in the first place, the screen and the modem use the most power, you want the charge to last switch to the lowest brighteness and 2g, that will give way more battery than uc/uv will.
Click to expand...
Click to collapse
+1 on the battery topic. Even at a high OC the battery drain is not that much worse... a little yeah but not too severe.
Also good point about UC.. wasn't thinking about that at all ..underclock what!?!?

some people falsely think that the phone runs at 1ghz all the time, when in fact it downclocks itself and ramps up clockspeed when it needs it....so unless you have an app thats using 100% CPU all the time, your phone is running around 200mhz at idle.

Pirateghost said:
some people falsely think that the phone runs at 1ghz all the time, when in fact it downclocks itself and ramps up clockspeed when it needs it....so unless you have an app thats using 100% CPU all the time, your phone is running around 200mhz at idle.
Click to expand...
Click to collapse
+1 again Although there are different governors that do different things most phone at stock will idle down to 200mhz. My phone for instance idles down to 800mhz, but thats just my prefrence

Yep, I meant OC/UV. I typed too fast for my own good!

Good points
Thanks for the message on how little battery undervolting saves. That was quite helpful. I did try the discussion board for Cognition, but no one seemed to be posting on using an alternate kernel, which is why I asked for recommendations here.

I believe Cog is KB1 based, so this kernel should work: http://forum.xda-developers.com/showthread.php?t=988805

Thanks I will certainly trie eXist's kernel.

Ernesto47 said:
Thanks I will certainly trie eXist's kernel.
Click to expand...
Click to collapse
If you want the best battery life, I suggest something other than cognition. In my experience, i9000 based custom roms get better battery life.
Sent from my CM7 powered captivate

@sixstringsg I notice that you are using Cyanogenmod. I keep looking at that, but since it was still not listed as stable, I was not sure whether to try it. How are you finding the stability?

[Q] A question about overclocking

Hi,
having registered here some time ago i've been reading many threads about custom ROMs and the kernels used. Many of them seem to support overclocking your phones CPU. The thing i'm wondering about is that there's kernels which actually overclock your CPU to double the speed its CPU is supposed to be running on (!!), giving the CPU some more voltage i believe.
Actually i'm a bit sceptical about how setting the CPU to such sick frequencies has a bad effect on the CPU's lifetime. The way i understood the problem with clocking the CPU high is always the heat development, meaning without proper cooling the CPU will simply "melt away" (at least that's how it is on desktop computers). Of course, CPU's on smartphones are not cooled or anything. Now that there seem to be many people here, developpers or not, who got deeper into the hardware, probably already opened up a phone, or have some experience with the long term consequences of overclocking.
So my final question is: What is safe and what is not? I saw for the Galaxy 3 for example exist different kernels, some non-overlock kernels, as some kernels only doing limited overclocking up to 800 MHz (which seems to be the most healthy option to me), but also some kernels overclocking up to 1300 MHz, which as i said seems kinda sick to me. Well i bet there's someone out there with a bit more experience than me regarding this so i'd be thankful for any answer.

I believe its safe as long as you dont keep the phone at high overclocked spds all the time. Besides, this chips are designed to last 5 years at least so if you overclock and shorten its life, you would have already changed your phone. In short, dont worry, just dont leave your phone at above 1000mhz all the time
Sent from my GT-I9003 using xda premium

bscraze said:
Besides, this chips are designed to last 5 years at least so if you overclock and shorten its life, you would have already changed your phone.
Click to expand...
Click to collapse
You got a point there hehe. Technical progress is moving in light speed. Anyway, i want to make my phone last as long as possible of course. But it's true, with CPU stepping it won't run on the highest frequency the whole time, even if overclocked, so i guess that overheating won't be an issue.

The only time i overclock is when im playing 3d games. Other times mine is 700mhz at most
Sent from my GT-I9003 using xda premium

hi bscraze..,& others...
pls share ur setcpu setings...i've started a thread in Q&A...so that we can get an idea...
i'm always using 1200mhz...is it safe...??

LooksLikeSmart said:
hi bscraze..,& others...
pls share ur setcpu setings...i've started a thread in Q&A...so that we can get an idea...
i'm always using 1200mhz...is it safe...??
Click to expand...
Click to collapse
No.. 800mhz should be your main profile. When charging i put 1200mhz 300mhz on demand. You shouldnt always leave it at 1200mhz. Only when you need it
Sent from my GT-I9003 using xda premium

LooksLikeSmart said:
hi bscraze..,& others...
pls share ur setcpu setings...i've started a thread in Q&A...so that we can get an idea...
i'm always using 1200mhz...is it safe...??
Click to expand...
Click to collapse
if you use a governor like OnDemand/Conservative, your phone wont always be on 1200 but usually on the lower values...It will go only to 1200 when needed

[INFO] Achieving good battery life!!

I want to share my setup with you guys for getting good battery life which lasts the day without making you compromise on the features. The primary things I've seen on the forums so far has a lot of involved setup and frankly by the time you get it perfect, you will flash a new ROM and have to re-do a lot of it and so on, overall it's not the worth the hassle.
This is usually what my days look like and I manage to last the entire day:
I keep wifi and GPS on always, regardless of whether I'm using it or not.
Get a fair bit of calls because I live away from family so they all call a lot (I have a massive family, so we are talking about 5-6 hrs of talking everyday).
I like to read news from news republic and I'm subscribed to a lot of stuff there so I go through like 2000+ articles in a given day.
XDA like every few hrs (damn ICS!).
Text messages are also flowing throughout the day with the woman being on the other side of the country and all (100+ a day?).
I have facebook on push (not an addict but active enough to mention)
My gmail, school and exchange are all on push for email so they I see a fair bit there
The setup is VERY easy to setup and replicate. It doesn't require you to lose out on features or use your phone at an anorexic level either. You don't need a task manager or watch your processor non-stop either.
So without further delay, here we go:
Pick a ROM
I'm using Seanster_GBaxe EX v1.5.1 from the T-Mobile section, you can find it here.
Get faux's kernel
The reason for this particular one is because it's given the best results when it comes to undervolting and overclocking without SOD. You can find the kernel here.
Get System Tuner
This is available on market. There are alternatives but for this post, I will be making all the references from this app.
Get the AGPS patch from crypted
This isn't for battery directly but it does get locks VERY fast and you waste less clock cycles getting the signal. Less clock cycles wasted, more battery saved. The patch is available here.
I personally use the v3.0 Google CWM Build (scroll down his post and you will see it)
Get the V6 SUPERCHARGER from zeppelinrox
This is available here. Why the beta one? It works fine.
Okay, at this point you can pretty much store these things together in a neat little folder on your SD card because it makes a perfect library. So let's get started, I'll assume that we are starting from scratch. The order for everything will be as follows:
Get into recovery and install your ROM
This I shouldn't have to explain, the instructions you can find on the ROM thread.
Install the kernel
Same with this, read the kernel thread.
Install the GPS patch
Same with this as well
Boot into ROM
Hmm.... hopefully you can manage this
Restore all your backups and apps, accounts and whatever else
Using titanium here is always good
Install System Tuner
Okay, let's get started. Although faux has done an amazing job with the kernel, there's always the personal bias that goes into making things so his balanced settings might not reflect yours (nor mine but you will be tweak even those soon).
Inside System Tuner, go to CPU:
The first you thing you should choose is whether you want to keep the 1.72 GHz OC or not. I kept it but if you want to get even more you can lower to stock 1.56 GHz or go even lower, your choice. Once you set the max, set the min to 384 MHz. Set it once and you don't need to do it again after. Leave the governer to ONDEMAND.
Now go to the Voltage tab:
Be careful here, this can crash you if you go too far. What we do here is globally undervolt, you can do that by hitting the -12.5 mV button over and over. I use -75 mV (press the button 6 times, for those bad at math). Keep in mind that all chips are NOT THE SAME!!! -75 mV might be too much for you or you might even be able to get to -100 mV, find out by doing it.
Now go back to the CPU tab and hit Boot Settings:
Hit Screen-off behavior:
Governor - No changes
Max frequency - 384 MHz (push doesn't lag at all still so don't worry about notifications)
Max frequency/in call - 384 MHz (yes, calls don't require full blast, they work fine even under 500 MHz)
Now go back
Hit Governors behavior:
Sampling rate - Unchanged (faux has it done perfect)
Up-threshold - 75 (what's this? This means that the CPU will scale to higher frequencies when the load is above 75%)
Power-save Bias - 70 (what's this? This means that the CPU will be "biased" towards lower frequencies when load is below 70%)
Setting the Power-save Bias higher than the Up-threshold is obviously stupid so make sure you did it right.
Now go back
At the bottom, there is a whole bunch of tweaks:
Hit Re-apply CPU settings, choose init.d script (you can choose boot too but init.d works 100% of the time)
Hit Boost app loading, choose init.d
Hit Clear cache, choose init.d
Now go back
Find the Startups section and disable whatever you don't want running at boot (this is purely a personal thing).
Install V6 script
His instructions are very good so I'll assume that you have gotten it installed. Once you have it running, choose option 9, the 1000 HP one. Reboot. Run script again, make sure you've got it at 100% supercharged. Done. Reboot just to be sure again.
All done! Now, I know that was lengthy but here's the awesome part. Make a titanium full backup of System Tuner and you NEVER have to do that again for ANY ROM as long as you use the same kernel!! The script is unfortunately the only thing you have to re-apply, probably that has a quick setup too but I'm new to it so I can't give you shortcuts on it.
Hope you have luck with this and it works for you. I promise nothing and if you break your phone please don't come crying to me because you chose to do this yourself. It works for me so I shared it!! Any suggestions are welcome of course.
Note: NO task manager required!! I will modify this for cm7 if needed.

nice job. thanks a lot!

You're using the rc6.1 correct?
Sent from my SAMSUNG-SGH-I727 using xda premium

Thanks for the detailed write-up.
Are you in an LTE market? A full day on LTE would be pretty awesome.
For the screen-off behavior, do you think one can get away with using the smartass governor instead?

I'm using the RC6, tad older I guess.
Sent from my SGH-T989 using Tapatalk

jedah said:
Thanks for the detailed write-up.
Are you in an LTE market? A full day on LTE would be pretty awesome.
For the screen-off behavior, do you think one can get away with using the smartass governor instead?
Click to expand...
Click to collapse
I'm not in LTE area :-(... Would be nice because that's why I got the phone but then I had to move so can't say anything about LTE.
As for smartass, what kernel are you using? Smartass works very similar to the modified ondemand settings that I set up so it wouldn't make a difference as far as I forsee.
Sent from my SGH-T989 using Tapatalk

I tried this, will post results later. Thanks for the great tutorial

If you could post screen shots of your CPU Spy that would be helpful! How well does your phone do on going into deep sleep? On average from what to what time does yours last you? I'm just skeptical about setting the screen off behavior cause that usually prevents the phone from going to Deep Sleep.
Sent from my SAMSUNG-SGH-I727 using xda premium

DANIEL133337 said:
If you could post screen shots of your CPU Spy that would be helpful! How well does your phone do on going into deep sleep? On average from what to what time does yours last you? I'm just skeptical about setting the screen off behavior cause that usually prevents the phone from going to Deep Sleep.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
You're right about the deep sleep, don't let it go into deep sleep. It lasts me 12 hours normally. I'll get you screenshots when I get a chance.
Sent from my SGH-T989 using Tapatalk

Mine goes into deep sleep with screen off behavior setup.
Sent from my SGH-T989 using XDA App

kr3w1337 said:
You're right about the deep sleep, don't let it go into deep sleep. It lasts me 12 hours normally. I'll get you screenshots when I get a chance.
Sent from my SGH-T989 using Tapatalk
Click to expand...
Click to collapse
Dont you think the phone waste alot more battery though when it doesn't go into deep sleep? I've also found that WiFi tends to create a nasty wake lock. My set up is Sky ICS Speed with Faux Clock 1.296 ghz max -384 mhz min. -37.5 u/v LTE on all day, extremely heavy usage. 12 hour battery life on average.
Sent from my SAMSUNG-SGH-I727 using xda premium

InstigatorX said:
Mine goes into deep sleep with screen off behavior setup.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Which kernel are you using?

kr3w1337 said:
Which kernel are you using?
Click to expand...
Click to collapse
Using faux kernel with foxstar rom.
Sent from my SGH-I727 using XDA App

DANIEL133337 said:
Dont you think the phone waste alot more battery though when it doesn't go into deep sleep? I've also found that WiFi tends to create a nasty wake lock. My set up is Sky ICS Speed with Faux Clock 1.296 ghz max -384 mhz min. -37.5 u/v LTE on all day, extremely heavy usage. 12 hour battery life on average.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
From what I've noticed with the faux kernel, it goes into deep sleep after some time on it's own, regardless of the screen-off behavior. I haven't opened up the source to check it out for a better explanation but that's something I doubt is worth exploring since the performance doesn't take any hit.
I haven't chosen to underclock to 1.2 but it should do better than the 12 hrs I get now if I did do that. I have a tendency to start GTA 3 and start playing whenever I get bored so that's why I went OC rather than under. For others looking strictly to use the phone with minimal gaming, this would be a good option. LTE isn't available in my area so I can't test with it but the WiFi radio uses just as much battery as the LTE, if not more I have a feeling.
Trying eugene's kernel from today to see if the lionheart governor does better than the current setup. I will know in a couple of days because every ROM flash needs a couple of charge cycles before it accurately shows battery status.

InstigatorX said:
Using faux kernel with foxstar rom.
Sent from my SGH-I727 using XDA App
Click to expand...
Click to collapse
Do you get any SOD? Everything working okay? Is the setup different than what I've got up there? Would like to know and try it out, can update the OP accordingly.

Just finished with eugene's kernel and the results were pretty disappointing. Looks like the second core is always kept on regardless, faux's kernel turns the second core offline until usage demands need it.
If anyone knows how to tweak eugene's to stop that from happening, do share.

kr3w1337 said:
Just finished with eugene's kernel and the results were pretty disappointing. Looks like the second core is always kept on regardless, faux's kernel turns the second core offline until usage demands need it.
If anyone knows how to tweak eugene's to stop that from happening, do share.
Click to expand...
Click to collapse
Can you clue me location of his latest ROM? Or is it somewhere in the Macnut thread on TMO side of the fence?

InstigatorX said:
Can you clue me location of his latest ROM? Or is it somewhere in the Macnut thread on TMO side of the fence?
Click to expand...
Click to collapse
Using darkside ROM at the moment with the faux kernel, had the Eugene kernel but I noticed that the second core is kept alive regardless of usage and that wasn't helping so I changed back to faux.
Sent from my SGH-T989 using Tapatalk

thanks for the awesome write up!
Did it last night, and lasted the day without a sweat! However, my min frequency wont stick? I have it set to stock frequency 1.5, using faux kernal, and my voltages arent as low as yours (im not a crazy user like you.. maybe an hour of talking a day, lots of texts and emails tho), but i cannot get my min frequency of 3xx to stay. Suggestions?
Thanks!
edit- running stockMod v1.0

im sorry, i have a hard time believing you talk for 6 hours and scroll thry 2000 pages of web and get a day of use. I myself could get about 1.5 days on battery strictly by staying home, connected to wifi all day and barely talking on the phone. i would like to see a screenshot of battery usage at the end of your day