yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] mike216:
I was afraid of bfs because previous ones I tried made my colors weird but this bfs kernel looks great! Just like cfs

So far its really quick but I already figured that! Will report back later after I put my phone through a beating, thanks franco your a genius my friend :)

Sent from my G1
[Nexus S Android Development] JmPTaz09:
11/1 kernel running really nicely on CM7 n.241 with liveoc 120% set to 960/480 lazy. (1230 &1080 volts respectively) Very fast/smooth, etc. My phone won't handle 125% OC without some major tweaking that is not worth it. The above is quick and should use battery fairly.
[Nexus S Android Development] :
Running lazy with 400 min 800 max (no live OC) voltages:

400 MHz 950

800 MHz 1125

using setcpu.

Sent from my obnoxious finger using Swype
[Nexus S Android Development] mike216:
Dam dude I honesty thought it would be hard to top the 27th version but this kernel actually is slightly faster and I'm starting to like this bfs scheduling and battery life with lazy is crazy good just listened to 40 minutes of tunes and barely lost any battery ,excellent job ,how many others love that he test before release and because of it see what we get! :) running perfect on nscollab I9020T

Sent from my G1
[Nexus S Android Development] mike216:
Hows that at 1000 40 UV across the board

Sent from my G1
[Nexus S Android Development] mike216:
Your way under! Nice what rom are you on ?

Sent from my NSCOLLAB + FRANCO'S 01 BEAST
[Nexus S Android Development] :
This is with Carbon 1.1

Runs flawless, quadrant (!) 2950. No reboots. Expecting good battery hopefully. Will run this setup for a few days.

Sent from my obnoxious finger using Swype
[Nexus S Android Development] yaronyud:
i gotte ask why did you wanted to make a BFS ker instead of CFS i tryed some kernels with both CFS & BFS i couldn't noticed any big differences... so maybe you can tell us why BFS is "better" or why you prefer it over CFS??
[Nexus S Android Development] mike216:
Cfs are generally better for multitasking and bfs are better on focusing on individuall task

Cfs completely fair schudeling

Bfs brain f*+- sceduling

Sent from my NSCOLLAB + FRANCO'S 01 BEAST
[Nexus S Android Development] franciscofranco:
Because I wanted to see users feedback on a BFS kernel. CFS is a multi tasking scheduler, is good all around but doesn't focus very much on the foreground task, while BFS on the contrary focus much of the processing power into the foreground app giving it extra juice and still maintaining the multi-tasking power from CFS. I'm happy with it, but I needed users feedback, I'm just one man with specific needs and every user uses its phone differentially thus the needed feedback on different environments.
[Nexus S Android Development] mike216:
One thing I like about bfs is certain apps will lag once in a while but bfs tends to get rid of the lag because of the focus on the task

Every bfs kernel ive ever tried before coming to francos kernel made my colors really dull but not this bfs version! I dont know what you did different but the colors are perfect

Sent from my NSCOLLAB + FRANCO'S 01 BEAST
[Nexus S Android Development] coloxim:
sorry...but if i listen the music with sreen oof...the cpu stays always at max freq!!!???
[Nexus S Android Development] Maximilian Mary:
Since flashing 11/1, my data connection has dropped a number of times, requiring a reboot to get it back. This has happened on other kernels recently, but I don't recall noticing it on 10/27.

Ns4g

Euroskank CM kangs

D720SPRKE1 radio

Live_oc @ 110
[Nexus S Android Development] DebauchedSloth:
Same here. This exact thing.

CM7.1, nightly 241.
[Nexus S Android Development] JmPTaz09:
I just experienced this as well; not sure if it's kernel or rom related. I'm on CM7 nightly 241.

Seems us 3 that just mentioned it are running versions of CM, could be related to that and not kernel.
[Nexus S Android Development] kevinngck1:
Nice with cherry kang 1101. Good respond with this lastest kernel :D
[Nexus S Android Development] DebauchedSloth:
A very good point. I'll back out to the 10/27 kernel and see what I see.
[Nexus S Android Development] franciscofranco:
Yes, that is intended, read Deep Idle and Live OC threads for more information about that behavior.

The data drops might be rom related, nightlies are not a very good enviorment, usually not stable and with broken ****.
[Nexus S Android Development] al_madd:
I9020T..

CM 7.1

LIVE OC

stock voltage

I got alot of reboots..

just flash your kernel at 12.00am.at that time battery level 10%.charging.get into the bed..

