yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] DvTonder:
OK, I am making progress.

With the phone plugged into USB and the above command running, the behaviour is as intended:

This is the text message coming in

This is the gmail message coming in

However, once I unplug the phone from the USB, the old behaviour (lights going off after approx 2 seconds) returns.

Running dmesg in terminal on the phone, this is what I get when a message comes in: (Sorry for the amount of text)

Debug info removed.

Hope this helps.

I will delete the contents in this message once you have reviewed it as I don't want to clutter your thread with debug output.
[Galaxy S I9000 Android Development] bilboa1:
you can use pastie.org for such pastes (tho i dont care for the thread clutter too much)

in the log there doesnt seems to be any error

in short, as you might expect:

notify_led_on (android request to turn on led) => led is turned on and stays on until either:

- notify_led_off is called (android request to turn led off, means an app or android itself decided so)

- screen goes off/on (in that case, you have another call to notify_led_on as the kernel knows the switch was not requested by android, to reactivate the led - its fast enough that it doesnt blink, except for turn on of course, as led is not re-enabled with screen on, until screen goes off again)

that might help you find out more closely whats happening, but it might be either:

- the i9000m is slightly diff (try dmesg|grep hardware after the phone booted, it gives the touchkey firmware version, then paste it here)

- one of your app or android really turns off the led

- something spooky which i can't put my finger on right now ;-)
[Galaxy S I9000 Android Development] DvTonder:
$ export PATH=/data/local/bin:$PATH

$dmesg|grep hardware

<6>[ 4.694878] cypress_touchkey_driver 10-0020: cypress_touchkey_probe: hardware rev1 = 0x4, rev2 = 0x1
[Galaxy S I9000 Android Development] boarder.2k9:
Ahh my phone can't handle -125mV at 100Mhz. It causes a reboot within a minute or two of saving the setting. 100mV works though (well it worked before so i guess it will now :D).

By the way everyone, 'official' gingerbread appears to be out (i say 'official' because loads of people are arguing over whether or not it is) but heres a link to latest modem (XXJVK) (thanks zach):

http://www.multiupload.com/EBPI1FAPSX
[Galaxy S I9000 Android Development] bilboa1:
that's indeed a different firmware from the GT-I9000 (rev1 = 0xa9, rev2 = 0x3) although it doesn't mean that it is necessarily the reason (but it could be)

if it is i'm not sure how to troubleshoot it - it would be good if another I9000-M user could report the same trouble (or another user at all, if possible with I9000 ^^), so that we're more confident its not caused by some background process etc... then i could also up a kernel just for you with a lot of "printk" telling what's exactly going on
[Galaxy S I9000 Android Development] fireymint:
Im having the same trouble as DvTonder (led light turn on for 2 sec then goes off).

as well as cocchiararo (keyboard coming out when phone turned on).

The second one might not be kernal related though.

Using GO sms fyi.
[Galaxy S I9000 Android Development] DvTonder:
I just experienced the keyboard coming out issue as well.
[Galaxy S I9000 Android Development] apewall:
Latest kernel puts my captivate in a bootloop. :/

Also, never has BLN worked at all for me on it yet.. :/ :/
[Galaxy S I9000 Android Development] gabby131:
im stuck after the latest kernel (20110327_16)......cant even boot into recovery.....need to re-flash >_<

EDIT: okay back in action.....trying to flash that again....maybe i just did something not right.
[Galaxy S I9000 Android Development] baba420:
Please bring more battery savings profiles like that. I love it, works great here.
[Galaxy S I9000 Android Development] cocchiararo:
It never happens if the phone is locked.

but of there phone is not locked and screen is off, waking it up triggers a vibration and keyboard comes up.
[Galaxy S I9000 Android Development] zacharias.maladroit:
if you don't like my kernel & nevertheless want to have powersave governor enabled

you can use my 2 scripts (available for download in my thread - see sig)

this is also sort of a "battery savings profile" (while the screen is off)
[Galaxy S I9000 Android Development] derrzredeem:
yes...i get that too.

not sure if it's kernel related tho
[Galaxy S I9000 Android Development] -Yaya-:
Just flashed the newest CM7 Update (update-cm-7-03262011-NIGHTLY-GalaxyS-signed.zip) and the newest kernel update (CM7_GT-I9000_kernel_kang_20110327_16_update.zip)

I dont actually know whether this is kernel related or related to the new CM7 update but now my phone has a SIMLOCK!!

I unlocked it several months ago using this and it worked perfect until I updated today... I did the procedure again but still no changes, lock is removed in nv_data.bin

