yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] oswade:
Check the mirrors page for 0.4.1 etc.

BTW, running 0.4.1 now and backlights are stuck on when screen is on :(.

EDIT: weird, they went off eventurally. perhaps the timeout is just set really high :eek: either way.. hope it can be fixed!
[Galaxy S I9000 Android Development] pikachu01:
It's not for me. What ROM are you using?
[Galaxy S I9000 Android Development] mohnishism:
using juwe 5.1...talon kerel.3.1 1200..r ther ny side effects of over clocking??my phone is blazng fast rt now..ny side effects of overclcking?
[Galaxy S I9000 Android Development] petsasj:
where did you get 0.4.1.? and afaik the bigmem version is only for captivate. did you flash a wrong kernel by any chance?
[Galaxy S I9000 Android Development] astralmind:
Excellent, I'll give it a shot as soon as my battery is charged.

Consensus seems to be that EXT4 is not really that much of an improvement on this rom ? Any basic noob friendly settings I should be looking for ?

Thanks!
[Galaxy S I9000 Android Development] angiogram:
Video

Got problem when playing video. Can't stop. Have to take out battery and reboot.I'm from tiramitsu evo v5.2. When I flash back to voodoo kernal it's ok. any idea?
[Galaxy S I9000 Android Development] existz:
I will probably update to Speedmod color/sharpness in the next build, everyone ok with that?...
[Galaxy S I9000 Android Development] kalpik:
Would love that! Thanks :)
[Galaxy S I9000 Android Development] pikachu01:
Yes to speedmod color/sharpness fix.

How about efficient ext4 mount options and ext4 perfomance hacks?
[Galaxy S I9000 Android Development] aladin6:
Absolutely ;)
[Galaxy S I9000 Android Development] xtoad:
I prefer the brighter screen and dimming with Screen Filter if necessary...

Actually, the default as opposed to voodoo color.
[Galaxy S I9000 Android Development] st4rk:
Would be great if you could use his backup/format/reapply function that he has in his cwm mod as well..

Had some corruption on sd today and that is a really convenient way of fixing it without reflashing.. i just jumped to his kernel to do it then back to yours but would be great if you could add this as well?

As for colour i'm not too fussed ;-)
[Galaxy S I9000 Android Development] astralmind:
Installed and configured all good !

One question though: EXT4 through the CF App seems to convert everything to EXT4 and not specific sections, isn't that "dangerous" or simply needless ? I thought only a few basic items benefited from the EXT4 conversion.

Thanks :)
[Galaxy S I9000 Android Development] existz:
No its not dangerous, its how all other conversions worked before (froyo) with system, data, dbdata and cache as ext4
[Galaxy S I9000 Android Development] .:Crack:.:
is it possible to use Voodoo color and Speedmod (SAMSUNG_MDNIE i think) sharpness?

In my opinion that would be best
[Galaxy S I9000 Android Development] Tatsuya79:
From flashy to neutral colours this would be:

Samsung->Speedmod->Voodoo

This would be the same for sharpness strength.

I'm really happy with Voodoo stuff but I guess it's a matter of taste. A tweak in CWM would be perfect but I don't know if it is possible.
[Galaxy S I9000 Android Development] corps20k:
I flashed TalonDev 1.2.1 over Darky 10.1 Extreme Edition, I downloaded CPUSpy to see how much time is being spent on each frequency and it showed 100, 200 and Deep Sleep as "Unused States".

I then used odin to return to JVH, then Darky 10.1, I then checked with CPUSpy and it was using all frequencies. Flashed TalonDev over it again and again it's showing 100, 200 and Deep Sleep as Unused CPU States. I only got to undervolt -25 on each frequency as I was stress testing it.

Is anyone else getting the same thing?
[Galaxy S I9000 Android Development] existz:
Talon uses the ondemand governor, meaning it scales to max clock when there's load, when there's no load it drops to 100... so if ur stress testing or whatever then its only going to use max clock...when there's no load it will drop...it does not work like it did with froyo or conservative governor...it gets to max clock faster, giving better performance, and it drops to min clock quicker, giving better battery life...it does not have to scale through each frequency like before.

