yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] Rahulrulez:
Does anybody have BLN Libs and services.jar for JVQ? I need it to integrate in my ROM
[Captivate Android Development] toy028:
4.3 kernel has been the best for me yet. No shutdowns and very little lag, almost none after several days of up time.
[Captivate Android Development] tege989:
Well when I originally did that it was telling me that the flash had failed, but I re-downloaded and tried again and it worked. Thanks!

The reason I was going to update the Kernel is because the Samsung Home launcher on Continuum 6.1 keeps force closing on me. I thought it may have been the kernel but it's still doing it after I updated the kernel. Possible bad flash? Guess I'll head over to the Continuum thread and see if anyone else is having this issue but I didn't see anyone talking about when I checked earlier today.
[Captivate Android Development] lospulpo:
Kernel's killin it. Always works great for me. Thanks
[Captivate Android Development] zacharias.maladroit:
I've tons of additional patches & fixes to commit

but right now don't have much time

so I have to figure out which on of those might kind of fix & improve memory handling

stop *****ing around !

talk is cheap - so where are the patches ? :rolleyes:
[Captivate Android Development] demarton:
I've seen lag, creeping in after 60 hours or so uptime on latest 0.4.3,

my own opinion, I've seen memory leak overtime on 0.4.1, 0.4.2, 0.4.3 but 0.4.3 showing progress, it lags but not as bad as previous version after 24hr+.

Darkcore kernel, has issue with battery life, compare this with 0.4.3, 0.4.3 win hands down, use cpu spy look at how many % deep sleep Talon has, compare it with Darkcore.

Darkcore do not have that lag /leak issues >24hrs.

Each of kernels has it's own weakneses, let's wait for whoever comes out with un-lag long run kernel + great battery life, it will progress I'm sure.
[Captivate Android Development] nm131:
I've tried disabling voodo lagfix but I can't

I'm on 0.4.3 no-oc

I went to CWM>> voodo>>disable lagfix

It shows voodo lagfix is actually: enable

nextboot: disable

after rebooting nothing happens I'm still on EXT4

why is that? what did I do wrong?
[Captivate Android Development] slayp00n:
Exists, please why did we drop 1.2ghz+? tegrak only goes to 1.3 and is a pos... I was stable at 1.5ghz on your early kernals.. Please bring back an option for us who know what we be doing.
[Captivate Android Development] melvinaury:
Did you try using the Voodo control app?
[Captivate Android Development] mrhaley30705:
He's working on creating an overclock module for Talon. Unless something changes Tegrak is just temporary. Also, I think 1.2 is still an option without using tegrak

edit You can buy the app and go past 1.3, it also saves sings on reboot and allows uv from tegrak app.
[Captivate Android Development] nm131:
Yes I did but same result

any more ideas?
[Captivate Android Development] mrhaley30705:
Reflash the kernel.
[Captivate Android Development] nm131:
I've tried reflashing the kernel First I used 0.4.1(came with continuum 6.1)

then 0.4.2 still couldn't solve the problem and then 0.4.3 still can't
[Captivate Android Development] slayp00n:
I know I can go 1.2, but my phone just SINGS @ 1.5 :)...

Not a tegrak fan.
[Captivate Android Development] topiratiko:
@ existz

Or anyone thats knows

Did some searching could not find answer...what are differences between internal voltage and core voltage using tegrak? ill keep searching meanwhile

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] cnu4u:
Reboot Talon 0.4.3

@existz

We are still facing reboot after call when battery is <18%. One more observation - Battery use graph is not showing any information after 20%.... Not sure what could be the problem.
[Captivate Android Development] slayp00n:
Core voltage is the voltage in the cpu core, internal voltage is the internal bus voltage between chip elements: cpu, gpu, etc
[Captivate Android Development] existz:
Next version should have a few new features..so far been messing with ...

Updated sched_autogroup v4 patch with a few new upstream fixes (fixes memory leak in sched_autogroup)...not sure yet if that fixes the actual memory leak ...

Switched to TinyRCU (for smaller memory footprint) ...plus some new upstream fixes to RCU/TinyRCU ---needs testing

Added and switched to XZ kernel compression; also switch initramfs compression to none (cuts kernel size down to 5.5mb!) ---needs testing

