yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] shaz999:
hi guys...am only geting wifi at home...not workin at my brothers house. it keeps conecting and disconecting..however when i boot from windows the wifi works ok at his house!...i was using tytung v 2.8 gingerbread... i have made a fresh instal using tytung v 3.0 gingerbread but the problem is stil there.....using a htc hd2 running andrtoid from sd card.........please could somebody shed sum light!!!....
[Android Q&A, Help & Troubleshooting] otnos:
Most likely it is the router, not your phone.
[Android Q&A, Help & Troubleshooting] redpoint73:
Yeah, you might just need to power cycle your brother's router.
[Android Q&A, Help & Troubleshooting] shaz999:
hmm not to sure if its the router...as i mentioned if i switch the phone to windows it connects to the internet without a problem....same to be having the same problem at my cousins and my sisters house!....3 routers couldnt possibly need repowering?...any body got any other ideas?!.....
[EVO 4G Q&A, Help & Troubleshooting] ringoshu:
Hello,

I own a rooted Evo with CM7. For some time now I've noticed that my device only connects to 2G/1xRTT and not EVDO. I have tried many apps to force it into 3G but it doesn't even try to connect or anything. 4G and WIFI work just fine. I would like to be able to use 3G cause there's not 4G signal everywhere I go, especially here in San Francisco.

I tried the following:

* Installed a Sense Rom and updated profile, PRL, etc.

* Calling Sprint (Had a bad representative who said it's probably connected and didn't believe me)

I have the latest PRL and I'm pretty sure I have the latest radio. Here is the version number:

Baseband Version: 2.15.00.11.19

PRL: 60681

I thought maybe updating the radio or PRL to a lower version would fix it but I've read the risks of messing with the radio and bricking your phone, so if I do it, I would like to clearly understand what is it that can brick the phone.

Any thoughts?

Thanks again.

UPDATE: I actually did not have the latest radio. Now I have version 2.15.00.0808
[Thunderbolt Q&A, Help & Troubleshooting] JillyBohnson:
Anyone else experiencing the phone freezing for a few seconds & then reboots? I'm stock, not rooted & have done a factory reset. Still does reboot & its driving me crazy. Thanks.
[Thunderbolt Q&A, Help & Troubleshooting] loonatik78:
Not a lot of info there, Jilly....

What RUU are you running?
[Thunderbolt Q&A, Help & Troubleshooting] fixxxer2008:
ive had none since the last ota radio was released.
[Thunderbolt Q&A, Help & Troubleshooting] loonatik78:
I can tell ya how to! Rip out Ziggy's latest kernel and run my script on it. It will crash and reboot every 5 minutes all day long.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] idsam:
Please don't try anything mentioned below, if you are not familiar with flashing roms and programming ! You've been warned !

The following steps had been done in 4 sets of Galaxy Tab 10.1 (from different sources), all touchscreens become unresponsive within a minute. The system is still running, volumn keys are working, orientation sensor is operational, even the clock and wifi signal is fine. The only problem is the touchscreen. All 4 devices are not rooted, brand new, fully charged, and now returned to Samsung for inspection. :(

WARNING !!! The following steps may cause you trouble ! I share these steps only because I think some experts here may be able to solve it ! I'm also looking for some proof, if the same problem occurs to Samsung Tab 10.1 devices in different countries.

The steps to trigger an unresponsive touchscreen :

(1). Download and install any file manager from the Market (skip if you already have).

(2). Browse to "/sys/devices/virtual/sec/sec_touch/".

(3). Select all files (excluding folders).

(4). Copy and paste to any other location that have write permission (such as sdcard). Some of the files are not allowed to be copied, so just skip it.

And then, in a short while, the touchscreen will not respond anymore. :mad:

The files mentioned in step 2, are some driver files of Atmel mxt1386 (the touchscreen hardware). It seems that users of Acer Iconia also have touchscreen issue, turned out to be using the same hardware.

I know that there are also many users that do not have any touchscreen problem. This may only because those files are not accidentally accessed yet. I'd rather hope that you have a different version of the hardware driver that does not have such problem. :o

I'd like to ask for help from experts and developers here. But please don't try it if you are not absolutely confident to at least restore the system. Please don't blame me if your Tab becomes un-usable.

For those who are willing to try (at your own risk), I'm much appreciated. And I'd like to say thank you to all of you. Your effort may be helping a lots of users who have this problem.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] tier.ru:
Hey idsam,

