yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] existz:
Ok good, see if it happends with kernel vm tweak disabled, like I said though it might have been a coincidence, but I've yet to have a charge death, and I've tested over 35 builds so far (actually probably more like 50+ builds of this kernel), after enabling it I finally had a charge death, so there has to be something related there...
[Captivate Android Development] WickedNite:
So you recommend ext4nj then?

Sent from my Muscles using Brain Cells
[Captivate Android Development] existz:
I do, ONLY on cache partition, since it doesn't hurt anything and it allows you to dload larger apps if you want them, but keep system and data ext4
[Captivate Android Development] WickedNite:
Okay. I guess I'm gonna change cache partition to ext4nj again. Thanks for the info.

Sent from my Muscles using Brain Cells
[Captivate Android Development] meridianblade:
Existz, any idea why my phones crashing with the kernel scheduler tweak enabled?
[Captivate Android Development] sjavvaji:
last time i cleared my cache with this setting...i got massive fc's...but i wasn't sure if that was because of the ext4 nj partitions or the fact that i set the lagfixes the were in rows 4-7 to ext2
[Captivate Android Development] LimaI896:
Existz if your still wondering about tweaks I have all of them enabled,.i get cd but I use colds temp fix to stop it.
[Captivate Android Development] existz:
Try doing it without the Kernel VM tweak enabled and see if you get CD for me if you dont care. I might be going down the wrong road with this, and it might not work, but its worth a shot.
[Captivate Android Development] Auridran:
It's because of the loop and the bind lagfixes that you got the force closes.

Also, I have not had a charge death since #32, and I had three charge/sleep deaths in one day before that.
[Captivate Android Development] zerkai:
Hey existz, is this kernel compatiable with 'Call Recording'?
[Captivate Android Development] sixstringsg:
I'm gonna try this. I fixed my charge death by undervolting a lot less, but I'm going to take off the Kernel VM then raise my UV.
[Captivate Android Development] iXNyNe:
switched to fast mounting today and got my quadrant scores up to 1800s and linpacks to 17s

not really caring about file system stability - i reflash SOMETHING every couple days or i start to itch... (so i end up reformatting/repartitioning a lot because of rom installs)

i will report tomorrow if it makes a difference for battery life (but i would imagine it wouldnt)
[Captivate Android Development] existz:
**UPDATE**

Build #36

Updated initramfs from K12T

Improved sharpness: turned on AMOLED mode in MDNIE

Slightly optimized light sensor driver

Disabled gamma 1.9 setting, everything uses gamma 2.2 now
[Captivate Android Development] zerkai:
Woo! Nice, thanks existz!
[Captivate Android Development] airbillion:
Existz,

Awesome kernel, the best in my opinion. Any progress with the lastufo port yet?
[Captivate Android Development] existz:
Thank you sir :) , Yea theres been a little progress, still digging through his source, checking everything out, finally got a rough beta build going. Ive also been getting VSF tweaked some, trying to fine tune a few other things, its getting there. Hopefully get to actually dig into it this weekend. Open beta shouldnt be to long from now, hoping for within a week or so... Also been messing with the JL1 sources, thinking about doing a version with it, but cant make up my mind yet.
[Captivate Android Development] airbillion:
Awesome, keep up the good work! Running #36 right now perfectly. I can't wait to see what you come up with next. Thanks!

Edit: love the new sharpness settings, really makes a difference.
[Captivate Android Development] soypoi:
So which one would be for faster speeds, the 500 or the regular?
[Captivate Android Development] IStern:
depends, 500hz supposedly gives better UI performance, but your 3D games will take a hit. For me, 100hz is perfect.
[Captivate Android Development] WickedNite:
I agree. 100hz is perfect for my daily use. I don't play games that much though.

Sent from my Muscles using Brain Cells
[Captivate Android Development] cumanzor:
It affects 3d games? I haven't even noticed.
[Captivate Android Development] existz:
Technically you dont have to, it should work just fine, but it is recommended to disable first, I always use to leave voodoo enabled when flashing to Hardcores or similar just to keep system as ext4, but Hardcore uses a different method now when converting system to ext4, you should gain alittle bit more space on the system partition, but basically the choice is up to you..
[Captivate Android Development] Nickel Dime Bay:
Thanks, im going to flash over it then. I will test it out.
[Captivate Android Development] mkr14:
I would like to know this as well. Is the GPU running at 200mhz+ in either of these kernels?

