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..

[THINK-TANK] EB13 Source a Rebranded DKxx Source? : Cleaned Source Inside : (87.4 mb)

Searching through the EB13 source in /arch/arm/boot/ I came across three files of interest, victory_test_kernel.tar, recovery.bin and zImage, I ran over hear excited since I thought Sammy was throwing us a bone to get some custom kernels running early, but nevertheless in true Samsung fashion the files of interest come from October 1st of all dates, and seem to be before DK28. That's Sammy for you. You'll have to wait until Monday to get anything truly EB13.
-rwxr-xr-x 1 android android 5.5M Oct 1 08:22 victory_test_kernel.tar
Click to expand...
Click to collapse
This got me thinking, maybe Samsung is just had this source for a while now and this is the outcome of all their edits they've made through the leaked stages, this being the final product, anyways, here is a totally cleaned version of the EB13 source that takes half the time to download and is ready to be compiled with a few edits to victory_03_defconfig and build_kernel.sh.
Code:
Edited victory_03_defconfig to add initramfs source and cleaned
various aspects of unneeded files let behind by Samsung.
If your a dev coming from the DI18 source you might find it interesting to know that the default config is no longer ares_003_defconfig, but is victory_03_defconfig.
Click to expand...
Click to collapse

Yo didnt you say that you was working on MIUI and few other roms?How is that coming along?

bubby323 said:
Browsing the EB13 source and took a peak at /arch/arm/boot and found victory_test_kernel.zip. Flash with Odin, should work great on any DK28 rom, using rfs.
I also found recovery.bin which can be flashed to bml8 for the stock Samsung recovery experience you'll find which I assume is 3e. here
Click to expand...
Click to collapse
Do I get to keep root? How is the GPS? More questions that no one can answer this quickly...

u say for RFS?
What does this mean for ext? Is that going to have to be updated or something based on this new releases or no ?

honestly not to knock bubby but i wouldnt bother, wait like 40 mins there will be cwm3 friendly versions that keep root and have ext4/rfs etc etc

shabbypenguin said:
honestly not to knock bubby but i wouldnt bother, wait like 40 mins there will be cwm3 friendly versions that keep root and have ext4/rfs etc etc
Click to expand...
Click to collapse
Granted, this post was mostly for devs in the first place, just letting everyone know and uploading resources for those who dont want to dig through the source and wait for it to download.

yea i get that bubby, and i thank you for it
plus its good to let end users know there is work being done behind the scenes

shabbypenguin said:
honestly not to knock bubby but i wouldnt bother, wait like 40 mins there will be cwm3 friendly versions that keep root and have ext4/rfs etc etc
Click to expand...
Click to collapse
Ok thought so, btw do we still have to wait til monday, to get things really going like roms even with this?
I read elsewhere that the source doesnt help if we dont have the modem and kernal from the ota?

theres work on the kernel right now, may not be done fully but there is work.. the ota will give stuff like modem and the rom itself. dont be surprised to see test builds before thern tho

shabbypenguin said:
theres work on the kernel right now, may not be done fully but there is work.. the ota will give stuff like modem and the rom itself. dont be surprised to see test builds before thern tho
Click to expand...
Click to collapse
Thought so, i will wait til next week, maybe mid week and, probaly be an update for everything and and and update zip for the new modem.

The initramfs seems to be half-developed there is alot of junk added, and stuff *seems* to be alot missing comparing everything to DK28.

it an old build.. it was compiled on 10/2010 pre dk28 kernel
lock the thread

noobnl said:
it an old build.. it was compiled on 10/2010 pre dk28 kernel
lock the thread
Click to expand...
Click to collapse
HMM, meaning the source has old stuff in it??

noobnl said:
it an old build.. it was compiled on 10/2010 pre dk28 kernel
lock the thread
Click to expand...
Click to collapse
That's odd why would they include old stuff in the source. Junk has been left everywhere.

davidrules7778 said:
Thought so, i will wait til next week, maybe mid week and, probaly be an update for everything and and and update zip for the new modem.
Click to expand...
Click to collapse
<delete>..............

