Hey guys,
I've had this issue intermittently on my S4 Active but my wife has it constantly on her regular s4. The keypad won't stay on during calls when you're trying to use an automated phone system. It's like the proximity sensor gets confused about how close you are. I've read a couple posts on different forums with other people asking the same question but nobody seems to have a solution other than disabling the screen off during call feature. Any guru's here know anything that could be helpful? I just put the Hyperdrive ROM on my phone and have noticed it more since the software change.
Related
Hi, I'm considering going back to WMobile phones and seriously considering the Kaiser. I currently have the N73 but had many wm5 phones before, SPV m600, Trinity, XDA Orbit, Wizard etc etc, all had annoying little "bugs".
I know the Kaiser is only just out, but can anyone tell me if you have noticed any of the following?
1) delay in ringing when receiving an incoming call. i.e. people on the other end hears a ring, but my phone takes about 3seconds before it rings...v. annoying!
2) delay in waking up.
3) slow response in dialing, i.e. when pressing a number on the dial pad.
4) Missing incoming comes, i.e. full reception but people unable to get through. Extremely annoying.
5) Rebooting itself
6) Alarm not going off.
Hows the call quality?
Anyone used and have any issues with the T9 pad, think that's what it's called. I use to use this, but gave me problems when i switched back to virtual keyboard, e.g. wouldn't switch back at all.
Sorry for all the questions.
1) Haven't tested this yet, i'm hoping this isn't the case though...!
2) Wakes up pretty quick, no unbarable lag
3) Same as 2) - all seems pretty responsive, no bad lag
4) Never had that issue before, don't expect to get it with the Kaiser
5) Nope, although i haven't installed any other apps etc yet...
6) Same as 4)
I can only really compare with the Universal (as that's the only other WM phone i've owned)... my initial impressions are that it's a lot quicker than the Universal... maybe that's partially due to the fact that i haven't installed any bits yet... or really tweaked it.
The 3 second delay was REALLY annoying.... as i'd have to start every phonecall with: "hello....... hello? heeeelllllllllo?" lol... i hope this isnt the case with the Kaiser!
Also i think a lot of the noticable improvements are also due to the fact that im using a vanilla HTC phone, as opposed to a crappy T-mobile 'runined' one! Also i think WM6 has brought in a lot of changes which are noticeably improved over WM5.
EDIT: oh and the only thing that really 'bugs' me - is that i'm used to the lovely VGA Screen of the Universal, so dropping down to QVGA is rather noticable... text looks blockier and using Cleartype seems to make it alot fuzzier than on the Universal.... but that's my only really negative point so far.... hopefully it'll be the ONLY one
EDIT2: Something else i just thought of.... the fact that when my Universal locked up... if i didnt have my Stylus on me (which i usually didnt) and i didnt have a small pin-like object to stick into the reset hole... i was SCREWED... which REALLY pi**ed me off.... countless times i'd be on the train home from work, about to email a friend... only to have my phone lockup... then i'd have to wait an hour before i could reset it and start writing... GRRRRR. Anyway, the Kaiser actually turns off when you hold down the power button... simple... and GREAT! (the power button on the Universal was so stupid.... in my opinion.... was there any way (except by using 3rd party apps) to actually turn the damn thing OFF?! lol)
Hi
hongsit said:
Hi, I'm considering going back to WMobile phones and seriously considering the Kaiser. I currently have the N73 but had many wm5 phones before, SPV m600, Trinity, XDA Orbit, Wizard etc etc, all had annoying little "bugs".
I know the Kaiser is only just out, but can anyone tell me if you have noticed any of the following?
1) delay in ringing when receiving an incoming call. i.e. people on the other end hears a ring, but my phone takes about 3seconds before it rings...v. annoying!
2) delay in waking up.
3) slow response in dialing, i.e. when pressing a number on the dial pad.
4) Missing incoming comes, i.e. full reception but people unable to get through. Extremely annoying.
5) Rebooting itself
6) Alarm not going off.
Hows the call quality?
Anyone used and have any issues with the T9 pad, think that's what it's called. I use to use this, but gave me problems when i switched back to virtual keyboard, e.g. wouldn't switch back at all.
Sorry for all the questions.
Click to expand...
Click to collapse
1) The delay is/was caused by the CPU/OS coming out of standby. With PDA type Windows Mobile devices they have a standby mode where the whole operating system is suspended. The mobile chip remains powered and when a call comes in it has to send a wake up request to the CPU and OS. It is the time the CPU and OS takes to become responsive that causes the delay. I noticed this delay was quite a lot on the Toshiba G900, several seconds or rings before it had woken up to sound the internal audio to alert you to the call. Sometimes it wouldn't wake at all :-(
The Kaiser wakes very quickly, hardly any delay at all, they have certainly put in a lot of work in this area.
Windows SmartPhones don't have this problem as they remain "always on" so respond without delay even though they may look off.
2) Answer above, very quick, almost instant.
3) Seems okay to me.
4) This is probably the OS failing to wake up, I would doubt this happens on the Kaiser.
5) Okay so far.
6) This again is related to the CPU/OS failing to wake up to a request. It is likely the phone you have experienced this with has some problems waking up when asked and would explain all your concerns.
Hope that helps.
Regards
Phil
I read on another thread regarding the assembly which houses the green and red call buttons being loose. What is the opinion of other users over here. I am asking this as I am considering buying one soon to replace my Touch
Regards
Yes the whole section moves slightly on mine, it must just be where they float on a rubber section underneath.
I hadn't noticed this until now, why is this a problem? If it was fixed two tight the keys would scrape against the sides when pressed. Makes sense there is some space.
Regards
Phil
The buttons feel a bit 'loose' but no more than in any other device (the buttons on my PSP for example).
Thanks for the reply guys, kaiser sounds promising, just hope it continues to impress.
hongsit said:
1) delay in ringing when receiving an incoming call. i.e. people on the other end hears a ring, but my phone takes about 3seconds before it rings...v. annoying!
Click to expand...
Click to collapse
There are two contributors to this:
One is a registry entry, where all of the "standard" options cause a 3 second pre-ring delay and 3 second delay between rings. This can be fixed in the registry.
The second is network delay. The caller will hear ringing before your phone rings (usually 1-2 rings) no matter what phone you use. I've had such delays with every mobile phone I have ever used, smart or not. If you try the registry hack (search around for the exact key, numerous posts on it and I can't remember the exact registry key at the moment) and are still not happy, you have one option to reduce ring latency - get a landline.
Hi!
My GNote hangs up/becomes non-responsive when I receive or make a call, everything else is just fine, but it can't be used as a phone now.
I have tried many roms but the problem persists, according to my observation and research the proximity sensor is the culprit here, and it is a hardware problem, which can't be fixed by software, I suppose. But there might be a way to disable the sensor at all, in which way screen won't turn off while making a call, but who cares if I can make a call. I found a couple of threads describing the same problem but with no solution.
Is there a way to do the trick, if not, can you please guide me write my own kernel to disable the sensor, I am not an Android developer but I do have a Master's Degree in Computer Science so I am pretty much confident that I can do it myself if given some pointers.
Any help is greatly appreciated, thanks.
Have a good day, Regards.
have you tried disabling the screen off during calls?
nokiamodeln91 said:
have you tried disabling the screen off during calls?
Click to expand...
Click to collapse
Thank you sooo much, this did the trick..... Now I am wondering why I didn't think of that earlier.....
BTW is there any other way I could get rid of this problem completely, now my screen won't turn off during phone calls, causing unwanted operations.....
Thank you so much.....
if you have tried many roms then may be a issue with the sensor.. try consulting a Samsung service personnel
galaxy note N7000 freeze while during call 1000% solved
you just clean the sensor your prob will be solve 1000%
A few days ago I got the Nokia Lumia Icon from Verizon Wireless. Overall, the phone is great as far as Windows phone go. This is my work phone and I use an Android phone as my person cell phone.
I have discovered that during calls periodically that the proximity sensor gets stuck in detected on the Lumia. Basically, whether sensor is covered or not, the phone's display goes dark during calls. This does not happen on every call but it does on most.
Does anyone know of a fix? Is there a patch / update coming soon?
Thank you,
gabato
I found a post on WPCentral that said to blow in to the 3.5 headphone jack and it would fix the issue for a while. Well I did it - heck no one has replied with a fix yet. So what did I have to loose. It worked. Now I want to see for how long.
Remember, the Icon is still extremely new. I have no clue if/when I'll end up getting an Icon. This place hasn't had much Verizon talk anyways....
My Nexus 6 now goes off and doesnt come on during call I have to end the call to even see.
I just checked and it has been damaged. I have tried everything and finally thought is there a method by which i can disable it by Build prop or disabling drivers. I have tried all apps so i wanted a root level solution
Please devs help me out
FIX: Finally got the fix in benzo rom, in the call app there is an option to keep screen on during calls (only in newer builds from 25th may onwards). FInally fell in love with N6 all over again
This is very weird.
I have never noticed this kind of radio silence in any of the device threads, but on the most open phone of them all and google flagship was most surprising.
I just wanted to know any root kind of fix for priximity sensor, have googled and tried everything, just wanted some help from a dev
http://forum.xda-dev...-1-rom-t3069031
try that
I've seen a million threads asking for proximity sensor or hall effect sensor being disabled in various device forums and I've never seem one get a working answer
Exactly
rootSU said:
I've seen a million threads asking for proximity sensor or hall effect sensor being disabled in various device forums and I've never seem one get a working answer
Click to expand...
Click to collapse
I've tried everything, from apps to hardware disabler to prximity off lite and all that. Nothing has worked, the boggest problem is I am in a lot of conference calls and this is out of question while using this phone
cmh714 said:
http://forum.xda-dev...-1-rom-t3069031
try that
Click to expand...
Click to collapse
tried that as well.
I think its damaged, hardware problem, jsut wanted to disable it completely
and FYI i dont have any screen protector
the kind of fix I am talking about is this
http://forum.xda-developers.com/galaxy-nexus/themes-apps/fix-proximity-sensor-call-issue-t2016338
There's a proximity fix zip for this phone too, but I don't think it will help in your situation.
Like the title says, the proximity sensor on my s10 is flashing. (Little circle above the battery percentage)... Everything i find online says this should only happen during a call. But I'm not in a call, nor have i been in a call at any point in the day. Phone apps aren't open.
Only thing that's changed recently is I've update to the newest Good lock earlier today. Just noticed the flashing pixel.
Any ideas, or is this happening to anyone else?
U.s. snapdragon on Sprint