yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] SimeonAS89:
I'm having an issue. I have not flashed any updates or anything as of Sunday morning, so correct me if I need to update.

But as far as this kernal goes, I'm having lag issues, specifically when playing Angry Birds.

Should I try reinstalling and seeing how that goes? Anybody else having that issue?

Another note: I flashed the HD version because I do take HD videos frequently.
[Vibrant Android Development] BuLLeT_PrOOf_wAlleTz:
Tried the 344mb ram version. Full hd works flawless.
[Vibrant Android Development] EricDET:
Good catch.... After remounting, my nandroid went through perfectly... All others having nandroid hangup problems need to take heed of this....
[Vibrant Android Development] nebur562:
This kernel is great. Im getting 23 hours on this after battery wipe.

For those who wants to know, im on trigger 2.6.1, dow v1.1.1, and jk4 modem..with no issues whatsoever..
[Vibrant Android Development] compuguy1088:
Interesting point, going to check that right now!

Edit: Strike that......system backup was fine, data still is freezing...though now it is not even backing up any of the files of the data partition...yes I did mount the data permission before starting the backup....

Edit2: Tried attempting a backup with the data partition mounted......currently seems to hang at the data partition
[Vibrant Android Development] vnamee:
Nandroid still hangs after mounting /data as well.
[Vibrant Android Development] Mr. Apocalypse:
Ok...i can't disable VooDoo lagfix....go into CWM Recovery...VooDoo..disable lagfix...reboot...all Linda says is

"Convert data partition...Convert system partition"