Plus cpyspy is not 100% in real time, so it might not be fully up to date..but as long as your doing something to put load on the cpu it will only use max clock ... the conservative governor (used in froyo) is very laggy with gingerbread...
[Galaxy S I9000 Android Development] ickyboo:
I can confirm what you say is true, very odd isn't it? I was going to just give up on this kernel til I saw your hint. Much thanks
[Galaxy S I9000 Android Development] zacharias.maladroit:
*subscribes*

concerning the WIFI reboot issue

I just did a test-compile and saw some

"array subscript is above array bounds" or "array subscript is below array bounds"

warning messages

perhaps fixing those or forcing the driver to compile with -Os (optimize for size instead of -O2) improves stability :)

getting a working kernel should be as easy as running the build-script and modifying the toolchain path, right ?

thanks !
[Galaxy S I9000 Android Development] aladin6:
82% in DEEP SLEEP with this kernel. Awesome battery life, never see this before! Thank you existz :)
[Galaxy S I9000 Android Development] zenosteam:
is it an update TalonDev 1.2.1 ? the thread is TalonDEV 0.2.1
[Galaxy S I9000 Android Development] fylim:
No matter what i do I can't get this kernel to boot. I just reflashed to stock DXJV9 and even with a factory reset, it just keeps hanging at the ANDROID animation.

Any ideas ?
[Galaxy S I9000 Android Development] nedooo:
Tried it, but still freezes at 1200MHZ, back to HC's SpeedMod.

Is there any mod that can bring stabile OC?
[Galaxy S I9000 Android Development] JhonnyGo:
HI there, just flashed this

REMOVED

but now the back key is wrongly mapped, in recovery the test key util say it is the same as the home button (102) but while in android, back key does nothing.

EDIT: My fault, sorry!
[Galaxy S I9000 Android Development] petsasj:
This kernel is for the i897 aka the Captivate. Why rush into flash things that are not for our phone and report non-existing bugs? Just wait for the OP to be updated.
[Galaxy S I9000 Android Development] pikachu01:
The i9000 ones are here:

http://berryfx.com/RobBeane/Kernel/i9000/Talon/
[Galaxy S I9000 Android Development] rayma6a30:
btw, could you please create a 1.12 ghz, 1.2ghz, 1.3ghz, 1.4ghz, 1.44 ghz, 1.5ghz and finally 1.6ghz together in one kernel just like the 0.2.2 r2 before. Sometimes more options is better than only one option. i'm using the 0.4.1 1.44ghz one, it wastes a lot of battery when running apps, i think if there're more steps, the cpu shouldn't lock on 1.44ghz only while overclocking. 3Q:)

anyway talon still the best kernel though;>>>
[Galaxy S I9000 Android Development] petsasj:
Taking 0.4.1 isn't "officially" up, can we hope to get 0.4.2? :P
[Galaxy S I9000 Android Development] .:Crack:.:
Well actually it is up. just not posted on xda yet.

take a look at http://talon.darkirc.info/
[Galaxy S I9000 Android Development] petsasj:
I know, hence my "officially" up comment.
[Galaxy S I9000 Android Development] gsw5700:
Just want to double check, can I flash this kernel directly using sgs flasher. I am currently on JVQ/Galaxian all ext4? Thx

Sent using geek power
[Galaxy S I9000 Android Development] petsasj:
It's a CWM .zip that you flash trough recovery.
[Galaxy S I9000 Android Development] pikachu01:
CWM is the recommended choice though no one will stop you from extracting the zimage and flashing. I would think that no support will be given if you do that.
[Galaxy S I9000 Android Development] Parkuu:
What's the diff between bigmem and no bigmem on versions?
[Galaxy S I9000 Android Development] gsw5700:
Thanks for replying quickly, CWM it is then, do I need to convert back to rfs first or does it recognise extra?

Sent using geek power
[Galaxy S I9000 Android Development] petsasj:
I've actually flashed Galaxian and TalonDEV back and forth with no conversion at all so should be safe to do.
[Galaxy S I9000 Android Development] gsw5700:
Thx dude

