yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] minlee85:
2 out of 3 times, "clear zram" shuts off my phone....even when it does not shut off the phone, I don't see any improvement on lagginess... other than that, it is a great kernel..I keep coming back to it even with the memory leak.....can't wait to see the fix for it... I really appreciate your effort, existz!!! :):):)
[Captivate Android Development] TonyStark R.I.P.:
Hey E, do you and your posse have any plans for AT&T SGS ll?
[Captivate Android Development] existz:
Probably not... Which currently the only people working on Talon is me and shane87, havent talked to kodos in awhile, not sure what hes up to, and not sure what ytt3r's plans are.. My next device will probably be Nexus Prime
[Captivate Android Development] bkimbel:
Agreed. "Clear ZRAM" reboots my phone, too.
[Captivate Android Development] shane87:
Hmmm, that's very odd. I have only used "Clear ZRAM" a handful of times, but I have never seen it cause a reboot. It could be due to the sudden removal of needed data from availability, and the resulting page faults, but I don't think that would cause a reboot. If you guys having reboots using "Clear ZRAM" could do me a favor, open a terminal emulator and type:

1. "su" then hit enter

2. "clearzram" then hit enter

Obviously, don't put the quotes in. Anyway, this is exactly what mf should be doing. If calling clearzram this way causes a reboot, then it is in the clearzram binary, and me and ex will have to look into it. Otherwise, I will need to fix mf.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] Sqb:
I had it reboot last night when I tried the button. so I tried it through terminal emulator and I don't know if it worked but it didn't reboot. Thanks for all the hard work and for putting out another great release.

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] topiratiko:
Ive used it 4 times. Rebooted once. I dont view that as an issue.

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] Sqb:
Especially if reboot is the next option

Sent from a rock on fire qin the middle of the sea
[Captivate Android Development] holeindalip:
Ive used clear zram option a couple times but no reboots.
[Captivate Android Development] bkimbel:
I ran it from the script manager console and this is what I got :

exec sh -c "cd '/mnt/sdcard' ; exec /system/bin/sh"

# h -c "cd '/mnt/sdcard' ; exec /system/bin/sh"

# su

# cd /bin

# clearzram

clearzram: not found

# ls cle*

clearzram

# . ./clearzram

./clearzram: 1: Syntax error: word unexpected (expecting ")")

#
[Captivate Android Development] ugoff:
I went to the power menu by holding the power button down and tapping 'shut down'.

I was trying to shut down the phone so I could charge the battery to match the percentage reported in the OS as close as possible, then boot up into recovery and delete the battery stats from there.
[Captivate Android Development] pikachu01:
Ahh .. never encountered that before. Never heard of this happening before even. Not sure what could be the problem. Try a full reflash if you can to pinpoint this.
[Captivate Android Development] shane87:
Hmm, very odd. I just ran clearzram from android terminal emulator, and I got errors about not being able to insmod lzo_compress.ko and lzo_decompress.ko, but that is because thise modules are not rmmod'ed first. Then it reported a successful zram initialization, success on mkswap, success on swapon, then I got the message "swap cleared!" I know that existz had had some difficulties with other binaries throwing errors similar to what you reported, but I have never seen clearzram show that error.

As far as the efficiency of clearing zram to fix lagginess, it helps if you drop caches as well, although even that may not help. The benefit of clearing zram is that stale pages can accumulate in zram, and by clearing zram it frees up the space that those stale pages occupied. Another note is that clearing zram may not show immediate improvements. This is due to the nessecity of re-fetching data from NAND stirage, and swapping unused pages back to zram, so it may take a few minutes for the system to respond and level back out. Unfortunately, the only way to completely remove lag is an eventual reboot. At least until we can track down the memory leak, which is proving to be extremely elusive.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] FocuseD83:
Is it wrong that I got a boner from this? Lol

Sent from my Gingerbread Cappy
[Captivate Android Development] Kyuta Syuko:
I agree with this post. Like...

100, 200, 400, 800, 1000

100, 300, 600, 900, 1200

100, 300, 600, 1000, 1400

100, 400, 800, 1200, 1600

