yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] existz:
Change it in /arch/arm/Kconfig and /kernel/Kconfig.HZ for HZ_300 (just to make sure, you might not have to set it in both, but doesnt take 2s) ..and in /arch/arm/plat-s5p/Kconfig for S5P_HIGH_RES_TIMERS..

Ive tried with upping it a few times, ive tried 300, 400, 500.., as well as 200 for USER_HZ, but anything above 250 lead to issues for alot of testers.., theres really no difference between 250/300, atleast that anyones going to notice, so changing the stability for that is not worth it IMO..For some reason, this source is very touchy and some things are best left where they are.., trust me, every small 'tweak' like this has been done to Talon, 4-5 times, we have tested every possible option..
[Galaxy S I9000 Android Development] LukeSP:
I just check it. MemoryFreak already has SU access on my phone. But I can successfully config rams.conf manually.

I am using STOCK JVQ.
[Galaxy S I9000 Android Development] Marcopololo:
Hello,

I use new talondev 0.4.4.21, but I have problem with bluetooth. If I use headset. After stop to phone, I have a problem of forceclose of com.android.phone and I lost connexion with headset.

I have this problem with old version of talondev.

Can you help me.

Best
[Galaxy S I9000 Android Development] XblackdemonX:
I have a question about MemoryFreak

the Hidden App Mem Size, what does it do exactly? I don't understand.

thanks
[Galaxy S I9000 Android Development] HTCDevil:
Is it possible to have a non-ext4 (no lagfix) enabled by default version of your kernels?

I need it because my roms works at 100% without lagfix at start ;)

Thank you for your work existz, really appreciate! :D
[Galaxy S I9000 Android Development] existz:
Just put a blank file named "disable-lagfix" in /sdcard/voodoo/ folder, this will disable it by default..,then if you want to convert to ext4 you will have to remove it
[Galaxy S I9000 Android Development] HTCDevil:
Thank you very much, i'll put it in my next .zip ;)
[Galaxy S I9000 Android Development] yagami:
Been using your kernel and its very nice.

Thanks :)

By the way, i am curious , what is your config HZ ? is it 100hz ?

could it be configured to a higher HZ ? like 300HZ (for multimedia) or 1000Hz(for low latency) ?

is it preemptible ?

DAMN sorry ... completly forget this question... a person doesnt follow this topic for some hours and someone already talks about what i was wondering for some days ....

