yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] Metalzoa:
Just tested this out. Had weird vibrations after pretty much every action.

Realized I was in the JFS setup and switched to advanced EXT4 ... 177x or so quadrant score. Impressively smooth .. probably even better than the JFS overkill I was running previously. Then again, EXT4 always ran smoother, I just went down to JFS for battery consumption reasons. Mind you, I also had the 337 ram mod going with the JFS, which made it noticably quicker.

I'm not sure if its compatible with what you've done here, but the results could be very outstanding if the improvement is as significant as it was for the JFS setup.

edit: 2220 quadrant, overkill ext setup.

303 ram.

everything running smoothly ... will be closely monitoring the battery life too.

Good work sir ... hats off :D
[Galaxy S I9000 Android Development] dwillMUFC:
Great work :)

EDIT: Just flashed over my JP9 - Amazing speed well done again.

Thanks

Dan
[Galaxy S I9000 Android Development] bodivas:
darky 3.0 over (Universal lagfix 440 mb

-No-RFS Advanced)

set cpu:1200

quadrant:

cpu-1630

memory-1817

i/o-4203

2d-367

3d-1040
[Galaxy S I9000 Android Development] glitterballs:
They have a 1.6GHz kernel, but their Linpack is only about 12. Significantly higher scores with this kernel at a lower clock speed.
[Galaxy S I9000 Android Development] dwillMUFC:
Just a thought although this is in very early stages "Extreme" Alpha.

Would it be possible to also overclock the GPU - The "Manhattan" kernel in the Vibrant section, has managed to get it all the way upto 80fps!!

Amaizing:eek:

Just a thought to wet your appetite :)

Dan
[Galaxy S I9000 Android Development] reidefors82:
And what if i aint satisfied after flash ?

Can I take the *.tar from my Doc-rom and flash it back?
[Galaxy S I9000 Android Development] raspdeep:
ya, its steeper than what i would like, i will see if i can tweak it to be more conservative
[Galaxy S I9000 Android Development] ajay003:
Hey Raspdeep, is it possible still to overclock more than 1.2Ghz? maye 1.3 or 1.4?
[Galaxy S I9000 Android Development] xan:
raspdeep, what about this lil vid (not big booty *****es one :p) I've recorded?
[Galaxy S I9000 Android Development] raspdeep:
this is cpu related tweaks and if it is feasible to implement without taking too much hit on the battery, i will release more info.

possible, highest i got on my phone was 1.4ghz but some things doesnt run properly and i know not too many will be able to run so i wont attempt to release anything :). you are free to use my source code to implement higher frequency if you like but you'll need to study the datasheet to get that far

the big booty *****es are awesome!! hahaha.. j/k

ya, i got that and i think is a source bug (need more comfirmation to check my n1 if its doing the same thing). i've updated my first post
[Galaxy S I9000 Android Development] EarlZ:
Rasp, would it be possible for you to add on the future change logs on w/c specific 341MB kernel its updated to, something like this current version is based on the K1r2-300Hz.
[Galaxy S I9000 Android Development] raspdeep:
this is not based on K1r2.. he did not release source so it is not possible to be base off his work. what he released was bits and pieces of information that i can only 2nd guess

mem tweaks are there since version 1 so it is in general info.

im going to try some cpu tweaks by trial and error but it is not the same as what hardcore has done
[Galaxy S I9000 Android Development] dupel:
Didn't he add file with changes to attachments in his thread?
[Galaxy S I9000 Android Development] EarlZ:
oic, i always thought its purely based on his kernel.
[Galaxy S I9000 Android Development] rui.mamede:
For the ppl trying different uv settings and testing stability I recommend that you try to play around with Google Earth for a minute or two, you might be surprised...
[Galaxy S I9000 Android Development] raspdeep:
ahh ok, just saw he uploaded the source.
[Galaxy S I9000 Android Development] raspdeep:
now you made me curious what the surprise might me:p
[Galaxy S I9000 Android Development] ashwinds:
On an extended run (mostly idle overnight with wifi on, sync for 2 mail accounts on) - it runs about 14% over 11.5 hrs. Which is not too far from the average 1% per hour drain I normally see. Maybe it drains more in use.
[Galaxy S I9000 Android Development] raspdeep:
it is not easy to tweak the speed significant enough to be noticed and still maintain low battery usage.

