yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] bilboa1:
my kernel is a dictatorship :p

that means I put in whatever I see fit or wanna play with, depending on my time, whatever I enjoy atm, etc. Sometimes I stretch things a bit and do whatever people want just to be nice of course, but in general, I really just do as I see fit.

OC can be controversial as it actually require having voltage higher at some frequencies due to the way it works with the CPU scaling (for stability). it means also some cpufreq governors can appear more stable than others (I would say ondemand is the least stable) as they switch more or less quickly and more or less often.

Anyhow, CM7 battery usage (and android in general) is rather hard to quantify, I too have the battery going down quick sometimes and stabilize, and the next day, same setup, it just works ok "normally" instead (even on 2.2.1 in fact, although it seems to be "more" broken in CM7).

I personally don't think things such as compiler flags and small optimizations are interesting at this stage - in fact, I think the opposite. The reason is that optimizations often bring the opposite effect and again are hard to quantify. (a simple dumb example: -O3 binaries are most often slower than -O2, those being GCC presets for optimization levels, higher being better).

Some others are unsafe such as fast maths on so on (thats why some kernels crash randomely with some toolchains/flags/etc).

This kind of optimization unless drastically efficient (but those who are, are already default optimizations), being this difficult to tweak properly for so little gain, I would say its usually making more sense when done on a stable kernel.

In fact, these optimizations probably make a much larger difference when used to compile the complete CM7 instead of just the kernel. The kernel while a key component is not the complete OS, by very far. Optimizing apps usually brings much better direct results.

All that to say, I prefer adding features or real bug fixes (as stable as possible, but not necessarily always). if i had time i'd like to fix eg the camera lines, and probably the iptable bug upstream (my current fix being just a quick hack so that it works, but its not proper).

Please note that it doesn't mean other kernels are wrong or whatever, it's just my opinion. It's nice to have the choice.:cool:

/fat post ends
[Galaxy S I9000 Android Development] supercurio:
+1 to all that :)
[Galaxy S I9000 Android Development] branalvere:
Make that a +2

I really like the extra functionality this kernel gives over and above stock CM7 and the OC/UV controls are welcome whether or not I use them! Latest update, another hour, another 10 mins talk, 63%
[Galaxy S I9000 Android Development] melorib:
My intention was not to tell you what to do, just trying to balance the wishlist...

Usually only people wanting "advanced" features voice their opinion, and that is ok, but the majority sit quietly and just dont use it if they feel it is risky... :rolleyes:

In the end it is your toy, and no one has the right to demand anything, only to thank you...
[Galaxy S I9000 Android Development] bilboa1:
Actually that was more of a reply to DvTonder, but nothing "personal" toward anyone of course. i just know there is a tendency toward requesting such optimizations so i made a small (ok, rather big) post about it to clear it up.

edit: also ppl have the right to demand whatever they like - i don't require thanks or ask for any donation etc either. i don't wanna feel like in a small ivory tower ^^ but it doesnt mean i will listen to the demands xD

i generally use my own kernels so they tend to be stable as i need my phone to be reliable tho.
[Galaxy S I9000 Android Development] melorib:
I understood, no problem... ;)
[Galaxy S I9000 Android Development] DvTonder:
Bilboa, if you read my posting as a demand then I would like to apologize - it was not the intent at all.

I was just observing that people are expecting all kinds of advanced options from these kernels (I posted the same note in the other CM7 kernel thread) and then complain when their phones crash etc. By adding complexity to an unstable base, problems can get compounded.
[Galaxy S I9000 Android Development] bilboa1:
it triggered my reply but i don't mean to upset anyone. I just noticed it was a general feeling - as you did notice too. No apologies necessary :)
[Galaxy S I9000 Android Development] derrzredeem:
One question...i'm trying to set the clock limit to 1200, but it's always set back to 1000 after a while. Is it supposed to behave like this ?

~drz
[Galaxy S I9000 Android Development] dehem333:
Hmmm , not happening here :p Reaching 2200 Quadrant lol (meaningless:o)

Thanks once again bilbao1 for your kernels , your kernels are perfect.
[Galaxy S I9000 Android Development] derrzredeem:
this is my first time oc/uv-ing :o

so i don't really know what the hell is wrong...rrrr...

though i never had a single reboot with my current settings, so it's fine...i think. :p

ps. quadrant for fun, i get 2400 lol

EDIT: what is wrong with my phone, now it set back to 800...wtf!!
[Galaxy S I9000 Android Development] bilboa1:
it sets back on reboot, but also, due to the frequency scalling, what you say is the max frequency.

