yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] AlexForTomorrow:
nope, with the latest nightly everything was fine.

with automatic brightness selected, the level increased/decreased based on the amount of light in the environment.

now, it's stuck on max no matter how light/dark it is..

really weird, since this bug also happens with stock kernel.

shall we blame "black magic" for it? :D
[Galaxy S I9000 Android Development] bilboa1:
ive quickly read that the light sensor might be failing with the last upstream update

there should be a tool in spare parts or devtools or some apk like that to read the light sensor output, it should tell you if its really broken
[Galaxy S I9000 Android Development] zacharias.maladroit:
does Google Goggles work for you guys using this kernel ?

if not: bilboa1 do you know what might screw it up ?

from what I saw it seems to be a kernel thing (not sure yet)

thanks !
[Galaxy S I9000 Android Development] ashwinds:
After google goggles crashed because it couldn't start camera, nothing can start up camera. Not the camera app, nor any app which uses camera. All crash.

If you start up camera directly FIRST, there is no preview. But it does capture images.
[Galaxy S I9000 Android Development] currydude:
Yea Google Goggles didn't work with bilboa1's kernel. Probably why your new tests don't too (since you based your new test kernels off bilboa1's)
[Galaxy S I9000 Android Development] bilboa1:
fimc_reqbuf_capture: no memory for capture buffer

prolly due some recent upstream changes actually (i never touch memory or even camera)

vignette etc work fine btw

need to test on regular cm7 kernel and if its still there (i suppose it is) find out the offending commit ;-)
[Galaxy S I9000 Android Development] zacharias.maladroit:
it works on stock

lol

I had enough of git bisecting and tracking offending commits down :p

thanks !

edit:

just tested again from the kernel compiled from upstream without changes

it indeed works

weird issue :\
[Galaxy S I9000 Android Development] Arkanius:
Google Goggles never worked even in the stock kernels
[Galaxy S I9000 Android Development] zacharias.maladroit:
it does

try ! :)
[Galaxy S I9000 Android Development] Rixsta:
Got mine today ...big step up from SGS1...and thats of course stock ...

Cant wait for the real roms to start rolling out :) ..

Confirmed unlocked bootloaders :)
[Galaxy S I9000 Android Development] bilboa1:
ill have a look tonight if time allows
[Galaxy S I9000 Android Development] zacharias.maladroit:
FYI:

dmesg output:

logcat:

http://pastebin.com/EyZ1TGau

full dmesg:

http://pastebin.com/WYmWNYi7

thanks !
[Galaxy S I9000 Android Development] bilboa1:
in fact i found time now

as suspected fimc0 was out of memory - but yes its in my patches. Somehow I missed it when cherry-picking the screen timing stuff, that it also halved the video memory.

Fixed in GIT, new kernel coming and thx for the report ofc :)
[Galaxy S I9000 Android Development] zacharias.maladroit:
I also was half the way towards it ;)

selectively applying voodoo sound, led notification and the battery fix didn't broke it

screen timing sort of would have been my final candidate

thanks for fixing it so fast ! :)
[Galaxy S I9000 Android Development] bilboa1:
I kinda suspected it because its the only diff that could remotely be nearby FIMC mem size.. and yeah.. it remotely was lol

Anyhow new kernels are up (or almost) now
[Galaxy S I9000 Android Development] zacharias.maladroit:
the only change is the changed screen timing ?

(with rewritten git history)

so I can selectively revert that and re-apply the new one

thanks !
[Galaxy S I9000 Android Development] bilboa1:
did not rewrite this time, been lazy

just apply that https://github.com/kangsterizer/and...mmit/200214d2f6b910c829d958ead84ffa3623f0bcca
[Galaxy S I9000 Android Development] zacharias.maladroit:
thanks !

now that's what I call a quick-/hotfix :D
[Galaxy S I9000 Android Development] Adevem:
just don't be like me, rebooting into recovery without even downloading the file...
[Galaxy S I9000 Android Development] zacharias.maladroit:
haha - I did that several times already

