yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] woeds:
Seems like it's already further along than CM6.1 :) Awesome work.

Could you shine some light on what the fb-problem is? Or is that too difficult? Isn't the graphicshardware equal to the Nexus S?
[Galaxy S I9000 Android Development] ashwinds:
Great to hear that. I used to use CM6.1B3 as my daily driver - maybe I will go back to it for nostalgia while we wait for a GB release :D
[Galaxy S I9000 Android Development] benoitb85:
To compare, stock JPU with Voodoo module (still stock Kernel) is:

Flower Power: 22.20 fps

Ninja's Garden: 15.86 fps

Emperor's new clothes: 43.18 fps

Magic Island: 30.42 fps

TOTAL SCORE: 24168
[Galaxy S I9000 Android Development] zacharias.maladroit:
I know this might sound lame but if you guys tried to fix it for some time now

you thought about asking google devs ?

if they won't help - it's also fine but at least you tried and when you're lucky the problem could be fixed in no time :)
[Galaxy S I9000 Android Development] dani31:
I believe the hardware drivers are done by Samsung not by Google, even for Nexus S, and they will laugh in your face if you ask them.

After all, Hummingbird is their child.

Probably the worst case scenario is that we have to wait until Smasungs releases Gingerbread officially.
[Galaxy S I9000 Android Development] codeworkx:
Most of the commits at github are done by samsung devs. So i would say samsung did the most driver stuff. Userspace libs for graphics are closed source. That's our problem.
[Galaxy S I9000 Android Development] leoon:
1. what does WiFi sleep do?

2. what is framebuffer and what it affects?
[Galaxy S I9000 Android Development] jaju123:
This might seem like a stupid question but can't you just ask the samsung open source center? They usually at least respond with some kind of answer whether they release it or not.
[Galaxy S I9000 Android Development] Arkanius:
I was under the idea that Google had written a open sourced video driver for the Nexus S. The hardware is the same... Couldn't you take a peek?
[Galaxy S I9000 Android Development] codeworkx:
If wifi wants to sleep, whole phone goes to sleep. ;-)

It crashes completely.

Framebuffer: google for it http://tldp.org/HOWTO/Framebuffer-HOWTO/

Userspace libs for graphics on Nexus S are closed source! RIL, too!

No chance!
[Galaxy S I9000 Android Development] loermansa:
Puts the Wifi hardware to sleep if it is not needed (e.g. you can configure SGS to let WiFi sleep when display is off, saves battery)

