Droid X2 Dialing Problems?

When my DX2 has been at rest, or when I reboot my phone, I can maybe make one phone call. After that when I try to either dial a number or select from my contacts it takes on average 30 seconds to a minute to dial the number (in that span of time I have probably hit the dial button seven to ten times because I am frustrated . . . much like the Power Point scenario when you slides are not advancing and when the computer finally catches up you get the 20+ slides advancing ; - ) ). My question is this . . . what is causing this and what can I do to get this revolutionary funtion called (wait for it) making a call, back? I thought it might have something to do with the number of apps a person has, or what they have running on their phone, e.g. Skpe, Weather Apps that run all the time, etc. I consider this a high priority problem and would think there is solution. As an aside, this is the very reason why I complained to Verizon when I had my HTC Droid Eris. It too, was having the exact same issue with not dialig the call immediately. So, I do not believe it is a Motorola problem. So, the question still stands, what can I do to be able to make phone calls?

Hi there loleee71. I am sure that can be quite frustrating to have this issue. Did this problem just start? A hard reset may fix this issue. First, back up your contacts either using the Backup Assistant or by using Google contacts. Usually they backup automatically to Google if sync is checked. You can check if the contacts are backed up by logging on www.google.com/contacts . Pictures are saved on SD card. After ensuring your items are backed up, perform the hard reset. Here is how: http://bit.ly/oV4Meh .
Let us know if the issue persists after the reset.
Thank you,
Lena A.
Follow us on Twitter @VZWSupport

Similar Messages

Mot Droid X2 dial pad snafu - same problem on 2nd replacement phone

I have have received two replacement phones in the last 5 days with the same problem as the original.When on a call and asked to input some numbers from the dial pad....like voicemail password, the dialer will take maybe one or two numbers and then take no more and black out. Can get it lighted again but cannot input the numbers,...like it is dead. Verizon might as well remove voicemail from its services. Serious issue. Phone is running Android 2.3.4.and System version1.3.380 MB870 Anyone else have this problem???

I thought this may be the case. There are a lot of apps where if you look at the permissions of the applications, it has full access to phone calls. It's really hard to tell if it's like a bad concoction of apps or if it's one app in particular. What I would recommend is downloading a dialer application. Just search for "Dialer" in the Market, and you should see plenty of them that have great reviews. Give 1 or 2 a shot and see if that helps the issue any. Just an idea. Maybe the only thing affected is the stock dialer.
The other option is to of course master reset and add apps slowly one by one to try and figure out which is the culprit. That is tedious, and may not give you a definitive answer in my opinion.
Post your results if you have some time.

Droid x voicemail problem

I have been having a problem with my voicemail icon not disappearing after I have cleared out all of my messages.
I have checked to see if there is a way to reset the notification, and there wasn't. I looked at the notification area and the clear button did not make it go away. There was no x button or anything at the icon. When I press and hold the icon it calls my voice mail and does not give me a option to delete it.
This is the second time around I have had this problem. I did a full system reset on my droid x and that seemed to fix the problem for a couple of days. But once I received another voicemail the icon will not go away again.
Any idea's on how to fix this or should I just call Verizon and get rid of it?

had the same problem, coming over from BB... Here is what I have found... You can do it (adding the pauses) by editing the number in the contacts list... You MUST change the keyboard layout to multi-tap.....there u will find the pause and wait keys...... The only thing about doing this is that in order to use this feature is that u have to go into contacts and select Voice Mail... You cannot use the Voice Mail Icon on the home screen... It is proprietary... I noticed the two little buttons at the bottom of the screen...(call voice mail) and (Subscibe to Visual Voice Mail)... Guess what.. If you subscribe to Visual Voice Mail you can use the Voice Mail Button on the home screen and not have to enter the paswword everyime.... Con: 2.99 month.... I subscribed to see how it works... Nice little feature.... shows who left the voice mail what time. etc....
Now there is an article over on the Motorola site about how to use the pause and wait features... I found it and wished I had bookmarked it....Do a search on "adding pause to dialing" in the support forums for Droid X... There are a few, but one had detailed instructions with pictures...
Hope this helps.