EDIT: THIS IS GETTING REALLY WEIRD; Phone asks me for an unlock code now, If I want to call someone I get an error: no Simcard inserted. Same for Mobile Data.

But If somebody calls me everything works perfect, I can talk etc!

Oh and I also just had the keyboard-vibration bug (kernel related?) :D

EDIT2: O_o just reverted back to update-cm-7-03122011-NIGHTLY-GalaxyS-signed.zip and CM7_GT-I9000_kernel_kang_20110323_02_update.zip where everything was working before... still no change!! :(

EDIT3: I deleted some files (old roms/kernels) on my sdcard before I flashed the updates to gain some space, could this be related to my problem?!

HELP!!!
[Galaxy S I9000 Android Development] branalvere:
I am running the latest MIUI build 8.2 with the latest bilboa kernel and the UV sliders don't work now. They did on the previous MIUI beta and CM7 users don't seem to be reporting issues so I'm guessing it's down to the MIUI build rather than the kernel.

Shame because I would like to test the powersave set up with MIUI as it's by far the smoothest 2.3.3 ROM I've tested to date

Edit : the sliders will work by tapping around them randomly but not as they should. Testing the UV settings now
[Galaxy S I9000 Android Development] Steyux:
A question for bilboa1

In 26_04 and 26_16 notifications for the sms (with stock app, but also with go sms) works very fine :D

In the next releases when I receive an sms the light goes up for 1-2 seconds and then switch off, is there any reason to this behaviour?

I've tried to flash these kernels without making changes in any setting of the sms app and system, and when I flash 26_04 or 26_16 the light notification works fine and when I flash the next releases they are crappy :(
[Galaxy S I9000 Android Development] BTTNext:
Having the same issue as you on a Captivate. Sometimes it boots up, sometimes it reboots after showing the Galaxy S Cyanogen logo. Pretty random, can't get into recovery.
[Galaxy S I9000 Android Development] BTTNext:
This has nothing to do with the kernel AFAIK.
[Galaxy S I9000 Android Development] gabby131:
Fixed this....just download the default cm7 on the cappy (initial kernel) and flash it via odin (uncheck autoreboot) then boot to recovery, flash a stable kernel.
[Galaxy S I9000 Android Development] bilboa1:
for the led going off.. its 9s and its the default setting in CM7 - i don't know exactly why - also why they bypass it when powered hrrm

see device/samsung/galaxys/overlay/frameworks/base/core/res/res/values/config.xml

and

frameworks/base/services/java/com/android/server/NotificationManagerService.java

there must be a difference somewhere on the nexus s and probably others
[Galaxy S I9000 Android Development] jetdite:
CM7_Captivate_kernel_kang_20110327_16_update still not good enough:

- New sms: BLN work but it turn off after 2-3s

- New missed call: BLN work but it was like blinking 1-2 times then turn off

Looking forward to a stable BLN like it was in 2.2 rom: new notification -> softkey turn on and stay there until the notification cleared, no matter the screen on or off.
[Galaxy S I9000 Android Development] BTTNext:
Yeah it's not complicated to flash back, the tough part is to figure out what is causing this.
[Galaxy S I9000 Android Development] cocchiararo:
anyone knows what all the latest commits are for ? :P (not one is something i could understand)
[Galaxy S I9000 Android Development] baba420:
I'm not familiar with adb. It would be great if you could make an update.zip package of that script.

ps. Just flashed your kernel. The keyboard pop-up bug is gone.

==

Please fix the keyboard pop-up bug.
[Galaxy S I9000 Android Development] boarder.2k9:
noooo it just stated doing the 2 second bln timeout after message comes in on my i9000 :(
[Galaxy S I9000 Android Development] bilboa1:
yeah as i found out in an earlier post, its actually an android setting, so you might or might not have it, and there's no real interface for it

CM7 provides some such options so i'm looking into it so that we can set it to what we want. you can set it blinking, the blink duration, etc.. would be good to also set "always on", "no blink" "always off". but i haven't found an UI for these options yet. might have to add them.

the cm7 options (cmparts.apk) are NOT enabled in the SGS's and friends currently so don't go looking for them :)

they will be enabled upstream if i find out which ones make sense and can do the above.. anyone who's familiar with that stuff and wanna help (or has another phone which has these options in CM) feel free to chime in.
[Galaxy S I9000 Android Development] Mercury0660:
keyboard popup is very annoying when receiving a call.
[Galaxy S I9000 Android Development] Hayden4018:
same thing is happening to me
[Galaxy S I9000 Android Development] cocchiararo:
ok, this post was meant for the CM7 thread, sry :P
[Galaxy S I9000 Android Development] dxtrlabs:
Same for me
[Galaxy S I9000 Android Development] blyfoten:
Same for me...
[Galaxy S I9000 Android Development] bilboa1:
same for me

:D
[Galaxy S I9000 Android Development] Uss_Defiant:
Just installed CM7, and I know there's supposed to be a colour change with 2.3.3, but still looks quite bad even with the kernel running. Is there some way i'm missing to enable the voodoo colour fix?
[Galaxy S I9000 Android Development] derrzredeem:
Install voodoo control app [?]

~drz
[Galaxy S I9000 Android Development] Uss_Defiant:
Sorry didn't realize that there were settings there. Anyone got close good colour settings?
[Galaxy S I9000 Android Development] derrzredeem:
Hi bilboa1,

flash an "official" kernel, apparently the keyboard bug wasn't there.

here's an output http://pastie.org

Hope you could take a look.

For me, the actual 2.3.3 color is pretty good just a bit to yellow, so i add some blue in RGB settings: 2413362720

my settings for gamma:

red: -30

green: -34

blue: -36
[Galaxy S I9000 Android Development] dxtrlabs:
Hey what in 29_03?
[Galaxy S I9000 Android Development] bilboa1:
give me time to finish icecream!

i made a few changes in the handling

i suppose it works fine now although i'm not sure about the keyboard popup issue (as usual i dont rly get that lol)

at least leds will stay on and you can also now configure the leds per app, you just need to follow this quick procedure:

- adb shell rm /system/app/CMParts.apk

- adb push CMParts.apk /system/app

- adb shell killall system_server (or restart your phone)

Then go to menu settings => cyanogen=>interface=>LED notifications and figure it out on your own its not _that_ complicated

for led colors always chooose a BRIGHT color or it will detect it as quiet times (=LED off). That's a little issue from CM7.

CMParts.apk that u need is there (its stock, no source change, just LED stuff enabled):

http://kang.project-voodoo.org/f/CM7/CMParts.apk
[Galaxy S I9000 Android Development] dxtrlabs:
Can i just place the file with root explorer?
[Galaxy S I9000 Android Development] bilboa1:
prolly yeh

but ' need to install the apk afterwards
[Galaxy S I9000 Android Development] kenkiller:
I tried replacing the file via Root Explorer before flashing (since gonna have to reboot to flash).

FCs on entering Cyanogenmod settings. Tried with adb, works fine. But YMMV. :D
[Galaxy S I9000 Android Development] dxtrlabs:
Ok worked great replaced file and rebooted ran fine....but 2 things.....1 I'm getting an aplocation kill notification as if i long pressed back everytime i unlock....and also i get a bug opening text messeges....the com in led notify correctly but i try to open and it backs me to the inborn y try again and same....it happens 2 now it stooped doing it but ill let you know ......
[Galaxy S I9000 Android Development] BTTNext:
Just flashed 20110329_03 on I897 -- doesn't go beyond the Galaxy S/CyanogenMod logo. Reboot loop is infinite as far as I can tell.
[Galaxy S I9000 Android Development] Killemalll:
Same issue here on my Captivate. I tried flashing already a couple of times. Went back to the previous revision for now.
[Galaxy S I9000 Android Development] :
help with kernel!!!

Hi i tried to build cm7 kernel for telus fascinate (not verizon one)

i found that the only diffrence between i9000 and fascinate is the key mapping. ( my home key and search key dont work!)

i tried to flash captivate kernel and touchkey worked fine, but the speaker and headphone fuction got reversed and the gravity sensor not working.

So i think changing i9000 cm7 keyboard driver to captivate cm7 keyboard driver would work perfectly, but i dont know how.

I tried and I spend about 1week, but i failed.

Can somebody make one for telus fascinate users?

or tell me how to do it step by step?

The file that i attached is the captivate cm7 keyboard driver
[Galaxy S I9000 Android Development] derrzredeem:
Flash your latest kernel 29_03, and it seems to fix the keyboard pop-up bug and no problem with led - i never had a problem with your prevoius anyway, thanks man. However, i lost root, push busybox and everything is fine again :D
[Galaxy S I9000 Android Development] Mercury0660:
latest kernel (29)broke my touchkeys. They are shining bright, but don't function, going back to 27...
[Galaxy S I9000 Android Development] Steyux:
Same issue with my sgs i9000
[Galaxy S I9000 Android Development] bilboa1:
so hmm it sounds like everything works just fine except for captivates

anyone has a captivate he wanna get rid of?! xD
[Galaxy S I9000 Android Development] Mercury0660:
i have a i9000 and my touchkeys broke, so no, not everything :D
[Galaxy S I9000 Android Development] boarder.2k9:
I replaced with root explorer and it fc so I went into system/app and installed cmparts.apk then it worked fine. I also did a reboot.

Works awesomely on my i9000 bilboa, thanks so much. Not a problem at all so far, loving the extra functionality you bring!
[Galaxy S I9000 Android Development] kenkiller:
Currently CMParts led only allows blinking correct? Is there a way to make it stay constantly on like in the previous version?

Doesn't flash fast enough for a quick glance.
[Galaxy S I9000 Android Development] joel88:
hello, is there any problem if i just install your new kernel, and don't install your apk????
[Galaxy S I9000 Android Development] gabby131:
oh boy....looks like with the above....hooh haah!!!!

@_@
[Galaxy S I9000 Android Development] bilboa1:
no problem
[Galaxy S I9000 Android Development] bilboa1:
my "personal testers" didn't get this issue so far, so more info would be welcome. actually i'm not sure how that can happen at all ;o

you should be able to get both blinking and non-blinking, although it require playing with the settings a bit as if it was a LED
[Galaxy S I9000 Android Development] kepke:
It happens to me too, clean install, 26.03 with 29th kernel on i9000.:cool:

I’ll be happy to provide any info needed.

EDIT:

WAIT!! now it works.

WTF?

locking and unlocking fixes the issue.
[Galaxy S I9000 Android Development] kenkiller:
Hmmm....i looked at all the led settings, only blinking allowed. Have u managed to make it not blink and stay on?
[Galaxy S I9000 Android Development] Mercury0660:
so how can I get you info? Logcat doesn't say anything
[Galaxy S I9000 Android Development] derrzredeem:
don't tick anything in advance settings, that will make led always on. directly go to application

works great on my phone ;)
[Galaxy S I9000 Android Development] DvTonder:
can you explain what you mean by "I went into system/app and installed cmparts.apk ". I get the FC as well and dont quite understand what you did to fix it.
[Galaxy S I9000 Android Development] kepke:
here's the logcat

