yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] ro_explorer:
If I'm not mistaken ,that is the system battery monitor from MIUI :) ... (I have it in a similar way on my wife's defy)
[Nexus S Android Development] jeffkhlam:
does it include latest ezekeel gps bug fix? also do i just wipe davik cache then flash your kernel if using other kernel? wanna try it out.

thanks in advance.
[Nexus S Android Development] franciscofranco:
Next update will have that yes.
[Nexus S Android Development] roshga:
Its not true.. The battery stats on miui are weird, if he'll turn them off and on he'll see that the phone is not awake, but after its on for a while the stats get ****ed up. I'm having the same picture on my phone and on cpuspy I get like 95% sleep.

Another thing is look at his graph, the drops happens in sync to the screen on time. His screen was on a lot of time, that's why his battery went off. You can't expect to stay with 90% battery the while day when you use it...
[Nexus S Android Development] Cybergr:
Can please someone tell me why I can't overclock over 1200mhz with LiveOC..!?Is there a limit to 120!?
[Nexus S Android Development] franciscofranco:
Yes. Next update will have 150 as a limit.
[Nexus S Android Development] kalinusa:
How can I turn off the BLN lights being activated by default? What is the battery drain from them?
[Nexus S Android Development] mike216:
Best idle time I've ever got but it took 3 charge cycles to get that battery life

Sent from my G1
[Nexus S Android Development] franciscofranco:
Yes that's normal, but in general users don't understand. I never ever ever got battery drains in the 3 phones that I owned, and battery always took 2/3 charge cycles to get perfect.
[Nexus S Android Development] mike216:
That's normal with deepidle mod? Because I've never had that good idle time on other kernels with deepidle build into them, Im really loving this and certainly appreciate it

Sent from my G1
[Nexus S Android Development] mike216:
Get bln apk from the market and disable it

Sent from my G1
[Nexus S Android Development] franciscofranco:
The extra battery power from my kernel comes from other places, not just deep idle. With the latest deep idle fixes from Ezekeel I expect the battery power to be even better. It's already running on my Nexus, and I'll be testing it for the next days to make sure everything is perfect :) obviously full credits to Ezekeel for the fixes, I did nothing but cherry-pick them.
[Nexus S Android Development] coloxim:
But I don't understand why...

Idle depending from charge cycles ...???

Inviato dal mio Nexus S
[Nexus S Android Development] franciscofranco:
It's not idle that needs charging cycles, its the battery that needs charging cycles to have it perform like it should. This has been explained 50 thousand times in thousand other websites and forums ;)
[Nexus S Android Development] Maximilian Mary:
This is where it gets interesting...

Bus & gpu will now be overclockable to 300 MHz. :eek:

What happens to the phone that tries to run @ 300 and can't handle it? Fire roasted hummingbird? Or just a freeze & reboot?
[Nexus S Android Development] coloxim:
Ohh..okey..sorry...forgive me...:p

Inviato dal mio Nexus S
[Nexus S Android Development] mike216:
Well I'm certainly looking forward to it and I appreciate the fact that you test before releasing to the masses,

I'm looking for another NS to have when this one gets old because of your kernel and nscollab,I like the prime and will more than likely get one but I'm not going to ever abandon my NS si if anyone knows where I can get one for a decent price Please PM me and if its cheap enough ill throw you something for a finders fee,thanks a bunch franco

Sent from my G1
[Nexus S Android Development] jodtalingchan:
Thank you, Franco for your amazing work. It's a good combi with nscollab indeed. I just wonder this is my second charge after flashing yr kernel. I noticed that when the phone is in deepidle state, sometimes it drains around -20mA and sometime shows -2mA. I just don't get it. what causes that? You might have any ideas and get me to gain the best performance of yr kernel.

I'm running +10% live oc with stock voltage 440/1100 conservative

Once again greatly appreciate your work
[Nexus S Android Development] jodtalingchan:
after fully charged it was drained -2mA and later it was getting higher .. I have no clue. There was no awake in between.
[Nexus S Android Development] franciscofranco:
Something definitely woke the phone from idle, otherwise it wouldn't need more power.

Both of you what frequencies, min and max, were you using?

Anyway with the latest fixes from Ezekeel everything should be even better according to my initial tests.
[Nexus S Android Development] jodtalingchan:
liveoc 110

max 1100

min 440

conservative gov

stock voltage

should I turn sync off?
[Nexus S Android Development] ho0o0o11111:
I just flashed this kernel yesterday with rom Nexus MX 10.26.

