Database Users

Slider unlock sometimes doesn't work with incoming call

Once in a while when trying to answer an incoming call the unlock slider won't respond. I will slide my thumb to unlock and ...nothing. When this happens the call will just go to voicemail . The workaround is to touch the power button to turn off screen , then touch it again to wake it up ,then the slider will work and I can answer the call. Sometimes this takes too long and I miss the call.
This is not a deal-breaker as it only happens 5% of the time , still it is annoying. I have tried different roms with no real difference. Anybody else have this problem? Any advice other than get a new phone under warranty?

Ditto. And I always act as you did to work around the issue, only difference is, I haven't missed a call due to this.
In any case, based on experience, the chance of this happening could be minimized (if not eliminated) by always locking the phone from the "desktop" (e.g. do not lock the phone when an app is running).
BACK STORY:
I remember this happening (more than once) when someone called me up after a train ride. And the last thing I could recall is that I have locked the phone while playing Angry Birds / Fruit Ninja / Zenonia 2, etc.
But it still sucks that it happens.

I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?

question... are the phones plugged in to a wall charger when this happens?

Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).

DKYang said:
Nope. Only happened to me when I under clocked the CPU with Setcpu using the powersave profile (I was just testing things out).
Click to expand...
Click to collapse
can happen any time any place

ransome7 said:
I guess my real question is , are all Nexus s doing this sporadically , even rarely , or is my phone defective?
Click to expand...
Click to collapse
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).

cygnum said:
I'm not sure if everyone's having this, but I'm with you on this. I'm on stock but rooted 2.3.3. Experienced this since 2.3.1.
EDIT: My wife has this problem too, since 2.3.1 until 2.3.3 (not rooted).
Click to expand...
Click to collapse
Mine did it stock , I rooted and loaded roms to see if that would fix the problem , lessened but still there

My nexus s (i9020T) has exactly the same problem. I've also tried to flash different ROMs, including CM-7rc2 and stock 2.3.3, and the problem remains.
I tried to bind Multi-touch Visualizer 2 to long pressing home button, and found the when screen is unresponsive, it can still detect press near edges very well, but not the center. While I press at the edge and drap across the center, it keeps tracking my finger correctly. In addition, Locking and unlocking the screen can solve the problem temporally. I connect my phone with adb, and tried to "cat /dev/input/event0" The behavior confirms what I see in Multitouch Visualizor 2: the when the center of screen is unresponsive, nothing can be read from the device node.
I read the mxt224 touch screen controller doc, and it seems the chip features self-calibration, and thus I believe the "lock & unlock" will trigger the chip to tune it self in some way. I've also read the driver code of nexus s, htc incredible and moto droid x, all using the same controlling chip. Both HTC and moto would send calibrate command to the chip during resume, but sumsang does not. I guess this might be the reason, but I'm not skilled enough to port the drivers

I experienced it twice so far i think, but only have the device for a little more than 2 weeks.
I am on stock 2.3.1 currently.

Beside the lock&unlock method, I discovered a new way of getting screen back to work: rub your hands a couple of times and touch again... Anyway it seem the screen is not well calibrated.

problem seems fixed with my customized kernel
Last night, I modified the touchscreen driver and mach settings a bit on the source of netarchy's nice kernel, and compiled a kernel of my own. The screen now seems working well with my new kernel

Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App

swa2k4 said:
Never have experienced this on the nscollab rom which is cm7 and kernel together stable. I suggest give it a shot
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
May I know how to perform the suggested steps, i have been experience twice since i bought it on 2 weeks ago

I would like to bring this issue up again (after so long) as I am still randomly experiencing this exact issue even with Ice Cream Sandwich 4.0.3 (Stock & Custom ROMs). Any fix yet?

[Q] Miui degrading over time?

I have Miui installed in my HD2, currently running from SD. Since the beggining i noticed that sometimes the rom freezes when doing stuff. (I´ve seen the chinese guy and the turtle a lot) but nothing really bad.
Since a few weeks, the telephone freezes sometimes when receiving a call and i cannot answer. i have to lose the call, wait a few minutes and then be able to see who called. When bad comes to worse, it keeps ringing and vibrating and i have to remove the battery. It is not my wokr phone so i could live with it.
The last 2 days, it started doing the same, but with the screen black. I was able to pick up the call with the button, and terminate the call, but after that the screen remained dead. Buttons light up if touched, but screen no. Again, only fix was to remove the battery.
I went back to the 2.2 rom w/sense that i have in magldr.
Questions are:
Can this be because i was running from SD? I assumed that because running from SD might be slower.
It is possible for a Rom to degrade and start presenting errors like that? in the 2.2 rom i have none of this problems, do i do not think its hardware related.
Probably will use this chance to try another ROM.
Interested in a Cyanogen port of trying ICS if there is something stable yet.
What are my options for stable roms?
Im no dev, no cook, only an average user...

