yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] RashaMatt:
MemoryFreak feedback ( .21)

- The "LMK Settings" dropdown is empty.

- The "Help/Tips" button does nothing when pressed (except flash).

And maybe related:

When I run 'free' it always says 0 0 0 for 'swap', but I never disabled it. Has been like this forever.

If I run "su; swapoff /dev/block/zram0" I get "no such file or directory".

According to Root Explorer, there is no /dev/block/zram0 (surprise).

EDIT: yes, SU is enabled for MF

____________________________________________________________

AT&T Captivate SGS I897, Serendipity VII b.1, TalonDEV 0.4.4.21, KC1
[Captivate Android Development] pikachu01:
Did you enable Superuser for the app? It works fine for me.
[Captivate Android Development] pikachu01:
I tried using ZRAM = 0. No problem for me. You can try deleting ram.conf and letting the kernel regenerate it. (Back it up first in case something goes wrong)
[Captivate Android Development] shane87:
It sounds like mf is having trouble reading your ram.conf file. You can try the above tip, deleting ram.conf and letting the kernel regenerate it. If that doesn't work, I will have to do some digging to see what could be causing it.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] Rrryan2:
.21 1200 with stock LMK, stock scheduler/governor: more of the same good-to-begin-with-but-problematic-later experience I've been frustrated with lately. Gets increasinly sluggish between reboots.

.21 1200 with Memory-Freak Nexus S LMK, stock scheduler/governor: dramatically easier to deal with. Snappier to wake from sleep, handles multitasking well, no lagginess when running multiple applications... Cappy *finally* feels like it's behaving like it ought to under GB. :)

My compliments to Mr. Shane. ;)
[Captivate Android Development] geokilla:
.20 and Darky is fine. There should be Mosaic users who also use Talon .21 and haven't reported a problem either.
[Captivate Android Development] pcguy23:
Trying out go launcher ex

Looks good so far

Had been switching between launcher pro and adw ex previously
[Captivate Android Development] pikachu01:
How did you flash the kernel btw? SGS Kernel flasher?

If you used the kernel flasher, it won't wipe the init.d dir as well as the scripts that you load which potentially might clash. An example is the S_volt_scheduler script that does your OC/UV. As the number of CPU steps are different in different kernels, flashing a kernel over a kernel without wiping the OC/UV settings might lead to this:

Original:

-50mv for 1.0GHz

-75mv for 800MHz

New Kernel

-50mv for 1.2GHz

-75mv for 1.0GHz

Instant bootloop.
[Captivate Android Development] geokilla:
I always flash via Recovery menu, wiping everything before flashing. Never SGS Kernel Flasher. I don't trust those kinda apps. Less of a headache to flash in Recovery anyways.

Anyways I'm back on Talon but MemoryFreak still is coming up blank for me. Guess I'll just use .21 without MemoryFreak for now. It's beta anyways.
[Captivate Android Development] greasyguy:
I just joined the crew and flashed ver. 0.4.3 1200 MHz. Seems nice so far. Thanks to the dev.
[Captivate Android Development] pikachu01:
You should flash the newest test version 0.4.4.21. It's 150% (rough estimation) better than 0.4.3 :)

Edit:

http://xdaforums.com/showpost.php?p=16778328&postcount=4136
[Captivate Android Development] greasyguy:
Will try tomorrow. Had to much bootlooping today due to another kernel I don't want to mention here ;-).
[Captivate Android Development] Fate-Silver:
How to config the MemoryFreak? I have no idea how to do it properly... :(

Can someone show me the BEST configuration for it?

Thanks. ;)
[Captivate Android Development] pikachu01:
There is no "BEST" configuration. You'd have to try it yourself and see how it affects the performance in your phone as each phone has its own list of applications and how they interact with the RAM.

Just in case if you wonder what my settings are:

Stock Talon

Stock Hidden App

Zram set to 160

Swappiness set to 50
[Captivate Android Development] Fate-Silver:
1stly, thanks for the settings sharing.

I read the 1st Page, it says there should be no "RAMHACK" Scripts in the /etc/init.d/? Right?

I wonder if I can disable the MemoryFreak as well as those things related to it.

