yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] existz:
0.4.4.20 Public Test

0.4.4.20

Changelog since 0.4.4.19

- added few ZRAM upstream fixes

- possible 'charge bug' fix from AOSP upstream

NOTE

Its to early to tell if this 100% fixes the problem yet, so if you guys can test this for the 'charge bug' id really appreciate it..(where after charging to 100% it drops to 95-below when pulling off of the charger)..Again, im not sure if it fixes it, but its an attempt to..
[Galaxy S I9000 Android Development] ryuzaki_eru:
I will test the charger ;-)

Can i use noop scheduler on your kernel?
[Galaxy S I9000 Android Development] yagami:
I have almost the same setup but with OnDemand ( not X ).

Also , i have 1200 - 50 = 1250

:) seems fine , even after some benchmarking test.
[Galaxy S I9000 Android Development] existz:
Yes if you want to.., you can use Noop, Deadline, CFQ, SIO, VR and BFQ.., IMO V(R) give really great IO performance..you can change it in voltage control
[Galaxy S I9000 Android Development] HTCDevil:
0.4.4.20 working great for me with SIO ondemandX on JVR deodexed.

Thank you existz for your work...testing charge ;)

Inviato dal mio GT-I9000 usando Tapatalk
[Galaxy S I9000 Android Development] cronosmachine:
What I mean the voodoo color control. Is gone I can't adjust for my white edition. Is suffer from yellowish. I need to justify color RGB. Did you saw my foot note?
[Galaxy S I9000 Android Development] existz:
I dont understand?...voodoo color controls are still in Talon with options to adjust RGB, ..

1) make sure you are updated to latest version (latest is 0.4.4.20)

2) make sure your using latest version of voodoo control app
[Galaxy S I9000 Android Development] folkg:
Talon is starting to get stable again for me. My only complaint is that Talon, unlike Galaxian or Semaphore, will always stutter when first changing home screens after exiting an app or unlocking the screen. What might be causing this? It's like Talon takes longer to get up to 1000 hz or something.
[Galaxy S I9000 Android Development] pikachu01:
I can't reproduce that. Only one that I can reproduce is when calling, the screen takes some time to appear like <1 sec but definitely more than 0.5 sec.
[Galaxy S I9000 Android Development] existz:
Yea i cannot reproduce it either..., if your using OndemandX governor then yea technically it might take longer to scale up than the others because the up threshold is set to 95%, meaning that there must be 95% load on the cpu before it scales up...with regular ondemand its at 65% which is what i use and have no issues/lag whatsoever
[Galaxy S I9000 Android Development] The Undertakerr:
0.4.4.19 & 0.4.4.20 are as stable as a rock for me. Superfast and lagfree.

I believe Talon had a littlebit a tough time after 0.4.3, but now it's 100% back on track!

I really like the way this kernel is going, beats them all!!

I do have a small request. In my country some people have problems loosing root rights when coming from a different kernel, and then switch to Talon.

I don't know why. But I do know they regain rootrights when they flash the kernel through Odin.

Would it be possible to add a .tar of Talon so this people get root again, without the need to flash an old Odin Talon kernel?

That would be much appreciated.

Edit:

Hey, my battery is now fully charged and a do notice something different!

Before when the battery was fully charged it said 100%. After I took it off the charger, it dropped to about 98%

Now when the battery is fully charged it says 98%. After I take it off the charger, it still says 98% :cool:

Atleast the phone isn't lying to me anymore:D
[Galaxy S I9000 Android Development] rlorange:
@exitz

Does tegrak ultimate control tweak voltages independent of the voltage table others apps access?

Edit: sorry you already answered this. Ok I might just stick with tegrak ultimate then. I've ramped up to 1.34ghz now seems stable at 1330mv and 1120 internal voltage.

@Existz is it wise to bump up internal voltage on this Max freq?

**Simply Honey3.9, Talon kernel1.3ghz**
[Galaxy S I9000 Android Development] existz:
To be honest, i do not know what tegrak exactly writes to or how it applies voltages..(no sources).., but yes, it does do it differently than say Voltage Control.., personally i dont recommend using both apps, since they both do the same thing but differently (same goes for SetCPU), which can lead to problems (because you have 2 apps trying to do the same thing but in a different way)... What i recommend is, if you going to use an app like tegrak to OC, then only use it to oc/uv.., if your going to use the built in OC in the kernel (up to 1.2ghz), then only use Voltage Control, Control Freak..etc., as the oc/uv code in the kernel was actually wrote for VC, and the way it applies states, frequencies, voltages..etc.., is different than say SetCPU..
[Galaxy S I9000 Android Development] rlorange:
Ok thank you very much for clarifying this. I'm sticking with tegrak then. The finer control over voltage increments is cool and I do like going beyond 1.2ghz.

