yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Holmes108:
Just checked out System Panel. It's very good at closing running apps.

I'm generally at about 240MB used when I boot up. A quick check in System Panel shows all kinds of apps running (that I hadn't opened during that boot), such as Firefox, daily briefing, amazon app store, netflix, supermanager, pulse, etc..

I closed all active apps in System Panel, and it put me to 145 used... which was fantastic (i'm NEVER below 200). I did that at 3:00 sharp. I shut off the screen and didn't touch my phone until now (3:40). I'm sitting at 210MB used. That's crazy. Checking the running apps in system panel again, I see Pulse is back, and Facebook suddenly showed up (I realize facebook does stuff in the background, so that's fine.)

None of the apps that were originally there, outside of Pulse, came back. So I'm not positive which processes are new. There were too many to keep track of off the top of my head. I may have to reboot and actually write every one down.

I might have to use Autostarts or something to stop things like Gmail and Maps from starting.
[Captivate Android Development] tmng95014:
+1 I don't know why people would want to tweak things so low at this level and then report problem for kernel developer to support. I worked in OS kernel also and know the issue of reproducing the problems. If the problem is intermittent like we have seen compounded by memory leak etc. Why introduce even more variables? Are we just happy with a stable firmware?
[Captivate Android Development] topiratiko:
Understood. I DO have one more question though. lmk Adj levels are 1,2,3,7,15...but at the top there are a few fours and NO 7's..in this regard should i change anything??? Just trying to understand this a little more
[Captivate Android Development] geokilla:
I can duplicate it as many times as you wish, even if it's a fresh ROM flash. Haven't gone back to stock Gingerbread, but yea, nothing holds in the RAM. I don't have many services running either. Only 14 services, and they are the pretty much the same services as when I was running FireFly + SuckerPunch. The current services are:

Settings

Voodoo Control

Tap Tap 4 (never play it lol)

Skype (never use it lol)

Fancy Widget Pro

DRM content

Software update

SNS (always restarting)

Google Services

Maps

Email

NoLED

Aquarium

Swype

Btw, people need to stop double and triple posting. Use multi-quote or multi-quote manually if you're not posting on your phone.
[Captivate Android Development] existz:
Im looking at releasing 0.4.2 tomorrow, will only be non-oc and 1.2ghz versions, but you can use tegrak oc app if you want higher. This is only temporary, until we can get our own oc module created, then you will be able to load the module and oc up to 1.4ghz or whatever we set it at . Most likely have it up around mid-day tomorrow

Sent from my SGH-I897
[Captivate Android Development] topiratiko:
Good stuff Existz

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] cnigro1279:
Nice...

Looking forward to giving this a whirl....

Thanks for all your hard work!!
[Captivate Android Development] topiratiko:
Antsy

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] topiratiko:
Does it include modified lmk settings?

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] topiratiko:
We want 4.2! we want 4.2! we want 4.2! LOL

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] tylercarter:
Good things come to those who wait.
[Captivate Android Development] existz:
yes, way better than 0.4.1
[Captivate Android Development] topiratiko:
Awesome!

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] existz:
UPDATE

TalonDEV-0.4.2

update to 2.6.35.13 (still shows 2.6.35.7)

added BFQv2-r1 I/O Scheduler (SIO default)

fully ported mDNIe driver from nexus

tweaked mDNIe UI settings similar to speedmod

fix colour multiplier to avoid yellow tint

tweaked lowmemorykiller driver

revert lmk settings similar to old #7

added boot progress bar during boot

arm: Allow CPU-supported unaligned accesses

add support for BT_PAN, Apple Magic Mouse + more

fix .int_volt on higher frequencies (thnx Cy4n1d3)

set kernel log buffer size to 4kb (from 128kb)

ashmem: fix deadlock when system is low on memory

compiled with 4.5.1 toolchains (RIL with 4.4.3)

removed unused governors; conservative now module

UV for LCD 3.0v->2.6v, RAM 1.8v-1.6v, ADC 3.3v->3.0v

some PM and battery runtime upstream fixes

NOTE

