yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] VFO:
Been using 4.4.16 all day now and it is super smooth and stable. I am on the 1200 version and using sio sched. Switching wifi with power management is working fine with no errors thus far. RAM has not been an issue so far and there is no perceived lag when running many apps and multi-tasking. Battery has been excellent today. Really the only issue I have is one I have had with all Talon kernels although I don't believe it to be kernel related and that is the blasted "call settings" that shows up in System Panel after a phone call. It seems that if I forget to kill that process after a phone call it severely drains my battery. The only way I have been able to kill it is using Terminal Emulator. Other than that I really like the way my cappy is working with 4.4.16. Great job and thank you to the development team!

eta: It figures as I type my post a new version is up for testing. Existz, you are amazing man!
[Captivate Android Development] everest.deth:
Ok guys, So i do not know what happened with the previous .16 version lol I tried installing it one more time via CWM, it flashed properly according to CWM but then i was unable to boot anywhere O_O Regular power up would get stuck on the boot screen, and so did any other booting method (Vol up + power, Vol down + Power, Vol up + Vol Down + Power)

I had to go on Odin and flash the previous kernel i had, (default from Apex). That booted up.

Today i noticed that there was a new release though :D So i downloaded, installed via recovery, and now booted up properly o/*
[Captivate Android Development] -Thrive-:
Just installed 4.4.17. I have installed each of the Talon test releases on Continuum 6.1 with no issues to report and incremental improvement at each step. Great job Existz and team!
[Captivate Android Development] agaruba:
Can anyone report average battery life using the 1200 version moderately.
[Captivate Android Development] Sqb:
I use 1200 and I have actually been getting better battery life these last few builds

Edit: sorry never really answered, pretty good battery life but has been getting a lot better. I can get 3 hours screen, music for about an hour, no sync but background on,dozen texts and email,facebook, light browsing and so on

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] mrhaley30705:
Don't think the call settings problem is because of talon. I've had that problem since froyo on several different kernels. The only thing I haven't saw it on is MIUI, but with it messaging does the same thing.
[Captivate Android Development] Time_Zone:
heh looks like my boot loops were from the kc1 modem in apex

Jk4 fixed me right up.
[Captivate Android Development] VFO:
yeah I didn't think it was due to Talon. What an odd thing, it doesn't show up all the time but if I forget to check I do notice the battery loss. Must be a Samsung issue maybe.
[Captivate Android Development] bulawayo:
No problems with .16 either. I'm about to flash .17 too
[Captivate Android Development] tmng95014:
+1 no issue with 17 so far
[Captivate Android Development] manny05:
No problems with. 17 either

Captivate running dlev's latest rom

Talon kernel/snail

Overclocked and undervolt
[Captivate Android Development] Aus_Azn:
I have very aggressive undervolting on my phone (-140mV across the board).

I'm still on .15, and all of the RAM undervolting is still working. No sleep death and not much lag.
[Captivate Android Development] iXNyNe:
17 seems to not have boot loops for me and is running smoothly

i have been able to tether and mobile ap on all versions i've been running btw, so i dont know it the tether issue was affecting only certain people or scenarios (i didnt hear about it until it was mentioned to be fixed)
[Captivate Android Development] RashaMatt:
0.4.4.17 feedback

1) All my widgets had to be recreated after flashing 0.4.4.17 from 0.4.4.15 :( Never seen that before (ADW)

2) Apps/widgets that previously had "Device Administrator" status LOST that status after the flash, and had to be re-granted.

3) [This happened for a while but seems to have stopped] Apps/widgets that lock the screen (see #2) are now disabling NoLock (widget which allows any hardware button to turn on the screen, and disables the Lock screen).

P.S. In 0.4.4.15 I was unable to reproduce the charge bug and the "slide-status-bar-brightness" bug - first time ever! :) Too soon to tell for .17

Looking good!!
[Captivate Android Development] pikachu01:
You might have OC/UV settings that are incorrect. You probably loaded your settings from VC/Pimp My CPU? Existz removed one step (1GHz) in the 1.2GHz kernel, hence you would need to reconfigure the OC/UV settings.

Again, you might have loaded an incorrect OC/UV setting after you flashed. Try manually configuring your OC/UV setting as the CPU now only have 5 steps as opposed to 6 steps.

Probably your phone can't support 1.2GHz?

Also due to your phone not supporting 1.2GHz?

Due to a bad flash I guess.

Not sure what could trigger that as it is app related (probably superuser related)
[Captivate Android Development] Koizuma:
Say If we wanted to keep the undervolt how would one go about re-changing that? would it be as easy as just editing a file like the ram.conf for example or is there a bit more into it then that? my phones been really nice and stable with the UV that im running all around including the ram and ADC voltages too
[Captivate Android Development] existz:
No, you would have to make the changes to the source and recompile the kernel .., but honestly I don't think the UV on ram and adc is making any huge difference, barely noticable if even at all IMO
[Captivate Android Development] pikachu01:
It has to be compiled from the kernel.

https://github.com/existz/linux_gt-i9000-gb/commit/ee4ec35b55110f60e98a5de6d63918fdeddca2a7
[Captivate Android Development] Rrryan2:
0.4.4.17 feedback

Memory leak persists for me on 0.4.4.17, only about 7 hours after flashing . Got up to 315/339MB in use when horrible lag set in. When I go into task manager to clear memory, the phone freezes when and the soft reboots. :/
[Captivate Android Development] pikachu01:
Hmmm, you should enable logcat and figure out the root of this problem. It's not reproducible at my side, hence I would think that some app went rogue in your phone and consumed memory till there's not much left.

Upload the log here when you get the soft reboot. It should be able to tell us what causes the leak and the soft reboot.
[Captivate Android Development] manny05:
Weird.. An hr ago I wasn't able to turn on my screen... Had to press the power button like 5 times to turn it on at the lock Screen. Never had that happened.. It didn't happen again though

Captivate running dlev's latest rom

Talon kernel/snail

Overclocked and undervolt
[Captivate Android Development] RashaMatt:
Unplugged at 100%, dropped to 70%...

Charge bug still present in .17 :(

_________________________________________

AT&T Captivate, Serendipity VII b1, TalonDEV 0.4.4.17, KC1
[Captivate Android Development] -Thrive-:
Yes the charge bug is still there but a workaround that works for me 100% of the time is, after the phone is fully charged while powered off, power on and boot while still plugged into the wall charger. Gives me 100% battery most of the time and never lower than 99%.
[Captivate Android Development] johan8:
I also have the similar issue.

In .15 , .16 , memory looks low in the first 10hrs of using.

After a day, memory used will raise to 260-290MB.

Now over 30hrs without switch off, memory used become 290~300MB.

However, I think nothing can help with that.

For all those Android phone with GB, the standby occupied memory are nearly up to 300-400MB.

GalaxyS just have 340MB in total, it is become the end of the road.

I think this is bug of samsung rom, of maybe the kernel.

long ago, i9000 i897 still have this problem.

Talon is based on samsung kernel source, so the bug is still there,

unless somebody take a deep look into the source and rewrite everything....
[Captivate Android Development] tmng95014:
I have never seen this. Left phone on charger since yesterday afternoon and full when detached today. Could it be hardware issue?
[Captivate Android Development] Peaster111:
You never know, but I don't think so. Mine drops to the upper 80's after disconnecting. I've never tried the suggestion from -thrive- though.

As an interesting note... When I played with Darkcore 3.0, I didn't see the "charge bug".
[Captivate Android Development] existz:
OndemandX Governor

ADDON - OndemandX CPU Governor Update v1.2

So instead of putting out a whole new update with OndemandX governor, Ive compiled it as a module and made it CWM flashable.

Just flash with CWM, then select it via Voltage Control, SetCPU..etc.. The module will load on every boot..This is only to test the

new governor.., if all is good then it will probably be added in the next test

Some info about OndemandX

- includes sleep code (better battery life)

- threshold set to 95

The sysfs files are not located in the normal /sys/devices/system/cpu/cpu0/ondemandx/, but rather in /sys/devices/system/cpu/ondemandx/

so programs like SetCPU..etc.., will not be able to adjust sampling rate, up threshold..etc.., but you can manually edit the values by echoing to the file

or by setting it in the /etc/init.d/s10ondemandx startup script

Files are located in .. /sys/devices/system/cpu/cpufreq/ondemandX

UPDATED - v1.2

- renamed startup script so it can be saved as boot settings and is actually set on reboot

UPDATED - v1.3

- fixed suspend frequency
[Captivate Android Development] alexige:
Would you say OnDemandX is best for battery life then?
[Captivate Android Development] zacharias.maladroit:
well, that governor should be sleep-aware :)

we'll see what the experience shows

there are also a bunch of other governors scary, smartass2, brazilianwax, etc.

to name a few

not sure which of them is the best one for our needs
[Captivate Android Development] existz:
Thats the whole point.., it should be... It includes sleep code and threshold is set to 95 (regular ondemand is set to 65), meaning that it does not scale up until there is 95% load.., instead of 65%
[Captivate Android Development] existz:
Updated OndemandX again.., sorry for all the updates so quickly.., had overlooked something and now fixed it..

v1.3

http://xdaforums.com/showpost.php?p=16648522&postcount=3926
[Captivate Android Development] ou812bkewl:
This kernel has broken some of my video codecs ever since 0.1.2. Even now, on Apex 9.1, most videos encoded in Divx3 will play fine with the included dark core, but I only get audio with talon. I was just wanting to see if anyone else has had video playback issues and if anyone knows why. Otherwise, this is the best kernel in here in my opinion.
[Captivate Android Development] eliminat:
Wow, Definitely seeing more time at other steps other than the top and bottom.
[Captivate Android Development] eliminat:
I play video on my phone everyday at work. Haven't had any problems with video since one of the 0.3.x's.
[Captivate Android Development] RichMD:
Great video clip in Zacharia's signature

@Zacharias - I just saw the video clip in your sig for the first time - that's one of the best I've seen... :D
[Captivate Android Development] RichMD:
I am running Apex 9.1 and left the stock Darkcore 3.0. I had the phone charging via USB/PC - it showed 100% until I disconnected and it dropped to 80%. I don't know about others but charging via USB on the computer is where I am WAY more likely to see the charge bug compared to the wall charger that comes with the phone...
[Captivate Android Development] tmng95014:
I charge via USB on computer and never see charge bug.
[Captivate Android Development] irishvandal:
I had the charge bug on DC2.9 and I trained the batt one time. Only took two power up/down cycles with a stat clear and I reach 99-can% every time I do full charges. And I don't drop to zero if I can help it, and don't always do a 100% charge. But I get my 18-24hr charge cycles when I roll all day.

It also helped doing the same under Talon. Btw existz, I miss Talon buddy, just can't roll beta right now. Can't wait though. Can't stand 1000mhz. No one can feel the extra 200mhz my foot. Lol. Keep up the hard work buddy, I am waiting in the shadows. Lol.

Sent from a state of Delusion....
[Captivate Android Development] Peaster111:
I would tend to agree... "training" is probably the best thing to do. I'm sure we all know similar stories on every kernel... :)
[Captivate Android Development] carey:
Just flashed .17

No 3G?

I came, I saw... I left confused
[Captivate Android Development] existz:
Huh? yea theres 3G
[Captivate Android Development] H3llstorm:
Is the preferred I/O Scheduler still SIO (in terms of stability/performance)?

Here's some test results suggesting NOOP might be preferable - http://xdaforums.com/showthread.php?p=16006776#post16006776
[Captivate Android Development] carey:
Well all I did was flash .17 and have had nothing but edge ever since

Edit: Never mind. Rebooted and it is back to normal.

I came, I saw... I left confused
[Captivate Android Development] iXNyNe:
I don't even think talon has sio, I've just been using ondemand until ondemandX was released.
[Captivate Android Development] existz:
Yea, SIO, VR and BFQv2 are all additional IO schedulers..., Ondemand and OndemandX are cpu governors..

But to answer the question, either SIO/VR or BFQ are good choices
[Captivate Android Development] Johnsondr80:
@existz

Never got back to me on any of my pm's

Is this a hint to me or have you just overlooked me.

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] pikachu01:
You can ping him in the IRC if he's not available in the PMs :)

webchat.freenode.net #suckerpunch
[Captivate Android Development] topiratiko:
OndemandX feels excellent thus far. No noticable drop in performance and usage looks alot better in cpu spy....original on demand looked more like interactive/performance

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] Koizuma:
So far loving the new governor works like a charm so far and .17 is smooth as can be.

Swyped from my SGH-I897 using XDA App
[Captivate Android Development] existz:
So next release ill include both ondemand and ondemandX, if you want performance go with ondemand (threshold=65), if you want battery life then ondemandX (threshold=95)...

@johnsondr80

My bad, must have gotten buried in my inbox.., ill get back to you on that
[Captivate Android Development] cuticuti:
Auto brightness seems a bit slow:(
[Captivate Android Development] apparition:
I still have the memory leak issue on .17 after about 10h of light usage. Still, Talon gives me the most stability on TW4.5. strange bug....
[Captivate Android Development] Time_Zone:
I have reboot issues. .15 .16 .17 on apex 9.1 Here are all the logs I can find. I can't make anything of them personally.
[Captivate Android Development] Xx-Ness-xX:
Someone has made a post about this charge "bug" per se, it's very informative. This happens pretty much to all Android phones...

http://xdaforums.com/showthread.php?t=871051
[Captivate Android Development] sinichi21:
+ 1 on this i cant remember where it start but seems to me the the auto brightness is confuse when to bright and when to dim not sure if its a kernel problem or rom though.
[Captivate Android Development] Rrryan2:
+2. Auto-bright in .17 seems a little off its mark to me too, something I hadn't quite noticed on recent Talon evolutions. I know that for quite some time eXistz's bias (dating back at least to early Suckerpunch builds, back when it was all about UV and only tangentially about OC and other goodies...) has been in favor of battery life over screen brightness, but recent Talon versions had seemed much more palatable to me.

I'm admittedly one of those weirdos who's mostly pleased to leave auto-brightness to do its thing. I figure there's little point in having a device with a great display if the display performance is constantly undermined in singular pursuit of battery life, and if I have to adjust it manually then something's probably amiss somewhere. 0.4.4.17 in particular though seems not just biased in favor of battery life but also slow to react to down-power the display when faced with low light conditions. I've found myself thinking the display is too bright and overpowered almost as often as underpowered, making me wonder if there's not something up with the light sensor.

Otherwise I'm pretty happy with .17 and OndemandX thus far. I'm still having memory leak issues at about 10-15 hours of runtime, but am somewhat resigned to just reboot and considering just setting Tasker to reboot the phone every so often to mitigate. So far seems to solve the problem definitively, if perhaps somewhat inelegantly.
[Captivate Android Development] mystichobo:
Dammit existz,

I liked it better on my old phone, with it's locked bootloader, now I'm stuck religiously flashing your kernel with every update :P
[Captivate Android Development] artvandalay22222:
Ok, this is not a big deal, but I was hoping someone smarter than me knows how to fix this. I was running continuum 6.1 and I flashed to talon4.3 from 2.1(yes this was a while ago) ever since then my boot animation plays the samsung one despite changing boot animations. I've flashed several versions of talon and flashed to continuum 6.2.1 and still no luck.

Its my understanding that you replace the"sanim.zip" in the system/media folder. should I try flashing a different rom? Or bootloaders?

Or is it something simple I overlooked?
[Captivate Android Development] shane87:
Have you rebooted againg after the flash? When you first flash talon, it wipes cache, dalvik-cache, and voltage settings. There is an issue with displaying custom bootanimations while the kernel is rebuilding the dalvik-cache, so talon uses the samsung bootanimation. If you reboot again AFTER the phone boots all the way up, it SHOULD show the continuum bootanimation.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] IDoMy0wnRacing:
If you are trying to use a custom sanim.zip, and you allowed compression when zipping it WONT work. When making a custom bootanimation (sanim.zip) you must use the "store" instead of a "normal" or "fast", etc... compression.
[Captivate Android Development] iXNyNe:
So ondemandX with a threshold set to 65 is basically the same as regular ondemand, but it would sleep better?

Another question;

It was mentioned that setcpu cannot change threshold and some other settings for ondemandX because it uses a different file location for sysfs. Can the governor be modified so that the file location it uses is the standard one setcpu looks for?
[Captivate Android Development] alexige:
Use control freak in the theme and apps section here, it was built and still being developed to be like setcpu but exclusively for the cappy.
[Captivate Android Development] topiratiko:
+12345678910 the autobrightness has gone berserk! Revert! Revert! lol

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] existz:
Well, basically...but there's still some small differences...for example..there were some changes to ondemand to refractory frequency increase code which removed applying sampling down factor when increasing cpu..with ondemandx its still there..so its not exactly the same, but close.

As for changing sysfs location, its not as easy as just changing a file location, the ondemand we use, and what most apps are setup to use is the percpu sysfs, with ondemandx it does not use this..the percpu ondemand sysfs is actually depreciated in newer source, so that whole code for the layout would have to be added back ..at which I'm not sure if that will even work. The info for ondemandx in the Kconfig says it does not support sysfs, so I'm not sure if it was just removed for that reason alone and the tuneables in /sys/devices/system/cpu/cpufreq/.., do nothing , or if they just noted that because it does not use the old method, which most android devices use. But ill look into it. For now though ill leave ondemand at 65, if you performance use it ...and ondemandx at 95, if you want battery life use it.
[Captivate Android Development] -Thrive-:
Great to have this option! I installed demandx immediately and have to say I see no perceptible impact on performance. On the other hand, even a small improvement in battery life is welcome. Monitoring battery throughout the day and so far seems to be helping. Thx!
[Captivate Android Development] topiratiko:
+1 drains noticebly slower when in use

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] ThatJawn:
So having this one issues. Sometimes when I go to lock the phone. All it does is bring down my drag down top bar from up top then my soft keys don't work. Tried reflashing, etc etc. Just a bit annoying.

If anyone has anyideas let me know.
[Captivate Android Development] eliminat:
I'm loving the OnDemand-X Gov, but when listening to music it will still switch to deep sleep and stop playing until I hit the power button quick to wake it up. OnDemand didn't do this. Using WinAmp.
[Captivate Android Development] Josh K.:
existz,

On the official Samsung Rom's the screen stays awake when in the "Samsung Car Dock", is there any way to get this working with all non Official Rom's?

Thanks,

Josh-
[Captivate Android Development] RTBee:
Check out settings_

_Applications

_Development

check 'stay awake'

I think that should work for you. It works in the Samsung Home dock. :)
[Captivate Android Development] existz:
0.4.4.18 Public Test

0.4.4.18

Changelog since 0.4.4.17

- added hardfloat optimization flags

- a few ARM/S5P/SAMSUNG upstream fixes

- introduce OndemandX CPU governor (use for best battery life)

- updated to Linaro 4.5 (GCC 4.5.4) 2011.07 toolchains (from 2011.06)
[Captivate Android Development] tmng95014:
Goodies! Flashed and running now.
[Captivate Android Development] LNJ:
New build seems to have fixed the lock up and reboots in Sensation when using stock browser.

Thanks Ex!
[Captivate Android Development] oriveradel:
First time a new flash comes out and I am on 100% charge! running already... will check and report later..
[Captivate Android Development] existz:
Just wanted to give you guys a little update on MemoryFreak, currently running a beta version which i hope will make it in the next test/release of Talon.., so far theres Stock, Nexus S and Talon default settings...with Talon settings you will have the option to adjust HIDDEN APP MEM SIZE (28MB to 52MB, lower = more aggressive settings, higher = more multitasking, more app stored in memory), then with all presets you will be able to adjust ZRAM_SIZE (0-256, 0=disabled), and swappiness size.., Hopefully this will elimnate everyones LMK issues, giving you some control over having more aggressive settings or multitasking settings, while being able to take full advantage of all the features in Talon..
[Captivate Android Development] alexige:
Hopefully a tutorial section on what to do and the conciquences per say.
[Captivate Android Development] existz:
Theres a help/tip button which briefly explains what each setting does, nothing too complicated..should be easy for users to use
[Captivate Android Development] existz:
Ok, i found a bug thats actually preventing UV from actually being applied, it still shows in VC..etc.., that its set.., but actually its not.. This could be the reason for reboots/instability for some of you.. you can check /sys/devices/system/cpu/cpu0/cpufreq/frequency_voltage_table ..., middle numbers are stock voltage and the numbers on the right are current voltages.., as you can see they are the same no matter what UV settings are... I will put a build up with this fixed in the morning. Sorry for this one guys, took me awhile to figure out that its not actually setting...update in the morning
[Captivate Android Development] H3llstorm:
I'm still getting skips when playing music using 0.4.4.17. Is there a fix in the works?
[Captivate Android Development] pikachu01:
What scheduler are you using?
[Captivate Android Development] H3llstorm:
SIO. Would NOOP, VR or BFQ be better choices?