yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] existz:
Ill be updating the OP Kernel Features as I go along, so don't be surprised if you see it change alot today
[Captivate Android Development] MarlowXim:
Funny I built from your tree using it as a base this morning with my own tweaks.

I added some of the upcoming features as well you can include chainfire ext4/rfs initramfs works well although I don't think ext4 is necessary in comparison. Atleast it gives you the ext4 option. BFQ works pretty well with preempt from my testing. I tried getting SQLB to work but it causes a problem with mounting the filesystem. SLOB doesn't work either from my testing. Although you might have better luck.

Although I can't wait until 1.2 ghz is stable I was testing it the other day in a separate build. Very smooth I was surprised how responsive the phone was. I think that's the biggest significant change to user experience.
[Captivate Android Development] existz:
Ill def have to check out Chainfires initramfs, care to send me a link to the ones you used?
[Captivate Android Development] bobmanfred:
CWM Flashable? Just to make sure... Can I flash this like the 2.2 Roms? If so... YES!
[Captivate Android Development] existz:
Yep, as of right now it uses v2.5.1.2, later on i will update to cwm3 as everything will be using it before to long
[Captivate Android Development] slider2828:
Existz! I have been waiting for this day when you jump on the GB stuff.... Been on JUWE Rom's for awhile and just updated xcals kernel on my gf's phone. Its pretty awesome and battery is awesome...

Can't wait to get some OC / Voodoo feature support! Man its been awhile!
[Captivate Android Development] MarlowXim:
I did a bit of a hack. I extracted it from cf-root kernel. You'll need to search initramfs extraction. I don't recall the utility I used had it for awhile, and I'm away from my pc. It works for the most part although it has an incompatibility with the wifi module.
[Captivate Android Development] IamSonoma:
Slider - I agree. Like you, been on it for sometime now and this beats uses the rotate app and toggleheadset app. :)
[Captivate Android Development] magicman0:
I'm just wondering, why is logcat disabled?

As an android developer, logcat is probably the most important thing I need, which is why I'm curious.
[Captivate Android Development] Shammyh:
Saves battery and CPU cycles if you disable it. Usually there's an option within CWM to toggle it on or off. That might not make it into the first few builds of this kernel, but I'm sure the toggle will be there eventually.
[Captivate Android Development] slider2828:
Wassup Sonoma? What ROM are you using now? I have been pretty loyal to Juwe's rom cause of hte batt life and everything...

My GF got a new phone build like 1156 or some crazy number. SHE SMOKES my phone. For some reason I think its faster and gps locks faster....

I think my 1001 built phone straight fails!

Sidenote: She is using xcal's reoriented kernel with JUWE so far so good!

-Ken
[Captivate Android Development] sinichi21:
Just want to ask is the battery percentage working right now? like when its fully charge its will really show 100% even you unplug it or still the same playing between 97 to 99%.
[Captivate Android Development] goodolsen:
Showing 97-99% is accurate. It is to keep the phone from overcharging. Think of it as a battery safeguard.
[Captivate Android Development] wonner:
I just unplugged at 100% and it dropped immediately to 96%.
[Captivate Android Development] IamSonoma:
Hamsterbread
[Captivate Android Development] existz:
a little update for you guys...

added Chainfires CFRoot initramfs, which includes init.d support, CWM3 and ext4 support via CFs ext4 app.. added SIO scheduler..getting ready to add Voodoo color
[Captivate Android Development] Doug8796:
waiting for the OC. good luck. cant wait!!
[Captivate Android Development] nuwayman:
Sweet. You the man!
[Captivate Android Development] Sqb:
You are awesome thanks for sharing. If not for you and all the devs here there would be only a portion of us out there spanking iphones.

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] LNJ:
So do the rom zips work in cwm 3 just like in 2.5?

Samsung Galaxy S i896 on Cezar's Continuum v5 GingerBread
[Captivate Android Development] used2hvatreo:
Any reason why UV wont stick? I tried to save the settings to boot, but its all back at zero when I reboot. Any suggestions?
[Captivate Android Development] Doug8796:
So is 1.3-1.5ghz in the works? or will another dev do it in his kernel
[Captivate Android Development] AReynante:
I'm hoping for 1.4ghz, but as it stands now, I love it. Runs really smooth.

