yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] coderunner:
Ok thanks, I also found out you if you flash the update zip from cyanogen it goes back to the original kernel.
[Galaxy S I9000 Android Development] bilboa1:
yes, every ota package overwrite the kernel :)
[Galaxy S I9000 Android Development] bilboa1:
in doubt, odin-flash a complete samsung rom with repartition + bootloader checked (the rom must have the bootloader)
[Galaxy S I9000 Android Development] bilboa1:
this is a bug in CM7 SGS not the kernel (albeit kernel does miss multiport also), going to fix and request them a pull
[Galaxy S I9000 Android Development] kepke:
thank you so much!

i miss that too.
[Galaxy S I9000 Android Development] BTTNext:
@bilboa1

Since this commit the Captivate can't boot up. Can the r/w check not be set up correctly for the Captivate?
[Galaxy S I9000 Android Development] DvTonder:
LED notification seems to be completely turned off for me now.

I did the following:

1) Installed latest kernel via CWM

2) Installed CMPARTS as described and can open the LED settings

3) I reset all LED settings

4) When I receive either gmail or sms, the lights never turn on

Is there a specific setting I need to set to make the notifications show? Maybe in the Miscelaneous, per app settings?
[Galaxy S I9000 Android Development] derrzredeem:
Hello bilboa1,

I think i've found a possible bug, i'm not sure if you understand this but...

When i try to open some apps, it just flash back to home screen - it won't enter the app. I need to go to a different app first to get it to work...

Maybe this could explain a lot better: http://pastie.org/1731671 :p

ps. my phone is i9000
[Galaxy S I9000 Android Development] boarder.2k9:
same on my i9000. full of bugs this one. Closes apps on opening and kills application on unlock. Plus on reboot once it came up with card error and then touchkeys didnt work. reverting to 27
[Galaxy S I9000 Android Development] bilboa1:
if you reset through the cm settings, yes, you should setup the apps you want notification for
[Galaxy S I9000 Android Development] DvTonder:
Under Miscelaneous settings I set up my 3 apps - calls, gmail and chompsms with white as the selected flash colour. I only have the option to select from 'slow' to 'fast' blinking with no option to set 'always on'. I am unsure what to set this to.

In the advanced settings everything is unchecked.

I am running the 03/26 update of CM7.

LED's dont work
[Galaxy S I9000 Android Development] bilboa1:
try that, tell me if it works (captivate only kernel!):

http://kang.project-voodoo.org/f/CM7/test2919.zip

For those who get FC, try to wipe the cache
[Galaxy S I9000 Android Development] Bo$s:
It happens for me too but it's really hard to reproduce.

i9000

20110329_03 kernel
[Galaxy S I9000 Android Development] charkey:
Others have reported this problem before but I'm going to try to better explain it with this scenario. It seems as though whenever the BLN goes off (after a text, gmail, etc.) there is a bug with the back button. Here's the order of events that happen so that you can reproduce the bug:

1. Text comes in

2. BLN fires off the LEDs

3. Unlock the phone

4. Phone will keep hitting the back button to go to the original screen

5. Problem can be fixed after touching any one of the buttons (in this case I use the home button)

6. Problem is resolved and I can use the phone normally.

Hope this helps!

Also note that this is using the Vibrant kernel.
[Galaxy S I9000 Android Development] ashwinds:
I couldnt get it to work with the 29th release either (i9000 Galaxy S). Had to go back to 27th release.
[Galaxy S I9000 Android Development] BlackDino:
Is there any way to get LED notifications settings in MIUI?

Thanks,
[Galaxy S I9000 Android Development] buzzworkers:
I got also this, backup your apps do a wipe/reset factory

flash the kernel, flash gaaps, reboot, restore your apps

solved all this crash apps all at once, i'm not even sure it's the kernel fault.

because if you do a fresh install, reboot, then recovery and flash the kernel

you will see that everything is just fine.
[Galaxy S I9000 Android Development] DvTonder:
Can you please share your exact per app led settings. I reverted to 2716 and get the turning off led problem.
[Galaxy S I9000 Android Development] BTTNext:
Boots up perfectly, but the touchkeys never get initialized. :(
[Galaxy S I9000 Android Development] domy1985:
Bln does not work at all for me even if i enable it in led settings
[Galaxy S I9000 Android Development] bilboa1:
at which last one do they get initialized? or are you just talking about leds not lighting on resume ^^
[Galaxy S I9000 Android Development] gabby131:
Do i need to adb push the cm7part.apk and then apply this test2919.zip kernel? Almost home....testing soon...thanks
[Galaxy S I9000 Android Development] bilboa1:
dont try test releases i make for a specific person ;)