If it can be compared to a regular computer (which I'm pretty sure it can) it is what drives the display. It is split into a driver that is inside the kernel (kernel space) that drives the underlying hardware and a userspace library which allows applications to talk to this driver. The last part is apparently tricky... Correct me if I'm wrong though, wouldn't be the first time :)

Arjan
[Galaxy S I9000 Android Development] wsyx:
thanks for your work.how about the sensors now?
[Galaxy S I9000 Android Development] woeds:
Is it a matter of not wanting to use them because they're closed source, or aren't the libs compatible with the Galaxy S?
[Galaxy S I9000 Android Development] codeworkx:
we're using them. but if the graphics errors are caused by this libs, we'll have a very big problem because of the missing source code.
[Galaxy S I9000 Android Development] jscurtu:
Yeah.. that would suck!

Are you using the libs from nexus or galaxy?

Reminds me of the damn poulsbo from intel with integraded SGX..
[Galaxy S I9000 Android Development] xero2002:
I know they'll probably laugh at me but I still sent them a msg to make source code available for graphics and RIL.
[Galaxy S I9000 Android Development] cesierra:
that's how a leak can happen, oops
[Galaxy S I9000 Android Development] jeebspawnshop:
Haha, true.
[Galaxy S I9000 Android Development] jscurtu:
They wont laugh... They (samsung or google) just wont be able to help as it is IP from Imagination Technologie Inc. And they wont allow opensource through thier licensing! Many already tried!!

Google for "intel poulsbo GMA 500"
[Galaxy S I9000 Android Development] codeworkx:
nexus libs.

if we use galaxy libs, we're forced to use .32 kernel.
[Galaxy S I9000 Android Development] dehem333:
So this means we are screwed? or can some legend fix it?

What features will not work with this problem?

:confused:
[Galaxy S I9000 Android Development] codeworkx:
with galaxy libs same problems as on cm 6.1.

just give us some time.
[Galaxy S I9000 Android Development] cocchiararo:
as far as i understand, either they fix it (with some black magic :P, or reverse engeniering maybe ?) or when 2.3 comes out for the sgs the new libs might work...
[Galaxy S I9000 Android Development] leoon:
That means after 4 months :(
[Galaxy S I9000 Android Development] codeworkx:
vote for black magic
[Galaxy S I9000 Android Development] Waza_Be:
That seem obvious that you will have exactly the same issues than CM 6.1...

I guess that the source code of android has no major changes (2.2 vs 2.3) and the issues you are facing are quite the same than CM6.1, right?
[Galaxy S I9000 Android Development] d2loader:
as I remembered, the CM6.1 on SGS have a lot problem with ALSA. But now CM7 has fully working sound, so just give the developers more time.
[Galaxy S I9000 Android Development] cocchiararo:
your post and this commit made me laugh xD

@CMSGSTeam: [android] http://bit.ly/foQ9e8 Daniel Hillenbrand - added black magic
[Galaxy S I9000 Android Development] codeworkx:
yes, got fully working audio. but no sensors at all.

would say "same ****, slightly different"
[Galaxy S I9000 Android Development] MiG-:
Why? Why oh why are the libs tied to a Kernel version? Bad bad design, IMO.

:mad:
[Galaxy S I9000 Android Development] meisterlampe2000:
So let the black magic bring some light to the repo ;)

nice one codeworkx,wish u good luck!
[Galaxy S I9000 Android Development] zacharias.maladroit:
might be due to API and other changes in the kernel that it won't work

probably the libs are something like the /lib/modules directory for the linux-kernel

it might not be a big change like that but:

compare it to going from xp to windows vista and try installing nvidia oder ati drivers

the drivers most probably will NOT work

so it's the same with these

@back on topic:

*crosses fingers and toes* that Samsung replies and lends a helping hand to get it working :)

I hope more and more devs/people all over the world (including the Galaxy Tab devs) will collaborate to get this working ASAP
[Galaxy S I9000 Android Development] jscurtu:
No.. "proprietary" is the bad desing!

The proprietary userspace libs are tied to the opensource SGX ddx kernel modules! They are compiled to that particular kernel..

No source == no fix
[Galaxy S I9000 Android Development] kouryu:
yes i backup it,like efs.img,but how flash it to new partitions?

and i use your black magic :D

build a new otapackage,

in updater-script

show_progress(0.200000, 10);

assert(package_extract_file("zImage", "/tmp/zImage"),

write_raw_image("/tmp/zImage", "boot"),

delete("/tmp/zImage"));

show_progress(0.100000, 0);

not work for me, must use bmlwrite?

btw:

use paypay first time, it says Confirmation number: 7FV16796VM322282A ,idon't know if it success

sorry i can't donate any more this time:D
[Galaxy S I9000 Android Development] codeworkx:
You've made a efs.img using dd? So it's a rfs image now.

You cannot restore a rfs image to a mtd partition. ;-)

Use "cp" to copy contents of efs to your internal sdcard and simply copy it back to the new efs partition on mtd.

You've to flash the new kernel using odin. after this you can try using otapackage. but it's still untested. may cause a thermonuclear war. i've never tried it.
[Galaxy S I9000 Android Development] ashwinds:
If it could cause a thermonuclear war, request you to release an Alpha so that we get to try CM7/GB before we all get nuked :D

PS: that was just an ignorable opportunistic plea - I know you release when you are ready for the deluge of "should I rename this to update.zip" comments :P
[Galaxy S I9000 Android Development] lightning18:
How about the modem? Is modem.bin in rfs also?
[Galaxy S I9000 Android Development] kouryu:
i copy rfs files to efs

in my phone /efs files as:

.imei

.nv2.bak

,nv2.bak.md5

.nv_data.bak

.nv_data.bak.md5

.nv_state

