yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] kodos96:
OK, so either one of two things is going on here with this post:

1) You didn't realize that it was eXistZ himself who was talking with a fellow developer about a test build, or

2) You did realize that, but your real issue is not that test builds are being talked about, but that they're not being released to the public.

If it was option 1, well, now you know. If it was option 2, well then that's a pretty silly thing to be upset about. Nothing is being withheld from the public - everything is in git for you to build from source if you want to, and test builds are made available to basically anyone who shows up on IRC and demonstrates some degree of technical competence and understanding of the risks they're running by flashing untested code. If you don't have the know-how to obtain a test build via one of those two methods, then really we're protecting you from yourself by not making it any easier for you to brick your phone.
[Captivate Android Development] mrhaley30705:
Well said, bravo.

Now, lets get back to kernel development, shall we?
[Captivate Android Development] existz:
Non-OC version of Talon coming in next release... Also will include 1200, 1400 and possibly 1440 versions. With the OC versions I removed the 200mhz step, since most governors (ondemand/smartass..etc) rarely use it, I doubt it will be missed much...plus I removed it so there was the same amount of frequencies, saving me some work :P..
[Captivate Android Development] watsa:
I didnt realize that me giving a happy feedback will be such a big issue with some people.

Existz aplogies, will try and PM these things in future so that your lovely thread stays clean
[Captivate Android Development] existz:
Dont apologize, theres nothing wrong with 2 developers talking about "development".. all i asked was users not discuss test builds, to keep down on confusion, since most dont post what versions they are running, causing problems trying to figure out whats happening with what version...But if we are discussing development, theres nothing wrong with that,,,but you done nothing wrong ..no need to apologize to me..and honestly, any rom dev/app dev can discuss whatever they want in this thread..thats what this is all about, development
[Captivate Android Development] topiratiko:
YES! Will give this a whirl....if sleep death comes back ill just switch to your noname kernel :D

Sent from my 2.3.3 Ext4 Fresh Ginger Blue equipped Samsung Captivate.
[Captivate Android Development] irishvandal:
OMG, what did i miss? lol. a storm came through atlanta that took down some trees around us and i come in here and find trees down as well. okay, so answer this ppl, who has the biggest **** now? lol. jk. (no need to answer that because your lies are not development, lol).

on a serious note, i am putting Blue Banshee on hold. The current public builds of Talon 0.2.2 series will not play nicely with Serendipity7 build 1or2. This is under various themes from several devz. I can throw the Serendipity4.1 kernel in and cant find a weakness other than response(lag-speed-etc). i am going to give Continuumv6R1 a whirl and see if it can give me the stability I am desiring.

existz - yes, this means i am going to try out your input from last week. i just cant leave Talon alone, lol. its like crack, i need more. lol.

sidenote - has anyone found a way to do a "Proper" MasterClear of GB? Froyo had Odin-MasterClear that actually passed an AT&T agent ID-10-T test. Was looking for a similar solution to possibly wipe any dirt inside of my Cappy.

existz - from my inept observations of different versions applied to this Cappy, the Zac-Talon 0.2.1 seemed to be the most well rounded and smoothest of all thus far. with S7 thrown on top of course.
[Captivate Android Development] zacharias.maladroit:
mainline talon is getting there :)

mainline (most likely) will be even better than that (with the GPU overclock and other nice additions)

from what I saw kodos included Juwe11's OOM + my memory settings

or at least parts of it

let's make the best kernel out of it available for the SGS / galaxy s series ^^
[Captivate Android Development] golfslicer:
I flashed Continuum 6RC1, booted, took forever. Restored apps. tried to run SetCPU Donate 2.14 on two different Captivates and rebooted. No boot after about 3 minutes. Flashed Excalibrand 2.0 and the phone rebooted in less than a minute. Flashed the Talon Kernel from Continuum 6 again and no boot, tried the one posted here and no boot. Flashed Excalbrand again and booted in less than a minute, whats up, anybody else having this problem with Continuum 6.
[Captivate Android Development] froli13:
Same issue on ApeX. Even when I just reboot after pushing a new SystemUI.apk, flash modem... It seems to be random.
[Captivate Android Development] mrhaley30705:
removed......
[Captivate Android Development] watsa:
Nevermind...
[Captivate Android Development] mrhaley30705:
Your right.