With max frequency set to 800 and lazy governor, battery just dropped 1% in my 7 hour sleep!!!! Amazing.

Thanks for your good work.
[Nexus S Android Development] jodtalingchan:
Just curious that once turning the screen off, the phone will enter the deepidle stage or it will wait for a while ... ?
[Nexus S Android Development] franciscofranco:
That might be the issue. With Auto-sync on apps can make network requests as they see fit so they can keep waking the phone up ;)

I think it will enter deep idle as soon as the background tasks that can keep the phone awake are finished, not 100% sure though.
[Nexus S Android Development] mike216:
Just throw auto sync in your drop down along with your data for easy excess if you want the maximum battery life,toggle on and off as you need to

That's one of many reasons CM is great. Atleast that's what I do

Sent from my G1
[Nexus S Android Development] doc_v15:
So..it has to do with the usage then? :D
[Nexus S Android Development] mike216:
I seen your post over at Ezekiels thread! I'm definitely excited for the next release! I'm definitely not rushing, just saying

Sent from my G1
[Nexus S Android Development] mike216:
I've noticed that also it seems like the weaker the battery gets the higher voltage that app shows

I'm certain its still going to deep sleep because my battery says so lol..

That app could be off some and by running intervals every 5 minutes it could be getting in the way

Sent from my G1
[Nexus S Android Development] saranyan:
Brilliant work franco :),

Flashed your kernel with oxygen and it has been brilliant after one charge cycle.

68% after 15 hours, Just brilliant. I lost just 2 % in my 8 hours of sleep, Other than that with moderate usage, Very good battery life. Keep up the good work!

Edit: Btw, I have uv'ed 100 and 200 Mhz by 50 and all other frequencies by 20, Stable for my phone. No reboots.
[Nexus S Android Development] mike216:
Smartass v2 feels very quick does anyone know if its better than conservative or lazy on battery any help would be appreciated

Sent from my G1
[Nexus S Android Development] mike216:
I hope you enable the screen off profile in lazy+ as default but im sure you know what's best for us all,thanks franco sounds good over on deepidle thread :-)

Sent from my G1
[Nexus S Android Development] caleb1783:
i read it as well.. sounds great!

Sent from Divinus Nexus S...
[Nexus S Android Development] jodtalingchan:
Something must stop my phone from idle but how do I find out? Should I use lower min freq or stick at 440 since I read somewhere that deepidle works well at this freq ...
[Nexus S Android Development] jai134:
Hello. Was on stock rom with your kernel. Had some difficulties with LiveOC. Newbie to this. In any case, my question is: What should I mount as rw to be able to echo 110 to oc_value? Can do it with es file manager, but I like to use the terminal.
[Nexus S Android Development] roshga:
Yeah... Of I'd use the phone like you do I'll have the same battery.. The deep idle helps on idle mode. Look at the graph where the screen was off.
[Nexus S Android Development] notabene:
So, after some testing :)

Brainmaster .21 ROM, your kernel from 27.10, everything stock(frequencies+voltages).

Really satisfied :)
[Nexus S Android Development] skinniezinho:
Well guys to see how awesome this kernel is, I went to bed with 72% battery and wake up with 73%! :D

Perfect!

It may be because in earlir I charged the phone completely and wiped battery stats.=)
[Nexus S Android Development] franciscofranco:
Nice to see nice feedback again after waking up :) Next update will be awesome I guarantee!
[Nexus S Android Development] al_madd:
whats more beside ezekeel bugfixes??
[Nexus S Android Development] franciscofranco:
You'll see when it's ready.
[Nexus S Android Development] magrejh:
I had the longest battery-time on 21 October version of this kernel.

And some people said same word with me.

Would you make Special version of this kernel that has LiveOC but anything else is just same with 21 October version?

I think It will be best kernel for some people.
[Nexus S Android Development] doc_v15:
+1, confirmed!

Quicker, smoother than lazy and conservative eventhough I have no idea what smartassV2 is :D
[Nexus S Android Development] Ezekeel:
Smartass (both V1 and V2) does not properly use the low frequency states and stays at the higher frequency states even for the smallest loads. No surprise that it does a good job at appearing smooth, however it will drain you battery quicker.
[Nexus S Android Development] doc_v15:
Thanks for the clear explanation Ezekeel!

Could you also assist us with the other scaling governor's description? I really dont have any idea about all of them :P
[Nexus S Android Development] notabene:
Use google :)

