yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] gokhanmoral:
I did.

apex, nova, swiftkey3, touchpal keyboard, samsung keyboard and new touchwiz.
[Galaxy S III Original Android Development] :
you don't flash that script, it is for i9000. it's in the kernel already.

edit: stealth gokhanmoral, always around and faster:)
[Galaxy S III Original Android Development] cba1986:
I also noticed that on lulzactive the four cores are not always on. Most of the time three of them go offline. I took an screenshot from system tuner.
[Galaxy S III Original Android Development] evrest:
Will there be any chance that first two core only be overclocked
[Galaxy S III Original Android Development] EdgaBimbam:
i didnt flash, i have put manually at etc/init.d that script. Just testing. Maybe it will give some smoothness, maybe not :D

---------- Post added at 08:23 PM ---------- Previous post was at 08:22 PM ----------

btw i know that ics is from old times. But maybe it isnt hard to implent that script on 1.5.3 ics kernel? ;) just wondering
[Galaxy S III Original Android Development] gokhanmoral:
it is in /sbin/ext/tweaks.sh

you can get only the last for loop and put it as an init script and it will work.

I said it is experimental because changing the priority of kswapd0 may have some adverse effects and maybe boosting the process priority of the others won't help.
[Galaxy S III Original Android Development] EdgaBimbam:
yeh i understand that it is experimental :) but i always like to try new things :) btw maybe anyone could copy paste that tweak from tweaks.sh? :) thx
[Galaxy S III Original Android Development] gokhanmoral:
I will push ramfs changes in 10 mins.

you can look at the contents of that file in ramfs github (link in the first post)

EDIT: pushed
[Galaxy S III Original Android Development] albireox:
Only if you select "dual core mode" from stweaks. But in this case, you'll have only two cores active.
[Galaxy S III Original Android Development] Tk-Glitch:
As I've said earlier (with a big typo btw), I think that's directly linked to the difference between frequency table :

{L1, 1700*1000} sending 1700 MHz (SetCPU reads this as available step)

and the APLL value :

((213<<16)|(3<<8)|(0x0)) sending 1704 MHz. (SetCPU reads this when you are actually on the 1700MHz step, and locks because the step doesn't exist)

GM should try to set ((425<<16)|(6<<8)|(0x0)) for 1700 MHz or keep 1704 MHz in the freq table.
[Galaxy S III Original Android Development] XDA mark:
Flashed 1.6.6, I am seeing choppiness on the homescreen while using Nova. CM10, nothing changed in Stweaks.

It's really noticable lag
[Galaxy S III Original Android Development] NZDroidDev:
People on this forum have no issues with users leaving posts stating experience or thoughts about the kernels. What people have an issue with is users not reading. Right at the top of the OP in large lettering GM has posted a link and a message about where to post experience and thought related posts (non development posts) on the syiah discussion thread, he also has said several times throughout the thread that anyone too lazy to read or who ignores what is posted is open game to flames etc. The fact is this is a development thread, it is a thread specifically for posts relating to proper bug reports, requests, and other such related posts. Long and short of it is, if you don't want to be flamed, post in the appropriate thread.

Yes we are all noobs at some point in time, but even a noob can read back a few pages and read the OP, to make sure they dont post in the wrong thread.

Now I'm not saying that being nasty is acceptable, but you do need to realise that those trying to follow the development of the kernel also experience 'pain' at having to read pages of nonsense because people continuously post in the wrong thread, even after several warnings from the dev.

Please keep the discussion on topic, everyone gets rather annoyed at having to read 20 pages of posts to find the 3 posts that are actually on topic.
[Galaxy S III Original Android Development] gokhanmoral:
hmm now I can see the problem.

there was another problem with clocks not being set correctly but it is not related with this one.

and no, I will not make the step 1704 for the reasons I have mentioned before.

I may try the second option but I think 425 is just too high, I am not sure if it will be stable.

I will prefer to make the scaling possible from 1704 to a lower freq by applying an old patch because the scaling fails when 1704 is not found in the available set.

good to have more bugs...

so, until I fix it do not use 1700 because it has frequency disorder :)
[Galaxy S III Original Android Development] gokhanmoral:
any chance that you are using lulzactiveq?

