yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] topiratiko:
When swapiness was set low memory seemed to fill up faster.....the idea behind zram is its compressed ram so u theoretically get more than 340 thats y i left it maxed.

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] mkr14:
FPS cap increase

Any chance that you can increase the FPS cap to 60+? Fpse emulates at 60fps and some games dont play nice and glitch out with the 56fps cap. I brought this up a number of times a couple months ago and no change.

The Snail kernel and the 2 non-stock CM7 kernels raise the cap and I have no issue with them. Everything runs great.

You mentioned that there is some bug in the Samsung Gingerbread ROMs. Is this still an issue now that we have Voodoo Color?

It would nice to have everything running correctly :)

Your kernel is in continued development and really shines. I would prefer to use your kernel with Samsung GB based ROMs.
[Captivate Android Development] rlorange:
I9000 user if that affects things but no problem with Bluetooth here. My rom is in my tag.

**Simply Honey4.0 JVP, Talon kernel & Tegrak OC app 1.38ghz@1335mv**
[Captivate Android Development] singlag:
is it possible to add USB-OTG support like Xperia Arc ?

http://xdaforums.com/showthread.php?t=1224676
[Captivate Android Development] topiratiko:
So i flashed darkcore 3.1 to see what all the fuss is about...flashed back to Talon after 3 minutes. Contrast JACKED. Colors too warm. Whites are yellow. That alone kills it for me.

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] studacris:
Yes, the contrast is odd, rather the brightness doesn't get all that dim.

But whites are white here...
[Captivate Android Development] topiratiko:
Although talon has 2 issues, i choose it over anything because of sheer control it gives its user. This bluetooth issue is kinda scary tho.

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] Yuna:
What the BT issue itself? Neven encountered, on .21 test me am.

and yes, we need voodoocolor v2 -which is out there
[Captivate Android Development] topiratiko:
More than one user has reported filesystem corruption when using bluetooth headsets. Phone shuts down and starts to convert to voodoo while already on voodoo (from what ive read) and requires flash 2 stock. Its not widespread but its there. Hence test builds pulled and under scrutiny. I dont use bt so im not trippin.

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] Yuna:
I just dn't use headsets too :) Just a PC to OBEX
[Captivate Android Development] tmng95014:
I am on 0.4.421 and Continuum 6.1. I used BT every in my car for my phone conversation while driving. No issue at all.
[Captivate Android Development] Time_Zone:
Hmm, wonder what Cezar is doing different.
[Captivate Android Development] aalh:
FYI I have been on 0.4.4.21 since it was put out

I just used BT to xfer a file to my pc

no reboot, but it did reload the desktop (ADW EX)

no odd behavior othwerwise

I can't find my headset so I havent tested BT calling
[Captivate Android Development] Darryl Henley:
Using Continuum v6.1 and TalenDev 0.4.4.21 Nexus S setting with LauncherPro Plus

Testing BT connecting to PC, transfered files and listening to music from phone through BT to PC. working great.

The only problem I have is wifi randomly turns off. This happened before I even started testing BT.
[Captivate Android Development] kodos96:
I don't see any disclaimer on this post.
[Captivate Android Development] topiratiko:
Im not sure what you mean about there not being a disclaimer on this post. This is a link to a thread with settings that I find work well for me. In this thread, I explain how I tweaked these settings to what felt better for myself. Turns out, after memory freak debuted, that the settings I ended up with were similar to Nexus S settings. After seeing Nexus S settings, i tinkered with them just a TAD more. In this thread, I thank everyone, INCLUDING yourself, and give proper credit where its due. Please explain what "disclaimer" I must leave in my posts.
[Captivate Android Development] alexige:
I believe he means the usual "noone is holding a gun to your head so don't come running back to me with a brick if stuff goes wrong" type warning
[Captivate Android Development] topiratiko:
Its in the OP of the linked thread.

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] aalh:
Yup

The CYA Clause :p
[Captivate Android Development] jerkysh:
a test or a normal version is wanted :D

especially a BIGMEM one
[Captivate Android Development] tmng95014:
Same set up as mine. You may want to turn on/off wifi using setting instead. It will help with stability and no reboot.
[Captivate Android Development] aalh:
Well you do live up to your name, thats for sure.:p:D:p
[Captivate Android Development] studacris:
Trolololol
[Captivate Android Development] existz:
0.4.4.22 Public Test

