yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] Lavundra21:
ive been running project core 1.2 since its release date and havent had a single problem. a random freeze here and there the first day but nothing since then. it seems as if the phone works out the kinks by itself and learns how to deal with whatever problem it had. i run OCLF and i still have setcpu installed even though its not needed, i just like to have the option to control my settings.
[Vibrant Android Development] neur0t0xin64:
Hmmm.... that doesn't really help.
[Vibrant Android Development] boodies:
why doesn't it help? you said your phones jacking up at 1.2 so I told you to try 1.0 sounds logical to me.:confused:
[Vibrant Android Development] neur0t0xin64:
I also stated that it is incredibly smooth with JACS Kernel at 200/1200 (which I have reverted to). So it does work perfectly at 1.2GHz. However, I would greatly prefer a Team Whiskey Kernel since they are made for the Team Whiskey ROMS.

In fact the Kernel that totally jacks up my phone is the Core 1.0GHz. The Core 1.2GHz works perfectly, until my phone reaches 100% charge. If I leave it plugged in, it turns off with full charge. Therefore going with a 1.0 Kernel is not so good for me.
[Vibrant Android Development] Dragoth12:
Ffs...did you read or search any of this thread? Your answers are all in it. There are quite a few phones that can't handle team whiskey's kernels for some reason (mine included) that oc just fine on jacs. Team whiskey is working on a modified kernel that will hopefully correct the problems on these phones.......

Mobile Post Courtesy Of Tapatalk
[Vibrant Android Development] neur0t0xin64:
I did search and I didn't find anything on this particular issue and I did read about the modified kernel. I was hoping someone else had experienced the problem and/or knew how to correct it, if it was an easy fix.
[Vibrant Android Development] ajamils:
After experiencing exceptional battery life for few days (18+ hours) my phone has suddenly slipped to the other side of the spectrum and now my battery life has gone from Awesome to terrible.

I took the phone off the charger this morning and its been 7 hours and I have only 40% battery left. This is without ANY usage of the phone (no wifi, no GPS and no phone calls).

Anybody else experienced this ?
[Vibrant Android Development] Kubernetes:
Just stick with JACs if it works for you. I was using it before I moved to Core, and honestly I thought performance was nearly identical. The only reason I chose Core is for the z4mod, which is better than Voodoo IMO.
[Vibrant Android Development] Kubernetes:
Something is running amuck on your phone. Can you see what services and apps are running? What does your battery usage say?
[Vibrant Android Development] ajamils:
Cell Standby = 44%

Phone idle = 33%

Display = 13%

No application is running.
[Vibrant Android Development] adm1jtg:
I am sure this was asked before but don't recall ever seeing an answer in the thread. I am currently running the 1.2 core and not having any issues *knocks on wood* but I was curious why in that kernel there is no 1ghz step. It goes from 1.2 down to 800 or so it would seem. Maybe I am just being way to OCD but shouldn't there be a 1ghz step in there?

That said I am not a kernel designer or even a dev for that matter just a very curious techy who would like to know just cause.
[Vibrant Android Development] Kubernetes:
What about services?
[Vibrant Android Development] vibrantFTW:
I don't know if it has anything to do with the fact I don't screw with lag fixes to achieve false results in pointless benchmarks but Fusion and v1 have ran flawlessly for me. I just flashed it directly over Bionix. No lag, no closing, and battery life finally seems to be where it should be.

Regards,

B
[Vibrant Android Development] MtJason:
This is during work, so checking mail/twitter/facebook/battery status a few times an hour and texting on and off. This is typical use for me, and on most setups I burn through 8-10% an hour. This is the second ROM/app/kernal combo I've stumbled across where I only use 3-4% an hour. I'm going to be reluctant to change anything if this keeps up.

