Database Info

[ROM] AOSP Mesmerize Vanilla Froyo ALPHA 0.1

I have finally, successfully, gotten jt1134's device tree and Froyo framework all configured for the Mesmerize. This is a Vanilla Froyo (no Cyanogenmod) build and works enough to play around with (= But, I should warn you, this isn't a terribly stable build, so don't freak out if something acts weird d= Also, I'm not responsible for any harm you may do to your devices..
It's late and I have an 8:00 am tomorrow so I haven't tested everything out yet, but what is working and not working should be similar to what jt1134 has listed over in his Fascinate thread. Here's what I've tried though:
Working:
Phone
SMS
GPS
WiFi
Not Working:
Data?
Bluetooth
Camera
sdcard?
Oh, and it may randomly 'boot loop' a few times.. don't freak out though.
For this to work you need to be using the Mesmerize Froyo kernel I recently posted. To get everything setup just download the ROM and the Kernel and put them on your sdcard. Boot into recovery and make a backup. Wipe your data and cache partition. Flash the ROM. Flash the Kernel. Reboot. Froyo! If you're going to try to adopt this ROM for everyday use (good luck), make sure you grab the GApps package and flash that last.
I haven't got a Mesmerize device tree on github yet, but you can find the alterations to the kernel up. Really, you should look at jt's source/github because that's where all the dirty work is done (= Also, some of his work is under ModADroid on github.
Download Links:
Mesmerize Vanilla Froyo ROM: http://dl.dropbox.com/u/464066/Mesmerize/ROMs/froyo_mesmerize_0122.zip
Mesmerize Froyo Voodoo Kernel: http://dl.dropbox.com/u/464066/Mesmerize/Kernels/0123_mesmerize_voodoo5.zip
I'll post a link to a nonvoodoo kernel when I get one compiled.
Froyo GApps: http://goo-inside.me/google-apps/gapps-hdpi-20101114-signed.zip
Be careful!! This kernel is named the same as jt's Voodoo Sound 2.1 Kernel that he released yesterday. You may want to rename one of the two if you plan on using both. The ROM will bootloop or freeze at the lockscreen if you mistakenly use a 2.1 kernel (=
Source:
http://github.com/jt1134
http://github.com/dcow
Credits:
jt1134 <-- for all the SCH-I500 framework work
punk-kaos <-- for his contributions to the SCH-I500 framework
phidelt82 <-- for keeping me company late at night (not like that.. ..) and for letting me bounce ideas off of him, calling me out when I'm being stupid, and flashing whatever I throw at him (=
Enjoy!

Let me be the first! Thank you so much this should hold me over until official release comes out.. Maybe even then lol, thanks again.
Sent from my SCH-I500 using XDA App

cpfeifer said:
Let me be the first! Thank you so much this should hold me over until official release comes out.. Maybe even then lol, thanks again.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Perhaps if we get a to a final release or beta then. I don't think you'll be wanting to employ this for everyday use until we get more issues fixed.

cpfeifer said:
Let me be the first! Thank you so much this should hold me over until official release comes out.. Maybe even then lol, thanks again.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
dcow90 said:
Perhaps if we get a to a final release or beta then. I don't think you'll be wanting to employ this for everyday use until we get more issues fixed.
Click to expand...
Click to collapse
It was definitely fun to play with, but yeah, as for everyday use, there is still work to do. Hopefully soon though. I know I'll be digging in some more tonight to see if I can find anything fixes.

be glad to help test things once you get a little bit more stable with this.
Sent from my SCH-I500 using Tapatalk

phidelt82 said:
It was definitely fun to play with, but yeah, as for everyday use, there is still work to do. Hopefully soon though. I know I'll be digging in some more tonight to see if I can find anything fixes.
Click to expand...
Click to collapse
The sdcard issue is just a problem with the init.rc I think.. but we'll see whats still not working after I get jt's latest source built and we can work from there.
Sent from my USCC SCH-I500..

