yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] demarton:
it's the /cache partition, all app downloaded / updated from market will be stored temporarily on this /cache with filename downloadfile.apk, on mine it's only 27MB in size. So whenever this space filled you will got not insufficient storage message, it doesn't matter how much is it in internal/sd. That's why all this Samsung bug where app dev must split their apk to small one or it simply won't work/downloadable on samsung.

Why the hell samsung set it that small is beyond me, have been looking around to find how to resize this partition but hadn't find any clue yet.

For comparison, on lousy old Nexus 1, /cache is 80MB.
[Captivate Android Development] existz:
You can actually disable journalling on /cache to allow dloading of apps larger than 30mb...hardcore had a thread on how to disable jounral on ext4 partition in i9000 forum awhile back..just disable it on /cache and you should be good then..
[Captivate Android Development] sstarre:
@existz..

This is just an FYI....

Running 0.4.4.8 and it seems good...very smooth and responsive.

I set ZRAM_SIZE=0 and I usually have only 230-240 MB ram used when I clear with task manager. It was significantly higher with the other versions and never really went down until I re-booted..now it seems to free up memory even when idle for a while. That's new behavior for my phone.

No wifi re-boots at all.. But wifi is disabled on every re-boot and when I turn it on from the settings menu, it usually takes 2-3 trys and then it's ok.

All in all, it seems like a much improved release.

Thanks for the efforts....
[Captivate Android Development] Koizuma:
So far i noticed on the latest test that I've got a memory leak from hell and back. normally after a whole night of sitting i still had alot of free ram, but checked it when i got up this morning and had only 15MB free. I've noticed that my phone will lag every once and a while as well
[Captivate Android Development] kodos96:
Well it's not clear how much of the "charge bug" is caused by the kernel vs the framework... in fact it isn't even clear how much of it is actually a bug in charging behavior vs just a difference between Froyo and GB in how the system REPORTS charge % (i.e. how much it lies to you)....

But that said, I backported some battery/charging code from infuse that eXistZ and I are currently testing.... it's too soon to say for sure, but it MIGHT end up helping the problem some.

I also backported a small fix to the light/proximity sensor that seems to help some with the auto-brightness problems (though doesn't fix it completely - I think fully fixing it will require framework changes)... and it MIGHT also help with the proximity sensor problems some people have.

Also, I think I have a pretty good idea how to fix the issue with the infuse wifi driver update making the dropdown toggle not work sometimes.... if it works like I think it will, then we might finally have no wifi-reboot AND working toggle....

So, yeah.... the infuse source release has turned out to be a pretty major help to us... ALMOST as good as if Samsung had actually put out updated source for cappy/i9000 O_o .... a lot of this stuff is still up in the air, but finally it seems like we're at least making some progress towards resolving some of the longstanding issues with GB on the captivate
[Captivate Android Development] kodos96:
What you're describing is not a memory leak. A memory leak is when your amount of available memory, WITH NO APPS LOADED, decreases over time. So unless you're using something like system panel to kill all your apps first, just looking at the amount of free ram doesn't tell you anything about the leak.

I'm not saying we don't have a memory leak somewhere in Talon - it seems like we do. But lets try not to confuse the issue.
[Captivate Android Development] johan8:
simply try that

umount /cache

tune2fs -O ^has_journal -m 0 /dev/block/stl11
[Captivate Android Development] Holmes108:
I'm not a programmer, but that would still be a memory leak no? It would just be that we couldn't be sure if the system is causing it, or an app.

Available ram shouldn't just constantly drop when nothing is being used (ie: overnight). It might fluctuate, due to background syncing, etc.... but it shouldn't just drop and drop until the phone becomes laggy.

Again, not saying it's Talon's fault...
[Captivate Android Development] melvinaury:
Well, it depends. There is a lot of Apps that likes to run in the background, you can close the app with a task manager and it will load again. You can go to applications, manage application and force stop. And it continue to load an ex Gmaps.

That's not the problem of the kernel, it's from the app itself, and that behavior can cause the memory to be used and lag in the phone.
[Captivate Android Development] zacharias.maladroit:
that behavior usually comes down to memory leaks and issues with not properly coded apps from userland

(I e.g. had that on Linux and the Xorg-server or a frontend to git where it would consume several GiB - resulting in massive swapping and slowing everything down to a crawl - killing those processes ended up in freeing the ram, swapping data back into ram and everything was fast again)

take a look at the app

usage timeline from the market and from time to time

see whether memory-usage of an app has increased to unusually heights
[Captivate Android Development] Sqb:
Zram set to 0 and so far so good. Will give time to settle in and report back

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] topiratiko:
I've noticed erratic memory management behavior. 6-7 hours runtime i checked ram it was 301/340...hit clear...dropped to 265...2 minutes later was @ 291 hit clear zero apps closed and LAGGY ...im using my own lmk values that worked great on 4.4.6

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] topiratiko:
Just checked again sittin @ 304/340. sync off apps closed.

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] tmng95014:
+1. More than 24 hours and no leakage observed.
[Captivate Android Development] topiratiko:
Can i set zram to zero in etc/ram config?

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] existz:
Yes, just set ZRAM_SIZE=0 in /etc/ram.conf and reboot...this will disable ZRAM and keep it from loading the module on boot
[Captivate Android Development] topiratiko:
Quick question...what was zrams initial upside?

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] LNJ:
Latest public test build is way too laggy for me as well. Phone does nothing and it consumes 304mb of ram.

Switching between anything lags terribly.

LMK settings too liberal maybe?
[Captivate Android Development] topiratiko:
Thats not it because i have my rather strict settings set for lmk...i just disabled zram to see if that helps

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] topiratiko:
Looks as if that may do it...i have xda,browser,AND market in memory and sittin @ 268...will update later

Its a pleasant surprise that we can use infuze source....i gues it really is just an overclocked cappy with a bigger screen!

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] existz:
The lag might be due to the new cgroup changes, I've seen some reports of this on other android kernels running these changes..so ill probably revert them and see how it does.

Ill put a new public test up shortly with a few fixes
[Captivate Android Development] Dani897:
did this kernel break gps for anyone else? the service wont even start.
[Captivate Android Development] johan8:
I think you are quite don't understand what's going.

All those kernels here, such as speedmod, sucherpunch, onix, talon etc.....

They are kind of Reoriented kernel for i897 use with i9000 rom !

As you know i897 rom is ATT branded.

To restore back to full and unbranded GalaxyS, everybody here use i9000 rom.

And due to different h/w, you will need i897 kernel or such Reoriented kernel.

i9000 rom means, stock rom, and cook (custom) rom.

Darky, Serendipity, Perception etc etc....

They are all based on stock i9000 rom.

So !

After flashed those i9000 rom, flash the i897 kernel or reoriented kernel,

your phone will work properly.
[Captivate Android Development] shane87:
Hmm, how are you trying to turn on gps? I have a widget by curvefish that I use to enable/disable gps. However, after flashing to gb, it has not worked. Turning gps on through the notification bar or through settings works, but my widget does not anymore.

ROM: Perception II beta 1

Kernel: TALONDEV 0.1.1, voodoo snd v8, chainfire ext4 lagfix

Modem: I9000 ugjk4

HW Build Number: 1101
[Captivate Android Development] rlorange:
Us i9000 owners are looking at talon with envy! Captivate dev's are pushing the envelope with gb and exitz is the first with oc/uv... We hope and beg that this team ports talon over to i9000 soon

**Simply Honey 3.0, UltimateGB beta7 kernel, JQ1 modem**
[Captivate Android Development] jde984:
You can use this kernel with a JVB based ROM in the i9000 forums. (I tried Debus and Juwe both worked well).

Keep in mind though, when you flash one of those it will replace your kernel with a non-reoriented one, so you'll need to flash this kernel back onto your phone.
[Captivate Android Development] astrocrep:
I just flashed 0.1.3 (running Debus G1 from the i9000 forums) and I've lost the function of my home button.

When I first installed Debus, I needed to use Xcal's home button fixed... but after flashing 0.1.3 (worked fine in 0.1.2) Home button no longer registers it's hit (the light's still flicker when pressed though)

I tried reflashing Xcals fix... still no dice... any ideas?

Thanks
[Captivate Android Development] ou812bkewl:
Has anyone on here tried stagefright setting in the "tweaks" app installed on Continuum RC3? It inflated my Quadrant score to over 2800. I couldn't find alot of info on what it actually does. I know Quadrant scores are BS but I just wanted to know why the score would have increased so much.
[Captivate Android Development] H3llstorm:
I gave in and flashed MikeyMike01's Gingerbread ROM (GR). What do you expect from someone who's only run Assonance and Serendipity ROMs? :D

I had to do that with MikeyMike01's GR anyway, even though I flashed Talon after flashing stock GB.
[Captivate Android Development] solinar:
Looking to upgrade from 0.1.2 to 0.1.3. What happened to the CWM flashable zip versions? Am I missing something?

Edit: I downloaded SGS kernel flasher and used the tar file. It worked fine for anyone else looking to do the same.
[Captivate Android Development] grkmaster:
Id like to know as well!
[Captivate Android Development] existz:
Its the same exact branch me and ytt3r use, I've cloned it 20 times now and every kernel here has been built from it ... sorry for leaving one thing out in the config, you can fix it with a make menuconfig or set it in the config manually..or use any governor you like..what else doesn't match up? But like I said, it's the exact same branch we use and I've cloned it and built off it tons of times.. Use 2009q3 toolchains, 2010.09 seems to cause problems , also read supercurios notes in the readme and make sure your setting the localversion correctly, these kernels have to be built different than 2.6.32 and are wayy more sensitive
[Captivate Android Development] CuriousTech:
Holy hell! 2850. It went through the arithmetic part in a flash. Only 16.5 Mflops in Linpack though.
[Captivate Android Development] markmunsch:
Anyone else having issues downloading the kernels? I've been trying last night and now this morning and the server keeps timing out.
[Captivate Android Development] rjayflo:
I was running Simply Honey 3.1 with Talons oc/uv....super super snappy and fast. Currently I'm trying out GR-9 by mikeymike with same kernel...snappy as well
[Captivate Android Development] existz:
Nope, just tested from my phone and it downloads
[Captivate Android Development] Vivified:
I had a really weird issue happen last night on Talon 0.1.3(first night with it). I laid down for the night to get some sleep, plugged my phone in and turned on my tunes(always go to sleep to music) and set the sleep timer in PlayerPro. After about 5 minutes(still awake) the music began to skip really bad, almost as if the phone was lagging really badly. Opened my eyes to annoyance and grabbed my phone. The screen was black and wouldn't come back on and the music continued it's poor performance. I ended up having to force it to recovery using volume up+power. So I flashed Dark Core, rebooted, started PlayerPro, set my sleep timer, and closed my eyes once again. Phone worked fine and was good to go this morning, albeit still having the charge bug to it was ~80%.
[Captivate Android Development] markmunsch:
Well hell I don't know what the deal is. On my phone i get webpage not available, and on my PC i get problem loading page, server timed out.

I'm running RC3 so I have the older 0.1.3 and wanted to swap it out, but I guess it'll have to wait until I can download it. Strange, like I said I've been trying this since last night, still the same things on both phone and PC.
[Captivate Android Development] existz:
hmm..works both on my phone and pc... try http://berryfx.com/RobBeane/Kernel/Talon/
[Captivate Android Development] markmunsch:
Nope that link says not available either, maybe I need to clear my caches. But I've tried from the PC in firefox, from the XDA app on my phone, and in the phone browser, with the same results.
[Captivate Android Development] nakedninja42:
Odd, I had no problem with the link yesterday. I just tried it out and its only taking me to berryfx main page while still showing talon in the address bar :confused:
[Captivate Android Development] pinoymutt:
So far so good with the .8 release. No discernible lag, nor issues with Wifi. Battery seems to be quite good so far compared to earlier builds.
[Captivate Android Development] existz:
0.4.4.9 Public Test

Changelog since 0.4.4.8

- disabled sched_autogroup v4

- set correct apll_freq_max value for OC versions

- merge fixes from 2.6.35.9 longterm linux tree

- updated proximity/light sensor patch from Infuse

- reverted cgroup timer slack subsystem changes

Let me know if the slowdown/lag introduced in 0.4.4.8 is resolved with this test

Also theres an attempt to fix proximity issue, so let me know how it does for you
[Captivate Android Development] irishvandal:
uh, i will take one of these, thank you very much.

btw, the bfq sched under 0.4.4.6 is a little wonky. couldn't put my finger on it and don't feel like dealing with it, switch back to sio to get me home and now going to run some beta for ya i guess with this new bird of urz. lol. tnx again.
[Captivate Android Development] Peaster111:
I noticed the lag introduced in 0.4.4.8... I'll give 0.4.4.9 a go and see how she runs.
[Captivate Android Development] aalh:
noticeably snappier

using bfq at the moment

zram still at stock settings
[Captivate Android Development] sinichi21:
finally the proximity on call is fix :D, been playing with zram lately been turning it off and on to see, seems to me that when the zram is off it tends to free more ram but im experiencing lag time to time but with zram on its tends to free ram but less than when its off and its less lag from time to time when its on for me.
[Captivate Android Development] bferguson:
I really liked the Talon logo boot screen from .4.3, was sad to see it missing in the new one. Please consider bringing it back.

It was cool and had that pro/official look
[Captivate Android Development] irishvandal:
+1, however, i am going to guess that with these runs the default Talon boot will be on hold till a official public release comes out.

Exists,

on the subject of boot screen. i have notice ever since the loading bar has been put in place that the boot screen itself flashes the screen twice in the beginning. this is even the case with the BETA boot screen. not sure if you are aware.

two cents, take it or leave it. but i will be rev'ing Talon-Nucleus either way.
[Captivate Android Development] Sqb:
+1 for the return of the"talon" boot. New test with vr sched. Zram@"0" and phone is humming along zero lag. I think you guys are about to have a great breakthrough. Especially with that "gamechanger" you said you had planned. Can't wait to see. Thanks for all your hours

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] existz:
Ah yes, forgot to mention that proximity sensor could possibly be fixed now with latest changes from infuse sources...let us know your results
[Captivate Android Development] topiratiko:
I like the new kernel splash. Old talon boot was a tad plain. Zram turned off hummin along flawlessly

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] lospulpo:
Hey I've noticed that light sensor only reports values of 6, 5000, 9000, and 15000

Using an app called Total Screen Control that has a "Dynamic Screen Filter Mode" - basically puts a darkness filter on the screen based on light sensor values. (to save battery life with AMOLEDS)

During lots of usage it always feels like there should be a value between 6 and 5000. Any chance this new update will affect that? Gonna flash anyways to find out but thanks!
[Captivate Android Development] demarton:
0.4.4.9 fixes stuttering in games for me, it was first started in 0.4.4.6.

Proximity sensor... the jump in brightness is still too much, but at least is not erratically jump without any change in light, going manual for now.

Will keep on monitoring memory leak.. we'll see in next hours..
[Captivate Android Development] topiratiko:
After disabling zram all my memory issues r gone!

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] tmng95014:
+1 10 chars
[Captivate Android Development] Koizuma:
So far the new test build is running really smooth the lash seemed to disappear, one question though when you flash a new kernal does it also flash a new ZRAM file?

Swyped from my SGH-I896 using XDA App.
[Captivate Android Development] Sqb:
If it's worth anything the bfq scheduler us working a lot better than it has in previous builds. Better than vr on my phone which has always been my choice. Great work!

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] bferguson:
I think mine is still set to SIO, but either way, no lag here. Just what we all expect from such a fine dev. Great work!
[Captivate Android Development] shane87:
What do you mean, does it flash a new zram file? If you are talking about the zram modules that control zram in the kernel, the answer is "technically" yes, since the zram modules get rebuilt with each build. If you are talking about the file that the swaps from memory to zram go into, the answer is slightly more complicated. Any time you reboot the phone it rebuilds /dev/block/zram0, assuming you have zram enabled, so yes, flashing a new kernel will cause you to have a fresh zram partition, but so will simply rebooting the phone.

As a side note to those who are interested, zram is stored in ram. It is not a traditional swap file/partition on secondary storage (i.e. flash memory, sd card, hard drive, etc). Zram simply copies information from a location in main memory, compresses it, and stores it back in main memory until it is needed again. The effect is to increase available ram, since unused info in memory is being compressed and takes up less space, giving more space for the info that is being used.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] sstarre:
I think he might be asking if the ram.conf file is overwritten.

I know that I set ZRAM_SIZE=0 when I flashed 0.4.4.8 and it stayed with subsequent flash to 4.4.9.
[Captivate Android Development] Jep56:
Was running 0448 and had massive lag, and went back to 0446, which runs great, now on 0449 and it flies, no lag! Great job
[Captivate Android Development] Jep56:
Maybe a dumb question, but, how do I get to this setting on my phone? Root Explorer? If so, what folder is it in?
[Captivate Android Development] agaruba:
How exactly do we disable zram because when I look in the file there are two instances of it. Do I change them both?
[Captivate Android Development] rajendra82:
There's only one line that you'd need to change in the ram.conf file. There's another line below it that mentions zram, but if look closely, it is in the comments section mentioning the old preset 7 settings, and starts with a # symbol.
[Captivate Android Development] Jep56:
How do you get to this file to edit it?
[Captivate Android Development] chickelnoodensoup:
Use root explorer and navigate to /etc/ram.conf
[Captivate Android Development] Jep56:
Thanks! I appreciate it!
[Captivate Android Development] slayp00n:
When can we get a 1.6ghz build again.
[Captivate Android Development] xThe Enforcer:
TalonDEV 0.4.3 352MB 1200MHZ with lagfix on Serendipity = pure win.
[Captivate Android Development] demarton:
sad to report, after running 0.4.4.9 for a while, 12+ hours.

Lag or to be exact, stutter in games is back, any kind of racing game is unplayable, asphalt 6, GT, falling fred, etc, massive stuttering.

amount of free ram has been not too bad very rarely dips <30.

zram=0, continuum 6.1.
[Captivate Android Development] H3llstorm:
Does it start after running for a number of hours? I just played Asphalt 6 with no stutter.
[Captivate Android Development] existz:
Yea the "lag" after long uptime is still there, still working on it. But what I ment for feedback was the lag introduced in 0.4.4.6, most stated usually right after boot or not to long after . This should be gone in 0.4.4.8
[Captivate Android Development] Jep56:
I had lag from the very beginng with 0.4.4.8, but not with 0.4.4.6, and have been running 0.4.4.9 for abour 5 hours w/o a hitch....so far!
[Captivate Android Development] tallsilver:
.9 running fine so far for me!
[Captivate Android Development] Koizuma:
yeah i was talking about the ram.conf i was really tired at the time of the posting and couldnt for the life in me remember the files proper name lol

guess i'll just have to give it a look sometime and see
[Captivate Android Development] TonyStark R.I.P.:
Well 4.9 seems to have fixed prox sens for me.

Now if you could just write a subscript for batt drain, I'd have to nominate you for the Nobel;)
[Captivate Android Development] alexige:
Installed .9 around 11pm last night and left phone on charger woke up at 7:30am with some lag on use and used sporatocally down to 70% which isn't alot of use for me and had serious lag by 12:10pm turned zram off for the first time ever and still some lag even initially. More lag on this version than any others I feel. Battery seems to not be as good on recent tests as on most recent stable release.

On .9 test the light sensor seems much more severe on changing screen illumination even when in the same place.

Hate to say it but im thinking ill go back the stable release for now
[Captivate Android Development] Koizuma:
so far on the .9 everything has been pretty good, light sensor is much better, and my phone only lost 10% over night which isn't to bad. lag to seems to have cleared up as well for me
[Captivate Android Development] agaruba:
Thanks!!!
[Captivate Android Development] keller.jeff:
I have the charging bug for the first time on my phone. Pull cord and it drops to 80-90%

With .9

Sent from my GT-I9000
[Captivate Android Development] deltatyger:
Just had a low battery reboot during phone call with 0. 4. 4. 9 battery was around 25% charge left
[Captivate Android Development] existz:
Are you able to reproduce it? Also anyone else able to reproduce it?
[Captivate Android Development] deltatyger:
Actually this was my 2nd time, I wanted to confirm before posting and it happened again
[Captivate Android Development] Peaster111:
Been running 4.4.9 since last night... The lag exists describes (which I had badly) appears gone.

The prox sensor now works perfect. I don't use auto bright.

Still no phone call reboots for me since 4.4.6.