yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] mulcahyd:
Im not using any extra kernals, im using the default kernal came with this rom.
[Vibrant Android Development] Zeno78:
interested in the kernel for OC via setcpu or auto like in that kernel... just curious if anyone is using an OC kernel?
[Vibrant Android Development] customyota:
I noticed one other person had this issue, but it was never discussed. My wifi remains running even when the phone is sleeping. I can't get it to turn off regardless of the sleep setting. Any ideas?
[Vibrant Android Development] krazykidd:
Well guys, good luck with the vibrant froyo firmware. I'm currently hardware locked and bricked down (download mode failed). Currently spent 50 dollars to go make myself 5 of those USB jigs in case anyone wants to buy one, just PM me. Hopefully I can get back into download mode to throw back JI6 and then JK2.
[Vibrant Android Development] player4lifeov:
My problem is this. I can get into download but I can't get Odin to read a com or recognize that my phone is connected! I'm really frustrated at this point. When i turn the phone on like normal and have Odin open it reads the Com or whatever. SO i then adb reboot download and it goes into download mode and then Odin no longer finds or recognizes phone. Can't access recovery, hence why I'm trying to Odin, phone does start up but I want to be able to flash whatever i like. Can anyone please help.
[Vibrant Android Development] eniac325ix:
Wiimote still will not work on mine with this rom. Says no device found same as it did stock so no fault to this rom. It works fine on my Cliq and G2 which both have physical keyboards...go figure.
[Vibrant Android Development] DonutYankee:
Have you attempted to reinstall the USB drivers?
[Vibrant Android Development] player4lifeov:
Yup, more the once to
[Vibrant Android Development] stevewabc:
Yaa I think I'm staying away from this one for now in tell the recovery problems get fixed :( you do have a nice rom and I do like it a lot but for now I going back to Macnut R11 witch will be out tomorrow....
[Vibrant Android Development] mattb6288:
i did that and it is still really off
[Vibrant Android Development] mulcahyd:
Ill be staying on this rom for awhile. Thanks.
[Vibrant Android Development] androidcee123:
A bit mixed up here

I have tried for a few days to flash this ROM with no luck.

I have used ROM Manager, as well as Clockwork to no avail. Every time that I attempt to flash I get error message stating that the patch can not be opened from my sd card. I have read through the thread but have not seen THIS problem.

Any thoughts would greatly appreciated.

BTW, I am rooted via the one click root method, no lag fix installed, running stock JI6.

If you have any thoughts, please let me know.

Thanks.
[Vibrant Android Development] JD76:
Not hearing from the developer while all these problems are being posted is troubling. Hopefully he's too busy fixing the problems
[Vibrant Android Development] androidcee123:
Agreed, however just reading through the thread for the last couple days while fruitlessly trying flash the ROM, I did come across him stating that he was working on an update.
[Vibrant Android Development] mikeku:
when you get to the recovery screen just hit apply update packages ... it will take you to clockwork recovery mode....
[Vibrant Android Development] DonutYankee:
You know guys, you flash at your own risk. The people who make these ROMs have lives, too.
[Vibrant Android Development] roguly:
Swype

anyone tested out the swype keyboard? i know the new version is really annoying and was wondering if it was working any better on this rom.
[Vibrant Android Development] Malike25:
I agree with you on this. They build ROM's for themselves & we're lucky to have them share it with us. He'll update it once he has an update & when he has time.

This ROM has been working great for me. I've been using it for the past two days & got 14 hrs 45 min so far with 6% left on my battery. Thanks for a great ROM & keep up the good work!

If you keep having issues I suggest flashing back to stock using Odin & reflashing. I did this twice & it's working great for me.
[Vibrant Android Development] androidcee123:
I definitely agree that we are lucky to have these devs...I go back to the G1, then MTGSlide, all rooted, so I know the drill.

That said, I just didn't see anything concrete on how to flash the ROM. I figured that it was simply a matter of using Clockwork since it wasn't stated that I need to do otherwise.

For me, I wouldn't flash if I didn't think that the ROM was worth, and this ROM is most definitely a keeper!

Keep up the good work and thanks dude.
[Vibrant Android Development] mulcahyd:
I just had one lockup during browsing online. I rebooted and everything is normal. No biggie. But everything else is exceptional.
[Vibrant Android Development] ugokind:
true.. I hope there's a possible fix
[Vibrant Android Development] ugokind:
please let us know hot to go in clockworkd recovery because now it's impossible!!