dcow90 said:
The sdcard issue is just a problem with the init.rc I think.. but we'll see whats still not working after I get jt's latest source built and we can work from there.
Sent from my USCC SCH-I500..
Click to expand...
Click to collapse
I think it has to do with the mounting. It looked the same as the other init.rc's that I was looking at, but it was all running together at that point last night. I'll dig into it some more tonight and look at the mounting of the base init file and see what I can come up with. Hopefully something will jump out.

Dont pull bin/vold from a prebuilt image, make sure you're building the aosp version. Also, make sure you are pulling prebuilt/vold.fstab from my device repo.
Android uses the vold daemon and fstab files to manage sdcard mounts, not a simple mount command like the ones used in init.rc for other partitions.
Sent from my SCH-I500 using XDA App

Thank you guys for all the hard work!

Looking forward to trying this out! Just to be sure- when I'm done playing I can go straight back to the exact way I have it now as long as I have a nandroid backup? No harm done?
sent from my superclean mesmerize

co6alt said:
Looking forward to trying this out! Just to be sure- when I'm done playing I can go straight back to the exact way I have it now as long as I have a nandroid backup? No harm done?
sent from my superclean mesmerize
Click to expand...
Click to collapse
No, you also need to revert to a 2.1 kernel as well. I mean 2.1 will boot on this kernel, but I can't say that it will work perfectly, and I found my scdard still didn't after a restore until I reverted kernels.

So restoring doesn't change the kernels, just the rom?
sent from my superclean mesmerize

co6alt said:
So restoring doesn't change the kernels, just the rom?
sent from my superclean mesmerize
Click to expand...
Click to collapse
What you should do is download jt1134's Mesmerize Voodoo5 w/ Voodoo Sound kernel and flash it. You should then take a backup in perfect working order. If you want to play with 2.2, wipe, flash the rom, then kernel. When you're done, wipe, restore the backup, then flash the previous kernel.

Gotcha. Ha, I just found out about voodoo sound. That'll be tonights project, then 2.2 tomorrow hate this edge network junk
sent from my superclean mesmerize

co6alt said:
Gotcha. Ha, I just found out about voodoo sound. That'll be tonights project, then 2.2 tomorrow hate this edge network junk
sent from my superclean mesmerize
Click to expand...
Click to collapse
EDGE? AT&T.. What?
I've got the source downloading for jt's latest build so hopefully we'll have some improvements soon. (=

dcow90 said:
EDGE? AT&T.. What?
I've got the source downloading for jt's latest build so hopefully we'll have some improvements soon. (=
Click to expand...
Click to collapse
Sweet waiting for a few more things to be functioning before I try using it. Thought maybe about trying to tomorrow but only as a test.
Edit: I just flashes the ROM and Kernel last night 0 problems booting and starting up phone was basically functioning then when I installed the Froyo Gapps I couldn't use the phone anymore because no data connection couldn't get passed the google account setup but seemed to work.
The only thing that was weird is before I installed the gapps zip while playing around the phone kept going back to the silver Android logo seeming as if it was restarting and going back to the lock screen but I managed to test the Phone, called 611 got US Cellular so that works!
Thanks again for your work I definitely and looking forward to this.

Big thanks to the devs! This is an awesome step forward. I flashed the ROM and Kernel, and although it's definitely alpha, it's awesome progress!
<rant>
It's pitiful that team of hobbyists and enthusiasts, working for free, in their spare time can port 2.2 faster than Samsung, who employs a full staff of software and hardware engineers, armed with development tools and source code. SAMSUNG, YOU SHOULD BE ASHAMED.
</rant>

Yoder808 said:
Big thanks to the devs! This is an awesome step forward. I flashed the ROM and Kernel, and although it's definitely alpha, it's awesome progress!
<rant>
It's pitiful that team of hobbyists and enthusiasts, working for free, in their spare time can port 2.2 faster than Samsung, who employs a full staff of software and hardware engineers, armed with development tools and source code. SAMSUNG, YOU SHOULD BE ASHAMED.
</rant>
Click to expand...
Click to collapse
From what I've read, it isn't a question of capability, i'ts just politics.
Thankfully we have wonderful developers to take the crap manufacturers throw at us and turn it into what really should be!