davidrules7778 said:
HMM, meaning the source has old stuff in it??
Click to expand...
Click to collapse
Excellent avatar! "Who ARE you....!!?"
Anyway, Seems that without the kernel and modem the source isn't the end al be all. I'm dying to get f'n TV out working on this phone though. I can continue to dream.

bubby323 said:
That's odd why would they include old stuff in the source. Junk has been left everywhere.
Click to expand...
Click to collapse
Sprint figures we need something to do? ;-)
Sent from Bonsai v 5.0.3

ZenInsight said:
Excellent avatar! "Who ARE you....!!?"
Click to expand...
Click to collapse
What are you talking about? Are you being an ass?

So is this an old source or is this thread a mistake its new EB13 source? I am so confused after reading this thread.

ryno502 said:
So is this an old source or is this thread a mistake its new EB13 source? I am so confused after reading this thread.
Click to expand...
Click to collapse
Sammy posted it as new eb13, however it apparently has some very old code in it...hmmmm.

[Q] Whats the newest official captivate rom out?

Im unfamiliar with the names of new roms, and want to try a new rom out. In the past I have used CM7, MIUI, apex, etc.
I am currently on Pinnacle 1.2 and I love it. From what i understand this is a KH3 rom, and was a official captivate rom, and this is why my battery life is so much better compared to CM and apex roms.
From now on i only want to stick with releases like pinnacle, for battery purposes. How do i know which releases are captivate releases, and which are I9000 or other roms?
Which rom is out right now that is the newest official captivate release? Also is there any new kernels that are compatible with pinnacle/new oficial captivate releases?
Thanks in advance.

