I'm on stock rooted. Whenever I try to call someone, I dial the number, hit the call button and it kicks me out of the dialer app and puts me back onto my launcher screen. Anyone else noticing this issue? I haven't disabled any apps.
EDIT: Weird. Rebooted and it didn't fix it. Powered down, powered back up and it's working again. Wondering if anyone else has had this issue? I'm on T-Mobile.
Ascertion said:
I'm on stock rooted. Whenever I try to call someone, I dial the number, hit the call button and it kicks me out of the dialer app and puts me back onto my launcher screen. Anyone else noticing this issue? I haven't disabled any apps.
EDIT: Weird. Rebooted and it didn't fix it. Powered down, powered back up and it's working again. Wondering if anyone else has had this issue? I'm on T-Mobile.
Click to expand...
Click to collapse
Never seen that issue. Also on T-Mobile. Next time a weird thing happens try holding power button till it hard reboots. I have other weird issues some times. I think xposes causes them. Hard reboot fixes it.
Related
sometimes when i get a call and i try to mute by pushing the volume button up or down, it wont work and it will keep on ringing until i pick up or hit ignore.
is anyone else experiencing this problem?
bigneeker said:
sometimes when i get a call and i try to mute by pushing the volume button up or down, it wont work and it will keep on ringing until i pick up or hit ignore.
is anyone else experiencing this problem?
Click to expand...
Click to collapse
Have you installed maniac's Auto-Keylock freeware? (the one that locks your keypad after a given timeout). There have been reported some issues with it.
no i havent installed auto-keylock.
maybe its another program.
i will keep on checking to see what is causing it unless someone else knows what the problem is.
the problem stops once i soft reset it but it acts up again after a few hours.
no one else is experiencing this problem?
bigneeker said:
the problem stops once i soft reset it but it acts up again after a few hours.
no one else is experiencing this problem?
Click to expand...
Click to collapse
Yes my S710 does the same thing...quite annoying really....
no one knows whats causing this?
its really frustrating. i hope someone find a solution to this problem.
Based on own experience - when the button is not working - try to switch to "Vibra" profile and back. Sometimes it solves the issue.
I have a USCC Samsung Mesmerize, rooted EC10 with Voodoo with TW... Anyway, my phone only vibrates when ringer is turned on, and when I try to select a new ringtone under Sound Settings, my phone vibrates and says sorry! process com.android.settings has stopped unexpectedly. So I have no ringtone, only vibration...
Also, when I attempt to raise the volume of the ringer using the side key, while on homescreens, the phone reboots...
Any help/ideas? I tried a reboot and factory data reset to no avail...
Thanks a bunch
I had this issue and hard reset to solve it.
Sent from my SCH-I500 using XDA App
Yes... Issue solved, wiped cache in recovery and hard reset... Thanks
Please help noobie
I have the same issues since upgrading my samsung mesmerize to 2.2. The volume shortcut keys black out the phone and in the settings for voice call ring tone i get the process com.android.settings error message.
Is there somewhere I can go online to get details how to do a hard reset and clear the cache through recovery?
I also have the issues with missed calls but the USCC reps tell me there is a patch coming out. When I explained the issue I have no one had a clue what to do.
Any help is greatly appreciated
Thank you!
Volume button reboots phone
My husband and I are having the same problem with our new Samsung Mesmerize phones -- the volume button makes the phone vibrate and reboot, regardless of whether the button is pushed when a call is in progress, the browser is being used, or the phone is idle. This is just bizarre. There has to be a way to fix what should be such a basic function. This phone is too expensive to have the volume button not work!
Any thoughts on how to fix this? Thank you in advance!
kdkmilwaukee said:
My husband and I are having the same problem with our new Samsung Mesmerize phones -- the volume button makes the phone vibrate and reboot, regardless of whether the button is pushed when a call is in progress, the browser is being used, or the phone is idle. This is just bizarre. There has to be a way to fix what should be such a basic function. This phone is too expensive to have the volume button not work!
Any thoughts on how to fix this? Thank you in advance!
Click to expand...
Click to collapse
Are you running stock? If so, sounds like a hardware issue. USCC will tell you to try a factory reset so give that a go. You will lose all settings and user apps though. Otherwise you may be looking at a warranty replacement.
Last night I noticed that pressing the power button on my phone no longer did anything. Thinking that maybe the phone had somehow become frozen, I pulled the battery and put it back in. Much to my surprise, the phone came on all by itself without me having to do anything. It seems that somehow the power button got stuck in the "pushed" position even though I can still push it like normal.
I have managed to work around the issues for now thanks to some features of Cyanogenmod (I can now wake the phone up using the volume keys and lock by tapping a widget in the notification area), but I'm wondering what caused this and if it's something that could be easily fixed.
Has anyone else ever experienced something like this or does anyone know how I could go about fixing the issue?
Oldiesmann said:
Last night I noticed that pressing the power button on my phone no longer did anything. Thinking that maybe the phone had somehow become frozen, I pulled the battery and put it back in. Much to my surprise, the phone came on all by itself without me having to do anything. It seems that somehow the power button got stuck in the "pushed" position even though I can still push it like normal.
I have managed to work around the issues for now thanks to some features of Cyanogenmod (I can now wake the phone up using the volume keys and lock by tapping a widget in the notification area), but I'm wondering what caused this and if it's something that could be easily fixed.
Has anyone else ever experienced something like this or does anyone know how I could go about fixing the issue?
Click to expand...
Click to collapse
Hi, take a look here:
http://forum.xda-developers.com/showthread.php?t=1524858&highlight=power+button
and here
http://forum.xda-developers.com/showthread.php?t=1504501&highlight=power+button
Anyway, someone solve this problem opening the nexus s and manually cleaning the power button. Here a guide to open your device if you want to try:
http://www.ifixit.com/Teardown/Nexus+S+Teardown/4365/1
Opening my ns and cleaning it did the trick for me. Worth a try, your warranty is void now anyway
Sent from my Nexus S using xda app-developers app
Thanks for the info. I'll give it a shot when I get a chance.
This has happened a number of time using both Dalvik and ART.
Phone rings, I try and answer by swiping the green button, the phone gives a little vibrate and stops ringing but nothing else happens. It still looks like I have not answered the call. No other buttons will work and I have to do a long press power button restart.
Searching shoes similar behavior on other Android phones eg. Nexus and others.
Anyone else experiencing this?
Seems I am the only one experiencing this. I did a hard reset and that still did not fix the problem.
Checking voice messages the other day I had a similar freeze up.
Replacement G3 on the way from AT&T. This will be number 4!
Just wondering if anyone else's back button occasionally stops working? It's only every now and then, and you can still see it respond to touch but nothing happens and multiple presses do nothing.
Pressing the home button always works, then after that it will start working again. It's happened a couple of times today already.
Not a biggy I guess, but quite annoying.
Anyone else? Any know why this might happen?
Thanks in advance.
A few times, but always in a crashed app so I assume it's the app not responding.
Sent from my SM-G955U using Tapatalk