yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] MohammadAG:
gokhanmoral, how do I compile the kernel? I got the toolchain all set up, but kernel/sched.c fails to compile.

kernel/sched.c: In function 'add_preempt_count':
kernel/sched.c:4377: error: implicit declaration of function '__add_preempt_count' [-Wimplicit-function-declaration]
kernel/sched.c: In function 'sub_preempt_count':
kernel/sched.c:4408: error: implicit declaration of function '__sub_preempt_count' [-Wimplicit-function-declaration]

Also:

sound/soc/codecs/wm8994_voodoo.c: In function 'update_recording_preset':
sound/soc/codecs/wm8994_voodoo.c:620: error: 'WM8994_IN1L_VU' undeclared (first use in this function)
sound/soc/codecs/wm8994_voodoo.c:620: error: (Each undeclared identifier is reported only once
sound/soc/codecs/wm8994_voodoo.c:620: error: for each function it appears in.)

Where are those defined? (this is latest pull from github).

Edit: Nevermind, could you please edit the README_Kernenl.txt to point to build_kernel.sh, with a link to ramfs_sgs3? Also, there's a line in build_kernel.sh that depends on your setup, the one that uses strip. You have it hardcoded to a path in /opt.
[Galaxy S III Original Android Development] faddys123:
To only 1600mhz on other kernels it's fine, but I want to use this kernel but my phone is like a radiator
[Galaxy S III Original Android Development] Haris1977:
Hello there:) Can i connect a usb2ethernet adapter to my SG3 with this kernel? Anyone tested it?
[Galaxy S III Original Android Development] fakpuppet:
That is a nominal frequency, meaning that it is the max clock that the CPU will be clocked at. That however doesn't say how the CPU will actually step up or down is clock. If you use an aggressive governor that keeps your CPU constantly at a high frequency then you will notice the heat. The same thing goes for voltages. Keep in mind that the dissipative power of the CPU scales with the square of both the voltage and clock meaning that if you up the voltage by say 10% the dissipative power will increase by 21% which you will feel as radiated heat. Same with frequency. So of the CPU isn't kept at a constantly high clock and/or voltage it will have the chance to efficiently cool down by scaling clock down and will on average be noticeably cooler.

So you sold probably check your CPU voltage and governor setup on Siyah.

Sent from my GT-I9300
[Galaxy S III Original Android Development] SpideRMaN-17:
I would like to ask 2 questions

Is it possible to wake phone by pressing audio buttons?

Is it possible to fix the slide2wake option in kernel ? It works maybe 1 in 20 tries on international S3 with omega rom v34 and jkay framework.

Thank you for your hard work developing this very good kernel
[Galaxy S III Original Android Development] LRC1710:
I have a problem, trying to restore a nandroid backup to 2nd rom, when flashing, it says MD5 mismatch! and wont fllash it... Im using Omega v34 as primary and trying to use my cm10 (YES ITS CM10 NOT 10.1) nandroid backup as my 2nd rom any idea on how to make it work?
[Galaxy S III Original Android Development] 4l3gU:
you can try putting the recovery 6.0.1.9. I tried it and after putting it the restore of the secondary has worked. Test and if you can confirm? First with the old recovery never worked restore. Sorry for my bad english:p

Edit: here http://xdaforums.com/showthread.php?p=35039672

INVIATO DA ? CON IL MIO S?
[Galaxy S III Original Android Development] GhiGo65:
same here, sometimes... But...

Thanks bro!

Normally i used cwm 5.5 because was the only that works always on secondary restore but tonight i use 6.0.1.9 and it works :D

Trollallero trollallá
[Galaxy S III Original Android Development] sachilleas:
+1

I have exactly the same questions.
[Galaxy S III Original Android Development] cinciopillo:
I'm on stock ROM and I'm experiencing many reboots, especially during phone calls.

Enyone else facing the same problem? Any workaround?
[Galaxy S III Original Android Development] scuba156:
Hey guys, I found this awesome thread, you should all check it out...

