Hello, I have followed many of the forums to upgrade my phone to WM6.1 and it seemed I had it all working well but now I am having all sorts of trouble. I started getting patched to recorded calls when I tried calling home, so I decieded to redue my ROM. but now I can not get my camera to work and if I try to dial ##000000 or ##3424 they do nothing. THe dialing of those 2 numbers will say Dialing, then Connected then hang up, but never put me into diagnostics mode. Can anyone tell me what I have done wrong or how I might fix it? Thank you.
Am I posting this in the wrong area? Or has any one else had these types of problems?
Related
I have tried searching everywhere but i cannot find anyone with a similar problem.
I have an o2 XDA 2s which so far has been the best phone PDA i have used.
However, I have one small problem sometimes which happens about once in every ten calls i answer or dial, I cant hear anything the person on the other end is saying and they cant hear me too, althought the phone shows im connected and the call duration works as well. However, I am able to make/recieve calls as normal if i do a soft reset which takes about 2 mins, rather irritating. Has anyone had a similar experience? Its just so fustrating when the phone is such a superb phone that this rather small problem happens.
Please can someone advise me on what the best thing to do is, I have tried a hard reset but this has not solved anythinga and the problem remains.
Should i try upgrade using the upgrades provided for the XDA 2S on the o2 site? i understand this flashes the ROM or something. Is this easy to do and is there a chance of doing worse damage when flashing? also my XDA which is an O2 phone is unlocked onto all networks, i.e. orange, tmobile, vodafone, does this mean if i flash the rom that i will lose the unlocked networks and be stuck on O2? I would be very grateful if someone could advise a newby as to how i could rectify this problem on what otherwise is a superb phone.
Thanks
rio
Try keeping Bluetooth ON all the time. Check if problem still occures...
Robert
Does anyone else's Dash have troubles making or answering phone calls?
After disabling the phone radio in the comm manager (or going into flight mode), and then reactivating it, this Dash can't make or accept incoming phone calls.
The error says something along the lines of phone not ready, even though it has already reconnected to the network and has full signal strength. The only way to remedy this is to do a soft reset.
Has anyone else run across this? We are using the HTC WWE WM6 Rom. The same problem occured on the T-Mobile WM6 rom. I have also tried using both Radio Rom's, (HTC and T-Mobile) and the error occurs on both.
Bump for a response...
Has anyone else had this issue? Can someone else test on their Dash?
If not, should we try to get a warranty replacement?
I'm working with a Tilt2 running the stock euro HTC 6.5 rom
and I have an odd delay. once a call comes in and I either use
the "slide to answer" feature or if i just press the call answer button
there is a long...sometimes 10 second delay between my action and
the call actually connecting.
During this time i often miss calls and ive asked those who are calling me
what they hear and they say my phone goes silent for 10 seconds before i
answer. any ideas?
Someone else found this link, not me -- and I haven't tried it, but I have experienced similar (3 secs though and not often).
http://forum.ppcgeeks.com/showpost.php?p=458469&postcount=1
After doing this it does seem to pick up the calls a lot faster but now I'm getting a slew of various data connection errors. SOTI wont connect, my weather tab will not connect.
Thanks for the assist I'm going to try and find a happy balance between the two reg settings
Update: I was wrong initially about the reg edit fixing things. I had my wife call immediately after the edit and it seemed to fix it when I noticed the connection issues through various programs.
Well during work today I answered about 7 calls. The delay affected all of the and on all but 1 the call actually disconnected before it allowed me to speak. so i will be reversing the red edit to combat the connection issues.
So clarify a few questions I Got regarding this:
When the phone rings and I press the answer button or "slide to answer" the ringing does stop and the icon in the task bar shows a call connected. but for me and my caller we hear dead silence for 10 seconds until they either hang up or the call connections. Any ideas friends?
I'm having the same issue on my US AT&T Tilt 2. It is driving me crazy, the regedit did not fix anything for me either. Did you figure you this out at all?
Are you guys running stock or a custom ROM? I have had this issue in seven ROMS. In my case, it seems that my phone has to have the ATT Dialer to avoid this. Tried Energy Photon and Leo,Josh Koss, TPS, and Shadowline. All had this problem. I'm now on Fusion 6.0 with the ATT Dialer. Not one issue. Day before I flashed this one, I missed 19 calls at work because I couldn't get the slider to register. Tried TPC's latest last night(he uses the HTC Dialer), missed calls. Flashed ATT Stock no problem. Fusion is the only other ROM I found with an ATT Dialer.
It seems there is a conflict in the device when connecting.
Some things to try:
- remove the custom dialer (just use the WM6 dialer, but this will loose video calls)
- check if there is some call-recording software that kicks in
- does this happen when the device is off or also when it was already on?
I'm Using HTC's stock rom instead of the ATT rom. since I'm America I really would not be apposed to loosing video call from the dialer since Its not supported on my network but I'm really not sure how to change the dialer back to AT&Ts ...is this something that would have to be cooked into the rom because I cant stand AT&T's rom.
Flash a ROM that uses the AT&T dialer: problem solved.
Your options are: Stock AT&T, At0mAng, Arrupenthal, Twopumpchump roms.
So how do we go about getting a cab file of the AT&T dialer, video share and PTT packages that each individual user can apply as needed? Is this even possible and would it require uninstalling whatever dialer the chefs cooked in? I think it would be impractical to ask the chefs to make two versions of their ROMs (one for at&t tilt2 users and one for everyone else) as I have attempted to cook my own ROM and know how difficult it can be.
Thanks,
Stephen
hi
sorry. bad post
Managed to get a HTC Desire for an absolute steal of a price as the seller had managed to forget his lock pattern and hadn't set up a google mail account to bypass the lock pattern. Having used Android phones before I knew that if I could just figure out the correct combination of buttons on startup I'd be able to reset the phones to factory settings and have a working phone.
So, I quickly bought the phone, figured out the "Power+Vol Down" combination and ran a factory reset from within that menu.
The phone restarted and I went through the setup and everything seemed fine, until I tried to send a text/make a call.
When I send a text message, I get the message sending failed error and it retrys various times before the phone finally gives up and stops trying.
When I try and make a call the phone just hangs for a couple of seconds on the dialing screen, beeps and cuts off (as though I have no signal).
I assumed that the phone had been blocked, hence the seller was selling it so cheap and he had come up with this story of locking it out, but after having a play I realised the internet was working perfectly and I had full HSDPA signal. Now correct me if I'm wrong but I'd have no sort of connection if the phone had been blocked by the carrier?
I assumed this was a software issue and have updated from 2.2 to 2.3 but still the same issue. After updating, I've also realised that I am unable to change network carriers (I'm on TMobile and they now share networks with orange).
My sim works perfectly in other phones and if I put another sim in the Desire, it still has the same issues. The phone is locked to TMobile (not that I think that would matter), running the official HTC 2.3 Gingerbread release and as far as I'm aware my APN settins are all okay.
If anyone could shed any light onto what is going on here, and hopefully to a fix then it would be greatly appreciated
Thanks in adavnce
Please use the Q&A Forum for questions Thanks
Moving to Q&A
my apologies, thanks for moving me to the correct forum
Hi there.
My M9 has a strange problem where it rejects phone calls on a seemingly random basis. When I try to call the phone from a landline or another mobile it shows no sign that there's an incoming call. The phone making the call hears a ringing tone twice, and then only a beeping (like an engaged tone but with one beep longer than the other). The odd part is that it doesn't always happen. I get the occasional cold call come through, and sometimes people phoning me can get through, but at other times they can't. It seems consistent that when I'm at home in the evenings it rejects all calls. I'm sitting at home now and if I try to phone from a landline or mobile it won't get through yet the phone is showing full signal and can make calls. I've tried with WiFi and mobile data on and off and rebooting the phone to no avail. SMS messages come through fine all the time.
I've contacted my network (Virgin mobile UK) and they've issued a replacement SIM - same problem. I've tried the SIM in a Nokia and it seems to work perfectly, so I've come to the conclusion it must be the M9 causing this.
To start with I was on the stock HTC Android, and I've not got any auto-reject settings turned on (that I can see). To try and solve this I've done a factory reset via the phone, and when that didn't work I tried doing a complete wipe and installing TWRP recovery and ViperOneM9. It still rejects calls!
Anyone got any ideas? I've tried searching for this but all the posts seem to be about setting up auto rejects, or not receiving any calls at all. Are there any logs I could look at to see if the M9 is getting the call but then rejecting it without my knowledge? Any hints here would be appreciated!
TIA
Flash the stock firmware via SD card method. It seems like a cliché but it really solves most problems both software and hardware. If it doesn't then you know you have bigger issues.
I'd place a bet that you have a rogue app abusing it's call permissions but it'd take ages to find it.
shivadow said:
Flash the stock firmware via SD card method. It seems like a cliché but it really solves most problems both software and hardware. If it doesn't then you know you have bigger issues.
I'd place a bet that you have a rogue app abusing it's call permissions but it'd take ages to find it.
Click to expand...
Click to collapse
Thank you. I started doing that but had some problems, so in the end I bought a new phone, and lo and behold I had the same problem as I had with the HTC, and that was when the phone was fresh out of the box before I'd installed any apps.
After a LOT of playing around with settings, I've now figured out that if I have 4G turned on when I'm at home then all calls are rejected, even if WiFi is also turned on. Forcing the phone to use 3G when I'm at home means I get calls, and if I have 4G turned on when I'm at work I get calls OK. I guess the test with the Nokia worked OK as it wasn't a 4G phone.
After repeated calls to Virgin they've finally admitted that there's a fault on the phone mast close to my house, and by the sounds of it they have a lot of open tickets for that mast. As they use EE's network they say they can't do anything until EE pull their finger out, but as I've had the issue for months I bet it won't be anytime soon. For now I'll have to switch to 4G manually whenever I'm away from home and try to remember to put it back to 3G when I get back. Not ideal but at least I know what the problem is now!
Thanks for your suggestion, even though it wouldn't have worked in this case.