yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] street954:
I got 13.25hrs out of this kernel using:

SetCPU 1400 max, 400min with bat >50%, 800 400 bat>15, 400 200 batt<15%, also used 800 200 w/ screen off in power save mode, all else were on demand.

DRM content frozen

i had pandora running for at least 5 of those hrs

Heavy use of WiFi and 3g connections. Put into airplane mode for 1.5 hrs while in a dead zone

Screen on auto brightness.

Quad scores: 2050

MFLOPS: aprox 19.3

Nicely done TW, MUCH more stable than the Dragon kernel ... just wish the mic/headset was usable, but definitely not a deal breaker!

Donate people, this work is impressive!
[Vibrant Android Development] Jdom58:
I agree everything about the kernel with B-V1.2.1 is fantastic super fast, but once I start using the phone and multitasking, it drains way too fast.
[Vibrant Android Development] SuperJMN:
+1. I almost can see it going down! No OC.
[Vibrant Android Development] december.underground:
When ever I set screen off to powersave I get sleep of death so I set it to conservative, also my battery stats are all F**ked up and I flashed the kernal on 100% charge and at this point I don't know how to get back to an accurate battery stats.

0bey <-_->
[Vibrant Android Development] december.underground:
I have been having this same issue so its hard to gauge battery life but for me it seems poor about 20% and hour :-(. Ill try to reinstall and remove setcpu and get a full charge on stock kernal and try again.

0bey <-_->
[Vibrant Android Development] harabinger66:
Normal battery life

False.

I want to be clear that I only think the title of the thread should be changed. Its far from normal battery life. Standby is certainly improved, but when you're using the phone (for instance, listening to music without the screen being on) it drains very fast.

Great Job on the actual functioning of the kernel though, snappy, + voodoo sound. I appreciate your work. Especially against the backdrop of a lack of source.
[Vibrant Android Development] gopheer:
Wow crazy battery life if you set the right setcpu profiles.. Especially 200/400 when screen is off.. Drained 10% in 8 hrs.. Fantastic job
[Vibrant Android Development] :
Me too, best sleep ever by far, but actual usage drops so fast. No overclock. Bionix 1.2.1 - 4:00 pm

Unexpected turn off, no wake. Must be the SOD. - 8:30 pm
[Vibrant Android Development] |Logic|:
went back to stock KB1 + Voodoo. I had a weird issue with external sd. couldn't see it when I mounted the phone to a computer, and also couldn't see the anything on it (including the music on it) when I wasn't mounted to a computer
[Vibrant Android Development] mprosper69:
anyone can answer the above question

the question again is wich apps to use with this kernel
[Vibrant Android Development] cjggilbert:
Battery, and performance

OK so I have been using this kernel now for well over 24 hours, and at work today I have not noticed any difference in battery from that of Bionix V 1.2.1

I am OC'd to 1.4 and have noticed better speeds on everything from downloads to the responsiveness of the phone itself. Ran a quadrant while posting this and it was 2072

Thanks Morfic,,

Also Is this kernel going to work with Frost (not sure if it's been asked yet)

If not will there be a DOW kernel for Frost?
[Vibrant Android Development] ctran81:
Working great, great battery life, excellent sleep, fast web browsing!

Only issue I've seen is wifi doesnt work sometimes (helps if you disable mobile data first), and setcpu profile of screen off with 200/400mhz conservative would cause wake of death, but using 'on demand' fixes that.

It's my daily driver until 'dead horse' kernel gets out of what i consider alpha status.
[Vibrant Android Development] existz:
Hey morfic, was wondering if you cared to shoot me PM on what you done to fix sleep death, using JPX sources as well for my captivate kernel, seems some users having sleep death even with no oc/uv, if you dont mind, drop me a msg, thanks
[Vibrant Android Development] AngryDinosaur:
so i flash with CWM?

Disable original voodoo first?
[Vibrant Android Development] shovelhead83:
Not tryin to be rude. Just lookin out. If you have to ask. Dont flash it.
[Vibrant Android Development] treyvaporizer:
Yes you flash it with cwm , the Odin version didn't work. Don't listen to shovelhead, for he was a noob once before too..

Sent from Bionix powered vibrant! If I helped, hit the thanks button!
[Vibrant Android Development] jangst123:
Please Help

I've been running DoW14 with Bionix-V 1.2.1 for a few days now and it's been running great.

Up until an 2 hours ago.

I had about 30% battery left when, it, I believe turned off and I had to do a battery pull.

When I turned it back on, it would not boot past the green lady android screen,, after 15 min

I pulled the battery. And tried again with the same results.

So I Odined back to stock, and it seemed to go fine, until it rebooted.

Got the Standard Virbrant Boot screen for about 4 sec then the screen goes off and it will not do anything.

Pulled the battery after 15 min and tried again and got the same results, 4 sec boot screen and nothing,

So I tried Odin, again..

Same result.

Tried with and without sim card, different battery,,

Any ideas!?

I'm beginning to think I fried something or may be a lemon phone,, purchased it Friday.

We Now have 6 in he office all running Bionix-V 1.2.1

2 with Dow14D

Thank you Team Whiskey, Because of you guys, we love this phone enough to get one for each employee!
[Vibrant Android Development] Goten310:
You were new at one point too. Yes you were rude. Simple question but like most rude people you took more effort to put someone down then to actually "look out" for them. Geez most of you don't have the courage to be such dicks in the real world because someone will put you in your place but yet it is okay to be one here? Bravo Cool Guy.
[Vibrant Android Development] es7241:
Try flashing Eugenes "Froyo that does not brick" then flashing JFD or JK2. That is very odd.... Hope it helps, its worth a shot.
[Vibrant Android Development] n2ishun:
Be aware that if you had this device overclocked (which is one of the main purposes of the DOW kernel) it is possible to over heat the CPU.

If it gets too hot it can smoke the chip, as in permanently fried.

It sounds to me like this is what happened to you.

I do not know an accurate way to diagnose this on these phones.

If you only got it a few days ago as you say...take it back, it is still under warranty.
[Vibrant Android Development] jangst123:
Any chance I can get a bit more direction,, I think I have the right file but I'm not positive and I don't want to make this any worse! Can I get a link to the file or forum.
[Vibrant Android Development] es7241:
http://eb-productions.proboards.com/index.cgi?board=samsungsgs&action=display&thread=8

Download it flash with odin(when it boots to recovery just reboot and get back into download mode... the phone will not boot up), then when your flashing back to stock select the repartition feature in ODIN..

See if it works and if not just like the other guy said your phone is fried :/
[Vibrant Android Development] :
updates to earlier posts

Should say this was around the 30% life mark. My phone started up fine though. Had this issue on stock 2.1 no root, no roms. Never had this until now with the custom roms.

Here's my assessment after testing each: (toss up?)

1. Dow14: Great sleep, snappy, bad drain with usage (no oc)

2. Eugene's Vibrant_4: okay sleep, really snappy, okay with usage, questionable stability... not sure I want to over-clocking and the advanced file system flashing (RFS advanced, oc 1.2 as it comes)

3. Dragon 3.2: bad sleep, really snappy, bad drain with usage (no oc).

When team whiskey releases a new rom, I'll probably stay on the voodoo kernel and won't flash the other stuff. Wish I could still get the memory hack though.
[Vibrant Android Development] jangst123:
Thanks for the help!

It looked promising, everything went perfect until it rebooted after Odining T959UVJFD

Shows the Battery then keeps boot looping to show the battery charging, over and over.

If I unplug the USB and turn it on, it shows the Vibrant boot screen for about 3 seconds then shuts off.

Looks like I will need to return it! Cross your fingers for me!

Very strange! You would thing it would have happened while running benchmarks or using Navigation and talking on the phone,, not after hitting the power button after using the XDA APP,, wasn't even warm when I put it down.

Too many flashes to count, 1 nasty brick, o well don't do the crime, if ya can't do the time!
[Vibrant Android Development] Nabeel10:
Does this work with Trigger?
[Vibrant Android Development] cashyftw:
Yes it does.
[Vibrant Android Development] Nabeel10:
So im a bit confused, when it says good battery life, does it mean better than stock or what?
[Vibrant Android Development] All~G1:
It's close to it, if not a bit better. The point of the kernel is more about performance, options or tweaks.
[Vibrant Android Development] a4 moda:
Weird issue guys. Panic!!!

Keep in mind that I have OC with DOW with, TTbal's OC kernel, with EUgene's OC kernel, all with stability and ZERO problems .

But today...

Phone froze. When I tried to restart it. It stays frozen at the "DOW" Green splashscreen with the avatar woman. Stays frozen forever.

And, I can't get into Recovery. At all.

Please help.

Thanks
[Vibrant Android Development] M5devil:
Looks like your only option is to ODIN back to stock and try again.
[Vibrant Android Development] a4 moda:
okay. i've done it.

ODINed backed to stock, Eugene's Froyo Non-Bricking, Ji5 Ji6,

I can't get past the boost screen.

"Vibrant"

Then blank.

nothing. Can't get into recovery.

The phone shuts off after Vibrant.

I can get into download mode, but it's not doing much good.

Another poster in the Q&A section reported the same exact thing.

Bionix + DOW

This is really bizarre.

My phone is now fried, and I'm gonna call for a replacement.

Just FYI everyone.
[Vibrant Android Development] jangst123:
Sounds like we have the same very ugly problem!!

Even more bizarreness,, I gave up on it last night!

Just for shi** and grins I turned it on this morning and it acted like it was going to do the after Odin setup, and seemed to install something, but it went by too quick with the red and yellow writing + progress bar.

Now it's in a strange boot cycle, different than the last one.

The initial Vibrant boot image keeps flashing, On for 13 sec, off for 2.

I'm going to let it sit for a few and see what happens.
[Vibrant Android Development] :
Next morning: won't boot past green lady. Can't get to recovery mode. Just odin back to stock, but can't get past vibrant logo. I didn't overclock this...:mad:

I'm seeing that it fails to wipe data during the boot process after odin. Phone is not working!!!! Any help would be great... is the sd card not mounting, what?
[Vibrant Android Development] eunkipark92:
Did u check the repartition box when u were odining back to jfd

just simplu reflashing the kernel would have fixed it though..probably.

bionix 1.2.1 with adw launcher ex
[Vibrant Android Development] :
Yes, I did that, I've repartitioned before though and it started fine.
[Vibrant Android Development] Jdom58:
Actually battery life has been very different between users, some people claim 17hrs up time and some like myself only got 8hrs max with moderate use. It's one of those things where untill you try it you won't know how your phone will react. Other than that the kernel is fantastic and I had no problems whatsover running it with B-V 1.2.1
[Vibrant Android Development] vahdyx:
For me this hasn't been a good add on, my battery life is worse and when I don't have a successfully sent message it freaks out. My phone will say, will send message when signal is available like 200 times or until I reset the phone.

Oh and another thing is during wifi calling now my audio plays out both speakers. The one for your ear and the one for speaker phone.
[Vibrant Android Development] drewdude007:
So I was running Bioniox-v 1.1.2 with this kernel and using set cpu to overclock it to 1.4 Ghz. Ran great for a few days then I ran into a problem that some people are having. My phone was frozen on the DOW boot up picture so I Oden back to stock then the phone would not boot into recovery after Odin. Tried Eugene no brick fix with no luck... nothing I have tried everything (spent 12 straight hours) and nothing will bring it back to life.
[Vibrant Android Development] richan90:
Eh same thing happened to me. Why do a full odin flash when its clearly a kernel problem? Odined the stock voodoo kernel and was up and running instantly.

Plus I think doing an odin rom flash while ur in ext4 is a bad idea?

Sent from my SGH-T959
[Vibrant Android Development] a4 moda:
I've had all kind of bricking problems before man. Never had a this problem though.

And, I can't get into recovery at all.

I understand your concern with JFS conversion to Ext4 then back, I had the same concern, which is why I flashed EUgene's nonbricking Froyo.

Either way, my phone still doesn't go into Recovery, and nothing I flash in ODIN works.

I can't get past the Vibrant screen. THe phone just shuts down.

The only thing I can do is get into download mode.

Any help please??

Thanks
[Vibrant Android Development] a4 moda:
This is absolutely my problem too. Same damn thing. Nothing I try in ODIN works.

I can't get into recovery mode but I can get into download mode.

But that does no good.
[Vibrant Android Development] ruskiiwrx02:
I loved it at first seemed fast and snappy got over 2K on Quadrant and 19 mflops on linpack.

But running it for 2 hours now at 1.4ghz and have gotten 2 sleeps of death. Turned it down to 1.0ghz. Was wondering why i can't make it 1.2ghz or 1.3? only 1.4 or no OC.

Also wondering where I can get the stock kernel for the latest bionix, so I can flash back to it in case I get another sleep of death.

Thank you
[Vibrant Android Development] I7oobie:
Bionix runs the latest Voodoo Kernel.
[Vibrant Android Development] ruskiiwrx02:
I realize that. I'm looking to just flash that kernel instead of this one, so i don't have to reflash the whole rom.... any idea of where i can get a zip of just the kernel in bionix...
[Vibrant Android Development] jmcghee1973:
Right on the OP for Bionix...toward the bottom
[Vibrant Android Development] ruskiiwrx02:
Nope that's not the newest kernel, that's why I asked instead of just downloading that. I appreciate the suggestions, however I'm not a newb, and I searched for it before asking. So if i'm asking it's not in an obvious place like that... or maybe it is lol can anyone point me to it?
[Vibrant Android Development] Kubernetes:
Check out Supercurio's thread for stock + voodoo kernels.
[Vibrant Android Development] CsanMan:
I've been stuck in quite a few situations myself but was able to get out of it. You were able to Odin to stock using the pit and tar file successfully? but phone still shuts off after Vibrant screen bootup? Did you get any MD5 Checksum errors?
[Vibrant Android Development] a4 moda:
That is correcto man.

I've got no MD5 checksum errors.

But i can't get past the Vibrant splash screen. Phone doesn't pause, it just SHUTS OFF.

Please help guys.
[Vibrant Android Development] ruskiiwrx02:
GOOD CALL!!! Thanks!
[Vibrant Android Development] CsanMan:
1 more question to make sure whether your phone really shuts off. After the Vibrant splash screen and the screen goes black, does the 4 buttons on the bottom lights up when you touch the screen?
[Vibrant Android Development] :
Update: Found some posts... found out my internal sd card is not mounting... found a thread with eugene's froyo will not brick. I flashed this after my first Odin and JFD. Still not mounting, but phone started up...

So I need a fix for mounting my internal back... HOPE HOPE the bunny does
[Vibrant Android Development] a4 moda:
Absolutely, I've waited 30 minutes at most, and less on other occasions.

During this time, I touched the buttons, all 4 buttons. I'm positive, it is actually OFF.

Yes, it's dead.
[Vibrant Android Development] CsanMan:
Damn not sure then. But...I do know there is 2 types of Eugene's Froyo no-brick and 1 of them saved my a$$. The no-brick ROM I used does not boot up to your OS but it boots up to the recovery giving you some error message. But the thing was it at least booted me up to recovery and from there I just odin back to stock and everything worked fine. Not sure exactly which file you have but when I get home from work tonight, I'll link you the one I have and see if that works.
[Vibrant Android Development] richan90:
You can't just flash back to jfd when yiu have voodoo enabled. It well brick your phone. Flash a voodoo kernel from supercurios thread and it should be fixed.

Sent from my SGH-T959
[Vibrant Android Development] a4 moda:
Thanks,

that's the one I have. Where you have to use Root Explorer to reboot the phone from Recovery.

This isn't the problem. There is something more here, and I can't figure out what's Fked UP.

But I appreciate the help.
[Vibrant Android Development] CsanMan:
The file I have is a .tar and use for Odin-ing, not through Root Explorer or flashing through Recovery.

Sorry I should have been more specific but I'm at work and trying not to get caught browsing the internet lol. The file that I have was something like SamsungFroyodoesnotbrick.tar. I was stuck on the black screen after the Vibrant screen like you but I was able to light up the 4 buttons when I touched the screen. I Odin that .tar, it fixed something and went to the bootloader but couldn't load to the OS. Then I Odin again to stock and everything was fine.
[Vibrant Android Development] Sdobron:
Back to stock for now. Gave it a good try, but this battery life will not suffice for me. I'd noticed sometimes standby life would differ as well.. Sometimes long, other times drained quickly.
[Vibrant Android Development] AngryDinosaur:
mine bricked

using Bionix V 1.2.1

how do i actually flash this?

CWM?

do i need to disable voodoo first?
[Vibrant Android Development] d33dvb:
I have tried several , the first were a set of speakers a standard set of Dell's with a powered sub. I am not sure the impedance, but they are 3 pin. Second were a pair of crappy memorex headphones, also not sure the impedance but were also stereo 3 pin. The last was my car cassette adapter, which is also 3 pins.

It is this model: http://www.americanesuperstore.com/dbt41748.html which it states is 16ohms.

Does the module check for impedance and only allow certain levels?

Also to summarize, no call audio was heard on any device, also the call mic was not working on any output device. I can get audio through music player, but when a call comes in, audio and mic fail to init.
[Vibrant Android Development] hanbaoquan15:
Audio works for me in all situations, just the mic that doesn't work
[Vibrant Android Development] a4 moda:
No no, i'm agreeing with you here.

I'm flashing all ODIN files. I can't get into Clockwork recovery, I can't get into stock recovery. I can't get into ANY recovery. I can only get into Download mode.

For that matter, it doesn't matter which ODIN ROM I flash, none of them boot past the vibrant screen. I see the Vibrant screen, then the phone shuts off. Period.

No recovery.

And I get a charging bootloop too.

Also, i do have the Eugene Non-Bricking ODIN Froyo rom that you have. It supposed to boot you into stock recovery, and you have to use Root Explorer to reboot the phone. So we have the same rom.

Hope that explains it.
[Vibrant Android Development] Otherkid:
Flashed this last night and while charging systempanel showed 35% cpu usage while in lock mode and charging. Previous before showed maybe 3%. Absolutely killed my battery life. I did everyting exactly as it said in the first post. ive flashed this kernel before this update and never had too bad of problems but this was ridiculous. I lost 30% of battery life in standy in my pocket for 2 hours. I know that it couldnt be anything else because I've kept the same ROM and everything the same before I flashed for a week at least.

I will try again when its updated and see what happens.

Edit: and dont know if it matters but I did flash this with 100% battery.
[Vibrant Android Development] CsanMan:
I know how you feel when the phone have issue and you wasted hours trying to find a solution. I'm gonna guess that you have one of the 2 file names below? Most likely the first one:

EUGENE373_SamsungS_Froyo_PDA.tar

Eugene_2E_JK2_Froyo.tar.md5

Both worked for me when I soft-bricked my phones. Let me know and good luck!
[Vibrant Android Development] eunkipark92:
My vibrant handles 1.4 ghz like a champ

bionix 1.2.1 with adw launcher ex
[Vibrant Android Development] drewdude007:
I used this method several times and it won't work as a fix for this problem. I tried to Odin every .tar and .pit combo I could find and used every version of Odin I could find. Nothing works... phone is bricked!
[Vibrant Android Development] a4 moda:
THank you.

Yes, I really appreciate your help. But, like DrewDude said below, i've also tried every possible odin file and combo I could find to no avail.

I did use the same exact files that you have below.
[Vibrant Android Development] misfit1306:
Ok...this may sound goofy but I guess I hadn't paid any attention to that new voice upon startup until just now. Rebooting my phone and turning the lights off and starting to fall asleep when suddenly I hear some strange deep voice mumble something from my phone. It kind of have me the spooks. That's pretty strange sounding when your not expecting it.
[Vibrant Android Development] tduermeier:
I'm assuming you're taking about flashing to jfd through cwm? Because I've had no issues using odin to flash jfd from any file system. Maybe something particular about my setup, or is this the case for everyone else?
[Vibrant Android Development] scrizz:
LMFAO I can't believe people try to odin a whole rom when all the flashed was a kernel.

;)

hehehe

some people are so0o0 dumb. If you're on a phone, it doesn't count.
[Vibrant Android Development] richan90:
That's what I've been saying. Flash a stock voodoo kernel with Odin and you're good. Takes like a few minutes.

Above poster:

I thought if you Odin to stock rom with ext4 enabled it could give you problems?
[Vibrant Android Development] Poser:
If you Odin to stock, you return to stock... as in rfs. Watch the messages on Odin and you will see that it rewrites the fs information.
[Vibrant Android Development] :
thank you, yes odin and jfd will get you to all stock, including file system (rfs). done it tons, should have work.

Anyway, internal won't mount now. eugene's froyo no brick works only partially, still no mount of internal, but phone works.

I'm still under warranty. Is there a warranty thread on xda. I want to see if I can wipe my internal still to remove anything I had on it. don't want t-mobile snooping around.:eek:
[Vibrant Android Development] :
This is not just a kernel, it's also the file system to voodoo (ext4) because most people are coming from a custom rom like bionix or trigger...
[Vibrant Android Development] PaiPiePia:
Anyone else having wifi issues? The wifi connects fine but after you turned it off and then back on in a different location, the phone will try to connect to network that are no longer in range and causes it to hang (instead of connecting to another saved wifi at the new location). I have to put the phone into flight mode several times to "clear" the wifi and for it to work again.
[Vibrant Android Development] gatesmarch123:
Quadrant -2120

Linpack - 18.16

Neocore - crash, crash, crash.

Phone sleep - crash

Uninstalled :(
[Vibrant Android Development] cjggilbert:
Was loving this rom for days, then all the sudden freezes, one sleep of death, and it seems odd but my external sd card would not mount. Had not installed anything new before all this.

Grabbed the kb1 kernel from supercurio's thread. All the problems went away.

Love the DoW kernels, will try again maybe after bugs are worked out.