1. Samsung never released any official GB ROM for our captivates, KH3 is also a leaked build, though have been pretty solid build.
2. KF1, KH3, KI1, KI2, KJ1, KJ2 and KJ3 are Captivate (I897) GB ROM base leaked so far.
3. There are few KJ3 custom ROMs out there.
4. KJ3 kernels (Boog's, Corn Kernel, Samurai & Red Nebula) should work with Pinnacle 1.2/1.3.

IlluminatedOne said:
1. Samsung never released any official GB ROM for our captivates
Click to expand...
Click to collapse
Samsung doesn't release the update, the carrier does. Rogers in Canada has released gingerbread officially for the captivate. And source code for the kernel.
Manufacturers are at the mercy of the carriers.
Cappy native builds usually start with k
I9000 start with j
Cm7 and miui are completely different altogether.

IlluminatedOne said:
1. Samsung never released any official GB ROM for our captivates, KH3 is also a leaked build, though have been pretty solid build.
2. KF1, KH3, KI1, KI2, KJ1, KJ2 and KJ3 are Captivate (I897) GB ROM base leaked so far.
3. There are few KJ3 custom ROMs out there.
4. KJ3 kernels (Boog's, Corn Kernel, Samurai & Red Nebula) should work with Pinnacle 1.2/1.3.
Click to expand...
Click to collapse
Ah, i see. So just leaks of gingerbread have been released so far? Is that the order they came out in? Is kj3 a better rom than kh3?
I basically just want to know which rom is based on what release - and how old that release has been out for. I see so many roms on xda, but really know nothing about the initial release that they are based on.
Is there a site everyone watches to wait for releases?
studacris said:
Samsung doesn't release the update, the carrier does. Rogers in Canada has released gingerbread officially for the captivate. And source code for the kernel.
Manufacturers are at the mercy of the carriers.
Cappy native builds usually start with k
I9000 start with j
Cm7 and miui are completely different altogether.
Click to expand...
Click to collapse
Do rogers builds work on captivate? i know the answer is yes, but i mean work like a (k) build does on my phone.

Like you, I like to stay stock as much as possible. Use Andromeda³ and Ursa Minor². It's Froyo and as close to official stock as you can get. It's a great ROM and really underrated with all the usual fixes you would expeect; exceptional performance, good battery life, GPS fixed, etc. It's really all you need. Slap on Go Launcher Ex and a nice theme and you're set.
No longer sent from my BlackBerry.

lourivellini said:
Ah, i see. So just leaks of gingerbread have been released so far? Is that the order they came out in? Is kj3 a better rom than kh3?
I basically just want to know which rom is based on what release - and how old that release has been out for. I see so many roms on xda, but really know nothing about the initial release that they are based on.
Click to expand...
Click to collapse
Yes thats the order of Captivate GB updates....KH3 is most solid version yet with good battery, gps and over all performance...A new one has just popped up called KK1.....
The naming convention depends on the months and number of release...K is for 2011 in KH3 but H stands for the month and number(3) stands for the number of release that month...similarly for others...
lourivellini said:
Is there a site everyone watches to wait for releases?
Click to expand...
Click to collapse
try Samfirmware.com and XDA....but it will be all over the news if the official updates comes for captivate....like it came for Epic

I used a KJ3 ROM for a while, then went to KH3 (Pinnacle). I saw no difference in memory usage, etc. except that the KJ3 ROM was missing a bunch of ringtones (only came with digital phone), and the Gallery was pretty much unusable (black screen issue). For me, KH3 has been less buggy. Now there's a new leak out, but I'll wait to see if there are any real improvements before going through the trouble of flashing another ROM and configuring my phone again.

KK1is out now!
Sent from my I897 using xda premium

viny2cool said:
The naming convention depends on the months and number of release...I forgot whats K is in KH3 but H stands for the month and number stands on the number of release that month...similarly for others...
Click to expand...
Click to collapse
The first K stands for the year K=2011, the stock shipped firmware was JF6, J=2010. At least this is my understanding of it.

Dnorwood said:
The first K stands for the year K=2011, the stock shipped firmware was JF6, J=2010. At least this is my understanding of it.
Click to expand...
Click to collapse
yes, that's correct!

AT&T Offically Announce GB for Captivate!

I know that this is not a developmental release or a custom built ROM but I thought the community might like to see this.....AT&T officially releases GB for our Captivates!
http://www.samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00024051&fm_seq=24219

Unfortunately, the notice indicates it is KK4, but the source has also been posted at http://opensource.samsung.com. Let the fun begin....again.

disappointed about AT&T and SAMSUNG

gibson3659 said:
Unfortunately, the notice indicates it is KK4, but the source has also been posted at http://opensource.samsung.com. Let the fun begin....again.
Click to expand...
Click to collapse
The source has been out for a while now...I'm thinking a few weeks, at least.

Has anyone checked to see whether this KK4 is the same as what was leaked two months ago - there's always the possibility of slipstreamed changes without reversioning, especially since there are definite bugs that remain in the leaked version, e.g., the kernel crashes when too many apps are are installed to SD.
At a minimum, given that the linked instructions describe this as a full wipe, the ROM is packaged differently than the previous leaks.

LOL. couldn't have come at a better time! /sarcasm

Anyone got an alternate mirror in the event the Kies Mini upgrade fails for me, as it did previously when I tried to upgrade to Froyo? It would be a nice backup in the event I need to go back to stock (assuming, although I probably shouldn't, that in the two months since KK4 leaked, something had to get updated.

God do I miss bln.

RKight said:
The source has been out for a while now...I'm thinking a few weeks, at least.
Click to expand...
Click to collapse
Then is there anyone working on a custom kernel based on KK4? If it has been out for a few weeks, I would have expected a thread or 2 by now with BLN and voodoo sound. Developer interest seems to be waning for our cappy's.

Thread moved
satans spawn1972 said:
I know that this is not a developmental release or a custom built ROM but I thought the community might like to see this.....AT&T officially releases GB for our Captivates!
http://www.samsung.com/us/support/SupportOwnersFAQPopup.do?faq_id=FAQ00024051&fm_seq=24219
Click to expand...
Click to collapse
If you know something isn't development, don't post it there!

reinbeau said:
If you know something isn't development, don't post it there!
Click to expand...
Click to collapse
I knew that that my post wasn't dev (as I stated in my own post) but I posted it there so the devs could see the "Official" release was out. That way they could use it as the source to their ROMs for KK4.
Sorry for the infraction.................

satans spawn1972 said:
I knew that that my post wasn't dev (as I stated in my own post) but I posted it there so the devs could see the "Official" release was out. That way they could use it as the source to their ROMs for KK4.
Sorry for the infraction.................
Click to expand...
Click to collapse
Just a warning This is all over, so I'm sure they all know about it. Hopefully it'll bring some stability to our Captivate ROMs (they won't have to be based on I9000 now, although I have no idea what else the I9000 functionality brings). I am not a developer, just an educated user.

gibson3659 said:
Then is there anyone working on a custom kernel based on KK4? If it has been out for a few weeks, I would have expected a thread or 2 by now with BLN and voodoo sound. Developer interest seems to be waning for our cappy's.
Click to expand...
Click to collapse
This is the same Rom/Kernel developers have been working on for the last month, so yes there is a lot of custom kernel, but none with BLN or voodoo color due to lack of source for it.

popfan said:
This is the same Rom/Kernel developers have been working on for the last month, so yes there is a lot of custom kernel, but none with BLN or voodoo color due to lack of source for it.
Click to expand...
Click to collapse
Has anyone confirmed that this is in fact the same code that was leaked back in November? Just because it is named the same, it doesn't mean it will be exactly the same.

stoobie-doo said:
Has anyone confirmed that this is in fact the same code that was leaked back in November? Just because it is named the same, it doesn't mean it will be exactly the same.
Click to expand...
Click to collapse
I have a hard time believing ATT would release such an unstable release. It just can't be the same KK4 leaked back in November. It is inconcievable.

Upgraded my cappy without a hitch.. Unfortunately, it was then powered off and put back in my Galaxy SII box (now my backup phone)

Time_Zone said:
I have a hard time believing ATT would release such an unstable release. It just can't be the same KK4 leaked back in November. It is inconcievable.
Click to expand...
Click to collapse
Inconcievable? I think this applies...
http://www.youtube.com/watch?v=G2y8Sx4B2Sk

newbie here, How do you root your phone again now?

z450 said:
newbie here, How do you root your phone again now?
Click to expand...
Click to collapse
Assuming this is the same as the leak; go to the dev KK4 thread and download the fugu kernel and the KK4 kernel
Flash fugu via Odin let it start and bootloop; pull battery; flash KK4 kernel

Or Click this...[APP]SuperOneClick

AT&T official gingerbread for Captivate discussion

I am opening this thread to discuss the new official release from AT&T and Samsung. Details can be found here.
I'm not sure why discussion rooting was a reason to close a thread, but I guess a overzealous mod is better than no mod.

I hate to burst your bubble but there's already an active thread about the official AT&T Gingerbread release.
http://forum.xda-developers.com/showthread.php?t=1437947

I am not sure how much needs to be discussed. It is the same rom that was leaked back in 11/16/2011. Developers have done some amazing stuff with the Rom so far. All that is left for them to do really is add BLN and voodoo color to the kernel. I am not sure if having the source will do anything more for the Rom themselves.
FYI - Mod don't like ppl reopening closed threads.

yes I was active on that thread. It was locked by a mod because people started to discuss how to root the new release. zergRush does not work on it.

popfan said:
I am not sure how much needs to be discussed. It is the same rom that was leaked back in 11/16/2011. Developers have done some amazing stuff with the Rom so far. All that is left for them to do really is add BLN and voodoo color to the kernel. I am not sure if having the source will do anything more for the Rom themselves.
FYI - Mod don't like ppl reopening closed threads.
Click to expand...
Click to collapse
Do we know yet that it is bit for bit the same?
Does anyone have an Odin or Heimdall compatible version of the ROM?

stoobie-doo said:
Do we know yet that it is bit for bit the same?
Does anyone have an Odin or Heimdall compatible version of the ROM?
Click to expand...
Click to collapse
Those are the two big questions I have too.

That last thread was sure cut short, but i have a question regarding kies mini. Im currently running the leaked UCKK4 Stock, rooted, and bloatfree; will i be able to upgrade with kies mini?

gbalwing said:
That last thread was sure cut short, but i have a question regarding kies mini. Im currently running the leaked UCKK4 Stock, rooted, and bloatfree; will i be able to upgrade with kies mini?
Click to expand...
Click to collapse
I had the exact type of rom running on my phone. Mini kies told me I was already running the latest rom. So, I did one click back to KB2 then used mini kies.

Ah, my apologies then.

I'll throw a bone out there, Fugu Root. Nuf said. Interesting enough tether manager likes to fc when you have debug enabled along with the usb connected.

c0ldburn3r said:
I'll throw a bone out there, Fugu Root. Nuf said. Interesting enough tether manager likes to fc when you have debug enabled along with the usb connected.
Click to expand...
Click to collapse
I also had Tethering manage FC on me, but only right after I flashed it on the first reboot. I have not seen it FC again. I am very familiar with the Fugu kernel swap and think it great method, but my issue that I don't have a source of the kies released KK4 kernel. Do you know how to gernerate or extract an ODIN flashable kernel from the running image?

I'm running Cyanogenmod kang build 7.2 right now but I gotta ask is it worth going to stock gingerbread? How stable is it? I'll be honest I miss some of the touchwiz apps, but IMO the stock froyo rom sucked. At the very least I'd probably root and remove the AT&T BS, but IMO The froyo rom ran slower and buggier than the stock eclair rom! I really just want everyone's general opinion of it. Its a tough call. I got my phone running pretty stable with Cyanogenmod right now and its out of warrenty anyway so it might not even be worth my time anyway.

nbarsotti said:
I also had Tethering manage FC on me, but only right after I flashed it on the first reboot. I have not seen it FC again. I am very familiar with the Fugu kernel swap and think it great method, but my issue that I don't have a source of the kies released KK4 kernel. Do you know how to gernerate or extract an ODIN flashable kernel from the running image?
Click to expand...
Click to collapse
Check the KK4 leak thread for the tar.

No one has confirmed that the KK4 leak is exactly the same of the offical KK4. That is my only hesitation. I would like to be sure that I am running the AT&T KK4 release

Cor-master said:
I'm running Cyanogenmod kang build 7.2 right now but I gotta ask is it worth going to stock gingerbread? How stable is it? I'll be honest I miss some of the touchwiz apps, but IMO the stock froyo rom sucked. At the very least I'd probably root and remove the AT&T BS, but IMO The froyo rom ran slower and buggier than the stock eclair rom! I really just want everyone's general opinion of it. Its a tough call. I got my phone running pretty stable with Cyanogenmod right now and its out of warrenty anyway so it might not even be worth my time anyway.
Click to expand...
Click to collapse
Well the camera is a heck of a lot better the AOSP. It's worth it, even though it's still RFS, it's snappy and way better the KB1 ever was.

Yeah speaking of rfs I'd definitely be putting a lag fix on. I might look into it, and yes I agree about the camera, in fact honestly the hate against touchwiz is unwarranted. All the touchwiz apps are better, even the launcher is better than vanilla android one(not counting cyanogenmod that uses adw, which is one if the best). Only thing I did notice is without touchwiz the rom is faster, so obviously it adds bulk but the apps are so much better!
Sent from my SGH-I897 using XDA App

I never did get slacker radio and maps working at the same time on kk4. Even with tweaks I mentioned in another thread, slacker started dying after about a day of use. No problems like that with cm7. Thats why I am mostly interested if they actually made any changes from the leak. I doubt it though.

Ginger Bread is here
Im updating currently to official ginger bread

Didn't you notice that Samsung & at&t dropped lots of original Gingerbread features? like the CRT screen-off animation... I can't find it on the new official GB update one.

Is CarrierIQ still present in the official build? Curious. It was in the leak.
Sent from my SGH-I897 using xda premium