thanks
[Galaxy S I9000 Android Development] simone201:
Ok thank u for the explanation, i will stick with 250....the kernel works fine!
[Galaxy S I9000 Android Development] existz:
Its actually at 250hz., probably need to update the OP.. Ive tried different HZ values, but anything higher than 250 seems to cause stability issues with this source.., ive tried 300, 400, 500, and even adjusting USER_HZ to 200.., so im leaving it at 250 to ensure stability (btw your not going to notice much, if any, difference between 250/300... and unlike froyo source, which we could up to 1000, it seems with this GB source it does not like higher values
[Galaxy S I9000 Android Development] jaiiscool:
Never had this problem before, but after flashing #21 I unplugged after charging overnight and the battery was just 90%.......

Maybe the new changes for charging bug has introduced the bug to my phone.

But i did not have this on #20

Confused.......

For now I have cleared batt stats, will report tomorrow if it happens again.

Thanks existz!!!!!
[Galaxy S I9000 Android Development] pikachu01:
Before this, the battery stats will lie to you, i.e. even if you have 90%, it will say that it has 100% and this feature was inconsistent between users. Right now if it says you have 90%, you really have 90%. And wiping battery stats will help.
[Galaxy S I9000 Android Development] Gvdn:
One thing i noticed with my rom (Simplicity) is that once battery is fully charged the charging animation stops. I also unplugged at 90% this morning. This is running .21
[Galaxy S I9000 Android Development] pikachu01:
I can only charge mine to 96% (that means, my battery can charge up to 96%). Wiping my battery stats, and recharging gave me 97% before the battery full notification popped up.

That means, I've ran down my battery (through use) to 97% of its capacity. I can only charge my battery up to 97%.
[Galaxy S I9000 Android Development] Tatsuya79:
New Neutral Colours Version:

-Speedmod MDNIE & Sharpness settings - thanks hardcore

-Reworked Amoled Values: Deeper black, new brightness scaling (no more strong red tint on 3rd brightness level!), more contrast on darkest levels (though still a bit red, current OLED technology problem on low brightness) - thanks Lukiqq
[Galaxy S I9000 Android Development] anoneemooz:
I seem to have a bit of a different problem (?) when it comes to battery.

Mine charges to full, then from then on it starts discharging even while left plug. As in, I can see the battery level actually slowly go down in the indicator (as if it weren't plugged in).

Something similar was happening to me before in uhh I think the 19 version but back then it still said it was charging but when I would unplug it, then I would see that it had depleted.

By deplete I don't just mean I'm getting 95-100 or something. It literally depletes to like 80 and below even depending how long I leave it plugged in after charging to full.

And oh yeah, 21 seems to be acting up on me now after a few days of fine operation... I seem to be experiencing some problems with my sd card? Some of my apps disappear and such. :\ And now I can't download anything from the market. I just get intermittent vibrates but no force close dialog or whatever. I've been attempting to download alogcat but yeah..it just stays perpetually downloading once I click "install" but no actual progress is shown and I feel the random single vibrations. I've rebooted several times and still can't..I'm not sure if it's kernel related but that's the only thing I've changed recently.

I'll be doing a clean install now :o
[Galaxy S I9000 Android Development] phoebusnz:
Thanks. Your versions always look great (far better than Voodoo to my eyes), this one's the best yet :) Definitely noticing the difference from earlier .21 release.

Keep it up, they're absolutely worth waiting for after official Talon release :).
[Galaxy S I9000 Android Development] pikachu01:
It seems more of a ROM related problem. No one's ever seen a problem occur like your phone did.
[Galaxy S I9000 Android Development] poyda69:
For some reason with V0.4.21 the camera programs would not work, I have the Stock Camera program and Camera360 ( both not working).
[Galaxy S I9000 Android Development] Rootax:
Thx you very much ! Could you release a 1000mhz version too ?
[Galaxy S I9000 Android Development] anoneemooz:
I sure hope it's not kernel related. Would hate to have to use something else. :o I hope a clean install fixes all this.

Nevermind about the random vibrations. Forgot I had tasker running and it was just tasker signalling profile changes and such since I have a profile related to whenever I would open Market.

The missing apps thing seems more like my launcher lagging or something I dunno. But after a few refreshes things show like the way they should again.

The battery thing though I've had for a while already since using SURFACE. At first I thought the discharging was related to the battery heating up but i tried observing it recently and feeling my phone and it didn't feel hot at all and yet it was still discharging. Maybe it's my battery that's acting up.
[Galaxy S I9000 Android Development] Tatsuya79:
Sorry I don't know how to do!

I'm no dev, just copy/pasted the code I needed for the version I'm using.

I'm even glad I could understand where the code was in Galaxian sources, took me an hour to find out. :D
[Galaxy S I9000 Android Development] pikachu01:
It's working fine for me.
[Galaxy S I9000 Android Development] Rootax:
Well, thx for your honesty lol :D
[Galaxy S I9000 Android Development] :
Nice Kernel. The sharpness and colors are amazing.
[Galaxy S I9000 Android Development] st4rk:
To guys with 'battery issues' it is a function of our battery to charge until 100 and then stop charging even if connected to the charger still.

They make it this way because if it continued to charge even though it was full it would wear down the battery and effect it's life span and capacity.

They only difference with .21 is that you are now seeing the truthful battery figures, where as before it was lying to you. :-)

If you want to get it back to 100, just unplug and plug it in again. Although mine seems to be lingering on 98 for ever but a few posts back someone said this it's also a battery feature.

Anyway 98 or 100 doesn't really make any difference..
[Galaxy S I9000 Android Development] poyda69:
I flashed Galaxian it worked, i then flashed back to 0.4.21 and it works now.

Go Figure!!!! :confused::confused:

Thanks.:D
[Galaxy S I9000 Android Development] anndalis:
everything is working smooth and superb with me.. just can't figure why I didn't use your kernel long time ago! thanks :)
[Galaxy S I9000 Android Development] theos0o:
Same here! :(
[Galaxy S I9000 Android Development] pikachu01:
That's the 2nd issue that Existz will try to fix. :)
[Galaxy S I9000 Android Development] jaiiscool:
The actual behaviour is something like this:

battery full

Discharge upto 95%

charge it back upto full

And cycle repeats......

So the battery should never go below 95%

But now whats happening is it does not start charging back and drops to levels way below (80, 70), this is something that definitely needs to be looked at....

Plz help team Talon......

existz ur kernel is the god of all kernels....
[Galaxy S I9000 Android Development] The Undertakerr:
Hi Existz,

Several people encountered a Deep Sleep with both 0.4.4.20 and 0.4.4.21 in a forum of my country.

I had one last night. I had an internet-page opened in the brower and left my phone lying for about half an hour. When I came back, ofcourse the screen was black, but wouldn't wake up anymore. I pulled the battery and put it back in to get it working again.

First time I ever had this with Talon. I am using 0.4.4.21.(No OC or UV)

I have logcat enabled now and will wait till the next deep sleep. IF it comes...

What could be the cause of this? Other people encountered it with both .20 & .21.
[Galaxy S I9000 Android Development] jeebspawnshop:
Just FYI;

It's called "Sleep Death".

"Deep sleep" is a natural state for the phone when it is idle.
[Galaxy S I9000 Android Development] existz:
What governor are you using? If its on ondemandX, switch to ondemand and see if it works better
[Galaxy S I9000 Android Development] The Undertakerr:
I didn't touch any of that, it's on OnDemand, everything untouched Talon-settings...
[Galaxy S I9000 Android Development] jaiiscool:
Today again I woke up at 91%.......
[Galaxy S I9000 Android Development] Gvdn:
Anyone could tell me how i can check if scripts in init. d are executed?
[Galaxy S I9000 Android Development] cwc289:
For me, sleep death only happened on custom rom, and i have changed to stock odex jvr for 3 days with .21 and no bugs found at all.
[Galaxy S I9000 Android Development] mak777:
I see that everybody tooks the battery off when your's phone hangs up. But there is a simplest way- just put the power on/blocking key for few seconds and phone will restarts himselfs.
[Galaxy S I9000 Android Development] fylim:
What is blocking key? Do you mean hold them down?
[Galaxy S I9000 Android Development] Rootax:
The power key.

I've a question about Zram. As I understand it, it compress ram, right ? But where the compressed data goes ? Still in ram ? Of so, what the point knowing that the SGS 1 is kind of ram limited ?

I must be wrong, if somedy can explain the benefit to me (I google it, I understand what is the benefit in some situation, but I've hard time understand it for the SGS)
[Galaxy S I9000 Android Development] mak777:
Yep ;) Just hold it down (power button) for few seconds and phone will reboot :) Sorry for my english in previous post.
[Galaxy S I9000 Android Development] pbecks1963:
lag / widgets / LMKSet

