yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] MexicanAmerican:
Tested #34 build at 100 Hz (first time I used a 100 Hz build) all day today. First thing I noticed is that when I wake the phone up (either swipe to remove the lockscreen, or enter a pattern, security code, etc.), swiping between homescreens is noticeably jerky. The jerkiness goes away when I launch the app drawer then return to my homescreen, or if I launch an app, then return to my homescreen. Then, switching screens is smooth as silk. It doesn't matter which launcher I used (Launcher Pro, ADW, Froyo Launcher), same issue.

I flashed #36 build, 100 Hz kernel and the same thing happened. I then flashed the 500 Hz #36 build, and the issue was resolved. When I wake up my phone I can swipe between homescreens all silky smooth like.

I guess 500 Hz really is smoother. I did get slightly better battery life out of the 100 Hz variant, but not enough to justify dealing with the homescreen hiccup issue.

I'll stick with the 500 Hz variants from here on end. Keep up the good work, existz.
[Captivate Android Development] ulupinar:
How to confirm that CPU really goues up to 1.4 ghz

I just installed this kernel. I played around a bit. It seems pretty snappy, however, my previous kernel @ 1.2ghz was pretty snappy too. The voltage control and the setcpu app says max CPU is 1.4 ghz, however, I never see the setCpu app showing anything higher than 1ghz as the instantaneous speed. Is there a program that plots history of clock speed?

Also I tried linpack, it gave me lower results than the previous 1.2ghz kernel. The results I get are:

SuckePunch36-1.4ghz 13.3

gb-reorient-f-1.2ghz 16+