Because I feel like want to use the V6 SuperCharger Script which is much faster, IMO.
[Captivate Android Development] jswclw:
I am having the same problem. Based on the later recommendation to delete ram.conf I went looking for it to do just that. No luck. Looking in \system\etc I do not see it.

To add a little more insight, the first time I flashed .21 all my widgets were gone when it booted up. I'm using the AOSP Launcher.

So after not seeing ram.conf, combined with the widget problem, I though I would flash .21 again. The widgets didn't disappear this time, but still no ram.conf to be found.

Any ideas?
[Captivate Android Development] pikachu01:
Supercharger is incompatible with ZRAM. You would have to disable ZRAM in the scripts to apply Supercharger. Even then, there are a few optimizations that are done for memory related stuff. You could try disabling ZRAM and swapping and then using Supercharger.
[Captivate Android Development] pikachu01:
Try removing all your scripts in the init.d and reflashing the kernel.

I will upload my ram.conf here in a few mins. You could try placing that file in the kernel (after removing your init.d scripts) and try again.
[Captivate Android Development] Fate-Silver:
It isn't working.

It keep reverting back to STOCK after a reboot. :(
[Captivate Android Development] pikachu01:
Try removing all your init.d scripts and try again.
[Captivate Android Development] Spidious:
So far so good..

Thought I would give it a try again..

Installed Thursday, Is it just me or is it actually louder now ? Is that the Voodoo sound ?
[Captivate Android Development] Fate-Silver:
It's alright(lazy to test meanwhile)... I think I'll just stick with the MemoryFreak.
[Captivate Android Development] jswclw:
Still having troubles here. So the "/etc/init.d" directory should be empty? I have 4 files in there.
[Captivate Android Development] pikachu01:
Yes, try removing all of them (back them up first) and try again.
[Captivate Android Development] jswclw:
I gave it a shot. No joy. Deleted all 4 files from init.d directory (actually copied to a backup directory). Back to recovery and re-installed talon .21. Directory is still empty. Interestingly...it seems pretty snappy now, more so than before. But maybe that's because I just restarted.

Still no LMK Setting choice in the drop-down in MemoryFreak. If I press the dropdown, the whole screen goes dim except for a white box which opens over the ZRAM Size slider. For what its worth, the about in MemoryFreak says 1.10b. Is that right?
[Captivate Android Development] pikachu01:
Here's my ram.conf. After loading it, you should see Memory Freak reporting 160 in ZRAM and swapiness 50.
[Captivate Android Development] topiratiko:
If you guys are experimenting with ram settings...try clicking my signature! I get good results :D
[Captivate Android Development] jswclw:
Now MemoryFreak is working! I did drop the ".txt" from the file name.

Now in MemoryFreak it shows-

LMK Settings: Talon

Hidden: 36

ZRAM: 160

Swappiness: 50

I would assume a reboot is in order. Doing so now. Many thanks.
[Captivate Android Development] mmalka:
I am new to Android OC and UV. So, instead of asking a bunch of basic questions, I will ask just one: could someone point me to posts or other resources to learn about how to do it and the tools available? I read a lot hear about governor and other stuff I have no clue about.

I promise to do my homework if pointed on the right direction.
[Captivate Android Development] pikachu01:
1. Download Voltage Control from the market.

2. Experiment with Schedulers and governors. VR and SIO schedulers are known to be good. Ondemand or OndemandX governors only. Ondemand is for performance, OndemandX is for battery life.

3. OC can be unstable and potentially dangerous. Try out UV on the safe side.

4. To UV, limit your max frequency to 100MHz (Warning! Your phone will become very slow when you do this)

5. Try a value of -100mv for 100MHz and try playing a video with Rockplayer. You will hang if you UV too much. Do this for other frequencies going up the scale until 1GHz.

Good values to try:

100MHz - -125mv

200MHz - -75mv

400MHz - -75mv

800MHz - -50mv

1GHz - 0mv
[Captivate Android Development] aalh:
Try Control Freak instead of VC

also there is a good doc that was linked in the Onix thread

shaolin95's Overclocking Guide

existz, I did not see a link to it in the Talon OP
[Captivate Android Development] existz:
Let refresh on what we mean by "RAMHACK" scripts ..., LMK settings are set in 2 places, userspace and kernel side. If you use a script like Darkys ramhack ..etc, it only sets it to the kernel side (sys/module/lowmemorykiller/parameter/minfree), so then you end up with 2 LMK settings in 2 places.., so there COULD be issues in the way LMK actually works. Also, the way LMK values are set to userspace/kernel is completely different than how a normal kernel sets them. That's why we came up with MemoryFreak to set them correctly on Talon. I know it does not give full control over LMK settings, but this gives wayyy more options to the end user with the basic tweaks to setup to their liking, without giving them enough rope to hang themselves.. if your a more "advanced" user and want 110% control, then you can adjust all the LMK settings in ram.conf ..

So that's the logic behind it all, ramhack scripts that just go in /etc/init.d/ are bad.., they are just that, a hack.. Now the V6 SuperCharge DOES seem to set it in both places, if your going to use it then you probably don't want to set presets with MemoryFreak. , Also, ZRAM comes into play.., ZRAM compresses swap pages and stores it in memory itself, increasing the capacity ,allowing more apps to be stored in memory. So, whatever settings that were made, most likely were not created with ZRAM in mind, as it does change things up a bit.. Which ZRAM is very nice on our devices where we have limited amount of memory, this helps us squeeze a little more out of it, without actually having to have more physical ram. .. this is another reason we don't want you using "ramhack" scripts..,AFAIK talon is the only kernel that has swap and that actually uses it (ZRAM), so those hacks were setup on a stock like kernel, and they could behave completely different than what they do on talon, so just because 1000 ppl had great results using Darkys or Juwes hack on another kernel, doesn't mean its going to react the same on Talon..

So for optimal settings and compatibility, its best to use Talons setting and MemoryFreak to adjust them if you need to.., IMO nexus s settings are better than stock, so if you want more of a stock experience, I recommend using those.., plus you can tweak ZRAM size and swappiness to your liking ..,if you want more clear instructions on what those 2 do, just Google them, Zram is used in newer kernels, plus Compcache has their site that explains in detail how it works.. Hope this helps understand why we say what we do, and why things are they way they are
[Captivate Android Development] topiratiko:
Hows that inspire?

Sent from my Apex Blue JVR Samsung Captivate.
[Captivate Android Development] squishy5:
is the test version stable
[Captivate Android Development] jswclw:
So now that I got Memory Freak working with the help of pikachu01, and with existz explanation of ram hacks, some questions come to mind.

I wonder what left behind those files in my init.d directory. There were 4 which I would attach for reference, but that doesn't seen possible right now.

There is also the question of the missing ram.conf. Why do you suppose that was missing? Where was out supposed to come from?
[Captivate Android Development] existz:
Not all files in /etc/init.d/ are bad, for example , _99ramset is generated by talon, also things like S01sysctl, S08zipalign, S99complete are fine, those are included in your rom...just delete the files that say ramhack or similar, its usually named so you can tell what it is.
[Captivate Android Development] existz:
Yes very, 150% better than 0.4.3..., just not ready to release 0.4.4 yet so its a test build.., but should be more like a rc1
[Captivate Android Development] tylercarter:
Will we see another test build soon?
[Captivate Android Development] existz:
Possibly..., I've made a few small changes since last test., honestly there's not enough that's been done yet to make a new test/rc1 release .. so once a few more things get done or bugs fixed, ill release a new test..but will prolly be a day or two (unless something pops up)
[Captivate Android Development] tylercarter:
Awesome. Im really loving. 21 right now
[Captivate Android Development] zacharias.maladroit:
++

awesomely stable & smooth :)

