I have a completely stock Nexus S. Whenever I answer or place a phone call the screen goes black and never comes back on. I have to remove the battery and reboot the phone. Anyone have any ideas as to the cause of this?
I think it may have something to do with the proximity sensor not being sensitive enough.
Thanks
Sorry for the thread necromancy but it's either that or creating another redundant thread for the same issue. I'm suffering from the same problem as the op (nonrooted Nexus S everything stock) and so are the people who have responded to the informal bug report in the Google mobile help forums you'll get as the first hit if you google "Nexus S back screen after call" (sorry, first post so no links).
I've been unable to remedy it despite quite a bit of research and it's getting quite frustrating, especially since the problem is still present after the update to ICS.
I've gathered this has been an issue with a multitude of handsets and that the problem is on the kernel level and seems to be the result of the proximity sensor being miscalibrated.
Now I don't know how the calibration data is handled on the Nexus S so if anyone is sitting on info related to this I'd love to hear it. Also if there is any way to recalibrate the proximity sensor via ADB or some MMI code that would be great.
Otherwise, has anyone suffered from this problem and managed to solve it by changing kernels? If so which kernel did you use?
Cheers.
Just noticed it wasn't working. I've flashed back to rooted stock and tried several apps with nothing working. I can't say if it ever worked as I never use it. Has anyone tested this to see what could be the issue? Does it work on a clean phone, unrooted stock original? Are we somehow messing the magnetometer up with flashing?
Bump. Anyone tried their compass even?
Wouldnt rely on it. Ive had the phone sitting on a table with the compass pointing North, closed the app and reopened and it was way off. Closed and opened again and it was pointing a different direction.
So your compass is broke as well. There are phones where this works. It's nice for apps like google skymaps. Question is does it come broke or does rooting/unlocking/flashing somehow mess it up.
I have yet to see a phone where the compass works consistently. Due to the fact that some countries restrict the use of very sensitive magnetometers I doubt we will ever have very reliable ones in cell phones.
Perhaps but this is an advertised feature of a US based phone. We have every right to expect it to function. The question is does it function at all even on new in bow devices. Some youtube videos show it working bit it's not clear if those are i9300s or i535s. It could also just be an unreliable device hitting on some and being broke on others.
So using the sensor test (*#0*#) I was able to see my y axis sensor is very low. It goes above the threshold when the top of the phone is oriented north. The device must be calibrated to start and periodically. It also loses direction if turned up as you would for google skymaps. This makes the app useless. Other devices do not have this problem. I believe I have a defective sensor but also that samsung drivers are shotty. Can anyone else look at their readings and report?
This is probably related to the crap GPS as well. I believe the issue can be fixed in the kernel too bad we don't have many devs that work on the kernels.
Where in the hell is the compass?
Android 4 Life
The compass is a built in piece of hardware that you need an app to see. Search for compass in the play store. Any one should work.
On a sidenote, a Samsung rep checked two of their devices and found it working. One was a vzw on 4.04 and the other was on 4.1. I tried to get him to send me the 4.1 rom to test on but he couldn't.
This may be a sporadic problem inherent in only some devices.
Had vzw ship me a new one but before I returned the old one I flashed it back via odin and low and behold, the compass came back. Even on a stock rom that was slightly modified it wasn't happening. After odin, I was able to root, unlock and flash cwm and keep it running. Once I flashed any rom, the compass was dead but I could flash back to a backup of the stock unmodified rom and it worked. So it's a software issue and I'm going to return the warranty replacement.
Hi Everyone,
I bought an S3 at the end of May, rooted and flashed cm 10.1 about a week later (and flashed firmware required to get the camera working a few days after that).
Earlier this week, the display suddenly shifted green and started to die - no amount of resetting, wiping, or unrooting and flashing stock would fix it (the screen ultimately came back on, but with a permanent blue-green tint and low resolution). Although I've basically chalked it up to a hardware failure (maybe gpu?), I got a replacement and am a little hesitant to flash CM again for fear that this might be a common issue.
Has anyone here experienced something similar? Is there any way that flashing and running a custom rom for a month could put undue stress on the motherboard, gpu, or other hardware? Would a custom kernel address the issue?
Just basically looking for thoughts from people who are way more experienced with this stuff than I am. Sorry if this has been posted before; I browsed the forums briefly and the display issues I saw didn't quite seem to match what I experienced.
purudaya said:
Hi Everyone,
I bought an S3 at the end of May, rooted and flashed cm 10.1 about a week later (and flashed firmware required to get the camera working a few days after that).
Earlier this week, the display suddenly shifted green and started to die - no amount of resetting, wiping, or unrooting and flashing stock would fix it (the screen ultimately came back on, but with a permanent blue-green tint and low resolution). Although I've basically chalked it up to a hardware failure (maybe gpu?), I got a replacement and am a little hesitant to flash CM again for fear that this might be a common issue.
Has anyone here experienced something similar? Is there any way that flashing and running a custom rom for a month could put undue stress on the motherboard, gpu, or other hardware? Would a custom kernel address the issue?
Just basically looking for thoughts from people who are way more experienced with this stuff than I am. Sorry if this has been posted before; I browsed the forums briefly and the display issues I saw didn't quite seem to match what I experienced.
Click to expand...
Click to collapse
A co-worker of mine had an S3 T999 on tmobile that did this same exact thing on the stock unrooted rom. I'd say its unrelated to CM, and glad you got a replacement. It should not do it again, so CM is safe to run on it.
Not a Rom issue. Sounds like just bad luck of the draw. I am on my 3rd or 4th s3 and i haven't had a Rom kill my phone yet.
Sent from my GT-P5113 using xda premium
Hey!
The Issue: During a phone call the screen turns dark and will not reactivate...it will pop back up after the call disconnects. Hitting any of the site buttons does nothing.
I have tried flashing with the newest firmware (http://blog.geekbuying.com/index.ph...-firmware-released-0502-version/#.UtMOWM93vVI), and although it says this issue has been resolved, it does not fix the problem for me.
I heard that custom ROM fix the solution? (Saw it on this http://forum.xda-developers.com/showthread.php?t=1518663).
But last time I tried one of those, the phone bricked and it took me a while to get it back working (finding stock followed by lost IMEI).
Anyone know a solution? Or possibly a good solid custom ROM that will work? I would really appreciate your help!
I am also having this same issue but with my Cubot X6. However mine just doesn't work in the dark. During daylight it responds as it should.
After a lot of googling it seems to be a problem with jellybean as it occurs on a lot of other phones. A way of solving this would be to disable the proximity sensor but I can't find any settings to do so.
Need help
alrightiwill said:
I am also having this same issue but with my Cubot X6. However mine just doesn't work in the dark. During daylight it responds as it should.
After a lot of googling it seems to be a problem with jellybean as it occurs on a lot of other phones. A way of solving this would be to disable the proximity sensor but I can't find any settings to do so.
Need help
Click to expand...
Click to collapse
Hey! Not sure if this be of any help, but for me removing the screen (plastic) cover fixed the issue. I assume the screen cover was blocking a sensor thus resulting in my issues.
Just thought I let you know what worked for me...although I doubt your issue can be solved like this.
BTW, I suggest you start a new post, as this one is old and I doubt anyone will read it! also, check out geekbuying.com blog in regards to your phone. They might have more info.
A few people here and there have been starting to have this problem pop up- including me.
My phone was perfectly fine with absolutely no problems with the touch screen but about three days ago, my phone started acting weird.
At that time, I was running CM 5.1 nightly and then dirty flashed over to the latest. I thought that this was the problem and so I did a clean flash but still the problem was there.
Went back to the original CM nightly that I was previously on and problem is still there.
Tried many different ROMs but the problem is still there..
I can't type out a sentence without my phone failing to register a touch and sometimes registering rapid touches as one - the same problems before Synaptic released a 'fix' for this issue.
At this point, I don't really know what to do but it's aggravating that a phone can't do it's basic tasks such as type.
The phone seems really sluggish when I type - which I haven't encountered before this which slightly leads me to believe that input lag is the crux of the problem however, I can't say for certain.
Can anyone with more expertise help me with this?
Same issue
You_got_owned123 said:
A few people here and there have been starting to have this problem pop up- including me.
My phone was perfectly fine with absolutely no problems with the touch screen but about three days ago, my phone started acting weird.
At that time, I was running CM 5.1 nightly and then dirty flashed over to the latest. I thought that this was the problem and so I did a clean flash but still the problem was there.
Went back to the original CM nightly that I was previously on and problem is still there.
Tried many different ROMs but the problem is still there..
I can't type out a sentence without my phone failing to register a touch and sometimes registering rapid touches as one - the same problems before Synaptic released a 'fix' for this issue.
At this point, I don't really know what to do but it's aggravating that a phone can't do it's basic tasks such as type.
The phone seems really sluggish when I type - which I haven't encountered before this which slightly leads me to believe that input lag is the crux of the problem however, I can't say for certain.
Can anyone with more expertise help me with this?
Click to expand...
Click to collapse
Im having a similar problem. I cant type a single sentence without errors. It doesnt register the touch as well few times. Using a device is so sluggish.. hate it. Tried many roms with clean wipe but without any success. Would be nice if anyone could help with the above issues.
I have similar issues and I don't think it's a software issue - I have never flashed a ROM. I think it's hardware problem, probable the earthing suggested in this post:
http://forum.xda-developers.com/oneplus-one/general/fixing-ghost-touch-grounding-issue-hint-t2951000
There is an app that re-calibrates the touchscreen every time you turn it on, but it doesn't completely solve the problem for me and also prevents unlocking until it has completed, which is annoying. The fact that a re-calibration is needed to even achieve a little stability is consistent with an earthing problem.
If mine gets any worse, and I think it will, I'm going to investigate a warranty claim, but that sounds like a few weeks with no phone, which I can't tolerate.
hi, i'm experiencing the same problems. you can test this when registering 2 touches on the same Y axis (try with anyone of touch test apps).
I think that this is popping out to a lot of people in this moment because of the hot days kicking in. in fact, if your phone is cold (try to put in a fridge for 5 minutes) it will work perfectly, but when it will become hot again in your hands the touch will start to freak out again
What sucks is my phone was perfectly fine a few days ago and we've only had an increase of about 5 deg F over the week.
Occasionally the capacitive buttons don't register either.
Same thing here. Perfectly working screen, flashed 5.1 unofficial some weeks ago and no matter wich versión of cm or what kernel, randomly ghost touches happens.
Now with official 5.1 and ak 200 works better, but it's still there. There must be some kind of firmware/software problem, It's too curious that this issue begin to happend to many people at the same time.
My bro has the same problem, some days after flasing CM12S the screen doesn't feel as responsive anymore.
The screen isn't able to handle multiple touches anymore what makes typing really annoying, scrolling through settings also goes really slow.
Tried flashing latest 12.1 nightly but I don't think any ROM will be able to fix it.
No idea what caused it and if there is a way to fix it.
ZuLa said:
Same thing here. Perfectly working screen, flashed 5.1 unofficial some weeks ago and no matter wich versión of cm or what kernel, randomly ghost touches happens.
Now with official 5.1 and ak 200 works better, but it's still there. There must be some kind of firmware/software problem, It's too curious that this issue begin to happend to many people at the same time.
Click to expand...
Click to collapse
This is exactly what happened to me and it seems like it happened to a good number of people around the same time. Either 1)It's a huge coincidence 2)OnePlus rigged our phones to go haywire around this time or 3)Something in one of the nightlys got messed up for a few people however like you said, flashing new roms for kernels doesn't help anymore which makes me want to do a complete wipe - Internal data included.
Same issue
I was sure it's the heat some time back but then this touchscreen fixer app in the Themes and Apps section is actually helping. That makes me wonder if its the firmware, coz the problem only kicked off after the CM12.1 update. A few of my classmates purchased the OPO at the same time as I did and they dont have this issue (they didnt go to CM12.1).
Any tips on what firmware/ROM to revert to?
Edit: I also flashed the Oxygen OS firmware.
It's not a change in the firmware, mine did it spontaneously. It's hardware. OnePlus will do everything they can to spin a software story and indeed it will often be possible to partially mitigate in software, but ultimately everyone with this problem should be getting a replacement. That could be a lot of people.
patp said:
It's not a change in the firmware, mine did it spontaneously. It's hardware. OnePlus will do everything they can to spin a software story and indeed it will often be possible to partially mitigate in software, but ultimately everyone with this problem should be getting a replacement. That could be a lot of people.
Click to expand...
Click to collapse
I'd love to see how you jumped to such a definite conclusion. I live in a warm climate to begin with, temperatures are actually lower now than they were a month and a half ago, and the CPU of my OPO has definitely risen above the 41-45 Celcius range that people seem to quote for this current wave of issues (and I have corroborated with my own testing). However, if I go to the recovery, the touchscreen seems to have normal responsiveness, regardless of the CPU temperature. Unless it was a built in hardware malfunction set for a specific moment, the probability of a sample, even of this size, where a series of individuals can all see the exact same lineup of hardware-based issues occurring at the same time, is too ugly for me to try and imagine calculating. But I would fare to bet it isn't high.
However, if a set of users are all changing their software as new versions and builds come out, just as the release occurs... At least then you have a series of events occurring all at the same time. Not causation, but at least there's a stronger correlation than "it's warming up so now we see the hardware defects".
The temperature range this "defect" is being attributed to can be reached quite easily in normal use in temperate areas, but even in colder climates, it should be simple to reach such temperatures if the phone isn't underclocked, as the phone is set to charge, or even if the phone is running a software update of some kind, and countless other things.
TL;DR - Don't jump to conclusions that fast, weather changes aren't a strong correlation.
hyshion said:
I'd love to see how you jumped to such a definite conclusion. I live in a warm climate to begin with, temperatures are actually lower now than they were a month and a half ago, and the CPU of my OPO has definitely risen above the 41-45 Celcius range that people seem to quote for this current wave of issues (and I have corroborated with my own testing). However, if I go to the recovery, the touchscreen seems to have normal responsiveness, regardless of the CPU temperature. Unless it was a built in hardware malfunction set for a specific moment, the probability of a sample, even of this size, where a series of individuals can all see the exact same lineup of hardware-based issues occurring at the same time, is too ugly for me to try and imagine calculating. But I would fare to bet it isn't high.
However, if a set of users are all changing their software as new versions and builds come out, just as the release occurs... At least then you have a series of events occurring all at the same time. Not causation, but at least there's a stronger correlation than "it's warming up so now we see the hardware defects".
The temperature range this "defect" is being attributed to can be reached quite easily in normal use in temperate areas, but even in colder climates, it should be simple to reach such temperatures if the phone isn't underclocked, as the phone is set to charge, or even if the phone is running a software update of some kind, and countless other things.
Click to expand...
Click to collapse
The outside temperature being warm would keep the screen hot for a prolonged period of time as compared to the phone heating while charging or intense usage. However, your recovery argument is spot on! The touch works flawlessly in recovery!
goldengargoyle said:
The outside temperature being warm would keep the screen hot for a prolonged period of time as compared to the phone heating while charging or intense usage. However, your recovery argument is spot on! The touch works flawlessly in recovery!
Click to expand...
Click to collapse
Well I guess it's good that it's not hardware damage.
Has anyone tried going back to android 4.x to see if it helps- if it really is software?
Surprised there hasn't been more people experiencing this issue given the number of people going to android 5.x
I have the same frustrating issue
Same here, works fine in recovery. Also had this issue arise after the first bout of touch issues: https://www.youtube.com/watch?v=yoFYcFawTI4&feature=youtu.be
(clearing cache seems to alleviate that particular problem)
I think it's a software issue. I mean possibly there is hardware problems too but mine started appearing only after I installed the 5.1 update... also some things for me feel like a software issue for example when scrolling instagram back up to the top. as soon as it gets to the top it bounces back down again.. seems like software problem to me.
This is definitely a hardware issue. My phone was working perfectly. Until I went on a 5 days trip and used it for navigation, and went very hot. Up until then I was on the same CM12 rom for weeks without a problem. Since then, I've flashed many roms and the problem persists. It's definitely a hardware problem. For me it occurs whenever the phone runs a little bit hot. Practically all the time when I'm on 3G. When the phone has been in my pocket with 3G on, it's almost impossible to unlock it when I try to use it.
I contacted Oneplus a week ago and I still try to get them to RMA the phone. They've sent me all sorts of crap emails, I wiped the phone and now they ask me to shoot a video to showcase the problem. This company has the worst customer service you can find. As much as I like the pricing, I won't be bothered again with their devices. I only hope they'll RMA it otherwise I'll open it myself and try to fix the grounding issue. There is a detailed how to which also explains what's the problem.
I always had it but it was so minim that maybe couple of times a day weren't that big problem!
Just yesterday and today the issue is now intolerable! I removed the screen protector and used the stock lollipop keyboard (bcz swiftkey is kinda slower the issue was there more).
It's still very annoying and I can't type easily! I had to remove flow/swype feature to minimize it further!
Seriously considering buying another phone although I wanted to keep it for a year at least! But the hate is growing on me...
HAha exact same problem here happening since 3days.
I was on Euphoria 29/3 build. I flashed ak kernel, after reboot i couldn't type properly anymore. I was like damn, maybe its bad kernel setting or so. Didn't help.
Cleanflashed 3 roms since then, didn't solve anything. All tho touch works fine in twrp for me. So im really clueless. Swiping does seem to work better for some unknown reason to me!
The ghost swipes while typing is driving me crazy. Thinking of going back to 5.0.2 to see if that helps. Do I need to flash an old firmware to go back to a previous Android version