yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] cba1986:
Nobody is saying that lulzactiveq is faulty i understand the behaviour of the governor. Is that i dont understand is why they tweak lulzactive to shutdown cores when hotplug governor do the same thing. as far as i know they both are based on interactive.

And the bettery drain with lulzactive (four cores active) is almost the same as with pegasusq (I lost no more than 1% compared to pegasusq overnight). If you use 1.6.5 (default lulzactive non the q) you will see that the phone is snappier and faster to launch apps without a significant impact on battery life.

I prefer to use lulzactive, i my opinion it react faster and it is far more smoother than pegasusq in games. But is like what i said it is just my opinion. It would be great to have both though.
[Galaxy S III Original Android Development] Jack Barrett:
I also wouldn't be happy to be removed. Weeks ago u wanted to remove it and I asked if u can leave it. Now you wanna remove it again. U can just put notice: please disable for fm radio. I'm audio lover and I appreciate what u made till now. Hope u wont remove it.
[Galaxy S III Original Android Development] Dark_Angel85:
Hmmm it's quite a shame that Siyah has been causing lags and stuttering.. even to the point of some apps closing and freezing...

Used to be flawless back in the ICS days... tried 1.6.4, 1.6.6i...

I've flashed it over wanam v3.7. The only thing tweaked in stweaks is the charging voltaged which I maxed out.

What could have caused the freezing?
[Galaxy S III Original Android Development] NZDroidDev:
Yup, Correct, switching the core off and on does use less power than leaving all cores on at all times. There is no additional power cost in switching it on & off. So why not take advantage of the power savings by switching off extra cores that are not being used? Essentially it is just another form of scaling. I haven't looked into the details of how the S3 does hotplugging under the different governors. But on the S2, the second core was linked to the first, so when it was on it shared the same frequency as the first core. And the load was just halved between cores. AFAIK, multi-core multithreading is not that advanced on our phones, and the cpu load is just shared equally between cores depending on the number of cores currently active.

Extremely basic example (This is only for example, not what really happens in the phones, just to illustrate how having all cores active all the time is more power hungry than using hotplug):

Idle (Not deep sleep):

Hotplug: 1 core active, 875mA

All cores on: 4 cores active, 4x 875mA

Basic task (say scrolling home screens)

Hotplug: 1 core active, 1000mA.

All cores on: 4 Cores active, 4x 1000mA

Edit: Comparing overnight battery loss is kind of pointless really as the phone is in deep sleep. A better comparison would be to measure the battery drain over say an hour long period with the screen on the whole time but doing something that isn't causing high use on the CPU. Something like say reading a book using the kindle app. It is during times like these that the battery drain difference will show the most.
[Galaxy S III Original Android Development] drknezz:
Sorry if I shouldn't be posting this in here, I'm just trying to help out with the "lag" issues people have been experiencing on LIB.

I'm running Omega v27, Siyah v1.6.5 and the only things changed in kernel settings are lulzactiveq governer, sio scheduler and speaker tweaks (tuning, + 3 amp).

Everything runs perfect after the phone boots but after 10-15 mins I get 2-3 sec lag spikes and sometimes slowdowns of up to 20 sec halts where I cannot do anything until the CPU settles.

I've enabled show CPU usage toggle in developer settings and when the spikes or halts commence the 2 biggest processes at fault are mmcqd/0 and kswapd/0

I'm pretty cluey when it comes to using Android but have no idea what these 2 processes are. Im thinking mmc has something to do with my external sd card perhaps. I've got a Samsung 16GB class 4 from my old S1 installed, maybe this is the reason for my extreme lags?

Im going to update to v1.6.6 and leave everything default, take out my sd card and see if that fixes any of these extreme spikes but it's bizarre because with any of the older JB leaks I've never had these lags before.

I hope we can all work together on this and rectify these issues, you've done a great job Gokhan and I won't ever stop using your kernels :D

Sent from my GT-I9300
[Galaxy S III Original Android Development] Dark_Angel85:
+1 in terms of the experience of lag. Same. Starts off well and smooth, then lags start to come bit by bit to the point of freezing sometimes.

Unfortunately, I didn't make the analysis of show cpu. So I can't share it here. will logcat help?
[Galaxy S III Original Android Development] NZDroidDev:
Anything could be causing the freezing. Without logs there isn't much that can be done. Apps, ROM, Kernel, conflicts between any of them, scripts, could be anything.

