yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] alienmind:
For me 1.6.3 has fixed all the freezes and lags on cm10 latest.

Many thanks for this piece of art

Sent with my cold hands from the grave
[Galaxy S III Original Android Development] GrimPivo:
Therei is no discrete wakelock stats for BBS in 1.6.3?
[Galaxy S III Original Android Development] nfsmw_gr:
Actually this happens in every rom..

There is a file transfer to /data/app when market installs(not downloads,this doesn't affect anything) the app that's why the device is lagging.

When the app is installed you're good to go.

@gokhanmoral

Using Wanam 3.7 sammy jb XXDLIB with a manually completely cleaned build.prop and init.d folder(only using external to internal mod) till now i didn't have any lag issues...

i'll test more and report back.

If you want i can attach some logs,even though they were from the previous vesion 1.6.2.

Something noticable about the logs is that there was a lot of vm activity and mali drivers was reloaded again.
[Galaxy S III Original Android Development] currydude:
If that's the case, then there's some kind of i/o problem
[Galaxy S III Original Android Development] NetCopAD:
For me 1.6.3 is a big improvement lagwise. All the heavy lag is gone. Phone is not quite as snappy as with stock kernel and I do experience some minor lagging, but it's waaay better than it was with previous versions of siyah. This version is completely useable for me.

10x!

PS: I'm on Omega 27

Edit: The damn lag is back this morning 20h after I flashed 1.6.3 :(
[Galaxy S III Original Android Development] bordikun:
Just notice it now after reading this. :(
[Galaxy S III Original Android Development] MattBooth:
The stock kernel hasn't lagged and forced a reboot/battery pull for me once. When I first installed JB I installed Siyah kernel and got crazy lags. A friend suggested it might be the kernel and I dismissed this idea... Then in testing my own ROM I tested the option to install the stock kernel and the lags disappeared and haven't come back :(

I get this when restoring from Titanium Backup for sure. It seems that writing to /data/ storage causes major lag on the entire system. But, as other mentioned as soon as the processes is complete the lag is gone and doesn't come back (until you install a few things from the market at once).

This is wildly different to the lock ups people are experiencing with Siyah. On the stock kernel, I don't get a lock up when using Chrome or generally just doing things. On Siyah I do.

This said, 1.6.3 is here so I'll try that for today and see how it goes :)
[Galaxy S III Original Android Development] matust:
I'm using wanam 3.7 (JB) and tried 1.6.2 and 1.6.3. When I had a lot of processes running ie downloading, surfing the web trying to message the phone kept freezing up. Back to the stock wanam kernel and it seems to be running properly.
[Galaxy S III Original Android Development] joe_donkor:
Just hought I would check this thread to see if anyone else was havin problems and it seems they do. Running 1.6.3 with omega ROM. Just pulled the battery as the phone more or less froze doing a play update. But it's not the first time in the last few days I had to do this. I'll go back to stock for now I think.
[Galaxy S III Original Android Development] daath:
Omega 27 here - I flashed 1.6.3 yesterday (to test if lag was there, and to get rid of wlan_rx_wake at work) - Before that, at home, I was consuming 1-1.5%/hour in standby. Last night it consumed 3+%/hour - BBS said wlan_ctrl_wake - odd. wlan_rx_wake seemed to be on a more normal level. Kinda confused by that.

I didn't notice any lag, but then again, I was only on 1.6.3 for like 10 hours before flashing back to RC1 - and the lag is usually first evident after 10 hours or so.
[Galaxy S III Original Android Development] gokhanmoral:
guys, stop the lag discussions please.

I don't have it but some people has it. I already put it in "known problems" part.

and now a friend is helping me to figure out the problem as he can easily get the lag with siyahkernel and no lag with the stock.

I sent him some test versions and trying to figure out the problem.

I have no idea why some of you has it and some of you don't.

for now, the friend is testing a stock-like (very bare) kernel with only mali as module.

I only wish that part is not the problem because I need that to support both samsung and cm10 with a single kernel image.

if it is not the problem I will release a version with some optimizations and patches removed and will try to introduce them one by one.

if it is the problem, I will have to distribute two different kernels for samsung and cm10 until I find a better way...
[Galaxy S III Original Android Development] rlorange:
OK no logs sorry GM but I started getting lags on Wanam 3.7 Siyah v1.6.1. Also a general loss of butter...

I really do feel it's related to mis-simlinked busy box aplets. Since you end up with different busy box versions in a mess from the rom and kernel combined. I had busy box in system/xbin, system/bin AND /sbin from the kernel.

I uninstalled all the rom derived busy boxes and then reflashed wanam with no wipe. This left me with just v1.2 cm9 bysybox from the kernel is /sbin. But stericson busy box app showed me that this stripped down version lacked many applets. Incidently there was UI LAG at this point like I had before starting this "experiment".

Now I installed busy box 1.2 COMPLETE version to system/sbin. With Stericson app restoring missing applet simlinks....

Suddenly the butter returned! Lag GONE!!!

Now I'm no expert here... don't fully understand what I did to fix it but I made a nandroid backup in case I break it again.. Lol!

Hope this helps someone more knowledgeable than me understand this elusive beast.

Edit: Sorry GM was writing before your last post... no more lag discussion:)
[Galaxy S III Original Android Development] dondavis007:
I just want to report that I had a weird screen/gpu crach. Everything went white, kind of, and I had to reboot. Stock no extra settings.

Sent from a gadget...
[Galaxy S III Original Android Development] tolis626:
I am referring to the S3.But you know,it was words of anger.Like when you have a fight with your girlfriend/wife and then you tell your best friend "I want to kill the *****!".You don't mean it(Usually that is) but you say it.Deep inside,however,you still love her. :p
[Galaxy S III Original Android Development] MattBooth:
Hi Gokhan,

I think the lag discussion is more for others to check. I must admit I'm checking to see if others are having the problem too. I also I wanted to dispute what Kenny had to say because the lag that is present in the stock kernel (Titanium backup, or play installs) is different to the lag experienced with the kernel.

I think you're doing a fantastic job and I will be checking back to see how this is going on every day (especially with how fast you're updating)

Don't be put off by the lag discussions as they are helping other members more, really. Don't view them as complaints too easily :)

That kind of lag is also in the stock kernel and not specific to Siyah kernel. It seems to be a wider Jelly Bean issue.
[Galaxy S III Original Android Development] mamba720027:
Sniff sniff...wipes tears from eyes. Touching story,might make for a good movie :D:p

Anyways besides goofing, So far latest kernel running on criskelo rom like butter,sometimes it feels like melted butter and delicious. No lags for me,dunno why but such is life :cool:

Sent from my GT-I9300
[Galaxy S III Original Android Development] nicregi:
I changed to lulzactiveq and some tweak in settings and lag gone.
[Galaxy S III Original Android Development] gokhanmoral:
I don't mind reporting your problems with the kernel but I do mind if you don't do it properly.

I have written it in my signature as well. I will just ignore any reports which doesn't give details or have any additional information to previous reports.

Saying "I have lag" will not help me nor you. It is wasting your time and mine.

You can repeat that you still have lag on every new version but repeating it for different roms with different posts will not help neither.

Just use common sense that's all.

Or the repeated messages or useless discussions will make me turn my hacre mode on which I will regret and so will you.

As I said I am already receiving some help from a friend who can observe the lag in several hours. If you want to help with that and experience lag regularly as well send me a pm and I will send you a test version. Or if you can tell me how to lock up my device with the latest version it will also help. And if you think you cannot help please do not try to slow it down at least.
[Galaxy S III Original Android Development] Netman_:
Some? Specify...
[Galaxy S III Original Android Development] mattiadj:
I don't have lags but I want know how have you tweaked the kernel.

Thanks

Inviato dal mio GT-I9300 con Tapatalk 2

---------- Post added at 03:25 PM ---------- Previous post was at 03:11 PM ----------

Anyone can explain me how works led on jelly bean?

I mean that sometimes led light is very hight as in ics, often not is very low!

It's normal?

Thanks

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] nicregi:
I used the one that one of the xda member gave previously. I think like 4 days ago. Changing the lulzactiveq init.d thingy.

