yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Rebel2k:
You just have to choose the one you want from the archive and copy it in /system/etc/init.d and give it execution permission with your favorite file explorer (in root mode). Then reboot and you're in! :)
[Galaxy S I9000 Android Development] trungdaika:
But the tem + cpu pro only show 1Ghz.

And how do I set the governer?

Can I use setcpu as well.
[Galaxy S I9000 Android Development] Rebel2k:
Are you sure you set the execution permission on the file? That's strange, it should show the good speed if yes. Which version of busybox do you have?
[Galaxy S I9000 Android Development] devianceluka:
Hello!

enable_oc_1300 doesnt work for me. It makes a freeze after "loading talon" with black screen. Does that mean my device is unstable at 1300? Because it is perfectly stable at 1200, and I think it was stable 1300 on CM7 also few months ago when I tried.

enable_oc_1200 works perfectly though.

Best Regards,

Luka

EDIT: my suggestion would be to make a 1300 script with 1300 step disabled but max freq still 1300 so we can see if its a bug or instability. We can enable and save it as boot anyway when its working.
[Galaxy S I9000 Android Development] existz:
Its just unstable...I know quite a few people running it at 1.3ghz... Remember, this is not like cm kernels, it does not have the extra 1ghz and up steps (ie ....800/1000/1200/1300), instead it just replaces max clock so its...(800-1300) so those extra steps are not there to take the load off the CPU.. So in this case, it actually has to be a whole lot more stable than on cm kernel.

Also, there's no way to load the module and not set the max clock, as it actually replaces the max clock...so when you use whatever script, it replaces 1ghz with that step...(ie if you use 1.2gh, it actually replaces 1ghz with 1.2ghz, so the steps become 100,200,400,800,1200... if you use 1.3ghz, it becomes 100,200,400,800,1300)... which the gap from 800-1300 might just be to much and is simply not stable on your device... if 1.2ghz is working, then its not the module .. which as I mentioned, I know quite a few who run at 1.3ghz fine... it might be just about getting the voltages right on your device. Make sure to always remove oc/uv settings when switching scripts
[Galaxy S I9000 Android Development] existz:
If its showing 1ghz then either 1 of 2 things are happening, are both...

1) make sure to set executable permissions on the script after placing it in /etc/init.d/

2) the script is not getting executed, make sure your using the correct version of busybox, 1.18 does not have runparts so it will not run scripts..use 1.17 or 1.19
[Galaxy S I9000 Android Development] pikachu01:
Existz, check this out!!

https://opensource.samsung.com/community.do?menuType=support&qId=3

Official Galaxy S git :D
[Galaxy S I9000 Android Development] hackeron:
Since we dont have full sources its still rather limited what can be done to improve the phone? Cm7 and talon and your tweaks has taken the phone really far .. but What more can be done.. really.

I think OFficial JVT will be final firmware for our phone. Since it has now been released on KIes also. Maybe they will release new sources also.. :D
[Galaxy S I9000 Android Development] existz:
Well, we actually do have full sources, or atleast all we will ever get, what we don't have is proprietary closed source drivers that Samsung probably wont release. There's actually alot that can still be done, remember kernel is only at version 2.6.35.13 (stock is 2.6.35.7) ..so there's still alot that can be done kernel wise, just will take some work.

Also, the point of Samsung now using git, is now we don't have to dig through 75mb of tarball.. git makes it a hell of alot easier/better for kernel devs ...for example, instead of me having to dig through 75+ MB of tar packages and diff'ing between source directories to merge in new updates, I can just pull in new changes from git with one command.
[Galaxy S I9000 Android Development] cba1986:
The voltages in 1300 are too low. I can get 1440 working perfectly on my phone using 1473mv. I used that freq for about two or three months without any problems.

But with this voltages i cannot even boot @ 1.3.

I know that are suicides voltages, but I don't mind burning my phone. ;).

