yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] JeremyNT:
I'm stable now for several hours, with set cpu totally disabled, voltage control set to default voltage and "don't overclock", no lag fix, no advanced ulf tweaks, no bln.

I'm hopeful that this will stay stable through the night. If it does, I'll enable something and see what happens.
[Vibrant Android Development] Kubernetes:
Why don't you run the voltage app and see for yourself?
[Vibrant Android Development] Telanis:
I'm not entirely sure what the point in having this kernel is if you can't use the features of it ;)
[Vibrant Android Development] ludachez:
yeah i loaded up MacnutR12 and then loaded the app, set everything -25 and i see its overclocking....so ok then...works for me!
[Vibrant Android Development] ludachez:
i agree with that. I reset everything and loaded up MacnutR12 figuring it would work better and so far so good. Running A13, voltage all -25 , OC'd and Ext4 Overkill. So far so good...
[Vibrant Android Development] JeremyNT:
At this point I'm just trying to isolate the issue. I enabled so many things initially that I have no idea what was causing my problems. If I can get it stable with everything disabled I can slowly enable stuff until I find out what the problem is.

I'm kind of wondering if the oc is the root problem in my case.
[Vibrant Android Development] Fedburin:
Yeah I am with you there - I don't really feel like reflashing another ROM. As for the point of running this kernel, it is the only thing that seems to fix my GPS when running 2.2. I wish the phone could sleep without freezing - so close to getting a stable ROM/kernel. It seems like I am always just one step away ;).
[Vibrant Android Development] faldiin:
Sleep not waking

I am using A14 and Macnut 12. I am not running Lagfix since each time I have tried it I get a complete failure. Not sure the error but my screen say Panic. I have left the setting for the Voltage program as default. So I guess this is an FYI. Everything else works great. I have not tried Voodoo or any of the others since I have had problems as is.

Faldiin
[Vibrant Android Development] m00nshake:
I flashed today before going to work and am getting the same issue with the phone not waking. I'm not UV. I just turned off tweaks and hopefully that fixes it.
[Vibrant Android Development] m00nshake:
What scheduler are you using?
[Vibrant Android Development] firefly6240:
I realize its realy to late for this reply...

(I work nights so I'm awake weird hours)

but I had the same problem with A12.

it seems to be something going wrong sporadicly with the lag fix.

I had no rfs JFS advanced enabled, and my market icon dissapeard although it was still in the data partition (I always keep a backup of root explorere just in case I cant get to the market so I can still install apps and mess with my data partition)

so I tryed reinstalling it from the data partition which of course gave the same errors as what you tryed (you really have to flash the market rather than just installing the apk usualy) but what worked for me was disabling the lag fix, as soon as it ran the backup and restore, my market was back and working.

it seems to be a fluke because I'm running the exact same lag fix and its working just fine now.

if you look in the thread about the universal lag fix on the i9000 forum, you see that he says theres a possibility of data corruption, I'm guessing thats what happened.

so in short, if your market dissapears, disable the lag fix, and then just re enable it until it works :)
[Vibrant Android Development] Fedburin:
I changed the scheduling from CFQ in the voltage app and that seems to have killed the sleep death...for now. I know that CFQ in Linux will sometimes do the same if running dual core as it tries to schedule to both cores fairly and locks the CPU. I am not sure why the sleep death issue is happening but I have never been fond of CFQ. BFQ on the other had is batsh*t crazy most of the time. I went with deadline. I will post an update in the morning.
[Vibrant Android Development] hanbaoquan15:
I changed to deadline and it still died on me.
[Vibrant Android Development] henreeg:
I'm also using Axura ROM. But I flashed the A14 kernel [thank you so much eugene!]. I'd like to know what settings you are using.
[Vibrant Android Development] ludachez:
i was using deadline scheduler. and after 2 hours of the no sleep issue it just got me. which is such a shame, i LOVE the ULF kernel option. Ext4 overkill works amazingly well for me. I assume i cant use Overkill and then change the kernel right? Whats very weird to me is i was on A11 and did not have ANY issues, upgraded to a13 and had the sleep issues. Downgraded to a11 and lost all wake/sleep issues. I heard that setting setCPU to ondemand would fix it so i put it back to a13 to try and now no matter what i do a11 and a13 get me the sleeping phone of death
[Vibrant Android Development] gfropr:
I get the same thing I've tried everything, and I mean everything. I'm sure Eugene will fix it, he's the man!
[Vibrant Android Development] m00nshake:
Thanks keep me posted. I disabled all tweaks and still having same issue
[Vibrant Android Development] ludachez:
from what ive tried the tweaks have nothing to do with it. i turned them on and off a bunch of times. i even tried not using the UV app, freezing it with titanium and nothing. So far the only thing i DIDNT try was not overclocking. im doing so now, and its lasted 10 minutes....i'll let you know. Using deadline scheduler and -25 down the line.
[Vibrant Android Development] m00nshake:
Tried ondemand still same issue. I uninstalled setcpu so we'll see if no OC fixes it. Thanks for the update.
[Vibrant Android Development] ludachez:
if you want no OC and you have the voltage app be sure to check "no overclocking" or else it will do it for you....i learned the hard way
[Vibrant Android Development] ludachez:
Got the same lockup, i have tried everything. this is the part where i hate being a rookie and wish i knew how to read a logcat or even get one for someone. Oh well, this kernel when working is so amazing, as ive said 99 times, and Eugene always comes through
[Vibrant Android Development] Kubernetes:
I've installed setcpu and set min at 200mhz. Wondering if it sleep-dies because 100mhz is the issue. Worked on some early TW OC kernels, so I'm going to give it a shot.
[Vibrant Android Development] firefly6240:
I tryed setting it to 100, 200, and 400 and it still died during sleep...