new test version up.. tell me if it fixes the kills/close and if anything new is broken lol

i hope to have a test for cappy/vibrant at least

ps: it intentionally breaks timeout a bit :p

fixed it real quick xd

thx
[Galaxy S I9000 Android Development] ashwinds:
I meant that I couldnt get BLN going at all with the 29th version. IT works with the 27th version, but I dont know how to keep it "always on" - only blinks.
[Galaxy S I9000 Android Development] SweetwaterBurns:
Kernel 30_04 seems to be working fine with captivate. Rebooted several times and no issues getting into recovery. Guess I'll just wait and see if you broke anything else.
[Galaxy S I9000 Android Development] Steyux:
30_04 seems to correct all the issues, but I need some more test :D

Galaxy S I9000

Thanks bilboa1!
[Galaxy S I9000 Android Development] gabby131:
Ouch.....that's what I get on not reading carefully.

Testing 20110330_04....so far so good .....thanks

Sent from my SGH-I896
[Galaxy S I9000 Android Development] Mercury0660:
30_04 still has broken touchkeys, but lock/unlock solves it. OK for me.
[Galaxy S I9000 Android Development] bilboa1:
you mean at first boot or?

phone model / dmesg after lock might help, specially "failed to write" stuff or "touchkey not responding"
[Galaxy S I9000 Android Development] pafnucy7:
hello

I have also problem with touch keys, for "restart" the keys I need switch off/on display then is ok, i9000, miumi rc2
[Galaxy S I9000 Android Development] evensteven:
Hmm... For me the touchkeys are fine (International I9000). These weird app closes are gone.

But I can't get the notifications working. F. e. I choose missed call, set a bright color (white), set blinking to medium or something and nothing happens when i get a missed call. Any magic trick I missed to get it working?!?
[Galaxy S I9000 Android Development] bilboa1:
try the button to test flash to see if its working, inside the same menu

in general, green is the default led color
[Galaxy S I9000 Android Development] DvTonder:
Seems like it is finally working. Will test more in a bit.
[Galaxy S I9000 Android Development] DvTonder:
It can now blink on and off. I like it!

Don't know how to make it stay on but not sure I care.

Thank you. Great progress.
[Galaxy S I9000 Android Development] evensteven:
Doesn't work at all. There's nothing else I need to set, right?

Here is the dmesg output after firing off a few tests: http://pastie.org/1734821

Btw. is there any way to filter this output a bit for your purposes?
[Galaxy S I9000 Android Development] Mercury0660:
ok, i'll take a log. it is after every boot.

model is i9000

this is after lock /unlock

http://pastie.org/1734921
[Galaxy S I9000 Android Development] bilboa1:
according to this there's no problem, led is turned off once and that's all (android does that at boot)

probably android is not triggering the led, it means its something in the settings.

go in cm's led settings and setup notificationes for one app (eg chrome2phone is easy to test with)

for my purpose complete output is probably better. in general i'm looking for:

notify_led_off <= means the kernel is requested to turn led off

notify_led_on <= same, for on

touchkey messages:

"write error" (or read etc), means the touchkey either tried to read/write to the keys while the device is OFF/sleeping, or the touchkey firmware just ****ed up (happens)

touchkey not responding: means an incorrect sequence has been written and the touchkey will be disabled until next lock/unlcok

recovery_routine: means a failure has been detected and the driver attempts to auto recover from the error (if it fails you usually get the not responding shortly after)

Other things: various s3cfb_late_resume and request_suspend_state, this is when the device goes to sleep (screen off) and back on (technically, suspend state is system wide, the late resume of s3cfb is just the screen, but in practice its about the same as if the complete phone was out of sleep)

the timing in front of each message can tell how long it took between led on/off for example

i'm going to write a small "how to" for who is unfamiliar with the led settings, especially that in the sgs case they're not really leds so it might be confusing. most "led apps" ive seen such as noled, bln, led blah, etc write all those settings for you. In CM its not as fool proof and it has more settings -

in your case, theres zero touchkey message, nothing failing or working.maybe earlier in the log (just after boot?) it has some more info such as touchkey not responding.