http://pastebin.com/h3K7Az3W
[Galaxy S I9000 Android Development] derrzredeem:
@DvTonder:

click on CMParts.apk in/system/app using Root Explorer, that will give you the option to install.

i'm pretty sure that is what he/she means
[Galaxy S I9000 Android Development] Steyux:
In my device (a standard i-9000) is only possible to set the blinking, and this blinking is too fast. I've unticked all the advanced options... And in addiction there is this issue http://xdaforums.com/showpost.php?p=12484947&postcount=758

I've tried reflashing several times but nothing changed, can't post a dmesg or logcat beacause I'm at work

Despite this defects, all working great

Thank bilboa1 for the amazing kernel :D
[Galaxy S I9000 Android Development] bilboa1:
yes, cmparts *must* be installed

the reason it is removed by hand first is that you cannot installer over it or overwrite it, you have to first delete it, then it let you install it

maybe i wasnt clear enough on that point

other questions have been answered by others as well (thanks :-)

also, once again, cmpart is only to get the advanced functionality (per app settings, blinking etc)

eventually this might be enabled in CM7 by default in the future, so i didn't make a convenient zip installer for it yet ;-)

it also depends a lot on your version of CM7 (works on latest for now)
[Galaxy S I9000 Android Development] joel88:
if i don't installed the cmparts because i don't know so much about the adb,,,,is the BLN will work like before??(just like previous kernel's setting)

sorry for my poor english:p:p
[Galaxy S I9000 Android Development] cocchiararo:
hey, i moved to MIUI, and the keyboard issue was there... only after restoring SOMETHING, dunno what.

a factory reset later, it was gone.

i guess something was broken also on CM7, i bet those who have the same issue i had, will not have it anymore after a factory reset or starting from scratch. (restoring apps is ok :P)

------------------------

is your newer kernel still miui compatible ? i guess cmparts is not a miui component, what can we do in that case ? :P
[Galaxy S I9000 Android Development] bilboa1:
as i already said: oui/yes/ja/ok/no problemo ^^
[Galaxy S I9000 Android Development] joel88:
thanks a lot~ :):):) sorry for bother you, :D:D i don't fully understand what you said before because my poor english:(:(