no idea in what area it could be yet optimized

so far the experience is very consistent & smooth
[Captivate Android Development] jswclw:
You mentored 3 of the 4 that were in there. The one you didn't mention was S02edt_perms. They are all gone now. Should I expect some I'll effects? Seems the best yet. Of course I also added the missing ram.conf. Any clue why that was missing?
[Captivate Android Development] existz:
I've got a few more bugs that needs squashed before putting 0.4.4 out, still need to track this damn memory leak down, plus I'd like to get the other half of the charge bug fixed..but got a feeling that might be a journey in itself.., so I'm not sure if that will be marked off the list for 0.4.4 yet :(

Well, it could possibly cause issues.. I'm not sure what all that particular script for S02edt_perms (which sets file permissions) actually sets... if you still have the rom zip on ur phone, you can use root explorer or similar and grab those files out of the zip and copy back to /etc/init.d if you have any problems.. As for ram.conf not being there, I have no clue ..the kernel usually takes care of this and places it in /etc/init.d ..just mark it up to a random fluke I guess
[Captivate Android Development] jswclw:
I have the ROM (Apex), but I also saved all 4 files in a backup directory. Since they all seem to be expected, and actually weren't the problem with MemoryFreak, I guess I will put them back. If I don't do it now, I might forget. Just in case some problems arise down the road - it will not be because of these missing files. Thanks again for your insight.
[Captivate Android Development] Peaster111:
@exists

