yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] alienmind:
Sorry to reopen the lag-debate but ... after a few ours the problem reappeared.

What I can see in a logcat is that a lot of frames are being skipped (I/Choreographer entries scattered all around)

Probably that's a consecuence and not the cause, but just wanted to post this here just in case.

Also, when the lag and freezes starts (after a few hours) the device starts enqueing lots of events, and you can clearly see the screen responding to your input several seconds later (scrolling up, down whatever you were doing)

I/System.out( 5079): start a thread http://xdaforums.com/customavatars/thumbs/avatar3755174_1.gif
W/ResourceType( 5079): Skipping entry 0x202021c in package table 0 because it is not complex!
W/ResourceType( 5079): Skipping entry 0x202021c in package table 0 because it is not complex!
D/dalvikvm( 2552): GC_EXPLICIT freed 2286K, 32% free 20229K/29635K, paused 26ms+12ms, total 187ms
I/Choreographer( 5079): Skipped 96 frames! The application may be doing too much work on its main thread.
D/dalvikvm( 5079): GC_CONCURRENT freed 4538K, 43% free 8828K/15299K, paused 70ms+38ms, total 273ms
W/SQLiteConnectionPool( 5079): A SQLiteConnection object for database '/data/data/com.quoord.tapatalkpro.activity/databases/tapatalknew.db' was leaked! Please fix your application to end transactions in progress properly and to close the database when it is no longer needed.
I/Choreographer( 5079): Skipped 60 frames! The application may be doing too much work on its main thread.
I/SERVICE ( 6332): **** android.intent.action.BATTERY_CHANGED
I/SERVICE ( 6332): *** RELAUNCH ***
W/BatteryWidget( 6332): Direct0
I/Choreographer( 5079): Skipped 51 frames! The application may be doing too much work on its main thread.

Please tell me if I can help with more information, and I'm willing to test whatever you need me to

Thanks!
[Galaxy S III Original Android Development] ties169:
Pls delete, posted in wrong thread...

Sent from my Galaxy S3 with Tapatalk
[Galaxy S III Original Android Development] b-eock:
^Dafuq you talking about?
[Galaxy S III Original Android Development] MuertoKo:
SystemUI.apk is not touched by kernel at any level. It's common to just check what are you flashing before doing it, so there you can easily see what is it doing.

Anyway, DEV thread so please keep this question for Q&A thread of this kernel as it's stated in OP.
[Galaxy S III Original Android Development] Geo1997:
No lags or problem with 1.6.3 and omega 27.1

Smooth, awesome

Thx :)

Good luck for dual boot :D
[Galaxy S III Original Android Development] Franc38:
Same here... 1.6.3 on Omega 27.1... Amazingly smoooth... not a glitch, not a lag, and battery seems more than decent. Probably the best combo on my SGS III so far!

Great job, Gokhan!
[Galaxy S III Original Android Development] ties169:
Oh ****, sorry sorry sorry... Posted in the wrong thread, wanted to post in temasek's cm10 build.

I'll blame yesterday night's beers... :o

Sent from my Galaxy S3 with Tapatalk

---------- Post added at 12:55 AM ---------- Previous post was at 12:51 AM ----------

Wrong thread

This is embarrassing... :banghead:

Sent from my Galaxy S3 with Tapatalk
[Galaxy S III Original Android Development] android.francis:
I heard that this kernel has an updated WiFi driver to solve the connection issue.

Can anyone provide a CWM flashable zip that can also be used in stock ROM?

Thanks!
[Galaxy S III Original Android Development] jeebspawnshop:
The driver is in the kernel, bro.

Either you flash the kernel, or you don't get the driver.

And FYI: this kernel works for stock ROMs, in case you hadn't read that in the OP.
[Galaxy S III Original Android Development] sohail77:
Don't know why but siyah just doesn't read my 32gb sd card........it only shows total space 11gb internal and 11gb external but there should be 29gb external...........

I tried 2 versions i.e 1.6.1 & 1.6.3 but the same result what should i do plzzzzz help me
[Galaxy S III Original Android Development] nfsmw_gr:
What the..?

I suppose you use an internal to external sd mod so check that thread and post your questions there.

It's not Siyah kernel's fault in any possible way.

And by the way,in a friendly tone not trying to offend you in any way...

