yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] rlorange:
Same issue! I recovered by flashing. .12 talon via odin then. .21 via sgs kernel flasher. Thought I'd have to do a full clean slate wipe... must be a memory freak bug.

**Simply Honey3.9, Talon kernel1.3ghz**
[Galaxy S I9000 Android Development] flolep:
No, I will try that and the process I told you in my preceding post when the next version of Talon comes, I will be patient. I was just kidding, I will remember your settings and advice, thanks pikachu :p
[Galaxy S I9000 Android Development] flolep:
It is installed with the process of flashing last version of talon (.21) in CWM... In your applications...
[Galaxy S I9000 Android Development] cink40:
I use Cordy game (huge Ram user) from market for test app and it is working only with stock Samsung settings. With Nexus S and Talon default phone frozes almost any time that i try to play Cordy...
[Galaxy S I9000 Android Development] wolper13:
got it!

thanks!
[Galaxy S I9000 Android Development] shaarky:
With .21 version I've problem with Tasker-seems that I have to wake mobile to get profile applied...with Galaxian I don't have this problem.Like it's sleeping too deep.I'm using Ondemand governor (not Ondemand X).Anyone else have this problem?
[Galaxy S I9000 Android Development] mak777:
It's inside Talon 0.21 ;) You don't need to download it ;)
[Galaxy S I9000 Android Development] Fekke:
Going to try the new stable version. Anyone tried some UV? What settings are you users trying? or just using it as it is?
[Galaxy S I9000 Android Development] Rootax:
Honestly the .0.4.4 branch is more stable than 0.4.3, even if the name says otherwise...
[Galaxy S I9000 Android Development] Blondasisko:
I had two BSOD in last three days with Talon .21 (criskelo rom v. 77). I tried to read logcat, but there are only logs from the current session, no logs before BSOD and manual reboot. Is the previous log stored/dumped somewhere?

Do I have to use adb to recover it (maybe terminal simulator), or any logcat reader?
[Galaxy S I9000 Android Development] InkZ:
0.4.3 crashed all over the place, updating to 0.4 has resolved most of the issues. Still not as stable as I'd like really but it's certainly going in the right direction.
[Galaxy S I9000 Android Development] Mangus_U*RA:
as I did two days ago, you have to use adb BEFORE rebooting the phone.

When you get bsod, just connect the phone with usb cable and use adb to retrive the log.

Check in the last pages in this thread, you will find more info about it.
[Galaxy S I9000 Android Development] anoneemooz:
I've been running stable with no black screens of death or whatever fortunately. :)

My OC/UV settings using Voltage Control:

1200 0

800 -25

400 -50

200 -75

100 -100

Pretty standard stuff. I used to have -25, -50, -100, -125 but then I would get black screens playing a particular game so I lessened the UV. It only happened with that particular game though (My Country). My phone was perfectly fine otherwise. ;)
[Galaxy S I9000 Android Development] anoneemooz:
Set home_app_adj = 1. That's pretty much what HTK does in supercharger. :) Works for me!

Edit: oops answered already! Didn't notice.
[Galaxy S I9000 Android Development] The Undertakerr:
I had a second BSOD this morning after sleep, my phone didn't want to wake up anymore.

No OC/UV, ondemand governor.

I a loosing a little trust in my phone now, I need to be able to trust my phone to work and wake up if it's needed.

Reverted now to Talon 0.4.4.17, hoping this will end the BSOD's because of this:

I don't care about batterylife, as long as the phone is stable.

Really don't know to which version I have to revert to be certain the BSOD's will stay away. Any advise on this?
[Galaxy S I9000 Android Development] Hrithan2020:
Yeah, right now, I have set it as 2.

But, not sure that is the only change which supercharger does as part of the OOM priority fixes. [all those oom.panic and the entire LMK_ADJ values are different]
[Galaxy S I9000 Android Development] jayakumar6591:
guys pls help me !!!!!

im in simplicity 0.33 rom , i could not flash talon kernel!!!!!!