now i understood :D:D:D:D:D:D:D

\thanks you very much, you are a good guy:):):)

and i get a bug after flashed this kernel: when i get a notification by my facebook, i unlock my phone and press on the message on my notification and try to launch my facebook app, it immediately back to home screen,(it's like i press the back button immediately when i launch the app), and the press the back button again, the problem fix, and next time when i get a message from facebook, the problem occur again
[Galaxy S I9000 Android Development] Hayden4018:
same here, best kernel at the moment except this issue http://xdaforums.com/showpost.php?p=12484947&postcount=758

keep up the good work
[Galaxy S I9000 Android Development] derrzredeem:
Yes that is correct, but if you tick force analog. It's the media volume that set to max instead of the gain.

And for me it's kinda ruin the sound.

~drz
[Galaxy S I9000 Android Development] sewe:
if I remember correctly supercurio think we should have the media volume on full and raise and lower with the app, which in turn becomes the volume buttons on the side in this case
[Galaxy S I9000 Android Development] TubeShaped:
omg this sounds so good now i need to try cm7!!! thank you
[Galaxy S I9000 Android Development] Bo$s:
Media volume doesn't cause small distortions cause it's digital gain. Analog gain causes distortions and other unwanted effecs so we should use as lowest analog gain as possible. This is why media volume should be locked on MAX.

Without Voodoo Sound analog gain value is locked in kernel and we can steer only with media volume.
[Galaxy S I9000 Android Development] derrzredeem:
@sewe & Bo$s

Ah, yes, you guys are correct.

It seems i've been playing too much with DSP settings, after i disable it. The output sound's back like i was on sammy.

Thanks for the enlightenment :)

