yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Mickyman:
Sorry for the noobish question but, the download is a zip file. Do I need to change that to .tar or something?
[Galaxy S I9000 Android Development] jeebspawnshop:
See how it says "CWM" in the name of the file? It means it must be applied through CWM.
[Galaxy S I9000 Android Development] Flynny75:
No, no need to change. Just flash with CWM
[Galaxy S I9000 Android Development] Mickyman:
Ah ofcourse, thank you.

I have problems flashing it trough CWM.

This is what I get:

Kernel flash failed!

No zImage was found.
[Galaxy S I9000 Android Development] jeebspawnshop:
Then you're downloading the wrong thing... or the download isn't completing and is therefor corrupt.

What are you downloading, precisely? And are you using silly things like a download accelerator?
[Galaxy S I9000 Android Development] Mickyman:
I downloaded the TalonDEV 0.4.3 340MB 1200MHZ zip file. And no, this is a fresh 2.3.4 JVR upgrade so no download accelerators.

I currenty have CF-Root installed. I want to use TalonDEV with SURFACE rom.
[Galaxy S I9000 Android Development] jeebspawnshop:
Don't know what to tell you, bud. I have no idea what's up.

Maybe other readers might know something...
[Galaxy S I9000 Android Development] Mickyman:
Is it maybe because I have to install the SURFACE rom first?
[Galaxy S I9000 Android Development] HTCDevil:
OndemandX works for me only with 0.4.4.17 (that misses 1000Mhz), doesn't work with 0.4.3.
[Galaxy S I9000 Android Development] Flynny75:
It shouldnt be, you should be able to flash a kernel whenever. Download a fresh copy, maybe that one was corrupt.
[Galaxy S I9000 Android Development] Mickyman:
Tried it 2 more times. Same result :(
[Galaxy S I9000 Android Development] existz:
Just downloaded both versions, both are fine..., i would try downloading from a PC then copy it over
[Galaxy S I9000 Android Development] shaarky:
So I confirm - so far no issues with OndemanX, very well done. Just wish you can again release version with RAM/LCD UV... battery was discharging 2-3% instead of current 4-5% during night. How much should I donate to get it ? ;)
[Galaxy S I9000 Android Development] cink40:
:rolleyes::rolleyes:and what 1-2% over night means to you? Shut down the phone, you will get 0%...
[Galaxy S I9000 Android Development] shaarky:
:) Well, good idea....however as it's business phone (my phone, business sim) , I need to be online even during night.
[Galaxy S I9000 Android Development] Rootax:
But where is the fun :p
[Galaxy S I9000 Android Development] ryuzaki_eru:
I tried all mv @1200mhz: -25, -50 and -75. The phone reboot all time. What can i do?
[Galaxy S I9000 Android Development] jeebspawnshop:
Easy... don't UV and it'll work just fine.
[Galaxy S I9000 Android Development] HTCDevil:
Confirmed using Viber :D

Inviato dal mio GT-I9000 usando Tapatalk
[Galaxy S I9000 Android Development] existz:
0.4.4.18 Public Test

0.4.4.18

Changelog since 0.4.4.17

- added hardfloat optimization flags

- a few ARM/S5P/SAMSUNG upstream fixes

- introduce OndemandX CPU governor (use for best battery life)

- updated to Linaro 4.5 (GCC 4.5.4) 2011.07 toolchains (from 2011.06)
[Galaxy S I9000 Android Development] jeebspawnshop:
Cool beans. Gonna test it now.

THANKS!
[Galaxy S I9000 Android Development] aerospyke:
Downloading!
[Galaxy S I9000 Android Development] ryuzaki_eru:
I tried, but the phone is instable. I don't understand the problem.
[Galaxy S I9000 Android Development] Flynny75:
The phone is unstable even if you dont undervolt?
[Galaxy S I9000 Android Development] ryuzaki_eru:
Yes. The weird thing is that with Galaxian @1200 and 1300mv the phone is stable. I don't understand why.
[Galaxy S I9000 Android Development] existz:
One thing i noticed, with Galaxian he uses up threshold=90 for ondemand, I use 65..., which can change how much the cpu spends at max clock (talon spending more time at 1.2ghz), try using the OndemandX governor, its set to 95..it will not scale to 1200 as easily, putting less load on max clock and could make things more stable for you
[Galaxy S I9000 Android Development] Flynny75:
Or, just use the nonOC version...

