yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] bordikun:
Fix permissions fixed the microphone issue for me on 1st boot but on later reboots, mic won't work again. but only in voice recorder and other apps using the mic, in phone calls everything is fine outgoing or in-going calls no problem.

also I don't normally use voice recorder,s voice,etc. so i think it's ok for now. no need to flash back to 1.2.6 coz i'm loving the ******** sound mod :D
[Galaxy S III Original Android Development] BoneMo:
an Update

1.3.4 beta online just now :highfive::good:

Changes:

changed descriptions and removed some items from audio tab in ExTweaks. decreased default headphone volume slightly.added/removed some options and some defaults are changed. some cleanup in init scripts. reverted some parameters in pegasusq governor to defaults.
[Galaxy S III Original Android Development] giajp:
hi Gokhan,

when you release the various profiles of extweaks?
[Galaxy S III Original Android Development] gokhanmoral:
yes, v1.3.4beta is up.

the main purpose of the update was to change some texts in audio tab to prevent users thinking that extweaks = voodoo.

it still can amplify some audio but it is not voodoo, just a buggy crap from old sources which can prevent in-call volume or microphone to work properly.. some like it, some don't.. some experience bugs, some don't... so, be careful with it until the kernel is out of beta phase. I will add a global enable/disable switch to extweaks/audio tab which will completely toggle old wm8994 enhancements to prevent any bugs and let users use the kernel without any audio modification. and hopefully it will also help with the compatibility with the upcoming Voodoo Sound for S3 from François Simond (Supercurio). I tried not to modify any modifier on the functions, so I hope it will not break any compatibility if the in-built enhancements are disabled which will be disabled by default in one of the following versions.
[Galaxy S III Original Android Development] gokhanmoral:
I won't add any profiles until I figure out how to over/underclock GPU properly.

so, for now, ExTweaks regular version is just the same as paid version.

and to be honest I never had the paid version :)
[Galaxy S III Original Android Development] winwiz:
Just flashed v.1.3.4 on CM9

and as soon as I have, when I make an outgoing call there is no sound. The other party can hear me but I can not hear them. Help please! :crying:
[Galaxy S III Original Android Development] camspy:
I will install new betas when there will be assurance from others that microphone in calls and apps works without glitches
[Galaxy S III Original Android Development] BoneMo:
make a call to my self: OK,microphone works

make a search through google search using voice: OK,it works too :victory::victory:

info about my phone is in signature
[Galaxy S III Original Android Development] willybilly:
Marvelous beta release and no major issues running stock ROM ALF6. Audio sounds very sweet and beautiful. Treat this as a prelude on how a S3 audio sound would be with more tweak coming from Supercurio. Being using his Voodoo Louder in S2 and waiting impatiently for him to release it in S3.
[Galaxy S III Original Android Development] hellsgod:
i reported two weeks or so back that my sound in calls won't work anymore. i tried 3 stock roms, 3 modems and kernel, but... silece. so i sent it to the service, and it seems to be a hardware problem because they have to wait for a component.

so, its not siyah or any rom. if you have your sound back when you flash a stock rom and then never again had that problem, lucky you. but don't wait too long, use triangle away to reset the counter, flash stock and sent it to the service.

hells
[Galaxy S III Original Android Development] winwiz:
restored another ROM and it works fine, so the issue is pointing to a possible incompatibility between siyah and CM9
[Galaxy S III Original Android Development] neferym:
Sorry if my question is idiot... is it possible to backup my parameters of extweak?

They are reset for eatch flash :(

Thx !
[Galaxy S III Original Android Development] hellsgod:
many users who don't flash anything on their device also reported this sound problem. sometimes it's only incompatibility, maybe. but as i said, i flashed stock roms, restored backups but my sound won't come back.

hells
[Galaxy S III Original Android Development] elloar:
nothing change

hi

I have the same problems as before (with 1.3.4b). problems with the volume of the microphone.Can not Record, use S-voice and call out. But musicsound is wonderful with or without Headphone :D nice Work, I'm back to 1.2.6 for now...

But I had the feeling that the start up till the apps are done has taken longer than in 1.2.6, but maybe ims wrong.
[Galaxy S III Original Android Development] knights.JayTana:
Thanks Gokhan... glad to see the sign that you and Sig are back @ good... :good:

To all who already have 1.3.4, what are the removed toggle in audio tab? im contented with 1.3.2 for now...
[Galaxy S III Original Android Development] currydude:
From what I see only dac direct and a lot things have been renamed
[Galaxy S III Original Android Development] d8389:
New for SGS3 after SGS2

1. I'm using Go Launcher and several memory expensive application in background.

2. Not sure, but custom ROM's with ext power menu and 15 toggles and memory tweaks, that I've no idea how to remove seems to has memory leak.

Old:

3. Incoming call can cause system to kill my GPS navigator.
[Galaxy S III Original Android Development] mmse88:
1.3.4 GREAT!!! LOL~~

Will test it on my wife's stock rom.

Thanks bud :-)