however I've finally found something that seems to be working so far although its pretty extreme...

I turned off all undervolting, unchecked the overclock limiter and closed the voltage app.

then in set cpu I just overclocked completely to 1200 both high and low and set it to performance so that theres no scalling going on.

so far I've had no trouble coming out of sleep, although I cant imagine leaving the phone completly overclocked is good for it long term :-/

also on a side note... my battery is randomly draining a whole lot slower with it fully overclocked and set to performance than it was when it was scaling.

weird.
[Vibrant Android Development] mautai916:
I flashed the A12 kernel, how much do you guys normally undervolt using the voltage app? I was thinking -25 for everything?
[Vibrant Android Development] firefly6240:
-25 is usualy pretty stable.

you can go more, but you'll just have to play with it to find out how far your phone goes :)
[Vibrant Android Development] ludachez:
So far i just reverted back to A11 and it seems to be working fine. Macnut12 and A13 didnt work for me. is A14 any better? or is everyone getting issues with both?
[Vibrant Android Development] firefly6240:
I'm getting issues with A14 but 13 and 14 are essentialy the same.

so far mines doing fine but I have it completly overclocked at 1200 all the time with no scaling.

otherwise I've been having it die when it sleeps.
[Vibrant Android Development] xspeed9190:
Haven't noticed any improvement yet. Showing 25% at 3717..... Thats not close to 3.0v let alone 3.2v using a14
[Vibrant Android Development] firefly6240:
well my phones been running most of the night now with no sleep death.

so I suppose its safe to say that keeping it at 1.2 ghz fixes that.

unfortunatly I'd imagine once I start using it much it'll eat the battery for breakfast lol

its super snappy though hehe
[Vibrant Android Development] vtp:
Here is my report after 2 days with kernel A12

My set up:

Vibrant with Axura 2.0.4 ROM and kernel A12 with:

lagfix: no rfs advance: all partitions ext4

kenel setting: using default

sleep/Awake freeze randomly about 2-3/day

compass app loaded by not working correctly (not response to direction change )

GPS working great

bettery life about 17 hrs on lightly use made few phone call, play with apps for ~ 1hr

quadrant: ~1600

linpack: ~15
[Vibrant Android Development] m00nshake:
This has been confirmed with me as I uninstalled SetCpu last night, rebooted, and woke up this morning and the phone was still turned on...

Eugene, how can I overclock without SetCpu... I've been told using the VoltageControl app, but all I see is UV settings, scheduler, and a checkbox for limiting to 1ghz (no OC). I'm not sure what to do next....

Thanks as always for your hard work.

Edit:

Ok I spoke to soon. It appears the phone was doing fine while I was sleeping because it was charging. Unplugged thIs morning and went to make a pot of coffee came back it was dead.

~m00n
[Vibrant Android Development] JeremyNT:
Just a follow up, my phone seems to be stable in this configuration. I'm going to try using it like this today and hope for the best.

In my case, it seems like disabling the oc may have done the trick, although it's too soon to say for sure.
[Vibrant Android Development] henreeg:
suggestions

Can anyone please enlighten me on how to take full advantage of the A14 kernel?

