Database Develop

Nookie Froyo Users!!! Touch Screen corners.

It seems that corner touch screen sensitivity issues are prevalent among all nook color users. What I'm wondering is, does nookie Froyo have this issue as well?

Yes, or at least for me.

No difference on nookie froyo for me either. I'm pretty sure its a hardware defect and not a software one.

I'm on a rooted stock, but my edge sensitivity issues went away when I loaded one of the overclock kernels. I don't know how the two could be linked, but it is the only explanation I have for the difference. I'm not sure if that's been explored on Nookie, but I thought I would share since that would point to a software issue rather than hardware.

isolated_epidemic said:
I'm pretty sure its a hardware defect and not a software one.
Click to expand...
Click to collapse
That I'm not so sure of. Using "Touch Test" I see all touches, but they seem to get shifted slightly when I press near the edges. Maybe this could get solved in the driver (maybe with some help of calibration tool). I hope to have time to play with this sometime soon.

isolated_epidemic said:
No difference on nookie froyo for me either. I'm pretty sure its a hardware defect and not a software one.
Click to expand...
Click to collapse
How can you be so sure?
If i use google market, sometimes the search button is hard to press,
but using appbrain market it works 100% of the time without problems.

No its not H/W I think, run some tests and corners work fine.
Its certainly something else, I also have better response after loading OC.

I've seen the same thing (I would bet every nook owner has.) The Market Search especially takes *%)(!%&! forever to get to work for me.
I've seen the same behaviour as well, some apps the corners take 18,013,108 tries to get to work, other apps I'm all "Whoa, first try and it worked?!".
I put the 950 OC on my autonoot but then I started playing with Froyo on a C10 SD card (very quick) so I don't know if the OC's actually helped with the corners or not. And of course this is the one day I leave it at home since I got it.

Ultimoose said:
I've seen the same thing (I would bet every nook owner has.) The Market Search especially takes *%)(!%&! forever to get to work for me.
Click to expand...
Click to collapse
Use Menu>Search instead of trying to touch the top magnifying glass.

Happens to me with Froyo. I seriously doubt its hardware related. Seemed to work fine on the stock B&N.

It is common for digitizers to be less accurate along the edges but the Nook Color seems worse than normal. I've noticed the problem regardless of kernel or rom used.

I'm pretty sure it has something to do with the LCD Density. All buttons/elements are a lot easier to press when I switched to 240-250. It does look ugly though, it'd be a lot prettier when we get a custom rom running.

Sigvard is right. Fixed for me by chaging my LCD Density. I set it to 200, which is a little too large for me, so I may lower it. But since doing that I have had no problems at all.
Guide here: http://forum.xda-developers.com/showthread.php?t=889951&highlight=LCD+Density

Ha! I have the exact problem even with stock rom. I though it was the problem of the particular corner of the unit I got! It is much easier to press the button in landscape view.

I dont believe its the screen. Download AppBrain and tap the search button. it works 100% of the time

It is the screen. Use a drawing program and notice how it is easy to draw a straight line in the middle and not as easy on the sides and corners. Note, you need to drag your finger slowly or else you will see more interpolation.
Raising the LCD density just hides the problem by making the hit zone bigger. Fortunately, I can live with the it.

[Q] Touch Screen Responsiveness

Device: Nook Color rooted to 1.1
I had my Nook Color in the car today (40 degrees or so), pulled it out to show her what it looked like rooted. While standing in the driveway showing her different things, I found the touch screen was overly sensitive. As I was scrolling through different things (the app list, twitter, facebook), the slightest touch would select/open an item. It normally doesn't do this. It was incredibly frustrating and almost unusable. I pulled it out later and it seems to be behaving like it normally does.
Does temperature affect the NC screen? Where they any touch screen changes in 1.1? Is there a setting to calibrate the touch screen? I can't seem to find one. Any other suggestions?
I tried doing a search on the forum, but the search crashed.
Thanks.

horsemom said:
Is there a setting to calibrate the touch screen? I can't seem to find one.
Click to expand...
Click to collapse
I was wondering this myself. My input doesn't seem to register as I get towards the edge of the screen.