Can you make a 1300 version with higher voltages?
[Galaxy S I9000 Android Development] cba1986:
now my phone is randomly shuting down when plugged to the USB.
[Galaxy S I9000 Android Development] s30ckf:
my phone also can't operate properly with 1.3Ghz (1350mv), it will reboot with no sign. Work pretty well in 1.2Ghz (1300mv)...
[Galaxy S I9000 Android Development] zenosteam:
i try to flash kernel 4 times but memory freak apk don't appear for me what wrong ?
[Galaxy S I9000 Android Development] pikachu01:
You have a busybox issue. See my sig for Android Optimization Tips. Ctrl f for busybox.
[Galaxy S I9000 Android Development] rlorange:
Try a lower voltage mine likes 1300mv at 1.3ghz

**Simply Honey 5.1 JVR, Talon kernel & Tegrak OC app 1.36ghz@1340mv**
[Galaxy S I9000 Android Development] s30ckf:
When the earlier version (v0.5.2.1), the mv for 1.3Ghz was 1300mv, but still same, it will freeze when using heavy apps like games...
[Galaxy S I9000 Android Development] Mopral:
With previous Talon-1200MHz releases (without oc module), My phone works with these voltages:

1200MHz - 1300mV

800MHz - 1150mV

400MHz - 950mV

200MHz - 825mV

100MHz - 775mV

But on latest Talon release, my phone freeze and restart each time I try to apply them
[Galaxy S I9000 Android Development] pikachu01:
With the OC module, the implementation is different with switching of frequencies. The robustness also changed and certain frequencies can only be undervolted to a threshold. For me, I need to reduce my undervolting for my 100Hz by 25mv. Not that big of a deal actually.
[Galaxy S I9000 Android Development] Mopral:
Thanks!

Just change 100MHz value from 775mV to 800mV and all seems to works fine
[Galaxy S I9000 Android Development] NickDunn:
picachu, could u pls share me your settings?

1300MHz - ??mV

800MHz - ??mV

400MHz - ??mV

200MHz - ??mV

100MHz - ??mV

thank you.
[Galaxy S I9000 Android Development] pikachu01:
I'm only using 1GHz with these values:

1GHz = 1225mv

800MHZ = 1125mv

400MHz = 925mv

200MHz = 800mv

100MHz = 775mv
[Galaxy S I9000 Android Development] rlorange:
@existz I know you have your own OC modules happening but I thought I should mention that tegrak has recently released source code for his oc app I believe, could be mistaken. But maybe might be worth investigating as its one app to control all oc /UV needs and those that have bought the app have the fidelity of 1mv increments and internal voltage control. Drop him a line. :)

**Simply Honey 5.1 JVR, Talon kernel & Tegrak OC app 1.36ghz@1340mv**
[Galaxy S I9000 Android Development] existz:
Ah, I've been in the fight to get tegrak to release sources for months now (on xda and gpl violations) atleast for the module source part.. as the module was actually signed with GPL license, but he would not release them.. this was main reason i wanted to do my own module or atleast get someone else to build it, as stratosk done .. so ill probably not use anything from tegrak, honestly after all the **** that we went through, i don't want anything associated with him.

But as for smaller increments than 25mV, it might just be simple as setting it in the app, which i would have to have shane87 add .. if it can't be, then ill look into adjusting it in the sources..
[Galaxy S I9000 Android Development] betoNL:
1.5 ?? Even when you run games like NFS Shift?

Anyway, in case you get stabilities issues, dont forget to report...

Can anyone overclock up to 1.3 and run NFS Shift for more than 5 mins?

NFS Shift is not really my game, but it is very good to test stability on overclocked devices.....