have you got any ideas how to fix touchscreen broken this way?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] dannstarr:
Im sorry, I dont get this.

To me its like saying "I removed my battery and now my device won't turn on"

So, if I dont mess around with my system files and touch screen drivers, then my touch screen will be fine?

If you mean something else, please explain
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] tier.ru:
Yeah, you got wrong.

Topic starter made too complicated example. The simple description is: if you try to read files from /sys/devices/virtual/sec/sec_touch/ directory - you'll got broken touchscreen. Looks like this operation damages touchscreen firmware, though this won't happen with properly configured/written (by manufacturer) system.

So who wants to read from those files? Any software for any reason. E.g. a lot of users have bricked their devices by doing a full system scan with Dr.Web for Android antivirus.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] idsam:
Sorry for the complicated example. I just tried to provide as much information as I could.

Feedback from Samsung is that it need hardware replacement (which is weird due to a software issue). But when they have a lots to sell, they simply says that they don't have parts for replacement at this moment. And they confirmed that flashing rom does not recover the device. :(

Yes. In most cases, we won't touch those files, except using any kind of antivirus software. I don't think it is limited to one brand, unless the antivirus software doesn't scan system files at all. :p

Besides, I also noticed that some Tablet users talked about unresponsive touchscreen : some said it happened suddenly; some said after charging for a while; some said having a useless device when woke up in the morning. It is hard to believe that all caused by the same antivirus software, right ?

What I've mentioned in the first post, is a way to trigger the problem. There may be other causes I'm not aware of. Some experts here may be interested in this issue. But it will be quite difficult for them, if they don't know how to replicate the case. This is why I posted the steps in the first place, and hope someone can help.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] IDroidThere4Iam:
When the touchscreen goes unresponsive, do other parts of the device still function? For example, when you hold down the power button, will the shutdown menu appear? When you rotate the device will the orientation change?

I have had an unresponsive touchscreen many many times. I'm not sure it is the same unresponsive touchscreen you talk about here. When mine goes unresponsive I can still use the power button and if I rotate the screen a few times it eventually becomes responsive again.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] idsam:
Yes. The power and volume up/down buttons work, orientation sensor also works as a normal device. I tried to rotate the screen, discharge and recharge the battery, but it aside for hours and tried again, nothing helps.

And it is actually confirmed by Samsung that hardware replacement is needed. They said that they tried to recover the device by flashing rom, but failed.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] Lanky14:
so I have the same problem. Quite frustrating. Not only that, I've noticed that there is a vertical 1-2 inch area from top to bottom of the screen that doesn't ever respond to touch.

I'm sending it to Samsung
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] AlexNovoross:
Hi Idsam, I'm from Russia and have a same problem. After full scan by Dr. Web the touchscreen not responding and now I don't know what to do, beacause I've bought my Samsung in USA in Bestbuy, but now I'm at home in Russia, no warranty, no service, nothing. May be somebody can give me advise?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] idsam:
To be honest, it seems that Samsung doesn't have a solution yet. And probably worse, Samsung did not modify the driver at all, which means Atmel is responsible to fix the problem. No matter what, you can wait, but who knows how long it takes.

I think Best Buy has refund policy. You should discuss with them asap, as this kind of policy is normally time limited. You may consider to pay for delivery, in order to minimize your lost. If they refuse to refund for you, then you may need to contact Samsung Russia. I'm sure they know about this issue, and perhaps you may discuss with them. Still, you may need to consider to pay a little more as repair service charge.

BUT, I'm not saying you should pay more for what they've done wrong. It is only a suggestion, in order to speed up the process and at least minimize your lost.