http://xdaforums.com/showthread.php?p=27389678
[Galaxy S III Original Android Development] yakie996:
hello, this is my favourite kernel! but when will it come available for omega rom??
[Galaxy S III Original Android Development] kerbiii:
It is already available

- SIII GT-I9300
[Galaxy S III Original Android Development] chudy_85:
hi all

i have problem witch this kernel on my 4.1.2 odex for poland

when i put to mtp and do to sdcard/android/data i dont see my file but when i use fone i see this file

can any body now how fix this

thx
[Galaxy S III Original Android Development] Schmurtz1968:
MTP refresh problem

Same case here,

It looks like MTP driver doesn't refresh correctly infos.

Have tried two PCs and same thing happens.
[Galaxy S III Original Android Development] AndroidGX:
Confirmed here aswell.

Strangely, it appears much more often about extsdcard, but sdcard is working perfectly 95% of the time for me.
[Galaxy S III Original Android Development] gokhanmoral:
I saw your pull request on github and thank you for that one, but I will wait before pulling it because I didn't test it by myself. for now, I recommend the users to use Chainfire's workaround.

and for README, I think it is not needed. If someone doesn't know how to download a toolchain and change cross compiler path he should not complain about not being to compile kernels but read a little more.

it is a very basic step and should be trivial to change paths of executable in both Makefile or build script.

by the way, samsung also keeps that /opt path to cross compiler in some of their tarballs. if you download android_prebuild, siyahkernel-sgs3 and ramdisk-sgs3 repositories from my github you should not need to change cross compiler path because it is already set to be used from parent dir in the build script. you can skip fixing strip binary location because that step is not mandatory.
[Galaxy S III Original Android Development] JDogg1329:
Also seen this, extremely annoying with TWRP backups and titanium backups I want to get off my phone straight away.
[Galaxy S III Original Android Development] koko115:
Hi after instal latest siyah 1.8.4 in battery stat i have only this after couple houers ?

How fix this ? I buy stweaks from playstore, but i dont see any tweaks for stat battery...

On stock kernel i dont have this problem.

Sgs3 omega 35 4.1.2 JB
[Galaxy S III Original Android Development] Onraad:
Clear batterystats in CWM
[Galaxy S III Original Android Development] faddys123:
What is the recommend or the best both for cooler and battery life?
[Galaxy S III Original Android Development] DonHuan:
Just updated STweaks in Google Play and it says "Sorry, no kernel support!".
[Galaxy S III Original Android Development] gokhanmoral:
it is not a kernel problem nor stweaks problem.

it is probably because of your broken superuser/supersu.
[Galaxy S III Original Android Development] DonHuan:
Sorry. The problem was in patched kernel (exynos mem-fix). In "stock" 1.8.4 it's OK.

Hope to see a fix for this vulnerability in the next release of your awesome kernel. Thanks.
[Galaxy S III Original Android Development] gpvecchi:
I can't wait for a CM 10.1 compatible version... I offer to be a beta tester...
[Galaxy S III Original Android Development] schif:
Me TOO ! :D
[Galaxy S III Original Android Development] Boopop:
Please help!

I updated my CM10 by downloading latest nightly build and then installing from zip, and then did the same to flash the Siyah kernel back on. Now CM10 doesn't boot, and I can't get into CWM (what's the key combo?). The Siyah logo shows up before it tries to boot, except with no text. What do?

Thanks!

EDIT: Turns out what I thought was a CM10 nightly was a CM10.1 nightly. Now I feel stupid! How do I go back to CM10?
[Galaxy S III Original Android Development] enigma1981:
Vol up, home and power for recovery, then just flash a cm10 nightly that is actually a cm10 file ;) that should fix you

Shouldn't need to wipe either as your data will be from cm10 not 10.1