then it boots right the hell up....what's the problem?
[Vibrant Android Development] bobshute:
When I have had that problem on stock KB1+voodoo (I haven't tried DOW) I have fixed it by grabbing a copy of fat.format from a rom and pushing it to /system/bin. after rebooting recovery I was able to enable/disable voodoo.
[Vibrant Android Development] Mr. Apocalypse:
thanks....that worked....disabling now and hoping back on the Dead Horse...

(that didn't sound right... :o)

EDIT: Now i'm bootlooping and Linda won't shut up....great
[Vibrant Android Development] bobshute:
eeek... sorry it worked for me.
[Vibrant Android Development] ameedi600:
Morfic or anyone here that is good at programming, I as well as many others have bricked our phones somehow. Can anyone at all please help, the problem is that the internal storage is corrupted anf the phone cannot recognize the sd card which does not allow us to flash back to stock. For more info please visit this site http://xdaforums.com/showthread.php?t=957615 and Thank you to all who would at least try to help us. I would recommend looking at the beginning and then go near the end and see what we have gotten so far.
[Vibrant Android Development] Mr. Apocalypse:
its ok...now i got an excuse to Odin so i can try BIONIX FROST!!
[Vibrant Android Development] mrqu1cky:
Camera App Failed!

Bionix 1.2 w/FFC

Hacked camera app from SGS Tools.

I installed both 1.1.1 and 1.4 kernels in hopes of resolving the HD recording.

Duplicate

-Start the camera app, select camcorder, resolution 1280x720.

-Start the recording.

Prior to using this kernel, when I attempted to record, the display would crash and the phone would soft boot.

After the kernel, the camera still shows the live display and shows live update of how many KB is being consumed.

- 1.1.1 shows a white background interleaved every half second.

- 1.4 shows a green screen interleaved every half second.

When attempting to stop recording, I'm either rewarded with a message dialog that says "Camera app failed," but most often I'm given a softboot.
[Vibrant Android Development] vnamee:
I have also noticed that wifi status doesn't stick after a reboot. Normally, I just leave my wifi on and its start default as off now. Not a big deal, just thought I'd mention it.
[Vibrant Android Development] december.underground:
When is that actually going to be released? I keep hearing about and nothing has been released LOL I am getting jumpy over here cause I need me a new rom to flash soon before I go through withdrawals LOL.

0bey <-_->
[Vibrant Android Development] muchelaguito:
I think you are a bit late to the party... :D
[Vibrant Android Development] december.underground:
Yeah your right its been out since the 23rd LOL oh well its still buggy so ill wait before I flash.

0bey <-_->
[Vibrant Android Development] belial20xx:
mobile AP

It seems mobile AP is shot on v1.4 344mb. Shame too. It is really a nice kernal.
[Vibrant Android Development] morfic:
To address FFC issues, i will reduce free memory and increase reserved mem to address wifi issues.

It in itself is pretty stable for me, so the fixes will be in a 1.4.1 hopefully over the weekend. Unless i find something more better, also need a 1.2 and 1.6 or 1.3 and 1.5

Oy, and a UV Kernel that OCs a little too. lot's to build, will continue to bounce between DoW and Trinity work.
[Vibrant Android Development] itsjusttim:
1.6oc? Is that what you ment?
[Vibrant Android Development] DannyDoan:
This is a really dumb question, but how do I get into Voodoo Recovery?
[Vibrant Android Development] Binary100100:
I can confirm with this. There seem to be a pattern where everyone that has corrupted internal sdcard was in fact running this kernel and not necessarily overclocked either. So to all the readers in here, be forewarned that if this happens to you there is NO FIX!

What we are experiencing:

You might start experiencing sudden sdcard corruption. This is to include nandroid failures, media corruption, zip files corrupted, etc.

Your phone will eventually lock up forcing you to do a battery pull.

Once you power the phone back on you will be stuck at the "green android".

Your phone is now toast!

You cannot access any storage device. Internal or external and most roms will not flash and your phone will not boot. Any rom that does flash (by Odin) will not have any kind of storage and you will not be able to download any apps from the Market.

Most of us that this has applied to are sending our devices in directly to Samsung to get repaired/replaced and I'm quite certain that we will be avoiding OC kernels like the plague when or if we ever get them back. :p

And fyi, we are not blaming or pointing fingers at any of the developers. We are all in agreement that it is nobody's fault but our own. Not the developers, not Samsungs, T-Mobiles, etc. Our own. Nobody forces you to flash a seperate kernel. Nobody forces you to take the risks of modifying your device. However we all do feel that it needs to be discussed and others should be warned.

If this does not apply to you and you haven't experienced any issues and your phone is still alive and well we wish you the best and hope that it doesn't happen to you. But at the same time... we envy you. :(
[Vibrant Android Development] jh180:
Against all warnings I went ahead and flashed this, I figured since my Vibrant overclocks well and I used Dow from i9000 source without problems I figured I would be OK. Everything is great! Thank you morfic (mashing the thanks button once I get to my laptop).

Edit: really like to splash screen at boot up, hmm could that be Linda..
[Vibrant Android Development] brandonyoung:
I tried version 1.4, and it seemed to go well for a while. But when I mounted it to my PC and tried to transfer files to or from my PC, Windows explorer locked up. I didn't have the problem on 1.1.1
[Vibrant Android Development] morfic:
Welcome, glad you like it.

Yes, I am behind on some fixes, like increasing some of the reserved memory to fix cams, seems not all vibrants work at the same available memory, possibly due to various cam apps people/roms use.

Soon I get a break with Nexus S being caught up and DoW gets attention.

Hm, just call her Trinity, play on the nexus s kernel by that name.

The old DoW logo everyone hated so much, that was Trinity....

Should you see a HoneyDoW kernel pop up, be on it like white on rice....

It's going to be this kernel in sweeter clothes.

Sent from my Nexus S
[Vibrant Android Development] jh180:
Strange, I could not duplicate this. All is well on my end.
[Vibrant Android Development] tincanman:
Hi morfic,

I have a problem with the touch sensitive keys after flashing your kernel. Everything else seems to be working 100% fine :-)

The long hold of the keys (such as to bring up multitasking menu) does not work as well as stock kernel + voodoo.

I've done a test where I long hold the home key to bring up the multitasking menu with a constant pressure with my finger for 20 tries.

The testing conditions are:

My fingers and key area are clean and dry.

The phone was fresh rebooted and had a level2 ram clear.

ADWLauncher EX 1.2.1 volatile homescreen with home.key binding to "move to default desktop ".

The phone is at stock clock (1000mhz) and is under normal environmental conditions.

I done this test with your DoW 1.4 344 mb ram, Dragon test4, and stock kb1.

This is all under Axura 2.3.1.2.

Dragon: worked 9/20

kb1: worked 18/20

DoW 1.4: worked 8/20

I will be contacting ttabbl about this problem too on Dragon kernel.

Im not sure if this is just my phone or everyone else too. I thought to just bring this up.

Thank you,

tincanman
[Vibrant Android Development] PJcastaldo:
Beast

This is easily the best kernel available if you can handle o/c.. High 19 linpacks, over 2300 quads and awesome battery life with profiles set in set cpu. I know there are people having alot of problems, but I used this alot on and off, no issues... tried all the new kernels.. Non compare..
[Vibrant Android Development] xsteven77x:
That may be an overstatement since it does run the risk of frying your internal sd behind all reprehension...that's why this topic has fallen off the main page.
[Vibrant Android Development] morfic:
It's more that I am not adding news, it runs well and until I update there is no need to bump the thread.

Sent from my Nexus S
[Vibrant Android Development] morfic:
Bull butter, fix is in OP.

But I like your accepting that people do weird things when it comes to Odin.

Once the number of downloads go up, the number of Murphs goes up.

Still under 1%

Sent from my Nexus S
[Vibrant Android Development] gopheer:
Hey Morfic, are you planning on adding voodoo sound v5 soon? Or are you done updating this kernel?
[Vibrant Android Development] Binary100100:
We all tried what was in the OP. We did EVERYTHING! Following this thread wouldn't even allow our phones to boot. It would flash the files just fine, but it just wouldn't boot up. It'll display the "Vibrant" splash screen for about ten seconds and then go completely dark. If you were to press one of the buttons they would light up and not go back off. It would not register on your pc through Odin or adb. I have received mine back from Samsung and they said the problem was a bad "BGA COMPONENT" and they "Replaced PBA" but that's all greek to me since I don't know what any of that is. By the sounds of it it would seem that a component on the main board burned out and they had to replace the entire board. But what could cause that I wonder? Because I'm sure they didn't ship the devices out like that but once they replaced the main board it was repaired and sent back to me. So... if the fix in the OP suggests replacing the PBA because of the bad BGA COMPONENT then I think that is just a little too advanced for the average users. :rolleyes:

Again... I'm not saying that it's anyones fault but those that flashed it. I think that using any kind of modification that is not meant for the device is risky regardless of the odds. Hey... maybe I'm just unlucky. Not that I'm superstitious, but I had the flu and my truck was busted into all in the same week. So yeah... why shouldn't my internal components fry out? That's what normal phones do, right? :p
[Vibrant Android Development] SnowHydra:
Wow, at least ten people asked, nobody answered...

I just flashed it, it doesn't have Voodoo Colorfix.

(It seems to be overlooked these days... I like it because it lets you set the brightness way down. It's great for nighttime use. The "color" fix is only at 100% brightness anyways.)
[Vibrant Android Development] es7241:
Just like my question on battery life it seems to have been ignored o.o
[Vibrant Android Development] SnowHydra:
Well, right when my battery dropped to 95, I kept running quadrant back to back. It went 3 times before it was at 94. All other background processes were off and it was a fresh boot. It was overclocked to 1.4GHz on conservative with SetCPU.

Do with that as you want.
[Vibrant Android Development] morfic:
I tested with my hfi-780, the issue was explained a few posts up, it's not a problem with the audio going into your car's stereo, it's mic related.

I didn't think it was fixed, I was waiting for feedback on the issue.

Feel free to call me morfic, or Daniel, not op :)
[Vibrant Android Development] Sdobron:
Incorrect. This is the old 2.1 color fix. The new one works at all brightness, with that said I don't think it's in this kernel anyway.
[Vibrant Android Development] morfic:
Ok so 1 of 2 parts work. Going to see what keeps mic on when 3pin are plugged, not 4pin.
[Vibrant Android Development] morfic:
Voodoo color not yet included.
[Vibrant Android Development] }{Alienz}{:
:( no support of Xan's voltage app lol.

Otherwise seems great. I'm doing a whole lot of stability testing right now. Managed to crash it once in SetCPU Stability test (crashed after about 20 minutes into the test). Will see if its reproducible. Prolly my phone barely not liking the 1.4Ghz again lol

Battery so far seemed "good" as indicated though have not had it for long enough to make conclusive measurements.

EDIT: Crash is reproducible. Guess its unstable for 1.4Ghz for me. Neocore locks it up just about every time. Please add states under 1.4Ghz. Seems only benchmarks lock my phone lol.
[Vibrant Android Development] Kubernetes:
I had some spontaneous reboots, but the serious issue I had was that the radio was inoperative on several boots. I had to pull the batt and reseat the sim card, and even then it was touch and go. Really looking forward to further iterations of this kernel though, because it ran really well when it worked.
[Vibrant Android Development] amwilliams9:
Been running since this am and DAMN!!!! This is the HOTTNESS!! Everything appears to work fine and VOODOO SOUND is on HIT!! I love it!!
[Vibrant Android Development] ewidtfeldt:
I've had two sleep of deaths so far on this. Great speed but stability is questionable for me. Dk test 4 has been the best for, me lately.
[Vibrant Android Development] lavcoles:
why do i get a bootloop every time i flash this kernal? should i be disabling voodoo? wiping data and cash?
[Vibrant Android Development] ctcpitt:
Awesome Kernel!!!

Thank you Thank you Thank you!!!!!!!!!!!
[Vibrant Android Development] camrs73:
possible minor issue, if wifi is on and you reboot, it gets turned off during the reboot. not a big deal, just a minor annoyance.

using bionix v 1.2.1 and I tried this kernel and Dow14D. wasnt an issue with Dow14D. also it's not a hardware issue because with bionix v and Dow14D my phone was dead stable with never a hiccup for ~400 hours of up time,
[Vibrant Android Development] cjggilbert:
Thank you morfic,,,, stable, clean boot, voodoo sound rocks, 2133 quadrant, been waiting for this
[Vibrant Android Development] playa0506:
Disables voltage readings in currentwidget
[Vibrant Android Development] d33dvb:
This is UNTRUE. It does not work bro.
[Vibrant Android Development] hanbaoquan15:
He already knew that and started working on it already
[Vibrant Android Development] lavcoles:
how is your quadrant so high? i can't get voodoo enabled, but when i overcloack to 1.4 with set cpu i only get like 1200 quadrants
[Vibrant Android Development] Dolphinwigs:
3.5g?

is this one based off of the same one eugene just released a little bit ago thats supposed include the 4g (3.5g) upgrade?
[Vibrant Android Development] morfic:
Can you relax? No, don't "relax", simply stop calling me a liar. I know what I heard......

A call initiated by me went to the headphones.

The mic not working will be addressed.

Sent from my Nexus S
[Vibrant Android Development] jvpde:
Love the kernel, man. It truly is the new hotness at 1.4ghz.
[Vibrant Android Development] morfic:
Nope i9000 JPX source as before.

Sent from my Nexus S
[Vibrant Android Development] duboi97:
This bricked my phone lol and my phones already frozen once in the first 5 minutes
[Vibrant Android Development] cjggilbert:
Its with voodoo enabled, and oc to 1.4
[Vibrant Android Development] lavcoles:
any idea why i dont have the voodoo menu when i flash this? i flashed over bionix, thanks
[Vibrant Android Development] morfic:
I have no cure for freezing bricks and refer you to my chancellor of murph: jlevy.

Expect a call from him shortly.

Sent from my Nexus S
[Vibrant Android Development] lavcoles:
actually can ithink i just have to wait till voodoo is enabled in stock kernal, and then flash this kernal over it, is that right?
[Vibrant Android Development] nick1217:
Does this support BLN pro or just free??
[Vibrant Android Development] morfic:
Hm, that's a tough one, ask the person whose kernel you flashed, it's not anything from the OP.

Sent from my Nexus S
[Vibrant Android Development] morfic:
It works with pro, someone mention something about blinking?

Neldar used to say that's not possible, if it is now, I'll update the kernel patch.

Sent from my Nexus S
[Vibrant Android Development] funeralthirst:
running this at 1.4Ghz on EDT's 2.2.1 stock rom and so far so good. linpack around 18 and quadrant in the 1900s. but most importantly, so far the battery life so far is much improved (though, i admittedly haven't used a dow kernel since 2.x).
[Vibrant Android Development] cjggilbert:
Why is bln not working?
[Vibrant Android Development] Jdom58:
TW very nice work on this kernel :)

Iv'e been running it now for about 4 hours and so far all is quite good, running very fast and smooth with Set CPU at 200min 1400max on conservative, no other settings adjusted.

Quadrant = 2138

Linpack 19.15

Neocore FPS = 64.7

So far no FCs, no reboots, and no problems at all waking from sleep.

Keep up the great work guys :D
[Vibrant Android Development] DreamcastDC:
So is Voodoo enable by default? I just flashed this over my KB1 voodoo enabled Kernel?
[Vibrant Android Development] morfic:
Turn it on with the app from the market.

Sent from my Nexus S
[Vibrant Android Development] morfic:
Thanks.

Btw, Nenamark or an3dbenchxl are better 3D performance indicators :)

