yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] vnamee:
I flashed it yesterday and I must say, this kernel is awesome on my phone so far. Mine handles OC like a champ. After wiping the battery, I'm draining about 4% an hour w/ light usage/standby. I flashed dragon this morning just for fun, and it ate up 10% while I was taking a dump (it was short dump). Flashed back and battery life is great again. Pulled like 2000 quadrant. This one looks like a daily driver for me.

Also, the two combos I know of to get into download mode are vol+, vol- then usb plug, and depending on rom flashed previously, vol - and power. Also, the phone-pc screen should be flashable w/ odin as well.
[Vibrant Android Development] ameedi600:
Don't get your hopes up, all who don't want to brick there vibrant, do not flash this until many people have confirmed that the sd parted method has worked. So far only a few people have successfully flashed there phone back to stock. If you don't know what I am talking about then got to Vibrant Q&A and look for Samsung Vibrant Bricked? It should be around the first one
[Vibrant Android Development] ameedi600:
Don't worry about that just try to get into download mode like you normally would, it should work if you are doing it right.
[Vibrant Android Development] gendolookin:
I GOT IT!!!!

Ok!.

I basically had to flash back to stock... I downloaded a stock rom and used heimdall to flassh it, it took! Now i have to get working on rooting and installing bionix again! Thanks everyone for your helpl
[Vibrant Android Development] Infoport:
I have been successfully running this kernel, with the Bionix 1.2.1 ROM.I took the DoW kernel zImage w/HD support, and put it in the DoW14-T959.zip over the other kernel so I would still get the init scripts (TW didn't provide the dow14-t959-hd.zip then)

I was coming from Dragon 3.6 kernel with the same Bionix 1.2.1 ROM.

Everything booted ok, I've been enjoying it with no issues, though haven't used OC.

One more note: I also previously had the issue with "no internal storage/sd card not seen", coming from Eugene's Dead Horse (I think test28 or something). I think it was from filesystem corruption, or from Dead Horse using a filesystem not recognized by the next kernel I tried. After many hours, and Heimdall back to JFD and then KA5, waiting after each boot and rebooting, I got the sdcard reformatted and everything back to normal. I hadn't used DoW for a while before that, though I'm using the Vibrant-source-based DoW now fine.

Remember: if your phone still does anything, it isn't truly "bricked" and you have hope. Sending it back to your carrier may be easier, but if you can get it reflashed and back up you won't have to wait.(and you'll feel more confident when you flash again, and you know you want to! ;-)

Good luck, and enjoy! (for those who flashed successfully)

William
[Vibrant Android Development] takato23:
hey, why when i shutdown the phone.. it doesn't? like stays on a black screen till i press the off button 10 seconds.
[Vibrant Android Development] Infoport:
btw Morfic, if the sleep fix is "not in yet", wouldn't it be better to remove the words "SoD fix" from the thread title?

just saying...

William

(a happy user of Bionix 1.2.1 and DoW14-T959-HD)
[Vibrant Android Development] morfic:
Obviously, point taken, thanks.

I like your story, same symptom, although not all with this issue came riding in on a dead horse, a majority of them did.

Sent from my Nexus S
[Vibrant Android Development] morfic:
Give me a list of your apps and especially widgets.

List all check intervals on your twitter/facebook/[SNS]/IM apps.
[Vibrant Android Development] jonwilly:
Ran perfect at 1mhz.. Cant OC to 1.4 wish you could scale down to 1.2 because I can run stable only at 1.2 for OC..

Big issue though with mobile AP not working when I install this kernel. I re flashed a couple times to check if its the kernel or not. Only get errors with mobile AP with this kernel. Had to switch because of this problem.
[Vibrant Android Development] MStrawder:
Been trying to follow this and the thread with people trying to recover from it and wanna throw this out there. I was running a different kernel and ran into a similar issue with mounting errors, reboots, and ultimately I had a device in hand that wouldn't display anything on the screen, nor would the capacitive buttons light up. I actually called T-Mo and had arranged for a replacement, figuring it was a true brick.

In any event, I decided one last time yesterday morning to try and resurrect my device. I should add that I couldn't get into Download Mode to save my life. I tried for over an hour the previous night. So on my one last try I removed SIM/sdcard/battery and plugged it into the USB port on my PC. Held the volume keys, inserted the battery, and voila, Download Mode. I flashed a Froyo ROM/kernel and the device seemed to boot up, but continually reverted to stock recovery and mentioned a mount error.

I downloaded the stock ROM here containing the PIT, Phone, PDA, and CSC. Flashed with re-partition checked and my phone is back. Now I never saw that specific ROM mentioned as being flashed, so if you've tried everything else, give it a shot. It returns the device to out-of-the-box newness.
[Vibrant Android Development] morfic:
Did they use an ULF based kernel?
[Vibrant Android Development] morfic:
v1.1.1 uploaded, it replaces v1.1 which did not upload correctly, added md5sum for user verification of download.
[Vibrant Android Development] Spartoi:
Hm, tried running Nenamark at 1ghz and it crashed immediately.... Will try again.

EDIT:

Seems to have been a fluke.
[Vibrant Android Development] MStrawder:
No, it was a Voodoo kernel (red recovery). My issue was caused in part by an inability to convert the /system partition back to RFS. That eventually led to some major filesystem corruption that got worse and worse.
[Vibrant Android Development] jeproxx2:
+1 backlight stays on and black screen. does not shut down all. I'm using HD version 1.1.1
[Vibrant Android Development] morfic:
OP updated with fix for the internal storage, the dead horse ate.

http://xdaforums.com/showthread.php?p=11522460#post11522460
[Vibrant Android Development] xgamer791:
People if your phones are running good than dont download a new kernel! Is it worth brickin your vibrants?

Here what I can tell by now, the vibrants memory and cpu core have both been maxed out in bionix v+vodoo 14, that is the best it is going to get untill the duel core phones come out, from now on if something new comes out it is not going to do anything new, get over it for now.
[Vibrant Android Development] PJcastaldo:
:rolleyes:
[Vibrant Android Development] PJcastaldo:
Working great at 1.4 . Over 2000 in quadrant, high 18 linpacks... Thank you very much.
[Vibrant Android Development] MStrawder:
That's not accurate at all. The CPU's have been overclocked to 1.4ghz. 400mhz above the stock speed, which is what the kernel that comes with Bionix runs at. Many people have ran this speed reliably and even supplied less voltage to the CPU in the process, thus saving battery. The GPU's have had the FPS cap raised and have put out 50+ FPS in benchmarks. So they are nowhere near "maxed out" yet.

I will however agree that unless you're willing to accept the risk of possibly bricking your device, don't flash everything you see posted.
[Vibrant Android Development] EasyTiger6x13:
The problem has seemed to fix it self. Let it drain all the way down through the day. Charged it back up. Let it die again. Wiped Battery Stats and now sitting happy at 100 percent after Id say 30 mins is roughly of being unplugged. However I will say with very minimal use, 4 text messages, checked xda, checked market, checked facebook and thats that. Just flashed the new kernel V1 you posted and will report anything back to you sir.

I will add the apps and widgets I used on the last kernel

Widgets: Just simplistic widget or whatever its called, 2 widgets one for time/weather, and one for date.

Apps: not many just facebook and xda really. A little bit of web searching, facebook set to check for updates every 6 hrs.

Great kernel Morfic
[Vibrant Android Development] xgamer791:
My bad I thought voodoo 14 was overclocked to 1.4, I worded that wrong.
[Vibrant Android Development] apollo15rover:
Dumb NooB Questions..

So I installed this latest version this AM - decided to freeze some theme elements (forgot to back up my Kernel - oh well.. )

And it installed perfectly.

I don't have SetCPU

Can't tell what my Quadrant score is because Quadrant keeps giving me internal error messages at the end of its scan ( tried reinstalling Quadrant but no joy on this)

Do I need SetCPU to get some benefits with this Kernel or am I fine just running as is..

Samsung Vibrant

2.2.1 Beta 2 XDT

(now with DOW)

Thx!!
[Vibrant Android Development] :
Running it without set cpu and its flawless. 1600 quadrant.
[Vibrant Android Development] I7oobie:
+1 on this. Trigger 2.6.1 and DoW14 HD v1.1.1
[Vibrant Android Development] imitebewrong:
Just reporting, I have no problem with the phone shutting down.

I am using the latest release of the kernal.

1.4ghz Bionix 1.2.1

So far I have no negative effects from this release. Thank you!
[Vibrant Android Development] MStrawder:
The kernel defaults to 1ghz unless you use SetCPU or the voltage app to raise the threshold.
[Vibrant Android Development] xgamer791:
Anyone know how I can raise the voltage for DOW14? I keep getting crashes in neocore and other stress tests, I suspect a voltage problem because temps are fine.
[Vibrant Android Development] Sdobron:
The wifi seems to have intermittent issues on version 1.1.1.

edit: Using KA5 modem, sometimes scan fails and immediately turns off then another attempt will result in a successful scan and network connection.
[Vibrant Android Development] apollo15rover:
So I'm up a few hours with this (SetCPU at 1.4) and seems to be running well.

Only issues so far..

Turn off issue described above - sometimes this happens sometimes not, but I can always get the phone to start easily.

Once the data went completely off and had to reboot - everything came back up to 3G fine.

While phone was in cradle, crashed (milky screen with vertical lines)

Reboot went fine.

So thinking about setting back to 1.0 for the time being..
[Vibrant Android Development] a4 moda:
Morific,

So, now onto day 6 of No Phone, because of a Hard Brick. Been troubleshooting the phone since 8am this morning. Here are my findings.

Hopefully This will help you, so that you can help us.

DOW- previous I9000 Kernel:

This is my "Mount" output

Comparatively, here is the "mount" table from another member, who has a working Vibrant.

I hope this will help, and point you in the right direction as to what and how the DOW kernel is affecting/performing on phones.

Thanks boss.

Please let us know if you have any fixes/updates.
[Vibrant Android Development] compuguy1088:
I've had this occur once......though this is not consistent. I wonder if this has anything to do with coming from that dead horse kernel...
[Vibrant Android Development] Sdobron:
A4 moda, did you use ulf previously? I doubt DOW alone caused it.
[Vibrant Android Development] lqaddict:
Got the same issue.

Seem to be fine after a few attempts of cycling it on/off via the Settings, but won't work from the status bar pulldown.
[Vibrant Android Development] a4 moda:
Don't know how to respond to that because I don't know what you are referring to.

1. I used all the TW's roms since Bionix 1.8 then Fusion, obisidian, nero, now Bionix Final.

2. I've always used ext 4 Voodoo lagfix that came with the TW roms

3. I was running Bionix 1.2.1 stable for 2 weeks *(just about if not more) when DOW released *(previous Kernel) with I9000.

Then Day 2, the phone died

Many others have reported the exact same incident.

The current DOW seems to be fine.

The previous one *(which is no longer up), seems to be the problem.

When you say ULF, you mean Eugene's ext 2 / ext4 Lagfix?

I've always run Voodoo on this phone, otherwise, no voodoo, so JFD.

Hope that clarifies it.
[Vibrant Android Development] treyvaporizer:
I am experiencing the same thing, it has to be these kernels. But I dont really give a crap if i can just restore my stuff which i am doing with ODIN
[Vibrant Android Development] serban954:
ULF stands for Universal LagFix.
[Vibrant Android Development] PowSniffer0110:
Is it me.. or is my.market gone?? Im not crazy its deff gone my shortcut to it wont work. Any help would be appreciated.
[Vibrant Android Development] apollo15rover:
White Line Crash

Just for the heck of it, I did a Nandroid backup - from the Red Voodoo CWM, not the Emerald ROM Mgr CWM and it did fine.

However, I noticed that when my Vibrant was plugged into the powered desk dock, it white lined and I had to reboot.

I set the setCPU back to 1.0 from 1.4 and it did it again at 1.0.

I don't know if the dock is the issue or the screen being constantly on within the dock.

I am rebooted ok and am leaving the phone out of the dock off power. If it stays ok, I'll plug into power cable only. Lastly I'll plug back into the dock. If it fails, now that I know how to generate a CWM log, I'll run and post here to see if that helps the developers any..
[Vibrant Android Development] MStrawder:
ULF is universal lagfix and is in the green CWM recovery. It was the one with the standard, advanced, and overkill lagfixes. JFS or ext4 or one with the ext2 loopback. Eugene and others have used it in their kernels.
[Vibrant Android Development] morfic:
Kind Sir,

Here is my ransom list of demands:

Read the fix in OP.

Follow it.

Don't bold me in the face like that again.

it's morfic, not morific

Fulfill this list of demands or else.

Sent from my Nexus S
[Vibrant Android Development] apollo15rover:
For Anyone With Samsung Vibrant Desk Dock Accessory

Are you running into the same thing I am ?

After installing DOW, kept white-line crashing even at 1.0 on SetCPU and back of unit getting a bit warm.

Off the dock and on a regular power cable at 1.4 working nicely and cool as a cucumber even with Stay Awake while charging and Live Wallpaper running..

I don't know why that would be the case, but that dock has always been a bit twitchy..
[Vibrant Android Development] morfic:
So far the majority of people who had this issue ran an ULF kernel before.

Some recognized the issue and got themselves fixed with the link now in the OP.

Some managed to get themselves fixed with the JFD version.

Some tried a random order of "odin events" and got themselves stuck in the mud harder.

For this reason, we ad a user on irc volunteer and he broke his system by flashing dow from an ulf kernel, he recovered using the method in the OP. After this proof of concept, he needed a smoke, bad, and i added the fix to the OP.

His internal sdcard was completely gone, only his external was recognized by the system.
[Vibrant Android Development] PaiPiePia:
lol. Where is Scrizz!?!
[Vibrant Android Development] BuLLeT_PrOOf_wAlleTz:
Omg! I flashed back and forth from ulf kernel("deadhorse"). And I neva had any brick or sd issue. I held back and waited till dow kernel was actual vibrant source.

Been running the very first kernel with NO issues. Getting 20 plus hours.

Hd recording is fine.. no sod.
[Vibrant Android Development] 啊喔鹅咦呜鱼:
I'm working with dow hd 1.0 now,if i could directly flash v1.1?

BTW,i've used dead horse long ago.
[Vibrant Android Development] GoodVibrant-ions:
I'm running bionix v 1.2.1 and the kernel it came with. I decided to wait til the kernels from source were out. I have a couple questions.

I went from stock to bionix v, to 1.2 and then 1.2.1. Technically I should have no problems flashing the new DoW from source....is that correct? Can anyone say they've flashed DoW under this same set of circumstances?

And lastly.....(I know this is probably easily found but) disable voodoo before flashing?
[Vibrant Android Development] muchelaguito:
I did EXACTLY THE SAME. THE SAME PATH RIGHT FROM THE BEGINNING and I DID NOT HAVE any issues. I haven't flashed any other kernel than DoW or stock kb1 with Voodoo. Not even a hint of issues, I'm very happy myself.
[Vibrant Android Development] apollo15rover:
Thanks much!! Couldn't get my Wifi up and running until I read this..
[Vibrant Android Development] Kubernetes:
I had the broken Voodoo issue once when switching between Dead Horse, DoW, and Dragon. I remember getting out by flashing stock kernel and when that didn't work I Odined from there.
[Vibrant Android Development] Trets:
how to change the KERNEL boot animation?

Hi,

I just switched from the dead Horse to try some TW goodness. So far all good, Odin'ed back to stock, then Bionix 1.2.1, disabled Voodoo (I know I know, but.. well, takes no time really), flashed DoW14, then the KA7 modem (had not the best experience with KB1 that comes with Bionix 1.2.1; battery went down rather quick). No WiFi issues, no FC, all smooth and nice. Will report in a day or two how battery is with this one.

Question, though: How can I get back to the 'old' Vibrant boot animation (want to replace the lady that came with the kernel)?

Thanks Morfic for your work!
[Vibrant Android Development] morfic:
Welcome.

That's just the boot logo built into kernel, boot animation I don't touch.

The logo may change over time, but only my stock frequencies with voodoo * + bln will have the std vibrant logo.

Sent from my Nexus S
[Vibrant Android Development] Trets:
Ah, I see. Thanks for letting me know.

Greets from SF
[Vibrant Android Development] morfic:
I think it is more related to ulf being such a treasure chest that makes it impossible to consider any two ulf phones the same.

I am glad not more got bit by this.

I think it also relates to 1550 downloads for dow14fow increasing the chances for "bad luck".

Sent from my Nexus S
[Vibrant Android Development] serban954:
Just flashed the 1.1 hd. Where can i get all the BLN apps and all that?
[Vibrant Android Development] muchelaguito:
uh... Market. Oh, Wait! you are joking, right? he he he
[Vibrant Android Development] morfic:
Bln and voodoo control apps are in market.

Voodoo sound can be controlled, Voodoo color is always on.

Sent from my Nexus S
[Vibrant Android Development] serban954:
Yes it was a joke lol. I already have them. BTW, nice boot image ;)
[Vibrant Android Development] morfic:
Nice save. :P

Thanks, always nice to hear someone is *NOT* scared by it.

Sent from my Nexus S
[Vibrant Android Development] TruLuvNvrDies:
red voodoo?

thanks as always for the great work, morfic. i just got my vibrant and i'm in process of doing the whole root thing and I want to eventually flash your DoW rom. I want follow the instructions closely but can't find the red recovery you reference in the OP. is it just flashed from the stock voodoo kernels? or do I need to flash it separately? i've searched for but no luck so far.

and thanks again, esp. with resolving the issues from prior pages.
[Vibrant Android Development] serban954:
Yea, some people just dont know style ;). I guess im one of the few who can run 1.4ghz without any hiccups whatsoever. Running smooth and getting quadrants of 2000+ and linpack of 18+ Thanks once again. :)
[Vibrant Android Development] muchelaguito:
Well, you can count another one. Your work is awesome Morfic. I'm really happy with your kernel. I'm just waiting for you to release a Kernel that will allow me to set profiles on boot with less than 800mhz as Max. But other than that... it works just awesome.
[Vibrant Android Development] muchelaguito:
BTW, I also ran it @ 1.4 with no issues. So far, my device has been performing awesome! since day 1. Team Whiskey from the beginning, less than 24 hours after I got my phone from T-Mobile I had rooted it, and installed Bionix V, 1.2 and 1.2.1.