tactfulcactus said:
I was wondering this myself. My input doesn't seem to register as I get towards the edge of the screen.
Click to expand...
Click to collapse
I don't know if it's placebo or not, but I feel like this app improved my screen response.
http://forum.xda-developers.com/showthread.php?t=934500
As for the other question, I would expect the screen to be less responsive in cold weather, but I don't have anything to base that on.

Guessing what you experienced was due to condensation on the screen. Doesn't take much and can be 'invisible' to you but the screen is sensitive to 'stuff' on the screen and will become overly sensitive if there is anything on it, like moisture, skin oils, etc .. a screen protector may help but unless it continues that is probably the cause.

tactfulcactus said:
I was wondering this myself. My input doesn't seem to register as I get towards the edge of the screen.
Click to expand...
Click to collapse
What you experience is probably temperature related, but another thing to try is to increase the LCD screen density to around 190, 200, or a little more. For me, I get improved sensitivity, especially near the corners.

My daughter accidentally got a little water on the screen and it was a little erratic. I put it in a ziplock with a handful of rice for about 6 hours and it was like new.

I have owned 3 nook colors, the first one I owned freaked out when I used a damp cloth to wipe the screen. It exhibited some strange behavior and emitted some loud static from the speaker. It would not power down or anything... finally it just went back to normal, so I took it back to B&N and then went and bought one at walmart. I took it back because I thought I wanted the Viewsonic G Tablet. But after trying it I finally bought a Nook Color at Best Buy, bought a screen protector too so that I don't have a repeat of my first NC. The screens on these things are, I believe, rather sensitive and the cold or the moisture may have played a part in your unit's behavior.
migrax

tactfulcactus said:
I was wondering this myself. My input doesn't seem to register as I get towards the edge of the screen.
Click to expand...
Click to collapse
Same here. My screen also seems very inaccurate.
Have you found a fix?
Sent from a NookColor using the xda app

I'd be interested in a solution for this as well, since the edges of my NC screen seems to be a lot less sensitive. For instance, when the Market is launched, it takes 4-5 tries to hit the search button at the right top corner (I know that I can hit menu and select search from there, but I am trying to illustrate my point).

tenderidol said:
I'd be interested in a solution for this as well, since the edges of my NC screen seems to be a lot less sensitive. For instance, when the Market is launched, it takes 4-5 tries to hit the search button at the right top corner (I know that I can hit menu and select search from there, but I am trying to illustrate my point).
Click to expand...
Click to collapse
this modified kernel solves that
http://forum.xda-developers.com/showthread.php?t=925451
and you'll also get a speedier nook

It's funny, actually... The cold makes your skin less detectable because of vasoconstriction in your fingers as a physiological response to the cold temperature, but a hint of moisture by means of condensation has the opposite effect.
For me, condensation is rarely a problem, but the decreased capillary blood flow effect is quite noticeable.
Sent from my Nexus S using XDA Premium App

One thing that's been mentioned before (and the B&N salesman told me while buying a screenprotector) is that if the screen has a lot of fingerprints, it'll make the nook act weird.
Try wiping the screen of fingerprints.

don_ernesto said:
this modified kernel solves that
http://forum.xda-developers.com/showthread.php?t=925451
and you'll also get a speedier nook
Click to expand...
Click to collapse
Thanks for the reply. Is it safe to assume that the screen sensitivity would not be an issue in Honeycomb since it is designed for tablets? If so, I may just wait for the final release of HC before fiddling with different kernels,etc. Thanks!

tenderidol said:
Is it safe to assume that the screen sensitivity would not be an issue in Honeycomb since it is designed for tablets? If so, I may just wait for the final release of HC before fiddling with different kernels,etc. Thanks!
Click to expand...
Click to collapse
final realease of HC? no one knows if we will ever have one...... anyhow, it seems to be a fix at kernel level (had to be fixed in eclair, froyo and HC), and it fact, it was discovered by deeper (the guy who ported our HC version)
my suggestion? go for it now. the sensitivity problem is way too bothersome, and it is very easy to apply

don_ernesto said:
final realease of HC? no one knows if we will ever have one...... anyhow, it seems to be a fix at kernel level (had to be fixed in eclair, froyo and HC), and it fact, it was discovered by deeper (the guy who ported our HC version)
my suggestion? go for it now. the sensitivity problem is way too bothersome, and it is very easy to apply
Click to expand...
Click to collapse
Thanks again for the reply.
Yes, I'd love to take care of it ASAP, since I'm sick of trying to hit a small button on the screen and going somewhere else instead.
My NC was rooted with B&N 1.1 + Autonooter 3.0. Will I still be able to "apply" the changes that you mentioned on top of that or do I have to start from scratch?
Thanks!

