Is anyone using a USB keyboard with their Tab 3? I have wierd problems with mine on a 4.2.2 t315. If there is a pause of more than about 2s between key presses the next key press causes the screen to turn off, the next one turns it back on (locked), the third one unlockes it and the fourth one gets correctly registered. I suspect there is either a problem with my keyboard (don't currently have another to check) or with the USB autosuspend that is set to 2s. Unfortunately I have not yet rooted my Tab (a bit scared to lose the warranty) otherwise I woul check if I can owrride the default USB autosuspend.
Any experience with this kind of problem?
Related
Hi!
Something is wrong with the touch on my Xperia S. When I plug in the charger or headphones the phone starts to register every tap as a long touch, but only on the lowest centimeter of the screen plus the back, home and meny buttons.
An example is if I tap the Homebutton the list of previous apps opens up, and if I press an icon in the dock it just wants to move it, just like if you long press on it. This makes the phone pretty much useless as I cant use the lower part of the screen.
Like I said this only happens when I have the charger or headphones connected, otherwise it works just fine.
Anyone knows if there is a solution for this, or should I just return the phone?
"EDIT: It seems like the problem goes away after the charger has been connected for a while"
Just clean your screen and if any screen protector exists replace it. If the problem still exists do a software repair
I have a problem with an HTC Incredible 2. In portrait mode two keys (j & n) do not respond or an adjoining key displays.
Two different repair companies have tried three different replacement LCD and digitizers. The problem remained.
Both shops told me it was a "software" problem. One said it was a faulty ROM.
I replaced the ROM (Evervolv) with Cyanogenmod 7.2. The problem remained. I installed Cyanogenmod 10.2. The problem remained. I tried Swiftkey, ICS, and Jelly Bean keyboards. The problem remained with all of them.
Does anyone have any idea what this might be and how to fix it?
Have you tried pressing those keys with different fingers? Maybe you're just pressing them wrong somehow.
Does the area of the screen where those keys are respond to touch when the keyboard isn't being shown?
When you install new ROMs, do you first wipe everything but the SD card? You're supposed to do that before installing ROMs. If you don't, you could have problems. The best way to do a thorough wipe is to use chillybean's Anti-Venom Super Duper Wipe utility inside of 4EXT Recovery.
Have you tried pressing those keys with different fingers? Yes, fails with different fingers and stylus.
Does the area of the screen where those keys are respond to touch when the keyboard isn't being shown? No.
When you install new ROMs, do you first wipe everything but the SD card? Yes, using Anti-Venom Super Wipe
That definitely sounds like a hardware problem then, but you also said "Two different repair companies have tried three different replacement LCD and digitizers. The problem remained." Are you using a screen protector, or a case with a screen protector built in? When you take it off, what happens to the problem?
Here's a way to more definitively verify that it's a hardware problem. Temporarily change the keyboard layout to something like DVORAK instead of QWERTY. What happens? Do j and n start working, but now the two keys where j and in were (with QWERTY) no longer work?
A similar test would be to change SwiftKey's settings so that the keyboard is detached from the bottom of the screen, allowing the keyboard to be moved freely to anywhere on the screen. To do this, first set your keyboard layout back to QWERTY. Then, bring up the SwiftKeyboard and press and hold the "123" button for a few seconds. Choose undock, move the keyboard to a new location, and then test each key.
These two tests could effectively show whether it is a hardware problem or a software problem. I'm leaning towards hardware based on your last comment, but these tests should add further proof.
If it's a hardware problem, one way to show the repair people where the problem area (the area not responding to touch) truly is would be to get install some kind of drawing app. Something that will let you freehand paint on the screen with a finger or stylus. Using a small brush size and one solid color, try to paint the entire screen. It should then be pretty obvious where the screen is responding to touch and where it isn't.
One possibility that could make it a software problem: After installing a new ROM, do you restore data from a backup? Have you tried not doing that?
Hello, n00b here!
I have a Samsung Galaxy S II (SGH-T989 T-Mobile), that has four 'hard softkeys', that is, touchbuttons (menu, home, back, search) outside the display area [no physical clicky Home button], and can't for the life of me, or with bad google-fu, figure out how to make the Home button take me right back to the home screen (launcher). When I press it once I just get a haptic 'bzz', and nothing at all happens. When I double-click it, as I have set in the settings, it goes to Task Switcher, from where I then can reach the home screen by tapping outside the miniaturized windows of running apps.
But, how to I make a single click go directly to the home screen?
Ideally I'd like to have the four buttons be menu=menu, home=homescreen, back=back, search=taskswitcher. Installing a specific app for it (that preferably won't eat up screen real estate with on-display softkeys), another launcher, another Settings app etc, is all okay by me as long as it fixes this major nag.
I don't get to choose other than a preset list in Settings, though. :/
System info is SAMSUNG-SGH-T989, CyanogenMod 11-20140506-NIGHTLY-hercules, Kernel 3.0.101-DIABLO-3.3, launcher Trebuchet 1.0.
(As a little gripe and boo, CM-11 on the Kindle Fire worked wonderfully, where the three on-display softkeys for taskswitch/home/back did just what I wanted them to. I can't see any reason why a JB'd phone would be unable to remap the keys to a select very few options just because they happen to be outside the actual display area. Especially as Home doesn't lead to the Home Screen. :/ )
Tons of grapefruitgrateful for any help here!
-Henrik
Problem solved, good enough for me - installing Hellybean and getting rid of all KitKat related junk.
Suddenly the phone works like it's supposed to, whee!
SII T989 home keys not working
Snoutfoo said:
Problem solved, good enough for me - installing Hellybean and getting rid of all KitKat related junk.
Suddenly the phone works like it's supposed to, whee!
Click to expand...
Click to collapse
SGH-T989 Galaxy S II. Home keys aren't working. Sent phone in for charging port repairs. Sent phone back to replace touch keypad flex cable. Buttons have worked intermittently since. They also light up intermittently. I was hoping this was software related. Kies says the firmware is the latest. Any suggestions? The phone is for my 10yr old. Don't really want to invest in something new for her right now, just for games!
I have a Samsung Galaxy S II (SGH-T989 T-Mobile), that has four 'hard softkeys', that is, touchbuttons (menu, home, back, search) outside the display area....and they are all not working now...the moment i on the phone sync not allowed pop...........please help me out
help
hi guys i I have a Samsung Galaxy S II (SGH-T989 T-Mobile), that has four 'hard softkeys', that is, touchbuttons (menu, home, back, search) outside the display area....and they are all not working now...i cnt hve it repaired coz the accessories of this model re scarce in our nation bt i hve found an app whch cn help m with the home and back button now i want the menu button so that i can b able to add APN on mi fo to use internet
My lovely tab s suddenly stopped working since yesterday. If I press power/home button then the screen turns on. But I cannot swipe to unlock. The screen is frozen. It doesn't respond to any touches and the information on the notification bar (battery, wifi, time...) stay the same.
I cannot turn it off by holding power button (tried all the methods that i could find on the Google's search).
I also cannot reset the tab by using Samsung 's Kies because it was on a restricted account (has to be on owner's account in order to have Kies works).
Any one experienced the problem? Is my tab defective one? Can I exchange it for a new one (21 days of purchase date)? Please help!
Read this: http://forum.xda-developers.com/showthread.php?p=54618555
Good afternoon all, I'm wondering if anyone can help.
My Galaxy Tab Pro 10.1 developed an issue with the screen (after travel - where it may have been knocked around a little)...
The tablet boots up fine and the screen appears to work normally.
However once the screen times out and switches off, or the screen is switched off by the power button, it is not possible to get the screen back on.
It appears that it's just the backlight that is not coming back on?.... as the screen responds to touch (you can here the pin code buttons being clicked).... but can't see anything at all on the screen.
Rebooting the tablet from here makes the screen come back on as normal - so as it works like this and just does not come back on after being 'on staandby' I thought it might be a software issue... I did a full factory reset but unfortunately the problem is still exactly the same.
I've had the tablet to bits to see if I could see any cables loose or anything - but everything looks ok - I think (Although it's the first time I've had one apart and wasn't 100% sure which cables were for the screen)
There was nothing obviously disconnected or loose.
Has anyone come across this fault before or can anyone provide any more guidance? Maybe a particular cable to check or how to check it?
Many Thanks,
Tom Leitch
I have the same issue, but I was able to fix it entering the factory mode and pressing the sleep button. That was possible using the calculator and entering (+30012012732+ and then entering *#0*# to get to test mode.
The problem now is that I'm using lineageOS so I don't know how to get to that menu or trigger that sleep button. Anyone?