I was stable at 1.3ghz with 1275mv but only just. Currently venturing up to 1.35ghz stable so far at 1330mv woop woop!

**Simply Honey3.9, Talon kernel1.3ghz**
[Galaxy S I9000 Android Development] folkg:
I was using OndemandX, and I switched to just Ondemand, and it was better.

However, after closing twitter, cpu spy, messaging for example, it still lags in changing screens every now and then.

I am using TW 4.5, but the other two kernels don't give me this trouble. Everything else I prefer about Talon.
[Galaxy S I9000 Android Development] pikachu01:
Might be a ROM issue (transitions?). Try disabling animation and see if you're still seeing it.
[Galaxy S I9000 Android Development] existz:
So getting some great feedback so far in the Captivate thread in regards to the 'charge bug', its actually charging to 100% and staying there when pulling off the charger..which its still to early to say for 110%, we will see how things are in the morning..., but ive had it charging at 100% for the last 4hrs or so and ive pulled it off the charger about every hour and its staying at 100%, others reporting the same in captivate thread, hopefully this is the fix
[Galaxy S I9000 Android Development] rlorange:
Yep can concur 1st time since froyo I pulled off the USB and it was at 100%! Great work Existz and team.

**Simply Honey3.9, Talon kernel1.3ghz**
[Galaxy S I9000 Android Development] rlorange:
What's the deal with internal voltage on tegrak ultimate? All except 100mhz are at 1100v stock....

Wow! Stable: 1.344ghz 1325mv core 1110mv internal.

**Simply Honey3.9, Talon kernel1.3ghz**
[Galaxy S I9000 Android Development] Rootax:
What script do you have in your init.d ?
[Galaxy S I9000 Android Development] omnia-one4all:
Hi

The charge bug your are talking about is it not surposed to stop at 95 % so that it doesn't kill your battery when leaving the on the charger over night. Heard something about that lithium batteries can not be on the charger to long" when it has reached 100%" without being damaged.
[Galaxy S I9000 Android Development] existz:
The fix i used is actually from Samsung themselves, pulled it from their AOSP tree, all it does is revert a commit that sets SOC level report as 100% if batt_full flag set true.., .Also this is how it was on froyo, so its not going to hurt anything.., the commit was introduced in gingerbread kernel, then simply removed a little while later, but was not removed in our source..not sure if it was reverted after they done ours or what...but the notes on the commit is..

"We don't want to lie to userspace about the state of the battery.

When charging is complete, the battery will drain until it can

charge again. If the user disconnects after the first charge cycle

is complete, the battery level may jump from 100 to 95% or less."
[Galaxy S I9000 Android Development] rlorange:
Sorry exitz I know you are busy busy but could you briefly explain internal voltages. All except 100mhz are 1100mv stock in talon. Should I mess with these?