Freetalk-1200 Connect.Me speed dial problem

Just received my long awaited Connect.Me and it's been working just as I expected. The only problem I encountered was that I couldn't assing speed dial numbers to 2 of my contacts. Others work perfectly, when I click them, box of information appears to the middle of the screen, but when I click one of the two with the problem, nothing happens.
I have tried everything like resetting from the button and from the web UI, deleting and adding them again to my contacts but nothing helps. Adding new contacts works fine. I would not rather create a new Skype account for my self - nor ask these two friends to make a new account for themselves - just because of this problem. Any kind of advice is welcome
Cheers from Finland!

Skype hasn't supported speed dials in it's software for some time. It's considered a legacy feature. The use of speed dials is configured through the Freetalk Connect Me web interface, not the Skype client. You need to sign into your Connect Me device via your web browser and click on "Contacts and Speed Dials". Once there all your contacts will be listed on the left pane. Select any one of those contacts and click "ADD TO SPEED DIAL". It will assign a speed dial number incrementally on the right pane. You can change that number to a number of your choosing (0-99) at any time. That's all it takes to set up. If you recently add a contact it my not show on that list. If it doesn't sign off the client in which you added the contact or contact changes, then power cycle the Connect Me box and log back in. It should update. If it does not, the only other alternative is to do a factory reset on the unit so that it will purge the list and updated it with the latest copy. Below I attached an image of the screen, though it may take some time until it gets approved and displayed to the general public.

Droid X Contacts Problem

This problem has to do with Contacts being displayed consistently between the various APS that use them. These all worked fine and as expected until I shut down the phone. The problem started and remains after turning the phone back on. All my contacts were synced from my BlackBerry Tour by a Verizon Wireless technician at the time of the Driod X purchase.
Examples of the problems I having are:
Only a few contacts (mostly the defaults contacts I believe) are displayed when I launch the Contacts app. All Contacts was selected by default, and changing the selection to Favorites or Phone Contacts both came up empty. But when I press the Phone icon to make a call, and touch to display contacts, all my contacts are displayed correctly as Phone Contacts.
The same problem exists attempting to select a Contact to Text. It show my previous contacts that I text with. When I try to bring up my Contacts to text someone else the same few Contacts are displayed and not my Phone Contacts.
Does anyone else have this same problem?

Yes, I do think that we are all in the same boat here! I think Google has to rethink how it handles contacts, and fix this frustrating problem. Contacts on phone should be based on the phone, and not Gmail or anything else. I've never had a problem with contacts on any other phone before in my life!
There was someone who posted they do not have the same problem. My problem started after I powered down the phone I believe. All contact was proper and available when I took the phone out of the store.
I also would like it if we could post the Droid model number and OS version so we can be sure we are all talking about the device setup.
I have:
Driod X
System Version 1.13.516.MB810.Verizon.en.US
Firmware 2.1-update1
Kernel version 2.6.29
Build number VZW
I am not sure what other information is pertinent.
Thank you for all the input!!!

UCCX 7 outbound dialing, problem with area codes

Hello all,
I'm just testing the outbound dialing feature in a lab, and have run into the following problem:
I have following:
outbound configuration:
general:
Customer dialing time: start (9:00) end (21:00)
dialing prefix - 9
international prefix - 00
Local Area Code: 44
Area Codes:
44 -> Europe/London
34 -> Europe/Madrid
86 -> GMT-10 (for testing purposes, does not correspond to real China time).
Then, I upload a .CSV file into a campaign with the following information:
Jane,Smith,00447111113007
Jacky,Chan,0086611115002
Juan,Pablo,0034611114001
The dialing works, the agent receives the call, accepts it, and then the call is made.
if anyone is interested, although it has nothing to do with the question itself, the calls are translated to other extension on CUCM to be able to make a call.
The problem is that, they are all treated as in the same AREA CODE, although I have clearly defined area codes for each of those countries.
when the call appears it shows on the CAD as BAAreaCode: +00060
Therefore the calls are made through to China even when it's midnight there!!!???
I know I must be doing something wrong, but I don't know what?
Many thanks for your help,
Cheers,

