[Q] Touchscreen does not react properly - Galaxy Tab 10.1 Q&A, Help & Troubleshooting

Hey guys
My Galaxy Tab 10.1 is giving me a hard time since a few weeks.
I run the CM 10.1 nightlies on the device and have the following issue:
The touchscreen does not react to my finger properly. Sometimes it works, but then doesn't react anymore. I then press the power button, to send it into sleep mode, then press it again to wake up. the device reacts then like 99% of the time to unlock it. but after that its just a pain in the a**. As far as I can remember, I did not change the ROM when this happened, but since then I tried dozens of different nightly versions, even ones that I know they worked before.
The strange thing is, that it seems to be dependent on the position sensor, because when the tablet is on a flat surface, and is not moved, it works the best. Not 100% but like 80% of the time. But when I hold it in an upright position, or just in my hands, not flat on a table or something, it reacts to like 5% of my tries...
I have been searching on xda and on google about that problem, the most matching one was a driver issue that occurs after like a minute or when a graphic intense app has loaded. They provided a kernel fix, which just made my tab boot into infinity and never reaches the lock screen. after factory reset it boots again, but the problem still exists.
hope somebody can help, because I love my Tab and I can just not accept the fact that it could be a HW issue, since it works 99% of the time on the logon screen, and due to the fact of the position sensor being involved...
thanks in advance! please make me happy again!

@shr00my
Let me ask you this..Does this problem occur in all apps or just you're browser...?
Also..when you flash a new rom..I assume you wipe data/cache/dalvik cache...but do you go in and format system( only system )...you might have something left over from a bad flash that is causing problems..

Hi Gil81
Thanks for your answer! Yes that happens everywhere, in the android menu, homescreen, inside games, video player etc...
Yes i always wipe the caches and data. But I also tried various combinations with different nightlies and wipe scenarios.
Could you tell me a good different rim that is on android 4.2 and not CM based so I could try to flash that and see what happens.
Sent from my GT-I9195 using Tapatalk 4

Looks like the problem is deeper than i thought...
I installed the latest cm10.2 build from the forum here, full wipe cache/dalvik/everything except SD mount, before and after installation.
when coming back to the recovery to install the gapps that I forgot to download, I realized, that i also had issues with the touchscreen in the recovery menu...
I also installed the Kernel (kernel_p4wifi-cm-10.2-20130903-0100-exp.zip) that was provided on the goo.im directory http://goo.im/devs/loosethisskin/p4wifi/cm-10.2
I also experienced some ghost touch issues with the "back" button... Not sure yet if it was because of a specific touching of the frame or an angle of the tabled when lying on my back, holding the tablet in face down. (since I experienced strange behaviour depending on the position sensor)

Related

[Q] Touchscreen locked, is this a software problem?

I am encountering strange touchscreen locks. They occured first with Google Navigation amd always after approx. 20-30 minutes of permanent display usage.
It looks like I would tap on the screen (I see the maginification buttons clicked in the lower right corner), but I cannot go back, because the screen does not react anymore. I have to use the power button twice to get it back to work, sometimes even that does not help. Imagine you want to stop the Navigation software (which is still talking) but you cannot...
This happens also with Navdroid, but the software seems not to be hindered as much as Googles Navigation. In any case, the screen does not react to touch anymore.
I also found this to happen after a longer telephone call, the screen does simply not react anymore, but still shows everything.
I had this effect with Megatron, Void, Prime, Miks CM7 and Andys Gingerbread ROMs, so is this then a hardware or a software (driver) issue? I cannot remember having that with the stock ROM, but that's a long time ago
With the Gingerbread ports there seems to be a problem with the screen after calls but am not too sure if thats the reason for ur problem as u had the same with Froyo.
I am on stock rom and i dont have any such problem. And i have never heard anyone else having the same problem. You could try wiping everything and then flashing a froyo rom again. If that doesn't work, it might be a hardware problem.
In case you do need to send it in to LG, you will have to revert it back to stock condition. When you do that, check if this happens then too.

[Q] Random strange things happening

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.

accelerometer off by 5 degrees