and then at Recovery (or even while booting) was like "D'oh ! - didn't push the new kernel" :D
[Galaxy S I9000 Android Development] DvTonder:
Under Mounts and Storage in recovery you can mount the phone as a USB device. Comes in handy when you forget to copy the file before.
[Galaxy S I9000 Android Development] zacharias.maladroit:
and I have access to the internal SD ?

awesome ! :)

thanks !
[Galaxy S I9000 Android Development] lippol94:
Adb is even more fast from recovery than mounting internal SD :)

And by the way i do that too many times :p i'm too young for this kind of memory problems :D
[Galaxy S I9000 Android Development] leamoor:
Bilboa1

cyanogenmod 7 have a new update!

and i hope u will update your kernel again

u give me most stable and fast

thanks
[Galaxy S I9000 Android Development] crazililazn:
Is the latest kernel compatible with the latest nightly?
[Galaxy S I9000 Android Development] maisi:
Yep you have access , saved me some trouble already when i forgot to put a rom on the SD card and wiped my phone ^^

I think it never worked on the old CWM (2.x) but with CWM3 it works ;-)
[Galaxy S I9000 Android Development] bilboa1:
LED notifications have been merged in mainline so you don't need a custom kernel anymore to support it - its my code so it works just like it did before

current kernels don't work so well with nightly however

i'm currently playing a bit with video chat stuff before i upload new kernels^^
[Galaxy S I9000 Android Development] apollo15rover:
Cool!!

Even though 2.3.4 fixed the color problem from 2.3.3, I still prefer Voodoo Color - nothing makes my screen look better than ..

Blue Max

Red 321...

Green 321..

Gamma -28 all three settings..

Really makes my display pop!
[Galaxy S I9000 Android Development] supercurio:
Good to know Voodoo color present crappy hack works for you!

However 2.3.4 Nexus S Super AMOLED driver changes nothing in term of Color rendering (but acted as placebo for some people!)
[Galaxy S I9000 Android Development] apollo15rover:
Hey Supercurio - am I wrong or isn't the Voodoo control yours? I thought you were the main architect behind Voodoo on the Galaxy S - is there a better way you can steer me on this one? Thanks!!
[Galaxy S I9000 Android Development] supercurio:
Yes its my stuff but it doesn't prevent me telling current Voodoo color for Nexus S is a crappy hack! like written here ^^
[Galaxy S I9000 Android Development] apollo15rover:
I think we're talking about different things - I was writing that I liked being able to tune voodoo color on 2.3.3 with Bilboa's kernel..

While the current Nexus S color on 2.3.4 is improved from 2.3.3, it's far from equal to what I could get on Voodoo color (still a bit too warm for me even with brightness at max) - so am looking forward to Bilboa updating so I can get my own settings back..

By the way, I love the new Voodoo Control Plus -- playing Blondie right now on my Bose headphones :)
[Galaxy S I9000 Android Development] matt310:
Chalk me up as another big fan of this kernel+voodoo control. It completely transforms my Captivate from a dirty yellow screen to a crisp white one. (See photos below!)

Before:

After:

I haven't flashed the latest CM7 build yet because I don't want to go back to the warmer color temps! :)

Also, this kernel is the only one I can run OC with no freezing or weird behavior. Completely stable @1300Mhz is hard to steer away from.

-M
[Galaxy S I9000 Android Development] supercurio:
Sorry to insist but:

source code is the same, are you really sure 2.3.4 changes color from 2.3.3?

Because here it doesn't − Nexus S

There was only 1 commit related:

https://github.com/project-voodoo/linux_samsung/commit/e6b8e4458a2936c29caa0e2f94929173529bfc58

It avoids the screen that was staying black in some situations. (like at boot after flashing a kernel for me, sometimes)

Fully History: https://github.com/project-voodoo/linux_samsung/commits/android-samsung-2.6.35/drivers/video/samsung/s3cfb_tl2796.c

That's why I'm surprised that some people say 2.3.4 fixed anything related to color :D

