Resolved (for now, at least)
The home key on my phone appears to have stopped working. Nothing happens when I press it. Occasionally, if I mash my finger on the area aroud the home key, my lockscreen wallpaper will display for a second or two before returning me to whatever app I was in.
A) Is there any way to tell whether this is a hardware problem (somehow not making a connection when I touch) or software problem (phone detects the touch but doesn't respond)?
B) Any simple fixes I can do to restore functionality?
C) If it is a hardware problem, what are my options? How is Samsung at handling exchanges? I've rooted my phone - if I do need to send it in, should I restore it to factory default first?
__________
10:00 am:
Okay, that's really bizarre.
Phone restart did nothing, using task manager to clear all apps and ram did nothing...
I turned off Tasker to get a clean(er) logcat to share, and then the home button started working again.
I've turned Tasker back on again, and it's still working.
Weird.
A. Have you flashed a kernel recently? Gotten it wet or Left it in a very humid area?
B and C:
You could flash to stock and reset the flash counter if the problem is still present, you are now in a state ready to get a warranty exchange for faulty hardware.
studacris said:
A. Have you flashed a kernel recently? Gotten it wet or Left it in a very humid area?
Click to expand...
Click to collapse
No to all of the above.
Trying to decipher logcat, I do see lines which suggest the system does know something is being touched:
Code:
12-10 09:31:32.768 D/InputReader( 385): Input event: value=1
12-10 09:31:32.778 D/RestrictionPolicy( 385): isHomeKeyEnabled :true
...
12-10 09:31:32.908 D/InputReader( 385): Input event: value=0
12-10 09:31:32.918 D/RestrictionPolicy( 385): isHomeKeyEnabled :true
12-10 09:31:32.928 D/RestrictionPolicy( 385): isHomeKeyEnabled :true
Okay, that's really bizarre.
Phone restart did nothing, using task manager to clear all apps and ram did nothing...
I turned off Tasker to get a clean(er) logcat to share, and then the home button started working again.
I've turned Tasker back on again, and it's still working.
Weird.
Related
I noticed a weird, repeatable crash I'm getting today and I'm curious if anyone else is experiencing it:
Settings>Sounds and Notifications>Notifications tab
Settings as:
Event: Phone: Incoming Call
Ring type: Vibrate and ring
Ring tone: Ring-OldPhone2
When I test the settings, everything works fine, but when I hit OK to leave the page, the Event box goes blank, and it kicks me out to an error message that there's been a shell32.exe crash. (It keeps whatever settings I make, though.)
Whether I pick send or don't send, a new screen then comes up and thanks me for sending the error data. Then, it goes out to a splash screen that shows the phone as locked. I have to hit the lock button to get back to my Today screen.
I can repeat this pretty consistently on my Verizon TP.
kal
Get that alot when Im running opera and it opens up a pgae slowly. What causes this?
mrbonner said:
Get that alot when Im running opera and it opens up a pgae slowly. What causes this?
Click to expand...
Click to collapse
No idea. I've had about 10 Windows Mobiles/Pocket PCs, and I've never had it happen before.
Confirm
I confirm the bug, and its really bugging me! I have to turn off the device completely because some application won't work right.
Please, help!!
i get this error with the TF3D at times and have to restart TF3D
I have had this happen a couple of times too, both times I was previewing ringtones.
I had that problem when I first got my phone I went crazy and used Adv Config to change nearly everything there was, shortly afterwards I got a shell32.exe error and a gwes.exe error. I finally did a hard reset and tweaked more carefully and since then haven't had any problems.
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.
Hello, sorry if this is in the wrong forum. I do not believe this to be a device specific problem and could use help from anyone.
Background;
I have a LG Optimus G2X (p999), running CM7.
The phone got waterlogged being in a backpack during a thunderstorm. The common "overnight-in-rice" remedy worked to dry the phone. On power up everything seemed fine except for one thing, the notification that says "Safe to remove SD Card". Upon further inspection it seems to be irrelevant to the real problem, as the sd card is still readable and writable by the phone.
Problem
The phone "freezes" after allowing the phone to sleep (locking not necessary for the problem to occur). After the screen goes off for more than a few seconds, then next wake action will turn on the screen but the system will not respond. Only hitting the power button seems turn off the screen. From that point onward, no key is responsive (screen will stay off). The cause seems to be caused by the following logcat message
[ 09-12 16:36:26.434 1110:0x495 W/SharedBufferStack ]
waitForCondition(LockCondition) timed out (identity=67, status=0). CPU may be pegged. trying again.
Click to expand...
Click to collapse
This warning is spammed from the point of "freezing" untill I pull the battery. Also the following message seems to be an indicator as to why the phone won't wake again.
[ 09-12 16:36:26.991 1110:0x497 D/KeyguardViewMediator ]
wakeWhenReadyLocked(26)
Click to expand...
Click to collapse
The problem is difficult to debug because I cannot debug it, literally. The problem only occurs while on battery power. Connecting the cable to a usb port stopping this problem from occuring.
Things I've tried
-Airplane mode (to eliminate any communcation device as being the problem)
-Loaded an entirely different rom (Paranoid Android CM9 Based)
Question
Does anyone have any ideas as to what the problem may be? or possibly advice as to how I can further debug the situation.
I changed the title to indicate the problem more clearly. Anyone?
Hi, I have a 2 week old handset which has now twice displayed a pretty strange/annoying bug.
I have been using no Stamina settings other than location based WiFi and queue background data for the most part to gauge battery life under my normal work schedule but I noticed last week that my saved WiFi at home wasn't on, so instinctively I tried to click the WiFi symbol but to no avail.
I then tried to restart the phone, but when pressing the power off option, it simply booted me back on to the screen I was on before hand. This continually happened until I got pee'd off and repaired it.
Again today I ran into the exact same problem. No WiFi and I could not power off. After several attempts at powering off I managed to get it to boot into safe mode where I started uninstalling apps to rule out any rogue apps. I still couldn't reboot forcing me to repair and wipe the phone.
I keep telling myself that this is merely a software bug and I can't seem to find other posts where people are suffering similar problems.
So I futilely ask, has anyone ever had anything similar happen to theirs?.
Yeah I think this is a software bug too, a similar thing has happened to me a couple of times with the wifi becoming "stuck" and rebooting the phone fixed it but if you're having trouble shutting down your phone, have you got quickboot enabled? Regardless of that though, you do have two options to force a restart, either hold volume up and power, this will force shutdown or press the small red button next to the sim card tray.
TheOnlyIntruder said:
Yeah I think this is a software bug too, a similar thing has happened to me a couple of times with the wifi becoming "stuck" and rebooting the phone fixed it but if you're having trouble shutting down your phone, have you got quickboot enabled? Regardless of that though, you do have two options to force a restart, either hold volume up and power, this will force shutdown or press the small red button next to the sim card tray.
Click to expand...
Click to collapse
I am pretty sure it is the quick boot option now. Stupid bug.
Phew...don't have to return it now.
I think sony have disabled the quick boot functionality for some reason, I ticked it thinking it might be almost like a reboot instead of power off & then power on, later I noticed the power off menu wasn't doing anything when tapping it, was almost about to do a reset but then remembered I ticked the quick boot option.
Hope they enable it in future updates.
Hello Everyone. I have my new Samsung S6 Edge about 3 weeks now. It worked flawlessly the first week and a half but lately I've been getting an intermittent problem with the sensitivity of the touchscreen and it is very annoying. I have to swipe, touch a letter (if texting), or touch an icon, multiple times before it will execute the touch. Sometimes it seems as if it is in slow motion where the execution responds 4 to 5 seconds after the touch. There has not been any new software added and I always close out of any running programs.
I have tried all of the following to which none had any effect:
a) Restarting the phone by using the on/off key dialog box
b) Shutting it down for a couple of minutes and starting it again
c) Using Samsung's method to restart the phone by holding the on/off key and down volume key simultaneously
After a day and a half of frustration I was ready to take it back to my mobile supplier when it all of a sudden starting working properly after checking to see if my phone volume was at the maximum volume by hitting the up volume button. It worked well for about 3 days and then started to do the same thing. So again, I played with the volume down and up buttons until the touchscreen sensitivity worked.
I'm currently having the same issue again which prompted me to post this message. Playing with the up and down volume keys seem to help it at a ratio of about 7 out of 10 times. I've searched the web but haven't found anyone else with the same issues. A look at the Applications Manager under Running apps, System is taking up 1.1 GB, Apps taking up 530 Mb, leaving 0.99 GB of free memory.
Any suggestions? Maybe I should be taking it back for a hardware replacement?
Thanks for listening.
OK, so now I've come to the conclusion that hitting the volume up key was just a fluke although It seemed to help sometimes. S6 touchscreen returned to normal again yesterday afternoon. It just comes and goes which makes it rather difficult to show a mobile technician. I'll have to wait until it malfunctions again before taking it in to a Samsung Repair shop.
Me too....
I have subscribed to this thread, in hopes of finding some clues, because I too, have noticed the same exact behavior that OP described and was searching for a remedy/explanation. Also, had the volume up and seemed to somewhat fix it, but like OP said it is sporadic. I, by accident in trying to clear the cache, completely blew away my phone and had to rebuild my phone as I had before and even after a complete reset, I still have the same behavior.
Hi Chris, I stumbled across another interesting behaviour. While the phone is acting up, if you press and hold the UP Volume key (keeping it depressed) you will be able to scroll and press icons as normal. As soon as you let go of the volume key, the issue continues.
This is a link to a video I uploaded today to You Tube that shows exactly the issue I am having.
w w w .youtube.com/watch?v=vkfaxILs4VQ&feature=youtu.be
Just saw your vid, looks like yours is more pronounced than mine (non-Edge btw) and happens once in a while and then it goes away - I am hoping it isn't progressive. I can't seem to identify what triggers the sluggish behavior. I typically clear all apps from the recent apps as a matter of my normal operation in all my previous smartphones. When I notice it the most is when pulling down the notification center and either nothing happens or I have to pull down the shade all the way down for it to stick, otherwise it slides back up.
disable briefing app
Alex-V said:
disable briefing app
Click to expand...
Click to collapse
Thanks Alex, I tried your suggestion and disabled Briefing, cleared the cache & data, then restarted the phone. It did not fix the problem.
DreamMaker888 said:
Thanks Alex, I tried your suggestion and disabled Briefing, cleared the cache & data, then restarted the phone. It did not fix the problem.
Click to expand...
Click to collapse
for me it's much better..still think it's also the memory problem..as around a half day all is fine..than the lag starts..
Took the phone to a Samsung Repair Shop today. Turns out the LCD display was malfunctioning. It took them 1.5 hours to repair and replace under warranty. Hopefully I won't have anymore issues with it
DreamMaker888 said:
Took the phone to a Samsung Repair Shop today. Turns out the LCD display was malfunctioning. It took them 1.5 hours to repair and replace under warranty. Hopefully I won't have anymore issues with it
Click to expand...
Click to collapse
Wait what? They told you the LCD screen is broken....?
Alex-V said:
disable briefing app
Click to expand...
Click to collapse
Briefing app? Can you provide more details please?
I'm having the same issue
To send a text I have to hit almost all the buttons 3 times! This just started. I may have to root this phone now. This pisses me of
He hair s trying appear.. This is what it looks like trying to use my phone now. I originally wrote "the issue is getting worse" but the lag is unbearable now
delete
delete
Alex-V said:
delete
Click to expand...
Click to collapse
lol....my Rom will come. massive. later..must sent phone into warranty repair..touchscreen digitizer is not. working fine
Hello,
For touch screen problem try this:
-in dialer type *#2663#
-TSP firmware update (general)
You should see "PASS"
That have solve my touch screen problem...
-JFK- said:
Hello,
For touch screen problem try this:
-in dialer type *#2663#
-TSP firmware update (general)
You should see "PASS"
That have solve my touch screen problem...
Click to expand...
Click to collapse
This solve my unresponsive touchscreen issue!!! Thanks very much
-JFK- said:
Hello,
For touch screen problem try this:
-in dialer type *#2663#
-TSP firmware update (general)
You should see "PASS"
That have solve my touch screen problem...
Click to expand...
Click to collapse
actually it really helped a lot
thx bro
Yes, I did that same thing, and it did help a LOT.. however after the latest update (I have the Edge+) the issue returned.. did it again, and it "fixed" it, but for how long?
And why is this happening??