I have never experienced any of these lags or issues on any Siyah version, so my thinking would be it is a certain combination or ROMs, Apps and settings in the kernel specific to your phone that are causing the issues, as GM put a lot of effort into the kernel to eliminate any issues like this, so i doubt it is solely the kernels fault.

I have been using CheckRom EvoHD V5.5 and Siyah V1.6rc1 to 1.6.6i the whole time I have been on JB. No lags, no freezes, no issues.
[Galaxy S III Original Android Development] Infy_AsiX:
Unfortunately the hotplugging doesn't work well. On my phone I can get down to one core while screen is on only with the hotplug governor. On a friends phone hers doesn't drop to single core in any governor. It's either 3-4 cores or forced 2, so the only efficient option is 2 forced. Pretty strange huh

Sent from my GT-I9300 using Xparent Cyan Tapatalk 2
[Galaxy S III Original Android Development] thunderknob:
Google Now voice search broken.

G'day all.

Just like to report that with the last couple of builds I have noticed that Google now voice search seems to be broken with this Kernal.

I'm using Omega 27.1 JellyBean and have confirmed twice that flashing back to the stock kernal fixes it for me.

Symptoms: I get a picking up sound animaltionin the top right corner but the middle doesn't light up red to tell me it's trying to understand me.

Great Kernal Otherwise.

Cheers. :)
[Galaxy S III Original Android Development] Dark_Angel85:
Agreed. So.. How do you suggest I aid in this? Should I enable android logger? How do I get the log?

Thanks
[Galaxy S III Original Android Development] MuertoKo:
Glad you liked

my setup on GPU :) updated my sign with steps and voltage on each :) no impact on battery and hope it can't hurt in any way!

Does Gpu deep sleep as well as cpu?
[Galaxy S III Original Android Development] NZDroidDev:
A few pages back there were a few posts with apps that can be downloaded to get the logs from your phone. I'm on my phone at the moment so searching for the post and linking it will just take too long as I am at work. But if you do a search on the thread for logs or logcat or something you should be able to narrow the posts down and find it. And then if you are able to post up the logs from when it is happening it will help GM and others narrow down the cause. Thanks
[Galaxy S III Original Android Development] XDA mark:
1.6.6i, no more lag in Nova. Awesome work Gokhan, you're speed and support is great. About 100x as fast as Samsung :p

Will try Lulzactive since people seem to be reporting good things about it.

CM10 0930, stock STweaks settings.

Edit: today I'm testing Lulzactiveq + 50mV undervolting. Curious to see how it goes, first time I'm undervolting on my S3 (though I always undervolted on my S2).

Anyway, so far it's great.
[Galaxy S III Original Android Development] Theshawty:
Im having A LOT of freezes with 1.6.6i kernel. :/

It freezes for some time and then unfreezes
[Galaxy S III Original Android Development] GrimPivo:
Did you try lulzactiveq governor?
[Galaxy S III Original Android Development] gokhanmoral:
tumult told me that he had some weird error messages while using chrome and I wanted to test it.

and I experience the lag now.

I don't know how it is related but I had some massive lags while using chrome.

before then I was using dolphin beta and everything was smooth.

it never caused a crash though. I check with pressing home button 4 times and if mdnie negative effect toggles I wait.

but I had some 5-10 seconds of freezes.

anyway.. I will try to find the reason.
[Galaxy S III Original Android Development] Frostyeo:
Hi guys for those trying out lulzactiveq, or anyone else who has smooth and no lag issues, May I ask do you keep the following ticked under developer settings?

1.force gpu rendering on 2d drawing

2 disable HW overlays
[Galaxy S III Original Android Development] elloar:
I also had the Same Problem with dolphin and Standard Browser.
[Galaxy S III Original Android Development] elloar:
Speed with 1.6.6i

Just for fun

ROM omega 27.1

200 - 1700 mhz

Cpu 266 - 700 Hz
[Galaxy S III Original Android Development] GrimPivo:
That's weird, coz not a sinle lag here in Chrome.

Siyah 1.6.6i (lulzactiveq) + Omega 27.1
[Galaxy S III Original Android Development] Geo1997:
Got exactly the same problem with 1.6.5.

No problem after reset stweaks and install v1.66i ;)
[Galaxy S III Original Android Development] gokhanmoral:
I am still trying to fix that problem in kernel level.

