yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] danielsf:
Wow I'm impressed, 533 and 600mhz seem perfectly usable for long term use as in heat produced from overclocking. Even playing nova 3 at 640mhz with 1.4ghz cpu it produces less heat than my s2 running at stock frequencies all undervolted. I am so happy we have a usable GPU overclock. Like the performance differences in nova 3 is incredible, at 533mhz it is silky smooth at 1000mV unlike it being choppy before. I think 533 is defiantly going to be my new max freq (I do a lot of gaming on my phone) gokhanmoral thank you and please could we have the option for one more frequency steps for the gpu, as I would love 160,266,350,440,533mhz for the gpu.

Sorry, I am just so happy about this performance increase, as it is just so usable, and as the GPU is the first thing in a phone to go out of date, I think I am going to like this phone for a long time :)
[Galaxy S III Original Android Development] llvllorpheus:
Am I the only one with micro lags? Left all my settings the same a before (all working perfectly on v.1.5b 3), just changed the max. GPU step to 800@1200. CPU @ -100...
[Galaxy S III Original Android Development] Crunozaur:
Yeah, GPU overclock is really noticable. Worth a try, unlike overclocking CPU which gives nothing besides higher benchmark scores.

I'm testing stability for about an hour and 533MHz seems to be stable on 975mV for me.

Temperature (i'm using badass battery app for it, meh) stays on 45 degrees during full load. Default frequency (and 925mV) was running about 3-5 degrees cooler; on the other hand, it's kinda warm today
[Galaxy S III Original Android Development] Tk-Glitch:
Yeah, same here with 1050 mV, I'm a happy camper :D

Coming from ~34 at stock it's really a move forward !
[Galaxy S III Original Android Development] jody2k:
Anyone manages to run it stable @ 800 mhz? :)
[Galaxy S III Original Android Development] Tk-Glitch:
I guess it would pass with around 1100 to 1150 mV on my device, I'll give it a short try.

EDIT : It didn't pass Basemark Taiji with up to 1175 mV (freezing a few times then lock). I guess my chip limit is at 700 MHz with 1050 mV ^^

700 MHz passed a few minutes of Nova 3, Batman, and Dungeon defenders. I'll stress it more to see if it's really stable.

The heat doesn't seem much higher than stock, really impressive !

EDIT 2 : Reran Taiji waiting a bit for the device to boot fully and got 48.75 FPS !
[Galaxy S III Original Android Development] llvllorpheus:
Yes, all stable @800, except for the lags. Now reduced to 700 and the lags are gone. Strange...
[Galaxy S III Original Android Development] jody2k:
Same thing here I tried 1200mv also
[Galaxy S III Original Android Development] Franc38:
Flashed it right now, every thing seems real smooth and nice... I'll report more tomorrow, since I'm off to bed.

Autobrightness seems to be set a bit "too bright" for me. But I prefer minimum brightness in any condition but the brighter sunlight...

Seems like yet another superb Siyah kernel... Many thanks for that, Gokhan!

---------- Post added at 01:30 AM ---------- Previous post was at 01:26 AM ----------

Probably not lags but micro freezes, like bottle necks as this speed is probably the limit for your hardware.

I wouldn't use it too much, the heat and all might shorten the lifespan of the GPU.
[Galaxy S III Original Android Development] llvllorpheus:
Probably. Interestingly, my phone is not really heating up...
[Galaxy S III Original Android Development] nfsmw_gr:
Nice scores man!!

Awesome...

By the way...You are THE Tk-Glitch?From s1 development??

Wooow....:)

Back then i thought tou were the best dev ever! :P

Your kernels for i9000 were wicked!

Nice to see you here...will you be joining us in development too? :)
[Galaxy S III Original Android Development] Tk-Glitch:
Yes I am ^^ Thanks man. Yeah I'll join the S3 devs in a few ;)