what can I do with ar rom if it's hardened?
[Vibrant Android Development] stoober:
I think I found the answer to the size of the sd card showing wrong size!

My solution was to remove these files:

Android.secure

Lost.dir

I did this with card out of phone then copied all remaining info to hard drive, put card back into phone then unmounted and formatted card. It then showed up with correct size. Mounted card. Hooked phone up to computer and recopied files back to card and all is well. I know it's a bit much but it worked!!

Just remember remove those 2 files first!!

Froyoness again!! So happy ;-)
[Vibrant Android Development] Anderdroid:
3 words...

adb reboot recovery

Other than that. The only issue I have personally running this is ChromeToPhone forcecloses. I have had 0 recovery issues. I never use 'reboot to recovery' from ROM Manager though. Only Install ZIP from SD card. I usually do adb reboot recovery to get into recovery.

Oh, and 2 more words :p

adb logcat. Punch this in and see where the error is. See what your phone is doing while it's stuck on the bootloop. This is the only way that it will get fixed as I can't produce the bootloop myself.
[Vibrant Android Development] DonutYankee:
Yeah, I've also had the ChromeToPhone issue. That and calendar (when you select Calendars) are the only apps that force-close for some reason.
[Vibrant Android Development] MeasIIDX:
Great work with this rom!

I really appreciate what you're doing for everyone here!
[Vibrant Android Development] anthonys2r:
Does anyone know when Anderoid is going to release v1.2? Really looking forward to the AOSP accurate battery mod...
[Vibrant Android Development] jtc442:
I have not had one single issue whatsoever. The rom installed perfectly with no glitches or hangups. Been running smooth as can be since it was released. As far as recovery. I don't see why people are having this issue either? Boot phone into recovery, volume down to reinstall packages, hit power, you should be there. If not, volume down again then power again. If that don't work, reboot phone, reflash clockwork mod and try again.
[Vibrant Android Development] The K-Zoo Kid:
Does anyone know is this mod works on this rom?

http://xdaforums.com/showthread.php?t=835540
[Vibrant Android Development] Grantisimo:
I've noticed that I can't copy files over USB to the internal SD using Windows anymore. It doesn't affect my 8GB MicroSD. I am, however, able to copy to the internal card using Astro from the external SD.

Other than that, it is so nice to have FroYo back and on a phone that can actually take advantage of it!
[Vibrant Android Development] Fluesopp:
I flashed, and now I can't find my SD card. I tried disabling USB debugging, and the USB setting is set to Media, but I still can't find it. :/
[Vibrant Android Development] ugokind:
yes but

how can I logcat if it boots in a stucked vibrant menu?

now we've been achieved the way to magically return back and alive after that problem.. but the problem persist!

so I reask.. how can I enter in recovery menu if the procedure fails and get the phone brick?

so this make me use Odin .. because there's no way to load a rom .. or itself or a damned update.zip.
[Vibrant Android Development] zoid_99:
I'm not sure if logcat will tell you anything but I could adb shell into my phone when I was "stuck" at the vibrant screen. Try it...
[Vibrant Android Development] zoid_99:
adb reboot recover just goes to a stuck "Vibrant" screen. This is the problem everyone is having. I ended up having to odin back to stock. FWIW you can adb shell into the phone when you are stuck on the vibrant screen. I have no idea if that is useful at all but you can get a shell and run commands.
[Vibrant Android Development] stevewabc:
WOW I got this rom to work correctly :D I was one with problems getting into recovery as well but after 3 days of learning hehehe how to restore the phone to factory, then I just went for it again and BINGO got it working great and I have recovery as well... so the only thing I could come up with is I had a bug from all the past rom flashes... Just my 2 cents..

Love the rom:cool:
[Vibrant Android Development] jlatnyc:
You make it seem so easy. I'd understand if it was 1 or 2 people with issues but it's not
[Vibrant Android Development] cozmicfool:
I actually just flashed this ROM and noticed only two major issues. If anyone can help it would be much appreciated.

1.) Can't connect to google servers. (Can't Sync contacts, connect to gTalk, or Marketplace)

2.) Droping of SMS and MMS text messages

3.) Can't flash any ROMs via cWm after loading this rom. (In all fairness I've seen this happen in the Stock 2.2 rom from Eugene too)

Okay, that was three major issues. lol