or something... (Number of levels pulled from Tegrak's OC app)
[Captivate Android Development] pikachu01:
One thing to consider is that these settings will certainly break support of Voltage Control/Control Freak etc.
[Captivate Android Development] existz:
Well, the module will only replace L0 (max clock), I cannot change the lower freqs based on oc version...so whatever I make the lower freqs, they would be the same for 1ghz-1.4ghz... there's alot of users that prefer the stock layout of frequencies, so I will be keeping them the same.. only will max clock be able to be changed... by default the module will be unloaded and max clock will be stock 1ghz..then if you want to oc, you will be able to load the module, which will be adjustable from 1120mhz - 13/1400mhz... so there will only be one version of Talon (2 actually, non-bigmem and bigmem), then if you want to oc, load the module, if u don't then its stock freq layout by default ...and there will be an app to enable/disable oc and select higher oc
[Captivate Android Development] Kyuta Syuko:
I did not consider that, but then again I didn't think the apps had that kind of limitation.

I see...
[Captivate Android Development] pikachu01:
I would think that they have, as they have to detect UV values at each stage. If they used frequency as a yardstick to compare, they would be confused if suddenly a 300MHz or 600 MHz came up. If they are using another algorithm, then I'm not sure.
[Captivate Android Development] ugoff:
I ended up flashing Apex 10.1. It doesn't seem to have the issue, but it could have been something I did (or didn't do) to the last flash.
[Captivate Android Development] existz:
Actually, voltage control wouldn't have any issues, as the frequencies/voltages are defined in the source, then exported to a sysfs, voltage control then reads from those... so if someone was to change the layout of the frequencies, there's various places in the source you have to define them, then VC just reads the contents of the files...for example, there's various files that gets read, like /sys/devices/system/cpu/cpu0/cpufreq/frequency_voltage_table,..states_enabled_table, ..UV_mV_table, .etc..which is apart of the oc code.. Then VC knows which states are enabled..etc..I don't know the exact process of voltage control, shane87 might need to chime in, but you can change it...like with my Onix froyo kernel, I added 600 and 900 step, the same goes for OC frequencies, your just adding additional code to the source, then you have to adjust the layout for the sysfs file so VC reads it for the additional steps...but long story short, you can make the frequencies any numbers, as long as you set them up correctly in the source ..they are not defined in the app itself .. And this is the main reason i only recommend Voltage Control/Control Freak, as the whole OC/UV code is setup for Voltage Control through various functions and sysfs files.., apps like SetCPU does not use these.

But the problem with doing it this way is, 1) I cannot make certain frequencies depending on the OC, because only the max clock is getting changed with the module, it doesn't communicate with anything else or read anything else, just max clock...and 2) alot of people don't OC, and prefer the stock layout ... so I'm keeping the frequencies stock except max clock for those that want the extra option.
[Captivate Android Development] shane87:
The way voltage control/control freak works is that, at app launch, it reads certain sysfs files. These include the ones existz mentioned. Anyway, it then uses thise files to determine what frequencies are available, and what the default voltage is for each frequency. Then it populates its lists. So if uv_mv_table says that you have 100 300 600 900 1200 1400 frequencies, with default voltages of 1050, 1100, 1200, 1300, 1350, 1400 mv, it will show the frequencies available, and set the max value on the undervolt sliders to the proper default voltage. It also reads in the current voltage, so that it can set the position of the uv sliders appropriately. Any changes are written back to the syafs files when apply is selected, and written into an initd script when save is selected.

So, changing the frequencies would not affect the operation of voltage control/control freak. However, if an initd script is left unchanged, it could apply inappropriate uv values to the wrong frequency.

For example, say you set up an aggressive uv scheme with stock frequencies. If you save it to be applied at boot, then decide to apply an oc of 1400 and forget to reset the uv values, you could have an unstable phone that may not even boot. This is because the initd script may be applying a uv to the top frequency of -100mv. 1000mhz may be able to handle -100, but 1400mhz may not be able to handle that much uv. Also, the initd script will limit the max clock to 1000mhz, but if there is no 1000mhz frequency, it will default to the next lower frequency, say 800mhz.