Removed. I have followers?
[Captivate Android Development] mrhaley30705:
Can someone explain what a redbend ua file is? I have came across this twice in the last week, and I have no clue what it does
[Captivate Android Development] geokilla:
It was option one.
[Captivate Android Development] bryman27:
It's the tool used by almost all Captivate developers to flash kernels and modems through recovery mode.

That's the simple definition.
[Captivate Android Development] shane87:
I am running Apex 7.1 and I have had no major boot problems. Then again, I have not tried flashing any modems/themes/etc, so that may be why I am having no issues.
[Captivate Android Development] johan8:
redbend_ua is a "software" to dump and write data to block partitions.

so it is used to write kernel, modem to bml partitions in all CWM pack.
[Captivate Android Development] kodos96:
Huh?

Are you talking about the example ram.conf I sent Juwe11 to include in his rom? That was just for him, not for mainline Talon.

So here's the deal: the way that you/Juwe11/Darky have been setting LMK settings in your ram scripts is not entirely correct - you're just setting the kernel LMK thresholds, but there are actually two sets of LMK settings in android: one set of kernel settings, and one set of userspace settings, and the two sets need to match each other or else the kernel and userspace end up disagreeing with each other about which set they're supposed to be using. When you just echo values to the LMK /sys/ handles like you guys are doing, you're changing the kernel settings, but leaving the userspace settings at stock, which is results in non-optimal behavior.

Talon solves this problem with a script that takes a set of LMK values (from a provided preset, or from user-supplied values) and applies them to both places, making sure they fully take effect, and that the kernel and userspace are both on the same page about which settings they're supposed to be using. But when you then put a script like yours or Juwe11s in init.d, you end up overwriting the kernel values, and you're back in the same situation with half your system using one set of LMK values, and the other half using another. The correct way to set custom LMK values in Talon is by putting them into /etc/ram.conf - if you really want to use Juwe11's settings, you can put them in there and they'll get applied correctly, instead of only getting halfway applied like they are if you just write to the /sys/ handles in an init.d script.

But really, you don't want to use Juwe11's settings on Talon - I'm sure they work great on other kernels, but Talon uses ZRAM, which has a major effect on how your system uses ram, so it's highly unlikely that a set of LMK values developed on a different kernel, without ZRAM, will work optimally on Talon. I explained all of this to Juwe11, and recommended that he remove his LMK settings from his script and just let Talon use the settings I developed, but he seemed really attached to his settings, so I helped him out and showed him how to incorporate his settings into ram.conf - I figured that although those settings may not be optimal on Talon, if he's going to use them in his rom, he'd be better off at least using them correctly and making sure they get fully applied. But those settings are not getting merged into mainline Talon. I'm still actively working on fine-tuning Talon's default LMK settings, and I appreciate feedback to improve them, but just using a script like Juwe11's is not the right way to go about doing it.

That's just the LMK part of the script I'm talking about.... I realize there's a bunch of other tweaks in that script, and I'm open minded to the idea of merging them... honestly I haven't had a chance to take a look at them yet, but it's on my to-do list (along with all the git commits you made against Talon awhile back).
[Captivate Android Development] alkiter:
When do the rest of us get to try 0.3.1?
[Captivate Android Development] Vivified:
When it releases. Patience is a virtue
[Captivate Android Development] existz:
Hopefully soon.. finally hitting the home stretch with 0.3.1, just cleaning up some small bugs and testing a few things... hopefully next day or two (give or take)
[Captivate Android Development] Koizuma:
Can't wait to give it a go, what all can we look forward to in 0.3.1? since i been seeing a little about GPU OCing im guessing thats gonna be tossed into the mix?
[Captivate Android Development] froli13:
I am flashing theme and pushing apks to phone many times a day when working on my theme, and reboots (mini-bootloops) happens often. I flashed existz nameless kernel yesterday. Everything seems fine for now.
[Captivate Android Development] existz:
Well, we are getting close to the home stretch with 0.3.1, just fixing up a few small bugs..etc..and testing a few small things, but the most part of 0.3.1 is ready.. So probably in a day or two..(give or take).. But its getting there.. There will be quite a few changes with 0.3.1, and a few new versions introduced..there will be..

