yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] ludachez:
I dont think the OP doesnt believe us about our recovery issues, its just how can he fix a problem he isnt having? I flashed this ROM through CWM over AOSP1.4 (ji6) and im having the recovery problem, but also have the larger NAND chip, not hardware locked. If you have the recovery issue, you can do what i did to get back to flashing whatever you want. Odin the stock jk2 rom and when its done it takes you to stock recovery, and if you flashed CWM before when you hit reinstall packages it should go to CWM where you can restore or reflash or whatever. at least thats how it worked for me.
[Vibrant Android Development] ohnoezmahfone:
I'm really happy this ROM fires does *not* enforce Exchange remote administrator rules. It's crazy annoying having to use a numeric lockscreen just to get my work email on my phone.
[Vibrant Android Development] anthonys2r:
Anderdroid: Any ETA on the next update?
[Vibrant Android Development] brew1brew:
First off THANKS this ROM is great!

I have a question about recovery, for you or anyone that knows. I flashed this over an ASOPish 2.1. every thing worked fine, but I decided to flash the SDfix.zip and went to rom manager and said to boot into recovery. BOOM soft Brick! So I Oden'd back to JKD and then I found that instead of re-rooting all I had to do was boot into recovery and reload files and clockwork recovery cam up and I restored my Nandroid.

So how am I suppose to go into recovery? since I found that the update.zip (clockwork recovery) was still there, how do I get E2 recovery loaded? or do I just manually boot to recovery? and not use Rom manager? I don't want to brick it again.

Also when was I suppose to flash the SDfix.zip? this time I flashed it right after flashing 1.1 before rebooting. but when I plug the phone into the computer the ext SD shows up as 2.2 gig not 16 gig.

Again great ROM, awsome work. I hate TW and love ASOP/ADW!

Les
[Vibrant Android Development] trilaxx:
Error

OK as much as i love AOSP and the work u have down im off thos rom tell i feel things are safe.

I set the phojne on my desk went to piss and came back and the phone had a black screen wiht yellows words that said Kernal panic and erroe 0x00 5 times in a row. Which usaully means a bricked phone.

I pulled the battery and reboot the phone and things are ok, but ive never had this happen with any rom before.

If its not the rom thats did this, well thats great but to be safe. ill be back when i fell its save.

Thanks for all ur hard work and effort, hope to be back soon.

PS, was to much in a panic to take a pic if it happens again i will.
[Vibrant Android Development] mulcahyd:
Hey. The rom flashes perfectly. Even with clockwork recovery no issues. I flashed it and applied the lag fix. Easy as cake.
[Vibrant Android Development] querjh:
I flashed 1.0 and 1.1 without any problems. I have flashed to other ROMS since and came back to this ROM. I haven't had any problems, I mean not one problem, everything works perfectly. I flashed via CWM (premium version) every time. I also re-install apps via Titanium premium version.

Great ROM!!!!! Can't wait for the next update :)
[Vibrant Android Development] murse:
I've followed pretty much this same protocol and don't have any major issues. I finally got wifi calling to work by using a different router at home. The battery life is not great, but it's no worse than 2.1. I see high CPU usage from the wifi calling app and the kswap0d system process, but overall it runs pretty smoothly.

Looking forward to the accurate battery mod.
[Vibrant Android Development] gaore:
Hi, op. Is the wifi calling UMA based? Thanks
[Vibrant Android Development] msw1382:
I will second this 100%. This ROM has been flashed over everything on my device.

Great work Anderoid. I don't know what else you can do to make this ROM better but I await your next update.

PS. How do ya feel about our Steelers this Sunday? Might be rough!
[Vibrant Android Development] murse:
Wifi calling is similar to UMA except there is no handoff to the cellular network. If you lose the wifi signal, you lose the call.
[Vibrant Android Development] gaore:
I can not install the *.zip file.