And an initial report of .18: 'Damn, this is smooth'
[Galaxy S I9000 Android Development] ryuzaki_eru:
How can i change governo? However why my cpu don't work at 65? It sucks?
[Galaxy S I9000 Android Development] aerospyke:
Sorry for the newbie question, is the above the same OnDemandX CPU Governor you posted for trial a few pages ago?
[Galaxy S I9000 Android Development] existz:
yes

10char
[Galaxy S I9000 Android Development] existz:
Its just a guess, not sure if its the problem.., but say if it is, at 65%, it scales to Max clock quicker and will spend more time there, since it takes less % of load to scale up, so if its at 90-95%, then it does not have to be truly as stable as what it would have to be at 65.., since it will spend less time at 1.2ghz... but again, its only a guess, and something I noticed that was different between the 2
[Galaxy S I9000 Android Development] :
@existz... Can you make a version without voodoo color (0.4.4.18)??? maybe with the settings from lukiqq???
[Galaxy S I9000 Android Development] Bavaria85:
Are the ram issues fixed with these latest releases?
[Galaxy S I9000 Android Development] jeebspawnshop:
Not sure yet...

But if the RAM issues are still present, just download the free app named "Autokiller Memory Optimizer" from the market, open it, select "Strict" preset, and hit Apply.

Poof! RAM issues are automagically resolved.
[Galaxy S I9000 Android Development] brfsa:
this kernel is pretty damn good.

you did an excellent job!

0.4.4.18 works perfect with surface 3.0.2

actually all versions since 0.4.4.9 have been working great.

Cheers.
[Galaxy S I9000 Android Development] existz:
:) glad its working good..., im hoping next test or so ill be able to include a little something special for you guys, shane87 is making great progess on MemoryFreak..., currently running a beta version which hopefully will be included in Talon shortly.., So far it includes Stock, Nexus S and Talon default settings.., with Talon settings you will have an option to manually adjust HIDDEN APP MEM SIZE, from 28MB to 52MB (lower = more agressive settings, higher = more multitasking, apps stored in memory).., then with all presets you will be able to adjust ZRAM_SIZE (from 0-256 , 0=disabled), and swappiness size.. It should allow you guys to tweak the LMK settings to your liking, while keeping good settings based on Talon...
[Galaxy S I9000 Android Development] Cy4n1d3:
Latest versions make a very good haptic impression to me :)

OndemandX however won't work for me, I get random reboots.
[Galaxy S I9000 Android Development] pikachu01:
It's better to edit the minfree settings using ram.conf (or Memory Freak when it's released). AMO doesn't apply the values where Talon needs them to be and might lead to some mismatches that can affect zram/swapping.

Change your governor using Voltage control/Pimp My CPU, SetCPU. Galaxian rarely scales up to 1.2GHz (doesn't spend much time in 1.2GHz) Hence why it's stable for you. If you ran a stress test that stresses your CPU to 1.2GHz all the time, you will eventually get the same reboots too. Conclusion: Your CPU is not stable at 1.2GHz. Try not to OC k?

What error are you getting? Insmod should work from early versions of Talon.

Umm, this is an error when flashing through SGS kernel flasher right? You should flash through CWM which is using the recovery mode. (Up + Home + Power button)

Your ROM might have modded some strings (build.prop or your ROM as a different pit than 512). Flash stock JVR and then dark core (Or Talon using Odin by extracting the zimage and tarring it). It will convert your partition to ext4.

Dark core is easier if it has Odin. Alternatively, you can convert to Ext4 using Semamphore (using CF ext4) or Speedmod ext4. Your choie.

Then flash your ROM with Talon.
[Galaxy S I9000 Android Development] existz:
Ok, i found a bug thats actually preventing UV from actually being applied, it still shows in VC..etc.., that its set.., but actually its not.. This could be the reason for reboots/instability for some of you.. you can check /sys/devices/system/cpu/cpu0/cpufreq/frequency_voltage_table ..., middle numbers are stock voltage and the numbers on the right are current voltages.., as you can see they are the same no matter what UV settings are... I will put a build up with this fixed in the morning. Sorry for this one guys, took me awhile to figure out that its not actually setting...update in the morning
[Galaxy S I9000 Android Development] Galaid:
no, but i will the next version with UV fixed..
[Galaxy S I9000 Android Development] pikachu01:
That would mean that even without UV, my phone lasts more than 1.5 days. This is really good :)

