yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] burakgon:
Can I edit to 1400 mhz?
[Galaxy S I9000 Android Development] existz:
No, kernel is either only up to 1ghz or 1.2ghz, depending which version you are on. Only can u adjust voltages higher if u need to, it would be the same if you had VC+, with free version it doesn't have the option in the app, but you can still raise it up to 50mv above default via sysfs file since the kernel actually supports VC overvolt.. its just a missing option in the free app, if you had the paid version of VC, you still couldn't go above the kernel max CPU clock
[Galaxy S I9000 Android Development] nedooo:
Don't know was this reported before, but I had problem with 0.5.1-RC1 and new Android Market (FC after trying to install anything), when I flashed Semaphore it works normally. :confused:
[Galaxy S I9000 Android Development] existz:
Nothings changed (in alonggg time) that would effect this, no other users are having any issues, something else is causing it...try wiping cache/dalvik cache and clear market data
[Galaxy S I9000 Android Development] pikachu01:
Clear your data from your market and try again? The new market is always iffy and I'm not sure if it caused by the 30MB limit (as Semaphore can enable the >30MB cache tweak)
[Galaxy S I9000 Android Development] Proelio:
Battery life isn't so good.
[Galaxy S I9000 Android Development] Tatsuya79:
Battery life is really good.
[Galaxy S I9000 Android Development] burakgon:
This is not stock colors :(

This kernel is holy good. But give us a stock color version with no speedmod or voodoo please...
[Galaxy S I9000 Android Development] Tatsuya79:
My phone rebooted while transferring a file with MTP connection (kies mode).

It happened randomly these past days: sometimes can't access at all (unidentified driver in windows), sometimes works fine.

Not sure if that's recent kernel commits or JVT yet... anyone noticed this?

@burakgon: Sorry I'm not going to make an additional version with stock colours. I think speedmod and Lukiqq modifications are an improvement over that.

Why do you think it's better? is it just because you want max sharpness?
[Galaxy S I9000 Android Development] saszseb:
What to do, if I want to grab an app. (>30 MB.) from Market using Talon kernel?

(I've read "Market issue" on XDA).

Thanks.
[Galaxy S I9000 Android Development] rlorange:
Had a reboot while clearing zram.

**Simply Honey 5.1 JVR, Talon kernel & Tegrak OC app 1.36ghz@1340mv**
[Galaxy S I9000 Android Development] pikachu01:
Revert to the old market. Solved it for me :)

Known issue. It'll be fixed in the next iteration.
[Galaxy S I9000 Android Development] rlorange:
Ok great thanks... Hey I was wondering if anyone if you help me with a truly bizarre anomaly. While flashing talon on a friends phone the screen colors changed to a crazy pastel over gamma-ed situation. i'm guessing voodoo color hack has gone screwy but it's persisting across kernel and rom flashes. Does everything in the root directory get wiped in a odin flash with repartition?

Everything else on this phone is perfect. It happened during a failed superuser sun update and had stuck like that. If I use voodoo app I can shift the gamma right down and it looks better but then the screen goes green if I go too far. This very odd indeed.

**Simply Honey 5.1 JVR, Talon kernel & Tegrak OC app 1.36ghz@1340mv**
[Galaxy S I9000 Android Development] pikachu01:
Yes, shifting too much will result in the green gamma-ed screen. It's a known issue.

Yes, everything gets wiped with an Odin repartition flash. The problem here is not kernel/ROM as long as the kernel/ROM supports Voodoo Color, you'll get an almost the same setting across it.

The only way to reset it is to wipe the data of Voodoo Control and then restart. It'll go back to the default Voodoo configuration (which might or might not have the green gamma issue)

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

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

The result of that is included in ThunderBolt! (my sig).
[Galaxy S I9000 Android Development] sherpa25:
As MemoryFreak has been deemed obsolete in v1.5 and up, is there still use for it (i.e. do the Clear Buffer and Clear ZRam functions have any use)? If not, can I just delete/uninstall it? Sorry, not sure if this should be under Talondev or Thunderbolt!.
[Galaxy S I9000 Android Development] pikachu01:
It's only obsolete if you're using ThunderBolt!

I'm getting existz to implement the LMK/OOM setting that I've done into mainstream Talon ;)
[Galaxy S I9000 Android Development] hackeron:
Been using cm7 for a while now.. But

Talon as always is tempting to go back to =)... JVT+talon+tweaks.. hmm.. I think ill flash this later and make a comparison to cm7 or something.
[Galaxy S I9000 Android Development] MaoJie:
Hi existz,