Hi Aaron,
Sorry for being so late to answer you. But I've done quite a few tests last weekend and have couple traces as well.
Apparently, the first time I added area codes, I did something incorrect, although I do not know what exactly, because now I've added area codes and it partially worked.
Area code: 4420 - Europe/London with Daylight saving
Area code: 3498 - Europe/Madrid with Daylight saving
Area code: 8661 - GMT/+7 NO Daylight saving
The first two Area codes (Spain and London) were correctly identified, In traces I could even see:
this one is for Spain:
type=com.cisco.executor.QueuedExecutor,Thread=MIVR_CFG_MGR_INVOKE_NOTIFICATION-33-189,Thread priority=7,Original Thread=null,Original thread priority=5,Time=null,Exception=null 358035:
Jul 03 10:56:40.390 BST %MIVR-CFG_MGR-7-UNK:configStubImpl-replace() notified with DialingListConfig,time=2010-07-03 10:56:40.373,recordId=0,impl=class com.cisco.crs.outbound.DialingListConfig,desc=,key[137],columns[137,1,,Jacky,Chan,0086611115002,,,377,0,424,1,424,1,,1278150825843,6,0,0,0,0,0,0,0,0] 358036:
Jul 03 10:56:40.390 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getPhoneNumber: callStatus=2callResult=0lastNumDialed=0 358037:
Jul 03 10:56:40.390 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getUnformattedPhoneNumber: dlcID:138 358038:
Jul 03 10:56:40.390 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getFormattedPhoneNumber: phoneNum=0034981114001 0034981114001 358039:
Jul 03 10:56:40.390 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getFormattedPhoneNumber: intPrefix=00 localAreaCode=004420 lenAreaCode=6 include lac=true 358040:
Jul 03 10:56:40.390 BST %MIVR-SS_OB-7-UNK:numToDial=0034981114001 0034981114001 358041:
Jul 03 10:56:40.390 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getUnformattedPhoneNumber: dlcID:138 358042:
Jul 03 10:56:40.390 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: timezone=sun.util.calendar.ZoneInfo[id="Europe/Madrid",offset=3600000,dstSavings=3600000,useDaylight=true,transitions=165,lastRule=java.util.SimpleTimeZone[id=Europe/Madrid,offset=3600000,dstSavings=3600000,useDaylight=true,startYear=0,startMode=2,startMonth=2,startDay=-1,startDayOfWeek=1,startTime=3600000,startTimeMode=2,endMode=2,endMonth=9,endDay=-1,endDayOfWeek=1,endTime=3600000,endTimeMode=2]] 358043:
Jul 03 10:56:40.390 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: DST observed=true 358044:
Jul 03 10:56:40.390 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: localTimeMins=716 globalStartTime=480 globalEndTime=1410 358045:
Jul 03 10:56:40.390 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: isValidTime=true 358046:
Jul 03 10:56:40.390 BST %MIVR-SS_OB-7-UNK:CampaignMgr.getContactsFromMemory: no more in-memory contacts left for campaignID 1 358047:
As we can see, localTimeMins is 716 which is: 11:56AM. That was correct time, and in between min/max globalstart times.
And this one is for London:
getPhoneNumber: callStatus=2callResult=0lastNumDialed=0 276065:
Jul 03 10:27:41.687 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getUnformattedPhoneNumber: dlcID:130 276066:
Jul 03 10:27:41.687 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getFormattedPhoneNumber: phoneNum=00442081114002 276067:
Jul 03 10:27:41.687 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getFormattedPhoneNumber: intPrefix=00 localAreaCode=004420 lenAreaCode=6 include lac=true 276068:
Jul 03 10:27:41.687 BST %MIVR-SS_OB-7-UNK:numToDial=00442081114002 276069:
Jul 03 10:27:41.687 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getUnformattedPhoneNumber: dlcID:130 276070:
Jul 03 10:27:41.687 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: timezone=sun.util.calendar.ZoneInfo[id="Europe/London",offset=0,dstSavings=3600000,useDaylight=true,transitions=242,lastRule=java.util.SimpleTimeZone[id=Europe/London,offset=0,dstSavings=3600000,useDaylight=true,startYear=0,startMode=2,startMonth=2,startDay=-1,startDayOfWeek=1,startTime=3600000,startTimeMode=2,endMode=2,endMonth=9,endDay=-1,endDayOfWeek=1,endTime=3600000,endTimeMode=2]] 276071:
Jul 03 10:27:41.687 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: DST observed=true 276072:
Jul 03 10:27:41.687 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: localTimeMins=627 globalStartTime=480 globalEndTime=1410 276073:
Jul 03 10:27:41.687 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: isValidTime=true 276074:
As we see, localTimeMins is 627 which is: 10:27AM which is correctly between min/max globalstart times too.
But the problem started with GMT+7.
Jul 03 10:28:41.859 BST %MIVR-SS_OB-7-UNK:CampaignMgr.getContactsFromMemory: for campaignID=1 280255:
Jul 03 10:28:41.859 BST %MIVR-SS_OB-7-UNK:CampaignMgr.getContactsFromMemory: campaignID=1;#of DLC=2 280256:
Jul 03 10:28:41.859 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getPhoneNumber: callStatus=2callResult=0lastNumDialed=0 280257:
Jul 03 10:28:41.859 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getUnformattedPhoneNumber: dlcID:131 280258:
Jul 03 10:28:41.859 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getFormattedPhoneNumber: phoneNum=0086611115002 280259:
Jul 03 10:28:41.859 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getFormattedPhoneNumber: intPrefix=00 localAreaCode=004420 lenAreaCode=6 include lac=true 280260:
Jul 03 10:28:41.859 BST %MIVR-SS_OB-7-UNK:numToDial=0086611115002 280261:
Jul 03 10:28:41.859 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getUnformattedPhoneNumber: dlcID:131 280262:
Jul 03 10:28:41.859 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: timezone=sun.util.calendar.ZoneInfo[id="Etc/GMT+7",offset=-25200000,dstSavings=0,useDaylight=false,transitions=0,lastRule=null] 280263:
Jul 03 10:28:41.859 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: DST observed=false 280264:
Jul 03 10:28:41.859 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: localTimeMins=148 globalStartTime=480 globalEndTime=1410 280265:
Jul 03 10:28:41.859 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: isValidTime=false 280266:
Jul 03 10:28:41.859 BST %MIVR-SS_OB-7-UNK:CampaignMgr.getContactsFromMemory: cannot dial at this time, will be marked RETRY
It correctly identifies Etc/GMT+7 but then it calculates the localtime wrongly... It came up with 148 which is 2:28AM... and the time I was making a call GMT+0 time was around 9:28AM so GMT+7 should've been 4:28PM...
Then I tried GMT-7 too:
Jul 03 11:25:40.843 BST %MIVR-SS_OB-7-UNK:CampaignMgr.getContactsFromMemory: for campaignID=1 433346:
Jul 03 11:25:40.843 BST %MIVR-SS_OB-7-UNK:CampaignMgr.getContactsFromMemory: campaignID=1;#of DLC=2 433347:
Jul 03 11:25:40.843 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getPhoneNumber: callStatus=2callResult=0lastNumDialed=0 433348:
Jul 03 11:25:40.843 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getUnformattedPhoneNumber: dlcID:140 433349:
Jul 03 11:25:40.843 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getFormattedPhoneNumber: phoneNum=0086611115002 433350:
Jul 03 11:25:40.843 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getFormattedPhoneNumber: intPrefix=00 localAreaCode=004420 lenAreaCode=6 include lac=true 433351:
Jul 03 11:25:40.843 BST %MIVR-SS_OB-7-UNK:numToDial=0086611115002 433352:
Jul 03 11:25:40.843 BST %MIVR-SS_OB-7-UNK:CMgrUtil: getUnformattedPhoneNumber: dlcID:140 433353:
Jul 03 11:25:40.843 BST %MIVR-SS_OB-7-UNK:OutboundContactInfo:isRequestingContacts() for CSQ 2 returns true 433354:
Jul 03 11:25:40.843 BST %MIVR-SS_OB-7-UNK:OutboundContactInfo:setNrGetContactsReqSent() for CSQ 2 to 1 433355:
Jul 03 11:25:40.859 BST %MIVR-SS_OB-7-UNK:OutboundContactsRequestor before sleep 433356:
Jul 03 11:25:40.859 BST %MIVR-SS_OB-7-UNK:Dialer:printLicenses() working_resources for CSQ:2 is 0 433357:
Jul 03 11:25:40.859 BST %MIVR-SS_OB-7-UNK:Dialer:printLicenses() total_working_resources:0, OB_contacts_in_progress:0 433358:
Jul 03 11:25:40.859 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: timezone=sun.util.calendar.ZoneInfo[id="Etc/GMT-7",offset=25200000,dstSavings=0,useDaylight=false,transitions=0,lastRule=null] 433359:
Jul 03 11:25:40.859 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: DST observed=false 433360:
Jul 03 11:25:40.859 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: localTimeMins=1045 globalStartTime=480 globalEndTime=1410 433361:
Jul 03 11:25:40.859 BST %MIVR-SS_OB-7-UNK:CMgrUtil: isValidLocalTime: isValidTime=true 433362:
Jul 03 11:25:40.859 BST %MIVR-SS_OB-7-UNK:CampaignMgr.getContactsFromMemory: remaining # of in-memory contacts for campaignID 1:1 433363:
and this time it did all the way around, instead of early morning, it was 1045: 5:25PM...
I do not understand what am I doing bad... but I'm starting to think it's some kind of a bug...
and the other problem is: outbound dialer does not even take contacts out of the campaign for calling if the server's local time is not between global start time and global end time. which should not be the case, as I understand campaign times should be applied to area code local time not to server local time.
Many thanks to all,
Cheers,
George