More than likely, when I write the app to load/unload the oc module, I will have it erase any oc/uv initd scripts, just like talon does when you flash it.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] tazman171:
I tried running it from terminal emulator and also got the message of "clearzram: not found". :cool:
[Captivate Android Development] shane87:
Yeah, I made a mistake on the instructions for calling clearzram from the command line. You have to call "/bin/clearzram" Or you can cd into /bin and call ./clearzram. I forgot that /bin is not in the PATH, so you have to give the full path of any executable located inside /bin, which includes clearzram.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] goodolsen:
Just tried a clear zram and it rebooted my phone. Happens about 1 in 3 times. Guess I'll just not use that feature anymore.
[Captivate Android Development] keitaroguy:
I'm getting the charge issue, Also my phone restarted around 30% battery life then dropped to 1% then it "Charged" (WAS NOT PLUGGED IN) it went from 1% to 8% before it started to drain again. wtf? I've never seen this before????? Help?
[Captivate Android Development] topiratiko:
Im sure itll be fixed in next release

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] topiratiko:
You, my friend, need to calibrate your battery. If that does not fix it, you need a new one.

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] geokilla:
Smartass governor doesn't work. Keeps on reverting back to ondemand. Doesn't better though because pikachu's tweaks don't work with smartass anyways unless I modify them.

Sent from my Samsung i896
[Captivate Android Development] existz:
Smartass works, make sure you don't have any scripts or screenstate scripts that's setting something else...remember, if your using 3rd party scripts I cannot support it
[Captivate Android Development] reinbeau:
I'm sure I'm probably wrong, but I have to ask here, as this is the only major change I've made to my phone lately, and the symptoms started up right after I flashed the latest update to 0.5.1-RC1 1000 BIGMEM. I am getting a database is full error message every time the media synchs. The little icon shows up at the top, I click on it, and the screen I'm brought to tells me I'm only using 535 megs, with 1.3 gigs free - would the kernel have anything at all to do with this? I'm learning, please don't kill me :o :p
[Captivate Android Development] Kyuta Syuko:
pikachu's scripts automatically set ondemand unless you change it.
[Captivate Android Development] geokilla:
I did. But it was still ondemand when I checked earlier. He said I made the correct changes to the script though so I dunno. Either way, guess I'll just stick with ondemand.

I'm just wondering, but why is that only Talon seems to have the memory bug/leak/whatever? I don't recall other kernels having this problem.
[Captivate Android Development] pikachu01:
Can you attach it here?

Let me look at the entire script just to be sure :)
[Captivate Android Development] existz:
Because the issue is more than likely caused by swap support and/or zram, and Talon is only SGS kernel with swap support.. but we are not sure which one is the culprit, or exactly what in swap and/or zram is causing it..
[Captivate Android Development] geokilla:
Oh I already deleted the 1.3 that I modded. I'll post 1.4 modded to smartass if I ever change it lol.

But before swap and zram, Talon also had this problem so...
[Captivate Android Development] existz:
I don't think so, ...remember, way back earlier in talon, it really wasn't a memory leak, it was more of a lmk issue.. users confused the 2... the lmk settings back then were allowing to much to be open at once., which was causing lag..etc., not enough apps were getting killed,.or wasn't getting killed as often as it needed.. the issue now is that its actually leaking memory somewhere, and after a long up time, its causing lag.. There were alot of false reports about this, but later on the lmk settings were made alot more aggressive, resolving this issue, then probably back in mid-0.3.x there became an actual memory leak issue.. Which kodos was able to eliminate the leak by disabling swap/zram completely in the source (which is not the same as just disabling zram via userspace...as the source is actually compiled based on specific code depending if swap/zram is enabled... so when its disabled, different code is compiled).. but the problem now is trying to find exactly under what circumstance..etc..triggers the leak.. We can disable swap support completely and avoid the problem, but the extra benefits of swap/zram is worth having to reboot daily until its fixed (ie..the speed, being able to store alot more in memory without actually having to have more memory ..etc, which zram is perfect for devices like SGS with limited memory ...for example its not really needed or an issue on devices with 768mb+)
[Captivate Android Development] pikachu01:
I'm testing an LMK setting that would prevent lagginess (memory leak?) for ThunderBolt! v1.5. :P

I'll post it up after I am sufficiently satisfied that the lags are gone :)
[Captivate Android Development] RashaMatt:
FWIW I don't see the memory leak when I run with zram=0 in MF (which is what I normally do).