Though let's keep this thread focused on gokhanmoral's great work :) !
[Galaxy S III Original Android Development] jody2k:
Also Asphalt 7 is running silky smooth now :D
[Galaxy S III Original Android Development] mmse88:
Same here. That is why I can only use 600mhz:rolleyes:
[Galaxy S III Original Android Development] jody2k:
49,30 on basemark es 2.0 now whoop whoop xd

Edit: 49,97 ^^ changed some gpu threshold settings
[Galaxy S III Original Android Development] menkromsen:
Is it just me or has switching between apps become slower?

Seem to take a short while from pressing an app (from memory) for it to show. I remember things launched instantly before updating to beta5...

On the plus side: Speaker tuning works exceptionally well :) Try it out! Play a track, and change the setting on and off.

What a difference!
[Galaxy S III Original Android Development] radeonxt:
i'm loving the new option under speaker amplification.

as in daym! speaker tuning for the win!!!

running smooth with touch boost @ 200mhz.

btw, someone asked was it here or on another thread that setting speaker to 63 would lessen its life? is that true or any proof to that?

don't see 63 at full volume distorting sound even on music full of heavy bass.

only distortion i see was flowers notification.

no problems switching apps here.
[Galaxy S III Original Android Development] m00moo:
What does the Touch boost do? Running it at 500mhz and I don't notice any difference atm. Great Kernel btw Gok!
[Galaxy S III Original Android Development] Chris_84:
Thanks Gokhan for this great kernel! Tested zram and swap and both are running great. Got swap on at moment and now my phone got 1.6 GB ram:)
[Galaxy S III Original Android Development] menkromsen:
radeonxt: You're running Touchboost at 200mhz without lagging? That sure is low!

(Touchboost boost the cpu clock to the value you set when you touch the screen. In that way you can eliminate lags if you don't set it too low)

I guess people were just guessing (lol) that the speaker could take damage in the long run, playing it really loud. It's no good for a speakerelement to distort all the time, but I think you can play for quite some time still. So in my simple world, this should be nothing to worry about.

Although I do think it distort somewhat at the loudest volume (with slider at 59-60) when playing some songs. Not all though, so I keep my slider at 58. More than loud enough for me.

I also think that the distortion we can hear sometimes is from the preamp stage, and not the actual speakerelement itself. I guess that the Speakertune option just adjust the eq in the preamp stage, and therefore -on some songs will start to clip.

The speaker adjustment is probably done in the analog department.
[Galaxy S III Original Android Development] radeonxt:
i'm noticing faster battery drain on this beta.

nope i'm not overclocking.

i'm for underclocking/volting to the point where it doesn't sacrifice performance too much.
[Galaxy S III Original Android Development] nodstuff:
49.97

Not bad on a 720p screen, every other phone in the comparison has a lower resolution.

The Mali 400mp4 is a beast.
[Galaxy S III Original Android Development] radeonxt:
for those new to this, tell us how to test please.
[Galaxy S III Original Android Development] nodstuff:
Where do you see 1.6gb of ram?
[Galaxy S III Original Android Development] Chris_84:
I mean the total ram. Here's the screenshot:

Edit: Here's another one. You can see it on the little widget.
[Galaxy S III Original Android Development] nodstuff:
What's the app?

Link?
[Galaxy S III Original Android Development] Chris_84:
It called ramexpander. You can get it from the play store but it is very expensive (bought it back in my s1 days) and it's a little bit tricky to install cause market say it's not compatible. So I downloaded it on my s1 and safe the apk with titanium backup and than send the file via Bluetooth to my s3 and it runs. :)
[Galaxy S III Original Android Development] menkromsen:
Took a wild guess and searched for Swap it expander on google.

https://play.google.com/store/apps/details?id=com.swapit.expander.de&hl=no

Seems to be the same software :)

Edit: Too slow...
[Galaxy S III Original Android Development] Chris_84:
Yeah you right.
[Galaxy S III Original Android Development] nodstuff:
Thanks guys.