Hello Existz/Kodos,

I am on a Samsung Galaxy S with a custom rom, Dutch Gingerpower, bad to the bone. The dev of this rom uses Talon Kernel by default and advices everybody not to use a memory killer/free-er/taskkiller.

I just read this:

Lowmemorykiller Settings

Talon kernel includes Kodos96's "LMKSet". You can adjust the PRESET=X value in /etc/ram.conf ..

The presets are listed in the file, recommended settings are set by default. Reboot to take effect

Also make sure theres no "ramhack" scripts in /etc/init.d/ , if there is, delete it and reboot.

And was wondering if i should change the value X.. I have 20 widgets on 3 screens (go-launcher) and experience lag from time to time (not always). After a reboot the SGS and the widget run fast. But after 10 minutes or so the amount of free memory drops to <45 mb and that's when everything runs slower.

Note: even though i run the SGS on 1200 Mhz and have lagfixes on i still run into lag from time to time..

Any advice you can give me??

ps: i use the talondev-0.4.4.20-1200
[Galaxy S I9000 Android Development] JhonnyGo:
I think there is a bug with the giroscope, you can notice it browsing the sky with Google sky map.
[Galaxy S I9000 Android Development] Flynny75:
We don't have a gyroscope. You probably just need to calibrate your compass.
[Galaxy S I9000 Android Development] pikachu01:
Try installing 0.4.4.21 and using Memory Freak to set the settings (to your liking) and report back of your experience.

My setting is:

Talon stock

No change in Hidden App

160 in ZRAM

50 in swappiness

just in case you're curious.
[Galaxy S I9000 Android Development] JhonnyGo:
You're right, just recalibrate the compass and now it works perfectly.
[Galaxy S I9000 Android Development] Gvdn:
Just want to share, with the ramconfig that comes with the kernel when opening for example Facebook app it froze for 30 sec before i could scroll down. No i aplied supercharger script and Facebook and market are instant available. Dunno why just wanted to share and if anyone could tell me what i perhaps did wrong i would appreciate it.
[Galaxy S I9000 Android Development] Flynny75:
Could it be because the facebook app was already loaded in ram the second time? Running the SC script does not wipe your ram, or close anything. The facebook app always takes a long time to load on the first time for me.
[Galaxy S I9000 Android Development] Gvdn:
Well with talon mem Config it always takes long. Now it's instantly usable. With talon i also sometime had home button not showing unlock screen on first press. Had to hit it twice to get lockscreen. But as i said perhaps i did something wrong. I installed simplicity rom which came with supercharger and installed talon ontop. Never had real problem untilled i deleted supercharger when i installed latest talon as i saw it came with new memory tweaks.
[Galaxy S I9000 Android Development] kitkitfok:
http://xdaforums.com/showpost.php?p=16834051&postcount=4253
[Galaxy S I9000 Android Development] Rootax:
Thx you !
[Galaxy S I9000 Android Development] pbecks1963:
Thanks! It looks promesing!
[Galaxy S I9000 Android Development] Gvdn:
Can i use memory freak along supercharger? And should i use your settings?
[Galaxy S I9000 Android Development] jeebspawnshop:
As I understand it, Memory Freak changes the same things that Supercharger does.