0.4.4.22

Changelog since 0.4.4.21

- ARM: more aosp/upstream ARM fixes

- cpufreq: fixed ondemandX wakeup issues

- voodoo: add new i9000 partition table support

- usb: read/write speed hack for mass storage

- reverted: parts of infuse wifi and power fixes

NOTES

UPDATE: So it seems this release does in fact resolve the bluetooth causing corruption issue

BIGMEM version added
[Captivate Android Development] mrhaley30705:
My safe kf1 is full Odin or 1 click. Your choice.
[Captivate Android Development] Time_Zone:
Here I go. I raised the roof on this. I get to play guinea pig.
[Captivate Android Development] tmng95014:
Running Continuum 6.1 with 0.4.4.22. Use BT to transfer files and audio with no issue so far.
[Captivate Android Development] kodos96:
Sorry, my mistake - I thought you were still pointing people to your old settings. These new ones look much more reasonable... and in fact, not much different from the Talon default settings.

Two things to keep in mind though:

-you probably want to lower the HOME_APP_MEM to where its a notch lower than the ones that come before it (i.e. on your settings, that'd be 4096). That will help keep your launcher from getting killed.

-You're probably not getting a whole lot of actual benefit from raising SECONDARY_SERVER (and the others at that same level) up to 7168, since those are the ones that respawn automatically after they're killed.... if you raise that too high you can end up with "service thrash", where your services keep getting killed and restarted, hurting performance and battery life. It's hard to say whether that will actually be happening to you, since it depends on what services you run... you should check in logcat when you're under memory pressure and make sure that's not happening.... or just notch that level down a bit to be safe, since, like I said, even if you're not hitting service thrash, there's not a whole lot to be gained from aggressively killing processes that are going to respawn immediately after.

And with those two minor tweaks made.... well... then you're basically right back at where you started, with Talon's default settings ;)
[Captivate Android Development] topiratiko:
No problem. Thanks for the advice. Everything seems good...if i use stock talon the leak surfaces ALOT quicker....thats why i jacked them up a bit...closer to nexus s than talon really...was kinna stoked to see what i came up with was validated through current nexus settings. Does this update mean wifi reboots are back?

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] tmng95014:
I have not seen it. Running Continuum 6.1 with 04.4.22. Turn wifi on/off via setting no wifi reboot so far.
[Captivate Android Development] CuriousTech:
Charging seems to stop on 0.4.4.22 at some point before it hits 100%. I think it's during sleep but not sure yet.
[Captivate Android Development] existz:
Nothing changed that would effect charging, or atleast cause any issues. ..only thing i removed was the infuse power/pm/charging patches., so if anything it is closer to stock than before. Wipe battery stats if your having any issues
[Captivate Android Development] bigbooty:
Settings don't show in set cpu for sampling freq., up threshold, etc using onfemandx?
[Captivate Android Development] alexige:
Use control freak found in the cappy theme and apps section, its built for this kernel same kind of control.
[Captivate Android Development] Time_Zone:
So far so good.
[Captivate Android Development] existz:
*fingers crossed*... and god speed my friend

On another note, thanks to stratosk, we now have OC as a module.., just working on implementing it in Talon and modifying it for higher clocks..,
[Captivate Android Development] bigbooty:
No, not the same kind of control.

Control freak is no different than voltage control. Has no sampling freq, or up threshold settings at all. I want to "see" the up threshold and sampling rate settings.
[Captivate Android Development] Xx-Ness-xX:
Trying out .22, I will let you guys know what I find
[Captivate Android Development] alexige:
Oh sorry don't know alot about that stuff. Just thought I heard cf is like setcpu just built for talon guess I was wrong.
[Captivate Android Development] kodos96:
No, although the problem with the dropdown toggle sometimes not working is still there. As before, if you run into it, just enable via settings.
[Captivate Android Development] bigbooty:
Switched back to ondemand, set the SF to 70000, up threshold 95, uv-50 across the board, 1200oc and all is well. Very smooth.
[Captivate Android Development] topiratiko:
So far so good

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] Koizuma:
So far so good on my end too