P.S: I like flashing as well :-D
[Galaxy S III Original Android Development] woshiahboi:
Phones getting warm, any reasons pertaining to this/
[Galaxy S III Original Android Development] bordikun:
GM, quick question in the bass-boost mod. what's the diffence between the "gimme-drums" effect levels?
[Galaxy S III Original Android Development] KennyLegend:
Yeah... Its a beta!!!

Go back to last known stable edition. V1.26. ;)
[Galaxy S III Original Android Development] currydude:
Each progressive level has greater emphasis on bass than the previous. Level 4 has greater bass than level 1,2 and 3
[Galaxy S III Original Android Development] EdgaBimbam:
Atm for me 1.3.3 is allmost perfect just microphone isnt working fine :/
[Galaxy S III Original Android Development] gokhanmoral:
it's the next item in my todo list to reproduce and fix...

and then some mic boost will come next...
[Galaxy S III Original Android Development] bordikun:
Just flashed 1.3.4 mic problem still presists, I can only get to lvl 2 bass-boost mod. lvl 3 and 4, at max volume bass just sounds like a broken glass.

no mic problem on calls, either out-going/in-going calls are fine. just other apps that use mics.

edit: mic works but has very very low input/recording sound.

PS: now 1.3.4 boots like 1.2.6 (for me)
[Galaxy S III Original Android Development] hazri1974:
Download files seems too terrible now....arghhh....
[Galaxy S III Original Android Development] sacredabyss:
i thought international sgs3 have the same quad core cpu? So you mean all sgs3 cpu can,t handle 1800 mhz?:confused:
[Galaxy S III Original Android Development] mark2222:
Some wont handle it at all, some will require more power than others. Best to leave it at 1.4 if you don't know much about overclocking.
[Galaxy S III Original Android Development] drknezz:
So in both v1.33 and .34 I'm getting crazy graphical glitches and pretty big lags while scrolling through camera images in Quickpic.

No problems with v1.26 though, anybody else experiencing this too?

The sound mod is great however and no mic issues for me, I just can't deal with the Quickpic glitches so back to stable for me..

Sent from my storming fast Galaxy S3
[Galaxy S III Original Android Development] Franc38:
It's officially a 1.4 GHz processor. So anything faster than that is pure bonus. Some are lucky and get a perfectly engraved processor that can run flawlessly at 1800 (or even more) MHz and undervolt at -150 mV without a glitch. Others just have unstabilities at 1.5 GHz...

As all pass 1.4 GHz without problems, they get released, that's it. Those which cannot make it at this freq' just get thrashed.

Anyway, I flashed 1.3.4 3 hours ago and it's as great smooth and stable as 1.3.3 was.

No microphone issues, great sound, all seems well and stable.
[Galaxy S III Original Android Development] mark2222:
Scrolling in quickpic is fine here with 1.33?
[Galaxy S III Original Android Development] Franc38:
Quickpic scrolling is supersmooth with 1.3.4...
[Galaxy S III Original Android Development] Andrewtst:
previously I mention apps rotating issue, it wasn't there, all because of jelly bean animation install, Just removed and this kernel no rotating lagging issue.

but I found out v1.3.4 is not smooth as v1.3.3 .
[Galaxy S III Original Android Development] gokhanmoral:
I am now talking to a friend and he told me that Paranoid has resolved the in-call volume problem.

it seems that the problem is framework related.

if it is so I hope we can get the fix in cm9 as well...
[Galaxy S III Original Android Development] ascariz:
good. hope the stable version will be released soon. your kernel the only 1 that have better core control with your app.
[Galaxy S III Original Android Development] hazri1974:
1.3.4beta is smoother than v.1.3.3beta...thanks gokhan for ur hard works....tq
[Galaxy S III Original Android Development] stephenjason89:
You got it right :) thanks curry dude :P