bdemartino said:
From what I've read, it isn't a question of capability, i'ts just politics.
Thankfully we have wonderful developers to take the crap manufacturers throw at us and turn it into what really should be!
Click to expand...
Click to collapse
Oh I agree 100%. They COULD have rolled out 2.2 months ago, if they wanted to.

Yoder808 said:
Oh I agree 100%. They COULD have rolled out 2.2 months ago, if they wanted to.
Click to expand...
Click to collapse
Samsung could have rolled out an firmware update but from what I've read they leave it up to the carriers to decide when they roll out updates.. especially OTAs since its on their end. US Cellular does spend a large amount of time testing their phones before releasing anything because their still small business orientated. That said, they easily could have rolled something out for us much earlier than this, as far as the small business goes they could have released it un-supported to commercial users and told business' not to load it yet plus not shipped any phones with it.. at least we'd have the option then..

I9000 Gingerbread is out

There is a new leak of gingerbread out for the SGS over in the I9000, and apparently this is supposed to be version that will be the official release.
http://forum.xda-developers.com/showthread.php?t=1009177

Nice, hopefully it doesn't take forever to see it officially released like it did with Froyo!

Waiting for source

I'm not too worried about AT&T, I believe once the source is released we will have many official releases XDA style

once the source is out we will have it. thank god for xda! and of coarse supercurio! i have been rocking out to music for the last couple days thanks to voodoo sound, not that the sound was bad before but now i can really appreciate it. also getting some better iem's (in ear monitors) the samsung ones are ok, well for an included accessory they are amazing but nothing compared to what is out there. i wouldnt think about getting a different phone right now. but i will see if the infuse has the hifi wolfson amp in it. the galaxy s 2 looks amazing but makes me wonder what will be out when i am up for a new contract.

Neat, hope the source appears sooner rather than later after the official release.

Lol... I must be losing it. And official sgs 2.3 leaks and this is the extent of the discussion. .... Lol wtf.

most people are more excited by cm7 for some reason. this is what i will use as soon as a reorient kernel comes about, all i can do is hope the source is realesed shortly. i think it was available pretty quick after jpx/jpy were released so i think it wont take long.

Nevermind

whiteguypl said:
Lol... I must be losing it. And official sgs 2.3 leaks and this is the extent of the discussion. .... Lol wtf.
Click to expand...
Click to collapse
Probably because this is like the 5th thread this weekend about this.

Miami_Son said:
Probably because this is like the 5th thread this weekend about this.
Click to expand...
Click to collapse
Regardless... It's a big deal. And none of the other threads made it very far. At all.
Go look at the i9000 forums. They're littered with posts and 2.3 sgs roms. All we have are crickets.

To be fair, we don't have the source available, so the leaked rom is kind of useless to us. It's a neat novelty, just to flash for a few minutes to see what's in store, but it's definitely not something you would use daily.

Just downloaded the Rom.. anyone know of a good kernel to use with this rom?? will CM7 kernel work with this rom? since its 2.3.3

TriC_101 said:
Just downloaded the Rom.. anyone know of a good kernel to use with this rom?? will CM7 kernel work with this rom? since its 2.3.3
Click to expand...
Click to collapse
Highly doubtful.. It should come with a compatible kernel and modem packaged in to it.
I wouldn't flash it straight through odin if I were you, though. If you have access to a linux machine, you should repackage it as a cwm flashable zip that doesn't flash boot or sbl, otherwise you risk either perma-bricking your phone or locking your bootloader.

My memory must be going. I remember us having ported i9000 2.2 roms well before the source dropped.

TriC_101 said:
Just downloaded the Rom.. anyone know of a good kernel to use with this rom?? will CM7 kernel work with this rom? since its 2.3.3
Click to expand...
Click to collapse
Stock kernel will boot, but there will be sound logic, screen orientation, button mapping...... problem list extends
Not until Sammy realeses the source code of GS gingerbread ROM that we can have reoriented kernels.

whiteguypl said:
My memory must be going. I remember us having ported i9000 2.2 roms well before the source dropped.
Click to expand...
Click to collapse
No... We didn't have reoriented kernel until JPM source was released. And before that, we were playing with the leak JI6 Captivate Froyo.

Guess it's time to start taking vitamins.

