yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] jontoo:
I think that I take the right one I'm with i9000, just download from providet link on first page :(
[Captivate Android Development] pikachu01:
This is the captivate thread ;)

The i9000 ones are here:

http://xdaforums.com/showthread.php?t=1106075
[Captivate Android Development] existz:
I9000 builds ALWAYS have -I9000 in the filename, so if your on i9000, make sure its at the end of the filename, otherwise its a captivate build
[Captivate Android Development] jontoo:
Sorry mates it's my mistace :D, just now I read it say Captivate Android Development :rolleyes:
[Captivate Android Development] Jep56:
Flashed this last night. Was on charger for 7 hours! Pulled plug and it dropped to 98%. Nice!
[Captivate Android Development] upNsmokeAllDay:
Yeah same thing happened to me and i haven't found a fix yet.
[Captivate Android Development] rajendra82:
Thanks for the explanation. What about the second part of the question, though, dealing with different memory usage and total memory being reported by Settings and Task Manager on the Captivate? Can you explain what is going on there?
[Captivate Android Development] pikachu01:
It's always been like this (discrepancy of free memory from "Running") My best guess is that it's deducting used RAM from the services displayed there and reporting it. There are services in "Running" that are not shown in there that uses memory.
[Captivate Android Development] rajendra82:
But shouldn't the sum of the used ram and free ram still add up to 340 MB?
[Captivate Android Development] pikachu01:
Yeah, which I am also confused. Android OS monitoring tools agree with Task Manager, hence I would think that is the de-facto number to look at.
[Captivate Android Development] Johnsondr80:
Will be sending you a pm. Please look for it later today.

Ps. DG thinks he may know what is and how to fix memeory leaks in gingerbread. Just saying.

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] johan8:
Here is i897 section.

why don't you browser i9000 dev section ?

Talon for i9000 is there ! not here !
[Captivate Android Development] zerkai:
He said a couple posts ago that he made a mistake.
[Captivate Android Development] demarton:
I'm experiencing unusual amount of lockup in game on 0.4.4.13

looking at changelog a few pages back

is it possible that this setting is too aggressive UV not suitable for all devices?

is that setting switchable?

I'm using my phone for games a lot, currently used 1200 version, going to try 1000 non oc one, we'll see.
[Captivate Android Development] carey:
Switch to .15 and see if that alone helps

I came, I saw... I left confused
[Captivate Android Development] kodos96:
Who did you mean you were going to send a PM to? Me? If so, I didn't get it.

If DG says he knows how to fix the memory leak... well, consider me skeptical.... but of course I'm willing to take a look at whatever he comes up with. Do you have a link to any more info?

BTW, with the latest changes (some since the last test release) I think the memory leak may have been reduced somewhat (but not entirely eliminated). Stay tuned.
[Captivate Android Development] demarton:
same with 0.4.4.15 1000, and it's not just 1 game, different games with different lock up time.
[Captivate Android Development] kodos96:
Yeah, it seems like no two apps ever report free memory exactly the same way, because there are just so many different ways to do the accounting... under the hood in kernel land, its a lot more complex than just "free" or "not free"... there's different memory zones, and different kinds of allocations, and it's highly debatable which is the most "correct" way to count them, i.e. which kinds of memory do you consider "free". If you go to a shell prompt and type "free", you'll see a VERY small amount of free ram reported - that's because it's using a strictly literal interpretation of "free," which considers ram used by pagecache and swapcache as being "in use"... which you could argue is technically correct, but not very useful, since cache, though not LITERALLY free, is EFFECTIVELY free, since it can be discarded when memory pressure hits.

That's just one example of many ways that its possible to count free ram differently... without looking at the source code, its impossible to tell how any particular app is doing it's accounting. I'd recommend you try the "system panel" app from the market for measuring free memory - it's a really nice app, and since you can install it on your captivate, your nook, and your status, you can get a consistent measurement methodology on all three.
[Captivate Android Development] existz:
Most likely not, it has actually been in previous versions of talon already for awhile, a couple test back it was pulled for like 1-2 test, then added back.. (before it had uV on LCD also, it was pulled because of that, then RAM/ADC was added back)
[Captivate Android Development] rajendra82:
Thanks again. I'll take up your suggestion and use System Panel (and System Information Viewer, which I also like) on all three devices.
[Captivate Android Development] alexige:
I seem to be experiencing unusually high battery usage on the last two test kernels just to put it out there. Same usage as before.
[Captivate Android Development] slayp00n:
Hi So I flashed the latest darky rc2 jvr, but now the homebutton doesnt work, even thought in keytest in cwm it does.