Don't have an S1 or any phone on anything before JB in the house right now, my nexus s and gnex are JB and my sister is using my S1 and she's off at the galway races for a few days.

Oh well
[Galaxy S III Original Android Development] rednav:
@gokhan instant wifi boost on beta 4 with lg8. My signal strength which was earlier close to 1 bar has just gone up to 4. Definite wifi improvement with the new drivers you've put in.

Obviously more battery drain. But I'm happy with it.

Loving your work man!
[Galaxy S III Original Android Development] radeonxt:
good to know that.

but btw, didn't even need to turn on wifi to notice battery is draining fast in latest beta 4.

i'm underclocking/volting btw.
[Galaxy S III Original Android Development] bala_gamer:
@ gokhan

woke up just now and what a surprise. :D

thanks a loads gokhanmoral... you just took our mobile to next level with this release.

All the benchmarks are amazing

gl benchmark 2.5 egypt hd

14 fps @ 600 mhz

15 fps @ 700 mhz

gl benchmark 2.5 egypt classic

57 fps @ 600 mhz (vsync limited most of the times)
[Galaxy S III Original Android Development] kartalgurhan:
Guys, sorry to *bump* but after making adjustments in STweaks and reboot the device, the ONLY that goes back to default is the GPU voltage.

when: cat /sys/class/misc/gpu_voltage_control/gpu_control I always get the default values.

Am I doing something wrong?

PLEASE try and see yourself.
[Galaxy S III Original Android Development] bala_gamer:
regardless of my gpu clock i couldnt go past beyond 35 or 36 fps. :( which rom are u using?

edit : got 41 fps @ 700 mhz(1100mv)
[Galaxy S III Original Android Development] sachinaik:
Gokhan,

I like the audio quality in B3. Something wrong with B4's audio quality.

Went back to B3.

Anyone else feeling the same ?
[Galaxy S III Original Android Development] nodstuff:
Using faryaabs aosp JB rom, raised min GPU to like 300mhz I think and raised each step accordingly and then 700 for the 4th step.
[Galaxy S III Original Android Development] cb_jimmy:
zram is new to me. I have a general idea of what it is. Should I enable it? What size is ideal?
[Galaxy S III Original Android Development] mmse88:
Confirmed beta5 conflicts with V6 Super Charger

The V6 Super charger's minfree will not stick after reboot and will get back to balance level due I need aggressive.

Flashed back to the previous version beta4:rolleyes:
[Galaxy S III Original Android Development] davelinders:
49+ in Basemark.

Settings are: CPU 1600 with -100mv GPU 700 with mv set to1100 and the other three steps are

clocked at 266 350 440 and last step 700.

Did not tried 800.
[Galaxy S III Original Android Development] Cyb3rGlitch:
I get 48FPS @ 666Mhz and 1050mv.
[Galaxy S III Original Android Development] davelinders:
Is this a save clock phone becomes warm totally not hot.

Or is it overkill and just battery eating for nothing?
[Galaxy S III Original Android Development] bala_gamer:
looks like its time to reflash my rom ;). wasted almost an hour this morning and nothing more than 40 even with 700mhz . will report back if it works
[Galaxy S III Original Android Development] davelinders:
I'am back to 1400 -100mv and GPU 533 at 1000mv and the rest -50mv.

700 battery eating and overkill with 533 all games plays smooth.

But I know phone is handeling 700 at 1100mv very good so maybe in the future when

the games needed this clock to run.

---------- Post added at 07:47 AM ---------- Previous post was at 07:46 AM ----------

700 gave me a score of 49 and even 50 in basemark.

With 533 I get 42 and 43 in basemark.

