yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] gonintendo:
You could also try a different version of odin. I've had the most success with 1.3 but I think it goes up to version 1.7.
[Vibrant Android Development] gonintendo:
It's CM7 only.
[Vibrant Android Development] C-4Nati:
So it says you can't see voodoo recovery. Can u see regular clock work?
[Vibrant Android Development] NCn1:
I cant use the newest one because it wont even load into clockwork, so im using the oldest one it ends with 1.1, that and the newest one are the only ones that will download into my phone.

Write every suggestion possible, I will try everything tomorrow, or pm if u dont wanna flood this thread.
[Vibrant Android Development] Tha Maxx:
::tips hat:: ty sir......:cool:
[Vibrant Android Development] DonutYankee:
Samsung really hid MobileAP in there. I'm guessing carriers asked for it.

Double rainbow looks much better in Beta 2.
[Vibrant Android Development] pegasus912:
Does this include JIT optimized for hummingbird processor? I saw that someone found it in this leak and figured out how to enable it.
[Vibrant Android Development] gonintendo:
Seconded
[Vibrant Android Development] wizern23:
Great job on the rom.
[Vibrant Android Development] xplanowestx:
So i was a little hesitant to flash this, however i'd have to say this is very polished for being so new and an i9000 rom. I still do see hiccups in lag and such every now and then, but overall great job. Going to try to use as a daily driver. Great work guys.
[Vibrant Android Development] DonutYankee:
Great ROM. This is the *first* 2.2.1 or 2.3.2 ROM where the lock-screen wallpaper actually worked. In previous ROMs phone ignored me setting a different one for lock screen and just showed the home-screen wallpaper. Great stuff, Whitehawk.
[Vibrant Android Development] darkknight49:
installing now.
[Vibrant Android Development] gonintendo:
It seems like Sammy has implemented some gpu acceleration in the browser. That must also be why it randomly stops scrolling and dolphin doesn't.

Sent from my Samsung Vibrant running Whitehawkx's gingerbread.
[Vibrant Android Development] pegasus912:
Great rom, everything works great except when you use the headphone toggle widget and you listen to audio through headphones, you can't turn the screen off (it will reboot). You can let the screen timeout and it won't reboot. This has probably been covered in this thread, but I don't have time to search through 33 pages.

Thanks again this rom is pretty cool.
[Vibrant Android Development] Whitehawkx:
This does not have the modified build.prop that was posted previously. Rawat has been very knowledgeable on the subject in the i9000 forums. Pretty much the theory is that the JIT optimizations are already in effect, they just aren't being calculated in quadrant scores. Going in and setting a bunch of the defaults from false to true in the build.prop enabled these to be calculated, but the benefit was already there without doing anything to the build.prop. So why not include it anyways just for fun? Because it breaks video playback for many different types of media, as well as the video recorder and camera.
[Vibrant Android Development] bobofosho123:
I would just like to give a huge, steaming, frothy pile of "Thank YOU!" to Whitehawx for giving us the divinely sweet treat known as gingerbread, in a non-volatile/idiot-resistant form no less. Thank you, thank you, thank you!
[Vibrant Android Development] mr.orange303:
+1

ive finally moved on from R2. Just awesome. Flat out awesome.
[Vibrant Android Development] DonutYankee:
Found one possible bug so far: Google Maps keeps force closing in the background for me. Haven't opened it yet.

EDIT: Just tried to open it and Force Closed immediately. So there's some issue with Maps for me.
[Vibrant Android Development] Whitehawkx:
Thanks for pointing this out. I was able to correct this in the asound.conf. Didn't include the modified file b/c I need to test how it works with the current workaround for routing calls properly. I will see about getting this fixed tomorrow and post the file you can just drop in without having to re-wipe everything.
[Vibrant Android Development] darkknight49:
damn, didn't work. Just got stuck in a boot loop.
[Vibrant Android Development] pegasus912:
Thanks for the quick response. I can tell, at least in the browser, that it is faster than 2.2 and 2.2.1 roms.
[Vibrant Android Development] }{Alienz}{:
Now if only Voodoo sound and GPS got in here along with a theme and this is banging :)
[Vibrant Android Development] HRodMusic:
i flashed it but i accidently hit a difrent language =S how do i go to english?
[Vibrant Android Development] DonutYankee:
Disregard my Maps issue. If anyone else had it, simply use Titanium to uninstall Maps, reboot and install from Market. Works fine for me.
[Vibrant Android Development] The_Ravager:
I flashed an i9000 theme on js5 AtriArc on my vibrant....works great...may just want to try....i took a shot in the dark
[Vibrant Android Development] HRodMusic:
i fixed the language issue =D
[Vibrant Android Development] projectxmatt:
Just flashed beta2 camera no longer works for me, I only get rainbow and pictures come back black. Also the left side of gallery has the rainbow too. I didn't have either of these issues in beta1. Other wise everything seems smooth so far.

