yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] g4rvd4:
I've a question regarding exTweaks.

If I uninstall the app, will all the modifications be removed? Or do I have to manually set everything back to default before uninstalling?

And if I install another kernel, on reboot will exTweaks attempt to modify that too? (I mean some change like UV)

Edit: in short, what do I do to completely remove siyah + extweaks and go stock?

Thanks will be sent your way.. :)
[Galaxy S III Original Android Development] EdgaBimbam:
also with 1.3.7 while listening to music and going to extweaks, sound volume reduces.

btw i saw that some of you use 100mhz as minimum scale. Whats the difference between 200 or 300 mhz while they also have same voltage? o.O
[Galaxy S III Original Android Development] shorty1483:
Less frequency = less power dissipation = less power consumption (vCore) and less heat

...if I remember right...
[Galaxy S III Original Android Development] Franc38:
I confirm what many have already said...

with 1.3.7 the sound quality is improved (OK, that's subjective, but well... )

and battery drain gets much worse than 1.3.6...

You see quite well the moment I flashed 1.3.7... It's the point when the slope suddenly becomes much steeper! Same settings in exTweaks, same (light) use, same location so identical or very similar network conditions...

I feel like I'll soon be back to 1.3.6... until 1.3.8 gets to combine 1.3.7 sound and 1.3.6 battery (or even better ;) )
[Galaxy S III Original Android Development] KennyLegend:
U have a lot of wakelocks in that "steep slope" period. . Have u tried running BBS to see what's keeping ur phone awake? I'm guessing it's a rogue app and a coincidence it happened after u flashed the kernel.
[Galaxy S III Original Android Development] mark2222:
Just checked my bbs and audioout_1 was top of the lists. Could just be from using the headphones I guess.
[Galaxy S III Original Android Development] Franc38:
Stupid me... I should have checked. Now I've re-plugged into my PC for uploading the pic and so the stats got all messed up so it's hard to see what happened at this time. I don't think I've installed anything at this time or that any other specific app could have gone rogue... Always a possibility but hard to tell, now...
[Galaxy S III Original Android Development] box4m:
Does it lag more when setting min frequency to 100mhz instead of 200?

Any impact at all with this setting? Except less power maybe
[Galaxy S III Original Android Development] T.K.B:
Just posting to say thanks to Gokhanmoral :) I've been using the 1.3.3 kernel for a few days now and have tested out the sound intensively. My first impression was indeed WOW- finally was able to listen to music at a decent volume output level compared to stock kernel's. Im using stock ROM and Playerpro- maxed out headphone amp in extweaks- and now i dont even have to put the music volume to max cos it's so loud already :p very impressed. Although I do have one problem- can;t hear anything from fm radio- but it's ok for now since I don't listen to radio anyways. I'd rather wait for your next stable release- till then just gonna stick with 1.3.3

Keep up the good work Gokhan :good:
[Galaxy S III Original Android Development] shorty1483:
No because CPU only settles down to this frequency when in idle, screen on our off does not matter. Pegasusq and hotplug are ship responsive that I personally don't feel it being laggy...

Gesendet von meinem GT-I9300 mit Tapatalk 2
[Galaxy S III Original Android Development] supercurio:
Hello.

I didn't test latest kernel versions but in the source code I see the fork of my old driver written for original Galaxy S and WM8994 is still declaring itself as voodoo_sound.

Existing Voodoo Sound application with this driver on Galaxy S III will disappoint (optimizations that are not, malfunctions) and I want to be sure to avoid that and confusion to users.

Please change it to your own name: I would suggest to "sound_boost" as its the name used in this thread.

This request can be ignored if it's done already.
[Galaxy S III Original Android Development] hkfriends:
confirm 2 things on 1.37

1.) better sound quality

2.) battery draining => kernel wakelock on

"secril_fc-interface"

"usb device wake lock"

"battery-monitor"

"multipdp"

"AudioOutLock"

"usb cb wake lock"

"alarm_rtc"

....
[Galaxy S III Original Android Development] mmse88:
Hi mate,