«»
[Galaxy S I9000 Android Development] Fr4gg0r:
I always flash with heimdall, reflashed the kernel but won't boot.
[Galaxy S I9000 Android Development] existz:
Did u come from rfs or ext4?... but either way u should be able to get into recovery ...if you came from ext4, try converting back to rfs then flash again, sometimes its picky about the ext4 u had before...also if you are coming from rfs, give it some time at talon logo because it will convert on boot... Also, just make sure your giving it enough time at the talon logo, with the voodoo it checks your filesystem and other things, sometimes causing it to stay there for a couple min.
[Galaxy S I9000 Android Development] Fr4gg0r:
I'm on ext4

flashed fugu

-flashed talon again, boots

-reboot also works

-reboot recovery stays at talon logo

-after that normal reboot also stays at talon logo
[Galaxy S I9000 Android Development] cink40:
When i used fugu and tried to switch kernel i always had problem (and others also - there is something in fugu kernel ehat causes problems when you try to change kernel...). Anyway i solved thah only with full flash with repartition and stock rom....
[Galaxy S I9000 Android Development] betoNL:
Lol....I can also overclock up to 1.6Ghz and it will remain stable and battery efficient AS LONG AS I dont do anything with the phone.....:D

But then, try running heavy apps and games

How are you testing stability btw?

«»
[Galaxy S I9000 Android Development] conqueror110:
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.

I'm on Juwe v5. Juwe is using his ram script. Does it mean that I've to remove it before installing the Kernel and Should I return it after installation. !!
[Galaxy S I9000 Android Development] st4rk:
Well personally i don't really use it to play games.. so in my general use so far it has been stable, i have used benchmarks to push the cpu and tested it using browser, music players (playing flac) and video players (playing 720p). Everything ok so far.. :-)
[Galaxy S I9000 Android Development] existz:
They say there's problems when going from fugu to a different kernel, only way to goto a different kernel is a full flash of a rom...
[Galaxy S I9000 Android Development] Atom960i:
It's rom from one Russian guy, i've just made it less heavy by uninstalling some crap.

Sure, i'll do some screens in next few days, but don't expect anything magician - after 10 mins using sgs the charge fell down to 98%.
[Galaxy S I9000 Android Development] madd0g:
Flashed from Semaphore, had RFS, works super smooth of all kernel yet :] Wi-fi works, BT works , wicked kernel !
[Galaxy S I9000 Android Development] jordane1993:
Hello I have a small question. I have kernel 2.7.3 dark core with the JVP in lagfix ext 4. should I disable the lagfix before flashing the kernel via the kernel apk samsung galaxy s flash, or I can flash directly without removing the lagfix can I reactivate?

the core is based on a DC lagfix of voodoo. thanks in advance ^ ^
[Galaxy S I9000 Android Development] genich1971:
can someone write down a suggested/tested OC/UV table, which balance between good battery, stability and responsiveness.

thanks in advance
[Galaxy S I9000 Android Development] lenny.chem.dat:
He guys;

is anyone else having problems with the light sensor on TalonDev 0.2.2?

I'm coming from a Romkitchen built JVP with CF-Root and flashed Talon over it. Now my light sensor doesn't work while the screen is on. It only changes the brightness when I switch the screen off and on again.
[Galaxy S I9000 Android Development] paratox:
that`s normal behavior on JVH source compiled kernels like this and all the others (fugu, tegrak, speedmod, ...).

only cf-root and supercurio with original JVP kernel (not compiled) have working auto brightness. until there is no official JVP release with source you have to choose what`s more important for you - features or auto brightness! ;)

@topic: love the new talon! perfect like the last version! :)
[Galaxy S I9000 Android Development] madd0g:
If you use TW, there's a quick switch to control manual brightness : press the finger on the notification bar and wait a bit , then you can slide to left or right to adjust the brightness :] Auto brightness is kinda useless, because it doesn't max out in the sun anyway.
[Galaxy S I9000 Android Development] Atom960i:
Lol, if i'm telling 'bout stability - i'm serious. I played Paradise island, Adrenaline 5 and 6, Speedx, Contract Killer. Surfed net via OpMobile, same time sitting in icq, listening mortplayer, skype in bckgrnd. 720p videos also. The only thing was not normal to my sgs is temperature: 52°C
[Galaxy S I9000 Android Development] wingg:
Great kernel. On 1.6 -after few voltage sets- full stability.