Sent using geek power
[Galaxy S I9000 Android Development] .:Crack:.:
and remember to download the -I9000 version!

There is no BIGMEM for I9000. But for cappy it has 353 mb RAM instead of 340.
[Galaxy S I9000 Android Development] pikachu01:
Bigmem gives more RAM but disables 720p recording.
[Galaxy S I9000 Android Development] petsasj:
It's only for the Captivate though, is it not?
[Galaxy S I9000 Android Development] .:Crack:.:
.........http://xdaforums.com/showpost.php?p=15491284&postcount=1195

two posts above yours.
[Galaxy S I9000 Android Development] petsasj:
...............I had read your post before it was edited, so i didn't know any new information was added, and look again.
[Galaxy S I9000 Android Development] gsw5700:
Now running Talon and looking good, fast 5m gps fix, BT looks

to be working, BLN, how do you find talon against galaxian?

Can I still flash directly back to galaxian using sgs flasher if I so choose?

Sent using geek power
[Galaxy S I9000 Android Development] pramathesh:
Can't use the same OC/UV values for 4.1 that i'd used for 3.1. Something which made me go back to 3.1. Existz mind shedding some light on this?

Here is what I'd been using for 3.1

800 ------> -25

400 ------> -50

200 ------> -75

100 ------> -100
[Galaxy S I9000 Android Development] Cy4n1d3:
I noticed the same and worked through the code, if I am correct theres a typo I guess. Have to check it out later though :)
[Galaxy S I9000 Android Development] Perka:
Hi you mind if I use your Kernel in my PerkaROM?

THX
[Galaxy S I9000 Android Development] petsasj:
Yes you can. I flashed Galaxian through Odin and it worked fine. However before flashing i used a cleaning script via recovery.
[Galaxy S I9000 Android Development] existz:
I've still got some work I need to do on the voodoo color, thats why I have not officially posted 0.4.1 for i9000, however it has been uploaded, so its an "unofficial" release and will not be supported. The framebuffer is a WIP, so some more porting needs to be done. Ill do what I can to get 0.4.2 up today or tomorrow for you guys.

Sent from my SGH-I897
[Galaxy S I9000 Android Development] Cy4n1d3:
I've left you a comment on github concerning the int_volt, not sure if I'm correct there.

Good job on the framebuffer though, still fiddling with color settings but apart from that - great :)
[Galaxy S I9000 Android Development] mawardi:
Yup. UV is so not stable on 0.4.1. Just give heads up before making it official. ;) 0.3.2 is awesome btw. I can UV 100MHz -175, 200MHz -150, 400MHz -125, 800MHz -75, and 1000MHz -50. On 0.4.1, I cannot even detect which UV freezed my phone.
[Galaxy S I9000 Android Development] pikachu01:
My UV for reference with 0.4.1:

100 MHz : -250mv

200 MHz : -150mv

400 MHz : -125mv

800 MHz : -75mv

1000 MHz : -50mv

Stable so far.
[Galaxy S I9000 Android Development] petsasj:
I believe the only difference between 0.3.2 T7 and 0.4.1 is voodoo sound v10.
[Galaxy S I9000 Android Development] mawardi:
I'm no expert but that's what I experienced. Maybe it's not UV freezing my phone.
[Galaxy S I9000 Android Development] existz:
Yea 0.3.2 and 0.4.1 are the exact same thing except voodoo sound 10

Also, notice in the changelog, there were some voltage tweaks...for some frequencies it was showing one thing but was actually another...I fixed them so they were correct...so you might have to adjust VC settings , this is normal ...for example, 800 step showed stock voltage, which is what it should have been...but was actually overvolted like 25-50mV, so you could probably UV alot more than normal...but that was fixed so it was actual default voltage. So now you probably wont be able to UV as much on 800...etc..check the git commits to see what all was changed

Sent from my SGH-I897
[Galaxy S I9000 Android Development] ramas123:
Who gives a fuc* how long it boots? What is matters how it works :)
[Galaxy S I9000 Android Development] rlorange:
Phone just ate through 23% battery for 2hrs music playback on 4.1... seems to have been stuck on 800mhz the whole time...