it freez on talon boot screen!!!
[Galaxy S I9000 Android Development] Tatsuya79:
Current version has those same values: no uV on RAM and ADC in 4.4.21.
[Galaxy S I9000 Android Development] TheBigX:
Now in good english please.

From which Kernel do you come from?
[Galaxy S I9000 Android Development] folkg:
I like the Juwe RAM script, but it unfortunately has the same problems as the super charger script with this kernel.
[Galaxy S I9000 Android Development] pikachu01:
Does this start with the 0.4.4.21 version? Was it there before this? Do you use any init.d scripts?

How often does this occur? And yes, RAM and LCD is back to their stock voltages. Are you using any init.d scripts?

The LMK settings can be adjusted using Memory Freak. Other than that, the kernel panic etc are set by default by the kernel to be using the most optimized settings.

The first time you flash, you'll need to wait ~5mins for the dalvik caches to rebuild.

It's intentional that these scripts won't work. Try setting it from MemoryFreak or setting it by manually editing /etc/ram.conf
[Galaxy S I9000 Android Development] The Undertakerr:
I did a modification of Talon's ram.conf in system/etc, because I wanted to try some supercharger settings and I really like Juwe's Ram management.

Instead of using init d. scripts, modification of Talon's own ram.conf seemed to be the best thing to do, to try the settings, so they don't desturb Talon's settings.

It works, also at startup!

Please don't flame me for giving it a try.

I used:

-Supercharger's: Set home_app_adj = 1 & echo "0,3,5,7,14,15" > /sys/module/lowmemorykiller/parameters/adj

-Pikachu's: 160 in ZRAM & 50 in swappiness

- Juwe's: LMK minfree settings: if [ -e /sys/module/lowmemorykiller/parameters/minfree ]; then echo "2560,4096,6144,12288,14336,18432" > /sys/module/lowmemorykiller/parameters/minfree

FOREGROUND_APP_MEM=2560

VISIBLE_APP_MEM=4096

PERCEPTIBLE_APP_MEM=6144

HEAVY_WEIGHT_APP_MEM=6144

SECONDARY_SERVER_MEM=6144

BACKUP_APP_MEM=6144

HOME_APP_MEM=12288

HIDDEN_APP_MEM=14336

EMPTY_APP_MEM=18432

-Juwe's:

[ -e /proc/sys/vm/vfs_cache_pressure ]; then

echo "50" > /proc/sys/vm/vfs_cache_pressure

[ -e /proc/sys/vm/dirty_expire_centisecs ]; then

echo "3000" > /proc/sys/vm/dirty_expire_centisecs

[ -e /proc/sys/vm/dirty_writeback_centisecs ]; then

echo "500" > /proc/sys/vm/dirty_writeback_centisecs

[ -e /proc/sys/vm/dirty_ratio ]; then

echo "22" > /proc/sys/vm/dirty_ratio

De rest of the ram.conf I left untouched:p

Untill now everyting is working fine with this setup:D

If you want to give this config a try, flash this zip.

Ofcourse at own risk.

This .zip will delete your old _99ramset in /system/etc/init .d to make sure it won't be in the way of the nieuw config. The kernel will create a new one with the new settings.

This .zip will add the new ram.config in /system/etc.

Downloadlink: http://dl.dropbox.com/u/25779832/BttB diversen/Talon Ram.conf.zip

*In case you're interested in giving this conf. a try, before you flash it, go to mounts&storage in CWM and choose mount system. Then go back to main menu and flash the "Thing":o

*After flashing have a look in /system/etc/init d/_99ramset if the new settings are there. Also you could check with a terminal by entering: cat /sys/module/lowmemorykiller/parameters/minfree

The result should be: 2560,4096,6144,12288,14336,18432

