im trying to compare these two dll files but i dont reall know how to
I use this app.
http://www.ultraedit.com/index.php?name=Content&pid=34
I also recommend the free (!) WinDiff, on which I've elaborated in depth at http://discussion.brighthand.com/showthread.php?t=215073
hmm i like the ultraedit but it makes the dlls look all wierd. maybe its supposed to be like that.
my problem is that the dll bta2dp.dll from tornado makes the a2dp work. and the bta2dp.dll from treo 750v does allow it to work.
i feel this file is necessary but i dont know the differances
I presume that's a typo because as I read it, both dll's allow your application to work?
I don't understand the problem, if you have have one that works then isn't that the solution? I don't get what you're trying to achieve. DLL's are composed of functions which are dynamically linked to at runtime from the application code. If the parameters passed from the application to the function in the DLL differ from one version to another, or the return information is different then that's the reason why one works and the other doesn't.
Unless you have the programming skill to debug the procedure as it is entered and subsequently change it then there's nothing that you're going to be able to do other than compare version numbers of the files but since you have already found one that works, what's the issue?
David.
(Now I've noticed you try to compare binary files - windiff is only usable for comparing textual ones. Sorry.)
I need to lower the microphone gain.
My audio codec is clipping becouse of incoming PCM samples saturated from
the mic. I don't need AGC becouse it doesn't work well with my app.
I just need to manipulate the mic gain via software.
Is there a way to do it? I'm using waveform audio api ti capture voice.
Actually the gain is too loud !!!
Thanks.
Anyone knows?
OK, I don't have the answer. But since no one is responding I'll try to give a few ideas that might help.
First, I have a hp6315 and an apache. Under settings, they both have a utility to enable/disable AGC. The ipaq's utility is labeled "ipaq audio" if you disable agc, you can then configure the microphone gain. This gain is stored in the registry. I think searching for gain or audio will find it. The apache doesn't have this. searching for audio, gain, wav, volume in the apache registry doesn't find anything that looks like microphone gain. I guess this is a "value added" thing from hp. But you could try searching anyway.
Then there's the mixer API. This is the way that user level apps are meant to control the audio. Works great on the desktop. Use mixerGetNumDevs() to find out how many devices you can control. On the h6315 mixerGetNumDevs returns 0. I haven't tried the apache, but I can remember a few years ago reading that many (most?) devices return 0. Oh well, hopefully you'll have better luck. However, there are two mixers that are implemented on the pocketPC the question is how to access them.
see this link for info on the mixers
http://blogs.msdn.com/medmedia/archive/2007/01/12/what-do-you-mean-by-mixer.aspx
Here's a link that shows the relationship between the mixer api and the other mixers, wavedev2 mixer, and software mixer.
http://msdn2.microsoft.com/en-us/library/ms923709.aspx
You'll notice that the the mixer api interacts with the mixer in the device driver not the software mixer in the WaveAPI.dll. You'll so notice that this section on audio drivers has pages for MDD/PDD drivers and Unified Audio Model (UAM) drivers. Platform Builder for WinCE 5.0 comes with a sample for each of these model drivers. Both models handle WAV_IOControl Messages. There are two types of messages, IOCTL_MIX_MESSAGE for the mixer, and IOCTL_WAV_MESSAGE for the rest of the driver. It looks like these IOCTL_MIX_MESSAGE are the way the mixer API controls the mixer. In the MDD/PPD sample they can be used to set WPDMX_MIC_VOL and WPDMX_LINEIN_VOL. In the UAM driver it's AC97_MIC_VOL and AC97_LINEIN_VOL. Perhaps sending the right IOCTL will solve the problem.
This blog entry
http://blogs.msdn.com/medmedia/archive/2007/01/03/windows-ce-audio-driver-samples.aspx
seems to say that a wavedev2 sample is available now. Also, while the WinCE 5.0 page above only metions two models the corresponding wince 6.0 also talks about wavedev2. I suspect if you got the current version of platform builder for WinCE 6.0 (trial version is free) you would have get the sample code for wavedev2, which is likely to be the best documentation of how this works. Amazingly, the drivers aren't that hard to read.
Both of the functions waveInMessage() and waveInSetProperty() are available to user apps. Hopefully both should be able to change the microphone gain if you can set the parameters properly. While most of these things are about windows CE, I think most (or all) apply to windows mobile 5.
Windows mobile 5, likely uses wavedev2 devices not MDD/PDD or UAM drivers.
Another interesting page about wavedev2 audio is here:
http://blogs.msdn.com/medmedia/archive/2007/01/04/the-wavedev2-gainclass-implementation.aspx
If your able to succeed or even learn more, be sure to post it back here.
I said a lot so I probably got something wrong. Anyone, please feel free to correct anything.
mixerGetNumDevs() returns 0 on my device
I can't find any registry entry which suggests microphone gain manipulation.
Perhaps i just need to send a waveInMessage properly.
I'm getting confused, should i implement a driver for this?
How do i know what kind of driver is running on my device and what messages
does it accept?
Thanks.
i think this may be what you need(?)
use a registry editor, (phm do a good free one)
hkey_local_machine/software/htc/audiogain (and audiogain 0 and 1 and 2)
try playing with the settings in there, soft reset to take effect
I don't have that keys on my HTC, should i create it?
Do you mean audiogain0 audiogain1 audiogain2?
Thanks.
see the attached screenshot, if you don't have those settings to adjust, a similar/same question was asked last night in a other thread, with different answers here
http://forum.xda-developers.com/showthread.php?t=306655
Looks like the cab file from the link provided by bbobeckyj just sets those audiogain registry settings. I don't have those settings on my apache. I don't think adding will help, but "you never know".
If you want to use waveInMessage() or waveInSetProperty() search for them at microsoft. You'll find there are a few parameters that you don't know. Read though the sample drivers that you can get with platform builder. See what values they expect, and which one cause them to change the microphone level. Try calling the function with values from the sample driver. While there is no guarantee that they use the same values, it's like that they do. I would start with the wavedev sample.
I don't know why microsoft doesn't seem to allow access to the source without agreeing to download all of platform builder, but it looks like that's the only way to get it. You can download the trial version for free. The source often helps if your trying to fingure out how something really works.
Uhmmm, i havn't found any download link about platform builder for windows CE 6.0. I've only found the 5.0.
Should't the trial be free?
Thanks.
I need to fix audio gain in my Itel Experience Phone (Windows Mobile 6.0 Pro)?
Please help.
I need to mute mic while on a call. Anyone has a idea of how may i do it?
Thanks
moved to the right forum, please post in the correct forums.
Hi,
I'm trying to work through a hardware detection problem running an app (Osmos, purchased in the Humble bundle for Android). It seems that maybe there's something weird about how my Chinese tablet reports its multitouch or something, I figured I'd just hack the apk to remove the multitouch check and be done with it.
The problem is that the error string isn't in the application itself, it's part of a support library and occurs during initialisation, there's no obvious call to the library to ask for multitouch though I'm sure something flags it as required somewhere along the line but probably in one of a couple of parameter values that are long, undocumented integers.
The support library is called libverde.so and appears in the apk's lib directory when decompiled (apktool, dex2jar, JD are the tools I'm using). There's almost no information about it on the net, only a reference on a pirate site about patching it to remove a check for screen size (similar to what I want to do).
Has anyone heard of this library? Can provide any information on it?
bp.
Has anyone played with the Si4709 chip in a SPH-L900?
I've read plenty of stuff saying that the us variants don't have the hardware, but I thought I'd check for myself.
I built a kernel with support for the chip (using ashton seo of samsung's driver) and loaded up the module.
The driver is only documented in the code comments, so I tried Spirit just to see if it'd pick up on it, but Spirit reboots the phone when started. Sooo... I tried just turning on the chip in FM receive mode, which didn't result in a reboot.
I went over to sysfs and poked through the related twiddles (which there are a bunch of) and didn't come up with anything useful (most things were full of zeroes).
Anyone have any experience with it? Anyone have some sample code that works with the Si4709?
I guess it could be that the phone really doesn't have the hardware, but I'm not sure how to tell at this point.
The Spirit author (who presumably knows all about this stuff) does say in his Spirit thread that this phone lacks hardware, so maybe I should defer to that wisdom, unless someone has an idea as to how we can verify that the hardware is or is not there.
Edit: Here is a kernel with si47xx support if anyone wants to have a go. It's built as a module, so modprobe Si4709_driver to load 'er up.
The phone doesn't have the chip, you're wasting your time here.
Link doesn't let me access the files
Multiple errors on build: X module depends on Y library
Anyone have a good hack for dealing with broken library dependencies? Sure, you can go one by one to line them out, but seems like it'd be easier to put and ignore statement somewhere so you're not prompted each time a broken library is found on build.
Separate, but related, why would folks put source out there with so many of these issues? Is it just considered part of the build process that you have to deal with this sort of thing?