sorry for the very late reply... was out :)

---------- Post added at 11:18 PM ---------- Previous post was at 11:16 PM ----------

thanks for that info :)

i appreciate it..
[Galaxy S III Original Android Development] gokussjx:
As far as I know, the framework should work on CM9 too!

Someone should definitely give it a shot. :cowboy:

Just replace the current framework-res.apk & framework.jar with the In-call Fix framework files.

Well, best use ADB Push. Framework-res replacement while using phone, would cause a crash. :mad:

(Don't forget to keep a backup ;) )

gokhanmoral, is the VoiceSearch issue due to Siyah Kernel?

I, & all the rest of the ROM users are facing the issue. Anything that use Voice Engine just listens, but doesn't type down.

I'm wondering if its Kernel issue, or something wrong with the Port :eek:

PS: I tried both v1.3.3 & v.1.3.4.

(I'll downgrade to last stable kernel if required, but first need to be be sure :) )
[Galaxy S III Original Android Development] knights.JayTana:
Just for the confirmation that 1.2.6 is indeed more battery friendly compared to 1.3.2
[Galaxy S III Original Android Development] currydude:
Pics or it didn't happen
[Galaxy S III Original Android Development] gokhanmoral:
should be kernel related.

omega and paranoid users have that problem

it should work fine on 1.2.6

I will try to reproduce and fix that problem.

for now it seems to be the last problem in the existing port.
[Galaxy S III Original Android Development] gokussjx:
Alright, hoping you find the fix soon :good: :)

I'll test it with v1.2.6 & share my results...

UPDATE: Yup, definitely some issue with last two builds. Voice search works perfectly with v1.2.6!

Good Luck with the fix mate :good:
[Galaxy S III Original Android Development] shorty1483:
Some of Omega users (including me) also facing the issue. Just reverted back to NEAK, and here the voice recognition works well. Also with Siyah 1.2.6.

So I personally would say, yes, Kernel related. But I am to noobish in Kernels to sort out the exact problem.

@Gokhan

Referring to your PM hint with DAC Direct, could that issue be related to the SoundBoost in your Kernel? I hope wo have no question of either / or :(
[Galaxy S III Original Android Development] EdgaBimbam:
While having call microphone works, with google voice app and record app it doesnt works

P.s. damn 1.3.3 so smooth
[Galaxy S III Original Android Development] Code124Y:
currently in Xlite ROM 7.0

with 1.3.4b

UV -100mV all step

max on 1Ghz

running until now, so far so good...

Sent from my GT-I9300
[Galaxy S III Original Android Development] ozzyita:
Hi guys, can I mount a 1,5tb ntfs hard disk drive which is powered by ac adapter with this kernels? Because I've tried without any luck.

Thank in advance

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] kilian7th:
Same problem on foxhound rom, sound is great but I miss the audio menu of 1.3.3 ...more options and best sound effects... but maybe it's just me who think that...

You're just great...

Thanks Master :)
[Galaxy S III Original Android Development] kilian7th:
Double post, sorry...
[Galaxy S III Original Android Development] droidphile:
@All users using aosp/aokp.

For the in-call sound fixed roms, do not attempt anything that will modify your framework-res.apk and/or framework.jar. It may break your in-call sound again. Talking about mods and themes. (This includes universal CM9/Aokp themes available on playstore too. If i'm right they're modifying framework along with systemui)

@gokussjx

You may wanna warn your users about this.