Non-OC Talon (100-200-400-800-1000)

1200 Version (100-400-800-1000-1200) **

1400 Version (100-400-800-1000-1400) **

1440 Version (100-400-800-1000-1440) ***

** Notice that 200mhz was removed, this was done to keep the amount of frequencies the same, which with the Ondemand governor, it scales from min to max, so 200 is not used much at all (only seconds over hours of time...but remember that with 0.2.3 if usb is plugged in, it doesn't drop below 200 (stock default)...in 0.3.1, I set it to 100), so it wont be missed any.. this is also why there is not a 1200 version in the 1400/1440 versions.. since it does not scale through the frequencies like it did on froyo, just goes from 100 to max in one jump.. so it wont have much effect any battery/performance...been running it for days and get the same battery life...

*** The 1440 version is a maybe, not sure if ill release it yet, IMO 1400 is more than plenty, but i might anyways (1440 will be the highest i go for now)..

Also, with 0.3.1, it will include GPU OC (thanks TheEscapist), you will be able to control the gpu oc with Control Freak App... The gpu will default 200mhz by default, then with the app, it allows a 200mhz OC (400mhz max).. which its only the initial support for gpu oc, so it may/may not work,, it may/may not have bugs..this is expected, its just initial support for it
[Captivate Android Development] goob1284:
Cool beans man!! Im stoked
[Captivate Android Development] existz:
Actually scratch my last post...ive went back and added 200mhz in...i was trying not to, so it kept things clean in the source, but i said screw it and added it back :P ..so it will be..

non-oc (100-200-400-800-1000)

1200- (100-200-400-800-1000-1200)

1400- (100-200-400-800-1000-1400)

1440- (100-200-400-800-1000-1440)
[Captivate Android Development] shane87:
Just as a curiosity, why add 200 back in? I mean, was not having 200 causing issues? And I'm guessing here, but the only difference this will make when it comes time to flash is you MUST delete S_volt_scheduler, correct? Which I ALWAYS delete svoltscheduler before a kernel flash. I forgot too once, and it wasn't pretty, lol!
[Captivate Android Development] geokilla:
Is such a jump in states good? The speed difference between 1000 and 1440 is quite huge... Of course if the CPU ain't stable at 1440, I can try 1400 by switching to another kernel.
[Captivate Android Development] existz:
With ondemand, it does not scale through the frequencies like it did on froyo or with conservative governor... most of the time the cpu will scale from min to max and vice versa., rarely using the other frequencies.. even if there was a 1200 inbetween, it would rarely even be used if 1.4 was max

But its either this way or I have to just set 1.2ghz as max...because for some reason, certain apps/launchers is making it scale to the max available clock no matter what max clock is set to...for example, if I made a build up to 1.44, and you only wanted to use 1.2ghz, or even 1.4ghz, it would still jump to 1.44 periodically...so if you cannot handle 1.44, then it can cause stability issues... so with 0.3.1, just use the version you are stable at .. this is the only way I can offer higher oc options... And to be completely honest, this is easier on me..
[Captivate Android Development] zerkai:
Does the kernel know by default to read from ram.conf? Or was there something you have to enable first?

Swiped from my SGH-I897 using Tapatalk
[Captivate Android Development] Koizuma:
good to hear exists, I wouldnt mind a 1600MHz version but the only time i really used 1.6GHz was using emulators but everything else has been ran at a happy 800MHz and when just using the phone or doing text messages i been running 200MHz (all of which has been stable for me)

but keep up the awesome work!
[Captivate Android Development] zerkai:
Nice. Are you using setCPU profiles?

Swiped from my SGH-I897 using Tapatalk
[Captivate Android Development] existz:
Yes the kernel reads from ram.conf by default, the ram.conf file is Talons custom way of controlling lmk, it controls both userspace values and kernel values so that it writes custom settings to both places (via presets in the file)..instead of how scripts just write to the kernel settings...
[Captivate Android Development] Koizuma:
Nah, i used Voltage Control land set up voltages from stock then stability tested it at each step
[Captivate Android Development] kodos96:
Are you asking whether Talon reads from it by default, or if the linux kernel in general does? Yes to the former, no to the latter - it's a custom thing I implemented for Talon, so you can't use ram.conf on another kernel, unless its author integrates my scripts. But on Talon it gets read by default, you don't have to do anything to enable it (if you want to use your own settings rather than one of the presets, you have to change PRESET to 0).
[Captivate Android Development] roadrash7:
What is the best governer. I am trying conservative right now cause it sounds like it makes sense for best battery and it seems to be using all the frequencies more evenly.
[Captivate Android Development] existz:
Ondemand, that's why its default... it does not scale through the frequencies like conservative does, when there's load, it scales to max. .(getting to max faster, giving smoother results.) When there's no load it drops to 100 (getting to min freq quicker, giving better battery life) ..this is just my opinion, conservative does not run very well for me

Sent from my SGH-I897
[Captivate Android Development] roadrash7:
Cool i will stick with ondemand. it did seem a little bit laggy (conservative) but not too bad. the way it was in all the frequencies evenly though i thought battery life was gonna be a lot better but i couldnt tell i think it might have been worse. Thanks man
[Captivate Android Development] tmng95014:
Stick with default dude. Similar to what Existz runs.
[Captivate Android Development] Koizuma:
On demand is what I use as well and had no issues so far, and i got my phone running from an 100MHz to 200MHz range with being undervolted and had no issues yet like that. I need to fully charge my phone and see what kinda battery life i'd get. 9h, 46m sitting on 74% right now.

I tried messing with the other governors but they actually locked my phone up when running with this setup
[Captivate Android Development] existz:
Yea, IMO ondemand works best with Talon..with conservative, it actually comes to a crawl..very very un-usable for me..which YMMV.. but i have tested various governors over the life of Talon (even tested again with 0.3.1), with smartass and interactive, but always end up going back to ondemand.. Smartass has a problem with my builds above 1200, will not scale down, and interactive just has hiccups from time to time...So IMO, ondemand is the most stable/reliable..and gives best results for battery/performance.. I will probably be sticking with it for awhile
[Captivate Android Development] zacharias.maladroit:
yeah,

and besides that it - thank God - doesn't have regressions (from my usage + testing patterns so far)

otherwise we might have had to revert to an older version :\

how's the autogroup (automatic tty task groups) going ?

is it stable ?

e.g. on CM7 kernels the autogroup & BFS scheduler lead to reboots + instability very often for me

the stock-based kernels seems to be of a whole different nature

I've still some fixes in store for that patch so when I find some time I'll send you a pull-request or simply point to the commits

Thanks !
[Captivate Android Development] existz:
So far it has been really stable..havent had any issues with it yet, its been a few days now i dont have anything bad to say about it... smooth as butter :P ... Which ive been looking into BFS but cannot get it to build without errors, which ive only messed with it once and moved on (most of my time has been into revamping the oc/uv layout.. trying to get the best possible combinations, while keeping it pretty simple).. But i will probably dig back into getting BFS working, just for the sake of it I just want to try it :P
[Captivate Android Development] IDoMy0wnRacing:
I can't get voltage control to run faster then 1000Mhz on t4?

Don't remember having that problem before.
[Captivate Android Development] existz:
Depends which version you are running, with 0.3.1 they are individual OC versions aand there's a non-oc version...so if 1000 is all its showing, then its probley just the non-oc version ...there will be non-oc, 1200 version and a 1400 version (100-200-400-800-1000-1400) ...im not doing all in one OC versions for now, they are unstable

But either way, I cannot support test versions, there are more test versions since T4 that have alot of fixes in it...currently on T8

Sent from my SGH-I897
[Captivate Android Development] rlorange:
@Exitz just wondering about overclocking the GPU. What sort of stable oc are you guys getting? Also are the risks the same as CPU oc? Finally what should I look for in terms of signs of instability as I scale up?

Oh and you have a pm :)