So maybe reflashing rom is not a bad idea. ;)
[Galaxy S III Original Android Development] EdgaBimbam:
Wouod be cool if at op would be written defaupt voltages values for 533mhz gpu and etc because atm at stweaks are given defaults voltages for 166mhz and etc. :) btw b4 rocks. No issues
[Galaxy S III Original Android Development] danarama:
533 is not a default clock speed therefore there is no default voltage. When you change to 533, the voltage used is that of 440mv. Its down to you to find what voltage is stable. Nothing op can do to tell you
[Galaxy S III Original Android Development] DirkStorck:
Hi.when I try to download it from play store it tells me that it is not compatible with my device.

Send from my Omega ROM powered SGS3 :)
[Galaxy S III Original Android Development] FadeFx:
Known problem, mail the dev to make it available for the i9300...

–—–—–—–—–—–—–—–—

tapatalked from Galaxy SIII
[Galaxy S III Original Android Development] Franc38:
It's either a problem flashing the kernel (did you flash with mobile Odin -really the recommended method- or in recovery?), or one of the multiple times we have problems with settings in STweaks when it's "not clean".

I'd recommend resetting to default (last tab). Then rebooting (completely... wait 10 minutes after it's booted). Then reflashing Siyah v1.5 beta 4, and then set all the parameters you want. Then re-boot to see what happens, but I guess it will stay put.

---------- Post added at 09:05 AM ---------- Previous post was at 09:01 AM ----------

Yup...

I get 41.5 with just the highest GPU step to 533 MHz (the rest in default), all steps undervolted -75 and CPU max at 1.5 GHz, undervolted -100...
[Galaxy S III Original Android Development] KMino:
Zram Swappiness seems fine at 60, noticed that app posted before says 90. (Couldn't download it, not compatible with ROM, I use system tuner anyway)

Bet that is choppy and uses more battery. Just mentioning it as it was like that on the SGS1.

Those that say battery use is higher try turning zram off our lowering swappiness down, 40 should be fine.

Good news the large zram size doesn't effect the SGS3 much (like SGS1), have it set to 250 and swappiness to 50 :D
[Galaxy S III Original Android Development] bordikun:
Anyone kind enough to explain zRAM? for none geeky guys like me? :)

Will it increase performance on the phone? if so does that makes battery life suffer in expense of performance? TIA
[Galaxy S III Original Android Development] minipaolo:
could you please explain what that means for noobs like me? :)
[Galaxy S III Original Android Development] nickporwal:
@siyah---- i am getting a black bar in the camera with miui rom. Is there any workaround? Stock miui kernel works though.Everything else is working just great. Thanx for the awesome kernel.
[Galaxy S III Original Android Development] DirkStorck:
What app do you use for greating a swap file...I tried "Swapper 2" but at the end it told me "invalid argument..."

Thanks! :)
[Galaxy S III Original Android Development] mchu6am4:
Hi...can someone please post a couple of typical settings (for a noob to follow) i can apply in kernel to improve performance and battery life etc?
[Galaxy S III Original Android Development] bala_gamer:
you mean system tuner pro?

---------- Post added at 01:21 PM ---------- Previous post was at 01:20 PM ----------

to do both of those at the same time better stick with the stock values.
[Galaxy S III Original Android Development] minipaolo:
There used to be post #6 to explain everything, but it is not up-to-date :o
[Galaxy S III Original Android Development] Franc38:
For typical battery life improvement, the key point in undervolting...

So get -50 mV in CPU, if your phone runs stable then try -75, then maybe even -100.

You can also try applying undervolting to GPU (I use -50 mV at all steps, but then again, you need to find what works on your own device since they are not all totally identical).