Since you seem so far to be the only one i could see with that issue, please make sure you flashed the correct kernel - just in case
[Galaxy S I9000 Android Development] bilboa1:
Added a FAQ in the first post how to trouble shot issues and how to use LED stuff, in case there's any misunderstanding or further troubles, please check it if there's something you don't understand etc (it's also a rewrite of my previous post for some points of course)
[Galaxy S I9000 Android Development] blyfoten:
30_04 made my day! THANK YOU!
[Galaxy S I9000 Android Development] Mercury0660:
the kernel is correct.

As far as i understand that dmesg things, this log is from the beginning of boot or not? Else I don't know how to get a log from earlier events then the one i posted. I typed dmesg just after the first time i got adb access from starting the handset.
[Galaxy S I9000 Android Development] DvTonder:
Possible bug:

I have no notifications yet my lights turn on when the phone is locked.

I noticed the lights were on solid. I unlocked the phone and had no incoming messages etc. When I locked the phone again the lights turned on again.

Since I have my per apps LED settings to fast blink, the solid on LED is not something triggered by any of the configured apps. I had the phone charging and had run a Titanium scheduled Backup, either of which could have triggered the LED state but since all notifications were cleared I am not sure what the triggering event was.

I have now rebooted and the LED's are once again off as they should be. I will monitor and post here if the problem shows up again.
[Galaxy S I9000 Android Development] derrzredeem:
for me the test flash is not working too, though led is on when there's a notification, test flash was fine in 29_03 - i even can set it like what i want blinking or always on, quiet hours. The only problem for me (29_03) was the instant close/kill apps.

here's the /proc/kmsg output http://pastie.org/1735148

my touchkey is broken too after a reboot, but i can't find anything about read/write error in dmesg output, guess i'm not that fast :o
[Galaxy S I9000 Android Development] Mercury0660:
that describes my problems too
[Galaxy S I9000 Android Development] bilboa1:
dmesg has a limited buffer size, so if you're phone is on since a while (in fact, 5min are enough) the top of the log is not kept, that's why it's missing. turning screen on/off for example generate a lot of messages that will the buffer quickly.

it's a ring buffer, aka when its full, it keeps getting new messages and old ones are deleted progressively (like a circle/ring)

when you turn off/on the screen this should reset the LEDs every time as its a hardware reset, unless Android is requesting the LED to be lit (this can be an app or w/e).

To confirm that:

adb logcat |grep lights (linux) or just adb logcat and look for messages starting with lights

it will say when it tries to lit up the led or turn it off

what _can_ happen, is that android asks for the let to be lit (eg via blink) and that the last message to turn off the LED is lost, in that case, there would be "turn on led" message last and no "turn off".

it can also be the behavior a program "wanted to achieve", hard to say. it can also be that it expects to "set flashing mode" (blink) and that the led turn off on its own. android specify that no program should assume that, but maybe some do.. in that case, well, i might have to implement "driver level blinking" to avoid it.

in all cases you can reset manually with that also (not convenient but to help debug:)

adb shell echo 0 > /sys/devices/virtual/misc/notification/led (path from heart i hope its correct :P)
[Galaxy S I9000 Android Development] bilboa1:
always on means "on when screen is on" the driver currently does not support that btw

(mostly because it makes no sense for us)

about the log, it only tries to turn off the led as you can see, you can try to see whats in logcat about that, it should correspond

i believe this kind of issues are solely settings based however
[Galaxy S I9000 Android Development] Mercury0660:
my phone was on about 60 seconds. I don't think I can get more out.

Another question.

My music becomes laggy when screen is off. What are useful settings for cpu frequency and governor?

edit: minimum 200 works. but will suck more juice. is there another possibilty?
[Galaxy S I9000 Android Development] derrzredeem:
hmm...maybe i describe it wrong, what i meant for always on is:

f.e. email in

screen off = led is on

screen on = led is off

i tried the same settings like i was on 29_03 to make the led on/blink when i click the test flash button with no luck.