what my tweak does is to speed jump from 100 -> 400 -> 1ghz -> 1.2ghz, 200 -> 800 - 1.2ghz vs the conventional 100->200->400->800->1ghz->1.2ghz. also some minor tweak adjust the thresholds.

what im trying to tweak is so it can stay within 100 to 400mhz range during idle (to conserve power) so it doesnt hit 1ghz easily. but still responsive enough to hitting high frequency when needed, there are tradeoffs. more trial and error needed tho
[Galaxy S I9000 Android Development] rui.mamede:
I just found Earth to be a really nice stressing test. I have used my phone OC'ed for weeks and then found out that Earth still crashes my phone (it doesn't at 1Ghz tho).

Like you said, every cpu is different, i must have got a crappy one. Nonetheless, i think anyone that wants to know if they have a rock stable device should give Earth a shot.
[Galaxy S I9000 Android Development] raspdeep:
i managed to find get v1.1 earth and it runs fine on my phone at 1.2ghz, after about 30mins of playing, the temp went up to 60C. yup it stress the phone so its a pretty good test.
[Galaxy S I9000 Android Development] xan:
rockplayer >> all.

If you gonna have freezes [anywhere], you gonna get them under 30 secs in rockplayer.
[Galaxy S I9000 Android Development] android53:
Actually you could do better than rockplayer testing. If the gpu gets overclocked as a byproduct, rockplayer would not detect that instability

Raspdeep, is the gpu at stock speeds?
[Galaxy S I9000 Android Development] xan:
This is true, good point. :)
[Galaxy S I9000 Android Development] EarlZ:
Whats so special about rock player? It cant even display subs on my anime xD
[Galaxy S I9000 Android Development] raspdeep:
nope not yet. if gpu is overclocked and unstable, you can still test it using hardware mode, no?
[Galaxy S I9000 Android Development] raspdeep:
its good for stressing the cpu because it has software mode. for whatever reasons, other apps that ran fine during OC/UV seems to show up instability using rockplayer so it sets the standard higher for stability test while OC/UV'ing your phone
[Galaxy S I9000 Android Development] android53:
Yeah, but most hardware video playback barely stesses the gpu.

800x480 h264 mkv avc level high 4.0, Q16

No frame drop no stutter or lag, amazing for a phone.

Ofc lags on software mode though lol
[Galaxy S I9000 Android Development] jeebspawnshop:
Hey guys. Been following this thread for a while, and finally feel like having a taste of this kernel ;)

Just one question; I'm running sztupy's kernel with all JFS turned on, but no binds. Can I just drop his kernel in as a replacement? Or should I disable the lagfix and tweaks, etc, then drop in the kernel?

Thanks in advance for the help.