woke up around 5 am..unplugged...I reboot many times...

from 100% , reboot until my phone 89%....
[Nexus S Android Development] coloxim:
this thing is terrible....my phone stay always to max freq....i've to change kerne!!!
[Nexus S Android Development] DebauchedSloth:
Could be, but so far 10/27 is rock solid with the same ROM. 11/1 lost data pretty quickly.

I've seen two distinct data loss behaviours: with wifi, I still show signal, but cannot get out to the internet - but the indicator stays green. On the cell network, I get the white indicator.

Again, have only seen this on 10/27 with everything else the same.

Will keep testing.
[Nexus S Android Development] Flying Fox:
11/1 seems solid with KelLMSKing MIUI Mod 2.4.1, no problems with wifi.
[Nexus S Android Development] franciscofranco:
Do as you want, I told you to read the threads, if you don't want to learn that's your problem. Just think it like this, you don't want to waste time learning, if I didn't waste my personal time creating the kernel there would be no kernel for anyone, so if you're not willing to waste some of yours to learn something then suit yourself and change kernels.
[Nexus S Android Development] DebauchedSloth:
That should be 11/1. Does not reproduce with 10/27, at least not yet.
[Nexus S Android Development] jodtalingchan:
When entering deepidle stage, it's nescessary that the phone drains at -2mA? Mine is drained -9mA. Is this normal? I've lost 7% in 7 hours after full charge with liveoc 110 running 440/1100 lazy on nscollab

Btw, so far I like this bfs, also have tried other bfs kernels and their color are dull. This 11/1 is very good in color. Thanks again franco :)
[Nexus S Android Development] coloxim:
no...i know...and i've read..but i stupid use the max freq for listen the music...

and when i connect to usb the phone stay always at the max freq...is no good thing..

I know that you di it for deep idle..

don't be angry friend...
[Nexus S Android Development] Flying Fox:
Just took a look to CPU Spy and found out the same behavior. But when screen is on, the cpu calms down to the min. frequency. Don´t know the reason for that. Tomorrow I´ll try another kernel, just for comparison.

Anyway 1/11 is a dream, fast and stable under my settings: 400min, 800max, UV -50mV, lazy gov. Tomorrow I´ll know more about battery drain.

Many thanks franco!!!

edit: the frequency-behaviour is concerning to deep idle? I´m following the whole thread, seems that I´ve missed that part ;), sry!
[Nexus S Android Development] boostern:
Guys, if you only read the deepidle and the liveoc thread you know why it uses the max freq (and not max but the 800mhz frequency).

@franciscofranco

I don't know if it is just coincidence or it is something related to usb (I read that while the phone is connected to usb deepidle is disabled), but turning off "usb debug" has given better battery...maybe usb debug leave on the adb daemon and the phone behave like it is connected to usb?
[Nexus S Android Development] franciscofranco:
The frequency behavior is caused my screenoff_maxfreq change by Ezekeel... This is the explanation:

It's really max frequency!

Dunno, but if it seems to give you better battery then good :)
[Nexus S Android Development] coloxim:
But if i use my phone like iPod..my battery drain so fast..or not?

Inviato dal mio Nexus S
[Nexus S Android Development] boostern:
Ci sono i grafici proprio nel primo post del deepidle, basta leggere!
[Nexus S Android Development] franciscofranco:
Thank you, maybe in italian he/she understands.
[Nexus S Android Development] mike216:
Noting wrong with this kernel and be sure you don't have a rom that's a work in progress and know to have issues for that purpose alone before you blame your issues on this kernel

You might wanna go through at least 2 full charge cycles before you know how battery life is :)

Sent from my NSCOLLAB + FRANCO'S 01 BEAST
[Nexus S Android Development] JmPTaz09:
I agree, typically, but N 241 and most recent nightlies have been extremely stable. I moved up to 242 but still had the data drop with 11/1 kernel. I've moved back to CM7 standard kernel and all seems well for now... will see if I still get the data drop and will report back.
[Nexus S Android Development] ellesshoo:
Running CM7 #241, liveoc causes my phone to lock in on max frequency (lazy, ondemand, screen off and on, deep idle off and on) . Tried Matrix with exact same scenario and it works as expected. Hopefully this helps to get to the bottom of this.
[Nexus S Android Development] mike216:
I'm no fan boy but it does get frustrating when people don't do there research before they slam a good kernel and then complain about it . On a nightly complaining about issues