*When you want to go back to all Talon's default settings, the easiest thing you can to is maybe flash the kernel again... :eek:
[Galaxy S I9000 Android Development] Tatsuya79:
Didn't you say you've got BSOD? :confused:
[Galaxy S I9000 Android Development] shaarky:
Hard to say, as it's not happening really every time...but definitively it's most often happening with .21 version.The settings of Tasker is the same, latest version...and no scripts in init except of ram and voltage scripts.Let's see, I will watch this.
[Galaxy S I9000 Android Development] The Undertakerr:
Yes, I had 2 BSOD's completely random.

I hope it will stay with this 2 times, so now I try the above setup to gain some more free Ram... Probably won't have any effect on future BSOD's, I'm afraid..
[Galaxy S I9000 Android Development] anoneemooz:
I suppose making another copy of the zip and replacing your ram.conf with talon's default ram.conf would be a good way to revert as well wouldnt it? :)

Or just use Root Explorer or something similar to rename the default ram.conf to ram.conf.bak and deleting the necessary stuff then pushing your version.

Anyway

I'll try this out!
[Galaxy S I9000 Android Development] pikachu01:
Ok, you can give more details like:

- Which tasker profile needs the phone to be awaken

- Is tasker controlling the CPU speed/frequency

- Is there clashing profiles in Tasker that relates to speed/frequency
[Galaxy S I9000 Android Development] betoNL:
Somebody correct me if I am wrong, but all these "memory leak" discussions are so useless...

You can change LMK settings and 00M values with apps like Auto Memory Manager and AutoKiller Memory Optimizer .

These apps get in action after boot and you can even configure AutoKiller Memory Optimizer to apply settings 2 minutes after boot, meaning they overwrite any script or service, or magic solution or whatever !

But no app, Script or mod will solve the real problem of the sgs which is the "insufficient RAM issue".

Any Super Android Smartphone should have more than 500MB Ram Stock and that's by far not the case of the SGS.

Symbian devices can run on less powerfull processors and with less RAM, but Android is too fat :eek:

So until a "remaining" REAL active dev doesnt come up with a BIGMEM version for the i9000, all these "memory leak/scrip/management" discussions are useless.

Here I am managing as good as I can with the above mentioned apps and other mods like disabling ZRam and removing/freezing bloatware , background services , all kind of google and samsung crap.

And, if a bigmem kernel version finnaly appears, I will jump to it with as fast as I can, no matter which kernel that is....

Actually I think I will start a new "BOUNTY" thread

Peace
[Galaxy S I9000 Android Development] existz:
Pulled latest test version, Captivate is seeing severe corruption when using Bluetooth on /data, where a flash back to stock does not fix it.., so until futher notice I am pulling the latest test and advising not to use bluetooth until more info is found out.. As of right now looks like all those that suffered from this was using the same rom, users on other roms do not have this issue.., so it might not even effect different roms or SGS, but to be on the safe side im going to pull it and advise not to use bluetooth till i can figure more out about this
[Galaxy S I9000 Android Development] cink40:
huh, went back to Darky kernel 3.1 just in case... There are still 2 talon files there: _99Ramset in etc\init.d and ram.conf in etc. May I delete those?
[Galaxy S I9000 Android Development] The Undertakerr:
Yes, you may delete them. Those files only have effect on Talon kernels...
[Galaxy S I9000 Android Development] TheBigX:
I will give 100€ to this bounty!

Normally the SGS has 512MB ram.. Maybe 64MB for graphics from ram... there should be more than 448MB (over 100MB more than now!)..

I´ve looked at many sites to confirm, that the SGS has 512MB ram.

So... GO ON MY DEVS.. WANNA EARN 100€? BIGMEM please :)
[Galaxy S I9000 Android Development] The Undertakerr:
If it would be possible, to have 400mb of usable Ram, without losing a hack of a lot of features, like videorecording, etc, it would have been done already.

It would have even been done in Froyo times already.

You WILL lose a lot of features. And you will NOT gain much. Maybe a few extra mb's of free memory, which will fill up also.

It's by far not worth the features you lose.

Putting bounties on stuff like that will not bring you the things you are looking for...

Just my 2 cents...
[Galaxy S I9000 Android Development] betoNL:
Bounty thread is launched....re-post there pl