Need to include stock gingerbread keyboard, I know its in the market but you, know for the authentic gb feel.

Great rom. Thanks!
[Vibrant Android Development] boimarc89:
is it just me or is the haptic feedback for the home button the only button not working?
[Vibrant Android Development] DonutYankee:
Sadly, even with having the setting in Spare Parts on normal the death-lag memory leak persists. I'll try Aggressive and see how that works.
[Vibrant Android Development] pegasus912:
Yeah same here, let me know how it works out.
[Vibrant Android Development] HRodMusic:
wait the 15 mins then reboot it should all be gone =D
[Vibrant Android Development] joe.kerwin:
+1. Aggressive messes with my launcher tho, restarts often. So close! But if I jump into a few apps it just bogs, sometimes locks up. Could a task killer help? Just to autokill certain apps like FB, plume, etc
[Vibrant Android Development] yvliew:
does this rom supprot .avi/divx video playing?? afaik, CM7 does not.
[Vibrant Android Development] cashyftw:
Man I doubt my phone has ever been this fast even with OC/UV! Thanks for all your hard work! Your seriously the best person ever.

PS: ahh I was wondering about the Task killer also, maybe it would stop the leaks?
[Vibrant Android Development] HawkPidgeon:
Same here. I can't get it into recovery or download mode, and I can't connect to ADB. I'm feeling a little lost.

Edit: Got it into download mode. I was just hitting the buttons at the wrong times.

Edit 2: Woo! Got it running, and this thing is FAST. Thank you for this ROM
[Vibrant Android Development] HRodMusic:
edit: task killer does an ok job at stoppin the leaks!
[Vibrant Android Development] sharkethicx:
So, I think I may have borked this thing up. I wanted to install a gb keyboard, so I went to ROM Manager and went to install zip and navigated to it, picked it, and then when it went to restart, it just hangs up at the Vibrant splash screen.

Do I need to install the Nexus S drivers to get this thing to work with Odin?
[Vibrant Android Development] yvliew:
I thought it was posted as RC1 but it got downgraded to Beta2?
[Vibrant Android Development] projectxmatt:
I did, i waited probably closer to 30 mins after the initial boot to reboot. Problem remains after multiple flashes.
[Vibrant Android Development] gonintendo:
He thought he fixed the audio 100% but a few bugs came up.

Sent from my Samsung Vibrant running Whitehawkx's gingerbread.
[Vibrant Android Development] Demiurgic:
I noticed this too last nite. Mine works now so let me check if some of the build.prop edits I did fixed the camera.
[Vibrant Android Development] DonutYankee:
Audio works fine for me. Aggressive setting seems to have helped a bit.
[Vibrant Android Development] andROIDS:
This is a total noob question, but how do you tell if you have a memory leak?

Sent from my Whiskey powered rocket.
[Vibrant Android Development] yvliew:
so how does this compare with CM7?
[Vibrant Android Development] C-4Nati:
Well ****, i need to go back to another rom from this and my laptop literally bit the dust last night. since i cant odin or see clockwork is there any other way to flash a diff rom? rom manager or darkys app?
[Vibrant Android Development] ozmulti:
THis is So fricking amazing. Wow, we will have stable gingerbread soon :D
[Vibrant Android Development] Demiurgic:
you can try to flash thru rom manager but if something goes wrong then you will be without a phone:eek: This rom is pretty stable minus a few bugs no ril resets or anything crazy maybe you should just hold off flashing until you can get a computer.
[Vibrant Android Development] C-4Nati:
Thanks. Holding off for a few more thoughts on it
[Vibrant Android Development] buddahlou:
This ROM is solid even in it's BETA stage i used it from it's release date and have been really pleased with it :-) I only switched out because vacation at work ended and i need GPS :-(
[Vibrant Android Development] xsteven77x:
If you NEED a gps what are you doing with this phone ;) j/k :)
[Vibrant Android Development] Demiurgic:
Seems that memory issues are to blame for camera/gallery/music with lockscreen issues. If changing the process management with spare parts works for you then great consider yourself lucky. For everyone else go into /system and edit the build.prop