**Simply Honey3.9, Talon kernel1.3ghz**
[Galaxy S I9000 Android Development] aerospyke:
after the new kernel, my battery goes up to 99, never saw 100, and then started counting backwards... actually SHOWED 98, 97, 96... unplugged at 95 and plugged back in again and it was going back up. this could be the visual of what the "missing feature" from android was supposed to be doing
[Galaxy S I9000 Android Development] existz:
I wonder if a rom that has the battery full notification removed (as the rom I'm using does) has any effect on this.., say if it is removed, its keeping it from stopping once it hits 100% and just continues charging...as with a rom that does have the battery full notification, the notification kicks in as soon as it hits 100, then lets it drop, then kicks back in...this might be why some are seeing it charge to 100 and actually just staying at 100%, like mine does .. I'd assume this would be based on when the notification kicks in, where as if its removed and it never kicks in, it just continues charging ...so with this fix and a rom with battery full notification, it now actually works the way it should...Either way, its behaving alot better than it did.., plus the is how Samsung has it in newer source, all should be fine either which way
[Galaxy S I9000 Android Development] cink40:
But...if you remove battery full notification and you use .20, your battery may be in trouble (charging continuously after 100%)?
[Galaxy S I9000 Android Development] existz:
Well, if its true, then its possible, thats what im trying to come to a conclusion with, if so then roms should leave the battery full notification....BUT, and the only BUT, is im trying to figure out why on froyo, when it was fully charged it never dropped and when you unplugged it, it was always at 99-100% ..., im not going to say "its in trouble" or goto the extreme of saying anything like that just yet.

But you can see for yourself, the way it is in .20 is the way Samsung has it now, you can see the commit was added on 11/15/2010, then removed on 01/06/2011..., so it was only this way for 2months ...

Top commit is the revert I have applied, the 7th one below it is the original commit (the way it is in stock SGS gingerbread source..(pre-0.4.4.20))

http://android.git.kernel.org/?p=ke...c;hb=2ff416463040342dbd68aaa96f8a8d604792a557
[Galaxy S I9000 Android Development] rlorange:
WHAT THE??? using tegrak ultimate oc to 1.364ghz system panel and stability test show 904 bogomips.... what is going on here is my phone stuck at a slower freq or something?

EDIT: ok it's getting weirder... with stock 1200mhz talon stability test is showing 794 bogomips... which indicates the app is stuck at 800mhz... something about using tegrak boosts this to 904mips on my settings weird, weird, WEIRD!

**Simply Honey3.9, Talon kernel1.3ghz**
[Galaxy S I9000 Android Development] pikachu01:
Some findings about the battery indicator:

http://xdaforums.com/showpost.php?p=16729832&postcount=4053

Official XXJVR is out.

http://www.samfirmware.com/apps/blog/show/8111250-samsung-start-android-2-3-4-updates-for-galaxy-s
[Galaxy S I9000 Android Development] tobiasth:
same here, it shows/stays at 98% .... after unplugging it stays at 98% ...
[Galaxy S I9000 Android Development] rlorange:
Another weird anomaly:

Using tegrak ultimate to UV all frequencies only the 800 one has been changed in the voltage table. This is what it shows.

1200000 1300 1300

800000 1200 1160

400000 1050 1050

200000 950 950

100000 950 950

What is a good way to find out exactly what UV is running on the other frequencies?

**Simply Honey3.9, Talon kernel1.3ghz**
[Galaxy S I9000 Android Development] jetcz:
Same here... also I have there a 1000mhz (I'm on no oc/uv kernel version) step which in fact I don't even use.

I guess tegrak oc app works somehow differently from standard oc/uv app+kernel...
[Galaxy S I9000 Android Development] rlorange:
Yrs exits said that... but I'm wanting to know if UV is working on the other frequencies without crashing my phone to find out lol!

**Simply Honey3.9, Talon kernel1.3ghz**
[Galaxy S I9000 Android Development] ryuzaki_eru:
How do you know when CPU needs and overvolt instead of undervolt? I though that more frequency means less voltage, not more voltage.

Right now i have a seriously problema with OC: yesterday the phone was very stable @1200mhz and 1.3mv, from yesterday night it became very unstable. I don't pass any stress test, how is that possible? i didn't touch anything :confused:
[Galaxy S I9000 Android Development] Tatsuya79:
Latest versions are becoming really good, hope the memory leak is a thing from the past.

But... each time I feel my phone is getting slow and I see my free memory getting near the 290/300mb used, it's always after using the new google market.

Now I'm always killing it with a task manager after I used it and everything stays smooth.
[Galaxy S I9000 Android Development] folkg:
I turned off all animations and I still get the stutter on the first screen swype after coming out of a low clock program like messaging or cpu spy. I have had some problems with TW 4.5 with freezing on restarts and stuff, but this still isn't a problem on other kernels.
[Galaxy S I9000 Android Development] pikachu01:
Hmmm, I don't have TW4.5 to test, but TW4.5 has been known to be screwy towards frequency changes.
[Galaxy S I9000 Android Development] folkg:
Ya, I just said screw it and switched to go launcher. Thanks for the help.
[Galaxy S I9000 Android Development] Galaid:
Using 0.4.4.20, setup 1200 ondemandX, SIO. Deep sleep is working fine, quadrant 2800 after first run. Sunspider 5220.
[Galaxy S I9000 Android Development] ryuzaki_eru:
2800 after third run. What ROM did you use?
[Galaxy S I9000 Android Development] rlorange:
I'm getting 3250 after 3 run on simply honey at 1.38ghz. No stafefright either!

**Simply Honey3.9, Talon kernel1.3ghz**
[Galaxy S I9000 Android Development] simone201:
Glad to see ur using my rom with Talon...

This evening i will release my own modded latest Talon with a lot of really good mods....

I got 2800 on quadrant @1.2Ghz with InteractiveX, and the phone is smooth as butter....;)
[Galaxy S I9000 Android Development] ryuzaki_eru:
I don't understand why with Galaxian SP5 @1252mhz and 1250mv i'm solid and with TalonDev @1200mhz @1275mv i'm totally unstable. The threshold value in Galaxian is 80, noop scheduler and ondemand governor.

Right now, with Galaxian at 1252mhz i get 3553 in Antutu.

P.S. what "strafefrigh" means?

I got 2800 on Quadrant only one times, why??
[Galaxy S I9000 Android Development] omnia-one4all:
Thanks :)

