yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] xpandnz:
Any update on voice functions (s voice & Google now) working? This kernel rocks bug that's the only thing I find is not working. I'm using with stock rom.
[Galaxy S III Original Android Development] buge boyo:
I am using it with stock Rom s voice and Google now working perfectly.
[Galaxy S III Original Android Development] cooldoc007:
me too had similar prob.. problem solved by uninstalling kies and installing this http://xdaforums.com/showthread.php?t=1703488

never had dat problem again.. could be some drivers not being installed properly:)
[Galaxy S III Original Android Development] unholygid:
V1.8 is working awesomely well on both stock odexed j1 and 4.1.2.

Im getting 5.9k score on quad with no OC. Presq + sio -75mv under volt.

Ran stablity test for 30mins no problems at all!
[Galaxy S III Original Android Development] GR0S:
Gokhan, can you merge some patches http://pf.natalenko.name/ from this linux fork.

I'm using it on desktop, and system MUCH more responsible, apps starting mostly instantly.

Benchmarks reporting ~20% performance boost in comparetion with stock 3.6 kernel.

I've tried depatching samsung sources to 3.0 than patching to 3.6 with PF, but samsung removed a lot of needed files, so patches dont work.

You probably have more experience with those messed sources, so you should try.
[Galaxy S III Original Android Development] siliconaddict:
Thanks!

Omega ROM & your kernel are a perfect match :good:. Thank you very much! 8YJ0006905604333K
[Galaxy S III Original Android Development] PIRATA!:
Where can I find a list of the different governors and schedulers so to understand their differences from each other??

Thank you.
[Galaxy S III Original Android Development] Yank555:
Why not ask google ?

http://www.google.lu/search?hl=en&t...0.175.2831.2j20.22.0...0.0...1c.1.Cg9FEbXaCC8

JP.

Sent from my custom Paranoid Android 2.54 / Yank555.lu CM10 kernel v1.2a Aroma (Linux 3.0.53) powered Galaxy S3 i9300 using Tapatalk 2
[Galaxy S III Original Android Development] li0rli0r:
Hello,

I noticed that in Karnel S3 can not run saving device battery, when I run this option still device reaches a speed of 1.4GHZ

Is it possible battery saving work in S3?

It should limit the processor to work up to 1GHZ It also saves more battery do not need the device to work as quickly ...
[Galaxy S III Original Android Development] ov2rey:
how to get my sd card work? 64gb

using latest version 1.8
[Galaxy S III Original Android Development] jeebspawnshop:
Wrong thread.

Go here, then ask your questions:

http://xdaforums.com/showthread.php?p=27389678
[Galaxy S III Original Android Development] Lither:
I've flashed Siyah kernel via Recovery, which profile should I apply? I only use my S3 for Facebook, Viber, Internet and Games (But don't play that much)
[Galaxy S III Original Android Development] NeoBlade:
Sorry for jumping in again and nagging about the same issue... On previous kernels MTP/PTP worked fine under Mac OSX (Mountain Lion) but on the latest Siyah 1.8 Kernel it has stopped working again. Its not a massive deal breaker as I've gotten used of using AirDroid to overcome this issue however for faster transfers of large ROMs etc it would be useful.

It works perfectly fine under Windows 7 and 8 btw. Thank you for your time.
[Galaxy S III Original Android Development] jnr21:
Wrong thread....again
[Galaxy S III Original Android Development] NeoBlade:
Gokhan has been pretty humble and good at fixing the MTP/PTP issue for Mac OSX users in the past, of which we are grateful for. Feel free to check his previous changelogs to see the patches he added to make it work throughout the lifespan of his kernel. It is a dev issue as its not a "General Setup/Configuration" issue since we, as the end user, cannot configure the kernel itself to make it work. If we can then feel free to point me to the source so it can be compiled. As ever I can provide logs etc at the developers request if it helps.

I understand the frustration towards many posts here which are very General Setup/Configuration based but unless you can prove that it is user error or a mis-configuration at the user end then it is a valid question to ask. I have asked politely and mean no offense or harm to anyone here on this thread.