tenderidol said:
My NC was rooted with B&N 1.1 + Autonooter 3.0. Will I still be able to "apply" the changes that you mentioned on top of that or do I have to start from scratch?
Thanks!
Click to expand...
Click to collapse
go ahead! you won't loose any app or any data (not even your progress in Angry Birds)
Of course, before applying this changes i always make a backup. good to have a way back in case something goes wrong

Good test tool
I ran GoJimi's tool, and since then my screen has been flipping out. Typing anything is a good test...I enter one key like "z", and get 2 - "zm". Utterly maddening.
A good tool to see what's going on is "Mutitouch Test" from JerryW in the market.
When I press with one finger, I see a "phantom" 2nd point jumping around. Very quick way to see 1) how good tracking is and 2) if there's any random inintended multitouch action happening.

Is anyone working on a fix for the appalling 8.9 touchscreen sensitivity?

I know that there is the build prop "fix" which helps slightly (changing one of the values from the default 150 to 300 - can't remember which but you'll find it with a Google around). However, I was wondering if anyone is working on the touchscreen of the 8.9, or has any ideas on improving response sufficiently so that handwriting is feasible.
It seems that there is some kind of filter that disregards small movements - you can demo this but putting your finger down on the desktop and wiggling it from left to right about 2mm or so. I'd expect to see the screen "wiggle" slightly, part scrolling from left to right. Instead after a few seconds it responds as if you have held your finger down motionless. This is the issue that makes handwriting impossible.
On the 10.1 there is the app and discussion thread TouchScreenTune which fixes all of this. I have tried it on my 8.9 but no joy - but I can't imagine there is much in the way of difference between the two devices, and reckon that the 10.1 fixes could easily be applied to the 8.9 if someone with a bit of knowledge applied themselves (that's not me, unfortunately)

Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums and Read THIS
Moving to General

I think we have to contact the dev of touchscreentune and get him on board of this since both devices is kinda similar.

jeremy89632 said:
I think we have to contact the dev of touchscreentune and get him on board of this since both devices is kinda similar.
Click to expand...
Click to collapse
i sent him a mail. here are the responses:
it seems unlikely:
- I don't have the device
- it uses different touch controller than 10.1
- kernel doesn't support configurable parameters for 8.9
Click to expand...
Click to collapse
I'm speaking about driver provided for controller used in 8.9, it has
no possibility to change configuration. And the firmware of the
controller is a binary blob with no documentation.
Click to expand...
Click to collapse
looks like we are unlucky

being very upset with this problem i started poking around the build.prop
it might be placebo but i feel that when this is added:
Code:
windowsmgr.max_events_per_sec=300
it gets a little more responsive. still not what i want it to be but better than before.

Try Touchscreen booster
It seems to have helped mine.

thanks. seems a little more responsive.
here is the apk if anybody else was wondering:
http://forum.xda-developers.com/showthread.php?t=1261237

My 8.9 LTE is super sensative, probbly the most I have seen on any android tab.
I can just barely graze my screen with rhe back of my fingernail and it even picks that up.
Compared to my roomates ASUS Transformer Prime, wo cant even use his fingernail unless he really jams it down.

iinteresting but im on the tegra version which aparently has completely different hardware

hi everybody
I'd like to try to find some answer to the annoying problem of the touch filtering.
I've been searching around the internet for days, I've also asked the author of TST but with no luck till now.
Is there anybody that knows or can address me to how this problem can be solved? I don't think it's just a hardware problem, but a software one.
I'm also willingly to write to Samsung directly, so wish me good luck.
If I'm not gonna find a way to do this in a couple of weeks, I'm quite sure I'm gonna sell this beautiful black useless brick to an iPad.

MatteAce said:
hi everybody
I'd like to try to find some answer to the annoying problem of the touch filtering.
I've been searching around the internet for days, I've also asked the author of TST but with no luck till now.
Is there anybody that knows or can address me to how this problem can be solved? I don't think it's just a hardware problem, but a software one.
I'm also willingly to write to Samsung directly, so wish me good luck.
If I'm not gonna find a way to do this in a couple of weeks, I'm quite sure I'm gonna sell this beautiful black useless brick to an iPad.
Click to expand...
Click to collapse
Try TouchScreen Booster?

