yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] Lakers3408:
Overkill is just that it overkills my phone. It runs great for a few hours (6-7) then my phones goes into a coma, over and over, cant wake my phone from the coma. It also gets the kernel panic when I turned the phone off to charge, it showed the big battery for about 2minutes then kernel panic, it did this every single time I tried to charge my phone while off.... These ULF kernels, from what I read, corrupt the phones file system, causing major problems. Its a very bad kernel to use, major issues.

Yes I removed the mtpx file, did not use UV or SetCPU
[Vibrant Android Development] eugene373:
Sorry I've yet to update it, but like I tell everyone there is no need for this to begin with....

I only suggest using JFS on Data & that's it..

lmao... 1Ghz Min??? That was a bad thought to start with hehe..
[Vibrant Android Development] calvinpreston:
eugene, what kernel are you doing right now? is it like A14 with a A_Overkill battery? that would be awesome.
[Vibrant Android Development] eugene373:
Correct... A13 with Battery of Overkill
[Vibrant Android Development] naughtyboy119:
Hi there, i put A14 on my phone and try to do some tweak. After reboot, it give me a lot of error and can't boot at all. I was trying to ODIN back to stock but ODIN just stuck at SetupConnection and on my phone have an icon that tell me the phone is not connected to the computer.

Can anybody help me to recover my phone to stock. Thank you very much
[Vibrant Android Development] eugene373:
OP Updated with New Kernel... Battery = Awesome

Read OP Before USING
[Vibrant Android Development] hnrclothing:
When trying to install kernel threw flash clockworkmod it goes to the 2e recovery, then it looks for an update.zip. After it finds an update.zip it seems to unpack quickly then it will then go to flash clockworkmod recovery. I can try to install from sd from there but it unpacks quickly and doesnt seem to work. Nothing changed with the clocking in OC or setcpu. I tried this will a couple different kernels. Any help?

Edit: I guess 3rd times the charm. It finally worked.

I went into "About Phone" to look at something. It is now frozen. System feels a little jumpy before this too. In the benchmark it was jumpy for the 2d/3d tests from 9fps to 55fps.
[Vibrant Android Development] qreffie:
Per the notes that TW typed up when they released the ULF kernel I think that's the rout you need to take.

Looks like these kernels have that 1 in 20 chance of soft brick too eh? Still rather tempting though. I may try my hand at it later on tonight.

Edit: Screw it, I'm flashing A9

Edit 2: Didn't brick!!!

Edit 3: Weird, I rebooted and it worked, then went into recovery to try to install the JFS lagfix but it was the same exact menu and nothing new was there so I just selected reboot. Then my phone just hung in the marked and I couldn't get use the phone's data or wifi. Market, Browser, and even Speed Test just hung and wouldn't connect on either. Then I tried rebooting, the phone stuck at the I9000 screen and I thought oh crap I've got a soft brick, then I tried to manually booting into recovery which was now updated. I selected a lagfix to install and everything looked like it was ok, but now the phone won't boot past the Galaxy S screen, so looks like I did brick it. Time for some Odin.
[Vibrant Android Development] eugene373:
A11 & A12 OC/UV now Posted

A10 Link is Now Fixed as well.

~Eugene
[Vibrant Android Development] jumaaneface:
Running a12. everything running smooth so far. Have you had the chance to look into the sd issue ?
[Vibrant Android Development] eugene373:
What SD issue? I'm not having any..

~Eugene
[Vibrant Android Development] jumaaneface:
My external sd is mounting as a cd drive..
[Vibrant Android Development] eugene373:
This has been asked before in other thread.. You need to edit the Vold.fstab in the etc folder to Fix that.
[Vibrant Android Development] diazf09:
So wich kernel has the best battert.. Im literraly watching my battery go down...

Sms vibrant black body glove

Rom-macnutR2 kernel #53

Latest cwm

Black Htc G1

Sparksmod1.7