I was used to use VooDoo LOUDER (paid) version. Is there any new drivers that can support GS3? Thanks!
[Galaxy S III Original Android Development] supercurio:
I'm currently working on Voodoo Sound for Galaxy S III, for a pre-release, quite soon.
[Galaxy S III Original Android Development] g4rvd4:
I'm experiencing intermittent crackling sounds over Bluetooth while playing music, could that be because I have undervolted by 50mV? Running the stable kernel.
[Galaxy S III Original Android Development] mmse88:
Seems latest version battery drains

Been tested latest version 1.3.7 for a while and found that battery drains much faster then 1.3.6. My wife's setting has no change at all:(
[Galaxy S III Original Android Development] Andrewtst:
v 1.3.7 is not smooth.
[Galaxy S III Original Android Development] androb0t:
battery gets hotter with 1.3.7 .....,is anyone experiencing the same ?
[Galaxy S III Original Android Development] xos84292:
I am on 1.3.7 , 5 hour with 45min music 20 min display and 4.5 hour hspda idle (auto sync ,whatsapp gmail cubie) ,98%->85% ,i think it's not bad
[Galaxy S III Original Android Development] doki81:
i got the same experience for stock rom with 1.3.7..now revert back to 1.3.5 where the battery draining seem to be slower ...
[Galaxy S III Original Android Development] MagicOnline:
reverted back to 1.3.6. battery life with 1.3.6 is better than 1.3.7.
[Galaxy S III Original Android Development] bordikun:
battery is fine for me, overnight 8hrs+ 4% drop. not on airplane mode
[Galaxy S III Original Android Development] willybilly:
1.3.7 sound has drastically improved. Audio quality is good now.
[Galaxy S III Original Android Development] gokhanmoral:
You will remember this post that I sent you some days ago but since you continue to tell me the same I will post it here this time:

First "don't use my descriptions and titles" and now "don't use my device file"

This software is announcing itself as a kernel which has almost exactly the same file as this one.

just read lines 6 & 7.

I don't want to start another discussion on this.

If you insist on having voodoo_sound dir renamed I will do that.

but "be careful what you wish for".

my anarchist instincts are sometimes hard to control and I can sacrifice my holiday to modify couple of registers on wm1811.

I have written more than a dozen drivers (from scratch) on vxworks and integrity. it is way more easier even than MIL-STD-1553...

if it is really your main source of income, don't push me hard and make me develop ScoobyDoo Sound...

I just wanted to have an amplification feature based on your previous implementation (which by the way you twitted about it of not being possible) and you know my reasons already.

so, it is your call Francois...

free kernel, free source, free app and free will...

I only share, you also sell... and only noobs can believe in what you say about "not possible" and "completely different".