but that problem does not happen only with siyahkernel but also happens with stock kernel even it is less frequent.

if you have no sound on boot (boot animation without sound and no lockscreen sound and no notification) mic doesn't work.

I will try to fix that problem at the kernel level, but it is not my priority.

just use a boot animation with sound and you'll be fine.
[Galaxy S III Original Android Development] gokhanmoral:
yeah, I thought so at first. but after opening 15 tabs with heavy content it starts to lag :)

I am not sure if it happens with stock kernel though.
[Galaxy S III Original Android Development] bordikun:
May I ask what setting was applied to the CFS? since it was removed from Stweaks.
[Galaxy S III Original Android Development] gokhanmoral:
nothing is applied. should be default.. whatever the ROM or init scripts have...
[Galaxy S III Original Android Development] GrimPivo:
I find it difficult to even imagine the necessity of opening 15 tabs with a heavy content in a mobile browser.

Even on my desktop I usually open not more than 10.

But, people use their smartphones in different ways, no doubt...
[Galaxy S III Original Android Development] :
opening 15 tabs in Chrome is just brute forcing it.. under normal usage it happen after few hours or a day or sometime..
[Galaxy S III Original Android Development] Arkanius:
In my case it doesn't happen only when lots of tabs are opened. It's not a exclusive of browsers.

I have to start supplying logs. I had android logger deactivated, now it's activated. I'll return with a log
[Galaxy S III Original Android Development] :
true, but with chrome it is easiest to reproduce in shortest time.. anyway, lets hope Gokhan will find a reason..
[Galaxy S III Original Android Development] GrimPivo:
Oh, by the way! Always forget to ask. Does android logging affects performance of the phone somehow?
[Galaxy S III Original Android Development] NZDroidDev:
GM - Just tested chrome on my phone, with 20 tabs open, varying heavy content, noticed a general slow down, but no actual lags. However, I did notice that ram usage for chrome was blown out quite heavily (50mb+). I have a very fresh build with very few background processes running, so usually only have an average usage of about 450mb, leaving plenty free (possibly why I haven't experienced any lag). It seems to me that it would be something to do with memory, as the lag seems to be worst around high usage. It wouldn't surprise me if there is an issue within memory management within the ROM itself that isn't compatible with something within Siyah? I'm not extremely familiar with the nitty gritty of the Android RAM management, but have experienced similar issues in app programming on PC due to errors in memory management. Just a thought.

Yes I have both checked at all times.
[Galaxy S III Original Android Development] iBuzman:
I have no lag whatsoever [1.6.6i, AOKP b4] using lulzactiveq 1.6 overclock with no under voltage.

I force GPU rendering on 2d (checked) but don't disable HW overlays (unchecked).

I found changing the 3 animation scale settings under developer options from 1 to 0.5 helped things 'appear' smoother. :)
[Galaxy S III Original Android Development] srivas95:
GM I have a bug on my 1.6.6i. Google now and voice typing are not working because the Mic is not being detected It's fine on stock kernel
[Galaxy S III Original Android Development] SAEVARM3:
Yeah but I´m running stock JellyBean Firmware and as I understand Chainfire hasn´t updated his scripts so I can´t use them on my phone running JellyBean ....

Any idea what is the best way to get Recovery+Root on stock JellyBean Firmware?

Peace
[Galaxy S III Original Android Development] NZDroidDev:
GM posted this only 1 page back. Please read a bit before posting :) GM is working on it!!
[Galaxy S III Original Android Development] daath:
+1 to that - I had a total freeze of the phone this morning, just after I deactivated AlarmClock Xtreme - Phone got a little hot while it was frozen. It was frozen for more than a minute - I was just about to pull the battery when it started responding again. I didn't want to post anything, since I didn't have any logs.

I trust GM will track down the bug :)
[Galaxy S III Original Android Development] wl3gan:
ZRAM

No plan to include back ZRAM?
[Galaxy S III Original Android Development] mattiadj:
Guys what are advantages of lulazctiveq???

In have tried it and even with -50 undervolt and 200-1400 mhz my phone became quickly hot. Also all 4 cores are active at 1.4ghz.

I'm making something wrong?

Inviato dal mio GT-I9300 con Tapatalk 2

---------- Post added at 10:57 AM ---------- Previous post was at 10:55 AM ----------