Sent from my Nexus S
[Vibrant Android Development] Jdom58:
Thanks Morfic, actually Nenamark came it at 54.3 FPS so I just posted the higher of the two ;)
[Vibrant Android Development] bbm21:
is it possible to remove the 65 fps cap or no
[Vibrant Android Development] morfic:
It relates to the refresh of the screen.

Sent from my Nexus S
[Vibrant Android Development] treyvaporizer:
Battery life is awesome on standby time. My phone seems to love the overclock because it has never been so stable. Or so damn fast!!

Sent from Bionix powered vibrant! If I helped, hit the thanks button!
[Vibrant Android Development] Mannymal:
So this should have the same battery life as stock Bionix? I don't plan to overclock only want it for the Voodoo sound.
[Vibrant Android Development] Jdom58:
Hey FWIW you should at least give it a try, IT IS working quite nicely.
[Vibrant Android Development] glensta:
Yes I tried the aux. test on the car also, same results - just a second confirmation if you need it
[Vibrant Android Development] coolkid893:
wow works really smooth team whiskey does some great work i tell you an that keep on top of somthing till its perfect that dead horse kernal omg what a fail lol but this one fast smooth an battery is like factory
[Vibrant Android Development] cjggilbert:
OOps sorry nevermind, had to reboot, works now
[Vibrant Android Development] treyvaporizer:
Hey man don't hate on eugene. He's doing what he's doing by himself. This kernel is amazing but its cause more than one person was involved. But yea this kernels battery life is amazing