http://xdaforums.com/showthread.php?p=16952452#post16952452

«»
[Galaxy S I9000 Android Development] betoNL:
This is becoming off-topic.....if you repost it over there, I will gladly explain why I disagree with you
[Galaxy S I9000 Android Development] Rootax:
Safe move existz, good luck.
[Galaxy S I9000 Android Development] jayakumar6591:
im using Semaphore 1.5v kernel!!!!!
[Galaxy S I9000 Android Development] ZioGTS:
Very wise existz, I appreciate that. And very professional. Thanks for the great work you're doing! :)
[Galaxy S I9000 Android Development] greasyguy:
@anoneemooz: trying your .conf now. Seems to be nice. Thanks!
[Galaxy S I9000 Android Development] folkg:
How can I implement all of the Juwe values into the conf file? I really liked his values.
[Galaxy S I9000 Android Development] shaarky:
Never had this problem, using Bluetooth daily (rSAP), staying on .21 ;)
[Galaxy S I9000 Android Development] brfsa:
which rom where people having that issue?

I did not notice any problem here, on surface 3.0.2.

cheers
[Galaxy S I9000 Android Development] st4rk:
Not a problem for me as don't use bluetooth, but better safe than sorry for those that do. Keep up the good work existx.
[Galaxy S I9000 Android Development] anoneemooz:
Not mine~ it's The Undertakerr's. I just commented on it. Credit goes to him for that. The only modification by my own doing is suggested making home_app_adj = 1 to keep the launcher from being killed which I had a serious problem with before when it was set at 2. :)
[Galaxy S I9000 Android Development] flolep:
Well well well, thanks for this effort for talon community :-) maybe I will try to go back to talon kernel sooner than I thought and give a try to your zip :-) but I must admit it really is a dilemma as I didn't reboot my phone since two full days when I tried supercharger and my phone is still smooth as hell and has between 80 and 100 mb free always (105 apk installed...). It is a really long time since I was in such comfortable situation with my sgs (froyo maybe). But, really, thanks The Undertakerr.
[Galaxy S I9000 Android Development] flolep:
+ 1 on this one.

Moreover, who cares to have more memory when everything runs smooth with more than 100 applications installed.

If I had only 5 mb free ram but everything smooth, new applications launching, smoothly replacing preceding one in memory, without any lag, I would really be the happiest man over here, I agree with kodos on that one.

But the experience proves that it doesn't exist, even with 40 mb free.

Things become to get smooth when there are 60 mb free, and if scripts can help us achieve this goal, why not?

I don't think it is useless to try to have smoother phones, easier as possible, and sharing that with the community.

Finally, applications you quoted, betonl, are what they are... More applications installed... And trying both, multi tasking was dead with them and phone unstable. But yes, they worked a little, but there are better "craps" out there for that, supercharger is one of them :p
[Galaxy S I9000 Android Development] The Undertakerr:
Thanks!

I made a mixture of settings, people speak good about from Supercharger, Juwe's and Talon settings.

Till now it is working great! More free Ram, no lag, supersmooth and the home button reacts instantly now when trying to open the lockscreen.

No init d. script which could work against Talon, just changes in ram.conf.

But it could be my imagination, placebo:o

I will have to find out the next couple of days!!
[Galaxy S I9000 Android Development] flolep:
Hmm, if your phone is now working like mine, believe me, it is not placebo, 100 percent sure :p
[Galaxy S I9000 Android Development] folkg:
Talon isn't allowing me to set the permissions of any file. The modded ram.conf file flashed has zero permissions, and are reset on reboot after changing them.

Also, will memory freak eventually allow you to change all memory parameters rater than just using presets? It is very un flexible and almost useless.
[Galaxy S I9000 Android Development] pikachu01:
MemoryFreak is still in beta testing, hence more features will come. Have patience :)

And what are you using to set permissions to ram.conf? Root Explorer?
[Galaxy S I9000 Android Development] folkg:
Good :)