if not, then I better remove those tweaks in the next version.
[Galaxy S III Original Android Development] XDA mark:
Pegasusq. Didn't change anything in Stweaks. So unless Lulzactive is the default govoner, it should be pegasusq.

Just checked, its pegasusq.

Edit: just to be clear, no undervolting, quad core mode, 1.4GHz. All stock.
[Galaxy S III Original Android Development] edgarf28:
@gokhanmoral can you answer my question maybe on the previous page about the newest wi-fi driver from the Note II? does your kernel include this driver, like Perseus' kernel?
[Galaxy S III Original Android Development] GrimPivo:
Dunno is it kernel related or not, but strange thing just happens: my phone at wall outlet charge, but thinks that he connected to USB (according to all battery testing apps).

I'm on Omega v27.1 and Siyah 1.6.6. AC charger - samsung stock.

Charging boosted to max in STweaks.

WTH?
[Galaxy S III Original Android Development] Milchbeck:
With the lutzaktivq is all smooth I have 200-1000 and nothing laggs :D

PERFEKT work!

Aktuell:

CheckROM EvoHD ™ V5.5

ICS BLUE By Raubkatze
[Galaxy S III Original Android Development] :
http://www.gokhanmoral.com/gm/2012/09/27/siyahkernel-s3-v1-6alpha/

(hint 1.6 –> 1.6.1)
[Galaxy S III Original Android Development] edgarf28:
Thanks!
[Galaxy S III Original Android Development] cba1986:
Anybody?
[Galaxy S III Original Android Development] brunodmjr:
1.6.6 is Really choppy at nova launcher. =/ if it helps, in using 1.6rc2 repacked and it works perfectly
[Galaxy S III Original Android Development] gokhanmoral:
please check github for such questions.

I did not check note2 sources but https://github.com/gokhanmoral/siyahkernel-sgs3/commit/ac6881cbd2884b16dc83db4c9e72072ce30cfbce

this one is from note2 lte (n7105) sources which were leaked.

but I don't think wifi signal strength will ever change with a driver unless it uses another mode and the new one doesn't. maybe firmware may change it. anyway...

if there is any newer source you can suggest I am open to suggestions.

but I think this one is the newest one from samsung as it is not even published yet.
[Galaxy S III Original Android Development] tranquility:
Hi Gokhan

first of all thank you for these quick updates, it's really better now with 1.6.6 i'll observe it further but for now i can say that it's far better.

my question is maybe sounds noob is process priority modifications already implemented in kernel or should we cwm it, if needed to cwm which one is needed
[Galaxy S III Original Android Development] MuertoKo:
Posible adding Smart Keyboard, or can I add it via script or kinda? Testing 1.6.6 on stock LIB now !
[Galaxy S III Original Android Development] Ostatni:
Sorry if my problem was repeated but there are so many sites that it's hard to find.I set music bost on 62 and sometimes just shifts the default and only reboot helps. I use last PA 2.16+ 1.6.5 your kernel
[Galaxy S III Original Android Development] gokhanmoral:
conflicting feedbacks :)

hard to make it everybody happy...

my guess is that the widgets make it choppy.

maybe the hightest priority is not a good idea for nova.

I will comment out that tweak when I publish 1.6.7 to fix 1704<->1700 confusion.
[Galaxy S III Original Android Development] Milchbeck:
Please look Screenshots from Quadrat benchmark and Antutu benchmark.. Wow

This is with lutzaktivq 200-1200 dual core :D;)

Aktuell:

CheckROM EvoHD ™ V5.5

