[Q] Galaxy Tab 10.1 Touch Screen Unresponsive After Installing Ubuntu to 12.4 - Galaxy Tab 10.1 Q&A, Help & Troubleshooting

I rooted my Galaxy tab 10.1 and then installed Ubuntu. No problems worked great. A couple of days ago I updated Ubuntu to 12.4. Now I'm unable to use the touch screen. That is when I touch the screen to activate an app, move a page or touch home button nothing works. Nothing works in terms of touching the screen with my fingers. However I can use my Samsung Galaxy Tab 10.1 external Keyboard Dock along with my Bluetooth mouse.
I've tried everything form removing Ubuntu installing new ROM to UN-rooting it. I went to Sammobile Firmware for a stock rom to give a fresh start. In installed GT-P7510 ... P7510UEKMP. Still no luck. Does anyone know what I can do and what is causing the problem?
Thanks
Alan

Hardware issue?
I don't think the problem is caused by software

Related

[Q] SGS+ touchscreen doesn't respond when connecting it to notebook using USB?

Hello guys,
I'm using Samsung Galaxy S Plus (I9001).
Whenever I connect it to my notebook for charging the touch screen starts acting weired either not responding or responding with lag.
I have tried other notebooks, PCs and another USB cables but still problem is there.
I also have tried other ROMs.
Am I missing something in the configurations?
Thanks.
Try to help
hweidi said:
Hello guys,
I'm using Samsung Galaxy S Plus (I9001).
Whenever I connect it to my notebook for charging the touch screen starts acting weired either not responding or responding with lag.
I have tried other notebooks, PCs and another USB cables but still problem is there.
I also have tried other ROMs.
Am I missing something in the configurations?
Thanks.
Click to expand...
Click to collapse
Maybe same problem with this one:
http://forum.xda-developers.com/showpost.php?p=42461874&postcount=1342
I also have the same problem to connect my gtab to PC for restocking, its not recognized at all. So I though the problem is because of the new rom I used, I have no idea but uninstal the usb driver and clean the registry as well. Than instal the driver again-restart (windows) and connect my Gtab to PC done. It Works again. :good:
Its my first post, so I hope its usefull for everyone.
Greeting from Jakarta.
Thanks, the problem solved after moving from stock ROM to custom ROM.
Currently, I'm using [ROM][JB][JZO54K] CyanogenMod 10 by ivendor - Release 2.5 - Kernel 3.0.x and it's working great

Galaxy S3 Allshare Cast problem

Please someone help!
I've tried a couple of ROMs on my Galaxy S3 i9300, and the one I took a shine to was the Foxhound 1.4.
Love everything about it but I cant seem to get the Allshare Cast function to work.
I have the dongle, and the phone connects, but after a few seconds it disconnects again.
This happens on every ROM i try.
Does anybody know how to fix this?
Before I rooted my phone and it was completely stock, I did not have the Allshare Cast function in settings.
This has arrived after an update from Samsung, but since I'm on root and custom ROM i never got this update.
May this be why it dont work?
My girlfriend has stock unrooted S3 and the Allshare Cast works perfectly.
Wonder if I have to unroot my phone, update it from Samsung, then do it all over again...?!
Hope someone can help me.. Drives me insane

Screen corruption

GT-P7510 (wifi/us)
Hi, today my tab started to show some real bad screen corruption. The colors are all garbled and the text very blurry. No matter what setting on the tab, nothing makes it right.
Last week I flashed the stock UK ICS rom via the Odin method from this forum. Everything was great until today...
I do not think this problem is related to the rom, because it happend before in HC 3.2 BEFORE I even rooted the tab.
Also, the problem persists even when the tab is "off" as you can see the corrupted charging screen. Recovery and download modes also show the corruption.
Has anyone experienced a similar problem? What can be done (the tab is out of warrant).
I attached photos of the tab exhibiting the problem.
Thanks for your time!
If you search the forum, you'll find that a few others had the same issue. If I remember correctly, they had to send it to Samsung, as it is a hardware issue.
Sent from my amazing 10.1 galaxy tab

Bluetooth keyboard won't type on Galaxy Tab 2 10.1

I just purchased a Zaggkeys Flex keyboard for a friend that has a Samsung Galaxy Tab 2 10.1. I followed the instructions and paired the keyboard to the device, but it will not type when I press any of the keys. I paired the Flex keyboard to my Samsung Infuse 4g and it worked without any problems. However what I noticed is that when I connect the Flex keyboard to my Infuse it automatically switches from the Android on-screen keyboard to the Samsung on-screen keyboard as the input method and then it works. However when I looked at the input methods on the Galaxy Tab the only option available is the Android on-screen keyboard. The tablet is rooted and is running Cyanogenmod 10.1. I am not the one that rooted the tablet and I am wondering if the person that did deleted the Samsung keyboard or if this happens with Cyanogenmod 10.1 or if this is even the problem. I also tried using apps like blueinput and bluekeyboard, but when trying those I received the message that HID is not supported by the device which I don't believe is correct because I have seen many posts stating how easily this keyboard normally pairs with the Galaxy Tab.
Please let me know if you think it is something with the way the tablet was rooted or if it has to do with Cyanogenmod 10.1 or any other problems that may be causing this issue and any solutions you may have. Or at the very least is there anyway I can get the Samsung on-screen keyboard back onto the tablet to see if that is the problem?? This is very frustrating especially since this keyboard was supposed to be a graduation gift. Please help

Unresponsive touches?

I recently flashed CM 10.1 on my samsung infuse, it's working great except for one thing: The screen is not responding properly. Every now and then, I have to tap on my selection multiple times before it registers a touch, and I didn't have this problem before flashing the ROM. Is it a problem with the ROM, or is it my phone? I didn't have this problem before flashing it.

Categories

Resources