Again, thanks for you time.
[Galaxy S III Original Android Development] merbiyatch:
im running android revolution rom lk4 with siyah 1.8. just tried out this kernel. it fixed my video recording problem now i want to fiddle around with the setting for s tweaks but dont know half of what ill be doing. so im here seeking advice. i dont want to undervolt but i do what good batt life. smooth stable no lag s3. what would my setting be in s tweaks if i want to acheive this kind of outcoe on my phone? thanks in advance.
[Galaxy S III Original Android Development] jnr21:
You are right, read your post too quickly, sorry for that :) I deleted your quote on my previous post.
[Galaxy S III Original Android Development] orangerot.:
And again wrong thread.. for general questions go to the discussion thread... and if you would go and read the faqs on the first page of the thread you wouldn't have any questions about stweaks as all the settings are explained there + you'll find some packages containing different tweaks (battery save, performance.....) you can flash depending to your needs. So just go ahead to the faqs which should contain everything you need and if that's not enough please ask in the DISCUSSION THREAD again.
[Galaxy S III Original Android Development] _polimorph_:
Thank you for your time.

I read the article and it's a challenging job to deal with permissions under windows. However I must fix this issue so I started to learn how to keep the permissions. I didn't found any /etc/passwd nor /etc/group files in the boot.img so I need to run the "mkpasswd" and "mkgroup" commands? Any further details on how to preserve permissions while unpacking/packing boot.img under cygwin are highly apreciated.
[Galaxy S III Original Android Development] NZDroidDev:
Hi,

My suggestion would be to download a copy of a live Linux distribution, burn it to disk and use that to work with android files, that way you'll have no issues with permissions, you don't have to worry about installing Linux, as it runs straight from the disk, and is able to access all the files on your windows partitions. Something like kubuntu or mint are pretty good live distros.

I worked with cygwin for a few years while studying, and ending up using a live Linux distro instead as cygwin makes everything infinitely more long winded.
[Galaxy S III Original Android Development] NeoBlade:
Thanks for your understanding and don't sweat it ^_^ I too get annoyed when the same question gets asked over and over again in this thread, which is why I rarely post here anymore unless its something that I cannot fix or test myself.

You can also run Linux off a USB stick, which would be faster and as an added bonus it can also be setup to be persistant aka your preferences, settings etc all gets saved to USB too. Try using the YUMI USB tool (freeware) to add one or multiple ISO's to a USB stick to boot from. Good luck!
[Galaxy S III Original Android Development] Notronic:
Hey,

I´ve a little question about the dualboot function at this great Kernel :)

Is it possible to flash an original Firmware with Odin or Mobile Odin as 2nd ROM :confused:
[Galaxy S III Original Android Development] Erahgon:
Please use the discussion thread henceforth for questions and discussions not related to development.

The simple answer is: no, you can not use Odin, nor mobile Odin to flash a second ROM.

What you could do is:

Clone 1st ROM to 2nd using Siyah's CWM from sTweaks,

Use Odin or mobile Odin to flash a ROM,

Use Odin or mobile Odin to flash the Siyah kernel again.

If required, you could now swap the 1st and 2nd ROMs using Siyah's CWM from sTweaks.

I haven't personally tried this method, so I'd recommend having backups (a good policy in any case)!
[Galaxy S III Original Android Development] anpho:
I have a problem i narrowed down to the kernel. I am using omega rom 33.3 and using this kernel. when i plug it on the pc using windows 8 it mounts ok and sees the phone with the internal storage and the sd card. But when I try to copy files to the sdcard after 4-5 minutes it just hangs up. the procedure hangs and i don't have access to the sdcard or the internal storage through the pc. I have to unplug the usb and plug it again to be able to have access to the phone again. And again after 4-5 minutes it hangs...

I said I narrowed it down to the kernel because the issue doesn't occur when i use the stock kernel. It works fine and the problem only occurs when i use siya's kernel. tried it with both 1.7rc3 and 1.8.

Any help would be great because I really like the kernel, especially for the dual boot functionality.
[Galaxy S III Original Android Development] staticN0de:
You have the same rom and kernel I use. I copy large files to my device often using windows 8 and do not get lockups.

Have you tried different usb ports or another cable? Does it hang when you copy to both the internal and sd card storage or just one of them?
[Galaxy S III Original Android Development] Agaranda:
Some older people need to boost bass more in one channel. Would be possible in a future version of Siyah to have separate channel eq?

Thanks in advance