ICS BLUE By Raubkatze
[Galaxy S III Original Android Development] cba1986:
Sorry to be persistent but i flashed 1.6.5 and the four are core active all the time, this is not the case with 1.6.6 i am using lulzactive by the way.

EDIT: The screenshot from the left is 1.6.5 and the screenshot from the right is 1.6.6. in the same condition and the same ROM(stock LIB and)
[Galaxy S III Original Android Development] gokhanmoral:
ok uploaded v1.6.6i

please check if it fixes 1704MHz problem.

and I modified process priorities a little.

hope it helps with the sluggish launcher performance with full of widgets.

that's all for tonight.
[Galaxy S III Original Android Development] Franc38:
I've been trying 1.6.6 for the last hour or so and the impression is quite mixed.

With Apex on Omega 27.1, phone gives the impression to be faster YET choppier than with 1.6.5...

Pages flip quicker, I feel, but the transitions and rebounds are not as smooth as they were with 1.6.5...

I'm trying to decide whether I prefer it this way or the "slower but smoother" previous version... :confused:

Ok, missed 1.6.6i being release. I'll try it and see if that changes things ;) Great and speedy work, Gokhan !
[Galaxy S III Original Android Development] gokhanmoral:
it is a matter of settings and defaults.

if you set the same parameters in setcpu to the ones in v1.6.5 you will have the same behavior.
[Galaxy S III Original Android Development] cba1986:
I will try that with 1.6.6i and report back.

Hd you change the parameters in the kernel for 1.6.6i for lulzactve?
[Galaxy S III Original Android Development] MuertoKo:
With 1.6.6i Nova working great even full of widgets here ;)

All rest looks good at launch at least but will keep reporting ofc, which is the default cfs now? Samsung??

As said before can we edit those memory priorities on any place or needs recompile?? Want to try adding Smart Keyboard to it to test how different priorities behave on keyboards :)

Great work anyway!

Edit: Ok, now I can say, IT'S smoother than before on deodexed LIB, way more on scrolling on xda and browser as well as gaming, just tweaked a bit my GPU to set Min. Freq to 266 then 300/350/4XX/566 and put voltages acording to it :D

Edit2: managed to put Smart Keyboard to memory priority by copying a ine on tweaks.sh and adding the process "net.cdeguet.smartkeyboardpro" to it with -10 like the others, is this the proper way to get it?? (Srry for asking before looking for it btw)
[Galaxy S III Original Android Development] cba1986:
No more 1704 step problem. The only thing that i would like to do is change lulzactive parameters to make it work like 1.6.5. I cannot do it in setcpu( I can only change parameters with setcpu to interactive, ondemand and conservative.)

It's working like hotplug.
[Galaxy S III Original Android Development] Franc38:
So on Apex, 1.6.6i is definitely smoother than 1.6.6... Now, I can't really decide weather it's smoother than 1.6.5... But 1.6.5 was really really buttery smooth on my device, so that means 1.6.6i looks great so far ;)

using hotplug as a governor lately... Seems to give very good battery and ramp up nicely for heavy usage.
[Galaxy S III Original Android Development] Milchbeck:
Oh yes 1.6.6i is soooooo smoothly :D:thumbup:;)

:D Lutzaktivq rocks :D

Aktuell:

CheckROM EvoHD ™ V5.5

ICS BLUE By Raubkatze
[Galaxy S III Original Android Development] AndroidGX:
Just re-opened my computer before going to bed, to say that 1.6.6i perfectly fixed back my lags/stutters issues on GTA3 from 1.6.6 !

Thanks gokhan :good:

The kernel looks perfect to me for now.
[Galaxy S III Original Android Development] BUFUMAN:
hmm not for me

its fast but if u start to scroll in:

Tapatalk

Watzapp

its stuttering more than @ 1.6.4 dude

