Thanks. Mine says dirty, but 2.6.3.9, Im pretty sure I`d flashed a 3.1 one.

Can I use any of them for an asus stock ics?

Originally Posted by will5

Thanks. Mine says dirty, but 2.6.3.9, Im pretty sure I`d flashed a 3.1 one.

Can I use any of them for an asus stock ics?

In terminal, run the command -

uname -a

You should see the build number (for example mine is #689), and you can match those numbers with the ones on the first page of this thread.

I have sound on the 700 kernel. but how does one load the voodoo module?

Sent from my Transformer TF101 using xda premium

Originally Posted by clouse2013

I have sound on the 700 kernel. but how does one load the voodoo module?

Sent from my Transformer TF101 using xda premium

If you are on ICS, no need. There is an ICS pre-alpha app on supercurio's thread that can be used together with his paid Voodoo Control Plus license from Play Store and then you will be good to go with Voodoo sound - on ICS.

Originally Posted by sidneyk

If you are on ICS, no need. There is an ICS pre-alpha app on supercurio's thread that can be used together with his paid Voodoo Control Plus license from Play Store and then you will be good to go with Voodoo sound - on ICS.

I know this. I I'm on Jelly Bean but I don't have the paid license. I trying to use the patches Guevor put in the latest version. The he just compiled it as a module.

Sent from my Transformer TF101 using xda premium

Originally Posted by guevor

I could not spend much time with the computer, so all I could do for now is to add timduru changes to add support for voodoo sound (thanks timduru). I've compiled it modular, so that everyone can decide whether to load it or not, and we can test if it gives any problems.
I have also made a test to CM10. The compilation is the same as for EOS3 but the ramdisk is different. I wait to comments on whether this version works.

Hi, I'm trying the JB CM10 700 kernel with the latest Jellybro and sound works fine, but i have no wifi. it doesn't pick up anything. anyone else? i tried flashing twice, clearing cache/dalvik, and fixing permissions, but still no wifi. i just redownloaded to my pc and compared checksums and they match up.

i loved this kernel on AOKP and I'm dying to use it again!

thanks!

Originally Posted by kukky

hi guevor...in your kernels i am not able to use wifi direct....is it a problem of mine?? now i'm on v23...

Inviato dal mio Transformer TF101 con Tapatalk 2

looks like you're not the only one.

Any idea if or when this awesome feature (very useful for Ad-Hoc WIFI multiplayer and file transfers) will be available on this kernel?

Really need a kernel that supports both USB game controllers AND WiFi Direct

Originally Posted by clouse2013

I know this. I I'm on Jelly Bean but I don't have the paid license. I trying to use the patches Guevor put in the latest version. The he just compiled it as a module.

Sent from my Transformer TF101 using xda premium

I'll just refer you to Supercurio's thread where he has stated that he will soon render that ability useless.

Originally Posted by clouse2013

I have sound on the 700 kernel. but how does one load the voodoo module?

If you're on TeamEOS3 you can flash the kernel from this thread:
http://forum.xda-developers.com/show....php?t=1810722

This basically is guevor #700 (#696 + voodoo sound)
the only difference should be that I enabled voodoo sound by default.
Otherwise dropping a script in /etc/init.d/ that insmod guevor's module at boot time will do the same on Guevor's kernel.

Originally Posted by sidneyk

I'll just refer you to Supercurio's thread where he has stated that he will soon render that ability useless.

From what I understood from our little talk, Supercurio is still ok with having kernels that include voodoo sound directly.
What he prefers not to have is the module distributed alone without a kernel.

From what I understand, in his next app he says that he's going to change his "business model",
and that both free app and non free will have the defaut analog volume control
(I think that also means that both his apps will try to insert the module, and that the module will not be distributed only with his pay app anymore)
And then the pay app will have more features.


Since I ported the module I've made much more researches and verified tests,
so I can confirm that the voodoo module is obsolete anyway.
There is actually no need for any new module needed to be able to control the analog level of the amp,
or actually any of its registers.

Which can simplify either the voodoo app greatly, (because Supercurio wouldn't need to even insert a module for his app to work)
But any alsa mixer can already control 80 or so exported registers, and you can control ALL unfiltered registers of the WM8903 by ioctl.

So yeah I'll leave the "business model" of inserting a voodoo module into a kernel to Supercurio, and just make an app that allows us to control much more, and also add other features, like the control of the FM34 and all that without any need for a new module.

One of the first use of that last one would be to work around the current bug in JB roms,
as I discovered yesterday.

Crap sound issue:
For those having the "crap sound issue" it's not particular to Guevor's kernel or the voodoo sound patch,
it seems to be a bug with the microphone handling, for example with Google Voice and our current JB roms.
To put the sound back to its high quality mode, you can either reboot, or just simply launch that in a terminal:
su
ioctl /dev/dsp_fm34 0x4004f302 1

From what I've discovered, what happens is that basically when you launch google voice, it activates different things including the DSP in the FM34 chip, thing being that something seems to crash, and so it never restores the values to their original values after it's done recording.
(basically it leaves the DSP in "MIC voice filter mode" which degrades the audio a lot if you try to play music in that mode, as it incorporates voice filters.And so the sound is degraded.

Until we can fix what is crashing, either don't use an app using the mic it, or launch the command I gave above after the first audio issue, and then it seems that you should fine until the next reboot.

just crashed with kernel 701 on stock .24 at 1000mhz underclock while goig "home" from AndChat, was using 607 with stock 24 before without stability issues.