Sometimes we hope things so much it seems to become real...
[Galaxy S I9000 Android Development] apollo15rover:
Probably not.. maybe my own wishful thinking then.. I'll take your word for it on this one :D
[Galaxy S I9000 Android Development] apollo15rover:
Thanks Bilboa!

Installing..
[Galaxy S I9000 Android Development] bilboa1:
wait a moment im testing it x)

ok r2 should be fine :)

main change beside support of 2.3.4 is .. removal of features and cleanup

some features are now upstream (like leds, haptick etc) and removed the 2 extra governors as they're useless in their current state. if you want a nice bench use performance

if you want to use ur phone normally use ondemand

i'll have a look at modified interactive later maybe, unless my sgs2 comes first lol.
[Galaxy S I9000 Android Development] seriouser:
I flashed the latest kernel over the latest NIGHTLY (0501) and the phone got stuck at boot at the Samsung/Cyanogenmod screen.
[Galaxy S I9000 Android Development] jaju123:
Wifi isnt working on the latest kernel - try to turn it on and it just says 'error'.
[Galaxy S I9000 Android Development] zacharias.maladroit:
that indicates a mismatch between modules & kernel

try re-installing the kernel package

if "Error" still is shown

move the modules from /system/modules

to /system/lib/modules

hope that helps :)
[Galaxy S I9000 Android Development] jimmy080705:
Same here......stuck!
[Galaxy S I9000 Android Development] Putzy:
CM7_GT-I9000_kernel_kang_20110501_r2_update.zip works correctly on the most recent CM7 nightly (0501)

The other _20110501_ releases didn't seem to work correctly (boot hanging, no WiFi)
[Galaxy S I9000 Android Development] seriouser:
Confirmed. R2 works. Which is the best CPU governor with this kernel concerning battery life without losing too much performance?
[Galaxy S I9000 Android Development] bilboa1:
ondemand is the best all around for both perf and battery so far. modified versions of interactive might beat it in the future but not the ones i included previously
[Galaxy S I9000 Android Development] kickassdave:
I can't open the market after flashing this. Tried wiping cache and dalvik.

It just flashes for a second then closes.
[Galaxy S I9000 Android Development] nanu_x2:
everything is working great here..:)

latest cm7+ ur kernel

thank you..
[Galaxy S I9000 Android Development] crazililazn:
Bad flash? My market works fine.
[Galaxy S I9000 Android Development] kickassdave:
Reflashed twice after deleting /system. Still isn't working. Also the sd scan in startup is stalling unless you unlock the phone.
[Galaxy S I9000 Android Development] zacharias.maladroit:
does WIFI work for you guys using this kernel ?
[Galaxy S I9000 Android Development] bilboa1:
use r2 :P

1234
[Galaxy S I9000 Android Development] zacharias.maladroit:
if it didn't work with non-r2 kernels

what did you change ? :)

thanks !
[Galaxy S I9000 Android Development] jaju123:
Yeah it only started to work with r2 kernel.
[Galaxy S I9000 Android Development] bilboa1:
i merged stuff wrongly :)
[Galaxy S I9000 Android Development] zacharias.maladroit:
stupid question:

what exactly ?

and could I be affected, too ?

thanks !
[Galaxy S I9000 Android Development] bilboa1:
nop it was a rebase merge in my own scripts and i havent comitted it

however i did rewrite my git history with cleaned up patches^^

keeps stuff clean and tight.. for me ofc
[Galaxy S I9000 Android Development] boarder.2k9:
bilboa,

