yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] renaud:
Thanks for reporting, I also got that but wasn't sure which version caused it or if it was just me. It seems the modem firmware doesn't load as fast, I still have to find why.

EDIT:

at first sight, it seems to be the RIL daemon

<5>[ 12.067947] init: starting 'ril-daemon'

<6>[ 12.074683] init: Created socket '/dev/socket/rild-debug' with mode '660', user '1001', group '1000'

<6>[ 12.074968] init: Created socket '/dev/socket/rild' with mode '660', user '0', group '1001'

<6>[ 13.578746] warning: `rild' uses 32-bit capabilities (legacy support in use)

<5>[ 63.017971] init: process 'ril-daemon', pid 114 exited

<5>[ 63.018098] init: process 'ril-daemon' killing any children in process group

<5>[ 63.018458] init: starting 'ril-daemon'

<6>[ 63.019573] init: Created socket '/dev/socket/rild-debug' with mode '660', user '1001', group '1000'

<6>[ 63.019865] init: Created socket '/dev/socket/rild' with mode '660', user '0', group '1001'

<5>[ 112.608422] init: process 'ril-daemon', pid 846 exited

<5>[ 112.608549] init: process 'ril-daemon' killing any children in process group

<5>[ 112.608887] init: starting 'ril-daemon'

<6>[ 112.609705] init: Created socket '/dev/socket/rild-debug' with mode '660', user '1001', group '1000'

<6>[ 112.609999] init: Created socket '/dev/socket/rild' with mode '660', user '0', group '1001'

<5>[ 162.011457] init: process 'ril-daemon', pid 1058 exited

<5>[ 162.011585] init: process 'ril-daemon' killing any children in process group

<5>[ 162.011912] init: starting 'ril-daemon'

<6>[ 162.012724] init: Created socket '/dev/socket/rild-debug' with mode '660', user '1001', group '1000'

<6>[ 162.013011] init: Created socket '/dev/socket/rild' with mode '660', user '0', group '1001'

<5>[ 211.570621] init: process 'ril-daemon', pid 1067 exited

<5>[ 211.570813] init: process 'ril-daemon' killing any children in process group

<5>[ 211.571138] init: starting 'ril-daemon'

<6>[ 211.571936] init: Created socket '/dev/socket/rild-debug' with mode '660', user '1001', group '1000'

<6>[ 211.572220] init: Created socket '/dev/socket/rild' with mode '660', user '0', group '1001'

<5>[ 261.239237] init: process 'ril-daemon', pid 1079 exited

<5>[ 261.239430] init: process 'ril-daemon' killing any children in process group

<5>[ 261.239692] init: starting 'ril-daemon'

<6>[ 261.240580] init: Created socket '/dev/socket/rild-debug' with mode '660', user '1001', group '1000'

<6>[ 261.240803] init: Created socket '/dev/socket/rild' with mode '660', user '0', group '1001'

<3>[ 304.777103] in_atomic(): 1, irqs_disabled(): 0, pid: 1519, name: rild

<3>[ 309.409752] in_atomic(): 1, irqs_disabled(): 0, pid: 1519, name: rild

A small trace of ril: https://faramir.eriador.org/r/ril.trace.txt
[Galaxy S I9000 Android Development] ic3joker:
After flash to 1026 baseband become unknown. : ( revert back to 999 everything back to normal.
[Galaxy S I9000 Android Development] renaud:
Wait a little bit on 1026 and it will come back. I am searching the problem.
[Galaxy S I9000 Android Development] ic3joker:
its ok. i will flash the latest 1032. :D
[Galaxy S I9000 Android Development] renaud:
Also, this version of the ril daemon may not be fully compatible with 2.6.36, I will try to see if I can test a ril daemon from a galaxy tab
[Galaxy S I9000 Android Development] sptorrent:
Back Light

FYI:

The last few releases all have this (on my phone at least - and I don't remember on what version it started):

When waking the phone up, the back light takes quite a while to adjust to ambient light.

It remains dark for a few dozens of seconds, so when outside under the sun (it's summer now!!!), the screen it too dark to read anything - after those dozens of seconds, it lights up.
[Galaxy S I9000 Android Development] FadeFx:
I did a nightly update to 94 and installed my 1.2 update.zip, it sets ntp to at.pool.ntp.opg and installs angrygps, nothing else GPS related. Compass didn't work for me for at least a week with any fugumod version since then but its not that important to me. But gps is somewhat important to me.

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

tapatalked
[Galaxy S I9000 Android Development] renaud:
Did you try without angrygps?

Sent using internet connectivity
[Galaxy S I9000 Android Development] Zatta:
Something more changed between 1017 and 1032: can't connect to google servers and github (your changelog) is giving a security error in browser, both on the last one (1032).

edit: and 1017 just gave a sod. For the record.

Tapatalked u see
[Galaxy S I9000 Android Development] renaud:
You get that when you authenticate on an interface (ex, wifi) and fetch the pages with the other (ex, cell)

Sent using internet connectivity
[Galaxy S I9000 Android Development] Zatta:
Interesting, didn't know that. 1032 running again.

Tapatalked u see
[Galaxy S I9000 Android Development] mikereidis:
One of these days there will be another Katrina or 9/11 scale emergency. And smartphones won't be able to send or receive any info, unless they have FM, or digital TV etc.

I hope I can get it working soon on this kernel. But the use of a V4L FM driver and a sound driver that doesn't "understand" FM Radio paths are challenges. I can add V4L support for the first issue, but audio routing may be more difficult.
[Galaxy S I9000 Android Development] renaud:
Did you try on 1032? weather is bad here.
[Galaxy S I9000 Android Development] renaud:
The one from P7500 didn't work at first sight, but I had no tools to verify why at the moment I tried
[Galaxy S I9000 Android Development] mikereidis:
The stock CM7 kernel uses the proprietary Samsung si4709 driver, not the V4L si470x driver. It creates a /dev/radio0 device node, which I think is a bad move because that's the naming for V4L drivers. I think they should have used the same name as Samsung used: /dev/fmradio .

Yes, that's the V4L driver. I'm running FuguMod 1032n now and there still is no /dev/radio* and no /dev/fmradio .

I appreciate that your are using the V4L driver, because I'd like to support V4L. Functionality might be better with the Samsung driver though, Module support would allow a choice...

I don't see "CONFIG_RADIO_SI4709=y" in your aries_ra_defconfig file.

I'm wondering if you need to specify the I2C address somewhere. This: http://pastebin.com/HzHgu26h (board_callisto.c) has this:

#ifdef CONFIG_RADIO_SI4709

{ I2C_BOARD_INFO("Si4709",0x20>>1), },

Once we have a working FM driver, we face some issues with audio routing. The more vanilla WM8994 driver you are using doesn't have selections for FM audio routing like the Samsung one does.

And there is no /sys/devices/virtual/misc/voodoo_sound/wm8994_write I can use for writing to the registers from userspace.
[Galaxy S I9000 Android Development] strickyy:
Really dissapointed with ur kernels.. stock is much better for now, with better battery life, and working much smooter. :(
[Galaxy S I9000 Android Development] renaud:
I tried to get si4709 working but I get the same bug as the open driver. And si4709 does only compile as a module

Sent using internet connectivity
[Galaxy S I9000 Android Development] renaud:
Thanks for your constructive criticism, I think it helps many people.

Sent using internet connectivity
[Galaxy S I9000 Android Development] Chief_Death:
Yeah it is so detailed and constructive.. you better note it down nikademus.. :p
[Galaxy S I9000 Android Development] rtfpessoa:
If you just came here to say **** about the kernel it was better for you not to come....
[Galaxy S I9000 Android Development] strickyy:
Right after i unlock the device, scrolling trough home panels is choppy, after doing something for a few minutes, it becomes much smoother. Is it because of deep sleep or running on very slow clock speed when idle?
[Galaxy S I9000 Android Development] mikereidis:
Is it possible something in the kernel is still configured for the Samsung driver ?

When I do:

cat /sys/bus/i2c/devices/8-0010/*

I get:

i2c:Si4709

Si4709

...

MODALIAS=i2c:Si4709

I would have thought it would say "si470x" with an "x" at the end. Same result with 995 kernel.
[Galaxy S I9000 Android Development] zacharias.maladroit:
++

let the man work

he's hard working porting our phone to 2.6.36 kernel base

you use linux on your desktop and ever tried early RC kernels ?

then you'll know that not everything is rosy from the start
[Galaxy S I9000 Android Development] rtfpessoa:
i'm just givin more thanks to his work, the other noob appeared here to say bad things about the nikademus hard work...
[Galaxy S I9000 Android Development] renaud:
I still have some details to solve. I think I know where the slow RIL bug comes from, however, I don't have a solution yet. hint: look at the clock, it's slowly drifting and with the ril trace you can see that ril-daemon waits before commands, which explains why it's slow to establish connection since clock is drifting backwards.

That said, most kernel features are already 2.6.36 right now. You have the most useful and hard to port things, like fs, scheduler, workqueue. There is no more BKL (although on an uniprocessor phone, it's not that useful). I think you should be able to apply most of the patches you thought :)
[Galaxy S I9000 Android Development] sunra0815:
Thank you for this kernel!

The advantage from voodoo color is, that you can change the rgb and gamma settings as you want! What's the problem?
[Galaxy S I9000 Android Development] CaracalSef:
Let's say I **** up mV and before ****ing them up, I set them on boot, but then the phone won't boot because of that. What's to be done with this? :)

P.S.: I haven't ****ed it up (yet), but I have this gift...
[Galaxy S I9000 Android Development] sunra0815:
If your phone won't boot, use the kernel cleaning script and flash the kernel again.
[Galaxy S I9000 Android Development] PAGOT:
Well you could get to CWM and erase the script in init.d. Or install some kernel without UV support (some other one) and pimpy wont set it .

No idea about the cleaning script which is mentioned above without a link :)
[Galaxy S I9000 Android Development] rudeboy150:
I'd also like a link to said cleaning script i've herd about it a couple of times but near seen it
[Galaxy S I9000 Android Development] PAGOT:
Would say its this one ? http://www.multiupload.com/922KMXMMVJ

(got it from the platypus thread)

Also updating with CM7 might help with that :P (not sure though)

btw if you mess up badly, like flashing a kernel release thats not booting and no CWM (not getting past the splash, has nothing to do with UV). You can try to flash with Odin the CM7 initial kernel from the faramir page (if your download mode works ofc). Reboot right away to CWM and flash from there a working kernel :) (or full CM7 zip)
[Galaxy S I9000 Android Development] sunra0815:
Yes, I meant this one. Sorry I was posting from my Phone ...

But now you have the right downloadlink. Everyone should archive this on his internal SD-Card ;-)

It does the following:

ui_print(" Formatting cache partition ");
ui_print(" ");
delete_recursive("/cache");
ui_print(" Wiping dalvik-cache ");
ui_print(" ");
delete_recursive("/data/dalvik-cache");
ui_print(" Deleting old kernel settings files ");
ui_print(" ");
delete("/system/etc/init.d/S_volt_scheduler");
delete("/system/etc/init.d/S90scheduler");
delete("/system/etc/init.d/S99finish");
delete("/system/etc/init.d/89system_tweak");
delete("/system/etc/init.d/90screenstate_scaling");
ui_print(" Formatting cache partition for security purpose ");
delete_recursive("/cache");
ui_print(" Wiping dalvik-cache for security purpose ");
ui_print(" ");
delete_recursive("/data/dalvik-cache");
show_progress(0.300000, 0);
[Galaxy S I9000 Android Development] renaud:
I have stored it on Faramir
[Galaxy S I9000 Android Development] PAGOT:
Uh uh, voodoo haters can rejoice :P (spoiler alert)
[Galaxy S I9000 Android Development] pixiebob:
i really appreciate thanks a lot . some person like me prefer not to complicated changing rgb settings

edit: i just try r43n but color aren't exactly same cm7.little less brilliant.try and compare you will see
[Galaxy S I9000 Android Development] rudeboy150:
Thanks so much ill be storing that for safety cheers guys
[Galaxy S I9000 Android Development] Christophe86:
hi nikademus,

thanks for developing a custom kernel for CM7. been using your kernels quite some time now, and i have to say that they are overall very good regarding speed, smoothness and features.

I'm - back - on CM7 now for a week or two and decided to give your cm7 kernel a go - version r43v

my preliminary thoughts..

- 3D performance is great, it's a lot better than std cm7 kernel - don't know why std cm7 kernel's 3d performance is so bad, but the difference is quite big.

- sd performance, especially write speed, is quite low.. i'm using antutu benchmark tot test this and i'm getting most of the time between 2 and 3 MB/sec whereas this was 8 MB/sec on zacharias his cm7/miui kernels. otherwise, read speed is okay! (10MB/sec)

generally this is already a pretty good kernel and i'm looking forward to future versions :)
[Galaxy S I9000 Android Development] jornbjorn:
lets say u use nenamark to test 3d performance... it does not like ondemand governor...
[Galaxy S I9000 Android Development] sptorrent:
Battery

Just to let you know (in case anyone is interested!):

Best battery performance so far with CM7:

nightly #24 / CM7_FuguMod_20110610_r43_update.zip with no UV (only because I can't find a stable UV - I must be dumb...).

After 14 hours of light usage, I'm still left with 60% of battery charge. It may not be much for some of you, but for me, it's at least as good as stock GB.

Thanks very much!
[Galaxy S I9000 Android Development] PAGOT:
Well go -50 on everything? (except 600) If that wont work (but it should) go with -25 on everything :)

My stable is in my signature :) (some guys here wrote pretty decent stuffs about the UV read it up )

Also am confirming the awesome battery life. It literally doubled from the time I flashed CM the first time :)
[Galaxy S I9000 Android Development] maisi:
-300mV on 100Mhz , and it's really stable ? Lucky you , I guess you have one of the best chips out there ;-)

Max stable I can go with the current kernel is : -200,-175,-150,-150,-100,-75.
[Galaxy S I9000 Android Development] PAGOT:
You are then the luckier one :) -75 and -100 I can never go.

And I am writing again. 600 is not used, its no use to set anything to it ....

Also the -300 is set, but not accepted :) . Its just for the future when nikademus allows it. Its on the max the pimp my cpu allows (or kernel) dont mind the -300 :) (had even -950 there :P)
[Galaxy S I9000 Android Development] PAGOT:
Man love how you handled this and what you do for us, making 2 builds :) etc

but wouldn't be me to point this out.

ehm what?

how much would you consider a winner or clear winner?

Just admit you like to do this for the community and try to please all if you can :)

and dont make up silly excuses :p
[Galaxy S I9000 Android Development] maisi:
Well the phone is usually more in idle than on load so IMO 100 Mhz matters the most ;)

Your right, it's not used , never noticed that , I just set it to the value I had on other kernels ;-)

Oh ok , well -250 is good too and should really help with battery life :-)

Testing -250 , -200 now :D
[Galaxy S I9000 Android Development] toddmworth:
I would like to know the correct tools for testing performance of this kernel, any advice?
[Galaxy S I9000 Android Development] ArctiX:
Updated from 995 to 1033 and on nearly every boot up the modem crashes, my imei is unknown, no signal, etc. Additionally, the time and date can't synchronize automatically and resets with every reboot. Running JVR modem. Tried running kernel cleaning script and reinstall but it didn't change anything. When reverted back to 995 everything is working ok.
[Galaxy S I9000 Android Development] renaud:
As I explained formerly, I am actively searching for this bug. You modem will work fine if you wait a little bit. However, clock is drifting.
[Galaxy S I9000 Android Development] FadeFx:
No, and as i will most likely need spirit-fm support at least for a while now, i wont, as i am forced to stock, however, i will come back to fugumod asap for some benefits like voodoo color and lower min brightness. I hate to light the whole bedroom when reading something in the evening.

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

tapatalked
[Galaxy S I9000 Android Development] encho:
Screenfilter is your friend.
[Galaxy S I9000 Android Development] FadeFx:
I know it, but i don't like it.

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

tapatalked
[Galaxy S I9000 Android Development] zacharias.maladroit:
thanks nika !

I'll start to apply the patches and see how it goes

hopefully the issues with e.g. RIL can be solved

btw: I seemingly also got them (not sure if it's the same)

when the phone starts up in airplane mode and airplane mode is toggled off

it takes significantly longer for the phone to acquire the network (at least from the name it displays):

it shows "sos calls only" / "sos"

afaik when toggling airplane mode again - waiting a few moments and deactivating it should go a little faster

yeah, it's great e.g. for reading longer passages of text

but when watching movies, pictures, etc. the colors definitely look more blurred and steplike

so not really recommended for general usage
[Galaxy S I9000 Android Development] renaud:
I must admit that I have flashed #95, so I decided to test CM7 stock kernel a little bit to see what was that better.

And I was really surprised, compared to 1036.

With stock CM7, OCed to 1200mhz, I get about the same or lower quadrant scores (FuguMod being of course at 1Ghz), which is something I don't really understand :confused: . If someone else can confirm, this would be very nice.

3D has really heavy lags from time to time

color is really bad blue looking, but that's a matter of choice

battery drained quite a lot while I ran the tests, but that may be because it was at 100%, as generally first percents go very fast.

the UI was quite slow to respond, but that may be touchscreen settings
[Galaxy S I9000 Android Development] Zatta:
I have flashed 1038v and 1041v this morning:

On 1038v wifi functionality got lost on build #95, giving some error. Don't know what the reason was for this but reverting to 991 fixed it.

Then 1041v didn't boot at all (flashed simultaniously with build #96) so hiemdalled back to 964 (wich was still in the heimdall folder on the notebook) and wifi didn't work either (that is why I think I have maybe missed something or had a bad flashing back to 991 previously).
[Galaxy S I9000 Android Development] master0z:
One question nikademus: What is fixed on 1036? I have read the changelog, but I don't understand that you have fixed.

Thanks
[Galaxy S I9000 Android Development] renaud:
Clock drifts less, but still does a little bit
[Galaxy S I9000 Android Development] renaud:
If you flash through heimdall, you only flash the kernel itself, not the wifi modules. Just flash again any other version and wifi will work again.
[Galaxy S I9000 Android Development] FadeFx:
Nika, would your wifi modules work on stock cm7 kernel? And if yes, can you pm me a link to them?

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

tapatalked
[Galaxy S I9000 Android Development] renaud:
No, they will not work, they are not for the same kernel version. This is particularly true with kernels > r1000
[Galaxy S I9000 Android Development] master0z:
Nikademus, I think that you can put in the first post the possible kernel bugs, and if you fix definitely the bug, you can erase it!

It's only an idea ;)!
[Galaxy S I9000 Android Development] renaud:
OK, I have added some lines
[Galaxy S I9000 Android Development] renaud:
That doesn't seem to be the same thing at all. Try to do a strace of rild.
[Galaxy S I9000 Android Development] master0z:
The autoilumination is working now? I'm already on 995v because I think that is a very nice build.

Thanks!
[Galaxy S I9000 Android Development] FadeFx:
Ok, so if i take lets say 938 and extract the modules i could use them on stock kernel? Because the disconnects are annoying there, i prefere not to have Chanel 13,14 instead...

Edit: just tested, didn't work...

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

tapatalked
[Galaxy S I9000 Android Development] master0z:
Nika, the 1036 doesn't ask me the number pin, and I don't have signal...

I have to come back to the 995... Do you know something about it?
[Galaxy S I9000 Android Development] renaud:
yes, this is due to the clock drift, if you wait it will come
[Galaxy S I9000 Android Development] master0z:
OK, Thanks!!!!
[Galaxy S I9000 Android Development] sptorrent:
Some feed back on backlight:

Using GPS status we can see the "Lux" sensor value. I think the problem of backlight not adjusting fast enough may come from the light sensor.

The lux number takes ages to adjust: I put my hand over the captor on the top of the device and, after several seconds, the value eventually changes. So I guess that's why the backlight doesn't respond either. (doing the same on samy's ROM works instantly)

I hope it helps you a bit ...

Kernel 1051
[Galaxy S I9000 Android Development] rtfpessoa:
JUST REPORTING, NOT COMPLAINING

Version 1068 is having some problems to boot in my sgs...

After install, before boot I think the device rebooted twice and some other strange stuff but after all that he booted and instantly asked for the PIN...
[Galaxy S I9000 Android Development] renaud:
thanks, great report. clock should be fixed in that one but I had no time to check

Sent using internet connectivity
[Galaxy S I9000 Android Development] rtfpessoa:
got one strange reboot...

Some instability in this last one...

going to keep testing...
[Galaxy S I9000 Android Development] Zatta:
had this strange booting after flashing as well but not after an 'empty' reboot (I actually needed to try this since I hardly ever reboot without flashing something :)

Network picked up before the usual launcherpro fc, nice work!

Edit: just had a spontaneous reboot. After this it took about 45 seconds to pick up network. 10 for the wifi, to compare.

Tapatalked u see
[Galaxy S I9000 Android Development] renaud:
I haven't got 1068 to run stable at all.

I tested all versions and frequency breaks at 1014 and ril at 1017. so latest ultimately stable is 1006.

but this will help to correct problems

Sent using internet connectivity
[Galaxy S I9000 Android Development] renaud:
I reverted all commits to go back to 1006. 1006<releases<1068 are in either testing or experimental folders.

This will allow me to move slower to the same goal.
[Galaxy S I9000 Android Development] Zatta:
I already wondered why my bookmark "fugu test" gave error 404 on my browser :)
[Galaxy S I9000 Android Development] renaud:
it's experimental now since testing it's for those who have proven to work but with bugs

Sent using internet connectivity
[Galaxy S I9000 Android Development] Chief_Death:
So since #1080 is not on the test/experimental folders does it mean it is 'safe' ? :p
[Galaxy S I9000 Android Development] renaud:
yes I am running it for a few hours

Sent using internet connectivity
[Galaxy S I9000 Android Development] Chief_Death:
Thanks for the answer already flashed no problems at all :))
[Galaxy S I9000 Android Development] Zatta:
r1086v up and running, feels good. 82v was not a real 'v' and without wifi. 72 gave some reboots, no idea why. All on build #96.

Oh, good morning btw.

Edit: But.. Picked up an 1000 mhz lock on 1086v, reverted for the time being to 1006v.

Tapatalked u see
[Galaxy S I9000 Android Development] renaud:
r1080 is the most current stable. I reorganized the folder to be clearer.
[Galaxy S I9000 Android Development] renaud:
There is now an automatically generated front page to help people choosing :)
[Galaxy S I9000 Android Development] kimlindo:
I upgraded from 995 to 1080 a couple of hours ago and everything feels super smooth! The battery seems to be draining similar to r995, so I should be able to get a day or two out of it with minor use. :)

Edit: on nightly 96. :p

Sent from my Galaxy S
[Galaxy S I9000 Android Development] master0z:
Is fixed the problem with the clock in a 1083???