Database Info

Sound via CarKit Problem

Hello! I recently upgraded my Himalaya to WM5 AKU 3.5. Everything runs nice but I have a problem with the Sound. I use the Himalaya in my car in the T-Mobile CarKit. However since I upgraded the sound is not routed through the CarKit speaker anymore but remains on the internal speaker. I had this issue with some WM2003 Roms and so I know it's pure software. Can anybody please point me to a solution? Is there a way to change this in the ROM or do I need to search for a ROM that has this feature enabled?
Thanks

XDA II said:
Hello! I recently upgraded my Himalaya to WM5 AKU 3.5. Everything runs nice but I have a problem with the Sound. I use the Himalaya in my car in the T-Mobile CarKit. However since I upgraded the sound is not routed through the CarKit speaker anymore but remains on the internal speaker. I had this issue with some WM2003 Roms and so I know it's pure software. Can anybody please point me to a solution? Is there a way to change this in the ROM or do I need to search for a ROM that has this feature enabled?
Thanks
Click to expand...
Click to collapse
Hi.
Same with me as well. I am missing that very much. In between there is one workaround: if the 2.5mm stereo jack is accessible in your car kit, just plug a connector without a headphone/mike into it. This enables output on the 22pin pin connector as well. As I am using a homemade adaptor, this works for the moment - but I do not like the idea to use that 2.5mm jack all the time without really needing it...
So any suggestion, maybe some program to switch? - I do not care if I have to run that program manually when I want to have external output, although some automatic switching would be appreciated...
Regards, Uwe

Hi!
Thanks for your input. Unfortunately the 2,5mm jack is not accessible in the carkit. I start thinking about going back to WM2003SE. What a pity to loose DirectPush for that but the sound is more important....

Hello again.
IF someone from the "developer" group reads this thread at all:
Why are questions about this car kit audio issue always ignored by the rom cooking guys - at least I did not manage to find any answer by llbasha, c_shekar etc (my apology if I missed one). Even if it would not be possible to fix this, at least a definitive answer might be surprisingly interesting.
Please forgive me if this is a little rude, but I consider this a BUG in ALL wm5 roms - instead of just stuffing the rom with more and more gadgets of personal preference someone might look into this???????? HEEEELLLLLPPPPP!!! Anyway - do not misunderstand me - you did a great job, but still - some guys would like to have this problem solved...
I still think that even if there is no fix in wavedev.dll possible (I think that dll is the cause of the problem) it should be possible to write some small application to "tell" wavedev.dll to use the external speaker/mike for all audio I/O. If I would have the necessary input I would be willing to try to write an app. So maybe someone can tell me where to find information about functions within wavedev.dll?
Regards, Uwe

Solved !!!
astroguy said:
Hello again.
IF someone from the "developer" group reads this thread at all:
Why are questions about this car kit audio issue always ignored by the rom cooking guys - at least I did not manage to find any answer by llbasha, c_shekar etc (my apology if I missed one). Even if it would not be possible to fix this, at least a definitive answer might be surprisingly interesting.
Please forgive me if this is a little rude, but I consider this a BUG in ALL wm5 roms - instead of just stuffing the rom with more and more gadgets of personal preference someone might look into this???????? HEEEELLLLLPPPPP!!! Anyway - do not misunderstand me - you did a great job, but still - some guys would like to have this problem solved...
I still think that even if there is no fix in wavedev.dll possible (I think that dll is the cause of the problem) it should be possible to write some small application to "tell" wavedev.dll to use the external speaker/mike for all audio I/O. If I would have the necessary input I would be willing to try to write an app. So maybe someone can tell me where to find information about functions within wavedev.dll?
Regards, Uwe
Click to expand...
Click to collapse
Simply Download the attachement. It is a working wavedev2.dll which must be place in /Windows
After that, search Registry for "wavedev.dll" and replace it with "wavedev2.dll". Wait a minute, until you do a (software-made) soft-reset.
After that, you are DONE
Hope, you are not angry anymore...

Thanks
Hi.
Sorry for being this late, but due to some lack of time I did not check regularly. So I am the more surprised to find an answer .
I will check it this afternoon and report back.
Regards,
Uwe

<< S710/VOX VoIP Earphone vs Speaker Problem >>

Has anyone come up with a solution to route **INCOMING** VoIP audio to the internal speaker on the S710/VOX?
The vanilla S710/Vox VoIP install (at below link) works great out of the box, except I can find no way to redirect incoming audio to the earpiece. The conversation always plays through the speakerphone.
http://forum.xda-developers.com/showthread.php?t=311087&highlight=voip
There’s lots of talk about this problem on the Development and Hacking board—but I cant find a published solution—For **ANY** wifi enabled handset—even with cooked ROMs.
Any suggestions-- ??
THANKS.

Same Problem
Please, Help !!!
This problem is only with this phone, urgent VoIP Services please...
TAL

OK-
Ive found two solutions-- unfortunately, both for **PPC**.
Glofiish X500—WM5 non cooked:
http://eten-users.eu/index.php?showtopic=9556&hl=
SPV M3100—WM6 cooked:
http://forum.xda-developers.com/showpost.php?p=1400247&postcount=783
Several posts on different boards indicate this is an **OS** problem. Seems to me if this is true we are out of luck until an official ROM update (because there are no S710/Vox SP ROM Hacks out there).
On the otherhand—
The implementation may lie in the VoIP .dll’s which may be worth looking at since there are some floating around for SP's and PPC's.
Can anyone **CONCEPTUALLY** confirm the above?
Of course—
There may be an temporary workaround like the Glofiish solution.
Thanks.

