Related
I have noticed a major heating sometimes when making a phonecall, and I mean it becomes really hot...
Im not using the GPS what seems to be causing overheating to some users.
also please post your radioversion etc if you have this type of problems...
Make sure you don't hold the phone near where the battery is. If you look at the manual you will be exposed to dangerously high radiation levels! If you cover it with your finger or hand the phone module goes into high power mode which could account for the heat problem.
Well yes I did some investigating and it does not happen always. I think it could be happening when taking a phone call after charging. By this I don’t mean it’s hot when unplugging the device, it keeps getting hotter and hotter while speaking.
topspeclt said:
Make sure you don't hold the phone near where the battery is. If you look at the manual you will be exposed to dangerously high radiation levels! If you cover it with your finger or hand the phone module goes into high power mode which could account for the heat problem.
Click to expand...
Click to collapse
What, my package and manual are put away. Sorry, I didn’t understand 100%, where I can’t place my finger exactly?
I looked at the manual and did not find anything unusual… What did you mean?
There is a wiki nearby, with links to the on-line manuals
(the part below the battery is where the antenna is )
Ok now that you said antenna I found the part from the manual, if you look at the previous post he says only don’t hold your finger near the battery…. The battery is ½ of the phone…
But seriously am I the only one that thinks this is TOTALLY crazy that if you hold your phone normally from the bottom half you will be exposed to DANGEROUS LEVELS OF RADIATION??? I have had mobiles for 15 years and this is the first one that cant be held in your hand without looking how you hold it…
Are others also experiencing overheating sometimes?
Yep, I said 'battery' - if you look at the picture in the manual (page 10 - see attachment below). The danger zone is bottom 1/3 of the back surface area.
As far as i'm concerned this device should not have had certification and approval for use because NORMAL handling includes the bottom part of the phone. They expect you to be at least 1.5cm away from it too so in practical terms it is extremely difficult and inconvenient to hold. If you hold the top part your palm will cover or get near the bottom anyway so their constraint is ridiculous.
I wasn't aware of this when I first used the phone and I remember my fingers getting hot with a sharp pain.
This device should therefore NOT have safety approval because the context of operation does not include normal and reasonable handling.
So you have to ask yourself: is the HTC Touch Pro worth getting cancer over?
Yes I found that page after I searched the manual "antenna"... That just sounds crazy to me...
But still I don’t know did the SERIOUS overheating I had resulted from that. I couldn’t replicate it... It could be it was caused by the charging before I answered.
I have to pay more attention to that, because I think I had it happen before also.
excuse me, topspeclt, but if you are that worried, why do you use a mobile phone
The top of the phone got really hot. The steel around the camera lens was so hot I could not keep my finger over it… I don’t know, am I the only one experiencing this type of behaviour?
karloe said:
excuse me, topspeclt, but if you are that worried, why do you use a mobile phone
Click to expand...
Click to collapse
I used a Nokia N73 prior to this and no probs. So I'm in for a little dosage. But the handling contraint with the TP is a joke. I end up using the headset now because I can't maintain the ridiculous holding position without receiving hazardous SAR levels.
My observation is one that affects ALL users of the HTC TP and not necessarily other brands.
Had I known this BEFORE I bought the HTC TP I would have skipped it. Damn good for nothing 'Reviewers'.
Loco5150 said:
The top of the phone got really hot. The steel around the camera lens was so hot I could not keep my finger over it… I don’t know, am I the only one experiencing this type of behaviour?
Click to expand...
Click to collapse
That doesn't sound right at all. My TP doesn't get that hot. You might want to swap it (if you can) or call HTC support.
I have to duplicate it and see when exactly it happens…
I’ve noticed it happening few times, but didn’t pay that much attention to it because I use the HF when I’m not home. I started to use that a year ago when there was more talk about the radiation. I talk about 2hrs a day, so the tumours are probably on their way already. Its much more convenient anyway to use the HF.
I got full warranty so I will chance the device when I have confirmed this.
I have to say also that I came from Kaiser WAY too soon… I should have given the real cooks and wizards of XDA few months to find and fix the major bugs for HTC (mind you, they are doing it for FREE to them). I just got a too good of a deal; I got this device almost for the price of my old Kaiser.
No one is experiencing heating around the camera flash/lens area when talking?
Plase confirm so I know do I need to return the device.
I have the same problem sometimes. But it is not conected to making phonecalls. I expreienced this temperture phenomen while browsig the web (wifi) and I think some other situations.
I'll keep an eye on that problem and let you know when it happens again.
I had this problem with my xda orbit 2 as well (when using tomtom while the phoen was plugged in for chargching)
Loco5150 said:
The top of the phone got really hot. The steel around the camera lens was so hot I could not keep my finger over it… I don’t know, am I the only one experiencing this type of behaviour?
Click to expand...
Click to collapse
Perhaps a visit to HTC service centre?
I haven't had this extreme heating yet.
The TP becomes warm while charging, GPS use, Wifi, and even calls, but not to that extend that you can burn your fingers on the lense area.
I think your TP has a hardware problem.
Loco5150 said:
No one is experiencing heating around the camera flash/lens area when talking?
Plase confirm so I know do I need to return the device.
Click to expand...
Click to collapse
My first TP have battery problem and really heat up at the camera metal area when using call/apps. I got a replacement and the new unit don't heat up so fast or so much.
First of all, I don't think that you can possibly expose yourself to any dangerous levels of radiation, no matter how you hold your TP. The SAR tests are done anyway with maximum transmit power, so if you hold your phone from the bottom part and so impair the reception the phone gets, you can only get the official specified SAR levels at most. It does increase battery usage (hence not recommended), as the phone needs to use more transmit power, but the SAR levels are definitely safe - always at or below spec. The design were the phone antenna is at the bottom of the phone is actually very advantageous from SAR point of view, because the antenna element is further away from your brain --> less radiation. However, I do agree that for best reception (holding the phone from the upper part) the handling of the phone is a bit awkward. HTC probably just put the "dangerous levels of radiation" warning there to keep off any possible Americans waiting to sue their a**
Also, looking at the back part of my TP, it seems that the Wifi and GPS antennas are at the top of the phone, so getting hot around the camera lens/upper area while using these features should be expected. Again, I think this is actually quite a good setup, as the phone and wifi/gps antennas are as far away from each other as possible, thus interference between different antennas is kept minimal.
Oh yeah, and you should definitely not burn your fingers on your phone, there's something wrong if you really did (it can get quite warm, but not that hot).
Just my 0.02
My TP aint that warm, but it does get a little warm when playing games but not hot, only a bit warm.
Time to put fans into mobile phones
I don't know if this is just an issue with me or if others are experiencing the same issue.
for some reason my proximity sensor is VERY sensitive... for example if I move my face just 1/2 and inch from the screen my screen turns on and I either press "Mute" or "Speaker" with my cheek OR i hang up on the person I'm calling when I place the phone back against my face.
This happens about 50% of the time... so every other call I make has this issue.
I don't know if I can change the sensitivity or the length of time before the screen turns on.
I'm coming form the Eris/D1/DX/Fascinate and I never had these issues with my older phones.
Any advice or Steps to fix this would be greatly appreciated.
Plz Advise
Happens to me too, but I don't manage to hang up or mute the calls normally. I'd love a solution as well!
Magicadder said:
I don't know if this is just an issue with me or if others are experiencing the same issue.
for some reason my proximity sensor is VERY sensitive... for example if I move my face just 1/2 and inch from the screen my screen turns on and I either press "Mute" or "Speaker" with my cheek OR i hang up on the person I'm calling when I place the phone back against my face.
This happens about 50% of the time... so every other call I make has this issue.
I don't know if I can change the sensitivity or the length of time before the screen turns on.
I'm coming form the Eris/D1/DX/Fascinate and I never had these issues with my older phones.
Any advice or Steps to fix this would be greatly appreciated.
Plz Advise
Click to expand...
Click to collapse
Which kernel / rom are you using? I have heard that some kernels have caused proximity sensor issues but I'm not sure if the issue others have experienced is the same as yours. I'd try a battery pull first, if that doesn't help try a different kernel and see if that fixes it. If the issue still persists, it could be a hardware issue and you might have to get the phone exchanged under the manufacturers warranty.
Sent from my Thunderbolt using Tapatalk
m00nshake said:
Which kernel / rom are you using? I have heard that some kernels have caused proximity sensor issues but I'm not sure if the issue others have experienced is the same as yours. I'd try a battery pull first, if that doesn't help try a different kernel and see if that fixes it. If the issue still persists, it could be a hardware issue and you might have to get the phone exchanged under the manufacturers warranty.
Sent from my Thunderbolt using Tapatalk
Click to expand...
Click to collapse
I'm using Stock firmware with bamf 4.3a Kernal
I've reset this thing too many times... installing different roms and such.. but I can verify that this is happening to another phone. My wife's phone does exactly the same thing. we purchased out tbolts on launch day ( if that helps )
The proximity sensor is located were the Verizon V is at
In between the big V is the sensor. Very hard to see go under a light a tilt the like you would if you want to find scratchs on your phone it really is between the V or I'm you can not find it. Make a phone call and get your index or any finger. And again make sure your under light and make the shadow of your finger go on top of the proximity sensor. Mine is very sensitive also.
-Monky_1
-Monky_1
My proximity sensor seems pretty touchy, as well.
I initially thought it to be a problem with a particular version of Adrynalyne's kernel, but I'm not so sure anymore. Adrynalyne also said that a kernel shouldn't affect the proximity performance -- that HTC puts these setting or whatever in the framework (what that means exactly, I'm not sure).
Anyway, I haven't done any exhaustive testing or anything, but I did notice one thing that seems to help keep my screen off is to have the thing pointed straight down while on the phone. My natural inclination is to have it along my jaw line, with the end pointed at my mouth. But the proximity sensor is to the left-of-center on the phone. Angling it moves the sensor away from your ear a bit. Assuming you've got it up to your right ear, that is.
I'd still welcome any other points folks might have about this.
calbruc said:
My proximity sensor seems pretty touchy, as well.
I initially thought it to be a problem with a particular version of Adrynalyne's kernel, but I'm not so sure anymore. Adrynalyne also said that a kernel shouldn't affect the proximity performance -- that HTC puts these setting or whatever in the framework (what that means exactly, I'm not sure).
Anyway, I haven't done any exhaustive testing or anything, but I did notice one thing that seems to help keep my screen off is to have the thing pointed straight down while on the phone. My natural inclination is to have it along my jaw line, with the end pointed at my mouth. But the proximity sensor is to the left-of-center on the phone. Angling it moves the sensor away from your ear a bit. Assuming you've got it up to your right ear, that is.
I'd still welcome any other points folks might have about this.
Click to expand...
Click to collapse
This is exactly what's happening. It's nice to see that I'm not the only one having this issue... even tho I'm sure it's annoying for everybody. Hopefully we'll be able to get some relief from this.
http://market.android.com/details?id=i4nc4mp.myLock.phone
This app keeps me from smashing my Droids.
this is not a signature I type it in every time maybe sent from my phone or my computer
rizzomegav said:
http://market.android.com/details?id=i4nc4mp.myLock.phone
This app keeps me from smashing my Droids.
this is not a signature I type it in every time maybe sent from my phone or my computer
Click to expand...
Click to collapse
Would this work even tho the Thunderbolt has no physical Trackball or Camera Button?
Not to discredit this app Kudos to the Dev who wrote it, but it seems like a work around and not an actual Fix.
But I'll try it out and reply back with some feedback
Here's what I do and it works for me most of the time. When making or receiving a call, once the call is 'connected' I quickly hit the 'home' button so I'm no longer on the 'phone screen' & then the power button which darkens & locks the screen. Even if the proximity sensor allows the screen to light up, the lockscreen is still there and prevents me from muting or hanging up on the other person. It's not a perfect solution since my jaw has managed to unlock the screen & randomly open apps occasionally but it beats hanging up on someone every 5 seconds.
Sent from my NookColor using Tapatalk
I'll just throw my hat in that I am experiencing the same issues of muting/hanging up on people. I don't recall having the issue on the stock ROM, but have really noticed it since I've been on BAMF 1.5 with Adrynalyn's 4.4.2 kernal included with BAMF 1.5.
I was running 4.4.2 with the stock ROM before BAMF 1.5 and don't recall having proximity sensor issues. Who knows?
Edit: Anybody think that screen protectors are causing interference in any way? I have an Invisible Shield that I've had since shortly after launch date.
gatorguy said:
I'll just throw my hat in that I am experiencing the same issues of muting/hanging up on people. I don't recall having the issue on the stock ROM, but have really noticed it since I've been on BAMF 1.5 with Adrynalyn's 4.4.2 kernal included with BAMF 1.5.
I was running 4.4.2 with the stock ROM before BAMF 1.5 and don't recall having proximity sensor issues. Who knows?
Edit: Anybody think that screen protectors are causing interference in any way? I have an Invisible Shield that I've had since shortly after launch date.
Click to expand...
Click to collapse
BAMF 1.5 is based on the new leak, which includes a fix for the proximity sensor. If the rom you are running isn't based on the recent leak for our phones, then you don't have the fix, and will most likely have problems with it.
Check this thread out at droid forums! It fixed my "problem" with the proximity sensor. Simply blow out the sensor with air. Apparently dust gets in there and jacks it all up. I can confirm big time results with this method.
http://www.droidforums.net/forum/thunderbolt-tech-support/142050-thunderbolt-proximity-sensor-issue.html
Edit: All those kernel switches and setcpu tweaks over pocket lint!!! Damnitman!
Magicadder said:
Would this work even tho the Thunderbolt has no physical Trackball or Camera Button?
Not to discredit this app Kudos to the Dev who wrote it, but it seems like a work around and not an actual Fix.
But I'll try it out and reply back with some feedback
Click to expand...
Click to collapse
Well the fix is only to hold the phone correctly unfortunately. My gf has no problem using either phone (hers or mine) but if I touch them its muted hang up bam.
One of my coworkers has the same problem as me another dosent. Its absolutely user errorish IMO.
It works with my thunder bolt sort of the home key still works. I don't mind it, moreso than buggered calls.
this is not a signature I type it in every time maybe sent from my phone or my computer
gatorguy said:
I'll just throw my hat in that I am experiencing the same issues of muting/hanging up on people. I don't recall having the issue on the stock ROM, but have really noticed it since I've been on BAMF 1.5 with Adrynalyn's 4.4.2 kernal included with BAMF 1.5.
I was running 4.4.2 with the stock ROM before BAMF 1.5 and don't recall having proximity sensor issues. Who knows?
Edit: Anybody think that screen protectors are causing interference in any way? I have an Invisible Shield that I've had since shortly after launch date.
Click to expand...
Click to collapse
A screen protector was an issues for me. The first one I put on did not fit perfectly, so the top of the protector cut directly threw the center of the sensor and collected dust and gave me some issues. The second one i used was applied from the top down to not obstruct the sensor. Solved my problem.
My phone sensor will black out when I am on a call and the phone is against my face, but when I pull the phone away the screen won't come back up for some reason..
I find that it seems to reflect off the arm of my glasses, which is kinda glossy like. When the IR LED reflects back at it, it seems to assume infinite distance. Same thing happened on my Droid.
There was also a case that lacked the cutout for the proximity sensor on the Droid... screen would never turn off because it reflected the IR.
I'm glad to see I'm not the only one with this problem. It's been happening to me for a few weeks now. I've run the majority of available ROMs and kernels (pre- and post- radio update) in multiple combinations so, I believe its safe to say they are not to blame.
I'm not using a screen protector so, that can't be to blame. And I don't have any scratches on my screen either. I'm curious about this dust theory though. It may be the best one I've heard yet. Has anyone else put the air hose to their Thunderbolt yet? I think I'm gonna give it a go asap. But, in the meantime, I'd love to hear whether anyone else has had positive results. If not, I fear I may have to move on to the glasses theory. I really hope it isn't that one though. I don't want to choose between having my Thunderbolt or my sight!
Mine still does it and I'm using the leak , so I don't think there is a fix in it. If so it doesn't work. Locking the screen seems like a pain but that's the best bet for now.
Sent from my ADR6400L using XDA Premium App
dzigns said:
Here's what I do and it works for me most of the time. When making or receiving a call, once the call is 'connected' I quickly hit the 'home' button so I'm no longer on the 'phone screen' & then the power button which darkens & locks the screen. Even if the proximity sensor allows the screen to light up, the lockscreen is still there and prevents me from muting or hanging up on the other person. It's not a perfect solution since my jaw has managed to unlock the screen & randomly open apps occasionally but it beats hanging up on someone every 5 seconds.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
After trying many ways to work around this problem with the proximity sensor I have found that this is actually works the best .... And I can't thank you enough..... I've grown used to this method and so far its flawless.
Thank you again
Sent from my ADR6400L using XDA App
this has gotten to be a real serious problem for me - hanging up with my face while on a call. i am surprised this isn't talked about more here. any help would be appreciated! is it possible for the dev's to not only remove the end call button but the mute as well?
so far you are the only one that has ever reported anything like that,ya know it could be a hardware defekt
sent via my bamfed out tbolt
Nope I'm in the same boat as im sure are many others. I have only ever had it actually impact me I think twice on phone calls out of almost a hundred or so that I have had since I purchased the phone. All the others times though it was extremely annoying to keep hearing the click sounds of the screen turning on and off on and off on and off etc.
I keep hoping for a software update that addresses the sensitivity of the sensor, but still no
I also wonder how much the battery is affected by the screen turning on and off repeatedly while in a phone conversation...
I get the same. More on my right ear than my left, but it will often take a digit that I just typed for an automated system and try to dial it, resulting in an alarm tone in my ear during the conversation.
sorry but i have 3 different bolts,the 1st one was rooted stock had that problem but it also went into the brick loop so it got replaced,rooted that one but never had the prob again,this one has the bamf 2 prev 3 on it and no probs that is why i suggested harware cause my first one had major hardware issues
sent via my bamfed out tbolt
i get it too. but i dont call so much. so i dont really care lol
I too had this problem, and did some quick searching on Google. Stumbled upon someone who said to spray it with canned air to clean it out. To my surprise, it worked. There is just enough room between the screen and the body of the phone for dust/crap to get in and it hinders both the light and proximity sensors.
You might be holding the phone in a weird position?
THUNDERBOLT
Damn, you lean something new every day, this thing makes phone calls too!
I've had the issue too recently. But it only started when I returned the last phone to stock. Before that, I had a small issue with it, but it didn't happen often.
pnd4pnd said:
this has gotten to be a real serious problem for me - hanging up with my face while on a call. i am surprised this isn't talked about more here. any help would be appreciated! is it possible for the dev's to not only remove the end call button but the mute as well?
Click to expand...
Click to collapse
I have the screen turn on during calls, but I've never had a face hang up. Honestly I think the screen turns on for me, but can't be interacted with.
Scratch that just did a test. I guess I'm lucky. Then again I don't hold the phone flat to my face. So I guess I would never hit it...
i have had hangups, the mute button pressed, and a 3 way call started. i just tried blowing the screen out with some compressed air as someone suggested. it seems better - will give an update after some testing.
No issues with hang ups for me. Had that problem all the time coming from the X.
Sent from B.A.M.F. 1.7 using Tapatalk
I have the same problem and have had it with every Rom I've run and stock. I'm surprised we don't have a way to adjust the proximity sensor yet, that's something I really miss about my Droid X.
After answering a call and putting the tb to my ear, my screen stays on.
Sometimes my ear dials numbers, sometimes the screen stays illuminated but doesn't respond to any touch! I have to toggle the screen on/off with the power button to get the touch response working again.
I have never had an issue. Been on mostly whatever the latest bamf release since rooting.
It happens to me whenever I forget the bluetooth especially after working out or anytime facial area is warmer then normal. I have a screen protector and clean the screen frequently.
I am having the same issue, so I called Verizon yesterday and they are sending me a new phone. I hope it works, because it makes talking on the bolt almost impossible.
Sent from my ADR6400L using XDA App
this is the first I am hearing of this. No problems for me.
Have the same problem...its really annoying man....will not get a refurbished unit until they fix the reboots
Super sensitive touch:
Sometimes car keys work, other times they don't. I have thick gloves- doesn't really work consistently there either. It's weird- I can use the screen a few times with metal devices then they no longer work until I toggle the sensitivity setting.
Speakers:
The on device speakers pop when I change volume (while music is playing). This actually happens on my Windows 3.1 Compaq computer (except it happens there when no music is playing)! Interesting that such an ancient problem has come back to haunt me... It can be hard to hear in certain songs, but in a soft, slow song it is easily heard.
Colors/Rendering:
A couple times now, I noticed that my screen has misrendered colors. Like, I'll be typing something, and the entire screen becomes paler, as if the contrast were turned up high (as in, *actual* contrast, not "high contrast" mode which just changes the colors to black and white). It would change back within seconds. Is this the "daylight" mode or something?
Is something wrong with my device or is this normal...?
Thanks. I only have 13 days to return it for another.
I've experienced the first two problems.
I only experience the second problem with music on my sd card.
As for the third, are you typing with the phone held horizontal, and possibly have your finger over the light sensor at the top near the front camera, this will cause the brightens to go down.
You can change the screen sensitivity. They say when it is on high u can use it with gloves.
jambo89liam said:
I've experienced the first two problems.
I only experience the second problem with music on my sd card.
As for the third, are you typing with the phone held horizontal, and possibly have your finger over the light sensor at the top near the front camera, this will cause the brightens to go down.
Click to expand...
Click to collapse
No, it was in portrait orientation at the time. Hasn't happened since...
Sent from my 820 using Board Express
You always get these kind of quirks with new hardware software, mine has random reboot issues. I'm sure they will be ironed out. You always have your 2 year Nokia Warranty, i'd stick with it its a great device.
jambo89liam said:
You always get these kind of quirks with new hardware software, mine has random reboot issues. I'm sure they will be ironed out. You always have your 2 year Nokia Warranty, i'd stick with it its a great device.
Click to expand...
Click to collapse
It's a question of 'does mine have hardware defects and should I get another' rather than getting a different phone altogether. It would be easier to walk into an AT&T store and walk out with a new phone than to go through a warranty process (you are allowed to do this within 14 days). I think I've determined these are all software bugs though, so that shouldn't be necessary.
Sent from my Windows 8 device using Board Express Pro
There are lots of videos showing this problem: after you have touched the screen sometimes the screen registers finger presses even after you've removed them.
It's very hard to see what is going on if you don't turn on "show touches" in settings, so I suspect many reports about touch screens being unresponsive, or acting strangely is really the same problem.
It occurs both in stock ROMs and aosp, but subjectively more often in stock roms. It's not about moisture remaining, I've wiped the screen completely clean and dry and the phantom touches are there before, during and after cleaning.
Is there a software solution to this or is it hardware? Any thoughts of how this problem could be approached? I'm having trouble even reproducing it reliably.
yet another video of the odd problem: https://www.dropbox.com/s/mglol5qon6vy67g/2013-08-11 20.15.01.mp4
I replaced my Asus TF300 because of a similar issue. Asus fixed it once under warranty (replaced the entire LCD and digitizer, I think) but the issue came right back within a few months after RMA. By then the warranty had expired. In my case, the ghost touches were prevalent in a specific part of the screen; couldn't tell from your video whether the false touches were in the same general area every time or not.
Surprisingly, until the problem became so bad that an entire area was unusable, I could flash a new ROM and get somewhat different behavior. Just to be sure, though, I did flash a stock ROM prior to sending back to Asus and verified the issue existed there, labeled the area with tape so they could not miss it, and described in details the steps to reproduce.
Good luck.
Sent from my GT-N8013 using xda app-developers app
bsaman said:
I
Surprisingly, until the problem became so bad that an entire area was unusable, I could flash a new ROM and get somewhat different behavior.
Sent from my GT-N8013 using xda app-developers app
Click to expand...
Click to collapse
This is my experience also, the aosp revolt rom, seems to suffer much less so than the stock roms.
It does seem to be the same area but it might be just because it's the side that is used most often for scrolling due to me being right handed.
The difference between how the roms behave is what make me suspect it's a software issue.
Just to be clear, you've not noticed this even once with your note? Before I turned on the "show touches" I saw it most clearly when I used chrome or other programs with scrollable elements. The page would sometimes just vibrate a little when left alone.
PremiumMediocre said:
Just to be clear, you've not noticed this even once with your note? Before I turned on the "show touches" I saw it most clearly when I used chrome or other programs with scrollable elements. The page would sometimes just vibrate a little when left alone.
Click to expand...
Click to collapse
No, my note has been rock solid, but I haven't enabled show touches so I can't say for sure.
Sent from my Vivid 4G using xda app-developers app
I'm thinking it might be possible to alter the idc file that specifies the behaviour of the touchscreen (https://source.android.com/devices/tech/input/input-device-configuration-files.html). But it's all a bit over my head.
I'm not alone at least:
http://www.youtube.com/watch?v=ii7m2696T3Y
A simpler cause?
I'm not alone at least:
(YouTube Video URL that I'm not allowed to post, yet)
Click to expand...
Click to collapse
The guy in the video did a great job with research. Did you catch the part where he found nearly imperceptible damage to the screen that was a possible cause? The ghosting always seems to occur in the same places because that's where the screen has been "crushed". Now "crushed" is a bad word because the screen probably hasn't been compressed beyond an acceptable level but there might be some correlation between where the users normally places his/her hand when using the pen and where the phantom touches occur. Maybe when writing, some users are baring-down harder than they realize and prolonged pressure in the same arc-shaped area created by the side of a hand, causes some changes in the capacitive properties in that area which cause a "latch" condition -- where the digitizer gets stuck and won't unstick until power is removed.
I've noticed in the videos that I've seen that the presenter get the problem to appear when using the side of their hand in a rolling fashion -- probably the same motion that they use when they just start to write. I also believe that devices that have this problem "get better" or less sensitive when not used for a while. This would follow the idea that the screen is compressed and given some time, the compression relaxes.
If the problem is limited to a certain area of the screen, I find it hard to believe that the problem could possibly have anything to do with ROM or firmware. The matrix of the digitizer in X-Y coordinates is addressed such that if there were a problem like this, the error would occur and repeat in either a straight vertical or horizontal direction instead of finite points spanning many rows and columns.
I guess one way of ruling this idea out would be to find someone who has never used the pen to write yet still has the problem.
I haven't ruled out that it is hardware related, but I have noted a significant improvement leaving stock ROMs for aosp. Maybe that's just a coincidence, I can't know for sure. I have noted something else that might help diagnose this problem.
If the period of turning on the screen, using the tablet then turning off the screen constitutes one session, there are two types of sessions. Sessions which suffer from this problem, which will be apparent in a relative short period of time. But there are also sessions where everything works as it should, regardless of how long the session is. So you will notice this problem within 10 min or not at all.