Plus some general fixes from zacharias.maladroits snail kernel

...which we are looking into the actual memory leak and can hopefully locate it soon...(hopefully the new sched_autogroup fixes will fix it)..

Lastly, Shane87 has msg me and has made some progress on his/our new app 'MemoryFreak'... which will eliminate everyones LMK settings issue, you will be able to select from several different LMK presets from within the app.

Also fixed USB charging lock to 100mhz instead of 200mhz.
[Captivate Android Development] geokilla:
Were you able to fix the less than 20% phone freeze and restart problem?
[Captivate Android Development] existz:
Still trying to narrow it down, getting harder and harder...before it happened almost everytime and happened to everyone..now its hit and miss...but looking into it...going to take some time though..cause im going to have to revert one commit then test it, like i said though its hit or miss, so might take awhile to see if it happens or not...then move on to the next commit...and so on, so might be awhile before that one is narrowed down
[Captivate Android Development] demarton:
If memory leak / overtime lag finally fixed for good, talon will be a perfection.
[Captivate Android Development] Yuna:
did you tryed to do logcat on phone and then to test - phone shut off and then read logcat?
[Captivate Android Development] ngochuy:
awesome, i cant wait for it :D
[Captivate Android Development] topiratiko:
Bring back GPU overclock!!!!

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] topiratiko:
Off topic but HOW did the vibrant guys beat us to 2.3.5??

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] bryman27:
Are you talking about Trigger Redux? That's based on CyanogenMod that's why
[Captivate Android Development] existz:
GPU overclock never worked in the first place...can't bring back something that was never there :P...as I mentioned when adding it, it was only the initial support, may or may not work
[Captivate Android Development] mrhaley30705:
Placebo effect.
[Captivate Android Development] manny05:
Are you sure? Lol I swear I saw a big difference in speed when I raised the gpu. Everything open much quicker and loaded alot faster. I even turned it off to see if it's just a placebo effect and it was slower....
[Captivate Android Development] topiratiko:
Raging thunder 2 DEF ran better...and also higher quad scores...i did some comparos...i honestly cant say it didnt work

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] demarton:
Gpu oc never worked, no single benchmark shows it.

Oc to 300 50% without breaking a sweat looks too good to be true.
[Captivate Android Development] topiratiko:
Quadrant scores were higher on ALL 3 test runs....oced to 325

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] aalh:
that just shows how easy it is to manipulate quad scores
[Captivate Android Development] existz:
The creator of the code says it does not work yet, simply going by that ...I also see no difference, even at 400mhz... Quadrant is not a good tool to go by, I can run it 5 times in a row and each one be off by -/+ 500 points.. ran it yesterday and had 2300, 1830, 2765 (1.2ghz on latest test) ... its more of a random number generator than a benchmark..

Comparing it to actually overclocking the gpu in the source...for example setting max gpu clock to 250ish in actual gpu source, shows better results than just using configurable gpu oc at 400
[Captivate Android Development] topiratiko:
I want the attain.

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] existz:
I originally wanted to get one, or atleast international sgs2, but now will probably wait till ice cream flagship nexus comes out
[Captivate Android Development] topiratiko:
The prime? That seems badass. Might wait for it...dunno if i can tho

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] ngochuy:
When will u release 0.4.4? Im waiting for u:D
[Captivate Android Development] existz:
Once we get most of the bugs fixed ... trying to eliminate as much as we can before releasing... NO ETAs!

:P

But seriously, trying to fix phone call reboot issue and locate memory leak...both are being a pain in the ass to locate
[Captivate Android Development] zacharias.maladroit:
indeed ;)

and I just had an epiphany:

@komoornik & other with reboot issue:

please try this edition of Talon 0.4.3

- only change is a disabled stack-protector [this caused some major instability for me in the past on my cm7/miui kernel ^^]

- [and the obligatory broken bootanimation with my toolchain/box :p]
[Captivate Android Development] existz:
Zach,