whiteguypl said:
My memory must be going. I remember us having ported i9000 2.2 roms well before the source dropped.
Click to expand...
Click to collapse
Vibrant owners have a port of this already, so yes it would seem that reorienting can be done without source, but devs aren't touching this for some reason...I really hope that changes cause I want to try this out but don't have the knowledge base to try to reorient the kernel myself and don't have time to learn currently.

No source, no kernel, no ROM. That simple.
Sent from my Xoom.

[REF] Github repo for SGH-I997R Source Release

Inspired by supercurio creating a master git repo for SGH-I997R development, I'm in the process of uploading today's source release from Samsung of the Gingerbread kernel for the Rogers Infuse 4G. (I'm surprised none of the other kernel hackers here have already done it... )
See supercurio's post http://forum.xda-developers.com/showthread.php?t=1054738 for more info on why git is good, and superior to kernel devs using tarballs directly from Samsung. This method is already unofficially how the kernel devs have been working - nearly every kernel here is forked from gtg465x's github repo.
I don't plan on directly doing development on this repo - It's just here as a starting point for everyone else to fork from. Some of us have slow upstream, so it's easier to pull a fork than it is to push a tarball import. However I might consider pulling in basic fixes to this repo (.gitignore, Makefile fixes - basically the same things supercurio has fixed in his unified git repos). (Edit: I'm starting to consider doing things a bit differently in order to allow this to stay as a relevant reference - After all there are certain "core" features like Voodoo Lagfix/Sound that have no known detrimental effects and are basically expected from any kernel used by the community.)
One thing is that most of the other ref repos are on a github "team" account - mine is on a personal account. I'm going to look into whether I can change this without breaking the fork relationships.
The repo is located at https://github.com/Entropy512/linux_kernel_sgh-i997r
Initramfs from Wednesday's dump is at https://github.com/Entropy512/initramfs_sgh-i997r
Note: If someone creates a better "master" repo for everyone to track, I'll happily edit this post to point there.
Update: Merged a pull request from LinuxBozo that has a bunch of .gitignore fixes and Makefile fixes.

Good work! Looking now.