A small tip to all: Before nandroid restoring a backup, do a hard reboot (don't directly boot to recovery from rom for the same) - power Off/On Or power Off/battery pull/On. Else something that was working for you might not be restored properly because of an active register in the memory.
[Galaxy S III Original Android Development] gokhanmoral:
only one of them is removed because people were enabling it and complaining about fm not working. I will add it back after adding necessary code to check if fm radio is on or not.

other than that I only changed the titles...

all interface from old-voodoo (opensource one) implementation and functionality are the same as in 1.3.3

and I have just lowered the volume level a bit but you can make it whatever you like using extweaks.
[Galaxy S III Original Android Development] gokussjx:
Great tip.

Thanks, I'll let them know :good:
[Galaxy S III Original Android Development] ozzyita:
Hi guys, when I connect via otg I get this message. Any ides

Inviato dal mio GT-I9300 con Tapatalk 2
[Galaxy S III Original Android Development] danarama:
I'm pretty sure I answered you at least 3 times in eviollets manu kernel thread.

Anyway to help you and clear this thread up a bit...

What one kernel does for one person may not be best for another. Each device varies slightly in the voltages and CPU frequencies it can handle. This is because even in modern times, manufacturing processes are still unable to produce truly identical hardware.

This means that two "identical" devices with the same software, same settings, carrying out the same tasks on the same network in the same room will still use battery differently.

So now imagine two devices, different roms, different software, different settings, different Tasks, different networks, different countries....

...There is no way one kernel, one governor, one scheduler will be best.

There is only one solution, test yourself. Its the long answer but it's the only true answer.

I hope this helps. It's due to this that many people do avoid answering this question. You may notice threads like "best x for performance" or "best for battery" actually just get locked.

If you're going to get involved in rooting, you have to prepare to get involved with experimentation and testing...learn to get scientific about your methods.
[Galaxy S III Original Android Development] Franc38:
You know, it usually takes one or two days, and some charging cycles and or reboots to really get a kernel to settle down. 1.3.2 and even worse 1.3.3 and 1.3.4 are too new to really have an accurate idea of how they impact battery life compared to 1.2.6.

Plus, exTweaks options having changed, it's difficult to compare for identical configurations...
[Galaxy S III Original Android Development] kwanyin:
why always reboot to the hone page during editing or writing email??
[Galaxy S III Original Android Development] j3di:
I think you probably need to reduce your cpu under voltage values.
[Galaxy S III Original Android Development] asafba:
hi

how can i swap my link to internal sdcard with my external sd?

is it possible?

ty
[Galaxy S III Original Android Development] FadeFx:
Probably u just touch the back button unintentionally ...

–—–—–—–—–—–—–—–—

tapatalked from Galaxy SIII
[Galaxy S III Original Android Development] Pyr0x64:
I read in one of the threads here that you can bind links to your extSdCard with DirectoryBind

[Edit]

found it:

http://xdaforums.com/showthread.php?t=1741463
[Galaxy S III Original Android Development] hefonthefjords:
1.3.4 is the best implementation yet. Everything seems to be great here for me running on omega 7.0.
[Galaxy S III Original Android Development] gokhanmoral:
I might have fixed mic problem with omega roms.

can you please test v1.3.5beta and give a feedback?

but as I said in the blog, make sure you power off your device after flashing.
[Galaxy S III Original Android Development] SkillfulMmd:
Thanks i love this kernel!
[Galaxy S III Original Android Development] elloar:
I will Test it now, give me just 10 min :-)
[Galaxy S III Original Android Development] vsohail:
been using siyah kernel [currently the 1.2.6] for long however lately on my S3 running the latest CM9 nightly...when loading siyah kernel...everything works fine even the overclock to 1800Mhz however anything above 1600 (ie 1704 or 1800) when i run a quadrant on the first step at 7 out of 8 screeen just goes blank and phone crashes..i have to remove battery and insert again and then when i boot things are fine..wht problem could it be..i checked tht 1.2.6 supports CWM and CM9 ROM's ...apart from benchmarks there is no other issue..everything runs smooth and fine...please help..wht kind of issue coould this be..??is anyone else getin this issue...a software isuue or hardware issue??

---------- Post added at 02:53 AM ---------- Previous post was at 02:51 AM ----------