Latest radio death spl

Oc kernel 617mhz jit enabled ram hack
[Vibrant Android Development] eugene373:
Might just Go to another Kernel then... Some work Fine while other have Horrid Battery Life.. Mine however is Doing Great.
[Vibrant Android Development] MINUS Stl:
Eugene, I'm assuming we use the Voltage Control app for the UV settings? Any recommendations/guidance on voltages?
[Vibrant Android Development] Reyland:
please, how to do this :confused:??
[Vibrant Android Development] matt_stang:
I think Eugene said it's only necessary if you are using a ROM other than R12. I recommend just flashing R12

You won't regret it.. ;)
[Vibrant Android Development] jumaaneface:
Sombionix posted a flashable zip in his obsidian thread op
[Vibrant Android Development] Reyland:
thanks but it didn't resolve the issue!
[Vibrant Android Development] t1h5ta3:
theres just some stuff that if you have to ask how to do it, shuld tell you you shuldnt....

this is an alpha , ie: buggy, prone to breaking things. do you know how to fix it?
[Vibrant Android Development] Whitehawkx:
The new zip Sombionix posted fixed the issue for me...
[Vibrant Android Development] Reyland:
thanks for your help, your post was very helpful !
[Vibrant Android Development] Reyland:
the sd mounting as cd drive issue??
[Vibrant Android Development] Maverick777:
Yea, update.zip fixed it for me as well. My computer is able to read/write to both SD cards now.
[Vibrant Android Development] jumaaneface:
Try wiping dalvik cache after flashing.

Edit: anybody suggest some settings for the uv app. I caused the kernel to go into panic mode and had a few lockups.
[Vibrant Android Development] Whitehawkx:
I UV'd the bottom three (800, 1000, 1200) by -25. I tried -50 on 1200 and got lockups. Best way I've found to test it is with the gallery. If the gallery doesn't lockup then you are (probably) good.
[Vibrant Android Development] ginzberg:
Eugene, with all due respect... and I genuinely mean this. I am a donator that has followed your work on the Vibrant from the beginning...