Can anyone help? Thanks!!!!
[Vibrant Android Development] jtc442:
Guess I'm just a lucky one then. Are the people that have these issues trying what I, or others have suggested to get into recovery? I'm not saying they aren't, I'm just asking. And yes, it was easy. I've flashed every Froyo rom that is out to date, and have not had any issues with recovery or being stuck on the vibrant screen? Like I said, maybe I'm just lucky?
[Vibrant Android Development] defconoi:
I'm using 1.0 with no issues at all, recovery works
[Vibrant Android Development] JeremyNT:
1) Did you restore from Titanium? If you did, this is a common side effect. Try re-flashing and only restoring app data, not account or system data.

If you didn't restore from titanium, I have no idea :) Try reflashing.

2) No idea, but see #1

3) Re-install clockwork recovery from ROM manager. When I installed macnut it nuked my recovery, but I can get in now that I've done a reinstall. Oddly I still boot to stock recovery and I still have to select "update packages" to get into clockwork, but from there it works fine.
[Vibrant Android Development] DaytonaDU:
When I get stuck at the Vibrant screen I plug the phone into the PC via USB and hold down Down Volume while turning it on, this lets it boot normally.
[Vibrant Android Development] mulcahyd:
I also had no issues with flashing this rom. Clockwork works nicely too.
[Vibrant Android Development] murse:
This ROM is running well for me too. I can get into clockwork by reinstalling packages from the stock recovery. The only issue I've encountered is the FC in the stock calendar when trying to pick the calendars to display. I use an app called Gemini Calendar, so it's not a big issue. I love the AOSP look and can't wait for the next update.
[Vibrant Android Development] mannybeekause:
Did you find anything on this? I also have the same question
[Vibrant Android Development] ugokind:
excuse me .. but HOW did you do? because now I cannot enter in recovery and now I have another bad surprise.. cannot enter in download mode.. so how can I use Odin to reflash a stock package?

ADDED:

is impossible to uninstall rommanager because is stock with the rom.. I can't uninstall
[Vibrant Android Development] enuro12:
swype works great on this rom for me.
[Vibrant Android Development] MeasIIDX:
When you plug in your phone, does it show you the battery charging (The battery filling with green and dots)?

If it is, here's what I did last night:

1) Remove SD + SIM (leave battery)

2) Had ODIN running with the correct TAR and PIT files. Also installed Samsung's USB drivers just in case on the PC.

3) Plugged phone into the USB and let it go to the battery screen

4) Held down both volume buttons and pressed power. Some people recommend booting the phone first in download mode then plugging in the USB, but this worked out for me. Hopefully you'll see Download Mode.

5) Let ODIN do its thing.

I just soft bricked last night for the first time and this worked for me. Good luck sir!
[Vibrant Android Development] _atlien_:
I'm Bricked

I followed the instruction in the original post before attempting to go into recovery. It didn't save me. I'm bricked.

I understand that this is always a possibility when modifying your phone. But since I, and others are actually contending with brick situations the original post should be modified to reflect this and save others trouble/money (if they have to purchase a new Vibrant).

There should be something in the original post warning folks before they flash that the current rom is causing various serious problems including bricked phones.

I'll let the forum know if I get my phone outta this.
[Vibrant Android Development] enuro12:
When i do this, it just sits at a blinking cursor.

What i did..

1. Turned on phone...

2. Plugin usb while its sitting at vibrant screen

3. ADB logcat

4. blinking cursor, i waited about 5min before i Ctrl+c

I'm available for MSN/ ICQ chat or a phone call if i can help you gather info on this problem
[Vibrant Android Development] enuro12:
So i'm a total noob, but i've got my G1 backup so i don't mind trying crap.

I've tried the latest Clockworkmod

2.5.0.7

2.5.1.0

2.5.1.2

All fail. I would note ADB stooped working when i tried the 2.5.1.2. Odin brought it back some how...
[Vibrant Android Development] MeasIIDX:
Is your phone not turning on at all or is it stuck at the Vibrant logo?
[Vibrant Android Development] diaa08:
Can almost guarantee your phone is not bricked. Read through, learn about Odin, and you should be fine. Getting a little frustrated at all the assumption that there is something wrong with this rom, I've flashed it on three different phones and twice on mine without any problems; just have to be careful and read thoroughly. Developers shouldn't have to waste their time warning you about the fact that things might go wrong and that you might have to Odin back. Also last bit of advice: always wipe the phone and go back to stock before flashing anything, clears up 90% of problems.
[Vibrant Android Development] jtc442:
Wow!! In all honesty here, you are flashing these roms at your own risk! Op says this as well. Any time you attempt to modify your phone, in any way, you are risking brick. That is common sense folks!! Don't blame it on the rom or the Op for something you did on your own. I seriously doubt he made any of you flash this rom!!
[Vibrant Android Development] enuro12:
Here is what i get. I logcat and pressed reboot into recovery. I ran logcat again quickly but its just blank.