E65 Speed dial problem

Just got a new E65 after dumping my i-mate SP5 Windows Mobile device. I seem to have a bug/problem with the speed dial functionality. The speed dials work fine when using the kepad long press method, but if I select from the on screen application I just get "Invalid phone number". Can anyone help

I managed to resolve this myself throguh trial and error. It seems that the speed dial application doesn't like spaces and brackets in the phone number (as often happens when the number is first entered in Outlook for example), whilst the long key press method doesn't care about this sort of number punctuation. Using +country-code doesn't seem to be a problem in either mode. So I just edited my stored numbers and it works fine.
Also note that the same problem exists with the number used for conference calls, and using the hot key for conference call dialing.

EOS 70D - Mode Dial problem...

Hi ... I'm Patricio from Argentina.
One week ago I received from the U.S. a Canon EOS 70D.
It worked ok until yesterday.
Since today, when I want to choose different modes with the dial mode, the camera just sets: P or A+ (auto).
- If I select A+ mode (Auto mode) or "Disabling Flash mode" or "Manual mode" .... the camera sets as A+ (Auto mode).
- If I select modes: CA, SCN, C, B, AV, TV, or P ... the camera sets as "P mode".
I have read some similar cases in other models of EOS cameras ... they recommen do a "hard reset" by removing the main battery and clock battery.
I tried to do that, but this model (EOS 70D) seems to have a battery for the date and clock ... but it is internal, It`s a rechargeable battery.
I guess as a new model, there is no more than the actual firmware, that comes from factory ... so I can`t try to update, since there is no other firmware available.
Anyone have any suggestions before taking it for service?
Thanks!
you can see what's wrong with my 70D here: (the mode selected by the dial, it's not the same on the screen)