I look forward to try your next kernels and Frosted ;-) But I can wait, take your time.
[Vibrant Android Development] gforceriders:
You count that as three that can run this blazing fast 1.4 Ghz kernel without one hiccup. Thanks again morfic.
[Vibrant Android Development] playa0506:
Same here
[Vibrant Android Development] playa0506:
I don't know if anyone has been having the battery stat issue but this kernel wrecked mine. I went back to stock kernel and back to normal. I'm trying to figure if we're supposed to wipe stats at 100% to notice the battery drain fix? I am at stock getting easy 20hrs+ but tried everything with the original release couldn't get more than eight. Biggest problem was I couldn't recondition because the phone wouldn't shut off properly if plugged in. Why is that?

Bionix 1.2.1 + kb5
[Vibrant Android Development] morfic:
DoW14-T959-HD-v1.4 added to op for testing. 344MB version, please test.

If everyone is happy this will ring in the end to HD and bigmem versions as 344MB is "bigmem enough" and it has HD recording and playback working.
[Vibrant Android Development] jkhrist:
The main problem I have is I lose data connection when sending or receiving mms. Anyone else having this problem?
[Vibrant Android Development] notverycreative:
HD works fine for me as well. No problems as of yet except really poor battery life, but hopefully clearing battery stats will fix that.
[Vibrant Android Development] GoodVibrant-ions:
Hey man...if you still need help, I'd be glad to help you. I had quite a few ppl answer my questions for me....and I keep having more. But they always get answered by someone.