I have used several kernels but somewhat still considered new to this. I can feel the difference in your kernel and still want to support your kernel. I'm currently on the 5.1.4 1.2Ghz version for I9000. I'm running stock JVS ODEX ROM, can you recommend me a version of the kernel that I can use that is the most suitable for my version of ROM?

Also, I have read about the memory leak issues, if I set zRam to 0, does it solve the memory leaks issue? Thanks in advance. :)

Cheers
[Galaxy S I9000 Android Development] elghouchd:
Can anyone give me any tips on how to get the most battery out of this kernel? Thanks!
[Galaxy S I9000 Android Development] jeebspawnshop:
Same as any other kernel;

1 - Undervolt it, but not by too much

2 - Disable live wallpapers

3 - Remove all widgets

4 - Lower screen brightness

5 - Remove any app-killer apps

6 - Apply pikachu's Thunderbolt tweaks

Bam! E Z!
[Galaxy S I9000 Android Development] s30ckf:
1 - Undervolt it, but not by too much Ticked

2 - Disable live wallpapers Ticked

3 - Remove all widgets Ticked

4 - Lower screen brightness Ticked

5 - Remove any app-killer apps Ticked

6 - Apply pikachu's Thunderbolt tweaks XCross, correction: Apply pikachu's TB tweaks v 1.5.1
[Galaxy S I9000 Android Development] existz:
Latest RC1 should work fine on JVS.. as for the mem leak, the issue is still reproducible even disabling zram..although it does help mask it.. You can try pikachu01s thunderbolt tweaks, most report it solves the issue, but some also say its to aggressive.. it just depends on your use.. Currently pik is working on new lmk settings, once he finds a good medium, and it does in fact prevent the issue, then ill add those as default lmk settings
[Galaxy S I9000 Android Development] shaarky:
I disabled regular reboots after two days, however it appears to be a mistake. Yesterday I experienced huge slowdown of my mobile, drop caches didn't help at all - I had to reboot phone again. (JVT ROM, Picachu's tweaks, 0.5.1RC1 kernel)
[Galaxy S I9000 Android Development] rlorange:
Yeah this is the sacrifice we make for the benefits of talon... Seriously tho i.e. don't understand the issue people have rebooting beyond the purely ideological argument that we shouldn't have to. My phone takes 30 seconds to boot.

**Simply Honey 5.1 JVR, Talon kernel & Tegrak OC app 1.36ghz@1340mv**
[Galaxy S I9000 Android Development] sherpa25:
30 secs is good enough for me....as long as that means the phone becomes totally responsive already. For me, regardless of when I had it rooted or stock, in 30 seconds it only start to show the homescreen refreshing and setting up the widgets, so it takes like more than a couple of minutes or so.
[Galaxy S I9000 Android Development] pikachu01:
Which ThunderBolt! version were you using? The 256HP one?

I'm running a beta currently. Are you interested to join it? :)
[Galaxy S I9000 Android Development] MaoJie:
Thank you, phone is good now :) I will try the tweaks again. Used to crashed my ROM because I deleted something wrongly.. LOL
[Galaxy S I9000 Android Development] :
any eta for rc2 or final?
[Galaxy S I9000 Android Development] existz:
Hopefully will have RC2 up pretty soon... waiting till pikachu01 gets some new lmk settings tested (which original talon settings will still be available via new preset in MF) .. which work is still being done on oc module, but that will probably be a little bit before its even testable, then in a release

But once new lmk settings are added and released in RC2, and if it proves to fix/prevent the memory leak as bad, then we should be on track for a final 0.5 release.. probably won't make it a v1.0 release until oc module is added and everything tested reports back good and stable ..but we are getting close ..those are about the 2 only big things left before a final stable version
[Galaxy S I9000 Android Development] hackeron:
When I flash Zips from cwm i have to manually mount system and data everytime,or else they won't get flashed, I remembered having this issue long ago but now it's here again?
[Galaxy S I9000 Android Development] existz:
It never changed, it all depends on the updater-script in the zip...some work, some don't (usually some themes from the kitchen)
[Galaxy S I9000 Android Development] hackeron:
Next Q,

I set my UV settings in voltage control. But after every reboot they are reset to default settings again..

And Ive pressed save profile and also, apply settings at boot.

Im running stock JVT with latest talon + thunderbolt tweaks latest beta. ( cant remember if this problem was before applying the thunderbolt tweaks but it might have been) .

I have tried to fix permissions in cwm but it didnt help anything. Any ideas?
[Galaxy S I9000 Android Development] pikachu01:
You might have a busybox issue. Try looking at Android optimization tips and look for busy box :)
[Galaxy S I9000 Android Development] hackeron:
Worked thx :P
[Galaxy S I9000 Android Development] zenosteam:
witch version of busy box do you recommande?
[Galaxy S I9000 Android Development] jeebspawnshop:
Get Busybox from Market (by stericson) and install latest, which is 1.19.2.
[Galaxy S I9000 Android Development] existz:
0.5.2.1 Public Test