Am outside now. Will share with you guys when I am back home. Saved on my lappy.
[Galaxy S III Original Android Development] sharingan92:
@gokhan

I have lags on paranoid 2.16 but only with games like asphalt and my gba emulator but no random lags like others. In stweaks i have it set to linux kernel default but if i switch to samsung defaults the lags become more frequent also undervolted -25mv an OC 200-1600
[Galaxy S III Original Android Development] tolis626:
Guys,I'm either losing it,or lulzactiveq eliminates the lag to a large extent.With it,it's more an occasional stutter than lag.If anybody can test it too I can see if it's just me... :)
[Galaxy S III Original Android Development] Infy_AsiX:
Governors seem really finicky between devices. On mine hotplug works well in the latest but the others don't as in the past.

On a friends running same omega it doesn't work. But does very rarely briefly then stuck on all cores again.

Sent from my GT-I9300 using Xparent Cyan Tapatalk 2
[Galaxy S III Original Android Development] cba1986:
I have yet to face a lag with 1.6.3. But i can tell that battery life is significantly better on WIFI probable due to Entropy's patch. In 9 hours of idle the drain was only of 5% with everything syncing.

Excellent work!!

EDIT: DELETED.

---------- Post added at 11:17 AM ---------- Previous post was at 11:06 AM ----------