And I've tried file expert, super manager and script manager. I'm a little worried about the state of my ROM, I don't like that my permissions aren't sticking.

I don't, for example, even have any access to my ram.conf file whatsoever. I hope that doesn't cause problems.
[Galaxy S I9000 Android Development] pikachu01:
Have you tried to install only one version of busybox in xbin and remove all others?
[Galaxy S I9000 Android Development] folkg:
I've basically just installed Juwe's ROM and talon. I don't know where I'd find out about multiple busy box versions and how they'd have gotten there.
[Galaxy S I9000 Android Development] pikachu01:
Install the busybox installer and install 1.17.x in xbin. After that, check /system/sbin /system/bin and /bin for the busybox binary and remove them.
[Galaxy S I9000 Android Development] folkg:
Okay, so this is weird. I did as you said, installed it, deleted old version from /bin and it was gone.

However, I reboot the phone! And it's back again. Same file last modified August 6th. Nothing I change seems to survive a phone reboot. I appreciate the help so far, any idea what's going on now?
[Galaxy S I9000 Android Development] pikachu01:
How about trying to change the permissions to ram.conf now? Is it working?
[Galaxy S I9000 Android Development] jayakumar6591:
im in simplicity rom running Semaphore 1.5v kernel .....

i flashed talon kernel and it freez on talon boot screen ...i have waited for 20min ..

and it still remains on boot screen!!!!

pls guide me .........
[Galaxy S I9000 Android Development] pikachu01:
How did you flash it? CWM or SGS Kernel Flasher?
[Galaxy S I9000 Android Development] jayakumar6591:
finnaly it works but it took too much time !!!!

but i couldt enable lagfix!!!!
[Galaxy S I9000 Android Development] .:Crack:.:
These values are commented-out in your ram conf... (remove the # in front of the lines)

Just sayin ;)
[Galaxy S I9000 Android Development] folkg:
Only for the session before they are reset on reboot. I have no idea what's going on, this is so weird. No filibuster changes will apply at all.
[Galaxy S I9000 Android Development] folkg:
That was to be file system changes haha, nothing to do with filibuster.
[Galaxy S I9000 Android Development] The Undertakerr:
Thanks!:D

Didn't notice that!:D

Now after removing comments, Juwe's VM settings are working.:)

For example, now when I type: cat /proc/sys/vm/dirty_expire_centisecs in the terminal, then the echo= "3000"

New zip for who wants to test: http://dl.dropbox.com/u/25779832/BttB diversen/NEW Talon Ram.conf.zip

To revert back to Talon's ram conf. settings of 0.4.4.20, flash this one:

http://dl.dropbox.com/u/25779832/BttB diversen/Restore Original Talon Ram.conf.zip

Will be testing this...:p
[Galaxy S I9000 Android Development] pbecks1963:
Looks VERY promising (more ram free) My widgets and Go launcher screens are swimming like fish in the sea....
[Galaxy S I9000 Android Development] shaarky:
New ram.config seems to be really great! I can't believe it, so far testing for 10 hours and it's really fast! Thanks Undertaker
[Galaxy S I9000 Android Development] androiderrr:
How to update this new ram.config?I updated it through CWM and is unable figure out any difference between this and orginal ram.config of talon
[Galaxy S I9000 Android Development] Widget21:
Still on Talon 0.4.3 so would these ram scripts work on this version too? Also are these flashable via CWM?
[Galaxy S I9000 Android Development] Flynny75:
Is anyone having issues with Performance governor? I set it in perf, ran quadrant and got sub-par scores. Underclocked back to 1GHz from 1.4, and still getting sub-par (eliminates stability at higher clock). Set back to OnDemand/X, and scores are back up again 2700/3200 (at 1 and 1.4). Why would the scores with OnDemand be higher?