The last option, I think, is to wait until Samsung announce a solution. If the method to fix it doesn't require hardware exchange, perhaps you may get information from Samsung and try to solve it by yourself.

As I know, when the touchscreen issue occurred, the Android system is actually still running WITHOUT problem. It means that you may still control the device by using ADB via USB. So, if Samsung can provide a patch, it may be easily fixed. I'm not sure if it is possible or not, just hope it will be as simple as that.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] oawalker:
I think I heard to get it on hold the lock button for 10 seconds then touch the screen the it should turn bk on try it let me know if it works
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] AlexNovoross:
Thanks for your answer. As I understood we have to wait patch from Samsung and when they provide this patch then problem can be fix without hdd replacement?

---------- Post added at 07:28 AM ---------- Previous post was at 07:23 AM ----------

No, it doesn't help. Only one method left - use the hammer.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] idsam:
Thanks for your suggestion, which I tried before and didn't help. Actually, I wouldn't start this thread if it is that simple. But probably too risky for anyone to try to fix this. :(

I can't say if hardware replacement is needed or not. I just *HOPE* that a patch will be able to fix the problem, which should be the best news for all of us.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] oawalker:
I hope Samsung can patch this up when they update to 3.2 if that update comes
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] g.s.w:
Does this mean i Lost my Tap if that patch did't come out..:confused::eek::mad:

!!!???
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] idsam:
Honestly, only Samsung can answer your question. But my steps can help you to show proof to them that it is a design flaw, and force them to admit that it is their responsibility to provide solution.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] sp3dev:
This is, unfortunately, the known issue with all mxt1386, mxt224 and qt64-blah-something touchscreens. I have wasted a week debugging my iconia and have experienced tons of butthurt. To put it simple, when an error occurs in the touchscreen controller, it does not report proper ID, but an error code instead. Some versions of drivers (like Asus one) just return -ENODEV in that case. Acer's driver was intended to handle it, but was written poorly and died in a deadlock in such an event. My solution was to comment out semaphores and other synchronization techniques and that got past the device detection and cleared error bits.

You can read more in http://xdaforums.com/showthread.php?t=1143892 and try to use the drivers from iconia (the patched drivers are also uploaded and there's a link in that thread)
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] joealley:
I have the same problem with my Galaxy Tab P1010. I can get into download and recovery mode i can move the selection using the volume button but i can't press the power to enter my selected option. :( I have already tried re-installing the latest available firmware for my device using ODIN 1.7. Eventually everything seems to be ok until i reach the point where you select the language. I can't select any option mainly because the touchscreen is unresponsive. All along i thought this problem is only software? Hopefully somebody can find the solution to this.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] idsam:
It seems that the second link is invalid. Besides, it is necessary to root the device and flash CWM recovery first, right ?

I mean, it may be a bit risky. I read your post before, but not sure if it is the same issue. If it is not, and the device is rooted, the official warranty may be voided too.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] sp3dev:
I have updated the links but the recovery image is only valid for the Iconia tablet. I mean, one could try using the attached driver sources and add them to the kernel but that will require at least flashing custom kernel. Samsung seems to be releasing a firmware update to fix this issues but people familiar with linux kernel development may try experimenting with the driver from acer.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] ClericDade:
Just tried - and my Galaxy Tab still has touch. I want to back my tab to shop so i want this guaratee problem)
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] laflaf3d:
Hi,

If this trouble happend to you, you can try to connect a mouse to still use your tablet. My touchscreen not responding at all and I continue to use it with a mouse :victory:

Kind regards
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] k1mu:
Wow. Samsung says that repairing this needs hardware replacement?

That's utter nonsense.

http://xdaforums.com/showthread.php?p=32585690#post32585690
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] wamaOnline:
Can I have the same problem on my galaxy tab 8.9 LTE ? Having the same symptoms after flashing ICS
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] k1mu:
It's possible, but unlikely. A new ROM shouldn't do anything this bad to the tablet unless you powered it off at exactly the wrong time.

If you have ADB installed and can shell into the tablet, you can try using "adb shell" to log in from your PC.

Then type "su" and enter, then

