7100t Shuts off During Phone Calls
 

Greetings all!

I'm just trying to get a general idea if I'm by myself on this one, or is this is happening to others.

This is the second replacement phone, so all three I've had (original, refurb 1, and refurb 2) just shut off during a phone call. I never see the error (if there is one) because it happens too randomly, and the screen is usually already asleep. The call just ends and the red light comes on then the hourglass spins for a couple minutes.

I also noticed that once it is back up, it takes an extra minute to aquire signal.

There is no common thing happening when it happens. Either I'm mobile or stationary (so it isn't having trouble handing off). And it doesn't matter who I'm talking to.

As soon as I get each unit, I immediatly put 4.0 on it. I'm using the OEM wired headset (it has happened with a bluetooth headset too). T-Mo customer care has had me replace the battery - still happens. Replaced SIM - still happens.

Is anyone else having the same troubles as me?

I haven't had this problem. I was losing calls while the unit was in the holster, but I finally realized that pressing the escape key while in holster ends a call.

This has happened to me twice in the last week on my 7100g - both times I was using my bluetooth headset.

It happened to me while i was running on 3.8 and only on bluetooth headset. Headset mic went bad before i up'd to 4.0 but will be replaced today. I guess i will find out in a week or so if it has happened or not.

This same thing happened to me, but I was on 3.8 and on speakerphone. It's happened to me again on 4.0 on speakerphone. Really embarassing.

This happened to me for the first time yesterday. I was NOT using the speakerphone or any hands-free device... just straight-up talking on my handset. But with me - I received another phone call and didnt click over - next thing I know I hear some sort of beep and then my call was dropped. I looked at the screen and there was a spinning hourglass and then it took a few seconds before it went back to the homescreen where it then had to reacquire the signal - weird and SUPER ANNOYING!

Yeah this just happened to me the screen shuts off and it restarts and you have to wait for it to aquire signal again. This is just random on any longer phone call

Has been happening to me lately too. I have 4.0 now but I never had this problem with 3.8...REALLY ANNOYING

Similar Here
 

It never happend to me until I put 4.0 on. I have had it SEVERAL times.

The probability is higher on longer calls but it has never happened on shorter calls. I thought it was cell switching but it has happened while stationary.

The anoying part is the reboot/signal acquisition time. It feels like 10 minutes when attempting to rejoin a conference call. More like 2-3.

The only thing I've noticed is that the call that I was on was NOT recorded in the log so I can't tell how long I was on each time.

Is there a debug log?

can one of you try installing the latest Cingular OS code? it happened to me twice on the T-Mobile OS 4.0 code, but i have yet to have it happen since upgrading to the latest Cingular code (there has been an update released since the 7100g was released, so if you aren't using the latest code - 4.0.0.219 - then try it).

you will need to delete vendor.xml in order to install it on a non-7100g handset (7100t, 7100x, etc). this is located in c:\program files\common files\research in motion\apploader.

Found the error
 

Well this happened at 11:30 last night, so I forget what the exact wording was, but the error code finally popped up.

It was a fatal exception error, code 30. Message queuing overflow.

I'm trying this right now. I will let you know if it happens again. Thank you very much for the suggestion!

I've been running the cingular OS on both of my 7100's since it was released. The issue is not bound to a carrier's OS, it still happens to me with the Cingular build....TMO blames it on network traffic, or BES admin pushing reboots (I'm hosted thru mailstreet).... No one seems to know.

I have the EXACT same problem and TMO told me it is the battery and they are sending me a new new one. This is my 2nd 7100t. The first one had a problem where the bottom row of keys didn't work. I didn't have this problem until I upgraded to 4.0.

I'm really losing my patience with blackberry...I have had nothing but problems.

Problems I had on my TMO 7100t,
OS 3.8, reboots when pickup call.
upgrade to OS4, Freezes / hangs during calls and needs a battery remove and insert, the reboots takes 7 minutes. Signal lost while on call and needs battery reset to get signal back.

It rebooted
 

Well the son of a you-know-what just rebooted during a phone call with the Cingular version of the software.

I have the same problem with dropped calls, spinning hourglass. Sometimes it spins for a minute or two and every thing gets back to normal with the call still showing connected for just a second maybe and then disconnecting and the phone drops back into the call log screen.

I called T-Mobile and the tech support blamed it on the blackberry unit and wanted to send me a "new" refurbished unit to swap my less than one month unit. 7 days regular ship or I pay $15 dollars for a quick ship. I felt like climbing up a wall. Opted for the 3 day quick ship at $15 bucks after the rep did a reload from the desk top and almost killed my phone. Spinned for eternity and he condemned it.

An hour later it finally came back to life. I couldnt stand loosing my blackberry for even an hour so I called TMO back and cancelled the swap. I will just suffer through it till the next software upgrade and hope it will resolve it. Wont let TMO get their paws on this baby!

Funny thing is TMO blackberry tech support did not even have a blackberry units. Go figure.

Oh and it gets better it just happened again to me after a 20 second phone call. It reboots and now the bluetooth on and off icon is gone!!!!! WTF ive tried changing themes and going into settings to restart bluetooth and no cigar. This is really starting to get on my nerves. Has anybody managed to get any word out of tmobile about a fix for this its just rediculous

Has anyone heard from RIM regarding this? Any end in sight?

I have had this problem since upgrading to 4.0. At first it only happened while using bluetooth but a few days ago I had it happen in the middle of a short call using no headset.