Use Tegrak Overclock app if you want to OC higher than 1.2ghz, this is only temporary...Also, kernel base is updated to 2.6.35.13 but will still show 2.6.35.7 so samsungs precompiled modules and voodoo control plus works correctly, but it is updated
[Captivate Android Development] sstarre:
Looks Good so far ! :)
[Captivate Android Development] mrhaley30705:
Same as t8?
[Captivate Android Development] melvinaury:
Working Fine.
[Captivate Android Development] topiratiko:
Um. Is bfq the brain **** scheduler i read about in the vibrant threads?

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] mrhaley30705:
I tried using Tegrak to test uv, and the free version won't let. It days you have to buy it. Will control freak still handle uv even if someone uses tegrak to oc?
[Captivate Android Development] sstarre:
@existz...

I now you put a ton of work in this, but I have to say the progress bar is a MASTERSTROKE ! :D
[Captivate Android Development] pikachu01:
UV and OC are in completely different files. One is in cpufreq file and another in Volt_scheduler (name?)

I would think that it's safe to use tegrak as well as UV programs such as CF or Pimp My CPU. However, tweaks must be mutually exclusive I think.

My take is that you should first UV then only OC.
[Captivate Android Development] existz:
No, BFQ is an I/O scheduler, BFS is a cpu scheduler

Yes, you can use Voltage Control, Control Freak..etc to UV when using Tegrak OC...Tegrak app just replaces the highest frequency with whatever OC u choose..tegraks free app wont let you uv unless u buy paid version, but since the kernel supports UV, using VC/CF will work still

Sent from my SGH-I897
[Captivate Android Development] topiratiko:
O ok. LOL

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] mrhaley30705:
I don't usually uv and I run the 1200mhz bigmem all the time, so it doesn't matter to me. But I do know a lot of people uv and run higher oc than me.I guess I'm asking for them.
[Captivate Android Development] cnigro1279:
Wow...

Impressive changelog my friend....

D/L now.....

Looks brilliant!!!
[Captivate Android Development] existz:
Also want to note, and ill add it to the OP, I forgot and left it out...if you want to use conservative governor (which I do NOT recommend), it is now a module so you will have to load it in order to use it. Once you load the module, you can use whatever program to select it (SetCPU, VC, CF...), ill put an init.d script up for those that want it loaded on every boot later today...but simply type this in a terminal emulator or adb shell ...

Su

insmod /lib/modules/cpufreq_conservative.ko

Sent from my SGH-I897
[Captivate Android Development] existz:
Gotcha, but yea u can still use Voltage Control, Control Freak etc to UV even though Tegraks app wont let you with free version since the kernel itself actually supports UV

Sent from my SGH-I897
[Captivate Android Development] mrhaley30705:
You think Talon is about ready for v1.0, or is your wish list for it much bigger than we can imagine?
[Captivate Android Development] existz:
its getting close... but still got a few things up my sleeve i want to do before making it a v1.0 release :P
[Captivate Android Development] mrhaley30705:
If you could figure out to make it empty the dishwasher, my wife would appreciate it :)
[Captivate Android Development] kodos96:
Well I don't really know what to tell you, because what you're describing is basically the opposite of what everyone else is complaining about - that Talon keeps TOO MANY apps in memory, doesn't kill them quick enough.

If you start a bunch of small apps, then check task manager, do you still see them running? What apps are you seeing getting killed? And are you sure they're actually getting killed?
[Captivate Android Development] cnigro1279:
Or...

Mow my lawn maybe??

Seriously, Onix was, imho, the best froyo kernel developed and this has all the makings to blow it out of the water.
[Captivate Android Development] existz:
Mirrors are up, but please make sure to visit http://talon.darkirc.info and click the ads! We get a few $$ on ad clicks :P

Mirrors: http://berryfx.com/RobBeane/Kernel/i897/Talon/
[Captivate Android Development] pizz0wn3d:
Woop woop! Thanks :P

Ad Clicks Inc :P

-Herp derp Captivate XDA app
[Captivate Android Development] mrhaley30705:
Why does it take so long to dl from the darkirc site, but the mirror is flying.
[Captivate Android Development] Thegodfather156:
the amount of people downloading the file slows the bandwith down.
[Captivate Android Development] oriveradel:
Beautiful, screen colors are are perfect now, quadrant score when up 200 points win no OC, with OC 1200 I get 2600! wow I love it! Thank you very much sir, you are a Genius!
[Captivate Android Development] yobbei:
Sorry newbie question can I use this with JVP based rom Mosaic V?
[Captivate Android Development] XblackdemonX:
Awesome job on the kernel. I love it