Sent from my NSCOLLAB + FRANCO'S 01 BEAST
[Nexus S Android Development] got2best:
sorry if this is a n00b question... i am wondering what lowmemorykiller module is..?
[Nexus S Android Development] franciscofranco:
It's just a file inside the kernel that defines what happens when the system is running out of memory..or better, it controls how the system behaves RAM wise.

I'll rephrase my changelog, it's not a module, it's just a file called lowmemorykiller.c ;)
[Nexus S Android Development] DebauchedSloth:
This makes sense if deep idle is available, but when I'm listening to music with screen off, deep idle generally isn't an option - whereas 100mhz is. An hour of listening to music shows almost all of it spent at 100mhz, a bit at higher frequencies, virtually none at deep idle. The phone is low-level busy all the time. Can't idle. This change is locking it at a higher frequency than it would otherwise be able to achieve.

The same would be true of just about any ongoing activity, but music playback would be the most common.

Edit: Unless it can now race to idle. Duh. Will have to try it and see how it does.
[Nexus S Android Development] franciscofranco:
Yes, but deep idle is activated, so it works fine. The device enters deep idle as soon as the screen is off so even with music its working, thus locking at max frequency being thebest option :)
[Nexus S Android Development] Lazat:
Sorry, I really tried to search for this, but with all the recent changes its hard to be certain about some things.

My questions:

Is screen_off.maxcpufreq (for deep idle) set automatically when I change maxfreq in scripts/setcpu?

Running a minfreq at 100mhz (for screen on) wont affect deep idle anymore right?

Can I keep morfics 98tweak? Cause I wiped that one and I cannot seem to find where you add your tweaks to dirtywriteback, lowmemkiller and so on. And with that one wiped, lowmem returns to android default.

Thanks for a great kernel!
[Nexus S Android Development] boostern:
Playing flac:
[Nexus S Android Development] franciscofranco:
max freq is automatically changed for deep idle yes don't worry.

I still advise 400mhz as minfreq, not lower.

Yes you can keep that file. The dirty writeback tweaks are already enabled in the kernel files, but the minfree aren't, they are set by init.rc so even if I change them inside lowmemorykiller they are reset back to the roms default, so yes you can keep the minfree settings from that file ;)
[Nexus S Android Development] Lazat:
Thanks for your answer :) okey, then I set minfreq to 400.

Had understood it wrong and thought that the minfreq would only apply to screen on (and thus save me battery when the screen is on and deep idle is out of the equation) and that it wouldn't interfere with deep idle to kick in and stay in while screenoff.
[Nexus S Android Development] from1989:
how to set the minfreq at 400 with script??
[Nexus S Android Development] Lazat:
In /system/etc/unit.d make a file with the permissions like the rest of the files in there. Or just copy this into an existing tweak file.

# enable liveOC and set maxfreq and minfreq

echo 800000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

echo 400000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

echo 110 > /sys/class/misc/liveoc/oc_value
[Nexus S Android Development] from1989:
thanks but do you find it lost more power when we listening to the music screen off? it seems can not kick into deepidle
[Nexus S Android Development] thoth77:
data connection issues

In minutes after boot, data connection drops on CM (stable 7.1.0.1)

So I tried 11/1 on Oxygen 2.3.1, data connection works fine

I think Roms based on CM have trouble with 11/1
[Nexus S Android Development] mike216:
I'm getting crazy battery life! This might be a 48 hour with moderate to heavy use

I can't say enough how much I appreciate this, best damn birthday present I got today lol.. thanks a bunch franco ! :)

Not only is data good for me on nscollab but getting that great signal in my basement also on 01

Sometimes things doing go so smooth on a flash but I would reflash your favorite modem if your having data dropping issues,I've done this in the past on other kernels and it worked

Sent from my NSCOLLAB + FRANCO'S 01 BEAST
[Nexus S Android Development] JmPTaz09:
Yep, something not playing well together... I flashed standard CM7 kernel back and no more data drop... Seems to be a specific problem to recent CM7 builds... odd since this is based off the CM7 kernel. Hope it gets sorted, as that's my favorite rom (cm7) and this is my favorite kernel (franco).
[Nexus S Android Development] franciscofranco:
I can have a look, but I haven't touched any wifi/data stuff :(
[Nexus S Android Development] from1989:
thanks for your excellent works but do you find it lost more power when we listening to the music screen off? it seems can not kick into deepidle
[Nexus S Android Development] franciscofranco:
I really get more battery life out of it than before. Ezekeel just released a small bugfix maybe that fixes any problems that were left, I'll patch it up and see.
[Nexus S Android Development] timeToy:
I can't seems to find the BFS scheduler, Voltage Control do not show it. Usually it is there...