it means the phone will go between 100 and 1200mhz, but the current freq depends on the load and the cpu scaling algorithm (default: on demand)

if you change it to performance it will always be 1200mhz for example (but thats for testing only , i don't recommend performance at all, it will kill your battery, heat up the phone, etc)

if ever that would not be a misinterpretation on your part, check you have no special software that would change the value in the background
[Galaxy S I9000 Android Development] derrzredeem:
It seems OSMonitor app is causing the problem, uninstalled, and now everything works like it supposed to :)

Thanks man.

EDIT: it's not os monitor app, my bad it was just me being to dumb. Sorry :o
[Galaxy S I9000 Android Development] Moudii:
bilboa1

I know you kinda gave up on it, but will this kernel work on the MIUI beta?
[Galaxy S I9000 Android Development] bilboa1:
yes except the cards will be inverted probably
[Galaxy S I9000 Android Development] bilboa1:
if anyone is running xan's oc kernel on 2.2, can you give me the output of this command via adb shell:

cat /sys/devices/system/cpu/cpu0/cpufreq/frequency_voltage_table

thanks :)
[Galaxy S I9000 Android Development] bilboa1:
found it ^^
[Galaxy S I9000 Android Development] shaolin95:
I really like this kernel for the Captivate but unfortunately LCD Density does not work with it. Are you planning to work on that?

Thanks

BTW all my benchmarks are a bit faster with your kernel compared to Escapist at the same speed...not idea why though. Test it twice in my last two flashes so I am hoping you can fix the LCD thing which I know the Escapist had at some point too.
[Galaxy S I9000 Android Development] zacharias.maladroit:
for me to get lcd density working I had to modify /system/build.prop

in the ~/android/system/out/target/product/galaxys/ folder and then compile the kernel

a system update-package with the kernel included took care of that - don't know if the kernel stand-alone with that modified file would work

bilboa1 are you planning to include the smartass cpufreq governor, too ?

interactive is nice but it keeps the cpu spinning all the time (ticks)

smartass is an evolution of interactive and tends to be working better

I tried to get the implementation from TheEscapist from his git repo working but files seemingly were missing or not added to the commit

besides that smartass also is quite "qualified" for OC kernels where classic governors such as ondemand don't seem to work well

thanks !
[Galaxy S I9000 Android Development] dxtrlabs:
hey guys just a heads up...the 2300 gave me a bootloop it was the voltage control boot settings so tick them off before you flash.......and for me 1300 doesnt want to UV tried 25 and 50 and it crashes......so eveything else is at 25 for now.....will continue testing.....

EDIT. also setcpu is causing problems with UV so its gone....running all cpu setting with cyanogenmod settings.....works great.
[Galaxy S I9000 Android Development] bilboa1:
the OC is very sensible to voltage, basically, what we found out with escapist tonight is that:

when the freq goes down, then voltage goes down, the freq does not seem to go down as fast as voltage (don't ask me where's the logic here, regulators are supposed to be a lot slower than clocks afaik)

so, the fix for 1.3ghz for example is to boost 1.2ghz slightly higher, so that it doesn't crash when the clock is still 1.3ghz (going down to 1.2) but the core voltage is 1.35v already (was 1.30v before and that would crash)

this principle is exactly the same for Uv, that is, your lower freq shouldn't be too far off the upper freq, or it crashes. experiment and report best results I guess.

we might work on a fix that make it wait for the freq and voltage to stabilize properly, but zero promise lol.

About smartass, ondemand etc, in the end i think ondemand is just fine - although i'd test smartass maybe.

the issue with ondemand and OC is that it switches very very fast and triggers the above behavior very easily

oh also, "fixed" kernels are up.

as for density i'll rebuilt the ramfs for capi and friends, thats the reason its not working afaik - might take a while tho, so might just do that tomorrow (long compiles)

ps: if somehow 1.3ghz is still not stable, try the performance governor and report if its crashing with that (at 1.3ghz) - careful, it will eat the battery ;-)
[Galaxy S I9000 Android Development] cocchiararo:
do i need to update to the last kernel (have the previous one) if i don't oc/uv ?
[Galaxy S I9000 Android Development] branalvere:
Still getting reboots if I try and oc battery seems to overheat if I try and oc with the charger plugged in. Shame, because it feels blazing fast with when you give it the beans, ESP with fast animations selected in spare parts. I've flashed the latest update btw, not noticed a difference performance wise
[Galaxy S I9000 Android Development] bilboa1:
try to see if it crash with PERFORMANCE governor selected please (all phones are not created equal so .. ;)
[Galaxy S I9000 Android Development] vukandric:
Works ok for me, no freezes or reboots. Governor is ondemand, and I have -25 for 1000-1300, -50 for 400-800 and -100 for 100-200.