Quadrant score: 3451 @ 1.467mhz :D
[Captivate Android Development] Sqb:
Top notch work from a top notch developer. Thank you for all the countless hours invested into this project. The smoothness and pure polish and power puts this above the rest!

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] topiratiko:
There was a time when i stayed away from talon....thats long gone. I tired dark core and that lasted about 7 minutes. Talon IS the best kernel for ginger on our devices...jvp voodoo is the next best :D On another note...ive caught some heat lately about my insane lmk settings....been looking in to this some more..and existz or kodos...what do you think about the settings below? I am giving the stock 4.2 settings a shot first but from what im reading these seem pretty good...i just want a more knowledgeable opinion because im not QUITE there yet lol

http://xdaforums.com/showthread.php?t=1111145&highlight=Serendipity
[Captivate Android Development] KayvinM:
yes you can
[Captivate Android Development] Thegodfather156:
simple answer.....yes
[Captivate Android Development] melvinaury:
In the first page it was indicated that it will work.
[Captivate Android Development] existz:
Im still running Apex JVP and works fine
[Captivate Android Development] topiratiko:
Existz can i ask why you prefer jvp? is it because of the stock browser?

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] existz:
Just been to lazy to update
[Captivate Android Development] harpo1:
I'd say more like to busy.
[Captivate Android Development] topiratiko:
Kernel is great thus far....smoothness is unparalleled.

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] mrhaley30705:
No one ever said if this was the same as 0.4.2.8. Just wondering if theres a need to flash the release.
[Captivate Android Development] topiratiko:
Eh. Just do it. For the flash of it. Lol

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] tmng95014:
(1) not many people has this test release.

(2) If you want support, it is best just to go with the version everyone use.

As stated, just flash the damn release.
[Captivate Android Development] kodos96:
Well if you take LMK settings from another kernel or ram script like Juwe11's and use them on Talon, they're not actually going to end up working exactly the same way as they did on the other kernel, since I've redefined some of the mappings between app classes and adj levels, so those 6 mem threshold levels don't actually mean exactly the same thing on talon as they do on other kernels... I know its confusing, I don't know how to explain it better without going into a whole lot of technical detail, but the bottom line is that a set of values that may work well on another kernel may not work well on Talon.

If your goal is just to have your apps killed quicker, you should probably just start with Talon's default settings, and increase the value for HIDDEN_APP_MEM (and the corresponding value in LMK_MINFREE)... and if you end up increasing it to the point that it's higher than EMPTY_APP_MEM, then also increase EMPTY_APP_MEM just so that it's higher than HIDDEN_APP_MEM.

You probably shouldn't mess with any of the other values. If you really want to, you can try raising the threshold on the next level as well (the ones that are all set to 5120 in my default config), but you want to be really conservative with that one - you don't want to increase it by more than a couple mb, or you'll end up in the situation where your services are always getting killed and restarted.
[Captivate Android Development] topiratiko:
Thank you. Im actually starting to grasp this stuff.

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] manny05:
Just updated and its looking good so far
[Captivate Android Development] IDoMy0wnRacing:
Thanks eXistZ, I always look forward to your updates...:D
[Captivate Android Development] Pf.ozer:
can i use the 0.4.2 kernel on a jvp based rom?
[Captivate Android Development] bryman27:
yes, existz is actually running a jvp rom
[Captivate Android Development] existz:
If anyone experiences reboots during phone calls, the problem is aware of and working on fixing it. Its possible its due to 2010/2011 toolchains, getting ready to put a test out with 2009q3 again and see if it fixes it. Some have reported it only happens at low battery level, ~30%...for me it only happens when around 5% or below, so it varies... This issue seems to only be related to phone call reboots, not causing reboots during any other situations, so make sure its not because of OC/UV instabilites before posting please.
[Captivate Android Development] Sqb:
Haven't had one yet but thanks for the heads up. Support here is unbelievable.

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] offwiththeface:
Hey guys do I have yo dissable voodoo lagfix before flashing this Kernal? Thanks
[Captivate Android Development] zacharias.maladroit:
nope, it should work