I am the only one ? Or the name different ?
[Nexus S Android Development] Lazat:
Franco, your kernel is amazing! I'm running bus at 240 and 960/480 and the phone flies! I get lower quadrant then other kernels, 3600 vs 3900, but maybe your bfs scheduler makes it so snappy, I don't know, it just feels better in everything! :) just one complaint.. scrolling in the browser is the only thing that gotten worse, strange... cannot say anything on batterlife yet, only used it for 4 hours. I'm running gigglebread cm7 kang 30/10 and Franco 01/11
[Nexus S Android Development] franciscofranco:
Maybe you gave it too much bus overclock (it overclocks the GPU too) and your browser didn't like it :p just a hunch, try to reduce it a little and come here with the results :)
[Nexus S Android Development] from1989:
it always at maxfreq when i listen to the music i canot find the deepidle is working .in my mind the freq should be much lower in deepidle right?
[Nexus S Android Development] franciscofranco:
Read the previous posts, I already explained everything.
[Nexus S Android Development] from1989:
i am so sorry about that i really canot understand it i think many people canot understand it too
[Nexus S Android Development] belvedere:
good stuff man. I've got a NS4G running decks ROM. at work I get crap for signal and I'd be lucky to make it back to my house after work with 15%. left yesterday with about 40%, today 50%. deep idle is great. sent a few text messages, checked twitter (refresh every hr) and FB a handful of times, Words with Friends with the boss ;), and read a handful of articles on Pulse. I did have sync turned off, but 3G data was on alllllll day. following that I went to the gym and blasted some mp3's for about an hour (3G still on, sync off). was about 25% after that. the first blip in the graph is flashing the 1 NOV release at work :D and then later when I got home from work I toggled WiFi on and eventually my phone become unresponsive. not sure what that was about. I blame it on UV'ing.

no qualms about max frequency and all that jazz... obviously something that some can't seem to grasp. I've toyed with Live OC but eventually my phone will reboot, usually not right away.. but I just haven't found that perfect balance with UV'ing.
[Nexus S Android Development] got2best:
Ok I dont know what's wrong... I came from matrix and wanted to try yours for battery life was good went back to matrix for overclock and then decided I want 2 use yours till he updates and when I went back battery SUCKS! Idk what I did wrong.. I wiped delvik each time.. any ideas?

sent from my Nexus S i9023 from XDA premium
[Nexus S Android Development] :
You could fully charge, wipe your battery stats, completely drain then fully charge once more. Should return to what you normally get within a couple of days.

Sent from my obnoxious finger using Swype
[Nexus S Android Development] got2best:
Thank u so much! :) so just to get this straight full charge... then wipe stats.. then drain.. then charger again?

sent from my Nexus S i9023 from XDA premium
[Nexus S Android Development] :
Yes, that's right.

Sent from my obnoxious finger using Swype
[Nexus S Android Development] mike216:
That happens to me every time I try a kernel with deepidle mod but I give you my word it will get better every charge cycle and by the time your on your third charge you'll be in great shape :) I guarantee this

My guess is the stats get wacky after the flash and just takes a few cycles to generate

I remember complaining to franco about this the first time I tried his kernel and felt bad a couple days later about it:)

You don't have to wipe your stats to get that great battery life but it wont hurt

Sent from my NSCOLLAB + FRANCO'S 01 BEAST
[Nexus S Android Development] kalinusa:
Hey guys, quick note here.

So I was wondering, I am have been running Cm nightlies and since the very first day I loaded them the battery has been simply mediocre not even comparing to what I was getting on stock. Now with this kernel I am just about close to the original battery life on stock. I am wondering, is anybody running this kernel on stock rom.if without it I had amazing battery then with this kernel the stock must be UNBELIEVABLE! !!! what do u think.
[Nexus S Android Development] mike216:
I think after 3 charge cycles it will be 40% better than stock but you will have to go through a few cycles first to generate new stats, goodnight

Sent from my NSCOLLAB + FRANCO'S 01 BEAST
[Nexus S Android Development] yaachi:
I think its related to commits in 28 Oct, maybe BFS. i manually cherry-picked commits without BFS on 28 Oct (ezekeel fixes) it works well
[Nexus S Android Development] Jamdat33:
Could people post their successful UV values for use in setcpu?