cat /sys/devices/virtual/sec/sec_touchscreen/tsp_firm_update

Wait a little while (about 3 minutes or so), then

exit

adb reboot

That'll fix it.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] wamaOnline:
Hello joealley , I have the exact same problem, did you ever get to fix it ?

---------- Post added at 01:57 AM ---------- Previous post was at 01:46 AM ----------

Thanks for you reply, however the command didn't work, there is no tsp_firm_update file

Moreover, there is a debug_log there, but when i try to "cat" on it i get the following

root@android:/ # cat /sys/devices/virtual/sec/sec_touchscreen/tsp_firm_update
sh: cat: /sys/devices/virtual/sec/sec_touchscreen/tsp_firm_update: No such file or directory

root@android:/ # cat /sys/devices/virtual/sec/sec_touch/debug_log
sh: cat: /sys/devices/virtual/sec/sec_touch/debug_log: I/O error

# Files under /sys/devices/virtual/sec/sec_touch/
debug_log fw_bin fw_bin_slv power/ uevent
debug_mode fw_bin_detail fw_dev subsystem/

---------- Post added at 02:03 AM ---------- Previous post was at 01:57 AM ----------

I should also note that am running CM10 now to be able to connect using adb to start with, stock ROM doesn't respond to ADB [ maybe there is a flag i can set using recovery mode ? ]
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] k1mu:
It may be that you're running a different driver from the Gtab, which doesn't create that device node. Or, it doesn't get created due to the failure of the maxtouch to initialize.

Since you've got adb working, you can try rebooting, then use "adb shell dmesg >dmesg.txt" right after the boot completes.

Search that for maXTouch and see if you get something like the following:

That "no acknowledge from address 0x4c" is the key to the issue - the touchscreen controller is in firmware update mode and won't allow you to talk to it until you finish the update. What I did to fix my GTab was to modify the kernel source to detect this problem and finish the firmware update.

If you're not seeing anything like the above during boot, then you have some other problem.

If you ARE seeing this 'no acknowledge', then with kernel source you can build a new kernel that fixes it.

Edit: the ADB not working with stock is probably due to USB debugging not being enabled.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] wamaOnline:
Thanks for that, ok so didn't get the exact same messgae, but got this

<3>[ 21.554504] ERROR sdio_cmux_open: Wait Timed Out for ch0
<3>[ 21.554534] ERROR sdio_ctl_open: sdio_cmux_open failed with rc -110
<6>[ 21.794525] [TSP] TSP reset & TA/USB connect
<6>[ 22.590179] [TSP] MELFAS_ESD Detection
<6>[ 22.590270] melfas_touch_power_enable off
<3>[ 23.054504] ERROR sdio_cmux_open: Wait Timed Out for ch0
<3>[ 23.054626] ERROR sdio_ctl_open: sdio_cmux_open failed with rc -110
<6>[ 23.294525] melfas_touch_power_enable on
<6>[ 23.804534] [TSP] TSP reset & TA/USB connect
<3>[ 24.554504] ERROR sdio_cmux_open: Wait Timed Out for ch0
<3>[ 24.554656] ERROR sdio_ctl_open: sdio_cmux_open failed with rc -110
<6>[ 24.615325] [TSP] MELFAS_ESD Detection

then the coming lines repeated a lot

<6>[ 123.934478] [TSP] MELFAS_ESD Detection
<6>[ 123.934539] melfas_touch_power_enable off
<6>[ 124.644439] melfas_touch_power_enable on
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] wamaOnline:
Adding the output of dmesg in case it helps
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] wamaOnline:
Do you think compiling kernel from source can help here ?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] iamgreen:
Hello. I have same problem - galaxy tab 10.1

after full san Dr.Web antivirus touch screen not work.

I try make hard reset - not help.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] k1mu:
Uninstall Dr. Web and make sure to tell them that they're idiots. There is no reason whatsoever for an "Antivirus" to be reading files in /sys. None.

They broke your device - I'd ask them to replace it. :)