boot loop on r2, not the classic looping at the boot animation though. It boots, then freezes within around 10 seconds if not less then reboots over and over and over. Will try flashing again, possibly voodoo control plus trying to load kernel modules on boot (as it was ticked) which caused crash? I will see.
[Galaxy S I9000 Android Development] boarder.2k9:
yeah it was voodoo app trying to load modules. No worries.
[Galaxy S I9000 Android Development] pcboyy:
everything is working great.. rotation, wifi, 3G, even i use setcpu and pimp my cpu together.. works like charm
[Galaxy S I9000 Android Development] CROrION:
Installed r2, no network, only emergency calls :/
[Galaxy S I9000 Android Development] ashwinds:
No such issue here. Try rebooting and also lock and unlock after 10-15 seconds.
[Galaxy S I9000 Android Development] gabby131:
Working r2 here.....the only kernel i've tried that agrees with setcpu...:)
[Galaxy S I9000 Android Development] Bonta768:
r2 roxors. Good to see you back in the game bilboa1. I'm glad you took out all the tweaked governors. Go for quality not a billion features
[Galaxy S I9000 Android Development] Alle46:
Superb job, congratulations bilbao.

One question, how can I activate the LED notifications with the MIUI 1.4.29?
[Galaxy S I9000 Android Development] r3ferrei:
Is the Compass working in the 1/5 release of CM7 using this Kernel?

I've noticed my compass is not working, but it might be exclusive to me.

I just wanted to know if others worked so I can begin debugging it if its just mine.

Running on Captivate btw.
[Galaxy S I9000 Android Development] matt310:
Hah - me too. Everything working great here as well.
[Galaxy S I9000 Android Development] Killemalll:
I can confirm the compass works fine on my Captivate with the 05/01 release.

I had it for 2 days. No issues experienced so far. Very solid :)
[Galaxy S I9000 Android Development] r3ferrei:
Thanks. Time to go cwm crazy.
[Galaxy S I9000 Android Development] r3ferrei:
Clearing dalvik/cache/fix permission got it going again. Its amazing how that fixes so many issues.
[Galaxy S I9000 Android Development] fenerbuuh:
If I flash r2 it stops at cm boot logo. What's the problem? Cleared init..... dalivik. Etc
[Galaxy S I9000 Android Development] bilboa1:
-make sure u use latest cm7 nightly

-clear up various caches if it still fails

but mostly

-make sure u use latest cm7 nightly

^ ^

edit:

- wait a good while to make sure its a loop - boot is slightly longer now

in a boot loop you see the screen resetting anyway
[Galaxy S I9000 Android Development] bilboa1:
R3: upstream sync

note: this release has not much testing.
[Galaxy S I9000 Android Development] matt310:
2.6MB vs 3.7MB for the last several (for captivate). That sound right to you?
[Galaxy S I9000 Android Development] vvaffles:
i've seem to have lost recovery after updating to r3 (for the captivate), any 1 else with this problem?
[Galaxy S I9000 Android Development] omiks3:
+1 dunno if the pattern has changed or its just gone. Download mode still works gonna do a fresh flash when I get home from work
[Galaxy S I9000 Android Development] vvaffles:
mm i guess it is not just me.
[Galaxy S I9000 Android Development] bilboa1:
it needs latest cm7 and uhm it might be in latest cm7 that there is some breakage between recovery/normal mode^^

specially depending on devices ^^
[Galaxy S I9000 Android Development] DvTonder:
+1.

Recovery mode is broken with R3 - could get into recovery from clockwork with the stock 0503 build. Now no longer working. Bummer - this looks like it will need a complete reflash from ODIN to get recovery again?
[Galaxy S I9000 Android Development] madmack:
try extracting the zImage file from the last update. tar it and install only that in Odin.

it should do the job without having to go through the whole flashing process again.

you could also flash the initial cm7 kernel with Odin, boot into recovery and install the latest update from there .
[Galaxy S I9000 Android Development] bilboa1:
the difference is that now there is a fix to enter recovery properly but it's in testing and require super latest cm7 ofc

as i said "its not very much tested" (even in cm7)

if you're ever in a boot loop with that, flash any kernel with CWM3 via odin (any kernel in .tar) and reflash an older kernel from the recovery
[Galaxy S I9000 Android Development] TheEscapist:
Hey kang, what happened to the build system? I cannot, for the life of me, get it to work. Kernel builds fine if I use ./build.sh, copies kernel + modules to the device tree, creates the boot.img, but refuses to boot past recovery. Is initramfs not being pulled in properly, or something? or is the kernel from the seperate kernel build not being compressed into the img properly?
[Galaxy S I9000 Android Development] DvTonder:
I decided not to try TAR on my windows box and it is too late at night to boot up my vmware instance of UBUNTU and try and figure out the whole TAR thing. Did the 2nd option you suggested. Got recovery working again.
[Galaxy S I9000 Android Development] bilboa1:
probably doesnt "create the boot.img"