the notify_led_off appears when i try to test flash (sorry if i'm wrong *knowsnotmuch) :)
[Galaxy S I9000 Android Development] bilboa1:
i use 100-1200 and ondemand governor, no issue - i use poweramp & winamp also, but i expect the stock players to work just as well - never ever skips with screen off. i t might be player related or you might have other apps using the cpu in the background at the same time (although ondemand should scale up..)

i might have inverted your log and the other guy log tho, i don't remember xD but looking at your prvious post its including approx the complete dmesg (first msg timing start at 0s aka boot)

and it just disable led once and thats all it does, so probably settings
[Galaxy S I9000 Android Development] bilboa1:
i'm talking about the always on option from CM, which does what i described

for the test flash, maybe try to change the led color

, at least, it should send a notify_led_on (also, look at logcat too, stuff that starts with light, might give you more info about what android wants)

f.ex. if you are in quiet hours its going to be notify_led_off, and looking at log cat you will see a color set etc and final result "status 0" (=off)

another example, if it displays all 0, it means android really wants the led off
[Galaxy S I9000 Android Development] derrzredeem:
oc'ed to 1.3Ghz, and i can say it's pretty stable, never had a freeze or random reboots with this settings - tried uv it even more but keeps freezing:

1300 - 25

1200 - 25

1000 - 50

800 - 50

600- 100

400 - 100

200 - 100

100 - 125

btw, governor is ondemand.
[Galaxy S I9000 Android Development] Mercury0660:
ok, i think my problem is because of a script from zacharias thread, that distinguishes between screen on and screen off governor. I used ondemand for display on and powersave for display off, BUT when i go to cm settings there always stands conservative as active. I don't understand that. Is this script "killed" when flashing a new kernel?

it's the screenscaling script by flohimself
[Galaxy S I9000 Android Development] Killemalll:
I'm using the following UV setting at 1.2Ghz, fully stable:

1200 - 25

1000 - 50

800 - 50

600- 75

400 - 75

200 - 100

100 - 100

Everything works, but I'm experiencing massive battery drain (wifi off) just streaming Pandora on 3G.

Does the latest kernel revision include the wifi interrupts fix released with the latest CM7 nightly update? Is the fix kernel related?

(SGS Captivate)
[Galaxy S I9000 Android Development] derrzredeem:
ah, that script, tried it with the same result as yours.

i'm not sure if flashing a new kernel could killl it, you should check it in /etc/init.d if it's there you could just remove it.
[Galaxy S I9000 Android Development] Mercury0660:
yes, i found and removed it, i'll check everything after reboot.

ok, works, thx
[Galaxy S I9000 Android Development] Spirit02:
I9000

26.03

30.04

Haven't been able to get backlights to work at all (when screen is off) since the switch to CMParts. Colour is set to green, can't get the test function to make them light up at all, regardless of blink speed.

Dmesg

http://pastie.org/1735658

brief logcat

http://pastie.org/1735674

This line concerns me a little:

I/InputManager-Callbacks( 156): No input device calibration properties found for device cypress-touchkey.
[Galaxy S I9000 Android Development] bilboa1:
both are logcat, no dmesg

anyhow, theres zero call to the lights server once started in these logs, means android never tried to light up the led (=setting)

if the touchkey work fine except the led notification, nothing to worry about
[Galaxy S I9000 Android Development] BTTNext:
@bilboa1

Just wanted to report that 20110330_04 is working great on the Captivate. Many thanks!

EDIT:

I'm getting a lot of these errors in my dmesg:

Is this normal?
[Galaxy S I9000 Android Development] DvTonder:
This latest kernel is great! Full day of LED notifications working!

Not sure if it is the JVK modem or this kernel but I have a significant improvement in battery life. Usually I was around 30% this time of the day, today I am at 55%.
[Galaxy S I9000 Android Development] joaoennes:
I think is the modem, since I switched to JVK I noticed a little better battery aswell. :D
[Galaxy S I9000 Android Development] bilboa1:
yes & no ^^

if you find when this happen we can determine if its "normal" or not.

eg "led was on and i was turning screen on" or smth like that (need adb shell cat /proc/kmsg running "live")

if you have no issue with the led lighting up, then it's no problem anyway, but i'm still curious where it happens
[Galaxy S I9000 Android Development] trustsyzaa:
i have a weird colour like in my attachment i try to fix this in voodoo control app but it's still the same,could you please suggest me about that.thanks.
[Galaxy S I9000 Android Development] Mercury0660:
I don't understand one behaviour of the phone, when the screen goes off after the desired time limit, it should first become darker, but mine becomes green (like a green rendered). Is this normal?
[Galaxy S I9000 Android Development] trustsyzaa:
yes me too,but for me when im watching a video when the colour is black it show me a bit green

that's the question im waiting for some answer to adjust it to normal.
[Galaxy S I9000 Android Development] bilboa1:
sleep/resume sometimes does that, it's not specific to this kernel afaik, its just kinda rare
[Galaxy S I9000 Android Development] Mercury0660:
but it doesn't hurt the display or something?
[Galaxy S I9000 Android Development] crypta:
sensor buttons are broken, SGS 0330 update 4 kernel.
[Galaxy S I9000 Android Development] Lazy Rich:
Mine too. Pressing the power button to lock the phone and immediately unlocking it again fixes that for me.
[Galaxy S I9000 Android Development] SweetwaterBurns:
On my screen, if I go under the CyanogenMod settings and manually tweak the auto-brightness settings, setting it below the initial low value of 20 affects color. It's only slightly noticeable until I go below 12, when it will dramaticly shift to green.

I do not know if you have tweaked those settings, but you might try raising the lowest brightness a bit.
[Galaxy S I9000 Android Development] trustsyzaa:
thank you very much:)
[Galaxy S I9000 Android Development] bilboa1:
updated