half-way down the page change

dalvik.vm.heapsize=64m

to

dalvik.vm.heapsize=[B][COLOR="Red"]48m[/COLOR][/B]

and reboot

When you change spare parts make sure you reboot. No need to change memory if you dont have to.
[Vibrant Android Development] theyownus:
Just did this using root explorer. it was after a fresh reboot so not other changes, i rebooted and now im stuck with BLN on and no response except long power press to reboot. any suggestions? I just got this all reinstalled and set up with beta2...

I might also add that im on a computer which will not recognize the phone using ADB (work pc)

I did save the previous build.prop so i will attempt to get ADB running again to delete the new and rename the build.prop.bak file. any other quick suggestions?
[Vibrant Android Development] Demiurgic:
Try to reboot I guess I used root explorer to change mine up to 128 and back with no issues. adb is just a jar file I think. Programs like super one click and apk manager come with it. If possible you could download adb then nav to the dir in terminal and run adb from there. heimdall comes with usb drivers - not sure how your security policy is setup.
[Vibrant Android Development] phonepersonality:
Crashed phone. Wiped SD-Card.

ODINed back to stock.
[Vibrant Android Development] genaropr:
Flashed it and giving it a test drive, up to now running smothly great job.:o
[Vibrant Android Development] C-4Nati:
Finally back on bionix. Honestly I think its faster than this rom
[Vibrant Android Development] cashyftw:
This worked for me, thanks.
[Vibrant Android Development] lightninbug:
OK for going back to a different ROM, the OP states, "2. Make sure you have the update.zip on your internal sdcard for clockwork recovery".. I grab the update zip for the Vibrant still right?
[Vibrant Android Development] theyownus:
adb saved me :) I used a coworkers personal laptop (he wanted me to help him root his GS4g anyways) i was able to get the phone back working. strangely when i pulled the edited build.prop file that i placed it was blank??? so i just renamed the .bak file root explorer auto made and pushed it. everything back to normal now.

oh and btw this vibrant running 2.3.2 blows the GS4G out of the water!
[Vibrant Android Development] theyownus:
something that may be causing the bricks people are getting is restoring backups from 2.1 or 2.2 just food for thought. i would not restore any system files from an earlier Android build and would be very selective/carefull about restoring application data unless its very important. might be a good idea to add this to the OP

FYI: I was able to successfully restore sms, call data, but not bookmarks using mybackup pro
[Vibrant Android Development] darkknight49:
Same here. This is pretty sweet so far.
[Vibrant Android Development] joe.kerwin:
Did this in root explorer and didn't work. Music stutters when it sleeps by itself requiring reboot. Running pretty well otherwise
[Vibrant Android Development] darkknight49:
so far, the most annoying thing is the email and status bar processes keep freezing on me.
[Vibrant Android Development] lorddart:
So i believe white said he found gps fix yet in the op and changelog post they both say Gps is broken and are looking into fixing it. Seems conflicting reports. Anyone able to tell me whether it works or not if so i will flash this baby
[Vibrant Android Development] Whitehawkx:
Unfortunately no GPS fix. I changed the permissions of the files in /system/vendor/bin I believe to RWXR-XR-X and it will get the gps icon to flash for about 5 seconds but then it crashes. Looking at the logcat it seems to start just fine but then runs into a polling error. Been playing with it off and on since posting this but still haven't had any luck. I know Demiurgic has been looking into this as well. I believe the GPS can operate if we can just find out what the issue is. Hopefully we can track it down.
[Vibrant Android Development] mr.orange303:
Had issues getting back. Rom had issues rebooting.

Had to reinstall drivers for odin. The whole shaboodle.

Finally back to ginger clone R2.

Thank heavens for R2.
[Vibrant Android Development] silox2000:
Double Rainbow! WHAT DOES IT MEAN?!
[Vibrant Android Development] jellette:
I think I'll dig in to this too and see what I can fix.
[Vibrant Android Development] hazard99:
IT Just means the screen spaz's out and rainbow colors appear.

I love the speed. Id love to stay on the gingybread.
[Vibrant Android Development] Demiurgic:
same issues with supercurio test kernel - calls/buttons. Recovery works but due to the double rainbow my vibrant is overcome with joy. The only way I can confirm recovery work and use it is with androidscreencast

- linda's a chipmonk lol