What is going on here?
[Captivate Android Development] cnu4u:
In general, we tend use phone when we update something new.

Go to, battery usage and check which is eating up your battery. Based on this, if required, use TiBu to freeze apps.

Try to re-calibrate. This generally requires when switching between ROM(s) but no harm in doing when required.

If nothing works, if you know someone carrying Cappy, try their mobile battery if your mobile's battery is something you need to re-think off.
[Captivate Android Development] cnu4u:
I hope you got it answered in other thread... :)
[Captivate Android Development] Johnsondr80:
Sorry for confusion. I was sending pm to eXistz. (Sent now BTW)

And just saying to all talking about memory leak.

I just seen a post or gtalk message with him where he breifly mentioned that he thought the memory leak was fixable by linking data/and dbdata/ some how and thought he could fix it. Asked to see a users screenshoots of tibu screen....yea now I remember....on his captivate cog thread....

The user posted the pic and now no responce about it to-date.

So I don't know if he's on to something or not. If he his he's keeping it tight liped.

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] timn2bama:
New Gmail

On my phone the new gmail app 4.5 I think made my phone slow and laggy! I went back to 4.1 lets see how that does 24 hrs from now. Plus it was slow to load my new messages up to.
[Captivate Android Development] eliminat:
After 24 hours, .15 is GOLDEN for me. If you also get the supposed DG GB memory fixes, I can just imagine how great GB could be.
[Captivate Android Development] carey:
Darn, was night and day for me and was hoping it would be for you too. Which games are particularly bad?

I came, I saw... I left confused
[Captivate Android Development] Koizuma:
So far for me .15 is running well for me lag seems like it has cleared up too.

Swyped from my Captivate using XDA App
[Captivate Android Development] alexige:
Like i said usage didnt go up, my job doesnt allow me much play time now. The phone is staying awake, I think its Android system eatting it. I'm in the process of calibrating my battery now.
[Captivate Android Development] kodos96:
That doesn't sound like it has anything to do with a memory leak.... probably some other issue he was talking about.
[Captivate Android Development] Yuna:
Hmm, confirming thoughts too: latest kernels hive me pretty high amount of non-sleepy phone. In 5.5 hours io get nearly 1 hour and 2 hours screen on/awake timers.

Can this be REALY kernel releated?
[Captivate Android Development] pikachu01:
It's not for me. I get 2 days of battery life with 2 and 50 mins of display time. Should be an app problem. Try freezing some apps. Have 97% in sleep mode.
[Captivate Android Development] alexige:
I'm thinking its a high draw on android system. From my research around here it was an early bug in Samsung GB that got nipped around a month ago and somehow came back.

Sent from my Blanco Galaxy Tab 10.1
[Captivate Android Development] Yuna:
Hmm, but percentage were extremely low...
[Captivate Android Development] demarton:
anyone notice weirdness 0.4.4.15 when playing games yet?

it's frequently locked up, or at least that was I thought, screen not responding to touch, all buttons not responding.