Sent from my GT-I9000
[Galaxy S I9000 Android Development] dxtrlabs:
For some reason cm settings is not letting me get into performance or any other governor
[Galaxy S I9000 Android Development] dxtrlabs:
Those settings look good going to try them out....
[Galaxy S I9000 Android Development] bilboa1:
ok last update and i'm gone ;-)

captivate, etc: please see if density is fixed

smartass: added it so u can kang it - but as i noted, it doesnt go under 400mhz which is just bad. changing the settings doesn't seem to fix it, didn't look further. it probably just doesnt detect the sleep properly or smth

vibrant: upstream sync
[Galaxy S I9000 Android Development] branalvere:
Tested 1.3 with performance governer:

Noop: SB 1241/2507; QUAD: 2066; NENA: 55.3

cfq: SB 1283/2519; QUAD: 1801; NENA: 54.4

deadline : SB: 1267/2500; QUAD: 2053; NENA: 55.6

1.3 with ondemand governor :

Noop: SB: 1289/2533; QUAD: 2194; NENA: 36.2

cfq: SB: 1349/2588; QUAD: 2089; NENA: 33.7

deadline : SB: 1301/2496; QUAD: 1968; NENA: 34.2

All with background stuff running. Tried again with UV -25 and hit reboot every time I run SB.

Normal apps browser, twitter, xda run very fast, no noticeable system lag at all. Battery drain 7% whilst running tests. (30 mins ish)
[Galaxy S I9000 Android Development] domy1985:
What about front camera position? Is this also fixed?
[Galaxy S I9000 Android Development] derrzredeem:
not yet...
[Galaxy S I9000 Android Development] zoubidou:
just flashed your kernel with the latest version of cm7. seems to work fine, besides the switching between wifi and H is always sort of a hazard.

concerning OC. i have set mine to 1.2, but infact i would like to set it to 1.125, because i have figured out, that you have nearly no gain between 1.125 and 1.2 but you don't have to touch any voltage settings, unfortunately 1.125 is missing in the values.

i am not sure about 1.3, will check this later.
[Galaxy S I9000 Android Development] bilboa1:
i get quite a big performance boost at 1.3 altogether (for quadrant fans, im at 2500+)

we might get the voltage step up fixed at some point and lower voltages back / add intermediate freqs as well. note that you can also just use voltage control and lower the voltage yourself, and keep 1Ghz as max freq (which is default)

oh, going to push BLN soon (well it might be in 10h or so but still)
[Galaxy S I9000 Android Development] :
Amazing! I miss BLN so much. Just wanted you to know that your Kernel has made a big difference to my phone - I love it!

Tony
[Galaxy S I9000 Android Development] bilboa1:
This one has BLN and a couple of other fixes: http://goo.gl/mSMe9

Now here comes the fat warning: i put it only here because I DID NOT TEST IT, because I cannot test it right now, no phone here. Just for daring people. if it breaks your phone or your panel, or whatever, don't come complaining. It might also just work, tho. Source's on GIT of course. And need the BLN app.
[Galaxy S I9000 Android Development] zacharias.maladroit:
thanks for this & thanks for the WIFI fix (from Google - Google FTW !) :)

I've already spent all my thanks for today otherwise you would have got one :p
[Galaxy S I9000 Android Development] vukandric:
Sorry to say this, but my touch keys doesn't work as they should after flashing this kernel, so I went back to my previous kernel. Hope to see it fixed soon. :) Glad to see you are working on it, thanks! :)
[Galaxy S I9000 Android Development] bilboa1:
if you test the kernel, please tell me if it works, lol :-)
[Galaxy S I9000 Android Development] Arkanius:
I have a problem with this kernel. When I insert my headphones my cellphone thinks they are not inserted, and plays the sound from the loudspeaker. And when they are removed the headphones icon shows up and I get no sound at all. This happens with the official headphones and a nokia adapter. To fix it I have to reboot.
[Galaxy S I9000 Android Development] boarder.2k9:
Hey man, loving the kernel progress! Your an awesome developer. I've tested this one out and like the other post said the touch keys aren't working properly. The menu button doesn't seem to respond till the back button is pressed which seems to respond as a long press (killing the app if the development option is ticked). Can't wait till its sorted, bln is awesome.

Thanks man
[Galaxy S I9000 Android Development] doronkdoron:
Headphones problem