Essentially I do not think I am getting 1.4 ghz from this kernel :(

Anyone was able to confirmed the higher speeds of this kernel?

Thanks
[Captivate Android Development] existz:
Make sure you select which states you want to use in Voltage Control app, make sure to use the latest (attatched in OP) if you don't have the frequency you want to use selected, just setting it in max clock will not work, since the frequency is not active

I usually get 17.9 with 1.28ghz
[Captivate Android Development] MexicanAmerican:
Yup. As I'm sure everyone will start asking....did you enable your overclocked states in Voltage Control?
[Captivate Android Development] ulupinar:
Thanks for the quick reply. Turns out I had an older version of the VC.

I have higher Linpack (19.0) number now - wow.

Thanks again
[Captivate Android Development] kytrauma:
Try uninstalling setcpu
[Captivate Android Development] airbillion:
Audio out through USB port

Exist,

Could you bake this into your kernel: http://xdaforums.com/showpost.php?p=11105520&postcount=51

It is a fix for allowing audio out through the USB port on the car and home dock.
[Captivate Android Development] existz:
Yea, looks like xcaliburinhand is working on it, ill see what he has done and try to get it in a build soon
[Captivate Android Development] lpsi2000:
I hear you and I am checking them as I do with all kernels. So far with all tweaks off no COD yet. I think I need more time to confirm that is good. So give me until tomorrow since I am going to have it on regular AC tonight.
[Captivate Android Development] bsc7080xsc:
Anyone running Continuum 2.1 with this kernel ? Curious what your OC/UV settings are, as well as tweaks. For the most part I have it all working, but its a little off and locks up sometimes. I have turned on all the tweaks with exception of the VM manager and converted things over to the Ext4 filesystem structure. Its looking like I will need to go through the process of trying different settings and seeing how they hold up while run the stability tester app.

Thanks in advance.
[Captivate Android Development] Nickel Dime Bay:
could someone plz explain what states would need to be checked off for 1280? or the 1300 one? i feel like im messing up when i check/uncheck those, thanks.
[Captivate Android Development] sixstringsg:
Check all of the ones up to 1000, and then one overclocked one.
[Captivate Android Development] Nickel Dime Bay:
Thanks, when trying to install the voltage app I get a parsing error, I did a fresh flash from stock to serendipity 5.2 a couple hours ago.
[Captivate Android Development] lpsi2000:
OK, I have confirmed the COD still exist even by changing UV and making it less aggressive then my signature. With all tweaks off, and UV from 1.4 down is 25 50 50 75 75 75 75 75 75 75. COD only exist when charging via computer USB. I left it all night on the AC charger and I had no issues with any UV settings. My next steps is to turn all tweaks on and only use the AC power to see if I get COD.

How to duplicate the COD: Left the phone on regular AC until it get to 100% then I plug into the computer USB for about 1 hour then when I return it is seating at the big green battery saying 100%.

Edit: I also notice using the Voltage Control app that my UV / OC settings don't get apply until I launch the app and apply them a second time. I don't remember having this issue with other kernels prior to this one, so I will try other kernels later today to confirm.
[Captivate Android Development] existz:
Alright a break from the charge death for a min, before it kills me, how many people actually use 1360/1400 steps? I mean 24/7 as their daily? The reason I ask is, I've been wanting to go back to where I started....battery life. Ive been wanting to ditch the 2 higher speeds for 600/900 steps. The 600 step is really what I think could help some, since its a big jump from 400-800. I have a test build im running and so far so good. But if there's a big enough request I might keep them. Im not meaning you just set them for a hour or so and go back to 1280, I think the 600/900 is something everyone will benefit from instead of a couple lucky ones with the higher speeds. Let me know what you guys think, if the request is high enough im sure I can try to make everyone happy
[Captivate Android Development] ccdoggy:
I love your kernel and really only go to 1.1, i dont really use my phone for anything that requires more. 600 would be a great step for the cpu. I am all about battery life and really appreciate that you are too.

so you are limited by something to how many steps you can build into it?
[Captivate Android Development] existz:
Actually no, I could keep the 1360/1400 steps with the 600/900, but was just going to remove them if they wasn't used that much. But if alot of people use them I will keep them along with the 600/900
[Captivate Android Development] neffarious:
i only use 1280 any hard work at 1300+ and i get frozen. I also get better benchmarks (not a bench racer, just using them for comparison @ a given speed) with 1280 than 1300. 1400 freezes almost instantly. Also I have the same issue with the poster earlier where you have to apply the UV/OC settings twice to get them to work.
[Captivate Android Development] shawn122:
1280 would be fine for me as well
[Captivate Android Development] slider2828:
I agree too 1280 is the sweet spot.... 1300 just doesn't rock....
[Captivate Android Development] lrs421:
I agree with 1280. In fact, I never go past 1200.
[Captivate Android Development] ulupinar:
1400 works fine for me and I am using it. I prefer to keep it.

Thanks
[Captivate Android Development] RonH54:
Under SpeedMod Options---->LagFix there is a Enable Lagfix...DATA EXt4 then there a Convert System Ext 4/RFS is it Recommend to do Both Data and System to Ext4?

Thanks
[Captivate Android Development] Auridran:
I agree. Even with not being able to undervolt 1400 at all, I can undervolt the rest so much that my battery life is still stellar. I get around 30 hours with the crappy 1500mAh eBay batteries.
[Captivate Android Development] KreacherComfort:
Wow... I'm in lesbians with this kernel. Best thing that happened to me all day.
[Captivate Android Development] zerkai:
What settings are you using?
[Captivate Android Development] Auridran:
From 100 to 1000MHz is all at -150.

I'm currently at over 16 hours at 79% battery with the stock Samsung one.
[Captivate Android Development] ulupinar:
Wow, that is good batter life. Did you do anything during the 16 hours or it is just standby time. Either way it is very good.
[Captivate Android Development] ulupinar:
Screen brightness/darkness

Hi,

I started using this kernel yesterday. Everything seems to be good. However, I have one issue which is from the speedmod kernel. The screen is intentionally made darker in auto mode than samsung preset. Is there a way to bring the auto brightness to stock level? There are apps like Screen Filter than lowers the brightness but I could not find anything that brightens it.

May be can we have a variant of the kernel with stock screen brightness?

Thanks
[Captivate Android Development] sixstringsg:
He's been talking about making one without that mod, but it hasn't been done yet. Until then, there isn't anything you can do except don't use Auto.
[Captivate Android Development] meridianblade:
Yes! I would love this, I can't even get 1200 to run stable lol
[Captivate Android Development] sixstringsg:
How much do you UV at 1200?
[Captivate Android Development] existz:
Not right now, I've talked about maybe doing a variant but there's alot of things I want to do/fix first, but maybe after I iron those out I will
[Captivate Android Development] c0ldburn3r:
Ugh don't need another kernel to test! lol maybe once we nail down the CD issue e might look into it but that adds two more versions he would have to update, don't know about you but that's a bit to maintain.

Testing one last setting out but I'm pretty sure the CD issue has been resolved, will know for sure tomorrow morning. ;)
[Captivate Android Development] sjavvaji:
isn't it just possible to include the 600/900 steps without removing the highest 2...i would like to use 100, 200, 400, 600, 800, 1000, 1200, and 1400

EDIT: sorry...i didn't read :D
[Captivate Android Development] Auridran:
Probably 40 texts sent and received, and 20 minutes of display time.
[Captivate Android Development] sjavvaji:
plz keep it
[Captivate Android Development] sjavvaji:
yea i get just about that too...i run 1.4ghz with uv of like 100ish on all frequencies lower than it...i can attest to similar battery life...existz...u rock
[Captivate Android Development] c0ldburn3r:
Gone! Whole point of this kernel is battery life not overclocking. ;)
[Captivate Android Development] sjavvaji:
but its nice when u can sacrifice an hour for some incredible speed...id prefer to have both speed and battery since im not a battery extremist...but is it rlly gone (since u are smr testing)?
[Captivate Android Development] c0ldburn3r:
Yes, eXistZ and I both agreed it was better to trade off those upper speeds, which most user couldn't even oc to, for speeds that will allow the battery to last longer. You can still oc to 1280 but nothing higher.