Swyped from my SGH-I897 using XDA App
[Captivate Android Development] RashaMatt:
Mine is charging to 100%, though because I run Mobile AP all the time, it doesn't normally sleep at all.

____________________________________________________________

AT&T Captivate SGS I897, Dlev ROM 5.0, TalonDEV 0.4.4.22, KC1
[Captivate Android Development] Reynaldinho111:
OndemandX is so much better than before. Talon gets better every day.

sent from my beloved cappy!!
[Captivate Android Development] TheSoaresan:
So far so good..
[Captivate Android Development] fuloplori:
Bluetooth running fine on .22, just made a cpl of calls from my headset. OndemandX is performing quite nicely and after calibrating battery it stays @ 100 after unplug. Running on SensatioN.GJ team :D

Sent from a captivated SensatioN
[Captivate Android Development] CuriousTech:
It was almost full when I started charging, so that was part of it. I just wasn't used to it showing the power status correctly. Once the charge ends, it switches to battery. Now it's really showing it.
[Captivate Android Development] romeovn:
@existz : any chance to make Talon work with I897 version like KH3 ?
[Captivate Android Development] mrhaley30705:
Not until source code is released. Until then, it is very limited as to what he can do. If you want a kernel to use on kh3 other than stock, look at the Atomic Fusion kernel (made by existz), Cog 5 kernel, or the new nuclear fusion kernel.
[Captivate Android Development] cnu4u:
Unbelievable... I am able to see 100% true charge indicator....
[Captivate Android Development] mpencexda:
So what does the Sampling Frequency and the up threshold do for you? Or more to the point what are their functions..
[Captivate Android Development] Kyuta Syuko:
Sweet a new test Kernel. Def will try it out. Will probably flash later today.
[Captivate Android Development] TwinkyOfHope:
Flashed yesterday when i had 63% battery remaining and it charged to 100% over night.

Everything is great so far
[Captivate Android Development] existz:
Sampling rate is how often you want the kernel to look at the CPU usage and to make decisions on scaling up or not, the up_threshold is the % of load the cpu has to be at before it scales up...
[Captivate Android Development] existz:
Ok, so I've got a working module now that when its unloaded (default), everything is same ad stock, 1ghz, then when you load the module (via startup script) it will load the module on boot and set 1.2ghz instead of 1ghz step. There's still a few things that needs to be done before its working 100% correctly, but the hard part is done thanks to stratosk.. But, bad news is, I'm without my captivate for a week or so.. (my g/f has it), so i wont be able to fully test everything myself.. , so it might take me a little longer to get it going .. once this is done, then ill work on making higher clocks.. what i will probably do is create seperate modules for each overclock, so there will be a module for 1.2ghz, 1.3ghz..and so on. Then a script to load whatever step you want, so if you want 1.4ghz, load the 1.4ghz module ..etc. This is long-term talking, i will probably only include the 1.2ghz module for the next few builds, that way everything is tested and stable before i go any higher. ..but there's starting to be light at the end of the tunnel
[Captivate Android Development] mrhaley30705:
Girlfriend? With your captivate? Dude, should have gave her the inspire, we need you and your captivate. :) jk
[Captivate Android Development] melvinaury:
Girlfriend or grandfather. LOL
[Captivate Android Development] existz:
lol, girlfriend
[Captivate Android Development] melvinaury:
Ooooopppsssss
[Captivate Android Development] bigbooty:
Up threshold is the percent of cpu usage at a given speed before it ramps up to the next speed. Sampling freq. is how often the kernel ck's cpu usage. You can increase it by multiples of 35000 which is the stock rate. I've upped mine now to 105000 and still have no lag. The more you can increase it without losing performance improves battery life.
[Captivate Android Development] mpencexda:
so setcpu has the following "Sampling Rate (-1 us--1 us) Note the u is a different character that I am not able to put.. Would I set this to 1 to =35000 and 2 for 7000 and so forth.. ALso should I use Ignore Nice Load (0/1) and Powersave Bias (0-1000) Currently all of these are set to -1 which I assume means disabled.
[Captivate Android Development] Time_Zone:
.22 definitely seems to have fixed the BT bug for me. Thanks for everything Existz...
[Captivate Android Development] existz:
Awesome :), glad its fixed.., and sorry for the earlier bug and all the issues it caused everyone
[Captivate Android Development] bigbooty:
It only shows -1 in ondemandx. You can't change it, the settings won't stick for some reason. Using ondemand, everything is adjustable. Yes leave nice load and powersave set to 0. Switch to ondemand and you will see the kernel defaults. SF=35000, UPFREQ=65, etc.
[Captivate Android Development] existz:
Yea, ondemandX does not support sysfs tuning via SetCPU..etc.., the sysfs file location is different than it normally would be.., so instead of the sysfs files being in /sys/devices/system/cpu/cpu0/cpufreq/ondemandX , they are located in /sys/devices/system/cpu/cpufreq/ondemandX ...which you can manually adjust the sampling rate, up_threshold..etc.. by editing the file, and creating a startup script so it sets on boot if you want. But since apps like SetCPU checks the per-cpu sysfs file location, it doesnt show up for ondemandX
[Captivate Android Development] mpencexda:
sweet thanks.. I will check this out and post a startup script later..
[Captivate Android Development] existz:
I'm getting ready to post bigmem versions of 0.4.4.22 for i9000, ill go ahead and upload ones for captivate also.. give me a few minutes and ill get bigmem up
[Captivate Android Development] mpencexda:
Well they are already set to 80% and 35000