mv_data.bin

nv_data.bin.md5

.android/ (nothing)

imei/.nvmac.info

imei/bt.txt

mps_code.dat

no servers too~

new kernel? where? i just build zImage from coolya's, 3.9MB.

somethings wrong?
[Galaxy S I9000 Android Development] lightning18:
Latest kernel from coolya's github is about 12 hours ago.

How's the modem problem that you have?
[Galaxy S I9000 Android Development] kouryu:
maybe,but i can't modem?

~ # mount

mount

rootfs on / type rootfs (rw)

tmpfs on /dev type tmpfs (rw,relatime,mode=755)

devpts on /dev/pts type devpts (rw,relatime,mode=600)

proc on /proc type proc (rw,relatime)

sysfs on /sys type sysfs (rw,relatime)

none on /acct type cgroup (rw,relatime,cpuacct)

tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)

tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)

none on /dev/cpuctl type cgroup (rw,relatime,cpu)

/dev/block/mtdblock2 on /system type yaffs2 (rw,relatime)

/dev/block/mtdblock3 on /cache type yaffs2 (rw,relatime)

/dev/block/mmcblk0p2 on /data type ext4 (rw,nosuid,nodev,noatime,nodiratime,barr

ier=1,data=ordered,noauto_da_alloc)

/dev/block/mtdblock6 on /datadata type yaffs2 (rw,relatime)

/dev/block/mtdblock4 on /efs type yaffs2 (rw,relatime)

/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,relatime)

~ #

cat /proc/mtd

dev: size erasesize name

mtd0: 00780000 00040000 "kernel"

mtd1: 00780000 00040000 "recovery"

mtd2: 0bb80000 00040000 "system"

mtd3: 05000000 00040000 "cache"

mtd4: 00c80000 00040000 "efs"

mtd5: 00d80000 00040000 "modem"

mtd6: 0ac00000 00040000 "userdata"

~ #

how to flash modem.bin to mtd5 ? use bmlwrite?
[Galaxy S I9000 Android Development] lightning18:
I've tried to flash_image modem ...../modem.bin

The Baseband still shows "Unknown".
[Galaxy S I9000 Android Development] codeworkx:
bml is gone away! we've transformed your galaxy s into a nexus s.

btw. i had problems to revert back to a "normal" rom.

you shouldn't play with this stuff. it's not ready.

dd if=modem.bin of=/dev/block/mtdblock5

^^ last info for now. no more help from us until it's released.

I've no passion to fix a lot of semi-bricked phones because some unexperienced users played with stuff they don't understand.
[Galaxy S I9000 Android Development] kouryu:
me too,

and can't find sdcard
[Galaxy S I9000 Android Development] :
STOP USING THE ROM / KERNEL IF YOU DON'T KNOW WHAT YOU ARE DOING!

If you don't know what MTD is: Don't use it

If you dont' know how to use mtd utilities: Don't use it

If you can't read kernel source to see what is going on your phone: Don't use it

If you want to use your phone for long term:Don't use it

If you don't have a spare phone:Don't use it

This kernel is under heavy development, there are no long term experiences with MTD and YAFFS on the oneNAND this Kernel might kill your phone even month after you used it!

This Kernel can surly brick your phone or components of it. Some might show instant other might hit you long time later. We can give you absolutely no guarantee that this Software won't damage hardware! Just because no one reported issus to this point this doesn't mean there are non. Some Drivers are not finished so we can't tell you if the hardware is working in anyway or got bricked by the kernel. Don't expect the kernel to be stable just because it doesn't kill hardware at a certain point in time, later changes in the kernel might kill it.

This is totally experimental, if the SGS is your main phone and you can't afford a spare phone or can't accept that your SGS might got totally bricked: Don't use it
[Galaxy S I9000 Android Development] kouryu:
Codeworkxyou are my hero,i get my phone works on 3g now :D

Sdcard doesn't work
[Galaxy S I9000 Android Development] codeworkx:
sdcard doesn't work out of the box, but with a few commands it will work. but only one of them. two cards are still not supported.

please read coolya's post above.
[Galaxy S I9000 Android Development] kouryu:
i read it,i'd just to know how:D