Not quite sure on what to do other than... flash it. :confused:
[Vibrant Android Development] drhonk:
Just curious if anyone here ever try successfully switching back to RFS and stock kernel?
[Vibrant Android Development] m00nshake:
Odin back to Unofficial Tmo Froyo 2.2, do a factory set in recovery, then flash ROM and kernel of choice. I'm going back to A10 and Macnut 12 until things with A13/14 get sorted.
[Vibrant Android Development] m00nshake:
Right now we're having issues w/ the phone not waking after its been sleeping for a few moments. I've tried everything I can think of and it still persists, so unless you want to constantly pull the battery, I'd advise holding off on this kernel until that problem gets resolved.

To answer your question, though, after you flash the kernel and you reboot into recovery, you can enable all of the tweaks, enable bln (backlight notifcation, which will cause your buttons to light to notify you when you've missed a call or have a new email, etc.). You can also choose any lagfix that suits you, I used the last one in the list. Finally you'd install and use Setcpu from the Market in order to overclock to 1.2 ghz.

But again, I'd wait a bit...
[Vibrant Android Development] drhonk:
I meant without using ODIN, basically switch everything back to RFS from recovery and even reflash stock kernel.
[Vibrant Android Development] calvinpreston:
does anyone know how to permanently uncheck the "limit max clock to 1Ghz" on voltage control app? whenever i reboot my phone, i always need to uncheck it.
[Vibrant Android Development] m00nshake:
I tried that, got nothing but Kernel Panic mode when trying to boot up, and then I had no choice but to Odin, and felt lucky I could even get that done. I thought I had bricked my phone. You can try it, it might even work, just be forewarned.
[Vibrant Android Development] JeremyNT:
I've not switched back to stock, but I have switched to a different kernel from this one using ROM manager. The steps are roughly:

- Boot into recovery (volup/down)

- ULK options -> lag fix -> disable lag fix there (I think it's the first option in the menu)

- Disable all of the various other tweaks in the ULK menus (I'm not sure what happens if you leave these enabled and have a kernel that doesn't support them, but I'd be safe and turn everything off)

- "Go back" in CWMR and "reboot system"

- On reboot, the recovery menu will prompt you that the lagfix config differs; allow it to do its thing to restore RFS (it's a nandroid backup/restore)

- You'll have to reboot again when this completes

- Once you're back in the phone, reboot into CWMR, and flash the kernel you desire.

YMMV of course. As always make a backup of everything you care about before attempting, and be prepared to Odin/Heimdall if it fails.
[Vibrant Android Development] drhonk:
Hmm.. so it does work. I'm just concern with supercurio finding:

http://twitter.com/supercurio/status/6675035024531456
[Vibrant Android Development] MINUS Stl:
I was originally getting the no-wake issue with a14 (on Macnut r12). Decided to ODIN back to stock and start from scratch this weekend. BLN is enabled, but no kernel tweaks are. Also been slowly changing the UV settings one by one. Haven't had a no-wake issue yet (all weekend).

So far I'm running it non-OC'd, and all but 100mhz are a -25uv.
[Vibrant Android Development] m00nshake:
are you running a lag-fix? If so, which one? And definitely keep us updated. I tried taking out the tweaks but maybe a fresh start without enabling the tweaks would do the trick. Thanks.

m00n
[Vibrant Android Development] MINUS Stl:
No lag-fix either. Haven't ran one since FWiz w/Voodoo.
[Vibrant Android Development] opentofalling:
I installed r12 and a14 yesterday...flashed each individually with a couple of reboots inbetween...over eugene's unofficial odin image. The no-wake issue is hitting me with no tweaks other than the JFS data lagfix. When this happens, I noticed that holding power/vol-up/vol-down drops me straight into cw recovery after about 3 seconds each of the vibrant/i9000 boot screens. Seems like a better option than popping the battery...who knows...
[Vibrant Android Development] Whitehawkx:
You can also just hold the power button down for 10 secs to reboot the phone.
[Vibrant Android Development] JeremyNT:
That's concerning; I'd be curious to know what sort of corruption he's referring to so I could verify whether it's hit me. I assume it would be due to some issue with how the devices are being repartitioned and the loopback devices are being created when the lagfix is applied, and not an issue with the kernel itself, so presumably you'd be fine if you weren't applying lag fixes?

With the ULK kernel my device has now gone from RFS -> JFS -> RFS -> JFS -> RFS so if there's any corruption to be had due to that process, it seems likely I'd have it. I wonder if it could be the cause of my failure-to-wake issues (which, for the moment at least, seem to be gone).
[Vibrant Android Development] drhonk:
I think the only way to test it if you switch back to RFS and install a different kernel, like stock kernel for example. I think you should be fine if you stay with ULF kernel, but supercurio is working on the fix. :)
[Vibrant Android Development] FATEOWNZYOU:
which one will work best with axura
[Vibrant Android Development] Lavundra21:
what voltage settings work best for the a14 kernel?
[Vibrant Android Development] bstromberg:
what scheduler are you using?
[Vibrant Android Development] bstromberg:
i think that kernel is clocked at 100-1000 on first boot. could be that its set too low and that is causing the no-wake issues. have you changed the min clock speed?
[Vibrant Android Development] JeremyNT:
Most people seem to recommend 25 or 50. I'm running (hopefully) stable now at 25 across the board.
[Vibrant Android Development] eugene373:
Still around, working on the Kernel still... & a new Build coming shortly as well.
[Vibrant Android Development] ludachez:
Good to know...even though we arent doubting you. The a14 kernel is amazing aside from the sleep of death, when working the quality really shows. if that issue gets fixed it makes 2.2 all the better.
[Vibrant Android Development] firefly6240:
clock it completely to 1.2 ghz with the performance setting rather than on demand, and disable the 1ghz limiter in the voltage app.

and disable the undervolting. (you may be able to get away with it but I've only tried this with it off.)

that fixes the sleep of death, but it also drinks the battery.

the phone runs snappier than my computer now though hehe.

I'll be almost sad when I go back to regular clock scaling, but I cant imagine staying on 1.2 ghz constantly is great for the phone long term.
[Vibrant Android Development] m00nshake:
Ok so I odin'ed back to unofficial Froyo, factory reset, flashed macnut12, Frobuntu theme, then the A14 kernel. Applied the tweaks and the last lag fix on the list. No OC, no UV set, been running stable for about five hours. No sleep no wake problems so far, fingers crossed
[Vibrant Android Development] calvinpreston:
i'm running no rfs advanced without OC for about 5 hours now and i'm not having the sleep of death. i'm getting 1500 benchmark. not bad rather than getting the sleep of death. i wiped cache partition too before activating the lagfix.
[Vibrant Android Development] ludachez:
wow i did the same thing and i had problems. i might have done one little thing different and got the issues. such a finicky phone
[Vibrant Android Development] m00nshake:
Well after hours of running stable the phone had the waking issue again. I didn't change a thing. Hopefully Eugene will get this worked out with the new build he mentioned that he's working on
[Vibrant Android Development] nanim0n:
only solution there is for a14 is to stay awayyyyyy
[Vibrant Android Development] JeremyNT:
I don't want to jinx it, but I've been stable for 24 hours. I'm running with no OC widget, undervolted by 25 across the board, no lagfix, BLN on, Voltage Control set to "limit to 1GHz."

After remaining stable for a day, I've enabled all the other kernel tweaks. We'll see if I make it through tonight as well.
[Vibrant Android Development] mjb337:
just wanted to know do my sdcard on my vibrant has to be partition in order for lag-fix kernels to work properly?
[Vibrant Android Development] mjb337:
does lag-fix only works with partition sdcards? im asking because when trying to apply lag-fix on any of these kernels it doesnt work...help?
[Vibrant Android Development] mjb337:
do i need an ext4 on my sdcard in order for lag-fix kernels to work properly on my vibrant?
[Vibrant Android Development] mjb337:
do my sdcard has to have an ext2 or ext4 partition before applying any lag-fix kernels?
[Vibrant Android Development] henreeg:
HELP! A14 JUST BRICKED MY PHONE!

j/k...

just kidding as in i don't need help.

but it did brick my phone [using Axura 2.0.4].
[Vibrant Android Development] firefly6240:
no the lag fix does that for you. just chose your lag fix in recovery and reboot. it will ask you if you want to back up and restore. just say yes is usualy the best choice. then it will back up your stuff and reformat then it will restore your stuff and reboot.
[Vibrant Android Development] mjb337:
thanks alot bro will see how it goes
[Vibrant Android Development] krntehknik303:
thanks for the kernel's going to try them out right now.
[Vibrant Android Development] xspeed9190:
has anyone checked their voltage at the end where the battery is about to die. Im on a14 got 23% showing with 3750mV..i thought it was supposed to go as low as 3200mV when it was dead.
[Vibrant Android Development] t1h5ta3:
im guessing you didnt wipe batt stats?
[Vibrant Android Development] xspeed9190:
its funny because i tried a few times and it just errors out with the new ULF recovery...any other way to do it

>>>>>

I tried renaming the ULF update.zip and reinstalling cwm update zip and when i do the wipe battery stats the notifications at the bottom where it says done to W/E ..nothing happens but when i do cache it says wiping cache.. DONE...anyone have any ideas
[Vibrant Android Development] atapio:
I flashed Macnut R12 and A14 today. Been running stable at these settings:

100Mhz -100

200Mhz -100

400Mhz -100

800Mhz -100

1000Mhz -75

1200 Mhz -75

No OC (OC is stable though)

Lagfix: Use JFS

Enabled:

IO Scheduler

Kernel VM Management

Kernel Scheduler

Misc tweaks

Been running smooth as butter. Going to see how long a full charge lasts with these settings tomorrow.
[Vibrant Android Development] Kubernetes:
My impression is that Eugene's 3.0v fix isn't working. I did wipe batt stats and used three different batteries and all died around 3.5v or 3.6v. Something else is at work here, and Eugene's fix doesn't work.
[Vibrant Android Development] eugene373:
Funny that you say that... If I flash to a Stock kernel when at 50% roughly on my kernel... The Stock kernel Reports it 9% / 10%

When Flashing back to my Kernel it Show once again roughly 50% again... So, that sounds about right given there is a huge bump in Voltage be dropped... Given the I9000 Kernel source it's self suck the battery, you only see at most a few hours.. However I think I got it figured out as to what's sucking the battery... Well, I know the cause of it, just fixing it has been a Pain!!
[Vibrant Android Development] xspeed9190:
at least i know im not the only one then. i had to use root explorer and delete the battery bin..now its dieing at 3.5
[Vibrant Android Development] xspeed9190:
so Eugene should we be lookin in info and seeing the voltage readings going below 3.5.

i am trying axura 2.0.4 and a14 im at 7% 3650

for some reason wiping battery stats in cwm does not work i have to use rootexplorer to do it.
[Vibrant Android Development] jzero88:
Now this is purely a work of genius. I remember a dude posting about voltage and how we weren't using the battery to its full extent, glad eugene either read about it or figured it out by himself, either way this is bad ass!

Unfortunately I have gotten rid of all the 2.2 roms I have been using. Battery life just plainly sucks. And yeah, I know I will hear a few people say "well what did you expect, 42423423 hours" NO! Just a battery that will last me through a full ****ing day of heavy use!! RIGHT GUYS!!! I mean common, not to go on any tangent or anything, but for a piece of $500 hardware, I definitely aint getting my batteries worth, let alone on any other phone. Good **** eugune.

But do you got a kernel like this on for stock 2.1?? JI6??

Would be great to have some kind of update.zip or some way to add only this to a stock kernel. What do you think?
[Vibrant Android Development] ludachez:
try AOSPish 1.1 (jk2) froyo with Eugenes EBKanged kernel #2 and delete or freeze the WiFi calling app. I got ridiculous battery life on it, easily made it a whole day with a lot of internet, twitter, and angry birds.
[Vibrant Android Development] ludachez:
when i hit wipe battery stats in CWM nothing happens, it just takes me back to the last screen. does that mean it wasnt working this whole time? i know SGS Tools in the market has a wipe battery stats key, guess ill use that
[Vibrant Android Development] cashyftw:
Could you let me know how well your battery life is, I was curious, and wanted to know before I flash.
[Vibrant Android Development] firefly6240:
well A14 has been running really stable with the constant overclock (No scaling) and I have found I can under-volt and it stays stable.

But as soon as I set any gap between low frequencies and high (I.E. 200mhz - 1000 mhz), the sleep death comes back. even at 1000 mhz - 1000 mhz sleep death occurs.

anyone have any idea what keeping my cpu at 1.2 ghz constantly will do to it?

I do like the performance lol

and I really dont care about battery life, but I dont want to burn out the phone either.
[Vibrant Android Development] jzero88:
Definitely will try that, actually will flash that tonight.
[Vibrant Android Development] cashyftw:
So will I, I'm looking for battery life lol.
[Vibrant Android Development] jzero88:
Well I am on thos build now. Idid not see an increase in battery lofe percentage when flashing at fifty percent. And now when the phone sleeps, I cant wake it from a sleeping state. I have to reboot. Am I missing something on how typo enable the increased battery life? Because of right now,i still get better battery life from stock JI6