EDIT: Also, kind of nitpicky, but can you remove the FM Radio function of the Voodoo Sound driver? DG and GB did this with their kernels. Some kernels have this enabled still and it feels incomplete.
[Captivate Android Development] opcow:
Just flash over. I flashed 1120, flashed back to GB, then when the 1280 version dropped I flashed it. I used Nedlar's each time.
[Captivate Android Development] Nick281051:
can anyone tell me what undervolting (uv i think thats what it is) and how i should do it with voltage control? sorry i am kind of a noob with this
[Captivate Android Development] opcow:
You are reducing the voltage fed to the CPU. The point being to save battery. Be conservative with voltage control to begin with. No one can tell you what settings will work with your phone, but something like -25mV at the highest clock speed down to -75mV at 100MHz (interpolate to between) would probably be a good starting point. After you set the UV for each frequency, hit the menu button and select 'Apply for now'. Run the phone for a while and if you don't get any lockups then you can go back into voltage control and 'save as boot settings' so that the setting will be applied every time the phone boots.

I'm using -25, -50, -75, -75, -100, -100, highest freq. to lowest, at the moment. Those are the initial values I used and I haven't tried pushing it further. Finding the minimal values which work for you will require trial and error.
[Captivate Android Development] lrs421:
wifi ??

Hmm, for some reason I can't seem to get a stable wifi connection with this kernel. I either get an error message or it just never connects to my router. Rebooted, wiped cache, nothing worked.

I just flashed back to hardcores and all is well again, I connected immediately. Does this use the same wifi drivers?
[Captivate Android Development] shawn122:
I wouldn't mind trying this...post it :)
[Captivate Android Development] yokozuna82:
After I flashed the 1280 version I went to uv using uv app and the 1280 shows this ...

1280Mhz:?-0=?mvp

Is this right?
[Captivate Android Development] silverslotcar:
Yes its right. Its just that the volt control app isn't coded to do 1280 and subtract the millivolts to what u set it as.

sent from my SGH-I897 running Serendipity 4.3 w/ Exists SuckerPunch SpeedMod Remix kernel and KP1 modem!!
[Captivate Android Development] hamburgertrain:
I am getting a large amount of sleep deaths. I tried using the undervolt settings I always use, and my phone died. I tried lessening the settings by one increment each, and am still getting sleep death.
[Captivate Android Development] LimaI896:
Hey guys I'm having the sanger problem as I was on gbs 1280 kernel. When I delete my S_voltage file then flash my phone freezes street media scan is complete. But if I keep my file there with my uv setting I run.sable after a flash. Except now my voltage control app force closes, any ideas how to fix this?
[Captivate Android Development] crupp:
If you convert system to ext 4 do you still need to enable lag fix.

Sent from a Serendipity ROM
[Captivate Android Development] LimaI896:
Why not have both done? :cool:

So I fixed my problem. I think my phone doesnt like the 1280oc at full voltage. So I managed to quickly get into the voltage control after a reboot to apply a uv setting.
[Captivate Android Development] silverslotcar:
Edit: nevermind.

sent from my SGH-I897 running Serendipity 4.3 w/ Exists SuckerPunch SpeedMod Remix kernel and KP1 modem!!
[Captivate Android Development] existz:
I didnt touch the gpu, and yea ill remove the fm driver from voodoo sound, I thought I already did but apparently I didn't lol...

Hardcore is working on the wifi connectivity issue with test builds in the i9000 thread, for now try turning IPv6 off or if its already disabled try toggling it on then back off with reboots in between and see if it that helps, I done the same and ended up working fine, for some reason its acting like its loaded, even though it says its not..this might be my fault... but ill get this fixed as soon as possible
[Captivate Android Development] sixstringsg:
I got charge death last night with uv at 100 100 100 100 75 75.
[Captivate Android Development] hamburgertrain:
Same issue.
[Captivate Android Development] PuffinNugz:
oops, meant to click QUOTE, not thanks..

Anyhow, I got sleep deep also, with the settings SSC posted. Gonna mess around with it a bit.
[Captivate Android Development] ccdoggy:
Also just noticed that In the voltage app i cannot change the scheduler, its stuck on cfq. can be changed to Noop but when you start the app again its back to cfq.