http://themikmik.com/showthread.php?5541-GUIDE-Comprehensive-User-s-Guide-to-Kernels

+ performance

The CPUfreq governor "performance" sets the CPU statically to the highest frequency within the borders of scaling_min_freq and scaling_max_freq.

+ powersave

The CPUfreq governor "powersave" sets the CPU statically to the lowest frequency within the borders of scaling_min_freq and scaling_max_freq.

+ userspace

The CPUfreq governor "userspace" allows the user, or any userspace program running with UID "root", to set the CPU to a specific frequency by making a sysfs file "scaling_setspeed" available in the CPU-device directory.

+ ondemand

The CPUfreq governor "ondemand" sets the CPU depending on the current usage. To do this the CPU must have the capability to switch the frequency very quickly. There are a number of sysfs file accessible parameters: sampling_rate, show_sampling_rate_min, up_threshold, ignore_nice_load, sampling_down_factor.

+ conservative

The CPUfreq governor "conservative", much like the "ondemand" governor, sets the CPU depending on the current usage. It differs in behaviour in that it gracefully increases and decreases the CPU speed rather than jumping to max speed the moment there is any load on the CPU. This behaviour more suitable in a battery powered environment. The governor is tweaked in the same manner as the "ondemand" governor through sysfs with the addition of: freq_step & down_threshold

+ interactive

The CPUfreq governor "interactive" is designed for latency-sensitive, interactive workloads. This governor sets the CPU speed depending on usage, similar to "ondemand" and "conservative" governors. However, the governor is more aggressive about scaling the CPU speed up in response to CPU-intensive activity. The tuneable value for this governor are: min_sample_time & go_maxspeed_load

+ smartass (By erasmux@XDA)

The smartass governor is a complete rewrite of the interactive governor. CPU spends much more time at the lower frequencies for improved battery life. It gives the phone an automatic Screen Off profile, keeping speeds at a minimum when the phone is idle.

+ savagedzen (By jsseidel@XDA)

SavagedZen is a governor based on the Smartass governor. With tweaks to paramaters which control how much and how fast cpu ramps up/down. Main difference versus Smartass is that cpu ramps down not in fixed steps, but based on cpu load heuristics, i.e. when cpu load falls below threshold (min_cpu_load), cpu immediately ramps down to a frequency derived from the measured load.

+ interactiveX (By imoseyon@XDA)

Modified version of interactive with suspend code which locks at lowest clock speed when screen is off. Has a sleep+awake profile, meaning you don't need to set up manual profiles, it will lock at your minimum frequency during screen off
[Nexus S Android Development] doc_v15:
SWEEET!!! Now its like a new revelation to me!

Thanks buddy!
[Nexus S Android Development] Ezekeel:
Purely judging from the description, a properly tuned SavagedZen governor could be useful (for the time the screen is on) since it should spend more time on lower frequencies than the original smartass.

Since there are a lot of different governors testing which governor is the actually the best during screen-on will require a lot of benchmarking. However that is something which does not involve much technical knowledge and most people should be capable of. So if a lot of you help with this and run benchmarks for the different governors with different parameter configurations, it surely can be done.

Just grab a movie, a movie player (I used MoboPlayer) and CPUSpy and start benchmarking:

0. Enable Airplane mode.

1. Reset stats with CPUSpy.

2. Switch to movie player and start playing the movie from the start up to a certain point (about 5min should be enough).

3. Switch to CPUSpy, update stats and make a screen shot.

Then switch to another governor or change the parameters and repeat steps 1-3.

Currently the king-of-the-hill seems to be lazy (I used 10000/40000/80 as parameters which is my daily driver) and I officially challenge each and everyone of you to find a better governor + parameter configuration which does better than lazy and runs without problems also for other screen-on tasks (I do not care about screen-off) like games, browsing, listening to music, and so on.

Post the results in the lazy thread please.
[Nexus S Android Development] thomasck:
Well, no problems so far. Very snappy, fast and stable!

Incredible performance at 1GHz!

Bom trabalho!
[Nexus S Android Development] yaachi:
i tried to compile a kernel with your source with 28 oct commits, after using a while(like 20 mins or more), the network(wifi/3g) would stop working, had to reboot to get it work again. Tried 29 Oct too, it still exists, now trying 27 oct commits to have a control experiment.
[Nexus S Android Development] mike216:
This was nice to wake up too I know it can't be too long