____________________________________________________________

AT&T Captivate SGH-I897 build 1010, Apex 10, Talon Dev 0.5.1 RC1 1200 BIGMEM kernel, KC1 modem
[Captivate Android Development] topiratiko:
@existz

Was talkin to a buddy of mine with an iphone4 and he said there was a hack to use part of internal sd to expand ram. Is this possible on sgs? Or was he in over his head?

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] Kyuta Syuko:
That sounds kinda like the vRAM/Page File business Windows uses...
[Captivate Android Development] johan8:
Theoretically it is possible to do that.

But beware that your phone will become very very laggy.

You know why ?
[Captivate Android Development] pikachu01:
Sdcard read/write speed is very very slow compared to RAM. It'll kill the access time.

And I would like to announce that I managed to contain the memory leak through some research:

http://xdaforums.com/showpost.php?p=18529320&postcount=288

The result of that is included in ThunderBolt! (my sig).
[Captivate Android Development] sinichi21:
Hi existz so decided to oc more on ny cappy and just want to ask what is the difference on core voltage and internal voltage will changing the internal voltage value will hurt my cappy I'm using tegrak right now
[Captivate Android Development] topiratiko:
Awesome work dude! If i wanna revert i can do a restore right?

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] Darryl Henley:
nice, how do we install supercharger?
[Captivate Android Development] pikachu01:
I posted a restore/revert instruction in the OP of my thread.

You either install Supercharger or ThunderBolt!. Actually, you can't install Supercharger in TalonDev, TalonDev will disable it at boot time.
[Captivate Android Development] existz:
So I'm going to go by what you guys think for default talon LMK settings... for those that have memory leak issues/lag..etc after long up time, try pikachu01s new settings in his thread and then you guys let me know if you want them default or not .. Since I don't have a SGS right now and cannot run them myself, nor benefit for my own use, ill just go by what the majority wants.. of course, I need these highly tested under various circumstances, need different types of users trying them ..etc.. (ie heavy multitaskers, gamers, those that don't do much..etc ..all types) .. and if you guys all agree and want them, ill include them as default in next release
[Captivate Android Development] Boomgawd:
pikachu01s Majic

I can confirm whatever LMK settings are done in thunderbold 1.6 have cleared the leak for me completly. My phone has never been so fast.. seriously.

Apex 10.1 (thanks whatsa)

Talon 0.5.1-RC1 (thanks existz)

Thunderbolt (thanks pikachu01s)

remount script at boot (thanks pikachu01s)
[Captivate Android Development] Kyuta Syuko:
It would be good to know what you do on your phone and how often. Like do you play Angry Birds all day, browse the web while writing a report on the bus to the library, etc. Just for reference.
[Captivate Android Development] Darryl Henley:
installed ThunderBolt over Continuum 6.2.1. i use launcher pro and i lost all widgets and icons. script manager and supercharger did not install.
[Captivate Android Development] pikachu01:
It's a known issue. I did say corruption is a risk with sqlite fsync disabled. Launcher pro might have some special fsync requirements. Try re adding then back and see if it's still getting corrupted.
[Captivate Android Development] Darryl Henley:
adding back shortcuts and angry gps shows as installed but it is not showing in the app drawer.
[Captivate Android Development] pikachu01:
Angry GPS is not shown in my drawer too. Isn't that a hidden app that can only be accessed by a special phone code?
[Captivate Android Development] Darryl Henley:
recreated angry gps shortcut by going to shortcuts -> activities -> angry gps
[Captivate Android Development] pikachu01:
Ok. Any problems so far?

How about a reboot?

Save your configuration first before rebooting.
[Captivate Android Development] justin860:
i'm using thunder bolt.so far so good, i'm a heavy user a lot of internet texting and applications.

which version of talon is best for

j v s?
[Captivate Android Development] pikachu01:
The newest?
[Captivate Android Development] justin860:
I have been having wifi issues with it
[Captivate Android Development] existz:
Talon is always up to date with latest version available, therefor I can only support use with latest version (in this case JVT)...but the only thing in regards to wifi thats been changed in Talon (actually in a very long time), is initramfs updates from Samsung
[Captivate Android Development] pikachu01:
Disable your address reservation setting or set your lease time to something more than 24 hours in your router.
[Captivate Android Development] justin860:
Thanks guys I truly appreciate the hard work
[Captivate Android Development] Darryl Henley:
with thunderbolt, is the supercharger script supposed to be init.d folder? looks like continuum and thunderbolt don't work well together.
[Captivate Android Development] AceofSpades90:
ok so I am running Darky's JVT with KJ3 modem (dont know why i put modem here.. anyways!) on my captivate(SGH-I897). i switched from DarkCore 4.0 -> DarkCore 4.1 (reason: laggy and unstable) -> Semaphore (reason: do not support SGH-I897...) -> Darkcore 4.0 (reason: no support for voodoo colors :o) -> Galaxian (thought but never tried, no support for SGH-I897 again..) -> Talon 0.5.1 RC-1 @ 1 Ghz with Bigmem (reason: looks as if it has all the features from all kernels? and its dev know what he's doing and is helpful.) and now i feel terrible terrible lag that i NEVER in my life felt :/ Is it because of incompatibility with Darky?