boot.img is in out/target/... and it contains recovery + ramfs+kernel (its a multi-stage-ramfs thats why its a bit slower to boot too)

you can check my git to use a manual packing of the boot.img or use the main build script of cm7 instead of the kernel one
[Galaxy S I9000 Android Development] TheEscapist:
Boot.img shows up in out/.. and without it, it wouldn't boot into recovery. That's what makes me think the initramfs isn't being packaged in properly. As for using the main build script, that's what I use. It just calls the kernel build script, then calls brunch. Unless you mean using brunch on its own, which just copies the prebuilt kernel from the device tree (and doesn't boot up either).
[Galaxy S I9000 Android Development] bilboa1:
Check that:

https://github.com/kangsterizer/android_kernel_samsung/blob/android-samsung-2.6.35/multi_build.sh

taht specially:

../../../device/samsung/common/aries/mkshbootimg.py release/boot.img arch/arm/boot/zImage ../../../out/target/product/$code/ramdisk.cpio.gz ../../../out/target/product/$code/recovery.cpio.gz || { echo "failed mkshbootimg"; exit 1; }
[Galaxy S I9000 Android Development] TheEscapist:
Yeah, I just saw that. Gonna try putting it in the kernel build.sh. Have to do a clean build before trying it though, mucked up my directory just before. Thanks though.
[Galaxy S I9000 Android Development] zacharias.maladroit:
try to build via:

./build.sh captivate kernel

for me the android-part currently is failing due to some wimax **** being pulled in :(
[Galaxy S I9000 Android Development] TheEscapist:
No problems here, but I haven't synced for an hour or so.
[Galaxy S I9000 Android Development] tiuk:
For the record, with r8 I have no problem booting into recovery through the menu, haven't tried the button combo yet. Currently I've cleared stats and am going to charge overnight, will test button combo in the morning but I expect it should be fine. I did clear cache, dalv, and fix permissions both after flashing the nightly as well as after the kernel.

(p.s. loving this release so far)
[Galaxy S I9000 Android Development] dxtrlabs:
Hey I flashes r5 and now I can't 3button combo into recovery what am I doing wrong?
[Galaxy S I9000 Android Development] scheichuwe:
r9 working fine here, no problems booting in recovery mode (3 button combo and from menu).

Nice one :)
[Galaxy S I9000 Android Development] bilboa1:
there's a typo in the battery calibration code so don't worry if the stats aren't accurate at all :p (missing 0)

i'll make a new build in 8H or so ;-)
[Galaxy S I9000 Android Development] bilboa1:
done (r10)
[Galaxy S I9000 Android Development] Putzy:
r10 seems to work well. Will post again if something wrong pops up. :)
[Galaxy S I9000 Android Development] vitalij:
same here everything is fine. thanks bilboa!
[Galaxy S I9000 Android Development] DvTonder:
R10 works fine. Thank you.
[Galaxy S I9000 Android Development] jimmy080705:
Bilboa, any reason why nenamark is scoring well below cm7 nightlies.....like 30fps vs 50 fps?.....are graphics drivers being compiled properly?
[Galaxy S I9000 Android Development] Bo$s:
Try changing governor from ondemand to conservative or performance (performance sets CPU to max freq so it drains battery very fast) and Nenamark scores will be about 50-60 fps. But with conservative governor phone isn't so smooth as with ondemand.
[Galaxy S I9000 Android Development] gabby131:
i decided to be serious on undervolting and surprise surprise! stable @1300mhz - 150 = 1250mV

less battery consumption that results i less heat.....:)

