Database Info

VOIP software hangs phone

Hi,
I bought the Excalibur and the Vox 'cause I though it would have been great being able to place VOIP calls from my phone, using the same setup I use with my ATA.
The files to enable VOIP and MS phones have been circulating since a while, but even though I tried couple of packages I still have some issues.
The problem I have is that, for some strange reason, when the VOIP cab is installed my phone sometimes loses "Calling and receiving" capability.
Sometimes I trie to place a phone call and the phone hangs, I can only switch it off and on again. Sometimes I even have to remove the SD card otherwise it will keep doing a Reboot Loop.
Other times I receive an SMS for a missed call, as if I had been offline. When I then try to call back my phone hangs.
This bug seems to affect only the Calls and not the SMS functionality.
Has anybody experienced the same issue?
Thanks,
Ka.

I also have the same problems except for the SD rebooting.
I installed the VOIP client from the workarround posted here and I also experience the same problems:
1) phone seems to work fine until I decide to place a call, when I finish entering the numbers and I hit the Call button, the phone does nothing (not even the beep) and from that point I know that I can't place calls (dial pad doesn't even works on home screen). I have to reboot.
2) I receive SMS from missed incoming calls. If I call my S710 from another phone I get a calling tone and then the answering service, but the S710 does nothing.
I had email accounts configured and I thought this problem was from GPRS not letting GSM calls come in (as it says in other threads) but now I have no active email accounts, no GPRS traffic and it is ever worst (3 to 4 reboots a day!)
I honestly don't remember this problem before VOIP client installed.
Anyone has this simptoms???

I do have the same probs
Probably others aren't experiencing the same because they disable the VOIP when no Wifi is available. I'll try to reinstall the VOIP Cab and try that way.
Bought the S710 for it's VOIP cababilities and possibility to hook it to my PBX and finally feel the freedom of VOIP (Ok, bit exagerating but you get my point ).
Anyway, since we're two at the moment, promised to keep you posted.
Thanks for your help.
Ka.

kast did you improve your VoIP configuration tool? I once tried it, but it never worked. I gave you feedback in another thread but never heard of you

same probs too

jockyw2001 said:
kast did you improve your VoIP configuration tool? I once tried it, but it never worked. I gave you feedback in another thread but never heard of you
Click to expand...
Click to collapse
Hi there,
sorry for taking so much time. Actually been quite busy lately and well, ok, must admin left this VOIP thing a bit aside.
Anyway, would you mind trying this version, hope it will work a bit better.
Tested with the provider you sent me and it seems to work.
(This is not a Cab Install thing, been packed up in couple of minutes, please unzip it and run it from your mobile.)
I think I'll get back to this so stay tuned for some little enhancements.
Ka.

COOOL.....Works on my modded Tornado with wm06...great!!!!Thanks!!!!

Hello Kast,
After my last post, I unistalled the VOIP software from within the phone's start>Settings>Remove Programs>Sleuth's WM6VoIP
I got this message "Sleuth's WM6VoIP was not completly removed. Do you want to remove it from the list of installed programs?", I didn't remove it.
I then changed the Settings>phone>Internet Calling>"Use Internet Calling" to "Never".
Since then I haven't experienced any troubles at all and I haven't rebooted the phone for some days now! problem solved but no VoIP!
I'll try your VoIP files and see what happends.
Cheers
P.S. My setting for VoIP was "whenever available" but i had WiFi off 99% of the day. (some days even 100%).

Kenwood BT-200 Handsfree Kit

I've got a Kenwood BT-200 bluetooth handsfree car kit and have found the following issues with it;
1. Everytime a call is completed, the phone book downloads all over again and takes over 10 minutes, preventing making follow on calls till complete.
2. The received and dialed calls list doesn't work
3. Cannot initiate a call from the head unit unless the phone screen is on (was working perfectly on previous HTC Touch Cruise).
4. Unable to initiate voice dialing on Phone using Microsoft Voice Command whereas with previous HF kits it was as simple as pressing and holding the call button.
Anyone else use the same Touch Pro - BT200 combination? Or experience similar problems with other HF kits?

I have Pioneer BT unit. I can not connect, but I installed Hands-Free Config from JETware Mobile Software and it solved all my problems. There are many setting options which should help you...

