I have seen 2-3 other threads discussing the same thing but no issues were found. Hopefully I will be lucky enough to find one.
I am using an unlocked rezound with a rom that I am not too sure of. I don't remember which one I eventually got working.
My issue is essentially the following,
Power button to lock screen is slow. The red buttons light up but the screen takes 1 minute to show.
I can dial phone numbers and even hear the other person and they can hear me but the touch screen becomes unresponsive.
Ultimately the phone restarts itself or just turns black.
Occasionally I get the error "Process System is not responding, would you like to close it?". I also now have a slight buzzing
sound coming from the earpiece in calls.
Try Wiping and flashing a new rom or doing a factory reset from within the recovery
Atheyst said:
I have seen 2-3 other threads discussing the same thing but no issues were found. Hopefully I will be lucky enough to find one.
I am using an unlocked rezound with a rom that I am not too sure of. I don't remember which one I eventually got working.
My issue is essentially the following,
Power button to lock screen is slow. The red buttons light up but the screen takes 1 minute to show.
I can dial phone numbers and even hear the other person and they can hear me but the touch screen becomes unresponsive.
Ultimately the phone restarts itself or just turns black.
Occasionally I get the error "Process System is not responding, would you like to close it?". I also now have a slight buzzing
sound coming from the earpiece in calls.
Click to expand...
Click to collapse
If you want to know what ROM you're on, go into Settings > About > Software information and it should say something under Software number. Mine says the name of my ROM.
Then just for fun you can pull down on the bottom of the list and see it stretch out and then boing back up when you let go. :cyclops:
But yeah, try wiping and if you do a factory reset make sure you back up any files you want to keep. Do a fresh flash if that doesn't fix it.
SOLUTION - PROXIMITY SENSOR CALIBRATION
Someone on here posted an app for rooted only devices that alters the sensitivity of the proximity sensor.
Dust can be causing the issue or you can use this app to fix it for you. The app fixed my problem instantly.
Related
Over the past week or so I have noticed the backlight on my Atrix acting strange during calls. Sometimes it will not shut off when placed next to my head(I can see the screen out of the corner of my eye) or it will not light up when taken away from my head(to key in a selection on a menu). Sometimes it also shuts the backlight off as soon as the call is placed and I have to press the power button to "wake it up" so that I can make a selection.
The only other thing that I noticed just a little bit ago is - while in a call the LED next to the earpiece appears to be glowing red(dim - like the Terminator's eye right before it got crushed ).
I haven't added any apps in the last two weeks and there haven't been any major updates to speak of.
The phone is basically stock. I did root it so I could use titanium backup and barnacle.
Build: OLYFRU4 1.8.3
Kernel: 2.6.32.9-00007
baseband: n_01.77.15p
android version: 2.2.2
sys ver: 4.1.83.nb860.att.en.us
Has anyone else had a similar problem? More importantly, has anyone else resolved a similar problem?
Thank you in advance for any assistance provided.
Interesting.. I have similar problems, and I've heard this is a known problem with the Gingerbread update (which you haven't done it seems). I've personally noticed that this happens after I use bluetooth and making calls and stuff with BT devices. Do you do anything like that?
I do use a bluetooth headset but haven't noticed any problems when using it.
Shortly after making this thread I checked for any OTA updates and there was the gingerbread update available. I went ahead and performed the update and the problem still exists.
I also believe that my terminology was different and that is why I didn't have success when searching. I have found several threads describing the problem as dealing with the proximity sensor instead of the light sensor. I have not found a definite solution though yet - I'm contemplating a factory reset.
So I went ahead and did the big wipe and still have the same issue. I've read over the other "proximity issue" threads which all involve editing the value in build.prop.
The problem with this is, mine seems to have problems both ways. I've had it blank the screen right after pressing "dial" and then I've also had it not blank the screen at all(allowing it to cheek dial). The other weird thing I mentioned in my first post, is the sensor LED( to the right of the ear slot) is glowing red when there is an active call. I don't recall seeing it do that before.
I'm really tempted to have an insurance claim really soon.
71chevellejohn said:
So I went ahead and did the big wipe and still have the same issue. I've read over the other "proximity issue" threads which all involve editing the value in build.prop.
The problem with this is, mine seems to have problems both ways. I've had it blank the screen right after pressing "dial" and then I've also had it not blank the screen at all(allowing it to cheek dial). The other weird thing I mentioned in my first post, is the sensor LED( to the right of the ear slot) is glowing red when there is an active call. I don't recall seeing it do that before.
I'm really tempted to have an insurance claim really soon.
Click to expand...
Click to collapse
Unfortunately, it sounds like your proximity sensor (or logic board in general) may be going haywire - meaning a hardware problem not a software problem (I'm guessing that since, as you said, it's happening both ways)...
In my sig there is a app called Build.prop editor. You can use this to change the proximity timing and distance. the little red light you see is the infrared sensor that tells the screen to shut off.
In the build.prop edit mot.proximity.delay=200
and edit mot.proximity.distance=30
should fix screen not turning off issue.
Once again link in my sig for build.prop app( must be rooted)
You can try other values that fit you, doesnt have to be 200 and 30
Ok so I want to convey all the relevant information without this being a mile long.
I have a o2 UK SGS2 running on a 3 sim. I have flashed on Lite'ing 6.1 with ninphetmaine 2.0.5. Up until the following, everything has been 100%.
This morning I downloaded Destinia and played it for a while. Before quitting I took a quick look at in app purchases to see if they charge ridiculous prices (they do). I'm not interested so I quickly spam back to close everything. This is when **** ****s up. OS becomes unresponsive immediately and I have no choice but to pull the battery. (power menu disappears instantly, no registered actions from soft keys or menu button in OS). No change on reboot.
I try reflashing Lite'ning. Mostly no change but I got the chance to get into task manager and uninstall Destinia/Launcher Pro.
I reinstall launcher pro, and now it works most of the time except:
1. Quite frequently the voice action app will load itself, and the unlock notification will pop up.
2. MTP notification will appear occasionally and phone will act like it's plugged in
3. Random Launcher/OS crashes. Sometimes screen on but no response from apps or OS. Sometimes screen won't turn on at all, just softkeys and darkness.
4. at first unlock after boot, camera makes standard focusing sound.
5. on boot, little popup dialog will read "in app purchases not supported in this version of android".
Really I doubt there's going to be any solution other than "wipe and reflash" but I'm really interested if anyone knows what would cause all these problems.
Cheers
. I'm not interested so I quickly spam back to close everything
Whatever that means looks to be the source of your problem..
jje
JJEgan said:
. I'm not interested so I quickly spam back to close everything
Whatever that means looks to be the source of your problem..
jje
Click to expand...
Click to collapse
what this means is that pressed back from the game's in app purchases screen, back to the main menu and then back to the Launcher, I'm sure everyone has done basically this countless times.
Fine but my dictionary defines spam as a different meaning .
But as posted that's where it all went wrong for whatever reason .
jje
Right I wipe-flashed stock 2.3.5 and it's STILL doing this. Voice actions popping up at random, all sorts of apps crashing and hanging all the time.
This has to be a hardware problem now, right?
just a stab in the dark but run a virus check.
I've never had a virus in my life, but I checked anyway and nothing.
Right so I've been watching my phone today. It's still doing random voice action popups. If I leave the phone on standard standby it will be fine for a while. It will then randomly turn on the screen by itself. The screen will stay on, if i leave it long enough the whole thing become totally unresponsive. If I press power the phone will wait a few seconds, then restart. If I don't touch it, it will just restart on its own eventually.
Can anyone recommend at least, some logging software that will let me look at the underlying OS and see what's happening when this is going on.
Is there any possibility your phone also goes to car-mode by itself?
spare parts app??
Your phone is more or less doing the same thing as mine is. It's a hardware issue from the seems of it. The voice command thing is from a dirty pin in the USB connector part which apparently isn't that hard to clean, for users in the thread below it actually helped to solve the issue. But my persisting issue is the unresponsive screen and power button causing an active screen to dim out and making the screen unresponsive..
http://forum.xda-developers.com/showthread.php?t=1174291
Im getting random voice talk and mtp etc. phone is all ovr the place. flashed litening and nimphet last week and seemed fine. used mhl hdmi cable and problems seemed to start from there.
millia90 said:
Your phone is more or less doing the same thing as mine is. It's a hardware issue from the seems of it. The voice command thing is from a dirty pin in the USB connector part which apparently isn't that hard to clean, for users in the thread below it actually helped to solve the issue. But my persisting issue is the unresponsive screen and power button causing an active screen to dim out and making the screen unresponsive..
http://forum.xda-developers.com/showthread.php?t=1174291
Click to expand...
Click to collapse
Read your thread http://forum.xda-developers.com/showthread.php?t=1278790 and your problems are down to the letter the same. I've resigned myself to it being a hardware fault and put in a service request with samsung. Wish I had better news.
Yea me too. My issue is that my SGSII was manufactured in UK so I'm at odds seeing as how I'm in America. The people at the Samsung call center referred me to the UK number so I guess I will have to bits the bullet.
Hi,
I am having issues with ending calls. After I speak with someone and I remove my photon away from my ear, the screen refuses to turn on. The calls stays connected. The only way to end the call is to pull the battery. This happens randomly and frequently almost half the calls.
The entire phone is unresponsive, even the power or volume buttons do nothing. The screen remains off. I guess this has to do something with the proximity sensor.
One thing I have observed is it happens a lot (much more than half) if I get to voicemail or any IVRS system.
I am on beta 0.4.2.1 of joker's. Is anyone facing the same issues? I have had this issue long, pre-beta 0.3
Looking for suggestions and fixes if anyone has one.
- Harakiri
Harakiri1298 said:
Hi,
I am having issues with ending calls. After I speak with someone and I remove my photon away from my ear, the screen refuses to turn on. The calls stays connected. The only way to end the call is to pull the battery. This happens randomly and frequently almost half the calls.
The entire phone is unresponsive, even the power or volume buttons do nothing. The screen remains off. I guess this has to do something with the proximity sensor.
One thing I have observed is it happens a lot (much more than half) if I get to voicemail or any IVRS system.
I am on beta 0.4.2.1 of joker's. Is anyone facing the same issues? I have had this issue long, pre-beta 0.3
Looking for suggestions and fixes if anyone has one.
- Harakiri
Click to expand...
Click to collapse
I did not experience this issue running 0.4.2.1. First thing I would do is download ScreenOn from the Market and set it to keep the screen on when using the dailer/call function.
Not sure what is actually causing this on your particular device though.
My HTC One Max's screen often comes on during calls. Then the touch screen reads my face's contact with the screen and acts according to what it thinks I selected. I have ended up several menu layers into apps that opened because of this. But worse, I have frequently had my calls mute - so the person I am talking to can no longer hear me.
I have had my HTC One Max less than a month, and it has had to be replaced twice, once because the 3G radio didn't work, and the second time because of this issue. Well, the current replacement has the same issue too. I used Android Sensor Box to test the functioning of the proximity sensor, which should be what controls this function. It appears to work, but my experience tells me that it stops working a few minutes into a call.
Your ideas and suggestions are welcome. I love the phone, but this is a problem I can't live with.
Is anyone else experiencing this issue?
My suggestion is to always press the power button during calls that way the phone only comes back on if you hit the power button again... The reason it comes on now during calls because your ear / side of your head covers and uncovers the sensors at the top of your phone so to eliminate that just turn the screen off by pressing the power button it work 100% for me, my wife had the same problem until I told her to start doing that.. Lmk if that works!!
Sent from my HTC6600LVW using Tapatalk
when I use the original oxygenos, I always happens (in each call) that there are unintentional touches the screen that usually make me turn the microphone off or pause the call, all this makes it impossible to make a phone call.
I tried doing upgrades, downgrades, cache cleaning, reset but nothing!
The only way to solve it is to use the CyanogenMod 13 where the bug does not occur but.
can someone help me with this problem ??? I like the stock rom and I would use it without problems
Lock the phone after acepting or making a call, maybe? Ive never had such issues with OOS.
aredpanda said:
Lock the phone after acepting or making a call, maybe? Ive never had such issues with OOS.
Click to expand...
Click to collapse
Yes! the only way is to turn off the phone with the power button after starting the conversation, it is still very frustrating!
If I type a number and make e call the display will immediately go off when I put the phone near the ear. If I just keep it in the hand it will not go off. I guess this is what happen by default. Maybe it has to do with some kind of sensor you turn off on your settings in OOS?
fotjon said:
If I type a number and make e call the display will immediately go off when I put the phone near the ear. If I just keep it in the hand it will not go off. I guess this is what happen by default. Maybe it has to do with some kind of sensor you turn off on your settings in OOS?
Click to expand...
Click to collapse
I think the screen is responsive to the touch in some cases despite the proximity sensor turns off the screen, it's a pretty serious problem, those of OnePlus are willing to fix it, but they will leave at least 30 days.
I do not understand if it is a sofware or hardware problem because with the various tests I did the sersore proximity seems to work fine, but I can not make a phone call without any problems