Do you know when this bug was committed?
[Galaxy S I9000 Android Development] existz:
I have no clue when it was actually removed, for some strange reason i was just going through and happened to check the file and noticed it.., so its hard saying how long its been like this
[Galaxy S I9000 Android Development] Galaid:
eXistZ,

could you please attach MemoryFreak apk? Looks nice :)
[Galaxy S I9000 Android Development] existz:
Not yet, still doing some testing with it...when its ready it will be included in talon by default .., most likely it wont be in the update tomorrow, but hopefully the next one
[Galaxy S I9000 Android Development] Cy4n1d3:
The freq_uv_table stuff was already commented out in late May :)

Don't think it was added back in later.

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

Cleaned up in

https://github.com/existz/linux_gt-i9000-gb/commit/ee0c09a51fa5d8e022c3c51de46c2a9b56637d23
[Galaxy S I9000 Android Development] Rootax:
Just because I'm a pain in the *ss , with 0.4.4.18, the kernel version shows a Linux version string, not "Talon vXXX" :o
[Galaxy S I9000 Android Development] SamHaLeKe:
Oh man, what a bummer :(

I was thinking all the time I was doing UV on my phone :rolleyes:

I'm sure it will fixed very soon as this is a high priority problem with an OC kernel ;)
[Galaxy S I9000 Android Development] Cy4n1d3:
On git this is already fixed, update will be tomorrow like existz said.
[Galaxy S I9000 Android Development] ryuzaki_eru:
So, what can i do for make the phone stable with your kernel?

Conclusion: my CPU really sucks and OC is a dream for me.

Maybe is this the problem for me?

Same here!!! One question: because some people have a 1300mv on default and the phone work fine and other some people needs to UV the CPU?
[Galaxy S I9000 Android Development] pele78:
To the TalonDev's

Gotta hand it to ya, cant find any faults with this kernel, been running it for some time now, flawless.. its like a flash and forget kernel (how most things should be) and nothing to worry about.

Looking forward to pushing this into the RomKitchen at some point too.

Regards

Keep up the good work!
[Galaxy S I9000 Android Development] badworker:
What about the RAM/ADC voltage in the last .18 release?
[Galaxy S I9000 Android Development] HTCDevil:
existz why have you omitted 1000Mhz step in 0.4.4.18 and other test versions?

Thank you for your work, 0.4.4.18 on JVR with ext4 works great ;)
[Galaxy S I9000 Android Development] ryuzaki_eru:
I have found another strange thing. Withi this kernel, when i run Quadrant, the I/O test requires too much time, with other kernel it pass very fast. All the partitions are formatted in EXT4. Anybody have seen that strange thing?
[Galaxy S I9000 Android Development] Rootax:
In the 1.2ghz version ?

I'm not a dev but I believe having more cpu states than the default number is complicated, because it has consequence on the dynamic voltage, and a lot of other technical stuff.

But maybe I'm wrong, wait for Existz for a good answer :D
[Galaxy S I9000 Android Development] rlorange:
Simply mount data and system in talon recovery before sh add on flash. This fixes it.