I do believe that you may be misunderstanding the /system issue with ULF 0.3. The corruption is not occurring because users are converting their /system mount point from RFS to another file system. The issue is that because the 0.3 code fails to mount the /system node as check=no, the directory can become corrupted over time as standard file system checks may misdiagnose an issue and attempt to correct when it should avoid the directory altogether. It is inherent to all kernels based on this code unless you had manually edited the code to add in the check=no flag. From my understanding, ULF 0.4-pre does include this fix.
[Vibrant Android Development] }{Alienz}{:
Using the new Stock 1.256Ghz Kernel and love it. Only issue is like Eugene says, it occasionally freezes the phone at 1.256. Easily remedied by setting it to 1Ghz max as stated in description. Everything else seems to be working.

IT DOES NOT LOCK UP AT 100Mhz anymore! I did several tests where I locked min and max at 100Mhz and let it sleep. It NEVER locked up so it's great.

@ Eugene: Am I right the 1.256Ghz occasionally freezes due to voltage? Would a slight volt bump for that frequency stabilize it?

Also, would it be possible in future versions to incorporate the 341MB RAM fix and 3.0 batt voltage drop into the Kernels?
[Vibrant Android Development] eugene373:
Voltage on the CPU is fine, I need to fix other clock rates at this point.

341MB yes soon... Still Ironing out the 3.0v after some Feed back it's set to 3.30v now, by Default it was set to 3.60v
[Vibrant Android Development] scrizz:
Good to see you have things covered.

You never disappoint!!!!
[Vibrant Android Development] }{Alienz}{:
Ah. Sounds good. Sounds VERY VERY good actually haha.
[Vibrant Android Development] jdkackley:
So far..............

Latest OC kernel working very well so far. No hangups or freezes yet. Installing lagfix now then will charge her up and report back later. Good Work EUGENE!

MY GAWD! my sig is sooooo old!
[Vibrant Android Development] Sh8dyDan:
I am currently running a fresh install of R12 with the included 106 kernel.

I recall earlier, it was recommented to remove mptx file for the A_OVERKILL Kernel, is that still the case with A_Stock_1256 Kernel?

Thank You
[Vibrant Android Development] JeremyNT:
I finally got the sleep of death on A_OVERKILL even with the clock capped at 1GHz.

For now I've just switched back to a stock 2.2 kernel, this is just a bit too sketchy to be my daily driver at this point.

Also, FWIW, Despite all the warnings about ULF kernels breaking your ability to flash to other kernels, I had absolutely no issues switching back to stock.
[Vibrant Android Development] TunedFish:
The new kernel freezes during Asphalt 5 at 1.256GHz. I reverted to A_Overkill set at 800mhz to 1200mhz. It runs pretty good. Gonna test out battery life at those settings.
[Vibrant Android Development] deez1234:
Eugene I am interested in the option to change the bootanimation.zip. Just wanted to give you more feedback. Would love to add a custom one here and there. Hopefully demand for this is high!
[Vibrant Android Development] jdkackley:
+1

tenchars
[Vibrant Android Development] eugene373:
Coming soon... Tired of making several kernel's for testing... Another test kernel Coming in a few... Set to 1.12GHz and should be stable for all.
[Vibrant Android Development] }{Alienz}{:
I'm donating tomorrow lol. You are amazing. Period.
[Vibrant Android Development] xspeed9190:
so as of right now the current A_Stock_1256 Kernel supports as low as 3.30 v but we will have one that goes down to 3.00 v when its fixed up.
[Vibrant Android Development] yungballla6:
your kernels are amazing but i always get the sleep of death using any of your new "A" kernels, does your new kernel fix this issue. thank you.
[Vibrant Android Development] cashyftw:
1.3 ghz is working great, the only reason i'm going to 1.256 is for battery life.
[Vibrant Android Development] nebur562:
I've noticed that when my phone is plugged in the charger, I don't get the no wake issue. But as soon as I unplug it and let it go into sleep mode it doesn't wake up.
[Vibrant Android Development] yungballla6:
flashed eb kernel "soft brick" advise no one flash over his A kernels.
[Vibrant Android Development] eugene373:
What are you Smoking?
[Vibrant Android Development] m00nshake:
Another kernel in a few hours?! Is it just me or is Eugene on fire today?
[Vibrant Android Development] yungballla6:
lol well i was running macnut 12 w/ a14 kernel. and in your post you said that the eb kernel was stable right? well i flashed the eb kernel and then it soft bricked me. i didnt have any lagfix on or anything. what went wrong. btw i wasnt like attacking you or your work, your effing amazing
[Vibrant Android Development] eugene373:
I use the Kernel all the time? no issue's at all.... lol, I know you wasn't attacking me, just didn't understand why you would have issue.. This is the first time anyone has had an issue..

@Everyone Else

Stable OC kernel + Battery Fix now Posted... Enjoy & i'll get around to posting Bootanimation.zip support sometime tonight
[Vibrant Android Development] ilaf0106:
Will this work with aospish 1.1 rom?

Honk! If you want to see me flash!
[Vibrant Android Development] JeremyNT:
I've been using it with AOSP ish. Only issue for me has been hard lock on sleep, but that's kind of a big issue - not sure whether the latest kernel has this issue resolved (and it may be specific to phone hardware as well).
[Vibrant Android Development] ilaf0106:
Yeah I'm going to try the newest kernel see if it still has the wake issue I'll post to see how it goes on aosp ish rom

Honk! If you want to see me flash!
[Vibrant Android Development] calvinpreston:
the A_stock_1256's battery is not fixed? what's the difference of A_stock_1256 and A_stock_1120? just the speed or even the battery?
[Vibrant Android Development] Whitehawkx:
This is b/c you flashed from a ULF kernel to a non-ULF kernel. This is what the /system corruption does... sometimes you will brick and sometimes you won't. If you use ULF kernels it's a gamble. It can be fixed, in fact, someone posted in great detail what is required to fix this and stop it from happening a few posts back.
[Vibrant Android Development] ilaf0106:
So do we even use set cpu or does it do it by itself?

Honk! If you want to see me flash!
[Vibrant Android Development] m00nshake:
If Eugene gets this new stock kernel with boot animation support up tonight I'm going to have a very very happy Thanksgiving!
[Vibrant Android Development] ilaf0106:
So far! Good I'm not getting wake issue s now to run some battery test! !

Honk! If you want to see me flash!
[Vibrant Android Development] badaphooko01:
Will this work on the Odin froyo leak?
[Vibrant Android Development] Tynen:
I was running a14 with onyx 4. Was working well. I did however have to change OC to 200-1200 isntead of 100-1200. Seemed to come back more often from lock screen.

I'm about to flash a_stock1256 with obsidian 5
[Vibrant Android Development] yungballla6:
anyone test if this is "sleep of death free" i really hate to keep having to take battery out like every hour. also battery life? i know A_Stock_1120 Kernel was just posted but im just curious.
[Vibrant Android Development] jzero88:
I haven't had any sleep of death on the 1120 kernel, but yet to see any change with battery stats.
[Vibrant Android Development] Reyland:
stock 1120 kernel running very fine on Axura 2.0.5!
[Vibrant Android Development] Lavundra21:
I'm running the 1.256 kernel and its nice and stable.. Not a single problem at all.. I'm liking it.. And I'm running onyx 4.2 with ulf overkill.
[Vibrant Android Development] miguelmondo:
Just installed 1120 with AOSPish ROM. Will report back if there are any issues.

I was running A11 and loving the speed. This kernel seems to run at 15+ mflops whereas A11 ran at 16+ mflops.

Also, what's the easiest way to determine if my lagfix options are still set?
[Vibrant Android Development] Fedburin:
Meaning battery life is still like 4 hrs?
[Vibrant Android Development] Fedburin:
Can I install this over your previous Voodoo kernel w/t Voodoo enabled? Not the ULF one your original Voodoo port.

Edit - It worked.
[Vibrant Android Development] firefly6240:
I had more than 4 hours with it set to min 1200 and max 1200 same with the overkill kernel, more than 4 hours with 1300 min and 1300 max. :-/
[Vibrant Android Development] Fedburin:
lol - with A14 I was getting around 4 hours. It was atrocious. My phone was hot and it was eating the battery. When the previous poster said his stats hadn't changed I was just wondering if that was a good thing or a bad thing.
[Vibrant Android Development] eugene373:
Need a Few Testers in a Bit... A. Must know how to Use ODIN if things Go wrong... B. Must have Lock-ups / Freeze Issue's at 1.2GHz ( Testing for Stability for those unlucky people) .. C... install and then Uninstall a Lag fix, then revert back to EB kernel to check if corruption is Fixed on system
[Vibrant Android Development] rsfaze:
I can do that ... hit me up my man.
[Vibrant Android Development] JeremyNT:
I'm game...
[Vibrant Android Development] cashyftw:
I can do this also.

Sent from the speed demon
[Vibrant Android Development] daenigma:
Like I said on your forums (AKA Maximuh), I would love to help.
[Vibrant Android Development] m00nshake:
I have had freezing at 1.2 with A14 and A Overkill. I can also use Odin. I will test for you, PM me if you need my assistance.

m00n
[Vibrant Android Development] eugene373:
Okay... I just Had to ODIN myself... I can Personally confirm the /system Corruption is now Fixed... All A Series Kernel will be removed due to this...

btw, there is no Point in new Source for the Fix... It just a Mount Flag that fixes it..

~Eugene
[Vibrant Android Development] m00nshake:
Can't wait, Eugene. Thanks so much for this... and if you still need testers I'm available
[Vibrant Android Development] GreenDroidX:
I second this question tired of reflashing software. Can i just flash the kernel?
[Vibrant Android Development] m00nshake:
Home from work and ready to test!
[Vibrant Android Development] salvador3:
I installed the EB Productions stock kernel using Clockwork in the reboot mode. I manually selected the zip file for installing the update.

How can I check/verify if I installed it correctly? I went to "About Phone" in the settings and see my kernel is version 2.6.32.9 is this correct?
[Vibrant Android Development] Fedburin:
Yeah - the problem is trying to flash back. I would wait until the next release. Should be out shortly.
[Vibrant Android Development] eugene373:
Okay... B Series is now Here due to /system mount issue's fixed in ULF Kernel's..

If you flash to a Stock Kernel ( Hence EB-Productions Kernel ) and you get no Boot... You will need to ODIN to stock first to fix the hang issue...

It's late, so going to hold off the 1.2 kernel...

Mainly just wanted to get the Soft brick issue taken care of first.. So now it's Fully safe to flash and Stock Kernel & any Kernel that has the Mount issue fixed in the ULF Kernel's as well...

But, likely I'm the Only one so far to fix this issue for the Vibrant again.. I'm sure more Vibrant ULF kernel Maker's will follow suite soon..

PS,

the Source they Posted is Bogus, there is no need to add all that into your Kernel source.. Just fix the Mount issue when building your next kernel..
[Vibrant Android Development] m00nshake:
Downloading now... and supports bootanimation.zip!!?!? Thanks thanks thanks... Sweet!
[Vibrant Android Development] eugene373:
remember to ODIN first, if using any of the Old A kernel... A4 & A5 is fine as the ULF was not in them..
[Vibrant Android Development] m00nshake:
Absolutely! A short time ago I took the plunge and learned how to use Odin and made it a habit to always Odin back to unofficial Tmob 2.2 everytime I flash a new kernel or rom...

I can hardly contain my excitement... Thanks, Eugene!

~m00n
[Vibrant Android Development] frank707:
Anyway you can post a kernel with system mount fix without bootanimation.zip support and stock boot. Like previously kernels?
[Vibrant Android Development] yungballla6:
so this soft brick issue i was the first one to bring this too your attention after all. lol
[Vibrant Android Development] JeremyNT:
I switched from an A kernel back to stock already with no problems, do I still need to heimdal/odin? How do I verify that I have the corruption?
[Vibrant Android Development] firefly6240:
I just switched with no problems and no odin, but be ready cause theres always the chance it wont work and you'll need odin.
[Vibrant Android Development] eugene373:
Yes & thank you..

If you didn't apply any lag fix prior you should be fine & no need to odin.
[Vibrant Android Development] JeremyNT:
Running uname -a from terminal or adb will give you the build date at least.
[Vibrant Android Development] calvinpreston:
with B_Stock_1120 kernel, do I need SetCPU to OC? or SetCPU is only for underclocking?
[Vibrant Android Development] firefly6240:
I have applied JFS advanced lag fix on all previous kernels but disabled it before flashing a new one. maybe I just got lucky :)
[Vibrant Android Development] salvador3:
ok i ran it from the terminal and got this:

2.6.32.9

Nov 3 was the build date

I'm guessing this is not correct....
[Vibrant Android Development] hanbaoquan15:
Anyone got sleep death issue with the newest kernel?
[Vibrant Android Development] lralexl:
Is this relating to the drop from 3.7 to 3.0v shutoff for battery?
[Vibrant Android Development] m00nshake:
Ok so I Odined back to stock... factory reset... flashed Macnut 12 Rom, rebooted, then flashed the new B-stock kernel, rebooted again, applied lagfix Overkill (last one on the list). Rebooted again, did not disable lagfix, just flashed just the E-productions stock kernel, did not factory reset, upon booting, dailybriefing force closed but everything else loaded. Rebooted into clockwork, was getting mount errors. Odined back to stock Froyo. Did I do something wrong in this testing?

~m00n
[Vibrant Android Development] eugene373:
Um? You didn't disable lagfix :rolleyes::rolleyes: I hope this was meant as a Joke.
[Vibrant Android Development] m00nshake:
No, maybe I misunderstood the following line from the OP...

~ No longer required to disable lagfixes before flashing

I guess that's what you wanted to test...

Tomorrow I'll try switching back and forth from the B-stock to the E-productions stock without a lag fix and give you some feedback.

I'm gonna sleep now, and I wish you, Eugene, a very Happy Thanksgiving!!!