The main motor of performances is overclocking. So set the max clock for the CPU to 1.6 GHz instead of 1.4 (you may even have a stable phone at 1.7 or 1.8, but, again, not all phones are able to sustain those clock settings... and they do suck battery like no one's business... )

To increase GPU perfs, you may overclock it as well (I personnally just use 533 MHz as the top step clock, and don't change the rest).

Overall, you don't really need that much increase in perf, methinks, as the SGSIII is a beast on standard settings... Undervolting to get better battery life, is quite useful, though.

I found as well my phone to be more responsive and performing better with deadline IO scheduler...
[Galaxy S III Original Android Development] gsw5700:
Happy to provide my settings:-

CPU

GENTLE_FAIR_SLEEPERS = OFF

ARCH_POWER=ON

CFS_TWEAKS=Linux defaults

CPU_IDLE=idle+LPA

SMOOTH_SCALING=1800

MAX_CPU_LOCK=Quad Core

CPU UV = -75mV (you need to test this in stages)

GOVERNOR=pegasusq

MAX_CPU=1400 (fast enough)

SCALING_MIN=200

GPU

MALI= ON

Standard GPU Steps (with -50mV)

Highest GPU Freq=533MHz @ 1025mV

Default GPU frequency change frequencies

Default GPU staycounts

Audio

Speaker=61

Speaker Tuning = ON

headphone Amp=61

3D effect=OFF

PRESET=EARGASM

FLL/DAC=Enabled

Force Mono=OFF

Screen

All default with negative toggle=OFF

Misc

Android Logger =ON

ADB=OFF

I/O scheduler = SIO

ZRAM = OFF (I have removed a massive amount of bloat so don't need extra cpu cycles squeezing RAM)
[Galaxy S III Original Android Development] Franc38:
We had problems with black bars in cameras sometimes ago with samsung based roms... The key point is then the sources used in the kernel. Possibly MiUI is using a firmware for the camera that is either very new (doubt it) or outdated and in conflict with the kernel newer drivers.

However, I feel it's really not much of an issue, as it wasn't showing on the pics taken (just on the camera screen, check it).

You may also try alternate camera apps that work quite well (I alternate between stock camera and "ICS camera" free from the play store, it's quite good and gives the panorama option back).
[Galaxy S III Original Android Development] Chris_84:
Here's a explanation from wiki:

zRam

zRam*is an available feature for certain distributions of*Linux, that was previously called "compcache". It increases performance by avoiding*paging*on disk and instead uses a compressed*block device*in*RAMin which paging takes place until it is necessary to use the swap space on the*hard disk drive. Since using RAM is faster than using disks, zRam allows Linux to make more use of RAM when swapping/paging is required, especially on older computers with less RAM installed.[1][2]Even though the cost of RAM hardware is relatively low this feature still offers advantages for*netbooksand other lower-powered latops,*virtualization*and in the case of*embedded devices, especially those that use*flash memories*that have a limited lifespan, dependent on write-use and thus wear out quickly when used as a swap device.[2]
[Galaxy S III Original Android Development] gokhanmoral:
I will release it when I arrive home.
[Galaxy S III Original Android Development] the2rrell:
Thanks for the update.
[Galaxy S III Original Android Development] RMXO:
Sweet, I can't wait.

Is it possible to make futures editions of Siyah compatible with AOKP/CM9 to get EXFAT support? Or is that something we have to wait from CM9's end?
[Galaxy S III Original Android Development] FadeFx:
Cm9 vold would need to be reworked as well, it can not deal with the exfat kernel module. I am not sure if it is a big thing to change it, or just adding one or two lines... codeworkx stated it can not that.

–—–—–—–—–—–—–—–—

tapatalked from Galaxy SIII
[Galaxy S III Original Android Development] gokhanmoral:
v1.2 is up.

supports cm9 and paranoid.

just don't report anything if you experience something weird. flash cm9 rom again and make sure the problem still exists.

and for exfat, you can use an init script to mount that for now.

I am sure some aokp/aosp developer will make required changes in vold.
[Galaxy S III Original Android Development] FadeFx:
Gokhanmoral, can extools app be tweaked to allow higher frequency than 1600? I can run 1704 stable, but need second app to set it as extools ends at 1600...

–—–—–—–—–—–—–—–—

tapatalked from Galaxy SIII
[Galaxy S III Original Android Development] gokhanmoral:
yes, but it will be better if you can use voltage control app or init script for that because 1704 is not stable for everybody. although we have some dangerous undervolting options which can prevent device boot, I don't want to add that one.
[Galaxy S III Original Android Development] currydude:
Strange I just flashed 1.2I cwm and lost haptic feedback and boot up is really slow. Going to try flashing back to 1.1 now hopefully not a hardware problem lol

On stock lf2
[Galaxy S III Original Android Development] EdgaBimbam:
hmmm with antutu only i get 4830 score, yeh i know benchmark tests are crapz, but why is it so low? o.O
[Galaxy S III Original Android Development] Meraklis56:
i see lower perfomance,too.Both in booting and in menus :/
[Galaxy S III Original Android Development] FadeFx:
You could add a menu to recovery with special options for the kernel like clear extweaks data...

–—–—–—–—–—–—–—–—

tapatalked from Galaxy SIII
[Galaxy S III Original Android Development] currydude:
Just flashed back to 1.1 haptic feedback is back and phone is responsive

I think the sound stuff is the cause of regression
[Galaxy S III Original Android Development] EdgaBimbam:
would be cool to see 1.1v with audio boost tweaks. Seems that 1.2 lost a bit performance :/
[Galaxy S III Original Android Development] gokhanmoral:
I removed v1.2 because that antutu score was really weird.

I will upload it after finding the reason of that.
[Galaxy S III Original Android Development] Meraklis56:
exactly the same.Faster boot up and must more responsive.With 1.2 the device was struggling.The application draw was refreshing for at least 1 sec.

I dont think to be difficult for gokhanmoral to find whats broken :)
[Galaxy S III Original Android Development] domeniconico:
The version 1.2i the vibration non work .i just setting ,disarged (download ) two (2) for test file corructed (not valid ) the file ok ,the wibration non work .re flash 1.1 vibration ok ,re re flash now new 1.2i non work vibration .tank
[Galaxy S III Original Android Development] currydude:
I know the Samsung keyboard sucks but say what?
[Galaxy S III Original Android Development] dazbutler1:
Yeah same here flashed 1.2 and performance dropped considerably on black star rom. Flashed back to 1.1 and all ok. Will hold off for now till sorted thanks anyway
[Galaxy S III Original Android Development] smsmasters:
I flashed 1.2 and I'm getting around 5k in the AnTuTu benchmark whereas I used to get around 11k.
[Galaxy S III Original Android Development] marioh:
How do I reset ex tweaks settings?
[Galaxy S III Original Android Development] minipaolo:
Ok, I have found this:

http://xdaforums.com/showpost.php?p=27921064&postcount=6
[Galaxy S III Original Android Development] gokhanmoral:
Any problems with speaker tuning?

I will revert back the latest brightness modifications before the release. Any other complaints?
[Galaxy S III Original Android Development] dxdiag32:
tested the newest kernel beta4,and i fell not smooth as beta3 even though i disabled zram(or swao?didn't see the option clearly and i don't remember) and reboot :(

so i back to beta3 now

i don't know where was it wrong,maybe the zram and swap
[Galaxy S III Original Android Development] marck1991:
thanks for asking :)

maybe you can add a "negative value" for min_gamma, for those (like me) who want a darker screen...

speaker tuning is fine for me :) (maybe it could be a little bit less agressive)

all in all it is a great kernel!

thanks for your hard work! -> donation is coming ;)

EDIT: just done 8TM599198R1185838
[Galaxy S III Original Android Development] jott_st:
The EQ Settings are still being resetted after opening and closing Samsung Camera or Music Player.
[Galaxy S III Original Android Development] EdgaBimbam:
For me b4 is alot of smoother than b3
[Galaxy S III Original Android Development] bala_gamer:
guys... reinstalled a fresh copy of checkrom 3.5 and oced the gpu to 700mhz straight.. and guess what the basemark es ti 2.0 taiji is giving me 40 fps.. damn again the same 40 fps i got with cm10. this is getting really weird