error: can not open e:sdcard/*.zip
[Vibrant Android Development] parmijo11:
Its uma lite meaning it doesn't support handover to network, so if you leave your wifi while on a call expect it to drop.
[Vibrant Android Development] customyota:
+1. Again. This is one of only two bugs that have given me any problem with this ROM. My wifi will not stop running when the phone is sleeping. Besides the screen, it's my biggest battery draw since I use it for much of the day. I can still last the whole day without recharging, but I think it could do much better if this were fixed. The other bug has to do with the wifi as well. It fails to turn on more often than not and just says 'error'.
[Vibrant Android Development] kennyp987:
Fantastic job anderdroid...this rom is probably the best one i ever flashed...so smooth and loads of eye candy.

Vibrant + aospish 1.1 + oclf
[Vibrant Android Development] ram130:
Smooth so far.. just a quick update.. battery draining issues are due to wifi calling.. kswap and drm constantly using CPU.. anyways I just flashed this new kernel and so far things are better.. ill keep yall posted..
[Vibrant Android Development] ram130:
No issues with Chrome to phone here!
[Vibrant Android Development] JD76:
For the ones here, me included, who have no luck getting into recovery via Rom Manager, can anyone offer us advice on how to so we can flash an update or another rom? Is ODIN to stock the only way out?
[Vibrant Android Development] msw1382:
Explain the steps you have taken to attempt to get into recovery and what happens when it fails.
[Vibrant Android Development] stephenj37826:
Yes I'm using eugenes 805 right now and love it. I am using xans uv ui as well.

But you can't use core on it. Its a 2.1 kernel. I like to oc/uv but I don't uv @ 1 ghz or above. I use .50-.75 on the lower clock speeds. I also set a profile in setcpu for temp. If it goes over 104 f It underclocks to 800 mhz. I don't have a problem with that but I just do it to be safe.
[Vibrant Android Development] androidcee123:
For me.

1.) Downloaded the file

2.) Connected the phone via USB.

3.) Transferred file over to the root folder of my device.

4.) Using ROM Manager, I selected the option to "Install ROM from SD Card."

5.) The phone reboots into CWM.

6.) The app runs for a few seconds then I get an error message that it can't open the file from sd card.

This is what continues to happen to me. Am I missing a something..?
[Vibrant Android Development] JD76:
For me - just starting Rom Manager and hitting either "install rom" or "reboot into recovery" or "backup current rom" yields me a frozen Vibrant screen. It just doesnt boot into recovery.
[Vibrant Android Development] teknx:
Same here. I can't even get into regular recovery.

For those of you who are stuck in the Vibrant bootloop

Try to plug in your usb cable and type "adb reboot" to get back into android.

It works for me, instead of having to Odin.
[Vibrant Android Development] diaa08:
Have you done the install recovery, reboot into recovery thing? That should take you into stock from where you should be able to reinstall packages and then be in clockwork recovery. Maybe that it's where we are miscommunicating, because at least I never ask clockwork app to install anything but rather do it from actual recovery.

EDIT: just saw what you are doing, have a quick question, because something always yields the same error for me is: copying file to external sd, then copying that over through astro or root explorer to root of internal sd; not sure why but always screws up zip file is that what you are doing? If so just copy straight to root of sd from pc solves it.
[Vibrant Android Development] diaa08:
Have you tried redownloading and reinstalling recovery?
[Vibrant Android Development] secularhuman:
I got the courage to flash my first (this) ROM

yesterday and WOW am I impressed.!!!! Was on 2.1, but this is stable and pretty.

Glad I didn't wait for the official t-mobile ota.

I'm using the usb tether to link to the internet right now and it is easily as fast and smooth as my home cable line.

Thanks, thanks, thanks

ps; it would be nice if this thread only had technical stuff and solutions in it. 700+ messages make it pretty hard to filter just the needed info. Thanks

Secular
[Vibrant Android Development] teknx:
Possible fix for the Clockwork recovery issue

I installed the ROM today and experienced the same issue a lot of people were complaining about, i.e. not being able to get into recovery at all and getting frozen at the vibrant screen.

For those of you who can still get into Froyo.

Download busybox installer and after busybox has been installed (needs root) reboot normally by pressing the power button and choose reboot.

When your back in froyo, open up Clockwork and choose the Flash ClockworkMod Recovery option and select Samsung Vibrant (even if you did this before, do it again, just to be on the safe side)

then choose "Reboot into recovery"

It should reboot to the Vibrant screen, wait a little, some text will pop up and it may restart again. Leave it alone, then it should go into the 2e recovery.

Choose reinstall all packages, and hopefully the Clockwork recovery will come up.

Let me know how it works out for you guys.

For those of you who can't get into Froyo and are stuck at the Vibrant screen, you might be able to get back in without needing to use ODIN.

If you have the adb installed, plug in your USB cable while still on the Vibrant screen and open up the console in windows and type "adb reboot"

It should reboot your phone back into Froyo.
[Vibrant Android Development] jtc442:
Recovery issue

I actually finally had the recovery issue last night and then again this morning, several times. I started flashing different roms last night, like masters new release, and when I tried to go into recovery, I got (error 7: no bitmap image or something), 6 lines that said that, then it said in yellow, finding update, and stayed right there. I couldnt even go into stock recovery, and the phone wouldnt boot. Had to odin several times and start over. I played with it some more this morning, and installed master rom again, then reinstalled clockwork through rom manager, and got the same errors. So, odin again. Tried it all again, except this time, I installed clockwork mod from rom manager again, and after it was done, I rebooted the phone and let it boot up fully, then powered off and then tried to go into recovery, and it worked flawlessly. Did this several times, and still working fine. This might not work for everyone, but it did for me.

NOW, by saying all of this, everyone can quit saying its Anderdroid's rom, because its not, something else is causing this.
[Vibrant Android Development] androidcee123:
Actually, I have tried installing directly to the sd card and flashing via the stock Sammy recovery using the reinstall package method...no dice. I am basically lost. I do have a quick thought though:

Maybe I have to wipe, which I admit I have been scared to do since it didn't install the first few times, but I just don't know.

As for the file, it is directly on the sd card, not in a folder. Maybe I have to learn the Odin thing, but being an former G1 person then MTGS, my experience is limited.

Thanks for your time dude.
[Vibrant Android Development] mikeku:
in original samsung recovery just select reinstall package and you'll go into clocwork recory, asuming you've already select to boot into recovery from bootmanager... enjoy .... life is short....
[Vibrant Android Development] tjsynkral:
This rom is awesome and it'll be my choice for a while.

One issue though: The battery full notification plays the FULL RINGTONE when it comes up. If my battery is fully charged at 4 in the morning, the full ringtone plays. Is there a way I can fix that or can it be fixed for the next build?
[Vibrant Android Development] EyeAndroid:
Wow guys,

Im just amazed as to how many people are having problems getting this rom loaded. It booted right up for me. So far so good & huge props to the devs on this. Question though, and I hate having to post this as im sure its been covered - but search literally does not work on this issue (go ahead and try).

Every link I click on in the stock browser will give me an error of "No network connection" blah blah - but it will continue to the page im looking for. I just have to click cancel. So at this point its more of an annoyance than anything else, but is there a fix for this?

I haven't tried another browser, because I was hoping there was a fix.

Thanks.
[Vibrant Android Development] deku_nut:
Hat's off to you devs, this sucker is awesome. Daily driver for me. I've been dying for a close-to-vanilla android since i switched from mytouch3g to vibrant.

Just a note: I used the circular battery add-on (THE APK, NOT THE MOD) and it works like a champ and provides more accurate battery levels. Primo battery life on my vibrant too.

thanks!

for those curious: Circular battery status http://www.xda-developers.com/android/circular-battery-status-for-android/
[Vibrant Android Development] setrepaca:
Vibrant AOSPish JK2 v1.1 vs Eugene_SD+2E_JK2_Froyo Download

Yes this worked for me! So I think there's issues putting the VIBRANT in recovery mode after installing as per this posting XDA's showthread.php?t=832532. I gotta say, I was quite pissed off at the fact that my VIBRANT was working so flawless and I mean for everything save for the SD thingy which I wanted to apply and haha, couldn't get into recovery mode to load from SD.

Anyways, now I resorted to using XDA's showthread.php?t=833024. Its still froyo but with the ugly additional laggy bunch of t-mobile apps grrr. I now have OCLF v2.0 on there working good quandrant went from 954 to 1960 not bad, its very stable and the SD is working too, renamed to External_SD but I don't care. I hate how slow SAMSUNG is when releasing updates its almost end of 2010 that company needs the spanks!
[Vibrant Android Development] Anderdroid:
Did anyone with the recovery issue try the 'install busybox' method in the post above? Can more people report if this is fixing it? Busybox should be installed with this ROM so it's weird.
[Vibrant Android Development] enuro12:
While it is possible it is not his rom, i'd love to know what it is?

This is my first ROM i've ever messed with. I followed the tutorials to root, them load the rom right from this set of posts. So nothing has touched my phone besides this rom and stock.

I've since moved on to macnut to see if the CWM would work and it does fine.

I've clicked the top button in CWM where i select vibrant a dozen times. And subsequently became familiar with adb.

While i may be a noob, to say its not the rom seems ridiculous.

Flashing back to 1.1 and trying it now.
[Vibrant Android Development] enuro12:
I followed this, and it worked! I can now get into recovery!
[Vibrant Android Development] enuro12:
Rebooted then went back to CWM. Installed the SD_Fix. Rebooted

Busybox defiantly fixed the problem.
[Vibrant Android Development] t1n0m3n:
Odin'd JFD, root, rom manager'd this on. Looked good until a reboot. Couldn't even reach recovery. Had to start over with an Odin of JFD. As much as I would like to run an AOSP looking version of Froyo, I won't be loading this version again. Running Bionix right now with no issues.
[Vibrant Android Development] secularhuman:
Is flash player supported.

do I need to download 10.1 from the market or is it included in the Rom?

web videos take forever to load and playback seems to FC the included browser.

(I have searched for the answer but Flash brings up almost every post.)
[Vibrant Android Development] enuro12:
Busybox fixed this for me. However i flashed over Macnut R10. So maybe R10 fixed it. I'll Odin JFD then do it all again.
[Vibrant Android Development] invisiblemonki:
goot

sitting here waiting for all the fancy ROMs to get updated and installed this in the meantime. wow, i'm really not flashy, cause this is great. my phone works. it's functional like android, but not crippled like samsung. i now understand the design aesthetic that keeps this mod going. i love my phone again. please keep up the good work.
[Vibrant Android Development] Zeno78:
uninstalled OCLF to flash SD_Fix.. and stuck back at the vibrant screen... instead of choosing the zip in ROM manager i just told it to boot to recovery. guess its ODIN time again
[Vibrant Android Development] Zeno78:
work'd the easiest when trying to get into D/L Mode... Going to give up on this MOD until next revision... going to see what Bionix Obsidian V2 is like.. was extremely happy with Bionix 1.5....
[Vibrant Android Development] parmijo11:
Been rocking 1.1 for about 24 hours with no issues, can boot into recovery and battery life is not so bad. Nice job!
[Vibrant Android Development] JD76:
YES!!!! It worked for me too!!! Thank you!!!
[Vibrant Android Development] JD76:
The busybox trick worked! Thank you soooooo much!
[Vibrant Android Development] DonutYankee:
No idea where people are having all these issues with recovery. Did I get lucky or something? I followed the generic flashing instructions and everything works great for me. Battery life has improved, too.
[Vibrant Android Development] Anderdroid:
You're on your own with those kernels. Those are i9000-based kernels I think. They may or may not work.
[Vibrant Android Development] ram130:
Ok not bad so far.. I've see some lag here and there but not posting it on anything until another 3 reboots...I only found one bug so far and thats with the signal bars when Wifi Calling is enabled:

I usually have 3 or more bars..
[Vibrant Android Development] Anderdroid:
This is because WiFi calling pretty much disconnects you from T-Mobile and uses your WiFi as service.
[Vibrant Android Development] azn_kendy:
good job !!!
[Vibrant Android Development] ram130:
lol I just realize that when I disabled it! LOL o wow..total wifi calling newbie :D
[Vibrant Android Development] ram130:
liking it so far.. I think this rom is trying to restore all my app automatically!! Last time I saw that was with my nexus one !! :eek::cool:

EDIT: false alarm.
[Vibrant Android Development] aczarney:
Backed up, flashed, and booting now....

EDIT: Holy ****. This rom is fast. I think I'm in love. My only question is if we can change boot animations (I miss "Millie" from Bionix Fusion 1.2, ha).
[Vibrant Android Development] redwolf313k:
Yessss ander wooo!!!
[Vibrant Android Development] ram130:
And for those wanting to know..THIS HAS NOT WIPE MY INTERNAL SD CARD ..coming from 2.1 to 2.2 ..nice!
[Vibrant Android Development] explodingboy70:
Word of caution I flashed one of Eugenes Kernel over the Obsidian Rom and everything went to pot. I've since had to ODIN back to stock and lost everything in the process. It wiped everything on the internal SD. I'd wait for a stable OC Kernel based on this one.
[Vibrant Android Development] ram130:
Everything is great so far..Just need a H icon and black notification bar morph with a circle battery mod and I'm good!!

Restoring all my apps now
[Vibrant Android Development] DonutYankee:
Just flashed and giving it 5 or so minutes to chill after first boot and then I'll reboot it to be safe.
[Vibrant Android Development] ram130:
nevermind..figured out it ..system/app
[Vibrant Android Development] ram130:
Well here is something weird. I just rebooted and notice these 3 apps AUTO UPDATED or install their self..
[Vibrant Android Development] DonutYankee:
Auto updates turned on by default I'd guess.

Request: Galaxy S i9000 camera app. This stock one...eh...it's kind of bad. I think we can all agree the camera is where we can go with Samsung's version, especially considering it's just a camera app and not a big UI interference.
[Vibrant Android Development] Anderdroid:
That's normal for Froyo to auto update system apps I think.
[Vibrant Android Development] ram130:
anyways I'm tired..mid terms tomorrow..plus i got to work out..so lata everyone!! if I have any issues I'll report them tomorrow...so far battery seems good!
[Vibrant Android Development] ram130:
Figured that would be it. Just never thought auto updates was on by default :D you usually have to enable that in 2.2..anyway nice touch..anyone have any issues so far?
[Vibrant Android Development] DonutYankee:
Oh snap, that's the T-Mobile shutdown animation. Didn't see that coming.
[Vibrant Android Development] ram130:
Stereo Bluetooth streaming, controls working great and loud too.

Caught me too :D ..it's great actually
[Vibrant Android Development] enuro12:
Alright i've confirmed it :)

Odin back to Stock

Rooted

Installed CWM Rom Manager

Flash to AOSP

No problems

AOSP loads

Reboot into Download from CWM

Freeze at Vibrant Screen....

ADB Reboot

Install Busybox

Reboot into Download from CWM

Works!
[Vibrant Android Development] enuro12:
What APK did you use. The kitchen errors out every time i try to make it.
[Vibrant Android Development] ytleinad:
ok well thanks for this ROM, it looks nice.

I cant really get into recovery though unless I reflash through Odin.

And I'm having a problem where I cant download any apps from the Android marketplace for some reason... I need stuff like google voice/handcent/yelp etc...

It always shows 0 space for application storage and Android always says not enough space to download apps.

After flashing through Odin again this is the only ROM I can load... no others will boot It just gets stuck after the Galaxy S logo after the tmobile flash screen ding ding ding ding ding.

Any help appreciated! (Just want marketplace to work on this ROM)
[Vibrant Android Development] enuro12:
Clear your cache in the Market (market FIx)

Install busybox (recovery fix)
[Vibrant Android Development] ludachez:
So just reinstall busybox and i can get into recovery? cause i have the recovery issue as well. and what busybox are you using to install? from market? from a site?
[Vibrant Android Development] ludachez:
IT WORKS!

Enuro12 you are AWESOME. i downloaded stericsons busybox installer from the market, ran it, flashed a new CWM and then manually rebooted into recovery for the first time with this ROM. thank you for figuring this out now i can make backups and try other kernels...so thank you.

Edit: i hit reinstall packages and it didnt work it just went back to 2e but i hit it again and then got CWM. might happen to others so just try again
[Vibrant Android Development] ohnoezmahfone:
I haven't experienced this, but if I had to take a guess at how to fix it:

I had the very loud t-mobile ringtone at startup/shutdown. I did adb shell and went into /system/etc/audio/ui/ or something like that, and renamed the files from startup.mp3 to startup.mp3.backup or whatever (mv oldname newname). I would guess that battery full sound file is in the same location?

Sorry for the handwaving, I don't remember the exact path or filenames but that should be enough for you to find it.

I had to install 10.1 from the marketplace. Flash is very usable once you do, though.
[Vibrant Android Development] enuro12:
From the market. 1.17.1
[Vibrant Android Development] ytleinad:
Thanks a lot but when I go to clear cache in manage applications --> market, it won't let me because the cache is 0 bytes (not an option to tap it). Still getting no space when I try to download.

I figured use clockwerkmod to free up 512mb for apps but of course when it reboots to recovery, recovery wont work (Can only Odin to start from scratch again after I do this)

Busybox people online are giving different instructions, the easiest one I found so far was to stick busybox and installbusybox.sh onto the root of my sdcard, then unmount, adb, su, sh ./installbusybox.sh, which after doing gives me an error message: mkdir: can't create directory 'system/xbin': File Exists.
[Vibrant Android Development] Anderdroid:
It's confirmed then. Install busybox from market to fix your recovery. Added to OP.
[Vibrant Android Development] xitsxjack:
badass, busybox fix worked for me!! THANKS EVERYONE!!!
[Vibrant Android Development] ripsphone:
Busy box did the trick indeed.