10char
[Galaxy S I9000 Android Development] betoNL:
So....long time no see.. xda

I see that a BIGMEM version for the i9000 is not even in the "Upcoming features" list ?

Pitty...

Anybody know another Gingerbread kernel with a BigMem version?

«»«
[Galaxy S I9000 Android Development] simone201:
Well, u can do it by yourself, is very easy to build a Talon kernel and configure it...

If u want i can explain u how to do it! ;)
[Galaxy S I9000 Android Development] betoNL:
Oh man...I can hardly keep up with the ready-made solutions over here...

Some basic stuff...

But if you have some tips / tutorials etc....I will try to find some more time to play with....

Priorities :rolleyes:

Tks
[Galaxy S I9000 Android Development] shaarky:
Most probably we have problem with OnDemandX governor - it seems that if someone is calling you, there is like 2sec delay before screen turns on and then additional delay before it shows who is calling. When I change it to Ondemand governor, it's reacting immediately.

Anyone else could confirm this problem ?
[Galaxy S I9000 Android Development] Tatsuya79:
Yes, I heard the usual interference in my PC speakers that happen when I get a call but the phone took a bit of time to ring.

And it's sometimes slow to go out of deep sleep, missing a screen swipe I have to do twice.

Lukkiq did a fix about that in Galaxian: "removed cpu speed switching (DVFS) when sweeping home/menu screens to avoid lags"

Can't say I noticed the difference, it was still slow to react.

He's planning a "uber good new governor that is so good he couldn't believe it" now. :D
[Galaxy S I9000 Android Development] Mangus_U*RA:
I can confirm that :)
[Galaxy S I9000 Android Development] existz:
Its possible its either from the suspend_freq at 100, might have to bump it up to 200.., or could be from the threshold at 95.., might drop it down to 80 or so.., but issue acknowledged and will get fixed..thanks for the reports.

On another note, so are you guys happy with the new behaviour with the battery driver? i know its about half fixed now, more work needs to be done, but whats done so far pleases everyone?
[Galaxy S I9000 Android Development] shaarky:
Need little bit more testing...today I was charging it and when I came back it has already 95% and was not charging. Not sure whether it should really work like that ;-) It's a pity that it can't charge fully battery, then disconnect it and take power from charger, so battery would stay on 100%.
[Galaxy S I9000 Android Development] existz:
Try wiping battery stats.., it should then allow it to charge all the way, instead of stopping at 95 (atleast it fixed it for a few users with same problem)...mine has no problem charging to 99-100%
[Galaxy S I9000 Android Development] shaarky:
Well actually I don't know whether it charged to 100% and then discharged to 95% (as I noticed it later) or it stopped on 95%...
[Galaxy S I9000 Android Development] poyda69:
Had my phone on the charger all night, when i took it off it went to 89%.
[Galaxy S I9000 Android Development] The Undertakerr:
Yesterday I wiped battery stats. Today, it charges up to 98%, stops charging then and then I get the message it's full. After I take it off the charger, it still says 98%.

It is ok for me like this. Not really an advantage or disavantage as far as I'm concerned...
[Galaxy S I9000 Android Development] iamprayl:
Hi, talon kernel is the best. I've been a follower of this kernel ever since I got my cappy. Your works were fantastic. I've been flashing almost every two days coz everytime I checked on xda you got new updates. Lol. So far i got no issues e.g. soft reboots except when i UV but now it's running fine and stable along with a new Sensation ROM.

Phone: Samsung Captivate

Kernel: TalonDev Kernel 0.4.4.19

ROM: Sensation ROM 2 with

i9000 Bootloader
[Galaxy S I9000 Android Development] The Undertakerr:
Existz,

You know I like your kernel very much.

I do have a request. I like to overclock once and a while, but not all the time.

Before I could take the 1.2Ghz version and most of the time use it on 1Ghz and some times on 1.2Ghz.

I know you removed a step for stability reasons, but I am not so happy with this solution. Always on 1Ghz or always on 1.2Ghz.

I like to decide myselve and do it via voltage control.

I do not really like to use the tegrak overclock app allthough I have the paid version. It feels like using a different kernel when I use that app.

Can you find a way like in the past? Stock CPU on 1Ghz and adjustable via voltage control?