(I myself have updated/tested from DarkCore with lagfix enabled to Talon)
[Captivate Android Development] zerkai:
That would explain what happened to me last night. My battery definitely got to red during the call.Though, it's a bit rare for me to use the phone on low battery without being plugged in.
[Captivate Android Development] golfslicer:
Will this work on KF1 gingerbread.
[Captivate Android Development] existz:
No, only for i9000 2.3.4 gingerbread

Sent from my SGH-I897
[Captivate Android Development] golfslicer:
Bummer
[Captivate Android Development] mrhaley30705:
Will any of your gb kernels work with kf1? And are you planning on making one?
[Captivate Android Development] manny05:
i can also confirm i had a random reboot after i ended a phone call..

battery was at 15%... i did make phone calls earlier before it reached 60% and nothing. so im assuming this only happens below 20% but im not too sure..its deff going to be a problem lol especially since i work as a taxi and i make phone calls all day... im just gonna go back to the last update until there is a new version. great job though
[Captivate Android Development] shoman94:
He has one.... it will be released with Solstice. Cezar's upcoming KF1 ROM.

:)
[Captivate Android Development] existz:
No, will not work with KF1. There's really not much that can be done without sources. However I did do a kernel for Atomic Fusion and also one for Cezar when he does a KF1 version. Its nothing fancy, again..not much that can be done

Yea, seems to only happen around lower battery levels...been working on it some and believe its due to newer toolchains. Zach put out a new 'Snail' kernel based on latest Talon with older toolchains, so it should fix the problem if thats what's causing it.

Sent from my SGH-I897
[Captivate Android Development] mrhaley30705:
I know I can't wait for that.
[Captivate Android Development] RashaMatt:
FWIW after a day's use, the "lag issue" I've seen on all the GB kernels seems MUCH improved in 0.4.2 over 0.4.1. Not quite perfect yet, but definitely a huge improvement. This is the first GB kernel I've used that is actually "acceptable" to me, and I was running 0.4.1 at 1400.

Btw 1500 was stable for me and it would be a shame to see it be an option. I chose not to run at 1500 because if the phone were to get stuck in a full-cpu usage state, it would have overheated very quickly. 1400 is bad enough, lol. I think I would choose 1300 as my default, though it's always nice to have options.

(Serendipity VII)
[Captivate Android Development] LNJ:
So I had a lock up happen while on a Flickr page. None of the buttons would work either. Then all of a sudden it automatically rebooted.

It's happened to me on different versions and normally on pages with lots of high resolution images.

I think it may be that the browser takes up all free memory causing the lock up since it only happens with pages with high resolution images for me.

Samsung Galaxy S i896 on Cezar's Continuum v5 GingerBread
[Captivate Android Development] Reynaldinho111:
I had the same thing happen but it was as i brought up my keyboard in the stock messaging app. Im on apex 8.2 could be my oc/uv settings but i dont think so. Not really a problem for me but i thought id mention it. Aside from that, 0.4.2 has run beautifully.

sent from my beloved cappy!!
[Captivate Android Development] pikachu01:
Lag when accessing keyboard is always there at every kernel (using swype 3.0). My take is that Swype being beta is still not yet as optimized as the keyboards out there like SwiftKey.
[Captivate Android Development] Reynaldinho111:
Im aware of that. But random reboots when accessing they keyboard is very different from lag.

sent from my beloved cappy!!
[Captivate Android Development] pikachu01:
Ah, misread your post. Does it happen everytime or once in awhile? Try not UVing if it happens every time.
[Captivate Android Development] iRide113:
Seemed to fix for me when I used this.
[Captivate Android Development] Reynaldinho111:
It only happened once and im not particularly worried about it, just thought i'd post my feedback.