Nexus Swag
[Nexus S Android Development] from1989:
i lost 1% power per 5 minutes when i listen to music with screen off. rom is miui 1.10.28
[Nexus S Android Development] Flying Fox:
minfreq400, maxfreq800, UV -50mV, Lazy

I tried it like @MultiCulti had explained, but it didn´t work for me.

I`ve changed the 92kernelconfig to echo 110 > /sys/class/misc/liveoc/oc_value and the 83aroc to echo 800000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq; echo 400000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq, but without success. I use SpyCPU and couldn´t find any changes after booting. By the way, not using SetCPU anymore......

Can somebody help me once more to use LiveOC? Thx!!!!!
[Nexus S Android Development] coloxim:
Ok..ma con il nuovo kernel se ascolto la musica la CPU rimane al massimo della frequenza..io non capisco..

Inviato dal mio Nexus S
[Nexus S Android Development] doc_v15:
Okay, the 1st Nov kernel is TOTALLY AWESOME! Very FAST, responsive and SMOOTH!!!

Muchas gracias Franco!!
[Nexus S Android Development] ro_explorer:
I'm on stock rom (I really do not feel any need to move to CM or MIUI).

Franco's kernels are working great for me until now. The battery life is excellent. I can not tell about the latest release because I just flashed it yesterday and is too early to jump to conclusions. So far so good though.
[Nexus S Android Development] Zorrich:
Just wanted to say that on oxygen 2.3.1 this kernel is working great. I have never tried a BFS kernel before, but with the way i use my phone, it seems fantastic. Phone feels snappy. Thanks for your work Franco.
[Nexus S Android Development] DebauchedSloth:
If you have it bisected to something that works, would love to test it here. CM7 241 with 11/1 dropped data multiple times in the first hour. CM7 241 with 10/27 has been rock solid for 12 hours.
[Nexus S Android Development] Cybergr:
With latest 01.11 Kernel i decided to jump again on Oxygen 2.3 Rom from my favorite NSCollab..!

So i done a complete wipe to everything and flashed first the rom and then the kernel..Everything works flawlessly and battery seems awesome, from 79% i went down to 77% over night..!!

Now...when we use LiveOC to overclock we don`t touch only the CPU frequency but also the GPU, so overclocking over 120 is not really something we can achieve..

What i mean i tried overclocking up to 140 and the screen gone crazy..that a matter of the GPU chip and has nothing to do with the CPU voltages..!!So down to 130 system seems very unstable...change the voltages and played with different values but no luck..!

Someone has achieve a stable OC over 120??If yes, it is possible to provide me his LiveOC setup script..??

And something more..no more 65 fps on planets in Quadrant test..at least on my setup!!
[Nexus S Android Development] kecinzer:
So far latest kernel working great, I can't say a word about battery life yet, but on Oxygen 2.3.1 working without problems.
[Nexus S Android Development] aiacone:
This means that exists same Android browser with hardware acc like on the SGS2?
[Nexus S Android Development] fede91it:
Awesome framework, no issues!

How can I disable BLN definitively? I've tried to set 0 in /sys/class/misc/blacklightnotification/enabled but after reboot this will set again to 1.

Any suggestion?
[Nexus S Android Development] coloxim:
I've problem with wifi connection..

Is connect but there isn't data transfer ..

Inviato dal mio Nexus S
[Nexus S Android Development] al_madd:
Just download BLN from market
[Nexus S Android Development] kecinzer:
Realy good solution - around 15MB of RAM wasted for nothing.
[Nexus S Android Development] al_madd:
Yeah..depend on people..

I dont really good at script...

touchwake : sparkmod manager

BLN: BLN app
[Nexus S Android Development] ro_explorer:
Create a file in /etc/init.d called ... "my_startup_commands" or whatever.

in that file put the following:

#!/system/bin/sh

echo 0 > /sys/class/misc/blacklightnotification/enabled

Download script manager (free from market) and set the respective script as run on boot and run as root.

That's all ... from now on, the bln will be deactivated on every boot.

You can put whatever lines in the respective file .. liveOC values, min/max frequencies ... etc
[Nexus S Android Development] thoth77:
+25% LiveOC

#!/system/bin/sh

echo "conservative" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

echo "1250 1230 1065 950 950" > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

echo "800000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

echo "400000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq

echo "125" > /sys/class/misc/liveoc/oc_value

echo "lazy" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

☞ min freq 500MHz, max freq 1000MHz, bus speed 250MHz

Smoooooth!