UPDATE

0.5.2.1 Public Test

- ext4: fix memory leak in ext4_free_branches

- newmail's deep sleep detection scaling patch

-- limits sleep max freq to 800mhz

- initial support for semaphore oc module (up to 1.3ghz)

-- no oc (1ghz) by default, use script to OC

- cpuidle: extend cpuidle and menu governor to handle dynamic states

NOTE

This is only a test for the initial support for OC module. You may need to

adjust voltages..etc.. There may or may not be any issues, so beware!

To overclock, extract the oc-scripts.zip and use the preferred script

of your choice in /etc/init.d/ . Also make sure to set permissions on

the script so it works!. We will have the option to adjust oc via app

shortly, so just use the scripts for now. As of this test it still uses

normal Talon LMK settings, once pikachu01 is set on some new LMK

settings and they have been tested to be ok, I will include them in

the next test/release.

Thanks to stratosk for creating the module, and big thanks to shane87

for his work on fixing deep sleep patch and putting the working touches

on getting oc module to work with Talon..plus all his work on MF!
[Galaxy S I9000 Android Development] jeebspawnshop:
Brilliant, man! Your constant work and attention is much appreciated by us all ;)
[Galaxy S I9000 Android Development] Perka:
Flashed first with kernel flasher all ok. Flashed in cwm, fc on calendar o_o,

Running odex jvt
[Galaxy S I9000 Android Development] :
can i use control freak with your v0.5.2.1? or not? i have set max freq, gov and shed with this app (init.d script).
[Galaxy S I9000 Android Development] existz:
No, only way to change max clock for now is to use the scripts, the module has to be loaded/unloaded, and certain parameters set.. as of right now no app does this, but shane87 is working on adding it to Control Freak..it will be released once he does, so until then just use the scripts to set max clock..you can use Control Freak or Voltage Control to adjust voltages if you need to
[Galaxy S I9000 Android Development] Tatsuya79:
0.5.2.1 Public Test - Neutral Colours Version

-Reverted Voodoo Colour Gamma Hack

-Speedmod MDNIE

-Galaxian OLED panel values

-Custom Sharpness in-between Speedmod and Samsung

-Compiled with Linaro GCC 4.5 2011-10 from today

thanks hardcore, Lukiqq and Talon devs :cool:

Fixed version HERE
[Galaxy S I9000 Android Development] Tatsuya79:
O/C module seems to be working (had to change the path in sema_mod/makefile for it to compile, lost some time on this I'm noob lol).

I'm using the 1200 script and different programs react strangely: voltage control is showing 1200mHz as current real time speed while Systempanel app display 800mHz max. :confused:

Anyway playing Riptide GP seems smooth so the o/c must be working, will try it more.
[Galaxy S I9000 Android Development] existz:
lol, yea theres actually info added in the build script, as well as a new commit for the notes on building the oc module

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

But you can do this via adb shell or term emu to see what the actual device/kernel max clock is to verify, if it shows 1200/1300 then its working correctly

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
[Galaxy S I9000 Android Development] stratosk:
You should use these lines in script:

rmmod cpufreq_stats

insmod /lib/modules/whatever_oc_module_called.ko

sleep 1

insmod /lib/modules/cpufreq_stats.ko

echo 1200000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

With this apps that based on freq_stat table will show correctly frequencies and the last line will ensure the scaling_max_freq (during transition the max frequency will go to L1 state = 800Mhz)
[Galaxy S I9000 Android Development] Tatsuya79:
lol I read those lines and didn't understand it was the folder name at that time... :o

Your command give me 1200000, so that's ok for the max but I wonder if despite that the cpu isn't actually going above 800mHz.

That's what Systempanel says in its monitoring while I'm moving the active Apps/services list up and down (which usually bump the CPU at full speed, here it shows 800 max with an empty space to 1200 the bar never fills).
[Galaxy S I9000 Android Development] existz:
You can verify by using adb shell while putting load on the device

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq

As long as this shows its going to 1200 your good, despite what any app says, but if its still limiting to 800, let me know because it could be something due to deep sleep detection patch...Also, if this is on your own custom version, try with official Talon and see if it does the same thing..so we can narrow it down
[Galaxy S I9000 Android Development] Tatsuya79:
Thanks, I tried this but it doesn't help with this app, still shows 800 max in monitoring.

This always give me 1200000, even if CPU is idle.

I tested some games which seems fast so I assume it's this monitoring app.

Can't test standard Talon as I'm soon out of battery, perhaps later.

Thanks for the help. :)
[Galaxy S I9000 Android Development] Mopral:
I just try 0.5.2.1 neutral colors