And since you insist on that opensource part changed I will do that request just because you used the word "please" (you know it better that I don't have to make any single change in that part, no matter who requests it). But I promise I will implement every single feature you make in your voodoo sound app as free and open...
[Galaxy S III Original Android Development] gokhanmoral:
he can do that by updating his own app. he has no right to force that change, but can only request and whine about it if I do not fulfill that request.

and FYI, he put that repo up some time ago and it was opensource.

everybody was happy, curious and willing to spend money on that work.

I even bought his pro app to support that.

but when I talked to him about two weeks ago he told me that the new implementation will be closed. he has his reasons.

but then I have the right to, at least, make a port and make some parts to work.

if he doesn't want his app to work with S3, he can make modifications on it and publish so that people will see that it is not compatible when they update.

and "I have already closed that repo" thing is just not acceptable.

why would I care about his app, product and others on an opensource project?

why would I care about him except for giving credits to him, which I did already, for the previous implementation?

I would, if the manner wasn't so harsh and forcing...

But, well, now I don't...
[Galaxy S III Original Android Development] tridibsahabd:
The crackling sound is a known problem with S3. There's a dedicated thread on this.
[Galaxy S III Original Android Development] ch061441:
LED Problem wit 1.3.7

Yesterday upgraded to 1.3.7 and now have following issue

after charging and togle the cable, the red led still on.
[Galaxy S III Original Android Development] svetliol:
Can i flash this kernel with older versions of Odin 1.3 or 1.7?
[Galaxy S III Original Android Development] 8ax:
As there is no tutorial on how to flash kernels, I just flashed PDA with Odin 1.85. (1.3.7b)

Now, in settings it says it's on Siyah kernel, but I can't install ExTwaks, it says something about uname, and SuperSu doesn't work too.
[Galaxy S III Original Android Development] jody2k:
For my personal experience 1.3.7 gives less battery drain than 1.3.6 i'm on omega rom
[Galaxy S III Original Android Development] Franc38:
Flashing with Odin is OK, mobile Odin even better.

Now, apparently you've lost superSu, so you'll probably need to reflash or simply re-install it.

It may even be that you've lost root for some weird reason. In that case, flash CF-root using Odin, then install mobile Odin, reboot (maybe wipe cache and dalvik for good measure), wait a bit then flash Siyah 1.3.7b.

You should then be OK.

By the way, back to 1.3.7 problems with battery... After yesterday problems I reflashed it, turned the device off for the night and TADAAA this morning battery usage is back to normal: after 3 hours (mainly being "idle", syncing my exchange/gmail/facebook etc. on weakish E/3G/H/H+ networks, reading 2 or 3 mails, DL-ing one app update) I still have 94% battery left.

The wakelocks seem to be on the fall...

So I think that for whatever reason, the flashing of that version 1.3.7. is quite sensitive... wiping, flashing, stopping the device (maybe even remove battery) etc. seem necessary for a proper installation... At least in my case (but I suspect many others too).

EDIT

By the way, I've realised that I had sound problems during the time of the intense battery drain: at some points no sound would come from the device, be them from the speaker or from the plugged headphones... Some times I had sound but very very delayed.

Now that battery drain is back to more standard territories, no more sound issues... I suppose that supports my hypothesis about incorrect/incomplete/sensitive flashing.
[Galaxy S III Original Android Development] supercurio:
First thing, an abuse of my brand and product name (publishing a "Voodoo Sound port" when there's high demand and expectations for me to release).

Then a counterfeit of one of my work (inside ExtTweaks, 100% copy of exact sentences from my app on Play Store).

Now, threats.

"Be careful what you with for, my anarchists instincts are sometimes hard to control."

No matter how I read this sentences written, that's very much sound like threats, which is not acceptable.

I must have done something really bad to deserve this. Or maybe I don't.

If you have any doubt, please re-read what I actually wrote and asked for, it's all here.

Seriously, its as ugly as it gets.
[Galaxy S III Original Android Development] DirkStorck:
Stupid question but how do I download 1.3.7 from http://d-h.st/yXb ?

Thanks!

EDIT: I am stupid....found it ;) :)
[Galaxy S III Original Android Development] cyberdick:
There is a Download button between the two ads. Click that!

EDIT I'm stupid too, and didn't see your edit.
[Galaxy S III Original Android Development] KennyLegend:
Guys.... Its been said 50 million times now that wiping cache and dalvik does nothing for the kernel. It's like pulling in at a garage for petrol because your tyre is flat.!! .. Quoted from Hacre aka NinpoUK.

I always use mobile odin with the tar version and I never have a problem. Most of the problems seem to stem from flashing through cwm.
[Galaxy S III Original Android Development] FadeFx:
I'd say most problems stem from user error, i always flash from cwm without problems...

That Guy without root probably never had rooted his device in first place, why some have excessive battery drain is hard to say, looks to me like some rouge app...

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

tapatalked from Galaxy SIII
[Galaxy S III Original Android Development] TYA.:
I use Neutron mp + dspmanager, and a Shure SE535 before 1.3x with sound tweak

Sound was good. But after use 1.3 x I got broken sound, because of over gain.

Then I setting again Eq in Neutron, Eq in dspmanager and its loudless compensation to match setting of 1.3x tweak.