Swyped from my Galaxy S3
[Galaxy S III Original Android Development] Tatsuya79:
I'm back at trying to figure out the mdnie system. :cyclops:

I don't understand that misc device stuff...

I go there, try to change some values in let's say "tune_standard_ui" but the file isn't changed. Double checked R/W setting...

And after a reboot all files are rewritten somehow by the kernel judging by their date...

Is there some kind of protection or am I supposed to do it another way?
[Galaxy S III Original Android Development] daniel_costa_rj:
I installed Wannalite LKC V5.1 and NIGHTLY ROM CM10, but the dual boot didn't work. Could be because am I install the Jkay with wannalite ?

Enviado de meu GT-I9300 usando o Tapatalk 2
[Galaxy S III Original Android Development] alchemist316:
Try installing on the main ROM and the other one that works for me
[Galaxy S III Original Android Development] omizzz:
+1 me too....
[Galaxy S III Original Android Development] rickoslyder:
The battery I'm getting on JellyBam 3.0.0 using Siyah 1.8.4 is pitiful. I literally can barely manage to get 10 hours, and that's with moderate usage.

I've linked a logcat and a BBS dumpfile of my battery drain overnight.

http://db.tt/FQFKNfgZ

http://db.tt/WTxu4ujM
[Galaxy S III Original Android Development] Dreamweaver:
Restore your backup you did before flashing CM10.1 ;)

No backup, no pity. :p
[Galaxy S III Original Android Development] gokhanmoral:
definitely not kernel related and definitely not in the scope of this thread.

I could see the reason as soon as I open the first file and I am sure someone will help you if you post it to the other thread...
[Galaxy S III Original Android Development] red.hat:
I agree with GK on this am using the kernel without a problem. You should disable ur wifi and then visit other thread like GK said. Will ltry and help out.

Link here http://xdaforums.com/showthread.php?t=
[Galaxy S III Original Android Development] Casper[DK]:
I had Omega 34 installed as primary and only ROM. Then I installed Siyah 1.8.4, rebooted into 2nd rom utils, formatted 2nd rom partition, wiped cache and dalvik and fixed permissions. Then I installed Paranoid Android 2.54 as 2nd rom and reinstalled Siyah 1.8.4 kernel.

When I boot into Paranoid Android I seem to lack the play store and if I try to install Titanium Backup or Astro File Manager from the web, they claim it is already on my device. I don't know what I'm doing wrong? I'd like to go to the playstore and install these apps, so I can restore my backup from my primary ROM, som I can get all my stuff back and give P.A. a try.

Please Help?!

Thanks a lot :)
[Galaxy S III Original Android Development] Lulavc:
Hi mate, you are on the wrong Thread. This one is for DEVELOPMENT ONLY.

Try this one.... http://xdaforums.com/showthread.php?p=27389678
[Galaxy S III Original Android Development] TheMasahiro:
What is moderate usage for you? U guys have to stop saying moderate usage or high usage, moderate usage for you could be high usage for me. in your case u have wifi turned on all the time. for me thats high usage since i disable mine all the time coz i done need it. And any battery problem isn't related to kernel or rarely is. At least with kernels developed by recognized developers. Search some battery threads, post your dump file they will help you. But like it was said, turn off your wifi and mobile data when u dont need it. Also you have apps with auto sync that will sync probably every hour preventing your phone from going to deep sleep. Search about it. Good luck
[Galaxy S III Original Android Development] Kevin.Silbstedt:
Ok, so this is my first bug report here and I'm a bit confused by this weird behavior. Before I explain further: I'm on Omega V35 and Siyah Kernel 1.8.4. I'm currently using the "evenmorebattery" profile and underclocked the first step of the gpu to 54 Mhz and undervolted it to 675 mv. I got no problem with this set up under normal conditions.

So Samsung released a Smart Dock for the Galaxys S3 and the Galaxy Note 2. This Smart Dock is "smart" enough, to switch off the screen on the device, when you connect a HDMI cabel and a mouse with it. So far, so good.