you can use the following to change them at boot though

S_98init_upthreashold_samplingrate (Change to what you want the S## is important though)

echo 70000 > /sys/devices/system/cpu/cpu0/cpufreq/ondemandX/sampling_rate

echo 95 > /sys/devices/system/cpu/cpu0/cpufreq/ondemandX/up_threshold
[Captivate Android Development] existz:
0.4.4.22 bigmem

0.4.4.22 BIGMEM Public Test

BIGMEM versions of 0.4.4.22 added to the original 0.4.4.22 test post

http://xdaforums.com/showpost.php?p=16992230&postcount=4461
[Captivate Android Development] mpencexda:
Installing now.. Will see if it makes any improvements.. Thanks for the great work..
[Captivate Android Development] mpencexda:
Works as advertised so far.. Little bit better in the benchmarks but we know how that goes.. I myself prefer the BIGMEM version but probably all in my head LOL
[Captivate Android Development] mrhaley30705:
@existz

Just saw your sig. You got Talon kernels everywhere. Next thing we know, the iPhone will be Talon powered!
[Captivate Android Development] geokilla:
What are the settings for default and Nexus S in Memory Freak? I tried the different tabs but Swappiness and ZRAM doesn't change. They both stay at 256/90.
[Captivate Android Development] RTBee:
I noticed the same thing. When you talk in your sleep is it Taloneese? :D:D:D
[Captivate Android Development] existz:
:) ...i was going to start with a completely new name but decided to keep talon for the inspire. Since talon represents opensource and collaboration, i decided to stick with it in hopes to expand the team outside of just the SGS.. and bring some of the collaborations that's been done on talon, over to the HTC threads.. Talon started off only for captivate and has grown into what opensource was ment to be, with it being forked off into Zachs snail kernel, an upcoming Vibrant version, the I9000B fork, and all the other 5-6 variants of Talon in the i9000 forum. So hopefully talon can be not limited to only SGS, but for alot of different devices also.. that's my goal anyways.. And kind of break this competition mentality that's out there and quit making it devA versus devB, and instead, have all those devs working on one main project to get the most out of our devices.. I'm proud of talon and its team, its not about trying to make the best kernel out there or competeing against someone , but rather something that benefits everyone and brings all the latest features and fixes to one place
[Captivate Android Development] existz:
Zram and swappiness will stay the same throughout different presets unless you change them yourself...because stock kernels do not use ZRAM and does not have swap support (making swappiness useless), so they are enabled by default and can be adjusted or disabled if desired ..but there's no "stock" settings for ZRAM and basically swappiness (which default it's set to 60 but useless since there's no swap support), so its open to you to adjust it how u want it, but there's no set default "stock" settings for them
[Captivate Android Development] -Thrive-:
You rock man!
[Captivate Android Development] Sqb:
Thank you so much for all the hard work sir. Glad to see the bt bug get squashed so quickly

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] TwinkyOfHope:
. 22 has been running like a champ for me. For memory freak someone suggested using nexus s with ZRAM at 160 and Swapiness at 50, and so far it hasn't been laggy after being on for hours.