What's weird I found out when playing captain america sentinel of liberty, just in for 2 minutes, then all inputs stop responding, no it's not lock up, capt animation still moving on screen, just that I cannot control it, none of the button work even, on/off. So I leave it there for like 5 minutes, animation is getting choppier, and eventually screen dies, and few secs later soft reboot.
[Captivate Android Development] CuriousTech:
Something has definitely improved. I went from 0.4.3 to 4.4.15 finally and it's running much smoother. The market was really slow, but it just updated. Oh great, this looks like pop-up ads. ^%@$!!
[Captivate Android Development] pikachu01:
If you could provide the list of apps that lock up (free ones) I can try and pinpoint which code is rogue. A next test would try to fix the issue. Thanks!
[Captivate Android Development] pikachu01:
Wrong thread.
[Captivate Android Development] apparition:
0.4.4.15 has shown a big improvement since 0.4.3 with regards to lag. After being on DarkCore 3.0C for a while though, switching between various apps and bringing up contexts and menues are still more responsive on DC. Hope this memory leak/lag issue g:cool:ets solved soon because I do like Talon's OC ans UV options
[Captivate Android Development] cnu4u:
I do have that issue sometimes. problem would be with task manager or tasks or sns. I kill them manually from going to running services.
[Captivate Android Development] Yuna:
I forzen tasks, but for what sns required? can i freeze it too?
[Captivate Android Development] cnu4u:
sns is required for in built facebook and so on. Not sure complete list but you can freeze, else kill it for sometime and if something is not working, unfreeze or restart the phone
[Captivate Android Development] lownox:
Only needed for fb widget as far as I know. I have deleted it without issue many times and never had a sync issue by doing so. I don't use Widgets that need sync though.
[Captivate Android Development] bballer182:
I skipped a view builds. went from .9 to .15 and i have noticed that the auto-brightness is working correctly or mostly correctly now!
[Captivate Android Development] melvinaury:
I'm just continue with the charge bug. Yesterday I do a test. I charge the phone off and turn it on and let it charge to 100% t hen unplug play some games until 95%. Then reconnect the cable to charge the phone at 11:00 pm, today the phone has the message that is fully charge, I disconnect and Booommm the battery was only 91%.

I already re-calibrate the battery.

Any suggestinos, the ROM is Delv's RAM 4.2 and the buil of the phone is 10-10

I'm
[Captivate Android Development] Rrryan2:
Still having memory leak on .15. After about 12 hours since but I'm at 312 mb in use, and using ' clear' in task manager only gets me down to 310.
[Captivate Android Development] geokilla:
Same for me, but it's not as bad as before. Vastly improved.
[Captivate Android Development] pikachu01:
The charge bug is not fully fixed, but I've heard that people who got around 70% last time managed to creep up to 95% just by using this build, hence it is greatly improved but not fixed.

And what is 10-10? The latest build is 0.4.4.15
[Captivate Android Development] tmng95014:
I think you are talking about kernel build date and he is talking about phone build date.
[Captivate Android Development] Wdustin1:
The 1010 is the build number of the phone its self I have a build 1007. I have only been dropping to 98 I was dropping to 60 so this kernel has REALLY improved over 4.4.9.
[Captivate Android Development] Wdustin1:
Repost delete please
[Captivate Android Development] DaUnderSheriff:
Noticing email lockup with the test build .15. Only thing different is the test build flashed. Will try clearing cache. Freezes phone.

Sent from my Apex 9.x & Talon powered Captivate.
[Captivate Android Development] existz:
Email works fine for me.., you might have to adjust your OC/UV settings with 1.2ghz version since the 1ghz step was removed, the cpu will spend more/less time on different frequencies now., so what might have been stable then, might not be 100% stable now for certain frequencies
[Captivate Android Development] mrhaley30705:
@eXistZ: All the current CWM versions have cleaning scripts built in, right (similar to the one recommended by MIUI flashers)?
[Captivate Android Development] existz:
0.4.4.16 Public Test

0.4.4.16

Changelog since 0.4.4.15

- tons of ext4 upstream/aosp fixes

- some upstream/aosp cpufreq fixes

- more cgroup/sched upstream fixes; fixes from CodeAurora

- CodeSourcery 2011.03 (GCC 4.5.2) with O3 and Graphite optimizations

Let me know if tethering is better/worst in this version (dropping every couple minutes)
[Captivate Android Development] eliminat:
Apparently I just checked at the right time...
[Captivate Android Development] cnu4u:
wi-fi not getting enabled

I have updated kernal 0.4.4.15 and wi-fi is not getting enabled. Tried via settings & toggle.... nothing is working.... :mad: Please help.

Edit: Updated to .16 but no luck...
[Captivate Android Development] Sqb:
Sweet. Thank you for the friday treat!

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] pikachu01:
What is the error when you tried to enable Wifi? Try using a widget to toggle your wifi?
[Captivate Android Development] cnu4u:
No.