and then i return CM6

I know how to get sdcard ;)

just mount it,and it work now
[Galaxy S I9000 Android Development] xero2002:
As expected...
[Galaxy S I9000 Android Development] ikenley:
It was a somewhat sincere response. What about doing it the other way and showing them the code the Dev team currently have for RIL and Graphics and see if they can help?

We might prick the interest of a Samsung Dev who might like the project.

I know it's unlikely, but I think Samsung owes it to us.
[Galaxy S I9000 Android Development] codeworkx:
We've no code for ril and graphics. You need mass datasheets, knowledge and a lot of time we don't have. It's not as easy as you think.
[Galaxy S I9000 Android Development] ikenley:
I appreciate the response Codeworkx.

Sorry for the interruptions, unfortunately I know nothing of the coding behind Android, just tend to get a bit idealistic at times.

I will continue to help in the only way I can...

...random donations!

Do we have a Witch Doctor in the forums that can help with the Black Magic?
[Galaxy S I9000 Android Development] woeds:
Have you tried asking swetland? As a Nexus S kernel-dev, he might be more familiar with the libs. I know it's a different situation here because of the SGS hardware, but you never know.
[Galaxy S I9000 Android Development] mickeko:
Somewhat sincere? Really? What would have been more sincere than that? Ignoring the being friendly tone? :)
[Galaxy S I9000 Android Development] mickeko:
Proprietary means that someone else has the rights to the code being used. It would be extremely counterproductive to even ask him to consider doing anything that might get him fired and in worst case sued on top of that.
[Galaxy S I9000 Android Development] kouryu:
thanks for your work;)

i'd back to cm6,wait for you

:rolleyes:
[Galaxy S I9000 Android Development] codeworkx:
We're trying to get it usable as fast as we can to make you happy.

We won't release anything unstable which has the possibility to destroy your phones or make you unhappy.

So please be patient and give us the time we need.

Coolya and i have full-time jobs and we're developing in our free time. So we cannot work on cm7 the whole day.

If someone comes in here and will say: "Hey guys, i'll pay you for developing on cm7 the whole day" <- feel free to contact us. ;-)

If we got something usefull and stable, it will be instant out for download.
[Galaxy S I9000 Android Development] woeds:
I wasn't suggesting he gives them the sources ;) but he might be able to steer them in the right direction with the framebuffer problems. I can recall supercurio having framebuffer issues when he first tried to boot the Nexus S system dump on the SGS, and swetland then gave him some pointers to help out.
[Galaxy S I9000 Android Development] Guiper:
Just to add my warnings and fast comments after using the rom for a few days, trying to help on what I can Coolya and Codeworkx.

Once again, if you don't know what you are doing, just don't flash it. It may be hard to go back to Samsung Roms, even after repartition with Odin, and nobody will be able to help you on it!!

Regarding the current status, I would like to add also that I have some strange WiFi issues, cannot turn on WiFi if bluetooth is not enabled, and battery life is not yet as good as on Samsung roms. I have 67% after 8:38h on 2g on gmail and exchange sync and 2 calls and 1 email (no other usage).

The rest you can read on Codeworkx replies.

If you cannot help with coding, give some extra support, buying them some beers or pizza. I'm quite sure it helps to keep them motivated :)
[Galaxy S I9000 Android Development] gbohm:
Tryed to find the post perhaps it has been discuessed before what about flasing it on a extern sd And just mount the extern one .... Is it possible? It was done for quite a lot devices and there it runs good enough

Would love to help coding but i think obj-c,c++ delphi java or sql wont help....
[Galaxy S I9000 Android Development] codeworkx:
C, C++ and Java are needed
[Galaxy S I9000 Android Development] gbohm:
Cool what can i do i am from db development but i think if i look into it i could help

I will write u a pm with my gmail
[Galaxy S I9000 Android Development] amir_rafie:
Hi Supercurio,

When do you think the next version is being ready?
[Galaxy S I9000 Android Development] Hanness:
Are u serious ?
[Galaxy S I9000 Android Development] kUdtiHaEX:
1 month, maybe more, that is for sure.
[Galaxy S I9000 Android Development] gbohm:
Like allways...when it is ready !