EDIT: I've tried restarting my phone several times...

I've heard people using scripts/mods and apps that may help fix this???

So please please please list ALL the scripts/mods and apps you have experienced or think are compatible and might help in anyway(just curious)...

Let me start as i've already done some research on this topic myself but have not tried none of the scripts yet(do not know what they EXACTLY do lol). ok things i found as follows(with their correct file extensions as i downloaded from the net):

Acid Tweaksv6 - Removed Useless Stuff.zip

control-freak-0.5b.apk

Universal Adrenaline ShotvXIX.zip

ThunderBolt-CWM+i9000+v1.6+Talon.zip

V6_SuperCharger_for_Android-update9_beta_6.3.sh (no clue how the hell im supposed to apply this script/mod???)

Universal Adrenaline Shot BL vXIX.zip (not compatible?? the site said nothing about it..)

JournalingOn.zip

(I'll add your's here w/ links if provided :D)

Some of the above scripts overlap on top of each other and that's why i haven't tried them yet :/

NOTE: anyhow, i love this kernel and i understand **** happens. im not blaming anyone though i know as a programmer myself, existz is such a cool programmer and know his stuff. Hands down to his hard work. :)
[Captivate Android Development] existz:
Most likely the dreaded memory leak after long up time...as of this second you got 3 choices....

1) try clearing drop caches and zram in memoryfreak ...sometimes this helps

2) you can simply reboot, problem goes away but later returns after long period of up time

3) use pikachu01s thunderbolt tweaks (use the one designed for talon)... as its designed with talon and swap/zram in mind

#3 is more of a long term fix if none of the other 2 help/benefit you... which I was just talking a couple post back about using pikachu01s lmk settings in next release, but first need user feedback about these settings.. Also, if you mess around with any other memory scripts/tweaks, you have to remember that talon uses swap support (no other sgs based kernel, and most android devices, do not use swap..so all those tweaks were designed for non-swap systems, so the way memory management is handled in talon is completely different) but alot have had success with thunderbolt tweaks, and reporting the memory leak does not happen, so if you don't want to reboot or clearing caches/zram doesn't help, then try those... Which more than likely ill be including only his lmk settings in next release and hopefully get rid of the long up time memory leak issue
[Captivate Android Development] AceofSpades90:
Thanks a lot, but the file i downloaded says ThunderBolt-CWM+i9000+v1.6+Talon.zip which is for i9000? does that make any difference... but again i shouldn't be asking this in the first place.. im running kernel that's reoriented for captivate with I9000 Rom on top of it. nothing in my phone is captivate at its heart without of course the hardware and modem lol
[Captivate Android Development] pikachu01:
Hey existz :)

I'm going to re-do the LMK settings as some feedback I got about it is that it is too aggressive. I'll do it in the weekends :)

Yes, it should work if you follow all the instruction in the OP (original post).
[Captivate Android Development] AceofSpades90:
Thank you :)
[Captivate Android Development] pikachu01:
Why?
[Captivate Android Development] AceofSpades90:
just a quick question... now that google announced their galaxy nexus, will this kernel port important features from android 4.0 (ice cream sandwich) kernel? xD

http://developer.android.com/sdk/android-4.0.html