DRM Protected Content Storage 2.1-update1 (this is listed twice in Titanium, froze them both

DRM ContentLauncher 1.0
[Vibrant Android Development] TheExpertNoob:
I was having this same problem, I noticed it after I flashed Fusion with Core (1.2GHz) on top of JI6.... I used ODIN and reverted back to JFD AND repartitioned then flashed Fusion w/ Core 1.2GHz shortly after I installed my FFC and FFC wouldn't work so I installed Jac XMOD to get FFC to work and my battery life is at 55% with 7 hours of its usual use where as before I had maybe 5 hours of life with almost all 'sleep' time.

So i wonder if flashing Fusion with CORE on top of JFD vs JI6 has something to do with it

or

its a kernel thing.... cause it seems Core v1 has a sleep issue, but speed145a over in IRC reports he has excelent battery live with CORE v1 w/z4

so

how much difference is there between CORE with and without z4?
[Vibrant Android Development] fearmonkey:
Is there some overriding technical reason why the FFC hasn't been enabled? Unless you've change a LOT of stuff, it should just take compiling with "CONFIG_VIDEO_S5KA3DFX=y".
[Vibrant Android Development] ajamils:
I see the following services running:

- SnsPhotoService

- OmaDrmConfigService

- Download Manager

- SnsService

- Swype

- DMService

- PoweAmp Player Service

Come to think of it, the only new thing that I recently installed is the PowerAmp player. Could it be the culprit ?
[Vibrant Android Development] moonfire711:
You tell us. Remove it and see if things get better.
[Vibrant Android Development] Duce HD2:
Man I sure hope my phone is going to grow some balls (even though so far so good) because the battery is outstanding with this kernel.

10 hours of Moderate to heavy use today, 1 hour call, weather, 3 email accounts synching every 2 hours, facebook every hour, quite a bit of news reading and XDA app, and of course I have a data plan.

Sorry, don't know way the picture is so freaking big....normaly the quality is real ****ty.
[Vibrant Android Development] Kubernetes:
OmaDrmConfigService.

It's one of the services connected to Media Hub and it will drain your battery. Epic users figured it out a few weeks back: it won't let your phone sleep properly because it pings the CPU constantly.
[Vibrant Android Development] kuhan:
I have similar battery life with MUCH less usage AND JuiceDefender installed
[Vibrant Android Development] atlaswingpasaway:
I also disabled the 3 drm apps present in the titanium backup. Im not sure if im seeing some immediate effects yet. So will i have to freeze them every boot?

Im happy with the battery life, stability and smoothness so far. All that except the music playback skipping i mentioned before.

Bring on the new kernel!
[Vibrant Android Development] rembonjaski:
I tested and can confirm they stay frozen after rebooting.
[Vibrant Android Development] henreeg:
From the 2 kernels in the front page, which one are you using?
[Vibrant Android Development] Duce HD2:
I recently flashes Bionix Fusion w/core 1.2GHz installed. But I also did an ODIN to start fresh, maybe that helped.
[Vibrant Android Development] Duce HD2:
Where is the fusion thread? I can't see it out there! Is there an update on the way?

**never mind, it came back.
[Vibrant Android Development] moonfire711:
Thread....slowing....down. Need....something.....new....
[Vibrant Android Development] infared:
where is everone.... we need some life in here!!!
[Vibrant Android Development] addison892:
Okay, noob question w/noob problem. I have looked in the forum, and on a few threads for this and I am unable to find my answer...

My phone will not run OC and will not run Project Core 1 or 1.2. I have accepted this. Can I flash JACS kernel back or do I have to reflash Fusion 1.1 to get the JACS kernel.

If there is a link to a download will someone please respond with it?

Thanks for your help.
[Vibrant Android Development] moonfire711:
You can flash a kernel over a rom without losing your data. Safe practice overall is to flash from fresh stock Rom, but you don't have to.

http://xdaforums.com/showthread.php?t=791478

Do some reading and find the right version for your phone. It'll be good for you.
[Vibrant Android Development] cashyftw:
Where....is....something new.....
[Vibrant Android Development] timafey:
everyone probably just dropped this POS and picked up the new myTouch 4g!

haha jk :)
[Vibrant Android Development] blackoakx22:
Just to double check this is a2.1 kernel right? I'm going to try out some froyo and I need a2.1ROM and a 2.1 kernel as well
[Vibrant Android Development] moonfire711:
Yes, it's a 2.1 Rom, but not a stock ROM in case that is what you are looking for.
[Vibrant Android Development] moonfire711:
If you can, please post a link to your logcat in the future so as not to take up so much thread space. There have been many people reporting similar issues with freezing on the core kernel. If that is you, then try another kernel for now. The team whiskey devs are working on improving the kernel and making it more stable for more phones. Thanks for your insight.
[Vibrant Android Development] sombionix:
Thee would still be banding in the rear camera. This issue still has not been resolved by any developer.
[Vibrant Android Development] blackoakx22:
I know that it is a 2.1 rom I just didn't know if the core kernel was a2.1 kernel
[Vibrant Android Development] blackoakx22:
When people say banding what do they mean? Did the rear camera not work at all?
[Vibrant Android Development] blackoakx22:
When people say banding what do they mean? Does the rear camera not work at all?