You have made amazing progress on Talon... very impressed. If you squash the memory leak and other half of the charge bug, it'll be freakin' perfect :D

... any remaining potential "bugs" (I can't think of any) would be noise level stuff.

Thanks Again
[Captivate Android Development] zacharias.maladroit:
sure, that memory leak issue is really stupid & sort of a showstopper bug

I'll see if it also occurs for me

but the charge bug doesn't appear as severe as the other

well, we could try to revert samsung's algorithm and use the one implemented in cm7

use "02_0001-battery-Force-100-when-batt-is-full-and-display-actu.patch" for help to reverted samsung implementation (it's not reverting cleanly)

then try to revert "01_0001-Revert-Return-battery-capacity-as-percentage-of-max.patch" / make it look like the implementation from August 16th

and apply the other 2 patches from August 17th

on lower values (e.g. below 25 %) it doesn't appear as accurate as on higher ones but it's way better than in the past

maybe one of you guys wants to attempt this

I actually wanted do this but I'm rather slow in porting stuff & also don't have much time [almost all used up for my cm7 kernel to get it to speed & stability]

perhaps that helps with the battery

concerning the memory leak:

those that suffer from it:

- what are your apps installed ? (ALL of them !)

- any background services running ?

- any appkiller used ?

- when is it happening more easily / faster [e.g. what might trigger it faster ?]

- ...
[Captivate Android Development] topiratiko:
Question for one of the smart guys or anyone else that knows...what negatives would lowering swappiness bring? I know it would reduce writes and extend battery but what negatives?
[Captivate Android Development] TheSoaresan:
Hey guys i need help,

So today my phone started acting weird: I was on the latest talon (0.4.4.21) and latest mosaic and I when i did ANY activity on my phone, it just froze. By froze, I mean the screen froze, the touch screen didnt work. After about 10 seconds, the phone restarted itself. This happened a couple of times...I tried wiping dalvic etc and rebooted but the phone go stuck in the boot animation i.e. it kept playing the boot animating over and over again for atleast 30-40 mins. I have max 20-30 apps. It didnt do this normally when i wiped dalvic, etc. So i decided to try go back to stock GB. Im following these (http://xdaforums.com/showthread.php?t=1045734&highlight=tut) instuctions. I flashed stock using odin and once again the phone is stuck on the boot animation... Any ideas whats going on?
[Captivate Android Development] Time_Zone:
Do you, by chance, use a bluetooth headset?
[Captivate Android Development] TheSoaresan:
Hey thanks for the reply..but after an hour...it worked after i took out my sim card...:/ and no i do not use a bluetooth headset. F**king finally, this phone has booted up.
[Captivate Android Development] pikachu01:
Let us know about your progress so far. I don't think this is a kernel related issue, but we'll be glad to troubleshoot it together :)
[Captivate Android Development] RashaMatt:
I copied in the ram.conf file that was posted here, and re-flashed .21. No change - 'free' still shows swap at 0, and MF still has the empty Dropdown. Wtf...?

Why would I have no zram? Like I said, it's always been like this.

____________________________________________________________

AT&T Captivate SGS I897, Serendipity VII b.1, TalonDEV 0.4.4.21, KC1
[Captivate Android Development] Fate-Silver:
Maybe Serendipity VII ROM doesn't support it.

It's just like the V6 SuperCharger Script doesn't work on Darky's ROM. :(
[Captivate Android Development] TheSoaresan:
Everything is fine. Phone is working without freezing, thanks guys
[Captivate Android Development] shane87:
Try dropping in the ram.conf without reflashing. It sounds like, for whatever reason, when you are flashing talon .21 it is not generating the ram.conf file. And putting the ram.conf in etc then reflashing is deleting it.

Try this: copy the ram.conf posted earlier into etc, NOT /etc/init.d!!! The path to ram.conf should be /etc/ram.conf!! After that, reboot w/o reflashing and see if it works.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] jswclw:
It has been about 20 hours since ram.conf has been properly placed, as evidenced by MemoryFreak being operational. I didn't actually change anything in MemoryFreak so the settings remained the same as supplied in the message above.

The ROM continues to operate smoothly and swiftly. Used RAM has climbed to 286-294 range. Still running smoothly though. In the past, when used RAM got this high, the phone would get real laggy and I would have to reboot. So far that hasn't happened, I would guess because ZRAM is in use now, and wasn't before (since ram.conf was missing).
[Captivate Android Development] geokilla:
Exact same problem I got on Mosaic. I find it weird that the developers are saying a ROM doesn't support it... I was planning to do a complete back to stock Gingerbread reflash too. Guess that's not needed anymore.
[Captivate Android Development] jerkysh:
i think that a stable is needed!!!
[Captivate Android Development] aalh:
you say that like it is his choice

when bugs are found versions are changed

if the test version does not work for you, ask how you can help fixing your issue

dont just demand a new version number
[Captivate Android Development] studacris:
By all means, builds it yourself...

I like the analogy azrienach made on xda tv about the why operation iron fist was implemented: "some people are starting to act like demanding dissatisfied costumers instead of neighbors borrowing tools."

this is development, it takes work and several test builds to ya know develop...
[Captivate Android Development] d_gritza:
i got a reboot yesterday while I was on the phone yesterday with a dog pound (found a lost dog :()

MY Battery was at ~15% using .21 1000MHz
[Captivate Android Development] smokestack76:
Very good quote indeed.
[Captivate Android Development] RashaMatt:
Doh! I was looking in the wrong dir. All that talk about ramhack scripts threw me off :-\

So anyway apparently I DO have a ram.conf file in /etc, but after rebooting the symptoms are the same - no zram here.

EDIT: Have enabled logging, rebooted, still no zram, and logs have no match for 'zram' or 'cache'. Devs, any possibility of adding some logging to help debug this?

____________________________________________________

AT&T Captivate SGS I897, Serendipity VII b.1, TalonDEV 0.4.4.21, KC1
[Captivate Android Development] existz:
If you have the ram.conf, then delete it and reboot...this will regenerate a new one, and things should be normal then ...have you messed with the ram.conf file any before? Setting ZRAM_SIZE to 0, or changing any LMK values? Either way try just deleting the file so a new one is generated ..

You can do the command below to see if zram is in use ...

cat /proc/swaps

As well as the following to see how much swap is being used

free
[Captivate Android Development] killer_raj:
charge bug is still there...

one feedback for watsa and existz...

i tried the new talon...0.4.4.20...1000..and charge bug was still there..

and yesterday i tried 0.4.4.20...1200 and then i put my phone on charge....and left it for 12 hours..(yeah i slept for contineous 12 hours..i so much needed it for a long time)

and when i unplugged..then i was still at 99%..so seems chargebug has gone

though the lag is there...and lag increases with the usetime...

will test it again today...with talon running..

and then again will flash DC and test it again..and will update the feedback...

Edit 1: its in charge again...this time i m observing the charging progress...(last time i was asleep)....so it reached 97% and the battery notification showed that battery is full pls unplug..i didnt unplug....and i saw that my batt was still charging..and it went to 99% slowly..didnt increase from there...its still plugged in and discharging slowly..it has reached 95%..will update again..

EDIT 2: 77% and falling...i wanna see when it starts charging again..i m not unplugging it...

EDIT 3 : 61% and falling..so 16 % fall in 1 hour 10 min in idle condition...means it falls more faster when the charge bug is there..

and final conclusion...charge bug is still there..and it doesnt start chargin after a certain drop....

now i m gonna unplug n replug...coz i wanna use my phone..lol

post eneded
[Captivate Android Development] gangpe:
Hey existz,

I love what you've done with .21, but I've ruin into something (not really major, just an inconvenience). When I try to user any gps app (yes, I know gps is normally bad), it takes a while to find a signal. Usual times are around < 50 seconds for a lock, but with talon, it took somewhere around 5+ minutes. Minor inconvenience once again; just thought I'd give you the heads up.