To fix it, you'll need to install a kernel that recognizes the problem and resets the touch screen chip. I think that Pershoot incorporated my changes into his kernel, so installing one of his updates may fix it. Or, you can grab mine (which is for the WiFi GT-P7510) and use that to recover your touchscreen. http://www.rickmurphy.net/mxt1386_fixer.zip

Push it to your tablet's /sdcard using adb, boot into recovery, and use "install zip from sdcard" to install it. Boot the tablet and wait - it'll take a lot longer than usual to finish booting. Once that's done, check the touchscreen. If it's not yet working, reboot one last time.

If you're not using a P7510, you'll need to install a kernel for your device to get your radios back. Look in the Android Development section.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] iamgreen:
IT WORKS :laugh::good:. Thank's a lot!
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] k1mu:
That is fantastic news. Samsung would have told you the tablet was trashed. It's great that yours is fixed.

Now, don't forget to leave thanks - without the click, it didn't happen. :)

Oh, and also tell Dr Web that reading devices in /sys will destroy devices. I can't leave 'em feedback since I'm not a user.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] iamgreen:
They knew it, and everything that they says - we fixed this problem in our program, call to samsung service.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] MacMillan25:
Thank You!!! It Works!! After flashing the file stopped working 3G! I just flash the tablet again and it worked! :laugh:
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] k1mu:
Thanks. That's another way to fix this - flash the fix, then re-flash an appropriate ROM that has the appropriate modem to allow your network to work again.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] fredor73:
Apply for tab 8.9 I957?

Excuse for involve tab 8.9, but, I have the same problem of TS tried in this discution and I can't find a solution. Apparently, is possible fix the problem in tab 8.9 using the method mentioned here. Is it possible?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] k1mu:
Yes, it's quite possible. It's a small change to the kernel source. If you can find kernel source for your tab 8.9 and send me a pointer, I can try to build it with the fix installed.

Edit: The A1 kernel already has the fix incorporated. Go to the Galaxy Tab 8.9 Android Development forum, find the A1 kernel, and install it on your tab. That should fix it for you.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] jamracer:
got the same problem with my i957, after ics update the touch screen stop responding, any suggestions

i wipe factory reset, reflash isc, flash hc, still notn responds, took it apart took out the digitizer cable noting same way
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] gcarterny:
Anyone know if this would work on the gt-5110 model?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] k1mu:
No - the GT-5110 is not a Tegra-based device, so the fix doesn't apply. (The 5110 is a TI OMAP).
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] asdms:
help me please!

help please! my galaxy tab 3 8.0 T310, was badly run sensor
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] einjelhart:
touchscreen

is this also work on TAB 3 8.0?
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] k1mu:
It's not likely as it's very different hardware. What symptom are you having?

The Tab 10.1 problem basically left you in a state where the screen would turn on, but not respond to touches.

If you can connect to your tablet using ADB, an "adb dmesg" command soon after boot may help with telling what's failing if it's just a touchscreen issue.

If you have a USB OTG adapter, you may be able to plug in a USB keyboard so you can log in to the tablet as well if the touchscreen is dead - those cables are fairly cheap.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] einjelhart:
touchscreen

mine is the touchscreen is not responding well. sometimes it works but it's hard. the lastime i just stop on running apps some application like google services and more and it works perfectly i thought there's some apps that triggering the non responsive touchscreen. when i tried to restart or press the power button the problem of the touchscreen is back. can some one help me on this. im planning to wipe the system and install the stockroom but i'm afraid. power button is working properly i can rotate the screen, lower the volume everything is perfectly working but only the touchscreen is not responding well.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] k1mu:
If it's working at all, then the fix I discovered won't work for you. In my case, the touchscreen was entirely disabled because the controller chip had lost it's firmware.
[Galaxy Tab 10.1 Q&A, Help & Troubleshooting] mercu3:
Hi,

This is my log, very similar to yours few pages back.

Applied your fix, but still no answer from the screen.

Any new idea?

My tab was working perfectly until it suddenly stopped. I can´t remember if I installed any app before the failure, as other users mentioned.

Maybe the chip is dead?