Quadrant 3200 (3d-1100), AnTutu system bench. 2660.
[Galaxy S I9000 Android Development] genich1971:
can you share your voltage sets?
[Galaxy S I9000 Android Development] iem1:
After flash JVP rom over ODIN, then Talon 0.2.2r2 my wifi doesn' t work. Otherwise good kernel. Keep going.
[Galaxy S I9000 Android Development] rlorange:
Oh dear such a shame with Tegrak... he does such great work and I understand he wants to make a dollar but he can't base his app around a linux kernel module and not share source. If only he followed supecurio with voodoo sound and realised he with still do well on the market with paid app restrictions. Shame cos his module is very good.

**Simply Honey 5.1 JVR, Talon kernel & Tegrak OC app 1.36ghz@1340mv**
[Galaxy S I9000 Android Development] jornbjorn:
i love the obsession with GPL here on these forums. Especially since most of the people here use some sort of pirated software, download mp3s/movies....
[Galaxy S I9000 Android Development] Tatsuya79:
I'm not sure I understand your post.
[Galaxy S I9000 Android Development] rlorange:
Hmmm very strange linkage of concepts here. Kinda like saying "Gee it's amazing that you wonder about the meaning of life since you don't believe in God"

**Simply Honey 5.1 JVR, Talon kernel & Tegrak OC app 1.36ghz@1340mv**
[Galaxy S I9000 Android Development] rlorange:
Well I froze tegrak oc app and used your 1.3ghz oc script and it's performing much BETTER! lol! Must have been some clash between app or extra overhead but my phone is snappier than ever.

**Simply Honey 5.1 JVR, Talon kernel & Tegrak OC app 1.36ghz@1340mv**
[Galaxy S I9000 Android Development] rlorange:
@existz

Is is possible to edit the oc module to a different value? Say make 1.3ghz 1.36?

**Simply Honey 5.1 JVR, Talon kernel & Tegrak OC app 1.36ghz@1340mv**
[Galaxy S I9000 Android Development] existz:
In due time, i will offer half steps (1200,1250,1300,1350...etc) once module is 100% and fine tuned
[Galaxy S I9000 Android Development] rlorange:
Cool bananas cos my unit loves 1.35ghz and runs it at 1325mv. 1.4ghz needs 50mv more and is not %100 stable.

**Simply Honey 5.1 JVR rom & Talon kernel @ 1.3ghz**
[Galaxy S I9000 Android Development] :
@existz