**Simply Honey3.9, Talon kernel1.3ghz**
[Galaxy S I9000 Android Development] pikachu01:
That is correct. Having more than the number of default CPU states slows the CPU scaling considerably and leads to instability.
[Galaxy S I9000 Android Development] rlorange:
Wow stuck UV settings... that explains why people have Been reporting impossible UV levels. I'm lucky my phone is stable at 1.3ghz using tegrak with 1.2 voltages.

**Simply Honey3.9, Talon kernel1.3ghz**
[Galaxy S I9000 Android Development] ryuzaki_eru:
Why some people have a 1300mv on default and the phone work fine and other some people needs to UV the CPU? It depend on every CPU?
[Galaxy S I9000 Android Development] SamHaLeKe:
you will be the first to run SGS @ 1300MHz with 1200mv (that's + 300MHz over stock and -75mv!!!)

post a video that proves stability with the above settings while running Asphalt 6,

I highly doubt it

! ;)

no video and no answer means you are bullshitting :D
[Galaxy S I9000 Android Development] ryuzaki_eru:
if that's true, he is a very lucky guy :D
[Galaxy S I9000 Android Development] h4m74ro:
My phone hangs and then reboots instantly when I UV too much.

So UV must have been somehow applied.:confused:
[Galaxy S I9000 Android Development] rlorange:
Misunderstood. I meant voltage settings on 1.2ghz stock which is 1300mv. As this value is frozen for the moment as Existz mentioned. Whatever voltage control it tegrak show stock voltages are stuck.

**Simply Honey3.9, Talon kernel1.3ghz**
[Galaxy S I9000 Android Development] rlorange:
Weird. Mine are stuck

**Simply Honey3.9, Talon kernel1.3ghz**
[Galaxy S I9000 Android Development] rom08:
I was using tegrk app to oc. As this app load a module did the uv settings applied on talon or it wasn't like with setcpu?
[Galaxy S I9000 Android Development] cink40:
yep, mine to (0.4.4.18), uv definitelly working...
[Galaxy S I9000 Android Development] rlorange:
Check the undervolting settings table file in sys folder. Mine stays stock no matter what UV I set in tegrak. Maybe other apps do work ill try now.

**Simply Honey3.9, Talon kernel1.3ghz**
[Galaxy S I9000 Android Development] rom08:
Thanks i check the file and I'm not even on talon and the voltages are stock.
[Galaxy S I9000 Android Development] SamHaLeKe:
tested that and same for me, when going to low on UV my phone hangs, so UV is applied somehow :confused:
[Galaxy S I9000 Android Development] SamHaLeKe:
maybe it's not adjusted in that file but IS truly applied?
[Galaxy S I9000 Android Development] rlorange:
Tegrak doesn't use an init.d script yo set voltages like other apps so maybe this is the difference. Does init.d script file override the one in sys folder?

**Simply Honey3.9, Talon kernel1.3ghz**
[Galaxy S I9000 Android Development] ryuzaki_eru:
With Tegrak UV @1300 works?

Same for me i think, but the problem is that @1300mv - 25 my phone reboot too. So IMHO the values are not saved in the file. We have to wait tomorrow for new version and hope that this time works.
[Galaxy S I9000 Android Development] ryuzaki_eru:
But with Tegrak it is possible to make UV permanent? Need i the non-free version?
[Galaxy S I9000 Android Development] _PrEzi_:
So far running on .17 with OndemandX v1.3, my two cents that have been noticed :

- Havent had a reboot, either with BT or WiFi (or both combinations) on.

- UV is as stable as it was, my settings (might look less agressive, but I cherish the stability a lot ;) :

Rate UV Voltage

1200 - 0 - 1300

800 - -75 - 1125

400 - -100 - 950

200 - -125 - 825

100 - -150 - 800

- Phone seems to consume less battery (on idle during night - it is 1-3% less compared to earlier build without OndemandX) resulting in overnight consumption of around 2-3% (!! great - at last we have a good battery usage - similar to what I've seen in Laststufo's Froyo superoptimized kernels !! )