It is better now!
[Galaxy S III Original Android Development] Franc38:
Yeah. I flash with mobile Odin... And yeah, normally wiping wouldn't do anything. But then I observe what's going on with my phone... (That said, I've flashed countless kernels from recovery with my Nexus One, and never had a problem)

Now it might have been a rogue app... and it almost certainly was. However, that app going rogue had to be related to the kernel. I didn't install any new app, I didn't do anything fancy.

And... I'm far from being the only one having had bad battery life with 1.3.7 to begin with. So...
[Galaxy S III Original Android Development] KennyLegend:
I'm not saying 1.3.7 was not heavy on battery or that u don't know how to flash.

In ur situation... Observing what's going on in ur phone is obviously placebo as wiping cache and dalvik cannot have an effect on the way the kernel behaves. Maybe coincidence, maybe the reboot did it. Maybe flash twice one after another.... I dunno... But wiping cache and dalvik cannot be the reason ur phone returned to normal. And it cannot cause an app to mess up. Again.. Coincidence.
[Galaxy S III Original Android Development] gokhanmoral:
now here is my answer to your post:

did you or did you not threaten me to use XDA authorities to resolve this issue if I do not change the file with GPL license?

and I told you to do that.... please do that already because I don't think XDA authorities are unaware of that license model and force me just to make you more happy.

I always talked to you on gtalk before I post something related with you.

and my posts are just an answer to yours...

you have been tweeting lots of things about the old implementation.

I have already made some modifications on the descriptions, titles and corrected some parts to prevent users think that it is voodoo sound which is your brand name.

BUT....

in you tweets you used "defective", "broken", "poor results", "won't work", "kanging", "clone of an original product", "inadequate"...

I proudly say that I cloned your old kernel repo which was for Nexus S and ported it to S3...

I do not hide that the original implementation is made by you.

I also say that there may be some bugs, and most of them are fixed already...

and the results are great now...

now what is your problem?

is the problem that people using old voodoo sound app with this kernel?

and that supports that old code could be ported and you were totally wrong on claiming otherwise?

as I said in my response to your previous post: I will change the sysfs name.

and I will publish a free app on the market to control all the previous features.

this is not a threat but a declaration.

you have gone too far on that, both on twitter and in my thread. and I think somebody should prove that it is not your monopoly.

so, if you do not have anything else to request please stop talking about my kernel and the port (a successful port)...

I am planning to publish it today. I am just trying to make the number of changes less than 50 (they are 70 now)
[Galaxy S III Original Android Development] armanderli:
Back on Topic...

the last 1.3.7 beta doesn't work very well with the last CM9 Experimental build as far as Camera is concern...Codeworkx modiifed the camera can you look at it in the next beta...Thanks
[Galaxy S III Original Android Development] supercurio:
I think anyone who followed the thread noticed that it was broken. I don't see any way you could deny that.

Among defect: Headphone, microphone, calls issues.

I asked for respect for my hard work, based on common sense requests and also generally accepted in this world copyright basic stuff, and said "please don't force me to ask help to xda authorities"

Now there's no doubt you have you very own way to see things, and that you prefer twisting facts your way in order to use your large fan base (you have one because so far you always did great work, so well deserved) as an amplifying weapon.

If I can say there are defect, malfunctions or optimizations thare are not, it's simply because I use a strict testing and measurement methodology instead releasing something and asking users "Please tell me if it improves sound quality".

It's my job, recognized by the audio chip manufacturer themsleves so maybe it means something.

I make some open source software and some closed source, some free and some I sell.

Is it supposed to be right to be threatened and insulted publicly because some of my work is not open source?

So, your day job is in aeronautics right. All your work is opensource as well?

If not, you think its would be fine receiving threats and insult for that, and that someone would direct a fan base against you?

That's wayyy over the line.

I'm off for a while now. Lost motivation.
[Galaxy S III Original Android Development] supercurio:
And BTW.

People rejoice! Yay.. Free stuff! gokhanmoral our savior !

Reality check: a free Vodooo Sound application is existing, since the beginning.

Wake up call, that's manipulation, in no way gokhanmoral attitude is fair or right.

Also, no doubt it will be easier to create a clone thanks to all the knowledge I shared with you in private chat. My mistake, trusting you. Huge one.
[Galaxy S III Original Android Development] gokhanmoral:
I will leave the evaluation of most of your points to users. There were bugs. maybe there still are some more... but as I said before, I share what I use...

just tell me this: when did I insult you?

you are the one having problems with the port.

you are free to keep any part of your closed as long as it doesn't violate some other license. and I have the right to use any GPL code in another GPL'd code. this is very easy to understand, isn't it?

I have stated countless times that it is your expertise and you might come up with a better implementation.

but I also claim that it is not hard to modify those registers and gain considerable amount of quality over the stock one.
[Galaxy S III Original Android Development] gokhanmoral:
I never named anything in my kernel Voodoo Sound.

I used "port" and it is a port of an open-source kernel driver mod/hook.

and the application that people use to configure it is ExTweaks.

I have already removed all voodoo references (check the first post and blog)

I have just put there that which sources are used in that and I have just given the link and the link already has the author and copyright.

There was NEVER [Voodoo] in my thread title.

now there is [SoundBoost]

It is not the name that matters now. it is the old Voodoo Sound application compatibility with the new port because I used the GPL'd code as is...

and it will be resolved in the next version, as promised...
[Galaxy S III Original Android Development] supercurio:
If I read correctly it means that you are now accessing my request not using voodoo_sound anymore right.
[Galaxy S III Original Android Development] gokhanmoral:
just paste here anything you shared with me on Voodoo Sound implementation that helped me on that port and I will resign and never come back here again...

I was the first one loading your mc1n2_voodoo module and helping you to work it on custom kernels. If you let me I can happily share that part...

in case you remember it wrong, go back and read all our chats...
[Galaxy S III Original Android Development] gokhanmoral:
I will remove "voodoo_sound" from the code.

not because I have to, I especially want to emphasize that...

because no one on earth can force me to do that...

so, I will fulfill your kind request....
[Galaxy S III Original Android Development] supercurio:
This has been hard.

At last.
[Galaxy S III Original Android Development] gokhanmoral:
would be easier if you attitude was not harsh and threatening from the beginning...
[Galaxy S III Original Android Development] supercurio:
Maybe I shouldn't post here but, i still feel the need to explain.

I'm anal about quality and quality control, why I started this project in the first place, nothing new here.

I might be perceived as crazy about quality control before releasing anything, but that's my trademark, and also why I'm so slow.

I have no issue with other sound mods: franco made his own, nobody was confused, fine!

Current Voodoo Sound application on Google Play cannot work properly on Galaxy S III (stuff like headphone equalizer affecting speaker or earpiece, not good, and a lot more), and what's an optimization for WM8994 is not for WM1811, hence my requests.

Quality!

That's why now Vodooo Sound app cannot be downloaded from Google Play with a Galaxy S III. Its still the case. If it doesn't apply from your device, please tell me how to reproduce the issue. (is it CyanogenMod?)

I do the same with many other incompatible devices, to avoid 1* ratings except Play filtering is a mess (blacklist) instead of a white-list, why inevitably there are hit an misses.

You know, its fairly easy to receive tons of 1* ratings and comments on google play if people are unhappy with something, and in a few hours your app can be spammed heavily.

Previous Google play experiences forced me to react without delay, this has been a deciding factor.

If it was my intention since the beginning its true I eventually failed to blacklist Galaxy S III GT-I9300 for Voodoo Sound app in time, because the device appeared late in Play Store filtering capabilities and I admitted the thing would be so broken nobody would try to port the old code anyway.

When I said there always have been a Voodoo Sound free app, I mean since the beginning of the project, which made a few people happy according to feedback.

There's none yet for Galaxy S III as the moment as it's not ready.

PS: I tend inevitably to answer to questions and feedback.

I'm aware its not my thread. If you don't want me to post here, don't ask to, or just ignore my messages.
[Galaxy S III Original Android Development] Mopral:
To supercurio:

The free app is blocked on google play but the paid one is not!!!

(see screenshot...)

screenshot here

So what is your main issue with GM ports:using old stuff or possibility for you to earn less money???

If you really do not want to support GM ports, then you HAVE to block both apps...

Otherwise it is just a matter of money...
[Galaxy S III Original Android Development] supercurio:
This comment is a bit of a stretch but I understand it perfectly, typical French state of mind, I can think the same.

Some people buy the app just to encourage me, so there's no valid reason I should prevent that.

Also, when Voodoo Sound for Galaxy S III will be released, it will be a pre-version apk, not published on Google play before weeks of more work.

However this pre-version will transform into "Plus" with the app you linked installed.

As it takes between hours and days for an unlisted application to re-appear again, depending on cache, carriers etc I kept the Plus application online, as I was planning pre-release today.

But instead I'll go out and rest a little.

Sorry again about the thread hijack. People ask: I answer.