can you compile the wifi drivers from the new source (released by samsung)? Look at hardcore's speedmod kernel. He has compiled/implemented it in his new speedmod... thanks
[Galaxy S I9000 Android Development] Hrithan2020:
Any idea whether that fixes the Wi-Fi DHCP issue which a few people faced? [ Considering that, the issue came up even with stock kernel, I guess not? ]
[Galaxy S I9000 Android Development] existz:
Ive always used wifi driver from source...my guess is hardcore just used the precompiled module from Samsung initramfs..
[Galaxy S I9000 Android Development] cba1986:
Ot would be nice to have the ability to tune the voltages ourself. Every phone it's different.
[Galaxy S I9000 Android Development] existz:
What do you mean? You can already tune voltages with Voltage Control / Control Freak... or edit the S_volt_scheduler manually (there's a 50mV cap on overvolting) ..
[Galaxy S I9000 Android Development] existz:
0.5.2.5 Public Test

UPDATE

0.5.2.5

- updated lmk settings from Pikachu01

NOTE

New modified LMK settings should prevent memory leak, let me know how these work for you guys.., they are a little more aggressive than the recent talon LMK settings..

We are working out a couple bugs with new OC App, once its ready for release ill get a new test build up.. To OC, simply place script of choice in /etc/init.d/ and set permissions
[Galaxy S I9000 Android Development] Tatsuya79:
0.5.2.5 - Neutral Colours Version

-Reverted Voodoo Colour Gamma Hack

-Speedmod MDNIE

-Galaxian OLED panel values

-Custom Sharpness in-between Speedmod and Samsung

thanks hardcore, Lukiqq and Talon devs
[Galaxy S I9000 Android Development] cba1986:
I didn't know that. Thanks!!

The S_volt_scheduler file is in init.d?
[Galaxy S I9000 Android Development] sherpa25:
Yes. When you save settings as boot in Voltage Control, that file is created in init.d for running during boot.

---------- Post added at 06:11 PM ---------- Previous post was at 06:07 PM ----------

Thanks guys. When you say 'updated lmk settings from Pikachu01', does this mean I don't have to run again the latest Thunderbolt! v1.80 after flashing this? I ask because I noticed that I no longer have s98system_tweak in init.d after flashing this.
[Galaxy S I9000 Android Development] fishcake13:
sorry if its already looked at and answered... is anyone having BLN issue? i've checked all the file and everything....
[Galaxy S I9000 Android Development] lazy_ursache:
BLN working ok here with the last Talon!
[Galaxy S I9000 Android Development] existz:
BLN works, make sure your using Busybox v1.17 or v1.19, theres issues with v1.18 where it does not have runparts, meaning no scripts will get executed..so the scripts required to copy liblights..etc..for BLN to work will not get executed
[Galaxy S I9000 Android Development] cba1986:
How do i edit the S_volt_scheduler to add overvoltage to the 1300 feq before applying the script?

If i applied the script with that voltages my phone freezes instantly.
[Galaxy S I9000 Android Development] fishcake13:
so if i install v1.17 then reflash the kernel again should be all good?
[Galaxy S I9000 Android Development] existz:
IF thats the problem, yes..., also remember that certain features of BLN are required by your rom.., such as BLN for sms..etc.. Your rom must have a patched service.jar for BLN to fully work. (also make sure BLN is enabled via BLN Control app)
[Galaxy S I9000 Android Development] fishcake13:
thanks!

one more noob question... would busybox have effected my rom install?
[Galaxy S I9000 Android Development] cba1986:
Anybody ?

123456
[Galaxy S I9000 Android Development] flolep:
Only Low Memory Killer values have been taken from thunderbolt tweaks to be integrated in talon, but there are other tweaks in thunderbolt, so if the sys tweak is no longer in init.d, yes, flash thunderbolt again :-)

Sent from my GT-I9000
[Galaxy S I9000 Android Development] flolep:
Edit the script, look at the text bloc where it talks about "set UV" (uv equals undervolt) and put a -25 or -50 (25 or 50 mv more) value for the first range...

Like that :

echo "Set UV" | tee -a $LOG_FILE;

echo "-25 0 0 0 0 " > /sys/devices/system/cpu/cpu0/cpufreq/UV_mV_table

echo ""

echo "---------------"

Save, put all permissions, reboot, you're done. But pay attention please, overvoltage is dangerous ok.

Take care.

Sent from my GT-I9000
[Galaxy S I9000 Android Development] cantIntoCode:
Thanks for the neutral version ! :)
[Galaxy S I9000 Android Development] chiefy009:
Flashe captivate version doh

My back button stopped working ?
[Galaxy S I9000 Android Development] cantIntoCode:
Flash the normal version back again?
[Galaxy S I9000 Android Development] chiefy009:
Got it working now, trying to get 1.3ghz now, freezing and reboots though
[Galaxy S I9000 Android Development] cantIntoCode:
Yep, overclocking is nothing but trial and error. If I had the time I'd give it a good solid go but I guess I don't.
[Galaxy S I9000 Android Development] kmilof:
hey, im getting this message a lot

"sim card removed reboot phone"

with the last kernel, is normal? with the previous version nothing happened.

=/

