Database Users

MDA Pro - Not ringing when I phone it :(

Dunno what is going on here - I had this problem occasionally with E200 / C500 on Orange, but not to this extent.
Sat at my desk, I suddenly get a Voicemail notification. Strange, as the phone hasn't rung. So I decide to test it.
I get NO ringtone on the phone I'm calling from. Nothing at all. Then it cuts straight to VM. (Phone is sat with full signal, and connected to UMTS network). I phoned 5 times, all with the same result.
Then I hung up the UMTS. Same thing happened.
I did a soft reset and left it in clamshell mode, and phoned again. This time I could clearly hear the ringing on the phone I was calling from, but the device didn't ring / vibrate or anything.
I opened it up and had a message "The phone operation failed" so I hit OK on this and closed it back up again. Phoned it again and this time it rang properly. I hung up before connecting, and got the "Missed call" notification.
Its not (entirely) down to being connected to UMTS - as my phone reconnects automatically as soon as it starts up.
Anyway, having dismissed the "You have a missed call" notification, I tried again. Its back to its original state now, no ringing heard on the phone you call from, and nothing on the phone itself. I only got ONE missed call notification, despite calling it around 7 or 8 times in all.
What the hell is going on here? It almost seems like the phone itself signals to the network that it is totally unreachable (hence no ringing heard by the caller).

I assume you haven't set up diverts or anything?
Get your network provider to do a test and see if they can give you any further information.
Failing that, it's possible that if you stopped the ExtROM from fully installing, it could be causing problems? Or maybe even some sort of task manager may be 'killing' the phone services?

I hadn't set any diverts, and it was the oddly random nature that was cause for concern - it worked after the soft reset, but didn't work beforehand. I can't be doing with a phone that, for its own reasons, refuses to aknowledge an inbound call! This should take precedence over anything else the "phone" is doing at the time, surely...
I've got T Mobile to send me out a reset of my profile (a text message which I delete, then power off the device) and I'll see how it goes.
I did have SBP PocketPlus installed, but no longer... I've not got much installed at all, at the moment.
Strongly considering flashing to the iMate ROM at this moment!

After removing the battery I retested. It was fine.
After writing the last post, I retested again and its broken again.
B*llocks.

The same as you my XDA Exec, oftern misses calls, ( you ring your self and hear it reing bu the phone makes no noise) i also had the same on my XDA2i, and yes removing the battery fixes it for a while.
Also mine when it looses service ( witch is oftern ) it will not go back into service until i soft reset it
John

Hmm, sorry no clue.
I have a JasJar and no-one has told me off for missing their calls. (I take quite a few from work, but rarely make any myself)
Maybe try a ROM flash, but I'm sure other Exec users are not having these problems, so it sounds like it might be something other than a ROM issue?

I've just stuck the iMate Rom on it. Was probably going to do it anyway, but didn't want to break my TomTom setup...
I'll do some testing and will repost on this thread with my findings.

I'm still getting the problem with the iMate ROm installed.
When I go to the Phone settings, it thinks I'm on the UMTS T-Mobile UK network. Now I'm sure this is fine for data, but maybe its not OK for voice, or something like that?
Can anyone let me know what they have in those settings?

Spotted this too on the Jasjar - can't pin down why though as it only appeqars to have started recently
Stu

I'm becoming certain that my data connection is effectively hogging the phone and not allowing voice traffic. I just had problems sending a text message. Every time I hit send, it failed (about 6 times) and went into drafts. To get it to sent, I hung up my active data connection and tried again, and it went immediately.
This is a nightmare, as the device HAS to perform both voice and data functions. I want an always-on data device, but the data MUST be interuptable by inbound / outbound phonecalls as well as notifications (SMS etc).

Right...
I've dropped down to GSM instead of 3G by removing the "Auto" setting from the Band option within the Phone Settings. This appears to have solved the problem.
From looking at the network, it appeared my phone was always connecting to a network called "UMTS T Mobile" (this was even displayed on the occasional incoming call that worked as the carrier). I'm certain this is what is causing the problems. After a Soft Reset, it would still connect to this, as my OTA ActiveSync connection would start up...
Having changed to GSM instead, I'm now connecting to "T Mobile UK" as my carrier - and this is allowing full inbound/outbound functionality - albeit only with GPRS data connectivity.

I'm on T-Mobile UK, and MSN Messenger will happily be interrupted when I get a voice call?
I'm lucky enough to live and work in an area where I'm only ever connected to UMTS (although the setting on my phone is "Auto"). I'm 99% certain that I can get calls every time, and having tested it just now a couple of times it's working without any problems, so there must be something that'll sort out your problem?

sub69 said:
I'm on T-Mobile UK, and MSN Messenger will happily be interrupted when I get a voice call?
I'm lucky enough to live and work in an area where I'm only ever connected to UMTS (although the setting on my phone is "Auto"). I'm 99% certain that I can get calls every time, and having tested it just now a couple of times it's working without any problems, so there must be something that'll sort out your problem?
Click to expand...
Click to collapse
I'm lucky enough to live and work in an area immediately covered by whatever equipment may (or may not) be located a T Mobile's head office... :roll:
I cannot discount the possibility that they've erected a UMTS cell which they "tinker with", which may (or, indeed, may not) be causing my problems...
I guess next time I'm out of the area, and in a 3G coverage area elsewhere, I will revert and test it.
In the meantime, they've asked me to test by switching back to "Auto" and trying to phone my phone once in a while, taking note of when I call and whether I get through, and they'll endeavour to trace those calls and find out what is going on...

I hope you'll be sending them an invoice!?!

I have this problem now. I only noticed it after a ROM upgrade (to the latest TMUK ROM). What fixed your problem in the end?

Hi All
I have had a very similar problem and have been discussing it in a separate thread.
http://forum.xda-developers.com/viewtopic.php?t=62863
As you will see, it seems to me that it is a T-Mobile issue, but they don't acknowledge that it is a fault. I don't get the same problem when I put an O2 sim in my Exec.
Other than downgrading to GPRS, I don't think there is any fix.
Mark

Mark, I've had a thought. Do you (like me) have an old 5v T-Mobile SIM.
These SIM’s can be identified either by SIM serial number 893044 05 or 16 – up to and including 893044 50. SIMs with serial numbers 893044 52 and above will be ok- anything lower is likely to be a 5v.
There was an issue when I 1st got my MDA Pro. It had to be network unlocked by T-Mobile for it to work with my SIM. Is it possible that the ROM update as "re-awakend" this problem?
(Also posted in thread you link to)

Thanks for the idea, Slave1, but I don't think that is the cause of the problem. My SIM doesn't have a serial number anything like those you suggested (it starts 060080...) and I only got it a couple of months old and so I am sure that it is a 3G one.
However, now that you mention it, I did have a problem getting the SIM to work when I first got it. I had to get on to Customer Services to get them to register it on the network becuase, they said, the shop hadn't registered it correctly!
Mark

mburgin said:
and I only got it a couple of months old and so I am sure that it is a 3G one.
Click to expand...
Click to collapse
All SIMs are usable with 3G (it's the handset that make the difference)
mburgin said:
I did have a problem getting the SIM to work when I first got it. I had to get on to Customer Services to get them to register it on the network becuase, they said, the shop hadn't registered it correctly!
Click to expand...
Click to collapse
That's a different issue but just as frustrating.
I had another though. Is anyone using a T-Mobile SIM in an XDA Exec (or just using an O2 ROM) having the same problem?
Could it be a ROM issue?

"Cannot complete the call. The Signal ma be unavailable

I sometimes get on my exec the following message when I'm hyst trying to make a REGULAR NORMAL ORDINARY phone call to any of my contacts:
"Cannot complete the call. The signal may be unavailable or the phone number may not be valid. Verify the number and try again later."
This bull**** also happened to me before ocassionaly on my old i-mate PDA2K. Driving me nuts, can't make a phone call till a soft reset is made. Making the phone flight mode on/off doesn't fix it.
WTF is wrong? Why does the machine gets confused. Today I had to make an urgent phone call and this **** happened and I lost some business. This machine is simply not as reliable as a phone.

same thing here....Imate sucks.
Ya, I'm getting the same thing here too. I miss calls and have to frequently press redial, as to redial the same number, since it incomprehensibly couldn't dial it. I've got the latest update.
Unfortunately for me, my unit is an Imate and their support "services" SUCK big time.
Paid $1000.00 dollars for this unit and get even get $2.00 service.
IMATE Sucks!

hmm
has similar problems..
using vodafone i noticed it was trying to connect to 3G et.. so i changed Band settings..
select network type to GSM instead of Auto.. i now see a nice G instead of a U next to my vodoafone connection signal thingy..
and all seems to work great again!!
let me know if that solved your problem :lol:

not so sure whether it's relevant or not, but since I removed all "hooking" applications like Smart Filter, ReDial, and calls time monitors ... etc and this issue didn't happen except once during a full month ...
I think those applications suppliers have to do more than just re-compliling their S/W to claim it's WM5 compatible!

HELP! TyTN Can't Receive Phone Calls! Only SMS!

ROM version: 1.18.255.3
ROM date: 05/30/06
Radio version: 1.03.03.10
Protocol version: 32.34.7010.01H
ExtROM version: 1.18.255.105
For the last few days, calls have not been able to come through to my TyTN. When people call my phone, there is just a message from the phone company (Telstra in this case) saying that the person has their phone switched off and a courtesy text message will be sent to tell them that they missed the call.
That text message is what I get. So I can call my phone from another number, get told it's off, then a few seconds later the message comes through to the phone!
A soft reset allows incoming calls again but this is ridiculous and SOMETIMES not doing anything works, I just have to wait and the next person who calls can sometimes get through!. Anyone have any ideas?
Network selection is Manual with Telstra selected. Network type is GSM and GSM/UMTS band is set to Auto (it was on GSM(900+1800)+UMTS(2100) but I changed it to Auto hoping it would help the problem.
Thanks!

Have you tried your sim card in an alternative phone, just to make sure it isn't a network problem?
Also, are you in a weak 3G signal area, if yes, perhaps this is happening because it is losing 3G and switching between the two types of signals. You could try selecting just GSM without UMTS (if that is an option in the settings) and see if that fixes it.

Strange, last week my issue was quite the opposite.
For some reason my "Messaging" went missing. The button configuration was still there, just no receiving of SMS and clicking on Messaging did not do anything. It was if the whole thing was uninstalled.
(I didn't play with any registry or Ext_Rom settings at the time).
A hard reset obviously fixed this.
But my situation is obviously different to yours.
I'm on Optus and am having no coverage/ or BAIC issues yet.

Well, changing the network and band to Auto seems to have fixed it so far...

I don't believe it's a phone related problem... I had similar issues with my Vodafone (UK) mobile the other week... Problem just sorted itself out after a couple of days.

Check you don't have voice diverts active. What doe the distant party caller get when they try to ring you?
Gavin.

Hi. Try pulling out the battery and putting it back in...

tatuanui said:
Hi. Try pulling out the battery and putting it back in...
Click to expand...
Click to collapse
Hmm, dude, this thread is almost a year old

Well did you try it?

LandyMan said:
Hmm, dude, this thread is almost a year old
Click to expand...
Click to collapse
Hahahaha yeah, I just realised after I posted. I'm a newbie and I just had the same problem the day before so you'll have to forgive me! Just trying to be helpful... Thanks

That's what used to happen on Telstra before they updated their network to support concurrent data and calling on NextG. Are you still using the first official Telstra ROM? Because if you are, and you are inadvertently creating a data connection then you will just receive the missed call SMS notification and no actual incoming call. I'd suggest at least the official ROM update first, and if you don't mind voiding your warranty, then go for one of the nice cooked ROMs on here
Hope it helps

I feel like such a dummy now. I only just looked at the original post date

Accept button does not work on incoming calls

I am part of a corporate group that just started using the Palm Treo Pro, through Bell. We have in excess of 30 phones across the company, and 90% of the users are unable to accept incoming calls. The calls show on the screen, the phone rings, but neither the accept soft button on the bottom of the screen or the send button on the phone will allow us to pick up the call. The call then goes to voicemail, then we get notifications that we missed a call.
The strange thing is that about 4 out of 6 calls have this happen. Then out of the blue, it will work, then the next call it will not accept it. I have done a hard reset on the phone, no third party apps running either.
Anybody else seeing this? I have yet to find any major problems with this phone through research, so are we the only ones to see this problem?

I have a Bell Treo Pro phone as well, I have never had any of these issues, I am sorry to hear.

Re: Unable to answer calls
I have had this happen multiple times. Each time I traced it down to whichever profile manager I had installed, whether it was Gprofile, PhoneAlarm, SPB Phone Suite and several others. Once I uninstalled the software no more problems answering calls. I wish that PhoneAlarm wouldn't cause this problem as the ability to automatically switch profiles based on time or appointment status was awesome - no more ringing phone when in a meeting because I forgot to mute the phone.

So the only time this issue has presented itself is with a profile manager? Nobody in our company has installed a profile manager of any kind, there may be some various third party apps, but these don't seem to make any difference. We are now thinking that we have a batch of defective phones.
Thanks for the responses!

Rich9584 said:
I am part of a corporate group that just started using the Palm Treo Pro, through Bell. We have in excess of 30 phones across the company, and 90% of the users are unable to accept incoming calls. The calls show on the screen, the phone rings, but neither the accept soft button on the bottom of the screen or the send button on the phone will allow us to pick up the call. The call then goes to voicemail, then we get notifications that we missed a call.
The strange thing is that about 4 out of 6 calls have this happen. Then out of the blue, it will work, then the next call it will not accept it. I have done a hard reset on the phone, no third party apps running either.
Anybody else seeing this? I have yet to find any major problems with this phone through research, so are we the only ones to see this problem?
Click to expand...
Click to collapse
same prob here, very fustrating!!!
bell treo also

Possibility
AFAIK, Bell Canada runs on a CDMA network? I haven't seen the band settings for a CDMA version of the Treo Pro, but I was having a similar problem with my unlocked GSM Treo Pro on the US T-Mobile network. I would dial a number, and as soon as it connected it would hang up. This happened multiple times. After some searching around, I came across a post that theorized that since the phone band settings were set to auto, and the phone was capable of detecting the 2100MhZ 3G band (used by AT&T), it was "confused" and tried to connect to that 3G band. It suggeted going into the settings, go under phone, then go to the band tab & change the network type from "Auto" to "GSM". I changed this setting, did a soft-reboot, and things have been fine ever since. While this method is obviously for the unlocked version of the phone, maybe if you set it to the specific network band for your wireless provider it might help?

ThrillHill1 said:
AFAIK, Bell Canada runs on a CDMA network? I haven't seen the band settings for a CDMA version of the Treo Pro, but I was having a similar problem with my unlocked GSM Treo Pro on the US T-Mobile network. I would dial a number, and as soon as it connected it would hang up. This happened multiple times. After some searching around, I came across a post that theorized that since the phone band settings were set to auto, and the phone was capable of detecting the 2100MhZ 3G band (used by AT&T), it was "confused" and tried to connect to that 3G band. It suggeted going into the settings, go under phone, then go to the band tab & change the network type from "Auto" to "GSM". I changed this setting, did a soft-reboot, and things have been fine ever since. While this method is obviously for the unlocked version of the phone, maybe if you set it to the specific network band for your wireless provider it might help?
Click to expand...
Click to collapse
Evidently the Palm Treo's that we are using do not have a Band tab in phone settings. Supposedly we have some replacement phones on the way from Palm, so now it will be a matter of seeing if they work or not. There's only about 25% of us that are having these problems, so there may be some hope for us yet.
Thanks for the response, though!!

I had similar probs due to a bad app install. hard reset fixed everything for me. there is also a palm support ringer update that just came out not too long ago. you can also change your cellular radio settings to check for calls more frequent.

[Q] i cant send/receive calls/texts.. HELP

I've just bought a second hand omnia 7, i put my sim card in and went straight on facebook so i assumed it was fine.. i then realised i couldnt make calls or send texts, and none of my calls went through. i tried it on a different sim and had the same problem.. HELP

I also have this problem any help? I cant make/send calls or texts but can get on G and browse the internet, could this be a problem with the setting on the phone? APN's maby? done 2 factory resets and recieved a text from windows phone saying welcome but thats all it will do....

I have the same problem, after some time. Messaging and calls stop working...

Has anyone come up with a fix for this?
I have full signal on an unlocked Omnia 7 but it is a simple case of not being able to make any calls or texts (or receive them for that matter).

Maybe they tamperd in Diagnostic Tools. I messed aroun and had a hard time restoring the radio settings. Look for diagnostic codes here you find a toon if codes to use. Hit this in your dial pad and you install and start the diagnostic tools.
##634#
You need to find the codes (cant remember em im afraid) that gives access to gsm/3G section.

Just had to look =P
- Hit *#32489# and you get to Cyphering. Mine is on
- Hit back once and you can press [5] RRC (HSPA). Mine is set to REL6
- If you back to the side where we could find the above [5]RRC option, you have below a Dual Mode setting. Mine says "Not ACT"
- When you type in *#32489# you can press back 2 times. There you can select option [7] Network settings. In there you can look if stuff is in automatic modes. Like...
[2] Band selection, mine is in automatic.
Well, there you have it. Something to compare to a working device. A hard reset won't put these values to default so you will have to look for your self. Now be carfull in there, you can do more damage if you dont acctully read what the pages says. If you understand what im saying, there should be no problems. Check out your settings and compare to mine. Se any diff just set it like i given advice on. Hope this helps..

Cheers for the advice but it hasn't helped as I have the same settings as you, another thing to add whenever I do try to make a call it comes up "00:00 Call Ended". I hope that may help someone in diagnosing the problem.

Have you tried downloading the Samsung Network Profile tool from Marketplace and then changing the Active profile to your SIM card?
Hvae you tried putting an unbranded ROM on? (even an old one as Zune will update with the unbranded ROM!!)

Same problem tried different ROMS but still have "Emergency Only".
The SIM is OK.

anybody found a fix for this problem ? im also suffering but the phone will receive texts and voice-mail on the orange network, it was on orange before i got it unlocked.
thanks hope there is help out there