Related
Hi there, I am using VJgrace latest 3.4 ROM, I realized that nowadays, sometimes I would not be able to receive incoming calls, my friends and relatives have complained that I do not pick up their calls, they even showed me the proof of their call logs. They said there were dialing tone. So one day, I tried for myself and true enough, at times, the phone will just light up from idle, but it will not say that there is an incoming calls. When this happen, I cannot make outgoing calls as well, when I try to dial someone, it just hang there.
Any solution? Is this a radio or ROM problem?
I have run the GSM update
I faced the same problem too. I thought my friends were joking. just called myself to confirm. true enough the phone lights up for a second or two then it goes back to sleep.
this is serious. am thinking of going back to WM 5
Really? Wow. That's a new one. I guess I haven't seen this. illi - would you really go *all* the way back to WM5? Are you saying this is a problem in every WM6 ROM you have installed? I'm surprised... I've never seen it on my phone. But I don't get too many calls during the day. And I reboot my phone every 2 or 3 days just for good measure.
bipinsen said:
Really? Wow. That's a new one. I guess I haven't seen this. illi - would you really go *all* the way back to WM5? Are you saying this is a problem in every WM6 ROM you have installed? I'm surprised... I've never seen it on my phone. But I don't get too many calls during the day. And I reboot my phone every 2 or 3 days just for good measure.
Click to expand...
Click to collapse
i cant afford to loose calls. some friends had complained since a few months back. so i suspect its all WM6 ROMs not just vj's.
i think it happened when the device is syncing because i receive lots of emails. so at that time the gprs/edge is being use. THIS IS MY WILD GUESS ONLY!! I noticed it (the device awakes then back to sleep) once while on active sync and at that moment emails were being downloaded from my email server.
How can yew trouble shoot this problem?
illi said:
i cant afford to loose calls. some friends had complained since a few months back. so i suspect its all WM6 ROMs not just vj's.
i think it happened when the device is syncing because i receive lots of emails. so at that time the gprs/edge is being use. THIS IS MY WILD GUESS ONLY!! I noticed it (the device awakes then back to sleep) once while on active sync and at that moment emails were being downloaded from my email server.
How can yew trouble shoot this problem?
Click to expand...
Click to collapse
Do you have this checkbox selected? I'm not sure if it makes a difference, but it's one thing I saw.
bipinsen said:
Do you have this checkbox selected? I'm not sure if it makes a difference, but it's one thing I saw.
Click to expand...
Click to collapse
not too sure but will check next time i active sync. anyway i rarely sync with my pc so i doubt thats the problem - i noticed once while hooked to pc the phone awakens and then sleep. i use mail2web.com's microsoft exchange to sync my emails. i active sync only to do spring cleaning on my device and SD.
if karhoe subscribe to the same telco as me than i suspect its the operator. (hello karhoe you there;-))
I have this problem even when the phone is not connected to Active Sync, when i'm outside. The phone just light up, and then poof, gone. Well, I am using DiGi telco. But I don't have this problem when using Andot's PEE, don't have it when using 3.0 ROM, only recently when I started using 3.1, had this problem, after so long, then use 3.4, still have it
I had this issue with WM5.. now with WM6 I didn't found (yet) this issue. (using EA ROM)
This is a quote of one of my posts (Oct 7 2006, 18:43, modaco):
i think this is a software issue..
i have a spv c600 and have problem with the telephony part (and many other spv c600 users)
1. some times when somebody is calling me the phone does not announce in any way that i have a call.
2. other times when somebody is calling me the phone send automatically a busy tone to the caller and again does not announce me that somebody has called me.
3. and other times when somebody is calling me, the caller is announced by the robot that 'the user is in an uncovered area or has the phone turned off' or it divert it to voice mail (if the WM user has voice mail active. i have it off)
however, point 1 and 2 can be 'detected' by eye on call (phonesharpen). only detected (no answer, no nothing).
- in the first case, a window with caller information is displayed as long as the caller is calling you.
- in the second case, a window appears and disparears extremly fast
to bad that the phonesharpen does not log the detected calls . i have mailed them about this, but on answer..
i gues the problem is the native telephone application
so .. in conclusion WM smartphones are not recommended for people who want to use them as a phone.. who knows what important calls you miss.. i hope this will be fixed someday
Click to expand...
Click to collapse
@karhoe you should tell this to NiTroGeN and to VJgrace
Gentlemen, I suspect this issue is somehow connected to currently selected homescreen. I had this issue on WM6 build 18120 homescreen with VOIP plugin, but when I chose another one not containing VOIP info, this issue has gone
ega2oo2 said:
Gentlemen, I suspect this issue is somehow connected to currently selected homescreen. I had this issue on WM6 build 18120 homescreen with VOIP plugin, but when I chose another one not containing VOIP info, this issue has gone
Click to expand...
Click to collapse
I tend to believe that it is caused by either of these problems:
1 - the telco (I'm subscribing to the same telco as karhoe)
2 - the voip plugin on the Homescreen
This is what I'll do: I shall deactivate the voip plugin. But I cant afford to unsubscribe from my current telco; it offers the cheapest unlimited data plan. LOL!!
I have a feeling that it is related to VOIP, I did configure my VoIP using the xml method, and then I also installed the VoIP fix button for communication manager. Now im using HTC Home screen and so far, so good
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.
Hello, i need some serious help over here
What's the problem:
I own a galaxy 3 since June, a week ago i started noticing the internal mic wasn't working on some incoming calls.
Details:
First of all the problem began for no apparent reason (the phone works fine otherwise and no major updates / new apps were installed)
This started happening on the official froyo ROM which was an excuse for me to flash the Kyrillos 9.4 ROM (wiped all data / formatted sd card in the process). The problem still occurs on Kyrillos 9.4 ROM suggesting that this is not a ROM issue
I thought it was a hardware issue but the caller can hear me perfectly if i connect the headset or use the speaker Also the internal mic works fine on some incoming calls and ALL outgoing ones!
Upon further investigation i came upon 2 threads on other forums (unfortunately i can't post the urls as i am a new user, if needed pm me or search google for "Microphone not working on incoming calls") which point out that the same problem incurs on HTCs and XPERIAs. Also it happens on replacement phones (original unit shipped back after this problem), on different providers, on official and custom ROMs, on clean phones (only the stock apps installed).
This seems to happen when the phone is idle for a set period of time (unconfirmed). Fast Reboot app / manual reboot / removing battery don't fix this, however making an outgoing call seems to enable the internal mic temporarily (even if the outgoing call never connects)
When this happens apart from the mic not working on incoming calls it becomes also unresponsive for other apps (Tape-a-Talk, Skype, Soundhound etc.)
Conclusion:
It seems to me that there is bug in froyo that keeps the incoming call code from activating the microphone or perhaps there is a conflict of sorts that keeps the microphone blocked. It is highly unprobable i think that the microphone would randomly start to fail on different android phones in the exact same way, so this shouldn't be a hardware issue.
Question:
Does anyone know/guess or can produce a possible solution for this? If not, could you please suggest further testing steps to help reproduce 100% this problem in an attempt to solve it?
Any help would be greatly appreciated as this is a pain in the neck for me (and others i guess?!)
PS: Excuse the thread form, i 'm really bored of writing / reading long posts
PS 2: This is my first post, hello xda community!
samsung vibrant
I have the same problem. I flashed the phone from android 2.1 TO cyanogen 2.3 and from it TO ice cream. I had this problem even to cyanogen and only in incoming call,never in other situation.
Googling I found same information but no solution. Anyone here knows something?
Anyway I found a stupid solution....try switching to 2g( I know that it's not a solution but...). It works for me!
that's ridiculous! how can network state have anything to do with the microphone of the device? can this be related to service providers maybe a more techish member could tell us.
anyway i am on 2g already as i don't have a usim card and this happens even if data network mode is deactivated. glad you found a way out but is it really a solution? i mean you have to ditch 3g for the phone to be actually a phone...
Since we seem to be the only ones among so many to be having this problem i am seriously thinking of taking back the phone for a replacement and hope for the best...
just an update, i lost functionallity of the microphone completely earlier today. That is with outgoing / incoming calls and any app i can think of, so i thought i 'd try changing the network data setting to 3g only since i was already on 2g...
WOW!!! that had an instant effect,it works seamlessly now,didn't even have to reboot.fingers crossed it will last.
that is one nasty and very strange bug. Please any of the developers could you take a closer look at this?
much appreciated
Sent from my GT-I5800 using XDA App
I was hoping that CM13.0 would solve my Bluetooth problem but did not.
Although most of the time is working with a factory Bluetooth system (in a MB car) every now and then it disconnects.
Disconnection usually happens when there is an incoming call - before I press the accept call button, phone disconnects and reconnects a second or so latter.
I had this problem with CM12.1 and I was hoping CM13 would fix it - only in CM12.0 it was working fine.
Rare times it disconnects while idle – or it happens often and it goes unnoticed.
Is there any solution I missed?
Things like complete factory reset / clearing cash etc are done with no change in the results.
Car has no update (it’s an Alpine NTG2.5 system).
papars said:
I was hoping that CM13.0 would solve my Bluetooth problem but did not.
Although most of the time is working with a factory Bluetooth system (in a MB car) every now and then it disconnects.
Disconnection usually happens when there is an incoming call - before I press the accept call button, phone disconnects and reconnects a second or so latter.
I had this problem with CM12.1 and I was hoping CM13 would fix it - only in CM12.0 it was working fine.
Rare times it disconnects while idle – or it happens often and it goes unnoticed.
Is there any solution I missed?
Things like complete factory reset / clearing cash etc are done with no change in the results.
Car has no update (it’s an Alpine NTG2.5 system).
Click to expand...
Click to collapse
Sadly, this is a wide problem with a lot of Android phones.
One of the fixes Ive read around is to not give so many permissions when pairing a Android device. Example I read: Someone's device would never connect if they shared contacts with their car. You can share contacts and have the hands free not working or not share any contacts and have handsfree working. Its a trade off.
So far CM13 seems little better.
What I can't figure out is the pattern, if there is one. Why sometime it works and sometimes is not. When I initiate the call from the phone or the car keypad, 99% it will work without a problem.
When I receive a call, its a hit or miss. Sometimes it works, sometimes it doesn't. The only reason the phone is not landed out of the window is the fact that reconnection is quick, so I get to answer the call from BT no matter what. But is frustrating.
I remember my first phone with this car was a (non smartphone) nokia. In that case from BT I could hear the selected phone ringtone and the phone did not ring at all.
With any smartphone from then on, both the phone rings (with its own ringtone) and the BT rings with a generic tone. Oh well ...
BTW I had zero problem with BT when I first bought OPO - but then it had CM12.0 I think.