Hi everyone!
I have a situation here. I have this old A106, i am using as a secondary phone. Upgraded it to lollipop 15-20 days back and since then something or the other is happening with the phone.
First was the proximity sensor, the screen would shut off right after i dial a number and wont come up unless i press the power button. The proximity sensor is not functioning at all i guess.
Secondly, since this morning, I am unable to receive any calls on my phone. The phone rings, I swipe it to the right but nothing happens and the icon comes back to the middle, and within a few seconds the call gets disconnected.
Tried factory reset/data wipe from recovery but it didnt fix the issue. Any help would be highly appreciated.
Thanks, Have a good day!
Related
Hi guys!
I use the XDA II myself but gave an XDA I as a gift to a friend.
However, while he has it in his pocket it seems to turn itself off completely, as in not remaining on standby for calls and sms.
He turns off the screen using the usual button, puts it in his pocket and an hour or so later, wonders why he hasn't had calls or messages. He touches the button again and gets the blue o2 screen and logo just as in a soft reset, as the device turns itself on and receives messages and missed calls notifications.
It doesn't happen all the time but once or twice a day. Obviously the device is useless if he cannot rely on it to be on standby for calls, and if he has to keep rechecking it to see if it's live.
It happens even when battery is fully charged so it's not a powersaving cutoff.
Here's the details
XDA I
ROM 317.03ENG
Romdate 05/15/03
Radio Version 4.21.00
Protocol Version 32S54
I'd be grateful for help if anyone knows what's wrong and how to solve it.
Best regards to all
Conor
Does this happen even when the xda is clean with nothing installed? It may be an idea to do a hard reset and use it for a while to see if it happens without any software installed.
Conor said:
He turns off the screen using the usual button, puts it in his pocket and an hour or so later, wonders why he hasn't had calls or messages. He touches the button again and gets the blue o2 screen and logo just as in a soft reset, as the device turns itself on and receives messages and missed calls notifications.
Conor
Click to expand...
Click to collapse
I do have this problem too. I think WM2003 is not really fully suitable for XDA1.
Beside this, I also encounter problems like the phone will gard reset itself if you enter the phone BAND selection page. Also, the phone will turn on by itself which it didnt when I was still with the PPC2002.
Have to bear with it as I CANNOT flash the rom anymore as the WM2003 refused to let me do it.
Bye.
Raymond
Yes - a hard reset didn't help things...
Yes - a hard reset didn't help things...
Any other ideas out there?
Thanks
The SIM rubber cover is reseting the device.
To test it, turn the device on and lightly press on the rubber cover to see if the device resets or turns off.
It is a known problem! Try to open the rubber cover on top of the SIM card and close it again.
If that does not help do a search for a fix...
Just got it. Looks great and all functions seem to work except if left for a bit, the device seems to freeze with a blank screen, but the green network signal LED still flashes every few seconds as normal.
The display is off, and all buttons don't work when it's like this and a battery out job is needed to reboot and get it back to working.
Everything will be fine until it times out or whatever and goes into this hibernation/semi dead mode.
This seems odd as I thought most phones these days allowed emergency calls in most standby modes. No keys work so no 999's for me when this is being like this.
Have I missed something obvious or is it a proper fault?
Please help as I need to send it back asap if it's a faulty phone.
Thanks,
Joe
Just to add, it has just frozen again but this time on the today screen. No keys active, and when I call the phone number it rings on the phone I call from, but nothing happens on the v1240.
Update: I also bought another as a gift, it doesn't do this and the faulty phone has been returned as I am away from the UK with work for some time soon.
Topic can be closed now - it's a hardware fault.
Does anyone know if there is an issue with the proximity and light sensors in the Samsung Focus v1.3? Neither of them work on mine.
When I go into Diagnosis, the Proximity Sensor test shows XXX where the detection value would be, and the light sensor says "Val: 0000" in red where the ambient light value would be.
This means whenever I make a call, I have to hit the sleep button on the phone to turn the screen off, lest I accidentally press buttons on it with my ear while I'm talking.
All other features and functions of the phone work just fine. I've dropped it once, but the Prox/Light sensor issues started occurring before that.
Any assistance would be appreciated.
Might be a hardware issue i have the same problem, i tried to fix it by installing the factory ROM. No luck. I'm gonna bring it back to rogers to see if i can get it fixed :\
Similar problem
My phone will go to blank screen as soon as I hit "Answer" or for outgoing whet I tap "Call" so I can't put on the speakerphone or hangup. All butons and functions are disabled. I have to remove the battery to reset the phone or wait for the caller to hang up. On calling "VoiceMail" it just goes on and on before hanging up so removing the battery works faster and restarting the computer.
I have tried to adjust the proximity indicator as I read on another forum but it doesn't seem to make any difference. I have to add that this seems intermittent and sometimes it works normal and sometimes not.
Maybe "dropping it" has something to do with it. One forum said customer service wanted him to do a hard reset which I assume is the only way to get rid of the Mango update or any apps installed that may be a contributing factor. If anyone has any ideas let us know.
not if I'm in the right place to post this but,,,,,, what happens is that my nexus 5 ceases to vibrate completely for a few hours, whether or not activated the vibration, I have it set to always vibrate, calls, messages, etc.
but like I said only stops vibrating as in a few hours back the vibration, I've made a reset to factory, turn off and turn on the phone, but that does not help and does not happen every day but sometimes from week to also Signed in safe mode to verify that an application is not what is causing this but nothing I can not change because the lost with the guarantee that the holes for the increased volume ,,, any idea why this happens and any solution, thanks
You could return to stock, flash the factory image, and hope it solves the problem. But I'm guessing not and it's a hardware issue
When I make or receive a phone call on my new Nexus the screen blacks out. I understand that it should black out when the phone is brought up to my ear, but it blacks out even though the phone is eighteen inches away from me. There is nothing on top of the proximity sensor and it is clean. The phone is not in a case. The sleep timer in set to two minutes. The cache partition has been cleared.
I think this happened after upgrading from Android 5 to 5.1, but I cannot be certain.
The AndroSensor app always reports that the proximity sensor detects something at 0.0 inches (with 12.7 mA), even though the sensor is uncovered.
I have seen several threads in various forums on this issue with the Nexus 5, but I have not seen a definitive answer as to what is wrong and what can be done about it.
Help would be very much appreciated as I need to know if it is a software bug that will be fixed as part of routine updates, if it is a user fixable problem (operator error!), or if the sensor is actually dead, in which case I can exchange the phone (Amazon uk).
Chasharv
Chasharv said:
When I make or receive a phone call on my new Nexus the screen blacks out. I understand that it should black out when the phone is brought up to my ear, but it blacks out even though the phone is eighteen inches away from me. There is nothing on top of the proximity sensor and it is clean. The phone is not in a case. The sleep timer in set to two minutes. The cache partition has been cleared.
I think this happened after upgrading from Android 5 to 5.1, but I cannot be certain.
The AndroSensor app always reports that the proximity sensor detects something at 0.0 inches (with 12.7 mA), even though the sensor is uncovered.
I have seen several threads in various forums on this issue with the Nexus 5, but I have not seen a definitive answer as to what is wrong and what can be done about it.
Help would be very much appreciated as I need to know if it is a software bug that will be fixed as part of routine updates, if it is a user fixable problem (operator error!), or if the sensor is actually dead, in which case I can exchange the phone (Amazon uk).
Chasharv
Click to expand...
Click to collapse
Just press the power button when that happens, screen will turn on again. Done.
Nexus 5 black screen: thanks, but more help needed
beekay201 said:
Just press the power button when that happens, screen will turn on again. Done.
Click to expand...
Click to collapse
Thanks for this, but if the power button it set to end the call it does indeed turn the screen on again, but of course also ends the call prematurely. If the power button is not set to end the call, then nothing happens when it is pressed during a call and the screen stays black. The only way out of the black screen under those circumstances is to hold the power button down to turn the phone off and then restart it!
Prior to the upgrade 5.1, from the version of 5 that came with the phone, when I made or received a call the screen remained active until I put the phone to my ear.
Further advice would be much appreciated.
Chasharv
Chasharv said:
Thanks for this, but if the power button it set to end the call it does indeed turn the screen on again, but of course also ends the call prematurely. If the power button is not set to end the call, then nothing happens when it is pressed during a call and the screen stays black. The only way out of the black screen under those circumstances is to hold the power button down to turn the phone off and then restart it!
Prior to the upgrade 5.1, from the version of 5 that came with the phone, when I made or received a call the screen remained active until I put the phone to my ear.
Further advice would be much appreciated.
Chasharv
Click to expand...
Click to collapse
if i make or answer a phone call, and put it on speaker, after a few secs it will turn the screen off automatically. If i then press the pwer button (i don't have the accessibility option on), it WILL wake the screen but doesn't end the call.
running stock LMY47D
Nexus 5 black screen, solved
beekay201 said:
if i make or answer a phone call, and put it on speaker, after a few secs it will turn the screen off automatically. If i then press the pwer button (i don't have the accessibility option on), it WILL wake the screen but doesn't end the call.
running stock LMY47D
Click to expand...
Click to collapse
Thanks for this, but the problem was that the screen blacked instantly on making or receiving a call and was unresponsive, so the only way forward was to press the power button. This either terminated the call or shut down the phone, according to how it was set, so neither was useful.
As I said originally, I suspected the proximity sensor was faulty as the a proximity detector sensor app always indicated that there was something close to it. Hence the phone would assume it was next to my ear when making or receiving calls, and so black the screen. This morning, for reasons that I don't understand at all as I have not changed anything on the phone, the proximity sensor is reported as working and the phone behaves as it should on making and receiving calls!
I suppose that either the sensor has an intermittent fault, or something in the phone's software has changed to permit it to work. I have a couple of week's left before the Amazon return window expires, so I will monitor the situation.
Thanks once more for the help.
Chasharv
I have the identical problem with my nexus 5 running stock kitkat. Makes it very hard to use the keyboard to reply to automated requests to "if... press 1, if.... press 2".
Is it possible to turn the proximity sensor off? I don't need it and it just causes problems for me.