In all sense roms I notice that after a call sometimes the htc media link initializes and also wifi turns on. Has anyone ever had this issue?
beeroatsnp90x said:
In all sense roms I notice that after a call sometimes the htc media link initializes and also wifi turns on. Has anyone ever had this issue?
Click to expand...
Click to collapse
Never experienced this before (though I don't make phone calls that often). Try turning off HTC Gestures in Settings -> Display & Gestures. It could be that the phone's screen is turning back in before you take it away from your face and the action of you moving it away is causing screen contact and the phone is mistaking that for a 3 finger swipe. I know it sounds a bit far fetched, but I've seen weirder things happen.
Related
I'm running CM 7.0.3, and I'm having massive proximity sensor issues, t the point where the phone is becoming unusable. If I'm in a call and I don't manually shut the screen off, the following happens (constantly):
I'll feel some haptic feedback on my ear, and my voice will mute. When I look at the screen, the lock screen is up and when I unlock it, it's at the dialer screen. I'm not hitting the mute or hold button with my ear, it seems like once it gets away from the call screen, my voice is muted.
Needless to say, this is getting massively annoying. Later tonight I'm going to try to see if using a Sense based rom fixes this, but I'd much rather stick with CM. Has anyone else experienced this?
I believe there is another post on this.. you can also Google search for inspire proximity sensor adjustment - someone created an app to adjust the sensor
Sent from my Desire HD using XDA Premium App
The thread in question:
http://forum.xda-developers.com/showthread.php?t=1062561
EDIT: I haven't used the proximity sensor adjustment application that's linked in the thread as mine is working normally. If it doesn't work there's a possibility the sensor's faulty and should be replaced (I recently went through this whole thing with my old iphone 4).
Yeah, to be honest, I tried that app and it didn't seem to make much difference. I'll try calling HTC
Flashed to a sense based ROM, and the sensor seems to be working fine. Very odd, to be honest. I will say that after using AOSP for so long, I have no idea how you guys deal with Sense at all.
Well, now I have to decide: I can live with Sense, or I can ship my phone back to HTC and be without a device for 2 weeks. Going to try out the proximity sensor app again, but it didn't seem like any setting made a difference, but it could be that I just don't know what I'm doing with it.
Check under Settings>Call Settings and put a check mark in the "Always use proximity" box. It says it's to help with prox. sensor screen locking when the phone is horizontal, but the CM7-based ROM that I was using showed the same issues and I fixed my particular issue by checking that box.
Tested with a few calls and the screen is definitely shutting off when the phone is standing or lying down.
I read up on the proximity app, and I think I have it calibrated properly at 5/6. It certainly helps, but it's definitely not perfect. Night, thanks for the advice, but yeah, that option has been checked from the start. At least the issue is tolerable now, before it would do this 10 times per call.
Funny - mine was calibrated at 10/11 by default and works pretty well. Try going up to those values. I used a local time/temperature number here, and it worked well when my finger got 1/8" or so from the phone. While I admittedly haven't measured the depth of my ear or anything, it does seem to be working well at those settings.
I think the upper threshold is where you may want to adjust. From my playing with that app, changing the lower threshold too high will make it ignore things too close to the phone and so will an upper threshold that is too low. Try lower 5, upper 11 and see what happens. Anything between lower and upper apparently triggers the sensor. (<<< speculation without documentation)
Hi,
I have this wierd problem with my sensation. I found out that if i have my camera on and it falls a sleep it wont unlock any more. no ring nothing.buttons glow but a solid black screen. The only way out is a battery pull.
It's with photo camera and video camera mode. no other apps suffer fom this.
I've tried other roms but nothing. I currently run ARHD 3.6.7
I found out on accident but it is realy annoying me now
Any of u with the same problem or ideas?
known issue with kernel. not sure which kernels. try keepscreen app to keep screen awake if using camera so it doesnt freeze
https://market.android.com/details?id=com.tni.KeepScreenLite&hl=en
Yeah, it's bricked kernel. Doesn't matter what version you use, it seems to keep on happening randomly.
knuddeknurft said:
Hi,
I have this wierd problem with my sensation. I found out that if i have my camera on and it falls a sleep it wont unlock any more. no ring nothing.buttons glow but a solid black screen. The only way out is a battery pull.
It's with photo camera and video camera mode. no other apps suffer fom this.
I've tried other roms but nothing. I currently run ARHD 3.6.7
I found out on accident but it is realy annoying me now
Any of u with the same problem or ideas?
Click to expand...
Click to collapse
Hi,
Go into Bricked Kernel post, there is a .zip file called, CAM-FIX.zip
Flash that, magic will happen =]
Thanks guys, I've all ready flashed an other kernel and it works all fine now.
CAM-FIX.zip on the other hand is only for sense 3.5 and I really prefer sense 3.0
The camfix patch is so the camera can even function in the first place, it does not fix this issue. Without the camfix, if you try to use the camera the screen just goes black and the phone freezes. This issue however is an intermittent one, where sometimes when you exit the camera you get the black screen and freeze. Doesn't happen all the time, but it's definitely the kernel at fault.
To the OP, if in your case it's only happening once the screen times out, you could always use tasker to make it not timeout when using that app?
StuartTheFish said:
The camfix patch is so the camera can even function in the first place, it does not fix this issue. Without the camfix, if you try to use the camera the screen just goes black and the phone freezes. This issue however is an intermittent one, where sometimes when you exit the camera you get the black screen and freeze. Doesn't happen all the time, but it's definitely the kernel at fault.
To the OP, if in your case it's only happening once the screen times out, you could always use tasker to make it not timeout when using that app?
Click to expand...
Click to collapse
You can try keep screen, it will keep phone up when camera is on
Sent from my HTC Sensation XE with Beats Audio using XDA App
Hi!
My Sensation has been experiencing some weird behaviours.
Although the rotation is locked on the rom (I tried several, all same issue), it still rotates. The only way to stop this is through the launcher options and force vertical mode.
It wakes up during the night, out of the blue. Nothing running, no processes waking it up.
Sometimes I'm browsing stuff (like this morning, browsing the TB backup list), and it kept going back like I pressed "Back" button.
Now, I tried several roms since, all same behaviour (Sense, AOSP, CM, etc..).
Used an app to test the sensors, they all seem to be responding accordingly, although I don't exclude a sensor issue, for some reason it shows normal behaviour in everything else. The rotation works properly as in, turning the way it should, but if it's locked, why it keeps rotating?
Did anyone ever experienced anything like this? I searched on google / xda, there's some odd cases here and there and either they ended up being sensor files being corrupted or uncalibrated.
Anyone care to shed a light on this?
Thank's a lot
Update: New sympthom, on Sense 3.6, it seems like Dock Mode is being called randomly too. This makes me consider a sort of loose contact or alike :S
Anyone?
So now lets talk real world experience of the phone interface
When it blanks the phone buttons seem to operate...
I mean a number of occasions I have lost people because I have mysteriously put them on hold...with the phone to my ear.
People are always complaining to me that I am quiet even though the phone is in the correct place on my face and incall volume is at max
Often I cannot pick up calls ...I hit the answer icon to no avail...if I flick it upscreen it works but pressing the icon is only recognised intermittently
What is it like for you?
PianoSam said:
So now lets talk real world experience of the phone interface
When it blanks the phone buttons seem to operate...
I mean a number of occasions I have lost people because I have mysteriously put them on hold...with the phone to my ear.
People are always complaining to me that I am quiet even though the phone is in the correct place on my face and incall volume is at max
Often I cannot pick up calls ...I hit the answer icon to no avail...if I flick it upscreen it works but pressing the icon is only recognised intermittently
What is it like for you?
Click to expand...
Click to collapse
have to tried to factory data reset the phone to see if that helps?
This is called the incall/proximity sensor issue and the reasons have not yet been found by xda people.
There are few fixing attempts available though which involve different strategies.
Someone lately suggested to the ViperOne team to make a tweak that allows for automatically locking the phone on call pick up as a permanent workaround fix. There was no developer response on this yet though. Its a good idea though.
The same sensor is causing another issue which is quite frustrating. On some occasions the normal method of simulated battery pull (press power for more than 15 seconds to force reboot) does not do anything unless shining a really bright light into the sensor. Apparently the prox sensor, not the light sensor.
It seems there are a few units out there which have issues with this sensor.
Another theory is that its jut the user tilting the phone until it recognizes landscape orientation and then the sensor is switched off...
I have reading the forum and tried contacting 1+7 also but they just say switch off nfc and so on but till today (1 month since I bought it ) I still have the problem . while making a call it goes on hold or connects another call or something or the other happens and the other person gets irritated as if I am doing on purpose. I am still unable to solve this will changing rom be the solution or can someone please help I am fed up with this instrument
My 2 cents... are you sure that it's a ghost touch issue? To me it seems more a proximity sensor trouble... it is possible that, while in call, screen doesn't go off (or wake up while you're talking) and your ear triggers commands at random.
Try to check that your screen remains black while in call, else you could try to reset sensors with one of the apps available on Play Store.
BTW: I had a similar problem one or two times, but maybe because I wasn't so near the phone while I was talking.
will try out can you advice reset sensors apps
jonsat said:
My 2 cents... are you sure that it's a ghost touch issue? To me it seems more a proximity sensor trouble... it is possible that, while in call, screen doesn't go off (or wake up while you're talking) and your ear triggers commands at random.
Try to check that your screen remains black while in call, else you could try to reset sensors with one of the apps available on Play Store.
BTW: I had a similar problem one or two times, but maybe because I wasn't so near the phone while I was talking.
Click to expand...
Click to collapse
will try out can you advice reset sensors apps
Issue is back again after 9.5.9 update.
IEESH said:
will try out can you advice reset sensors apps
Click to expand...
Click to collapse
Search for "Proximity sensor reset" or similar names. Usually apps like that needs root privileges, btw.
I've had problems with the screen waking up and then causing problems while in call too. This while it's still against my face. Apparently touching my face makes it go into other apps and causes problems. I've had it go into airplane mode, mute and do other weird stuff.
I've had the screen go crazy with multiple chains of taps too, especially while holding it in landscape mode.
Turning the refresh rate down to 60 Hz helped some, but the problem's still there.
I think there's something jacked in their implementation. I came from an S8 that had a curved screen and I never had the phantom tap problems I have with this thing.
Superguy said:
I've had problems with the screen waking up and then causing problems while in call too. This while it's still against my face. Apparently touching my face makes it go into other apps and causes problems. I've had it go into airplane mode, mute and do other weird stuff.
I've had the screen go crazy with multiple chains of taps too, especially while holding it in landscape mode.
Turning the refresh rate down to 60 Hz helped some, but the problem's still there.
I think there's something jacked in their implementation. I came from an S8 that had a curved screen and I never had the phantom tap problems I have with this thing.
Click to expand...
Click to collapse
Disabling double tap to wake resolved my screen wakeup during calls issue...
UPG to 9.5.10 Plz - Issue has disappeared again.
ram4ufriends said:
Disabling double tap to wake resolved my screen wakeup during calls issue...
Click to expand...
Click to collapse
I'll try that, but I don't think I have that enabled. I disabled NFC for the other tap issues and that helped some.
I really wish there was a screen calibration tool. Samsung curved screens have none of these issues.
Do you have a dirty screen protector?
This is a known bug with the proximity sensor, although, actually, I believe the root cause is something else.
Screen does go black, which indicates the proximity sensor is working and recognizes your face is near... But input is still allowed (meaning it does not lock it).
As a result, during a call your face/ear will press whatever is underneath and trigger random actions.
I believe (I hope?) that OnePlus is aware of this issue and they issue a fix.
I think it was briefly fixed for 9.5.9 and then reverted on 9.5.10 since it introduced other issues.
Quality control has been a bit subpar on the OnePlus 7 Pro builds when compared to my previous OnePlus phones...