Had this happen on my last Sammy phone too (Charge)
The keypad works fine for the initial call but when I go to enter in a number after the call is connected such as (press one for English) the screen goes black as I go to touch it, pull my finger away and it reappears. After some persistence and a few choice words the number will finally register. Anyone else get this or better yet have a solution.
I'm on synergy rom with stock kernal, not sure if it did it on stock ROM.
Related
Got a new tp2 from sprint. whenever i make a call it flips to home screen then off then back over and over. Also when I call voicemail, the keypad never comes up until i press keypad and while i am listening it goes back to home screen then turns off. whats going on? dam its annoying!
I'm having a similar issue. When ever I remove the phone from my ear while I'm still on a call it goes to the home screen. Very annoying. It will work as it's suppose to some of the time but I'd say 95% of the time I have this issue. Hopefully someone comes out with a fix for this.
Me too (I'm on TMobile). Also, at the end of the call when it asks if you want to add to contacts, it flips back to home if you don't respond fast enough. But the worst is when I'm dialing in for voice mail and need the touchpad; it flips to home and I have to hit the bottom left hard button to get back to the phone.
I assume it's something to do with the way it turns off the touch screen based on the proximity sensor when it's up by your ear, then turns it back on again as you move away from your ear, so no doubt there's a setting somewhere to adjust that.
same here... during a call the screen goes on and off several times. may be light sensor.... who knows
anything that prompts you to make choices by picking numbers becomes a pain unless you use speakerphone. really hoping for a fix
I have no clue if this will last but I changed the setting to lock the phone if it's unused from 30min to 1hr and that seemed to work for now. Changed it back to 30min to double check, it happened first try during the call but worked properly after.
the way its supposed to work is, when you put the phone to your ear the screen goes out when you pull it away it will come on to the call status screen(not the keypad, unless you push keypad then it should stay on keypad,but if you put it to your ear it will go off, when you pull it away it will come back on to the keypad.)this feature is so you do not push buttons with your face.
Same issue...
Orginally seemed to keep on the call status screnn, but now moves to the home screnn when pulled from head.
Any fix would be apprecaited...
today i noticed an odd issue with the lights on the navicap on my TP, When the screen switches off the lights on the navicap stay illuminated (The home, back, answer and hangup buttons) the light round the dpad/scroll wheel dont light up tho, i dont know how long this has been going on though as i have only just noticed it
does anyone know why this mite happen or any ideas to solve it
cheers
I also can confirm this issue.
Seems to happen only when the light has been activated in landcape mode.
I can recreate this failure every time I reply to a SMS:
Slide open keyboard
Keyboard and navipad lights come on
Reply to sms
Press power button
...and tada! The light is stuck on
The light will go off if I press the center dpad button before I turn off the device, or if I turn back on the device and tap the button.
This problem has followed me through 3 ROMs: the stock ATT Fuze ROM, the new ATT ROM, and an older EnergyROM (8/11/09, not sure which version anymore).
I can also confirm that this problem exists across multiple phones running stock software. My first Fuze had this problem, my current Fuze has this problem, and my friend's Fuze does too. Very odd.
Not a showstopper, but I figure it's the only annoyance I really have to put up with day to day, now that I've got the phone configured the way I like it.
Anyone have any ideas?
Thanks in advance!
I've had this problem since the first day I got my phone, but it seemed to go away...now it's back with a vengeance. I'm assuming it's a hardware issue...
I have haptic turned on and sound off for button presses. The issue persists regardless of settings. Basically, the phone will randomly receive HOME button presses, while I'm not pressing the button. Insanely bothersome. Has anyone else experienced this behavior?
I did root and flash to the most recent COG, which, fwiw, made google voice act insanely wonky (was showing Google's number as outgoing CallerID, NOT my google voice number), so I had to go back. Interestingly, my RomManager backup WOULD NOT WORK and the phone was freezing on the white ATT World Phone screen. I did manage to fix it with ODIN, but entering download mode was not as easy as described, my button combination wasn't what any other post said it should be.
So this new ROM isn't exactly the same as the original stock rom, and I'm thinking of rerooting and trying something other than Cog, but obviously if I need to return this phone I should do that first. Interestingly, it didn't do the behavior described even ONE TIME when Cog was onboard.
after a few minutes of having my phone on and texting, my keyboard will stop typing letters. the keyboard will come up on the screen and i can push the letters but they wont be typed into the box, ive tried switching keyboards and using swypes but nothing will work until i reset my phone.... and when the keyboard is working my phone is agonizingly slow and freezes up constantly. just now my phone started to call somebody that i tried to call a few minutes ago but it would not call. i typed in the number and hit the green button and it just stayed on that screen....
samsung captivate... 2.2 froyo on rogers
If you're on, a custom rom, try a reflash. If you're unrooted on stock froyo, I have no idea. Replacement phone?
Sent from a phone inside a phone inside a KFC inside a McDonald's.
I would do some research and learn how to flash a custom rom. Stock OS is buggy and laggy. Which is the exact reason the custom rom community is so large.
Hi, I just got my Sensation back from the repair (new touchscreen), and now when I unlock the keyboard, it doesn't respond for 4-5 seconds, looks like the phone lags, but the other animations (like the jumping circle on the bottom) plays fine. The same issue, when I try to make a phone call, the screen is not responding to any touch while calling, I can't end a call. (The four buttons on the bottom of the phone aren't working too.) I just updated my phone to ViperS 1.1.0, I hoped that the new rom and the wipe will help, but it didn't. The ROM before (and when the accident happened) was the latest OrDroid.
Do you have any idea how to fix it? In other situations, the touchscreen works perfectly.