EDIT: spelling mistakes :(
[Galaxy S I9000 Android Development] dupel:
should work. If it doesnt just flash your last kernel.
[Galaxy S I9000 Android Development] xan:
just flash and its rolling.
[Galaxy S I9000 Android Development] jeebspawnshop:
Thanks for the quick response, boys.
[Galaxy S I9000 Android Development] fane1:
I tried this kernel today and was so happy because the phone is so fast and responsive.But i have one aplication that makes the phone crash and its one of my favourites: Power Amp.I know that its kinda gpu hungry im not using any lagfix just the kernel.Its a shame really what can i do to avoid it? thank you and great job
[Galaxy S I9000 Android Development] tristecire:
GPU hungry, or maybe, better CPU hungry !

graphic processing unit or central processing unit.

It seems Rasdeep's hacks are only about the second one.

It seems too there are lucky one's, stable at 1.2GHZ with pretty large UV ( here 0,50,100,100,150,150) and not so lucky ones , maybe Samung sells CPU's that failed to support OC, and then UV.

Here everything is allright, old SGS i9000, june 2010 production, i play with everyting over XDA i9000n, never failed.

Poweramp OK, switching tunes as i like, same with videos.

Eh, never tried Rockplayer nor Google Earth, the main culprits if i'm a reasonable reader.

So. Cpu series are not equal. some do, some don't.

Just my feeling.
[Galaxy S I9000 Android Development] xan:
Its the whole truth.

Fortunately for you, unfortunately for me =]
[Galaxy S I9000 Android Development] raspdeep:
did you do UV? post your UV setting or try to reduce or zeroing UV at 1.2ghz.. If it still crash, check "do not overclock" option in xan's app
[Galaxy S I9000 Android Development] raspdeep:
v215 UV alpha (1.2ghz and 1.12ghz OC support)

- 100->400mhz fast scaling (less aggressive than v212 for better battery life)

- tweak for faster response

- bootanimation support

- do Linpack benchmark of your current kernel vs my kernel for comparison. Only benchmark 5 mins after system bootup (without USB cable attached)

- Linpack: 13.9-14.2@1ghz, 15.3-15.7@1.12ghz,16.5-16.9@1.2ghz

For those that is unstable at 1.2ghz, now you have 1.12ghz to play with :)
[Galaxy S I9000 Android Development] dupel:
Setcpu doesnt see 600 and 1.12 now.
[Galaxy S I9000 Android Development] dereknas:
Great!!! Will give it a spin.
[Galaxy S I9000 Android Development] Medel-Silver:
Is it based on the last version of hardcore speedmod kernel???

I use that and it's awesome

On Eclair I used your last kernel and it's incredible too
[Galaxy S I9000 Android Development] raspdeep:
600mhz was dropped cos i dont see the benefit.. the latency just to scale with 600mhz causes slow down but it is probably better for energy saving. i will try to run some test later and if it doesnt cause too much response hit, i will try add it in. i separated 1.12ghz as another kernel for those that cannot run stable @1.2ghz

its not based on hardcore tweaks cos it will be duplicating efforts. i try to tweak more on the cpu part. if you like hardcore's kernel speed, i doubt you will be disappointed in this as i tested it to run better than hardcore's latest kernel even when i limit my kernel's scaling frequency to 1ghz.. why dont u do a benchmark to compare the two.. the difference is not much but its there
[Galaxy S I9000 Android Development] Medel-Silver:
Thanks, I will try it
[Galaxy S I9000 Android Development] raspdeep:
thanks, please report your finding, if it really works better, maybe it can be incorporated in hardcore's kernel to get both software and cpu tweaks
[Galaxy S I9000 Android Development] Medel-Silver:
Both work very well, i will test more your kernel, stability, daily usage, etc

Test Results:

Hardcore:

-Linpack: 12.797 / 6.55

-Quadrant: 1515

Yours (1.2 Ghz):

-Linpack: 14.713 / 5.7

-Quadrant: 1816

Both, software and cpu tweaks, it will be incredible
[Galaxy S I9000 Android Development] xan:
I think I'm gonna love 1.12 Ghz mode, will give it a shot in few mins. I'm little woried about 'fast scaling's possible battery drain.
[Galaxy S I9000 Android Development] raspdeep:
i've ran this fast scaling for few days and battery drain is minimal so i dont notice much difference.
[Galaxy S I9000 Android Development] raspdeep:
your linpack numbers are kinda low.. hmm

can you try limit to 1ghz (no overclocking) using xan's app and check difference?
[Galaxy S I9000 Android Development] Metalzoa:
The only thing keeping me from trying this is Hardcore's 1.2Ghz OC kernel .. it just works amazingly for me. Only thing that still sucks is the GPS, but then maybe I shouldn't be trying to get my location while indoors.