10 chars
[Galaxy S I9000 Android Development] sayli:
Thanks for the all the work bilboa ! I'm gonna test your kernel :P. I just had one question ! Do you add nightly's change to your kernel too? I mean, like the headset is kinda fixed in the last nightly, will it be fixed in your's too? Or it's not kernel related and i'm totally wrong? xD
[Galaxy S I9000 Android Development] bilboa1:
yes i updated that too, forgot to put in changelog, will put ;)
[Galaxy S I9000 Android Development] sayli:
Great then =) Flashed it and everything going fine so far! It's amazingly smooth compared to all samsung's rom i've tryed. Everythin respond like 1/10 seconds after u pressed on it! I love cm more & more everyday :)
[Galaxy S I9000 Android Development] Steyux:
I've noticed a strange issue, I've flashed the new nightly and the new kernel, and then I've reinstalled cmparts.apk... But this broke led notification.. So I flashed 26_16 kernel and then again 31_21 and everything was fine!!! :confused:

BTW great job bilboa1!!!
[Galaxy S I9000 Android Development] DvTonder:
Exactly the same thing is happening to me. I will try to flash the earlier kernel and come back as well and see if I can replicate your solution

UPDATE: Confirmed! Reverting to the older kernel and then reinstalling the newest kernel fixed the lights for me as well.
[Galaxy S I9000 Android Development] f.lix.droid:
hmm i noticed something really strange....i can't seem to set what cpu governor i want for a long time....say i choose ondemand, but then i noticed, just moments later it'll switch back to conservative....anyone knows what's going on? thanks :D
[Galaxy S I9000 Android Development] bilboa1:
you probably flashed another kernel and there's the script to change the governor automatically that is left over

its somewhere in /etc/init.d/90... or so i think.. otherwise look at zach's thread the path is prolly there ;-)
[Galaxy S I9000 Android Development] f.lix.droid:
sweet thanks for ur reply!! also i just noticed my phone just suddenly froze and restart by itself....happens quite a few times already....thought id let u know...
[Galaxy S I9000 Android Development] evensteven:
Did the same. Now it's working for me too. Thanks! :)
[Galaxy S I9000 Android Development] kenkiller:
So some files were missing the in later kernels?
[Galaxy S I9000 Android Development] kenkiller:
Works....maybe due to flashing fresh copy of CM7 and not having the previous files installed by the previous kernels. Maybe bilboa can look into including the older libraries in the newer kernels as well?
[Galaxy S I9000 Android Development] Spirit02:
FINALLY!

For whatever reason, the modules weren't getting replaced during the cwm install process.

After manually replacing them (and lights.aries.so for good measure), and setting permissions, LED notification works :D

The 'test' function in the settings doesn't light up, for anyone hoping it will...

Cheers bilboa.

Now if I could just get wifi to reliably get an IP address, and better battery life (still losing 10% overnight, even with jvk & uv), then I'd have an awesome daily driver.
[Galaxy S I9000 Android Development] Adevem:
just went through the commits in github and compared it to zach's.

this is the kernel that's closest to being "stock" CM7 kernel + OC/UV + voodoo modules... right? lol. don't really want such a "bloated" (no offense to any devs) kernel.

nonetheless i've given it a shot.
[Galaxy S I9000 Android Development] Ferdimage:
Thanks Bilboa lovin the latest kernel mixed with CM7 31-03 update and JVK modem!

Super smooth and decent battery drain.
[Galaxy S I9000 Android Development] buzzworkers:
Just lost my wifi after flashing the latest kernel version...it stay forever looking for an IP address. strange part is that if i ho back to previous kernel, wifi works just fine...any hint?