I'm putting 24th,and 27th in the archives for safe keeping and wiping out all my old clutter after 4 days with this kernel it definitely proved to be king kernel

No need to OC and colors are perfect

Great experience franco certainly appreciate it

Sent from my G1
[Nexus S Android Development] kalinusa:
Thank you so much for the guys who replied about BLN turning off. I had an older version of BLN and this is why I was not doing it right.

I have one more question please.

I did not quite get the whole LiveOC method thing. So i have Root Explorer or ES File Manager with Root, is there a file I have to edit in order to write the new 110 value. Does it necessarily have to be through the Terminal.

I went with root explorer to the folder /sys/class/misc/ and then there was not liveoc folder. It was a file I think. I tried opening it with notepad through Root Explorer but nothing happened.

thank you for helping me.
[Nexus S Android Development] mike216:
Use terminal emulater and enter this exactly how you see it below

echo 110 > /sys/class/misc/liveoc/oc_value

Then hit enter,you might have to raise voltages but I wouldn't unless you experience a reboot, good luck

Sent from my G1
[Nexus S Android Development] al_madd:
use android mate
[Nexus S Android Development] jai134:
Just open the file oc_value with ES and edit it with ES. I did so and that raised my cpu-freq.

Sorry. To late.
[Nexus S Android Development] jai134:
Do you have busybox installed? If so try to use this command from terminal: find -a | grep oc_value that will give you an answer if the file exists.
[Nexus S Android Development] kalinusa:
Thank you guys it worked.

it was an error with ES File manager, the Root feature was giving me an error so I reinstalled it and then I was able to access the LiveOc thing.

Now I am waiting for the updated Kernel version.

I have been having 1 reboot per day and 1-2 complete freezes -> battery pools, but I am not sure if it is the CM Nightly or the Kernel.

But definitely a tid bit unstable. Especially when I am messing around with the Camera
[Nexus S Android Development] mike216:
To get rid of your reboot please try these two things

Unckeck dithering in cyanogen performance settings and reboot and if that doesn't fix it (did for me) raise the voltages some and set your min at 400 if you haven't already

Sent from my G1
[Nexus S Android Development] franciscofranco:
Yes that seems like being a ROM issue, nightlies are nightlies.

Now I'm going to do a little testing and experiments regarding loading modules and some other neat things like loading optimized minfree settings, loading optimized ext4 mounting options etc...Then when I'm satisfied I'll release the update.

Just a little preview of what's coming:

- First and entirely BFS kernel with the newest 0.413 version

- Optimized the tunable BFS parameters for extra interactivity and smoothness

- More debugging disabled - I'm pretty sure 99% of the debugging flags are now disabled

- All the latest bugfixes and implementations from Ezekeel

- Small change to the lowmemorykiller module

- Added some minor improvements and tweaks

- Work in progress: a modular system to enable/disable few tweaks like optimized minfree values, optimized ext4 mounting flags, logcat on/off etc
[Nexus S Android Development] Lazat:
Looking forward to it :D
[Nexus S Android Development] Ezekeel:
Did you manage to find the problem with the DEEP IDLE stats not working?
[Nexus S Android Development] franciscofranco:
Haven't tried yet, that's what I'm gonna do next but it should be because printk is disabled or something like that.
[Nexus S Android Development] PLEEZEFRAGME:
heyho, is it possible to post the stock voltages for your kernel? I am running LiveOC with 115 (460-1150mhz) right now an in Proton Voltage control it says me the existing voltages are

Speeds= 100-200-400-800-1000-1200-1300-1400

Voltages= 100-100-100-950-950 - 1050-1200-1250

some can´t be right here
[Nexus S Android Development] Ezekeel:
Nah, I doubt that it is related to printk. Take a look at /sys/devices/system/cpu/cpu0/cpuidle/state0/time and /sys/.../usage. If time is 0 but usage not 0, it probably is related to some timer that is not enabled.
[Nexus S Android Development] franciscofranco:
Proton Voltage is ****ed up with my frequency table, use SetCPU.

Both time and usage show 0.
[Nexus S Android Development] SA-07:
Lmao ;)
[Nexus S Android Development] mike216:
Stock voltages

Sent from my G1
[Nexus S Android Development] Cybergr:
Please Franco don't forget to raise the overclock limit to 150..Thank u once more for your hard work..I am looking forward for your latest update..
[Nexus S Android Development] mike216:
He's got us! Professionals rarely make mistakes lol..