Which voltage control are you all using? The normal one or EX, and then if EX, which version?
[Captivate Android Development] c0ldburn3r:
Since this kernel is in such an early dev state, I highly doubt that is on the to do list right now. ;)

Got Gingerbread?
[Captivate Android Development] wonner:
I'm using VC EX 1.3.
[Captivate Android Development] squishy5:
maby u could add Tiny RCU patch and low memory killer and more ram aviable and free
[Captivate Android Development] existz:
try updating your busybox with the busybox app

As for 1.4-1.5ghz....give me TIME guys...alot of other things are more important right now, we cant just take stuff from froyo and put it in the kernel, alot of stuff has to be rewrote/ported over, so we are literally starting with nothing and starting over, as I mentioned before, once it gets to being just about features instead of actual development (notice the DEV) tag, then i might go higher and start adding in "features", but we need to get other things actually working first
[Captivate Android Development] grkmaster:
I had a similar issue and was going back and forth with existz. Remove boot settings from voltage control then reboot into cwm and wipe voltage, then set some UV and apply and save as boot. See if that does anything and maybe reboot after you save as boot
[Captivate Android Development] pizz0wn3d:
thanks. I actually just flashed back to 1.2, except now it's showing the 100 & 200 mhz steps as unused as well. Could that be a compatibility issue with cpu spy?

Herp derp Captivate XDA app.
[Captivate Android Development] grkmaster:
Same thing happened to me as well when I did that. It took me a while before it ended up displaying. Are you on Continuum RC3?

FUnny thing is cezar said that its underclock to 1000mhz for RC3 yet cpu spy shows 1200 being used and nothing below 400
[Captivate Android Development] pizz0wn3d:
Yeah. Did you do anything special to get the states to be displayed?

Herp derp Captivate XDA app.
[Captivate Android Development] froli13:
You can grab the sources and it build it yourself without the i897 patches. I *should* work just fine with i9000 SGS
[Captivate Android Development] used2hvatreo:
Thanks existz, I'm having a weird drain issue too so the batt is dead, but I will try updating busybox when I get the damn thing back up and running.
[Captivate Android Development] keitht:
I have the same issue. Updated Busybox to 1.18.4, same issue. Will not stick after reboot even though I chose to save. Any ideas?

Also any suggestions on UV settings?
[Captivate Android Development] pizz0wn3d:
Installed busybox 1.18.4 and cpu spy is showing 100+200mhz as used states again, though deep sleep is still displayed as unused. Hopefully my phone doesn't experience as much battery drain as it was before though. :D

edit: battery stats is showing android OS as using 11% again, I do believe my problem has been solved :)

Herp derp Captivate XDA app.
[Captivate Android Development] existz:
Should have 341mb version up tomorrow, plus a few other small things, still putting them throught test
[Captivate Android Development] pizz0wn3d:
Looking forward to it :)

Herp derp Captivate XDA app.
[Captivate Android Development] keitht:
Are we getting close to BLN support? I really miss it. :)
[Captivate Android Development] harpo1:
existz if I'm already in cezar's irc channel can I just click on your name to get into yours?
[Captivate Android Development] AReynante:
I understand about the starting over thing. I didn't mean to sound demanding or anything.

On a side note, vc ex doesn't have the same stuff it had on froyo for me. I'm running 1.3, but yeah. If this is normal, let me know
[Captivate Android Development] pikachu01:
You could try each of them and report back if they're giving you problems. And which music player are you using? Are you using SetCPU profiles?
[Captivate Android Development] H3llstorm:
Amazon MP3/Cloud player