i think its really hard to make it smooth on different roms
[Galaxy S III Original Android Development] MuertoKo:
What rom are you using? For me on LIB and lulzactive it's running just amazing! Only problem, and it's a base one, is when opening keyboard on WhatsApp it... "lags" for a while, but surely not scrolling nor whats, xda or browser!
[Galaxy S III Original Android Development] bigr1979:
has anyone got a link to 1.6.5 please ?
[Galaxy S III Original Android Development] GrimPivo:
Here: https://dl.dropbox.com/s/s9x6k4s2ej8qyso/Siyah-s3-v1.6.5-CWM.zip?dl=1
[Galaxy S III Original Android Development] Stivikivi:
are you guys resetting stweaks when flashing an update?
[Galaxy S III Original Android Development] Franc38:
Nope, unless specified by GM. For identical features, that is...

---------- Post added at 11:58 PM ---------- Previous post was at 11:53 PM ----------

As a rule I always keep, in the same "kernels" directory on my external sd card, the last 3 kernels (sometimes 4 when they're really in "alpha/beta" state) I've flashed.

That way, I can revert easily to the previous or previous but one version if bad things happen...
[Galaxy S III Original Android Development] stamatisx:
1.6.6i with CM10 (latest nightly) lulzactiveq and noop, @1.7 -25mV, stock GPU clocks -100mV for all steps.

The phone simply flies! Awesome work!

Also a couple of benchmarks after stress testing the CPU for stability.
[Galaxy S III Original Android Development] BUFUMAN:
I am on Omega v27.1

No lags with keyboard the kernel feels smooth until i start scrolling at my contact list or at tapatalk

Browsing is fine.

I did a reset before i flashed tbe new one.

Gesendet von meinem GT-I9300
[Galaxy S III Original Android Development] aamirleo55:
when will the new kernel release ? im eagerly waiting for it
[Galaxy S III Original Android Development] Vaedryn:
In two days, eleven hours, twenty minutes and thirteen seconds.

Its done when its done.

via.Tapatalk
[Galaxy S III Original Android Development] thyttel:
Sendt fra min GT-I9300 med Tapatalk2
[Galaxy S III Original Android Development] quattro_rs:
What do I set smooth scaling level to, the cup is set @ 1200-100/ max-min?

Can someone provide me with a link for extweak documentation .
[Galaxy S III Original Android Development] KennyLegend:
Gokhan what parameter would u recommend to adjust to get smoother scrolling? Smooth scaling perhaps?
[Galaxy S III Original Android Development] jayharper08:
Seriously? You did not see my post like two before you? If you want it released, start working on it yourself and stop harassing the dev.

I'm asking again to please stop with posts like this. I will start handing out infractions for spam if necessary.

---Jay--- From the Nexus
[Galaxy S III Original Android Development] gokhanmoral:
although I have "almost" completed v1.3 changes I need to fix one last thing about GPU part before I release it and unfortunately I was very busy this week.

and please read the second post, especially the first point is important.

if you don't be careful about cm9 bug reports people in cm9 team will hate me more :)

we need a single kernel image for dual-booting and it is why I have added cm9 support, but I don't use cm9 as my daily rom and I don't recommend you to use this kernel on cm9 for now.
[Galaxy S III Original Android Development] aamirleo55:
oopss.. im sorry. it will never happen again. seriously
[Galaxy S III Original Android Development] zodiaxe66:
"READ THESE FIRST" should be highlighted in big red types,so everyone can see it clearly when scrolling down the page...
[Galaxy S III Original Android Development] quattro_rs:
never mind, found it :) :

http://xdaforums.com/showpost.php?p=23616564&postcount=6
[Galaxy S III Original Android Development] mrmrmrmr:
well, I really need cifs. I'd be pleased if anyone can point me what I'm doing wrong...
[Galaxy S III Original Android Development] danielsf:
Just got my s3 today, I have moved from the s2. I loved siyha on my s2: ) I am quite happy, I have used the -100mV under volt option in extweeks and I have been playing nova 3 for an hour, and played music a lot and it is rock stable all day. My original s2 was a great undervolter, it looks like my s3 is going to be decent as well. I am really hoping the gpu will eventually be able to overclock by a small amount (i hope its not like the s2 where you could oc the gpu, but the oc was so high that it wasnt good with heat production) Thank you so much:):)