- no lag with quick boot commands

- home/search are completely broken they just thing they are a cursor or something. moves map/text cursor
[Vibrant Android Development] STiGLOGiC:
Flashing now to test bluetooth. I will report back after I randomly call some people here in the middle of the night and listen to some music.
[Vibrant Android Development] eugene373:
Not sure if this was posted, but here it is anyways to be able to use the phone..

http://code.google.com/p/toggleheadset/downloads/detail?name=ToggleHeadset.apk
[Vibrant Android Development] hazard99:
Is the camera apk different than the one we currently have? the night mode seems to work better for me
[Vibrant Android Development] Demiurgic:
edit: To get home/search working go into system/usr/keylayout/melfas_touchkey and change D-PAD LEFT to HOME and D_PAD RIGHT to SEARCH.
[Vibrant Android Development] STiGLOGiC:
Bluetooth is working flawlessly on my device. I tested stereo for music first, and I am currently in a call as I type this.

EDIT: Also swype is not working. At least not in english(any version). Managed to use ROM manager to flash clockwork mod for Nexus S to flash another version of swype, but bricked on reboot. Had to repartition to make ODIN flash stock firmware. Flashed this a few more times trying different things all ending in bricks. Fixing permissions from ROM manager will also cause a brick(for numerous reasons, I'm sure). In any case this is a good start. Can't wait until this is in beta stages. If you need anything else tested, I'm always happy to brick my phone a few times for the cause.
[Vibrant Android Development] nakagusukumike:
hahaha you obviously haven't seen the video.

youtube. now. that's an order!

http://www.youtube.com/watch?v=OQSNhk5ICTI

also:

http://www.youtube.com/watch?v=OQSNhk5ICTI

But on a serious note:

GPS Fix working for this?

Which is more tolerable CM7 or this?
[Vibrant Android Development] nakagusukumike:
Can someone confirm if the full Bluetooth stack is included and Wiimote's work with this?
[Vibrant Android Development] Dan_Brutal:
Wow. Great job whitehawk. I went to bed with froyo, and wake up with ginger. Woot!
[Vibrant Android Development] epakrat75:
CM7 ATM IMO but that will change.
[Vibrant Android Development] Rawat:
Swype fix

Voodoo lagfix - Has ext4, and easy root (install apk from market) Does not have voodoo sound, colour or anything else.

Screen lock anim

cfroot it's recovery 3e at the moment. Flash using ODIN.

Coloured reception/wifi/3G icons for when fully connected to Google's cloud stuff

Browser is unstable. Use Opera or something else. It will crash, and often make a "POWER RESET or UNKNOWN UPLOAD MODE" screen come up.
[Vibrant Android Development] Br1cK'd:
Fan-freakin-tastic!

Sent from my Loki powered Vibrant via the XDA App
[Vibrant Android Development] apollo15rover:
Agreed, Alienz!

Samsung's release of Froyo was just as awful - that was what caused me to come to XDA finally and try custom..

I love Samsung - nicest piece of hardware I've owned.. but they just don't have sw /fw development down.. and I don't think they care

. . they're out to sell machines at a profit. At least now it seems like they're wizening up to this and starting to get out of the way..
[Vibrant Android Development] Demiurgic:
swype beta works just fine...lol no need to odin cuz of swype

Edit: nevermind fcs on reboot
[Vibrant Android Development] Whitehawkx:
Update coming. Going to include ToggleHeadset.apk (thanks Eugene for pointing this out!) so calls work normally and going to correct the button mapping (thanks to Demiurgic for pointing this out!).

Also will include working swype and GB launcher. That will move this into beta seeing as pretty much everything works except entering recovery. :)
[Vibrant Android Development] Rawat:
Might as well add the modified framework-res which has the screen off anim.

Oh, and voodoo.
[Vibrant Android Development] Whitehawkx:
Adding modified framework and was going to test voodoo. Thanks to you for pointing out all the other fixes! :)
[Vibrant Android Development] joe.kerwin:
Do we have to download nexus S cwm to revert? I have the update zip on my SD but when I tried to flash a ROM through RM it sat on rainbow for 20 minutes. The minute I hit power it rebooted still on 2.3.2. So it must've not gotten into cwm. Whitehawx can you confirm if we need the nexus s version? It's the only option when I select "flash cwm" in rom manager
[Vibrant Android Development] Thismines:
FAST!!!