Sent from Bionix powered vibrant! If I helped, hit the thanks button!
[Vibrant Android Development] morfic:
which involved people do you refer to?

Sent from my Nexus S
[Vibrant Android Development] Mannymal:
Installed solely for the sound. Fully charged and will see how long the battery goes.
[Vibrant Android Development] los0325:
Me too
[Vibrant Android Development] morfic:
Los from irc?

Sent from my Nexus S
[Vibrant Android Development] cashyftw:
Battery life is pretty "freaking" good! Good job, only losing 9% per minute ;] haha kidding.. I haven't really tested battery, but the phone is flying!
[Vibrant Android Development] treyvaporizer:
From your original post you said somebody helped you fixed the battery life for sleep time. Lol if you did do this by yourself, well... damn you're awesome

Sent from Bionix powered vibrant! If I helped, hit the thanks button!
[Vibrant Android Development] los0325:
Irc meaning chat room? If no I don't use it.. but Los from the home of the SPURS!!!
[Vibrant Android Development] morfic:
On Irc, #teamwhiskey has a user "los", figured I'd check :)

Sent from my Nexus S
[Vibrant Android Development] morfic:
Yeah, I had someone point at something and I fixed it.

Just checking, cause eugene isn't as lonely as you make him sound, he always had and always will have help......