the_hatrix said:
Try TouchScreen Booster?
Click to expand...
Click to collapse
that's been the first thing I did, but the improvements it brings are very light.

Does the tablet really have different hardware between the wifi and the LTE version? (at least regarding the screen digitizer)

Loccy said:
I know that there is the build prop "fix" which helps slightly (changing one of the values from the default 150 to 300 - can't remember which but you'll find it with a Google around). However, I was wondering if anyone is working on the touchscreen of the 8.9, or has any ideas on improving response sufficiently so that handwriting is feasible.
It seems that there is some kind of filter that disregards small movements - you can demo this but putting your finger down on the desktop and wiggling it from left to right about 2mm or so. I'd expect to see the screen "wiggle" slightly, part scrolling from left to right. Instead after a few seconds it responds as if you have held your finger down motionless. This is the issue that makes handwriting impossible.
On the 10.1 there is the app and discussion thread TouchScreenTune which fixes all of this. I have tried it on my 8.9 but no joy - but I can't imagine there is much in the way of difference between the two devices, and reckon that the 10.1 fixes could easily be applied to the 8.9 if someone with a bit of knowledge applied themselves (that's not me, unfortunately)
Click to expand...
Click to collapse
Hmm, is it really a sensitivity issue? If I swipe first then wiggle like you mention, the screen will wiggle slightly. It sounds like there is a threshold to switch from holding the finger down motionless, to scrolling from left to right.
Perhaps a threshold setting (if available) is sufficient to overcome this?

I'm noticing the samething. When I first saw this thread I thought everyone was crazy but after trying to type large amounts of text I've found it incredibly unresponsive in landscape mode (though portrait feels perfect!). I'm eagerly waiting for the official ICS update as in hoping it'll fix some of these issues.
It would be nice if they at least updated us to 3.2.

Kasracer said:
I'm noticing the samething. When I first saw this thread I thought everyone was crazy but after trying to type large amounts of text I've found it incredibly unresponsive in landscape mode (though portrait feels perfect!). I'm eagerly waiting for the official ICS update as in hoping it'll fix some of these issues.
It would be nice if they at least updated us to 3.2.
Click to expand...
Click to collapse
I have Samsung 3.2 OTA update and it really changes nothing.
Btw no answer yet from Samsung, and yes, the problem is just about some sort of accidental touch filter

[Q] Is it possible to fix this dual-touch bug? (video)

Hi,
There's this thing about the dual-touch module that really bothers me a lot lately. Since it is difficult to put the issue into words, I've uploaded a video for you people to see what the thing is.
See how the touch is recognized in the middle? It happens quite often since I write text messages very fast. Is this possible to fix? Or do the hardware limitations force me to live with it?
Sorry about the quality - the video was recorded using another Xperia device
Relevant info:
Digitizer: Cypress
ROM: FroyoPro v2.5
Kernel: Stock

Have you seen this video? It is too smooth for syncaprtics. It is definitely cypress.

feherneoh said:
Yes, by replacing your Synaptics (I'm almost sure it's Synaptics) tuochpanel by a Cypress one.
Click to expand...
Click to collapse
Sorry I haven't mentioned this before. The touchpanel is definitely a Cypress one. I will add this information to the first post.
Also to note: ROM is FroyoPro v2.5, kernel is stock (bootloader cannot be unlocked).
Is this even normal behavior for the Cypress digitizer? It almost seems as if you suggest it isn't. This bug/problem is one of the things that actually made me want to root the original device. But even though the phone is 2x better than it was before, this problem still persists, and can be annoying at times.
The solution would be most welcome.

This is quite annoying when I'm typing on the keyboard... when I type quickly it thinks very often that I pressed a button halfway between my 2 fingers...
edit: I have tested it with 3 multitouch tester apps and I can't reproduce the problem. Something else causes the keyboard to operate wrongly (happens with all keyboard applications).

