yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] hardcore:
This shouldn't be a problem, as what that does is reboot the phone if a process gets stuck. Haven't encountered a situation where that has happened either.

It compiles for sure. Just tried to insmod it and it does load:

# insmod /lib/modules/mc1n2_voodoo.ko
insmod /lib/modules/mc1n2_voodoo.ko
# lsmod
lsmod
mc1n2_voodoo 1593 0 - Live 0xbf004000

If possible, I definitely do not want to enable KERNEL_DEBUG for this. If the module loads, does that means that it works?

BTW yes it is in the default directory /lib/modules which is where all the other kernel modules are.
[Galaxy S II Original Android Development] pedrolopes665:
My english is already very bad, but reading the supercurio and hardcore´s post make it seens even worse. LOL
[Galaxy S II Original Android Development] supercurio:
I think it applies more specifically to defective or OCed devices that tend to crash or behave unexpectedly.

Rebooting in this situation might tend to help making the situation a little worse.
[Galaxy S II Original Android Development] Entropy512:
This is NOT documented in the README. Nothing in the README indicates that vol_hpgain_addr and vol_hpsp_addr are set by the app.

You want kernel developers to integrate your module, but then insult them and claim they can't read C?

Hint for you here - the developers that are resisting are those who read C and find it strange. The developers that have included your module did so without any analysis or asking questions. If they had, they would have seen two module parameters (memory or register addresses from the looks of things) with no default values and no documentation, parameters which the module cannot function without (the sysfs interfaces will report -ENODATA when trying to retrieve values if these are not set, and will silently do nothing when trying to store values)

No, it's not a go. An interface test is a hell of a long way off from a functional test. (Where I work, interface releases actually occur 2-3 months ahead of functional releases in many cases, so we can fully test the interface before providing any function!) Edit: The reviews of your app from CM7/MIUI users prove my point. For them, interface checks are passing, actual functionality is failing. This is EXACTLY why I don't put stuff in that doesn't have a proper functional check.

A functional test would cycle through a few volume settings, playing a test sound in between.

Twitter? You support people on TWITTER? 140 character limit makes it kind of useless for that. I tweeted at you requesting more documentation on December 22 - the 140 char limit.

As to other methods of approaching you - the last time I did (when LinuxBozo and I had questions regarding Voodoo Sound on the Infuse after reviewing the code.), you just insulted me and accused me of nitpicking your coding style and ignored requests for clarification of the code or pointers to documentation describing what certain aspects of the code were supposed to do. We didn't receive a valid technical explanation from you regarding why some devices had speaker tuning and some didn't for at least two months (August 11 to, at the earliest, October 25.)

Right now, you are asking me to spend a few hours of my time to add module building to my build scripts, to claim that I support your paid functionality which I cannot test. If that functionality fails, will users come whine to you? Probably not, *I* will have to deal with the fallout. It's frustrating enough to deal with complaints of problems I can't test or can't reproduce, but to deal with that when a user's money is on the line? That's just simply irresponsible to claim support for something I haven't tested and requires the user to spend money to determine if it actually works or not. (As I said - you perform an interface check only, and NOT a functional check.)

A basic functional check/demo as described above would keep most people happy I think.
[Galaxy S II Original Android Development] ozzyita:
Hi guys, what's the cause of audioinlock kernel wakelock?

Inviato dal mio GT-I9100 usando Tapatalk
[Galaxy S II Original Android Development] supercurio:
@Entropy512 ok you're welcome not integrating the driver, and I'll feel much better once your aggression stop.

I'm not sure you realise the tone you're using here, and I'm definitely not prepared to act like a punching ball.

Probably why you didn't get the answers the first time? Not impossible sorry I don't remember.

However it seems like there is a pattern here.

@hardcore, sorry for the topic hijack.
[Galaxy S II Original Android Development] :
No offence taken, but I wouldn't like a kernel cluttered with things I will never use...I like speedmod because it's stripped of less useful things and it simply works out of the box.

Sent from my SGS2 - Checkrom Revo 4 | Speedmod k18 | Vertumus ICS Theme |
[Galaxy S II Original Android Development] pikachu01:
I seriously think that enabling kernel debugging won't cause much downgrade in speed. :/
[Galaxy S II Original Android Development] supercurio:
Testing and measurements should give a pretty clear answer here.
[Galaxy S II Original Android Development] gtda:
sorry i dont know much about ur app supercurio

