Screen turns off when placing phone to ear as expected however does not come back on when pulled away. Only after the 2nd party disconnects will the screen come back on after pressing power button and the only to the lock screen. This is a new issue. Anyone else having this problem or know of a solution?
Sent from my SCH-I605 using xda premium
Maybe faulty proximity sensor. I had that issue in my galaxy nexus. Ended up getting a new one
Sent from my SCH-I605 using xda app-developers app
I'll inquire with Verizon about that.
Sent from my SCH-I605 using xda premium
Call insurance. Get a new one or refurb for that matter.
Sent from my SCH-I605 using xda app-developers app
Are you stock? Rooted? I ran into this issue a few times with persus kernel.
I'm having the same issue. Anyone find a fix for this?
Just got off the phone with Verizon. They're sending a replacement. Something wrong with proximity sensor. Actually appears to be a speck behind glass over sensor.
Sent from my SCH-I605 using xda premium
I have also been having a bit of trouble with the same thing. On top of the screen not always coming on when I move the phone away from my ear during a phone call, sometimes when I pull up the keypad while on the phone and attempt to press a key, the screen will turn off. I think it's because the shadow of my hand makes it think it's back up to my ear. I see two little sensors next to the camera; one of them appears to have a little speck or dot on it. Maybe a piece of dirt in it? Can somebody who doesn't have this problem check and see if they see a very very tiny dot on the sensor closest to the in call speaker?
I've been having the same issue with my Note 2, I was wondering if this could be a software issue since I have messed with a few roms but decided to go back to stock. I've been looking everywhere for a solution, even went as far trying to find replacement files to see if that would fix it, but to no avail. I guess I'll have to replace the device.
tbns said:
Can somebody who doesn't have this problem check and see if they see a very very tiny dot on the sensor closest to the in call speaker?
Click to expand...
Click to collapse
I am not having issues, and do not see a dot on the sensor.
Sent from my SCH-I605 using xda premium
scurley1898 said:
Just got off the phone with Verizon. They're sending a replacement. Something wrong with proximity sensor. Actually appears to be a speck behind glass over sensor.
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
Have you received your replacement?
If you have, did they send you a certified like-new or a brand new replacement?
Thank you
SilentO said:
Have you received your replacement?
If you have, did they send you a certified like-new or a brand new replacement?
Thank you
Click to expand...
Click to collapse
I received a certified like new and it's in perfect condition.
Sent from my SCH-I605 using xda premium
I have found a fix for this, at least for me, as I mentioned in an earlier post I had flashed a few ROMs, decided to search the other carriers galaxy note 2 forums and found this:
http://forum.xda-developers.com/showthread.php?t=2070360&highlight=proximity+sensor
Luckily there is a Perseus kernel for verizon too here: http://forum.xda-developers.com/showthread.php?t=2048013
Will do this later and report.
Edit: the perseus kernel by itself didn't do the trick but beanstown's stock root/deodex and jelly 'beans' roms did! I now have everything working like new with cleanrom installed
scurley1898 said:
I received a certified like new and it's in perfect condition.
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
You probably got one that was repaired in China. Hate getting phones from the Chinese, cheap but poor quality. Thanks
Sent from my SCH-I605 using xda app-developers app
Related
My dad cracked the screen on his Galaxy Note so I bought a replacement and replaced it. But when I turn the phone on the Samsung Galaxy Note logo turns from white to purple and everything after bootup has a purple tint to it. The weird thing is, if I boot up the phone with the old screen attached then replace the old one with the new one, while the phone is still on, the new one doesn't have purple tint to it. But if I reboot the phone with the new screen it turns purple again. I am not sure what to do. How can I fix this?
Get another replacement, there may be ways to fix it but you might as well just get new one because there could be more problems down the road
Sent from my SAMSUNG-SGH-I717 using xda premium
Display Drivers
android4545 said:
Get another replacement, there may be ways to fix it but you might as well just get new one because there could be more problems down the road
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
I can't really afford to pay another $250 for another replacement. Why does it work if I bootup with old screen then replace with new one while the phone is on? The phone must be detecting the new screen as something else and using the wrong display drivers or something. Can't I force it to use the right drivers?
Is it the right part from Samsung or is it a non OEM replacement?
And why did you steal my avatar!?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
keller.jeff said:
Is it the right part from Samsung or is it a non OEM replacement?
And why did you steal my avatar!?
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
The LCD part # is AMS529HA01 which is the same part # as the original. It also has Samsung branding on the front as well as the ribbon cable. So it appears to be a OEM part. I did not get it from Samsung, I got it from smartphonebay.net, which says it is 100% OEM.
emerysteele said:
I can't really afford to pay another $250 for another replacement. Why does it work if I bootup with old screen then replace with new one while the phone is on? The phone must be detecting the new screen as something else and using the wrong display drivers or something. Can't I force it to use the right drivers?
Click to expand...
Click to collapse
Sorry thought it was a free replacement, are you running ics or gb?
Sent from my SAMSUNG-SGH-I717 using xda premium
android4545 said:
Sorry thought it was a free replacement, are you running ics or gb?
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
I upgraded it to ICS a few weeks ago.
i had a problem like that on an old phone it turned out to be the ribbon cable wasn't fully connected. i ended up putting a tiny piece of foam on the connector to hold it down real good once the phone was put back together.
I agree. It sounds like bad ribbon connection to some signal needed for boot detection.
I almost bought a $250 replacement when I cracked my glass. AT&T was no help. Samsung offered to fix it cheaper. $197.01 including parts, labor and shipping to and from Plano, TX.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
emerysteele said:
I upgraded it to ICS a few weeks ago.
Click to expand...
Click to collapse
If it's still happening I'd say it's a hardware problem because new software should fix any bugs
Sent from my SAMSUNG-SGH-I717 using xda premium
emerysteele said:
I can't really afford to pay another $250 for another replacement. Why does it work if I bootup with old screen then replace with new one while the phone is on? The phone must be detecting the new screen as something else and using the wrong display drivers or something. Can't I force it to use the right drivers?
Click to expand...
Click to collapse
A mate of mine is having the exact same issue as you. He brought his replacement screen off Ebay which was "claiming" 100% OEM. On boot the Samsung Galaxy Note logo stays white for a couple of seconds then turns a shade of purple. We did discover that if you install a GB rom the issue is resolved. In particular if a GB kernel is installed the issue goes away. Did you find a fix to your problem?
d1wepn said:
A mate of mine is having the exact same issue as you. He brought his replacement screen off Ebay which was "claiming" 100% OEM. On boot the Samsung Galaxy Note logo stays white for a couple of seconds then turns a shade of purple. We did discover that if you install a GB rom the issue is resolved. In particular if a GB kernel is installed the issue goes away. Did you find a fix to your problem?
Click to expand...
Click to collapse
I've got the exact same problem. I replaced the display on my N7000 and a few seconds after showing the logo it goes purple and stays that way. I installed a GB ROM and voila! No more purple. But I want to run a Jelly Bean ROM! This is driving me nuts!
Anyone found another solution yet?
So just got my phone back from Samsung after they replaced the screen. The menu button is very dim and the search button is dim compared to the middle two buttons. I was going to call Samsung but wondered if it may be an easy fix that I could do on my own instead of waiting another week to get it fixed. Any guidance would be appreciated.
Sent from my SGH-I777 using xda app-developers app
Are you running a custom rom?
jthatch12 said:
Are you running a custom rom?
Click to expand...
Click to collapse
I was but went back to stock with same issue
Just called Samsung and they want me to send it back for repair. I don't know if its worth it, will b third time sending it to them...why can't they fix it right the firs time?!
Sent from my SGH-I777 using xda app-developers app
Anyone have any ideas
Sent from my SGH-I777 using xda app-developers app
Sorry. It looks like sending it back to them will be the only way to fix it that doesn't take cash out of your pocket. As for why they can't get it right? Most likely because it is a low paid repair tech just following a shop manual.
Sent from my SGH-I777 using xda premium
Yeah, I ended up sending it to them today. I got next day air shipping and the guy expedited the process for me for the hasal for no charge at all since its their fault. Hopefully, I get it back with no problems.
Hey guys, so I picked up a galaxy note 2 the other day and it's been great but after a few days I noticed the the vibrate had gotten louder and different sounding and I figured out that it is caused by the s-pen rattling when the phone vibrates because it feels slightly loose in the slot because i can kind of move it back and forth when it is in there and I was wondering if anyone else was having the same problem? or if not I might go swap devices at the store if I'm the only one with the issue. Thanks
Mine is pretty tight, take it back and get another one.
Sent from my SCH-I605 using Tapatalk 2
thats what she said.
Yeah mine is nice and snug in there. I'd have them swap it out for another phone.
Sent from my SCH-I605 using xda premium
I mean it doesnt like jiggle around if I shake the phone, I can just slightly move the end when its inserted in the slot. But I guess it is loose enough in there or something so that I can hear it when the phone vibrates, I think I'll head to the verizon store today then
Sent from my SCH-I605 using xda app-developers app
Shamestick said:
Hey guys, so I picked up a galaxy note 2 the other day and it's been great but after a few days I noticed the the vibrate had gotten louder and different sounding and I figured out that it is caused by the s-pen rattling when the phone vibrates because it feels slightly loose in the slot because i can kind of move it back and forth when it is in there and I was wondering if anyone else was having the same problem? or if not I might go swap devices at the store if I'm the only one with the issue. Thanks
Click to expand...
Click to collapse
I had this same issue on my other phone. I swapped it out due to speaker issues, and my second phone doesn't have the same issue. On my previous phone, my friend tried to jam the S-Pen back in the slot without putting it in the proper direction. Anyways, I used the S-Pen a lot initially and now barely use it. I'm wondering if those who say they have a snug s-pen fit, utilize the s-pen a lot?
Anyways, i'd take it back if you can. If it was with assurion/replacement, i'd just say deal with it because most likely it'll happen again if you use the s-pen a lot.
Im still within the first 14 days of having it so I believe I can exchange it for a new one
Sent from my SCH-I605 using xda app-developers app
Shamestick said:
Im still within the first 14 days of having it so I believe I can exchange it for a new one
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
I'd do it then.
Usually I never buy with insurance, but with all the issues that the Note2 has I bought it this go around.
But I still think this issue will pop up again with constant S-Pen use.
Thats what I was thinking.. because it didn't start happening until after a few days of having it, in which I played around with the s pen a good amount.. but if other people dont have the issue I would rather not have it either because I text a lot and when it rattles on 60% of them it gets a bit annoying
Sent from my SCH-I605 using xda app-developers app
Shamestick said:
Thats what I was thinking.. because it didn't start happening until after a few days of having it, in which I played around with the s pen a good amount.. but if other people dont have the issue I would rather not have it either because I text a lot and when it rattles on 60% of them it gets a bit annoying
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Like I said, the people above didn't comment on their usage though of the S-pen... I barely use it now, and it is in there pretty snug. When I first got the phone before the swap, I used the pen for everything.
So I have had the issue, but on the new phone not yet. May as well do the exchange... though if you can.
Im not even sure anymore.. I used a buddies phone today and sent myself 10 texts and it didnt do it on any of them but then I had anothee friend send me 10 and it did it on 5/10 of them
Sent from my SCH-I605 using xda app-developers app
Picked my One up today to replace my freshly broken Nexus 4. So far so good, but this home "button" registers about one out of five presses. Anyone else seeing this behavior? The back button works fine every time.
Sent from my HTC One using xda app-developers app
Got a screen protector on it?
The sensitivity is a bit low for it to register perfectly. Happens on mine.
Sent from my HTC One using xda premium
I sure do! I guess I will try peeling it back and see if it helps.
Sent from my HTC One using xda app-developers app
I have no screen protector and my home button doesn't register often either. Also when trying to touch places in the standard browser it doesn't register immediately. Starting to think there's a defect in screen or software.
Sent from my HTC One using Tapatalk 2
I'm having the sane issues it does it with the back button as well. Did it before I put the screen protector on it. It doesn't help that they sit so close to the screen. When I start tapping frantically trying to make it work I end up pressing whatever is right above it on the screen. Thinking about returning it to try another but if it's a common problem I don't want to waste my time. It's not too bad usually at least one of the two buttons will register if the other one won't
Sent from my HTC One using xda premium
Diesel321 said:
I'm having the sane issues it does it with the back button as well. Did it before I put the screen protector on it. It doesn't help that they sit so close to the screen. When I start tapping frantically trying to make it work I end up pressing whatever is right above it on the screen. Thinking about returning it to try another but if it's a common problem I don't want to waste my time. It's not too bad usually at least one of the two buttons will register if the other one won't
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Yeah it's my back button as well, I thought about replacing. It seems that quite a few people are having the issue. I don't know should I try and replace or if it's a software issue.
Sent from my HTC One using Tapatalk 2
I know I just put the screen protector on along with a carbon fiber skin. The idea of having to go and deal with the people at AT&T alone makes me want to just deal with it. Also afraid I'll just get another one
Sent from my HTC One using xda premium
Diesel321 said:
I know I just put the screen protector on along with a carbon fiber skin. The idea of having to go and deal with the people at AT&T alone makes me want to just deal with it. Also afraid I'll just get another one
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
I agree, if the issue is only on our variant then it could be software or hardware. I have no idea what to do.
Sent from my HTC One using Tapatalk 2
godfirst said:
I agree, if the issue is only on our variant then it could be software or hardware. I have no idea what to do.
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Me neither. I suppose deal with it and wait to see how common it is and if any dev can fix it. I'm waiting to unlock and root anyway
Sent from my HTC One using xda premium
I had the same issue on my device. It took three swaps to figure out it wasn't the phone but, the Zagg HD screen protector I had on it. Once I took it off, everything started behaving as intended,
I noticed last night that my Zagg screen protector still had some water bubbles (very tiny ones) near the home button. So today after another night the bubbles are gone and the home button works well enough I can assign a double tap short cut.
Never had any issues with the back button, just for reference.
Sent from my HTC One using xda app-developers app
Noticed the issue as well. Saw it mentioned in a recent review of the phone. You have to be really precise because the buttons are so small.
Sent from my HTC One using xda premium
dxwilliams40 said:
Noticed the issue as well. Saw it mentioned in a recent review of the phone. You have to be really precise because the buttons are so small.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Precise isn't the word lol. I hope a software update will fix it completely
Sent from my HTC One using Tapatalk 2
abisai said:
I had the same issue on my device. It took three swaps to figure out it wasn't the phone but, the Zagg HD screen protector I had on it. Once I took it off, everything started behaving as intended,
Click to expand...
Click to collapse
I'm almost 100% sure it has to do with the screen protector.
I was using an Otterbox Defender case which has the screen protector with the soft keys uncovered. I was using the phone without a hitch. But this morning I decided to use a different screen protector other than the one provided by Otterbox and that screen protector covers the soft keys.
Now I'm having issues with the sensitivity of the soft keys.
Somehow covering the soft keys with the screen protector affects the sensitivity level of the soft keys. I'm thinking of uncovering the soft keys just to finally confirmed that, that is the problem.
Sent from my HTC One using xda app-developers app
Same problem on Sprint variant. I went to the store and the display model also had same problem. Neither had a screen protector.
This is either a widespread hardware defect or a widespread software problem.
Some have said the latest update to the Taiwan variant fixed it.
RE: http://forum.xda-developers.com/showthread.php?t=2245637
I have had the issue as well and I believe it's software, rather than hardware. If my back button freezes and I turn the screen off and then back on, it works fine. It only seems to do it when I "overload" the back button in an app that needs it a lot, like this one.
Sent from my HTC One using Tapatalk 2
Has anyone else been experiencing weak or unresponsive home and back keys. My home key does not always work. Just trying to see if mine is faulty or others experience this issue.
Sent from my HTC One using xda app-developers app
I have the same issue and it has been pissing me off. I have read the OTA has fixed this issue for some. I am still waiting for my OTA to come through.
Screen off/screen on seems to kick it back into gear most of the time for me.
I had the same problem. Unlocked bootloader and put TrickDroid on, and this problem is gone. Not that it should be the solution, but it seems the move to the international update fixed that problem.
I also had the problem on stock AT&T ROM. Flashed ARHD and the problem is gone
Sent from my HTC One
I had the problem after i installed a screen protector. I cut around the buttons and now the problem it's gone.
Sent from my HTC One using xda premium
airicd22 said:
I had the problem after i installed a screen protector. I cut around the buttons and now the problem it's gone.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
I just installed a screen protector and noticed the buttons are a little finicky. Just dealing with it for now.
mrjasenr said:
I just installed a screen protector and noticed the buttons are a little finicky. Just dealing with it for now.
Click to expand...
Click to collapse
I wonder if a software update will fix it.
Sent from my HTC One using xda app-developers app
Mrkrackie said:
I wonder if a software update will fix it.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Doubt it. Sounds completely independent of software.
Sent from my HTC One
I flashed international Rom and it's alot better I have two ones that I use and there's s big difference between stock att and international imo
Sent from my HTC One using xda premium
Stock ATT rom here and there are times I have to hit the home button a few times. Gonna unlock bootloader tonight and see about installing a rom.
Mine definitely require very accurate taps. I am getting used to it, but I am hoping a software update will improve the responsiveness.
Sent from my HTC One using Tapatalk 2
Seems to be the case more with our (ATT) software. Flashing the international or one of the international ROMs seems to make it much more responsive. Hopefully our phones will get the update soon!
I loaded an international Rom and I still occasionally get buttons that don't work and I have to lock and unlock the screen.
Sent from my HTC One using xda app-developers app
Some say it's the screen protectors some say it's not. I did notice before I out one on it wasn't so bad. But once I out it in was constantly smashing the buttons and where the are so flipping close to the screen I would open unwanted apps. Anyway I too a straight edge and an exacto knife and cut the protector off right where the screen ends and the black capacitive area begins. Did it last night and haven't had to press anything more than once. Just a thought from a guy
Sent from my HTC One using xda premium
Compared to my One X, neither of the buttons are precise at all, even without a screen protector on the AT&T Rom.
Sent from my HTC One using xda premium
mjwitt2 said:
Compared to my One X, neither of the buttons are precise at all, even without a screen protector on the AT&T Rom.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
I agree. A screen protector shouldn't make a difference. Never did with ny One X either.
Sent from my HTC One using xda app-developers app
mjwitt2 said:
Compared to my One X, neither of the buttons are precise at all, even without a screen protector on the AT&T Rom.
Click to expand...
Click to collapse
Even when I didn't have the screen protector installed it was also very finicky. It seems like you have to press down exactly on the buttons for them to register the action. Even then, one of the buttons will sometimes wig out on me while the other one will continue working. It seems like the problem resolves itself within fifteen seconds most of the time, but its annoying nonetheless.
What's funny is that I thought it was a software problem at first, but even after switching over to the newest CM nightlies it still happens every now and then.
Yea but basing that in cm10 is irrelevant
Because so much is patched and ported but agreed this thing sucks sometimes
Sent from my HTC One using xda premium