yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] pikachu01:
You might have more than one version of busybox in your phone. Keep the /system/xbin and remove all other instances of busybox and try again.

Boot into recovery and install the CWM zip from your sdcard. It's that easy :)
[Galaxy S I9000 Android Development] WiwiPouPou:
Hi all,

I'm just back from MIUI, tried some of the kernels... that one seems to be the best ! Love it, as i loved Zach's one.

Now i got an issue, i used to use my own scripts in init.d, and here it's not working anymore.

I've tried rename it with an "S...", "S_...", i.'ve changed permissions...

But nothing. When i test Galaxian it works, but i don't want to use it.

So, that's all, everything is perfect so far.
[Galaxy S I9000 Android Development] flolep:
Because for this kernel everything is done in etc/ram.conf...
[Galaxy S I9000 Android Development] bhu1:
I did the exact same thing i booted into recovery and installed talondev 0.4.4.22 and after that the X sign was their for like 15 minutes then i reflashed galaxian ! Can anyone speciy how much time it can take for first boot?

Sent from my sgs

kernel: galaxian

Rom: jetpack
[Galaxy S I9000 Android Development] Hrithan2020:
For me, it took hardly 10 minutes. [ Roughly the same time taken if I manually wipe dalvik cache,cache and fix permissions, which I believe is where majority of time goes during the installation process]
[Galaxy S I9000 Android Development] pbecks1963:
Hello Existnz,

I am using the big mem version of talon kernel and noticed a drop in free ram (after a while). This means (on my SGS) a performance drop (launcher gets laggy).

That is why i changed the settings in memory freak to:

Hidden app mem = 52 mb (later i noticed that the other sliders autom. changed to zram 256 swapp 90)

My SGS seems to perform better now..

Any comment/ideas/warnings?
[Galaxy S I9000 Android Development] WiwiPouPou:
Mmh.. so how do you set OC/UV at boot ?

That's strange.. i don't speak about any ram script, and my scripts aren't erased so..

I'll search more.

EDIT : that's what i was thinking, etc/init.d should work.

As for loading conservative module..
[Galaxy S I9000 Android Development] bhu1:
but why only talondev requires clearing all this cache and not other kernels! Should I re try?

Sent from my sgs

kernel: galaxian

Rom: jetpack
[Galaxy S I9000 Android Development] Hrithan2020:
Yes, try again.

I am afraid, I won't able to give you a complete answer on why though.
[Galaxy S I9000 Android Development] kyiori:
use this cleaning script.

http://xdaforums.com/showthread.php?p=15609632
[Galaxy S I9000 Android Development] HTCDevil:
My data/local.prop:

ro.FOREGROUND_APP_ADJ=0

ro.VISIBLE_APP_ADJ=2

ro.PERCEPTIBLE_APP_ADJ=3

ro.HEAVY_WEIGHT_APP_ADJ=4

ro.SECONDARY_SERVER_ADJ=5

ro.BACKUP_APP_ADJ=6

ro.HOME_APP_ADJ=1

ro.HIDDEN_APP_MIN_ADJ=7

ro.EMPTY_APP_ADJ=15

ro.FOREGROUND_APP_MEM=2048

ro.VISIBLE_APP_MEM=3072

ro.PERCEPTIBLE_APP_MEM=4096

ro.HEAVY_WEIGHT_APP_MEM=4096

ro.SECONDARY_SERVER_MEM=6144

ro.BACKUP_APP_MEM=6144

ro.HOME_APP_MEM=6144

ro.HIDDEN_APP_MEM=7168

ro.EMPTY_APP_MEM=8192

----------------------------------------

my system/etc/ram.conf:

# Kernel VM settings

# (kernel defaults are the commented-out ones below

VFS_CACHE_PRESSURE=50

#DIRTY_RATIO=20

#DIRTY_BACKGROUND_RATIO=5

#DIRTY_EXPIRE_CENTISECS=200

#DIRTY_WRITEBACK_CENTISECS=500

#LOWMEM_RESERVE_RATIO=32

LOWMEM_RESERVE_RATIO=256

#MIN_FREE_ORDER_SHIFT=4

#PAGE_CLUSTER=3

# LMK/ZRAM settings

FOREGROUND_APP_ADJ=0