D/AudioHardwareALSA( 2380): Latency: 46439
W/PowerManagerService( 2491): Timer 0x7->0x3|0x0
I/PowerManagerService( 2491): Ulight 7->3|0
I/AudioHardwareALSA( 2380): Output standby called!!. Turn off PCM device.
V/WindowManager( 2491): Dsptch > Window{48583e40 com.koushikdutta.rommanager/com
.koushikdutta.rommanager.RomManager paused=false}
V/InputDevice( 2491): ID[0]=0(0) Dn(0=>1)
I/PowerManagerService( 2491): Ulight 3->7|0
V/WindowManager( 2491): Dsptch > Window{48583e40 com.koushikdutta.rommanager/com
.koushikdutta.rommanager.RomManager paused=false}
V/InputDevice( 2491): ID[0]=0(0) Up(1=>0)
D/AudioHardwareALSA( 2380):
D/AudioHardwareALSA( 2380): ALSA OPEN mode 0,device 2
I/AudioHardwareALSA( 2380): Try to open ALSA PLAYBACK device AndroidPlayback_Spe
aker_normal
I/AudioHardwareALSA( 2380): Initialized ALSA PLAYBACK device AndroidPlayback_Spe
aker_normal
D/AudioHardwareALSA( 2380): Set PLAYBACK PCM format to S16_LE (Signed 16 bit Lit
tle Endian)
D/AudioHardwareALSA( 2380): Using 2 channels for PLAYBACK.
D/AudioHardwareALSA( 2380): Set PLAYBACK sample rate to 44100 HZ
D/AudioHardwareALSA( 2380): Buffer size: 2048
D/AudioHardwareALSA( 2380): Latency: 46439
D/su ( 3234): 10036 com.koushikdutta.rommanager executing 0 . /data/data/co
m.koushikdutta.rommanager/files/rommanager.sh using shell /system/bin/sh : sh

C:\Documents and Settings\Chuck\My Documents\ADB\ADB\tools>adb logcat
[Vibrant Android Development] mulcahyd:
Agree. Before I was flashing these ROMs, I have encountered problems which were not fixable but was wrong. I followed the steps on Odin and got it working. Now I know what to do if I have voodoo lag installed or any lag fixed.
[Vibrant Android Development] player4lifeov:
What if I could get into download mode but can't get odin to recognize phone. It only recognized when the phone was actually on
[Vibrant Android Development] gthmcty1:
It's funny this ROM runs fantastic in the stock environment, but it seems as everytime I apply Ryan lag fix I get FC on the phone dialer and the display option....I have reflashed twice from a clean start. If I dont apply lag fix.......no problem????
[Vibrant Android Development] _atlien_:
I understand that we do all of this at our own risk. But this is a community. The OP says that there is a small issue with going into recovery that was resolved.

I'm just saying that isn't true and the many posts in this thread seem to affirm each other. People are having problems with recovery that aren't addressed in the OP. It's not just one or two phones.

It isn't unreasonable that the OP reflect the current state of the rom.
[Vibrant Android Development] mulcahyd:
I had no issues on applying ryans lag fix. My quadrant score 1780.
[Vibrant Android Development] nranson:
I was using the v1.0 of this ROM. Standard kernel (duh), no lag fixes and nothing special going on.

I ran into the problem with getting into Clockwork. It would always bring me into the default Android recovery. I'd run the "reinstall packages" option, Clockwork would load, and whenever I'd try to load a zip to install, it would just hang. It would give me an error of "cannot open" or "no such directory" or something similar. Not just for this 1.1 ROM, but I couldn't get any zip to load.

I tried to use a previous Nandroid backup to restore from, but then it just hung on the Vibrant screen. So I was kind of frustrated.

I got it into download mode and restored the J16 firmware. But for some reason, it kind of got screwy. All of my programs were still in tact (which should not have been the case?) with one exception: The Market. I rerooted, but Clockwork (which was still on the phone) kept having FC issues.

So now I'm panicky. I restored all the way back to the ORIGINAL firmware (before the J16 update), rerooted, reinstalled this ROM and now everything appears to be in order, from what I can tell.