plzzz check my issue above and tell me if u geting the same problem
[Galaxy S III Original Android Development] elloar:
Ok i just flashed 1.3.5b in recovery and then i put out my Bat. Then i starded my phone. The Problem with mic is still there :(. With the first start was mic volume ok, after i activated the new soundthings and restart the phone my mic was gone:(.
[Galaxy S III Original Android Development] gokhanmoral:
ok thanks for the feedback. I will test it more before i release the next update. I will update the blog now.
[Galaxy S III Original Android Development] elloar:
This time i just let those things off and restart. Problem is still there. I go back to 1.2.6

Your wellcome
[Galaxy S III Original Android Development] vsohail:
plzzz help!!!
[Galaxy S III Original Android Development] torsrex:
Not all phones can handle overclocking. Either your uv is too low, or your phone simply won't handle 1,8ghz.

Edit: Oh, and I'm still experiencing low microphone volume within applications using latest 1.3.5.

Edit2: I'm using stock settings (no sound enhancements) and the problem is still there.
[Galaxy S III Original Android Development] vsohail:
oh so its basically an experimental feature...the question is the phone konks off only during a quadrant benchmark else it runs prfectly at 1800
[Galaxy S III Original Android Development] Cristiano Matos:
I already raise this question and don't get feedback. Sorry if i'm be persistent.

With latests betas camera dosent work properly (video recording) with cm9.

Sometimes camera crashes, sometimes not. When I'm able to completed a recording the video quality is very poor. Looks like vertical lines in screen.

With cm9 kernel all works fine. But I have another bigger problem: cm9 don't have your sound implementations:)

I'm afraid I can't live without it.

Any chance that it can be fixed when get back to stable?

Now I'm out of cm9 just to be able to use siyah. By the way, I don't have any kind of problem with checkrom.
[Galaxy S III Original Android Development] Franc38:
As I (and others) explained before, the cpu are produced with rather tight specs but still, each number is slightly different from the next. The objective is that most of them can handle 1.4 GHz (those which cannot are destroyed) therefore, many (if not most) can actually handle more than this. However it's just the luck of the draw. For some, the CPU can manage clocks of up to 2 GHz, for some anything above 1.4001 GHz will be too much. Same goes for underclocking (but that's quite correlated to the ability of handling overclocking).

As for the reaction of your phone. Well having the clock set to 1.8 GHz doesn't mean it actually runs at that speed for consistant periods of time in real life. Unless you throw some heavy gaming or maths tasks to it, chances are that your CPU runs idle most of the time and hardly breaks a sweat at any time.

To put it more directly, it is very probable that the only time when your CPU runs really at 1.8 GHz for more than a fraction of a second is when you run a benchmark, like quadrant (not the best one, if you want my opinion on that). So my suggestion is to set the clock to 1.7 GHz, try runing a benchmark, see if you have problems. If you do, set the clock to 1.6 GHz... etc.

In day to day tasks (and even in hardcore games like NOVA 3) you hardly see a difference between the CPU running at 1.4 and 1.8 GHz...
[Galaxy S III Original Android Development] Gilg@mesh:
running CPU@1GHz it eats NOVA3, FIFA12, Max Payne, GTA3, Asphalt 7, so imo running over 1.4GHz is overkill.
[Galaxy S III Original Android Development] mark2222:
First off this guy clearly has no idea what he's doing so I wouldn't personally suggest trying any overclocking. Did he even bump the voltage?

Second, games aren't everything but you're right, when the gpu takes over much cpu power isn't needed yet.
[Galaxy S III Original Android Development] laneyofdeath:
what ur saying about each device/chip having little bit different tolerance (one may be able to oc consistently whereas an identical spec device next to it may not be able to; as u say luck of the draw) not sure bout the rest though pal. If u tell CPU to ramp to 1800 it will, and most likely reboot. It will also get pretty damn hot :-)
[Galaxy S III Original Android Development] bedtime_with_the_bear:
You clearly don't understand how CPU governors work. That's OK, but please don't try to pass off your ignorance as fact.

When you set the CPU "speed" to 1.8GHz, you are setting the *maximum* CPU speed. Your CPU speed will still normally be very low (200 MHz on my GS3) and will only increase in speed when your usage hits a certain threshold (say 80%).

For your CPU to hit the maximum speed, you would have to be running at almost 100% CPU usage.

There is not a single battery powered device is not the world that, when configured correctly, behaves as you describe. If they did, if they did then instead of seeing 2 day battery life, your GS3 would get a few hours at most.

Install CPU Spy and check it a couple of hours later to prove how wrong you are. Unless you have a rogue app installed, then almost all of the time would have been spent in Deep Sleep - with your CPU running as slow as possible to preserve battery power.
[Galaxy S III Original Android Development] laneyofdeath:
I mean if u set max then min to 1800 jeez
[Galaxy S III Original Android Development] sacredabyss:
I thought I was the lucky one as i got a perfect screen without any ink marks. but not that lucky on the cpu as mine can only handle 1600 mhz.:p

it all gotta balance at the end of the day.
[Galaxy S III Original Android Development] sachinaik:
Gokhan,

I use Omega 7.0 and Patiently waiting for 1.3.5 final release.

Thank you for enabling voodoo audio enhancements in your kernel. :)