With binds and EXT file system, Quadrant hits 23XX range and the device is unbelievably smooth. Losing about 1% every hour ~ 90 mins on standby. Wifi on, but no sync. It really does everything right .. Im just trying to figure out if its worth it to try undervolt to squeeze out more juice from the battery even though partial wake is not where i lose my juice ...
[Galaxy S I9000 Android Development] Medel-Silver:
Linpack: 14.09 / 5.95

Quadrant: 1581

Diference is too low, why???

I don´t know
[Galaxy S I9000 Android Development] dupel:
Been using it for a bit. So far faster than hardcores kernel. Especially love fast scaling (tried to do so myself on eclair).

Raspdeep, how about traditional voodoo version? As new voodoo rocks.
[Galaxy S I9000 Android Development] xan:
Yeah! 1.12 stable! Thanks raspdeep!
[Galaxy S I9000 Android Development] Medel-Silver:
I try it now and linpack is 16.4 - 16.8

With cpu 1ghz with xan app 14

P.S. I did not read i must wait 5 min after boot, jeje
[Galaxy S I9000 Android Development] Bo$s:
Thanks for this kernel raspdeep :)

I have one request - please add BLN 2.2 support to your kernel and it will be great! :)
[Galaxy S I9000 Android Development] pcboyy:
I guess 1.12ghz is the limit for the stable sgs daily usage.. 1.2ghz keeps hanging on me, thanks for the great kernel :)
[Galaxy S I9000 Android Development] xan:
+1 for BLN,

I would like to use 1.12Ghz kernel on daily basis, BLN is the only feature I miss.
[Galaxy S I9000 Android Development] dupel:
However, speed has downside (even with uv). It is much more power hungry than normal scalling.

Barely lasted a day today, when I can usually go by day and a half - barely two.
[Galaxy S I9000 Android Development] raspdeep:
ya, the number looks more like how it should

I will try add in

it will be a little but with UV, you should not feel the difference much. Use it for a day or two more and see how bad the condition is..

i left my phone untouch at night after 8hrs still 3% drop without data connection so i think that is pretty good. did you get similar results when phone sleeping?

i read you are using ext4 so it will drain more battery
[Galaxy S I9000 Android Development] EarlZ:
Could you site examples where it is faster compared to hardcore's kernel as ive tried this kernel and it didnt seem faster on my end, I might wanna give it another run through.

@Topic

Would playing a video with rockplayer (hardware mode) or using the stock samsung video player work well as a stress tester?

Would it be safe to replace the zImage here to one of hardcore's CWM flashable zip so I can skip odin for this and flash anytime ?
[Galaxy S I9000 Android Development] dupel:
Havent tried with sleeping (probably will be good results). But during light usage it appears that phone is much more responsive because of fast scaling and thus uses more than usually.

I do however need a couple of days to have a better idea of how it behaves, but "preliminary" findings - eats quite more battery.

I usually use for testing opening speed of handsetsms (bear in mind that I have 2k sms), opening speed of gmail and most importantly: using beatiful widgets home widget when I click on weather I measure how fast and how smoothly it opens weather pop-up menu.