If it's possible please write in proper english in this forum.

You could make everyone's life easier and make them understand you better this way because this is an international forum and most people speak proper english here. :)

http://xdaforums.com/showthread.php?t=1772234
[Galaxy S III Original Android Development] chudm:
guys i was having big problems with my cellphone (cm10 lastest nightly + siyah 1.6.3), phone hanged up, and it was slow... now i installed a nightly from a week ago, and its working much much better!
[Galaxy S III Original Android Development] bordikun:
no lags here phone running smoothly for the last 8 hours. will see how it goes after more hours.

edit: I'm running only at dual core mode.
[Galaxy S III Original Android Development] Tarek82:
@ gokhanmoral

Have a beer on me mate, 06A532630M559922T
[Galaxy S III Original Android Development] bufosp:
i don't know why but i prefer the sound quality from the stock insecure kernel rather on siyah kernel for JB. this is strange since the sound quality of the stock insecure on ICS is crappier and i really got eargasm on siyah ICS. especially in middle bass, it's kinda overpowered or something. had to reflash my rom. too bad tho, i kinda like other feature on siyah like USB charging n other
[Galaxy S III Original Android Development] gokhanmoral:
with the helps of droidphile, tumult, tolis626 and nfsmw_gr I managed to narrow down the problem to modules.

I am now removing one of them and moving the functionality to the kernel side, also adding 1700 and 1800 steps.

still too early to tell that it is fixed. but their device has not had a huge lag or crash yet.

but I am almost 100% sure that it will be fixed in the next release.

there were more than one reasons: 1- my fault in one of those modules, 2- I didn't know that the memory allocated from modules was not pageable so those vmscan and swap messages was related with mali.

I will use another method to support samsung and cm10 in the next version.

I will try to release a new kernel as soon as possible (when I have time today).
[Galaxy S III Original Android Development] sohail77:
Sorry mate my bad now i got it right ......

And does overclocking gpu reduces battery life
[Galaxy S III Original Android Development] EdgaBimbam:
ofc? because higher gpu clock stage, higher energy consumption?
[Galaxy S III Original Android Development] JohnCorleone:
I was on last nights CM10 and WiFi idle timeout was set at 15 minutes and has been since CM9. I have 2 questions...1) is CM10 still better having WiFi timeout instead of always on while sleeping? My S2 got much better battery when on WiFi while sleeping. And does increasing WiFi scan interval help with battery? My S2 was always at 15 and we always upped it to 180 (which is an option in advanced WiFi settings on CM10 now

Sent from my GT-I9300 using Xparent SkyBlue Tapatalk 2
[Galaxy S III Original Android Development] :
I always put Wifi to Always and never look back.. don't like the sleep policy.
[Galaxy S III Original Android Development] JohnCorleone:
Agreed. I know early CM10 builds had some wake lock issue so they advised not to but I figured that was fixed long ago. I can't see how WiFi timing out then phone sitting idle (especially in bad signal areas) can be better on battery. Thanks for response...back to my usual settings I go

Sent from my GT-I9300 using Xparent SkyBlue Tapatalk 2
[Galaxy S III Original Android Development] mattiadj:
I have problems with recharge.

If I switch off the phone and recharg it, if I want switch on it in have to pull out the battery.

It's a know bug?

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] kenzolo:
Press and hold Power Burton until the Red charging led turn off... Relase it and You can see the battery status... If You want turn on the phone press another time Power button

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] BUFUMAN:
little bit laggy at Contacts

Hi gokhanmoral,

i am using your kernel @ Omega rom since v26 its really good and fast, but i recognized one thing.

Its a bit laggy @ contacts when u scroll up and down. like FPS drops. With stock kernel is really smooth and fast.

stweaks are at deflault.

but anyway thank you for the great kernel and exFAT support!! :cowboy:
[Galaxy S III Original Android Development] gokhanmoral:
I am making some last minute tests on 1.6.4

I made both mali drivers compiled into the kernel, they are no longer modules.

and that will improve the performance a lot (not directly related with mali part but related with the memory allocated from that part which are unevictable when mali drivers are modules)

I am adding back all the features I removed during the lag-hunting process.