Lajbymester said:
This is quite annoying when I'm typing on the keyboard... when I type quickly it thinks very often that I pressed a button halfway between my 2 fingers...
edit: I have tested it with 3 multitouch tester apps and I can't reproduce the problem. Something else causes the keyboard to operate wrongly (happens with all keyboard applications).
Click to expand...
Click to collapse
Same thing happened on stock ROM (I applied the dual touch module before switching to FroyoPro), so I don't think the ROM is responsible. All the keyboards suffer the same issue, except 2.3 Gingerbread Keyboard which performs passable. I really wonder if this case is specific to my phone or do other people have the same issue. Because, if they do, I might as well drop this and blame it on the phone

feherneoh said:
On Synaptics fake dt it seems to be normal. On Cypress... You should try to slow down
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
But I like doing everything fast

Here's just an update on the issue.
Recently I had a chance to try another Xperia X8 with a Synaptics digitizer, and luckily the owner had a Gingerbread ROM installed on it. I can say with certainty that dual touch had indeed performed better in typing than on my unit, albeit the Multitouch Visualizer gave some really strange results when both fingers were on the screen. The owner also said that other effects like pinch-to-zoom and performance in games seem to work a lot better on Cypress.
I did some homework regarding the dual touch module made for Cypress devices. Among other things, the developer wrote about this issue which caught my eye:
"- on FroyoBread sliding position of touch from first finger to second if you release first and quicly press second finger in another position - could you check both v003 versions guys ?"
FroyoPro actually is a continuation of FroyoBread, and this sounds very much like the issue I'm having right now.
Can Cypress users (especially if you're also FroyoBread users) please confirm if this problem is common to all of us, so perhaps flashing another ROM, like Gingerbread, could actually solve it?

xWhiskey said:
Here's just an update on the issue.
Recently I had a chance to try another Xperia X8 with a Synaptics digitizer, and luckily the owner had a Gingerbread ROM installed on it. I can say with certainty that dual touch had indeed performed better in typing than on my unit, albeit the Multitouch Visualizer gave some really strange results when both fingers were on the screen. The owner also said that other effects like pinch-to-zoom and performance in games seem to work a lot better on Cypress.
I did some homework regarding the dual touch module made for Cypress devices. Among other things, the developer wrote about this issue which caught my eye:
"- on FroyoBread sliding position of touch from first finger to second if you release first and quicly press second finger in another position - could you check both v003 versions guys ?"
FroyoPro actually is a continuation of FroyoBread, and this sounds very much like the issue I'm having right now.
Can Cypress users (especially if you're also FroyoBread users) please confirm if this problem is common to all of us, so perhaps flashing another ROM, like Gingerbread, could actually solve it?
Click to expand...
Click to collapse
did i understood your statement right?.. that if you press a finger at one position and then press at another postition and quickly remove the first finger it acts like a sliding gesture...if so then yes it does... it does the same on all the roms i have tried yet...

CnC-ROCK said:
did i understood your statement right?.. that if you press a finger at one position and then press at another postition and quickly remove the first finger it acts like a sliding gesture...if so then yes it does... it does the same on all the roms i have tried yet...
Click to expand...
Click to collapse
Aye. But that was the statement of the module creator, AnDyX, not mine Just tried it on the launcher screen. It was funny that it actually forced me to the next screen without doing the slide gesture. This confirms the issue. The module perceives it as a single touch that slided from the first to the second finger. Not as two touches altogether. Typing with it is really a nuisance.

xWhiskey said:
Aye. But that was the statement of the module creator, AnDyX, not mine Just tried it on the launcher screen. It was funny that it actually forced me to the next screen without doing the slide gesture. This confirms the issue. The module perceives it as a single touch that slided from the first to the second finger. Not as two touches altogether. Typing with it is really a nuisance.
Click to expand...
Click to collapse
that action is so fast that it interprets it as a continuous slide....we cant do anything in that.. but it should not give problems in typing... just try to estimate the minimum gap that is required for proper typing so that you can type at the max possible speed.....

CnC-ROCK said:
that action is so fast that it interprets it as a continuous slide....we cant do anything in that.. but it should not give problems in typing... just try to estimate the minimum gap that is required for proper typing so that you can type at the max possible speed.....
Click to expand...
Click to collapse
Yes, I do it with relative success. But then again, I'd rather go without it
Thanks for replying. The issue, it seems, cannot be fixed.

Multitouch with +5 fingers

****UPDATE: *****
This is what happens https://imgflip.com/gif/1xvxm0
What can be the cause of this? Does this happen to any of you as well? Should i open the casing and see if there is anything touching the metal casing that should not ?
****EO UPDATE ****
I have been testing with both
Settings -> Developer Options - > Show Pointers (and looking at the top left that says x/x points)
or
Using a multitouch test app like so https://play.google.com/store/apps/details?id=com.the511plus.MultiTouchTester
The latter is nice because it has big handlers and you can clearly see the point/touch flickering like loosing and creating point (hence creating a new point ID)
From what i can say in Marshmallow it worked way better, on the last 2 Nougat updates i saw that at the 7th point it started to do the flickering and with this one it starts at the 5th point.
With 3 fingers screenshot disabled (and all the gestures for that matter) as i know it would create a conflict.
Just tested in a Motorola with Marshmallow and it created the 10 points flawlessly.
I wonder if any of you noticed the same or is something off with my touchscreen?
Might it be a Nougat thing ?
Any known solutions?
I searched around and nothing Nougat related seem to pop up
Just tested with both OP2 and a Moto G5 and they both work great, actually it even worked great on my Samsung Galaxy i9000
I have noticed that for the last 2 updates or so multitouch capability has been decreasing.

When are you ever going to use ten fingers to multitask? If it wasn't for the screenshot gesture, we wouldn't even be using three.

JarJarWinks said:
When are you ever going to use ten fingers to multitask? If it wasn't for the screenshot gesture, we wouldn't even be using three.
Click to expand...
Click to collapse
That is irrelevant for what i am trying to figure out, what i want to know is if it is a HW problem by default or just my HW is faulty or even if it is a Nougat problem.
It works flawlessly on other less capable phones

Either software or hardware fault I would say. I just tried it out without any flickering with 10 fingers on my 3t running latest unofficial LineageOS 15/Oreo ROM.

pitrus- said:
Either software or hardware fault I would say. I just tried it out without any flickering with 10 fingers on my 3t running latest unofficial LineageOS 15/Oreo ROM.
Click to expand...
Click to collapse
Thank you, from what i get so far is a Nougat thing, all the users that have Oreo seems to work fine

Conductive electricity ?
Ok some pretty strange updates...
I accidentally tested it on a metal table and it worked perfectly, which lead me to think that it might be due to conductive energy or something.
So i tried the test on a wooden table and it does flicker and loose touches, so i pressed with a finger on a metal part of the OP3T casing and the points are registered properly.
I had made a video so people don't think i am crazy here is the result https://imgflip.com/gif/1xvxm0 at this point i can say that is directly related.
What can be the cause of this? Does this happen to any of you as well? Should i open the casing and see if there is anything touching the metal casing that should not ?

anyone ?

This is a non issue honestly. If it doesn't change how your phone functions in day to day practical use, you probably shouldn't bother with something like that. The touch display functionally is fantastic especially the screen colors and with the recently fixed touch latency it does happen to be one of the best screens on the market despite its lower resolution. Factually you won't use more than a three touch input so. IMHO

nagi_007pk said:
This is a non issue honestly. If it doesn't change how your phone functions in day to day practical use, you probably shouldn't bother with something like that. The touch display functionally is fantastic especially the screen colors and with the recently fixed touch latency it does happen to be one of the best screens on the market despite its lower resolution. Factually you won't use more than a three touch input so. IMHO
Click to expand...
Click to collapse
It is definitely a problem did you watched the video ? because it seems like a real hard problem to me, use cases for you might be different from others. My old samsung galaxy i9000 as well as my OP2 did not had that problem

It may be a problem for one and may not be a problem in another's eyes.
To address your issue, have you tried switching ROM's? I don't think it could be a Nougat problem, but you might as well try Oreo or even MM.
This may sound funny, but have you tried with another person's fingers?

thes3usa said:
It may be a problem for one and may not be a problem in another's eyes.
To address your issue, have you tried switching ROM's? I don't think it could be a Nougat problem, but you might as well try Oreo or even MM.
This may sound funny, but have you tried with another person's fingers?
Click to expand...
Click to collapse
I had the feeling that it might be from the updates (still using official OP updates) but right now i think it might be hardware. Yes i tried with other fingers, thinking about opening the phone to see if there is something touching the metal case inside.