(And yes, I know Quadrant scores are meaningless... but still)
[Galaxy S I9000 Android Development] darass:
i flashed Undertakers zip with ner ram.conf, deleted 99ramconf file from init.d before, then flashed it mounting system before in cwm, and after rebot there is no new 99ram conf in init.d. Is it bad? And there are no updates in /sys/module/lowmemorykiller/parameters/minfree and parameters are different than those in new ram.conf

Im on semaphore 1.5.0

what should i do now?
[Galaxy S I9000 Android Development] The Undertakerr:
Only flash it on Talon 0.4.4 and higher. Not working on Semaphore.

Only flash it with Talon 0.4.4 or higher.

Please read the initial post over here for more info:

http://xdaforums.com/showpost.php?p=16947104&postcount=2827
[Galaxy S I9000 Android Development] darass:
cant find 0.4.4 version... can anybody post it? in first post is only 0.4.3
[Galaxy S I9000 Android Development] existz:
0.4.4.22 Public Test

0.4.4.22

Changelog since 0.4.4.21

- ARM: more aosp/upstream ARM fixes

- cpufreq: fixed ondemandX wakeup issues

- voodoo: add new i9000 partition table support

- usb: read/write speed hack for mass storage

- reverted: parts of infuse wifi and power fixes

NOTES

UPDATE: So it seems the bluetooth causing corruption issue is resolved in this release.

Also added I9000 BIGMEM version. These versions will break 720P video recording.

A new partition table added for newer SGSs, hopefully this fixes the issue some

of you have not being able to convert with voodoo
[Galaxy S I9000 Android Development] existz:
The performance governor does not function 100% as it should and it should not be used.., the only reason its there is because it could not be disabled in the source.. Only ondemand and ondemandX is supported/recommended...

You can set ondemand and then set min/max to 1/1.2ghz , thats all performance does is run at max clock (does not scale)
[Galaxy S I9000 Android Development] Tatsuya79:
0.4.4.22 - Neutral Colours Version

-Voodoo hack reverted

-Speedmod Sharpness/MDNIE tweaks

-Galaxian AMOLED brightness scaling modification

-UI Sharpness now stronger (fonts were hard to read at average distance, now crisp without jaggies)

thanks Hardcore

thanks Lukiqq
[Galaxy S I9000 Android Development] The Undertakerr:
Flashing from my bed... oww I'm very addicted lolllB-)

Thanks Existz!
[Galaxy S I9000 Android Development] flolep:
Followed, I presume, by your new ram tweak... Lol better without comments :p didn't try now as my phone didn't reboot since 3 days now and still smooth. But downloaded .22 and your script and keeping them hot in a protected area for later :p
[Galaxy S I9000 Android Development] greasyguy:
+ 1
[Galaxy S I9000 Android Development] androiderrr:
Should i disable lagfix before applying new test version?
[Galaxy S I9000 Android Development] pikachu01:
You shouldn't need to. I've flashed many test versions on top of each other without disabling lagfix.
[Galaxy S I9000 Android Development] androiderrr:
Thanks just flashed the new test version
[Galaxy S I9000 Android Development] ic3joker:
anyone flash 0.4.3 on milky 1.3? i flash on it and it stuck at startup screen with TALON word. been waiting for 15min and i cant go into recovery too.:confused:
[Galaxy S I9000 Android Development] pikachu01:
Hey ic3joker, can you flash the latest test version (0.4.4.22). Did you remove all your init.d scripts before flashing? How about OC/UV settings?
[Galaxy S I9000 Android Development] ic3joker:
i come from cm7 so it is a clean installation. i didnt delete the script. i flash to 0.4.3 because i cant get root access on milky 1.3but i get stuck. how long it need to bootup? been waiting for 15min+. so i have to redo everything xxjvq>custom kernel> milky 1.2. you on milky?
[Galaxy S I9000 Android Development] pikachu01:
You have to flash back to stock. I always flash back to stock before going to a custom kernel (with a boot into each one before flashing another).

You can go XXJVR -> Milky -> Talon.
[Galaxy S I9000 Android Development] ic3joker:
that is what i did now back to milky 1.3 so can i flash 0.4.2 on it?