**Simply Honey3.8, Talon 0.3.2 t2 kernel1.4ghz**
[Galaxy S I9000 Android Development] zenosteam:
is there bigmem for 1900 gt?
[Galaxy S I9000 Android Development] lohho:
800hz @music is some state of deep sleep for hardware decoding, take it as a visual bug, its not really the 800hz.
[Galaxy S I9000 Android Development] existz:
No, just captivate...since we don't have an i9000 to test on, it would be hard to get the max memory without breaking something (ie FFC or whatever)..

But been messing with some new voodoo color settings and think I've finally got it...atleast its better looking, got rid of the yellow tint...will try to get 0.4.2 up tonite

Sent from my SGH-I897
[Galaxy S I9000 Android Development] Tatsuya79:
Did you manage to lower the amount of gamma in the dark greys?
[Galaxy S I9000 Android Development] existz:
I have not messed with the gamma..i personally do not see this issue..
[Galaxy S I9000 Android Development] zenosteam:
wow great news stay tuned :)
[Galaxy S I9000 Android Development] paratox:
how do i wipe the voodoo color settings? changing it in the app doesn`t resolve my issues. my screen is too dark. if i change gamma i get green screen. i`ve tried to reflash kernel, but htis did not help.
[Galaxy S I9000 Android Development] Tatsuya79:
Ok, as this gamma problem is hard to explain, I've made a badly compressed jpg to check if it is just my problem or something regarding Voodoo implementation.

Do you see all the dark trees black or full of green/blue/yellow artefact really distinctly?