I'm using Voltage Control, not SetCPU.
[Captivate Android Development] RichMD:
I saw that eXistz listed control freak rather than voltage control. I am using cf since I don't know that vc would be completely compatible with recent kernels builds - should it be and are there any signficant differences? I've also stayed away from SetCPU because again I'm not certain what would be compatiblle. Can anyone "in the know" confirm if we can use any of them without causing any stability problems?
[Captivate Android Development] rajendra82:
The latest version of Voltage Control is fine to use. It correctly allows you to adjust all the settings for OC/UV. The older versions did not allow you to adjust all the settings, which is why Control Freak was written. SetCPU does not allow you to properly enable and disable states, and set voltages for each one, so don't use that one.
[Captivate Android Development] pikachu01:
I'm using the stock music player without any glitches. Voltage Control should work fine. SetCPU should be compatible (unless you're doing something else with SetCPU other than setting voltages)
[Captivate Android Development] Johnsondr80:
Thanks. I got my ubuntu installed yesterday. Not really done anything to it except clicking around. I'm excited to learn and get into developing with it.

sign up for dropbox using this link to get 250mb free and help fusion at the same time.

http://db.tt/cCn3zrY

presented by Xdapremium app
[Captivate Android Development] Koizuma:
So far .18 has been flawless, put the phone on the charger last night about 80% woke up to it being at 100% and only dropped to 98%

and with the charger i got here it charges pretty quickly too so its been sitting that way for a good portion of the night.
[Captivate Android Development] topiratiko:
Cool thanks

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] Josh K.:
Doesn't work, never has for the car dock. The samsung official roms have something possibly in the kernel that keeps the screen on. It works even without the Car Dock app.
[Captivate Android Development] topiratiko:
How far back does this go? I reverted back to .17 and checked voltages and that ones inoperative too

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] iXNyNe:
In reference to the talon kernel here are my opinions about voltage control vs setcpu vs control freak.

I'm currently using talon 0.4.4.18, voltage control 4.2.0 rc3, setcpu 2.2.4, and control freak 0.5b.

All three seem to be able to manage voltages for available CPU states, toggle CPU states, set min and Max CPU frequencies, and select from available governors.

Voltage control offers very basic features and information. VC does its job well and sports the cleanest interface, however interacting with the advanced tab is a bit of a bother since it constantly rearranges the order of CPU frequencies when enabling/disabling them. It would be nicer if they just stayed in order. The apply button covering part of the interface can also be bothersome.

I have no issues with functionality or stability using this app. Everything works fine.

Setcpu lacks the feature (found in both of its competitors) to select from available I/O schedulers. Setcpu is also the only one of the three to offer profiles based on the condition of the phone (CPU temp, battery %, charging state, etc). It also has a very nice info tab which tells you more than you really cared to know and allows you to run some benchmarks and stability tests.

As long as you're NOT using ondemandX you can use the advanced tab to adjust some handy features which can either beef up performance or help conserve battery if you know what you're doing.

I have no issues with this app either, everything works well for me here (including toggling CPU states).

Control freak is based on older versions of voltage control but modified to show a little more information (time in state) and allow selection of governor (current voltage control has this feature anyway). Functionally speaking this app is the exact same as voltage control, but the interface (in my opinion) is a bit cluttered.

This app also causes no functional or stability issues for me.

So if anyone can show examples of one of these apps not working where they should or claim any real benefit to using one over another feel free to educate me.
[Captivate Android Development] rlorange:
Yo

No offence but did most people miss the big deal here? There is a bug in talon just discovered and soon to be fixed which renders ANY voltage control app useless atm because it is not actually changing anything yet showing that it is... the voltage/freq table is not being properly adjusted.

**Simply Honey3.9, Talon kernel1.3ghz**
[Captivate Android Development] kodos96:
That's an excellent article (its been around a while - I've linked people to it a lot)... everything it says is true.... BUT, that said, there actually is a real "charge bug" somewhere in the gb software stack (framework? kernel? both? who knows). If your charging is working right, you should be getting 95+% off the charger... if the charge cycling algorithm is letting it drop all the way down to 70% before cycling back up, then that's as bug.