Ok so might have it fixed, atleast on Talon... Reverted the 2.6.35.13 back to .7 and so far it seems to be working.. Ivr got about 8-9 confirmations from those that could reproduce the reboot almost everytime.. atleast now they have not had a single reboot... But, what don't make sense is, before on snail, the same issue was there way before we done the version update...but...someone posted some kmsg output on the 2.6.35.13 commit and it might be related to hibernate.c ...so it could be a PM commit or something that was in snail before, but not Talon, atleast until we updated to 2.6.35.13
[Captivate Android Development] zacharias.maladroit:
Hi existz,

awesome - thanks for letting me know !

so that single change reproducibly leads to those reboots ?

ok, so I'll redo a snail-build & see whether that also solves it for me

yes, afaik there are 1 or 2 commits that I had applied to snail before that are also included in 2.6.35.13 -so that might explain why users/testers got those reboots beforehand
[Captivate Android Development] topiratiko:
This is development at its finest. Existz&Zacharias ill be sendin u guys a nice lil token of appreciation soon

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] ngochuy:
Watsa has released apex 8.3. When will u release the next version of talon. I must go back to talon 0.4.3 because darkcore kernel in apex 8.3 is so lag
[Captivate Android Development] existz:
Hopefully in next couple days... Shane87 sent me update on his/our new app MemoryFreak, most of the layout is done and its looking nice.. also trying to still locate memory leak issue...really wanting to tackle those 2 before releasing..but if things go smoothly with my latest private test, might put up a public test in the mean time
[Captivate Android Development] existz:
Those with the lag after a long period/memory leak issue will you do me a favor? Kind of an experiment....on a clean boot do this from a terminal emulator...

su
swapoff /dev/block/zram0

This will disable swap/zram, and then see if memory leak still happens after quite a bit of uptime .. This way we can kind of eliminate if zram is the issue.. But do this right after you boot up (and no this will not stick through reboots)

But id like to get your guys results with zram vs no zram... our new app will have the option to enable/disable zram, the size of zram and swappiness value...(how much it swaps)...so kinda need some info for future purposes...if you want to monitor how much swap is used/free when using zram, simply type 'free' in a terminal emulator
[Captivate Android Development] irishvandal:
yo existz,

go get a dew, on me. tnx for all the hard work. cant wait to hear some solid results on 0.4.4.

conf#8H805550M6427762W

btw,

i am running talon 0.4.3 1200 342mb with apex8.2. this coupled with go launcher ex. with this set-up i seem to evade the lag bug by closing all running apps thru the drawer from go launcher. my biggest snag is a random deadlock for 3sec, followed by a softboot. this last lock changed the screens output to a wicked yellow hue followed by entire y-intercept pixel line drops(completely deal lines). was slightly worried, but i followed the softboot with a fresh cold boot. okay, maybe i was sweating, lol. no, not oc the gpu at all. running 1200 with -100uv the whole way down. might need to play with the uv a little. have there been issues with the gpu in 0.4.2 1200?

anyways, tnx again for all the hard work and solid support you provide to us all.
[Captivate Android Development] rlorange:
Aha! Someone else has the same problem that baffled me for ages. I think I finally solved it. But I needed to do a clean install of the rom but then an advanced nandroid restore of a back up just the data partition. Got all of my stuff back no problems

Check in your root directory... is /sbin folder missing?

**Simply Honey3.9, Talon kernel1.3ghz**
[Captivate Android Development] existz:
There was a commit back for 0.4.3 that ended up clearing out /sbin, but since has been fixed for upcoming 0.4.4...so if that was the problem, it should be fixed in next release

Fixed here:

http://existz.darkirc.info/git/?p=k...;hp=988169f7d5bee5dfdbfe2725efa5ff6bdb8247f6
[Captivate Android Development] existz:
Thanks alot! Really appreciate it...

As for the lockup, there is no known issue with 0.4.3 1200, I currently run 1200 myself with no issues...but its most likely caused by to much uv, 100mv on 1200 might be a little to much, usually I run around 50-75, best bet would be to try 50... also having way to less of voltage can cause it to act weird, so the screen glitch could have been caused by that.. as for the gpu, there is no OC on the gpu..the configurable gpu oc that was in talon did not work correctly and was removed, so the gpu is running stock and should not cause any problems...it sounds like not enough voltage on cpu..try running -50mV on 1200, you might also have to adjust the lower frequencies as well...but usually 50mV is a good starting point
[Captivate Android Development] Koizuma:
Gotta love how settings can vary from one device to another :p