No charging death with 100-100-100-75-75-75 UV
[Captivate Android Development] MexicanAmerican:
Still using #34 for now, but just made the switch to 100Hz kernel. I had been using 500. I'm not much of a gamer, either. I wanted the better battery life option. First real world test is tomorrow.
[Captivate Android Development] iNFRiNGE:
Love it! Also love the clean up of the OP much easier to read great job ex. ;)
[Captivate Android Development] johan8:
Great captivate kernel !
[Captivate Android Development] LimaI896:
Just saw this now, I got a cd with colds temp fix still. Ill try it out tonight with that fix disabled. I only get charge death on long charges over night.

Edit: was quoting existz.
[Captivate Android Development] cumanzor:
I talked too soon. Got a CD today, even with Sleep as an Droid running... :(
[Captivate Android Development] ronpinoy253:
Compatibility with Paragon ROMs

I can't seem to get my phone to work with Suckerpunch kernals (even the new #36) on Paragon 4.0. I tried installing it with the Kernal Installer App, and with CWM, but the phone will go into a constant reboot cycle when it gets into the media scanner of the OS. I also tried disabling the lagfix and then installing, still no go.

Any ideas?

Batch: 1008

Paragon 4.0
[Captivate Android Development] slider2828:
That is weird.... I am running Paragon 4.0 as well with SuckerPunch #36 and it works flawlessly. In tweaks I have the first 4 options checked, and charged it over night. Made it into work on time, no CD for me. hahaha....

But yeah it works fine. What LagFixes do you have? I also removed VC first and any scripts and then CWM updated the 100Mhz kernel. Its been working great and nenamark is up to 49FPS @ 1280Mhz on Noop....
[Captivate Android Development] ronpinoy253:
Hmm...maybe I should also try removing VC before switching the kernels...let me try that out thanks for the tip!

EDIT: Uninstalling VC first seemed to do the trick. Weird...but thanks anyways for the tip!
[Captivate Android Development] sixstringsg:
I disabled Kernel VM, then raised my UV back up some, and didn't get a CD last night.
[Captivate Android Development] lrs421:
Wifi is back to driving me nuts. I just don't get it. I tried enabled ipv6 and disabling but connection is still spotty. Switching back to speed mod fixes it immediately.

Am I alone here?
[Captivate Android Development] slider2828:
I think the VC that came with Paragon is an old beta version. The newer VC is release so it with you cleaning up the scripts might have done the trick.
[Captivate Android Development] slider2828:
What modem are you currently using? Usually wifi problems are more related to bad rom flash.... Might have to go clean and reinstall it.... but try a different modem like JL2 (But I really doubt modems have an affect on wifi)
[Captivate Android Development] neffarious:
So people that are not having CD issues, would you mind posting your UV settings? I use mine as an alarm so i went back to GB since i can afford to have it CD over night.
[Captivate Android Development] lrs421:
Actually this gave me an idea to reflash the kernel. This seems to be have done the trick but it's still too early to tell. I also set my router to a specific channel.
[Captivate Android Development] sixstringsg:
Low to high. 75 75 100 75 75 50 CFQ up to 1120 with Kernel VM disabled.
[Captivate Android Development] lrs421:
All tweaks enabled, everything set to -75. Running 1200, 1120 not used in "states"
[Captivate Android Development] capita:
For those not getting CD, are you guys charging through the AC wall outlet adapter, or USB through the computer? I've noticed I get CD when plugged up to AC, but not when I'm hooked up to the computer.
[Captivate Android Development] lrs421:
Nope, its kernel related :-( switched back to speedmod fixed it. Damn I do love this kernel, just hasn't been right with wifi for me since the first release. The thing I don't get is that its based off speedmod. Weird.
[Captivate Android Development] stacio88:
Question, do I have to flash the kernel on a full battery? I usually always do bit I don't want to wait for it to fully charge. Will it make a difference if I flash the kernel at full charge as to an 80%?
[Captivate Android Development] meridianblade:
I had this same exact issue with Phoenix 4.5. Disabling Kernel Scheduler in the tweaks fixed it for me.. I wish there was an official fix for this though so I can have that tweak enabled.
[Captivate Android Development] existz:
Alright guys, ive had about 4-5 people confirm that disabling VM tweak in recovery, they DID NOT have charge death, this is coming from people thats had charge death since the first release. So if you have VM tweak enabled, disable it. Going to look into it more since people are confirming its the problem. Is there anyone out there that has CD but have NO tweaks enabled?
[Captivate Android Development] bclark:
No CD in outlet or usb. All tweaks enabled
[Captivate Android Development] sixstringsg:
I'm charging through AC.
[Captivate Android Development] existz:
Alright, good.. It could be a combo of the VM Tweak AND setting UV to low, thats what I need to figure out, I know some of you have all tweaks and NO charge death, but for some reason those that DO have charge death, the VM tweak disabling solves it. The only thing setting VM Tweak to enabled, is it sets /proc/sys/vm/swappiness to 0 instead of 60. So that setting, either on certain phones dont like it, or swappiness = 0 plus low UV is causing it..ill figure something out :P ....So for those WITH charge death and have ALL TWEAKS enabled, DISABLE VM tweak and see if that solves it for you
[Captivate Android Development] cumanzor:
If that is the reason, can you actually think of any relation between low UV and swappiness? : S
[Captivate Android Development] sixstringsg:
I had VM tweak and the settings at 125 and had CD. then lowered my UV to 25, and had no CD. Then disabled VM, went back to 125, and have no CD.
[Captivate Android Development] lpsi2000:
I was getting the COD before and got it recently. I am now disabling VM tweak to see if that helps.
[Captivate Android Development] existz:
So far its like 5 for 5 thats had CD and tried that, then it fixed CD ...so def let me know if it fixes it for you, i think im on to something here, might have a fix up soon (tonite/tomorrow)
[Captivate Android Development] lrs421:
Existz, I've been playing with wifi firmware as of late. Do you think that could effect connectivity, are you still running jpa?
[Captivate Android Development] c0ldburn3r:
So very very very close to having thd CD issue figured out and fixed. A few of us are testing some tweaks and I hope we have the answer in the morning. This will be a load off eXistZ shoulders.
[Captivate Android Development] lrs421:
Good luck dudes!
[Captivate Android Development] fluidd:
If I specificied OC settings through the Voltage Controller App, do I have to erase those settings first before I flash #36 kernal?

Edit: I already previously flashed the #34 kernal.
[Captivate Android Development] c0ldburn3r:
Nope, those settings should work just fine. Did for me anyways.
[Captivate Android Development] existz:
To be honest, im not 100% sure, I haven't touched anything related to wifi, so it should be the same as hardcores, but apparently something is wrong for some users, some have no problems, I think I might have the charge death issue resolved, once I get that done ill look into the wifi issue. And yes, I still use JPA firmware.
[Captivate Android Development] fluidd:
Thanks! Will try this later on tonight when I get home
[Captivate Android Development] Dlev7:
I just tried the tweak disabling the VM and im going to retry suckerpunch.

Ill keep you posted
[Captivate Android Development] existz:
Great! Def let me know if that fixes it, so far everyone who has tried it, it worked. If this is 100% the problem, then I think I know why its causing it.

With VM tweak enabled it sets swappiness to 0, disabling swap. When VM tweak is disabled it sets swappiness to 60. So theres something with UVing needing swap. So right now im trying to find the best setting for swap without causing charge death. Im hoping this fully fixes the charge death, so far it has...
[Captivate Android Development] deuceduzit:
Stability Test 1.2

Does anyone use this? I can never get it to complete without auto closing... Should I be worried? I have read on several forums that it gives unreliable results.... Just wanted to see if anyone here is using the program and any feedback on it....
[Captivate Android Development] c0ldburn3r:
IMO that test blows. You can use SetCPU's stress test for better resault, just don't set anything in that program. Stability test craps out on stock kernels too.
[Captivate Android Development] lrs421:
In my experience stability test works best in airplane mode. When I have data active it goes nuts. I found good/stable settings using stability test but only after disabling data.
[Captivate Android Development] deuceduzit:
Thanks for the quick response guys, new to this whole UV/OC thing just testing things out.
[Captivate Android Development] bclark:
I have to be honest, these tests all suck IMHO. Just use your phone. If you get a FC adjust your settings and continue about your day. The real world is all that is truly necessary for a day to day user.
[Captivate Android Development] sjavvaji:
i use the js3 one...so far it has proved to have little battery use and nice connectivity
[Captivate Android Development] lpsi2000:
I am still getting COD with vm tweak disabled. I just turn all tweaks off and trying again. It seems as COD are coming when it is connected to the computer. I will see later if I get them when I connect to the AC
[Captivate Android Development] existz:
Also make sure to rule out that its not from your UV settings, if they are to low they will cause charge death... Cause right now it seems if they are to low it causes it and/or if vm tweak is enabled
[Captivate Android Development] FocuseD83:
What are the gpu clocks?

Just have a question about the gpu clocks... Was wondering what the gpu clocks were for each oc setting... This kernel is great! Was having some live wallpaper issues with the settings and was wondering if my gpu clocks had anything to do with it... A slight lag was showing up in the both versions of the kernel... Probably not even the kernel but would like to know either way... Thanks for all the hard work!
[Captivate Android Development] existz:
The gpu clocks were not touched, so they are still set to whatever the stock frequencies were. I've been messing around with different threshold settings, should give less lag and some better battery as well. It should be in the next release. I might look into adjusting gpu clocks later on
[Captivate Android Development] lpsi2000:
I have using the same uv settings I have used for setiron and paragon with no issues. Basically the ones in my signature
[Captivate Android Development] existz:
Yea but still make sure, as there's quite a few different settings/options I use than they do, that could need less uv, or more uv. I had to adjust my uv settings when starting this kernel than what I used with GBs kernel. Alot of things come into play, and could cause instability .. But it might not effect it and your UV settings are fine, but its best to rule it out first, don't always assume.

EDIT

im not saying your UV settings are wrong, or that it will even fix it, its just it could be one frequency that needs a 25mV bump and it stop charge death..(i.e the 100mhz frequency might need just a tad bit more voltage, so adjusting by 25mv it solves it)... Its just with trying to troubleshoot a problem when theres 100 different options and variables, its best to make 100% positive that everythings ruled out. But who knows, your UV settings could be fine...better to check though. With disabling VM tweak, ive had 6-6 saying it solved charge death, but if it doesnt help yours and your UV settings are good, then theres something else causing it..
[Captivate Android Development] sjavvaji:
thats what did it for me...i had to go from -125 (which i used to use on setiron's) to -100 on 100mhz and 200mhz frequencies to stop sleep death...im still running the vm tweaks and no sleep death since the raspdeep's switch
[Captivate Android Development] existz:
See thats what is confusing, for some disabling VM tweak solved everything, but then theres others running the VM tweak without charge death... so im not sure why its helping some, but not even a factor to others. I think for the most part, peoples UV settings need adjusted.. you might not need to adjust them all, maybe just 1 frequency.. But im still digging into this and trying a few different options, hopefully i can get a fix soon... (wish GB would msg me back...)

So for right now, all I can recommend if you have charge death is..

1) go back and adjust your UV settings, maybe just 1 or 2 frequencies (or maybe all of them) might need more voltage

2) try disabling VM tweaks via CWM (seems to solve charge death for some users)
[Captivate Android Development] lrs421:
This is soooo strange, like you I've never had CD and I do have VM enabled. Even on settings that were determined later to be unstable still no CD. We're in your corner dude.
[Captivate Android Development] joeshmoe08:
GB has been inactive for a long time. The last time he logged in was the 26 of Jan according to his profile.
[Captivate Android Development] aalh:
Cant we test by changing the swappiness at runtime by echoing a different value to it like so:

echo 0 > /proc/sys/vm/swappiness

no boot to recovery needed?
[Captivate Android Development] existz:
Yes, you can just issue the command via terminal emulator or adb shell, note though it wont stick through reboots, so if you reboot make sure to do it again. When you enable the tweak it sets swappiness to 0, when you disable it it sets it to 60 (default) ..im trying out different values now, trying to see which gives best performance without cd..so to test it for now, make sure to make it 60, since its been confirmed to work (as I don't know yet if anything besides 60 works or not) I have a few testers trying different values now trying to find the best setting. .but just type this via terminal..

echo 60 > /proc/sys/vm/swappiness