For a while it seemed like the code I backported from the Infuse had fixed the charge bug ("fixed" meaning always over 95%), but I think maybe we might have reintroduced it in some of the more recent changes. Either that or it was never fixed in the first place and I was just misinterpreting a few days worth of lucky charges as the problem being fixed. Still working on the problem - stay tuned.
[Captivate Android Development] topiratiko:
Wierd. I say that because when i try to undervolt by more than 150mv the phone freezes. Like its being uved too much. Yet voltage table is unchanged? Hmph. Ill just wait for the fix lol

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] kodos96:
Nothing changed in .17 regarding auto-brightness, although it did a few versions back, not sure of the exact version number. Autobrightness has always been broken on GB, on all kernels.... but a while back I backported some new light sensor code from the samsung infuse that seemed to make things a ton better - not 100% fixed (a 100% fix would require framework changes too, not just kernel)... users' reports seemed to agree with me that it was a lot better than it had been before. But then right after that, samsung did a new code drop for the i9000, which included new updates to the light sensor driver, and we merged that code. In my opinion, those updates reverted autobrightness behavior to being just as bad as they were before the infuse backports. So personally I think we should revert - I've suggested it to eXistZ but he had some reason he didn't want to - I can't remember offhand what the reason was. I'll revisit the issue with him when I see him on IRC,
[Captivate Android Development] existz:
0.4.4.19 Public Test

0.4.4.19

Changelog since 0.4.4.18

- fixed issue with UV not writing to frequency_voltage_table
[Captivate Android Development] existz:
IMO, if anything we should revert the infuse changes.., from what ive gathered (mostly from i9000 kernels), that the new fixes from Samsung does seem to have fixed the autobrightness issue ..as long as the correct, recent sensors are used.., so if anyones using the old fix for autobrightness, it needs to be removed
[Captivate Android Development] kodos96:
So I actually did some informal benchmarking of IO schedulers the other day... the thing is, most benchmarks are totally useless for testing IO scheduler behavior, because they're testing the performance of only a single app doing IO... the whole point of an IO scheduler is to divide up IO bandwidth between multiple processes doing IO simultaneously... with only a single process doing IO, then ALL schedulers are effectively a noop, and all you're actually measuring is the complexity overhead of their algorithm.

So what I did is started a process running in the background doing IO (I used firefox, which synchs its database every few seconds, even when running in the background, which is really stupid behavior, but happened to be just what I needed for the purposes of this test), and then running IO/db access benchmarks with firefox running in the background.

The results of my tests were kind of surprising: pretty much all of the schedulers performed essentially the same, within the limits of the precision of my testing..... EXCEPT for BFQ, which performed significantly WORSE than all the others, which is totally not what I expected, since BFQ is supposed to be the New Hotness in IO schedulers. But I ran my tests a bunch of times and that result was totally reproducible.

According to theory, either NOOP or SIO should probably be best for use on flash storage like ours... but the takeaway message from my testing is: don't spend a lot of time worrying about IO schedulers - there's really not much real world performance difference between them on our hardware - just make sure you don't use BFQ.
[Captivate Android Development] watsa:
May be I am overlooking something but what doesnt make sense in all the "charge bug" reports is drop right down to 60% - 70%.

Ok the phone got charged to 100% and then it started to discharge, but I have never heard of a phone discharging 30-40% sitting idle doing nothing
[Captivate Android Development] kodos96:
Had you changed anything from stock settings? Like disabling zram?
[Captivate Android Development] kodos96:
Interesting.... it sounds like the memory configuration (stealing ram back from the hardware reserved ram) might be breaking something. We do a little bit of that even on the non-Bigmem kernel, just not enough to break 720p video recording like Bigmem does, but I had thought that the changes to non-Bigmem were small enough that they didn't break anything... but of course its always possible there's something we just didn't notice until now.

Can you send me a link to a copy of an example video that plays on darkcore but not on talon? If you're not sure how to get me a copy of the video, PM me and I'll set you up with someplace you can upload it.
[Captivate Android Development] kodos96:
Yeah, that's an interesting point I hadn't considered.
[Captivate Android Development] melvinaury:
+1 with you the max drain for me was to go to 88% but I let the connected for 10 hours. That's 1.2% drain per hour.

