Hello, all. I'm new here and I'm also a new Mi Mix user. Luckily, I have another daily phone because I am having issues with incoming calls and dialing out. First, when I get a call, I can hear the phone ringing, but there's no notification on the main screen so I can see who's calling. I'm not even sure how to answer the call. I think I've been hitting the phone icon to answer, but not sure if that is what has helped me answer the call. Shouldn't there be an answer or ignore option that I visually see somewhere? Also, I don't see any option to hang up the call. I'm guessing, my Mi Mix hangs up after the caller has hung up. These things seem like simple things that a smartphone should do nice and simple. Why am I having an issue with seeing who's calling me, issues with dialing out, and issues figuring out how to hang up. Please help me. Thank you.
zunelander said:
Hello, all. I'm new here and I'm also a new Mi Mix user. Luckily, I have another daily phone because I am having issues with incoming calls and dialing out. First, when I get a call, I can hear the phone ringing, but there's no notification on the main screen so I can see who's calling. I'm not even sure how to answer the call. I think I've been hitting the phone icon to answer, but not sure if that is what has helped me answer the call. Shouldn't there be an answer or ignore option that I visually see somewhere? Also, I don't see any option to hang up the call. I'm guessing, my Mi Mix hangs up after the caller has hung up. These things seem like simple things that a smartphone should do nice and simple. Why am I having an issue with seeing who's calling me, issues with dialing out, and issues figuring out how to hang up. Please help me. Thank you.
Click to expand...
Click to collapse
Hello. Please mention your current rom version, modifications you've made, etc. to get a better help. Otherwise some would suggest you to clean flash the rom or something like that.
Besides, it also might be caused by a theme(If*). Change it to default. Also this post has to be posted under Q/A forum(only and once).
Sent from my lithium using XDA Labs
Konstantine34 said:
Hello. Please mention your current rom version, modifications you've made, etc. to get a better help. Otherwise some would suggest you to clean flash the rom or something like that.
Besides, it also might be caused by a theme(If*). Change it to default. Also this post has to be posted under Q/A forum(only and once).
Sent from my lithium using XDA Labs
Click to expand...
Click to collapse
Hi. I am very new to this particular phone, so I am new to things like ROM and flash. I bought the phone used. The seller listed is as not having been ROMed at all, but maybe it was. How can I tell what ROM I have? I also would not be opposed to clean flashing it since I would prefer it to be new (so to speak) when I purchased it. I have already factor reset it and wiped it and then rebooted it, but not sure if that is the same as cleaning the flash. Please advise. Thank you for your time.
I got the issue fixed. Thanks for your efforts.
Related
I have moved away from WinMob for the same reasons as many others and now find myself searching for similar Apps for Android (T-Mobile UK G2) now....
One such app I used was the 'In Call Tweak' app which woke the phone screen up when you removed it from your ear during a call.... very useful.
Has/does anyone have information as to this type of app existing for Android or know that it's being worked on?
Many thanks and I apologise in advance if I have been a numpty and not searched hard enough.
I am not going to be helpful here. There was an app, I removed it for some reason and now I cant remember what the app was called!
I do remember that it stopped the screen going off fully and it was a bit oversensitive but otherwise ok.
Thanks for the reply..... At least I know that one existed.
Can you remember if you found it in the Market? that could narrow down the search.
Ta,
I believe that "Shake Awake" is what you're after...
http://www.androlib.com/android.application.com-maplekeycompany-apps-shake-ptw.aspx
cdmackay said:
I believe that "Shake Awake" is what you're after...
http://www.androlib.com/android.application.com-maplekeycompany-apps-shake-ptw.aspx
Click to expand...
Click to collapse
You could not be more right! Thank you very much for reminding me...
Thanks guys.... I'll give it a whirl.
Having done some testing.....
The 'Shake Awake' app doesn't seem to work as well as the windows version which uses the light sensor as a trigger...
So if any one else knows of another appI could test I would be grateful.
by coincidence, i had need of it today, and it didn't seem to work at all. worked fine when I tested it using its own calibration tester thing.
I need to do some more real-call testing before I can tell if it's me, or it's broken.
You should try these settings for the HTC Hero:
select sensitivity: Like it ows you money..
enable cheek guard screen : OFF
show status : ON
outgoing calls : ON
incoming calls : OFF or ON as you like it (save would be OFF)
Don't forget to only leave this app with the back(arrow)button !
have fun!
Rubbish
This app suck major a$$ and rarely works properly.....
cdmackay said:
by coincidence, i had need of it today, and it didn't seem to work at all. worked fine when I tested it using its own calibration tester thing.
I need to do some more real-call testing before I can tell if it's me, or it's broken.
Click to expand...
Click to collapse
I'd failed to note that it only works for outgoing calls, by default, and it's a security problem if you enable it for incoming calls. I suspect that when I wanted to use it, it was an incoming call.
Can anyone explain what the cheek guard option is for? I can't find it explained anywhere...
Hi cdmackay,
I saw some reference to it in the help file but it wasn't specific but I think that it might stop your cheek from accidentially activating the screen.....
I still find it unreliable... about an 80% hit rate...
I'm not a programmer (in the true sense) but I can't see why it can't be made to work like the Win Mob version which senses the attitude of the phone together with what the light sensor is reading to check if the phone is by your ear or you are looking at it to enter data of some kind..
I might email the developer to see if this is possible.
Somebody else has also raise the same question...
http://forum.xda-developers.com/showthread.php?t=553108
they have mentioned an app called keepscreen which can keep the screen alive but this can also be done by PowerManager (for calls).
thanks much
First time poster, all, so be please be gentle!
I've got a problem that I've not seen anyone else ask about or reference. For some time now, my Captivate has not been ringing when I receive a regular phone call. However, it does: play media files with sounds as normal; play notification sounds; play game sounds; alarm sounds when the alarm goes off. In fact, the only sound-type application it has any problem with is ringing on an incoming call.
I'm not a complete noob, so please assume that I've checked all the usual suspects (silent mode, vibrate mode, using stock ringtone vs. custom, physical volume up/down buttons, rebooting, etc.) However, if you know of a more esoteric setting that could be missed, I'm dying to hear about it.
I'm running Cognition 2.3b1 or 2.3b2 at the moment, but I'm going to go out on a limb here and say that this problem began before upgrading, although I've been using Cognition before the Froyo update; I really don't think it's an issue with Cog, especially as I haven't seen anyone complain of the same symptom.
Is there perhaps some system level directive along the lines of incoming_call_ring=NEVER that I've somehow, someway triggered and just don't know how to undo?
Anyway, thanks in advance for any help! I enjoy these forums and the sense of community, even though I generally just lurk
If it really has been going on since before you flashed I think you know the answer to your question
Sorry to hear that.
Have you tried master clear? If it persists then flash to stock.
Sent from my SAMSUNG-SGH-I897 using XDA App
I haven't tried master clear yet, good suggestion. By this weekend I should probably be at just the right ratio of desperation vs time to give that a try. I'll post back here after.
Not just me!
It would seem that this is affecting a small number of Captivate owners. The solution was suprisingly simple and effective: push in the 'speaker' with your thumb. Guess the speaker isn't locked in as tightly as it should be, or is prone to short-circuiting. Haven't had any more problems since pushing it in, go figure!
Anyway, see this thread for more details:
hxxp://forums.wireless.att.com/t5/Samsung/Samsung-Captivate-Sound-not-working-over-loud-speaker/td-p/1996034
First, a HUGE thanks to this community, both the O4X and xda, as a whole. Can't tell you how many times the collective expertise here has saved my...
To my issue: on occasion, my phone mutes itself. The onscreen display doesn't show my end as being muted (pressing and repressing does nothing). I end up having to end the call and call again, which is a pain after being on hold for 20 minutes.
I can find no rhyme or reason for this behavior either. Most of the time it's on outgoing calls, but happens on incoming also. Happens across networks (VZW, AT&T) and with landlines (calling my bank). This has happened in the morning, afternoon and at night, though it doesn't happen in the middle of a call, only the beginning. Just seems to be random.
I've browsed through the 3845#*880#/hidden menu but didn't find any sort of relevant tests. If anyone has any thoughts and/or solutions as to what's going on, be happy to hear 'em.
Thanks
tadees said:
First, a HUGE thanks to this community, both the O4X and xda, as a whole. Can't tell you how many times the collective expertise here has saved my...
To my issue: on occasion, my phone mutes itself. The onscreen display doesn't show my end as being muted (pressing and repressing does nothing). I end up having to end the call and call again, which is a pain after being on hold for 20 minutes.
I can find no rhyme or reason for this behavior either. Most of the time it's on outgoing calls, but happens on incoming also. Happens across networks (VZW, AT&T) and with landlines (calling my bank). This has happened in the morning, afternoon and at night, though it doesn't happen in the middle of a call, only the beginning. Just seems to be random.
I've browsed through the 3845#*880#/hidden menu but didn't find any sort of relevant tests. If anyone has any thoughts and/or solutions as to what's going on, be happy to hear 'em.
Thanks
Click to expand...
Click to collapse
i had this issue, pinpointed it down to viber, for some reason. uninstalled it, and it works fine now. a workaround is, during the call, switch to speaker, then normal again, your mic should be working for a minute or so
Flying_Bear said:
i had this issue, pinpointed it down to viber, for some reason. uninstalled it, and it works fine now. a workaround is, during the call, switch to speaker, then normal again, your mic should be working for a minute or so
Click to expand...
Click to collapse
Thanks for the timely reply Flying_Bear.
I don't have Viber installed (assuming it's an app/service called Viber, not com.lge.viber or something). The sole reason I went root was to clean out the bevy of junk that comes preinstalled. Unfortunately, your work-around didn't work either. Just called my bank and switching between speaker and earpiece had no effect; the operator still couldn't hear me.
Any other guesses?
I did find this from another thread, reads like CM10 might do the trick, but I'd rather not go that route if possible. This seems to be a known, albeit infrequent, yet annoying issue.
tadees said:
Thanks for the timely reply Flying_Bear.
I don't have Viber installed (assuming it's an app/service called Viber, not com.lge.viber or something). The sole reason I went root was to clean out the bevy of junk that comes preinstalled. Unfortunately, your work-around didn't work either. Just called my bank and switching between speaker and earpiece had no effect; the operator still couldn't hear me.
Any other guesses?
I did find this from another thread, reads like CM10 might do the trick, but I'd rather not go that route if possible. This seems to be a known, albeit infrequent, yet annoying issue.
Click to expand...
Click to collapse
oh well, it seems that our problems, even though they have similar simptoms, aren't caused by the same thing. i can't give you much, except the standard factory reset / reflash .kdz advice. good luck!
Flying_Bear said:
i can't give you much, except the standard factory reset / reflash .kdz advice. good luck!
Click to expand...
Click to collapse
ah well, thanks for trying. :cheers:
About 2 days ago I noticed when i receive a call, it rings but the screen is black. If i hit the power button it will wake the screen but it doesn't show I'm receiving a call except for the fact I lose LTE ( I'm on Verizon). I can also double tap the screen ( have the mod) and it will wake but still nothing. Once the call is over it will show a missed call in the status bar. I'm rooted but on 5.0.1 stock. Was working fine until a few days ago. Anyone else?
Are you using Lux? If so, uninstall it. Problem solved. If not, then I'm not sure what to tell you.
KB112 said:
Are you using Lux? If so, uninstall it. Problem solved. If not, then I'm not sure what to tell you.
Click to expand...
Click to collapse
No, not using Lux. Starting to piss me off. Just shows up out of the blue and haven't really installed any new programs in a while.
Well I'm still having the problem but i have found if I can wake the screen and then hit the phone icon, one of the options it gives me is to "return to call in progress" and if I hit that it gives me the option to answer the call. This sucks.
Any chance you've got something covering or blocking the ambient light sensor? When my screen got cracked, there was a fissure that went directly over the sensor, and I had the same problem you're having. Maybe some dust under a screen protector?
chemguru said:
Any chance you've got something covering or blocking the ambient light sensor? When my screen got cracked, there was a fissure that went directly over the sensor, and I had the same problem you're having. Maybe some dust under a screen protector?
Click to expand...
Click to collapse
That was a great idea but still didn't work. I took the screen protector off and still the same thing. I might try a custom rom but I think it's time to sell. I love big phones and I do like this phone but it may be a tad too big for me. Might put it on Craigslist but the hicks in my area don't understand what "Nexus" is or "price is firm"...."will you take $150 for that there phone?"
alnova1 said:
Well I'm still having the problem but i have found if I can wake the screen and then hit the phone icon, one of the options it gives me is to "return to call in progress" and if I hit that it gives me the option to answer the call. This sucks.
Click to expand...
Click to collapse
Do you have your phone number integrated with Google Voice? If so you might want to double check your Google Voice integration settings as I know they have that caller ID that lets it ring to voice mail and you can decide if you want to take the call after they start to leave a message
Google just did some changes with Hangouts this week that nerfd Messenger and Google Voice for me
Post here in the Q&A section is forthcoming but in the mean time you can check out my post on the Google forums about what their changes broke HERE
If you are looking to try a ROM check out Clean ROM - link is in my signature below
SP_Kenny said:
Do you have your phone number integrated with Google Voice? If so you might want to double check your Google Voice integration settings as I know they have that caller ID that lets it ring to voice mail and you can decide if you want to take the call after they start to leave a message
Google just did some changes with Hangouts this week that nerfd Messenger and Google Voice for me
Post here in the Q&A section is forthcoming but in the mean time you can check out my post on the Google forums about what their changes broke HERE
If you are looking to try a ROM check out Clean ROM - link is in my signature below
Click to expand...
Click to collapse
I do use my google voice number but I don't have it setup like you were talking about. It rings directly to my phone. I checked my setting and they are the same. I tired using hangouts for my voice text messages but found that a lot of the time it wouldn't notify me that I had received a message so I went back to the Voice app. I'm just stumped. I my give the Clean Rom a shot. Do you know if it works well with Verizon? Seen some people saying they were having a few problems with some of the roms on Verizon. Thanks for the input.
alnova1 said:
I do use my google voice number but I don't have it setup like you were talking about. It rings directly to my phone. I checked my setting and they are the same. I tired using hangouts for my voice text messages but found that a lot of the time it wouldn't notify me that I had received a message so I went back to the Voice app. I'm just stumped. I my give the Clean Rom a shot. Do you know if it works well with Verizon? Seen some people saying they were having a few problems with some of the roms on Verizon. Thanks for the input.
Click to expand...
Click to collapse
Clean ROM is a striped down and tweaked stock rom so it doesn't have some of the issues the ASOP roms do. I had to look through a few pages from about page 18 on, as that is when he announced CR was no longer in beta and released the 1.1 rom. Saw more t-mob, at&t and sprint peeps in there but at least 1 person on verizon reported in all was good and tether is supposed to be working
SP_Kenny said:
Clean ROM is a striped down and tweaked stock rom so it doesn't have some of the issues the ASOP roms do. I had to look through a few pages from about page 18 on, as that is when he announced CR was no longer in beta and released the 1.1 rom. Saw more t-mob, at&t and sprint peeps in there but at least 1 person on verizon reported in all was good and tether is supposed to be working
Click to expand...
Click to collapse
I just installed it and it seems to have fixed my problem for answering calls. Have no idea what was wrong before on the original rom. Seems to be running nicely and Verizon is working fine it seems like. Thanks for the recommendation.
Nice!! :highfive:
If you could please chime in on the clean rom thread so others see that a verizon user is up and running on it as I had seen way more peeps on the other 3 carriers there
SP_Kenny said:
Nice!! :highfive:
If you could please chime in on the clean rom thread so others see that a verizon user is up and running on it as I had seen way more peeps on the other 3 carriers there
Click to expand...
Click to collapse
I definitely will as soon as I head out and do a little testing on it.
I had this exact problem with my wife's Nexus 6 but mine was functioning fine. Turns out that under SETTINGS - SOUND & NOTIFICATION - APP NOTIFICATION she had the Goggle Dialer blocked.
Have the exact problem outlined by the original thread starter, scour a few webpages with different sort of solution.... nothing works!
My solution: Simple, just uninstall the Phone app updates, voila, all back to normal.
Hope it'll help someone.
I have a problem with my new 11t pro. Stock Rom MiUI 12.5 purchased in Viet Nam, debloat some app (all in suggested app to debloat). I've use this phone for 2 weeks, and sometimes when im making a call, the other side cannot hear me at all, and i can hear them. This occurs occasionally, i think about 1/15 calls i make. This only happen when i was the one calling, receiving calls is totally fine. I've tried turn off "Hey google", no use. Tried "True phone" dialer instead of Phone by Google, it happens less but still there. Please help!
thangbeo2708 said:
I have a problem with my new 11t pro. Stock Rom MiUI 12.5 purchased in Viet Nam, debloat some app (all in suggested app to debloat). I've use this phone for 2 weeks, and sometimes when im making a call, the other side cannot hear me at all, and i can hear them. This occurs occasionally, i think about 1/15 calls i make. This only happen when i was the one calling, receiving calls is totally fine. I've tried turn off "Hey google", no use. Tried "True phone" dialer instead of Phone by Google, it happens less but still there. Please help!
Click to expand...
Click to collapse
Try resetting the phone and reinstalling the rom like that you will be sure it is not a software problem.
NOSS8 said:
Try resetting the phone and reinstalling the rom like that you will be sure it is not a software problem.
Click to expand...
Click to collapse
Im doing a Factory reset first without debloating to see how it goes, only been 1 day but so far so good.
The proximity sensor is one of the weakest point of the phone.
During call the screen used to turn on and unfortunately the mute button is the first what I used the press with my ear..., so the microphone get muted.
I seen many people reported the same issue.
Check it before making hard reset!