[/COLOR]

And you have an idea why IDLE+LPA is recomended in our S3 when AFTR+LPA (supposedly) saves more power? It's for stability or for perfomance reasons?
[Galaxy S III Original Android Development] mamba720027:
from the faq on very first page i will quote

"8. "Why is Idle+Lpa default on STweaks/ExTweaks and recommended settings. In Siyah kernel for GS2, Aftr+Lpa was recommended!"

A. Aftr ofcourse saves more power than Idle if you consider what each of those low power state modes do. But with quad core architecture and pegasusq/some other hotplugging logic, the last three cores will not turn off as soon as screen is off. Aftr requires that all cores except first (cpu0) be turned off - to kick in. So we're better off with Idle+Lpa.

However if you're using forced single core mode always (which is non sense in this powerful device), you can go for Aftr+Lpa.

"

so to summerize it only in single core mode its worth useing AFTR+LPA. Since the palaxy s2 was a dual core i figure if force the gs3 in dual core mode it would also work but im not clear on this part myself.
[Galaxy S III Original Android Development] AndreiLux:
That FAQ is wrong, the cores do turn off when the screen goes off, but the problem is that AFTR is meant to be used when the screen is actually on. Then it can only kick in when the only one core is online. But anyway the code has fallbacks so even if you set it to AFTR it won't do anything bad.
[Galaxy S III Original Android Development] cba1986:
Whoa. I love when two major devs makes argument's i learn a lot.

I tried installing busybox on sbin but the Stericson tell me that /system/sbin is not valid path. :mad:
[Galaxy S III Original Android Development] mamba720027:
ok that shead some light on the doubt i had about the cores and if it will work.
[Galaxy S III Original Android Development] carlos67:
+1. I used to use pegasusq on s3 with all siyah versions (Omega v27 Rom) and had micro lags. However, about 4 days ago I thought "let's give lulzactiveq a go" after @Edgabimbam recommended it (with cfq scheduler).