I9300XXELK4+Siyah1.7
[Galaxy S III Original Android Development] anpho:
it hangs when i copy to both the internal and the sd card. It stills shows them in file explorer but the procedure is hanged and I cannot access them. I tried different usb ports but not another cable. If It was a cable problem thoough, wouldn't the problem occur with both kernels? Instead when I use stock kernel everything is fine. When I use siyah the problem occurs.
[Galaxy S III Original Android Development] Tungstwenty:
You don't have /etc/passwd or /etc/group on the boot.img file (android kernel) but rather on your Cygwin installation.

You'd need to run "mkpasswd > /etc/passwd" from Cygwin to generate a passwd file that reflects your actual user accounts in Windows, and the same for the groups.

Anyway, I highly recommend you do use a proper Linux environment for stuff like this. I also worked with Cygwin for many things in the past (and sometimes still do) but it's worth a small step creating a secondary Linux environment for android-related stuff of this nature.

My approach was installing a VirtualBox or VMWare virtual machine with Ubuntu, as it will also allow building the Android stuff (the full distribution, only the kernel, etc.) should you need it at some point.

You just need to create the machine with the specs you want, boot from the virtual dvd pointing to the downloaded iso, and set it up once. Then you can create a shared folder between the host and the virtual machine and from there use linux easily for whatever you need.
[Galaxy S III Original Android Development] msurg:
Another variant of this problem. With version 1.8, I cannot see the content of external sd card on my PC. I am on stock JB with CWM recovery. When I plug to USB I can see GT-I9300 in my computer folder. Double click on it. Can see Card and Phone, too. But no content on Card.

I tried version 1.6.8 and could access to content without problem.
[Galaxy S III Original Android Development] xpandnz:
I did have trouble with S-Voice and Google Now voice search, or any app other than the phone that would use the mic. However, a couple of times this has worked fine but it has now stopped working again. I remember reading that this was a known issue that is still being worked on. Is this correct?
[Galaxy S III Original Android Development] deom2i:
2nd Rom problem

Please help, Recovery status states that 2nd ROM can not be found!!

I have followed this below steps to install AOSP Omega ROM:

1) Present sammy, setup aosp as secondary:-

i) Hit "Run 2nd Rom Utils" in Stweaks app from your current rom. This will run the embedded recovery in the kernel. Under dual boot options, wipe 2nd Rom data and cache+dalvik. Format 2nd Rom System.

ii) Using install zip to 2nd rom option, flash aosp rom as 2nd rom.

iii) Fix 2nd Rom permissions

iv) Flash Siyah again

I have fix permission by Hit "Run 2nd Rom Utils" in Stweaks app after installing AOSP and also fix permission then reboot.

I still get blank screen!! where im i going wrong? :eek:
[Galaxy S III Original Android Development] DarrenCarnall:
Yeah I've got this too since flashing this but it's the weirdest thing I can't figure out why sometimes it works and sometimes it doesn't.
[Galaxy S III Original Android Development] gokhanmoral:
It is a known problem and you need to enable either boot sound or lockscreen sound as a workaround. if any kind of sound plays before you start using the mic that doesn't happen.