sent from my beloved cappy!!
[Captivate Android Development] bluerogue85:
when it says 352MB versions break 720p video recording on the kernel versions and stuff whats it mean breaks 720p video recording? like theres no 720p/hi def recording or what? cause i couldve sworn i used it before with that kernel version..or maybe not the 1280x720 option? thanks for your answers..
[Captivate Android Development] nybmx:
Yup exactly that.
[Captivate Android Development] shane87:
I have not had a random reboot with 0.4.2 yet, but with 0.4.1 I did see occasional reboots, mainly durring low battery phone calls, although I did see one or two while playing games. They all happended when my battery was low. The entire screen would go black, but the haptic buttons would stay lit. No button would work. Then after about 30 seconds, the phone would vibrate, then reboot.

I have yet to see one on 0.4.2, but I have also yet to use 0.4.2 below 22% battery, which is what I am at now. If I see one on 0.4.2, I will let you know.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] H3llstorm:
TalonDEV 0.4.2 gave me boot loops, back on TalonDEV 0.4.1.
[Captivate Android Development] Rhiannon224:
Sounds like a bad flash. What Rom are you on?
[Captivate Android Development] H3llstorm:
I'm running Dlev's v3.9 [JVQ] ROM.

I flashed 0.4.2, went into a boot loop, pulled the battery, went into recovery, flashed 0.4.1, and didn't go into a boot loop. :cool:
[Captivate Android Development] existz:
Try reflashing

Sent from my SGH-I897
[Captivate Android Development] Barsky:
Hmm. don't recall a progress bar on the Talon load screen in past versions. NICE
[Captivate Android Development] tylercarter:
Any news on the toolchain fix? I'm getting flash happy! :)
[Captivate Android Development] existz:
Still working on some things, but zacharias.maladroit has a new snail kernel out built off latest talon with 2009 toolchains.
[Captivate Android Development] zacharias.maladroit:
++

"welcome reboot syndrome" :rolleyes:

just flash again (I got reports from my cm7 kernel for those, too and experienced those myself in the past)
[Captivate Android Development] dtlove74:
Not that big of a deal, but just went from 4.1 to 4.2, and all widgets now are white boxes with the words "Problem loading widget". I'm using Go Launcher Ex, and the widgets are fine in the other launchers. Plus, when I re-add them in Go Launcher, that works too.
[Captivate Android Development] manny05:
Where could we find this?
[Captivate Android Development] mcx6:
I believe this is what kernel he is referring too:

Link: http://xdaforums.com/showthread.php?t=1148614
[Captivate Android Development] existz:
But note that zach still uses a precompiled modem driver even though hes using 2009, which can make results vary.. Im still trying to narrow it down, but as of right now running 2009q3 with it compiled normally (no precompiled driver) and have not had any reboots,...getting ready to put a test up for my testers and see how it goes.
[Captivate Android Development] mrhaley30705:
Any chance that will also fix wifi reboots?
[Captivate Android Development] existz:
No, the wifi reboot issue is a Samsung issue..seems to happen alot with either dropdown menu or power widget, doesnt seem to happen as often when enabling/disabling in Settings menu...I have no clue where to start on this...who knows, it could be a framework/rom issue..or it could be from where we are still using JVB sources, this issue started with JVH i believe, so its very possible its just from not having updated sources...kind of like the autobrightness issue
[Captivate Android Development] mrhaley30705:
Well, just hoping...
[Captivate Android Development] Sqb:
I seemed to have stopped having the wifi reboot except for enabling airplane mode then trying to enable wifi only (so I can browse and what not without interruption)

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] H3llstorm:
I'm fine with 0.4.1 until your next release comes out.

I'm also available for testing. :cool:
[Captivate Android Development] topiratiko:
If you leave wifi on and reboot...itll boot loop a few times....if its off its fine.

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] shane87:
I have not seen any wifi related bootloops yet, but I have not rebooted with wifi enabled either. I have seen one reboot after call w/<20% battery left. I thought I had experienced an after call reboot at about 80% battery. The screen stayed black, haptic lit, no buttons worked. Then I put the phone back to my face, pulled it back, and the screen came back on and did not reboot.

That makes me wonder if the after call reboot is related to an issue with the proximity sensor driver. Maybe the 2010 & 2011 toolchains mucked up the prox sensor driver, and at low battery levels it is causing reboots. No solid proof, just an idea to look into.

Ex, kodos, zacharias and ytt3r, you all are the best devs for the cappy!! Keep up the good work!

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] mrhaley30705:
I've not saw this.