This governor plays better than pegasusq from a lag/stutter perspective. I also have forceGPU and disable hw overlays both ticked in dev options & cfs linux defaults (although can't notice much difference if any with samsung defaults - thunderbolt has always lagged rally bad across different roms & kernels).

99% of the time I'm lag free. I get the very occassional micro lag when scrolling the first homescreen after waking up the phone but after that first swipe it's butter all the way, everywhere apart from widget drwaer like everyone:rolleyes:

I'm undervolted -75mV/CPU 200-1500Mhz. On GPU side I'm 266/350/440/533/600 with default volts. Fair sleepers off. Siyah 1.6.1 (but I'm about to flash 1.6.3 and stock to compare.
[Galaxy S III Original Android Development] Satch09:
I hope I'm not infringing on the development policy, please delete if I am.

To contribute in the hopes of changing the "status quo" of gpu settings I want to give my opinion as I feel that the lag or "butter" problem might lie in our gpu settings (yes I know project butter is very much about gpu settings) I don't wish to report a "BUG" but would rather like to give perspective to users having latency issues and experiencing them as problems as kernel bugs.

I must state my ROM: ARHD 11.0 a great ROM which I have used as my daily driver without any roblems.

I want to mention (incase you aren't aware) that there has been a lot of comments about how well ARHD 11.0 works with perseus 23.3, and and it does, but what I want to point out that after looking at Perseus' GPU settings I noticed that the default settings are far more dramatic than that of Siya. If those of you look on Perseus look at /sys/class/misc/qpu_control/gpu*something* can't remember the file but I think it's gpu threshold, you will see that the up and down thresholds are much lower than Siya defaults.

Take a look and try the same settings of Perseus and see how it works before complaining about lag.

I have and I have almost no lag but with the loss of battery life as is the same with Perseus.
[Galaxy S III Original Android Development] carlos67:
I tweak these down in Siyah and don't have lag/stutter problems. For example step 1 up threshold = 60, step 2 down threshold = 40. Works for me and I'm happy to take the very slight battery hit when scrolling around.

Edit: I think maybe @Rlorange has a point about different versions/locations of busybox and also symlinks. I think titanium backup also has it's own version too. Maybe some of the issues people have with lag (on any kernel/rom) are related to this multiple busybox issue?
[Galaxy S III Original Android Development] Schmurtz1968:
I have been playing with GPU threshold for a long time, without being totaly satisfied.

One thing i'm sure, is that Siyah's settings are too much agressives for "project butter", but battery friendly.

Can you share with us, Perseus settings ?
[Galaxy S III Original Android Development] kvv515kvv:
yes it is normal. it is autobrightness. in dark room led is low, and under light led is bright
[Galaxy S III Original Android Development] Satch09:
At 160 up 35 down 21

At 266 up 37 down 26

At 350 up 37 down 25

At 440 there was a space without any values so I don't know if 440 is used.

I've set 1.6.3 to the same (after rounding off the above values) and it's been perfect although my battery is going because my usage today, been quite intensive.
[Galaxy S III Original Android Development] AndreiLux:
Wait wait wait, hold it there. First of all those values are false as they're not displayed correctly (Thanks for the bug), I'm using 0-90, 55-95, 68-95, 64-100. Second of all even if they're different this can't cause any lags as described here.
[Galaxy S III Original Android Development] sohail77:
Does under voting effects the performance of the phone and what are the best underlying values to maintain good balance between performance and battery
[Galaxy S III Original Android Development] Satch09:
Sorry, my bad. I just stating what I saw
[Galaxy S III Original Android Development] Schmurtz1968:
So. well !

Because your settings looks like being differents than the default ones when flashing the kernel, may be can you give us your full settings ?:D

I must confess that 0-90 seems a wery strange setting for me. When GPU needs to speed up at 90% it never calms down (0%)...
[Galaxy S III Original Android Development] AndreiLux:
No you don't understand it correctly: At 90% it jumps to the next frequency and threshold pair, 55-95. Then below 55 it goes back to the previous step, 0-90. The 0 is there because there's no other step below it, same as there's none above 440, so 100% up on that bracket. Edit: I think you're all getting confused because of the 0 and 100, just interpret it as 90-55-95-68-95-64 then.
[Galaxy S III Original Android Development] EdgaBimbam:
i was also using only pegasusq till i have tried pegasuq. With system tuner you can check how many cores are working with concrete cpu frequency. From my testings, pegasusq at the begining uses 4 cores, later it uses first two cores. While lulzactiveq always is using four cores which gives better performance :)
[Galaxy S III Original Android Development] Schmurtz1968:
i'll be a little less stupid for a day with your explanation ! :laugh:
[Galaxy S III Original Android Development] maddler:
DISCLAIMER: I KNOW BENCHMARKS SUCKS BUT, PLEASE, READ THE WHOLE POST BEFORE KILLING ME. THX :cyclops:

I've just flashed 1.6.3 and tried running Antutu, CF Bench and Geekbench in order to check if OC and UV settings where fine. Geekbench and CF Bench actually show a result in line with what I expected but Antutu show a result which is about 50% less than what I expected.

Again, I don't really care about bechmarks, but my question is: could it be a symptom of something not working as expected?

Thx.
[Galaxy S III Original Android Development] kvv515kvv:
im i correct, if will state next

1. gpu undrvolting all steps (-100 for example, assumind that phone can handle thiss settings)

a. will save 0 energy when screen is off

b. will save x energy when screen is on

c. will save 2x energy when play video

d. will save 3x energy when play games with 3d graphyc

conclusion - gpu undervolting make sence if you want save some energy when you use 3d graphyc or watch video

2. cpu undervoltinng (-100 for example, assumind that phone can handle thiss settings)

a. will save x energy when screen is off

b. will save x energy when screen is on

c. will save 2x energy when cpu is heavy used

d. will save 3x energy when cpu is used at maximum

conclusion - cpu undervolting make sence if you want save energy, but performance goes down.
[Galaxy S III Original Android Development] Schmurtz1968:
Yes ! Too much undervolting CPU gives instability. -50mv is a good thing for stability.

With GPU if your settings are too much undervolted, then you may have frame drops. -25mv per frequence is correct.

@kvv515kvv

I do prefer thinking about undervolting not in terms of powersaving (that is a side effect, not a real fact) but in terms of cpu and gpu getting hot when under heavy use.

That is too say, that with a little less of juice CPU and GPU are getting a little less hot and last longer.
[Galaxy S III Original Android Development] cba1986:
I don't know the case for the GPU. But in the case of the CPU i undervolted -100 and oc to 1600. With no perfomance loss. It's more with less voltages you get less heat with limits the throttling.
[Galaxy S III Original Android Development] DashingGentleman:
Undervolting does not directly decrease performance at all. It's not slowing down the CPU/GPU, just decreasing the power overhead that the processor is running at. The only way UV degrades performance is if you overdo it and the processor starts making calculation errors due to the transistors inside not having enough voltage to switch reliably. If you push it even further, you get crashes and the system locks up. So if you undervolt carefully, you will get THE SAME performance as stock voltages but less power usage.

The power usage difference can actually be significant, because the power dissipated by a processor varies linearly with clock speed but quadratically with the voltage. The problem is that the CPU/GPU power usage is usually not your main power drain - when screen is on it's the display which is the big drainer and when the phone is idle the radios and any background processes are much more significant power suckers.
[Galaxy S III Original Android Development] MBurns2:
is there a way for change color value (gamma..)? i have cyano 10 with this kernel.ty
[Galaxy S III Original Android Development] ZACQ8:
Wow... it takes only one second now to connect wifi...from v1.6.2+

What magic did you do...

Thanks a lot
[Galaxy S III Original Android Development] Shidapu:
I can confirm that something is much better.

Im virtualizing a private wifi network with a wifi dongle, Every piece of wifi item in my household has no issues connecting, except my SGS3, now its working flawlessly. :)
[Galaxy S III Original Android Development] nfsmw_gr:
Updated wifi drivers did the trick. :)