I'm making something better than zram... Check my thread all ASAP I'll release by new fix.

For now is present the old method

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] GrimPivo:
It's faster in smoother in 3D games and UI.
[Galaxy S III Original Android Development] mattiadj:
But it is a battery drainer?

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] XDA mark:
Only problem with setting the animations to 0.5 is that the CRT off effect doesn't work anymore
[Galaxy S III Original Android Development] GrimPivo:
I wouldn't say so. Too soon for reports, only 1 day on lulzaqtiveq, but I have a 4% drain last night.
[Galaxy S III Original Android Development] NZDroidDev:
Battery drain overnight shouldn't be much different between the pegasusq and lulzactiveq as both should be in deep sleep overnight. Lulzactive would drain more battery than pegasus during operation of the phone under light tasks. Under heavy tasks both should have the about the same battery usage. So will depend on the usage as to whether you will have more battery drain on lulzactive. As I perform a majority of light tasks, pegasus is better for my usage. But if you do a majority of heavy tasks Lulzactive may be better.
[Galaxy S III Original Android Development] Akik:
Hi guys, I'm pretty new to Siyah Kernel on S3. I've put governor to Lulzactiveq instead of pegasusq but I left the i/o to default CFQ. Should I change to sio or noop for better smooth UI + multi tasks or CFQ is great too?

I didn't touch anything else as I don't know how it works.
[Galaxy S III Original Android Development] iBuzman:
True, I'm happy to sacrifice it though.
[Galaxy S III Original Android Development] GrimPivo:
By the way, I'm just install System Tweaks now and see that all 4 cores used only when apps running in foreground. If I press home and look in System Tweaks, I see that 4 cores used for a pair of second, then switch to 2, and a bit later - to 1 core 200 Mhz.

I'm noob, so don't hit me if I say something stupid :)
[Galaxy S III Original Android Development] droidphile:
If tweaked 'properly', pegasusq can be made a battery drainer and luzactiveq a power saver. It's just easy as that.

While we talk about pegasusq v lulzactiveq always remember one is ondemand based and one is interactive based. ie pegasusq takes CPU busy time as the reference to identify how critical is performance. Lulzactiveq takes CPU idle time as the reference to identify how critical is performance. Think about it deeply, you will understand why we feel interactive based governors are more responsive and 'fast'.

Interactive governors on exynos can be considered to be like V(R) I/O scheduler behavior-wise. When it performs, it performs the best and otherwise .........

Use setcpu to tweak luzactiveq or pegasusq. Change different values, see how it goes, when you're satisfied, all good. Kernel default values for governor parameters are GM's personal choice. Not everyone can be happy with same settings. Also, it's not a good idea to use apps such as systemtuner to view no of online cores. When you open such an app, an overhead is added as to run queues and it can delay turning off cores. Best would be connect phone to PC, and cat sysfs files on adb to see how many cores are up and down.
[Galaxy S III Original Android Development] Arkanius:
Log from one of my last lagging sessions:

http://db.tt/v0Z9pyie
[Galaxy S III Original Android Development] GrimPivo:
Is it make sence to set another governor for screen-off? And what governor is better, if "yes"?
[Galaxy S III Original Android Development] jay_snake:
Same problem here with Chrome
[Galaxy S III Original Android Development] mattiadj:
Wonderful explanation mate. Thanks!

Since I have setcpu but now not installed, can u share your configuration just for try?

I want a cold phone if possible... With Lulazctiveq I have a hot phone!

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] Arkanius:
You shouldn't select the Disable Hardware Overlay option. It stops the the GPU composition
[Galaxy S III Original Android Development] dmstar:
Chrome is not a recommended browser. (Known for Lags and FCs)

Use others instead...

I am just fine using the stock one.
[Galaxy S III Original Android Development] Arkanius:
Also I might be going paranoid but I'm sure someone did a post that the problem with the lag was concerning the Sharpness mdnie tweak. I disabled it and the phone isn't locking up anymore. (Never had this problem on hardcore kernel but it was on ICS). Anyway it's basically to report that no problems if you disable the tweak. At least for now.
[Galaxy S III Original Android Development] gokhanmoral:
then I guess the thing I am working on will help and hopefully will be the last fix for the remaining lags.

check the changelog for v1.6.7...
[Galaxy S III Original Android Development] Arkanius:
Great. So basically the bad 2d performance and the lags / lockups were all related to the changes you made in attempts to make everything modal.