Have you tried powering off the camera, removing the battery, waiting a minute, re-inserting the battery, and powering it back on?
The on/off switch is really puts the camera into an extended power-saving sleep mode. The camera still technically has power. When you turn on the camera again, the camera really just wakes up -- it does NOT actually re-start or reload the firmware.
If, however, you remove the batteries from the camera, you (mostly) deprive it of power. When you insert the battery and power it up it actually forces the camera to load the stored firmware again... you are in effect "rebooting" the camera when you do this -- the camera does not "reboot" simply by turning the power swtich off and on again.
I did say "mostly" deprive power when you remove the battery because there is a technicality. Depending on the camera body, most cameras have a 2nd battery used to store settings and also maintiain the date/time clock. That battery is either a removable coin size battery OR it's a built-in rechrageable battery which recharges off the regular battery. If you store the camera without a battery for too long, it will prompt you for the date & time when it powers up -- but this means the internal battery was depleted of power.
I *think* your 70D has an internal rechargeable battery. Simply leaving the batteries out over-night will not be enough. Hopefully just re-started the firmware by ejecting and re-inserting the main battery will be enough to fix the problem.
Tim Campbell
5D II, 5D III, 60Da

Droid X Text Problem

When i turn off my droid X and then turn it back on the last text from almost every text conversation on my phone is RE sent out. has anyone else had this happen is there any fixes? i am planing on bringing it down to the store and making them fix it but i dont have a lot of time so if anyone knows a quick fix let me know. Please let me know what you guys think because it is **bleep** me off.