[Q] Screen Shift ICS 4.0.4-Sense 3.5-Cm Scream Rom-Miui Rom Help Me

hi my phone is just working 7.2 CM nand rom. ICS 4.0.4 - Htc Sense 3.5 - Cm scream rom - Miui Rom shift of the screen is in them. Usually red, vivid color screen is moving.Screen shift off color doesn't cause. Please help me.
Sorry for my english google translate

please help?

you should return to windows mobile first...

looks like a screen replacement that is not supported by our kernels

schlund said:
looks like a screen replacement that is not supported by our kernels
Click to expand...
Click to collapse
I had broken my screen repair.But it works cm7.2. ICS-HTC Sense-CM scream doesn't work. Why? What should I do?

please help me

what about old ROMs
mustafa3m said:
please help me
Click to expand...
Click to collapse
did try to switch back to SD card version of android or WM6.5??

do you have this problem yet?

tm.bax said:
do you have this problem yet?
Click to expand...
Click to collapse
yes, the problem continues

Hello there,
I recently changed from Schlund's Photonic SD Boot to CM 7.2 NAND Version, where I started having this strange issue. SD Boot worked just fine once I managed to get over the critical first 10 minutes after booting without freezing. Now the screen shifts occasionally, especially when I'm opening white windows or menus like the shutdown menu or the one where you enter a wlan security key. It stops in every position, just like mustafas picture shows. If I turn it around, the line dividing the screen just stays where it is, both frames will turn. I tried changing every single option related to the screen, flashing different versions, without gapps, without update, even [ROM] Phonerty MIUI v4 (ICS). The bug is a bit slower in this one, but still there. In all cases everything is the way it ought to be after tapping the standy button and waking it up again. But in most cases it will wont stay that way. I can't even flash it back to WM (and I don't really want to since I know how useful this little thing can be with Android on it), every RUU i tried to use told me I was using the wrong one. Any ideas? Anything new about this one?

[Q] Phone is frozen after a call

So I switched to GB from WM65 and found it's pretty slow but usable. I don't have time to switch back to WM65 so I'll stick with GB.
Now, one big issue I have is the phone app (not wifi app, just plain phone). When I dial a number, the screen goes black to prevent pressing the wrong button with your ear etc. Problem is, I can't get back to the screen, meaning I don't have access to the dialpad. Annoying when you're on queue and you need to press a key to get to a menu... like repeat a message on your messagebank for instance.
Second issue, is after the call, the phone is frozen for about a minute or two. Nothing responds. Then it comes back alive.
I haven't found any threads on this, though users seem to complain about wifi calling, which is not my case.
Anyone has seen this ?
Txs.

Can you please tell us which ROM that is?
I know that this issue was fixed, but maybe your ROM is just too old. Or maybe the developer didn't include the fix.

I had this problem with almost every gingerbread build on my HD2.
Im not sure what's causing it, but i fixed this issue by installing screebl lite from play store. While this app enabled, phone would wake up normally after a call in 99.9% of the cases. You should try the same.
Strangely, i don't have any issues on ICS or JB roms.

Marvlesz said:
Can you please tell us which ROM that is?
I know that this issue was fixed, but maybe your ROM is just too old. Or maybe the developer didn't include the fix.
Click to expand...
Click to collapse
Android Version 2.3.7
Baseband Version 15.42.50.11U_2.15.50.14
Kernel Version 2.6.32.15_tytung_gb_r16 [email protected] #292
Build nr GWK74 (nexusHD-Gingerbread V3.3a) DataOnEXT
Got it from this dude http://forum.xda-developers.com/showthread.php?t=905060
So there is a patch ?

Boags said:
Android Version 2.3.7
Baseband Version 15.42.50.11U_2.15.50.14
Kernel Version 2.6.32.15_tytung_gb_r16 [email protected] #292
Build nr GWK74 (nexusHD-Gingerbread V3.3a) DataOnEXT
Got it from this dude http://forum.xda-developers.com/showthread.php?t=905060
So there is a patch ?
Click to expand...
Click to collapse
Okay, I have looked throughout that thread's pages, and it seems that you're not the only one with that problem. So apparently the ROM doesn't have the fix (which is weird, because tytung almost always fixes everything in a rom before moving onto another one).
You're better off changing the ROM, or maybe trying to figure out what is wrong with your device and those who're facing the same issue.

Marvlesz said:
Okay, I have looked throughout that thread's pages, and it seems that you're not the only one with that problem. So apparently the ROM doesn't have the fix (which is weird, because tytung almost always fixes everything in a rom before moving onto another one).
You're better off changing the ROM, or maybe trying to figure out what is wrong with your device and those who're facing the same issue.
Click to expand...
Click to collapse
Thanks Marv, so...no hotfix ? no patch ? just change ROM ? this is silly :|