The person that goes 60 or 70% should check for any drain from an app or services. The bus is that after fully charge it stops charging the phone. It suppose to monitor and after let's said 98%, it begin to charge to 100% again.

That was made to protect the battery in the past the phone continue charging and damage the battery.
[Captivate Android Development] topiratiko:
Kodos just curious did you include v(R) scheduler in your io tests?

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] Thunder22:
What undervolt settings would go well with 1200 mhz overclock talon?
[Captivate Android Development] Coak5:
So I just flashed this and checked the frequency voltage tables after applying my OC/UV profile through tegrak overclock and the voltages still look unchanged like in the previous .18 build. Anyone else getting this?
[Captivate Android Development] existz:
It all varies from phone to phone, each one is different...so it just depends on what your phone likes. Some can handle alot of UV, others cannot handle any
[Captivate Android Development] existz:
Tegrak, SetCPU..etc. do not use the same method as Voltage Control, Control Freak..etc., .. Tegrak/SetCPU was not effected by this, just VC..etc.. The OC/UV code in the kernel was originally wrote for Voltage Control and with the use of the frequency_voltage_table.., so only VC...and apps based on it only use this file
[Captivate Android Development] Coak5:
Ahhh. Makes sense. Thanks existz for all your hard work.
[Captivate Android Development] tmng95014:
I set -75 across the board and this has worked well for me.
[Captivate Android Development] sinichi21:
Just want to clarify what is the old fix for the auto brighness before? All i remember before was watsa saying on his rom that it was fix before on his previous rom
[Captivate Android Development] existz:
There was a DIY autobrightness fix in the i9000 forum by Lukiqq.., according to him, with latest samsung source fixes, those changes need reverted and to use latest sensor .so
[Captivate Android Development] existz:
So i might be on to something with the 'charge bug'.., was looking through some AOSP commits for samsung tree and noticed one battery commit that was reverted, but still exists in our source..., the notes on the commit are..

"We don't want to lie to userspace about the state of the battery.

When charging is complete, the battery will drain until it can

charge again. If the user disconnects after the first charge cycle

is complete, the battery level may jump from 100 to 95% or less."

So ive ported the fix over to ours and trying it out now.., of course its going to take awhile to actually see if it does help/fix the issue.., if it does then ill include it in the next test... *fingers crossed*...all though this is just a hunch, and could possibly do nothing, but im hoping
[Captivate Android Development] topiratiko:
That HAS to be it. Describes it spot on

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] topiratiko:
Id be GLAD to test a test ;D

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] disellusional:
but some users can leave it on and take it off and have 98-100 while others get 60-70..

if say, the phone starts charging again at 85 or 90, there should no reason for a phone to come out 60-70 when unplugged.
[Captivate Android Development] lowlymarine:
While that's true, it's quite possible the commit was reverted because it was behaving incorrectly or inconsistently, which could explain our issues.
[Captivate Android Development] iXNyNe:
regardless of the voltage bug the apps can all still be used to set min/max cpu frequencies and governors, and do other things depending on which app you chose. i made my post knowing full well about the voltage bug, i just wanted to explain the benefits of each as well as express my opinions, and attempt to answer a question asked a page or two back about stability using one app vs another

so does this mean those of us using tegrak/setcpu have been able to set voltage levels the whole time and have not been affected by the bug fixed in 0.4.4.19?

also here is an open question to all - is there any REAL benefit to using voltage control vs control freak vs setcpu vs tegrak apps with the current test releases of talon?

all i've seen so far is a lot of people saying use control freak because 'it just works better' and 'its built for talon' and i really havent seen any benefit one way or another myself
[Captivate Android Development] Peaster111:
I've used all of them and can honestly say they all work equally well for OC/UV purposes (they essentially do the same thing). Given I only use the OC/UV functions I stick to either control freak or voltage control. I'm currently running control freak because of the dev relationship with Talon (it's a good gesture thing).