but does it improve sound across the whole phone or just when using a headset

coz personally i barely ever use a headset

i think in call sound needs to be improved but other than that im pretty happy with my phone
[Galaxy S II Original Android Development] iNeri:
So... No love from harcore to supercurio and us:(

Common guys, you can make a deal, no one of you want to givein to what he thinks is right :(
[Galaxy S II Original Android Development] supercurio:
Hi gtda. It doesn't improve sound quality but only allow to reach higher output levels with the headphone amp, when they're connected on JACK.

The main goal is to drive high impedance and/or low sensitivity cans easier while listening to music or watching movies on your phone and it succeed pretty well at that.

I've always been a bit reluctant tweaking volume for calls, first because I'm worried I would break something - earpieces are reputed fragile.

Also feedback/requests about it can say one thing or the opposite so its hard to build an opinion. In doubt I focus only on what really makes a difference instead of adding as many half-backed features as possible.
[Galaxy S II Original Android Development] radicalgel:
Come on guys, the price that supercurio is charging for louder is next to nothing. Looking at his track record and the work he's done, I bought the app to show some respect and appreciation for his efforts even though i'm perfectly happy with the headset volume on my phone.

Hardcore and Gokhan are 2 more guys who do incredible work here and provide unparalleled support, and all this for free. Gokhan incorporated supercurio's module almost immediately and it works perfectly with siyah 2.6.3+, and that was his choice to do so. Hardcore may our may not choose to do the same. Either way, I Know that I have absolutely no right to complain.

Sorry about the long rant, but this is just me showing some gratitude. Really appreciate the effort you guys take.
[Galaxy S II Original Android Development] gtda:
thanks for the explanation, i understand that some ppl will want this and other like me it wont really effect (dont really use the JACK) much respect for your work and any dev here on xda, i will say im using ur voodoo screen tuning app and i love it. also love what hardcore has done with this kernel, getting much better battery life than before. have followed both u guys since sgs days
[Galaxy S II Original Android Development] shahulvm:
Seeing hardcore's posts after a long time.
[Galaxy S II Original Android Development] doongoo:
Hi hardcore,

I was using speedmod kernel since I have had my SGS2, but now I had to change the kernel to CF-root, because I need voodoo louder and CWM5.

I hope, you will integrate this two things in your kernel, and then I will be back to you:)
[Galaxy S II Original Android Development] supercurio:
Hi @hardcore yesterday I finished and released an ICS port for Voodoo LOUDER. So today I'll search why the module doesn't insmod in your kernel.

Even if the configuration won't work if full kallsyms is missing I suppose it should insmod!

Imagine that the .ko I built for Samsung KP8 3.0.13 kernel is in reality built against Galaxy Nexus 3.0.8 sources, which I didn't even hoped it worked.

But it's possible thanks to the minimalistic approach of this module, moving the complexity in the app instead.
[Galaxy S II Original Android Development] supercurio:
Erf no logcat no kmsg by default, its is kind of a nightmare for debugging.

How to enable logcat is described in the first post but no kmsg :confused:

~ # dmesg
dmesg: klogctl: Function not implemented

Too bad this kernel is so troubleshooting and developer unfriendly.

I hope hardcore you will reconsider your position about the logging policy, every app developer on the planet needs logcat for debugging their apps. Enabling logcat and kmsg by default, even if there's an easy option to disable would be a lot nicer.
[Galaxy S II Original Android Development] hardcore:
Hi supercurio,

I think you mis-read. I did compile the module and it *did* insmod correctly (without kallsyms_all).

Since the module insmod-ed correctly, will the app work?
[Galaxy S II Original Android Development] supercurio:
Ah but I'm trying to understand why the module I compile here doesn't insert, to begin with, because.. I don't like not understanding why :D

I checked and the .config I use to build "portables" kernel modules has debugging and tracing disabled as well.

Here it is.

http://pastebin.com/x5Wf6twE

But without the ability to debug this kernel, my only choice is to give up the idea or trying to do something else without KALLSYMS_ALL.

It just too difficult and I don't want to spend days trying in the dark.
[Galaxy S II Original Android Development] hardcore:
Could be because the last version of this kernel was compiled with preempt_voluntary instead of preempt. The modules wont work if they are compiled differently.

I downloaded the app to test it. I manually insmod-ed the module. It works until the "Driver configuration". The sysfs interface should already work once the driver module is loaded. My guess is, you need the KALLSYMS_ALL to determine compatibilty? Maybe you can work around that somehow?
[Galaxy S II Original Android Development] supercurio:
This kernel is no preemptible, like the old Galaxy S? (basically, as kernel itself cannot be interrupted) Seems like a regression no?

Ok that must be that, kernels modules becomes incompatible in this case, thanks for the explanation.

The sysfs interface becomes active only once the module is configured by the app, based on what's found in kallsyms (except the version entry which work all the time)

There is no workaround and I can't even try to build one with a kernel with kmsg disabled.
[Galaxy S II Original Android Development] supercurio:
Are you on gtalk/irc something like that for better communication efficiency?
[Galaxy S II Original Android Development] hardcore:
I've been experimenting between preempt and preempt-voluntary. In some cases the preempt-voluntary actually feels smoother than preempt, and definitely scores higher in benchmarks. Not sure which is better on the battery, but they seem to be similar. As you've discovered, the kernel in Galaxy Nexus is preempt-voluntary (but it could be because the CPU is a TI OMAP, and maybe OMAP uses preempt-voluntary by default).

Okay I have good news. With a little bit of hacking I could enable KALLSYMS_ALL without DEBUG_KERNEL. I still have to manually load the module, but your test app indicates that it works.

Are you able to update the app to load the module itself?

insmod /lib/modules/mc1n2_voodoo.ko
[Galaxy S II Original Android Development] hardcore:
K2-19-test1:

- Updated compiler options

- PREEMPT mode

- CPU hotplug changes

- Enabled KALLSYMS_ALL for Voodoo Louder and Tegrak OC compatibility

- Voodoo Louder module loaded at startup for testing
[Galaxy S II Original Android Development] fenomeno83:
Hello supercurio, sorry for little ot.

have you plan to allow to change microphone gain for video recording, because by default is too much high..or is it coded in camera.apk?
[Galaxy S II Original Android Development] :
Any major benefits over k18? These changelogs are quite obscure for users without programming knowledge :)