Tried toggling wifi button by pulling notification bar. It did not work. Then wento setting and tried turning on, then it is showing "Error" under Wi-Fi. Nothing new I have done to my phone.
[Captivate Android Development] pikachu01:
It's sometimtes normal to get the error. Try toggling a few times more and you'll eventually get it.
[Captivate Android Development] existz:
Try clearing cache and dalvik cache
[Captivate Android Development] artvandalay22222:
have you tried reboot?
[Captivate Android Development] cnu4u:
When I try to clear davlik cache, it is giving that "E: ......not found". I think it is clearing because boot up is taking more time but not sure.

It worked for the first time but not working after turning off... :confused:
[Captivate Android Development] pikachu01:
Your ROM is unstable from the get-go. Probably a pit error (not sure). Try flashing stock JVR using repartition 512.pit and then flash a custom ROM of your choice. After that try reflashing Talon again.
[Captivate Android Development] geokilla:
I get the same thing when I clear dalvik cache as well. Been like this since the Froyo days actually. This means my phone is unstable?! :confused:
[Captivate Android Development] pikachu01:
It means your pit file is not 512. But not sure if it really is clearing Dalvik caches or not. It's a fail safe method to be sure that your issue is not due to some other reasons such as apps/custom ROM instabilities etc.
[Captivate Android Development] geokilla:
Well when I clear Dalvik, it still takes a couple minutes to boot up after so I think it gets cleared properly... I dunno lol. But as long as it works I guess.
[Captivate Android Development] cnu4u:
My only surprise is that this E: error will not be found when using other Kernel. Thanks for your answer. I will try to see if resetting will help.
[Captivate Android Development] pikachu01:
Thank you for making the effort to do that :)

A lot of issues are hard to troubleshoot if coupled with inherent instabilities. Your effort would lead to Talon kernel being more robust by reducing the number of factors.
[Captivate Android Development] cnu4u:
Sometimes toggle seems to work after giving a long break between on & off. It's weird but I can live with it for now. If it bothers me again, I will give a try to do reset. Thanks for your help.
[Captivate Android Development] pikachu01:
ytt3r just posted a Talon fork for CM7/MIUI. Go check it out:

http://xdaforums.com/showthread.php?p=16602723
[Captivate Android Development] IDoMy0wnRacing:
4.4.15 is working great for me. Updated to 4.4.16 and I lost WiFi capabilities. Reverted back to 4.4.15 and all is well again. Fast and smooth.
[Captivate Android Development] Rrryan2:
.15 gave me a bad memory leak with continued uptimes; .16 seems good so far. I did notice that Wifi turned itself off at flash, but was readily re-enabled from power manager widget.
[Captivate Android Development] everest.deth:
Bootloop? lol

Hey guys, I just flashed the Test version (0.4.4.16) over Apex 9.1 - which is compatible - and somehow i got caught up on a bootloop. The phone will say "Loading Talon" with the nexus sign on the background, but once it finishes loading it reboots to the ATT logo, and starts "loading Talon" again. I am quite new to The captivate forum, but im not a noob by any means, so shoot up any suggestions you may have :P

Please notice that me not being a noob doesnt mean i cannot make dumb mistakes lol, so just to quote what i did, i flashed Apex 9.1, it does a data wipe over the previous 9.0 version, and right after i installed Talon Test version via CWM 3.x

Thanks for the support

Edit: So instead of flashing them both (ROM + Talon Kernel), i installed the ROM only to see if it booted on its own, and in fact it did. So I guess i must be missing a step or something while installing the kernel?
[Captivate Android Development] irishvandal:
^^

bad flash most likely. this post here in the APEX forum is saying that APEX 9.x and Talon .16 are compatible. i would suggest a stock flash and start with the rom flash afterwards. i am one that really prefers a clean sd before flashing any ROM, even if it is a version change. updates i treat diff though. i just roll those over.

here is an odin stock pack from S7 that i have used since the big GB jump and have no issues thus far while following every direction to a tee. i hope this helps with your issue and you are back up in the Cappy clouds once again real soon.

good luck.