~drz
[Galaxy S I9000 Android Development] funkateer2:
When flashing the original and this update, after restart from cwm there is a black screen for a while. Don't panic and just wait... until the sim unlock appears. Don't know if it as been mentioned before.
[Galaxy S I9000 Android Development] zacharias.maladroit:
yes, agreed

if you're not a poweruser (e.g. running dozens of apps at the same time that are download, syncing, etc. etc.) you won't probably notice much of the benefit of those patches

most of the patches I include in the kernel I've put through daily test use on my box so they definitely improve things but that is a whole different beast (quad-core with HT & 8 GiB of RAM) and you can't derive data from a multi-cpu, "workstation" to a small handset device

since the SGS is a memory constrained device at least all the "optimizations" that lead to less memory consumption (disabling debug, tinyrcu, etc.) are welcome

there are more upstream changes that lead to less memory consumption & interactivity improvements but they are probably too far off (for merge into Linus' tree with 2.6.39 or even 2.6.40) to work with 2.6.35-kernels
[Galaxy S I9000 Android Development] bilboa1:
most of the memory u gain by removing debug is from symbols, but that's not RAM, that's the memory on disk/flash.

there's other things which usually don't really change much especially as android freezes most background apps anyway

there's a good reason usually why some options don't make it upstream ^^
[Galaxy S I9000 Android Development] DROCSID:
Like it guys, my CM7 is now really smooth!!!

Had some problems, so I installed the whole 'new' initial process from cyanogen,

let it boot once, after put this one on it. No probs anymore.
[Galaxy S I9000 Android Development] google741:
@Bilboa

Thanks for this kernel.

Is there any way to fix the netfilter on cm kernel for using droidwall?

I'm using it a lot to block some 3g traffic
[Galaxy S I9000 Android Development] Aphova:
First, thanks

a lot

for this!

Now I have a prob...

:eek:Download mode is gone:eek: I flashed JV1 (rubbish) a few days ago and then went straight back to CM7 0225. Then accidentally went back to 0203 (thought it was the 0302 version). Since then I tried flashing every CM7 version I have (except the broken 0303 version) and nothing worked with wipes in between, re-odining the initial kernel etc. I then saw a link to this post for bootloaders and remembered I saw the stripey broken bootloader image before. So I flashed the SBL tar. The only diff is now the phone gets to the Samsung+Cyanogenmod screen and goes straight to recovery. No amount of playing with three buttons and swearing gets me to DL and ADB isn't showing anything. Two hours of searching and now I'm stressed :o

I'd appreciate some help :) Especially anything that doesn't involve a JIG :p Thanks
[Galaxy S I9000 Android Development] apewall:
First boot of kernel this occurs for like 30 seconds. then it seems fine.. for me.
[Galaxy S I9000 Android Development] coderunner:
If I want to go back to the original kernel can I replace the zimage in this zip file or does adding voodoo change more stuff than just the zimage?
[Galaxy S I9000 Android Development] bilboa1:
lock & unlock the screen after boot. it seems to be an upstream issue in the display driver. i might actually have a go at fixing it later.

(for the explanation: locking the screen shutdown the screen and unlocking reinitialize it properly - aka the boot init function has something wrong and the resume function fixes it)
[Galaxy S I9000 Android Development] bilboa1:
you can just change the zImage *and* add the modules in system/modules (.ko files)