is anyone lucky enough or tried to undervolt lower than -150? i am experiencing serious issues with 1000mhz if voltage is less than 1250mV so i wont even try lower on 1300mhz. :)
[Galaxy S I9000 Android Development] jimmy080705:
But cm7 has ok battery life and very smooth so something else must be going on here...?
[Galaxy S I9000 Android Development] Bo$s:
With 0501 nad 0504 updates my Nenamark scores on stock CM7 kernel (default ondemand governor) was about 35-40fps.
[Galaxy S I9000 Android Development] :
R10 sends my phone into a bootloop. I'm using an euro Galaxy S with 0405 nightly. I have cleared cache, dalvik cache etc. no change.
[Galaxy S I9000 Android Development] Aus_Azn:
According to CM7 Captivate dev, atinm, this is a known issue with the 05/04 nightly. Just keep rebooting and it will start, eventually.
[Galaxy S I9000 Android Development] zacharias.maladroit:
try pulling the battery

that also seemed to help - after a new boot it should (hopefully) work
[Galaxy S I9000 Android Development] Aus_Azn:
R10 and the 05/04 nightly has completely borked UV for be. Last time, it ran with 50mV off on all to 600Hz and 100mV off of any above that. Now, my phone can't even take 25mV across the board...
[Galaxy S I9000 Android Development] tiuk:
Funny because for me it's better than ever.. currently -125 from 1300mhz down to 100mhz in all states, rock stable. Can't believe it, but it's working and sipping the battery ever so slightly; awesome.
[Galaxy S I9000 Android Development] DvTonder:
I am having a similar experience with UV. My phone was solid with -125 at 100, -100 at 200, -75 up to 1000 and -50 at 1200. With R10 I cannot run with -25 on any of the speeds. Not sure why that is but back to running stock for me, unfortunately :-(
[Galaxy S I9000 Android Development] bilboa1:
Maybe you were running another governor than ondemand ?

There's no changes to UV/OC etc. In fact I rarely make any change lol
[Galaxy S I9000 Android Development] Aus_Azn:
I only run Conservative and Powersave... No change here either.
[Galaxy S I9000 Android Development] bilboa1:
uhlala r12

most camera stuff is fixed

use new CM7 nightly
[Galaxy S I9000 Android Development] bilboa1:
if you run latest cm7, just hit power button and select reboot recovery (some don't know its fixed since a couple of days :) it's easier than the key combo ;-)

devs using the scripts, make sure the header says /bin/bash not /bin/sh (fixed it just now on git) if you're running ubuntu and the like and wonder why it's not working

real men os link /bin/sh to bash anyway xD
[Galaxy S I9000 Android Development] Bo$s:
After R12 flash my light sensor reports 5000/5000 all time. All fine on stock kernel.

Using latest 0605 CM7 update on i9000.
[Galaxy S I9000 Android Development] currydude:
r12 has not be upstream synced with the latest CM7 nightly yet (sources habe not been released yet)
[Galaxy S I9000 Android Development] bilboa1:
http://xdaforums.com/showpost.php?p=13563484&postcount=985
[Galaxy S I9000 Android Development] filiptc:
I found a minor (but painful) bug. It has to do with the Swype keyboard (installable through beta.swype.com) which works great with the standart CM7 kernel but each time I flash bilboa1's kernel, swype stops recognizing any swype gesture (regular keyboard functionality works normal). I tried wiping dalvik, uninstalling, reinstalling,...

I noticed the bug after flashing 20110504_r10 on 05042011-NIGHTLY and it disappeared after updating to 05062011-lightsensor-NIGHTLY. I now have it again after flashing 20110507_r12.

Cheers
[Galaxy S I9000 Android Development] Bo$s:
So is R12 fully compatible with 0506-lightsensor update or not?
[Galaxy S I9000 Android Development] tiuk:
Swype works fine for me. Try switching to a different input method then back to swype, sometimes the beta is picky about licensing crap.
[Galaxy S I9000 Android Development] kobik77:
I wonder if anyone here encountered a problem which the touchkeys lights remains on when locking the phone on the latest nightly+r12.