Entropy512 said:
Inspired by supercurio creating a master git repo for SGH-I997R development, I'm in the process of uploading today's source release from Samsung of the Gingerbread kernel for the Rogers Infuse 4G. (I'm surprised none of the other kernel hackers here have already done it... )
See supercurio's post http://forum.xda-developers.com/showthread.php?t=1054738 for more info on why git is good, and superior to kernel devs using tarballs directly from Samsung. This method is already unofficially how the kernel devs have been working - nearly every kernel here is forked from gtg465x's github repo.
I don't plan on directly doing development on this repo - It's just here as a starting point for everyone else to fork from. Some of us have slow upstream, so it's easier to pull a fork than it is to push a tarball import. However I might consider pulling in basic fixes to this repo (.gitignore, Makefile fixes - basically the same things supercurio has fixed in his unified git repos)
The repo is located at https://github.com/Entropy512/linux_kernel_sgh-i997r - There is nothing visible there yet as the push is still in progress. It should be done within 30 minutes or so.
I don't have an initramfs repo yet - we need an initramfs dump from a device first.
Note: If someone creates a better "master" repo for everyone to track, I'll happily edit this post to point there.
Click to expand...
Click to collapse
Absolutely awesome news :-D
Sent from my SAMSUNG-SGH-I997 using XDA Premium App

Oh blast, hadn't even seen that kernel code was available... thanks Entropy!

A personal favor I'd like to ask of people forking - try to keep things to one feature per commit. An example being LinuxBozo's ext4 backport to the Froyo kernels - it was simple and easy to apply to other kernels. As opposed to someone had a massive supercommit that added a whole bunch of stuff at once, making it hard to either pick-and-choose or hard to apply if they had already applied a single-feature commit for one of the features. (One example being a commit that combined something like TinyRCU, jhash3, and BFQ all in one. I don't remember exactly what it was.)

Entropy512 said:
A personal favor I'd like to ask of people forking - try to keep things to one feature per commit. An example being LinuxBozo's ext4 backport to the Froyo kernels - it was simple and easy to apply to other kernels. As opposed to someone had a massive supercommit that added a whole bunch of stuff at once, making it hard to either pick-and-choose or hard to apply if they had already applied a single-feature commit for one of the features. (One example being a commit that combined something like TinyRCU, jhash3, and BFQ all in one. I don't remember exactly what it was.)
Click to expand...
Click to collapse
Defuse kernel
Sent from my SAMSUNG-SGH-I997 using XDA Premium App

Is that all we needed for gb roms or is there still more needed?
Sent from my SAMSUNG-SGH-I997 using XDA Premium App

nelomen said:
Is that all we needed for gb roms or is there still more needed?
Sent from my SAMSUNG-SGH-I997 using XDA Premium App
Click to expand...
Click to collapse
Initramfs, radio firmware dump, proper /system dump. Ours is incomplete.

Updates:
Merged LinuxBozo's pull request with build fixes
Merged LinuxBozo's pull request with the rainbow fix
Added initramfs repo

Entropy512 said:
Updates:
Merged LinuxBozo's pull request with build fixes
Merged LinuxBozo's pull request with the rainbow fix
Added initramfs repo
Click to expand...
Click to collapse
Nice!! Anything buildable yet?

ookba said:
Nice!! Anything buildable yet?
Click to expand...
Click to collapse
should be buildable since initramfs is available, tomorrow gtg's voodoo commit should be available too. this is all very exciting.

ookba said:
Nice!! Anything buildable yet?
Click to expand...
Click to collapse
A few more things got pulled in last night.
Kernel - not much
Initramfs - Working CWM - or at least it comes up, it hasn't been fully tested functionally yet
As of last night a few people have custom kernels running including myself, although some people still can't boot them. CWM wasn't working until past midnight...
Next up is voodoo - Not sure if I'll include that in the main initramfs repo or not. Maybe as a branch. It is a fairly standard mod, so it should be in a readily accessible repo

Bad news - as I said before CWM hadn't been fully tested.
Apparently, after further testing, it still does indeed have some pretty severe issues.

Sadface
10c

P1 Wookie said:
Sadface
10c
Click to expand...
Click to collapse
We have what seems to be working CWM and Voodoo thanks to gtg - in testing now.
The trolls in IRC aren't helping. Not a good time for the ops to be AFK.

trolls suck.
GL guys.

Entropy512 said:
We have what seems to be working CWM and Voodoo thanks to gtg - in testing now.
The trolls in IRC aren't helping. Not a good time for the ops to be AFK.
Click to expand...
Click to collapse
Gotta love the trolls.
Good luck guys. I know you all will figure it out

Well, thanks to the blasted trolls and the unfortunate circumstance of my only internet being my phone, I'm borked from being able to participate in the main infuse4g room as webchat is banned (for a good reason) and I can't get past the SASL issue otherwise.... oh well.

bedwa said:
Well, thanks to the blasted trolls and the unfortunate circumstance of my only internet being my phone, I'm borked from being able to participate in the main infuse4g room as webchat is banned (for a good reason) and I can't get past the SASL issue otherwise.... oh well.
Click to expand...
Click to collapse
why no use of a client?

drowningchild said:
why no use of a client?
Click to expand...
Click to collapse
Finally got it to work, had to hack a command line client.... urg.

Is there hope?

Sorry if this has been asked, but I checked a lit of the q&a but is there any hope or any developers working on ICS for us? And because I don't know much why is it hard to port to the sgs 4g?
Sent from my SGH-T959V using XDA App

An entire kernel needs to be built from practically scratch... Its a tonnnn of work. And our GB source JUST came out...
Sent from my SGH-T959V

OK sorry, like I said I don't know much and just was curious. Thank you for the info tho
Sent from my SGH-T959V using XDA App

tehgyb said:
An entire kernel needs to be built from practically scratch... Its a tonnnn of work. And our GB source JUST came out...
Sent from my SGH-T959V
Click to expand...
Click to collapse
Really? I know some (almost all except the very newest ones) of the Motorola phones have completely locked boot loaders which prohibit any unauthorized kernel from being loaded. Take for example, the Milestone and the Milestone xt720- they were forced (figuratively speaking) to build roms for Froyo and Gingerbread off of the same, crappy kernel that was released with Eclair. They have done a lot, it's far from stable. Which surprises me considering how bad the phone was, how few people got it, and the general negative attitude that tends to flow through Xda.
I don't know much about it- for example, once the kernel is built for gingerbread, does a new one need to be built, or can that kernel be repurposed?

How about building a Gingerbread Kernel ( CM7 based )
Now that they have finally released a Gingerbread source for the 4GS, It would be nice to have a CM7 build. I know the Devs are busy with ICS, or other products, but if one would be willing to work with me, I'd be willing to make a jab at it. I can currrently build the released kernel, but something is missing that I can not get the zimage to successfully load. It is also smaller in size. The only referenced web discussion I could find was for the I9003 series and there are files mentioned that are not part of the 4G. Any help would be appreciated.

mccabet said:
Now that they have finally released a Gingerbread source for the 4GS, It would be nice to have a CM7 build. I know the Devs are busy with ICS, or other products, but if one would be willing to work with me, I'd be willing to make a jab at it. I can currrently build the released kernel, but something is missing that I can not get the zimage to successfully load. It is also smaller in size. The only referenced web discussion I could find was for the I9003 series and there are files mentioned that are not part of the 4G. Any help would be appreciated.
Click to expand...
Click to collapse
Oh trust me, devs are looking at cm7. I know I am, like its a big New York steak!
But its going to be a while, unless you can employee me to work on it. Otherwise... Gotta pay the bills before I have fun.
Sent from my SGH-T959V using xda premium

I know that and realize other priorities make everyones time valuable. I am trying to get up to speed and just need a little bit of help getting the base kernel to build. I have successfully built the CM7 in the past for the captivate, but this is the first time for an raw, untouch source release from samsung.
Thanks for your input.

Also, just to note. There are multiple kernel devs here.
Still waiting for drhonk to release some Bali goodness.
My kernel has a different goal and approach from drhonk's. Search the op of my kernel thread for 'plan'.
As usual, all code is GPL and is available on github (see my signature), so if you want to learn or help out, start with the source.
Sent from my SGH-T959V using xda premium

finch8423 said:
Really? I know some (almost all except the very newest ones) of the Motorola phones have completely locked boot loaders which prohibit any unauthorized kernel from being loaded. Take for example, the Milestone and the Milestone xt720- they were forced (figuratively speaking) to build roms for Froyo and Gingerbread off of the same, crappy kernel that was released with Eclair. They have done a lot, it's far from stable. Which surprises me considering how bad the phone was, how few people got it, and the general negative attitude that tends to flow through Xda.
I don't know much about it- for example, once the kernel is built for gingerbread, does a new one need to be built, or can that kernel be repurposed?
Click to expand...
Click to collapse
you seem to be forgetting that every device except for the SGS1 series takes a boot.img this makes it a lot easier to do things because of the partition layout. sgs1 series uses zImage with initramfs, and has a BML/RFS file system. Not ext4, mtd, yaffs2, ext3...but a **** file system.

krylon360 said:
you seem to be forgetting that every device except for the SGS1 series takes a boot.img this makes it a lot easier to do things because of the partition layout. sgs1 series uses zImage with initramfs, and has a BML/RFS file system. Not ext4, mtd, yaffs2, ext3...but a **** file system.
Click to expand...
Click to collapse
Yea, don't sweat this quite yet, Krylon360
I say we work on the cwm that converts to ext4 like epic4g, like you'd suggested in irc. I already have some code and tests in place to convert to mtd. It's just not in any kind of stable/usable/releasable form yet. It's still early code.
When (hopefully soon) I get time, and hopefully an email back from chipworks about some info I need, I'm going to get u-boot rolling. It's hard for me to explain all the benefits of this now, but some snippets:
fastboot mode (say, flash an mtd partition like: fastboot flash <partition name> <file>)
android usb gadget support (adbd) in u-boot (say to have early console access at the bootloader), and plenty of other goodies.
many other things I just don't have time to list, on top of the fact that we can now control the bootloader...

doing the auto conversion is cake. it's just a bit inside init.rc that tells it to run a script in /sbin, that script is just a quick conversion to ext4. as long as /system, /data, and /cache have the ext4 mounting bit in init.rc, and the ext4.ko is in /lib/modules, it should would just fine.
I'll get the script while Im at work tomorrow.

Krylon360,
you mentioned the initramfs being combined with the zimage. Can you shed some light on how this is done?
bhundven,
Thank you for your help. I will be checking out your source to look over and looking at your forum. Thanks Again!

I know everyone has prob said this. But I'm willing to test betas and such for the sgs4g. Let me know if I can. Thanks
Sent from my SGH-T959V using XDA App

[wip][aosp][port][dev] 2.6.35.7 AOSP Kernel Port [05/14/2012]

This is a development thread. If you want a conversation thread, please open one in the general forum!
I've released the source a little early of completion, so I can get others on teamacid to help out. So until we get on the android-samsung-2.6.35-gingerbread branch and changes added, tested, pushed, and tested by a more general audience, I would NOT SUGGEST FLASHING THIS. Don't expect any wiz-bang features added or anything like that. This is a port. After the port is done, we can do all sorts of stuff.
Milestones to complete:
Scrub existing code that does not relate to Galaxy S 4G (SGH-T959V/VibrantPlus) from arch/arm/...
Move architecture specific code to mach-herring.c (as it should be) and make the changes diff cleanly with the aosp samsung android-samsung-2.6.35-gingerbread branch
Scrub and import needed drivers to new android-samsung-2.6.35-galaxys4g branch with herring conversion stuff imported.
Try to get rid of dvfs stuff and move to stock cpufreq (for easier future porting to Linus's mainline, which is the goal of this kernel, amongst other modifications that will open up...)
Get all components working (wifi/bt/gps/etc. It may not be possible to use bml/fsr/rfs/ext4, because of the symbol table changing, but lets try to see if we can get it working before making the kernel compatible with cm/aosp)
investigate BML<->MTD rom conversion kernel
I have currently completed Milestone 1. I am currently running stability tests with unnamed rc2. The binary should be the same as the minimal changes to stock source to make it boot and work with a standard bml rom, but without the other board code for dempsy, kepler, vibrant, vibrantplustelus, flemming, aries ntt, and others. All code is cleaned up and specific for VibrantPlus/SGH-T959V.
I've put together a new initramfs/recovery based on v5.0.2.8 to work on BML. This does not contain the voodoo lagfix support.
You WILL have to use an updater-script that forces conversion to ext4.
GitHub:
Kernel - https://github.com/bhundven/android_kernel_samsung_galaxys4g
Initramfs - https://github.com/bhundven/android_initramfs_samsung_galaxys4g
Stay tuned... I will update with progress.

post for uploads

OP updated. Using new initramfs (gingerbread branch), some kernel and build.sh fixes.

Just a note, I've made a little progress on m2.
Looking at possibly having something releasable here in the next week or two.
I've been out of work now since may 1st and its been hard to motivate myself on anything phone related.
Much thanks to the members of teamacid and teamkickass for keeping this stuff going!
Sent from my SAMSUNG-SGH-I717 using xda premium

So these are BML kernels converted to MTD?
Sent from my SGH-T959V using XDA

smontero said:
So these are BML kernels converted to MTD?
Sent from my SGH-T959V using XDA
Click to expand...
Click to collapse
You missed the point entirely.
EDIT
Look under "Milestones to complete"

I see but I don't completely understand. I just found out the difference between BML and MTD but I was asking cause I'm using the miui MTD and i wanted to know if these kernels would work
Sent from my SGH-T959V using XDA

He hasn't posted download links to them yet.

FBis251 said:
He hasn't posted download links to them yet.
Click to expand...
Click to collapse
Right. If you know how to compile the kernel, you could. If you did, you would currently have a BML kernel. (note there is also no mtd support in the current initramfs either)
I'm not sure if Milestone 2 will be able to support RFS. I may pull in the FSR code from supercurio's repository so that we can still have BML+ext4, but that code was for a froyo kernel.
If I can't get that to work, then this kernel will be MTD only. I'm still having some problems where my current Milestone2 changes (not checked in) is not booting correctly.
As I said, I'll have an update soon.