From a posting on Modaco: would the headset solve the noise/privacy issue? I have not yet tested (I use Skype) but it seems like a reasonable workaround.

This issue is NOT SPECIFICALLY related to the S710/VOX!
THIS IS A CROSS POST-- TO CLOSE THE ISSUE IN THIS THREAD--
I EXPECT A NEW ISSUE-RELATED THREAD IN THE "DEVELOPMENT AND HACKING BOARD" SOMETIME SOON. THOSE GUYS KNOW WHAT THEY ARE DOING-- SO I THINK THATS WHERE THE ISSUE BELONGS.
And I Quote from Windows CE Networking Team WebLog:
http://blogs.msdn.com/cenet/archive/...ws-mobile.aspx
“… On some Windows Mobile 6 SKUs, VOIP (Voice over IP) is supported. This functionality is based on RTC. So, RTCDll.dll (RTC binary) will be available on some of the WM 6 SKUs. However, on these SKUs, RTC is not released as an SDK, but solely to provide the VOIP functionality. So if an application wishes to use RTC on these SKUs, it is free to do so, but that scenario won’t be supported by Microsoft. …” (May 23, 2007)
My reading of this is simply:
In order to “correct” the speakerphone problem, you gotta “correct” the rtcdll.dll.
And since all we have is a Microsoft binary release of the .dll (there’s no source out there, correct?) the only solution would be to write a new handset-aware (hardware-integrated, lets say, native) sip-client. And that’s not trivial without rtcdll.dll source.
That’s basically why the ROM-chefs havent come up with a solution… yet.
Or:
Is it as simple as getting the correct registry-settings?
I think not. I can think of several reasons why there’s likely no easy/simple registry fix.

How to get the remote control work on Duttys V4?

Hi people, I am hoping the remote control could get it work, coz I use my kasia as mp3 very often.
if any of you know how to sort it out please let me know, I've just saw on other thread that the remote control wont works on the HTC cruise, and since dutty V4 is base on the cruise...
oh well, I am just hoping to get it sort it.
and thanks to Dutty again for the fantasic Rom !!

if what your looking for a television remote of sorts, the tilt lacks the RF chip.

oh no, it's the wired remote for htc audio !!

You need the drivers. But the remote only works with wmp.

I thought the wired remote only worked with Audio Manager?
I would like to upgrade to V4 but not if the wired remote will cease to function.
p.s. any O2 users upgraded their radio? does it really SIM lock the phone ??

I have it and it does not work with duttys v4 polaris rom.
On other roms it works fine.
It works with audio manager and with WMP. Someone in another section of xda currently has some buttons working when you use pocketplayer.
All new devices already come with the drivers for this remote.
Older devices like hermes, Trinity etc, they are the ones that need the drivers. If you examine the EXE driver file from HTC, you will see all these names.
My own amateur opinion is that I thought the polaris/cruise came with a certain type of headset, and might have it's own drivers for the headset and not the normal drivers that say the tytn ii or touch have preinstalled.
I have asked dutty about it and he doesnt anything off the top of his head. he might try changing a few things in v4 final editions to see if that changes anything.
P.S. if anyone finds other drivers, and looks at the cabs inside and you see polaris/cruise as one of the cab files.. please let us know! Currently it's all older devices that the cabs are for.

you would think more people have this problem, or use this thing :O

install ms bt stack instead of widcomm (LG KS20)

Hello!
i have some trouble with the widcomm bt stack on my LG KS20.
For more information read this.
Is it possible to delete the widcomm-stack (included in original rom) and install a ms stack?
I have been searching for a long time to find an installable version of the ms-stack, but it seems like most people want to get rid of it and install a widcomm-stack...
Can anybody help me?
Thanks,
andi

there's the Definitive guide to bluetooth services in my sig.
go there...
i also believe the cabs are in the stack files i put there.

As far as I understood, this guide is how to optimize your Windows PC and not the mobile device. The bt-stacks also seem to be for PC. Am I right?
My Problem is between mobile device and bt carkit.

Please help me, because otherwise i have to sell the phone...

Samsung i908 BT DUN for WM6.1

I am using Samsung i908 with WM6.1, I just bought a Tomtom ONE XL and found that I have no way to connect it with my phone. After I checked and read many articles and found that the problem is from BT DUN, Microsoft makes this function to optional and still provides it to OEM manufacturers, but it seems Samsung removed this function when they produced i908.
Is there any way for me to add BT DUN back? I found that I can find a patch to add this function back if my phone is WM6.0, unfortunately my phone is WM6.1 Please help. Thanks.

I contacted TOMTOM, but they said that's the compatibility issue, they can not help. I also asked Samsung for help, but they have not provided any solution yet. Sad. Do you have any solution/suggestion for me?

Welcome to the forum
Perhaps you have not noticed that this is an HTC devices only forum, however in off topic there is a thread regarding samsung, perhaps there someone can help you
Good luck,