What is the latest version of android on polaris with everything working (especially Headset and camera)?
Plz, post linksa to the distribution along with the kernel and initrd, and necessary updates (if any).
Plz, DO NOT ANSWER, if you don't know about HEADSET AND CAMERA.
A quick search on this forum will answer your question!
Related
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
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.
Hey, I currently use Dutty's ROM. Not sure of the version, but I put it on in March, so it is probably a bit behind as of now.
I really like the ROM overall, but I'm looking for a VoIP option. I like the full featured ROMs and I'm searching through the threads, but wondering if anyone has any suggestions for the full-featured ROM I'm looking for with VoIP.
Laurentius26's L26_KaiserDiamond_V9 has just that animal.
It's also a full feature rom that is very nice to use.
Psi
It is pretty easy to re-cook most of the ROMs with VoIP integrated
I took the latest official HTC WWE ROM, dumped it and put it into the kitchen and re-cooked it with VoIP included. It was pretty simple to do. There seem to be 3 different VoIP file versions floating around however I used the latest I could find (files from April & June 2007), if there are newer ones I would be grateful if anyone could post them or post an URL?
There is still the ongoing issue of the audio being routed to the external speaker and not the phone speaker (unless you use a wired/bluetooth headset). It looks like the Hermes is the only HTC device that gets the VoIP audio routed correctly?
I replied to a previous thread about this
http://forum.xda-developers.com/showthread.php?p=2378090#post2378090
Andy
Hi,
Hope I don't seem like a noob in asking this question, In the fallout ROM under Hardware information, We are using BT V3.0, Could the issue with BT not working be related somehow to this, In simple English "Is the BT on the ROM too advanced for our BT devices?, Do out BT devices support and recognise BT V3.0"
Should be backward compatible...
Tapatalked from a Desire S waiting for Kernel 3 sources. WAKE UP HTC!!!!!!
Should be, Does leave room for doubt though, I'm not a dev but it might be worth looking into
dannyhoughton74 said:
Hi,
Hope I don't seem like a noob in asking this question, In the fallout ROM under Hardware information, We are using BT V3.0, Could the issue with BT not working be related somehow to this, In simple English "Is the BT on the ROM too advanced for our BT devices?, Do out BT devices support and recognise BT V3.0"
Click to expand...
Click to collapse
Acc to Lowveld, he's now managed to solve the issue (as usual) and the next update will bring fully functional bluetooth to Fallout.
Yeah, Seen that in the Fallout thread... I did PM him to ask him to see if that was a possible solution / cause to the problem, Next thing it's fixed. Wonder if it was that and I've helped him solve it or if it's just his superb ability with the ROM's. I kind of hope it was to do with the BT versions and I've game him the heads up, Just for a kind of personal satisfaction, Although I pretty much doubt it. A novice like me assisting the great lowveld
Update for those not following the Fallout thread. Fallout V2.0.0 is now release with working BT audio
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
Hi
I have read a few of the posts in the dev section and think the answer to this is a "no".
I would like to clarify though please, with those of you who are more regular on this board and have a greater knowledge.
My question is, does a ROM exist which allows for the 3D side of things to work 'and' allow the use of BT controllers?
I've read of some nice sounding ROM's but they all seem to be built of the back of the stock, so have the BT stack problem and cannot work with BT control pads.
Read of the CM7 [I think] that does allow the use of BT control pads but this one lacks the 3D side of things.
I want the best of both worlds, but believe this is not yet possible.
Just looking for confirmation please.
Also if there is development work in progress on a ROM that will include the BT control pad connections and the 3D apps, please could you name it/point me to it, so I can keep an eye on that one.
Thanks
Apparently works with 20p...untested by me though...
See below issues with bluez ime....
http://code.google.com/p/android-bluez-ime/issues/detail?id=84
Cheers, I upgraded as was on an old 2.2 froyo still.
Now on 2.3.5 with the s/w v21a
Still no luck with the BluezIME though unfortunately, hopefully one day I'll be able to get that working.
Thanks for info shredman