Edit: I'm really sorry, it has been a very long day, and I didn't mean to put this is the developer forum. Tired or not, I should know better. Sorry :)
[Galaxy S III Original Android Development] mark2222:
Me too, had this working on s2 but can't remember how. annoying, it's so helpfull.
[Galaxy S III Original Android Development] Toss3:
Did you try to specify multiple modules in the "Path to cifs.ko" preference by separating them via a colon ( : )?

e.g. /system/lib/modules/cifs.ko:/system/lib/modules/nls_utf8.ko
[Galaxy S III Original Android Development] MrAndroid12:
I have tested a demo unit of SGS3 here in Auckland.

What I observed is; The hotter the phone gets, the lower the performance.

Running stock 4.0.4 Antutu benchmark shows;

First run:

12000

11000

10000

9000

8000

Fifth run

Since it is summer in Hong Kong (Where I was born :) it is safe to assume that the temperature of your phone might have affected your quadrant score as a pose to the kernel itself.
[Galaxy S III Original Android Development] quattro_rs:
---------------------------
[Galaxy S III Original Android Development] edgarf28:
Where? It's not yet released says the official site...
[Galaxy S III Original Android Development] danielsf:
gokhanmoral have you found any GPU frequencies higher than stock that actually work please? I remember some time ago you removed gpu OC'ing as it wasn't working. Anyway, I have used your kernel since I first got my s2, as it always had great customization but more importantly they were so stable. I am so glad I can have your kernels on my s3 :) Thank you :)

Sorry, one last thing. :) Will you ever consider getting the nexus 7, as it would be fantastic to have your work over there. :)
[Galaxy S III Original Android Development] quattro_rs:
ooops sorry my bad, its been a very looooong day ..
[Galaxy S III Original Android Development] cba1986:
Would you check something for me?

Can you check if the four cores are always active?

In my case since 1.6.6 lulzactive is shutting down cores and i don't know how to modify this behaviour.

Thanks
[Galaxy S III Original Android Development] stamatisx:
Sure, what app do you use ?
[Galaxy S III Original Android Development] sharingan92:
Try system tuner then click on the cpu button

---------- Post added at 11:55 AM ---------- Previous post was at 11:54 AM ----------

Just checked and i have the same problem here
[Galaxy S III Original Android Development] Milchbeck:
I have one problem I use the dual core settings but the quad core running??

Aktuell:

CheckROM EvoHD ™ V5.5

ICS BLUE By Raubkatze
[Galaxy S III Original Android Development] stamatisx:
Ok just checked, no problem here, all cores are active
[Galaxy S III Original Android Development] sharingan92:
It may be that way now but for me they eventually go off
[Galaxy S III Original Android Development] Milchbeck:
Okay check please the dual Modus ;)

Aktuell:

CheckROM EvoHD ™ V5.5

ICS BLUE By Raubkatze
[Galaxy S III Original Android Development] stamatisx:
I can let it deep sleep for a while and check back. Any way you can trigger this behavior?
[Galaxy S III Original Android Development] BUFUMAN:
ok one step forward contacts are now smooth like stock kernel!

what i did

CPU @ -50mv