VISIBLE_APP_ADJ=2

PERCEPTIBLE_APP_ADJ=3

HEAVY_WEIGHT_APP_ADJ=4

SECONDARY_SERVER_ADJ=5

BACKUP_APP_ADJ=6

HOME_APP_ADJ=1

HIDDEN_APP_MIN_ADJ=7

EMPTY_APP_ADJ=15

FOREGROUND_APP_MEM=2048

VISIBLE_APP_MEM=3072

PERCEPTIBLE_APP_MEM=4096

HEAVY_WEIGHT_APP_MEM=4096

SECONDARY_SERVER_MEM=6144

BACKUP_APP_MEM=6144

HOME_APP_MEM=6144

HIDDEN_APP_MEM=7168

EMPTY_APP_MEM=8192

LMK_ADJ=0,1,2,4,7,15

LMK_MINFREE=2048,3072,4096,6144,7168,8192

ZRAM_SIZE=160

SWAPPINESS=50

LMK: Nexus S.

That works great with my JVR deodex based rom with Talon 0.4.4.22 without undervolting.

I've tried supercharger but it wasn't so happy... :D

Thank you all for your reports where i've taken some parts ;)

Inviato dal mio GT-I9000 usando Tapatalk
[Galaxy S I9000 Android Development] pikachu01:
What scripts are you trying to load? Can you list them here and also what they do?
[Galaxy S I9000 Android Development] ekaja:
very fast

Thank you.
[Galaxy S I9000 Android Development] existz:
Check the path at the top of the script and make sure its #!/system/bin/sh ... ours might be different than how it was on miui.. Also, yes startup scripts go in /etc/init.d/ ... If no scripts at all are working, like Voltage Control settings..etc.., then check what version of busybox your using, you can use the official busybox app in the market.., if its 1.18.x , switch it to lower version
[Galaxy S I9000 Android Development] zacharias.maladroit:
it's all about choice:

if you don't like the cleaning procedure during flash then clone the repo

remove that script & re-compile the kernel

problem solved - at least for you

this script is there for a reason:

it's supposed to remove remnants from prior kernels or scripts that could cause interference with talon's memory settings and/or instabilities (e.g. with voltage values that might be incompatible with talon kernel and damage your hardware; scripts that have incompatible memory settings etc. etc.)
[Galaxy S I9000 Android Development] WiwiPouPou:
Ok i found a really strange behaviour, always about init.d scripts :

My own scripts (to set voodoo sound volume and some others things from zach) never load because its permissions reset at each boot to read-write for owner (root:root), but no execute.

I use Root explorer, chmod with shell.. scripts permissions are reset every boot (but not the one generated by Pimp my CPU !??).

So, i don't understand,

is there a specific way to name or to set permissions to make it work ? I've never had an issue before, stock or MIUI.. :(

EDIT : My script was the issue, but no idea why and where..
[Galaxy S I9000 Android Development] jeebspawnshop:
Hey guys, is it just me, or does the phone not enter Deep Sleep while charging?

Cuz mine only hits Deep Sleep when I pull it off the charger. Otherwise, it sits at 100 mHz while charging - which is ok, I guess, but I was using .19 before I updated to .22 an hour ago, and it charged in Deep Sleep just fine.

Any thoughts?
[Galaxy S I9000 Android Development] corgar:
Inside your script you are trying to Change lmk values? If yes remove that string, fix again the permission and reboot. If you need to Change lmk settings Change directly the file named ram.conf Inside system/etc/

Tapatalked, powered by Corgar Slim Rom GB Edition.
[Galaxy S I9000 Android Development] existz:
USB charging was changed to 100mhz, stock Samsung default was 200mhz... which 100mhz is fine, the cpu cannot go any lower ..even in deep sleep, 100mhz is as low as it goes
[Galaxy S I9000 Android Development] jeebspawnshop:
That's what I thought - just got a bit confused cuz CPUSpy was reporting a much higher 100, and much lower Deep Sleep than I was expecting.

Thanks E.
[Galaxy S I9000 Android Development] flolep:
Ok. I wanted to test for two days and two nights long before posting back again.