**Simply Honey3.8, Talon 0.3.1 t5 kernel1.4ghz**
[Captivate Android Development] shane87:
Well, I designed control freak to take advantage of gpu oc, and I have ran considerable tests on gpu oc. So far, I have seen no stability problems with gpu oc, and I have ran the gpu oc'ed to 416mhz. The stock gpu clock is 200mhz. Right now, control freak only supports gpu oc to +200mhz. As far as signs of gpu oc related instability, I am unsure of specific problems, as I have had no problems, but I would imagine that gpu instability would cause glitches in rendering of graphics, especially tearing and stuttering of moving images. Also, keep in mind with the gpu that the gpu chip in these phones are designed to run at 400mhz, but samsung underclocked them to 200mhz. So really I have never even oc'ed the gpu chip that much. As always, ymmv!
[Captivate Android Development] rlorange:
Thanks heaps for that great explanation! So I'll ramp up to 380 I reckon. Already using your great app to control my freaky fast phone! Just hit 3330 on quadrant no stagefright. :)

**Simply Honey3.8, Talon 0.3.1 t5 kernel1.4ghz**
[Captivate Android Development] shane87:
No problem man! For right now, voltage control goes in steps of 25 on gpu oc, and there are 8 steps for a total of up to 200mhz above stock settings. So you could either go to 375 or 400. Well, I guess the final frequency may be different if you are running one of the test kernels that had a stock oc added, since control freak simply adds the gpu level you select to the stock value, so if you have a stock value of 216, your max would be 416. I know on 0.3.1 t8, ex removed all stock oc, leaving the initial values at 200 mhz on all states except for the 100mhz state, which defaults to 100mhz gpu clock. I may add more steps, depending on stability, or I may change the size of the steps for more fine control, or both, I haven't decided yet. Good luck!
[Captivate Android Development] Koizuma:
If it's not to much of a problem existz could you post up the talon image used when the phone boots up? Since I had to go back to stock I got the lame i9000 start up screen and would like to replace it with the talon one to give me a nice clean start up sequence.