(for me it's ok, totally dark here on Talon 3.1 but on recent 3.7 or 4.1 artefacts are everywhere, whatever I change in Voodoo control)
[Galaxy S I9000 Android Development] Hrithan2020:
Similar issue for me. It gets stuck in the highest possible clock speed. (when set to 100 MHZ, it uses 100, if set to 400 MHZ, it uses 400 etc..)..

Would love if this issue is fixed in 4.2..

? Can you please elaborate?

`

Yeah, I am getting the same issue, but only after the gamma values are changed. I am sure, this would get fixed in 0.4.2.

EDIT: Hadn't seen the picture earlier, the issue I am getting is different. The screen becomes green (like you find on 4-bit systems) , when you change the gamma values or after restarting the phone.
[Galaxy S I9000 Android Development] existz:
Lol im still not seeing it. Looks normal to me...but ill see what I can do

Sent from my SGH-I897
[Galaxy S I9000 Android Development] Tatsuya79:
OK, thanks for confirming it's not just me! :p

I went into flashing JVQ as I was still on JVP but the problem is still here.

I was trying to identify the code on git, but I don't understand much. There should be some lines giving the values of the dark greys or "black level" which aren't working, the values not following all the other higher tones.
[Galaxy S I9000 Android Development] Hrithan2020:
Sorry, I had a different problem. Had tried editing my post immediately after noticing the error, but my net went down..
[Galaxy S I9000 Android Development] existz:
So after messing with it some, yes, i do see it now...will def look into, now that i can replicate it
[Galaxy S I9000 Android Development] rlorange:
@ existz

I saw a new script in init.d and deleted it thinking it was rom based script spam it had lmk values in it.

Looking at your ram config file I now worry it was part of talon. I do believe it was s999ramset or something. Reflashed and it hasn't returned.

**Simply Honey3.8, Talon 0.3.2 t2 kernel1.4ghz**
[Galaxy S I9000 Android Development] pikachu01:
IT's _99ramset. It's an autogenerated file from the looks of it.

It has:

echo 0,1,2,4,6,15 > /sys/module/lowmemorykillter/paramters/adj

echo 2048,3072,4096,5120,8192,12288 > /sys/module/lowmemorykiller/parameters/minfree

echo 50 > /proc/sys/vm/swappiness

I did change the LMK to preset #7 because its smoother for me when playing games (like Farm Tower)
[Galaxy S I9000 Android Development] rlorange:
Ok thanks :) well mine has not regenerated since I deleted it... hmmm

Edit: tried changing the preset in ram.config hoping it might regenerate the script but nothing.

Could you pm me this file? Just rename it with. Zip at the end?

**Simply Honey3.9, Talon 0.4.2 t1 kernel1.3ghz**
[Galaxy S I9000 Android Development] currydude:
Just reflash the kernel LOLS, it'll regenerate then.
[Galaxy S I9000 Android Development] rlorange:
Of course I tried reflashing the kernel! More than once and it wont regenerate. I also tried editing ram.confg to a different preset hoping it would regenerate but it hasn't.

**Simply Honey3.9, Talon 0.4.2 t1 kernel1.3ghz**
[Galaxy S I9000 Android Development] currydude:
I'm not sure if it's just me but I seem to be getting higher battery drain with TalonDEV-0.4.1 and 0.3.2-T7

I will be sticking with 0.3.1 for now (Yes I know they are still test kernels, so I don't blame anyone! Just want to point it out :P)

Further observations:

- As stated earlier, battery drain "appears" to be higher while youtubing, music playback, browsing, etc. (idle/deep sleep is the same though, 8 hours 0% battery drain :P)

- Voodoo Color Implementation on 0.3.2-T7/0.4.1 is great! I don't know why people do not like it, I love it :)

- Fantastic job here and I'm glad Zach is also contributing (Will hopefully be moving back into the CM7/MIUI scene when exams are over) - Don't stop what you guys are doing!
[Galaxy S I9000 Android Development] currydude:
Try flashing Juwe11's RAM Script http://xdaforums.com/showthread.php?t=1111145 then reflashing the kernel :)
[Galaxy S I9000 Android Development] existz:
Rlorange, you should be fine, that script is autogenerated, but its sets the same thing ram.conf sets.. I haven't throughly went through kodos' latest changes, but I think its just a fail proof script that gets autogenerated on its own so it sets kodos' settings...

Sent from my SGH-I897
[Galaxy S I9000 Android Development] rlorange:
Ok thanks existz. But in the ram.config file there isn't the actual values for the preset anymore. But reading the script comments I think they have been moved to another file... anyways ill trust ya existz. Still I wonder why it hasn't regenerated since I deleted it and reflashed...

I would feel better if someone could post it for me :)

**Simply Honey3.9, Talon 0.4.2 t1 kernel1.3ghz**
[Galaxy S I9000 Android Development] currydude:
LOLS if you insist (See file attached)
[Galaxy S I9000 Android Development] rlorange:
Thank you :)

You didn't have to go the trouble of making a cmw3 zip. I know how to transplant system files with root explorer and set permissions.

**Simply Honey3.9, Talon 0.4.2 t1 kernel1.3ghz**
[Galaxy S I9000 Android Development] currydude:
No worries, sorry I jsut found a problem with the script. Please reflash the following:

EDIT:

Haha don't worry, it was no trouble, just took my previous script when I helped Juwe11 out with making a cwm zip file for his ram script.
[Galaxy S I9000 Android Development] rlorange:
All good did it manually :)

**Simply Honey3.9, Talon 0.4.2 t1 kernel1.3ghz**
[Galaxy S I9000 Android Development] currydude:
Haha okay :)
[Galaxy S I9000 Android Development] rlorange:
Weird that it didn't regenerate by itself with a reflash and cache /dalvik wipe... was that the only script that talon injected into init.d?

**Simply Honey3.9, Talon 0.4.2 t1 kernel1.3ghz**
[Galaxy S I9000 Android Development] currydude:
Yes, I believe it is. Better wait for existz for confirmation :)
[Galaxy S I9000 Android Development] rlorange:
Well thanks again :)

**Simply Honey3.9, Talon 0.4.2 t1 kernel1.3ghz**
[Galaxy S I9000 Android Development] zenosteam:
Talon 0.4.2 is it up ?
[Galaxy S I9000 Android Development] .:Crack:.:
Not for you if you're not a tester ;)
[Galaxy S I9000 Android Development] eli2412:
course :mad::mad::confused:,

is the only way to get to the end in good condition

thanks and keep up the good work in the core:):):):):):):)
[Galaxy S I9000 Android Development] petsasj:
Taking a note on your signature, i see you OC your GPU by quite a lot. 400@1200mhz, etc etc etc. Doesn't that cause overheating problems? I am using 300mhz approx in the top 3 scales and while playing the phone gets quite a bit hot. (Around 46 degrees centigrade). What about you?

And btw, how do you become a tester? :P By pm'ing exitz (which i did yesterday)?
[Galaxy S I9000 Android Development] Cy4n1d3:
I'm using maximum overclock across the board, from 100 to 1400 mhz. No problems.
[Galaxy S I9000 Android Development] petsasj:
Maximum overclock in the GPU i guess? And the phone doesn't get hot? Essentially my question is if the GPU can cause more overheat problems than already exist due to the CPU OC.
[Galaxy S I9000 Android Development] Cy4n1d3:
Yes gpu overclock. The phone gets warm but not hot. Hot means you can't touch the back with your fingers...
[Galaxy S I9000 Android Development] rlorange:
Its winter down in Australia... but come summer I will be dropping oc on both gpu and CPU!

**Simply Honey3.9, Talon 0.4.2 t1 kernel1.3ghz**
[Galaxy S I9000 Android Development] Rootax:
I'm sorry but, with what application do you oc the Gpu ?
[Galaxy S I9000 Android Development] zacharias.maladroit:
control freak

http://xdaforums.com/showthread.php?t=1072403
[Galaxy S I9000 Android Development] petsasj:
Just wanted to confirm what others have already said. When music is playing with the screen off, the 800mhz scale is selected. It seems a bit too much for me, i always thought for music the 100-200mhz scale would be selected with screen off.
[Galaxy S I9000 Android Development] rlorange:
23% battery drain for 2hrs playback is way too steep for me too... I'm sure this is already fixed tho...

**Simply Honey3.9, Talon 0.4.2 t1 kernel1.3ghz**
[Galaxy S I9000 Android Development] boris03:
where to get newer builts?

just wondering you people talking about 0.3.2 and 4.1.2 ...

Sorry no plan to share it with others?

Where to get it?

Thanks
[Galaxy S I9000 Android Development] petsasj:
In 0.4.2 t1? Because i'm using 0.4.1 and it ain't fixed. :P
[Galaxy S I9000 Android Development] Cy4n1d3:
For me it's not using 800 mhz. What player are you using?

I'm on Ubermusic.
[Galaxy S I9000 Android Development] petsasj:
I'm using the stock one.
[Galaxy S I9000 Android Development] lohho:
The 800hz payer "issue" explanation:

http://xdaforums.com/showthread.php?p=15121501&highlight=80battery+life#post15121501
[Galaxy S I9000 Android Development] pramathesh:
Now, if you can oc the gpu. Is it not possible to uv it?
[Galaxy S I9000 Android Development] zacharias.maladroit:
over

clock

is not the same like over

volt

voltage isn't changed

and it's already downclocked from default (400 what it's capable of) to 200

there might be the possibility though

don't know where the voltage values are located for the gpu ...

afaik on eclair kernels it was quite easy to locate all sorts of voltage + other values

only the description was somewhat short/insufficient

haven't looked at the related bits in the code yet,

so perhaps besides overclocking it's also overvolted ...

so leaving it at default might gain max battery runtime with performance like before ...
[Galaxy S I9000 Android Development] flypubec:
@existz: How did you replace the default SAMSUNG boot screen with the TALON one?

I am looking at your the source and can't find the TALON image anywhere.

EDIT:nevermind did figured it out by myself (from here http://xdaforums.com/showpost.php?p=10851192&postcount=118)
[Galaxy S I9000 Android Development] faithhh:
I want to be a tester /cry gj guyz
[Galaxy S I9000 Android Development] kodos96:
It sounds like you must have messed something up while editing ram.conf. Delete ram.conf and reboot, and both it and _99ramset will get auto regenerated.
[Galaxy S I9000 Android Development] kodos96:
That won't accomplish anything, since I now have code in the bootscript that looks for these kinds of harmful scripts and disables them ;)

If you've managed to screw up your ram settings, just delete ram.conf and reboot, and everything will get set back to talon defaults.