- Phone battery drain when plugged in seems to be fixed (during charging I believe it now is hardfixed to 100 MHz when screen off which is a + for me) - earlier when you plugged off your charger even when it seemed that the batt = full it dropped to 97/98/99% just after a few seconds (not a battery calibration issue, since I wiped and recalibrated the battery ? Seemed more like - the phone charged till full, then it signaled 'full' and slowly discharged during night without recharging back),

- Phone seems to be a little 'sluggish' when waking up (power button or receiving a call) - it sometimes needs 1 or 2 seconds for the display to show, but I assume it is related to the OndemandX governor and the 95 step - is ok for me, but as an idea - would it be possible to 'hardcode' an immediate step to say- 200MHz in case an event occured (SMS/CALL/Power button pushed ?? ) Just a thought - I would rather sacrifice this slugishness on the beginning rather go back to the earlier bat. consumption.

- Havent noticed 'hard' memleaks... But it might also be because I have AMM with my settings. Once only it was weird as my phone was slow and below 60MB of Ram without any noticable services running in for/backgrnd/buffered

To sum it up - SO FAR SO GOOD, seems to be a keeper for me until the uV won't be fixed in the next (19 ?) build :)

BEST kernel overall - wonder why it is not integrated in all custom roms ;)

THX Existz & the Talon Dev team.

I promise you a drink on me (or two) after the first of the month :)
[Galaxy S I9000 Android Development] Rootax:
I don't know if it is link with the small lags when something is trigered, but the galaxian creator implemented this : removed cpu speed switching (DVFS) when sweeping home/menu screens to avoid lags.
[Galaxy S I9000 Android Development] _PrEzi_:
Hmm... rather - it seems to me that the phone is on the 100MHz rate, and needs on or two seconds to raise the rate higher and in between the screen goes on ;)

But again - not a serious issue - rather keep it that way and don't sacrifice it for worse battery life.

But in case it can be tweaked... ;):D
[Galaxy S I9000 Android Development] ryuzaki_eru:
While i waiting for new version that solve Uv bug, i want to know if i change voltage values manually with file modifications. Thanks.
[Galaxy S I9000 Android Development] Gvdn:
Alsof using tegrak ultimate and i can make phone reboot just by changing uv. Just wanted to share.
[Galaxy S I9000 Android Development] rlorange:
Ok thanks for sharing... I too use this app. And it may control UV independently via its kernel module.

Did you achieve this only for the top freq it sets or all of them?

**Simply Honey3.9, Talon kernel1.3ghz**
[Galaxy S I9000 Android Development] Gvdn:
Was only for testing purpose that i used uv settings of which i was sure they wouldn't work. But i uv all frequencies. Can use default and only do top if u like. Just tell me what you want me to test. This is on v.18 btw with ondemandx.

Edit: rlorange u mind sharing your oc and uv settings? Or send em in a pm. Ty
[Galaxy S I9000 Android Development] ryuzaki_eru:
I tried to change manually the file, but the modification are not applied. I waiting for Uv fix. Meanwhile i tell you that @1200 and 1300mv the phone is half-stable. With Antutu it rebooted one time.
[Galaxy S I9000 Android Development] rlorange:
I'm a bit wary of data corruption so I'm inclined to wait for Existz to fix this bug before testing. All I know is people have been reporting crazy UV success for a while now. Maybe the bug is affecting only some. I can't oc beyond 1.3 now and used to be able to go to 1.5. Using tegrak ultimate, I'm guessing the voltage I'm setting to achieve this based on past experience (1.4-1.5v) is not sticking because of the bug. 1.3ghz does work on my phone at talon stock voltage settings for 1.2ghz (1.3v) so I'm lucky cos my preference if 1.3ghz works with the current frozen stock settings. A lot if stability confusion has just resolved with this new bug IMO.