It also happened with some old cm10 kernels that I tried (I don't know if the new ones still have that problem) and I still don't know the reason why it happens.
[Galaxy S III Original Android Development] _polimorph_:
It's a pain to work in Live Linux environment since I constantly get "permission denied" when doing split_boot.pl. I did "chmod a+x split_bootimg.pl" with no luck. I'm now creating an Ubuntu VirtualBox to see if there's any difference from the live usb and I belive it will be.
[Galaxy S III Original Android Development] xpandnz:
Where abouts do I enable these options? I'm just using stock rom with your kernel.
[Galaxy S III Original Android Development] Codekrypt:
Hi GM,had a random reboot today while uninstalling an application so posting this:

ROM: PA v2.54

Kernel:Siyah v1.8

Has happened before too while uninstalling an application.

Please have a look.

Thanks alot.

Edit:Wrong file. Will try uploading one soon.
[Galaxy S III Original Android Development] gokhanmoral:
I'm sorry but there is no info in the logfile if the reboot is related with the kernel or not.
[Galaxy S III Original Android Development] Codekrypt:
No problem. Thought it was. Thanks anyways sir.

Sent from my GT-I9300

---------- Post added at 05:10 PM ---------- Previous post was at 05:06 PM ----------

Nvm. Attached the wrong one. Will try to get it again.

Sent from my GT-I9300
[Galaxy S III Original Android Development] gokhanmoral:
I am uploading v1.8.1 to testing directory ( http://d-h.st/users/siyah/testing ) because I have not tested the last minute changes.

it will probably be moved to s3 directory tonight unchanged unless somebody reports a bug meanwhile.

increase FB earlysuspend in screen tab to fix CRT animation issue. I think 200ms would be enough but test it yourself.

You will have new CPU_UV tab in STweaks (thanks to Andrei for the scripts and descriptions). It will override the other UV-all-steps settings. I did not remove the old one because some users may prefer to use it for the simplicity.

I have also removed some eq bass modifications in this version. sound may be better or worse. please make comments in the other thread.

EDIT: file removed. will be released tonight.
[Galaxy S III Original Android Development] The Broken:
Nothing there.. :s
[Galaxy S III Original Android Development] gokhanmoral:
I fixed the gpu voltage bug and uploading 1.8.2...

it was setting the gpu voltage too low values (1000 times lower than expected because I forgot to append 000) and that was causing crash.
[Galaxy S III Original Android Development] dantheman122:
Just to check, the values I posted 900, 950 etc were all 900000, 950000, maybe my post wasn't as clear as I thought? Or was it something different? I found that I got a bootloop when I set the values to defaults so maybe the 1000 times lower was why?
[Galaxy S III Original Android Development] connta:
im not really sure should i report a bug here but when i installed 1.8.1 version all my GPU voltages were set to 1200 mV by default on all frequencies.

this is kinda major since it could potentially destroy hardware if someone doesnt recheck the settings after installing.

EDIT: forgot to refresh, sorry.
[Galaxy S III Original Android Development] gokhanmoral:
I will release 1.8.2 tonight after making sure that gpu values are set correctly.

there are limits anyway but the lower limit is just too low and causes crash and I made a mistake in gpu script...

it is hard for me to fix it without seeing the output and values... so, please wait several hours...
[Galaxy S III Original Android Development] dantheman122:
No worries at all, just wanted to make sure I didn't report anything wrong so you weren't trying to fix something that wasn't broken haha. Look forward to the newer version :)
[Galaxy S III Original Android Development] gokhanmoral:
if you check the values you will see that gpu voltages are not set to 1200...

and I will be glad if you can send me a link that 1200mV will destroy the device, because it will not even if all the voltages are set to that value.

please write something if you have an idea about it.
[Galaxy S III Original Android Development] AndroidGX:
I had the chance to test 1.8.1, and I tested your old CPU UV interface with -100mV for all steps directly, then after a reboot, checked uv values in the new Andreilux table STweaks tab, and all steps was still at default (900mV instead of 800 for 200Mhz step for example), is this normal ?

Anyway just to be safe, after seeing your message about removing 1.8.1, I reverted back to 1.8.

I had the time to test also the "less bass" feature, and I saw no difference at all, but I will speak more about this in the appropriate thread :good:
[Galaxy S III Original Android Development] connta:
whoa, no need to be hostile.

you made the mistake not me and its really easy to put up bold red leathers saying everything you do has a risk and then claim there can be absolutely no ill effect from overvolting to maximum value.

also when i reverted back to 1.8 version and looked at my gpu voltages they were set at 1200 mV again, dont really have anything to check if the gpu voltages are really set at that value but i guess il take your word for it.

good day, sir.
[Galaxy S III Original Android Development] gokhanmoral:
they are completely independent..

I didn't make that tab to show the effective value because the customized values would be lost if you were using setcpu or any other cpu uv app.

I am thinking about adding a textbox control to stweaks. then I can add a textbox for each step to show the effective voltage level.

if you UV with the old setting it will be applied as the first UV value during boot, then if you have "set on boot" checked in the new tab those will override the previous values.

and for now, there is no way to see effective voltages in STweaks.
[Galaxy S III Original Android Development] JDogg1329:
So we're mine, stock values are shown I just dragged the sliders to where they should be and pressed apply. Phone isn't fried. And this is the risk of flashing test versions of anything and especially kernels, it's all good, no harm done.
[Galaxy S III Original Android Development] gokhanmoral:
if you are on 1.8.1 they will not be applied and if you change them you will have crash because of too low voltages.

if you revert back to 1.8 reset stweaks profiles to get back to defaults.

and for that warning in red letters, there is no need to say that... everybody should know that flashing a kernel is risky. I sometimes make such mistakes and I do not hide them. but this one is not a dangerous one. it was not being hostile but it was a warning to prevent your message to cause panic on others just because you thought 1200mV is too high that could burn your device.

good day to you too...
[Galaxy S III Original Android Development] Satch09:
have some respect!! You noob!!
[Galaxy S III Original Android Development] connta:
thank you for escalating this to a name calling discussion, that is just tops!

no harm was done, no panic was intended on my part tho now i see how it could be interpreted as such. im quite aware that 1200 mV wont fry my phone instantly but it is on a high side and thats how i reported it. on the end it was actually a non issue since 1200 mV was never actually aplied.

call me an ungrateful bastard, i might have hinted that voltages and clocks are things that should be double checked on every step of development, betas, finals and all in between. cant really say thats not valid. never came here with a "OMG YOU ALMOST FRIED MY PHONE, NOOB!" and never will.

also that comment does not diminish the respect i have for the author and his work which is amazing.
[Galaxy S III Original Android Development] gokhanmoral:
v1.8.2 is up

gpu voltage initialization part is fixed.

nothing else is changed. only fixes in uci.sh interface
[Galaxy S III Original Android Development] AndroidGX:
Fast and nice work, as always :good:

I see that sched_mc setting is back, which is a good thing.

Stock GPU voltages bar looks wrong by default (not the real default from stock ones, as displayed in STweaks infos) but it is not very important anyway.

By the way, where is the line value in default.profile of "earlysuspend delay" please ? can't find it :(

Many thanks :good:
[Galaxy S III Original Android Development] westernmg:
Just flashed 1.8.2, but for me STweaks is forceclosing on todays CM10 build.
[Galaxy S III Original Android Development] gokhanmoral:
damn :) you are right. I forgot to put that to default.profile which means it will not be saved.

and that means I will release 1.8.3 now :)