And of course gokhanmoral's great work for updating them! :D

Exact quote from his site:

"v1.6 -> v1.6.1: reverted mtp driver to fix mtp problems on osx. removed some tweaks which were suspected to degrade performance. reniced kswapd0 to have lower priority. new wifi driver from n7105 sources."

@All

Guys i have a big issue...one hour ago my sTweaks showed unexpected error out of the blue and the app wouldn't open.

Anyway i deleted the app because i though it would be reinstalled after reboot...

But that didn't happen.

Tried flashing again,flashing another version but still...sTweaks is a no go..

Can anyone help me get this app back?

Thanks! :)
[Galaxy S III Original Android Development] cba1986:
Here you go:
[Galaxy S III Original Android Development] qwerty12:
I don't know if this works for the JB kernels, but if you delete /system/.siyah/stweaks-installed and reboot then /sbin/ext/install.sh should reinstall STweaks
[Galaxy S III Original Android Development] :
Hi,

@ nfsmw_gr

With a file explorer go to /res folder and you'll see Stweaks. Copy it to system/app, set the corect permissions like the other apps and reboot.

In case you lost again Stweaks, the app is in the /res folder.

:)
[Galaxy S III Original Android Development] MIKEMON:
Perfect work, wifi and super fast, thanks very much,

sounds too good, it's absolutely wonderful
[Galaxy S III Original Android Development] Esahin1992:
1.5.3 brêaks video recording funktion on miui
[Galaxy S III Original Android Development] flaviosp:
for some strange reason, siyah gives me a cracking sound when making phone calls, all other sounds are fine...

stock JB - rooted...

had to flash two times JB to solve the issue...and no siyah for me :(