**Simply Honey3.9, Talon kernel1.3ghz**
[Galaxy S I9000 Android Development] existz:
Yes, tegrak controls it differently and should not effected by this., nor is SetCPU, or any app that works on a stock kernel (I would think anyways)... sorry I didn't make this clear ...only if using Voltage Control, Control Freak..etc will it not write to frequency_voltage_table ..it was 5am when I noticed this, I was tired lol...but I'm working on uploading .19 with this fixed

The frequency_voltage_table is a sysfs that is apart of the OC/UV code which was originally wrote for Voltage Control, so this is any effected by such apps that use this..(ControlFreak, Pimp My CPU (i think),)...

@rlorange

One reason you might not be able to OC as much now is because, since the 1ghz step was removed, its putting more stress on the max frequency..which could very well effect stability ..so using higher clocks like 1.3/1.4..etc, have to be alot more stable than they were before, since they are spending more time there... Other small things like the ondemand up threshold can effect stability for some also. Lowering the threshold will make it scale to max clock quicker, spending more time there, needing more stability than before (if you dont believe me, try setting threshold to 95 and watch how much less time it spends)
[Galaxy S I9000 Android Development] folkg:
I second this. The only noticeable lags on the phone are when scrolling. Although memory does get high, too.
[Galaxy S I9000 Android Development] Tatsuya79:
Have you decided to keep a particular cross compiler or still comparing which could be the best?
[Galaxy S I9000 Android Development] ryuzaki_eru:
But Tegrak can change Uv succesfully? If ut can i buy ultimate version. Hiw do you check the stability of your CPU? My phone @1200 and 1.3mv works fine, but in Antutu it rebooted. Another strange thing happend in Quadrant: I/O test require much time, but before with other kernel and rom it was so fast. How is that possible? Lagfix is on.
[Galaxy S I9000 Android Development] existz:
0.4.4.19 Public Test

0.4.4.19

Changelog since 0.4.4.18

- fixed issue with UV not writing to frequency_voltage_table
[Galaxy S I9000 Android Development] ale0crysis:
Awesome :D
[Galaxy S I9000 Android Development] existz:
So far linaro 4.5 (GCC 4.5.4) 2011-07 or 2011-06 is working really well with O3 + Graphite + hard float optimizations. I will probably stick with these for awhile "officially" but ill always continue to try newer ones .
[Galaxy S I9000 Android Development] ryuzaki_eru:
Thanks! Now the phone seems stable @1200 and 1.3mv. I will buy Tegrak Ultimate and i will try 1300mhz frequency. I tried it with 1.3mv, but the cpu is unstable and i have not the time for changing mv because the phone is rebooting.
[Galaxy S I9000 Android Development] jeebspawnshop:
Looking good so far... admittedly it's only been running for 15 minutes, hehe.

But the new direction of the kernel and the stuff you're beginning to include is really great. Keep it up.

And oh! Never mentioned it before, but the kernel boot screen is great. Simple, clean, attractive ;)
[Galaxy S I9000 Android Development] Rootax:
About boot animation, is there a way to only have the Talon one, and remove the default samsung one ?
[Galaxy S I9000 Android Development] Rootax:
For the record, if you use Galaxian too, remove the S80 script from init.d. Talon was not as smooth as usual until I, delete it and reboot.
[Galaxy S I9000 Android Development] existz:
Whats the filename on Galaxian script? ill add it to the CWM script to remove it when flashing
[Galaxy S I9000 Android Development] Rootax:
S80galaxian

Thx!
[Galaxy S I9000 Android Development] Tatsuya79:
I skipped some versions sorry.

Speedmod Neutral Colours version (Voodoo Gamma Hack reverted).

I would have liked to change it to latest Galaxian settings though, they are quite nice. But no sources yet and I don't know if that's easy to do or linked to a different OLED driver Lukkiq refered to in his release notes...

Well, anyway that's it for now. :p
[Galaxy S I9000 Android Development] ryuzaki_eru:
How can i change scheduler? I want to use noop.

BTW today the phone was completely stable, tonight it is very unstable. I did not touch anything...how that is possible?

Curiosity: With Antutu i get 3330. There is a guy with 1.7ghz phone...how he did it?!?!?!?!