Sent from my SGS2 - Checkrom Revo 4 | Speedmod k18 | Vertumus ICS Theme |
[Galaxy S II Original Android Development] yabosid:
Ljuder works. Nice.
[Galaxy S II Original Android Development] supercurio:
Galaxy Nexus is PREEMPT

tuna defconfig
[Galaxy S II Original Android Development] coolfire:
Hurray! Downloading now! :D

BTW hardcore, will it be possible to have in CWM Recovery the option of enabling supercurio's Voodoo Louder? I know nuts about programming, though. Just saw this in N.E.A.K's kernel, and thought that you may consider doing something similar... :p
[Galaxy S II Original Android Development] newHere:):
is the problem of screen do not turns off sometimes fixed on the new test version?

thanks :)
[Galaxy S II Original Android Development] ithehappy:
@Hardcore:

Thanks for your effort on K19. But I've a request,

This screen unresponsiveness problem while charging is sorta irritating. I am sure you're aware of that, some other users already have mentioned of it, still if you like I'll upload a video of the problem.

Will look forward to your response.

Thanks in advance.
[Galaxy S II Original Android Development] gtda:
tried ur app with this kernel supercurio

i can definitely tell the difference

i only have stock samsung headphones so bass is pretty crappy

maybe with a quality set of headphones it would sound much better

still for me its not such a big deal but i paid to show my support as i use your screen tuning app

hardcore, what kind of difference are we expecting from k19 compared to k18

other than adding supercurios module

k18 was working well for me
[Galaxy S II Original Android Development] ProNewb:
Hi guys, I have noticed that Arabic isn't displayed properly after flashing this kernel. What should I do?
[Galaxy S II Original Android Development] newHere:):
the language is not related to the kernel...

it is roms related
[Galaxy S II Original Android Development] warfanax:
Hey hardcore. When you stated that this kernel has compatibility with Tegrak overclock I was so happy. But when I try tegrak oc app it can't load module and gives error (unable to run "insmod")

What might be the problem? Is this tegrak oc compatibility is not what I understood?
[Galaxy S II Original Android Development] gtda:
Had black screen issue on k19, never had that issue with k18, had to pull battery.