~m00n
[Vibrant Android Development] firefly6240:
nope :) no sleep death on the newest one, its running beautifully :-D
[Vibrant Android Development] eugene373:
Yeah still have to Disable the lagfix if switch to EB kernel... All those Modules are not supported..... It's Posted that way so you can still Flash or Fix as where Voodoo will Not even boot into recovery mod ( Old voodoo )
[Vibrant Android Development] hanbaoquan15:
I flashed many times without disabling lag fix, never had a problem.
[Vibrant Android Development] flameinthefire:
mancut it self= battery drain with this new kernel i guess the battery will die in no time. am i right?
[Vibrant Android Development] flameinthefire:
so are you suppose to flash both kernels?
[Vibrant Android Development] eugene373:
LMAO... Guess you don't even Bother Testing.. What a Shame...

Regarding Kernel... Do what ever man, it's just always a good I deal to disable anything..
[Vibrant Android Development] flameinthefire:
Whoa nothing personal eugene i give you mad props for doing what you doing. i think you are doing an amazing job. didn't mean to go on you like that. its just that all those kernels ive tried so far kill the battery very quck that's why i was asking.
[Vibrant Android Development] eugene373:
lol... It kernel related not the Rom is why i Responded like that... If you want good battery life use the EB Kernel Mod

However I have found the reason behind battery drains & the the B_1120 kernel should do well on Battery.
[Vibrant Android Development] flameinthefire:
ok i odin backed to stocked flashed r12 and flased the b1120 i lost 12 percent battery in 8mins and 30 secs is that normal? no phone calls , no games , no gps , no bluetooth just browsing thru the rom
[Vibrant Android Development] eugene373:
Anytime you Flash a Kernel you have to Reset Batterystat.bin & Fully charge the battery... The configs are not the same.
[Vibrant Android Development] hanbaoquan15:
Is it the same thing as wipe battery stats?
[Vibrant Android Development] MINUS Stl:
Did you recondition your battery? I'm guessing you probably didn't.
[Vibrant Android Development] cashyftw:
So we don't do a Lagfix with the new bstock kernel?
[Vibrant Android Development] hanbaoquan15:
There are lag fix options if you want to. It's in the kernel
[Vibrant Android Development] jzero88:
Fyi, every single rom and kernel, eugenes, tw, masters, etc gives crappy battery life, period. Compare it to stock and you will see. I will stick on stock, with xda superpower of course till eugene fixes the kernel to support battery voltage drop to 3.0v. Also reseting battery stats on any rom or kernel really doesnt do much. At least from my experience.
[Vibrant Android Development] cashyftw:
Oh okay, but I mean is it okay now, or has it always been okay lol?
[Vibrant Android Development] cashyftw:
Going back to stock, then flashing bkernel.. Had a little issue, No big.
[Vibrant Android Development] takato23:
I have 2 issues. First i've installed Macnut R12, then 1256 kernel and now this last one (with /system fix). The problem is that every time i reset the phone, the language gets back to english and setcpu says "speed not detected" and set 19.25 for max and min. So i check 1120 and 200 manually. I have it "on demand" and "set on boot"
[Vibrant Android Development] nickerrides:
does this kernel work on stock unofficial 2.2 rom??