Hi all,
As the title says the callers to my Desire via my CK-7W car kit experience a bad echo of their own voice.
I found on a WinMo thread that the problem had been cured by chaging the Class of Device from 'Smartphone' to 'phone' so I routed my Desire and changed the class in the /system/etc/bluez/main.conf file to Class = 0x000200 (Phone) but no improvement.
I then got in touch with some people in the HTC Hero forum who have a CK-7W and they confirmed that they have no echo.
I then requested if someone could post the contents of their bluez folder (which is different to ours). I copied the files onto my device, rebooted and still no difference.
Then, just for a test, I deleted everything from the folder and rebooted. Again no difference but to be honest I was surprised that it still worked at all.
Where else does the Device get it's bluetooth settings from?
Bumpty bump
Just stumbled across this thread as I have the same car kit and same issue with my Desire
Been looking around and no fixes as far as I can see, maybe a rom flash will help?
I've known of similar problems with non Nokia phones using Nokia car kits. I think it's to do with an incompatability of the duplex system, in that keeps the microphone activated on the kit, when someone is speaking over the loudspeaker, resulting in feedback.
I hope that makes sense!
This was the reason I stopped using their car kits, eeven when I was still using their phones, as my wife's Sony phone would echo like hell.
I'm not sure if there is a work-a-round for this?
It's worth noting that my HTC Touch Diamond worked well with no echo at all for 18 months prior to the Desire.
Perhaps the forthcoming Froyo rom will cure the problem??
neomagik said:
It's worth noting that my HTC Touch Diamond worked well with no echo at all for 18 months prior to the Desire.
Perhaps the forthcoming Froyo rom will cure the problem??
Click to expand...
Click to collapse
lets hope so as I hate wearing an ear piece so much
Good news, the DeFrost Froyo rom has completely eliminated the echo, at least for me anyway.
Hope my Desire doesn't have this issue with my Parrot CK3200! I suffered enough with an echo when using an old Sony Ericsson
-------------------------------------
Sent via the XDA Tapatalk App
I had the same carkit and its not an issue your phone and even some Nokias have the same problem.
I did have a Blackberry Bold once that started working fine one day after I did a firmware upgrade on it though.
excatly the same problem.
I've used HTC diamond - flawlessly.
other phones - also
some issues with one of nokias - don't remember.
with desire - it is.
morover when I used BT5010 jabra headset one of my callers also complained on this echo
right now jx20 titanium - quite good, but sometimes callers are complaing that they can hardly hear me
With Android 2.2 is the same.
I had bad echo on the my desire when calling talktalk users ( myself included ) , this was just using my phone , in the normal way .. with out headset etc...
This seams to resolve itself last week and have not had any trouble since ...
Herbert188 said:
With Android 2.2 is the same.
Click to expand...
Click to collapse
This possibly will not help!, but....
I too have a Nokia CK7W car-kit, used with all my Nokias over wired and BlueTooth connectivity, and no problems. My Desire (s/w 2.1) would connect okay, but my CALLERS or CALLED PARTIES would ALWAYS get "echo" from whatever they were saying. I neither heard that echo, nor did I "suffer" with the same problem when I was speaking. It was ONLY my called parties, or callers. Desire worked fine with other bluetooth units (earpieces) - Jabra BT5020 and Jabra BT500.
Spoke with HTC, but they blamed Nokia for incompatibility issues, which sounded quite possible. After all, I was using an HTC on a Nokia car-kit (although the protocols would be the same I'd have thought??).
Anyway, bottom line, since having loaded v2.20 (FroYo) the echo has gone, and all works perfect.
Cheers
HTC cannot justify blaming Nokia for incompatibility. The standalone Froyo (less HTC sense) works fine, no echo. HTC have done something in sense to cause the echo (verified in 5 different sense roms both official and none official). I might get in touch with them again and point this out!
Hi All , Im just after getting the HTC Desire HD and am trying to use it with my nokia CK-7W and all my callers report this echo. I am running latest software on the phone. Anybody have any sort of a workaround for this?
Hi, I have Desire Z with latest version of Android (2.2.1) and I have same issue with bad echo ...
Do you have any idea for fix?
Any news about that echo problem? I have Gingerbread 2.3.5 in a ZTE Blade and i don't to know what to do to solve that problem
Hit this subject after couple of years
Thanks to the Tapatalk app on iPad
But still using this carkit.
So:
Works flawlles With :
- iphone 4s
- galaxy advance i9070
In past - htc desire with cm7 - also great
Aditional hint:
Keep volume of carkit low.
Increase radio volume instead.
Related
Hello all
I have been using it with the Pocket PC version of Skype on my Orbit without any major problems. The general running of the app is sometimes slow due to its minimum requirement of a 400mhz processor, and the Orbit running at 186mhz as reported my omapclock (or 200mhz as O2 claim -what is the deal with that?). However, audio quality is fine, and calls can be made without problem. In short, it works.
However, I actually noticed a degredation in performance after installing this BETA version until I overclocked my Orbit to 264mhz (again using omapclock). Prior to this, the interface would often hang and stall, resulting in me getting fed up and resetting! It's strange that a version optimised for 200mhz would work at a lower level of performance on 186mhz than something designed for 400mhz.
Another observation is that I can't get audio to route to the ear speaker, only the rear speaker on the telephone...perhaps this issue isn't as model specific as first thought, so let's hope this is addressed.
Have any other O2 XDA Orbit users had similar experiences?
Yes - I also have the problem that only the rear hands-free speaker works with Skype (O2 XDA Orbit) . Tried the new Beta and the one from the day before (2.1?).
The new beta worked ok - but had some dropouts. No overclocking.
The version before worked fine without overclocking, after disabling 3 codecs in the registry.
@ Osussat: Did your "normal" speaker worked with the version you used before this beta?
StiflersMom: I always assumed it did...However, I'm now unsure...Maybe I should reinstall to see...Perhaps it's always been routed through the rear speaker. Does your Orbit run at 200mhz or 186mhz like mine reports?
This is by design. there is no way to route sound to phone speaker on this platforms. You can use wired headset to overcome this issue.
StiflersMom said:
Yes - I also have the problem that only the rear hands-free speaker works with Skype (O2 XDA Orbit)....
Click to expand...
Click to collapse
No! Really? Surely that's a major flaw that should be addressed?
In a german PPC-Forum a user told me he installed the new skype version on his Orbit and can talk "normal" - not through the hands-free speaker.
And he said he didn't change something during or after installation.
That says the Skype Forum about that issue:
http://forum.skype.com/index.php?showtopic=71801
Right.. I wish that was the case..
please see this page for details:
http://www.securegsm.com/pages.php?pageid=89
StiflersMom said:
In a german PPC-Forum a user told me he installed the new skype version on his Orbit and can talk "normal" - not through the hands-free speaker.
And he said he didn't change something during or after installation.
That says the Skype Forum about that issue:
http://forum.skype.com/index.php?showtopic=71801
Click to expand...
Click to collapse
Can we use the Skype on Touch pro / att fuse ?
will we be able to use on 3g (unlimited plan) or wifi ?
both way there shouldnt be any charge correct ?
cos we talking to other person whos on skype too
Please let me know
Now before anyone goes bashing me for not searching the forum, lemme tell everyone, I've done just that. I just haven't found the answer to my problem.
I recently acquired an 8525 (which I'm loving BTW ). I have a Jawbone headset that pairs up fine with all of my phones (BB Pearl, 8125, & 8525). Only problem is, I can actually *use* the Jawbone with my Pearl and my Wizard, just not my Hermes.
I've paired, deleted, and re-paired again but to no avail. I've tried to get an actual conversation going using 3 different ROMs: AT&T's official WM6, Schaps 4.30 Full, and vp3G's 3.62 Full, but nothing works. I've reset the Jawbone more times than I can count, and I still can't use it.
ANY input on this would be GREATLY appreciated, since I actually *need* to use it for work...
BombaMyte said:
Now before anyone goes bashing me for not searching the forum, lemme tell everyone, I've done just that. I just haven't found the answer to my problem.
I recently acquired an 8525 (which I'm loving BTW ). I have a Jawbone headset that pairs up fine with all of my phones (BB Pearl, 8125, & 8525). Only problem is, I can actually *use* the Jawbone with my Pearl and my Wizard, just not my Hermes.
I've paired, deleted, and re-paired again but to no avail. I've tried to get an actual conversation going using 3 different ROMs: AT&T's official WM6, Schaps 4.30 Full, and vp3G's 3.62 Full, but nothing works. I've reset the Jawbone more times than I can count, and I still can't use it.
ANY input on this would be GREATLY appreciated, since I actually *need* to use it for work...
Click to expand...
Click to collapse
I am currently using my Jawbone with Schnaps 4.01 Lite rom and no problem. Before that I have been using all of Matt's Pandora Kitchen roms, right up to the latest and never had a problem. I ran Schnaps 4.30 Full rom too, but really can't remember if I used the Jawbone during the testing time. If someone else can't help I can flash that rom again and test the Jawbone with it too. Let me know ho wit goes.
works with vp3g3.62. no issues, didnt require anything special. Does bt radio on your 8525 work?
I have an 8525 running Schaps 4.30 with radio 1.48.00 and mine is working. I did however have to return one Jawbone because it would connect and I could hear the conversation but the mic didn't pick up my voice. I tried that one on my wife's razor and it had the same symptoms though. What radio are you running?
Using with TNT's latest ROM and no problems, however not real impressed with Jawbone so far. Most people I call say it sounds "tinny".
mthomas said:
works with vp3g3.62. no issues, didnt require anything special. Does bt radio on your 8525 work?
Click to expand...
Click to collapse
AFAIK, the BT radio works. Like I said, I can pair up with it just fine, and even see the other BT-enabled phones/devices at my job. I just can't get any type of audio from my JB. I'm currently using vp3G as well.
UPDATE: Well to be on the safe side, I tested my Jawbone on a couple other phones; sure enough it's working fine, so it's got to be something up with my poor Hermes... Any advice?
Mine Jawbone Works fine also. I remember when I first got it I was having trouble with my sound. I remember changing the audio bitrate from 48 bit to 44 bit in the advanced config utility 1.1 Also try changing the stereo setting to mono.
May help you out, hope so.
Just a quick update: I reflashed vp3G's 3.62 ROM, reset my JB and repaired it; same effect, nothing. Just to be on the safe side I paired the JB with my Wizard, BB Pearl, and a couple of phones at my store and it works as it should.
@ mthomas: I'm using 1.48.00 for my radio. Since you and I seem to have the same type of setup, did you install any other cabs that help your BT out?
Do you have another Bluetooth headset to test. Even thought it can pair ok, it only means the "data" channel is working. The problem could easily be the voice channel which is not working. If possible, may be borrow another headset to try.
That's my next idea. I think I have an old Plantronics I can charge up and test out...
*BUMP!*
Gotta keep this fresh. Funny thing I noticed though: when I have the Jawbone connected and the phone rings, I still hear it's little tone in my ear, but no audio comes or goes through. No registry edits have been made; I've even done a hard reset, re-paired and tried again, to no avail.
C'mon you guys! Why am I the only 8525/Jawbone user around here that *can't* use his Jawbone??? Help me out here...
wish i had the answer. im using the most current att radio 1.54.07.00. how did your device work w/ another headset?no additional tweaks
Okay, now I'm getting pissed.
I tried using my old Plantronics 320. It pairs fine with the Hermes, but making phone calls is a no-go.
The only thing I removed (from anyone using vp3G's 3.62 Full) was Sleuth's PTT Fix; I need PTT more than being able to re-map the button. So I doubt this is the culprit.
WTH can't I use my good Jawbone with this thing?!?!
Quick *bump*
Same Problem
I have tried everything, I can hear the calls just fine but no sound from my mic. I have paired with other phones & it works fine. Please let me know if you find a fix!!
UPDATE: I tried using a Moto H700 and a Plantronics 340-no dice. Now I'm starting to think if it's a BT stack issue...
Now I'm completely stumped. I just flashed back to the original ATT WM5 rom, paired up, SR, then made a phone call to my 8525 from my house line. Jawbone rang in my ear, sure. I answer the call, no sound.
Could there be a problem with my BT radio? And if there is, how can I be sure/troubleshoot it?
Just throwing someting into the pot. have you tried unpairing it with your other phones? I know i was trying to pair my to my wifes and it would work because it was paired to my phone. Try deleting the relationship between the other phones. Other than that if its new enough just take it back and get another
myv6mustang said:
Just throwing someting into the pot. have you tried unpairing it with your other phones? I know i was trying to pair my to my wifes and it would work because it was paired to my phone. Try deleting the relationship between the other phones. Other than that if its new enough just take it back and get another
Click to expand...
Click to collapse
Good thought... But I already did that, still no joy. In fact, I just flashed over to HTC's official TyTN rom, and still nothing. I'm going to call a friend of mine and see if I can get it to work on their 8525. Here's a good ? tho: Should it matter if it's Cingular or AT&T branded? Are there any differences in hardware between the two types? Or could it be a faulty BT radio? I'm racking my brain trying to figure this out.
Worse comes to worse, I'm sure I could exchange my Jawbone; I *do* work for AT&T so it should be okay...
Okay, here's another question: If I were to flash *ALL* the way down to the original Cingular shipped ROM, RUU_HER_Cingular_1.34.502.1_1.16.00.00_wwe_cws_ship, would this have any effect on the BT stack? I'm only asking because I can't seem to find any type of information about replacing the built-in stack (outside of the Widcomm project and that's too beta for me ATM), and I still can't understand why so many headsets that I've tried with this damned 8525 don't seem to work, but so many people here @ XDA can use theirs. There's no differences between the Cingular branded and AT&T branded models (at least hardware/software-wise), and if I pair up my trusty Jawbone with another 8525 (AT&T branded, btw), it works fine.
I know I've been going back and forth with this, but I did pay a good amount for my 8525 and I don't want it to be partially or mostly functional. Hell, if my poor Wizard can handle my Jawbone, why can't my Hermes?
BTW, thanks for all of the suggestions you guys have given me to help me with this problem. Even though none of them have worked, I still need to give props where they're due.
Hello everyone,
I'm having a problem with the RCD 510 Premium Bluetooth kit that is installed on the new VW Scirocco and its been troubling me for over 2 months now.
When I first got my Scirocco the Bluetooth connection was working fine (for 3-4 months). One day out of a sudden the Touch Pro II was not pairing anymore with the car's bluetooth kit.
At the time I was using Windows Mobile 6.1 that originally came along with the phone. I tried the basics - deleting the connection, re-pairing - with no success.
So I gave a shot at phone's factory reset - still no luck. The phone is recognized when I use the "Device Search" function on the car, it prompts me to enter the pass code provided, I do so, the phone loses the GSM signal (which of course is normal) but then suddenly I get a message on the RCD510's main screen "No bluetooth connection to phone" that lasts for about 2 seconds.
Since the problem began, I tried factory reset the phone (as I mentioned before), and tried pairing before installing even a single software, still no luck.
I tried multiple ROM's in the meanwhile (I mean third-party ROMs from this forum) and now I am using the official Windows Mobile 6.5 from HTC for my phone.
I also did many tests using third-party applications for the rSAP protocol (JetWare hands-free extension, SAPSettings, some patches and drivers found around the net here and there) even though there is native support for rSAP since the first firmware that came along with the device.
As I mentioned before, the phone was pairing fine the first 3-4 months.
Please note that this phone uses the Widcomm Bluetooth Stack - not the Microsoft one.
Any help/ideas would be greatly appreciated.
PS: I apologize for the big length of the post, but I believe the more the information I provide, the more the chances to get proper help
Sorry i cant help you but.. I want your CAR...
Any pics?
Well.. try this
Unhook the cars battery. Let it reset the radio (make sure you have the radio code if any) and try again.. maybe the radio is holding some sort of setting. Resetting to default (like with the device) might do the trick..
.
Thanks for the idea. I'm kind of worried though plugging out the battery, because there are many settings besides the radio that probably will be lost if I do so.
You know all these new cars and their complicated electronic sensors...I don't mind losing minor settings for the car that I have adjusted, my main concern is that if anything goes wrong, I will probably have issues with the car's warranty. I still have 2 and a half years of warranty.
I' will probably have a talk with the dealership before doing that.
Many thanks for your thought though
hi i like to know if pairing went okay with the 6.1 rom because if so maybe when you switch back to this rom problems are solved
Nop
Unfortunately no
It was one of the first things I tried. Switching back to the official 6.1 ROM. I actually kept it saved on my hard disk and I tried it a couple of times - I mean when I tried other ROMs from time to time - hoping it would resolve the issue.
And that's the strange of this case. I mean, it was working (pairing) fine the first couple 3-4 months when I unboxed the phone, and then out of a sudden, no pairing.
First logical thought would be that something has changed in the car's settings. But I have an Athena X7500 that pairs fine with the car up to this day. My car's dealership isn't much of a help...
Second thought - phone settings mess-up. But as stated in my original post, no factory reset helped, no switching to other ROMs, no playing around with settings.....
I'm really desperate. I'm thinking to switch to another phone, but besides this problem I'm quite satisfied with the TP2. And I do "need" Windows Mobile based phones, because I sync with Thunderbird's Lightning via BirdieSync for a long time now, and I am not willing to revert back to the horror days of MS Outlook. I carry my TB profile for over 2 years now and its customized the way it suits me for manipulating my 10+ email accounts.
Thank you very much for your reply though
Any other thoughts/recommendations?
i downloaded firmware 1.20 from volkswagen hope this will help me will try tomorrow with my laptop i am with a touch adapter connected to rns 510 no pairing with tp 2 at the moment for me the only workable solution is a duo sim with my old blackberry bold meanwhile i love he TP2 so hope i can get it to pair with my premium touch adapter volkswagen carkit any other suggestion or solutions are very welcome cheers
And that's the strange of this case. I mean, it was working (pairing) fine the first couple 3-4 months when I unboxed the phone, and then out of a sudden, no pairing.
what radio where you on first couple of months
Nice thought about the radio....but unfortunately I don't remember.
Currently I am using v4.49.25.17 that was upgraded with the latest official HTC firmware of WinMo 6.5 if I am not mistaken.
I am 90% positive though that the problem started before even upgrading, back when I was using the first release of WinMo 6.1 and the unknown version of radio, and everything was working ok at the beginning.
I know, I am not helpful at all but frankly, this problem surprises me as much as you.
You mentioned a firmware upgrade - for the RNS right? Not the RCD....
Do you by any chance happen to know if there is a firmware upgrade for the RCD510 and where can I get it from?
Thanks for your help.
looking-g:
I just realized that you are having a problem with the RNS.
Did you had this all along? I mean, did you ever managed to get it working and then it stopped, or you never had it paired?
I am just asking to see if I can be of any help...
well the problem is not with the rns 510 but with the touch adapter which come delivered as premium carkit i use to pair everything with it blackberry,s nokia,s and also a touch dual (niki) without any problem but now with my new phone the tp2 its not pairing it also never did after i fill in the pincode it gives an error message it should connect with the touch adapter my car by the way is a golf gti mk6 cheers, mark
You kind of lost me there.
What do you mean "touch adapter"? Is this a component of the RNS 510? Because I have never heard of it...
Have you determined a solution?
I just picked up a new VW Jetta with premium bluetooth and it worked the first time and not since.....
You guys are scaring me -- I have an Audi A3 TDI scheduled for delivery in January, and it'd be a bummer if its Bluetooth didn't work. FWIW, my current car has a Sony MEX-BT3700U headunit and the Tilt 2 pairs with it in both handsfree & A2DP modes.
3waygeek: You will be probably fine. I think Audi does not have anything to do with Nokia regarding building their units.
Wish you best luck with that.
Extra info
Some more information regarding the whole subject:
I found out that when I press the "Emergency Call" option on the touch screen of the RCD510 (i.e. try to call the international emergency number - 112) and then immediately end that emergency call, the next time I try to pair the Touch Pro 2, it does pair!!! But it has no signal at all, and if you try to make a call you get a "Dial up error" (or something like that, can't remember exactly)!
Any ideas what could be the reason for that?
Thanks.
Your problem is common to VW/Audi's. Chances are the car kits have the rSAP Bluetooth unit. I had exactly the same issue in my A6 using rSAP, as soon as i upgraded to wm 6.5 the problem went away.
Yes, indeed the car kit uses the rSAP profile, as well as the Phonebook Access Protocol (PBAP), but both of these protocols are supported by the TP2. Actually the rSAP functionality I believe is support in Windows Mobile 6.1 and above - I mean besides the fact that your phone's BT radio must support it in order to work correctly. (Without being entirely sure for the above comment).
And some more info for those who are willing to give an opinion:
I did eventually decided to remove the car's battery. I left the car without battery for approximately 40 minutes. Now here's the strange part: All the settings of the card indeed reset (window settings, light settings, etc) BUT the RCD510 was not affected at all by the battery removal! Yes, as weird as it might sound, the station list was there, bass/tremble customizations were there also, everything in place (regarding the radio unit always).
Side note for all those who might remove the battery from a similar VW car:
As soon as I plugged the battery back on, I had somewhere 15+ warning indicators on my dashboard turned on. From ABS malfunctions, air pressure, EPS malfunctions etc. But after rolling the car for 3m or so everything turned off. Back to normal. Probably had something to do with the electronic sensors giving proper signal to the car's "brain". Just my opinion.
Now, besides that - the fact that removing the battery didn't perform a reset of the radio (RCD510) unit, I also tried reverting my Touch Pro II to a WM 6.1 cooked ROM - don't remember which one exactly - but that didn't helped either. Same stupid error message after pairing for 2 secs: "No bluetooth connection to mobile phone".
And to confirm again: My X7500 (Athena) with a cooked WM6.1 ROM from michy still pairs and works fine. (Tested it last night, just to make sure that battery removal didn't had any side-effects)
PLEASE help me if you can. Any suggestion/recommendation will be greatly appreciated.
PS: I decided to contact the car's dealership to inform them about the whole problem. I will post soon regarding how that went...
Thanks for your time everyone...
By the way, does anyone knows the proper way to reset the RCD 510 to it's factory default settings? Besides the function that is given inside the menu itself - I already tried that. I was just wondering if there was a "hidden" way that will entirely wipe all settings/customizations from the unit....
Hi guys! I m in the same situation: Sirocco + TP2 with 6.5 from Orange. Any progress from your side? Ideas would be greatly appreciated!! Cheers, P
Unfortunately!
No friend, sorry. No news yet.
I do keep the post open hoping that someone will give me a new year's present
It's nice to know that I am not alone though
Hi!
I have a question if its possible to record incoming and outgoing calls on the Desire.
+1 !!!!
2-way phone recording need very much!
Dear All:
001.
Anybody has any positive experience with Ultimate Voice Recorder running on the HTC Desire (in the field of calls recording)?
002.
UVR on N1 seems to have problems with recording of the second party's voice, but on the US market this can actually be an "intentional" configuration/setup of the device.
003.
If same issues are present on the Desire how likely it is to get "fix" like the 2WayRecording? I have successfully used it on my TYTN2 together with Resco Audio Recorder to alleviate second party's voice recording issues.
+1 !!!!
2-way phone recording need very much!
any solution?
Desire and Ultimate Voice Recorder 2.3.4
Hi,
an "In Call Recording function" would be nice to have. I partially was succesful with the Ultimate Voice Recorder 2.3.4 which was able to record the remote person very silent, but still recognizable.
Same problems as I had with Windows Mobile 6: I used to have a T-Mobile Ameo (HTC Advantage x7501, Code name Athena) which would only record the other side's person in speaker mode.
More or less bad luck until now, as I expected Android-devices being superiour in this matter!
Greetings.
shame this, my c905 did it out of the box flawlessly
Hy guys, I just installed on my Desire (Android 2.1) something from the market called vRecoreder.
Used it once running in the background and it recorded my conversation (the recorded volume is kind low, but you understand).
Give it a try.
ps: had to uninstall all my call voice recorders that run in the background.
cnic said:
Hy guys, I just installed on my Desire (Android 2.1) something from the market called vRecoreder.
Used it once running in the background and it recorded my conversation (the recorded volume is kind low, but you understand).
Give it a try.
ps: had to uninstall all my call voice recorders that run in the background.
Click to expand...
Click to collapse
Update: it records .3gpp (hence the bad quality i think) and aparently records only incoming calls. Must test more though.
Two ways call recording is depending upon hardware construction same like wm and symbian. For example if wm, Asus and Samsung can but HTC cannot, whereas if in symbian case, Nokia can but Samsung cannot. This conclusion comes from my long experience with the aforementioned mobile phones. Have not tested with Garmin Asus android yet as it is not available in my market but believe this one can.
grandxo said:
Two ways call recording is depending upon hardware construction same like wm and symbian. For example if wm, Asus and Samsung can but HTC cannot
Click to expand...
Click to collapse
I'm sorry, but I have an exception on that theory right here.
My Touch Diamond wouldn't do a two way recording whatever I tried. Until I switched to a custom (WM6.5.1) ROM, there it worked fine. So no hardware issue, it was a ROM issue.
Sandeman1976 said:
I'm sorry, but I have an exception on that theory right here.
My Touch Diamond wouldn't do a two way recording whatever I tried. Until I switched to a custom (WM6.5.1) ROM, there it worked fine. So no hardware issue, it was a ROM issue.
Click to expand...
Click to collapse
I second this, as in a few Win Mobile threads discussed (no link at hand, sorry) there are registry values to be manipulated for successful two-way-voice recording. As far as I remember Microsoft and HTC stated that being NOT possible to record 2-way (without speaker mode), were hardware (design!) related facts and decisions made - until someone figured it out otherwise, by accident! (As a prior Win Mobile user: praise him!)
Not being able to record calls in Android phones is really sad.
The Palm system was able to do it from day one.
In fact the largest selling single piece of software for a smart phone ever is
Qmobilsoft's "Callrec" for palm.
So what does that say for a needed feature.
P.S. The Palm OS is now over 15 years old.
forcemaker said:
I second this, as in a few Win Mobile threads discussed (no link at hand, sorry) there are registry values to be manipulated for successful two-way-voice recording. As far as I remember Microsoft and HTC stated that being NOT possible to record 2-way (without speaker mode), were hardware (design!) related facts and decisions made - until someone figured it out otherwise, by accident! (As a prior Win Mobile user: praise him!)
Click to expand...
Click to collapse
It worked on my Touch Pro2 as well, but seems as though the stock rom was on there for around 10 mins i dont know if it worked out of the box or not.
AirVoice claims to be able to do this. Unfortunately in my experience it just doesn't
Hi falks!
The situation is easyer, then you think.
The hardware and the software are ready to record 2way the phone conversations. We have only one problem: we doesn't have any software, which would do it for us.
At this time is the only solution the Ultimate Voice Recorder, which records the outgoing voice perfect, and the incoming voice very quiet.
Total Recall is the other software, which could be able to do this feature, unfortunatelly it does it only under 1.6, so on our phone - HTC Desire - doesn't works.
For the moment... maybe turn the speakerphone on... and record the whole conversation with another phone! Hahaa... lmao!
is there apps for 2 way rec
or only wish centar
Sandeman1976 said:
I'm sorry, but I have an exception on that theory right here.
My Touch Diamond wouldn't do a two way recording whatever I tried. Until I switched to a custom (WM6.5.1) ROM, there it worked fine. So no hardware issue, it was a ROM issue.
Click to expand...
Click to collapse
Agreed but I had HTC Touch Cruise too and did adjust the registry value up to 5 in the Sound Categories using Memmaid software. The incoming call recording improve but very slightly indeed and is too far to compare with the clear quality from my Samsung i780 using Vito audio note in non speaker phone for both. Finally sold the HTC out and bought Asus P552w and very happy with the unit. Suggest to know and choose the right hardware from the start otherwise one has to learn how to play with registry or cooked rom and run the risk of losing warranty if does not know how to flash back the official rom.
malmosyd said:
Hi!
I have a question if its possible to record incoming and outgoing calls on the Desire.
Click to expand...
Click to collapse
No one here can confirm that Desire can do this yet. Samsung Spica and Galaxy S are reported to fail to record incoming call
I haven't seen this mentioned but has anybody been able to use a BT headset to make, receive, and control calls? I can't. I get "this feature isn't supported on the connected phone" from my Blueant Q2. I know this was an issue with the Sensation and tried installing the voicedialer.apk but the phone won't allow it to be installed. I installed Vlingo but it crashes the phone and I have to do a reset to get it back. Thoughts? Experiences?
Update. We're apparently screwed. There's no native voice dialer included in ICS. I found one that installs but it loses its connection with the headset as soon as it starts. The folks on the Vivid forum are having the same issue. I tried the apps they discussed but they didn't work either. So I guess we wait for HTC to do something.
http://forum.xda-developers.com/showthread.php?t=1562886
BarryH_GEG said:
I haven't seen this mentioned but has anybody been able to use a BT headset to make, receive, and control calls?
Click to expand...
Click to collapse
Yes... ish
I posted the same question a few days ago, but I got no reply, so I bought the phone anyway and tried. Vlingo sort of works with my jawbone earpiece. What I do not like at all is the fact that it does not confirm the command before dialling, or at least I did not figure out how to set it up properly, with the result of dialing the wrong contact in case of a misunderstanding.
I am really missing the simplicity of the blackberry voice dialler, amongst other things (mostly due, I guess, to my being a newbie with android). It was a no-brainer, whilst all the solutions I have seen for android are slightly more cumbersome.
Thanks to the other thread you linked I think I am going to try cyberon voice commander. I could save a couple of dollars/euros buying their voice dialler, but as far as I can see it needs training to attach voice tags to contacts. I don't like the idea of spending time to do that.
This seems like such a basic feature these days, why the hell hasn't it got it?!!!
this is very disappointing news. all the reviews i looked at mentioned voice dialing as a feature. and i just ordered a blueant q2. just tried using voice dial on my phone menu. awful.
i found a retail site online that says the blueant q2 is not compatible with the htc one x and identified several other bluetooth items (including blueant) that are. i decided to try the jawbone era and have it on order. not as many desirable (to me) features as the q2, but if it works, it will be a step up from nothing.
online site is htcpediadotcom. i don't know how reliable it is; first time i've looked at it.
I only just noticed yesterday that the phone would not send the bluetooth connection to the head unit in my car, even though it was connected to it.
I had to use the phones loudspeaker....
All of the Android phones in the past 2 years have worked fine!