Don't know if this is what you are experiencing as I've never encountered this problem, but I was about to post this when I saw yours.
http://m.androidcentral.com/sms-bug-what-it-and-what-you-need-do
Check that out, basically it says you may need to use a third party app from the market. Just make sure to go into your default app settings and disable notifications. Hope it helps, seems like a real PITA.

Droid Razr M Problems

I have had my droid razr m since february of this year and have had no problems. Today however, i turned on my phone and it started to update some apps due to me still being connected to the wifi at my house. I tried to stop the updates to help save data on my phone. I was unable to stop the update of the Gmail app on my phone. I then proceeded to open the app and saw that the autosync was turned off. I went to turn it on and my phone goes crazy. It started to restart itself repeatedly. Now it will not allow me to get off the lock screen and it keep trying to gain verizon wireless service but then it stays on lock screen and states no service and then tries again to regain service but it acts like it is unable to do it. Anyone know if the Gmail app update is causing this or is it something else?

According to several reviews posted on the Gmail app site, this has happened to others. Users have reported doing hard resets to correct the problem. One user said they turned off the phone's sync setting, then uninstalled the update.
Gmail - Android Apps on Google Play

BB curve 8900 dialing problem

i am facing a problem with my blackberry which was previously being used on Vodafone uk and i am in pakistan, when ever i dial a number from my contacts it adds +44 to the dialed number. how ever i have not saved any contact with +44, these all are pakistan number

Open your Call Log > press the Menu key > Options > Smart Dialing, and edit your settings there to correctly reflect your location and dialing preferences.
1. If any post helps you please click the below the post(s) that helped you.
2. Please resolve your thread by marking the post "Solution?" which solved it for you!
3. Install free BlackBerry Protect today for backups of contacts and data.
4. Guide to Unlocking your BlackBerry & Unlock Codes
Join our BBM Channels (Beta)
BlackBerry Support Forums Channel
PIN: C0001B7B4 Display/Scan Bar Code
Knowledge Base Updates
PIN: C0005A9AA Display/Scan Bar Code

Cronic voice dialing problem, PLEASE help

Hey everyone,
I'm new to posting on these forums but have been browsing for about two weeks. I recently got a Curve 8330 and loved it until this problem arose. I have researched it and cannot find a solution, and it is really starting to drive me crazy. I hope someone can help, and I would be very grateful.
Anyway, I have a Seidio Extended Battery, and a 16 gig microSD card in the phone, but I don't think either one has anything to do with the problem (it still occurs with them removed). A lot of times when the phone is idle or I am trying to make a call, the voice dialing screen pops up. At the top it says Voice Dialing, under that it says "Say a command", and then it says Listening. I believe this is the regular voice dialing screen. However, I do NOT want to use voice dialing at all. I have the side convenience keys set to lock and camera, so it does not have to do with them. This screen randomly pops up and repeats itself over and over to the point where I must remove the battery and reload. A few minutes later, it happens again. Also, when this screen is up and I'm in the middle of the call, I cannot hear the opposite party which causes further issues.
Does anyone else have this problem and/or a solution? Is there a way I can just eliminate voice dialing altogether from the phone? This thing is driving me nuts and ruining an otherwise fantastic piece of technology. Thank you very much for your responses!
Message Edited by dparker313 on 07-02-2009 05:30 PM