this ROM is awesome, and its still in beta :D keep it up, will be donating on payday!
[Vibrant Android Development] wizern23:
My gps works. It locks on almost instantly at my house. Theres a slight lash with the maps app though.
[Vibrant Android Development] HRodMusic:
After using it all night.. i found alot of bugs.. far from daily driver.. but this is a dam good start! Whitehawk u are amazing!
[Vibrant Android Development] one4house:
What did you do to get it working? Are you sure you don't have WIFI sharing on, and it is just getting your position from that?
[Vibrant Android Development] joe.kerwin:
Anyone?
[Vibrant Android Development] joe.kerwin:
That's the case there's no reason his would just work
[Vibrant Android Development] Whitehawkx:
I used the update.zip specifically for the Vibrant.
[Vibrant Android Development] one4house:
Is there a way to add the MIC icon to the swype keyboard for quick access to the Speak-to-text function?
[Vibrant Android Development] ronnieb00:
Same problem, boot loop with chipmunk linda and double rainbow heaven, how'd you get it running? Did you odin/re-flash or is there a simpler way?

TIA
[Vibrant Android Development] deeznutz1977:
Google,android screen cast and download. that will let u see recovery from your computer. that way u can see what going on look at the pic it will explain better
[Vibrant Android Development] hitman818:
I had the same boot loop as you. I think its because I cleared the cache, because when i cleared tge cache, it said e:dev block no partition, something like that.
[Vibrant Android Development] alexrz619:
Vibrant ginger

so i did the up date .....and i know it says to be patience and it will boot but i think mine might be bootlooping.....it boots and does the chimpmunk noise goes to the crazy rainbow screen then just reboots?? is thatr wha its supposed to do its been 10 minutes
[Vibrant Android Development] yb2fast:
First off thanks fot the awesome work .so far only problem I have our have had is music through 3.5 jack.havent tried head phones yet but I use this In my car to the radio. O one other thing,,, can you install unlock draw gesture ,i used it on cm7 and really liked it
[Vibrant Android Development] alexrz619:
i was on a nero rom 2.2.1
[Vibrant Android Development] xsteven77x:
I wanna try this so bad but my phone is PERFECT the way it is right now, and i have heard alot of stories of the hell people went through trying to come back from gingerbread. Does not seem to be TOOOOO hard to flash to another rom, but have not read too much of being able to restore back to a previous nandroid backup that easily...
[Vibrant Android Development] ronnieb00:
I didn't clear cache, followed OP guide to the letter, but no worries. How'd you fix it? Looking into screencast now...
[Vibrant Android Development] ronnieb00:
I got the same problem, and seems like a few others too, but haven't been able to get an answer as to how to fix it.

Just Odin-ed back to jfd, will try again and report back. Hopefully just a bad flash, but with so many cases...?

White any thoughts? Thanks a bunch for working on this as well.
[Vibrant Android Development] Whitehawkx:
I'm curious what is causing bootloops for you guys as well. You aren't by chance coming from the dead horse kernel are you? Cause I can see that causing issues (boot loops, wiped sdcard, ect). I tested flashing from stock JFD and from voodoo enabled KB1 and both went through no problems. I also tested reflashing this build with it already on my phone and flashing from this build to KB1 with voodoo kernel and both worked no problem (following instructions in OP to the letter on both, but you already said you did that). Could you tell me what rom/kernel you were running when you tried flashing?
[Vibrant Android Development] hitman818:
I first had cm7, then went back to stock and flashed this rom. Could it be the wiping of the cache. It was giving me errors or something on e: partition.
[Vibrant Android Development] turbosix:
just chiming in to say i bit the bullet and flashed this this morning... no issues whatsoever other than what is in the 1st post.
[Vibrant Android Development] cashyftw:
Just reporting (flashed yesterday night) Battery life was pretty bad, idk if I did something, but I played music in my car, and when I sat down in class, my battery was at 88 (from 100) weird 10 min drive to school, and through out the day it finally ended up dieing. I was using xda, and sending text just in case anyone was wondering what I was doing. I LOVE this rom though, it was super freaking fast!
[Vibrant Android Development] jcc332006:
Yes I experienced the same thing coming from CM7. I flashed the 1st beta without a hit. Flashed CM7 repartioned as instructed in the CM7 thread to flash another rom tried to reflash Gingerbread beta again and kept getting the same message you're referring to as well as being kicked back to recovery menu. I'm wondering also if flashing CM7 and then attempting to flash gingerbread beta maybe causing the conflict also. :confused: