yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] kodos96:
What app are you using for killing all apps and checking ram usage? Try using System Panel, and when you think you're seeing the memory leak, look on its process list at the bottom under system processes and see if you see a process called android.process.acore - I'd bet that that's where the missing 50mb of ram went. If that's the case, then it's not actually anything to worry about, since that process will get killed by LMK when needed, just like a user app.
[Captivate Android Development] mrhaley30705:
I usually use TaskKiller by AxDroid,LLC. I don't have the auto kill feature configured, but the widget allows for a kill all and also monitors amount of free ram. I will try System Panel.

Any ideas about my Call Settings problem?

EDIT: Post #3130
[Captivate Android Development] eliminat:
What I've been seeing hasn't been a memory leak, but more of a decrease in app management. Running the same apps, Froyo with Onix+S6.4 seemed much better at managing background apps, swap, memory, etc. It stayed responsive the entire time.

So far with Gingerbread, Talon+S7, I start with even better responsiveness, but it gradually loses responsiveness, no matter how much "free RAM" it claims to have. I can tell my phone to kill all apps**, but after about 2 days it becomes laggy* enough I have to reboot my phone, which I never had to do with the Froyo versions.

Again, this is with the same apps with the same settings, only difference being the kernel/ROM. It does not seem to be a memory leak, as the amount of available RAM seems to only mildly affect it. Again, this is my experience, and I don't know if this is the "norm".

* Laggy being takes longer to switch homescreens, start apps, general responsiveness.

**I don't run a Task Killer app, but I use the Task Manager, and the Task Manager from Go Launcher X
[Captivate Android Development] FocuseD83:
@eliminat, I have a similar setup with go launcher ex. I've encountered the same types of problems that you have, and I think it's the norm. But memory leak is the only thing acting funny with this kernel. Love Talon, and I'm sure with some more testing, exists will perfect it.

Sent from my Gingerbread Cappy
[Captivate Android Development] shane87:
I am seeing the same issue with call settings staying in memory after someone hangs up before I do. As for the cause, I have no clue, and can't really do much testing until next week. As an interim fix, I use System Panel to find the PID of call settings. Then I open my terminal emulator, type su then hit enter to get root, then type "kill " and hit enter. Of course, replace with the actual PID you get from System Panel. This WILL kill the process, and it does not automatically respawn.

On another note, I have been watching memory usage, and I have noticed that I have a non-system process, something to do with bt, can't remember the name of it, that ALWAYS runs, and I can't even use the PID and "kill" command to kill it. It gets killed, but automatically respawns. The weird thing is, I do not use bt, I do not have bt enabled, and I have never used bt, or even paired it once, so why is the bt app running? Not a huge deal, more of a curiosity.

[EDIT]The name of the bt app is BrcmBluetoothServices[/EDIT]

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] mrhaley30705:
What's the best way to determine which process needs killed? I am not sure which one holds call settings.
[Captivate Android Development] -Thrive-:
I think I have experienced actual memory leak. I boot, kill all tasks and look at available memory using Process Monitor Pro. Several hours later, I kill all tasks and available memory has decreased. On the other hand, if there are system tasks that are not being killed by this method, that could account for memory decrease. I have installed System Panel per your earlier suggestion and will try using that instead of Process Monitor Pro to see if I get different results. I see that System Panel specifically allows you to kill excluded apps and system apps so I will kill everything and compare. Not sure what levels Process Monitor Pro kills.
[Captivate Android Development] geokilla:
Then I guess I got the wrong interpretation of memory leak as that is clearly not what I am experiencing. What I'm trying to say is that lately with Talon, apps keep on closing by itself with no warning whatsoever such as Messaging, Browser, and music when I change volume via my car's BT. Even if I just press the home button to hide them, the apps act like they are closed and when I open it up literally a minute later, I have to reload everything again. When I was on Froyo running Speedmod or SuckerPunch, I never had this problem.
[Captivate Android Development] manny05:
Im using advance task killer.

personally after I restart my phone I have about 150mb free. After opening some app like facebook. Twitter. Google+. I usually hit the widget to kill those apps. I do so because I notice my phone lags and memory is low. Even after I kill all the apps my memory is as low as 60-90mb... at which point I check my task manager and see if anything else is running...then I restart my phone
[Captivate Android Development] rlorange:
The gingerbread sgs taskkiller us not as thorough as froyo. It doesn't kill off background service apps as aggressively. Not talon related

**Simply Honey3.9, Talon 0.4.2.5 kernel1.3ghz**
[Captivate Android Development] manny05:
True. But I also went into setting, application, running services and close any running apps. Same results...
[Captivate Android Development] topiratiko:
@ kodos

Ever since ive implemented the settings i initially set with autokiller memory optimizer to etc/ram config every time i check my ram its hovering right around 265-270. granted its only been 2 days but i haveny had any lag episodes..another thing.....i uninstalled some sns app which i saw as constantly restarting under running services....that may be an issue

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] rlorange:
Even running services seems to be missing some items in gingerbread.

I think there are deep fundamental differences in how the two versions handle ram and app and minfree so I don't think they can be compared directly.

Take third party launchers for example in froyo they ran as any other app showing up in taskkiller and when clearing ram l2 the launcher would be killed. In gingerbread my adw launcher is treated like a native app and does not get killed with a l2 ram clear.

**Simply Honey3.9, Talon 0.4.2.5 kernel1.3ghz**
[Captivate Android Development] chappatti:
Talon 0.4.2.5 ?? Can you clarify? Thanks.
[Captivate Android Development] pikachu01:
Test version of the kernel. Only for beta testers.
[Captivate Android Development] RashaMatt:
+1 same experience here. Difficult to track what's causing it, and who's using how much memory... or if that's even really the issue :\
[Captivate Android Development] rlorange:
Beta tester kernel is currently 0.4.2.5. They're not available to the general public sorry... probably should tasked it off my signature

**Simply Honey3.9, Talon 0.4.2.5 kernel1.3ghz**
[Captivate Android Development] H3llstorm:
I wasn't trying to be a **** either, which is why I didn't say you were wrong, just that I wasn't noticing any problems.

Perhaps it's because I'm not using ridiculously high values.

With these values in Autokiller Memory Optimizer, what values should I plug into /etc/ram.conf?
[Captivate Android Development] Holmes108:
Well, all I know regarding the "memory leak", is that when I boot up, I'm generally at about 240MB used (out of 350).

Throughout the day, that number goes up and up, even if I "clear memory", using the built in task manager that comes with stock (I think it's samsungs). If my phone is on over 24 hours, I can't get below 300MB used, despite hitting "clear memory" or ending processes in the app menu.

It's one thing to say it's Androids memory management "doing it's thing", but the problem is that the phone is noticeably more sluggish at this point.

Now, it's never an issue for me to reboot a phone every 24 hours... in fact it's often been recommended anyways, even for dumb phones. But it would be nice if this behavior was improved.
[Captivate Android Development] ap89b:
Im not sure if this is a rom or kernel issue, but is it normal to have android os to have such a high percentage of battery used? This only happens after a while without a reboot.

Running continuum 6.1 with talon .4.1
[Captivate Android Development] Holmes108:
Definitely not normal. I've never seen mine more than 10%. It's usually more like 4-6%.
[Captivate Android Development] topiratiko:
Look for sns app under running services....if it says restarting thats prolly it. Uninstall

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] topiratiko:
+1 id like to try this setting as well

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] ap89b:
Thats the thing I have sns app frozen so it can't be that.
[Captivate Android Development] topiratiko:
Buddies now widget gave me problems also

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] kodos96:
Yeah, that annoys me too. Even worse is that there are two other bluetooth related processes, called something like bluetooth sharing and something else I can't remember, that always run whenever you have bluetooth enabled. Those two I've managed to disable by freezing them in titanium backup, and it's seemed to have no ill effects on normal bluetooth usage (I think they are only needed for things like file sharing over bluetooth)
[Captivate Android Development] kodos96:
It doesn't seem to base its decision of what to kill on oom_adj levels, it just kills everything that's a non-system process (except for things that have been specifically excluded). That's why android.process.acore doesn't get killed even though it's oom_adj level should be in the LMK-killable range.

So yeah, like I told the other guy, look in system panel for android.process.acore - I suspect that's what accounts for the difference in free ram.
[Captivate Android Development] sinichi21:
just want to ask existz does this suppot Call audio through dock? like excalibur has?
[Captivate Android Development] jcr81:
Any significant performance difference in Nexus S driver and Froyo driver? I really don't care about KTLO so I'm hesitant to flash the update if the touchkey performance will suffer as a result. Thanks!
[Captivate Android Development] existz:
Yes it includes all of xcals fixes

I havent noticed any difference
[Captivate Android Development] froli13:
Is there a fix for charging problems?

I let the phone charge overnight and when I woke up the phone said it was fully charged but when I unplugged it immediately drops to 88%

Any ideas?
[Captivate Android Development] existz:
No, seems to be a gingerbread issue...happens with multiple roms and kernels, some experience it...some dont.. Mine doesnt drop below 92ish
[Captivate Android Development] timn2bama:
I cleared the battery stats in cwm3 menu and rebooted seems to help.
[Captivate Android Development] kodos96:
Yeah, that's what it looked like to me too... although the apps description in the market says that it does support gingerbread.... I suppose I should file a bug report with that author.

In the meantime, does anyone know if there are /proc entries or something where I can control the eq manually?
[Captivate Android Development] froli13:
Thanks for your answers. I will see if happens again. Yesterday was the first time.

It it happens again I'll try to wipe battery stats, worth trying.
[Captivate Android Development] sinichi21:
dont know it its a fix i saw it on continum changelog Fixed battery charge issue (maybe..). If not fixed, try the Flight mode for 15-30 sec while charging
[Captivate Android Development] Time_Zone:
No, the continuum fix doesnt work either. Flight Mode workaround works though.
[Captivate Android Development] rons_sacramental:
Can anyome tell me which kernel i should flash .

Talon.tar with debug enabled

Or

Talon.tar debug disabled

Thanks and anyone kind enough to also say whats the difference between two. :-)
[Captivate Android Development] rjayflo:
Flashed your kernel from excal's with no problem. Put up a score of 1040 with excals...and then 1460 set at 1ghz...2060 at 1.2 ghz. This kernel is blazin'!!
[Captivate Android Development] existz:
Read the OP...one has debug (logcat enabled) the other doesn't...its up to you which one to flash. If you use apps that rely on logcat or you use logcat yourself to debug, then use the debug version. If not, use the one without it...saves some on battery
[Captivate Android Development] Dlev7:
Hey existz can I flash this through SGS Kernel Flasher or iis it frowned upon?

Thanks
[Captivate Android Development] existz:
You can, but Odin is highly recommended and preferred
[Captivate Android Development] Dlev7:
Alright thanks. I'm on darky 10.0 RC5 and I wanna use contiuum but I have to flash this kernel to obtain CWM3
[Captivate Android Development] existz:
I would recommend flashing with Odin just to be safe
[Captivate Android Development] sjavvaji:
is anyone else having trouble getting the oc/uv settings to stick through the boot?...i haven't been able to do it...
[Captivate Android Development] existz:
1) check and make sure its writing S_volt_scheduler to /etc/initd/

2) try using the busybox app and replacing your busybox version...this happened on earlier test releases and replacing busybox fixed it
[Captivate Android Development] shane87:
Finaly released a final version of vcex, and now I am on gb!! Its amazing!! And I haven't converted to ext4 yet, and I am still runnin talon 0.1.1, as that is what perception ii comes with. Can't wait to flash talon 0.1.3 and get some oc, plus I am going to be converting to ext4 soon. Can't wait!! Awesome work existz, and ytt3r!!!

ROM: Perception II beta 1

Kernel: TalonDEV 0.1.1 Voodoo color, voodoo snd v8

Modem: I9000 ugjk4

HW Build Number: 1101
[Captivate Android Development] kodos96:
Heh, so then what you're saying is that the LMK thresholds are too LOW for you, while everyone else (at least the most vocal faction anyway) seems to think they're too HIGH. Just goes to show that you can't make everyone happy.

Check your running services and see if there's anything using ram that you can uninstall or disable, and try running the bigmem version of the kernel if you're not already.
[Captivate Android Development] kodos96:
Yeah, there are some significant difference between froyo and GB in how the system manages memory, but the specific thing you're talking about is just that in the newer version of the samsung stock task manager, it specifically excludes your launcher.

Try System Panel - it'll actually show you everything.
[Captivate Android Development] kodos96:
Well yeah, if you lower your LMK thresholds, it'll definitely increase the amount of ram you have free, nobody's questioning that... it's just a question of whether or not that's a good thing or a bad thing.

As far as the SNS app, does anyone know what SNS actually is? I've never been able to get a clear answer on that. Mine also shows as "restarting" in the control panel "running services" page, but I'm not sure why... looking at logcat it doesn't look like it actually is restarting constantly, so I don't think that's a source of cpu usage.
[Captivate Android Development] kodos96:
Yeah, the stock task manager "clear memory" only kills user apps, not services or anything like that.... but if you can't get below 300mb used with "clear memory", then you must have TONS of services running. I'd recommend you figure out what services you have running and see if there are any you can live without.
[Captivate Android Development] Holmes108:
Yeah, I haven't investigated much with other 3rd party task apps... but what I don't get is why it changes over time. I shouldn't have anything special running... It's only over 300MB after many hours. Maybe some apps I run throughout the day are leaving processes behind.

I'm not sure exactly what the stock task manager closes... generally I go in there, and maybe have 2 or 3 apps running under "active applications"... but under the "RAM" tab, I hit the "clear memory, and it will say something like "9 apps closed"... But it becomes less and less effective throughout the day.
[Captivate Android Development] geokilla:
Not necessarily. It's some sort of bug or something. It happens when I first boot up the phone as well. As of right now I have 256MB/340MB of RAM used, yet the phone still doesn't seem to hold anything in memory. I used to be able to open many things in SuckerPunch, such as Browser and Messaging both at the same time and it'll stay in the RAM. With Talon, I open one, the other gets closed.

Maybe I have to change to Darky's kernel... I didn't like Darky's though. Can't remember why I didn't like it >.>

That just may explain my complaints.
[Captivate Android Development] Sqb:
@kodos: thanks for the heads up on system panel. Best monitor/killer I have seen. Most in depth and like you said good to keep an eye out for run away system process. Also love the battery temp and voltage bar.

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] existz:
So, im thinking I might start doing OC versions a little different with upcoming release..im thinking about having the normal non-oc version, then an OC version but it will be tegraks oc until I can get my module built. What it will be is, 100-1000 then you can select 1.2, 1.25 and 1.3ghz... (or even higher if you buy his app).. there will be UV support, unlike running tegrak on a stock kernel or any non-oc kernel ..so technically nothing will change..this way I don't have to compile and upload so many versions..and to be honest this is the main reason updates take so long, so if I only had 2-4 builds to upload (non-oc and oc, then bigmem and non-bigmem) I would be able to get updates out quicker. Currently I have 12-14 versions I have to upload, including i9000, ... so reducing the number of builds would def mean more/quicker updates. But if I do this, the app will be included in the kernel, so you wont have to dload and install it..etc.

Sent from my SGH-I897
[Captivate Android Development] pikachu01:
Good thinking existz. Is tegrak replying to his PMs yet about his OC modules?
[Captivate Android Development] manny05:
Sounds good. :)
[Captivate Android Development] leoriver42:
Very nice! Your hard work is always most appreciated :D

Sent from my Samsung Captivate running Apex 8.2
[Captivate Android Development] sremick:
The particular drastic one I'm dealing with and that I think is the one that everyone is referring to I did not see until I moved to Android 2.3 (Apex). On all my 2.1 and 2.2 ROMs, while certainly a reboot would make things feel snappier, I wasn't effectively forced to reboot once or twice every single day just to keep my phone usable. It was a big change... before, I could run for days and days and be fine without rebooting.

We're on the same page

Definitely. Using tools like OS Monitor is unable to attribute the memory to any particular app/process... in fact, it tends to show individual apps/processes using less RAM than the same ones did immediately after a reboot. Yet the total free memory will decrease from as high as 140MB down to below 40MB. You can always tell as the phone gets laggier and laggier... more and more delays opening new apps and even just working within an individual app.

I don't use any auto task killers, although I do have ATK for occasional manual use when things get bad. I don't use it regularly though, only as a last resort before rebooting (and also immediately right after reboot, for the stuff that Startup Cleaner doesn't seem to catch).
[Captivate Android Development] topiratiko:
Try this ;)

Sent from my Apex Blue 2.3.4 Ext4 equipped Samsung Captivate.
[Captivate Android Development] kodos96:
Well that's definitely not normal behavior you're describing... are you able to reproduce that behavior every single time? Because Talon, since it uses ZRAM, and has higher LMK thresholds than most kernels, should be much better in this respect (keeping apps in memory) than other kernels. When I try to open as many apps as possible, just to test the LMK, I can usually get 15 or more apps open simultaneously before any start getting killed. That's with small apps of course - if one of the apps is something big, like a browser with several tabs open, obviously its gonna be less than that, but it shouldn't be getting killed instantly as soon as you switch away from it. I use firefox, which is significantly more memory hungry than the stock browser, yet I'm able to keep it in memory a good amount of the time (on Talon - not on other kernels).

So I'm not sure what's going on with you - maybe you have a bunch of services running?
[Captivate Android Development] kodos96:
OK, but if you're just looking at open apps in the stock task manager, you're not getting the full picture - there's usually tons of stuff running in the background that the stock task manager doesn't tell you about. Try System Panel and look for running services you may not be aware of, and look for android.process.acore under system processes - I suspect that's a large part of where the missing ram is going. And then try doing a "kill all" in system panel and see how much ram you have free (note: I'm not saying that you should have to do a "kill all" under ordinary circumstances just to speed your phone up, I'm just saying it's useful for the purpose of measuring free ram, looking for a memory leak).
[Captivate Android Development] kodos96:
Topiratiko, these settings may work for you, but I'd appreciate it if you didn't keep recommending them to other people - they're going to be really bad for most people. For one thing, they're going to end up killing your launcher constantly - YOU might be using a launcher which is able to pin itself in memory and not get killed, but most launchers aren't able to do that, so using these settings is going to result in mass frustration for most people.

Also, I suspect that if you took a look at your logcat, you would see that your services are constantly getting killed and restarted by that 10240 threshold you have on the adj level 3 classes. You may not notice it, cause its happening under the hood, but it'll cause increased battery drain.

I would recommend to you that you change all those 10240's back to 5120 and just keep your changes to the last two levels - it's really just HIDDEN_APP and EMPTY_APP that are having the effect you're looking for (i.e. killing apps quickly). The others are just related to killing SERVICES, and you REALLY don't want that - when services get killed by LMK they just relaunch automatically, so you're not actually freeing any ram, just killing performance and battery.

To everyone else reading this, please don't use these settings. If you want your apps to be killed quicker, you should change HIDDEN_APP_MEM (and the associated value in LMK_MINFREE).... but don't start right out by setting it to something crazy high like Topiratiko's settings - start with something more reasonable like maybe 8192 or 9216 (that's what I'm going to be using in the next talon release I think), and if you still want it higher, try notching it up gradually in increments of 1024 until you find a value that works for you.
[Captivate Android Development] sremick:
Oh, I know. ;) That's why I said I was using OS Monitor. I also have several others installed... including System Panel so I'll poke around with that some more too.
[Captivate Android Development] kodos96:
Yeah, OS Monitor is great for when you want a REALLY low level view of your processes, but since it mixes together your system processes and your user apps it's not very useable for just checking out what apps/services you have running.... System Panel seems to be about the right level of abstraction for what we're looking at here.