Swyped from my Samsung Captivate using XDA App.
[Captivate Android Development] existz:
Here ya go...

http://berryfx.com/RobBeane/Kernel/Files/talon10.png

Sent from my SGH-I897
[Captivate Android Development] sinichi21:
Running the talon its best when I dont use the wifi the moment it reboots due to turning on the wifi i get in like 10 times reboot cycle is there a way to toggle wifi in recovery mode xD

Edit: Hmmm seems the t-4 solve my wifi random reboot thanks exist for a great kernel
[Captivate Android Development] topiratiko:
@ Existz

Thanks for your continuous development and support.

Confirmation :6V886909TV984492S
[Captivate Android Development] TonyStark R.I.P.:
I too had offered the same sentiments a couple days ago;)
[Captivate Android Development] existz:
Its much appreciated guys!..thanks alot!
[Captivate Android Development] bballer182:
Is the framerate locked @ 55.5fps in 0.3.1? All I can get no matter how fast I oc the gpu is 55.5 in neocore. And antutu says the same score for 2d and 3d no matter how much oc I throw at the gpu. Any thoughts?
[Captivate Android Development] existz:
Yes fps is locked at 56fps (refresh rate = 60)... i will not unlock it, as of now anyways....when raising the refresh rate it washes colors out at min brightness, causing blacks to turn brownish/redish... But having gpu oc will help with other gpu intensive task, such as browser rendering..etc..
[Captivate Android Development] shane87:
I thought the fps was locked at 65? At least that's what I remember from froyo. And knowing that the fps is locked at 56, I have a question. Is it normal for the fps to ocasionally spike above 56? I have seen the fps counter in quadrant tests occasionally spike to 65 for about half of a second. Just curious.
[Captivate Android Development] iXNyNe:
So when overclocking the gourmet is it best to oc each CPU state to the same gpu level? Ex say I choose 375, should I set 375 on all CPU states? Or should I be attempting to vary them based on voltage for the CPU?

It seems like a great concept to oc the gpu but it also seems that there is very little explanation about the procedures, whereas there are some decent guides to CPU undervolting and testing overclock stability.
[Captivate Android Development] bballer182:
The GPU is designed for 400MHz and comes in our phone UNDERclocked to 200MHz from the samsung factory. So if you want run it all the way up to 400 and it will not hurt the gpu at all. It will probably eat more battery is about the only side affect.
[Captivate Android Development] bballer182:
Ah ha. Ok cool just wondering if the gpu overclocking was actually working or not. I can't find an app anywhere that tells what the GPU is actually running at or has ran at. Maybe Shane would like to tackle that as well... hint hint.. lol