and for stock values, I will remove them because the defaults are not set when I generate the xml.
[Galaxy S III Original Android Development] westernmg:
1.8.3 is working fine, thank you.
[Galaxy S III Original Android Development] Quipper2008:
@gokhanmoral

My favorite kernel love it :good:

Just one question. Why dont you use the latest kernel version from kernel.org ? (e.g. 3.0.54 or 3.6.9)
[Galaxy S III Original Android Development] gokhanmoral:
not all changes in kernel.org/linux-3.0.y branch are related to our device.

staying on 3.0.31 makes it easier to compare with samsung kernels as there is no changelog in Samsung's releases.

if anyone can suggest me a patch from higher 3.0.y versions I can commit that, but I don't know any really useful patch which makes our device more stable or fast.

for 3.6.y, it is not easy to port drivers (even not possible for some of them, such as for closed exfat module) to that branch or backport patches from that branch.

honestly, I don't have that much of free time to do it.
[Galaxy S III Original Android Development] Quipper2008:
Oh okay. Thanks for your info and your nice kernel =)
[Galaxy S III Original Android Development] egandt:
stweaks dwon after installing 1.8.3

updated to 1.8.3, so I had to download stweaks, but it always fails to download with a message ""stweaks" failed to down with error. (941). I've cleared the play store cache and rebooted, but still no luck.

Nor can I find anything on the error, is there a apk of it as I really could care less where I get it from, if Play wants to be annoying I'm willing to simply side load it.

Thanks,

ERIC
[Galaxy S III Original Android Development] sarbe:
There you go mate : http://db.tt/jkJS5qn8
[Galaxy S III Original Android Development] gokhanmoral:
It is still in /res folder. I just disabled the auto installation.
[Galaxy S III Original Android Development] MBurns2:
guys i flashed siyah 1.8 on last wanam 5.1 (lkc).I have some problems:high battery drain,slow charging..maybe 1.8 has some conflicts with last firmware ? ty
[Galaxy S III Original Android Development] ahac85:
For me battery so far seems quite good on.1.8.3, it's a bit early to say just yet, charging is normal on leaked 4.1.2
[Galaxy S III Original Android Development] MBurns2:
i flashed 1.8..maybe 1.8.3 can be better for last firmware ? ty mate
[Galaxy S III Original Android Development] przmus:
Does this kernel support 2WCR?
[Galaxy S III Original Android Development] ahac85:
Yes it seems to work for me