So I tested your configuration, rebooted and used my phone really hard for one day, left it charge the night, and did some test in the next morning. Then I changed the configuration for really much more aggressive settings in minfree values, don't even know if numbers are good values, that was just testing numbers, but,believe me or not, it worked... And I did the same testing again.

And the result is without a call... My configuration is really much much much smoother, that's all, and everyone out there that will want to compare yours and mine will tell you the same, I am 99% sure about that.

They surely won't have so good multitasking and battery but they WILL have a much smoother phone.

For all people who want explanations about this post, please, before asking, go some pages back to understand what I am talking about. And remember, the following settings are aggressive ones, there should be some middle between currydude's ones and mine.

And here, my configuration in etc/ram.conf :

# ram.conf: settings file for use with ramset -kodos

RAM_CONF_VERSION=5.8 # Do not edit this

#

# This file controls various tweakable aspects of how your system manages its

# memory usage, including LowMemoryKiller behavior, ZRAM/compcache (i.e.

# compressed ram swap) settings, and kernel VM settings

# Kernel VM settings

# (kernel defaults are the commented-out ones below

VFS_CACHE_PRESSURE=50

DIRTY_RATIO=22

#DIRTY_BACKGROUND_RATIO=4

DIRTY_EXPIRE_CENTISECS=3000

DIRTY_WRITEBACK_CENTISECS=500

#LOWMEM_RESERVE_RATIO=32

LOWMEM_RESERVE_RATIO=256

#MIN_FREE_ORDER_SHIFT=4

#PAGE_CLUSTER=3

# LMK/ZRAM settings

FOREGROUND_APP_ADJ=0

VISIBLE_APP_ADJ=1

PERCEPTIBLE_APP_ADJ=2

HEAVY_WEIGHT_APP_ADJ=2

SECONDARY_SERVER_ADJ=2

BACKUP_APP_ADJ=2

HOME_APP_ADJ=1

HIDDEN_APP_MIN_ADJ=5

EMPTY_APP_ADJ=15

FOREGROUND_APP_MEM=4096

VISIBLE_APP_MEM=6144

PERCEPTIBLE_APP_MEM=12288

HEAVY_WEIGHT_APP_MEM=12288

SECONDARY_SERVER_MEM=12288

BACKUP_APP_MEM=12288

HOME_APP_MEM=14336

HIDDEN_APP_MEM=24000

EMPTY_APP_MEM=32000

LMK_ADJ=0,1,2,1,5,15

LMK_MINFREE=4096,6144,12288,14336,24000,32000

ZRAM_SIZE=0

SWAPPINESS=0

Sent from my GT-I9000
[Galaxy S I9000 Android Development] Hrithan2020:
I just wanted to say ,that after a few days of testing, it does seem that with Nexus S LMK , [160 MB ZRAM and 50% Swappiness and HOME_APP_ADJ=1], the phone does tend to lag quite a bit at around 40 MB free memory point.