Note: You still have incredible performance you just can't oc as high, imo it's useless and very unstable for anything past 1280. Personally I only clock to 1120.
[Captivate Android Development] sixstringsg:
Very rarely does your phone go that high anyway.
[Captivate Android Development] c0ldburn3r:
+1 Agreed.

Sent from < clever remark here >
[Captivate Android Development] r3ferrei:
Is it really detrimental to the rom to keep the high clocks while introducing the lower clocks as well?

Would it impact performance if it was kept in but disabled by default? Sure 1280 is fast but 1400 is even better for those that can. Seems like kind of a waste to lose the option when it potentially doesn't hurt the kernel to keep it in, unless there is a performance reason.
[Captivate Android Development] c0ldburn3r:
8

I wont speak for eXistZ but most users that are worried about going that high usually worry about quad/linpack scores. Useless. If you want to go that high use the Super Optimized kernel. This gives you enough power without killing your battery plain and simple.

Sent from < clever remark here >
[Captivate Android Development] RonH54:
Is this considered CD and possible Kernel related? I recently was trying the Battery Calibration where you Charge the Phone while ON to 100% then Power down and let is keep Charging while OFF when I did this my Phone "locked". I unplugged from AC and after a few tries Holding the Power button it did power back up.
[Captivate Android Development] sixstringsg:
Did your phone do this while it was on?
[Captivate Android Development] LimaI896:
600/900 have my vote.

Disabled that tweak last night and didn't get a cd but of course when I unplugged my phone it went to 99%.
[Captivate Android Development] sixstringsg:
Yeah, that's a "feature" in 2.2.1.
[Captivate Android Development] c0ldburn3r:
Its the way batteries charge now. They hit 100 then stop charging and drop a bit then charge to 100 etc..

Sent from < clever remark here >
[Captivate Android Development] r3ferrei:
I have noticed a definite increase smoothness, especially in the browser during rendering and even an increase in the rendering speed itself which is why I would miss the option. I could care less about scores to be honest. What I care about is the user experience which is noticeably increased with the overclock.

I just figure if its there already and it doesn't hurt to keep it", then just leave it. Those that use it do so at their own risk.

But that's just me. I would still use it with only 1280 but it would be nice to have the 1400 option too.
[Captivate Android Development] ccdoggy:
How is the Headphone passthrough supposed to work? Until the latest kernel its been perfect to use with the headphone/mic combo that comes with the phone.

I installed the latest and now it does not use the mic on the headphones, just uses the phone's mic. that works great for those without the built in mic, but it would be great to be able to use that built in mic for the phone.

or is this a problem just I am having?
[Captivate Android Development] RonH54:
No it occurred after I Powered it Off and it started to try to Charge to 100% again.
[Captivate Android Development] c0ldburn3r:
Works fine here.

Sent from < clever remark here >
[Captivate Android Development] sixstringsg:
It might have just been a little slow, usually Charge death happens when the phone is booted.
[Captivate Android Development] sjavvaji:
exactly so it doesn't affect battery life because it stays downclocked most of the time
[Captivate Android Development] sjavvaji:
agreed...i don't give a living crap about scores, i feel the smoother interface and gameplay...u are just removing a feature that some of us use for whatever reason (psx in my case)...my phone is 100% stable at it and gets good battery life too...with the states feature it doesn't even affect other users
[Captivate Android Development] c0ldburn3r:
No one is forcing you to use this kernel. Remix it if you want, but as of right now the next build wont be going higher than 1280. Your opinion has been heard.

