Curious to know how many other people are having issues with their proximity sensor while using a AOSP rom. I have been using Antp's "le n00b" (lol) AOSP CM9 Kang and have been having issues with my device locking up during calls. So I started to investigate more into the problem and have tried multiple fixes, nothing seems to work. I've took it a step forward just to determine whether my proximity sensor has just recently gone bad. I restored my backup of Venom and walaa, my sensor is working normally. No lockups, or any misbehaving. Only thing I find weird is some people have the issue, and some don't. Many factors come into this, I know... But my screen would only lock up if I was in a room with dim lighting. When I was outside in the sun, worked smooth. Would really like some feedback on this if you guys don't mind. Thanks!
HTC Rezound
Try a fresh install of the latest build. Report back after lol
Sent from my aokp_tenderloin using Tapatalk 2
antp121 said:
Try a fresh install of the latest build. Report back after lol
Sent from my aokp_tenderloin using Tapatalk 2
Click to expand...
Click to collapse
Lol will do. I got a replacement on the way anyway, but I will surely report back on this with my current rezound. Thanks a lot.
HTC Rezound
luis86dr said:
Lol will do. I got a replacement on the way anyway, but I will surely report back on this with my current rezound. Thanks a lot.
HTC Rezound
Click to expand...
Click to collapse
No problem
Sent from my aokp_tenderloin using Tapatalk 2
Yup, still an issue on new build for me. Hopefully replacement has a working prox sensor.lol
Sent from my Xoom using xda app-developers app
luis86dr said:
Yup, still an issue on new build for me. Hopefully replacement has a working prox sensor.lol
Sent from my Xoom using xda app-developers app
Click to expand...
Click to collapse
It must be on your end. Mines fine. Anyways, good luck
Sent from my aokp_tenderloin using Tapatalk 2
I've got this problem too. I don't have to be in the middle of a call for my phone to freeze though. I checked with the Android Sensor app and it doesn't toggle between 0 and 9 (cm? I don't have my phone on me right now) like someone else reported. I have to turn off the screen (which takes a few seconds after pushing the power button), and then when I turn it back on the phone works normally.
Another detail I found though is that even though the display "freezes", it still accepts input. If the screen freezes, and then I press the home button, when I turn the screen off and then back on, I'll be on my home screen. Not in the app that I had running. Same with the other cap buttons, keyboard, on-screen buttons. If it was an issue with the proximity sensor, I would think the screen would just turn off and not accept input, right?
The ROM isn't at fault here, it is a hardware issue of the sensor getting dust in it. Simple as that.
Yeah, it's not Rom related. It's definitely a hardware issue and if your still under warranty I would take action ASAP. My replacement should be here tomorrow so crossing my fingers its problem free.
HTC Rezound
luis86dr said:
Yeah, it's not Rom related. It's definitely a hardware issue and if your still under warranty I would take action ASAP. My replacement should be here tomorrow so crossing my fingers its problem free.
HTC Rezound
Click to expand...
Click to collapse
Well it may not be ROM related, sure. But I don't think it's a physical problem with the hardware either. luis, you said yourself when you restored back to Venom your 'sensor is working normally' and you had no hiccups. I didn't have the problem under CleanROM DE either.
Maybe the problem is in dmeadow's kernel. It is beta after all
wildfirewolf said:
Well it may not be ROM related, sure. But I don't think it's a physical problem with the hardware either. luis, you said yourself when you restored back to Venom your 'sensor is working normally' and you had no hiccups. I didn't have the problem under CleanROM DE either.
Maybe the problem is in dmeadow's kernel. It is beta after all
Click to expand...
Click to collapse
It's happening on Venom for me now. Only difference is I can hit power button to get my screen back.
HTC Rezound
Ah, damn. Alright, maybe it was just an unfortunate coincidence that the timing for when this started happening matched up with when I started flashing the newer ROMs/kernels.
Different ROMs detect it differently. It IS a hardware issue.
Found out how to disable the sensor completely. Testing it out now. So far so good.
Edit: Sensor disabled and sticks after reboot. If anyone with sensor issues wants this mod, pm me. I want someone else to test this out.
HTC Rezound
I'll give it a shot luis!
wildfirewolf said:
I'll give it a shot luis!
Click to expand...
Click to collapse
OK, so I've made two flashable zips. One enables and the other disables the proximity sensor. Flash normally thru recovery, no wipes needed.
I've tested them both and it works flawless for me so far.
ICS Proximity Sensor Disabler
ICS Proximity Sensor Enabler
Let me know how it works for you. Thanks!
Sent from my Xoom using xda app-developers app
The proximity sensor in this phone is a problem. Mine wasn't working at all, so I got a replacement. Got it and set it up yesterday and this one works....kinda. It works mostly correctly in bright light..outdoors, in an office, etc. It doesn't work correctly in low light...at night, in my house, etc. However, I can make it work temporarily by rubbing my thumb across the top of the phone over the Verizon logo for a few seconds. That will make it work for between 10 seconds and a minute or so. It seems to be IR/heat related, as even in bright light it sometimes needs help. I think I might just going to disable this one and deal with it.
shrike1978 said:
The proximity sensor in this phone is a problem. Mine wasn't working at all, so I got a replacement. Got it and set it up yesterday and this one works....kinda. It works mostly correctly in bright light..outdoors, in an office, etc. It doesn't work correctly in low light...at night, in my house, etc. However, I can make it work temporarily by rubbing my thumb across the top of the phone over the Verizon logo for a few seconds. That will make it work for between 10 seconds and a minute or so. It seems to be IR/heat related, as even in bright light it sometimes needs help. I think I might just going to disable this one and deal with it.
Click to expand...
Click to collapse
Yeah, these sensors are horrible. Its not a show stopper, but it does suck to have these issues with a device we paid good money for.
Sent from my Xoom using xda app-developers app
Question to those who have done it, how far do you have to tear down the device to get to the sensors? Are they attached to the motherboard or are they in the display? The guides and videos I've seen revolved around replacing the display/digitizer, and I haven't been able to tell exactly where the sensors live.
Sorry luis! I went to sleep between my post and your post so didn't test last night. I'll flash it right now and get back to you on whether my display freezes anymore while I'm out today.
---------- Post added at 10:40 AM ---------- Previous post was at 10:26 AM ----------
I had my first freeze up already. I checked with the Android Sensor Box app and the proximity sensor is still registering values (0 cm if I cover it, or 9 cm if I don't, no in between).
Related
Anyone else had this problem rooted or not? I couldnt hang up the call to customer service just now to request a replacement. Ive had to turn off the screen then back on to get touch reponse to work again. Phone has never been rooted. Weird. Resets dont fix either.
Sent from my PG86100 using XDA Premium App
i have the same problem lower part of the screen becomes unresponsive randomly then goes away
surmanm said:
i have the same problem lower part of the screen becomes unresponsive randomly then goes away
Click to expand...
Click to collapse
I also noticed that the calibration gets all outta whack along with the unresponsiveness. Like u tap a link on the scteen but it thinks u tapped another link or something like that. Did u request a replacement?
Sent from my PG86100 using XDA Premium App
Visionikz03 said:
I also noticed that the calibration gets all outta whack along with the unresponsiveness. Like u tap a link on the scteen but it thinks u tapped another link or something like that. Did u request a replacement?
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
Iv seen that with the OG evo also, as well as my 3vo
Having the same problem. Probably will carry it in next week for replacement. Already took it in once and they said wait for a couple of weeks to see if HTC/Sprint release a software update. It's starting to get very annoying and unusable. Very much ruining the experience of having a powerful smartphone.
i have it too with my gsm version , the upper part of mine screen is sometimes not responsive
Visionikz03 said:
Anyone else had this problem rooted or not? I couldnt hang up the call to customer service just now to request a replacement. Ive had to turn off the screen then back on to get touch reponse to work again. Phone has never been rooted. Weird. Resets dont fix either.
Sent from my PG86100 using XDA Premium App
Click to expand...
Click to collapse
i wonder if this is related at all to the screen grounding issues which they originally had in the HTC EVO. the end result of the screen grounding issue was parts of the screen were unresposive...
i do remember they patched something in an update which fixed that issue.
i remember there was a test for the screen grounding issue but i barely remember how it worked. i'm sure there are older threads on it as it was a fairly big deal when the device first came out. the test had something to do with drawing lines or something on the screen?
might not be helfpul, but figured it was worth mentioning. i haven't had any issues on my evo 3d so its hard for me to troubleshoot and compare...
at least replacing the phone will be a decent solution until we can find out more about this issue ... sad it seems to be fairly common.
I am having an issue with my phone not reacting correctly to the proximity sensor. When I am in call, the screen shuts off when I put the phone to my face like it is supposed to, however when I remove it from my ear the screen doesn't come back on. I tested the sensor with an app called sensor list, and it is without a doubt working correctly. I have a custom kernel installed. Could that be causing my issue, or is the software just bugged?
Stock, rooted, unlocked, what Rom? Info would be a good starting place.
Sent from my ADR6425LVW using XDA
Stock rom, debloated, rooted, and incredikernel beta 6.
I ordered a new digitizer to replace my mildly scratched one and would like to replace the prox switch while I have it apart. does anyone have any clue where I can get a replacement? Or better yet, what is the exact switch I need. I have an old d1 somewhere, can I Frankenstein that into my rezound to make some abomination?
I recommend testing the sensor itself to rule out whether it is a hardware of a software issue. There are many proximity sensor tester apps in the Play Store.
Edit: NVM, it looks like you already did test it. Disregard this post.
This is what part the Elixir app reads on my Rezound; the phone hardware revision B rather than XA if that has any impact (likely not for this simple part, check under the battery to make sure you have a B model phone if you wish):
when you bring "her" back to life you can watch this
http://www.youtube.com/watch?v=_pQUn2GTymw&feature=youtube_gdata_player
griffstert said:
I recommend testing the sensor itself to rule out whether it is a hardware of a software issue. There are many proximity sensor tester apps in the Play Store.
Edit: NVM, it looks like you already did test it. Disregard this post.
Click to expand...
Click to collapse
the op was from a while back, I have since got my sensor to fail the test. Thus I will replace it. I don't want to send my phone in only to be received by someone in a bad mood who will charge me 650 bucks for unlocking my bootloader. And they will send me a refurbished device that will probably have more problems than this one.
PhantasmRezound said:
This is what part the Elixir app reads on my Rezound; the phone hardware revision B rather than XA if that has any impact (likely not for this simple part, check under the battery to make sure you have a B model phone if you wish):
Click to expand...
Click to collapse
Thanks, I will be in touch with them to find a vendor.
johnwaynegacy said:
the op was from a while back, I have since got my sensor to fail the test. Thus I will replace it. I don't want to send my phone in only to be received by someone in a bad mood who will charge me 650 bucks for unlocking my bootloader.
Click to expand...
Click to collapse
Despite the fact that nobody has actually had that happen yet???
So you will void the warranty instead... so if you really break it, you don't have no repair option at all.
And they will send me a refurbished device that will probably have more problems than this one.
Click to expand...
Click to collapse
This makes more sense... but even then there, it is not 100% you will get a refurbed unit or that you will have problems with what you get.
BTW, my stock unit doesn't turn the display on when you take your face away from the screen. I always have to press one of the volume keys to get the display back on (easier than reaching the power button)
My display stays off as well. Does not seem hardware related to me.
Sent from my ADR6425LVW using XDA
My display stays off as well. Noticed this today when trying to switch to speakerphone. Just press the power button nothing really wrong with it.
krelvinaz said:
Despite the fact that nobody has actually had that happen yet???
So you will void the warranty instead... so if you really break it, you don't have no repair option at all.
This makes more sense... but even then there, it is not 100% you will get a refurbed unit or that you will have problems with what you get.
BTW, my stock unit doesn't turn the display on when you take your face away from the screen. I always have to press one of the volume keys to get the display back on (easier than reaching the power button)
Click to expand...
Click to collapse
I have already had this phone apart and the little green void sticker is already gone.
I guess if everyone is having this same issue, it must be a design flaw. I doubt I will correct it by changing the sensor. The screen is supposed to come back on when you remove the phone from your face, unless that's a software bug in sense.
The real question is does it work in 100% stock Gingerbread no custom anything. If it does work then it could be a app or the kernel if it doesn't work then its hardware.
How is this such a hard concept for people to grasp?
Sent from my ADR6425LVW using XDA
jazzyjames said:
The real question is does it work in 100% stock Gingerbread no custom anything. If it does work then it could be a app or the kernel if it doesn't work then its hardware.
How is this such a hard concept for people to grasp?
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
If you look at my op I was on 100% stock gingerbread other than a kernel. If everyone has the same problem, yes it is hardware related, but it is a design flaw. It is unlikely that everyone who posted has a bad proximity sensor.
Yes I did read and as you just posted your not on 100% pure stock. You said stock rom, but never said stock ics or gingerbread but like I said best way to test is go 100% stock no mods at all and even go the route of no extra apps, it may seem extreme but its crazy all apps that can cause issues.
Sent from my ADR6425LVW using XDA
Here is the real question. Does your screen always go off when you cover the sensor. Mine does not. I have to try several times, and when it finally does turn off, it only sometimes comes back on. other times, I have to press the power button. Who else is experiencing this?
Mine acts as if it had no proximity sensor at all. Programs say it does, but it always reads that something is zero cm. away from it... power button is the only way I've found to turn the screen back on.
I bet a lot of HTC phones have this issue. When I searched the number for this sensor, a lot of their phones came up as results. I think we are all running bugged hardware.
I know this may look like a "first post" SEARCH kind of thread but I'm a long time lurker I am on a rooted ICS CleanROM 4.5 and after much diagnostics I've concluded there is a physical issue with the phone that is causing my prox sensor to fail. I have the typical symptoms most of you have with bad prox sensors- pull the phone away and it may come back on or you push power on and it immediately turns back off. What is the point of having a phone with simultaneous voice/data if you can't use your apps on calls?
I know many have had some success with blowing dust out but that's not the case here. When I push down on the upper right hand corner of my screen with Androsens fired up my prox sensor will start working perfectly. As i start using the screen the prox sensor will go dead again until I push hard on the upper right of the LCD. This appears to be a build flaw in these phones and I'm out of warranty and sick of it so I want to kill the feature.
Is there ANY way to completely disable the phone from turning the LCD off during calls? Good solution for those of us with this issue that are done dealing with the hardware with no resolution in sight. I know there was a property you could drop into the build prop on GB of "gsm.proximity.enable=false" but this doesn't have any effect in ICS. Thoughts?
Have this same problem it drives me up the wall. Not sure how to fix it.
Sent from my ADR6425LVW using xda app-developers app
Yeah I've seen a lot of thread with people ditching the rezound all together because of this one stupid issue... seems like something that can be management in the software
Well, if you are out of warranty, you could always open it up and clean it. I have to do it about every two months.
AZKlaus said:
I know this may look like a "first post" SEARCH kind of thread but I'm a long time lurker I am on a rooted ICS CleanROM 4.5 and after much diagnostics I've concluded there is a physical issue with the phone that is causing my prox sensor to fail. I have the typical symptoms most of you have with bad prox sensors- pull the phone away and it may come back on or you push power on and it immediately turns back off. What is the point of having a phone with simultaneous voice/data if you can't use your apps on calls?
I know many have had some success with blowing dust out but that's not the case here. When I push down on the upper right hand corner of my screen with Androsens fired up my prox sensor will start working perfectly. As i start using the screen the prox sensor will go dead again until I push hard on the upper right of the LCD. This appears to be a build flaw in these phones and I'm out of warranty and sick of it so I want to kill the feature.
Is there ANY way to completely disable the phone from turning the LCD off during calls? Good solution for those of us with this issue that are done dealing with the hardware with no resolution in sight. I know there was a property you could drop into the build prop on GB of "gsm.proximity.enable=false" but this doesn't have any effect in ICS. Thoughts?
Click to expand...
Click to collapse
How are you out of warranty? The phone hasn't been out for a year yet...
Mine just started doing this after I updated to the leaked global ruu. Don't talk on the phone much so haven't looked much into it.
Sent from my ADR6425LVW using Tapatalk 2
AshtonTS said:
How are you out of warranty? The phone hasn't been out for a year yet...
Click to expand...
Click to collapse
? I'm 3 months out of warranty.
Sent from my ADR6425LVW using xda premium
RomsWell said:
? I'm 3 months out of warranty.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
Not possible. Htc warranty is 1yr from original purchase date of phone. Phone came out last November
Sent from my ADR6425LVW using Tapatalk 2
This is beyond cleaning, the phone is immaculate and I already did that dance. And again, this is an asinine design flaw- I'm perfectly okay with (as I'm sure many of us would be) to just manually turn on and off the screen while on a call. There has to be a way to nuke this
Is this a general ICS issue or just certain ROMs?
If it's because anything official and didn't happen on GB, wouldn't it be able to be fixed with an OTA?
No this is sadly 100% a hardware issue being that the sensor will come back on when pressing down on the upper right of the screen. I've seen other posts where pushing on the screen has temporarily reengaged this as well. The "cleanings" that are being done I'm confident have nothing to do with the cleaning itself but of putting pressure in the right spots while cleaning.
Is this potentially something that could be addressed with the new open source projects coming out?
On Gingerbread, you could edit & add this to your build prop to disable the proximity sensor:
gsm.proximity.enable=false
Problem is, this doesn't work on ICS. I've read people Hex editing files in order to disable it while running ICS.
Off topic: Finally hit 1000 posts!
HTC Rezound
nrfitchett4 said:
Not possible. Htc warranty is 1yr from original purchase date of phone. Phone came out last November
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Mine is out of warranty too. It was a replacement for my thunderbolt, it cane with a 90 day warranty.
Sent from my ADR6425LVW using Tapatalk 2
luis86dr said:
On Gingerbread, you could edit & add this to your build prop to disable the proximity sensor:
gsm.proximity.enable=false
Problem is, this doesn't work on ICS. I've read people Hex editing files in order to disable it while running ICS.
Off topic: Finally hit 1000 posts!
HTC Rezound
Click to expand...
Click to collapse
Haha and that 1000 was a repost I mentioned the GB fix in the original post and that's what's driving me nuts about this! There has to be a build prop toggle that I can use.
I think I've figured out how to disable the sensor. Seems to work for me on Venom Rom. If someone wants to test pm me.
HTC Rezound
roosxter said:
Mine is out of warranty too. It was a replacement for my thunderbolt, it cane with a 90 day warranty.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
If you pay for the $6.99 insurance you still have warranty. Its extended warranty that I believe is for as long as you own the phone and switches to any other phone you get as a replacement. I've gone from Thunderbolt-Bionic-Rezound-S3 all with same warranty. So as long as you pay for that you still have warranty and are all good if you don't pay for that then you still have warranty threw HTC till November.
Sent from my Sense 4 ICS Rezound
This still work on ics
Sent from my ADR6425LVW using xda premium
cflo360 said:
This still work on ics
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1874297
HTC Rezound
i Know but this code or script still works gsm.proximity.enable=false
cflo360 said:
i Know but this code or script still works gsm.proximity.enable=false
Click to expand...
Click to collapse
On gingerbread. Didn't work on ICS for me.
HTC Rezound
Ok, so me and another guy did some tests with the onex+ touch screen and found out why so many of us have issues with scrolling, we need as many people as possible to report the issue to HTC so we can get a hotfix, i dont think HTC realize at the moment, this is what to do, type in on th phone keypad *#*#3424#*#*. choose more, then choose the screen drawing option, dont draw, just touch it with your finger and see if there is a white dot, if there isnt then touch another part of the screen and then see if the previous touch shows up, if so you have the same software issue as many of us, its quite possible that its a major hardware flaw and cant be rectified in which case HTC will have to do mass repairs or recall, we are not going to stand for this at a price of £500, if you have this issue please report on HTC website, either email or chat or phone call, it needs to be done or we will have scrolling issues time and time again on each update.
What touch screen issue are you talking about? I've not heard anything about it from anyone on here. I think mine is fine. Or maybe I haven't noticed it yet.
Sent from my HTC One X+ using xda app-developers app
I Did what u suggested and indeed... Dots appeared in places where I didn't even touch the screen... And yes ive also noticed that when I want to Swype through f.ex. tapatalk forum i verry often just pres thread instead of swype through them...
Wysyłane z mojego HTC One X+ za pomocą Tapatalk 2
Krzysiec said:
I Did what u suggested and indeed... Dots appeared in places where I didn't even touch the screen... And yes ive also noticed that when I want to Swype through f.ex. tapatalk forum i verry often just pres thread instead of swype through them...
Wysyłane z mojego HTC One X+ za pomocą Tapatalk 2
Click to expand...
Click to collapse
Soon as you get the chance report issue to HTC, more people the better.
sjred_uk said:
What touch screen issue are you talking about? I've not heard anything about it from anyone on here. I think mine is fine. Or maybe I haven't noticed it yet.
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
Me and another guy discovered it, trying to sort out our scrolling problems, as of now theres an issue. 4 people have the exact same issue so far and i bet theres more.Test your screen and you will no for sure. Its causing random clicks and rubberbanding when scrolling, its not all the time and probably wouldnt notice it unless your a heavy user(always on your phone)
you have the same software issue as many of us, its quite possible that its a major hardware flaw
Click to expand...
Click to collapse
Yup, I noticed it too. It's gone now, since I switched over to CM10. It makes no sense! (See what I did there? )
I think I'm that other guy OP was talking about. I have this scrolling issue where stuff on screen are being selected or clicked on accidentally instead of scrolling though them - but never had this problem before I updated to the most recent firmware, so I'm pretty sure this is a software thing.
Best we could do right now is report to HTC.
---------- Post added at 11:18 PM ---------- Previous post was at 11:17 PM ----------
KaiUno said:
Yup, I noticed it too. It's gone now, since I switched over to CM10. It makes no sense! (See what I did there? )
Click to expand...
Click to collapse
Oh, so switching to a custom rom solves it. Must learn about those stuff then.
Had very similar problem on the sensation. Ended up being a bad ground. It was easy to fix because you could take the cover off. Small piece of aluminum foil or solder fixed it like new. http://forum.xda-developers.com/showthread.php?p=17072026#post17072026
Also i assume you guys are talking about the international version..? Anyone with US ATT version experience this issue yet?
Rant: These forums need separating... Nothing is interchangeable between the two phones..
nugzo said:
Had very similar problem on the sensation. Ended up being a bad ground. It was easy to fix because you could take the cover off. Small piece of aluminum foil or solder fixed it like new. http://forum.xda-developers.com/showthread.php?p=17072026#post17072026
Also i assume you guys are talking about the international version..? Anyone with US ATT version experience this issue yet?
Rant: These forums need separating... Nothing is interchangeable between the two phones..
Click to expand...
Click to collapse
It would be nice to know if the problem shows its ugly head on the lte/4g versions, its def got to be reported, if its hardware they will have to recall or fix them, and they cant turn away people who are rooted or have custom roms if it hardware. Hi sharpshooterr, yes op is you, i couldnt remember your name untill i seen it lol. Same test on the onex with android 4.1.1 with sense 4+ shows the screen is perfect, theres not even any lag when drawing either. Things like this shouldnt be getting through quality control on high end flagship devices, really shows HTC is going down hill fast.
As of now i think your testing might be a little flawed, you are using the wrong test. This is a line draw test, not a touch test. Its liable to act the same for everyone when just touching. How does it draw for you? Draws fine for me. the thing about touching then touching again and both dots show is not any sort of test IMO because again this is a LINE DRAW test. Maybe download some of the touch and multitouch tests from the market and try those.
Dont get me wrong, if there is something wrong then it needs to be addressed. I applaud you for trying to bring it public. You should look into some other tests though. HTC will not pay any attention to this issue if its brought to them like this. Get some more info, more tests, different tests.. The more the merrier
With the information i've read here it does sound software related though.. custom roms can fix it and firmware updates can break it. Doesn't sound hardware to me.
nugzo said:
As of now i think your testing might be a little flawed, you are using the wrong test. This is a line draw test, not a touch test. Its liable to act the same for everyone when just touching. How does it draw for you? Draws fine for me. the thing about touching then touching again and both dots show is not any sort of test IMO because again this is a LINE DRAW test. Maybe download some of the touch and multitouch tests from the market and try those.
Dont get me wrong, if there is something wrong then it needs to be addressed. I applaud you for trying to bring it public. You should look into some other tests though. HTC will not pay any attention to this issue if its brought to them like this. Get some more info, more tests, different tests.. The more the merrier
With the information i've read here it does sound software related though.. custom roms can fix it and firmware updates can break it. Doesn't sound hardware to me.
Click to expand...
Click to collapse
Ok, ive tested the same drawing test screen on the onex, doesnt happen, soon as you touch the screen it registers under your finger, the screen has to register the first touch in that same spot your finger is on no matter what your doing, this is why its clicking in other places and rubber banding when your scrolling, its registering to late, and the line drawing lags like f---k. When your drawing your keeping your finger on it so its going to register eventually in the place you want it, its no good when your scrolling. Ive reproduced the same in gesture search, and again on the onex it doesnt do it in gesture search. Keep in mind there both running android 4.1.1 with 4+ sense, the only screen difference is the glass. If what your saying is true then the onex should be the same way so i know its not down to he test app along with the other tests ive done. Eitherway theres def a problem with scrolling.Your probably right about HTC not doing anything.EDIT: Ive decided to refund or sell it and carry on using the onex, it just seems faster, battery last longer.
boe323 said:
It would be nice to know if the problem shows its ugly head on the lte/4g versions, its def got to be reported, if its hardware they will have to recall or fix them, and they cant turn away people who are rooted or have custom roms if it hardware. Hi sharpshooterr, yes op is you, i couldnt remember your name untill i seen it lol. Same test on the onex with android 4.1.1 with sense 4+ shows the screen is perfect, theres not even any lag when drawing either. Things like this shouldnt be getting through quality control on high end flagship devices, really shows HTC is going down hill fast.
Click to expand...
Click to collapse
The problem does indeed show its ugly head on att lte/4g phone also.
Sent from my HTC One X+ using xda app-developers app
dantegl36 said:
The problem does indeed show its ugly head on att lte/4g phone also.
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
You received an OTA from AT&T?
Kraizk said:
You received an OTA from AT&T?
Click to expand...
Click to collapse
No... But thinking on it I may be a bad test subject since my phone is now rooted, bl unlocked, and running an insertcoin rom. I've had the phone for about a week.
Sent from my HTC One X+ using xda app-developers app
dantegl36 said:
No... But thinking on it I may be a bad test subject since my phone is now rooted, bl unlocked, and running an insertcoin rom. I've had the phone for about a week.
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
With the exception of insert coin my phone is the same. I do not have this problem. Something is wrong with the rom, your kernel or your phone if you are having touch screen issues.
I am unlocked, running elegancia, rooted. I do not have TWRP flashed as there are issues charging when the battery dies. Even when i did I never had touch screen issues.
Multi touch is useless also, only 2 fingers register, on a brandnew high end device and it only supports 2 finger multitouch, oh yes, i have a touch screen app that actually registers a soon as you touch the screen, but its only one app, all others i tested do as i described so i really do not know what to think, its def not hardware, its down to the software, we should get 4.2.1 soon and hopefully it will be gone, as the op said, i dont think HTC will do anything, especially now i found an app that makes the touch work as it should. So, basically, dont worry to much, its not the hardware. Ive boxed my onex+ back up and im using the onex untill new OS, i might even flash stock nexus 4 OS on the onex.
boe323 said:
Multi touch is useless also, only 2 fingers register, on a brandnew high end device and it only supports 2 finger multitouch, oh yes, i have a touch screen app that actually registers a soon as you touch the screen, but its only one app, all others i tested do as i described so i really do not know what to think, its def not hardware, its down to the software, we should get 4.2.1 soon and hopefully it will be gone, as the op said, i dont think HTC will do anything, especially now i found an app that makes the touch work as it should. So, basically, dont worry to much, its not the hardware. Ive boxed my onex+ back up and im using the onex untill new OS, i might even flash stock nexus 4 OS on the onex.
Click to expand...
Click to collapse
To get the device to register more than 2 fingers go into settings -Display, gestures & buttons - turn off under gestures - HTC gestures (uncheck) this will give you up to 10 multitouch points.
ihavoc said:
To get the device to register more than 2 fingers go into settings -Display, gestures & buttons - turn off under gestures - HTC gestures (uncheck) this will give you up to 10 multitouch points.
Click to expand...
Click to collapse
I think what he said is absurd, I didn't disable HTC gestures and enabled "show touches" under developer options and the screen picks up my 10 fingers.
saibz said:
I think what he said is absurd, I didn't disable HTC gestures and enabled "show touches" under developer options and the screen picks up my 10 fingers.
Click to expand...
Click to collapse
wow absurd huh? I can confirm that it is NOT absurd and works the way he posted it... even if you hit show touches in development, and leave htc gestures checked, none of the multitouch testing apps pick up more than 2 touches... even though you can see more, they dont register as touches in apps and games.. So... in order to have the full 10 point multitouch, no matter how absurd you think it is, HTC gestures must be unchecked.. Google it
nugzo said:
wow absurd huh? I can confirm that it is NOT absurd and works the way he posted it... even if you hit show touches in development, and leave htc gestures checked, none of the multitouch testing apps pick up more than 2 touches... even though you can see more, they dont register as touches in apps and games.. So... in order to have the full 10 point multitouch, no matter how absurd you think it is, HTC gestures must be unchecked.. Google it
Click to expand...
Click to collapse
You misunderstand, I'm saying that it's absurd that boe323's saying the device can only support up to two touches and multi-touch is useless. Since you yourself said it will register up to 10 touches with the correct setting then it IS absurd that he claims it can only pick up two. Even the HTC gesture settings clearly says 3 finger-touches so that in itself made his statement of only two-touch support absurd.
It seems that you think I'm disagreeing with ihavoc, you should improve your reading comprehension.
so I've unlocked my boot loader and am running the latest INFECTION rom by neo.
I've noticed, probably for the last couple months at least, that if my phone vibrates a lot (ex, in vibration mode, getting alerts a lot from instant message, or toggling vibration in status bar toggle back and forth), each time it gets weaker and weaker.
but after a while (possibly hours, could be less or more, Idk), it gets stronger. at least until it starts being used again, then it gets weaker as it is being used.
I've been running custom roms pretty much since I started using this phone, in November '12.
so the question, is this a hardware problem, or could it be fixed going back to stock?
if hardware, is replacing the motor a viable solution? is it soldered to the main board?
I appreciate any input on this matter, thanks!
Sent from my Infected Rezound using xda app-developers app
mvmacd said:
so I've unlocked my boot loader and am running the latest INFECTION rom by neo.
I've noticed, probably for the last couple months at least, that if my phone vibrates a lot (ex, in vibration mode, getting alerts a lot from instant message, or toggling vibration in status bar toggle back and forth), each time it gets weaker and weaker.
but after a while (possibly hours, could be less or more, Idk), it gets stronger. at least until it starts being used again, then it gets weaker as it is being used.
I've been running custom roms pretty much since I started using this phone, in November '12.
so the question, is this a hardware problem, or could it be fixed going back to stock?
if hardware, is replacing the motor a viable solution? is it soldered to the main board?
I appreciate any input on this matter, thanks!
Sent from my Infected Rezound using xda app-developers app
Click to expand...
Click to collapse
it could be a couple of things...if this has been an ongoing thing since you started flashing last year...it may be roms as some have different haptic settings...but if its just very recent the hardware could be failing or it loosened itself outta the housing in the inside....i know a few people on here who have changed their motors and where they got it...its on either the rezound general, q&a, or accesorries thread
REV3NT3CH said:
it could be a couple of things...if this has been an ongoing thing since you started flashing last year...it may be roms as some have different haptic settings...but if its just very recent the hardware could be failing or it loosened itself outta the housing in the inside....i know a few people on here who have changed their motors and where they got it...its on either the rezound general, q&a, or accesorries thread
Click to expand...
Click to collapse
well I don't remember exactly when it started, but I remember realizing that the vibration would get weak if used too often. I suppose it happened all at once, but it might have been gradual, and I only just noticed it once it reached a certain threshold.
I'll see if I can find the threads you're talking about. but if you find them first, you could post them
Ya sounds like its hardware related...give me a little and I'll dig the links up for you...I'm in the process of packing as I'm moving over 3000 miles away from where I currently am on Saturday
Sent from my Rezound using xda app-developers app
---------- Post added at 02:40 PM ---------- Previous post was at 02:27 PM ----------
http://forum.xda-developers.com/showthread.php?t=2191028
Need a Replacement Vibrator Motor
This guy here bought a new motor for is...this is the link I was referring to
Sent from my Rezound using xda app-developers app
REV3NT3CH said:
Ya sounds like its hardware related...give me a little and I'll dig the links up for you...I'm in the process of packing as I'm moving over 3000 miles away from where I currently am on Saturday
Sent from my Rezound using xda app-developers app
---------- Post added at 02:40 PM ---------- Previous post was at 02:27 PM ----------
http://forum.xda-developers.com/showthread.php?t=2191028
Need a Replacement Vibrator Motor
This guy here bought a new motor for is...this is the link I was referring to
Sent from my Rezound using xda app-developers app
Click to expand...
Click to collapse
thanks! looked on eBay and ordered one for less than $4, sounds like a straight forward install with only 6 screws.
it'll be nice to have reliable haptic feedback/silent notifications again.
Sent from my Infected Rezound using xda app-developers app
I have experienced the same symptoms, and I'm running the stock Sense 3.6 ROM (rooted). But for me, it's on and off: it'll do this for a couple of days and then be fine for several weeks. I'm not worried about it anymore. At this point it's been going on for almost a year, I'd say, and vibration hasn't ever fully stopped working in all that time.
So that at least confirms that it's not ROM specific.
El Schisne said:
I have experienced the same symptoms, and I'm running the stock Sense 3.6 ROM (rooted). But for me, it's on and off: it'll do this for a couple of days and then be fine for several weeks. I'm not worried about it anymore. At this point it's been going on for almost a year, I'd say, and vibration hasn't ever fully stopped working in all that time.
So that at least confirms that it's not ROM specific.
Click to expand...
Click to collapse
It's never come to a dead stop, it's just been extremely week at times.
I'm really hoping it's not the main board failing to supply the right power to the motor.
So what happened, the motor I got on eBay was DOA (tested it with strands of wire as probes). My old motor turned on at a couple volts, but the other one was completely dead. (Unfortunately I took my rez apart twice cause I expected it to work, lol).
I did a stupid thing I suppose, I tried to use my old motor's brushes on the new motor (after accidentally opening the broken one up and seeing it spun with my test leads). Long story short I ruined my original motor, so I have absolutely 0 haptic/vibration on my phone right now. Let me tell you, it's really annoying! (Especially pressing back )
Well I got a refund from the seller and bought a new one yesterday but it won't be shipped till Monday.
Sent from my Infected Rezound using xda app-developers app
mvmacd said:
well I don't remember exactly when it started, but I remember realizing that the vibration would get weak if used too often. I suppose it happened all at once, but it might have been gradual, and I only just noticed it once it reached a certain threshold.
I'll see if I can find the threads you're talking about. but if you find them first, you could post them
Click to expand...
Click to collapse
Thanks again! Just got a new motor installed and it works great! (It's crazy awesome to have haptic feedback again)
I bought one for the HTC amaze 4g, and cut off the connector and soldered my old one on. Put some heat shrink on it and installed it, and that did the trick. Good thing there's a little bit of extra room under the back cover!
Sent from my Infected Rezound using xda app-developers app