I haven't tried currydude's value, but have reverted back to the values I was using before [Juwe's LMK values-10,16,24,48,56,72] , and it does seem to respond much better.

In short, [even if currydude's values are optimal], I feel that the talon's default settings needs to be changed,so that out of the box, it would be optimal for the majority of people.

[I do feel the zep's LMK values are way too aggressive.

@flolep, perhaps , you can give this a try ? ]

EDIT:

LMK_MINFREE=2560,4096,6144,12288,14336,18432
[Galaxy S I9000 Android Development] flolep:
Yes, I already tried these values too. Of course they are better than currydude's ones for smoothness, and without sacrificing multitasking.

But in my case I prefer sacrificing a little bit more multitasking and have a phone that responds almost instantly when I launch something, and your values are not in this case for me.

As I said 32000 for the last value is too much but maybe something around 24000 (and modifying the other values accordingly) could be just enough to have multitasking of two applications in the same time AND a great smoothness...
[Galaxy S I9000 Android Development] Hrithan2020:
Ok, so for you the problem comes even before the RAM goes down to 40 MB free? [ which would usually happen for me , over a period of time, say 18-24 hr after reboot] . Strange, it is a bit counter-intuitive..

Have you tried MegaRam II [ or other super-agressive LMK settings] and if so, how did it fare? [For me, the biggest problem w.r.t multitasking,is the browser,even with v.low LMK; but after changing the build.prop a.k.a similar to Nitro Lag Nullifier, I am notificing that the browser doesn't close as often].
[Galaxy S I9000 Android Development] flolep:
It's not a real "problem". It's just not as smooth as with more free ram, that's all.

Yes I tried "megaram 2" (lol). Of course it's the best for smoothness and performance but I think it's too aggressive, loosing too much battery and multi tasking.

I saw Nitro lag nullifier in v9 beta but I didn't try... What is it and what does it really do?

When you say that the browser is closing, what do you mean? You are surfing and browser is force closing? Or you want to have browser in a task in background when you do something else and want to go back on there without it closing by too aggressive values?

Sent from my GT-I9000
[Galaxy S I9000 Android Development] tommy34:
Thankyou! The new partition tables finally solved my problem! Now I can fully enjoy this kernel. Thanks for recognizing this as abug and not a user failure.
[Galaxy S I9000 Android Development] Hrithan2020:
I meant the browser [ with say, 4 tabs/windows open] will have to reload all the tabs, if say, I go to another application , say camera and then come back.

Nitro lag nullifier or similar settings from other devs in the thread [somehow] allows for more apps to be open. [ But doesn't really improve the performance for me, maybe it overall is slightly less responsive even].
[Galaxy S I9000 Android Development] flolep:
Ok. It helps with multi tasking but do you know what are the concrete modified values and in what file they are?
[Galaxy S I9000 Android Development] Hrithan2020:
It is in the build.prop [ENFORCE_PROCESS_LIMIT set as false, and in the case of lag nullifier lots of other values like MAX_HIDDEN_APP ,MIN_x... etc set as blank; THe values I had put , have them set as false].

For the complete values, you can check in the script itself. The values I used, I think was suggested in the script thread itself, primarily by two guys in the thread.
[Galaxy S I9000 Android Development] flolep:
Ok. Thanks, will look at this.

But for the moment, I am very happy with these aggressive settings of minfree : 6, 12, 60, 75, 90, 110 mb.

My phone is smooth as hell and I can still use two applications in the same time.

I don't care about having more multitasking or battery.

Sent from my GT-I9000
[Galaxy S I9000 Android Development] existz:
Don't thank me, thank flypubec :P, enjoy!
[Galaxy S I9000 Android Development] simone201:
Hey existz, i see that u're moving to Inspire 4G....

Will u continue dev-ing for Galaxy S?
[Galaxy S I9000 Android Development] existz:
Yea, ill still do both ..maybe not as much as before, but ill still work on SGS. I kept my captivate but now my g/f uses it as her daily, so can't test as much as i want to, but i got a great group of private testers that help out with that. Right now I'm working on taking stratosk oc module and incorporating it in to talon for higher oc. It will probably be a week or so before i can actually mess with it any and fully test it, but there's still plans for the SGS.. plus kodos96 and zach are still around and help out
[Galaxy S I9000 Android Development] jeebspawnshop:
Since you mentioned OC, I thought I should mention that Tk-Glitch (the guy who devs a kernel for CM7) actually has some purely genius OC code;

He has different kernels for different types of CPUs (high leakage, medium leakage and low leakage). I can't honestly say that I understand any of it, but when I used his kernels whilst on CM7, my phone overclocked and undervolted FAR more than with any other kernel I've ever used.

It may be worth a peak, or maybe I'm way off base.

Just trying to help ;)
[Galaxy S I9000 Android Development] existz:
Basically it just puts higher voltages for lower quality devices, upping the arm and internal voltages. Which this can be adjusted with Tegraks OC app.., for 1.2ghz usually 1300mV is more than enough, using the oc code provided by the kernel...Also, Talon supports OV (overvolt) code for Voltage Control (+50mV limit), but it can only adjust arm voltage.. But if you need more arm/int voltages, just adjust with Tegraks app
[Galaxy S I9000 Android Development] jeebspawnshop:
Ah, I didn't realize they both worked basically on the same principal.

Thanks!
[Galaxy S I9000 Android Development] Seraphim Works:
Hi, I was wondering if it's possible that a kernel with the modifications found at xdaforums.com/showthread.php?t=1233072 could be compiled for usb host testing if at all possible. I can test on the hardware side of things but I haven't learnt the art of kernel modifications yet.
[Galaxy S I9000 Android Development] mawardi:
I got black screen of death. I thought it was running out of battery. But when I plugged-in, there was a sound and I thought my display was broken. I got the battery out and power on. All is fine again. Then I just remembered why the heck people talked about BSOD. I experienced for the first time using 0.4.4.22. Stock Android JVQ, LockOn AOSP theme. Anybody care to shed a light?
[Galaxy S I9000 Android Development] Flynny75:
Undervolting at all? To everyone, in future, please list your configurations along with crash report. Makes it just that little bit easier for everyone to figure it out
[Galaxy S I9000 Android Development] mawardi:
Yes, of course there's a UV configuration. I don't know how to send log. Does this happen because of UV?
[Galaxy S I9000 Android Development] Flynny75:
It seems to be a common trait. Try not undervolting and see if you can repeat it
[Galaxy S I9000 Android Development] existz:
Yes, UV is usually 99% the cause of sleep death (BSOD), try without any UV and see if you can reproduce the problem.. if not, then start putting only -25mV at a time, testing it for a few to make sure there's no problems
[Galaxy S I9000 Android Development] mawardi:
I think the BSOD is not same with false configuration of UV because the phone functions okay, even gives a vibration and sound when unlocking. Just display has gone blackout. Before this, when I falsely applied UV, it's dead, nothing working.
[Galaxy S I9000 Android Development] pikachu01:
For me, BSOD happens when my XDA app goes haywire. I get a BSOD in the morning and found XDA app consuming more than my display ~ 35%. Hence, I always close my XDA app after I exit it and never had a problem till now.

Try leaving your BSOD'ed phone for 10hours and check what's draining the battery. That's the app that went haywire. For me it was XDA. Try uninstalling it at your side?
[Galaxy S I9000 Android Development] mawardi:
Is the problem related to Talon? I already removed XDA, just used Tapatalk. I wanted to know whether anyone got the same problem. If there weren't, I guess it's on me.
[Galaxy S I9000 Android Development] daoth:
Hey,

unfortunately i messed up installing 0.4.4.22, so phone won't startup.

I do have enough different kerlen versions on SD, but won't get into CWM

Can somebody point me to 0.4.3 ODIN Flashables ?, can't find it in Talon file store

(Quess i need to get talon working, since lagfixes are enabled)
[Galaxy S I9000 Android Development] existz:
If it won't go into cwm, it sounds like a bad flash.. u can grab a tar of any kernel and just replace the zimage ..try copying 0.4.4.22 zimage into a tar and flash with Odin ..this is half the problem with using CWM and/or sgs kernel flasher, alot more bad flashes happen easier. Also redownload the file, sometimes it can get corrupted in the process.. But usually 99% of the time that it wont go into CWM, then the flash didn't take successfully, its not really something wrong with the kernel, just cwm is not perfect and can cause this way easier than Odin. You can grab a tar of Talon from the links to older versions in the OP..but definitely redownload 22 and try flashing with Odin.. i don't think its the kernel because there's been over a 1000 downloads of 22 and its not an issue
[Galaxy S I9000 Android Development] anoneemooz:
+1 for this mod to be ported over to the SGS ;)
[Galaxy S I9000 Android Development] Mangus_U*RA:
for me, as pikachu knows, bsod has nothing to do with UV.
[Galaxy S I9000 Android Development] Hrithan2020:
Wow! It would be awesome if this works for our device.
[Galaxy S I9000 Android Development] Spezia12:
This is my configuration:

# Kernel VM settings

# (kernel defaults are the commented-out ones below

#VFS_CACHE_PRESSURE=50

#DIRTY_RATIO=22

#DIRTY_BACKGROUND_RATIO=4

#DIRTY_EXPIRE_CENTISECS=3000

#DIRTY_WRITEBACK_CENTISECS=500

#LOWMEM_RESERVE_RATIO=32

LOWMEM_RESERVE_RATIO=256

#MIN_FREE_ORDER_SHIFT=4

#PAGE_CLUSTER=3

# LMK/ZRAM settings

FOREGROUND_APP_ADJ=0

VISIBLE_APP_ADJ=1

PERCEPTIBLE_APP_ADJ=2

HEAVY_WEIGHT_APP_ADJ=2

SECONDARY_SERVER_ADJ=2

BACKUP_APP_ADJ=2

HOME_APP_ADJ=1

HIDDEN_APP_MIN_ADJ=5

EMPTY_APP_ADJ=15

FOREGROUND_APP_MEM=4096

VISIBLE_APP_MEM=6144

PERCEPTIBLE_APP_MEM=12288

HEAVY_WEIGHT_APP_MEM=12288

SECONDARY_SERVER_MEM=12288

BACKUP_APP_MEM=12288

HOME_APP_MEM=14336

HIDDEN_APP_MEM=18432

EMPTY_APP_MEM=24576

LMK_ADJ="0,1,2,1,5,15"

LMK_MINFREE="4096,6144,12288,14336,18432,24576"

ZRAM_SIZE=0

SWAPPINESS=0

I have good battery life and great smoothness. I always have about 80 mb free. I think it's the best configuration
[Galaxy S I9000 Android Development] betoNL:
Inspire 4G?

No news about the Nexus Prime? Wolfson Dac? etc.? etc.?

Just a little bit off-topic for a change...
[Galaxy S I9000 Android Development] existz:
Yea i went ahead and got the inspire for now to play with.. ill still get nexus prime when it releases, or possibly HTC holiday, haven't decided yet..
[Galaxy S I9000 Android Development] flolep:
It seems indeed that these are good values for smoothness :p

Without sacrificing too much multitasking too :-)

In my case, I prefer to sacrifice even more battery and multitasking and have values similar to megaram 1 in supercharger script (I lowered a little my previous settings because sometimes I couldn't have two applications running in the same time, that's all that I need)

Just to know, why did you comment vfs_cache_pressure or dirty_xxx variables? Did you try with and without and see any difference?

Just curious about that :-)