Sorry for the double post. Waky browser
[Vibrant Android Development] moonfire711:
Sorry, I misread your post partly because I am bouncing between this thread and the fusion 1.1 thread. Yes, this kernel is based off the ji6 if I am not mistakin.

If I didn't answer your question, then I don't know what the heck I'm talking about.
[Vibrant Android Development] blackoakx22:
Lol its ok I know how hecktik it can be switching back and forth but you did answer my question. Thank you for your help once again
[Vibrant Android Development] dbacchus:
Removed nvm
[Vibrant Android Development] ajamils:
OK I stopped it. Lets see what it changes the battery life. What I do not understand is that, since this app is included in the ROM, it should have been running at the time when I was getting great battery life as well. So what could have made it an issue now?

Also, is there any app that can specifically show which service is draining battery?
[Vibrant Android Development] kangxi:
I'm having this problem right now also. Music freezes when switching songs in the library and also Zenonia will not start. Quadrant stops at the 11/12 part which is video decoding.

I ODIN back up stock JFD then did a clean install of Bionfix Fusion with Core v1 and it is still happening. Kind of disheartening.
[Vibrant Android Development] moonfire711:
Actually, I think the fusion rom is based off of ji6 and perhaps the kernel is based off of original jfd.

I did it again. Sorry.
[Vibrant Android Development] a4 moda:
No problem.

I've come across threads where troubleshooting was not done if a log wasn't posted. Guess I jumped the gun there. I'll post elsewhere for future reference.

Thanks
[Vibrant Android Development] adrianr514:
i need stock vibrant kernel i may have messed up and im stuck in a bootloop and dont know what to do help please ASAP!!
[Vibrant Android Development] moonfire711:
http://xdaforums.com/showthread.php?t=734475

If that was fast enough for you, make sure to donate to my slurpee fund.
[Vibrant Android Development] benjaminh98:
OK, I've searched using as many combinations of words that I could think of to lead me to a solution, so if I missed it I apologize.

I was originally running Bionix Fusion with JAC's OC kernel. I am know running the Core, I think.

I disabled Voodoo, prior to the flash of the new kernel. I rebooted into recovery and applied the zip file. Everything seems to be ~~normal~~, but I cant re-enable Voodoo and my Quadrant scores are ~1000..

Any help?
[Vibrant Android Development] moonfire711:
Core does not contain voodoo. You will need to apply voodoo to your phone now that you have core kernel. Edit: Meaning you need a different kernel.
[Vibrant Android Development] adrianr514:
ok need major help.. still lost with all that
[Vibrant Android Development] atoz350:
You can't. Voodoo is a different kernel altogether. The only lag fix that works currently is RyanZA's Ext 2 lag fix.
[Vibrant Android Development] moonfire711:
Ok, if you say so. :rolleyes: I guess I was not clear on how I worded it. "Core does not contain voodoo." Should have left it at that.
[Vibrant Android Development] fearmonkey:
Depends on your definition of "works". Google "camera banding" and you'll get a good definition.

Right, there would still be banding. But it's so trivial to implement and only those with the ffc would see the banding. I don't see a downside to enabling.
[Vibrant Android Development] moonfire711:
I got you covered in the PMs. Considering this has been talk about to death.
[Vibrant Android Development] adrianr514:
got it back thank you
[Vibrant Android Development] moonfire711:
Shiz, I just sent you a novel in the pm's.
[Vibrant Android Development] jonwilly:
So my phone can't handle the over clocked kernel. My temp fix that seems to work is to use setcpu set to 800. Tried to flash the other core kernel 1.0 but won't install. Phone just hangs on re boot so I flash back to the 1.2 version with temp fix. Ideas how I can get the 1.0 core kernel to work?
[Vibrant Android Development] moonfire711:
Did you try redownloading it? If you got a bad download, then it won't flash. Otherwise, your phone probably just won't work with it. Some phones just don't seem to like it.
[Vibrant Android Development] SkOrPn:
lmao moon, dont you just hate when that happens?
[Vibrant Android Development] jonwilly:
I have tried to re flash stock and the core 1.0 and cant get boot past the vibrant screen. Go back to core 1.2 and I boot right up. So strang because on the stock kernel I could hear boot sounds but just show the vibrant screen. I'm seem to be stuck on this kernel. Ideas?
[Vibrant Android Development] Duckblind:
ultra stupid question im sure... How do i know the flash worked? My kernel still says 2.6.29.... did i fail?
[Vibrant Android Development] amandadam:
If you flashed it,you now have it as your kernel and it will say 2.6.29.
[Vibrant Android Development] SkOrPn:
probably not, it is based on linux kernel 2.6.29. I think if you saw the blue text on the screen moments after flashing then you did it correctly.
[Vibrant Android Development] mikeyinid:
So you cant ask for help on this forum?...you think I would have asked if I was able to find a straight forward answer myself? I have nothing but time, and I cant find it. Forgive me for asking a probably VERY easy to answer question...
[Vibrant Android Development] mjnbrn:
Just installed. Heading to bed. Will see what happens tomorrow. Switched from JACs.