Don't stress a developer.....
[Galaxy S I9000 Android Development] SquirtingCherry:
I think supercurio is not working on the port anymore, as i can read on twitter he's working on the voodoo sound project.
[Galaxy S I9000 Android Development] nucleic acid:
[OFF TOPIC] Gingerbread 2.4 leaked

[OFF TOPIC] Gingerbread 2.4 leaked:

info> Android 2.4 leaks on an XPERIA Arc prototype, is still Gingerbread

info (dutch) > CES: Hands on Android 2.4, Gingerbread reloaded

hmm...maybe this will get him started again!? ;)
[Galaxy S I9000 Android Development] lightenup:
@wifi sleep problems:

how to enter wifi sleep? I tried setting the policy in the GUI but it doesn't seem to have an effect (and it didn't crash yet).

--edit: ah - just got it :)

[ 2240.897498] dhd_dev_reset: WLAN OFF DONE
[ 2240.899293] wifi_set_power = 0
[ 2240.900083] sdhci_s3c_force_presence_change : Enter
[ 2240.900787] =========== WLAN placed in RESET ========
[ 2240.985760] kernel BUG at drivers/mmc/core/sdio_io.c:29!
[ 2240.986532] Unable to handle kernel NULL pointer dereference at virtual address 00000000
[...]
[Galaxy S I9000 Android Development] Bara2:
That's strange - kernel version is 2.6.32 which is the kernel used for froyo. Gingerbread kernel is numbered 2.6.35 i I'm not wrong...
[Galaxy S I9000 Android Development] Guiper:
The default timeout for wifi is 15 minutes. You need to wait this time to get the kernel panic.

I'm trying to solve it for 3 days, without much success. Any comments or suggestions are welcome.I would say it's some GPIO missing configuration, but everything looks quite ok.

I'm willing to pay 15$ for any clue that lead me to the problem and potential fix :)
[Galaxy S I9000 Android Development] comdei:
Just wondering is this port still around?

It looks promising, a ton of community support and lot of dev support.
[Galaxy S I9000 Android Development] 0utkast:
Thanks for the update. Was starting to wonder what kept them up.

Patiently waiting =D
[Galaxy S I9000 Android Development] adchevrier:
maybe I'm off topic, but wouldn't this be helpful for devs when it arrives ?

www phoronix com/scan.php?page=news_item&px=ODk4Ng
[Galaxy S I9000 Android Development] mr_at_sgs:
heho, this sounds good. http://www.phoronix.com/scan.php?page=news_item&px=ODk4Ng
[Galaxy S I9000 Android Development] codeworkx:
"closed-source user-space bits" are our main problem.
[Galaxy S I9000 Android Development] donharden2002:
You guys working on this are very special people. I myself would have blown a gasket by now with all of this going on.

We should all be thankful that you guys love the challenge of trying to do things that even samsung or att can't do. You have given me froyo on my captivate which att can't do.

I appreciate your hard work and hope you guys are getting enough rest and family time while doing this.

Best of luck to you all on this. Hopefully for your own satisfaction you are able to make this work. After all the hours spent it's the least you deserve.
[Galaxy S I9000 Android Development] lightenup:
What does this '' sdhci_s3c_force_presence_change'' do and why is it required in the wlan_power_en function? (compared to nexus s, this is not needed)

btw codeworkx, you missed a bit in your latest commit to android_kernel_samsung:

diff --git a/arch/arm/mach-s5pv210/Kconfig b/arch/arm/mach-s5pv210/Kconfig
index 6e8150f..7fc2246 100644
--- a/arch/arm/mach-s5pv210/Kconfig
+++ b/arch/arm/mach-s5pv210/Kconfig
@@ -149,8 +149,7 @@ config MACH_ARIES
select ARCH_HAS_CPUFREQ
select S3C_DEV_HSMMC
select S3C_DEV_HSMMC1 if !S5PV210_SD_CH0_8BIT
- select S3C_DEV_HSMMC2 if !S5PV210_SD_CH2_8BIT
- select S3C_DEV_HSMMC3 if !S5PV210_SD_CH2_8BIT
+ select S3C_DEV_HSMMC2 if !S5PV210_SD_CH2_8BIT
select S5PV210_SETUP_SDHCI
select S5PV210_POWER_DOMAIN
help