Sent From The Bermuda Triangle
[Galaxy S II Original Android Development] ephraim:
Be warned (i think this is because of my settings).

I flashed v19 test 1 without wiping cache and dalvik cache and it didn't go past the boot logo and i can't enter recovery mode.. so better wipe first, i had to flash to stock for it to boot. After that i wiped and ut booted :)

Just a piece of advice :D
[Galaxy S II Original Android Development] gtda:
i flashed via mobile odin and had no dramas
[Galaxy S II Original Android Development] ephraim:
I flashed through CWM.. Maybe it's just me, but hey, better safe than sorry :)
[Galaxy S II Original Android Development] nikzDHD:
I flashed through recovery and also got boot stuck, went into download mode and flashed via Odin that worked.
[Galaxy S II Original Android Development] ephraim:
You mean at the bootlogo? Same here. Did you wipe cache and dalvik cache? It worked as soon as i did it :)
[Galaxy S II Original Android Development] FrenchSparda:
not stuck at boot logo..but k19 isnt smooth on my phone.
[Galaxy S II Original Android Development] Randall Flagg78:
K19 Test works fine, with voodoo louder?

I'm on syiah since 2 days, because this app. When it's works fine, i return to speedmod. :)
[Galaxy S II Original Android Development] singingshiver:
I've switched from siyah and can confirm voodoo louder working fine.

Only prob is that cwm app isn't compatabile so cant specify backup name.

Battery life seems very good
[Galaxy S II Original Android Development] cbeckstein:
recovery manager app from market is your friend...
[Galaxy S II Original Android Development] warfanax:
Is this K19 support Tegrak OC? I didn't really get it? I red it in the description but when I install tegrak oc app it didn't work?

Can someone help me?
[Galaxy S II Original Android Development] singingshiver:
Thanks. Just tried to backup and it failed signature verification. Any ideas?
[Galaxy S II Original Android Development] mathsmart:
I switched to void from speedmod test 18 and I got really great batt life since !

If you can make it as smooth and batt friendly without the big heating issue on void than Ill get back for sure ! test 18 was great but a bit less on batt life than void

the problem with void is when used for a moderate to long time use the phone became a bit hot (even if its just browsing or talking a long conversation) :(

im gonna wait more review on test 19 before :) what do you guys think about it ?( I mean if you compare to void echo)
[Galaxy S II Original Android Development] jonny68:
Still using K2-18 and no issues,will keep an eye on here to see how people are getting on with this before i decide to flash or not.
[Galaxy S II Original Android Development] Marc-Sch:
Maybe you need to adjust the thread title :-)

Envoyé depuis mon GT-P7500 avec Tapatalk
[Galaxy S II Original Android Development] marsexpress:
Hi all. A bit of feedback for you. A few days ago I switched to siyah kernel; was using k18 final but I had a few problems, one was the phone locking up on the lockscreen and the other was about 3 times it would seemingly randomly start using 9% per hour idling on the lockscreen! Couldn't identify the cause via the usual tools. Battery usage showed android os as the consumer but no wakelocks visible. I accept that it might not be speedmod kernel at fault there.

So I switched, installed setcpu, undervolted and switched governor and I'm now getting the best battery life I've ever had, barely over 1% per hour idling, never had better than around 2% previously with any kernel combo. I know this kind of tweaking goes against what speedmod is about.

Now I'm not just writing this to trash speedmod-one thing about my new setup that interests me the most is that with siyah I have never, not once, seen a flash of the home screen when unlocking the phone before the pattern lock appears! Even with the stock samsung kernel I get that.

Cheers.
[Galaxy S II Original Android Development] Marc-Sch:
Strange! I do exactly the opposite : better battery life and more efficiency whith my car charger (even with the specific void.echo usbchg)...

Envoyé depuis mon GT-P7500 avec Tapatalk
[Galaxy S II Original Android Development] Marc-Sch:
Can you tell us more? I don't understand what "flash" you are speaking about...

Envoyé depuis mon GT-P7500 avec Tapatalk
[Galaxy S II Original Android Development] ephraim:
Hardcore doesn't usually change thr title if the ones he releases is just a test kernel :)
[Galaxy S II Original Android Development] marsexpress:
Hi there. Imagine your phone is locked with the screen off. You press the home or power button and the screen turns on and should display the pattern lock screen. The problem is that more often than not when you press the home button or power button as the phone wakes up you see a split second flash of your homescreen or the application you were running before you locked the screen before the pattern entry lockscreen appears.