I have weird things after pulling oc-1200 in /system/etc/init.d folder:

-control freak still show 1000MHz as max frequency (but antutu and quadrant see 1200MHz as max frequency)

-control freak does not see default voltage for this 1000MHz
[Galaxy S I9000 Android Development] existz:
Try with official Talon...cannot support anything I dont compile.. Also make sure you have no other scripts or no other app is trying to set something different..So make sure to clear any OC settings from previous build
[Galaxy S I9000 Android Development] Mopral:
Just try with official one and all works fine!

(I always clear all uv/oc settings and init.d folder before flashing a new kernel)

I prefer neutral colors so I hope that Tatsuya will fix this issue...
[Galaxy S I9000 Android Development] existz:
@Tatsuya

One thing that pops to mind, make sure in your config that CONFIG_CPU_FREQ_STAT=m ... the issue Mopral is reporting (and the issue you had) sounds like something screwy with the cpufreq stats driver...normally its set =y, but with the oc module it must be set to =m (its compiled as a module because it needs to be loaded/unloaded each time the max clock is changed).. Also after you compile make sure it creates the module in usr/initrd_files/lib/modules/cpufreq_stats.ko
[Galaxy S I9000 Android Development] Mopral:
just try to apply my old uv settings on official one: phone freeze and restart and then stuck on bootloop
[Galaxy S I9000 Android Development] Tatsuya79:
I have CONFIG_CPU_FREQ_STAT=m but I don't have cpufreq_stats.ko in usr/initrd_files/lib/modules/.

I have semaphore_oc.ko though... :confused:
[Galaxy S I9000 Android Development] pikachu01:
I've also encountered that. It's normal since how the CPU handles frequencies are a little bit different than stock.

Try reducing your UV on your 100MHz (or was it 1GHz) a bit.
[Galaxy S I9000 Android Development] Mopral:
The weird thing is that I do not apply uv setting on boot so phone should have restart on default voltage...
[Galaxy S I9000 Android Development] existz:
Fixed an issue with the build script, not sure if this would have contributed to your problem or not, but you can try pulling in latest changes and see
[Galaxy S I9000 Android Development] Tatsuya79:
Ok I cloned the git twice (messed things up by using make menuconfig before launching buildgalaxys.sh), I mimicked the same folder structure and it seems to be alright now.

I get the cpufreq_stats.ko but I can see an error about semaphore_oc.ko while building the BigMem version..?

Anyway I tested the standard "not BigMem" version and I can change it to 1000 or 1200 with scripts now without the issues I had before.

Tell me if BigMem is OK.

Thanks a lot Existz for helping, sorry to have spammed your thread with unrelated stuff. :o

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Forgot to mention Supercurio made his new in development colour correction tool compatible with I9000. You can grab it here. It helps slightly with the dark greys for now.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

0.5.2.1 Public Test - Neutral Colours Version

-Reverted Voodoo Colour Gamma Hack

-Speedmod MDNIE

-Galaxian OLED panel values

-Custom Sharpness in-between Speedmod and Samsung

-Compiled with Linaro GCC 4.5 2011-10 from today

thanks hardcore, Lukiqq and Talon devs
[Galaxy S I9000 Android Development] :
Thanks so far, but the colors are bad against your 0.5.1-RC1 version. maybe there is something wrong...
[Galaxy S I9000 Android Development] Tatsuya79:
Just double-checked and don't see anything strange.

My reference pictures look the same on my screen and I verified the code I always paste from the same files, it's here (gamma22 from lukiqq and speedmod mdnie after reverting the voodoo commits).
[Galaxy S I9000 Android Development] :
sorry, my fault... i redownload your kernel and flashed it... now the color is normal... thanks :-)
[Galaxy S I9000 Android Development] existz:
0.5.2.2 Public Test

UPDATE

0.5.2.2

- fixed unsupported kernel error with MemoryFreak

To overclock, extract the oc-scripts.zip and use the preferred script

of your choice in /etc/init.d/ . Also make sure to set permissions on

the script so it works!. We will have the option to adjust oc via app

shortly, so just use the scripts for now. As of this test it still uses

normal Talon LMK settings, once pikachu01 is set on some new LMK

settings and they have been tested to be ok, I will include them in

the next test/release.

Thanks to stratosk for creating the module, and big thanks to shane87

for his work on fixing deep sleep patch and putting the working touches