Thanks to the devs for all the free roms :)
[Vibrant Android Development] SeanFloyd:
Bionix Team -

Thanks again for yet again another quality delivery.

Would someone kindly explain the benefit of running the z4 mod vs. say this + Voodoo?
[Vibrant Android Development] Yellow C6:
Installed and running bionix final. So far so good. Pandora seems to work without locking up. Fast and smooth. I'm going to bed now and will mess with some more in the morning. I'm sure this thread will be 100+ pages by then. Thank you Team Whiskey.
[Vibrant Android Development] joshuapurcell:
I wonder if this kernel reverts the SSL fix for fusion 1.1? I ask because I know for sure it reverted the blue battery mod...
[Vibrant Android Development] hockeyrcks9901:
Everything is great so far. Running fusion with this new kernel and haven't had any issues yet. Swype seems to recognize my inputs better but it's probably placebo...

Came from jac's with voodoo and I don't see much difference. Benchmarks are a little higher than what I got without voodoo, no noticeable differences other than benchmarks. I'll post again if I come across any issues.

Typos and other gibberish courtesy of Swype
[Vibrant Android Development] implosive_disgorgence:
awesome kernal, this did however lockup my phone during any neocore run i tried to do
[Vibrant Android Development] FRuiTBoOT:
It didn't revert my battery mod. Still blue segmented.... weird.
[Vibrant Android Development] Bugdog:
Just flashed this on Anderdroid's AOSPish 1.4, and seems to be working great so far. Flashed over JACs OC/UV. Uninstalled set cpu - not sure if that was necessary, but whatever -and no issues so far, very smooth. Thank you!
[Vibrant Android Development] sombionix:
That doesn't make any sense. Backward support files are already included in the rom.
[Vibrant Android Development] CompConfig:
First of all Sombionix and the entire Team Whiskey I want to say thank you once again for your great work. I was having severe flash withdrawals so this will hold me a little longer till 2.2 comes out.

Now I have flashed this kernel and I ran quad and linpack several times with my old 1.2 kernal and then several times with this new kernel and I have say with all due respect…….. Are you freaking kidding me??? My scores on both tests jumped on Linpack from 8.6 to 9.7 on Quad from 850 to 1045! The phone has been running super smooth and very fast.
[Vibrant Android Development] sombionix:
People, this doesn't change anything other than the kernel. Lol.
[Vibrant Android Development] turbosix:
the installation guide link is in every team whiskey rom post dude:

http://www.teamwhiskey.com/installation-guide
[Vibrant Android Development] smashpunks:
Damn, this thing is fast... Awesome job guys, voodoo what?
[Vibrant Android Development] StefanB86:
I answered your question on page 7.
[Vibrant Android Development] s0niqu3:
Hi,

If you extract and open the update script, you can see that this is literally, only flashing the kernel/zimage via redbend_ua:

show_progress 0.1 0
copy_dir PACKAGE:kernel_update TMP:/kernel_update
set_perm 0 0 755 TMP:/kernel_update/redbend_ua
run_program /tmp/kernel_update/redbend_ua restore /tmp/kernel_update/zImage /dev/block/bml7
show_progress 0.1 10

it doesn't include or touch any system files at all, and so far the battery mods I know of for the vibrant work by modifying /system/framework/framework-res.apk

Anyway, so this can't really revert or break any mods you've applied, unless you either get a bad flash and need to use ODIN to restore for some reason, or if you were using mods that were kernel specific, like voodoo, z4mod, backlight notifications, aosp bootanimation.zip support, etc.

And to the OP/TeamWhiskey: running this on eugene's hybrid_r4 (sorry, absolutely love the aosp dialer and contacts and despise touchwiz, else I'd be running fusion) and it runs great so far, very smooth, can't wait to see the battery life!

Also, do you have any plans to incorporate the backlight notification mod, or aosp bootanimation support?

Thanks for the awesome kernel, cheers!

=)
[Vibrant Android Development] blackerwater:
This happend to me also. Must be running stock ji6 like me