after this it looks very good:

<7>[ 220.754402] s3cfb_early_suspend is called
<7>[ 220.754621] s3cfb s3cfb: global display is off
<7>[ 220.765221] save exit: isCheckpointed 1
<7>[ 220.774404] save exit: isCheckpointed 0
<7>[ 221.270315] save exit: isCheckpointed 0

<5>[ 1120.650740] init: service 'dhcpcd' is being killed
<6>[ 1120.687442] init: waitpid returned pid 571, status = 00000100
<5>[ 1120.687624] init: process 'dhcpcd', pid 571 exited
<4>[ 1121.706523] dhd_dev_reset: WLAN OFF DONE
<4>[ 1121.708468] wifi_set_power = 0
<4>[ 1121.709704] =========== WLAN placed in RESET ========
<6>[ 1122.140510] max8998_int_work_func : pmic interrupt
<6>[ 1122.154691] s3c_cable_status_update : battery status discharging : 1

Seems like the NULL pointer dereference was caused by the wrong S3C_DEV_HSMMC3 switch. I also discovered the wrong usage of the hsmmc platform data handle (s3c_device_hsmmc3), but had still crashes. So good work codeworkx!
[Galaxy S I9000 Android Development] Jeshter2000:
"@CMSGSTeam: [android_kernel_samsung] http://bit.ly/ghwN1r Daniel Hillenbrand - mach aries: removed mmc rescan, fixes wifi sleep"
[Galaxy S I9000 Android Development] leoon:
awesome!

if im not wrong, the "only" other big issue that is left is the framebuffer
[Galaxy S I9000 Android Development] s44:
This seems to be the change suggested by the post above it. Nice job, mysterious poster. ;)
[Galaxy S I9000 Android Development] lightenup:
Mmm .. just for reference:

It seems that this mmc rescan is really bad (somehow a NULL pointer is dereferenced in sdio_release_irq): I just questioned it's presence because it's not in the Nexus S source and my phone didn't behave much different without it. Not until I removed the S3C_DEV_HSMMC3 (see codeworkx commit + my patch) wifi sleep started to work crash free.

Anyway, that's been probably one of our smallest and most easiest problems to "fix" - and it's still too early to call this fixed, but for all I can say, my phone runs without crashes for about 12 hours now.
[Galaxy S I9000 Android Development] codeworkx:
It's fixed. ;-)

Whats left?

- second sdcard

- magnetic, orientation sensors

- graphics

- RIL polling problem

- 2G toggle doesn't work if 3G is available and in use. after disabling data, it's possible.

- camera

- make otapackage

- boot.img

Still much to do.
[Galaxy S I9000 Android Development] Putzy:
You say there is a lot, but you've already covered a lot. In terms of a to-do list, you must have knocked the vast majority off. ;)

Still, great to see progress on this. Can't wait to ditch all the 'custom' roms and finally get to see a proper AOSP base. :)
[Galaxy S I9000 Android Development] dehem333:
You can make your own conclusion , BUT this remaining stuff will not be easy to fix , and willl take alot of time no matter how many people work on it.

Anyway , thanks codeworkx for the information. Me and I know many others do always appreciate information like this , I wish you(and all others) best of luck.
[Galaxy S I9000 Android Development] Chad_Petree:
Im afraid youre right, i think this might be ready for an alpha in mid february :( , at least im almost certain that gingerbread will stick for sometime, honeycomb wont be released for android smartphones, maybe icecream will be used for both phones and tablets , until then well have to settle for gingerbread, this gives quite some time for the port to be finished and fully functional
[Galaxy S I9000 Android Development] TechTony13:
I find it hard to believe that Google would up and abandon the smart phone market that they have begun to so successfully penetrate. It wouldn't surprise me to see honeycomb stay only with tablets, but 2.4 is certainly coming. And we can't stay in 2.x forever.

Sent via XDA App on my CM Captivate.