on getting oc module to work with Talon..plus all his work on MF!
[Galaxy S I9000 Android Development] :
i have tested memory freak. no problems with Tatsuya79 0.5.2.1 edition.
[Galaxy S I9000 Android Development] existz:
Its was a talon only issue, build script didn't catch the kbuild version for some reason ...and MF checks this to verify ..so it wasn't there and was causing it to error out
[Galaxy S I9000 Android Development] zenosteam:
i was on 0.5.1-RC1 i tested i falshed 0.5.2.2 and i have a bootloop what wrong i have try script cleaner but it's the same help
[Galaxy S I9000 Android Development] existz:
Try reflashing and make sure to remove oc/UV scripts
[Galaxy S I9000 Android Development] zenosteam:
i will test

edit : cool it's work thanks mate
[Galaxy S I9000 Android Development] rom-g:
Same here...

In updater-script this line doesn't seems to work with the Talon Kernel :

mount("MTD", "system", "/system");

It only works if i change it to : mount("ext4", "/dev/block/stl9", "/system");

Then => no need to manually mount /system before applying zip. But /system has to be ext4.

FYI : The MTD mounting method is working fine with the other kernels i tried (Semaphore, Cf-Root, Speedmod).
[Galaxy S I9000 Android Development] jornbjorn:
problem with voltage control... wont save scritp as startup
[Galaxy S I9000 Android Development] cba1986:
There is a way to restore the original sharpness and colours?
[Galaxy S I9000 Android Development] existz:
Its a busybox issue, not kernel issue.. make sure to use 1.17 or 1.19... alot of roms use 1.18 but it does not include runparts, so scripts are not executed...
[Galaxy S I9000 Android Development] Valinorian:
Ok so i installed stock JVT. Then installed CF-Root. Did not convert to Ext4.

I installed TalonDev. Started converting lagfix voodoo at the start. After that getting bootloop :(

Using 0.5.1 RC1 1200mhz

Can get in recovery but if i click something it gets stuck.

Edit: ok, nevermind, was able to go back to CF-Root by using Odin. Flashed Talon again and no bootloop.

EDIT2: Everytime I do a wipe data/factory reset from cwm I get bootloop :( Accessing cwm works, flashed 0.5.2 still same problem :(
[Galaxy S I9000 Android Development] existz:
Simple answer, no.... you would have to modify the source code yourself and recompile the kernel...but if u look 1 page back, Tatsuya has a non-voodoo color version he made posted
[Galaxy S I9000 Android Development] cba1986:
OK. Thanks.

I will try it.

Another question. There is a way to raise the OC beyond 1.2?

---------- Post added at 04:42 PM ---------- Previous post was at 03:44 PM ----------

This.

123456789
[Galaxy S I9000 Android Development] existz:
As of right now only 1.3ghz, that's all the new oc module supports...just use the 1.3ghz script instead... Once we get the module and voltages fine tuned and Shane gets support added to his app ill add half steps up to 1.4ghz (ie 1200, 1250, 1300, 1350, 1400).. you get the drift
[Galaxy S I9000 Android Development] existz:
0.5.2.3 Public Test

UPDATE

0.5.2.3

- cpufreq: lower voltage a notch for 1300mhz step

- cpufreq: introduce 1120mhz oc version (experimental)

-- added new enable_oc_1120 script in oc-scripts.zip

To overclock, extract the oc-scripts.zip and use the preferred script

of your choice in /etc/init.d/ . Also make sure to set permissions on

the script so it works!. We will have the option to adjust oc via app

shortly, so just use the scripts for now. As of this test it still uses

normal Talon LMK settings, once pikachu01 is set on some new LMK

settings and they have been tested to be ok, I will include them in

the next test/release.
[Galaxy S I9000 Android Development] zenosteam:
thanks for keeping the good work
[Galaxy S I9000 Android Development] sherpa25:
quick question... if installing 0.5.2.2 bigmem (w/c I believe is already 1.2GHz), is the oc-script still needed to activate oc'g to 1.2GHz?
[Galaxy S I9000 Android Development] pikachu01:
All Talon CWMs come with 1GHz by default now since OC scripts are available :)
[Galaxy S I9000 Android Development] sherpa25:
Right! My bad, was correlating bigmem w/ 1.2GHz :D

So is this correct?

1. flash Talondev 0.5.2.2, reboot

2. 'i9000 restore'

3. Thunderbolt! 1.7.2

4. remount i9000

5. oc-script
[Galaxy S I9000 Android Development] pikachu01:
Yup, that's about right :)
[Galaxy S I9000 Android Development] trungdaika:
Sr for the noob question but how do i apply the Oc scripts?