Before we had many steps, even up to 1.6Ghz and that one was stable for me also(ofcourse not on 1.6Ghz:o)

1.6Ghz is not necessary, but up to 1.44Ghz or so.

Lukiqq also reintroduced the 1.2Ghz kernel with the 1Ghz step...

I am very sure more people would like it this way.

Hope you can find a way...
[Galaxy S I9000 Android Development] djdeeles:
Yes i want stepping and 1440 mhz :) without tegrak
[Galaxy S I9000 Android Development] k!pps:
Feel the same :D

Hope You consider this.
[Galaxy S I9000 Android Development] existz:
As of right now I wont, there's still the issue where it scales to Max frequency no matter what Max clock is set ...ie., it will jump to 1.6ghz even if 1ghz is set..which is triggered by certain launchers, apps, games..etc., However, this issue does not come into play until freqs of 1.3ghz and higher are set. It does not happen with 1.2ghz and below versions..,. I'm not sure what's causing it, I don't think its a DVFS issue since it does not happen with 1.2ghz added as an extra step..If it was a DVFS issue then it would have scaled to 1.2ghz when 1ghz was set Max clock (in earlier versions of talon with 1ghz and 1.2ghz in same kernel).. This is a huge stability issue for those that cannot handle the higher clocks.., so until that can be fixed, I wont add multiple oc ..stability is #1 on my list right now
[Galaxy S I9000 Android Development] shaarky:
Only FYI - there is one point to be mentioned with the 1000MHz step - actually it was presented by Lukiqq, but then he back introduced it to his Kernel (which I really don't understand, his explanation sound logical ;-) ). True it's not giving the possibility to configure it ourselves, but if it's because of stability, it's worth doing it.
[Galaxy S I9000 Android Development] iamprayl:
Thanks for the great kernel. Will try .20 update.
[Galaxy S I9000 Android Development] existz:
Which what he mentioned IS correct, it is setup that way with DVFS settings, and it is spread through out different drivers. Which this can be fixed if you go through and correct each setting, upping the Lx value to what the new setting should be (for example if its set to L2, which is 400mhz on stock amount of frequencies, 5...so if you add 1.2ghz along with 1ghz (now 6 frequencies), then L2 becomes 800mhz, so you would have to change it to L3)..there's quite a few of these in the source, and it would be a pain to go through and locate each one .., I'm not saying it can't be done, it's just a ***** to do.. Also, with having 1ghz removed in the 1ghz version, that's one less step it has to scale through, and should make it a smoother experience..as it does "bypass" through 1ghz from time to time.. And honestly IMO, if your using 1.2ghz, then there's no need for 1ghz step.., less steps it has to jump through = smoother results..
[Galaxy S I9000 Android Development] Rootax:
Existz, do you see a point implanting the smartass governor ? I used it with the Snail kernel, and the results were pretty good.
[Galaxy S I9000 Android Development] existz:
Nah not really.., we have tested and tested and tested every governor.., (interactive and interactiveX are still in Talon source).., ever since Talon was born we tried different governors, only to come back to Ondemand each time.. Theres less problems with Ondemand, its smooth and good on battery.., and the most important, its reliable.., So to keep the number of issues down, ill probably only include Ondemand/OndemandX .. But who knows, some updates to smartass or interactive might come along and change things, Im always trying different things that do not make it to test/public builds., so maybe one of these days
[Galaxy S I9000 Android Development] zacharias.maladroit:
++

on the reliability

smartass might be more consistent in the experience but it tends to lock the cpu on high frequencies

might be a bug or a algorithm thingy

interactive - it tends to hickup from time to time and besides that the phone gets really warm

maybe in the near future the "perfect" governor is born and incorporated into talon - who knows :)
[Galaxy S I9000 Android Development] The Undertakerr:
Ok so you could make a save 1.2Ghz version with the 1Ghz step in it?

I understand that stability is nr 1 on your list, but mine and many other phones were stable with both steps included.

Many people like me just want an option to overclock, but not overclock all the time...
[Galaxy S I9000 Android Development] stratosk:
Nice team! Real developers! Perfect work!
[Galaxy S I9000 Android Development] ascariz:
Some want battery saving, some want OC. Super sapiens.. My suggestion, create different kernel for both condition. I cum in peace.. o_Ov
[Galaxy S I9000 Android Development] jovi232437:
http://www.addictivetips.com/mobile...pt-on-galaxy-s-ii-to-record-calls-dialer-mod/

possible to add this script to our gingearbread?
[Galaxy S I9000 Android Development] zenosteam:
This is the only thing that i missed on my rom .it will be fantastic if that possible to make it