BUT, Samsung, as awesome and godlike as they are (warning: sarcasm), totally ****ed up project butter, when the S3 is in this mode. If I mirror the screen by not using a mouse, it is fluid as hell on both screens. If I use a mouse and let the screen on the S3 go off, it becomes project stutter on my external monitor.

Now, lets jump to the point, where Siyah Kernel comes into play. Without Siyah Kernel, the UI laggs a bit (kind of like ICS times), but it is usable and you can play games.

But with Siyah Kernel it laggs so much, that it gets annoying and gaming (like Asphalt 7) is out of the question.

Now my guess is the following:

If you switch off the screen, Siyah Kernel seems to force the GPU clock to the lowest step, which just makes sense, when you want to save battery. But since it seems to do this, when you use the phone with the smart dock (with mouse and HDMI out), it forces the phone to become a laggy mess. (And yes, I know, it's because my lowest step is especially low)

Now, setting the lowest GPU step to a higher clock helps to make it usable, but I can set it to only 266 Mhz max and also, switching this everytime, just because I want to use the damn Smart Dock, is just annoying.

Now, the weird part is: When you set the clock of the first step back to 54 Mhz, it is still "fluid" like with 266 Mhz. I don't know why, maybe it ignores the setting, maybe it learned to be able to at least scale up to 266 Mhz. I don't have a clue. This effect is gone after rebooting the phone.

Now, I know, I'm probably one of the few, who even have this Smart Dock and developers need to reproduce this problem.

So what can I do, to help fixing this behavior, so that the GPU scales with the Smart Dock like under normal conditions? Would a log actually help or would that be waste of time, like waiting for the exynos sources? (knock knock Samsung, it's the end of the year, where the **** are they?)

I appreciate your work and help.
[Galaxy S III Original Android Development] gokhanmoral:
v1.8.5 is up. I hope it boots on cm10 because I did not test that.

and "maybe" it will boot on cm10.1 but it is very unlikely

do not use dualbooting with cm10.1, it will definitely not work.
[Galaxy S III Original Android Development] ikons:
Quick test of 1.8.5 with slim bean 3.1 as first rom and omega 35 (Samsung LL5) as second rom. No boot of first AND second rom :confused:. With 1.8.4 everything is perfect.
[Galaxy S III Original Android Development] gokhanmoral:
EDIT: reuploaded
[Galaxy S III Original Android Development] fidorulz:
Tested 1.8.5 on JELLYBAM - v3.0.0 and wont boot
[Galaxy S III Original Android Development] gokhanmoral:
reuploaded and after testing with cm10 nightly.

sorry for the inconvenience.

please redownload if you are using cm10 or cm10 based rom.
[Galaxy S III Original Android Development] senses!:
1.8.5. Reboots with Fouxhound

Busco trabajo!
[Galaxy S III Original Android Development] fidorulz:
Tested new kernel and phone boots now
[Galaxy S III Original Android Development] Kaydin:
Experiencing some random reboots on 1.8.5 on WanamLite 5.2. What's going on? Is it because of the I/O scheduler? It hangs a bit, and then reboots. I had no problems on 1.8.4. 1.8.5 seems faster, though.
[Galaxy S III Original Android Development] darkbahamut:
I notice that with 1.8.5 that the kernel seems to spend time at 1.8GHz, despite STweaks being set to 1.5GHz. There are not other CPU control apps that have root that could be changing this, and the behavior worked fine in 1.8.4 just before I flashed.
[Galaxy S III Original Android Development] illuminato 67:
Siyah 1.85 reboot with Omega 35.

Inviato con il mio S3 ROM Omega 35
[Galaxy S III Original Android Development] EtienneBordeaux:
I am having reboots as well with Omega v35. I guess I'll revert back to 1.84 for the mean time.
[Galaxy S III Original Android Development] inscythe:
Reset your STweaks settings and restart? I don't have this problem.
[Galaxy S III Original Android Development] EnemyOfGlaDOS:
If you had left out the second comma it would've sounded slightly nicer :rolleyes:
[Galaxy S III Original Android Development] sharingan92:
I'm having no reboots at all on paranoid android over clocking to 1704 all is working perfectly

im what Willis was talking about
[Galaxy S III Original Android Development] danny19901:
Worked on CM10.1 but I overclocked to 1800mhz and 900mhz for screen responsiveness then after a while my phone rebooted and ended up in a boot loop so. I flashed cm kernel back and it's working fine again but when I flash siyah it just puts me boot loop I don't want to have to restore as I have way to many apps and stuff also was wondering is there anyway to fix this (siyah 1.8.5)
[Galaxy S III Original Android Development] MattBooth:
One Samsung ROM here on two different S3's... one running 1.8.5 perfectly, the other runs for a while and reboots into a bootloop. Sometimes it'd bootloop just after a fresh install, sometimes it'd wait an hour.

ROW IO perhaps to blame? I was stuck on a bootloop on one, flashed 1.8.4 and it broke the loop and booted as normal.

I'd get a logcat but my GF (her phone) was freaking lol. I thought it was my ROM but flashing an old version of siyah fixed it so perhaps it's that?
[Galaxy S III Original Android Development] Code124Y:
run 1.8.5 on temasek's unofficial build cm10.1, working well as normal, as OP said, no DB. The rest working well~

Sent from my GT-I9300
[Galaxy S III Original Android Development] nmeuret:
Bootloop on Wanam 5.2 with 1.8.5. Back to 1.8.4.
[Galaxy S III Original Android Development] Blackbirdxx9:
Runs perfect with omega v35 and AC!D 5.0

before i flashed the new kernel i set stweak to default. wipe cache and dalvik - all good :D

Gesendet mit meinem SGS3
[Galaxy S III Original Android Development] krzakzak:
with FH 1.6 don't work
[Galaxy S III Original Android Development] AndroidGX:
Bootloop confirmed here aswell.

Deleting .siyah folder before going to recovery +wipe cache + dalvik = booting perfectly and came to homescreen. Did my usual STweaks settings and after a manual reboot : stuck in bootloop :good:
[Galaxy S III Original Android Development] Hyena:
Bootloop with german vodafone ll5 after stweaks reset to default, cache, and dalvik wipe.
[Galaxy S III Original Android Development] 75markus:
everything is fine on CM 10.1 (Temasek V14) !

didn´t wipe anything or cleared any data :p
[Galaxy S III Original Android Development] mbalun:
exactly the same thing with me
[Galaxy S III Original Android Development] Schmurtz1968:
Cpu undervolt sensitiv

Il looks like the new kernel is very cpu-undervolt sensitiv too.

To avoid bootloops or suden reset it was needed to lesser cpu UV.
[Galaxy S III Original Android Development] gokhanmoral:
I think bootloops or random restarts are related with the power saving mode changes.

people reported that 1.8GHz step is being used.

I will check that part again tonight and release a fix for that.

that problem will happen on Samsung ROMs only because (if I am not wrong) that interface is not used on cm10/10.1
[Galaxy S III Original Android Development] darkbahamut:
I reset STweaks, uninstalled it, rebooted, re-installed STweaks, reset my settings, rebooted again and... no change.

The kernel still peaks at over the max CPU clock speed set in STweaks. What it seems to do is when the CPU loads is low and the load spikes, the CPU clock speed spikes up to 1.7-1.8GHz, then drops back to 1.5GHz and holds there while the load remains. When the load drops it scales back the clock speeds and this scenario repeats for the next load spike. So the kernel does seems to be listening to what STweaks has set, but there is some 'delay' in it locking to the desired frequency.

Never had this under 1.8.4 as even after 2 weeks uptime any speeds over 1.5GHz would remain unused, using the same STweaks settings.
[Galaxy S III Original Android Development] gokhanmoral:
I think testing will not be required. I could see the reason. I will reupload v1.8.5 once again.

please redownload
[Galaxy S III Original Android Development] 75markus:
Edit : broke the camera !

Just a green screen !

I guess the exploit mem fix ?!

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] inscythe:
I didn't notice the spike since I was just eyeballing the CPU speed in ROM Toolbox. I guess the spike is too fast to be captured by the refresh rate of ROM Toolbox. When I checked CPU Spy, it does seem to show that 1.8GHz has been reached for small period of time. Sorry for doubting you...
[Galaxy S III Original Android Development] PIRATA!:
Is actual v1.8.5 available now at this time the new one re-uploaded???

EDIT: your website http://www.gokhanmoral.com/ appears to be down...
[Galaxy S III Original Android Development] RedDevils88:
CPU

Hi, i have a question here, i am on siyah Kernel and used SetCPU to set a profile for one of the games. i clocked the CPU at 1400Mhz for both max and min settings. Set the governor to Performance.

Then i used PerfMon to monitor my CPU clock speed. However, it is constantly on 1000Mhz max and sometimes 1 or 2 cores will be offline.

Anyone can tell me why is this so?

Thanks
[Galaxy S III Original Android Development] inscythe:
You can go straight to Gokhan's dev-host if you have the link in your browser's history. I compared the 1.8.5 there with the one I'm currently using, it is different. I suppose he already updated it. The main site seems to be down from here too.

For a few minutes of using it, power-saving mode and 1.8GHz spike bug seem to have been fixed.

Thanks GM!
[Galaxy S III Original Android Development] OisteinR:
The latest 1.8.5 works perfect here!
[Galaxy S III Original Android Development] avary:
what about dualboot? espicially cm10.1 ?
[Galaxy S III Original Android Development] Vaedryn:
Read the Changelog, dosnt work at the moment.
[Galaxy S III Original Android Development] kerbiii:
im stuck in bootloop and i cant go either in my recovery because im using siyah kernel hijack recovery and flashing the 1.8.5 might remove that so i think i dont have recovery (i guess im f***ed), i have no access for the mean time on windows, i dont really like using odin pc, the only thing i can access is download mode
[Galaxy S III Original Android Development] slaphead20:
There is camera fix on exynos abuse thread....apologies no link to hand
[Galaxy S III Original Android Development] nmeuret:
You're right :

1st version MD5 : 8F7B709F8B2BE06AECEC586BD054ED08

Current version MD5 : 37FA2623CDFB6500B30DE2E3733C38F8

Something changed !!! Don't think it's a good practice to hide changes ...

BTW, new version works now with my Wanam 5.2 (bootloop on 1st version). Thanks !!!!
[Galaxy S III Original Android Development] Schmurtz1968:
Read this link to understand

Don't blame at gokhanmoral

Read this Link and you'll understand all, my friend ;)
[Galaxy S III Original Android Development] PIRATA!:
Well i downloaded from phone browser...don't have the link....

Can you point it here??
[Galaxy S III Original Android Development] Schmurtz1968:
Here is for you :

Link for CMW

And for Odin
[Galaxy S III Original Android Development] gokhanmoral:
the changes are not hidden. they are in my github.

only the version number is the same.

this is the second reupload for 1.8.5. first change was in the ramfs and it was a typo (in /init, "CM10" -> "CM101")

the second change was a little fix in /kernel/power/main.c to prevent spikes to 1800MHz, which was the reason of unexpected reboots
[Galaxy S III Original Android Development] illuminato 67:
The new 1.85 work like a charm!

Omega v35

Thank's Gokhan
[Galaxy S III Original Android Development] btje:
I think it is wise to change the version number. Because you changed something to a released into the public version. You could name it 1.8.4.1

This becasue after you put it up for download it will be downloaded and with the same name the public can't see the difference.

Further thanx for your tremendous work.