Greetings all,
I have the HTC Droid Incredible, runing Android 2.3.4, Kernel 2.6.35.13.
I would like to use Skype with wifi, but have discovered a bug. When I make a skype call, all works well on speakerphone. However, as soon as I put the phone to my ear, the proximity sensor turns the screen off, and slows down wifi considerably. This results in my skype call being ended.
I would like to fix this by setting my phone to keep wifi on like normal, even when the proximity sensor turns the screen off. I found this thread, which sounds like what I need, but there doesn't seem to be a download for my kernel version: http://forum.xda-developers.com/showthread.php?t=752856
Can someone explain to me the steps I would need to take to fix this issue?
Thank you!
Related
i've tried searching this forum with no luck for results, so maybe someone can point me in the right direction...
just wondering if there is a fix for this issue, that apparently is a bug:
when receiving an incoming call, and while the phone ringer is turned on, it will ring for a split second then it will stop ringing. the call will still be coming through and i can answer it and talk just fine, it's just the ringer that is the problem. this happens randomly, and i've found numerous posts on other forums by searching google, but haven't been able to find anything here.
can't post a url so here's some quotes:
My Dinc sometimes stops ringing after half a second with incoming calls. I'd hear a very short ring and then it just stops ringing or vibrating. I just noticed this today after missing several calls with my phone today.
This problems comes on randomly and goes away in a similar fashion. This seems to happen only when the phone is lying screen down on a flat surface. I called HTC and they said it might be due to the sensor in the front and advised me to not put phone face down and always carry it in a pouch. This is not an acceptable solution. I carry my phone in my pocket and it can very well be face down in there.
Has anyone noticed this problem? If not, I invite you to reproduce this problem. Put your phone screen down on a perfectly flat surface and try to call your cell. I'm wondering whether my phone is defective or it's a much wider issue.
Thanks.
Update: Apparently there is a feature on HTC devices when if you're holding the phone and if it rings, it will mute if you put it on a surface face down. While this is fine, the problem with my device is that if I leave it on a flat surface, it will do that for all subsequent calls too (ring for half a second and then mute). Maybe my phone has a bug in implementation of this 'feature'?
Click to expand...
Click to collapse
It's a well known issue that HTC has not fixed and will most likely never fix. I've been through 3 Dincs because of this problem and they all do the same thing. Quite irritating! Nice phone except for this BIG bug.
Click to expand...
Click to collapse
is there any fix for this bug? and does anyone know if this bug is software or hardware related. currently, i'm running stock 2.2 rooted with city id deleted. thinking about flashing CM7 or another custom rom, and just curious if it will do this with those roms as well.
thanks for any help
Must be an issue with the stock rom. I've never had a problem. But I've also never ran the stock 2.2 rom. I ran stock 2.1 until root was achieved. Custom Rom's from there on out.
Sent from my ADR6300
Also on my HTC Wildfire
This happens also on my htc wildfire android v2.2.1 (latest official rom), i think it is caused by the mute-on-pickup feature that is bugged in some way, even if i have turned it off.
Thought I'd share my experience about this. I was running Paranoid Android 0.9, no issues at all. One day I was talking on the phone and noticed the screen flickered quickly... then it just stayed on. I hung up the phone a minute later not thinking much of it.
Well today I made some phone calls and the screen never turned off.. I had to manually turn it off via power button. I installed Paranoid 1.1, no changes. I flashed Trinity kernel, no changes. Just a bit ago I fully wiped the device and flashed the latest 6/4/2012 CM9 Nightly and the issue is still present.
At this point I'm guessing there is definitely a hardware issue. I have never dropped this phone and it's in mint condition aesthetically. It's the GSM version bought via Expansys.. and I won't waste my time with warranty through them I'll just bare with using the power button to turn the screen off/on during calls.
Another note, I noticed if I tap or press firmly on the proximity sensor area during a call it will trigger the screen to momentarily turn off.
Could this possibly be a CM9 issue (Paranoid is built from CM9)? I may try flashing a rom not built from CM9. I've searched high and low on the internet and NO ONE has had this issue which is leading me to believe that there's no way this is hardware related.
All roms are based off of AOSP.
I guess I'm the only one.
There are some apps that can test your Proximity sensor, though I can't remeber the app name.
/Edit: Link to the app.
Have you tried franco kernel to check if this happens aswell? You can then pin down the possible kernel related issues.
Firmware again plays a major factor? What firmware are you on? Mines came as an OTB 4.0.2 and I too had this similar issue where I had to manually swipe my finger against it, Upgraded to 4.0.4 and the issue went away. Weird.
Misledz said:
Have you tried franco kernel to check if this happens aswell? You can then pin down the possible kernel related issues.
Firmware again plays a major factor? What firmware are you on? Mines came as an OTB 4.0.2 and I too had this similar issue where I had to manually swipe my finger against it, Upgraded to 4.0.4 and the issue went away. Weird.
Click to expand...
Click to collapse
I'm on 4.0.4. I just flashed Android Revolution (4.0.4 based rom with the stock kernel) and the problem still persists. It's very intermittent. Sometimes the proximity sensor detects an object close thus turning the screen off, but it only turns it off for 2-3 seconds or sometimes not at all. I wonder if a piece of dirt/dust is sitting right on the sensor?
I tried a couple proximity sensor testing apps out there but none of them work and say "If your reading displays nothing or the maximum value then your device does not support reading of proximity sensor values".
The apps display a max of 5cm with a resolution of 5.. and the current value is ALWAYS a 5.
I just find this hard to belive I'm THE ONLY ONE on the interwebz, out of MILLIONS sold, who has reported this problem.
Ok, I'm a complete idiot....
Turns out the Galaxy Nexus proximity sensor ONLY works when the phone is in the upright position!!! I kept testing it with it flat on the table and, by design, it's SUPPOSED to keep the screen lit.
So, I've sideloaded Android Wear 1.4 to my Huawei Watch and it's been working well so far!
In my phone's bluetooth settings, I've configured it to "use the watch for phone audio", so that I can answer calls through the watch.
Today, however, I noticed something annoying: when I use my phone to make calls, the proximity sensor is no longer activated (the screen remains on during the phone call). Did anyone notice the same problem? Any workarounds?
I'm not sure this is relevant, but my phone is an HTC One M8 running Android 6.0 (Google Play Edition).
Thanks!
tiagobt said:
So, I've sideloaded Android Wear 1.4 to my Huawei Watch and it's been working well so far!
In my phone's bluetooth settings, I've configured it to "use the watch for phone audio", so that I can answer calls through the watch.
Today, however, I noticed something annoying: when I use my phone to make calls, the proximity sensor is no longer activated (the screen remains on during the phone call). Did anyone notice the same problem? Any workarounds?
I'm not sure this is relevant, but my phone is an HTC One M8 running Android 6.0 (Google Play Edition).
Thanks!
Click to expand...
Click to collapse
Same here, except that I'm on a Moto X Pure 2015.
What I've just ended up doing is after dialing/answering a call, I press the power button to turn the screen off, and turn it back on to end it.
The same here. Another alternative is to manually choose "Earpiece" within in-call screen. This activates prox sensor again.
This should be considered a bug and I believe Google will make necessary adjustments in the Dialer app in this regard.
Thanks for the help, guys! The workarounds you provided do work. However, the bug is still very annoying. I've reported the bug in the AOSP issue tracker:
https://code.google.com/p/android/issues/detail?id=202776
tiagobt said:
Thanks for the help, guys! The workarounds you provided do work. However, the bug is still very annoying. I've reported the bug in the AOSP issue tracker:
https://code.google.com/p/android/issues/detail?id=202776
Click to expand...
Click to collapse
Thanks for taking care of creating an issue. I added my vote and comment.
Just voted as well...Nexus6P
This issue does not seem to present in my Samsung Galaxy S6 ... the proximity sensor works as intended during phone calls from phone.
The phone screen does not dim when the call is actually running on the watch , however the proximity sensor works as expected and dims the screens if the call is placed from the phone or transferred back to the phone from the watch......Perhaps this issue is Device specific or present in the stock versions of Android OS
Most likely related to Google's Dialer app and InCallUI app
Samsung delivers its own modified Dialer so it is possible they took care of that issue themselves.
Added new comment. Quoting.
Issue seems to be fixed after updating my Nexus 5X to MHC19J. Well, almost. Handset earpiece is forced as soon as call is connected resulting in proximity sensor being active, which is OK for handling incoming calls. Issue is with outgoing calls as when dialing, I have to wait for call to be connected before proximity sensor kicks in. Proximity sensor should kick in as soon as dialing starts, before call is connected.
Click to expand...
Click to collapse
nomad032 said:
This issue does not seem to present in my Samsung Galaxy S6 ... the proximity sensor works as intended during phone calls from phone.
Click to expand...
Click to collapse
Works also fine for my Samsung Note 4.
tiagobt said:
So, I've sideloaded Android Wear 1.4 to my Huawei Watch and it's been working well so far!
In my phone's bluetooth settings, I've configured it to "use the watch for phone audio", so that I can answer calls through the watch.
Today, however, I noticed something annoying: when I use my phone to make calls, the proximity sensor is no longer activated (the screen remains on during the phone call). Did anyone notice the same problem? Any workarounds?
I'm not sure this is relevant, but my phone is an HTC One M8 running Android 6.0 (Google Play Edition).
Thanks!
Click to expand...
Click to collapse
Same here! Huawei watch and Droid Maxx 2 running Marshmallow. I thought it was Android Wear until I stumbled upon this post. This so negatively impacts the user experience that I'm considering returning the watch.
I've put up with the proximity sensor malfunctioning once i take or make a call, the touch screen not working [restarting it solves the problem, after i had the screen replaced due to complete failure to function, which seems to be evident of a software issue] and the UI keeps crashing. I know this isn't a very smart question, but would rooting to the right ROM solve all these bugs? These seem to be a software issue, but again; I'm nowhere close to an expert on this. Also, what I mean by the proximity sensor malfunctioning is that when the phone is in a call, the screen doesn't turn on even if it isn't close to my ear or anything else.
I have a weird issue with my A2 Lite.
I tried couple of ROMs so far and it's all the same.
When I receive a call and answer it, I bring the phone to my ear and I can see that display goes off - that's good. But, despite keeping the phone close to my ear, the flash light turns on, bt or even airplane mode so it disconnects the call, it changes the screen brightness or mutes the mic during the call. It's like touch sensor was alway on with display off, so I can't even see what I'm touching and switching.
I even went back to stock MIUI to be able to run system check with *#*#64...etc. and proximity sensor works fine.
My problem is similiar to this one: https://forum.xda-developers.com/mi-a2-lite/help/lockscreen-notification-sound-proximity-t3867872.
This drives me crazy!!!
Did anyone have this problem or knows some tricks to fix it (beside smashing the sh..t on the wall)?
I experience the same thing sometimes with stock rom
keyone72 said:
I experience the same thing sometimes with stock rom
Click to expand...
Click to collapse
That - I didn't expect...
But it has to do something with the Android or kernel maybe. How does it come, that screen is being turned off but not locked (meaning insensitive for touches)?
Weird...
And I'm almost sure, it wasn't like this before... before I installed one of custom ROMs (Arrow maybe). But since then I even went back to stock Pie, so if any firmware/kernel manipulation caused it, with stock - it should've fixed.
I'm starting to dislike daisies...