Sent from my G1
[Nexus S Android Development] doc_v15:
So, I just fully charged my phone to 100% on 11.30pm. Wiped battery stats, calibrated my battery using battery widget pro.

Slept for 5 hrs, 6% decreased :D Not bad, considering whatsapp, Go Chat for YM, FB messenger, gtalk were running in background. 2G network, 15% brightness.

Now, 7.46am battery is 82% (running about 8hrs and 16 min), after texting, whatsapping, newsfeed, friendcaster for FB for 30 min. :D

Scaling governor smart_assV2 :D

Thanks franco!
[Nexus S Android Development] mike216:
Have you tried lazy it might help some with screen on use and on the next release lazy +, Governor (not sure if its really named lazy+)

Is going to be the champ of all governors

And if you read through the op that whatsapp is a battery hog some users have found

Sent from my G1
[Nexus S Android Development] doc_v15:
I havent tried it, the lazy, will do after the next cycle battery :D

Yes, I'm aware that whatsapp really sucking out battery so much, too bad I need it like crazy :p

What governor that you are using now? How was it?
[Nexus S Android Development] mike216:
Lazy,after lots of testing I think it handles battery life best and is quick,smartass is good but I'd rather have the battery conserving governor

Sent from my G1
[Nexus S Android Development] doc_v15:
Hmm..I will try it after tonight when my battery dies :D

Thanks man!
[Nexus S Android Development] caleb1783:
i would like to test bfs... thanks franc.

Sent from Divinus Nexus S...
[Nexus S Android Development] mike216:
We all will be soon!

Sent from my G1
[Nexus S Android Development] idelgado782:
One issue I've cross across with this latest release but not with the others is signal loss. I get it more than 3xs a day but had never had it with the 2 previous releases. Not sure what it could be.
[Nexus S Android Development] yaachi:
Kernel built from 27 oct commits doesn't have the issue. I'm using crespo + cm nightly.
[Nexus S Android Development] mike216:
+1 as a matter a fact it cured my radio dumps on nscollab

On another note I didn't know we can take really small steps in liveoc like 105,very cool for those like me who dont like to go with high OC

Sent from my G1
[Nexus S Android Development] vis80k:
does CPU SPY app show deep idle status correctly? I mean, does its "deep idle" mean the same as deep idle in this kernel?
[Nexus S Android Development] mike216:
Honestly I dont think so be when I ran other kernels before deepidle mod came out I would get deepsleep stats but it can tell you several things like what governors use different frequencys and other useful stuff you may want to gauge

Sent from my G1
[Nexus S Android Development] morfic:
Francisco, do you also not get any stats?

You no longer get reboots when camera has been used moments before putting phone to sleep? (power button)

Trying to see where my kernel differs.

Since Ezekeel is on 2.3.3 his feedback is not too useful.

It's only certain that I can stop reboots when disabling didle.
[Nexus S Android Development] xdviper:
The battery life is amazing but the performance is horrible? Its been really bad since I've installed this on oxygen.

I mean, apps will take a while to start, such as Twitter, messages and such. I don't use any task kilers even though I have atk installed.

Any reason why? I haven't downloaded any new apps since I've flashed this except for weather channel, mint and evernote.

Any ideas?

And mind you, I'm coming from a HTC sensation which obviously is better in specs but I thought this would be as good.
[Nexus S Android Development] mike216:
Blazing fast on nscollab for me and another bazillion people here might wanna try another rom

I passed that up for my NS and soooo glad I did,not hating just no development and of course SAMSUNG

Sent from my G1
[Nexus S Android Development] doc_v15:
Hmm.. your comment is really contradictive to all of us has experienced..

There must be something wrong with your tom..

try to do FULL CLEAN install ROM and kernel. Wipe data/cache and see how it goes.
[Nexus S Android Development] Zorrich:
Hi there,

Just wanted to let you know that I am also running oxygen 2.3.1 with Franco kernel, and I have no slow downs at all. Actually, it is probably the fastest combo I've tried, and trust me I've tried them all. As previously suggested I would do a full wipe, and try again.

Edit: I'm on stock settings too, other than min frequency set to 400.
[Nexus S Android Development] Flying Fox:
Thanks for this brilliant work!!!

Two questions:

1, do I have to enable deep idle or is it already enabled in this kernel?

2, I tried to raise the bus speed by entering echo 120 > /sys/class/misc/liveoc/oc_value in the terminal emulator but after rebooting the settings went back to 100. Any idea?

Thanks for helping!