The only minor issue I have is that sometimes wifi won't turn on via status bar or the power control widget. But this kernel is AWESOME
[Captivate Android Development] Adame8:
i cant seem to get the ext4 app to work

can someone help or is there another way to do this?
[Captivate Android Development] Sqb:
Ext4 voodoo conversion is done through recovery on this kernel

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] Adame8:
i dont see an option on the recovery
[Captivate Android Development] Adame8:
nvm i got it

thanks
[Captivate Android Development] Sqb:
Go get the voodoo control app in the market. It allows you to control color and sound. Helps a lot on both

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] mystichobo:
So how does the bigmem version work?

I know it breaks 720p recording, but does it have any other negative effects?
[Captivate Android Development] Sqb:
You get 353 instead of 339 nothing bad. Anything worth shooting at high def should be done on an actual video camera. Another plus is it allows you a little more tinkering room with memory freak

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] Kyuta Syuko:
There's an option called voodoo near the bottom of the main menu.

*edit*

nvm I see you got it now...
[Captivate Android Development] henge:
Not sure if anyone else has seen this as well, but since going to 4.4.22 I have been noticing a some what different charge bug. Instead of showing 100% and then dropping when you unplug, it basically gets to 100% and then stops charging (as though it was unplugged.) So you can actually see the battery drop while it is still plugged in, rather than seeing 100% the whole time and then seeing the drop when you unplug.
[Captivate Android Development] pikachu01:
The changes made it so that you can actually see the battery going down (as opposed to the phone lying to you and staying at 100%). Hence, right now rather than unplugging and seeing it drop to x%, you'll get the real battery status. About the discharging while being plugged, that's actually a feature to prevent overcharging.
[Captivate Android Development] mystichobo:
Would be cool if after it reaches a certain threshold (say 80%) it starts charging again though.

It's a pain in the ass if you leave the phone on charge overnight then get to it in the morning and it's siting at 60%.
[Captivate Android Development] watsa:
Thats the famous GB bug, it is supposed to start charging at ~95% which does not happen

The bigger bug is an app that makes your phone drop from 100% to 60% overnight? :confused:
[Captivate Android Development] Aus_Azn:
.4.4.22 finally fixed the "bug" that I had, where my phone would constantly stay awake despite the screen being off. Awesome, because I haven't been able to use any incarnation since .4.4.15.
[Captivate Android Development] murauder:
Just wanted to let you know 4.4.22 bigmem 1200 oc is running on my cappy great. Unplugged this morning and battery said 100%

Best kernel out there for my phone. Thanks for all the work you put in on this and all your other projects

The machines are alive!
[Captivate Android Development] mystichobo:
More of a bad battery issue :P

Got a new one now, and things work a lot better.
[Captivate Android Development] existz:
Yea originally the charge bug was. ..

1) when it topped out at battery full, it would start to discharge, like its ment to, but never kicked back in to start charging again. Which in result, lead to..

2) once it hit 99-100% it would start discharging and not kick back in, for some resulting in it dropping to ~80% ..but while its on the charger it would still show 99-100, then when you unplugged it, it dropped to whatever percentage ..

So, we have fixed half of the bug, instead of it being like it was for #2, now it will not lie about the actual percentage, if it says you have 99%, then you have 99%, ..also it will correctly show the percentage even if it's discharging while on the charger., that's why some of you see it dropping down.. instead of it showing 99-100 all the time..

So now, we are trying to figure issue #1 out.. to get it to start kicking back in once it starts to discharge.
[Captivate Android Development] iXNyNe:
I don't know if this is a kernel issue, rom issue, hardware issue, or just specific to my device, but I have a problem once in a while (right now for example) where my phone can't decide how bright it wants to be with autobrightness on so it switches back and forth between two brightness levels about once every 2 seconds.

I know I'm going to be told to just turn off autobrightness but other than this little issue which happens only sometimes I generally like autobrightness as it does a great job keeping my screen visible when switching from indoor to outdoor lighting.

I think I read somewhere that if I were using captivate software (not reoriented i9000 software) that the brightness level would fade between switching levels and it wouldn't be as noticeable, that true?

Anyway I'm using apex 9.1 and talon 0.4.4.22, if this is the wrong place to ask feel free to correct me