Governor @ lulzactiveq (i don't know what this governor did :p )

GPU like the dude a few post before 266 / 300 /350 / 440 / 533 (voltage @ defaults)

Android logger > off

and one thing for Headphone user the default Headphone Amplifier is toooooo high / distorted you should decrease to 38-40

i use AKG Headphone they dont like it!
[Galaxy S III Original Android Development] cba1986:
Leave the phone untouch for about 20 or 30 second with system tuner and nothing more. This time look at the cpu tab that measures real time usage.
[Galaxy S III Original Android Development] stamatisx:
Hope this helps

First one during idle

Second one after pressing the sd tab
[Galaxy S III Original Android Development] cba1986:
This exactly the thing. with lulzactive the four cores should remain active the whole time. This is almost like hotplug.

I THINK that i found the answer, from this thread:

We are using a modified version of lulzactive. I am basing on this:

@Gokhanmoral. There is a way tweak the hotplugging logic?

Also i found this app to tweak the governor: https://play.google.com/store/apps/details?id=com.tegrak.lulzactive
[Galaxy S III Original Android Development] DrReD:
wow... nice 1.6.6i
[Galaxy S III Original Android Development] iBuzman:
Unfortunately the lulzactive app only works with lulzactive and not lulzactiveq
[Galaxy S III Original Android Development] zappoo:
I see Phenomenal kernel is out for JB - any comparisons? I am very happy with 1.6.6i siyah but just curious as i used to use Phenomenal kernel (medium).
[Galaxy S III Original Android Development] Mumin:
I installed siyah 1.6.6i now I haven't got stweaks, tried using another old version but still stweaks, can someone post the stweaks apk please
[Galaxy S III Original Android Development] cba1986:
The only app i found to do that is SetCpu but only in the latest version which arent free.

I found this:

I didn't find a parameter to deactivate the hotplug logic. What i don't know is what this is:

echo "0" > /sys/devices/system/cpu/cpufreq/lulzactiveq/hotplug_lock
[Galaxy S III Original Android Development] SAEVARM3:
Can I flash this Kernel on stock JellyBean Firmware with Odin to get Root+CWM ?

Peace
[Galaxy S III Original Android Development] naveediftikhar:
Alright...1.6.6i..awesome kernel but somehoq i just cant put my device to deepsleep on hotplug/sio...no sleeping..got a huge wakelock of checking service..which is a google service..so can anybody help me!
[Galaxy S III Original Android Development] sumsy2011:
Yep;)
[Galaxy S III Original Android Development] SAEVARM3:
Thanks for an quick and easy answer!
[Galaxy S III Original Android Development] nfsmw_gr:
For all of you having "issues" with lulzactiveq

Please learn how to use the search function.The issue was a couple of pages back and has been answered by Gokhan.

Exact quote.

Originally Posted by cba1986

Sorry to be persistent but i flashed 1.6.5 and the four are active all the time, this is not the case with 1.6.6

I attach to pictures the one from the left is 1.6.6 and the one from the right is with 1.6.5

it is a matter of settings and defaults.

if you set the same parameters in setcpu to the ones in v1.6.5 you will have the same behavior.
[Galaxy S III Original Android Development] Steve_max:
If you want CWM, you flash CWM. If you want root, you flash CF-Root. If you want a kernel, you flash a kernel. On the S3, the kernel and recovery partitions are separated, so no kernel should include CWM; and root is more easily done with a separate script, which CF-Root flashes.
[Galaxy S III Original Android Development] NZDroidDev:
So what exactly are you trying to achieve? Why would you want all 4 cores running all the time? In idle this would just drain battery. Hotplugging is the most efficient way to manage the 4 cores on our devices. To me this discussion would be best in the other thread, as there is no fault with lulzactiveq, it is working exactly as it should. If you want to have it work any other way, you would have to alter its default behaviour. But I can't think of any advantage having all 4 cores constantly active would have. :rolleyes:
[Galaxy S III Original Android Development] hellsgod:
PegasusQ tweaked like Samsung have all 4 Cores online if they were activated once. So... Is it really battery friendly to switch Cores on and off? Just a thought. To switch a Core on, then off and then on again needs less Energy than let the Core on all the time?

hells

Mit dem Kontinuum-Transfunktionator gesendet