Hi Pritman,
I just went through the same thing after upgrading to the Touch Pro from the Dopod 838Pro (Hermes).
There's a firmware update available for the KCA-BT200 which may well fix your issues (certainly did mine).
I created a post about this earlier today (didn't see your post here).
http://forum.xda-developers.com/showthread.php?t=440494
The firmware flash is very easy to do. You will just need a laptop with a bluetooth adaptor.
Codenix.

Kenwood have released another update.
See my other post at http://forum.xda-developers.com/showthread.php?t=440494 for details.
Codenix.

Wow, never thought I would fine anyone else with the combination of Kenwood DNX-7100, KCA-BT200 AND the touch pro. I am having similar issues.
DNX-7100 with BT100 worked fine with touch pro.
"upgraded" to BT200, and I have nothing but headaches.
I have tried two different BT200, and both have been flaky.
I have tried BT200 firmware 1.60 and 1.70, and both have been flaky.
My problem is similar to the ones you folks have been experiencing, mainly it is constantly downloading, and the interface is super sluggish when downloading. I can retrieve a name and phone number from the BT200's memory, but when I call out it will say downloading and do nothing. Sometimes it won't "pair" with the phone automatically unless I manually select my phone from the DNX-7100, and sometimes it will just drop the connection. I used the BT100 for about a year, and it was solid 95% of the time. I am running stock Telus rom, btw. I have also played around with the dip switch on the BT-200. From the shipped manual, DNX-7100 belongs in group F, which is off, off, on for dip switch 1, 2, 3. But when I searched online, some of Kenwood's info listed the DNX-7100 under group G, which has dip switch off, on, off, just to add to the confusion. I have also tried removing the "wireless stereo" profile as well as the "serial port" profile, but that fixed nothing. Lastly, just to kick me when I'm down, when it list the numbers, sometimes it list them as first name, then last name, but sometimes it list it as last name then first. This is super irritating as you can't be sure where anyone is listed ..... so far my experience with the BT200 has been nothing but horrible. I am on the verge of flashing my touch pro to a cooked ROM just to see if it is due to the stock Telus rom's bluetooth (I went back to stock as the juggalo rom I used became corrupt after a few weeks).
So, did you guys finally find a solution that worked 100% of the time?

Idea
Hi Guys, I'm glad there are more people out there with my combination.
Upgrading the BT 200 to 1.70 has improved things significantly but not as good as it would be with another handset like a Nokia N95. The download delay and sluggishness still exist.
I recall when I paired the TP, a notice came up on the TP that the BT 200 is requesting access to the phonebook or contacts and prompted me to allow or deny. I'm wondering what would happen if I deny? I do know that when I first paired the N95 with the older firmware, it wouldn't syncronise the contacts and I had to manually send the contacts to the BT 200. If this can be done with the TP, it may eliminate the constant downloading, perhaps.
Anyone else willing to try this. I may not be able to do this till later this weekend so if any of you do manage to test this before me, please post the results.
Good luck!

If you don't give it access to the phonebook, I suspect it can't download your phonebook automatically, and you would have to manually push the phonebook over, which defeats the purpose of the BT-200, effectively making it a BT-100. After trying a 2nd BT-200 for 3 days, I have given up and chalked up the BT-200 as extremely flaky, and is easily the worst purchase I have ever made as:
1) Half the time it won't pair with the phone automatically
2) The other half when it does pair, you can't dial out as half time time again when you want to make it call, it decides to do a download from your phone instead (never mind that it already "downloaded" when it paired already. Half x half = quarter.
3) Half the time when it does manage to make it call, it magically drops the bluetooth pairing and drops the call.
If you're keeping track, we are at half x half x half, which is 0.125, or this damn thing only works 12.5% of the time. This is not a time saver, nor a gadget of convenience/safety. It is the ultimate source of anxiety, danger (as you're trying to get the damn thing to work), and a big disappointment. Kenwood, shame on you for putting out such flaky products, and especially for not fixing it (look at the first post, it is from Oct 08).
I am going to return both of my BT-200 to Clutchfield, and am going back to my 99% stable BT-100. BT-100 actually is not as horrible with the TP as TP runs WinMo 6.1, which lets you push multiple phone book contacts at once (not like the older WinMo where you had to push contacts ONE BY ONE!!!). The only caveat with the BT-100 is if you need to delete or modify any contacts, you can't, and you have to delete all the entries for a particular phone and repair and push all contacts again, which takes 1 minute now as oppose to half an hour with pre-WinMo 6.1. When I buy a HU next time, I don't think I will consider Kenwood again due to:
1) Flaky software/interface.
2) Poor documentation.
3) Poor service support. Kenwood Canada actually NEVER REPLIED. I only received the auto-gen email notification indicating they received my email. Clutchfield Canada has been very supportive, and I will pay more to buy from them in the future solely due to their strong customer support.