Sent from my vibrant
[Vibrant Android Development] allthrottle:
So far not bad either. Quadrant jumped from in the 850 range with jac xmod/fusion at 1.2ghz to around 1100 with just the kernel change. There does seem to be slightly more lag than the jac w/voodoo, but it's seems like it's clearing up the longer the phone is on.

Sent from my Team Whiskey Powered Vibrant
[Vibrant Android Development] dbacchus:
I was trying to flash from *stock* ji6 rom.
[Vibrant Android Development] sombionix:
Just so everyone is aware, ALL custom kernels are built off JFD. That'd the only source we have. Just an fyi.
[Vibrant Android Development] Dragoth12:
Check my sig. It's a re-link of what is posted in the Vibrant Directory as updated 3 days ago. Some good info on Battery life in there.
[Vibrant Android Development] Duckblind:
Yes i did!.. Thanks for the quick reply!
[Vibrant Android Development] RaymondPJR:
FFC banding

I would stay more focused on whether or when support for the FFC will be included in a TW ROM. I have been following that mod thread and think they are on the brink of a solution. They have to figure out how to turn off one cam while the other is in use, or alternatively lower the voltage to one cam so that the other gets enough power. On the Vibrant they both draw power so neither gets enough which causes the banding. I'm waiting for a TW Rom based on Froyo with FFC support before I do the mod. The cam has been acquired and is waiting.
[Vibrant Android Development] eortizr:
Battery life on this Rom is insane,,, 48 hours,, still 10% left....:D
[Vibrant Android Development] blackoakx22:
even if that was jfd is still 2.1 not 2.2 therefore i am pretty sure it will work
[Vibrant Android Development] Duce HD2:
And this relates to Project Core V1 thread how????
[Vibrant Android Development] blackoakx22:
i searched and i see what you are saying yo can still use the rear camera to take pictures but you will see a line through the image right?
[Vibrant Android Development] jonwilly:
Anyone? Tried flashing stock and the 1.0 core and just freezes on boot. Have tried several times. Flashing using clock works
[Vibrant Android Development] moonfire711:
Have you used Odin to go back to stock kernel and rom with a fresh partition and then flashing custom stuff again? This could easily solve your problem.
[Vibrant Android Development] Duce HD2:
Are you using CWR to flash? (I guess you are)

Is should work - place Core 1GHz on internal SD>Reboot into recovery with CWR>locate Core 1>flash>reboot.

Maybe you need to ODIN back to stock and reflash, might be a bug floating around.

In case you've never used ODIN: http://xdaforums.com/showthread.php?t=734475
[Vibrant Android Development] moonfire711:
Learning Odin

Ok, do you need to learn Odin? It's easy. Just download Odin here:

http://xdaforums.com/attachment.php?attachmentid=428351&d=1288241735

Now you need the two files to wipe your phone and start fresh at a stock rom and kernel. Here are the links to the files:

www.justanotherdev.slackdev.com/s1_odin_20100512.rar

www.justanotherdev.slackdev.com/T959UVJFD.tar

Now, you need to un-rar the Odin file and the s1_odin_20100512.rar file using winrar.

Start Odin and get your phone into download mode (if you don't know how look here): When phone is off, hold in both volume buttons and power button for 10 seconds or so.

http://xdaforums.com/showthread.php?t=734475

That last site will also walk you through all the other steps, but I'll do it again. That site also contains the two links to the files you need, but older version of Odin.

Once your phone is in downloading mode (big yellow triangle with android in center) and plugged into the pc and you see a yellow box with a com# in it on Odin, then you can load that .tar file into the pda place holder and the .pit into the pit place holder. Then hit start and wait for your phone to reboot. When it has rebooted, wait a while for it to fully boot. Then you can reboot, re-root, re-flash, and re-enjoy your phone. :D
[Vibrant Android Development] wondringsoul:
There are some of us, myself included, that have a ffc and would like it to work with core. As for those asking about banding, it's really only noticeable in low light settings, but support in core would still be nice.
[Vibrant Android Development] Duce HD2:
Maybe I'll give it a shot one of these days, but first, I'd like to get a refurb to use as a guinea pig for my experiments...
[Vibrant Android Development] wondringsoul:
I would love to have my modded vibrant and then one running pure stock to compare to and just have as a fail safe.
[Vibrant Android Development] speedysilwady:
this is odd even the 1ghz kernel freezes on me in both final versions of bionix and fusion.
[Vibrant Android Development] bigragu:
My phone is struggling on this one. Lots of freezing. Going back to KK for now.