The only difference is that Supercharger changes MORE things, and allows for much finer grained control than Memory Freak.

So the short answer is: No, there's no point using both. Use 1 of them, and stick with it.
[Galaxy S I9000 Android Development] The Undertakerr:
Supercharger LMK settings will be deleted anyhow. Same like Juwe's Script. Kodos' ram.conf in /system/etc overrules any of that scripts, so they just will not be executed.

I gave it a try, just for testing and flashed the supercharger script. After that I checked the LowMemoryKiller values by executing this command in the terminal:

cat /sys/module/lowmemorykiller/parameters/minfree

The result was Kodos' LMK values, not the ones of supercharger.

Same thing happened when I tried with Juwe's ramscript.

So I guess Kodos' made sure none of those ramscrips will interfere with Talon.

I think that's a good thing...
[Galaxy S I9000 Android Development] anoneemooz:
True that. When I was trying supercharger before, every after reboot my lmk settings remain as talon default. I guess if one would really want to use supercharger, you could manually edit the ram.conf with supercharger values. A ram.conf.bak is created anyhow so you could easily revert.
[Galaxy S I9000 Android Development] jeebspawnshop:
You guys are right, but all you need to do is simply run the Supercharger script after reboot.

It will then override ram.conf settings and maintain Supercharger values until the next reboot.

Since I only reboot my phone every few weeks, this is quite viable for people like me.
[Galaxy S I9000 Android Development] betoNL:
Auto Memory Manager app, doesnt get overwritten bij any script imho

Very satisfied with that app (AMM)

.
[Galaxy S I9000 Android Development] The Undertakerr:
Hmm that ain't exactly recommended by neither Kodos, nor Existz.

I think best thing we can do is stick with Talon settings; others might interfere.

Some values might conflict with each other.

Although I would appreciate some more free memory.
[Galaxy S I9000 Android Development] Gvdn:
That's really weird as i see a big difference in smoothness after i flashed back supercharger and deleted ramconfig from init.d or are supercharger settings allied afther u flashed it in recovery?
[Galaxy S I9000 Android Development] The Undertakerr:
Ramset from init d. is auto generated, so deleting it won't be of any use...

Ram.conf in /system/etc overrules everything at system startup, or you have to enable supercharger yourselve after every reboot like Jeebspawnshop said..

If you did not do that, it might have been your imagination that made your phone feel faster :-)
[Galaxy S I9000 Android Development] anoneemooz:
That's cus it runs after boot so it goes after ram.conf and overrides it instead of using init.d scripts. :) AKMO works the same for me. I stopped using it for now though to see how Talon does on it's own when it comes to memory management.
[Galaxy S I9000 Android Development] Timo Schmidt:
Hi there!

I get BSOD's with the current build with ondemandX and ondemand. With .20 it was the same issue.

Greetings

Timo
[Galaxy S I9000 Android Development] pikachu01:
Are you UVing too much?
[Galaxy S I9000 Android Development] TheBigX:
Hello there.

There's something i have to wonder about.

Many of you are using JVR as your primary ROM and dont have any problems about using the latest kernel...

But i've got a problem there.

I'm using 0.4.4.15 at this moment, because if i use any newer version, i get random reboots if i do something.

If i dont use the phone, it takes a long time to the issue i have.

Do someone know, why?

As declared above, i'm using a stock JVR rom.

Both, the 1,2 and 1GHz versions lead to reboots.