+1

having the same problem also. Using samsung original headphones.

Beside of that, Very good kernel. Got my CM7 work even faster.

Any solution to this Headphones problem?
[Galaxy S I9000 Android Development] zoubidou:
true headphone are cabled the wrong way round.
[Galaxy S I9000 Android Development] Arkanius:
I've tried with both Samsung's and Nokia's and other random headsets. They all show the same behaviour. It's a kernel bug.

Works correctly on platypus
[Galaxy S I9000 Android Development] BlackDino:
any way you could raise the max batt temp charging?

Right now I believe its at 43C and stock samsung sets it to above 56C
[Galaxy S I9000 Android Development] zoubidou:
headphones are working the wrong way round. when i plug them in it plays the speaker, and when i unplug them it show the headphone symbol and i have to restart the phone to remove the headphone symbol. would be nice if you could correct this please.
[Galaxy S I9000 Android Development] zoubidou:
i am choking when i say cabled. it is definitively a kernel bug. something is cabled the wrong way round in the kernel.
[Galaxy S I9000 Android Development] zacharias.maladroit:
@those having problems with headphones / speaker:

try playing around with the Voodoo Control App meanwhile

specifically the [x] Tune speaker for music setting,

either turn it on or off and see whether that makes a change
[Galaxy S I9000 Android Development] bilboa1:
headphone is an upstream bug which i fixed now, will be in the next release (grmpf hehe)

@zachari dont merge upstream yet ^^
[Galaxy S I9000 Android Development] branalvere:
I flashed, bln didn't work, just disabled soft keys so "back " didn't work, didn't try anything else restored previous kernel.

It's great that you're working bln into the kernel, you keep adding to the functionality of cm7 daily. Keep it up bilboa!
[Galaxy S I9000 Android Development] bilboa1:
http://kang.project-voodoo.org/f/CM7_GT-I9000_kernel_kang_20110323_21_update.zip

another unsafe test-only thing

fixed: headphone issue

fixed: touchkey works

not-sure: bln
[Galaxy S I9000 Android Development] BlackDino:
I will try this now,

Btw did you read my post a while back.

Is it possible to allow charging for temp above 43C?
[Galaxy S I9000 Android Development] bilboa1:
probably, havent looked at it. but "stopping" charge between 95-100% is normal

its just that before it would lie and say 100% when above 95 until you unplug then quickly drop

also, got BLN working fine, but there's something odd with the touchkey version, although fw upgrade was no enabled, which i'm looking into..
[Galaxy S I9000 Android Development] Ronnymes:
The headset is working now!

Can you also fix the buttons from the stock headset? they are not working
[Galaxy S I9000 Android Development] bilboa1:
ok enough derping around.

if you have flashed one of the test kernels, adb shell to your device and type:

rm /system/lib/hw/lights.s5pc110.so

then flash the new 'stable' release (which is uploading atm)
[Galaxy S I9000 Android Development] branalvere:
Re : charging, I was playing with the oc last night, the battery hits "overheat " in spare parts at 47 degrees + but will charge up to that on my sgs
[Galaxy S I9000 Android Development] bilboa1:
when charging with oc, granted that you're not using the phone etc, it changes nothing with non-oc

the phone heats up quite a bit while charging anyway, and I suppose the limit is there for a good reason, although we could probably bump it up, i wouldnt really wanna risk that too much.
[Galaxy S I9000 Android Development] BlackDino:
Right but on the stock samsung kernels the cap is around 56C
[Galaxy S I9000 Android Development] zacharias.maladroit:
wait - that fixed it ? XD

maybe I don't get it but mach_aries is the common platform for the SGS based phones

ok, mach_aries might not be specific enough - so why is it working now when there's no CONFIG_SAMSUNG_GALAXYS

e.g.

#if defined (CONFIG_SAMSUNG_CAPTIVATE) || defined(CONFIG_SAMSUNG_VIBRANT) || defined CONFIG_SAMSUNG_GALAXYS

?

great job btw ! :)

besides that - perhaps I already asked this (apologies in advance):

but do voltage values change when using the kernel without Xan's VoltageControl app or any other manipulator app ?

that's the reason why the core CMSGSTeam devs are waiting for Samsung to release the sources for the Gingerbread kernel

currently the CM7 kernel is based off the Nexus S kernel

and things might work a little bit different between those two devices

if Samsung's fine with it (set to 55 or 56°C) it sure will be changed to that value in the CM7 kernel, too