hope you can help me.
[Galaxy S I9000 Android Development] Nash123:
I am 65 hours on the new kernelrelease and it is awesome. Memoryleak seems to be “fixed“.

Thanks to the devs who made it possible!
[Galaxy S I9000 Android Development] existz:
Nothings changed except lmk settings, so 99.99% of the kernel is the exact same, if it didn't happen on the last one, there's literally no reason why it should happen on new one..try reflashing kernel and wiping cache/dalvik cache, if that doesn't solve it, something else is going on
[Galaxy S I9000 Android Development] existz:
Thanks to all of you who reported back, so we can all agree they are better than previous? ... once Shane gets me the oc app ill get a stable release out...possibly 1.0 release... (as i cannot promise higher overclock will be stable for everyone, but 1ghz and possibly 1.2ghz should work fine for most people, giving voltages are tuned correctly)... then later on ill get half step oc clocks added
[Galaxy S I9000 Android Development] Vostradamus:
I might just be unlucky, but with the latest-but-one version I've had a "black screen of death" three times in a few days when going to wake the phone.

Didn't try the latest version 'cause I've read it's the same as the previous one with just a different lmk setting.

Reverted back to 0.5.1 RC1 and so far so good (knock on wood)

If it may be of any help, I was not using any overclock and/or undervolt.

Great kernel nonetheless though ;) :p
[Galaxy S I9000 Android Development] lazy_ursache:
Yes the phone is working very well with 0.5.2.5! This is the best version!:)
[Galaxy S I9000 Android Development] rodirodi:
I had "black screen of death" issue twice in last 24 hours on 0.5.2.5.

Didn't have this problem with previous Talon versions. I'm performing the same UV as before, just installing 0.5.2.5
[Galaxy S I9000 Android Development] hackeron:
no bsod's here.

hmm, what rom are you who get this using, and are you using tatsuyas speedmod color ver or default?
[Galaxy S I9000 Android Development] Gvdn:
It has been posted more then once to not blindly apply previous oc/uv settings when u flashed a new kernel release. Return to no oc/uv and see if it happens again. If not restart you oc/uv from scratch to see how far u get.
[Galaxy S I9000 Android Development] Vostradamus:
- sconcau extreme 9.0 Rom (JVS-based rom)

- JVT Modem

- tatsuyas version

Also, I had it happen again on 0.5.1 RC1 too a few mins ago.

It looks like it happens if I don't wake the phone up for an extended time (this time it was like 4 hours), but not always.

Does not seem to happen if the phone is charging, no matter how long I don't wake it up

EDIT: just noticed... I've taken a look at the battery usage graph: I didn't wake up the phone for about 4 hours, and it looks like during the last 2.5-3 hours it was somehow active (battery has actually dropped too, more than what it should have if the phone was really resting there doing nothing)
[Galaxy S I9000 Android Development] Tatsuya79:
I don't have this issue here, I'm on my version since I made it. (at 1200 oc)

Perhaps the BOSD happened when the deep sleep patch got implemented in Talon again? edit: (guess no, since it's not in RC1)

Make sure you don't have a script like the thunderbolt "screen off" one that could cause problem for a particular reason.

I had strange reboots more than a week ago and it was when I was using some live wallpapers (the ones with animated galaxy from Maxelus). Removed them and no problem since then.
[Galaxy S I9000 Android Development] Vostradamus:
Nope, I don't have anything like that

I'm using super wall lite live wallpaper, link: https://market.android.com/details?id=com.cellophanesoftware.superwalllite&feature=search_result#?t=W251bGwsMSwxLDEsImNvbS5jZWxsb3BoYW5lc29mdHdhcmUuc3VwZXJ3YWxsbGl0ZSJd

Been using it since forever (with previous talon versions too) and never had any issues, can we assume it's not the cause of the problem?

Anyway, I'm flashing the new sconcau extreme 10 rom now (JVT based), so I guess I'll have to experiment some more :p