edit to his edit - the only step is to goto recovery as you well know and select install zip, install Talon .16 and should be a wam-bam for ya. and def flash under SEPARATE boots. i personally clear my cache/dalvik manually even if the kerenl does it on its on. kinda of my own little prevention tool. again, good luck to ya. i am soon to follow you to the APEX9.1/Talon .16 world, i have two meetings tomm so i need my cappy stable for the next 24-48hrz.
[Captivate Android Development] F1reEng1neRed:
I'm running the same setup and everything is good so far.
[Captivate Android Development] cnu4u:
I have been on .16 for past 9 - 10 hr. This version its amazing so far.. Overnight I used to drop 6% drop.. but not last night... it might be too early to provide this feedback but @existz work is amazing... Thanks
[Captivate Android Development] parnz:
since flash .16 phone freeze (when playing some app such as typing text, scroll up-down web page, playback video) than reboot :(

but .15 work find

edit: I used 1.2GHz version I'll try the 1.0GHz later, but flashed back to .15 right now.

ROM Contunuum 6.2
[Captivate Android Development] Time_Zone:
me too. think it is bootloader related.
[Captivate Android Development] pikachu01:
Enable logcat and post your last few lines before you rebooted.
[Captivate Android Development] parnz:
Phone reboot itself after freezing so I can't do anything on that time.
[Captivate Android Development] holeindalip:
phone is running like a champ on .16, tethering is also working correctly again

apex 9.1

talon 4.4.16

build date 1010

kf1 boot loaders
[Captivate Android Development] jcr81:
I assume this kernel works with jvp?
[Captivate Android Development] pikachu01:
Yes, logcat is persistent. It stores a log on memory. You just need to get the log out and see what it says.

Yes, it is compatible with 2.3.4, but try it with JVR if you're facing problems.
[Captivate Android Development] parnz:
update: flashed the .16 - 1.0GHz version seems working for now :D
[Captivate Android Development] Holmes108:
Just want to add I had problems with 16 as well. 15 ran great, but 16 would freeze my phone after 5 minutes or so and send me to the 'unknown upload mode' screen, causing me to pull my battery.

Might have been a bad flash, and I didn't try again. Just went to 15 again.

This was the 1200 version, btw.
[Captivate Android Development] mrhaley30705:
1200 version of.16 causing random reboots and freezing up (once on shutdown). Tried reflashing, only made it worse. Back to .15

EDIT using vr scheduler and no uv on Continuum 6.2.1b
[Captivate Android Development] iXNyNe:
I can confirm 0.4.4.16 1200 causes bootloops after the galaxy s boot animation on apex 9.1 for me

Tried reflashing and downloading fresh copies of both the kernel and rom

0.4.4.15 and below do not do cause this.
[Captivate Android Development] Rrryan2:
Uh... I can confirm it doesn't, as have several other posters in this thread.

Bad download or flash perhaps?
[Captivate Android Development] watsa:
+1

I am using .16 on Apex 9.1. No bootloops
[Captivate Android Development] topiratiko:
Negative. Perfectly fine& flyin here

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] iXNyNe:
:( maybe I'm unlucky I haven't had any other issues with flashing anything, so I *think* my bootloaders are fine but I don't know a sure shot way to test.
[Captivate Android Development] topiratiko:
Can someone confirm that this update gives 339 ram as oposed to 340? just curious

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] iXNyNe:
It seems the poll in the apex thread favors talon and you use it yourself, will it be the default kernel in a future apex release?
[Captivate Android Development] existz:
Yea thats normal.., its from 2011 toolchains/O3 + graphite optimizations.., But im going to revert back to Linaro toolchains again, as they were not the reason for tethering dropping.., seems hardcore found it in the latest samsung source update, so hopefully ill get another test up shortly
[Captivate Android Development] topiratiko:
Cool. This is lightning fast and responsive. Haptic feels sharper too. Not sure if thats Talon, Apex 9.1 or just in my head

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] existz:
0.4.4.17 Public Test

0.4.4.17

Changelog since 0.4.4.16

- reverted all USB changes from latest source update

- bump voltages back up for RAM(1.6->1.8v) and ADC(3.0->3.3v)

- Linaro Android 4.5 (GCC 4.5.4) with O3 and Graphite optimizations

Hopefully this build fixes the Tethering issues where it keeps dropping., also

removed the uV for RAM/ADC, let me know if this fixes sleep death for some of u