This kernel beats hardcores at first two very-very slightly (I wish raspdeep added all other tweaks and complier options as hardcore, at least for a test version... I'm even thinking of compiling myself) and vastly beats hardcores kernel at 3rd test (it always lags on all other kernels).
[Galaxy S I9000 Android Development] raspdeep:
benchmark it is the best you can do. linpack shows .3-.4 more than hardcore using k series at same 1ghz.

rockplayer software mode will stress the cpu good and will show instability. if 1.2ghz is unstable for you even without UV, try the 1.12ghz kernel
[Galaxy S I9000 Android Development] EarlZ:
@dunpel

Ok, just a quick one.. still on RFS?
[Galaxy S I9000 Android Development] EarlZ:
Never had a crashing issue when I gave the 1.2Ghz a try before, will try it again later on.
[Galaxy S I9000 Android Development] raspdeep:
i will release the source soon so you can put all in since hardcore find it unstable to use, i've made a 1.12ghz which i think 99% phones should be able to run
[Galaxy S I9000 Android Development] dupel:
ext4x3.

Do really want to try out the new voodoo... It has all the possible speedy mount points, and mounts system as well.. And sound... Ah =)
[Galaxy S I9000 Android Development] EarlZ:
It would be interesting to see the 1.2Ghz on the K kernels, dupel if you can.. please share the your recompiled when its done.
[Galaxy S I9000 Android Development] raspdeep:
hmm.. its been long since i talked to curio, will hv to hit irc again.. but after 2 weeks on ext4, it does uses more battery.. so i suggest to only do ext4 in /data if you are really concern about battery life.

now with oc/uv kernel, even rfs is bearable
[Galaxy S I9000 Android Development] EarlZ:
are the SMS messages also stored in /data?
[Galaxy S I9000 Android Development] dupel:
I am a very-very lazy person =) But I'm slowly getting to point where I finally want to do some stuff myself.

Well, I'm usually satisfied with battery life (and I have spare one :D ), plus I'm a speed junky :cool:

If im not mistaken - in dbdata. But I do notice speed up in rfs-ext4 and different kernels. Seems that loading speed is more heavily influenced by cpu speed (or more likely amount of data kernel-cpu-system can process in a second) than lagfix.
[Galaxy S I9000 Android Development] raspdeep:
will you be game to do voodoo oc/uv + hardcore tweak kernels?

its not hard, just time consuming but if you have time in your hand to put everything together, i will run your kernel :)
[Galaxy S I9000 Android Development] EarlZ:
Installed the 1.2Ghz Kernel, played a vid under rockplayer (SW mode) for 15mins, closed rockplayer and connected to USB.. screen went off but touch buttons are lit and the phone vibrates after a while, popped the battery out and power on the phone I get a vibrate after the Galaxy S logo, restored back to hardcode's kernel and wiped cache, removed SD card and still getting a no boot.. right now.. anyway to salvage this aside from flashing to a fresh new firmware?

I was also too careless not to make any nandriod backup's before flashing.. damn it! but Im making one now maybe it can work after restoring... I have EXT4 if it matters.
[Galaxy S I9000 Android Development] raspdeep:
what was your UV settings?

well, you could have run adb shell and do rm -r /dbdata/databases.. that should reset your phone to default state and boot up at least
[Galaxy S I9000 Android Development] EarlZ:
just a -25mV

after some trial and error in restoring my back-up I see its the /data thats been corrupted or something..

I've used adb shell before but Im not familar on what state to put the phone in before I perform the rm -r/dbdata/databases, should I go into recovery and use mount USB or something ?

EDIT:

I lost my copy of adb, can anyone post a link to that package , the pack that does not need the sdk..
[Galaxy S I9000 Android Development] raspdeep:
once the phone got past the galaxy S logo in the beginning and is booting, adbd should run.. even if the screen is off. my kernel has rooted adb shell so should not even need to run su

download android sdk from here: http://developer.android.com/sdk/index.html

extract the folder (name it to sdk or something easy to type) into your computer and open up command prompt.. cd to the drive/directory you extracted the folder and cd again to tools directory, run adb shell
[Galaxy S I9000 Android Development] EarlZ:
Performed the command and rebooted the phone and still nothing.. while I was typing it in the phone vibrated from time to time.. any other thoughts?

The last nandriod backup I had was Nov13 =(

Whats important to me is the content on my Inbox, I can easily reinstall my other apps anyyway... and I think I only added like 2-3 apps since then.
[Galaxy S I9000 Android Development] raspdeep:
sorry bro, if you did not backup, very likely your data will be gone. you should try restore nandroid backup to at least get your phone running. whats strange was phone vibrating.
[Galaxy S I9000 Android Development] EarlZ:
I did have a nandriod back up last Nov13, im restoring it.. my Inbox was backed up on the 17th
[Galaxy S I9000 Android Development] ashwinds:
@raspdeep - phone vibrating is typical when the phone is in that flashing S state.
[Galaxy S I9000 Android Development] raspdeep:
good to hear you have backup :)