Sent from < clever remark here >
[Captivate Android Development] Auridran:
I get better battery life with this kernel at 1.4GHz than I do with Speedmod. Being worried about battery life with something that is completely optional is just outright silly, especially when the battery life at a 40% overclock is still better than the "best" of the non-OC/UV kernels.

Also: I don't care about getting the best benchmark scores. It's just nice to have my phone running at the absolute fastest that it possibly can while barely sacrificing battery life. 1.4GHz will be nice once I find my FFVII discs and get psx4droid up and running.
[Captivate Android Development] existz:
Alright guys, I just wanted input, its no biggy to leave the higher clocks, I just wanted to see if anyone actually uses it, I can still add 600/900 with the higher clocks, so hopefully I can get a build tonite or tomorrow with these frequencies...

100/200/400/600/800/900/1000/1120/1200/1280/13xx/1400

Still trying to tweak the swappiness, more and more reports coming in that it fixes charge death, should have that fixed in next release also
[Captivate Android Development] sjavvaji:
thank you existz...
[Captivate Android Development] lrs421:
One down, wifi to go :) Sign me up for that test :)

Great work existz!
[Captivate Android Development] RobertInCypress:
just installed the new version of SuckerPunch. Had been using the #34 kernel very happily. Will try this new one out!
[Captivate Android Development] r3ferrei:
Much appreciated.

This is really becoming, if it isn't already, the ultimate captivate kernel. It really does have it all.
[Captivate Android Development] Auridran:
I agree completely. Lower brightness, sharpness, voodoo sound, OC/UV, no i897 logo or AT&T logo, great speed, and fantastic battery life. What more could one want?
[Captivate Android Development] LimaI896:
Oh I was just stating that as maybe k didn't get a cd due to never actually hitting 100%.

Just curious on a past post as I saw if you choose to clock at 1200 you don't check off 1120? As I have both checked off.
[Captivate Android Development] gleonard3:
Wired Headset Phone Calls

Finally! I can make wired headset phone calls and still have Froyo! THANKS!!!!
[Captivate Android Development] lpsi2000:
This just my two cents: Higher speeds is what I am interested in, otherwise their are plenty of other kernels that does well on battery with lower speed.

Now back on the charge of death issue, I had all tweaks turn on all day today and had no issues with COD. The only the difference, I am not charging it via the USB port on the computer. It seems to be fine with the wall charger.
[Captivate Android Development] evrionis:
Would I be able to use this kernel with Phoenix 4.5?
[Captivate Android Development] lrs421:
Existz, no one can question your dedication to making a great kernel even better. Keep up the great work sir.

Donation sent!
[Captivate Android Development] existz:
Awesome! Thank you, I appreciate it alot ...there's more to come :)
[Captivate Android Development] iXNyNe:
+1 vote for focusing on battery life.

600 sounds like an awesome idea, donno about 900, but the way things are looking it doesn't hurt having extra frequencies.

Btw voltage control mentions we should try to stay between 5 and 7 active frequency states, anyone care to comment on that recommendation? Is it bad to use more? Or less? Or does it not matter as much as the recommendation implies?
[Captivate Android Development] ccdoggy:
Works great on 4.5, other then my phone hates me and a replacement phone is on its way.
[Captivate Android Development] froli13:
Can't wait for the 600-900 steps!

