I've looked around and haven't dug up any answers, so I figured I'd ask.
The right directional button on my tilt is stuck on. It's not pushed down, the button is free to be pushed in and out, but the phone is registering it as being held down. It even does it when you open the phone into landscape mode, but it selects downwardly because of the change of screen orientation.
If you mash the face buttons while it is glitching, it stops, but then the right direction key doesn't work. However, if you slide it open or closed, it just starts doing it again.
I am at a loss for ideas. Internal problem?
Related
Hey guys,
I've got this problem. See, after sliding my fingers across the tabs, checking sms's, turning on wi-fi, and trying to logon to FB using the app I can't lock the device
What happens is, everytime i hold the hw "end" key to lock the device, nothing happens and the instant I let go, my touchflow goes to my "favourites" and if I hit the end key again, it continues going to next tab.
When I hit the "<--" key, it goes to the left tabs in the touchflow.
While doing this the directional and center button work, but the "talk" and "home" button don't work.
The only fix that I know of is rebooting the phone. But on some occasions I have been able to manage to get it to lock again.
Cheers!
Hi guys, I just got my new replacement Bell Samsung galaxy S and have gotten things running on it again, but the damn thing keeps going into some weird screen capture.
What happens is that when I hit the "back" button it will go dark and the "menu" button will light up. repeatedly hitting the back button will do nothing, and hitting the menu button will do nothing. Pressing the center "home" button will take a picture of what I have displayed on the screen.
I go and check my running applications and it shows this "screen capture service" running. I stop it and then I continue on what I'm doing and it happens again, going back to the running apps and it is back.
The only way it seems I can use my "back" button is if i hit the "volume" button on the side and then both the "back" and "menu" buttons will light up, and then I have to wait until they both go dark before I can hit the "back" button and have it work. if I hit it will they are lit up it goes back into the screen capture "mode"
The phone came in the mail with I9000UGJL2, firmware 2.2.
Any advice on how to permanently kill that damn screen capture thing would be greatly appreciated because it is driving me nuts. I get a way with maybe 2 "back" button pushes where it works and then it goes into that mode
Same problem...
Samsung Galaxy S i9000 (Facinate)
It seems that by pressing the back button too quickly puts you in the Screen Capture mode...Back button dims but the Menu button stays lit. I found that if I push the Home button that take s the screen shot, then wait for both the Menu and Back button to come on and then lowlight, I can then hit the back button and continue on for a while?
Package name: com.sec.android.app.screencapture
Source: /system/app/ScreenCaptureService.apk
Please, I would like to find out more about this app in order to try and control it. It really slows moving back when you have to wait for the Menu and Back buttons to lowlight before you can hit the back button again!
Just after posting the above, I was able to Force Stop the package and I have not had a problem with the phone going into screen capture mode since.
Woohoo!
My i9100 built-in Screen Capture Service default output is png format. How can I change it to jpeg format?
Like the title says... holding the power button does not produce the "Shut down, restart etc" menu anymore. It locks the screen just fine and dose force feed back upon long hold but no menu pops up...any ideas whats up?
This just happened recently.
Also sometimes when I unlock the phone it randomly presses either the home key or back button. Any ideas on this as well?
the first is a software problem, a reflash should fix it.
the second is a hardware issue, could be caused by humidity inside the phone, remove everything from the phone (battery, cover, cards) drop it ina bag of rice for a few hours to soak up the moisture. if that doesnt work then if you're still under warranty you could get it replaced.
First off, I'd like to mention I'm new here, so if I'm posting this in the wrong place, please forgive me.
Second, the topic: I've had a problem with my power key for at least half a year now. As far as I can tell, it started after I accidentally dropped it (No harder than I usually would if I ever did drop it which is rare) with my otterbox case on it. I picked it up and tried to turn on my screen and noticed a long lag before the screen came on.
I didn't think anything of it until the next day the key wasn't responsive at all. I looked, and the key is not cracked, and there's no visible damage from the outside. I figured out if I shook the phone, or tapped on the button a certain way, sometimes I could get the button to work, but that was just unacceptable. So i found a fix in the application "Button Savior". Coupled with the volume rocker wake feature of my ROM.
But after all this time, I'd still really like my power button to work, so here are my questions:
1. Is this a common problem? Have you yourself experienced this, or have you seen others have this problem?
2. Any ideas on what is actually wrong with the button, and how I could fix the button mechanism? I'm not against taking the phone apart to repair it if that's what it takes.
Thanks in advance guys!
Additional info: Maybe not a hardware issue?
I've found that while having to enter into recovery mode by using the three button combo, it seems to register the power button being pressed in order to actually get into recovery, but once in recovery I have the same old problem of not being able to use the power button (as in I have to shake it and tap it a lot for it to register, and even that is unreliable)
Hello,
I have a rooted and TWRP installed but otherwise stock 5.something T710 that I had worked on months ago. It's been great and my daughter had been using it to watch videos a couple days ago. I took the tablet from her at the end of our road trip and noticed it had about 63% battery left. I left it in the truck while we went to the movies(about 40 degrees f outsides) and then drove home without ever touching it until we got home. I went to use it when we got home and it would not turn on. I plugged it in to let it charge thinking it died for some reason, using the stock charger, though battery icon never appeared. The next morning I went to check it and it still would not turn on.
When I press the power button or plug in or unplug the charger the Recent and Back soft key lights will turn on for a second, then turn back off again.
I've tried:
Holding the power button down alone for over 3 minutes.
Held the power and volume up button for over a minute
Power and volume down for over a minute.
Home, volume down and power for over a minute
Home, volume up and power for over a minute.
I can connect it to my computer and it recognizes that my Tab S2 is connected but no files show as the default for the device was just charging mode and not the file modes.
Odin3 v3.10.7 recognizes it as connected. But fails to send the TWRP file again.
Any help?
Since the soft keys light up and the computer recognizes the device, it sounds like maybe the tab is still working but with no display? By any chance did you have adb working? I f so you could try rebooting, or booting into recovery to see if you see anything on the screen. It's possible that when you held the button combos, that it did boot into download and recovery but you couldn't see anything? In which case it could be a hardware problem. Hopefully it will fix itself! Sorry I can't be of more help..
Well adb shows the device as unauthorized. Reboot command says the same thing.
The home key is unresponsive to my finger print unlocks and no sound plays when I try to adjust the volume, like the ding sound it makes to hear if this is the volume level I want. There are never any of the capacitive touch vibrations or whatever its called to feel when you press a button on the screen.
I was wondering if it had something to do with hardware it's just strange that it would stop working from just being in my truck. From my knowledge it was never dropped or bumped heavily or anything, at least recently.
I guess it is possible something just burned up inside, that would be inconvenient, I've got to look up if its still in warranty. I love the size and performance of this thing.
Thanks for replying, hopefully more to come.
Still can't get it to work, same issues as above. I let the battery fully die which took about 2+weeks from the initial post. Which is to say that eventually the back and recent buttons stopped lighting up. I recharged it and after holding the power button for a few seconds the same condition repeated itself. If I touch the power button or home button the back and recent button back lights turn on for a moment and turn off again. There is no other indication of life. I would assume if it was just a dead screen then I should feel it try to turn on.
If I had to replace parts which ones should I look at first? Probably just the main board?
Buy a new one. Send yours in as defect. Done.
erase111
I see that is an old thread, but I having the same issue to a certain degree. The screen goes dark, but I can see the back light. If I play around enough times, (pressing the back and process button, before pressing the sensor button... Sometime, pressing the volume buttons and back button before pressing the sensor button), everything goes back to normal. Of course, it some random time, even when I am reading a web page or some other activity, it will go back to black.
So has anyone figured out what this issue actually might be? I thought maybe it was an issue with the ROM I was using, so I just moved over to LineageOS 16, but the problem still continues!