(edit: added 'defined' - without it - it of course wouldn't work if that was the correct way)
[Galaxy S I9000 Android Development] bilboa1:
the support for buttons/mic etc in the headsets is half broken upstream atm, i didn't know that / didn't check hard enough i guess. so i just reverted the thing that enables support for it in the SGS, because its not implemented yet.

they probably are silently working on it.

for voltage, only xan's app works. you can also just echo values in /sys/.... (look for cpufreq stuff), that's what the app does
[Galaxy S I9000 Android Development] zacharias.maladroit:
and those values (if not changed) should be the ones activated & valid in the stock (CM7) kernel

ok,

thanks !
[Galaxy S I9000 Android Development] DvTonder:
YES! BLN works. Thank you!
[Galaxy S I9000 Android Development] branalvere:
Flashed the update, bln now working, strange thing, camera controls disappeared after flash then return after a couple of reboots.

So now we have voltage control, bln and Ffc in a week, Congrats. Any chance of a fix for the dodgy rotation in Ffc? Anyone?
[Galaxy S I9000 Android Development] bilboa1:
actually, nope. the voltage values for the higher frequencies are not the same as stock, they're slightly higher, its a trade off so that you don't crash when switching freqs atm. the values are really only slightly higher so its no big deal.
[Galaxy S I9000 Android Development] zacharias.maladroit:
got it now

thanks again, bilboa1 ! :)

I'm gonna UV (undervolt) anyway so that shouldn't be a dealbreaker for me

are you more the OC (+OV) type or undervolter (going for battery runtime) ?

anyone has stable UV values to share with this kernel ? (they're surely different from the ones from Froyo)

thanks !
[Galaxy S I9000 Android Development] BlackDino:
Hmm, my bln is not working, anyone know whats going on.

I have the premium version of bln and when trying a test my keys never light up

Edit:: it seems the test on the app is broken.

SMS does show BLN
[Galaxy S I9000 Android Development] bilboa1:
it depends on the hardware really. the humming bird we have seems very stable with higher voltage and the boost in performance is more than noticeable.

so in the end im running at 1.3ghz now and i don't think it can get any smoother in many apps (not all tho :p)

as for undervolt, i like when it works but i'm not sure if the gain is very significant.

due to the way voltage/frequency works, you cannot undervolt a lot right now without freezing the phone (it depends on your phone of course, on some it work better than others).

i plan to fix that eventually one day.. it needs to wait before "downing" voltages after the frequency is lowered, but its annoying to implement
[Galaxy S I9000 Android Development] boarder.2k9:
omg man, bln is working, oc/uv, voodoo. You are f'ing awesome. You have fixed so much its unreal. My phone is freaking amazing now. The only fix im waiting for in the main package is 2g/3g toggle to work without reboot, thats literally it!
[Galaxy S I9000 Android Development] DvTonder:
Possible bug with BLN, a few times now the lights have come on without a notification triggering it. I think something is waiting for me but when I unlock, nothing.

Will keep an eye open to see if it continues to happen.
[Galaxy S I9000 Android Development] dxtrlabs:
Same here....i wonder what it was the only thing that changed was the wifi sleep....not saying its related but its the only think that changed for me...
[Galaxy S I9000 Android Development] bilboa1:
if you touch the keys manually they light up and dont go off (due to an upstream bug it doesnt go off that is)

it might be possible to make it so that it doesnt light up at all manually, but ill look at it tomorrow only
[Galaxy S I9000 Android Development] DvTonder:
You are correct. When the screen is locked, touching the keys make the lights turn on. Pressing the home button turns them off.
[Galaxy S I9000 Android Development] BlackDino:
I dont have this issue? You are saying once your screen is locked if you touch the keys (that are not backlight) they will turn on?
[Galaxy S I9000 Android Development] boarder.2k9:
True, they stay off permanently once you click the home button as well.
[Galaxy S I9000 Android Development] kroat999:
How did you get 2500 in Quadrant ? with Fresch install of CM7 and your kernel i only get 1753 points with 1.3 ghz
[Galaxy S I9000 Android Development] bilboa1:
nothing special, and i know others get 2500 too at 1.3ghz - all standard + that kernel
[Galaxy S I9000 Android Development] BlackDino:
try killing all your apps,

I got a 2100 with 1.3GHz
[Galaxy S I9000 Android Development] kroat999:
i alredy killd all apps i dont understand that why is mine so low
[Galaxy S I9000 Android Development] vukandric:
2541 with 1.3 :)
[Galaxy S I9000 Android Development] boarder.2k9:
nice!! :D

I got 2050 once at 1.3