Sent from my GT-I9000
[Galaxy S I9000 Android Development] flolep:
Deleted sorry
[Galaxy S I9000 Android Development] betoNL:
Ok , and thanks for helping simone with re-adding 6 frequencies on that bigmem!

My sgs is as good as it gets ! ( I know, I said that before :rolleyes:) super smooth and stable

Here is small contribution (just when I thought to cut down the donations),

to the Nexus Prime fund: 0BT67304KN082115Y

Please warn me with a PM or something when your reports about the Nexus prime, HTC holliday and all those gadgets that I can afford only once every 3 years, is ready...:o

I could go for another expensive phone, but its sound have to be at least as good as the sgs's .....

Cheers
[Galaxy S I9000 Android Development] Flynny75:
Had the bluetooth problem again today. Phone has been on for 48+ hrs, with wifi on whole time. Now BT wouldnt switch on. Reboot fixed it.

Also experiencing the charging problem. Would leave on charge overnight at ~90%, and watch the battery icon indicate charging. Wake up, and its on ~40%, with the icon not indicating charging. Build data is Aug 26th. Is there a newer version?

(Note that for the first few days, I didnt see these problems.)

EDIT:downloaded .4.4.22 again from first post, and build date is now 25th. I think I had flashed a speedmod colour version (colours were definitely cooler) and am now back on official. This could mean that whoever produces the speedmod colour versions (can't remember the guys name... sorry..) could be using older buggy sources? Just something to consider. Ill keep testing the official 4422 and let you guys know if anything funny happens.
[Galaxy S I9000 Android Development] existz:
As always, greatly appreciated :) thank you

The nexus prime is suppose to be flagship icecream sandwhich, like nexus s is for gingerbread, pure AOSP is always a plus! .. But I'm liking HTC so far, kernel dev wise its awesome and the Holiday is suppose to be badass device so i can't make up my mind. It will probably come down to pricing when they are released. I thought about the SGS2 but i have started to hate Samsung properitary rom/kernels with a passion.. so the Prime being just Samsung hardware with Google aosp rom/kernel will be nice (i believe every phone should be Google AOSP and manufacturers just doing hardware only so android is as Google intended)
[Galaxy S I9000 Android Development] ekaja:
0.4.4.22 + BIGMEM + 1GHZ + Lagfix = quadrant 2500+,Antutu 3000+

smooth screen never see before (except MIUI)
[Galaxy S I9000 Android Development] Spezia12:
I didn't try it. I posted it only because i copied from ram.conf