I know this is kind of a rehash of some things that people have said, but, I just wanted to give my two cents. While I am by no means a developer, if there is any help I can give (clarify my workflow, re-explain something, anything), please let me know! I'll be happy to give what I can.
[Vibrant Android Development] ugokind:
sorry and thanks.. but I've repeated that procedure a dozen time before.. but

now the problem is quite different

there's no way to enter in download menu

when I press both volume menu and power I only have grey battery, no odin connection showned, and after a while the batt return green

tried all the combination with the following variables:

2 volume + pow + already plugged with odin opened

"" "" "" "" without odine opened

"" "" not plugged but after yes.. with and without odin opened

vol down + power cause the START of the phone.. never download! strange!!

If I have odin started, with the phone ready (normal software ok?) I anter in adb and type reboot recovery..

the phone goes to obviously windows VIBRANT but the odin tell the COM in already opened and

if I reenter ADB shell the cursor stops. as It wait for a response that never arrive..

boh

We have to try a different point of view..

so what is the nature of the problem?

is it involved with e2 recovery (I don't know what it is maybe I'm writing a stupidity)

let's try to reverse eng

I post the previous log after the last vibrant stuck
[Vibrant Android Development] _atlien_:
Ugokind,

Don't press the power button, just the up and down volume buttons. No power button. Don't press the power button. While pressing up/down volume buttons plug in your usb cable and if ODIN is already open on your computer it should enter download mode.

This has worked for me when having a problem that sounds like the one you are having.
[Vibrant Android Development] jlatnyc:
Well I tried manualy (power+vol keys), tried thru terminal & CWM. It throws me into Vibrant boot loop. To get it out I get the phone into download mode, turn it off and then boot up normal. I haven't tried to add media yet, but if I can add my music and pictures... I'm keeping this ROM until the official 2.2/3 comes out.
[Vibrant Android Development] Anderdroid:
Don't know what to tell you guys about recovery honestly. I'll look into that logcat.

Either way, if you don't know how to consistently get into Download mode you shouldn't be flashing anything on your phone. Learn how download mode works fully first for your phone so you can save yourself from anything, then flash. Save yourself the scare. Save yourself the 'money'. Save T-Mobile from having to send out warranty replacements. Blahblah...

There is no possible way that this ROM can perma-brick any Vibrant to the point where it needs a replacement.

I have had no recovery issues. The only issues I have are battery life hasn't been as good as when I originally flashed, but still decent enough to use. Better than the old Froyo ROMs that died way fast.

And the Calendar FC (although, I don't need multiple calendars). I'll try to fix this.

And lastly Chrome To Phone FC. And slightly sluggish settings menu (needs XML optimization)

That's it. I've flashed this over Odin'd JFD. I've flashed this over stock JI6. I've flashed this over macnut. I've flashed this over Bionix. I've flashed this over Obsidian. I've flashed this over 2.1 JI6 AOSPish 1.4. I've flashed this over both of eugene's Odin JK2 tars. I've flashed this over JK2 flashable zip. I've flashed this over Axura. I've flashed this over OCLF enabled ROMs. I've flashed this over itself. No recovery issues.
[Vibrant Android Development] ugokind:
cazzo.. ha funzionato!

I never used that method.. no power button

voilà

muchas gracias amigo

now I'll restart my experiences...

thanks to all

ciao
[Vibrant Android Development] _atlien_:
None of this is to insult/offend you or anyone else. You don't really think all the folks with recovery issues are lying. We know they (and I) are telling the truth. It is helpful when the OP states what is happening as things develop. Folks who have less experience with ODIN can steer clear until either they learn or until the problems are alleviated. This keeps the threads clean as well and allows devs to hear about problems discovered by more experienced users and fix them faster without wading through dozens of posts on a recurring issue people can't get past. If properly reflected in the OP they probably would have held off to begin with.

The rom is pretty fast, it looks good, my menus were flying, everything was fab. SOME REALLY GOOD WORK WENT INTO THIS ROM. The recovery process is bugged. Letting people know up front, so that those who can't easily put things back together will hold off, shouldn't be a big deal and should be encouraged in this community.
[Vibrant Android Development] crazygamer1:
Can you please also look into wifi staying on even when the sleep policy is set to turn it off when the screen is off? The battery is pretty good, but wifi is one of my biggest drains now so it would be great if it worked according to the settings and not always stayed on. Thanks!