Sent from my Nexus S
[Vibrant Android Development] ceoesquad:
Bln works but it doesn't blink if u want it to blink download blinky 2.3 and flash it with cwm and it will blink
[Vibrant Android Development] jhepoy:
Could somebody who is experiencing good batt life post their setCPU settings? My setCPU is set to conservative, no overclock, but i lost 20% batt within 30 mins after I flashed this.. (i'm on Bionix 1.2.1)
[Vibrant Android Development] CsanMan:
After I flashed either of your kernels (regular and 1.1), my phone just stays on the green lady boot screen (is that Lynda? lol) forever. Am I doing something wrong? My phone is running on Bionix V and was running on Dragon Kernel.
[Vibrant Android Development] treyvaporizer:
I overclocked to 1.4 and left it on conservative. Then I made a profile and set it max 800 min 200 when screen is off and put it on powersave. Drains 2% per hour for me in standby mode. I imagine if I don't oc it, life would be even better but I prefer the speed

Sent from Bionix powered vibrant! If I helped, hit the thanks button!
[Vibrant Android Development] jhepoy:
i should start tweaking the profiles then.. thanks..
[Vibrant Android Development] scrizz:
no voodoo color?

lol

GJ

thx for the kernel!
[Vibrant Android Development] imitebewrong:
I originally went back to stock kernals from the overclock ones because of the poor battery life, but this really looks promising!

My Results:

Overclocked to 1.4 with SetCPU, conservative profile.

So far I have ZERO issues. Quadrant score was 2088 :) highest it has been with any kernal.

I'll report back with my battery life results, and if I get any sleep of deaths, FC's, etc...

Great job guys, I really appreciate it.
[Vibrant Android Development] DCrozier28:
is it recommended to flash this with a full battery??
[Vibrant Android Development] scrizz:
IT's always best to flash with a full battery.

last thing you want is phone dying in the middle of a flash.

:rolleyes:
[Vibrant Android Development] Poser:
Trigger 2.0.1

1.4 enabled

Quad: 2109

LinP: 19.23

Nena: 53.2

So far stable. Heat is noticeable...but not alarming yet.

Set cpu profiles:

Screen off: power save 800/200 con

Batt <35%: 1000/200 con

Batt <25%: 800/200 psave

Temp >55*: 800/200 peace

1 crash during nenamark, unable to reproduce. Full charge, pulling plug and will report overnight drain (sys panel mon enabled).

So far first experience with dow, very impressive.

Nice work morfic.
[Vibrant Android Development] DCrozier28:
hahaha. no doubt. I know for ROM's its suggested to flash with full battery because it helps battery life in the long run. just not sure if it will affect the battery either way when flashing a kernel??