Boags said:
Thanks Marv, so...no hotfix ? no patch ? just change ROM ? this is silly :|
Click to expand...
Click to collapse
Well, the fix wasn't a flashable zip, it was implemented. It was a problem with the proximity sensor if I recall correctly. And since I don't use this ROM, I can't really help you much.
I tried googling the problem (it's fun, you should try it) and this came up : http://forum.xda-developers.com/showthread.php?t=1376251
Your sensor/screen could be dirty making it hard for the proximity to detect. You can try another non-GB ROM and see if the problem is still present.
I am sorry I can't help.

Marvlesz said:
Well, the fix wasn't a flashable zip, it was implemented. It was a problem with the proximity sensor if I recall correctly. And since I don't use this ROM, I can't really help you much.
I tried googling the problem (it's fun, you should try it) and this came up : http://forum.xda-developers.com/showthread.php?t=1376251
Your sensor/screen could be dirty making it hard for the proximity to detect. You can try another non-GB ROM and see if the problem is still present.
I am sorry I can't help.
Click to expand...
Click to collapse
Right, I'll go with the hypothesis that a dirty screen hinders proximity sensors. That should affect a black screen DURING a call (issue I'm also facing) but that should not affect the phone once the call is terminated, should it ? What I mean is, in my case, when I hang up a call, I can't use my phone for a couple of minutes, until it comes back to life. I will get a new "screen protector" and see what happens in the meantime though.
As for a hotfix, seems odd there is none out there. Thanks for trying.

Incoming call ISSUE.

Hello guys. I have proble with my p7000 and incoming calls. Sometimes the incoming call just bug whole phone. I can't recieve the call and I have to put out the battery. It's really annoying. And also, I don't see who called me in call history. I've made factory reset, but it didn't help. Also I updated my firmware to the version 20150807 but this bug is still here.
Absolutely same problem has man on this video. /watch?v=c588Clm67ME
Please help me.
/Sorry for bad English/

I had the same issue, try the November update from Stock or the Miui rom (the new one, not the one created the day the phone was out), I didn't had the glitch with those 2. I'm trying to know from what that problem come from but I'm far from being an expert sadly. That problem is on all the stock roms except the first and the one from November. All the roms based on stock got that issue (even those based with the November update strangely !?) so I guess it's something related to the voltage or something...

leomon32 said:
I had the same issue, try the November update from Stock or the Miui rom (the new one, not the one created the day the phone was out), I didn't had the glitch with those 2. I'm trying to know from what that problem come from but I'm far from being an expert sadly. That problem is on all the stock roms except the first and the one from November. All the roms based on stock got that issue (even those based with the November update strangely !?) so I guess it's something related to the voltage or something...
Click to expand...
Click to collapse
Thank you. So do you think, that ROMs like cyanogenmod doesn't have this issue? I almost can't use my phone... Today it happened to me again, but not on incoming call, but on alarm clock. So it has to be something with sound/soundcar/voltage of reproductors or something like that.. I am not expert so I am not sure.

filipusfikus said:
Thank you. So do you think, that ROMs like cyanogenmod doesn't have this issue? I almost can't use my phone... Today it happened to me again, but not on incoming call, but on alarm clock. So it has to be something with sound/soundcar/voltage of reproductors or something like that.. I am not expert so I am not sure.
Click to expand...
Click to collapse
The best is to test it. First install TWRP then make a backup of your current rom then install that rom : http://bbs.elephone.hk/thread-8425-1-1.html#.VlyDufkvdhF and see if that problem occur again. Personally I had no issue with the November rom for the P7000 so I'm staying on that one for now, even the root doesn't mess up anything... If that occur with alarm that might be a problem with the sound board/card then I had the same issue, when I get a call, the sound was looping, screen staying black, had to or remove the battery or long long press on the power button.
Hope that will help you !
PS : The november rom is here : http://bbs.elephone.hk/thread-9111-1-1.html#.VlyFPPkvdhE but you need a working flashtool for that one (you need flashtool for a custom recovery too anyway).

solved - cant receive incoming calls 4g'
I know this is an old thread but I have just had this exact same problem and after WEEKS of googling and determination I have found the fix to this problem..
I'm posting it because as I was googling I found that there are still hundreds of people experiencing this today.
HERE IS THE SOLUTION!
Dial *#*#4636#*#* on your phone..
Then scroll down and you will see a small down arrow next to "Set proffered network type"
Choose LTE/GSM/CDMA Auto (prl)
Also, you might need to check one other thing.. On the same screen go to top right ":" drop down nav menu settings shortcut and "Select Radio band" - do this if the 1st change hasn't fixed your incoming calls problem.. You can experiment with AUS, AUS2 or Automatic etc and try again.
I was about to throw this new Elephone S3 back to China but it's all great now
Hope this helps someone
Shakir