for example my UV settings are:

1200mhz = -75mV

1000mhz = -75mV

800mhz = -100mV

400mhz = -125mV

200mhz = -125mV

100mhz = -125mV

Just gotta sit down and find out whats stable, from my testing i found using the stability tester app that whatever i had set would fail but if i increased by +25mV then it was fine.

like an example of this would be at 1200mhz i was trying to run a -100mV UV and it would either fail or lock the phone up increased it +25mV so that its a -75mV UV and can pass the stability test day in and day out and so far im stable on a day to day basis with how i got mine set.
[Captivate Android Development] topiratiko:
I use -150 ALL the way down STABLE I LOVE Talon :D

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] demarton:
I'll try it out, will report in a day or two.
[Captivate Android Development] Koizuma:
lol nice, I'm testing -125mV across the board now
[Captivate Android Development] Reynaldinho111:
I wish i could uv like that. I can oc to 1.6 all day but i can only uv by -125 on 100 & 200mhz :(

@existz

Are you guys still gonna work on gpu oc once you have memory freak working like you want? It seemed like a really cool idea to me and i'd hate to see it abandoned.

sent from my beloved cappy!!
[Captivate Android Development] aalh:
Custom boot animation not displayed

I have noticed this in MV and MVI, as well as the past couple TalonDEVs

when I flash the kernel, the rom's boot animation is replaced with the GS bootanim.

I have read that it is a cache issue and to reboot the phone, but this has not returned the boot animation to the custom one from the rom

what else should I try to fix this?
[Captivate Android Development] topiratiko:
+1

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] existz:
So im pretty confident we eliminated the phone call reboot issue, im going to try and put a public test up sometime today... quite a few changes in this release that I want to test with a wider audience before posting as a final release.. I will probably only put 1.2ghz non-bigmem version up as the test.. not sure yet when ill post it, still testing a couple new patches...but it shouldn't be long

We are still trying to pinpoint the memory leak, but there has been a few changes so far to kinda help with it ..so it might still be there, but might not be as bad
[Captivate Android Development] topiratiko:
YES! ready to flash NOW!

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] IDoMy0wnRacing:
eXistZ,

I would SO like to participate in your public test... if it is a select group of the public test, I have my hand raised.
[Captivate Android Development] existz:
The public test will be posted here in this thread, running a few more quick test real quick and then ill put 0.4.4.6 up for you guys to test
[Captivate Android Development] baxim:
hello!

were i download the .tar file to use on odin?

In topic haves .zip files

thanks!
[Captivate Android Development] watsa:
flash it using CWM just like u did for ROM
[Captivate Android Development] tylercarter:
jvr

jvr dropped on samfirmware. think this kernel with work with it? jw
[Captivate Android Development] existz:
0.4.4.6 Public Test

So im pretty confident the phone call reboot issue is resolved, so if you still have this issue, please let me know.. Also, we are still trying to locate memory leak issue, some changes have been made to kind of help with it until we locate it..so it might still be there, but it shouldnt be as bad.

0.4.4.6 Changelog

- revert back to 2.6.35.7 base

- added new kernel boot logo (just experimenting with new one)

- disable more kernel debug

- set VFP mfpu=neon optimization

- set usb charging lock to 100mhz

- upstream fixes for sched_autogroup

- upstream fixes for RCU/TinyRCU

- updated to sched_autogroup v4 (per session)

- switch to TinyRCU (smaller memory footprint)

- more random upstream fixes to ARM/SAMSUNG

- added sampling down factor to ondemand

- XZ kernel compression; initramfs to none

- tons of general fixes from zacharias.maladroit

- few new security fixes from zacharias.maladroit

This release will only be 1.2ghz 340MB version.

If some of you want to disable ZRAM to see if its related to memory leak..

From a terminal emulator...it will not stick through reboots

su
swapoff /dev/block/zram0

Please report kernel issues here
[Captivate Android Development] baxim:
hey watsa!

i have a problem! ;/

can you help me?

i try flash new talon kernel, but the file is .zip

I cant find .tar file.

i just rename the file to .tar and flash on odin get error ;//////

now i cant reisntall darkcore , i try flash back to stock and get error, kf1 and get error ;////

i can enter in download mode but not flash.

