Just added 2.6.35.y-longterm branch. (current: 2.6.35.13)

Originally Posted by supercurio

There is no such consensus.
Galaxy S II kernel is 100% open source.

Some driver are partially Kernel partially user-space as usual, and we don't have source for those but speaking of the kernel we have everything. (already proven with custom kernels using arbitrary version numbers and no pre-compiled binary kernel module like mine)

then i stand corrected. with complete kernel code anything should be possible including boosting audio volume quite easily then. that's my number 1 at the moment.

Originally Posted by RogerPodacter

then i stand corrected. with complete kernel code anything should be possible including boosting audio volume quite easily then. that's my number 1 at the moment.

I analyzed the whole driver now.
The only thing possible is to boost the output signal by a maximum of +6dB (only) by analog settings of the headphone amp.
Its adding more noise and introduce bad ass distortion quickly, so there is no point using it.

Originally Posted by supercurio

I analyzed the whole driver now.
The only thing possible is to boost the output signal by a maximum of +6dB (only) by analog settings of the headphone amp.
Its adding more noise and introduce bad ass distortion quickly, so there is no point using it.

bad news. perhaps someone can use the gingerbread audio APIs that were introduced in 2.3.3 to beef up the output volume or audio quality.

Originally Posted by RogerPodacter

bad news. perhaps someone can use the gingerbread audio APIs that were introduced in 2.3.3 to beef up the output volume or audio quality.

Unfortunately those are hardware issues and limitations you cannot overcome by software.

Any comments on the source code repository?

Supercurio,

Your sample build script won't work the first time from what I've seen, as the modules will always be one "step" out of sync with the sources.

Originally Posted by pulser_g2

Supercurio,

Your sample build script won't work the first time from what I've seen, as the modules will always be one "step" out of sync with the sources.

That's right!
I updated the first post with links to scripts I use now, for compilation and flashing.

Originally Posted by supercurio

Unfortunately those are hardware issues and limitations you cannot overcome by software.

Any comments on the source code repository?

yes could someone give me a quick push in the right direction for when browsing thru the source how to identify which file(s) are actually part of the ROM, and which are just extra included but not used?

half of the source is loaded up with drivers and files for other devices/boards/etc.

Originally Posted by RogerPodacter

yes could someone give me a quick push in the right direction for when browsing thru the source how to identify which file(s) are actually part of the ROM, and which are just extra included but not used?

half of the source is loaded up with drivers and files for other devices/boards/etc.

There is no simple way to do this cleanly, basically it would just lead to boost hiss level and get more output distortion. Like I said: no point.

This is not an audio hack thread, please stay on topic.

Originally Posted by supercurio

That's right!
I updated the first post with links to scripts I use now, for compilation and flashing.

Thanks I botched one up, but this looks better