Thanks for your help.
[Galaxy S I9000 Android Development] Timo Schmidt:
Well i'll try out without uv now
[Galaxy S I9000 Android Development] pikachu01:
Are you using SGS kernel flasher to flash the ROM? You might have flashed the ROM using it (which does not wipe your UV/OC settings) and the newer version (you might've changed 1.2GHz back to 1GHz version?) have different UV/OC values that are needed to be set again.

Supercharger is not compatible with ZRAM/Swap enabled phones. Try using MemoryFreak and change the settings from there (or edit the ram.conf settings SuperCharge settings)

AMM might not write to the kernel space/userspace correctly, hence you're using two different settings in one phone. And the smoothness you get might be a placebo. Try using Memory Freak or editing ram.conf with the settings you chose in AMM?
[Galaxy S I9000 Android Development] TheBigX:
I used Odin to flash the ROM (as always).

My way to get this config atm:

Flashing JVR with Odin + repit 512

Flashing speedmod to get root (talon doesnt work)

Going into CWM and flashing Talon + convert the filesystem (system+data use) to ext4.

I've tried the "wipe voltage settings" in CWM. No change...

I never changed the Voltage settings. But if you want to, you could tell me, where the file for this setting is located.

Only #16 and above have this problem. Could it be the ext conversion, that ****s up my sys? (Sorry for the bad language :P)

Every other kernel i've tried doesn't lead to random reboots.
[Galaxy S I9000 Android Development] pikachu01:
Talon needs free space in /system to gain root access. You could flash a custom ROM that already has root (like Simplicity or Milky) to root your phone.

You can remove the voltage settings in /system/etc/init.d. Just erase a file named S_volt_scheduler (or something along those lines). Also remove other files in init.d as it might be clashing with the tweaks Talon kernel already has.

You should flash the kernel only with CWM as it wipes some files that can clash with Talon.

Ext4 conversion shouldn't be a problem. Talon auto-converts your system to Ext4 on first boot.
[Galaxy S I9000 Android Development] pbecks1963:
Thanks again Pikachu1! my sgs hasn't been this responsive in ages.... :-)
[Galaxy S I9000 Android Development] Gowtham34:
Hi,

I have a small problem in running the Talon Kernel. The voodoo lagfix is not getting enabled in my sgs. I am using SURFACE ROM V3.2. I tried talondev 0.4.3 and 0.4.4. I am not able to enable lagfix. I select the option to enable lagfix in recovery but still nothing happens in next boot. Same is with voodoo app. The folders are still in rfs and not in ext4 whatever i do...
[Galaxy S I9000 Android Development] hackeron:
As PIKAchuuu stated above.. These problems are usually that its not enough space on /system .. so try to remove some bloat .. and then try to convert again,..
[Galaxy S I9000 Android Development] Gowtham34:
I am using SURFACE ROM v3.2 which already very light and removed all unnecessary apps and data. When using speedmod kernel, there is no problem i can convert to ext4, but in talon nothing happens(though i feel its fast already).

Saw the issue tracker, it is still a pending and ongoing issue i think....
[Galaxy S I9000 Android Development] DerTeufel1980:
using memory freak has crashed my system really down. had to do a nandroid to get it back running. wiping dalvic, cache or anything other did not bring my system back. I always run into bootloops, after i applied the settings of memoryfreak. maybe I was hinting the ok button faster than memory freak was abled to save its data?
[Galaxy S I9000 Android Development] TheBigX:
There are only ondemandx and _ramset files. Should i delete it?
[Galaxy S I9000 Android Development] pikachu01:
Look at the logs inside /sdcard/voodoo/. Does it have an error saying "model not supported"? This is happening on a few other ROMs too (like Milky) when the partition table is not compatible with Voodoo. It will be fixed soon:

https://github.com/existz/linux_gt-i9000-gb/commit/f9c0a8271d426ff22164b4389a6377562b6adf03

A release will be forthcoming in a day or two I guess.
[Galaxy S I9000 Android Development] pikachu01:
Not sure. Never happened to me before. Try reflashing the kernel through CWM?

Yeah, delete them. It will be regenerated by the kernel when you reflash it using CWM.
[Galaxy S I9000 Android Development] DerTeufel1980:
i was trying to flash talon and the midnight kernel. but i also ran into bootloops after that.

don´t know what really happend, did 2 reboots before by aplying changes, abd the third time it was as described.
[Galaxy S I9000 Android Development] pikachu01:
Talon, and then midnight kernel? Did you wipe your UV/OC settings before flashing midnight?
[Galaxy S I9000 Android Development] DerTeufel1980:
yes, by trying midnight, i was deleting everything possible from within recovery
[Galaxy S I9000 Android Development] polariscon:
one thing guys, if u using stock JVQ/JVR after flashing kernel try install busybox - that sorted lot of problems with lags and BSOD for me, now I set ZRAM to 160 and swapiness to 60, everything smooth like hell.