hmm.. i dont recall having vibration during flashing S. Well, i have to pay more attention i guess. usually if my phone doesnt boot, i will fire up adb and check dmesg and logcat :p
[Galaxy S I9000 Android Development] EarlZ:
Ok so Im back testing the 1.2Ghz kernel, Id probably say no undervolting for my phone... but ill perform a Nandriod backup now and try to get -25mV and perform some testing see If my phone goes out again.
[Galaxy S I9000 Android Development] EarlZ:
My Inbox backup is a day old, better than losing everything I guess.

The first vibration starts on the Galaxy S logo, this only happens if something is wrong.. for normal operation it does not vibrate.

I can start to feel the speed on this 1.2GHz would be awesome if this is combined with hardcore's
[Galaxy S I9000 Android Development] raspdeep:
dont UV at 1.2ghz but you should be able to do some UV at lower frequencies.. Check first post on OC/UV 101.. Start small and go up higher when you know its stable enough but generally, the lower frequencies, can do quite a bit of UV'ing
[Galaxy S I9000 Android Development] ashwinds:
No - not in normal bootup. But when it hangs - it vibrates. I think its part of the "replay boot animation" code - just to show that its still doing something :)
[Galaxy S I9000 Android Development] EarlZ:
Id like to add for what this is worth, if I dont use setCPU to performance, the linpak is 16.x but if I set it to performance and its always clocked at 1.2Ghz the linpak goes at about 17.4

Would it case damage to my CPU if i use setCPU and set it up for performance mode, Im kinda like thinking there should be a setting for setCPU to just like go in 2 speed modes 200Mhz if screen is locked and 1.2Ghz if unlocked.
[Galaxy S I9000 Android Development] raspdeep:
setting the governor to performance will make it runs at 1.2ghz ALL THE TIME. this means your phone will drain battery very very quickly so it is not advisable unless you are playing games.

what you wanted is similar to ondemand governor which does something similar but in eclair kernels, it is not stable but i did not try it on froyo. from what i've tested, setting anything other than conservative usually causes more battery drain
[Galaxy S I9000 Android Development] EarlZ:
Ok so after some playing around I lock my phone, took lunch and the phone powered off.. lol so im guessing my phone is not stable with the 1.2Ghz OC w/o undervolting.. But I have to tell you though the UI experience is VERY smooth.. Dunno if its because of the 1.2Ghz and I doubt its always running at 1.2Ghz when moving around the UI or theres something in your tweak thats not on hardcore's that making it noticable smoother on this release.
[Galaxy S I9000 Android Development] raspdeep:
if you dont have much luck with 1.2ghz, try the 1.12ghz one..
[Galaxy S I9000 Android Development] chrisjcks:
Hi, im new to this kernal so im giving 1.2ghz a go.

Quadrant scores cpu at 1700 instead of 14xx during full benchmark.

1115 total score with no lagfix installed, with voodoo it scores 1800 instead of the usual 15xx or so.

Hows this thing on battery, im coming from hardcores 500hz kernal.
[Galaxy S I9000 Android Development] XziTe:
Damt!

Updating SetCPU changes my OC! oO? (down to max. about 500MHz)...

Now my galaxy boot but after mediascanner the phone do nothing more... just reboot with power button is possible... think its crash all the time because low frequency

Any help for this?

I hope :(
[Galaxy S I9000 Android Development] XziTe:
reflash the kernel dont solves the problem :(

if the mediascanner starts system crashes
[Galaxy S I9000 Android Development] ashwinds:
Connect via adb shell, uninstall SetCPU and then try.