Every now and then, probably after using it for a couple of days, my TC gets problems with the phone function. First, it will not notify me of incoming calls, these get diverted to the voice mail. Second, when I try to make a call, it starts to dial, but the dialing never succeeds. After a minute or so of dialing it just ends the call.
I found out the following funny thing: when it is dialing, if I push the off-button at that time, the screen goes off and the sound comes on. I'm even properly connected to the person I'm trying to call!! So the connection was already there, I just can't hear anything, neither can the other person, until I push the off-button.
This behaviour doesn't happen all the time, just after a day or so of use. The solution is to soft-reset the device, not really a solution though in my opinion. Switching the phone off and on in the comm.manager doesn't help. Is there any bettter solution? I'm using the standard dutch ROM.
Thanks! Wouter
deechte said:
Every now and then, probably after using it for a couple of days, my TC gets problems with the phone function. First, it will not notify me of incoming calls, these get diverted to the voice mail. Second, when I try to make a call, it starts to dial, but the dialing never succeeds. After a minute or so of dialing it just ends the call.
I found out the following funny thing: when it is dialing, if I push the off-button at that time, the screen goes off and the sound comes on. I'm even properly connected to the person I'm trying to call!! So the connection was already there, I just can't hear anything, neither can the other person, until I push the off-button.
This behaviour doesn't happen all the time, just after a day or so of use. The solution is to soft-reset the device, not really a solution though in my opinion. Switching the phone off and on in the comm.manager doesn't help. Is there any bettter solution? I'm using the standard dutch ROM.
Thanks! Wouter
Click to expand...
Click to collapse
Does a different radio ROM help?
I'm a bit scared for doing that... It hasn't always been like this, so I'd rather send it back I think.
deechte said:
I'm a bit scared for doing that... It hasn't always been like this, so I'd rather send it back I think.
Click to expand...
Click to collapse
If it's under warranty, do that!
deechte said:
Every now and then, probably after using it for a couple of days, my TC gets problems with the phone function. First, it will not notify me of incoming calls, these get diverted to the voice mail. Second, when I try to make a call, it starts to dial, but the dialing never succeeds. After a minute or so of dialing it just ends the call.
I found out the following funny thing: when it is dialing, if I push the off-button at that time, the screen goes off and the sound comes on. I'm even properly connected to the person I'm trying to call!! So the connection was already there, I just can't hear anything, neither can the other person, until I push the off-button.
This behaviour doesn't happen all the time, just after a day or so of use. The solution is to soft-reset the device, not really a solution though in my opinion. Switching the phone off and on in the comm.manager doesn't help. Is there any bettter solution? I'm using the standard dutch ROM.
Thanks! Wouter
Click to expand...
Click to collapse
I'm experiencing exactly the same problem since a week with bepe 0.67 rom.
Please, anyone with the same problem?
sounds a little similar to this...
http://forum.xda-developers.com/showthread.php?p=2374406
hopefully that ^ solves the problem
Thanks for your reaction. It's not the same problem though, when my problem occurs it stays. I can never make a phone call normally again anymore, nor receive a call. I have to soft reset.
Kukatrap said:
I'm experiencing exactly the same problem since a week with bepe 0.67 rom.
Please, anyone with the same problem?
Click to expand...
Click to collapse
Do you have Webis Note2Self installed?
I cloned my device's software and settings to a new one from the shelve. After a few days the problem occured again. So it's probably not a hardware problem in my case. With the problem occuring, I changed the phone settings from Auto to GSM and the UMTS settings from Auto to GSM(900+1800)+UMTS(2100), both didn't solve the problem when it was occuring.
Then I opened Memmaid and discovered there was an instance of Note2Self (Webis) under the running processes. I closed that one down and closed Memmaid and then the problem was gone!!
On their forum, other users report about audio issues. I'm looking in to this further. I'm using N2S 2.01 build 2326.
[edit]
Yes! Upgrading to version 2.03 solved my problem! Finally!
deechte said:
Do you have Webis Note2Self installed?
Click to expand...
Click to collapse
Yes, I am!!
I'll upgrade, thanks.
I had the same issue with the standard WM6 ROM thats the whole reason I changed to Diamond R4 ROm, has not happened since then. One thing I did notice is that I had my phone in my hand and it came out of sleepmode by it's self and 3 minutes later after putting it back to sleep I receive a message to say I had voice mail. Now I am thinking that the phone knew a call was comming in but it was to lazy to ring so it just sent it to voice mail. When I tried to call voice mail the phone connected but there was no sound. I had to power cycle the phone for it to work again.
Came across an interesting issue with my RAPH whilst away.
The phone would reboot when ringing, or making outbound calls, sometimes the call could be established and a conversation could be had for a random amount of time (never more than a minute) and the phone would suddenly reboot.
I fixed the issue by turning off bluetooth (might have been looking for my headset) and just changing every setting in "Phone" to something and then changing it back.
Havent had an issue since.
figured id post incase anyone else had this frustrating issue.
I guess this might be solved with a different Radio version.
what version are you in?
atreidae said:
Came across an interesting issue with my RAPH whilst away.
The phone would reboot when ringing, or making outbound calls, sometimes the call could be established and a conversation could be had for a random amount of time (never more than a minute) and the phone would suddenly reboot.
I fixed the issue by turning off bluetooth (might have been looking for my headset) and just changing every setting in "Phone" to something and then changing it back.
Havent had an issue since.
figured id post incase anyone else had this frustrating issue.
Click to expand...
Click to collapse
Are you using S2U2 by any chance?
Mine started doing it since i put S2U2 on but am not sure if its entirely to blame.
Hi all,
I have been doing further testing and can report that S2U2 is not the problem. Its a device issue that occurs when i roam to a GSM network. When on 3G its usually fine. I have just upgraded radio to the .28 to see if this helps.
Both myself and my brother who have the same devices are seeing the same issue. I have seen it on the 3 rom and also the HTC asia rom hence why im looking at radio now.
I tried Radio .32 with no luck. Tried a few different ROMS as well, ROMEoS, the HTC ASIA update as well as the updated 3 ROM with no joy. Shame cause the phone is great apart form this "showstopper", back to my ever trusty Blackjack until a new handset arrives.
I'm on NextG btw, and problem occurs when swictching between GSM, Edge and HSDPA. Unfortunatey both home and office are in spots that switch between signals depending on where I am in the house/office, very frustrating. I'm also 90% sure it only happens when a call and data are happening at the same time, as my phone syncs wth Exchange, this is regularly.
I rang HTC support, they suggested a hard reset, which of course I've done many times, otherwise return for repair/replacement.
I've noticed that on every lollipop build I've tried, in getting phone call hang ups. Sometimes 5 seconds into a call, sometimes 30. It doesn't happen on speaker. I make a conscious effort to keep the phone away from my face so I don't accidentally hang up by touching anything. Am I the only person this is happening to? Anyone else? Anyone find the root of the problem? I've tried wiping and clean flashing all the custom Roms and nothing has fixed this problem.
Also noticing in not able to connect to 5g Wi-Fi either.
Hi guys, this is a very particular problem and it's annoying the hell out of me. Can't find any reference to it anywhere.
Phone was working flawlessly until a firmware update was pushed by Samsung, taking me to the APEQ firmware version. Since then, the phone will become unresponsive whenever this scenario happens:
Connected to bluetooth (BMW 3-Series, 2015)
On an ongoing phone call
A second call comes in, but I don't answer it. I don't reject it either, I just let it ring.
Phone freezes, Loses connection to the car. Original call drops. Will become unresponsive for several minutes, or outright reboot by itself.
I've noticed that the phone app itself seems to be slow to execute any action: Start a call, blank screen for 3-5 seconds. End a call: Phone app screen frozen, phone unresponsive for 3-5 seconds.
I haven't rooted my phone, but I've rooted all my android devices in the past, so I'm not a stranger to it.
Any suggestions? I'd like to avoid flashing a new ROM because of the hassle (I just don't have the time to fiddle with a new ROM) and my SD card is encrypted...
Thank you all
I have similar on Galaxy Note 4 and also Galaxy Edge after marshmallow update. If using bluetooth, cant answer next call even if first call is diconnected already. phone freezes, rings forever, cant answer thru phone (nothing shows up on screen even saying there is a call, not in call log either)-- phone will sometimes reboot or i have to pull battery to get it to stop ringing. I also never know who called because no record in call logs of the perpetually ringing call.
Hello! I'm going to need some help on someone that might know more than I do.
Here's the challenge:
Phone: Samsung Galaxy S7 AT&T Unlocked (G930A)
Build: G930AUCS4BRA1 (latest)
This phone has two really hard to pin down issues that will surely make a challenge.
First one, is the microphone. Calling or receiving a call makes the person on the other end to hear themselves. It is not explained by the other person using speakers, since it happens 100% of the time, even testing it with the express instruction to not use a speaker.
What the hard-to-pin-down issue is? It doesn't happen with any other calling program. I can voice call from WhatsApp or from an app from my provider using Wi-Fi or 4G and the issue disappears. Only happens if I receive or make a call from the phone without using Internet.
Second one, is a new one that happens randomly. The phone freezes, shuts down and restarts in a loop, about 3 or 4 times, and then works normally. Happens about 2-3 times a day and started two days ago, without any physical damage as a cause.
What has been done to try to fix this issue?
Cleared cache
Phone reset
Installed updates (twice, one from 6.0 to 7.0, and then updated the build number), once by using Odin, and the other one to update from SD Card.
Nothing has fixed any of these issues.
Any ideas?