please help! \o/

thanks!!!!
[Captivate Android Development] topiratiko:
First :)

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] IDoMy0wnRacing:
Flashing now... :D (he says eagerly).
[Captivate Android Development] pizz0wn3d:
It's a zip file because you're supposed to flash it in cwm3, just like all the other zip files...

Recovery > install zip > choose zip > flash.
[Captivate Android Development] d_gritza:
I've been having a terrible time with Talon 4.1, 4.2, 4.3 over the last month (?). I will be trying this and letting you know my impressions tonight and tomorrow.

I've been having trouble with.

1. More Battery consumption than DC 2.9.X

2. More Lag than DC 2.9.X

3. Reboots as soon as the phone starts up (1 out of every 5 times).

I am running DlevROM 4.1 (JVQ) and always used Talon 1000 Big mem
[Captivate Android Development] topiratiko:
In order to start messing with memory managment we have to wait for shanes/existz app right?

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] existz:
Correct, which hes got the base close to done, it looks pretty sweet IMO, so hopefully it will be done for the final 0.4.4
[Captivate Android Development] pizz0wn3d:
Oh man this is gonna be awesome.

-Herp derp Captivate XDA app
[Captivate Android Development] existz:
Yea, the new app from shane87 is gonna be epic...user will have full control over memory management .. I haven't been this excited in along time., we have been brainstorming and have came up with quite a bit of ideas for the end user to control..it will be very nice ..can't wait till its finished!
[Captivate Android Development] watsa:
0.4.4.5 seems to be working fine with JVR so far buddy. good job. Feels much smoother IMO
[Captivate Android Development] Peaster111:
Another milestone event for TALON... keep pressin'. Hopefully the phone bug is solved (squished). That is huge itself. Good luck on the mem leak... patience pays. I was having to go back to xcal's reorient 2.0, due to the phone call reboots. While xcal's kernel is stable, the lag is painful. I need to stay put with Talon! :D

Thanks for all your dedicated efforts!
[Captivate Android Development] existz:
Hopefully this version fixes it for good, def let me know if it resolves it for you
[Captivate Android Development] IDoMy0wnRacing:
Out of the box; picture color and picture clarity is awesome (Neocore).

Added some OC and UV, very fast and very stable (without Lag Fix).

Trying to stress the phone with this Kernel I ran repeated tests using:

AnTuTu Benchmark, CPU Benchmark, Linpack for Android, NenaMark1, Neocore, Quadrant Standard (for stress only). Played a couple games of Angry Birds, and Tank Recon 3D.

Used the phone, sent some texts, took some pics and sent MMS.

After 4+ hours of hard use, I have NO issues to report at this time...

Job well done.
[Captivate Android Development] squishy5:
existz or any other person is their any other optimizations other then oc for the gpu to enhance the graphics

The sgx 540 is a great fast gpu that is crippled by samsung
[Captivate Android Development] Holmes108:
Is there something you're having trouble running? I've never had a single game give me a problem.

Sent from my Galaxy S I896
[Captivate Android Development] squishy5:
no there is no real problems. But there is a lot ram,screen,sound, and processor optimizations and there is basically none optimizations ( other then oc) out today for the cappys gpu.
[Captivate Android Development] rlorange:
Yes that would have caused it. But flashing later versions did not fix it until I did a clean install with and odin rom package

**Simply Honey3.9, Talon kernel1.3ghz**
[Captivate Android Development] existz:
Well...not much that i know of, we can still OC the gpu in the source (not the same as the configurable GPU OC that was in Talon, which did not work), we can set max clock for the gpu for each frequency (ie. 300 on 1.2ghz, 250 on 1ghz..etc)...but the only problem with this is, just like oc'ing the cpu not all phones can handle certain gpu max clocks..this is main reason why i have not bumped up the gpu max clock by default.. Which once Talon is a point where its fully stable, i might start looking into it, giving a max clock of like 250 or so, something small thats stable on all systems (who knows, we might be able to get 300mhz+ out of it and be stable for everyone, I dont know yet havent tested it)...But other than that, theres really not much that I can do, as always, we are limited with samsung source.. But im not saying nothing can be done, just that its out of my comfort area and someone else with more experience/know how would have to come up with something...