I have read many people have had problems with random phone restarts when making or receiving calls, but my issue is much more specific.
I'm surprised my Googling hasn't turned up anything on this problem, as my Touch Pro is running a stock rom (from 3 Australia), and issue was occurring before I installed any additional apps.
Issue as follows:
Model: HTC Touch Pro T7272 (Raph100)
ROM: 1.90.861.7 WWE
Radio: 1.02.25.19
Protocol: 52.33.25.17U
When connected to PC via USB and Windows Device Mobility Centre is active (the Vista version of Activesync), whenever an incoming call is answered, the phone restarts / reboots itself within a second of answering the call. I don't know if this also happens when making a call as I haven't tested that yet.
** Edit 1 **
I have now tested outgoing calls and the phone does not reboot / restart, so this problem is limited to incoming calls only.
** Edit 2 **
Restart also occurs when mail is syncronising over a GPRS/EDGE connection and an incoming call occurs. Appears issue is somehow related to Activesync or mail send/receive (in this case it was an IMAP mail account).
** Edit 3 **
I've found another reference to perhaps the same issue at http://forum.xda-developers.com/showthread.php?p=2827920 where the phone would reboot within 30 seconds or so of making a call when roaming. My house (the only place I've seen this issue now that I think of it), is in a roaming area for my carrier, so this may be the same issue. Mine definitely only reboots during a mail send / receive though (not sure if normal data transfer will cause this - haven't tested yet).
** Edit 4 **
Reboot occurs during ANY data transfer on EDGE/GPRS when an incoming call occurs. Tested by updating weather whilst calling phone from landline. It appears the Raphael doesn't know how to handle the fact that Voice and Data aren't supported on GPRS/EDGE simultaneously, so it just poos itself and reboots. Although I originally thought this was somehow related to an active WMDC connection via USB, my phone must have been syncronising mail via the GPRS/EDGE connection (as I'm roaming here), even though it was plugged in to the PC. I have now confirmed that so long as data isn't being transmitted via GPRS, calls can be received or made whilst it is plugged in via USB and Activesync/WMDC is active.
** End Edit **
As I do more tests I'll add more information to this post.
I'm experiencing the same problem here also.... I'm with 3 and when the phone is roaming on the Telstra network, it will reboot within 30 or so seconds of receiving an incoming call.
Just want to add that I can reliably crash the phone if I make an outgoing call whilst roaming (easily done, my house is in a roaming area for 3), and I go into my mail client and select send/receive... bang... restart.
Another 3 customer with same issue
Hi guys.. Just wanted to drop myself in as another user with the same issue.
I thought it was a doa handset and took it back but new one doing the same thing (when roaming)
Has anyone tried any other rom on it?
Cheers
I have a colleague with the same phone and ROM as me, so I will test with his device today to see if the same thing happens. I suspect the Network 3 Radio stack is dodgy, so I'll be letting 3 know about this as soon as I confirm whether this is happening on my friend's phone.
There's another person having this issue here;
http://www.1800pocketpc.com/2008/03/19/auto-disconnect-gprs-on-ppc.html
He says
# Marko Says:
October 5th, 2008 at 11:48 am
how do i hack the registry, so that when an incoming call is received, to turn of GPRS.
I have a problem with my network, when GPRS is downloading, and an icoming call is received -> the device restarts.
Thanks
Marko
Click to expand...
Click to collapse
Okay, have now tested this with my colleague's TP (which has same ROM, Same radio, same carrier and so-forth), and his TP DOES NOT RESET under the same circumstances!
This being the case, it looks like a hard reset is the logical next step as something must have gotten buggered up somewhere along the line!
Now to look up how to hard reset these things....
I'll report back with my results.
Okay, Hard Reset fixed it.
I read somewhere in XDA-Dev that a part of the OEM setup you see when you first start the device has already been completed (either by 3 or someone else further up their supply chain). I can confirm that after the hard reset, the setup process was slightly different (longer), than what I saw when I first turned the TP on out of the box. Whether this has any bearing on things I have no idea.
I will now begin the laborious process of installing and tweaking everything as per my requirements whilst testing this restart-on-call issue in-between each step to see if the issue arose because of something I did.
I'll report back either way.
After a day, and all software reinstalled, I don't seem to have this issue anymore. I can only assume that this was due to some setting / configuration which was made by 3 or someone else up the supply chain before I received the phone, or maybe one of the configuration scripts didn't run properly when I first turned on the phone. Either way it's working now.
Codenix.
guys, just letting you all know that my phone is a non-3 HongKong edition, it has RomeOS2 on it and the latest radio. I haven't tested it in a couple of days, but since mine hasn't been "touched" by Three, I doubt it has to do with their ROM or Radio
guys, just letting you all know that my phone is a non-3 HongKong edition, it has RomeOS2 on it and the latest radio. I haven't tested it in a couple of days, but since mine hasn't been "touched" by Three, I doubt it has to do with their ROM or Radio
Edit: and my phone is still crashing.
Mine crashed again on the weekend, so either the problem was intermittent when I did my testing the other day and didn't show itself, or something I've installed since then has caused the problem.
The only thing which springs to mind is the latest version of Google Maps which I installed on the weekend, and which I had also installed prior to noticing the reboot issue before my hard restart.
Thanks for your input Sawbones - at least this confirms that there's nothing specific to the Three ROM causing this.
I surprised many more people aren't also experiencing this problem. Perhaps most people rarely roam.
I have the touch pro and use this India. I have the same problem while roaming. I have installed BlackBerry Connect and whenever i am on EDGE or GPRS, the phone crashes and reboots when I receive an email while I am on an incoming call. I haven't found a solution yet.
- Radha
Codenix said:
I have read many people have had problems with random phone restarts when making or receiving calls, but my issue is much more specific.
I'm surprised my Googling hasn't turned up anything on this problem, as my Touch Pro is running a stock rom (from 3 Australia), and issue was occurring before I installed any additional apps.
Issue as follows:
Model: HTC Touch Pro T7272 (Raph100)
ROM: 1.90.861.7 WWE
Radio: 1.02.25.19
Protocol: 52.33.25.17U
When connected to PC via USB and Windows Device Mobility Centre is active (the Vista version of Activesync), whenever an incoming call is answered, the phone restarts / reboots itself within a second of answering the call. I don't know if this also happens when making a call as I haven't tested that yet.
** Edit 1 **
I have now tested outgoing calls and the phone does not reboot / restart, so this problem is limited to incoming calls only.
** Edit 2 **
Restart also occurs when mail is syncronising over a GPRS/EDGE connection and an incoming call occurs. Appears issue is somehow related to Activesync or mail send/receive (in this case it was an IMAP mail account).
** Edit 3 **
I've found another reference to perhaps the same issue at http://forum.xda-developers.com/showthread.php?p=2827920 where the phone would reboot within 30 seconds or so of making a call when roaming. My house (the only place I've seen this issue now that I think of it), is in a roaming area for my carrier, so this may be the same issue. Mine definitely only reboots during a mail send / receive though (not sure if normal data transfer will cause this - haven't tested yet).
** Edit 4 **
Reboot occurs during ANY data transfer on EDGE/GPRS when an incoming call occurs. Tested by updating weather whilst calling phone from landline. It appears the Raphael doesn't know how to handle the fact that Voice and Data aren't supported on GPRS/EDGE simultaneously, so it just poos itself and reboots. Although I originally thought this was somehow related to an active WMDC connection via USB, my phone must have been syncronising mail via the GPRS/EDGE connection (as I'm roaming here), even though it was plugged in to the PC. I have now confirmed that so long as data isn't being transmitted via GPRS, calls can be received or made whilst it is plugged in via USB and Activesync/WMDC is active.
** End Edit **
As I do more tests I'll add more information to this post.
Click to expand...
Click to collapse
Any luck so far? I have the same issue in India. I have tried every single trick that i know off including updating the ROM and flashing a new Radio (1.02.25.28 - saw it in another thread that this is a good and stable Radio Version.). It is very annoying that everytime i receive a blackberry email when i am on a call the phone would reboot
-Radha
No luck here. I thought the reset had fixed it, but perhaps my testing wasn't very good as I had to force my phone to roam, unlike when I am at home and I'm outside my provider network area.
I'm surprised more people aren't reporting this issue though.
Surprising indeed. Not many are complaining about this it looks like. I have been searching the Internet relentlessly to see if anyone has solved this but to my bad luck there is none.
The phone crashes if i receive a call while i am updating my weather. So far i have tried the following Radios:
1.01.25.16
1.02.25.11
1.02.25.19
1.02.25.28
1.02.25.27
1.02.25.31
1.02.25.32
The phone crashes on the said problem consistently. I even recently updated my ROM to ROMeOS 1.40 and repeated the above Radio's to verify. I am able to reproduce this problem with:
* Blackberry Connect receiving emails while on the call
* ActiveSync Receiving emails while on the call
* Updating Weather
Basically any data connection being active.
I am extremely frustrated with this phone and thinking of dumping this phone and go back to my TYTN II (Kaiser) which was perfect and worked with EDGE/GPRS and BlackBerry flawlessly.
- Radha
+1 Here, tried different ROMS, different radios and even different SIM cards, I guess it's goin back......
Same here guys. Im on 3 and when I roam to Telstra GSM it dies very soon after. This is very annoying and HTC should fix this as a matter of urgency.
Rename thread to "Raphael restarts on call when roaming"
Can a moderator please rename this thread? The issue is not related to wmdc as I originally thought.
Thanks.
Codenix.
Happening to me as well (and i am trying to support 4 others in our business).
If only 3 would have some bloody coverage it wouldnt be such a problem.
Has anyone tried the new ROMs for Optus/Vodafone?
Or could it have something to do with turning on/off HSDPA?
Is there a way to stop data connections when roaming? so at least we could use it as a normal phone when roaming.
Related
Just a heads-up
I have had the Vox for a couple of weeks here in Sweden
It is being used with Active sync towards an Exchange 2003 over GPRS
I quickly noticed that suddely it was not possible to receive SMS or incoming calls, the calls just got redirected to voicemail, after a reboot the phone started working for a while again, but it kept coming back.
After a couple of discussions with HTC and the distributor (and 2 rounds to the service partner for more extensive tests only to say that the phone was fully functional...) I now know what the problem is, and I put it here to let you know.
Aparently here in sweden and the rest of the nordic coutries we use GPRS type B
See here for a spec:
http://www.gsmworld.com/technology/gprs/class.shtml
And the radio stack in S710 has trouble switching between GPRS and GSM
What they told me is that HTC are working on this, (and they better be and fast...), because without a fix GPRS is useless on this phone it could anytime hang in either GPRS or GSM mode, resutling in nonworking GPRS or (even worse) no GSM, you only notice this on the fact that incoming calls are not working, outgoing calls works.
So the only way to test is constantly call your own phone to see if it is still working.
The only fix I have found to this so far is to disable all GPRS accounts and reboot the phone...
Just thought I should share this information with you. I have a feeling that more people will experience this, and I had to do a lot of digging to get this information.
If someone else has some more information or experienced this I would love to hear about it.
Thanks for the tip.
Got my S710 yesterday evening, did the GRPS setup today afternoon and tonight got couple of calls redirected to voicemail... Yep GPRS was on (although I wasn't actually doing anything, just noticed the "E" icon for an active connection). Thought was only bad reception... Knew about the missed calls because of the SMS telling me right away somebody had called.
Anyhow, SMS were getting in... Maybe it's not related to the same problem... Hopefully was really only bad reception, but enough reception for SMS.
I'll do some more testing tomorrow. I can't afford missing work calls or I know I'm fired by listening my voicemail.
Thanks,
Ka.
Ok, time to disable the GPRS settings... Let's hope they make a bugfix soon for this.
thats really worrying. has anyone experienced this in the UK ?
The whole point of the S710 is so I can have IM and push email and phone on one tiny device with keyboard
I think this is all related to the GPRS class B, what I understand so far at least is that this is mainly a problem in the nordic counties where this is used (I may very well be misinformed, this is new to me, I have a diploma in GSM technologies from a short course but that is not even worth the paper anymore )
If a network uses Class A, this is what I am told not a problem, and Class C seems mostly useless everywhere, look at my link in my first post and read about Class C ,you will see why
Kast, that sounds like a slightly different problem, I don't get SMS or calls when this happens, you also have access to EDGE and that may not have the same problem (don't know). But it would either way be interresting to see if you experience problems.
gprs class b
The class of GPRS (class B) is parameter no to gsm provider. This is spesification on device htc s710.
I have also htc s620. Result of my testing is that this device is working on Gprs Class B. When i made sinhronzation to exchange server then you can't call my gsm number, but when my sinhro is done you can call my gsm.
The bug on htc s710 is very serios i hope that from htc make quickly patch or update to solve it !
definitely all working fine on my new S710 in the UK. Will be trying in NY next week .....
Yes I think the problem is definately in Tele2's network in Sweden but probably also the other networks hera as well as in Denmark, Norway and Finland
That is what I've been told anyway. But thanks for the info
htc-s710
gd day friends
have just tried this issue on a orange il simcard and no problems were found
i can get calls and sms while gprs is on !
thanks
Then orange has GPRS class A (I wish they had that in sweden as well then we would not have that problem here...)
I have the same problem with a HTC Tytn in Belgium with Proximus, whenever the GPRS connections is enabled, calls tend to be blocked and go directly to my voicemail. Only fix is to disable the GPRS connection and only use it to check your mail every hour or so.
If I remember rightly, All GPRS phones are class B anyway. Never come across a class A GPRS handset yet (or if i have, it was never plugged as a class A device).
what tends to happen is that the network and the phone will negotiate to suspend the GPRS connection when there have been no packets sent for a certain amount of time to save the power on the handset and the towers, and to optimise the bandwidth to accomodate as many users as possible.
Seems your network might have this suspend timeout set a little too high, or alternatively, I suppose the network infrastructure could be Class B and therefore not support it at all.
I'm sure there was a reg hack around for earlier smartphones to make the GPRS connection disconnect automatically after 30 seconds or so. seems you might have to set activesync to check avery so often and see if you can find this hack.
ubfortunately, this is always going to be an issue on GPRS/EDGE devices if you are a heavy email user....but the networks still want the handsets, so they will still be made.
Hi,
I donät think the problem is with the network timeout, I have used the similar setup with Nokia handsets and Sony-ericsson and the correctly suspend the GPRS and then resume it after a finished call. But this phone seems to hang in the GPRS mode, then network is trying to send the call to the phone but the phone is not able to pick it up.
I think you are right that the registry hack might help, have not tried that yet, don't know if it is the same in WM6 either. But I might give it a try, now I have solved it via WLan at work and no e-mail elsewhere :-/
Did a bit of testning with the registry keys found this thread
And changing the first key
DWORD CacheTime
60 - Timeout in seconds
String SuspendResume
~GPRS! - Always On
GPRS_bye_if_device_off - Timeout after CacheTime
This works, setting the timer to 30 seconds automatically disconnects the GPRS session, next is to see if the phone stops receiving calls or if it still works even with GPRS activated... Let¨s keep out fingers crossed
Solved this (at least temporarily)
The registry edit seems to solve the problem at least eough for me to receive e-mail at scheduled times and receive calls.
However this is not a final solution, still waiting for a radio update from HTC...
And there is always a risk that the phone stops working during the rime GPRS is active...
I have a s710 also. I'm having missed calls very often, people are complaining they can't reach me. Sometimes after a certain period a sms arrives that i haved missed calls.
I use GRPS constantly due to the syncing with exchange (push mail) at my work.
Is there a solution for this problem yet?
You should try the radio in the Arabic rom (do a search).
It's the latest version.
After much experimentation, i have found the following:
1. If i boot up my phone WITHOUT the USB cable attached, and i start transferring data from the internet, my phone will not allow any incoming calls. They all get sent to voicemail.
2. If i boot up my phone WITH the USB cable connected (which happens to block GPRS data), but THEN DISCONNECT the USB cable so i can activate a GPRS connection, when I start transferring data from the internet to my phone, it will pause the data transfer and allow incoming calls to ring through to the phone.
My company has C500 ( Vox in Asia named Dopod C500 ). We suffer from the same problem that everyone in this thread are talking about....hang and incoming calls blocked. The only way to solve is romove the battery to reset it.
HTC Thailand gave us the -new hope- ROM which I believe it was modified from the Arabic ROM. But no improvement.
Anyone get the solution?
MR2046 T_T
on my S710 i can receive calls but the caller cannot hear me.
but when i make a call its perfect.
I am tired of making callbacks, somebody pls help
I just started using the phone (with original ROM) in Rogers/Fido network in Toronto, and I have been getting on and off calls going straight to voice mail without the phone ever ringing (no missed call notification by the phone).
Anyone else having the problem? Is it related to the phone going to deep sleep state or polling frequency? Any tweaks or registry editing which would reduce the chance of that?
This is a serious problem for me, as I need reliability. I don't mind giving up some battery performance to correct it.
I may trying updating the GSM Radio. Will it make any difference? As I understand, updating GSM Radio only should not erase all the programs like updating OS ROM does, am I correct? I would back up before doing so.
Sorry to state the obvious, but did you accidentally set your phone to forward all calls to voicemail in setting?
sonus said:
Sorry to state the obvious, but did you accidentally set your phone to forward all calls to voicemail in setting?
Click to expand...
Click to collapse
No. And this does not happen all the time. If I make a call from the phone, then it can start to receive calls without any problem. It just happens at random. And when it happens, repeated calls will all go straight to voice mail.
And I have disabled the no answer forwarding, so it should keep ringing until the caller hangs up.
hey -
first, I'd like to say these forums are awesome! thanks for the great info.
But i am having the 'straight-to-voice mail' problem with my TC too. It doesn't happen every time, but every once and a while i get a voice mail indicator, but the phone never rang. My girlfriend actually called me 3 times in a row, 2 of which went right to mail, the third one rang. odd. So if anyone has any ideas, i would appreciate it!
Edit: I am also on Fido in Toronto. I have been looking around, and there is the suggestion that perhaps this is a problem with the 'Who Called' or 'Name display' features of voicemail, which doesnt work well with some phones. Now i am not sure if this is it - but i upgraded my VM at the same time I got the TC. Another suggestion has been that the Radio Rom doesnt work well with some netorks. Can anyone confirm/deny this? Any other ideas?
hmm - anything new on this?
For me, my workaround solution is to disable 3G - network settings changed to "GSM" instead of "Auto". Now, the calls have been very reliable with no straight to voice mail problem.
So it looks like there are some incompatibility issues with my 1.58.21.23 Radio ROM and Rogers/Fido network/3G. But I don't know where to look for a better radio ROM (other than loading everything for trial and errors).
And which radio ROM is compatible with Polaris? Only those made for Polaris or the same class of phones? It is rumored that Rogers would release Kaiser very soon, so I presume that Kaiser's Radio ROM (not OS obviously) should be compatible?
aww...i really hope it's not 3G - i guess i might as well cancel that data plan Anyway, I've disabled it, so we shall see if it remedies the problem.
Edit: for those of you who are having the same problem and want to disable 3G but still want to be able to use 3G data every once and a while, I have installed Schap's Advanced Configuration too (which is awesome, btw, and can be found by searching the forums). It has a handy feature that permits you to add 3G on/off to the comm. manager, which makes switching between GSM and 3G really easy. Just thought I'd share.
Just grabbed this thread out and update it here:
Seems the problem does not depend mandatory on using 3G or GPRS
and also not depending on the Radio version. I have noticed missed
calls with enabled 3G and with GPRS only. And I have noticed them
with Radio 1.58.23.21 and with 1.64.08.21 on bepe WM6.1 0.64 GER.
I also have a friend who confirmed he noticed missed calls on stock
WM6.0 GER from O2 germany with stock Radio 1.58.23.21. Its annoying!!
I had the same problems with my old Hermes (TyTN 1) with all ROMs
and all Radio versions also. It's a pity to seem the problem persist on
the Polaris I mean, hey, the TC is some kind of phone, isn't it?
And the main task for a phone is being able to receive a call if radio
reception is OK. Never had a standalone phone, which suffered such
problems...
Olioaglio
Hi everyone, I have been having the exact same problem on my Cruise (and no, my phone is not set to forward to voice mail). It's very odd since it seems to happen randomly. I found it resolves temporarily if i make a call then hang up.
Can anyone follow-up if switching to "GSM" instead of "Auto" resolves the issue. This has become a serious problem for me and would appreciate any help. Thanks!
UPDATE: after several days of testing, i am happy to say that i have not had any problems since swithching to GSM
Mine is not doing the same in Vancouver.bc Fido.
I've tried multiple radio roms and am gradually working my way down the list from newest to oldest. so far no difference.
Any other ideas?
sorry to resurrect an old threat.
I know many people, including myself, have been trying to find the best combination of WM6/6.1 ROM and radio ROM to eliminate the missed call problem on our wizards.
I think part of the problem is our feedback is spaced apart in many threads and there is often varying results based on carrier. For this reason, I'm creating this thread for all US T-Mobile users to post their own results with their wizards.
I'm running TNT.19199 Series V.2. I have push e-mail through activesync and GPRS always on. I'm based in NY, but I travel in NJ often and have the same results in both states.
On my first flash, I was using the US T-Mobile stock radio rom (2.25.11) and I was missing calls and not getting voicemail notifications.
I changed my radio to UK T-Mobile radio rom (2.19.11) and I thought I had good results for a few weeks, until this weekend I missed 5 calls and received voicemail notifications and text messages about 20 minutes late. I had service during this time, but no calls came in.
Any US T-Mobile users, please post your own positive and negative experiences with WM6/radio roms and missed calls.
Any other wizard users having missed call issues, I encourage you to create similar threads specific to your own carriers.
In batterystatus do you have the default minimum speed set to 143MHZ. If you do change it to 175 or higher. I have had missed calls below 175.
same here!!
im using tnt's 6.1 my ipl/spl is 3.08 and 2.71 radio.. i wasnt having any problems for about 2 weeks until this week of april.. i missed 5 calls and 9 text messages.. so im switching to 2.19 and see how that goes for about a week.. but the radios i guess usually work better depending on where you live..
Me Too
I'm in the same boat. I'm using TNT.19199 Series V.2 with push email on. I don't have GPRS always on (just when a push is needed). I missed two calls and 1 voice mail this past weekend. I never had this problem on WM 5 and the stock T-Mobile rom. I'm using radio version 2.25 here in Washington State, US.
BTW, activesync seems to run much more often that neccessary -- not just when a new email is available. Sometimes it seems that it it always phoning home. I know there have been some threads that state the "fix" for missed calls is to turn off push email but like I said it wasn't a problem on WM 5.
BTW, I do OC to 234 using BatteryStatus and default to 195 at bootup.
I'd be happy if there was some applet that could be scheduled to check for voice mail and missed calls from the t-mobile cloud. Speaking of scheduling... I wonder if this has something to do with the Notifications database? I don't know what it does exactly but I do know that activesync uses it for some of it's scheduling. Maybe we are missing some entry in the Notifications database that is scheduled to periodically check for messages, etc. I too suffer occationaly to the miriad of mesage popups related to dupe events in the Notifications database.
USE 2.19
Kojacked said:
I'm in the same boat. I'm using TNT.19199 Series V.2 with push email on. I don't have GPRS always on (just when a push is needed). I missed two calls and 1 voice mail this past weekend. I never had this problem on WM 5 and the stock T-Mobile rom. I'm using radio version 2.25 here in Washington State, US.
BTW, activesync seems to run much more often that neccessary -- not just when a new email is available. Sometimes it seems that it it always phoning home. I know there have been some threads that state the "fix" for missed calls is to turn off push email but like I said it wasn't a problem on WM 5.
BTW, I do OC to 234 using BatteryStatus and default to 195 at bootup.
I'd be happy if there was some applet that could be scheduled to check for voice mail and missed calls from the t-mobile cloud. Speaking of scheduling... I wonder if this has something to do with the Notifications database? I don't know what it does exactly but I do know that activesync uses it for some of it's scheduling. Maybe we are missing some entry in the Notifications database that is scheduled to periodically check for messages, etc. I too suffer occationaly to the miriad of mesage popups related to dupe events in the Notifications database.
Click to expand...
Click to collapse
Change to 2.19 radio. Best radio for WM6 and WM 6.1 no missed calls.
Refering to the batterystatus, if you are overclocking and use the cpu scaler function and have the minimum cpu speed below 175 you may miss calls. Not the default to 195 after reboot.
Thanks
Thanks Goofy. I'm going to try radio v2.19 in the next couple of days. I don't find any option for cpu scaler in the battery status config. Maybe I'm using an old version?
I really do think part of the problem lies with check notifications. This morning I awoke to find I was connected to edge for 12 hours. I have it set to auto-disconnect after 2 minutes of inactivity. I turned of Exchange push and guess what?!?!? It still tried to sync a minute later. I just purged 3 dupe check notifications so let's see how that works.
BTW, Anyone know where activesync keeps its log? I set log level to verbose but don't know where it keeps it? Is that just the "status" page information that it keeps?
I always had this problem with my MDA and T-Mobile, regardless of ROM. It was especially frustrating when I missed a call for a job interview because of it. Since I have switched to AT&T (several months now) it has not happened again.
I flashed my boss' phone to WM6.1 a few days ago and he is having the same problem with missed calls and missed text alerts. I just upgraded the radio to 2.19.11 and will see where this goes...
I'm having missed calls as well. Actually... they are being logged as incoming calls! Or sometimes not logged at all. I've tried 2.19.11 and 2.25.11 radio only roms. I've tried removing htc dialer and disabled smart dialing. I have tried several wm6 and wm6.1 roms, all have the same results. I have missed calls displayed under sounds and notifications. I guess I going back to wm5... sadly, I've determined wm6 just isn't made for the MDA nor will it EVER work properly with it. I guess I'm getting a T-Mobile Wing sometime soon.
update: I've gone back to wm5 for now and no more missed calls. Some advice for those insisting on keeping wm6, the tmo boring rom had the LEAST missed calls of any wm6 rom I tried along with 2.19.11 radio.
I'm having pretty much the same situation with missed calls and no voicemail notifications. I'm running 2.25.11 radio, but have used this for a long time with WM5 with no problem. The problem started when I installed TNT.19199 on my T-mo Wizard.
Has the downgraded radio worked consistently for anyone?
guags99 said:
I'm having pretty much the same situation with missed calls and no voicemail notifications. I'm running 2.25.11 radio, but have used this for a long time with WM5 with no problem. The problem started when I installed TNT.19199 on my T-mo Wizard.
Has the downgraded radio worked consistently for anyone?
Click to expand...
Click to collapse
2.25.11 worked great with WM5, but most radios miss call with WM6, except 2.19. Flash it on your phone and try it.
I found a solution... hopefully!
Alright, I hate wm5! So, i've gone back to wm6.1 and have finally figured this out. For me at least, it seems to be the GPRS/EDGE connection being active. If I disconnect, the missed calls are displayed. If data is connected, missed calls are logged as incoming calls and I get no notification. Sadly, to fix the always active connection, I've had to get rid of the exchange server and setup email manually. Also setting up a bogus server through activesync and setting schedule as "manually" should kill the constant data connection. I haven't figured out why this doesn't happen with wm5, this is so stupid! If this doesn't work for everyone, please let me know by posting your experience.
To disconnect gprs/edge automatically, use GB-SOFT Tweak. Seems to work while device is asleep too!
I'm going to bump this.
How is everyone doing with the 2.19.11? Any missed events? What rom?
I have been running this radio for a long time, shortly after i stepped into the WM6 world. Recently though after flashing the TNT WM6.1 (19199), I have been missing events, but it only seemed to start a fews weeks after the flash. There was one time where i missed events for an ENTIRE evening, it wasn't until the next morning when i soft reset my phone did the text messages and VM notifications start rolling in. i have also caught it a few other times.
It seems theres going to be no end to WM6 and the missed even problem, might have to upgrade to the 8525.
I'm using Jaguar 4.0 ROM (WM6, not WM 6.1) from here (http://forum.xda-developers.com/showthread.php?t=356683)
IPL/SPL 3.08
Radio is 2.71.11
Battery Status with CPU Scaler (min=143, Org=195, Max=260, boost=273).
Rock solid. No missed calls. Great ROM.
With
SPB Pocket Plus/Diary/Weather
Photo Plugin (kind of TMO myFaces)
Google search
VoIP
etc, etc, etc ... ~500 phone numbers
Free memory after loading 25.5M
I am running my own 6.1 cooking and am NOT having problems with missed calls. The codebase I'm using is '199 based.
I'm running 2.25.11 for the radio side and am happy with it.
Both my brother and I bought Fuze's last week and he has recently been having trouble with his.
Unfortunately I live on the opposite coast so I can't troubleshoot his phone using the hands on approach and instead will try asking here
The Problem:
After working splendidly for the past week and a half, my brother has noticed within the last two days that he cannot send or receive calls regularly. When he is able to receive a call or make an outgoing connection his call quality is significantly distorted and garbled, often ending in a dropped call. Also when people place a call to him it is often the case that the phone doesn't even ring or show up in the call logs and he is only made aware of the call if someone leaves a voicemail.
I insist to him that this is not the phones fault and instead a service problem with the fault belonging all to ATT. I remember having the same problems with my 8525.
He is adamant to the fact that something must be wrong with his Fuze / Touch Pro. He says that when he pops his sim card into his old krazr (for which the Fuze is replacing) all the problems disappear. He also insists that he has full bars and 3g service at his location.
Background:
Via mymobiler and remote desktop, I added YouTube and Live Search back to the internet tab. I added a few cities to the Weather tab using the WeatherDatabaseEditor from andreas.falke and also reverted his phone to the original Black Touch Pro theme (found here) using Diamond TF3D Config 0.6.7.
I also removed the forcecell connection registry entry to allow him to tether his phone.
I believe none of these tweaks would have caused his current problems and still believe the blame mostly falls on ATT's service.
Any advice, help, or comments into this matter would be greatly appreciated!
You could have him try flashing to a different radio just to test. They don't hard reset the device, and as long as you use another TP radio you don't need to be security unlocked.
If that doesn't work, flash back to the original radio and I would bring it in for service.
allenh said:
Both my brother and I bought Fuze's last week and he has recently been having trouble with his.
Unfortunately I live on the opposite coast so I can't troubleshoot his phone using the hands on approach and instead will try asking here
The Problem:
After working splendidly for the past week and a half, my brother has noticed within the last two days that he cannot send or receive calls regularly. When he is able to receive a call or make an outgoing connection his call quality is significantly distorted and garbled, often ending in a dropped call. Also when people place a call to him it is often the case that the phone doesn't even ring or show up in the call logs and he is only made aware of the call if someone leaves a voicemail.
I insist to him that this is not the phones fault and instead a service problem with the fault belonging all to ATT. I remember having the same problems with my 8525.
He is adamant to the fact that something must be wrong with his Fuze / Touch Pro. He says that when he pops his sim card into his old krazr (for which the Fuze is replacing) all the problems disappear. He also insists that he has full bars and 3g service at his location.
Background:
Via mymobiler and remote desktop, I added YouTube and Live Search back to the internet tab. I added a few cities to the Weather tab using the WeatherDatabaseEditor from andreas.falke and also reverted his phone to the original Black Touch Pro theme (found here) using Diamond TF3D Config 0.6.7.
I also removed the forcecell connection registry entry to allow him to tether his phone.
I believe none of these tweaks would have caused his current problems and still believe the blame mostly falls on ATT's service.
Any advice, help, or comments into this matter would be greatly appreciated!
Click to expand...
Click to collapse
I suggest he reverts back to the original theme because whenever I change my theme I cannot make calls or receive calls but when I go back to the original theme calls work perfectly. Please let us know your result.
I have a G8142 with the latest security patches/updates on AT&T.
I'm having a strange issue occur on probably one out of every two or three calls. After about 45-60 seconds of conversation, my mic will cut out. I can still hear the other person clearly. I can end the call (this is not instant - it hangs up for 3 to 5 seconds) and then call the person back and resume conversation normally.
A few notes:
It doesn't matter if I place the call or if I am called
The duration from beginning of call to cutting out fluctuates
My microphone diagnostic indicates it is working properly
The call does not seem to actually drop - it will go on for quite some time (with me able to hear the other person) until someone eventually hangs up
Calling the person back/being called back does not fix the issue (it can happen multiple times in a row with the same person/call sequence)
Signal strength is usually -80 or better
The phone functions flawlessly otherwise. There also don't seem to be any issues or drops with respect to the data connection, and SMS/MMS messages seem to get delivered immediately every time. The phone hasn't been dropped or exposed to any liquid. I have disabled some system apps (like Facebook), but none that seemingly have to do with making phone calls.
I have full bars most of the time. I force 3G+ on the phone, as the 4G+ (LTE) signal is weak in many areas. AFAIK that only affects data rates anyway.
It doesn't seem to happen as much if at all if I put the call in speaker mode. I have not used a bluetooth headset for calls to see if that fixes the issue.
Here's some things I've tried:
Rebooted the phone
Updated my IMEI with AT&T. I'm not sure if they actually did it (they stated it was "already changed") or if it makes a difference. My last phone was an unlocked Nexus 6p and did not have this issue. I did not get a new SIM for this phone.
Double-checked and redownloaded the APN settings.
I haven't tried voice calling through a third-party app, like hangouts or whatsapp, but I assume it would work just fine because it's being transmitted over data.
There is either a GSM/setting issue on my end, a settings issue on AT&T's end, or possibly a hardware issue (like a loose SIM, faulty mic, or bad antenna).
For now I'm at a loss, and any ideas would be greatly appreciated.
*** UPDATE ***
I've tried clearing the phone app cache and making sure that battery optimization is turned off for the app. I'll report back if this seems to fix it in case anyone is having a similar problem.
*** UPDATE 2 ***
That didn't work. Calls still drop intermittently. I've pretty much narrowed it down to a problem with the antenna, AT&T towers not particularly caring for the baseband firmware on this phone, or an issue with the dialer app. Performing calls over data (like Whatsapp/Hangouts/Duo) works flawlessly.
We'll see what happens if the phone app gets an update, or maybe after Sony releases the Oreo update.
For those US XZP users on AT&T or those that were considering buying this model, be aware this issue may affect you.
*** UPDATE 3 ***
Changing the mobile radio to 4G (preferred) instead of forcing 3G seems to have solved the problem.