but the good part is that we had a natural selection. I guess the unnecessary traffic on the thread will be less than before :)
[Galaxy S III Original Android Development] MuertoKo:
Just before releasing I think I got a bug which I can't get logs for (or at least dn how, tell me how and I will pull them here).

Using stock deodexed DLIB on 1.6.3 kernel, no mods.

When I switch off my device and plug in the charger the green battery appears and starts charging, all ok. As soon as the green battery disappears my devices blocks.

By blocking I mean I can't push home button to show the battery as usual, and if I unplug the wire it rests on "red led light" for some minutes and I can't switch my device on. Only way to revive it is battery pull or long press power button to force reboot... Having this since RC1 btw! No problem with beta15, even they are so different kernels it may not matter at all I guess... No problem on other JB kernels.

Any other reporting? Just ask me what u want me to tell and I will!
[Galaxy S III Original Android Development] GabrielSousa:
is the cpu UV and gpu UV working ?
[Galaxy S III Original Android Development] sharingan92:
Seems to be working fine
[Galaxy S III Original Android Development] luke05dee:
Hi, may I ask if you have done what AndreiLux has done below with the new frequency steps as from what I can understand it looks interesting :)
[Galaxy S III Original Android Development] gokhanmoral:
I took the dividers from his repo but without knowing about this changelog :)

I guess I have to thank him for this change then. his repo was already checked out when I started moving some module functionality to kernel code.

but there is one change: I used 1700 as freq step. it is still 1704 (because it has to be a multiple of 8) but you will see 1700 instead of 1704.

and I added that step to stweaks. I would have to make the selection a spinner if it was 1704 but now it can stay as seekbar.
[Galaxy S III Original Android Development] Rob2222:
Hello,

a shot in the dark and maybe some infos to reproduce the lags...

I have big problems as soon I activate the preload "watch later" videos feature on the actual youtube app settings. Then attach a charger and open the youtube app and go to you "watch later" section.

The S3 becomes very slow (I wait for each screen update / touch entry 10-30 seconds then) and in Watchdog taskmanager I then get higher load on "mmcqd" and "kswapd". Currently using 1.6.3.

I do not want to say it is caused by siyah, but maybe you can use this to reproduce the problem.

Phone was back to normal as soon as I managed to disable WLAN/Wifi.

Using stock XXLIB, no uv/oc.

EDIT: Problem is gone with siyah 1.6.4.

BR

Rob
[Galaxy S III Original Android Development] gokhanmoral:
it is fixed in v1.6.4
[Galaxy S III Original Android Development] GabrielSousa:
@gokhanmoral

what are the files to change ? for UV ? thanks
[Galaxy S III Original Android Development] nicregi:
Seriously glad to hear that!
[Galaxy S III Original Android Development] BUFUMAN:
This sounds good dude! And thank you very much for fast response.

UV works good here i am @ -50mv @ CPU
[Galaxy S III Original Android Development] gokhanmoral:
v1.6.4 is up.

new steps. all features are back (gestures, discrete wakelock stats, and some more that I reverted but cannot remember now)

both mali drivers are linked in. that is why you will have some more device files in /sys/module/mali/parameters

the ones having "new_" prefix is for cm10 and new mali driver.

and lockup problem while charging the device in off mode is fixed.

I tried to check almost everything but might have missed some tiny details.

waiting for the bug reports :)
[Galaxy S III Original Android Development] bordikun:
1.6.4 is UP! weeeeee
[Galaxy S III Original Android Development] Meraklis56:
my s-tweaks can go up to 1700 mhz.I also i am trying to use the camera gesture.(the one with the 3 fingers up to the screen and sliding them down to the bottom) but it doesnt work.

Stock rom.
[Galaxy S III Original Android Development] Schmurtz1968:
Many thanks for you're hard work !

1.6.4 Flashed via Mobile Odin.

Will report if lags and stutter have gone.
[Galaxy S III Original Android Development] luen76:
Hi gokhan, has swap been disabled in 1.6.4?
[Galaxy S III Original Android Development] Schmurtz1968:
Many thanks for your hard work !

1.6.4 Flashed via Mobile Odin.:highfive:

Will report if lags and stutter have gone. :good:
[Galaxy S III Original Android Development] gokhanmoral:
1800 is not stable on all devices. even I had some doubts about 1700.. so if you want 1800 you will have to do it with scripts or setcpu/nofrills/voltagecontrol or anything else.