Anyone else have issues with their accelerometer being off. I was trying to play temple run and noticed I had to hold it at an angle for the player to stay in the middle of the screen. Then I loaded up bubble level and it shows it being 5 degrees off. I tried to calibrate it from the screen menu and a factory reset neither of which helped. Should I send to Samsung for repairs?
Hmm, no clue. Have you tried Googling "how to calibrate android accelerometer" or similar?
Sent using Tapatalk
Me too
Man, that's so weird. I had almost the same problem on the same day. Suddenly, my player's accelerometer freaked out. The x axis keeps showing -9 at horizontal position. I have tried calibrating it many times and also tried lots of wipes and even 2 flashes using odin and nothing seems to solve the problem.
My player was bought 2 months ago in Brazil and I have never let it fall or suffer any kind of physical shock. Now I don't know even how to send for repair cause I only have rooted roms to flash on it and support may discover custom roms through CWM recovery on boot.
I'm still pretty sure it's not hardware malfunction. Something has happened and I can't find out how to reset sensors the hard way.
Strange that happened to us on the same day (at least, with me was on 21st).
I'll keep searching for a solution. It's horrible to use the player with this issue. (Not to say, almost impossible.)
Best regards.
I have found this and it seems to work for many ppl. I'll try it later, when I get back home (I'm at work).
First, navigate to /data/system folder and then rename or delete ms3c_yamaha.cfg
Later (you need to have your phone rooted), try this at the terminal:
adb shell
su
/system/bin/sensorcalibutil_yamaha
then place your phone horizontally and still and press enter.
Finally, run the Horizontal Calibration from the Display settings and then reboot.
Really hope it helps and work.
I tried everything I could
So, I got back home and started trying many things I saw on the web.
I reflashed again, using odin, different roms (now I'm keeping Eryigit-GB-2.3.6 G70ZCKPA Galaxy Player 5.0 For USA and INT (Rls:3.5) with rotation off).
I also tried what I have posted before and it didn't work, actually I found 2 files similar to the ones posted before: One is caled sensorlib_yamaha_test.so and the other is sensorlibconfig.so (not pretty sure about the name of the second file).
What happened during my attempts was that: before, the X sensor had the problem (value -9 with the cellphone laid on a desk, at horizontal position) and now, surprisingly, the X sensor is OK and now the Y sensor has the failure.
Using the HORIZONTAL CALIBRATION in SAMSUNG 2.3.6 (or 2.3.5, whatever), the ball only stays in the middle of the screen if I keep my phone in vertical position - upside (cause of the Y axis). Even if I rotate the tab in every direction possible, the ball never goes UP, so it only keeps with negative values and never positive ones.
BUT If I shake the phone, not so hard and not so soft, I see the ball of the calibration software moving on all directions. But when I manage to do it softly (as we do with normal use), the ball never goes up.
I have downloaded many sensor programs to test the calibration and after trying about 20 programs, ONLY ONE have showed the exact values as if the accelerometer was normal, but the calibration of the program did not affect the accelerometer on the system and other programs.
So, this is it, of course I won´t give up and try as many things as I can. Here in Brazil we have a saying that is: I'm Brazilian and I never give up.
P.S. I hope someone reads this and give me ideas. hehe
Thanks in advance.
Have a nice day u all.
Great news - a solution
GREAT NEWS - I HAVE SOLVED IT
Ok, after lots of attempts here is what I did.
I have downloaded android Froyo firmware from a Korean website (its on a thread of android development from galaxy player). Then I flashed it with ODIN and when it turned on, at first it was discalibrated the same way (Y axis only showing from 0 to -9).
I turned the player OFF and then turned it ON holding vol + button to enter in stock recovery mode. In recovery mode I wiped cache and data. Then I tried to calibrate again, with my device upside down and then voila.
Of course it was sort of a luck, but I had to try everything my mind could guess.
After all, I think that maybe It wasn't necessary to flash other roms (but it would be impossible to solve it using ICS due to a lack of calibrator - without having to use terminal / for curious noobies like me).
Then, I always tried to calibrate my tab laying it in horizontal position and that is the why I never got any satisfactory results. When I tried the calibration with the tab in 'incorrect' positions, the problem was solved. I guess, the calibration program tried to compensate the wrong results cause of the vertical position and then it calibrated itself.
Hope this helps someone someday. (But I really hope you won't have this kind of problem. It's frustrating.
Any device you have, if you have accelerometer problems, you should try this idea: wipe data and cache, and the first calibration you do, do it with your device turned to the side that has the wrong value or to the oposite side. This worked for me.
Best Regards,
Very happy Zilian28.
go to settings>display>horizontal calibration lay it on a flat surface and calibrate it
Sent from my GT-I9000 using XDA

[Q] 9100 Got stuck with any rom after booting (Currently with stock one). Help

Hi everyone, Im concerned i might have bricked my phone for good (not good at all). I was using latest Spirit rom when had to change my usb flex since it was not connecting to my pc. After that every time I blocked the screen phone stopped responding. So i decided to go back to stock Rom through Odin.
Now phone boots to the initial screen where Im asked for language and doesnt respond at all. After the flex change usb connection is working again (probably you realized since i used Odin).
What can i try now before reaching the conclusion i have a hardware brick? (if thats possible)
Thanks.
Leo.
UPDATE EDIT.
Phone now has a previous version of stock rom and finally booted. Now i can see that the real problem is that something is making it laggy. The screen does not slide at my touch, rather freezes at its position as soon as I stop touching, and takes really long time block the screen, any thoughts?
...
Some details I will be adding to complement my lack of english vocabulary to explain this issue.
To use any icon at all i have to press twice on it, first attemp pushes the botton down and the second attemp finally activates it. Like if the touch screen is doind weird stuff. I can deduce that the touch screen has everything to do with the laggyness of the phone, maybe power-button has something to do as well.

[Q] Tapping issues on GT-P7510 (Google IO)

Several months ago my old trusted Galaxy Tab 10.1 Z(Google IO) developed a strange problem. I will not be able to tap on certain buttons or select list items (for example in Settings). Not all buttons/items but some. Since that tab was pretty much trashed by my 10 yo I did the factory reset/cache clean but the problem remained.
Finally I got to rooting the tab, cleaned dalvik and regular cache and installed CM 10.2.
But the problem remains so it is really low level, not the OS. Is it hardware problem or can I try something else as far as resetting or installing some packages here?
Work around for me is to change tablet orientation and going from landscape to portrait I get the button/item back.
I also noticed that while typing tapping on the key sometimes produces multiple strokes and sometimes two adjacent keys are tapped (very frustrating to enter any sort of password)
Is there a life left in the device or should I just toss it to the garbage can? Having my Nexus7 bricked recently does not help either so any suggestions will be greatly appreciated

Categories

Resources