Good debugging run we had this week!

We should have posted logs sooner.

Sent from my GT-I9300
[Galaxy S III Original Android Development] Theshawty:
Tried it as per your request and it feels okay but it's too early to say if it helped. I don't think it did.
[Galaxy S III Original Android Development] SAEVARM3:
Just wantrd to report what happened to me when I flashed this Kernel.

I had been running Omega ROM just fine for a couple of days, then I decided to try another kernel and I went with this one ... everything was okey when I flashed it, then later that night I was going to play a game that I had been playing (Real Football 2012) ... all of a sudden the game froze and crashed so I just started it again but the second time it froze completely and went into boot loop.

I couldn't boot into recovery, I had to Odin flash stock Firmware and when I had done that I noticed that my internal sd card had been wiped so I lost all my photos/videos and more :(

Just wanted to share my sad story, having a hard time believing that this was the kernels fault since so many people are using it but hey ... you never know :(

Peace and love.
[Galaxy S III Original Android Development] mloc33:
ALWAYS have a backup, no matter what ya do.... Two is the biz.
[Galaxy S III Original Android Development] gokhanmoral:
v1.6.7 is up.

now you can play with mdnie values...

I would love to have some suggestions on them and add some presets.

you will have to reverse engineer them a bit, but I am sure you'll have a lot of fun while playing with them because you won't believe how strange the screen can look like :)

the interface is in /sys/class/misc/mdnie

and an example script is hardcore's sharpness tweaks: https://github.com/gokhanmoral/ramfs-sgs3/blob/master/sbin/ext/mdnie-sharpness-tweak.sh
[Galaxy S III Original Android Development] Franc38:
Will try it ASAP...

However, I must admit that I'm currently back on 1.6.5 which is the best Siyah I've run on my device so far.

I didn't really experience those nasty lags people are speaking about, but for me, general smoothness is better on 1.6.5 than on both versions of 1.6.6 or on previous versions.
[Galaxy S III Original Android Development] XDA mark:
Is flashing 1.6.7 enough to:

solve the lag

have the standard Hardcore sharpness fix enabled?

I'm not sure about this when I read the changelog and what you say. I know one thing for sure: flashing 1.6.7 will solve the lag, but will it also keep the Sharpness tweak? Or do I have to do that by myself? (and if yes, any "simple" noob explanation :p)

I really wan't to have that sharpness mod, a few hours ago I disabled it and couldn't believe how bad the screen looks :eek:

edit: btw, I remember on the S2 there was a "legendary" version which everybody kept using for a long while, it was considered the best for a long time. It was either 2.6.7 or 1.6.7, don't remember. Maybe the same this time haha
[Galaxy S III Original Android Development] :
Hi gokhanmoral,

You're a machine??? :eek:

;)

As always impressed by your work ;), now testing the Mdnie values...

Thanks again: 84P53504EB6657203

:)
[Galaxy S III Original Android Development] mattiadj:
Ehm... I have not understand... What can I do?

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] SAEVARM3:
Well, I don't mind having have to flash everything again but to loose all my data on my sd card is a bummer .... I got into this situation many times on my SGS1 but my internal sd card never got touched, guess the S3 is different :(

Will remember to back up my photos from now on I guess

Peace
[Galaxy S III Original Android Development] gokhanmoral:
I also believe in lucky numbers :)

mdnie tweaks should be working as before.

but they are applied in a different way. the module just creates some interfaces for mdnie values and I changed hardcore's tweaks to a script.

so, if it is really related with the memory allocated by mdnie module it is now linked into the kernel and should fix the lag, and also you can still have the sharpness tweak.

and more, I am sure there are lots of display freaks among us :) hopefully some of them will advise useful modifications on those mdnie values which will make the display better.
[Galaxy S III Original Android Development] elloar:
@

gokhanmoral

1.6.7 is great.

Can we have some presets for mDNIE section like you did in eargasm section:)

For those who are not so freaky in scriptthings :_)

Thx for your wunderful Kernel .it rocks:)
[Galaxy S III Original Android Development] Dark_Angel85:
I've no idea what I just did that caused the phone to suddenly not lag with v1.6.6i

I just changed the gov to lulzactiveq...

could that be the reason it doesn't lag anymore? Cause the thing now is like

... dAMMMmmmmNNNN smooth