Keep it up existz!!
[Captivate Android Development] lrs421:
Strange, mobileap just stopped working for me. Unable to connect packet....This happened after enabling tweaks. As a test a flashed a different kernel and it came back. Then flashed back and got the error message again. Any ideas?
[Captivate Android Development] zerkai:
sorry if this sounds dumb, whats the benefit of having 600-900 steps?
[Captivate Android Development] froli13:
Your phone often uses these frequencies, so being able to UV them will allow you to save precious battery life. (Correct me if I'm wrong)
[Captivate Android Development] existz:
Going to check into it, do you have IPv6 Privacy enabled? Not sure if it would cause this, but its been causing Wifi issues for some..

EDIT

just checked and I have no issues with mobileap, connected fine. As I mentioned above if you have IPv6 privacy enabled, disable it, I've seen it cause more problems than its worth
[Captivate Android Development] lrs421:
No I dont. It worked for the first connection but won't reconnect. I just swapped between hardcores latest and #36 4 times and each time mobile AP worked on the other kernel but gave me an error message on this kernel. Bizzare.

Thanks for looking into it.
[Captivate Android Development] sjavvaji:
Same issue...first occurence...maybe its an network thing...i restarted my phone and it worked fine
[Captivate Android Development] lrs421:
Not for me. I just tried a different kernel as well. Worked immediately but gave me an error message when I switched back to this kernel.
[Captivate Android Development] c0ldburn3r:
Sadly I can confirm this too, tried mobile AP the other day and didn't word but didn't place much thought into it. USB Tether works...
[Captivate Android Development] lrs421:
Misery loves company. I use mobileap quite often :(
[Captivate Android Development] pizz0wn3d:
Well I wouldn't mind it doing my homework for me... It's way better at math than I am anyways.

:P

Herp derp Captivate XDA App
[Captivate Android Development] nachin:
I9000B Kernel add.

Hello existz.

I would like to use this great kernel on my i9000b (brazilian version), Could you make a Kernel version for us? I tried to use this but have several issues with the touch screen.

Or maybe you could share the source and tried to do it by myself.

Thank you for all that you do for the i9000 community :)
[Captivate Android Development] storm68:
I still get charge death no matter what I do, on gb's kernel I don't, I'm wondering if you can add whatever it was that gb did to his that doesn't allow a charge death?

Other than that it's an awesome kernel, good job!
[Captivate Android Development] davwman:
No charge death here with any version. I don't overclock and run only up to 800mhz with recommended tweaks only as well as system and data on rfs.
[Captivate Android Development] lrs421:
Well then you don't count ;) driving your Porsche at 20 miles an hour :)
[Captivate Android Development] davwman:
Funny...However, I'm running ryudes precision, and seriously it's fast...real fast. And not benchmark made up fast, real world use fast without lag. I have used higher clock speeds before and cannot tell the difference with this rom and this is without lagfix.
[Captivate Android Development] Dlev7:
I disabled the VM tweak in recovery and for someone that had constant COD I now do NOT have it.

Now this will be my every day kernel as its super fast, and great battery life.

Great job Existz
[Captivate Android Development] existz:
Awesome :) next version will have the VM tweak to where you can enable it without having charge death. Been trying different values for swappiness, seems having swappiness=0 is causing cd for most people.
[Captivate Android Development] Dlev7:
Well thats awesome, but for now this is insanse I can OC to 1.28, get better battery life than ive ever had. And not have charge death. Impressive work
[Captivate Android Development] existz:
Deleted post
[Captivate Android Development] davwman:
Is the vm tweak a recommended or optional and what does it do?
[Captivate Android Development] davwman:
When's the next release :-)
[Captivate Android Development] existz:
Well its not recommended anymore since its the reason for charge death for most people. So with disabling the tweak it puts an end to charge death, for most people...there's been 15-20 ppl confirm it works, but there's been 2-3 say it didn't make a difference. So if you have charge death disable VM Tweak. The tweak disables swappiness, setting it to 0, so when you disable the tweak it sets it back to samsung stock, 60, I've been messing with different values, seems lower the better, 10 still causes charge death, so far 20 has been the lowest tested with no charge death

As for next release, hopefully soon, I've been doing some testing with different swappiness values, but think I've finally got it, also ran into some issues with frequency steps. I made a test version with 600/900 added and removed 1360/1400, and it works really well, (keeping a total of 10 states) but when I try a version with 600/900 and 1360/1400 (total of 12 states) the voltage control app keeps FCing on me. Apparently I've missed something somewhere regarding the amount of states in the oc/uv code, so im gonna go back over it, whenever I straighten it out ill have a build up. The 600/900 steps seems to really help so I def want to keep them
[Captivate Android Development] nachin:
Source code Kernel

Please existz, can you post the source code of your kernel with OC? I have an i9000b and I want to do a kernel for my sgs with yours.

Thank´s a lot.
[Captivate Android Development] existz:
Link to source is on the first page

EDIT

I also keep my repo updated everytime I put out a new release, so its kept up to date