Anyway...figured I'd pay it forward. Are you rooted? And if so...whats your next step or question?

Ps....red recovery is found in rom manager (if that's wrong...feel free to correct me someone) Download that from the market.

And also...you'll want to read the first part of this thread http://xdaforums.com/showthread.php?p=9375927 in it's entirety. Very important you fo this!...because DoW isn't a rom....it's a kernel. So you have a little bit of learning to do.

Its all good. Three weeks ago I was completely lost and now I know enough to help. PM me if you have more questions.
[Vibrant Android Development] tiquau:
So happy with v1.1.1. Thank you. Having problem with v1.4, HD record, screen froze when pause/stop record. I have to take out the battery to restart my phone. Back to v1.1.1 now.
[Vibrant Android Development] compuguy1088:
Just tried to replicate this.... couldn't.
[Vibrant Android Development] roffee:
the newest with 344m. HD is ok.
[Vibrant Android Development] ameedi600:
Do not flash this if you value your phone, this will likely brick your phone as I and many others have been suffering through. There is no fix for this brick as far as I know. Just remember I WARNED you.
[Vibrant Android Development] a4 moda:
Sire,

Thank you for volunteering by force one of your serfs/vassals to brick his/her phone.

That was over the top and certainly, unexpected for you to go above and beyond the call of duty.

I am personally grateful.

However, I regret to inform you that JE8 did not work.

The partition is still F*K'D.

I've got corrupted or nonexistent "system" folder/files, among others. But that is the major corruption, from what I can tell anyway.

I'm going to try another method. if I am successful, I will be sure to let you know.

Thanks.

Oh, and I will be donating to your fund.

BTW: Don't you think Morific sounds better???
[Vibrant Android Development] bobmyers:
Same thing happened to me, except my phone also shut down and went into a boot loop (I think)
[Vibrant Android Development] imitebewrong:
I flashed it onto two Vibrants I value.

No problems on either one, great kernel overall.

Have flashed back to the stock kernel, and then back to DoW several times testing things and haven't had an issue yet.

Only thing that once corrupted my data and wiped internal SD was the Dead Horse kernel. But I Odined to stock and reflashed Bionix without a hitch.

You can't assume because it didn't work that it won't work for everyone, just as I can't assume that just because it worked for me it will work for you :)

There is a risk flashing everything, even a botched rom flash can screw up your phone.