I don't want to help you to crash your device.

for gestures: you have to flash the gesture script to have that.

I did not put that one as default.

but not a bad idea to put an example script in the next version.
[Galaxy S III Original Android Development] gokhanmoral:
hmm, unfortunately yes. I forgot to enable it.
[Galaxy S III Original Android Development] bordikun:
confirmed also here. swap is gone.
[Galaxy S III Original Android Development] GabrielSousa:
can some one please tell me the files for UV ?

thanks
[Galaxy S III Original Android Development] gokhanmoral:
the method used in this kernel is a little different.

I wanted to make it modular (a module) which can also be used in the leaked kernels.

you can check cpu_undervolting.c and mali_control.c

there are very little error checking on those files. if you have kernel panic while porting them do not blame me.

you may need to debug a little to get them working.
[Galaxy S III Original Android Development] gaetanolip:
will you implement swap support,autobrightness settings and 857 ram in next release?

thanks
[Galaxy S III Original Android Development] gokhanmoral:
swap support, yes.

autobrightness settings, no. because that part is not as primitive as in s2 and already good enough. there were flaws in my previous implementation and that is why I removed it. I think the autobrightness is good as default.

for 857MB, maybe. I want to test it on cm10 first because last time I changed those values people on CM9/10 ROMs complained a lot and I had to release another version with old values.
[Galaxy S III Original Android Development] fastcx:
I know I might sound against your plan, but will it be easy to disable swap in next release?

EDIT: nvm, I guess the swap support you meant was actual swap instead of zram? :) Then that, I have nothing to oppose. Sorry
[Galaxy S III Original Android Development] Infy_AsiX:
About auto brightness. If there were flaws in your old implementation I sure didn't notice them! The stock jb auto system can't hit zero brightness in low ambience. I miss your implementation, flawed or not.

Sent from my GT-I9300 using Xparent Cyan Tapatalk 2
[Galaxy S III Original Android Development] aegeuss:
Gökhan,

Thanks for the new version; I also vote for swap support.

Regards.
[Galaxy S III Original Android Development] RazielSasy:
I'm testing it for few minutes and it seems to hold up well with heavy use (before with the previous build I already had the now famous lag). So congratulations for the excellent work.

Maybe a stupid question but in the light of what has happened in the last few days which governor do you suggest? (I do not care to have 10 days without charge but a powerful governor that do not waste battery) Thanks
[Galaxy S III Original Android Development] carlos67:
Could the kernel not detect if CM10 is the installed Rom and.....

a. If it is then do not use higher memory values

b. If not then use higher memory values.

Simples:p

Please don't penalise non-cm10 users just because cm10 can't use the higher memory values.

Thanks and great work btw. Love your kernel - zero lags here not just on this version but previous ones also.
[Galaxy S III Original Android Development] nicregi:
First impression. Goods good. Let's see if this stays and good job in this.
[Galaxy S III Original Android Development] gokhanmoral:
I wish it would be as easy as writing that :)

I cannot make that detection when those memories are allocated.
[Galaxy S III Original Android Development] Arkanius:
Loving 1.6.4 so far

The difference in smoothness in UI operations is noticeable.

I believe you when you say the huge lockups and lags are fixed.
[Galaxy S III Original Android Development] wl3gan:
How about zram?
[Galaxy S III Original Android Development] DakiX:
1.6.4: all smooth/fast as usual (drawer+scrolling) but homescreen lags a little by switching.
[Galaxy S III Original Android Development] Infy_AsiX:
Got two phones here. One can only get proper core disabling on hotplug.

The other can't get any cores disabled except during screen off. But it can use two core mode, number one and four in 6.3 but not in 6.4.

Phones are almost identical in use. It's my girlfriends that I've tweaked out for her.

Edit: got the gf's to work the same where hotplug disables cores properly. Just had to reset to default in stweaks then put settings back on.

Sent from my GT-I9300 using Xparent Cyan Tapatalk 2
[Galaxy S III Original Android Development] AndroidGX:
1.6.4 + Samsung rom

:

No more overall UI lags, and big random lags/stutters in GTA3 game are gone for me, everything is back to normal, like ICS.

In my wish list, to make this kernel perfect as ICS, I would only need 2 features :

Full compatibility with CWM app (for features in it).