Hi Johnnysks,
As far as the Touch Pro is concerned, I understand your frustration and totally support your argument.
On the other hand, I have tested the BT-200 with a Nokia 96 & my previous Touch Cruise, works like a dream! I've had good responses from Kenwood UK but whenever I contact HTC, I alway get vague responses, which to me suggests that Kenwood must have been making the effort but keep getting let down by HTC. Ultimately the BT-200 works with majority of the handsets out there.
I will still keep trying for a solution though as I really do like the TP and the BT-200!

I have no doubts the BT-200 works with other phones, and I know my TP works with my BT-100 flawlessly. I also know from prior personal dealings with Kenwood Canada's technical support that:
1) They're rude, have a bad attitude, and unprofessional (as my first inquiry for a different product from a year ago was met with a reply that was condescending, unhelpful, and was not even in proper English). I'll be more than happy to dig up my old email for you if you have any doubts.
2) They're not responsive. It's been over a week, and they never replied to my current inquiry regarding the BT-200 (funny. They used to be rude and unprofessional. Now they're missing in action)
Perhaps Kenwood USA, Kenwood UK, or Kenwood Japan are doing an awesome job. However, I can only go with what I have personally experienced.

Anyone find a fix for this? I have the same problems with my DNX8120. Tried Jetware, no luck, I would try BTRestore, but it won't work with .net 3. My biggest complaint is that even if it is connected via bluetooth, it won't start a call from th eheadset unless the phone is not in standby. Next biggest issue is that it drops the connection after hanging up from a call.
Very f*&%*g annoying!
FYI, worked with 2 different ETEN's

Intermec CN3 WM5 wakeup issues

Hello all, I recently purchased an Intermec CN3 running Windows Mobile 5 on the Sprint CDMA network for development purposes and am having a couple of issues. It uses EV-DO Rev A I believe which allows for simultaneous voice/data, just for the record.
The first is the device randomly wakes up and turns on the screen. This morning, when I was in the car, I would push the power button to put the device in sleep mode.. every 15 seconds the screen would pop back on. I do not know if this is due to it trying to grab email, or what. However, now that I am at work, it has not come on in a few minutes. This is all random.
The only idea is that SEVEN, a push email service, is starting data on the device and it is waking up. I tried using a config tool to have data always on and this did not fix the issue. It will wake up even when there is no new email. I also have Battery Pack Pro installed.
My second issue is, when someone calls my phone and the phone is in sleep mode it takes about 5 rings for my phone to even register a call is coming in.. when my phone rings twice, the call goes to voicemail. Is there a way to tweak WM to make this faster?
If you have any questions, please feel free to ask.

This actually reminds me of the bugs present when we ported WM5 for the Blue Angel (same exact bugs)...
It might seem that you are right on your assumption of the data transfer. Try to disable/disconnect the EVDO connection (put it in Flight mode) and see if the device still wakes up by itself.
As far as the ring delay, you may want to read through this
http://forum.xda-developers.com/showthread.php?t=258109
This is a patch that was for both Himalaya and Blue Angel, but should in theory work for other WM5 devices as it seems to be modifications to the registry rather than anything else.
Just so you know, I do not believe that the CN3 is a HTC device, but since your problem was mildly general, you got lucky
Good luck...

Thanks for the reply.
It is certainly not an HTC device however this forum has some of the most knowledgeable people around and figured I'd give it a shot.
As you stated, this is a fairly generic question probably related to software and configuration.

You could try over in the Developers Forum that Intermec just launched. It's at http://community.intermec.com.

HTC (AT&T) FUZE BT earpiece issues

I re-downloaded the new ROM for the FUZE. The first time, I noticed the change in the phone with the slider added but it became painfully obvious that my earpieces ( motorolas HS850 AND S9-HD ) don't pick up (hands-free) anymore. I have to slide the bar and hopeit pics up - that takes a few seconds also.
Seems like this second time has put some pieces I guess were missing but the BT ear piece stuff is still an issue.
I wish they never got rid of the app. I used to call hands free on the 8125. Can't stand Voice Command never gets my calls correct so I just keep it disabled. At least with the other app. I could go to each contact and "train" it to respond - had hiccups but at least it worked more than not.
I've used Andrea F's weatherdatabase to add cities to my accuweather app. on the touchflo 3D. So i'm wondering is there anything I can do about the above.
I'm running Windows Mobile 6.1 Professional.
HTC say that they are getting lots of calls on this but for now nothingas far as a fix.
Any help with the BT issue or even voice command would be greatly appreciated.
Thanks T.

Moved as not ROM Development.

[Q]Please Help! Microphone not working on incoming calls..

Hello, i need some serious help over here
What's the problem:
I own a galaxy 3 since June, a week ago i started noticing the internal mic wasn't working on some incoming calls.
Details:
First of all the problem began for no apparent reason (the phone works fine otherwise and no major updates / new apps were installed)
This started happening on the official froyo ROM which was an excuse for me to flash the Kyrillos 9.4 ROM (wiped all data / formatted sd card in the process). The problem still occurs on Kyrillos 9.4 ROM suggesting that this is not a ROM issue
I thought it was a hardware issue but the caller can hear me perfectly if i connect the headset or use the speaker Also the internal mic works fine on some incoming calls and ALL outgoing ones!
Upon further investigation i came upon 2 threads on other forums (unfortunately i can't post the urls as i am a new user, if needed pm me or search google for "Microphone not working on incoming calls") which point out that the same problem incurs on HTCs and XPERIAs. Also it happens on replacement phones (original unit shipped back after this problem), on different providers, on official and custom ROMs, on clean phones (only the stock apps installed).
This seems to happen when the phone is idle for a set period of time (unconfirmed). Fast Reboot app / manual reboot / removing battery don't fix this, however making an outgoing call seems to enable the internal mic temporarily (even if the outgoing call never connects)
When this happens apart from the mic not working on incoming calls it becomes also unresponsive for other apps (Tape-a-Talk, Skype, Soundhound etc.)
Conclusion:
It seems to me that there is bug in froyo that keeps the incoming call code from activating the microphone or perhaps there is a conflict of sorts that keeps the microphone blocked. It is highly unprobable i think that the microphone would randomly start to fail on different android phones in the exact same way, so this shouldn't be a hardware issue.
Question:
Does anyone know/guess or can produce a possible solution for this? If not, could you please suggest further testing steps to help reproduce 100% this problem in an attempt to solve it?
Any help would be greatly appreciated as this is a pain in the neck for me (and others i guess?!)
PS: Excuse the thread form, i 'm really bored of writing / reading long posts
PS 2: This is my first post, hello xda community!

samsung vibrant
I have the same problem. I flashed the phone from android 2.1 TO cyanogen 2.3 and from it TO ice cream. I had this problem even to cyanogen and only in incoming call,never in other situation.
Googling I found same information but no solution. Anyone here knows something?

Anyway I found a stupid solution....try switching to 2g( I know that it's not a solution but...). It works for me!

that's ridiculous! how can network state have anything to do with the microphone of the device? can this be related to service providers maybe a more techish member could tell us.
anyway i am on 2g already as i don't have a usim card and this happens even if data network mode is deactivated. glad you found a way out but is it really a solution? i mean you have to ditch 3g for the phone to be actually a phone...
Since we seem to be the only ones among so many to be having this problem i am seriously thinking of taking back the phone for a replacement and hope for the best...

just an update, i lost functionallity of the microphone completely earlier today. That is with outgoing / incoming calls and any app i can think of, so i thought i 'd try changing the network data setting to 3g only since i was already on 2g...
WOW!!! that had an instant effect,it works seamlessly now,didn't even have to reboot.fingers crossed it will last.
that is one nasty and very strange bug. Please any of the developers could you take a closer look at this?
much appreciated
Sent from my GT-I5800 using XDA App