my phone is doing the exact same thing with the voice command popping up intermittently throughout the day. I have reinstalled the software back to the factory specs and this worked for a week or so. I have also pulled battery, changed side buttons, etc and nothing has seemed to actually fix the problem...all just patches. I have already had the motherboard replaced in this phone once and now this. I have only had the phone for maybe 2 months! Thank you for your input.

EOS Rebel SL1 Mode Dial Problems

Hi, I don't know much about cameras, but I have always wanted a nice one like this and a friend of mine told me that the SL1 was good for beginners. It arrived in the mail today and I just started to experiment and play around with it. I don't know if it's something I did by mistake or it's just an issue with the camera, but I realized the Mode Dial is not programmed correctly. To elaborate if I were to spin the dial to the A+ symbol (I'm sorry if that's not what it's called), the camera will go to the sports function. I'm sorry, but I really do no understand this and I would love it if someone could help me. Thanks!

Hmmm.
On that camera the Sports mode is directly across from the A+ (Auto) mode position.  There is a little pip as the indicator on the camera on the left side of the dial.
Are you sure you are looking at the white pip and not the power on lever as the indicator?
If so, that is the problem.
If not:
Do ALL the modes register as the one directly across from the correct one, or are they all Sports or are they random or something?
The modes are printed on a thin metal "cap" that is literally glued on top of the knob.  I know because mine fell off once and I had to glue it back on.  I suppose it is possible that they put it on backwards at the factory, but I don't think so because there was a little slot in thge knob and a tab in the cap that have to line up or else you can't set the cap in flush.
If you are reading it right and the knob is wrong you need to return the camera.

Voice dialing problem

I just activated a new Blackberry World Edition Model RBK41CG
Everything was great for the first 3 days but now the voice dialing won't
work. Everytime I push the "convenience button" I get a message that says,
"Unable to allocate audio channel. Close other applications and try
again". I can't find any info relative to this problem.
Please help. I really need voice dialing as I have failing sight.
Thanks in advance for your assistance.

I got it fixed when I found the rebbot suggestion from another posting - I gave appropriate KUDOS!!

E65 voice dialing problem

I realized that not all the contacts has a voice tag. Is this normal?

Dear François,
We should shout all together : ANY BODY FROM NOKIA THERE!!!
I had this problem once again after having discussed with you. I am in Turkey. I experienced the problem completely the same as you described in your post both with English and Turkish languages on the phone.
I think this is a problem of comptability of any of the following combinations; Phone Software / PC suite / Windows Vista / and, maybe, the silly Toshiba bluetooth stack I am bedly experiencing since I have changed my laptop for about 15 days ago. Before, it was a heaven with XP + Vidcomm bluetooth drivers.
I will try to describe my environment parameters and what happens when, just expecting that somebody from Nokia may read and bring a solution to this problem as soon as possible.
The voice dialing is dieing when you synchronize is with PC suite and try to reach text messages and calender on the phone through PC suite. The way I found to solve the problem is to turn off the synthesiser. Swicth the phone off and then swicth it on again and finally turn the synthisiser on. Here you are. It works and also with contacts. This feature is very important for me because I use this feature with my car kit since a while and I was really happy until I had this problem. It was a big comfort.
My environment, if anybody from Nokia will be interested in:
I synchronize my E65 with one Vista laptop, one XP laptop, one car kit (Parrot CK 3000) and one GPS device.
E65 software version is 3.0633.69.00 06.02.2008 RM208
PC suite versions I keep using 6.86.9.0 and 6.86.9.3.tur
NOKIA PLEASE BRING A SOLUTION TO THAT PROBLEM !!!!!
BR
Yilmaz

Droid X2 Dialing Problems?

Similar Messages

Maybe you are looking for