100 Mhz CPU step.

Many thanks for your work gokhan :good:
[Galaxy S III Original Android Development] jeebspawnshop:
You don't need the 100 mHz step, as it would use the exact same voltage as the 200 mHz.

Also, including an additional step would make the CPU take longer to reach idle mode and turn off (because of having to take an additional step down), so if you really looked at it closely, you'd be wasting battery instead of saving it.

:cowboy:
[Galaxy S III Original Android Development] mattiadj:
Swap support is not present in latest 1.6.4??

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] bordikun:
nope, he forgot to enable it.

don't worry next release will have swap support for sure.
[Galaxy S III Original Android Development] AndroidGX:
I understand your point of view, as you are not totally wrong.

But I remember had a bit more battery saving in idle using 100Mhz step instead of 200 one in ICS kernel. At least giving this choice possible to users will still be interesting for those who still want to experiment it ;)
[Galaxy S III Original Android Development] baileyjr:
Basemark ES 2.0 Taiji gives massive screen tearing in at 1.6/700 when using 1.6.4 at the stock voltages.

1.63 was flawless at 1.6/700 on stock voltages. i9300 running DL18.

Also temps seem higher in general.. I've dropped back to 1.63
[Galaxy S III Original Android Development] mattiadj:
Please add it back it's the most important thing for me. Thanks!

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] DakiX:
Okay no more lags :D i've changed one things in STweaks and its smooth like butter :good:
[Galaxy S III Original Android Development] RazielSasy:
really impressive, with this new kernel I managed to undervolt up to -100 with an overclock to 1.5GHz. Before my hand up Undervolt was -50 (default frequency) from -75 onwards I have freeze using benchmarks, but now all is very stable
[Galaxy S III Original Android Development] EViollet:
I also agree.

Voltages aren't everything. The CPU uses less current at 100Mhz than at 200Mhz.

But it's a non matter. The phone spends more time in deep sleep than anything else, and deep sleep is much better than anything.

So, adding 100Mhz will maybe help ooze out 1mA/hour. But I don't think you'll get anything more.

I tried Abyss kernel that has 100, 75 and 50Mhz steps (or something like that), and I didn't see much of a battery usage difference. Maybe 1mA/hour, but it isn't really outstanding.

Regards,
[Galaxy S III Original Android Development] GabrielSousa:
the gpu undervolting isnt working :(
[Galaxy S III Original Android Development] GabrielSousa:
cpu UV, isnt working to...

you can test put 600mv in all freqs, and the phone wont boot
[Galaxy S III Original Android Development] DakiX:
after all it works by me (not UV hardcore) ^^
[Galaxy S III Original Android Development] baileyjr:
I suspect the GPU voltage settings are not being applied full stop.

This would explain why I cant run the 700mhz gpu setting anymore, because I require 1100mv to get it to run which it does by default in 1.6.3 but in 1.64 it runs at 1075mv. I do not believe that any change in the GPU voluage settings in STweaks is actually being implemented in 1.64
[Galaxy S III Original Android Development] danielsf:
I think the gpu voltage regulators haven't been adjusted, as I can still change voltage and the voltage is been used as long as it is between 875-1075mV. :)
[Galaxy S III Original Android Development] extralife:
Do you think, it has to be gm's job to make adaption on cwmmanager app?

I don't.

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] gokhanmoral:
oops :)

now it is a good reason to publish 1.6.5...

you are right. I forgot to adjust them.

compiling right now ...
[Galaxy S III Original Android Development] mattiadj:
Don't forget swap please!!! I don't mean zram but swap support please mate :)

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] BUFUMAN:
why do u need swap?
[Galaxy S III Original Android Development] mattiadj:
To have more apps running together mate. It's essential

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] Cyb3rGlitch:
LED fading is still not working on Samsung JB.
[Galaxy S III Original Android Development] gokhanmoral:
v1.6.5 is up.

swap is enabled.

fixed touch boost cpu level setting.

re-adjusted gpu and cpu regulator voltage constraints (600-1400 and 600-1500 respectively)
[Galaxy S III Original Android Development] GabrielSousa:
cpu and gpu UV is working ?
[Galaxy S III Original Android Development] mattiadj:
Thanks mate!

Inviato dal mio GT-I9300 con Tapatalk 2