The consensus seemed to be this is caused because the phone goes into a super deep sleep state. I had this problem with the stock samsung kernel and speedmod, the problem also persists between various firmwares. Since putting Siyah on I haven't seen this issue once yet.

Hope that clarifies what I am talking about.

Thanks.
[Galaxy S II Original Android Development] sinancetinkaya:
Hi Hardcore,

Recently I'm trying to get Bluetooth PAN to work but I couldn't. No matter what I did.

AFAIK BT PAN requires bnep protocol support, so, I compiled it as module. Insmod worked well but

pand -n --listen --role NAP

is not working, says "pand[3846]: Failed to connect to the local SDP server. Connection refused(111)"

I tried to build a kernel with bnep (enabled in menuconfig) from your sources. Device booted. Bnep module is working as module but I still get the same error :(

is the error hardware related, i9100 doesn't support BT PAN?

if not, where am I doing wrong?
[Galaxy S II Original Android Development] blossom:
can i flash this kernel over miui based rom?
[Galaxy S II Original Android Development] mariotme:
Nope its only for Samsung based Roms
[Galaxy S II Original Android Development] It_ler:
Can confirm.

With some stock, SpeedMod and Phenomenal kernels I have recognized the same thing. But it does not bother me.

BTW with N.E.A.K (1.2) it is gone too.

So it seems to be kernel-related.
[Galaxy S II Original Android Development] AllSeeyinEye:
I second that. Only NEAK and Siyah don't seem to have that 'issue'.
[Galaxy S II Original Android Development] ithehappy:
Voodoo Louder working, Deep sleep as well

Voodoo louder working fine with K2-19 Test 1.

Deep sleep is working fine too.

I can confirm there was no problem while flashing this, of course I ran the Kernel Cleaning Script prior to flash.

Swyping from my GT-I9100 via Tt
[Galaxy S II Original Android Development] xsaintzx:
Nope, I always have that issue when I'm using siyah kernel. 2.1 beta 6 and 2.4.2. Speedmod, phenomenal acts the same.
[Galaxy S II Original Android Development] Slow N Stupid:
just a question not meant to flame or anything...

does this issue matter? O.o i mean beside someone opening your phone and see what you were doing for SPLIT second... does this issue cause more trouble than that?
[Galaxy S II Original Android Development] KeesStolk:
Nop, this "problem" doesn't cause any problems.
[Galaxy S II Original Android Development] supercurio:
Hi guys :)

I updated Voodoo LOUDER app to load automatically kernel module from

/lib/modules/mc1n2_voodoo.ko

as requested previously by hardcore.

Its loaded only if it contains the version magic, which I added in source code 2 days ago, see https://github.com/project-voodoo/mc1n2_voodoo.

If the the custom kernel provides its own module, the version is checked first. If version matches with what's expected by the app its loaded.

If it's obsolete, instead the app attempt to load its own (which may fail if the kernel is not compatible).

In case of error, I added better reporting with dmesg error printed − for kernel having dmesg.

Starting with version "Launch special 9" now available on market (no other change)

Et voilà ;)
[Galaxy S II Original Android Development] scary_master:
How can i download it from Germany? It's not in german android market?
[Galaxy S II Original Android Development] supercurio:
Its not available in Germany until alternative payment systems are implemented, due to negative feedback.

I'm working on it.
[Galaxy S II Original Android Development] warfanax:
Hey guys what is TEGRAK OC COMPATIBILITY?

Does tthis mean this kernel support Tegrak OC app? I have been asking for the 3rd time but no one replied yet.

I wanna OC this kernel so much, downliaded Tegrak OC app but it gives error. So why Hardcore says TEGRAK OC COMPATIBILITY.

What the hell is that mean?

Anyone?
[Galaxy S II Original Android Development] spelaben:
You can download it and pay for the app in Germany if you install it from here: https://market.android.com/details?id=org.projectvoodoo.louder

Worked for me. :)
[Galaxy S II Original Android Development] hardcore:
tegrak might need to build a new module for this kernel. Not sure why it didn't work.